Gb over IP

August 5, 2010

METHOD
OF
PROCEDURE

Gb over IP

Nokia Siemens Networks Pvt Ltd.

MS India
Process & Quality Team

Page 1
 Gb over IP
August 5, 2010

Document History

Document Author Vipindas Regional BSS vipindas.d@nsn.com

Manager-South
Document Contributor(s)

Document Approver Lalit Sharma National BSS- lalit.sharma@nsn.com

Head
Document Release Authority

Versions
Date Name Version Contents of change
01/08/2010 Vipindas V1.0 Initial Document

Page 2
 Gb over IP
August 5, 2010

Table of contents
1. Purpose and Scope of Document ................................................................................................ 4
2. Prerequisite ................................................................................................................................. 4
3. Compatibility / Dependencies to other products/system/owner .................................................... 4
4. Acronym Glossary ....................................................................................................................... 4
5. Assumptions & Out of Scope details............................................................................................ 5
6. Relations with other work instructionns ........................................................................................ 5
7. Detailed description ..................................................................................................................... 5
7.1 Detailed job description ......................................................................................................... 5
7.2 Tools Used. ........................................................................................................................... 5
7.3 Impact on Service ................................................................................................................. 6
7.4 Identification of the Stakeholders .......................................................................................... 6
7.5 Specific Instructions ( Entry / Exit Criteria) ............................................................................ 6
7.6 Software backup and change control requirements ............................................................... 6
7.7 Pre-Test Plan and expected results ...................................................................................... 6
7.8 Detailed step-by-step procedures.......................................................................................... 7
7.9 Post-Test Plan and expected results ..................................................................................... 9
7.10 Roll back Plan ................................................................................................................... 9
7.11 Emergency Contact Details ............................................................................................... 9
7.12 Additional Document Reference ........................................................................................ 9
Appendix ............................................................................................................................................10

Page 3
 Gb over IP
August 5, 2010

1. Purpose and Scope of Document

This technical document covers the Gb over IP Procedure .The purpose of this document is
to describe the actions needed for Implementing Gb over IP.This document is intended for the use of
Managed services professional only for the purpose of the agreement under which the document is
submitted, and no part of it may be used, reproduced, modified or transmitted without the prior
permission of Nokia Siemens Networks

2. Prerequisite

i) An engineer with detailed knowledge of:

- BSC architecture.
- Expertise in Fault Management, Configuration & Integration of Nokia BSC

ii) A laptop that meets the following requirements:

- An ethernet interface
- A crossover ethernet cable
- Reflection tool for login to BSC

iii) Sufficient data regarding the IPs of PCU from the concerned team.

iv) Check Licence for Gb over IP Installed in BSC before doing the Activity

3. Compatibility / Dependencies to other products/system/owner

• None

4.Acronym Glossary

Table 4.1 Acronym and Glossary

S.No: Key Word Definition

1. BCSU Base Station Controller Signalling Unit

2. NSEI Network Service Entity Identifier

3. PSEI Packet service entity identifier

Page 4
 Gb over IP
August 5, 2010

5. Assumptions & Out of Scope details

• None

6. Relations with other work instructions

None

7. Detailed description

7.1 Detailed job description

• Take a Fall back of BSC SW Before the activity

• Precheck the BSC before the Activity
• Check any critical alarms in BSC
• Ask the Field Engr to carry out all Field related activities
• Check whether PCU2D or PCUB is used in the BSC.
• Get Proper data of IP for each PCU card
• After confirmation from the field, Disable GENA for all the sectors in the present NSEI
• Lock Old NSEI
• Delete Old NSEI
• Delete Bearer ID
• Create NSEI over Gb using the commands.
• Now attach the sectors for the corresponding NSEI as mentioned and enable GENA

7.2 Tools Used.

(Vendor Platform, Software version, Application Details)

• Tools Used: Reflection software

• Vendor platform: Nokia DX 200 BSC

Page 5
 Gb over IP
August 5, 2010

7.3 Impact on Service

• Activity Duration:Depends on Field activities

• Outage Involved: YES
• Outage Severity: Major
• Additional Outage due to Fallback, if required: NIL
• Outage Severity in case of fallback: NIL
• Outage Time & Duration (Fallback): NIL

7.4 Identification of the Stakeholders

• GNSC-SWUP Team

• Circle BSS Team

7.5 Specific Instructions (Entry / Exit Criteria)

• Login to BSC with correct username and password.

• Check the user rights of particular user name (authority should be 250).
• Precheck the BSC before the activity.
• Approval from the customer is Must before doing the Activity.
• Check the outage window.
• Check proper Licence for GB over IP is installed and is ON before the activity.
• Coordination with field Engineer is required throughout the activity

