Nokia Command List

NOKIA COMMANDS:

Hot Keys: Ctrl + B Ctrl + Y repeats last and previous commands on the MML interrupts current command being typed or run

Alarm monitoring: ZAHO; d BSC only ZEOL:#; r or CF) displays current active alarms in actual MSC an displays active alarms on BCF (BCF = Site Manage

ZEEI:BCF=#;

displays the operational state of the site

ZEOH:date,time:BCF=#; displays alarm history for site for the date and time lis ted ZAHO:ET,#; ZAHP:ET,#; ZEEL:BL; displays current alarms for that ET (PCM) displays alarm history for that ET displays locked Sites, Sectors and TRXs on BSC

Investigating Clear Codes: ZTUT:CLR; ZTUL:CLR; displays current clear codes on the MSC displays latest history of clear codes

Canceling Bogus alarms on a Site: (Perform both commands) ZEOR:#:alarm #; ZEFR:#:OMU; cancels alarm on site resets the OMU (Operations and Maintenance Unit)

Canceling Bogus alarms on a BSC: ZACC:####; came in ZACA:####; cancels the alarm using the consecutive # in which it cancels the alarm using the alarm identifier #

Locking and unlocking a Site: ZEFS:bcf #:L; ZEFS:bcf #:U; locks entire Site without Forced Handover unlocks entire Site

Locking and unlocking Sectors: ZEQS:BTS=#:L; locks entire sector down without Forced Handover

ZEQS:BTS=#:L:FHO,#; shuts down entire sector with Forced Handover ZEQS:BTS=#:U; unlocks entire sector

Locking and unlocking TRXs: ZERS:BTS=#,TRX=#:L; locks TRX down without Forced Handover

ZERS:BTS=#,TRX=#:L:FHO,#; ZERS: BTS=#,TRX=#:U;

shuts down TRX with Forced Handover unlocks TRX

Resetting the Site or OMU: ZEFR:#:SITE; ZEFR:#:OMU; restarts SITE restarts OMU

Bouncing Lap D ZDTI:::PCM=#; ZDTC:lap d #:BL; ZDTC:lap d #:WO;

s on a Site: displays Lap D channels for entire site blocks desired Lap D channel places Lap D channel in working state

Error Checking on an ET (PCM): ZYMO:ET,#; ZYEU:ET,#:SLIDL=5; checks error counter for specific ET resets error counter for specific ET

Querying the # of calls on a site: ZERO:BTS=#; ZERO:BTS=#,TRX=#; displays all calls on desired sector displays all calls on desired TRX only

Sparing or Rolling a BCSU: ZUSI:BCSU; on ZFWO:BCSU=0&&8; ZUSC:BCSU,#:SP; Y for Yes displays what BCSU the SP was previously displays what BCSU the BL condition is on spares the BCSU with the BL condition on it executes the command

Statusing Timeslots: ZEEL::BCF=#; Status the timeslots on a BCF

Status ET alarms on a BSC ZAHP:ET,:::; Show all ET's that are in alarm

Taking an ET out of Seperated State ZUSC:ET,#:SE; (SE-NH) Will place the ET in a Separated - No Hardware state

Status session for User ID and commands: ZIGO: Displays commands run for BSC on specific date and time.

Reloading software on a site: ZEWV:BCF #:BU; Reloads the software on a BCF

Checking OMC alarms: Open a terminal and telnet to the IP Log in Run the following command: df k

Taking an ET out of BL state: ZUSC:ET,#: WORKING BLOCKED TEST SEPERATED SEPERATED-NO HARDWARE Go back up the tree to get it back into Working

Rolling the BCCH on a Sector: ZDTI:::PCM=#; BCCH on Find out what TSL the radio is on that you want the

ZDTC:lapd:BL; o ZDTC:lapd:AL; to ZDTC:lapd:WO; to ZDTI:::PCM=#; ZDTC:lapd:AD; ZDTC:lapd:BL; ZDTC:lapd:WO;

Block the TSL on the radio that the BCCH is going t Allow activation of the TSL that the BCCH is going Brings TSL to a working state that the BCCH is going Find out what TSL the radio that HAD the BCCH is on Deny Activation of the TSL that HAD the BCCH on it Block the TSL that the BCCH was on Brings the TSL to a working state

Clearing Circuit Releasing Failed in CAS alarms:

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 Nok ia locks out the trunk in question. When you see this alarm you should assume t hat it is 911 related and the issue needs to be corrected ASAP. The alarm field will be shown below.

<HIST> SLMSC001 *** ALARM CASU-1 1E001-00

CASU-1 SI9_SO

SWITCH

2005-11-27 00:07:37.44

(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 b ack 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.

<HIST> SLMSC001 CANCEL CM-1 1A003-03

CM-1 KICKER

SWITCH

2005-11-29 08:07:22.06

(0178) 2087 LOW TRAFFIC CAPACITY ON CIRCUIT GROUP 02 0386

Sign in|Report Abuse|Print Page|Remove Access|Powered By Google Sites