BLADE CLUSTER DEFINATION

CHECK FOR IRAT HO

BC DEFINATION CHECK PROCESS

EXTRACT DUMP
› DUMP CAN BE OBTAINED FROM WINFIOL OR SECURE CRT BY
LOGIN INTO THE OSS BY FOLLOWING THE NORMAL
PROCEDURE.
› AFTER ENTERING THE OSS IT WILL PROMPT
*****@#####>
LET THE BLADE CLUSTER NAME BE “XYZBC01” SO WE HAVE TO
ENTER THE COMMAND
*****@#####>eac_esi_config -ne XYZBC01
------
------
ADDRESS 10.XX.X.X
--
-----
*****@#####>telnet 10.XX.X.X

BLADE CLUSTER CHECK FOR IRAT HO | SWARNENDU DAS | © Ericsson RTC EAST 2012 | Page 2
EXTRACT DUMP
› THE ADDRESS WILL BE SHOWN AFTER THE eac COMMAND
WHICH WE TO GIVE IN ‘TELNET’ THIS 10.XX.X.X IS THE BLADE
CLUSTER IP.
login name: XXXXXX
password: ********
Windows NT Domain:
NOW PRESS “enter” IT WILL TAKE TO THE BLADE CLUSTER.
XXXXXX & ******** ARE THE BC LOGIN ID AND PASSWORD.
THIS Windows NT Domain CAME AS THE BC IS IN NT DOMAIN AND
ON ENTER THE BRIDGE BETWEEN USER DOMAIN AND BC
DOMAIN IS COMPLETED.
THE FOLLOWING PROCESS TAKES YOU TO DATABASE OF THE BC
WHERE WE CAN ONLY FETCH DATA. TO ENTER THE BC
PROCESSOR WE HAVE TO ENTER ANOTHER COMMAND mml.

BLADE CLUSTER CHECK FOR IRAT HO | SWARNENDU DAS | © Ericsson RTC EAST 2012 | Page 3
EXTRACT DUMP
› C:\WINNT\Profiles\ XXXXXX >mml
CLUSTER SESSION - EXPERT MODE
<
NOW WE HAVE TO ENTER FOLLOWING COMMANDS TO GET THE
FOLLOWING DUMP
<mgocp:cell=all;
MT OUTER CELL DATA
CELL AREAID MSC NCS

<mglap;
MT LOCATION AREA DATA
LAI PFC PRL POOL AIDX

BLADE CLUSTER CHECK FOR IRAT HO | SWARNENDU DAS | © Ericsson RTC EAST 2012 | Page 4
EXTRACT DUMP
<mgnmp:msc=all;
MT NEIGHBOURING MSC DATA
MSC MSCADDR R MSCCAP

<mgaap:area=all;
MT AREA CLUSTER DATA
AREA ACET AREAID RO CO EA

<mgocp:cell=all;
MT OUTER CELL DATA
CELL AREAID MSC NCS

BLADE CLUSTER CHECK FOR IRAT HO | SWARNENDU DAS | © Ericsson RTC EAST 2012 | Page 5
Check NEIGHBOURING MSC DATA
› WE HAVE TO CHECK THE NEIGHBOUR MSC DATA BY VERIFIYING
MSCADDR. WE HAVE TO COME OUT THE BC “exit” AND ENTER THE
EACH MSC TO CHECK
*****@#####> eaw MSC
*****@#####> mgcap
INT NAT

NOW WE TO MATCH EACH MSC MSCADDR=NAT TO FIND ANY

ANOMALY.

BLADE CLUSTER CHECK FOR IRAT HO | SWARNENDU DAS | © Ericsson RTC EAST 2012 | Page 6
Check AREA CLUSTER DATA
› THIS ONE IS THE VITAL CHECK WHERE FIRST WE TO MATCH THE AREAID
DEFINED IN THE BLADE CLUSTER MATCHES THE ACTUAL DEFINATION OF THE
UTRANCELLS FROM KGET FOR PROPER DEFINATION.

› ANOTHER CHECK WE HAVE TO DONE WE HAVE TO FIND OUT THE CELLS WHICH
ARE NOT DEFINED IN BLADE CLUSTER. AND WE HAVE TO DEFINE THOSE CELLS.

› ANOTHER POSSIBLE CASE (as experienced) CELLS DEFINED IN BLADE CLUSTER

BUT NOT IN THE 3G DATABASE.

› BOTH SIDE CHECK HAVE TO BE DONE IN THIS FASHION.

› CELLS NOT IN KGET BUT DEFINED IN BC: ACTION=DELETE THOSE CELLS.

› CELLS TO BE DEFINED IN BC: ACTION= DEFINE THEM IN BC & FIND THE

GSMRELATION OF THOSE CELSS WITH THEIR RESPECTIVE BSC

BLADE CLUSTER CHECK FOR IRAT HO | SWARNENDU DAS | © Ericsson RTC EAST 2012 | Page 7
Check OUTER CELL DATA
› IN THIS CHECK WE HAVE TO ALL THE BSCs ARE PROPERLY DEFINED OF THE
GSMRELATION CELLS.

› FOR THIS CHECK WE TO TAKE ALL GSMRELATION 2G CELLS WITH THEIR

RESPECTIVE BSCs AND LAI. NOW FROM THE OUTER CELL DATA WE HAVE TO
LOOKUP THE BSC TO CHECK WHETHER ALL BSC DEFINATIONS ARE PROPERLY
DEFINED AND NO BSC GOT MISSED OUT WHOSE 2G CELLS IS IN THE
GSMRELATION LIST.

BLADE CLUSTER CHECK FOR IRAT HO | SWARNENDU DAS | © Ericsson RTC EAST 2012 | Page 8