bsc guidelines for vms omc version2 0

BSC O&M Guidelines

BSC O&M Guidelines

BSC O&M Guidelines

Content

BSC O&M Guidelines .................................................................................................... 1

Content ........................................................................................................................... 2

1. General Information about BSC ............................................................................ 3

1.1 Required software ............................................................................................ 3

1.2 NetAct links ..................................................................................................... 3

2. Alarm Monitoring .................................................................................................. 3

2.1 Alarm Monitoring via NetAct ......................................................................... 4

2.2 Monitoring alarms directly from OMU via TANG ......................................... 6

3. Display working status of Cards/Units & In/Out devices .................................... 9

3.1. Display status of Cards/Units ......................................................................... 9

3.2. Display status of In/Out devices ................................................................... 12

4. Software Packages in BSC ................................................................................... 14

4.1 Display BSC software package with MML Command ................................. 14

4.2 Display BSC software package with FTT ..................................................... 15

5. BSC Backup ......................................................................................................... 16

5.1 Fallback copying of BSC software package .................................................. 16

5.2 Safe copy of running software package to USB drive................................... 18

5.3. Command Calendar ...................................................................................... 19

6. Check Memory Disk Space and Signalling status ............................................... 22

6.1 Check Memory status .................................................................................... 22

6.2 Check Signalling links status ......................................................................... 23

7. Monitoring BSC/BTS KPI with Reporting Suite ................................................ 24

8. Some useful NSN Commands for O&M ............................................................. 27

BSC O&M Guidelines

1. General Information about BSC

Currently at VMS C6, we have 6 BSCs. BSC Name, ID and OMU IP are shown as table

below:

BSC Name BSC ID OMU IP

BDNBH1N 437114 10.22.16.228

BDNLT1N 437107 10.22.18.228

BDNNT1N 437124 10.22.20.228

BDNTB1N 437104 10.22.22.228

BVTBR1N 437112 10.22.34.228

BVTVT1N 437116 10.22.32.228

1.1 Required Softwares:

To work effectively in alarm monitoring and troubleshooting at O&M, we need some

software to help in our daily work. Those softwares includes:

- Tang, putty, reflection... etc for Telnet connection to OMU

- 2G BTS Manager to remote log in to each BCF and verify, change configurations

- FTT to log in and view BSC softwares, folders and files

1.2 NetAct links:

https://rclogin.r06.netact.vms.com.vn/netact/login.html

https://rclogin.r06.netact.vms.com.vn/CertGenWeb/getCAInit.do

https://rclogin.r06.netact.vms.com.vn/client_sw

2. Alarm Monitoring

Alarms in BSC should be monitored continuously in order to timely identify faults or

network problems. Then, we can quickly analyze and clear alarms to recover the system. Shift

engineers can use 1 among 2 options below (or combine both of them) to monitor alarms:

- Option 1: Monitoring Alarms via NetAct

- Option 2: Monitoring alarms directly from OMU (via TANG software)


https://rclogin.r06.netact.vms.com.vn/CertGenWeb/getCAInit.do

https://rclogin.r06.netact.vms.com.vn/client_sw

BSC O&M Guidelines

2.1 Alarm Monitoring via NetAct

- Firstly, we access to NetAct via link below:


- Then, provide ID & PW and go to NetAct > Monitoring > Alarm Monitor

- NetAct classifies Alarm Windows into 3 groups: Major, Medium and Minor


BSC O&M Guidelines

- We can choose to Monitor BSC Alarms only. To do that, we follow steps below:

Alarm Monitor > Configuration > Monitoring Criteria >

- To monitor all alarms with NE list in Managed Object, we choose Object Class / Alarm

Number as in picture below:

BSC O&M Guidelines

- To monitor some specific alarms only, we add some alarm numbers into the list as

picture below:

2.2 Monitoring alarms directly from OMU via TANG

- Alarms in BSC can be printed out in only 1 format. There is no Long and Short format

as alarms of RNC.

- Alarm structure is as 2 pictures below:

BSC O&M Guidelines

BSC O&M Guidelines

- In order to see alarms via OMU, we follow steps as below:

Step 1: Connect Telnet to OMU of BSCs (OMU IP of BSCs are shown in content 1.General

Information about BSC )

Step 2: use MML Commands below

View BTS active alarms with command ZEOL

< ZEOL; # view all Active BTS alarms.

< ZEOL::CLS=AL3; # view all Active BTS alarms with alarm type Critical.

< ZEOL:25::; # view all Active BTS alarms of site having BCF ID=25

< ZEOL::NR=7401; # view all Active BTS alarms with Alarm Number=7401

BSC O&M Guidelines

Use command ZEOH to view BTS alarm history:

< ZEOH:2011-12-13,::; # view BTS Alarm History from 2011-12-13 to time of

Command execution

< ZEOH:2011-11-14,:BCF=12,; # view BTS Alarm History from 2011-12-14 to time

of Command execution for BCF ID = 12;

Use Command ZAHO to view BSC Active alarms:

< ZAHO; # view all Active BSC alarms

Use Command ZAHP to view BSC alarm history:

< ZAHP:::2011-12-11,12-00-00; # view BSC Alarm History from date 2011-12-

11, time 12-00-00 until time of Command execution.

< ZAHP:OMU::2011-12-14; # view BSC Alarm History related to unit OMU from

date 2011-12-14 until time of Command execution.

3. Display working status of Cards/Units & In/Out devices:

3.1 Display status of Cards/Units

- All Cards/Units have following Main States: working, spare, blocked, test, separated and

transition. More detail, please see picture below:

BSC O&M Guidelines

- In each States of units, we have Sub states: executing, restarting, updating, idle, out of

use, and no hardware:

- Combining Main states and Sub states of units, we have the following:

BSC O&M Guidelines

- When we need to change (replace) or diagnostic one card, or unit, we must follow

procedures below for safety purpose:

- To show working status of units, we use Command ZUSI

< ZUSI:COMP; # show current status of all Computer units

BSC O&M Guidelines

< ZUSI:ET; # show current status of all ET units

3.2 Display Status of In/Out devices

- To view working status of I/O devices, we use command ZISI

< ZISI:WDU; # show current status of Hard Disks (WDU – Winchester Disk Unit)

BSC O&M Guidelines

< ZISI:ALL; # show current status of all I/O devices

Notes:

- WDU - Winchester Disk Unit (Hard Disk)

- FDU - Floppy Disk Unit

- VPP - Virtual Printer Protocol

- VTP - Virtual Terminal Protocol

- VDS - Virtual Data Storage

BSC O&M Guidelines

4. Software Packages in BSC

4.1 Display BSC software packages with MML Command

BSC has many software packages. Software packages with DEF=Y is software package

which is controlling the BSC (BSC is running on this software package). In picture below,

BSC is running on package with name SF0111PP and its STATUS=BU.

To show software packages in BSC, we use command: ZWQO:CR;

Note:

- SF0111PP means software version of BSC is S15 CD1.1-1

BSC O&M Guidelines

4.2 Display BSC software package with FTT

There is another option to display and browse BSC software package, folders in BSC and

its file system. That is, we use FTT Software. Its function is similar to other normal FTP

software. The different is NSN BSC supports FTT while not supporting other normal FTP

software. For better understanding on the software, please see picture below:

Note: FTT is NSN Proprietary software.

BSC O&M Guidelines

5. BSC Backup

BSC Backup should be done frequently to ensure BSC stability and to prepare for quick

recovery from any unexpected EMCY situation might happens. BSC Backup can be done in

several ways: make a Fallback copy (safe copy) of current stable running software package to

BSC hard disk, make a Fallback copy to USB thumb drive, or create Command Calendar

(routine schedule) for BSC to make Fallback copy at any wanted period of time…etc.

5.1 Fallback copying of BSC software package

Before making a safe copy, we should verify and confirm that current running package is

stable with no error. To verify software package, we use command ZWQB

