Hey everyone,
I'm seeing some odd behavior on a handful of my switch stacks. This behavior has only occurred on stacks where a failed node has been replaced. Stacks that have never had a failed node do not display this behavior. That may totally be a red herring, but I wanted to point it out.
The behavior we are seeing is that all ports that did not previously have a display-string configured are now configured with a simple (and useless) name of "switchSNMPname_portnumber". We only have two network engineers with access to our CLI, and neither of us would have (intentionally) done something quite this dumb.
For example, here is the expected output from a good configuration:
Slot-1 MDF.1 # sh vlan eng
Ports: 117. (Number of active ports=88)
Untag: *1:1, *1:2, *1:3, *1:9, *1:10, *1:11, *1:12,
*1:17, *1:18, *1:19, *1:20, *1:26, *1:28, *1:33,
*1:34, *1:35, *1:36, *1:41, *1:42, 1:43, *1:44,
*1:47, *2:10, *2:12, 2:13, 2:15, 2:16, *2:17,
*2:18, *2:20, *2:21, *2:23, *2:26, 2:28, 2:29,
And here is the output from a stack showing the behavior in question:
Slot-1 IDF01.2 # sh vlan eng
Ports: 20. (Number of active ports=7)
Untag: *1:5(IDF01_1:5),1:6(IDF01_1:6),*1:9(IDF01_1:9),*1:10(IDF01_1:10),*1:13(IDF01_1:13),1:14(IDF01_1:14),1:20(IDF01_1:20),
1:21(IDF01_1:21),1:22(IDF01_1:22),1:30(IDF01_1:30),2:21(IDF01_2:21),2:22(IDF01_2:22),4:14(IDF01_4:14),4:28(IDF01_4:28),
4:29(IDF01_4:29),*4:30(IDF01_4:30),6:5(IDF01_6:5),*6:37(IDF01_6:37)
Tag: *1:53bg, *6:53g
As you can see, this makes it super annoying to look at things in the CLI, and we have no idea why it happened. I can go through and manually unconfigure the display strings (and have been) but we are just generally curious what caused this in the first place.
Thanks for any insight!
