Data Collection Guideline

BTS

User Guide

1/1553-LZA 701 6002 Uen B

Copyright

© Ericsson AB 2016. All rights reserved. No part of this document may be

reproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use
of this document.

Trademark List

All trademarks mentioned herein are the property of their respective owners.
These are shown in the document Trademark Information.

1/1553-LZA 701 6002 Uen B | 2016-05-10

 Contents

Contents

1 Introduction 1
1.1 Prerequisites 1

2 Data Collection 3
2.1 Problem Description 3
2.2 Log Collection 5
2.3 STN Node (RBS 2409 or SIU) Faults 9

1/1553-LZA 701 6002 Uen B | 2016-05-10

Data Collection Guideline

1/1553-LZA 701 6002 Uen B | 2016-05-10

 Introduction

1 Introduction

The purpose of this document is to provide a guideline for collecting the

troubleshooting data, that must be enclosed in a Customer Service Request
(CSR). A CSR is written when a problem is experienced with the product.

Note: All data collection activities must be carried out as soon as possible,
before any recovery is attempted since the recovery procedure results
in some logs and statistics being overwritten.

Note: If it is an RBS with multi-standard configurations, make sure that

troubleshooting data is collected for both radio standards. For
information regarding which data to collect for WCDMA or LTE refer to
the Data Collection Guideline documents for each RBS type.

Any comments are appreciated and can be sent as a ticket towards GRAN help
desk http://grantier2.lmera.ericsson.se/GRANticket/newticket.

1.1 Prerequisites
The following prerequisites must be fulfilled before using this User Guide.

1.1.1 Conditions
Ensure that the following conditions are met:

• Remote OMT (ROMT) over IP is needed to connect remotely.

Note: If no ROMT over IP is available, collection of logs must be done

at site.

1.1.2 Tools
Ensure that the following tools are available:

• OMT SW

• BSC Connection SW (WinFiol or some other tools which can connect BSC)

• NetHawk or Tektronix which can collect Abis log

• TEMS which can collect Um log

1/1553-LZA 701 6002 Uen B | 2016-05-10 1

 Data Collection Guideline

2 1/1553-LZA 701 6002 Uen B | 2016-05-10

 Data Collection

2 Data Collection

Logs together with the problem description can be included in the CSR. All logs
must be named with CSR number, time, and date of collection and attached
to the CSR.

CSR1234567_20140326-12-56
Example 1 Log Filename

If the log-file is too large to be attached to the CSR, contact GRAN help desk
for FTP details.

2.1 Problem Description

The solution time of a CSR is highly dependent on a good problem description
and logs showing the fault. Therefore it is important to spend time gathering
data rather than rushing a CSR without information.

The template in Section 2.1.2 on page 3 can be used as a help to

describe the problem. It can be attached to the CSR as a text file named
CSRXXXXXX_TroubleDescription.txt

2.1.1 Trouble Reproduction

Information regarding if the fault is reproducible or not can be included. If the
fault is reproducible, information regarding how it is reproduced needs to be
added as well.

Other useful information to include is:

• If any changes or updates was done in the system before the fault occurred,
for example, new software installed.

• In which Transceiver Group(s) the fault occurred.

2.1.2 Trouble Description Template

The following is a template for the trouble description:

Trouble Effect
----------------

Clearly describe the consequences the customer is experiencing with the

problem and the impact it has on the network.

Problem description
--------------------

1/1553-LZA 701 6002 Uen B | 2016-05-10 3

 Data Collection Guideline

Provide as detailed information as possible of the problem:

• When and in what node did the problem start to occur?

-Date, time and name (identification) of node.
-Additional events in the same node? (Date, time)
-Events in other nodes with same symptom? (Date, time and name)

• Number of affected sites?

• Is the fault permanent or intermittent?

• What was done or what happened before the fault appearance

-HW or SW changed, upgrade or update?
-BSC, RBS or cell parameters changed?
- BSC commands entered?
- Changes on transmission?
-RBS power ON/OFF?

• Any other special configuration or special circumstances?

-Is this configuration Mixed mode or Not?
-If it is Mixed mode, is this Configuration G+W,G+L or G+W+L?

• Any activities in other nodes connected to issued BSC or RBS?

• Any attempet to update any of the node(s) with the problem to the latest SW?

RBS documentation faults

• Title, product number and R-state of the faulty manual

• Chapter and page number of the faulty (or missing) information

• Description of the problem and proposal of update

OMT, ROMT or ROMTIP faults