After confirming current running package is stable, we can start to make a safe copy of

current running package (make a Fallback) by using command: ZWKS

< ZWKS:MODE=FULL,DIRE=FB161211,NAME=FB161211:;

# make a Fallback copy of current running package in Full Mode to Directory name

FB161211 with Software package name FB161211

BSC O&M Guidelines

While BSC is creating a Fallback copy, we can display current copying status of software

package with command ZWKI

After copying finished, we can re-confirm Fallback copy has been done correctly with

command ZWQO:CR;

Note: making a Fallback copy of the current running safe package should always be done

before any important tasks that make changes to BSC configurations.

BSC O&M Guidelines

5.2 Safe copy of running software package to USB drive

Option 1: we can use FTT software to copy software package from BSC to Local Drive or

USB drive. In image shown below, left hand side is BSC folders and files, right hand side is

Local computer folders and files:

Option 2: we can copy Software Package from BSC to USB drive by MML Command. To do

this, first plug in the USB drive to BSC and follow the steps as below:

Step 1: copy software package to USB with command ZIPS

< ZIPS:"OMU",WDU-0,FB161211,*.*,:,UMS-0,,,:::; # Copy Fallback

package with name FB161211 from OMU Hard Disk of BSC to USB drive 0.

Step 2: After copying started, we can view the copying status with command ZIPI

< ZIPI:NAME=<copy task name>;

BSC O&M Guidelines

Step 3: If there is some errors in the copying process, we can view them in details with

command ZIPP

< ZIPP:NAME=<copy task name>;

Step 4: If the previous copy is failed, we must repeat the copying tasks again with command

ZIPS

< ZIPS:"OMU",WDU-0,FB161211,*.*,:,UMS-0,,,:::;

5.3 Command Calender

We can use Command Calendar to make the BSC to run any MML Commands at

specific times in rountines such as: weekly, every 2 days, daily…etc. Command Calendar is

often used to schedule the BSC to make Fallback to copy with specific routines. To check FB

copy via Command Calendar schedule, please follow steps as below:

Step 1: display the content of Command Calendar with command: ZICL

Step 2: Check latest Date and Time of Fallback copy with command ZWKP

< ZWKP:FULL:EMODE;

BSC O&M Guidelines

Step 3: Check status of Fallback package with date and time in Step 2 with command ZAHP

< ZAHP::NR=27,:2011-12-13,::;

The Fallback package is OK if 2 status STARTED and READY appear after the Command

above.

Step 4: Check alarm number 2393 and 2394

Alarm 2393: FALLBACK COPYING TERMINATED IN ERROR

Alarm 2394: ERROR IN FINISHING FALLBACK COPYING

Ensure that these two alarms are not appeared. To check these use following commands:

< ZAHP::NR=2393;

< ZAHP::NR=2394;

BSC O&M Guidelines

Step 5: Finally, we should verify the FB copy again to ensure there is no error.

< ZWQB:STAT=FB:FORM=FAILED;

Note: If there is Work Around Update (WAU) installed on top of the standard package. The

above command will produces error result. Please check the result clearly. In most cases, error

output is normal.

BSC O&M Guidelines

6. Check Memory Disk Space and Signalling status

6.1 Check Memory Status

We can check BSC memory status (total Disk space and Free space in MB and

percentage) by using command ZIWX. In picture below total disk space is 140272MB

(~137GB), free space is 128022 MB (~125MB, 91%). O&M engineers should check BSC disk

space frequently. And when free space percentage is low, some unnecessary files in BSC

should be cleaned up.

BSC O&M Guidelines

6.2 Check Signaling Links Status

We can check BSC signaling links status (SS7, A-interface links connecting BSC to

MSC) by using command ZNET or ZNEL. Status AV-EX means Available-Executing, that is

links are working properly. Otherwise, if we see status UA-INS or the similar, then it means

links are down. In picture below, we have both links working properly, one link being handled

by TCSM-1089, another link handled by TCSM-1088.

BSC O&M Guidelines

