fm bss technical document (2).pdf

For internal use only 1 (55)

Bharti FM-BSS 24-Apr-2014

For internal use only Nokia Solutions and Networks

BHARTI GDC FM-BSS Troubleshooting Doc for Day to Day Activities




TABLE OF CONTENTS

1 WDU Replacement ............................ ..............................................3

2 NSEI Deletion Creation.. 10

1. NSEI deletion creation Frame based11

2. NSEI shifting to another BCSU Frame based12

3. NSEI deletion creation GB ov IP based..13

4. PCU Pooling Implementation

3 Discriminator Clearance1 6

1. Discriminator clearance.17

2. BSDATA & PDDATA clearance18

3. OMU & MCMU process restart.18

4. CMISE application restart..19

4 Procedure to Take BSC Backup on Laptop .20

5 Revert BSC on Fall Back ( Delete the DBI* and DBA* files)26

6 Incraese BSC Alarm Buffer Size ..28

7 BSC Fallback copying Error ..31

2663-DUMPING ERROR IN DATABASE MANAGER..32

2393-FALLBACK COPYING TERMINATED IN ERROR..32

8 EMB Troubleshooting.36

9 MB Troubleshooting40

10 BSC Fallback & MO Disk (FDU) Backup .47

11 BSC Login via OMU (CPU J7 Port) ...51

12 PCU Pooling Concept/Troubleshooting .53

13




WDU REPLACEMENT PROCEDURE




REPLACING A HARD DISK UNIT (WDU)

MUST REMEMBER

You should have an initialized WDU at your disposal. Here we assume WDU-1 is faulty and during the activity

please mind the below points.

1) Block Command Calendars 2) Make sure there should be no other activity is in process during the replication process i..e.step-22 3) Stop all activities on the SCSI bus(like FDU) where you are making changes

PROCEDURE

1. Find the states of the WDUs (EG:-WDU-1)

ZISI: :WDU,1:;

2. Dump the data files from OMU and MCMU to disks of OMU

ZDFC:OMU;

ZDFC:MCMU,0; (Working MCMU)

NORMALLY THESE COMMAND END WITH ERROR"

/*** DX ERROR: 11502 ***/

/*** UPDATE FAILED TO I/O UNIT W1 ***/

3. Copy ALL databases from memory to disk

ZDBC:BSDATA,0;

ZDBC:EQUIPM,0;

ZDBC:OEDATA,0;

ZDBC:ILDATA,0:;

ZDBC:PDDATA,0:;

4. See the database file in BSC

ZDBL:;

ZDUR;

"EXP.

BSC3i B012GAY1 2010-10-24 02:46:26

DATABASE OCCURRENCE UNIT DB FAMILY FILES BASE DB IDENTIFIER

BSDATA 0 MCMU 019B 06390000 0009

EQUIPM 0 OMU 01C5 06A50000 0011

OEDATA 0 MCMU 0262 07BD0000 0022




ILDATA 0 OMU 0679 0B640000 0069

PDDATA 0 MCMU 06AE 0BA60000 006A

5. Prevent file updates and disk updates of databases

ZDUP:;

6. Prevent file updates and disk updates of databases

ZDBP:,:DISK;

ZDBP:BSDATA,0:DISK;

ZDBP:EQUIPM,0:DISK:;

ZDBP:OEDATA,0:DISK:;

ZDBP:ILDATA,0:DISK:;

ZDBP:PDDATA,0:DISK:;

7. Check for database either they get Prevent or not

ZDBS:BSDATA,0;

ZDBS:EQUIPM,0;

ZDBS:OEDATA,0;

ZDBS:ILDATA,0;

ZDBS:PDDATA,0;

NOTE: O/P should be

MEMORY UPDATES PREVENTED SHOULD BE " YES " STATE

DISK UPDATES PREVENTED SHOULD BE " YES " STATE

8. Check that all databases have been unpacked from the disk log to the disk database (DBX)

The command unpacks the disk logs if they are not empty.

ZDBX:,;

ZDBX:BSDATA,0:;

ZDBX:PDDATA,0:;

ZDBX:ILDATA,0:;

ZDBX:EQUIPM,0:;

ZDBX:OEDATA,0:;

9. CHECK THE PLUG-IN INFO OR FIND THE TRACK NO OF PLUGIN UNIT ZWTI:P:OMU:;

10. Block the WDU you are changing to BL-US state

ZISC:,,:,:;

ZISC::WDU,1:BL-US,;

ZISC::WDU,1:MI-US,;

11. Block the other I/O devices (FDU) on the same unit pair's SCSI bus




ZISC::FDU,00:BL-US,;

12. Check that the state of the hard disk to be replaced is correct (BL-US/MI-US)

ZISI:,,:,;

13. Remove the WDU from the OMU computer cartridge:

1) Switch off power by pressing the 'OFF' button and wait about 7 seconds, until the 'Power Off' led lights.

2) Remove the WDU unit from the cartridge.

14. Check the jumper settings of the new WDU.

15. Install the new WDU to the OMU computer cartridge:

Install the WDU to the cartridge and wait about 3 seconds, Until the 'OFF' led is off.

16. After placing new WDU, Change the state of the new WDU to WO-ID (ISC)

ZISC:,,:,:;

ZISC::WDU,1:WO-ID,;

17. Check that the new disk is the backup disk (WB) (IWQ)

***Note that the command does not end in a semicolon.

ZIWQ:,,

BY COMPAIRE THIS WITH ZISI::WDU;

IF WDU-0 is Faulty then WS=1, WB=0

IF WDU-1 is Faulty then WS=0, WB=1

18. Format the new hard disk. (This process can take 30 to 60 min.)

Initialize WDU

ZIWI:,OMU:WB,F5,NAME,FFF,02,AG:;

Format WDU

ZIWK:,:WB,,NAME,FF,,AG:;

19. Change the states of other I/O devices on the same SCSI bus (Change the states of FDU to WO-BU)

20. Diagnose the WDU (UDD)

Before diagnostic, change the state of WDU to TE-ID using command ZISC::WDU,1:TE-ID;

ZUDD: , , : , ;

ZUDD:OMU,0:WDU,1;




If the diagnosis is successful, you will see diagnostic report 3999 DIAGNOSIS EXECUTED - UNIT OK

21. Change the working state of the new WDU to WO-BU (ISC)

ZISC:,,:,:;

ZISC:,OMU:WDU,1:WO-BU;

22. Copy the system WDU to the new WDU (IPS) including subdirectories, using the default and active build directory name 'ASE_1_28_0'. Use ZWQO:CR; to verify build directory name.

ZIWY:S:SYSTEM=,UNIT=OMU,PATH=/,DRIVE=WDU-S,; (Create Source)

ZIWY:D:SYSTEM=,UNIT=OMU,PATH=/,DRIVE=WDU-B,; (Create Destination)

ZIBC:,,,,,,,,,DIR:; (Copy Source to Destination)

****IF Files are not getting transfer to new disk using above commands, then need to create source

and destination using below commands****

ZIPS:,,,,:,,,,:,;

ZIPS:"OMU",WDU-S,/ASB_1_34_0,:,WDU-B,/,:DIR=INC,NAME=COPY,;

