cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
182
Views
0
Helpful
1
Replies
Beginner

C4500X VFETQINTERRUPT Crash

Hi there,

 

We’ve been experiencing a series of crashes across our C4500Xs. Each time they start to alert about “VFE TQ dhmParErr interrupt wrBuffer: 0” and then crash about an hour or two later. The switches seem to start alerting randomly, some have been up for 2 months, while some over a year.  We previously opened a TAC case and were told to upgrade the switches to 3.09 in order to get access to the command “platform fw-asic buffer-used unSwitching, Catalyst 4000derrun-error reload never”. Unfortunately, we recently had another 4500 crash that had the command above applied. Looking at the bug report it seems that 3.09 is the last version mentioned. We’re now looking to upgrade to 3.11 and were wondering if anyone had experienced similar issues past 3.09.

 

Fix Command: platform fw-asic buffer-used underrun-error reload never

 

Log:

Host: XXX.XXX.XXX.XXX

         DISMAN-EVENT-MIB::sysUpTimeInstance  461:10:14:58.32

                   SNMPv2-MIB::snmpTrapOID.0  SNMPv2-SMI::enterprises.9.9.41.2.0.1

SNMPv2-SMI::enterprises.9.9.41.1.2.3.1.2.174  "C4K_SWITCHINGENGINE*"

SNMPv2-SMI::enterprises.9.9.41.1.2.3.1.3.174  5

SNMPv2-SMI::enterprises.9.9.41.1.2.3.1.4.174  "VFETQINTERRUPT"

SNMPv2-SMI::enterprises.9.9.41.1.2.3.1.5.174  "(Suppressed 15 times)VFE TQ dhmParErr interrupt wrBuffer: 0"

SNMPv2-SMI::enterprises.9.9.41.1.2.3.1.6.174  461:10:14:58.32

 

Any help would be appreciated. Thank you.

1 REPLY 1
Highlighted
Hall of Fame Community Legend

Re: C4500X VFETQINTERRUPT Crash

1. I'd stick with 3.8.X over 3.11.X (because the later is very, very "new").
2. Post the complete output to the command "dir crashinfo:".
CreatePlease to create content
Content for Community-Ad