ZTEDH ZXR10 Router/Ethernet Switch Alarm Handling Manual {ZTE CORPORATION PLR. China 518057 Tel: (86) 7: Fax: (86) URL mai 26771900, 26770802, it Version 4.8.23LEGAL INFORMATION Copyright © 2006 ZTE CORPOR ATION. ‘The contents of this document are protected by copyright laws and intemational treaties. Any reproduction or dtribution of this document or any partion ofthis document, in any frm by any means, thou the prior written consent of ZTE CORPO- RATION s prohibited, Addtionally, the contents of this document are protected by contractual confidential obligations. ‘All company, brand and product names are trade or service matks, or registered trade or service marks, of ZTE CORPOR ATION or of their respective owners, This document is provided "a i", and all express, implied, or statutory warranties, representations or condtions are ds- claimed, inducing without limitation any implied warranty of merchartabty,fness for pattcular purpose, title er norin- Fringement, ZTE CORPORATION anditslcensers shall nat be lable For damages resulting from the use oF or reliance on the information contained herein. ZZTE CORPCRATION or its licensors may have current or pencing intellectual property ights or applications covering the subject, tmalter ofthis document. Except as expressly provided in any wien license between ZTE CORPORATION ands licensee, the user of ths documert shallnct acquire any license to the subject matter herein {ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice Users may ist ZTE technical sunpert website hitp:/Jensuppatzte.com cn to inquire related information. ‘The imate right to interpret this product resides in ZTE CORPORATION. Revision History Revision No. _| Revision Date | Revision Reason R10 Oct.16th, 2009 _| First Edition’ Serial Number: sj2I20095779Contents About This Manual... Alarm Overview overview. Alarm Glossry Overview Message No. Default Severity Level Alarm Recovery Alarm Type... NM Level... Cause . RRR HHH Related Alarms - Recommended Operations Alarm Prototype Description Alarm Description...... - Supported device type ........ Appendix Description Message Format Description...... Alarm Message. Hardware alarm Environment Alarm ... 64 vsecssesssesstrnsttssttssteastsaninsttseteseesesessses 20 68 vsecssesssesstrnstnesttsstsnetaninsteseteseeseenetes LD en a OE ES a TBesesssessetietinstenstnsttiastasenstssetssetsssnsses 16 TAssssssersetietinstinsetsetiastissinsensetisetssensees LT TB csesssessstistinstesstesstiastisninstesetssetcssensees 18 TWO csssssessstsstinstnnsteveteetaninstssetnetsesneses 19 weoeOCnnnnne ewwBO... Board Alarms 279 293 299 300 301 302 303 310 Bil 312 313 Port Alarm .. 512 540 S41 542 Software Alarm ETHOAM Alarm... 16128 16129 16130 16131 30464 30465 30466 30467 ROS Alarm... 16384 16386 16389 16391 16392 16393 16394 16395 16396 DATABASE Alarm ..... 16640 1) 222 222 222 222 21.23 224 224 2.25 21-26 21-26 227 a) 2129 2129 2129 2129 2129 2130 2130 2130 e31 e31 232 234 235 236 237 238 238 238 238 238 239 239 240 ol ol 242 24216642 16643 16644 16645 16646 OAM Alarm .. 16899 16900 16901 16903 16904 16905 16906 16907 16916 16917 16918 16919 16920 16921 16922 16923 16924 16925 16926 OSPF Alarm . 17408 17409 17410 a74in 17412 17413 17414 174s 17416 7417 i74is 17419 17420 1742117422 17423 17424 17425 17426 17427 17428 17429 RIP Alarm 17664 17666 17667 17670 17671 17672 17673 17676 17677 BGP Alarm... 17920 17921 17922 17923 17924 17925 17927 17928 17932 17934 17936 17938 17940 17941 17942 17943 17944 17945 17946 17947 17949 255 255 255 56 56 56 56 56 257 257 257 257 257 58 58 58 58 259 259 259 259 259 259 +60 +60 +60 +60 261 261 261 261 261 2162 2162 2162 2162 2162 2.63 2.63 2.6317950 17981 17952 17953 17984 17955 17956 17987 17958 17959 17960 17961 17962 17963 17964 DRP Alarm 18176 18177 1g1g0 isigi 1g182 18183 isis¢ isis 18186 1189 18190 isi91 1gi92 18193 18195 18196 TCP Alarm 18433 18434 18435 18436 18437 18438 18439 63 63 64 64 64 64 64 65 65 65 65 65 66 66 66 66 66 66 67 67 67 67 68 68 68 68 68 69 69 69 69 70 271 271 271 271 271 271 72 7218440 18450 18451 18452 18453 18455 18456 18457 18458 18459 18460 18461 18463 18464 UDP Alarm... 18560 18561 18562 18563 18564 IP Alarm... 18689 18691 18692 18720 18721 18722 18737 18738 18739 18740 18741 18742 18743 18744 18745 18752 18754 18784 18785 272 272 272 2.73 2.73 2.73 2.73 2.73 a T4 a T4 a T4 a T4 a T4 27S 27S 27S 27S 27S 27S 2.76 2.76 2.76 2.76 2.76 eT eT eT eT eT 2.78 2.78 2.78 2.78 2.78 279 279 279 279 279 +8018786 18787 18790 18791 18794 18832 18833 18834 18835 IGMP Alarm . 18944 18945 ARP Alarm 19712 19713 19714 19715 19716 19717 19720 IS-IS Alarm 19968 19969 19970 19972 19974 19975 19976 19977 19978 19979 19980 i991 19982 19983 RMON Alarm 20737 20746 20747 20748 80 80 80 80 81 81 82 82 83 83 83 84 84 84 84 84 85 85 85 85 86 86 86 86 87 87 87 87 87 88 88 88 88 88 89 90 90 90 90 9020757 20758 20759 20776 20793 URPF Alarm 21248 ACL Alarm .. 21762 21764 21773 21774 21775 21776 21777 VRRP Alarm 22016 MAC Alarm .. 22784 22785 22786 22787 22788 22789 22790 22792 22793 22794 22795 22796 22797 22798 Loop Detect 23296 DHCP Alarm 23808 23809 23810 23811 23812 91 91 91 91 91 2192 2192 2192 2192 2192 2192 2193 2193 2193 294 295 295 295 295 295 295 296 296 296 296 296 297 297 2198 2198 299 299 100 100 100 100 100 101 101 10223813 vosscsscssesseseeseeseeseesienieneiieinsasesessases 203 23814 vosscssesserseseeseeseesnesienensiiinssssessssasess 203 2381S vocsccscssesseseesceseessessnnetieeeeesessassasssnsesees LO4 23816 vosscssessessescesseseesseesetietietieesessassanssnsesees LO4 23817 vesscssesseeseseeeeesetsnenenieneiinsssessasee 20S 23818 sosscsscssesseseeeeeseeenesineniisssesasee 20S 23819 sessossessesseseeseeseessteienienieiieinssnsesssnsasess 206 23820 vossossesseeseseeseeseesnteietienietieinsssvsssssasess 206 2BB2L vesscssessesseseeseeseesseesenienietieiesssssssssssavess 207, 23822 vesscssessesseseeseeseeseesienetitiisessnssssssssasess 207, 23823 vocscssesserseseeseeseesnesimneniesassessasess 208 23824 vosscssessesseseeseeseesneeieneniisnssessases 208 MLD Alarm vcsssssssssosserseesersessensesssensetitiinsisesssssssssess 209 24064 vocscsscssesseseeseesetseteeeneniieenssnsnsssssaves 209 24065 vosscsscsscsseseeeeeeetsneseenieneieinsisssessssess 209 STP Alarm vssssssssssssssorseeseeseesensesssensetieinvisvsssenssssess 209 24320 vessossessesseseeseeseeeneeienieniieinsssssessssess 209 24821 vossossesserseseeseeseeeetsieneneienessvessavee LL 24322 vossossesseeseseeseeseesnteinensinsnvsessasee EL 24323 vosscssessessesenseeseeeetsieneniinsnsvensasees LL 24327 vessossesseeseseeseeseeseteimneniiesssssssasees EL LOCAL ACCOUNTING Alarm ....cssscssseenesvvevenvee ELL 24832 vosscsscsserseseeseeseeseeeeeneniensesvevsasees ELE LDP Alarm vsssssssssssssserseeseeseesensesnisnetevvevenvees ELE 25344 vocscsscsserseseeseeseeeneeeeneneieinsvvevavees ELE 25347 socsossessesseseeseeseesnesieneniieinsssvvsevsavees 212 25349 vosscssceseeseseeseeseessesieteniiesesssssvssssavees E12 2SBSL sosscssessesseseeseeseesneeeenenieinssvevevsavees LLB 25354 vossosscssesseseeseeseeseeeieneniensvvsvsavees LLB 2535S vosscssessesseseeseeseesnesinneneiinssvessevsavees LLB 25356 vessossessesseseeeeeseesneeisnienieiinssvevsevsavees LLB QSBS7 sessocseeseeseseeseesesssessntetveesessavsasssnsesees 214 LOVPN Alarm vosssssssssssseesseererserseesersensessesssessnineees 14 2SBS6 sessccsessessescescesessseesntietierseevessosvassansasees 214 QSBST sesscssessessescescessssseesetietveevessassasssnsesees 214 2SBSB vocsccsessessesceseeseesseesetetevsevessassonssnsasees 214 2SBS9 vocsccsessesseesesceseesseesstietivesvessavsssssnsavees 214 25863 vosscsscsseeseseeseeseeseenieneneiiisvvensavee ELS 25864 vossosscssesseseeseeseesnesieneneiessivenavee ELS ZESR Alarm .sssssscssssseseeseeserseesesnienieiieivsesenven ELS26368 26369 26370 26371 26372 26373 26374 26375 26376 TACACS Alarms 28160 28161 28162 28163 28164 28165 28166 28167 28168 28169 AAA Alarms 28418 28419 28421 28422 28423 28429 MIX Alarms.. 29952 29953 29954 29955 29956 29957 29958 29959 29960 BFD alarm .. 30208 30209 115 115 116 116 116 116 116 117 117 117 117 117 118 118 118 118 118 119 119 119 119 119 120 120 120 120 120 121 121 121 121 122 122 123 123 124 124 125 125 12630210 30212 30213 UDLD Alarm. 29696 29697 29698 29699 MUX Alarm .. 29440 ZESS Alarm . 32512 32513 32514 POE Alarm 30720 30721 ESM Alarm, 26385 EPON Alarm. 33280 33281 33282 33283 33284 33285 33286 33287 33288 33289 33290 33291 33292 33203 33204 33295 33296 33297 Command Configuration Error Prompt Messages .. 126 127 127 128 128 128 129 129 130 130 130 130 131 131 132 132 133 134 134 134 134 135 136 137 137 138 138 139 140 140 141 142, 142, 143 143 144 144 145Message Format Error Message Description 10. 1. 12. 13. 14. 1s. 16. vw. 18. as. 20... 21. 22.. 23... 24. 25... 26... 27. 28... 29. 30... 31... 33... 340. 35... 36... 37. 38. 39. 40. 41. 42.0 44. 100 101 102 103 104 147 147 147 147 147 148 148 148 148 148 149 149 149 149 149 150 150 150 150 150 151 151 151 151 151 151 152 152 152 152 152 153 153 153 153 154 154 154 154 154105 .... 106... 107... 108... 109... 110 .... 112... 201... 202 «0 203 «... 204 206 «... 207 ae 208 «... 209... 210 ae 211 oan 212 oe 213 on 214 oan 21S an 216 an 217 vee 218... 219 on 220 ae 221 on 222 an 223 an 224 oan 225 a 226 ae 227 ee 228 229 on 230 231 on 232 on 233 «0. 235 on. 154 155 155 155 155 155 155 156 156 156 156 156 157 157 157 157 157 158 158 158 158 158 159 159 159 159 159 160 160 160 160 160 160 161 161 161 161 161 162 162236 237 238 239 240 par 242 243 244 245 246 247 248 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 162 162 162 162 163 163 163 163 163 164 164 164 164 164 164 165 165 165 165 165 166 166 166 166 166 166 167 167 167 167 167 168 168 168 168 168 168 169 169 169277 ove 278 oan 279 cae 280 .... 284 .... 285 .... 288 .... 289 .... 290 nn 292 300 «... 303 .... 305 «... 306 «... 307 nn 308 .... 309... 1001... 1002... 1003... 1004... 1005... 1006... 1007... 1008... 1009... 1010... 1011... 1012... 1013... 1014... 1015... 1016... 1017... 1018... 1019... 1020... 1021... 1022... 1024... 169 169 170 170 170 170 170 1 1 1 1 1 172 172 172 172 172 173 173 173 173 173 173 174 174 174 174 174 175 175 175 175 175 176 176 176 176 176 176 w7177 177 177 177 177 178 178 178 178 178 .179 .179 .179 .179 .179 .179 180 180 180 180 180 181 181 181 181 181 181 182 182 182 182 182 183 183 183 183 183 183 184 1841074... 1080... 1081... 1082... 1083. 1500... 1501... 1502... 1503... 1504... 1505... 1700... 2001... 2002... 2003... 2004... 2005... 2006... 2007... 2008... 2009... 2010... 2011... 2012... 2013... 2014... 2015... 2016... 2017... 2018... 2019... 2020... 2021... 2022... 2023... 2024... 2025... 2026... 2027... 2028... 184 184 184 185 185 185 185 185 185 186 186 186 186 186 187 187 187 187 187 188 188 188 188 188 188 189 189 189 189 189 190 190 190 190 190 190 191 191 191 1912029 2030 2031 2032 2033 2034, 2035 2036 2037 2038 2039 2040 2041 2042 2043 2044, 2045 2046 2047 2048 2049 2050 2051 2052 2053 2054, 2055 2056 2057 2058 2059 2060 2200 2801 2802 2803 2804, 2805 2806 2807 191 191 192 192 192 192 192 193 193 193 193 193 194 194 194 194 194 194 195 195 195 195 195 195 196 196 196 196 196 197 197 197 197 197 198 198 198 198 198 1982808... 2809... 2810... 2811... 2812... 2813... 2814... 2815... 3001... 3002... 3003... 3004... 3005... 3006... 3007... 3008... 3009... 3010... 3011... 3012... 3013... 3014... 3015... 3016... 3017... 3018... 4001... 4002... 4003... 4004... 4005... 4006... 4007... 4008... 4009... 4010... 4011... 4012... 4013... 4014... 199 199 199 199 199 199 200 200 200 200 200 201 201 201 201 201 201 202 202 202 202 202 203 203 203 203 203 203 204 204 204 204 204 204 205 205 205 205 205 2054015 4016 4030 4031 4032 4033 4034, 4035 4036 4037 4038 4039 4040 4041 4042 4043 4044, 4045 4046 4047 4048 4049 4501 4502 4503 4504, 4508 4506 4507 4508 4509 4510 4511 4512 5001 5002 5003 5004. 5008 50065007... 6001... 6010... 6011... 6012... 6020... 6021... 6022... 6023... 6024... 6025... 6026... 6027... 6028... 6029... 6030... 6031... 6032... 6033... 6034... 6035... 6036... 6037... 6038... 6040... 6050... 6051... 6052... 6053... 6054... 6055... 6056... 6057... 6058... 6059... 6080... 6081... 6082... 6083... 6084... 213 213 213 214 214 214 214 214 215 215 215 215 215 215 216 216 216 216 216 216 217 217 217 217 217 217 218 218 218 218 218 219 219 219 219 219 220 220 220 2206085 6086 6087 6088 6089 6601 7001 7002 7003 7004. 7008 7006 7007 7008 7010 7011 7012 7020 7021 7022 7023 7024. 7030 7031 7032 7040 7041 7042 7050 7051 7052 7053 7061 7062 7063 7064. 7065 7066 7067 70687069... 7071... 7081... 7082... 7083... 7091... 8008... 8009... 8010... 8011... 8501... 8502... 8503... 8504... 8505... 8506... 8509... 8510... 8511... 8512... 8513... 8514... 8515... 8516... 8517... 8601... 8602... 8603... 8604... 8605... 8606... 8607... 8608... 8609... 8610... 8611... 8612... 8613... 8614... 8615... 227 227 227 227 228 228 228 228 228 228 229 229 229 229 229 229 230 230 230 230 230 231 231 231 231 231 231 232 232 232 232 232 233 233 233 233 233 233 234 2348616 8617 8618 8619 8620 8621 8622 8623 8624, 8625 8626 8701 8702 8703 8704, 8705 8706 8707 8708 8801 8802 8803 8804, 8805 8806 8901 8903 8904, 8908 8906 8907 8908 8909 8910 go11 8912 8913 8914, go1s 89168917... 8918... 8919... 8951... 8952... 8953... 8954... 8955... 8956... 9001... 9002... 9003... 9004... 9005... 9101... 9102... 9103... 9105... 9106... 9201... 9202... 9203... 9204... 9501... 9502... 9503... 9506... 9507... 9508... 9510... 9811... 9512... 9513... 9514... 9515... 9516... 9517... 9518... 9519... 9520... 241 241 241 242 242 242 242 242 243 243 243 243 243 243 244 244 244 244 244 244 245 245 245 245 245 246 246 246 246 246 247 247 247 247 247 247 248 248 248 2489521 9522 9523 9601 9602 9603 9604. 9605 9606 9607 12401 12402 12403 12404 12405 12406 12407 12409 12410 a24i 12420 12421 12422 12423 12424 12425 12426 12427 12428 12429 12430 12431 12432 12433 30201 30202 30203 30204 30205 3020630207... 30208. TRAP Messages TRAP Message Explanation....... System TRAP Message . coldStart ..... warm Start authenticationFailure. linkup . inkDOWN sssscseeeesssee Alarm TRAP Message.... Hardware Alarm Trap Software Alarm Trap RMON TRAP Message risingAlarm Trap fallingalarm Trap .... OSPF TRAP Message .... ospfVirtlfStateChange ospfNbrStateChange ospfVirtNbrStateChange ospflfConfigError ...... ospfVirtlfConfigérror ospflfauthFailure ...... ospfVirtlfauthFailure ospflfRxBadPacket ospfVirtlfRxBadPacket ospffxRetransmit ..... ospfVirtlfTxRetransmit ........ ospforiginateLsa....... ospfMaxAgeLsa OSpfLsdbOVErAOW .sscsssseeeen ospfLsdbApproachingOverflow ospflfStateChange BGP TRAP Message bgpEstablished - bgpBackwardTransition........ DHCP TRAP Message... online . offline . ce VRRP TRAP Message ..... 256 256 257 257 257 258 258 258 259 259 259 260 261 261 261 262 262 262 263 264 264 265 266 266 267 267 268 269 269 270 270 27. 27. 27. 27. 272 272 272 273vrrpTrapAuthFailure vrrpTrapNewMaster.. IPV6TRAP Information ipvelfStateChange... POE TRAP Information.. pethPsePortonofiNotification pethMainPowerUsageOnNotification......... pethMainPowerUsageOfiNotification ........About This Manual Purpose Intended Audience What Is in This Manual ‘The manual is ZXR10 Router/Ethernet Switch Message Manual and suited for following equipments. = ZXR10 GAR universal access router (shorted as ZXR10 GAR) = ZXR10 GER universal high-performance router (shorted as ZxR10 GER) = ZXR10 T646/T128 carrier class high-end router (shorted as ZXR10 T64E/T128) = ZXR10 3900/3200 series intelligent Ethernet switches (shorted as ZXR10 3900/3200) = ZXR10 5900/5200 series all gigabit-port intelligent routing switch (shorted as ZXR10 5900/5200) = ZXR10 T160G/T64G/T40G 10G MPLS routing switch (shorted as ZXR10 T160G/T64G/T40G) = ZXR10 8900 series 10G MPLS routing switch (shorted as ZXR10 8900) ‘The manual content is based on unified ZXROS platform and suited to all equipments if with no special note or described as 2XR10. In the manual, the contents describing router are also applied to the switches with route function This manuals intended for engineers and technicians who perform operation activities on ZXR10 Router/Ethernet Switch This manual describes alarm messages that may appear during the operation of ZXR10 router/Ethernet switch, command configura- tion error prompt messages that may appear during configuration, as well as TRAP messages sent by the router. This manual contains the following chapters: Chapter Summary Chapter 1, Alarm Overview This chapter describes the alarm message format on ZXR10 Router/Ethemet Switch Chapter 2, Alarm Message This chapter describes the alarm messages appeared on ZXR10 data product, induding hardware alarm and software alarm. Chapter 3, Command Configuration Error Prompt Messages This chapter describes the error prompt message appeared during command configuration, Chapter 4, TRAP Message This chapter describes all TRAP messages sent by system, Confidential and Proprietary Information of ZTE CORPORATION2xR10 Alarm Handling Manual TIER This page is intentionally blank, ii Confidential and Proprietary Information of ZTE CORPORATIONChapter 1 Alarm Overview Table of Contents OVEFVIEW vvocsesssssseseeseee Alarm Glossry Overview svssssenn. Message Format Description ....... Overview The alarm management is responsible for gathering the malfunc- tion and the event information which appears in the system run- ning and the handling of traffic process. Real-time display or stor- lage into the database is executed in form of alarm or notice on the user-oriented alarm monitoring platform. It also provided the in= terface direct-viewing monitoring or the historical inquiry method to reflect the current or the past system running status and the handling of traffic process, All of these helped the maintenance personnel to do the troubleshooting and take preventive mea~ sures, so that the system and the service restores normal as soon as possible. Alarm Glossry Overview Message No. Message No. is also named alarm code. It is the unique identi~ fication to distinguish alarms. It includes foreground alarm and backgroud alarm. The foreground alarm code is a fixed value de- fined by macro for distinguishing alarms, Because alarm and the corresponding recovery use the same alarm code, only alarm code and notice code need to be defined, The alarm source provides the macro name in the alarm code identifier macro column. 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 STE CORPORATION 12XR40 Alarm Handling Manual TIE 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. Severity 3: critical messages CRITICAL. Emergency condition appears Severity 4: error messages ERRORS. Error condition appears Severity S: warning messages WARNINGS. The system prompts that warnings appear. Severity 6: notification messages NOTIFICATIONS. The normal but significant event information that the system notifies to each part and records Severity 7: informational messages INFORMATIONAL. It is only an informational message Severity 8: debugging messages DEBUGGING. It is the re- spondse information type when the administrator debugs the system or network ‘Alarm level includes the default and actual level. The default level is the original alarm level and it is fixed. Users can not modify it, The actual alarm level is the one used in the process of device running which is equal to the default level. Users can modify it using the command alarm level-change . Only alarm levels 4-8 can be modified Alarm Recovery Alarm recovery includes "available" and "unavailable". "available" means that a prompt will appear when this alarm is deleted "unavailable" means that there is no prompt when this alarm is deleted Alarm Type Alarm type includes the following six categories "Communicationalarm" "ProcessingErrorAlarm® "QoSalarm" "Equipm entalarm" "Environm entalalarm" "omsalarm" 2 Confidential and Proprietary Information of ZTE CORPORATIONTIER Chapter 1 Alarm Overview NM Level NM level includes level 1, level 2, level 3, level 4 and level 5. The meanings for each level are as follows. Level 1: critical Level 2: major Level 3: minor Level 4: dear Level 5: informational Cause 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: L The hardware or device malfunction. Single board malfunction ii, Other hardware malfunction, such as system power mal- funcrion, fan malfunction, flash card malfunction and so on. ili. Hardware can not satisfy needs. For example, current hardware such as single board, CPU and the memory can not satisfy the increasing needs Software malfunction, It may be the software BUG or the fail- ure caused by the software upgrade. Environment alarm. For example, i, The smooth running of the system has a strict requirment on the environment, If the temprature or the humidity can not satisfy the requirment, alarm occurs. ji, Natural disaster and the accidental incident can also gen- erate alarms. For example, lightening, fire or earthquake The configuration error or the improper setup. i. The setup problem: the interface setup between devices, the system privilege, password, file and catolog setup, ii, The configuration can not satisfy the system requirments: the system capability and capacity decrease caused by con- figuration error. Especially if the alarm threshold is set by users, proper configuration is strongly required. ‘The malfunction on the other end device also generates alarms. ‘Confidential and Proprietary Information of STE CORPORATION 32XR40 Alarm Handling Manual TIE Related Alarms If there is some alarms that are related to this one, such as the source alarm that generates this one and the alarms caused by this one, please list them Recommended Operations This section lists the recommended operations that can remove the alarms 1. The general analysis methods for the alarms are as follows. i, Read the alarm message, information description carefully and refer to the related content in this manual ii, Check whether the network connection is normal using net- work commands such as ping, telnet, netstat, ipconfig /if- config, route, trace/tracert and so on. ili. View the related data configuration directly to check whether there is error, missed or unreasonable configura~ tions. iv. For more difficult problems, analyse them with the net- work protocol analysis software "sniffer" v. For possible hardware malfunction, replace this hardware with the same available hardware to help the manager to determine whether the malfunction is from the software or the hardware. 2, The general disposal methods for the alarms are as follows i, For hardware or device malfunction, contact with ZTE ser- vice staff to replace it. For malfunctions such as "hardware dissatisfactory", add the hardware or replace the low ca~ pacity parts. ii, For software or the system malfunctions, upgrade or down- grade the software version, Backup the configuration be- fore version upgrading. ili, For alarms caused by the environment, please check and resolve the problems in time according to alarm failure and alarm message. Avoide or reduce the direct or physical damage for the device caused by the enviranment, iv. For system setup and configuration problems, check where the malfunction is and modify the configuration . For alarms caused by error input commands, please view the online command "help" or refer to related manual and execute it after inputting this command again v. For alarms caused by the other end, inform the other end of the displayed alarm message and assist in resolving this problem. 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- 4 Confidential and Proprietary Information of TE CORPORATIONTIER Chapter 1 Alarm Overview tomer support center at 800-830-1118(for free) , 400-830- 1118(modename for free) and 0711-65000(military network). 4. The subsequent steps to dispose the alarms are as follows i. Check whether the alarm is removed. The methods in- clude: the alarm message does not appear or the normal system alarm appears; reboot the single board or this mad= ule; the service recovers to normal ji, Remember to record the detailed "alarm processing log" which includes alarm phenomenon, alarm cause and the disposal methods. The ‘alarm processing log" is convenient for resolving the similar problems Alarm Prototype Description It is the alarm instance that is the display information on the rack when the alarm occurs. This is shown by the command show logging alarm. Alarm Description Alarm description is the explanation for the rack alarms. It de~ scribes the malfunction on the device. Supported device type Supported device type lists all the device types that supports this alarm Appendix Description Appendix Description list all the points that should pay attention to. for example, explain that there is difference of this alarm between versions and devices. Message Format Description The alarm message format is as follows. alarm {occurred | cleared} sent by ‘Confidential and Proprietary Information of STE CORPORATION 52XR40 Alarm Handling Manual TIE The following table describes each field of an alarm message. Field Description Alarm generation time number Alarm code occurred | cleared Alarm status: “occurred” indicates that an alarm has occurred; while “cleared” indicates that the alarm has been cleared (it is only applied to hardware alarms) type Alarm type, which is identified with %, Alarm message description sender Alarm message sender O note: 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 = Hardware alarms can be divided into environment alarms, board alarms and port alarms. = Software alarms may be separated as more sub-types as ROS, DATABASE, OSPF, RIP, BGP, DRP, TCP, UDP, IP, TELNET, ARP, ISIS, RMON, ACL, URPF, VRRP, PPP, VIRUS-SCAM and MAC. Alarm message examples are as follows. 1. Hardware alarm » Environment alarm (alarm occurred) 1S: 41: 22 09/11/2003 UTC alarm 6 occurred. %ENVI- RONMENT% Rack fan 1 wrong sent by UPC(MPU) 1 » Environment alarm (alarm cleared) 15: 51: 22 09/11/2003 UTC alarm 6 deared. 9%ENVIRON- MENT% Rack fan 1 normal sent by UPC(MPU) 1 » Line board alarm (alarm occurred) 10: 13: 36 09/15/2003 UTC alarm 279 occurred. %Board% Remove Interface from slot 3 sent by SMP 1 » Line board alarm (alarm deared) 10: 13: $1 09/15/2003 UTC alarm 279 cleared. %Board% ‘Add Interface at slot 3 sent by SMP 1 » Port alarm (alarm occurred) 5 Confidential and Proprietary Information of ZTE CORPORATIONTIER Chapter 1 Alarm Overview 10: 12: §7_ 09/15/2003 UTC alarm $12 occurred. ‘%PORT% Port Down on fei_S/6 sent by SMP 1 Port alarm (alarm cleared) 10: 12: 59 09/15/2003 UTC alarm 512 cleared. %PORT% Port Up on fei_5/6 sent by SMP 1 2. Software alarm BGP alarm 10: 12: 88 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 72xR10 Alarm Handling Manual TIER This page is intentionally blank, 8 Confidential and Proprietary Information of 2TE CORPORATIONChapter 2 Alarm Message Message No. Default Severity Level Alarm Recovery Alarm Type NM Level Cause Related Alarms Recommended ‘Operations Alarm Prototype Description Table of Contents Hardware alarm ...sosssssessesseseseesensienentiersssvsse 9 Software Alarm ...cscsscssessesseseeseeseesseiiensneneseseeee 30 Hardware alarm Environment Alarm 63 Available Environmental Alarm 4 Board temperature is lower than the set lower threshold. ‘The command used to set threshold for equipment temperature is: temper-threshold UPC master local lowthreshold -20 first-high- threshold 55 second-highthreshald 90 64, 65 Increase environmental temperature of equipment if necessary. Alarm Occurred %s Panel 9d Current local temperature is %d'C/%dF,under the low threshold(%d'C/% dF) Alarm Cleared %s Panel %d Current local temperature is %d°C/%dF,exceeds the low threshald(%d'C/% dF) The first 9s 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 STE CORPORATION 52XR40 Alarm Handling Manual TIE al arm Description Supported Devices Appendix Specification Message No. Default Severity Level Alarm Recovery Alarm Type NM Level Cause Related Alarms Recommended Operations Alarm Prototype Description board; the third %d is the Fahrenheit temperature of board; the fourth %d is the centigrade temperature of the set threshold and the fifth 9%d is the Fahrenheit temperature of the set threshold. Alarm Occurred %s Current local temperature is %d'C/9%dF,under the low thresh- old(96d'C /%6 dF) Alarm Cleared %s Current local temperature is %d'C/%dF, exceeds the low threshold(%d'C/% dF) The first %s is the board type and is fixed to BIC board. There is no panel number on BIC board, so the display format is different from other board: the first %d is the centigrade temperature of the board, the second %d is the Fahrenheit temperature of board, the third 9d is the centigrade temperature of the set threshold and the fourth %d is the Fahrenheit temperature of the set threshold ‘An alarm 63 level § occurred at 01:58:00 01/28/2001 UTC sent by UPC(MPU) 2 %ENVIRONMEN 1% SFC Panel 1 Current local tem= perature is 33°C/91F,under the low threshald(40°C/104F) ‘An alarm 63 level § cleared at 01:58:20 01/28/2001 UTC sent by UPC(MPU) 2 %ENVIRONMENT% SFC Panel 1 Current local tem= perature is 33°C/91F,exceeds the low threshold(-10°C/13F) Board temperature is lower than the set lower threshold 7128/T64,T600/T1200 NA, 64 64 5 Available Environmental Alarm 4 Board temperature is higher than the set first-high temperature threshold. The command used to set threshold for equipm ent temperature is: temper-threshold UPC master local lowthreshold -20 first-high- threshold 55 second-highthreshold 90 63, 65 Decrease board temperature if necessary. Decrease the environ- ment temperature of the equipment by the fan heat dissipation. Alarm Occurred %s Panel %d Current local temperature is %d'C/%dF,exceeds the first high threshold(%d'C/%dF) Alarm Cleared io ‘Confidential and Proprietary Information of ZTE CORPORATIONTIER Alarm Description Supported Devices Appendix Specification Message No. Default Severity Level Alarm Recovery Alarm Type NM Level Cause Related Alarms Recommended ‘Operations Chapter 2 Alarm Message %s Panel 96d Current local temperature is %d'C/%dF,under the first high threshold(%d'C/%dF) The first 9s is the board type, the first %d is the panel number of the board, the second %d is the centigrade temperature of the board, the third %d is the Fahrenheit temperature of board, the fourth %d is the centigrade temperature of the set threshold and the fifth %d is the Fahrenheit temperature of the set threshold. Alarm Occurred %s Current local temperature is %d'C/%dF,exceeds the first high threshold(%d'C /%dF) Alarm Cleared %s Current local temperature is %d'C/%dF,under the first high threshold(%d°C/% dF) The first %s is the board type and is fixed to BIC board. There is no panel number on BIC board, so the display format is different from other board: the first 9d is the centigrade temperature of the board, the second 9d is the Fahrenheit temperature of board, the third 96d is the centigrade temperature of the set threshold and the fourth 96d is the Fahrenheit temperature of the set threshold. An alarm 64 level § occurred at 01:58:30 01/28/2001 UTC sent by UPC(MPU) 2 %ENVIRONMENT% SFC Panel 1 Current local tem= perature is 33°C/91F,exceeds the first high threshold(30°C/86F) An alarm 64 level 5 cleared at 01:59:20 01/28/2001 UTC sent by UPC(MPU) 2 9ENVIRONMENT% SFC Panel 1 Current local tem perature is 33'C/91F,under the first high threshold(5S'C/131F) Board temperature is higher than the set first-high temperature threshold. 7128/T64,T600/T1200 NAL 65 65 Available Environmental Alarm 3 Board temperature is higher than the set second-high temperature threshold. ‘The command used to set threshold for equipment temperature is: temper-threshold UPC master local lowthreshold -20 first-high- threshold 55 second-highthreshold 90 63, 64 Decrease board temperature if necessary, Decrease the environ- 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 11.2XR40 Alarm Handling Manual TIE al Alarm Prototype Description arm Description Supported Devices Appendix Specification Message No. Default Severity Alarm Recovery Alarm Type NM Level Cause Recommended Operations Alarm Occurred %s Panel %d Current local temperature is %d'C/%dF,exceeds the second high threshold(%d°C/%dF) Alarm Cleared %s Panel 96d Current local temperature is %d'C/%dF,under the second high threshald(%d°C/%dF) The first %s is the board type, the first 9d is the panel number of the board, the second %d is the centigrade temperature of the board, the third 9%d is the Fahrenheit temperature of board, the fourth %d is the centigrade temperature of the set threshold and the fifth 9%d is the Fahrenheit temperature of the set threshold. Alarm Occurred %s Current local temperature is %d'C/%dF,exceeds the second high threshold(%d'C/%dF) Alarm Cleared %s Current local temperature is %d'C/%dF,under the second high threshold(%d'C/%dF) The first %s is the board type and is fixed to BIC board. There is no panel number on BIC board, so the display format is different from other board: the first %d is the centigrade temperature of the board, the second %d is the Fahrenheit temperature of board, the third 9d is the centigrade temperature of the set threshold and the fourth %d is the Fahrenheit temperature of the set threshold ‘An alarm 65 level § occurred at 01:58:40 01/28/2001 UTC sent by UPC(MPU) 2 %ENVIRONMEN T% SFC Panel 1 Current local tem perature is 33'C/91F,exceeds the second high threshold(32'C/89F) ‘An alarm 65 level § cleared at 01:58:50 01/28/2001 UTC sent by UPC(MPU) 2 %ENVIRONMENT% SFC Panel 1 Current local tem perature is 33°C/91F,under the second high threshold(30'C/86F) Board temperature is higher than the set second-high temperature threshold. 7128/T64,T600/T1200 NA, 66 66 5 Available Environmental Alarm 4 The CPU utilization exceeds the set memory utilization threshold. The command used to set threshold for memory utilization is (un- der environmental configuration mode): memory-threshold. Use the command show process to view the CPU utilization and analyzse whether it is normal or not. 2B ‘Confidential and Proprietary Information of ZTE CORPORATIONTIER Alarm Prototype Description Alarm Description Supported Devices Appendix Specification Message No. Default Severity Level Alarm Recovery Alarm Type NM Level Cause Related Alarms Recommended ‘Operations Alarm Prototype Description Chapter 2 Alarm Message Alarm Occurred %5(M) panel 96d exceeds memory rate is: %3.3f%% under the alarm threshold is %d%% %5(S) panel %d exceeds memory rate is: %3.3f%% under the alarm threshold is %d%% Alarm Cleared %5(M) panel %d current memory rate is: %3.31%9% under the alarm threshold is %4%% %5(S) panel %d current memory rate is: %3.3f%% under the alarm threshold is %d%% ‘The first 95 is CPU type, the first %d is CPU SlotNo, the first 96fis the current CPU utilization and the second %d is the set memory utilization threshold. An alarm 66 level § occurred at 01:47:50 01/28/2001 UTC sent by UPC(MPU) 2 %ENVIRONMENT% SP(M) panel 1 current memory rate is: 40.562% exceeds the alarm threshold is 2% An alarm 66 level 5 cleared at 01:48:20 01/28/2001 UTC sent by UPC(MPU) 2 9ENVIRONMENT% RP(M) panel 2 current memory rate is: 40.084% under the alarm threshold is 60% CPU utilization exceeds the set memory utilization threshold. It is 60% by default. 7128/T64,T600/T1200 NAL 67 67 Available Environmental Alarm 4 ‘The rem ote temperature is lower than the set remote lower thresh- old of the board ‘The command used to set threshold for equipment temperature: temper-threshold UPC master local lowthreshold -20 first-high- threshold 55 second-highthreshald 90. 68, 69 Increase the environment temperature of the equipment if neces- sary. Alarm Occurred %s Panel %d Current remote temperature is %d'C/%dF,under the low threshold(%d'C/% dF) Alarm Cleared %s Panel %d Current remote temperature is %d°C/9 dF exceeds the low threshold(%d'C/%dF) ‘Confidential and Proprietary Information of ZTE CORPORATION 132XR40 Alarm Handling Manual TIE al arm Description Supported Devices Appendix Specification Message No. Default Severity Level Alarm Recovery Alarm Type NM Level Cause Related Alarms Recommended Operations Alarm Prototype Description The first %s is the board type, the first 9d is the panel number of the board, the second %d is the centigrade temperature of the board, the third 9%d is the Fahrenheit temperature of board, the fourth %d is the centigrade temperature of the set threshold and the fifth 9%d is the Fahrenheit temperature of the set threshold. Alarm Occurred %s Current remote temperature is %d'C/%dF,under the low threshold(%d'C /%dF) Alarm Cleared %s Current remote temperature is %d'C/%dF,exceeds the low threshold(%d'C /% dF) The first %s is the board type and is fixed to BIC board. There is no panel number on BIC board, so the display format is different from other board: the first %d is the centigrade temperature of the board, the second %d is the Fahrenheit temperature of board, the third 9d is the centigrade temperature of the set threshold and the fourth %d is the Fahrenheit temperature of the set threshold ‘An alarm 67 level S occurred at 02:01:20 01/28/2001 UTC sent by UPC(MPU) 2 %ENVIRONMENT% SFC Panel 1 Current remote temperature is 51°C/123F, under the low threshold(56'C/132F) ‘An alarm 67 level 5 cleared at 02:01:30 01/28/2001 UTC sent by UPC(MPU) 2 %ENVIRONMENT% SFC Panel 1 Current remote temperature is 51'C/123F, exceeds the low threshald(-20'C/-4F) ‘The remote temperature is lower than the set remote lower thresh- old of the board 7128/T64, T600/T1200 NA, 68 68 5 Available Environmental Alarm 4 ‘The remote temperature is higher than the set remote first-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. 67, 69 Decrease the board temperature if necessary. Decrease the envi- ronment tem perature of the equipment by the fan heat dissipation Alarm Occurred %s Panel %d Current remote temperature is %d'C/%dF,exceeds the first high threshold(%d'C/96dF) a ‘Confidential and Proprietary Information of ZTE CORPORATIONTIER Alarm Description Supported Devices Appendix Specification Message No. Default Severity Level Alarm Recovery Alarm Type NM Level Cause Related Alarms Chapter 2 Alarm Message Alarm Cleared %s Panel %d Current remote temperature is %d'C/%dF,under the first high threshold(%d°C/%dF) The first 9s is the board type, the first %d is the panel number of the board, the second %d is the centigrade temperature of the board, the third %d is the Fahrenheit temperature of board, the fourth %d is the centigrade temperature of the set threshold and the fifth %d is the Fahrenheit temperature of the set threshold. Alarm Occurred %s Current remote temperature is %d'C/%dF,exceeds the first high threshold(% dc/% dF) Alarm Cleared %s Current remote temperature is 9%d'C/%dFunder the first high threshold(%d°C/% dF) The first %s is the board type and is fixed to BIC board. There is no panel number on BIC board, so the display format is different from other board: the first 9d is the centigrade temperature of the board, the second 9d is the Fahrenheit temperature of board, the third 96d is the centigrade temperature of the set threshold and the fourth 96d is the Fahrenheit temperature of the set threshold. An alarm 68 level 5 occurred at 02:01:50 01/28/2001 UTC sent by UPC(MPU) 2 9ENVIRONMENT% SFC Panel 1 Current remote tem perature is 51°C/123F,exceeds the first high threshold(40°C/104F) An alarm 68 level 5 cleared at 02:02: 10 01/28/2001 UTC sent by UPC(MPU) 2 9ENVIRONMENT% SFC Panel 1 Current remote tem= perature is 51°C/123F,under the first high threshold(S3°C/127F) ‘The remote temperature is higher than the set remote first-high threshold of the board, 7128/T64,T600/T1200 NAL 69 69 Available Environmental Alarm 3 ‘The remote temperature is higher than the set rem ote 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-highthreshald 90. 67, 68 ‘Confidential and Proprietary Information of ZTE CORPORATION 152XR40 Alarm Handling Manual TIE Recommended Operations Alarm Prototype Description Alarm Description Supported Devices Appendix Specification Message No. Default Severity Level Alarm Recovery Alarm Type NM Level Decrease the board temperature if necessary. Decrease the envi- ronment tem perature of the equipment by the fan heat dissipation If the temperature is too high, stop using the board Alarm Occurred %s Panel %d Current remote temperature is %d'C/%dF,exceeds the second high threshold(%d'C/%dF) Alarm Cleared %s Panel %d Current remote temperature is %d'C/%dF,under the second high threshald(%d°C/%dF) The first %s is the board type, the first 9d is the panel number of the board, the second %d is the centigrade temperature of the board, the third 9%d is the Fahrenheit temperature of board, the fourth %d is the centigrade temperature of the set threshold and the fifth 9%d is the Fahrenheit temperature of the set threshold. Alarm Occurred %s Current rem ote temperature is %d'C/%dF,exceeds the second high threshold(%d'C/%dF) Alarm Cleared %s Current remote temperature is %d'C/%dF,under the second high threshold(%d'C/%dF) The first %s is the board type and is fixed to BIC board. There is no panel number on BIC board, so the display format is different from other board: the first %d is the centigrade temperature of the board, the second %d is the Fahrenheit temperature of board, the third 9d is the centigrade temperature of the set threshold and the fourth %d is the Fahrenheit temperature of the set threshold ‘An alarm 69 level S occurred at 02:02:40 01/28/2001 UTC sent by UPC(MPU) 2 %ENVIRONMENT% SFC Panel 1 Current remote temperature is 51°C/123F,exceeds the second high thresh~ old(S0°C/122F) An alarm 69 level § deared at 02:02:50 01/28/2001 UTC sent by UPC(MPU) 2 %ENVIRONMENT% SFC Panel 1 Current remote temperature is 51°C/123F,under the second high thresh- old(100°C/212F) ‘The remote temperature is higher than the set remote second-high threshold of the board, 7128/T64, T600/T1200 NA, 73 73 5 Available Environmental Alarm 4 16 Confidential and Proprietary Information of ZTE CORPORATIONTIER Cause Influence Recommended ‘Operations Alarm Prototype Description Alarm Description Supported Devices Appendix Specification Message No. Default Severity Level Alarm Recovery Alarm Type NM Level Cause Influence Recommended ‘Operations Alarm Prototype Description Chapter 2 Alarm Message ‘The rack temperature is higher than the set single high threshold. This leads to the abnormal working of the switch Lower the environment temperature of the rack by using fan heat dissipation’ Alarm occured Current temperature is %dC/%dF,exceeds the _thresh~ o1d(%d¢/%d) Alarm deared Current temperature is 9%dC/%6dF,under the threshold(%dC/%dF) The first %d is the environment Centigrade degree; the second %d is the Fahrenheit degree; the third 9d is the environment Centigrade degree of the set threshold; the fourth 9d is the envi- ronment Fahrenheit degree of the set threshold Alarm occured 16:20:31 06/26/2008 UTC alarm 73 occurred %ENVIRON- MENT% Current temperature is 90C/194F,exceeds the thresh- old(80C/176F) Alarm deared 16:22:11 06/26/2008 UTC alarm 73 cleared %ENVIRONMENT% Current temperature is 80C/176F,under the threshold(90C/194F) ‘The rack temperature is higher than the set single high threshold. ZXR10 3900/3200, 5900/5200 and G-series switch Na. 74 14 Available Environmental Alarm 3 ‘The power works abnormally. This leads to the abnormal working of the switch Check whether the power input is normal and whether the rack output is normal; whether the power module is plugged correctly; whether the connection is OK. Alarm occured Power%d do not work! Alarm deared Powerdd restart! % d: the power serial number. Multiple power states can be dis- played simultaneously. UAS10800E: ‘Confidential and Proprietary Information of ETE CORPORATION 172XR40 Alarm Handling Manual TIE Alarm Description Supported Devices Appendix Specification Message No. Default Severity Level Alarm Recovery Alarm Type NM Level Cause Influence Recommended Operations Alarm Prototype Description Current Power Module %d is removed %d: power module number Alarm cleared Current Power work normal % d: the power serial number. Multiple power states can be dis- played simultaneously, Example: Alarm occured 15:20:31 06/26/2008 UTC alarm 74 occurred %ENVIRONMENT9®. Power do not work! Alarm cleared 15:21:3 06/26/2008 UTC alarm 74 occurred %ENVIRONMENT9® Power1 restart! The power works abnormally. ZXR10 3900/3200, 5900/5200, G-series switch and Zx- UAS-UAS10600, UAS10800E. NA, 75 75 Available Environmental Alarm 4 The fan works abnormally. This leads to the abnormal working of the switch Check whether the power input and output of the fan is normal; whether the fans are plugged correctly; whether the fuse is OK Alarm occured Fan%d do not work! Alarm cleared: Fanded restart! % d: the power serial number. Multiple power states can be dis- played simultaneously, UAS10800E: Current Trunk 9s Fan fail to work %s: Top or Bottom Alarm cleared Current Cabinet/Trunk Fan work normal %s: Top or Bottom 18 Confidential and Proprietary Information of ZTE CORPORATIONTIER Alarm Description Supported Devices Appendix Specification Message No. Default Severity Level Alarm Recovery Alarm Type NM Level Cause Influence Related Alarms Recommended ‘Operations Alarm Prototype Description Chapter 2 Alarm Message Example: Alarm occured 15:10:11 06/26/2008 UTC alarm 75 occurred %ENVIRONMENT% Fan1 do not work! Alarm deared 15:13:13 06/26/2008 UTC alarm 75 occurred %ENVIRONMENT% Fanl restart! The fan works abnormally. ZXR10 3900/3200, 5900/5200, G-series switch and Zx- UAS-UAS10600, UAS10800E. NAL 79 79 6 Available Equipment Alarm 1 Power malfunction. This leads to the abnormal working of the board. 76, 77 Wait for our customer service personnel to deal with the power model malfunction. Alarm occurred Power errorreason%s Alarm eared Power recover: %s %s: the cause for this malfunction The content of %s is = New rack alarm(only be applied for new rack) i, Current Power Module 1 fail to work 15:02:38 08/14/2008 UTC alarm 79 occurred Power er- ror, reason: Current Power Module 1 fail to wark sent by UPC(MPU) ii, 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 wark sent by UPC(MPU) 1 iii, Current Power Module 3 fail to work ‘Confidential and Proprietary Information of ZTE CORPORATION 132XR40 Alarm Handling Manual TIE Alarm Description Supported Devices Appendix Specification Message No. Default Severity Level Alarm Recovery Alarm Type NM Level Cause Influence Recommended Operations 15:06:08 08/14/2008 UTC alarm 79 occurred Power er- ror, reason: Current Power Module 3 fail to work sent by UPC(MPU) 1 Old rack alarm i. Current Power Commutate Module 1 fail to work 15:07:38 08/14/2008 UTC alarm 79 occurred Power error, reason: Current Power Commutate Module 1 fail to work sent by UPC(MPU) 1 ii, Current Power Commutate Module 2 fail to work 15:46:02 08/14/2008 UTC alarm 79 occurred Power error, reason: Current Power Commutate Module 2 fail to work sent by UPC(MPU) 1 15:46:02 08/14/2008 UTC alarm 79 occurred Power error, reason: Current Power Commutate Module 2 fail to work’ sent by UPC(MPU) 1 ili. Current Power Commutate Module 3 fail to work 15:47:32 08/14/2008 UTC alarm 79 occurred Power error, reason: Current Power Commutate Module 3 fail to work sent by UPC(MPU)1 General alarm: i. The power data line isn't plugged into the bic board 14:32:38 08/14/2008 UTC alarm 79 occurred Power error, reason: The power data line isn't plugged into the bic board sent by UPC(MPU) 1 ii, Current Power work normal 15:05:08 08/14/2008 UTC alarm 79 cleared Power recover Current Power work normal sent by UPC(MPU) 1 Power malfunction ZXR10 T64E, T128, T600, T1200 ZXR10 T64, 7128 adopts old rack; ZXR10 T600, T1200 adopts new rack 80 80 Available Equipment Alarm Fan malfunction This may cause heat dissipation malfunction on the rack and the tem| wait perature increment on each single board. it for our customer service personnel to deal with the fan mal- function, 20 ‘Confidential and Proprietary Information of ZTE CORPORATIONTIER Alarm Prototype Description Chapter 2 Alarm Message Alarm Occurred Fan errorreason%s Alarm Recovered Fan recover: %s %s cause ‘The 3 types of new rack alarms are as follows( only for new rack). i, The fan data line isn't plugged into the BIC board. If none of the 3 power modules are working, it implies that the power and the fan are not plugged well 14:51:08 08/14/2008 UTC alarm 80 occurred Fan error, reason: The fan data line isn't plugged into the bic board sent by UPC(MPU) 1 ii, Current Trunk Top Fan fail to work 14:44:38 08/14/2008 UTC alarm 80 occurred Fan er- ror, reason: Current Trunk Top Fan fail to work sent by UPC(MPU) 1 iii, Current Trunk Bottom Fan fail to work 15:51:32 08/14/2008 UTC alarm 80 occurred Fan error, reason: Current Trunk Bottom Fan fail to work sent by UPC(MPU) 1 The 4 types of old rack alarms are as follows(only for old rack). i, The fan data line isn't plugged into the BIC board. If all the fans are not working, it implies that the line of the fan is not plugged well 14:51:08 08/14/2008 UTC alarm 80 occurred Fan error, reason: The fan data line isn't plugged into the bic board sent by UPC(MPU) 1 ii. Current Trunk Top Fan Num ....fail to work (One or two of the 8 fans work abnormally. The abnormal fan number is behind Num. For example, Num 3 5. 14:53:08 08/14/2008 UTC alarm 80 occurred Fan error, reason: Current Trunk Top Fan Num 3 4 7 8 fail to work sent by UPC(MPU) 1 iii, Current Trunk Bottom Fan Num..... fail to work (One or two of the 8 fans work abnormally. The abnormal fan number is behind Num. For example, Num 3 5. 14:55:08 08/14/2008 UTC alarm 80 occurred Fan error, reason: Current Trunk Bottom Fan Num 3 47 8 fail to work sent by UPC(MPU) 1 iv. Current Cabinet Top Fan Num .....fail to work (One or two of the 6 fans work abnormally. The abnormal fan number is behind 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 2.2XR40 Alarm Handling Manual TIE = Corrent alarm (Both old and new racks can generate this alarm) is as follows: i, Fan recover: Current Cabinet/Trunk Fan work normal 14:58:38 08/14/2008 UTC alarm 80 cleared Fan recorver Current Cabinet/Trunk Fan work normal sent by UPC(MPU) 1 Alarm Description Fan malfunction. Supported Devices 1128/T64,7600/T1200 spcigpendix T64, 7128 adopts old rack; 7600, T1200 adopts new rack. pecification Board Alarms MessageNo. 279 Default Severity 3 Level Cause The line board is offline Recommended Check whether the line board is unplugged normally, or the board Operations offline is caused by abnormal line card. 293 MessageNo. 293 Default Severity 3 Level Cause When the active board and standby board change over, the Card Type reported by the lower layer BSP is not in the valid range. Its value is abnormity. Recommended This alarm is used for the location of the malfuction. It has no Operations influence on the operation or the utility. 299 MessageNo. 299 Default Severity Level Alarm Recovery Available Alarm Type Equipment Alarm NM Level 2 Cause Alarm occurs: Device is removed from 59 stack system 22 Confidential and Proprietary Information of ZTE CORPORATIONTIER Related Alarms Recommended ‘Operations Alarm Prototype Description Alarm Description Supported Devices Appendix Specification Message No. Default Severity Level Alarm Recovery Alarm Type NM Level Cause Influence Related Alarms Recommended ‘Operations Alarm Prototype Description Alarm Description Chapter 2 Alarm Message Alarm dears: Device is added to 59 stack system. $12, 18720, 18721 Check whether any device is removed from stack system Alarm occurred Remove Device No.%d! (%d is device number) Alarm eared Add Device No.%d! (%d is device number) Example: 15:50:49 01/22/2008 UTC alarm 299 cleared %Board% Add De- vice No.3! sent by Stack Master Devid 2 15:52:13 01/22/2008 UTC alarm 299 occurred %Board% Remove Device No.3! sent by Stack Master Devid 2 Device is removed from stack system. 59 stack system Na. 300 300 2 Available Equipment Alarm 1 The double SFC(MPU, RPU) are both active or both standby caused by hardware malfunction The rack can not work normally. No. 1, Reboot the two boards with abnormal alarm 2. If reboot operation is invalid, contact with ZTE service staff. 3. ZTE service staff can input printHardwareState in ros and record the result, 2 %5 is %s,system abnormal. The first 9s is the abnormal CPU type. Generally it is SFC, MPU or RPU, The second %s is the abnormal master or slave state. The second %s is the abnormal master or slave state. 16:30:38 06/21/2007 UTC alarm 300 occurred 2 SFC is mas- ter,system abnormal. sent by UPC(MPU) 2 16:38:39 06/21/2007 UTC alarm 300 cleared 2 SFC is master,sys~ tem abnormal. sent by UPC(MPU) 2 ‘The double SFC (MPU, RPU) are both active or both standby caused by hardware malfunction. ‘Confidential and Proprietary Information of ETE CORPORATION 232XR40 Alarm Handling Manual TIE Supported Devices Appendix Specification Message No. Default Severity Level Alarm Recovery Alarm Type NM Level Cause Influence Related Alarms Recommended Operations Alarm Prototype Description Alarm Description Supported Devices Appendix Specification Message No. Default Severity Level Alarm Recovery Alarm Type NM Level Cause 164/T1200, T600/T1200. NA, 301 301 6 Unavailable Equipment Alarm 5 Abnormality of NPCT line card will lead to interruption of switch network reset, which further causes the repeat reset of switch network and thus normal line cards in other slots will fail to send packets normally. To solve this problem, we give a limit to reset times. If the times of switch network reset caused by abnormal line card exceed this threshold, only alarm will be prompted and switch network will not be reset. The linecard with malfunction can not work normally. There is no influence on other linecards. No. Wait for engineer from customer service department to deal with the fault line card. Pannel %d NPC resets switch module over limit times %d line card slot number 11:02:34 03/21/2008 UTC alarm 301 occurred Pannel 5 npc resets switch module over limit times. sent by UPC(MPU) 1 ‘The times of SFU reset caused by abnormal line card exceed this threshold. T64e/T128 NA, 302 302 6 Unavailable Equipment Alarm 5 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. 24 Confidential and Proprietary Information of ZTE CORPORATIONTIER Influence Related Alarms Recommended ‘Operations Alarm Prototype Description Alarm Description Supported Devices Appendix Specification Message No. Default Severity Level Alarm Recovery Alarm Type NM Level Cause Influence Related Alarms Recommended ‘Operations Alarm Prototype Description Alarm Description Supported Devices Chapter 2 Alarm Message To avoid continuous switchover of master/slave SFC, we set a limit to the switchover. When threshold is exceeded, master/slave switchover of SFC will stop. The linecard with malfunction leads to the active/standby switchover. 294, alarm generated by line card out of synchronism. No. Panel %d SFC is exchanged to be slave because switch-module is unsynchronous %d: SFC slot number 11:15:57 03/21/2008 UTC alarm 302 occurred Panel 1 SFC is exchanged to be slave because switch-module is unsynchronous. sent by UPC(MPU) 1 SFC synchronization fails. Master/slave switchover of SFC will oc cur and alarm is sent out ‘T64E/T128 NAL 303 303 6 Unavailable Equipment Alarm 5 It fails to read/write card memory due to the problem of hardware. ‘The single board can not work normally. The thread application on the single board may suspend due to the abnormal memory No. Wait for engineer from customer service department to deal with the fault line card Pannel:%d NPC %s data eye abnormal. %d line card slot number %s Master/slave, Master/slave line card 13:31:30 03/25/2008 UTC alarm 303 occurred Pannel:7 NPC mas- ter data eye abnormal. sent by UPC(MPU) 1 The thread application on the single board may suspend due to the abnormal mem ory read-write, T64E/T128, T1200 ‘Confidential and Proprietary Information of ETE CORPORATION 252XR40 Alarm Handling Manual TIE Appendix Specification Message No. Default Severity Level Alarm Recovery Alarm Type NM Level Cause Influence Related Alarms Recommended Operations Alarm Prototype Description Alarm Description Supported Devices Appendix Specification Message No. Default Severity Level Alarm Recovery Alarm Type NM Level Cause Influence Related Alarms NA 310 310 6 Unavailable Equipment Alarm 5 ‘The hardware is instable. Fails to write to the register in interface board initialization or the platform command configuration. The interface board or the line card can not work normally. The platform command configuration fails. No. Plug the interface board or the line card again. If the malfunction still exists, then contact ZTE customer service personnel to check whether the interface board or the line card is abnormal write register failed:baseaddr = 0x%08x ,offset =0x% 4x %08x: the base address %04x: the offset address Example: 14:17:56 05/20/2008 UTC alarm 303 occurred %Board% write register failed:baseaddr = 0xC6002000 ,offset =0x0006 sent by NPC 2 Alarm appears when the line card fails to modify the register. Alarm may also appear when failing to write to the register in interface board initialization or the platform command configura~ tion. It is used to diagnose the hardware abnormity. T64e/T128, T600/T1200 NA 311 311 5 Unavailable Equipment Alarm 5 The board link forwarding is abnormal. The corresponding hardware reboots, No, 26 Confidential and Proprietary Information of ZTE CORPORATIONTIER Recommended ‘Operations Alarm Prototype Description Alarm Description Supported Devices Appendix Specification Message No. Default Severity Level Alarm Recovery Alarm Type NM Level Cause Influence Related Alarms Recommended ‘Operations Chapter 2 Alarm Message Check whether the board link forwarding is normal; whether the hardware works normally. Alarm occurred NP %d link exception cause %s %s,warning; %d: board number The first %s is the hardware name: 870874FPGASFCBOARD The second %s is the action: reset, rotate Example: 15:29:12 08/09/2008 UTC alarm 311 occurred %Board% link ex- ception cause 874 reset, warning sent by NPC 9 15:28:28 08/09/2008 UTC alarm 311 occurred %Board% link ex- ception cause two 870 reset,warning sent by NPC 9 15:29:30 08/09/2008 UTC alarm 311 occurred %Board% link ex- ception cause FPGA reset,warning sent by NPC 9 15:44:23 08/09/2008 UTC alarm 311 occurred %Board% link ex- ception cause SFC rotate,warning sent by NPC 9 15:46:16 08/09/2008 UTC alarm 311 occurred %Board% link ex- ception cause board reset, warning sent by NPC 9 ‘The board link forwarding is abnormal which brings to something wrong in the corresponding hardware ‘T64E/T128, T600/T1200 NAL 312 312 5 Available Equipment Alarm 2 Alarm occurred The board link forwarding is abnormal. User configuration inter- face is down physically. Alarm deared ‘The board link forwarding works normally for the specified time. User configuration interface is up physically. User configuration interface is up/down, 512 Check whether the board link forwarding is normal; whether the user configures this interface ‘Confidential and Proprietary Information of ZTE CORPORATION 272XR40 Alarm Handling Manual TIE Alarm Prototype Description Alarm Description Supported Devices Appendix Specification Message No. Default Severity Level Alarm Recovery Alarm Type NM Level Cause Influence Related Alarms Recommended Operations Alarm Prototype Description Alarm Description Supported Devices NP %d link exception cause interface %s %s,warning %d: board number The first %s is the interface name. The second %s means that the interface is enabled or disabled. Alarm occurred: shutdown Alarm cleared: up Example: 15:30:31 08/09/2008 UTC alarm 312 occurred %Board% link ex- ception cause interface fei_9/S shut down,warning sent by NPC 9 16:36:27 08/09/2008 UTC alarm 312 deared %Board% link ex- ception cause interface fei_9/5 up,warning sent by NPC 9 The board link forwarding is abnormal which brings to the user configuration interface down T64e/T128, T600/T1200 NA 313 313 6 Unavailable Equipment Alarm The forwading link on np is always abnormal and can not be solved Discard the packets and take corresponding actions. 311 Check whether the board link forwarding is normal or not. Whether there is packet loss or not, The device reboots the relative hard- ware automatically. NP %d forward link has exception, warning %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 The forwarding link is abnormal. T64e/T128, T600/T1200 28. Confidential and Proprietary Information of ZTE CORPORATIONTIER Appendix Specification Message No. Default Severity Level Cause Recommended ‘Operations Alarm Prototype Description Message No. Default Severity Level Cause Recommended ‘Operations Message No. Default Severity Level Cause Recommended ‘Operations Message No. Default Severity Level Chapter 2 Alarm Message NAL Port Alarm 512 512 6 The port is down or up. If it is a port down message, please check whether the port con- nection is normal Alarm occurs: 10:12:57 09/15/2003 UTC alarm 512 occurred, %PORT% Port Down on fei_5/6 sent by SMP 1 Alarm dears: 10:12:59 09/15/2003 UTC alarm 512 cleared. %PORT% Port Up on fei_5/6 sent by SMP 1 540 540 6 ‘The aggregation of port configuration in SMARTGROUP interface is successful. No. 541 41 6 ‘The aggregation of port configuration in SMARTGROUP interface fails. No. 542 542 6 ‘Confidential and Proprietary Information of ZTE CORPORATION 232XR40 Alarm Handling Manual TIE Cause Recommended Operations Message No. Default Security Level Alarm Type NM Level Cause Influence Recommended Operations Alarm Description Prototype For a certain interface board, the quantity of local port returned from lower layer is 0. No. Software Alarm ETHOAM Alarm 16128 16128 5 "ProcessingErrorAlarm® 5 The local end starts loopback and the remote end fails to respond for the reason that the response is delayed or the status configu- ration is not correct. Loopback fails. Start loopback again. Interface %s %s is the reason The details are as follows: 1, loopback failure for Mode Ethernet oam protocol mode can't satisfy loopback sending condition. Ethernet oam is not enable Ethernet oam is not enabled 3. Discovery is undone Ethernet oam protocol negotiation fails. 4. in slave mode 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 30 Confidential and Proprietary Information of ZTE CORPORATIONTIER Alarm Description Supported Devices Message No. Default Security Level Alarm Type NM Level Cause Influence Recommended ‘Operations Alarm Description Prototype Alarm Description Supported Devices Message No. Default Security Level Alarm Type NM Level Cause Influence Chapter 2 Alarm Message Remote respond loopback stop fails Examples: 00:16:14 01/01/2001 UTC alarm 16128 occurred %ETHOAM% In- terface loopback respond start command failed on fei_1/1 sent by NPC 1 00:16:14 01/01/2001 UTC alarm 16128 occurred %ETHOAM% In- terface loopback respond stop command failed on fei_1/1 sent by NPC 1 The local end starts loopback and the remote end fails to respond. All series (This alarm can be available from V4.8.22.) 16129 16129 5 "Communicationalarm" 5 Lost the message that keeps protocol success status within timer time. Cause local Ethernet oam protocol status initialization. Check if link and packet sending/receiving in receive direction are normal and re-initiate protocol negotiation. Interface %s localmac %s peermac %s The first %slost link in recsive direction. The second %s and the third 9ssource MAC address and destina~ tion MAC address. Examples: 00:16: 1401/01/2001 UTC alarm 16129 occurred %ETHOAM% In- terface lost ink in receive direction localmac 00d0.d0c6.5e27 peer- mac 00d0.d0c0.7d81 on fei_1/1 sent by NPC 11 Packets fail to be received on receive direction of link All series (This alarm can be available from V4.8.22.) 16130 16130 5 "ProcessingErroralarm" 5 The local or remote configuration modification causes that the local or remote can’t satisfy the modified configuration. Cause Ethernet oam protocol status to change ‘Confidential and Proprietary Information of ZTE CORPORATION 322XR40 Alarm Handling Manual TIE Recommended Operations Alarm Description Prototype Alarm Description Supported Devices Message No. Default Security Level Alarm Type NM Level Cause Influence Recommended Operations Alarm Description Prototype Check attribute configuration and re-initiate Ethernet OAM proto- col negotiation Discovery %s localmac %s peermac %s The first %s details are as follows 1, Reset for remote unsatisfied The remote can’t satisfy the modified configuration Reset for local unsatisfied The local can't satisfy the modified configuration. 3. is successfully connected Discovery is successfully connected. The second %s and the third %s: source MAC address and desti- nation MAC address. Examples: 00:16:14 01/01/2001 UTC alarm 16130 occurred %ETHOAM% Discovery Reset for remote unsatisfied localmac 00d0.d0c6.5227 peermac 00d0.d0c0.7d81 on fei_1/1 sent by NPC 1 00:16:14 01/01/2001 UTC alarm 16130 occurred %ETHOAM% Discovery Reset for local unsatisfied localmac 00d0.d0c6.5227 peermac 00d0.d0c0.7d81 on fei_1/1 sent by NPC 1 00:16:14 01/01/2001 UTC alarm 16130 occurred %ETHOAM% Discovery is successfully connected localmac 00d0.d0c5.5227 peermac 00d0.d0c0.7d81 on fei_1/1 sent by NPC 1 The local and remote can't satisfy the Ethernet oam protocol at- tribute configuration. All series (This alarm can be available from V4.8.22.) 16131 16131 5 "Communicationalarm" 5 The local receives the related fault event such as link fault, dying gasp fault and fault frame event. Generate protocol message to inform remote related event and print alarm locally. Check attribute configuration and re-initiate Ethernet OAM proto- col negotiation Discovery %s localmac %s peermac %s The first %s details are as follows Link fault: check link state Dying gasp fault: check device state Critical fault: check device state Error frame event: check received error frames BORE 32. Confidential and Proprietary Information of ZTE CORPORATIONTIER Alarm Description Chapter 2 Alarm Message Interface %s localmac %s peermac %s The first %s details are as follows 1. occur remote link fault occur remote link fault event 2. occur remote dying gasp event occur remote dying gasp event 3. occur remote critical event occur remote critical event 4. occur local link fault occur local link fault 5. occur local dying gasp event ‘occur local dying gasp event 6. occur local critical event occur local critical event i. occur error frame event occur error frame event locally ii, occur error frame-period event occur error frame-period event locally ili. occur error frame-second event occur error frame-second event locally iv, occur error symbol-period event occur error symbol-period event locally The second %s and the third 96s: source MAC address and desti- nation MAC address Example: 1, 00:16:14 01/01/2001 UTC alarm 16131 occurred %ETHOAM% Interface occur remote link fault localmac 00d0.d0c6.5e27 peermac 00d0.d0c0.7d81 on fei_1/1 sent by NPC 1 2. 00:16:14 01/01/2001 UTC alarm 16131 occurred %ETHOAM% Interface occur remote dying gasp event localmac. 00d0.d0c6.5e27 peermac 00d0.d0c0.7481 on fei_i/1 sent by NPC 1 3. 00:16:14 01/01/2001 UTC alarm 16131 occurred %ETHOAM% Interface occur remote critical event localm ac 00d0.d0c6.5227 peermac 00d0.d0c0.7d81 on fei_1/1 sent by NPC 1 4. 00:16:14 01/01/2001 UTC alarm 16131 occurred %ETHOAM% Interface occur local link fault localmac 00d0.d0c6.5e27 peer- mac 00d0.d0c0.7d81 on fei_i/1 sent by NPC 1 S. 00:16:14 01/01/2001 UTC alarm 16131 _ occurred %ETHOAM% Interface occur local dying gasp event localmac. 00d0.d0c6.5e27 peermac 00d0.d0c0.7481 on fei_i/1 sent by NPC1 6. 00:16:14 01/01/2001 UTC alarm 16131 occurred %ETHOAM% Interface occur local critical event localmac 00d0.d0c6.5227 peermac 00d0.d0c0.7d81 on fei_1/1 sent by NPC1 ‘Confidential and Proprietary Information of ZTE CORPORATION 332XR40 Alarm Handling Manual TIE Alarm Description Supported Devices Message No. Default Security Level Alarm Recovery Alarm Type NM Level Cause Influence Recommended Operations Alarm Description Prototype 7. 00:16:14 01/01/2001 UTC alarm 16131 occurred %ETHOAM% Interface occur error frame event localmac 00d0.d0c6.5e27 peermac 00d0.d0c0.7d81 on fei_1/1 sent by NPC 1 8, 00:16:14 01/01/2001 UTC alarm 16131 occurred ‘%ETHOAM% Interface occur error frameperiod event localmac 00d0.d0c6.5e27 peermac 00d0.d0c0.7481 on fei_i/1 sent by NPC 1 9, 00:16:14 01/01/2001 UTC alarm 16131 occurred %ETHOAM% Interface occur error framesecond event locaimac 00d0.d0c6.Se27 peermac 00d0.d0c0.7d81 on fei_1/1 sent by NPC 1 10. 00716: 14 01/01/2001 UTC alarm 16131 occurred %ETHOAM% Interface occur error symbol- period event localmac 00d0.d0c6.5227 peermac 00d0.d0c0.7d81 on fei_1/1 sent by NPC 1 The device occurs related fault event such as link fault, dying gasp fault and fault frame event. All series (This alarm can be available from V4.8.22.) 30464 30464 6 Available "ProcessingErrorAlarm® 5 Local configuration has fault. The peer receives faulty CC message or doesn't receive CC message that local sends Local prints alarm. Link fault: check link state, check configuration %s MD %d MA %d MEP %d, %5 The first 9d is the ID of MD with RDI alarm The second %d is the ID of MA with RDI alarm The third %d is the ID of MEP with RDI alarm The first %s is someRDIdefect, when alarm appears, the alarm is the content which shows 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 34 Confidential and Proprietary Information of ZTE CORPORATIONTIER Alarm Description Supported Devices Appendix Specification Message No. Default Security Level Alarm Recovery Alarm Type NM Level Cause Influence Recommended ‘Operations Alarm Description Prototype Chapter 2 Alarm Message all remote MEPs RDI defect disappear! when alarm disappears, the alarm is the content which shows above Example: 1, 10:38:07 08/10/2009 UTC alarm 30464 occurred %CFM% MD 1 MA 1 MEP 2,has received a packet from some remote MEPs with RDI flag 2. 10:38:10 08/10/2009 UTC alarm 30464 occurred %CFM% MD 1 MA i MEP 2, all remote MEPs RDI defect disappear! When CC message that sends from peer has RDI, this alarm ap~ pears. All series This alarm can be available from V4.8.23, 30465 30465 6 Available Communication Alarm 5 Local can't receive CC message of peer. This leads to protocol message to inform remote related event and local printing alarm Link fault: check link state, check configuration, SomeRMEPCCMdefect,MD 9d MA %d MEP %d , s The first 9d is the ID of MD with DefRemoteCcM alarm. The second %d is the ID of MA with DefRemoteCcM alarm The third %d is the ID of MEP with DefRemoteCcM alarm The first %s is has not received CCM from some remote MEPs expired 3.5 times CCM's transmission interva when alarm appears, the alarm is the content which shows above. ‘Som eRMEPCCMdefect 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 ETE CORPORATION 352XR40 Alarm Handling Manual TIE Alarm Description Supported Devices Appendix Specification Message No. Default Security Level Alarm Recovery Alarm Type NM Level Cause Influence Recommended Operations Alarm Description Prototype from some remote MEPs expired 3.5 times CCM's transmission interval! 2, 10:38:10 08/10/2009 UTC alarm 30465 occurred %CFM% MD 1 MA 1 MEP 2, SomeRMEPCCMdefect defect disappear! When configured local MEP can't receive CC message sended from peer, this alarm will appaer. All series This alarm can be available from V4.8.23. 30466 30466 6 Available Configuretrroralarm 5 The local or peer configuration has error. Local receives faulty CC message. Local prints alarm. View local and remote configurations. %s MD %d MA %d MEP %d, %5 The first 9d is the ID of MD with RDI alarm The second %d is the ID of MA with RDI alarm The third %d is the ID of MEP with ERR alarm. The first %s is errorcCMdefect, when alarm appears, the alarm is the content which shows above When alarm disappears, this character string is empty. The second character string content is one or more invalid CCMs has been received! when alarm appears, the alarm is the content which shows above errorCCMdefect defect disappear! when alarm disappears, the alarm is the content which shows above. 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! 36 Confidential and Proprietary Information of ZTE CORPORATIONTIER Alarm Description Supported Devices Appendix Specification Message No. Default Security Level Alarm Recovery Alarm Type NM Level Cause Influence Recommended ‘Operations Alarm Description Prototype Chapter 2 Alarm Message 2. 10:38:10 08/10/2009 UTC alarm 30466 occurred %CFM% MD 1 MA i MEP 2, errorCCMdefect defect disappear! When local reosives faulty CC message that sends from peer, this alarm appears. All series This alarm can be available from V4.8.23, 30467 30467 6 Available ConfigureErrorAlarm 5 Receive the CC messge which doesn't belong to this Level or doesn't belong to this MA. Local prints alarm View local and remote configurations. %5 MD %d MA %d MEP %d, %s The first 96d is the ID of MD with RDI alarm The second %d is the ID of MA with RDI alarm The third 96d is the ID of MEP with XCON alarm The first 9s is xconccMdefect, when alarm appears, the alarm is the content which shows above. When alarm disappears, this character string is empty. The second character string content is ‘one or more cross connect CCMs has been received!, when alarm appears, the alarm is the content which shows above. xconCCMdefect defect disappear! when alarm disappears, the alarm is the content which shows above Example: 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 i MEP 2, xconCCMdefect defect disappear! ‘Confidential and Proprietary Information of ZTE CORPORATION 372XR40 Alarm Handling Manual TIE Alarm Description Supported Devices Appendix Specification Message No. Cause Recommended Operations Message No. Cause Recommended Operations Message No. Default Severity Level Cause Recommended Operations Alarm Prototype Description Message No. Default Severity Level Alarm Recovery Alarm Type NM Level When the CC messge which doesn't belong to this Level or this MA is received, this alarm appears. All series This alarm can be available from V4.8.23. ROS Alarm 16384 16384 The process is suspended. Please copy and save the information, then contact ZTE mainte- nance staff. 16386 16386 Privileged mode password is changed Please check the password. 16389 16389 6 The rack is cold starting which is opposite to hot starting. Cold starting means that to turn on the power and start-up the device Hot starting means that to reboot the device when itis still running No. Alarm occurred 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 16391 5 Unavailable CLASS_NOTIFY 4 38 Confidential and Proprietary Information of ZTE CORPORATIONTIER Cause Recommended ‘Operations Alarm Prototype Description Alarm Description Supported Devices Appendix Specification Message No. Default Severity Level Alarm Type NM Level Cause Recommended ‘Operations Alarm Prototype Description Alarm Description Supported Devices Appendix Specification Message No. Default Severity Level Alarm Recovery Alarm Type NM Level Chapter 2 Alarm Message The current version is in trial run state. ‘The command updatever activate in privilege mode can be used to remove the try-running alarm Current version is in try-running and activate it please. Example: 14:28:01 03/21/2008 UTC alarm 16392 occurred %ROS% Current version is in try-running and please activate it sent by MEC 1. ‘The current version is in trial running state and it need to be acti~ vated by users. Or the device reboots automatically after a while. ‘The remaining time can be viewd by command show updatever in privileged mode CERPTN 6100 CERPTN 8900 CERPTN version supports this alarm 16392 16392 5 CLASS_NOTIFY 4 The current version is the rollback. The reason may be that the trial run fails when updating the version. ‘The command updatever activate in privilege mode can be used to remove the trial run alarm Back-version is running now for loading update-version failed 14:27:32 03/21/2008 UTC alarm 16392 occurred %ROS% Back- version is running now for loading update-version failed sent by MEC 1 The current version is the rollback. The reason may be that the trial run fails when updating the version CERPTN 6100 CERPTN 6100 CE &PTN version supports this alarm 16393 16393 5 Unavailable CLASS_NOTIFY 5 ‘Confidential and Proprietary Information of ZTE CORPORATION 332XR40 Alarm Handling Manual TIE Cause Recommended Operations Alarm Prototype Description Alarm Description Supported Devices Appendix Specification Message No. Default Severity Level Alarm Recovery Alarm Type NM Level Cause Influence Recommended Operations Alarm Prototype Description ‘A prompt appears: succeed to download and upgrade the version, but fail to write the upgrade rollback. No. Downloading update-version file successfully but setting the flag failed Example: 14:29:01 03/21/2008 UTC alarm 16392 occurred %ROS% Down- loading update-version file successfully but setting the flag failed sent by MEC 1 ‘A prompt appears: succeed to download and upgrade the version, but fail to write the upgrade rollback. CERPTN 6100 CERPTN 8900 CERPTN version supports this alarm 16394 16394 5 Available Equipment Alarm 5 Alarm occurred Users configure the device again after plugging the backplane, The backplan backup does not complete. Alarm cleared The backplane finishes the backup for the main board. The back- plane can work instead of the main board. The backplane can not work instead of the main board, Wait for a while to see whether the alarm recovers. Or check whether the backplane backup the data on the main board. Alarm occurred Slave is not a copy of master. Slave board can not substitute for master board. 14:50:22 08/20/2008 green alarm 16394 occurred %ROS% Slave is copying of master. Slave board can not substitute for master board, sent by UPC(MPU) 2 Alarm cleared 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. 40. Confidential and Proprietary Information of ZTE CORPORATIONTIER Alarm Description Supported Devices Message No. Default Security Level Alarm Recovery Alarm Type NM Level Cause Influence Recommended ‘Operations Alarm Description Prototype Alarm Description Supported Devices Message No. Default Security Level Alarm Type Chapter 2 Alarm Message The backplan backup does not complete. It can not work instead of the main board. ‘T64E/T128 16395 16395 5 Available "Equipmentalarm" 4 SD is removed. SD removed notice Insert SD Alarm Occured SD is removed Slave SD is removedslave board Alarm Recovery SD is inserted Slave SD is insertedslave board Examples: Alarm Occured 18:30:50 09/02/2008 alarm 16395 occurred %ROS% SD is re- moved sent by MEC 1 18:32:55 09/02/2008 alarm 16395 occurred %ROS% Slave SD is removed sent by MEC2 Alarm Recovery 18:30:51 09/02/2008 alarm 16395 cleared %ROS% SD is inserted sent by MEC 1 18:33:00 09/02/2008 alarm 16395 cleared %ROS% Slave SD is inserted sent by MEC2 SD is removed 89 and 69 series routing switch(This alarm can be available from 4.8.22.) 16396 16396 4 "ProcessingErroralarm" ‘Confidential and Proprietary Information of ZTE CORPORATION 422XR40 Alarm Handling Manual TIE NM Level Cause Influence Recommended Operations Alarm Description Prototype Alarm Description Supported Devices Message No. Default Severity Level Cause Recommended Operations Message No. Default Severity Level Cause Recommended Operations 5 When slice memory is applied, if the first valid slice memory in slice idle table, the physical next block or the logical next block has check failure the applied slice memory is modified illegally. Maybe memory is exhausted. Use the show processor command to view if memory utilization Memory is abnormal. Slice Isolate Unit(%d) Times(%d) At Tick(%d) On %5(%s) Panel(%d)! The first %d: slice memory queue type, the range is from 2 to 30 The second %d: isolated times, the maximum is 256. The third %d: tick value in this isolation. The first %ssingle board type, the value is RP,MP,SP or NP. The second %s: single board master/slave type, master is M, slave is S. The fourth %dpanel number of single board. Example: 18:28:05 10/17/2008 UTC alarm 16396 occurred %ROS% Slice Isolate Unit(3) Times(1) At Tick(15628) On RP(M) Panel(1)! sent by UPC(RPU) 1 Slice memory check fails. 7128/T600/T1200 device (This alarm can be available from V4.8.20.) DATABASE Alarm 16640 16640 3 Database writing is wrong. Check whether the system is running normally. If it occurrs in system configuration, it may try again a few minutes later. 16642 16642 6 The alarm buffer only has 20% space left. Ifit does not configure to send alarm messages to external server in ftp or syslog mode, please check if there is any important alarm 42. Confidential and Proprietary Information of ZTE CORPORATIONTIER Message No. Default Severity Level Cause Recommended ‘Operations Message No. Default Severity Level Cause Recommended ‘Operations Message No. Default Severity Level Cause Recommended ‘Operations Message No. Default Severity Level Cause Chapter 2 Alarm Message message in alarm buffer by using show logging alarm comm and; if there is, copy the important alarm message for backup. Set alarm log buffer size by using command logging buffer ."buffer-size” is the size of alarm buffer: 100~1000, 200K by default. 16643 16643 5 The alarm buffer overflows. Some old alarm messages will be cleared If alarm message is needed, export alarm message at first. Set alarm log buffer size by using command logging buffer . "buffer-size" is the size of alarm buffer: 100~ 1000, 200k by default. 16644 16644 3 The alarm buffer overflows. Some old alarm messages will be cleared If alarm message is needed, export alarm message at first. Set alarm log buffer size by using command logging buffer . "buffer-size" is the size of alarm buffer: 100~ 1000, 200k by default. 16645 16645 3 The standby board fails to acquire the main board database file via FTP. Check the system running status. Restart the standby board if necessary. 16646 16646 3 ‘The node recursion level is too deep in the program to delete the database. ‘Confidential and Proprietary Information of ZTE CORPORATION 432XR40 Alarm Handling Manual TIE Recommended Operations Message No. Default Severity Level Alarm Recovery Alarm Type NM Level Cause Influence Related Alarms Recommended Operations Alarm Prototype Description Alarm Description Supported Devices Appendix Specification Message No. Default Severity Level There may be redundant configuration. Please contact ZTE for the solution. OAM Alarm 16899 16899 5 Available QoSAlarm 4 CPU load, namely CPU utilization ratio reaches the set low thresh~ old. It may bring to the slow operation response. 16900, 16901 If the operation with great consumption on cpu is carried out in short time, then it is normal phenomenon. Commands show process, show process detail can be used to view CPU utilization. %(M) panel %d current CPU load is: %d% %5(S) panel %d current CPU load is: %4% The first 95 is the CPU type. The first %d is panel number and the second %d is CPU utilization. Alarm occured: ‘An alarm 16899 level 5 occurred at 00:52:07 01/01/2001 UTC sent by UPC(MPU) 1 %0AM% CPU load exceeds the lowest threshold NP(M) panel 7 current CPU load is: 80%. Alarm cleared: ‘An alarm 16899 level 5 cleared at 00:53:07 01/01/2001 UTC sent by UPC(MPU) 1 %0AM% CPU load exceeds the lowest threshold NP(M) panel 7 current CPU load is: 50%. CPU load, namely CPU utilization ratio exceeds the set low thresh- old. Al The platform 4.6.03b and the upgrade versions support this alarm Not CERPTN version. 16900 16900 5 144 Confidential and Proprietary Information of ZTE CORPORATIONTIER Alarm Recovery Alarm Type NM Level Cause Influence Related Alarms Recommended ‘Operations Alarm Prototype Description Alarm Description Supported Devices Appendix Specification Message No. Default Severity Level Alarm Recovery Alarm Type NM Level Cause Influence Related Alarms Recommended ‘Operations Alarm Prototype Description Alarm Description Supported Devices Appendix Specification Chapter 2 Alarm Message Available QoSAlarm 4 CPU load, namely CPU utilization ratio reaches the set middle threshold. It may bring to the slow operation response. 16899, 16901 If the operation with great consumption on cpu is carried out in short time, then it is normal phenomenon. Commands show process, show process detail can be used to view CPU utilization. %5(M) panel %d current CPU load is: %d% %5(S) panel %d current CPU load is: 94% ‘The first 9s is CPU type. The first %d is panel number and the second 9d is CPU utilization. CPU load, namely CPU utilization ratio exceeds the set middle threshold. All ‘The platform 4.6.03b and the upgrade versions support this alarm. Not CE&PTN version 16901 16901 5 Available QoSAlarm 3 CPU load, namely CPU utilization ratio reaches the set high thresh- old It may bring to the slow operation response. 16899, 16900 If the operation with great consumption on cpu is carried out in short time, then it is normal phenomenon. Commands show process, show process detail can be used to view CPU utilization. %5(M) panel %d current CPU load is: %d% %5(S) panel %d current CPU load is: 94% ‘The first 9s is CPU type. The first %d is panel number and the second 9d is CPU utilization. CPU load, namely CPU utilization ratio exceeds the set high thresh~ old All ‘The platform 4.6.03b and the upgrade versions support this alarm. Not CE&PTN version ‘Confidential and Proprietary Information of ZTE CORPORATION 452XR40 Alarm Handling Manual TIE Message No. Default Severity Level Cause Recommended Operations Message No. Default Severity Level Cause Recommended Operations Message No. Default Severity Level Cause Recommended Operations Message No. Default Severity Level Cause Recommended Operations Message No. Default Severity Level Cause 16903 16903 5 FLASH tests are not successful. Check the hardware of the equipment and check whether FLASH exists or there is something abnormal. 16904 16904 5 FLASH exists but can not work normally after setting up the rack Change FLASH for a new one, or set up the rack without FLASH. 16905 16905 4 Backplane fails to write nvram Backup the configuration to prevent configuration loss. Check whether the backplane is running normally. Change the backplane if neccesarry. 16906 16906 6 Distributing system RP sends a message to MP and inform to add or delete interface, Give an alarm after the synchronized message fails. Send the alarm message to ZTE's maintenance personnel. 16907 16907 5 When QoS is applied for dynamic memory, the application fails. 446 Confidential and Proprietary Information of ZTE CORPORATIONTIER Recommended ‘Operations Message No. Default Severity Level Cause Recommended ‘Operations Alarm Prototype Description Message No. Default Severity Level Cause Recommended ‘Operations Alarm Prototype Description Message No. Send the alarm message to ZTE’ 16916 16916 6 The ftp user logs into the device No. Alarm occurred Chapter 2 Alarm Message 's maintenance personnel 00:02:21 01/01/2001 UTC alarm 16916 occurred %OAM% ftp user from 192.168.1.125 port: port:21IN OK sent by MCP 16917 16917 5 3549 to load:192.168.1.10 If one of the terminal executes “write” operation, then the terminal is still in the phase of configure collection. If the connection is cut down for some reason, then the alarm is generated. The possibility of disconnection is as follow: = Console, telnet connection times out. = Other terminal execute clear Please do not cut down the con tep to delete a TCP link nection when the “write” opera tion is being performed. If the terminal connection is cut down in the phase of configure collection, stopped. Alarm occurred then all the write operations are The serial port interrupts to execute write 10:52:25 06/27/2007 UTC alarm 16917 occurred %0AM% Writing configuration aborted because con 0 is closed! sent by UPC(MPU) PT Telnet execute write terminal 10:56:20 06/27/2007 UTC alarm 16917 occurred %OAM% Writing configuration aborted because vty 0 is closed! sent by UPC(MPU) 1 The terminal number after vty keeps consistent with the one after command who. 16918 16918 Confidential and Proprietary Information of 2TE CORPORATION 472XR40 Alarm Handling Manual TIE Default Severity Level Cause Recommended Operations Alarm Prototype Description Appendix Specification Message No. Default Severity Level Cause Alarm Prototype Description Appendix Specification Message No. 5 Ifone of the terminal execute “write” operation, then the terminal is in the phase of background file copy because it already finishes the configure collection, if the connection is cut, then alarm is gen= erated. The possibility of disconnection is as follows: = Cut down the windows of the terminal directly. = Console, telnet connection times out. = Other terminal executes clear tep to delete a TCP link. Do not cut this connection as much as possible when “write” op~ eration is being performed. If connection is cut down when write is still executing fle operation, then “write” continues in the bacl ground as far as the final "startrun” created. Please do not restart the bracket. Alarm occurred The serial port interrupts to execute write. 10:59:29 06/27/2007 UTC alarm 16918 occurred %OAM% Con 0 is dosed, but writing configuration is still in process! sent by UPC(MPU) Telnet executes write terminal: 10:59:29 06/27/2007 UTC alarm 16918 occurred %0AM% Vty 1 is dosed, but writing configuration is still in process! sent by UPC(MPU) The terminal number after vty keeps consistent with the one after command who. Please do not restart the rack in order to prevent the created “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. 16919 16919 6 FTP users delete the files on the device. Alarm occurred 00:07:21 01/01/2001 UTC alarm 16919 occurred %0AM% DELE file /flash/1.tkt sent by MCP Please do not restart the rack in order to prevent the created “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 16920 e ‘Confidential and Proprietary Information of ZTE CORPORATIONTIER Default Severity Level Cause Alarm Prototype Description Message No. Default Severity Level Cause Alarm Prototype Description Message No. Default Severity Level Cause Alarm Prototype Description Recommended ‘Operations Message No. Default Security Level Alarm Type NM Level Cause Influence Recommended ‘Operations Chapter 2 Alarm Message 6 The ftp user uplosds files to the device Alarm occurred 00:05:49 01/01/2001 UTC alarm 16920 occurred %OAM% STOR file /flash/1.txt sent by MCP 16921 16921 6 The ftp user copies files on the device Alarm occurred 00:04:25 01/01/2001 UTC alarm 16921 occurred %OAM% RETR. file /flash/hes59.bin sent by MCP 16922 16922 6 The ftp server fails to send message. Alarm occurred 00:07:21 01/01/2001 UTC alarm 16922 occurred %OAM% Send message to protocol error by MCP. Check whether FTP server configuration is correct and whether the connection is well 16923 16923 6 "ProcessingErroralarm" 4 After enabling DHCP, the switch will download configuration file through TFTP circularly. When retry time is 10, about 4~5 min= utes, version is not downloaded Inform user of failure of downloading and suggest downloading again. Stop DHCP automatic download configuration file function. ‘Confidential and Proprietary Information of ZTE CORPORATION 432XR40 Alarm Handling Manual TIE Alarm Description Prototype Alarm Description Supported Devices Message No. Default Security Level Alarm Recovery Alarm Type NM Level Cause Influence Related Alarms Recommended Operations Alarm Description Prototype Alarm Description Supported Devices Message No. Default Security Level Alarm Recovery Auto download config file fail Example: 00:57:29 01/01/2001 UTC alarm 16923 occurred %OAM% Auto download config file fail sent by MCP DHCP auto download configuration file retry fails. 39,59,69 16924 16924 3 Available QOS Alarm 3 The utilization ratio that process uses CPU resource reaches de~ fined high threshold. Response to operation may be slow 16925 16926 It is normal that CPU resource is consumed too much in a short time. Use the show task detail command to view the utilization ratio that process uses CPU resource, Task %s current CPU load is: %d.%02d%% exceeds the highest Threshold %d%9% 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 9%d is high threshold that process uses CPU resource. Alarm Generated An alarm 16924 level 3 occurred at 00:52:07 01/01/2001 UTC sent by UPC(MPU) 1 %0AM% Task ACL current CPU load is: 60.0% exceeds the highest Threshold 55% Alarm Recovery An alarm 16924 level 3 cleared at 00:53:07 01/01/2001 UTC sent by UPC(MPU) 1 %OAM% Task ACL current CPU load is: 50.0% under the highest Threshold 55% The utilization ratio that process uses CPU resource reaches de~ fined high threshold. 6989 16925 16925 4 Available 50. Confidential and Proprietary Information of ZTE CORPORATIONTIER Alarm Type NM Level Cause Influence Related Alarms Recommended ‘Operations Alarm Description Prototype Alarm Description Supported Devices Message No. Alarm Recovery Default Security Level Alarm Type NM Level Cause Influence Related Alarms Recommended ‘Operations Alarm Description Prototype Chapter 2 Alarm Message QOS Alarm 4 The utilization ratio that process uses CPU resource reaches de- fined medium threshold. Response to operation may be slow, 16924 16926 It is normal that CPU resource is consumed too much in a short time. Use the show task detail command to view the utilization ratio that process uses CPU resource. Task %s current CPU load is: %d.9602d%% exceeds the interme- diate Threshold %d%9% The first %s is process name type. The first 9d and second %d are peak value of utilization ratio that process uses CPU resource. ‘The third %d is medium threshold that process uses CPU resource. Alarm Generated An alarm 16924 level 4 occurred at 00: 54:07 01/01/2001 UTC sent by UPC(MPU) 1 9%0AM% Task ACL current CPU load is: 40.0% exceeds the intermediate Threshold 35% Alarm Recovery ‘An alarm 16924 level 4 cleared at 00:55:07 01/01/2001 UTC sent by UPC(MPU) 1 %0AM% Task ACL current CPU load is: 30.0% under the intermediate Threshold 35% The utilization ratio that process uses CPU resource reaches de- fined medium threshold. 6989 16926 16926 Available 5 QOS Alarm 4 The utilization ratio that process uses CPU resource reaches de- fined low threshold Response to operation may be slow, 16924 16925 It is normal that CPU resource is consumed too much in a short time, Use the show task detail command to view the utilization ratio that process uses CPU resource. Task %s current CPU load is: 96d.%02d%% exceeds the lowest Threshold %d%% The first %s is process name type. The first 9d 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 ETE CORPORATION Si2XR40 Alarm Handling Manual TIE Alarm Description Supported Devices Message No. Default Severity Level Cause Recommended Operations Message No. Default Severity Level Cause Recommended Operations Message No. Default Severity Level Cause Recommended Operations Alarm Generated An alarm 16924 level 5 occurred at 00:56:07 01/01/2001 UTC sent by UPC(MPU) 1 %OAM% Task ACL current CPU load is: 20.0% exceeds the lowest Threshold 15% Alarm Recovery An alarm 16924 level 5 cleared at 00:57:07 01/01/2001 UTC sent by UPC(MPU) 1 %0AM% Task ACL current CPU load is: 10.0% under the lowest Threshold 159 The utilization ratio that process uses CPU resource reaches de~ fined low threshold 6989 OSPF Alarm 17408 17408 6 The port status shifts. Check whether OSPF status shift is normal according to the dis- played alarm message. Ifit is abnormal, please check whether the configuration is correct and the corresponding status is correct. 17409 17409 6 The virtual link port status shifts. Check whether OSPF status shifts is normal according to the dis- played alarm message. If it is abnormal, please check whether the configuration is correct and the corresponding virtual link port status is correct. 17410 17410 6 The neighbor status shifts. Check whether the OSPF status shifts is normal according to the displayed alarm message. [fit is abnormal, please check whether 52. Confidential and Proprietary Information of ZTE CORPORATIONTIER Message No. Default Severity Level Cause Recommended ‘Operations Message No. Default Severity Level Cause Recommended ‘Operations Message No. Default Severity Level Cause Recommended ‘Operations Message No. Default Severity Level Cause Recommended ‘Operations Message No. Chapter 2 Alarm Message the configuration is correct and the interface status connected with neighbor is correct. 17411 17411 6 The virtual neighbor status shifts. Check whether the OSPF status shifts isnormal according to the displayed alarm message. If it is abnormal, please check whether the configuration is correct and the virtual link interface status connected with neighbor is correct. 17412 17412 6 Port authentication fails. Check whetehr the set authentication password of adjacent equip- ment at the interface corresponding to home equipment is consis- tent with the configuration on home equipment. 17413 17413 6 Virtual port authentication fails Check whether the set authentication password of adjacent equip- ment at the virtual interface corresponding to home equipment is consistent with the configuration on home equipment. 17414 17414 6 ‘The port receives error packets, Check whether the physical interface connection is reliable. 17415 17415 ‘Confidential and Proprietary Information of ZTE CORPORATION 532XR40 Alarm Handling Manual TIE Default Severity Level Cause Recommended Operations Message No. Default Severity Level Cause Recommended Operations Message No. Default Severity Level Cause Recommended Operations Message No. Default Severity Level Cause Recommended Operations Message No. Default Severity Level Cause Recommended Operations 6 The virtual port receives error packets. Check whether the physical connection of interfaces forming the virtual interface is reliable. 17416 17416 6 The database size is beyond the threshold After saving configuration information, re-enable relative module or restart equipment if possible. 17417 17417 6 The interface configuration is wrong, Modify the interface configuration to be inconsistent with the op~ posite end interface. 17418 17418 6 The virtual interface configuration is wrong Modify the virtual interface configuration inconsistent with the op~ posite end interface. 17419 17419 7 Packets are retransmitted at the interface. Please check whether the network status is normal and the net- work load is too heavy. 54 Confidential and Proprietary Information of ZTE CORPORATIONTIER Message No. Default Severity Level Cause Recommended ‘Operations Message No. Default Severity Level Cause Recommended ‘Operations Message No. Default Severity Level Cause Recommended ‘Operations Message No. Default Severity Level Cause Recommended ‘Operations Message No. Default Severity Level Cause Chapter 2 Alarm Message 17420 17420 7 Packets are retransmitted at the virtual interface Please check whether the network status is normal and the net work load is too heavy. 17421 17421 6 Fail to transmit MDS report. Check whether the MDS keyword configured at the interface is correct and valid 17422 17422 6 Fail to distribute the memory. Please copy and save the information, then contact ZTE mainte- nance staff. 17423 17423 6 Receiving error request packet results in link-disconnection, Please check whether the interface physical link is stable 17424 17424 6 ‘The error sequence No. in DD packets the interface received re~ sults in link-disconnection ‘Confidential and Proprietary Information of ETE CORPORATION 552XR40 Alarm Handling Manual TIE Recommended Operations Message No. Default Severity Level Cause Recommended Operations Message No. Default Severity Level Cause Recommended Operations Message No. Default Severity Level Cause Recommended Operations Message No. Default Severity Level Cause Recommended Operations Message No. Default Severity Level Cause Please check whether the interface physical link is stable. 17425 17425 6 The route id not contained in Hello packet the interface received results in link-disconnection Please check whether the interface physical link is stable. 17426 17426 6 Receiving Hello packet results in link-disconnection. Please check whether the interface physical link is stable or the configuration is correct. 17427 17427 6 Management Down results in link-disconnection. Please check whether the disable process operation is executed. 17428 17428 6 Physical interface Down result in link-disconnection, Please check whether the shutdown operation is executed under the interface 17429 17429 6 Interface state change results in link-disconnection 536 Confidential and Proprietary Information of ZTE CORPORATIONTIER Recommended ‘Operations Message No. Default Severity Level Cause Recommended ‘Operations Message No. Default Severity Level Cause Recommended ‘Operations Message No. Default Severity Level Cause Recommended ‘Operations Message No. Default Severity Level Cause Chapter 2 Alarm Message Please check whether the interface state is changed, RIP Alarm 17664 17664 6 RIP module fails to apply for the memory distribution Please check whether the system memory utilization reaches the top and the system configuration information reaches or exceeds the permitted limits; Ifit reaches the top, consider to upgrade the equipment. If the system memory utilization does not reach the top, please contact ZTE maintenance staff. 17666 17666 6 RIP module fails to create timer. If the problem appears during command configuration, it may at- tempt a few minutes later, Please record the fault phenomenon and contact ZTE maintenance staff in time. 17667 17667 6 RIP route table is full and unable to add more RIP routes and new neighbors. Please check whether the configuration related to RIP protocol is correct and proper and whether the system running state is nor- mal 17670 17670 6 The RIP neighbor is not on the same subnet or the neighbor ad- dress is @ network broadcast address. ‘Confidential and Proprietary Information of ETE CORPORATION 572XR40 Alarm Handling Manual TIE Recommended Operations Message No. Default Severity Level Cause Recommended Operations Message No. Default Severity Level Cause Recommended Operations Message No. Default Severity Level Cause Recommended Operations Message No. Default Severity Level Cause Recommended Operations Please check whether the configuration related to RIP protocol is correct and proper. 17671 17671 6 Simple authentication has no keyword, so no authentication for packages. Please check whether the configuration related to RIP protocol is correct and proper. 17672 17672 6 RIP ignores invalid packet (which means packet failing to authen- ticate, or with incorrect version number, and not supporting com =~ mand), Please check whether the configuration related to RIP protocol is correct and proper. 17673 17673 6 The RIP neighbor is invalid. Please check whether the configuration related to RIP protocol is correct and proper, the network link status is normal and the router corresponding to RIP neighbor is running normally. 17676 17676 6 The RIP interface status turns to down Please check whehter the link status is normal and whether the system is running normally. 58 Confidential and Proprietary Information of ZTE CORPORATION