ZIPS:OMU,WDU-S,/ASC_1_40_0,:,WDU-B,/,:DIR=INC,NAME=COPY; OR

ZIPS:,WDU-S,/,,:,WDU-B,/,:NAME=COPY,DIR=INC,::;

Now, Check the progress of the copy task to see when it is ready.

ZIPI: NAME=;

23. Kill GEORGE Use service terminal command to prevent the log files of Q3 Disseminator getting corrupted.

ZDDS:;

00-MAN>OD: 2B1

24. Remove LOGRECS* files from the disks LFILES on both OMU disks

Use service terminal command MD in order to maintain the required syncronisation status between

DEEGUT and GEORGE during the hard disk change. Use ZWQO:CR; to verify build directory name. Here

build directory name is ASE_1_28_0.

ZMD: W0-//LFILES/LOGR*.*

ZMD: W1-//LFILES/LOGR*.*

ZDDS:;




WELCOME TO SERVICE TERMINAL DIALOGUE

00- MAN>ZMD:W1-/ASE_1_28_0/LFILES/LOGR*.* (Also use the same command for W0)

Sample Output:

DELETING FILE: W1-/ASE_1_28_0/LFILES/LOGRECSD01.DAT:00

EXECUTED


EXECUTED


EXECUTED


EXECUTED

00000004 FILES DELETED

25. Resume updates of disks and memory file disk copies of the databases which you prevented before changing the WDU

ZDUR;

ZDBR:BSDATA,0:DISK;

ZDBR:EQUIPM,0:DISK:;

ZDBR:OEDATA,0:DISK:;

ZDBR:ILDATA,0:DISK:;

ZDBR:PDDATA,0:DISK:;

26. Check that the database states are restored to 'normal' or 'dumping' (DBS)

ZDBS:,; //The command displays the states of the databases.

ZDBS:BSDATA,0;

ZDBS:EQUIPM,0;

ZDBS:OEDATA,0;

ZDBS:ILDATA,0;

ZDBS:PDDATA,0;

NOTE: O/P should be

MEMORY UPDATES PREVENTED SHOULD BE " NO " STATE

DISK UPDATES PREVENTED SHOULD BE " NO " STATE

27. Copy the data from database to disk

ZDBC:,;

ZDBC:BSDATA,0:;

ZDBC:EQUIPM,0:;

ZDBC:OEDATA,0:;

ZDBC:ILDATA,0:;

ZDBC:PDDATA,0:;




28. Check that the states of the units are correct (WO-EX, SP-EX) (USI)

ZUSI:,;

29. Restart OMU (USU) ZUSU:OMU:C=DSK;

30. Take Fall Back

ZWKS:MODE=FULL,NAME=FB011211,DIRE-FB011211:;

31. Check for consistency of both BU & FB packages

ZWQB:NAME=directory_name:FORM=FAILED:;

SOME POINTS NEED TO BE CHECKED AFTER THE ACTIVITY

1) Check state of both WDU

2) Check Measurements are getting transfer or not atleast for next two hours. If found any issue escalate the same to your SPOC and perform necessary action.

3) Check for critical alarms at BSC.




NSEI DELETION & CREATION STEPS




NSEI DELETION AND CREATION STEPS (FRAME BASED)

PROCESS-1

1) Find the Name of NSEI by executing below command and take all required pre activity log.

ZFXO:BCSU=0&&6:;

ZFXO:BCSU=0&&6:BTS;

2) First note down the given below parameter very carefully.

NS-VC ID 06655 (for eg)

Name NS_TEL65_5

DLCI 655

CIR 448

Bearer ID 0005

Channel Name (BCN) BSC65TEL_5

3) Either shift the DAPs to another NSEI or make GENA disable for all BTS which are attached to particular NSEI on which we are working.

ZEQV:SEG=:GENA=N:;

4) Lock the NSEI using below command

ZFXS:NAME=:L;

5) Delete NSEI using the below command

ZFXD:NAME=;

6) Create NSEI (NSEI SAME AS NSVCI)

ZFXC:NSVCI=06655;NAME=NS_TEL65_5,NSEI=06655:DLCI=655,CIR=448:BCN=BSC65TEL_5:;

7) Unlock NSEI and check NSEI state

ZEFS:NAME=nsei_name:U;

8) Attach cells to NSEI after coming to WO state by making GENA enable for all BTS.

ZEQV:BTS=bts_no:GENA=Y:;




STEPS TO SHIFT NSEI TO ANOTHER BCSU

PROCESS-2

1) First of all perform STEP-1 to STEP-5 as given in process-1 and then only delete the Frame Relay (Bearear ID) using below command. Here Bearear ID is 5.

ZFUD:5,NS_TEL65_5:;

2) Create Frame Relay (Bearear ID) to another BCSU

ZFUC:5,NS_TEL65_5:5:106,17:BCSU,1,3:;

Here

5 is Bearear ID,

NS_TEL65_5 is NSVCI Name,

5=320/64 DIR/64

17 is starting PCM

Sample Output

BEARER BEARER BEARER CHANNEL EXTTIME

ID NAME RATE (KBIT/S) PCM SLOTS UNIT TERM FUNCT

------ ---------- -------------- ---- ------ ------ ---- -------------------------------------------------------------

315 B180KOC1_2 384 530 13-18 BCSU-3 3 0

3) Now execute STEP-6, 7 & 8 as given in the above process-1.




NSEI DELETION AND CREATION STEPS (GB OV IP BASED)

PROCESS-3

1) Find out the number (i.e. ID) of NSEI & PSEI by executing below command and take all required pre activity log.

ZFXI:NSVLI=0&&65535:;

ZFXL:PSEI=0&&99:BTS:;

ZQRI;

ZQKB;

2) First note down the given below parameter very carefully.

i. IP address of PCU IFETH port using command ZQRI

Say IP for BCSU-1 & PCU2D-3 IFETH0/ IFETH1 is 172.26.128.39

IP for BCSU-1 & PCU2D-4 IFETH0/IFETH1 is 172.26.128.40

ii. Default Gateway IP address using command ZQKB. Here Gateway IP is 172.26.128.34

iii. Note down the NSEI & PSEI number. Here, NSEI are 1783 & 1784 and PSEI are 2 & 3. If NSVCI not found error encounter, then get the down NSVLI NO from PSEI data.

iv. Note Down NSEI Name, RSW, RDW, LPNBR, RPNBR & RIP(REMOTE IP ADDRESS) using ZFXL command.

NAME= NS_JRK78_3 and NS_JRK78_4

RIP= 10.246.224.43 RSW=1,

RDW=1,

LPNBR=50023 and 50024,

RPNBR= 50023 and 50024,

v. Note down the segment using below command

ZEBP:NSEI=;

3) Disable GENA in all cells attached to particular NSEI.

ZEQV:SEG=:GENA=N:;

4) Delete the problematic NETWORK SERVICES VIRTUAL LINK (NSVLI).

ZFXH:NSVLI=1783:;

ZFXH:NSVLI=1784:;

5) Delete PACKET SERVICE ENTITY (PSEI, Corresponding to NSVLI)

ZFXE:PSEI=2:;

ZFXE:PSEI=3:;




6) Delete Static Route (For static route check ZQKB; output)

