Académique Documents
Professionnel Documents
Culture Documents
Objective:
The objective of this document is to describe O & M workflow, salient guidelines for
maintenance of Multiplay Broadband network and define the responsibilities of various
node incharges to ensure uninterrupted service of Broadband and customer satisfaction.
Contents:
1. Broadband network elements and Maintenance categories
2. Responsibilities of Node incharges
3. O&M Process and Support mechanism by the vendor
4. Annexure A& B Trouble Tickets / Escalation Mechanism (REFER CONTENTS
IN UTSTAR TSC PORTAL)
5. Annexure C UTSTAR RMA Procedures (REFER CONTENTS IN UTSTAR
TSC PORTAL)
6. Annexure D- Contact details of vendors / Technical Support Centers (REFER
CONTENTS IN UTSTAR TSC PORTAL)
1. Broadband network elements and Maintenance categories:
(Supplied by M/s UTSTARCOM and THEIR SUB-VENDORS)
Broadband Network distributed all over India comprises of following elements:
1. BNGs situated in all A type cities (Supplied by M/s UTSTARCOM)
2. Tier1 situated in all A&B type cities co located with BNGs (Supplied by M/s
UTSTARCOM)
3. Tier2 distributed all over India in all major cities
4. STM1 converter to connect OC city T2 to nearest T1.
5. Transmission media involved between T1&T2 and T2& DSLAM
6. AAA servers at Bangalore,Chennai,Pune,Kolkata,Noida
7. SSSC server situated in Multiplay Broadband NOC- Bangalore, DRNOC -Pune,
and RPOPs at NOIDA, KOLKATA,CHENNAI.
8. eMS server for DSLAMs situated in Bangalore, Chennai
9. eMS server for RPR at Bangalore, Pune(DR)
10. eMS server for BNGs at Bangalore, Pune(DR)
11. eMS server for OCLANs at Bangalore, Pune(DR).
12. eMS server for CPEs at Bangalore , Pune (DR)
13. SSSS servers situated in Bangalore, Pune, Noida, Chennai, Kolkata
14. DSLAMs distributed all over India
15. CPEs of different makes at customer premises
16. Local lead between DSLAM port and CPE
17. Netsweeper Servers (4 Locations) Two As Policy Managers and 4 as Enterprise
Filters.
NOC
External help / Vendors
2. Responsibilities of various Node In-charges:
A1/A2/A3/A4 City Node In-charges (where BNG, RPR T-1, AAA are
installed):
1. Monitoring all the concerned equipment and inter NE links of their region
regularly. Handling/solving/escalating the complaints received from L1.
2. Monitoring/ solving/escalating the configuration related and traffic related
problems of T1 & T2 of same city and other city.
3. Regularly checking the media between T1 and T2 of same city and other city.
4. Monitoring all the media converters at T1 location connected to T2s of other
cities.
5. Solving the problems related to ports of DSLAM and T2
6. Resetting the hanged ports in DSLAMs
7. Observing the ports of T2 and T1 for any CRC errors. Monitoring Power
levels and reporting to NOC about any abnormal power levels.
8. It will be the responsibility of node in-charge to rectify the faults that are
escalated from call center through appropriate co ordination with DSLAM incharges and field units. Since the remedy terminals will be available only up
to node in-charges at the moment.
9. Creating the BB VPN domains for existing/new Broadband customers.
Providing the NOC with relevant information about NAS port IDs, DSLAMs
for creating / configuring required PVCs for VPN / IP TV etc.,
10. Using eMS client for monitoring the T2 and DSLAMs and escalating the
faults.
11. Monitoring the status on SSSS /AAA and escalating to L3(NOC) in case of
problems. Intimating NOC about any spurts /abnormality/lapses during
generation of CDRs.
12. Maintaining and reporting any faults in respective eMS servers to NOC.
13. Raising RMA and doing follow-up for equipment related problems and major
faults which are not solved with in reasonable time as in Annexure A,B & C
to the concerned vendor.
14. Localization of problems/faults is to be done as far as possible locally and
NOC/Vendor may be contacted only after trying all possible means.
15. For provisioning and other operational activities for handling Multiplay
connections through P.3 platform please refer to the manual issued by Data
Networks along with release notes issued from time to time
16. A register should be maintained with necessary entries like equipment Sl. No,
date of fault,etc for Faulty cards/CPE sent for repair. Hard copies of reports
from UTSTAR Technical Support Center (UTSTAR TSC) website which is
www.utstarcomtsc.bsnl.co.in are also to be maintained.
17. Prompt action is to be taken to send the faulty cards for repair immediately in
case it is replaced in advance by vendor.
18. Any major work like giving hard reset to T1/T2/DSLAM to be done only after
concurrence with NOC/Vendor.
19. Regularly use the website where UTSTAR TSC portal is hosted for latest
information on NOC activities.
20. Port unbinding, wherever necessary, to be done by the node incharges.
21. All issues are to be addressed by e-mail only .
B,C and Other type city Node In-charges (where T-2 is installed) :
1. Monitoring all the concerned equipment and links of their region regularly
2. Handling and solving the complaints received from L1 and informing
DSLAM in charges/field units through email/ phone/FAX/ UTSTAR TSC
web portal wherever required/related
3. Monitoring and solving the problems related to DSLAMs and T2/
OCLANs
4. Checking the media between DSLAM to T2 and T2 to T1 / other RPR T2s
/OCLAN
5. Monitoring the media converter at T2 /OCLAN location
6. Solving the problems related to ports of DSLAM and T2 / OCLAN
7. Solving the complaints pertaining to excess billing
8. Addition of new cards in DSLAMs and activating the ports
9. Resetting the hanged ports in DSLAMs, in case not possible intimating the
node A-city node in charges to carry out this activity.
10. Changing of FE/GE ports in T2 / OCLAN if uplink is not working
11. Creating the Broadband user-ids with port binding and communicating to
field units.
12. Keeping information about DSLAM ports of the BB VPN userids for
existing/new Broadband customers.
13. Attending the faults related to Modems
14. Attending the faults related to local lead.
15. Shifting/re parenting of DSLAMs
16. Using eMS client monitoring the T2 and DSLAMs and attending to the
faults.
17. Node in-charge should solve the problems related to T2/OCLAN and
DSLAM by themselves and co ordinate with field units
18. It will be the responsibility of node in-charge to rectify the faults that are
escalated from call center through appropriate co ordination with DSLAM
in-charges and field units since the remedy terminals will be available only
up to node in-charges.
Responsibilities of NOC
I Configuration management :
1. Configuration in T1,T2, OCLANs and BNGs for port expansion in
DSLAMs
2. Configuration in T1/BNG for addition or shifting of T2 and DSLAMs
3. Configuration of VPN instance, IP pool and domain in BNGs for VPN over
BB Multiplay N/W.
4. Configuration in BNG/T1/T2SSSS/SSSc/DSLAMs for value added services
like IP TV, wifi, wi-max, gaming services, Bandwidth On Demand etc.,
5. Changes in configuration in servers involved in Broadband network
6. Interacting with Project1 and Project -3 team for works involving
integration with them. For example, CDR issues , routing of external IPs for
CDN/ VPN servers etc.,
II Monitoring of networks:Monitoring of various equipment and links are done on the basis of their
importance in the networks i.e. the criticality of equipment/link.
Hourly monitoring of AAA Server, BNGs, Traffic on BNG,
Authentication (AAA) servers, DHCP,DNS, Netsweeper, Motive
etc.
Continuous Monitoring of Tier-1,Tier-2 switch, link between Tier1 & BNG, and loading on inter N/E links
Regular monitoring of traffic at each of N/E elements as per
BSNL/ TRAI requirements, ensuring sufficient static / dynamic IP
pools at all BNGs and recommending BSNL for any
augmentations.
Regularly watching activity between AAA and BNGs for any
critical errors leading to loss / spurt cases in CDRs.
Regularly monitoring replication process between NOC and DR
NOC by keeping a well integrated schedulers in SN DR.
Weekly monitoring of opening of various links of important
websites like NIC, Trading websites, E-governance, e-learning
etc. from Broadband networks are carried out in order to take
proactive measures
Daily routines:
Weekly Routines
8.
Product Number
Serial Number
A copy of the RMA (Repair Material Form) and Fault tag is to be sent along
with the faulty material.
As far as possible use the original packaging to prevent any physical damage
in transit/ handling Otherwise proper packing has to be made to ensure NO
DAMAGE is done to the faulty units in transit.
In case of any damage/burn noticed at the time of receipt of the card, the
same will be returned back without servicing and it will not qualify for any
repair/replacement or warranty. The same condition applies to burnt cards as
well
Ticket number/(s) should be indicated on the outside the cartons. If possible,
the RMA copy should be pasted on the Cartons.
If more than one product - per carton - is shipped, label each product with the
correct serial number.
Ensure that every material should contain the Ticket number.
the
10. A register should be maintained with necessary entries like equipment Sl. No,
date of fault, etc for Faulty cards sent for repair.
11. Prompt action is to be taken to send the faulty card for repair immediately in
case it is replaced in advance by vendor.
Configuration
issue/ Known
issue/
issue/H/W
H/Wissue?
issue
YES
NO
YES
Issue
Closed
NO
Configuration
issue/ Known
issue/issue?
H/W issue
YES
Issue
Closed
NO
Customer opens a Service
request with UTS Escalation
Centre through:
Phone, E-mail or Web
Phone # - 18001801204
E-mail - apac.support@utstar.com
Web
- http://support.utstar.com/
YES
Configuration issue/
Known issue?
Issue
Closed
NO
Escalation Centre works on the issue.
Customer provides the required logs.
YES
Configuration
issue?
Issue
Closed
NO
UTS H/W issue?
YES
Issue
Closed
NO
UTS to work with R&D and fix the issue
http://www.utstarcomtsc.bsnl.co.in