SMSC 4.2 Alarms Rev 0.1

(1)

SMSC 4.2

Alarm Reference Manual

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

(2)

Notice

This document contains proprietary and confidential material of Comverse, Inc. Any unauthorized reproduction, use, or disclosure of this material, or any part thereof, is strictly prohibited. This document 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, no

responsibility is assumed by Comverse, Inc. for the use of this material. Comverse, Inc. reserves the right 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 document shall constitute any contractual commitment whatsoever by Comverse, Inc.

Comverse, its logo, the spark design, Kenan, and Netcentrex are registered trademarks of Comverse Technology, 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 registered trademarks of Comverse, Inc. or its subsidiaries, or their respective owners.

Corporate Headquarters 100 Quannapowitt Parkway Wakefield, MA 01880 USA

(3)

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

(4)

1 Introduction to Alarms

... 1 1.1 Alarms Overview ... 2 1.2 Alarm Agents... 3 1.3 Alarm Format ... 4 1.4 Alarm Notification ... 5

1.5 Unit EMS Access ... 6

1.6 Alarm Fields Description... 7

1.7 Alarms by Unit... 10

2 SMSC SNMP Traps

... 12 2.1 SMSC SNMP Traps Overview... 13 2.2 SMSC Component Traps ... 14 2.3 SMSC Connection Traps ... 16 2.4 SMSC Database Traps ... 19 2.5 SMSC Generic Traps... 20

2.6 SMSC Application Specific Traps ... 21

2.6.1 CCS-EI Traps... 21

2.6.2 OMAP Traps ... 21

2.7 SMSC Trap Varbinds... 23

2.8 Cluster Traps... 26

3 Hardware Agent Alarms

... 29

3.1 Hardware Agent Alarms Overview ... 30

3.2 EMC Alarms... 31

3.2.1 Alarm 3030202 ... 31

3.2.2 Alarm 3030203 ... 31

3.2.3 Alarm 3030204 (Log only) ... 32

3.2.4 Alarm 3030205 (Log only) ... 32

3.2.5 Alarm 3030210 (Log only) ... 33

3.2.6 Alarm 3030211 (Log only) ... 33

3.2.7 Alarm 3030212 (Log only) ... 33

3.2.8 Alarm 3030215 ... 34

3.2.9 Alarm 3030239 ... 34

DRAFT

(5)

Table of Contents

3.2.12 Alarm 3030247 ... 36

3.2.13 Alarm 3030250 ... 36

3.2.14 Alarm 3030251 (Log only) ... 36

3.2.15 Alarm 3030402 (Log only) ... 37

3.2.16 Alarm 3030403 ... 37

3.2.17 Alarm 3030406 (Log only) ... 38

3.2.18 Alarm 3030407 (Log only) ... 38

3.2.19 Alarm 3030408 ... 38

3.2.20 Alarm 3030409 (Log only) ... 39

3.2.21 Alarm 3030410 (Log only) ... 39

3.2.22 Alarm 3030411 ... 40

3.2.23 Alarm 3030412 ... 40

3.2.24 Alarm 3030413 ... 41

3.2.25 Alarm 3030414 ... 41

3.2.26 Alarm 3030415 ... 42

3.2.27 Alarm 3030416 (Log only) ... 42

3.2.28 Alarm 3030501 ... 42 3.2.29 Alarm 3030503 ... 43 3.2.30 Alarm 3030508 ... 44 3.2.31 Alarm 3030509 ... 44 3.2.32 Alarm 3030510 ... 45 3.2.33 Alarm 3030512 ... 45 3.2.34 Alarm 3030513 ... 46 3.2.35 Alarm 3030524 ... 46 3.2.36 Alarm 3030526 ... 47 3.2.37 Alarm 3030528 ... 48 3.2.38 Alarm 3030601 ... 48 3.2.39 Alarm 3030602 ... 49 3.2.40 Alarm 3030603 ... 49 3.2.41 Alarm 3030604 ... 50 3.2.42 Alarm 3030605 ... 50 3.2.43 Alarm 3030607 ... 51 3.2.44 Alarm 3030608 ... 51 3.2.45 Alarm 3030612 ... 52 3.2.46 Alarm 3030613 ... 52 3.2.47 Alarm 3030614 ... 53 3.2.48 Alarm 3030615 ... 53 3.2.49 Alarm 3030616 ... 54 3.2.50 Alarm 3030617 ... 54

SMSC 4.2 Alarm Reference Manual ii

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

(6)

Table of Contents 3.2.51 Alarm 3030618 ... 55 3.2.52 Alarm 3030619 ... 55 3.2.53 Alarm 3030620 ... 56 3.2.54 Alarm 3030622 ... 56 3.2.55 Alarm 3030629 ... 57 3.2.56 Alarm 3030633 ... 57 3.2.57 Alarm 3030639 ... 58 3.2.58 Alarm 3030640 ... 59 3.2.59 Alarm 3030641 ... 59 3.2.60 Alarm 3030653 ... 60 3.2.61 Alarm 3030654 ... 61 3.2.62 Alarm 3030655 ... 61 3.2.63 Alarm 3030656 ... 62 3.2.64 Alarm 3030658 ... 62 3.2.65 Alarm 3030659 ... 63 3.2.66 Alarm 3030660 ... 63 3.2.67 Alarm 3030702 ... 64 3.2.68 Alarm 3030704 ... 64 3.2.69 Alarm 3030709 ... 65 3.2.70 Alarm 3030714 ... 65 3.2.71 Alarm 3030730 ... 66 3.2.72 Alarm 3030731 ... 66 3.2.73 Alarm 3030805 ... 67 3.2.74 Alarm 3030806 ... 67 3.2.75 Alarm 3030809 ... 68 3.2.76 Alarm 3030816 ... 68 3.2.77 Alarm 3030821 ... 69 3.2.78 Alarm 3030822 ... 69 3.2.79 Alarm 3030823 ... 70 3.2.80 Alarm 3030824 ... 70 3.2.81 Alarm 3030825 ... 71

3.2.82 Alarm 3030830 (Log only) ... 71

3.2.83 Alarm 3030832 ... 71

3.2.84 Alarm 3030833 (Log only) ... 72

3.2.85 Alarm 3030834 ... 72

3.2.86 Alarm 3031002 ... 73

3.2.87 Alarm 3031046 ... 73

3.2.88 Alarm 3031110 ... 74

DRAFT

(7)

Table of Contents 3.2.90 Alarm 3031142 ... 75 3.2.91 Alarm 3031172 ... 75 3.2.92 Alarm 3031232 ... 76 3.2.93 Alarm 3032121 ... 77 3.2.94 Alarm 3032122 ... 77 3.2.95 Alarm 3032131 ... 78 3.2.96 Alarm 3032168 ... 78 3.2.97 Alarm 3032169 ... 79 3.2.98 Alarm 3032190 ... 79 3.2.99 Alarm 3032238 ... 80 3.2.100 Alarm 3032239 ... 80 3.2.101 Alarm 3032243 ... 81 3.2.102 Alarm 3032253 ... 81 3.2.103 Alarm 3032403 ... 82 3.2.104 Alarm 3035708 ... 82 3.2.105 Alarm 3035723 ... 83 3.2.106 Alarm 3035749 ... 84 3.2.107 Alarm 3035750 ... 84 3.2.108 Alarm 3037004 ... 85 3.2.109 Alarm 3037061 ... 85 3.2.110 Alarm 3037062 ... 86 3.2.111 Alarm 3037075 ... 86 3.2.112 Alarm 3037076 ... 87 3.2.113 Alarm 3037102 ... 87 3.2.114 Alarm 3037113 ... 88 3.2.115 Alarm 3037122 ... 88 3.2.116 Alarm 3037123 ... 89 3.2.117 Alarm 3037315 ... 89 3.2.118 Alarm 3037339 ... 90 3.2.119 Alarm 3039062 ... 91 3.2.120 Alarm 3039063 ... 91

3.2.121 Alarm 3039065 (Log only) ... 92

3.2.122 Alarm 3039066 (Log only) ... 92

3.2.123 Alarm 3039069 ... 93

3.2.124 Alarm 3039070 ... 93

3.2.125 Alarm 3039071 (Log only) ... 94

3.2.126 Alarm 3039073 (Log only) ... 94

3.2.127 Alarm 3039074 ... 94

3.2.128 Alarm 3039075 (Log only) ... 95

SMSC 4.2 Alarm Reference Manual iv

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

(8)

Table of Contents

3.2.129 Alarm 3039076 (Log only) ... 95

3.2.130 Alarm 3039077 (Log only) ... 96

3.2.131 Alarm 3039079 ... 96

3.2.132 Alarm 3039090 (Log only) ... 96

3.2.133 Alarm 3039091 (Log only) ... 97

3.2.134 Alarm 3039092 (Log only) ... 97

3.2.135 Alarm 3039094 ... 98

3.2.136 Alarm 3039103 ... 98

3.2.137 Alarm 3039134 (Log only) ... 99

3.2.138 Alarm 3039148 ... 99

3.2.139 Alarm 3039149 ... 100

3.2.140 Alarm 3039150 ... 100

3.2.141 Alarm 3039151 (Log only) ... 101

3.2.142 Alarm 3039152 ... 101 3.2.143 Alarm 3039153 ... 101 3.2.144 Alarm 3039154 ... 102 3.2.145 Alarm 3039155 ... 103 3.2.146 Alarm 3039156 ... 103 3.2.147 Alarm 3039157 ... 104 3.2.148 Alarm 3039158 ... 104 3.2.149 Alarm 3039159 ... 105 3.2.150 Alarm 3039160 ... 105 3.2.151 Alarm 3039161 ... 106

3.2.152 Alarm 3039162 (Log only) ... 107

3.2.153 Alarm 3039163 ... 107 3.2.154 Alarm 3039164 ... 108 3.2.155 Alarm 3039165 ... 108 3.2.156 Alarm 3039166 ... 109 3.2.157 Alarm 3039167 ... 110 3.2.158 Alarm 3039169 ... 110 3.2.159 Alarm 3039170 ... 110 3.3 Langley 4 Alarms... 112 3.3.1 Alarm 4090101 ... 112 3.3.2 Alarm 4090102 ... 112 3.3.3 Alarm 4090103 ... 112 3.3.4 Alarm 4090104 ... 113 3.3.5 Alarm 4090105 ... 113 3.3.6 Alarm 4090106 ... 114

DRAFT

(9)

Table of Contents 3.3.8 Alarm 4090108 ... 115 3.3.9 Alarm 4090109 ... 115 3.3.10 Alarm 4090110 ... 116 3.3.11 Alarm 4090111 ... 116 3.3.12 Alarm 4090112 ... 117 3.3.13 Alarm 4090113 ... 117 3.3.14 Alarm 4090114 ... 118 3.3.15 Alarm 4090115 ... 118 3.3.16 Alarm 4090116 ... 118 3.3.17 Alarm 4090117 ... 119 3.3.18 Alarm 4090118 ... 119 3.3.19 Alarm 4090119 ... 120 3.3.20 Alarm 4090120 ... 120 3.3.21 Alarm 4090121 ... 121 3.3.22 Alarm 4090122 ... 121 3.3.23 Alarm 4090123 ... 122 3.3.24 Alarm 4090125 ... 122 3.3.25 Alarm 4090126 ... 123 3.3.26 Alarm 4090127 ... 124 3.3.27 Alarm 4090128 ... 125 3.3.28 Alarm 4090129 ... 125 3.3.29 Alarm 4090130 ... 126 3.3.30 Alarm 4090131 ... 127 3.3.31 Alarm 4090132 ... 128 3.3.32 Alarm 4090133 ... 128 3.3.33 Alarm 4090134 ... 129 3.3.34 Alarm 4090135 ... 129 3.3.35 Alarm 4090136 ... 130 3.3.36 Alarm 4090137 ... 130 3.3.37 Alarm 4090138 ... 131 3.3.38 Alarm 4090139 ... 131 3.3.39 Alarm 4090140 ... 132 3.3.40 Alarm 4090141 ... 132 3.3.41 Alarm 4090142 ... 133 3.3.42 Alarm 4090143 ... 133 3.3.43 Alarm 4090144 ... 134 3.3.44 Alarm 4090145 ... 134 3.3.45 Alarm 4090146 ... 135 3.3.46 Alarm 4090147 ... 135

SMSC 4.2 Alarm Reference Manual vi

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

(10)

Table of Contents 3.3.47 Alarm 4090148 ... 135 3.3.48 Alarm 4090149 ... 136 3.3.49 Alarm 4090150 ... 136 3.3.50 Alarm 4090151 ... 137 3.3.51 Alarm 4090152 ... 138 3.3.52 Alarm 4090153 ... 138 3.3.53 Alarm 4090154 ... 139 3.3.54 Alarm 4090155 ... 139 3.3.55 Alarm 4090156 ... 140 3.3.56 Alarm 4090157 ... 141 3.4 LSI Alarms... 142 3.4.1 Alarm 3080001 ... 142 3.4.2 Alarm 3080003 ... 142 3.4.3 Alarm 3080004 ... 142 3.4.4 Alarm 3080005 ... 143 3.4.5 Alarm 3080006 ... 143 3.4.6 Alarm 3080007 ... 144 3.4.7 Alarm 3080008 ... 144 3.4.8 Alarm 3080009 ... 145 3.4.9 Alarm 3080010 ... 145 3.4.10 Alarm 3080011 ... 145 3.4.11 Alarm 3080012 ... 146 3.4.12 Alarm 3080013 ... 146 3.4.13 Alarm 3080014 ... 147 3.4.14 Alarm 3080019 ... 147 3.4.15 Alarm 3080022 ... 148 3.4.16 Alarm 3080050 ... 148 3.4.17 Alarm 3080051 ... 149 3.4.18 Alarm 3080052 ... 149 3.4.19 Alarm 3080054 ... 149 3.4.20 Alarm 3080059 ... 150 3.4.21 Alarm 3080067 ... 150 3.4.22 Alarm 3080068 ... 151 3.4.23 Alarm 3080069 ... 151 3.4.24 Alarm 3080070 ... 152 3.4.25 Alarm 3080071 ... 152 3.4.26 Alarm 3080073 ... 153 3.4.27 Alarm 3080074 ... 153

DRAFT

(11)

SMSC 4.2 Alarm Reference Manual viii

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

(12)