ZQKA:(STATIC Route no):;

7) Delete IP addresse from interfaces (IFETH0 & IFETH1)

ZQRG:BCSU,1:PCU2D,3:IFETH0:"172.26.128.39":;

ZQRG:BCSU,1:PCU2D,3:IFETH1:"172.26.128.39":;

COMMAND format If PCU_B PIU is in use

ZQRG:BCSU,:PCUB,:IFETH0:"":;

ZQRG:BCSU,:PCUB,:IFETH1:"":;

COMMAND format If PCU2_D PIU is in use

ZQRG:BCSU,:PCU2D,:IFETH0:"":;

ZQRG:BCSU,:PCU2D,:IFETH1:"":;

8) Now check for ETH interfaces using command ZQRI;

9) Configure network interfaces

ZQRA:BCSU,1:PCU2D,3:IFETH0:::;

ZQRA:BCSU,1:PCU2D,3:IFETH1:::;

10) Configure IP addresses to IFETH

ZQRN:BCSU,1:PCU2D,3:IFETH0,:"172.26.128.39",27,L::;

ZQRN:BCSU,1:PCU2D,3:IFETH1,:"172.26.128.39",27,L::;

OR (Use below command instead of above two)

ZQRN:BCSU,1:PCU2D,3:IFETH0,IFETH1:"172.26.128.39",27,L::;

COMMAND Format if PCU_B is used

ZQRN:BCSU,:PCUB,:IFETH0,IFETH1:"",NET MASK LENGTH( Eg- 27),L,::;

COMMAND Format if PCU2_D is used

ZQRN:BCSU,:PCU2D,:IFETH0,IFETH1:"",NET MASK LENGTH( Eg-

27),L,::;

11) Create Static Route

ZQKC:BCSU,1:PCU2D,3::"172.26.128.34":LOG:;

ZQKC:BCSU,1:PCU2D,4::"172.26.128.34":LOG:;

COMMAND Format

ZQKC:BCSU,BCSU NO:PCU_B/PCU2_D,PCU NO::"GATE WAY IP ADDRESS":LOG:;




12) Test host reachability (PING/TRACEROUTE)

ZQRX:BCSU,1:PCU2D,3::IP="172.26.128.34",:;

ZQRX:BCSU,1:PCU2D,4::IP="172.26.128.34",:;

13) If host reachabily is ok then create PSE

ZFXA:PSEI=2,BCSU=1,PCU=3;

ZFXA:PSEI=3,BCSU=1,PCU=4;

COMMAND Format

ZFXA:PSEI=02,BCSU=BCSU NO ,PCU=PCU NO,:;

14) Create NSVLI (NSEI number same as NSVLI number)

ZFXK:NSVLI=1783,NAME=NS_JRK78_3,NSEI=1783,PSEI=2:LPNBR=50023,PRE=N:RPNBR=50023,RSW=1,RD

W=1, RIP="10.246.224.43";

ZFXK:NSVLI=1784,NAME=NS_JRK78_4,NSEI=1784,PSEI=3:LPNBR=50024,PRE=N:RPNBR=50024,RSW=1,RD

W=1, RIP="10.246.224.43";

COMMAND Format

ZFXK:NSVLI=,NAME=,NSEI=,PSEI=:LPNBR=,PRE=N:RPNBR=, RSW=001, RDW=001,RIP="REMOTE IP ADDRESS":;

RSW, RDW, LPNBR, RPNBR & REMOTE IP ADDRESS will get from STEP-2 or Prelog.

15) Check for NSEI state and enable GENA in all BTS/Segments.




DISCRIMINATOR CLEARANCE PROCEDURE




DISCRIMINATOR CLEARANCE

Discriminator clearance activity can be performed during below given scenario-

1) RNW Network Plan Database state is INTERRUPTED BY SYSTEM. Use ZEEK command to check the same.

(Execute Step-A, B, C)

2) Sometimes when MO Upload getting failed.

3) Not able to lock/Unlock sector or site. (Execute Step- B, C, D & G only one by one)

4) Getting Fetching Error while CM performing BTS software download from software manager

5) Getting error NO RESOURCE FOR REQUESTED TASK while changing name using CM edtor.

MUST REMEMBER BEFORE ACTIVITY

1) Plan the activity during maintenance window with proper outage approval. 2) Remember to make a valid FALLBACK 3) Stop command Calendar and resume after completion of activity

PROCEDURE

A) If problem is related to Upload than first of all check ZEAT output, and delete all the cells captured. If output is blank than perform the next procedure.

B) Discriminator clearance Steps

ZDDS:;

ZL:2

ZLE:2,EXODUSGX

2

D:1,DEAD

After performing the above, ensure that all are 0000 except for Windows currently in use, by using

the following commands and exit:

S:1

S:2

S:3

S:4

SAMPLE OUTPUT

*************************************

Windows currently in use = 0001

Last window written to disk = 0000

Number of records in the que = 0000

Amount of bytes used = 0000

Identifier of the first record = 0000




Identifier of the last record = 0000

Last ULA record written = 0000

*************************************

Now, delete the Dissiminator Extension, using the command L:2 and exit the service terminal using

ZE.

C) Change plan database state to clear in active database (BSDATA)

ZDDS:;

ZLE:Q,DAEMONGX

ZQD:6390000,4505,19B

ZQM:412,T:00,XD5CEF,XD5CEF,XD5CEF

Wait for 5 min and then go to the next step

D) Change at last plan database state in plan database (PDDATA)

ZQD:BA6002A,4505,6AE


Now, Perform OMU restart from Disk( C= DSK)

Please check ZEEK (it should be clear) and if still problem exists please restart below given process on

OMU as well as both active MCMU's and check.

E) Clear both the DOWNLOAD & UPLOAD directories

ZIWD::WSB, DEF:DOWNLOAD:%,%;

ZIWD::WSB, DEF:UPLOAD:%,%;

F) Clear the SEND2NW directory

ZIWD::WSB, NODEF:SEND2NW:%,%;

G) Restart CMISE applications ZQDI;

Lock CMISE applications

ZQDG:BSC938784A,LOC; (change C number of BSC, marked in red color)

ZQDG:BSC938784EHA,LOC;

ZQDG:OMC000000D1,LOC;

ZQDG:OMC000000BP,LOC;




Unlock CMISE applications

ZQDG:BSC938784A,UNL;

ZQDG:BSC938784EHA,UNL;

ZQDG:OMC000000D1,UNL;

ZQDG:OMC000000BP,UNL;

H) Perform OMU code loading restart ZUSU:OMU:C=DSK;




PROCEDURE TO TAKE BSC BACKUP ON LAPTOP




TAKING BSC BACKUP ON LAPTOP

1) First install FTT software in laptop. If already installed go to the next step.

2) Take the valid Fallback with below MML command.

ZWKS:MODE=FULL,NAME=FBddmmyy,DIRE=FB_ddmmyy;

3) Use- ZQRI:; command to check BSC IP.

4) In BSC3i, use Ethernet port available in ESB card in LANU or MCMU (ETH1 or ETH2) to connect laptop trough FTT.

In BSC2i, use Ethernet port available in OMU section.

5) Open FTT application to take BACK UP on Laptop.




6) Go to Setup in menu bar of FTT application

Continue.




7) Make the new connection for BSC login (Provide IP, User Name & Password) & save.

Continue.




8) Open the New connection, click on Open FTP tab. In the left side, BSC data shown & in the right side Laptop C drive data shown.

9) Open the Fallback directory in the BSC side (left side)

10) Make a folder (with name fallback) in C drive, and then make all subfolders with the same name as in Fallback directory in left side.

Continue.




11) Then Copy files from each folder with the same folders. (e.g.: files in left side under the folder BLCODE should be copied in the right side (C drive) with the folder name BLCODE.

BSC SIDE LAPTOP SIDE

BLCODE (all files) --------------------------------------- BLCODE (all files)

-----------------------------------------------Process Completed------------------------------------------------------------




RVERT BSC ON FALL-BACK




STEP TO REVERT BSC ON FALL BACK

1.1 Restoring the software builds if the BU build is faulty and MML working

The fallback activation restores the situation that was present at the time the fallback was made. If

any changes have been made after the last fallback, the changes must be made again.

If the BU build is found to be faulty, the FB build can be restored to serve as the BU build.

1) Delete the DBI* and DBA* files from FB Package

ZIWD::WSB,NODEF:,LFILES:DBI%,IMG;

ZIWD::WSB,NODEF:< FB_Package >,LFILES:DBA%,IMG;

2) Verify the consistency of FB package.

ZWQB:NAME=Fallback_name:FORM=FAILED:;

3) hange the FB build to be the default (WSD)

ZWSD:STAT=FB;

Where STAT= Status of the build which need to be restored.

Or

ZWSD:NAME=FB_040506;

Where NAME= Name of the build which need to be restored.

Note Changing the default build causes the system to restart. The system informs the user about

this and asks for verification.

4) When the FB build is working, roll back the status so that the FB build is changed to the BU build.

ZWSR;

5) Verify the consistency of the Build package again and perform BSC health check.




INCREASE ALARM BUFFER SIZE




INCREASE ALARM BUFFER SIZE

Use below given steps to increase alarm buffer size of BSC

1. Interrogate the ALHIST on both Disks

a) ZIWX::WS:LFILES: ALHIST%, %:;

b) ZIWX::WS:LFILES: ALHIST%, %:;

VOLUME NOKIA.DIR: 0 INITIALIZED 08-04-11 REL 5

DIRECTORY OF LFILES LIMIT 2

==========================================================

FILE NAME FILE FILE FILE DATA PAGE 1

VERSION NO LENGTH LENGTH CREATOR ATTR

(H) (H) (DEC) (DEC)

ALHISTGX .ALF 1 AC 614400 614392 02 D

TOTALS 614912 614904 ( INCLUDING FIDS )

FREE LABELS IN DIRECTORY 1089

FREE BLOCKS IN DISK 115943842 ( 80 %) 56613 MB

DISK SIZE 143638992 BLOCKS 70136 MB

2. Delete the files from both Disk

ZIWD:,OMU:WSB,:LFILES:ALHIST%,%,;

3. Create a new file of 2MB

ZIWC::WSB:LFILES:ALHISTGX,ALF,2048000,AB:;

4. Check version of created file

a) ZIWX::WS:LFILES:ALHIST%,%:; b) ZIWX::WB:LFILES:ALHIST%,%:;

VOLUME NOKIA.DIR: 0 INITIALIZED 08-04-11 REL 5

DIRECTORY OF LFILES LIMIT 2

===============================================================

FILE NAME FILE FILE FILE DATA PAGE 1

VERSION NO LENGTH LENGTH CREATOR ATTR

(H) (H) (DEC) (DEC)

ALHISTGX .ALF 1 AC 2048000 0 AB D




TOTALS 2048512 512 ( INCLUDING FIDS )

FREE LABELS IN DIRECTORY 1089

FREE BLOCKS IN DISK 115941042 ( 80 %) 56611 MB

DISK SIZE 143638992 BLOCKS 70136 MB

COMMAND EXECUTED

5. Set default version to new created ALHISTGX file

ZIWF::WSB:LFILES:ALHISTGX,ALF,1:;

6. Reset BSC OMU

ZUSU:OMU:C=DSK,;




BSC FALLBACK COPYING ERROR




BSC FALLBACK COPYING ERROR

2663-DUMPING ERROR IN DATABASE MANAGER

2393-FALLBACK COPYING TERMINATED IN ERROR

RESULT: BSC Fall back will not be possible or terminated if any of these alarm is present in BSC.

Precaution: Need to be execute the activity under senior supervision in night hours with proper outage approval as per process.

PROCEDURE

1) First check WDU state using below command. if both WDU reflect as WO-BU then execute this process otherwise follow the WDU troubleshooting document.

ZISI::WDU;

2) If both WDU are WO-BU, then check ZDBD output to verify disk consistency.

Example:

ZDBD:OMU;

BSC3i BSC78BHU 2012-01-24 13:19:38 DATA OCCUR- DUMPING CONSIST ALLOWED LOG WRITE LOG EMPTY FREE BASE RENCE OR DISK OPERATIONS WRITE ERROR EMPTY ERROR DISKLOG NAME LOADING TO LOG COUNT COUNT COUNT COUNT BUFFERS PDDATA 0 NONE W0 WRITE,MOVE 6 0 5 0 45 ILDATA 0 NONE W0, W1 WRITE,MOVE 0 0 0 0 120 OEDATA 0 NONE W0, W1 WRITE,MOVE 0 0 0 0 30 EQUIPM 0 NONE W0, W1 WRITE,MOVE 0 0 0 0 600 BSDATA 0 NONE W0, W1 WRITE,MOVE 6 0 4 0 45 COMMAND EXECUTED

NOTE: Here PDDATA is not updating on WDU-1. Hence Fallback is not possible or terminating. It may be

possible that other database has the same issue, same process needs to be executed to resolve the fault. I have

seen that this problem will occur mostly in respect of BSDATA & PDDATA.




3) Now Check the output of below command and verify database State & Sub state.

ZDBS:PDDATA,0:;

ZDBS:BSDATA,0:;

ZDBS:ILDATA,0:;

ZDBS:OEDATA,0:;

ZDBS:EQUIPM,0:;

Example: (Only for PDDATA, check for others also)

MAIN LEVEL COMMAND < DBS:PDDATA,0; LOADING PROGRAM VERSION 14.15-0 BSC3i BSC78BHU 2012-01-24 13:09:34 DATABASE OCCURRENCE WO/SP STATE SUBSTATE PDDATA 0 WO DUMPING DUMPING DATABAS PDDATA 0 SP NORMAL NORMAL MEMORY UPDATES DISK UPDATES TRANSACTION BACK UP PREVENTED PREVENTED OVERFLOW IS ON NO NO NO NO LOGBUF ID 000F LATEST TRANSACTIONS: REQUESTOR`S COMPUTER REQUESTOR`S FAMILY TRANSACTION ID TRANSACTION PHASE 4505 0295 008D EXEC SUCCESS 4505 0295 008D EXEC SUCCESS 4505 01B5 0094 EXEC SUCCESS 4505 01B5 0093 EXEC SUCCESS 4505 0295 008C EXEC SUCCESS 4505 06B7 00E7 EXEC SUCCESS 4505 0295 008D EXEC SUCCESS 4505 0295 008D EXEC SUCCESS

