<?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 segmented management on 5520 running VOSS in ExtremeSwitching (VSP/Fabric Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/segmented-management-on-5520-running-voss/m-p/83607#M1444</link>
    <description>&lt;P&gt;Hi, has anybody gotten a 5520 running VOSS and acting as a router with two routed interfaces (VLANs with IPs) to have the segmented management VLAN be accessible from both sides of the router?&amp;nbsp; I created VLANs A and B on the 5520, assigned (public, routable) IPs to them, and then created a segmented management VLAN, and gave it an IP on the same subnet as VLAN A, with VLAN A’s IP address as it’s default route.&lt;/P&gt;&lt;P&gt;I can SSH to the segmented management VLAN address, but ONLY when I’m physically connected to anything on VLAN A side of the router, including devices going through another router that connects the VLAN A.&amp;nbsp; Anything on VLAN B or connected to the VLAN B side, cannot SSH to the segmented management VLAN address.&lt;/P&gt;</description>
    <pubDate>Fri, 05 Mar 2021 01:16:25 GMT</pubDate>
    <dc:creator>Chi</dc:creator>
    <dc:date>2021-03-05T01:16:25Z</dc:date>
    <item>
      <title>segmented management on 5520 running VOSS</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/segmented-management-on-5520-running-voss/m-p/83607#M1444</link>
      <description>&lt;P&gt;Hi, has anybody gotten a 5520 running VOSS and acting as a router with two routed interfaces (VLANs with IPs) to have the segmented management VLAN be accessible from both sides of the router?&amp;nbsp; I created VLANs A and B on the 5520, assigned (public, routable) IPs to them, and then created a segmented management VLAN, and gave it an IP on the same subnet as VLAN A, with VLAN A’s IP address as it’s default route.&lt;/P&gt;&lt;P&gt;I can SSH to the segmented management VLAN address, but ONLY when I’m physically connected to anything on VLAN A side of the router, including devices going through another router that connects the VLAN A.&amp;nbsp; Anything on VLAN B or connected to the VLAN B side, cannot SSH to the segmented management VLAN address.&lt;/P&gt;</description>
      <pubDate>Fri, 05 Mar 2021 01:16:25 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/segmented-management-on-5520-running-voss/m-p/83607#M1444</guid>
      <dc:creator>Chi</dc:creator>
      <dc:date>2021-03-05T01:16:25Z</dc:date>
    </item>
    <item>
      <title>Re: segmented management on 5520 running VOSS</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/segmented-management-on-5520-running-voss/m-p/83608#M1445</link>
      <description>&lt;P&gt;With segmented mgmt with a VLAN the IP is treated just as a mgmt address.&amp;nbsp; Not a routed address.&amp;nbsp; You need to make sure that you give the MGMT VLAN IP a default route.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;4901:1(mgmt:vlan)#ip route ?&lt;BR /&gt;&amp;nbsp; {A.B.C.D/X}&amp;nbsp; Ip address/subnet mask&lt;BR /&gt;&amp;nbsp; {A.B.C.D}&amp;nbsp;&amp;nbsp;&amp;nbsp; IP address&lt;BR /&gt;4901:1(mgmt:vlan)#ip route&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 05 Mar 2021 01:27:42 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/segmented-management-on-5520-running-voss/m-p/83608#M1445</guid>
      <dc:creator>EXTR_Paul</dc:creator>
      <dc:date>2021-03-05T01:27:42Z</dc:date>
    </item>
    <item>
      <title>Re: segmented management on 5520 running VOSS</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/segmented-management-on-5520-running-voss/m-p/83609#M1446</link>
      <description>&lt;P&gt;better example&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color:#000000;"&gt;&lt;SPAN style="color:#000000;"&gt;mgmt vlan 192&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color:#000000;"&gt;&lt;SPAN style="color:#000000;"&gt;ip address 192.16&lt;SPAN style="background-color:#ffee8a;"&gt;8.2&lt;/SPAN&gt;.7/24&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color:#000000;"&gt;&lt;SPAN style="color:#000000;"&gt;ip route&amp;nbsp;&lt;SPAN style="background-color:#6a5a00;"&gt;&lt;SPAN style="color:#ffffff;"&gt;0.0.0.0&lt;/SPAN&gt;&lt;/SPAN&gt;/0 next-hop 192.16&lt;SPAN style="background-color:#ffee8a;"&gt;8.2&lt;/SPAN&gt;.1 weight 200&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color:#000000;"&gt;&lt;SPAN style="color:#000000;"&gt;enable&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color:#000000;"&gt;&lt;SPAN style="color:#000000;"&gt;exit&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color:#000000;"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 05 Mar 2021 01:29:55 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/segmented-management-on-5520-running-voss/m-p/83609#M1446</guid>
      <dc:creator>EXTR_Paul</dc:creator>
      <dc:date>2021-03-05T01:29:55Z</dc:date>
    </item>
    <item>
      <title>Re: segmented management on 5520 running VOSS</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/segmented-management-on-5520-running-voss/m-p/83610#M1447</link>
      <description>&lt;P&gt;Yes, I gave the VLAN A IP address as the default route for the segmented management VLAN interface.&amp;nbsp; I could only SSH to the seg mgmt IP from the VLAN A IP and other networks connected to the VLAN A side.&amp;nbsp; I could not SSH from the VLAN B IP nor any other network connected to the VLAN B side&lt;/P&gt;</description>
      <pubDate>Fri, 05 Mar 2021 01:32:58 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/segmented-management-on-5520-running-voss/m-p/83610#M1447</guid>
      <dc:creator>Chi</dc:creator>
      <dc:date>2021-03-05T01:32:58Z</dc:date>
    </item>
    <item>
      <title>Re: segmented management on 5520 running VOSS</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/segmented-management-on-5520-running-voss/m-p/83611#M1448</link>
      <description>&lt;P&gt;can you dump the config for us please?&lt;/P&gt;</description>
      <pubDate>Fri, 05 Mar 2021 01:44:53 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/segmented-management-on-5520-running-voss/m-p/83611#M1448</guid>
      <dc:creator>EXTR_Paul</dc:creator>
      <dc:date>2021-03-05T01:44:53Z</dc:date>
    </item>
    <item>
      <title>Re: segmented management on 5520 running VOSS</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/segmented-management-on-5520-running-voss/m-p/83612#M1449</link>
      <description>&lt;P&gt;Chi,&lt;/P&gt;&lt;P&gt;From the doc:&lt;/P&gt;&lt;FIGURE&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="d311c0b2055141e5942fb2496660a05d_3cfd4136-5b66-4a10-97e6-53eef1060667.png"&gt;&lt;img src="https://community.extremenetworks.com/t5/image/serverpage/image-id/1819i2E6DC44480DCE458/image-size/large?v=v2&amp;amp;px=999" role="button" title="d311c0b2055141e5942fb2496660a05d_3cfd4136-5b66-4a10-97e6-53eef1060667.png" alt="d311c0b2055141e5942fb2496660a05d_3cfd4136-5b66-4a10-97e6-53eef1060667.png" /&gt;&lt;/span&gt;&lt;/FIGURE&gt;&lt;FIGURE&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="d311c0b2055141e5942fb2496660a05d_2ffd8c26-bede-4f89-8e91-5d9406816a08.png"&gt;&lt;img src="https://community.extremenetworks.com/t5/image/serverpage/image-id/371i53DEE8DB9C1A9C84/image-size/large?v=v2&amp;amp;px=999" role="button" title="d311c0b2055141e5942fb2496660a05d_2ffd8c26-bede-4f89-8e91-5d9406816a08.png" alt="d311c0b2055141e5942fb2496660a05d_2ffd8c26-bede-4f89-8e91-5d9406816a08.png" /&gt;&lt;/span&gt;&lt;/FIGURE&gt;&lt;P&gt;The mgmt IP and the VLAN A IP must match if I not mistaking.&lt;/P&gt;&lt;P&gt;The default gateway is the one defined on your switch and not the VLAN A’s IP&lt;/P&gt;&lt;P&gt;Mig&lt;/P&gt;</description>
      <pubDate>Fri, 05 Mar 2021 05:29:08 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/segmented-management-on-5520-running-voss/m-p/83612#M1449</guid>
      <dc:creator>Miguel-Angel_RO</dc:creator>
      <dc:date>2021-03-05T05:29:08Z</dc:date>
    </item>
    <item>
      <title>Re: segmented management on 5520 running VOSS</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/segmented-management-on-5520-running-voss/m-p/83613#M1450</link>
      <description>&lt;P&gt;just a thought….&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;if your network is routed, just use a CLIP for mgmt.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;mgmt clip vrf GlobalRouter&lt;BR /&gt;ip address 172.17.49.1/32&lt;BR /&gt;enable&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 05 Mar 2021 05:47:54 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/segmented-management-on-5520-running-voss/m-p/83613#M1450</guid>
      <dc:creator>EXTR_Paul</dc:creator>
      <dc:date>2021-03-05T05:47:54Z</dc:date>
    </item>
    <item>
      <title>Re: segmented management on 5520 running VOSS</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/segmented-management-on-5520-running-voss/m-p/83614#M1451</link>
      <description>&lt;P&gt;The point raised is that a mgmt VLAN IP cannot be reached if the same VSP is required to IP route the packet to the mgmt VLAN. This is documented as a limitation. The point is that if the VSP is acting as an IP router, then you should not be using a mgmt vlan IP but a mgmt clip instead.&lt;/P&gt;&lt;P&gt;See the attached slides, slide 19.&lt;/P&gt;</description>
      <pubDate>Mon, 08 Mar 2021 16:25:31 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/segmented-management-on-5520-running-voss/m-p/83614#M1451</guid>
      <dc:creator>Ludovico_Steven</dc:creator>
      <dc:date>2021-03-08T16:25:31Z</dc:date>
    </item>
    <item>
      <title>Re: segmented management on 5520 running VOSS</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/segmented-management-on-5520-running-voss/m-p/83615#M1452</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I’m in the exact same situation.&lt;/P&gt;&lt;P&gt;We have 2 VOSS VSP4900 acting as network core and L3 for all our VLAN.&lt;/P&gt;&lt;P&gt;We cannot access the VSP in the Vlan as before.&lt;/P&gt;&lt;P&gt;I understand we must now use CLIP mgmt, but is somebody know how to configure CLIP MGMT Interface ?&lt;/P&gt;&lt;P&gt;It as to be /32, and how the CLIP Mgmt IP can be reach from other Vlan ?&lt;/P&gt;&lt;P&gt;Thanks for explanation,&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Mon, 08 Mar 2021 18:48:52 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/segmented-management-on-5520-running-voss/m-p/83615#M1452</guid>
      <dc:creator>LionelH</dc:creator>
      <dc:date>2021-03-08T18:48:52Z</dc:date>
    </item>
    <item>
      <title>Re: segmented management on 5520 running VOSS</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/segmented-management-on-5520-running-voss/m-p/83616#M1453</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I found my mistake, Router ISIS SPBM Ip wasn’t activate with IP shortcut as source.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Now Clip are working fine around the network.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Mon, 08 Mar 2021 21:05:06 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/segmented-management-on-5520-running-voss/m-p/83616#M1453</guid>
      <dc:creator>LionelH</dc:creator>
      <dc:date>2021-03-08T21:05:06Z</dc:date>
    </item>
    <item>
      <title>Re: segmented management on 5520 running VOSS</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/segmented-management-on-5520-running-voss/m-p/83617#M1454</link>
      <description>&lt;P&gt;Both sides of the router have publicly routable IP addresses, so I would need to get another IP from the ISP and have them route to it.&amp;nbsp; But the end customer doesn’t really want to do that.&lt;/P&gt;</description>
      <pubDate>Wed, 07 Apr 2021 01:06:51 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/segmented-management-on-5520-running-voss/m-p/83617#M1454</guid>
      <dc:creator>Chi</dc:creator>
      <dc:date>2021-04-07T01:06:51Z</dc:date>
    </item>
  </channel>
</rss>

