Method Of Procedure

FBSC GB Links Expansion (L3 Configuration without MultiPoint SGSN

feature)

1. Purpose

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

doing GB Links expansion in Flexi BSC (L3 configuration without MultiPoint
SGSN feature).

2. Customer Information

Customer Name INDOSAT

Site name
Products Flexi BSC
Project Description FBSC GB Links Expansion (L3 Configuration without
MultiPoint SGSN Feature)

3. Requirements Before PCU Expansion

3.1. Licences

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

Install additional Licence Keys if needed.

FTP new Licence Keys to NODEF/LICENCE directory
ZW7L:(LK NAME):ON:;
ZW7I:LIC,FULL:;
ZW7I:FEA,FULL:FEA=7&13,;
Check that additional LKs were successfully installed.

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;

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

ASG 11-Feb-16 SG1010MP-CARE 1 of 10
3.3. Test BTS

Nominate one test BTS (preferrably without DAP). Test BTS will be attached to all new GB
links to verify that the new GB links can handle PS traffic.
3.4. 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";
ZDDE:BCSU,3:"ZGDC";
ZDDE:BCSU,3:"ZGSC";
ZDDE:BCSU,4:"ZGDC";
ZDDE:BCSU,4:"ZGSC";

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

ASG 11-Feb-16 SG1010MP-CARE 2 of 10
 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 with the GB

Links expansion.

3.5. Fallback Copy of the Active Package

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

3.6. 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.7. 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).

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

ASG 11-Feb-16 SG1010MP-CARE 3 of 10
3.8. Check PCU traffic for all PCU

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.9. FBSC cabinet layout

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

4. Actual GB Links Expansion (without MultiPoint SGSN Feature)

Note: In this step, it is assumed that HW expansion was implemented, new PCU
interfaces were defined and additional Licence Keys already installed.

4.1. Check Existing GB Parameters

ZFXI:NSEI=0&&65535;
ZFXL:PSEI=0&&99;

4.2. Check that PCU Interfaces are already created.

ZUSI:BCSU;
ZQRI:BCSU;
Note: Double check that all IFETH interface were created for all new PCU modules.

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

ASG 11-Feb-16 SG1010MP-CARE 5 of 10
4.3. Define new PCU IP Address

ZQRI:BCSU;
ZQRN:BCSU,X:PCU2E,Y:IFETH0:"(PCU IP Address)",(Subnet Mask),L,:;
ZQRN:BCSU,X:PCU2E,Y:IFETH1:"(PCU IP Address)",(Subnet Mask),L,:;
PCU IP Addrress and Subnet Mask - taken from provided datafill/IP plan
ZQRI:BCSU;
X - BCSU index
Y - new PCU index
Define IP address in all new PCUs except for SP-EX BCSU! PCU IP address should be in the
same network as with the existing PCU IP addresses.

Note: VERY IMPORTANT! DO NOT define IP ADDRESS for the

SP-EX BCSU!

4.4. Define new PCU Static Route

ZQKB:BCSU;
ZQKC:BCSU,X:PCU2E,Y::"(GB gateway IP Address)":LOG;
ZQKB:BCSU;
Define static route for all new PCUs except for new PCU in SP-EX BCSU! Gateway IP address
should be the SAME with the existing GB gateway IP.

Note: VERY IMPORTANT! DO NOT define static route for the

SP-EX BCSU!

4.5. Check SWU Configuration (L3)

ZW6T:SWU,Z;

SWU 2 and 3 should show this configuration.

sh runn

Port 1/1/8-1/1/22 (PCU ports in SWU) should be assigned to VLAN50.

sh vlan

Port 1/1/8-1/1/22 (PCU ports in SWU) should be assigned to VLAN50.

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

ASG 11-Feb-16 SG1010MP-CARE 6 of 10
 SWU 4 and 5 should show this configuration.
sh runn

Port 1/1/3-1/1/22 (PCU ports in SWU) should be assigned to VLAN50.

sh vlan

Port 1/1/3-1/1/22 (PCU ports in SWU) should be assigned to VLAN50.

Note: Make the necessary changes if needed.

4.6. Test Ping from PCU to GB Gateway IP Address

PCU to GB gateway IP.

ZQRX:BCSU,X:PCU2E,Y::IP="(GB gateway IP Address)":;

PCU to SGSN IP.

ZQRX:BCSU,X:PCU2E,Y::IP="(SGSN IP Address)":;
Test ping for all new PCU. Result should be OK.

4.7. Create Additional PSEI

ZFXA:PSEI=P,BCSU=X,PCU=Y;
P - new PSEI number
X - BCSU index
Y - PCU index
Create new PSEI for all new PCUs.

ZFXL: PSEI=0&&99;

Check that all PSEI are in WORKING state.

4.8. Create GB Links (NSEI/NSVLI)

ZFXK:NSVLI=(NSVLI#),NAME=(NAME),NSEI=(NSEI#),PSEI=(PSEI#):LPNBR=(LPNBR#),PRE
=(Y or N):RIP="(RIP/SGSN IP)",RPNBR=(RPNBR#),:;
Get data from provided datafill. Create for all new PCUs.

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

ASG 11-Feb-16 SG1010MP-CARE 7 of 10
 ZFXI:NSEI=(newNSEI#);
ZFXI:NSEI=0&&65535;

Check that all new NSEIs are in WO-EX state.

4.9. Add NSEI in all existing Routing Areas

ZEBP;
ZEBH:MCC=510,MNC=01,LAC=(LAC#),RAC=(RAC#):A:NSEI=(newNSEI_1)& (newNSEI_2) &
(newNSEI_Last) ;

Note:
Maximum 10 NSEIs per ZEBH command execution.
MCC and MNC is unique for Indosat network.
Add all new NSEIs to all Routing Areas in the BSC.

Make sure that all new NSEIs are included in the NSEI list of all existing Routing Areas.

4.10. Attach Test BTS to New NSEIs and Check PCU Traffic

Test BTS without DAP:

ZEQO:BTS=(BTS#):GPRS;
ZEQV:BTS=(BTS#):GENA=N;
ZEQV:BTS=(BTS#):GENA=Y:NSEI=(newNSEI_1);
ZEQO:BTS=(BTS#):GPRS;

Test BTS with DAP:

ZEQO:BTS=(BTS#):GPRS;
ZEQV:BTS=(BTS#):GENA=N;
Disable GENA for all sectors of the test BTS.

ZEEI:BCF=(BCF#);
Get the ET number used for DAP pool.

ZESI;

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

ASG 11-Feb-16 SG1010MP-CARE 8 of 10
 Check DAP ID of the ET used.

ZESM:ID=(DAP ID#),PSEI=(PSEI#):;
ZEQV:BTS=(BTS#):GENA=Y:PSEI=(PSEI#);
Check PCU traffic. PCU should handle PS traffic. If ZERO PS traffic, troubleshoot by BCSU
switchover (2 times) or by rechecking PCU jumper settings.

Detach & attach test BTS to all new GB links to test if PS traffic is handled by the PCU.

4.11. Ready for NSEI Rebalancing

Once all GB links are created, all PSEI status is WORKING, all NSEI status WO-EX and new
NSEIs tested and can handle PS traffic, the BSC is now ready for NSEI Rebalancing.

5. Requirements After GB Links Expansion

5.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";

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

ASG 11-Feb-16 SG1010MP-CARE 9 of 10
 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";

5.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.

5.3. Check PCU traffic for all PCU

Refer to Step 3.8.

5.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

5.5. Fallback Copy of the Active Package

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

6. 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