You are on page 1of 525

DRAFT

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 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.
20042007 Comverse, Inc. All rights reserved.
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
Tel: (781) 246-9000

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

DRAFT
Table of Contents
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

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

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

3.2.10

Alarm 3030240 .................................................................................................................. 35

3.2.11

Alarm 3030241 (Log only) .............................................................................................. 35

SMSC 4.2 Alarm Reference Manual


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

DRAFT

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


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

ii

DRAFT

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

3.2.89

Alarm 3031124 .................................................................................................................. 74

SMSC 4.2 Alarm Reference Manual


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

iii

DRAFT

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


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

iv

DRAFT

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

3.3.7

Alarm 4090107 ................................................................................................................ 114

SMSC 4.2 Alarm Reference Manual


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

DRAFT

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


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

vi

DRAFT

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

3.4.28

Alarm 3080075 ................................................................................................................ 154

SMSC 4.2 Alarm Reference Manual


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

vii

DRAFT

Table of Contents

3.4.29

Alarm 3080096 ................................................................................................................ 154

3.4.30

Alarm 3080098 ................................................................................................................ 155

3.4.31

Alarm 3080099 ................................................................................................................ 155

3.4.32

Alarm 3080128 ................................................................................................................ 155

3.4.33

Alarm 3080129 ................................................................................................................ 156

3.4.34

Alarm 3080130 ................................................................................................................ 156

3.4.35

Alarm 3080131 ................................................................................................................ 157

3.4.36

Alarm 3080132 ................................................................................................................ 157

3.4.37

Alarm 3080133 ................................................................................................................ 158

3.4.38

Alarm 3080134 ................................................................................................................ 158

3.4.39

Alarm 3080135 ................................................................................................................ 158

3.4.40

Alarm 3080136 ................................................................................................................ 159

3.4.41

Alarm 3080144 ................................................................................................................ 159

3.4.42

Alarm 3080145 ................................................................................................................ 160

3.4.43

Alarm 3080146 ................................................................................................................ 160

3.4.44

Alarm 3080147 ................................................................................................................ 161

3.4.45

Alarm 3080150 ................................................................................................................ 161

3.4.46

Alarm 3080151 ................................................................................................................ 162

3.4.47

Alarm 3080152 ................................................................................................................ 162

3.4.48

Alarm 3080153 ................................................................................................................ 162

3.4.49

Alarm 3080157 ................................................................................................................ 163

3.4.50

Alarm 3080176 ................................................................................................................ 163

3.4.51

Alarm 3080177 ................................................................................................................ 164

3.4.52

Alarm 3080178 ................................................................................................................ 164

3.4.53

Alarm 3080179 ................................................................................................................ 165

3.4.54

Alarm 3080180 ................................................................................................................ 165

3.4.55

Alarm 3080181 ................................................................................................................ 166

3.4.56

Alarm 3080320 ................................................................................................................ 166

3.4.57

Alarm 3080321 ................................................................................................................ 167

3.4.58

Alarm 3080322 ................................................................................................................ 167

3.4.59

Alarm 3080323 ................................................................................................................ 167

3.4.60

Alarm 3080324 ................................................................................................................ 168

3.4.61

Alarm 3080325 ................................................................................................................ 168

3.4.62

Alarm 3080326 ................................................................................................................ 169

3.4.63

Alarm 3080327 ................................................................................................................ 169

3.4.64

Alarm 3080328 ................................................................................................................ 170

3.4.65

Alarm 3080329 ................................................................................................................ 170

3.4.66

Alarm 3080331 ................................................................................................................ 171

3.4.67

Alarm 3080332 ................................................................................................................ 171

SMSC 4.2 Alarm Reference Manual


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

viii

DRAFT

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

3.4.106

Alarm 3080438 ................................................................................................................ 188

SMSC 4.2 Alarm Reference Manual


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

ix

DRAFT

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


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

DRAFT

Table of Contents

3.5.21

Alarm 2112062 ................................................................................................................ 206

3.5.22

Alarm 2112063 ................................................................................................................ 206

3.5.23

Alarm 2112064 ................................................................................................................ 207

3.5.24

Alarm 2112065 ................................................................................................................ 207

3.5.25

Alarm 2112066 ................................................................................................................ 208

3.5.26

Alarm 2112067 ................................................................................................................ 208

3.5.27

Alarm 2112068 ................................................................................................................ 208

3.5.28

Alarm 2112069 ................................................................................................................ 209

3.5.29

Alarm 2112070 ................................................................................................................ 209

3.5.30

Alarm 2112071 ................................................................................................................ 210

3.5.31

Alarm 2112072 ................................................................................................................ 210

3.5.32

Alarm 2112073 ................................................................................................................ 211

3.5.33

Alarm 2112074 ................................................................................................................ 211

3.5.34

Alarm 2112075 ................................................................................................................ 211

3.5.35

Alarm 2112076 ................................................................................................................ 212

3.5.36

Alarm 2112077 ................................................................................................................ 212

3.5.37

Alarm 2112078 ................................................................................................................ 213

3.5.38

Alarm 2112079 ................................................................................................................ 213

3.5.39

Alarm 2112080 ................................................................................................................ 214

3.5.40

Alarm 2112081 ................................................................................................................ 214

3.5.41

Alarm 2112082 ................................................................................................................ 215

3.5.42

Alarm 2112083 ................................................................................................................ 215

3.5.43

Alarm 2112084 ................................................................................................................ 215

3.5.44

Alarm 2112085 ................................................................................................................ 216

3.5.45

Alarm 2112086 ................................................................................................................ 216

3.5.46

Alarm 2112087 ................................................................................................................ 217

3.5.47

Alarm 2112088 ................................................................................................................ 217

3.5.48

Alarm 2112089 ................................................................................................................ 218

3.5.49

Alarm 2112090 ................................................................................................................ 218

3.5.50

Alarm 2112091 ................................................................................................................ 218

3.5.51

Alarm 2112092 ................................................................................................................ 219

3.5.52

Alarm 2112093 ................................................................................................................ 219

3.5.53

Alarm 2112094 ................................................................................................................ 220

3.5.54

Alarm 2112095 ................................................................................................................ 220

3.5.55

Alarm 2112096 ................................................................................................................ 221

3.5.56

Alarm 2112097 ................................................................................................................ 221

3.5.57

Alarm 2112098 ................................................................................................................ 222

3.5.58

Alarm 2112099 ................................................................................................................ 222

3.5.59

Alarm 2112100 ................................................................................................................ 223

SMSC 4.2 Alarm Reference Manual


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

xi

DRAFT

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


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

xii

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

3.6.52

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

SMSC 4.2 Alarm Reference Manual


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

xiii

DRAFT

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


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

xiv

DRAFT

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

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

4.3.15

Alarm 2112015 ................................................................................................................ 265

SMSC 4.2 Alarm Reference Manual


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

xv

DRAFT

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

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


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

xvi

DRAFT

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

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

6.2.6

Alarm 2810050 ................................................................................................................ 302

SMSC 4.2 Alarm Reference Manual


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

xvii

DRAFT

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


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

xviii

DRAFT

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

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

7.5

Oracle Database Alarms (OnGuard Agent) .............................................................. 340

SMSC 4.2 Alarm Reference Manual


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

xix

DRAFT

Table of Contents

7.5.1

Alarm 2110001 ................................................................................................................ 340

7.5.2

Alarm 2110002 ................................................................................................................ 340

7.5.3

Alarm 2110003 ................................................................................................................ 340

7.5.4

Alarm 2110004 ................................................................................................................ 341

7.5.5

Alarm 2110005 ................................................................................................................ 341

7.5.6

Alarm 2110006 ................................................................................................................ 342

7.5.7

Alarm 2110007 ................................................................................................................ 342

7.5.8

Alarm 2110008 ................................................................................................................ 342

7.5.9

Alarm 2110009 ................................................................................................................ 343

7.5.10

Alarm 2110010 ................................................................................................................ 343

7.5.11

Alarm 2110011 ................................................................................................................ 344

7.5.12

Alarm 2110012 ................................................................................................................ 344

7.5.13

Alarm 2110013 ................................................................................................................ 345

7.5.14

Alarm 2110014 ................................................................................................................ 345

7.5.15

Alarm 2110015 ................................................................................................................ 345

7.5.16

Alarm 2110016 ................................................................................................................ 346

7.5.17

Alarm 2110017 ................................................................................................................ 346

7.5.18

Alarm 2110018 ................................................................................................................ 347

7.5.19

Alarm 2110019 ................................................................................................................ 347

7.5.20

Alarm 2110020 ................................................................................................................ 348

7.5.21

Alarm 2110021 ................................................................................................................ 348

7.5.22

Alarm 2110022 ................................................................................................................ 348

7.5.23

Alarm 2110023 ................................................................................................................ 349

7.5.24

Alarm 2110024 ................................................................................................................ 349

7.5.25

Alarm 2110025 ................................................................................................................ 350

7.5.26

Alarm 2110026 ................................................................................................................ 350

7.5.27

Alarm 2110027 ................................................................................................................ 351

7.5.28

Alarm 2110028 ................................................................................................................ 351

7.5.29

Alarm 2110029 ................................................................................................................ 352

7.5.30

Alarm 2110030 ................................................................................................................ 352

7.5.31

Alarm 2110031 ................................................................................................................ 353

7.5.32

Alarm 2110032 ................................................................................................................ 353

7.5.33

Alarm 2110033 ................................................................................................................ 353

7.5.34

Alarm 2110034 ................................................................................................................ 354

7.5.35

Alarm 2110035 ................................................................................................................ 354

7.5.36

Alarm 2110036 ................................................................................................................ 355

7.5.37

Alarm 2110037 ................................................................................................................ 355

7.5.38

Alarm 2110038 ................................................................................................................ 355

7.5.39

Alarm 2110039 ................................................................................................................ 356

SMSC 4.2 Alarm Reference Manual


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

xx

DRAFT

Table of Contents

7.5.40

Alarm 2110040 ................................................................................................................ 356

7.5.41

Alarm 2110041 ................................................................................................................ 357

7.5.42

Alarm 2110042 ................................................................................................................ 357

7.5.43

Alarm 2110043 ................................................................................................................ 358

7.5.44

Alarm 2110044 ................................................................................................................ 358

7.5.45

Alarm 2110045 ................................................................................................................ 359

7.5.46

Alarm 2110046 ................................................................................................................ 359

7.5.47

Alarm 2110047 ................................................................................................................ 360

7.5.48

Alarm 2110048 ................................................................................................................ 360

7.5.49

Alarm 2110049 ................................................................................................................ 361

7.5.50

Alarm 2110050 ................................................................................................................ 361

7.5.51

Alarm 2110051 ................................................................................................................ 361

7.5.52

Alarm 2110052 ................................................................................................................ 362

7.5.53

Alarm 2110053 ................................................................................................................ 362

7.5.54

Alarm 2110054 ................................................................................................................ 363

7.5.55

Alarm 2110055 ................................................................................................................ 363

7.5.56

Alarm 2110056 ................................................................................................................ 363

7.5.57

Alarm 2110057 ................................................................................................................ 364

7.5.58

Alarm 2110058 ................................................................................................................ 364

7.5.59

Alarm 2110059 ................................................................................................................ 365

7.5.60

Alarm 2110060 ................................................................................................................ 365

7.5.61

Alarm 2111000 ................................................................................................................ 366

7.5.62

Alarm 2111001 ................................................................................................................ 366

7.5.63

Alarm 2111002 ................................................................................................................ 366

7.5.64

Alarm 2111003 ................................................................................................................ 367

7.5.65

Alarm 2111004 ................................................................................................................ 367

7.5.66

Alarm 2111005 ................................................................................................................ 367

7.5.67

Alarm 2111006 ................................................................................................................ 368

7.5.68

Alarm 2112001 ................................................................................................................ 368

7.5.69

Alarm 2112002 ................................................................................................................ 369

7.5.70

Alarm 2112003 ................................................................................................................ 369

7.5.71

Alarm 2112004 ................................................................................................................ 370

7.5.72

Alarm 2112005 ................................................................................................................ 370

7.5.73

Alarm 2112006 ................................................................................................................ 371

7.5.74

Alarm 2112007 ................................................................................................................ 371

7.5.75

Alarm 2112008 ................................................................................................................ 372

7.5.76

Alarm 2112009 ................................................................................................................ 372

7.5.77

Alarm 2112010 ................................................................................................................ 373

7.5.78

Alarm 2112011 ................................................................................................................ 373

SMSC 4.2 Alarm Reference Manual


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

xxi

DRAFT

Table of Contents

7.5.79

Alarm 2112012 ................................................................................................................ 373

7.5.80

Alarm 2112013 ................................................................................................................ 374

7.5.81

Alarm 2112014 ................................................................................................................ 374

7.5.82

Alarm 2112015 ................................................................................................................ 375

7.5.83

Alarm 2112016 ................................................................................................................ 375

7.5.84

Alarm 2112017 ................................................................................................................ 376

7.5.85

Alarm 2112018 ................................................................................................................ 376

7.5.86

Alarm 2112019 ................................................................................................................ 377

7.5.87

Alarm 2112020 ................................................................................................................ 377

7.5.88

Alarm 2112021 ................................................................................................................ 377

7.5.89

Alarm 2112022 ................................................................................................................ 378

7.5.90

Alarm 2112023 ................................................................................................................ 378

7.5.91

Alarm 2112024 ................................................................................................................ 379

7.5.92

Alarm 2112025 ................................................................................................................ 379

7.5.93

Alarm 2112026 ................................................................................................................ 380

7.5.94

Alarm 2112027 ................................................................................................................ 380

7.5.95

Alarm 2112028 ................................................................................................................ 381

7.5.96

Alarm 2112029 ................................................................................................................ 381

7.5.97

Alarm 2112030 ................................................................................................................ 382

7.5.98

Alarm 2112031 ................................................................................................................ 382

7.5.99

Alarm 2112032 ................................................................................................................ 383

7.5.100

Alarm 2112033 ................................................................................................................ 383

7.5.101

Alarm 2112034 ................................................................................................................ 384

7.5.102

Alarm 2112035 ................................................................................................................ 384

7.5.103

Alarm 2112036 ................................................................................................................ 385

7.5.104

Alarm 2112042 ................................................................................................................ 385

7.5.105

Alarm 2112043 ................................................................................................................ 385

7.5.106

Alarm 2112044 ................................................................................................................ 386

7.5.107

Alarm 2112045 ................................................................................................................ 386

7.5.108

Alarm 2112046 ................................................................................................................ 387

7.5.109

Alarm 2112047 ................................................................................................................ 387

7.5.110

Alarm 2112048 ................................................................................................................ 388

7.5.111

Alarm 2112049 ................................................................................................................ 388

7.5.112

Alarm 2112050 ................................................................................................................ 389

7.5.113

Alarm 2112051 ................................................................................................................ 389

7.5.114

Alarm 2112052 ................................................................................................................ 389

7.5.115

Alarm 2112053 ................................................................................................................ 390

7.5.116

Alarm 2112054 ................................................................................................................ 390

7.5.117

Alarm 2112055 ................................................................................................................ 391

SMSC 4.2 Alarm Reference Manual


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

xxii

DRAFT

Table of Contents

7.5.118

Alarm 2112056 ................................................................................................................ 391

7.5.119

Alarm 2112057 ................................................................................................................ 392

7.5.120

Alarm 2112058 ................................................................................................................ 392

7.5.121

Alarm 2112059 ................................................................................................................ 393

7.5.122

Alarm 2112060 ................................................................................................................ 393

7.5.123

Alarm 2112061 ................................................................................................................ 394

7.5.124

Alarm 2112062 ................................................................................................................ 394

7.5.125

Alarm 2112063 ................................................................................................................ 395

7.5.126

Alarm 2112064 ................................................................................................................ 395

7.5.127

Alarm 2112065 ................................................................................................................ 395

7.5.128

Alarm 2112066 ................................................................................................................ 396

7.5.129

Alarm 2112067 ................................................................................................................ 396

7.5.130

Alarm 2112068 ................................................................................................................ 397

7.5.131

Alarm 2112069 ................................................................................................................ 397

7.5.132

Alarm 2112070 ................................................................................................................ 398

7.5.133

Alarm 2112071 ................................................................................................................ 398

7.5.134

Alarm 2112072 ................................................................................................................ 398

7.5.135

Alarm 2112073 ................................................................................................................ 399

7.5.136

Alarm 2112074 ................................................................................................................ 399

7.5.137

Alarm 2112075 ................................................................................................................ 400

7.5.138

Alarm 2112076 ................................................................................................................ 400

7.5.139

Alarm 2112077 ................................................................................................................ 401

7.5.140

Alarm 2112078 ................................................................................................................ 401

7.5.141

Alarm 2112079 ................................................................................................................ 401

7.5.142

Alarm 2112080 ................................................................................................................ 402

7.5.143

Alarm 2112081 ................................................................................................................ 402

7.5.144

Alarm 2112082 ................................................................................................................ 403

7.5.145

Alarm 2112083 ................................................................................................................ 403

7.5.146

Alarm 2112084 ................................................................................................................ 404

7.5.147

Alarm 2112085 ................................................................................................................ 404

7.5.148

Alarm 2112086 ................................................................................................................ 405

7.5.149

Alarm 2112087 ................................................................................................................ 405

7.5.150

Alarm 2112088 ................................................................................................................ 405

7.5.151

Alarm 2112089 ................................................................................................................ 406

7.5.152

Alarm 2112090 ................................................................................................................ 406

7.5.153

Alarm 2112091 ................................................................................................................ 407

7.5.154

Alarm 2112092 ................................................................................................................ 407

7.5.155

Alarm 2112093 ................................................................................................................ 408

7.5.156

Alarm 2112094 ................................................................................................................ 408

SMSC 4.2 Alarm Reference Manual


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

xxiii

DRAFT

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


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

xxiv

DRAFT

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

7.6.61

Alarm 1993802 ................................................................................................................ 440

SMSC 4.2 Alarm Reference Manual


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

xxv

DRAFT

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


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

xxvi

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

7.8.46

Alarm 1140015 ................................................................................................................ 471

7.8.47

Alarm 1140015 (Log only) ............................................................................................ 471

SMSC 4.2 Alarm Reference Manual


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

xxvii

DRAFT

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>


<compIdInstanceTo>.<currentCount> out of <*.totalCount>
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


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

xxviii

DRAFT

Table of Contents

7.9.2

GenericHardware Alarms............................................................................................. 486

7.9.3

GenericOS Alarms.......................................................................................................... 487

7.9.4

SPM Agent Alarms ........................................................................................................ 489

SMSC 4.2 Alarm Reference Manual


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

xxix

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

Related Documents
For more information, see:

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


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

xxx

DRAFT

Introduction to Alarms

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

1: Introduction to Alarms

1.1

DRAFT

Alarms Overview

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


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

2 of 492

1: Introduction to Alarms

1.2

DRAFT

Alarm Agents

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,

Process Control Subagents: Monitor the health of application and service

Application Subagents: Monitor a specific application or service.

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.

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.

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

SMSC 4.2 Alarm Reference Manual


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

3 of 492

1: Introduction to Alarms

1.3

DRAFT

Alarm Format

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

Alarm List: A comprehensive list of all possible alarms that can be generated by

GUI Browser Pane, from which you can access further details for each alarm.

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

SMSC 4.2 Alarm Reference Manual


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

4 of 492

DRAFT

1: Introduction to Alarms

1.4

Alarm Notification

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

SMSC 4.2 Alarm Reference Manual


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

5 of 492

1: Introduction to Alarms

1.5

DRAFT

Unit EMS Access

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

SMSC 4.2 Alarm Reference Manual


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

6 of 492

1: Introduction to Alarms

1.6

DRAFT

Alarm Fields Description

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
SMU GUI
Notification Table Browser Pane

Specific Problem

Specific Problem

Application

Description
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.

SMSC 4.2 Alarm Reference Manual


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

7 of 492

1: Introduction to Alarms

DRAFT

Alarm Fields Description

Alarm Fields

Alarm
SMU GUI
Notification Table Browser Pane

Description

Severity

Perceived Severity

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

Message Group
Probable Cause)

Alarm
Automatically
Cleared

SMSC 4.2 Alarm Reference Manual


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

Probable Cause

Not Included

Severity

Msg Grp

Not Included

Indeterminate
(Unknown)

Critical
Major
Minor
Warning
Cleared
(Normal)

The Message
Group ID based
on predefined rules:

Hardware

Operating
System

Resource /
Capacity

Performance

Application
Communication /
Network

High Availability
Database
Miscellaneous

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.

8 of 492

DRAFT

1: Introduction to Alarms

Alarm Fields Description

Alarm Fields

Alarm
SMU GUI
Notification Table 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

SMSC 4.2 Alarm Reference Manual


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

9 of 492

DRAFT

1: Introduction to Alarms

1.7

Alarms by Unit

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_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

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

RKVM

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

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

VERITAS Cluster
3.5

VERITAS Cluster

Veritas 3.5 Cluster Alarms,


Page 286

CCS
DSU

TRM

SMSC 4.2 Alarm Reference Manual


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

10 of 492

1: Introduction to Alarms

DRAFT

Alarms by Unit

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

SMSC 4.2 Alarm Reference Manual


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

11 of 492

DRAFT

SMSC SNMP Traps

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

2: SMSC SNMP Traps

2.1

DRAFT

SMSC SNMP Traps Overview

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,

SNMP agent: Is a segment of application code running in a managed device

MIB: Is usually defined as a standard set of statistical and control variables. The

then subsequently processes information returned to the management station.

which interacts with the management station.

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 Generic Traps, Page 20
SMSC Application Specific Traps, Page 21
OMAP Traps, Page 21
SMSC Trap Varbinds, Page 23
Cluster Traps, Page 26

SMSC 4.2 Alarm Reference Manual


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

13 of 492

2: SMSC SNMP Traps

2.2

DRAFT

SMSC Component Traps

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.

Informational

When this trap occurs, it should cancel


the trap smsCompDown.
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.

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.

smsCompMsgRate

Indicates that the rate of incoming


messages in the reporting component
has increased above a monitored
threshold of one of the components
licenses.

smsCompSuccessful
DeliveryRate

Indicates that the rate of successful


message deliveries in the reporting
component has decreased below a
monitored threshold.

SMSC 4.2 Alarm Reference Manual


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

Informational

Informational

14 of 492

2: SMSC SNMP Traps

DRAFT

SMSC Component Traps

Trap Name

Description

smsCompLicenseExceeded

Indicates that the rate of incoming


messages in a reporting component
has exceeded one of the components
licenses.

smsTaskTerminated

Indicates that an SMSC task has


terminated.

Severity

This trap contains the following


varbinds:

taskId: Contains a unique


representation of the task in
reference

startDateTime and endDateTime:


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 traps severity where:

0,1 = informational
2 = major

terminationReason An
enumerated code depicting
the exact nature of the task failure
(in case the terminationStatus
varbind is set to unplanned).

For more information, see SMSC 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

SMSC 4.2 Alarm Reference Manual


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

15 of 492

2: SMSC SNMP Traps

2.3

DRAFT

SMSC Connection Traps

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

Trap Name

Description

Severity

smsConnectionUp

Indicates that a connection between


two systems was established.

Informational

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

Informational

When this occurs, it cancels the trap


smsConnectionBlocked.
smsConnectionSwitchedFocus Indicates a connection with a redundant
counterpart, to which the focus is
always kept to the active component.

Informational

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.

SMSC 4.2 Alarm Reference Manual


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

16 of 492

2: SMSC SNMP Traps

DRAFT

SMSC Connection Traps

Trap Name

Description

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.

Severity

This trap contains the following


varbinds:

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, see SMSC
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.
This trap contains the following
varbinds:

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, see SMSC 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=clear value.

SMSC 4.2 Alarm Reference Manual


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

17 of 492

2: SMSC SNMP Traps

DRAFT

SMSC Connection Traps

Trap Name

Description

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.

Severity

Related Information:
SMSC Component Traps, Page 14
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

SMSC 4.2 Alarm Reference Manual


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

18 of 492

2: SMSC SNMP Traps

2.4

DRAFT

SMSC Database Traps

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.

Critical

The trap clears any smsDbCapacity


trap for the same component
smsDbIntegrityProblem

Indicates that a database held by the


reporting component has encountered
an integrity problem.

smsDbCapacity

Indicates that a database used by the


reporting component has exceeded a
monitored threshold.

Major

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.

Related Information:
SMSC Component Traps, Page 14
SMSC Connection Traps, Page 16
SMSC Generic Traps, Page 20
SMSC Application Specific Traps, Page 21
OMAP Traps, Page 21
SMSC Trap Varbinds, Page 23
Cluster Traps, Page 26

SMSC 4.2 Alarm Reference Manual


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

19 of 492

2: SMSC SNMP Traps

2.5

DRAFT

SMSC Generic Traps

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


the eventMessage variable 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.

Related Information:
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
Cluster Traps, Page 26

SMSC 4.2 Alarm Reference Manual


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

20 of 492

2: SMSC SNMP Traps

2.6

DRAFT

SMSC Application Specific Traps

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)

Related Information:
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, see SMSC 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.

SMSC 4.2 Alarm Reference Manual


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

21 of 492

2: SMSC SNMP Traps

Table 9: OMAP
Trap

DRAFT

SMSC Application Specific Traps

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

SMSC 4.2 Alarm Reference Manual


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

22 of 492

2: SMSC SNMP Traps

2.7

DRAFT

SMSC Trap Varbinds

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.

SMSC 4.2 Alarm Reference Manual


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

23 of 492

2: SMSC SNMP Traps

DRAFT

SMSC Trap Varbinds

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.

Related Information:
SMSC Component Traps, Page 14
SMSC Connection Traps, Page 16
SMSC Database Traps, Page 19

SMSC 4.2 Alarm Reference Manual


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

24 of 492

2: SMSC SNMP Traps

DRAFT

SMSC Trap Varbinds

SMSC Generic Traps, Page 20


SMSC Application Specific Traps, Page 21
OMAP Traps, Page 21
Cluster Traps, Page 26

SMSC 4.2 Alarm Reference Manual


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

25 of 492

2: SMSC SNMP Traps

2.8

DRAFT

Cluster Traps

Cluster Traps
The following traps belong to the SMSC availability subsystem. They cover events
generated 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 reports
the event.
These traps are located under the 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.
Table 11: Cluster
Traps

Trap Name

Description

Severity

smsSvcEnabled

Indicates the cluster leader entity which


enables the service serviceName on
the host memberName. The cluster is
identified by the clusterName varbind.

Informational

For more information, see SMSC Trap


Varbinds, Page 23.
It replaces any active occurrence of the
trap smsSvcDisabled with the same key
values.
smsSvcDisabled

Indicates the cluster leader entity which


disables the service serviceName on
the host memberName.
the trap contains the following varbinds:

clusterName: Identifies the cluster


name

perceivedSeverity: Defined the


trap severity

For more information, see SMSC Trap


Varbinds, Page 23.
It replaces any active occurrence of the
trap smsSvcEnabled with the same key
values.

SMSC 4.2 Alarm Reference Manual


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

26 of 492

2: SMSC SNMP Traps

DRAFT

Trap Name

Description

smsSvcOperationStatus

Indicates that the service (specified


by the varbind) running on host
memberName within the cluster
(specified by the varbind) has identified
a change in the status.

Cluster Traps

Severity

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

For more information, see SMSC Trap


Varbinds, Page 23.
It replaces any active occurrence of the
trap smsSvcEnabled with the same key
values.

SMSC 4.2 Alarm Reference Manual


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

27 of 492

2: SMSC SNMP Traps

DRAFT

Trap Name

Description

smsHostUp

Indicates that the member-host has


been identified as being part of the
cluster.

Cluster Traps

Severity

This trap contains the following


varbinds:

memberName: Indicates the


member host

clusterName: Indicates the cluster


name

For more information, see SMSC Trap


Varbinds, Page 23.
When this trap occurs, it cancels the
trap smsHostDown.
smsHostDown

Indicates that the member-host has


been identified as not being part of the
cluster.
This trap contains the following
varbinds:

memberName: Indicates the


member host

clusterName: Indicates the cluster


name

For more information, see SMSC Trap


Varbinds, Page 23.
When this trap occurs, it cancels the
trap smsHostUp.
Related Information:
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

SMSC 4.2 Alarm Reference Manual


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

28 of 492

DRAFT

Hardware Agent Alarms

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

3: Hardware Agent Alarms

3.1

DRAFT

Hardware Agent Alarms Overview

Hardware Agent Alarms Overview


Hardware Agent alarms monitor the hardware units and generate an alarm if the
unit 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

SMSC 4.2 Alarm Reference Manual


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

30 of 492

3: Hardware Agent Alarms

3.2

DRAFT

EMC Alarms

EMC Alarms
Search 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.

Additional
Information

This occurs when:

A LUN is trespassed. When a trespass occurs, this event


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

A hot spare is invoked. The message indicates on which


drive the LUN is being enabled.

The SP boots, reporting which LUNs it owns (excluding


hot spares).

While hot-spare LUNs are not owned by either SP until


invoked, the message is still reported. Upon boot, each
SP reports a 602 CRU Enabled for each hot-spare LUN.
This lets you know that each SP can see and access the
hot-spare LUN. Ownership is not implied.

A LUN is brought online after a 906 Unit Shutdown event


has occurred.

Severity

Minor

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Recommended
Corrective Action

Contact Comverse customer support.

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

3.2.2

Alarm 3030203
Specific Problem

3030203

Managed Object

EMC

Description

0x603: CRU Unit Rebuild Started.

Additional
Information

FLARE has started a rebuild for a particular LUN contained on


a disk due to a fault in the RAID group.

SMSC 4.2 Alarm Reference Manual


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

31 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030204

System Impact

RAID redundancy for the specific LUN will be lost during the
rebuild.

Recommended
Corrective Action

Contact Comverse customer support.

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

3.2.3

Alarm 3030204 (Log only)


Specific Problem

3030204 (Log only).

Managed Object

EMC

Description

0x604: CRU Unit Rebuild Completed.

Additional
Information

FLARE has completed a rebuild for a particular LUN contained


on a disk.

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

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

3.2.4

Alarm 3030205 (Log only)


Specific Problem

3030205 (Log only).

Managed Object

EMC

Description

0x608: Drive Ready.

Additional
Information

The SP has booted or new drive has been inserted.

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.
SMSC 4.2 Alarm Reference Manual
P/N 10-000-1050 Issue 1 Rev. 0.1

32 of 492

3: Hardware Agent Alarms

3.2.5

DRAFT

EMC Alarms

Alarm 3030210 (Log only)


Specific Problem

3030210 (Log only).

Managed Object

EMC

Description

0x630: Fan Installed.

Additional
Information

The fan/power supply has been reinstalled.

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

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

3.2.6

Alarm 3030211 (Log only)


Specific Problem

3030211 (Log only).

Managed Object

EMC

Description

0x631: VSC Installed.

Additional
Information

The fan/power supply module has been reinserted.

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

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

3.2.7

Alarm 3030212 (Log only)


Specific Problem

3030212 (Log only).

Managed Object

EMC

Description

0x639: System Cache Enabled.

Additional
Information

The system cache has been enabled.

Severity

Normal

SMSC 4.2 Alarm Reference Manual


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

33 of 492

3: Hardware Agent Alarms

DRAFT

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

EMC Alarms

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

3.2.8

Alarm 3030215
Specific Problem

3030215

Managed Object

EMC

Description

0x654: Cache Dumping.

Additional
Information

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

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030212

System Impact

System performance might be impacted.

Recommended
Corrective Action

Either identify the problem and fix it, or wait for the storage
system to fix it (for example, wait for the SPS to reach full
charge or for the vault disks to be rebuilt). When the fault no
longer exists, the storage system automatically re-enables
storage system write caching.

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

3.2.9

Alarm 3030239
Specific Problem

3030239

Managed Object

EMC

Description

0x6c0: BE (Backend) Fibre Loop Error.

Additional
Information

The back-end (storage array) is faulty.

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030241

SMSC 4.2 Alarm Reference Manual


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

34 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

System Impact

FC connectivity to the back-end will be lost.

Recommended
Corrective Action

Check the back-end loop cables. Check connections from


the SP to the DAE.

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

3.2.10

Alarm 3030240
Specific Problem

3030240

Managed Object

EMC

Description

0x6C1: BE (Backend) Fibre Loop Down.

Additional
Information

The back-end (storage array) has a fiber loop problem. This


event is usually caused by a hardware problem, for example,
a disk module or LCC module was pulled out, or a CLARiiON
array powered down or rebooted.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030241

System Impact

System performance might be impacted.

Recommended
Corrective Action

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

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

3.2.11

Alarm 3030241 (Log only)


Specific Problem

3030241 (Log only).

Managed Object

EMC

Description

0x6C3: BE (Backend) Fibre Loop Operational.

Additional
Information

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

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

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

SMSC 4.2 Alarm Reference Manual


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

35 of 492

3: Hardware Agent Alarms

3.2.12

DRAFT

EMC Alarms

Alarm 3030247
Specific Problem

3030247

Managed Object

EMC

Description

0x6e1: Front-end Fibre Loop Event.

Additional
Information

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

Severity

Minor

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030251

System Impact

Connectivity between the host and the storage system might


be lost.

Recommended
Corrective Action

Check the status of the link.

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

3.2.13

Alarm 3030250
Specific Problem

3030250

Managed Object

EMC

Description

0x6e4: Fibre Channel Loop Down.

Additional
Information

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


impacted.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030251

System Impact

Loss of redundancy on front-end FC connectivity will occur,


and system performance might be impacted.

Recommended
Corrective Action

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

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

3.2.14

Alarm 3030251 (Log only)

SMSC 4.2 Alarm Reference Manual


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

36 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

Specific Problem

3030251 (Log only).

Managed Object

EMC

Description

0x6e5: Fibre Channel Loop Up.

Additional
Information

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

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

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

3.2.15

Alarm 3030402 (Log only)


Specific Problem

3030402 (Log only).

Managed Object

EMC

Description

0x714: Read cache enabled.

Additional
Information

Read caching has been enabled by the administrator.

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

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

3.2.16

Alarm 3030403
Specific Problem

3030403

Managed Object

EMC

Description

0x715: Read cache disabled.

Additional
Information

Read caching has been disabled by the administrator.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030402

SMSC 4.2 Alarm Reference Manual


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

37 of 492

3: Hardware Agent Alarms

DRAFT

System Impact

System performance might be impacted.

Recommended
Corrective Action

Enable the read cache.

EMC Alarms

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

3.2.17

Alarm 3030406 (Log only)


Specific Problem

3030406 (Log only).

Managed Object

EMC

Description

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

Additional
Information

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

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

This event is logged for reference and troubleshooting and


cannot be cleared.

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

3.2.18

Alarm 3030407 (Log only)


Specific Problem

3030407 (Log only).

Managed Object

EMC

Description

0x761: Power Supply B on xPE is restored.

Additional
Information

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

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

This event is logged for reference and troubleshooting and


cannot be cleared.

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

3.2.19

Alarm 3030408

SMSC 4.2 Alarm Reference Manual


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

38 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

Specific Problem

3030408

Managed Object

EMC

Description

0x768: A fan is faulted on the xPE.

Additional
Information

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

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3039090, 3039091

System Impact

System performance might be impacted.

Recommended
Corrective Action

Replace or reinsert the fan module.

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

3.2.20

Alarm 3030409 (Log only)


Specific Problem

3030409 (Log only).

Managed Object

EMC

Description

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

Additional
Information

Power has been restored to power supply A on the xPE


(CX700).

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

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

3.2.21

Alarm 3030410 (Log only)


Specific Problem

3030410 (Log only).

Managed Object

EMC

Description

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

Additional
Information

Power has been restored to power supply B on the xPE


(CX700).

Severity

Normal

SMSC 4.2 Alarm Reference Manual


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

39 of 492

3: Hardware Agent Alarms

DRAFT

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

EMC Alarms

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

3.2.22

Alarm 3030411
Specific Problem

3030411

Managed Object

EMC

Description

0x775: xPE PSA Power Fail Testing.

Additional
Information

The power to power supply A has been interrupted and SPS


testing is in progress.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030409

System Impact

Power supply redundancy might be lost.

Recommended
Corrective Action

Determine if this is a part of SPS testing.

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

3.2.23

Alarm 3030412
Specific Problem

3030412

Managed Object

EMC

Description

0x776: xPE PSB Power Fail Testing.

Additional
Information

The power to power supply B has been interrupted and SPS


testing is in progress.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030410

System Impact

Power supply redundancy might be lost.

Recommended
Corrective Action

Determine if this is a part of SPS testing.

For a detailed description of these rows, see Alarm Fields Description, Page 7.
SMSC 4.2 Alarm Reference Manual
P/N 10-000-1050 Issue 1 Rev. 0.1

40 of 492

3: Hardware Agent Alarms

3.2.24

DRAFT

EMC Alarms

Alarm 3030413
Specific Problem

3030413

Managed Object

EMC

Description

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

Additional
Information

Power to power supply A in the xPE has been interrupted.


This also indicates that the unit is being supplied backup
power by the SPS (CX700).

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030409

System Impact

Loss of power supply redundancy will occur, and performance


will be impacted due to cache disabling.

Recommended
Corrective Action

Reinsert/replace power supply A on the DPE.

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

3.2.25

Alarm 3030414
Specific Problem

3030414

Managed Object

EMC

Description

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

Additional
Information

Power to power supply B in the xPE has been interrupted.


This also indicates that the unit is being supplied backup
power by the SPS (CX700).

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030410

System Impact

Loss of power supply redundancy will occur, and performance


will be impacted due to cache disabling.

Recommended
Corrective Action

Reinsert/replace power supply B on the DPE.

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

SMSC 4.2 Alarm Reference Manual


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

41 of 492

3: Hardware Agent Alarms

3.2.26

DRAFT

EMC Alarms

Alarm 3030415
Specific Problem

3030415

Managed Object

EMC

Description

0x78b: Drive was physically removed from the slot.

Additional
Information

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

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030416

System Impact

System performance might be impacted.

Recommended
Corrective Action

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

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

3.2.27

Alarm 3030416 (Log only)


Specific Problem

3030416 (Log only).

Managed Object

EMC

Description

0x78c: Drive was physically inserted into the slot.

Additional
Information

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

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

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

3.2.28

Alarm 3030501
Specific Problem

3030501

Managed Object

EMC

Description

0x801: Soft SCSI Error.

SMSC 4.2 Alarm Reference Manual


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

42 of 492

3: Hardware Agent Alarms

Additional
Information

DRAFT

EMC Alarms

A SCSI operation failed and needed to be retried. This error


indicates that the retry succeeded.
NOTE: 801 events are not strictly confined to being
disk-related problems. Soft SCSI errors can indicate a bad
LCC cable or an LCC not handling back-end bus loop noise
correctly. Look at the extended status in the CLARiiON log for
the affected drive to determine the cause of the event.
This event is logged for reference and troubleshooting and
cannot be cleared.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

If there are recent occurrences of the message, the system


might have a problem with the back-end loop This might cause
loss of connectivity redundancy and impact performance.

Recommended
Corrective Action

Continue monitoring the system for further events. The drive


should only be considered for replacement if the errors recur
frequently.

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

3.2.29

Alarm 3030503
Specific Problem

3030503

Managed Object

EMC

Description

0x803: Recommend Disk Replacement.

Additional
Information

The drives predictive failure analysis has determined that the


drive is likely to fail soon. This event is logged for reference
and troubleshooting and cannot be cleared.

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Possible data loss.

Recommended
Corrective Action

Replace the drive as soon as possible.

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

SMSC 4.2 Alarm Reference Manual


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

43 of 492

3: Hardware Agent Alarms

3.2.30

DRAFT

EMC Alarms

Alarm 3030508
Specific Problem

3030508

Managed Object

EMC

Description

0x820: Soft Media Error.

Additional
Information

The drive in question encountered an error trying to read its


data. The extended status of 0x05 for the event is significant
in that it means that more than one bit was flipped, and
that the data cannot be recovered from the drives SMART
technology. FLARE attempts to rebuild the data from the parity
of the RAID group. This is significant in that if the RAID group
is already degraded, for example, if a rebuild is ongoing,
then FLARE is forced to invalidate that data stripe because
it cannot be rebuilt. Some amount of soft media errors are
expected per drive, but recurring soft media errors could
be a sign that the drive in question might be going bad and
should be replaced. This event is logged for reference and
troubleshooting and cannot be cleared.

Severity

Warning

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

The disk might fail.

Recommended
Corrective Action

Drive replacement is usually recommended in instances when


an amber LED on the hard drives is on, which indicates
that the drive is not operating normally. Replacement is also
recommended when recommend drive replacement (event
code 803) has been logged, or if one or more 920 Hard Media
Errors have occurred on a Fiber Channel drive. The status of
the RAID group to which the drive belongs should be checked
to make sure that replacing the drive does not result in a more
problematic array condition.

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

3.2.31

Alarm 3030509
Specific Problem

3030509

Managed Object

EMC

Description

0x840: Data Sector Invalidated.

SMSC 4.2 Alarm Reference Manual


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

44 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

Additional
Information

The checksum error and block matches the FLARE RAID


invalid sector format. This means that at some time in the
past, RAID invalidated this sector because of another adjacent
checksum error or media error in the stripe. This could occur
because of a media error or checksum error on a different
drive during a degraded condition or rebuild, or this could
occur due to detection of multiple (checksum/media) errors
on a nondegraded unit.

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Data loss might occur.

Recommended
Corrective Action

Because the drive hit this error multiple times, it is


recommended that this drive be replaced. In addition, it is
recommended that the LUN be unbound first, bound again,
and then restored from a backup.

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

3.2.32

Alarm 3030510
Specific Problem

3030510

Managed Object

EMC

Description

0x850: Enclosure state change.

Additional
Information

The state of the disk enclosure has changed. This error is


usually the result of an FRU component failing or being
removed. The extended codes can be interpreted by knowing
what the possible state changes mean.

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030830

System Impact

Loss of redundancy on one of the FRUs will occur, and


performance might be impacted due to cache disabling.

Recommended
Corrective Action

Check the event log to see which component failed.

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

3.2.33

Alarm 3030512

SMSC 4.2 Alarm Reference Manual


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

45 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

Specific Problem

3030512

Managed Object

EMC

Description

0x852: Enclosure Duplicate Address Error.

Additional
Information

Duplicate enclosure addresses are on the back-end bus. This


could be a result of a incorrect enclosure address having been
set or the enclosure being cabled to the wrong bus.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030830

System Impact

System performance might be impacted.

Recommended
Corrective Action

Power cycle the entire array to normalize the chassis


configuration. The proper enclosure address and cabling must
be set before applying power to the system.

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

3.2.34

Alarm 3030513
Specific Problem

3030513

Managed Object

EMC

Description

0x854: The LCC cables are connected to the wrong input


port. Make sure that the LCC input cable is connected to the
primary port.

Additional
Information

The DAE LCC is connected to the Extension port instead of


the Primary port.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030830

System Impact

There will be no access to DAE.

Recommended
Corrective Action

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

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

3.2.35

Alarm 3030524

SMSC 4.2 Alarm Reference Manual


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

46 of 492

3: Hardware Agent Alarms

DRAFT

Specific Problem

3030524

Managed Object

EMC

Description

0x867: The read can fail because of:

Additional
Information

EMC Alarms

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. Resume


PROM contains basic part identification information. The read
can 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 and


cannot be cleared automatically.
Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3039073

System Impact

System performance might be impacted.

Recommended
Corrective Action

Determine the underlying issue:

The device might not be present


The device might be dead
I2C bus error
Checksum error

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

3.2.36

Alarm 3030526
Specific Problem

3030526

Managed Object

EMC

Description

0x870: Battery on the SP Board is either low or missing.


Install new battery.

Additional
Information

This error is related to the condition of the battery on the SP


itself.

Severity

Major

Message Group
(Probable Cause)

Hardware

SMSC 4.2 Alarm Reference Manual


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

47 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

Alarm Automatically
Cleared

Yes; by 3030830

System Impact

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

Recommended
Corrective Action

Replace the SP reporting the error.

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

3.2.37

Alarm 3030528
Specific Problem

3030528

Managed Object

EMC

Description

0x873: Person boots system and FLAREs ATM detects one


CMI connection is down.

Additional
Information

One of the CMI buses (the communication bus between SPs)


is down.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030830

System Impact

Internal hardware architecture redundancy will be impacted.

Recommended
Corrective Action

Replace this SP.

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

3.2.38

Alarm 3030601
Specific Problem

3030601

Managed Object

EMC

Description

0x901: Hard SCSI Error.

Additional
Information

A SCSI operation failed and needed to be retried. This error


indicates that the retry attempts failed.
This event is logged for reference and troubleshooting and
cannot be cleared automatically.

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

SMSC 4.2 Alarm Reference Manual


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

48 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

System Impact

Data loss might occur.

Recommended
Corrective Action

Look at the extended status for the affected drive to determine


the cause of the event.

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

3.2.39

Alarm 3030602
Specific Problem

3030602

Managed Object

EMC

Description

0x903: Fan Removed.

Additional
Information

A fan has been removed or is faulty.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030211

System Impact

Loss of fan redundancy will occur, and performance might be


impacted due to cache disabling.

Recommended
Corrective Action

Reinsert the power supply or fan.

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

3.2.40

Alarm 3030603
Specific Problem

3030603

Managed Object

EMC

Description

0x904: VSC Removed.

Additional
Information

A power supply unit in the expansion enclosure has been shut


down or removed from the storage system.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030211

System Impact

Loss of power supply redundancy will occur, and performance


will be impacted due to cache disabling.

Recommended
Corrective Action

Check if the power supply power cord is plugged in. Replace


the power cord if necessary.

SMSC 4.2 Alarm Reference Manual


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

49 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

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

3.2.41

Alarm 3030604
Specific Problem

3030604

Managed Object

EMC

Description

0x905: Chassis Overtemperature.

Additional
Information

The temperature inside the storage shelf is too high.

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

The system might crash.

Recommended
Corrective Action

Check the status of the fans or the surrounding environment


to determine why the system is overheating.

This event is logged for reference and troubleshooting and


cannot be cleared.

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

3.2.42

Alarm 3030605
Specific Problem

3030605

Managed Object

EMC

Description

0x906: Unit Shutdown.

Additional
Information

A disk is being shut down by FLARE. This might be due to


excessive errors, but it also might be something more simple.
If the drive in question is a hot spare, this message would be
expected if it occurs as the drive is preparing to step in for
another failed disk. Do not use this message alone as a basis
for replacing a drive. Search for other supporting messages.
Another possibility is that a disk is being released by this
currently owning SP so that it can be trespassed over to the
other SP. Very often this is an expected behavior.

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030202

SMSC 4.2 Alarm Reference Manual


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

50 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

System Impact

Data loss might occur.

Recommended
Corrective Action

Make sure that there are no fault conditions on the array or on


the hosts HBAs, and take appropriate action if required.

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

3.2.43

Alarm 3030607
Specific Problem

3030607

Managed Object

EMC

Description

0x908: Hardware Fault - Cache Disabling.

Additional
Information

Under certain array hardware failure scenarios, the array


cache is disabled to ensure data integrity. After these events,
storage subsystem performance might be poor until the cache
is manually re-enabled via the Navisphere interface.

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030212

System Impact

System performance might be impacted.

Recommended
Corrective Action

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

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

3.2.44

Alarm 3030608
Specific Problem

3030608

Managed Object

EMC

Description

0x909: Cache Dump Failed.

Additional
Information

The cache started dumping due to a preceding event but


was unable to do so because of some hardware reason. This
event is logged for reference and troubleshooting and cannot
be cleared automatically.

Severity

Critical

SMSC 4.2 Alarm Reference Manual


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

51 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

System performance might be impacted, and data loss might


occur.

Recommended
Corrective Action

Check the vault drives (if failed).

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

3.2.45

Alarm 3030612
Specific Problem

3030612

Managed Object

EMC

Description

0x90D: BBU or SPS Removed.

Additional
Information

The SPS has failed or has been removed. The storage system
dumped the write cache to the vault, then disabled caching
and flushed the vault to disk. The write cache cannot be
enabled until the problem is corrected either by replacing the
SPS if it failed, or by reinstalling it.

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3039071

System Impact

System performance might be impacted.

Recommended
Corrective Action

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

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

3.2.46

Alarm 3030613
Specific Problem

3030613

Managed Object

EMC

Description

0x90E: BBU Failed.

Additional
Information

The BBU has failed.

Severity

Major

Message Group
(Probable Cause)

Hardware

SMSC 4.2 Alarm Reference Manual


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

52 of 492

3: Hardware Agent Alarms

DRAFT

Alarm Automatically
Cleared

Yes; by 3039071

System Impact

System performance might be impacted.

Recommended
Corrective Action

Replace the failed BBU.

EMC Alarms

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

3.2.47

Alarm 3030614
Specific Problem

3030614

Managed Object

EMC

Description

0x90F: Cache Recovered with Errors.

Additional
Information

The data recovered from the cache after it was enabled


is corrupted. This event is logged for reference and
troubleshooting and cannot be cleared.

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Data loss might occur.

Recommended
Corrective Action

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

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

3.2.48

Alarm 3030615
Specific Problem

3030615

Managed Object

EMC

Description

0x910: Cache Recovery Failed.

Additional
Information

The recovery process has failed. This event is logged for


reference and troubleshooting and cannot be cleared.

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

SMSC 4.2 Alarm Reference Manual


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

53 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

System Impact

System performance might be impacted, and data loss might


occur.

Recommended
Corrective Action

Verify that your system is functioning normally. Check the


incoming events to find a reason for recovery fail.

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

3.2.49

Alarm 3030616
Specific Problem

3030616

Managed Object

EMC

Description

0x911: The SPS Power cable 1 is not configured properly (not


getting power supplied by SPS). Power cable 1 is to the xPE
on Chameleon2 and is to the X1 enclosure on X1.

Additional
Information

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

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030830

System Impact

Array functionality might be impacted.

Recommended
Corrective Action

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

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

3.2.50

Alarm 3030617
Specific Problem

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 the
first Katana enclosure on Chameleon2. This is not applicable
for X1.

Additional
Information

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

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030830

SMSC 4.2 Alarm Reference Manual


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

54 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

System Impact

Array functionality might be impacted.

Recommended
Corrective Action

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

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

3.2.51

Alarm 3030618
Specific Problem

3030618

Managed Object

EMC

Description

0x913: The serial connection between the SPs and SPSs


are crossed. This results in SP A controlling SPS B and vice
versa. This condition makes it difficult to properly identify
failing component.

Additional
Information

The system might be misconfigured, that is, the serial


connection between the SPs and SPSs are crossed. This
results in SP A controlling SPS B and vice versa.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030830

System Impact

Failing components will not be properly identified.

Recommended
Corrective Action

Check the connections between the SPs and the SPSs.

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

3.2.52

Alarm 3030619
Specific Problem

3030619

Managed Object

EMC

Description

0x914: There are multiple cables (Power 1, Power 2, Serial)


that are improperly configured.

Additional
Information

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

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030830

SMSC 4.2 Alarm Reference Manual


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

55 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

System Impact

Array functionality might be impacted.

Recommended
Corrective Action

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

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

3.2.53

Alarm 3030620
Specific Problem

3030620

Managed Object

EMC

Description

0x920: Hard Media Error.

Additional
Information

Hard Media Errors (920) on the Fiber Channel drives indicate


that a condition has occurred that might not have been
correctable by means of a drives remapping capabilities, and
it might be a precursor to data loss situations. This event
is logged for reference and troubleshooting and cannot
be cleared. This event must be investigated and cleared
manually because the error and fix need investigation and
manual intervention.

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Data loss might occur.

Recommended
Corrective Action

Drive replacement is usually recommended in instances when


an amber LED on the hard drives is on, which indicates
that the drive is not operating normally. Replacement is also
recommended when recommend drive replacement (event
code 803) has been logged, or if one or more 920 Hard Media
Errors have occurred on a Fiber Channel drive. The status of
the RAID group to which the drive belongs should be checked
to make sure that replacing the drive does not result in a more
problematic array condition.

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

3.2.54

Alarm 3030622
Specific Problem

3030622

Managed Object

EMC

Description

0x922: Host Vault Load Inconsistent.

SMSC 4.2 Alarm Reference Manual


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

56 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

Additional
Information

The inconsistency can be seen after cache dirty events,


multiple disk failures within the cache vault, or if there are
uncorrectable sector errors in the cache vault.

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030830

System Impact

Data loss might occur in case of multiple disk failures, and


performance might be impacted due to cache disabling.

Recommended
Corrective Action

Do the following:
1

In the Navisphere Manager, click the Memory tab in the


Array Properties dialog box.

Set the write cache values to zero and then click Apply.

Reset the values to original.

Enable write cache.

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

3.2.55

Alarm 3030629
Specific Problem

3030629

Managed Object

EMC

Description

0x929: Front End Fibre Link Down.

Additional
Information

Link down detected on the front-end Fiber Channel port. This


indicates a physical problem with the connection to the EMC
storage device.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030830

System Impact

Loss of redundancy on front-end FC connectivity will occur,


and system performance might be impacted.

Recommended
Corrective Action

Verify Layer 1 connectivity.

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

3.2.56

Alarm 3030633

SMSC 4.2 Alarm Reference Manual


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

57 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

Specific Problem

3030633

Managed Object

EMC

Description

0x7152811B: DRP Alarm - Incremental update has completed


successfully. Mirrorview/A is unable to communicate with the
secondary array to stop the protective snap session. Check
the mirrorview connection between the arrays.

Additional
Information

MirrorView/A cannot communicate with the secondary array


to stop the remote snap session after an incremental update
has completed. This event is logged for reference and
troubleshooting and cannot be cleared. After communication
with the remote SP is resumed, MirrorView/A operations can
be resumed manually.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

The MirrorView process will be impacted.

Recommended
Corrective Action

Check all devices in the communication path between the


source and target arrays.

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

3.2.57

Alarm 3030639
Specific Problem

3030639

Managed Object

EMC

Description

0x940: BBU Faulted.

Additional
Information

The voltage feeding the CLARiiON has dropped below


acceptable values. The system has started dumping cache to
disk. Typically, most arrays can tolerate a longer line dropout
episode (for example, 30 msec), but the maximum time
cannot be quantified because conditions vary too much. A
1.0 sec line dropout definitely induces a switch to BBU power
and the storage processors dumping data from cache to disk
modules. After a cache-dump starts, it must finish completely
even if the power line recovers immediately. When the cache
is 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

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3039134

SMSC 4.2 Alarm Reference Manual


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

58 of 492

3: Hardware Agent Alarms

DRAFT

System Impact

System performance might be impacted.

Recommended
Corrective Action

Check BBU status, and replace it if faulted.

EMC Alarms

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

3.2.58

Alarm 3030640
Specific Problem

3030640

Managed Object

EMC

Description

0x942: Excessive single-bit ECC errors on SP memory


module.

Additional
Information

Memory errors were detected on the SP memory module.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030830

System Impact

System performance might be impacted.

Recommended
Corrective Action

Correctable ECC errors should be treated as single-bit ECC


errors, which means that no corrective action is required
unless more than 50 errors are generated in a single week. If
this occurs, contact Comverse customer support.

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

3.2.59

Alarm 3030641
Specific Problem

3030641

Managed Object

EMC

Description

0x944: Hard Peer Bus Error.

Additional
Information

The SP has rebooted. This event is logged for reference and


troubleshooting and cannot be cleared.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

SMSC 4.2 Alarm Reference Manual


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

59 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

System Impact

Loss of RAID controller (SP) redundancy during the reboot will


occur, and performance during reboot will be impacted.

Recommended
Corrective Action

Determine the reason for the SP reboot, either based on an


event that occurred or using the event viewer.

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

3.2.60

Alarm 3030653
Specific Problem

3030653

Managed Object

EMC

Description

0x951: CRU Signature Error.

Additional
Information

The CRU Signature defines in which Enclosure/Bus/Slot the


disk is. It also has an entry that is unique for each RAID
group, which means that a disk must not only match the
Enclosure/Bus/Slot but also the RAID group to be included
in as part of a LUN. If you pull one disk, that slot is marked
for rebuild. If you pull a second disk from a RAID group, the
RAID group shuts down. If you then insert a new disk for the
second disk you pulled, FLARE (the array operating system)
tries to bring up the LUN in n -1 disks mode but because it
is not the original disk, it cannot bring the LUN online, and
instead returns a CRU signature error. If you insert the correct
disk (that is, the one you pulled from that slot), the LUN comes
back online. If you insert a new disk into the first slot you
pulled or insert the original disk you pulled from that slot, the
disk is rebuilt because that first slot is marked as needing a
rebuild. When a slot requires a rebuild, the CRU signature
of the disk does not matter. A rebuilt disk is assigned a new
CRU signature, which is created when a LUN is bound and
stored on the private area of each disk.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030830

System Impact

System performance might be impacted.

Recommended
Corrective Action

If two disks were removed from a RAID group before the


rebuild was completed on the first one, insert the correct disk
back into its proper place. In some cases, the only way to
re-establish ownership of this LUN is a nondestructive bind
(NDB), which can only be performed by EMC Engineering. By
unbinding the LUN and then rebinding it with NDB, the CRU
signature is rewritten.

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

SMSC 4.2 Alarm Reference Manual


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

60 of 492

3: Hardware Agent Alarms

3.2.61

DRAFT

EMC Alarms

Alarm 3030654
Specific Problem

3030654

Managed Object

EMC

Description

0x952: Single Fan Fault.

Additional
Information

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

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030210

System Impact

Loss of fan redundancy will occur.

Recommended
Corrective Action

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

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

3.2.62

Alarm 3030655
Specific Problem

3030655

Managed Object

EMC

Description

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

Additional
Information

Power supply A on the xPE has been removed or is faulty


(CX700).

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030406

System Impact

Loss of power supply redundancy will occur, and performance


will be impacted due to cache disabling.

Recommended
Corrective Action

First try replacing the power supply, standby power supply


(SPS), and SPS sense cable, and then run SPcollect
scripts. If one of the SPS persistently reports 76008103
(0x76008103) Found an error during POST errors, replace
that SP.

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

SMSC 4.2 Alarm Reference Manual


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

61 of 492

3: Hardware Agent Alarms

3.2.63

DRAFT

EMC Alarms

Alarm 3030656
Specific Problem

3030656

Managed Object

EMC

Description

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

Additional
Information

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

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030407

System Impact

Loss of power supply redundancy will occur, and performance


will be impacted due to cache disabling.

Recommended
Corrective Action

First try replacing the power supply, standby power supply


(SPS), and SPS sense cable, and then run SPcollect
scripts. If one of the SPS persistently reports 76008103
(0x76008103) Found an error during POST errors, replace
that SP.

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

3.2.64

Alarm 3030658
Specific Problem

3030658

Managed Object

EMC

Description

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

Additional
Information

Possible faulty standby power supply or power supply


(CX700).

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030830

System Impact

Loss of power supply redundancy will occur, and performance


will be impacted due to cache disabling.

Recommended
Corrective Action

First try replacing the power supply, standby power supply


(SPS), and SPS sense cable, and then run SPcollect
scripts. If one of the SPS persistently reports 76008103
(0x76008103) Found an error during POST errors, replace
that SP.

For a detailed description of these rows, see Alarm Fields Description, Page 7.
SMSC 4.2 Alarm Reference Manual
P/N 10-000-1050 Issue 1 Rev. 0.1

62 of 492

3: Hardware Agent Alarms

3.2.65

DRAFT

EMC Alarms

Alarm 3030659
Specific Problem

3030659

Managed Object

EMC

Description

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

Additional
Information

Possible faulty standby power supply or power supply.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030830

System Impact

Loss of power supply redundancy will occur, and performance


will be impacted due to cache disabling.

Recommended
Corrective Action

First try replacing the power supply, standby power supply


(SPS), and SPS sense cable, and then run SPcollect
scripts. If one of the SPS persistently reports 76008103
(0x76008103) Found an error during POST errors, replace
that SP.

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

3.2.66

Alarm 3030660
Specific Problem

3030660

Managed Object

EMC

Description

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

Additional
Information

The SP is coming up and recovering the cache image. The


vault 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 dirty
units, so it issues these errors to let the user know that
manual intervention might be required. After the units become
assigned, the cache can enable successfully.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030830

SMSC 4.2 Alarm Reference Manual


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

63 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

System Impact

System performance might be impacted.

Recommended
Corrective Action

Verify that this systems failover implementation (for example,


PowerPath) is installed and configured correctly. The fact
that these LUNs were unassigned probably means that this
systems failover implementation is deficient.

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

3.2.67

Alarm 3030702
Specific Problem

3030702

Managed Object

EMC

Description

0xA05: NON VOL Not Initialized.

Additional
Information

The nonvolatile memory on the SP has been found to be


uninitialized. The SP reinitializes the memory to its default
state and then the SP is functional after reboot. This event
should only occur once when a new SP is inserted. If you
see this message on an existing SP that has already been
initialized, it indicates that either the NVOL chip is bad or the
onboard battery on the SP is bad.

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030830

System Impact

System performance might be impacted.

Recommended
Corrective Action

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

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

3.2.68

Alarm 3030704
Specific Problem

3030704

Managed Object

EMC

Description

0xA07: Disk Powered Down.

Additional
Information

A customer-replaceable unit (most likely a disk drive) has


been powered down. This can be an indication that the drive
is problematic, but it can also be a perfectly normal message
in the context of a controlled shutdown of an enclosure.

Severity

Critical

SMSC 4.2 Alarm Reference Manual


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

64 of 492

3: Hardware Agent Alarms

DRAFT

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030830

System Impact

Data loss might occur.

Recommended
Corrective Action

The message must be examined in its context.

EMC Alarms

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

3.2.69

Alarm 3030709
Specific Problem

3030709

Managed Object

EMC

Description

0xA11: SP is removed.

Additional
Information

The SP has been physically removed.

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3039075

System Impact

Loss of RAID controller (SP) redundancy will occur, and


performance will be impacted due to cache disabling.

Recommended
Corrective Action

Check to see if any SP have been physically removed.


Reinsert them if they have.

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

3.2.70

Alarm 3030714
Specific Problem

3030714

Managed Object

EMC

Description

0xA18: CRU Drive Causing Loop Failure.

Additional
Information

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

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030830

SMSC 4.2 Alarm Reference Manual


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

65 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

System Impact

System performance might be impacted, and data loss might


occur.

Recommended
Corrective Action

Replace the drive that caused the error.

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

3.2.71

Alarm 3030730
Specific Problem

3030730

Managed Object

EMC

Description

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

Additional
Information

Fan module C on the xPE either failed or has been physically


removed (CX700).

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3039090

System Impact

System performance might be impacted.

Recommended
Corrective Action

Replace or reinsert the fan module.

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

3.2.72

Alarm 3030731
Specific Problem

3030731

Managed Object

EMC

Description

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

Additional
Information

Fan module A on the xPE either failed or has been physically


removed (CX700).

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3039092

System Impact

System performance might be impacted.

Recommended
Corrective Action

Replace or reinsert the fan module.

For a detailed description of these rows, see Alarm Fields Description, Page 7.
SMSC 4.2 Alarm Reference Manual
P/N 10-000-1050 Issue 1 Rev. 0.1

66 of 492

3: Hardware Agent Alarms

3.2.73

DRAFT

EMC Alarms

Alarm 3030805
Specific Problem

3030805

Managed Object

EMC

Description

0x2047: The system time has been set backwards. This may
affect event collection.

Additional
Information

The system time has been set backwards. This might affect
event collection. Event Monitor begins processing events
when the system time catches up to the time of the last event
Event Monitor processed.
This event is logged for reference and troubleshooting and
cannot be cleared.

Severity

Minor

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

The event collection process will be impacted, and a possible


mismatch of event times might occur.

Recommended
Corrective Action

Manually set the system time correctly.

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

3.2.74

Alarm 3030806
Specific Problem

3030806

Managed Object

EMC

Description

0x2080: SP busy, couldnt respond to at least one Error event


on the SP.

Additional
Information

Too many events were encountered together. Please see the


CX event log (either through Navisphere Manager or through
NaviCLI) for more details on events and check if any of them
are severe.
This event is logged for reference and troubleshooting and
cannot be cleared.

Severity

Minor

Message Group
(Probable Cause)

Hardware

SMSC 4.2 Alarm Reference Manual


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

67 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

Alarm Automatically
Cleared

No

Recommended
Corrective Action

Please check which errors led to this alert. Use either


Navisphere Manager or NaviCLI.

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

3.2.75

Alarm 3030809
Specific Problem

3030809

Managed Object

EMC

Description

0x20c0: SP busy, couldnt respond to at least one Critical


event on the SP.

Additional
Information

Too many events were encountered together, and at least one


event is critical. See the CX event log for more details.

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030830

System Impact

RAID controller (SP) redundancy might be lost, which will


impact system performance.

Recommended
Corrective Action

Check the CX event log (either using Navisphere Manager


or NaviCLI) for critical errors.

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

3.2.76

Alarm 3030816
Specific Problem

3030816

Managed Object

EMC

Description

0x2183: The computer has rebooted from bugcheck (0x3e9):


<bugcheck_details>.

Additional
Information

The SP has rebooted because of a bugcheck. This error


should not appear after FLARE 14.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030830

SMSC 4.2 Alarm Reference Manual


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

68 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

System Impact

RAID controller (SP) redundancy might be lost, which will


impact system performance.

Recommended
Corrective Action

Check the SPS or storage processor (SP) or both. Replace


if necessary.

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

3.2.77

Alarm 3030821
Specific Problem

3030821

Managed Object

EMC

Description

0x2480: Disk Failure.

Additional
Information

A disk has failed.

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3039059

System Impact

System performance might be impacted, and data loss might


occur.

Recommended
Corrective Action

Replace the hard drive.

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

3.2.78

Alarm 3030822
Specific Problem

3030822

Managed Object

EMC

Description

0x2481: Fan Failure.

Additional
Information

A fan has been removed or is faulty.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030830

SMSC 4.2 Alarm Reference Manual


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

69 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

System Impact

Loss of fan redundancy will occur, and performance might be


impacted due to cache disabling.

Recommended
Corrective Action

Replace the fan.

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

3.2.79

Alarm 3030823
Specific Problem

3030823

Managed Object

EMC

Description

0x2482: Power Supply Failure.

Additional
Information

A power supply has failed.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030830

System Impact

System performance might be impacted.

Recommended
Corrective Action

Replace the power supply.

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

3.2.80

Alarm 3030824
Specific Problem

3030824

Managed Object

EMC

Description

0x2483: LCC Failure.

Additional
Information

A Link Control Card has failed.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030830

System Impact

LCC redundancy will be lost.

Recommended
Corrective Action

Replace the Link Control Card.

For a detailed description of these rows, see Alarm Fields Description, Page 7.
SMSC 4.2 Alarm Reference Manual
P/N 10-000-1050 Issue 1 Rev. 0.1

70 of 492

3: Hardware Agent Alarms

3.2.81

DRAFT

EMC Alarms

Alarm 3030825
Specific Problem

3030825

Managed Object

EMC

Description

0x2484: Enclosure Failure.

Additional
Information

The enclosure has failed.

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030830

System Impact

System performance might be impacted, and data loss might


occur.

Recommended
Corrective Action

Check the incoming events (either using Navisphere Manager


or NaviCLI) to find a reason for enclosure failure.

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

3.2.82

Alarm 3030830 (Log only)


Specific Problem

3030830 (Log only).

Managed Object

EMC

Description

0x2500: Storage system has no faults.

Additional
Information

The storage system has no faults.

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

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

3.2.83

Alarm 3030832
Specific Problem

3030832

Managed Object

EMC

Description

0x2580: Storage system is faulted.

SMSC 4.2 Alarm Reference Manual


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

71 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

Additional
Information

Storage system is faulted. This message usually follows a


critical event such as a CRU power-down of a disk.

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030830

System Impact

System performance might be impacted, and data loss might


occur.

Recommended
Corrective Action

Check the preceding events either using Navisphere Manager


or NaviCLI.

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

3.2.84

Alarm 3030833 (Log only)


Specific Problem

3030833 (Log only).

Managed Object

EMC

Description

0x2700: Path to an array is up.

Additional
Information

The path from host to storage system is up.

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

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

3.2.85

Alarm 3030834
Specific Problem

3030834

Managed Object

EMC

Description

0x2780: Path to an array is down.

Additional
Information

The physical path to an array is down.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3039171

SMSC 4.2 Alarm Reference Manual


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

72 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

System Impact

Loss of redundancy on front-end FC connectivity will occur,


and system performance might be impacted.

Recommended
Corrective Action

A physical path failure might have occurred; replace the


relevant component.

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

3.2.86

Alarm 3031002
Specific Problem

3031002

Managed Object

EMC

Description

0x40004001: The MessageDispatcher detected an error


during initializationt. This error code appears only in the event
log messages.

Additional
Information

SP Reboot. The peer died in run.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030830

System Impact

Loss of RAID controller (SP) redundancy during the reboot will


occur, and performance during reboot will be impacted.

Recommended
Corrective Action

Determine the reason for the SP reboot, either based on an


event that occurred or using the event viewer at Navisphere
Manager or NaviCLI.

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

3.2.87

Alarm 3031046
Specific Problem

3031046

Managed Object

EMC

Description

0x40008010: int3, int5, etc.

Additional
Information

FLARE issue with Navisphere Management Software. The


exception was most likely caused by a bad memory reference.
This is an internal software exception event that is logged
for reference.

Severity

Major

Message Group
(Probable Cause)

Hardware

SMSC 4.2 Alarm Reference Manual


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

73 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

Alarm Automatically
Cleared

No

System Impact

RAID controller (SP) redundancy might be lost.

Recommended
Corrective Action

Determine if the SP is unmanaged. If it is, reboot it; otherwise,


cancel the case, indicating that the SP is managed and that
no action is necessary.

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

3.2.88

Alarm 3031110
Specific Problem

3031110

Managed Object

EMC

Description

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

Additional
Information

The storage system has been restarted but the storage


system drivers did not start (NDU degraded mode).
This event is logged for reference and troubleshooting and
cannot be cleared automatically. Clearing must be manual
for this event.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030830

System Impact

Upgrade success will be impacted, and the RAID controller


(SP) might fail.

Recommended
Corrective Action

If NDU (Software Installation) just upgraded the SP, you might


need to back out the changes made. However, if this occurs
with other event code messages, it might indicate a failed SP.

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

3.2.89

Alarm 3031124
Specific Problem

3031124

Managed Object

EMC

Description

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

SMSC 4.2 Alarm Reference Manual


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

74 of 492

3: Hardware Agent Alarms

Additional
Information

DRAFT

EMC Alarms

An attempt was made to trespass a private LUN, for example,


a LUN in a reserved LUN Area for MirrorView/A. Do not
trespass these LUNs.
This event indicates a failure of an administrative action and
is logged for troubleshooting and reference and cannot be
cleared.

Severity

Warning

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Recommended
Corrective Action

Configure the Reserved LUN pool.

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

3.2.90

Alarm 3031142
Specific Problem

3031142

Managed Object

EMC

Description

0x40008044: An installed software package must be


committed before this command can be accepted.

Additional
Information

An installed software package must be committed before this


command can be accepted. A feature being requested cannot
be used until the recent FLARE upgrade is committed.
This event indicates a failure of an administrative action and
is logged for troubleshooting and reference and cannot be
cleared.

Severity

Warning

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Installed software will not be usable until it the package is


committed.

Recommended
Corrective Action

Commit the software package.

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

3.2.91

Alarm 3031172

SMSC 4.2 Alarm Reference Manual


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

75 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

Specific Problem

3031172

Managed Object

EMC

Description

0x40008053: Unbind failed-LU May Be Private.

Additional
Information

Failed to unbind LUNs The LUNs may be private and cannot


be unbound before they are removed from their container.
This event indicates a failure of an administrative action and
is logged for troubleshooting and reference and cannot be
cleared.

Severity

Warning

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Recommended
Corrective Action

Remove a LUN from a storage group before attempting to


delete. You can unbind a private LUN but be careful when
doing so. The private LUN must be made public before
unbinding. If the LUN has Reserved LUN Pool next to its RAID
group in Navisphere User Interface (UI), it must be removed
from the Reserved LUN pool before being unbound.

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

3.2.92

Alarm 3031232
Specific Problem

3031232

Managed Object

EMC

Description

0x41008004: Caught ASSERT or INT5.

Additional
Information

Possible memory leak. This error should not occur in newer


FLARE versions (14, 16, 19).
This event is logged for reference and troubleshooting and
cannot be cleared. Rebooting the SP might clear it.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

RAID controller (SP) redundancy might be lost.

Recommended
Corrective Action

If this seems to be a one-time occurrence, it can safely be


ignored. However, you should continue to monitor the array
for this error. If it occurs again, it might indicate a memory
leak, which could have multiple causes, and might require
the SP to be rebooted.

For a detailed description of these rows, see Alarm Fields Description, Page 7.
SMSC 4.2 Alarm Reference Manual
P/N 10-000-1050 Issue 1 Rev. 0.1

76 of 492

3: Hardware Agent Alarms

3.2.93

DRAFT

EMC Alarms

Alarm 3032121
Specific Problem

3032121

Managed Object

EMC

Description

0x71058155: DRP Alarm - Failed to request remote K10 to


destroy a mirror.

Additional
Information

A communication error to the remote SP has occurred. This


event is logged for reference and troubleshooting and cannot
be cleared automatically. After the mirror is destroyed, this
event can be cleared.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

The MirrorView process will be impacted.

Recommended
Corrective Action

Check the communication to the remote system.

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

3.2.94

Alarm 3032122
Specific Problem

3032122

Managed Object

EMC

Description

0x71058156: DRP Alarm - Failed to request remote K10 to


update a mirror.

Additional
Information

A communication error to the remote SP has occurred.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

The MirrorView process will be impacted.

Recommended
Corrective Action

Check the communication to the remote system.

This event is logged for reference and troubleshooting and


cannot be cleared automatically.

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

SMSC 4.2 Alarm Reference Manual


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

77 of 492

3: Hardware Agent Alarms

3.2.95

DRAFT

EMC Alarms

Alarm 3032131
Specific Problem

3032131

Managed Object

EMC

Description

0x7105815F: DRP Alarm - Failed to request remote K10 to


promote an image.

Additional
Information

A communication error to the remote SP prevented a promote


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

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

The MirrorView process will be impacted.

Recommended
Corrective Action

Check the communication to the remote system.

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

3.2.96

Alarm 3032168
Specific Problem

3032168

Managed Object

EMC

Description

0x71058187: DRP Alarm - Maximum mirrors already allocated


on the system.

Additional
Information

The maximum number of mirrors have been allocated on


the system (CX500 up to 50 MV/A LUNs, CX700 up to 100
MV/A LUNs).
This event is logged for reference and troubleshooting and
cannot be cleared.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

The MirrorView process will be impacted.

Recommended
Corrective Action

Reduce the number of MV/A LUNs.

For a detailed description of these rows, see Alarm Fields Description, Page 7.
SMSC 4.2 Alarm Reference Manual
P/N 10-000-1050 Issue 1 Rev. 0.1

78 of 492

3: Hardware Agent Alarms

3.2.97

DRAFT

EMC Alarms

Alarm 3032169
Specific Problem

3032169

Managed Object

EMC

Description

0x71058188: DRP Alarm - Maximum number of mirrors on


the system.

Additional
Information

The maximum number of mirrors have been allocated on


the system (CX500 up to 50 MV/A LUNs, CX700 up to 100
MV/A LUNs).
This event is logged for reference and troubleshooting and
cannot be cleared.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

The MirrorView process will be impacted.

Recommended
Corrective Action

Reduce the number of MV/A LUNs.

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

3.2.98

Alarm 3032190
Specific Problem

3032190

Managed Object

EMC

Description

0x7105819E: DRP Alarm - Promoting a secondary image was


allowed, but recreating the secondary images failed due to two
incompatible admin operations being performed at the same
time. Its possible when cross mirroring to get into a deadlock
situation if you are doing promotion or add/delete secondary
operations at the same time. To prevent this we check current
operations and add the secondary to a promoted image to
prevent the deadlock.

Additional
Information

Two conflicting MirrorView operations were run at the same


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

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

SMSC 4.2 Alarm Reference Manual


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

79 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

System Impact

The MirrorView process will be impacted.

Recommended
Corrective Action

Check the currently running operations and add the secondary


image to a promoted image to prevent the deadlock.

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

3.2.99

Alarm 3032238
Specific Problem

3032238

Managed Object

EMC

Description

0x71058233: DRP Alarm - Cant remove the mirroring driver


from an LUs stack, as it is currently part of a mirror.

Additional
Information

Cannot destroy a mirror in an active state.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

The MirrorView process will be impacted.

Recommended
Corrective Action

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

This event is logged for reference and troubleshooting and


cannot be cleared automatically.

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

3.2.100

Alarm 3032239
Specific Problem

3032239

Managed Object

EMC

Description

0x71058235: DRP Alarm - Cant remove the mirroring driver


from an LUs stack, as it is currently synchronizing.

Additional
Information

Cannot destroy a mirror in a synchronizing state.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

SMSC 4.2 Alarm Reference Manual


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

This event is logged for reference and troubleshooting


and cannot be cleared automatically. After the mirror is
synchronized, the mirror can be destroyed.

80 of 492

3: Hardware Agent Alarms

DRAFT

System Impact

The MirrorView process will be impacted.

Recommended
Corrective Action

Wait until synchronization completes.

EMC Alarms

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

3.2.101

Alarm 3032243
Specific Problem

3032243

Managed Object

EMC

Description

0x7105823C: DRP Alarm - Cant start synchronization from


the current image condition.

Additional
Information

MirrorView condition might be synchronizing or in a state that


does not allow the start of another synchronization.
This event is logged for reference and troubleshooting and
cannot be cleared automatically.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

The MirrorView process will be impacted.

Recommended
Corrective Action

Determine the state of the mirror. If it is active, wait until it


ends and then continue. If there is an additional error, resolve
it first before continuing.

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

3.2.102

Alarm 3032253
Specific Problem

3032253

Managed Object

EMC

Description

0x71058248: DRP Alarm - A secondary image reported a


media failure.

Additional
Information

Media failure fractures can be caused by physical disk errors


within the LUN associated in the mirror connection. This might
result in the MirrorView software detecting an I/O failure to a
physical disk.
This event is logged for reference and troubleshooting and
cannot be cleared.

Severity

SMSC 4.2 Alarm Reference Manual


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

Critical

81 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030830

System Impact

The MirrorView process will be impacted.

Recommended
Corrective Action

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

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

3.2.103

Alarm 3032403
Specific Problem

3032403

Managed Object

EMC

Description

0x7105852B: DRP Alarm - Unable to verify the remote array


version during add secondary operation. Check connectivity
between the arrays.

Additional
Information

This error is usually the result of a partial connection between


the Primary and Secondary SPs. Partially connected is defined
as a connection that is useable but not fully established (for
example, SP-A <-> SP-A, but SP-B <-> SP-B does not exist
or vice versa). This is a degraded state of operation. This
event is logged for reference and troubleshooting and cannot
be cleared automatically. After connectivity is restored, this
condition can be cleared manually.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

The MirrorView process will be impacted.

Recommended
Corrective Action

Check the connectivity between the CX storage systems and


verify correct zoning configuration both at the FC Switch and
the SAN Gateway (if available).

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

3.2.104

Alarm 3035708
Specific Problem

3035708

Managed Object

EMC

SMSC 4.2 Alarm Reference Manual


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

82 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

Description

0x71528169: DRP Alarm - Mirrorview/A is unable to


communicate with secondary array and trespass the
destination LU for the mirrors secondary image while starting
an incremental update.

Additional
Information

A communication error with a remote SP has occurred.


MirrorView/A cannot communicate with the secondary array
to trespass the target LUN to the correct SP and start an
incremental update. This event is logged for reference and
troubleshooting and cannot be cleared. After communication
with the remote SP is resumed MirrorView/A operations can
be resumed manually.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

The MirrorView process will be impacted.

Recommended
Corrective Action

Check all devices in the communication path between the


source and target arrays.

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

3.2.105

Alarm 3035723
Specific Problem

3035723

Managed Object

EMC

Description

0x71528180: DRP Alarm - Operation prohibited as


MirrorView/A is in degraded mode.

Additional
Information

MirrorView/A state does not allow performing a required


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

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

The MirrorView process will be impacted.

Recommended
Corrective Action

Determine which event lead to the MirrorView/A state and


fix that event.

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

SMSC 4.2 Alarm Reference Manual


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

83 of 492

3: Hardware Agent Alarms

3.2.106

DRAFT

EMC Alarms

Alarm 3035749
Specific Problem

3035749

Managed Object

EMC

Description

0x7152819b: DRP Alarm - The session for the mirror has


failed because the primary array has run out of cache. As a
result of this error, the mirror is adminfractured.

Additional
Information

The secondary image for the mirror has fractured because the
reserved LUN pool on the primary array was exhausted. As a
result, the mirror is adminfractured.
This event is logged for reference and troubleshooting and
cannot be cleared automatically.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

The MirrorView process will be impacted.

Recommended
Corrective Action

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

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

3.2.107

Alarm 3035750
Specific Problem

3035750

Managed Object

EMC

Description

0x7152819c: DRP Alarm - The session for the mirror has


failed because the secondary array has run out of cache. As a
result of this error, the mirror is adminfractured.

Additional
Information

The secondary image for the mirror has fractured because the
reserved LUN pool on the secondary array was exhausted.
As a result, the mirror is adminfractured.
This event is logged for reference and troubleshooting and
cannot be cleared automatically.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

SMSC 4.2 Alarm Reference Manual


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

84 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

System Impact

The MirrorView process will be impacted.

Recommended
Corrective Action

Add more cache LUNs on the secondary array and retry a


sync.

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

3.2.108

Alarm 3037004
Specific Problem

3037004

Managed Object

EMC

Description

0x71298001: Unable to initialize allocate memory for poll


data. Polls fail.

Additional
Information

An internal problem has occurred with the array management.


This event is logged for reference and troubleshooting and
cannot be cleared.
This is the result of an error in the Navisphere Management
Server (CIMOM), which is unable to perform one of its
functions on the storage processor.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Management towards storage system might be lost.

Recommended
Corrective Action

Restart CIMOM on the SP. If the error persists after restarting


the CIMOM or has resulted in an unmanaged SP, contact
Comverse customer support.

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

3.2.109

Alarm 3037061
Specific Problem

3037061

Managed Object

EMC

Description

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

Additional
Information

An installation failure has occurred on the peer SP.

Severity

Major

Message Group
(Probable Cause)

Hardware

SMSC 4.2 Alarm Reference Manual


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

85 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

Alarm Automatically
Cleared

No

System Impact

Software package installation will be impacted.

Recommended
Corrective Action

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

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

3.2.110

Alarm 3037062
Specific Problem

3037062

Managed Object

EMC

Description

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

Additional
Information

Installation of software on the master SP has failed.

Severity

Minor

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Software package installation will be impacted.

Recommended
Corrective Action

Look at the text attached to the event to understand the


reason for the problem. After you have solved the issue, run
an NDU again.

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

3.2.111

Alarm 3037075
Specific Problem

3037075

Managed Object

EMC

Description

0x71518026: The SP failed to reboot.

Additional
Information

Service processor failed to reboot due to a hardware issue


that needs to be investigated.

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030830

SMSC 4.2 Alarm Reference Manual


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

86 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

System Impact

Loss of RAID controller (SP) redundancy will occur, and


performance will be impacted due to cache disabling.

Recommended
Corrective Action

A diagnosis must be made to determine if a minor corrective


action is sufficient to rectify the situation or if the SP
boot-drives must be re-imaged. Certain types of failures
require re-imaging a pair of SP boot drives. Other types
of failures require the SP replacement, or recabling and
reconfiguring the array.

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

3.2.112

Alarm 3037076
Specific Problem

3037076

Managed Object

EMC

Description

0x71518027: The SP failed to reboot.

Additional
Information

Service processor failed to reboot due to a hardware issue


that needs to be investigated.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030830

System Impact

RAID controller (SP) redundancy might be lost.

Recommended
Corrective Action

A diagnosis must be made to determine if a minor corrective


action is sufficient to rectify the situation or if the SP
boot-drives must be re-imaged. Certain types of failures
require re-imaging a pair of SP boot drives. Other types
of failures require the SP replacement, or recabling and
reconfiguring the array.

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

3.2.113

Alarm 3037102
Specific Problem

3037102

Managed Object

EMC

Description

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

Additional
Information

This is a generic error with specific text that describes the


problem. The error could be duplicate enclosure address,
power supply, standby power supply (SPS), or SPS sense
cable.

Severity

Major

SMSC 4.2 Alarm Reference Manual


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

87 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030830

System Impact

Redundancy might be lost in the power supply or RAID


controller (SP), and performance might be impacted due to
cache disabling.

Recommended
Corrective Action

Look at the text attached to the event to understand the


reason for the problem. Possible solutions: replace the power
supply, standby power supply (SPS), and SPS sense cable.
If one of the SPs persistently reports 0x76008103 Found an
error during POST errors, replace that SP.

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

3.2.114

Alarm 3037113
Specific Problem

3037113

Managed Object

EMC

Description

0x7600800c: Cannot alloc or free memory.

Additional
Information

A call has been made to an internal FLARE application


(psmtool). This application is not critical to the arrays
operation or management.

Severity

Minor

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Recommended
Corrective Action

The array retries this operation. If this message is not


continually being logged more than a few times a day, it can
be safely ignored.

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

3.2.115

Alarm 3037122
Specific Problem

3037122

Managed Object

EMC

Description

0x76008101: Found single bit ECC error. See message


details.

SMSC 4.2 Alarm Reference Manual


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

88 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

Additional
Information

There was an error correction code error in the CX memory


modules. This is an issue that affects a limited number of
dual in-line memory modules (DIMMs) on CX-Series storage
processors (SPs). This alarm is a notification of a Memory
ECC error, and cannot be cleared.

Severity

Minor

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Threshold

If this occurs more 50 times, contact customer support.

Recommended
Corrective Action

Correctable ECC errors should be treated as single-bit ECC


errors, which means that no corrective action is required
unless more than 50 errors are generated in a single week.

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

3.2.116

Alarm 3037123
Specific Problem

3037123

Managed Object

EMC

Description

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

Additional
Information

When a multibit error occurs, the memory controller generates


an SMI interrupt. Information about what DIMM and the
syndrome bits are gathered and this information is stored in
the DMI log prior to reboot. Upon a successful reboot, this
DMI logged information is read via the DGSSP driver and
stored into the NT event log.

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030830

System Impact

Loss of RAID controller (SP) redundancy will occur, and


performance will be impacted due to cache disabling.

Recommended
Corrective Action

Replace the SP. This is required because a multibit ECC error


causes the SP to panic and reboot without creating a dump
file.

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

3.2.117

Alarm 3037315

SMSC 4.2 Alarm Reference Manual


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

89 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

Specific Problem

3037315

Managed Object

EMC

Description

0x7950800E: This occurs when trying to remove the device


creator form the list of filter drivers.

Additional
Information

This error occurs when trying to remove the device creator


from the list of filter drivers. It means that the command
was sent to the wrong Storage Processor (SP), and then
forwarded to the other SP.
This event is logged for reference and troubleshooting and
cannot be cleared automatically.

Severity

Warning

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Recommended
Corrective Action

Please contact Comverse customer support.

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

3.2.118

Alarm 3037339
Specific Problem

3037339

Managed Object

EMC

Description

0x79508026: Subroutine failed, see data section for source


error.

Additional
Information

An internal software error with accessing the system


configuration files (PSM LUN) has occurred.
This event is logged for reference and troubleshooting and
cannot be cleared.

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

SMSC 4.2 Alarm Reference Manual


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

90 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

System Impact

Data loss might occur in case of multiple disk failures, and


performance might be impacted due to cache disabling.

Recommended
Corrective Action

Do the following:
1

Verify that all disks making up the PSM LUN are


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

If there are no other signs of trouble on the array, the


action required depends on whether you are seeing any
other adverse effects. An array should definitely not be
logging these messages frequently, because this would
indicate some sort of problem with accessing the PSM
LUN or its drives

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

3.2.119

Alarm 3039062
Specific Problem

3039062

Managed Object

EMC

Description

0x605: CRU Unit Rebuild Halted.

Additional
Information

FLARE has stopped a rebuild that was in progress for a


particular LUN contained on a disk. This can be generated
either because of LUN trespassing, or because of a double
fault in the RAID group where the LUN is trying to be rebuilt.

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030204

System Impact

Data loss might occur.

Recommended
Corrective Action

Check that the rebuild continues on the other SP until it is


completed.

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

3.2.120

Alarm 3039063
Specific Problem

3039063

Managed Object

EMC

Description

0x606: Unit Shutdown for Trespass.

SMSC 4.2 Alarm Reference Manual


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

91 of 492

3: Hardware Agent Alarms

Additional
Information

DRAFT

EMC Alarms

The SP has shut down the LUN containing this drive module
at the request of the peer SP because of a trespass operation.
Under the following conditions, a CLARiiON array might
experience 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

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3039063

System Impact

FC connectivity towards the CX will be impacted or RAID


controller (SP) redundancy will be lost.

Recommended
Corrective Action

If all LUNs have failed over to the peer SP, review the event
logs to determine the root cause. If the SP failed, it must
be replaced. Check HBAs and fiber connections to the CX
system.

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

3.2.121

Alarm 3039065 (Log only)


Specific Problem

3039065 (Log only).

Managed Object

EMC

Description

0x621: Backround Verify Started.

Additional
Information

A background check on the correctness of parity information


has begun on the unit of which this drive is a member.

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3039066

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

3.2.122

Alarm 3039066 (Log only)


Specific Problem

3039066 (Log only).

Managed Object

EMC

Description

0x622: Backround Verify Complete.

SMSC 4.2 Alarm Reference Manual


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

92 of 492

3: Hardware Agent Alarms

DRAFT

Additional
Information

The Background Verify process has completed.

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

EMC Alarms

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

3.2.123

Alarm 3039069
Specific Problem

3039069

Managed Object

EMC

Description

0x636: BBU/SPS Removed.

Additional
Information

SPS was removed from the storage system.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3039071

System Impact

System performance might be impacted.

Recommended
Corrective Action

Reinsert/reconnect the BBU.

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

3.2.124

Alarm 3039070
Specific Problem

3039070

Managed Object

EMC

Description

0x637: BBU Recharging.

Additional
Information

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


reboot.

Severity

Warning

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3039071

SMSC 4.2 Alarm Reference Manual


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

93 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

System Impact

System performance might be impacted.

Recommended
Corrective Action

Wait about 20 minutes for recharging before the cache is


enabled.

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

3.2.125

Alarm 3039071 (Log only)


Specific Problem

3039071 (Log only).

Managed Object

EMC

Description

0x638: BBU Enabled.

Additional
Information

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

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

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

3.2.126

Alarm 3039073 (Log only)


Specific Problem

3039073 (Log only).

Managed Object

EMC

Description

0x63F: Resume PROM information was read successfully.

Additional
Information

The SP has successfully read the PROM information about


the device denoted by the extended status code. This event
is logged for reference and troubleshooting and cannot be
cleared.

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

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

3.2.127

Alarm 3039074

SMSC 4.2 Alarm Reference Manual


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

94 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

Specific Problem

3039074

Managed Object

EMC

Description

0x642: Backround Verify Aborted.

Additional
Information

A Background Verify operation has been terminated due to


an abnormal event, such as the failure of one of the disks
in the LUN, trespass, or SP reboot. This event is logged for
reference and troubleshooting and cannot be cleared.

Severity

Warning

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Recommended
Corrective Action

Please contact Comverse customer support.

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

3.2.128

Alarm 3039075 (Log only)


Specific Problem

3039075 (Log only).

Managed Object

EMC

Description

0x644: Peer SP Inserted.

Additional
Information

The peer SP has been reinserted.

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

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

3.2.129

Alarm 3039076 (Log only)


Specific Problem

3039076 (Log only).

Managed Object

EMC

Description

0x645: CRU Bound.

Additional
Information

A disk was bound to a RAID group.

Severity

Normal

SMSC 4.2 Alarm Reference Manual


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

95 of 492

3: Hardware Agent Alarms

DRAFT

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

EMC Alarms

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

3.2.130

Alarm 3039077 (Log only)


Specific Problem

3039077 (Log only).

Managed Object

EMC

Description

0x646: Disk Module Unbound.

Additional
Information

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

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

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

3.2.131

Alarm 3039079
Specific Problem

3039079

Managed Object

EMC

Description

0x698: SPS/Battery Testing In Progress.

Additional
Information

A series of these logs indicates that the scheduled SPS test


event has occurred.

Severity

Warning

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030830

System Impact

The cache will be automatically disabled during battery


testing, and performance will be impacted.

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

3.2.132

Alarm 3039090 (Log only)

SMSC 4.2 Alarm Reference Manual


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

96 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

Specific Problem

3039090 (Log only).

Managed Object

EMC

Description

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

Additional
Information

Fan module C on the xPE has been installed or repaired


(CX700).
This event is logged for reference and troubleshooting and
cannot be cleared.

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

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

3.2.133

Alarm 3039091 (Log only)


Specific Problem

3039091 (Log only).

Managed Object

EMC

Description

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

Additional
Information

Fan module B on the xPE has been installed or repaired


(CX700).
This event is logged for reference and troubleshooting and
cannot be cleared.

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

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

3.2.134

Alarm 3039092 (Log only)


Specific Problem

3039092 (Log only).

Managed Object

EMC

Description

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

Additional
Information

Fan module A on the xPE has been installed or repaired


(CX700).
This event is logged for reference and troubleshooting and
cannot be cleared.

SMSC 4.2 Alarm Reference Manual


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

97 of 492

3: Hardware Agent Alarms

DRAFT

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

EMC Alarms

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

3.2.135

Alarm 3039094
Specific Problem

3039094

Managed Object

EMC

Description

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

Additional
Information

Fan module B on the xPE either failed or has been physically


removed (CX700).

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3039091

System Impact

System performance might be impacted.

Recommended
Corrective Action

Replace or reinsert the fan module.

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

3.2.136

Alarm 3039103
Specific Problem

3039103

Managed Object

EMC

Description

0x78A: Write cache enable pending.

Additional
Information

The write cache is in a pending state until it is possible to


enable 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

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030212

SMSC 4.2 Alarm Reference Manual


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

98 of 492

3: Hardware Agent Alarms

DRAFT

System Impact

System performance might be impacted.

Recommended
Corrective Action

Check the CLARiiON event log for details.

EMC Alarms

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

3.2.137

Alarm 3039134 (Log only)


Specific Problem

3039134 (Log only).

Managed Object

EMC

Description

0x941: BBU on line.

Additional
Information

The battery backup unit is online. The cache should return to


the enabled state.

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

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

3.2.138

Alarm 3039148
Specific Problem

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 reasons
mentioned in first sentence. Communication between SPA
and SPB is down.

Additional
Information

Software issue. The Peer SP is down because of


hang/crash/bugcheck. Communication between SPA and
SPB is down.

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030830

System Impact

Loss of RAID controller (SP) redundancy will occur, and


performance will be impacted due to cache disabling.

Recommended
Corrective Action

Reboot the SP. Check for FLARE updates/patches.

For a detailed description of these rows, see Alarm Fields Description, Page 7.
SMSC 4.2 Alarm Reference Manual
P/N 10-000-1050 Issue 1 Rev. 0.1

99 of 492

3: Hardware Agent Alarms

3.2.139

DRAFT

EMC Alarms

Alarm 3039149
Specific Problem

3039149

Managed Object

EMC

Description

0xA25: Enclosure state change.

Additional
Information

A component, for example, a fan module, has failed or has


been removed. The extended codes can be interpreted by
knowing what the possible state changes mean.

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030830

System Impact

One of the FRUs redundancy will be impacted.

Recommended
Corrective Action

Check the joining events to determine why the enclosures


state changed.

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

3.2.140

Alarm 3039150
Specific Problem

3039150

Managed Object

EMC

Description

0x2003: SP busy, couldnt respond to at least one


Informational event on the SP.

Additional
Information

Too many events were encountered together. Please see the


CX event log (either through Navisphere Manager or through
NaviCLI) for more details on events and check if any of them
are severe.
This event is logged for reference and troubleshooting and
cannot be cleared.

Severity

Minor

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Recommended
Corrective Action

Please check which errors led to this alert. Use either


Navisphere Manager or NaviCLI.

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

SMSC 4.2 Alarm Reference Manual


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

100 of 492

3: Hardware Agent Alarms

3.2.141

DRAFT

EMC Alarms

Alarm 3039151 (Log only)


Specific Problem

3039151 (Log only).

Managed Object

EMC

Description

0x4600: Informational Audit Log entry.

Additional
Information

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

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

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

3.2.142

Alarm 3039152
Specific Problem

3039152

Managed Object

EMC

Description

0x4640: Warning Audit Log entry.

Additional
Information

An audit log entry has been created for an unsuccessful


login/request. Login failure must be logged and cannot be
cleared.
This is not a problem and Navisphere is working as
designed. Any client that issues a request without an
authorized username/password results in an audit log entry.

Severity

Warning

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Recommended
Corrective Action

Please contact Comverse customer support.

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

3.2.143

Alarm 3039153

SMSC 4.2 Alarm Reference Manual


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

101 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

Specific Problem

3039153

Managed Object

EMC

Description

0x71004000: DRP Alarm - The Reserved Lun Pool for Lun


<number> has become <x> percent full.

Additional
Information

This error is related to MirrorView/Snap view reserved


space. The CLARiiON array gets the following message:

The Reserved LUNs assigned to LUN XX have


become 95 percent full. MirrorView/A does
not fail.
The next message is: The Reserved LUNs assigned

to LUN XX have become 50 percent full.


This is not a problem. MirrorView/A has acquired a new disk
from the Reserved LUN pool and the session is still running.
When a MirrorView/A session reaches 100 percent, it acquires
another LUN from the Reserved LUN pool. As long as LUNs
are available in the Reserved LUN pool when the existing
LUN fills up, a new LUN is added to the session. The percent
full varies according to the size of the LUN added and how
many LUNs are already in the session. There is no specific
clearing event for this, and it must be cleared manually when
there is more space in the Reserved LUN pool.
Severity

Warning

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Recommended
Corrective Action

Please contact Comverse customer support.

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

3.2.144

Alarm 3039154
Specific Problem

3039154

Managed Object

EMC

Description

0x7100801C: DRP Alarm - There is no more room in the


Reserved Lun Pool.

Additional
Information

The Reserved LUN pool holds the changed blocks for


MirrorView/A. When there is no more room in the pool, expect
MirrorView/A to fail. There is no specific clearing event for
this, and it must be cleared manually when there is more
space in the Reserved LUN pool.

Severity

Major

Message Group
(Probable Cause)

Hardware

SMSC 4.2 Alarm Reference Manual


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

102 of 492

3: Hardware Agent Alarms

DRAFT

Alarm Automatically
Cleared

No

System Impact

The MirrorView process will be impacted.

Recommended
Corrective Action

Add more LUNs to the reserved pool area.

EMC Alarms

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

3.2.145

Alarm 3039155
Specific Problem

3039155

Managed Object

EMC

Description

0x7100802D: DRP Alarm - SnapView has attempted an


operation on a Session that no longer exists.

Additional
Information

MirrorView/A mirrors are permanently fractured after cache


dirty LUN condition on array. During cleanup and restoration of
mirroring, the secondary images must be removed and added
back to the mirror. When attempting to add the secondary
image to the mirror a 71008043 or 7100802d error is received
by the user and the secondary image cannot be added back
to the mirror. A layered driver used by MV/A is maintaining
information related to the primary image LUN and cannot
correctly identify the owning SP of the primary image. This
issue is a side effect of the LUNs on the array experiencing
a cache dirty condition. As a result, the attempt to add the
secondary image fails. This event is logged for reference and
troubleshooting and cannot be cleared automatically.

Severity

Minor

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

The MirrorView process will be impacted.

Recommended
Corrective Action

Remove the secondary and primary image of the MirrorView


and any snaps and then recreate them.

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

3.2.146

Alarm 3039156
Specific Problem

3039156

Managed Object

EMC

Description

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

SMSC 4.2 Alarm Reference Manual


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

103 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

Additional
Information

A SnapView command was sent to a non-owning SP. This


event is logged for reference and troubleshooting and cannot
be cleared automatically.

Severity

Minor

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Recommended
Corrective Action

Issue the snap command against the controlling SP for that


LUN.

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

3.2.147

Alarm 3039157
Specific Problem

3039157

Managed Object

EMC

Description

0x71050200: DRP Alarm - An image was fractured. If the


failure clears automatic resynchronization may be allowed.

Additional
Information

An image was fractured for some reason. If the failure


clears, automatic resynchronization might be allowed. This
error must be investigated further to see the root cause of
the image fracture. This event is logged for reference and
troubleshooting and cannot be cleared automatically. After
connectivity is restored and synchronization continues, this
condition can be cleared manually.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

The MirrorView process will be impacted.

Recommended
Corrective Action

Check the event log to determine which failure triggered this


alarm and then fix it. Check to see whether resynchronization
continues. If not, contact Comverse customer support.

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

3.2.148

Alarm 3039158
Specific Problem

3039158

Managed Object

EMC

SMSC 4.2 Alarm Reference Manual


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

104 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

Description

0x71050201: DRP Alarm - An image was fractured, and


administrator action is required for resynchronization.

Additional
Information

An image was fractured for some reason. The synchronization


cannot continue automatically.
This event is logged for reference and troubleshooting
and cannot be cleared automatically. After the mirror is
synchronized, this event can be cleared.

Severity

Minor

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

The MirrorView process will be impacted.

Recommended
Corrective Action

Check the event log to determine which failure triggered this


alarm and then fix it. Restart the synchronization manually.

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

3.2.149

Alarm 3039159
Specific Problem

3039159

Managed Object

EMC

Description

0x71058238: DRP Alarm - Cant fracture an image as were


not the primary K10 and/or controlling SP for the mirror.

Additional
Information

The fracture command has been sent to either the incorrect


SP (via navicli commands) or the mirror underneath the
secondary array.
This event is logged for reference and troubleshooting and
cannot be cleared.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

The MirrorView process will be impacted.

Recommended
Corrective Action

Retry the command and send it to either the correct SP or


the primary array mirror.

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

3.2.150

Alarm 3039160

SMSC 4.2 Alarm Reference Manual


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

105 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

Specific Problem

3039160

Managed Object

EMC

Description

0x7105823B: DRP Alarm - Cant start synchronization as


were not the primary K10 and/or controlling SP for the mirror.

Additional
Information

The fracture command has been sent to either the incorrect


SP (via navicli commands) or the mirror underneath the
secondary array.
This event is logged for reference and troubleshooting and
cannot be cleared.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

MirrorView/A management will be impacted.

Recommended
Corrective Action

Retry the command and send it to either the correct SP or


the primary array mirror.

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

3.2.151

Alarm 3039161
Specific Problem

3039161

Managed Object

EMC

Description

0x71170008: A Fibre Channel connection has become


inactive.

Additional
Information

Something happened to the front-end FC connection. Possible


causes of the front-end Fiber Loop errors are:

Customer powered down or rebooted a server

The SP problem

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

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3039162

SMSC 4.2 Alarm Reference Manual


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

106 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

System Impact

FC connectivity between host and storage will be impacted,


and system performance might be impacted.

Recommended
Corrective Action

To troubleshoot front-end fiber loop errors on the CLARiiON


array, do the following:
1

Verify that the user was not booting or powering down


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

Examine the SP event logs and the fault lights on the


CLARiiON array to see if any other errors indicate a bad
SP

If no other errors indicate a bad SP, look at the server


logs and fault lights on the HBA (if any) to see if they
indicate a failed HBA

If the front-end fiber errors continue, replace the cables


and GBICs between the switch and the SP on the
CLARiiON array

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

3.2.152

Alarm 3039162 (Log only)


Specific Problem

3039162 (Log only).

Managed Object

EMC

Description

0x71170009: A Fibre Channel connection has become active.

Additional
Information

The front-end fiber loop is up and functional.

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

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

3.2.153

Alarm 3039163
Specific Problem

3039163

Managed Object

EMC

Description

0x71214000: The service failed to start, or was stopped. See


error text for details either at Navisphere Manager or using
NaviCLI.

SMSC 4.2 Alarm Reference Manual


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

107 of 492

3: Hardware Agent Alarms

3.2.154

DRAFT

EMC Alarms

Additional
Information

Various SP services/processes are being impacted by a very


busy system. This is usually seen on busy arrays when an
agent indicates loss of contact with CIMON.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

System performance might be impacted.

Recommended
Corrective Action

Please contact customer support engineers.

Alarm 3039164
Specific Problem

3039164

Managed Object

EMC

Description

0x71270006: Text is of the form Bus N Disk M status: The


data area contains sense data from a back-end disk drive.

Additional
Information

This is the result of a SCSI check condition.

Severity

Minor

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Recommended
Corrective Action

Please contact customer support engineers.

This event is logged for reference and troubleshooting and


cannot be cleared.

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

3.2.155

Alarm 3039165
Specific Problem

3039165

Managed Object

EMC

Description

0x71518003: This file is either not a valid upgrade file or is


corrupt. It may have been corrupted during a file transfer.
Obtain a new copy and retry the upgrade.

Additional
Information

During an upgrade from FLARE 16 to 19, a file is missing or


its extension is not supported.

SMSC 4.2 Alarm Reference Manual


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

108 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

Severity

Minor

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Software package installation will be impacted.

Recommended
Corrective Action

If this is the result of an NDU, the NDU (with a Release 16


Navisphere) 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 14
and Release 16

Obtain a Release 19 Navisphere (Release 19 CLI or the


off-array GUI). Both Release 19 Navisphere utilities can
unzip the PBU file before it sends the packages to the
NDU

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

3.2.156

Alarm 3039166
Specific Problem

3039166

Managed Object

EMC

Description

0x71518007: The software package may not be reverted,


either because it has already been committed or because no
previous revision is available.

Additional
Information

The software package might not be reverted, either because it


has already been committed or because no previous revision
is available. This is caused by a configuration problem, and is
unable to revert to an older software revision.
This event indicates a failure of an administrative action and
is logged for troubleshooting and reference and cannot be
cleared.

Severity

Minor

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Recommended
Corrective Action

Determine which layered application has been installed and if


it can be reverted.

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

SMSC 4.2 Alarm Reference Manual


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

109 of 492

3: Hardware Agent Alarms

3.2.157

DRAFT

EMC Alarms

Alarm 3039167
Specific Problem

3039167

Managed Object

EMC

Description

0x7151801D: NDU app caught some sort of exception.

Additional
Information

A nondisruptive upgrade (NDU) has failed.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3030830

System Impact

Upgrade success will be impacted.

Recommended
Corrective Action

Reboot the SP to reset the upgrade, if it is not rebooted


automatically.

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

3.2.158

Alarm 3039169
Specific Problem

3039169

Managed Object

EMC

Description

0x76008103: Found POST error. See message details either


at Navisphere Manger or using NaviCLI.

Additional
Information

If this event occurs every 60 seconds, the BIOS POST event


log area is not being properly cleared after the messages are
displayed.

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

One of the systems FRUs will be impacted, or performance


will be impacted.

Recommended
Corrective Action

Please contact Comverse customer support.

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

3.2.159

Alarm 3039170

SMSC 4.2 Alarm Reference Manual


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

110 of 492

3: Hardware Agent Alarms

DRAFT

EMC Alarms

Specific Problem

3039170

Managed Object

EMC

Description

0x79008009: Attempt to consume/delete already consumed


obj.

Additional
Information

An attempt was made to consume/delete an already


consumed object. This might be a private LUN or a LUN in
a storage group.
This is a storage manager action that failed, which means that
it is logged for reference and troubleshooting.

Severity

Minor

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Recommended
Corrective Action

Remove a LUN from a storage group before attempting to


delete. You can unbind a private LUN but be careful when
doing so. The private LUN must be made public before
unbinding. If the LUN has Reserved LUN Pool next to its RAID
group in Navisphere User Interface (UI), it must be removed
from the Reserved LUN pool before being unbound.

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

SMSC 4.2 Alarm Reference Manual


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

111 of 492

3: Hardware Agent Alarms

3.3

DRAFT

Langley 4 Alarms

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

3.3.1

Alarm 4090101
Specific Problem

4090101

Managed Object

Langley 4

Description

The overall server health is now OK.

Additional
Information

Server Health

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

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

3.3.2

Alarm 4090102
Specific Problem

4090102

Managed Object

Langley 4

Description

The overall server health is now degraded.

Additional
Information

Server Health

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 4090101

System Impact

Server performance or redundancy will be degraded.

Recommended
Corrective Action

This is a generic trap indicating that the general servers state


has become degraded, noncritical from another state. This
trap is always accompanied by other traps. Follow these other
traps instructions.

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

3.3.3

Alarm 4090103

SMSC 4.2 Alarm Reference Manual


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

112 of 492

3: Hardware Agent Alarms

DRAFT

Langley 4 Alarms

Specific Problem

4090103

Managed Object

Langley 4

Description

The overall server health is now critical.

Additional
Information

Server Health

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 4090101

System Impact

The server will be in a failed state.

Recommended
Corrective Action

This is a generic trap indicating that the general servers state


has become degraded, critical from another state. This trap
is always accompanied by other traps. Follow these other
traps instructions.

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

3.3.4

Alarm 4090104
Specific Problem

4090104

Managed Object

Langley 4

Description

The overall server health is now nonrecoverable.

Additional
Information

Server Health

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 4090101

System Impact

The server will fail.

Recommended
Corrective Action

Contact Comverse customer support.

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

3.3.5

Alarm 4090105
Specific Problem

4090105

Managed Object

Langley 4

Description

An intrusion to the chassis has been detected.

SMSC 4.2 Alarm Reference Manual


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

113 of 492

3: Hardware Agent Alarms

DRAFT

Langley 4 Alarms

Additional
Information

Server Chassis

Severity

Minor

Message Group
(Probable Cause)

Security

Alarm Automatically
Cleared

Yes; by 4090106

System Impact

No immediate impact. The chassis will be vulnerable to


external factors.

Recommended
Corrective Action

The chassis top cover is protected from intrusion. If this trap


occurs when the server is not undergoing maintenance,
determine if someone is tampering with the server.

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

3.3.6

Alarm 4090106
Specific Problem

4090106

Managed Object

Langley 4

Description

The chassis intrusion is no longer detected.

Additional
Information

Server Chassis

Severity

Warning

Message Group
(Probable Cause)

Security

Alarm Automatically
Cleared

No

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

3.3.7

Alarm 4090107
Specific Problem

4090107

Managed Object

Langley 4

Description

The processor experienced an IERR (Internal Error).

Additional
Information

CPU

Severity

Critical

Message Group
(Probable Cause)

Hardware

SMSC 4.2 Alarm Reference Manual


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

114 of 492

3: Hardware Agent Alarms

DRAFT

Langley 4 Alarms

Alarm Automatically
Cleared

No

System Impact

If CPU0 fails, the server will fail. If CPU1 fails, performance


will be degraded.

Recommended
Corrective Action

The processor encountered an internal error. Contact


Comverse customer support.

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

3.3.8

Alarm 4090108
Specific Problem

4090108

Managed Object

Langley 4

Description

The processor experienced a thermal trip.

Additional
Information

CPU

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

If CPU0 fails, the server will fail. If CPU1 fails, performance


will be degraded.

Recommended
Corrective Action

The processor reached its critical temperature, either due to


insufficient cooling or heatsink decoupling issues. Contact
Comverse customer support.

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

3.3.9

Alarm 4090109
Specific Problem

4090109

Managed Object

Langley 4

Description

The processor experienced an FRB1 error, BIST failure.

Additional
Information

CPU

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

SMSC 4.2 Alarm Reference Manual


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

115 of 492

3: Hardware Agent Alarms

DRAFT

Langley 4 Alarms

System Impact

If CPU0 fails, the server will fail. If CPU1 fails, performance


will be degraded.

Recommended
Corrective Action

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


support.

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

3.3.10

Alarm 4090110
Specific Problem

4090110

Managed Object

Langley 4

Description

The processor experienced an FRB2 error, hang in POST


failure.

Additional
Information

CPU

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

If CPU0 fails, the server will fail. If CPU1 fails, performance


will be degraded.

Recommended
Corrective Action

The CPU has failed. Contact Comverse customer support.

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

3.3.11

Alarm 4090111
Specific Problem

4090111

Managed Object

Langley 4

Description

The processor experienced an FRB3 error, initialization failure.

Additional
Information

CPU

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

SMSC 4.2 Alarm Reference Manual


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

116 of 492

3: Hardware Agent Alarms

DRAFT

Langley 4 Alarms

System Impact

If CPU0 fails, the server will fail. If CPU1 fails, performance


will be degraded.

Recommended
Corrective Action

The CPU has failed. Contact Comverse customer support.

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

3.3.12

Alarm 4090112
Specific Problem

4090112

Managed Object

Langley 4

Description

The processor experienced a configuration error.

Additional
Information

CPU

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

If CPU0 fails, the server will fail. If CPU1 fails, performance


will be degraded.

Recommended
Corrective Action

The CPU has failed. Contact Comverse customer support.

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

3.3.13

Alarm 4090113
Specific Problem

4090113

Managed Object

Langley 4

Description

The processor presence has been detected.

Additional
Information

CPU

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

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

SMSC 4.2 Alarm Reference Manual


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

117 of 492

3: Hardware Agent Alarms

3.3.14

DRAFT

Langley 4 Alarms

Alarm 4090114
Specific Problem

4090114

Managed Object

Langley 4

Description

The processor has been disabled.

Additional
Information

CPU

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Server performance will be degraded.

Recommended
Corrective Action

The processor was disabled. If this trap occurs when no


planned maintenance is being done, contact Comverse
customer support.

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

3.3.15

Alarm 4090115
Specific Problem

4090115

Managed Object

Langley 4

Description

The processor has encountered an SMBIOS uncorrectable


CPU-Complex error.

Additional
Information

CPU

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

If CPU0 fails, the server will fail. If CPU1 fails, performance


will be degraded.

Recommended
Corrective Action

The CPU has failed. Contact Comverse customer support.

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

3.3.16

Alarm 4090116

SMSC 4.2 Alarm Reference Manual


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

118 of 492

3: Hardware Agent Alarms

DRAFT

Specific Problem

4090116

Managed Object

Langley 4

Description

The power supply unit is fully redundant.

Additional
Information

Power Redundancy

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Langley 4 Alarms

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

3.3.17

Alarm 4090117
Specific Problem

4090117

Managed Object

Langley 4

Description

The power supply unit redundancy has been degraded.

Additional
Information

Power Redundancy

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 4090116

System Impact

Another power supply failure might cause the server to fail.

Recommended
Corrective Action

Contact Comverse customer support.

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

3.3.18

Alarm 4090118
Specific Problem

4090118

Managed Object

Langley 4

Description

The power supply unit redundancy has been lost.

Additional
Information

Power Redundancy

Severity

Critical

SMSC 4.2 Alarm Reference Manual


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

119 of 492

3: Hardware Agent Alarms

DRAFT

Langley 4 Alarms

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 4090116

System Impact

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

Recommended
Corrective Action

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

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

3.3.19

Alarm 4090119
Specific Problem

4090119

Managed Object

Langley 4

Description

The power supply <PowerSupply> presence has been


detected.

Additional
Information

<PowerSupply>

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

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

3.3.20

Alarm 4090120
Specific Problem

4090120

Managed Object

Langley 4

Description

The power supply <PowerSupply> is no longer detected as


present.

Additional
Information

<PowerSupply>

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 4090119

SMSC 4.2 Alarm Reference Manual


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

120 of 492

3: Hardware Agent Alarms

DRAFT

Langley 4 Alarms

System Impact

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

Recommended
Corrective Action

This trap indicates a user removal of a power supply unit.


If this is not a planned event, contact Comverse customer
support.

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

3.3.21

Alarm 4090121
Specific Problem

4090121

Managed Object

Langley 4

Description

The power supply <PowerSupply> has failed.

Additional
Information

<PowerSupply>

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 4090116

System Impact

Another power supply failure might cause the server to fail.

Recommended
Corrective Action

One of the power supply units has failed. Contact Comverse


customer support.

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

3.3.22

Alarm 4090122
Specific Problem

4090122

Managed Object

Langley 4

Description

Failure of this power supply <PowerSupply> has been


predicted.

Additional
Information

<PowerSupply>

Severity

Minor

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 4090116

SMSC 4.2 Alarm Reference Manual


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

121 of 492

3: Hardware Agent Alarms

DRAFT

Langley 4 Alarms

System Impact

Power supply will fail.

Recommended
Corrective Action

One of the power supply units is predicted to fail. Replacement


of this power supply unit is recommended. Contact Comverse
customer support.

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

3.3.23

Alarm 4090123
Specific Problem

4090123

Managed Object

Langley 4

Description

The power supply <PowerSupply> AC/DC connection has


been lost.

Additional
Information

<PowerSupply>

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 4090116

System Impact

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

Recommended
Corrective Action

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

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

3.3.24

Alarm 4090125
Specific Problem

4090125

Managed Object

Langley 4

Description

<VoltageSensor>: Current reading is below lower


nonrecoverable threshold. Status for this sensor is
nonrecoverable.

Additional
Information

<VoltageSensor>

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 4090128

SMSC 4.2 Alarm Reference Manual


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

122 of 492

3: Hardware Agent Alarms

Threshold

DRAFT

Langley 4 Alarms

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.

Recommended
Corrective Action

There a problem with one of the servers voltages. Contact


Comverse customer support.

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

3.3.25

Alarm 4090126
Specific Problem

4090126

Managed Object

Langley 4

Description

<VoltageSensor>: Current reading is below lower critical


threshold. Status for this sensor is critical.

Additional
Information

<VoltageSensor>

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 4090128

SMSC 4.2 Alarm Reference Manual


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

123 of 492

3: Hardware Agent Alarms

Threshold

DRAFT

Langley 4 Alarms

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

The server might fail either partially or completely.

Recommended
Corrective Action

One or more of the servers voltages is below the lower critical


threshold. Contact Comverse customer support.

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

3.3.26

Alarm 4090127
Specific Problem

4090127

Managed Object

Langley 4

Description

<VoltageSensor>: Current reading is below lower noncritical


threshold. Status for this sensor is noncritical.

Additional
Information

<VoltageSensor>

Severity

Minor

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 4090128

SMSC 4.2 Alarm Reference Manual


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

124 of 492

3: Hardware Agent Alarms

Threshold

DRAFT

Langley 4 Alarms

Baseboard 1.2V: 1.10


Baseboard 1.25V: 1.05
Baseboard 1.8V: 1.65
Baseboard 1.8VSB: 1.65
Baseboard 2.5V: 2.22
Baseboard 3.3V: 3.08
Baseboard 3.3AUX: 3.00
Baseboard 5.0V: 4.68
Baseboard 5VSB: 4.58
Baseboard 12V: 11.16
Baseboard 12VRM: 10.91
Baseboard -12V: -13.41
Baseboard VBAT: 2.76 Processor Vccp: 1.09

System Impact

The server might fail either partially or completely.

Recommended
Corrective Action

One or more of the servers voltages is below the lower


noncritical threshold. No immediate action is required;
however, action is required if there is an escalated trap.

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

3.3.27

Alarm 4090128
Specific Problem

4090128

Managed Object

Langley 4

Description

<VoltageSensor>: Current reading is within normal thresholds,


status is OK.

Additional
Information

<VoltageSensor>

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

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

3.3.28

Alarm 4090129
Specific Problem

4090129

Managed Object

Langley 4

SMSC 4.2 Alarm Reference Manual


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

125 of 492

3: Hardware Agent Alarms

DRAFT

Langley 4 Alarms

Description

<VoltageSensor>: Current reading exceeds upper noncritical


threshold. Status for this sensor is noncritical.

Additional
Information

<VoltageSensor>

Severity

Minor

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 4090128

Threshold

Baseboard 1.2V: 1.29


Baseboard 1.25V: 1.45
Baseboard 1.8V: 1.92
Baseboard 1.8VSB: 1.92
Baseboard 2.5V: 2.74
Baseboard 3.3V: 3.54
Baseboard 3.3AUX: 3.59
Baseboard 5.0V: 5.33
Baseboard 5VSB: 5.45
Baseboard 12V: 12.71
Baseboard 12VRM: 12.96
Baseboard -12V: -10.74
Baseboard VBAT: 3.52 Processor Vccp: 1.88

System Impact

High voltage might cause the server to fail.

Recommended
Corrective Action

A voltage value went above its upper noncritical value. No


immediate action is required; however, action is required if
there is an escalated trap.

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

3.3.29

Alarm 4090130
Specific Problem

4090130

Managed Object

Langley 4

Description

<VoltageSensor>: Current reading exceeds upper critical


threshold. Status for this sensor is critical.

Additional
Information

<VoltageSensor>

Severity

Critical

Message Group
(Probable Cause)

Hardware

SMSC 4.2 Alarm Reference Manual


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

126 of 492

3: Hardware Agent Alarms

DRAFT

Alarm Automatically
Cleared

Yes; by 4090128

Threshold

Langley 4 Alarms

Baseboard 1.2V: 1.33


Baseboard 1.25V: 1.49
Baseboard 1.8V: 1.98
Baseboard 1.8VSB: 1.98
Baseboard 2.5V: 2.83
Baseboard 3.3V: 3.64
Baseboard 3.3AUX: 3.69
Baseboard 5.0V: 5.49
Baseboard 5VSB: 5.62
Baseboard 12V: 13.08
Baseboard 12VRM: 13.39
Baseboard -12V: -10.46
Baseboard VBAT: 3.63 Processor Vccp: 1.94

System Impact

The server might fail either partially or completely.

Recommended
Corrective Action

A voltage value went above its upper critical value. Contact


Comverse customer support.

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

3.3.30

Alarm 4090131
Specific Problem

4090131

Managed Object

Langley 4

Description

<VoltageSensor>: Current reading exceeds upper


nonrecoverable threshold. Status for this sensor is
nonrecoverable.

Additional
Information

<VoltageSensor>

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 4090128

SMSC 4.2 Alarm Reference Manual


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

127 of 492

3: Hardware Agent Alarms

Threshold

DRAFT

Langley 4 Alarms

Baseboard 1.2V: 1.33


Baseboard 1.25V: 1.49
Baseboard 1.8V: 1.98
Baseboard 1.8VSB: 1.98
Baseboard 2.5V: 2.83
Baseboard 3.3V: 3.64
Baseboard 3.3AUX: 3.69
Baseboard 5.0V: 5.49
Baseboard 5VSB: 5.62
Baseboard 12V: 13.08
Baseboard 12VRM: 13.39
Baseboard -12V: -10.46
Baseboard VBAT: 3.63 Processor Vccp: 1.94

System Impact

Server failure might be imminent.

Recommended
Corrective Action

There a problem with one of the servers voltages. Contact


Comverse customer support

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

3.3.31

Alarm 4090132
Specific Problem

4090132

Managed Object

Langley 4

Description

The discrete voltage sensor meets performance standards:


<VoltageSensor>.

Additional
Information

<VoltageSensor>

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

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

3.3.32

Alarm 4090133
Specific Problem

4090133

Managed Object

Langley 4

SMSC 4.2 Alarm Reference Manual


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

128 of 492

3: Hardware Agent Alarms

DRAFT

Langley 4 Alarms

Description

The discrete voltage sensor lags from performance standards:


<VoltageSensor>.

Additional
Information

<VoltageSensor>

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 4090132

System Impact

The server might have degraded performance or might shut


down.

Recommended
Corrective Action

The specified voltage value has reached its critical value.


Contact Comverse customer support.

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

3.3.33

Alarm 4090134
Specific Problem

4090134

Managed Object

Langley 4

Description

A single-bit error occurred in memory.

Additional
Information

Memory

Severity

Warning

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Recommended
Corrective Action

A single-bit error occurred in memory and was corrected by


the ECC mechanism. If this event occurs frequently, one or
more memory DIMMs might need to be replaced.

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

3.3.34

Alarm 4090135
Specific Problem

4090135

Managed Object

Langley 4

Description

A multi-bit error occurred in memory.

Additional
Information

Memory

SMSC 4.2 Alarm Reference Manual


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

129 of 492

3: Hardware Agent Alarms

DRAFT

Langley 4 Alarms

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Software applications running on the server might crash or


run with errors.

Recommended
Corrective Action

One or more memory DIMMs must be replaced. Contact


Comverse customer support.

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

3.3.35

Alarm 4090136
Specific Problem

4090136

Managed Object

Langley 4

Description

A parity error occurred in memory.

Additional
Information

Memory

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Software applications running on the server might crash or


run with errors.

Recommended
Corrective Action

If this trap appears frequently, one or more memory DIMMs


must be replaced. Contact Comverse customer support.

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

3.3.36

Alarm 4090137
Specific Problem

4090137

Managed Object

Langley 4

Description

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

Additional
Information

Memory

Severity

Major

Message Group
(Probable Cause)

Hardware

SMSC 4.2 Alarm Reference Manual


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

130 of 492

3: Hardware Agent Alarms

DRAFT

Langley 4 Alarms

Alarm Automatically
Cleared

No

System Impact

Server performance and data integrity might be degraded.

Recommended
Corrective Action

There might be issues with memory integrity. Contact


Comverse customer support.

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

3.3.37

Alarm 4090138
Specific Problem

4090138

Managed Object

Langley 4

Description

Memory device was disabled.

Additional
Information

Memory

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

The servers memory capacity will be reduced, and


performance might be degraded.

Recommended
Corrective Action

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

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

3.3.38

Alarm 4090139
Specific Problem

4090139

Managed Object

Langley 4

Description

Correctable error logging limit reached for memory device.

Additional
Information

Memory

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

SMSC 4.2 Alarm Reference Manual


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

131 of 492

3: Hardware Agent Alarms

DRAFT

Langley 4 Alarms

System Impact

Server performance and data integrity might be degraded.

Recommended
Corrective Action

There might be issues with memory integrity. Contact


Comverse customer support.

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

3.3.39

Alarm 4090140
Specific Problem

4090140

Managed Object

Langley 4

Description

Cooling unit is fully redundant.

Additional
Information

Fan Redundancy

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

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

3.3.40

Alarm 4090141
Specific Problem

4090141

Managed Object

Langley 4

Description

Cooling unit redundancy has been degraded.

Additional
Information

Fan Redundancy

Severity

Minor

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 4090140

System Impact

Another cooling unit failure will cause the server to overheat


and shut down.

Recommended
Corrective Action

One or more system fans have failed. Contact Comverse


customer support.

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

SMSC 4.2 Alarm Reference Manual


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

132 of 492

3: Hardware Agent Alarms

3.3.41

DRAFT

Langley 4 Alarms

Alarm 4090142
Specific Problem

4090142

Managed Object

Langley 4

Description

Cooling unit redundancy has been lost.

Additional
Information

Fan Redundancy

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 4090140

System Impact

Server overheating might cause slow performance or a


complete server failure.

Recommended
Corrective Action

One or more system fans have failed. Contact Comverse


customer support.

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

3.3.42

Alarm 4090143
Specific Problem

4090143

Managed Object

Langley 4

Description

<fanSensor>: Current reading is below lower nonrecoverable


threshold. Status for this sensor is nonrecoverable.

Additional
Information

<fanSensor>

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 4090146

Threshold

80mm Sys Fan: 1836.00 40mm Sys Fan: 3264.00 Power


Cage Fan: 4500.00

System Impact

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

Recommended
Corrective Action

A system fan has failed. Contact Comverse customer support.

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

SMSC 4.2 Alarm Reference Manual


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

133 of 492

3: Hardware Agent Alarms

3.3.43

DRAFT

Langley 4 Alarms

Alarm 4090144
Specific Problem

4090144

Managed Object

Langley 4

Description

<fanSensor>: Current reading is below lower critical threshold.


Status for this sensor is critical.

Additional
Information

<fanSensor>

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 4090146

Threshold

80mm Sys Fan: 1836.00 40mm Sys Fan: 3264.00 Power


Cage Fan: 4500.00

System Impact

The server might fail either partially or completely.

Recommended
Corrective Action

A fan speed went below its critical speed threshold, probably


due to a fan failure. Contact Comverse customer support.

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

3.3.44

Alarm 4090145
Specific Problem

4090145

Managed Object

Langley 4

Description

<fanSensor>: Current reading is below lower noncritical


threshold. Status for this sensor is noncritical.

Additional
Information

<fanSensor>

Severity

Minor

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 4090146

Threshold

80mm Sys Fan: 1989.00 40mm Sys Fan: 3774.00 Power


Cage Fan: 4980.00

System Impact

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

Recommended
Corrective Action

A fan speed went below its noncritical speed threshold. No


immediate action is required; however, action is required if
there is an escalated trap.

For a detailed description of these rows, see Alarm Fields Description, Page 7.
SMSC 4.2 Alarm Reference Manual
P/N 10-000-1050 Issue 1 Rev. 0.1

134 of 492

3: Hardware Agent Alarms

3.3.45

DRAFT

Langley 4 Alarms

Alarm 4090146
Specific Problem

4090146

Managed Object

Langley 4

Description

<fanSensor>: Current reading is within normal thresholds,


status is OK.

Additional
Information

<fanSensor>

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

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

3.3.46

Alarm 4090147
Specific Problem

4090147

Managed Object

Langley 4

Description

The discrete cooling device meets performance standards:


<fanSensor>.

Additional
Information

<fanSensor>

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

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

3.3.47

Alarm 4090148
Specific Problem

4090148

Managed Object

Langley 4

Description

The discrete cooling device lags from performance standards:


<fanSensor>.

Additional
Information

<fanSensor>

SMSC 4.2 Alarm Reference Manual


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

135 of 492

3: Hardware Agent Alarms

DRAFT

Langley 4 Alarms

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 4090147

System Impact

Server overheating might cause slow performance or a


complete server failure.

Recommended
Corrective Action

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

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

3.3.48

Alarm 4090149
Specific Problem

4090149

Managed Object

Langley 4

Description

<tempSensor>: Current reading is below lower nonrecoverable


threshold. Status for this sensor is nonrecoverable.

Additional
Information

<tempSensor>

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

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 servers integrity at risk.

Recommended
Corrective Action

There is a problem with the temperature sensor. Contact


Comverse customer support.

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

3.3.49

Alarm 4090150
Specific Problem

4090150

Managed Object

Langley 4

SMSC 4.2 Alarm Reference Manual


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

136 of 492

3: Hardware Agent Alarms

DRAFT

Langley 4 Alarms

Description

<tempSensor>: Current reading is below lower critical


threshold. Status for this sensor is critical.

Additional
Information

<tempSensor>

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

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 might fail either partially or completely.

Recommended
Corrective Action

The servers temperature value went below its lower critical


value. Ensure that the servers environment is providing the
proper ambient temperature. If it is, and the problem remains,
contact Comverse customer support.

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

3.3.50

Alarm 4090151
Specific Problem

4090151

Managed Object

Langley 4

Description

<tempSensor>: Current reading is below lower noncritical


threshold. Status for this sensor is noncritical.

Additional
Information

<tempSensor>

Severity

Minor

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 4090152

Threshold

SMSC 4.2 Alarm Reference Manual


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

Baseboard Temp: -5.00


FntPnl Amb Temp: -5.00
Power Cage Temp: -5.00
Processor1 Temp: -5.00
Processor2 Temp: -5.00

137 of 492

3: Hardware Agent Alarms

DRAFT

Langley 4 Alarms

System Impact

Too low temperature might cause the server to fail.

Recommended
Corrective Action

The servers temperature value went below its lower


noncritical value. Ensure that the servers environment is
providing the proper ambient temperature. Further action is
required if there is an escalated trap.

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

3.3.51

Alarm 4090152
Specific Problem

4090152

Managed Object

Langley 4

Description

<tempSensor>: Current reading is within normal thresholds,


status is OK.

Additional
Information

<tempSensor>

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

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

3.3.52

Alarm 4090153
Specific Problem

4090153

Managed Object

Langley 4

Description

Current reading exceeds upper noncritical threshold. Status


for this sensor is noncritical.

Additional
Information

<tempSensor>

Severity

Minor

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 4090152

SMSC 4.2 Alarm Reference Manual


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

138 of 492

3: Hardware Agent Alarms

Threshold

DRAFT

Langley 4 Alarms

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.

Recommended
Corrective Action

The servers temperature value went above its lower


noncritical value. Ensure that the servers environment is
providing the proper ambient temperature. Further action is
required if there is an escalated trap.

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

3.3.53

Alarm 4090154
Specific Problem

4090154

Managed Object

Langley 4

Description

<tempSensor>: Current reading exceeds upper critical


threshold. Status for this sensor is critical.

Additional
Information

<tempSensor>

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 4090152

Threshold

Baseboard Temp: 65.00


FntPnl Amb Temp: 45.00
Power Cage Temp: 65.00
Processor1 Temp: 80.00
Processor2 Temp: 80.00

System Impact

The server might fail either partially or completely.

Recommended
Corrective Action

The servers temperature value went above its lower critical


value. Ensure that the servers environment is providing the
proper ambient temperature. If it is, and the problem remains,
contact Comverse customer support.

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

3.3.54

Alarm 4090155

SMSC 4.2 Alarm Reference Manual


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

139 of 492

3: Hardware Agent Alarms

DRAFT

Langley 4 Alarms

Specific Problem

4090155

Managed Object

Langley 4

Description

<tempSensor>: Current reading exceeds upper


nonrecoverable threshold. Status for this sensor is
nonrecoverable.

Additional
Information

<tempSensor>

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 4090152

Threshold

Baseboard Temp: 65.00


FntPnl Amb Temp: 45.00
Power Cage Temp: 65.00
Processor1 Temp: 80.00
Processor2 Temp: 80.00

System Impact

The server will not be able to reliably report thermal issues,


which might put the servers integrity at risk.

Recommended
Corrective Action

There is a problem with the temperature sensor. Contact


Comverse customer support.

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

3.3.55

Alarm 4090156
Specific Problem

4090156

Managed Object

Langley 4

Description

The system BIOS has been reconfigured.

Additional
Information

System

Severity

Warning

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

BIOS changes might affect the servers performance and


stability.

Recommended
Corrective Action

The BIOS setup was changed. Contact Comverse customer


support to determine if this change was coordinated and
approved.

SMSC 4.2 Alarm Reference Manual


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

140 of 492

3: Hardware Agent Alarms

DRAFT

Langley 4 Alarms

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

3.3.56

Alarm 4090157
Specific Problem

4090157

Managed Object

Langley 4

Description

The system has booted.

Additional
Information

System

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

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

SMSC 4.2 Alarm Reference Manual


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

141 of 492

3: Hardware Agent Alarms

3.4

DRAFT

LSI Alarms

LSI Alarms
Search for the alarm you need by its Specific Problem (Alarm ID).

3.4.1

Alarm 3080001
Specific Problem

3080001

Managed Object

LSI

Description

A physical disk has been placed online.

Additional
Information

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

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

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

3.4.2

Alarm 3080003
Specific Problem

3080003

Managed Object

LSI

Description

Physical disk error found.

Additional
Information

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

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact. Hot spare disk will go online.

Recommended
Corrective Action

Replace the faulty disk.

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

3.4.3

Alarm 3080004

SMSC 4.2 Alarm Reference Manual


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

142 of 492

3: Hardware Agent Alarms

DRAFT

LSI Alarms

Specific Problem

3080004

Managed Object

LSI

Description

Physical disk PFA condition found.

Additional
Information

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

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact. If the disk fails, there is a hot spare disk that will
go online.

Recommended
Corrective Action

Contact Comverse customer support.

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

3.4.4

Alarm 3080005
Specific Problem

3080005

Managed Object

LSI

Description

Automatic rebuild has started.

Additional
Information

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

Severity

Warning

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3080007

System Impact

No impact.

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

3.4.5

Alarm 3080006
Specific Problem

3080006

Managed Object

LSI

Description

Rebuild has started.

Additional
Information

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

SMSC 4.2 Alarm Reference Manual


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

143 of 492

3: Hardware Agent Alarms

DRAFT

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

LSI Alarms

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

3.4.6

Alarm 3080007
Specific Problem

3080007

Managed Object

LSI

Description

Rebuild has been completed.

Additional
Information

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

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

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

3.4.7

Alarm 3080008
Specific Problem

3080008

Managed Object

LSI

Description

Rebuild has been cancelled.

Additional
Information

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

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact on data. The LUN will be in critical status, and disk


redundancy will be lost.

Recommended
Corrective Action

Check if this action was initiated by a user.

SMSC 4.2 Alarm Reference Manual


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

144 of 492

3: Hardware Agent Alarms

DRAFT

LSI Alarms

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

3.4.8

Alarm 3080009
Specific Problem

3080009

Managed Object

LSI

Description

Rebuild has been stopped with error.

Additional
Information

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

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Might cause data loss.

Recommended
Corrective Action

Check the LUN status and act accordingly.

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

3.4.9

Alarm 3080010
Specific Problem

3080010

Managed Object

LSI

Description

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

Additional
Information

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

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

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

Recommended
Corrective Action

Check the LUN status and act accordingly.

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

3.4.10

Alarm 3080011

SMSC 4.2 Alarm Reference Manual


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

145 of 492

3: Hardware Agent Alarms

DRAFT

Specific Problem

3080011

Managed Object

LSI

Description

Logical drive failed - rebuild has been stopped.

Additional
Information

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

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Downtime - LUN failed. Might cause data loss.

Recommended
Corrective Action

Check the LUN status and act accordingly.

LSI Alarms

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

3.4.11

Alarm 3080012
Specific Problem

3080012

Managed Object

LSI

Description

Physical disk has failed.

Additional
Information

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

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact. Hot spare disk will go online.

Recommended
Corrective Action

Replace the faulty disk.

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

3.4.12

Alarm 3080013
Specific Problem

3080013

Managed Object

LSI

Description

A new physical disk has been found.

SMSC 4.2 Alarm Reference Manual


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

146 of 492

3: Hardware Agent Alarms

DRAFT

Additional
Information

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

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

LSI Alarms

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

3.4.13

Alarm 3080014
Specific Problem

3080014

Managed Object

LSI

Description

Physical disk has been removed.

Additional
Information

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

Severity

Minor

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

Recommended
Corrective Action

Check if this action was initiated by a user.

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

3.4.14

Alarm 3080019
Specific Problem

3080019

Managed Object

LSI

Description

SCSI command time-out on physical disk.

Additional
Information

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

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

SMSC 4.2 Alarm Reference Manual


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

147 of 492

3: Hardware Agent Alarms

DRAFT

LSI Alarms

System Impact

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

Recommended
Corrective Action

Check the physical device status and replace if faulty.

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

3.4.15

Alarm 3080022
Specific Problem

3080022

Managed Object

LSI

Description

Parity error found.

Additional
Information

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

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact if all physical devices are online; otherwise, data


loss will occur.

Recommended
Corrective Action

Check the physical device status and replace if faulty.

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

3.4.16

Alarm 3080050
Specific Problem

3080050

Managed Object

LSI

Description

Physical disk status has changed to offline. The service is up


must be handled immediately (within 2 hours).

Additional
Information

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

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact. Hot spare disk will go online.

Recommended
Corrective Action

Replace the offline disk.

SMSC 4.2 Alarm Reference Manual


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

148 of 492

3: Hardware Agent Alarms

DRAFT

LSI Alarms

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

3.4.17

Alarm 3080051
Specific Problem

3080051

Managed Object

LSI

Description

Physical disk status has changed to hot spare.

Additional
Information

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

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

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

3.4.18

Alarm 3080052
Specific Problem

3080052

Managed Object

LSI

Description

Physical disk status has changed to rebuild.

Additional
Information

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

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

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

3.4.19

Alarm 3080054
Specific Problem

3080054

Managed Object

LSI

Description

Physical disk failed to start.

SMSC 4.2 Alarm Reference Manual


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

149 of 492

3: Hardware Agent Alarms

DRAFT

Additional
Information

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

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

Recommended
Corrective Action

Replace the faulty disk.

LSI Alarms

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

3.4.20

Alarm 3080059
Specific Problem

3080059

Managed Object

LSI

Description

Physical disk is switching from one channel to the other


channel.

Additional
Information

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

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

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


Loss of FC loop redundancy in case of loop failure.

Recommended
Corrective Action

If only a single disk shows this alarm, replace it; otherwise,


contact Comverse customer support.

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

3.4.21

Alarm 3080067
Specific Problem

3080067

Managed Object

LSI

Description

Physical disk found on only one disk channel.

Additional
Information

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

Severity

Major

SMSC 4.2 Alarm Reference Manual


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

150 of 492

3: Hardware Agent Alarms

DRAFT

LSI Alarms

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

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


Loss of FC loop redundancy in case of loop failure.

Recommended
Corrective Action

If only a single disk shows this alarm, replace it; otherwise,


contact Comverse customer support.

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

3.4.22

Alarm 3080068
Specific Problem

3080068

Managed Object

LSI

Description

Physical disk type is not approved by vendor.

Additional
Information

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

Severity

Minor

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

Recommended
Corrective Action

Replace the disk with an approved type.

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

3.4.23

Alarm 3080069
Specific Problem

3080069

Managed Object

LSI

Description

Physical disk has acquired an inappropriate loop ID. Enclosure


disk-slot operations are disabled while this condition persists.

Additional
Information

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

Severity

Major

Message Group
(Probable Cause)

Hardware

SMSC 4.2 Alarm Reference Manual


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

151 of 492

3: Hardware Agent Alarms

DRAFT

Alarm Automatically
Cleared

No

System Impact

No impact.

Recommended
Corrective Action

Replace the disk.

LSI Alarms

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

3.4.24

Alarm 3080070
Specific Problem

3080070

Managed Object

LSI

Description

Physical disk port has failed or cannot operate at the


configured channel speed.

Additional
Information

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

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

Recommended
Corrective Action

Replace the disk.

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

3.4.25

Alarm 3080071
Specific Problem

3080071

Managed Object

LSI

Description

Mirror Race recovery has failed for logical drive.

Additional
Information

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

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

SMSC 4.2 Alarm Reference Manual


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

152 of 492

3: Hardware Agent Alarms

DRAFT

LSI Alarms

System Impact

If LUN is offline, the system will be down.

Recommended
Corrective Action

Contact Comverse customer support to check the LUN status.

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

3.4.26

Alarm 3080073
Specific Problem

3080073

Managed Object

LSI

Description

Online controller firmware upgrade has started.

Additional
Information

Controller: <$2>

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Downtime during controller firmware upgrade.

Recommended
Corrective Action

Check if this action was initiated by a user. This action should


not be done while the system is online.

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

3.4.27

Alarm 3080074
Specific Problem

3080074

Managed Object

LSI

Description

Online firmware upgrade has been completed successfully.

Additional
Information

Controller: <$2>

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

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

SMSC 4.2 Alarm Reference Manual


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

153 of 492

3: Hardware Agent Alarms

3.4.28

DRAFT

LSI Alarms

Alarm 3080075
Specific Problem

3080075

Managed Object

LSI

Description

Online firmware upgrade has failed.

Additional
Information

Controller: <$2>

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact. System is down during this operation.

Recommended
Corrective Action

This alarm occurs when a storage expert is upgrading the


system.

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

3.4.29

Alarm 3080096
Specific Problem

3080096

Managed Object

LSI

Description

Device loop ID conflict (soft addressing) detected.

Additional
Information

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

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Risk of data corruption.

Recommended
Corrective Action

A conflict was detected on a disk channel, causing soft


addressing, which can lead to data corruption. This usually
occurs when you have DF4000 with expansion JBODs
attached and the DIP switches on the back of the enclosure(s)
have not been set properly. To correct this problem, check
the DIP switch, and set appropriately. If the problem persists,
contact Comverse customer support.

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

SMSC 4.2 Alarm Reference Manual


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

154 of 492

3: Hardware Agent Alarms

3.4.30

DRAFT

LSI Alarms

Alarm 3080098
Specific Problem

3080098

Managed Object

LSI

Description

The host fiber channel is down.

Additional
Information

Controller: <$2>

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3080099

System Impact

Loss of storage path redundancy.

Recommended
Corrective Action

Check the fiber channel to host.

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

3.4.31

Alarm 3080099
Specific Problem

3080099

Managed Object

LSI

Description

The host fiber channel is up.

Additional
Information

Controller: <$2>

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

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

3.4.32

Alarm 3080128
Specific Problem

3080128

Managed Object

LSI

Description

Consistency check has started.

SMSC 4.2 Alarm Reference Manual


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

155 of 492

3: Hardware Agent Alarms

DRAFT

Additional
Information

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

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

Recommended
Corrective Action

Check the DIP switch, and set appropriately.

LSI Alarms

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

3.4.33

Alarm 3080129
Specific Problem

3080129

Managed Object

LSI

Description

Consistency check has finished.

Additional
Information

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

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

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

3.4.34

Alarm 3080130
Specific Problem

3080130

Managed Object

LSI

Description

Consistency check has been cancelled.

Additional
Information

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

Severity

Normal

Message Group
(Probable Cause)

Hardware

SMSC 4.2 Alarm Reference Manual


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

156 of 492

3: Hardware Agent Alarms

DRAFT

Alarm Automatically
Cleared

No

System Impact

No impact.

LSI Alarms

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

3.4.35

Alarm 3080131
Specific Problem

3080131

Managed Object

LSI

Description

Consistency check on logical drive error.

Additional
Information

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

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

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

Recommended
Corrective Action

Replace the faulty disk.

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

3.4.36

Alarm 3080132
Specific Problem

3080132

Managed Object

LSI

Description

Consistency check on logical drive has failed.

Additional
Information

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

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

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

Recommended
Corrective Action

Replace the faulty disk.

For a detailed description of these rows, see Alarm Fields Description, Page 7.
SMSC 4.2 Alarm Reference Manual
P/N 10-000-1050 Issue 1 Rev. 0.1

157 of 492

3: Hardware Agent Alarms

3.4.37

DRAFT

LSI Alarms

Alarm 3080133
Specific Problem

3080133

Managed Object

LSI

Description

Consistency check has failed due to physical disk failure.

Additional
Information

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

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

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

Recommended
Corrective Action

Replace the faulty disk.

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

3.4.38

Alarm 3080134
Specific Problem

3080134

Managed Object

LSI

Description

Logical drive has been made offline.

Additional
Information

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

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Downtime - LUN is offline. Causes data loss.

Recommended
Corrective Action

Contact Comverse customer support.

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

3.4.39

Alarm 3080135
Specific Problem

3080135

Managed Object

LSI

SMSC 4.2 Alarm Reference Manual


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

158 of 492

3: Hardware Agent Alarms

DRAFT

LSI Alarms

Description

Logical drive is critical.

Additional
Information

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

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3080136

System Impact

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

Recommended
Corrective Action

Contact Comverse customer support.

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

3.4.40

Alarm 3080136
Specific Problem

3080136

Managed Object

LSI

Description

Logical drive has been placed online.

Additional
Information

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

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

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

3.4.41

Alarm 3080144
Specific Problem

3080144

Managed Object

LSI

Description

Logical drive initialization has started.

Additional
Information

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

Severity

Normal

Message Group
(Probable Cause)

Hardware

SMSC 4.2 Alarm Reference Manual


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

159 of 492

3: Hardware Agent Alarms

DRAFT

LSI Alarms

Alarm Automatically
Cleared

No

System Impact

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

Recommended
Corrective Action

Check if this action was initiated by a user. This action erases


all storage data.

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

3.4.42

Alarm 3080145
Specific Problem

3080145

Managed Object

LSI

Description

Logical drive initialization is done.

Additional
Information

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

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

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

Recommended
Corrective Action

Check if this action was initiated by a user. This action erases


all storage data.

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

3.4.43

Alarm 3080146
Specific Problem

3080146

Managed Object

LSI

Description

Logical drive initialization has been cancelled.

Additional
Information

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

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

SMSC 4.2 Alarm Reference Manual


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

160 of 492

3: Hardware Agent Alarms

DRAFT

LSI Alarms

System Impact

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

Recommended
Corrective Action

Check if this action was initiated by a user. This action erases


all storage data.

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

3.4.44

Alarm 3080147
Specific Problem

3080147

Managed Object

LSI

Description

Logical drive initialization has failed.

Additional
Information

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

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

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

Recommended
Corrective Action

Check if this action was initiated by a user. This action erases


all storage data.

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

3.4.45

Alarm 3080150
Specific Problem

3080150

Managed Object

LSI

Description

Expand capacity has started.

Additional
Information

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

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

Recommended
Corrective Action

Check if this action was initiated by a user.

SMSC 4.2 Alarm Reference Manual


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

161 of 492

3: Hardware Agent Alarms

DRAFT

LSI Alarms

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

3.4.46

Alarm 3080151
Specific Problem

3080151

Managed Object

LSI

Description

Expand capacity has been completed.

Additional
Information

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

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

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

3.4.47

Alarm 3080152
Specific Problem

3080152

Managed Object

LSI

Description

Expand capacity has stopped with error.

Additional
Information

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

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Impact only for the expanded capacity activity.

Recommended
Corrective Action

This action must only be done by a storage expert who checks


for a reason in case of error.

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

3.4.48

Alarm 3080153
Specific Problem

3080153

Managed Object

LSI

SMSC 4.2 Alarm Reference Manual


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

162 of 492

3: Hardware Agent Alarms

DRAFT

LSI Alarms

Description

Bad blocks have been found.

Additional
Information

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

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact. Bad blocks may result in disk failure and in this


case, loss of disk redundancy.

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

3.4.49

Alarm 3080157
Specific Problem

3080157

Managed Object

LSI

Description

Logical drive LUN mapping has been written to configuration.

Additional
Information

Controller: <$2>

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

Recommended
Corrective Action

Check if this action was initiated by a user.

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

3.4.50

Alarm 3080176
Specific Problem

3080176

Managed Object

LSI

Description

Logical drive background initialization has started.

Additional
Information

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

Severity

Normal

Message Group
(Probable Cause)

Hardware

SMSC 4.2 Alarm Reference Manual


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

163 of 492

3: Hardware Agent Alarms

DRAFT

LSI Alarms

Alarm Automatically
Cleared

No

System Impact

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

Recommended
Corrective Action

Check if this action was initiated by a user. This action erases


all storage data.

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

3.4.51

Alarm 3080177
Specific Problem

3080177

Managed Object

LSI

Description

Logical drive background initialization has stopped.

Additional
Information

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

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

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

Recommended
Corrective Action

Check if this action was initiated by a user. This action erases


all storage data.

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

3.4.52

Alarm 3080178
Specific Problem

3080178

Managed Object

LSI

Description

Logical drive background initialization has been paused.

Additional
Information

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

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

SMSC 4.2 Alarm Reference Manual


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

164 of 492

3: Hardware Agent Alarms

DRAFT

LSI Alarms

System Impact

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

Recommended
Corrective Action

Check if this action was initiated by a user. This action erases


all storage data.

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

3.4.53

Alarm 3080179
Specific Problem

3080179

Managed Object

LSI

Description

Logical drive background initialization has restarted.

Additional
Information

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

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

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

Recommended
Corrective Action

Check if this action was initiated by a user. This action erases


all storage data.

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

3.4.54

Alarm 3080180
Specific Problem

3080180

Managed Object

LSI

Description

Logical drive background initialization has failed.

Additional
Information

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

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

SMSC 4.2 Alarm Reference Manual


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

165 of 492

3: Hardware Agent Alarms

DRAFT

LSI Alarms

System Impact

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

Recommended
Corrective Action

Check if this action was initiated by a user. This action erases


all storage data.

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

3.4.55

Alarm 3080181
Specific Problem

3080181

Managed Object

LSI

Description

Logical drive background initialization has been completed.

Additional
Information

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

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

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

Recommended
Corrective Action

Check if this action was initiated by a user. This action erases


all storage data.

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

3.4.56

Alarm 3080320
Specific Problem

3080320

Managed Object

LSI

Description

Fan failure.

Additional
Information

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

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3080321

System Impact

Loss of cooling redundancy.

Recommended
Corrective Action

Replace the fan.

SMSC 4.2 Alarm Reference Manual


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

166 of 492

3: Hardware Agent Alarms

DRAFT

LSI Alarms

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

3.4.57

Alarm 3080321
Specific Problem

3080321

Managed Object

LSI

Description

Fan has been restored.

Additional
Information

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

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

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

3.4.58

Alarm 3080322
Specific Problem

3080322

Managed Object

LSI

Description

Fan is not present.

Additional
Information

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

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3080321

System Impact

Loss of cooling redundancy.

Recommended
Corrective Action

Insert the fan module.

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

3.4.59

Alarm 3080323
Specific Problem

3080323

Managed Object

LSI

SMSC 4.2 Alarm Reference Manual


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

167 of 492

3: Hardware Agent Alarms

DRAFT

Description

Power supply failure.

Additional
Information

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

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3080324

System Impact

Loss of power supply redundancy.

Recommended
Corrective Action

Replace the power supply.

LSI Alarms

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

3.4.60

Alarm 3080324
Specific Problem

3080324

Managed Object

LSI

Description

Power supply has been restored.

Additional
Information

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

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

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

3.4.61

Alarm 3080325
Specific Problem

3080325

Managed Object

LSI

Description

Power supply is not present.

Additional
Information

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

Severity

Major

Message Group
(Probable Cause)

Hardware

SMSC 4.2 Alarm Reference Manual


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

168 of 492

3: Hardware Agent Alarms

DRAFT

LSI Alarms

Alarm Automatically
Cleared

Yes; by 3080324

System Impact

Loss of power supply redundancy.

Recommended
Corrective Action

Contact Comverse customer support to check power status.

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

3.4.62

Alarm 3080326
Specific Problem

3080326

Managed Object

LSI

Description

Temperature is over safe limit. Failure imminent.

Additional
Information

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

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3080328

Threshold

68 C

System Impact

Danger of downtime due to high system temperature.

Recommended
Corrective Action

Check temperature at the site.

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

3.4.63

Alarm 3080327
Specific Problem

3080327

Managed Object

LSI

Description

Temperature is above working limit.

Additional
Information

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

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3080328

Threshold

64 C

SMSC 4.2 Alarm Reference Manual


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

169 of 492

3: Hardware Agent Alarms

DRAFT

LSI Alarms

System Impact

Danger of downtime due to high system temperature.

Recommended
Corrective Action

Check temperature at the site.

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

3.4.64

Alarm 3080328
Specific Problem

3080328

Managed Object

LSI

Description

Normal temperature has been restored.

Additional
Information

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

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

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

3.4.65

Alarm 3080329
Specific Problem

3080329

Managed Object

LSI

Description

Temperature sensor is not present.

Additional
Information

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

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact. System is exposed to high temperature with no


alarm. Repair action is needed.

Recommended
Corrective Action

Contact Comverse customer support about the temperature


sensor.

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

SMSC 4.2 Alarm Reference Manual


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

170 of 492

3: Hardware Agent Alarms

3.4.66

DRAFT

LSI Alarms

Alarm 3080331
Specific Problem

3080331

Managed Object

LSI

Description

Enclosure access has been restored.

Additional
Information

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

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

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

3.4.67

Alarm 3080332
Specific Problem

3080332

Managed Object

LSI

Description

Enclosure access is offline.

Additional
Information

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

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3080331

System Impact

No impact.

Recommended
Corrective Action

If no other component failure is reported, a reset to the


controller may be needed. Contact Comverse customer
support for more help.

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

3.4.68

Alarm 3080333
Specific Problem

3080333

Managed Object

LSI

Description

Enclosure soft addressing detected.

SMSC 4.2 Alarm Reference Manual


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

171 of 492

3: Hardware Agent Alarms

DRAFT

LSI Alarms

Additional
Information

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

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Risk of data corruption.

Recommended
Corrective Action

A conflict was detected on a disk channel, causing soft


addressing, which can lead to data corruption. This usually
occurs when you have DF4000 with expansion JBODs
attached and the DIP switches on the back of the enclosure(s)
have not been set properly. To correct this problem, check
the DIP switch, and set appropriately. If the problem persists,
contact Comverse customer support.

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

3.4.69

Alarm 3080334
Specific Problem

3080334

Managed Object

LSI

Description

Enclosure services ready.

Additional
Information

Controller: <$2>

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

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

3.4.70

Alarm 3080335
Specific Problem

3080335

Managed Object

LSI

Description

Access to temperature sensor has been lost.

Additional
Information

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

Severity

Major

SMSC 4.2 Alarm Reference Manual


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

172 of 492

3: Hardware Agent Alarms

DRAFT

LSI Alarms

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact. System is exposed to high temperature with no


alarm. Repair action is needed.

Recommended
Corrective Action

Verify that the I/O card is in place. Contact Comverse


customer support for more help.

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

3.4.71

Alarm 3080336
Specific Problem

3080336

Managed Object

LSI

Description

Access to power supply status information has been lost.

Additional
Information

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

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

Recommended
Corrective Action

Contact Comverse customer support.

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

3.4.72

Alarm 3080337
Specific Problem

3080337

Managed Object

LSI

Description

Access to fan status information has been lost.

Additional
Information

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

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

SMSC 4.2 Alarm Reference Manual


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

173 of 492

3: Hardware Agent Alarms

DRAFT

System Impact

No impact.

Recommended
Corrective Action

Contact Comverse customer support.

LSI Alarms

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

3.4.73

Alarm 3080338
Specific Problem

3080338

Managed Object

LSI

Description

Physical disks in enclosure are being spun down.

Additional
Information

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

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Might result in data corruption or downtime.

Recommended
Corrective Action

Contact Comverse customer support.

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

3.4.74

Alarm 3080339
Specific Problem

3080339

Managed Object

LSI

Description

Temperature is below working limit.

Additional
Information

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

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3080328

Threshold

25 C

System Impact

Danger of downtime due to low system temperature.

Recommended
Corrective Action

Check the temperature at the site.

SMSC 4.2 Alarm Reference Manual


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

174 of 492

3: Hardware Agent Alarms

DRAFT

LSI Alarms

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

3.4.75

Alarm 3080340
Specific Problem

3080340

Managed Object

LSI

Description

Temperature is under safe limit. Failure imminent.

Additional
Information

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

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3080328

Threshold

15 C

System Impact

Danger of downtime due to low system temperature.

Recommended
Corrective Action

Check the temperature at the site.

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

3.4.76

Alarm 3080384
Specific Problem

3080384

Managed Object

LSI

Description

Array management server software started successfully.

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact

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

3.4.77

Alarm 3080389
Specific Problem

3080389

Managed Object

LSI

SMSC 4.2 Alarm Reference Manual


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

175 of 492

3: Hardware Agent Alarms

DRAFT

LSI Alarms

Description

Controller has been reset.

Additional
Information

Controller: <$2>

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Downtime during controller reset.

Recommended
Corrective Action

Check if this action was initiated by a user during system


downtime. Contact Comverse customer support.

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

3.4.78

Alarm 3080392
Specific Problem

3080392

Managed Object

LSI

Description

Battery present.

Additional
Information

Controller: <$2>

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

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

3.4.79

Alarm 3080393
Specific Problem

3080393

Managed Object

LSI

Description

Battery power low.

Additional
Information

Controller: <$2>

Severity

Major

Message Group
(Probable Cause)

Hardware

SMSC 4.2 Alarm Reference Manual


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

176 of 492

3: Hardware Agent Alarms

DRAFT

LSI Alarms

Alarm Automatically
Cleared

Yes; by 3080394

System Impact

Causes the system to work without cache, no impact on


system functionality.

Recommended
Corrective Action

Recharge or replace the battery.

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

3.4.80

Alarm 3080394
Specific Problem

3080394

Managed Object

LSI

Description

Battery power OK.

Additional
Information

Controller: <$2>

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

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

3.4.81

Alarm 3080400
Specific Problem

3080400

Managed Object

LSI

Description

Battery reconditioning has started.

Additional
Information

Controller: <$2>

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

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

SMSC 4.2 Alarm Reference Manual


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

177 of 492

3: Hardware Agent Alarms

3.4.82

DRAFT

LSI Alarms

Alarm 3080401
Specific Problem

3080401

Managed Object

LSI

Description

Battery reconditioning has finished.

Additional
Information

Controller: <$2>

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

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

3.4.83

Alarm 3080402
Specific Problem

3080402

Managed Object

LSI

Description

Battery reconditioning has been canceled.

Additional
Information

Controller: <$2>

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

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

3.4.84

Alarm 3080405
Specific Problem

3080405

Managed Object

LSI

Description

The Battery Backup Unit has been removed.

Additional
Information

Controller: <$2>

SMSC 4.2 Alarm Reference Manual


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

178 of 492

3: Hardware Agent Alarms

DRAFT

LSI Alarms

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3080392

System Impact

Causes the system to work without cache, no impact on


system functionality.

Recommended
Corrective Action

Replace the battery component.

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

3.4.85

Alarm 3080406
Specific Problem

3080406

Managed Object

LSI

Description

WARM BOOT has failed.

Additional
Information

Controller: <$2>

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Might result in downtime.

Recommended
Corrective Action

Contact Comverse customer support.

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

3.4.86

Alarm 3080407
Specific Problem

3080407

Managed Object

LSI

Description

Battery calibration cycle has started.

Additional
Information

Controller: <$2>

Severity

Normal

Message Group
(Probable Cause)

Hardware

SMSC 4.2 Alarm Reference Manual


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

179 of 492

3: Hardware Agent Alarms

DRAFT

Alarm Automatically
Cleared

No

System Impact

No impact.

LSI Alarms

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

3.4.87

Alarm 3080408
Specific Problem

3080408

Managed Object

LSI

Description

Battery calibration cycle has finished.

Additional
Information

Controller: <$2>

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

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

3.4.88

Alarm 3080409
Specific Problem

3080409

Managed Object

LSI

Description

Battery calibration cycle has been cancelled.

Additional
Information

Controller: <$2>

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

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

3.4.89

Alarm 3080410

SMSC 4.2 Alarm Reference Manual


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

180 of 492

3: Hardware Agent Alarms

DRAFT

LSI Alarms

Specific Problem

3080410

Managed Object

LSI

Description

Battery is not present.

Additional
Information

Controller: <$2>

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3080392

System Impact

Causes the system to work without cache, no impact on


system functionality.

Recommended
Corrective Action

Insert the BBU in the enclosure.

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

3.4.90

Alarm 3080411
Specific Problem

3080411

Managed Object

LSI

Description

Controller entered conservative cache mode.

Additional
Information

Controller: <$2>

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3080412

System Impact

Causes the system to work without cache, no impact on


system functionality.

Recommended
Corrective Action

Contact Comverse customer support.

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

3.4.91

Alarm 3080412
Specific Problem

3080412

Managed Object

LSI

Description

Controller entered normal cache mode.

SMSC 4.2 Alarm Reference Manual


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

181 of 492

3: Hardware Agent Alarms

DRAFT

Additional
Information

Controller: <$2>

Severity

Minor

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3080411

System Impact

No impact.

LSI Alarms

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

3.4.92

Alarm 3080413
Specific Problem

3080413

Managed Object

LSI

Description

Controller device start complete.

Additional
Information

Controller: <$2>

Severity

Minor

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

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

3.4.93

Alarm 3080414
Specific Problem

3080414

Managed Object

LSI

Description

Soft ECC error corrected.

Additional
Information

Controller: <$2>

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

SMSC 4.2 Alarm Reference Manual


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

182 of 492

3: Hardware Agent Alarms

DRAFT

System Impact

No impact.

Recommended
Corrective Action

Contact Comverse customer support.

LSI Alarms

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

3.4.94

Alarm 3080416
Specific Problem

3080416

Managed Object

LSI

Description

Battery recondition suggested.

Additional
Information

Controller: <$2>

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

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

3.4.95

Alarm 3080419
Specific Problem

3080419

Managed Object

LSI

Description

Updated partners status.

Additional
Information

Controller: <$2>

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

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

3.4.96

Alarm 3080420

SMSC 4.2 Alarm Reference Manual


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

183 of 492

3: Hardware Agent Alarms

DRAFT

Specific Problem

3080420

Managed Object

LSI

Description

Relinquished partner.

Additional
Information

Controller: <$2>

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

LSI Alarms

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

3.4.97

Alarm 3080422
Specific Problem

3080422

Managed Object

LSI

Description

Dual controllers enabled.

Additional
Information

Controller: <$2>

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

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

3.4.98

Alarm 3080423
Specific Problem

3080423

Managed Object

LSI

Description

Disabled partner.

Additional
Information

Controller: <$2>

Severity

Major

Message Group
(Probable Cause)

Hardware

SMSC 4.2 Alarm Reference Manual


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

184 of 492

3: Hardware Agent Alarms

DRAFT

LSI Alarms

Alarm Automatically
Cleared

No

System Impact

No impact. Loss of controller redundancy.

Recommended
Corrective Action

One of the two controllers is down. Check the controllers


health.

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

3.4.99

Alarm 3080424
Specific Problem

3080424

Managed Object

LSI

Description

Dual controllers entered nexus.

Additional
Information

Controller: <$2>

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

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

3.4.100

Alarm 3080425
Specific Problem

3080425

Managed Object

LSI

Description

Controller boot ROM image needs to be reloaded.

Additional
Information

Controller: <$2>

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact. Loss of controller redundancy.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.
SMSC 4.2 Alarm Reference Manual
P/N 10-000-1050 Issue 1 Rev. 0.1

185 of 492

3: Hardware Agent Alarms

3.4.101

DRAFT

LSI Alarms

Alarm 3080432
Specific Problem

3080432

Managed Object

LSI

Description

Dual-active automatic flash of replacement controller.

Additional
Information

Controller: <$2>

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

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

3.4.102

Alarm 3080434
Specific Problem

3080434

Managed Object

LSI

Description

Dual-active negotiation failed IDs.

Additional
Information

Controller: <$2>

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

Recommended
Corrective Action

Contact Comverse customer support.

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

3.4.103

Alarm 3080435
Specific Problem

3080435

Managed Object

LSI

Description

Dual-active negotiation failed board types.

SMSC 4.2 Alarm Reference Manual


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

186 of 492

3: Hardware Agent Alarms

DRAFT

Additional
Information

Controller: <$2>

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

Recommended
Corrective Action

Contact Comverse customer support.

LSI Alarms

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

3.4.104

Alarm 3080436
Specific Problem

3080436

Managed Object

LSI

Description

Dual-active negotiation failed disk channels.

Additional
Information

Controller: <$2>

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

Recommended
Corrective Action

Check the rear panel for orange LEDs. Contact Comverse


customer support.

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

3.4.105

Alarm 3080437
Specific Problem

3080437

Managed Object

LSI

Description

Dual-active negotiation failed host ports.

Additional
Information

Controller: <$2>

Severity

Major

Message Group
(Probable Cause)

Hardware

SMSC 4.2 Alarm Reference Manual


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

187 of 492

3: Hardware Agent Alarms

DRAFT

LSI Alarms

Alarm Automatically
Cleared

No

System Impact

No impact.

Recommended
Corrective Action

Check the rear panel for orange LEDs. Contact Comverse


customer support.

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

3.4.106

Alarm 3080438
Specific Problem

3080438

Managed Object

LSI

Description

Dual-active negotiation failed memory size.

Additional
Information

Controller: <$2>

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

Recommended
Corrective Action

Contact Comverse customer support.

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

3.4.107

Alarm 3080439
Specific Problem

3080439

Managed Object

LSI

Description

Dual-active negotiation failed cache memory size.

Additional
Information

Controller: <$2>

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

Recommended
Corrective Action

Contact Comverse customer support.

SMSC 4.2 Alarm Reference Manual


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

188 of 492

3: Hardware Agent Alarms

DRAFT

LSI Alarms

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

3.4.108

Alarm 3080440
Specific Problem

3080440

Managed Object

LSI

Description

Error in Mirror Race table.

Additional
Information

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

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

Recommended
Corrective Action

Contact Comverse customer support.

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

3.4.109

Alarm 3080441
Specific Problem

3080441

Managed Object

LSI

Description

A replacement controller attempted to stop the surviving


controller.

Additional
Information

Controller: <$2>

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

Recommended
Corrective Action

Contact Comverse customer support.

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

3.4.110

Alarm 3080519

SMSC 4.2 Alarm Reference Manual


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

189 of 492

3: Hardware Agent Alarms

DRAFT

Specific Problem

3080519

Managed Object

LSI

Description

Battery test has started.

Additional
Information

Controller: <$2>

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

LSI Alarms

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

3.4.111

Alarm 3080520
Specific Problem

3080520

Managed Object

LSI

Description

Battery test is complete.

Additional
Information

Controller: <$2>

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

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

3.4.112

Alarm 3080521
Specific Problem

3080521

Managed Object

LSI

Description

Battery test has been canceled.

Additional
Information

Controller: <$2>

Severity

Normal

Message Group
(Probable Cause)

Hardware

SMSC 4.2 Alarm Reference Manual


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

190 of 492

3: Hardware Agent Alarms

DRAFT

Alarm Automatically
Cleared

No

System Impact

No impact.

LSI Alarms

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

3.4.113

Alarm 3080522
Specific Problem

3080522

Managed Object

LSI

Description

Battery test has failed - battery bad.

Additional
Information

Controller: <$2>

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Causes system to work without cache, no impact on system


functionality.

Recommended
Corrective Action

Replace the battery.

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

3.4.114

Alarm 3080644
Specific Problem

3080644

Managed Object

LSI

Description

Back-end fiber dead.

Additional
Information

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

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 3080645

System Impact

No impact. Loss of FC loops redundancy.

Recommended
Corrective Action

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

For a detailed description of these rows, see Alarm Fields Description, Page 7.
SMSC 4.2 Alarm Reference Manual
P/N 10-000-1050 Issue 1 Rev. 0.1

191 of 492

3: Hardware Agent Alarms

3.4.115

DRAFT

LSI Alarms

Alarm 3080645
Specific Problem

3080645

Managed Object

LSI

Description

Back-end fiber alive.

Additional
Information

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

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

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

3.4.116

Alarm 3080700
Specific Problem

3080700

Managed Object

LSI

Description

Event log empty.

Additional
Information

Controller: <$2>

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

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

3.4.117

Alarm 3080701
Specific Problem

3080701

Managed Object

LSI

Description

Event log entries lost.

Additional
Information

Controller: <$2>

SMSC 4.2 Alarm Reference Manual


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

192 of 492

3: Hardware Agent Alarms

DRAFT

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

LSI Alarms

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

3.4.118

Alarm 3080702
Specific Problem

3080702

Managed Object

LSI

Description

Request sense.

Additional
Information

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

Severity

Minor

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

Recommended
Corrective Action

Contact Comverse customer support. This trap may be the


first sign of a failing disk.

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

3.4.119

Alarm 3080800
Specific Problem

3080800

Managed Object

LSI

Description

New configuration has been received.

Additional
Information

Controller: <$2>

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

SMSC 4.2 Alarm Reference Manual


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

193 of 492

3: Hardware Agent Alarms

DRAFT

LSI Alarms

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

3.4.120

Alarm 3080801
Specific Problem

3080801

Managed Object

LSI

Description

Configuration has been cleared.

Additional
Information

Controller: <$2>

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

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

3.4.121

Alarm 3080806
Specific Problem

3080806

Managed Object

LSI

Description

A debug dump exists on this system.

Additional
Information

Controller: <$2>

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

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

3.4.122

Alarm 3080807
Specific Problem

3080807

Managed Object

LSI

Description

A debug dump exists on this system.

SMSC 4.2 Alarm Reference Manual


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

194 of 492

3: Hardware Agent Alarms

DRAFT

Additional
Information

Controller: <$2>

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

LSI Alarms

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

3.4.123

Alarm 3080808
Specific Problem

3080808

Managed Object

LSI

Description

No valid Configuration On Disk (COD) found.

Additional
Information

Controller: <$2>

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

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

3.4.124

Alarm 3080809
Specific Problem

3080809

Managed Object

LSI

Description

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


found.

Additional
Information

Controller: <$2>

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

No impact.

SMSC 4.2 Alarm Reference Manual


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

195 of 492

3: Hardware Agent Alarms

DRAFT

LSI Alarms

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

SMSC 4.2 Alarm Reference Manual


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

196 of 492

3: Hardware Agent Alarms

3.5

DRAFT

Netra 240/440 Hardware Alarms (OnGuard Agent)

Netra 240/440 Hardware Alarms (OnGuard


Agent)
Search for the alarm you need by its Specific Problem (Alarm ID).

3.5.1

Alarm 2112042
Specific Problem

2112042

Managed Object

OnGuard

Description

CPU fan 2 has failed.

Additional
Information

CPU fan

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced system cooling.

Recommended
Corrective Action

Contact Comverse customer support.

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

3.5.2

Alarm 2112043
Specific Problem

2112043

Managed Object

OnGuard

Description

CPU fan 3 has failed.

Additional
Information

CPU fan

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced system cooling.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.
SMSC 4.2 Alarm Reference Manual
P/N 10-000-1050 Issue 1 Rev. 0.1

197 of 492

3: Hardware Agent Alarms

3.5.3

DRAFT

Netra 240/440 Hardware Alarms (OnGuard Agent)

Alarm 2112044
Specific Problem

2112044

Managed Object

OnGuard

Description

Fan 0 has failed.

Additional
Information

Fan

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced system cooling.

Recommended
Corrective Action

Contact Comverse customer support.

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

3.5.4

Alarm 2112045
Specific Problem

2112045

Managed Object

OnGuard

Description

Fan 1 has failed.

Additional
Information

Fan

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced system cooling.

Recommended
Corrective Action

Contact Comverse customer support.

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

3.5.5

Alarm 2112046
Specific Problem

2112046

Managed Object

OnGuard

SMSC 4.2 Alarm Reference Manual


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

198 of 492

3: Hardware Agent Alarms

DRAFT

Netra 240/440 Hardware Alarms (OnGuard Agent)

Description

DC power unavailable for power supply 0.

Additional
Information

DC power

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced power redundancy.

Recommended
Corrective Action

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

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

3.5.6

Alarm 2112047
Specific Problem

2112047

Managed Object

OnGuard

Description

DC power unavailable for power supply 1.

Additional
Information

DC power

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced power redundancy.

Recommended
Corrective Action

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

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

3.5.7

Alarm 2112048
Specific Problem

2112048

Managed Object

OnGuard

Description

Fan 0 has failed.

Additional
Information

Fan

Severity

Major

SMSC 4.2 Alarm Reference Manual


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

199 of 492

3: Hardware Agent Alarms

DRAFT

Netra 240/440 Hardware Alarms (OnGuard Agent)

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced system cooling.

Recommended
Corrective Action

Contact Comverse customer support.

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

3.5.8

Alarm 2112049
Specific Problem

2112049

Managed Object

OnGuard

Description

Fan 1 has failed.

Additional
Information

Fan

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced system cooling.

Recommended
Corrective Action

Contact Comverse customer support.

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

3.5.9

Alarm 2112050
Specific Problem

2112050

Managed Object

OnGuard

Description

Fan 2 has failed.

Additional
Information

Fan

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

SMSC 4.2 Alarm Reference Manual


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

200 of 492

3: Hardware Agent Alarms

DRAFT

Netra 240/440 Hardware Alarms (OnGuard Agent)

System Impact

Reduced system cooling.

Recommended
Corrective Action

Contact Comverse customer support.

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

3.5.10

Alarm 2112051
Specific Problem

2112051

Managed Object

OnGuard

Description

Fan 3 has failed.

Additional
Information

Fan

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced system cooling.

Recommended
Corrective Action

Contact Comverse customer support.

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

3.5.11

Alarm 2112052
Specific Problem

2112052

Managed Object

OnGuard

Description

Power supply 0 has been inserted.

Additional
Information

Power supply

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Recommended
Corrective Action

Check that this action was initiated and planned internally.

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

SMSC 4.2 Alarm Reference Manual


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

201 of 492

3: Hardware Agent Alarms

3.5.12

DRAFT

Netra 240/440 Hardware Alarms (OnGuard Agent)

Alarm 2112053
Specific Problem

2112053

Managed Object

OnGuard

Description

Power supply 0 has been removed.

Additional
Information

Power supply

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 2112052

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Check that this action was initiated and planned internally.


Contact Comverse customer support.

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

3.5.13

Alarm 2112054
Specific Problem

2112054

Managed Object

OnGuard

Description

Power supply 1 has been inserted.

Additional
Information

Power supply

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Recommended
Corrective Action

Check that this action was initiated and planned internally.

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

3.5.14

Alarm 2112055
Specific Problem

2112055

Managed Object

OnGuard

Description

Power supply 1 has been removed.

SMSC 4.2 Alarm Reference Manual


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

202 of 492

3: Hardware Agent Alarms

DRAFT

Netra 240/440 Hardware Alarms (OnGuard Agent)

Additional
Information

Power supply

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 2112054

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Check that this action was initiated and planned internally.


Contact Comverse customer support.

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

3.5.15

Alarm 2112056
Specific Problem

2112056

Managed Object

OnGuard

Description

CPU 0 high temperature exceeded hard shutdown threshold.

Additional
Information

CPU temperature

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Threshold

118 C

System Impact

Server down due to high temperature. Downtime in case of


no server redundancy.

Recommended
Corrective Action

Contact Comverse customer support.

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

3.5.16

Alarm 2112057
Specific Problem

2112057

Managed Object

OnGuard

Description

CPU 0 high temperature exceeded soft shutdown threshold.

Additional
Information

CPU temperature

SMSC 4.2 Alarm Reference Manual


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

Soft shutdown performs self shutdown through command.

203 of 492

3: Hardware Agent Alarms

DRAFT

Netra 240/440 Hardware Alarms (OnGuard Agent)

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Threshold

115 C

System Impact

Server down due to high temperature. Downtime in case of


no server redundancy.

Recommended
Corrective Action

Contact Comverse customer support.

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

3.5.17

Alarm 2112058
Specific Problem

2112058

Managed Object

OnGuard

Description

CPU 0 high temperature warning.

Additional
Information

CPU temperature

Severity

Minor

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Threshold

110 C

Recommended
Corrective Action

Contact Comverse customer support.

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

3.5.18

Alarm 2112059
Specific Problem

2112059

Managed Object

OnGuard

Description

CPU 1 high temperature exceeded hard shutdown threshold.

Additional
Information

CPU temperature

Severity

Major

SMSC 4.2 Alarm Reference Manual


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

Hard Shutdown performs immediate shutdown.

204 of 492

3: Hardware Agent Alarms

DRAFT

Netra 240/440 Hardware Alarms (OnGuard Agent)

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Threshold

118 C

System Impact

Server down due to high temperature. Downtime in case of


no server redundancy.

Recommended
Corrective Action

Contact Comverse customer support.

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

3.5.19

Alarm 2112060
Specific Problem

2112060

Managed Object

OnGuard

Description

CPU 1 high temperature exceeded soft shutdown threshold.

Additional
Information

CPU temperature

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Threshold

115 C

System Impact

Server down due to high temperature. Downtime in case of


no server redundancy.

Recommended
Corrective Action

Contact Comverse customer support.

Soft shutdown performs self shutdown through command.

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

3.5.20

Alarm 2112061
Specific Problem

2112061

Managed Object

OnGuard

Description

CPU 1 high temperature warning.

Additional
Information

CPU temperature

Severity

Minor

SMSC 4.2 Alarm Reference Manual


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

205 of 492

3: Hardware Agent Alarms

DRAFT

Netra 240/440 Hardware Alarms (OnGuard Agent)

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Threshold

110 C

Recommended
Corrective Action

Contact Comverse customer support.

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

3.5.21

Alarm 2112062
Specific Problem

2112062

Managed Object

OnGuard

Description

Power Supply 0 internal connection failure.

Additional
Information

Power supply

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Check the power supply LED. If the problem persists, contact


Comverse customer support.

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

3.5.22

Alarm 2112063
Specific Problem

2112063

Managed Object

OnGuard

Description

Power Supply 1 internal connection failure.

Additional
Information

Power supply

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

SMSC 4.2 Alarm Reference Manual


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

206 of 492

3: Hardware Agent Alarms

DRAFT

Netra 240/440 Hardware Alarms (OnGuard Agent)

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Check the power supply LED. If the problem persists, contact


Comverse customer support.

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

3.5.23

Alarm 2112064
Specific Problem

2112064

Managed Object

OnGuard

Description

Power Supply 2 internal connection failure.

Additional
Information

Power supply

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Check the power supply LED. If the problem persists, contact


Comverse customer support.

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

3.5.24

Alarm 2112065
Specific Problem

2112065

Managed Object

OnGuard

Description

Power Supply 3 internal connection failure.

Additional
Information

Power supply

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Check the power supply LED. If the problem persists, contact


Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.
SMSC 4.2 Alarm Reference Manual
P/N 10-000-1050 Issue 1 Rev. 0.1

207 of 492

3: Hardware Agent Alarms

3.5.25

DRAFT

Netra 240/440 Hardware Alarms (OnGuard Agent)

Alarm 2112066
Specific Problem

2112066

Managed Object

OnGuard

Description

CPU fan tray 0 has been inserted.

Additional
Information

CPU fan tray

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Recommended
Corrective Action

Verify that this action was planned and initiated by a


technician.

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

3.5.26

Alarm 2112067
Specific Problem

2112067

Managed Object

OnGuard

Description

CPU fan tray 0 has been removed.

Additional
Information

CPU fan tray

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 2112066

System Impact

Reduced system cooling.

Recommended
Corrective Action

Verify that this action was planned and initiated by a


technician.

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

3.5.27

Alarm 2112068
Specific Problem

2112068

Managed Object

OnGuard

Description

CPU fan tray 0 has failed.

SMSC 4.2 Alarm Reference Manual


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

208 of 492

3: Hardware Agent Alarms

DRAFT

Netra 240/440 Hardware Alarms (OnGuard Agent)

Additional
Information

CPU fan tray

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced system cooling.

Recommended
Corrective Action

Check the fan LED status.

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

3.5.28

Alarm 2112069
Specific Problem

2112069

Managed Object

OnGuard

Description

CPU fan tray 1 has been inserted.

Additional
Information

CPU fan tray

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Recommended
Corrective Action

Verify that this action was planned and initiated by a


technician.

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

3.5.29

Alarm 2112070
Specific Problem

2112070

Managed Object

OnGuard

Description

CPU fan tray 1 has been removed.

Additional
Information

CPU fan tray

Severity

Major

Message Group
(Probable Cause)

Hardware

SMSC 4.2 Alarm Reference Manual


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

209 of 492

3: Hardware Agent Alarms

DRAFT

Netra 240/440 Hardware Alarms (OnGuard Agent)

Alarm Automatically
Cleared

No

System Impact

Reduced system cooling.

Recommended
Corrective Action

Verify that this action was planned and initiated by a


technician.

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

3.5.30

Alarm 2112071
Specific Problem

2112071

Managed Object

OnGuard

Description

CPU fan tray 1 has failed.

Additional
Information

CPU fan tray

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 2112069

System Impact

Reduced system cooling.

Recommended
Corrective Action

Check the fan LED status.

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

3.5.31

Alarm 2112072
Specific Problem

2112072

Managed Object

OnGuard

Description

CPU fan tray 2 has been inserted.

Additional
Information

CPU fan tray

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Recommended
Corrective Action

Verify that this action was planned and initiated by a


technician.

For a detailed description of these rows, see Alarm Fields Description, Page 7.
SMSC 4.2 Alarm Reference Manual
P/N 10-000-1050 Issue 1 Rev. 0.1

210 of 492

3: Hardware Agent Alarms

3.5.32

DRAFT

Netra 240/440 Hardware Alarms (OnGuard Agent)

Alarm 2112073
Specific Problem

2112073

Managed Object

OnGuard

Description

CPU fan tray 2 has been removed.

Additional
Information

CPU fan tray

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 2112069

System Impact

Reduced system cooling.

Recommended
Corrective Action

Verify that this action was planned and initiated by a


technician.

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

3.5.33

Alarm 2112074
Specific Problem

2112074

Managed Object

OnGuard

Description

CPU fan tray 2 has failed.

Additional
Information

CPU fan tray

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced system cooling.

Recommended
Corrective Action

Check the fan LED status.

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

3.5.34

Alarm 2112075
Specific Problem

2112075

Managed Object

OnGuard

SMSC 4.2 Alarm Reference Manual


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

211 of 492

3: Hardware Agent Alarms

DRAFT

Netra 240/440 Hardware Alarms (OnGuard Agent)

Description

CPU fan tray 3 has failed.

Additional
Information

CPU fan tray

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced system cooling.

Recommended
Corrective Action

Check the fan LED status.

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

3.5.35

Alarm 2112076
Specific Problem

2112076

Managed Object

OnGuard

Description

Input power unavailable for power supply 0.

Additional
Information

Input power

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced power redundancy.

Recommended
Corrective Action

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

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

3.5.36

Alarm 2112077
Specific Problem

2112077

Managed Object

OnGuard

Description

Input power unavailable for power supply 1.

Additional
Information

Input power

Severity

Major

SMSC 4.2 Alarm Reference Manual


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

212 of 492

3: Hardware Agent Alarms

DRAFT

Netra 240/440 Hardware Alarms (OnGuard Agent)

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced power redundancy.

Recommended
Corrective Action

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

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

3.5.37

Alarm 2112078
Specific Problem

2112078

Managed Object

OnGuard

Description

Input power unavailable for power supply 2.

Additional
Information

Input power

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced power redundancy.

Recommended
Corrective Action

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

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

3.5.38

Alarm 2112079
Specific Problem

2112079

Managed Object

OnGuard

Description

Input power unavailable for power supply 3.

Additional
Information

Input power

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

SMSC 4.2 Alarm Reference Manual


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

213 of 492

3: Hardware Agent Alarms

DRAFT

Netra 240/440 Hardware Alarms (OnGuard Agent)

System Impact

Reduced power redundancy.

Recommended
Corrective Action

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

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

3.5.39

Alarm 2112080
Specific Problem

2112080

Managed Object

OnGuard

Description

Power supply 0 has been inserted.

Additional
Information

Power supply

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Recommended
Corrective Action

Verify that this action was planned and initiated by a


technician.

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

3.5.40

Alarm 2112081
Specific Problem

2112081

Managed Object

OnGuard

Description

Power supply 0 has been removed.

Additional
Information

Power supply

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Verify that this action was planned and initiated by a


technician.

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

SMSC 4.2 Alarm Reference Manual


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

214 of 492

3: Hardware Agent Alarms

3.5.41

DRAFT

Netra 240/440 Hardware Alarms (OnGuard Agent)

Alarm 2112082
Specific Problem

2112082

Managed Object

OnGuard

Description

Power supply 0 has failed.

Additional
Information

Power supply

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Check the power supply LEDs status. If the problem persists,


contact Comverse customer support.

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

3.5.42

Alarm 2112083
Specific Problem

2112083

Managed Object

OnGuard

Description

Power supply 0 is not properly in place.

Additional
Information

Power supply

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Check that power supply 0 is properly inserted.

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

3.5.43

Alarm 2112084
Specific Problem

2112084

Managed Object

OnGuard

SMSC 4.2 Alarm Reference Manual


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

215 of 492

3: Hardware Agent Alarms

DRAFT

Netra 240/440 Hardware Alarms (OnGuard Agent)

Description

Power supply 1 has been inserted.

Additional
Information

Power supply

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Recommended
Corrective Action

Verify that this action was planned and initiated by a


technician.

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

3.5.44

Alarm 2112085
Specific Problem

2112085

Managed Object

OnGuard

Description

Power supply 1 has been removed.

Additional
Information

Power supply

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Verify that this action was planned and initiated by a


technician.

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

3.5.45

Alarm 2112086
Specific Problem

2112086

Managed Object

OnGuard

Description

Power supply 1 has failed.

Additional
Information

Power supply

Severity

Major

Message Group
(Probable Cause)

Hardware

SMSC 4.2 Alarm Reference Manual


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

216 of 492

3: Hardware Agent Alarms

DRAFT

Netra 240/440 Hardware Alarms (OnGuard Agent)

Alarm Automatically
Cleared

No

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Check the power supply LED.

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

3.5.46

Alarm 2112087
Specific Problem

2112087

Managed Object

OnGuard

Description

Power supply 1 is not properly in place.

Additional
Information

Power supply

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Check that power supply 1 is properly inserted.

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

3.5.47

Alarm 2112088
Specific Problem

2112088

Managed Object

OnGuard

Description

Power supply 2 has been inserted.

Additional
Information

Power supply

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Recommended
Corrective Action

Verify that this action was planned and initiated by a


technician.

For a detailed description of these rows, see Alarm Fields Description, Page 7.
SMSC 4.2 Alarm Reference Manual
P/N 10-000-1050 Issue 1 Rev. 0.1

217 of 492

3: Hardware Agent Alarms

3.5.48

DRAFT

Netra 240/440 Hardware Alarms (OnGuard Agent)

Alarm 2112089
Specific Problem

2112089

Managed Object

OnGuard

Description

Power supply 2 has been removed.

Additional
Information

Power supply

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Verify that this action was planned and initiated by a


technician.

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

3.5.49

Alarm 2112090
Specific Problem

2112090

Managed Object

OnGuard

Description

Power supply 2 has failed.

Additional
Information

Power supply

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Check the power supply LED.

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

3.5.50

Alarm 2112091
Specific Problem

2112091

Managed Object

OnGuard

SMSC 4.2 Alarm Reference Manual


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

218 of 492

3: Hardware Agent Alarms

DRAFT

Netra 240/440 Hardware Alarms (OnGuard Agent)

Description

Power supply 2 is not properly in place.

Additional
Information

Power supply

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Check that power supply 2 is properly inserted.

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

3.5.51

Alarm 2112092
Specific Problem

2112092

Managed Object

OnGuard

Description

Power supply 3 has been inserted.

Additional
Information

Power supply

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Recommended
Corrective Action

Verify that this action was planned and initiated by a


technician.

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

3.5.52

Alarm 2112093
Specific Problem

2112093

Managed Object

OnGuard

Description

Power supply 3 has been removed.

Additional
Information

Power supply

Severity

Major

Message Group
(Probable Cause)

Hardware

SMSC 4.2 Alarm Reference Manual


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

219 of 492

3: Hardware Agent Alarms

DRAFT

Netra 240/440 Hardware Alarms (OnGuard Agent)

Alarm Automatically
Cleared

No

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Verify that this action was planned and initiated by a


technician.

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

3.5.53

Alarm 2112094
Specific Problem

2112094

Managed Object

OnGuard

Description

Power supply 3 has failed.

Additional
Information

Power supply

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Check the power supply LED.

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

3.5.54

Alarm 2112095
Specific Problem

2112095

Managed Object

OnGuard

Description

Power supply 3 is not properly in place.

Additional
Information

Power supply

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Check that power supply 3 is properly inserted.

SMSC 4.2 Alarm Reference Manual


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

220 of 492

3: Hardware Agent Alarms

DRAFT

Netra 240/440 Hardware Alarms (OnGuard Agent)

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

3.5.55

Alarm 2112096
Specific Problem

2112096

Managed Object

OnGuard

Description

CPU 0 high temperature exceeded hard shutdown threshold.

Additional
Information

CPU temperature

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Threshold

118 C

System Impact

Server down due to high temperature. Downtime in case of


no server redundancy.

Recommended
Corrective Action

Contact Comverse customer support.

Hard Shutdown performs immediate shutdown.

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

3.5.56

Alarm 2112097
Specific Problem

2112097

Managed Object

OnGuard

Description

CPU 0 high temperature exceeded soft shutdown threshold.

Additional
Information

CPU temperature

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Threshold

110 C

System Impact

Server down due to high temperature. Downtime in case of


no server redundancy.

Recommended
Corrective Action

Contact Comverse customer support.

SMSC 4.2 Alarm Reference Manual


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

Soft shutdown performs self shutdown through command.

221 of 492

3: Hardware Agent Alarms

DRAFT

Netra 240/440 Hardware Alarms (OnGuard Agent)

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

3.5.57

Alarm 2112098
Specific Problem

2112098

Managed Object

OnGuard

Description

CPU 0 high temperature warning.

Additional
Information

CPU temperature

Severity

Minor

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Threshold

102 C

Recommended
Corrective Action

Contact Comverse customer support.

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

3.5.58

Alarm 2112099
Specific Problem

2112099

Managed Object

OnGuard

Description

CPU 1 high temperature exceeded hard shutdown threshold.

Additional
Information

CPU temperature

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Threshold

118 C

System Impact

Server down due to high temperature. Downtime in case of


no server redundancy.

Recommended
Corrective Action

Contact Comverse customer support.

Hard Shutdown performs immediate shutdown.

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

SMSC 4.2 Alarm Reference Manual


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

222 of 492

3: Hardware Agent Alarms

3.5.59

DRAFT

Netra 240/440 Hardware Alarms (OnGuard Agent)

Alarm 2112100
Specific Problem

2112100

Managed Object

OnGuard

Description

CPU 1 high temperature exceeded soft shutdown threshold.

Additional
Information

CPU temperature

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Threshold

110 C

System Impact

Server down due to high temperature. Downtime in case of


no server redundancy.

Recommended
Corrective Action

Contact Comverse customer support.

Soft shutdown performs self shutdown through command.

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

3.5.60

Alarm 2112101
Specific Problem

2112101

Managed Object

OnGuard

Description

CPU 1 high temperature warning.

Additional
Information

CPU temperature

Severity

Minor

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Threshold

102 C

Recommended
Corrective Action

Contact Comverse customer support.

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

3.5.61

Alarm 2112102

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

223 of 492

3: Hardware Agent Alarms

DRAFT

Netra 240/440 Hardware Alarms (OnGuard Agent)

Specific Problem

2112102

Managed Object

OnGuard

Description

CPU 2 high temperature exceeded hard shutdown threshold.

Additional
Information

CPU temperature

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Server down due to high temperature. Downtime in case of


no server redundancy.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.5.62

Alarm 2112103
Specific Problem

2112103

Managed Object

OnGuard

Description

CPU 2 high temperature exceeded soft shutdown threshold.

Additional
Information

CPU temperature

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Server down due to high temperature. Downtime in case of


no server redundancy.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.5.63

Alarm 2112104
Specific Problem

2112104

Managed Object

OnGuard

Description

CPU 2 high temperature warning.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

224 of 492

3: Hardware Agent Alarms

DRAFT

Netra 240/440 Hardware Alarms (OnGuard Agent)

Additional
Information

CPU temperature

Severity

Minor

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.5.64

Alarm 2112105
Specific Problem

2112105

Managed Object

OnGuard

Description

CPU 3 high temperature exceeded hard shutdown threshold.

Additional
Information

CPU temperature

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Server down due to high temperature. Down time in case of


no server redundancy.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.5.65

Alarm 2112106
Specific Problem

2112106

Managed Object

OnGuard

Description

CPU 3 high temperature exceeded soft shutdown threshold.

Additional
Information

CPU temperature

Severity

Major

Message Group
(Probable Cause)

Hardware

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

225 of 492

3: Hardware Agent Alarms

DRAFT

Netra 240/440 Hardware Alarms (OnGuard Agent)

Alarm Automatically
Cleared

No

System Impact

Server down due to high temperature. Downtime in case of


no server redundancy.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.5.66

Alarm 2112107
Specific Problem

2112107

Managed Object

OnGuard

Description

CPU 3 high temperature warning.

Additional
Information

CPU temperature

Severity

Minor

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

226 of 492

3: Hardware Agent Alarms

3.6

DRAFT

Q-Logic Alarms

Q-Logic Alarms
Search for the alarm you need by its Specific Problem (Alarm ID).

3.6.1

Alarm 2990000
Specific Problem

2990000

Managed Object

Q-Logic

Description

An unknown trap <$o> arrived from the Q-Logic system.

Severity

Unknown

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.2

Alarm 2990101
Specific Problem

2990101

Managed Object

Q-Logic

Description

Q-Logic - Switch status has changed to unknown with


unknown state.

Severity

Major

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.3

Alarm 2990102
Specific Problem

2990102

Managed Object

Q-Logic

Description

Q-Logic - Switch status has changed to unknown with online


state.

Severity

Major

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.4

Alarm 2990103

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

227 of 492

3: Hardware Agent Alarms

DRAFT

Q-Logic Alarms

Specific Problem

2990103

Managed Object

Q-Logic

Description

Q-Logic - Switch status has changed to unknown with offline


state.

Severity

Major

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.5

Alarm 2990104
Specific Problem

2990104

Managed Object

Q-Logic

Description

Q-Logic - Switch status has changed to unused with unknown


state.

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.6

Alarm 2990105
Specific Problem

2990105

Managed Object

Q-Logic

Description

Q-Logic - Switch status has changed to unused with online


state.

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.7

Alarm 2990106
Specific Problem

2990106

Managed Object

Q-Logic

Description

Q-Logic - Switch status has changed to unused with offline


state.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

228 of 492

3: Hardware Agent Alarms

DRAFT

Severity

Normal

Alarm Automatically
Cleared

No

Q-Logic Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.8

Alarm 2990107
Specific Problem

2990107

Managed Object

Q-Logic

Description

Q-Logic - Switch status has changed to ok with unknown state.

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.9

Alarm 2990108
Specific Problem

2990108

Managed Object

Q-Logic

Description

Q-Logic - Switch status has changed to ok with online state.

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.10

Alarm 2990109
Specific Problem

2990109

Managed Object

Q-Logic

Description

Q-Logic - Switch status has changed to ok with offline state.

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

229 of 492

3: Hardware Agent Alarms

3.6.11

DRAFT

Q-Logic Alarms

Alarm 2990110
Specific Problem

2990110

Managed Object

Q-Logic

Description

Q-Logic - Switch status has changed to warning with unknown


state.

Severity

Warning

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.12

Alarm 2990111
Specific Problem

2990111

Managed Object

Q-Logic

Description

Q-Logic - Switch status has changed to warning with online


state.

Severity

Warning

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.13

Alarm 2990112
Specific Problem

2990112

Managed Object

Q-Logic

Description

Q-Logic - Switch status has changed to warning with offline


state.

Severity

Warning

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.14

Alarm 2990113

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

230 of 492

3: Hardware Agent Alarms

DRAFT

Q-Logic Alarms

Specific Problem

2990113

Managed Object

Q-Logic

Description

Q-Logic - Switch status has changed to failure with unknown


state.

Severity

Major

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.15

Alarm 2990114
Specific Problem

2990114

Managed Object

Q-Logic

Description

Q-Logic - Switch status has changed to failure with online


state.

Severity

Major

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.16

Alarm 2990115
Specific Problem

2990115

Managed Object

Q-Logic

Description

Q-Logic - Switch status has changed to failure with offline


state.

Severity

Major

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.17

Alarm 2990301
Specific Problem

2990301

Managed Object

Q-Logic

Description

Q-Logic - Connectivity unit <connUnitId> has been deleted


from this agent.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

231 of 492

3: Hardware Agent Alarms

DRAFT

Severity

Warning

Alarm Automatically
Cleared

No

Q-Logic Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.18

Alarm 2990401
Specific Problem

2990401

Managed Object

Q-Logic

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

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.19

Alarm 2990402
Specific Problem

2990402

Managed Object

Q-Logic

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

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.20

Alarm 2990403
Specific Problem

2990403

Managed Object

Q-Logic

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>.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

232 of 492

3: Hardware Agent Alarms

DRAFT

Severity

Normal

Alarm Automatically
Cleared

No

Q-Logic Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.21

Alarm 2990404
Specific Problem

2990404

Managed Object

Q-Logic

Description

Q-Logic - An event of type configuration occurred on


switch <Chassis>, I/O blade <Blade>, port <Port>, module
<Module>, address <Addr>. Event description: <Descr>.

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.22

Alarm 2990405
Specific Problem

2990405

Managed Object

Q-Logic

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

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.23

Alarm 2990501
Specific Problem

2990501

Managed Object

Q-Logic

Description

Q-Logic - Sensor status has changed to unknown.

Severity

Major

Alarm Automatically
Cleared

No

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

233 of 492

3: Hardware Agent Alarms

DRAFT

Q-Logic Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.24

Alarm 2990502
Specific Problem

2990502

Managed Object

Q-Logic

Description

Q-Logic - Sensor status has changed to other.

Severity

Major

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.25

Alarm 2990503
Specific Problem

2990503

Managed Object

Q-Logic

Description

Q-Logic - Sensor status has changed to ok.

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.26

Alarm 2990504
Specific Problem

2990504

Managed Object

Q-Logic

Description

Q-Logic - Sensor status has changed to warning.

Severity

Warning

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.27

Alarm 2990505
Specific Problem

2990505

Managed Object

Q-Logic

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

234 of 492

3: Hardware Agent Alarms

DRAFT

Description

Q-Logic - Sensor status has changed to failed.

Severity

Major

Alarm Automatically
Cleared

No

Q-Logic Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.28

Alarm 2990601 (Q-Logic - Port status has changes


to unknown with bypassed state.)
Specific Problem

2990601

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to unknown with bypassed


state.

Severity

Major

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.29

Alarm 2990601 (Q-Logic - Port status has changes


to unknown with diagnostics state.)
Specific Problem

2990601

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to unknown with diagnostics


state.

Severity

Major

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.30

Alarm 2990601 (Q-Logic - Port status has changes


to unknown with offline state.)
Specific Problem

2990601

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to unknown with offline


state.

Severity

Major

Alarm Automatically
Cleared

No

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

235 of 492

3: Hardware Agent Alarms

DRAFT

Q-Logic Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.31

Alarm 2990601 (Q-Logic - Port status has changes


to unknown with online state.)
Specific Problem

2990601

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to unknown with online


state.

Severity

Major

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.32

Alarm 2990601 (Q-Logic - Port status has changes


to unknown with unknown state.)
Specific Problem

2990601

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to unknown with unknown


state.

Severity

Major

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.33

Alarm 2990602 (Q-Logic - Port status has changes


to unused with bypassed state.)
Specific Problem

2990602

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to unused with bypassed


state.

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

236 of 492

3: Hardware Agent Alarms

3.6.34

DRAFT

Q-Logic Alarms

Alarm 2990602 (Q-Logic - Port status has changes


to unused with diagnostics state.)
Specific Problem

2990602

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to unused with diagnostics


state.

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.35

Alarm 2990602 (Q-Logic - Port status has changes


to unused with offline state.)
Specific Problem

2990602

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to unused with offline state.

Severity

Major

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.36

Alarm 2990602 (Q-Logic - Port status has changes


to unused with online state.)
Specific Problem

2990602

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to unused with online state.

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.37

Alarm 2990602 (Q-Logic - Port status has changes


to unused with unknown state.)
Specific Problem

2990602

Managed Object

Q-Logic

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

237 of 492

3: Hardware Agent Alarms

DRAFT

Q-Logic Alarms

Description

Q-Logic - Port status has changes to unused with unknown


state.

Severity

Major

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.38

Alarm 2990603 (Q-Logic - Port status has changes


to ready with bypassed state.)
Specific Problem

2990603

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to ready with bypassed


state.

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.39

Alarm 2990603 (Q-Logic - Port status has changes


to ready with diagnostics state.)
Specific Problem

2990603

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to ready with diagnostics


state.

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.40

Alarm 2990603 (Q-Logic - Port status has changes


to ready with offline state.)
Specific Problem

2990603

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to ready with offline state.

Severity

Major

Alarm Automatically
Cleared

No

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

238 of 492

3: Hardware Agent Alarms

DRAFT

Q-Logic Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.41

Alarm 2990603 (Q-Logic - Port status has changes


to ready with online state.)
Specific Problem

2990603

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to ready with online state.

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.42

Alarm 2990603 (Q-Logic - Port status has changes


to ready with unknown state.)
Specific Problem

2990603

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to ready with unknown


state.

Severity

Major

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.43

Alarm 2990604 (Q-Logic - Port status has changes


to warning with bypassed state.)
Specific Problem

2990604

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to warning with bypassed


state.

Severity

Warning

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

239 of 492

3: Hardware Agent Alarms

3.6.44

DRAFT

Q-Logic Alarms

Alarm 2990604 (Q-Logic - Port status has changes


to warning with diagnostics state.)
Specific Problem

2990604

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to warning with diagnostics


state.

Severity

Warning

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.45

Alarm 2990604 (Q-Logic - Port status has changes


to warning with offline state.)
Specific Problem

2990604

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to warning with offline state.

Severity

Major

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.46

Alarm 2990604 (Q-Logic - Port status has changes


to warning with online state.)
Specific Problem

2990604

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to warning with online state.

Severity

Warning

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.47

Alarm 2990604 (Q-Logic - Port status has changes


to warning with unknown state.)
Specific Problem

2990604

Managed Object

Q-Logic

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

240 of 492

3: Hardware Agent Alarms

DRAFT

Q-Logic Alarms

Description

Q-Logic - Port status has changes to warning with unknown


state.

Severity

Major

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.48

Alarm 2990605 (Q-Logic - Port status has changes


to failure with bypassed state.)
Specific Problem

2990605

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to failure with bypassed


state.

Severity

Major

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.49

Alarm 2990605 (Q-Logic - Port status has changes


to failure with diagnostics state.)
Specific Problem

2990605

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to failure with diagnostics


state.

Severity

Major

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.50

Alarm 2990605 (Q-Logic - Port status has changes


to failure with offline state.)
Specific Problem

2990605

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to failure with offline state.

Severity

Major

Alarm Automatically
Cleared

No

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

241 of 492

3: Hardware Agent Alarms

DRAFT

Q-Logic Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.51

Alarm 2990605 (Q-Logic - Port status has changes


to failure with online state.)
Specific Problem

2990605

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to failure with online state.

Severity

Major

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.52

Alarm 2990605 (Q-Logic - Port status has changes


to failure with unknown state.)
Specific Problem

2990605

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to failure with unknown


state.

Severity

Major

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.53

Alarm 2990606 (Q-Logic - Port status has changes


to not participating with bypassed state.)
Specific Problem

2990606

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to not participating with


bypassed state.

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

242 of 492

3: Hardware Agent Alarms

3.6.54

DRAFT

Q-Logic Alarms

Alarm 2990606 (Q-Logic - Port status has changes


to not participating with diagnostics state.)
Specific Problem

2990606

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to not participating with


diagnostics state.

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.55

Alarm 2990606 (Q-Logic - Port status has changes


to not participating with offline state.)
Specific Problem

2990606

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to not participating with


offline state.

Severity

Major

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.56

Alarm 2990606 (Q-Logic - Port status has changes


to not participating with online state.)
Specific Problem

2990606

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to not participating with


online state.

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.57

Alarm 2990606 (Q-Logic - Port status has changes


to not participating with unknown state.)
Specific Problem

2990606

Managed Object

Q-Logic

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

243 of 492

3: Hardware Agent Alarms

DRAFT

Q-Logic Alarms

Description

Q-Logic - Port status has changes to not participating with


unknown state.

Severity

Major

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.58

Alarm 2990607 (Q-Logic - Port status has changes


to initializing with bypassed state.)
Specific Problem

2990607

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to initializing with bypassed


state.

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.59

Alarm 2990607 (Q-Logic - Port status has changes


to initializing with diagnostics state.)
Specific Problem

2990607

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to initializing with


diagnostics state.

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.60

Alarm 2990607 (Q-Logic - Port status has changes


to initializing with offline state.)
Specific Problem

2990607

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to initializing with offline


state.

Severity

Major

Alarm Automatically
Cleared

No

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

244 of 492

3: Hardware Agent Alarms

DRAFT

Q-Logic Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.61

Alarm 2990607 (Q-Logic - Port status has changes


to initializing with online state.)
Specific Problem

2990607

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to initializing with online


state.

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.62

Alarm 2990607 (Q-Logic - Port status has changes


to initializing with unknown state.)
Specific Problem

2990607

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to initializing with unknown


state.

Severity

Major

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.63

Alarm 2990608 (Q-Logic - Port status has changes


to bypass with bypassed state.)
Specific Problem

2990608

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to bypass with bypassed


state.

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

245 of 492

3: Hardware Agent Alarms

3.6.64

DRAFT

Q-Logic Alarms

Alarm 2990608 (Q-Logic - Port status has changes


to bypass with diagnostics state.)
Specific Problem

2990608

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to bypass with diagnostics


state.

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.65

Alarm 2990608 (Q-Logic - Port status has changes


to bypass with offline state.)
Specific Problem

2990608

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to bypass with offline state.

Severity

Major

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.66

Alarm 2990608 (Q-Logic - Port status has changes


to bypass with online state.)
Specific Problem

2990608

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to bypass with online state.

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.67

Alarm 2990608 (Q-Logic - Port status has changes


to bypass with unknown state.)
Specific Problem

2990608

Managed Object

Q-Logic

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

246 of 492

3: Hardware Agent Alarms

DRAFT

Q-Logic Alarms

Description

Q-Logic - Port status has changes to bypass with unknown


state.

Severity

Major

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.68

Alarm 2990609 (Q-Logic - Port status has changes


tools with bypassed state.)
Specific Problem

2990609

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes tools with bypassed state.

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.69

Alarm 2990609 (Q-Logic - Port status has changes


tools with diagnostics state.)
Specific Problem

2990609

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes tools with diagnostics state.

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.70

Alarm 2990609 (Q-Logic - Port status has changes


tools with offline state.)
Specific Problem

2990609

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes tools with offline state.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

247 of 492

3: Hardware Agent Alarms

DRAFT

Severity

Major

Alarm Automatically
Cleared

No

Q-Logic Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.71

Alarm 2990609 (Q-Logic - Port status has changes


tools with online state.)
Specific Problem

2990609

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes tools with online state.

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.72

Alarm 2990609 (Q-Logic - Port status has changes


tools with unknown state.)
Specific Problem

2990609

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes tools with unknown state.

Severity

Major

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.73

Alarm 2990610 (Q-Logic - Port status has changes


to other with bypassed state.)
Specific Problem

2990610

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to other with bypassed


state.

Severity

Normal

Alarm Automatically
Cleared

No

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

248 of 492

3: Hardware Agent Alarms

DRAFT

Q-Logic Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.74

Alarm 2990610 (Q-Logic - Port status has changes


to other with diagnostics state.)
Specific Problem

2990610

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to other with diagnostics


state.

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.75

Alarm 2990610 (Q-Logic - Port status has changes


to other with offline state.)
Specific Problem

2990610

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to other with offline state.

Severity

Major

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.76

Alarm 2990610 (Q-Logic - Port status has changes


to other with online state.)
Specific Problem

2990610

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to other with online state.

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

249 of 492

3: Hardware Agent Alarms

3.6.77

DRAFT

Q-Logic Alarms

Alarm 2990610 (Q-Logic - Port status has changes


to other with unknown state.)
Specific Problem

2990610

Managed Object

Q-Logic

Description

Q-Logic - Port status has changes to other with unknown state.

Severity

Major

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.78

Alarm 2990701
Specific Problem

2990701

Managed Object

Q-Logic

Description

Q-Logic - Cold start.

Severity

Warning

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.79

Alarm 2990801
Specific Problem

2990801

Managed Object

Q-Logic

Description

Q-Logic - authentication failure.

Severity

Warning

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.80

Alarm 2991001
Specific Problem

2991001

Managed Object

Q-Logic

Description

Q-Logic - QxPort link down. Current QxPort operational status


is offline. Desired status of the QxPort is online.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

250 of 492

3: Hardware Agent Alarms

DRAFT

Severity

Major

Alarm Automatically
Cleared

No

Q-Logic Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.81

Alarm 2991002
Specific Problem

2991002

Managed Object

Q-Logic

Description

Q-Logic - QxPort link down. Current QxPort operational status


is offline. Desired status of the QxPort is offline.

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.82

Alarm 2991003
Specific Problem

2991003

Managed Object

Q-Logic

Description

Q-Logic - QxPort link down. Current QxPort operational status


is offline. Desired status of the QxPort is testing.

Severity

Major

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.83

Alarm 2991004
Specific Problem

2991004

Managed Object

Q-Logic

Description

Q-Logic - QxPort link down. Current QxPort operational status


is testing. Desired status of the QxPort is online.

Severity

Warning

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.
SMSC 4.2 Alarm Reference Manual
P/N 10-000-1050 Issue 1 Rev. 0.1

251 of 492

3: Hardware Agent Alarms

3.6.84

DRAFT

Q-Logic Alarms

Alarm 2991005
Specific Problem

2991005

Managed Object

Q-Logic

Description

Q-Logic - QxPort link down. Current QxPort operational status


is testing. Desired status of the QxPort is offline.

Severity

Warning

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.85

Alarm 2991006
Specific Problem

2991006

Managed Object

Q-Logic

Description

Q-Logic - QxPort link down. Current QxPort operational status


is testing. Desired status of the QxPort is testing.

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.86

Alarm 2991007
Specific Problem

2991007

Managed Object

Q-Logic

Description

Q-Logic - QxPort link down. Current QxPort operational status


is link failure. Desired status of the QxPort is online.

Severity

Major

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.87

Alarm 2991008

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

252 of 492

3: Hardware Agent Alarms

DRAFT

Q-Logic Alarms

Specific Problem

2991008

Managed Object

Q-Logic

Description

Q-Logic - QxPort link down. Current QxPort operational status


is link failure. Desired status of the QxPort is offline.

Severity

Major

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.88

Alarm 2991009
Specific Problem

2991009

Managed Object

Q-Logic

Description

Q-Logic - QxPort link down. Current QxPort operational status


is link failure. Desired status of the QxPort is testing.

Severity

Major

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.89

Alarm 2991101
Specific Problem

2991101

Managed Object

Q-Logic

Description

Q-Logic - QxPort link up. Current QxPort operational status is


online. Desired status of the QxPort is online.

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.90

Alarm 2991102
Specific Problem

2991102

Managed Object

Q-Logic

Description

Q-Logic - QxPort link up. Current QxPort operational status is


online. Desired status of the QxPort is offline.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

253 of 492

3: Hardware Agent Alarms

DRAFT

Severity

Normal

Alarm Automatically
Cleared

No

Q-Logic Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

3.6.91

Alarm 2991103
Specific Problem

2991103

Managed Object

Q-Logic

Description

Q-Logic - QxPort link up. Current QxPort operational status is


online. Desired status of the QxPort is testing.

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

254 of 492

DRAFT

OS Agent Alarms

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

4.1

OS Agent Alarm Overview

OS Agent Alarm Overview


OS Agent alarms monitor the operating systems and generate an alarm if the
system is not functioning properly.
The following OS Agent alarms are monitored:

CCS_OS Alarms, Page 257


SUN OS Alarms (OnGuard Agent), Page 259
Health Probe Alarms, Page 276

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

256 of 492

4: OS Agent Alarms

4.2

DRAFT

CCS_OS Alarms

CCS_OS Alarms
Search for the alarm you need by its Specific Problem (Alarm ID).

4.2.1

Alarm 4087005
Specific Problem

4087005

Managed Object

CCS_OS

Description

SIGH process failed.

Severity

Major

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

Yes; by 4087005

Threshold

0 instances

System Impact

Switch over will occur.

Recommended
Corrective Action

Contact Comverse customer support for problem analysis.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

4.2.2

Alarm 4087006
Specific Problem

4087006

Managed Object

CCS_OS

Description

LAN process failed.

Severity

Major

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

Yes; by 4087006

Threshold

0 instances

System Impact

Switch over will occur.

Recommended
Corrective Action

Contact Comverse customer support for problem analysis.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

4.2.3

Alarm 4087501

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

257 of 492

4: OS Agent Alarms

DRAFT

CCS_OS Alarms

Specific Problem

4087501

Managed Object

CCS_OS

Description

SIGH process overloaded.

Severity

Major

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

Yes; by 4087501

Threshold

1900 messages in queue

System Impact

Possible messages loss.

Recommended
Corrective Action

Contact Comverse customer support for problem analysis.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

4.2.4

Alarm 4087504
Specific Problem

4087504

Managed Object

CCS_OS

Description

L3_MTP process overloaded.

Severity

Major

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

Yes; by 4087504

Threshold

1900 messages in queue

System Impact

Possible messages loss.

Recommended
Corrective Action

Contact Comverse customer support for problem analysis.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

258 of 492

4: OS Agent Alarms

4.3

DRAFT

SUN OS Alarms (OnGuard Agent)

SUN OS Alarms (OnGuard Agent)


Search for the alarm you need by its Specific Problem (Alarm ID).

4.3.1

Alarm 2112001
Specific Problem

2112001

Managed Object

OnGuard

Description

The CPU usage is <CPU value>%.

Additional
Information

<CPU value>: Percentage of the CPU in use

Severity

Normal

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

No

Threshold

069%

For a detailed description of these rows, see Alarm Fields Description, Page 7.

4.3.2

Alarm 2112002
Specific Problem

2112002

Managed Object

OnGuard

Description

The CPU usage is <CPU value>%. There is a problem with


the last <events number> events.

Additional
Information

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112001

Threshold

7089%

System Impact

Lower system performance.

Recommended
Corrective Action

Kill the process which consumes the CPU provided you do


not harm your system.

<CPU value>: Percentage of the CPU in use


<events number>: Number of consequent events with
this problem

Identify why the CPU consumption is high.

For a detailed description of these rows, see Alarm Fields Description, Page 7.
SMSC 4.2 Alarm Reference Manual
P/N 10-000-1050 Issue 1 Rev. 0.1

259 of 492

4: OS Agent Alarms

4.3.3

DRAFT

SUN OS Alarms (OnGuard Agent)

Alarm 2112003
Specific Problem

2112003

Managed Object

OnGuard

Description

The CPU usage is <CPU value>%. There is a problem with


the last <events number> events.

Additional
Information

Severity

Major

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112001

Threshold

90100%

System Impact

Lower system performance.

Recommended
Corrective Action

Kill the process which consumes the CPU provided you do


not harm your system.

<CPU value>: Percentage of the CPU in use


<events number>: Number of consequent events with
this problem

Identify why the CPU consumption is high.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

4.3.4

Alarm 2112004
Specific Problem

2112004

Managed Object

OnGuard

Description

A CPU usage event timed out.

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112001

System Impact

CPU usage is not checked.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

4.3.5

Alarm 2112005

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

260 of 492

4: OS Agent Alarms

DRAFT

SUN OS Alarms (OnGuard Agent)

Specific Problem

2112005

Managed Object

OnGuard

Description

A CPU usage event failed.

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112001

System Impact

CPU usage is not checked.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

4.3.6

Alarm 2112006
Specific Problem

2112006

Managed Object

OnGuard

Description

<usage value>% of the <file system> file system is in use


(<used MB> of <total MB> MB).

Additional
Information

<usage value>: Percentage used

<total MB>: Total number of MB in the file system

<file system>: File system name


<used MB>: Number of MB in the file system that are
in use

Severity

Normal

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

No

Threshold

089%

For a detailed description of these rows, see Alarm Fields Description, Page 7.

4.3.7

Alarm 2112007
Specific Problem

2112007

Managed Object

OnGuard

Description

<usage value>% of the <file system> file system is in use


(<used MB> of <total MB> MB).

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

261 of 492

4: OS Agent Alarms

Additional
Information

DRAFT

SUN OS Alarms (OnGuard Agent)

<usage value>: Percentage used

<total MB>: Total number of MB in the file system

<file system>: File system name


<used MB>: Number of MB in the file system that are
in use

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112006

Threshold

9094%

System Impact

Some applications may fail.

Recommended
Corrective Action

Delete unnecessary files from the file system. If none


available, the file system capacity should be enlarged.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

4.3.8

Alarm 2112008
Specific Problem

2112008

Managed Object

OnGuard

Description

<usage value>% of the <file system> file system is in use


(<used MB> of <total MB> MB).

Additional
Information

<usage value>: Percentage used

<total MB>: Total number of MB in the file system

<file system>: File system name


<used MB>: Number of MB in the file system that are
in use

Severity

Major

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112006

Threshold

95100%

System Impact

Some applications may fail.

Recommended
Corrective Action

Delete unnecessary files from the file system. If none


available, the file system capacity should be enlarged.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

262 of 492

4: OS Agent Alarms

4.3.9

DRAFT

SUN OS Alarms (OnGuard Agent)

Alarm 2112009
Specific Problem

2112009

Managed Object

OnGuard

Description

A file system free space event timed out.

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112006

System Impact

File system free space is not checked.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

4.3.10

Alarm 2112010
Specific Problem

2112010

Managed Object

OnGuard

Description

A file system free space event failed.

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112006

System Impact

File system free space is not checked.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

4.3.11

Alarm 2112011
Specific Problem

2112011

Managed Object

OnGuard

Description

The load average is <load average value>.

Additional
Information

<load average value>: Load average value.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

263 of 492

4: OS Agent Alarms

DRAFT

Severity

Normal

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

No

Threshold

02

SUN OS Alarms (OnGuard Agent)

For a detailed description of these rows, see Alarm Fields Description, Page 7.

4.3.12

Alarm 2112012
Specific Problem

2112012

Managed Object

OnGuard

Description

The load average is <load average value>. There is a


problem with the last <events number> events.

Additional
Information

<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 last
15 minutes per processor.
Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112011

Threshold

23

System Impact

Lower system performance.

Recommended
Corrective Action

Reduce the number of heavy applications on the unit if


possible.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

4.3.13

Alarm 2112013
Specific Problem

2112013

Managed Object

OnGuard

Description

The load average is <load average value>. There is a


problem with the last <events number> events.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

264 of 492

4: OS Agent Alarms

Additional
Information

DRAFT

SUN OS Alarms (OnGuard Agent)

<load average value>: Load average value


<events number>: Number of consequent events with
this problem

Very high average number of jobs in the run queue over the
last 15 minutes per processor.
Severity

Major

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112011

Threshold

4+

System Impact

Lower system performance.

Recommended
Corrective Action

Reduce the number of heavy applications on the machine if


possible.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

4.3.14

Alarm 2112014
Specific Problem

2112014

Managed Object

OnGuard

Description

A load average event timed out.

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112011

System Impact

Load average is not checked.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

4.3.15

Alarm 2112015
Specific Problem

2112015

Managed Object

OnGuard

Description

A load average event failed.

Severity

Warning

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

265 of 492

4: OS Agent Alarms

DRAFT

SUN OS Alarms (OnGuard Agent)

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112011

System Impact

Load average is not checked.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

4.3.16

Alarm 2112016
Specific Problem

2112016

Managed Object

OnGuard

Description

The swap usage is <swap value>%.

Additional
Information

<swap value>: Percentage of swap area in use.

Severity

Normal

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

No

Threshold

069%

For a detailed description of these rows, see Alarm Fields Description, Page 7.

4.3.17

Alarm 2112017
Specific Problem

2112017

Managed Object

OnGuard

Description

The swap usage is <swap value>%. There is a problem with


the last <events number> events.

Additional
Information

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112016

Threshold

7089%

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

<swap value>: Percentage of swap area in use


<events number>: Number of consequent events with
this problem

266 of 492

4: OS Agent Alarms

DRAFT

SUN OS Alarms (OnGuard Agent)

System Impact

Lower system performance.

Recommended
Corrective Action

Enlarge swap area size on this machine if possible.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

4.3.18

Alarm 2112018
Specific Problem

2112018

Managed Object

OnGuard

Description

The swap usage is <swap value>%. There is a problem with


the last <events number> events.

Additional
Information

Severity

Major

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112016

Threshold

90100%

System Impact

Lower system performance.

Recommended
Corrective Action

Enlarge swap area size on this machine if possible.

<swap value>: Percentage of swap area in use


<events number>: Number of consequent events with
this problem

For a detailed description of these rows, see Alarm Fields Description, Page 7.

4.3.19

Alarm 2112019
Specific Problem

2112019

Managed Object

OnGuard

Description

A swap usage event timed out.

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112016

System Impact

Swap usage is not checked.

Recommended
Corrective Action

Contact Comverse customer support.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

267 of 492

4: OS Agent Alarms

DRAFT

SUN OS Alarms (OnGuard Agent)

For a detailed description of these rows, see Alarm Fields Description, Page 7.

4.3.20

Alarm 2112020
Specific Problem

2112020

Managed Object

OnGuard

Description

A swap usage event failed.

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112016

System Impact

Swap usage is not checked.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

4.3.21

Alarm 2112021
Specific Problem

2112021

Managed Object

OnGuard

Description

The I/O wait is <I/O waits value>%.

Additional
Information

<I/O waits value>: Percentage of I/O waits out of the total


CPU time.

Severity

Normal

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

No

Threshold

09

For a detailed description of these rows, see Alarm Fields Description, Page 7.

4.3.22

Alarm 2112022
Specific Problem

2112022

Managed Object

OnGuard

Description

The I/O wait is <I/O waits value>%. There is a problem with


the last <events number> events.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

268 of 492

4: OS Agent Alarms

Additional
Information

DRAFT

SUN OS Alarms (OnGuard Agent)

<I/O waits value>: Percentage of I/O waits out of the


total CPU time

<events number>: Number of consequent events with


this problem

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112021

Threshold

10-29

System Impact

Lower system performance.

Recommended
Corrective Action

If possible, stop using the problematic application, or else


CPUs may need to be added to this machine.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

4.3.23

Alarm 2112023
Specific Problem

2112023

Managed Object

OnGuard

Description

The I/O wait is <I/O waits value>%. There is a problem with


the last <events number> events.

Additional
Information

<I/O waits value>: Percentage of I/O waits out of the


total CPU time

<events number>: Number of consequent events with


this problem

Severity

Major

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112021

Threshold

30+

System Impact

Lower system performance.

Recommended
Corrective Action

If possible, stop using the problematic application, or else


CPUs may need to be added to this machine.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

4.3.24

Alarm 2112024

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

269 of 492

4: OS Agent Alarms

DRAFT

SUN OS Alarms (OnGuard Agent)

Specific Problem

2112024

Managed Object

OnGuard

Description

An I/O wait event timed out.

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112021

System Impact

I/O wait is not checked.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

4.3.25

Alarm 2112025
Specific Problem

2112025

Managed Object

OnGuard

Description

An I/O wait event failed.

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112021

System Impact

I/O wait is not checked.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

4.3.26

Alarm 2112026
Specific Problem

2112026

Managed Object

OnGuard

Description

The network response time for <server name> is normal.

Additional
Information

<server name>: Server name, IP, or URL

Severity

Normal

Message Group
(Probable Cause)

Operating System

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

270 of 492

4: OS Agent Alarms

DRAFT

Alarm Automatically
Cleared

No

Threshold

019 ms

SUN OS Alarms (OnGuard Agent)

For a detailed description of these rows, see Alarm Fields Description, Page 7.

4.3.27

Alarm 2112027
Specific Problem

2112027

Managed Object

OnGuard

Description

High network response time. The network response time for


<server name> is <response time> ms.

Additional
Information

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112026

Threshold

20+ ms

System Impact

Poor network connection to the remote server which may


cause slow data transfer.

Recommended
Corrective Action

System administrator to check the network and remote server.

<server name>: Server name, IP, or URL


<response time>: Average response time in ms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

4.3.28

Alarm 2112028
Specific Problem

2112028

Managed Object

OnGuard

Description

<server name> is not responding to a ping request (<lost


packets> out of <sent packets> packets lost).

Additional
Information

<server name>: Server name, IP, or URL


<lost packets>: Number of lost packets
<sent packets>: Number of sent packets

Severity

Critical

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112026

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

271 of 492

4: OS Agent Alarms

DRAFT

SUN OS Alarms (OnGuard Agent)

Threshold

Failed ping

System Impact

Remote server is not accessible.

Recommended
Corrective Action

System administrator to check the network and remote server.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

4.3.29

Alarm 2112029
Specific Problem

2112029

Managed Object

OnGuard

Description

Ping error for <server name> (unknown host <server name>).

Additional
Information

<server name>: Server name, IP, or URL.

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112026

Threshold

Failed ping

System Impact

Remote server is not accessible.

Recommended
Corrective Action

Ask the system administrator about this host name and in


case of need, change it in OnGuard.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

4.3.30

Alarm 2112030
Specific Problem

2112030

Managed Object

OnGuard

Description

Network availability event timed out.

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112026

System Impact

Network availability is not checked.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.
SMSC 4.2 Alarm Reference Manual
P/N 10-000-1050 Issue 1 Rev. 0.1

272 of 492

4: OS Agent Alarms

4.3.31

DRAFT

SUN OS Alarms (OnGuard Agent)

Alarm 2112031
Specific Problem

2112031

Managed Object

OnGuard

Description

Pinging <server name> failed.

Additional
Information

<server name>: Server name, IP, or URL

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112026

System Impact

This server is not checked for network availability.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

4.3.32

Alarm 2112032
Specific Problem

2112032

Managed Object

OnGuard

Description

<memory used>% of the physical memory is in use (<used


MB> of <total MB> MB).

Additional
Information

<memory used>: Percentage of memory in use


<used MB>: Number of MB of memory in use
<total MB>: Total MB of memory

Severity

Normal

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

No

Threshold

084%

For a detailed description of these rows, see Alarm Fields Description, Page 7.

4.3.33

Alarm 2112033

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

273 of 492

4: OS Agent Alarms

DRAFT

SUN OS Alarms (OnGuard Agent)

Specific Problem

2112033

Managed Object

OnGuard

Description

<memory used>% of the physical memory is in use (<used


MB> of <total MB> MB).

Additional
Information

<memory used>: Percentage of memory in use


<used MB>: Number of MB of memory in use
<total MB>: Total MB of memory

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112032

Threshold

8594%

System Impact

Lower system performance.

Recommended
Corrective Action

Do one of the following:

If the server performance is low, check which


application is consuming a lot of memory and stop using
it if possible.

If the server performance is not low, add memory to


the machine.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

4.3.34

Alarm 2112034
Specific Problem

2112034

Managed Object

OnGuard

Description

<memory used>% of the physical memory is in use (<used


MB> of <total MB> MB).

Additional
Information

<memory used>: Percentage of memory in use


<used MB>: Number of MB of memory in use
<total MB>: Total MB of memory

Severity

Major

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112032

Threshold

95100%

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

274 of 492

4: OS Agent Alarms

DRAFT

System Impact

Lower system performance

Recommended
Corrective Action

Do one of the following:

SUN OS Alarms (OnGuard Agent)

If the server performance is low, check which


application is consuming a lot of memory and stop using
it if possible.

If the server performance is not low, add memory to


the machine.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

4.3.35

Alarm 2112035
Specific Problem

2112035

Managed Object

OnGuard

Description

A physical memory free event timed out.

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112032

System Impact

Physical memory free space is not checked.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

4.3.36

Alarm 2112036
Specific Problem

2112036

Managed Object

OnGuard

Description

A physical memory free event failed.

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112032

System Impact

Physical memory free space is not checked.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.
SMSC 4.2 Alarm Reference Manual
P/N 10-000-1050 Issue 1 Rev. 0.1

275 of 492

4: OS Agent Alarms

4.4

DRAFT

Health Probe Alarms

Health Probe Alarms


Search for the alarm you need by its Specific Problem (Alarm ID).

4.4.1

Alarm 2980001
Specific Problem

2980001

Managed Object

SMSCHP

Description

<eventType> utilization of CPU id <cpuID> has reached


<CPUload>%.

Additional
Information

CPU

Severity

Critical
Major
Minor
Normal

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

Yes; by 2980001

System Impact

Possible impacts:

Recommended
Corrective Action

If CPU, System performance might be affected.


If CPU, No impact.

If CPU, Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

4.4.2

Alarm 2980002
Specific Problem

2980002

Managed Object

SMSCHP

Description

<eventType> utilization has reached <usedSize> out of


<totalSize>.

Additional
Information

Physical memory

Severity

Critical
Major
Minor
Normal

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

276 of 492

4: OS Agent Alarms

DRAFT

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

Yes; by 2980002

System Impact

Possible impacts:

Recommended
Corrective Action

Health Probe Alarms

If Physical memory, System performance might be


affected.

If Physical memory, No impact.

If Physical memory, Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

4.4.3

Alarm 2980003
Specific Problem

2980003

Managed Object

SMSCHP

Description

<eventType> utilization has reached <usedSize> out of


<totalSize>.

Additional
Information

Swap memory

Severity

Critical
Major
Minor
Normal

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

Yes; by 2980003

System Impact

Possible impacts:

Recommended
Corrective Action

If Swap memory, System performance might be affected.


If Swap memory, No impact.

If Swap memory, Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

4.4.4

Alarm 2980004
Specific Problem

2980004

Managed Object

SMSCHP

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

277 of 492

4: OS Agent Alarms

DRAFT

Health Probe Alarms

Description

<eventType> utilization of <FSname> has reached


<usedSize> out of <totalSize>.

Additional
Information

File system

Severity

Critical
Major
Minor
Normal

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

Yes; by 2980004

System Impact

Possible impacts:

Recommended
Corrective Action

If File system, System performance might be affected.


If File system, No impact.

If File system, Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

278 of 492

DRAFT

Cluster Agent Alarms

Cluster Agent Alarms Overview, Page 280

SUN Cluster HA Alarms (OnGuard Agent), Page 281

Veritas 3.5 Cluster Alarms, Page 286

5: Cluster Agent Alarms

5.1

DRAFT

Cluster Agent Alarms Overview

Cluster Agent Alarms Overview


Cluster Agent alarms monitor the cluster units and generate an alarm if the unit is
not functioning properly.
The following Cluster Agent alarms are monitored:

CCS_OS Alarms, Page 257


SUN OS Alarms (OnGuard Agent), Page 259
Health Probe Alarms, Page 276

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

280 of 492

5: Cluster Agent Alarms

5.2

DRAFT

SUN Cluster HA Alarms (OnGuard Agent)

SUN Cluster HA Alarms (OnGuard Agent)


Search for the alarm you need by its Specific Problem (Alarm ID).

5.2.1

Alarm 2113042
Specific Problem

2113042

Managed Object

OnGuard

Description

The <ResourceGroupName> service on the <NodeName>


host was restarted.

Additional
Information

Severity

Normal

Message Group
(Probable Cause)

High Availability

Alarm Automatically
Cleared

No

<ResourceGroupName>: Service name


<NodeName>: Host name

For a detailed description of these rows, see Alarm Fields Description, Page 7.

5.2.2

Alarm 2113043
Specific Problem

2113043

Managed Object

OnGuard

Description

The <ResourceGroupName> service on the <NodeName>


host cannot start.

Additional
Information

Severity

Major

Message Group
(Probable Cause)

High Availability

Alarm Automatically
Cleared

Yes; by 2113042

System Impact

Depends on the resource; there may be downtime.

Recommended
Corrective Action

Contact Comverse customer support.

<ResourceGroupName>: Service name


<NodeName>: Host name

For a detailed description of these rows, see Alarm Fields Description, Page 7.

5.2.3

Alarm 2113044

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

281 of 492

5: Cluster Agent Alarms

DRAFT

SUN Cluster HA Alarms (OnGuard Agent)

Specific Problem

2113044

Managed Object

OnGuard

Description

The <ResourceGroupName> service on the <NodeName>


host was restarted.

Additional
Information

Severity

Normal

Message Group
(Probable Cause)

High Availability

Alarm Automatically
Cleared

No

<ResourceGroupName>: Service name


<NodeName>: Host name

For a detailed description of these rows, see Alarm Fields Description, Page 7.

5.2.4

Alarm 2113045
Specific Problem

2113045

Managed Object

OnGuard

Description

The <ResourceGroupName> service on the <NodeName>


host is offline.

Additional
Information

Severity

Major

Message Group
(Probable Cause)

High Availability

Alarm Automatically
Cleared

Yes; by 2113044

System Impact

Depends on the resource; there may be downtime.

Recommended
Corrective Action

Check if the service is really down, and that it is not a false


alarm. If the service is not online on any node and not
restarted automatically, manually restart the service.

<ResourceGroupName>: Service name


<NodeName>: Host name

For a detailed description of these rows, see Alarm Fields Description, Page 7.

5.2.5

Alarm 2113046
Specific Problem

2113046

Managed Object

OnGuard

Description

The <ResourceGroupName> service on the <NodeName>


host was restarted.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

282 of 492

5: Cluster Agent Alarms

DRAFT

Additional
Information

Severity

Normal

Message Group
(Probable Cause)

High Availability

Alarm Automatically
Cleared

No

SUN Cluster HA Alarms (OnGuard Agent)

<ResourceGroupName>: Service name


<NodeName>: Host name

For a detailed description of these rows, see Alarm Fields Description, Page 7.

5.2.6

Alarm 2113047
Specific Problem

2113047

Managed Object

OnGuard

Description

The <ResourceGroupName> service on the <NodeName>


host failed.

Additional
Information

Severity

Major

Message Group
(Probable Cause)

High Availability

Alarm Automatically
Cleared

Yes; by 2113046

System Impact

Depends on the resource; there may be downtime.

Recommended
Corrective Action

If the alarm is not cleared automatically, restart the resource.

<ResourceGroupName>: Service name


<NodeName>: Host name

For a detailed description of these rows, see Alarm Fields Description, Page 7.

5.2.7

Alarm 2113048
Specific Problem

2113048

Managed Object

OnGuard

Description

The <NodeName> host is up.

Additional
Information

<NodeName>: Host name

Severity

Normal

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

283 of 492

5: Cluster Agent Alarms

DRAFT

Message Group
(Probable Cause)

High Availability

Alarm Automatically
Cleared

No

SUN Cluster HA Alarms (OnGuard Agent)

For a detailed description of these rows, see Alarm Fields Description, Page 7.

5.2.8

Alarm 2113049
Specific Problem

2113049

Managed Object

OnGuard

Description

The <NodeName> host is down.

Additional
Information

<NodeName>: Host name

Severity

Critical

Message Group
(Probable Cause)

High Availability

Alarm Automatically
Cleared

Yes; by 2113048

System Impact

Depends on the resource; there may be downtime.

Recommended
Corrective Action

Check that the node is alive. Check that the heartbeat cables
are properly connected.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

5.2.9

Alarm 2113050
Specific Problem

2113050

Managed Object

OnGuard

Description

The <ResourceGroupName> service cannot fail over.

Additional
Information

<NodeName>: Host name

Severity

Critical

Message Group
(Probable Cause)

High Availability

Alarm Automatically
Cleared

Yes; by 2113044

Recommended
Corrective Action

Contact Comverse customer support.

The service is failing on both nodes and cannot be restarted.

For a detailed description of these rows, see Alarm Fields Description, Page 7.
SMSC 4.2 Alarm Reference Manual
P/N 10-000-1050 Issue 1 Rev. 0.1

284 of 492

5: Cluster Agent Alarms

5.2.10

DRAFT

SUN Cluster HA Alarms (OnGuard Agent)

Alarm 2113051
Specific Problem

2113051

Managed Object

OnGuard

Description

The <ResourceGroupName> service on the <NodeName>


host cannot start.

Additional
Information

<ResourceGroupName>: Service name


<NodeName>: Host name

The service is failing on both nodes and cannot be restarted.


Severity

Critical

Message Group
(Probable Cause)

High Availability

Alarm Automatically
Cleared

Yes; by 2113044

System Impact

Depends on the resource; there may be downtime.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

285 of 492

5: Cluster Agent Alarms

5.3

DRAFT

Veritas 3.5 Cluster Alarms

Veritas 3.5 Cluster Alarms


Search for the alarm you need by its Specific Problem (Alarm ID).

5.3.1

Alarm 2121011
Specific Problem

2121011

Managed Object

Veritas

Description

Resource <ResourceName> of type: <ResourceType> on


<systemName>: Resource State Unknown

Additional
Information

Resource vcs_SMSC of type: NotifierMngr on lsi1a: Resource


State Unknown

Severity

Minor

Message Group
(Probable Cause)

High Availability

Alarm Automatically
Cleared

No

System Impact

System is not monitored properly; downtime to service is


possible.

Recommended
Corrective Action

Verify that all resources (persistent and non-persistent) are


online. If not, contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

5.3.2

Alarm 2121012
Specific Problem

2121012

Managed Object

Veritas

Description

Resource <ResourceName> of type: <ResourceType> on


<systemName>: Resource Monitor Timeout

Additional
Information

Resource vcs_SMSC of type: NotifierMngr on lsi1a: Resource


Monitor Timeout

Severity

Minor

Message Group
(Probable Cause)

High Availability

Alarm Automatically
Cleared

No

System Impact

System is not monitored properly; downtime to service is


possible.

Recommended
Corrective Action

Manually verify the state of the resource.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

286 of 492

5: Cluster Agent Alarms

DRAFT

Veritas 3.5 Cluster Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

5.3.3

Alarm 2121013
Specific Problem

2121013

Managed Object

Veritas

Description

Resource <ResourceName> of type: <ResourceType> on


<systemName>: Resource Not Going Offline

Additional
Information

Resource vcs_SMSC of type: NotifierMngr on lsi1a: Resource


Not Going Offline

Severity

Minor

Message Group
(Probable Cause)

High Availability

Alarm Automatically
Cleared

No

System Impact

System is not monitored properly; downtime to service is


possible.

Recommended
Corrective Action

Check the logs for the cause of the resource not going offline.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

5.3.4

Alarm 2121014
Specific Problem

2121014

Managed Object

Veritas

Description

Resource <ResourceName> of type: <ResourceType> on


<systemName>: Resource Restarted By Agent

Additional
Information

Resource vcs_SMSC of type: NotifierMngr on lsi1a: Resource


Restarted By Agent

Severity

Warning

Message Group
(Probable Cause)

High Availability

Alarm Automatically
Cleared

No

System Impact

System is not monitored properly; downtime to service is


possible.

Recommended
Corrective Action

Check the logs for the cause of the resource restart.

For a detailed description of these rows, see Alarm Fields Description, Page 7.
SMSC 4.2 Alarm Reference Manual
P/N 10-000-1050 Issue 1 Rev. 0.1

287 of 492

5: Cluster Agent Alarms

5.3.5

DRAFT

Veritas 3.5 Cluster Alarms

Alarm 2121015
Specific Problem

2121015

Managed Object

Veritas

Description

Resource <ResourceName> of type: <ResourceType> on


<systemName>: Resource Went Online By Itself

Additional
Information

Resource vcs_SMSC of type: NotifierMngr on lsi1a: Resource


Went Online By Itself

Severity

Warning

Message Group
(Probable Cause)

High Availability

Alarm Automatically
Cleared

No

System Impact

System is not monitored properly; downtime to service is


possible.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

5.3.6

Alarm 2121016
Specific Problem

2121016

Managed Object

Veritas

Description

Resource <ResourceName> of type: <ResourceType> on


<systemName>: Resource Faulted

Additional
Information

Resource vcs_SMSC of type: NotifierMngr on lsi1a: Resource


Faulted

Severity

Major

Message Group
(Probable Cause)

High Availability

Alarm Automatically
Cleared

Yes; by 2121015

System Impact

Depending on the group may cause downtime.

Recommended
Corrective Action

Check the /var/VRTSvcs/log/engina_A.log file to check the


reason the resource faulted. Try to clear the fault and return
the resource to online.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

5.3.7

Alarm 2121021

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

288 of 492

5: Cluster Agent Alarms

DRAFT

Veritas 3.5 Cluster Alarms

Specific Problem

2121021

Managed Object

Veritas

Description

Service Group <ServiceGroupName> of type:


<ServiceGroupType> on <systemName>: Service Group
Online

Additional
Information

Service Group Server of type: Parallel on lsi1a: Service Group


Online

Severity

Normal

Message Group
(Probable Cause)

High Availability

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

5.3.8

Alarm 2121022
Specific Problem

2121022

Managed Object

Veritas

Description

Service Group <ServiceGroupName> of type:


<ServiceGroupType> on <systemName>: Service Group
Offline

Additional
Information

Service Group Server of type: Parallel on lsi1a: Service Group


Offline

Severity

Warning

Message Group
(Probable Cause)

High Availability

Alarm Automatically
Cleared

Yes; by 2121021

System Impact

Depending on the group may cause downtime.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

5.3.9

Alarm 2121023
Specific Problem

2121023

Managed Object

Veritas

Description

Service Group <ServiceGroupName> of type:


<ServiceGroupType> on <systemName>: Service Group
Autodisabled

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

289 of 492

5: Cluster Agent Alarms

DRAFT

Veritas 3.5 Cluster Alarms

Additional
Information

Service Group Server of type: Parallel on lsi1a: Service Group


Autodisabled

Severity

Warning

Message Group
(Probable Cause)

High Availability

Alarm Automatically
Cleared

No

Recommended
Corrective Action

If all systems are online and service group is still in the


Autodisabled state, run the command:
hagrp -autoenable <group> -sys <system>.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

5.3.10

Alarm 2121024
Specific Problem

2121024

Managed Object

Veritas

Description

Service Group <ServiceGroupName> of type:


<ServiceGroupType> on <systemName>: Service group has
faulted

Additional
Information

Service Group Server of type: Parallel on lsi1a: Service group


has faulted

Severity

Critical

Message Group
(Probable Cause)

High Availability

Alarm Automatically
Cleared

Yes; by 2121021

System Impact

Depending on the group may cause downtime.

Recommended
Corrective Action

Clear the fault (via command line or GUI) then try to turn the
service group online.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

5.3.11

Alarm 2121025
Specific Problem

2121025

Managed Object

Veritas

Description

Service Group <ServiceGroupName> of type:


<ServiceGroupType> on <systemName>: Service Group
Faulted Nowhere To Failover

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

290 of 492

5: Cluster Agent Alarms

DRAFT

Veritas 3.5 Cluster Alarms

Additional
Information

Service Group Server of type: Parallel on lsi1a: Service Group


Faulted Nowhere To Failover

Severity

Critical

Message Group
(Probable Cause)

High Availability

Alarm Automatically
Cleared

Yes; by 2121021

System Impact

Probable downtime.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

5.3.12

Alarm 2121026
Specific Problem

2121026

Managed Object

Veritas

Description

Service Group <ServiceGroupName> of type:


<ServiceGroupType> on <systemName>: Service Group
Restarting

Additional
Information

Service Group Server of type: Parallel on lsi1a: Service Group


Restarting

Severity

Warning

Message Group
(Probable Cause)

High Availability

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

5.3.13

Alarm 2121027
Specific Problem

2121027

Managed Object

Veritas

Description

Service Group <ServiceGroupName> of type:


<ServiceGroupType> on <systemName>: Service Group
Being Switched

Additional
Information

Service Group Server of type: Parallel on lsi1a: Service Group


Being Switched

Severity

Warning

Message Group
(Probable Cause)

High Availability

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

291 of 492

5: Cluster Agent Alarms

DRAFT

Veritas 3.5 Cluster Alarms

Alarm Automatically
Cleared

No

System Impact

Depending on the service, a short downtime may occur.

Recommended
Corrective Action

Follow up on the system and ensure the service group and all
resources turn to an online state.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

5.3.14

Alarm 2121028
Specific Problem

2121028

Managed Object

Veritas

Description

Service Group <ServiceGroupName> of type:


<ServiceGroupType> on <systemName>: Service Group
Concurrency Violation

Additional
Information

Service Group Server of type: Parallel on lsi1a: Service Group


Concurrency Violation

Severity

Critical

Message Group
(Probable Cause)

High Availability

Alarm Automatically
Cleared

No

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

5.3.15

Alarm 2121029
Specific Problem

2121029

Managed Object

Veritas

Description

Service Group <ServiceGroupName> of type:


<ServiceGroupType> on <systemName>: Service Group
Restarting In Response

Additional
Information

Service Group Server of type: Parallel on lsi1a: Service Group


Restarting In Response

Severity

Warning

Message Group
(Probable Cause)

High Availability

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

292 of 492

5: Cluster Agent Alarms

DRAFT

Veritas 3.5 Cluster Alarms

Alarm Automatically
Cleared

No

Recommended
Corrective Action

Follow up on the system and ensure the service group and all
resources turn to an online state.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

5.3.16

Alarm 2121031
Specific Problem

2121031

Managed Object

Veritas

Description

System <SystemName> of type: m: sun4u, sys: SunOS, r: 5.8


on <systemName>: System Up On The First Node

Additional
Information

System ins3b of type: m: sun4u, sys: SunOS, r: 5.8 on ins3b:


System Up On The First Node

Severity

Warning

Message Group
(Probable Cause)

High Availability

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

5.3.17

Alarm 2121032
Specific Problem

2121032

Managed Object

Veritas

Description

System <SystemName> of type: m: sun4u, sys: SunOS, r: 5.8


on <systemName>: System Restarting By HASHADOW

Additional
Information

System ins3b of type: m: sun4u, sys: SunOS, r: 5.8 on ins3b:


System Restarting By HASHADOW

Severity

Minor

Message Group
(Probable Cause)

High Availability

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

5.3.18

Alarm 2121033

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

293 of 492

5: Cluster Agent Alarms

DRAFT

Veritas 3.5 Cluster Alarms

Specific Problem

2121033

Managed Object

Veritas

Description

System <SystemName> of type: m: sun4u, sys: SunOS, r: 5.8


on <systemName>: System In Jeopardy

Additional
Information

System ins3b of type: m: sun4u, sys: SunOS, r: 5.8 on ins3b:


System In Jeopardy

Severity

Major

Message Group
(Probable Cause)

High Availability

Alarm Automatically
Cleared

No

System Impact

No immediate impact, but High Availability level is degraded,


and next fault will lead to downtime.

Recommended
Corrective Action

Ensure node heartbeat connections are connected. If


problems continue, contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

5.3.19

Alarm 2121034
Specific Problem

2121034

Managed Object

Veritas

Description

System <SystemName> of type: m: sun4u, sys: SunOS, r: 5.8


on <systemName>: System Faulted

Additional
Information

System ins3b of type: m: sun4u, sys: SunOS, r: 5.8 on ins3b:


System Faulted

Severity

Minor

Message Group
(Probable Cause)

High Availability

Alarm Automatically
Cleared

No

System Impact

No immediate impact, but High Availability level is degraded,


and the next fault will lead to downtime.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

5.3.20

Alarm 2121035

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

294 of 492

5: Cluster Agent Alarms

DRAFT

Veritas 3.5 Cluster Alarms

Specific Problem

2121035

Managed Object

Veritas

Description

System <SystemName> of type: m: sun4u, sys: SunOS, r: 5.8


on <systemName>: System Joined Cluster

Additional
Information

System ins3b of type: m: sun4u, sys: SunOS, r: 5.8 on ins3b:


System Joined Cluster

Severity

Normal

Message Group
(Probable Cause)

High Availability

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

5.3.21

Alarm 2121036
Specific Problem

2121036

Managed Object

Veritas

Description

System <SystemName> of type: m: sun4u, sys: SunOS, r: 5.8


on <systemName>: System Exited Manually

Additional
Information

System ins3b of type: m: sun4u, sys: SunOS, r: 5.8 on ins3b:


System Exited Manually

Severity

Normal

Message Group
(Probable Cause)

High Availability

Alarm Automatically
Cleared

No

System Impact

High Availability level is degraded.

Recommended
Corrective Action

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.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

5.3.22

Alarm 2121037
Specific Problem

2121037

Managed Object

Veritas

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

295 of 492

5: Cluster Agent Alarms

DRAFT

Veritas 3.5 Cluster Alarms

Description

System <SystemName> of type: m: sun4u, sys: SunOS, r: 5.8


on <systemName>: System Up But Not In Cluster

Additional
Information

System ins3b of type: m: sun4u, sys: SunOS, r: 5.8 on ins3b:


System Up But Not In Cluster

Severity

Warning

Message Group
(Probable Cause)

High Availability

Alarm Automatically
Cleared

No

System Impact

High Availability level is degraded.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

5.3.23

Alarm 2121062
Specific Problem

2121062

Managed Object

Veritas

Description

VCS <SystemName> of type: <UserName> on


<systemName>: GUI User Login

Additional
Information

VCS ins3a of type: unknown user on ins3a: GUI User Login

Severity

Normal

Message Group
(Probable Cause)

High Availability

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

5.3.24

Alarm 2121081
Specific Problem

2121081

Managed Object

Veritas

Description

Agent <AgentType> of type: <AgentType> on <systemName>:


Agent Restarting

Additional
Information

Agent Process of type: Process on ins3a: Agent Restarting

Severity

Warning

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

296 of 492

5: Cluster Agent Alarms

DRAFT

Message Group
(Probable Cause)

High Availability

Alarm Automatically
Cleared

No

Veritas 3.5 Cluster Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

5.3.25

Alarm 2121082
Specific Problem

2121082

Managed Object

Veritas

Description

Agent <AgentType> of type: <AgentType> on <systemName>:


Agent Faulted

Additional
Information

Agent Process of type: Process on ins3a: Agent Faulted

Severity

Minor

Message Group
(Probable Cause)

High Availability

Alarm Automatically
Cleared

No

System Impact

No immediate impact but High Availability level is degraded.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

297 of 492

DRAFT

Networking Agent Alarms

Networking Agent Alarms Overview, Page 299

Cajun Alarms, Page 300

Others Alarms, Page 310

6: Networking Agent Alarms

6.1

DRAFT

Networking Agent Alarms Overview

Networking Agent Alarms Overview


Networking Agent alarms monitor the network units and generate an alarm if the
network is not functioning properly.
The following network agent alarms are monitored:

Cajun Alarms, Page 300


Others Alarms, Page 310

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

299 of 492

6: Networking Agent Alarms

6.2

DRAFT

Cajun Alarms

Cajun Alarms
Search for the alarm you need by its Specific Problem (Alarm ID).

6.2.1

Alarm 2810027
Specific Problem

2810027

Managed Object

Cajun

Description

Duplicate IP address <$2> detected; MAC address <$1>.

Additional
Information

Severity

Warning

Message Group
(Probable Cause)

Configuration

Alarm Automatically
Cleared

No

<$2>: IP address
<$1>: Corresponding MAC address

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.2.2

Alarm 2810028
Specific Problem

2810028

Managed Object

Cajun

Description

IP VLAN Violation from <$2>: expected VLAN <$4>, detected


VLAN <$5>.

Additional
Information

<$2>: Packet IP
<$4>: Expected VLAN
<$5>: Detected VLAN

Severity

Warning

Message Group
(Probable Cause)

Security

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.2.3

Alarm 2810044
Specific Problem

2810044

Managed Object

Cajun

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

300 of 492

6: Networking Agent Alarms

DRAFT

Description

LAG <$3> (<$2>) connection lost.

Additional
Information

Severity

Critical

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

Yes; by 2810046

Cajun Alarms

<$2>: LAG ID
<$3>: LAG name

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.2.4

Alarm 2810046
Specific Problem

2810046

Managed Object

Cajun

Description

LAG <$3> (<$2>) connection lost - was cleared.

Additional
Information

Severity

Normal

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

No

<$2>: LAG ID
<$3>: LAG name

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.2.5

Alarm 2810048
Specific Problem

2810048

Managed Object

Cajun

Description

LAG <$3> (<$2>) partial connection.

Additional
Information

Severity

Major

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

Yes; by 2810050

<$2>: LAG ID
<$3>: LAG name

For a detailed description of these rows, see Alarm Fields Description, Page 7.
SMSC 4.2 Alarm Reference Manual
P/N 10-000-1050 Issue 1 Rev. 0.1

301 of 492

6: Networking Agent Alarms

6.2.6

DRAFT

Cajun Alarms

Alarm 2810050
Specific Problem

2810050

Managed Object

Cajun

Description

LAG <$3> (<$2>) partial connection - was cleared.

Additional
Information

Severity

Normal

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

No

<$2>: LAG ID
<$3>: LAG name

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.2.7

Alarm 2810052
Specific Problem

2810052

Managed Object

Cajun

Description

LAG <$3> (<$2>) Auto Negotiation inconsistent results.

Additional
Information

Severity

Warning

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

Yes; by 2810054

<$2>: LAG ID
<$3>: LAG name

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.2.8

Alarm 2810054
Specific Problem

2810054

Managed Object

Cajun

Description

LAG no. <$2> Auto Negotiation inconsistent results - was


cleared.

Additional
Information

<$2>: LAG ID

Severity

Normal

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

302 of 492

6: Networking Agent Alarms

DRAFT

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

No

Cajun Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.2.9

Alarm 2810079
Specific Problem

2810079

Managed Object

Cajun

Description

Module <$2> Main Power Supply Failure.

Additional
Information

<$2>: Module ID

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 2810081

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.2.10

Alarm 2810081
Specific Problem

2810081

Managed Object

Cajun

Description

Module <$2> Main Power Supply Failure was cleared.

Additional
Information

<$2>: Module ID

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.2.11

Alarm 2810083

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

303 of 492

6: Networking Agent Alarms

DRAFT

Specific Problem

2810083

Managed Object

Cajun

Description

Module <$2> Backup Power Supply Failure.

Additional
Information

<$2>: Module ID

Severity

Warning

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 2810085

Cajun Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.2.12

Alarm 2810085
Specific Problem

2810085

Managed Object

Cajun

Description

Module <$2> Backup Power Supply Failure was cleared.

Additional
Information

<$2>: Module ID

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.2.13

Alarm 2810087
Specific Problem

2810087

Managed Object

Cajun

Description

Module <$2> Backup Power Supply Fan Failure.

Additional
Information

<$2>: Module ID

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 2810089

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

304 of 492

6: Networking Agent Alarms

DRAFT

Cajun Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.2.14

Alarm 2810089
Specific Problem

2810089

Managed Object

Cajun

Description

Module <$2> Backup Power Supply Fan Failure was cleared.

Additional
Information

<$2>: Module ID

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.2.15

Alarm 2810091
Specific Problem

2810091

Managed Object

Cajun

Description

Module <$2> Fan Failure.

Additional
Information

<$2>: Module ID

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 2810093

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.2.16

Alarm 2810093
Specific Problem

2810093

Managed Object

Cajun

Description

Module <$2> Fan Failure was cleared.

Additional
Information

<$2>: Module ID

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

305 of 492

6: Networking Agent Alarms

DRAFT

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Cajun Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.2.17

Alarm 2810600
Specific Problem

2810600

Managed Object

Cajun

Description

Agent Up with Possible Changes (coldStart Trap)


enterprise:<$E> (<$e>)

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.2.18

Alarm 2810602
Specific Problem

2810602

Managed Object

Cajun

Description

Agent Interface Down (linkDown Trap) enterprise:<$E>


(<$e>) on interface <$1>

Additional
Information

<$1>: Interface index

Severity

Major

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

Yes; by 2810603

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.2.19

Alarm 2810603

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

306 of 492

6: Networking Agent Alarms

DRAFT

Cajun Alarms

Specific Problem

2810603

Managed Object

Cajun

Description

Agent Interface Up (linkUp Trap) enterprise:<$E> (<$e>) on


interface <$1>

Additional
Information

<$1>: Interface index

Severity

Normal

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.2.20

Alarm 2810604
Specific Problem

2810604

Managed Object

Cajun

Description

Incorrect Community Name (authentication failure Trap)


enterprise:<$E> (<$e>)

Severity

Warning

Message Group
(Probable Cause)

Security

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.2.21

Alarm 2812315
Specific Problem

2812315

Managed Object

Cajun

Description

Module <$2> cascading up connection lost.

Additional
Information

<$2>: Module ID

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 2812316

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

307 of 492

6: Networking Agent Alarms

DRAFT

Cajun Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.2.22

Alarm 2812316
Specific Problem

2812316

Managed Object

Cajun

Description

Module <$2> cascading up connection lost was cleared.

Additional
Information

<$2>: Module ID

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.2.23

Alarm 2812317
Specific Problem

2812317

Managed Object

Cajun

Description

Module <$2> cascading down connection lost.

Additional
Information

<$2>: Module ID

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 2812318

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.2.24

Alarm 2812318
Specific Problem

2812318

Managed Object

Cajun

Description

Module <$2> cascading down connection lost was cleared.

Additional
Information

<$2>: Module ID

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

308 of 492

6: Networking Agent Alarms

DRAFT

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Cajun Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

309 of 492

6: Networking Agent Alarms

6.3

DRAFT

Others Alarms

Others Alarms
Search for the alarm you need by its Specific Problem (Alarm ID).

6.3.1

Alarm 2820001
Specific Problem

2820001

Managed Object

Others

Description

Reload trap. Reason: <whyReload>

Additional
Information

whyReload: The reason for the reload trap

Severity

Warning

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

No

System Impact

Depending on the location and function of the device in the


network, the reload may cause service degradation or a total
service outage.

Recommended
Corrective Action

This event occurs when a Cisco entity is reinitializing. A reload


trap signifies that the sending protocol entity is reinitializing
itself such that the agents configuration or the protocol entity
implementation may be altered. Verify the reason for the
device reload.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.3.2

Alarm 2820002
Specific Problem

2820002

Managed Object

Others

Description

TCP connection state changed. Session Type:


<tslineSesType>. Session State: <tcpConnState>.

Additional
Information

tslineSesType: The session type tcpConnState: The session


connection state

Severity

Warning

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

No

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

310 of 492

6: Networking Agent Alarms

DRAFT

Others Alarms

System Impact

There is no known system impact for this alarm.

Recommended
Corrective Action

This event occurs when a tty connection state changed. This


trap signifies that a TCP connection previously established
with the sending protocol entity state for the purposes of tty
session has been changed. Verify if an authorized user is
connected to the system.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.3.3

Alarm 2820003
Specific Problem

2820003

Managed Object

Others

Description

Temperature state changed. Reporting Object:


<ciscoEnvMonTemperatureStatusDescr>. State: Normal.

Additional
Information

ciscoEnvMonTemperatureStatusDescr: The object reporting


a temperature change

Severity

Normal

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

No

Threshold

< 75 C

System Impact

There is no known system impact for this alarm.

Recommended
Corrective Action

A caemTemperatureNotification is sent if the over temperature


condition that was detected in the managed system is cleared.
No corrective action is required for this alarm.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.3.4

Alarm 2820004
Specific Problem

2820004

Managed Object

Others

Description

Temperature state changed. Reporting Object:


<ciscoEnvMonTemperatureStatusDescr>. State:
<ciscoEnvMonTemperatureState>.

Additional
Information

ciscoEnvMonTemperatureStatusDescr: The object reporting


a temperature change.
ciscoEnvMonTemperatureState: The state of the object
reporting a temperature change

Severity

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

Critical

311 of 492

6: Networking Agent Alarms

DRAFT

Others Alarms

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

No

Threshold

> 75 C

System Impact

Depending on the location and function of the device in


the network, the change in temperature may cause service
degradation or a total service outage.

Recommended
Corrective Action

A caemTemperatureNotification is sent if the over temperature


condition is detected in the managed system. Check the
device fans and ambient temperature.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.3.5

Alarm 2820005
Specific Problem

2820005

Managed Object

Others

Description

Environmental temperature state changed. Reporting Object:


<ciscoEnvMonTemperatureStatusDescr>. Temperature:
<ciscoEnvMonTemperatureStatusValue> degrees Celsius.
State: Normal.

Additional
Information

ciscoEnvMonTemperatureStatusDescr: The object reporting a


temperature change ciscoEnvMonTemperatureStatusValue:
The reported temperature

Severity

Normal

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

No

Threshold

< 75 C

System Impact

There is no known system impact for this alarm.

Recommended
Corrective Action

A ciscoEnvMonTemperatureNotification is sent if the


temperature measured at a given testpoint is at the normal
range for the testpoint. No corrective action is required for
this alarm.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.3.6

Alarm 2820006

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

312 of 492

6: Networking Agent Alarms

DRAFT

Others Alarms

Specific Problem

2820006

Managed Object

Others

Description

Environmental temperature state changed. Reporting Object:


<ciscoEnvMonTemperatureStatusDescr>. Temperature:
<ciscoEnvMonTemperatureStatusValue> degrees Celsius.
State: <ciscoEnvMonTemperatureState>.

Additional
Information

ciscoEnvMonTemperatureStatusDescr: The object reporting a


temperature change ciscoEnvMonTemperatureStatusValue:
The reported temperature ciscoEnvMonTemperatureState:
The state of the object reporting a temperature change

Severity

Critical

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

Yes; by 2820005

Threshold

> 75 C

System Impact

Depending on the environmental conditions, service


degradation may occur.

Recommended
Corrective Action

A ciscoEnvMonTemperatureNotification is sent if the


temperature measured at a given testpoint is outside the
normal range for the testpoint (i.e. is at the warning, critical,
or shutdown stage). Since such a Notification is usually
generated before the shutdown state is reached, it can convey
more data and has a better chance of being sent than does
the ciscoEnvMonShutdownNotification. This notification is
deprecated in favor of ciscoEnvMonTempStatusChangeNotif.
Check the ambient temperature and that all the fans are
operating.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.3.7

Alarm 2820007
Specific Problem

2820007

Managed Object

Others

Description

Environmental temperature status changed. Reporting Object:


<ciscoEnvMonTemperatureStatusDescr>. Temperature:
<ciscoEnvMonTemperatureStatusValue> degrees Celsius.
Status: Normal.

Additional
Information

ciscoEnvMonTemperatureStatusDescr: The object reporting a


temperature change ciscoEnvMonTemperatureStatusValue:
The reported temperature

Severity

Normal

Message Group
(Probable Cause)

Network

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

313 of 492

6: Networking Agent Alarms

DRAFT

Others Alarms

Alarm Automatically
Cleared

No

Threshold

< 75 C

System Impact

There is no known system impact for this alarm.

Recommended
Corrective Action

A ciscoEnvMonTempStatusChangeNotif is sent if the state of


a device being monitored by ciscoEnvMonTemperatureState
changed to normal. No corrective action is required for this
alarm.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.3.8

Alarm 2820008
Specific Problem

2820008

Managed Object

Others

Description

Environmental temperature status changed. Reporting Object:


<ciscoEnvMonTemperatureStatusDescr>. Temperature:
<ciscoEnvMonTemperatureStatusValue> degrees Celsius.
Status: <ciscoEnvMonTemperatureState>.

Additional
Information

ciscoEnvMonTemperatureStatusDescr: The object reporting a


temperature change ciscoEnvMonTemperatureStatusValue:
The reported temperature ciscoEnvMonTemperatureState:
The state of the object reporting a temperature change

Severity

Critical

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

Yes; by 2820007

Threshold

> 75 C

System Impact

Depending on the environmental conditions, service


degradation or a total service outage may occur.

Recommended
Corrective Action

A ciscoEnvMonTempStatusChangeNotif is sent if there


is change in the state of a device being monitored by
ciscoEnvMonTemperatureState. Check the ambient
temperature and that all the fans are operating.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.3.9

Alarm 2820009
Specific Problem

2820009

Managed Object

Others

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

314 of 492

6: Networking Agent Alarms

DRAFT

Others Alarms

Description

Fan tray state changed. Reporting Object:


<ciscoEnvMonFanStatusDescr>. State: Normal.

Additional
Information

ciscoEnvMonFanStatusDescr: The fan reporting a status


change

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

There is no known system impact for this alarm.

Recommended
Corrective Action

A ciscoEnvMonFanNotification is sent if any one of the fans in


the fan array (where extant) returned to normal. No corrective
action is required for this alarm.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.3.10

Alarm 2820010
Specific Problem

2820010

Managed Object

Others

Description

Fan tray state changed. Reporting Object:


<ciscoEnvMonFanStatusDescr>. State:
<ciscoEnvMonFanState>.

Additional
Information

ciscoEnvMonFanStatusDescr: The fan reporting a status


change ciscoEnvMonFanState: The state of the fan reporting
a state change

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 2820009

System Impact

There is no known system impact for this alarm.

Recommended
Corrective Action

A ciscoEnvMonFanNotification is sent if any one of the fans


in the fan array (where extant) returned to normal. Check the
units fans and replace them if required.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.3.11

Alarm 2820011
Specific Problem

2820011

Managed Object

Others

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

315 of 492

6: Networking Agent Alarms

DRAFT

Others Alarms

Description

The Cisco configuration changed via the


<ccmHistoryEventCommandSource> source.

Additional
Information

ccmHistoryEventCommandSource: The configuration change


source

Severity

Warning

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

No

System Impact

Depending on the change, it may have no impact, cause


service degradation, or cause a total service outage.

Recommended
Corrective Action

Notification of a configuration management event as recorded


in ccmHistoryEventTable. Verify that the configuration change
was planned and performed by an authorized engineer.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.3.12

Alarm 2820012
Specific Problem

2820012

Managed Object

Others

Description

Syslog message received. Message Text: <clogHistMsgText>.

Additional
Information

clogHistMsgText: The log message

Severity

Normal

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

No

System Impact

Depends on the message generated by the device. This alarm


is always generated with another application ID alarm.

Recommended
Corrective Action

When a syslog message is generated by the device a


clogMessageGenerated notification is sent. The sending
of these notifications can be enabled/disabled via the
clogNotificationsEnabled object. No corrective action is
required for this alarm.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.3.13

Alarm 2820013

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

316 of 492

6: Networking Agent Alarms

DRAFT

Others Alarms

Specific Problem

2820013

Managed Object

Others

Description

HSRP state changed to: <cHsrpGrpStandbyState>.

Additional
Information

cHsrpGrpStandbyState: The HSRP state

Severity

Major

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

No

System Impact

Service degradation may occur during the state change.

Recommended
Corrective Action

A cHsrpStateChange notification is sent when a


cHsrpGrpStandbyState transitions to either active or standby
state, or leaves active or standby state. There is only one
notification issued when the state change is from standby to
active and vice versa. Verify the reason for the HSRP state
change and review the status of the standby device.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.3.14

Alarm 2820014
Specific Problem

2820014

Managed Object

Others

Description

High CPU utilization. Rising Threshold Value:


<cpmCPURisingThresholdValue>%. Current Value:
<cpmProcExtUtil5SecRev>%.

Additional
Information

cpmCPURisingThresholdValue: The value of the CPU


utilization threshold cpmProcExtUtil5SecRev: The actual CPU
usage

Severity

Major

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

Yes; by 2820015

Threshold

0.85

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

317 of 492

6: Networking Agent Alarms

DRAFT

Others Alarms

System Impact

Service degradation may occur.

Recommended
Corrective Action

A cpmCPURisingThreshold notification is sent


when configured rising CPU utilization threshold
(cpmCPURisingThresholdValue) is reached and CPU
utilization remained above the threshold for configured
interval (cpmCPURisingThresholdPeriod) and such a
notification is requested. The cpmProcExtUtil5SecRev and
cpmProcessTimeCreated objects can be repeated multiple
times in a notification indicating the top users of CPU. Use the
show proc command to investigate the reason for the high
CPU utilization.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.3.15

Alarm 2820015
Specific Problem

2820015

Managed Object

Others

Description

Low CPU utilization. Falling CPU Utilization Falling Threshold:


<cpmCPUFallingThresholdValue>%.

Additional
Information

cpmCPUFallingThresholdValue: The value of the CPU


utilization threshold

Severity

Normal

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

No

Threshold

15

System Impact

There is no known system impact for this alarm.

Recommended
Corrective Action

A cpmCPUFallingThresholdTrap is sent when the configured


falling threshold (cpmCPURisingThresholdValue) is reached
and CPU utilization remained under threshold for configured
interval (cpmCPUFallingThresholdPeriod) and such a
notification is requested. No corrective action is required for
this alarm.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.3.16

Alarm 2820016
Specific Problem

2820016

Managed Object

Others

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

318 of 492

6: Networking Agent Alarms

DRAFT

Others Alarms

Description

Power supply state changed. Reporting Object:


<entPhysicalName>, <entPhysicalDescr>. Operational Status:
On. Administrative Status: <cefcFRUPowerAdminStatus>.

Additional
Information

entPhysicalName: The name of the device entPhysicalDescr:


The description of the device cefcFRUPowerAdminStatus:
The administrative status of the device

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

There is no known system impact for this alarm.

Recommended
Corrective Action

The cefcFRUPowerStatusChange notification indicates that


the power status of a FRU has changed. The varbind for this
notification indicates the entPhysicalIndex of the FRU, and
the new operational-status of the FRU. No corrective action is
required for this alarm.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.3.17

Alarm 2820017
Specific Problem

2820017

Managed Object

Others

Description

Power supply state changed. Reporting Object:


<entPhysicalName>, <entPhysicalDescr>. Operational
Status: <cefcFRUPowerOperStatus>. Administrative Status:
<cefcFRUPowerAdminStatus>.

Additional
Information

entPhysicalName: The name of the device entPhysicalDescr:


The description of the device cefcFRUPowerOperStatus:
The power supply status cefcFRUPowerAdminStatus: The
administrative status of the device

Severity

Minor

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 2820016

System Impact

There is no known system impact for this alarm.

Recommended
Corrective Action

The cefcFRUPowerStatusChange notification indicates that


the power status of a FRU has changed. The varbind for this
notification indicates the entPhysicalIndex of the FRU, and the
new operational-status of the FRU. Review the power input
to the rack, power cables, circuit breakers, and the power
switch on the power supply.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

319 of 492

6: Networking Agent Alarms

DRAFT

Others Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.3.18

Alarm 2820018
Specific Problem

2820018

Managed Object

Others

Description

FRU inserted. Reporting Object: <entPhysicalDescr>,


<entPhysicalContainedIn>.

Additional
Information

entPhysicalDescr: The description of the device


entPhysicalContainedIn: The unit in which the FRU was
inserted

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

There is no known system impact for this alarm.

Recommended
Corrective Action

The cecfFRUInserted notification indicates that a FRU


was inserted. The varbind for this notification indicates
the entPhysicalIndex of the inserted FRU, and the
entPhysicalIndex of the FRUs container. Verify that the FRU
was installed by an authorized engineer.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.3.19

Alarm 2820019
Specific Problem

2820019

Managed Object

Others

Description

FRU removed. Reporting Object:<entPhysicalDescr>,


<entPhysicalContainedIn>.

Additional
Information

entPhysicalDescr: The description of the device


entPhysicalContainedIn: The unit in which the FRU was
inserted

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 2820018

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

320 of 492

6: Networking Agent Alarms

DRAFT

Others Alarms

System Impact

Normally, there is no system impact. If the FRU is a fan tray


and a working fan tray is not installed within five minutes,
pending the ambient temperature service degradation, and
potentially a total service outage, may occur.

Recommended
Corrective Action

The cefcFRURemoved notification indicates that a FRU


was removed. The varbind for this notification indicates
the entPhysicalIndex of the removed FRU, and the
entPhysicalIndex of the FRUs container. Verify the reason for
the FRU removal. If the removed FRU is a fan tray, ensure a
fan tray is installed in less than five minutes.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.3.20

Alarm 2820020
Specific Problem

2820020

Managed Object

Others

Description

Operational state of fan tray changed to: On.

Severity

Normal

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

No

System Impact

There is no known system impact for this alarm.

Recommended
Corrective Action

This notification is generated when the value of


cefcFanTrayOperStatus changed to normal. No corrective
action is required for this alarm.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.3.21

Alarm 2820021
Specific Problem

2820021

Managed Object

Others

Description

Operational state of fan tray changed to:


<cefcFanTrayOperStatus>.

Additional
Information

cefcFanTrayOperStatus: The fan tray status

Severity

Major

Message Group
(Probable Cause)

Network

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

321 of 492

6: Networking Agent Alarms

DRAFT

Others Alarms

Alarm Automatically
Cleared

Yes; by 2820020

System Impact

Normally, there is no system impact. If the FRU is a fan tray


and a working fan tray is not installed within five minutes,
pending the ambient temperature service degradation, and
potentially a total service outage, may occur.

Recommended
Corrective Action

This notification is generated when the value of


cefcFanTrayOperStatus changes. Verify the status of the fans
using the show env command. If required, replace the fan tray.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.3.22

Alarm 2820022
Specific Problem

2820022

Managed Object

Others

Description

Redundant power supply state changed. Reporting Object:


<ciscoEnvMonSupplyStatusDescr>. State: Normal.

Additional
Information

ciscoEnvMonSupplyStatusDescr: The object reporting the


change

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

There is no known system impact for this alarm.

Recommended
Corrective Action

ciscoEnvMonRedundantSupplyNotification is sent if the


redundant power supply (where extant) returned to normal.
No corrective action is required for this alarm.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.3.23

Alarm 2820023
Specific Problem

2820023

Managed Object

Others

Description

Redundant power supply state changed notification.


Reporting object: <ciscoEnvMonSupplyStatusDescr>. State:
<ciscoEnvMonSupplyState>.

Additional
Information

ciscoEnvMonSupplyStatusDescr: The object reporting the


change
ciscoEnvMonSupplyState: The state of the power supply

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

322 of 492

6: Networking Agent Alarms

DRAFT

Others Alarms

Severity

Minor

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 2820022

System Impact

There is no known system impact for this alarm.

Recommended
Corrective Action

A ciscoEnvMonRedundantSupplyNotification is sent if
the redundant power supply (where extant) fails. Since
such a notification is usually generated before the
shutdown state is reached, it can convey more data
and has a better chance of being sent than does the
ciscoEnvMonShutdownNotification. This notification is
deprecated in favor of ciscoEnvMonSuppStatusChangeNotif.
Review the power input to the rack, power cables, circuit
breakers, and the power switch on the power supply.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.3.24

Alarm 2820024
Specific Problem

2820024

Managed Object

Others

Description

Redundant power supply status changed. Reporting Object:


<ciscoEnvMonSupplyStatusDescr>. Status: Normal.

Additional
Information

ciscoEnvMonSupplyStatusDescr: The object reporting the


change

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

There is no known system impact for this alarm.

Recommended
Corrective Action

A ciscoEnvMonSupplyStatChangeNotif is sent if the state of a


device being monitored by ciscoEnvMonSupplyState changed
to normal. No corrective action is required for this alarm.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.3.25

Alarm 2820025
Specific Problem

2820025

Managed Object

Others

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

323 of 492

6: Networking Agent Alarms

DRAFT

Others Alarms

Description

Redundant power supply status changed. Reporting


Object: <ciscoEnvMonSupplyStatusDescr>. Status:
<ciscoEnvMonSupplyState>.

Additional
Information

ciscoEnvMonSupplyStatusDescr: The object reporting the


change ciscoEnvMonSupplyState: The state of the power
supply

Severity

Minor

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 2820024

System Impact

There is no known system impact for this alarm.

Recommended
Corrective Action

A ciscoEnvMonSupplyStatChangeNotif is sent if there


is change in the state of a device being monitored by
ciscoEnvMonSupplyState. Review the power input to the rack,
power cables, circuit breakers, the and power switch on the
power supply.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.3.26

Alarm 2820026
Specific Problem

2820026

Managed Object

Others

Description

Fan tray state changed. Reporting Object:


<ciscoEnvMonFanStatusDescr>. State: Normal.

Additional
Information

ciscoEnvMonFanStatusDescr: The fan tray reporting the


change

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

There is no known system impact for this alarm.

Recommended
Corrective Action

A ciscoEnvMonFanStatusChangeNotif is sent if the state of a


device being monitored by ciscoEnvMonFanState changed to
normal. No corrective action is required for this alarm.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.3.27

Alarm 2820027

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

324 of 492

6: Networking Agent Alarms

DRAFT

Others Alarms

Specific Problem

2820027

Managed Object

Others

Description

Fan tray state changed. Reporting Object:


<ciscoEnvMonFanStatusDescr>. State:
<ciscoEnvMonFanState>.

Additional
Information

ciscoEnvMonFanStatusDescr: The fan tray reporting the


change ciscoEnvMonFanState: The state of the fan tray

Severity

Critical

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 2820026

System Impact

Depending on the environmental conditions, service


degradation may occur.

Recommended
Corrective Action

A ciscoEnvMonFanStatusChangeNotif is sent if there


is change in the state of a device being monitored by
ciscoEnvMonFanState. Check the ambient temperature and
that all the fans are operating.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.3.28

Alarm 2820028
Specific Problem

2820028

Managed Object

Others

Description

Storm control event state changed to: <cpscStatus>.

Additional
Information

cpscStatus: The storm control event state

Severity

Critical

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

No

System Impact

Depending on the event, it may cause service degradation or


a total service outage.

Recommended
Corrective Action

This notification is sent by the implementation when a storm


event occurs on an interface with respect to a particular traffic
type. Check for any changes in the network topology and/or
abnormal traffic.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

325 of 492

6: Networking Agent Alarms

6.3.29

DRAFT

Others Alarms

Alarm 2820029
Specific Problem

2820029

Managed Object

Others

Description

Loop inconsistency state changed to: Destroyed. Actual


Spanning Tree Mode: <stpxSpanningTreeType>.

Additional
Information

stpxSpanningTreeType: The actually spanning tree mode

Severity

Normal

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

No

System Impact

There is no known system impact for this alarm.

Recommended
Corrective Action

A stpxLoopInconsistencyUpdate notification is sent by a


bridge when an instance of stpxLoopInconsistencyState
is destroyed. That is, when such a loop-inconsistency
disappears. The object value of stpxSpanningTreeType
indicates which Spanning Tree protocol is running when
an instance of stpxLoopInconsistencyState is created or
destroyed. There is no corrective action for this alarm.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.3.30

Alarm 2820030
Specific Problem

2820030

Managed Object

Others

Description

Loop inconsistency state changed to: Created. Actual


Spanning Tree Mode: <stpxSpanningTreeType>.

Additional
Information

stpxSpanningTreeType: The actually spanning tree mode

Severity

Major

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

Yes; by 2820029

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

326 of 492

6: Networking Agent Alarms

DRAFT

Others Alarms

System Impact

Depending on the event, it may cause service degradation or


a total service outage.

Recommended
Corrective Action

A stpxLoopInconsistencyUpdate notification is sent by a


bridge when an instance of stpxLoopInconsistencyState is
created. That is, when a loop-inconsistency is discovered
in the VLANs or instances Spanning Tree for a particular
port. The object value of stpxSpanningTreeType indicates
which Spanning Tree protocol is running when an instance of
stpxLoopInconsistencyState is created or destroyed. Check
for any changes in the network topology.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.3.31

Alarm 2820031
Specific Problem

2820031

Managed Object

Others

Description

Cold start. Last Reset Reason: <LastResetReason>.

Additional
Information

LastResetReason: The reason for the last reset

Severity

Warning

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

No

System Impact

This alarm is sent after the unit is powered up. When the unit
is not operational, service degradation or a complete service
outage may occur.

Recommended
Corrective Action

A coldStart trap signifies that this entity, acting in an agent


role, is reinitializing itself and that its configuration may have
been altered. Verify that the unit power up was performed
intentionally.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.3.32

Alarm 2820032
Specific Problem

2820032

Managed Object

Others

Description

Link down on interface: <ifDescr>.

Additional
Information

ifDescr: The interface name

Severity

Major

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

327 of 492

6: Networking Agent Alarms

DRAFT

Others Alarms

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

Yes; by 2820033

System Impact

Depending on the functionality of the device connected to


that port, it may cause service degradation or a total service
outage.

Recommended
Corrective Action

A linkDown trap signifies that the sending protocol entity


recognizes a failure in one of the communication links
represented in the agents configuration. Check the cable
and/or link partner.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.3.33

Alarm 2820033
Specific Problem

2820033

Managed Object

Others

Description

Link up on interface: <ifDescr>.

Additional
Information

ifDescr: The interface name

Severity

Normal

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

No

System Impact

There is no known system impact for this alarm.

Recommended
Corrective Action

A linkUp trap signifies that the sending protocol entity


recognizes that one of the communication links represented in
the agents configuration has come up. There is no corrective
action for this alarm.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

6.3.34

Alarm 2820034
Specific Problem

2820034

Managed Object

Others

Description

Incorrect community name (authenticationFailure Trap).


Potential Attacker IP: <authAddr>.

Additional
Information

authAddr: The IP address

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

328 of 492

6: Networking Agent Alarms

DRAFT

Others Alarms

Severity

Minor

Message Group
(Probable Cause)

Security

Alarm Automatically
Cleared

No

System Impact

Login failure.

Recommended
Corrective Action

This event occurs when the Cisco agent detects an


authentication failure has occurred. An authentication
failure trap signifies that the sending protocol entity is
the addressee of a protocol message that is not properly
authenticated. Check the potential intruder - unauthorized
access attempt. Report security administration change (user
creation/deletion/edit, password change, encryption level
change).

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

329 of 492

DRAFT

Application Agent Alarms

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

7: Application Agent Alarms

7.1

DRAFT

Application Agent Alarms Overview

Application Agent Alarms Overview


Application Agent alarms monitor the Applications in the SMSC System and
generate 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

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

331 of 492

7: Application Agent Alarms

7.2

DRAFT

CCS_CC Alarms

CCS_CC Alarms
Search for the alarm you need by its Specific Problem (Alarm ID).

7.2.1

Alarm 1465330
Specific Problem

1465330

Managed Object

CCS_CC

Description

Peer application is not accessible via SLAN.

Severity

Minor

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

Yes; by 1465330

Threshold

After 1 occurrence

System Impact

When both events (5330 & 5331) occur, system will


switchover.

Recommended
Corrective Action

Verify COM ports of first unit are cross connected by cable to


the COM ports of second unit.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.2.2

Alarm 1465331
Specific Problem

1465331

Managed Object

CCS_CC

Description

Peer application is not accessible via UDP LAN.

Severity

Major

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

Yes; by 1465331

Threshold

After 2 occurrences

System Impact

When both events (5330 & 5331) occur, system will


switchover.

Recommended
Corrective Action

Verify LAN cable of peer unit is connected properly

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

332 of 492

7: Application Agent Alarms

7.2.3

DRAFT

CCS_CC Alarms

Alarm 1465350
Specific Problem

1465350

Managed Object

CCS_CC

Description

Peak capacity reached; possible message lost.

Severity

Minor

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

Yes; by 1465350

Threshold

After 1 occurrence

System Impact

All new incoming calls are released until expiration of time


interval

Recommended
Corrective Action

Check the BHCA in the system

If it is higher than expected, verify the load at the switch.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.2.4

Alarm 1467902
Specific Problem

1467902

Managed Object

CCS_CC

Description

Capacity has reached <$A> percent.

Severity

Critical
Major
Minor
Warning

Message Group
(Probable Cause)

Capacity

Alarm Automatically
Cleared

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

Recommended
Corrective Action

Check the BHCA in the system

If it is higher than expected, verify the load at the switch

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

333 of 492

7: Application Agent Alarms

DRAFT

CCS_CC Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.2.5

Alarm 1469110
Specific Problem

1469110

Managed Object

CCS_CC

Description

CCS <ce name> out of service.

Severity

Major

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

Yes; by 1469110

Threshold

FAIL

System Impact

Switch over

Recommended
Corrective Action

Contact Comverse customer support for problem analysis.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

334 of 492

7: Application Agent Alarms

7.3

DRAFT

GenericDatabase Alarms

GenericDatabase Alarms
Search for the alarm you need by its Specific Problem (Alarm ID).

7.3.1

Alarm 2113062
Specific Problem

2113062

Managed Object

OnGuard

Description

Generic Database Message - Normal

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.3.2

Alarm 2113063
Specific Problem

2113063

Managed Object

OnGuard

Description

Generic Database Message - Warning

Severity

Warning

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.3.3

Alarm 2113064
Specific Problem

2113064

Managed Object

OnGuard

Description

Generic Database Message - Minor

Severity

Minor

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.3.4

Alarm 2113065

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

335 of 492

7: Application Agent Alarms

DRAFT

Specific Problem

2113065

Managed Object

OnGuard

Description

Generic Database Message - Major

Severity

Major

Alarm Automatically
Cleared

No

GenericDatabase Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.3.5

Alarm 2113066
Specific Problem

2113066

Managed Object

OnGuard

Description

Generic Database Message - Critical

Severity

Critical

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

336 of 492

7: Application Agent Alarms

7.4

DRAFT

OMNI Alarms

OMNI Alarms
Search for the alarm you need by its Specific Problem (Alarm ID).

7.4.1

Alarm 1418001
Specific Problem

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/oad
sharing/non load sharing

Severity

Major

Message Group
(Probable Cause)

Communication/Network

Alarm Automatically
Cleared

Yes; by 1418001

Threshold

FAIL

System Impact

No service for specific routeset

Recommended
Corrective Action

Contact Comverse customer support for problem analysis.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.4.2

Alarm 1418201
Specific Problem

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/remotely
inhibited/ locally inhibited

Severity

Major

Message Group
(Probable Cause)

Communication/Network

Alarm Automatically
Cleared

Yes; by 1418201

Threshold

FAIL

System Impact

All the traffic is rerouted to other link/s in routeset if they exist.

Recommended
Corrective Action

Contact Comverse customer support for problem analysis.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

337 of 492

7: Application Agent Alarms

DRAFT

OMNI Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.4.3

Alarm 2113052
Specific Problem

2113052

Managed Object

OMNI

Description

Generic Application Message - Normal

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.4.4

Alarm 2113053
Specific Problem

2113053

Managed Object

OMNI

Description

Generic Application Message - Warning

Severity

Warning

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.4.5

Alarm 2113054
Specific Problem

2113054

Managed Object

OMNI

Description

Generic Application Message - Minor

Severity

Minor

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.4.6

Alarm 2113055
Specific Problem

2113055

Managed Object

OMNI

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

338 of 492

7: Application Agent Alarms

DRAFT

Description

Generic Application Message - Major

Severity

Major

Alarm Automatically
Cleared

No

OMNI Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.4.7

Alarm 2113056
Specific Problem

2113056

Managed Object

OMNI

Description

Generic Application Message - Critical

Severity

Critical

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

339 of 492

7: Application Agent Alarms

7.5

DRAFT

Oracle Database Alarms (OnGuard Agent)

Oracle Database Alarms (OnGuard Agent)


Search for the alarm you need by its Specific Problem (Alarm ID).

7.5.1

Alarm 2110001
Specific Problem

2110001

Managed Object

OnGuard

Description

The <database> database is down.

Additional
Information

<database>: Database name

Severity

Critical

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110002

If you do not have an Oracle database, this alarm is not


relevant.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.2

Alarm 2110002
Specific Problem

2110002

Managed Object

OnGuard

Description

The <database> database is up.

Additional
Information

<database>: Database name

Severity

Normal

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

No

If you do not have an Oracle database, this alarm is not


relevant.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.3

Alarm 2110003
Specific Problem

2110003

Managed Object

OnGuard

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

340 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

Description

The <database> database is pending startup or shutdown.

Additional
Information

<database>: Database name

Severity

Warning

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110002

If you do not have an Oracle database, this alarm is not


relevant.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.4

Alarm 2110004
Specific Problem

2110004

Managed Object

OnGuard

Description

A database status event timed out. The <database> database


is not responding.

Additional
Information

<database>: Database name

Severity

Warning

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110002

If you do not have an Oracle database, this alarm is not


relevant.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.5

Alarm 2110005
Specific Problem

2110005

Managed Object

OnGuard

Description

A database status event for the <database> database failed.

Additional
Information

<database>: Database name

Severity

Warning

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

If you do not have an Oracle database, this alarm is not


relevant.

341 of 492

7: Application Agent Alarms

DRAFT

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110002

Oracle Database Alarms (OnGuard Agent)

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.6

Alarm 2110006
Specific Problem

2110006

Managed Object

OnGuard

Description

The <listener> listener is up.

Additional
Information

<listener>: Listener name

Severity

Normal

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

No

If you do not have an Oracle database, this alarm is not


relevant.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.7

Alarm 2110007
Specific Problem

2110007

Managed Object

OnGuard

Description

The <listener> listener is down.

Additional
Information

<listener>: Listener name

Severity

Critical

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110006

If you do not have an Oracle database, this alarm is not


relevant.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.8

Alarm 2110008

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

342 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

Specific Problem

2110008

Managed Object

OnGuard

Description

The <listener> listener is not responding.

Additional
Information

<listener>: Listener name

Severity

Warning

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110006

If you do not have an Oracle database, this alarm is not


relevant.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.9

Alarm 2110009
Specific Problem

2110009

Managed Object

OnGuard

Description

A listener status event for the <listener> listener failed.

Additional
Information

<listener>: Listener name

Severity

Warning

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110006

If you do not have an Oracle database, this alarm is not


relevant.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.10

Alarm 2110010
Specific Problem

2110010

Managed Object

OnGuard

Description

The following error message was found in the alert log:


<specificError>.

Additional
Information

<specificError>: Detailed error text

Severity

Major

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

If you do not have an Oracle database, this alarm is not


relevant.

343 of 492

7: Application Agent Alarms

DRAFT

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

No

Oracle Database Alarms (OnGuard Agent)

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.11

Alarm 2110011
Specific Problem

2110011

Managed Object

OnGuard

Description

The following warning message was found in the alert log:


<specificError>.

Additional
Information

<specificError>: Detailed error text

Severity

Warning

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

No

If you do not have an Oracle database, this alarm is not


relevant.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.12

Alarm 2110012
Specific Problem

2110012

Managed Object

OnGuard

Description

The following error message was found in the listener log:


<specificError>.

Additional
Information

<specificError>: Detailed error text

Severity

Major

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

No

If you do not have an Oracle database, this alarm is not


relevant.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

344 of 492

7: Application Agent Alarms

7.5.13

DRAFT

Oracle Database Alarms (OnGuard Agent)

Alarm 2110013
Specific Problem

2110013

Managed Object

OnGuard

Description

The following warning message was found in the listener log:


<specificError>.

Additional
Information

<specificError>: Detailed error text

Severity

Warning

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

No

If you do not have an Oracle database, this alarm is not


relevant.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.14

Alarm 2110014
Specific Problem

2110014

Managed Object

OnGuard

Description

There are no locks in the <database> database.

Additional
Information

<database>: Database name

Severity

Normal

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

No

If you do not have an Oracle database, this alarm is not


relevant.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.15

Alarm 2110015
Specific Problem

2110015

Managed Object

OnGuard

Description

There are blocking locks in the <database> database.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

345 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

Additional
Information

<database>: Database name

Severity

Warning

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110014

If you do not have an Oracle database, this alarm is not


relevant.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.16

Alarm 2110016
Specific Problem

2110016

Managed Object

OnGuard

Description

A blocking locks event timed out. The <database> database


is not responding.

Additional
Information

<database>: Database name

Severity

Warning

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110014

If you do not have an Oracle database, this alarm is not


relevant.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.17

Alarm 2110017
Specific Problem

2110017

Managed Object

OnGuard

Description

A blocking locks event for the <database> database failed.

Additional
Information

<database>: Database name

Severity

Warning

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110014

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

If you do not have an Oracle database, this alarm is not


relevant.

346 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.18

Alarm 2110018
Specific Problem

2110018

Managed Object

OnGuard

Description

<usage value>% of the <tablespace> tablespace in the


<database> database is in use.

Additional
Information

<usage value>: Percentage used


<tablespace>: Tablespace name
<database>: Database name

If you do not have an Oracle database, this alarm is not


relevant.
Severity

Normal

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

No

Threshold

189%

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.19

Alarm 2110019
Specific Problem

2110019

Managed Object

OnGuard

Description

<usage value>% of the <tablespace> tablespace in the


<database> database is in use.

Additional
Information

<usage value>: Percentage used


<tablespace>: Tablespace name
<database>: Database name

If you do not have an Oracle database, this alarm is not


relevant.
Severity

Warning

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110018

Threshold

9095%

For a detailed description of these rows, see Alarm Fields Description, Page 7.
SMSC 4.2 Alarm Reference Manual
P/N 10-000-1050 Issue 1 Rev. 0.1

347 of 492

7: Application Agent Alarms

7.5.20

DRAFT

Oracle Database Alarms (OnGuard Agent)

Alarm 2110020
Specific Problem

2110020

Managed Object

OnGuard

Description

<usage value>% of the <tablespace> tablespace in the


<database> database is in use.

Additional
Information

<usage value>: Percentage used


<tablespace>: Tablespace name
<database>: Database name

If you do not have an Oracle database, this alarm is not


relevant.
Severity

Major

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110018

Threshold

96100%

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.21

Alarm 2110021
Specific Problem

2110021

Managed Object

OnGuard

Description

A tablespace free space event timed out. The <database>


database is not responding.

Additional
Information

<database>: Database name

Severity

Warning

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110018

If you do not have an Oracle database, this alarm is not


relevant.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.22

Alarm 2110022

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

348 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

Specific Problem

2110022

Managed Object

OnGuard

Description

A tablespace free space event for the <database> database


failed.

Additional
Information

<database>: Database name

Severity

Warning

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110018

If you do not have an Oracle database, this alarm is not


relevant.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.23

Alarm 2110023
Specific Problem

2110023

Managed Object

OnGuard

Description

There are no invalid objects in the <database> database.

Additional
Information

<database>: Database name

Severity

Normal

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

No

If you do not have an Oracle database, this alarm is not


relevant.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.24

Alarm 2110024
Specific Problem

2110024

Managed Object

OnGuard

Description

The status of the objects <objects> in the <database>


database is invalid.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

349 of 492

7: Application Agent Alarms

Additional
Information

DRAFT

Oracle Database Alarms (OnGuard Agent)

<objects>: List of objects


<database>: Database name

If you do not have an Oracle database, this alarm is not


relevant.
Severity

Warning

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110023

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.25

Alarm 2110025
Specific Problem

2110025

Managed Object

OnGuard

Description

The status of the objects <objects> in the <database>


database is invalid.

Additional
Information

<objects>: List of objects


<database>: Database name

If you do not have an Oracle database, this alarm is not


relevant.
Severity

Major

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110023

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.26

Alarm 2110026
Specific Problem

2110026

Managed Object

OnGuard

Description

An invalid objects event timed out. The <database> database


is not responding.

Additional
Information

<database>: Database name

Severity

Warning

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

If you do not have an Oracle database, this alarm is not


relevant.

350 of 492

7: Application Agent Alarms

DRAFT

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110023

Oracle Database Alarms (OnGuard Agent)

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.27

Alarm 2110027
Specific Problem

2110027

Managed Object

OnGuard

Description

An invalid objects event for the <database> database failed.

Additional
Information

<database>: Database name

Severity

Warning

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110023

If you do not have an Oracle database, this alarm is not


relevant.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.28

Alarm 2110028
Specific Problem

2110028

Managed Object

OnGuard

Description

<usage value>% of the <archive> archive in the <database>


database is in use.

Additional
Information

<usage value>: Percentage used


<archive>: Location of archive files
<database>: Database name

If you do not have an Oracle database, this alarm is not


relevant.
Severity

Normal

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

No

Threshold

184%

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

351 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.29

Alarm 2110029
Specific Problem

2110029

Managed Object

OnGuard

Description

<usage value>% of the <archive> archive in the <database>


database is in use.

Additional
Information

<usage value>: Percentage used


<archive>: Location of archive files
<database>: Database name

If you do not have an Oracle database, this alarm is not


relevant.
Severity

Warning

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110028

Threshold

8595%

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.30

Alarm 2110030
Specific Problem

2110030

Managed Object

OnGuard

Description

<usage value>% of the <archive> archive in the <database>


database is in use.

Additional
Information

<usage value>: Percentage used


<archive>: Location of archive files
<database>: Database name

If you do not have an Oracle database, this alarm is not


relevant.
Severity

Critical

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110028

Threshold

96100%

For a detailed description of these rows, see Alarm Fields Description, Page 7.
SMSC 4.2 Alarm Reference Manual
P/N 10-000-1050 Issue 1 Rev. 0.1

352 of 492

7: Application Agent Alarms

7.5.31

DRAFT

Oracle Database Alarms (OnGuard Agent)

Alarm 2110031
Specific Problem

2110031

Managed Object

OnGuard

Description

An archive dump destination event timed out. The <database>


database is not responding.

Additional
Information

<database>: Database name

Severity

Warning

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110028

If you do not have an Oracle database, this alarm is not


relevant.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.32

Alarm 2110032
Specific Problem

2110032

Managed Object

OnGuard

Description

An archive dump dest event for the <database> database


failed.

Additional
Information

<database>: Database name

Severity

Warning

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110028

If you do not have an Oracle database, this alarm is not


relevant.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.33

Alarm 2110033
Specific Problem

2110033

Managed Object

OnGuard

Description

The database backup was completed successfully.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

353 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

Additional
Information

If you do not have an Oracle database, this alarm is not


relevant.

Severity

Normal

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.34

Alarm 2110034
Specific Problem

2110034

Managed Object

OnGuard

Description

Problems were detected in the daily backup. Refer to


<logFilePath> for more details.

Additional
Information

<logFilePath>: Log file path

Severity

Major

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110033

If you do not have an Oracle database, this alarm is not


relevant.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.35

Alarm 2110035
Specific Problem

2110035

Managed Object

OnGuard

Description

There are no broken or failed jobs in the <database>


database.

Severity

Normal

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

354 of 492

7: Application Agent Alarms

7.5.36

DRAFT

Oracle Database Alarms (OnGuard Agent)

Alarm 2110036
Specific Problem

2110036

Managed Object

OnGuard

Description

The <database> database contains the following broken or


failed jobs: <JobInfo>.

Additional
Information

<database>: Database name


<JobInfo>: Job information list

If you do not have an Oracle database, this alarm is not


relevant.
Severity

Warning

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110035

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.37

Alarm 2110037
Specific Problem

2110037

Managed Object

OnGuard

Description

The <database> database contains the following broken or


failed jobs: <JobInfo>.

Additional
Information

<database>: Database name


<JobInfo>: Job information list

If you do not have an Oracle database, this alarm is not


relevant.
Severity

Major

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110035

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.38

Alarm 2110038
Specific Problem

2110038

Managed Object

OnGuard

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

355 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

Description

Job number <jobno> failed to rerun.

Additional
Information

<jobno>: Job number

Severity

Major

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110039

If you do not have an Oracle database, this alarm is not


relevant.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.39

Alarm 2110039
Specific Problem

2110039

Managed Object

OnGuard

Description

Job number <jobno> has successfully been rerun.

Additional
Information

<jobno>: Job number

Severity

Normal

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

No

If you do not have an Oracle database, this alarm is not


relevant.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.40

Alarm 2110040
Specific Problem

2110040

Managed Object

OnGuard

Description

A failed or broken jobs event for the <database> database


timed out.

Additional
Information

<database>: Database name

Severity

Warning

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

If you do not have an Oracle database, this alarm is not


relevant.

356 of 492

7: Application Agent Alarms

DRAFT

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110035

Oracle Database Alarms (OnGuard Agent)

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.41

Alarm 2110041
Specific Problem

2110041

Managed Object

OnGuard

Description

A failed or broken jobs event for the <database> database


failed.

Additional
Information

<database>: Database name

Severity

Warning

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110035

If you do not have an Oracle database, this alarm is not


relevant.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.42

Alarm 2110042
Specific Problem

2110042

Managed Object

OnGuard

Description

The <database> database has <NumberOfSessions>


connected sessions out of a maximum of <maxSessions>
(<usage value>% used).

Additional
Information

<database>: Database name

<usage value>: Percentage used

<NumberOfSessions>: Number of concurrent sessions


<maxSessions>: Maximum number of sessions allowed
in the database

If you do not have an Oracle database, this alarm is not


relevant.
Severity

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

Normal

357 of 492

7: Application Agent Alarms

DRAFT

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

No

Oracle Database Alarms (OnGuard Agent)

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.43

Alarm 2110043
Specific Problem

2110043

Managed Object

OnGuard

Description

The <database> database has <NumberOfSessions>


connected sessions out of a maximum of <maxSessions>
(<usage value>% used).

Additional
Information

<database>: Database name

<usage value>: Percentage used

<NumberOfSessions>: Number of concurrent sessions


<maxSessions>: Maximum number of sessions allowed
in the database

If you do not have an Oracle database, this alarm is not


relevant.
Severity

Warning

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110042

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.44

Alarm 2110044
Specific Problem

2110044

Managed Object

OnGuard

Description

The <database> database has <NumberOfSessions>


connected sessions out of a maximum of <maxSessions>
(<usage value>% used).

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

358 of 492

7: Application Agent Alarms

Additional
Information

DRAFT

Oracle Database Alarms (OnGuard Agent)

<database>: Database name

<usage value>: Percentage used

<NumberOfSessions>: Number of concurrent sessions


<maxSessions>: Maximum number of sessions allowed
in the database

If you do not have an Oracle database, this alarm is not


relevant.
Severity

Major

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110042

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.45

Alarm 2110045
Specific Problem

2110045

Managed Object

OnGuard

Description

A concurrent sessions event for the <database> database


timed out.

Additional
Information

<database>: Database name

Severity

Warning

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110042

If you do not have an Oracle database, this alarm is not


relevant.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.46

Alarm 2110046
Specific Problem

2110046

Managed Object

OnGuard

Description

A concurrent sessions event for the <database> database


failed.

Additional
Information

<database>: Database name

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

If you do not have an Oracle database, this alarm is not


relevant.

359 of 492

7: Application Agent Alarms

DRAFT

Severity

Warning

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110042

Oracle Database Alarms (OnGuard Agent)

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.47

Alarm 2110047
Specific Problem

2110047

Managed Object

OnGuard

Description

<usage value>% of the maximum allowed shared servers


is in use.

Additional
Information

<usage value>: Percentage used

Severity

Normal

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

No

If you do not have an Oracle database, this alarm is not


relevant.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.48

Alarm 2110048
Specific Problem

2110048

Managed Object

OnGuard

Description

<usage value>% of the maximum allowed shared servers


is in use.

Additional
Information

<usage value>: Percentage used.

Severity

Warning

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110047

If you do not have an Oracle database, this alarm is not


relevant.

For a detailed description of these rows, see Alarm Fields Description, Page 7.
SMSC 4.2 Alarm Reference Manual
P/N 10-000-1050 Issue 1 Rev. 0.1

360 of 492

7: Application Agent Alarms

7.5.49

DRAFT

Oracle Database Alarms (OnGuard Agent)

Alarm 2110049
Specific Problem

2110049

Managed Object

OnGuard

Description

<usage value>% of the maximum allowed shared servers


is in use.

Additional
Information

<usage value>: Percentage used

Severity

Major

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110047

If you do not have an Oracle database, this alarm is not


relevant.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.50

Alarm 2110050
Specific Problem

2110050

Managed Object

OnGuard

Description

There are <NumberOfServers> dedicated server connections.


The number of connections is normal.

Additional
Information

<NumberOfServers>: Number of dedicated servers in the


database.
If you do not have an Oracle database, this alarm is not
relevant.

Severity

Normal

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.51

Alarm 2110051
Specific Problem

2110051

Managed Object

OnGuard

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

361 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

Description

There are <NumberOfServers> dedicated server connections.


The threshold has been exceeded.

Additional
Information

<NumberOfServers>: Number of dedicated servers in the


database
If you do not have an Oracle database, this alarm is not
relevant.

Severity

Warning

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110050

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.52

Alarm 2110052
Specific Problem

2110052

Managed Object

OnGuard

Description

There are <NumberOfServers> dedicated server connections.


The threshold has been exceeded.

Additional
Information

<NumberOfServers>: Number of dedicated servers in the


database.
If you do not have an Oracle database, this alarm is not
relevant.

Severity

Major

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110050

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.53

Alarm 2110053
Specific Problem

2110053

Managed Object

OnGuard

Description

<usage value>% of the large pool is in use.

Additional
Information

<usage value>: Percentage used.

Severity

Normal

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

If you do not have an Oracle database, this alarm is not


relevant.

362 of 492

7: Application Agent Alarms

DRAFT

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

No

Oracle Database Alarms (OnGuard Agent)

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.54

Alarm 2110054
Specific Problem

2110054

Managed Object

OnGuard

Description

<usage value>% of the large pool is in use.

Additional
Information

<usage value>: Percentage used

Severity

Warning

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110053

If you do not have an Oracle database, this alarm is not


relevant.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.55

Alarm 2110055
Specific Problem

2110055

Managed Object

OnGuard

Description

<usage value>% of the large pool is in use.

Additional
Information

<usage value>: Percentage used

Severity

Critical

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110053

If you do not have an Oracle database, this alarm is not


relevant.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.56

Alarm 2110056

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

363 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

Specific Problem

2110056

Managed Object

OnGuard

Description

The activity log procedure was completed successfully.

Additional
Information

If you do not have an Oracle database, this alarm is not


relevant.

Severity

Normal

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.57

Alarm 2110057
Specific Problem

2110057

Managed Object

OnGuard

Description

The activity log procedure failed.

Additional
Information

If you do not have an Oracle database, this alarm is not


relevant.

Severity

Critical

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110056

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.58

Alarm 2110058
Specific Problem

2110058

Managed Object

OnGuard

Description

<usage value>% of the activity log directory is in use.

Additional
Information

<usage value>: Percentage used

Severity

Normal

Message Group
(Probable Cause)

Database

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

If you do not have an Oracle database, this alarm is not


relevant.

364 of 492

7: Application Agent Alarms

DRAFT

Alarm Automatically
Cleared

No

Threshold

179%

Oracle Database Alarms (OnGuard Agent)

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.59

Alarm 2110059
Specific Problem

2110059

Managed Object

OnGuard

Description

<usage value>% of the activity log directory is in use.

Additional
Information

<usage value>: Percentage used

Severity

Warning

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110058

Threshold

8089%

If you do not have an Oracle database, this alarm is not


relevant.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.60

Alarm 2110060
Specific Problem

2110060

Managed Object

OnGuard

Description

<usage value>% of the activity log directory is in use.

Additional
Information

<usage value>: Percentage used

Severity

Critical

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2110058

Threshold

90100%

If you do not have an Oracle database, this alarm is not


relevant.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

365 of 492

7: Application Agent Alarms

7.5.61

DRAFT

Oracle Database Alarms (OnGuard Agent)

Alarm 2111000
Specific Problem

2111000

Managed Object

OnGuard

Description

Warning: There is an internal database problem. Please


check the OnGuard console for further details.

Additional
Information

If you do not have an Oracle database, this alarm is not


relevant.

Severity

Warning

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2111002, 2111003

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.62

Alarm 2111001
Specific Problem

2111001

Managed Object

OnGuard

Description

Error: There is an internal database problem. Please check


the OnGuard console for further details.

Additional
Information

If you do not have an Oracle database, this alarm is not


relevant.

Severity

Major

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 2111002

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.63

Alarm 2111002
Specific Problem

2111002

Managed Object

OnGuard

Description

The database status is Normal.

Additional
Information

If you do not have an Oracle database, this alarm is not


relevant.

Severity

Normal

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

366 of 492

7: Application Agent Alarms

DRAFT

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

No

Oracle Database Alarms (OnGuard Agent)

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.64

Alarm 2111003
Specific Problem

2111003

Managed Object

OnGuard

Description

The database status is Warning.

Additional
Information

If you do not have an Oracle database, this alarm is not


relevant.

Severity

Warning

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.65

Alarm 2111004
Specific Problem

2111004

Managed Object

OnGuard

Description

The database status is Error.

Additional
Information

If you do not have an Oracle database, this alarm is not


relevant.

Severity

Major

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.66

Alarm 2111005

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

367 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

Specific Problem

2111005

Managed Object

OnGuard

Description

Warning: There is an internal application problem. Please


check the OnGuard console for further details.

Additional
Information

Generic message. The alarm should be ignored.

Severity

Warning

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

Yes; by 2111007

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.67

Alarm 2111006
Specific Problem

2111006

Managed Object

OnGuard

Description

Error: There is an internal application problem. Please check


the OnGuard console for further details.

Additional
Information

Generic message. The alarm should be ignored.

Severity

Major

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

Yes; by 2111007, 2111008

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.68

Alarm 2112001
Specific Problem

2112001

Managed Object

OnGuard

Description

The CPU usage is <CPU value>%.

Additional
Information

<CPU value>: Percentage of the CPU in use

Severity

Normal

Message Group
(Probable Cause)

Operating System

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

368 of 492

7: Application Agent Alarms

DRAFT

Alarm Automatically
Cleared

No

Threshold

069%

Oracle Database Alarms (OnGuard Agent)

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.69

Alarm 2112002
Specific Problem

2112002

Managed Object

OnGuard

Description

The CPU usage is <CPU value>%. There is a problem with


the last <events number> events.

Additional
Information

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112001

Threshold

7089%

System Impact

Lower system performance.

Recommended
Corrective Action

Kill the process which consumes the CPU provided you do


not harm your system.

<CPU value>: Percentage of the CPU in use


<events number>: Number of consequent events with
this problem

Identify why the CPU consumption is high.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.70

Alarm 2112003
Specific Problem

2112003

Managed Object

OnGuard

Description

The CPU usage is <CPU value>%. There is a problem with


the last <events number> events.

Additional
Information

Severity

Major

Message Group
(Probable Cause)

Operating System

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

<CPU value>: Percentage of the CPU in use


<events number>: Number of consequent events with
this problem

369 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

Alarm Automatically
Cleared

Yes; by 2112001

Threshold

90100%

System Impact

Lower system performance.

Recommended
Corrective Action

Kill the process which consumes the CPU provided you do


not harm your system.
Identify why the CPU consumption is high.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.71

Alarm 2112004
Specific Problem

2112004

Managed Object

OnGuard

Description

A CPU usage event timed out.

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112001

System Impact

CPU usage is not checked.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.72

Alarm 2112005
Specific Problem

2112005

Managed Object

OnGuard

Description

A CPU usage event failed.

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112001

System Impact

CPU usage is not checked.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.
SMSC 4.2 Alarm Reference Manual
P/N 10-000-1050 Issue 1 Rev. 0.1

370 of 492

7: Application Agent Alarms

7.5.73

DRAFT

Oracle Database Alarms (OnGuard Agent)

Alarm 2112006
Specific Problem

2112006

Managed Object

OnGuard

Description

<usage value>% of the <file system> file system is in use


(<used MB> of <total MB> MB).

Additional
Information

<usage value>: Percentage used

<total MB>: Total number of MB in the file system

<file system>: File system name


<used MB>: Number of MB in the file system that are
in use

Severity

Normal

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

No

Threshold

089%

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.74

Alarm 2112007
Specific Problem

2112007

Managed Object

OnGuard

Description

<usage value>% of the <file system> file system is in use


(<used MB> of <total MB> MB).

Additional
Information

<usage value>: Percentage used

<total MB>: Total number of MB in the file system

<file system>: File system name


<used MB>: Number of MB in the file system that are
in use

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112006

Threshold

9094%

System Impact

Some applications may fail.

Recommended
Corrective Action

Delete unnecessary files from the file system. If none


available, the file system capacity should be enlarged.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

371 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.75

Alarm 2112008
Specific Problem

2112008

Managed Object

OnGuard

Description

<usage value>% of the <file system> file system is in use


(<used MB> of <total MB> MB).

Additional
Information

<usage value>: Percentage used

<total MB>: Total number of MB in the file system

<file system>: File system name


<used MB>: Number of MB in the file system that are
in use

Severity

Major

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112006

Threshold

95100%

System Impact

Some applications may fail.

Recommended
Corrective Action

Delete unnecessary files from the file system. If none


available, the file system capacity should be enlarged.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.76

Alarm 2112009
Specific Problem

2112009

Managed Object

OnGuard

Description

A file system free space event timed out.

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112006

System Impact

File system free space is not checked.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.
SMSC 4.2 Alarm Reference Manual
P/N 10-000-1050 Issue 1 Rev. 0.1

372 of 492

7: Application Agent Alarms

7.5.77

DRAFT

Oracle Database Alarms (OnGuard Agent)

Alarm 2112010
Specific Problem

2112010

Managed Object

OnGuard

Description

A file system free space event failed.

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112006

System Impact

File system free space is not checked.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.78

Alarm 2112011
Specific Problem

2112011

Managed Object

OnGuard

Description

The load average is <load average value>.

Additional
Information

<load average value>: Load average value.

Severity

Normal

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

No

Threshold

02

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.79

Alarm 2112012
Specific Problem

2112012

Managed Object

OnGuard

Description

The load average is <load average value>. There is a


problem with the last <events number> events.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

373 of 492

7: Application Agent Alarms

Additional
Information

DRAFT

Oracle Database Alarms (OnGuard Agent)

<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 last
15 minutes per processor.
Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112011

Threshold

23

System Impact

Lower system performance.

Recommended
Corrective Action

Reduce the number of heavy applications on the unit if


possible.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.80

Alarm 2112013
Specific Problem

2112013

Managed Object

OnGuard

Description

The load average is <load average value>. There is a


problem with the last <events number> events.

Additional
Information

<load average value>: Load average value


<events number>: Number of consequent events with
this problem

Very high average number of jobs in the run queue over the
last 15 minutes per processor.
Severity

Major

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112011

Threshold

4+

System Impact

Lower system performance.

Recommended
Corrective Action

Reduce the number of heavy applications on the machine if


possible.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.81

Alarm 2112014

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

374 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

Specific Problem

2112014

Managed Object

OnGuard

Description

A load average event timed out.

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112011

System Impact

Load average is not checked.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.82

Alarm 2112015
Specific Problem

2112015

Managed Object

OnGuard

Description

A load average event failed.

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112011

System Impact

Load average is not checked.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.83

Alarm 2112016
Specific Problem

2112016

Managed Object

OnGuard

Description

The swap usage is <swap value>%.

Additional
Information

<swap value>: Percentage of swap area in use.

Severity

Normal

Message Group
(Probable Cause)

Operating System

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

375 of 492

7: Application Agent Alarms

DRAFT

Alarm Automatically
Cleared

No

Threshold

069%

Oracle Database Alarms (OnGuard Agent)

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.84

Alarm 2112017
Specific Problem

2112017

Managed Object

OnGuard

Description

The swap usage is <swap value>%. There is a problem with


the last <events number> events.

Additional
Information

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112016

Threshold

7089%

System Impact

Lower system performance.

Recommended
Corrective Action

Enlarge swap area size on this machine if possible.

<swap value>: Percentage of swap area in use


<events number>: Number of consequent events with
this problem

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.85

Alarm 2112018
Specific Problem

2112018

Managed Object

OnGuard

Description

The swap usage is <swap value>%. There is a problem with


the last <events number> events.

Additional
Information

Severity

Major

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112016

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

<swap value>: Percentage of swap area in use


<events number>: Number of consequent events with
this problem

376 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

Threshold

90100%

System Impact

Lower system performance.

Recommended
Corrective Action

Enlarge swap area size on this machine if possible.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.86

Alarm 2112019
Specific Problem

2112019

Managed Object

OnGuard

Description

A swap usage event timed out.

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112016

System Impact

Swap usage is not checked.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.87

Alarm 2112020
Specific Problem

2112020

Managed Object

OnGuard

Description

A swap usage event failed.

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112016

System Impact

Swap usage is not checked.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.88

Alarm 2112021

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

377 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

Specific Problem

2112021

Managed Object

OnGuard

Description

The I/O wait is <I/O waits value>%.

Additional
Information

<I/O waits value>: Percentage of I/O waits out of the total


CPU time.

Severity

Normal

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

No

Threshold

09

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.89

Alarm 2112022
Specific Problem

2112022

Managed Object

OnGuard

Description

The I/O wait is <I/O waits value>%. There is a problem with


the last <events number> events.

Additional
Information

<I/O waits value>: Percentage of I/O waits out of the


total CPU time

<events number>: Number of consequent events with


this problem

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112021

Threshold

10-29

System Impact

Lower system performance.

Recommended
Corrective Action

If possible, stop using the problematic application, or else


CPUs may need to be added to this machine.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.90

Alarm 2112023
Specific Problem

2112023

Managed Object

OnGuard

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

378 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

Description

The I/O wait is <I/O waits value>%. There is a problem with


the last <events number> events.

Additional
Information

<I/O waits value>: Percentage of I/O waits out of the


total CPU time

<events number>: Number of consequent events with


this problem

Severity

Major

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112021

Threshold

30+

System Impact

Lower system performance.

Recommended
Corrective Action

If possible, stop using the problematic application, or else


CPUs may need to be added to this machine.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.91

Alarm 2112024
Specific Problem

2112024

Managed Object

OnGuard

Description

An I/O wait event timed out.

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112021

System Impact

I/O wait is not checked.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.92

Alarm 2112025
Specific Problem

2112025

Managed Object

OnGuard

Description

An I/O wait event failed.

Severity

Warning

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

379 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112021

System Impact

I/O wait is not checked.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.93

Alarm 2112026
Specific Problem

2112026

Managed Object

OnGuard

Description

The network response time for <server name> is normal.

Additional
Information

<server name>: Server name, IP, or URL

Severity

Normal

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

No

Threshold

019 ms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.94

Alarm 2112027
Specific Problem

2112027

Managed Object

OnGuard

Description

High network response time. The network response time for


<server name> is <response time> ms.

Additional
Information

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112026

Threshold

20+ ms

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

<server name>: Server name, IP, or URL


<response time>: Average response time in ms

380 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

System Impact

Poor network connection to the remote server which may


cause slow data transfer.

Recommended
Corrective Action

System administrator to check the network and remote server.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.95

Alarm 2112028
Specific Problem

2112028

Managed Object

OnGuard

Description

<server name> is not responding to a ping request (<lost


packets> out of <sent packets> packets lost).

Additional
Information

<server name>: Server name, IP, or URL


<lost packets>: Number of lost packets
<sent packets>: Number of sent packets

Severity

Critical

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112026

Threshold

Failed ping

System Impact

Remote server is not accessible.

Recommended
Corrective Action

System administrator to check the network and remote server.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.96

Alarm 2112029
Specific Problem

2112029

Managed Object

OnGuard

Description

Ping error for <server name> (unknown host <server name>).

Additional
Information

<server name>: Server name, IP, or URL.

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112026

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

381 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

Threshold

Failed ping

System Impact

Remote server is not accessible.

Recommended
Corrective Action

Ask the system administrator about this host name and in


case of need, change it in OnGuard.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.97

Alarm 2112030
Specific Problem

2112030

Managed Object

OnGuard

Description

Network availability event timed out.

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112026

System Impact

Network availability is not checked.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.98

Alarm 2112031
Specific Problem

2112031

Managed Object

OnGuard

Description

Pinging <server name> failed.

Additional
Information

<server name>: Server name, IP, or URL

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112026

System Impact

This server is not checked for network availability.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.
SMSC 4.2 Alarm Reference Manual
P/N 10-000-1050 Issue 1 Rev. 0.1

382 of 492

7: Application Agent Alarms

7.5.99

DRAFT

Oracle Database Alarms (OnGuard Agent)

Alarm 2112032
Specific Problem

2112032

Managed Object

OnGuard

Description

<memory used>% of the physical memory is in use (<used


MB> of <total MB> MB).

Additional
Information

<memory used>: Percentage of memory in use


<used MB>: Number of MB of memory in use
<total MB>: Total MB of memory

Severity

Normal

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

No

Threshold

084%

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.100

Alarm 2112033
Specific Problem

2112033

Managed Object

OnGuard

Description

<memory used>% of the physical memory is in use (<used


MB> of <total MB> MB).

Additional
Information

<memory used>: Percentage of memory in use


<used MB>: Number of MB of memory in use
<total MB>: Total MB of memory

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112032

Threshold

8594%

System Impact

Lower system performance.

Recommended
Corrective Action

Do one of the following:

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

If the server performance is low, check which


application is consuming a lot of memory and stop using
it if possible.

If the server performance is not low, add memory to


the machine.

383 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.101

Alarm 2112034
Specific Problem

2112034

Managed Object

OnGuard

Description

<memory used>% of the physical memory is in use (<used


MB> of <total MB> MB).

Additional
Information

<memory used>: Percentage of memory in use


<used MB>: Number of MB of memory in use
<total MB>: Total MB of memory

Severity

Major

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112032

Threshold

95100%

System Impact

Lower system performance

Recommended
Corrective Action

Do one of the following:

If the server performance is low, check which


application is consuming a lot of memory and stop using
it if possible.

If the server performance is not low, add memory to


the machine.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.102

Alarm 2112035
Specific Problem

2112035

Managed Object

OnGuard

Description

A physical memory free event timed out.

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112032

System Impact

Physical memory free space is not checked.

Recommended
Corrective Action

Contact Comverse customer support.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

384 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.103

Alarm 2112036
Specific Problem

2112036

Managed Object

OnGuard

Description

A physical memory free event failed.

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 2112032

System Impact

Physical memory free space is not checked.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.104

Alarm 2112042
Specific Problem

2112042

Managed Object

OnGuard

Description

CPU fan 2 has failed.

Additional
Information

CPU fan

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced system cooling.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.105

Alarm 2112043
Specific Problem

2112043

Managed Object

OnGuard

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

385 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

Description

CPU fan 3 has failed.

Additional
Information

CPU fan

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced system cooling.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.106

Alarm 2112044
Specific Problem

2112044

Managed Object

OnGuard

Description

Fan 0 has failed.

Additional
Information

Fan

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced system cooling.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.107

Alarm 2112045
Specific Problem

2112045

Managed Object

OnGuard

Description

Fan 1 has failed.

Additional
Information

Fan

Severity

Major

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

386 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced system cooling.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.108

Alarm 2112046
Specific Problem

2112046

Managed Object

OnGuard

Description

DC power unavailable for power supply 0.

Additional
Information

DC power

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Check the power cable and power input for power supply 0.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.109

Alarm 2112047
Specific Problem

2112047

Managed Object

OnGuard

Description

DC power unavailable for power supply 1.

Additional
Information

DC power

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

387 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Check the power cable and power input for power supply 1.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.110

Alarm 2112048
Specific Problem

2112048

Managed Object

OnGuard

Description

Fan 0 has failed.

Additional
Information

Fan

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced system cooling.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.111

Alarm 2112049
Specific Problem

2112049

Managed Object

OnGuard

Description

Fan 1 has failed.

Additional
Information

Fan

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced system cooling.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.
SMSC 4.2 Alarm Reference Manual
P/N 10-000-1050 Issue 1 Rev. 0.1

388 of 492

7: Application Agent Alarms

7.5.112

DRAFT

Oracle Database Alarms (OnGuard Agent)

Alarm 2112050
Specific Problem

2112050

Managed Object

OnGuard

Description

Fan 2 has failed.

Additional
Information

Fan

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced system cooling.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.113

Alarm 2112051
Specific Problem

2112051

Managed Object

OnGuard

Description

Fan 3 has failed.

Additional
Information

Fan

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced system cooling.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.114

Alarm 2112052
Specific Problem

2112052

Managed Object

OnGuard

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

389 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

Description

Power supply 0 has been inserted.

Additional
Information

Power supply

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Recommended
Corrective Action

Check that this action was initiated and planned internally.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.115

Alarm 2112053
Specific Problem

2112053

Managed Object

OnGuard

Description

Power supply 0 has been removed.

Additional
Information

Power supply

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 2112052

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Check that this action was initiated and planned internally.


Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.116

Alarm 2112054
Specific Problem

2112054

Managed Object

OnGuard

Description

Power supply 1 has been inserted.

Additional
Information

Power supply

Severity

Normal

Message Group
(Probable Cause)

Hardware

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

390 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

Alarm Automatically
Cleared

No

Recommended
Corrective Action

Check that this action was initiated and planned internally.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.117

Alarm 2112055
Specific Problem

2112055

Managed Object

OnGuard

Description

Power supply 1 has been removed.

Additional
Information

Power supply

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 2112054

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Check that this action was initiated and planned internally.


Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.118

Alarm 2112056
Specific Problem

2112056

Managed Object

OnGuard

Description

CPU 0 high temperature exceeded hard shutdown threshold.

Additional
Information

CPU temperature

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Threshold

118 C

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

391 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

System Impact

Server down due to high temperature. Downtime in case of


no server redundancy.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.119

Alarm 2112057
Specific Problem

2112057

Managed Object

OnGuard

Description

CPU 0 high temperature exceeded soft shutdown threshold.

Additional
Information

CPU temperature

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Threshold

115 C

System Impact

Server down due to high temperature. Downtime in case of


no server redundancy.

Recommended
Corrective Action

Contact Comverse customer support.

Soft shutdown performs self shutdown through command.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.120

Alarm 2112058
Specific Problem

2112058

Managed Object

OnGuard

Description

CPU 0 high temperature warning.

Additional
Information

CPU temperature

Severity

Minor

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

392 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

Threshold

110 C

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.121

Alarm 2112059
Specific Problem

2112059

Managed Object

OnGuard

Description

CPU 1 high temperature exceeded hard shutdown threshold.

Additional
Information

CPU temperature

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Threshold

118 C

System Impact

Server down due to high temperature. Downtime in case of


no server redundancy.

Recommended
Corrective Action

Contact Comverse customer support.

Hard Shutdown performs immediate shutdown.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.122

Alarm 2112060
Specific Problem

2112060

Managed Object

OnGuard

Description

CPU 1 high temperature exceeded soft shutdown threshold.

Additional
Information

CPU temperature

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Threshold

115 C

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

Soft shutdown performs self shutdown through command.

393 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

System Impact

Server down due to high temperature. Downtime in case of


no server redundancy.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.123

Alarm 2112061
Specific Problem

2112061

Managed Object

OnGuard

Description

CPU 1 high temperature warning.

Additional
Information

CPU temperature

Severity

Minor

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Threshold

110 C

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.124

Alarm 2112062
Specific Problem

2112062

Managed Object

OnGuard

Description

Power Supply 0 internal connection failure.

Additional
Information

Power supply

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Check the power supply LED. If the problem persists, contact


Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.
SMSC 4.2 Alarm Reference Manual
P/N 10-000-1050 Issue 1 Rev. 0.1

394 of 492

7: Application Agent Alarms

7.5.125

DRAFT

Oracle Database Alarms (OnGuard Agent)

Alarm 2112063
Specific Problem

2112063

Managed Object

OnGuard

Description

Power Supply 1 internal connection failure.

Additional
Information

Power supply

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Check the power supply LED. If the problem persists, contact


Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.126

Alarm 2112064
Specific Problem

2112064

Managed Object

OnGuard

Description

Power Supply 2 internal connection failure.

Additional
Information

Power supply

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Check the power supply LED. If the problem persists, contact


Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.127

Alarm 2112065
Specific Problem

2112065

Managed Object

OnGuard

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

395 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

Description

Power Supply 3 internal connection failure.

Additional
Information

Power supply

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Check the power supply LED. If the problem persists, contact


Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.128

Alarm 2112066
Specific Problem

2112066

Managed Object

OnGuard

Description

CPU fan tray 0 has been inserted.

Additional
Information

CPU fan tray

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Recommended
Corrective Action

Verify that this action was planned and initiated by a


technician.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.129

Alarm 2112067
Specific Problem

2112067

Managed Object

OnGuard

Description

CPU fan tray 0 has been removed.

Additional
Information

CPU fan tray

Severity

Major

Message Group
(Probable Cause)

Hardware

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

396 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

Alarm Automatically
Cleared

Yes; by 2112066

System Impact

Reduced system cooling.

Recommended
Corrective Action

Verify that this action was planned and initiated by a


technician.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.130

Alarm 2112068
Specific Problem

2112068

Managed Object

OnGuard

Description

CPU fan tray 0 has failed.

Additional
Information

CPU fan tray

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced system cooling.

Recommended
Corrective Action

Check the fan LED status.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.131

Alarm 2112069
Specific Problem

2112069

Managed Object

OnGuard

Description

CPU fan tray 1 has been inserted.

Additional
Information

CPU fan tray

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Recommended
Corrective Action

Verify that this action was planned and initiated by a


technician.

For a detailed description of these rows, see Alarm Fields Description, Page 7.
SMSC 4.2 Alarm Reference Manual
P/N 10-000-1050 Issue 1 Rev. 0.1

397 of 492

7: Application Agent Alarms

7.5.132

DRAFT

Oracle Database Alarms (OnGuard Agent)

Alarm 2112070
Specific Problem

2112070

Managed Object

OnGuard

Description

CPU fan tray 1 has been removed.

Additional
Information

CPU fan tray

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced system cooling.

Recommended
Corrective Action

Verify that this action was planned and initiated by a


technician.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.133

Alarm 2112071
Specific Problem

2112071

Managed Object

OnGuard

Description

CPU fan tray 1 has failed.

Additional
Information

CPU fan tray

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 2112069

System Impact

Reduced system cooling.

Recommended
Corrective Action

Check the fan LED status.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.134

Alarm 2112072
Specific Problem

2112072

Managed Object

OnGuard

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

398 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

Description

CPU fan tray 2 has been inserted.

Additional
Information

CPU fan tray

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Recommended
Corrective Action

Verify that this action was planned and initiated by a


technician.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.135

Alarm 2112073
Specific Problem

2112073

Managed Object

OnGuard

Description

CPU fan tray 2 has been removed.

Additional
Information

CPU fan tray

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

Yes; by 2112069

System Impact

Reduced system cooling.

Recommended
Corrective Action

Verify that this action was planned and initiated by a


technician.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.136

Alarm 2112074
Specific Problem

2112074

Managed Object

OnGuard

Description

CPU fan tray 2 has failed.

Additional
Information

CPU fan tray

Severity

Major

Message Group
(Probable Cause)

Hardware

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

399 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

Alarm Automatically
Cleared

No

System Impact

Reduced system cooling.

Recommended
Corrective Action

Check the fan LED status.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.137

Alarm 2112075
Specific Problem

2112075

Managed Object

OnGuard

Description

CPU fan tray 3 has failed.

Additional
Information

CPU fan tray

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced system cooling.

Recommended
Corrective Action

Check the fan LED status.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.138

Alarm 2112076
Specific Problem

2112076

Managed Object

OnGuard

Description

Input power unavailable for power supply 0.

Additional
Information

Input power

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Check the power cable and power input for power supply 0.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

400 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.139

Alarm 2112077
Specific Problem

2112077

Managed Object

OnGuard

Description

Input power unavailable for power supply 1.

Additional
Information

Input power

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Check the power cable and power input for power supply 1.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.140

Alarm 2112078
Specific Problem

2112078

Managed Object

OnGuard

Description

Input power unavailable for power supply 2.

Additional
Information

Input power

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Check the power cable and power input for power supply 2.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.141

Alarm 2112079

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

401 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

Specific Problem

2112079

Managed Object

OnGuard

Description

Input power unavailable for power supply 3.

Additional
Information

Input power

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Check the power cable and power input for power supply 3.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.142

Alarm 2112080
Specific Problem

2112080

Managed Object

OnGuard

Description

Power supply 0 has been inserted.

Additional
Information

Power supply

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Recommended
Corrective Action

Verify that this action was planned and initiated by a


technician.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.143

Alarm 2112081
Specific Problem

2112081

Managed Object

OnGuard

Description

Power supply 0 has been removed.

Additional
Information

Power supply

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

402 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Verify that this action was planned and initiated by a


technician.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.144

Alarm 2112082
Specific Problem

2112082

Managed Object

OnGuard

Description

Power supply 0 has failed.

Additional
Information

Power supply

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Check the power supply LEDs status. If the problem persists,


contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.145

Alarm 2112083
Specific Problem

2112083

Managed Object

OnGuard

Description

Power supply 0 is not properly in place.

Additional
Information

Power supply

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

403 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Check that power supply 0 is properly inserted.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.146

Alarm 2112084
Specific Problem

2112084

Managed Object

OnGuard

Description

Power supply 1 has been inserted.

Additional
Information

Power supply

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Recommended
Corrective Action

Verify that this action was planned and initiated by a


technician.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.147

Alarm 2112085
Specific Problem

2112085

Managed Object

OnGuard

Description

Power supply 1 has been removed.

Additional
Information

Power supply

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Verify that this action was planned and initiated by a


technician.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

404 of 492

7: Application Agent Alarms

7.5.148

DRAFT

Oracle Database Alarms (OnGuard Agent)

Alarm 2112086
Specific Problem

2112086

Managed Object

OnGuard

Description

Power supply 1 has failed.

Additional
Information

Power supply

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Check the power supply LED.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.149

Alarm 2112087
Specific Problem

2112087

Managed Object

OnGuard

Description

Power supply 1 is not properly in place.

Additional
Information

Power supply

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Check that power supply 1 is properly inserted.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.150

Alarm 2112088
Specific Problem

2112088

Managed Object

OnGuard

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

405 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

Description

Power supply 2 has been inserted.

Additional
Information

Power supply

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Recommended
Corrective Action

Verify that this action was planned and initiated by a


technician.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.151

Alarm 2112089
Specific Problem

2112089

Managed Object

OnGuard

Description

Power supply 2 has been removed.

Additional
Information

Power supply

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Verify that this action was planned and initiated by a


technician.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.152

Alarm 2112090
Specific Problem

2112090

Managed Object

OnGuard

Description

Power supply 2 has failed.

Additional
Information

Power supply

Severity

Major

Message Group
(Probable Cause)

Hardware

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

406 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

Alarm Automatically
Cleared

No

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Check the power supply LED.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.153

Alarm 2112091
Specific Problem

2112091

Managed Object

OnGuard

Description

Power supply 2 is not properly in place.

Additional
Information

Power supply

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Check that power supply 2 is properly inserted.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.154

Alarm 2112092
Specific Problem

2112092

Managed Object

OnGuard

Description

Power supply 3 has been inserted.

Additional
Information

Power supply

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Recommended
Corrective Action

Verify that this action was planned and initiated by a


technician.

For a detailed description of these rows, see Alarm Fields Description, Page 7.
SMSC 4.2 Alarm Reference Manual
P/N 10-000-1050 Issue 1 Rev. 0.1

407 of 492

7: Application Agent Alarms

7.5.155

DRAFT

Oracle Database Alarms (OnGuard Agent)

Alarm 2112093
Specific Problem

2112093

Managed Object

OnGuard

Description

Power supply 3 has been removed.

Additional
Information

Power supply

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Verify that this action was planned and initiated by a


technician.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.156

Alarm 2112094
Specific Problem

2112094

Managed Object

OnGuard

Description

Power supply 3 has failed.

Additional
Information

Power supply

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Check the power supply LED.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.157

Alarm 2112095
Specific Problem

2112095

Managed Object

OnGuard

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

408 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

Description

Power supply 3 is not properly in place.

Additional
Information

Power supply

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Reduced power redundancy.

Recommended
Corrective Action

Check that power supply 3 is properly inserted.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.158

Alarm 2112096
Specific Problem

2112096

Managed Object

OnGuard

Description

CPU 0 high temperature exceeded hard shutdown threshold.

Additional
Information

CPU temperature

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Threshold

118 C

System Impact

Server down due to high temperature. Downtime in case of


no server redundancy.

Recommended
Corrective Action

Contact Comverse customer support.

Hard Shutdown performs immediate shutdown.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.159

Alarm 2112097
Specific Problem

2112097

Managed Object

OnGuard

Description

CPU 0 high temperature exceeded soft shutdown threshold.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

409 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

Additional
Information

CPU temperature

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Threshold

110 C

System Impact

Server down due to high temperature. Downtime in case of


no server redundancy.

Recommended
Corrective Action

Contact Comverse customer support.

Soft shutdown performs self shutdown through command.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.160

Alarm 2112098
Specific Problem

2112098

Managed Object

OnGuard

Description

CPU 0 high temperature warning.

Additional
Information

CPU temperature

Severity

Minor

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Threshold

102 C

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.161

Alarm 2112099
Specific Problem

2112099

Managed Object

OnGuard

Description

CPU 1 high temperature exceeded hard shutdown threshold.

Additional
Information

CPU temperature

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

Hard Shutdown performs immediate shutdown.

410 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Threshold

118 C

System Impact

Server down due to high temperature. Downtime in case of


no server redundancy.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.162

Alarm 2112100
Specific Problem

2112100

Managed Object

OnGuard

Description

CPU 1 high temperature exceeded soft shutdown threshold.

Additional
Information

CPU temperature

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Threshold

110 C

System Impact

Server down due to high temperature. Downtime in case of


no server redundancy.

Recommended
Corrective Action

Contact Comverse customer support.

Soft shutdown performs self shutdown through command.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.163

Alarm 2112101
Specific Problem

2112101

Managed Object

OnGuard

Description

CPU 1 high temperature warning.

Additional
Information

CPU temperature

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

411 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

Severity

Minor

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Threshold

102 C

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.164

Alarm 2112102
Specific Problem

2112102

Managed Object

OnGuard

Description

CPU 2 high temperature exceeded hard shutdown threshold.

Additional
Information

CPU temperature

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Server down due to high temperature. Downtime in case of


no server redundancy.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.165

Alarm 2112103
Specific Problem

2112103

Managed Object

OnGuard

Description

CPU 2 high temperature exceeded soft shutdown threshold.

Additional
Information

CPU temperature

Severity

Major

Message Group
(Probable Cause)

Hardware

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

412 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

Alarm Automatically
Cleared

No

System Impact

Server down due to high temperature. Downtime in case of


no server redundancy.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.166

Alarm 2112104
Specific Problem

2112104

Managed Object

OnGuard

Description

CPU 2 high temperature warning.

Additional
Information

CPU temperature

Severity

Minor

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.167

Alarm 2112105
Specific Problem

2112105

Managed Object

OnGuard

Description

CPU 3 high temperature exceeded hard shutdown threshold.

Additional
Information

CPU temperature

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

413 of 492

7: Application Agent Alarms

DRAFT

Oracle Database Alarms (OnGuard Agent)

System Impact

Server down due to high temperature. Down time in case of


no server redundancy.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.168

Alarm 2112106
Specific Problem

2112106

Managed Object

OnGuard

Description

CPU 3 high temperature exceeded soft shutdown threshold.

Additional
Information

CPU temperature

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

System Impact

Server down due to high temperature. Downtime in case of


no server redundancy.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.5.169

Alarm 2112107
Specific Problem

2112107

Managed Object

OnGuard

Description

CPU 3 high temperature warning.

Additional
Information

CPU temperature

Severity

Minor

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.
SMSC 4.2 Alarm Reference Manual
P/N 10-000-1050 Issue 1 Rev. 0.1

414 of 492

7: Application Agent Alarms

7.6

DRAFT

Server Monitor (SMU) Alarms

Server Monitor (SMU) Alarms


Search for the alarm you need by its Specific Problem (Alarm ID).

7.6.1

Alarm 1990001 (The \inetd\ process is not running


anymore)
Specific Problem

1990001

Managed Object

SMU

Description

The \inetd\ process is not running anymore.

Additional
Information

daemon

Severity

Minor

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

Yes; by 1990001

Threshold

0.5

System Impact

Network connectivity problems.

Recommended
Corrective Action

Restart the inetd process by typing:


/usr/sbin/inetd -s &

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.2

Alarm 1990001 (The \inetd\ process is running)


Specific Problem

1990001

Managed Object

SMU

Description

The \inetd\ process is running

Additional
Information

daemon

Severity

Normal

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

No

System Impact

None

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

415 of 492

7: Application Agent Alarms

7.6.3

DRAFT

Server Monitor (SMU) Alarms

Alarm 1990002 (CPU utilization (<$VALUE>%)


exceeds configured threshold (<$THRESHOLD>%.)
Specific Problem

1990002

Managed Object

SMU

Description

CPU utilization (<$VALUE>%) exceeds configured threshold


(<$THRESHOLD>%).

Additional
Information

CPU

Severity

Major

Message Group
(Probable Cause)

Capacity

Alarm Automatically
Cleared

Yes; by 1990002

Threshold

95 within 6 minutes

System Impact

System Monitoring may experience high service degradation.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.4

Alarm 1990002 (CPU utilization (<$VALUE>%) is ok)


Specific Problem

1990002

Managed Object

SMU

Description

CPU utilization (<$VALUE>%) is ok

Additional
Information

CPU

Severity

Normal

Message Group
(Probable Cause)

Capacity

Alarm Automatically
Cleared

No

System Impact

None

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

416 of 492

7: Application Agent Alarms

7.6.5

DRAFT

Server Monitor (SMU) Alarms

Alarm 1990003 (Utilization of file-system


<fileSystem> (<$VALUE>%) exceeds configured
threshold <$THRESHOLD>%.)
Specific Problem

1990003

Managed Object

SMU

Description

Utilization of file-system <fileSystem> (<$VALUE>%) exceeds


configured threshold <$THRESHOLD>%.

Additional
Information

<fileSystem>

Severity

Critical

Message Group
(Probable Cause)

Capacity

Alarm Automatically
Cleared

Yes; by 1990003

Threshold

95

System Impact

System Monitoring will probably experience high service


degradation.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

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

Additional
Information

<fileSystem>

Severity

Normal

Message Group
(Probable Cause)

Capacity

Alarm Automatically
Cleared

No

System Impact

None

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

417 of 492

7: Application Agent Alarms

7.6.7

DRAFT

Server Monitor (SMU) Alarms

Alarm 1990004 (Process table utilization


(<$VALUE>%) exceeds configured threshold
(<$THRESHOLD>%)
Specific Problem

1990004

Managed Object

SMU

Description

Process table utilization (<$VALUE>%) exceeds configured


threshold (<$THRESHOLD>%)

Additional
Information

process limit

Severity

Major

Message Group
(Probable Cause)

Capacity

Alarm Automatically
Cleared

Yes; by 1990004

Threshold

80

System Impact

May cause unexpected program failure.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.8

Alarm 1990004 (Process table utilization


(<$VALUE>%) is ok)
Specific Problem

1990004

Managed Object

SMU

Description

Process table utilization (<$VALUE>%) is ok

Additional
Information

process limit

Severity

Major

Message Group
(Probable Cause)

Capacity

Alarm Automatically
Cleared

No

System Impact

None

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

418 of 492

7: Application Agent Alarms

7.6.9

DRAFT

Server Monitor (SMU) Alarms

Alarm 1990005 (SWAP Utilization (<$VALUE>%)


exceeds configured threshold (<$THRESHOLD>%))
Specific Problem

1990005

Managed Object

SMU

Description

SWAP Utilization (<$VALUE>%) exceeds configured


threshold (<$THRESHOLD>%)

Additional Info

swap_disk

Severity

Major

Message Group
(Probable Cause)

Capacity

Alarm Automatically
Cleared

Yes; by 1990005

Threshold

80

System Impact

System may experience service degradation.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.10

Alarm 1990005 (SWAP Utilization (<$VALUE>%) is


ok)
Specific Problem

1990005

Managed Object

SMU

Description

SWAP Utilization (<$VALUE>%) is ok

Additional Info

swap_disk

Severity

Normal

Message Group
(Probable Cause)

Capacity

Alarm Automatically
Cleared

No

System Impact

None

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.11

Alarm 1990006 (Distribution files for <$VALUE>


node(s) exist)

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

419 of 492

7: Application Agent Alarms

DRAFT

Server Monitor (SMU) Alarms

Specific Problem

1990006

Managed Object

SMU

Description

Distribution files for <$VALUE> node(s) exist.

Additional
Information

Template

Severity

Warning

Message Group
(Probable Cause)

OpC

Alarm Automatically
Cleared

Yes; by 1990006

Threshold

System Impact

None

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.12

Alarm 1990006 (Distribution files for 0 node(s) exist)


Specific Problem

1990006

Managed Object

SMU

Description

Distribution files for 0 node(s) exist

Additional
Information

Template

Severity

Normal

Message Group
(Probable Cause)

OpC

Alarm Automatically
Cleared

No

System Impact

None

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.13

Alarm 1990007
Specific Problem

1990007

Managed Object

SMU

Description

Distribution still pending after <$OPTION(maxage)> min. for


<$MSG_TEXT>

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

420 of 492

7: Application Agent Alarms

DRAFT

Server Monitor (SMU) Alarms

Additional
Information

Template

Severity

Warning

Message Group
(Probable Cause)

OpC

Alarm Automatically
Cleared

No

System Impact

System monitoring may experience service degradation.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.14

Alarm 1991001 (Failed login of <user> on <tty>)


Specific Problem

1991001

Managed Object

SMU

Description

Failed login of <user> on <tty>

Additional
Information

<user> (log only)

Severity

Warning

Message Group
(Probable Cause)

Security

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.15

Alarm 1991001 (Resource <resource_name> is


faulted)
Specific Problem

1991001

Managed Object

SMU

Description

Resource <resource_name> is faulted

Additional
Information

SMU Monitor

Severity

Critical

Message Group
(Probable Cause)

High Availability

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

421 of 492

7: Application Agent Alarms

DRAFT

Server Monitor (SMU) Alarms

Alarm Automatically
Cleared

No

System Impact

<resource_name> is not in service and will not be available


until the resource is repaired.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

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>)

Additional
Information

cron (log only)

Severity

Major

Message Group
(Probable Cause)

Job

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.17

Alarm 1991002 (Group <group_name> is faulted)


Specific Problem

1991002

Managed Object

SMU

Description

Group <group_name> is faulted

Additional
Information

SMU Monitor

Severity

Critical

Message Group
(Probable Cause)

High Availability

Alarm Automatically
Cleared

No

System Impact

A critical resource is not in service. SMU monitoring will be


degraded; no SMU monitoring or alarms will arrive at the
NOC.

Recommended
Corrective Action

Contact Comverse customer support.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

422 of 492

7: Application Agent Alarms

DRAFT

Server Monitor (SMU) Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.18

Alarm 1991003 (System reboot)


Specific Problem

1991003

Managed Object

SMU

Description

System reboot

Additional
Information

log only

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

No

System Impact

System service downtime

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.19

Alarm 1991003 (Group <group_name> is offline)


Specific Problem

1991003

Managed Object

SMU

Description

Group <group_name> is offline

Additional
Information

SMU Monitor

Severity

Warning

Message Group
(Probable Cause)

High Availability

Alarm Automatically
Cleared

Yes; by 1991003

System Impact

System downtime while the group is offline.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.20

Alarm 1991004
Specific Problem

1991004

Managed Object

SMU

Description

System shutdown started on <tty>

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

423 of 492

7: Application Agent Alarms

DRAFT

Server Monitor (SMU) Alarms

Additional
Information

log only

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

No

System Impact

System service down until the SMU is restarted.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.21

Alarm 1991005
Specific Problem

1991005

Managed Object

SMU

Description

System shutdown started

Additional
Information

log only

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

No

System Impact

System service down until the SMU is restarted.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.22

Alarm 1991006
Specific Problem

1991006

Managed Object

SMU

Description

<Message Text>

Severity

Minor

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

424 of 492

7: Application Agent Alarms

7.6.23

DRAFT

Server Monitor (SMU) Alarms

Alarm 1991007
Specific Problem

1991007

Managed Object

SMU

Description

Bad logon via FTP

Additional
Information

log only

Severity

Warning

Message Group
(Probable Cause)

Security

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.24

Alarm 1991008
Specific Problem

1991008

Managed Object

SMU

Description

System <node> was rebooted by <who>.

Additional
Information

<who> (log only)

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

No

System Impact

System service downtime.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.25

Alarm 1991009
Specific Problem

1991009

Managed Object

SMU

Description

kernel table \<tablename>\ is full

Additional
Information

<tablename>

Severity

Warning

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

425 of 492

7: Application Agent Alarms

DRAFT

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

No

System Impact

System service will be degraded.

Server Monitor (SMU) Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.26

Alarm 1991010
Specific Problem

1991010

Managed Object

SMU

Description

The filesystem \<filesys>\ is nearly full

Additional
Information

Filesystem

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

No

System Impact

System service will be degraded.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.27

Alarm 1991011
Specific Problem

1991011

Managed Object

SMU

Description

The filesystem \<filesys>\ is full

Additional
Information

Filesystem

Severity

Critical

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

No

System Impact

System service will be degraded and may not be available.

Recommended
Corrective Action

Contact Comverse customer support.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

426 of 492

7: Application Agent Alarms

DRAFT

Server Monitor (SMU) Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.28

Alarm 1991012
Specific Problem

1991012

Managed Object

SMU

Description

NFS server <mach_name> is not responding to NFS requests

Additional
Information

NFS subsystem

Severity

Warning

Message Group
(Probable Cause)

Operating System

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.29

Alarm 1992001
Specific Problem

1992001

Managed Object

SMU

Description

<object name> on <object instance> did not respond to snmp


requests - agent may be down!

Additional
Information

<object name>

Severity

Critical

Message Group
(Probable Cause)

OpC

Alarm Automatically
Cleared

Yes; by 1992001

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.30

Alarm 1992001 (Cleared)


Specific Problem

1992001

Managed Object

SMU

Description

<object name> on <object instance> availability was verified!

Additional
Information

<object name>

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

427 of 492

7: Application Agent Alarms

DRAFT

Severity

Cleared (Normal)

Message Group
(Probable Cause)

OpC

Alarm Automatically
Cleared

No

Server Monitor (SMU) Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.31

Alarm 1992003
Specific Problem

1992003

Managed Object

SMU

Description

Inventory in SCDB was changed! Initiate Service Topology


population

Severity

Warning

Message Group
(Probable Cause)

OpC

Alarm Automatically
Cleared

Yes; by 1992004

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.32

Alarm 1992004 (Log Only)


Specific Problem

1992004

Managed Object

SMU

Description

Service Topology was successfully built

Severity

Normal

Message Group
(Probable Cause)

OpC

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.33

Alarm 1992004
Specific Problem

1992004

Managed Object

SMU

Description

Service Topology Population process FAILED!

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

428 of 492

7: Application Agent Alarms

DRAFT

Severity

Major

Message Group
(Probable Cause)

OpC

Alarm Automatically
Cleared

Yes; by 1992004

System Impact

No system topology.

Server Monitor (SMU) Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.34

Alarm 1992005
Specific Problem

1992005

Managed Object

SMU

Description

SCDB is not synchronized with Service Topology after


rollback was triggered

Severity

Major

Message Group
(Probable Cause)

OpC

Alarm Automatically
Cleared

No

System Impact

The map will not be synchronized with the SCDB.xml


configuration file.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.35

Alarm 1992006
Specific Problem

1992006

Managed Object

SMU

Description

rollback can not be done previous SCDB version could not


be found

Severity

Warning

Message Group
(Probable Cause)

OpC

Alarm Automatically
Cleared

Yes; by 1992004

System Impact

The system will not be returned to its previous state.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

429 of 492

7: Application Agent Alarms

7.6.36

DRAFT

Server Monitor (SMU) Alarms

Alarm 1992529
Specific Problem

1992529

Managed Object

SMU

Description

Your Name Services are performing poorly, likely to be a


wrong configuration.
The average for the past <number of lookups> lookups took
<average number of milliseconds> milliseconds, expect less
than <threshold value in milliseconds> milliseconds.

Additional
Information

Network

Severity

Minor

Message Group
(Probable Cause)

Performance

Alarm Automatically
Cleared

Yes; by 1992530

System Impact

Low service name performance.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.37

Alarm 1992530
Specific Problem

1992530

Managed Object

SMU

Description

Your Name Services is performing poorly, possibly a wrong


configuration.
<Lookup type> of <String being looked up> took <number of
seconds> seconds to resolve.

Additional
Information

Network

Severity

Warning

Message Group
(Probable Cause)

Performance

Alarm Automatically
Cleared

Yes; by 1992529

System Impact

Service name may have low performance.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.
SMSC 4.2 Alarm Reference Manual
P/N 10-000-1050 Issue 1 Rev. 0.1

430 of 492

7: Application Agent Alarms

7.6.38

DRAFT

Server Monitor (SMU) Alarms

Alarm 1992700
Specific Problem

1992700

Managed Object

SMU

Description

ovspmd managed process (<process name>) has terminated


unexpectedly

Additional
Information

<process name>

Severity

Major

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

Yes; by ovresume completed without errors, ovspmd resumed


process (<$4>) outside os the control of the ovresume

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.39

Alarm 1992804
Specific Problem

1992804

Managed Object

SMU

Description

Reporting system error: <event description> Details: <failure


details>

Additional
Information

Report System

Severity

Major

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.40

Alarm 1992805
Specific Problem

1992805

Managed Object

SMU

Description

HP OpenView Data Warehouse is down:<event description>.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

431 of 492

7: Application Agent Alarms

DRAFT

Server Monitor (SMU) Alarms

Additional
Information

Data Warehouse

Severity

Major

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

Yes; by HP OpenView Data Warehouse is back up

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.41

Alarm 1992829
Specific Problem

1992829

Managed Object

SMU

Description

<event description>

Additional
Information

<source of the event>

Severity

Major

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

No

System Impact

HP OVO error; system monitoring may not work

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.42

Alarm 1992830
Specific Problem

1992830

Managed Object

SMU

Description

<event description>

Additional
Information

<source of the event>

Severity

Critical

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

No

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

432 of 492

7: Application Agent Alarms

DRAFT

Server Monitor (SMU) Alarms

System Impact

HP OVO fatal error; System monitoring failure.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.43

Alarm 1992832
Specific Problem

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

Additional
Information

<source of the event>

Severity

Major

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

No

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.44

Alarm 1992965
Specific Problem

1992965

Managed Object

SMU

Description

Node down

Additional
Information

<node name>

Severity

Critical

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

Yes; by Node Up

System Impact

Node services down.

Recommended
Corrective Action

Restart the node unit.

For a detailed description of these rows, see Alarm Fields Description, Page 7.
SMSC 4.2 Alarm Reference Manual
P/N 10-000-1050 Issue 1 Rev. 0.1

433 of 492

7: Application Agent Alarms

7.6.45

DRAFT

Server Monitor (SMU) Alarms

Alarm 1992972
Specific Problem

1992972

Managed Object

SMU

Description

<The string to display>

Additional
Information

<source of the event>

Severity

Normal

Message Group
(Probable Cause)

Miscellaneous

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.46

Alarm 1992973
Specific Problem

1992973

Managed Object

SMU

Description

<The string to display>

Additional
Information

<source of the event>

Severity

Normal

Message Group
(Probable Cause)

Miscellaneous

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.47

Alarm 1992974
Specific Problem

1992974

Managed Object

SMU

Description

<The string to display>

Additional
Information

<source of the event>

Severity

Normal

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

434 of 492

7: Application Agent Alarms

DRAFT

Message Group
(Probable Cause)

Miscellaneous

Alarm Automatically
Cleared

No

Server Monitor (SMU) Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.48

Alarm 1993097
Specific Problem

1993097

Managed Object

SMU

Description

Bad ARP cache entry for <cache entry>

Additional
Information

<bad cache entry>

Severity

Minor

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

No

System Impact

Connectivity problems because of invalid physical IP in ARP


cache.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.49

Alarm 1993098
Specific Problem

1993098

Managed Object

SMU

Description

Bad physical address <IP address> returned from node.

Additional
Information

<IP address>

Severity

Minor

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

No

System Impact

Connectivity problems because of invalid physical IP returned


from a node via SNMP.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

435 of 492

7: Application Agent Alarms

7.6.50

DRAFT

Server Monitor (SMU) Alarms

Alarm 1993101
Specific Problem

1993101

Managed Object

SMU

Description

<Node name with incorrect entry> reports address <incorrect


IP address> for <interface IP address>, <node name>
reported <correct IP address> via SNMP

Additional
Information

<interface name>

Severity

Minor

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

No

System Impact

This could represent a duplicate IP that impacts the network


system.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.51

Alarm 1993102
Specific Problem

1993102

Managed Object

SMU

Description

<node name1> reports a different physical address for <node


name> than reported by <node name2>, changing from <old
IP address> to <new IP address>

Additional
Information

<interface IP address>

Severity

Minor

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

No

System Impact

This could represent a duplicate IP that impacts the network


system.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.52

Alarm 1993108

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

436 of 492

7: Application Agent Alarms

DRAFT

Server Monitor (SMU) Alarms

Specific Problem

1993108

Managed Object

SMU

Description

Incorrect routing to node <node name>

Additional
Information

<node name>

Severity

Minor

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.53

Alarm 1993115
Specific Problem

1993115

Managed Object

SMU

Description

Duplicate IP address: node <node name> reported having


<IP address>, but this address was previously detected on
node <node name where IP address is configured>

Additional
Information

<IP address>

Severity

Critical

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

No

System Impact

Duplicate IP address; network impact

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.54

Alarm 1993117
Specific Problem

1993117

Managed Object

SMU

Description

Possible device reconfiguration. Interface to IfIndex have


been remapped. You may need to reconfigure any data
collection on <node name>. The new interface mappings are:
<mapping description>

Additional
Information

<mapping description>

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

437 of 492

7: Application Agent Alarms

DRAFT

Severity

Normal

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

Server Monitor (SMU) Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.55

Alarm 1993122
Specific Problem

1993122

Managed Object

SMU

Description

Duplicate ifAlias value configured on different ifIndexes ignoring ifAlias on the following ifIndexes:<ifindexes names>

Additional
Information

<ifindexes names>

Severity

Major

Message Group
(Probable Cause)

Hardware

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.56

Alarm 1993236
Specific Problem

1993236

Managed Object

SMU

Description

<application name>: <alert class>: <alert message>

Additional
Information

<source of the event>

Severity

Minor

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.57

Alarm 1993458

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

438 of 492

7: Application Agent Alarms

DRAFT

Server Monitor (SMU) Alarms

Specific Problem

1993458

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>

Additional
Information

<application name>

Severity

Major

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

Yes; by ovresume completed without errors, ovspmd resumed


process (<$4>) outside os the control of the ovresume

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.58

Alarm 1993466
Specific Problem

1993466

Managed Object

SMU

Description

pmd detected an event storm of <number of events> events


over the past <time interval> seconds (<event rate> events
per second \> threshold of <threshold value>). <total number
of events> events have been sent since the pmd was started.

Additional
Information

pmd

Severity

Major

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

No

System Impact

System performance may be degraded due to event storm.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.59

Alarm 1993600
Specific Problem

1993600

Managed Object

SMU

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

439 of 492

7: Application Agent Alarms

DRAFT

Server Monitor (SMU) Alarms

Description

ovpause failed with errors - <message text>

Additional
Information

ovpause

Severity

Major

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

No

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.60

Alarm 1993605
Specific Problem

1993605

Managed Object

SMU

Description

ovresume completed with errors - <message text>

Additional
Information

ovresume

Severity

Major

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

Yes; by ovresume completed without errors

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.61

Alarm 1993802
Specific Problem

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>

Additional
Information

Data Warehouse

Severity

Warning

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

440 of 492

7: Application Agent Alarms

DRAFT

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

No

Server Monitor (SMU) Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.62

Alarm 1994001
Specific Problem

1994001

Managed Object

SMU

Description

SMU events download terminated successfully

Severity

Cleared (Normal)

Message Group
(Probable Cause)

Backup

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.63

Alarm 1994002
Specific Problem

1994002

Managed Object

SMU

Description

SMU events download terminated with errors on <date>. Log


file is: /backup/ICCeventsDownload.log

Severity

Major

Message Group
(Probable Cause)

Backup

Alarm Automatically
Cleared

Yes; by 1994001

System Impact

Possible impacts:

Recommended
Corrective Action

No NNM events backup.


No alarm history backup.

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.64

Alarm 1994003

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

441 of 492

7: Application Agent Alarms

DRAFT

Server Monitor (SMU) Alarms

Specific Problem

1994003

Managed Object

SMU

Description

SMU backup terminated successfully

Severity

Cleared (Normal)

Message Group
(Probable Cause)

Backup

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.65

Alarm 1994004
Specific Problem

1994004

Managed Object

SMU

Description

SMU backup terminated with errors on <date>. Log file is:


/backup/ICCbackup.log

Severity

Major

Message Group
(Probable Cause)

Backup

Alarm Automatically
Cleared

Yes; by 1994003

System Impact

Possible impacts:

Recommended
Corrective Action

No SMU database backup.


No SMU configuration files backup.

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.66

Alarm log only (Node Up)


Specific Problem

log only

Managed Object

SMU

Description

Node Up

Additional
Information

<node name>

Severity

Normal

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

442 of 492

7: Application Agent Alarms

DRAFT

Message Group
(Probable Cause)

log only

Alarm Automatically
Cleared

No

Server Monitor (SMU) Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.67

Alarm log only (ovpause completed without errors)


Specific Problem

log only

Managed Object

SMU

Description

ovpause completed without errors

Severity

Normal

Additional
Information

<object name>

Message Group
(Probable Cause)

log only

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.68

Alarm log only (ovresume completed without errors)


Specific Problem

log only

Managed Object

SMU

Description

ovresume completed without errors

Severity

Normal

Additional
Information

<object name>

Message Group
(Probable Cause)

log only

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.69

Alarm log only (ovspmd resumed process (<process


name>) outside os the control of the ovresume)
Specific Problem

log only

Managed Object

SMU

Description

ovspmd resumed process (<process name>) outside os the


control of the ovresume

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

443 of 492

7: Application Agent Alarms

DRAFT

Severity

Normal

Additional
Information

<object name>

Message Group
(Probable Cause)

log only

Alarm Automatically
Cleared

No

Server Monitor (SMU) Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.70

Alarm log only (Process (<process name>) resumed


itself after timing out and after ovpause/ovresume
has completed.)
Specific Problem

log only

Managed Object

SMU

Description

Process (<process name>) resumed itself after timing out


and after ovpause/ovresume has timed completed.

Severity

Normal

Additional
Information

<object name>

Message Group
(Probable Cause)

log only

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.6.71

Alarm log only (HP OpenView Data Warehouse is


back up)
Specific Problem

log only

Managed Object

SMU

Description

HP OpenView Data Warehouse is back up

Severity

Normal

Additional
Information

<event sequence number>

Message Group
(Probable Cause)

log only

Alarm Automatically
Cleared

No

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

444 of 492

7: Application Agent Alarms

DRAFT

Server Monitor (SMU) Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

445 of 492

7: Application Agent Alarms

7.7

DRAFT

SPM Agent Alarms

SPM Agent Alarms


Search for the alarm you need by its Specific Problem (Alarm ID).

7.7.1

Alarm 1700001
Specific Problem

1700001

Managed Object

SPMA

Description

Initialization failure

Additional
Information

<Exception information>

Severity

Critical

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

No

System Impact

The SPM Agent will not run; domain and batch provisioning
are disabled.

Recommended
Corrective Action

The SPM Agent failed to initialize. Fix the problem detailed


in the exception information.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.7.2

Alarm 1700002
Specific Problem

1700002

Managed Object

SPMA

Description

Data store connection failure

Additional
Information

MIP: <hostname>
or
LDAP: <hostname>
or
DB: <hostname>

Severity

Major

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

Yes; by 1700002

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

446 of 492

7: Application Agent Alarms

DRAFT

SPM Agent Alarms

System Impact

Domain and batch provisioning will be disabled.

Recommended
Corrective Action

The SPM Agent could not connect to a data store for


five times. Check the database specified in the additional
information.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.7.3

Alarm 1701001
Specific Problem

1701001

Managed Object

SPMA

Description

Possible data integrity problem

Additional
Information

<Detailed information>

Severity

Warning

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

No

System Impact

Possible data integrity problems of the provisioned entity.


A provisioning command might have caused data integrity
problems between data stores of the provisioned entity.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.7.4

Alarm 1701002
Specific Problem

1701002

Managed Object

SPMA

Description

Unable to send HTTP request

Additional
Information

URL: <full URL>

Severity

Major

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

Yes; by 1701002

System Impact

Domain provisioning commands will be disabled.

Recommended
Corrective Action

The SPM Agent could not send an HTTP request to the


specified URL for three times. Check the URL is correct and
the server is up.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

447 of 492

7: Application Agent Alarms

DRAFT

SPM Agent Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.7.5

Alarm 1702001
Specific Problem

1702001

Managed Object

SPMA

Description

Batch file operation error

Additional
Information

<Exceptional information>

Severity

Major

Message Group
(Probable Cause)

OS

Alarm Automatically
Cleared

Yes; by 1702001

System Impact

Batch provisioning fails.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.7.6

Alarm 1702002
Specific Problem

1702002

Managed Object

SPMA

Description

Active ToDormant operation error

Additional
Information

<Detailed information>

Severity

Major

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

Yes; by 1702002

System Impact

Active ToDormant operation failed

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

448 of 492

7: Application Agent Alarms

7.8

DRAFT

SMSC Alarms

SMSC Alarms
SMSC Alarms are generated by the SMU towards the customers NOC. If the SMU
is 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. Termination


reason is UNPLANNED.)
Specific Problem

1140001

Managed Object

Others

Description

Component down. Termination reason is unplanned

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Major

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

Yes; by 1140001

System Impact

The stopped process is not used in the system

Recommended
Corrective Action

Contact Comverse customer support

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.2

Alarm 1140001 (Component up. Role is UNKNOWN.)


Specific Problem

1140001

Managed Object

Others

Description

Component up. Role is unknown

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Normal

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

No

System Impact

No impact

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

449 of 492

7: Application Agent Alarms

7.8.3

DRAFT

SMSC Alarms

Alarm 1140001 (smsCompDownUnknown.


Component down. Termination reason is
UNKNOWN)
Specific Problem

1140001

Managed Object

Others

Description

smsCompDownUnknown. Component down. Termination


reason is unknown.

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Warning

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

Yes; by 1140001

System Impact

No impact

Recommended
Corrective Action

Contact Comverse customer support

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.4

Alarm 1140001 (Log only) (Component up. Role is


ACTIVE.)
Specific Problem

1140001 (Log only)

Managed Object

Others

Description

Component up. Role is active.

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Normal

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

No

System Impact

The new SMSC process joins the system

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.5

Alarm 1140001 (Log only) (Component up. Role is


CLUSTERED.)
Specific Problem

1140001 (Log only)

Managed Object

Others

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

450 of 492

7: Application Agent Alarms

DRAFT

Description

Component up. Role is clustered

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Normal

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

No

System Impact

No impact

SMSC Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.6

Alarm 1140001 (Log only) (Component up. Role is


STANDALONE.)
Specific Problem

1140001 (Log only)

Managed Object

Others

Description

Component up. Role is standalone

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Normal

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

No

System Impact

The new SMSC process joins the system

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.7

Alarm 1140001 (Log only) (Component up. Role is


STANDBY.)
Specific Problem

1140001 (Log only)

Managed Object

Others

Description

Component up. Role is standby

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Normal

Message Group
(Probable Cause)

Application

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

451 of 492

7: Application Agent Alarms

DRAFT

Alarm Automatically
Cleared

No

System Impact

The new SMSC process joins the system

SMSC Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.8

Alarm 1140001 (Log only) (smsCompDownPlanned.


Component down. Termination reason is PLANNED).
Specific Problem

1140001 (Log only)

Managed Object

Others

Description

smsCompDownPlanned. Component down. Termination


reason is PLANNED.

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Normal

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

No

System Impact

The stopped process is not used in the system.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.9

Alarm 1140002 (Component changed role to


ACTIVE.)
Specific Problem

1140002

Managed Object

Others

Description

Component changed role to active.

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Warning

Message Group
(Probable Cause)

High Availability

Alarm Automatically
Cleared

Yes; by 1140001

System Impact

The active SFE becomes a standby SFE and vice versa.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

452 of 492

7: Application Agent Alarms

7.8.10

DRAFT

SMSC Alarms

Alarm 1140002 (Component changed role to


CLUSTERED.)
Specific Problem

1140002

Managed Object

Others

Description

Component changed role to clustered.

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Warning

Message Group
(Probable Cause)

High Availability

Alarm Automatically
Cleared

Yes; by 1140001

System Impact

No impact.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.11

Alarm 1140002 (Component changed role to


STANDALONE.)
Specific Problem

1140002

Managed Object

Others

Description

Component changed role to standalone.

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Warning

Message Group
(Probable Cause)

High Availability

Alarm Automatically
Cleared

Yes; by 1140001

System Impact

No impact.

Recommended
Corrective Action

Contact Comverse customer support.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.12

Alarm 1140002 (Component changed role to


STANDBY.)
Specific Problem

1140002

Managed Object

Others

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

453 of 492

7: Application Agent Alarms

DRAFT

SMSC Alarms

Description

Component changed role to standby

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Warning

Message Group
(Probable Cause)

High Availability

Alarm Automatically
Cleared

Yes; by 1140001

System Impact

The active SFE becomes a standby SFE and vice versa

Recommended
Corrective Action

Contact Comverse customer support

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.13

Alarm 1140002 (Component changed role to


UNKNOWN.)
Specific Problem

1140002

Managed Object

Others

Description

Component changed role to unknown

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Warning

Message Group
(Probable Cause)

High Availability

Alarm Automatically
Cleared

Yes; by 1140001

System Impact

No impact

Recommended
Corrective Action

Contact Comverse customer support

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.14

Alarm 1140003 (A message burst was encountered


on <name>. Burst size is <burstCurrentSize>.)
Specific Problem

1140003

Managed Object

Others

Description

A message burst was encontered on <name>. Burst size is


<burstCurrentSize>

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Major

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

454 of 492

7: Application Agent Alarms

DRAFT

SMSC Alarms

Message Group
(Probable Cause)

Performance

Alarm Automatically
Cleared

Yes; by 1140001

Threshold

Severity determined subjectively according to the varbind


name

System Impact

Performance impact is possible due to the traffic load

Recommended
Corrective Action

Contact Comverse customer support

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.15

Alarm 1140003 (A message burst was encountered.


Burst size is <burstCurrentSize>.)
Specific Problem

1140003

Managed Object

Others

Description

A message burst was encountered. Burst size is


<burstCurrentSize>

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Major

Message Group
(Probable Cause)

Performance

Alarm Automatically
Cleared

Yes; by 1140001

System Impact

Performance impact is possible due to the traffic load

Recommended
Corrective Action

Contact Comverse customer support

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.16

Alarm 1140003 (A message burst was encountered


on <name>. Burst size is <burstCurrentSize>.)
Specific Problem

1140003

Managed Object

Others

Description

A message burst was encountered on <name>. Burst size


is <burstCurrentSize>

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

455 of 492

7: Application Agent Alarms

Severity

DRAFT

SMSC Alarms

Critical
Minor
Warning

Message Group
(Probable Cause)

Performance

Alarm Automatically
Cleared

Yes; by 1140001

Threshold

Severity determined subjectively according to the varbind


name

System Impact

Performance impact is possible due to the traffic load.

Recommended
Corrective Action

Contact Comverse customer support

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.17

Alarm 1140003 (A message burst was encountered.


Burst size is <burstCurrentSize>.)
Specific Problem

1140003

Managed Object

Others

Description

A message burst was encountered. Burst size is


<burstCurrentSize>

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Critical
Minor
Warning

Message Group
(Probable Cause)

Performance

Alarm Automatically
Cleared

Yes; by 1140001

System Impact

Performance impact is possible due to the traffic load

Recommended
Corrective Action

Contact Comverse customer support

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.18

Alarm 1140003 (Log only)


Specific Problem

1140003 (Log only)

Managed Object

Others

Description

Burst is terminated

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

456 of 492

7: Application Agent Alarms

DRAFT

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Normal

Message Group
(Probable Cause)

Performance

Alarm Automatically
Cleared

No

System Impact

No impact

SMSC Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.19

Alarm 1140004 (Component message rate for license


<name> has reached <percent>%.)
Specific Problem

1140004

Managed Object

Others

Description

Component message rate for license <name> has reached


<percent>%.

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Critical
Major
Minor
Warning

Message Group
(Probable Cause)

Capacity

Alarm Automatically
Cleared

Yes; by 1140001

Threshold

Warning: > 60 (default)


Minor: > 70 (default)
Major: > 80 (default)
Critical: > 90 (default)

System Impact

Performance impact is possible due to the traffic load

Recommended
Corrective Action

Contact Comverse customer support

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

457 of 492

7: Application Agent Alarms

7.8.20

DRAFT

SMSC Alarms

Alarm 1140004 (Component message rate for license


<name> has reached maximum.)
Specific Problem

1140004

Managed Object

Others

Description

Component message rate for license <name> has reached


maximum

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Critical

Message Group
(Probable Cause)

Capacity

Alarm Automatically
Cleared

Yes; by 1140001

Threshold

100 (default)

System Impact

Performance impact is possible due to the traffic load

Recommended
Corrective Action

Contact Comverse customer support

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.21

Alarm 1140004 (Component message rate for license


<name> is <percent>%.)
Specific Problem

1140004

Managed Object

Others

Description

Component message rate for license <name> is <percent>%

Severity

Unknown

Alarm Automatically
Cleared

No

System Impact

Performance impact is possible due to the traffic load

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.22

Alarm 1140004 (Log only)


Specific Problem

1140004 (Log only)

Managed Object

Others

Description

Component message rate for license <name> is <percent>%

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

458 of 492

7: Application Agent Alarms

DRAFT

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Normal

Message Group
(Probable Cause)

Capacity

Alarm Automatically
Cleared

No

Threshold

<60 (default)

System Impact

No impact

SMSC Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.23

Alarm 1140005
Specific Problem

1140005

Managed Object

Others

Description

Component successful delivery rate is: <percent>%

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Critical
Major
Minor
Warning
Unknown

Message Group
(Probable Cause)

Capacity

Alarm Automatically
Cleared

No

Threshold

Warning: > 60 (default)


Minor: > 70 (default)
Major: > 80 (default)
Critical: > 90 (default)

System Impact

If <compIdClassFrom>:<compIdInstanceFrom>,
Performance impact is possible due to the traffic load

Recommended
Corrective Action

If <compIdClassFrom>:<compIdInstanceFrom>, Contact
Comverse customer support

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

459 of 492

7: Application Agent Alarms

7.8.24

DRAFT

SMSC Alarms

Alarm 1140005 (Log only)


Specific Problem

1140005 (Log only)

Managed Object

Others

Description

Component successful delivery rate is: <percent>%

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Normal

Message Group
(Probable Cause)

Capacity

Alarm Automatically
Cleared

No

Threshold

<60 (default)

System Impact

No impact

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.25

Alarm 1140006 (Disconnected from


<compIdClassTo> <compIdInstanceTo>
<currentCount> out of <*.totalCount> connections
are up.)
Specific Problem

1140006

Managed Object

Others

Description

Disconnected from <compIdClassTo> <compIdInstanceTo>.


<currentCount> out of <*.totalCount> connections are up

Severity

Unknown

Alarm Automatically
Cleared

No

System Impact

Disconnections in the system might cause service block or


performance impact

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.26

Alarm 1140006 (Disconnected from


<compIdClassTo>:<compIdInstanceTo>.)
Specific Problem

1140006

Managed Object

Others

Description

Disconnected from <compIdClassTo>:<compIdInstanceTo>.

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

460 of 492

7: Application Agent Alarms

Severity

DRAFT

SMSC Alarms

Critical
Major
Minor
Warning

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

Yes; by 11400011140001

Threshold

Severity determined both subjectively by the cardinality of the


bonds between the components (as defined in varbinds $4
and $5) and individually based on client demands

System Impact

Disconnections in the system might cause service block or


performance impact

Recommended
Corrective Action

Contact Comverse customer support

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.27

Alarm 1140006 (Log only)


Specific Problem

1140006 (Log only)

Managed Object

Others

Description

Established connection with


<compIdClassTo>:<compIdInstanceTo>.

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Normal

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

No

System Impact

No impact

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.28

Alarm 1140007
Specific Problem

1140007

Managed Object

Others

Description

The connection to <compIdClassTo>:<compIdInstanceTo>


is blocked

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

461 of 492

7: Application Agent Alarms

DRAFT

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Critical

SMSC Alarms

Major
Minor
Warning
Unknown
Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

No

Threshold

Warning: > Severity determined both subjectively by the


cardinality of the bonds between the components (as defined
in varbinds $4 and $5) and individually based on client
demands

System Impact

If <compIdClassFrom>:<compIdInstanceFrom>,
Disconnections in the system might cause service block or
performance impact

Recommended
Corrective Action

If <compIdClassFrom>:<compIdInstanceFrom>, Contact
Comverse customer support

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.29

Alarm 1140007 (Log only)


Specific Problem

1140007 (Log only)

Managed Object

Others

Description

The connection to <compIdClassTo>:<compIdInstanceTo>


is unblocked.

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Normal

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

No

Threshold

Severity determined both subjectively by the cardinality of the


bonds between the components (as defined in varbinds $4
and $5) and individually based on client demands

System Impact

No impact

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

462 of 492

7: Application Agent Alarms

7.8.30

DRAFT

SMSC Alarms

Alarm 1140008 (The connection focus to


<compIdClassTo>:<compIdInstanceTo> switched
to ACTIVE.)
Specific Problem

1140008

Managed Object

Others

Description

The connection focus to


<compIdClassTo>:<compIdInstanceTo>
switched to ACTIVE.

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Warning

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

Yes; by 1140001

System Impact

No impact

Recommended
Corrective Action

Contact Comverse customer support

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.31

Alarm 1140008 (The connection focus to


<compIdClassTo>:<compIdInstanceTo>switched to
STANDALONE.)
Specific Problem

1140008

Managed Object

Others

Description

The connection focus to


<compIdClassTo>:<compIdInstanceTo>
switched to STANDALONE.

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Warning

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

Yes; by 1140001

System Impact

No impact

Recommended
Corrective Action

Contact Comverse customer support

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

463 of 492

7: Application Agent Alarms

7.8.32

DRAFT

SMSC Alarms

Alarm 1140008 (The connection focus to


<compIdClassTo>:<compIdInstanceTo> switched
to STANDBY.)
Specific Problem

1140008

Managed Object

Others

Description

The connection focus to


<compIdClassTo>:<compIdInstanceTo>
switched to STANDBY.

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Warning

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

Yes; by 1140001

System Impact

No impact

Recommended
Corrective Action

Contact Comverse customer support

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.33

Alarm 1140008 (The connection focus to


<compIdClassTo>:<compIdInstanceTo>switched to
UNKNOWN.)
Specific Problem

1140008

Managed Object

Others

Description

The connection focus to


<compIdClassTo>:<compIdInstanceTo>
switched to UNKNOWN

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Warning

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

Yes; by 1140001

System Impact

No impact

Recommended
Corrective Action

Contact Comverse customer support

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

464 of 492

7: Application Agent Alarms

7.8.34

DRAFT

SMSC Alarms

Alarm 1140009 (The capacity of the dialog-table


in front of <compIdClassTo><compIdInstanceTo>
reached <percent>%.)
Specific Problem

1140009

Managed Object

Others

Description

The capacity of the dialog-table in front of <compIdClassTo>


<compIdInstanceTo> reached <percent>%

Severity

Unknown

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.35

Alarm 1140009 (The capacity


of the dialog-table in front of
<compIdClassTo>:<compIdInstanceTo>reached
<percent>%.)
Specific Problem

1140009

Managed Object

Others

Description

The capacity of the dialog-table in front of


<compIdClassTo>:<compIdInstanceTo> reached
<percent>%

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Critical
Major
Minor
Warning

Message Group
(Probable Cause)

Capacity

Alarm Automatically
Cleared

Yes; by 1140001

Threshold

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

Warning: > 60 (default)


Minor: > 70 (default)
Major: > 80 (default)
Critical: > 90 (default)

465 of 492

7: Application Agent Alarms

DRAFT

SMSC Alarms

System Impact

Blocking one or more of the dialog tables in the system might


cause service block or performance impact

Recommended
Corrective Action

Contact Comverse customer support

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.36

Alarm 1140009 (Log only)


Specific Problem

1140009 (Log only)

Managed Object

Others

Description

The capacity of the dialog-table in front of


<compIdClassTo>:<compIdInstanceTo> reached
<percent>%

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Normal

Message Group
(Probable Cause)

Capacity

Alarm Automatically
Cleared

No

Threshold

<60 (default)

System Impact

Blocking one or more of the dialog tables in the system might


cause service block or performance impact

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.37

Alarm 1140010 (The Capacity of the DB-table


<dbName> reached <percent>%.)
Specific Problem

1140010

Managed Object

Others

Description

The Capacity of the DB-table <dbName> reached <percent>%

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Critical
Major
Minor
Warning

Message Group
(Probable Cause)

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

Database

466 of 492

7: Application Agent Alarms

DRAFT

Alarm Automatically
Cleared

Yes; by 1140001

Threshold

SMSC Alarms

Warning: > 60 (default)


Minor: > 70 (default)
Major: > 80 (default)
Critical: > 90 (default)

System Impact

Messages DB utilization might cause service block or


performance impact

Recommended
Corrective Action

Contact Comverse customer support

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.38

Alarm 1140010 (The DB-table <dbName> reached


its full capacity.)
Specific Problem

1140010

Managed Object

Others

Description

The DB-table <dbName> reached its full capacity

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Critical

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 1140001

Threshold

100 (default)

System Impact

Messages DB utilization might cause service block or


performance impact

Recommended
Corrective Action

Contact Comverse customer support

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.39

Alarm 1140010 (Log only)


Specific Problem

1140010 (Log only)

Managed Object

Others

Description

The Capacity of the DB-table <dbName> reached <percent>%

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Normal

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

467 of 492

7: Application Agent Alarms

DRAFT

SMSC Alarms

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

No

Threshold

<60 (default)

System Impact

Messages DB utilization might cause service block or


performance impact

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.40

Alarm 1140011
Specific Problem

1140011

Managed Object

Others

Description

An integrity problem was discovered in the DB-table


<dbName>

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Major

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 1140001

System Impact

No impact

Recommended
Corrective Action

Contact Comverse customer support

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.41

Alarm 1140012
Specific Problem

1140012

Managed Object

Others

Description

<eventMessage>

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Critical
Major
Minor
Warning

Message Group
(Probable Cause)

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

Application

468 of 492

7: Application Agent Alarms

DRAFT

SMSC Alarms

Alarm Automatically
Cleared

Yes; by 1140001

Threshold

Severity determined subjectively by the alarm, as defined by


client demands

System Impact

No impact

Recommended
Corrective Action

Contact Comverse customer support

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.42

Alarm 1140012 (Log only)


Specific Problem

1140012 (Log only)

Managed Object

Others

Description

<eventMessage>.

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Normal

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

No

Threshold

Severity determined subjectively by the alarm, as defined by


client demands

System Impact

No impact

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.43

Alarm 1140013
Specific Problem

1140013

Managed Object

Others

Description

The CIC-table capacity reached <percent>%

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Critical
Major
Minor
Warning

Message Group
(Probable Cause)

Capacity

Alarm Automatically
Cleared

Yes; by 1140001

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

469 of 492

7: Application Agent Alarms

Threshold

DRAFT

SMSC Alarms

Warning: > 60 (default)


Minor: > 70 (default)
Major: > 80 (default)
Critical: > 90 (default)

System Impact

No impact

Recommended
Corrective Action

Contact Comverse customer support

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.44

Alarm 1140013 (Log only)


Specific Problem

1140013 (Log only)

Managed Object

Others

Description

The CIC-table capacity reached <percent>%.

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Normal

Message Group
(Probable Cause)

Capacity

Alarm Automatically
Cleared

No

Threshold

<60 (default)

System Impact

No impact

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.45

Alarm 1140014
Specific Problem

1140014

Managed Object

Others

Description

A Trace-file loading failure occurred at: <date>. Cause:


<eventMessage>.

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Critical
Major
Minor
Warning

Message Group
(Probable Cause)

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

Application

470 of 492

7: Application Agent Alarms

DRAFT

SMSC Alarms

Alarm Automatically
Cleared

Yes; by 1140001

Threshold

Severity determined subjectively by the alarm, as defined by


client demands

System Impact

No impact

Recommended
Corrective Action

Contact Comverse customer support

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.46

Alarm 1140015
Specific Problem

1140015

Managed Object

Others

Description

The connections between


<compIdClassFrom>:<compIdInstanceFrom>
and <compIdClassTo>:<compIdInstanceTo> timed out on
<count> occasions within <timeFrame> seconds

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Critical
Major
Minor
Warning

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

Yes; by 1140001

Threshold

Severity determined both subjectively by the cardinality of the


bonds between the components (as defined in varbinds $4
and $5) and individually based on client demands

System Impact

No impact

Recommended
Corrective Action

Contact Comverse customer support

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.47

Alarm 1140015 (Log only)


Specific Problem

1140015 (Log only)

Managed Object

Others

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

471 of 492

7: Application Agent Alarms

DRAFT

SMSC Alarms

Description

The connections between


<compIdClassFrom>:<compIdInstanceFrom>
and <compIdClassTo>:<compIdInstanceTo> timed out on
<count> occasions within <timeFrame> seconds

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Normal

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

No

Threshold

Severity determined both subjectively by the cardinality of the


bonds between the components (as defined in varbinds $4
and $5) and individually based on client demands

System Impact

No impact

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.48

Alarm 1140016
Specific Problem

1140016

Managed Object

Others

Description

The connection utilization between


<compIdClassFrom>:<compIdInstanceFrom> and
<compIdClassTo>:<compIdInstanceTo> reached <percent>%.

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Critical
Major
Minor
Warning

Message Group
(Probable Cause)

Capacity

Alarm Automatically
Cleared

Yes; by 1140001

Threshold

Critical: > 60 (default)


Major: > 70 (default)
Minor: > 80 (default)
Warning: > 90 (default)

System Impact

No impact

Recommended
Corrective Action

Contact Comverse customer support

For a detailed description of these rows, see Alarm Fields Description, Page 7.
SMSC 4.2 Alarm Reference Manual
P/N 10-000-1050 Issue 1 Rev. 0.1

472 of 492

7: Application Agent Alarms

7.8.49

DRAFT

SMSC Alarms

Alarm 1140016 (Log only)


Specific Problem

1140016 (Log only)

Managed Object

Others

Description

The connection utilization between


<compIdClassFrom>:<compIdInstanceFrom> and
<compIdClassTo>:<compIdInstanceTo> reached <percent>%.

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Normal

Message Group
(Probable Cause)

Capacity

Alarm Automatically
Cleared

No

Threshold

<60 (default)

System Impact

No impact

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.50

Alarm 1140017
Specific Problem

1140017

Managed Object

Others

Description

The DB-table <dbName> was identified as not being the most


up-to-date.

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Critical
Major
Minor
Warning

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

Yes; by 1140001

Threshold

Severity determined subjectively by the DB name

System Impact

No impact

Recommended
Corrective Action

Contact Comverse customer support

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

473 of 492

7: Application Agent Alarms

7.8.51

DRAFT

SMSC Alarms

Alarm 1140017 (Log only)


Specific Problem

1140017 (Log only)

Managed Object

Others

Description

The DB-table <dbName> was identified as not being the most


up-to-date.

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Normal

Message Group
(Probable Cause)

Database

Alarm Automatically
Cleared

No

Threshold

Severity determined subjectively by the DB name.

System Impact

No impact.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.52

Alarm 1141001 (SMS component down due to


failure.)
Specific Problem

1141001

Managed Object

Others

Description

SMS component down due to failure.

Severity

Major

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.53

Alarm 1141001 (SMS component down for


maintenance.)
Specific Problem

1141001

Managed Object

Others

Description

SMS component down for maintenance.

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

474 of 492

7: Application Agent Alarms

7.8.54

DRAFT

SMSC Alarms

Alarm 1141002
Specific Problem

1141002

Managed Object

Others

Description

SMS node failure

Severity

Major

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.55

Alarm 1141006 (Disconnected from


<compIdClassTo> <compIdInstanceTo>.)
Specific Problem

1141006

Managed Object

Others

Description

Disconnected from <compIdClassTo> <compIdInstanceTo>

Severity

Critical
Major
Minor
Warning
Unknown

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.56

Alarm 1141006 (Disconnected


from <compIdClassTo>
<compIdInstanceTo>.<currentCount>
out of <*.totalCount> connections are up.)
Specific Problem

1141006

Managed Object

Others

Description

Disconnected from <compIdClassTo> <compIdInstanceTo>.


<currentCount> out of <*.totalCount> connections are up

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

475 of 492

7: Application Agent Alarms

Severity

DRAFT

SMSC Alarms

Critical
Major
Minor
Warning
Unknown

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.57

Alarm 1141007
Specific Problem

1141007

Managed Object

Others

Description

The connection to <compIdClassTo> <compIdInstanceTo>


became blocked.

Severity

Critical
Major
Minor
Warning
Unknown

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.58

Alarm 1142006
Specific Problem

1142006

Managed Object

Others

Description

Disconnected from <compIdClassTo>:<compIdInstanceTo>.


Currently <currentCount> connections out of <totalCount>
are up.

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Critical
Major
Warning
Minor

Message Group
(Probable Cause)

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

Application

476 of 492

7: Application Agent Alarms

DRAFT

SMSC Alarms

Alarm Automatically
Cleared

Yes; by 1140001

Threshold

Severity determined both subjectively by the cardinality of the


bonds between the components (as defined in varbinds $4
and $5) and individually based on client demands

System Impact

Disconnections in the system might cause service block or


performance impact

Recommended
Corrective Action

Contact Comverse customer support

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.59

Alarm 1142006 (Log only)


Specific Problem

1142006 (Log only)

Managed Object

Others

Description

Established connection with


<compIdClassTo>:<compIdInstanceTo>.
Currently <currentCount> connections out of <totalCount>
are up

Additional
Information

<compIdClassFrom>:<compIdInstanceFrom>

Severity

Normal

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

No

System Impact

No impact

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.60

Alarm 1143006
Specific Problem

1143006

Managed Object

Others

Description

Application is out of connections to <compIdClassTo>


<compIdInstanceTo>

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

477 of 492

7: Application Agent Alarms

Severity

DRAFT

SMSC Alarms

Critical
Major
Minor
Normal
Warning
Unknown

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.61

Alarm 1410002 (Association is down <association


name>.)
Specific Problem

1410002

Managed Object

Others

Description

Association is down <association name>

Severity

Warning

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.62

Alarm 1410002 (Link <number> <name> failed.)


Specific Problem

1410002

Managed Object

Others

Description

Link <number> <name> failed.

Severity

Warning

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.63

Alarm 1410002 (Link <number> <name> not failed.)


Specific Problem

1410002

Managed Object

Others

Description

Link <number> <name> not failed.

Severity

Normal

Alarm Automatically
Cleared

No

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

478 of 492

7: Application Agent Alarms

DRAFT

SMSC Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.64

Alarm 1410003
Specific Problem

1410003

Managed Object

Others

Description

Association is up <association name>

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.65

Alarm 1410004 (Link <number> <name> local


inhibited.)
Specific Problem

1410004

Managed Object

Others

Description

Link <number> <name> local inhibited

Severity

Warning

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.66

Alarm 1410004 (Link <number> <name> not local


inhibited.)
Specific Problem

1410004

Managed Object

Others

Description

Link <number> <name> not local inhibited.

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.67

Alarm 1410006 (Link <number> <name> not remote


inhibited.)
Specific Problem

1410006

Managed Object

Others

Description

Link <number> <name> not remote inhibited.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

479 of 492

7: Application Agent Alarms

DRAFT

Severity

Normal

Alarm Automatically
Cleared

No

SMSC Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.68

Alarm 1410006 (Link <number> <name> remote


inhibited.)
Specific Problem

1410006

Managed Object

Others

Description

Link <number> <name> remote inhibited

Severity

Warning

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.69

Alarm 1410008 (Link <number> <name> not remotely


blocked.)
Specific Problem

1410008

Managed Object

Others

Description

Link <number> <name> not remotely blocked

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.70

Alarm 1410008 (Link <number> <name> remotely


blocked.)
Specific Problem

1410008

Managed Object

Others

Description

Link <number> <name> remotely blocked

Severity

Warning

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

480 of 492

7: Application Agent Alarms

7.8.71

DRAFT

SMSC Alarms

Alarm 1410010 (Link <number> <name> locally


blocked.)
Specific Problem

1410010

Managed Object

Others

Description

Link <number> <name> locally blocked

Severity

Warning

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.72

Alarm 1410010 (Link <number> <name> not locally


blocked.)
Specific Problem

1410010

Managed Object

Others

Description

Link <number> <name> not locally blocked

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.73

Alarm 1410012 (Route set <number> <name>


Accessible.)
Specific Problem

1410012

Managed Object

Others

Description

Route set <number> <name> Accessible

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.74

Alarm 1410012 (Route set <number> <name> NOT


Accessible.)
Specific Problem

1410012

Managed Object

Others

Description

Route set <number> <name> not Accessible

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

481 of 492

7: Application Agent Alarms

DRAFT

Severity

Major

Alarm Automatically
Cleared

No

SMSC Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.75

Alarm 1410014 (Route set <number> <name>


Congestion level is <level>.)
Specific Problem

1410014

Managed Object

Others

Description

Route set <number> <name> Congestion level is <level>

Severity

Warning

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.76

Alarm 1410014 (Route set <number> <name>


Congestion level is Low.)
Specific Problem

1410014

Managed Object

Others

Description

Route set <number> <name> Congestion level is Low

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.77

Alarm 1410016 (RSSN <number> RPC <number(s)>


ALLOWED.)
Specific Problem

1410016

Managed Object

Others

Description

RSSN <number> RPC <number(s)> allowed

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

482 of 492

7: Application Agent Alarms

7.8.78

DRAFT

SMSC Alarms

Alarm 1410016 (RSSN <number> RPC <number(s)>


CONGESTED.)
Specific Problem

1410016

Managed Object

Others

Description

RSSN <number> RPC <number(s)> congested

Severity

Warning

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.79

Alarm 1410016 (RSSN <number> RPC <number(s)>


PROHIBITED.)
Specific Problem

1410016

Managed Object

Others

Description

RSSN <number> RPC <number(s)> prohobited

Severity

Warning

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.80

Alarm 1410016 (RSSN <number> RPC <number(s)>


UNEQUIPPED.)
Specific Problem

1410016

Managed Object

Others

Description

RSSN <number> RPC <number(s)> unequipped

Severity

Warning

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.81

Alarm 1410017 (LSSN <number> ALLOWED.)


Specific Problem

1410017

Managed Object

Others

Description

LSSN <number> allowed

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

483 of 492

7: Application Agent Alarms

DRAFT

Severity

Normal

Alarm Automatically
Cleared

No

SMSC Alarms

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.82

Alarm 1410017 (LSSN <number> PROHIBITED.)


Specific Problem

1410017

Managed Object

Others

Description

LSSN <number> PROHIBITED.

Severity

Warning

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.8.83

Alarm 1410017 (LSSN <number> UNEQUIPPED.)


Specific Problem

1410017

Managed Object

Others

Description

LSSN <number> UNEQUIPPED.

Severity

Warning

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

484 of 492

7: Application Agent Alarms

DRAFT

7.9

Possibly Used Traps

7.9.1

GenericBackup Alarms

Possibly Used Traps

Search for the alarm you need by its Specific Problem (Alarm ID).

7.9.1.1

Alarm 2113067
Specific Problem

2113067

Managed Object

GenericBackup

Description

Generic Backup Message - Normal

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.9.1.2

Alarm 2113068
Specific Problem

2113068

Managed Object

GenericBackup

Description

Generic Backup Message - Warning

Severity

Warning

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.9.1.3

Alarm 2113069
Specific Problem

2113069

Managed Object

GenericBackup

Description

Generic Backup Message - Minor

Severity

Minor

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.9.1.4

Alarm 2113070

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

485 of 492

7: Application Agent Alarms

DRAFT

Specific Problem

2113070

Managed Object

GenericBackup

Description

Generic Backup Message - Major

Severity

Major

Alarm Automatically
Cleared

No

Possibly Used Traps

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.9.1.5

Alarm 2113071
Specific Problem

2113071

Managed Object

GenericBackup

Description

Generic Backup Message - Critical

Severity

Critical

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.9.2

GenericHardware Alarms
Search for the alarm you need by its Specific Problem (Alarm ID).

7.9.2.1

Alarm 2113072
Specific Problem

2113072

Managed Object

GenericHardware

Description

Generic Hardware Message - Normal

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.9.2.2

Alarm 2113073
Specific Problem

2113073

Managed Object

GenericHardware

Description

Generic Hardware Message - Warning

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

486 of 492

7: Application Agent Alarms

DRAFT

Severity

Warning

Alarm Automatically
Cleared

No

Possibly Used Traps

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.9.2.3

Alarm 2113074
Specific Problem

2113074

Managed Object

GenericHardware

Description

Generic Hardware Message - Minor

Severity

Minor

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.9.2.4

Alarm 2113075
Specific Problem

2113075

Managed Object

GenericHardware

Description

Generic Hardware Message - Major

Severity

Major

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.9.2.5

Alarm 2113076
Specific Problem

2113076

Managed Object

GenericHardware

Description

Generic Hardware Message - Critical

Severity

Critical

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.9.3

GenericOS Alarms
Search for the alarm you need by its Specific Problem (Alarm ID).

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

487 of 492

7: Application Agent Alarms

7.9.3.1

DRAFT

Possibly Used Traps

Alarm 2113057
Specific Problem

2113057

Managed Object

GenericOS

Description

Generic OS Message - Normal

Severity

Normal

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.9.3.2

Alarm 2113058
Specific Problem

2113058

Managed Object

GenericOS

Description

Generic OS Message - Warning

Severity

Warning

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.9.3.3

Alarm 2113059
Specific Problem

2113059

Managed Object

GenericOS

Description

Generic OS Message - Minor

Severity

Minor

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.9.3.4

Alarm 2113060
Specific Problem

2113060

Managed Object

GenericOS

Description

Generic OS Message - Major

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

488 of 492

7: Application Agent Alarms

DRAFT

Severity

Major

Alarm Automatically
Cleared

No

Possibly Used Traps

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.9.3.5

Alarm 2113061
Specific Problem

2113061

Managed Object

GenericOS

Description

Generic OS Message - Critical

Severity

Critical

Alarm Automatically
Cleared

No

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.9.4

SPM Agent Alarms


Search for the alarm you need by its Specific Problem (Alarm ID).

7.9.4.1

Alarm 1700001
Specific Problem

1700001

Managed Object

SPMA

Description

Initialization failure

Additional
Information

<Exception information>

Severity

Critical

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

No

System Impact

The SPM Agent will not run; domain and batch provisioning
will be disabled.

Recommended
Corrective Action

The SPM Agent failed to initialize. Fix the problem detailed


in the exception information.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.9.4.2

Alarm 1700002

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

489 of 492

7: Application Agent Alarms

DRAFT

Specific Problem

1700002

Managed Object

SPMA

Description

Data store connection failure

Additional
Information

MIP: <hostname>

Possibly Used Traps

or
LDAP: <hostname>
or
DB: <hostname>

Severity

Major

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

Yes; by 1700002

System Impact

Domain and batch provisioning will be disabled.

Recommended
Corrective Action

The SPM Agent could not connect to a data store for


five times. Check the database specified in the additional
information.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.9.4.3

Alarm 1701001
Specific Problem

1701001

Managed Object

SPMA

Description

Possible data integrity problem

Additional
Information

<Detailed information>

Severity

Warning

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

No

System Impact

Possible data integrity problems of the provisioned entity.


A provisioning command might have caused data integrity
problems between data stores of the provisioned entity.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.9.4.4

Alarm 1701002

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

490 of 492

7: Application Agent Alarms

DRAFT

Possibly Used Traps

Specific Problem

1701002

Managed Object

SPMA

Description

Unable to send HTTP request

Additional
Information

URL: <full URL>

Severity

Major

Message Group
(Probable Cause)

Network

Alarm Automatically
Cleared

Yes; by 1701002

System Impact

Domain provisioning commands will be disabled.

Recommended
Corrective Action

The SPM Agent could not send an HTTP request to the


specified URL for three times. Check the URL is correct and
the server is up.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.9.4.5

Alarm 1702001
Specific Problem

1702001

Managed Object

SPMA

Description

Batch file operation error

Additional
Information

<Exceptional information>

Severity

Major

Message Group
(Probable Cause)

OS

Alarm Automatically
Cleared

Yes; by 1702001

System Impact

Batch provisioning will fail.

For a detailed description of these rows, see Alarm Fields Description, Page 7.

7.9.4.6

Alarm 1702002
Specific Problem

1702002

Managed Object

SPMA

Description

Active ToDormant operation error

Additional
Information

<Detailed information>

Severity

Major

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

491 of 492

7: Application Agent Alarms

DRAFT

Message Group
(Probable Cause)

Application

Alarm Automatically
Cleared

Yes; by 1702002

System Impact

Active ToDormant operation will fail

Possibly Used Traps

For a detailed description of these rows, see Alarm Fields Description, Page 7.

SMSC 4.2 Alarm Reference Manual


P/N 10-000-1050 Issue 1 Rev. 0.1

492 of 492

You might also like