Interrogating site status and info: ZEEI:BCF=xx;xx--> BCF number Block/Unblock a site (BCF): Set BCF state to LOCKED:ZEFS:xx:L;xx

--> BCF number;Set BCF state to UNLOCKED:ZEFS:xx:U;xx --> BCF number; Block/Unblock a sector (BTS) of a site (BCF) withoutforced handover (FHO): Set sector state to LOCKED:ZEQS:BTS=xx:L;xx--> BTS numberSet sector state to UNLOCKED:ZEQS:BTS=xx:U;xx--> BTS number Block/Unblock a sector (BTS) of a site (BCF) withforced handover (FHO): Set sector state to LOCKED:ZEQS:BTS=xx:L:FHO,time;xx--> BTS numbertime --> Time for forced handover in secondsSet sector state to UNLOCKED:ZEQS:BTS=xx:U;xx--> BTS number Block/Unblock a TRX of a site with FHO: Set TRX state to LOCKED:ZERS:BTS=xx,TRX=xx:L:FHO,time;Set TRX state to UNLOCKED:ZERS:BTS=xx,TRX=xx:U;Time is set in seconds.If the TRX is BL-SY, BL-RSL or BL-TRX then using the "FHO" argument in thecommand block is uneccessary.

Block/Unblock a TRX of a site without FHO: Set TRX state to LOCKED:ZERS:BTS=xx,TRX=xx:L;Set TRX state to UNLOCKED:ZERS:BTS=xx,TRX=xx:U; Base band hopping for all sectors on a site withoutForced Handover: 1.Check site in remedy for: BCF number, parent element (BSC) 2.Open MML session to BSC 3.Check site for status and BTS numbers: ZEEI:BCF=xx; xx--> BCF number 4.Set BCF state to LOCKED:ZEFS:xx:L; xx --> BCF number; 5.Set sector state to LOCKED:ZEQS:BTS=xx:L; xx--> BTS number 6.Change Hopping status:

ZEQE:BTS=xx:HOP=BB; (for BB activation) ZEQE:BTS=xx:HOP=N; (for BB deactivation) xx--> BTS number 7.Set sector state to UNLOCKED: ZEQS:BTS=xx:U; xx--> BTS number 8.Check site for status:ZEEI:BCF=xx; xx--> BCF number 9.Repeat steps 5 to 8 for all sectors 10.Set BCF state to UNLOCKED:ZEFS:xx:U; xx --> BCF number; 11.Check site for status:ZEEI:BCF=xx; xx--> BCF number Base band hopping for all sectors on a site withForced Handover: 1.Check site in remedy for: BCF number, parent element (BSC) 2.Open MML session to BSC 3.Check site for status and BTS numbers:ZEEI:BCF=xx; xx--> BCF number 4.Set sector state to LOCKED: ZEQS:BTS=xx:L:FHO,time; xx--> BTS number time --> Time for forced handover in seconds 5.Check site for status: ZEEI:BCF=xx;xx--> BCF number 6.repeat step 4 and 5 for all sectors 7.Set BCF state to LOCKED:ZEFS:xx:L ;xx --> BCF number;

8.Change Hopping status: ZEQE:BTS=xx:HOP=BB; (for BB activation) ZEQE:BTS=xx:HOP=N; (for BB deactivation) xx--> BTS number 9.Set sector state to UNLOCKED: ZEQS:BTS=xx:U; xx--> BTS number 10.Check site for status: ZEEI:BCF=xx; xx--> BCF number 11.Repeat steps 7 to 10 for all sectors 12.Set BCF state to UNLOCKED: ZEFS:xx:U;xx --> BCF number; 13.Check site for status: ZEEI:BCF=xx; xx--> BCF number TRX Specific MML Commands: 1.ZERO:BTS=xx,TRX=xx; This command displays the traffic channels in use on an individual TRX.You can see if there are alls taking place on the specific TRX identified inyour arguments given within you command. 2. ZERS:BTS=xx,TRX=xx:L:FHO,30; This command enables you to lock a TRX and force handover calls toanother TRX or adjacent cell. The given time here is 30 seconds as anexample.To unlock type:ZERS:BTS=xx,TRX=xx:U;If the TRX is BL-SY, BL-RSL or BL-TRX then using the "FHO" argument in thecommand block is unnecessary. 3. ZDTI:NAME=xxxxx; xxx= T+BCF Nr+sectorNr+TRXnr; This interrogation displays a LAPD link(Signaling Link) and shows whether ornot the LAPD is in working order or not.

Example: ZDTI:NAME=T8611; BCF Nr. = 86; The first sector of the BCF and the first trx on sector. 4. ZDTI:::PCM=xx; This shows all LAPD links attached to this specific PCM (ET). 5. ZDTC:xxxxx:AD; xxxxx= T+BCF Nr+sectorNr+TRXnr; This command sets signaling activation attribute to Denied on the specifiedTRX. 6. ZDTC:xxxxx:AL; xxxxx= T+BCF Nr+sectorNr+TRXnr; This command sets signaling activation attribute to Allowed on thespecified TRX. 7. ZDTC:xxxxx:BL; xxxxx= T+BCF Nr+sectorNr+TRXnr; This command blocks the signaling on the specified TRX. 8. ZDTC:xxxxx:WO; xxxxx= T+BCF Nr+sectorNr+TRXnr; This command activates the signaling on the specified TRX. BTS Specific MML Commands: 1. ZEQO:BTS=xx:ALL; This command displays all configuration settings on a BTS. The most common thing we will be looking for from a NOC Tech point of view is the GPRS settings. 2. ZEQS:BTS=xx:L:FHO,time; Set sector state to LOCKED: xx--> BTS number time --> Time for forced handover in seconds ZEQS:BTS=xx:U;

