ā07-31-2013 10:44 PM - edited ā03-07-2019 02:42 PM
Hi Guys,
I have received the following error on one of our Core switches.
%PM_SCP-2-LCP_FW_ERR_INFORM: module 1 is experiencing the following error: Port ASIC (VISHAKHA) packet buffer failure detected on ports 45
%PM-4-ERR_DISABLE: packet-buffer error detected on Gi1/45, putting Gi1/45 in err-disable state
The port Gi1/45 is connected to a server and now it is in err-diabled mode.
I have tried to shut and unshut the port but received the following errors -
%CONST_DIAG-3-HM_PORT_TEST_FAIL: Module 1 TestNonDisruptiveLoopback Port(s)[45] failed. System operation continues.
%HA_EM-6-LOG: Mandatory.go_nondislp.tcl: GOLD EEM TCL policy for TestNonDisruptiveLoopback
%PM-4-ERR_DISABLE: diagnostics error detected on Gi1/45, putting Gi1/45 in err-disable state
I have checked the port and could not find any errors or drops -
DBACoreR01#sh interfaces gigabitEthernet 1/45
GigabitEthernet1/45 is down, line protocol is down (err-disabled)
Hardware is C6k 1000Mb 802.3, address is 001a.2f60.447c (bia 001a.2f60.447c)
Description:
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
reliability 255/255, txload 0/255, rxload 0/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, Auto-speed, media type is 10/100/1000BaseT
input flow-control is off, output flow-control is off
Clock mode is auto
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
110065 packets input, 13673797 bytes, 0 no buffer
Received 16 broadcasts (12 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 3 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 input packets with dribble condition detected
170240392 packets output, 15793183649 bytes, 0 underruns
0 output errors, 0 collisions, 4 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 PAUSE output
0 output buffer failures, 0 output buffers swapped out
I have also checked the module and found a failure on port Gi 1/45
Core01#show diagnostic result module 1
Current bootup diagnostic level: minimal
Module 1: 48-port 10/100/1000 RJ45 EtherModule SerialNo : SAL10489C30
Overall Diagnostic Result for Module 1 : MINOR ERROR
Diagnostic level at card bootup: minimal
Test results: (. = Pass, F = Fail, U = Untested)
1) TestScratchRegister -------------> .
2) TestNonDisruptiveLoopback:
Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
----------------------------------------------------------------------------
. . . . . . . . . . . . . . . . . . . . . . . .
Port 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
----------------------------------------------------------------------------
. . . . . . . . . . . . . . . . . . . . F . . .
3) TestLoopback:
Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
----------------------------------------------------------------------------
. . . . . . . . . . . . . . . . . . . . . . . .
Port 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
----------------------------------------------------------------------------
. . . . . . . . . . . . . . . . . . . . . . . .
4) TestNetflowInlineRewrite:
Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
----------------------------------------------------------------------------
U U U U U U U U U U U U U U U U U U U U U U U U
Port 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
----------------------------------------------------------------------------
U U U U U U U U U U U U U U U U U U U U U U U U
5) TestAsicMemory ------------------> U
6) TestEobcStressPing --------------> U
7) TestFirmwareDiagStatus ----------> .
8) TestAsicSync --------------------> .
9) TestErrorCounterMonitor ---------> .
10) TestLtlFpoeMemoryConsistency ----> .
CoreR01#show module
Mod Ports Card Type Model Serial No.
--- ----- -------------------------------------- ------------------ -----------
1 48 48-port 10/100/1000 RJ45 EtherModule WS-X6148A-GE-TX SAL10689C30
3 48 48-port 10/100/1000 RJ45 EtherModule WS-X6148A-GE-TX SAL10889C3X
5 5 Supervisor Engine 2T 10GE w/ CTS (Acti VS-SUP2T-10G SAL1550Y4ZV
8 20 DCEF2T 4 port 40GE / 16 port 10GE WS-X6904-40G SAL1669C5GD
Mod MAC addresses Hw Fw Sw Status
--- ---------------------------------- ------ ------------ ------------ -------
1 001a.2f60.4450 to 001a.2f60.447f 1.5 8.4(1) 15.0(1)SY3 Ok
3 001a.2f6f.71f0 to 001a.2f6f.721f 1.5 8.4(1) 15.0(1)SY3 Ok
5 e05f.b911.0a3b to e05f.b911.0a42 1.3 12.2(50r)SYS 15.0(1)SY3 Ok
8 1cdf.0f9b.c05a to 1cdf.0f9b.c06d 1.0 12.2(50r)SYL 15.0(1)SY3 Ok
Mod Sub-Module Model Serial Hw Status
---- --------------------------- ------------------ ----------- ------- -------
5 Policy Feature Card 4 VS-F6K-PFC4 SAL1649TUFQ 1.2 Ok
5 CPU Daughterboard VS-F6K-MSFC5 SAL1646SJJ8 1.4 Ok
8 Distributed Forwarding Card WS-F6K-DFC4-E SAL1648T7QP 1.2 Ok
Mod Online Diag Status
---- -------------------
1 Minor Error
3 Pass
5 Pass
8 Pass
Could anyone please let me know what might be wrong here. is it a hardware faliure? Do I need to raise this with TAC?
Really appreciate your help.
Thank you,
Jay
Solved! Go to Solution.
ā08-01-2013 12:02 AM
No it is HW issue, though transient. Parity causes meory lockup on ASIC. On new cards this issue is fixed in manufacturing.
DDTS is only for informational purposes, there is no code fix.
Kind Regards,
Ivan Shirshin
**Please grade this post if you find it useful.
ā07-31-2013 11:07 PM
Hi,
This could be a result of a single parity (data corruption) in the SRAM on the ASIC, which is described in
CSCsw43503 WS-X6148A-GE-TX One port will go err-disable due to VISHAKHA error
It is recommended to reseat the card and i most cases the error won't reoccur after that.
Kind Regards,
Ivan Shirshin
**Please grade this post if you find it useful.
ā07-31-2013 11:56 PM
Hi Ivan.
Thank you for the reply.
So is it a bug on the line card?
Thanks,
Jay
ā08-01-2013 12:02 AM
No it is HW issue, though transient. Parity causes meory lockup on ASIC. On new cards this issue is fixed in manufacturing.
DDTS is only for informational purposes, there is no code fix.
Kind Regards,
Ivan Shirshin
**Please grade this post if you find it useful.
ā08-06-2013 12:03 AM
Hi Ivan,
Sorry for the late reply.
I will let you know if the restart of the line card has fixed the issue.
Appreciate your help.
Thanks
Jay
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: