O&M Handbook for Ericsson RAN
Released by BSNL
O&M Handbook for CMTS Networks on
Ericsson Technologies
(BSNL Internal Circulation Only)
1st Edition (May 2016)
Message
Anupam Shrivastava
Chairman and Managing Director BSNL Board
I am happy to note that Consumer Mobility vertical has taken an initiative to provide a comprehensive, OEM technology wise, ‘Operations & Maintenance Handbook’ for routine operation and maintenance. In this series, this handbook on Ericsson will be extremely beneficial for use by our Technicians and Engineers in 17 Circles of North and East Zones.
I feel that such a Ready compilation of day to day O & M activities, being followed in the 17 circles,
at one place will go a long way in helping our field units to learn from good practices being followed in other circles.
I congratulate Director (CM) Shri R. K. Mittal and his team for this great initiative and efforts. I am looking forward for release of such O&M Handbooks for other technologies.
07.05.2016
(Anupam Shrivastava)
Message R. K. Mittal
Director (CM) BSNL Board
I am very glad to see that the Handbook on CMTS Operation and Maintenance for Ericsson
technology has been made first time in BSNL. Availability of this comprehensive Handbook with
the field engineers and technicians for carrying out day to day operation and maintenance activities is of paramount importance.
I am sure that this Handbook will help and encourage operation and maintenance personals for
constant monitoring and taking immediate remedial actions through OMC-R & OMC-S for improving QoS parameters. This Handbook will help to solve problems related to: handover
issues; call drop issues; SDCCH/TCH congestion; SDCCH/TCH blocking; VSWR issues; call setup success rate; etc.
Basic guidelines also on conducting Drive Test, Optimisation, etc has been provided for field
personal who will immediately be able to start drive testing and RF optimisation activities. This Handbook is only the beginning and suggestions for improvement may be sent by email to
[email protected]
I thank Dr Biswajit Paul SrGM/CM Orissa Circle and other officers of East Zone Circles for their hard work and sincere efforts to bring out this much desired Handbook. I also thank Shri Shyam
Narain, Dr S K Samanta, Shri Kishore Bhagtani, and other officers of BSNL CO for their valuable contribution.
07.05.2016
(R. K. Mittal)
Preface
A comprehensive handbook for O&M activities to be undertaken by the field engineers and technicians is one of the most critical pieces of document and is required in hand for smooth maintenance as well as speedy resolution of various issues. There has always been a need of one
comprehensive book for resolving most of the day to day issues faced by network engineers and technicians in the field.
This handbook is a result of an idea initiated by Shri R K Mittal, DIR (CM) BSNL Board and translated by teams of experienced officers of various levels both at BSNL Corporate Office and in
the Circles. The final version is compiled by Dr S K Samanta AddlGM (NWO-CM) and Shri Kishore
Bhagtani DGM (NWO-CM) BSNL Corporate Office under the guidance of SrGM (NWO-CM) BSNL CO and Dir (CM) BSNL Board.
This Handbook will not only help the existing officers, engineers and technicians in SSAs and
circle offices, but will be very much useful to those new personnel, who will be posted for day to
day operation and maintenance activities for CMTS networks of Ericsson Technologies in the coming days.
Acknowledgements
Following officers of East Zone actively contributed for the preparation of this handbook under the guidance of Dr Biswajit Paul, Sr GM (NWO-CM) Orissa Circle Orissa Circle Gurudas Meher, GM CM, BSNL Odisha (Contact 94371-77700,
[email protected] ) BC Panda, DGM Core NW, BSNL Odisha (Contact 94370-82555,
[email protected])
PK Sahoo, SDE MSC Cuttack, BSNL Odisha (Contact 94370-55400,
[email protected] )
Prabir Sahoo, SDE RF, Rourkela, BSNL Odisha (Contact 94370-14200,
[email protected]) Calcutta Telecom District Debjit Saha, DE RF, BSNL Kolkata (Contact 94330-00419,
[email protected] ) Assam Circle Raju Sutradhar, JTO CMTS, BSNL Assam (Contact 94350-25262,
[email protected] ) M/s Ericsson Ramesh Chandra Dimri of M/s EIL has provided valuable suggestions for simple explanation on the technical issues.
INDEX Sl. No
Topic
Page No
1.
Introduction
2.1.
BTS Function and Block Diagram
12
2.2.1.
General Inspection of BTS
14
2.2.3.
Quarterly Routines
16
Annually Routines
17
BTS Fault Monitoring, Alert and Rectification Mechanism
17
Fault Alert Mechanism
18
2.
2.2.
2.2.2. 2.2.4. 2.2.5.
BTS
BTS Preventive Maintenance
Monthly Routines
Half-yearly Routines
2.2.6.
Logs and Records
2.3.1.
Fault Monitoring
2.3.3.
Fault Rectification Mechanism
2.3.
2.3.2. 2.4.
17
17
17
18
23
QoS of Radio Network – 2G
33
OMT Software
3.2.
16
Health Ckeckup & Maintenance
2.4.3. 3.1.
14
18
Winfiol
3.
12
BTS Health checkup & Routine Maintenance
2.4.1. 2.4.2.
9
Report Analysis
18
32 33
Improvement of 2G Data Services
37
4.
BSC
46
4.2.
BSC Hardware
47
3.3. 4.1. 4.3.
Case Study
BSC Function
BSC Preventive Maintenance
39 46
50
4.4.
BSC Fault Monitoring, Alert and Rectification Mechanism
51
4.5.1.
Daily Health Checkup
52
4.5.3.
Monthly O&M Routine
72
5.1.
Node B Hardware Description
76
5.2.1.
General Inspection of Node-B
86
5.2.3.
Quarterly Routine
87
4.5.
4.5.2. 5.
5.2.
5.2.2. 5.2.4. 5.2.5. 5.2.6. 5.3.
BSC Health Checkup & Routine Maintenance Weekly O&M Routine
3G Radio Network
Node B Preventive Maintenance
Monthly Routine
Half Yearly Routine Annual Routine Log & Records
52
70
76 86
87
88
88
89
Node B Fault Monitoring, Alert & Rectification Mechanism
89
6.
RNC
96
6.2.
RNC Hardware
5.4. 6.1. 6.3.
Node B Health checkup & Routine Maintenance RNC Function
90
96
102
RNC Health Checkup & Routine Maintenance
106
7.
QoS of Radio Network – 3G
128
8.1.
Purpose of Drive Test
140
Where to Undertake Drive Test
140
6.4. 8.
8.2. 8.3. 8.4. 8.5. 8.6.
Alarm & Analysis
Drive Test
When to Undertake Drive Test Route Plan
Drive Test Tools
Data Measurements
119
140
140 141
141
142
8.7.
Log File & Export
145
9.
Management Reports
155
9.2.
On Monthly Basis
155
9.1. 9.3.
On Daily Basis
Sample Management Report
156
Radio Network Optimization
162
10.
BTS Inspection
12.
Event based Recording for Efficient Optimisation of 3G RAN
13.1.
Minilink Hardware
13.3.
Fault Management
11.
13.
13.2. 14.
155
158
179
Minilink Operation & Maintenance
184
MSM Program
188
MPBN Monitoring
184
189
196
14.1.
Port Status
14.3.
Temperature measurement in MPBN Router & Switch
197
Exchange Data Backup Procedure
207
14.2. 15. 16. 17.
Error Counter Check & Reset
Frequently Asked Questions Daily Health Check Tracker
196
196
200
208
1. Introduction
A mobile network consists of: a) a access part - Base Station Subsystem (BSS); and b) a core part - Network Subsystem (NSS). BSS Networks consists of: Base Transceiver Stations (BTS) and Base Station Controller (BSC). NSS Networks consists of: Mobile Switching
Centre (MSC), Home Location Register (HLR), Visitor Location Register (VLR), IN and Billing & Customer Care Systems (B&CCS).
IN/Billing MS
BSC
BTS
BTS
BTS
MS
BSC
HLR/AuC/EIR
MSC VLR
GMSC
PCU BSC
1.1. BSS Networks
SMSC/MMSC
SGSN
Router GGSN
Other Networks (PSTN, Mobile & Data Networks) Packet Handling Nodes Internet
The main components of BSS networks consists of two parts: i) Radio - BTS, BTS-BSC links, BSC and ii) Infra - Tower, Diesel Generator (DG), Air Conditioners (AC) or Free Cooling System (FCS), -48 Volt Battery and Power Plant. BTS to BSC links are either provided through OFC networks (i.e. CPE, ADM. MADM, etc) or through Digital Microwave (i.e. Mini Link).
Schematic Diagram of a BSS
9
1.2. Base Transceiver Stations (BTS): BTS or access nodes provides connection to a user through a wireless local loop, with authorisation for access and call managed by HLR, VLR,
IN and B&CCS. The wireless loop is only used when a call is in progress and is shared among the BTS users served in a geographical area; this typically covers a radius up to 20km
(if there is no obstruction e.g tall buildings). The traffic from several BTS’s is multiplexed at
the Base Station Controller (BSC) which relays to the Mobile Switching Centre (MSC) thus providing the connection between users. A BTS is designed according to: minutes of call, number of messages and amount of Data to be provided in a specific time period. Assuming a
BTS is designed to handle 1000 minutes of calls per hour, it could provide 200 users with 5
minutes or alternatively 500 users with 2 minutes of calls. It is clear there can be more users if
the call duration is less. This is not the case in a wire line network where a dedicated connection from the access node is provided for each user. This characteristic of mobile
networks suggests a different strategy be folowed in providing desired Quality of Services (QoS) to Mobile users.
A successful call/connection uses two links for transport of information: 1) originating links:
and 2) terminating links. When both the links of a call are provided by the same BTS it is
defined as intra BTS call otherwise it is called inter BTS call. Both the intra BTS and inter BTS call passes through BSC and is switched at MSC. When a call is terminated in a network managed by a different operator it is routed via a Gateway MSC (GMSC).
Authorisation for access to the mobile network to a user is done by allocating a unique mobile
number against the subscribers’ Service Identity Module (SIM) and creating a matching data
base in the HLR. The Mobile Equipment (ME) with the SIM inserted in it is generally called the Mobile Station (MS) and communicates to HLR through BTS, BSC and MSC to get access to the network.
Components such as the BTS, BSC and their interconnections are used for the transport of all services, whereas components like MSC and links between BSC-MSC and MSC-GMSC are
only used for voice and low speed Data such as the Short Message Service (SMS). For
message services like SMS and Multimedia Message Services (MMS) additional nodes such
as Short Message Service Centre (SMSC) and Multimedia Message Service Centre (MMSC) are used to store and forward the message.
10
Traffic such as a voice call is carried through a Traffic Channel (TCH) which transports
information usually measured in kbps (kilo bits per second). For a full rate voice call each TCH carries 12.2 kbps whereas the Data rate per TCH can be up to 59.2 kbps depending on
the modulation scheme and technology e.g. GPRS or EDGE. A BTS configured with 4
carriers per sector i.e. total 96 channels is generally connected to a BSC with a 2 Mbps (Millions of bits per second) link i.e. 1E1. This 2Mbps is not sufficient for high Data usage customers in urban areas and therefore 2 nos of 2Mbps links i.e. 2E1 per BTS to BSC is required.
Smart Phone users heavily uses Data services such as e-mail, browsing, download and audio/video streaming and these services do not use elements such as the MSC and BSCMSC links. Technologies such as General Packet Radio Service (GPRS), Enhanced Data rates for GSM Evolution (EDGE), third Generation (3G) and forth Generation (4G) are generally
employed for these Data services. It uses Packet Handling Nodes (PHN) such as Packet Controller Units (PCU), Serving GPRS Support Nodes (SGSN), Gateway GPRS Support
Nodes (GGSN) and Routers in place of MSCs. The resources of BTS, BSC and interconnected links are used to update the location by each active mobile set even in the idle
state. The volume of such traffic is small but adequate no of communication channels need to be defined.
The authorisation to access a mobile network is controlled by elements such as the HLR, the
Authentication Centre (AuC), the Equipment Identity Register (EIR), the VLR and IN/B&CCS. HLR, AuC and EIR is normally configured in the same hardware and in general there are two systems (1 + 1) for each geographical area ( circle ) for redundancy purposes.
An HLR can provide access to the tune of 10.0 million subscribers and can be connected to
more than one MSC. Each MSC is paired with a VLR which temporarily stores the data for the customers who visits the area under the radio coverage of the BTSs connected to the MSC.
11
2. BTS
2.1BTS Function and Block Diagram. There are 2 models of 2G BTS of Ericsson mainly in operation in BSNL: A- RBS 2206; and B - RBS 2964. BTS Type RBS 2202 supplied in Phase I, will be replaced soon, and therefore, not included in this handbook.
A. RBS 2206: RBS 2206 consists of five main units: DXU; TRU; CDU; CXU; and IDM. Picture of a sample RBS 2206 is given below.
DISTRIBUTION SWITCH UNIT (DXU)
The Distribution Switch Unit (DXU) is the RBS central control unit. There is one DXU per RBS. It provides a system interface by cross connecting 2Mbit/s transport network and individual time slots to their associated transceivers. TRANSCEIVER UNIT (TRU) It is a transmitter/receiver and signal processing unit which broadcasts and receives the radio frequency signals that are passed to and from the mobile station. Each TRU handles 8 airtime slots (i.e. TCH). COMBINING AND DISTRIBUTION UNIT (CDU) A combiner is a device, at the base station, that allows connection of several transmitters to one antenna. It allows each transmitter’s RF energy out to the antenna, while blocking the RF energy from the other transmitters utilizing the same antenna. There are two types of combiners: Hybrid Filter 12
Configuration Switch Unit (CXU) The Configuration Switch Unit (CXU) distributes the Receiver (RX) signals from the Combining and Distribution Unit (CDU) to the double Transceiver Unit (DTRU) within the same RBS. • • • •
• • • • • • • • • •
Internal Distribution Module (IDM) Supplies +24DC to the system Has fuses and breakers for protection Has +24V DC filter for battery connections The main units in the power and climate system are: Power Supply Unit (PSU) Provide +24V DC to the system Available in two versions. PSU AC for 200~250VAC (Rectifier). PSU DC for -48V system. (Converter dc to dc). Number of units 0-3. Additional units required to reduce battery charging times. AC Connection Unit (ACCU) DC Connection Unit (DCCU) Fans controlled by Fan Control Units (FCU) Climate sensors, i.e. temperature and humidity sensors LOCAL BUS The local bus offers internal communication between the DXU, TRUs and ECU. Examples of information sent on this bus are TRX Signalling, speech and data. TIMING BUS The timing bus carries air timing information from the DXU to the TRUs. CDU BUS The CDU Bus connects the CDU to the TRUs and facilitates interface and O&M functions e.g. transfers alarms and RU specific information. IOM BUS This interface consists of three individual I2C ports. It is used to communicate with the CDU, CXU, TMA-CM and cabinet ID.
B. RBS 2964: RBS 2964 consists of PSU; DXU; DRU; and IDM . Picture of a sample RBS 2964 is given below.
13
• • • • • •
Dual Radio Unit (DRU) Consists of 2 GSM TRX Hybrid combiner 2 TX filter 2 duplex filters 2 bias injectors Number of units 1-6(12 TRX)
• • • • • • • • • • •
Y-Links Replaces Timing Bus, Local Bus and X Bus New point-to-point interface between DXU & TRUs Based on LVDS,( Low Voltage Differential Signalling) interface Backplane connector on DXU with compatibilityof 2102/2202 cabinets Each DRU has two Y links (one for each transciver) Each Y link is divided into two interfaces: Y1: TX control data TX burst data (X Bus data) Y2: Traffic data UL & DL O&M Data Timing
2.2
BTS Preventive Maintenance
2.2.1 General Inspection of BTS
Whenever visiting a BTS, check the following points to ensure that everything is in order: 14
Check for any fault in the unit or any other alarms
No visual damage to the equipment or site room is evident
Equipment
The waveguides and connectors are fixed properly
related
The equipement and the place should be kept clean and cleaning
checks
schedule should be maintained sincerely
It should be ensured that all external alarms are extended and are working properly
Air conditioners are functioning correctly. There is no leakage of air-conditioned air through door, window or waveguide openings. Environment
The air inlet / filters to the cabinet are clean
Indoor light is working & Indoor emergency light is working
Check for any surrounding activities or changes close to the site that may affect the performance of the system or safety of the equipment
All modules of SMPS power plant are working properly and load is being shared by all. Battery
/
Power plant / DG
Check back-up batteries for corrosion and leakage.
Check the run time of Engine Alternator and compare it with the
manufacturers’ recommended service interval regarding the run time and ensure regular service.
The oil in the Engine Alternator should be checked with the dipstick to ensure its sufficient level and also its usefulness. Earthing Fire Safety Tower Other
It should be ensured that Earth resistance value has been measured once in every six months and the same is displayed. It should be less than 0.5 ohm.
Expiry date on Fire extinguisher and sufficiency of fire safety equipments.
Check that the navigation light on the tower is operational and condition of tower with regard to its painting etc is OK.
The media connectivity record should be maintained in a database.
2.2.2 Monthly Routines
15
Climate control i.e. air conditioners are functioning correctly. There is no leakage of air-
The air inlet / filters to the cabinet are clean.
conditioned air through door, window or waveguide openings.
The oil in the Engine Alternator should be checked with the dipstick to ensure sufficient level and also its usefulness.
Functioning of all alarms is tested for service worthiness.
Weak cell of batteries to be identified and remedial action should be taken.
Check for logical parameter inconsistencies like Half Rate parameters modified in OMCR but not getting reflected in traffic report in terms of half rate erlang.
Audit of adjacencies and RF parameters like BCCH / BSIC/ HSN. Number of adjacencies should be optimized. It should be monitored whether all defined adjacencies takes traffic or not. Extra neighbours should be removed. Missing neighbours should be added. Cells having
high ratio of handover traffic to cell originating traffic should be studied further for
improvement.
Audit of 2G / 3G adjacencies should be carried with consideration of BCCH / BSIC. Nearby cells having same BCCH / HSN should be identified and modified
2.2.3 Quarterly Routines
The following should be checked once in a quarter in addition to the regular daily and weekly check-ups:-
Check BTS rack filters and replace if necessary.
Carry out battery back-up voltage test, to ascertain whether the batteries are holding their full charge.
Check the site temperature and humidity.
Updation of data in the planning tool based on results of Drive Tests during the quarter.
Cell Planning and RF Planning should be reviewed for any possible error or change in situation due to addition, deletion or change in configuration of BTS in the network.
Any additional BTS should be put in service only after A/T and special monitoring on Call
Success Rate (CSR) in all cells in the BSC is necessary so as to be sure that it is not impacting the performance of any other sector/ cell adversely.
Temperature monitoring
In case of shelter sites: - free cooling filter should be cleaned
In case of outdoor site: - all canopy fans should be in working condition
2.2.4 Half-yearly Routines
16
Power measurement of the BTS should be done.
The waveguides and connectors are fixed properly.
VSWR should be measured once in six months for every BTS and its value should be maintained within the limit ( After opening WinFiol, go to Channel then select new
2> Click Open
3> A notice will come, to activate channel properties.
19
[Note: If you have already created a channel then, right click on the channel, and go to properties.]
Setting Up the Channel Properties: 1> Provide Channel name.
2> Chose protocol type. 20
3> Chose mode.
4> Provide Host name [the IP address of OSS (Operation & Support System) connected to the 2G network]. Provide Port number, Terminal type.
21
5> Check some other parameters:
22
Understanding the Channel window When you open a channel normally two windows are shown, the upper window is the Output window, and the lower one is the Input Window. You can toggle between windows by using Alt+F5. Ericsson Commands 1> Logging into BSC with new channel: Whenever you open the channel that you have just created, will ask for User ID and Password. Login :
Password:
After that you are connected to the OSS.
Now to enter into BSC, run the command: eaw {BSC NAME} [Note BSC name in CAPITAL LETTER]
2.4.2 HEALTH CHECKUP AND MAINTENANCE 1. To check various class of alarms in BSC: ALLIP: ACL=A1; [ACL stands for alarm category, A1 stands for EXTERNAL 23
For example, High room temp, Door open…, A2 stands for INTERNAL. For example, Permanent fault, OML FAULT, Loop Test Fault, Local Mode….Date and Time of all alarms are shown, A3 stands for critical alarm] [To show all type of alarm] ALLIP;
1.1 ACL=A1
1.2 ACL=A2
1.3 ACL=A3
2. To check the status of the sites and cells in the BSC: 24
2.1
RLCRP: CELL=ALL;
BCCH: CBCH: SDCCH: NOOFTCH:
Number of BCCH available for the sector. Number of CBCH available for the sector. Number of SDCCH available for the sector. Number of TCH available for the sector.
[Note: If the sector is down, all values will be 0, 0]
2.2
=CAL875A; RLCRP: CELL=CAL875A;
CHANNEL:
(to check status of all cells)
Type of channel i.e. TCH/BCCH/SDCCH/CBCH. 25
STATE: USE:
3.
State of the channel BUSY/IDLE. Type of service, the channel is being used for, SPEECH/GPRS.
To check whether a cell is Active or Halted RLSTP: CELL={SECTOR ID};
3.1
To Halt or To Active a cell
RLSTC: CELL= {SECTOR ID}, STATE={STATE}; STATE=HALTED/ACTIVE]
26
[Note:
4. To Check the Hardware alarms of a Site RXTCP: MOTY=RXOTG, CELL={SECTOR ID}; [To see the Trunk Group]
RXASP: MO= RXOTG - {TG No.};
[For checking general Alarms]
[Meaning of some alarm: 27
OML FAULT:
Optical and Maintenance Link fail (Normally it indicates media is break.) PERMANENT FAULT: The equipment is permanently down due to some reason. (You can try to block & deblock the equipment, sometimes after blocking/deblocking, equipment starts working) LOCAL MODE: TRU in local mode & sometimes DXU in local Mode Here some alarms can be seen like “BTS EXT UNAFFECTED”, “BTS INT AFFECTED”, “BTS INT UNAFFECTED”. In that case we have to determine the Fault Code to know the exact problem. RXMFP:MO =RXOCF - {XX};
[To know the Fault Code, Class No &
=RXOTRX - {XX};
Replacement Unit No., Problem can be
=RXORX - {XX};
identified by using RBS Fault Decoder]
=RXOTX - {XX};
=RXOTF - {XX}; =RXOTS-{XX}
[ XX=TG No./TRX No./RX No/TF No/TS No.]
28
By putting fault code in “rbs fault decoder” we can know the fault details. Also locally in BTS by connecting “OMT software” we can know. After knowing the fault type i.e. vswr fault/rx diversity /card h/w fault. We shall take necessary action.
5. To Check the DIP(PCM) status of a site RXTCP: MOTY=RXOTG, CELL={SECTOR ID}; RXAPP: MO=RXOTG – {TG NO};
[To determine TG No.]
[To see RBLT]
Observe the first RBLT number: RBLT2 – 10977 Divide the number (10977-1) by 32, get the DIP no 343. DCP=1 to 31: PCM is connected to A port of DXU at BTS. DCP= 287 to 317:PCM is connected to C port of DXU at BTS. DTSTP: DIP={DIP No};[To Check Status of Digital Path]
[Observe STATE here, WO=> Working, ABL=> Automatically Blocked (PCM Fail), MBL => Manually Blocked] 29
6.
To Check the DIP(PCM) transmission quality
DTQUP: DIP= {DIP NO};
[Note: here values of N-ES, N-SES, SLIP, SFV, etc. are all measures of error values of the PCM, large values of which indicate poor performance of the PCM. T1 value is shown in minutes, T2 value is shown in hours]
7. To RESET error in DIP(PCM) DTQSR: DIP= {DIP NO},es,ses; DTQSR: DIP={DIP NO},unacc,degr;
30
8. BASIC MO COMMANDS 8.1
RXTCP: MOTY=RXOTG; (Shows cells connected to TG)
8.2
RXMOP: MOTY=RXOTG;
8.3
RXMOP: MOTY=RXOCF; (Shows TEI value, Signalling & s/w version of CF)
(Shows all TG parameters)
31
RXMOP:MOTY=RXOTF;
(Shows TF mode and SYNC source of site)
RXMOP:MOTY=RXOCON;
(Shows DCP value of CON)
RXMOP:MOTY=RXOTX;
(Shows CELL,Band,ChlGroup,MaxPower of TXs)
RXMOP:MOTY=RXOTRX; RXMSP:MOTY=RXOTRX; RXASP:MOTY=RXOTG;
(Shows TEI,Signalling,CELL,DCP values of TRXs) (Shows the status of TRXs)
(shows the Alarms of TGs)
By using RXMFP command we will also get h/w details of a card i.e. Product code,Sl no, etc.
2.4.3 OMT SOFTWARE:
OMT software is being loaded in Laptop for monitoring of BTS in BTS location.
1. It is very useful at site. It can be used locally to know all the information about site i.e. configuration, alarms etc. Connect->Read IDB
->OMT -> DISPLAY INFORMATION
->Installation DataBase->Display-> Information
2. It is required for any card addition, E1 addition, Cascading, Configuration change, TEI value change, Sector addition/deletion. OPEN OMT->CREATE IDB->CONNECT->MAKE LOCAL DXU->INSTALL IDB-> RESET DXU When a site is not working in spite of no faults, we must check the
A) The TEI value of DXU in BTS by IDB and defined TEI value of CF in BSC. B) The PCM terminated at A port or C port and defined DCP value in BSC. 32
3 QoS of Radio Network – 2G 3.1REPORT ANANLYSIS
Important KPIs (Key performance Indicators) are to be monitored and analyzed on regular basis.
i. ii. iii. iv. v. vi.
Important 2G VOICE KPIs are:
BBH Call/ TCH drop (Should be BBH_Report_Cell_RC5.3_rev1. ( For BBH of Sectors/ Cells) RADIO-->Performance_Overview_BSC
( For Whole day of BSCs)
3.1.1 There are several reasons for poor KPI (Call Drop, TCH Block, SDCCH Block, HSR and CSR). In this handbook, the faults are being explained as follows---SDCCH Block/ Congestion Reasons---
a. Check carried Traffic (Erlang) from BO Report
b. Defining Proper No of SDCCH Channels (Default value:upto 2TRX->SDCCH 1 TS,above 2TRX to 4TRX->SDCCH 2 TS, above 4TRX to 6TRX->SDCCH 3 TS,above 6TRX>SDCCH 4 TS.) (use command RLCCC) c. Dynamic SDCCH may be defined (use command RLACI)
d. Check Hardware Faults and Transmission Alarms (use command RXASP) e. Problem in TRX in which SDCCH is defined etc.
If a cell having SDCCH blocking with less TCH traffic, then increase the SDCCH in that cell. RF TEAM ACTIVITY---
a. Optimize LAC boundary b. BTS Boundary ==Define sufficient SDCCH Channels c. Increase Cell Reselection Hysteresis (crh) to shift the Location Area Border (RLSSC) 33
3.1.2 TCH Block/ Congestion--Reasons---
a. Check carried Traffic (Erlang) from BO Report
b. Check Hardware Faults and Transmission Alarms
c. Check TRX and Time slots Faults—(Idle/ low traffic handling TRX)
d. Power adjustment (BS TX Power max)(in exceptional cases) (using command RLCPC) e. AMRHR may be done (using command RLDHC) f. Lowering of HR triggering thresholds.
g. Directed retry/Traffic Handover may be enabled.( RLLBC: ASSOC= ON)----In BSC, ( RLLOC) In Cell RF TEAM ACTIVITY---
a. Antenna Adjustment for Serving Cell/Neighbour Cells– Increasing Mechanical/Electrical tilt , Lowering Antenna Height , Changing Antenna Azimuth etc. b. Planning for additional Cabinet (1800 band) or increasing TRX/ rearranging the existing configuration.* c. Load sharing in OL/ UL on basis of Path loss Criteria d. Fourth sector may be introduced at the same BTS. e. Last option: Introduction of new BTS
3.1.3 TCH/ Call Drop Reasons
a. Check Hardware Faults and Transmission Alarms (Command RXASP) b. Check Transmission error (Command DTQUP)
c. Due to Interference (ICM Band value should be= paste at Command File of WIN Fiol-> Create Log file (Press F8)->Run all commands(Again Press F8)->close output of log file. Process it through RL DUMP Processor S/W. It will show all the information of h/w all BTSs like TG,CF,TRX,TX,DIP everything in a EXCEL file. Similarly we can process al the RL commands. By which we get the cell parameters all BTSs like CGI, pwr, neighbour, hsn, maio everything in a EXCEL file.
45
4 BSC
4.1 BSC Function
The BSC is connected to the MSC on one side and to the BTS on the other. The BSC
performs the Radio Resource (RR) management for the cells under its control. It assigns and release frequencies and timeslots for all MSs in its own area. The BSC performs the inter-cell handover for MSs moving between BTS in its control. It also re-allocates frequencies to the
BTSs in its area to meet locally heavy demands during peak hours or on special events. The
BSC controls the power transmission of both BSSs and MSs in its area. The minimum power level for a mobile unit is broadcast over the BCCH. The BSC provides the time and frequency synchronization reference signals broadcast by its BTSs. The BSC also measures the time
delay of received MS signals relative to the BTS clock. The BSC provides control of the BTSs and manages radio resources and radio parameters. A single BSC can control a large number of BTS.
The BSC functions are divided into the following sub-functions: Provision of signalling links to the MSC
Signalling control of the BTSs and hence the Mobile Stations Signalling control of the links with the MFS (what is MFS) Switching of traffic between the MSC and the BTSs Routing of traffic between the MFS and the BTSs Provision of O&M facilities.
The basic functions of BSC are Telecommunication functions, Transmission functions, O&M functions
Telecommunication functions:
BTS are responsible to handle physical resources. Logical resources like Radio frequency
management (GSM & GPRS) and TCH management is done by the BSC. Every half second
BTS’s send radio measurements to the BSC. Those measurements are processed by the BSC which is going to take the handover decision in some cases.
Management of GSM radio frequency is also done by BSC. The frequency of various channels like Broadcast and Common control channels, signalling channels are handled by BSC. Radio measurement processing, In Call Modification handling is done by BSC. 46
BSC also handle GSM & GPRS traffic channel resource management like:Establishes and releases radio resources Queues requests
Selects TCH for handovers
4.2 BSC Hardware
Ericsson BSC is build up with AXE 810 architecture. It is more powerful, less space and power dissipating. The hardware components are:
1. 2. 3. 4. 5. 6.
GEM (Generic Ericsson Magazine) Group Switch GS 890 (distributed, non-blocking) CL 890 (new clock modules) On board RP (RPI) ET 155-1 (one board ET 155) APG – 40 An important factor behind the AXE flexibility is the APZ Control System Architecture, which is a two-level architecture including both central and distributed control. It is an approach that ensures high reliability and efficient call handling. APG CP EMG EMRPI EMG
RPs RPB STR
EMRPI STR
Adjunct Processor Group Central Processor Extension Module Group Extension Module Regional Processor Integrated Regional Processor..... RP Bus Signal Terminal Remote TCP/IP Ethernet
RPG
RP
RPP
RPI
RPB CP
47
AP G
RPG
IPN Ether net
CP & RP The Central Processor, CP is duplicated, offering high hardware fault tolerance. In the event of a fault, the control may be swapped to the other side with a minimum or no impact on the traffic handling capability. The Regional Processors, RPs, are used for routine repetitive processing and for processing intensive tasks such as the termination of the lower protocol layers. The most recent regional processors are open processing platforms, on which it is possible to run application software using industry-standard programming languages such as C or C++. The use of high-level languages also presents other opportunities such as substantial Time to Market gains through the incorporation of off-the-shelf standard software modules. RPP is targeted to support data communication related telecommunication applications. RPP offers a range of open hardware interfaces, a range of software applications plus a complete development environment. It work as a PCU (Packet Control Unit)
The PCU is a node in the GSM network. It is designed to provide an interface between the circuit-switched GSM network and the packet-switched GSN nodes. These GSN nodes in turn provide an interface to public packet-switched networks. The hardware consists of 1-7 RPPs and 2 no of EPSs which can be connected together using Ethernet i.e. IP. Each RPP can connect to the SGSN (via the Group Switch when FR is used). For GB over IP EPS card connects SGSN directly through the BSC internal IP Gateways . Each RPP card provides 64 circuits of 64kbps per circuit. If GB over Frame Relay is used 31circuits will be utilized for 2MB connectivity with SGSN and rest 33 circuits will be used for radio access. All the 64 circuits can also be used for radio access if GB over IP is used. In GB over IP configuration the EPS card provide up to 100 mbps bandwidth with SGSN through IP gateway and work in redundancy mode. In this case all the RPP resource will be utilized for radio access. Inter Platform Network An Ethernet based, 100 Mbps or 1 Gbps, Inter Platform Network, IPN, is ringing in an industry standard, high capacity interface into AXE.
A P
Other Systems, e.g. TSP, AXD 301
AP
IPN
CP
48
Generic Ericsson Magazine
Another far-reaching improvement is the GEM, a high-capacity, flexible, and scalable magazine (sub-rack) that anticipates future developments. GEM-based nodes will be smaller, dissipate less power, and have greater maximum capacity. Their implementation will dramatically improve the cost of ownership and cut time-to-customer for AXE. • • • • •
A GEM can house
two SCB-RPs, providing an Ethernet switch, control function, maintenance support, and power distribution; two switch boards (XDB), providing a 16 K plane duplicated group switch; up to 22 device boards with 15 mm spacing, such as ET155, ECP, or TRA; pairs of DLEBs, providing multiplexing functionality for DL3 cable interfaces, placed in device slots; and CL890 clock modules placed in device slots. Transcoder
The Transcoder/Rate Adaptation (TRA) function in BSC/TRC performs transcoding of speech information and rate adaptation of data information. It also contains functions for Discontinuous Transmission (DTX). The capacity in number of channels per board for the different versions of TRA hardware is given below. TRA Version
HW
R5A R5B R6 without TFO R6B R6 with TFO (Tandem Free Operation)
FR
EFR
HR
AMR FR
AMR HR
24 24 24 24 24 24 24 24 24 per device group of any speech codec (n=1..8), 192 in total 24 per device group of any speech codec (n=1..8), 192 in total 124 124 (16 per device (16 group) per device group)
For R5 different codec cannot be mixed on the same board. Each TRA R6/R6B board consists of 8 device groups and each device group can be configured for any of the supported codec. The capacity for TRA R6 differs depending on if the device group is configured to support TFO, in that case a device group can handle 16 channels. Else and for TRA R6B the capacity is 24 channels per device group. One TRA EM consists of one TRA board. The TRA R5 magazine includes (up to) 16 TRABs. TRA R6/R6B is housed in a GEM magazine where it can be mixed with other boards depending on the configuration. All TRA hardware versions can be mixed in the same speech codec pool. Presently we are using CSPB R2 board which work on R6B application. 49
Note that, when there are several pools, it is normally the case that AMR, EFR or HR capable mobiles also support FR. In this case the traffic can be shared between the pools and thus not all of them need to be dimensioned for the same grade of service. This means that congestion in one pool, for example, the EFR pool, does not necessary imply congestion for a call, as another pool, e.g. the FR pool, can be used instead. ET-155 The ET155-1 OC-3 is a single board 155 Mb/s, OC-3, Exchange Terminal supporting ANSI standards for SONET. The ET155-1 OC-3 together with the GEM concept of AXE offers very compact and scalable node solutions for cost efficient connections to the transport network. For the purposes of equipment and network protection, Automatic Protection Switching, APS 1+1, can be provided as an option. For Abis link E1 is required which can be extracted by connecting 2Mb MUX (OMS) with ET155-1. OMS OMS is a MUX which convert one TM to 63 E1. It is a separate equipment and not under AXE environment. For the maintenance of OMS its O&M software to be loaded in Laptop and by connecting the Laptop to OMS’s console the Card configuration and E1 configuration can be done. Sometimes, on power recycle, the E1 configuration of OMS gets corrupted. To rectify this we have to logging into OMS through console and through O&M command reconfiguration can be done. APG 40
The APG40 is a platform for the AXE central processor IO functions (APIO) that were inherited from the IOGs. It is also a platform for billing (for example, FOS) and statistic data collecting (for instance, STS), storage, processing and output from the AXE switch. For example, the APG40 can be a platform for collecting data related to in-service performance from the central processor. It can also format that data for distribution to an operations management.
4.3 BSC Preventive Maintenance
Whenever visiting a BSC, check the following points to ensure that everything is in order: Check for any fault in the unit or any other alarms
Equipment checks
related
No visual damage to the equipment or site room is evident
The equipement and the place should be kept clean and cleaning schedule should be maintained sincerely
It should be ensured that all external alarms are extended and are working properly
Environment
Air conditioners are functioning correctly. There is no leakage of air-conditioned air through door or window. 50
Indoor light is working & Indoor emergency light is working
All modules of SMPS power plant are working properly and load is being shared by all.
Check back-up batteries for corrosion and leakage. Battery
plant / DG
/
Power
Check the run time of Engine Alternator and compare it
with the manufacturers’ recommended service interval regarding the run time and ensure regular service.
The oil in the Engine Alternator should be checked with
the dipstick to ensure its sufficient level and also its usefulness. Earthing Fire Safety Other
4.4
It should be ensured that Earth resistance value has been
measured once in every six months and the same is displayed. It should be less than 0.5 ohm.
Expiry date on Fire extinguisher and sufficiency of fire safety equipments.
The media connectivity record should be maintained in a database.
BSCMonitoring, Alert and Rectification Mechanism
4.4.1 Fault Monitoring
Faults are being continuously monitored on 24 X 7 by NOC / OMCR personnels. As and when any fault occurs in the network it is indicated on OMCR monitor.
4.4.2 Fault Alert mechanism
24X7 NOC / OMCR staff escalates the fault to the concerned persons/ field staff.
Software based automatic alert system is put in place which informs the faults to the concerned staff through SMS
The concerned officer identifies the fault reason like media problem / power supply problem / equipment related problem
51
4.4.3 Fault Rectification Mechanism Reason Fault
of
Action to be taken The section is to be identified and concerned officer is being
Media Power
Equipement related
Enviorment (High
Temperature)
informed for furher rectification.
If the power supply is disconnected, it should be ensured tha Battery is taking load and if required DG set shoud be started.
If there is problem of power plant module, it should be replaced.
Hard reset should be given from the site Faulty cards should be replaced/ Jack-out-Jack-in.
Faulty hardwares should be attended as per the procedure given under BSC healthcheck & Routine Maintenance Check Air condition working
4.5 BSC Health Check & Routine Maintenance.
4.5.1 Daily Health Check 4.5.1.1 Check Alarm Log: Command ALLIP:ALCAT=APZ;
This command displays the all active alarm of control part. Command Output:A2/APZ "B25I18X0150_A.W" 163 151007 1842 RP FAULT RP TYPE 165 RPG3A
This implies RP-165 is faulty. Then attend the RP fault as per RP handling procedure given latter on in this document. 4.5.1.2 Check the Processor Load Command PLLDP;
52
Command Output:-
PROCESSOR LOAD DATA INT PLOAD CALIM OFFDO OFFDI FTCHDO FTCHDI OFFMPH OFFMPL FTCHMPH FTCHMPL 1 3 72000 59 1 59 1 3 57 3 57 2 3 72000 45 11 45 11 1 9 1 9 3 3 72000 53 9 53 9 3 4 3 4 4 3 72000 60 9 60 9 5 9 5 9 5 3 72000 62 10 62 10 3 4 3 4 6 3 72000 54 8 54 8 4 12 4 12 7 2 72000 43 8 43 8 4 5 4 5 8 3 72000 55 8 55 8 9 12 9 12 9 3 72000 56 3 56 3 6 4 6 4
Processor load must be within limits and report if it exceeds 90.
4.5.1.3
Check the CP State
Command DPWSP;
Sample Output:CP STATE MAU SB NRM B
SBSTATE WO
This implies Both CP are in working status with CP-A executive and CP-B in Standby state. If any of the CP is in wrong state then following commands may be used to rectify the same.
4.5.1.4
CP Diagnosis
REPCI;
This command initiates diagnosis of fault in CP. The command results in a printout CP DIAGNOSIS that contains list of suspected boards. Command Output:
CP DIAGNOSIS TESTRESULT Testresult FAULT TYPE Fault type
MAG PCB REPLACED REASON mag pcb [replaced reason] mag pcb [replaced reason] 53
If there is any hardware fault, the PCB name will be displayed under PCB with TESTRESULT as fault. Then replace the faulty board as per the output of following command.
4.5.1.5
Manual Intervention in CP Repair
REMCI:MAG=mag, PCB=pcb; Command Output:-
CP MANUAL INTERVENTION INTERVATION PREPARATION SUCCESSFUL |ACTION MAG PCB NOTE | |action |mag| |pcb| note | The result printout CP MANUAL INTERVENTION indicates if replacement of the board is permitted or not, and give instructions how the replacement should be done. 4.5.1.6 Repair Check in CP After PCB replacement as per previous command the CP repair is to be checked with the following command. RECCI; Command Output:-
CP REPAIR SUCCESSFUL NOT SUCCESSFUL [RP: rp1 rp2 ]
If the TESTRESULT shows successful, the CP has been repaired successfully. Otherwise we have to act as per UNCESSFUL remark (rp-address faulty)
4.5.1.7
Check RP status
EXRPP:RP=ALL:
Command Output:RP DATA
RP STATE TYPE 32 WO RP4S1A 33 WO RP4S1A 34 WO RPPS1 35 WO RPPS1 36 WO RPPS1 37 WO RPPS1
TWIN STATE DS MAINT.STATE 33 WO 248 IDLE 32 WO 248 IDLE IDLE IDLE IDLE IDLE 54
All RPs should be in WO state. If any RP is in ABL status then attend the RP fault as per the following commands.
4.5.1.8
Blocking & De-blocking of RP
BLRPI:RP=rp,forced; BLRPE:RP=rp;
Then check the RP status using EXRPP command. If again the RP status becomes ABL then use the following command to repair the RP.
4.5.1.9
RP Diagnosis
REPRI:RP=rp; Command Output:
RP DIAGNOSIS TESTRESULT testresult
RP EM PCB REPLACED REASON rp [em] pcb [replaced reason] pcb [replaced reason]
If there is any hardware fault, the PCB name will be displayed under PCB with TESTRESULT as fault. Then replace the faulty board as per the output of following command.
4.5.1.10
Manual Intervention in RP Repair
REMRI:RP=rp, PCB=pcb; Command Output:-
RP MANUAL INTERVENTION |RP EM PCB ACTION | |rp |em| |pcb| action | |FAULT INTERRUPT | |fault type |
4.5.1.11
Repair Check in RP
After PCB replacement as per previous command the RP repair is to be checked with the following command. 55
RECRI:RP=rp; Command Output:-
RP REPAIR RP EM TESTRESULT rp [em] testresult If the TESTRESULT shows passed, the RP has been repaired successfully. Otherwise we have to again test the RP by REPRI command.
4.5.1.12
Check that the latest backup file are available in the system
CP backup contains all Exchange database including hardware installed and configured BTS / GB link etc. This data is most important for BSC and in emergency this need to be reloaded to the system. Hence we should check the proper backup regularly. SYBFP: FILE;
Command
Command Output: SYSTEM BACKUP FILES FILE IO RELFSW0 -
EXCHANGE B25I18X0150_A.W
SUBFILE TYPE OUTPUTTIME CURRENT COMMANDLOG R1 DSSMALL 151202 0201 YES R2 DSSMALL 151201 0201 NO R3 DSLARGE 151201 0201 YES 0002639 R4 DSLARGE 151202 0201 NO 0002640 R5 PS,RS 151105 0823 YES FILE IO RELFSW1 -
EXCHANGE B25I18X0150_A.W
SUBFILE TYPE OUTPUTTIME CURRENT COMMANDLOG R1 DSSMALL 151104 0201 NO R2 DSSMALL 151105 0201 YES R3 DSLARGE 151105 0201 NO 0002612 R4 DSLARGE 151104 0201 YES 0002611 R5 PS,RS 151006 0733 YES FILE IO RELFSW2 -
EXCHANGE B25I18X0150_A.W 56
SUBFILE TYPE OUTPUTTIME CURRENT COMMANDLOG R1 DSSMALL 151005 0201 NO R2 DSSMALL 151006 0201 YES R3 DSLARGE 151006 0201 NO 0002581 R4 DSLARGE 151005 0201 YES 0002580 R5 PS,RS 150904 1435 YES END
The latest backup (yesterday date) file should be in RELFSW0 volume. If it is not up-to-date then backup has been halted. Then we will go for manual backup as per the following commands.
a. SYBUE; (to stop automatic backup)
b. SYBUP:FILE=RELFSW2; (to start cp backup in relfsw2 volume)
c. SYTUC; (to rotate latest backup from relfsw2 volume to relfsw0 volume) d. SYBUI:DISC; (to start automatic backup)
4.5.1.13
Check for any software file congestion
Command
DBTSP: Tab=SAACTIONS; Command Output:DATABASE TABLE
BLOCK TAB TABLE SAFTAB1 SAACTIONS
WRAPPED YES
ACTNUM SAE BLOCK TYPE CNTRTYP CURRNI 0 348 GLOBAL CONS2 512 528 NIE NIR STATUS NCONG 16 16 REG 4
NEWNI
This implies there is congestion in SAE-348 whose size to be increase from 512 to 528 using standard procedure as per Alex.
4.5.1.14
Check the status of the C7 Links
Command
C7LTP: LS=ALL; Command Output:-
CCITT7 LINK SET STATE 57
LS 3-10386
SPID SLC STATE INHIBST FCODE INFO ORMGSB1 00 ACTIVE 01 ACTIVE
All links should be active. If any link is not active then the E1 of corresponding link may be faulty. We have to check the E1 status by the DTSTP command. If E1 (dip) is ok, then the status of signalling terminal (ST) card is to be checked by the following commands. C7LDP:LS=3-10386;
CCITT7 LINK SET DATA LS 3-10386
SPID ASP ORMGSB1
SPID
SLC ACL PARMG ST 0 A2 24 C7STAH-1&&-31 1 A2 24 C7STAH-33&&-63
SDL SLI ORMGSB1-0 /C7STAH-1/RALT2-1 ORMGSB1-1 /C7STAH-33/RALT2-4033
EXEMP:RP=ALL,EM=ALL; EM DATA
RP TYPE EM EQM 258 RPPS1 0 C7STAH-0&&-31 482 RPPS1 0 C7STAH-32&&-63
TWIN CNTRL PP STATE PRIM WO PRIM WO.
For problematic link, the state of the EM may be in ABL / CBL state. If it is in ABL state we can reset the card by BLEMI, BLEME command. If it is in CBL state the RP card to be reset by BLRPI, BLRPE command.
4.5.1.15
GDSTP;
Check Group switch status
Command Output:-
DISTRIBUTED GROUP SWITCH STATE UNIT STATE BLSTATE VAR STATUS CLM-0 WO 11 MASTER CLM-1 WO 11 SLAVE UNIT
STATE BLSTATE VAR
UNIT
58
STATE BLSTATE
XM-A-0-0 XM-A-0-1 XM-A-0-2 XM-A-0-3 XM-A-0-4 MUX34-A-0 MUX34-A-1 MUX34-A-8 MUX34-A-9
WO WO WO WO WO WO WO WO WO
1 1 1 1 1
0 0 0 0
XM-B-0-0 WO XM-B-0-1 WO XM-B-0-2 WO XM-B-0-3 WO XM-B-0-4 WO MUX34-B-0 WO MUX34-B-1 WO MUX34-B-8 WO MUX34-B-9 WO
All TSM/SPMs should be in WO status. If any Switch card is in ABL state then attend it with the following command. GDBLI, GDTEI, GDBLE,
4.5.1.15.1 Check network synchronization data GDCVP;
DISTRIBUTED GROUP SWITCH CLM CONTROL VALUE CLM OSCILLATOR CONTRVALUE AVERAGEVALUE CLM-0 0 33706 33706 1 34018 34052 CLM-1 0 31228 31290 1 33853 33886
FAULTCASE
The clock control value should be 32768 with deviation from 31000 to 34000. If the deviation is more it might be due to reference clock failure. Then we have to check the reference clock status and deviation through below command. NSSTP; Command Output:
CLOCK-REFERENCE STATE REF STATE BLS 0ETM2,MS-0 EX 1ETM2,MS-1 SB One of the Clock reference state should be in EX condition. Otherwise, the corresponding TM status to be checked. We may check the SDIP status and error if any, in the RALT device. If TM is ok then reset clock with the following command:- NSBLI, NSTEI, NSBLE. a. NSDAP; Command Output:CLOCK-REFERENCE SUPERVISION DATA 59
AREA OPERATING STATIC DATA REF CLREFINL REFGRP PRI FDL WDL ACL 0ETM2,MS-0 1 1 1 5000 10 A1 1ETM2,MS-1 4 1 2 5000 10 A1 DYNAMIC DATA REF 0ETM2,MS-0 1ETM2,MS-1 END
FD WD 0 0 0 0
The FD and WD value should be zero. If there is deviation from standard value, the problem may be in external clock source or in clock cable. These need to be checked by clock measuring equipment.
4.5.1.16
Check for the status of the SNTs
Command
NTSTP:SNT=ALL; Command Output:-
SWITCHING NETWORK TERMINAL STATE SNT STATE BLS LST FCODE C7SNTAH-0 WO C7SNTAH-1 WO If any of the SNT has ABL status then reset it by NTBLI, NTBLE command. Still, if the status remains ABL, the card may be faulty. To replace the card, we may require to know its position. To know this we may use the following commands.
4.5.1.17
Check for the position of card.
Command
EXPOP:RP=520; DEVICE POSITION 60
RP 520
POS BSC1-3-26-3-64
This implies the card position of RP-520 is in BSC-1, Rack-3, Sub rack Vertical Position-26, and Card position in sub rack-64. The card position can also be known by the following command where light will glow in all card of the particular sub rack. Test Board Indication
Command
TEBIC:RP=520, LED=on;
Again to switch off light on PCB, give the following command. Command
TEBIC:LED=off; 4.5.1.18 Check for the status of the DIPS Command
DTSTP: DIP=ALL, STATE=ABL;
4.5.1.19
Transcoder Pool Status
Command
RRTPP:TRAPOOL=ALL; Command Output RADIO TRANSMISSION TRANSCODER POOL DETAILS TRAPOOL CHRATE SPV RNOTRA POOLACT POOLIDLE POOLTRAF AMRHR HR 3 7656 7440 6337 1103 SUBPOOL 1 2
SUBACT SUBIDLE SUBTRAF 7248 6145 1103 192 192 0
TRAPOOL CHRATE SPV RNOTRA POOLACT POOLIDLE POOLTRAF AMRFR FR 3 3840 3837 2546 1291 SUBPOOL 1
SUBACT SUBIDLE SUBTRAF 3837 2546 1291
TRAPOOL CHRATE SPV RNOTRA POOLACT POOLIDLE POOLTRAF 61
If the POOLIDLE count is 0 or very less we may face Transcoder congestion in corresponding pool. For this we have to rearrange TRAPOOL device by the following commands. RRTPC:TRAPOOL=AMRFR, RNOTRA=6500, force; It will resize the transcoder device of TRAPOOL AMRFR from 7656 to 6500. 4.5.1.20 TRX capacity check Command
SAAEP:SAE=1153;
SIZE ALTERATION OF DATA FILES INFORMATION SAE BLOCK CNTRTYP NI NIU NIE NIR 1153 MANUAL 2048 1681 This implies the Data base table for TRX capacity is 1153 whose equipped capacity is 2048 and working TRX is 1681.
4.5.1.21
Check for BSC Temperature
4.5.1.22
Check for GB link status
Command
RRGBP; (This command is used for GB over Frame Relay) Command Output:-
62
The NSVCI status should be active. If any of the NSVCI is not ok, then check the status of corresponding E1 as per the device given under DEV1 column. If the GB link is configured over IP (GB over IP) then use the following command. Command: RRINP: NSEI=ALL; Command Output
RADIO TRANSMISSION IP NETWORK SERVICE DATA NSEI 395 PRIP PPORT NSSTATE NSSTATUS RAT 10.222.60.88 2157 ACTIVE ACTIVE GERAN RIP PORT SWEIGHT DWEIGHT RIPSTATUS 10.222.60.88 35364 1 0 OPERATIONAL 10.222.60.88 2158 0 1 OPERATIONAL LIP IPDEV LIPSTATUS 10.222.95.119 RTIPGPH-20 OPERATIONAL 10.222.95.118 RTIPGPH-19 OPERATIONAL 10.222.95.117 RTIPGPH-18 OPERATIONAL 10.222.95.116 RTIPGPH-17 OPERATIONAL END The NSSTATUS should be active and RIPSTATUS should be operational. If it is not active, there may be problem in IP reachability. Then we have to check the LAN connectivity from RPS card or PCU sub rack to MPBN switch. 4.5.1.23 Check for latest Software Patches. Command
PCORP:BLOCK=MISSRA; Command Output:-
PROGRAM CORRECTIONS BLOCK SUID CA CAF MISSRA 5400/CAA 107 7256/M06AF R4A01 CI S TYPE POSITION Z02PA5697 C CODE H'00E4
SIZE 21 63
488 5 F
4
X12PA5041 C SST 60 16 X12PA5041 C SST 62 18 X12PA5041 C SDT ISSIGNALUSEDR 12 X12PA5041 C CODE H'0273 24 X12PA5041 C CODE H'039E 51 X12PA5041 C CODE H'043A 28 X12PA5041 C CODE H'0442 24 X12PA5114 C CODE H'03A8 28 X12PA5114 C CODE H'03E8 38 X12PA5114 C CODE H'03C6 29 X12PA5224 C CODE H'034F 34 X12PA5224 C CODE H'0410 36 ACA20100503 C CODE H'0178 20 IPA20100503 C CODE H'0183 20 IPA0000000007FF C CODE H'00B7 20 B30A07B130C02A C CODE H'007B 20 UPG20100503 C CODE H'01D1 20 U06AA0207BC021N C CODE H'014C 20 The Output shows the latest program correction is released on 3rd May 2010. We may ask the vendor to update the system with latest software patch. The latest software patch will reduce software error of the system. To know the software recovery information the following command may be used.
4.5.1.24
Check for software recovery information
Command
SYRIP:SURVEY; Command Output:
SOFTWARE RECOVERY SURVEY EVENT TYPE 3 FORLOPP 2 APPLERR 1 APPLERR 62 APPLERR 61 APPLERR 0 APPLERR 59 FORLOPP
EXPLANATION EVENTCNT FRDEL TIMEOUT AT FORLOPP AUDIT & FLERROR ERROR REPORTED BY PROCEDURE FLERROR ERROR REPORTED BY PROCEDURE FLERROR ERROR REPORTED BY PROCEDURE FLERROR ERROR REPORTED BY PROCEDURE FLERROR ERROR REPORTED BY PROCEDURE FLERROR TIMEOUT AT FORLOPP AUDIT & FLERROR
0 2 2 2 2
0
EVENT CODE INF1 INF2 INF3 INF4 SIDE STATE DATE TIME ACTIVE 64
3 H'310D H'4202 H'00E6 H'00AB H'00AB A-EX PARAL 151130 1718 YES 2 H'4301 H'4202 H'00E6 H'0002 H'9856 A-EX PARAL 151130 1703 YES 1 H'4301 H'4202 H'012F H'0002 H'7BD5 A-EX PARAL 151129 2357 YES 62 H'4301 H'4202 H'01CD H'0002 H'7BD5 A-EX PARAL 151129 2357 YES 61 H'4301 H'AB00 H'04CC H'0002 H'7BD5 A-EX PARAL 151129 2357 YES END The Output shows there is frequent software recovery (two times on 30-11-2015 and 3 times on 29-11-2015 and so on) and the cause is APPLERR (Application detected software error) and FORLOPP(Forlopp is a standard function which includes the capability of recovering a software error with a Forlopp Release instead of a System Restart). To overcome such problem latest software patch should be loaded.
4.5.1.25
Health Check for APG40
Logon on as Administrator on ACTIVE node. PROCEDURE: 1.Confirm On active node C:\>prcstate (Status should be active) active C:\>hostname (if gives the logged in node name) apg40c-2a 2.Check SW Version C:\>swrprint 3. Check no major alarms are present. C:\>alist 4. Check if all resource are online. C:\>cluster res C:\>cluster group 6.check AP message store C:\>msdls 7.Check if any abnormal process restarts automatically. 65
C:\>ispprint 8 List defined IO devices C:\cpdlist 9.Ping standby node C:\>ping
! standby node!
if timeout, restart standby node as correct solution. 10. Check FMS is working. C:\>:cpfls 11.Verify mml and CPT are working. C:\>:mml
