THE NEXT GENERATION ENTERPRISE NETWORK OPERATION

Author by Muharam Nur Cahyadi

OUTLINE

1. Who is Network Operation Center’s Enterprise ?2. How to Manage NOC Enterprise to achieve Target of Business

Company ? Current Process Proposed Plan Improvement Success Indicator

NOC ENTERPRISE

NOC Enterprise in PT Mora Telematika Indonesia has been established live since June 2015.NOC Enterprise focus handling Customer Enterprise using GPON (such as FTTH/FTTB/FTTX) and NON-GPON (Backbone MTI and 3rd Party)NOC Enterprise currently have personal as following :1. Fault Management (1 Person as Supervisor and 7 Person as Shift

Team)2. CCP ( 1 Person as Supervisor and 2 Person as Shift Team)NOC Enterprise has been established coordinate with Oxygen Technical Support (OTS), Technical Helpdesk (THD), Field Operation Center (FOC), Engineering PON (Eng. PON), and Customer Support (CS).

RESPONSIBILITY NOC ENTERPRISE

RESPONSIBILITY NOC FAULT ENTERPRISE (NON-GPON)

IMPROVEMENT PLAN

FCAPS NOC ENTERPRISE

FAULT ROADMAPS

NETWORK OPERATION CENTER TOOLS

1. MRTG by Cacti2. Network Performance Management by Solarwinds and

Observium3. Network Monitoring by The Dude4. Network Database System by Moraapps5. Network Fault Ticketing by Helpdesk Moratelindo / Oxygen6. Network GPON RADIUS by FTTH Radius Moratelindo7. NMS Client Server for Each Product GPON and SDH/DWDM

Usulan Proses Fault for GPON

The Dude / Complain From THD:More than 2 Customer Down dalam waktu yang

bersamaan

Identification Problem from OLT:

1. Show onu info | include Inactive2. Show onu detail-info [PON

Port]3. Show mgmt ip-path [PON Port]

Create TT Internal dan Email to Team Operasional and Project (If Under Project)

Call to :Oxygen Technical

Support

Update Ticket berkala 30 -60 menit

Pastikan setiap PON PORT yang Inactive mengalami Symptom LOS

dan Waktu bersamaanYes

Jika Tidak ada yang Inactive (Status PON Port Normal), namun IP Public Customer banyak yang tidak bisa

diaksesNo

OLT Can’t Access ONT Can Access ???

Escalation to FOC (Bambang FOC) by Email and Phone

Escalation to Engineering PON (Herry) by Email and Phone

No

Yes

Analyzing :“sho syslog local non-volatile reverse”

Trouble Shooting by NOC dan Eng PON

Not Solved

Still Down

Closed Ticket

Back to Normal

Back to Normal

Back to Normal

True

Link Back to Normal :1. Cek Traffic di MRTG Oxygen

2. Cek IP WAN di ONT User3. Confirmation From THD dan CS

Problem Access FDT or FAT

Created TT Internal

Problem Backbone

Problem OLT

Trouble Shooting by NOC dan Eng PON

Created by Men Behind Oxygen.id

Flow Trouble shooting for NOC F ault Enterprise

Call to :Project LTE or FTTB

Force

If NeededRestart OLT

Escalation to Engineering PON and Vendor by Email

and Phone

Update Ticket berkala 30 -60 menit

External

Improvement

1. Migration to FTTH Network2. Collect Data Customer and

Alocation Core Using LTE

Backbone Fault Management

Alert(Pastikan TT dibuat)

Via SDH

Transmission

Via Direct Core

Coordination to NOC TRX1. Pastikan Tidak Ada Alert

2. Jika No Alarm , Pastikan Traffic Lewat (Data Statistic IN/OUT)3. Jika Ada Alert, Pastikan Ada Protection / Tidak ?

4. Delete Create X-Connect If Needed

Escalation to Eng.PON for Tshoot Onsite

Solved

Updated Setiap Progress Restorasi

secara berkala

No

Yes

Coordination to FOC Enterprise (Bambang FOC / FOC Jabo):

1. Email2. Call

3. Create Permit Access if Needed

Coordination to Eng.PON :1. Email

2. Call / Telegram / WA3. Create Permit Access if Needed

Yes

Trouble Ticket CLOSED

After Monitoring 2 Hours

No

X-Check again in Logical NOC Ent. :1. Down Cause Physical ?

(Power Off or Interface Down)2. Down Cause Logical ?

(Spanning-Tree, Vlan Looping, CPU/Memory Usage, Routing Problem)

Yes

BRAS Oxygen Down(Open TT and Email to All Division Operation)

Symptom

FISIK LOGICAL

Power OFFInterface From Aggregation Switch (UP/Down)

Spanning-Tree blocking by Aggergation Switch(See Logging Alarm at Aggregation Switch)

iBGP DownOSPF Down

CPU Utilization HighAnomaly

Escalation to Infra and FOCEscalation to TAC

No

Solved

Closed TT

Yes

ImproveEvery problem that must be provided information to the PIC escalation level corresponding to the duration of his downtime

CONFIGURATION ROADMAPS

“Everything Add and Change Configuration Must Be Update in Database System For Sharing Information to Other Division is Needed”

PROPOSED RULE CONFIGURATION NOC ENTERPRISE

Start

ONT Synchronize with OLT by

OMCI

Established

Check ONT Signal, ONT Device, ONT

Distance, etc

A

Yes

No

A

MIB Processing between OLT and ONT (Synchronize ONT with Radius)

MIB Processing is Successfull

Radius Problem synchronize with OLT

End

Yes

No

ONT Profile , ONT Description, and other technical data for ONT

successful binding and implement in OLT

What is Type Service WAN ?

Private WAN

Public WANPublic LAN

Allocated IP Public /32 by

DHCP

Allocated IP Public /28 to /30 by

Static Route

Segment Operator (NOC / Provisioning Team)

Segment Installer (CTS Team FTTbhx)

A

MIB Processing between OLT and ONT (Synchronize ONT with Radius)

MIB Processing is Successfull

Radius Problem synchronize with OLT

End

Yes

No

ONT Profile , ONT Description, and other technical data for ONT

successful binding and implement in OLT

What is Type Service WAN ?

Bridge WAN(VLAN)

Segment Operator (NOC / Provisioning Team)

Improved

Must Be Create One Profile for All NON-GPON using ONT

ImproveImprove

Topologi Core Cust. GPON Must be Input in Moraapps

IMPROVEMENT IN BACKBONE CONFIGURATION NOC ENTERPRISE

Improvement Plan :1.Create Protection Automatically FO Route in OLT

Configuration Networks [Decreasing Duration Downtime]

2.Create Guidance Reroute Manually for Network that established Core Protection [Decreasing Duration Downtime and Other Solustion if Point (1) Not Ready]

3.Every Activities Related to Performance Network GPON must be do in Windows Maintenance (Such as Preventif Maintenance and Corrective Maintenance)

4.Update Every Change Configuration for Network Customer Enterprise in Moraapps

PROPOSED PERFORMANCE ACTIVITIES NOC ENTERPRISE

Improvement Performance Plan :1. Collect All Parameters Performance Network Enterprise such as : Optical Information OLT (Every 2 Week Report) Assign PIC Healthy Check Information OLT (Monthly Report) Assign PIC Configuration File All OLT (Weekly Report) Assign PIC Create MRTG per ONT Customer Enterprise using GPON (Still Progress) – (Review

and Schedule Refresh Routine Yearly) Assign PIC2. Review Performance Customer Premium Class by NOC Enterprise Tools (Monthly

Report) Assign PIC3. Proposed Request Improvement Network to Engineering PON (Every Quarter)

Assign PIC4. Build Security Access Level for All OLT Assign PIC

2016Week 1 2 3 4 5 6 7 8 9 10

Optical Information Report9/26/2016

Healthy Information OLT Report9/27/2016

OLT Configuration File9/28/2016

Review Performance Customer Premium Class NON-GPON10/3/2016

Review Performance Customer Premium Class NON-GPON 2nd11/1/2016

Review Performance Customer Premium Class GPON10/4/2016

Review Performance Customer Premium Class GPON 2nd11/2/2016

OLT Configuration File 2nd10/5/2016

Optical Information Report 2nd10/10/2016

Optical Information Report 3rd10/24/2016

Healthy Information OLT Report 2nd10/25/2016

Request Improvement Network GPON to Engineering12/1/2016

9/26/2016OLT Network Performance Report

10/3/2016

9/26/2016Collect Network Topology Customer Enterprise outboundary FTTH Network

10/10/2016

9/27/2016Guidance Reroute Manually OLT FO Route

9/30/2016

9/28/2016 10/17/2016Create MRTG Per ONT Customer using GPON

10/18/2016 11/18/2016Build Management Security Access Level OLT

Time Plan NOC Enterprise for Two Month Ahead

Manager NOC Enterprise

Supervisor NOC FM

Enterprise

Shift E(1 Person)

Shift Leader (L)

(1 Person)Shift A

(2 Person)Shift B

(2 Person)Shift C

(2 Person)Shift D

(2 Person)

Supervisor NOC CCP

Enterprise

Shift F1(2 Person)

Shift F2(2 Person)

Proposed Organization Structure NOC Enterprise

*Proposed Leader (L) For Lead and Monitor Daily Activities & Reporting All Shift Team Enterprise

Currently Manager NOC Enterprise still merge with NOC Backbone

Success Indicator

1.Decreasing Duration Time2.Database Customer Valid3.High Performance Network GPON Architecture4.Improving Effectiveness Performance of Staff

Network Enterprise5.Increasing Reliability and Capability

Performance of Network Enterprise6.Contribute to Business Company in Sector

Enterprise

Terima Kasih