SMSC 4.2 Alarms Rev 0.1

SMSC 4.2

Alarm Reference Manual

P/N 10-000-1050 March 07 Issue 1, Rev. 0.1

DRAFT

Notice

This document contains proprietary and confidential material of Comverse, Inc. Any unauthorizedreproduction, use, or disclosure of this material, or any part thereof, is strictly prohibited. Thisdocument is solely for the use of Comverse, Inc. employees and authorized Comverse, Inc. customers.

The material furnished in this document is believed to be accurate and reliable. However, noresponsibility is assumed by Comverse, Inc. for the use of this material. Comverse, Inc. reserves theright to make changes to the material at any time and without notice.

This document is intended for information and operational purposes only. No part of this documentshall constitute any contractual commitment whatsoever by Comverse, Inc.

© 2004–2007 Comverse, Inc. All rights reserved.

Comverse, its logo, the spark design, Kenan, and Netcentrex are registered trademarks of ComverseTechnology, Inc. or its subsidiaries in the United States and may also be registered in other countries.

OMNI is a trademark of Comverse, Inc.

Cajun is a registered trademark of Avaya, Inc.

Catalyst Switches 4948, 3550, 2950 are registered trademarks of Cisco Systems, Inc.

AAM is a registered trademark of EMC Legato, Inc.

OpenView and DL 580 are registered trademarks of Hewlett-Packard Development Company, L.P.

ODM and OnGuard are registered trademarks of Integrity Systems, Ltd.

Langley II and NIC Intel Pro 1000 Dual Port are registered trademarks of Intel Corporation.

Linux is a registered trademark of Linus Torvalds.

Passport is a registered trademark of Nortel Networks, Ltd.

Oracle 9.1 Server, Oracle Discoverer are registered trademarks of Oracle Corp.

LSI Raid is a registered trademark of Q Logic Corp.

Web Server Director is a registered trademark or RADWARE.

Red Hat Linux is a registered trademark of Red Hat, Inc.

Silicom Quad Copper PCIX Server Adapter U is a registered trademark of Silicom Corp.

Linux EMANATE is a registered trademark of SNMP Research, Inc.

Solaris and Sun Netra are registered trademarks of Sun Microsystems, Inc.

Jaguar Card is a registered trademark of Ulticom Inc.

Foundation Suite is a registered trademark of VERITAS Software Corporation.

Other denoted product names of Comverse or other companies may be trademarks or registeredtrademarks of Comverse, Inc. or its subsidiaries, or their respective owners.

Corporate Headquarters100 Quannapowitt ParkwayWakefield, MA 01880 USATel: (781) 246-9000

DRAFT

Fax: (781) 224-8143www.comverse.com

DRAFT

Table of Contents

1 Introduction to Alarms.............................................................................. 11.1 Alarms Overview............................................................................................................... 21.2 Alarm Agents...................................................................................................................... 31.3 Alarm Format ..................................................................................................................... 41.4 Alarm Notification ............................................................................................................. 51.5 Unit EMS Access ................................................................................................................ 61.6 Alarm Fields Description.................................................................................................. 71.7 Alarms by Unit ................................................................................................................. 10

2 SMSC SNMP Traps ...................................................................................... 122.1 SMSC SNMP Traps Overview....................................................................................... 132.2 SMSC Component Traps ................................................................................................ 142.3 SMSC Connection Traps ................................................................................................. 162.4 SMSC Database Traps ..................................................................................................... 192.5 SMSC Generic Traps........................................................................................................ 202.6 SMSC Application Specific Traps ................................................................................. 212.6.1 CCS-EI Traps..................................................................................................................... 212.6.2 OMAP Traps ..................................................................................................................... 212.7 SMSC Trap Varbinds....................................................................................................... 232.8 Cluster Traps..................................................................................................................... 26

3 Hardware Agent Alarms ........................................................................ 293.1 Hardware Agent Alarms Overview ............................................................................. 303.2 EMC Alarms...................................................................................................................... 313.2.1 Alarm 3030202 .................................................................................................................. 313.2.2 Alarm 3030203 .................................................................................................................. 313.2.3 Alarm 3030204 (Log only) .............................................................................................. 323.2.4 Alarm 3030205 (Log only) .............................................................................................. 323.2.5 Alarm 3030210 (Log only) .............................................................................................. 333.2.6 Alarm 3030211 (Log only) .............................................................................................. 333.2.7 Alarm 3030212 (Log only) .............................................................................................. 333.2.8 Alarm 3030215 .................................................................................................................. 343.2.9 Alarm 3030239 .................................................................................................................. 343.2.10 Alarm 3030240 .................................................................................................................. 353.2.11 Alarm 3030241 (Log only) .............................................................................................. 35

SMSC 4.2 Alarm Reference Manual iP/N 10-000-1050 Issue 1 Rev. 0.1

DRAFT

Table of Contents

3.2.12 Alarm 3030247 .................................................................................................................. 363.2.13 Alarm 3030250 .................................................................................................................. 363.2.14 Alarm 3030251 (Log only) .............................................................................................. 363.2.15 Alarm 3030402 (Log only) .............................................................................................. 373.2.16 Alarm 3030403 .................................................................................................................. 373.2.17 Alarm 3030406 (Log only) .............................................................................................. 383.2.18 Alarm 3030407 (Log only) .............................................................................................. 383.2.19 Alarm 3030408 .................................................................................................................. 383.2.20 Alarm 3030409 (Log only) .............................................................................................. 393.2.21 Alarm 3030410 (Log only) .............................................................................................. 393.2.22 Alarm 3030411 .................................................................................................................. 403.2.23 Alarm 3030412 .................................................................................................................. 403.2.24 Alarm 3030413 .................................................................................................................. 413.2.25 Alarm 3030414 .................................................................................................................. 413.2.26 Alarm 3030415 .................................................................................................................. 423.2.27 Alarm 3030416 (Log only) .............................................................................................. 423.2.28 Alarm 3030501 .................................................................................................................. 423.2.29 Alarm 3030503 .................................................................................................................. 433.2.30 Alarm 3030508 .................................................................................................................. 443.2.31 Alarm 3030509 .................................................................................................................. 443.2.32 Alarm 3030510 .................................................................................................................. 453.2.33 Alarm 3030512 .................................................................................................................. 453.2.34 Alarm 3030513 .................................................................................................................. 463.2.35 Alarm 3030524 .................................................................................................................. 463.2.36 Alarm 3030526 .................................................................................................................. 473.2.37 Alarm 3030528 .................................................................................................................. 483.2.38 Alarm 3030601 .................................................................................................................. 483.2.39 Alarm 3030602 .................................................................................................................. 493.2.40 Alarm 3030603 .................................................................................................................. 493.2.41 Alarm 3030604 .................................................................................................................. 503.2.42 Alarm 3030605 .................................................................................................................. 503.2.43 Alarm 3030607 .................................................................................................................. 513.2.44 Alarm 3030608 .................................................................................................................. 513.2.45 Alarm 3030612 .................................................................................................................. 523.2.46 Alarm 3030613 .................................................................................................................. 523.2.47 Alarm 3030614 .................................................................................................................. 533.2.48 Alarm 3030615 .................................................................................................................. 533.2.49 Alarm 3030616 .................................................................................................................. 543.2.50 Alarm 3030617 .................................................................................................................. 54

SMSC 4.2 Alarm Reference Manual iiP/N 10-000-1050 Issue 1 Rev. 0.1

DRAFT

Table of Contents

3.2.51 Alarm 3030618 .................................................................................................................. 553.2.52 Alarm 3030619 .................................................................................................................. 553.2.53 Alarm 3030620 .................................................................................................................. 563.2.54 Alarm 3030622 .................................................................................................................. 563.2.55 Alarm 3030629 .................................................................................................................. 573.2.56 Alarm 3030633 .................................................................................................................. 573.2.57 Alarm 3030639 .................................................................................................................. 583.2.58 Alarm 3030640 .................................................................................................................. 593.2.59 Alarm 3030641 .................................................................................................................. 593.2.60 Alarm 3030653 .................................................................................................................. 603.2.61 Alarm 3030654 .................................................................................................................. 613.2.62 Alarm 3030655 .................................................................................................................. 613.2.63 Alarm 3030656 .................................................................................................................. 623.2.64 Alarm 3030658 .................................................................................................................. 623.2.65 Alarm 3030659 .................................................................................................................. 633.2.66 Alarm 3030660 .................................................................................................................. 633.2.67 Alarm 3030702 .................................................................................................................. 643.2.68 Alarm 3030704 .................................................................................................................. 643.2.69 Alarm 3030709 .................................................................................................................. 653.2.70 Alarm 3030714 .................................................................................................................. 653.2.71 Alarm 3030730 .................................................................................................................. 663.2.72 Alarm 3030731 .................................................................................................................. 663.2.73 Alarm 3030805 .................................................................................................................. 673.2.74 Alarm 3030806 .................................................................................................................. 673.2.75 Alarm 3030809 .................................................................................................................. 683.2.76 Alarm 3030816 .................................................................................................................. 683.2.77 Alarm 3030821 .................................................................................................................. 693.2.78 Alarm 3030822 .................................................................................................................. 693.2.79 Alarm 3030823 .................................................................................................................. 703.2.80 Alarm 3030824 .................................................................................................................. 703.2.81 Alarm 3030825 .................................................................................................................. 713.2.82 Alarm 3030830 (Log only) .............................................................................................. 713.2.83 Alarm 3030832 .................................................................................................................. 713.2.84 Alarm 3030833 (Log only) .............................................................................................. 723.2.85 Alarm 3030834 .................................................................................................................. 723.2.86 Alarm 3031002 .................................................................................................................. 733.2.87 Alarm 3031046 .................................................................................................................. 733.2.88 Alarm 3031110 .................................................................................................................. 743.2.89 Alarm 3031124 .................................................................................................................. 74

SMSC 4.2 Alarm Reference Manual iiiP/N 10-000-1050 Issue 1 Rev. 0.1

DRAFT

Table of Contents

3.2.90 Alarm 3031142 .................................................................................................................. 753.2.91 Alarm 3031172 .................................................................................................................. 753.2.92 Alarm 3031232 .................................................................................................................. 763.2.93 Alarm 3032121 .................................................................................................................. 773.2.94 Alarm 3032122 .................................................................................................................. 773.2.95 Alarm 3032131 .................................................................................................................. 783.2.96 Alarm 3032168 .................................................................................................................. 783.2.97 Alarm 3032169 .................................................................................................................. 793.2.98 Alarm 3032190 .................................................................................................................. 793.2.99 Alarm 3032238 .................................................................................................................. 803.2.100 Alarm 3032239 .................................................................................................................. 803.2.101 Alarm 3032243 .................................................................................................................. 813.2.102 Alarm 3032253 .................................................................................................................. 813.2.103 Alarm 3032403 .................................................................................................................. 823.2.104 Alarm 3035708 .................................................................................................................. 823.2.105 Alarm 3035723 .................................................................................................................. 833.2.106 Alarm 3035749 .................................................................................................................. 843.2.107 Alarm 3035750 .................................................................................................................. 843.2.108 Alarm 3037004 .................................................................................................................. 853.2.109 Alarm 3037061 .................................................................................................................. 853.2.110 Alarm 3037062 .................................................................................................................. 863.2.111 Alarm 3037075 .................................................................................................................. 863.2.112 Alarm 3037076 .................................................................................................................. 873.2.113 Alarm 3037102 .................................................................................................................. 873.2.114 Alarm 3037113 .................................................................................................................. 883.2.115 Alarm 3037122 .................................................................................................................. 883.2.116 Alarm 3037123 .................................................................................................................. 893.2.117 Alarm 3037315 .................................................................................................................. 893.2.118 Alarm 3037339 .................................................................................................................. 903.2.119 Alarm 3039062 .................................................................................................................. 913.2.120 Alarm 3039063 .................................................................................................................. 913.2.121 Alarm 3039065 (Log only) .............................................................................................. 923.2.122 Alarm 3039066 (Log only) .............................................................................................. 923.2.123 Alarm 3039069 .................................................................................................................. 933.2.124 Alarm 3039070 .................................................................................................................. 933.2.125 Alarm 3039071 (Log only) .............................................................................................. 943.2.126 Alarm 3039073 (Log only) .............................................................................................. 943.2.127 Alarm 3039074 .................................................................................................................. 943.2.128 Alarm 3039075 (Log only) .............................................................................................. 95

SMSC 4.2 Alarm Reference Manual ivP/N 10-000-1050 Issue 1 Rev. 0.1

DRAFT

Table of Contents

3.2.129 Alarm 3039076 (Log only) .............................................................................................. 953.2.130 Alarm 3039077 (Log only) .............................................................................................. 963.2.131 Alarm 3039079 .................................................................................................................. 963.2.132 Alarm 3039090 (Log only) .............................................................................................. 963.2.133 Alarm 3039091 (Log only) .............................................................................................. 973.2.134 Alarm 3039092 (Log only) .............................................................................................. 973.2.135 Alarm 3039094 .................................................................................................................. 983.2.136 Alarm 3039103 .................................................................................................................. 983.2.137 Alarm 3039134 (Log only) .............................................................................................. 993.2.138 Alarm 3039148 .................................................................................................................. 993.2.139 Alarm 3039149 ................................................................................................................ 1003.2.140 Alarm 3039150 ................................................................................................................ 1003.2.141 Alarm 3039151 (Log only) ............................................................................................ 1013.2.142 Alarm 3039152 ................................................................................................................ 1013.2.143 Alarm 3039153 ................................................................................................................ 1013.2.144 Alarm 3039154 ................................................................................................................ 1023.2.145 Alarm 3039155 ................................................................................................................ 1033.2.146 Alarm 3039156 ................................................................................................................ 1033.2.147 Alarm 3039157 ................................................................................................................ 1043.2.148 Alarm 3039158 ................................................................................................................ 1043.2.149 Alarm 3039159 ................................................................................................................ 1053.2.150 Alarm 3039160 ................................................................................................................ 1053.2.151 Alarm 3039161 ................................................................................................................ 1063.2.152 Alarm 3039162 (Log only) ............................................................................................ 1073.2.153 Alarm 3039163 ................................................................................................................ 1073.2.154 Alarm 3039164 ................................................................................................................ 1083.2.155 Alarm 3039165 ................................................................................................................ 1083.2.156 Alarm 3039166 ................................................................................................................ 1093.2.157 Alarm 3039167 ................................................................................................................ 1103.2.158 Alarm 3039169 ................................................................................................................ 1103.2.159 Alarm 3039170 ................................................................................................................ 1103.3 Langley 4 Alarms........................................................................................................... 1123.3.1 Alarm 4090101 ................................................................................................................ 1123.3.2 Alarm 4090102 ................................................................................................................ 1123.3.3 Alarm 4090103 ................................................................................................................ 1123.3.4 Alarm 4090104 ................................................................................................................ 1133.3.5 Alarm 4090105 ................................................................................................................ 1133.3.6 Alarm 4090106 ................................................................................................................ 1143.3.7 Alarm 4090107 ................................................................................................................ 114

SMSC 4.2 Alarm Reference Manual vP/N 10-000-1050 Issue 1 Rev. 0.1

DRAFT

Table of Contents

3.3.8 Alarm 4090108 ................................................................................................................ 1153.3.9 Alarm 4090109 ................................................................................................................ 1153.3.10 Alarm 4090110 ................................................................................................................ 1163.3.11 Alarm 4090111 ................................................................................................................ 1163.3.12 Alarm 4090112 ................................................................................................................ 1173.3.13 Alarm 4090113 ................................................................................................................ 1173.3.14 Alarm 4090114 ................................................................................................................ 1183.3.15 Alarm 4090115 ................................................................................................................ 1183.3.16 Alarm 4090116 ................................................................................................................ 1183.3.17 Alarm 4090117 ................................................................................................................ 1193.3.18 Alarm 4090118 ................................................................................................................ 1193.3.19 Alarm 4090119 ................................................................................................................ 1203.3.20 Alarm 4090120 ................................................................................................................ 1203.3.21 Alarm 4090121 ................................................................................................................ 1213.3.22 Alarm 4090122 ................................................................................................................ 1213.3.23 Alarm 4090123 ................................................................................................................ 1223.3.24 Alarm 4090125 ................................................................................................................ 1223.3.25 Alarm 4090126 ................................................................................................................ 1233.3.26 Alarm 4090127 ................................................................................................................ 1243.3.27 Alarm 4090128 ................................................................................................................ 1253.3.28 Alarm 4090129 ................................................................................................................ 1253.3.29 Alarm 4090130 ................................................................................................................ 1263.3.30 Alarm 4090131 ................................................................................................................ 1273.3.31 Alarm 4090132 ................................................................................................................ 1283.3.32 Alarm 4090133 ................................................................................................................ 1283.3.33 Alarm 4090134 ................................................................................................................ 1293.3.34 Alarm 4090135 ................................................................................................................ 1293.3.35 Alarm 4090136 ................................................................................................................ 1303.3.36 Alarm 4090137 ................................................................................................................ 1303.3.37 Alarm 4090138 ................................................................................................................ 1313.3.38 Alarm 4090139 ................................................................................................................ 1313.3.39 Alarm 4090140 ................................................................................................................ 1323.3.40 Alarm 4090141 ................................................................................................................ 1323.3.41 Alarm 4090142 ................................................................................................................ 1333.3.42 Alarm 4090143 ................................................................................................................ 1333.3.43 Alarm 4090144 ................................................................................................................ 1343.3.44 Alarm 4090145 ................................................................................................................ 1343.3.45 Alarm 4090146 ................................................................................................................ 1353.3.46 Alarm 4090147 ................................................................................................................ 135

SMSC 4.2 Alarm Reference Manual viP/N 10-000-1050 Issue 1 Rev. 0.1

DRAFT

Table of Contents

3.3.47 Alarm 4090148 ................................................................................................................ 1353.3.48 Alarm 4090149 ................................................................................................................ 1363.3.49 Alarm 4090150 ................................................................................................................ 1363.3.50 Alarm 4090151 ................................................................................................................ 1373.3.51 Alarm 4090152 ................................................................................................................ 1383.3.52 Alarm 4090153 ................................................................................................................ 1383.3.53 Alarm 4090154 ................................................................................................................ 1393.3.54 Alarm 4090155 ................................................................................................................ 1393.3.55 Alarm 4090156 ................................................................................................................ 1403.3.56 Alarm 4090157 ................................................................................................................ 1413.4 LSI Alarms....................................................................................................................... 1423.4.1 Alarm 3080001 ................................................................................................................ 1423.4.2 Alarm 3080003 ................................................................................................................ 1423.4.3 Alarm 3080004 ................................................................................................................ 1423.4.4 Alarm 3080005 ................................................................................................................ 1433.4.5 Alarm 3080006 ................................................................................................................ 1433.4.6 Alarm 3080007 ................................................................................................................ 1443.4.7 Alarm 3080008 ................................................................................................................ 1443.4.8 Alarm 3080009 ................................................................................................................ 1453.4.9 Alarm 3080010 ................................................................................................................ 1453.4.10 Alarm 3080011 ................................................................................................................ 1453.4.11 Alarm 3080012 ................................................................................................................ 1463.4.12 Alarm 3080013 ................................................................................................................ 1463.4.13 Alarm 3080014 ................................................................................................................ 1473.4.14 Alarm 3080019 ................................................................................................................ 1473.4.15 Alarm 3080022 ................................................................................................................ 1483.4.16 Alarm 3080050 ................................................................................................................ 1483.4.17 Alarm 3080051 ................................................................................................................ 1493.4.18 Alarm 3080052 ................................................................................................................ 1493.4.19 Alarm 3080054 ................................................................................................................ 1493.4.20 Alarm 3080059 ................................................................................................................ 1503.4.21 Alarm 3080067 ................................................................................................................ 1503.4.22 Alarm 3080068 ................................................................................................................ 1513.4.23 Alarm 3080069 ................................................................................................................ 1513.4.24 Alarm 3080070 ................................................................................................................ 1523.4.25 Alarm 3080071 ................................................................................................................ 1523.4.26 Alarm 3080073 ................................................................................................................ 1533.4.27 Alarm 3080074 ................................................................................................................ 1533.4.28 Alarm 3080075 ................................................................................................................ 154

SMSC 4.2 Alarm Reference Manual viiP/N 10-000-1050 Issue 1 Rev. 0.1

DRAFT

Table of Contents


SMSC 4.2 Alarm Reference Manual viiiP/N 10-000-1050 Issue 1 Rev. 0.1

DRAFT

Table of Contents


SMSC 4.2 Alarm Reference Manual ixP/N 10-000-1050 Issue 1 Rev. 0.1

DRAFT

Table of Contents

3.4.107 Alarm 3080439 ................................................................................................................ 1883.4.108 Alarm 3080440 ................................................................................................................ 1893.4.109 Alarm 3080441 ................................................................................................................ 1893.4.110 Alarm 3080519 ................................................................................................................ 1893.4.111 Alarm 3080520 ................................................................................................................ 1903.4.112 Alarm 3080521 ................................................................................................................ 1903.4.113 Alarm 3080522 ................................................................................................................ 1913.4.114 Alarm 3080644 ................................................................................................................ 1913.4.115 Alarm 3080645 ................................................................................................................ 1923.4.116 Alarm 3080700 ................................................................................................................ 1923.4.117 Alarm 3080701 ................................................................................................................ 1923.4.118 Alarm 3080702 ................................................................................................................ 1933.4.119 Alarm 3080800 ................................................................................................................ 1933.4.120 Alarm 3080801 ................................................................................................................ 1943.4.121 Alarm 3080806 ................................................................................................................ 1943.4.122 Alarm 3080807 ................................................................................................................ 1943.4.123 Alarm 3080808 ................................................................................................................ 1953.4.124 Alarm 3080809 ................................................................................................................ 1953.5 Netra 240/440 Hardware Alarms (OnGuard Agent) .............................................. 1973.5.1 Alarm 2112042 ................................................................................................................ 1973.5.2 Alarm 2112043 ................................................................................................................ 1973.5.3 Alarm 2112044 ................................................................................................................ 1983.5.4 Alarm 2112045 ................................................................................................................ 1983.5.5 Alarm 2112046 ................................................................................................................ 1983.5.6 Alarm 2112047 ................................................................................................................ 1993.5.7 Alarm 2112048 ................................................................................................................ 1993.5.8 Alarm 2112049 ................................................................................................................ 2003.5.9 Alarm 2112050 ................................................................................................................ 2003.5.10 Alarm 2112051 ................................................................................................................ 2013.5.11 Alarm 2112052 ................................................................................................................ 2013.5.12 Alarm 2112053 ................................................................................................................ 2023.5.13 Alarm 2112054 ................................................................................................................ 2023.5.14 Alarm 2112055 ................................................................................................................ 2023.5.15 Alarm 2112056 ................................................................................................................ 2033.5.16 Alarm 2112057 ................................................................................................................ 2033.5.17 Alarm 2112058 ................................................................................................................ 2043.5.18 Alarm 2112059 ................................................................................................................ 2043.5.19 Alarm 2112060 ................................................................................................................ 2053.5.20 Alarm 2112061 ................................................................................................................ 205

SMSC 4.2 Alarm Reference Manual xP/N 10-000-1050 Issue 1 Rev. 0.1

DRAFT

Table of Contents


SMSC 4.2 Alarm Reference Manual xiP/N 10-000-1050 Issue 1 Rev. 0.1

DRAFT

Table of Contents

3.5.60 Alarm 2112101 ................................................................................................................ 2233.5.61 Alarm 2112102 ................................................................................................................ 2233.5.62 Alarm 2112103 ................................................................................................................ 2243.5.63 Alarm 2112104 ................................................................................................................ 2243.5.64 Alarm 2112105 ................................................................................................................ 2253.5.65 Alarm 2112106 ................................................................................................................ 2253.5.66 Alarm 2112107 ................................................................................................................ 2263.6 Q-Logic Alarms .............................................................................................................. 2273.6.1 Alarm 2990000 ................................................................................................................ 2273.6.2 Alarm 2990101 ................................................................................................................ 2273.6.3 Alarm 2990102 ................................................................................................................ 2273.6.4 Alarm 2990103 ................................................................................................................ 2273.6.5 Alarm 2990104 ................................................................................................................ 2283.6.6 Alarm 2990105 ................................................................................................................ 2283.6.7 Alarm 2990106 ................................................................................................................ 2283.6.8 Alarm 2990107 ................................................................................................................ 2293.6.9 Alarm 2990108 ................................................................................................................ 2293.6.10 Alarm 2990109 ................................................................................................................ 2293.6.11 Alarm 2990110 ................................................................................................................ 2303.6.12 Alarm 2990111 ................................................................................................................ 2303.6.13 Alarm 2990112 ................................................................................................................ 2303.6.14 Alarm 2990113 ................................................................................................................ 2303.6.15 Alarm 2990114 ................................................................................................................ 2313.6.16 Alarm 2990115 ................................................................................................................ 2313.6.17 Alarm 2990301 ................................................................................................................ 2313.6.18 Alarm 2990401 ................................................................................................................ 2323.6.19 Alarm 2990402 ................................................................................................................ 2323.6.20 Alarm 2990403 ................................................................................................................ 2323.6.21 Alarm 2990404 ................................................................................................................ 2333.6.22 Alarm 2990405 ................................................................................................................ 2333.6.23 Alarm 2990501 ................................................................................................................ 2333.6.24 Alarm 2990502 ................................................................................................................ 2343.6.25 Alarm 2990503 ................................................................................................................ 2343.6.26 Alarm 2990504 ................................................................................................................ 2343.6.27 Alarm 2990505 ................................................................................................................ 2343.6.28 Alarm 2990601 (Q-Logic - Port status has changes to unknown with bypassed

state.) ................................................................................................................................ 2353.6.29 Alarm 2990601 (Q-Logic - Port status has changes to unknown with diagnostics

state.) ................................................................................................................................ 235

SMSC 4.2 Alarm Reference Manual xiiP/N 10-000-1050 Issue 1 Rev. 0.1

DRAFT

Table of Contents

3.6.30 Alarm 2990601 (Q-Logic - Port status has changes to unknown with offline state.)........................................................................................................................................... 235

3.6.31 Alarm 2990601 (Q-Logic - Port status has changes to unknown with onlinestate.) ................................................................................................................................ 236

3.6.32 Alarm 2990601 (Q-Logic - Port status has changes to unknown with unknownstate.) ................................................................................................................................ 236

3.6.33 Alarm 2990602 (Q-Logic - Port status has changes to unused with bypassedstate.) ................................................................................................................................ 236

3.6.34 Alarm 2990602 (Q-Logic - Port status has changes to unused with diagnosticsstate.) ................................................................................................................................ 237

3.6.35 Alarm 2990602 (Q-Logic - Port status has changes to unused with offlinestate.) ................................................................................................................................ 237

3.6.36 Alarm 2990602 (Q-Logic - Port status has changes to unused with onlinestate.) ................................................................................................................................ 237

3.6.37 Alarm 2990602 (Q-Logic - Port status has changes to unused with unknownstate.) ................................................................................................................................ 237

3.6.38 Alarm 2990603 (Q-Logic - Port status has changes to ready with bypassedstate.) ................................................................................................................................ 238

3.6.39 Alarm 2990603 (Q-Logic - Port status has changes to ready with diagnosticsstate.) ................................................................................................................................ 238

3.6.40 Alarm 2990603 (Q-Logic - Port status has changes to ready with offlinestate.) ................................................................................................................................ 238

3.6.41 Alarm 2990603 (Q-Logic - Port status has changes to ready with online state.).. 2393.6.42 Alarm 2990603 (Q-Logic - Port status has changes to ready with unknown

state.) ................................................................................................................................ 2393.6.43 Alarm 2990604 (Q-Logic - Port status has changes to warning with bypassed

state.) ................................................................................................................................ 2393.6.44 Alarm 2990604 (Q-Logic - Port status has changes to warning with diagnostics

state.) ................................................................................................................................ 2403.6.45 Alarm 2990604 (Q-Logic - Port status has changes to warning with offline

state.) ................................................................................................................................ 2403.6.46 Alarm 2990604 (Q-Logic - Port status has changes to warning with online

state.) ................................................................................................................................ 2403.6.47 Alarm 2990604 (Q-Logic - Port status has changes to warning with unknown

state.) ................................................................................................................................ 2403.6.48 Alarm 2990605 (Q-Logic - Port status has changes to failure with bypassed

state.) ................................................................................................................................ 2413.6.49 Alarm 2990605 (Q-Logic - Port status has changes to failure with diagnostics

state.) ................................................................................................................................ 2413.6.50 Alarm 2990605 (Q-Logic - Port status has changes to failure with offline

state.) ................................................................................................................................ 2413.6.51 Alarm 2990605 (Q-Logic - Port status has changes to failure with online

state.) ................................................................................................................................ 2423.6.52 Alarm 2990605 (Q-Logic - Port status has changes to failure with unknown

state.) ................................................................................................................................ 242

SMSC 4.2 Alarm Reference Manual xiiiP/N 10-000-1050 Issue 1 Rev. 0.1

DRAFT

Table of Contents

3.6.53 Alarm 2990606 (Q-Logic - Port status has changes to not participating withbypassed state.)............................................................................................................... 242

3.6.54 Alarm 2990606 (Q-Logic - Port status has changes to not participating withdiagnostics state.) ........................................................................................................... 243

3.6.55 Alarm 2990606 (Q-Logic - Port status has changes to not participating withoffline state.).................................................................................................................... 243

3.6.56 Alarm 2990606 (Q-Logic - Port status has changes to not participating withonline state.) .................................................................................................................... 243

3.6.57 Alarm 2990606 (Q-Logic - Port status has changes to not participating withunknown state.) .............................................................................................................. 243

3.6.58 Alarm 2990607 (Q-Logic - Port status has changes to initializing with bypassedstate.) ................................................................................................................................ 244

3.6.59 Alarm 2990607 (Q-Logic - Port status has changes to initializing with diagnosticsstate.) ................................................................................................................................ 244

3.6.60 Alarm 2990607 (Q-Logic - Port status has changes to initializing with offlinestate.) ................................................................................................................................ 244

3.6.61 Alarm 2990607 (Q-Logic - Port status has changes to initializing with onlinestate.) ................................................................................................................................ 245

3.6.62 Alarm 2990607 (Q-Logic - Port status has changes to initializing with unknownstate.) ................................................................................................................................ 245

3.6.63 Alarm 2990608 (Q-Logic - Port status has changes to bypass with bypassedstate.) ................................................................................................................................ 245

3.6.64 Alarm 2990608 (Q-Logic - Port status has changes to bypass with diagnosticsstate.) ................................................................................................................................ 246

3.6.65 Alarm 2990608 (Q-Logic - Port status has changes to bypass with offline state.)........................................................................................................................................... 246

3.6.66 Alarm 2990608 (Q-Logic - Port status has changes to bypass with onlinestate.) ................................................................................................................................ 246

3.6.67 Alarm 2990608 (Q-Logic - Port status has changes to bypass with unknownstate.) ................................................................................................................................ 246

3.6.68 Alarm 2990609 (Q-Logic - Port status has changes tools with bypassed state.).. 2473.6.69 Alarm 2990609 (Q-Logic - Port status has changes tools with diagnostics

state.) ................................................................................................................................ 2473.6.70 Alarm 2990609 (Q-Logic - Port status has changes tools with offline state.) ..... 2473.6.71 Alarm 2990609 (Q-Logic - Port status has changes tools with online state.)...... 2483.6.72 Alarm 2990609 (Q-Logic - Port status has changes tools with unknown state.).. 2483.6.73 Alarm 2990610 (Q-Logic - Port status has changes to other with bypassed

state.) ................................................................................................................................ 2483.6.74 Alarm 2990610 (Q-Logic - Port status has changes to other with diagnostics

state.) ................................................................................................................................ 2493.6.75 Alarm 2990610 (Q-Logic - Port status has changes to other with offline state.).. 2493.6.76 Alarm 2990610 (Q-Logic - Port status has changes to other with online state.).. 2493.6.77 Alarm 2990610 (Q-Logic - Port status has changes to other with unknown

state.) ................................................................................................................................ 250

SMSC 4.2 Alarm Reference Manual xivP/N 10-000-1050 Issue 1 Rev. 0.1

DRAFT

Table of Contents

3.6.78 Alarm 2990701 ................................................................................................................ 2503.6.79 Alarm 2990801 ................................................................................................................ 2503.6.80 Alarm 2991001 ................................................................................................................ 2503.6.81 Alarm 2991002 ................................................................................................................ 2513.6.82 Alarm 2991003 ................................................................................................................ 2513.6.83 Alarm 2991004 ................................................................................................................ 2513.6.84 Alarm 2991005 ................................................................................................................ 2523.6.85 Alarm 2991006 ................................................................................................................ 2523.6.86 Alarm 2991007 ................................................................................................................ 2523.6.87 Alarm 2991008 ................................................................................................................ 2523.6.88 Alarm 2991009 ................................................................................................................ 2533.6.89 Alarm 2991101 ................................................................................................................ 2533.6.90 Alarm 2991102 ................................................................................................................ 2533.6.91 Alarm 2991103 ................................................................................................................ 254

4 OS Agent Alarms ......................................................................................... 2554.1 OS Agent Alarm Overview.......................................................................................... 2564.2 CCS_OS Alarms.............................................................................................................. 2574.2.1 Alarm 4087005 ................................................................................................................ 2574.2.2 Alarm 4087006 ................................................................................................................ 2574.2.3 Alarm 4087501 ................................................................................................................ 2574.2.4 Alarm 4087504 ................................................................................................................ 2584.3 SUN OS Alarms (OnGuard Agent) ............................................................................ 2594.3.1 Alarm 2112001 ................................................................................................................ 2594.3.2 Alarm 2112002 ................................................................................................................ 2594.3.3 Alarm 2112003 ................................................................................................................ 2604.3.4 Alarm 2112004 ................................................................................................................ 2604.3.5 Alarm 2112005 ................................................................................................................ 2604.3.6 Alarm 2112006 ................................................................................................................ 2614.3.7 Alarm 2112007 ................................................................................................................ 2614.3.8 Alarm 2112008 ................................................................................................................ 2624.3.9 Alarm 2112009 ................................................................................................................ 2634.3.10 Alarm 2112010 ................................................................................................................ 2634.3.11 Alarm 2112011 ................................................................................................................ 2634.3.12 Alarm 2112012 ................................................................................................................ 2644.3.13 Alarm 2112013 ................................................................................................................ 2644.3.14 Alarm 2112014 ................................................................................................................ 2654.3.15 Alarm 2112015 ................................................................................................................ 265

SMSC 4.2 Alarm Reference Manual xvP/N 10-000-1050 Issue 1 Rev. 0.1

DRAFT

Table of Contents

4.3.16 Alarm 2112016 ................................................................................................................ 2664.3.17 Alarm 2112017 ................................................................................................................ 2664.3.18 Alarm 2112018 ................................................................................................................ 2674.3.19 Alarm 2112019 ................................................................................................................ 2674.3.20 Alarm 2112020 ................................................................................................................ 2684.3.21 Alarm 2112021 ................................................................................................................ 2684.3.22 Alarm 2112022 ................................................................................................................ 2684.3.23 Alarm 2112023 ................................................................................................................ 2694.3.24 Alarm 2112024 ................................................................................................................ 2694.3.25 Alarm 2112025 ................................................................................................................ 2704.3.26 Alarm 2112026 ................................................................................................................ 2704.3.27 Alarm 2112027 ................................................................................................................ 2714.3.28 Alarm 2112028 ................................................................................................................ 2714.3.29 Alarm 2112029 ................................................................................................................ 2724.3.30 Alarm 2112030 ................................................................................................................ 2724.3.31 Alarm 2112031 ................................................................................................................ 2734.3.32 Alarm 2112032 ................................................................................................................ 2734.3.33 Alarm 2112033 ................................................................................................................ 2734.3.34 Alarm 2112034 ................................................................................................................ 2744.3.35 Alarm 2112035 ................................................................................................................ 2754.3.36 Alarm 2112036 ................................................................................................................ 2754.4 Health Probe Alarms..................................................................................................... 2764.4.1 Alarm 2980001 ................................................................................................................ 2764.4.2 Alarm 2980002 ................................................................................................................ 2764.4.3 Alarm 2980003 ................................................................................................................ 2774.4.4 Alarm 2980004 ................................................................................................................ 277

5 Cluster Agent Alarms............................................................................. 2795.1 Cluster Agent Alarms Overview................................................................................. 2805.2 SUN Cluster HA Alarms (OnGuard Agent)............................................................. 2815.2.1 Alarm 2113042 ................................................................................................................ 2815.2.2 Alarm 2113043 ................................................................................................................ 2815.2.3 Alarm 2113044 ................................................................................................................ 2815.2.4 Alarm 2113045 ................................................................................................................ 2825.2.5 Alarm 2113046 ................................................................................................................ 2825.2.6 Alarm 2113047 ................................................................................................................ 2835.2.7 Alarm 2113048 ................................................................................................................ 2835.2.8 Alarm 2113049 ................................................................................................................ 284

SMSC 4.2 Alarm Reference Manual xviP/N 10-000-1050 Issue 1 Rev. 0.1

DRAFT

Table of Contents

5.2.9 Alarm 2113050 ................................................................................................................ 2845.2.10 Alarm 2113051 ................................................................................................................ 2855.3 Veritas 3.5 Cluster Alarms ........................................................................................... 2865.3.1 Alarm 2121011 ................................................................................................................ 2865.3.2 Alarm 2121012 ................................................................................................................ 2865.3.3 Alarm 2121013 ................................................................................................................ 2875.3.4 Alarm 2121014 ................................................................................................................ 2875.3.5 Alarm 2121015 ................................................................................................................ 2885.3.6 Alarm 2121016 ................................................................................................................ 2885.3.7 Alarm 2121021 ................................................................................................................ 2885.3.8 Alarm 2121022 ................................................................................................................ 2895.3.9 Alarm 2121023 ................................................................................................................ 2895.3.10 Alarm 2121024 ................................................................................................................ 2905.3.11 Alarm 2121025 ................................................................................................................ 2905.3.12 Alarm 2121026 ................................................................................................................ 2915.3.13 Alarm 2121027 ................................................................................................................ 2915.3.14 Alarm 2121028 ................................................................................................................ 2925.3.15 Alarm 2121029 ................................................................................................................ 2925.3.16 Alarm 2121031 ................................................................................................................ 2935.3.17 Alarm 2121032 ................................................................................................................ 2935.3.18 Alarm 2121033 ................................................................................................................ 2935.3.19 Alarm 2121034 ................................................................................................................ 2945.3.20 Alarm 2121035 ................................................................................................................ 2945.3.21 Alarm 2121036 ................................................................................................................ 2955.3.22 Alarm 2121037 ................................................................................................................ 2955.3.23 Alarm 2121062 ................................................................................................................ 2965.3.24 Alarm 2121081 ................................................................................................................ 2965.3.25 Alarm 2121082 ................................................................................................................ 297

6 Networking Agent Alarms ................................................................ 2986.1 Networking Agent Alarms Overview........................................................................ 2996.2 Cajun Alarms .................................................................................................................. 3006.2.1 Alarm 2810027 ................................................................................................................ 3006.2.2 Alarm 2810028 ................................................................................................................ 3006.2.3 Alarm 2810044 ................................................................................................................ 3006.2.4 Alarm 2810046 ................................................................................................................ 3016.2.5 Alarm 2810048 ................................................................................................................ 3016.2.6 Alarm 2810050 ................................................................................................................ 302

SMSC 4.2 Alarm Reference Manual xviiP/N 10-000-1050 Issue 1 Rev. 0.1

DRAFT

Table of Contents

6.2.7 Alarm 2810052 ................................................................................................................ 3026.2.8 Alarm 2810054 ................................................................................................................ 3026.2.9 Alarm 2810079 ................................................................................................................ 3036.2.10 Alarm 2810081 ................................................................................................................ 3036.2.11 Alarm 2810083 ................................................................................................................ 3036.2.12 Alarm 2810085 ................................................................................................................ 3046.2.13 Alarm 2810087 ................................................................................................................ 3046.2.14 Alarm 2810089 ................................................................................................................ 3056.2.15 Alarm 2810091 ................................................................................................................ 3056.2.16 Alarm 2810093 ................................................................................................................ 3056.2.17 Alarm 2810600 ................................................................................................................ 3066.2.18 Alarm 2810602 ................................................................................................................ 3066.2.19 Alarm 2810603 ................................................................................................................ 3066.2.20 Alarm 2810604 ................................................................................................................ 3076.2.21 Alarm 2812315 ................................................................................................................ 3076.2.22 Alarm 2812316 ................................................................................................................ 3086.2.23 Alarm 2812317 ................................................................................................................ 3086.2.24 Alarm 2812318 ................................................................................................................ 3086.3 Others Alarms................................................................................................................. 3106.3.1 Alarm 2820001 ................................................................................................................ 3106.3.2 Alarm 2820002 ................................................................................................................ 3106.3.3 Alarm 2820003 ................................................................................................................ 3116.3.4 Alarm 2820004 ................................................................................................................ 3116.3.5 Alarm 2820005 ................................................................................................................ 3126.3.6 Alarm 2820006 ................................................................................................................ 3126.3.7 Alarm 2820007 ................................................................................................................ 3136.3.8 Alarm 2820008 ................................................................................................................ 3146.3.9 Alarm 2820009 ................................................................................................................ 3146.3.10 Alarm 2820010 ................................................................................................................ 3156.3.11 Alarm 2820011 ................................................................................................................ 3156.3.12 Alarm 2820012 ................................................................................................................ 3166.3.13 Alarm 2820013 ................................................................................................................ 3166.3.14 Alarm 2820014 ................................................................................................................ 3176.3.15 Alarm 2820015 ................................................................................................................ 3186.3.16 Alarm 2820016 ................................................................................................................ 3186.3.17 Alarm 2820017 ................................................................................................................ 3196.3.18 Alarm 2820018 ................................................................................................................ 3206.3.19 Alarm 2820019 ................................................................................................................ 3206.3.20 Alarm 2820020 ................................................................................................................ 321

SMSC 4.2 Alarm Reference Manual xviiiP/N 10-000-1050 Issue 1 Rev. 0.1

DRAFT

Table of Contents

6.3.21 Alarm 2820021 ................................................................................................................ 3216.3.22 Alarm 2820022 ................................................................................................................ 3226.3.23 Alarm 2820023 ................................................................................................................ 3226.3.24 Alarm 2820024 ................................................................................................................ 3236.3.25 Alarm 2820025 ................................................................................................................ 3236.3.26 Alarm 2820026 ................................................................................................................ 3246.3.27 Alarm 2820027 ................................................................................................................ 3246.3.28 Alarm 2820028 ................................................................................................................ 3256.3.29 Alarm 2820029 ................................................................................................................ 3266.3.30 Alarm 2820030 ................................................................................................................ 3266.3.31 Alarm 2820031 ................................................................................................................ 3276.3.32 Alarm 2820032 ................................................................................................................ 3276.3.33 Alarm 2820033 ................................................................................................................ 3286.3.34 Alarm 2820034 ................................................................................................................ 328

7 Application Agent Alarms ................................................................ 3307.1 Application Agent Alarms Overview ........................................................................ 3317.2 CCS_CC Alarms ............................................................................................................. 3327.2.1 Alarm 1465330 ................................................................................................................ 3327.2.2 Alarm 1465331 ................................................................................................................ 3327.2.3 Alarm 1465350 ................................................................................................................ 3337.2.4 Alarm 1467902 ................................................................................................................ 3337.2.5 Alarm 1469110 ................................................................................................................ 3347.3 GenericDatabase Alarms............................................................................................... 3357.3.1 Alarm 2113062 ................................................................................................................ 3357.3.2 Alarm 2113063 ................................................................................................................ 3357.3.3 Alarm 2113064 ................................................................................................................ 3357.3.4 Alarm 2113065 ................................................................................................................ 3357.3.5 Alarm 2113066 ................................................................................................................ 3367.4 OMNI Alarms................................................................................................................. 3377.4.1 Alarm 1418001 ................................................................................................................ 3377.4.2 Alarm 1418201 ................................................................................................................ 3377.4.3 Alarm 2113052 ................................................................................................................ 3387.4.4 Alarm 2113053 ................................................................................................................ 3387.4.5 Alarm 2113054 ................................................................................................................ 3387.4.6 Alarm 2113055 ................................................................................................................ 3387.4.7 Alarm 2113056 ................................................................................................................ 3397.5 Oracle Database Alarms (OnGuard Agent) .............................................................. 340

SMSC 4.2 Alarm Reference Manual xixP/N 10-000-1050 Issue 1 Rev. 0.1

DRAFT

Table of Contents


SMSC 4.2 Alarm Reference Manual xxP/N 10-000-1050 Issue 1 Rev. 0.1

DRAFT

Table of Contents


SMSC 4.2 Alarm Reference Manual xxiP/N 10-000-1050 Issue 1 Rev. 0.1

DRAFT

Table of Contents


SMSC 4.2 Alarm Reference Manual xxiiP/N 10-000-1050 Issue 1 Rev. 0.1

DRAFT

Table of Contents


SMSC 4.2 Alarm Reference Manual xxiiiP/N 10-000-1050 Issue 1 Rev. 0.1

DRAFT

Table of Contents

7.5.157 Alarm 2112095 ................................................................................................................ 4087.5.158 Alarm 2112096 ................................................................................................................ 4097.5.159 Alarm 2112097 ................................................................................................................ 4097.5.160 Alarm 2112098 ................................................................................................................ 4107.5.161 Alarm 2112099 ................................................................................................................ 4107.5.162 Alarm 2112100 ................................................................................................................ 4117.5.163 Alarm 2112101 ................................................................................................................ 4117.5.164 Alarm 2112102 ................................................................................................................ 4127.5.165 Alarm 2112103 ................................................................................................................ 4127.5.166 Alarm 2112104 ................................................................................................................ 4137.5.167 Alarm 2112105 ................................................................................................................ 4137.5.168 Alarm 2112106 ................................................................................................................ 4147.5.169 Alarm 2112107 ................................................................................................................ 4147.6 Server Monitor (SMU) Alarms .................................................................................... 4157.6.1 Alarm 1990001 (The \inetd\ process is not running anymore)............................ 4157.6.2 Alarm 1990001 (The \inetd\ process is running).................................................... 4157.6.3 Alarm 1990002 (CPU utilization (<$VALUE>%) exceeds configured threshold

(<$THRESHOLD>%.) .................................................................................................... 4167.6.4 Alarm 1990002 (CPU utilization (<$VALUE>%) is ok) .......................................... 4167.6.5 Alarm 1990003 (Utilization of file-system <fileSystem> (<$VALUE>%) exceeds

configured threshold <$THRESHOLD>%.) .............................................................. 4177.6.6 Alarm 1990003 (Utilization of file-system <fileSystem> (<$VALUE>%) is ok).. 4177.6.7 Alarm 1990004 (Process table utilization (<$VALUE>%) exceeds configured

threshold (<$THRESHOLD>%)................................................................................... 4187.6.8 Alarm 1990004 (Process table utilization (<$VALUE>%) is ok) ........................... 4187.6.9 Alarm 1990005 (SWAP Utilization (<$VALUE>%) exceeds configured threshold

(<$THRESHOLD>%)).................................................................................................... 4197.6.10 Alarm 1990005 (SWAP Utilization (<$VALUE>%) is ok) ...................................... 4197.6.11 Alarm 1990006 (Distribution files for <$VALUE> node(s) exist) ......................... 4197.6.12 Alarm 1990006 (Distribution files for 0 node(s) exist) ............................................ 4207.6.13 Alarm 1990007 ................................................................................................................ 4207.6.14 Alarm 1991001 (Failed login of <user> on <tty>) ................................................... 4217.6.15 Alarm 1991001 (Resource <resource_name> is faulted) ......................................... 4217.6.16 Alarm 1991002 (Cron command of <user> with pid <pid> failed (rc = <rc>)).. 4227.6.17 Alarm 1991002 (Group <group_name> is faulted).................................................. 4227.6.18 Alarm 1991003 (System reboot)................................................................................... 4237.6.19 Alarm 1991003 (Group <group_name> is offline) ................................................... 4237.6.20 Alarm 1991004 ................................................................................................................ 4237.6.21 Alarm 1991005 ................................................................................................................ 4247.6.22 Alarm 1991006 ................................................................................................................ 424

SMSC 4.2 Alarm Reference Manual xxivP/N 10-000-1050 Issue 1 Rev. 0.1

DRAFT

Table of Contents

7.6.23 Alarm 1991007 ................................................................................................................ 4257.6.24 Alarm 1991008 ................................................................................................................ 4257.6.25 Alarm 1991009 ................................................................................................................ 4257.6.26 Alarm 1991010 ................................................................................................................ 4267.6.27 Alarm 1991011 ................................................................................................................ 4267.6.28 Alarm 1991012 ................................................................................................................ 4277.6.29 Alarm 1992001 ................................................................................................................ 4277.6.30 Alarm 1992001 (Cleared) .............................................................................................. 4277.6.31 Alarm 1992003 ................................................................................................................ 4287.6.32 Alarm 1992004 (Log Only) ........................................................................................... 4287.6.33 Alarm 1992004 ................................................................................................................ 4287.6.34 Alarm 1992005 ................................................................................................................ 4297.6.35 Alarm 1992006 ................................................................................................................ 4297.6.36 Alarm 1992529 ................................................................................................................ 4307.6.37 Alarm 1992530 ................................................................................................................ 4307.6.38 Alarm 1992700 ................................................................................................................ 4317.6.39 Alarm 1992804 ................................................................................................................ 4317.6.40 Alarm 1992805 ................................................................................................................ 4317.6.41 Alarm 1992829 ................................................................................................................ 4327.6.42 Alarm 1992830 ................................................................................................................ 4327.6.43 Alarm 1992832 ................................................................................................................ 4337.6.44 Alarm 1992965 ................................................................................................................ 4337.6.45 Alarm 1992972 ................................................................................................................ 4347.6.46 Alarm 1992973 ................................................................................................................ 4347.6.47 Alarm 1992974 ................................................................................................................ 4347.6.48 Alarm 1993097 ................................................................................................................ 4357.6.49 Alarm 1993098 ................................................................................................................ 4357.6.50 Alarm 1993101 ................................................................................................................ 4367.6.51 Alarm 1993102 ................................................................................................................ 4367.6.52 Alarm 1993108 ................................................................................................................ 4367.6.53 Alarm 1993115 ................................................................................................................ 4377.6.54 Alarm 1993117 ................................................................................................................ 4377.6.55 Alarm 1993122 ................................................................................................................ 4387.6.56 Alarm 1993236 ................................................................................................................ 4387.6.57 Alarm 1993458 ................................................................................................................ 4387.6.58 Alarm 1993466 ................................................................................................................ 4397.6.59 Alarm 1993600 ................................................................................................................ 4397.6.60 Alarm 1993605 ................................................................................................................ 4407.6.61 Alarm 1993802 ................................................................................................................ 440

SMSC 4.2 Alarm Reference Manual xxvP/N 10-000-1050 Issue 1 Rev. 0.1

DRAFT

Table of Contents

7.6.62 Alarm 1994001 ................................................................................................................ 4417.6.63 Alarm 1994002 ................................................................................................................ 4417.6.64 Alarm 1994003 ................................................................................................................ 4417.6.65 Alarm 1994004 ................................................................................................................ 4427.6.66 Alarm log only (Node Up)........................................................................................... 4427.6.67 Alarm log only (ovpause completed without errors) ............................................. 4437.6.68 Alarm log only (ovresume completed without errors)........................................... 4437.6.69 Alarm log only (ovspmd resumed process (<process name>) outside os the

control of the ovresume)............................................................................................... 4437.6.70 Alarm log only (Process (<process name>) resumed itself after timing out and

after ovpause/ovresume has completed.) ................................................................. 4447.6.71 Alarm log only (HP OpenView Data Warehouse is back up) .............................. 4447.7 SPM Agent Alarms ........................................................................................................ 4467.7.1 Alarm 1700001 ................................................................................................................ 4467.7.2 Alarm 1700002 ................................................................................................................ 4467.7.3 Alarm 1701001 ................................................................................................................ 4477.7.4 Alarm 1701002 ................................................................................................................ 4477.7.5 Alarm 1702001 ................................................................................................................ 4487.7.6 Alarm 1702002 ................................................................................................................ 4487.8 SMSC Alarms.................................................................................................................. 4497.8.1 Alarm 1140001 (Component down. Termination reason is UNPLANNED.) ..... 4497.8.2 Alarm 1140001 (Component up. Role is UNKNOWN.) ......................................... 4497.8.3 Alarm 1140001 (smsCompDownUnknown. Component down. Termination

reason is UNKNOWN) ................................................................................................. 4507.8.4 Alarm 1140001 (Log only) (Component up. Role is ACTIVE.) ............................. 4507.8.5 Alarm 1140001 (Log only) (Component up. Role is CLUSTERED.)..................... 4507.8.6 Alarm 1140001 (Log only) (Component up. Role is STANDALONE.)................ 4517.8.7 Alarm 1140001 (Log only) (Component up. Role is STANDBY.) ......................... 4517.8.8 Alarm 1140001 (Log only) (smsCompDownPlanned. Component down.

Termination reason is PLANNED). ............................................................................ 4527.8.9 Alarm 1140002 (Component changed role to ACTIVE.) ........................................ 4527.8.10 Alarm 1140002 (Component changed role to CLUSTERED.) ................................ 4537.8.11 Alarm 1140002 (Component changed role to STANDALONE.) ........................... 4537.8.12 Alarm 1140002 (Component changed role to STANDBY.) .................................... 4537.8.13 Alarm 1140002 (Component changed role to UNKNOWN.) ................................ 4547.8.14 Alarm 1140003 (A message burst was encountered on <name>. Burst size is

<burstCurrentSize>.) ..................................................................................................... 4547.8.15 Alarm 1140003 (A message burst was encountered. Burst size is

<burstCurrentSize>.) ..................................................................................................... 4557.8.16 Alarm 1140003 (A message burst was encountered on <name>. Burst size is

<burstCurrentSize>.) ..................................................................................................... 455

SMSC 4.2 Alarm Reference Manual xxviP/N 10-000-1050 Issue 1 Rev. 0.1

DRAFT

Table of Contents

7.8.17 Alarm 1140003 (A message burst was encountered. Burst size is<burstCurrentSize>.) ..................................................................................................... 456

7.8.18 Alarm 1140003 (Log only) ............................................................................................ 4567.8.19 Alarm 1140004 (Component message rate for license <name> has reached

<percent>%.) ................................................................................................................... 4577.8.20 Alarm 1140004 (Component message rate for license <name> has reached

maximum.) ...................................................................................................................... 4587.8.21 Alarm 1140004 (Component message rate for license <name> is <percent>%.).. 4587.8.22 Alarm 1140004 (Log only) ............................................................................................ 4587.8.23 Alarm 1140005 ................................................................................................................ 4597.8.24 Alarm 1140005 (Log only) ............................................................................................ 4607.8.25 Alarm 1140006 (Disconnected from <compIdClassTo> <compIdInstanceTo>

<currentCount> out of <*.totalCount> connections are up.)................................. 4607.8.26 Alarm 1140006 (Disconnected from <compIdClassTo>:<compIdInstanceTo>.).. 4607.8.27 Alarm 1140006 (Log only) ............................................................................................ 4617.8.28 Alarm 1140007 ................................................................................................................ 4617.8.29 Alarm 1140007 (Log only) ............................................................................................ 4627.8.30 Alarm 1140008 (The connection focus to <compIdClassTo>:<compIdInstanceTo>

switched to ACTIVE.) ................................................................................................... 4637.8.31 Alarm 1140008 (The connection focus to

<compIdClassTo>:<compIdInstanceTo>switched to STANDALONE.) ............. 4637.8.32 Alarm 1140008 (The connection focus to <compIdClassTo>:<compIdInstanceTo>

switched to STANDBY.) .............................................................................................. 4647.8.33 Alarm 1140008 (The connection focus to

<compIdClassTo>:<compIdInstanceTo>switched to UNKNOWN.) ................... 4647.8.34 Alarm 1140009 (The capacity of the dialog-table in front of

<compIdClassTo><compIdInstanceTo> reached <percent>%.) ........................... 4657.8.35 Alarm 1140009 (The capacity of the dialog-table in front of

<compIdClassTo>:<compIdInstanceTo>reached <percent>%.) ............................ 4657.8.36 Alarm 1140009 (Log only) ............................................................................................ 4667.8.37 Alarm 1140010 (The Capacity of the DB-table <dbName> reached

<percent>%.) ................................................................................................................... 4667.8.38 Alarm 1140010 (The DB-table <dbName> reached its full capacity.) .................. 4677.8.39 Alarm 1140010 (Log only) ............................................................................................ 4677.8.40 Alarm 1140011 ................................................................................................................ 4687.8.41 Alarm 1140012 ................................................................................................................ 4687.8.42 Alarm 1140012 (Log only) ............................................................................................ 4697.8.43 Alarm 1140013 ................................................................................................................ 4697.8.44 Alarm 1140013 (Log only) ............................................................................................ 4707.8.45 Alarm 1140014 ................................................................................................................ 4707.8.46 Alarm 1140015 ................................................................................................................ 4717.8.47 Alarm 1140015 (Log only) ............................................................................................ 471

SMSC 4.2 Alarm Reference Manual xxviiP/N 10-000-1050 Issue 1 Rev. 0.1

DRAFT

Table of Contents

7.8.48 Alarm 1140016 ................................................................................................................ 4727.8.49 Alarm 1140016 (Log only) ............................................................................................ 4737.8.50 Alarm 1140017 ................................................................................................................ 4737.8.51 Alarm 1140017 (Log only) ............................................................................................ 4747.8.52 Alarm 1141001 (SMS component down due to failure.)......................................... 4747.8.53 Alarm 1141001 (SMS component down for maintenance.) .................................... 4747.8.54 Alarm 1141002 ................................................................................................................ 4757.8.55 Alarm 1141006 (Disconnected from <compIdClassTo> <compIdInstanceTo>.).. 4757.8.56 Alarm 1141006 (Disconnected from <compIdClassTo>

<compIdInstanceTo>.<currentCount> out of <*.totalCount>connections are up.) ..................................................................................................... 475

7.8.57 Alarm 1141007 ................................................................................................................ 4767.8.58 Alarm 1142006 ................................................................................................................ 4767.8.59 Alarm 1142006 (Log only) ............................................................................................ 4777.8.60 Alarm 1143006 ................................................................................................................ 4777.8.61 Alarm 1410002 (Association is down <association name>.) .................................. 4787.8.62 Alarm 1410002 (Link <number> <name> failed.).................................................... 4787.8.63 Alarm 1410002 (Link <number> <name> not failed.) ............................................ 4787.8.64 Alarm 1410003 ................................................................................................................ 4797.8.65 Alarm 1410004 (Link <number> <name> local inhibited.) .................................... 4797.8.66 Alarm 1410004 (Link <number> <name> not local inhibited.)............................. 4797.8.67 Alarm 1410006 (Link <number> <name> not remote inhibited.)......................... 4797.8.68 Alarm 1410006 (Link <number> <name> remote inhibited.)................................ 4807.8.69 Alarm 1410008 (Link <number> <name> not remotely blocked.) ....................... 4807.8.70 Alarm 1410008 (Link <number> <name> remotely blocked.)............................... 4807.8.71 Alarm 1410010 (Link <number> <name> locally blocked.)................................... 4817.8.72 Alarm 1410010 (Link <number> <name> not locally blocked.)............................ 4817.8.73 Alarm 1410012 (Route set <number> <name> Accessible.)................................... 4817.8.74 Alarm 1410012 (Route set <number> <name> NOT Accessible.) ........................ 4817.8.75 Alarm 1410014 (Route set <number> <name> Congestion level is <level>.) .... 4827.8.76 Alarm 1410014 (Route set <number> <name> Congestion level is Low.).......... 4827.8.77 Alarm 1410016 (RSSN <number> RPC <number(s)> ALLOWED.) ..................... 4827.8.78 Alarm 1410016 (RSSN <number> RPC <number(s)> CONGESTED.) ................. 4837.8.79 Alarm 1410016 (RSSN <number> RPC <number(s)> PROHIBITED.) ................. 4837.8.80 Alarm 1410016 (RSSN <number> RPC <number(s)> UNEQUIPPED.) ............... 4837.8.81 Alarm 1410017 (LSSN <number> ALLOWED.) ....................................................... 4837.8.82 Alarm 1410017 (LSSN <number> PROHIBITED.) ................................................... 4847.8.83 Alarm 1410017 (LSSN <number> UNEQUIPPED.) ................................................. 4847.9 Possibly Used Traps ...................................................................................................... 4857.9.1 GenericBackup Alarms.................................................................................................. 485

SMSC 4.2 Alarm Reference Manual xxviiiP/N 10-000-1050 Issue 1 Rev. 0.1

DRAFT

Table of Contents

7.9.2 GenericHardware Alarms............................................................................................. 4867.9.3 GenericOS Alarms.......................................................................................................... 4877.9.4 SPM Agent Alarms ........................................................................................................ 489

SMSC 4.2 Alarm Reference Manual xxixP/N 10-000-1050 Issue 1 Rev. 0.1

DRAFT

Preface

Target AudienceThis information is intended for high-level service engineers and maintenancepersonnel responsible for resolving alarms and troubleshooting system components.

Related DocumentsFor more information, see:

■ SMU 4.0 Monitoring Guide: Provides instructions for system administrators formonitoring system components and viewing alarm details, and for performingcluster operation and maintenance procedures for the Site Management Unit(SMU).

■ External Monitoring for CMA 5.0.10 Interface Description Document: Describesthe Host Interface for Alarms (HIL) and SNMP V2/V3 interfaces between theSMU Comverse Agent (CMA) and the external Network Operations Center(NOC).

SMSC 4.2 Alarm Reference Manual xxxP/N 10-000-1050 Issue 1 Rev. 0.1

DRAFT

Introduction to Alarms 1■ Alarms Overview, Page 2

■ Alarm Agents, Page 3

■ Alarm Format, Page 4

■ Alarm Notification, Page 5

■ Unit EMS Access, Page 6

■ Alarm Fields Description, Page 7

■ Alarms by Unit, Page 10

DRAFT

1: Introduction to Alarms Alarms Overview

1.1 Alarms OverviewEvent monitoring and management in the system is performed by the SiteManagement Unit (SMU). The SMU receives SNMP notifications from SNMP agentsthat monitor the system components, processes the data, and generates alarmsaccording to predefined templates. The alarms are described in:

■ Alarm Format, Page 4

■ Alarm Notification, Page 5

SMSC 4.2 Alarm Reference Manual 2 of 492P/N 10-000-1050 Issue 1 Rev. 0.1

DRAFT

1: Introduction to Alarms Alarm Agents

1.2 Alarm AgentsEach system unit hosts a number of agents or subagents that monitor the ManagedElements (MEs) on the unit. These subagents include:

■ Platform Subagents: Monitor events relating to the unit platform (Intel, Langley,and Sun), the operating system (Linux, Windows, and Sun), and hardware(for example, fans and disks). These subagents function as layered packagescommon to several units in the system, for example, all Linux-based units in thesystem have the same platform subagents with different application agents.

■ Process Control Subagents: Monitor the health of application and serviceprocesses co-hosted on a single unit, update the process state in the processtable, report process activation and deactivation to the manager, and collectinformation on resource consumption of each process, such as CPU andmemory usage.

■ Application Subagents: Monitor a specific application or service.■ Third-Party Agents: Monitor hardware and software supplied with specific

units, for example, Nortel and Sun. These agents monitor the related component.

Related Information:

Alarm Agents, Page 3

Alarm Notification, Page 5


DRAFT

1: Introduction to Alarms Alarm Format

1.3 Alarm FormatThe alarms generated and processed by the system are recorded in a specific formatwith predefined fields.

The format in which the alarms are presented and the predefined fields differdepending on the GUI or the format the alarms are viewed in. The alarms canbe viewed as follows:

■ Alarm Notification Tables: The alarms tables created by the external interfacesand stored in MIB files. For a detailed description of the MIB Alarm fields, seethe External Monitoring for CMA 5.0.10 Interface Description Document.

■ SMU Alarm Browser Pane: The alarms are displayed in table format in the SMUGUI Browser Pane, from which you can access further details for each alarm.

■ Alarm List: A comprehensive list of all possible alarms that can be generated bythe system.For a comparison of the alarm field names, see Alarm Fields Description, Page 7.

Parent Topic: Alarms Overview, Page 2

Alarm Notification, Page 5


DRAFT

1: Introduction to Alarms Alarm Notification

1.4 Alarm NotificationThe SMU performs alarm notification in the following ways:

■ Alarm Forwarding: The CMA on the SMU forwards alarms to NOCs using thefollowing supported protocols:□ SNMP X.733-Compliant Interfaces (SNMP V2 and V3)□ HIL-SNMP v1□ HIL-FTP□ HIL-TCEach interface supports a specific protocol type, and filtering and mapping rules.

■ Siren Notification: The SMU notifies the Alarm Interface Module (AIM) of thealarm. The AIM has colored LEDs that indicate the severity (Critical, Major,or Minor) of active alarms in the system and an extra LED that indicates thestatus of the SMU itself.

Parent Topic: Alarms Overview, Page 2

Alarm Format, Page 4


DRAFT

1: Introduction to Alarms Unit EMS Access

1.5 Unit EMS AccessYou can remotely access and manage SMSC units using Element ManagementSystems (EMS).

Table 1 describes the EMS used to manage the SMSC system units.

Table 1: SMSCUnit EMS Access Unit EMS

BLU Backup Library Console

CMS Telephony SUI on SMU

DSU ■ Legato Backup Console■ OnGuard Console■ SunOne Console■ SUI-MIB2■ Sun Console■ MIPS Console

FC Switch FC Switch Console

FWU Firewall Console

EMC EMC Storage Console

HSBN JDM

LBA ConfigWare

Linux Units SUI-MIB2

Linux/Windows Units MAM-SUI

OMU TCM SUI

RCU RAS Finder

RKVM RKVM Console

SAN GW SAN Gateway Console

SMU SUI-MIB2

OnGuard Console

VM-ASU MTA (MIPS) Console


Alarms by Unit, Page 10


DRAFT

1: Introduction to Alarms Alarm Fields Description

1.6 Alarm Fields DescriptionTable 2 describes the alarm fields used to define the alarms listed by alarm agentand includes the equivalent field names in the Alarm Notification Table and SMUGUI Browser Pane.

Table 2: AlarmFields Alarm Fields Alarm

Notification TableSMU GUIBrowser Pane

Description

Specific Problem Specific Problem Application The unique identifierof the alarm, alsocalled the Alarm ID.

Each alarm isidentified by a uniqueseven-digit number.

The first three digitsare a prefix specificto each type of agentand the next fourdigits are the alarmswhich are numberedfrom 0000 to 9999(four digits) withinthe same type ofagent.

Managed Object Managed ObjectClass

Not Included The name of theagent, also calledthe Managed ObjectClass (MOC).

Description Alarm Text Message Text The alarm message.

AdditionalInformation


Not Included Additionalinformation aboutthe alarm, forexample, possiblecauses, variableexplanations, andany other relevantinformation aboutthe alarm.


DRAFT


Alarm Fields AlarmNotification Table

SMU GUIBrowser Pane

Description

Severity Perceived Severity Severity The severitylevel of the faultaccording to ITU-TRecommendationX.733, as follows:■ Indeterminate

(Unknown)■ Critical■ Major■ Minor■ Warning■ Cleared

(Normal)

Message GroupProbable Cause)

Probable Cause Msg Grp The MessageGroup ID basedon predefined rules:■ Hardware■ Application■ Communication /

Network■ Operating

System■ Resource /

Capacity■ Performance■ High Availability■ Database■ Miscellaneous

AlarmAutomaticallyCleared

Not Included Not Included Whether the alarmis automaticallycleared, and bywhich Alarm ID.Possible values are:■ Yes; by <Specific

Problem>: Thealarm is clearedby anotheralarm.

■ No: The alarmcan onlybe clearedmanually.


DRAFT


Alarm Fields AlarmNotification Table

SMU GUIBrowser Pane

Description

Threshold ThresholdInformation

Not Included The severitythreshold levels, aslisted in the Severityrow.

System Impact Not Included Not Included The impact the faultsituation has on thenormal operation ofthe system.

RecommendedCorrective Action

Not Included Not Included The proceduresneeded to correctthe fault situation asrecommended byComverse customersupport.


Alarms Overview, Page 2

Alarms by Unit, Page 10


DRAFT

1: Introduction to Alarms Alarms by Unit

1.7 Alarms by UnitTable 3 lists the units and their corresponding alarm agents in the SMSC system.

Table 3: Alarmsby Unit Unit Component Agent Reference

CCS_CC CCS_CC CCS_CC Alarms, Page 332

OMNI OMNI OMNI Alarms, Page 337CCS

CCS_OS CCS_OS CCS_OS Alarms, Page 257

LSI LSI LSI Alarms, Page 142

SUN Cluster HA On Guard SUN Cluster HA Alarms(OnGuard Agent),Page 281

OS Resources On Guard SUN OS Alarms (OnGuardAgent), Page 259

Oracle OnGuard Oracle Database Alarms(OnGuard Agent),Page 340

Netra 240/440 HW On Guard Netra 240/440 HardwareAlarms (OnGuard Agent),Page 197

SPM SPM Agent SPM Agent Alarms,Page 446

DSU

VERITAS VERITAS Veritas 3.5 Cluster Alarms,Page 286

EMC Storage EMC EMC SNMP Agent EMC Alarms, Page 31

DMZ-HSBU Cajun Switch Cajun Agent Cajun Alarms, Page 300

SMU Server MonitorSMU

Server Monitor (SMU)Alarms, Page 415

VERITAS VERITAS Veritas 3.5 Cluster Alarms,Page 286

OS Resources On Guard SUN OS Alarms (OnGuardAgent), Page 259

Oracle OnGuard Oracle Database Alarms(OnGuard Agent),Page 340

RKVM

Netra 240/440 HW On Guard Netra 240/440 HardwareAlarms (OnGuard Agent),Page 197

SMU Server MonitorSMU

Server Monitor (SMU)Alarms, Page 415

TRM

VERITAS Cluster3.5

VERITAS Cluster Veritas 3.5 Cluster Alarms,Page 286


DRAFT

1: Introduction to Alarms Alarms by Unit


Alarms Overview, Page 2

Alarm Fields Description, Page 7


DRAFT

SMSC SNMP Traps 2■ SMSC SNMP Traps Overview, Page 13

■ SMSC Component Traps, Page 14

■ SMSC Connection Traps, Page 16

■ SMSC Database Traps, Page 19

■ SMSC Generic Traps, Page 20

■ SMSC Application Specific Traps, Page 21

■ SMSC Trap Varbinds, Page 23

■ Cluster Traps, Page 26

DRAFT

2: SMSC SNMP Traps SMSC SNMP Traps Overview

2.1 SMSC SNMP Traps OverviewSNMP is a widely used international protocol for the management of networks andnetwork focused IT systems. SNMP is extensible, meaning virtually any kind ofdevice can implement it. SNMP is an application layer protocol, which utilizes astandard message format to communicate between Network Management Station(NMS) and SNMP agents.

The SNMP consists of the following components:

■ NMS: An SNMP client application forwards commands to managed devices,then subsequently processes information returned to the management station.

■ SNMP agent: Is a segment of application code running in a managed devicewhich interacts with the management station.

■ MIB: Is usually defined as a standard set of statistical and control variables. Theprecise variables monitored by network devices are custom defined in the MIB.

The following SNMP traps are monitored:

■ SMSC Component Traps, Page 14

■ SMSC Connection Traps, Page 16

■ SMSC Database Traps, Page 19

■ SMSC Generic Traps, Page 20

■ SMSC Application Specific Traps, Page 21

■ OMAP Traps, Page 21

■ SMSC Trap Varbinds, Page 23

■ Cluster Traps, Page 26


DRAFT

2: SMSC SNMP Traps SMSC Component Traps

2.2 SMSC Component TrapsThis set of traps describes events that concern the availability of various softwarecomponents (usually processes) within the SMSC. While these traps are used bySMSC components, including MRE, different components implement differentcomponent traps.

Two main aspects of such a component are handled here:

■ The state of a component (that is, whether it is available or not)■ Traffic measurements

Table 4: SMSCComponentTraps

Trap Name Description SeveritysmsCompUp Indicates that a component has gone

up.

When this trap occurs, it should cancelthe trap smsCompDown.

Informational

smsCompDown Indicates that a component hasterminated.

When this trap occurs, it cancels thetrap smsCompUp.

smsCompRoleChanged Indicates that a component haschanged its role.

Informational

smsCompInBurst Indicates that a component hasidentified the beginning of amessage-burst situation.

smsCompOutOfBurst Indicates that a component hasidentified the end of a message-burstsituation.

Informational

smsCompMsgRate Indicates that the rate of incomingmessages in the reporting componenthas increased above a monitoredthreshold of one of the component’slicenses.

smsCompSuccessfulDeliveryRate

Indicates that the rate of successfulmessage deliveries in the reportingcomponent has decreased below amonitored threshold.


DRAFT

2: SMSC SNMP Traps SMSC Component Traps

Trap Name Description SeveritysmsCompLicenseExceeded Indicates that the rate of incoming

messages in a reporting componenthas exceeded one of the component’slicenses.

smsTaskTerminated Indicates that an SMSC task hasterminated.

This trap contains the followingvarbinds:■ taskId: Contains a unique

representation of the task inreference

■ startDateTime and endDateTime:Contains a textual representation ofthe task start and task terminationdate

■ terminationStatus: Indicateswhether the task has terminatednormally or abnormally, and alsodefines the trap’s severity where:□ 0,1 = informational□ 2 = major

■ terminationReason Anenumerated code depictingthe exact nature of the task failure(in case the terminationStatusvarbind is set to unplanned).

For more information, see SMSC TrapVarbinds, Page 23.


SMSC Connection Traps, Page 16

SMSC Database Traps, Page 19

SMSC Generic Traps, Page 20

SMSC Application Specific Traps, Page 21

OMAP Traps, Page 21

SMSC Trap Varbinds, Page 23

Cluster Traps, Page 26


DRAFT

2: SMSC SNMP Traps SMSC Connection Traps

2.3 SMSC Connection TrapsThis set of traps describes events that concern connection availability betweenvarious software components (usually processes) within the SMSC.

Two main aspects of such a connection include:

■ The state of a connection (that is, its availability and level of service)■ Traffic measurements between components on a connection

Because a connection is usually two-way, it is expected that these traps would be reportedfrom both of the SW components that reside in the ends of a given connection. Thisconcept assures that the state of a connection is well understood by both sides.

Table 5: SMSCConnectionTraps

Trap Name Description SeveritysmsConnectionUp Indicates that a connection between

two systems was established.

A similar trap is issued from the othercomponent indicating that the twocomponents see each other.

When this occurs, it cancels the trapsmsConnectionDown

Informational

smsConnectionDown Indicates that a connection betweentwo systems was disconnected.

When this occurs, it cancels the trapsmsConectionUp.

smsConnectionBlocked Indicates that a connection betweentwo systems is blocked (but is stillconnected).

When this occurs, it cancels the trapsmsConnectionUnblocked.

smsConnectionUnblocked Indicates that a connection betweentwo systems is unblocked (and is stillconnected).

When this occurs, it cancels the trapsmsConnectionBlocked.

Informational

smsConnectionSwitchedFocus Indicates a connection with a redundantcounterpart, to which the focus isalways kept to the active component.

When this occurs, it cancels theprevious appearance of that trap (thatbears the same identification var-binds).

The CCS-EI sends this trap wheneverthe CCS it is connected to, performs achange-over.

Informational


DRAFT


Trap Name Description SeveritysmsConnectionTimeOut Indicates that a number of connections,

defined by the count varbind, havetimed-out between the reportingcomponent and the counterpart in thetime-frame, defined by the timeFramevarbind.

This trap contains the followingvarbinds:■ compIdClassFrom and

compIdInstanceFrom: Indicate thespecific process which reports theconnection focus switch.

■ compIdClassTo andCompIdInstanceTo: Indicatethe component to which theconnection focus was switched.For more information, see SMSCTrap Varbinds, Page 23.

When this occurs, it cancels theprevious appearance of that trap (withthe same identification varbinds).

smsConnectionStatus Indicates that the state of a connectionbetween the reporting component andthe counterpart has changed.

This trap contains the followingvarbinds:■ compIdClassFrom and

compIdInstanceFrom: Indicate thespecific process which reports theconnection loss

■ compIdClassTo andCompIdInstanceTo: Indicatethe component to which theconnection focus was switched.


When this occurs, it cancels theprevious appearance of that trap (withthe same identification varbinds).

The trap is cleared by sending it with aperceivedSeverity=clear value.


DRAFT


Trap Name Description SeveritysmsDialogCapacity Indicates that a dialog table that

handles the connection between twocomponents has exceeded a monitoredthreshold.

smsConnectionUtilization Indicates that the overall utilizationof the connection between twocomponents has worsened.


SMSC Component Traps, Page 14




OMAP Traps, Page 21




DRAFT

2: SMSC SNMP Traps SMSC Database Traps

2.4 SMSC Database TrapsSoftware components, which manage any sort of database, can issue these trapsthat report the state of the database. The database is identified by its name usingthe dbName variable binding.

Table 6: SMSCDatabase Traps Trap Name Description Severity

smsDbFull Indicates that a database held bythe reporting component has filled upcompletely.

The trap clears any smsDbCapacitytrap for the same component

Critical

smsDbIntegrityProblem Indicates that a database held by thereporting component has encounteredan integrity problem.

Major

smsDbCapacity Indicates that a database used by thereporting component has exceeded amonitored threshold.

The trap replaces any previous instanceof itself and any previous active instanceof smsDbFull trap which was issued forthe same component.

smsDbNotUpToDate Indicates that a database used by thereporting component is identified as notbeing the most up-to-date.






OMAP Traps, Page 21




DRAFT

2: SMSC SNMP Traps SMSC Generic Traps

2.5 SMSC Generic TrapsThese traps are multipurpose and can be used by any SMSC component on anyindeterminate case. They contain functional information.

Table 7: SMSGeneric Traps Trap Name Description

smsAllPurposeAlarm Indicates that an event, whose description appears inthe eventMessage variable binding, occurred.

For more information, see SMSC Trap Varbinds,Page 23.

smsOperationStatus Indicates that a functional operation within the SMSCsystem, between the reporting component and itscounterpart, has changed its status.






OMAP Traps, Page 21




DRAFT

2: SMSC SNMP Traps SMSC Application Specific Traps

2.6 SMSC Application Specific TrapsThese traps are located under enterprises 5271.3.14.1.41 sub-node, which containsa set of branches that accommodate all the application specific events groupedby the application.

Currently the following applications contain a specific MIB structure:

■ 100 (see CCS-EI Traps, Page 21)■ 200 (see OMAP Traps, Page 21)








2.6.1 CCS-EI TrapsCCS-EI Traps, Page 21 lists the CCS-EI trap.

Table 8: CCS-EITrap Trap Name Description

smsCCSEICicCapacity Indicates that the size of the CIC-table(which is maintained in the CCS but alsovisible to the CCS-EI) has exceeded amonitored threshold.

The percent varbind indicates the currentsize of the table (in percents from its totalcapacity).


The trap is cleared by sending it onceagain with a cleared severity.

Parent Topic: SMSC Application Specific Traps, Page 21


OMAP Traps, Page 21

2.6.2 OMAP TrapsTable 9 lists the OMAP trap.


DRAFT

2: SMSC SNMP Traps SMSC Application Specific Traps

Table 9: OMAPTrap Trap Name Description

smsOMAPLoadTrace Failure Indicates that a failure has occurred duringthe message-trace records loading to theOMAP-DB.

The date field indicates the time of daywhen the failure has occurred.

The trap is never cleared.

Parent Topic: SMSC Application Specific Traps, Page 21


CCS-EI Traps, Page 21


DRAFT

2: SMSC SNMP Traps SMSC Trap Varbinds

2.7 SMSC Trap VarbindsData fields are used as variable bindings in all the traps.

Varbinds marked as deprecated do not exist on each of the traps. They remain in the MIBmerely for backward compatibility.

Table 10: DataTraps Variable Name Description

systemDn A unique name identifying a ManagedObject Instance. The field includes thehostname of the managed system, forexample, SMSC-1a.

perceivedSeverity The severity of a trap.

compIdClassFrom The class of an SMS component, whichhas generated a trap. It contains the classidentifier of such a component in a stringformat, for example, SFE, CCS/MAP,SMPP.

compIdInstanceFrom The group and instance of an SMScomponent which has generated a trap.These identifiers are contained in a periodseparated string format, for example, 1.2.

compIdClassTo The class of an SMS component to whichthe trap is referring. It contains the classidentifier of such component in a stringformat, for example, SFE, CCS/MAP,SMPP.

compIdInstanceTo The group and instance of an SMScomponent to which the trap is referring.These identifiers are contained in a periodseparated string format, for example, 1.2.

dbName The complete name of a database tableor inventory.

percent The part of an entity which is used.

burstCurrentSize The size of a message burst.

eventMessage An all-purpose alarm message text.

date A valid date text.

name An entity name.

timeframe Time-frame representation in seconds.

totalCount A counter representing the total number ofobjects, for example, connections, events,available in a context.


DRAFT


Variable Name DescriptioncurrentCount A counter representing the current number

of objects, for example, connections,available in a context.

compRole The role of a component.

terminationStatus The termination status of a component

connStatus Defines the valid values for describing thestatus of a connection between SMSCcomponents.

smsOperationName A name of an SMSC operation.

clusterSvcOperation Defines the valid values for describing thetype of a cluster service operation.

smsCorrelationMsgSource The IP or hostname of the componentwhich generated the original trap.

smsCorrelationMsgSeverity The set of PerceivedSeverity values in astring notation.

smsCorrelationMsgApplication The exact Comverse ID of the event. Thisis a string notation of a numeric ID (usually7-digits long).

smsCorrelationMsgObject Concatenation of the smsCompClassFromand smsCompInstanceFrom. Theseparator string is colon (:).

smsCorrelationMsgText The actual normalized message text (asit appears in the SMU). The text containsall the data that appeared in the originalvarbinds associated with the original trap.

smsCorrelationMsgService Exact value as in the systemDn varbind.

smsCorrelationMsgKey A unique key containing a concatenationof several other varbinds.

smsCorrelationMsgAckKey A uniqueness key of the acknowledgeevent. Similarly to smsCorrelationMsgKey,this varbinds contains a concatenation ofseveral other varbinds.

taskId A name of an SMSC task.

terminationReason A text representing the exact terminationreason of either a component or a task.

startDateTime Start date and time.

endDateTime End date and time.






DRAFT




OMAP Traps, Page 21



DRAFT

2: SMSC SNMP Traps Cluster Traps

2.8 Cluster TrapsThe following traps belong to the SMSC availability subsystem. They cover eventsgenerated by the temporary monitoring solution for the RHCS system.

All the events below share the following three varbinds:

■ clusterName■ memberName■ serviceName

These varbinds indicate the component in the availability subsystem which reportsthe event.

These traps are located under the enterprises 5271.3.14.1.41 sub-node, whichcontains a set of branches that accommodate all the application specific eventsgrouped by the application.

Table 11: ClusterTraps Trap Name Description Severity

smsSvcEnabled Indicates the cluster leader entity whichenables the service serviceName onthe host memberName. The cluster isidentified by the clusterName varbind.


It replaces any active occurrence of thetrap smsSvcDisabled with the same keyvalues.

Informational

smsSvcDisabled Indicates the cluster leader entity whichdisables the service serviceName onthe host memberName.

the trap contains the following varbinds:■ clusterName: Identifies the cluster

name■ perceivedSeverity: Defined the

trap severity


It replaces any active occurrence of thetrap smsSvcEnabled with the same keyvalues.


DRAFT


Trap Name Description SeveritysmsSvcOperationStatus Indicates that the service (specified

by the varbind) running on hostmemberName within the cluster(specified by the varbind) has identifieda change in the status.

The trap contains the following varbinds:■ serviceName: Specifies the service

running on the host■ clusterName: Specifies the host

name■ clusterSvcOperation: Specifies

the new status■ perceivedSeverity: Specifies the

trap severity


It replaces any active occurrence of thetrap smsSvcEnabled with the same keyvalues.


DRAFT


Trap Name Description SeveritysmsHostUp Indicates that the member-host has

been identified as being part of thecluster.

This trap contains the followingvarbinds:■ memberName: Indicates the

member host■ clusterName: Indicates the cluster

name


When this trap occurs, it cancels thetrap smsHostDown.

smsHostDown Indicates that the member-host hasbeen identified as not being part of thecluster.

This trap contains the followingvarbinds:■ memberName: Indicates the

member host■ clusterName: Indicates the cluster

name


When this trap occurs, it cancels thetrap smsHostUp.







OMAP Traps, Page 21



DRAFT

Hardware Agent Alarms 3■ Hardware Agent Alarms Overview, Page 30

■ EMC Alarms, Page 31

■ Langley 4 Alarms, Page 112

■ LSI Alarms, Page 142

■ Netra 240/440 Hardware Alarms (OnGuard Agent), Page 197

■ Q-Logic Alarms, Page 227

DRAFT

3: Hardware Agent Alarms Hardware Agent Alarms Overview

3.1 Hardware Agent Alarms OverviewHardware Agent alarms monitor the hardware units and generate an alarm if theunit is not functioning properly.

The following Hardware Agent alarms are monitored:

■ EMC Alarms, Page 31

■ Langley 4 Alarms, Page 112

■ LSI Alarms, Page 142

■ Netra 240/440 Hardware Alarms (OnGuard Agent), Page 197

■ Q-Logic Alarms, Page 227


DRAFT

3: Hardware Agent Alarms EMC Alarms

3.2 EMC AlarmsSearch for the alarm you need by its Specific Problem (Alarm ID).

3.2.1 Alarm 3030202

Specific Problem 3030202

Managed Object EMC

Description 0x602: Drive Enabled.


This occurs when:■ A LUN is trespassed. When a trespass occurs, this event

code is repeated for each drive in the RAID group wherethe LUN is bound. The SP taking ownership of the LUNlogs a 602 CRU Enabled, and the SP giving up ownershipof the LUN logs a 606 Unit Shutdown For Trespass event.

■ A hot spare is invoked. The message indicates on whichdrive the LUN is being enabled.

■ The SP boots, reporting which LUNs it owns (excludinghot spares).

■ While hot-spare LUNs are not owned by either SP untilinvoked, the message is still reported. Upon boot, eachSP reports a 602 CRU Enabled for each hot-spare LUN.This lets you know that each SP can see and access thehot-spare LUN. Ownership is not implied.

■ A LUN is brought online after a 906 Unit Shutdown eventhas occurred.

Severity Minor

Message Group(Probable Cause)

Hardware

Alarm AutomaticallyCleared

No


Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.2.2 Alarm 3030203


Managed Object EMC

Description 0x603: CRU Unit Rebuild Started.


FLARE has started a rebuild for a particular LUN contained ona disk due to a fault in the RAID group.


DRAFT


Severity Major


Hardware


Yes; by 3030204

System Impact RAID redundancy for the specific LUN will be lost during therebuild.




3.2.3 Alarm 3030204 (Log only)

Specific Problem 3030204 (Log only).

Managed Object EMC

Description 0x604: CRU Unit Rebuild Completed.


FLARE has completed a rebuild for a particular LUN containedon a disk.

Severity Normal


Hardware


No




Managed Object EMC

Description 0x608: Drive Ready.


The SP has booted or new drive has been inserted.

Severity Normal


Hardware


No



DRAFT




Managed Object EMC

Description 0x630: Fan Installed.


The fan/power supply has been reinstalled.

Severity Normal


Hardware


No




Managed Object EMC

Description 0x631: VSC Installed.


The fan/power supply module has been reinserted.

Severity Normal


Hardware


No




Managed Object EMC

Description 0x639: System Cache Enabled.


The system cache has been enabled.

Severity Normal


DRAFT



Hardware


No


3.2.8 Alarm 3030215


Managed Object EMC

Description 0x654: Cache Dumping.


The Array Cache content has been dumped to the vault disks.

Severity Major


Hardware


Yes; by 3030212

System Impact System performance might be impacted.


Either identify the problem and fix it, or wait for the storagesystem to fix it (for example, wait for the SPS to reach fullcharge or for the vault disks to be rebuilt). When the fault nolonger exists, the storage system automatically re-enablesstorage system write caching.


3.2.9 Alarm 3030239


Managed Object EMC

Description 0x6c0: BE (Backend) Fibre Loop Error.


The back-end (storage array) is faulty.

Severity Critical


Hardware


Yes; by 3030241


DRAFT


System Impact FC connectivity to the back-end will be lost.


Check the back-end loop cables. Check connections fromthe SP to the DAE.


3.2.10 Alarm 3030240


Managed Object EMC

Description 0x6C1: BE (Backend) Fibre Loop Down.


The back-end (storage array) has a fiber loop problem. Thisevent is usually caused by a hardware problem, for example,a disk module or LCC module was pulled out, or a CLARiiONarray powered down or rebooted.

Severity Major


Hardware


Yes; by 3030241



Check the event logs for other errors from these fieldreplaceable units (FRUs).


3.2.11 Alarm 3030241 (Log only)


Managed Object EMC

Description 0x6C3: BE (Backend) Fibre Loop Operational.


The back-end (storage array) fiber loop is up again.

Severity Normal


Hardware


No



DRAFT


3.2.12 Alarm 3030247


Managed Object EMC

Description 0x6e1: Front-end Fibre Loop Event.


The front-end fiber channel loop has encountered an event.

Severity Minor


Hardware


Yes; by 3030251

System Impact Connectivity between the host and the storage system mightbe lost.


Check the status of the link.


3.2.13 Alarm 3030250


Managed Object EMC

Description 0x6e4: Fibre Channel Loop Down.


The front-end fiber channel loop is down. The host might beimpacted.

Severity Major


Hardware


Yes; by 3030251

System Impact Loss of redundancy on front-end FC connectivity will occur,and system performance might be impacted.


Check if the host/switch is connected to the storage ports.


3.2.14 Alarm 3030251 (Log only)


DRAFT



Managed Object EMC

Description 0x6e5: Fibre Channel Loop Up.


The front-end fiber channel loop is up. The host can resumeoperations.

Severity Normal


Hardware


No


3.2.15 Alarm 3030402 (Log only)


Managed Object EMC

Description 0x714: Read cache enabled.


Read caching has been enabled by the administrator.

Severity Normal


Hardware


No


3.2.16 Alarm 3030403


Managed Object EMC

Description 0x715: Read cache disabled.


Read caching has been disabled by the administrator.

Severity Major


Hardware


Yes; by 3030402


DRAFT




Enable the read cache.


3.2.17 Alarm 3030406 (Log only)


Managed Object EMC

Description 0x760: Power Supply A on the xPE is restored.


Power supply A on the xPE has been restored (CX700).

This event is logged for reference and troubleshooting andcannot be cleared.

Severity Normal


Hardware


No


3.2.18 Alarm 3030407 (Log only)


Managed Object EMC

Description 0x761: Power Supply B on xPE is restored.


Power supply B on the xPE has been restored (CX700).


Severity Normal


Hardware


No


3.2.19 Alarm 3030408


DRAFT



Managed Object EMC

Description 0x768: A fan is faulted on the xPE.


One of the fan modules has either failed or been removed.

Severity Major


Hardware


Yes; by 3039090, 3039091



Replace or reinsert the fan module.


3.2.20 Alarm 3030409 (Log only)


Managed Object EMC

Description 0x773: Power Supply A Power on the xPE has been restored.


Power has been restored to power supply A on the xPE(CX700).

Severity Normal


Hardware


No


3.2.21 Alarm 3030410 (Log only)


Managed Object EMC

Description 0x774: Power Supply B Power on the xPE has been restored.


Power has been restored to power supply B on the xPE(CX700).

Severity Normal


DRAFT



Hardware


No


3.2.22 Alarm 3030411


Managed Object EMC

Description 0x775: xPE PSA Power Fail Testing.


The power to power supply A has been interrupted and SPStesting is in progress.

Severity Major


Hardware


Yes; by 3030409

System Impact Power supply redundancy might be lost.


Determine if this is a part of SPS testing.


3.2.23 Alarm 3030412


Managed Object EMC

Description 0x776: xPE PSB Power Fail Testing.


The power to power supply B has been interrupted and SPStesting is in progress.

Severity Major


Hardware


Yes; by 3030410

System Impact Power supply redundancy might be lost.


Determine if this is a part of SPS testing.



DRAFT


3.2.24 Alarm 3030413


Managed Object EMC

Description 0x783: Power Supply A Failure Detected on the xPE.


Power to power supply A in the xPE has been interrupted.This also indicates that the unit is being supplied backuppower by the SPS (CX700).

Severity Major


Hardware


Yes; by 3030409

System Impact Loss of power supply redundancy will occur, and performancewill be impacted due to cache disabling.


Reinsert/replace power supply A on the DPE.


3.2.25 Alarm 3030414


Managed Object EMC

Description 0x784: Power Supply B Failure Detected on the xPE.


Power to power supply B in the xPE has been interrupted.This also indicates that the unit is being supplied backuppower by the SPS (CX700).

Severity Major


Hardware


Yes; by 3030410



Reinsert/replace power supply B on the DPE.



DRAFT


3.2.26 Alarm 3030415


Managed Object EMC

Description 0x78b: Drive was physically removed from the slot.


The storage system has detected that one of the drives hasbeen removed from the storage array.

Severity Major


Hardware


Yes; by 3030416



Check the status of the disks, one of them might be out.


3.2.27 Alarm 3030416 (Log only)


Managed Object EMC

Description 0x78c: Drive was physically inserted into the slot.


The storage system has detected that one of the drives hasbeen placed back into the slot.

Severity Normal


Hardware


No


3.2.28 Alarm 3030501


Managed Object EMC

Description 0x801: Soft SCSI Error.


DRAFT



A SCSI operation failed and needed to be retried. This errorindicates that the retry succeeded.

NOTE: 801 events are not strictly confined to beingdisk-related problems. Soft SCSI errors can indicate a badLCC cable or an LCC not handling back-end bus loop noisecorrectly. Look at the extended status in the CLARiiON log forthe affected drive to determine the cause of the event.


Severity Major


Hardware


No

System Impact If there are recent occurrences of the message, the systemmight have a problem with the back-end loop This might causeloss of connectivity redundancy and impact performance.


Continue monitoring the system for further events. The driveshould only be considered for replacement if the errors recurfrequently.


3.2.29 Alarm 3030503


Managed Object EMC

Description 0x803: Recommend Disk Replacement.


The drive’s predictive failure analysis has determined that thedrive is likely to fail soon. This event is logged for referenceand troubleshooting and cannot be cleared.

Severity Critical


Hardware


No

System Impact Possible data loss.


Replace the drive as soon as possible.



DRAFT


3.2.30 Alarm 3030508


Managed Object EMC

Description 0x820: Soft Media Error.


The drive in question encountered an error trying to read itsdata. The extended status of 0x05 for the event is significantin that it means that more than one bit was flipped, andthat the data cannot be recovered from the drive’s SMARTtechnology. FLARE attempts to rebuild the data from the parityof the RAID group. This is significant in that if the RAID groupis already degraded, for example, if a rebuild is ongoing,then FLARE is forced to invalidate that data stripe becauseit cannot be rebuilt. Some amount of soft media errors areexpected per drive, but recurring soft media errors couldbe a sign that the drive in question might be going bad andshould be replaced. This event is logged for reference andtroubleshooting and cannot be cleared.

Severity Warning


Hardware


No

System Impact The disk might fail.


Drive replacement is usually recommended in instances whenan amber LED on the hard drives is on, which indicatesthat the drive is not operating normally. Replacement is alsorecommended when recommend drive replacement (eventcode 803) has been logged, or if one or more 920 Hard MediaErrors have occurred on a Fiber Channel drive. The status ofthe RAID group to which the drive belongs should be checkedto make sure that replacing the drive does not result in a moreproblematic array condition.


3.2.31 Alarm 3030509


Managed Object EMC

Description 0x840: Data Sector Invalidated.


DRAFT



The checksum error and block matches the FLARE RAIDinvalid sector format. This means that at some time in thepast, RAID invalidated this sector because of another adjacentchecksum error or media error in the stripe. This could occurbecause of a media error or checksum error on a differentdrive during a degraded condition or rebuild, or this couldoccur due to detection of multiple (checksum/media) errorson a nondegraded unit.

Severity Critical


Hardware


No

System Impact Data loss might occur.


Because the drive hit this error multiple times, it isrecommended that this drive be replaced. In addition, it isrecommended that the LUN be unbound first, bound again,and then restored from a backup.


3.2.32 Alarm 3030510


Managed Object EMC

Description 0x850: Enclosure state change.


The state of the disk enclosure has changed. This error isusually the result of an FRU component failing or beingremoved. The extended codes can be interpreted by knowingwhat the possible state changes mean.

Severity Critical


Hardware


Yes; by 3030830

System Impact Loss of redundancy on one of the FRUs will occur, andperformance might be impacted due to cache disabling.


Check the event log to see which component failed.


3.2.33 Alarm 3030512


DRAFT



Managed Object EMC

Description 0x852: Enclosure Duplicate Address Error.


Duplicate enclosure addresses are on the back-end bus. Thiscould be a result of a incorrect enclosure address having beenset or the enclosure being cabled to the wrong bus.

Severity Major


Hardware


Yes; by 3030830



Power cycle the entire array to normalize the chassisconfiguration. The proper enclosure address and cabling mustbe set before applying power to the system.


3.2.34 Alarm 3030513


Managed Object EMC

Description 0x854: The LCC cables are connected to the wrong inputport. Make sure that the LCC input cable is connected to theprimary port.


The DAE LCC is connected to the Extension port instead ofthe Primary port.

Severity Major


Hardware


Yes; by 3030830

System Impact There will be no access to DAE.


Check the cable connections and make sure that the inputcable to the LCC goes to the primary connection port.


3.2.35 Alarm 3030524


DRAFT



Managed Object EMC

Description 0x867: The read can fail because of:■ The device might not be present■ The device might be dead■ I2C bus error■ Checksum error


Failed to read the resume of PROM of a device. ResumePROM contains basic part identification information. The readcan fail because:■ The device might not be present.■ The device might be dead.■ I2C bus error.■ Checksum error.

This event is logged for reference and troubleshooting andcannot be cleared automatically.

Severity Major


Hardware


Yes; by 3039073



Determine the underlying issue:■ The device might not be present■ The device might be dead■ I2C bus error■ Checksum error


3.2.36 Alarm 3030526


Managed Object EMC

Description 0x870: Battery on the SP Board is either low or missing.Install new battery.


This error is related to the condition of the battery on the SPitself.

Severity Major


Hardware


DRAFT



Yes; by 3030830

System Impact Time settings in the RAID controller (SP) will be incorrect.


Replace the SP reporting the error.


3.2.37 Alarm 3030528


Managed Object EMC

Description 0x873: Person boots system and FLARE’s ATM detects oneCMI connection is down.


One of the CMI buses (the communication bus between SPs)is down.

Severity Major


Hardware


Yes; by 3030830

System Impact Internal hardware architecture redundancy will be impacted.


Replace this SP.


3.2.38 Alarm 3030601


Managed Object EMC

Description 0x901: Hard SCSI Error.


A SCSI operation failed and needed to be retried. This errorindicates that the retry attempts failed.


Severity Critical


Hardware


No


DRAFT




Look at the extended status for the affected drive to determinethe cause of the event.


3.2.39 Alarm 3030602


Managed Object EMC

Description 0x903: Fan Removed.


A fan has been removed or is faulty.

Severity Major


Hardware


Yes; by 3030211

System Impact Loss of fan redundancy will occur, and performance might beimpacted due to cache disabling.


Reinsert the power supply or fan.


3.2.40 Alarm 3030603


Managed Object EMC

Description 0x904: VSC Removed.


A power supply unit in the expansion enclosure has been shutdown or removed from the storage system.

Severity Major


Hardware


Yes; by 3030211



Check if the power supply power cord is plugged in. Replacethe power cord if necessary.


DRAFT



3.2.41 Alarm 3030604


Managed Object EMC

Description 0x905: Chassis Overtemperature.


The temperature inside the storage shelf is too high.


Severity Critical


Hardware


No

System Impact The system might crash.


Check the status of the fans or the surrounding environmentto determine why the system is overheating.


3.2.42 Alarm 3030605


Managed Object EMC

Description 0x906: Unit Shutdown.


A disk is being shut down by FLARE. This might be due toexcessive errors, but it also might be something more simple.If the drive in question is a hot spare, this message would beexpected if it occurs as the drive is preparing to step in foranother failed disk. Do not use this message alone as a basisfor replacing a drive. Search for other supporting messages.Another possibility is that a disk is being released by thiscurrently owning SP so that it can be trespassed over to theother SP. Very often this is an expected behavior.

Severity Critical


Hardware


Yes; by 3030202


DRAFT




Make sure that there are no fault conditions on the array or onthe host’s HBAs, and take appropriate action if required.


3.2.43 Alarm 3030607


Managed Object EMC

Description 0x908: Hardware Fault - Cache Disabling.


Under certain array hardware failure scenarios, the arraycache is disabled to ensure data integrity. After these events,storage subsystem performance might be poor until the cacheis manually re-enabled via the Navisphere interface.

Severity Critical


Hardware


Yes; by 3030212



Either identify the problem and fix it (for example, the SPSis not ready, that is, not present and fully charged; one ormore vault disks are missing or being rebuilt; a fan faultoccurred; the SP failed) or wait for the storage system to fixit (for example, wait for the SPS to reach full charge or forthe vault disks to be rebuilt). When the fault no longer exists,the storage system automatically re-enables storage systemwrite caching.


3.2.44 Alarm 3030608


Managed Object EMC

Description 0x909: Cache Dump Failed.


The cache started dumping due to a preceding event butwas unable to do so because of some hardware reason. Thisevent is logged for reference and troubleshooting and cannotbe cleared automatically.

Severity Critical


DRAFT



Hardware


No

System Impact System performance might be impacted, and data loss mightoccur.


Check the vault drives (if failed).


3.2.45 Alarm 3030612


Managed Object EMC

Description 0x90D: BBU or SPS Removed.


The SPS has failed or has been removed. The storage systemdumped the write cache to the vault, then disabled cachingand flushed the vault to disk. The write cache cannot beenabled until the problem is corrected either by replacing theSPS if it failed, or by reinstalling it.

Severity Critical


Hardware


Yes; by 3039071



Check the SPS or SP or both. Replace if necessary.


3.2.46 Alarm 3030613


Managed Object EMC

Description 0x90E: BBU Failed.


The BBU has failed.

Severity Major


Hardware


DRAFT



Yes; by 3039071



Replace the failed BBU.


3.2.47 Alarm 3030614


Managed Object EMC

Description 0x90F: Cache Recovered with Errors.


The data recovered from the cache after it was enabledis corrupted. This event is logged for reference andtroubleshooting and cannot be cleared.

Severity Critical


Hardware


No



If your data is inconsistent, recover it from the backup copy.


3.2.48 Alarm 3030615


Managed Object EMC

Description 0x910: Cache Recovery Failed.


The recovery process has failed. This event is logged forreference and troubleshooting and cannot be cleared.

Severity Critical


Hardware


No


DRAFT




Verify that your system is functioning normally. Check theincoming events to find a reason for recovery fail.


3.2.49 Alarm 3030616


Managed Object EMC

Description 0x911: The SPS Power cable 1 is not configured properly (notgetting power supplied by SPS). Power cable 1 is to the xPEon Chameleon2 and is to the X1 enclosure on X1.


The power or serial cables between the SPSs and SPs haveeither been miswired or are bad.

Severity Major


Hardware


Yes; by 3030830

System Impact Array functionality might be impacted.


If this event occurs after booting up, wait until this conditionclears. If it does not clear, check the power/serial wiring.


3.2.50 Alarm 3030617


Managed Object EMC

Description 0x912: The SPS Power cable 2 is not configured properly(not getting power supplied by SPS). Power cable 2 is to thefirst Katana enclosure on Chameleon2. This is not applicablefor X1.



Severity Major


Hardware


Yes; by 3030830


DRAFT






3.2.51 Alarm 3030618


Managed Object EMC

Description 0x913: The serial connection between the SPs and SPSsare crossed. This results in SP A controlling SPS B and viceversa. This condition makes it difficult to properly identifyfailing component.


The system might be misconfigured, that is, the serialconnection between the SPs and SPSs are crossed. Thisresults in SP A controlling SPS B and vice versa.

Severity Major


Hardware


Yes; by 3030830

System Impact Failing components will not be properly identified.


Check the connections between the SPs and the SPSs.


3.2.52 Alarm 3030619


Managed Object EMC

Description 0x914: There are multiple cables (Power 1, Power 2, Serial)that are improperly configured.



Severity Major


Hardware


Yes; by 3030830


DRAFT






3.2.53 Alarm 3030620


Managed Object EMC

Description 0x920: Hard Media Error.


Hard Media Errors (920) on the Fiber Channel drives indicatethat a condition has occurred that might not have beencorrectable by means of a drive’s remapping capabilities, andit might be a precursor to data loss situations. This eventis logged for reference and troubleshooting and cannotbe cleared. This event must be investigated and clearedmanually because the error and fix need investigation andmanual intervention.

Severity Critical


Hardware


No



Drive replacement is usually recommended in instances whenan amber LED on the hard drives is on, which indicatesthat the drive is not operating normally. Replacement is alsorecommended when recommend drive replacement (eventcode 803) has been logged, or if one or more 920 Hard MediaErrors have occurred on a Fiber Channel drive. The status ofthe RAID group to which the drive belongs should be checkedto make sure that replacing the drive does not result in a moreproblematic array condition.


3.2.54 Alarm 3030622


Managed Object EMC

Description 0x922: Host Vault Load Inconsistent.


DRAFT



The inconsistency can be seen after cache dirty events,multiple disk failures within the cache vault, or if there areuncorrectable sector errors in the cache vault.

Severity Critical


Hardware


Yes; by 3030830

System Impact Data loss might occur in case of multiple disk failures, andperformance might be impacted due to cache disabling.


Do the following:1 In the Navisphere Manager, click the Memory tab in the

Array Properties dialog box.2 Set the write cache values to zero and then click Apply.3 Reset the values to original.4 Enable write cache.


3.2.55 Alarm 3030629


Managed Object EMC

Description 0x929: Front End Fibre Link Down.


Link down detected on the front-end Fiber Channel port. Thisindicates a physical problem with the connection to the EMCstorage device.

Severity Major


Hardware


Yes; by 3030830



Verify Layer 1 connectivity.


3.2.56 Alarm 3030633


DRAFT



Managed Object EMC

Description 0x7152811B: DRP Alarm - Incremental update has completedsuccessfully. Mirrorview/A is unable to communicate with thesecondary array to stop the protective snap session. Checkthe mirrorview connection between the arrays.


MirrorView/A cannot communicate with the secondary arrayto stop the remote snap session after an incremental updatehas completed. This event is logged for reference andtroubleshooting and cannot be cleared. After communicationwith the remote SP is resumed, MirrorView/A operations canbe resumed manually.

Severity Major


Hardware


No

System Impact The MirrorView process will be impacted.


Check all devices in the communication path between thesource and target arrays.


3.2.57 Alarm 3030639


Managed Object EMC

Description 0x940: BBU Faulted.


The voltage feeding the CLARiiON has dropped belowacceptable values. The system has started dumping cache todisk. Typically, most arrays can tolerate a longer line dropoutepisode (for example, 30 msec), but the maximum timecannot be quantified because conditions vary too much. A1.0 sec line dropout definitely induces a switch to BBU powerand the storage processor’s dumping data from cache to diskmodules. After a cache-dump starts, it must finish completelyeven if the power line recovers immediately. When the cacheis safely written to a vault disk, Licensed Internal Code (LIC)determines that power is back to normal, restores the cache,and resumes normal data processing.

Severity Major


Hardware


Yes; by 3039134


DRAFT




Check BBU status, and replace it if faulted.


3.2.58 Alarm 3030640


Managed Object EMC

Description 0x942: Excessive single-bit ECC errors on SP memorymodule.


Memory errors were detected on the SP memory module.

Severity Major


Hardware


Yes; by 3030830



Correctable ECC errors should be treated as single-bit ECCerrors, which means that no corrective action is requiredunless more than 50 errors are generated in a single week. Ifthis occurs, contact Comverse customer support.


3.2.59 Alarm 3030641


Managed Object EMC

Description 0x944: Hard Peer Bus Error.


The SP has rebooted. This event is logged for reference andtroubleshooting and cannot be cleared.

Severity Major


Hardware


No


DRAFT


System Impact Loss of RAID controller (SP) redundancy during the reboot willoccur, and performance during reboot will be impacted.


Determine the reason for the SP reboot, either based on anevent that occurred or using the event viewer.


3.2.60 Alarm 3030653


Managed Object EMC

Description 0x951: CRU Signature Error.


The CRU Signature defines in which Enclosure/Bus/Slot thedisk is. It also has an entry that is unique for each RAIDgroup, which means that a disk must not only match theEnclosure/Bus/Slot but also the RAID group to be includedin as part of a LUN. If you pull one disk, that slot is markedfor rebuild. If you pull a second disk from a RAID group, theRAID group shuts down. If you then insert a new disk for thesecond disk you pulled, FLARE (the array operating system)tries to bring up the LUN in n -1 disks mode but because itis not the original disk, it cannot bring the LUN online, andinstead returns a CRU signature error. If you insert the correctdisk (that is, the one you pulled from that slot), the LUN comesback online. If you insert a new disk into the first slot youpulled or insert the original disk you pulled from that slot, thedisk is rebuilt because that first slot is marked as needing arebuild. When a slot requires a rebuild, the CRU signatureof the disk does not matter. A rebuilt disk is assigned a newCRU signature, which is created when a LUN is bound andstored on the private area of each disk.

Severity Major


Hardware


Yes; by 3030830



If two disks were removed from a RAID group before therebuild was completed on the first one, insert the correct diskback into its proper place. In some cases, the only way tore-establish ownership of this LUN is a nondestructive bind(NDB), which can only be performed by EMC Engineering. Byunbinding the LUN and then rebinding it with NDB, the CRUsignature is rewritten.



DRAFT


3.2.61 Alarm 3030654


Managed Object EMC

Description 0x952: Single Fan Fault.


A single fan has been removed or is faulty (CX700).

Severity Major


Hardware


Yes; by 3030210

System Impact Loss of fan redundancy will occur.


Check if a fan is faulty. If so, replace/reinsert it.


3.2.62 Alarm 3030655


Managed Object EMC

Description 0x960: Power Supply A on xPE was removed or faulted.


Power supply A on the xPE has been removed or is faulty(CX700).

Severity Major


Hardware


Yes; by 3030406



First try replacing the power supply, standby power supply(SPS), and SPS sense cable, and then run SPcollectscripts. If one of the SPS persistently reports 76008103(0x76008103) Found an error during POST errors, replacethat SP.



DRAFT


3.2.63 Alarm 3030656


Managed Object EMC

Description 0x961: Power Supply B on the xPE was faulted or removed.


Possible faulty standby power supply on the DPE (CX700).

Severity Major


Hardware


Yes; by 3030407





3.2.64 Alarm 3030658


Managed Object EMC

Description 0x963: Power Supply A Failure Detected on the xPE.


Possible faulty standby power supply or power supply(CX700).

Severity Major


Hardware


Yes; by 3030830






DRAFT


3.2.65 Alarm 3030659


Managed Object EMC

Description 0x964: Power Supply B Failure Detected on the xPE.


Possible faulty standby power supply or power supply.

Severity Major


Hardware


Yes; by 3030830





3.2.66 Alarm 3030660


Managed Object EMC

Description 0x966: Cannot enable write cache due to cache dirty unit(s).


The SP is coming up and recovering the cache image. Thevault is loaded and tests to see if the cache can be enabled.This SP looks for dirty units that are unassigned at this time.The cache is not enables while there are unassigned dirtyunits, so it issues these errors to let the user know thatmanual intervention might be required. After the units becomeassigned, the cache can enable successfully.

Severity Major


Hardware


Yes; by 3030830


DRAFT




Verify that this system’s failover implementation (for example,PowerPath) is installed and configured correctly. The factthat these LUNs were unassigned probably means that thissystem’s failover implementation is deficient.


3.2.67 Alarm 3030702


Managed Object EMC

Description 0xA05: NON VOL Not Initialized.


The nonvolatile memory on the SP has been found to beuninitialized. The SP reinitializes the memory to its defaultstate and then the SP is functional after reboot. This eventshould only occur once when a new SP is inserted. If yousee this message on an existing SP that has already beeninitialized, it indicates that either the NVOL chip is bad or theonboard battery on the SP is bad.

Severity Critical


Hardware


Yes; by 3030830



If this message is reported more than once for the same SP, itmust be replaced.


3.2.68 Alarm 3030704


Managed Object EMC

Description 0xA07: Disk Powered Down.


A customer-replaceable unit (most likely a disk drive) hasbeen powered down. This can be an indication that the driveis problematic, but it can also be a perfectly normal messagein the context of a controlled shutdown of an enclosure.

Severity Critical


DRAFT



Hardware


Yes; by 3030830



The message must be examined in its context.


3.2.69 Alarm 3030709


Managed Object EMC

Description 0xA11: SP is removed.


The SP has been physically removed.

Severity Critical


Hardware


Yes; by 3039075

System Impact Loss of RAID controller (SP) redundancy will occur, andperformance will be impacted due to cache disabling.


Check to see if any SP have been physically removed.Reinsert them if they have.


3.2.70 Alarm 3030714


Managed Object EMC

Description 0xA18: CRU Drive Causing Loop Failure.


A drive has failed, causing both FC loops to fail.

Severity Critical


Hardware


Yes; by 3030830


DRAFT




Replace the drive that caused the error.


3.2.71 Alarm 3030730


Managed Object EMC

Description 0x765: Fan Module C on xPE is faulted or removed.


Fan module C on the xPE either failed or has been physicallyremoved (CX700).

Severity Major


Hardware


Yes; by 3039090





3.2.72 Alarm 3030731


Managed Object EMC

Description 0x767: Fan Module A on xPE is faulted or removed.


Fan module A on the xPE either failed or has been physicallyremoved (CX700).

Severity Major


Hardware


Yes; by 3039092






DRAFT


3.2.73 Alarm 3030805


Managed Object EMC

Description 0x2047: The system time has been set backwards. This mayaffect event collection.


The system time has been set backwards. This might affectevent collection. Event Monitor begins processing eventswhen the system time catches up to the time of the last eventEvent Monitor processed.


Severity Minor


Hardware


No

System Impact The event collection process will be impacted, and a possiblemismatch of event times might occur.


Manually set the system time correctly.


3.2.74 Alarm 3030806


Managed Object EMC

Description 0x2080: SP busy, couldn’t respond to at least one Error eventon the SP.


Too many events were encountered together. Please see theCX event log (either through Navisphere Manager or throughNaviCLI) for more details on events and check if any of themare severe.


Severity Minor


Hardware


DRAFT



No


Please check which errors led to this alert. Use eitherNavisphere Manager or NaviCLI.


3.2.75 Alarm 3030809


Managed Object EMC

Description 0x20c0: SP busy, couldn’t respond to at least one Criticalevent on the SP.


Too many events were encountered together, and at least oneevent is critical. See the CX event log for more details.

Severity Critical


Hardware


Yes; by 3030830

System Impact RAID controller (SP) redundancy might be lost, which willimpact system performance.


Check the CX event log (either using Navisphere Manageror NaviCLI) for critical errors.


3.2.76 Alarm 3030816


Managed Object EMC

Description 0x2183: The computer has rebooted from bugcheck (0x3e9):<bugcheck_details>.


The SP has rebooted because of a bugcheck. This errorshould not appear after FLARE 14.

Severity Major


Hardware


Yes; by 3030830


DRAFT


System Impact RAID controller (SP) redundancy might be lost, which willimpact system performance.


Check the SPS or storage processor (SP) or both. Replaceif necessary.


3.2.77 Alarm 3030821


Managed Object EMC

Description 0x2480: Disk Failure.


A disk has failed.

Severity Critical


Hardware


Yes; by 3039059



Replace the hard drive.


3.2.78 Alarm 3030822


Managed Object EMC

Description 0x2481: Fan Failure.


A fan has been removed or is faulty.

Severity Major


Hardware


Yes; by 3030830


DRAFT


System Impact Loss of fan redundancy will occur, and performance might beimpacted due to cache disabling.


Replace the fan.


3.2.79 Alarm 3030823


Managed Object EMC

Description 0x2482: Power Supply Failure.


A power supply has failed.

Severity Major


Hardware


Yes; by 3030830



Replace the power supply.


3.2.80 Alarm 3030824


Managed Object EMC

Description 0x2483: LCC Failure.


A Link Control Card has failed.

Severity Major


Hardware


Yes; by 3030830

System Impact LCC redundancy will be lost.


Replace the Link Control Card.



DRAFT


3.2.81 Alarm 3030825


Managed Object EMC

Description 0x2484: Enclosure Failure.


The enclosure has failed.

Severity Critical


Hardware


Yes; by 3030830



Check the incoming events (either using Navisphere Manageror NaviCLI) to find a reason for enclosure failure.


3.2.82 Alarm 3030830 (Log only)


Managed Object EMC

Description 0x2500: Storage system has no faults.


The storage system has no faults.

Severity Normal


Hardware


No


3.2.83 Alarm 3030832


Managed Object EMC

Description 0x2580: Storage system is faulted.


DRAFT



Storage system is faulted. This message usually follows acritical event such as a CRU power-down of a disk.

Severity Critical


Hardware


Yes; by 3030830



Check the preceding events either using Navisphere Manageror NaviCLI.


3.2.84 Alarm 3030833 (Log only)


Managed Object EMC

Description 0x2700: Path to an array is up.


The path from host to storage system is up.

Severity Normal


Hardware


No


3.2.85 Alarm 3030834


Managed Object EMC

Description 0x2780: Path to an array is down.


The physical path to an array is down.

Severity Major


Hardware


Yes; by 3039171


DRAFT




A physical path failure might have occurred; replace therelevant component.


3.2.86 Alarm 3031002


Managed Object EMC

Description 0x40004001: The MessageDispatcher detected an errorduring initializationt. This error code appears only in the eventlog messages.


SP Reboot. The peer died in run.

Severity Major


Hardware


Yes; by 3030830

System Impact Loss of RAID controller (SP) redundancy during the reboot willoccur, and performance during reboot will be impacted.


Determine the reason for the SP reboot, either based on anevent that occurred or using the event viewer at NavisphereManager or NaviCLI.


3.2.87 Alarm 3031046


Managed Object EMC

Description 0x40008010: int3, int5, etc.


FLARE issue with Navisphere Management Software. Theexception was most likely caused by a bad memory reference.

This is an internal software exception event that is loggedfor reference.

Severity Major


Hardware


DRAFT



No

System Impact RAID controller (SP) redundancy might be lost.


Determine if the SP is unmanaged. If it is, reboot it; otherwise,cancel the case, indicating that the SP is managed and thatno action is necessary.


3.2.88 Alarm 3031110


Managed Object EMC

Description 0x40008031: Array has been booted but the K10 drivers didnot start (NDU degraded mode). This is not the same as RAID5 degradation.


The storage system has been restarted but the storagesystem drivers did not start (NDU degraded mode).

This event is logged for reference and troubleshooting andcannot be cleared automatically. Clearing must be manualfor this event.

Severity Major


Hardware


Yes; by 3030830

System Impact Upgrade success will be impacted, and the RAID controller(SP) might fail.


If NDU (Software Installation) just upgraded the SP, you mightneed to back out the changes made. However, if this occurswith other event code messages, it might indicate a failed SP.


3.2.89 Alarm 3031124


Managed Object EMC

Description 0x40008038: An attempt was made to trespass a private LUN.


DRAFT



An attempt was made to trespass a private LUN, for example,a LUN in a reserved LUN Area for MirrorView/A. Do nottrespass these LUNs.

This event indicates a failure of an administrative action andis logged for troubleshooting and reference and cannot becleared.

Severity Warning


Hardware


No


Configure the Reserved LUN pool.


3.2.90 Alarm 3031142


Managed Object EMC

Description 0x40008044: An installed software package must becommitted before this command can be accepted.


An installed software package must be committed before thiscommand can be accepted. A feature being requested cannotbe used until the recent FLARE upgrade is committed.


Severity Warning


Hardware


No

System Impact Installed software will not be usable until it the package iscommitted.


Commit the software package.


3.2.91 Alarm 3031172


DRAFT



Managed Object EMC

Description 0x40008053: Unbind failed-LU May Be Private.


Failed to unbind LUNs The LUNs may be private and cannotbe unbound before they are removed from their container.


Severity Warning


Hardware


No


Remove a LUN from a storage group before attempting todelete. You can unbind a private LUN but be careful whendoing so. The private LUN must be made public beforeunbinding. If the LUN has Reserved LUN Pool next to its RAIDgroup in Navisphere User Interface (UI), it must be removedfrom the Reserved LUN pool before being unbound.


3.2.92 Alarm 3031232


Managed Object EMC

Description 0x41008004: Caught ASSERT or INT5.


Possible memory leak. This error should not occur in newerFLARE versions (14, 16, 19).

This event is logged for reference and troubleshooting andcannot be cleared. Rebooting the SP might clear it.

Severity Major


Hardware


No



If this seems to be a one-time occurrence, it can safely beignored. However, you should continue to monitor the arrayfor this error. If it occurs again, it might indicate a memoryleak, which could have multiple causes, and might requirethe SP to be rebooted.



DRAFT


3.2.93 Alarm 3032121


Managed Object EMC

Description 0x71058155: DRP Alarm - Failed to request remote K10 todestroy a mirror.


A communication error to the remote SP has occurred. Thisevent is logged for reference and troubleshooting and cannotbe cleared automatically. After the mirror is destroyed, thisevent can be cleared.

Severity Major


Hardware


No



Check the communication to the remote system.


3.2.94 Alarm 3032122


Managed Object EMC

Description 0x71058156: DRP Alarm - Failed to request remote K10 toupdate a mirror.


A communication error to the remote SP has occurred.


Severity Major


Hardware


No






DRAFT


3.2.95 Alarm 3032131


Managed Object EMC

Description 0x7105815F: DRP Alarm - Failed to request remote K10 topromote an image.


A communication error to the remote SP prevented a promoteoperation.


Severity Major


Hardware


No





3.2.96 Alarm 3032168


Managed Object EMC

Description 0x71058187: DRP Alarm - Maximum mirrors already allocatedon the system.


The maximum number of mirrors have been allocated onthe system (CX500 up to 50 MV/A LUNs, CX700 up to 100MV/A LUNs).


Severity Major


Hardware


No



Reduce the number of MV/A LUNs.



DRAFT


3.2.97 Alarm 3032169


Managed Object EMC

Description 0x71058188: DRP Alarm - Maximum number of mirrors onthe system.


The maximum number of mirrors have been allocated onthe system (CX500 up to 50 MV/A LUNs, CX700 up to 100MV/A LUNs).


Severity Major


Hardware


No



Reduce the number of MV/A LUNs.


3.2.98 Alarm 3032190


Managed Object EMC

Description 0x7105819E: DRP Alarm - Promoting a secondary image wasallowed, but recreating the secondary images failed due to twoincompatible admin operations being performed at the sametime. Its possible when cross mirroring to get into a deadlocksituation if you are doing promotion or add/delete secondaryoperations at the same time. To prevent this we check currentoperations and add the secondary to a promoted image toprevent the deadlock.


Two conflicting MirrorView operations were run at the sametime. This event is logged for reference and troubleshootingand cannot be cleared automatically.

Severity Major


Hardware


No


DRAFT




Check the currently running operations and add the secondaryimage to a promoted image to prevent the deadlock.


3.2.99 Alarm 3032238


Managed Object EMC

Description 0x71058233: DRP Alarm - Can’t remove the mirroring driverfrom an LU’s stack, as it is currently part of a mirror.


Cannot destroy a mirror in an active state.


Severity Major


Hardware


No



Determine the state of the mirror, if active or not.


3.2.100 Alarm 3032239


Managed Object EMC

Description 0x71058235: DRP Alarm - Can’t remove the mirroring driverfrom an LU’s stack, as it is currently synchronizing.


Cannot destroy a mirror in a synchronizing state.

This event is logged for reference and troubleshootingand cannot be cleared automatically. After the mirror issynchronized, the mirror can be destroyed.

Severity Major


Hardware


No


DRAFT




Wait until synchronization completes.


3.2.101 Alarm 3032243


Managed Object EMC

Description 0x7105823C: DRP Alarm - Can’t start synchronization fromthe current image condition.


MirrorView condition might be synchronizing or in a state thatdoes not allow the start of another synchronization.


Severity Major


Hardware


No



Determine the state of the mirror. If it is active, wait until itends and then continue. If there is an additional error, resolveit first before continuing.


3.2.102 Alarm 3032253


Managed Object EMC

Description 0x71058248: DRP Alarm - A secondary image reported amedia failure.


Media failure fractures can be caused by physical disk errorswithin the LUN associated in the mirror connection. This mightresult in the MirrorView software detecting an I/O failure to aphysical disk.


Severity Critical


DRAFT



Hardware


Yes; by 3030830



Check if there is a physical fault on the secondary SP.


3.2.103 Alarm 3032403


Managed Object EMC

Description 0x7105852B: DRP Alarm - Unable to verify the remote arrayversion during add secondary operation. Check connectivitybetween the arrays.


This error is usually the result of a partial connection betweenthe Primary and Secondary SPs. Partially connected is definedas a connection that is useable but not fully established (forexample, SP-A <-> SP-A, but SP-B <-> SP-B does not existor vice versa). This is a degraded state of operation. Thisevent is logged for reference and troubleshooting and cannotbe cleared automatically. After connectivity is restored, thiscondition can be cleared manually.

Severity Major


Hardware


No



Check the connectivity between the CX storage systems andverify correct zoning configuration both at the FC Switch andthe SAN Gateway (if available).


3.2.104 Alarm 3035708


Managed Object EMC


DRAFT


Description 0x71528169: DRP Alarm - Mirrorview/A is unable tocommunicate with secondary array and trespass thedestination LU for the mirror’s secondary image while startingan incremental update.


A communication error with a remote SP has occurred.MirrorView/A cannot communicate with the secondary arrayto trespass the target LUN to the correct SP and start anincremental update. This event is logged for reference andtroubleshooting and cannot be cleared. After communicationwith the remote SP is resumed MirrorView/A operations canbe resumed manually.

Severity Major


Hardware


No



Check all devices in the communication path between thesource and target arrays.


3.2.105 Alarm 3035723


Managed Object EMC

Description 0x71528180: DRP Alarm - Operation prohibited asMirrorView/A is in degraded mode.


MirrorView/A state does not allow performing a requiredoperation.


Severity Major


Hardware


No



Determine which event lead to the MirrorView/A state andfix that event.



DRAFT


3.2.106 Alarm 3035749


Managed Object EMC

Description 0x7152819b: DRP Alarm - The session for the mirror hasfailed because the primary array has run out of cache. As aresult of this error, the mirror is adminfractured.


The secondary image for the mirror has fractured because thereserved LUN pool on the primary array was exhausted. As aresult, the mirror is adminfractured.


Severity Major


Hardware


No



Add more cache LUNs on the primary array and retry a sync.


3.2.107 Alarm 3035750


Managed Object EMC

Description 0x7152819c: DRP Alarm - The session for the mirror hasfailed because the secondary array has run out of cache. As aresult of this error, the mirror is adminfractured.


The secondary image for the mirror has fractured because thereserved LUN pool on the secondary array was exhausted.As a result, the mirror is adminfractured.


Severity Major


Hardware


No


DRAFT




Add more cache LUNs on the secondary array and retry async.


3.2.108 Alarm 3037004


Managed Object EMC

Description 0x71298001: Unable to initialize allocate memory for polldata. Polls fail.


An internal problem has occurred with the array management.


This is the result of an error in the Navisphere ManagementServer (CIMOM), which is unable to perform one of itsfunctions on the storage processor.

Severity Major


Hardware


No

System Impact Management towards storage system might be lost.


Restart CIMOM on the SP. If the error persists after restartingthe CIMOM or has resulted in an unmanaged SP, contactComverse customer support.


3.2.109 Alarm 3037061


Managed Object EMC

Description 0x71518014: Installation of software on the peer SP failed.


An installation failure has occurred on the peer SP.

Severity Major


Hardware


DRAFT



No

System Impact Software package installation will be impacted.


Reboot each SP, one at a time, and then retry the NDU.


3.2.110 Alarm 3037062


Managed Object EMC

Description 0x71518015: Installation of software on the master SP failed.


Installation of software on the master SP has failed.

Severity Minor


Hardware


No



Look at the text attached to the event to understand thereason for the problem. After you have solved the issue, runan NDU again.


3.2.111 Alarm 3037075


Managed Object EMC

Description 0x71518026: The SP failed to reboot.


Service processor failed to reboot due to a hardware issuethat needs to be investigated.

Severity Critical


Hardware


Yes; by 3030830


DRAFT




A diagnosis must be made to determine if a minor correctiveaction is sufficient to rectify the situation or if the SPboot-drives must be re-imaged. Certain types of failuresrequire re-imaging a pair of SP boot drives. Other typesof failures require the SP replacement, or recabling andreconfiguring the array.


3.2.112 Alarm 3037076


Managed Object EMC

Description 0x71518027: The SP failed to reboot.


Service processor failed to reboot due to a hardware issuethat needs to be investigated.

Severity Major


Hardware


Yes; by 3030830



A diagnosis must be made to determine if a minor correctiveaction is sufficient to rectify the situation or if the SPboot-drives must be re-imaged. Certain types of failuresrequire re-imaging a pair of SP boot drives. Other typesof failures require the SP replacement, or recabling andreconfiguring the array.


3.2.113 Alarm 3037102


Managed Object EMC

Description 0x76004101: Found a warning form POST. See text for details.


This is a generic error with specific text that describes theproblem. The error could be duplicate enclosure address,power supply, standby power supply (SPS), or SPS sensecable.

Severity Major


DRAFT



Hardware


Yes; by 3030830

System Impact Redundancy might be lost in the power supply or RAIDcontroller (SP), and performance might be impacted due tocache disabling.


Look at the text attached to the event to understand thereason for the problem. Possible solutions: replace the powersupply, standby power supply (SPS), and SPS sense cable.If one of the SPs persistently reports 0x76008103 Found anerror during POST errors, replace that SP.


3.2.114 Alarm 3037113


Managed Object EMC

Description 0x7600800c: Cannot alloc or free memory.


A call has been made to an internal FLARE application(psmtool). This application is not critical to the array’soperation or management.

Severity Minor


Hardware


No


The array retries this operation. If this message is notcontinually being logged more than a few times a day, it canbe safely ignored.


3.2.115 Alarm 3037122


Managed Object EMC

Description 0x76008101: Found single bit ECC error. See messagedetails.


DRAFT



There was an error correction code error in the CX memorymodules. This is an issue that affects a limited number ofdual in-line memory modules (DIMMs) on CX-Series storageprocessors (SPs). This alarm is a notification of a MemoryECC error, and cannot be cleared.

Severity Minor


Hardware


No

Threshold If this occurs more 50 times, contact customer support.


Correctable ECC errors should be treated as single-bit ECCerrors, which means that no corrective action is requiredunless more than 50 errors are generated in a single week.


3.2.116 Alarm 3037123


Managed Object EMC

Description 0x76008102: Found multibit ECC error. See message details.


When a multibit error occurs, the memory controller generatesan SMI interrupt. Information about what DIMM and thesyndrome bits are gathered and this information is stored inthe DMI log prior to reboot. Upon a successful reboot, thisDMI logged information is read via the DGSSP driver andstored into the NT event log.

Severity Critical


Hardware


Yes; by 3030830



Replace the SP. This is required because a multibit ECC errorcauses the SP to panic and reboot without creating a dumpfile.


3.2.117 Alarm 3037315


DRAFT



Managed Object EMC

Description 0x7950800E: This occurs when trying to remove the devicecreator form the list of filter drivers.


This error occurs when trying to remove the device creatorfrom the list of filter drivers. It means that the commandwas sent to the wrong Storage Processor (SP), and thenforwarded to the other SP.


Severity Warning


Hardware


No


Please contact Comverse customer support.


3.2.118 Alarm 3037339


Managed Object EMC

Description 0x79508026: Subroutine failed, see data section for sourceerror.


An internal software error with accessing the systemconfiguration files (PSM LUN) has occurred.


Severity Critical


Hardware


No


DRAFT


System Impact Data loss might occur in case of multiple disk failures, andperformance might be impacted due to cache disabling.


Do the following:1 Verify that all disks making up the PSM LUN are

accessible. If you find a double-faulted PSM LUN on anarray, or a triple-faulted PSM LUN (drives 0, 1, and 2)on a CX-Series array, this might explain why the PSMLUN cannot be reached

2 If there are no other signs of trouble on the array, theaction required depends on whether you are seeing anyother adverse effects. An array should definitely not belogging these messages frequently, because this wouldindicate some sort of problem with accessing the PSMLUN or its drives


3.2.119 Alarm 3039062


Managed Object EMC

Description 0x605: CRU Unit Rebuild Halted.


FLARE has stopped a rebuild that was in progress for aparticular LUN contained on a disk. This can be generatedeither because of LUN trespassing, or because of a doublefault in the RAID group where the LUN is trying to be rebuilt.

Severity Critical


Hardware


Yes; by 3030204



Check that the rebuild continues on the other SP until it iscompleted.


3.2.120 Alarm 3039063


Managed Object EMC

Description 0x606: Unit Shutdown for Trespass.


DRAFT



The SP has shut down the LUN containing this drive moduleat the request of the peer SP because of a trespass operation.Under the following conditions, a CLARiiON array mightexperience Unit Shutdown for Trespass messages:■ Path to CLARiiON array may be down.■ Possible problem with the SP.■ Fiber connection from server to switch or to CLARiiON

array might be loose or bad.

Severity Major


Hardware


Yes; by 3039063

System Impact FC connectivity towards the CX will be impacted or RAIDcontroller (SP) redundancy will be lost.


If all LUNs have failed over to the peer SP, review the eventlogs to determine the root cause. If the SP failed, it mustbe replaced. Check HBAs and fiber connections to the CXsystem.


3.2.121 Alarm 3039065 (Log only)


Managed Object EMC

Description 0x621: Backround Verify Started.


A background check on the correctness of parity informationhas begun on the unit of which this drive is a member.

Severity Normal


Hardware


Yes; by 3039066


3.2.122 Alarm 3039066 (Log only)


Managed Object EMC

Description 0x622: Backround Verify Complete.


DRAFT



The Background Verify process has completed.

Severity Normal


Hardware


No


3.2.123 Alarm 3039069


Managed Object EMC

Description 0x636: BBU/SPS Removed.


SPS was removed from the storage system.

Severity Major


Hardware


Yes; by 3039071



Reinsert/reconnect the BBU.


3.2.124 Alarm 3039070


Managed Object EMC

Description 0x637: BBU Recharging.


The battery backup unit (or SPS) is recharging, probably afterreboot.

Severity Warning


Hardware


Yes; by 3039071


DRAFT




Wait about 20 minutes for recharging before the cache isenabled.


3.2.125 Alarm 3039071 (Log only)


Managed Object EMC

Description 0x638: BBU Enabled.


The SPS has been re-enabled, allowing write caching.

Severity Normal


Hardware


No


3.2.126 Alarm 3039073 (Log only)


Managed Object EMC

Description 0x63F: Resume PROM information was read successfully.


The SP has successfully read the PROM information aboutthe device denoted by the extended status code. This eventis logged for reference and troubleshooting and cannot becleared.

Severity Normal


Hardware


No


3.2.127 Alarm 3039074


DRAFT



Managed Object EMC

Description 0x642: Backround Verify Aborted.


A Background Verify operation has been terminated due toan abnormal event, such as the failure of one of the disksin the LUN, trespass, or SP reboot. This event is logged forreference and troubleshooting and cannot be cleared.

Severity Warning


Hardware


No




3.2.128 Alarm 3039075 (Log only)


Managed Object EMC

Description 0x644: Peer SP Inserted.


The peer SP has been reinserted.

Severity Normal


Hardware


No


3.2.129 Alarm 3039076 (Log only)


Managed Object EMC

Description 0x645: CRU Bound.


A disk was bound to a RAID group.

Severity Normal


DRAFT



Hardware


No


3.2.130 Alarm 3039077 (Log only)


Managed Object EMC

Description 0x646: Disk Module Unbound.


A disk was unbound from a RAID group, therefore all the dataon it was lost.

Severity Normal


Hardware


No


3.2.131 Alarm 3039079


Managed Object EMC

Description 0x698: SPS/Battery Testing In Progress.


A series of these logs indicates that the scheduled SPS testevent has occurred.

Severity Warning


Hardware


Yes; by 3030830

System Impact The cache will be automatically disabled during batterytesting, and performance will be impacted.


3.2.132 Alarm 3039090 (Log only)


DRAFT



Managed Object EMC

Description 0x762: Fan Module C on xPE has been installed or repaired.


Fan module C on the xPE has been installed or repaired(CX700).


Severity Normal


Hardware


No


3.2.133 Alarm 3039091 (Log only)


Managed Object EMC

Description 0x763: Fan Module B on xPE has been installed or repaired.


Fan module B on the xPE has been installed or repaired(CX700).


Severity Normal


Hardware


No


3.2.134 Alarm 3039092 (Log only)


Managed Object EMC

Description 0x764: Fan Module A on xPE has been installed or repaired.


Fan module A on the xPE has been installed or repaired(CX700).



DRAFT


Severity Normal


Hardware


No


3.2.135 Alarm 3039094


Managed Object EMC

Description 0x766: Fan Module B on xPE is faulted or removed.


Fan module B on the xPE either failed or has been physicallyremoved (CX700).

Severity Major


Hardware


Yes; by 3039091





3.2.136 Alarm 3039103


Managed Object EMC

Description 0x78A: Write cache enable pending.


The write cache is in a pending state until it is possible toenable it. If all conditions are met, it enables automatically.This might be the result of a rebuild on the first five drives,battery recharging, and so on.

Severity Major


Hardware


Yes; by 3030212


DRAFT




Check the CLARiiON event log for details.


3.2.137 Alarm 3039134 (Log only)


Managed Object EMC

Description 0x941: BBU on line.


The battery backup unit is online. The cache should return tothe enabled state.

Severity Normal


Hardware


No


3.2.138 Alarm 3039148


Managed Object EMC

Description 0xA23: Peer SP is down because of hang/crash/bugcheck.The peer SP hardware is present but it is down for the reasonsmentioned in first sentence. Communication between SPAand SPB is down.


Software issue. The Peer SP is down because ofhang/crash/bugcheck. Communication between SPA andSPB is down.

Severity Critical


Hardware


Yes; by 3030830



Reboot the SP. Check for FLARE updates/patches.



DRAFT


3.2.139 Alarm 3039149


Managed Object EMC

Description 0xA25: Enclosure state change.


A component, for example, a fan module, has failed or hasbeen removed. The extended codes can be interpreted byknowing what the possible state changes mean.

Severity Critical


Hardware


Yes; by 3030830

System Impact One of the FRUs’ redundancy will be impacted.


Check the joining events to determine why the enclosure’sstate changed.


3.2.140 Alarm 3039150


Managed Object EMC

Description 0x2003: SP busy, couldn’t respond to at least oneInformational event on the SP.


Too many events were encountered together. Please see theCX event log (either through Navisphere Manager or throughNaviCLI) for more details on events and check if any of themare severe.


Severity Minor


Hardware


No


Please check which errors led to this alert. Use eitherNavisphere Manager or NaviCLI.



DRAFT


3.2.141 Alarm 3039151 (Log only)


Managed Object EMC

Description 0x4600: Informational Audit Log entry.


A user login or some other audit log entry has been recorded.This event is logged for reference and troubleshooting andcannot be cleared.

Severity Normal


Hardware


No


3.2.142 Alarm 3039152


Managed Object EMC

Description 0x4640: Warning Audit Log entry.


An audit log entry has been created for an unsuccessfullogin/request. Login failure must be logged and cannot becleared.

This is not a problem and Navisphere is working asdesigned. Any client that issues a request without anauthorized username/password results in an audit log entry.

Severity Warning


Hardware


No




3.2.143 Alarm 3039153


DRAFT



Managed Object EMC

Description 0x71004000: DRP Alarm - The Reserved Lun Pool for Lun<number> has become <x> percent full.


This error is related to MirrorView/Snap view reservedspace. The CLARiiON array gets the following message:The Reserved LUNs assigned to LUN XX havebecome 95 percent full. MirrorView/A doesnot fail.

The next message is: The Reserved LUNs assignedto LUN XX have become 50 percent full.

This is not a problem. MirrorView/A has acquired a new diskfrom the Reserved LUN pool and the session is still running.When a MirrorView/A session reaches 100 percent, it acquiresanother LUN from the Reserved LUN pool. As long as LUNsare available in the Reserved LUN pool when the existingLUN fills up, a new LUN is added to the session. The percentfull varies according to the size of the LUN added and howmany LUNs are already in the session. There is no specificclearing event for this, and it must be cleared manually whenthere is more space in the Reserved LUN pool.

Severity Warning


Hardware


No




3.2.144 Alarm 3039154


Managed Object EMC

Description 0x7100801C: DRP Alarm - There is no more room in theReserved Lun Pool.


The Reserved LUN pool holds the changed blocks forMirrorView/A. When there is no more room in the pool, expectMirrorView/A to fail. There is no specific clearing event forthis, and it must be cleared manually when there is morespace in the Reserved LUN pool.

Severity Major


Hardware


DRAFT



No



Add more LUNs to the reserved pool area.


3.2.145 Alarm 3039155


Managed Object EMC

Description 0x7100802D: DRP Alarm - SnapView has attempted anoperation on a Session that no longer exists.


MirrorView/A mirrors are permanently fractured after cachedirty LUN condition on array. During cleanup and restoration ofmirroring, the secondary images must be removed and addedback to the mirror. When attempting to add the secondaryimage to the mirror a 71008043 or 7100802d error is receivedby the user and the secondary image cannot be added backto the mirror. A layered driver used by MV/A is maintaininginformation related to the primary image LUN and cannotcorrectly identify the owning SP of the primary image. Thisissue is a side effect of the LUNs on the array experiencinga cache dirty condition. As a result, the attempt to add thesecondary image fails. This event is logged for reference andtroubleshooting and cannot be cleared automatically.

Severity Minor


Hardware


No



Remove the secondary and primary image of the MirrorViewand any snaps and then recreate them.


3.2.146 Alarm 3039156


Managed Object EMC

Description 0x71008043: Request sent to a non-owning SP.


DRAFT



A SnapView command was sent to a non-owning SP. Thisevent is logged for reference and troubleshooting and cannotbe cleared automatically.

Severity Minor


Hardware


No


Issue the snap command against the controlling SP for thatLUN.


3.2.147 Alarm 3039157


Managed Object EMC

Description 0x71050200: DRP Alarm - An image was fractured. If thefailure clears automatic resynchronization may be allowed.


An image was fractured for some reason. If the failureclears, automatic resynchronization might be allowed. Thiserror must be investigated further to see the root cause ofthe image fracture. This event is logged for reference andtroubleshooting and cannot be cleared automatically. Afterconnectivity is restored and synchronization continues, thiscondition can be cleared manually.

Severity Major


Hardware


No



Check the event log to determine which failure triggered thisalarm and then fix it. Check to see whether resynchronizationcontinues. If not, contact Comverse customer support.


3.2.148 Alarm 3039158


Managed Object EMC


DRAFT


Description 0x71050201: DRP Alarm - An image was fractured, andadministrator action is required for resynchronization.


An image was fractured for some reason. The synchronizationcannot continue automatically.

This event is logged for reference and troubleshootingand cannot be cleared automatically. After the mirror issynchronized, this event can be cleared.

Severity Minor


Hardware


No



Check the event log to determine which failure triggered thisalarm and then fix it. Restart the synchronization manually.


3.2.149 Alarm 3039159


Managed Object EMC

Description 0x71058238: DRP Alarm - Can’t fracture an image as we’renot the primary K10 and/or controlling SP for the mirror.


The fracture command has been sent to either the incorrectSP (via navicli commands) or the mirror underneath thesecondary array.


Severity Major


Hardware


No



Retry the command and send it to either the correct SP orthe primary array mirror.


3.2.150 Alarm 3039160


DRAFT



Managed Object EMC

Description 0x7105823B: DRP Alarm - Can’t start synchronization aswe’re not the primary K10 and/or controlling SP for the mirror.


The fracture command has been sent to either the incorrectSP (via navicli commands) or the mirror underneath thesecondary array.


Severity Major


Hardware


No

System Impact MirrorView/A management will be impacted.


Retry the command and send it to either the correct SP orthe primary array mirror.


3.2.151 Alarm 3039161


Managed Object EMC

Description 0x71170008: A Fibre Channel connection has becomeinactive.


Something happened to the front-end FC connection. Possiblecauses of the front-end Fiber Loop errors are:■ Customer powered down or rebooted a server■ Customer rebooted the CLARiiON array■ A server has a failed host bus adapter (HBA)■ GBIC or cable going from the switch to the SP on the CX

array failed■ The SP problem

Severity Major


Hardware


Yes; by 3039162


DRAFT


System Impact FC connectivity between host and storage will be impacted,and system performance might be impacted.


To troubleshoot front-end fiber loop errors on the CLARiiONarray, do the following:1 Verify that the user was not booting or powering down

a server, switch, or the CLARiiON array at the time ofthe errors

2 Examine the SP event logs and the fault lights on theCLARiiON array to see if any other errors indicate a badSP

3 If no other errors indicate a bad SP, look at the serverlogs and fault lights on the HBA (if any) to see if theyindicate a failed HBA

4 If the front-end fiber errors continue, replace the cablesand GBICs between the switch and the SP on theCLARiiON array


3.2.152 Alarm 3039162 (Log only)


Managed Object EMC

Description 0x71170009: A Fibre Channel connection has become active.


The front-end fiber loop is up and functional.

Severity Normal


Hardware


No


3.2.153 Alarm 3039163


Managed Object EMC

Description 0x71214000: The service failed to start, or was stopped. Seeerror text for details either at Navisphere Manager or usingNaviCLI.


DRAFT



Various SP services/processes are being impacted by a verybusy system. This is usually seen on busy arrays when anagent indicates loss of contact with CIMON.

Severity Major


Hardware


No



Please contact customer support engineers.

3.2.154 Alarm 3039164


Managed Object EMC

Description 0x71270006: Text is of the form Bus N Disk M status: Thedata area contains sense data from a back-end disk drive.


This is the result of a SCSI check condition.


Severity Minor


Hardware


No


Please contact customer support engineers.


3.2.155 Alarm 3039165


Managed Object EMC

Description 0x71518003: This file is either not a valid upgrade file or iscorrupt. It may have been corrupted during a file transfer.Obtain a new copy and retry the upgrade.


During an upgrade from FLARE 16 to 19, a file is missing orits extension is not supported.


DRAFT


Severity Minor


Hardware


No



If this is the result of an NDU, the NDU (with a Release 16Navisphere) does not handle PBU files.

Do one of the following:■ Unzip the file and point Navisphere at the LST file

contained within the bundle as was done in Release 14and Release 16

■ Obtain a Release 19 Navisphere (Release 19 CLI or theoff-array GUI). Both Release 19 Navisphere utilities canunzip the PBU file before it sends the packages to theNDU


3.2.156 Alarm 3039166


Managed Object EMC

Description 0x71518007: The software package may not be reverted,either because it has already been committed or because noprevious revision is available.


The software package might not be reverted, either because ithas already been committed or because no previous revisionis available. This is caused by a configuration problem, and isunable to revert to an older software revision.


Severity Minor


Hardware


No


Determine which layered application has been installed and ifit can be reverted.



DRAFT


3.2.157 Alarm 3039167


Managed Object EMC

Description 0x7151801D: NDU app caught some sort of exception.


A nondisruptive upgrade (NDU) has failed.

Severity Major


Hardware


Yes; by 3030830

System Impact Upgrade success will be impacted.


Reboot the SP to reset the upgrade, if it is not rebootedautomatically.


3.2.158 Alarm 3039169


Managed Object EMC

Description 0x76008103: Found POST error. See message details eitherat Navisphere Manger or using NaviCLI.


If this event occurs every 60 seconds, the BIOS POST eventlog area is not being properly cleared after the messages aredisplayed.

Severity Major


Hardware


No

System Impact One of the system’s FRUs will be impacted, or performancewill be impacted.




3.2.159 Alarm 3039170


DRAFT



Managed Object EMC

Description 0x79008009: Attempt to consume/delete already consumedobj.


An attempt was made to consume/delete an alreadyconsumed object. This might be a private LUN or a LUN ina storage group.

This is a storage manager action that failed, which means thatit is logged for reference and troubleshooting.

Severity Minor


Hardware


No


Remove a LUN from a storage group before attempting todelete. You can unbind a private LUN but be careful whendoing so. The private LUN must be made public beforeunbinding. If the LUN has Reserved LUN Pool next to its RAIDgroup in Navisphere User Interface (UI), it must be removedfrom the Reserved LUN pool before being unbound.



DRAFT

3: Hardware Agent Alarms Langley 4 Alarms

3.3 Langley 4 AlarmsSearch for the alarm you need by its Specific Problem (Alarm ID).

3.3.1 Alarm 4090101


Managed Object Langley 4

Description The overall server health is now OK.


Server Health

Severity Normal


Hardware


No


3.3.2 Alarm 4090102



Description The overall server health is now degraded.


Server Health

Severity Major


Hardware


Yes; by 4090101

System Impact Server performance or redundancy will be degraded.


This is a generic trap indicating that the general server’s statehas become degraded, noncritical from another state. Thistrap is always accompanied by other traps. Follow these othertraps’ instructions.


3.3.3 Alarm 4090103


DRAFT




Description The overall server health is now critical.


Server Health

Severity Critical


Hardware


Yes; by 4090101

System Impact The server will be in a failed state.


This is a generic trap indicating that the general server’s statehas become degraded, critical from another state. This trapis always accompanied by other traps. Follow these othertraps’ instructions.


3.3.4 Alarm 4090104



Description The overall server health is now nonrecoverable.


Server Health

Severity Critical


Hardware


Yes; by 4090101

System Impact The server will fail.




3.3.5 Alarm 4090105



Description An intrusion to the chassis has been detected.


DRAFT



Server Chassis

Severity Minor


Security


Yes; by 4090106

System Impact No immediate impact. The chassis will be vulnerable toexternal factors.


The chassis top cover is protected from intrusion. If this trapoccurs when the server is not undergoing maintenance,determine if someone is tampering with the server.


3.3.6 Alarm 4090106



Description The chassis intrusion is no longer detected.


Server Chassis

Severity Warning


Security


No


3.3.7 Alarm 4090107



Description The processor experienced an IERR (Internal Error).


CPU

Severity Critical


Hardware


DRAFT



No

System Impact If CPU0 fails, the server will fail. If CPU1 fails, performancewill be degraded.


The processor encountered an internal error. ContactComverse customer support.


3.3.8 Alarm 4090108



Description The processor experienced a thermal trip.


CPU

Severity Critical


Hardware


No



The processor reached its critical temperature, either due toinsufficient cooling or heatsink decoupling issues. ContactComverse customer support.


3.3.9 Alarm 4090109



Description The processor experienced an FRB1 error, BIST failure.


CPU

Severity Critical


Hardware


No


DRAFT




The CPU has failed its self-test. Contact Comverse customersupport.


3.3.10 Alarm 4090110



Description The processor experienced an FRB2 error, hang in POSTfailure.


CPU

Severity Critical


Hardware


No



The CPU has failed. Contact Comverse customer support.


3.3.11 Alarm 4090111



Description The processor experienced an FRB3 error, initialization failure.


CPU

Severity Critical


Hardware


No


DRAFT






3.3.12 Alarm 4090112



Description The processor experienced a configuration error.


CPU

Severity Critical


Hardware


No





3.3.13 Alarm 4090113



Description The processor presence has been detected.


CPU

Severity Normal


Hardware


No



DRAFT


3.3.14 Alarm 4090114



Description The processor has been disabled.


CPU

Severity Critical


Hardware


No

System Impact Server performance will be degraded.


The processor was disabled. If this trap occurs when noplanned maintenance is being done, contact Comversecustomer support.


3.3.15 Alarm 4090115



Description The processor has encountered an SMBIOS uncorrectableCPU-Complex error.


CPU

Severity Critical


Hardware


No





3.3.16 Alarm 4090116


DRAFT




Description The power supply unit is fully redundant.


Power Redundancy

Severity Normal


Hardware


No


3.3.17 Alarm 4090117



Description The power supply unit redundancy has been degraded.


Power Redundancy

Severity Major


Hardware


Yes; by 4090116

System Impact Another power supply failure might cause the server to fail.




3.3.18 Alarm 4090118



Description The power supply unit redundancy has been lost.


Power Redundancy

Severity Critical


DRAFT



Hardware


Yes; by 4090116

System Impact The server will fail if the other power supply is lost.


One power supply has failed or has been pulled out. If this isnot a planned event, contact Comverse customer support.


3.3.19 Alarm 4090119



Description The power supply <PowerSupply> presence has beendetected.


<PowerSupply>

Severity Normal


Hardware


No


3.3.20 Alarm 4090120



Description The power supply <PowerSupply> is no longer detected aspresent.


<PowerSupply>

Severity Major


Hardware


Yes; by 4090119


DRAFT


System Impact The server will fail if the other power supply is lost.


This trap indicates a user removal of a power supply unit.If this is not a planned event, contact Comverse customersupport.


3.3.21 Alarm 4090121



Description The power supply <PowerSupply> has failed.


<PowerSupply>

Severity Critical


Hardware


Yes; by 4090116

System Impact Another power supply failure might cause the server to fail.


One of the power supply units has failed. Contact Comversecustomer support.


3.3.22 Alarm 4090122



Description Failure of this power supply <PowerSupply> has beenpredicted.


<PowerSupply>

Severity Minor


Hardware


Yes; by 4090116


DRAFT


System Impact Power supply will fail.


One of the power supply units is predicted to fail. Replacementof this power supply unit is recommended. Contact Comversecustomer support.


3.3.23 Alarm 4090123



Description The power supply <PowerSupply> AC/DC connection hasbeen lost.


<PowerSupply>

Severity Critical


Hardware


Yes; by 4090116

System Impact The server will fail if the other power supply input is lost.


The AC/DC power feed to the power supply has been lost.Check the power feed to the unit.


3.3.24 Alarm 4090125



Description <VoltageSensor>: Current reading is below lowernonrecoverable threshold. Status for this sensor isnonrecoverable.


<VoltageSensor>

Severity Critical


Hardware


Yes; by 4090128


DRAFT


Threshold ■ Baseboard 1.2V: 1.07■ Baseboard 1.25V: 1.02■ Baseboard 1.8V: 1.60■ Baseboard 1.8VSB: 1.60■ Baseboard 2.5V: 2.16■ Baseboard 3.3V: 2.99■ Baseboard 3.3AUX: 2.92■ Baseboard 5.0V: 4.52■ Baseboard 5VSB: 4.44■ Baseboard 12V: 10.79■ Baseboard 12VRM: 10.60■ Baseboard -12V: -13.84■ Baseboard VBAT: 2.68 Processor Vccp: 1.03

System Impact Server failure might be imminent.


There a problem with one of the server’s voltages. ContactComverse customer support.


3.3.25 Alarm 4090126



Description <VoltageSensor>: Current reading is below lower criticalthreshold. Status for this sensor is critical.


<VoltageSensor>

Severity Critical


Hardware


Yes; by 4090128


DRAFT



System Impact The server might fail either partially or completely.


One or more of the server’s voltages is below the lower criticalthreshold. Contact Comverse customer support.


3.3.26 Alarm 4090127



Description <VoltageSensor>: Current reading is below lower noncriticalthreshold. Status for this sensor is noncritical.


<VoltageSensor>

Severity Minor


Hardware


Yes; by 4090128


DRAFT





One or more of the server’s voltages is below the lowernoncritical threshold. No immediate action is required;however, action is required if there is an escalated trap.


3.3.27 Alarm 4090128



Description <VoltageSensor>: Current reading is within normal thresholds,status is OK.


<VoltageSensor>

Severity Normal


Hardware


No


3.3.28 Alarm 4090129




DRAFT


Description <VoltageSensor>: Current reading exceeds upper noncriticalthreshold. Status for this sensor is noncritical.


<VoltageSensor>

Severity Minor


Hardware


Yes; by 4090128


System Impact High voltage might cause the server to fail.


A voltage value went above its upper noncritical value. Noimmediate action is required; however, action is required ifthere is an escalated trap.


3.3.29 Alarm 4090130



Description <VoltageSensor>: Current reading exceeds upper criticalthreshold. Status for this sensor is critical.


<VoltageSensor>

Severity Critical


Hardware


DRAFT



Yes; by 4090128




A voltage value went above its upper critical value. ContactComverse customer support.


3.3.30 Alarm 4090131



Description <VoltageSensor>: Current reading exceeds uppernonrecoverable threshold. Status for this sensor isnonrecoverable.


<VoltageSensor>

Severity Critical


Hardware


Yes; by 4090128


DRAFT



System Impact Server failure might be imminent.


There a problem with one of the server’s voltages. ContactComverse customer support


3.3.31 Alarm 4090132



Description The discrete voltage sensor meets performance standards:<VoltageSensor>.


<VoltageSensor>

Severity Normal


Hardware


No


3.3.32 Alarm 4090133




DRAFT


Description The discrete voltage sensor lags from performance standards:<VoltageSensor>.


<VoltageSensor>

Severity Critical


Hardware


Yes; by 4090132

System Impact The server might have degraded performance or might shutdown.


The specified voltage value has reached its critical value.Contact Comverse customer support.


3.3.33 Alarm 4090134



Description A single-bit error occurred in memory.


Memory

Severity Warning


Hardware


No


A single-bit error occurred in memory and was corrected bythe ECC mechanism. If this event occurs frequently, one ormore memory DIMMs might need to be replaced.


3.3.34 Alarm 4090135



Description A multi-bit error occurred in memory.


Memory


DRAFT


Severity Major


Hardware


No

System Impact Software applications running on the server might crash orrun with errors.


One or more memory DIMMs must be replaced. ContactComverse customer support.


3.3.35 Alarm 4090136



Description A parity error occurred in memory.


Memory

Severity Major


Hardware


No

System Impact Software applications running on the server might crash orrun with errors.


If this trap appears frequently, one or more memory DIMMsmust be replaced. Contact Comverse customer support.


3.3.36 Alarm 4090137



Description Memory scrub failed (stuck bit) error occurred in memory.


Memory

Severity Major


Hardware


DRAFT



No

System Impact Server performance and data integrity might be degraded.


There might be issues with memory integrity. ContactComverse customer support.


3.3.37 Alarm 4090138



Description Memory device was disabled.


Memory

Severity Major


Hardware


No

System Impact The server’s memory capacity will be reduced, andperformance might be degraded.


A memory DIMM was put out from the memory bank, mostlikely due to a fault. Contact Comverse customer support toreplace the faulty memory.


3.3.38 Alarm 4090139



Description Correctable error logging limit reached for memory device.


Memory

Severity Major


Hardware


No


DRAFT


System Impact Server performance and data integrity might be degraded.


There might be issues with memory integrity. ContactComverse customer support.


3.3.39 Alarm 4090140



Description Cooling unit is fully redundant.


Fan Redundancy

Severity Normal


Hardware


No


3.3.40 Alarm 4090141



Description Cooling unit redundancy has been degraded.


Fan Redundancy

Severity Minor


Hardware


Yes; by 4090140

System Impact Another cooling unit failure will cause the server to overheatand shut down.


One or more system fans have failed. Contact Comversecustomer support.



DRAFT


3.3.41 Alarm 4090142



Description Cooling unit redundancy has been lost.


Fan Redundancy

Severity Major


Hardware


Yes; by 4090140

System Impact Server overheating might cause slow performance or acomplete server failure.


One or more system fans have failed. Contact Comversecustomer support.


3.3.42 Alarm 4090143



Description <fanSensor>: Current reading is below lower nonrecoverablethreshold. Status for this sensor is nonrecoverable.


<fanSensor>

Severity Critical


Hardware


Yes; by 4090146

Threshold 80mm Sys Fan: 1836.00 40mm Sys Fan: 3264.00 PowerCage Fan: 4500.00

System Impact Fan failure might cause the server to overheat and shut down.


A system fan has failed. Contact Comverse customer support.



DRAFT


3.3.43 Alarm 4090144



Description <fanSensor>: Current reading is below lower critical threshold.Status for this sensor is critical.


<fanSensor>

Severity Critical


Hardware


Yes; by 4090146




A fan speed went below its critical speed threshold, probablydue to a fan failure. Contact Comverse customer support.


3.3.44 Alarm 4090145



Description <fanSensor>: Current reading is below lower noncriticalthreshold. Status for this sensor is noncritical.


<fanSensor>

Severity Minor


Hardware


Yes; by 4090146


System Impact Fan failure might cause the server to overheat and shut down.


A fan speed went below its noncritical speed threshold. Noimmediate action is required; however, action is required ifthere is an escalated trap.



DRAFT


3.3.45 Alarm 4090146



Description <fanSensor>: Current reading is within normal thresholds,status is OK.


<fanSensor>

Severity Normal


Hardware


No


3.3.46 Alarm 4090147



Description The discrete cooling device meets performance standards:<fanSensor>.


<fanSensor>

Severity Normal


Hardware


No


3.3.47 Alarm 4090148



Description The discrete cooling device lags from performance standards:<fanSensor>.


<fanSensor>


DRAFT


Severity Critical


Hardware


Yes; by 4090147

System Impact Server overheating might cause slow performance or acomplete server failure.


The specified fan speed has reached its critical value. ContactComverse customer support.


3.3.48 Alarm 4090149



Description <tempSensor>: Current reading is below lower nonrecoverablethreshold. Status for this sensor is nonrecoverable.


<tempSensor>

Severity Critical


Hardware


Yes; by 4090152

Threshold ■ Baseboard Temp: -10.00■ FntPnl Amb Temp: -10.00■ Power Cage Temp: -10.00■ Processor1 Temp: -10.00■ Processor2 Temp: -10.00

System Impact The server will not be able to reliably report thermal issues,which might put the server’s integrity at risk.


There is a problem with the temperature sensor. ContactComverse customer support.


3.3.49 Alarm 4090150




DRAFT


Description <tempSensor>: Current reading is below lower criticalthreshold. Status for this sensor is critical.


<tempSensor>

Severity Critical


Hardware


Yes; by 4090152




The server’s temperature value went below its lower criticalvalue. Ensure that the server’s environment is providing theproper ambient temperature. If it is, and the problem remains,contact Comverse customer support.


3.3.50 Alarm 4090151



Description <tempSensor>: Current reading is below lower noncriticalthreshold. Status for this sensor is noncritical.


<tempSensor>

Severity Minor


Hardware


Yes; by 4090152



DRAFT


System Impact Too low temperature might cause the server to fail.


The server’s temperature value went below its lowernoncritical value. Ensure that the server’s environment isproviding the proper ambient temperature. Further action isrequired if there is an escalated trap.


3.3.51 Alarm 4090152



Description <tempSensor>: Current reading is within normal thresholds,status is OK.


<tempSensor>

Severity Normal


Hardware


No


3.3.52 Alarm 4090153



Description Current reading exceeds upper noncritical threshold. Statusfor this sensor is noncritical.


<tempSensor>

Severity Minor


Hardware


Yes; by 4090152


DRAFT


Threshold ■ Baseboard Temp: 60.00■ FntPnl Amb Temp: 40.00■ Power Cage Temp: 60.00■ Processor1 Temp: 75.00■ Processor2 Temp: 75.00

System Impact Too high temperature might cause the server to fail.


The server’s temperature value went above its lowernoncritical value. Ensure that the server’s environment isproviding the proper ambient temperature. Further action isrequired if there is an escalated trap.


3.3.53 Alarm 4090154



Description <tempSensor>: Current reading exceeds upper criticalthreshold. Status for this sensor is critical.


<tempSensor>

Severity Critical


Hardware


Yes; by 4090152




The server’s temperature value went above its lower criticalvalue. Ensure that the server’s environment is providing theproper ambient temperature. If it is, and the problem remains,contact Comverse customer support.


3.3.54 Alarm 4090155


DRAFT




Description <tempSensor>: Current reading exceeds uppernonrecoverable threshold. Status for this sensor isnonrecoverable.


<tempSensor>

Severity Critical


Hardware


Yes; by 4090152


System Impact The server will not be able to reliably report thermal issues,which might put the server’s integrity at risk.


There is a problem with the temperature sensor. ContactComverse customer support.


3.3.55 Alarm 4090156



Description The system BIOS has been reconfigured.


System

Severity Warning


Hardware


No

System Impact BIOS changes might affect the server’s performance andstability.


The BIOS setup was changed. Contact Comverse customersupport to determine if this change was coordinated andapproved.


DRAFT



3.3.56 Alarm 4090157



Description The system has booted.


System

Severity Normal


Hardware


No



DRAFT

3: Hardware Agent Alarms LSI Alarms

3.4 LSI AlarmsSearch for the alarm you need by its Specific Problem (Alarm ID).

3.4.1 Alarm 3080001


Managed Object LSI

Description A physical disk has been placed online.


Controller: <$2> Target: <$7> LUN: <$8>

Severity Normal


Hardware


No

System Impact No impact.


3.4.2 Alarm 3080003


Managed Object LSI

Description Physical disk error found.



Severity Critical


Hardware


No

System Impact No impact. Hot spare disk will go online.


Replace the faulty disk.


3.4.3 Alarm 3080004


DRAFT



Managed Object LSI

Description Physical disk PFA condition found.



Severity Major


Hardware


No

System Impact No impact. If the disk fails, there is a hot spare disk that willgo online.




3.4.4 Alarm 3080005


Managed Object LSI

Description Automatic rebuild has started.



Severity Warning


Hardware


Yes; by 3080007



3.4.5 Alarm 3080006


Managed Object LSI

Description Rebuild has started.




DRAFT


Severity Normal


Hardware


No



3.4.6 Alarm 3080007


Managed Object LSI

Description Rebuild has been completed.



Severity Normal


Hardware


No



3.4.7 Alarm 3080008


Managed Object LSI

Description Rebuild has been cancelled.



Severity Normal


Hardware


No

System Impact No impact on data. The LUN will be in critical status, and diskredundancy will be lost.


Check if this action was initiated by a user.


DRAFT



3.4.8 Alarm 3080009


Managed Object LSI

Description Rebuild has been stopped with error.



Severity Critical


Hardware


No

System Impact Might cause data loss.


Check the LUN status and act accordingly.


3.4.9 Alarm 3080010


Managed Object LSI

Description New physical disk failed - rebuild has been stopped with error.



Severity Critical


Hardware


No

System Impact If a second disk fails during rebuild, data loss will occur.




3.4.10 Alarm 3080011


DRAFT



Managed Object LSI

Description Logical drive failed - rebuild has been stopped.



Severity Major


Hardware


No

System Impact Downtime - LUN failed. Might cause data loss.




3.4.11 Alarm 3080012


Managed Object LSI

Description Physical disk has failed.



Severity Critical


Hardware


No





3.4.12 Alarm 3080013


Managed Object LSI

Description A new physical disk has been found.


DRAFT




Severity Normal


Hardware


No



3.4.13 Alarm 3080014


Managed Object LSI

Description Physical disk has been removed.



Severity Minor


Hardware


No





3.4.14 Alarm 3080019


Managed Object LSI

Description SCSI command time-out on physical disk.



Severity Major


Hardware


No


DRAFT


System Impact No impact on data. Might result in loss of redundancy.


Check the physical device status and replace if faulty.


3.4.15 Alarm 3080022


Managed Object LSI

Description Parity error found.



Severity Major


Hardware


No

System Impact No impact if all physical devices are online; otherwise, dataloss will occur.


Check the physical device status and replace if faulty.


3.4.16 Alarm 3080050


Managed Object LSI

Description Physical disk status has changed to offline. The service is upmust be handled immediately (within 2 hours).



Severity Critical


Hardware


No



Replace the offline disk.


DRAFT



3.4.17 Alarm 3080051


Managed Object LSI

Description Physical disk status has changed to hot spare.



Severity Normal


Hardware


No



3.4.18 Alarm 3080052


Managed Object LSI

Description Physical disk status has changed to rebuild.



Severity Normal


Hardware


No



3.4.19 Alarm 3080054


Managed Object LSI

Description Physical disk failed to start.


DRAFT




Severity Major


Hardware


No





3.4.20 Alarm 3080059


Managed Object LSI

Description Physical disk is switching from one channel to the otherchannel.



Severity Major


Hardware


No

System Impact No impact. Loss of disk redundancy in case of disk failure.Loss of FC loop redundancy in case of loop failure.


If only a single disk shows this alarm, replace it; otherwise,contact Comverse customer support.


3.4.21 Alarm 3080067


Managed Object LSI

Description Physical disk found on only one disk channel.



Severity Major


DRAFT



Hardware


No

System Impact No impact. Loss of disk redundancy in case of disk failure.Loss of FC loop redundancy in case of loop failure.


If only a single disk shows this alarm, replace it; otherwise,contact Comverse customer support.


3.4.22 Alarm 3080068


Managed Object LSI

Description Physical disk type is not approved by vendor.



Severity Minor


Hardware


No



Replace the disk with an approved type.


3.4.23 Alarm 3080069


Managed Object LSI

Description Physical disk has acquired an inappropriate loop ID. Enclosuredisk-slot operations are disabled while this condition persists.



Severity Major


Hardware


DRAFT



No



Replace the disk.


3.4.24 Alarm 3080070


Managed Object LSI

Description Physical disk port has failed or cannot operate at theconfigured channel speed.



Severity Major


Hardware


No



Replace the disk.


3.4.25 Alarm 3080071


Managed Object LSI

Description Mirror Race recovery has failed for logical drive.


Controller: <$2> Logical Drive: <$5>

Severity Major


Hardware


No


DRAFT


System Impact If LUN is offline, the system will be down.


Contact Comverse customer support to check the LUN status.


3.4.26 Alarm 3080073


Managed Object LSI

Description Online controller firmware upgrade has started.


Controller: <$2>

Severity Normal


Hardware


No

System Impact Downtime during controller firmware upgrade.


Check if this action was initiated by a user. This action shouldnot be done while the system is online.


3.4.27 Alarm 3080074


Managed Object LSI

Description Online firmware upgrade has been completed successfully.


Controller: <$2>

Severity Normal


Hardware


No




DRAFT


3.4.28 Alarm 3080075


Managed Object LSI

Description Online firmware upgrade has failed.


Controller: <$2>

Severity Normal


Hardware


No

System Impact No impact. System is down during this operation.


This alarm occurs when a storage expert is upgrading thesystem.


3.4.29 Alarm 3080096


Managed Object LSI

Description Device loop ID conflict (soft addressing) detected.


Controller:<$2> Channel:<$5>

Severity Critical


Hardware


No

System Impact Risk of data corruption.


A conflict was detected on a disk channel, causing softaddressing, which can lead to data corruption. This usuallyoccurs when you have DF4000 with expansion JBODsattached and the DIP switches on the back of the enclosure(s)have not been set properly. To correct this problem, checkthe DIP switch, and set appropriately. If the problem persists,contact Comverse customer support.



DRAFT


3.4.30 Alarm 3080098


Managed Object LSI

Description The host fiber channel is down.


Controller: <$2>

Severity Major


Hardware


Yes; by 3080099

System Impact Loss of storage path redundancy.


Check the fiber channel to host.


3.4.31 Alarm 3080099


Managed Object LSI

Description The host fiber channel is up.


Controller: <$2>

Severity Normal


Hardware


No



3.4.32 Alarm 3080128


Managed Object LSI

Description Consistency check has started.


DRAFT




Severity Normal


Hardware


No



Check the DIP switch, and set appropriately.


3.4.33 Alarm 3080129


Managed Object LSI

Description Consistency check has finished.



Severity Normal


Hardware


No



3.4.34 Alarm 3080130


Managed Object LSI

Description Consistency check has been cancelled.



Severity Normal


Hardware


DRAFT



No



3.4.35 Alarm 3080131


Managed Object LSI

Description Consistency check on logical drive error.



Severity Major


Hardware


No

System Impact No impact. Loss of disk redundancy in case of disk failure.




3.4.36 Alarm 3080132


Managed Object LSI

Description Consistency check on logical drive has failed.



Severity Major


Hardware


No






DRAFT


3.4.37 Alarm 3080133


Managed Object LSI

Description Consistency check has failed due to physical disk failure.



Severity Major


Hardware


No





3.4.38 Alarm 3080134


Managed Object LSI

Description Logical drive has been made offline.



Severity Critical


Hardware


No

System Impact Downtime - LUN is offline. Causes data loss.




3.4.39 Alarm 3080135


Managed Object LSI


DRAFT


Description Logical drive is critical.



Severity Critical


Hardware


Yes; by 3080136

System Impact No impact to system. Loss of disk redundancy within a LUN.




3.4.40 Alarm 3080136


Managed Object LSI

Description Logical drive has been placed online.



Severity Normal


Hardware


No



3.4.41 Alarm 3080144


Managed Object LSI

Description Logical drive initialization has started.



Severity Normal


Hardware


DRAFT



No

System Impact This action erases all data in storage. System is down and alldata is lost while performing this action.


Check if this action was initiated by a user. This action erasesall storage data.


3.4.42 Alarm 3080145


Managed Object LSI

Description Logical drive initialization is done.



Severity Normal


Hardware


No





3.4.43 Alarm 3080146


Managed Object LSI

Description Logical drive initialization has been cancelled.



Severity Normal


Hardware


No


DRAFT






3.4.44 Alarm 3080147


Managed Object LSI

Description Logical drive initialization has failed.



Severity Major


Hardware


No





3.4.45 Alarm 3080150


Managed Object LSI

Description Expand capacity has started.



Severity Normal


Hardware


No





DRAFT



3.4.46 Alarm 3080151


Managed Object LSI

Description Expand capacity has been completed.



Severity Normal


Hardware


No



3.4.47 Alarm 3080152


Managed Object LSI

Description Expand capacity has stopped with error.



Severity Major


Hardware


No

System Impact Impact only for the expanded capacity activity.


This action must only be done by a storage expert who checksfor a reason in case of error.


3.4.48 Alarm 3080153


Managed Object LSI


DRAFT


Description Bad blocks have been found.



Severity Major


Hardware


No

System Impact No impact. Bad blocks may result in disk failure and in thiscase, loss of disk redundancy.


3.4.49 Alarm 3080157


Managed Object LSI

Description Logical drive LUN mapping has been written to configuration.


Controller: <$2>

Severity Normal


Hardware


No





3.4.50 Alarm 3080176


Managed Object LSI

Description Logical drive background initialization has started.



Severity Normal


Hardware


DRAFT



No





3.4.51 Alarm 3080177


Managed Object LSI

Description Logical drive background initialization has stopped.



Severity Normal


Hardware


No





3.4.52 Alarm 3080178


Managed Object LSI

Description Logical drive background initialization has been paused.



Severity Normal


Hardware


No


DRAFT






3.4.53 Alarm 3080179


Managed Object LSI

Description Logical drive background initialization has restarted.



Severity Normal


Hardware


No





3.4.54 Alarm 3080180


Managed Object LSI

Description Logical drive background initialization has failed.



Severity Major


Hardware


No


DRAFT






3.4.55 Alarm 3080181


Managed Object LSI

Description Logical drive background initialization has been completed.



Severity Normal


Hardware


No





3.4.56 Alarm 3080320


Managed Object LSI

Description Fan failure.


Controller:<$2> Enclosure:<$5> Unit: <$7>

Severity Major


Hardware


Yes; by 3080321

System Impact Loss of cooling redundancy.


Replace the fan.


DRAFT



3.4.57 Alarm 3080321


Managed Object LSI

Description Fan has been restored.



Severity Normal


Hardware


No



3.4.58 Alarm 3080322


Managed Object LSI

Description Fan is not present.



Severity Major


Hardware


Yes; by 3080321

System Impact Loss of cooling redundancy.


Insert the fan module.


3.4.59 Alarm 3080323


Managed Object LSI


DRAFT


Description Power supply failure.



Severity Major


Hardware


Yes; by 3080324

System Impact Loss of power supply redundancy.


Replace the power supply.


3.4.60 Alarm 3080324


Managed Object LSI

Description Power supply has been restored.



Severity Normal


Hardware


No



3.4.61 Alarm 3080325


Managed Object LSI

Description Power supply is not present.



Severity Major


Hardware


DRAFT



Yes; by 3080324

System Impact Loss of power supply redundancy.


Contact Comverse customer support to check power status.


3.4.62 Alarm 3080326


Managed Object LSI

Description Temperature is over safe limit. Failure imminent.



Severity Critical


Hardware


Yes; by 3080328

Threshold 68 C

System Impact Danger of downtime due to high system temperature.


Check temperature at the site.


3.4.63 Alarm 3080327


Managed Object LSI

Description Temperature is above working limit.



Severity Critical


Hardware


Yes; by 3080328

Threshold 64 C


DRAFT


System Impact Danger of downtime due to high system temperature.


Check temperature at the site.


3.4.64 Alarm 3080328


Managed Object LSI

Description Normal temperature has been restored.



Severity Normal


Hardware


No



3.4.65 Alarm 3080329


Managed Object LSI

Description Temperature sensor is not present.



Severity Major


Hardware


No

System Impact No impact. System is exposed to high temperature with noalarm. Repair action is needed.


Contact Comverse customer support about the temperaturesensor.



DRAFT


3.4.66 Alarm 3080331


Managed Object LSI

Description Enclosure access has been restored.


Controller:<$2> Enclosure:<$5>

Severity Normal


Hardware


No



3.4.67 Alarm 3080332


Managed Object LSI

Description Enclosure access is offline.



Severity Major


Hardware


Yes; by 3080331



If no other component failure is reported, a reset to thecontroller may be needed. Contact Comverse customersupport for more help.


3.4.68 Alarm 3080333


Managed Object LSI

Description Enclosure soft addressing detected.


DRAFT




Severity Critical


Hardware


No

System Impact Risk of data corruption.


A conflict was detected on a disk channel, causing softaddressing, which can lead to data corruption. This usuallyoccurs when you have DF4000 with expansion JBODsattached and the DIP switches on the back of the enclosure(s)have not been set properly. To correct this problem, checkthe DIP switch, and set appropriately. If the problem persists,contact Comverse customer support.


3.4.69 Alarm 3080334


Managed Object LSI

Description Enclosure services ready.


Controller: <$2>

Severity Normal


Hardware


No



3.4.70 Alarm 3080335


Managed Object LSI

Description Access to temperature sensor has been lost.



Severity Major


DRAFT



Hardware


No

System Impact No impact. System is exposed to high temperature with noalarm. Repair action is needed.


Verify that the I/O card is in place. Contact Comversecustomer support for more help.


3.4.71 Alarm 3080336


Managed Object LSI

Description Access to power supply status information has been lost.



Severity Major


Hardware


No





3.4.72 Alarm 3080337


Managed Object LSI

Description Access to fan status information has been lost.



Severity Major


Hardware


No


DRAFT






3.4.73 Alarm 3080338


Managed Object LSI

Description Physical disks in enclosure are being spun down.



Severity Critical


Hardware


No

System Impact Might result in data corruption or downtime.




3.4.74 Alarm 3080339


Managed Object LSI

Description Temperature is below working limit.



Severity Critical


Hardware


Yes; by 3080328

Threshold 25 C

System Impact Danger of downtime due to low system temperature.


Check the temperature at the site.


DRAFT



3.4.75 Alarm 3080340


Managed Object LSI

Description Temperature is under safe limit. Failure imminent.



Severity Critical


Hardware


Yes; by 3080328

Threshold 15 C

System Impact Danger of downtime due to low system temperature.


Check the temperature at the site.


3.4.76 Alarm 3080384


Managed Object LSI

Description Array management server software started successfully.

Severity Normal


Hardware


No

System Impact No impact


3.4.77 Alarm 3080389


Managed Object LSI


DRAFT


Description Controller has been reset.


Controller: <$2>

Severity Major


Hardware


No

System Impact Downtime during controller reset.


Check if this action was initiated by a user during systemdowntime. Contact Comverse customer support.


3.4.78 Alarm 3080392


Managed Object LSI

Description Battery present.


Controller: <$2>

Severity Normal


Hardware


No



3.4.79 Alarm 3080393


Managed Object LSI

Description Battery power low.


Controller: <$2>

Severity Major


Hardware


DRAFT



Yes; by 3080394

System Impact Causes the system to work without cache, no impact onsystem functionality.


Recharge or replace the battery.


3.4.80 Alarm 3080394


Managed Object LSI

Description Battery power OK.


Controller: <$2>

Severity Normal


Hardware


No



3.4.81 Alarm 3080400


Managed Object LSI

Description Battery reconditioning has started.


Controller: <$2>

Severity Normal


Hardware


No




DRAFT


3.4.82 Alarm 3080401


Managed Object LSI

Description Battery reconditioning has finished.


Controller: <$2>

Severity Normal


Hardware


No



3.4.83 Alarm 3080402


Managed Object LSI

Description Battery reconditioning has been canceled.


Controller: <$2>

Severity Normal


Hardware


No



3.4.84 Alarm 3080405


Managed Object LSI

Description The Battery Backup Unit has been removed.


Controller: <$2>


DRAFT


Severity Major


Hardware


Yes; by 3080392



Replace the battery component.


3.4.85 Alarm 3080406


Managed Object LSI

Description WARM BOOT has failed.


Controller: <$2>

Severity Critical


Hardware


No

System Impact Might result in downtime.




3.4.86 Alarm 3080407


Managed Object LSI

Description Battery calibration cycle has started.


Controller: <$2>

Severity Normal


Hardware


DRAFT



No



3.4.87 Alarm 3080408


Managed Object LSI

Description Battery calibration cycle has finished.


Controller: <$2>

Severity Normal


Hardware


No



3.4.88 Alarm 3080409


Managed Object LSI

Description Battery calibration cycle has been cancelled.


Controller: <$2>

Severity Normal


Hardware


No



3.4.89 Alarm 3080410


DRAFT



Managed Object LSI

Description Battery is not present.


Controller: <$2>

Severity Major


Hardware


Yes; by 3080392



Insert the BBU in the enclosure.


3.4.90 Alarm 3080411


Managed Object LSI

Description Controller entered conservative cache mode.


Controller: <$2>

Severity Major


Hardware


Yes; by 3080412





3.4.91 Alarm 3080412


Managed Object LSI

Description Controller entered normal cache mode.


DRAFT



Controller: <$2>

Severity Minor


Hardware


Yes; by 3080411



3.4.92 Alarm 3080413


Managed Object LSI

Description Controller device start complete.


Controller: <$2>

Severity Minor


Hardware


No



3.4.93 Alarm 3080414


Managed Object LSI

Description Soft ECC error corrected.


Controller: <$2>

Severity Major


Hardware


No


DRAFT






3.4.94 Alarm 3080416


Managed Object LSI

Description Battery recondition suggested.


Controller: <$2>

Severity Normal


Hardware


No



3.4.95 Alarm 3080419


Managed Object LSI

Description Updated partner’s status.


Controller: <$2>

Severity Normal


Hardware


No



3.4.96 Alarm 3080420


DRAFT



Managed Object LSI

Description Relinquished partner.


Controller: <$2>

Severity Normal


Hardware


No



3.4.97 Alarm 3080422


Managed Object LSI

Description Dual controllers enabled.


Controller: <$2>

Severity Normal


Hardware


No



3.4.98 Alarm 3080423


Managed Object LSI

Description Disabled partner.


Controller: <$2>

Severity Major


Hardware


DRAFT



No

System Impact No impact. Loss of controller redundancy.


One of the two controllers is down. Check the controller’shealth.


3.4.99 Alarm 3080424


Managed Object LSI

Description Dual controllers entered nexus.


Controller: <$2>

Severity Normal


Hardware


No



3.4.100 Alarm 3080425


Managed Object LSI

Description Controller boot ROM image needs to be reloaded.


Controller: <$2>

Severity Major


Hardware


No

System Impact No impact. Loss of controller redundancy.





DRAFT


3.4.101 Alarm 3080432


Managed Object LSI

Description Dual-active automatic flash of replacement controller.


Controller: <$2>

Severity Normal


Hardware


No



3.4.102 Alarm 3080434


Managed Object LSI

Description Dual-active negotiation failed IDs.


Controller: <$2>

Severity Major


Hardware


No





3.4.103 Alarm 3080435


Managed Object LSI

Description Dual-active negotiation failed board types.


DRAFT



Controller: <$2>

Severity Major


Hardware


No





3.4.104 Alarm 3080436


Managed Object LSI

Description Dual-active negotiation failed disk channels.


Controller: <$2>

Severity Major


Hardware


No



Check the rear panel for orange LEDs. Contact Comversecustomer support.


3.4.105 Alarm 3080437


Managed Object LSI

Description Dual-active negotiation failed host ports.


Controller: <$2>

Severity Major


Hardware


DRAFT



No



Check the rear panel for orange LEDs. Contact Comversecustomer support.


3.4.106 Alarm 3080438


Managed Object LSI

Description Dual-active negotiation failed memory size.


Controller: <$2>

Severity Major


Hardware


No





3.4.107 Alarm 3080439


Managed Object LSI

Description Dual-active negotiation failed cache memory size.


Controller: <$2>

Severity Major


Hardware


No





DRAFT



3.4.108 Alarm 3080440


Managed Object LSI

Description Error in Mirror Race table.



Severity Major


Hardware


No





3.4.109 Alarm 3080441


Managed Object LSI

Description A replacement controller attempted to stop the survivingcontroller.


Controller: <$2>

Severity Major


Hardware


No





3.4.110 Alarm 3080519


DRAFT



Managed Object LSI

Description Battery test has started.


Controller: <$2>

Severity Normal


Hardware


No



3.4.111 Alarm 3080520


Managed Object LSI

Description Battery test is complete.


Controller: <$2>

Severity Normal


Hardware


No



3.4.112 Alarm 3080521


Managed Object LSI

Description Battery test has been canceled.


Controller: <$2>

Severity Normal


Hardware


DRAFT



No



3.4.113 Alarm 3080522


Managed Object LSI

Description Battery test has failed - battery bad.


Controller: <$2>

Severity Major


Hardware


No

System Impact Causes system to work without cache, no impact on systemfunctionality.


Replace the battery.


3.4.114 Alarm 3080644


Managed Object LSI

Description Back-end fiber dead.



Severity Major


Hardware


Yes; by 3080645

System Impact No impact. Loss of FC loops redundancy.


Check the I/O card, the fiber cables, and the color of the LEDson the rear panel (green = OK, orange = fault).



DRAFT


3.4.115 Alarm 3080645


Managed Object LSI

Description Back-end fiber alive.



Severity Normal


Hardware


No



3.4.116 Alarm 3080700


Managed Object LSI

Description Event log empty.


Controller: <$2>

Severity Normal


Hardware


No



3.4.117 Alarm 3080701


Managed Object LSI

Description Event log entries lost.


Controller: <$2>


DRAFT


Severity Normal


Hardware


No



3.4.118 Alarm 3080702


Managed Object LSI

Description Request sense.



Severity Minor


Hardware


No



Contact Comverse customer support. This trap may be thefirst sign of a failing disk.


3.4.119 Alarm 3080800


Managed Object LSI

Description New configuration has been received.


Controller: <$2>

Severity Normal


Hardware


No



DRAFT



3.4.120 Alarm 3080801


Managed Object LSI

Description Configuration has been cleared.


Controller: <$2>

Severity Normal


Hardware


No



3.4.121 Alarm 3080806


Managed Object LSI

Description A debug dump exists on this system.


Controller: <$2>

Severity Normal


Hardware


No



3.4.122 Alarm 3080807


Managed Object LSI

Description A debug dump exists on this system.


DRAFT



Controller: <$2>

Severity Normal


Hardware


No



3.4.123 Alarm 3080808


Managed Object LSI

Description No valid Configuration On Disk (COD) found.


Controller: <$2>

Severity Normal


Hardware


No



3.4.124 Alarm 3080809


Managed Object LSI

Description No valid SAN map found in Configuration On Disk (COD)found.


Controller: <$2>

Severity Normal


Hardware


No



DRAFT




DRAFT

3: Hardware Agent Alarms Netra 240/440 Hardware Alarms (OnGuard Agent)

3.5 Netra 240/440 Hardware Alarms (OnGuardAgent)Search for the alarm you need by its Specific Problem (Alarm ID).

3.5.1 Alarm 2112042


Managed Object OnGuard

Description CPU fan 2 has failed.


CPU fan

Severity Major


Hardware


No

System Impact Reduced system cooling.




3.5.2 Alarm 2112043





CPU fan

Severity Major


Hardware


No






DRAFT


3.5.3 Alarm 2112044



Description Fan 0 has failed.


Fan

Severity Major


Hardware


No





3.5.4 Alarm 2112045





Fan

Severity Major


Hardware


No





3.5.5 Alarm 2112046




DRAFT


Description DC power unavailable for power supply 0.


DC power

Severity Major


Hardware


No

System Impact Reduced power redundancy.


Check the power cable and power input for power supply 0.


3.5.6 Alarm 2112047





DC power

Severity Major


Hardware


No





3.5.7 Alarm 2112048





Fan

Severity Major


DRAFT



Hardware


No





3.5.8 Alarm 2112049





Fan

Severity Major


Hardware


No





3.5.9 Alarm 2112050





Fan

Severity Major


Hardware


No


DRAFT






3.5.10 Alarm 2112051





Fan

Severity Major


Hardware


No





3.5.11 Alarm 2112052



Description Power supply 0 has been inserted.


Power supply

Severity Normal


Hardware


No


Check that this action was initiated and planned internally.



DRAFT


3.5.12 Alarm 2112053



Description Power supply 0 has been removed.


Power supply

Severity Major


Hardware


Yes; by 2112052



Check that this action was initiated and planned internally.Contact Comverse customer support.


3.5.13 Alarm 2112054





Power supply

Severity Normal


Hardware


No




3.5.14 Alarm 2112055





DRAFT



Power supply

Severity Major


Hardware


Yes; by 2112054





3.5.15 Alarm 2112056



Description CPU 0 high temperature exceeded hard shutdown threshold.


CPU temperature

Severity Major


Hardware


No

Threshold 118 °C

System Impact Server down due to high temperature. Downtime in case ofno server redundancy.




3.5.16 Alarm 2112057



Description CPU 0 high temperature exceeded soft shutdown threshold.


CPU temperature

Soft shutdown performs self shutdown through command.


DRAFT


Severity Major


Hardware


No

Threshold 115 °C





3.5.17 Alarm 2112058



Description CPU 0 high temperature warning.


CPU temperature

Severity Minor


Hardware


No

Threshold 110 °C




3.5.18 Alarm 2112059





CPU temperature

Hard Shutdown performs immediate shutdown.

Severity Major


DRAFT



Hardware


No

Threshold 118 °C





3.5.19 Alarm 2112060





CPU temperature


Severity Major


Hardware


No

Threshold 115 °C





3.5.20 Alarm 2112061





CPU temperature

Severity Minor


DRAFT



Hardware


No

Threshold 110 °C




3.5.21 Alarm 2112062



Description Power Supply 0 internal connection failure.


Power supply

Severity Major


Hardware


No



Check the power supply LED. If the problem persists, contactComverse customer support.


3.5.22 Alarm 2112063





Power supply

Severity Major


Hardware


No


DRAFT






3.5.23 Alarm 2112064





Power supply

Severity Major


Hardware


No





3.5.24 Alarm 2112065





Power supply

Severity Major


Hardware


No






DRAFT


3.5.25 Alarm 2112066



Description CPU fan tray 0 has been inserted.


CPU fan tray

Severity Normal


Hardware


No


Verify that this action was planned and initiated by atechnician.


3.5.26 Alarm 2112067



Description CPU fan tray 0 has been removed.


CPU fan tray

Severity Major


Hardware


Yes; by 2112066





3.5.27 Alarm 2112068



Description CPU fan tray 0 has failed.


DRAFT



CPU fan tray

Severity Major


Hardware


No



Check the fan LED status.


3.5.28 Alarm 2112069





CPU fan tray

Severity Normal


Hardware


No




3.5.29 Alarm 2112070





CPU fan tray

Severity Major


Hardware


DRAFT



No





3.5.30 Alarm 2112071





CPU fan tray

Severity Major


Hardware


Yes; by 2112069





3.5.31 Alarm 2112072





CPU fan tray

Severity Normal


Hardware


No





DRAFT


3.5.32 Alarm 2112073





CPU fan tray

Severity Major


Hardware


Yes; by 2112069





3.5.33 Alarm 2112074





CPU fan tray

Severity Major


Hardware


No





3.5.34 Alarm 2112075




DRAFT




CPU fan tray

Severity Major


Hardware


No





3.5.35 Alarm 2112076



Description Input power unavailable for power supply 0.


Input power

Severity Major


Hardware


No





3.5.36 Alarm 2112077





Input power

Severity Major


DRAFT



Hardware


No





3.5.37 Alarm 2112078





Input power

Severity Major


Hardware


No





3.5.38 Alarm 2112079





Input power

Severity Major


Hardware


No


DRAFT






3.5.39 Alarm 2112080





Power supply

Severity Normal


Hardware


No




3.5.40 Alarm 2112081





Power supply

Severity Major


Hardware


No






DRAFT


3.5.41 Alarm 2112082



Description Power supply 0 has failed.


Power supply

Severity Major


Hardware


No



Check the power supply LED’s status. If the problem persists,contact Comverse customer support.


3.5.42 Alarm 2112083



Description Power supply 0 is not properly in place.


Power supply

Severity Major


Hardware


No



Check that power supply 0 is properly inserted.


3.5.43 Alarm 2112084




DRAFT




Power supply

Severity Normal


Hardware


No




3.5.44 Alarm 2112085





Power supply

Severity Major


Hardware


No





3.5.45 Alarm 2112086





Power supply

Severity Major


Hardware


DRAFT



No



Check the power supply LED.


3.5.46 Alarm 2112087





Power supply

Severity Major


Hardware


No





3.5.47 Alarm 2112088





Power supply

Severity Normal


Hardware


No





DRAFT


3.5.48 Alarm 2112089





Power supply

Severity Major


Hardware


No





3.5.49 Alarm 2112090





Power supply

Severity Major


Hardware


No





3.5.50 Alarm 2112091




DRAFT




Power supply

Severity Major


Hardware


No





3.5.51 Alarm 2112092





Power supply

Severity Normal


Hardware


No




3.5.52 Alarm 2112093





Power supply

Severity Major


Hardware


DRAFT



No





3.5.53 Alarm 2112094





Power supply

Severity Major


Hardware


No





3.5.54 Alarm 2112095





Power supply

Severity Major


Hardware


No





DRAFT



3.5.55 Alarm 2112096





CPU temperature


Severity Major


Hardware


No

Threshold 118 °C





3.5.56 Alarm 2112097





CPU temperature


Severity Major


Hardware


No

Threshold 110 °C





DRAFT



3.5.57 Alarm 2112098





CPU temperature

Severity Minor


Hardware


No

Threshold 102 °C




3.5.58 Alarm 2112099





CPU temperature


Severity Major


Hardware


No

Threshold 118 °C






DRAFT


3.5.59 Alarm 2112100





CPU temperature


Severity Major


Hardware


No

Threshold 110 °C





3.5.60 Alarm 2112101





CPU temperature

Severity Minor


Hardware


No

Threshold 102 °C




3.5.61 Alarm 2112102


DRAFT






CPU temperature

Severity Major


Hardware


No





3.5.62 Alarm 2112103





CPU temperature

Severity Major


Hardware


No





3.5.63 Alarm 2112104





DRAFT



CPU temperature

Severity Minor


Hardware


No




3.5.64 Alarm 2112105





CPU temperature

Severity Major


Hardware


No

System Impact Server down due to high temperature. Down time in case ofno server redundancy.




3.5.65 Alarm 2112106





CPU temperature

Severity Major


Hardware


DRAFT



No





3.5.66 Alarm 2112107





CPU temperature

Severity Minor


Hardware


No





DRAFT

3: Hardware Agent Alarms Q-Logic Alarms

3.6 Q-Logic AlarmsSearch for the alarm you need by its Specific Problem (Alarm ID).

3.6.1 Alarm 2990000


Managed Object Q-Logic

Description An unknown trap <$o> arrived from the Q-Logic system.

Severity Unknown


No


3.6.2 Alarm 2990101



Description Q-Logic - Switch status has changed to unknown withunknown state.

Severity Major


No


3.6.3 Alarm 2990102



Description Q-Logic - Switch status has changed to unknown with onlinestate.

Severity Major


No


3.6.4 Alarm 2990103


DRAFT




Description Q-Logic - Switch status has changed to unknown with offlinestate.

Severity Major


No


3.6.5 Alarm 2990104



Description Q-Logic - Switch status has changed to unused with unknownstate.

Severity Normal


No


3.6.6 Alarm 2990105



Description Q-Logic - Switch status has changed to unused with onlinestate.

Severity Normal


No


3.6.7 Alarm 2990106



Description Q-Logic - Switch status has changed to unused with offlinestate.


DRAFT


Severity Normal


No


3.6.8 Alarm 2990107



Description Q-Logic - Switch status has changed to ok with unknown state.

Severity Normal


No


3.6.9 Alarm 2990108



Description Q-Logic - Switch status has changed to ok with online state.

Severity Normal


No


3.6.10 Alarm 2990109



Description Q-Logic - Switch status has changed to ok with offline state.

Severity Normal


No



DRAFT


3.6.11 Alarm 2990110



Description Q-Logic - Switch status has changed to warning with unknownstate.

Severity Warning


No


3.6.12 Alarm 2990111



Description Q-Logic - Switch status has changed to warning with onlinestate.

Severity Warning


No


3.6.13 Alarm 2990112



Description Q-Logic - Switch status has changed to warning with offlinestate.

Severity Warning


No


3.6.14 Alarm 2990113


DRAFT




Description Q-Logic - Switch status has changed to failure with unknownstate.

Severity Major


No


3.6.15 Alarm 2990114



Description Q-Logic - Switch status has changed to failure with onlinestate.

Severity Major


No


3.6.16 Alarm 2990115



Description Q-Logic - Switch status has changed to failure with offlinestate.

Severity Major


No


3.6.17 Alarm 2990301



Description Q-Logic - Connectivity unit <connUnitId> has been deletedfrom this agent.


DRAFT


Severity Warning


No


3.6.18 Alarm 2990401



Description Q-Logic - An event of type unknown occurred on switch<Chassis>, I/O blade <Blade>, port <Port>, module <Module>,address <Addr>. Event description: <Descr>.

Severity Normal


No


3.6.19 Alarm 2990402



Description Q-Logic - An event of type other occurred on switch<Chassis>, I/O blade <Blade>, port <Port>, module<Module>, address <Addr>. Event description: <Descr>.

Severity Normal


No


3.6.20 Alarm 2990403



Description Q-Logic - An event of type status occurred on switch<Chassis>, I/O blade <Blade>, port <Port>, module<Module>, address <Addr>. Event description: <Descr>.


DRAFT


Severity Normal


No


3.6.21 Alarm 2990404



Description Q-Logic - An event of type configuration occurred onswitch <Chassis>, I/O blade <Blade>, port <Port>, module<Module>, address <Addr>. Event description: <Descr>.

Severity Normal


No


3.6.22 Alarm 2990405



Description Q-Logic - An event of type topology occurred on switch<Chassis>, I/O blade <Blade>, port <Port>, module <Module>,address <Addr>. Event description: <Descr>.

Severity Normal


No


3.6.23 Alarm 2990501



Description Q-Logic - Sensor status has changed to unknown.

Severity Major


No


DRAFT



3.6.24 Alarm 2990502



Description Q-Logic - Sensor status has changed to other.

Severity Major


No


3.6.25 Alarm 2990503



Description Q-Logic - Sensor status has changed to ok.

Severity Normal


No


3.6.26 Alarm 2990504



Description Q-Logic - Sensor status has changed to warning.

Severity Warning


No


3.6.27 Alarm 2990505




DRAFT


Description Q-Logic - Sensor status has changed to failed.

Severity Major


No


3.6.28 Alarm 2990601 (Q-Logic - Port status has changesto unknown with bypassed state.)Specific Problem 2990601


Description Q-Logic - Port status has changes to unknown with bypassedstate.

Severity Major


No


3.6.29 Alarm 2990601 (Q-Logic - Port status has changesto unknown with diagnostics state.)Specific Problem 2990601


Description Q-Logic - Port status has changes to unknown with diagnosticsstate.

Severity Major


No


3.6.30 Alarm 2990601 (Q-Logic - Port status has changesto unknown with offline state.)Specific Problem 2990601


Description Q-Logic - Port status has changes to unknown with offlinestate.

Severity Major


No


DRAFT



3.6.31 Alarm 2990601 (Q-Logic - Port status has changesto unknown with online state.)Specific Problem 2990601


Description Q-Logic - Port status has changes to unknown with onlinestate.

Severity Major


No


3.6.32 Alarm 2990601 (Q-Logic - Port status has changesto unknown with unknown state.)Specific Problem 2990601


Description Q-Logic - Port status has changes to unknown with unknownstate.

Severity Major


No


3.6.33 Alarm 2990602 (Q-Logic - Port status has changesto unused with bypassed state.)Specific Problem 2990602


Description Q-Logic - Port status has changes to unused with bypassedstate.

Severity Normal


No



DRAFT


3.6.34 Alarm 2990602 (Q-Logic - Port status has changesto unused with diagnostics state.)Specific Problem 2990602


Description Q-Logic - Port status has changes to unused with diagnosticsstate.

Severity Normal


No


3.6.35 Alarm 2990602 (Q-Logic - Port status has changesto unused with offline state.)Specific Problem 2990602


Description Q-Logic - Port status has changes to unused with offline state.

Severity Major


No


3.6.36 Alarm 2990602 (Q-Logic - Port status has changesto unused with online state.)Specific Problem 2990602


Description Q-Logic - Port status has changes to unused with online state.

Severity Normal


No


3.6.37 Alarm 2990602 (Q-Logic - Port status has changesto unused with unknown state.)Specific Problem 2990602



DRAFT


Description Q-Logic - Port status has changes to unused with unknownstate.

Severity Major


No


3.6.38 Alarm 2990603 (Q-Logic - Port status has changesto ready with bypassed state.)Specific Problem 2990603


Description Q-Logic - Port status has changes to ready with bypassedstate.

Severity Normal


No


3.6.39 Alarm 2990603 (Q-Logic - Port status has changesto ready with diagnostics state.)Specific Problem 2990603


Description Q-Logic - Port status has changes to ready with diagnosticsstate.

Severity Normal


No


3.6.40 Alarm 2990603 (Q-Logic - Port status has changesto ready with offline state.)Specific Problem 2990603


Description Q-Logic - Port status has changes to ready with offline state.

Severity Major


No


DRAFT



3.6.41 Alarm 2990603 (Q-Logic - Port status has changesto ready with online state.)Specific Problem 2990603


Description Q-Logic - Port status has changes to ready with online state.

Severity Normal


No


3.6.42 Alarm 2990603 (Q-Logic - Port status has changesto ready with unknown state.)Specific Problem 2990603


Description Q-Logic - Port status has changes to ready with unknownstate.

Severity Major


No


3.6.43 Alarm 2990604 (Q-Logic - Port status has changesto warning with bypassed state.)Specific Problem 2990604


Description Q-Logic - Port status has changes to warning with bypassedstate.

Severity Warning


No



DRAFT


3.6.44 Alarm 2990604 (Q-Logic - Port status has changesto warning with diagnostics state.)Specific Problem 2990604


Description Q-Logic - Port status has changes to warning with diagnosticsstate.

Severity Warning


No


3.6.45 Alarm 2990604 (Q-Logic - Port status has changesto warning with offline state.)Specific Problem 2990604


Description Q-Logic - Port status has changes to warning with offline state.

Severity Major


No


3.6.46 Alarm 2990604 (Q-Logic - Port status has changesto warning with online state.)Specific Problem 2990604


Description Q-Logic - Port status has changes to warning with online state.

Severity Warning


No


3.6.47 Alarm 2990604 (Q-Logic - Port status has changesto warning with unknown state.)Specific Problem 2990604



DRAFT


Description Q-Logic - Port status has changes to warning with unknownstate.

Severity Major


No


3.6.48 Alarm 2990605 (Q-Logic - Port status has changesto failure with bypassed state.)Specific Problem 2990605


Description Q-Logic - Port status has changes to failure with bypassedstate.

Severity Major


No


3.6.49 Alarm 2990605 (Q-Logic - Port status has changesto failure with diagnostics state.)Specific Problem 2990605


Description Q-Logic - Port status has changes to failure with diagnosticsstate.

Severity Major


No


3.6.50 Alarm 2990605 (Q-Logic - Port status has changesto failure with offline state.)Specific Problem 2990605


Description Q-Logic - Port status has changes to failure with offline state.

Severity Major


No


DRAFT



3.6.51 Alarm 2990605 (Q-Logic - Port status has changesto failure with online state.)Specific Problem 2990605


Description Q-Logic - Port status has changes to failure with online state.

Severity Major


No


3.6.52 Alarm 2990605 (Q-Logic - Port status has changesto failure with unknown state.)Specific Problem 2990605


Description Q-Logic - Port status has changes to failure with unknownstate.

Severity Major


No


3.6.53 Alarm 2990606 (Q-Logic - Port status has changesto not participating with bypassed state.)Specific Problem 2990606


Description Q-Logic - Port status has changes to not participating withbypassed state.

Severity Normal


No



DRAFT


3.6.54 Alarm 2990606 (Q-Logic - Port status has changesto not participating with diagnostics state.)Specific Problem 2990606


Description Q-Logic - Port status has changes to not participating withdiagnostics state.

Severity Normal


No


3.6.55 Alarm 2990606 (Q-Logic - Port status has changesto not participating with offline state.)Specific Problem 2990606


Description Q-Logic - Port status has changes to not participating withoffline state.

Severity Major


No


3.6.56 Alarm 2990606 (Q-Logic - Port status has changesto not participating with online state.)Specific Problem 2990606


Description Q-Logic - Port status has changes to not participating withonline state.

Severity Normal


No


3.6.57 Alarm 2990606 (Q-Logic - Port status has changesto not participating with unknown state.)Specific Problem 2990606



DRAFT


Description Q-Logic - Port status has changes to not participating withunknown state.

Severity Major


No


3.6.58 Alarm 2990607 (Q-Logic - Port status has changesto initializing with bypassed state.)Specific Problem 2990607


Description Q-Logic - Port status has changes to initializing with bypassedstate.

Severity Normal


No


3.6.59 Alarm 2990607 (Q-Logic - Port status has changesto initializing with diagnostics state.)Specific Problem 2990607


Description Q-Logic - Port status has changes to initializing withdiagnostics state.

Severity Normal


No


3.6.60 Alarm 2990607 (Q-Logic - Port status has changesto initializing with offline state.)Specific Problem 2990607


Description Q-Logic - Port status has changes to initializing with offlinestate.

Severity Major


No


DRAFT



3.6.61 Alarm 2990607 (Q-Logic - Port status has changesto initializing with online state.)Specific Problem 2990607


Description Q-Logic - Port status has changes to initializing with onlinestate.

Severity Normal


No


3.6.62 Alarm 2990607 (Q-Logic - Port status has changesto initializing with unknown state.)Specific Problem 2990607


Description Q-Logic - Port status has changes to initializing with unknownstate.

Severity Major


No


3.6.63 Alarm 2990608 (Q-Logic - Port status has changesto bypass with bypassed state.)Specific Problem 2990608


Description Q-Logic - Port status has changes to bypass with bypassedstate.

Severity Normal


No



DRAFT


3.6.64 Alarm 2990608 (Q-Logic - Port status has changesto bypass with diagnostics state.)Specific Problem 2990608


Description Q-Logic - Port status has changes to bypass with diagnosticsstate.

Severity Normal


No


3.6.65 Alarm 2990608 (Q-Logic - Port status has changesto bypass with offline state.)Specific Problem 2990608


Description Q-Logic - Port status has changes to bypass with offline state.

Severity Major


No


3.6.66 Alarm 2990608 (Q-Logic - Port status has changesto bypass with online state.)Specific Problem 2990608


Description Q-Logic - Port status has changes to bypass with online state.

Severity Normal


No


3.6.67 Alarm 2990608 (Q-Logic - Port status has changesto bypass with unknown state.)Specific Problem 2990608



DRAFT


Description Q-Logic - Port status has changes to bypass with unknownstate.

Severity Major


No


3.6.68 Alarm 2990609 (Q-Logic - Port status has changestools with bypassed state.)



Description Q-Logic - Port status has changes tools with bypassed state.

Severity Normal


No


3.6.69 Alarm 2990609 (Q-Logic - Port status has changestools with diagnostics state.)Specific Problem 2990609


Description Q-Logic - Port status has changes tools with diagnostics state.

Severity Normal


No


3.6.70 Alarm 2990609 (Q-Logic - Port status has changestools with offline state.)



Description Q-Logic - Port status has changes tools with offline state.


DRAFT


Severity Major


No


3.6.71 Alarm 2990609 (Q-Logic - Port status has changestools with online state.)



Description Q-Logic - Port status has changes tools with online state.

Severity Normal


No


3.6.72 Alarm 2990609 (Q-Logic - Port status has changestools with unknown state.)



Description Q-Logic - Port status has changes tools with unknown state.

Severity Major


No


3.6.73 Alarm 2990610 (Q-Logic - Port status has changesto other with bypassed state.)Specific Problem 2990610


Description Q-Logic - Port status has changes to other with bypassedstate.

Severity Normal


No


DRAFT



3.6.74 Alarm 2990610 (Q-Logic - Port status has changesto other with diagnostics state.)Specific Problem 2990610


Description Q-Logic - Port status has changes to other with diagnosticsstate.

Severity Normal


No


3.6.75 Alarm 2990610 (Q-Logic - Port status has changesto other with offline state.)Specific Problem 2990610


Description Q-Logic - Port status has changes to other with offline state.

Severity Major


No


3.6.76 Alarm 2990610 (Q-Logic - Port status has changesto other with online state.)Specific Problem 2990610


Description Q-Logic - Port status has changes to other with online state.

Severity Normal


No



DRAFT


3.6.77 Alarm 2990610 (Q-Logic - Port status has changesto other with unknown state.)Specific Problem 2990610


Description Q-Logic - Port status has changes to other with unknown state.

Severity Major


No


3.6.78 Alarm 2990701



Description Q-Logic - Cold start.

Severity Warning


No


3.6.79 Alarm 2990801



Description Q-Logic - authentication failure.

Severity Warning


No


3.6.80 Alarm 2991001



Description Q-Logic - QxPort link down. Current QxPort operational statusis offline. Desired status of the QxPort is online.


DRAFT


Severity Major


No


3.6.81 Alarm 2991002



Description Q-Logic - QxPort link down. Current QxPort operational statusis offline. Desired status of the QxPort is offline.

Severity Normal


No


3.6.82 Alarm 2991003



Description Q-Logic - QxPort link down. Current QxPort operational statusis offline. Desired status of the QxPort is testing.

Severity Major


No


3.6.83 Alarm 2991004



Description Q-Logic - QxPort link down. Current QxPort operational statusis testing. Desired status of the QxPort is online.

Severity Warning


No



DRAFT


3.6.84 Alarm 2991005



Description Q-Logic - QxPort link down. Current QxPort operational statusis testing. Desired status of the QxPort is offline.

Severity Warning


No


3.6.85 Alarm 2991006



Description Q-Logic - QxPort link down. Current QxPort operational statusis testing. Desired status of the QxPort is testing.

Severity Normal


No


3.6.86 Alarm 2991007



Description Q-Logic - QxPort link down. Current QxPort operational statusis link failure. Desired status of the QxPort is online.

Severity Major


No


3.6.87 Alarm 2991008


DRAFT




Description Q-Logic - QxPort link down. Current QxPort operational statusis link failure. Desired status of the QxPort is offline.

Severity Major


No


3.6.88 Alarm 2991009



Description Q-Logic - QxPort link down. Current QxPort operational statusis link failure. Desired status of the QxPort is testing.

Severity Major


No


3.6.89 Alarm 2991101



Description Q-Logic - QxPort link up. Current QxPort operational status isonline. Desired status of the QxPort is online.

Severity Normal


No


3.6.90 Alarm 2991102



Description Q-Logic - QxPort link up. Current QxPort operational status isonline. Desired status of the QxPort is offline.


DRAFT


Severity Normal


No


3.6.91 Alarm 2991103



Description Q-Logic - QxPort link up. Current QxPort operational status isonline. Desired status of the QxPort is testing.

Severity Normal


No



DRAFT

OS Agent Alarms 4■ OS Agent Alarm Overview, Page 256

■ CCS_OS Alarms, Page 257

■ SUN OS Alarms (OnGuard Agent), Page 259

■ Health Probe Alarms, Page 276

DRAFT

4: OS Agent Alarms OS Agent Alarm Overview

4.1 OS Agent Alarm OverviewOS Agent alarms monitor the operating systems and generate an alarm if thesystem is not functioning properly.

The following OS Agent alarms are monitored:





DRAFT

4: OS Agent Alarms CCS_OS Alarms

4.2 CCS_OS AlarmsSearch for the alarm you need by its Specific Problem (Alarm ID).

4.2.1 Alarm 4087005


Managed Object CCS_OS

Description SIGH process failed.

Severity Major


Application


Yes; by 4087005

Threshold 0 instances

System Impact Switch over will occur.


Contact Comverse customer support for problem analysis.


4.2.2 Alarm 4087006



Description LAN process failed.

Severity Major


Application


Yes; by 4087006

Threshold 0 instances

System Impact Switch over will occur.




4.2.3 Alarm 4087501


DRAFT

4: OS Agent Alarms CCS_OS Alarms



Description SIGH process overloaded.

Severity Major


Application


Yes; by 4087501

Threshold 1900 messages in queue

System Impact Possible messages loss.




4.2.4 Alarm 4087504



Description L3_MTP process overloaded.

Severity Major


Application


Yes; by 4087504

Threshold 1900 messages in queue

System Impact Possible messages loss.





DRAFT

4: OS Agent Alarms SUN OS Alarms (OnGuard Agent)

4.3 SUN OS Alarms (OnGuard Agent)Search for the alarm you need by its Specific Problem (Alarm ID).

4.3.1 Alarm 2112001



Description The CPU usage is <CPU value>%.


<CPU value>: Percentage of the CPU in use

Severity Normal


Operating System


No

Threshold 0–69%


4.3.2 Alarm 2112002



Description The CPU usage is <CPU value>%. There is a problem withthe last <events number> events.


■ <CPU value>: Percentage of the CPU in use■ <events number>: Number of consequent events with

this problem

Severity Warning


Operating System


Yes; by 2112001

Threshold 70–89%

System Impact Lower system performance.


Kill the process which consumes the CPU provided you donot harm your system.

Identify why the CPU consumption is high.



DRAFT


4.3.3 Alarm 2112003






this problem

Severity Major


Operating System


Yes; by 2112001

Threshold 90–100%






4.3.4 Alarm 2112004



Description A CPU usage event timed out.

Severity Warning


Operating System


Yes; by 2112001

System Impact CPU usage is not checked.




4.3.5 Alarm 2112005


DRAFT




Description A CPU usage event failed.

Severity Warning


Operating System


Yes; by 2112001





4.3.6 Alarm 2112006



Description <usage value>% of the <file system> file system is in use(<used MB> of <total MB> MB).


■ <usage value>: Percentage used■ <file system>: File system name■ <used MB>: Number of MB in the file system that are

in use■ <total MB>: Total number of MB in the file system

Severity Normal


Operating System


No

Threshold 0–89%


4.3.7 Alarm 2112007





DRAFT





Severity Warning


Operating System


Yes; by 2112006

Threshold 90–94%

System Impact Some applications may fail.


Delete unnecessary files from the file system. If noneavailable, the file system capacity should be enlarged.


4.3.8 Alarm 2112008







Severity Major


Operating System


Yes; by 2112006

Threshold 95–100%






DRAFT


4.3.9 Alarm 2112009



Description A file system free space event timed out.

Severity Warning


Operating System


Yes; by 2112006

System Impact File system free space is not checked.




4.3.10 Alarm 2112010



Description A file system free space event failed.

Severity Warning


Operating System


Yes; by 2112006





4.3.11 Alarm 2112011



Description The load average is <load average value>.


<load average value>: Load average value.


DRAFT


Severity Normal


Operating System


No

Threshold 0–2


4.3.12 Alarm 2112012



Description The load average is <load average value>. There is aproblem with the last <events number> events.


■ <load average value>: Load average value■ <events number>: Number of consequent events with

this problem

High average number of jobs in the run queue over the last15 minutes per processor.

Severity Warning


Operating System


Yes; by 2112011

Threshold 2–3



Reduce the number of heavy applications on the unit ifpossible.


4.3.13 Alarm 2112013





DRAFT




this problem

Very high average number of jobs in the run queue over thelast 15 minutes per processor.

Severity Major


Operating System


Yes; by 2112011

Threshold 4+



Reduce the number of heavy applications on the machine ifpossible.


4.3.14 Alarm 2112014



Description A load average event timed out.

Severity Warning


Operating System


Yes; by 2112011

System Impact Load average is not checked.




4.3.15 Alarm 2112015



Description A load average event failed.

Severity Warning


DRAFT



Operating System


Yes; by 2112011





4.3.16 Alarm 2112016



Description The swap usage is <swap value>%.


<swap value>: Percentage of swap area in use.

Severity Normal


Operating System


No

Threshold 0–69%


4.3.17 Alarm 2112017



Description The swap usage is <swap value>%. There is a problem withthe last <events number> events.


■ <swap value>: Percentage of swap area in use■ <events number>: Number of consequent events with

this problem

Severity Warning


Operating System


Yes; by 2112016

Threshold 70–89%


DRAFT




Enlarge swap area size on this machine if possible.


4.3.18 Alarm 2112018






this problem

Severity Major


Operating System


Yes; by 2112016

Threshold 90–100%





4.3.19 Alarm 2112019



Description A swap usage event timed out.

Severity Warning


Operating System


Yes; by 2112016

System Impact Swap usage is not checked.




DRAFT



4.3.20 Alarm 2112020



Description A swap usage event failed.

Severity Warning


Operating System


Yes; by 2112016





4.3.21 Alarm 2112021



Description The I/O wait is <I/O waits value>%.


<I/O waits value>: Percentage of I/O waits out of the totalCPU time.

Severity Normal


Operating System


No

Threshold 0–9


4.3.22 Alarm 2112022



Description The I/O wait is <I/O waits value>%. There is a problem withthe last <events number> events.


DRAFT



■ <I/O waits value>: Percentage of I/O waits out of thetotal CPU time

■ <events number>: Number of consequent events withthis problem

Severity Warning


Operating System


Yes; by 2112021

Threshold 10-29



If possible, stop using the problematic application, or elseCPUs may need to be added to this machine.


4.3.23 Alarm 2112023







Severity Major


Operating System


Yes; by 2112021

Threshold 30+





4.3.24 Alarm 2112024


DRAFT




Description An I/O wait event timed out.

Severity Warning


Operating System


Yes; by 2112021

System Impact I/O wait is not checked.




4.3.25 Alarm 2112025



Description An I/O wait event failed.

Severity Warning


Operating System


Yes; by 2112021





4.3.26 Alarm 2112026



Description The network response time for <server name> is normal.


<server name>: Server name, IP, or URL

Severity Normal


Operating System


DRAFT



No

Threshold 0–19 ms


4.3.27 Alarm 2112027



Description High network response time. The network response time for<server name> is <response time> ms.


■ <server name>: Server name, IP, or URL■ <response time>: Average response time in ms

Severity Warning


Operating System


Yes; by 2112026

Threshold 20+ ms

System Impact Poor network connection to the remote server which maycause slow data transfer.


System administrator to check the network and remote server.


4.3.28 Alarm 2112028



Description <server name> is not responding to a ping request (<lostpackets> out of <sent packets> packets lost).


■ <server name>: Server name, IP, or URL■ <lost packets>: Number of lost packets■ <sent packets>: Number of sent packets

Severity Critical


Operating System


Yes; by 2112026


DRAFT


Threshold Failed ping

System Impact Remote server is not accessible.




4.3.29 Alarm 2112029



Description Ping error for <server name> (unknown host <server name>).


<server name>: Server name, IP, or URL.

Severity Warning


Operating System


Yes; by 2112026




Ask the system administrator about this host name and incase of need, change it in OnGuard.


4.3.30 Alarm 2112030



Description Network availability event timed out.

Severity Warning


Operating System


Yes; by 2112026

System Impact Network availability is not checked.





DRAFT


4.3.31 Alarm 2112031



Description Pinging <server name> failed.



Severity Warning


Operating System


Yes; by 2112026

System Impact This server is not checked for network availability.




4.3.32 Alarm 2112032



Description <memory used>% of the physical memory is in use (<usedMB> of <total MB> MB).


■ <memory used>: Percentage of memory in use■ <used MB>: Number of MB of memory in use■ <total MB>: Total MB of memory

Severity Normal


Operating System


No

Threshold 0–84%


4.3.33 Alarm 2112033


DRAFT







Severity Warning


Operating System


Yes; by 2112032

Threshold 85–94%



Do one of the following:■ If the server performance is low, check which

application is consuming a lot of memory and stop usingit if possible.

■ If the server performance is not low, add memory tothe machine.


4.3.34 Alarm 2112034






Severity Major


Operating System


Yes; by 2112032

Threshold 95–100%


DRAFT


System Impact Lower system performance






4.3.35 Alarm 2112035



Description A physical memory free event timed out.

Severity Warning


Operating System


Yes; by 2112032

System Impact Physical memory free space is not checked.




4.3.36 Alarm 2112036



Description A physical memory free event failed.

Severity Warning


Operating System


Yes; by 2112032






DRAFT

4: OS Agent Alarms Health Probe Alarms

4.4 Health Probe AlarmsSearch for the alarm you need by its Specific Problem (Alarm ID).

4.4.1 Alarm 2980001


Managed Object SMSCHP

Description <eventType> utilization of CPU id <cpuID> has reached<CPUload>%.


CPU

Severity Critical

Major

Minor

Normal


Application


Yes; by 2980001

System Impact Possible impacts:■ If CPU, System performance might be affected.■ If CPU, No impact.


If CPU, Contact Comverse customer support.


4.4.2 Alarm 2980002



Description <eventType> utilization has reached <usedSize> out of<totalSize>.


Physical memory

Severity Critical

Major

Minor

Normal


DRAFT



Application


Yes; by 2980002

System Impact Possible impacts:■ If Physical memory, System performance might be

affected.■ If Physical memory, No impact.


If Physical memory, Contact Comverse customer support.


4.4.3 Alarm 2980003



Description <eventType> utilization has reached <usedSize> out of<totalSize>.


Swap memory

Severity Critical

Major

Minor

Normal


Application


Yes; by 2980003

System Impact Possible impacts:■ If Swap memory, System performance might be affected.■ If Swap memory, No impact.


If Swap memory, Contact Comverse customer support.


4.4.4 Alarm 2980004




DRAFT


Description <eventType> utilization of <FSname> has reached<usedSize> out of <totalSize>.


File system

Severity Critical

Major

Minor

Normal


Application


Yes; by 2980004

System Impact Possible impacts:■ If File system, System performance might be affected.■ If File system, No impact.


If File system, Contact Comverse customer support.



DRAFT

Cluster Agent Alarms 5■ Cluster Agent Alarms Overview, Page 280

■ SUN Cluster HA Alarms (OnGuard Agent), Page 281

■ Veritas 3.5 Cluster Alarms, Page 286

DRAFT

5: Cluster Agent Alarms Cluster Agent Alarms Overview

5.1 Cluster Agent Alarms OverviewCluster Agent alarms monitor the cluster units and generate an alarm if the unit isnot functioning properly.

The following Cluster Agent alarms are monitored:





DRAFT

5: Cluster Agent Alarms SUN Cluster HA Alarms (OnGuard Agent)

5.2 SUN Cluster HA Alarms (OnGuard Agent)Search for the alarm you need by its Specific Problem (Alarm ID).

5.2.1 Alarm 2113042



Description The <ResourceGroupName> service on the <NodeName>host was restarted.


■ <ResourceGroupName>: Service name■ <NodeName>: Host name

Severity Normal


High Availability


No


5.2.2 Alarm 2113043



Description The <ResourceGroupName> service on the <NodeName>host cannot start.



Severity Major


High Availability


Yes; by 2113042

System Impact Depends on the resource; there may be downtime.




5.2.3 Alarm 2113044


DRAFT







Severity Normal


High Availability


No


5.2.4 Alarm 2113045



Description The <ResourceGroupName> service on the <NodeName>host is offline.



Severity Major


High Availability


Yes; by 2113044



Check if the service is really down, and that it is not a falsealarm. If the service is not online on any node and notrestarted automatically, manually restart the service.


5.2.5 Alarm 2113046





DRAFT




Severity Normal


High Availability


No


5.2.6 Alarm 2113047



Description The <ResourceGroupName> service on the <NodeName>host failed.



Severity Major


High Availability


Yes; by 2113046



If the alarm is not cleared automatically, restart the resource.


5.2.7 Alarm 2113048



Description The <NodeName> host is up.


<NodeName>: Host name

Severity Normal


DRAFT



High Availability


No


5.2.8 Alarm 2113049



Description The <NodeName> host is down.



Severity Critical


High Availability


Yes; by 2113048



Check that the node is alive. Check that the heartbeat cablesare properly connected.


5.2.9 Alarm 2113050



Description The <ResourceGroupName> service cannot fail over.



The service is failing on both nodes and cannot be restarted.

Severity Critical


High Availability


Yes; by 2113044





DRAFT


5.2.10 Alarm 2113051



Description The <ResourceGroupName> service on the <NodeName>host cannot start.



The service is failing on both nodes and cannot be restarted.

Severity Critical


High Availability


Yes; by 2113044






DRAFT

5: Cluster Agent Alarms Veritas 3.5 Cluster Alarms

5.3 Veritas 3.5 Cluster AlarmsSearch for the alarm you need by its Specific Problem (Alarm ID).

5.3.1 Alarm 2121011


Managed Object Veritas

Description Resource <ResourceName> of type: <ResourceType> on<systemName>: Resource State Unknown


Resource vcs_SMSC of type: NotifierMngr on lsi1a: ResourceState Unknown

Severity Minor


High Availability


No

System Impact System is not monitored properly; downtime to service ispossible.


Verify that all resources (persistent and non-persistent) areonline. If not, contact Comverse customer support.


5.3.2 Alarm 2121012



Description Resource <ResourceName> of type: <ResourceType> on<systemName>: Resource Monitor Timeout


Resource vcs_SMSC of type: NotifierMngr on lsi1a: ResourceMonitor Timeout

Severity Minor


High Availability


No



Manually verify the state of the resource.


DRAFT



5.3.3 Alarm 2121013



Description Resource <ResourceName> of type: <ResourceType> on<systemName>: Resource Not Going Offline


Resource vcs_SMSC of type: NotifierMngr on lsi1a: ResourceNot Going Offline

Severity Minor


High Availability


No



Check the logs for the cause of the resource not going offline.


5.3.4 Alarm 2121014



Description Resource <ResourceName> of type: <ResourceType> on<systemName>: Resource Restarted By Agent


Resource vcs_SMSC of type: NotifierMngr on lsi1a: ResourceRestarted By Agent

Severity Warning


High Availability


No



Check the logs for the cause of the resource restart.



DRAFT


5.3.5 Alarm 2121015



Description Resource <ResourceName> of type: <ResourceType> on<systemName>: Resource Went Online By Itself


Resource vcs_SMSC of type: NotifierMngr on lsi1a: ResourceWent Online By Itself

Severity Warning


High Availability


No



5.3.6 Alarm 2121016



Description Resource <ResourceName> of type: <ResourceType> on<systemName>: Resource Faulted


Resource vcs_SMSC of type: NotifierMngr on lsi1a: ResourceFaulted

Severity Major


High Availability


Yes; by 2121015

System Impact Depending on the group may cause downtime.


Check the /var/VRTSvcs/log/engina_A.log file to check thereason the resource faulted. Try to clear the fault and returnthe resource to online.


5.3.7 Alarm 2121021


DRAFT




Description Service Group <ServiceGroupName> of type:<ServiceGroupType> on <systemName>: Service GroupOnline


Service Group Server of type: Parallel on lsi1a: Service GroupOnline

Severity Normal


High Availability


No


5.3.8 Alarm 2121022



Description Service Group <ServiceGroupName> of type:<ServiceGroupType> on <systemName>: Service GroupOffline


Service Group Server of type: Parallel on lsi1a: Service GroupOffline

Severity Warning


High Availability


Yes; by 2121021



5.3.9 Alarm 2121023



Description Service Group <ServiceGroupName> of type:<ServiceGroupType> on <systemName>: Service GroupAutodisabled


DRAFT



Service Group Server of type: Parallel on lsi1a: Service GroupAutodisabled

Severity Warning


High Availability


No


If all systems are online and service group is still in theAutodisabled state, run the command:

hagrp -autoenable <group> -sys <system>.


5.3.10 Alarm 2121024



Description Service Group <ServiceGroupName> of type:<ServiceGroupType> on <systemName>: Service group hasfaulted


Service Group Server of type: Parallel on lsi1a: Service grouphas faulted

Severity Critical


High Availability


Yes; by 2121021



Clear the fault (via command line or GUI) then try to turn theservice group online.


5.3.11 Alarm 2121025



Description Service Group <ServiceGroupName> of type:<ServiceGroupType> on <systemName>: Service GroupFaulted Nowhere To Failover


DRAFT



Service Group Server of type: Parallel on lsi1a: Service GroupFaulted Nowhere To Failover

Severity Critical


High Availability


Yes; by 2121021

System Impact Probable downtime.




5.3.12 Alarm 2121026



Description Service Group <ServiceGroupName> of type:<ServiceGroupType> on <systemName>: Service GroupRestarting


Service Group Server of type: Parallel on lsi1a: Service GroupRestarting

Severity Warning


High Availability


No


5.3.13 Alarm 2121027



Description Service Group <ServiceGroupName> of type:<ServiceGroupType> on <systemName>: Service GroupBeing Switched


Service Group Server of type: Parallel on lsi1a: Service GroupBeing Switched

Severity Warning


High Availability


DRAFT



No

System Impact Depending on the service, a short downtime may occur.


Follow up on the system and ensure the service group and allresources turn to an online state.


5.3.14 Alarm 2121028



Description Service Group <ServiceGroupName> of type:<ServiceGroupType> on <systemName>: Service GroupConcurrency Violation


Service Group Server of type: Parallel on lsi1a: Service GroupConcurrency Violation

Severity Critical


High Availability


No




5.3.15 Alarm 2121029



Description Service Group <ServiceGroupName> of type:<ServiceGroupType> on <systemName>: Service GroupRestarting In Response


Service Group Server of type: Parallel on lsi1a: Service GroupRestarting In Response

Severity Warning


High Availability


DRAFT



No


Follow up on the system and ensure the service group and allresources turn to an online state.


5.3.16 Alarm 2121031



Description System <SystemName> of type: m: sun4u, sys: SunOS, r: 5.8on <systemName>: System Up On The First Node


System ins3b of type: m: sun4u, sys: SunOS, r: 5.8 on ins3b:System Up On The First Node

Severity Warning


High Availability


No


5.3.17 Alarm 2121032



Description System <SystemName> of type: m: sun4u, sys: SunOS, r: 5.8on <systemName>: System Restarting By HASHADOW


System ins3b of type: m: sun4u, sys: SunOS, r: 5.8 on ins3b:System Restarting By HASHADOW

Severity Minor


High Availability


No


5.3.18 Alarm 2121033


DRAFT




Description System <SystemName> of type: m: sun4u, sys: SunOS, r: 5.8on <systemName>: System In Jeopardy


System ins3b of type: m: sun4u, sys: SunOS, r: 5.8 on ins3b:System In Jeopardy

Severity Major


High Availability


No

System Impact No immediate impact, but High Availability level is degraded,and next fault will lead to downtime.


Ensure node heartbeat connections are connected. Ifproblems continue, contact Comverse customer support.


5.3.19 Alarm 2121034



Description System <SystemName> of type: m: sun4u, sys: SunOS, r: 5.8on <systemName>: System Faulted


System ins3b of type: m: sun4u, sys: SunOS, r: 5.8 on ins3b:System Faulted

Severity Minor


High Availability


No

System Impact No immediate impact, but High Availability level is degraded,and the next fault will lead to downtime.




5.3.20 Alarm 2121035


DRAFT




Description System <SystemName> of type: m: sun4u, sys: SunOS, r: 5.8on <systemName>: System Joined Cluster


System ins3b of type: m: sun4u, sys: SunOS, r: 5.8 on ins3b:System Joined Cluster

Severity Normal


High Availability


No


5.3.21 Alarm 2121036



Description System <SystemName> of type: m: sun4u, sys: SunOS, r: 5.8on <systemName>: System Exited Manually


System ins3b of type: m: sun4u, sys: SunOS, r: 5.8 on ins3b:System Exited Manually

Severity Normal


High Availability


No

System Impact High Availability level is degraded.


Do one of the following:■ If the system is required in the cluster, run the

command hastart as user root.■ If the system is not required in the cluster, ignore the

alarm.


5.3.22 Alarm 2121037




DRAFT


Description System <SystemName> of type: m: sun4u, sys: SunOS, r: 5.8on <systemName>: System Up But Not In Cluster


System ins3b of type: m: sun4u, sys: SunOS, r: 5.8 on ins3b:System Up But Not In Cluster

Severity Warning


High Availability


No

System Impact High Availability level is degraded.




5.3.23 Alarm 2121062



Description VCS <SystemName> of type: <UserName> on<systemName>: GUI User Login


VCS ins3a of type: unknown user on ins3a: GUI User Login

Severity Normal


High Availability


No


5.3.24 Alarm 2121081



Description Agent <AgentType> of type: <AgentType> on <systemName>:Agent Restarting


Agent Process of type: Process on ins3a: Agent Restarting

Severity Warning


DRAFT



High Availability


No


5.3.25 Alarm 2121082



Description Agent <AgentType> of type: <AgentType> on <systemName>:Agent Faulted


Agent Process of type: Process on ins3a: Agent Faulted

Severity Minor


High Availability


No

System Impact No immediate impact but High Availability level is degraded.





DRAFT

Networking Agent Alarms 6■ Networking Agent Alarms Overview, Page 299

■ Cajun Alarms, Page 300

■ Others Alarms, Page 310

DRAFT

6: Networking Agent Alarms Networking Agent Alarms Overview

6.1 Networking Agent Alarms OverviewNetworking Agent alarms monitor the network units and generate an alarm if thenetwork is not functioning properly.

The following network agent alarms are monitored:

■ Cajun Alarms, Page 300

■ Others Alarms, Page 310


DRAFT

6: Networking Agent Alarms Cajun Alarms

6.2 Cajun AlarmsSearch for the alarm you need by its Specific Problem (Alarm ID).

6.2.1 Alarm 2810027


Managed Object Cajun

Description Duplicate IP address <$2> detected; MAC address <$1>.


■ <$2>: IP address■ <$1>: Corresponding MAC address

Severity Warning


Configuration


No


6.2.2 Alarm 2810028



Description IP VLAN Violation from <$2>: expected VLAN <$4>, detectedVLAN <$5>.


■ <$2>: Packet IP■ <$4>: Expected VLAN■ <$5>: Detected VLAN

Severity Warning


Security


No


6.2.3 Alarm 2810044




DRAFT


Description LAG <$3> (<$2>) connection lost.


■ <$2>: LAG ID■ <$3>: LAG name

Severity Critical


Network


Yes; by 2810046


6.2.4 Alarm 2810046



Description LAG <$3> (<$2>) connection lost - was cleared.



Severity Normal


Network


No


6.2.5 Alarm 2810048



Description LAG <$3> (<$2>) partial connection.



Severity Major


Network


Yes; by 2810050



DRAFT


6.2.6 Alarm 2810050



Description LAG <$3> (<$2>) partial connection - was cleared.



Severity Normal


Network


No


6.2.7 Alarm 2810052



Description LAG <$3> (<$2>) Auto Negotiation inconsistent results.



Severity Warning


Network


Yes; by 2810054


6.2.8 Alarm 2810054



Description LAG no. <$2> Auto Negotiation inconsistent results - wascleared.


<$2>: LAG ID

Severity Normal


DRAFT



Network


No


6.2.9 Alarm 2810079



Description Module <$2> Main Power Supply Failure.


<$2>: Module ID

Severity Critical


Hardware


Yes; by 2810081


6.2.10 Alarm 2810081



Description Module <$2> Main Power Supply Failure was cleared.


<$2>: Module ID

Severity Normal


Hardware


No


6.2.11 Alarm 2810083


DRAFT




Description Module <$2> Backup Power Supply Failure.


<$2>: Module ID

Severity Warning


Hardware


Yes; by 2810085


6.2.12 Alarm 2810085



Description Module <$2> Backup Power Supply Failure was cleared.


<$2>: Module ID

Severity Normal


Hardware


No


6.2.13 Alarm 2810087



Description Module <$2> Backup Power Supply Fan Failure.


<$2>: Module ID

Severity Critical


Hardware


Yes; by 2810089


DRAFT



6.2.14 Alarm 2810089



Description Module <$2> Backup Power Supply Fan Failure was cleared.


<$2>: Module ID

Severity Normal


Hardware


No


6.2.15 Alarm 2810091



Description Module <$2> Fan Failure.


<$2>: Module ID

Severity Critical


Hardware


Yes; by 2810093


6.2.16 Alarm 2810093



Description Module <$2> Fan Failure was cleared.


<$2>: Module ID


DRAFT


Severity Normal


Hardware


No


6.2.17 Alarm 2810600



Description Agent Up with Possible Changes (coldStart Trap)enterprise:<$E> (<$e>)

Severity Normal


Hardware


No


6.2.18 Alarm 2810602



Description Agent Interface Down (linkDown Trap) enterprise:<$E>(<$e>) on interface <$1>


<$1>: Interface index

Severity Major


Network


Yes; by 2810603


6.2.19 Alarm 2810603


DRAFT




Description Agent Interface Up (linkUp Trap) enterprise:<$E> (<$e>) oninterface <$1>


<$1>: Interface index

Severity Normal


Network


No


6.2.20 Alarm 2810604



Description Incorrect Community Name (authentication failure Trap)enterprise:<$E> (<$e>)

Severity Warning


Security


No


6.2.21 Alarm 2812315



Description Module <$2> cascading up connection lost.


<$2>: Module ID

Severity Critical


Hardware


Yes; by 2812316


DRAFT



6.2.22 Alarm 2812316



Description Module <$2> cascading up connection lost was cleared.


<$2>: Module ID

Severity Normal


Hardware


No


6.2.23 Alarm 2812317



Description Module <$2> cascading down connection lost.


<$2>: Module ID

Severity Critical


Hardware


Yes; by 2812318


6.2.24 Alarm 2812318



Description Module <$2> cascading down connection lost was cleared.


<$2>: Module ID


DRAFT


Severity Normal


Hardware


No



DRAFT

6: Networking Agent Alarms Others Alarms

6.3 Others AlarmsSearch for the alarm you need by its Specific Problem (Alarm ID).

6.3.1 Alarm 2820001


Managed Object Others

Description Reload trap. Reason: <whyReload>


whyReload: The reason for the reload trap

Severity Warning


Network


No

System Impact Depending on the location and function of the device in thenetwork, the reload may cause service degradation or a totalservice outage.


This event occurs when a Cisco entity is reinitializing. A reloadtrap signifies that the sending protocol entity is reinitializingitself such that the agents configuration or the protocol entityimplementation may be altered. Verify the reason for thedevice reload.


6.3.2 Alarm 2820002



Description TCP connection state changed. Session Type:<tslineSesType>. Session State: <tcpConnState>.


tslineSesType: The session type tcpConnState: The sessionconnection state

Severity Warning


Network


No


DRAFT


System Impact There is no known system impact for this alarm.


This event occurs when a tty connection state changed. Thistrap signifies that a TCP connection previously establishedwith the sending protocol entity state for the purposes of ttysession has been changed. Verify if an authorized user isconnected to the system.


6.3.3 Alarm 2820003



Description Temperature state changed. Reporting Object:<ciscoEnvMonTemperatureStatusDescr>. State: Normal.


ciscoEnvMonTemperatureStatusDescr: The object reportinga temperature change

Severity Normal


Network


No

Threshold < 75 C



A caemTemperatureNotification is sent if the over temperaturecondition that was detected in the managed system is cleared.No corrective action is required for this alarm.


6.3.4 Alarm 2820004



Description Temperature state changed. Reporting Object:<ciscoEnvMonTemperatureStatusDescr>. State:<ciscoEnvMonTemperatureState>.


ciscoEnvMonTemperatureStatusDescr: The object reportinga temperature change.

ciscoEnvMonTemperatureState: The state of the objectreporting a temperature change

Severity Critical


DRAFT



Network


No

Threshold > 75 C

System Impact Depending on the location and function of the device inthe network, the change in temperature may cause servicedegradation or a total service outage.


A caemTemperatureNotification is sent if the over temperaturecondition is detected in the managed system. Check thedevice fans and ambient temperature.


6.3.5 Alarm 2820005



Description Environmental temperature state changed. Reporting Object:<ciscoEnvMonTemperatureStatusDescr>. Temperature:<ciscoEnvMonTemperatureStatusValue> degrees Celsius.State: Normal.


ciscoEnvMonTemperatureStatusDescr: The object reporting atemperature change ciscoEnvMonTemperatureStatusValue:The reported temperature

Severity Normal


Network


No

Threshold < 75 C



A ciscoEnvMonTemperatureNotification is sent if thetemperature measured at a given testpoint is at the normalrange for the testpoint. No corrective action is required forthis alarm.


6.3.6 Alarm 2820006


DRAFT




Description Environmental temperature state changed. Reporting Object:<ciscoEnvMonTemperatureStatusDescr>. Temperature:<ciscoEnvMonTemperatureStatusValue> degrees Celsius.State: <ciscoEnvMonTemperatureState>.


ciscoEnvMonTemperatureStatusDescr: The object reporting atemperature change ciscoEnvMonTemperatureStatusValue:The reported temperature ciscoEnvMonTemperatureState:The state of the object reporting a temperature change

Severity Critical


Network


Yes; by 2820005

Threshold > 75 C

System Impact Depending on the environmental conditions, servicedegradation may occur.


A ciscoEnvMonTemperatureNotification is sent if thetemperature measured at a given testpoint is outside thenormal range for the testpoint (i.e. is at the warning, critical,or shutdown stage). Since such a Notification is usuallygenerated before the shutdown state is reached, it can conveymore data and has a better chance of being sent than doesthe ciscoEnvMonShutdownNotification. This notification isdeprecated in favor of ciscoEnvMonTempStatusChangeNotif.Check the ambient temperature and that all the fans areoperating.


6.3.7 Alarm 2820007



Description Environmental temperature status changed. Reporting Object:<ciscoEnvMonTemperatureStatusDescr>. Temperature:<ciscoEnvMonTemperatureStatusValue> degrees Celsius.Status: Normal.


ciscoEnvMonTemperatureStatusDescr: The object reporting atemperature change ciscoEnvMonTemperatureStatusValue:The reported temperature

Severity Normal


Network


DRAFT



No

Threshold < 75 C



A ciscoEnvMonTempStatusChangeNotif is sent if the state ofa device being monitored by ciscoEnvMonTemperatureStatechanged to normal. No corrective action is required for thisalarm.


6.3.8 Alarm 2820008



Description Environmental temperature status changed. Reporting Object:<ciscoEnvMonTemperatureStatusDescr>. Temperature:<ciscoEnvMonTemperatureStatusValue> degrees Celsius.Status: <ciscoEnvMonTemperatureState>.


ciscoEnvMonTemperatureStatusDescr: The object reporting atemperature change ciscoEnvMonTemperatureStatusValue:The reported temperature ciscoEnvMonTemperatureState:The state of the object reporting a temperature change

Severity Critical


Network


Yes; by 2820007

Threshold > 75 C

System Impact Depending on the environmental conditions, servicedegradation or a total service outage may occur.


A ciscoEnvMonTempStatusChangeNotif is sent if thereis change in the state of a device being monitored byciscoEnvMonTemperatureState. Check the ambienttemperature and that all the fans are operating.


6.3.9 Alarm 2820009




DRAFT


Description Fan tray state changed. Reporting Object:<ciscoEnvMonFanStatusDescr>. State: Normal.


ciscoEnvMonFanStatusDescr: The fan reporting a statuschange

Severity Normal


Hardware


No



A ciscoEnvMonFanNotification is sent if any one of the fans inthe fan array (where extant) returned to normal. No correctiveaction is required for this alarm.


6.3.10 Alarm 2820010



Description Fan tray state changed. Reporting Object:<ciscoEnvMonFanStatusDescr>. State:<ciscoEnvMonFanState>.


ciscoEnvMonFanStatusDescr: The fan reporting a statuschange ciscoEnvMonFanState: The state of the fan reportinga state change

Severity Critical


Hardware


Yes; by 2820009



A ciscoEnvMonFanNotification is sent if any one of the fansin the fan array (where extant) returned to normal. Check theunit’s fans and replace them if required.


6.3.11 Alarm 2820011




DRAFT


Description The Cisco configuration changed via the<ccmHistoryEventCommandSource> source.


ccmHistoryEventCommandSource: The configuration changesource

Severity Warning


Network


No

System Impact Depending on the change, it may have no impact, causeservice degradation, or cause a total service outage.


Notification of a configuration management event as recordedin ccmHistoryEventTable. Verify that the configuration changewas planned and performed by an authorized engineer.


6.3.12 Alarm 2820012



Description Syslog message received. Message Text: <clogHistMsgText>.


clogHistMsgText: The log message

Severity Normal


Network


No

System Impact Depends on the message generated by the device. This alarmis always generated with another application ID alarm.


When a syslog message is generated by the device aclogMessageGenerated notification is sent. The sendingof these notifications can be enabled/disabled via theclogNotificationsEnabled object. No corrective action isrequired for this alarm.


6.3.13 Alarm 2820013


DRAFT




Description HSRP state changed to: <cHsrpGrpStandbyState>.


cHsrpGrpStandbyState: The HSRP state

Severity Major


Network


No

System Impact Service degradation may occur during the state change.


A cHsrpStateChange notification is sent when acHsrpGrpStandbyState transitions to either active or standbystate, or leaves active or standby state. There is only onenotification issued when the state change is from standby toactive and vice versa. Verify the reason for the HSRP statechange and review the status of the standby device.


6.3.14 Alarm 2820014



Description High CPU utilization. Rising Threshold Value:<cpmCPURisingThresholdValue>%. Current Value:<cpmProcExtUtil5SecRev>%.


cpmCPURisingThresholdValue: The value of the CPUutilization threshold cpmProcExtUtil5SecRev: The actual CPUusage

Severity Major


Network


Yes; by 2820015

Threshold 0.85


DRAFT


System Impact Service degradation may occur.


A cpmCPURisingThreshold notification is sentwhen configured rising CPU utilization threshold(cpmCPURisingThresholdValue) is reached and CPUutilization remained above the threshold for configuredinterval (cpmCPURisingThresholdPeriod) and such anotification is requested. The cpmProcExtUtil5SecRev andcpmProcessTimeCreated objects can be repeated multipletimes in a notification indicating the top users of CPU. Use theshow proc command to investigate the reason for the highCPU utilization.


6.3.15 Alarm 2820015



Description Low CPU utilization. Falling CPU Utilization Falling Threshold:<cpmCPUFallingThresholdValue>%.


cpmCPUFallingThresholdValue: The value of the CPUutilization threshold

Severity Normal


Network


No

Threshold 15



A cpmCPUFallingThresholdTrap is sent when the configuredfalling threshold (cpmCPURisingThresholdValue) is reachedand CPU utilization remained under threshold for configuredinterval (cpmCPUFallingThresholdPeriod) and such anotification is requested. No corrective action is required forthis alarm.


6.3.16 Alarm 2820016




DRAFT


Description Power supply state changed. Reporting Object:<entPhysicalName>, <entPhysicalDescr>. Operational Status:On. Administrative Status: <cefcFRUPowerAdminStatus>.


entPhysicalName: The name of the device entPhysicalDescr:The description of the device cefcFRUPowerAdminStatus:The administrative status of the device

Severity Normal


Hardware


No



The cefcFRUPowerStatusChange notification indicates thatthe power status of a FRU has changed. The varbind for thisnotification indicates the entPhysicalIndex of the FRU, andthe new operational-status of the FRU. No corrective action isrequired for this alarm.


6.3.17 Alarm 2820017



Description Power supply state changed. Reporting Object:<entPhysicalName>, <entPhysicalDescr>. OperationalStatus: <cefcFRUPowerOperStatus>. Administrative Status:<cefcFRUPowerAdminStatus>.


entPhysicalName: The name of the device entPhysicalDescr:The description of the device cefcFRUPowerOperStatus:The power supply status cefcFRUPowerAdminStatus: Theadministrative status of the device

Severity Minor


Hardware


Yes; by 2820016



The cefcFRUPowerStatusChange notification indicates thatthe power status of a FRU has changed. The varbind for thisnotification indicates the entPhysicalIndex of the FRU, and thenew operational-status of the FRU. Review the power inputto the rack, power cables, circuit breakers, and the powerswitch on the power supply.


DRAFT



6.3.18 Alarm 2820018



Description FRU inserted. Reporting Object: <entPhysicalDescr>,<entPhysicalContainedIn>.


entPhysicalDescr: The description of the deviceentPhysicalContainedIn: The unit in which the FRU wasinserted

Severity Normal


Hardware


No



The cecfFRUInserted notification indicates that a FRUwas inserted. The varbind for this notification indicatesthe entPhysicalIndex of the inserted FRU, and theentPhysicalIndex of the FRU’s container. Verify that the FRUwas installed by an authorized engineer.


6.3.19 Alarm 2820019



Description FRU removed. Reporting Object:<entPhysicalDescr>,<entPhysicalContainedIn>.


entPhysicalDescr: The description of the deviceentPhysicalContainedIn: The unit in which the FRU wasinserted

Severity Major


Hardware


Yes; by 2820018


DRAFT


System Impact Normally, there is no system impact. If the FRU is a fan trayand a working fan tray is not installed within five minutes,pending the ambient temperature service degradation, andpotentially a total service outage, may occur.


The cefcFRURemoved notification indicates that a FRUwas removed. The varbind for this notification indicatesthe entPhysicalIndex of the removed FRU, and theentPhysicalIndex of the FRU’s container. Verify the reason forthe FRU removal. If the removed FRU is a fan tray, ensure afan tray is installed in less than five minutes.


6.3.20 Alarm 2820020



Description Operational state of fan tray changed to: On.

Severity Normal


Network


No



This notification is generated when the value ofcefcFanTrayOperStatus changed to normal. No correctiveaction is required for this alarm.


6.3.21 Alarm 2820021



Description Operational state of fan tray changed to:<cefcFanTrayOperStatus>.


cefcFanTrayOperStatus: The fan tray status

Severity Major


Network


DRAFT



Yes; by 2820020

System Impact Normally, there is no system impact. If the FRU is a fan trayand a working fan tray is not installed within five minutes,pending the ambient temperature service degradation, andpotentially a total service outage, may occur.


This notification is generated when the value ofcefcFanTrayOperStatus changes. Verify the status of the fansusing the show env command. If required, replace the fan tray.


6.3.22 Alarm 2820022



Description Redundant power supply state changed. Reporting Object:<ciscoEnvMonSupplyStatusDescr>. State: Normal.


ciscoEnvMonSupplyStatusDescr: The object reporting thechange

Severity Normal


Hardware


No



ciscoEnvMonRedundantSupplyNotification is sent if theredundant power supply (where extant) returned to normal.No corrective action is required for this alarm.


6.3.23 Alarm 2820023



Description Redundant power supply state changed notification.Reporting object: <ciscoEnvMonSupplyStatusDescr>. State:<ciscoEnvMonSupplyState>.



ciscoEnvMonSupplyState: The state of the power supply


DRAFT


Severity Minor


Hardware


Yes; by 2820022



A ciscoEnvMonRedundantSupplyNotification is sent ifthe redundant power supply (where extant) fails. Sincesuch a notification is usually generated before theshutdown state is reached, it can convey more dataand has a better chance of being sent than does theciscoEnvMonShutdownNotification. This notification isdeprecated in favor of ciscoEnvMonSuppStatusChangeNotif.Review the power input to the rack, power cables, circuitbreakers, and the power switch on the power supply.


6.3.24 Alarm 2820024



Description Redundant power supply status changed. Reporting Object:<ciscoEnvMonSupplyStatusDescr>. Status: Normal.



Severity Normal


Hardware


No



A ciscoEnvMonSupplyStatChangeNotif is sent if the state of adevice being monitored by ciscoEnvMonSupplyState changedto normal. No corrective action is required for this alarm.


6.3.25 Alarm 2820025




DRAFT


Description Redundant power supply status changed. ReportingObject: <ciscoEnvMonSupplyStatusDescr>. Status:<ciscoEnvMonSupplyState>.


ciscoEnvMonSupplyStatusDescr: The object reporting thechange ciscoEnvMonSupplyState: The state of the powersupply

Severity Minor


Hardware


Yes; by 2820024



A ciscoEnvMonSupplyStatChangeNotif is sent if thereis change in the state of a device being monitored byciscoEnvMonSupplyState. Review the power input to the rack,power cables, circuit breakers, the and power switch on thepower supply.


6.3.26 Alarm 2820026



Description Fan tray state changed. Reporting Object:<ciscoEnvMonFanStatusDescr>. State: Normal.


ciscoEnvMonFanStatusDescr: The fan tray reporting thechange

Severity Normal


Hardware


No



A ciscoEnvMonFanStatusChangeNotif is sent if the state of adevice being monitored by ciscoEnvMonFanState changed tonormal. No corrective action is required for this alarm.


6.3.27 Alarm 2820027


DRAFT




Description Fan tray state changed. Reporting Object:<ciscoEnvMonFanStatusDescr>. State:<ciscoEnvMonFanState>.


ciscoEnvMonFanStatusDescr: The fan tray reporting thechange ciscoEnvMonFanState: The state of the fan tray

Severity Critical


Hardware


Yes; by 2820026

System Impact Depending on the environmental conditions, servicedegradation may occur.


A ciscoEnvMonFanStatusChangeNotif is sent if thereis change in the state of a device being monitored byciscoEnvMonFanState. Check the ambient temperature andthat all the fans are operating.


6.3.28 Alarm 2820028



Description Storm control event state changed to: <cpscStatus>.


cpscStatus: The storm control event state

Severity Critical


Network


No

System Impact Depending on the event, it may cause service degradation ora total service outage.


This notification is sent by the implementation when a stormevent occurs on an interface with respect to a particular traffictype. Check for any changes in the network topology and/orabnormal traffic.



DRAFT


6.3.29 Alarm 2820029



Description Loop inconsistency state changed to: Destroyed. ActualSpanning Tree Mode: <stpxSpanningTreeType>.


stpxSpanningTreeType: The actually spanning tree mode

Severity Normal


Network


No



A stpxLoopInconsistencyUpdate notification is sent by abridge when an instance of stpxLoopInconsistencyStateis destroyed. That is, when such a loop-inconsistencydisappears. The object value of stpxSpanningTreeTypeindicates which Spanning Tree protocol is running whenan instance of stpxLoopInconsistencyState is created ordestroyed. There is no corrective action for this alarm.


6.3.30 Alarm 2820030



Description Loop inconsistency state changed to: Created. ActualSpanning Tree Mode: <stpxSpanningTreeType>.


stpxSpanningTreeType: The actually spanning tree mode

Severity Major


Network


Yes; by 2820029


DRAFT


System Impact Depending on the event, it may cause service degradation ora total service outage.


A stpxLoopInconsistencyUpdate notification is sent by abridge when an instance of stpxLoopInconsistencyState iscreated. That is, when a loop-inconsistency is discoveredin the VLAN’s or instance’s Spanning Tree for a particularport. The object value of stpxSpanningTreeType indicateswhich Spanning Tree protocol is running when an instance ofstpxLoopInconsistencyState is created or destroyed. Checkfor any changes in the network topology.


6.3.31 Alarm 2820031



Description Cold start. Last Reset Reason: <LastResetReason>.


LastResetReason: The reason for the last reset

Severity Warning


Network


No

System Impact This alarm is sent after the unit is powered up. When the unitis not operational, service degradation or a complete serviceoutage may occur.


A coldStart trap signifies that this entity, acting in an agentrole, is reinitializing itself and that its configuration may havebeen altered. Verify that the unit power up was performedintentionally.


6.3.32 Alarm 2820032



Description Link down on interface: <ifDescr>.


ifDescr: The interface name

Severity Major


DRAFT



Network


Yes; by 2820033

System Impact Depending on the functionality of the device connected tothat port, it may cause service degradation or a total serviceoutage.


A linkDown trap signifies that the sending protocol entityrecognizes a failure in one of the communication linksrepresented in the agents configuration. Check the cableand/or link partner.


6.3.33 Alarm 2820033



Description Link up on interface: <ifDescr>.


ifDescr: The interface name

Severity Normal


Network


No



A linkUp trap signifies that the sending protocol entityrecognizes that one of the communication links represented inthe agent’s configuration has come up. There is no correctiveaction for this alarm.


6.3.34 Alarm 2820034



Description Incorrect community name (authenticationFailure Trap).Potential Attacker IP: <authAddr>.


authAddr: The IP address


DRAFT


Severity Minor


Security


No

System Impact Login failure.


This event occurs when the Cisco agent detects anauthentication failure has occurred. An authenticationfailure trap signifies that the sending protocol entity isthe addressee of a protocol message that is not properlyauthenticated. Check the potential intruder - unauthorizedaccess attempt. Report security administration change (usercreation/deletion/edit, password change, encryption levelchange).



DRAFT

Application Agent Alarms 7■ Application Agent Alarms Overview, Page 331

■ CCS_CC Alarms, Page 332

■ GenericDatabase Alarms, Page 335

■ OMNI Alarms, Page 337

■ Oracle Database Alarms (OnGuard Agent), Page 340

■ Server Monitor (SMU) Alarms, Page 415

■ SPM Agent Alarms, Page 446

■ SMSC Alarms, Page 449

■ Possibly Used Traps, Page 485

DRAFT

7: Application Agent Alarms Application Agent Alarms Overview

7.1 Application Agent Alarms OverviewApplication Agent alarms monitor the Applications in the SMSC System andgenerate an alarm when the application is not functioning properly.

The following Application Agent alarms are monitored:

■ CCS_CC Alarms, Page 332

■ GenericDatabase Alarms, Page 335

■ OMNI Alarms, Page 337

■ Oracle Database Alarms (OnGuard Agent), Page 340

■ Server Monitor (SMU) Alarms, Page 415

■ SPM Agent Alarms, Page 446

■ SMSC Alarms, Page 449

■ Possibly Used Traps, Page 485


DRAFT

7: Application Agent Alarms CCS_CC Alarms

7.2 CCS_CC AlarmsSearch for the alarm you need by its Specific Problem (Alarm ID).

7.2.1 Alarm 1465330


Managed Object CCS_CC

Description Peer application is not accessible via SLAN.

Severity Minor


Application


Yes; by 1465330

Threshold After 1 occurrence

System Impact When both events (5330 & 5331) occur, system willswitchover.


Verify COM ports of first unit are cross connected by cable tothe COM ports of second unit.


7.2.2 Alarm 1465331



Description Peer application is not accessible via UDP LAN.

Severity Major


Application


Yes; by 1465331

Threshold After 2 occurrences

System Impact When both events (5330 & 5331) occur, system willswitchover.


Verify LAN cable of peer unit is connected properly



DRAFT


7.2.3 Alarm 1465350



Description Peak capacity reached; possible message lost.

Severity Minor


Application


Yes; by 1465350

Threshold After 1 occurrence

System Impact All new incoming calls are released until expiration of timeinterval


1 Check the BHCA in the system2 If it is higher than expected, verify the load at the switch.


7.2.4 Alarm 1467902



Description Capacity has reached <$A> percent.

Severity Critical

Major

Minor

Warning


Capacity


Yes; by 1467902

Threshold ■ Warning: > 0.8■ Minor: > 0.9■ Major: > 1■ Critical: > 1.23

System Impact All incoming traffic is released until expiration of time interval


1 Check the BHCA in the system2 If it is higher than expected, verify the load at the switch


DRAFT



7.2.5 Alarm 1469110



Description CCS <ce name> out of service.

Severity Major


Application


Yes; by 1469110

Threshold FAIL

System Impact Switch over





DRAFT

7: Application Agent Alarms GenericDatabase Alarms

7.3 GenericDatabase AlarmsSearch for the alarm you need by its Specific Problem (Alarm ID).

7.3.1 Alarm 2113062



Description Generic Database Message - Normal

Severity Normal


No


7.3.2 Alarm 2113063



Description Generic Database Message - Warning

Severity Warning


No


7.3.3 Alarm 2113064



Description Generic Database Message - Minor

Severity Minor


No


7.3.4 Alarm 2113065


DRAFT

7: Application Agent Alarms GenericDatabase Alarms



Description Generic Database Message - Major

Severity Major


No


7.3.5 Alarm 2113066



Description Generic Database Message - Critical

Severity Critical


No



DRAFT

7: Application Agent Alarms OMNI Alarms

7.4 OMNI AlarmsSearch for the alarm you need by its Specific Problem (Alarm ID).

7.4.1 Alarm 1418001


Managed Object OMNI

Description RSET <$A> = RSET name DPC = <$B> = DPC number LN(<$C>) = logical node name (usually A7 or C7) [<$D>] =string to describe status: availaible/unavailable/blocked/oadsharing/non load sharing

Severity Major


Communication/Network


Yes; by 1418001

Threshold FAIL

System Impact No service for specific routeset




7.4.2 Alarm 1418201


Managed Object OMNI

Description LNK <$A> = LINK name LN (<$B>) = logical node name(usually A7 or C7) [<$C>] = string to describe status:availaible/fail/remotely blocked/locally blocked/remotelyinhibited/ locally inhibited

Severity Major


Communication/Network


Yes; by 1418201

Threshold FAIL

System Impact All the traffic is rerouted to other link/s in routeset if they exist.




DRAFT



7.4.3 Alarm 2113052


Managed Object OMNI

Description Generic Application Message - Normal

Severity Normal


No


7.4.4 Alarm 2113053


Managed Object OMNI

Description Generic Application Message - Warning

Severity Warning


No


7.4.5 Alarm 2113054


Managed Object OMNI

Description Generic Application Message - Minor

Severity Minor


No


7.4.6 Alarm 2113055


Managed Object OMNI


DRAFT


Description Generic Application Message - Major

Severity Major


No


7.4.7 Alarm 2113056


Managed Object OMNI

Description Generic Application Message - Critical

Severity Critical


No



DRAFT

7: Application Agent Alarms Oracle Database Alarms (OnGuard Agent)

7.5 Oracle Database Alarms (OnGuard Agent)Search for the alarm you need by its Specific Problem (Alarm ID).

7.5.1 Alarm 2110001



Description The <database> database is down.


<database>: Database name

If you do not have an Oracle database, this alarm is notrelevant.

Severity Critical


Database


Yes; by 2110002


7.5.2 Alarm 2110002



Description The <database> database is up.




Severity Normal


Database


No


7.5.3 Alarm 2110003




DRAFT


Description The <database> database is pending startup or shutdown.




Severity Warning


Database


Yes; by 2110002


7.5.4 Alarm 2110004



Description A database status event timed out. The <database> databaseis not responding.




Severity Warning


Database


Yes; by 2110002


7.5.5 Alarm 2110005



Description A database status event for the <database> database failed.




Severity Warning


DRAFT



Database


Yes; by 2110002


7.5.6 Alarm 2110006



Description The <listener> listener is up.


<listener>: Listener name


Severity Normal


Database


No


7.5.7 Alarm 2110007



Description The <listener> listener is down.




Severity Critical


Database


Yes; by 2110006


7.5.8 Alarm 2110008


DRAFT




Description The <listener> listener is not responding.




Severity Warning


Database


Yes; by 2110006


7.5.9 Alarm 2110009



Description A listener status event for the <listener> listener failed.




Severity Warning


Database


Yes; by 2110006


7.5.10 Alarm 2110010



Description The following error message was found in the alert log:<specificError>.


<specificError>: Detailed error text


Severity Major


DRAFT



Database


No


7.5.11 Alarm 2110011



Description The following warning message was found in the alert log:<specificError>.




Severity Warning


Database


No


7.5.12 Alarm 2110012



Description The following error message was found in the listener log:<specificError>.




Severity Major


Database


No



DRAFT


7.5.13 Alarm 2110013



Description The following warning message was found in the listener log:<specificError>.




Severity Warning


Database


No


7.5.14 Alarm 2110014



Description There are no locks in the <database> database.




Severity Normal


Database


No


7.5.15 Alarm 2110015



Description There are blocking locks in the <database> database.


DRAFT





Severity Warning


Database


Yes; by 2110014


7.5.16 Alarm 2110016



Description A blocking locks event timed out. The <database> databaseis not responding.




Severity Warning


Database


Yes; by 2110014


7.5.17 Alarm 2110017



Description A blocking locks event for the <database> database failed.




Severity Warning


Database


Yes; by 2110014


DRAFT



7.5.18 Alarm 2110018



Description <usage value>% of the <tablespace> tablespace in the<database> database is in use.


■ <usage value>: Percentage used■ <tablespace>: Tablespace name■ <database>: Database name


Severity Normal


Database


No

Threshold 1–89%


7.5.19 Alarm 2110019







Severity Warning


Database


Yes; by 2110018

Threshold 90–95%



DRAFT


7.5.20 Alarm 2110020







Severity Major


Database


Yes; by 2110018

Threshold 96–100%


7.5.21 Alarm 2110021



Description A tablespace free space event timed out. The <database>database is not responding.




Severity Warning


Database


Yes; by 2110018


7.5.22 Alarm 2110022


DRAFT




Description A tablespace free space event for the <database> databasefailed.




Severity Warning


Database


Yes; by 2110018


7.5.23 Alarm 2110023



Description There are no invalid objects in the <database> database.




Severity Normal


Database


No


7.5.24 Alarm 2110024



Description The status of the objects <objects> in the <database>database is invalid.


DRAFT



■ <objects>: List of objects■ <database>: Database name


Severity Warning


Database


Yes; by 2110023


7.5.25 Alarm 2110025



Description The status of the objects <objects> in the <database>database is invalid.


■ <objects>: List of objects■ <database>: Database name


Severity Major


Database


Yes; by 2110023


7.5.26 Alarm 2110026



Description An invalid objects event timed out. The <database> databaseis not responding.




Severity Warning


DRAFT



Database


Yes; by 2110023


7.5.27 Alarm 2110027



Description An invalid objects event for the <database> database failed.




Severity Warning


Database


Yes; by 2110023


7.5.28 Alarm 2110028



Description <usage value>% of the <archive> archive in the <database>database is in use.


■ <usage value>: Percentage used■ <archive>: Location of archive files■ <database>: Database name


Severity Normal


Database


No

Threshold 1–84%


DRAFT



7.5.29 Alarm 2110029







Severity Warning


Database


Yes; by 2110028

Threshold 85–95%


7.5.30 Alarm 2110030







Severity Critical


Database


Yes; by 2110028

Threshold 96–100%



DRAFT


7.5.31 Alarm 2110031



Description An archive dump destination event timed out. The <database>database is not responding.




Severity Warning


Database


Yes; by 2110028


7.5.32 Alarm 2110032



Description An archive dump dest event for the <database> databasefailed.




Severity Warning


Database


Yes; by 2110028


7.5.33 Alarm 2110033



Description The database backup was completed successfully.


DRAFT




Severity Normal


Database


No


7.5.34 Alarm 2110034



Description Problems were detected in the daily backup. Refer to<logFilePath> for more details.


<logFilePath>: Log file path


Severity Major


Database


Yes; by 2110033


7.5.35 Alarm 2110035



Description There are no broken or failed jobs in the <database>database.

Severity Normal


Database


No



DRAFT


7.5.36 Alarm 2110036



Description The <database> database contains the following broken orfailed jobs: <JobInfo>.


■ <database>: Database name■ <JobInfo>: Job information list


Severity Warning


Database


Yes; by 2110035


7.5.37 Alarm 2110037



Description The <database> database contains the following broken orfailed jobs: <JobInfo>.


■ <database>: Database name■ <JobInfo>: Job information list


Severity Major


Database


Yes; by 2110035


7.5.38 Alarm 2110038




DRAFT


Description Job number <jobno> failed to rerun.


<jobno>: Job number


Severity Major


Database


Yes; by 2110039


7.5.39 Alarm 2110039



Description Job number <jobno> has successfully been rerun.


<jobno>: Job number


Severity Normal


Database


No


7.5.40 Alarm 2110040



Description A failed or broken jobs event for the <database> databasetimed out.




Severity Warning


DRAFT



Database


Yes; by 2110035


7.5.41 Alarm 2110041



Description A failed or broken jobs event for the <database> databasefailed.




Severity Warning


Database


Yes; by 2110035


7.5.42 Alarm 2110042



Description The <database> database has <NumberOfSessions>connected sessions out of a maximum of <maxSessions>(<usage value>% used).


■ <database>: Database name■ <NumberOfSessions>: Number of concurrent sessions■ <maxSessions>: Maximum number of sessions allowed

in the database■ <usage value>: Percentage used


Severity Normal


DRAFT



Database


No


7.5.43 Alarm 2110043








Severity Warning


Database


Yes; by 2110042


7.5.44 Alarm 2110044





DRAFT






Severity Major


Database


Yes; by 2110042


7.5.45 Alarm 2110045



Description A concurrent sessions event for the <database> databasetimed out.




Severity Warning


Database


Yes; by 2110042


7.5.46 Alarm 2110046



Description A concurrent session’s event for the <database> databasefailed.





DRAFT


Severity Warning


Database


Yes; by 2110042


7.5.47 Alarm 2110047



Description <usage value>% of the maximum allowed shared serversis in use.


<usage value>: Percentage used


Severity Normal


Database


No


7.5.48 Alarm 2110048





<usage value>: Percentage used.


Severity Warning


Database


Yes; by 2110047



DRAFT


7.5.49 Alarm 2110049







Severity Major


Database


Yes; by 2110047


7.5.50 Alarm 2110050



Description There are <NumberOfServers> dedicated server connections.The number of connections is normal.


<NumberOfServers>: Number of dedicated servers in thedatabase.


Severity Normal


Database


No


7.5.51 Alarm 2110051




DRAFT


Description There are <NumberOfServers> dedicated server connections.The threshold has been exceeded.


<NumberOfServers>: Number of dedicated servers in thedatabase


Severity Warning


Database


Yes; by 2110050


7.5.52 Alarm 2110052



Description There are <NumberOfServers> dedicated server connections.The threshold has been exceeded.


<NumberOfServers>: Number of dedicated servers in thedatabase.


Severity Major


Database


Yes; by 2110050


7.5.53 Alarm 2110053



Description <usage value>% of the large pool is in use.


<usage value>: Percentage used.


Severity Normal


DRAFT



Database


No


7.5.54 Alarm 2110054







Severity Warning


Database


Yes; by 2110053


7.5.55 Alarm 2110055







Severity Critical


Database


Yes; by 2110053


7.5.56 Alarm 2110056


DRAFT




Description The activity log procedure was completed successfully.



Severity Normal


Database


No


7.5.57 Alarm 2110057



Description The activity log procedure failed.



Severity Critical


Database


Yes; by 2110056


7.5.58 Alarm 2110058



Description <usage value>% of the activity log directory is in use.




Severity Normal


Database


DRAFT



No

Threshold 1–79%


7.5.59 Alarm 2110059







Severity Warning


Database


Yes; by 2110058

Threshold 80–89%


7.5.60 Alarm 2110060







Severity Critical


Database


Yes; by 2110058

Threshold 90–100%



DRAFT


7.5.61 Alarm 2111000



Description Warning: There is an internal database problem. Pleasecheck the OnGuard console for further details.



Severity Warning


Database


Yes; by 2111002, 2111003


7.5.62 Alarm 2111001



Description Error: There is an internal database problem. Please checkthe OnGuard console for further details.



Severity Major


Database


Yes; by 2111002


7.5.63 Alarm 2111002



Description The database status is Normal.



Severity Normal


DRAFT



Database


No


7.5.64 Alarm 2111003



Description The database status is Warning.



Severity Warning


Database


No


7.5.65 Alarm 2111004



Description The database status is Error.



Severity Major


Database


No


7.5.66 Alarm 2111005


DRAFT




Description Warning: There is an internal application problem. Pleasecheck the OnGuard console for further details.


Generic message. The alarm should be ignored.

Severity Warning


Application


Yes; by 2111007


7.5.67 Alarm 2111006



Description Error: There is an internal application problem. Please checkthe OnGuard console for further details.


Generic message. The alarm should be ignored.

Severity Major


Application


Yes; by 2111007, 2111008


7.5.68 Alarm 2112001



Description The CPU usage is <CPU value>%.


<CPU value>: Percentage of the CPU in use

Severity Normal


Operating System


DRAFT



No

Threshold 0–69%


7.5.69 Alarm 2112002






this problem

Severity Warning


Operating System


Yes; by 2112001

Threshold 70–89%






7.5.70 Alarm 2112003






this problem

Severity Major


Operating System


DRAFT



Yes; by 2112001

Threshold 90–100%






7.5.71 Alarm 2112004



Description A CPU usage event timed out.

Severity Warning


Operating System


Yes; by 2112001





7.5.72 Alarm 2112005



Description A CPU usage event failed.

Severity Warning


Operating System


Yes; by 2112001






DRAFT


7.5.73 Alarm 2112006







Severity Normal


Operating System


No

Threshold 0–89%


7.5.74 Alarm 2112007







Severity Warning


Operating System


Yes; by 2112006

Threshold 90–94%





DRAFT



7.5.75 Alarm 2112008







Severity Major


Operating System


Yes; by 2112006

Threshold 95–100%





7.5.76 Alarm 2112009



Description A file system free space event timed out.

Severity Warning


Operating System


Yes; by 2112006






DRAFT


7.5.77 Alarm 2112010



Description A file system free space event failed.

Severity Warning


Operating System


Yes; by 2112006





7.5.78 Alarm 2112011



Description The load average is <load average value>.


<load average value>: Load average value.

Severity Normal


Operating System


No

Threshold 0–2


7.5.79 Alarm 2112012





DRAFT




this problem

High average number of jobs in the run queue over the last15 minutes per processor.

Severity Warning


Operating System


Yes; by 2112011

Threshold 2–3



Reduce the number of heavy applications on the unit ifpossible.


7.5.80 Alarm 2112013






this problem

Very high average number of jobs in the run queue over thelast 15 minutes per processor.

Severity Major


Operating System


Yes; by 2112011

Threshold 4+



Reduce the number of heavy applications on the machine ifpossible.


7.5.81 Alarm 2112014


DRAFT




Description A load average event timed out.

Severity Warning


Operating System


Yes; by 2112011





7.5.82 Alarm 2112015



Description A load average event failed.

Severity Warning


Operating System


Yes; by 2112011





7.5.83 Alarm 2112016



Description The swap usage is <swap value>%.


<swap value>: Percentage of swap area in use.

Severity Normal


Operating System


DRAFT



No

Threshold 0–69%


7.5.84 Alarm 2112017






this problem

Severity Warning


Operating System


Yes; by 2112016

Threshold 70–89%





7.5.85 Alarm 2112018






this problem

Severity Major


Operating System


Yes; by 2112016


DRAFT


Threshold 90–100%





7.5.86 Alarm 2112019



Description A swap usage event timed out.

Severity Warning


Operating System


Yes; by 2112016





7.5.87 Alarm 2112020



Description A swap usage event failed.

Severity Warning


Operating System


Yes; by 2112016





7.5.88 Alarm 2112021


DRAFT




Description The I/O wait is <I/O waits value>%.


<I/O waits value>: Percentage of I/O waits out of the totalCPU time.

Severity Normal


Operating System


No

Threshold 0–9


7.5.89 Alarm 2112022







Severity Warning


Operating System


Yes; by 2112021

Threshold 10-29





7.5.90 Alarm 2112023




DRAFT






Severity Major


Operating System


Yes; by 2112021

Threshold 30+





7.5.91 Alarm 2112024



Description An I/O wait event timed out.

Severity Warning


Operating System


Yes; by 2112021





7.5.92 Alarm 2112025



Description An I/O wait event failed.

Severity Warning


DRAFT



Operating System


Yes; by 2112021





7.5.93 Alarm 2112026



Description The network response time for <server name> is normal.



Severity Normal


Operating System


No

Threshold 0–19 ms


7.5.94 Alarm 2112027



Description High network response time. The network response time for<server name> is <response time> ms.


■ <server name>: Server name, IP, or URL■ <response time>: Average response time in ms

Severity Warning


Operating System


Yes; by 2112026

Threshold 20+ ms


DRAFT


System Impact Poor network connection to the remote server which maycause slow data transfer.




7.5.95 Alarm 2112028



Description <server name> is not responding to a ping request (<lostpackets> out of <sent packets> packets lost).


■ <server name>: Server name, IP, or URL■ <lost packets>: Number of lost packets■ <sent packets>: Number of sent packets

Severity Critical


Operating System


Yes; by 2112026






7.5.96 Alarm 2112029



Description Ping error for <server name> (unknown host <server name>).


<server name>: Server name, IP, or URL.

Severity Warning


Operating System


Yes; by 2112026


DRAFT





Ask the system administrator about this host name and incase of need, change it in OnGuard.


7.5.97 Alarm 2112030



Description Network availability event timed out.

Severity Warning


Operating System


Yes; by 2112026

System Impact Network availability is not checked.




7.5.98 Alarm 2112031



Description Pinging <server name> failed.



Severity Warning


Operating System


Yes; by 2112026

System Impact This server is not checked for network availability.





DRAFT


7.5.99 Alarm 2112032






Severity Normal


Operating System


No

Threshold 0–84%


7.5.100 Alarm 2112033






Severity Warning


Operating System


Yes; by 2112032

Threshold 85–94%







DRAFT



7.5.101 Alarm 2112034






Severity Major


Operating System


Yes; by 2112032

Threshold 95–100%

System Impact Lower system performance






7.5.102 Alarm 2112035



Description A physical memory free event timed out.

Severity Warning


Operating System


Yes; by 2112032





DRAFT



7.5.103 Alarm 2112036



Description A physical memory free event failed.

Severity Warning


Operating System


Yes; by 2112032





7.5.104 Alarm 2112042





CPU fan

Severity Major


Hardware


No





7.5.105 Alarm 2112043




DRAFT




CPU fan

Severity Major


Hardware


No





7.5.106 Alarm 2112044





Fan

Severity Major


Hardware


No





7.5.107 Alarm 2112045





Fan

Severity Major


DRAFT



Hardware


No





7.5.108 Alarm 2112046





DC power

Severity Major


Hardware


No





7.5.109 Alarm 2112047





DC power

Severity Major


Hardware


No


DRAFT






7.5.110 Alarm 2112048





Fan

Severity Major


Hardware


No





7.5.111 Alarm 2112049





Fan

Severity Major


Hardware


No






DRAFT


7.5.112 Alarm 2112050





Fan

Severity Major


Hardware


No





7.5.113 Alarm 2112051





Fan

Severity Major


Hardware


No





7.5.114 Alarm 2112052




DRAFT




Power supply

Severity Normal


Hardware


No




7.5.115 Alarm 2112053





Power supply

Severity Major


Hardware


Yes; by 2112052





7.5.116 Alarm 2112054





Power supply

Severity Normal


Hardware


DRAFT



No




7.5.117 Alarm 2112055





Power supply

Severity Major


Hardware


Yes; by 2112054





7.5.118 Alarm 2112056





CPU temperature

Severity Major


Hardware


No

Threshold 118 °C


DRAFT






7.5.119 Alarm 2112057





CPU temperature


Severity Major


Hardware


No

Threshold 115 °C





7.5.120 Alarm 2112058





CPU temperature

Severity Minor


Hardware


No


DRAFT


Threshold 110 °C




7.5.121 Alarm 2112059





CPU temperature


Severity Major


Hardware


No

Threshold 118 °C





7.5.122 Alarm 2112060





CPU temperature


Severity Major


Hardware


No

Threshold 115 °C


DRAFT






7.5.123 Alarm 2112061





CPU temperature

Severity Minor


Hardware


No

Threshold 110 °C




7.5.124 Alarm 2112062





Power supply

Severity Major


Hardware


No






DRAFT


7.5.125 Alarm 2112063





Power supply

Severity Major


Hardware


No





7.5.126 Alarm 2112064





Power supply

Severity Major


Hardware


No





7.5.127 Alarm 2112065




DRAFT




Power supply

Severity Major


Hardware


No





7.5.128 Alarm 2112066





CPU fan tray

Severity Normal


Hardware


No




7.5.129 Alarm 2112067





CPU fan tray

Severity Major


Hardware


DRAFT



Yes; by 2112066





7.5.130 Alarm 2112068





CPU fan tray

Severity Major


Hardware


No





7.5.131 Alarm 2112069





CPU fan tray

Severity Normal


Hardware


No





DRAFT


7.5.132 Alarm 2112070





CPU fan tray

Severity Major


Hardware


No





7.5.133 Alarm 2112071





CPU fan tray

Severity Major


Hardware


Yes; by 2112069





7.5.134 Alarm 2112072




DRAFT




CPU fan tray

Severity Normal


Hardware


No




7.5.135 Alarm 2112073





CPU fan tray

Severity Major


Hardware


Yes; by 2112069





7.5.136 Alarm 2112074





CPU fan tray

Severity Major


Hardware


DRAFT



No





7.5.137 Alarm 2112075





CPU fan tray

Severity Major


Hardware


No





7.5.138 Alarm 2112076





Input power

Severity Major


Hardware


No





DRAFT



7.5.139 Alarm 2112077





Input power

Severity Major


Hardware


No





7.5.140 Alarm 2112078





Input power

Severity Major


Hardware


No





7.5.141 Alarm 2112079


DRAFT






Input power

Severity Major


Hardware


No





7.5.142 Alarm 2112080





Power supply

Severity Normal


Hardware


No




7.5.143 Alarm 2112081





Power supply


DRAFT


Severity Major


Hardware


No





7.5.144 Alarm 2112082





Power supply

Severity Major


Hardware


No



Check the power supply LED’s status. If the problem persists,contact Comverse customer support.


7.5.145 Alarm 2112083





Power supply

Severity Major


Hardware


No


DRAFT






7.5.146 Alarm 2112084





Power supply

Severity Normal


Hardware


No




7.5.147 Alarm 2112085





Power supply

Severity Major


Hardware


No






DRAFT


7.5.148 Alarm 2112086





Power supply

Severity Major


Hardware


No





7.5.149 Alarm 2112087





Power supply

Severity Major


Hardware


No





7.5.150 Alarm 2112088




DRAFT




Power supply

Severity Normal


Hardware


No




7.5.151 Alarm 2112089





Power supply

Severity Major


Hardware


No





7.5.152 Alarm 2112090





Power supply

Severity Major


Hardware


DRAFT



No





7.5.153 Alarm 2112091





Power supply

Severity Major


Hardware


No





7.5.154 Alarm 2112092





Power supply

Severity Normal


Hardware


No





DRAFT


7.5.155 Alarm 2112093





Power supply

Severity Major


Hardware


No





7.5.156 Alarm 2112094





Power supply

Severity Major


Hardware


No





7.5.157 Alarm 2112095




DRAFT




Power supply

Severity Major


Hardware


No





7.5.158 Alarm 2112096





CPU temperature


Severity Major


Hardware


No

Threshold 118 °C





7.5.159 Alarm 2112097





DRAFT



CPU temperature


Severity Major


Hardware


No

Threshold 110 °C





7.5.160 Alarm 2112098





CPU temperature

Severity Minor


Hardware


No

Threshold 102 °C




7.5.161 Alarm 2112099





CPU temperature



DRAFT


Severity Major


Hardware


No

Threshold 118 °C





7.5.162 Alarm 2112100





CPU temperature


Severity Major


Hardware


No

Threshold 110 °C





7.5.163 Alarm 2112101





CPU temperature


DRAFT


Severity Minor


Hardware


No

Threshold 102 °C




7.5.164 Alarm 2112102





CPU temperature

Severity Major


Hardware


No





7.5.165 Alarm 2112103





CPU temperature

Severity Major


Hardware


DRAFT



No





7.5.166 Alarm 2112104





CPU temperature

Severity Minor


Hardware


No




7.5.167 Alarm 2112105





CPU temperature

Severity Major


Hardware


No


DRAFT


System Impact Server down due to high temperature. Down time in case ofno server redundancy.




7.5.168 Alarm 2112106





CPU temperature

Severity Major


Hardware


No





7.5.169 Alarm 2112107





CPU temperature

Severity Minor


Hardware


No





DRAFT

7: Application Agent Alarms Server Monitor (SMU) Alarms

7.6 Server Monitor (SMU) AlarmsSearch for the alarm you need by its Specific Problem (Alarm ID).

7.6.1 Alarm 1990001 (The \inetd\ process is not runninganymore)Specific Problem 1990001

Managed Object SMU

Description The \inetd\ process is not running anymore.


daemon

Severity Minor


Operating System


Yes; by 1990001

Threshold 0.5

System Impact Network connectivity problems.


Restart the inetd process by typing:

/usr/sbin/inetd -s &


7.6.2 Alarm 1990001 (The \inetd\ process is running)Specific Problem 1990001

Managed Object SMU

Description The \inetd\ process is running


daemon

Severity Normal


Operating System


No

System Impact None



DRAFT


7.6.3 Alarm 1990002 (CPU utilization (<$VALUE>%)exceeds configured threshold (<$THRESHOLD>%.)Specific Problem 1990002

Managed Object SMU

Description CPU utilization (<$VALUE>%) exceeds configured threshold(<$THRESHOLD>%).


CPU

Severity Major


Capacity


Yes; by 1990002

Threshold 95 within 6 minutes

System Impact System Monitoring may experience high service degradation.




7.6.4 Alarm 1990002 (CPU utilization (<$VALUE>%) is ok)


Managed Object SMU

Description CPU utilization (<$VALUE>%) is ok


CPU

Severity Normal


Capacity


No

System Impact None



DRAFT


7.6.5 Alarm 1990003 (Utilization of file-system<fileSystem> (<$VALUE>%) exceeds configuredthreshold <$THRESHOLD>%.)Specific Problem 1990003

Managed Object SMU

Description Utilization of file-system <fileSystem> (<$VALUE>%) exceedsconfigured threshold <$THRESHOLD>%.


<fileSystem>

Severity Critical


Capacity


Yes; by 1990003

Threshold 95

System Impact System Monitoring will probably experience high servicedegradation.




7.6.6 Alarm 1990003 (Utilization of file-system<fileSystem> (<$VALUE>%) is ok)Specific Problem 1990003

Managed Object SMU

Description Utilization of file-system <fileSystem> (<$VALUE>%) is ok


<fileSystem>

Severity Normal


Capacity


No

System Impact None



DRAFT


7.6.7 Alarm 1990004 (Process table utilization(<$VALUE>%) exceeds configured threshold(<$THRESHOLD>%)Specific Problem 1990004

Managed Object SMU

Description Process table utilization (<$VALUE>%) exceeds configuredthreshold (<$THRESHOLD>%)


process limit

Severity Major


Capacity


Yes; by 1990004

Threshold 80

System Impact May cause unexpected program failure.




7.6.8 Alarm 1990004 (Process table utilization(<$VALUE>%) is ok)


Managed Object SMU

Description Process table utilization (<$VALUE>%) is ok


process limit

Severity Major


Capacity


No

System Impact None



DRAFT


7.6.9 Alarm 1990005 (SWAP Utilization (<$VALUE>%)exceeds configured threshold (<$THRESHOLD>%))Specific Problem 1990005

Managed Object SMU

Description SWAP Utilization (<$VALUE>%) exceeds configuredthreshold (<$THRESHOLD>%)

Additional Info swap_disk

Severity Major


Capacity


Yes; by 1990005

Threshold 80

System Impact System may experience service degradation.




7.6.10 Alarm 1990005 (SWAP Utilization (<$VALUE>%) isok)


Managed Object SMU

Description SWAP Utilization (<$VALUE>%) is ok

Additional Info swap_disk

Severity Normal


Capacity


No

System Impact None


7.6.11 Alarm 1990006 (Distribution files for <$VALUE>node(s) exist)


DRAFT



Managed Object SMU

Description Distribution files for <$VALUE> node(s) exist.


Template

Severity Warning


OpC


Yes; by 1990006

Threshold 1

System Impact None




7.6.12 Alarm 1990006 (Distribution files for 0 node(s) exist)


Managed Object SMU

Description Distribution files for 0 node(s) exist


Template

Severity Normal


OpC


No

System Impact None


7.6.13 Alarm 1990007


Managed Object SMU

Description Distribution still pending after <$OPTION(maxage)> min. for<$MSG_TEXT>


DRAFT



Template

Severity Warning


OpC


No

System Impact System monitoring may experience service degradation.




7.6.14 Alarm 1991001 (Failed login of <user> on <tty>)


Managed Object SMU

Description Failed login of <user> on <tty>


<user> (log only)

Severity Warning


Security


No


7.6.15 Alarm 1991001 (Resource <resource_name> isfaulted)


Managed Object SMU

Description Resource <resource_name> is faulted


SMU Monitor

Severity Critical


High Availability


DRAFT



No

System Impact <resource_name> is not in service and will not be availableuntil the resource is repaired.




7.6.16 Alarm 1991002 (Cron command of <user> with pid<pid> failed (rc = <rc>))Specific Problem 1991002

Managed Object SMU

Description Cron command of <user> with pid <pid> failed (rc = <rc>)


cron (log only)

Severity Major


Job


No


7.6.17 Alarm 1991002 (Group <group_name> is faulted)


Managed Object SMU

Description Group <group_name> is faulted


SMU Monitor

Severity Critical


High Availability


No

System Impact A critical resource is not in service. SMU monitoring will bedegraded; no SMU monitoring or alarms will arrive at theNOC.




DRAFT



7.6.18 Alarm 1991003 (System reboot)


Managed Object SMU

Description System reboot


log only

Severity Warning


Operating System


No

System Impact System service downtime


7.6.19 Alarm 1991003 (Group <group_name> is offline)


Managed Object SMU

Description Group <group_name> is offline


SMU Monitor

Severity Warning


High Availability


Yes; by 1991003

System Impact System downtime while the group is offline.


7.6.20 Alarm 1991004


Managed Object SMU

Description System shutdown started on <tty>


DRAFT



log only

Severity Warning


Operating System


No

System Impact System service down until the SMU is restarted.


7.6.21 Alarm 1991005


Managed Object SMU

Description System shutdown started


log only

Severity Warning


Operating System


No

System Impact System service down until the SMU is restarted.


7.6.22 Alarm 1991006


Managed Object SMU

Description <Message Text>

Severity Minor


Operating System


No



DRAFT


7.6.23 Alarm 1991007


Managed Object SMU

Description Bad logon via FTP


log only

Severity Warning


Security


No


7.6.24 Alarm 1991008


Managed Object SMU

Description System <node> was rebooted by <who>.


<who> (log only)

Severity Warning


Operating System


No

System Impact System service downtime.


7.6.25 Alarm 1991009


Managed Object SMU

Description kernel table \<tablename>\ is full


<tablename>

Severity Warning


DRAFT



Operating System


No

System Impact System service will be degraded.


7.6.26 Alarm 1991010


Managed Object SMU

Description The filesystem \<filesys>\ is nearly full


Filesystem

Severity Warning


Operating System


No

System Impact System service will be degraded.




7.6.27 Alarm 1991011


Managed Object SMU

Description The filesystem \<filesys>\ is full


Filesystem

Severity Critical


Operating System


No

System Impact System service will be degraded and may not be available.




DRAFT



7.6.28 Alarm 1991012


Managed Object SMU

Description NFS server <mach_name> is not responding to NFS requests


NFS subsystem

Severity Warning


Operating System


No


7.6.29 Alarm 1992001


Managed Object SMU

Description <object name> on <object instance> did not respond to snmprequests - agent may be down!


<object name>

Severity Critical


OpC


Yes; by 1992001


7.6.30 Alarm 1992001 (Cleared)


Managed Object SMU

Description <object name> on <object instance> availability was verified!


<object name>


DRAFT


Severity Cleared (Normal)


OpC


No


7.6.31 Alarm 1992003


Managed Object SMU

Description Inventory in SCDB was changed! Initiate Service Topologypopulation

Severity Warning


OpC


Yes; by 1992004


7.6.32 Alarm 1992004 (Log Only)


Managed Object SMU

Description Service Topology was successfully built

Severity Normal


OpC


No


7.6.33 Alarm 1992004


Managed Object SMU

Description Service Topology Population process FAILED!


DRAFT


Severity Major


OpC


Yes; by 1992004

System Impact No system topology.


7.6.34 Alarm 1992005


Managed Object SMU

Description SCDB is not synchronized with Service Topology afterrollback was triggered

Severity Major


OpC


No

System Impact The map will not be synchronized with the SCDB.xmlconfiguration file.


7.6.35 Alarm 1992006


Managed Object SMU

Description rollback can not be done – previous SCDB version could notbe found

Severity Warning


OpC


Yes; by 1992004

System Impact The system will not be returned to its previous state.



DRAFT


7.6.36 Alarm 1992529


Managed Object SMU

Description Your Name Services are performing poorly, likely to be awrong configuration.

The average for the past <number of lookups> lookups took<average number of milliseconds> milliseconds, expect lessthan <threshold value in milliseconds> milliseconds.


Network

Severity Minor


Performance


Yes; by 1992530

System Impact Low service name performance.




7.6.37 Alarm 1992530


Managed Object SMU

Description Your Name Services is performing poorly, possibly a wrongconfiguration.

<Lookup type> of <String being looked up> took <number ofseconds> seconds to resolve.


Network

Severity Warning


Performance


Yes; by 1992529

System Impact Service name may have low performance.





DRAFT


7.6.38 Alarm 1992700


Managed Object SMU

Description ovspmd managed process (<process name>) has terminatedunexpectedly


<process name>

Severity Major


Application


Yes; by ovresume completed without errors, ovspmd resumedprocess (<$4>) outside os the control of the ovresume




7.6.39 Alarm 1992804


Managed Object SMU

Description Reporting system error: <event description> Details: <failuredetails>


Report System

Severity Major


Application


No


7.6.40 Alarm 1992805


Managed Object SMU

Description HP OpenView Data Warehouse is down:<event description>.


DRAFT



Data Warehouse

Severity Major


Application


Yes; by HP OpenView Data Warehouse is back up


7.6.41 Alarm 1992829


Managed Object SMU

Description <event description>


<source of the event>

Severity Major


Application


No

System Impact HP OVO error; system monitoring may not work




7.6.42 Alarm 1992830


Managed Object SMU

Description <event description>



Severity Critical


Application


No


DRAFT


System Impact HP OVO fatal error; System monitoring failure.




7.6.43 Alarm 1992832


Managed Object SMU

Description Command <command name> in response to event<event id> from <node> is not listed as a trusted action in$<$O>V_CONF/trustedCmds.conf



Severity Major


Application


No




7.6.44 Alarm 1992965


Managed Object SMU

Description Node down


<node name>

Severity Critical


Network


Yes; by Node Up

System Impact Node services down.


Restart the node unit.



DRAFT


7.6.45 Alarm 1992972


Managed Object SMU

Description <The string to display>



Severity Normal


Miscellaneous


No


7.6.46 Alarm 1992973


Managed Object SMU




Severity Normal


Miscellaneous


No


7.6.47 Alarm 1992974


Managed Object SMU




Severity Normal


DRAFT



Miscellaneous


No


7.6.48 Alarm 1993097


Managed Object SMU

Description Bad ARP cache entry for <cache entry>


<bad cache entry>

Severity Minor


Network


No

System Impact Connectivity problems because of invalid physical IP in ARPcache.


7.6.49 Alarm 1993098


Managed Object SMU

Description Bad physical address <IP address> returned from node.


<IP address>

Severity Minor


Network


No

System Impact Connectivity problems because of invalid physical IP returnedfrom a node via SNMP.



DRAFT


7.6.50 Alarm 1993101


Managed Object SMU

Description <Node name with incorrect entry> reports address <incorrectIP address> for <interface IP address>, <node name>reported <correct IP address> via SNMP


<interface name>

Severity Minor


Network


No

System Impact This could represent a duplicate IP that impacts the networksystem.


7.6.51 Alarm 1993102


Managed Object SMU

Description <node name1> reports a different physical address for <nodename> than reported by <node name2>, changing from <oldIP address> to <new IP address>


<interface IP address>

Severity Minor


Network


No

System Impact This could represent a duplicate IP that impacts the networksystem.


7.6.52 Alarm 1993108


DRAFT



Managed Object SMU

Description Incorrect routing to node <node name>


<node name>

Severity Minor


Network


No


7.6.53 Alarm 1993115


Managed Object SMU

Description Duplicate IP address: node <node name> reported having<IP address>, but this address was previously detected onnode <node name where IP address is configured>


<IP address>

Severity Critical


Network


No

System Impact Duplicate IP address; network impact


7.6.54 Alarm 1993117


Managed Object SMU

Description Possible device reconfiguration. Interface to IfIndex havebeen remapped. You may need to reconfigure any datacollection on <node name>. The new interface mappings are:<mapping description>


<mapping description>


DRAFT


Severity Normal


Hardware


No


7.6.55 Alarm 1993122


Managed Object SMU

Description Duplicate ifAlias value configured on different ifIndexes -ignoring ifAlias on the following ifIndexes:<ifindexes names>


<ifindexes names>

Severity Major


Hardware


No


7.6.56 Alarm 1993236


Managed Object SMU

Description <application name>: <alert class>: <alert message>



Severity Minor


Application


No


7.6.57 Alarm 1993458


DRAFT



Managed Object SMU

Description pmd lost contact with <application name>: pid <process id>ungracefully disconnected from pmd with <number of events>pending events: <disconnect reason>


<application name>

Severity Major


Application


Yes; by ovresume completed without errors, ovspmd resumedprocess (<$4>) outside os the control of the ovresume




7.6.58 Alarm 1993466


Managed Object SMU

Description pmd detected an event storm of <number of events> eventsover the past <time interval> seconds (<event rate> eventsper second \> threshold of <threshold value>). <total numberof events> events have been sent since the pmd was started.


pmd

Severity Major


Network


No

System Impact System performance may be degraded due to event storm.




7.6.59 Alarm 1993600


Managed Object SMU


DRAFT


Description ovpause failed with errors - <message text>


ovpause

Severity Major


Application


No




7.6.60 Alarm 1993605


Managed Object SMU

Description ovresume completed with errors - <message text>


ovresume

Severity Major


Application


Yes; by ovresume completed without errors




7.6.61 Alarm 1993802


Managed Object SMU

Description Data warehouse maintenance program (<program name>)exited with a non-zero return code of <return code number>and the following message: <message text>


Data Warehouse

Severity Warning


DRAFT



Application


No


7.6.62 Alarm 1994001


Managed Object SMU

Description SMU events download terminated successfully



Backup


No


7.6.63 Alarm 1994002


Managed Object SMU

Description SMU events download terminated with errors on <date>. Logfile is: /backup/ICCeventsDownload.log

Severity Major


Backup


Yes; by 1994001

System Impact Possible impacts:■ No NNM events backup.■ No alarm history backup.




7.6.64 Alarm 1994003


DRAFT



Managed Object SMU

Description SMU backup terminated successfully



Backup


No


7.6.65 Alarm 1994004


Managed Object SMU

Description SMU backup terminated with errors on <date>. Log file is:/backup/ICCbackup.log

Severity Major


Backup


Yes; by 1994003

System Impact Possible impacts:■ No SMU database backup.■ No SMU configuration files backup.




7.6.66 Alarm log only (Node Up)

Specific Problem log only

Managed Object SMU

Description Node Up


<node name>

Severity Normal


DRAFT



log only


No


7.6.67 Alarm log only (ovpause completed without errors)


Managed Object SMU

Description ovpause completed without errors

Severity Normal


<object name>


log only


7.6.68 Alarm log only (ovresume completed without errors)


Managed Object SMU

Description ovresume completed without errors

Severity Normal


<object name>


log only


No


7.6.69 Alarm log only (ovspmd resumed process (<processname>) outside os the control of the ovresume)Specific Problem log only

Managed Object SMU

Description ovspmd resumed process (<process name>) outside os thecontrol of the ovresume


DRAFT


Severity Normal


<object name>


log only


No


7.6.70 Alarm log only (Process (<process name>) resumeditself after timing out and after ovpause/ovresumehas completed.)Specific Problem log only

Managed Object SMU

Description Process (<process name>) resumed itself after timing outand after ovpause/ovresume has timed completed.

Severity Normal


<object name>


log only


No


7.6.71 Alarm log only (HP OpenView Data Warehouse isback up)


Managed Object SMU

Description HP OpenView Data Warehouse is back up

Severity Normal


<event sequence number>


log only


No


DRAFT




DRAFT

7: Application Agent Alarms SPM Agent Alarms

7.7 SPM Agent AlarmsSearch for the alarm you need by its Specific Problem (Alarm ID).

7.7.1 Alarm 1700001


Managed Object SPMA

Description Initialization failure


<Exception information>

Severity Critical


Network


No

System Impact The SPM Agent will not run; domain and batch provisioningare disabled.


The SPM Agent failed to initialize. Fix the problem detailedin the exception information.


7.7.2 Alarm 1700002


Managed Object SPMA

Description Data store connection failure


MIP: <hostname>

or

LDAP: <hostname>

or

DB: <hostname>

Severity Major


Network


Yes; by 1700002


DRAFT


System Impact Domain and batch provisioning will be disabled.


The SPM Agent could not connect to a data store forfive times. Check the database specified in the additionalinformation.


7.7.3 Alarm 1701001


Managed Object SPMA

Description Possible data integrity problem


<Detailed information>

Severity Warning


Application


No

System Impact Possible data integrity problems of the provisioned entity.A provisioning command might have caused data integrityproblems between data stores of the provisioned entity.


7.7.4 Alarm 1701002


Managed Object SPMA

Description Unable to send HTTP request


URL: <full URL>

Severity Major


Network


Yes; by 1701002

System Impact Domain provisioning commands will be disabled.


The SPM Agent could not send an HTTP request to thespecified URL for three times. Check the URL is correct andthe server is up.


DRAFT



7.7.5 Alarm 1702001


Managed Object SPMA

Description Batch file operation error


<Exceptional information>

Severity Major


OS


Yes; by 1702001

System Impact Batch provisioning fails.


7.7.6 Alarm 1702002


Managed Object SPMA

Description Active ToDormant operation error



Severity Major


Application


Yes; by 1702002

System Impact Active ToDormant operation failed



DRAFT

7: Application Agent Alarms SMSC Alarms

7.8 SMSC AlarmsSMSC Alarms are generated by the SMU towards the customer’s NOC. If the SMUis not installed, SMSC SNMP traps are used (see SMSC SNMP Traps Overview,Page 13).

Search for the alarm you need by its Specific Problem (Alarm ID).

7.8.1 Alarm 1140001 (Component down. Terminationreason is UNPLANNED.)Specific Problem 1140001


Description Component down. Termination reason is unplanned


<compIdClassFrom>:<compIdInstanceFrom>

Severity Major


Application


Yes; by 1140001

System Impact The stopped process is not used in the system


Contact Comverse customer support


7.8.2 Alarm 1140001 (Component up. Role is UNKNOWN.)Specific Problem 1140001


Description Component up. Role is unknown



Severity Normal


Application


No




DRAFT


7.8.3 Alarm 1140001 (smsCompDownUnknown.Component down. Termination reason isUNKNOWN)Specific Problem 1140001


Description smsCompDownUnknown. Component down. Terminationreason is unknown.



Severity Warning


Application


Yes; by 1140001





7.8.4 Alarm 1140001 (Log only) (Component up. Role isACTIVE.)Specific Problem 1140001 (Log only)


Description Component up. Role is active.



Severity Normal


Application


No

System Impact The new SMSC process joins the system


7.8.5 Alarm 1140001 (Log only) (Component up. Role isCLUSTERED.)Specific Problem 1140001 (Log only)



DRAFT


Description Component up. Role is clustered



Severity Normal


Application


No



7.8.6 Alarm 1140001 (Log only) (Component up. Role isSTANDALONE.)Specific Problem 1140001 (Log only)


Description Component up. Role is standalone



Severity Normal


Application


No



7.8.7 Alarm 1140001 (Log only) (Component up. Role isSTANDBY.)Specific Problem 1140001 (Log only)


Description Component up. Role is standby



Severity Normal


Application


DRAFT



No



7.8.8 Alarm 1140001 (Log only) (smsCompDownPlanned.Component down. Termination reason is PLANNED).Specific Problem 1140001 (Log only)


Description smsCompDownPlanned. Component down. Terminationreason is PLANNED.



Severity Normal


Application


No

System Impact The stopped process is not used in the system.


7.8.9 Alarm 1140002 (Component changed role toACTIVE.)Specific Problem 1140002


Description Component changed role to active.



Severity Warning


High Availability


Yes; by 1140001

System Impact The active SFE becomes a standby SFE and vice versa.





DRAFT


7.8.10 Alarm 1140002 (Component changed role toCLUSTERED.)Specific Problem 1140002


Description Component changed role to clustered.



Severity Warning


High Availability


Yes; by 1140001





7.8.11 Alarm 1140002 (Component changed role toSTANDALONE.)Specific Problem 1140002


Description Component changed role to standalone.



Severity Warning


High Availability


Yes; by 1140001





7.8.12 Alarm 1140002 (Component changed role toSTANDBY.)Specific Problem 1140002



DRAFT


Description Component changed role to standby



Severity Warning


High Availability


Yes; by 1140001

System Impact The active SFE becomes a standby SFE and vice versa




7.8.13 Alarm 1140002 (Component changed role toUNKNOWN.)Specific Problem 1140002


Description Component changed role to unknown



Severity Warning


High Availability


Yes; by 1140001





7.8.14 Alarm 1140003 (A message burst was encounteredon <name>. Burst size is <burstCurrentSize>.)Specific Problem 1140003


Description A message burst was encontered on <name>. Burst size is<burstCurrentSize>



Severity Major


DRAFT



Performance


Yes; by 1140001

Threshold Severity determined subjectively according to the varbindname

System Impact Performance impact is possible due to the traffic load




7.8.15 Alarm 1140003 (A message burst was encountered.Burst size is <burstCurrentSize>.)Specific Problem 1140003


Description A message burst was encountered. Burst size is<burstCurrentSize>



Severity Major


Performance


Yes; by 1140001





7.8.16 Alarm 1140003 (A message burst was encounteredon <name>. Burst size is <burstCurrentSize>.)Specific Problem 1140003


Description A message burst was encountered on <name>. Burst sizeis <burstCurrentSize>




DRAFT


Severity Critical

Minor

Warning


Performance


Yes; by 1140001

Threshold Severity determined subjectively according to the varbindname

System Impact Performance impact is possible due to the traffic load.




7.8.17 Alarm 1140003 (A message burst was encountered.Burst size is <burstCurrentSize>.)Specific Problem 1140003


Description A message burst was encountered. Burst size is<burstCurrentSize>



Severity Critical

Minor

Warning


Performance


Yes; by 1140001





7.8.18 Alarm 1140003 (Log only)Specific Problem 1140003 (Log only)


Description Burst is terminated


DRAFT




Severity Normal


Performance


No



7.8.19 Alarm 1140004 (Component message rate for license<name> has reached <percent>%.)Specific Problem 1140004


Description Component message rate for license <name> has reached<percent>%.



Severity Critical

Major

Minor

Warning


Capacity


Yes; by 1140001

Threshold ■ Warning: > 60 (default)■ Minor: > 70 (default)■ Major: > 80 (default)■ Critical: > 90 (default)






DRAFT


7.8.20 Alarm 1140004 (Component message rate for license<name> has reached maximum.)Specific Problem 1140004


Description Component message rate for license <name> has reachedmaximum



Severity Critical


Capacity


Yes; by 1140001

Threshold 100 (default)





7.8.21 Alarm 1140004 (Component message rate for license<name> is <percent>%.)



Description Component message rate for license <name> is <percent>%

Severity Unknown


No



7.8.22 Alarm 1140004 (Log only)

Specific Problem 1140004 (Log only)


Description Component message rate for license <name> is <percent>%


DRAFT




Severity Normal


Capacity


No

Threshold <60 (default)



7.8.23 Alarm 1140005Specific Problem 1140005


Description Component successful delivery rate is: <percent>%



Severity Critical

Major

Minor

Warning

Unknown


Capacity


No


System Impact If <compIdClassFrom>:<compIdInstanceFrom>,Performance impact is possible due to the traffic load


If <compIdClassFrom>:<compIdInstanceFrom>, ContactComverse customer support



DRAFT




Description Component successful delivery rate is: <percent>%



Severity Normal


Capacity


No




7.8.25 Alarm 1140006 (Disconnected from<compIdClassTo> <compIdInstanceTo><currentCount> out of <*.totalCount> connectionsare up.)Specific Problem 1140006


Description Disconnected from <compIdClassTo> <compIdInstanceTo>.<currentCount> out of <*.totalCount> connections are up

Severity Unknown


No

System Impact Disconnections in the system might cause service block orperformance impact


7.8.26 Alarm 1140006 (Disconnected from<compIdClassTo>:<compIdInstanceTo>.)Specific Problem 1140006


Description Disconnected from <compIdClassTo>:<compIdInstanceTo>.




DRAFT


Severity Critical

Major

Minor

Warning


Application


Yes; by 11400011140001

Threshold Severity determined both subjectively by the cardinality of thebonds between the components (as defined in varbinds $4and $5) and individually based on client demands





7.8.27 Alarm 1140006 (Log only)



Description Established connection with<compIdClassTo>:<compIdInstanceTo>.



Severity Normal


Application


No





Description The connection to <compIdClassTo>:<compIdInstanceTo>is blocked


DRAFT




Severity Critical

Major

Minor

Warning

Unknown


Application


No

Threshold Warning: > Severity determined both subjectively by thecardinality of the bonds between the components (as definedin varbinds $4 and $5) and individually based on clientdemands

System Impact If <compIdClassFrom>:<compIdInstanceFrom>,Disconnections in the system might cause service block orperformance impact


If <compIdClassFrom>:<compIdInstanceFrom>, ContactComverse customer support




Description The connection to <compIdClassTo>:<compIdInstanceTo>is unblocked.



Severity Normal


Application


No





DRAFT


7.8.30 Alarm 1140008 (The connection focus to<compIdClassTo>:<compIdInstanceTo> switchedto ACTIVE.)Specific Problem 1140008


Description The connection focus to<compIdClassTo>:<compIdInstanceTo>switched to ACTIVE.



Severity Warning


Application


Yes; by 1140001





7.8.31 Alarm 1140008 (The connection focus to<compIdClassTo>:<compIdInstanceTo>switched toSTANDALONE.)Specific Problem 1140008


Description The connection focus to<compIdClassTo>:<compIdInstanceTo>switched to STANDALONE.



Severity Warning


Application


Yes; by 1140001






DRAFT


7.8.32 Alarm 1140008 (The connection focus to<compIdClassTo>:<compIdInstanceTo> switchedto STANDBY.)Specific Problem 1140008


Description The connection focus to<compIdClassTo>:<compIdInstanceTo>switched to STANDBY.



Severity Warning


Application


Yes; by 1140001





7.8.33 Alarm 1140008 (The connection focus to<compIdClassTo>:<compIdInstanceTo>switched toUNKNOWN.)Specific Problem 1140008


Description The connection focus to<compIdClassTo>:<compIdInstanceTo>switched to UNKNOWN



Severity Warning


Application


Yes; by 1140001






DRAFT


7.8.34 Alarm 1140009 (The capacity of the dialog-tablein front of <compIdClassTo><compIdInstanceTo>reached <percent>%.)Specific Problem 1140009


Description The capacity of the dialog-table in front of <compIdClassTo><compIdInstanceTo> reached <percent>%

Severity Unknown


No


7.8.35 Alarm 1140009 (The capacityof the dialog-table in front of<compIdClassTo>:<compIdInstanceTo>reached<percent>%.)Specific Problem 1140009


Description The capacity of the dialog-table in front of<compIdClassTo>:<compIdInstanceTo> reached<percent>%



Severity Critical

Major

Minor

Warning


Capacity


Yes; by 1140001



DRAFT


System Impact Blocking one or more of the dialog tables in the system mightcause service block or performance impact




7.8.36 Alarm 1140009 (Log only)



Description The capacity of the dialog-table in front of<compIdClassTo>:<compIdInstanceTo> reached<percent>%



Severity Normal


Capacity


No


System Impact Blocking one or more of the dialog tables in the system mightcause service block or performance impact


7.8.37 Alarm 1140010 (The Capacity of the DB-table<dbName> reached <percent>%.)Specific Problem 1140010


Description The Capacity of the DB-table <dbName> reached <percent>%



Severity Critical

Major

Minor

Warning


Database


DRAFT



Yes; by 1140001


System Impact Messages DB utilization might cause service block orperformance impact




7.8.38 Alarm 1140010 (The DB-table <dbName> reachedits full capacity.)Specific Problem 1140010


Description The DB-table <dbName> reached its full capacity



Severity Critical


Database


Yes; by 1140001

Threshold 100 (default)







Description The Capacity of the DB-table <dbName> reached <percent>%



Severity Normal


DRAFT



Database


No






Description An integrity problem was discovered in the DB-table<dbName>



Severity Major


Database


Yes; by 1140001







Description <eventMessage>



Severity Critical

Major

Minor

Warning


Application


DRAFT



Yes; by 1140001

Threshold Severity determined subjectively by the alarm, as defined byclient demands







Description <eventMessage>.



Severity Normal


Application


No






Description The CIC-table capacity reached <percent>%



Severity Critical

Major

Minor

Warning


Capacity


Yes; by 1140001


DRAFT









Description The CIC-table capacity reached <percent>%.



Severity Normal


Capacity


No






Description A Trace-file loading failure occurred at: <date>. Cause:<eventMessage>.



Severity Critical

Major

Minor

Warning


Application


DRAFT



Yes; by 1140001








Description The connections between<compIdClassFrom>:<compIdInstanceFrom>and <compIdClassTo>:<compIdInstanceTo> timed out on<count> occasions within <timeFrame> seconds



Severity Critical

Major

Minor

Warning


Application


Yes; by 1140001









DRAFT


Description The connections between<compIdClassFrom>:<compIdInstanceFrom>and <compIdClassTo>:<compIdInstanceTo> timed out on<count> occasions within <timeFrame> seconds



Severity Normal


Application


No






Description The connection utilization between<compIdClassFrom>:<compIdInstanceFrom> and<compIdClassTo>:<compIdInstanceTo> reached <percent>%.



Severity Critical

Major

Minor

Warning


Capacity


Yes; by 1140001

Threshold ■ Critical: > 60 (default)■ Major: > 70 (default)■ Minor: > 80 (default)■ Warning: > 90 (default)






DRAFT




Description The connection utilization between<compIdClassFrom>:<compIdInstanceFrom> and<compIdClassTo>:<compIdInstanceTo> reached <percent>%.



Severity Normal


Capacity


No






Description The DB-table <dbName> was identified as not being the mostup-to-date.



Severity Critical

Major

Minor

Warning


Database


Yes; by 1140001

Threshold Severity determined subjectively by the DB name






DRAFT




Description The DB-table <dbName> was identified as not being the mostup-to-date.



Severity Normal


Database


No

Threshold Severity determined subjectively by the DB name.



7.8.52 Alarm 1141001 (SMS component down due tofailure.)Specific Problem 1141001


Description SMS component down due to failure.

Severity Major


No


7.8.53 Alarm 1141001 (SMS component down formaintenance.)Specific Problem 1141001


Description SMS component down for maintenance.

Severity Normal


No



DRAFT




Description SMS node failure

Severity Major


No


7.8.55 Alarm 1141006 (Disconnected from<compIdClassTo> <compIdInstanceTo>.)Specific Problem 1141006


Description Disconnected from <compIdClassTo> <compIdInstanceTo>

Severity Critical

Major

Minor

Warning

Unknown


No


7.8.56 Alarm 1141006 (Disconnectedfrom <compIdClassTo><compIdInstanceTo>.<currentCount>out of <*.totalCount> connections are up.)Specific Problem 1141006


Description Disconnected from <compIdClassTo> <compIdInstanceTo>.<currentCount> out of <*.totalCount> connections are up


DRAFT


Severity Critical

Major

Minor

Warning

Unknown


No




Description The connection to <compIdClassTo> <compIdInstanceTo>became blocked.

Severity Critical

Major

Minor

Warning

Unknown


No




Description Disconnected from <compIdClassTo>:<compIdInstanceTo>.Currently <currentCount> connections out of <totalCount>are up.



Severity Critical

Major

Warning

Minor


Application


DRAFT



Yes; by 1140001








Description Established connection with<compIdClassTo>:<compIdInstanceTo>.Currently <currentCount> connections out of <totalCount>are up



Severity Normal


Application


No





Description Application is out of connections to <compIdClassTo><compIdInstanceTo>


DRAFT


Severity Critical

Major

Minor

Normal

Warning

Unknown


No


7.8.61 Alarm 1410002 (Association is down <associationname>.)Specific Problem 1410002


Description Association is down <association name>

Severity Warning


No


7.8.62 Alarm 1410002 (Link <number> <name> failed.)Specific Problem 1410002


Description Link <number> <name> failed.

Severity Warning


No


7.8.63 Alarm 1410002 (Link <number> <name> not failed.)Specific Problem 1410002


Description Link <number> <name> not failed.

Severity Normal


No


DRAFT





Description Association is up <association name>

Severity Normal


No


7.8.65 Alarm 1410004 (Link <number> <name> localinhibited.)Specific Problem 1410004


Description Link <number> <name> local inhibited

Severity Warning


No


7.8.66 Alarm 1410004 (Link <number> <name> not localinhibited.)Specific Problem 1410004


Description Link <number> <name> not local inhibited.

Severity Normal


No


7.8.67 Alarm 1410006 (Link <number> <name> not remoteinhibited.)Specific Problem 1410006


Description Link <number> <name> not remote inhibited.


DRAFT


Severity Normal


No


7.8.68 Alarm 1410006 (Link <number> <name> remoteinhibited.)Specific Problem 1410006


Description Link <number> <name> remote inhibited

Severity Warning


No


7.8.69 Alarm 1410008 (Link <number> <name> not remotelyblocked.)Specific Problem 1410008


Description Link <number> <name> not remotely blocked

Severity Normal


No


7.8.70 Alarm 1410008 (Link <number> <name> remotelyblocked.)Specific Problem 1410008


Description Link <number> <name> remotely blocked

Severity Warning


No



DRAFT


7.8.71 Alarm 1410010 (Link <number> <name> locallyblocked.)Specific Problem 1410010


Description Link <number> <name> locally blocked

Severity Warning


No


7.8.72 Alarm 1410010 (Link <number> <name> not locallyblocked.)Specific Problem 1410010


Description Link <number> <name> not locally blocked

Severity Normal


No


7.8.73 Alarm 1410012 (Route set <number> <name>Accessible.)Specific Problem 1410012


Description Route set <number> <name> Accessible

Severity Normal


No


7.8.74 Alarm 1410012 (Route set <number> <name> NOTAccessible.)Specific Problem 1410012


Description Route set <number> <name> not Accessible


DRAFT


Severity Major


No


7.8.75 Alarm 1410014 (Route set <number> <name>Congestion level is <level>.)Specific Problem 1410014


Description Route set <number> <name> Congestion level is <level>

Severity Warning


No


7.8.76 Alarm 1410014 (Route set <number> <name>Congestion level is Low.)Specific Problem 1410014


Description Route set <number> <name> Congestion level is Low

Severity Normal


No


7.8.77 Alarm 1410016 (RSSN <number> RPC <number(s)>ALLOWED.)Specific Problem 1410016


Description RSSN <number> RPC <number(s)> allowed

Severity Normal


No



DRAFT


7.8.78 Alarm 1410016 (RSSN <number> RPC <number(s)>CONGESTED.)Specific Problem 1410016


Description RSSN <number> RPC <number(s)> congested

Severity Warning


No


7.8.79 Alarm 1410016 (RSSN <number> RPC <number(s)>PROHIBITED.)Specific Problem 1410016


Description RSSN <number> RPC <number(s)> prohobited

Severity Warning


No


7.8.80 Alarm 1410016 (RSSN <number> RPC <number(s)>UNEQUIPPED.)Specific Problem 1410016


Description RSSN <number> RPC <number(s)> unequipped

Severity Warning


No


7.8.81 Alarm 1410017 (LSSN <number> ALLOWED.)Specific Problem 1410017


Description LSSN <number> allowed


DRAFT


Severity Normal


No


7.8.82 Alarm 1410017 (LSSN <number> PROHIBITED.)



Description LSSN <number> PROHIBITED.

Severity Warning


No


7.8.83 Alarm 1410017 (LSSN <number> UNEQUIPPED.)



Description LSSN <number> UNEQUIPPED.

Severity Warning


No



DRAFT

7: Application Agent Alarms Possibly Used Traps

7.9 Possibly Used Traps

7.9.1 GenericBackup AlarmsSearch for the alarm you need by its Specific Problem (Alarm ID).

7.9.1.1 Alarm 2113067


Managed Object GenericBackup

Description Generic Backup Message - Normal

Severity Normal


No


7.9.1.2 Alarm 2113068



Description Generic Backup Message - Warning

Severity Warning


No


7.9.1.3 Alarm 2113069



Description Generic Backup Message - Minor

Severity Minor


No


7.9.1.4 Alarm 2113070


DRAFT




Description Generic Backup Message - Major

Severity Major


No


7.9.1.5 Alarm 2113071



Description Generic Backup Message - Critical

Severity Critical


No


7.9.2 GenericHardware AlarmsSearch for the alarm you need by its Specific Problem (Alarm ID).

7.9.2.1 Alarm 2113072


Managed Object GenericHardware

Description Generic Hardware Message - Normal

Severity Normal


No


7.9.2.2 Alarm 2113073



Description Generic Hardware Message - Warning


DRAFT


Severity Warning


No


7.9.2.3 Alarm 2113074



Description Generic Hardware Message - Minor

Severity Minor


No


7.9.2.4 Alarm 2113075



Description Generic Hardware Message - Major

Severity Major


No


7.9.2.5 Alarm 2113076



Description Generic Hardware Message - Critical

Severity Critical


No


7.9.3 GenericOS AlarmsSearch for the alarm you need by its Specific Problem (Alarm ID).


DRAFT


7.9.3.1 Alarm 2113057


Managed Object GenericOS

Description Generic OS Message - Normal

Severity Normal


No


7.9.3.2 Alarm 2113058



Description Generic OS Message - Warning

Severity Warning


No


7.9.3.3 Alarm 2113059



Description Generic OS Message - Minor

Severity Minor


No


7.9.3.4 Alarm 2113060



Description Generic OS Message - Major


DRAFT


Severity Major


No


7.9.3.5 Alarm 2113061



Description Generic OS Message - Critical

Severity Critical


No


7.9.4 SPM Agent AlarmsSearch for the alarm you need by its Specific Problem (Alarm ID).

7.9.4.1 Alarm 1700001


Managed Object SPMA

Description Initialization failure


<Exception information>

Severity Critical


Network


No

System Impact The SPM Agent will not run; domain and batch provisioningwill be disabled.


The SPM Agent failed to initialize. Fix the problem detailedin the exception information.


7.9.4.2 Alarm 1700002


DRAFT



Managed Object SPMA

Description Data store connection failure


MIP: <hostname>

or

LDAP: <hostname>

or

DB: <hostname>

Severity Major


Network


Yes; by 1700002

System Impact Domain and batch provisioning will be disabled.


The SPM Agent could not connect to a data store forfive times. Check the database specified in the additionalinformation.


7.9.4.3 Alarm 1701001


Managed Object SPMA

Description Possible data integrity problem



Severity Warning


Application


No

System Impact Possible data integrity problems of the provisioned entity.A provisioning command might have caused data integrityproblems between data stores of the provisioned entity.


7.9.4.4 Alarm 1701002


DRAFT



Managed Object SPMA

Description Unable to send HTTP request


URL: <full URL>

Severity Major


Network


Yes; by 1701002

System Impact Domain provisioning commands will be disabled.


The SPM Agent could not send an HTTP request to thespecified URL for three times. Check the URL is correct andthe server is up.


7.9.4.5 Alarm 1702001


Managed Object SPMA

Description Batch file operation error


<Exceptional information>

Severity Major


OS


Yes; by 1702001

System Impact Batch provisioning will fail.


7.9.4.6 Alarm 1702002


Managed Object SPMA

Description Active ToDormant operation error



Severity Major


DRAFT



Application


Yes; by 1702002

System Impact Active ToDormant operation will fail



DRAFT

SMSC 4.2 Alarms Rev 0.1

Documents

Transcript of SMSC 4.2 Alarms Rev 0.1