BSC O&M_NMC

Infratech Ghana LtdPrepared by No.

Mr. Manoj Kaundal 1Date

2009-04-14

O&M procedure for BSC

Abstract

This document is intended to describe the contents of BSS Health Check Service on site , and to outline AXE commands that can be used to check the operational status of the network.

1 Purpose

The commands in the document can be used as a Reference only for daily health check in BSS.

2 BSS Routines2.1 Check the Alarm Log

Command

IOEXP;

ALLIP;

Carefully check the alarms related to the below mentioned

CP STATE GROUP SWITCH CLOCK SIZE ALTERATION RP STATE

If any alarm found, Escalate to 1st level support immediately.

2.2 Check the Processor Load

Command

PLLDP;

Processor load must be within limits and report if in Eighties.

2.3 Check the CP State

Both CP should be working



2009-04-14

Command

DPWSP;

2.4 Check that the latest backup file are available in the system

Command

SYBFP: FILE;

2.5 Check the error intensity counter

Command

SYELP;

Note down error values. Escalate to 1st level support.

2.6 Check for restart details

Note down the latest restarts /applerr /forlopps, if any.

Command

SYRIP: SURVEY;

Check Explanation column. If there are restart info(small, large, reload), escalate immediately to 1st level Support

2.7 Check network synchronization and reference data

Command

CACLP: ALL;

2.8 Check for any SAE alteration, CP Buffer, Data Store

Command

DBTSP: TAB=SAACTIONS;

If printout shows blocks whose size has to be increased, please escalate to 1st level Support.



2009-04-14

2.9 Check SNT status

Command

NTSTP: SNT=ALL;

All SNT status should be in WO. Escalate to 1st level support if status is ABL.

2.10 Check AP-CP communication

Command

APAMP;

2.11 Check and print any disturbances in the RP.

Command

DIRRP:RP=ALL;

EXRPP:RP=ALL;

All RPs should be in WO state. Escalate to 1st level support if status is ABL.

2.12 Check Signaling links for Connected RBSC.

C7LTP:LS=ALL;

Status should be ACTIVE, escalate if status other than Active.

2.13 check C7 Over IP links

Command

IHSTP: IPPORT=ALL;

All ports should show BUSY state.

IHALP: EPID=ALL;

All associations should have ACTIVE status

M3ASP;

Printout should show ACT state for all M3UA associations



2009-04-14

M3RSP: DEST=ALL;

All Destinations should be in AVA state.

Escalate to 1 st level Support if the outputs are not as desired.

2.14 Check APG Status

Command

Aploc

Hostname — should be name of the node which is ACTIVE

Prcstate --- should be ACTIVE

Alist — check for new APG alarms. report to 1st level Support

Cluster node --- Both nodes should be UP

Cluster group -- All groups should be UP

Cluster res — All resources should be ONLINE state

Cluster netint --- All IP connections should be UP

Cluster res |findstr –ive online — report if this command gives any printout.

2.15 Check network synchronization data

NSSTP;

Escalate to 1st level support if status of clock is other than EX/SB.

NSDAP;

Note down deviations and inform 1st level.



2009-04-14

2.16 PRINTOUT CELL RESOURCES

Command:

RLCRP: CELL=ALL;

RLCRP: CELL=ALL, DETAIL;

If cell site is down,

Check the status of DIP

DTSTP:DIP=<dip>;.

DIP state is either WO (working) or MBL (manually blocked) or ABL (automatically blocked).

DTBLI: DIP=<DIP NAME>; DTBLE: DIP=<DIP NAME>; Above commands are to block or deblock the dip.

If still the DIP Status is ABL, escalate to Transmission Team.

If DIP is WO and the site is down and alarm is still “OML FAULT” and try with

softreload to the TG.

1. Blocking a TG RXBLI: MO=RXOTG-<TG No.>, SUBORD, FORCE; 2. Out of service RXESE: MO= RXOTG-<TG No.>, SUBORD;

3. In service RXESI: MO= RXOTG-<TG No.>, SUBORD;

4. Deblocking of TGRXBLE: MO= RXOTG-<TG No.>, SUBORD;

If still site fails to come up check the alarm, might be TRX are in Local mode contact FLM.



2009-04-14

2.16.1 PRINTOUT RADIO X-CEIVER ADMINISTRATION MANAGED

OBJECT DATA

Command:

RXMOP: MOTY=RXOTG;RXMOP: MOTY=RXOTRX;

2.16.2 PRINTOUT RADIO X-CEIVER ADMINISTRATION MANAGED

OBJECT STATUS

Command:

For : BTS

RXMSP:MOTY=RXOTG;

RXMSP:MOTY=RXOTRX;

RXMSP:MOTY=RXOCF;

RXMSP:MOTY=RXOTF;

RXMSP:MOTY=RXOTX;

RXMSP:MOTY=RXORX;

RXMSP:MOTY=RXOTS;

2.16 RXTCP:MOTY=RXOTG,CELL=<CELL NAME>; RXMFP: MO=RXOCF-<TG no.>; Help to get internal alarms of a cell, relating to system fault. Eg:- 2A:8 = VSWR 2A:33 = Rx. Diversity fault 2B:10 = site on battery 2A:41 = lost communication to TRX 2A:42 = lost communication to ECU

Refer to BTS Alex for BTS fault code list for detailed description of the faults and the for remedial actions.



2009-04-14

TG no. specifies TRANSRECEIVER GROUP NUMBER, of a particular cell’s DXU. The DXU is heart of BTS and all the software related to a cell/site are Loaded into this unit.

2.16.1 RLCRP: CELL=<CELL NAME>;

Check ICM band, ICM (Inter Cell Measurement) that gives interference with neighbouring cells.ICM band up to value 3 is acceptable but 4 & 5 is considered critical.ICM is can be controlled by supervising TRX of cell, as follows:-

1. Check ICM2. Block TRX of that cell3. Check ICM band again4. If ICM less than previous ICM then keep DRU blocked else try for next DRX.5. If ICM band is still high even after DRU Block / Deblock, escalate to 1st level support.

Documents

BSC O&M_NMC