Professional Documents
Culture Documents
NOKIA COMMANDS:
Hot Keys:
Ctrl + B repeats last and previous commands on the MML
Ctrl + Y interrupts current command being typed or run
Alarm monitoring:
ZAHO; displays current active alarms in actual MSC and BSC only
ZEOL:#; displays active alarms on BCF (BCF = Site Manager or CF)
ZEEI:BCF=#; displays the operational state of the site
ZEOH:date,time:BCF=#; displays alarm history for site for the date and time listed
ZAHO:ET,#; displays current alarms for that ET (PCM)
ZAHP:ET,#; displays alarm history for that ET
ZEEL:BL; displays locked Sites, Sectors and TRXs on BSC
Statusing Timeslots:
ZEEL::BCF=#; Status the timeslots on a BCF
The alarm that you are talking about happens on MF circuits and is caused by the LEC not releasing
or acknowledging us quick enough. Do to the latency, the Nokia locks out the trunk in question.
When you see this alarm you should assume that it is 911 related and the issue needs to be corrected
ASAP. The alarm field will be shown below.
SLMSC001 CASU-1 SWITCH 2005-11-27 00:07:37.44
*** ALARM CASU-1 1E001-00 SI9_SO
(9952) 2153 CIRCUIT RELEASING FAILED IN CAS
1081d 13d 29 0823 01 FF 01 02 01 01 10 00 00 00
If you look above I have highlighted in red the circuit that needs to be reset (1081-13). If you take
the circuit to a NU state for about 30 seconds and then back to WO it should clear.
ZCEC:CRCT=1081-1:BA;
ZCEC:CRCT=1081-1:NU;
ZCEC:CRCT=1081-1:BA;
ZCEC:CRCT=1081-1:WO;
Also, you should get a Low Traffic Capacity alarm with supplementary information. I have the
alarm listed below and the supplementary info is in red (02 0386). If you convert 386 from HEX to
Decimal it comes out to 902. At that time you can do the command
ZRCI:SEA=3:CGR=902:PRINT=5:; and look at the circuit group.