Zte ZXR10 Handling Manual

Zte ZXR10 Handling Manual

Router/ethernet switch alarm handling manual
Hide thumbs Also See for ZXR10:

Advertisement

ZXR10
Router/Ethernet Switch
Alarm Handling Manual
Version 4.8.23
ZTE CORPORATION
ZTE Plaza, Keji Road South,
Hi-Tech Industrial Park,
Nanshan District, Shenzhen,
P. R. China
518057
Tel: (86) 755 26771900
Fax: (86) 755 26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the ZXR10 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Summary of Contents for Zte ZXR10

  • Page 1 ZXR10 Router/Ethernet Switch Alarm Handling Manual Version 4.8.23 ZTE CORPORATION ZTE Plaza, Keji Road South, Hi-Tech Industrial Park, Nanshan District, Shenzhen, P. R. China 518057 Tel: (86) 755 26771900 Fax: (86) 755 26770801 URL: http://ensupport.zte.com.cn E-mail: support@zte.com.cn...
  • Page 2 The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution of this document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPO- RATION is prohibited.
  • Page 3: Table Of Contents

    Contents About This Manual..........i Alarm Overview..........1 Overview............... 1 Alarm Glossry Overview ..........1 Message No............... 1 Default Severity Level ..........2 Alarm Recovery ............2 Alarm Type ..............2 NM Level ..............3 Cause ............... 3 Related Alarms............4 Recommended Operations ...........
  • Page 4 80..............20 Board Alarms ............22 279..............22 293..............22 299..............22 300..............23 301..............24 302..............24 303..............25 310..............26 311..............26 312..............27 313..............28 Port Alarm ..............29 512..............29 540..............29 541..............29 542..............29 Software Alarm .............30 ETHOAM Alarm............30 16128 .............30 16129 .............31 16130 .............31 16131 .............32 30464 .............34 30465 .............35 30466 .............36 30467 .............37 ROS Alarm..............38 16384 .............38...
  • Page 5 16642 .............42 16643 .............43 16644 .............43 16645 .............43 16646 .............43 OAM Alarm ...............44 16899 .............44 16900 .............44 16901 .............45 16903 .............46 16904 .............46 16905 .............46 16906 .............46 16907 .............46 16916 .............47 16917 .............47 16918 .............47 16919 .............48 16920 .............48 16921 .............49 16922 .............49 16923 .............49 16924 .............50...
  • Page 6 17422 .............55 17423 .............55 17424 .............55 17425 .............56 17426 .............56 17427 .............56 17428 .............56 17429 .............56 RIP Alarm ..............57 17664 .............57 17666 .............57 17667 .............57 17670 .............57 17671 .............58 17672 .............58 17673 .............58 17676 .............58 17677 .............59 BGP Alarm ..............59 17920 .............59 17921 .............59 17922 .............59...
  • Page 7 17950 .............63 17951 .............63 17952 .............64 17953 .............64 17954 .............64 17955 .............64 17956 .............64 17957 .............65 17958 .............65 17959 .............65 17960 .............65 17961 .............65 17962 .............66 17963 .............66 17964 .............66 DRP Alarm ..............66 18176 .............66 18177 .............66 18180 .............67 18181 .............67 18182 .............67 18183 .............67 18184 .............68...
  • Page 8 18440 .............72 18450 .............72 18451 .............72 18452 .............73 18453 .............73 18455 .............73 18456 .............73 18457 .............73 18458 .............74 18459 .............74 18460 .............74 18461 .............74 18463 .............74 18464 .............75 UDP Alarm..............75 18560 .............75 18561 .............75 18562 .............75 18563 .............75 18564 .............76 IP Alarm..............76 18689 .............76 18691 .............76...
  • Page 9 18786 .............80 18787 .............80 18790 .............80 18791 .............80 18794 .............81 18832 .............81 18833 .............82 18834 .............82 18835 .............83 IGMP Alarm ..............83 18944 .............83 18945 .............84 ARP Alarm ..............84 19712 .............84 19713 .............84 19714 .............84 19715 .............85 19716 .............85 19717 .............85 19720 .............85 IS-IS Alarm .............86 19968 .............86...
  • Page 10 20757 .............91 20758 .............91 20759 .............91 20776 .............91 20793 .............91 URPF Alarm ..............92 21248 .............92 ACL Alarm ..............92 21762 .............92 21764 .............92 21773 .............92 21774 .............93 21775 .............93 21776 .............93 21777 .............94 VRRP Alarm ..............95 22016 .............95 MAC Alarm ...............95 22784 .............95 22785 .............95 22786 .............95...
  • Page 11 23813 ............103 23814 ............103 23815 ............104 23816 ............104 23817 ............105 23818 ............105 23819 ............106 23820 ............106 23821 ............107 23822 ............107 23823 ............108 23824 ............108 MLD Alarm ............. 109 24064 ............
  • Page 12 26368 ............115 26369 ............115 26370 ............116 26371 ............116 26372 ............116 26373 ............116 26374 ............116 26375 ............117 26376 ............117 TACACS Alarms ............117 28160 ............117 28161 ............117 28162 ............118 28163 ............
  • Page 13 30210 ............126 30212 ............127 30213 ............127 UDLD Alarm............128 29696 ............128 29697 ............128 29698 ............129 29699 ............129 MUX Alarm ............. 130 29440 ............130 ZESS Alarm ............130 32512 ............130 32513 ............131 32514 ............
  • Page 14 Message Format ............147 Error Message Description ..........147 10 ................. 147 11 ................. 147 12 ................. 147 13 ................. 148 14 ................. 148 15 ................. 148 16 ................. 148 17 ................. 148 18 ................. 149 19 ................. 149 20 ................. 149 21 .................
  • Page 15 105 ............... 154 106 ............... 155 107 ............... 155 108 ............... 155 109 ............... 155 110 ............... 155 112 ............... 155 201 ............... 156 202 ............... 156 203 ............... 156 204 ............... 156 206 ............... 156 207 ............... 157 208 ............... 157 209 ...............
  • Page 16 236 ............... 162 237 ............... 162 238 ............... 162 239 ............... 162 240 ............... 163 241 ............... 163 242 ............... 163 243 ............... 163 244 ............... 163 245 ............... 164 246 ............... 164 247 ............... 164 248 ............... 164 250 ............... 164 251 ...............
  • Page 17 277 ............... 169 278 ............... 169 279 ............... 170 280 ............... 170 284 ............... 170 285 ............... 170 288 ............... 170 289 ............... 171 290 ............... 171 292 ............... 171 300 ............... 171 303 ............... 171 305 ............... 172 306 ............... 172 307 ...............
  • Page 18 1025..............177 1026..............177 1027..............177 1028..............177 1029..............177 1030..............178 1031..............178 1032..............178 1033..............178 1034..............178 1035..............179 1036..............179 1037..............179 1038..............179 1039..............179 1040..............179 1041..............180 1042..............180 1043..............180 1044..............180 1049..............
  • Page 19 1074..............184 1080..............184 1081..............184 1082..............185 1083..............185 1500..............185 1501..............185 1502..............185 1503..............185 1504..............186 1505..............186 1700..............186 2001..............186 2002..............186 2003..............187 2004..............187 2005..............187 2006..............187 2007..............187 2008..............188 2009..............
  • Page 20 2029..............191 2030..............191 2031..............192 2032..............192 2033..............192 2034..............192 2035..............192 2036..............193 2037..............193 2038..............193 2039..............193 2040..............193 2041..............194 2042..............194 2043..............194 2044..............194 2045..............194 2046..............194 2047..............195 2048..............195 2049..............
  • Page 21 2808..............199 2809..............199 2810..............199 2811..............199 2812..............199 2813..............199 2814..............200 2815..............200 3001..............200 3002..............200 3003..............200 3004..............201 3005..............201 3006..............201 3007..............201 3008..............201 3009..............201 3010..............202 3011..............202 3012..............202 3013..............
  • Page 22 4015..............206 4016..............206 4030..............206 4031..............206 4032..............206 4033..............207 4034..............207 4035..............207 4036..............207 4037..............207 4038..............207 4039..............208 4040..............208 4041..............208 4042..............208 4043..............208 4044..............209 4045..............209 4046..............209 4047..............209 4048..............
  • Page 23 5007..............213 6001..............213 6010..............213 6011..............214 6012..............214 6020..............214 6021..............214 6022..............214 6023..............215 6024..............215 6025..............215 6026..............215 6027..............215 6028..............215 6029..............216 6030..............216 6031..............216 6032..............216 6033..............216 6034..............216 6035..............
  • Page 24 6085..............220 6086..............220 6087..............221 6088..............221 6089..............221 6601..............221 7001..............221 7002..............221 7003..............222 7004..............222 7005..............222 7006..............222 7007..............222 7008..............222 7010..............223 7011..............223 7012..............223 7020..............223 7021..............223 7022..............223 7023..............
  • Page 25 7069..............227 7071..............227 7081..............227 7082..............227 7083..............228 7091..............228 8008..............228 8009..............228 8010..............228 8011..............228 8501..............229 8502..............229 8503..............229 8504..............229 8505..............229 8506..............229 8509..............230 8510..............230 8511..............230 8512..............230 8513..............
  • Page 26 8616..............234 8617..............234 8618..............234 8619..............234 8620..............235 8621..............235 8622..............235 8623..............235 8624..............235 8625..............236 8626..............236 8701..............236 8702..............236 8703..............236 8704..............236 8705..............237 8706..............237 8707..............237 8708..............237 8801..............237 8802..............
  • Page 27 8917..............241 8918..............241 8919..............241 8951..............242 8952..............242 8953..............242 8954..............242 8955..............242 8956..............243 9001..............243 9002..............243 9003..............243 9004..............243 9005..............243 9101..............244 9102..............244 9103..............244 9105..............244 9106..............244 9201..............244 9202..............
  • Page 28 9521..............248 9522..............249 9523..............249 9601..............249 9602..............249 9603..............249 9604..............250 9605..............250 9606..............250 9607..............250 12401 ..............250 12402 ..............250 12403 ..............251 12404 ..............251 12405 ..............251 12406 ..............251 12407 ..............251 12409 ..............
  • Page 29 30207 ..............256 30208 ..............256 TRAP Messages ..........257 TRAP Message Explanation..........257 System TRAP Message ..........257 coldStart ..............257 warmStart .............. 258 authenticationFailure..........258 linkUp ..............258 linkDown ..............259 Alarm TRAP Message............ 259 Hardware Alarm Trap ..........259 Software Alarm Trap ..........
  • Page 30 vrrpTrapAuthFailure ..........273 vrrpTrapNewMaster..........273 IPv6TRAP Information ..........274 ipv6IfStateChange ........... 274 POE TRAP Information..........274 pethPsePortOnOffNotification........274 pethMainPowerUsageOnNotification......275 pethMainPowerUsageOffNotification ......275...
  • Page 31: About This Manual

    8900) The manual content is based on unified ZXROS platform and suited to all equipments if with no special note or described as ZXR10. In the manual, the contents describing router are also applied to the switches with route function.
  • Page 32 ZXR10 Alarm Handling Manual This page is intentionally blank. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 33: Alarm Overview

    The back- ground alarm code is used to display in alarm monitoring platform and is mapping with the foreground alarm code one by one ac- cording to some rules. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 34: Default Severity Level

    ZXR10 Alarm Handling Manual Default Severity Level ZXR10 devices alarm level includes the following 8 levels: � Severity 1: emergency messages EMERGENCIES, the system is unusable. � Severity 2: alert messages ALERTS. Magnitude malfunction appears in the system and immediate action is needed.
  • Page 35: Nm Level

    Various kinds of causes are as follows. In order to recover the system as soon as possible, we should find out trigger conditions, trigger frequency, the resolutions and the prevent measures. The causes for ZXR10 alarm messages are as follows: 1. The hardware or device malfunction. i. Single board malfunction.
  • Page 36: Related Alarms

    And then check and inform the other end whether this alarm is removed. 3. For alarms that can not be resolved by users, contact with ZXR10 router professors of ZTE corporation or call our cus- Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 37: Alarm Prototype Description

    Message Format Description The alarm message format is as follows. <time> alarm <number>{occurred | cleared}<type><descrip tion> sent by <sender> Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 38 Alarm messages in the "cleared" status are merely system recov- ery messages, which need no operation. ZXR10 alarm messages have 2 types, hardware alarm and soft- ware alarm. Of which, the 2 types may be divided further into more sub-types.
  • Page 39 Port Up on fei_5/6 sent by SMP 1 2. Software alarm BGP alarm � 58 09/15/2003 UTC alarm 17959 occurred. %BGP% 2d18h: BGP: 100.1.1.1 went from Idle to Connect sent by SMP 1 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 40 ZXR10 Alarm Handling Manual This page is intentionally blank. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 41: Alarm Message

    %s Panel %d Current local temperature is %d℃/%dF,exceeds the low threshold(%d℃/%dF) The first %s is the board type, the first %d is the panel number of the board; the second %d is the centigrade temperature of the Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 42 Decrease board temperature if necessary. Decrease the environ- Operations ment temperature of the equipment by the fan heat dissipation. Alarm Prototype Alarm Occurred Description %s Panel %d Current local temperature is %d℃/%dF,exceeds the first high threshold(%d℃/%dF) Alarm Cleared Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 43 Related Alarms 63, 64 Recommended Decrease board temperature if necessary. Decrease the environ- Operations ment temperature of the equipment by the fan heat dissipation. Stop using the board if the temperature is too high. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 44 The command used to set threshold for memory utilization is (un- der environmental configuration mode): memory-threshold. Recommended Use the command show process to view the CPU utilization and Operations analyzse whether it is normal or not. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 45 Increase the environment temperature of the equipment if neces- Operations sary. Alarm Prototype Alarm Occurred Description %s Panel %d Current remote temperature is %d℃/%dF,under the low threshold(%d℃/%dF) Alarm Cleared %s Panel %d Current remote temperature is %d℃/%dF,exceeds the low threshold(%d℃/%dF) Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 46 Decrease the board temperature if necessary. Decrease the envi- Operations ronment temperature of the equipment by the fan heat dissipation. Alarm Prototype Alarm Occurred Description %s Panel %d Current remote temperature is %d℃/%dF,exceeds the first high threshold(%d℃/%dF) Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 47 The remote temperature is higher than the set remote second-high threshold of the board. The command used to set threshold for equipment temperature: temper-threshold UPC master local lowthreshold -20 first-high- threshold 55 second-highthreshold 90. Related Alarms 67, 68 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 48 The remote temperature is higher than the set remote second-high threshold of the board. Supported Devices T128/T64, T600/T1200 N.A. Appendix Specification Message No. Default Severity Level Alarm Recovery Available Alarm Type Environmental Alarm NM Level Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 49 16:22:11 06/26/2008 UTC alarm 73 cleared %ENVIRONMENT% Current temperature is 80C/176F,under the threshold(90C/194F) Alarm Description The rack temperature is higher than the set single high threshold. Supported Devices ZXR10 3900/3200, 5900/5200 and G-series switch. N.A. Appendix Specification Message No. Default Severity...
  • Page 50 % d: the power serial number. Multiple power states can be dis- played simultaneously. UAS10800E: Current Trunk %s Fan fail to work %s: Top or Bottom Alarm cleared Current Cabinet/Trunk Fan work normal %s: Top or Bottom Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 51 Current Power Module 2 fail to work 15:04:08 08/14/2008 UTC alarm 79 occurred Power er- ror, reason: Current Power Module 2 fail to work sent by UPC(MPU) 1 iii. Current Power Module 3 fail to work Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 52 Current Power work normal sent by UPC(MPU) 1 Alarm Description Power malfunction. Supported Devices ZXR10 T64E, T128, T600, T1200 Appendix ZXR10 T64, T128 adopts old rack; ZXR10 T600, T1200 adopts new Specification rack. Message No. Default Severity Level Alarm Recovery...
  • Page 53 Num. For example, Num 3 5. 14:57:38 08/14/2008 UTC alarm 80 occurred Fan error, reason: Current Cabinet Top Fan Num 3 4 fail to work sent by UPC(MPU) 1 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 54: Board Alarms

    This alarm is used for the location of the malfuction. It has no Operations influence on the operation or the utility. Message No. Default Severity Level Alarm Recovery Available Alarm Type Equipment Alarm NM Level Cause Alarm occurs: Device is removed from 59 stack system. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 55 Related Alarms Recommended 1. Reboot the two boards with abnormal alarm. Operations 2. If reboot operation is invalid, contact with ZTE service staff. 3. ZTE service staff can input printHardwareState in ros and record the result. Alarm Prototype 2 %s is %s,system abnormal.
  • Page 56 Abnormality of NPCT line card will lead to failure of SFC syn- chronization. In case synchronization loss still exists for switch chip on SFC after it resets repeatedly for 30 times, master/slave switchover of SFC will occur and alarm is sent out. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 57 13:31:30 03/25/2008 UTC alarm 303 occurred Pannel:7 NPC mas- ter data eye abnormal. sent by UPC(MPU) 1 Alarm Description The thread application on the single board may suspend due to the abnormal memory read-write. Supported Devices T64E/T128, T1200 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 58 Recommended Plug the interface board or the line card again. If the malfunction Operations still exists, then contact ZTE customer service personnel to check whether the interface board or the line card is abnormal. Alarm Prototype write register failed:baseaddr = 0x%08x ,offset =0x%4x...
  • Page 59 The board link forwarding works normally for the specified time. User configuration interface is up physically. Influence User configuration interface is up/down. Related Alarms Recommended Check whether the board link forwarding is normal; whether the Operations user configures this interface. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 60 NP %d forward link has exception,warning Description %d: board number 15:27:36 08/09/2008 UTC alarm 313 occurred %Board% NP 6 forward link has exception,warning sent by NPC 6 Alarm Description The forwarding link is abnormal. Supported Devices T64E/T128, T600/T1200 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 61: Port Alarm

    The aggregation of port configuration in SMARTGROUP interface is successful. Recommended Operations Message No. Default Severity Level Cause The aggregation of port configuration in SMARTGROUP interface fails. Recommended Operations Message No. Default Severity Level Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 62: Software Alarm

    Local end ethernet oam is in slave mode. 5. loopback has on/off Local end ethernet oam is in on/off mode. 6. loopback respond start command failed Remote respond loopback start fails. 7. loopback respond stop command failed Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 63 Default Security Level Alarm Type "ProcessingErrorAlarm" NM Level Cause The local or remote configuration modification causes that the local or remote can’t satisfy the modified configuration. Influence Cause Ethernet oam protocol status to change. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 64 The first %s details are as follows: 1. Link fault: check link state 2. Dying gasp fault: check device state 3. Critical fault: check device state 4. Error frame event: check received error frames Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 65 %ETHOAM% Interface occur local dying gasp event localmac 00d0.d0c6.5e27 peermac 00d0.d0c0.7d81 on fei_1/1 sent by NPC1 6. 00:16:14 01/01/2001 UTC alarm 16131 occurred %ETHOAM% Interface occur local critical event localmac 00d0.d0c6.5e27 peermac 00d0.d0c0.7d81 on fei_1/1 sent by NPC1 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 66 When alarm disappears, this character string is empty. The second character string content is has received a packet from some remote MEPs with RDI flag! when alarm appears, the alarm is the content which shows above. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 67 SomeRMEPCCMdefect defect disappear! when alarm disappears, the alarm is the content which shows above. Example: 1. 10:38:07 08/10/2009 UTC alarm 30465 occurred %CFM% SomeRMEPCCMdefect,MD 1 MA 1 MEP 2,has not received CCM Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 68 Example: 1. 10:38:07 08/10/2009 UTC alarm 30466 occurred %CFM% MD 1 MA 1 MEP 2, one or more invalid CCMs has been received! Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 69 1. 10:38:07 08/10/2009 UTC alarm 30467 occurred %CFM% MD 1 MA 1 MEP 2, one or more cross connect CCMs has been re- ceived! 2. 10:38:10 08/10/2009 UTC alarm 30467 occurred %CFM% MD 1 MA 1 MEP 2, xconCCMdefect defect disappear! Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 70: Ros Alarm

    Hot starting means that to reboot the device when it is still running. Recommended Operations Alarm Prototype Alarm occurred Description 11:22:27 05/29/2007 UTC alarm 16389 occurred %ROS% SNMP agent on host ZTE is undergoing a cold start sent by MCP 16391 Message No. 16391 Default Severity Level Alarm Recovery...
  • Page 71 Supported Devices CE&PTN 6100 CE&PTN 6100 Appendix CE &PTN version supports this alarm. Specification 16393 Message No. 16393 Default Severity Level Alarm Recovery Unavailable Alarm Type CLASS_NOTIFY NM Level Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 72 Slave is a copy of master. Slave board can substitute for master board. 14:59:17 08/20/2008 green alarm 16394 cleared %ROS% Slave is a copy of master. Slave board can substitute for master board. sent by UPC(MPU) 2. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 73 MEC2 Alarm Description SD is removed. Supported Devices 89 and 69 series routing switch(This alarm can be available from V4.8.22.) 16396 Message No. 16396 Default Security Level Alarm Type "ProcessingErrorAlarm" Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 74: Database Alarm

    The alarm buffer only has 20% space left. Recommended If it does not configure to send alarm messages to external server Operations in ftp or syslog mode, please check if there is any important alarm Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 75 Check the system running status. Restart the standby board if Operations necessary. 16646 Message No. 16646 Default Severity Level Cause The node recursion level is too deep in the program to delete the database. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 76: Alarm Recovery Available

    ZXR10 Alarm Handling Manual Recommended There may be redundant configuration. Please contact ZTE for the Operations solution. OAM Alarm 16899 Message No. 16899 Default Severity Level Alarm Recovery Available Alarm Type QoSAlarm NM Level Cause CPU load, namely CPU utilization ratio reaches the set low thresh- old.
  • Page 77 %d is CPU utilization. Alarm Description CPU load, namely CPU utilization ratio exceeds the set high thresh- old. Supported Devices All. Appendix The platform 4.6.03b and the upgrade versions support this alarm. Specification Not CE&PTN version. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 78 Cause Distributing system RP sends a message to MP and inform to add or delete interface. Give an alarm after the synchronized message fails. Recommended Send the alarm message to ZTE's maintenance personnel. Operations 16907 Message No. 16907 Default Severity...
  • Page 79 Chapter 2 Alarm Message Recommended Send the alarm message to ZTE's maintenance personnel. Operations 16916 Message No. 16916 Default Severity Level Cause The ftp user logs into the device. Recommended Operations Alarm Prototype Alarm occurred Description 00:02:21 01/01/2001 UTC alarm 16916 occurred %OAM% ftp user from 192.168.1.125 port:...
  • Page 80 Specification “startrun” not complete. Reboot operation may lead to the loss of rack configuration or the command line error. Use dir to con- firm whether startrun file is updated. 16920 Message No. 16920 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 81 TFTP circularly. When retry time is 10, about 4~5 min- utes, version is not downloaded Influence Inform user of failure of downloading and suggest downloading again. Recommended Stop DHCP automatic download configuration file function. Operations Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 82 Threshold 55% Alarm Description The utilization ratio that process uses CPU resource reaches de- fined high threshold. Supported Devices 69 89 16925 Message No. 16925 Default Security Level Alarm Recovery Available Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 83 The first %s is process name type. The first %d and second %d are peak value of utilization ratio that process uses CPU resource. The third %d is low threshold that process uses CPU resource. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 84 Message No. 17410 Default Severity Level Cause The neighbor status shifts. Recommended Check whether the OSPF status shifts is normal according to the Operations displayed alarm message. If it is abnormal, please check whether Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 85 17414 Message No. 17414 Default Severity Level Cause The port receives error packets. Recommended Check whether the physical interface connection is reliable. Operations 17415 17415 Message No. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 86 17419 Message No. 17419 Default Severity Level Cause Packets are retransmitted at the interface. Recommended Please check whether the network status is normal and the net- Operations work load is too heavy. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 87 17422 Message No. 17422 Default Severity Level Cause Fail to distribute the memory. Recommended Please copy and save the information, then contact ZTE mainte- Operations nance staff. 17423 Message No. 17423 Default Severity Level Cause Receiving error request packet results in link-disconnection.
  • Page 88 Physical interface Down result in link-disconnection. Recommended Please check whether the shutdown operation is executed under Operations the interface. 17429 Message No. 17429 Default Severity Level Cause Interface state change results in link-disconnection. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 89 RIP module fails to create timer. Recommended If the problem appears during command configuration, it may at- Operations tempt a few minutes later. Please record the fault phenomenon and contact ZTE maintenance staff in time. 17667 Message No. 17667 Default Severity...
  • Page 90 RIP neighbor is running normally. 17676 Message No. 17676 Default Severity Level Cause The RIP interface status turns to down. Recommended Please check whehter the link status is normal and whether the Operations system is running normally. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 91 Fail to create the neighbor. Recommended Please check whether the configuration is correct and proper, the Operations system operation is normal and system memory application is to system maximum value. 17923 Message No. 17923 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 92 Message No. 17928 Default Severity Level Cause Fail to start the TCB of BGP active interception interface. Recommended Fail to start TCP for link setup. Please check whether TCP is running Operations normally first. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 93 17940 Message No. 17940 Default Severity Level Cause Received report is unidentifiable. Recommended Check the version information of the opposite end BGP, and check Operations whether the line connection is correct and proper. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 94 Please check whether the system operation is normal, and the Operations system resource occupancy is in normal range. After copying this alarm message, system resource occupancy and system configu- ration, contact with ZTE maintenance staff please. 17945 Message No. 17945...
  • Page 95: Message No

    Incorrect NOTIFICATION report Recommended Check the TX end settings. Operations 17950 Message No. 17950 Default Severity Level Cause Fail to transmit report. Recommended Check whether the port is operating normally. Operations 17951 Message No. 17951 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 96 Fail to transmit UPDATE unreachable report. Recommended None, and system will try again one second later. Operations 17956 Message No. 17956 Default Severity Level Cause SPOOL tries to send other report when it is not idle. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 97 Distribution protocol fails to use route memory. Recommended Check whether the route quantity is to maximum, and system Operations memory application is to the maximum value. 17961 Message No. 17961 Default Severity Level Cause The status shifts. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 98 Please check whether the physical link is normal. Recommended Operations DRP Alarm Syntax 18176 Message No. 18176 Default Severity Level Cause Fail to create IPI example. Recommended If possible, perform state machine change again. Operations 18177 Message No. 18177 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 99 The IPI example fails (exact information is in the generated alarm message description, which differs as the configuration varies) to create OSPF example for ROUTE-ID. Recommended If possible, perform state machine change again or set the relevant Operation parameters again. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 100 18190 Default Severity Level Cause Fail to distribute memory. Recommended Check whehter the router running is normal, the configuration is Operation proper and the system memory application is to maximum system operation limits. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 101 The new routing can not be added. Influence Related Alarms The alarm 18196 may occur before this alarm. Recommended Increase the routing maximum threshold according to the circum- Operations stance. Reduce the alarm. Configure Vpn route limit fuction, for Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 102 An alarm 18196 level 6 occurred at 00:01:02 01/01/2001 UTC sent by MCP %DRP% The routes warning limit of VPN1 is exceeded. Alarm Description The input vrf routing exceeds the configured alarm threshold. T128, 69 Supported Devices Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 103 Message No. 18436 Default Severity Level Cause TCP sends the message of who am I. Recommended Please check whether the local TCP address is set. Operations 18437 Message No. 18437 Default Severity Level Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 104 Cause TCP receives packets with BGP MD5 authentication failure. Recommended Check whether MD5 authentication setting is correct. Operations 18451 Message No. 18451 Default Severity Level Cause TCP receives packets with wrong header length. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 105 TCP sends the packets with incorrect IP versions. Recommended Check whether the remote IP address and TCP connection are nor- Operations mal. 18457 Message No. 18457 Default Severity Level Cause TCP fails in closing nonexistent connections. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 106 Default Severity Level Cause TCP calculates the available windows incorrectly. Recommended Check whether the TCP connection is normal. Operations 18463 Message No. 18463 Default Severity Level Cause When received BGP message, MD5 authentication fails. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 107 18562 Message No. 18562 Default Severity Level Cause UDP receives the packets with wrong headers. Recommended Check whether the network connection and router running is nor- Operations mal. 18563 Message No. 18563 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 108 Default Severity Level Cause RP fails to initialize routing table. Recommended If possible, save the configuration and then restart the router. Operations Please contact ZTE maintenance staff after saving this message. 18691 Message No. 18691 Default Severity Level Cause Fail to initialize the packet buffer.
  • Page 109 Default Severity Level Cause Receive the packet of undefined type. Recommended Check whether the network running is well and the system config- Operations uration is proper. 18738 Message No. 18738 Default Severity Level Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 110 Cause Receiving IP packets with illegal source address. Recommended Check whether the network connection and operation are normal, Operations and whether anybody is attacking the network. 18743 Message No. 18743 Default Severity Level Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 111 Check whether the network running status is normal. Operations 18784 Message No. 18784 Default Severity Level Cause route-map is configured on xx (digital No.) line card and there is no way to be valid. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 112 ZXR10 Alarm Handling Manual Recommended Please check whether the enabled route-map configuration on the Operations line card is reaching to system permitted limit configuration; if no, contact ZTE maintenance staff in time after recording the informa- tion. 18785 Message No. 18785...
  • Page 113 It makes no influence. If alarm sus- tains, check whether memory occupancy reaches the maximum and the configuration information reaches or exceeds the thresh- old. If the memory occupancy reaches the threshold, please up- grade the device. Or contact with ZTE corporation. 18794 Message No. 18794...
  • Page 114 4096 is the upper threshold of IPPOOL. Alarm occurred 20:33:24 08/13/2008 UTC alarm 18834 occurred %IP% ippool bitmap has reached max number 4096 sent by UPC(RPU) 2 Alarm Description Ippool address block number reaches the threshold. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 115 UPC(RPU) 1 Alarm Description The current ingress/egress traffic utilization exceeds the set threshold. Supported Devices T128, T1200 IGMP Alarm 18944 Message No. 18944 Default Severity Level Cause A member joins IGMP multicast group. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 116 Check whether ARP protection is configured and whether anybody Operations attacks balefully to pour ARP table fully. 19714 Message No. 19714 Default Severity Level Cause The received ARP report source MAC address is the same as local MAC address. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 117: Alarm Type Environmental Alarm

    Alarm Recovery Unvailable Alarm Type Environmental Alarm NM Level Cause Specify that at most 100 ARP packets can be received on interface per second. If the received packets are more than 100, drop the Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 118 Recommended Check whether the system operation and network connection is Operations normal, and whether the configuration is correct. 19970 Message No. 19970 Default Severity Level Cause Receive LSP packet from an invalid neighbor. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 119 SNP packet fails in authentication. Recommended Check whether the system configuration is correct and whether it Operations is consistent with the configuration of the opposite end. 19977 Message No. 19977 Default Severity Level Cause Receive illegal packets. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 120 When ISIS is in GR process, if system control module doesn't sup- port this boot mode, this alarm will be generated. Recommended Check whether the hot standby state of support module is correct. Operations 19982 Message No. 19982 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 121 The third %s: The string "P2P" or "BROADCAST". Port %s (port num %d) is deleted %s: interface name %d: interface number Port %s (port num %d) is not found, delete it %s: interface name Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 122: Rmon Alarm

    Cause The message data received by RMON module is wrong. Recommended Check whether the system running status is normal and the com- Operations mand input is correct. 20748 Message No. 20748 NM Level Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 123 RMON configurations again. 20793 Message No. 20793 NM Level Cause The resources do not exist. Recommended Check whether RMON configuration command is correct and the Operations relevant system parts are normally running. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 124 When Line-card reboots, one type of ACL: ACL+name(for example ACL test) is deleted. N.A. Recommended Operations Alarm Prototype Alarm occurred Description 05:46:35 04/16/2003 UTC alarm 21773 occurred %IP% SYNC ACLs, NPC send message failedsent by MEC 1 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 125 Stack Slave DevId 2 %ACL% Security access bind ip and mac error at driver. Alarm Description The drive operation is error on a non-stack master device. Supported Devices ZXR10 59/52 series. 21776 Message No. 21776 Default Severity Level Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 126 It's a prompt used when operation error occurs on a non-stack master device in stack system. Influence The current operation will not take effect. Recommended It's an internal processing error. Please contact ZTE engineer. Operations Alarm Prototype “Some error occurred” Description...
  • Page 127 Default Severity Level Cause vrrp status switchover notice Recommended Please check whether the status switchover is normal. If not, copy Operations: the alarm information and contact ZTE maintenance staff. MAC Alarm 22784 Message No. 22784 NM Level Cause MAC address reaches to the MAC quantity limitation set at port.
  • Page 128 MAC address of this port will be deleted. N.A. Recommended Operations 22792 Message No. 22792 NM Level Cause Outgoing interface of MAC address or inner outgoing tag changes. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 129 "< VLAN %4d > MAC address number drop to threshold" Prototype %s vlan id Example: 00:09:10 01/01/2001 UTC alarm 22794 occurred %MAC% < VLAN 1 > MAC address number drop to threshold sent by MEC 1 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 130 "< Port %s > Permanent MAC address canceled" Prototype Alarm Description When the interface is bound with smartgroup, if physical interface configures permanent mac alarm need to promprt that permanent mac address should be deleted. None Supported Devices Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 131 "Permanent MAC address number threshold reached" Prototype %d service number Example: 00:25:00 01/01/2001 UTC alarm 22798 occurred %MAC% Permanent MAC address number threshold reached Alarm Description Permanent MAC address number reaches the upper limit. 59A,69,89 Supported Devices Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 132 DHCP user obtains IP address and gets online. DHCP user releases IP address and gets offline. N.A. Recommended Operations 23809 Message No. 23809 Default Severity Level Alarm Recovery Available Alarm Type CommunicationAlarm NM Level Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 133 The user configure the IP address by manual which brings to that the IP address applied by DHCP CLIENT can not be withdrawed by DHCP SERVER immediately. Supported Devices ZXR10 5900. 23811 Message No. 23811 Default Severity Level Alarm Recovery Unavailable Alarm Type ProcessingErrorAlarm Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 134 Alarm Description The across network section roaming switch appears in DHCP Relay or DHCP server user. But the roaming switch is off. Supported Devices ZXR10 3900, 5900, 6900 series switch. T64E, T128, T600, T1200 series router. 23812 Message No. 23812...
  • Page 135 100.1.1.1 is n ot vlan100 addr sent by NPC Alarm Description DHCP Relay agent address is not the local interface address in the L3 interface that the DHCP users access. Supported Devices ZXR10 3900, 5900, 6900 series switch. T64E, T128, T600, T1200 series router. 23814 Message No. 23814...
  • Page 136 100.1.1.3 is local vrrp addr sent by NPC2 Alarm Description DHCP Relay Server address is the local VRRP address in the L3 interface that the DHCP users access. Supported Devices ZXR10 3900, 5900, 6900 series switch. T64E, T128, T600, T1200 series router. 23816 Message No. 23816...
  • Page 137 Chapter 2 Alarm Message Alarm Description DHCP Relay Server address is the local address in the L3 interface that the DHCP users access. Supported Devices ZXR10 3900, 5900, 6900 series switch. T64E, T128, T600, T1200 series router. 23817 Message No. 23817...
  • Page 138 Alarm Description The routing of the address distributed by the DHCP Server is not matching with the routing of the interface address. Supported Devices ZXR10 3900, 5900, 6900 series switch. T64E, T128, T600, T1200 series router. 23819 Message No. 23819...
  • Page 139 5 ! sent by NPC 2 Alarm Description DHCP access user number reaches the upper threshold. Supported Devices ZXR10 3900, 5900, 6900 series switch. T64E, T128, T600, T1200 series router. 23821 Message No.
  • Page 140 % DHCP policy bound invalid dhcppool [invalidPool] sent by UPC(RPU) 2 Alarm Description Invalid dhcppool. Supported Devices All. 23824 Message No. 23824 Default Severity Level Alarm Recovery Unavailable Alarm Type ProcessingErrorAlarm NM Level Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 141 Cause MLD multicast member leaves. Recommended Check whether MLD configuration is correct and proper. Check Operations whether it receives MLD multicast member joining or leaving pack- ets. STP Alarm 24320 Message No. 24320 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 142 24323 Message No. 24323 Default Severity Level Cause Delete STPROOT protect on the port instance, or the port instance receives inferior BPDU packet. Recommended N.A. Operations 24327 Message No. 24327 Default Security Level Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 143 Check whether the communication between UAS and accounting Operations server is normal. LDP Alarm 25344 Message No. 25344 Default Severity Level Cause Two different types of pw(spoke and hub) are configured in one vfi. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 144 OPERA- TIONAL,status code: 513 % Alarm Description LDP neighbor turns from OPERATIONAL state to NON EXIST state. Supported Devices ZXR10 T128. 25349 Message No. 25349 Default Severity Level Cause LDP GR is enabled Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 145 00:01:07 01/01/2001 UTC alarm 25355 occurred % LDP Timer% 25356 Message No. 25356 Default Severity Level Cause LDP fails to apply for LABEL resources, which are insufficient. Alarm Prototype Alarm occurred Description 00:01:07 01/01/2001 UTC alarm 25356 occurred % LDP Label% Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 146 L2VPN TLV 25858 Message No. 25858 Default Severity Level Cause GR is enabled in L2VPN Alarm ProtoType Alarm occurred Description 00:01:07 01/01/2001 UTC alarm 25858 occurred %L2VPN GR% 25859 Message No. 25859 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 147 ZESR ring turns from down state to up state. Recommended It notifies state changes of ZESR master node. Operations 26369 Message No. 26369 Default Severity Level Cause ZESR ring turns from down state to preup state. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 148 ZESR ring turns from preup state to down state and the reason is that Link-down frame is received. Recommended It notifies state changes of ZESR master node. Operations 26374 Message No. 26374 Default Severity Level Cause ZESR ring turns from preup state to up state. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 149 Recommended Please check whether the configuration of tacacs+server is cor- Operations rect; whether AAA configuration on NAS is correct; whether in- terconnection between NAS and server is ok; whether network communication is normal. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 150 Please check whether the configuration of tacacs+server is cor- Operations rect; whether AAA configuration on NAS is correct; whether in- terconnection between NAS and server is ok; whether network communication is normal. 28166 Message No. 28166 Default Severity Level Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 151: Aaa Alarms

    28167 Message No. 28167 Default Severity Level Cause Tacacs+ authentication request is wrong. Recommended It's an internal error, and please contact ZTE engineer. Operations 28168 Message No. 28168 Default Severity Level Cause Tacacs+ request packet is timeout.
  • Page 152 AAA fails to apply for memory space. Recommended Please check whether system memory utilization reaches the max Operations and whether system configuration information reaches or exceeds the threshold; if it does, consider upgrading the device. If system Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 153 Chapter 2 Alarm Message memory utilization doesn't reach the max, please contact ZTE en- gineer. MIX Alarms 29952 Message No. 29952 Default Severity Level Cause If the alarm state is occurred, it indicates the alarm has occurred. The general reason is main board detects that communication with other card breaks and the card doesn't work;...
  • Page 154 Alarm occurred The received packet in per unit time is more than the set value. The command used to set the value is: ZXR10(config-if)#port-up- send limit[packets num receive-interval num close-interval num]. The mode is interfasce configure mode, the received packet is counted by number and the time unit is seconds.
  • Page 155 This alarm may occur when plugging in or plugging out NPC. When plugging NPC, the event total number already reaches the upper threshold. After plugging in NPC, it tries to restore interface re- Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 156 When the system restore the relative sub event to the event list, the event total number already reaches the upper threshold. Supported Devices G-series, ZXR10 6900/8900. 29960 Message No. 29960 Default Security Level Alarm Type "ProcessingErrorAlarm" NM Level Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 157 [LDP BFD For FEC 10.40.64.121] is CONNECT on interface fei_1/1 BFD application prompt for RSVP LSP: 00:02:16 02/08/2002 UTC alarm 30208 occurred %BFD% Session [RSVP BFD For tunnel1] is CONNECT on interface fei_1/1 The prompt for other application: Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 158 00:02:16 02/08/2002 UTC alarm 30208 occurred %BFD% Session [RSVP BFD For tunnel1] is DOWN on interface fei_1/1 The prompt for other application: 00:02:16 02/08/2002 UTC alarm 30208 occurred %BFD% Session [10.40.64.120-->10.40.64.121] is DOWN on interface fei_1/1 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 159 An alarm 30213 level 5 occurred at 00:07:31 01/01/2001 UTC sent by UPC(RPU) 1 %BFD% Session CANNOT be created on interface smartgroup1 Alarm Description Establish BFD session on the interface which doesn't support it. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 160 %s: interface name, the two interfaces connect with the rack di- rectly. 00:14:07 01/01/2001 UTC alarm 29697 occurred interface fei_1/2 and fei_1/8 build udld neighbour relationship sent by MCP Alarm Description The loop occurs between the two ports. Supported Device ZXR10 3900/6900. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 161 %s: interface name 00:28:48 01/01/2001 UTC alarm 29699 occurred interface unidi- rection occurs on fei_1/2 sent by MCP 00:03:17 01/01/2001 UTC alarm 29699 cleared %UDLD% inter- face unidirection clears on fei_1/2 sent by MCP Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 162 Domain %u from up to down %d: the area id number, it can be 1-4. An alarm 32512 level 5 occurred at 04:49:42 02/01/2001 UTC sent by NPC 2 %ZESS% Domain 1 from down to up Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 163 An alarm 32514 level 5 occurred at 04:49:42 02/01/2001 UTC sent by NPC 2 %ZESS% Domain 1 from preup to up Alarm Description The timer times out. ZESS state turns from PREUP to UP. Supported Devices ZXR10 T40 T64 T160. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 164 The usage power (%dw) is above the PSE threshold (%dw) on pse The first %d: PSE total power of the power supply The second %d: PSE power threshold. The third %d: PSE device number. Example: Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 165 MCP Alarm Description 1. Power supply function on gei_2/1/24 is cancelled because of no response from port. 2. The power supply status on gei_1/10 becomes being in power supply. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 166 33280 Default Security Level Alarm Type "CommunicationAlarm" NM Level Cause Because the attenuation of the optical path between ONU and OLT is out of normal range or ONU and OLT optical parameter config- Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 167 Check the fiber connection between ONU module and OLT module. Operations This alarm is called frame error rate alarm in EPON project. This alarm can be opened and closed by using command and set alarm Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 168 < threshold> on the OLT interface. Alarm Description "Epon alarm llid-mismatch occour at %d!" Prototype %dindicate llid-mismatch value when alarm occurs. Example: Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 169 This alarm is called remote stable alarm in EPON project. In de- fault, this alarm is enabled. If the alarm need to be disabled con- figure “alarm remote-stable disable” on OLT interface. This alarm generates on ONU side and be sent back to OLT. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 170 Register ONU again. Recommended Operations This alarm is called registration error alarm in EPON project. In default, this alarm is enabled. If the alarm need to be disabled configure “alarm registration-error disable” on OLT interface. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 171 ZXR10(config-epon)#hardware-authentication card 5 disabled ZXR10(config-epon)#auto-authentication card 5 enable 2. The registration that need binding mac. ZXR10(config-epon)#hardware-authentication card 5 enable ZXR10(config-epon)#auto-authentication card 5 disabled ZXR10(config-if)#onu 1 type ZTE-F425 mac 0015.eba3.c6c9 Alarm Description "Epon alarm onu registration-error occour!" Prototype Example: 18:41:30 08/26/2008 UTC alarm 33286 occurred %EPON% Epon...
  • Page 172 14:57:30 08/26/2008 UTC alarm 33288 occurred %EPON% Epon alarm dying-gasp occour! sent by NPC 3 Alarm Description Communication over fiber is abnormal. Supported Devices EPON project of 4822 33289 Message No. 33289 Default Security Level Alarm Type "CommunicationAlarm" Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 173 NPC 3 Alarm Description It’s a data loading fault or other dying gasp fault. Or fault occurs in receive direction of local data terminal device. Supported Devices EPON project of 4822 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 174 Example: 10:57:30 08/26/2008 UTC alarm 33292 occurred %EPON% Epon alarm optical-power-overflow occour! sent by NPC 3 Alarm recovery 10:58:10 08/26/2008 UTC alarm 33292 cleared %EPON% Epon alarm optical-power-overflow recover! sent by NPC 3 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 175 Alarm Description "Epon alarm optical protection switch from interface %s to inter- Prototype face %s ” The first %sindicate the interface name before switchover. The second %s: indicate the interface name after switchover. Example: Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 176 ONU %s remote configuration fails for invalid parameter Prototype %s OLT sub interface name Example: 00:54:34 12/14/2008 UTC alarm 33296 occurred %EPON% ONU epon-olt_2/16.2 remote configuration fails for invalid parameter sent by MEC 1 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 177 00:54:34 12/14/2008 UTC alarm 33296 occurred %EPON% ONU epon-olt_2/16.2 remote configuration fails for wrong onu status or capability Alarm Description ONU status is wrong or ONU don't have the capability to configure this command. ZXR10 8900 Supported Devices Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 178 ZXR10 Alarm Handling Manual This page is intentionally blank. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 179 Cause The input parameter is illegal. Recommended Input the correct parameter to try again according to the command Operations prompt and ZXR10 Data Product Command Manual. Message No. Cause Fail to access database. Recommended Check whether the system operation is normal and the input con- Operations figuration information is correct.
  • Page 180 ZXR10 Alarm Handling Manual Recommended Check whether the system operation is normal and the configura- Operations tion is following the normal flow. If everything is correct, contact ZTE maintenance staff after recording the error please. Message No. Cause Fail to send message. Recommended Check whether the system operation is normal and try again later.
  • Page 181 Message No. Cause Fail to write nvram. Recommended Check whether the system operation is normal, and try again later. Operations If unsuccessful, please contact ZTE maintenance staff after record- ing the error. Message No. Cause Fail to write to flash. Recommended...
  • Page 182 Please check whether the flash exists or being damaged. If every- Operations thing is normal, please try again later. If fail to retry all the time, please contact ZTE maintenance staff after recording the error. Message No. Cause Fail to write configuration file.
  • Page 183 Message No. Cause Too many directory levels Recommended Reduce the directory levels. Operations Message No. Cause Boot upgrade is undergoing. Wait please. Recommended Try again later. Operations Message No. Cause Fail to update boot. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 184 Recommended Please check whether the boot file to upgrade exists. Please stop Operations system traffic and retry when the system is idle. If fail to retry many times, please contact ZTE maintenance staff after recording the error. Message No. Cause The line board to upgrade is offline.
  • Page 185 There is no response to overtime when writing Img image file. Recommended Check whether the system is busy, or the system flash exists or is Operations damaged please. If fail to retry many times, please contact ZTE maintenance staff after recording the error. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 186 Message No. Cause The command takes effect at the next start. N.A. Recommended Operations Message No. Cause router-id cannot be 0. Recommended Please configure correct command. Operations Message No. Cause Too many ldp interfaces. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 187 Message No. Cause The mpls cannot run at the loopback interface. Recommended Please configure correct command. Operations Message No. Cause The parameter setting is improper. Recommended Please set correct command parameter. Operations Message No. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 188 Check whether the line connection and server operation are nor- Operations mal. Message No. Cause Start to copy. Recommended Informational notice. No action is needed. Operations Message No. Cause Fail in Network-to-network copy. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 189 The command explanation module sends error messages. Recommended Please check whether the system is running normally and try again Operations later. If error remained many times, please contact ZTE mainte- nance staff after recording the error. Message No. Cause Transmit synchronization message incorrectly.
  • Page 190 Fail to transmit the response message. Recommended Check whether the system running is normal; if normal, please Operations try again later. If error appeared many times, please contact ZTE maintenance staff after recording the error. Message No. Cause It does not support the system file reading and writing temporarily.
  • Page 191 Please check whether the input parameter is legal and the com- Operations mand configuration is correct. Message No. Cause Fail to delete file. Recommended Please check whether the input parameter is correct and the file Operations is used. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 192 Informational notice. No action is needed. Operations Message No. Cause The command execution mode is wrong. Recommended Please contact ZTE maintenance staff after recording the error. Operations Message No. Cause Incorrect target file name path Recommended Please input the correct command parameter.
  • Page 193 Fail in route-map configuration operation. Recommended Check whether the configuration command is correct and proper, Operations and try again later. If fail to retry many times, please contact ZTE maintenance staff after recording the error. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 194 ZXR10 Alarm Handling Manual Message No. Cause Too many parameters entered Recommended Perform the configuration by following ZXR10 Router/Ethernet Operations Switch Command Manual please. Message No. Cause Input ACL incorrectly. Recommended Please input the correct command parameter. Operations Message No.
  • Page 195 ZTE maintenance staff after recording the error. Message No. Cause Fail to set the cos IP priority function. Recommended Please contact ZTE maintenance staff after recording the error. It Operations may try again later. Message No. Cause Fail to set cos IP priority function data.
  • Page 196 Please input the correct command parameter. Operations Message No. Cause The rule expression is too long. Recommended Please input the correct command parameter. Operations Message No. Cause Fail to distribute the memory for rule expression. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 197 Internal error occurs during rule expression generation. Recommended Please check whether the input command is proper and try again Operations later. Message No. Cause The + and * operations in the rule expression cannot be vacant initially. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 198 The content after +, * and % in the rule expression cannot be vacant. Recommended Please input the correct command parameter. Operations Message No. Cause There are other errors in the rule expression. Recommended Please input the correct command parameter. Operations Message No. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 199 The copies are wrong, and fail to write file. Recommended Check whether the system operation is normal, and try again later. Operations If error remained many times, please contact ZTE maintenance staff after recording the error. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 200 Message No. Cause Fail to access. There are too many users online at present. Recommended Please try again later. Operations Message No. Cause Fail to access. There are too many users online at present. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 201 The flash is not existed. Recommended Please check whether the system is running normally and the flash Operations device exists. Message No. Cause The system provides the reference clock for the interface board. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 202 Message No. Cause Too many configured prefix-list items, it reaches to permitted item quantity limitation. Recommended Check the configured prefix-list items and delete some unneces- Operations sary items, then perform the configuration. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 203 Recommended Check whether the configured prefix-list items reaches to limita- Operations tion, if not, try again later. If it remains the same after retrying many times, please contact ZTE maintenance staff after recording the error. Message No. Cause Fail to find prefix-list item.
  • Page 204 The user group does not exist. Recommended Please perform command configuration in correct sequence and Operations check whether the input parameters are correct. Message No. Cause There is illegal character in user group name. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 205 1005 Message No. 1005 Cause Fail to add IP address. Recommended Please check whether the parameter is correct and try again later. Operations 1006 Message No. 1006 Cause Fail to delete IP address. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 206 The next hop address is illegal, which cannot be the configured address for router. Recommended Please input the correct parameter. Operations 1011 Message No. 1011 Cause The next hop address is illegal, which can only be a direct-connect network section address. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 207 1015 Message No. 1015 Cause The interface is not configured with the route discovery. Recommended This is the system prompt. Operations 1016 Message No. 1016 Cause The interface has no IP address. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 208 Please check whether the input parameter is correct. Operations 1021 Message No. 1021 Cause The interface board already exists. Recommended This is the system prompt. Operations 1022 Message No. 1022 Cause The interface board does not exist. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 209 The debug of arp packet is deactivated. Recommended Informational notice. No action is needed. Operations 1028 Message No. 1028 Cause The debug of icmp packet is activated. Recommended Informational notice. No action is needed. Operations 1029 Message No. 1029 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 210 1033 Cause Fail to match the route to delete. Recommended Please check whether the input parameter is correct. Operations 1034 Message No. 1034 Cause Please remove the ip unnumber attribution of interface first. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 211 Please input the correct parameter and try again later. Operations 1039 Message No. 1039 Cause The address and mask are mismatched. Recommended Please configure correct command. Operations 1040 Message No. 1040 Cause The option length is incorrect. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 212 1049 Message No. 1049 Cause The input PVC value reaches the maximum limit. Recommended Please check whether the system configuration is proper and the Operations configuration information reaches the maximum system permitted value. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 213 1054 Message No. 1054 Cause Fail to delete ATM interface. Recommended Please check whether the input parameter is correct, and try again Operations later. 1055 Message No. 1055 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 214 Confirm that the input parameter is correct. Operations 1060 Message No. 1060 Cause PVC is used by other interface. Recommended Please check whether the input parameter is correct and whether Operations the command configuration is proper. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 215 Please plug in and plug out the designated interface board. Operations 1070 Message No. 1070 Cause Unable to create the interface Recommended Please input the correct command parameter. Operations 1071 Message No. 1071 Cause Unable to delete the interface Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 216 Please check whether the configuration is proper. Operations 1080 Message No. 1080 Cause No arp item exists. Recommended This is the system prompt. Operations 1081 Message No. 1081 Cause The interface has no arp item. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 217 Recommended Please start DHCP server. Operations 1502 Message No. 1502 Cause DHCP relay is still running. Please stop it first. Recommended Please check whether DHCP server stops working. Operations 1503 Message No. 1503 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 218 No main RADIUS server, please configure it first. Recommended please configure main RADIUS server first. Operations 2001 Message No. 2001 Cause No IP example is running. Recommended None. Operations 2002 Message No. 2002 Cause OSPF example is already running. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 219 Please check whether the command configuration is proper and Operations the parameter is correct. 2007 Message No. 2007 Cause The area is disabled. Recommended Please check whether the command configuration is proper and Operations whether the parameter is correct. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 220 It may try again later. Operations 2012 Message No. 2012 Cause This area is not NSSA area. Recommended Please check if the input parameter and the command configura- Operations tion are correct. 2013 Message No. 2013 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 221 It may try again later. Operations 2018 Message No. 2018 Cause Fail to delete NSSA area. Recommended Check whether the command configuration sequence is proper and Operations whether the command configuration is correct. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 222 Please check whether the command parameter is correct. Operations 2024 Message No. 2024 Cause OSPF is disabled. Recommended Please check whether the command configuration sequence is Operations proper and whether the command configuration is correct. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 223 Cause Fail to create OSPF example interface. Recommended Check whether the command configuration is proper and correct, Operations and try again later. 2030 Message No. 2030 Cause Fail to enable OSPF example interface. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 224 2034 Cause Fail to delete import filter. Recommended Check whethewr the command configuration is correct and try Operations again later. 2035 Message No. 2035 Cause The imported template quantity reaches the maximum value. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 225 It may try again later. Operations 2040 Message No. 2040 Cause Illegal LSA group time slice Recommended Please check whether the command parameter is correct and Operations whether the parameter configuration is proper. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 226 Fail to delete the import template. Recommended It may try again later. Operations 2045 Message No. 2045 Cause The address and mask are mismatched. Recommended Please configure correct command. Operations 2046 Message No. 2046 Cause Unknown protocol type Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 227 Please check whether the command configuration is proper and Operations correct. 2051 Message No. 2051 Cause The backbone area is disabled. Recommended Please check whether the command configuration is proper. Operations 2052 Message No. 2052 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 228 The MD5 keyword configured at the interface reaches the maxi- mum value. Recommended Decrease or change MD5 keyword. Operations 2057 Message No. 2057 Cause Warning: The router is ASBR but it has only one stub area. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 229 The vrf command does not match the OSPF example. Recommended Please check whether the command configuration is correct. Operations 2801 Message No. 2801 Cause The backbone area cannot be configured as an NSSA area. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 230 The stub area cannot be configured as an NSSA area. Recommended This is the system prompt. Operations 2803 Message No. 2803 Cause The ZXR10 router have only one NSSA area . Recommended This is the system prompt. Operations 2804 Message No. 2804 Cause It cannot configure NSSA area at stub.
  • Page 231 Recommended Please configure correct command. Operations 2812 Message No. 2812 Cause Please enable the OSPF example first. Recommended Please enable the OSPF example in global configuration. Operations 2813 Message No. 2813 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 232 No RIP example This is the system prompt. Recommended Operations 3003 Message No. 3003 Cause It cannot create RIP example. Recommended Please check whether the system is running normally and try again Operations later. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 233 3008 Cause This neighbor cannot be deleted. Recommended Check whether the command configuration is correct and try again Operations later. 3009 Message No. 3009 Cause The same neighbor already exists on this interface. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 234 The same key id already exists. Recommended None. Operations 3014 Message No. 3014 Cause Errors redistribution Recommended Check whether the system running is normal and whether the com- Operations mand configuration is correct and proper. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 235 Operations 4001 Message No. 4001 Cause It is only the A, B or C type network. Recommended This is the system prompt. Operations 4002 Message No. 4002 Cause The network mask is discontinuous. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 236 Please configure correct command. Operations 4007 Message No. 4007 Cause The mask parameter must be at the network side. Recommended Please configure correct command. Operations 4008 Message No. 4008 Cause The mask is too short. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 237 Please input the correct command configuration parameter. Operations 4013 Message No. 4013 Cause The input value is mismatched. Please adjust or use the default value. Recommended Please input the correct command parameter. Operations 4014 Message No. 4014 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 238 4031 Message No. 4031 Cause This neighbor does not exist. Recommended Please check whether the command configuration parameter is Operations correct. 4032 Message No. 4032 Cause This neighbor already exists. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 239 It supports maximum 3 neighbors’ debug function at one time. Recommended This is the system prompt. Operations 4037 Message No. 4037 Cause The neighbor's update debug function is not enabled. Recommended This is the system prompt. Operations 4038 Message No. 4038 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 240 Message No. 4042 Cause The coalition end point quantity exceeds the maximum value. Recommended This is the system prompt. Operations 4043 Message No. 4043 Cause The command is run in common user mode. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 241 No local AS member is allowed existing in coalition node list. Recommended Please check whether the command configuration is proper. Operations 4048 Message No. 4048 Cause No address-family example Recommended Please check whether the command configuration is correct. Operations 4049 Message No. 4049 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 242 Cause No DIS parameter can be set at a non-broadcast interface. Recommended This is the system prompt. Operations 4505 Message No. 4505 Cause No retransmission interval can be set at a broadcast interface. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 243 It is not allowed to change the system-id when changing the sys- tem-id range. Recommended Please do not change the system-id. Operations 4510 Message No. 4510 Cause It is not allowed to modify the system id when a system id exists already. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 244 This is the system prompt. Operations 5003 Message No. 5003 Cause The TCP connection is not set up. Recommended Please check whether the configuration is correct and whether ACL Operations blocks the TCP connection. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 245 Cause Error RMON group number Recommended Please confirm whether the current version supports RMON-related Operations groups and the command configuration is correct. 6010 Message No. 6010 Cause Error data in received message packet Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 246 Please check whether RMON supports the command and whether Operations the command configuration is correct. 6022 Message No. 6022 Cause Error command parameter Recommended Please check whether the input command parameter is valid and Operations proper. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 247 Please check if the command configuration is correct and try again Operations later. 6027 Message No. 6027 Cause Error ingress deletion (index not existed or mismatched) Recommended Please check if the command parameter is correct. Operations 6028 Message No. 6028 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 248 The history table is blank. Recommended This is the system prompt. Operations 6033 Message No. 6033 Cause The host table is blank. Recommended This is the system prompt. Operations 6034 Message No. 6034 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 249 Cause The event table is blank. Recommended This is the system prompt. Operations 6040 Message No. 6040 Cause The RMON timer is wrong. Recommended Please try again later. Operations 6050 Message No. 6050 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 250 Please check whether the command configuration is correct and Operations try again later. 6054 Message No. 6054 Cause Incorrect OID Recommended Please input the correct parameter and try again later. Operations 6055 Message No. 6055 Cause Add event table incorrectly. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 251 Recommended This is the system prompt. Operations 6059 Message No. 6059 Cause The index exists already. Recommended This is the system prompt. Operations 6080 Message No. 6080 Cause Ethernet statistics index number error Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 252 Recommended Please configure correct command. Operations 6085 Message No. 6085 Cause Matrix control table index number error Recommended Please configure correct command. Operations 6086 Message No. 6086 Cause Filter table index number error Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 253 Please check whether the configuration parameter is correct. Operations 7001 Message No. 7001 Cause Message ID error Recommended This is the system prompt. Operations 7002 Message No. 7002 Cause Incorrect pointer to obtain synchronous message return Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 254 This is the system prompt. Please try again later. Operations 7007 Message No. 7007 Cause Error process status Recommended Please check whether the system is running normally. Operations 7008 Message No. 7008 Cause Fail in initialization. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 255 Fail to write to database. Recommended Please try again later. Operations 7021 Message No. 7021 Cause Fail to access database. Recommended Please try again later. Operations 7022 Message No. 7022 Cause Fail to delete database. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 256 Please check if the input parameter is correct. Operations 7032 Message No. 7032 Cause Error command message ID Recommended Please check whether the system supports this command. Operations 7040 Message No. 7040 Cause The main log switch is turned off. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 257 Operations 7052 Message No. 7052 Cause Timer error occurs when starting log timing saving. Recommended Please try again later. Operations 7053 Message No. 7053 Cause Error pointers to obtain the message return area Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 258 Message No. 7065 Cause The alarm level corresponding to the alarm ID cannot be changed as the specific value. Recommended Please check whether the input parameter is correct. Operations 7066 Message No. 7066 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 259 Fail to set the unified NM trap host address. Recommended Please try again later. Operations 7081 Message No. 7081 Cause Error board type Recommended Please check whether the input parameter is correct. Operations 7082 Message No. 7082 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 260 8009 Cause The buffer is insufficient. Recommended Please try again later. Operations 8010 Message No. 8010 Cause Error occurs when obtaining configuration information. Recommended Please try again later. Operations 8011 Message No. 8011 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 261 Please check whether the input parameter is correct. Operations 8505 Message No. 8505 Cause PPP is not configured on this interface. Recommended Please check whether the system configuration is correct. Operations 8506 Message No. 8506 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 262 8513 Message No. 8513 Cause The IP address range of address pool is overlapped. Recommended There can't be repeated addresses in address pool. Please reset Operations Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 263 Please check whether the command configuration is correct. Operations 8601 Message No. 8601 Cause Fail to add address pool. Recommended Please try again later. Operations 8602 Message No. 8602 Cause Fail to delete address pool. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 264 Fail in interface configuration. Recommended Please try again later. Operations 8606 Message No. 8606 Cause Fail in interface configuration. Recommended Please try again later. Operations 8607 Message No. 8607 Cause NAT board is not got ready. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 265 Message No. 8612 Cause The address prefix is too long. Recommended Please check whether the input parameter range is proper. Operations 8613 Message No. 8613 Cause This interface is not configured as inside interface. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 266 Please check whether the command parameter is correct. Operations 8618 Message No. 8618 Cause The address pool name or address conflicts with others. Recommended Please check whether the command configuration is proper and Operations correct. 8619 Message No. 8619 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 267 8623 Cause Address confliction exists in the address pool and static rule. Recommended Please configure correct command. Operations 8624 Message No. 8624 Cause Address confliction exists in the static rule and dynamic rule. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 268 Please check whether the command configuration is correct. Operations 8703 Message No. 8703 Cause The time slot is used by another channel. Recommended Please check whether the parameter configuration is correct. Operations 8704 Message No. 8704 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 269 Please exit the multi-linkset configuration mode and then input the Operations command. 8708 Message No. 8708 Cause The command is illegal. Recommended Please check whether the command is supported in the mode. Operations 8801 Message No. 8801 Cause vrf does not exist. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 270 Message No. 8806 Cause VRF does not exist, or it has no RD. Recommended Please check whether the command configuration is correct. Operations 8901 Message No. 8901 Cause No frame-relay example at the interface Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 271 Please check whether the system configuration is correct. Operations 8907 Message No. 8907 Cause Error frame-relay parameter Recommended Please check whether the input parameter is correct. Operations 8908 Message No. 8908 Cause To configure DCE/NNI must enable frame-relay exchange. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 272 The frame-relay packet debug is closed. Recommended This is the system prompt. Operations 8913 Message No. 8913 Cause The frame-relay LMI debug is opened. Recommended This is the system prompt. Operations 8914 Message No. 8914 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 273 No frame-relay is configured for the interface. Recommended Please check whether the command configuration is proper and Operations correct. 8919 Message No. 8919 Cause The interface PVC quantity reaches the upper limit, unable to cre- ate PVC any more. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 274 There are too many members at buddle. Recommended Please check whether the command configuration is correct. Operations 8955 Message No. 8955 Cause Fail to find main connection. Recommended Please check whether the command configuration is proper and Operations correct. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 275 Please check whether the command parameter is correct. Operations 9005 Message No. 9005 Cause The group broadcast routing table does not exist. Recommended Please check whether the system is running correctly and the con- Operations figuration is correct. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 276 9106 Message No. 9106 Cause The pim spare mode is configured. Recommended This is the system prompt. Operations 9201 Message No. 9201 Cause The pimsm is running on this interface. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 277 9501 Message No. 9501 Cause There are few interfaces in the channel group. Recommended Please check whether the system configuration is correct and Operations proper. 9502 Message No. 9502 Cause Error parameter type Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 278 Recommended Please check whether the command parameter is correct. Operations 9510 Message No. 9510 Cause The system memory is insufficient. Recommended Please try again after deleting some useless configurations of the Operations system. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 279 Message No. 9515 Cause Error input channel mode Recommended Please check whether the command parameter is correct. Operations 9516 Message No. 9516 Cause Please allocate the above interfaces to the same management group first. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 280 Please allocate the above interfaces to the same vlan first. Recommended Please check whether the system configuration is proper and cor- Operations rect. 9521 Message No. 9521 Cause The buffer reserved for show command is overflowed. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 281 The IP address already exists in interface address group. Recommended Please check whether the command parameter is correct. Operations 9603 Message No. 9603 Cause IP address conflicts with the one at other interface. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 282 Please check whether the command parameter is correct and Operations proper. 12401 Message Number 12401 Alarm Reason The number of Template exceeds the maximum value. Recommended Delete some unused Template. Operations 12402 Message Number 12402 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 283 Alarm Reason This Template doesn't bind FW board or DPI board. Recommended Bind FW board or DPI board first. Operations 12407 Message Number 12407 Alarm Reason This Template has been bound with other Vlan. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 284 Create this signature entry first. Operations 12421 Message Number 12421 Alarm Reason This signature symbol doesn't exist. Recommended Create this signature symbol first. Operations 12422 Message Number 12422 Alarm Reason This flow pool doesn't exist. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 285 Verify which Template this VLAN interface has been bound in. Operations 12427 12427 Message Number Alarm Reason This Template hasn't bound with service. Recommended Bind Template with service. Operations 12428 12428 Message Number Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 286 This entry hasn't been configured. Recommended Configure this entry first. Operations 12433 Message Number 12433 Alarm Reason This service is bound with a Template. Recommended Release the Template binding with this service. Operations 30201 30201 Message Number Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 287 Please configure acl_ipv6f_entrynum first to make it non-null. Operations 30206 Message Number 30206 Alarm Reason At ESM_UDF mode, user configured entry number occupied ESM space has exceeded space of Sram or TCAM (TCAM space: 350MHz :521K, 500MHz 256K). Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 288 Note TCAM type when it is configured. Operations 30208 30208 Message Number Alarm Reason The deleting ACL mode of ESM configuration does not exist Recommended Configure ESM acl mode first and then delete. Operations Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 289: Trap Message Explanation

    The trap is sent during system power-on and starting. Description Triggering Criteria 1. The system is been powered on and started. 2. The relevant configuration for SNMP sending trap is correct. Recommended None. Operations Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 290 1. The interface management and operation status both are in 2. The relevant configuration for SNMP sending trap is correct. Recommended None. Operations Binding variables ifIndex (interface index) OID: 1.3.6.1.2.1.2.2.1.1 ifAdminStatus (interface managing status) OID: 1.3.6.1.2.1.2.2.1.7 ifOperStatus (interface operating status) OID: 1.3.6.1.2.1.2.2.1.8 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 291: Alarm Trap Message

    Rack No., value 1 OID: 1.3.6.1.4.1.3902.3.4.6.1.1 Shelf No., value 1 OID: 1.3.6.1.4.1.3902.3.4.6.1.2 Slot number OID: 1.3.6.1.4.1.3902.3.4.6.1.3 Port No., value 0 if no corresponding port existed OID: 1.3.6.1.4.1.3902.3.4.6.1.4 Alarm Code OID: 1.3.6.1.4.1.3902.3.4.6.1.5 Alarm Severe level Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 292: Software Alarm Trap

    OID: 1.3.6.1.4.1.3902.3.4.7.1.2 Slot number OID: 1.3.6.1.4.1.3902.3.4.7.1.3 Alarm Code OID: 1.3.6.1.4.1.3902.3.4.7.1.4 Alarm Severe level OID: 1.3.6.1.4.1.3902.3.4.7.1.5 Alarm generation time OID: 1.3.6.1.4.1.3902.3.4.7.1.6 Alarm status: alarm created OID: 1.3.6.1.4.1.3902.3.4.7.1.7 Alarm Type: ros 65, database 66 … Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 293: Rmon Trap Message

    3. The relevant configuration for SNMP sending trap is correct. Recommended Please take the corresponding measure according to the influence Operations of the monitored variable changes on the system. Binding variables alarmIndex (alarm control table item index No.) Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 294: Ospf Trap Message

    OSPF virtual interface is normal, and the router OSPF configuration (and the OSPF configuration of neighbors related to OSPF) is normal; if the fault remained, please contact ZTE. Binding variables ospfRouterId (router ID used to distinguish the routers in au- tonomous system, and the value is only value) OID: 1.3.6.1.2.1.14.1.1...
  • Page 295 OID: 1.3.6.1.2.1.14.1.1 ospfVirtNbrArea (the area crossed by OSPF virtual neighbor) OID: 1.3.6.1.2.1.14.11.1.1 ospfVirtNbrRtrId (the router ID of OSPF virtual neighbor) OID: 1.3.6.1.2.1.14.11.1.2 ospfVirtNbrState (OSPF virtual neighbor status) OID: 1.3.6.1.2.1.14.11.1.5 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 296 Binding variables ospfRouterId (router ID used to distinguish the routers in au- tonomous system, and the value is only value) OID: 1.3.6.1.2.1.14.1.1 ospfVirtIfAreaId (the area ID crossed by OSPF virtual connection) OID: 1.3.6.1.2.1.14.9.1.1 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 297 (the possible types of OSPF configuration er- rors, as error version number, mismatched area number and un- known virtual neighbor) OID: 1.3.6.1.2.1.14.16.1.2 ospfPacketType (OSPF packet type: hello packet, lsReq packet, and lsAck packet) OID: 1.3.6.1.2.1.14.16.1.3 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 298 OID: 1.3.6.1.2.1.14.1.1 ospfIfIpAddress (the IP address at OSPF interface) OID: 1.3.6.1.2.1.14.7.1.1 ospfAddressLessIf (index of interface without address, 0 for inter- face with address and ifIndex index for interface without address) OID: 1.3.6.1.2.1.14.7.1.2 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 299 OID: 1.3.6.1.2.1.14.1.1 ospfIfIpAddress (the IP address at OSPF interface) OID: 1.3.6.1.2.1.14.7.1.1 ospfAddressLessIf (index of interface without address, 0 for inter- face with address and ifIndex index for interface without address) Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 300 (link status broadcast type: router link, network link, and group broadcast link) OID: 1.3.6.1.2.1.14.4.1.2 ospfLsdbLsid (link status ID, formed by router ID or IP address) OID: 1.3.6.1.2.1.14.4.1.3 ospfLsdbRouterId (router ID originating link status broadcast re- port) OID: 1.3.6.1.2.1.14.4.1.4 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 301 (the area ID of router, value 0.0.0.0 for outside of autonomous system) OID: 1.3.6.1.2.1.14.4.1.1 ospfLsdbType (link status broadcast type: router link, network link, and group broadcast link) OID: 1.3.6.1.2.1.14.4.1.2 ospfLsdbLsid (link status ID, formed by router ID or IP address) Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 302 (router ID used to distinguish the routers in au- tonomous system, and the value is only value) OID: 1.3.6.1.2.1.14.1.1 ospfExtLsdbLimit (the maximum non-default external LSA quantity able to store on link status database) OID: 1.3.6.1.2.1.14.1.11 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 303: Bgp Trap Message

    BGP peer; value 0 if no error) OID: 1.3.6.1.2.1.15.3.1.14 bgpPeerState (BGP peer status, as idle, connect, and active) OID: 1.3.6.1.2.1.15.3.1.2 bgpBackwardTransition Information The trap indicates that BGP state machine regresses from high- Description level status to lower-level status. Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 304: Dhcp Trap Message

    Recommended Operations Binding variables offline Information The trap message sent when DHCP user gets offline. Description Triggering Criteria 1. DHCP user gets offline. 2. SNMP configuration for sending trap is correct. Recommended Operations Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 305: Vrrp Trap Message

    Check whether the system is steady after the active and the Operations standby changeover. Binding variables vrrpOperMasterIpAddr(the virtual IP address, when the active turns into standby) OID: 1, 3, 6, 1, 2, 1, 68, 1, 3, 1, 7, 0, 0 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 306: Ipv6Trap Information

    2. The configuration of SNMP related to PoE sending trap is cor- rect. Recommended N.A. Operations Bound Variables pethPsePortGroupIndexPSE device number OID 1.3.6.1.2.1.105.1.1.1.1 pethPsePortIndex (Port index) OID 1.3.6.1.2.1.105.1.1.1.2 pethPsePortDetectionStatus ( Port PoE power supply status) OID 1.3.6.1.2.1.105.1.1.1.6 Confidential and Proprietary Information of ZTE CORPORATION...
  • Page 307 2. The configuration of SNMP related to PoE sending trap is cor- rect. Recommended N.A. Operations Bound Variables pethMainPseGroupIndexPSE device number OID 1.3.6.1.2.1.105.1.3.1.1.1 pethMainPseConsumptionPowerPSE total power of power supply OID 1.3.6.1.2.1.105.1.3.1.1.4 pethMainPseUsageThresholdPSE power threshold OID 1.3.6.1.2.1.105.1.3.1.1.5 Confidential and Proprietary Information of ZTE CORPORATION...

Table of Contents

Save PDF