COMMAND EXECUTED

NOTE: Here, it is clear that the state (highlighted in above output) of PDDATA is in DUMPING state although

there is no dumping in progress. Hence, when we try for FALLBACK it terminated as dumping is not possible

because PDDATA is already in DUMPING state. It should be in NORMAL state and we will set as normal in

onwards procedure. Also check for other databases for the same.




4) Execute below command.

ZDUR:;

Output

BSC3i BSC78BHU 2012-01-24 12:55:02

RESUMING FILE UPDATES TO DISK

UNIT STATE

------ -------------

OMU NOT PREVENTED

COMMAND EXECUTED

5) Execute below command (Usually end with error)

ZDBR:PDDATA,0:DISK:;

Output

/*** DX ERROR: 10309 ***/

/*** REQUESTED TASK ALREADY DONE ***/

6) Restart the given process in Spare MCMU followed by MCMU code loading restart. (Execute this step if 2663 alarm is present in BSC)

ZDDS:MCMU,;

MAN>ZOKR:1B5

MAN>ZOKR:6B7

Wait for 5 min and perform MCMU code loading restart and repeat the same for another MCMU by

making it spare.

7) Execute below command in OMU using service terminal.

ZDDS:OMU;

-->Change plan database state to CLEAR in active database (BSDATA):

ZDDS:;

ZLE:Q,DAEMONGX

ZQD:6390000,4505,19B


Wait for 5 mins




-->Change at last plan database state in plan database (PDDATA):

ZQD:BA6002A,4505,6AE


8) Restart OMU with code loading

ZUSU:OMU:C=DSK;

9) Now check for database state and disk consistency using step-1 & 2. If found ok go to step-17 (Skip step-10, 11, 12, 13, 14, 15 & 16)

10) If Still issue not resolved delete the Delete the DBA*.IMG and DBINFOGX.IMG files from LFILES directory from BOTH DISKS (ZIWD).

ZIWD::WSB,NODEF:,LFILES:DBI%,IMG;

ZIWD::WSB,NODEF:,LFILES:DBA%,IMG;

11) Restart the DBSMAN process with below service terminal command

ZDDS;

ZODR:142

ZE

12) Wait for the system creates DBA*.IMG and DBINFOGX.IMG files on both disk (about 5-10 min)

13) Dump all the database from the memory to disks (ZDBC) ZDBC:PDDATA,0:; (Use the same cmd for other databases also)

14) Resume memory updates (ZDBR)

15) Give OMU restart with ZUSU:OMU:C=DSK;

16) Check the status of all data base(ZDBS) whether they are in normal state or no

17) Now take valid Fallback and check FB as well as BU consistency using below commands.

ZWKS:MODE=FULL,NAME=FB011211,DIRE-FB011211:;

ZWQB:NAME=directory_name:FORM=FAILED:;

Note: Also check for any service affecting alarm regarding BSC. In case of any major/critical alarms

observed escalate same to their SPOC.




BHARTI FM-BSS EMB TROUBLESHOOTING




EMB TROUBLESHOOTING

A) Check logs of port & other setting ZYFE:ALL; ----- ZYFF:INQ:: ---------ZW6I::::;

Here, I consider EMB-0 faulty.

B) Perform jack out & jack in of ESB card of MCMU-0

C) If still fails the do the following activity (EBSTER Testing):

1- Make EMB-0 in TEST mode. 2- Perform the EBSTER testing of EMB-0.

ZDDS;

ZLP:1,EBS;

Z1

00:EBS> AT:0x007F,0

The O/P should be like this:

Message sent Received test messages using EMB-0 from following units:

============================================================================

0000, 0004, 0005, 0030, 0031, 0032, 0033, 0034, 0035, 0036, 0037, 0038, 0039, 003A

3- Check the MAC addresses of all computer units.

00:EBS> A:0x000:0xFFFF

The O/P should be like:

EMB-0 OK, EMB-1 OK

Unit MAC addr 0 Mac addr 1 MB CID EMB0 EMB1 CPU SCD

=======================================================================

0000 02:00:00:80:00:20 02:00:00:80:00:30 0000 0000 OK OK CP816-A OK

0004 02:00:00:80:01:20 02:00:00:80:01:30 0001 0001 OK OK CP816-A OK

0005 02:00:00:80:02:20 02:00:00:80:02:30 0002 0002 OK OK CP816-A OK

0030 02:00:00:80:03:20 02:00:00:80:03:30 0003 0003 OK OK CP816-A OK

D) Secondly check ESB configuration via local login in ESB card through Serial Port

Login to the serial port of the ESB PIU of MCMU 0 after taking MCMU 0 to SE-NH Mode and EMB 0 to

TE-EX Mode and reload ESB card.

Password:nokia

Ena

Reload

Y

Diagnose the EMB-0.

E) Verify CPU jumper setting




SW1 switch settings

Switch 1 Setting Meaning 1-12 Off Interchangeability code bit 3 2-11 Off Interchangeability code bit 2 3-10 Off Interchangeability code bit 1 4-9 Off Interchangeability code bit 0 5-8 Off Not in use 6-7 Off Message Bus Interface (MBIF) status: OFF = MBIF in use (bit D3 in register 104h reads 0).

In NE installations, when EMB is used, thissetting must be ON = MBIF not in use .

** For interchangeability Code (ICC) setting please refer Jumper setting Document.

F) Replace ESB card with new one and configure the same.

G) Replace CPU card

H) Need to verify below cabling as per requirement & Fault Description

Note:

450 should be connected below cable no. 451 and 452 should be connected below cable no. 453 in ESB26

Cable No CABLE FROM CABLE TO Type Use FU Position FU Positi on BSCC_430 MCMU 0 2.0B 02.2X OMU 2.6B 10.1A CHES012 EMB BSCC_433 MCMU 0 2.0B 02.2R BCSU 0 3.0B 10.1A CHES023 EMB BSCC_434 MCMU 0 2.0B 02.2P BCSU 1 3.4B 10.1A CHES020 EMB BSCC_435 MCMU 0 2.0B 02.2N BCSU 2 3.8B 10.1A CHES017 EMB BSCC_436 MCMU 0 2.0B 02.2L BCSU 3 4.0B 10.1A CHES027 EMB BSCC_437 MCMU 0 2.0B 02.2J BCSU 4 4.4B 10.1A CHES024 EMB BSCC_438 MCMU 0 2.0B 02.2G BCSU 5 4.8B 10.1A CHES021 EMB BSCC_439 MCMU 1 2.3B 02.2X OMU 2.6B 10.1P CHES010 EMB BSCC_442 MCMU 1 2.3B 02.2R BCSU 0 3.0B 10.1P CHES021 EMB BSCC_443 MCMU 1 2.3B 02.2P BCSU 1 3.4B 10.1P CHES018 EMB BSCC_444 MCMU 1 2.3B 02.2N BCSU 2 3.8B 10.1P CHES015 EMB BSCC_445 MCMU 1 2.3B 02.2L BCSU 3 4.0B 10.1P CHES025 EMB BSCC_446 MCMU 1 2.3B 02.2J BCSU 4 4.4B 10.1P CHES022 EMB BSCC_447 MCMU 1 2.3B 02.2G BCSU 5 4.8B 10.1P CHES019 EMB BSCC_450 MCMU 0 2.0F 02.ETH26 MCMU0 2. 0B 07.1A CHUX035 EMB 1) BSCC_451 MCMU 0 2.0F 02. ETH25 MCMU1 2. 3B 07.1A CHUX033 EMB 1) BSCC_452 MCMU 1 2.3F 02.ETH26 MCMU 0 2. 0B 07.1P CHUX025 EMB 1) BSCC_453 MCMU 1 2.3F 02.ETH25 MCMU 1 2. 3B 07.1P CHUX023 EMB 1) Position ID Name FU Use Note 2.6B 10.1G C108719 ADMOD00 OMU EMB address




