Scribd
Upload
89 views2 pages

Weekly Ericsson BSC Check Procedure (Saturday) : Make A Logfile

Uploaded by

Mangata Acaronar

This document provides a weekly checklist of procedures for checking an Ericsson BSC, including: 1) Checking group switch disturbance statistics, CP error records, and faults in RP units. 2) Checking application allocations between SP and CP and their states. 3) Checking automatic backup time and SAE faults, actions, alarms, and space. 4) Checking transaction logging conditions and faults in nodes A and B. 5) Checking the fault log for SPs and system standby devices. 6) Checking store utilization.

Copyright:

© All Rights Reserved
Download as DOC, PDF, TXT or read online from Scribd
Download as doc, pdf, or txt

Weekly Ericsson BSC Check Procedure (Saturday) : Make A Logfile

Uploaded by

Mangata Acaronar
89 views2 pages
This document provides a weekly checklist of procedures for checking an Ericsson BSC, including: 1) Checking group switch disturbance statistics, CP error records, and faults in RP units. 2) Checking application allocations between SP and CP and their states. 3) Checking automatic backup time and SAE faults, actions, alarms, and space. 4) Checking transaction logging conditions and faults in nodes A and B. 5) Checking the fault log for SPs and system standby devices. 6) Checking store utilization.

Original Title

BSC_Weekly_Check_mobilis

Copyright

© © All Rights Reserved

Available Formats

DOC, PDF, TXT or read online from Scribd

Did you find this document useful?

Is this content inappropriate?

This document provides a weekly checklist of procedures for checking an Ericsson BSC, including: 1) Checking group switch disturbance statistics, CP error records, and faults in RP units. 2) Checking application allocations between SP and CP and their states. 3) Checking automatic backup time and SAE faults, actions, alarms, and space. 4) Checking transaction logging conditions and faults in nodes A and B. 5) Checking the fault log for SPs and system standby devices. 6) Checking store utilization.

Copyright:

© All Rights Reserved
Download as DOC, PDF, TXT or read online from Scribd
Download as doc, pdf, or txt
89 views2 pages

Weekly Ericsson BSC Check Procedure (Saturday) : Make A Logfile

Uploaded by

Mangata Acaronar
This document provides a weekly checklist of procedures for checking an Ericsson BSC, including: 1) Checking group switch disturbance statistics, CP error records, and faults in RP units. 2) Checking application allocations between SP and CP and their states. 3) Checking automatic backup time and SAE faults, actions, alarms, and space. 4) Checking transaction logging conditions and faults in nodes A and B. 5) Checking the fault log for SPs and system standby devices. 6) Checking store utilization.

Copyright:

© All Rights Reserved
Download as DOC, PDF, TXT or read online from Scribd
Download as doc, pdf, or txt
You are on page 1/ 2

Prepared Date Rev Document no

Ali Temel Kayhan 19-07-2005 A


Approved Checked File / reference
Simo Malinen BSC_Weekly_Check.doc

Weekly Ericsson BSC Check Procedure(saturday)


Make a logfile.
Make a dump to the Optical Disc in sunday.(front office make a dump to relfsw12 saturday night)

GSDSP; ! Check the Group Switch Disturbance statistics

DIRCP; ! Print CP error record

DIRRP:RP=ALL; ! Check the faults occured in RP’s.

EXJAP:APPL=ALL; ! Check the allocated applications between SP and CP. The state of
applications should be ACT in one of the IOG Nodes.

SYRAP; ! Forlopp Release must be ACTIVE

SYFSP; ! Forlopp Handling must be ACTIVE. (And also check ECF=OFF,


FLERROR=ON)

SYBTP; ! Check the automatic backup time. It should be set to 04:00 o’clock

DBTSP:TAB=SAEFAULTS; ! Check if there is a SAE Fault

DBTSP:TAB=SAACTIONS; ! Check the SAE Action List, if modification for a SAE is necessary or
not.

SAAEP:SAE=466; ! Number of alarms (It should be much more less than 2000). Otherwise alarms
can not be seen in the Alarm List.

SAAEP:SAE=298; ! Check the number of internal cells (There should be enough space
for new cell definitions

SAAEP:SAE=299; ! Check the number of external cells (There should be enough space
for new definitions

SAAEP:SAE=522,BLOCK=RQCD; ! Check the internal neighbour relations (There


should be enough space for new neighbour definitions)

SAAEP:SAE=523,BLOCK=RQCD; ! Check the external neighbour relations (There should be


enough space for new external neighbour definitions)

IMLIT:SPG=0;

SDDOP:OBJTYPE=ALL,AREA=OPER; ! Make a comparison between SAE values


and their corresponding NOBJ values. If it is necessary, change the NOBJ values.
Prepared Date Rev Document no
Ali Temel Kayhan 19-07-2005 A
Approved Checked File / reference
Simo Malinen BSC_Weekly_Check.doc

END;

IMLCT:SPG=0;

MCTLP; ! Check the transaction logging conditions. State should be WO.

END;

IMMCT:SPG=0;

IMALP:NODE=A; ! Check the faults occured in Node A

END;

IMMCT:SPG=0;

IMALP:NODE=B; ! Check the faults occured in Node B

END;

DISFP:SPG=0,NODE=A/B, FRDATE=week start date,TODATE=seven days later;


! Check the fault log for SP

IOSYP; ! Check the system standby device (normally it should be AT-0)

IOIOP:IO1=ALL; ! Check the standby device for AT-0, it should be AT-4 and vice versa.

SASTP; ! Check the store utilization

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy