NSN ICSU 1

ICSU (Fishing) Information:

configuration, settings and how to run it
ICSU
Version 1.0
NSN ICSU 2

Contents
1 INTRODUCTION .................................................................................................... 3
2 ICSU (FISHING) INSTALLATION AND CONFIGURATION .............................................. 5
3 SETTING UP ICSU (FISHING) ................................................................................ 7
4 CHECKING ........................................................................................................ 10
5 RUNNING ICSU (FISHING).................................................................................. 10
6 DEFINING AND GETTING A SPECIFIC DEFINED COUNTER LOGS FROM ICSU .............. 11
7 APPENDIX A (COUNTERS LIST) ........................................................................... 13
NSN ICSU 3

1 Introduction

The ICSU Super Call Trace information directly gathered from the user handset is obtained
through the ICSU logs that are triggered (and the logs gathered) by a tool called Fishing,
which is an executable program (.exe) based on a script. This script initiates a collection of
data from selected objects within the network.

This tool is being used now to get detailed information of the super call traces for
troubleshooting purposes.

The Fishing program is generally executed on a PC/Laptop/Server that is connected to the

same network (DCN network) where the Netact OSS resides. In this particular example the
program is executed through the Netact console once you log in (figure 1).

Figure 1

Then selecting desktop on the selection menu (on the left) you can login into the proper
screen to run the program. This program can be launched clicking on a couple of pre-
defined icons that are accessible through the Netact window that starts a Citrix session
and starts a fishing session (figure 2).
NSN ICSU 4

Figure 2

Then you can execute the program here by selecting or clicking in any of those 2 icons
that appear as machine 1 or machine 2, as it is configured for this specific case a Citrix
session will start where Fishing will be launch. As we said, in this particular case for this
configuration there are 2 Machines (Machine 1 and Machine 2) for backup/redundancy and
workload purposes.

Meanwhile, a program HIT provides the other way running Fishing without OSS system
access (Figure 3). User can install HIT program in any Windows OS computer and
performing Fishing in local computer with DCN network connection.

Figure 3
NSN ICSU 5

2 ICSU (Fishing) installation and configuration

2.1 Use NetAct OSS

The installation of the Fishing software requires to copy the macro its .ini files in the same
directory folder.

Then you need to edit the .ini file and make sure the following lines are there:

string PATH = "C:\\Users\\";

note: this is the default location for the produced log files in users laptop

string FTP_USER_NAME = "";

string FTP_PASSWORD = "";

note: This are the default values for RNC FTP username & password. Ask for RNC
administrator the required access information:

string BTS_USERNAME = "";

string BTS_PASSWORD = "";

From WN4.0 BTS software onwards username & password is required for fetching BTS Technical
Report. These default values for those:

If BTS Technical Report fetching tool is used, then the following settings need to be edited:

string BTS_LOG_FETCH_TOOL_PATH[RELEASES] =
{
"C:\\USERS\\BTSEMTool_For_WN3.3_V2_0_2130-S\\BTSTool\\", // RN_2_2 bts fetchlogtool
"C:\\Users\\BTSEMTool_For_WN4.0_V3_1_3061-S\\BTSTool\\", // RN_3_0 bts fetchlogtool
"C:\\Users\\BTSEMTool_For_WN4.0_V3_1_3061-S\\BTSTool\\", // RN_4_0 bts fetchlogtool
"C:\\Users\\BTSEMTool_For_WN4.0_V3_1_3061-S\\BTSTool\\" // IHSPA bts fetchlogtool
};

2.2 Use HIT program

The setup of the Fishing macro requires copy the macro package files to the local
computer drive.
NSN ICSU 6

Then you need to edit the fishing_ini.tel file before running fishing macro.

Define ICSU log capture scope in BTS level:

Define IMSI number

Define ICSU capture period

NSN ICSU 7

3 Setting up ICSU (Fishing)

As we explained in the previous paragraphs, you can login and run access the application
through the icon selection via Netact, then clicking in any of the icons you will access and
launch the Fishing application (figure 4). You also can install Hip program running Fishing
macro in your Windows computer with DCN connection (figure 5).

