<?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 RE: True VSP Fabric BCB IP management in ExtremeSwitching (VSP/Fabric Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/true-vsp-fabric-bcb-ip-management/m-p/8695#M276</link>
    <description>I tried to see if I could add a loopback interface to a Management VRF, but this didn't seem possible, so I'd end up with the BCB becoming a BEB if I added an "up" interface to the created Management VLAN.</description>
    <pubDate>Fri, 15 Feb 2019 19:56:00 GMT</pubDate>
    <dc:creator>Michael_Wentwor</dc:creator>
    <dc:date>2019-02-15T19:56:00Z</dc:date>
    <item>
      <title>True VSP Fabric BCB IP management</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/true-vsp-fabric-bcb-ip-management/m-p/8692#M273</link>
      <description>Please provide build information to build a Fabric, and IP managing the BCB Core switches from a Central station, because once you add a management C-VLAN it's no longer a BCB with only NNI interfaces. When you elable IP Shortcuts, the Core learns all the routes.&lt;BR /&gt;
&lt;BR /&gt;
I could create a non-isid vlan and manage the Cores, but are there better options?&lt;BR /&gt;
&lt;BR /&gt;
Is there any technique of managing a BCB without adding IP Shortcuts, because I don't believe a true BCB should be aware of all the routes.&lt;BR /&gt;
&lt;BR /&gt;
Thanks</description>
      <pubDate>Fri, 15 Feb 2019 16:04:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/true-vsp-fabric-bcb-ip-management/m-p/8692#M273</guid>
      <dc:creator>Michael_Wentwor</dc:creator>
      <dc:date>2019-02-15T16:04:00Z</dc:date>
    </item>
    <item>
      <title>RE: True VSP Fabric BCB IP management</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/true-vsp-fabric-bcb-ip-management/m-p/8693#M274</link>
      <description>Are you using VSP7200s or 8000?&lt;BR /&gt;
&lt;BR /&gt;
If your BCB are VSP7000s or VSP8000s you can set up the Out-of-Band management interface with a Management IP.&lt;BR /&gt;
&lt;BR /&gt;
On the VSP7Ks and 8K, the OoB interfaces is not routed, does not participate in the fabric, and is not part of the routing table.</description>
      <pubDate>Fri, 15 Feb 2019 19:43:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/true-vsp-fabric-bcb-ip-management/m-p/8693#M274</guid>
      <dc:creator>EXTR_Paul</dc:creator>
      <dc:date>2019-02-15T19:43:00Z</dc:date>
    </item>
    <item>
      <title>RE: True VSP Fabric BCB IP management</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/true-vsp-fabric-bcb-ip-management/m-p/8694#M275</link>
      <description>Thanks for the response Paul.&lt;BR /&gt;
My statement "I could create a non-isid vlan and manage the Cores" was due to only having 4450s in our LAB, but yes, the OOB interface on the 8000s.&lt;BR /&gt;
&lt;BR /&gt;
So, you're not aware of any other way of achieving IP management of the BCB doesn't cause the route learning......some special command?&lt;BR /&gt;
&lt;BR /&gt;
Thanks again anyway....much appreciated.</description>
      <pubDate>Fri, 15 Feb 2019 19:50:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/true-vsp-fabric-bcb-ip-management/m-p/8694#M275</guid>
      <dc:creator>Michael_Wentwor</dc:creator>
      <dc:date>2019-02-15T19:50:00Z</dc:date>
    </item>
    <item>
      <title>RE: True VSP Fabric BCB IP management</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/true-vsp-fabric-bcb-ip-management/m-p/8695#M276</link>
      <description>I tried to see if I could add a loopback interface to a Management VRF, but this didn't seem possible, so I'd end up with the BCB becoming a BEB if I added an "up" interface to the created Management VLAN.</description>
      <pubDate>Fri, 15 Feb 2019 19:56:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/true-vsp-fabric-bcb-ip-management/m-p/8695#M276</guid>
      <dc:creator>Michael_Wentwor</dc:creator>
      <dc:date>2019-02-15T19:56:00Z</dc:date>
    </item>
    <item>
      <title>RE: True VSP Fabric BCB IP management</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/true-vsp-fabric-bcb-ip-management/m-p/8696#M277</link>
      <description>Yes, I can understand your thinking.   I can't recommend that because that IP will still be in the Local routing table.  and I would need to test if that IP interface will be reachable from a BEB or other edge device if that IP/VLAN doesn't have an ISID.   &lt;BR /&gt;
&lt;BR /&gt;
the ULTIMATE solution would be to put all your management in the GRT, then use VRFs/L3VSNs for all your service traffic.  Do you have the Premier Licenses?&lt;BR /&gt;
&lt;BR /&gt;
That would be best practice.</description>
      <pubDate>Fri, 15 Feb 2019 20:01:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/true-vsp-fabric-bcb-ip-management/m-p/8696#M277</guid>
      <dc:creator>EXTR_Paul</dc:creator>
      <dc:date>2019-02-15T20:01:00Z</dc:date>
    </item>
    <item>
      <title>RE: True VSP Fabric BCB IP management</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/true-vsp-fabric-bcb-ip-management/m-p/8697#M278</link>
      <description>&lt;BR /&gt;
&lt;BR /&gt;
Management is only possible from the GRT and the OoB interfaces.  This is a good thing and what makes VOSS very secure.  &lt;BR /&gt;
&lt;BR /&gt;
IPs in VRFs or L3VSNs will not reply to Http/https/telnet/ssh/SNMP etc etc....</description>
      <pubDate>Fri, 15 Feb 2019 20:03:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/true-vsp-fabric-bcb-ip-management/m-p/8697#M278</guid>
      <dc:creator>EXTR_Paul</dc:creator>
      <dc:date>2019-02-15T20:03:00Z</dc:date>
    </item>
    <item>
      <title>RE: True VSP Fabric BCB IP management</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/true-vsp-fabric-bcb-ip-management/m-p/8698#M279</link>
      <description>Hi Michael,&lt;BR /&gt;
 &lt;BR /&gt;
This needs a bit effort,&lt;BR /&gt;
However, you can use SPB shortcut routing with a Loopback Address (CLIP), in GRT.&lt;BR /&gt;
For unwanted route learning you can use ISIS accept policy’s / route maps, to prevent/control IP route learning on your BCBs.&lt;BR /&gt;
(e.g. you would only accept routes to (within) your Management Network (IP Subnet) / Central station)&lt;BR /&gt;
(or just accept a default-route)&lt;BR /&gt;
 &lt;BR /&gt;
Best regards&lt;BR /&gt;
Niko</description>
      <pubDate>Mon, 18 Feb 2019 22:42:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/true-vsp-fabric-bcb-ip-management/m-p/8698#M279</guid>
      <dc:creator>Niko_P</dc:creator>
      <dc:date>2019-02-18T22:42:00Z</dc:date>
    </item>
  </channel>
</rss>

