NOC SHIFT RESPONSIBILITIES

General Shift/all shift: 07:00 15:00 SURVEILLANCE/FAULT RECTIFICATION ADJUNCT-PDSN

Notice: Each shift has designated Assignments: as indicated on the schedule. It is the Responsibility of the surveillance/fault rectification person to complete the following tasks during the shift:

[General Activities]

Change of Shift
New Shift Arrives 30 minutes before shift duties begin Open events/outages are discussed and updated Open TTs are discussed and updated (action taken, action pending, expected reporting times from staff dispatched, escalation criteria, etc.) Review the event log for the past 24 Hrs event log Review the complete Fault List New Shift Engineers takes charge after making entry in the event log.

Surveillance Activities at TTI

Perform surveillance & control alarms for PDSN/PHE2 Determine Severity and Attempt to reset Alarm via software commands Check the connectivity between PDSN and PHE2 by Pinging the Phe2 IP address from the PDSN. Record all request information for any office on the Surveillance Event Log.

Surveillance Activities at SMSC

Perform surveillance using Common Element Manager (CEM) GUI interface Record all request information for each site on the Surveillance Event Log.

Fault Rectification Activities

Perform Fault Rectification activities for PDSN adjunct covering all areas Perform analysis of alarm error & maintenance messages that could lead to potential service impact Put down alarms after service impact is determined to be Not Service Impacting and alarm has been cleared. Only alarms with Pending TT should remain up Create, Update, perform Preventive Maintenance routines and schedule.

NOC SHIFT RESPONSIBILITIES

24 May, 2012 PROPRIETARY This information is privileged and confidential. Use is limited To evaluation purposes only in response to UCS / NOC information needs. 1

All Shift:

07:00 15:00 SURVEILLANCE/FAULT RECTIFICATION ADJUNCT-PDSN

Notice: Each shift has designated Assignments: as indicated on the schedule. It is the Responsibility of the surveillance/fault rectification person to complete the following tasks during the shift:

Trouble Ticket Management

Open/Close and update trouble tickets for Critical & Major Alarms conditions and recurrent events Put down any associated alarms once TT has been Closed. Ensure all Referred & Pending TT's are checked as per intervals Ensure that ALL Service Affecting Incidents are noted / updated on the Surveillance Event Log, that a Trouble Ticket has been generated and proper attention is given Account of irregular activity on the log and associated Trouble Tickets number as applicable Coordinate Work with RDN/IDC, NNOC Switch guys and Lucent RTS Take all necessary actions to resolve the problem / Close the Trouble Ticket.

Escalation / Notification If a service affecting outage occurs, immediately notify CDMA Shift Head and the next level of support
[e.g.: any duplex failure of PROC, DISK, COMM, CCS7, NETW] Perform escalation as directed by management and escalation procedures Work directly with suppliers and carriers to resolve issues or troubles not with standing the ongoing surveillance of the SMSCs. If more than 30 minutes is required to work the trouble, generate a trouble ticket and refer to next level of support via the Trouble Ticket System and request TAC assistance as required.

Miscellaneous
Review all NOC communications issued by management & perform any requested actions Respond to customer and management special request, as needed Ensure that ALL Service Affecting Incidents are noted / updated on the Fault Rectification Event Log and a Trouble Ticket has been generated Ensure that bulletins, flashes, notifications, or Trouble Tickets are reviewed Coordinate Work with the Field Operations Engineers Maintenance Engineers (CO&M) when onsite.

Daily Routine Activities to be performed

Ping all the PHE2 IP address from PDSN to check the connectivity.

ALARM MANAGEMENT:
24 May, 2012 2

PROPRIETARY This information is privileged and confidential. Use is limited To evaluation purposes only in response to UCS / NOC information needs.

Ghaziaba UP W d HARYANA Ambala HARYANA Ambala Ghaziaba UP W d HARYANA Ambala

Ghaziaba d AMBALA AMBALA Ghaziaba d AMBALA

LUCENT 5ESS UBGZBDXXXXM001MSC001 PHE2 ALARM: PDSN STATUS:OOS --PDSN IP A LUCENT 5ESS HBAMBLXXXXM001MSC001 PHE2 ALARM: PDSN STATUS:OOS --PDSN IP A LUCENT 5ESS HBAMBLXXXXM001MSC001 PHE2 ALARM: PDSN STATUS:OOS --PDSN IP A

LUCENT 5ESS UBGZBDXXXXM001MSC001 PHE2 ALARM: PDSN STATUS:OOS --PDSN IP A LUCENT 5ESS HBAMBLXXXXM001MSC001 PHE2 ALARM: PDSN STATUS:OOS --PDSN IP A

Above alarm can be generated due to following reasons: ---- PDSN rebooted ----Connectivity between PDSN and PHE2 was lost due to fault in RDN network ---- PHE2 card is degraded ---- Call was failed due R_P registration was not success full ---- SM module is not processing the data calls FAULT ISOLATION: A) Ping the IP address of PHE2 from PDSN. If you are able to ping the ip address of PHE2 then do following: I) Telnet to AAA server and grep the latest accounting records and see if the calls are registering. grep 97.236.40.67 AAA0201_20030603_1845_00001.act*|tail "06/03/2003","19:00:00","BANP01C08","Stop","Gx99VN","200","Gx99VN"," 97.236.2.9", "2715","1","97.238.116.170","SBR-CL DN="Gx99VN" AT="200"","111111057273115","BAN P01C08","2","5210","40650","1","0.0.0.0","97.236.40.67","10552576","2337","2321" ,"0","0","0","0","0","0","1","0","3","0","1","0","0","0","0","0","13","0","9c II) If the call is not registering in AAA server then telnet to PDSN and monitor the ppp protocol.

PDSN PPP Monitor Select a letter for one of the following options: C) Monitor PPP Call Events. I) Monitor a specific interface. N) Monitor the next session that starts up. U) Monitor a specific user. T) Monitor a specific calling number.
24 May, 2012 PROPRIETARY This information is privileged and confidential. Use is limited To evaluation purposes only in response to UCS / NOC information needs. 3

X) Exit the monitor. Please Enter Your Choice : Monitoring the next session to start up. Decode tracing started, press ESCAPE to stop; press X for hex tracing. Outgoing PPP Data on interface: vha:1112 Time: 03-JUN-2003 19:28:03 LCP CFG_REQ MRU 05 ea ASYNC_MAP 00 00 00 00 AUTH_TYPE c0 23 MAGIC_NUM 58 f4 c6 9f PROTO_COMP AC_COMP Outgoing PPP Data on interface: vha:1112 Time: 03-JUN-2003 19:28:05 IPCP CFG_REQ COMPR_TYPE 00 2d 0f 00 NEW_ADDRS 61 e8 02 02 Incoming PPP Data on interface: vha:1112 Time: 03-JUN-2003 19:28:05 IPCP CFG_REQ COMPR_TYPE 00 2d 0f 01 NEW_ADDRS 00 00 00 00 PRIM DNS 00 00 00 00 SEC DNS 00 00 00 00 Outgoing PPP Data on interface: vha:1112 Time: 03-JUN-2003 19:28:05 IPCP CFG_NAK COMPR_TYPE 00 2d 0f 00 NEW_ADDRS 61 e9 05 c7 PRIM DNS 61 fd 19 09 SEC DNS 61 fd 19 0a Incoming PPP Data on interface: vha:1112 Time: 03-JUN-2003 19:28:05 IPCP CFG_ACK COMPR_TYPE 00 2d 0f 00 NEW_ADDRS 61 e8 02 02 Incoming PPP Data on interface: vha:1112 Time: 03-JUN-2003 19:28:06 IPCP CFG_REQ COMPR_TYPE 00 2d 0f 00 NEW_ADDRS 61 e9 05 c7 III) If you see the IPCP CFG_ACK that means user are authenticating and getting an IP address assigned and there is no problem on PDSN. IV) If you do not see any data coming in MON PPP then have the 5ESS Switch expert check the SM / PHE2 and see if the data calls are being processed.

24 May, 2012

PROPRIETARY This information is privileged and confidential. Use is limited To evaluation purposes only in response to UCS / NOC information needs.

B) if you can not ping the IP address of PHE2 from PDSN then do following: Do a trace route of PHE2 from PDSN , wherever the trace route stops, look at the Network diagram and see who controls that device and report the problem to that department and work along with that individual to resolve the problem. : MUMP01C01>traceROUTE 97.236.70.130 HOP IP ADDRESS ROUND TRIP TIME 1 97.232.1.1 0 2 97.208.2.22 0 ------------ If the traceroute stops here then its RDN problem 3 97.128.0.2 30 4 97.236.70.130 30

ESCALATION: --If the problem is on switch then please call the RTS at X5663 and open an AR# If the problem is on PDSN then call 3Com at X-5776 If the problem is on RDN network then call at X-2703 to 2708

24 May, 2012

PROPRIETARY This information is privileged and confidential. Use is limited To evaluation purposes only in response to UCS / NOC information needs.