12-24-2013 06:22 AM - edited 03-07-2019 05:13 PM
Hello,
We have two cisco 6509E switches which are configured in VSS mode. The status of one of the two supervisor engines (
Supervisor Engine 2T) is Major failure as follow:
B1CS05A#sh mod
Mod Ports Card Type Model Serial No.
--- ----- -------------------------------------- ------------------ -----------
1 48 CEF720 48 port 10/100/1000mb Ethernet WS-X6848-GE-TX SAL1644RGZC
2 8 DCEF2T 8 port 10GE WS-X6908-10G SAL1643QYRY
3 4 CEF720 4 port 10-Gigabit Ethernet WS-X6704-10GE SAL1518CXL4
5 5 Supervisor Engine 2T 10GE w/ CTS (Acti VS-SUP2T-10G SAL1643R24T
Mod MAC addresses Hw Fw Sw Status
--- ---------------------------------- ------ ------------ ------------ -------
1 6c20.56c3.2640 to 6c20.56c3.266f 1.0 12.2(18r)S1 15.0(1)SY2 Ok
2 001f.6ca4.a1f0 to 001f.6ca4.a1f7 1.2 12.2(50r)SYL 15.0(1)SY2 Ok
3 c471.febe.7d74 to c471.febe.7d77 3.2 12.2(14r)S5 15.0(1)SY2 Ok
5 e05f.b911.5acd to e05f.b911.5ad4 1.3 12.2(50r)SYS 15.0(1)SY2 MajFail
Mod Sub-Module Model Serial Hw Status
---- --------------------------- ------------------ ----------- ------- -------
1 Distributed Forwarding Card WS-F6K-DFC4-A SAL1644R94K 1.2 Ok
2 Distributed Forwarding Card WS-F6K-DFC4-E SAL1638MZ88 1.2 Ok
3 Centralized Forwarding Card WS-F6700-CFC SAL1518D0W3 4.1 Ok
5 Policy Feature Card 4 VS-F6K-PFC4 SAL1642PYZK 1.2 MajFail
5 CPU Daughterboard VS-F6K-MSFC5 SAL1643R1SK 1.4 MajFail
Mod Online Diag Status
---- -------------------
1 Pass
2 Pass
3 Pass
5 Major Error
When I reset the module, the status converted to "Minor Error"!!
Switch Number: 1 Role: Virtual Switch Active
---------------------- -----------------------------
Mod Ports Card Type Model Serial No.
--- ----- -------------------------------------- ------------------ -----------
1 48 CEF720 48 port 10/100/1000mb Ethernet WS-X6848-GE-TX SAL1644RGZC
2 8 DCEF2T 8 port 10GE WS-X6908-10G SAL1643QYRY
3 4 CEF720 4 port 10-Gigabit Ethernet WS-X6704-10GE SAL1518CXL4
5 5 Supervisor Engine 2T 10GE w/ CTS (Acti VS-SUP2T-10G SAL1643R24T
Mod MAC addresses Hw Fw Sw Status
--- ---------------------------------- ------ ------------ ------------ -------
1 6c20.56c3.2640 to 6c20.56c3.266f 1.0 12.2(18r)S1 15.0(1)SY2 Ok
2 001f.6ca4.a1f0 to 001f.6ca4.a1f7 1.2 12.2(50r)SYL 15.0(1)SY2 Ok
3 c471.febe.7d74 to c471.febe.7d77 3.2 12.2(14r)S5 15.0(1)SY2 Ok
5 e05f.b911.5acd to e05f.b911.5ad4 1.3 12.2(50r)SYS 15.0(1)SY2 Ok
Mod Sub-Module Model Serial Hw Status
---- --------------------------- ------------------ ----------- ------- -------
1 Distributed Forwarding Card WS-F6K-DFC4-A SAL1644R94K 1.2 Ok
2 Distributed Forwarding Card WS-F6K-DFC4-E SAL1638MZ88 1.2 Ok
3 Centralized Forwarding Card WS-F6700-CFC SAL1518D0W3 4.1 Ok
5 Policy Feature Card 4 VS-F6K-PFC4 SAL1642PYZK 1.2 Ok
5 CPU Daughterboard VS-F6K-MSFC5 SAL1643R1SK 1.4 Ok
Mod Online Diag Status
---- -------------------
1 Pass
2 Pass
3 Pass
5 Minor Error
Attached is Show diaganostic and show enviroment for the switch. What should I do to solve that issue?
12-24-2013 07:41 AM
Your best bet is to open a TAC case. They've seen errors like this whereas most of us have not.
Sent from Cisco Technical Support Android App
12-24-2013 10:20 AM
You will probably have to get that Sup replaced.
12-24-2013 04:24 PM
Hi,
Before going straight up for the RMA you may want to configure the following:
conf t
diagnostic bootup level complete
exit
Then reseat the supervisor by pulling it out and then back in into the chassis, once it runs the complete diagnostics and comes back up, check to see if the minor error still there in show module output, check the logs for any errors. finally do the show diagnostics result module 5 to see what test was the one that failed. It may be due to a parity error that can be recover with a hard reset, and as a last option go for the replacement.
Hope this helps.
12-25-2013 12:02 AM
Thanks for the reply.
But the diagnostic command "diagnostic bootup level complete" is not matching list of commands allowed on the switch as shown below:
#diagnostic ?
mode Configure Online Diagnostic Mode Information
ondemand On demand diagnostic setting
start Starting on demand diagnostic
stop Stopping diagnostic
what should I do?
Thanks
12-24-2013 07:12 PM
Hi,
You should try hard reseat of the sup card if still shows the same behaviour repalce the SUP.
02-19-2020 05:21 AM
just remplace battery
your error is:
53) TestNVRAMBatteryMonitor ---------> F
Error code ------------------> 322 (DIAG_LOW_NVRAM_BATTERY_POWER_ERROR)
Total run count -------------> 65
Last test testing type ------> Health Monitoring
Last test execution time ----> Dec 22 2013 08:48:17
First test failure time -----> Dec 19 2013 16:48:08
Last test failure time ------> Dec 22 2013 08:48:17
02-19-2020 06:23 AM
- So that supervisor is likely to loose it's configuration upon power failure; best to have it replaced as others have stated.
M.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: