Method Of Procedure

FBSC PCU HW Expansion (without Packet Abis)

1. Purpose

The purpose of this document is to provide the step by step procedure in

doing PCU expansion in Flexi BSC without Packet Abis implementation.

2. Customer Information

Customer Name INDOSAT

Site name
Products Flexi BSC
Project Description FBSC PCU HW Expansion without Packet Abis

3. Requirements Before PCU Expansion

3.1. Licences

Ensure that the Licence Keys are provided and Feature capacity is enough for the additional
PCUs to be installed.
ZW7I:LIC,FULL:;
ZW7I:FEA,FULL:FEA=7&13,;

3.2. PCU IP Plan

Ensure that the correct IP plan is provided for the target BSC. Double check the datafill will
existing PCU IPs.
ZQRI:BCSU;

3.3. Check alarms, Sigtran/GB/Unit/BTS states, CS/PS traffic, etc.

ZAHO;
ZAHP:::2013-01-01;
ZEOL;
ZEOH:2013-01-01;
ZIGO::USERID=ALL::;

Doc. No. Issue: Date: File: Page:

ASG 11-Feb-16 SG1010MP-CARE 1 of 10
 ZWTI:P;
ZWTI:U;
ZUSI;
ZUSI:COMP;
ZFXI:NSEI=0&&65535;
ZFXL:PSEI=0&&99:ALL;
ZNET;
ZOYI::A;

ZEEI;
ZEEL;
ZEEL:BL;
ZEEI::BCSU:;
ZIFO:OMU:MEASUR;
ZIFI:OMU:MEASUR;
ZISI;

ZDBS:BSDATA,0;
ZDBS:PDDATA,0;
ZDBS:OEDATA,0;
ZDBS:EQUIPM,0;
ZDBS:ILDATA,0;

Check ETPA traffic for all existing units:

ZDDS:ETPA,0;
detpcs
exit

Take Computer logs (only for existing computer units):

ZDDE:OMU:"ZGDC";
ZDDE:OMU:"ZGSC";
ZDDE:MCMU,0:"ZGDC";
ZDDE:MCMU,0:"ZGSC";
ZDDE:MCMU,1:"ZGDC";
ZDDE:MCMU,1:"ZGSC";
ZDDE:BCSU,0:"ZGDC";
ZDDE:BCSU,0:"ZGSC";
ZDDE:BCSU,1:"ZGDC";
ZDDE:BCSU,1:"ZGSC";
ZDDE:BCSU,2:"ZGDC";
ZDDE:BCSU,2:"ZGSC";
ZDDE:BCSU,3:"ZGDC";
ZDDE:BCSU,3:"ZGSC";
ZDDE:BCSU,4:"ZGDC";
ZDDE:BCSU,4:"ZGSC";
ZDDE:BCSU,5:"ZGDC";
ZDDE:BCSU,5:"ZGSC";
ZDDE:BCSU,6:"ZGDC";
ZDDE:BCSU,6:"ZGSC";

Note:
Check if there are major alarms, faulty BCSU/MCMU/OMU, faulty
WDU, down SIGTRAN/GB links, etc.

Make sure everything is in order before proceeding to the PCU HW

expansion.

Doc. No. Issue: Date: File: Page:

ASG 11-Feb-16 SG1010MP-CARE 2 of 10
3.4. Fallback Copy of the Active Package

ZWKS:MODE=FULL,NAME=FBDDMMYY,DIRE=FBDDMMYY:;
ZWKI;
ZWQO:CR;

3.5. Block Command Calendar (COMCAL)

Login using username/password: CALEND/CALEND123

ZICL;
ZICB:1&&3(all):BLOCK;
ZICL; ---> verify that all are in BLC state

3.6. Check all existing PCU in the BSC

ZWTI:PI:BCSU,0;

Check for all BCSU in BSC. All BCSU should have the same number of PCUs.

ZUSI:COMP;

Take note of PCU index & BCSU physical address. (enclosed in red box)