7.6 Software backup and change control requirements

• It is safe to take a Fallback of BSC SW before and after the activity.

7.7 Pre-Test Plan and expected results

BSC PRE CHECK:

• Open the new log for new BSC.

Page 6
 Gb over IP
August 5, 2010

• Check for the correct BSC using the command.

ZQNI;
• Check any Critical alarms in BSC
ZAHO;
• Take Logs of Below mentioned Commands
ZEQV:BTS=1&&660:GPRS;
ZFXO:NSEI=;
ZFXO:BCSU=0&&6;
ZFXO:BCSU=0&&6:BTS;
ZFUI;
ZEEL:BL;
ZFXO;
ZESI;
ZFXO:NSEI=<NSEI>;
ZFXO:NSEI=<NSEI>:BTS;
ZW7I:FEA,FULL:FEA=7;( FOR CHECKING LICENCE)

7.8 Detailed step-by-step procedures

BCSU ADDITION PROCEDURE:

• Open the new log for new BSC

• Check for the correct BSC using the command.
ZQNI;
• Take a Fallback of BSC SW before doing the activity
ZWKS:MODE=FULL,NAME=<package name>,DIRE=<package
directory>;
• Confirm with Field Engineer which PCU card is using

• Disable GENA for all the sectors in the present NSEI

ZEQV:BTS="(BTS_NO)":GENA=N;

• Lock Old NSEI

ZFXS:NSVCI="(NSVCI_No)":L;

• Delete Old NSEI

ZFXD:NSVCI="( NSVCI_No)";

• Delete Bearer ID

Page 7
 Gb over IP
August 5, 2010

ZFUD:< bearer channel id>,<bearer channel name>;

• Create NSEI over GB using the commands.

• Assigning IP to BCSU,PCU combination for ethernet 0

ZQRN:BCSU,(BCSU_NO):PCU2D,(PCU2D_No):IFETH0:(BCSU,PCU IP),L,:(Subnet
Mask Length):UP;

• Assigning IP to BCSU,PCU combination for ethernet1

ZQRN:BCSU,(BCSU_No):PCU2D,(PCU2D_No):IFETH1:(BCSU,PCU IP),L,:(Subnet Mask

Length):UP;

• Creating Static Route

ZQKC:BCSU,(BCSU_No):PCU2D,(PCU2D_No)::(Default Gateway IP);

• Creating PSEI

ZFXA:PSEI=(PSEI_NO),BCSU=(BCSU_NO),PCU=(PCU_NO);

• Creating NSEI

ZFXK:NSVLI=(NSVLI_NO),NSEI=(NSEI_NO),PSEI=(PSEI_NO),NAME=(NSEI
Name):LPNBR=(Local UDP Port Number),PRE=Y:RIP=(Remote IP),RPNBR=(Remote
UDP Port Number);

Note: PRE=Y means DYNAMIC CONFIGURATION and N means STATIC CONFIGURATION

(Usually using DYNAMIC CONFIGURATION)

• Check the NSEI status

ZFXI:NSVLI="(NSEI_NO)";

Note: If everything ok it should be in WO-EX condition

• Modify the Routing Area

ZEBH:MCC=(MCC_NO),MNC=(MNC_NO),LAC=(LAC_NO),RAC=(RAC_NO):(Id of
function):NSEI=(NSEI_NO);

Note: identification of function is

A add network service entity identifiers
R remove network service entity identifiers

• Now attach the sectors for the corresponding NSEI as mentioned and enable GENA
ZEQV:BTS="&&":GENA=Y:NSEI=(NSEI_NO);

Page 8
 Gb over IP
August 5, 2010

7.9 Post-Test Plan and expected results

 Check any Critical alarms in Particular NSEI (ZAHO ;)

 Check all BTS are attached in NSEI(Check it with logs taken before the
Activity)

7.10 Roll back Plan

Detach All BTS from NSEI

 ZEQV:BTS="(BTS_NO)":GENA=N;

Delete the Created NSVLI

 ZFXH: NSVLI=(NSVLI_NO);

Delete the PSEI

 ZFXE:PSEI=(PSEI_NO);

Create the OLD NSEI (frame relay) and Bearer Channel using ZFXC and ZFUC
Respectively.

7.11 Emergency Contact Details

Mandatory
Name & Phone No. Contact details,time line Escalation Priority
BSS Manager

Escalation Matrix
GNSC Manager

7.12 Additional Document Reference

Page 9
 Gb over IP
August 5, 2010

• NED

Appendix

Page 10