7. Monitoring BSC/BTS KPI with Reporting Suite

We can extract Network KPI with function Reporting Suite in NetAct. To extract KPI

reports, please following steps as below:

Step 1: Go to NetAct > Reporting > Reporting Suite

Step 2: Provide ID and Password. Then go to Default Report > Choose BSC Report > then

Choose Sub Report that we need such as: Traffic, Drop call, GPRS…etc.

BSC O&M Guidelines

Step 3: Choose Source Report, Time Filtering, Object Filtering, NE, Report level, Time

level…etc. Then press Generate button. Please refer picture below:

- Wait for a while and we will have a table of reports similar as below:

BSC O&M Guidelines

Step 4: If we want to save report to Excel or CSV format for further analyze of KPI, please

click on Export File as picture below. Then put a name, choose file extension and save it to

Local hard disk.

BSC O&M Guidelines

8. Some useful MML Commands for O&M:

Table below lists MML Commands that are most frequently used in daily O&M tasks of

BSC/BTS with their description:

No. MML

Command

Comma

nd Level Description of Command

1 ZAHO BSC View Active Alarms in BSC

2 ZAHP BSC View History Alarms in BSC

3 ZDSD TRX Delete LAPD

4 ZDSE TRX Create LAPD

5 ZDTC TRX Lock/Unlock LAPD

6 ZDTI ET view LAPD config/status on E1

7 ZDSB ET view LAPD config/status on E1 in details

8 ZEEI BTS view site config/status, site working, block, having traffic…etc

9 ZEFC BCF Create BCF (Site)

10 ZEFD BCF Delete BCF

11 ZEFS BCF Lock/Unlock BCF

12 ZEFE BSC Change BCF parameters

13 ZEFO BSC View BCF parameters

14 ZEOL BCF View Active Alarms of BCF

15 ZEOH BCF View History Alarms of BCF

16 ZEOR BCF Cancel Alarms of Bcf

17 ZEQC BTS Create BTS (Cell)

18 ZEQA BTS Change radio parameter of BTS

19 ZEQE BTS Change hopping parameter of BTS\

20 ZEQD BTS Delete BTS

21 ZEQM BTS Modify parameters of BTS

22 ZEQA BTS Modify parameters of BTS

23 ZEQO BTS Output BTS information including GPRS, EDGE, MNC…etc

24 ZEQS BTS Lock/Unlock BTS

25 ZEQV BTS Modify GPRS parameters of BTS

26 ZESM BSC Change BCSU controlling GPRS

27 ZESI BSC Check DAP information

28 ZEUG TRX Change Power paramater of TRX

29 ZERC TRX Create TRX

30 ZERD TRX Delete TRX

31 ZERO TRX Output TRX configurations

32 ZERM TRX Modify TRX configurations

BSC O&M Guidelines

No. MML

Command

Comma

nd Level Description of Command

33 ZERS TRX Lock/Unlock TRX

34 ZNEL BSC View SC7 links status

35 ZUSI BSC Output Cards/Units status in BSC

36 ZISI BSC Output I/O devices in BSC

37 ZYEF ET Output ET-PCM status

38 ZYMO ET Output BER on PCM

39 ZQNI BSC Output BSC information, including BSC ID

40 ZWGO BSC Output Link Set information

41 ZRCI BSC Output Circuit Group information

42 ZCEL BSC View details circuit state including number of calls in BSC

43 ZEEL BSC View Full Rate, Half Rate calls, GPRS time slots in BSC

44 ZIGO BSC View history of MML commands executed in BSC

45 ZIAI BSC View information of User ID and Profiles

46 ZW7I BSC View Licenses Information

NOTE: more useful and complicated MML Commands can be found in NED (NSN Electronic

Documents)

BSC O&M Guidelines

Version: 2.0

Date: 18/DEC/2011

bsc guidelines for vms omc version2 0

Documents

bsc backup

display bsc software

content bsc om guidelines

bsc id omu ip bdnbh1n

display status of cardsunits

signalling status

software packages

alarm monitoring