• Product number and R-state of the faulty OMT

• Windows version

• BTS SW version

• Trouble description and trouble effect

• Detailed description of the procedure that provokes the fault

Analysis
---------

•What analysis has been made, i.e. what has already been checked, any
actions taken, corrections loaded etc.?

•Is the fault reproducible? How to reproduce it? Can it be reproducible

for test purposes?

•Is there a work around or remedy?

Remote Access
---------------
Attach RSG information to the case if possible. If not, a contact person shall be ⇒
named that can be contacted to obtain RSG information.

4 1/1553-LZA 701 6002 Uen B | 2016-05-10

 Data Collection

2.2 Log Collection

Make sure to collect the RBS and BSC information as soon as the fault is
discovered. It is important since the log areas are of a limited size and is
overwritten if an alarm is continuously raising and ceasing.

2.2.1 RBS Information

The following logs and files needs to be collected for the RBS:

• OMT logs from:

0 DXU/DUG

0 TRU/dTRU/DRU/RUG/RUS

0 ECU

• BTS configuration file (IDB)

2.2.2 Collecting RBS Logs and IDB Files

To collect the mandatory RBS logs and IDB file, one of the following is needed:

• OMT

• ROMT

• ROMT/IP

There is one OMT version released for every RBS software release. To know
which OMT to use, refer to GRAN PLMs Ericoll site.

2.2.3 Collecting RBS Logs and IDB Files Using OMT

This section describes how to collect CSR data using the OMT. The data must
be collected for all CSRs, and all CSR problem types.

More information can be found in the OMT program online help.

In the OMT, do the following to export the RBS logs to a file:

1. Start the OMT application.

2. Go to the Tools menu.

3. Select Wizards.

4. Read the support information.

5. Click OK.

1/1553-LZA 701 6002 Uen B | 2016-05-10 5

 Data Collection Guideline

6. Choose the option Collect RBS Logs and click NEXT.

7. The wizard starts to collect the information. A zip-file is created and stored
on the computer.

2.2.4 Multi-Standard RBS

In case of Multi-Standard configuration, it is mandatory to collect and attach logs

from the other system, even if there is not any service impact on the other RAN.

For information on how to collect logs for the other systems follow the
instructions in the DCG documents found in the following libraries:

• LTE: EN/LZN78409001

• WCDMA: EN/LZN7356023

2.2.5 BSC Information

Follow the instructions in Data Collection Guideline, Base Station Controller
G13B, Ericsson GSM System to collect the BSC logs.

In addition run the following script in the BSC to collect BTS-related printouts:
@COMMENT *********************************************************
@COMMENT * *
@COMMENT * THIS IS THE OFFICIAL PLM BTS DCG SCRIPT V1.1 *
@COMMENT * *
@COMMENT * FTP://FTP201.RND.KI.SW.ERICSSON.SE/BTS-GLOBAL/BTSDCG/ *
@COMMENT * *
@COMMENT * WINFIOL 7.1 SP4 OR HIGHER IS REQUIRED FOR *
@COMMENT * THE SCRIPT TO RUN PROPERLY *
@COMMENT * *
@COMMENT * HTTPS://AXE-WINFIOL.RND.KI.SW.ERICSSON.SE/ *
@COMMENT * *
@COMMENT * FOR QUESTIONS REGARDING THE SCRIPT, *
@COMMENT * PLEASE CONTACT PLMBTS@ERICSSON.COM *
@COMMENT * *
@COMMENT *********************************************************
@CLEAR
@ASK {tg} "TG number?"
@PRESERVE
@R-
@GETDATE {date}
@GETTIME {time} HH:MM
@COMMENT SCRIPT STARTED ON {date} AT {time}
@COMMENT *********************************
@COMMENT ********* BSC PRINTOUTS *********
@CONNECT
IOEXP;
RAEPP:ID=ALL;
RLCAP;
RLEMP;
RLSQP;
RLBAP;
RLADP:SET=ALL;
ALLIP;
DBTSP:TAB=AXEPARS,PROJ=VALUE;
PCORP:BLOCK=ALL;
@COMMENT ********** MO PRINTOUTS *********
RXTCP:MO=RXOTG-{tg};
@SET {index} = 0
@SET {iterations} = 0
@SIZE {_LINES} {linecount}

6 1/1553-LZA 701 6002 Uen B | 2016-05-10

 Data Collection

@FOREACH {_LINES} GOSUB EXTRACTCELLNAMES

