O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.

Mw training slide

12.305 visualizações

Publicada em

Publicada em: Negócios, Tecnologia
  • Seja o primeiro a comentar

Mw training slide

  1. 1. Internal OptiX RTN 600 Troubleshooting www.huawei.com H UAW I T CH E E NOL OGIE CO., L D. S T All rights reserved
  2. 2. Objectives  Upon completion of this course, you will be able to:  List the common analysis methods of fault locating  Outline the Fault Handling Flow  Analyze the typical faults: traffic interruption, error bit, etc H UAW I T CH E E NOL OGIE CO., L D. S T All rights reserved P age 2
  3. 3. Content 1. Troubleshooting Preparation 2. Troubleshooting Idea and Methods 3. Classified Troubleshooting Examples H UAW I T CH E E NOL OGIE CO., L D. S T All rights reserved P age 3
  4. 4. Requirements for Maintenance Personnel  Be familiar with hardware system and Digital Microwave Communication principle, particularly in the alarm signal flow  Alarm/performance generation principle  Master the basic operations of the transmission equipment  NMS, testing devices, loopback, board replacement H UAW I T CH E E NOL OGIE CO., L D. S T All rights reserved P age 4
  5. 5. Requirements for Maintenance Personnel  Familiar with the network under maintenance  Network topology, network protection, traffic configuration  Collect and save on-site data  System alarms, performance events data, configurations, operation records of NMS H UAW I T CH E E NOL OGIE CO., L D. S T All rights reserved P age 5
  6. 6. Flow Chart Start On site or not NO YES Hardware problems? NO H UAW I T CH E E NOL OGIE CO., L D. S T YES If the fault does not affect the network element access, query the alarm and follow the “maintenance manual” ; If problems cannot be solved through the above methods or remote access is not permitted., please deal with the problems on site. water flowing or fire? If all indicators off, check the PXC board power input; And then check the SCC board indicators status. All rights reserved P age 6
  7. 7. Flow Chart Query alarms NO YES Please replace the corresponding board if report the alarm below: A_LOC, DBMS_PROTECT_MODE, HARD_BAD, POW ER_ALM, POW ER_FAIL, RADIO_TSL_HIGH, RADIO_TSL_LOW , RP_LOC, T_F_RST , T_FIFO_E, R_F_RST. Follow the “maintenance manual” to handle the alarms below : APS_MANU_STOP, ALM_RTC_FAIL, APS_FAIL, BD_NOT_INSTALLED, R_LOS,R _LOF,CONFIG_NOSUPPORT,R ADIO_MUTE,RADIO_RSL_LOW ,MW _LO F,MW _LIM Transfer to SDH process H UAW I T CH E E NOL OGIE CO., L D. S T All rights reserved P age 7
  8. 8. Content 1. Troubleshooting Preparation 2. Troubleshooting Idea and Methods 3. Classified Troubleshooting Examples H UAW I T CH E E NOL OGIE CO., L D. S T All rights reserved P age 8
  9. 9. One question  What is the key for troubleshooting ?  To locate a failure ACCURATELY in one station H UAW I T CH E E NOL OGIE CO., L D. S T All rights reserved P age 9
  10. 10. Basic Principles for Locating Faults  External first, then internal Exclude external problems first − IF cable, switch failure − Power failure, grounding  Station first, then boards Try your best to locate the troubles to one node H UAW I T CH E E NOL OGIE CO., L D. S T All rights reserved P age 10
  11. 11. Basic Principles for Locating Faults  Microwave side first, then SDH side  First check the Microwave side problems  Higher-severity alarms first, then Lower-severity alarms  First analyze critical/major alarms  Then come to minor/warning alarms H UAW I T CH E E NOL OGIE CO., L D. S T All rights reserved P age 11
  12. 12. Common Methods of Fault Locating  Alarm and performance analysis  Loopback  Replacement  Configuration data analysis  Configuration modification  Test with instruments  Rule of thumb H UAW I T CH E E NOL OGIE CO., L D. S T All rights reserved P age 12
  13. 13. Alarm and Performance Analysis  Us e N S M How to obtain alarms and performance? •Comprehensive •All alarms/performance events from the whole network •Accurate • Current alarms, history alarms, occurrence time and performance event data can be queried. H UAW I T CH E E NOL OGIE CO., L D. S T  O bs e rve ind ic a to rs o n bo a rd s a nd c a bine ts •Not detailed •No history alarms All rights reserved P age 13
  14. 14. Alarm and Performance Analysis Obtain alarm and Select the key alarm or performance events performance events Analyze reasons Limit the troubles to a certain range or a node H UAW I T CH E E NOL OGIE CO., L D. S T All rights reserved P age 14
  15. 15. Alarm and Performance Analysis 1 2 R-LOF 3 MW-RDI HSB-INDI  Description NE1 & NE2 is  STM-1 capacity 1+1 configuration; After switching, that was an alarm “R_LOF" on NE1; Alarm "MW_RDI", “HSB_INDI” on NE2. H UAW I T CH E E NOL OGIE CO., L D. S T All rights reserved P age 15
  16. 16. Alarm and Performance Analysis  Possible reasons: Second ODU is faulty; IF-board is faulty; TX/RX Frequencies of the second (protection) ODU are  different from the other three ODUs on this hop; Hybrid Coupler is faulty; There is water in hybrid coupler; IF-Jumper is faulty; IF-board is faulty. H UAW I T CH E E NOL OGIE CO., L D. S T All rights reserved P age 16
  17. 17. Loopback What is loopback? Loopback is the most common, most efficient method in troubleshooting. Inloop Inloop RTN equipment Line Line outloop outloop Inloop outloop Tributary H UAW I T CH E E NOL OGIE CO., L D. S T All rights reserved P age 17
  18. 18. Loopback Board involved Tributary board Line board Loopback options Inloop/ outloop Inloop/ outloop Loopback tools Loopback level Application Loopback cable, NMS Loopback at path level Separate switching faults from transmission faults. Determine the tributary board failure roughly. Be unnecessary to modify service configuration. Patch fiber, NMS Loopback by optical interface Locate single station faults. Roughly determines the line board failure. Be no need to modify service configuration Loopback by the IF/RF port the ODU supports RF port inloops and IF port inloops/outloops, separate the faults in the IFunits or the ODU Inloop/ IF/RF port Notes outloop NMS May interrupt the traffic and ECC Software loopback is not a thorough method Will automatically be removed in 5 minutes (provisionable) H UAW I T CH E E NOL OGIE CO., L D. S T All rights reserved P age 18
  19. 19. Loopback  Procedures  Draw the traffic flow diagram  Loopback section after section to locate the faulty NE  Locate the faults to certain boards H UAW I T CH E E NOL OGIE CO., L D. S T All rights reserved P age 19
  20. 20. Replacement Objective Application Fiber External faults Cable Boards faults Module Board Effective thoughts MSP switch SNCP switch 1+1 SD/FD switch 1+1 HSB switch H UAW I T CH E E NOL OGIE CO., L D. S T All rights reserved P age 20
  21. 21. Configuration Data Analysis  Query & Analyze the configuration  Timeslot configuration  J1 or C2 bytes  LU 、 TU 、 IF unit or ODU loopback  SNCP or MSP switching conditions (e.g. MS-SD)  External commands (e.g. locked switch)  The consistency of the frequency between two nodes  The appropriate transmission power of the ODU H UAW I T CH E E NOL OGIE CO., L D. S T All rights reserved P age 21
  22. 22. Configuration Modification Objective Application Examples Port No spare boards Timeslot Restore the traffic Slot temporarily H UAW I T CH E E NOL OGIE CO., L D. S T All rights reserved P age 22
  23. 23. Testing Instrument Instrument Test item Bit error testing device Bit error/traffic Optical power meter Optical power SDH analyzer Bit error/traffic/overhead bytes …… Multi-meter Voltage/current/resistance This method is the most authoritative, but we must have the devices in hand. H UAW I T CH E E NOL OGIE CO., L D. S T All rights reserved P age 23
  24. 24. Rule of Thumb Last resort  Reset board  Power off and on  Resend the configuration  Do not consider them as a panacea  They are not helpful for us to find the cause of the failure. H UAW I T CH E E NOL OGIE CO., L D. S T All rights reserved P age 24
  25. 25. Common Methods of Fault Locating Methods Application Features 1. Evaluate the whole network situation. 2. Locate the faulty point preliminarily based on the collected data. 3. Cause no negative effect on normal services 4. Depend on the NMS Alarm and performance analysis Universal Loopback Locate the fault to a single station or board Replacement Locate the fault to a board or isolate external faults Configuration data analysis Locate the fault to a single station or board 1. Can find the fault cause. 2. Fault locating time is longer. 3. Depend on the NMS Configuration modification Locate the fault to a board 1. Have a high risk. 2. Depend on the NMS Test with instruments Isolate external faults and resolve interconnectivity problem 1. A general method with high accuracy 2. Have certain requirements for the meters. 3. Applied with other methods Experience Special cases H UAW I T CH E E NOL OGIE CO., L D. S T 1. Independent of alarm and performance event analysis 2. Rapid and effective 1. Convenient 2. Require spare parts/equipment. 3. Applied with other methods 1. Fast fault handling 2. High probability of mistake 3. Need experience accumulation. All rights reserved P age 25
  26. 26. Common Troubleshooting Sequence Exclude external troubles Switching problem? Fiber problems? Trunk cable? Power supply system? Grounding problem? Replacement Instrument testing Loopback Alarm/performan ce analysis Locate troubles to one NE Loopback Alarm/performance analysis Locate the troubles to one board H UAW I T CH E E NOL OGIE CO., L D. S T All rights reserved Replacement Loopback Alarm/performance analysis Configuration analysis Configuration modification Rule of Thumb P age 26
  27. 27. Contents 1. Troubleshooting Preparation 2. Troubleshooting Idea and Methods 3. Classified Troubleshooting Examples H UAW I T CH E E NOL OGIE CO., L D. S T All rights reserved P age 27
  28. 28. Classified Troubleshooting Examples  Traffic Interruption  Wrong configuration  Bit Errors H UAW I T CH E E NOL OGIE CO., L D. S T All rights reserved P age 28
  29. 29. Traffic Interruption 2 1 16 E1 16 E1  Description  Hardware version is V1R2, can not configure 16E1 services ( just can configure 11E1 services);  There are no other services;  The link between NE1 & NE2 was configured 1+1HSB; H UAW I T CH E E NOL OGIE CO., L D. S T All rights reserved P age 29
  30. 30. Traffic Interruption  Handling process Check the license License just can support 23 E1( 7 E1 for free) and the 1+1 HSB need the 32 E1 license capacity Change the license Delete the 1+1 HSB configuration Generate the some alarms H UAW I T CH E E NOL OGIE CO., L D. S T All rights reserved P age 30
  31. 31. Traffic Interruption  Handling process 1 2 LOG_OUT MW-LOF 16 E1 16 E1 Other configurations YES be changed ? NO Check the configuration for 1+1HSB H UAW I T CH E E NOL OGIE CO., L D. S T All rights reserved Check the ODU launch frequency or the receiving power Use other configuration guides P age 31
  32. 32. Traffic Interruption  Handling process W rong operation process to delete the 1+1 HSB Analysis: configure the 1+1HSB, both ODUs are set unmute status; After delete the protection configuration, both ODUs will be disturbed each other because they have same launch frequency and polarization ; Shut down the ODU and configure the 1+1 HSB again H UAW I T CH E E NOL OGIE CO., L D. S T All rights reserved P age 32
  33. 33. Classified Troubleshooting Examples  Traffic Interruption W rong configuration  Bit Errors H UAW I T CH E E NOL OGIE CO., L D. S T All rights reserved P age 33
  34. 34. Wrong configuration 2 1 Config_nosupport   16 E1 16 E1  Description  NE1 configure 1+0 protection, at the 15 GHz band, and with 16E1 PDH;  NE1 ODU remains mute though it is set to the unmute status;  NE1 ODU transmits signals at the power of -55 dBm though its launched power is set to 21 dBm;  NE1 generates the Config_nosupport alarm.  H UAW I T CH E E NOL OGIE CO., L D. S T All rights reserved P age 34
  35. 35. Wrong configuration  Handling process The launched power of ODU is out of the range? The range is -6 to 24dbm, and the launched power is 21 dbm; The transmit frequency of ODU is out of the range? The range is 15GHZ band, and the actual frequency is 1.46655 GHZ The designed frequency is 14.6655 GHZ; so change the transmit frequency to 14.6655 GHZ H UAW I T CH E E NOL OGIE CO., L D. S T All rights reserved P age 35
  36. 36. Classified Troubleshooting Examples  Traffic Interruption W rong configuration  Bit Errors H UAW I T CH E E NOL OGIE CO., L D. S T All rights reserved P age 36
  37. 37. Bit Errors 2 1 MW_RDI MW_LOF   Description  Many bit errors generate in the microwave equipment for the interval is between 15 to 25 minutes;  The services are interrupted for 5 to 8 seconds each time;  The equipment generate MW_RDI and MW_LOF alarms; H UAW I T CH E E NOL OGIE CO., L D. S T All rights reserved P age 37
  38. 38. Bit Errors  Handling process W rong configuration? Yes No Hardware problems? Inconsistent working modes or working frequencies of the ODUs at the local and peer ends? No No Query the alarms MW _RDI: W hen this alarm is reported, it means that the link is faulty and consequently the peer end receives error bits. H UAW I T CH E E NOL OGIE CO., L D. S T MW _LOF: The performance of the microwave link deteriorates. The receive function of the local end fails. The working modes of the ODUs in the local and peer ends are different. The working efficiency of the ODUs in the local and peer ends are different.  All rights reserved P age 38
  39. 39. Bit Errors  Handling process The MW _RDI and MW _LOF alarms are related to the link performance deterioration a new link is created and the frequency interference occurs between the new and existing links After modify the receive and transmit  powers of the ODUs at the local and  peer ends, the problem is solved. H UAW I T CH E E NOL OGIE CO., L D. S T All rights reserved Guess: other company creates a new microwave hop and the new microwave hop shares the site with Huawei. P age 39
  40. 40. Questions  What is the key of troubleshooting?  To locate a failure ACCURATELY in certain station  What is the principle of troubleshooting?  External first, then internal  Station first, then boards  Microwave first, then SDH  Higher-severity alarms first, then lower-severity alarms H UAW I T CH E E NOL OGIE CO., L D. S T All rights reserved P age 40
  41. 41. Summary  Which methods for troubleshooting?        Alarm and performance analysis Loopback Replacement Configuration Data Analysis Configuration Modification Test with instruments Rule of Thumb H UAW I T CH E E NOL OGIE CO., L D. S T All rights reserved P age 41
  42. 42. Thank You www.huawei.com

×