2.6B 10.1J C108719 ADMOD00 OMU EMB Address 2.0B 07.1G C108691 ADMOD04 MCMU 0 EMB address 2.0B 07.1J C108719 ADMOD00 MCMU 0 EMB address 2.3B 07.1G C108692 ADMOD05 MCMU 1 EMB address 2.3B 07.1J C108719 ADMOD00 MCMU 1 EMB address 3.0B 10.1G C108703 ADMOD16 BCSU 0 EMB address 3.0B 10.1J C108585 ADMOD01 BCSU 0 EMB address 3.4B 10.1G C108704 ADMOD17 BCSU 1 EMB address 3.4B 10.1J C108585 ADMOD01 BCSU 1 EMB address 3.8B 10.1G C108705 ADMOD18 BCSU 2 EMB address 3.8B 10.1J C108585 ADMOD01 BCSU 2 EMB address 4.0B 10.1G C108706 ADMOD19 BCSU 3 EMB address 4.0B 10.1J C108585 ADMOD01 BCSU 3 EMB address 4.4B 10.1G C108707 ADMOD20 BCSU 4 EMB address 4.4B 10.1J C108585 ADMOD01 BCSU 4 EMB address 4.8B 10.1G C108708 ADMOD21 BCSU 5 EMB address 4.8B 10.1J C108585 ADMOD01 BCSU 5 EMB address




MB TROUBLESHOOTING




MB (Message Bus) Understanding

The MB is the physical connection between the computer units of the network element. It is controlled by the Message Bus Interface plug-in units (MBIF-B) located in every computer unit.

MB used by the BSC3i 660 which use a shared bus for communication.

The duplicated Message Bus has a transfer rate of 32 Mb/s. It is controlled by the Message Bus Interface plug-in unit (MBIF-B), which also acts as a bi-directional interface between a microcomputer and the 16-

bit parallel Message Bus.

The path of the message bus through the computer units is shown in Figure Message bus (MB).




The MBIF-B is connected to the CPU of the microcomputer unit via the PCI bus and to the MBIF-B plug-in units of the other microcomputer units in the exchange via the MB. The MBIF-Bs receive their basic

timing signals from the Clock Equipment (CLS).

The figure shows the connection principle of the microcomputer units to the duplicated Message Bus (MB) whose maximum length is about 50 m. Both MBs are normally in use (active) simultaneously. One

MB is chosen with the software as the active bus along which all call control messages are sent to make

sure that their order is retained at the receive end. The other bus can be used to send e.g. various loading

messages. If either MB becomes faulty, the entire load is transferred to the intact MB. No hardware-

based changeover signal is associated with the selection of the MB in the MBIF-B plug-in units.

Make sure about the MB state & MCMU state both should be same in case of any troubleshooting related activity such as MCMU/EMB fault rectification activity.




MB (Message Bus) TROUBLESHOOTING

A) The below four points to be taken care during the MB troubleshooting

1) MBIF-B PIU. (Placed in all the Computer Units of BSC)

2) MB back panel interconnected cables.

3) MBADR modules. (Placed in back panel of all the MBIF PIU.)

4) TRM9B terminators. (Placed in the starting & ending unit in a MB path i.e. BCSU-0 & MCMU-0)

B) In case of a MB failure scenario u cant find the affected computer unit Physically, however we have a mml

command to find out the fault. For example - Assuming a fault in MB1

ZDDS:OMU;

00-MAN>ZSMTAC:1,00,04,05,30,31,32,33,34,35,36:1000,1000 (MB1 Working or in Test)

(Repeat the above process with all the computer units)

Output Like this

TEST ROUND: 1 COMP DATA_ERR TIME_OUT REC_ERR LAST ERROR STATUS 0000 00000000 00000000 00000000 0004 00000000 00000000 00000000 0005 00000000 00000000 00000000 0030 00000000 00000000 00000000 0031 00000000 00000000 00000000 0032 00000000 00000001 00000000 TIME OUT 0033 00000000 00000000 00000000 0034 00000000 00000001 00000000 TIME OUT 0035 00000000 00000001 00000000 TIME OUT 0036 00000000 00000000 00000000 TOTAL 00000000 00000003 00000000 TEST ROUND: 2 COMP DATA_ERR TIME_OUT REC_ERR LAST ERROR STATUS 0000 00000000 00000000 00000000 0004 00000000 00000000 00000000 0005 00000000 00000000 00000000 0030 00000000 00000000 00000000 0031 00000000 00000000 00000000 0032 00000000 00000002 00000000 TIME OUT 0033 00000000 00000000 00000000 0034 00000000 00000002 00000000 TIME OUT 0035 00000000 00000002 00000000 TIME OUT 0036 00000000 00000000 00000000 TOTAL 00000000 00000006 00000000




C) To start with always check for the alarms related to MB failure & which unit has caused the alarm.

BSC67CIH BCSU-2 SWITCH 2011-09-27 01:08:15.22

* DISTUR MB-1 SUPPRO

1016 MB INTERFACE FAILURE

02 01

BSC67CIH BCSU-2 SWITCH 2011-09-27 01:08:21.84

* DISTUR MB-1 DPALAR *RECOV*

1598 UNIT FOUND FAULTY BY ALARM SYSTEM

FFFF FFFF 00001016 00000000 00000000 00000000 00000000 00000000

BSC67CIH OMU SWITCH 2011-09-27 01:08:21.86

NOTICE MB-1 RCXPRO

0691 AUTOMATIC RECOVERY ACTION

SP-EX TE-EX 0000 0002 7889 00001016 00001598 00000000

D) Post changing the unit state to SE-NH & concerned MB to SE-NH power off the Comp unit & check the MBIF-B

PIU jumper settings & the back panel pins for any bent.

E) If there is only one unit which fails, replace the diagnosed MBIF. Also terminator or cable can be faulty.

F) If units like in above output (32, 34, 35), there is probably fault in the first faulty unit in the chain (BCSU-2). The

bus goes in following chain in BSC3i (660 TRX).

MCMU-0, MCMU-1, BCSU-6, OMU, BCSU-1, BCSU-2, BCSU-5 , BCSU-4, BCSU-3, BCSU-0

G) You can also see from BCSU service terminal startup the MB ADDR are correct:

MB 00: MBIF-B, MB ADDR 30, FREQ 2MHZ, TRANS.FREQ 16MHZ, WIDTH 16BIT

