Cisco 4958 reloaded

[sb.saravanakumar]

Guys,

  I am facing problem with Cisco 4948 switch and got reloaded 2 times automatically. We are not facing  any issue before & after reloading. Please see below error:

4d12h: %C4K_SWITCHINGENGINEMAN-4-FATALERRORINTERRUPTSEEN:

4d12h: %C4K_HWPORTMAN-4-BLOCKEDTXQUEUE: Blocked transmit queue HwTxQId1 on Switch Phyport Gi1/41, count=231

4d12h: %C4K_HWPORTMAN-4-BLOCKEDTXQUEUE: Blocked transmit queue HwTxQId1 on Switch Phyport Gi1/33, count=231

4d12h: %C4K_HWPORTMAN-4-BLOCKEDTXQUEUE: Blocked transmit queue HwTxQId3 on Switch Phyport Gi1/36, count=231

4d12h: %C4K_HWPORTMAN-4-BLOCKEDTXQUEUE: Blocked transmit queue HwTxQId1 on Switch Phyport Gi1/29, count=231

4d12h: %C4K_HWPORTMAN-4-BLOCKEDTXQUEUE: Blocked transmit queue HwTxQId3 on Switch Phyport Gi1/32, count=231

4d12h: %C4K_HWPORTMAN-4-BLOCKEDTXQUEUE: Blocked transmit queue HwTxQId1 on Switch Phyport Gi1/31, count=231

4d12h: %C4K_HWPORTMAN-4-BLOCKEDTXQUEUE: Blocked transmit queue HwTxQId3 on Switch Phyport Gi1/26, count=231

4d12h: %C4K_HWPORTMAN-4-BLOCKEDTXQUEUE: Blocked transmit queue HwTxQId3 on Switch Phyport Gi1/25, count=231

4d12h: %C4K_HWPORTMAN-4-BLOCKEDTXQUEUE: Blocked transmit queue HwTxQId1 on Switch Phyport Gi1/28, count=231

4d12h: %C4K_HWPORTMAN-4-BLOCKEDTXQUEUE: Blocked transmit queue HwTxQId3 on Switch Phyport Gi1/28, count=231

4d12h: %C4K_HWPORTMAN-4-BLOCKEDTXQUEUE: Blocked transmit queue HwTxQId3 on Switch Phyport Gi1/21, count=231

4d12h: %C4K_HWPORTMAN-4-BLOCKEDTXQUEUE: Blocked transmit queue HwTxQId1 on Switch Phyport Gi1/17, count=231

4d12h: %C4K_HWPORTMAN-4-BLOCKEDTXQUEUE: Blocked transmit queue HwTxQId1 on Switch Phyport Gi1/14, count=231

4d12h: %C4K_HWPORTMAN-4-BLOCKEDTXQUEUE: Blocked transmit queue HwTxQId3 on Switch Phyport Gi1/13, count=231

Jun 13 10:17:33 hbdlinsw15k 1299: 4d12h: Current Freelist count 7879. Fell below threshold 1 times consecutively

Jun 13 10:18:03 hbdlinsw15k 1300: 4d12h: Current Freelist count 7286. Fell below threshold 602 times consecutively

Jun 13 10:18:33 hbdlinsw15k 1301: 4d12h: Current Freelist count 6693. Fell below threshold 1 times consecutively

Jun 13 10:19:03 hbdlinsw15k 1302: 4d12h: Current Freelist count 6102. Fell below threshold 602 times consecutively

Jun 13 10:19:33 hbdlinsw15k 1303: 4d12h: Current Freelist count 5509. Fell below threshold 1 times consecutively

Jun 13 10:20:03 hbdlinsw15k 1304: 4d12h: Current Freelist count 4918. Fell below threshold 602 times consecutively

Jun 13 10:20:33 hbdlinsw15k 1305: 4d12h: Current Freelist count 4325. Fell below threshold 1 times consecutively

Jun 13 10:21:03 hbdlinsw15k 1306: 4d12h: Current Freelist count 3734. Fell below threshold 602 times consecutively

Jun 13 10:21:33 hbdlinsw15k 1307: 4d12h: Current Freelist count 3141. Fell below threshold 1 times consecutively

Jun 13 10:22:03 hbdlinsw15k 1308: 4d12h: Current Freelist count 2550. Fell below threshold 602 times consecutively

Jun 13 10:22:33 hbdlinsw15k 1309: 4d12h: Current Freelist count 1957. Fell below threshold 1 times consecutively

Please help to resolve the issue.

Thanks in Advance

--Saravana

[Ivan Shirshin]

Hi,

Could you ccheck for crashinfo files in the bootflash and upload those?

     show bootflash:

Kind Regards,
Ivan

[smitesh kharecha]

Hi Saravana,

Please check below link, which outline common errors on CatOS:

http://www.cisco.com/en/US/products/hw/switches/ps663/products_tech_note09186a00801434de.shtml

HTH,

Smitesh

PS: Please rate helpful posts...

[Ivan Shirshin]

Hi,

This switch is running IOS 12.2(31)SGA9, not CATOS.

Kind Regards,
Ivan

[sb.saravanakumar]

Hi Ivan,

   Yes.. Switch is running with Version 12.2(31)SGA9, RELEASE SOFTWARE (fc1)

Thanks,

Saravana

[Ivan Shirshin]

Hi,

The decode shows K2FatalErrorInterruptMan interrupt in  the crash stack, which along with vector failure indicate the root  cause of SDRAM parity errors. Note that system tries to recover parity  errors and crashes only after 10 consequitive failures.

This  is hardware issue related to memory and that has to be replaced. The  reason for the memory failure could be the mem chip malfunction but also  there is a possibility of the following degradation described in the  following FN:

http://cco/en/US/ts/fn/620/fn62488.html

Check the SNs to see if that FN is affecting your switch.

====================

Only  WS-C4948-10GE fixed configuration switches with the Serial numbers  below and Hardware Revision numbers are vulnerable. Please follow the  following steps to identify if your switches are affected:

STEP 1) Check the WS-C4948-10GE Serial Number:

a) Lower than and equal to JAx1008xxxx

b) JAx1014xxxx to JAx1022xxxx

c) JAx1025xxxx

d) JAx1039xxxx

(where x at any location in the Serial Number can represent any letter or number)

STEP 2) If the Serial Number does not match the values above, then the WS-C4948-10GE is not affected. If the

Serial Number does match, please go to STEP 3.

STEP 3) Check the WS-C4948-10GE to see if it has a vulnerable Hardware Revision number:

a) 1.0, 1.1, 1.2

b) 2.0, 2.1, 2.2, 2.3

c) 3.0, 3.1, 3.2

STEP  4) If both the Serial Number and Hardware Revision number match the  values above, please use the standard RMA process to order replacement  parts. After receiving the replacement switch please return affected  unit to Cisco.

Units that do not meet both the Serial number and Hardware Revision detailed above are not vulnerable.

====================

Kind Regards,

Ivan

**Please grade this post if you find it useful.

[sb.saravanakumar]

Hi Ivan,

  Thanks for the detailed explanation. My device serial number is not faaling under affected series

Please see below serial number

SN: FOX1150G5RS

Thanks for identifying the issue.

Thanks,

Saravana

[Ivan Shirshin]

Welcome, Saravana.