This document provides an outline for a course on troubleshooting MSANs. It covers classification of narrow/broadband service faults, specific fault analysis approaches, examples of troubleshooting narrowband and broadband faults for various network elements like the user terminal, S200 transmission system, and U300. Common broadband service faults involving VLAN, PVC, and user end configurations are also discussed. Specific examples provided include troubleshooting noise during conversions, remote E1 alarms, ADSL subscribers unable to view web pages, and slow broadband access during evenings.
This document provides an outline for a course on troubleshooting MSANs. It covers classification of narrow/broadband service faults, specific fault analysis approaches, examples of troubleshooting narrowband and broadband faults for various network elements like the user terminal, S200 transmission system, and U300. Common broadband service faults involving VLAN, PVC, and user end configurations are also discussed. Specific examples provided include troubleshooting noise during conversions, remote E1 alarms, ADSL subscribers unable to view web pages, and slow broadband access during evenings.
This document provides an outline for a course on troubleshooting MSANs. It covers classification of narrow/broadband service faults, specific fault analysis approaches, examples of troubleshooting narrowband and broadband faults for various network elements like the user terminal, S200 transmission system, and U300. Common broadband service faults involving VLAN, PVC, and user end configurations are also discussed. Specific examples provided include troubleshooting noise during conversions, remote E1 alarms, ADSL subscribers unable to view web pages, and slow broadband access during evenings.
This document provides an outline for a course on troubleshooting MSANs. It covers classification of narrow/broadband service faults, specific fault analysis approaches, examples of troubleshooting narrowband and broadband faults for various network elements like the user terminal, S200 transmission system, and U300. Common broadband service faults involving VLAN, PVC, and user end configurations are also discussed. Specific examples provided include troubleshooting noise during conversions, remote E1 alarms, ADSL subscribers unable to view web pages, and slow broadband access during evenings.
AM_TS01_E2_P1 AM_TS01_E2_P1 Trouble shooting of MSAN Trouble shooting of MSAN V1.1 V1.1 2 Course Outline Course Outline Classification of narrow/broad band service faults Specific Fault Analysis Example of Trouble Shooting 3 Fault Classification Fault Classification 1. Hardware Fault 2. Improper Configuration 3. Version Fault 4 Narrowband service fault Analysis Narrowband service fault Analysis 1. user terminal 2. Subscriber Line (External Line) 3. U300 +T600 4. LE 5. transmission system: S200 5 Narrowband service fault Analysis Approach Narrowband service fault Analysis Approach 1. Change Cards + Self Loop Test 2. 112 Test 3. V5 Signaling Tracing 6 U/T Specific Fault Analysis U/T Specific Fault Analysis Fault Classification Fault Symptom Reasons of System Faults Communication interruption between foreground and background The NM displays: The NE link is interrupted, the query of the NE fails, and the maintenance operation. The network card fault, ICS communication setting error, inconsistency between software version and hardware version Active/standby switchover failure The ICS active/standby switchover fails, the service is abnormal after switchover, and the board running is abnormal. Inconsistency between software version and hardware version, and standby board fault NE Data synchronization failure The synchronization NE data times out or is wrong Inconsistency between software version and hardware version 7 U/T Specific Fault Analysis U/T Specific Fault Analysis Fault Classification Fault Symptom Reasons of V5 Protocol Faults V5 interface interruption DT indicator indication on the ICS board is wrong, the V5 interface interruption alarm on the NM, V5 interface L2 protocol alarm, V5 interface protocol is not established, all V5 subscribers cannot perform incoming/outgoing calls. Hardware fault, line fault, V5 interface data configuration problem, access network clock problem, grounding problem, and cooperation problem with the exchange V5 standby link establishment failure V5 interface alarm on the NM, the northern link is not established, and V5 interface switching origination failure Hardware fault, line fault, V5 interface data configuration problem, and cooperation problem with the exchange V5 partial protocol establishment failure The V5 protocol partial link layer is interrupted, and partial protocol cannot be established. Hardware fault, line fault, cooperation problem with the exchange, and grounding problem V5 interface protection protocol abnormality When the V5 interface is normal, the link switchover originated from the access side fails, and the signaling link cannot be switched automatically when the active link is faulty. V5 interface data configuration problem, and cooperation problem with the exchange 2M link abnormality 2M link fault Hardware or line fault, incorrect connection, and different configuration from the exchange 8 S200 Specific Fault Analysis S200 Specific Fault Analysis Fault Classification Description of Fault Inconsistency between board configuration and actual NE configuration on terminal Command timeoutreturned when commands are sent on the NMS Communication failure between the NMS and NE Alarm box fault Failure of NMS to receive the performance data of NEs Failure of boards to be installed on the NMS Failure to create logical subnet, with no timeslot available prompted Failure of the NMS to receive alarms NMS Faults 9 Fault Classification Description of Fault Optical interface alarm occurred when optical fiber connection is normal Loss of NE NE board restarting without reason Two-fiber unidirectional path protection failed Two-fiber unidirectional multiplexing section protection failed Board failed with the RUN indicator solid ON (Yellow) NVM Disk Fault Power-on failure of E1C or ES NE board power-on failure when power input is normal Ethernet interface indicator is OFF and link failed to receive or send packets STP on ES failed Incessant switchover of NE between clock sources NE failed to lock the expected clock source Traffic configuration failure Excessive transmission bit errors NE Faults S200 Specific Fault Analysis S200 Specific Fault Analysis 10 Broadband service fault Analysis Broadband service fault Analysis 1. User (Modem +Computer) 2. Subscriber Line 3. U300 (RT +COT) 4. S200 5. Uplink Device ( Switches + BAS) 11 Broadband service Common fault Broadband service Common fault 1. Vlan Configuration 2. PVC Configuration 3. FE Port Attribute Configuration 4. User End Configuration 12 ADSL User End Common Structure ADSL User End Common Structure 13 Specific Faults Analysis Specific Faults Analysis 1. Unable to Make Calls or Connect the Internet: 1) Usually this fault lies in the line in most cases; 2) Then check if the user-end splitter tap (to the phone set) and the corresponding splitter board of this subscriber are normal 14 Specific Faults Analysis Specific Faults Analysis 2. Call Can be Made but Internet Access Failed: 1) Record the subscribers MODEM model and indicator status; 2) J udge the fault according to the indicator status 3) Then the fault maybe stay with the user-end device, use method or uplink port 15 Specific Fault Analysis Specific Fault Analysis 3. Internet Access Allowed but at a Low Speed 1) If a large number of subscribers suffer a low Internet access speed; 2) If only several subscribers suffer a low Internet access speed: Check the line quality, and check the line bit error ratio 16 Specific Fault Analysis Specific Fault Analysis 4. Unstable Internet Access and Frequent Offline Usually, it is caused by the over-big high frequency attenuation from the poor line quality, overlong line, too-big line noise or poor line contact 1) First judge if the line exceeds 3 km; 2) Check if the splitter is installed properly 3) Check if each connector of the lead-in line is connected reliably 17 Example Of Practical Fault Example Of Practical Fault 1. Noise During Conversion in Big Area 18 Example Of Practical Fault Example Of Practical Fault 2. Remote E1 Alarm TAB ESQGE E1 E 1 Fiber RT S200 Q S200/U300 PST N P O W E R K P O W E R K A T I D L C C T R K T R K T R K T R K I C S I C S 19 Example Of Practical Fault Example Of Practical Fault 3. ADSL Subscribers Failed to View Web 20 Example Of Practical Fault Example Of Practical Fault 4. Slow broadband Access during Evening