MB 01: MBIF-B, MB ADDR 30, FREQ 2MHZ, TRANS.FREQ 16MHZ, WIDTH 16BIT

H) Also check the MBADR module position,TRM9B terminator & the MB back panel cables.

I) Irrespective of the diagnosis results there may be the Time Out scenarios in ZSMTAC command & thus needs to

replace the MBIF piu,the corresponding MB cables & MBADR modules one by one for eradicating the message

time out scenarios.

J) If several units are faulty you can also do the pin voltage measurement since there exists more problems on

MB-bus thus pin measurement is required.




Cabling Details: Equipping CABLE FROM CABLE TO

No FU Position FU Position Type Use

BSCC_050 MCMU 0 2.0B 05.1N MCMU 1 2.3B 05.2A CHX005 MB

BSCC_051 MCMU 0 2.0B 05.1T MCMU 1 2.3B 05.2G CHX005 MB

BSCC_052 MCMU 0 2.0B 06.1N MCMU 1 2.3B 06.2A CHX005 MB

BSCC_053 MCMU 0 2.0B 06.1T MCMU 1 2.3B 06.2G CHX005 MB

BSCC_054 MCMU 1 2.3B 05.1N BCSU 6 1.8B 08.1N CHX007 MB

BSCC_055 MCMU 1 2.3B 05.1T BCSU 6 1.8B 08.1T CHX007 MB

BSCC_056 MCMU 1 2.3B 06.1N BCSU 6 1.8B 09.1N CHX007 MB

BSCC_057 MCMU 1 2.3B 06.1T BCSU 6 1.8B 09.1T CHX007 MB

BSCC_062 OMU 2.6B 08.2A BCSU 1 3.4B 08.1N CHX005 MB

BSCC_063 OMU 2.6B 08.2G BCSU 1 3.4B 08.1T CHX005 MB

BSCC_064 OMU 2.6B 09.2A BCSU 1 3.4B 09.1N CHX005 MB

BSCC_065 OMU 2.6B 09.2G BCSU 1 3.4B 09.1T CHX005 MB

BSCC_066 BCSU 1 3.4B 08.2A BCSU 2 3.8B 08.1N CHX005 MB

BSCC_067 BCSU 1 3.4B 08.2G BCSU 2 3.8B 08.1T CHX005 MB







BSCC_082 BCSU 3 4.0B 08.1N BCSU 0 3.0B 08.1N CHX45C MB

BSCC_083 BCSU 3 4.0B 08.1T BCSU 0 3.0B 08.1T CHX45C MB

BSCC_084 BCSU 3 4.0B 09.1N BCSU 0 3.0B 09.1N CHX45C MB

BSCC_085 BCSU 3 4.0B 09.1T BCSU 0 3.0B 09.1T CHX45C MB

BSCC_078 BCSU 4 4.4B 08.1N BCSU 3 4.0B 08.2A CHX005 MB

BSCC_079 BCSU 4 4.4B 08.1T BCSU 3 4.0B 08.2G CHX005 MB

BSCC_080 BCSU 4 4.4B 09.1N BCSU 3 4.0B 09.2A CHX005 MB

BSCC_081 BCSU 4 4.4B 09.1T BCSU 3 4.0B 09.2G CHX005 MB

BSCC_074 BCSU 5 4.8B 08.2A BCSU 4 4.4B 08.2A CHX005 MB

BSCC_075 BCSU 5 4.8B 08.2G BCSU 4 4.4B 08.2G CHX005 MB

BSCC_076 BCSU 5 4.8B 09.2A BCSU 4 4.4B 09.2A CHX005 MB

BSCC_077 BCSU 5 4.8B 09.2G BCSU 4 4.4B 09.2G CHX005 MB

BSCC_058 BCSU 6 1.8B 08.2A OMU 2.6B 08.1N CHX005 MB

BSCC_059 BCSU 6 1.8B 08.2G OMU 2.6B 08.1T CHX005 MB

BSCC_060 BCSU 6 1.8B 09.2A OMU 2.6B 09.1N CHX005 MB

BSCC_061 BCSU 6 1.8B 09.2G OMU 2.6B 09.1T CHX005 MB




Terminator is located at the end of MCMU-0 & BCSU-0.

Position ID Name FU Use

2.0B 05.2A C100810 TRM9B MCMU 0 Terminator of MB

2.0B 06.2A C100810 TRM9B MCMU 0 Terminator of MB

3.0B 08.2A C100810 TRM9B BCSU 0 Terminator of MB

3.0B 09.2A C100810 TRM9B BCSU 0 Terminator of MB




BSC Fallback & MO Disk (FDU) Backup




STEP TO TAKE BSC FALLBACK

1.2 Detailed step by step procedure to take BSC Fallback on WDU

1) Open New logs for BSC

2) Check the correct BSC using below command

ZQNI:;

3) Check for others login (Make sure no activity should be carried out in this BSC)

ZQNS:;

4) Check for critical alarms in BSC

ZAHO;

5) Check the status of SOMAFI (How many packages are created in BSC)

ZWQO:CR;

6) If there are 8 packages already created in SOMAFI, deleted one old UT package

ZWQD:NAME=:DIRE,PRINTS;

7) Now check consistency of BU package

ZWQB:STAT=BU:FORM=FAILED;

NOTE: Consistency of all files in both disks should be ok. In case of abnormal output escalate the same

to your SPOC

8) If consistency found ok, take BSC fallback (on WDU)

NOTE: The fallback build can only be made from the build that has the BU status

ZWKS:MODE=FULL,NAME=,DIRE=;

Suppose we are taking fallback on 28-Feb-14 (FB280214) then the command is like below

ZWKS:MODE=FULL,NAME=FB280214,DIRE= FB280214;

9) Check the status of Fallback copying

ZWKI;

