FTTH Technical Guideline, Troubleshooting & Process Work Flow (UKM project based)

Last update: 1 April 2009

Objective
To show the technical process and guideline on FTTH (OLT, ONU, Fiber) supported by respective department: JARING Network Infrastructure (OIR) NMC Wireless Access JARINGs Team Access TFM AFM MELCO (JARINGs Partner) ATI (JARINGs Partner) To show JARING FTTH technical guideline & troubleshooting To show JARING FTTH contact person

FTTH Technical Responsibility Demarcation Flow Chart

Conceptual Diagram How It Works

Overall FTTH Technical Support Escalation Work Flow/Process between JARING,ATI & MELCO

Overall WIFI Technical Escalation Support Workflow

JARING JARING HELP DESK 1st Level Support JARING Call Center 03-8991 7080 E-mail : onehelp@jaring.my

JARING Technical Support

UKM STUDENTS

2nd Level Support Onsite Engineer

Overall FTTH Technical Escalation Support Workflow

Start

UKM PTM

NMC

Access

OIR

Jaring Support Engineer

Troubleshoot on : Power failure on ONU/OLT/sw itch/ AP Splitter Power supply destruction FRP cable (physical checking) ,UTP cable (between switch to AP and switch to OLT)

Wireless Access
Troubleshoot on : AP

Inbound Call/Email

Received Jims alert on OLT/switch failure

Troubleshoot problem : check connectivity (Fiber) ping into device (OLT,ONU)

Check fiber optic (FRP, single mode) Check patch cord Check patch panel Verify and restore UTP cable between switch to OLT

Identify and analyze the problem : check status of switch connected to OLT (up/down)

Create TT

AP failure not resolve?

Internal TT Respond time within 24 hours Resolution and Replacement of AP/Switch/Router within 2 working days

Access Technical Escalation Support Workflow

Access
Start Purchase equipment Troubleshoot on : ONU OLT Splitter

Innatech

AFM
Log RMA

End

Troubleshoot problem : check connectivity (Fiber, FRP cable) remote into devices (OLT,ONU, Switch)

Advise OIR to replace equipment

No

No Problem resolve? Problem not resolve or problem due to equipment failure? Equipme nt under warranty ? (1 year)

No

Yes Yes Update Access problem resolve

Advise Access to conduct RMA

Update Access status

Update CIC problem to resolve

8
End

Support Engineer Technical Escalation Support Workflow

Support Engineer
Start

TFM
Liaise with contractor to restore fiber optic cable/UTP cable

AFM

UKM
Verify and Restore fiber optic cable

Log RMA

Troubleshoot on : ONU power OLT power Splitter Switch power AP FRP,UTP cable (between switch to AP and switch to OLT)

Fill up and submit Facilities Request Form

End Update problem status Problem due infra : FRP cable (physical checking) UTP cable (from switch to OLT)

Update problem status

No Problem not resolve

Problem due infra: Single Mode Fiber (after verify by OIR) Power destruction

Yes

Update CIC TT to close

Problem due device: AP Splitter

Conduct RMA or issues to purchase item

9
End

OIR Technical Escalation Support Workflow

OIR
Start

TFM
Liaise with contractor to restore fiber optic cable

Support Engineer
Report to UKM PIC

UKM
Verify and Restore fiber optic cable

Check fiber, FRP cable Check and restore patch cord Check and restore patch panel Verify and restore UTP cable between switch to OLT

Fill up and submit Facilities Request Form

Update problem status

Update CIC TT to close

Update problem status

End No Problem due to infra

Problem not resolve?

Problem due to single mode fiber

Yes

Update problem status to Access

End

10

FTTH Technical Guideline & Troubleshooting

11

List of troubleshooting

AREA 1. Not able to connect 1. Fiber problem

ACTION Perform logical-link loop back tests Requirement needed: NE-OSS installed on a desktop or laptop PC. OLT M-SVCONT cards connected. OLT Management Window open. Please refer to document NE-OSS Handbook 11 Logical Link Loop back Testing fix11Dec for detail troubleshooting. Identify OLT problem At the time of displaying the OLT Management Window, or when the display is refreshed if the Status Icon does not show the normal coloring, a problem has occurred.

2. Alarm management when alarmed.

1. OLT problem

12

List of troubleshooting AREA ACTION Identify OLT problem The OLT Management Window shows the cards installed in the OLT and, by means of their colors, the alarm etc. status of each unit. Please refer to document NE-OSS Handbook 08 01-10 Eqpt Data Acquisition & Setting fix11Dec

3. Row of data in an LLID Management Window is not the normal color (black)

1. ONU problem

Identify ONU problem Please refer document NE-OSS Handbook 09 ONU Data Acquisition & Setting fix11Dec on topics:
Display the LLID Management Window

Display the LLID Properties Window 1. Unable to start the NE-OSS

4. When starting the NE-OSS, the command-line window closes and the NE OSS Main Screen fails to Appear.

The Java 2 Runtime Environment is probably not installed.

5. The OLT Management Window is not displayed or Refresh Screen fails, and the error box shown below appears.

1. Unable to connect to OLT

Check the network settings are correct Check the LAN cable is connected correctly (check that the ping command gets a response [see Windows Help]). Check that the registered OLT IP addresses and Set/Get community names are correct. Please refer to document NE-OSS Handbook 01-03 Startup Settings fix11Dec for detail action.

13

List of troubleshooting AREA 6. When setting up equipment information, the setting fails with the following error box ACTION Display the Error Factor Window The Logical Link concerned is not operational

7. Row of data in an LLID Management Window is not the normal color (black)

1. ONU problem

Identify ONU problem Please refer document NE-OSS Handbook 09 ONU Data Acquisition & Setting fix11Dec on topics:
Display the LLID Management Window

Display the LLID Properties Window 1. Unable to start the NE-OSS

8. When starting the NE-OSS, the command-line window closes and the NE OSS Main Screen fails to Appear.

The Java 2 Runtime Environment is probably not installed.

14

List of troubleshooting AREA 9. Error Appears when Making or Changing Equipment Settings 1. Equipment Setting Error Display the Error Factor Window ACTION

10. TRAP data is not displayed when the TRAP display Window is opened. 1. TRAP error

See the descriptions of the errors in the Attachments. In the above example the Logical Link concerned is not operational.

Confirm that the network settings are correct Confirm that the LAN connections are correct Check the TRAP sources are set up for the NE-OSS PC, and also the equipment-side settings. Confirm that TRAP sending is not inhibited Confirm that the network settings are correct Confirm that the LAN connections are correct \ Check that the registered OLT IP addresses and Set/Get community names are correct. If Steps 1~3 uncover incorrect settings, correct them. If the settings are correct, follow the procedure below. For FTP LOGIN failure Check that no other operator is has made an FTP connection to the equipment. Only one FTP process can be executed at a time. Wait until the process has been completed. For FTP PUT failure Confirm that the required software file exists in the designated directory under the correct file name. Refer to document 8.6. 15

11. Software download fails with FTP LOGIN Failure or FTP PUT Failure displayed.

1. Unable to Download Software.

List of troubleshooting AREA 12. OLT Log display fails with FTP LOGIN Failure or FTP GET Failure\ displayed. 1. Unable to Display OLT Log ACTION Confirm that the network settings are correct Confirm that the LAN connections are correct Check that the registered OLT IP address and Set/Get community names are correct. If Steps 1~3 uncover incorrect settings, correct them. If the settings are correct, follow the procedure below. For FTP LOGIN failure Check that no other operator is has made an FTP connection to the equipment. Only one FTP process can be executed at a time. Wait until the process has been completed. For FTP GET failure Confirm the correct temporary folder exists to receive the log from the OLT. If <Install_directory>EponOpsexecuserOltLog does not exist, create it.

16

CONTACT PERSON
JARING CIC
SUPPORT ENGINEER

OIR

ACCESS

TFM

AFM

INNATECH

Working Hours Monday - Friday (8000 am 1100 pm) Tel: 03-89917080 MY015: 01548155515 Email : ccsupervisor@jaring .my

Working Hours Monday - Friday (830 - 530pm) Tel: Email: zaim.alias@jaring. my Staff: 1) Mohd Zaim Alias

Working Hours Monday - Friday (830 - 530pm) Tel: 03-89965000 E-mail: J-inm@jaring.my

Working Hours Monday - Friday (830 - 530pm) Tel: 03-89965000 E-mail: access@jaring.my

Working Hours Monday - Friday (830 - 530pm) Tel: 0389965000 E-mail: tfm@jaring.my

Working Hours Monday - Friday (830 - 530pm) Tel: 03-89965000 E-mail: afm@jaring.my

Working Hours Monday - Friday Tel: E-mail: Response time: 4 hours Resolution time: within 24 hours Equipment replacement: 10 working days Equipment Checking & Maintenance: Every 3 months

Staff: 1) Low Pei Tien

Staff : 1) Mohd Fakhari B Deraman

Staff : 5 persons One person will be on standby after working hours including weekend.

Staff : Shaharudin Mohd Sharifudin

Staff : Abu Bakar Bin Mohamed Eusoff

All staff work on normal working hours.

17