Figure 4
NSN ICSU 8

Figure 5

Once you opening the Fishing macro, then the following information are requested, where
you will have to select the appropriate RNC software level first.

Then please select the RNC Software level as it is indicated in this example. Please notice
that in your specific configuration, the names will be different. The names that appear in
this axample are for illustrative purposes only.

Then you have to select the specific RNC by introducing (or selecting) the specific device
name of the target RNC to get the logs from.
NSN ICSU 9

Then you have to introduce the specific RNC username & password to have access to that
specific system, and which will permit and grant access so the information will be FTP as a
file transfer to the specified directory.

If the second screen appears, then a path on users PC/laptop/Sever needs to be

introduced in order to get the logs) which will be transferred to that particular directory.

Then on this screen, a specific trigger rule (counter or some other rule) should be selected.
The counters list is used to define the trigger to capture sessions (calls). A complete list of
those are provided on Appendix A.
NSN ICSU 10

4 Checking

Collect the following files under the PATH you defined when started the macro:
_fishing.txt
_fishing_summary.txt
In addition, collect the actual monitoring files and all other files located in the folder
named according to select trigger rule under the defined PATH.

5 Running ICSU (Fishing)

Now, following the sequence up to this point we need to select a specific counter in
order to run Fishing, it will provide the logs from ICSU.
Select the counter (e.g. RAB_ACT_FAIL_PS_DATA_INTERA_RNC ).
Note: Please keep in mind that you could define those in the configuration file, so this
selection would not be required (the prerequisite is that _ini_ file has default settings)
NSN ICSU 11

6 Defining and getting a specific defined counter logs from ICSU

Edit the monitoring conditions according to request from Tier3 or typically accept the
default condition.

Select monitoring collection method; in this case you collect only the monitoring from
the triggering ICSU:
NSN ICSU 12

Select BTS Technical Report fetching, if the tool for this purpose has been configured
and if its suspected that counter is updated due to BTS problem, otherwise click NO:

E2K printout is the output of one command of E2K service terminal extension in ICSU.
This command gives overview of other calls/services configured in a cell, where
counter triggered. Typically its better to collect this than not to do so.

Collect always computer logs from the ICSU where triggering happened.

Note: After executing this macro you should be getting the log files. Follow up messages in
HITs Message Window. There youll see indication when macro triggers.

A sample of the ICSU logs obtained after running the application in the directory specified
and defined are shown.
NSN ICSU 13

7 Appendix A (Macros)
Hit program:

Fishing (WN4.0, RU10):

Fishing (WN5.0, RU20)

NSN ICSU 14

8 Appendix A (Counters List)

RRC_CONN_ACT_FAIL
RRC_CONN_ACT_FAIL_IU
RRC_CONN_ACT_FAIL_RADIO
RRC_CONN_ACT_FAIL_BTS
RRC_CONN_ACT_FAIL_IUR
RRC_CONN_ACT_FAIL_CIPH
RRC_CONN_ACT_FAIL_I_CHK
RRC_CONN_ACT_REL_P_EMP
RRC_CONN_ACT_FAIL_RNC
RRC_CONN_STP_FAIL
RRC_CONN_STP_FAIL_HC
RRC_CONN_STP_FAIL_AC
RRC_CONN_STP_FAIL_BTS
RRC_CONN_STP_FAIL_TRANS
RRC_CONN_STP_FAIL_FROZBS
RRC_CONN_STP_FAIL_RNTI_ALLO
RRC_CONN_STP_FAIL_RNC
RRC_CONN_STP_ATT_REPEAT
RRC_CONN_ACC_FAIL
RRC_CONN_ACC_FAIL_RADIO
RRC_CONN_ACC_FAIL_MS
RRC_CONN_ACC_REL_CELL_RESEL
RRC_CONN_ACC_FAIL_RNC
RAB_ACT_FAIL_CS_VOICE
RAB_ACT_FAIL_CS_VOICE_IU
RAB_ACT_FAIL_CS_VOICE_RADIO
RAB_ACT_FAIL_CS_VOICE_BTS
RAB_ACT_FAIL_CS_VOICE_IUR
RAB_ACT_FAIL_CS_VOICE_I_CHK
RAB_ACT_REL_CS_VOICE_P_EMP
RAB_ACT_FAIL_CS_VOICE_UE
RAB_ACT_FAIL_CS_VOICE_RNC
RAB_STP_FAIL_CS_VOICE
RAB_STP_FAIL_CS_VOICE_AC
RAB_STP_FAIL_CS_VOICE_BTS
RAB_STP_FAIL_CS_VOICE_TRANS
RAB_STP_FAIL_CS_VOICE_FROZBS
NSN ICSU 15