Note: Execute the same commad till the message,*/NoFall back copying in progress/* will appear

10) After completing Fallback Check the Consistancy of FB

ZWQB:STAT=FB:FORM=FAILED;




1.3 Detailed step by step procedure to take BSC backup on FDU

11) Check whether FDU or UMS is working or not.

ZISI;

12) Create all directories and Subdirectories on FDU or UMS (I am considering here F0-FDU0)

ZIWL::F0,NODEF::,FF,,AA;

ZIWL::F0,NODEF::FB280214,FF,,AA;

Create subdirectories

ZIWL::F0,NODEF:FB280214:LFILES,900,,AA;

ZIWL::F0,NODEF:FB280214:BLCODE,900,,AA;

ZIWL::F0,NODEF:FB280214:MMDIRE,900,,AA;

ZIWL::F0,NODEF:FB280214:SCMANA,FF,,AA;

ZIWL::F0,NODEF:FB280214:ASWDIR,900,,AA;

13) To display the contents of MO disk

ZIWX::F0,NODEF:FB280214:%%;

ZIWX::WS,NODEF::%,%;

ZIWX::WS,NODEF:FB280214:%%;

(Use either Step-14 or Step-15 to copy data from WS to MO disk)

14) Copy contents from WS to MO disk. Copy file from source(WS) to destination(MO)

For LFILES:

ZIWY:S:UNIT=OMU,PATH=/FB280214/LFILES,DRIVE=WDU-S; Create Source of Copy

ZIWY:D:UNIT=OMU,PATH=/FB280214/LFILES,DRIVE=FDU-N0; Create Desdination

Copy Source to Destination

ZIBC;

Y

For BLCODE:

ZIWY:S:UNIT=OMU,PATH=/FB280214/BLCODE,DRIVE=WDU-S;

ZIWY:D:UNIT=OMU,PATH=/FB280214/BLCODE,DRIVE=FDU-N0;

ZIBC;

Y

For MMDIRE:

ZIWY:S:UNIT=OMU,PATH=/FB280214/ MMDIRE,DRIVE=WDU-S; ZIWY:D:UNIT=OMU,PATH=/FB280214/ MMDIRE,DRIVE=FDU-N0; ZIBC;

Y




For SCMANA:

ZIWY:S:UNIT=OMU,PATH=/FB280214/ SCMANA,DRIVE=WDU-S; ZIWY:D:UNIT=OMU,PATH=/FB280214/ SCMANA,DRIVE=FDU-N0; ZIBC;

Y

For ASWDIR:

ZIWY:S:UNIT=OMU,PATH=/FB280214/ ASWDIRE,DRIVE=WDU-S; ZIWY:D:UNIT=OMU,PATH=/FB280214/ ASWDIR,DRIVE=FDU-N0; ZIBC;

Y

15) Another process to copy content from WS to MO (Copy the entire FB package instead of Subdirectories)

ZIWX::F0,NODEF::%,%,;

ZIWL:,OMU:F0,NODEF:: FB280214,,,AG;

ZIWY:S:UNIT=OMU,DRIVE=WDU-S,PATH=/ FB280214,:; //Define Source point

ZIWY:D:UNIT=OMU,DRIVE=FDU-N0,PATH=/ FB280214,; //Define Destination point

ZIBC:,,,,,,,,,DIR::; //Copy source to destination

16) Check content of MO disk

ZIWX::F0,NODEF:FB280214:%,%;

1.4 Some other important commands may used during FDU troubleshooting

1. To reinitialize directories on MO (FDU) disk

ZIWK::F0,::;

2. Format MO disk if requierd (not recommended)

ZIWI::,,;




BSC Login via OMU (CPU J7 Port)




BSC Login through CPU J7 Port

First Connect RJ45 to CPU J7 PORT & DB9 to laptop port (use BSC login cable) and press ENTER.

1) Then system will ask for user name & password

2) Provide user name & password

a) First try with use user id SYSTEM & Password SYSTEM, if system say unauthorized b) Then use user id & password of 2nd line team of respective circle team.

3) Then System will show

WELCOME TO SERVICE TERMINAL DIALOGUE

00- MAN>

4) Create extension

00-MAN> L:2

00-MAN> ZLP:2,VIMMALGX

00-MAN> 2

00-VIM> C:2

Connected. (vtermd server hand is 1)

5) ENTER USERNAME < GNFMBT

ENTER PASSWORD < ******

BSC3i B23MRW 2014-03-28 13:39:30

WELCOME TO THE DX 200 SERIES DIALOGUE

MAIN LEVEL COMMAND




PCU Pooling Concept/Troubleshooting




PCU Pooling Troubleshooting

Before proceeding to troubleshoot lets clear some basic point about PCU Pooling.

1) PCU2 Pooling feature introduces the Packet Service Entity (PSE) concept. PSE is a logical concept, which covers several PCU PIUs in BSC. All PCUs in PSE are serving the same NSE

2) Logical network configuration is separated from HW configuration as Gb interface is configured to NSE only and DAPs and Segments are attached to PSE instead of PCU

3) When we adds a new PCU into PSE, the system automatically configures Gb interface to new PCU and then allocates DAPs and Segments to new PCU based on each Segments (E)GPRS load. The operator does

not need to do any changes to the logical network configuration in BSC and either in SGSN

4) PCU2 Pooling is optional feature (On/Off), managed by Licensing

5) PCU2 Pooling feature is implemented in BSC only to PCU2 and when IP is used as transport method on the Gb interface.

6) Minimum configuration: two PCU can form a PSE

7) Maximum configuration: 50 PCUs in one PSE

8) In case of Multipoint Gb, there is several NSEs in PSE. Each NSE covers PSEs all PCUs

9) IP configuration is static or dynamic in NSE. In case of Multipoint Gb, both IP configurations can be used parallel in PSE. However type of IP configuration in one NSE has to be same

10) All PCUs in PSE has to use same IP version (IPv4 or IPv6) in NSE. In case of Multipoint Gb, both IP versions can be used parallel in PSE. However type of IP version in one NSE has to be same

11) IP version 4 only is used on the Inter-PCU LAN interface

12) PCU2, Gb over IP and PCU2 pooling licenses must be activated.

Advantages of PCU Pooling

1) Easy way to increase (E)GPRS capacity in the network, in BSC

2) Savings in configuration costs (no modification to logical network configuration in the BSC and neither in the SGSN)

3) Abis and Gb resources are shared more efficiently and dynamically between PCUs in NSE

4) (E)GPRS load is shared dynamically between PCUs within the PSE when the operator adds a new PCU into the PSE or reallocates PSE configuration




Now go through the below steps one by one to troubleshoot the problem

1) Check the value of the Packet Control Unit (PCU2) Pooling feature state

ZW7I:FEA,FULL:FEA=70;

2) If necessary, change the Packet Control Unit (PCU2) Pooling feature state to ON

ZW7M:FEA=70:ON; (Use this command under SPOC/TL supervision only)

3) Verify logical PCU definition in PCU pooling using ZQKB:;

4) If inter PCU connections are missing please add the same using below steps. To understand the concept lets consider BCSU-0 and same must be defined for all BCSU.

ZQKC:BCSU,0:PCU2D,3:172.27.132.70,32:172.27.132.77:LOG:;

Here 172.27.132.70, defines the IP for BCSU-0 PCU-4 i.e inter connectivity between the logical PCUs of BCSU-0

(PCU-3-PCU-4) and 172.27.132.77 defines the IP used for Gateway purpose and it should be the IP of next

working BCSU i.e BCSU-1 PCU-3.

Same should be defined for other logical PCU in all the BCSU.

NOTE: Logical mapping required where PCU2_D is in use. It is not required in case of PCU_B/PCU2_E.

5) Check Ping response

a) Ping PCU to ESB b) Ping PCU to GW c) Ping ESB to PCU d) Ping ESB to SGSN e) SGSN to PCU

6) Perform GENA/EGENA Toggle, DAP deletion & creation, NSEI change or NSEI reset (night hours only with proper outage approval) at BSC end as well as SGSN.

7) Off load the problematic NSEI and perform PCU deletion & Creation using below Steps.

a) Remove PCU from PSE ZFXF:R:BCSU=0,PCU=4,PSEI=0::;

b) Add PCU to PSE ZFXF:A:BCSU=0,PCU=4,PSEI=0::;

8) If still not resolved perform BCSU swithover.

fm bss technical document (2).pdf

Documents

disk zdbp

internal use

disk logs

disk updates of databases

state disk updates

disk database dbx

disk updates of databases

hard disk unit wdu