MML Commands

Informations COMMANDS
Check All Sites Under Selected BSC ZEEI;
CHECK Specific site Under BSC ZEEI:NAME=<Site_Name_including_sector>;
ZEEI:BCF=01;
BTS
LOCK BCF ZEFS:<Bcf_id>:L;
UNLOCK BCF ZEFS:<Bcf_id>:U;

LOCK BTS ZEQS:BTS=<Bts_id>:L;

UNLOCK BTS ZEQS:BTS=<Bts_id>:U;

LOCK TRX ZERS:BTS=<Bts_id>,TRX=<Trx_no>:L;

UNLOCK TRX ZERS:BTS=<Bts_id>,TRX=<Trx_no>:U;

LOCK TRX TS (Time Slot) ZERS:BTS=<Bts_id>,TRX=<Trx_no>,CH=<Ch_no>:L;

ZERS:BTS=<Bts_id>,TRX=<Trx_no>,CH=<Ch_no>:U;

CHECK BTS ALARMS

Output Current Alarms of selected BTS ZEOL:<Bcf_id>;
Output History Alarms of Selected BTS ZEOH:<YYYY-MM-DD,:BCF=<Bcf_Id>;
Cancelled BTS alarm ZEOR:<Bcf_id>:<Consecutive_number>;

Need my assistance to provide information

Alarms
Lists alarms currently on ZEOL;
List alarm history ZEOH::BCF=bcf;
All BSC related alarms ZAHO;
Alarms from aall cp units (OMU, MCMU & BCSU's) ZAHO:COMP;
Alarm history for BSC ZAHP:::yyyy-mm-dd;
x=(1-min, 2-maj, 3-crit) ZEOL::CLS=ALx;
Block paticular BTS alarms in Bsc ZEOB:xxxx;
Lists blocked BTS alarms ZEOE;
Checks blocked cell sites ZEEL:BL;
Output blocked BSC alarms ZABO;
Block BSC alarm ZABB:<bsc_alm_nbr>;
Unblock BSC alarm ZABU:<bsc_alm_nbr>:
BSC alarm parameters ZEOO;

TOP LEVEL INFORMATION ON BSC

Shows C-NUM and name of BSC ZQNI;
All BSC related alarms ZAHO;
A-Interface / A-bis signaling Interface ZNET;
Signalling Link Status - Should be AV-EX ZNEL;
Operating states of all Units in BSC ZUSI:ALL;
Status all BCF's in BSC ZEEI;
Local IP to BSC ZQRI:OMU;
SS7 Through Connections ZWGO;

Kindly find Below procedure for Ping test .

Example :BCF=5(JIZ005)

To check control plane of OMU Association:-

ZOYV:IUA:NAME=BCFXOMU:A:; (where X is BCF no)

ZOYV:IUA:NAME=BCF5OMU:A:;

mcBSC JZNBSC01 2014-12-10 10:40:56

INTERROGATING SCTP ASSOCIATION DATA

SCTP ASSOCIATION ASSOC SCTP PARAMETER SET

NAME IND UNIT USER ROLE NAME STATE
---------------- ----- ------- ----- ------ ---------------- -------------
BCF5OMU 384 BCXU-6 IUA SERVER AFAST ASP-ACTIVE

SOURCE ADDRESS 1 . . . . . . . : 10.163.189.132

SOURCE ADDRESS 2 . . . . . . . :
SOURCE PORT . . . . . . . . . : 49152
PRIMARY DEST. ADDRESS . . . . : 10.164.113.72/26
SECONDARY DEST. ADDRESS . . . :
DESTINATION PORT . . . . . . . : 49152

MAX. DATA STREAM COUNT . . . . : 64

SPECIFICATION VERSION . . . . : 1

Command for Ping test :-

ZQRX:BCXU,6::PING:IP="10.164.113.72",SRC="10.163.189.132",SIZ=1500,; (Define both source & destination IP’s)

To check control plane/Userplane of TRX Association:- (both CP/UP IPdestination will be same for TRX’s only Source will differ)

ZOYV:IUA:NAME=BCFXY:A:; (where X is bcf no & Y is TRX no)

ZOYV:IUA:NAME=BCF5TRX1:A:;

mcBSC JZNBSC01 2014-12-10 11:26:51

INTERROGATING SCTP ASSOCIATION DATA

SCTP ASSOCIATION ASSOC SCTP PARAMETER SET

NAME IND UNIT USER ROLE NAME STATE
---------------- ----- ------- ----- ------ ---------------- -------------
BCF5TRX1 385 BCXU-6 IUA SERVER AFAST ASP-ACTIVE

SOURCE ADDRESS 1 . . . . . . . : 10.163.189.148

SOURCE ADDRESS 2 . . . . . . . :
SOURCE PORT . . . . . . . . . : 49153
PRIMARY DEST. ADDRESS . . . . : 10.164.101.72/26
SECONDARY DEST. ADDRESS . . . :
DESTINATION PORT . . . . . . . : 49153

MAX. DATA STREAM COUNT . . . . : 64

SPECIFICATION VERSION . . . . : 1

COMMAND EXECUTED

Command for Ping test :-

ZQRX:BCXU,6::PING:IP="10.164.113.72",SRC="10.163.189.132",SIZ=1500,; (Define both source & destination IP’s)

To Rest Associations :-
Check association:-
ZOYV:IUA:NAME=BCF5TRX1:A:;

Reset:-

ZOYS:IUA:BCF1TRX1:DOWN:;
Wait for some seconds
ZOYS:IUA:BCF1TRX1:ACT;

Dchannel:-

ZDWD: ..... DELETE D-CHANNEL

ZWWP: ..... CREATE ABIS D-CHANNEL
ZDWQ: ..... INTERROGATE ABIS D-CHANNEL DATA

(You can get the Dchannel no from ZERO command)

Memorize EXAMPLE
ZEEI ZEEI;
ZEEI ZEEI:NAME=ZMKA320A;
ZEEI:BCF=01;

ZEFS ZEFS:01:L;
ZEFS:01:U;

ZEQS ZEQS:BTS=01:L;
ZEQS:BTS=01:U;

ZERS ZERS:BTS=01,TRX=01:L;
ZERS:BTS=01,TRX=01:U;

ZERS ZERS:BTS=01,TRX=01,CH=0:L;
ZERS:BTS=01,TRX=01,CH=0:U;

ZEOL ZEOL:01
ZEOH ZEOH:2008-02-10,:BCF=01;
ZEOR ZEOR:01:28692
rce & destination IP’s)
for TRX’s only Source will differ).

