Solved: Need to understand LOG information for Cisco 15540

rlortiz · ‎01-07-2009

Anyone have an idea what could have caused the below log errors?:

Dec 31 06:06:04: %CPU_REDUN-5-PEER_EXITED_IOS: Peer CPU has exited IOS

Dec 31 06:06:04: %CPU_REDUN-5-STATUS_CHG: ACTIVE (sev 0), peer is NON-PARTICIPAN

T (sev 0)

Dec 31 06:06:04: %CPU_REDUN-5-STATUS_CHG: ACTIVE (sev 0), peer is NON-PARTICIPAN

T (sev 2)

Dec 31 06:06:04: %RF-3-COMMUNICATION: Communication with the peer CPU has been l

ost

Dec 31 06:06:04: %CPU_REDUN-3-PEER_COMM: Alarm: ASSERT, MINOR, CPU slot 6, Unpro

tected. Peer not responding,

Dec 31 06:06:04: %COUNTER_SYNC-3-TRANSMIT_ERROR: Unable to transmit message type

1 from Transparent10/2/0 action 1

Dec 31 06:06:04: %COUNTER_SYNC-3-STATUS: Performance stat sync failed on Trans

parent10/2/0

Dec 31 06:06:04: %COUNTER_SYNC-3-NO_BUFFER: No Memory to sync perf stats for Wav

e10/0

Dec 31 06:06:06: %LINK-3-UPDOWN: Interface Fastethernet-sby0, changed state to d

own

Dec 31 06:06:06: %LINK-3-UPDOWN: Interface Controller-peer0, changed state to do

wn

Dec 31 06:06:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface Fastethernet-sb

y0, changed state to down

Dec 31 06:06:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface Controller-peer

0, changed state to down

Dec 31 06:06:32: %RF-3-COMMUNICATION: Communication with the peer CPU has been e

stablished

Dec 31 06:06:33: %CPU_REDUN-3-PEER_COMM: Alarm: CLEAR, MINOR, CPU slot 6, Unprot

ected. Peer not responding,

Dec 31 06:06:34: %LINK-3-UPDOWN: Interface Controller-peer0, changed state to up

Dec 31 06:06:35: %LINEPROTO-5-UPDOWN: Line protocol on Interface Controller-peer

0, changed state to up

Dec 31 06:06:37: %CPU_REDUN-5-STARTUP_CONFIG_SYNCED: Startup config successfully

synced to standby

Dec 31 06:06:38: %CPU_REDUN-5-BASIC_CAPABILITY: Peer CPU hardware and software i

s fully compatible.

Dec 31 06:06:39: %CPU_REDUN-5-STATUS_CHG: ACTIVE (sev 0), peer is STANDBY (sev 2

)

Dec 31 06:06:39: %CPU_REDUN-5-STATUS_CHG: ACTIVE (sev 0), peer is STANDBY (sev 0

)

Dec 31 06:06:50: %LINK-3-UPDOWN: Interface Fastethernet-sby0, changed state to u

p

Dec 31 06:06:51: %LINEPROTO-5-UPDOWN: Line protocol on Interface Fastethernet-sb

y0, changed state to up

DWDM-TLC1-R1SW#

Michael Dooley · ‎01-14-2009

If you can get to this link the messages are explained there.

www.cisco.com/en/US/partner/products/hw/optical/ps2011/prod_error_message09186a00806065ca.html')">http://www.cisco.com/en/US/partner/products/hw/optical/ps2011/prod_error_message09186a00806065ca.html

It is the Cisco ONS 15540 ESPx System Alarms and Error Messages document. They are listed by the facility codes. In your example you look at what is there under CPU_REDUN.

You can also go down this path to get there:

www.cisco.com > (login) > Support > Troubleshoot > Optical Networking > Metro DWDM > Cisco ONS 15500 Series > error and System Messages

Then choose either:

1) Cisco ONS 15540 ESP System Alarms and Error Messages

OR

2) Cisco ONS 15540 ESPx System Alarms and Error Messages

Hope this helps.... Mike Dooley - Cisco Optical TAC

View solution in original post

Michael Dooley · ‎01-14-2009

It appears the CPU in slot 7 rebooted. The slot 6 CPU (active) is reporting this from its point of view looking toward the standby CPU (its PEER):

PEER_EXITED

peer is NON-PARTICIPANT

Communication with the peer CPU has been lost

Int Fastethernet-sby0, changed state to down

and so on for the peer CPU to go down and come back up.

rlortiz · ‎01-14-2009

Thanks midooley that helps.

Michael Dooley · ‎01-14-2009