zte manual msan

Upload: honestcheater

Post on 17-Oct-2015

909 views

Category:

Documents


84 download

DESCRIPTION

instruction manual

TRANSCRIPT

  • A10&DSL D&T GroupA10&DSL D&T Group

    AM_TS01_E2_P1AM_TS01_E2_P1

    Trouble shooting of MSANTrouble shooting of MSANV1.1V1.1

  • 2Course OutlineCourse Outline

    Classification of narrow/broad band

    service faults

    Specific Fault Analysis

    Example of Trouble Shooting

  • 3Fault ClassificationFault Classification

    1. Hardware Fault

    2. Improper Configuration

    3. Version Fault

  • 4Narrowband service fault AnalysisNarrowband service fault Analysis1. user terminal

    2. Subscriber Line (External Line)

    3. U300 +T600

    4. LE

    5. transmission system: S200

  • 5Narrowband service fault Analysis ApproachNarrowband service fault Analysis Approach

    1. Change Cards + Self Loop Test

    2. 112 Test

    3. V5 Signaling Tracing

  • 6U/T Specific Fault AnalysisU/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

  • 7U/T Specific Fault AnalysisU/T Specific Fault AnalysisFault

    Classification Fault Symptom Reasons of V5 Protocol Faults

    V5 interfaceinterruption

    DT indicator indication on the ICS board is wrong,the V5 interface interruption alarm on the NM, V5interface L2 protocol alarm, V5 interface protocolis not established, all V5 subscribers cannotperform incoming/outgoing calls.

    Hardware fault, line fault, V5 interfacedata configuration problem, accessnetwork clock problem, groundingproblem, and cooperation problemwith the exchange

    V5 standby linkestablishment failure

    V5 interface alarm on the NM, the northern link isnot established, and V5 interface switchingorigination failure

    Hardware fault, line fault, V5 interfacedata configuration problem, andcooperation problem with the exchange

    V5 partial protocolestablishment failure

    The V5 protocol partial link layer is interrupted,and partial protocol cannot be established.

    Hardware fault, line fault, cooperationproblem with the exchange, andgrounding problem

    V5 interfaceprotection protocolabnormality

    When the V5 interface is normal, the linkswitchover originated from the access side fails,and the signaling link cannot be switchedautomatically when the active link is faulty.

    V5 interface data configurationproblem, and cooperation problemwith the exchange

    2M link abnormality 2M link fault Hardware or line fault, incorrectconnection, and different configurationfrom the exchange

  • 8S200 Specific Fault AnalysisS200 Specific Fault Analysis

    Fault Classification Description of Fault

    Inconsistency between board configuration and actual NE configuration on terminal

    Command timeout returned 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

  • 9Fault Classification Description of FaultOptical 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 AnalysisS200 Specific Fault Analysis

  • 10

    Broadband service fault AnalysisBroadband service fault Analysis1. User (Modem +Computer)

    2. Subscriber Line

    3. U300 (RT +COT)

    4. S200

    5. Uplink Device ( Switches + BAS)

  • 11

    Broadband service Common faultBroadband service Common fault1. Vlan Configuration

    2. PVC Configuration

    3. FE Port Attribute Configuration

    4. User End Configuration

  • 12

    ADSL User End Common StructureADSL User End Common Structure

  • 13

    Specific Faults AnalysisSpecific 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 AnalysisSpecific Faults Analysis

    2. Call Can be Made but Internet Access Failed:

    1) Record the subscribers MODEM model and indicator status;

    2) Judge 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 AnalysisSpecific 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 AnalysisSpecific Fault Analysis4. 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 FaultExample Of Practical Fault1. Noise During Conversion in Big Area

  • 18

    Example Of Practical FaultExample Of Practical Fault2. Remote E1 Alarm

    TAB

    ESQGE

    E1

    E1

    Fiber

    RT

    S200

    Q

    S200/U300

    PSTN

    POWERK

    POWERK

    ATI

    DLCC

    TRK

    TRK

    TRK

    TRK

    ICS

    ICS

  • 19

    Example Of Practical FaultExample Of Practical Fault3. ADSL Subscribers Failed to View Web

  • 20

    Example Of Practical FaultExample Of Practical Fault4. Slow broadband Access during Evening

    Ip Network

    HW3500

    COT S200 T600

    RT 2 U300

    RT 1 U300

    NMS

  • 21

    Thanks

    Thanks