RAB_STP_FAIL_CS_VOICE_UE_CAPA
RAB_STP_FAIL_CS_VOICE_NOT_SUPP_PAR
RAB_STP_FAIL_CS_VOICE_ANCHOR
RAB_STP_FAIL_CS_VOICE_RNC
RAB_ACC_FAIL_CS_VOICE
RAB_ACC_FAIL_CS_VOICE_MS
RAB_ACC_FAIL_CS_VOICE_RNC
RAB_ACT_FAIL_CS_DATA_CONV
RAB_ACT_FAIL_CS_DATA_CONV_IU
RAB_ACT_FAIL_CS_DATA_CONV_RADIO
RAB_ACT_FAIL_CS_DATA_CONV_BTS
RAB_ACT_FAIL_CS_DATA_CONV_IUR
RAB_ACT_FAIL_CS_DATA_CONV_I_CHK
RAB_ACT_REL_CS_DATA_CONV_P_EMP
RAB_ACT_FAIL_CS_DATA_CONV_UE
RAB_ACT_FAIL_CS_DATA_CONV_RNC
RAB_STP_FAIL_CS_DATA_CONV
RAB_STP_FAIL_CS_DATA_CONV_AC
RAB_STP_FAIL_CS_DATA_CONV_BTS
RAB_STP_FAIL_CS_DATA_CONV_TRANS
RAB_STP_FAIL_CS_DATA_CONV_FROZBS
RAB_STP_FAIL_CS_DATA_CONV_UE_CAPA
RAB_STP_FAIL_CS_DATA_CONV_NOT_SUPP_PAR
RAB_STP_FAIL_CS_DATA_CONV_ANCHOR
RAB_STP_FAIL_CS_DATA_CONV_RNC
RAB_ACC_FAIL_CS_DATA_CONV
RAB_ACC_FAIL_CS_DATA_CONV_MS
RAB_ACC_FAIL_CS_DATA_CONV_RNC
RAB_ACT_FAIL_CS_DATA_STREAM
RAB_ACT_FAIL_CS_DATA_STREAM_IU
RAB_ACT_FAIL_CS_DATA_STREAM_RADIO
RAB_ACT_FAIL_CS_DATA_STREAM_BTS
RAB_ACT_FAIL_CS_DATA_STREAM_IUR
RAB_ACT_FAIL_CS_DATA_STREAM_I_CHK
RAB_ACT_REL_CS_DATA_STREAM_P_EMP
RAB_ACT_FAIL_CS_DATA_STREAM_UE
RAB_ACT_FAIL_CS_DATA_STREAM_RNC
RAB_STP_FAIL_CS_DATA_STREAM
RAB_STP_FAIL_CS_DATA_STREAM_AC
NSN ICSU 16

