[c-nsp] Parity Error -

[Paul Stewart]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

We had an incident this morning on one of our 6509's....

Apr 20 08:13:11: %PM_SCP-SP-6-LCP_FW_ERR_INFORM: Module 3 is
experiencing the following error: Pinnacle #0 PB parity error. Tx path.
Status=0x0042
Apr 20 08:13:53: %PM_SCP-SP-6-LCP_FW_ERR_INFORM: Module 3 is
experiencing the following error: Pinnacle #0 PB parity error. Tx path.
Status=0x0046
Apr 20 08:14:35: %PM_SCP-SP-6-LCP_FW_ERR_INFORM: Module 3 is
experiencing the following error: Pinnacle #0 PB parity error. Tx path.
Status=0x0042
Apr 20 08:15:17: %PM_SCP-SP-6-LCP_FW_ERR_INFORM: Module 3 is
experiencing the following error: Pinnacle #0 PB parity error. Tx path.
Status=0x0046
Apr 20 08:15:59: %PM_SCP-SP-6-LCP_FW_ERR_INFORM: Module 3 is
experiencing the following error: Pinnacle #0 PB parity error. Tx path.
Status=0x0046
Apr 20 08:16:41: %PM_SCP-SP-6-LCP_FW_ERR_INFORM: Module 3 is
experiencing the following error: Pinnacle #0 PB parity error. Tx path.
Status=0x0042
Apr 20 08:17:23: %PM_SCP-SP-6-LCP_FW_ERR_INFORM: Module 3 is
experiencing the following error: Pinnacle #0 PB parity error. Tx path.
Status=0x0046
Apr 20 08:18:05: %PM_SCP-SP-6-LCP_FW_ERR_INFORM: Module 3 is
experiencing the following error: Pinnacle #0 PB parity error. Tx path.
Status=0x0042

gw-6509-1#sh module
Mod Ports Card Type                              Model
Serial No.
- --- ----- -------------------------------------- ------------------
- -----------
~  1    2  Catalyst 6000 supervisor 2 (Active)    WS-X6K-SUP2-2GE
SAL062722LG
~  2    2  Catalyst 6000 supervisor 2 (Warm)      WS-X6K-SUP2-2GE
SAL062722J7
~  3   16  16 port GE RJ45                        WS-X6316-GE-TX
SAD070202D5
~  4   48  48 port 10/100 mb RJ-45 ethernet       WS-X6248-RJ-45
SAD041707G4
~  5   48  48 port 10/100 mb RJ-45 ethernet       WS-X6248-RJ-45
SAD042905Y1
~  6   48  48 port 10/100/1000mb EtherModule      WS-X6148-GE-TX
SAD082001GB

We've never had any issues with 6316's before.... the IOS was upgraded
last week so wondering if the upgrade is the issue or if it's actually a
hardware failure starting....

IOS: System image file is "slot0:c6k222-pk9sv-mz.122-18.SXD4.bin"

If anyone has any ideas, I'd love to hear them... we've had ZERO
problems with 6509's til this morning...

Thanks,

Paul Stewart
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)

iD8DBQFCZktBqMetgU57IuQRAtxTAJ9pSyogXzn/RRhsIzAwhUP5xGlWgACcCTHH
80oDQ2P7Tb5vS2ylJtaMCmI=
=5kn4
-----END PGP SIGNATURE-----