3.7. Check PCU traffic for all PCU

Doc. No. Issue: Date: File: Page:

ASG 11-Feb-16 SG1010MP-CARE 3 of 10
 ZDDS;
ZRS:XX,YYBF
XX - BCSU physical address
YY - PCU address

Example, for BSCU-5 / PCU-4, command is:

ZDDS;
ZRS:35,50BF;
dpcutbf
exit
ZZZE

Do this for all existing BCSU-PCU pair. Sample printout, PCU with normal PS traffic:

Sample printout, PCU with ZERO PS uplink & downlink traffic:

Doc. No. Issue: Date: File: Page:

ASG 11-Feb-16 SG1010MP-CARE 4 of 10
 Take note of BCSU/PCU pair with ZERO traffic (if any). Need to
double check the jumper settings of PCU card when BCSU is in SE-
NH status.

3.8. FBSC cabinet layout

Take note of the HW position for the new PCU to be installed.

4. Actual PCU HW Expansion and Creation

Note: In this step, expansion is done 1 BCSU at a time. We start with the SP-EX
BCSU. Once done with the first BCSU, we execute BCSU swithcover to the next
target BCSU and so on, until new HW is installed and configured for all existing
BCSUs in the BSC.

4.1. Put SP-EX BCSU to SE-NH

ZUSI:BCSU;
ZUSC:BCSU,X:TE;
ZUSC:BCSU,X:SE;
ZUSC:BCSU,X:SE;
ZUSI:BCSU;

4.2. Check PCU Jumper Settings

PCUs should have the correct jumper settings otherwise the PCU will have ZERO PS traffic.

Doc. No. Issue: Date: File: Page:

ASG 11-Feb-16 SG1010MP-CARE 5 of 10
4.3. Install PCU HW (in correct slot)

See cabinet layout photo for PCU HW positioning.

4.4. Create New HW in BSC

Note: create/execute commands only for the new PCU HW installed in specific
BCSU.

Doc. No. Issue: Date: File: Page:

ASG 11-Feb-16 SG1010MP-CARE 6 of 10
 ZWTI:P:BCSU,X:PCU2_E,Y:;
where: X - BCSU number
Y - PCU index

Below photo, sample of correctly created and connected PCU. All TSLs are set to 1.

Doc. No. Issue: Date: File: Page:

ASG 11-Feb-16 SG1010MP-CARE 7 of 10
 Note: There should be no command execution error after ZWTP and ZWUC
commands. All PCM TSLs should be 1 after ZWUC is executed. If execution error
occurs or not all TSL is set to 1, please contact Nokia PIC for support.

4.5. Create PCU Interface

ZQRI:BCSU,X;

ZQRA:BCSU,X:PCU2E,Y:IFETH0:(MTU SIZE):UP:;
ZQRA:BCSU,X:PCU2E,Y:IFETH1:(MTU SIZE):UP:;
MTU size - depend on default value from ZQRI printout.

4.6. Diagnose BCSU

Diagnose BCSU to test if new PCU HW is ok.

ZUSI:BCSU;
ZUSC:BCSU,X:SE;
ZUSC:BCSU,X:TE;
ZUDU:BCSU,X;
ZUDQ;
ZUDH:BCSU,X;
Note: If diagnostic result is UNIT NOT OK (FAULTY), set BCSU to SE-NH,
unplug/plug HW then diagnose BCSU again. If still UNIT NOT OK, replace PCU.
If diagnostic result is UNIT OK, set BCSU to SP-EX.

4.7. Set BCSU to SP-EX

ZUSC:BCSU,X:SP,:C=DSK,;
ZUSI:BCSU;
Note: After BCSU is back to SP-EX, wait 5 minutes before executing switchover.

4.8. Switchover BCSU to the Next Target BCSU

ZUSC:BCSU,Z:SP;
ZUSI:COMP;
Z - next target BCSU
4.9. Check PCU Traffic

