topic RE: Possible Bug when changing sysName through NMS in ExtremeCloud IQ- Site Engine Management Center

Possible Bug when changing sysName through NMS

davidj_cogliane — Fri, 17 Mar 2017 21:38:00 GMT

I recently found that when changing the sysName through Netsight it configures the old sysName as a display string on all ports that did not previously have a display string configured.

X460G2-48p-10G4 running 15.7.3.1-patch1-6.xos
NMS 7.0.6.27

RE: Possible Bug when changing sysName through NMS

davidj_cogliane — Fri, 17 Mar 2017 22:10:00 GMT

Found another related oddity....

RE: Possible Bug when changing sysName through NMS

Ronald_Dvorak — Fri, 17 Mar 2017 22:16:00 GMT

You've changed the port description-string and not the port display-string.

If you do a "show port description" you'd see that this are two different things - don't ask me why I also don't get it.

RE: Possible Bug when changing sysName through NMS

Patrick_Koppen — Fri, 17 Mar 2017 22:16:00 GMT

display-string is used with show port, show vlan, ... and is a short string.

description is the long version. You can see both with show port description
or show port X info detail.

One of them is exported via snmp.... that's the part where it get's ugly;)

RE: Possible Bug when changing sysName through NMS

Patrick_Koppen — Fri, 17 Mar 2017 22:30:00 GMT

Have the same here, but not with all devices. Testet with x460 (16.2) and x460-G2 (22.1):

old names: p1sw1 and p1sw2
new names: p1sw1XX and p1sw2XX

The good news: only ports without display-string or description are affected.

But: on sw2 the port-descr change to p2sw2_... (without XX), on sw1 nothing happend.
Maybe ports are only changed on switches that are ZTP+ ready. I noticed this behavior
when I tested ZTP+. But it's just fishing in the dark;)

* p1sw1XX.37 # show ports description
Port Display String Description String
===== ==================== ==================
1 test
2 test
3 tttt ttttx
4
5
* p1sw2XX.33 # show ports description
Port Display String Description String
===== ==================== ==================
1 test
2 test
3 tttt ttttx
4 p1sw2_1:4 p1sw2_1:4
5 p1sw2_1:5 p1sw2_1:5
20 p1sw2_1:20 p1sw2_1:20
I deleted port 20 and change the name again to YY:
* p1sw2YY.34 # show ports description
20 p1sw2_1:20 p1sw2_1:20Again the original name....

Then I looked at the Java-Console:
System Name: p1sw1YY and p1sw2YY
Nickname: p1sw1XX and p1sw2XX

So if you change the name the first time, it sets the nickname. If you change
it again, you have to open 'Device Annotation' and change it there too.

So maybe there's a third name somewhere....

EMC Version 7.1.1.9

edit: text formatting (3x)

RE: Possible Bug when changing sysName through NMS

davidj_cogliane — Fri, 17 Mar 2017 23:13:00 GMT

Ok,

Display-string and description-string just seems silly, why would we need to give a port 2 names?

But that discussion aside, why does changing the device name change either port string?? Still seems like a bug to me.

Thanks for the information,

RE: Possible Bug when changing sysName through NMS

Dorian_Perry — Mon, 20 Mar 2017 22:12:00 GMT

Hi,

How is the sysname being edited from the NMS side?

RE: Possible Bug when changing sysName through NMS

Bob_Maheu — Thu, 23 Mar 2017 23:54:00 GMT

Hi All,

Please upgrade to version 7.1.1.9 of Extreme Management. I was able to replicate this in 7.0.9.4, but not in 7.1.1.9.

RE: Possible Bug when changing sysName through NMS

Patrick_Koppen — Thu, 23 Mar 2017 23:54:00 GMT

Hi Bob,

I used 7.1.1.9 in the tests above...

RE: Possible Bug when changing sysName through NMS

davidj_cogliane — Thu, 23 Mar 2017 23:54:00 GMT

Thanks for the follow up.