RAB_STP_FAIL_CS_DATA_STREAM_BTS
RAB_STP_FAIL_CS_DATA_STREAM_TRANS
RAB_STP_FAIL_CS_DATA_STREAM_FROZBS
RAB_STP_FAIL_CS_DATA_STREAM_UE_CAPA
RAB_STP_FAIL_CS_DATA_STREAM_NOT_SUPP_PAR
RAB_STP_FAIL_CS_DATA_STREAM_ANCHOR
RAB_STP_FAIL_CS_DATA_STREAM_RNC
RAB_ACC_FAIL_CS_DATA_STREAM
RAB_ACC_FAIL_CS_DATA_STREAM_MS
RAB_ACC_FAIL_CS_DATA_STREAM_RNC
RAB_ACT_FAIL_PS_DATA_CONV
RAB_ACT_FAIL_PS_DATA_CONV_IU
RAB_ACT_FAIL_PS_DATA_CONV_RADIO
RAB_ACT_FAIL_PS_DATA_CONV_BTS
RAB_ACT_FAIL_PS_DATA_CONV_IUR
RAB_ACT_FAIL_PS_DATA_CONV_I_CHK
RAB_ACT_REL_PS_DATA_CONV_P_EMP
RAB_ACT_FAIL_PS_DATA_CONV_UE
RAB_ACT_FAIL_PS_DATA_CONV_RNC
RAB_STP_FAIL_PS_DATA_CONV
RAB_STP_FAIL_PS_DATA_CONV_AC
RAB_STP_FAIL_PS_DATA_CONV_BTS
RAB_STP_FAIL_PS_DATA_CONV_TRANS
RAB_STP_FAIL_PS_DATA_CONV_FROZBS
RAB_STP_FAIL_PS_DATA_CONV_UE_CAPA
RAB_STP_FAIL_PS_DATA_CONV_NOT_SUPP_PAR
RAB_STP_FAIL_PS_DATA_CONV_ANCHOR
RAB_STP_FAIL_PS_DATA_CONV_RNC
RAB_ACC_FAIL_PS_DATA_CONV
RAB_ACC_FAIL_PS_DATA_CONV_MS
RAB_ACC_FAIL_PS_DATA_CONV_RNC
RAB_ACT_FAIL_PS_DATA_STREAM
RAB_ACT_FAIL_PS_DATA_STREAM_IU
RAB_ACT_FAIL_PS_DATA_STREAM_RADIO
RAB_ACT_FAIL_PS_DATA_STREAM_BTS
RAB_ACT_FAIL_PS_DATA_STREAM_IUR
RAB_ACT_FAIL_PS_DATA_STREAM_I_CHK
RAB_ACT_REL_PS_DATA_STREAM_P_EMP
RAB_ACT_FAIL_PS_DATA_STREAM_UE
NSN ICSU 17

RAB_ACT_FAIL_PS_DATA_STREAM_RNC
RAB_STP_FAIL_PS_DATA_STREAM
RAB_STP_FAIL_PS_DATA_STREAM_AC
RAB_STP_FAIL_PS_DATA_STREAM_BTS
RAB_STP_FAIL_PS_DATA_STREAM_TRANS
RAB_STP_FAIL_PS_DATA_STREAM_FROZBS
RAB_STP_FAIL_PS_DATA_STREAM_UE_CAPA
RAB_STP_FAIL_PS_DATA_STREAM_NOT_SUPP_PAR
RAB_STP_FAIL_PS_DATA_STREAM_ANCHOR
RAB_STP_FAIL_PS_DATA_STREAM_RNC
RAB_ACC_FAIL_PS_DATA_STREAM
RAB_ACC_FAIL_PS_DATA_STREAM_MS
RAB_ACC_FAIL_PS_DATA_STREAM_RNC
RAB_ACT_FAIL_PS_DATA_INTERA
RAB_ACT_FAIL_PS_DATA_INTERA_IU
RAB_ACT_FAIL_PS_DATA_INTERA_RADIO
RAB_ACT_FAIL_PS_DATA_INTERA_BTS
RAB_ACT_FAIL_PS_DATA_INTERA_IUR
RAB_ACT_FAIL_PS_DATA_INTERA_I_CHK
RAB_ACT_REL_PS_DATA_INTERA_P_EMP
RAB_ACT_FAIL_PS_DATA_INTERA_UE
RAB_ACT_FAIL_PS_DATA_INTERA_RNC
RAB_STP_FAIL_PS_DATA_INTERA
RAB_STP_FAIL_PS_DATA_INTERA_AC
RAB_STP_FAIL_PS_DATA_INTERA_BTS
RAB_STP_FAIL_PS_DATA_INTERA_TRANS
RAB_STP_FAIL_PS_DATA_INTERA_FROZBS
RAB_STP_FAIL_PS_DATA_INTERA_UE_CAPA
RAB_STP_FAIL_PS_DATA_INTERA_NOT_SUPP_PAR
RAB_STP_FAIL_PS_DATA_INTERA_ANCHOR
RAB_STP_FAIL_PS_DATA_INTERA_RNC
RAB_ACC_FAIL_PS_DATA_INTERA
RAB_ACC_FAIL_PS_DATA_INTERA_MS
RAB_ACC_FAIL_PS_DATA_INTERA_RNC
RAB_ACT_FAIL_PS_DATA_BACKG
RAB_ACT_FAIL_PS_DATA_BACKG_IU
RAB_ACT_FAIL_PS_DATA_BACKG_RADIO
RAB_ACT_FAIL_PS_DATA_BACKG_BTS
RAB_ACT_FAIL_PS_DATA_BACKG_IUR
NSN ICSU 18