Once BCSU-X is in WO-EX state, check the traffic for all PCU. Refer to Step 3.6.
Note: New PCU will have no traffic since there is no BTS connected yet.
Old/existing PCUs should handle PS traffic.
If everything is normal, repeat Step 4 for all active BCSUs in the BSC.

Doc. No. Issue: Date: File: Page:

ASG 11-Feb-16 SG1010MP-CARE 8 of 10
 Proceed to Step 5 once HW expansion for all BCSU is completed.

5. Update EQUIPM Database

Once all PCU are installed, update EQUIPM database.

ZDBC:EQUIPM,0;
ZDBS:EQUIPM,0;

6. Requirements After PCU Expansion

6.1. Check alarms, Sigtran/GB/Unit/BTS states, CS/PS traffic, etc.

ZAHO;
ZAHP:::2013-01-01;
ZEOL;
ZEOH:2013-01-01;
ZIGO::USERID=ALL::;

ZWTI:P;
ZWTI:U;
ZUSI;
ZUSI:COMP;
ZFXI:NSEI=0&&65535;
ZFXL:PSEI=0&&99:ALL;
ZNET;
ZOYI::A;
ZEEI;
ZEEL;
ZEEL:BL;
ZEEI::BCSU:;
ZIFO:OMU:MEASUR;
ZIFI:OMU:MEASUR;
ZISI;
ZDBS:BSDATA,0;
ZDBS:PDDATA,0;
ZDBS:OEDATA,0;
ZDBS:EQUIPM,0;
ZDBS:ILDATA,0;

Check ETPA traffic for all existing units:

ZDDS:ETPA,0;
detpcs
exit

Take Computer logs (only for existing computer units):

ZDDE:OMU:"ZGDC";
ZDDE:OMU:"ZGSC";
ZDDE:MCMU,0:"ZGDC";
ZDDE:MCMU,0:"ZGSC";
ZDDE:MCMU,1:"ZGDC";
ZDDE:MCMU,1:"ZGSC";
ZDDE:BCSU,0:"ZGDC";
ZDDE:BCSU,0:"ZGSC";
ZDDE:BCSU,1:"ZGDC";
ZDDE:BCSU,1:"ZGSC";
ZDDE:BCSU,2:"ZGDC";
ZDDE:BCSU,2:"ZGSC";

Doc. No. Issue: Date: File: Page:

ASG 11-Feb-16 SG1010MP-CARE 9 of 10
 ZDDE:BCSU,3:"ZGDC";
ZDDE:BCSU,3:"ZGSC";
ZDDE:BCSU,4:"ZGDC";
ZDDE:BCSU,4:"ZGSC";
ZDDE:BCSU,5:"ZGDC";
ZDDE:BCSU,5:"ZGSC";
ZDDE:BCSU,6:"ZGDC";
ZDDE:BCSU,6:"ZGSC";

6.2. Check all PCU in the BSC

ZWTI:PI:BCSU,0;
ZWTI:P:BCSU,0;

Check that new PCU is alreay created in all BCSU. All BCSU should have the same number of
PCUs.

6.3. Check PCU traffic for all PCU

Refer to Step 3.7.

6.4. Unblock Command Calendar (COMCAL)

Login using username/password: CALEND/CALEND123

ZICL;
ZICB:1&&3(all):UNBLOCK;
ZICL; ---> verify that all are in TIM state

6.5. Fallback Copy of the Active Package

ZWKS:MODE=FULL,NAME=FBDDMMYY,DIRE=FBDDMMYY:;
ZWKI;
ZWQO:CR;

7. PCU HW Expansion Complete

Verify that everything is normal in the BSC.

--> BTS/BSC alarms
--> CS traffic
--> PS traffic
--> SIGTRAN links
--> GB links
--> HW states
--> BTS states
--> etc.

Doc. No. Issue: Date: File: Page:

ASG 11-Feb-16 SG1010MP-CARE 10 of 10