05-21-2013 10:56 PM - edited 03-07-2019 01:29 PM
Sup720 was a minor error.
Sup720 Modules are reset, and the attempt to recover from the effects of wonder if services?
BB#1#sh module
Mod Ports Card Type Model
--- ----- -------------------------------------- ------------------ -----------
3 4 CEF720 4 port 10-Gigabit Ethernet WS-X6704-10GE
4 4 CEF720 4 port 10-Gigabit Etherne t WS-X6704-10GE
5 2 Supervisor Engine 720 (Hot) WS-SUP720-3B
6 2 Supervisor Engine 720 (Active) WS-SUP720-3B
8 24 CEF720 24 port 1000mb SFP WS-X6724-SFP
9 48 CEF720 48 port 10/100/1000mb Ethernet WS-X6748-GE-TX
Mod MAC addresses Hw Fw Sw Status
--- ---------------------------------- ------ ------------ ------------ -------
3 001c.584b.6678 to 001c.584b.667b 2.6 12.2(14r)S5 12.2(18)SXF1 Ok
4 001c.588e.bab4 to 001c.588e.bab7 2.6 12.2(14r)S5 12.2(18)SXF1 Ok
5 0016.9de6.5d1c to 0016.9de6.5d1f 5.4 8.4(2) 12.2(18)SXF1 Ok
6 001a.2f3c.7c90 to 001a.2f3c.7c93 5.4 8.4(2) 12.2(18)SXF1 Ok
8 001d.4541.c804 to 001d.4541.c81b 2.6 12.2(14r)S5 12.2(18)SXF1 Ok
9 001e.13f5.fbd0 to 001e.13f5.fbff 2.6 12.2(14r)S5 12.2(18)SXF1 Ok
Mod Sub-Module Model Serial Hw Status
---- --------------------------- ------------------ ----------- ------- -------
3 Distributed Forwarding Card WS-F6700-DFC3B SAL1150AFVD 4.6 Ok
4 Distributed Forwarding Card WS-F6700-DFC3B SAL1150A3WA 4.6 Ok
5 Policy Feature Card 3 WS-F6K-PFC3B SAL11456H9S 2.3 Ok
5 MSFC3 Daughterboard WS-SUP720 SAL114671PP 3.0 Ok
6 Policy Feature Card 3 WS-F6K-PFC3B SAL11456HCZ 2.3 Ok
6 MSFC3 Daughterboard WS-SUP720 SAL114671L0 3.0 Ok
8 Distributed Forwarding Card WS-F6700-DFC3B SAL11456G87 4.6 Ok
9 Distributed Forwarding Card WS-F6700-DFC3B SAL11456G7K 4.6 Ok
Mod Online Diag Status
---- -------------------
3 Pass
4 Pass
5 Minor Error
6 Pass
8 Pass
9 Pass
BB#1#sh diagnostic result mod 5
Current bootup diagnostic level: minimal
Module 5: Supervisor Engine 720 (Hot) SerialNo :
Overall Diagnostic Result for Module 5 : MINOR ERROR
Diagnostic level at card bootup: minimal
Test results: (. = Pass, F = Fail, U = Untested)
1) TestScratchRegister -------------> .
2) TestSPRPInbandPing --------------> .
3) TestTransceiverIntegrity:
Port 1 2
----------
U U
4) TestActiveToStandbyLoopback:
Port 1 2
----------
. .
5) TestLoopback:
Port 1 2
----------
. .
6) TestNewIndexLearn ---------------> .
7) TestDontConditionalLearn --------> .
8) TestBadBpduTrap -----------------> .
9) TestMatchCapture ----------------> .
10) TestProtocolMatchChannel --------> .
11) TestFibDevices ------------------> F
12) TestIPv4FibShortcut -------------> .
13) TestL3Capture2 ------------------> .
14) TestIPv6FibShortcut -------------> F
15) TestMPLSFibShortcut -------------> .
16) TestNATFibShortcut --------------> .
17) TestAclPermit -------------------> .
18) TestAclDeny ---------------------> .
19) TestQoSTcam ---------------------> .
20) TestL3VlanMet -------------------> .
21) TestIngressSpan -----------------> .
22) TestEgressSpan ------------------> .
23) TestNetflowInlineRewrite:
Port 1 2
----------
U U
24) TestFabricSnakeForward ----------> .
25) TestFabricSnakeBackward ---------> .
26) TestTrafficStress ---------------> U
27) TestFibTcamSSRAM ----------------> U
28) TestAsicMemory ------------------> U
29) TestAclQosTcam ------------------> U
30) TestNetflowTcam -----------------> U
31) ScheduleSwitchover --------------> U
32) TestFirmwareDiagStatus ----------> .
33) TestFabricFlowControlStatus -----> U
Solved! Go to Solution.
05-22-2013 12:52 AM
It should not as you have redundant sup module.
SSO—Status shows Hot.
Hot redundancy refers to a degree of resiliency where the redundant system is fully prepared to handle the traffic of the primary system. Substantial state information is saved, so the network service is continuous, and the effect on traffic flow is minimal or nil in the case of a failover.
Regards
Inayath
05-21-2013 11:02 PM
Re-seat the card. If problem persist, move the card to a different chassis (since slot 6 is already occupied). If problem persist, RMA the supervisor card.
05-21-2013 11:56 PM
Sorry I apologies.
Here is what was suggested:
1- Kindly do the hard reset of the module which is Module 5.
2- If the reset module doesnt resolve the issue go ahead and raise an RMA for the this module.
Regards
Inayath
05-22-2013 12:06 AM
Module 5 reset after service downtime occur?
05-22-2013 12:52 AM
It should not as you have redundant sup module.
SSO—Status shows Hot.
Hot redundancy refers to a degree of resiliency where the redundant system is fully prepared to handle the traffic of the primary system. Substantial state information is saved, so the network service is continuous, and the effect on traffic flow is minimal or nil in the case of a failover.
Regards
Inayath
05-22-2013 01:04 AM
Thank you
09-06-2015 03:42 AM
Hi,
I am also facing this issue as i am using only one SUP engine on my 6509.
Should i do the jack in and jack out or reload of the switch will work?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide