Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

How to diagnosea HW/Sw pb issue on a E1 board (AS5850 HW)

Hello

I have seen the following on the TGW cisco A5850 / IOS 12.4(13d)

(In slot 1 - This is a 24 E1 card)

The state of the board switch between "Power Pending" // "ROMMON"

#sh chassis

Slot Board CPU Proc Memory I/O Memory State Elapsed

Type Util Total (free) Total (free) Time

0 24E1 0%/0% 89429568 ( 61%) 33554432 ( 66%) IOS up 3d00h

1 24E1 0 ( 0%) 0 ( 0%) Power pending 00:00:09

....

or

Slot Board CPU Proc Memory I/O Memory State Elapsed

Type Util Total (free) Total (free) Time

0 24E1 0%/0% 89429568 ( 61%) 33554432 ( 66%) IOS up 3d00h

1 24E1 0 ( 0%) 0 ( 0%) ROMMON 00:00:00

....

Other collected infos:

#sh diagnostic-monitor test fb1-mil-path-ping details

Note: R = Root cause failure.

S = Superseded root cause failure.

* = Bootup test only.

Name Test Test Result Reason

Result

-------------------------- ----------- -----------------------

fb1-mil-path-ping Unavailable SW/HW not ready

The following debug

M-Bus:

Environmental monitor debugging is on

RSC Slot Subsystem:

RSC Slot State Machine debugging is on

RSC Slot Redundancy debugging is on

Nitro MBUS:

MBUS state machine debugging is on

gives

Dec 31 10:42:59.140: SLOT(1):State 'ROMMON': Event 'timer expired'

Dec 31 10:42:59.140: MBUS(16): Download decrement lock (1)

Dec 31 10:42:59.140: MBUS(16): Download release lock

Dec 31 10:42:59.140: MBUS(1): Powering down slot

Dec 31 10:42:59.140: SLOT(1):State 'Power pending': Event 'entered'

Dec 31 10:42:59.140: MBUS(1): Requesting download lock for 'Slot SM'

Dec 31 10:42:59.140: MBUS(1): Download request queue is empty, wake up process

Dec 31 10:42:59.140: MBUS(1): Processing download lock request for this slot

Dec 31 10:42:59.140: MBUS(1): No current download lock, grant it to this slot

Dec 31 10:42:59.140: MBUS(1): Send lock grant to client 'Slot SM'

Dec 31 10:42:59.140: SLOT(1):State 'Power pending': Event 'download lock granted'

Dec 31 10:43:00.972: SLOT(1):State 'Power pending': Event 'power cycle'

Dec 31 10:43:00.972: MBUS(1): Download release lock

Dec 31 10:43:00.972: SLOT(1):State 'Power cycle': Event 'entered'

Dec 31 10:43:00.972: MBUS(1): Powering down slot

Dec 31 10:43:00.972: MBUS: No more lock requests to process

Dec 31 10:43:05.972: SLOT(1):State 'Power cycle': Event 'timer expired'

Dec 31 10:43:05.972: SLOT(1):State 'Power pending': Event 'entered'

Dec 31 10:43:05.972: MBUS(1): Requesting download lock for 'Slot SM'

Dec 31 10:43:05.972: MBUS(1): Download request queue is empty, wake up process

Dec 31 10:43:05.972: MBUS(1): Processing download lock request for this slot

Dec 31 10:43:05.972: MBUS(1): No current download lock, grant it to this slot

Dec 31 10:43:05.972: MBUS(1): Send lock grant to client 'Slot SM'

Dec 31 10:43:05.972: SLOT(1):State 'Power pending': Event 'download lock granted'

Dec 31 10:43:15.973: SLOT(1):State 'Power pending': Event 'timer expired'

Dec 31 10:43:15.973: MBUS(1): Joined the existing lock grant (0 existing members)

Dec 31 10:43:15.973: SLOT(1):State 'ROMMON': Event 'entered'

Dec 31 10:43:15.973: MBUS(1): Powering up slot

Dec 31 10:43:17.417: ENVMON:updating env stats before going to sleep for 30000 msec...

More informations is available in the attached file

My question is the following -

How can I konow if it is a HW pb (backlane, power supply, E1 Board) or a Sw pb ?

Unfortunately, I have no spare board to testif a replacement solves the pb.

I have to mention that this hw have worked in the past. but it is poassible that

a switch off on the pwer has been perfomed in our lab for maintenance purpose.

Any kind of information is welcome

2 REPLIES
New Member

Re: How to diagnosea HW/Sw pb issue on a E1 board (AS5850 HW)

The file with more informations

Cisco Employee

Re: How to diagnosea HW/Sw pb issue on a E1 board (AS5850 HW)

Hi, Have you switched the E1 card in slot0 with slot1? (Not sure if this is possible in your network if live or not). After the switch, if the card that was in slot0 works in slot1, and the card that was in slot1 does not work in slot0, then it seems the card is bad. (i.e. the problem follows the card). Or you can try the card in a different slot other than slot1 (but not 6 or 7). Also you might try "show chassis slot 1" and look at the flags and it may give you a clue as well. You can also try reseating the card or resetting the card via software such as "hw-module slot 1 reset". If the problem stays at the same slot no matter which card is present, then its a possible slot/backplane issue.

In my experience, this has proven to be bad card more times than not.

140
Views
0
Helpful
2
Replies
CreatePlease to create content