Set sector state to UNLOCKED: xx--> BTS number 3. ZEQV:BTS=xx:GENA=Y; This command toggles GPRS within the cell. Replace the Y with an N todisable GPRS. 4. ZERO:BTS=xx; This command displays the traffic channels in use on all TRXs within thecell. You can see if there are calls taking place on all of the TRX trafficchannels 5. ZEEI:BTS=xx; This will show the information pertaining to the BTS and the TRXsconnected to it. You will be able to see if it and the TRXs are in a workingstate.This will also show you which TRX has the BCCH on it. BCF Specific MML Commands: 1. ZEFS:xx:L; xx= BCF number. This command locks the BCF and by replacing the L with a U the commandwill unlock the site 2. ZEFR:xx:OMU; xx= BCF number.This command resets the OMU on the site. 3. ZEFR:xx:SITE; xx= BCF number. This command resets the entire site immediately And drops calls if present.

4. ZEEI:BCF=xx; This command shows site information such as the BTS's and TRX's connectedto the specified BCF.

5. ZEOL:xx; xx= BCF number.

This command shows the current alarms for the BCF in question. BSC Specific MML Commands: 1. ZAHO:; This command displays all the current alarms on the BSC. The search canalso be defined with the arguments as: ZAHO::CLS=AL1; (displays 1 star alarms) ZAHO::CLS=AL2; (displays 2 star alarms) ZAHO::CLS=AL3; (displays 3 star alarms) The second colon in the main command is default for all units. The searchcan be refined to individual units in the cabinet in alarm. So if you want tocheck 2 star alarms related to BCSU-0 type the command as follows: ZAHO:BCSU,0:CLS=AL2; 2. ZUSI:; Type this command to find out the working state of a units. You can also look at all computer related units in the BSC which excludes the ET's. 3. ZEEL; This command shows the amount of traffic currently running on the BSC. Italso shows blocked radio time slots which are obviously beneficial to theNOC. Refine the search by modifying the command as follows: ZEEL:BL; This will show you a very informative search result so you can actually seewhat BCF's, BTS's, and TRX's are in a blocked state whether it is BL-USR/BL-RSL/BL-TRX/BL-PWR/BL-SY/ you can see where this is going. 4. ZNEL; The command outputs the states of the signaling links on the BSC. 5. ZNER; This command interigates the signalling route set states.

6. ZAHP;

This command shows all the alarms from midnight of the current day. It isalso modified to investigate alarms from a previous date. For example: ZAHP:::2009-12-01,04-00-00; You can also refine the search to a specific unit. 7. ZDCD; This command shows you the current date and time on the BSC. MSC Specific MML Commands: 1. ZAHO:; This command displays all the current alarms on the MSC. The search canalso be defined with the arguments as: ZAHO::CLS=AL1; (displays 1 star alarms) ZAHO::CLS=AL2; (displays 2 star alarms) ZAHO::CLS=AL3; (displays 3 star alarms) The second colon in the main command is default for all units. The search can be refined to individual units in the cabinet in alarm. So if you want to check 2 star alarms related to BCSU-0 type the commandas follows: ZAHO:BCSU,0:CLS=AL2; 2. ZRCI:SEA=3:CGR=(cgr #):PRINT=5:; This command prints all the circuits with in the circuit group. ZRCI:SEA=4:CRCT=(circuit #(s)):; This command shows the circuit(s) working state. 3. ZUSI:<unit>; Type this command to find out the working state of a unit. You can alsolook at all computer related units in the MSC which excludes the ET's. 4. ZEPO:NAME=(bts name); This command displays the BTS information on the MSC side of the network. 5. ZCEL:FORM=EXT,ST=NO-WO; This command will print out the circuits in the MSC that are in a state otherthan working.

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; ZEOL:#; ZEEI:BCF=#; displays current active alarms in actual MSC and BSC only displays active alarms on BCF (BCF = Site Manager or CF) displays the operational state of the site

ZEOH:date,time:BCF=#; displays alarm history for site for the date and time listed 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:####; ZACA:####; cancels the alarm using the consecutive # in which it came in cancels the alarm using the alarm identifier #

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

ZEFS:bcf #:U;

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; ZERS:BTS=#,TRX=#:L:FHO,#; ZERS: BTS=#,TRX=#:U; locks TRX down without Forced Handover shuts down TRX with Forced Handover unlocks TRX

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

Bouncing Lap Ds on a Site: ZDTI:::PCM=#; ZDTC:lap d #:BL; ZDTC:lap d #:WO; 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; ZFWO:BCSU=0&&8; ZUSC:BCSU,#:SP; Y for Yes displays what BCSU the SP was previously on 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=#; ZDTC:lapd:BL; ZDTC:lapd:AL; ZDTC:lapd:WO; ZDTI:::PCM=#; ZDTC:lapd:AD; ZDTC:lapd:BL; ZDTC:lapd:WO; Find out what TSL the radio is on that you want the BCCH on Block the TSL on the radio that the BCCH is going to Allow activation of the TSL that the BCCH is going to Brings TSL to a working state that the BCCH is going to 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 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. <HIST> 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. <HIST> SLMSC001 CM-1 SWITCH 2005-11-29 08:07:22.06 CANCEL CM-1 1A003-03 KICKER (0178) 2087 LOW TRAFFIC CAPACITY ON CIRCUIT GROUP 02 0386