Wrong port names in Port Tree for EXOS switches

[Bartek]

Hi,

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".

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:

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
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

Do you have some ideas how to fix it? Now I'm seriously considering NMS reinstallation

[Robert_Haynes]

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.

[Bartek]

Hi,

When I run snmpwalk from NMS terminal I got response in less than a second so I believe the problem is with NMS:

snmpwalk -v 3 -On -u xiqse -l authPriv -a SHA -A '<AUTH_PASSWORD>' -x AES -X '<PRIV_PASSWORD>' -m ALL <SWITCH_IP> 1.3.6.1.2.1.31.1.1.1.1
.1.3.6.1.2.1.31.1.1.1.1.1000 = STRING: Management
.1.3.6.1.2.1.31.1.1.1.1.1001 = STRING: 1:1
.1.3.6.1.2.1.31.1.1.1.1.1002 = STRING: 1:2
.1.3.6.1.2.1.31.1.1.1.1.1003 = STRING: 1:3

etc.

[Robert_Haynes]

Try walking the ENTITY-MIB .1.3.6.1.2.1.47.

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.

[Bartek]

Hi,

Devices are running 30.7.1.1-patch1-86. I tested also 30.7.1.1-patch1-103 and 31.7.3.37-patch1-44 but with no success.