RXMSP:MO=RXOTG-{tg},SUBORD;
@CUT {mo} {_LINES} col 1 sep " "
@SET {index} = 0
@SET {highesttrxnumber} = 0
@FOREACH {mo} GOSUB EXTRACTTRXES

RXELP:MO=RXOTG-{tg};
RXMFP:MO=RXOTG-{tg},subord;
RXMFP:MO=RXOTG-{tg},subord,faulty;
RXCAP:MO=RXOTG-{tg},subord;
RXMOP:MO=RXOTG-{tg},subord;
@UNSET {tmode}
@RITEM {tmode} {_LINES[8]} " " 0
@COMMENT {tmode}
@IF {tmode} <> SCM THEN GOTO NOTSCM
@ITEM {scgr} {_LINES[11]} " " 4
RRSCP:SCGR={scgr};
@UNSET {index}
@FIND {index} {_LINES} ".*RBLT.*"
@FOREACH {index} GOSUB PRINTRBLT
@GOTO CONTINUE_MO

@LABEL NOTSCM
RXAPP:MO=RXOTG-{tg};
@UNSET {index}
@FIND {index} {_LINES} "RBLT.*"
@SET {iterations} = 0
@FOREACH {index} GOSUB EXTRACTALLDEVICES
@SET {iterations} = 0
@FOREACH {devnumbers} GOSUB EXTRACTUNIQUEDEVICES
@FOREACH {uniquedevices} GOSUB PRINTDIPSTATUS

@LABEL CONTINUE_MO
RXMDP:MO=RXOCF-{tg};
@FOREACH {trxes} GOSUB TRXPRINTOUTS
RXCDP:MO=RXOTG-{tg};
RXMLP:MO=RXOTG-{tg};
RXATP:MO=RXOTG-{tg};
RXASP:MO=RXOTG-{tg};
RLINP:CELL=ALL;
@FOREACH {celllines} GOSUB PRINTCELLINFO

@GETTIME {time} HH:MM

@COMMENT SCRIPT FINISHED ON {date} AT {time}
@COMMENT **********************************

@CLEAR
@R+
@EXIT

@LABEL PRINTCELLINFO
@COMMENT *** PRINTING INFO FOR CELL: {_CURRLINE} ***
RLACP:CELL={_CURRLINE};
RLAPP:CELL={_CURRLINE};
RLBDP:CELL={_CURRLINE};
RLCDP:CELL={_CURRLINE};
RLCLP:CELL={_CURRLINE};
RLCPP:CELL={_CURRLINE};
RLCRP:CELL={_CURRLINE};
RLCSP:CELL={_CURRLINE};
RLCXP:CELL={_CURRLINE};
RLDAP:CELL={_CURRLINE};
RLDEP:CELL={_CURRLINE};
RLDGP:CELL={_CURRLINE};
RLDHP:CELL={_CURRLINE};
RLDMP:CELL={_CURRLINE};
RLDTP:CELL={_CURRLINE};
RLGAP:CELL={_CURRLINE};
RLGNP:CELL={_CURRLINE};
RLGRP:CELL={_CURRLINE};
RLGSP:CELL={_CURRLINE};
RLHPP:CELL={_CURRLINE};
RLIHP:CELL={_CURRLINE};
RLIMP:CELL={_CURRLINE};
RLLCP:CELL={_CURRLINE};

1/1553-LZA 701 6002 Uen B | 2016-05-10 7

 Data Collection Guideline

RLLDP:CELL={_CURRLINE};
RLLFP:CELL={_CURRLINE};
RLLHP:CELL={_CURRLINE};
RLLLP:CELL={_CURRLINE};
RLLOP:CELL={_CURRLINE};
RLLPP:CELL={_CURRLINE};
RLLUP:CELL={_CURRLINE};
RLMFP:CELL={_CURRLINE};
RLMQP:CELL={_CURRLINE};
RLNCP:CELL={_CURRLINE};
RLNMP:CELL={_CURRLINE};
RLNPP:CELL={_CURRLINE};
RLNRP:CELL={_CURRLINE},CELLR=all;
RLOLP:CELL={_CURRLINE};
RLPBP:CELL={_CURRLINE};
RLPCP:CELL={_CURRLINE};
RLPDP:CELL={_CURRLINE};
RLPRP:CELL={_CURRLINE};
RLPSP:CELL={_CURRLINE};
RLSBP:CELL={_CURRLINE};
RLSDP:CELL={_CURRLINE};
RLSLP:CELL={_CURRLINE};
RLSMP:CELL={_CURRLINE};
RLSSP:CELL={_CURRLINE};
RLSTP:CELL={_CURRLINE};
RLSUP:CELL={_CURRLINE};
RLUMP:CELL={_CURRLINE};
RLCFP:CELL={_CURRLINE};
RLCCP:CELL={_CURRLINE};
RLSVP:CELL={_CURRLINE};
@RETURN

