Documente Academic
Documente Profesional
Documente Cultură
Bharti FM-BSS
1 (55)
24-Apr-2014
Bharti FM-BSS
2 (55)
24-Apr-2014
TABLE OF CONTENTS
1
Discriminator Clearance16
1. Discriminator clearance.17
2. BSDATA & PDDATA clearance18
3. OMU & MCMU process restart.18
4. CMISE application restart..19
Revert BSC on Fall Back (Delete the DBI* and DBA* files)26
EMB Troubleshooting.36
MB Troubleshooting40
Bharti FM-BSS
3 (55)
24-Apr-2014
Bharti FM-BSS
4 (55)
24-Apr-2014
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
0
0
0
MCMU
OMU
MCMU
019B
01C5
0262
0009
0011
0022
Bharti FM-BSS
ILDATA
PDDATA
5 (55)
24-Apr-2014
0
0
OMU
MCMU
0679
06AE
0B640000
0BA60000
0069
006A
ZWTI:P:OMU:;
Bharti FM-BSS
6 (55)
24-Apr-2014
ZISC::FDU,00:BL-US,;
12. Check that the state of the hard disk to be replaced is correct (BL-US/MI-US)
ZISI:,<destination unit>,<pair>:<I/O device type>,<I/O device index>;
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:,<destination unit>,<pair>:<I/O device type>,<I/O device index>:<working state>;
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:,<destination unit>,<pair>
BY COMPAIRE THIS WITH ZISI::WDU;
IF WDU-0 is Faulty then WS=1,
IF WDU-1 is Faulty then WS=0,
WB=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: <main unit type>, <pair>, <main unit index>: <device type>, <device index>;
ZUDD:OMU,0:WDU,1;
For internal use only Nokia Solutions and Networks
Bharti FM-BSS
7 (55)
24-Apr-2014
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:,<destination unit>,<pair>:<I/O device type>,<I/O device index>:<working state>;
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:;
****IF Files are not getting transfer to new disk using above commands, then need to create source
and destination using below commands****
ZIPS:<source unit>,<source I/O device>,<source path>,,:,<destination I/O device>,<destination
path>,,:<directory mode>,<copy task name>;
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=<copy task 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-/<Build directory name>/LFILES/LOGR*.*
ZMD: W1-/<Build directory name>/LFILES/LOGR*.*
ZDDS:;
For internal use only Nokia Solutions and Networks
Bharti FM-BSS
8 (55)
24-Apr-2014
Sample Output:
DELETING FILE: W1-/ASE_1_28_0/LFILES/LOGRECSD01.DAT:00
EXECUTED
DELETING FILE: W1-/ASE_1_28_0/LFILES/LOGRECSD03.DAT:00
EXECUTED
DELETING FILE: W1-/ASE_1_28_0/LFILES/LOGRECSD02.DAT:00
EXECUTED
DELETING FILE: W1-/ASE_1_28_0/LFILES/LOGRECSD04.DAT:00
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:<database name>,<occurrence>; //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:<database name>,<occurrence>;
ZDBC:BSDATA,0:;
ZDBC:EQUIPM,0:;
ZDBC:OEDATA,0:;
ZDBC:ILDATA,0:;
ZDBC:PDDATA,0:;
Bharti FM-BSS
9 (55)
24-Apr-2014
28. Check that the states of the units are correct (WO-EX, SP-EX) (USI)
ZUSI:<unit type>,<unit index>;
ZUSU:OMU:C=DSK;
Bharti FM-BSS
10 (55)
24-Apr-2014
Bharti FM-BSS
11 (55)
24-Apr-2014
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=<seg_no>:GENA=N:;
4) Lock the NSEI using below command
ZFXS:NAME=<nsei_name>:L;
5) Delete NSEI using the below command
ZFXD:NAME=<nsei_name>;
6) Create NSEI
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:;
Bharti FM-BSS
12 (55)
24-Apr-2014
Bharti FM-BSS
13 (55)
24-Apr-2014
Bharti FM-BSS
14 (55)
24-Apr-2014
Bharti FM-BSS
15 (55)
24-Apr-2014
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=<NSVLI NO>,NAME=<NSVLI NAME>,NSEI=<NSEI NO>,PSEI=<PSE NO>:LPNBR=<LOCAL UDP
PORT NO>,PRE=N:RPNBR=<REMOTE UDP PORT NO>, 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.
Bharti FM-BSS
16 (55)
24-Apr-2014
Bharti FM-BSS
17 (55)
24-Apr-2014
DISCRIMINATOR CLEARANCE
Discriminator clearance activity can be performed during below given scenario1) 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.
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
=
Last window written to disk
=
Number of records in the que
=
Amount of bytes used
=
Identifier of the first record
=
0001
0000
0000
0000
0000
Bharti FM-BSS
18 (55)
24-Apr-2014
0000
0000
Now, delete the Dissiminator Extension, using the command L:2 and exit the service terminal using
ZE.
C)
D)
E)
F)
G)
Bharti FM-BSS
24-Apr-2014
ZUSU:OMU:C=DSK;
<ZEEK;
output should be
BSC3i
BSC23JAY
19 (55)
2011-01-21 10:21:45
Bharti FM-BSS
20 (55)
24-Apr-2014
Bharti FM-BSS
21 (55)
24-Apr-2014
Bharti FM-BSS
Continue.
22 (55)
24-Apr-2014
Bharti FM-BSS
7)
23 (55)
24-Apr-2014
Make the new connection for BSC login (Provide IP, User Name & Password) & save.
Continue.
For internal use only Nokia Solutions and Networks
Bharti FM-BSS
24 (55)
24-Apr-2014
Continue.
Bharti FM-BSS
25 (55)
24-Apr-2014
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
-----------------------------------------------Process Completed------------------------------------------------------------
Bharti FM-BSS
26 (55)
24-Apr-2014
Bharti FM-BSS
27 (55)
24-Apr-2014
Bharti FM-BSS
28 (55)
24-Apr-2014
Bharti FM-BSS
24-Apr-2014
29 (55)
.ALF
TOTALS
AC
614400
614392 02 D
.ALF
AC
2048000
0 AB D
Bharti FM-BSS
TOTALS
30 (55)
24-Apr-2014
2048512
Bharti FM-BSS
31 (55)
24-Apr-2014
Bharti FM-BSS
32 (55)
24-Apr-2014
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
NONE
NONE
W0
WRITE,MOVE
45
W0, W1 WRITE,MOVE
120
OEDATA 0
NONE
W0, W1 WRITE,MOVE
30
EQUIPM 0
NONE
W0, W1 WRITE,MOVE
600
BSDATA 0
NONE
W0, W1 WRITE,MOVE
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.
Bharti FM-BSS
33 (55)
24-Apr-2014
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
STATE
PDDATA
WO
DUMPING
PDDATA
SP
NORMAL
MEMORY UPDATES
PREVENTED
NO
DISK UPDATES
PREVENTED
NO
SUBSTATE
DUMPING DATABAS
NORMAL
TRANSACTION
OVERFLOW
NO
BACK UP
IS ON
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.
Bharti FM-BSS
34 (55)
24-Apr-2014
Bharti FM-BSS
35 (55)
24-Apr-2014
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
36 (55)
24-Apr-2014
BHARTI FM-BSS
EMB TROUBLESHOOTING
Bharti FM-BSS
37 (55)
24-Apr-2014
EMB TROUBLESHOOTING
A) Check logs of port & other setting
Here, I consider EMB-0 faulty.
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
For internal use only Nokia Solutions and Networks
Bharti FM-BSS
38 (55)
24-Apr-2014
Setting
Off
Off
Off
Off
Off
Off
Meaning
Interchangeability code bit 3
Interchangeability code bit 2
Interchangeability code bit 1
Interchangeability code bit 0
Not in use
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
CHES012
CHES023
CHES020
CHES017
CHES027
CHES024
CHES021
EMB
EMB
EMB
EMB
EMB
EMB
EMB
BSCC_430
BSCC_433
BSCC_434
BSCC_435
BSCC_436
BSCC_437
BSCC_438
FU
MCMU 0
MCMU 0
MCMU 0
MCMU 0
MCMU 0
MCMU 0
MCMU 0
Position
2.0B 02.2X
2.0B 02.2R
2.0B 02.2P
2.0B 02.2N
2.0B 02.2L
2.0B 02.2J
2.0B 02.2G
FU
OMU
BCSU 0
BCSU 1
BCSU 2
BCSU 3
BCSU 4
BCSU 5
Position
2.6B 10.1A
3.0B 10.1A
3.4B 10.1A
3.8B 10.1A
4.0B 10.1A
4.4B 10.1A
4.8B 10.1A
BSCC_439
BSCC_442
BSCC_443
BSCC_444
BSCC_445
BSCC_446
BSCC_447
MCMU 1
MCMU 1
MCMU 1
MCMU 1
MCMU 1
MCMU 1
MCMU 1
2.3B 02.2X
2.3B 02.2R
2.3B 02.2P
2.3B 02.2N
2.3B 02.2L
2.3B 02.2J
2.3B 02.2G
OMU
BCSU 0
BCSU 1
BCSU 2
BCSU 3
BCSU 4
BCSU 5
BSCC_450
BSCC_451
MCMU 0
MCMU 0
BSCC_452
BSCC_453
MCMU 1
MCMU 1
2.3F 02.ETH26
2.3F 02.ETH25
2. 0B 07.1A CHUX035
2. 3B 07.1A CHUX033
EMB 1)
EMB 1)
EMB 1)
EMB 1)
Position
ID Name
FU
Use
Note
2.6B 10.1G
C108719
ADMOD00
OMU
EMB address
Bharti FM-BSS
2.6B 10.1J
2.0B 07.1G
2.0B 07.1J
2.3B 07.1G
2.3B 07.1J
3.0B 10.1G
3.0B 10.1J
3.4B 10.1G
3.4B 10.1J
3.8B 10.1G
3.8B 10.1J
4.0B 10.1G
4.0B 10.1J
4.4B 10.1G
4.4B 10.1J
4.8B 10.1G
4.8B 10.1J
39 (55)
24-Apr-2014
C108719
C108691
C108719
C108692
C108719
C108703
C108585
C108704
C108585
C108705
C108585
C108706
C108585
C108707
C108585
C108708
C108585
ADMOD00
ADMOD04
ADMOD00
ADMOD05
ADMOD00
ADMOD16
ADMOD01
ADMOD17
ADMOD01
ADMOD18
ADMOD01
ADMOD19
ADMOD01
ADMOD20
ADMOD01
ADMOD21
ADMOD01
OMU
MCMU 0
MCMU 0
MCMU 1
MCMU 1
BCSU 0
BCSU 0
BCSU 1
BCSU 1
BCSU 2
BCSU 2
BCSU 3
BCSU 3
BCSU 4
BCSU 4
BCSU 5
BCSU 5
EMB Address
EMB address
EMB address
EMB address
EMB address
EMB address
EMB address
EMB address
EMB address
EMB address
EMB address
EMB address
EMB address
EMB address
EMB address
EMB address
EMB address
Bharti FM-BSS
40 (55)
24-Apr-2014
MB TROUBLESHOOTING
Bharti FM-BSS
41 (55)
24-Apr-2014
Bharti FM-BSS
42 (55)
24-Apr-2014
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 hardwarebased 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.
Bharti FM-BSS
43 (55)
24-Apr-2014
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
Bharti FM-BSS
44 (55)
24-Apr-2014
C) To start with always check for the alarms related to MB failure & which unit has caused the alarm.
<HIST> BSC67CIH
BCSU-2
* DISTUR MB-1
SUPPRO
1016 MB INTERFACE FAILURE
02 01
<HIST> 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
<HIST> 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.
Bharti FM-BSS
45 (55)
24-Apr-2014
Cabling Details:
Equipping
CABLE FROM
No
FU
CABLE TO
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_068
BCSU 1
3.4B 09.2A
BCSU 2
3.8B 09.1N
CHX005
MB
BSCC_069
BCSU 1
3.4B 09.2G
BCSU 2
3.8B 09.1T
CHX005
MB
BSCC_070
BCSU 2
3.8B 08.2A
BCSU 5
4.8B 08.1N
CHX004
MB
BSCC_071
BCSU 2
3.8B 08.2G
BCSU 5
4.8B 08.1T
CHX004
MB
BSCC_072
BCSU 2
3.8B 09.2A
BCSU 5
4.8B 09.1N
CHX004
MB
BSCC_073
BCSU 2
3.8B 09.2G
BCSU 5
4.8B 09.1T
CHX004
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
Bharti FM-BSS
46 (55)
24-Apr-2014
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
Bharti FM-BSS
47 (55)
24-Apr-2014
Bharti FM-BSS
48 (55)
24-Apr-2014
Bharti FM-BSS
49 (55)
24-Apr-2014
Bharti FM-BSS
50 (55)
24-Apr-2014
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,:;
ZIWY:D:UNIT=OMU,DRIVE=FDU-N0,PATH=/ FB280214,;
ZIBC:,,,,,,,,,DIR::;
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::<drive>,<format>,<partition table>;
Bharti FM-BSS
51 (55)
24-Apr-2014
Bharti FM-BSS
52 (55)
24-Apr-2014
BSC3i
B23MRW
2014-03-28
13:39:30
Bharti FM-BSS
53 (55)
24-Apr-2014
Bharti FM-BSS
54 (55)
24-Apr-2014
Bharti FM-BSS
55 (55)
24-Apr-2014
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;
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.