MSI_MOP_PCU_ADDITION_IN_BSC.pdf

PCU Addition in BSC For Internal use only

METHOD OF

PROCEDURE

PCU ADDITION IN BSC

Nokia Siemens Networks Pvt Ltd.

MS India Process & Quality Team


Document History

Document Author N V Ajay Prabhu

Specialist - Fault Management

[email protected]

Document Contributor(s)

Soney M G Manager - BSS O&M

[email protected]

Document Approver Vipindas Regional BSS Manager-South

[email protected]

Document Release Authority Lalit Sharma National BSS-Head [email protected]

Versions

Date Name Version Platform Contents of change

27/09/2011 N V Ajay Prabhu V1.0 Vendor platform: Nokia DX 200 BSC

Initial Document


Table of contents 1. Purpose and Scope of Document ................................................................................................. 42. Prerequisite .................................................................................................................................. 43. Compatibility / Dependencies to other products/system/owner ..................................................... 44. Acronym Glossary ........................................................................................................................ 45. Assumptions & Out of Scope details ............................................................................................ 46. Relations with other work instructionns ........................................................................................ 47. Detailed description ...................................................................................................................... 5

7.1 Detailed job description .......................................................................................................... 57.2 Tools Used. ........................................................................................................................... 57.3 Impact on Service .................................................................................................................. 57.4 Identification of the Stakeholders ........................................................................................... 67.5 Specific Instructions ( Entry / Exit Criteria) ............................................................................. 67.6 Software backup and change control requirements ............................................................... 67.7 Pre-Test Plan and expected results ....................................................................................... 67.8 Detailed step-by-step procedures .......................................................................................... 77.9 Post-Test Plan and expected results .................................................................................... 157.10 Roll back Plan .................................................................................................................. 157.11 Emergency Contact Details .............................................................................................. 167.12 Additional Document Reference ....................................................................................... 16

Appendix ............................................................................................................................................ 16


1. Purpose and Scope of Document

This technical document covers the activity of PCU ADDITION in BSC. The purpose of this document is to describe the actions needed for PCU ADDITION definition in BSC. 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

• Engineer should have detailed knowledge about the architecture, Fault Management, Configuration & Integration of Nokia BSC.

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

NA

4. Acronym Glossary

Table 4.1 Acronym and Glossary S.No: Key Word Definition

1. BTS Base Transeiver Station

2. BCF Base Control Function

3. PCU Packet Control Unit

4. BSC Base Station Controller

5. Assumptions & Out of Scope details

• NONE


6. Relations with other work instructions

None

7. Detailed description 7.1 Detailed job description

PCU Addition in BSC

7.2 Tools Used.

(Vendor Platform, Software version, Application Details)

7.3 Impact on Service

• NONE

• Tools Used: Reflection

• Vendor platform: Nokia DX 200 BSC


7.4 Identification of the Stakeholders

7.5 Specific Instructions (Entry / Exit Criteria)

7.6 Software backup and change control requirements

7.7 Pre-Test Plan and expected results

NA

• NA

• Check the correct username and password of given BSC • Check the user rights of particular user name • Post check should be done befote exit

• GNSC-CM team • RF team


7.8 Detailed step-by-step procedures

• Open Reflection • Log into the specified BSC

ZQNI;

• Make the BCSU 0 to Spare mode ZUSC:BCSU,0:SP;

• Create the PCU in BCSU //BCSU_0// PCU2_D IN 7th

ZWTP:BCSU,0:PCU2_D,5,7::PCUDSP,4,134,TSL,0&&31:PCUDSP,4,135,TSL,0&&31:PCUPPC,4,141,TSL,0&&31;

Slot


• Connect the PCU with BCSU ZWUC:BCSU,0:PCU2_D,5; ZWUC:BCSU,0:PCU2_D,6;

• Configure the new network interface, i.e., to create new PCU2_D ZQRA:BCSU,0:PCU2D,5:IFETH0:1500:UP:; ZQRA:BCSU,0:PCU2D,5:IFETH1:1500:UP:; ZQRA:BCSU,0:PCU2D,6:IFETH0:1500:UP:; ZQRA:BCSU,0:PCU2D,6:IFETH1:1500:UP:;

• Make the BCSU 0 to test mode ZUSC:BCSU,0:TE;

• Run diagnostics of the Unit ZUDU:BCSU,0;

• Check the status od the diagnostics ZUDQ:BCSU,<BCSU no>;

• Check the Result of diagnostics & confirm the unit is OK ZUDH:BCSU,<BCSU no>;

• (Needs to perform the diagnosis of the same BCSU, with both MCMUs. If the diagnosis is

OK, then we will go for next BCSU for PCU addition) then put the BCSU 1 to spare mode.


• Create the PCU in BCSU // BCSU_1// PCU2_D IN 7th Slot


ZWTP:BCSU,1:PCU2_D,5,7::PCUDSP,4,150,TSL,0&&31:PCUDSP,4,151,TSL,0&&31:PCUPPC,4,157,TSL,0&&31; ZWTP:BCSU,1:PCU2_D,6,7::PCUDSP,4,148,TSL,0&&31:PCUDSP,4,149,TSL,0&&31:PCUPPC,4,156,TSL,0&&31;









• Make the BCSU 2 to Spare mode

ZUSC:BCSU,2:SP;

• Create the PCU in BCSU // BCSU_2// PCU2_D IN 7th


Slot













Slot ZWTP:BCSU,3:PCU2_D,5,7::PCUDSP,4,182,TSL,0&&31:PCUDSP,4,183,TSL,0&&31:PCUPPC,4,189,TSL,0&&31;







• Check the status od the diagnostics

ZUDQ:BCSU,<BCSU no>;







Slot











• Create the PCU in BCSU


// BCSU_5// PCU2_D IN 7th


Slot












ZWTP:BCSU,6:PCU2_D,5,7::PCUDSP,4,1078,TSL,0&&31:PCUDSP,4,1079,TSL,0&&31:PCUPPC,4,10 85,TSL,0&&31;

Slot














Slot







• Check the status od the diagnostics

ZUDQ:BCSU,<BCSU no>;







Slot












• Create the PCU in BCSU

// BCSU_9// PCU2_D IN 7th


Slot













Slot


• Connect the PCU with BCSU ZWUC:BCSU,10:PCU2_D,5;


ZWUC:BCSU,10:PCU2_D,6;








• Make the BCSU 10 to working mode ZUSC:BCSU,10:WO;

• Finally Give BSC system restart ZUSS::C=DSK;

• Check if any alarms are active or not in BSC. ZAHO ;

7.9 Post-Test Plan and expected results

• Inform to RF Team the PCU added.

7.10 Roll back Plan

• NONE


7.11 Emergency Contact Details

7.12 Additional Document Reference

Appendix

• NED of BSC

Mandatory Name & Phone No. Contact details,time line Escalation Priority RF Engg SPOC Escalation Matrix Team Lead

MSI_MOP_PCU_ADDITION_IN_BSC.pdf

Documents

Transcript of MSI_MOP_PCU_ADDITION_IN_BSC.pdf