6500 VSS shows the following error message vs_get_pslot_switch_id():vslot error..! vslot=0xFFFF

[ReinaldoRB]

Hello, we recently had an incident on our 6500VSS in which both units separated, we assume, and caused most interfaces to flap. 

Just before the incident we got the following messages:

Jan 15 20:37:56: %VSDA-SW1_SP-3-LINK_DOWN: Interface Gi1/2/48 is no longer dual-active detection capable

Jan 15 20:38:03: %PFREDUN-SW1_SP-7-KPA_WARN: RF KPA messages have not been heard for 27 seconds

Jan 15 20:37:50: %VSDA-SW2_SPSTBY-3-LINK_DOWN: Interface Gi2/2/48 is no longer dual-active detection capable

Jan 15 20:37:51: %VSDA-SW2_SPSTBY-5-LINK_UP: Interface Gi2/2/48 is now dual-active detection capable

Just after recovering shows these logs:

Jan 16 00:13:27: SW2_SPSTBY: vs_get_pslot_switch_id():vslot error..! vslot=0xFFFF

Jan 16 00:13:27: SW2_SPSTBY: -Traceback= 40E9C684 4125C8A0 411B83F8 40FD87D4 40FDDE94 40FDB714 419EFABC

Jan 16 00:13:27: SW2_SPSTBY: vs_get_pslot_switch_id():vslot error..! vslot=0xFFFF

Jan 16 00:13:27: SW2_SPSTBY: -Traceback= 40E9C684 41184BAC 4116A83C 4117331C 40FD8A70 40FDDE94 40FDB714 419EFABC

Jan 16 00:13:28: SW2_SPSTBY: vs_get_pslot_switch_id():vslot error..! vslot=0xFFFF

Jan 16 00:13:28: SW2_SPSTBY: -Traceback= 40E9C684 4125C8A0 411B83F8 40FD87D4 40FDDE94 40FDB714 419EFABC

Jan 16 00:13:28: SW2_SPSTBY: vs_get_pslot_switch_id():vslot error..! vslot=0xFFFF

Jan 16 00:13:28: SW2_SPSTBY: -Traceback= 40E9C684 41184BAC 4116A83C 4117331C 40FD8A70 40FDDE94 40FDB714 419EFABC

Jan 16 00:13:30: SW2_SPSTBY: vs_get_pslot_switch_id():vslot error..! vslot=0xFFFF

Jan 16 00:13:30: SW2_SPSTBY: -Traceback= 40E9C684 4125C8A0 411B83F8 40FD87D4 40FDDE94 40FDB714 419EFABC

Jan 16 00:13:30: SW2_SPSTBY: vs_get_pslot_switch_id():vslot error..! vslot=0xFFFF

Jan 16 00:13:30: SW2_SPSTBY: -Traceback= 40E9C684 41184BAC 4116A83C 4117331C 40FD8A70 40FDDE94 40FDB714 419EFABC

Jan 16 00:13:32: SW2_SPSTBY: vs_get_pslot_switch_id():vslot error..! vslot=0xFFFF

Jan 16 00:13:32: SW2_SPSTBY: -Traceback= 40E9C684 4125C8A0 411B83F8 40FD87D4 40FDDE94 40FDB714 419EFABC

Jan 16 00:13:32: SW2_SPSTBY: vs_get_pslot_switch_id():vslot error..! vslot=0xFFFF

Jan 16 00:13:32: SW2_SPSTBY: -Traceback= 40E9C684 41184BAC 4116A83C 4117331C 40FD8A70 40FDDE94 40FDB714 419EFABC

Can this be interpreted some way? 

I hope someone can help, as we are trying to apply appropriate correction measures and we are still not sure what could be the root cause of this.

Thanks

[Leo Laohoo]

Could be a bug so think about upgrading the IOS.
I noticed that the heartbeat sits on a non-supervisor card line card. So it could be a faulty SFP or the port in the line card is faulty or the cable.

[ReinaldoRB]

Hello, thanks for your feedback. How can I check if supervisor cable is faulty?

[balaji.bandi]

@Leo Laohoo  as mentioned this could be any issue.

can you post what your hardware supervisors and running code, how many supervisiors you have.

[ReinaldoRB]

I attach redundancy information. Thanks

[Mark Malone]

Looks like a bug , tracebacks are never a good sign
Jan 16 00:13:27: SW2_SPSTBY: -Traceback= 40E9C684 4125C8A0 411B83F8 40FD87D4 40FDDE94 40FDB714 419EFABC

The sups stayed up looking at the redundancy

have you ran the show tech yet through the cli analyzer tool (available Cisco website tool section) to see if it gave a bug id ?