RAB_ACT_FAIL_PS_DATA_BACKG_I_CHK
RAB_ACT_REL_PS_DATA_BACKG_P_EMP
RAB_ACT_FAIL_PS_DATA_BACKG_UE
RAB_ACT_FAIL_PS_DATA_BACKG_RNC
RAB_STP_FAIL_PS_DATA_BACKG
RAB_STP_FAIL_PS_DATA_BACKG_AC
RAB_STP_FAIL_PS_DATA_BACKG_BTS
RAB_STP_FAIL_PS_DATA_BACKG_TRANS
RAB_STP_FAIL_PS_DATA_BACKG_FROZBS
RAB_STP_FAIL_PS_DATA_BACKG_UE_CAPA
RAB_STP_FAIL_PS_DATA_BACKG_NOT_SUPP_PAR
RAB_STP_FAIL_PS_DATA_BACKG_ANCHOR
RAB_STP_FAIL_PS_DATA_BACKG_RNC
RAB_ACC_FAIL_PS_DATA_BACKG
RAB_ACC_FAIL_PS_DATA_BACKG_MS
RAB_ACC_FAIL_PS_DATA_BACKG_RNC
RRC_PMI
RAB_PMI
ALL_FAILURES
SP_ERROR_S
RECOVERY_ACTION
COCO_FAILURE
ISHO_DROPS
SRNC_RELOC_FAIL
SETUP_FAIL_RNC_HS_DSCH
SETUP_FAIL_UE_HS_DSCH
SETUP_FAIL_BTS_HS_DSCH
SETUP_FAIL_IUB_HSDCH
SETUP_FAIL_IUB_MAC_D
SETUP_FAIL_IUB_HS_TOTAL
HSDPA_RETAINABILITY_FAIL
REL_ALLO_OTH_FAIL_HSDCH
PS_SETUP_FAIL_OTHER
if(status == 1)
messagebox("The most important settings are at default values");
else
messagebox("Some settings not at default value, check messages window");
endif

endfunction
NSN ICSU 19

function bts_ip_address_configuration()
// bts id // bts ip address
bts_ip_list[ 1001 ] = "10.10.10.10";
bts_ip_list[ 1234 ] = "10.10.10.10";
bts_ip_list[ 0110 ] = "10.10.10.10";
endfunction

string IHSPA_FISHING_TOOL_OTHER_OPTIONS = "10 10 40 10";

string IHSPA_IP_FILENAME = "c:\\users\\perl\\ihspa.txt";
string IHSPA_FISHING_TOOL = "c:\\users\\perl\\ihspa_kala_1_1.pl";
SCC_FAILED_DUE_TO_UE
SCC_FAILED_DUE_TO_BTS
SCC_FAILED_DUE_TO_TRANSM
SCC_FAILED_DUE_TO_AC
SCC_FAILED_DUE_TO_OTHER
ALL_CALLS_IN_BTS
ALL_RAB_FAILURES_IN_BTS
ALL_RRC_FAILURES_IN_BTS
ALARMS
COMPUTER_LOGS
OS_LOGS
CUSTOM
CUSTOM_MULTIPLE_MSGS
NORMAL_MONITORING
RLC_MONITORING
SMS_ERRORSync_Power STANDARD