<?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 Wrong port names in Port Tree for EXOS switches in ExtremeCloud IQ- Site Engine Management Center</title>
    <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/wrong-port-names-in-port-tree-for-exos-switches/m-p/116530#M12400</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I have customer with +30 EXOS/Switch Engine switches (some stand alone, some stacked) and I see that Port Names for those devices are like: "10 Gbps Ethernet Port" or "1 Gbps Ethernet Port".&lt;/P&gt;&lt;P&gt;I enabled "Network Monitor Cache" debugging for PortView feature for core switch and after clicking "Refresh (Rediscover)" I see in server log multiple entries like this:&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;2024-10-29 10:46:13,886 DEBUG [Port] 10.12.1.9 DeviceEntityData: getPhysicalPorts(true) add port: IfIndex:1010 Name:[10 Gbps Ethernet Port Description:[null] Dot1dIndex:10 isLogical:false isLag:false&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;2024-10-29 10:46:13,886 DEBUG [Port] 10.12.1.9 DeviceEntityData: getPhysicalPorts(true) add port: IfIndex:2034 Name:[10 Gbps Ethernet Port Description:[null] Dot1dIndex:162 isLogical:false isLag:false&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;Do you have some ideas how to fix it?&amp;nbsp;Now I'm seriously considering NMS reinstallation&lt;/P&gt;</description>
    <pubDate>Tue, 29 Oct 2024 10:27:28 GMT</pubDate>
    <dc:creator>Bartek</dc:creator>
    <dc:date>2024-10-29T10:27:28Z</dc:date>
    <item>
      <title>Wrong port names in Port Tree for EXOS switches</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/wrong-port-names-in-port-tree-for-exos-switches/m-p/116530#M12400</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I have customer with +30 EXOS/Switch Engine switches (some stand alone, some stacked) and I see that Port Names for those devices are like: "10 Gbps Ethernet Port" or "1 Gbps Ethernet Port".&lt;/P&gt;&lt;P&gt;I enabled "Network Monitor Cache" debugging for PortView feature for core switch and after clicking "Refresh (Rediscover)" I see in server log multiple entries like this:&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;2024-10-29 10:46:13,886 DEBUG [Port] 10.12.1.9 DeviceEntityData: getPhysicalPorts(true) add port: IfIndex:1010 Name:[10 Gbps Ethernet Port Description:[null] Dot1dIndex:10 isLogical:false isLag:false&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;2024-10-29 10:46:13,886 DEBUG [Port] 10.12.1.9 DeviceEntityData: getPhysicalPorts(true) add port: IfIndex:2034 Name:[10 Gbps Ethernet Port Description:[null] Dot1dIndex:162 isLogical:false isLag:false&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;Do you have some ideas how to fix it?&amp;nbsp;Now I'm seriously considering NMS reinstallation&lt;/P&gt;</description>
      <pubDate>Tue, 29 Oct 2024 10:27:28 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/wrong-port-names-in-port-tree-for-exos-switches/m-p/116530#M12400</guid>
      <dc:creator>Bartek</dc:creator>
      <dc:date>2024-10-29T10:27:28Z</dc:date>
    </item>
    <item>
      <title>Re: Wrong port names in Port Tree for EXOS switches</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/wrong-port-names-in-port-tree-for-exos-switches/m-p/116533#M12401</link>
      <description>&lt;P&gt;This issue has been seen resulting from problematic EXOS firmware in the 31.7.3/32.x branches. The switches sometimes do not respond to SNMP walks and in this case it looks like the SNMP walk for ENTITY MIB did not complete. You can try to increase the SNMP timeouts for the switch(es) in question or upgrade the firmware to the latest branches if in the above version ranges.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Oct 2024 12:37:45 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/wrong-port-names-in-port-tree-for-exos-switches/m-p/116533#M12401</guid>
      <dc:creator>Robert_Haynes</dc:creator>
      <dc:date>2024-10-29T12:37:45Z</dc:date>
    </item>
    <item>
      <title>Re: Wrong port names in Port Tree for EXOS switches</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/wrong-port-names-in-port-tree-for-exos-switches/m-p/116545#M12402</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Devices are running 30.7.1.1-patch1-86. I tested also 30.7.1.1-patch1-103 and&amp;nbsp;31.7.3.37-patch1-44 but with no success.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 29 Oct 2024 20:10:33 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/wrong-port-names-in-port-tree-for-exos-switches/m-p/116545#M12402</guid>
      <dc:creator>Bartek</dc:creator>
      <dc:date>2024-10-29T20:10:33Z</dc:date>
    </item>
    <item>
      <title>Re: Wrong port names in Port Tree for EXOS switches</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/wrong-port-names-in-port-tree-for-exos-switches/m-p/116750#M12432</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;When I run snmpwalk from NMS terminal I got response in less than a second so I believe the problem is with NMS:&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;snmpwalk -v 3 -On -u xiqse -l authPriv -a SHA -A '&amp;lt;AUTH_PASSWORD&amp;gt;' -x AES -X '&amp;lt;PRIV_PASSWORD&amp;gt;' -m ALL &amp;lt;SWITCH_IP&amp;gt; 1.3.6.1.2.1.31.1.1.1.1&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;.1.3.6.1.2.1.31.1.1.1.1.1000 = STRING: Management&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;.1.3.6.1.2.1.31.1.1.1.1.1001 = STRING: 1:1&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;.1.3.6.1.2.1.31.1.1.1.1.1002 = STRING: 1:2&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;.1.3.6.1.2.1.31.1.1.1.1.1003 = STRING: 1:3&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;etc.&lt;/P&gt;</description>
      <pubDate>Wed, 13 Nov 2024 11:37:13 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/wrong-port-names-in-port-tree-for-exos-switches/m-p/116750#M12432</guid>
      <dc:creator>Bartek</dc:creator>
      <dc:date>2024-11-13T11:37:13Z</dc:date>
    </item>
    <item>
      <title>Re: Wrong port names in Port Tree for EXOS switches</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/wrong-port-names-in-port-tree-for-exos-switches/m-p/116754#M12434</link>
      <description>&lt;P&gt;Try walking the ENTITY-MIB .1.3.6.1.2.1.47.&lt;/P&gt;&lt;P&gt;If you are unable to resolve this I would suggest opening a case with GTAC and a full SNMPWALK of a target switch (.1.3.6) captured to a file for review. Thank you.&lt;/P&gt;</description>
      <pubDate>Wed, 13 Nov 2024 13:52:31 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/wrong-port-names-in-port-tree-for-exos-switches/m-p/116754#M12434</guid>
      <dc:creator>Robert_Haynes</dc:creator>
      <dc:date>2024-11-13T13:52:31Z</dc:date>
    </item>
  </channel>
</rss>

