<?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 Mgmt VLAN not accessible, but ISIS established in ExtremeSwitching (ERS)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-ers/mgmt-vlan-not-accessible-but-isis-established/m-p/76630#M171</link>
    <description>&lt;P&gt;Hi all,&lt;/P&gt;  &lt;P&gt;After an blackout on saturday, I have a very confusing phenomenon on one of my ERS4850. The Switch has active ISIS Adjacencys, but I cannot ping the Mgmt IP Adress, nor can the Switch ping any device inside the Fabric.&lt;/P&gt;  &lt;P&gt;The Mgmt VLAN ISID is correct, and the IP is assigned to the correct Mgmt VLAN.&lt;/P&gt;  &lt;P&gt;I disconnected the Uplinks to my VSP Cores, and rebooted the system, so that the ISIS LSDB is empty. If I connect one of the Uplinks, the Adjacency comes up, and the LSDB fills up with every information I’d think of have to be there. Even a L2 Ping through the Backbone VLANs started on the VSP is sucessful, but I can’t ping the Mgmt IP Adress…&lt;/P&gt;  &lt;P&gt;&amp;nbsp;&lt;/P&gt;  &lt;P&gt;Does anyone have a hint for me, or something I can try to troubleshoot this?&lt;/P&gt;  &lt;P&gt;Or may it just be a hardware defect after the blackout?&lt;/P&gt;  &lt;P&gt;&amp;nbsp;&lt;/P&gt;  &lt;P&gt;Thanks and Best Regards,&lt;/P&gt;  &lt;P&gt;Tobias&lt;/P&gt;</description>
    <pubDate>Tue, 14 Jul 2020 19:28:36 GMT</pubDate>
    <dc:creator>TobiasW</dc:creator>
    <dc:date>2020-07-14T19:28:36Z</dc:date>
    <item>
      <title>Mgmt VLAN not accessible, but ISIS established</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-ers/mgmt-vlan-not-accessible-but-isis-established/m-p/76630#M171</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;  &lt;P&gt;After an blackout on saturday, I have a very confusing phenomenon on one of my ERS4850. The Switch has active ISIS Adjacencys, but I cannot ping the Mgmt IP Adress, nor can the Switch ping any device inside the Fabric.&lt;/P&gt;  &lt;P&gt;The Mgmt VLAN ISID is correct, and the IP is assigned to the correct Mgmt VLAN.&lt;/P&gt;  &lt;P&gt;I disconnected the Uplinks to my VSP Cores, and rebooted the system, so that the ISIS LSDB is empty. If I connect one of the Uplinks, the Adjacency comes up, and the LSDB fills up with every information I’d think of have to be there. Even a L2 Ping through the Backbone VLANs started on the VSP is sucessful, but I can’t ping the Mgmt IP Adress…&lt;/P&gt;  &lt;P&gt;&amp;nbsp;&lt;/P&gt;  &lt;P&gt;Does anyone have a hint for me, or something I can try to troubleshoot this?&lt;/P&gt;  &lt;P&gt;Or may it just be a hardware defect after the blackout?&lt;/P&gt;  &lt;P&gt;&amp;nbsp;&lt;/P&gt;  &lt;P&gt;Thanks and Best Regards,&lt;/P&gt;  &lt;P&gt;Tobias&lt;/P&gt;</description>
      <pubDate>Tue, 14 Jul 2020 19:28:36 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-ers/mgmt-vlan-not-accessible-but-isis-established/m-p/76630#M171</guid>
      <dc:creator>TobiasW</dc:creator>
      <dc:date>2020-07-14T19:28:36Z</dc:date>
    </item>
    <item>
      <title>Re: Mgmt VLAN not accessible, but ISIS established</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-ers/mgmt-vlan-not-accessible-but-isis-established/m-p/76631#M172</link>
      <description>&lt;P&gt;Hi Tobias,&lt;/P&gt;  &lt;P&gt;I understand from you description that you are using fabric connect on the ERS.&lt;/P&gt;  &lt;P&gt;What are the SW version of ERS/VSP?&lt;/P&gt;  &lt;P&gt;Did you tried to swap the two uplinks? It sounds weird but I’ve seen some issues with specific topologies and old firmwares.&lt;/P&gt;  &lt;P&gt;Mig&lt;/P&gt;</description>
      <pubDate>Wed, 15 Jul 2020 03:31:45 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-ers/mgmt-vlan-not-accessible-but-isis-established/m-p/76631#M172</guid>
      <dc:creator>Miguel-Angel_RO</dc:creator>
      <dc:date>2020-07-15T03:31:45Z</dc:date>
    </item>
    <item>
      <title>Re: Mgmt VLAN not accessible, but ISIS established</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-ers/mgmt-vlan-not-accessible-but-isis-established/m-p/76632#M173</link>
      <description>&lt;P&gt;Hi Mig,&lt;/P&gt;  &lt;P&gt;yes, you’re right, the ERS is using fabric connect.&lt;/P&gt;  &lt;P&gt;The ERS Software is 5.12.0.55.&lt;/P&gt;  &lt;P&gt;Yes, I’ve tried to switch the uplinks, but without any positive effect.&lt;/P&gt;  &lt;P&gt;I thing I’m going to create an RMA Case in GTAC for exchange of the system. There was no change exept for the blackout, so the unit may simply got broke…&lt;/P&gt;  &lt;P&gt;However, thanks, and best regards&lt;/P&gt;</description>
      <pubDate>Fri, 17 Jul 2020 14:32:53 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-ers/mgmt-vlan-not-accessible-but-isis-established/m-p/76632#M173</guid>
      <dc:creator>TobiasW</dc:creator>
      <dc:date>2020-07-17T14:32:53Z</dc:date>
    </item>
  </channel>
</rss>