@LABEL TRXPRINTOUTS
RXMDP:MO=RXOTRX-{tg}-{_CURRLINE};
RXMDP:MO=RXOTS-{tg}-{_CURRLINE}-0&&-7;
RXHDP:MO=RXOTS-{tg}-{_CURRLINE}-0&&-7;
@RETURN

@LABEL EXTRACTTRXES
@ITEM {motype} {_CURRLINE} "-" 0
@IF {motype}<>"RXOTRX" THEN RETURN
@ITEM {trxnumber} {_CURRLINE} "-" 2
@SET {trxes[{index}]} = {trxnumber}
@INC {index}
@IF {trxnumber}>{highesttrxnumber} THEN SET {highesttrxnumber} = {trxnumber}
@RETURN

@LABEL EXTRACTALLDEVICES
@ITEM {devnumber} {_LINES[{_CURRLINE}]} " " 0
@SET {devnumbers[{index}]} = {devnumber}
@INC {index}
@RETURN
@LABEL EXTRACTUNIQUEDEVICES
@IF {iterations} > 0 THEN GOTO NOTFIRST
@SET {index} = 0
@SET {uniquedevices[{index}]}= {devnumbers[{iterations}]}
@COMPACT {uniquedevices}
@INC {index}
@GOTO NEXT
@LABEL NOTFIRST
@CALC {expectedvalue} = {previousvalue}+1
@ITEM {currentvalue} {devnumbers[{iterations}]} "-" 1
@IF {expectedvalue} = {currentvalue} THEN GOTO NEXT
@SET {uniquedevices[{index}]}= {devnumbers[{iterations}]}
@COMPACT {uniquedevices}
@INC {index}
@LABEL NEXT
@ITEM {previousvalue} {devnumbers[{iterations}]} "-" 1
@INC {iterations}
@RETURN
@LABEL PRINTDIPSTATUS
RADEP:DEV={_CURRLINE};
@ITEM {snt} {_LINES[4]} " " 1
NTCOP:SNT={snt};

8 1/1553-LZA 701 6002 Uen B | 2016-05-10

 Data Collection

@ITEM {dip} {_LINES[4]} " " 3

DTSTP:DIP=ALL;
@ITEM {dipstatus} {_LINES[4]} " " 2
DTQUP:DIP=ALL;
@RETURN
@LABEL PRINTRBLT
@ITEM {device} {_LINES[{_CURRLINE}]} " " 3
RADEP:DEV={device};
@ITEM {snt} {_LINES[4]} " " 1
NTCOP:SNT=all;
@ITEM {dip} {_LINES[4]} " " 3
DTSTP:DIP=ALL;
DTQUP:DIP=ALL;
@RETURN

@LABEL EXTRACTCELLNAMES
@SET {endvalue} = {iterations}+3
@INC {iterations}
@IF {endvalue}>{linecount} THEN RETURN
@IF {iterations}<6 THEN RETURN
@IF {iterations}>6 THEN GOTO FIRSTCOLUMN
@ITEM {cell} {_CURRLINE} " " 1
@GOTO NEXTCELL
@LABEL FIRSTCOLUMN
@ITEM {cell} {_CURRLINE} " " 0
@LABEL NEXTCELL
@SET {celllines[{index}]} = {cell}
@INC {index}
@UNIQUE {celllines}
@COMPACT {celllines}
@RETURN

2.2.6 Additional Logs

Attach any other logs that you believe can be of interest for the case. Clearly
describe the content of the logs and where and when the logs were taken.

• If possible, enclose an Abis log taken with a protocol analyzer, preferably

Nethawk or Tektronix. The log files must be in raw format (.rec or .rf5)

• TEMS logs if applicable

Note: If assistance is needed to collect the correct logs, contact GRAN

Tier2 help desk.

2.3 STN Node (RBS 2409 or SIU) Faults

For problems related to the Site Transport Node (STN) and STN parts of RBS
2409 refer to the following DCGs:

• RBS 2409 –Pico, the document can be found at GRAN

PLM/DataCollectionGuidlines EriColl site.

1/1553-LZA 701 6002 Uen B | 2016-05-10 9