Nokia BSC Commands

download Nokia BSC Commands

of 3

description

NOKIA BSC COMMANDS

Transcript of Nokia BSC Commands

Nokia BSC CommandsHello ,These commands use for Nokia BSC & MSC.

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

Alarm monitoring:ZAHO; displays current active alarms in actual MSC and BSC onlyZEOL:#; displays active alarms on BCF (BCF = Site Manager or CF)ZEEI:BCF=#; displays the operational state of the siteZEOH:date,time:BCF=#; displays alarm history for site for the date and time listedZAHO:ET,#; displays current alarms for that ET (PCM)ZAHP:ET,#; displays alarm history for that ETZEEL:BL; displays locked Sites, Sectors and TRXs on BSC

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

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

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

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

Locking and unlocking Sectors:ZEQS:BTS=#:L; locks entire sector down without Forced HandoverZEQS:BTS=#:L:FHO,#; shuts down entire sector with Forced HandoverZEQS:BTS=#:U; unlocks entire sector

Locking and unlocking TRXs:ZERS:BTS=#,TRX=#:L; locks TRX down without Forced HandoverZERS:BTS=#,TRX=#:L:FHO,#; shuts down TRX with Forced HandoverZERS: BTS=#,TRX=#:U; unlocks TRX

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

Bouncing Lap Ds on a Site:ZDTI:::PCM=#; displays Lap D channels for entire siteZDTC:lap d #:BL; blocks desired Lap D channelZDTC:lap d #:WO; places Lap D channel in working state

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

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

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

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

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

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

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 IPLog inRun the following command: df k

Taking an ET out of BL state:ZUSC:ET,#:WORKINGBLOCKEDTESTSEPERATEDSEPERATED-NO HARDWAREGo back up the tree to get it back into Working

Rolling the BCCH on a Sector:ZDTI:::PCM=#; Find out what TSL the radio is on that you want the BCCH onZDTC:lapd:BL; Block the TSL on the radio that the BCCH is going toZDTC:lapd:AL; Allow activation of the TSL that the BCCH is going toZDTC:lapd:WO; Brings TSL to a working state that the BCCH is going toZDTI:::PCM=#; Find out what TSL the radio that HAD the BCCH is onZDTC:lapd:AD; Deny Activation of the TSL that HAD the BCCH on itZDTC:lapd:BL; Block the TSL that the BCCH was onZDTC:lapd:WO; 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 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 CAS1081d 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.

SLMSC001 CM-1 SWITCH 2005-11-29 08:07:22.06CANCEL CM-1 1A003-03 KICKER(0178) 2087 LOW TRAFFIC CAPACITY ON CIRCUIT GROUP 02 0386