Guidelines for All OMCR Users (including remote/ SSA terminals)

1. RNUSM window is real time radio database application which is updating with NE status also. It is
observed that OMCR users start the activity from RNUSM. They first open RNUSM and then navigate other applications from RNUSM i.e. BSSUSM, Alarm Monitoring etc. Rather doing this they should click the respective icon i.e. BSSUSM, AS, DCN etc.

RNUSM to be open only for BTS creation, not for monitoring purpose.

2. Logout from OMCR client (especially from remote workstations) after you finishes the work or
before leaving for the day. Close & Exit all opened applications. Dont quit the A1353-RA Icon before closing or exit all the applications i.e. BSSUSM, RNUSM, Alarm Windows, Netscape Windows etc. Then exit from workstation (Logout) to see login screen. This practice will avoid the OMCR HANG & OMCR SLOW situations.

3. Acknowledge cleared alarms from Current Alarms list: After acknowledge cleared alarms, it will
move to History list. If cleared alarms not being acknowledged, current list will be overflow and active alarms will also be moved to history. 4. Inhibit Alarm reporting: Alarm reporting must be inhibited (locked) for all unused SBL or device to avoid huge false (or unused alarms) in current list. It will help in alarms handling process.

5. Keep minimum WINDOWS opened in OMCR Terminal. Once you finish the work in any application
WINDOW, it is recommended to close it rather just minimizing it. 6. Open only one A1353-RA (OMCR application session) icon box from each OMCR Client. Single Click on A1353-RA hexagonal icon. Capacity of OMCR session is limited and if you open more than 1 session on 1 machine you are preventing other users to LOG-IN in OMCR.

7. BSC Overload Alarm: If you observe BSC Overload Alarm on any DTCC or TCUC, clear it first
manually by restart that device. Generally overload alarm on DTCC is reported due to fluctuation on respective AterMux link. If PCM is not stable you can lock Ater TP for respective AterMux link. If traffic is not started even after alarm cleared on DTCC, you may restart both SYS-CPRC one by one and lock unlock N7 link. 8. Delete PRC: After PRC activated it has to be deleted to having better speed of RNUSM and avoid the parameters over written or reverting. 9. Delete old ODMC files from BSSUSM (From PMC Search campaign and delete manual reports) 10. BSC Login: Local BSS team should be able to login in both (G2 and MX) type of BSC for troubleshooting with online support in case of BSC to OMCR connectivity is down.

Guidelines for QoS monitoring team at Bhopal, Indore, Jabalpur & GWALIOR

1. Type 18 Report analysis: It will detect the faulty AterMux/ Alink which is producing one way
or calls problem on ACH. Further AterMux PCM has to be verified by check status of N7 link and loop break end to end.

2. Type 9 report analysis: It will be helpful for N7 related issues. 3. Paging load and Paging discard: Monitoring of MC925g and MC925h from hourly obsynt
report (peak hour) to detect paging load, congestion and problem of terminating calls. If Paging attempts is very high, proper LAC planning required. If paging discard is high (resulting Out of coverage) BCCH to be defined in non-combined mode. Related indicators are GCCPGRQABN, GCCPGRQACR, GCCPGRQN TRX1 configuration: TS0= BCC, TS1= SDH After this modification, cell broadcast has to be done from CBC server 4. Monitoring MC01 and MC02 from Obsynt report for MT and MO calls.

Additional GUIDELINES for Bhopal and users: 1. OMCR Backup: Please ensure you are doing OMCR Full Backup (automatic or manually) of OMCR server. [a] Before applying for OMCR backup make sure no network modification are in progress and if possible logout from all Workstations for respective OMCR. [b] Before applying the OMCR Full backup check the status of all disks by command # metastat or # metastat | grep State . State of all partitions should be Okay. [c] For manual backup you must get Backup Successful message in Netscape window where you have applied the backup. [d] For automatic backup check the backup log in mail as axadmin at Task Bar Menu. [e] For both case you can verify the TAPE by command # cat /dev/rmt/0cn. Check that no error reported in Tape content. [f] Keep the track of tape and store it at safe place to make it available whenever required.

2. New BSC Integration in OMCR: After successful discover of new BSS, kindly verify & modify all
the BSC related parameters from RNUSM (edit BSC) with reference to 1ML BSC in respective regions. Also modify the LAC & Cell ID of 2 default BTS in each new BSC to successful discover of next new BSC in same OMCR host.

3. Monitor the session on remote workstations: At end of the day, kindly check that all users from
all remote workstations have been LOGed-OFF. You can see the current users & session active in each HMI by command # ps ef | grep sess . If more than one session is active from any remote workstations, you have to inform them to exit the session. 4. If any message reported by system on screen and you are not sure about that massage, please inform us immediately.