Table of Contents 3.4.68 Alarm 3080333 ... 171 3.4.69 Alarm 3080334 ... 172 3.4.70 Alarm 3080335 ... 172 3.4.71 Alarm 3080336 ... 173 3.4.72 Alarm 3080337 ... 173 3.4.73 Alarm 3080338 ... 174 3.4.74 Alarm 3080339 ... 174 3.4.75 Alarm 3080340 ... 175 3.4.76 Alarm 3080384 ... 175 3.4.77 Alarm 3080389 ... 175 3.4.78 Alarm 3080392 ... 176 3.4.79 Alarm 3080393 ... 176 3.4.80 Alarm 3080394 ... 177 3.4.81 Alarm 3080400 ... 177 3.4.82 Alarm 3080401 ... 178 3.4.83 Alarm 3080402 ... 178 3.4.84 Alarm 3080405 ... 178 3.4.85 Alarm 3080406 ... 179 3.4.86 Alarm 3080407 ... 179 3.4.87 Alarm 3080408 ... 180 3.4.88 Alarm 3080409 ... 180 3.4.89 Alarm 3080410 ... 180 3.4.90 Alarm 3080411 ... 181 3.4.91 Alarm 3080412 ... 181 3.4.92 Alarm 3080413 ... 182 3.4.93 Alarm 3080414 ... 182 3.4.94 Alarm 3080416 ... 183 3.4.95 Alarm 3080419 ... 183 3.4.96 Alarm 3080420 ... 183 3.4.97 Alarm 3080422 ... 184 3.4.98 Alarm 3080423 ... 184 3.4.99 Alarm 3080424 ... 185 3.4.100 Alarm 3080425 ... 185 3.4.101 Alarm 3080432 ... 186 3.4.102 Alarm 3080434 ... 186 3.4.103 Alarm 3080435 ... 186 3.4.104 Alarm 3080436 ... 187 3.4.105 Alarm 3080437 ... 187

DRAFT

(13)

Table of Contents 3.4.107 Alarm 3080439 ... 188 3.4.108 Alarm 3080440 ... 189 3.4.109 Alarm 3080441 ... 189 3.4.110 Alarm 3080519 ... 189 3.4.111 Alarm 3080520 ... 190 3.4.112 Alarm 3080521 ... 190 3.4.113 Alarm 3080522 ... 191 3.4.114 Alarm 3080644 ... 191 3.4.115 Alarm 3080645 ... 192 3.4.116 Alarm 3080700 ... 192 3.4.117 Alarm 3080701 ... 192 3.4.118 Alarm 3080702 ... 193 3.4.119 Alarm 3080800 ... 193 3.4.120 Alarm 3080801 ... 194 3.4.121 Alarm 3080806 ... 194 3.4.122 Alarm 3080807 ... 194 3.4.123 Alarm 3080808 ... 195 3.4.124 Alarm 3080809 ... 195

3.5 Netra 240/440 Hardware Alarms (OnGuard Agent)... 197

3.5.1 Alarm 2112042 ... 197 3.5.2 Alarm 2112043 ... 197 3.5.3 Alarm 2112044 ... 198 3.5.4 Alarm 2112045 ... 198 3.5.5 Alarm 2112046 ... 198 3.5.6 Alarm 2112047 ... 199 3.5.7 Alarm 2112048 ... 199 3.5.8 Alarm 2112049 ... 200 3.5.9 Alarm 2112050 ... 200 3.5.10 Alarm 2112051 ... 201 3.5.11 Alarm 2112052 ... 201 3.5.12 Alarm 2112053 ... 202 3.5.13 Alarm 2112054 ... 202 3.5.14 Alarm 2112055 ... 202 3.5.15 Alarm 2112056 ... 203 3.5.16 Alarm 2112057 ... 203 3.5.17 Alarm 2112058 ... 204 3.5.18 Alarm 2112059 ... 204 3.5.19 Alarm 2112060 ... 205 3.5.20 Alarm 2112061 ... 205

SMSC 4.2 Alarm Reference Manual x

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

(14)

DRAFT

(15)

Table of Contents 3.5.60 Alarm 2112101 ... 223 3.5.61 Alarm 2112102 ... 223 3.5.62 Alarm 2112103 ... 224 3.5.63 Alarm 2112104 ... 224 3.5.64 Alarm 2112105 ... 225 3.5.65 Alarm 2112106 ... 225 3.5.66 Alarm 2112107 ... 226 3.6 Q-Logic Alarms ... 227 3.6.1 Alarm 2990000 ... 227 3.6.2 Alarm 2990101 ... 227 3.6.3 Alarm 2990102 ... 227 3.6.4 Alarm 2990103 ... 227 3.6.5 Alarm 2990104 ... 228 3.6.6 Alarm 2990105 ... 228 3.6.7 Alarm 2990106 ... 228 3.6.8 Alarm 2990107 ... 229 3.6.9 Alarm 2990108 ... 229 3.6.10 Alarm 2990109 ... 229 3.6.11 Alarm 2990110 ... 230 3.6.12 Alarm 2990111 ... 230 3.6.13 Alarm 2990112 ... 230 3.6.14 Alarm 2990113 ... 230 3.6.15 Alarm 2990114 ... 231 3.6.16 Alarm 2990115 ... 231 3.6.17 Alarm 2990301 ... 231 3.6.18 Alarm 2990401 ... 232 3.6.19 Alarm 2990402 ... 232 3.6.20 Alarm 2990403 ... 232 3.6.21 Alarm 2990404 ... 233 3.6.22 Alarm 2990405 ... 233 3.6.23 Alarm 2990501 ... 233 3.6.24 Alarm 2990502 ... 234 3.6.25 Alarm 2990503 ... 234 3.6.26 Alarm 2990504 ... 234 3.6.27 Alarm 2990505 ... 234

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

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

SMSC 4.2 Alarm Reference Manual xii

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

(16)

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 online

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

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

state.) ... 236 3.6.34 Alarm 2990602 (Q-Logic - Port status has changes to unused with diagnostics

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

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

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

state.) ... 237 3.6.38 Alarm 2990603 (Q-Logic - Port status has changes to ready with bypassed

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

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

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

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

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

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

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

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

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

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

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

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

state.) ... 242

DRAFT

(17)

Table of Contents

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

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

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

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

unknown state.)... 243 3.6.58 Alarm 2990607 (Q-Logic - Port status has changes to initializing with bypassed

state.) ... 244 3.6.59 Alarm 2990607 (Q-Logic - Port status has changes to initializing with diagnostics state.) ... 244 3.6.60 Alarm 2990607 (Q-Logic - Port status has changes to initializing with offline

state.) ... 244 3.6.61 Alarm 2990607 (Q-Logic - Port status has changes to initializing with online

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

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

state.) ... 245 3.6.64 Alarm 2990608 (Q-Logic - Port status has changes to bypass with diagnostics

state.) ... 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 online

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

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

state.) ... 247 3.6.70 Alarm 2990609 (Q-Logic - Port status has changes tools with offline state.) ... 247 3.6.71 Alarm 2990609 (Q-Logic - Port status has changes tools with online state.)... 248 3.6.72 Alarm 2990609 (Q-Logic - Port status has changes tools with unknown state.).. 248 3.6.73 Alarm 2990610 (Q-Logic - Port status has changes to other with bypassed

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

state.) ... 249 3.6.75 Alarm 2990610 (Q-Logic - Port status has changes to other with offline state.).. 249 3.6.76 Alarm 2990610 (Q-Logic - Port status has changes to other with online state.).. 249 3.6.77 Alarm 2990610 (Q-Logic - Port status has changes to other with unknown

state.) ... 250

SMSC 4.2 Alarm Reference Manual xiv

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

(18)

Table of Contents 3.6.78 Alarm 2990701 ... 250 3.6.79 Alarm 2990801 ... 250 3.6.80 Alarm 2991001 ... 250 3.6.81 Alarm 2991002 ... 251 3.6.82 Alarm 2991003 ... 251 3.6.83 Alarm 2991004 ... 251 3.6.84 Alarm 2991005 ... 252 3.6.85 Alarm 2991006 ... 252 3.6.86 Alarm 2991007 ... 252 3.6.87 Alarm 2991008 ... 252 3.6.88 Alarm 2991009 ... 253 3.6.89 Alarm 2991101 ... 253 3.6.90 Alarm 2991102 ... 253 3.6.91 Alarm 2991103 ... 254

4 OS Agent Alarms

... 255

4.1 OS Agent Alarm Overview... 256

4.2 CCS_OS Alarms... 257

4.2.1 Alarm 4087005 ... 257

4.2.2 Alarm 4087006 ... 257

4.2.3 Alarm 4087501 ... 257

4.2.4 Alarm 4087504 ... 258

4.3 SUN OS Alarms (OnGuard Agent) ... 259

4.3.1 Alarm 2112001 ... 259 4.3.2 Alarm 2112002 ... 259 4.3.3 Alarm 2112003 ... 260 4.3.4 Alarm 2112004 ... 260 4.3.5 Alarm 2112005 ... 260 4.3.6 Alarm 2112006 ... 261 4.3.7 Alarm 2112007 ... 261 4.3.8 Alarm 2112008 ... 262 4.3.9 Alarm 2112009 ... 263 4.3.10 Alarm 2112010 ... 263 4.3.11 Alarm 2112011 ... 263 4.3.12 Alarm 2112012 ... 264 4.3.13 Alarm 2112013 ... 264 4.3.14 Alarm 2112014 ... 265

DRAFT

(19)

Table of Contents 4.3.16 Alarm 2112016 ... 266 4.3.17 Alarm 2112017 ... 266 4.3.18 Alarm 2112018 ... 267 4.3.19 Alarm 2112019 ... 267 4.3.20 Alarm 2112020 ... 268 4.3.21 Alarm 2112021 ... 268 4.3.22 Alarm 2112022 ... 268 4.3.23 Alarm 2112023 ... 269 4.3.24 Alarm 2112024 ... 269 4.3.25 Alarm 2112025 ... 270 4.3.26 Alarm 2112026 ... 270 4.3.27 Alarm 2112027 ... 271 4.3.28 Alarm 2112028 ... 271 4.3.29 Alarm 2112029 ... 272 4.3.30 Alarm 2112030 ... 272 4.3.31 Alarm 2112031 ... 273 4.3.32 Alarm 2112032 ... 273 4.3.33 Alarm 2112033 ... 273 4.3.34 Alarm 2112034 ... 274 4.3.35 Alarm 2112035 ... 275 4.3.36 Alarm 2112036 ... 275

4.4 Health Probe Alarms... 276

4.4.1 Alarm 2980001 ... 276

4.4.2 Alarm 2980002 ... 276

4.4.3 Alarm 2980003 ... 277

4.4.4 Alarm 2980004 ... 277

5 Cluster Agent Alarms

... 279

5.1 Cluster Agent Alarms Overview... 280

5.2 SUN Cluster HA Alarms (OnGuard Agent)... 281

5.2.1 Alarm 2113042 ... 281 5.2.2 Alarm 2113043 ... 281 5.2.3 Alarm 2113044 ... 281 5.2.4 Alarm 2113045 ... 282 5.2.5 Alarm 2113046 ... 282 5.2.6 Alarm 2113047 ... 283 5.2.7 Alarm 2113048 ... 283 5.2.8 Alarm 2113049 ... 284

SMSC 4.2 Alarm Reference Manual xvi

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

(20)

Table of Contents

5.2.9 Alarm 2113050 ... 284

5.2.10 Alarm 2113051 ... 285

5.3 Veritas 3.5 Cluster Alarms ... 286

5.3.1 Alarm 2121011 ... 286 5.3.2 Alarm 2121012 ... 286 5.3.3 Alarm 2121013 ... 287 5.3.4 Alarm 2121014 ... 287 5.3.5 Alarm 2121015 ... 288 5.3.6 Alarm 2121016 ... 288 5.3.7 Alarm 2121021 ... 288 5.3.8 Alarm 2121022 ... 289 5.3.9 Alarm 2121023 ... 289 5.3.10 Alarm 2121024 ... 290 5.3.11 Alarm 2121025 ... 290 5.3.12 Alarm 2121026 ... 291 5.3.13 Alarm 2121027 ... 291 5.3.14 Alarm 2121028 ... 292 5.3.15 Alarm 2121029 ... 292 5.3.16 Alarm 2121031 ... 293 5.3.17 Alarm 2121032 ... 293 5.3.18 Alarm 2121033 ... 293 5.3.19 Alarm 2121034 ... 294 5.3.20 Alarm 2121035 ... 294 5.3.21 Alarm 2121036 ... 295 5.3.22 Alarm 2121037 ... 295 5.3.23 Alarm 2121062 ... 296 5.3.24 Alarm 2121081 ... 296 5.3.25 Alarm 2121082 ... 297

6 Networking Agent Alarms

... 298

6.1 Networking Agent Alarms Overview... 299

6.2 Cajun Alarms ... 300 6.2.1 Alarm 2810027 ... 300 6.2.2 Alarm 2810028 ... 300 6.2.3 Alarm 2810044 ... 300 6.2.4 Alarm 2810046 ... 301 6.2.5 Alarm 2810048 ... 301

DRAFT

(21)

Table of Contents 6.2.7 Alarm 2810052 ... 302 6.2.8 Alarm 2810054 ... 302 6.2.9 Alarm 2810079 ... 303 6.2.10 Alarm 2810081 ... 303 6.2.11 Alarm 2810083 ... 303 6.2.12 Alarm 2810085 ... 304 6.2.13 Alarm 2810087 ... 304 6.2.14 Alarm 2810089 ... 305 6.2.15 Alarm 2810091 ... 305 6.2.16 Alarm 2810093 ... 305 6.2.17 Alarm 2810600 ... 306 6.2.18 Alarm 2810602 ... 306 6.2.19 Alarm 2810603 ... 306 6.2.20 Alarm 2810604 ... 307 6.2.21 Alarm 2812315 ... 307 6.2.22 Alarm 2812316 ... 308 6.2.23 Alarm 2812317 ... 308 6.2.24 Alarm 2812318 ... 308 6.3 Others Alarms... 310 6.3.1 Alarm 2820001 ... 310 6.3.2 Alarm 2820002 ... 310 6.3.3 Alarm 2820003 ... 311 6.3.4 Alarm 2820004 ... 311 6.3.5 Alarm 2820005 ... 312 6.3.6 Alarm 2820006 ... 312 6.3.7 Alarm 2820007 ... 313 6.3.8 Alarm 2820008 ... 314 6.3.9 Alarm 2820009 ... 314 6.3.10 Alarm 2820010 ... 315 6.3.11 Alarm 2820011 ... 315 6.3.12 Alarm 2820012 ... 316 6.3.13 Alarm 2820013 ... 316 6.3.14 Alarm 2820014 ... 317 6.3.15 Alarm 2820015 ... 318 6.3.16 Alarm 2820016 ... 318 6.3.17 Alarm 2820017 ... 319 6.3.18 Alarm 2820018 ... 320 6.3.19 Alarm 2820019 ... 320 6.3.20 Alarm 2820020 ... 321

SMSC 4.2 Alarm Reference Manual xviii

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

(22)

Table of Contents 6.3.21 Alarm 2820021 ... 321 6.3.22 Alarm 2820022 ... 322 6.3.23 Alarm 2820023 ... 322 6.3.24 Alarm 2820024 ... 323 6.3.25 Alarm 2820025 ... 323 6.3.26 Alarm 2820026 ... 324 6.3.27 Alarm 2820027 ... 324 6.3.28 Alarm 2820028 ... 325 6.3.29 Alarm 2820029 ... 326 6.3.30 Alarm 2820030 ... 326 6.3.31 Alarm 2820031 ... 327 6.3.32 Alarm 2820032 ... 327 6.3.33 Alarm 2820033 ... 328 6.3.34 Alarm 2820034 ... 328

7 Application Agent Alarms

... 330 7.1 Application Agent Alarms Overview ... 331 7.2 CCS_CC Alarms ... 332 7.2.1 Alarm 1465330 ... 332 7.2.2 Alarm 1465331 ... 332 7.2.3 Alarm 1465350 ... 333 7.2.4 Alarm 1467902 ... 333 7.2.5 Alarm 1469110 ... 334 7.3 GenericDatabase Alarms... 335 7.3.1 Alarm 2113062 ... 335 7.3.2 Alarm 2113063 ... 335 7.3.3 Alarm 2113064 ... 335 7.3.4 Alarm 2113065 ... 335 7.3.5 Alarm 2113066 ... 336 7.4 OMNI Alarms... 337 7.4.1 Alarm 1418001 ... 337 7.4.2 Alarm 1418201 ... 337 7.4.3 Alarm 2113052 ... 338 7.4.4 Alarm 2113053 ... 338 7.4.5 Alarm 2113054 ... 338 7.4.6 Alarm 2113055 ... 338 7.4.7 Alarm 2113056 ... 339

DRAFT

(23)

SMSC 4.2 Alarm Reference Manual xx

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

(24)

DRAFT

(25)

SMSC 4.2 Alarm Reference Manual xxii

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

(26)

DRAFT

(27)

Table of Contents 7.5.157 Alarm 2112095 ... 408 7.5.158 Alarm 2112096 ... 409 7.5.159 Alarm 2112097 ... 409 7.5.160 Alarm 2112098 ... 410 7.5.161 Alarm 2112099 ... 410 7.5.162 Alarm 2112100 ... 411 7.5.163 Alarm 2112101 ... 411 7.5.164 Alarm 2112102 ... 412 7.5.165 Alarm 2112103 ... 412 7.5.166 Alarm 2112104 ... 413 7.5.167 Alarm 2112105 ... 413 7.5.168 Alarm 2112106 ... 414 7.5.169 Alarm 2112107 ... 414 7.6 Server Monitor (SMU) Alarms ... 415 7.6.1 Alarm 1990001 (The \inetd\ process is not running anymore)... 415 7.6.2 Alarm 1990001 (The \inetd\ process is running)... 415 7.6.3 Alarm 1990002 (CPU utilization (<$VALUE>%) exceeds configured threshold

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

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

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

(<$THRESHOLD>%))... 419 7.6.10 Alarm 1990005 (SWAP Utilization (<$VALUE>%) is ok) ... 419 7.6.11 Alarm 1990006 (Distribution files for <$VALUE> node(s) exist) ... 419 7.6.12 Alarm 1990006 (Distribution files for 0 node(s) exist) ... 420 7.6.13 Alarm 1990007 ... 420 7.6.14 Alarm 1991001 (Failed login of <user> on <tty>) ... 421 7.6.15 Alarm 1991001 (Resource <resource_name> is faulted) ... 421 7.6.16 Alarm 1991002 (Cron command of <user> with pid <pid> failed (rc = <rc>)).. 422 7.6.17 Alarm 1991002 (Group <group_name> is faulted)... 422 7.6.18 Alarm 1991003 (System reboot)... 423 7.6.19 Alarm 1991003 (Group <group_name> is offline)... 423 7.6.20 Alarm 1991004 ... 423 7.6.21 Alarm 1991005 ... 424 7.6.22 Alarm 1991006 ... 424

SMSC 4.2 Alarm Reference Manual xxiv

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

(28)

Table of Contents 7.6.23 Alarm 1991007 ... 425 7.6.24 Alarm 1991008 ... 425 7.6.25 Alarm 1991009 ... 425 7.6.26 Alarm 1991010 ... 426 7.6.27 Alarm 1991011 ... 426 7.6.28 Alarm 1991012 ... 427 7.6.29 Alarm 1992001 ... 427 7.6.30 Alarm 1992001 (Cleared) ... 427 7.6.31 Alarm 1992003 ... 428 7.6.32 Alarm 1992004 (Log Only) ... 428 7.6.33 Alarm 1992004 ... 428 7.6.34 Alarm 1992005 ... 429 7.6.35 Alarm 1992006 ... 429 7.6.36 Alarm 1992529 ... 430 7.6.37 Alarm 1992530 ... 430 7.6.38 Alarm 1992700 ... 431 7.6.39 Alarm 1992804 ... 431 7.6.40 Alarm 1992805 ... 431 7.6.41 Alarm 1992829 ... 432 7.6.42 Alarm 1992830 ... 432 7.6.43 Alarm 1992832 ... 433 7.6.44 Alarm 1992965 ... 433 7.6.45 Alarm 1992972 ... 434 7.6.46 Alarm 1992973 ... 434 7.6.47 Alarm 1992974 ... 434 7.6.48 Alarm 1993097 ... 435 7.6.49 Alarm 1993098 ... 435 7.6.50 Alarm 1993101 ... 436 7.6.51 Alarm 1993102 ... 436 7.6.52 Alarm 1993108 ... 436 7.6.53 Alarm 1993115 ... 437 7.6.54 Alarm 1993117 ... 437 7.6.55 Alarm 1993122 ... 438 7.6.56 Alarm 1993236 ... 438 7.6.57 Alarm 1993458 ... 438 7.6.58 Alarm 1993466 ... 439 7.6.59 Alarm 1993600 ... 439 7.6.60 Alarm 1993605 ... 440

DRAFT

(29)

Table of Contents

7.6.62 Alarm 1994001 ... 441 7.6.63 Alarm 1994002 ... 441 7.6.64 Alarm 1994003 ... 441 7.6.65 Alarm 1994004 ... 442 7.6.66 Alarm log only (Node Up)... 442 7.6.67 Alarm log only (ovpause completed without errors) ... 443 7.6.68 Alarm log only (ovresume completed without errors)... 443 7.6.69 Alarm log only (ovspmd resumed process (<process name>) outside os the

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

after ovpause/ovresume has completed.) ... 444 7.6.71 Alarm log only (HP OpenView Data Warehouse is back up) ... 444 7.7 SPM Agent Alarms ... 446 7.7.1 Alarm 1700001 ... 446 7.7.2 Alarm 1700002 ... 446 7.7.3 Alarm 1701001 ... 447 7.7.4 Alarm 1701002 ... 447 7.7.5 Alarm 1702001 ... 448 7.7.6 Alarm 1702002 ... 448 7.8 SMSC Alarms... 449 7.8.1 Alarm 1140001 (Component down. Termination reason is UNPLANNED.) ... 449 7.8.2 Alarm 1140001 (Component up. Role is UNKNOWN.) ... 449 7.8.3 Alarm 1140001 (smsCompDownUnknown. Component down. Termination

reason is UNKNOWN) ... 450 7.8.4 Alarm 1140001 (Log only) (Component up. Role is ACTIVE.) ... 450 7.8.5 Alarm 1140001 (Log only) (Component up. Role is CLUSTERED.)... 450 7.8.6 Alarm 1140001 (Log only) (Component up. Role is STANDALONE.)... 451 7.8.7 Alarm 1140001 (Log only) (Component up. Role is STANDBY.) ... 451 7.8.8 Alarm 1140001 (Log only) (smsCompDownPlanned. Component down.

Termination reason is PLANNED). ... 452 7.8.9 Alarm 1140002 (Component changed role to ACTIVE.) ... 452 7.8.10 Alarm 1140002 (Component changed role to CLUSTERED.)... 453 7.8.11 Alarm 1140002 (Component changed role to STANDALONE.) ... 453 7.8.12 Alarm 1140002 (Component changed role to STANDBY.) ... 453 7.8.13 Alarm 1140002 (Component changed role to UNKNOWN.) ... 454 7.8.14 Alarm 1140003 (A message burst was encountered on <name>. Burst size is

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

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

<burstCurrentSize>.) ... 455

SMSC 4.2 Alarm Reference Manual xxvi

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

(30)

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) ... 456 7.8.19 Alarm 1140004 (Component message rate for license <name> has reached

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

maximum.) ... 458 7.8.21 Alarm 1140004 (Component message rate for license <name> is <percent>%.).. 458 7.8.22 Alarm 1140004 (Log only) ... 458 7.8.23 Alarm 1140005 ... 459 7.8.24 Alarm 1140005 (Log only) ... 460 7.8.25 Alarm 1140006 (Disconnected from <compIdClassTo> <compIdInstanceTo>

<currentCount> out of <*.totalCount> connections are up.)... 460 7.8.26 Alarm 1140006 (Disconnected from <compIdClassTo>:<compIdInstanceTo>.).. 460 7.8.27 Alarm 1140006 (Log only) ... 461 7.8.28 Alarm 1140007 ... 461 7.8.29 Alarm 1140007 (Log only) ... 462 7.8.30 Alarm 1140008 (The connection focus to <compIdClassTo>:<compIdInstanceTo>

switched to ACTIVE.) ... 463 7.8.31 Alarm 1140008 (The connection focus to

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

switched to STANDBY.) ... 464 7.8.33 Alarm 1140008 (The connection focus to

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

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

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

<percent>%.) ... 466 7.8.38 Alarm 1140010 (The DB-table <dbName> reached its full capacity.)... 467 7.8.39 Alarm 1140010 (Log only) ... 467 7.8.40 Alarm 1140011 ... 468 7.8.41 Alarm 1140012 ... 468 7.8.42 Alarm 1140012 (Log only) ... 469 7.8.43 Alarm 1140013 ... 469 7.8.44 Alarm 1140013 (Log only) ... 470 7.8.45 Alarm 1140014 ... 470

(31)

Table of Contents

7.8.48 Alarm 1140016 ... 472 7.8.49 Alarm 1140016 (Log only) ... 473 7.8.50 Alarm 1140017 ... 473 7.8.51 Alarm 1140017 (Log only) ... 474 7.8.52 Alarm 1141001 (SMS component down due to failure.)... 474 7.8.53 Alarm 1141001 (SMS component down for maintenance.) ... 474 7.8.54 Alarm 1141002 ... 475 7.8.55 Alarm 1141006 (Disconnected from <compIdClassTo> <compIdInstanceTo>.).. 475 7.8.56 Alarm 1141006 (Disconnected from <compIdClassTo>

connections are up.) ... 475 7.8.57 Alarm 1141007 ... 476 7.8.58 Alarm 1142006 ... 476 7.8.59 Alarm 1142006 (Log only) ... 477 7.8.60 Alarm 1143006 ... 477 7.8.61 Alarm 1410002 (Association is down <association name>.) ... 478 7.8.62 Alarm 1410002 (Link <number> <name> failed.)... 478 7.8.63 Alarm 1410002 (Link <number> <name> not failed.) ... 478 7.8.64 Alarm 1410003 ... 479 7.8.65 Alarm 1410004 (Link <number> <name> local inhibited.) ... 479 7.8.66 Alarm 1410004 (Link <number> <name> not local inhibited.)... 479 7.8.67 Alarm 1410006 (Link <number> <name> not remote inhibited.)... 479 7.8.68 Alarm 1410006 (Link <number> <name> remote inhibited.)... 480 7.8.69 Alarm 1410008 (Link <number> <name> not remotely blocked.) ... 480 7.8.70 Alarm 1410008 (Link <number> <name> remotely blocked.)... 480 7.8.71 Alarm 1410010 (Link <number> <name> locally blocked.)... 481 7.8.72 Alarm 1410010 (Link <number> <name> not locally blocked.)... 481 7.8.73 Alarm 1410012 (Route set <number> <name> Accessible.)... 481 7.8.74 Alarm 1410012 (Route set <number> <name> NOT Accessible.) ... 481 7.8.75 Alarm 1410014 (Route set <number> <name> Congestion level is <level>.) .... 482 7.8.76 Alarm 1410014 (Route set <number> <name> Congestion level is Low.)... 482 7.8.77 Alarm 1410016 (RSSN <number> RPC <number(s)> ALLOWED.) ... 482 7.8.78 Alarm 1410016 (RSSN <number> RPC <number(s)> CONGESTED.)... 483 7.8.79 Alarm 1410016 (RSSN <number> RPC <number(s)> PROHIBITED.) ... 483 7.8.80 Alarm 1410016 (RSSN <number> RPC <number(s)> UNEQUIPPED.)... 483 7.8.81 Alarm 1410017 (LSSN <number> ALLOWED.) ... 483 7.8.82 Alarm 1410017 (LSSN <number> PROHIBITED.) ... 484 7.8.83 Alarm 1410017 (LSSN <number> UNEQUIPPED.)... 484 7.9 Possibly Used Traps ... 485 7.9.1 GenericBackup Alarms... 485

SMSC 4.2 Alarm Reference Manual xxviii

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

(32)

Table of Contents

7.9.2 GenericHardware Alarms... 486 7.9.3 GenericOS Alarms... 487 7.9.4 SPM Agent Alarms ... 489

(33)

Preface

Target Audience

This information is intended for high-level service engineers and maintenance personnel responsible for resolving alarms and troubleshooting system components.

■

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

■

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

SMSC 4.2 Alarm Reference Manual xxx

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

(34)

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

(35)

1: Introduction to Alarms Alarms Overview

1.1 Alarms Overview

Event monitoring and management in the system is performed by the Site

Management Unit (SMU). The SMU receives SNMP notifications from SNMP agents that monitor the system components, processes the data, and generates alarms according to predefined templates. The alarms are described in:

■

Alarm Format, Page 4

■

Alarm Notification, Page 5

SMSC 4.2 Alarm Reference Manual 2 of 492

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

(36)

1: Introduction to Alarms Alarm Agents

1.2 Alarm Agents

Each system unit hosts a number of agents or subagents that monitor the Managed Elements (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 packages common to several units in the system, for example, all Linux-based units in the system have the same platform subagents with different application agents.

■

Process Control Subagents: Monitor the health of application and service

processes co-hosted on a single unit, update the process state in the process table, report process activation and deactivation to the manager, and collect information on resource consumption of each process, such as CPU and memory 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

(37)

1: Introduction to Alarms Alarm Format

1.3 Alarm Format

The alarms generated and processed by the system are recorded in a specific format with predefined fields.

The format in which the alarms are presented and the predefined fields differ depending on the GUI or the format the alarms are viewed in. The alarms can be viewed as follows:

■

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

■

SMU Alarm Browser Pane: The alarms are displayed in table format in the SMU

GUI 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 by

the 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

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

(38)

1: Introduction to Alarms Alarm Notification

1.4 Alarm Notification

The SMU performs alarm notification in the following ways:

■

Alarm Forwarding: The CMA on the SMU forwards alarms to NOCs using the following supported protocols:

□

SNMP X.733-Compliant Interfaces (SNMP V2 and V3)

□

HIL-SNMP v1

□

HIL-FTP

□

HIL-TC

Each interface supports a specific protocol type, and filtering and mapping rules.

■

Siren Notification: The SMU notifies the Alarm Interface Module (AIM) of the

alarm. 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 the status of the SMU itself.

Parent Topic: Alarms Overview, Page 2 Alarm Format, Page 4

(39)

1: Introduction to Alarms Unit EMS Access

1.5 Unit EMS Access

You can remotely access and manage SMSC units using Element Management Systems (EMS).

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

Table 1: SMSC

Unit 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

Related Information: Alarms by Unit, Page 10

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

(40)

1: Introduction to Alarms Alarm Fields Description

1.6 Alarm Fields Description

Table 2 describes the alarm fields used to define the alarms listed by alarm agent and includes the equivalent field names in the Alarm Notification Table and SMU GUI Browser Pane.

Table 2: Alarm

Fields Alarm Fields Alarm

Notification Table

SMU GUI Browser Pane

Description Specific Problem Specific Problem Application The unique identifier

of the alarm, also called the Alarm ID. Each alarm is identified by a unique seven-digit number. The first three digits are a prefix specific to each type of agent and the next four digits are the alarms which are numbered from 0000 to 9999 (four digits) within the same type of agent.

Managed Object Managed Object Class

Not Included The name of the agent, also called the Managed Object Class (MOC).

Description Alarm Text Message Text The alarm message.

Additional Information

Additional Information

Not Included Additional

information about the alarm, for example, possible causes, variable explanations, and any other relevant information about the alarm.

(41)

Alarm Fields Alarm

Notification Table

SMU GUI Browser Pane

Description Severity Perceived Severity Severity The severity

level of the fault according to ITU-T Recommendation X.733, as follows:

■

Indeterminate (Unknown)

■

Critical

■

Major

■

Minor

■

Warning

■

Cleared (Normal) Message Group Probable Cause)

Probable Cause Msg Grp The Message Group ID based on predefined rules:

■

Hardware

■

Application

■

Communication / Network

■

Operating System

■

Resource / Capacity

■

Performance

■

High Availability

■

Database

■

Miscellaneous Alarm Automatically Cleared

Not Included Not Included Whether the alarm is automatically cleared, and by which Alarm ID. Possible values are:

■

Yes; by <Specific Problem>: The alarm is cleared by another alarm.

■

No: The alarm can only be cleared manually.

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

(42)

Alarm Fields Alarm

Notification Table SMU GUI Browser Pane Description Threshold Threshold Information

Not Included The severity threshold levels, as listed in the Severity row.

System Impact Not Included Not Included The impact the fault situation has on the normal operation of the system.

Recommended Corrective Action

Not Included Not Included The procedures needed to correct the fault situation as recommended by Comverse customer support.

Related Information: Alarms Overview, Page 2 Alarms by Unit, Page 10

(43)

1: Introduction to Alarms Alarms by Unit

1.7 Alarms by Unit

Table 3 lists the units and their corresponding alarm agents in the SMSC system.

Table 3: Alarms

by Unit Unit Component Agent Reference

CCS_CC CCS_CC CCS_CC Alarms, Page 332

OMNI OMNI OMNI Alarms, Page 337

CCS

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 (OnGuard Agent), Page 259

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

Netra 240/440 HW On Guard Netra 240/440 Hardware Alarms (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 Monitor

SMU Server Monitor (SMU)_{Alarms, Page 415} VERITAS VERITAS Veritas 3.5 Cluster Alarms,

Page 286

OS Resources On Guard SUN OS Alarms (OnGuard Agent), Page 259

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

RKVM

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

SMU Server Monitor

SMU Server Monitor (SMU)_{Alarms, Page 415} TRM

VERITAS Cluster 3.5

VERITAS Cluster _{Veritas 3.5 Cluster Alarms,}

Page 286

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

(44)

1: Introduction to Alarms Alarms by Unit

Related Information: Alarms Overview, Page 2 Alarm Fields Description, Page 7

(45)

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

(46)

2: SMSC SNMP Traps SMSC SNMP Traps Overview

2.1 SMSC SNMP Traps Overview

SNMP is a widely used international protocol for the management of networks and network focused IT systems. SNMP is extensible, meaning virtually any kind of device can implement it. SNMP is an application layer protocol, which utilizes a standard 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 device

which interacts with the management station.

■

MIB: Is usually defined as a standard set of statistical and control variables. The precise 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 Application Specific Traps, Page 21

■

OMAP Traps, Page 21

■

SMSC Trap Varbinds, Page 23

■

(47)

2: SMSC SNMP Traps SMSC Component Traps

2.2 SMSC Component Traps

This set of traps describes events that concern the availability of various software components (usually processes) within the SMSC. While these traps are used by SMSC components, including MRE, different components implement different component 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: SMSC Component Traps

Trap Name Description Severity

smsCompUp Indicates that a component has gone up.

When this trap occurs, it should cancel the trap smsCompDown.

Informational

smsCompDown Indicates that a component has terminated.

When this trap occurs, it cancels the trap smsCompUp.

smsCompRoleChanged Indicates that a component has changed its role.

Informational smsCompInBurst Indicates that a component has

identified the beginning of a message-burst situation.

smsCompOutOfBurst Indicates that a component has identified the end of a message-burst situation.

Informational

smsCompMsgRate Indicates that the rate of incoming messages in the reporting component has increased above a monitored threshold of one of the component’s licenses.

smsCompSuccessful DeliveryRate

Indicates that the rate of successful message deliveries in the reporting component has decreased below a monitored threshold.

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

(48)

2: SMSC SNMP Traps SMSC Component Traps

smsCompLicenseExceeded Indicates that the rate of incoming messages in a reporting component has exceeded one of the component’s licenses.

smsTaskTerminated Indicates that an SMSC task has terminated.

This trap contains the following varbinds:

■

taskId: Contains a unique representation of the task in reference

■

startDateTimeandendDateTime: Contains a textual representation of the task start and task termination date

■

terminationStatus: Indicates whether the task has terminated normally or abnormally, and also defines the trap’s severity where:

□

0,1 = informational

□

2 = major

■

terminationReason An enumerated code depicting the exact nature of the task failure (in case theterminationStatus

varbind is set to unplanned). For more information, seeSMSC Trap Varbinds, Page 23.

Related Information:

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

(49)

2: SMSC SNMP Traps SMSC Connection Traps

2.3 SMSC Connection Traps

This set of traps describes events that concern connection availability between various 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 reported from both of the SW components that reside in the ends of a given connection. This concept assures that the state of a connection is well understood by both sides.

Table 5: SMSC Connection Traps

smsConnectionUp Indicates that a connection between two systems was established.

A similar trap is issued from the other component indicating that the two components see each other.

When this occurs, it cancels the trap smsConnectionDown

Informational

smsConnectionDown Indicates that a connection between two systems was disconnected. When this occurs, it cancels the trap smsConectionUp.

smsConnectionBlocked Indicates that a connection between two systems is blocked (but is still connected).

When this occurs, it cancels the trap smsConnectionUnblocked.

smsConnectionUnblocked Indicates that a connection between two systems is unblocked (and is still connected).

When this occurs, it cancels the trap smsConnectionBlocked.

Informational

smsConnectionSwitchedFocus Indicates a connection with a redundant counterpart, to which the focus is always kept to the active component. When this occurs, it cancels the previous appearance of that trap (that bears the same identification var-binds). The CCS-EI sends this trap whenever the CCS it is connected to, performs a change-over.

Informational

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

(50)

smsConnectionTimeOut Indicates that a number of connections, defined by the count varbind, have timed-out between the reporting component and the counterpart in the time-frame, defined by the timeFrame varbind.

■

compIdClassFrom and

compIdInstanceFrom: Indicate the specific process which reports the connection focus switch.

■

compIdClassTo and

CompIdInstanceTo: Indicate the component to which the connection focus was switched. For more information, seeSMSC Trap Varbinds, Page 23.

When this occurs, it cancels the previous appearance of that trap (with the same identification varbinds). smsConnectionStatus Indicates that the state of a connection

between the reporting component and the counterpart has changed.

■

compIdClassFrom and

compIdInstanceFrom: Indicate the specific process which reports the connection loss

■

compIdClassTo and

CompIdInstanceTo: Indicate the component to which the connection focus was switched. For more information, seeSMSC Trap Varbinds, Page 23.

When this occurs, it cancels the previous appearance of that trap (with the same identification varbinds). The trap is cleared by sending it with a

perceivedSeverity=clearvalue.

(51)

smsDialogCapacity Indicates that a dialog table that handles the connection between two components has exceeded a monitored threshold.

smsConnectionUtilization Indicates that the overall utilization of the connection between two components has worsened.

SMSC Component Traps, Page 14 SMSC Database Traps, Page 19 SMSC Generic Traps, Page 20

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

(52)

2: SMSC SNMP Traps SMSC Database Traps

2.4 SMSC Database Traps

Software components, which manage any sort of database, can issue these traps that report the state of the database. The database is identified by its name using the dbName variable binding.

Table 6: SMSC

Database Traps Trap Name Description Severity

smsDbFull Indicates that a database held by the reporting component has filled up completely.

The trap clears any smsDbCapacity trap for the same component

Critical

smsDbIntegrityProblem Indicates that a database held by the reporting component has encountered an integrity problem.

Major

smsDbCapacity Indicates that a database used by the reporting component has exceeded a monitored threshold.

The trap replaces any previous instance of itself and any previous active instance of smsDbFull trap which was issued for the same component.

smsDbNotUpToDate Indicates that a database used by the reporting component is identified as not being the most up-to-date.

SMSC Component Traps, Page 14 SMSC Connection Traps, Page 16 SMSC Generic Traps, Page 20

(53)

2: SMSC SNMP Traps SMSC Generic Traps

2.5 SMSC Generic Traps

These traps are multipurpose and can be used by any SMSC component on any indeterminate case. They contain functional information.

Table 7: SMS

Generic Traps Trap Name Description

smsAllPurposeAlarm Indicates that an event, whose description appears in theeventMessagevariable binding, occurred. For more information, see SMSC Trap Varbinds, Page 23.

smsOperationStatus Indicates that a functional operation within the SMSC system, between the reporting component and its counterpart, has changed its status.

SMSC Component Traps, Page 14 SMSC Connection Traps, Page 16 SMSC Database Traps, Page 19

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

(54)

2: SMSC SNMP Traps SMSC Application Specific Traps

2.6 SMSC Application Specific Traps

These traps are located under enterprises 5271.3.14.1.41 sub-node, which contains a set of branches that accommodate all the application specific events grouped by the application.

Currently the following applications contain a specific MIB structure:

■

100(see CCS-EI Traps, Page 21)

■

200 (see OMAP Traps, Page 21)

SMSC Component Traps, Page 14 SMSC Connection Traps, Page 16 SMSC Database Traps, Page 19 SMSC Generic Traps, Page 20 SMSC Trap Varbinds, Page 23 Cluster Traps, Page 26

2.6.1 CCS-EI Traps

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

Table 8: CCS-EI

Trap Trap Name Description

smsCCSEICicCapacity Indicates that the size of the CIC-table (which is maintained in the CCS but also visible to the CCS-EI) has exceeded a monitored threshold.

The percent varbind indicates the current size of the table (in percents from its total capacity).

For more information, seeSMSC Trap Varbinds, Page 23.

The trap is cleared by sending it once again with a cleared severity.

Parent Topic: SMSC Application Specific Traps, Page 21

Related Information: OMAP Traps, Page 21

2.6.2 OMAP Traps

Table 9 lists the OMAP trap.

(55)

2: SMSC SNMP Traps SMSC Application Specific Traps

Table 9: OMAP

Trap Trap Name Description

smsOMAPLoadTrace Failure Indicates that a failure has occurred during the message-trace records loading to the OMAP-DB.

The date field indicates the time of day when the failure has occurred.

The trap is never cleared.

Parent Topic: SMSC Application Specific Traps, Page 21

Related Information: CCS-EI Traps, Page 21

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

(56)

2: SMSC SNMP Traps SMSC Trap Varbinds

2.7 SMSC Trap Varbinds

Data 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 MIB merely for backward compatibility.

Table 10: Data

Traps Variable Name Description

systemDn A unique name identifying a Managed Object Instance. The field includes the hostname of the managed system, for example, SMSC-1a.

perceivedSeverity The severity of a trap.

compIdClassFrom The class of an SMS component, which has generated a trap. It contains the class identifier of such a component in a string format, for example, SFE, CCS/MAP, SMPP.

compIdInstanceFrom The group and instance of an SMS component which has generated a trap. These identifiers are contained in a period separated string format, for example, 1.2. compIdClassTo The class of an SMS component to which

the trap is referring. It contains the class identifier of such component in a string format, for example, SFE, CCS/MAP, SMPP.

compIdInstanceTo The group and instance of an SMS component to which the trap is referring. These identifiers are contained in a period separated string format, for example, 1.2. dbName The complete name of a database table

or 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 of

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

(57)

Variable Name Description

currentCount 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 the

status of a connection between SMSC components.

smsOperationName A name of an SMSC operation.

clusterSvcOperation Defines the valid values for describing the type of a cluster service operation. smsCorrelationMsgSource The IP or hostname of the component

which generated the original trap. smsCorrelationMsgSeverity The set of PerceivedSeverity values in a

string notation.

smsCorrelationMsgApplication The exact Comverse ID of the event. This is a string notation of a numeric ID (usually 7-digits long).

smsCorrelationMsgObject Concatenation of the smsCompClassFrom and smsCompInstanceFrom. The

separator string is colon (:).

smsCorrelationMsgText The actual normalized message text (as it appears in the SMU). The text contains all the data that appeared in the original varbinds associated with the original trap. smsCorrelationMsgService Exact value as in the systemDn varbind. smsCorrelationMsgKey A unique key containing a concatenation

of several other varbinds.

smsCorrelationMsgAckKey A uniqueness key of the acknowledge event. Similarly to smsCorrelationMsgKey, this varbinds contains a concatenation of several other varbinds.

taskId A name of an SMSC task.

terminationReason A text representing the exact termination reason of either a component or a task. startDateTime Start date and time.

endDateTime End date and time.

SMSC Component Traps, Page 14 SMSC Connection Traps, Page 16 SMSC Database Traps, Page 19

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

(58)

SMSC 4.2 Alarms Rev 0.1

SMSC 4.2

Alarm Reference Manual

Notice

Table of Contents

1

Introduction to Alarms

2

SMSC SNMP Traps

3

Hardware Agent Alarms

DRAFT

DRAFT

DRAFT

DRAFT

DRAFT

DRAFT

DRAFT

4

OS Agent Alarms

DRAFT

5

Cluster Agent Alarms

6

Networking Agent Alarms

DRAFT

7

Application Agent Alarms

DRAFT

DRAFT

DRAFT

DRAFT

Preface

Target Audience

Related Documents

■

■

Introduction to Alarms

1

■

■

■

■

■

■

■

1.1

Alarms Overview

■

■

1.2

Alarm Agents

■

■

■

■

1.3

Alarm Format

■

■

■

1.4

Alarm Notification

■

□

□

□

□

■

1.5

Unit EMS Access

■

■

■

■

■

■

1.6

Alarm Fields Description

■