[nsp] Recovering of bad modems on AS5300

From: Vladimir Litovka (doka@kiev.sovam.com)
Date: Wed Dec 27 2000 - 17:55:07 EST


Hello,

 I've experienced strange trouble and don't know, is it feature of bug? :)
 There was few modems on AS5300 marked as 'B' and I have changed
 configuration in such way for correct (as I was thinking :) workaround:

spe 1/0 2/9
 firmware location flash:mica-modem-pw.2.7.2.0.bin
 firmware upgrade recovery
!
modem recovery maintenance window 60
modem recovery maintenance action drop-call
modem recovery maintenance time 6:00
modem recovery maintenance schedule immediate

 and after this action modems on 'problematic' module got status 'p' -
 download pending. Ok and I was suspecting, that after all modems will be
 available, firmware's download will start and finish (because 'schedule
 immediate' used), but they are still in pending state (already about 1
 hour). Is there way to return they to normal state and avoid such
 behaviour in the future? And, generally, is there way to return 'B'ad
 modems to normal state (if they, of course, don't broken really)?

 And next question - there are messages in log:

%MICA-3-MODEMBAD: Modem number 1/49 is bad, Error code is 31
%MICA-3-MODEMBAD: Modem number 1/52 is bad, Error code is 34
%MICA-3-MODEMBAD: Modem number 1/53 is bad, Error code is 35
%MICA-3-MODEMBAD: Modem number 1/51 is bad, Error code is 33
%MICA-3-MODEMBAD: Modem number 1/48 is bad, Error code is 30
%MICA-3-MODEMBAD: Modem number 1/50 is bad, Error code is 32

 what does it mean? Where is description of of these error codes?

 I'm using IOS 12.0(7)T IP Plus, firmware 2.7.2.0. AS5300 consists of 8
 E1/PRI ports and two CC2 cards with 120 modems on every board.

 Thank you.

-- 
Vladimir Litovka <doka@kiev.sovam.com>
 . Phone/Fax: +380 44 4900111
 . ICQ/none, talk/none ;)



This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:24 EDT