rce & destination IP’s)

·WORKING (WO)
The object is in the normal functional state. From the viewpoint of the BSS call control functions, the WORKING radio network
·BLOCKED ¾ BCF FAULT (BL-BCF)
The object is blocked out of use due to a fatal BTS-site-wide failure.
·BLOCKED ¾ BTS FAULT (BL-BTS)
The object is blocked out of use due to a fatal sector-wide failure on the BTS site.
·BLOCKED ¾ FU/CU FAULT (BL-CF)
The object is blocked out of use due to both a fatal FU (Frame Unit) failure and a fatal CU (Carrier Unit) failure on the BTS site
·BLOCKED ¾ CLOCK (BL-CLK)
The object is blocked out of use due to a clock synchronisation failure on the BTS site.
·BLOCKED ¾ CU FAULT (BL-CU)
The object is blocked out of use due to a fatal CU (Carrier Unit) failure on the BTS site.
·BLOCKED ¾ DIAGNOSTIC (BL-DGN)
The object is temporarily blocked out of use due to base station diagnostic activities.
·BLOCKED ¾ FLOATING (BL-FLO)
The logical TRX is blocked out of use on the sector, because the physical TRX has been switched to another sector of the BTS
·BLOCKED ¾ FU FAULT (BL-FU)
The object is blocked out of use due to a fatal FU (Frame Unit) failure on the BTS site.
·BLOCKED ¾ POWER (BL-PWR)
The object is blocked out of use due to a mains power failure on the BTS site.
·BLOCKED ¾ RSL FAULT (BL-RSL)
The object is blocked out of use due to a telecom Abis D-channel link disconnection.
·BLOCKED ¾ RESET (BL-RST)
The logical radio network object is blocked out of use due to the reset of the corresponding physical radio network equipment.
·BLOCKED ¾ SHUTTING DOWN (BL-SHD)
The object will be blocked out of use within a time limit. New call attempts are prohibited via an object in the BL-SHD state and
·BLOCKED ¾ BCSU RESET (BL-SU)
The object is blocked out of use due to a BCSU unit reset on the BSC.
·BLOCKED ¾ SWITCH OVER (BL-SWO)
The object is blocked out of use due to an ongoing background data switchover.
·BLOCKED ¾ SYSTEM (BL-SYS)
The radio network management function class of the BSC has blocked the logical object out of use due to ongoing radio netwo
·BLOCKED ¾ TRX FAULT (BL-TRX)
The object is blocked out of use due to a fatal TRX-wide failure on the BTS site.
·BLOCKED ¾ RTSL FAULT (BL-TSL)
The object is blocked out of use due to a fatal radio time slot (RTSL) wide failure on the BTS site.
·BLOCKED ¾ TESTING (BL-TST)
The object is blocked temporarily out of use due to radio network testing activities.
·BLOCKED ¾ USER (BL-USR)
The operator has blocked the object out of use. The administrative state of the object or of a related higher level object is LOC
·BLOCKED ¾ WAITING FOR AUTOCONFIGURATION (BL-WAC)
The object is blocked out of use because it is waiting for autoconfiguration or Automatic Picocell Planning