<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Vlan philosophy with NetSight - Oneview - Policy - Summit in ExtremeCloud IQ- Site Engine Management Center</title>
    <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/vlan-philosophy-with-netsight-oneview-policy-summit/m-p/34207#M3785</link>
    <description>I am planning for a new switch refresh for our High School.  In my network I have about 75 vlans.  My deployment plan for the new rollout of Summit switches is to have a policy setup to set port vlans based on 1.x and/or mac addresses.&lt;BR /&gt;
&lt;BR /&gt;
I have a existing enterasys  policy domain for my elementary buildings, and I have realized that keeping vlans consistent within devices has been a weak spot.&lt;BR /&gt;
&lt;BR /&gt;
I am planning to establish a gvrp setup.  With all the changes to NetSight, and the obvious migration to oneview, I am researching the best way to create my vlan database.&lt;BR /&gt;
&lt;BR /&gt;
I could enter the vlans one-by-one in oneview, or policy manager, or console....  and hope that they all work off the same global db.&lt;BR /&gt;
&lt;BR /&gt;
I haven't seen any way to import vlan definitions via csv in any of the management tools I have seen so far.&lt;BR /&gt;
&lt;BR /&gt;
Another idea would be to define the vlans on a switch via script, then import the vlans to netsight/oneview from that switch.  For the large number of vlans, this seems like the easiest path.&lt;BR /&gt;
&lt;BR /&gt;
Has anyone been through this with the new netsight (6.3) XOS (16.1) environment?  Is there a preferred place to build the vlans and what is the easiest way to bulk create them?&lt;BR /&gt;
&lt;BR /&gt;
--Keith&lt;BR /&gt;
&lt;BR /&gt;</description>
    <pubDate>Fri, 04 Dec 2015 21:17:00 GMT</pubDate>
    <dc:creator>Keith_Obermeier</dc:creator>
    <dc:date>2015-12-04T21:17:00Z</dc:date>
    <item>
      <title>Vlan philosophy with NetSight - Oneview - Policy - Summit</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/vlan-philosophy-with-netsight-oneview-policy-summit/m-p/34207#M3785</link>
      <description>I am planning for a new switch refresh for our High School.  In my network I have about 75 vlans.  My deployment plan for the new rollout of Summit switches is to have a policy setup to set port vlans based on 1.x and/or mac addresses.&lt;BR /&gt;
&lt;BR /&gt;
I have a existing enterasys  policy domain for my elementary buildings, and I have realized that keeping vlans consistent within devices has been a weak spot.&lt;BR /&gt;
&lt;BR /&gt;
I am planning to establish a gvrp setup.  With all the changes to NetSight, and the obvious migration to oneview, I am researching the best way to create my vlan database.&lt;BR /&gt;
&lt;BR /&gt;
I could enter the vlans one-by-one in oneview, or policy manager, or console....  and hope that they all work off the same global db.&lt;BR /&gt;
&lt;BR /&gt;
I haven't seen any way to import vlan definitions via csv in any of the management tools I have seen so far.&lt;BR /&gt;
&lt;BR /&gt;
Another idea would be to define the vlans on a switch via script, then import the vlans to netsight/oneview from that switch.  For the large number of vlans, this seems like the easiest path.&lt;BR /&gt;
&lt;BR /&gt;
Has anyone been through this with the new netsight (6.3) XOS (16.1) environment?  Is there a preferred place to build the vlans and what is the easiest way to bulk create them?&lt;BR /&gt;
&lt;BR /&gt;
--Keith&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Fri, 04 Dec 2015 21:17:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/vlan-philosophy-with-netsight-oneview-policy-summit/m-p/34207#M3785</guid>
      <dc:creator>Keith_Obermeier</dc:creator>
      <dc:date>2015-12-04T21:17:00Z</dc:date>
    </item>
  </channel>
</rss>

