0% found this document useful (0 votes)
341 views10 pages

Daily Healthcheck Proceedure For BSC: S/No BSC Name Command Activity

The document describes a daily health check procedure for a BSC. It lists 20 checks to perform including checking alarms, equipment status, processor load, and backups. For each check, it specifies the check, expected value, severity level, recommended action, status, and any remarks.

Uploaded by

Samir Adamu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
341 views10 pages

Daily Healthcheck Proceedure For BSC: S/No BSC Name Command Activity

The document describes a daily health check procedure for a BSC. It lists 20 checks to perform including checking alarms, equipment status, processor load, and backups. For each check, it specifies the check, expected value, severity level, recommended action, status, and any remarks.

Uploaded by

Samir Adamu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
You are on page 1/ 10

Daily Healthcheck Proceed

S/No BSC Name Command Activity

1 allip:alcat=apz; ALARM LIST

2 raasp RP APPLICATION DISTRIBUTION STATUS

3 RALDP:RP=ALL CTH LOAD DISTRIBUTION DATA

4 DIRRP:RP=ALL Check the Regional Processor (RP) errors

6 ihifp:vif=all VIRTUAL ETHERNET INTERFACE DATA

7 Dpwsp; CP STATE

8 Plldp; PROCESSOR LOAD DATA

10 ncdap NETWORK CLOCK REFERENCE DATA

11 Dbtsp:tab=saactions; DATABASE TABLE

12 Exrpp:rp=all; RP DATA

13 M3rsp:dest=all; M3UA ROUTING DATA

14 M3ASP; M3UA ASSOCIATION STATUS

15 ntstp:snt=all; SWITCHING NETWORK TERMINAL STATE

BSC
16 SYBFP:FILE; Check CP backup
BSC

17 Syrip:survey; SOFTWARE RECOVERY SURVEY

18 SYELP; SYSTEM FUNCTIONS, ERROR INTENSITY, HEALTHCHECK

19 Rrinp:nsei=all; RADIO TRANSMISSION IP NETWORK SERVICE DATA

20 RACLP ; BSC CAPACITY LOCK ALARM DATA

23 EXEMP:EM=ALL,RP=ALL EM DATA State

24 EXRNP:RP=ALL RPB-E RP DATA State

26 RLTDP:MSC=ALL; MSC TRAFFIC DISTRIBUTION DATA

27 RRRSP:RP=ALL; RADIO TRANSMISSION RP ETHERNET CONNECTION STATUS

29 afpls -ls File transfer Status Check

30 alist APG alarm list


hcheck Proceedure For BSC
To be checked Value Severity Action Status
No action OK
APZ alarm status NO Good required
All EPB board must be No action OK
operationnal NO Good required
No action OK
CTH RP load data NO Good required
No action OK
RP errors NO Good required
Virtual ethernet interface No action OK
state should be UP NO Good required
MAU state-NRM, SB-B, SBSTATE-
WO. Posible deviations may be No action OK
AAM, ACM, LOCK & FEX. NO Good required

Offered and fetched calls


should be same, OFFDO=FTCHDO &
OFFDI=FTCHDI. Logs has to be OK
stored. PLOAD must be less than
80% for continuous last 12 No action
measurements. NO Good required

All the external clocks must be


in STATE=EX or SB. Possible
deviations are OK
UPD/BLOC/PASSIVE. Escalate if
"Network Synchronization Fault" No action
alarm is not escalated. NO Good required
Check DATABASE TABLE Should be No action OK
Clear NO Good required
Status of all RPs should be in
WO state. If any RP is in MBL OK
state, then the reason for the No action
same should be known NO Good required
All M3UA routine data should be No action OK
ENABLED and ACTIVE NO Good required
All M3UA Association status No action OK
should be ACTIVE NO Good required
Switching Network Terminal No action OK
should in WO state NO Good required

Latest CP backup must be


available in RELFSW0 to that of
current date only. In case of OK
it is old, also check for
backup information fault in
APZ. Escalate to FO NSS team in No action
case not escalated already. NO Good required
Check for any repetitive sw
errors which can be found from
the CODE. If there is any
recent software errors which is
in state ACTIVE=NO then it OK
should be escalated. Possible
deviations are FORLOPP &
APPLERR under EVENT TYPE field.
Don't escalate where
EXPLANATION is either PLAN or No action
MANUALLY INTIATED. NO Good required

CURRENT ERROR LIMIT must be


3000 & CURRENT ERROR INTENSITY
must be zero. Any deviation OK
from in CURRENT ERROR LIMIT No action
from 3000 must be reported. NO Good required
Check the status of GB link in No action OK
BSC NO Good required
Verify that key license are No action OK
ACTIVATED NO Good required
All EM State should be WO
state. If any deviation, then OK
the reason for the same should No action
be known NO Good required
All RPB-E state be in WO state.
Any deviation should be No action OK
investigated NO Good required
MSC Traffic Mode should be
ACTIVE. Any deviation should be No action OK
investigated NO Good required
Must be in active state.
Possible deviation is No action OK
STATUS=PASSIVE NO Good required

All files should be in delete


state. Special care for
RTRFILES. Possible deviation is OK
READY/FAILED.There should not
be any old file from the No action
available sequence/trend. NO Good required
No action OK
Check and resolve APG alarms NO Good required
Summary
OK NOK

24 0
S/N Node ID Command
1 get DcDevice= oper 0
2 get DcDevice= admin 0
3 get CcDevice= oper 0
4 get CcDevice= admin 0
5 get ipaccesshostet oper 0
6 get ipaccesshostet admin 0
7 lget pdrdevice admin 0
8 lget pdrdevice oper 0
9 lh mp procload
10 RNC alt
11 lge -m 2d | grep -i restart
12 lgv -m 2d | grep -i Failure
13 lgs -i -m 2d | grep "Crash"
14 lh ranapmp ranap status
15 st plugin
16 get 0 corestates
17 pgetsn
18 cvls
19 lh cc procload / lh dc procload / lh pdr procload
20 st m3ua
Health check
Check dc devices status, isolate and troubleshoot dcdevice with disabled operatio
Check dc devices status, isolate and troubleshoot dcdevice with zero admin
Check cc devices status, isolate and troubleshoot ccdevice with disabled operationa
Check cc devices status, isolate and troubleshoot ccdevice with zero admin state
check all hostet that are operational disabled
check all hostet that are administratively disabled
check for administratively disabled pdrdevice
check for any operationally disabled pdrdevice
Checking Processor CPU Load
Check for alarms on the RNC
Check for board restart
Check for board failures
Check for crashes on the boards
Check ranap status for active board
Check plugin status
active board check
list of activated scanners
cv list, should be less then 40 CVs
Check processor load on cc, dc and pdr device
Check M3UA Association down
Value Severity Action Status Remark
NO Good No action required OK
NO Good No action required OK
NO Good No action required OK
NO Good No action required OK
NO Good No action required OK
NO Good No action required OK
NO Good No action required OK
NO Good No action required OK
NO Good No action required OK
NO Good No action required OK
NO Good No action required OK
NO Good No action required OK
NO Good No action required OK
NO Good No action required OK
NO Good No action required OK
NO Good No action required OK
NO Good No action required OK
NO Good No action required OK
NO Good No action required OK
NO Good No action required OK
Summary
OK NOK
20 0

You might also like