Kairos HLR Alarm Reference

Kapsch CarrierCom AG
PE/HLR/APP/027903 | Kairos HLR Alarm Reference Page 1 of 161

State released | Version 0.12 | 04.09.2014 CONFIDENTIAL
PE/HLR/APP/027903
HLR
Kairos HLR Alarm Reference

KAIROS platform
Release: HLR22
Replaces: NN10300-433

HLR
Release: HLR22
Document number: PE/HLR/APP/027903
Document release date: 04.09.2014
Copyright © 2014 Kapsch. All Rights Reserved.
The information contained in this document is the property of Kapsch CarrierCom (in the following referred to as
“Kapsch”). Except as specifically authorized in writing by Kapsch, the holder of this document shall keep the information
contained herein confidential and shall protect same in whole or in part from disclosure and dissemination to third parties
and use same for evaluation, operation and maintenance purposes only.
The content of this document is provided for information purposes only and is subject to modification. It does not
constitute any representation or warranty from Kapsch as to the content or accuracy of the information contained herein,
including but not limited to the suitability and performance of the product or its intended application.
Kapsch and the Kapsch logo are trademarks of Kapsch and/ or its licensors. All other trademarks are the property of
their owners.

Table of Contents
1 Alarm fundamentals ................................................................................................................................8
2 HLR alarms reference .............................................................................................................................9
2.1 ILLCFG ......................................................................................................................................................9
3 KAIROS alarms reference ....................................................................................................................10
3.1 AMF1300 .................................................................................................................................................10
3.2 COMFL ....................................................................................................................................................10
3.3 CisLi1300 ................................................................................................................................................11
3.4 CisLi1301 ................................................................................................................................................12
3.5 CisLi1302 ................................................................................................................................................12
3.6 CisLi1303 ................................................................................................................................................13
3.7 CisLi1304 ................................................................................................................................................13
3.8 CisLi1305 ................................................................................................................................................14
3.9 CisLi1306 ................................................................................................................................................14
3.10 CisLi1307 ................................................................................................................................................15
3.11 CisLi1308 ................................................................................................................................................15
3.12 CisLi1309 ................................................................................................................................................16
3.13 CisLi1310 ................................................................................................................................................16
3.14 DHCP1300 ..............................................................................................................................................17
3.15 DHCP1301 ..............................................................................................................................................17
3.16 DHCP1302 ..............................................................................................................................................18
3.17 HlrOamAgent1300...................................................................................................................................19
3.18 HlrOamAgent1301...................................................................................................................................20
3.19 HlrOamAgent1302...................................................................................................................................20
3.20 HlrOamAgent1303...................................................................................................................................21
3.21 HlrOamAgent1304...................................................................................................................................22
3.22 HlrOamAgent1305...................................................................................................................................22
3.23 HlrOamAgent1306...................................................................................................................................23
3.24 HlrOamAgent1307...................................................................................................................................23
3.25 HlrOamAgent1308...................................................................................................................................24
3.26 HlrOamAgent1309...................................................................................................................................25
3.27 HlrOamAgent1310...................................................................................................................................25
3.28 HlrOamAgent1311...................................................................................................................................26
3.29 HlrOamAgent1312...................................................................................................................................26
3.30 HlrOamAgent1313...................................................................................................................................27
3.31 HlrOamAgent1314...................................................................................................................................28
3.32 HlrOamAgent1315...................................................................................................................................28
3.33 HlrOamAgent1316...................................................................................................................................29
3.34 HlrOamAgent1317...................................................................................................................................29
3.35 HlrOamAgent1318...................................................................................................................................30
3.36 HlrOamAgent1320...................................................................................................................................31
3.37 HlrOamAgent1321...................................................................................................................................32
3.38 HlrOamAgent1322...................................................................................................................................32
3.39 HlrOamAgent1323...................................................................................................................................33
3.40 HlrOamAgent1324...................................................................................................................................33
3.41 HlrOamAgent1325...................................................................................................................................34
3.42 HlrOamAgent1326...................................................................................................................................35
3.43 HlrOamAgent1327...................................................................................................................................35
3.44 HlrOamAgent1329...................................................................................................................................36
3.45 HlrOamAgent1330...................................................................................................................................36
3.46 HlrOamAgent1331...................................................................................................................................37
3.47 HlrOamAgent1332...................................................................................................................................38
3.48 HlrOamAgent1333...................................................................................................................................38
3.49 HlrOamAgent1334...................................................................................................................................39

3.50 HlrOamAgent1335...................................................................................................................................40
3.51 HlrOamAgent1336...................................................................................................................................40
3.52 HlrOamAgent1337...................................................................................................................................41
3.53 HlrOamAgent1338...................................................................................................................................41
3.54 HlrOamAgent1339...................................................................................................................................42
3.55 HlrOamAgent1340...................................................................................................................................43
3.56 HlrOamAgent1341...................................................................................................................................43
3.57 HlrOamAgent1342...................................................................................................................................44
3.58 HlrOamAgent1343...................................................................................................................................44
3.59 HlrOamAgent1344...................................................................................................................................45
3.60 HlrOamAgent1345...................................................................................................................................46
3.61 HlrOamAgent1346...................................................................................................................................46
3.62 HlrOamAgent1347...................................................................................................................................47
3.63 HlrOamAgent1348...................................................................................................................................48
3.64 HlrOamAgent1349...................................................................................................................................48
3.65 HlrOamAgent1350...................................................................................................................................49
3.66 HlrOamAgent1351...................................................................................................................................50
3.67 HlrOamAgent1390...................................................................................................................................50
3.68 HlrOamAgent1399...................................................................................................................................51
3.69 Inv1312 ....................................................................................................................................................51
3.70 Inv1313 ....................................................................................................................................................52
3.71 InvAppBld1300 ........................................................................................................................................53
3.72 InvAppBld1301 ........................................................................................................................................53
3.73 InvFtm1300 .............................................................................................................................................55
3.74 InvFtm1301 .............................................................................................................................................55
3.75 InvFtm1302 .............................................................................................................................................56
3.76 InvPem1300 ............................................................................................................................................56
3.77 InvPem1301 ............................................................................................................................................57
3.78 InvPem1302 ............................................................................................................................................58
3.79 InvSam1300 ............................................................................................................................................58
3.80 InvSam1301 ............................................................................................................................................59
3.81 InvSam1302 ............................................................................................................................................59
3.82 MrfOamAgent1300 ..................................................................................................................................60
3.83 MrfOamAgent1301 ..................................................................................................................................61
3.84 MrfOamAgent1303 ..................................................................................................................................62
3.85 MrfOamAgent1304 ..................................................................................................................................63
3.86 MrfOamAgent1305 ..................................................................................................................................63
3.87 MrfOamAgent1306 ..................................................................................................................................64
3.88 MrfOamAgent1308 ..................................................................................................................................65
3.89 MrfOamAgent1309 ..................................................................................................................................66
3.90 MrfOamAgent1310 ..................................................................................................................................66
3.91 MrfOamAgent1311 ..................................................................................................................................67
3.92 MrfOamAgent1312 ..................................................................................................................................67
3.93 MrfOamAgent1313 ..................................................................................................................................68
3.94 MrfOamAgent1314 ..................................................................................................................................69
3.95 MrfOamAgent1315 ..................................................................................................................................69
3.96 MrfOamAgent1316 ..................................................................................................................................70
3.97 MrfOamAgent1317 ..................................................................................................................................70
3.98 MrfOamAgent1318 ..................................................................................................................................71
3.99 MrfOamAgent1320 ..................................................................................................................................72
3.100 MrfOamAgent1322 ..................................................................................................................................73
3.101 MrfOamAgent1323 ..................................................................................................................................74
3.102 MrfOamAgent1324 ..................................................................................................................................75
3.103 MrfOamAgent1325 ..................................................................................................................................75
3.104 MrfOamAgent1326 ..................................................................................................................................76
3.105 MrfOamAgent1327 ..................................................................................................................................76
3.106 MrfOamAgent1329 ..................................................................................................................................77

3.107 MrfOamAgent1330 ..................................................................................................................................77

3.108 MrfOamAgent1331 ..................................................................................................................................78
3.109 MrfOamAgent1332 ..................................................................................................................................79
3.110 MrfOamAgent1333 ..................................................................................................................................79
3.111 MrfOamAgent1334 ..................................................................................................................................80
3.112 MrfOamAgent1335 ..................................................................................................................................81
3.113 MrfOamAgent1336 ..................................................................................................................................81
3.114 MrfOamAgent1337 ..................................................................................................................................82
3.115 MrfOamAgent1338 ..................................................................................................................................82
3.116 MrfOamAgent1339 ..................................................................................................................................83
3.117 MrfOamAgent1340 ..................................................................................................................................84
3.118 MrfOamAgent1341 ..................................................................................................................................84
3.119 MrfOamAgent1342 ..................................................................................................................................85
3.120 MrfOamAgent1343 ..................................................................................................................................85
3.121 MrfOamAgent1344 ..................................................................................................................................86
3.122 MrfOamAgent1345 ..................................................................................................................................87
3.123 MrfOamAgent1346 ..................................................................................................................................87
3.124 MrfOamAgent1347 ..................................................................................................................................88
3.125 MrfOamAgent1348 ..................................................................................................................................89
3.126 MrfOamAgent1349 ..................................................................................................................................89
3.127 MrfOamAgent1350 ..................................................................................................................................90
3.128 MrfOamAgent1351 ..................................................................................................................................91
3.129 MrfOamAgent1390 ..................................................................................................................................91
3.130 MrfOamAgent1399 ..................................................................................................................................92
3.131 MtcAe1300 ..............................................................................................................................................92
3.132 MtcAe1301 ..............................................................................................................................................93
3.133 MtcAe1302 ..............................................................................................................................................93
3.134 MtcAe1303 ..............................................................................................................................................94
3.135 MtcAe1304 ..............................................................................................................................................94
3.136 MtcAppBld1300 .......................................................................................................................................95
3.137 MtcAppBld1301 .......................................................................................................................................96
3.138 MtcAppBld1302 .......................................................................................................................................96
3.139 MtcAppBld1303 .......................................................................................................................................97
3.140 MtcAppBld1304 .......................................................................................................................................98
3.141 MtcAppBld1305 .......................................................................................................................................98
3.142 MtcAppBld1306 .......................................................................................................................................99
3.143 MtcAppBld1307 .......................................................................................................................................99
3.144 MtcAppBld1308 .....................................................................................................................................100
3.145 MtcAppBld1309 .....................................................................................................................................101
3.146 MtcAppBld1390 .....................................................................................................................................101
3.147 MtcCpu1300 ..........................................................................................................................................102
3.148 MtcCpu1301 ..........................................................................................................................................102
3.149 MtcDisk1300..........................................................................................................................................103
3.150 MtcDisk1301..........................................................................................................................................103
3.151 MtcDisk1302..........................................................................................................................................104
3.152 MtcDisk1303..........................................................................................................................................105
3.153 MtcDisk1304..........................................................................................................................................105
3.154 MtcDisk1305..........................................................................................................................................106
3.155 MtcDisk1306..........................................................................................................................................106
3.156 MtcDisk1307..........................................................................................................................................107
3.157 MtcDisk1308..........................................................................................................................................107
3.158 MtcDisk1309..........................................................................................................................................108
3.159 MtcDisk1310..........................................................................................................................................109
3.160 MtcDisk1311..........................................................................................................................................109
3.161 MtcEth1300 ...........................................................................................................................................110
3.162 MtcEth1301 ...........................................................................................................................................110
3.163 MtcEth1302 ...........................................................................................................................................111

3.164 MtcFtm1300 ..........................................................................................................................................111

3.165 MtcFtm1301 ..........................................................................................................................................112
3.166 MtcFtm1302 ..........................................................................................................................................113
3.167 MtcMem1300.........................................................................................................................................114
3.168 MtcPem1300 .........................................................................................................................................115
3.169 MtcPem1301 .........................................................................................................................................115
3.170 MtcPem1302 .........................................................................................................................................116
3.171 MtcPem1303 .........................................................................................................................................117
3.172 MtcPem1304 .........................................................................................................................................117
3.173 MtcPem1305 .........................................................................................................................................118
3.174 MtcRAMDisk1300..................................................................................................................................118
3.175 MtcSam1300 .........................................................................................................................................119
3.176 MtcSam1301 .........................................................................................................................................120
3.177 MtcSam1302 .........................................................................................................................................120
3.178 MtcSam1303 .........................................................................................................................................121
3.179 MtcSam1304 .........................................................................................................................................121
3.180 MtcWDT1300 ........................................................................................................................................122
3.181 MtcZombie1300.....................................................................................................................................123
3.182 NTP1300 ...............................................................................................................................................123
3.183 NTP1301 ...............................................................................................................................................124
3.184 PmCentral1300 - Failed to transfer a file to a remote host ...................................................................125
3.185 SCA1300 ...............................................................................................................................................125
3.186 SCA1301 ...............................................................................................................................................126
3.187 SCA1302 ...............................................................................................................................................127
3.188 SCA1303 ...............................................................................................................................................127
3.189 SCA1304 ...............................................................................................................................................128
3.190 SCA1305 ...............................................................................................................................................128
3.191 SCA1306 ...............................................................................................................................................129
3.192 SCA1307 ...............................................................................................................................................130
3.193 SCA1308 ...............................................................................................................................................130
3.194 ScaDdm1300.........................................................................................................................................131
3.195 ScaDdm1301.........................................................................................................................................131
3.196 ScaDdm1302.........................................................................................................................................132
3.197 ScaDdm1303.........................................................................................................................................132
3.198 ScaDdm1304.........................................................................................................................................133
3.199 ScaDdm1305.........................................................................................................................................133
3.200 ScaLaq1301 ..........................................................................................................................................133
3.201 ScaLaq1302 ..........................................................................................................................................134
3.202 ScaLaq1303 ..........................................................................................................................................134
3.203 ScaLaq1304 ..........................................................................................................................................135
3.204 ScaLaq1305 ..........................................................................................................................................135
3.205 ScaOma1300 ........................................................................................................................................135
3.206 ScaOma1301 ........................................................................................................................................136
3.207 ScaOma1302 ........................................................................................................................................137
3.208 ScaOma1303 ........................................................................................................................................137
3.209 ScaOma1304 ........................................................................................................................................138
3.210 ScaOma1305 ........................................................................................................................................138
3.211 ScaOma1306 ........................................................................................................................................139
3.212 ScaOma1307 ........................................................................................................................................139
3.213 ScaTam1300 .........................................................................................................................................139
3.214 ScaTam1301 .........................................................................................................................................140
3.215 ScaTam1302 .........................................................................................................................................140
3.216 ScaTam1303 .........................................................................................................................................141
3.217 ScaTam1304 .........................................................................................................................................141
3.218 ScaTam1305 .........................................................................................................................................141
3.219 Storage1330 ..........................................................................................................................................142
3.220 Storage1331 ..........................................................................................................................................142

3.221 Storage1332 ..........................................................................................................................................143

3.222 Storage1333 ..........................................................................................................................................143
3.223 Storage1334 ..........................................................................................................................................144
3.224 Storage1335 ..........................................................................................................................................145
3.225 Storage1380 ..........................................................................................................................................145
3.226 TimeZone1300 ......................................................................................................................................146
3.227 TimeZone1301 ......................................................................................................................................146
3.228 USM1300 ..............................................................................................................................................147
3.229 USM1301 ..............................................................................................................................................147
3.230 USM1302 ..............................................................................................................................................148
3.231 USM1303 ..............................................................................................................................................148
3.232 USM1304 ..............................................................................................................................................149
3.233 USM1305 ..............................................................................................................................................149
3.234 USM1306 ..............................................................................................................................................149
3.235 USM1307 ..............................................................................................................................................150
3.236 USM1308 ..............................................................................................................................................150
3.237 USM1309 ..............................................................................................................................................151
3.238 USM1310 ..............................................................................................................................................151
4 KAIROS based HLR alarms reference ..............................................................................................152
4.1 HLR1300 ...............................................................................................................................................152
4.2 HLR1301 ...............................................................................................................................................152
4.3 HLR1302 ...............................................................................................................................................153
4.4 HLR1303 ...............................................................................................................................................153
4.5 HLR1304 ...............................................................................................................................................154
4.6 HLR1305 ...............................................................................................................................................155
4.7 HLR1306 ...............................................................................................................................................155
4.8 HLR1307 ...............................................................................................................................................156
4.9 HLR1308 ...............................................................................................................................................157
4.10 HLR1350 ...............................................................................................................................................157
4.11 HLR1351 ...............................................................................................................................................158
4.12 HLR1352 ...............................................................................................................................................159
4.13 HLR1360 ...............................................................................................................................................160
4.14 HLR1363 ...............................................................................................................................................160

1 Alarm fundamentals
A log report is a message about an important conditions or events related to component(s) performance. Log
reports include, but are not restricted to, the following information:
• state and activity reports

• hardware or software errors
• other events or conditions that affect performance
Both system actions and manual overrides can generate log reports.

2 HLR alarms reference

This section provides a reference for the HLR Alarms for the Kapsch Advanced Integrated Reliable Operat-
ing System (KAIROS) based HLR with HLR22 release.
2.1 ILLCFG
This alarm occurs when a mismatch between the data at the SOS level and the KAIROS base is detected.
Configuration data received from Base Config contains an incorrect entry.
In the Message Routing Function (MRF) node, the GHLRVLR or GHLRSGSN table contain a non-nil entry.
Subscribers are datafilled on the MRF node.
Subscriber mappings are datafilled on the HLR node.
Inconsistencies exist between HLRINV data (for instance, local node type: HLR or MRF) and local node vari-
ables listed by the platform command.
2.1.1 System impact

The HLR number entered into KAIROS configuration via the CLI cannot be applied at the SOS level.
2.1.2 Remedial action

Analyze the GHLR336 log on the SOS level to determine the nature of the problem. The Action field of the
log specifies the action required to clear this alarm. Contact Kapsch Engineering Support if the log does not
specify the correct action.
2.1.3 Attributes
Attribute Value
Log name GHLR336 HLR Illegal Config
Severity Major
Type Operational Violation
Probable cause Database Inconsistency
Suppression setting suppression-not-allowed
2.1.4 Associated logs

• GHLR336

3 KAIROS alarms reference

This section provides a reference for the KAIROS alarms.
3.1 AMF1300
This is the AMF service-group quality-of-service alarm.
An alarm is raised when a service-unit’s readiness-state changes from in-service. A service-unit with an ad-
min-state of offline is considered to be in-service.
This is a quality of service alarm that affects a service-group.
The service-group is configured in the service-group table.
3.1.1 System impact

This alarm is service-affecting. It indicates a loss of redundancy within a service-group.
This alarm is originally a minor alarm. The alarm can be updated to major when the number of service-units
with a readiness-state of in-service is equal to the sg-min-num-of-sus for the service-group. The alarm can
be updated to critical when the number of service-units with a readiness-state of in-service is less than the
sg-min-num-of-sus for service-group.

Investigate the cause of the service-unit failure.
3.1.3 Attributes
Attribute Value
Severity • Critical
• Major
• Minor
Type Quality of Service Alarm
Probable cause Application Subsystem Failure
Suppression setting suppression-allowed
3.2 COMFL
This alarm occurs on the local node if communication with the peer node unexpectedly fails, for instance
when the application-level heartbeat is unexpectedly lost.
When this alarm is raised, the local node cannot send single-shot messages to the peer nor receive re-
sponses to these messages and therefore the local node cannot accurately monitor the peer. The local node
cannot determine whether or not the peer is in service.

This alarm clears once the local node starts to:

– communicate with its peer
– the peer node is manually busied or brought out of the cluster

Manual actions are required to recover the peer node INSV or remove it from the cluster.
These actions should not be carried out on the local node. The recovery actions should be carried out on the
peer node either at the SOS level or via KAIROS CLI. Contact Kapsch Engineering Support for more infor-
mation.
3.2.2 Attributes
Attribute Value
Severity Major
3.2.3 Associated logs

• GHLR330
3.3 CisLi1300
There was an error performing an operation on the specified file.
This alarm indicates an error while handling a file.
This alarm is generated with the entityType as cis-li.
3.3.1 System impact

This alarm is service affecting.
The alarm severity can be either major or minor. The alarm is managed via the OAM FM Library API only.

If the condition persists, contact your next level of support.
3.3.3 Attributes
Attribute Value
Severity • Minor
• Major
Type Processing Error Alarm
Probable cause File Error

3.4 CisLi1301
Error opening a file
This alarm indicates an error while opening a file.
3.4.1 System impact

This is a major alarm. The alarm severity is passed in via the OAM FM Library API only.

If the condition persists, contact your next level of support.
3.4.3 Attributes
Attribute Value
Severity Major
Probable cause File Error
3.5 CisLi1302
This alarm is generated when one component cannot connect to another resource.
This alarm indicates there is a communication problem.
3.5.1 System impact


1. Verify that the resource is available.
2. Within the cli, confirm the CisLi configuration.
3. If the condition persists, contact your next level of support.
3.5.3 Attributes
Attribute Value
Severity Major
Type Communications Alarm

3.6 CisLi1303
The connection to the formatter is down.
This alarm indicates a communication problem between the formatter and the specified component.
3.6.1 System impact


If the problem persists, contact your next level of support.
3.6.3 Attributes
Attribute Value
Severity Major
Probable cause Communication Subsystem Failure
3.7 CisLi1304
The CisLi application cannot connect to the SOS image to receive CNR records.
This alarm indicates a communication problem with the SOS image.
3.7.1 System impact


Verify the SOS image is available.
3.7.3 Attributes
Attribute Value
Severity Major

3.8 CisLi1305
Invalid profile
This alarm indicates an invalid profile.
3.8.1 System impact

This alarm is not service affecting.
This is either a minor or major alarm. The alarm severity is passed in via the OAM FM Library API only.

Verify the configuration values as indicated in the reason text.
3.8.3 Attributes
Attribute Value
Severity • Minor
• Major
Probable cause Corrupt Data
3.9 CisLi1306
A configuration value is invalid and the application cannot provide service until it is corrected.
This alarm indicates that CisLi is not configured correctly.
3.9.1 System impact

This alarm is service affecting
This is a critical alarm. The alarm severity is passed in via the OAM FM Library API only.

2. Restart the CisLi service-units.

3.9.3 Attributes
Attribute Value
Severity Critical
Probable cause Configuration or Customizing Error
3.10 CisLi1307
A configuration value is missing and the application cannot provide service until it is configured correctly.
This alarm indicates that CisLi is not configured correctly.
3.10.1 System impact

This is a critical alarm.

2. Restart the CisLi service-units.
3.10.3 Attributes
Attribute Value
Severity Critical
3.11 CisLi1308
The alarm is generated when an unknown agency attempts to connect. Possible reasons are invalid configu-
ration of the agency values, or an unauthorized connection attempt.
This alarm is raised when an unknown agency attempts to connect to CisLi.



1. Within the cli, confirm the agency configuration values.
2. Restart the CisLi service-units if there are changed.
3. Contact your next level of support.
3.11.3 Attributes
Attribute Value
Severity Major
Probable cause Unauthorized Access Attempt
3.12 CisLi1309
The remote IP cannot be retrieved.
This alarm indicates a communication problem between the reporting component and another component.


1. Verify any configuration values as indicated in the reason text.
3.12.3 Attributes
Attribute Value
Severity Major
Probable cause Software Error
3.13 CisLi1310
An internal software error occurred.



Contact your next level of support.
3.13.3 Attributes
Attribute Value
Severity Major
3.14 DHCP1300
This is a DHCP Service Unavailable alarm.
An alarm is raised when the dhcpMgr is unable to restart the DHCP Server after an add/modify/delete to the
dhcp-entry entity.
This is a DHCP Manager alarm.
The dhcp service is configured in the Dhcp Entry Table.

This alarm is service affecting. It can result in the inability to boot an application from this card.
This alarm is initially a major alarm and does not change.

Contact your next level of support for help.
3.14.3 Attributes
Attribute Value
Severity Major
Probable cause Communication Protocol Error
3.15 DHCP1301
This is a DHCP Manager Alarm that is seen when the dhcpd.conf files are not accessible for update.

An alarm is raised when the dhcpMgr is unable to write to the dhcpd.conf files.

This alarm is initially a critical alarm and does not change.

The following steps must be taken when this alarm is seen:
1. Verify the file permissions for the dhcpd.conf files under

/opt/kapsch/cnp/data/platform/netserv/dhcpmgr/. If the permissions are not read/write/execute
for root then modify them.
2. If step 1 did not clear the alarm, delete both the dhcpd1.conf and dhcpd0.conf files in the
above directory. The files will be re-created automatically. If the alarm persists, contact your
next level of support.
3.15.3 Attributes
Attribute Value
Severity Critical
3.16 DHCP1302
This is a DHCP Manager alarm that is seen when the dhcpd.conf file are not accessible for update.
An alarm is raised when the dhcpMgr is unable to write to the dhcpd.conf file.

This alarm is initially a major alarm and does not change.

1. Verify the file permissions for the dhcpd.conf file under

/opt/kapsch/cnp/data/platform/netserv/dhcpmgr/. If the permissions are not read/write/execute
for root then modify them.

2. If step 1 did not clear the alarm, delete dhcpdx.conf file in the above directory where x repre-
sents the unit. The file will be re-created automatically. If the alarm is not cleared, contact
your next level of support.
3.16.3 Attributes
Attribute Value
Severity Major
3.17 HlrOamAgent1300
The switch generates log AUTO300 and raises a critical alarm when the memory pool allocation equals the
maximum pool allocation. That is, the value of ALLOC in table OFCAUT is equal to the value of MAXSIZE, in
table OFCAUT. Because the memory pool allocation is at its maximum, any additional memory requirement
causes call degradation.
The system generates a reminder log AUTO300 each day at 8 a.m. for every office parameter that is at its
maximum memory allocation. Alarms are not generated for reminder logs.
This alarm indicates that a memory pool allocation is maximized and call degradation can occur.
This alarm is generated from the HLR SOS image.

This alarm is service affecting. It indicates a likely call degradation.
The alarm severity is initially critical. Once raised, it will not be updated, only cleared. The alarm is raised or
cleared via the OAM FM Library API only.

Contact your next level of support immediately. The office parameter memory pool allocation has reached
maximum allowed levels and call degradation can occur.
3.17.3 Attributes
Attribute Value
Severity • Clear
• Critical
Probable cause Resource at or Nearing Capacity

An OM2200 log has been generated to indicate that an OM count has exceeded a preset threshold.
The Operational Measurement 2 (OM2) subsystem generates OM2200 when the system exceeds a thresh-
old condition. Entries in tables ALARMTAB (read only) and OMTHRESH (read/write) define thresholds. The
number of events that the register counts during a period of minutes (SCANTIME) can exceed the value
stored in threshold. If this error occurs, a log generates with the specified severity.
This alarm indicates that OM counts have exceeded preset thresholds.

Whether or not this alarm is service affecting depends on the OM that has surpassed the threshold.

Clear alarm from the EXT level of the MAP (maintenance and administration position). The name of the
alarm is OMCRITICAL.
3.18.3 Attributes
Attribute Value
Severity • Clear
• Critical
Probable cause Threshold Crossed



alarm is OMMAJOR.
3.19.3 Attributes
Attribute Value
Severity • Clear
• Critical
This alarm indicates that OM counts have exceeded preset thresholds. This alarm is generated from the HLR
SOS image.


alarm is OMMINOR.
3.20.3 Attributes
Attribute Value
Severity • Clear
• Critical

This alarm indicates that an error was found during the sanity check after the patching automatic process.
The POST_AUTOPROCESS_SANITY_ALARM appears on the EXT banner of the MAPCI as a Major
POST_AUTOPROC_SA alarm.
This alarm indicates that an error has been found during the sanity after the patching auto process.

The alarm severity is initially major. Once raised, it will not be updated, only cleared. The alarm is raised or

Proposed repair action is unknown at this time.
3.21.3 Attributes
Attribute Value
Severity • Clear
• Major
The PRSM Patch Audit raises alarms under the MAP’s EXT banner as necessary based on findings from its
daily status audit. The potential alarms and their severity are set in table PATALARM.
This alarm indicates that the PRSM patch audit has detected an active patch that has not been applied.
This alarm indicates that the PRSM patch audit has detected that an active patch has not been applied.

This alarm is potentially service affecting depending on the nature of the missing patch.
The alarm severity is set based on the datafill in the PATALARM table. The alarm is raised or cleared via the
OAM FM Library API only.

Investigate the cause of the patch application error and apply the patch as needed.

3.22.3 Attributes
Attribute Value
Severity Clear
Attribute Value
This alarm indicates that the PRSM patch audit has detected an active patch that has not been activated.
This alarm indicates that the PRSM patch audit has detected that an active patch has not been activated.

This alarm is potentially service affecting depending on the nature of the problem patch.

Investigate the cause of the patch activation error and activate the patch as needed.
3.23.3 Attributes
Attribute Value
Severity Clear
This alarm indicates that the PRSM patch audit has detected that an active password has not been activat-
ed.


This alarm is not service affecting

Investigate the cause of the password activation error and activate the password as needed.
3.24.3 Attributes
Attribute Value
Severity Clear
This alarm indicates that the PRSM patch audit has detected a debug patch has been applied.
This alarm indicates that the PRSM patch audit has detected that a debug patch has been applied.

This alarm is potentially service affecting depending on the nature of the debug patch.

If the applied debug patch is unexpected, it should be removed. If the applied debug patch is expected, no
action is required.
3.25.3 Attributes
Attribute Value
Severity Clear
Probable cause Procedural Error

This alarm indicates that the PRSM patch audit has detected a debug patch on the system that has not been
applied.
This alarm indicates that the PRSM patch audit has detected that a debug patch is on the system but not ap-
plied.


If the debug patch is supposed to be applied, it needs to be applied. Otherwise, the alarm can be ignored.
3.26.3 Attributes
Attribute Value
Severity Clear
This alarm indicates that the PRSM patch audit has detected a DNR (Do Not Reapply) patch that has not
been applied.
This alarm indicates that the PRSM patch audit has detected that a DNR (Do Not Reapply) patch has not
been applied.



3.27.3 Attributes
Attribute Value
Severity Clear
This alarm indicates that the PRSM patch audit has detected an emergency patch that has not been applied.
This alarm indicates that the PRSM patch audit has detected that an emergency patch has not been applied.


3.28.3 Attributes
Attribute Value
Severity Clear
This alarm indicates that the PRSM patch audit has detected a general purpose patch that has not been ap-
plied.
This alarm indicates that the PRSM patch audit has detected that a general purpose patch has not been ap-
plied.



3.29.3 Attributes
Attribute Value
Severity Clear
This alarm indicates that the PRSM patch audit has detected a limited patch that has not been applied.
This alarm indicates that the PRSM patch audit has detected that a limited patch has not been applied.


3.30.3 Attributes
Attribute Value
Severity Clear

This alarm indicates that the PRSM patch audit has detected a MAN (extended multiprocessor system XPM
operational code) patch that has not been applied.
This alarm indicates that the PRSM patch audit has detected that a MAN (extended multiprocessor system
XPM operational code) patch has not been applied.


3.31.3 Attributes
Attribute Value
Severity Clear
This alarm indicates that the PRSM patch audit has detected a SRC (XPM source code) patch that has not
been applied.
This alarm indicates that the PRSM patch audit has detected that a SRC (XPM source code) patch has not
been applied.



3.32.3 Attributes
Attribute Value
Severity Clear
This alarm indicates that the PRSM patch audit has detected an obsolete patch has not been removed.
This alarm indicates that the PRSM patch audit has detected that an obsolete patch has not been removed.


Remove the obsolete patch and investigate why it is still on the system.
3.33.3 Attributes
Attribute Value
Severity Clear
This alarm indicates that the PRSM patch audit has detected an obsolete emergency patch has not been
removed.
This alarm indicates that the PRSM patch audit has detected that an obsolete emergency patch has not
been removed



3.34.3 Attributes
Attribute Value
Severity Clear
This alarm indicates that the PRSM patch audit has detected that patches have been removed.


Load the missing patches on to the system and investigate the cause of the missing patches.
3.35.3 Attributes
Attribute Value
Severity Clear

3.35.4 HlrOamAgent1319
This alarm indicates that the PRSM patch audit has detected a patch that has been applied but not installed.
This alarm indicates that the PRSM patch audit has detected that a patch has been applied but not installed.

This alarm is potentially service affecting depending on the nature of the patch.

Investigate the cause of the patch installation error and install the patch as needed.
3.35.7 Attributes
Attribute Value
Severity Clear
The group_mismatch alarm is raised when all destinations with the same load name do not contain the same
patch content. These alarms are very useful to detect patches missing due to actions outside of PRSM such
as device reloads. Affected devices can be identified by invoking the SELECT GRPMISMATCH command.
These devices be may corrected by invoking the APPLY GRPMISMATCH command.
This alarm indicates that the PRSM patch audit has detected a group patch mismatch in that all destinations
with the same load name do not contain the same patch content.

This alarm is potentially service affecting depending on the nature of the missing patches.

Affected devices can be identified by invoking the SELECT GRPMISMATCH command. These devices be
may corrected by invoking APPLY GRPMISMATCH command.

3.36.3 Attributes
Attribute Value
Severity Clear
The db_entry invalid alarm can be used to identify patches that were discovered by PRSM to be applied to a
dest but the instance of PRSM running now did not actually perform the apply. This situation can occur due
to reloads from images that contain patches applied from another instance of PRSM.
This alarm indicates that the PRSM patch audit has detected that a patch has been applied but not by this
instance of PRSM and thus appears invalid.


Identify the relevant PRSUIDs using SELECT ENTRYVALID, locate or download the missing PRSU files and
validate the PRSUs. Validating these PRSUs on just one device with the entryvalid field set is enough to fix
the alarm.
3.37.3 Attributes
Attribute Value
Severity Clear
The PRSM Patch tool raises this major alarm under the MAP’s EXT banner when a pre-autopatch sanity fail-
ure occurs. Please refer to the associated log for more details.
This alarm indicates that a Pre-AutoPatch Sanity failed.


This alarm is potentially service affecting depending on the nature of the patches involved.

Investigate the cause of the pre-autopatch sanity error.
3.38.3 Attributes
Attribute Value
Severity • Clear
• Critical
The PRSM Patch tool raises this major alarm under the MAP’s EXT banner when a post-autopatch sanity
failure occurs. Please refer to the associated log for more details.
This alarm indicates that a Post-AutoPatch Sanity failed.


Investigate the cause of the post-autopatch sanity error.
3.39.3 Attributes
Attribute Value
Severity • Clear
• Critical
The PRSM Patch system raises alarms under the MAP’s EXT banner as necessary based on findings from
its daily status audit. The ACTPATCH alarm and its severity is defined in table SFWALARM.

This alarm indicates that PRSM has detected that a patch that is ready to be activated has not been activat-
ed.
ed.

This alarm is potentially service affecting depending on the nature of the patch involved.
The alarm severity is set based on the datafill in table SFWALARM. The alarm is raised or cleared via the

3.40.3 Attributes
Attribute Value
Severity Clear
The Patch Audit raises alarms under the MAP’s EXT banner as necessary. This alarm and its severity is de-
fined in table SFWALARM.
This alarm indicates that the patch audit has detected a critical issue.

This alarm is potentially service affecting.

Investigate the cause of the patch system error.

3.41.3 Attributes
Attribute Value
Severity • Clear
• Critical
This alarm indicates that the patch audit has detected a major issue.


3.42.3 Attributes
Attribute Value
Severity • Clear
• Major
This alarm indicates that the patch audit has detected a minor issue.


The alarm severity is initially minor. Once raised, it will not be updated, only cleared. The alarm is raised or

3.43.3 Attributes
Attribute Value
Severity • Clear
• Minor
The switch generates a GHLR308 log to raise and clear this alarm condition. This alarm condition occurs
when the HLR’s CPU occupancy has surpassed the preset thresholds.
The switch generates a GHLR308 alarm and raises this alarm when the alarm condition occurs. A GHLR308
alarm is also generated when the alarm condition is cleared.
This alarm indicates that the HLR’s CPU occupancy has surpassed the preset thresholds.

This alarm is potentially service affecting if the condition persists for an extended period of time.
The alarm severity is variable. The alarm severity is set, updated, and cleared based on the severity set in
the GHLR308 log raising the alarm. The alarm is raised or cleared via the OAM FM Library API only.

No immediate action or post analysis is required. If the condition persists, next level support should be con-
tacted.
3.44.3 Attributes
Attribute Value
Severity Clear
Probable cause CPU Cycles Limit Exceeded
The HLR runs a database audit every 3 hours to check the status of the database memory usage. If the

HLR’s database memory usage has surpassed the preset thresholds set in the GHLRPARM table against
the DBMEMLIM parameter key, the alarm is raised and a GHLR308 log is generated.
This alarm indicates that the HLR’s database memory usage has surpassed the preset thresholds.


tacted.
3.45.3 Attributes
Attribute Value
Severity Clear
Probable cause Out of Memory
when the HLR’s Standby times have surpassed the preset thresholds defined in table GHSBYCFG.
This alarm indicates that HLR’s Standby times have surpassed the preset thresholds.


tacted.

3.46.3 Attributes
Attribute Value
Severity Clear
The HLR runs an audit every 5 seconds to monitor the transaction resources high water marks. If the re-
source usages surpasses the set alarm limits (set using the HLRRESOURCES tool), this alarm is raised and
a GHLR308 log is generated. A GHLR306 log is also generated to output the details of the resource usage.
This alarm indicates that HLR’s transaction resources have surpassed the preset thresholds.


tacted.
3.47.3 Attributes
Attribute Value
Severity Clear
The HLR runs a daily audit to monitor the status of the database. If the audit detects a corruption, this alarm
is raised and a GHLR308 log is generated.
This alarm indicates that a corrupt database has been detected on the HLR.



tacted.
3.48.3 Attributes
Attribute Value
Severity Clear
This alarm condition occurs when the HLR third party controller memory utilization has surpassed the preset
thresholds. The switch generates a GHLR308 log to raise and clear this alarm condition.
This alarm indicates that HLR third party controller memory utilization has surpassed the preset thresholds.


tacted.
3.49.3 Attributes
Attribute Value
Severity Clear
Type Equipment Alarm

If a change has been made to either table GHLRNDSC or GHLRNDCL this alarm is set. Such a change may
result in invalid data being present at one or more VLRs at which subscribers are presently located. As such,
this alarm is raised and an GHLR308 log is generated.
This alarm indicates that table GHLRNDSC or GHLRNDCL have been changed.


tacted.
3.50.3 Attributes
Attribute Value
Severity Clear
If the HLR detects a problem in the zone code datafill, this alarm is raised and an GHLR308 log is generated.
A GHLR680 log is also generated with the details of the zone codes datafill conflict.
This alarm indicates that the HLR has detected a problem in the zone code datafill.


tacted

3.51.3 Attributes
Attribute Value
Severity Clear
If the HLR detects a problem with the translations datafill, this alarm is raised and a GHLR308 log is gener-
ated. A GHLR663 log is also generated with the details of the translations datafill problem.
This alarm indicates that the HLR has detected a problem in the translations datafill.


tacted.
3.52.3 Attributes
Attribute Value
Severity Clear
If the HLR detects a datafill problem in table GHLRPCC, this alarm is raised and a GHLR308 log is generat-
ed. A GHLR662 log is also generate with the details of the datafill problem.
This alarm indicates that the HLR has detected a datafill problem in table GHLRPCC.



tacted.
3.53.3 Attributes
Attribute Value
Severity Clear
The HLR monitor’s outgoing Invoke messages originated on a Network Appearance basis and if it finds that
the load distribution offered by the HLR to the network reaches alarmable levels, this alarm is raised and a
GHLR308 log is generated.
This alarm indicates that HLR’s load distribution has reached alarmable limits.


tacted.
3.54.3 Attributes
Attribute Value
Severity Clear

If the switch detects that image files are not registered in the two computing module (CM) or two message
switch (MS) ITOCs, a critical ITOC alarm is raised. If the switch detects that image files are registered in one
computing module (CM) ITOC while the other ITOC is empty or one message switch (MS) ITOC while the
other ITOC is empty, a minor ITOC alarm is raised.
This alarm indicates that required image file registrations are missing.

This alarm is potentially service affecting if it is a critical alarm. If a reload is initiated during the ITOC critical
alarm, a loss of service can occur. A minor ITOC alarm is not service affecting.
The alarm severity is variable. The alarm is raised or cleared via the OAM FM Library API only.

Using ITOCCI, determine the missing image files. Then load them on the switch and register them. If the
alarm does not go away, contact the next level of support for assistance.
3.55.3 Attributes
Attribute Value
Severity Clear
The Device Independent Recording Package (DIRP) subsystem generates this alarm when a condition pre-
venting normal operation of DIRP occurs in relation to the DLOG facility. A DIRP101 log is generated with full
details regarding the cause of the alarm. See the Translations Guide for a description of DIRP and its use.
The cause of the alarm is variable and is indicated in the DIRP101 log. Please refer to the Log Report Refer-
ence guide for the DIRP101 log for full details regarding the translation of the DIRP101 log contents.
This alarm indicates that the Device Independent Recording Package (DIRP) subsystem has detected an
alarmable condition with the DLOG facility

The alarm severity is variable depending on the cause. The alarm is raised or cleared via the OAM FM Li-
brary API only.


The repair actions are variable depending on the cause of the alarm. Please refer to the Log Report Refer-
ence for the DIRP101 log for full details.
3.56.3 Attributes
Attribute Value
Severity Clear
venting normal operation of DIRP occurs in relation to the JF facility. A DIRP101 log is generated with full de-
tails regarding the cause of the alarm. See the Translations Guide for a description of DIRP and its use.
This alarm indicates that the Device Independent Recording Package (DIRP) subsystem is unable to open
the required number of journal files for recording.


The repair actions are variable depending on the cause of the alarm. Please refer to the generated DIRP101
log and the Log Report Reference for the DIRP101 log for full details.
3.57.3 Attributes
Attribute Value
Severity Clear
This USP M3UA alarm is raised when the path between the SCA and the SSG goes out of service.
This alarm indicates that the connection between the SCA and SSG is out of service.



Attempt to bring the resource in service. If the condition persists, please contact next level support for assis-
tance.
3.58.3 Attributes
Attribute Value
Severity • Clear
• Critical
Probable cause Underlying Resource Unavailable
If a CCS7 route set goes SYSB or MANB, this alarm is raised and a CCS153 or CCS154 log is generated
with the details. A routeset may be manual busy or system busy because of 1) faults in the peripheral mod-
ules that associate with the linksets in the routeset, 2) faults on the links that associate with your office, or 3)
problems on the network.
This alarm indicates that a CCS7 route set is SYSB or MANB.


Bring any related Peripherals or Link Sets in service and then attempt to bring the routeset in service. If the
condition persists, contact next level support for assistance. For full details, refer to the Alarm and Perfor-
mance Monitoring Procedures (297-8021-543P1) document for clearing CCS RS critical alarms.

3.59.3 Attributes
Attribute Value
Severity • Clear
• Critical
CCS7 Local SubSystems are defined in table C7LOCSSN. When one of these local subsystems goes SYSB
or MANB, the switch raises this alarm and generates a CCS219 log with the details regarding the affected
subsystem.
This alarm indicates that a CCS7 Local SubSystem is SYSB or MANB.


Access the CCS7 MAP level and attempt to bring the affected subsystem in service. For full details, refer to
the Alarm and Performance Monitoring Procedures (297-8021-543P1) document for clearing CCS LSSC crit-
ical alarms.
3.60.3 Attributes
Attribute Value
Severity • Clear
• Critical
CCS7 Remote SubSystems are defined in table C7NETSSN. When one of these remote subsystems goes
SYSB or MANB, the switch raises this alarm and generates a CCS213 or CCS214 log with the details re-
garding the affected subsystem.
This alarm indicates that a CCS7 Remote SubSystem is SYSB or MANB.



Access the CCS7 MAP level, and if there’s a critical point code alarm, attempt to clear it and then wait to see
if the remote subsystem alarm clears. If not, work with the remote office in an attempt to clear the alarm. For
full details, refer to the Alarm and Performance Monitoring Procedures (297-8021-543P1) document for
clearing CCS RSSC critical alarms.
3.61.3 Attributes
Attribute Value
Severity • Clear
• Critical
If a CCS7 point code goes SYSB, this alarm is raised and a CCS210 log is generated. Note that a point code
might be SYSB because a route set has gone SYSB, which would be indicated in the CCS210 log.
This alarm indicates that a CCS7 point code is SYSB.


Access the CCS7 MAP level, and if there’s a critical route set alarm, attempt to clear it and then wait to see if
the point code alarm clears. If not, attempt to bring the point code in service. If unable to bring the point code
in service, contact next level support for assistance. For full details, refer to the Alarm and Performance Mon-
itoring Procedures (297-8021-543P1) document for clearing CCS PCC critical alarms.

3.62.3 Attributes
Attribute Value
Severity • Clear
• Critical
This USP M3UA alarm is raised when the path between the SCA and the SSG in trouble.
This alarm indicates that the connection between the SCA and SSG is in trouble.


If the condition persists, attempt to bring the resource in service and contact next level support for assistance
if necessary.
3.63.3 Attributes
Attribute Value
Severity • Clear
• Major
If a CCS7 route set goes IsTb, this alarm is raised. A routeset may be IsTb because
• faults in the peripheral modules associated with the linksets in the routeset,
• faults on the links associated with your office,
• problems on the network, or
• problems within a network cluster.
The routeset can continue to carry traffic with the risk of a degraded level of service.

This alarm indicates that a CCS7 route set is IsTb.



Bring any related Peripherals or Link Sets in service and then wait to see if the routeset returns to in service.
If the condition persists, contact next level support for assistance. For full details, refer to the Alarm and Per-
formance Monitoring Procedures (297-8021-543P1) document for clearing CCS RS major alarms.
3.64.3 Attributes
Attribute Value
Severity • Clear
• Major
CCS7 Local SubSystems are defined in table C7LOCSSN. When one of these local subsystems goes IsTb,
the switch raises this alarm and generates a CCS231 log with the details regarding the affected subsystem.
This alarm indicates that a CCS7 Local SubSystem is IsTb (in service trouble).


Access the CCS7 MAP level and investigate the cause of the inservice trouble condition. Wait for the alarm
to clear. If the alarm persists for an extended period of time, contact the next level of support to help investi-
gate the cause of the condition. For full details, refer to the Alarm and Performance Monitoring Procedures
(297-8021-543P1) document for clearing CCS LSSC major alarms.

3.65.3 Attributes
Attribute Value
Severity • Clear
• Major
If a CCS7 point code goes IsTb because of congestion on the routes between the office and the remote of-
fice represented by the point code, this alarm is raised and a CCS229 log is generated with the details.
This alarm indicates that a CCS7 point code is IsTb.

This alarm is potentially service affecting. This alarm indicates traffic congestion on the routes between the
office and the remote office indicated by the point code. If this condition persists, and the congestion level is
too high, the can discard messages to the signalling point identified by the point code.

Access the CCS7 MAP level, and if there’s a minor route set alarm, attempt to clear it and then wait to see if
the point code alarm clears. If the condition persists, contact next level support for assistance. For full details,
refer to the Alarm and Performance Monitoring Procedures (297-8021-543P1) document for clearing CCS
PC minor alarms.
3.66.3 Attributes
Attribute Value
Severity • Clear
• Minor
This alarm indicates that there is a mismatch between the OM transfer periods of the SOS image and
KAIROS PM.



Change either the SOS or KAIROS PM collection Periods
3.67.3 Attributes
Attribute Value
Severity • Clear
• Major
Probable cause Timing Problem
The KAIROS SOS Alarm Agent is likely clearing all alarms because of a loss of communication with the
HLR which makes it is impossible for the KAIROS SOS Alarm Agent to accurately maintain the state of
raised alarms.
This event indicates that the KAIROS SOS Agent has cleared all alarms.
This alarm is generated by the KAIROS SOS Alarm Agent.

The alarm severity is cleared since the application is clearing all alarms.

tacted.
3.68.3 Attributes
Attribute Value
Severity Clear
3.69 Inv1312
This is an application blade seated in incorrect slot alarm.

This alarm is raised when the application blade is inserted into an incorrect slot.
This is an equipment configuration error alarm.
The application blade is configured in table app_blade.

This alarm is service affecting. The alarmed blade will not provide service.
This alarm is a critical alarm. The alarm severity is passed in via the OAM FM Library API only.

The following actions must be taken:
1. Remove the application blade from the current slot;
2. Delete provision for the slot.
3.69.3 Attributes
Attribute Value
Severity Critical
3.70 Inv1313
This is a System Hardware Inventory become active failure alarm.
This alarm is raised when the System Hardware Inventory failed to switch activity from standby to active.
This is a software application failure alarm.


No repair action required.

3.70.3 Attributes
Attribute Value
Severity Critical
3.71 InvAppBld1300
This is an assigned PEC and inventory PEC mismatched alarm.
This alarm is raised when the application blade is inserted into an incorrect slot, or the incorrect PEC is as-
signed during provisioning.


One of the following steps must be taken:
1. Replace the application blade if the wrong blade is inserted to the slot;
2. Delete and re-add provision, if the application blade is inserted in the proper slot but the
wrong PEC was assigned to the slot during initial provision.
3.71.3 Attributes
Attribute Value
Severity Critical
3.72 InvAppBld1301
This is an application blade missing alarm.
This alarm is raised when the provisioned application blade is not inserted into the slot.



One of the following actions must be taken:
1. Insert the proper application blade into the slot; or

2. Delete provision if the slot is meant to be empty
3.72.3 Attributes
Attribute Value
Severity Critical
3.72.4 InvAppBld1302
This is an unknown application blade alarm.
This alarm is raised when the seated application blade cannot be recognized by the release software.


1. Remove the application blade in slot;
2. Insert the proper application blade into the slot.
3.72.7 Attributes
Attribute Value
Severity Critical

3.73 InvFtm1300
This is a Fan Tray Module assigned PEC and inventory PEC mismatched alarm.
This alarm is raised when the incorrect PEC is assigned during Fan Tray Module provisioning.
Fan Tray Module is configured in table ftm.


The following action must be taken: delete and re-add provision with correct PEC for the Fan Tray Module.
3.73.3 Attributes
Attribute Value
Severity Critical
3.74 InvFtm1301
This is a Fan Tray Module missing alarm.
This alarm is raised when the Fan Tray Module is not inserted into the slot.
Fan Tray Module is configured in table pem.


The following action must be taken: insert the Fan Tray Module into the slot

3.74.3 Attributes
Attribute Value
Severity Critical
3.75 InvFtm1302
This is an unknown Fan Tray Module alarm.
This alarm is raised when the Fan Tray Module cannot be recognized by the release software.
Fan Tray Module is configured in table ftm.


1. Remove the Power Entry Module in slot;

2. Insert a proper Power Entry Module into the slot
3.75.3 Attributes
Attribute Value
Severity Critical
3.76 InvPem1300
This is an unknown Power Entry Module alarm.
This alarm is raised when the Power Entry Module cannot be recognized by the release software.
Power Entry Module is configured in table pem.



1. Remove the Power Entry Module in slot;
2. Insert a proper Power Entry Module into the slot
3.76.3 Attributes
Attribute Value
Severity Critical
3.77 InvPem1301
This is a Power Entry Module missing alarm.
This alarm is raised when the Power Entry Module is not inserted into the slot.


The following action must be taken: insert the Power Entry Module into the slot.
3.77.3 Attributes
Attribute Value
Severity Critical

3.78 InvPem1302
This is a Power Entry Module assigned PEC and inventory PEC mismatched alarm.
This alarm is raised when the incorrect PEC is assigned during Power Entry Module provisioning.


The following action must be taken: delete and re-add provision with correct PEC for the Power Entry Mod-
ule.
3.78.3 Attributes
Attribute Value
Severity Critical
3.79 InvSam1300
This is a Shelf and Alarm Manager assigned PEC and inventory PEC mismatched alarm.
This alarm is raised when the incorrect PEC is assigned during Shelf and Alarm Manager provisioning.
Shelf and Alarm Manager is configured in table sam.


The following action must be taken: delete and re-add provision with correct PEC for the Shelf and Alarm
Manager.

3.79.3 Attributes
Attribute Value
Severity Critical
3.80 InvSam1301
This is a Shelf and Alarm Manager missing alarm.
This alarm is raised when the Shelf and Alarm Manager is not inserted into the slot.


The following actions must be taken: insert the Shelf and Alarm Manager into the slot
3.80.3 Attributes
Attribute Value
Severity Critical
3.81 InvSam1302
This is an unknown Shelf and Alarm Manager alarm.
This alarm is raised when the Shelf and Alarm Manager cannot be recognized by the release software.



1. Remove the Shelf and Alarm Manager in slot;
2. Insert a proper Shelf and Alarm Manager into the slot.
3.81.3 Attributes
Attribute Value
Severity Critical
3.82 MrfOamAgent1300
The switch generates log AUTO300 and raises a critical alarm when the memory pool allocation equals the
maximum pool allocation. That is, the value of ALLOC in table OFCAUT is equal to the value of MAXSIZE, in
table OFCAUT. Because the memory pool allocation is at its maximum, any additional memory requirement
causes call degradation.
The system generates a reminder log AUTO300 each day at 8 a.m. for every office parameter that is at its
maximum memory allocation. Alarms are not generated for reminder logs.
This alarm indicates that a memory pool allocation is maximized and call degradation can occur.
This alarm is generated from the MRF SOS image.

This alarm is service affecting. It indicates a likely call degradation.

Contact your next level of support immediately. The office parameter memory pool allocation has reached
maximum allowed levels and call degradation can occur.
3.82.3 Attributes
Attribute Value
Severity • Clear
• Critical



alarm is OMCRITICAL.
3.83.3 Attributes
Attribute Value
Severity • Clear
• Critical
3.83.4 MrfOamAgent1302



alarm is OMMAJOR.
3.83.7 Attributes
Attribute Value
Severity • Clear
• Critical


alarm is OMMINOR.
3.84.3 Attributes
Attribute Value
Severity • Clear
• Critical

This alarm indicates that an error was found during the sanity check after the patching automatic process.
The POST_AUTOPROCESS_SANITY_ALARM appears on the EXT banner of the MAPCI as a Major
POST_AUTOPROC_SA alarm.
This alarm indicates that an error has been found during the sanity after the patching auto process.


3.85.3 Attributes
Attribute Value
Severity • Clear
• Major
This alarm indicates that the PRSM patch audit has detected that an active patch has not been applied.



3.86.3 Attributes
Attribute Value
Severity Clear
This alarm indicates that the PRSM patch audit has detected an active patch that has not been activated.
This alarm indicates that the PRSM patch audit has detected that an active patch has not been activated.

This alarm is potentially service affecting depending on the nature of the problem patch.

3.87.3 Attributes
Attribute Value
Severity Clear
Attribute Value
This alarm indicates that the PRSM patch audit has detected that an active password has not been activat-
ed.



Investigate the cause of the password activation error and activate the password as needed.
3.87.7 Attributes
Attribute Value
Severity Clear
This alarm indicates that the PRSM patch audit has detected a debug patch has been applied.
This alarm indicates that the PRSM patch audit has detected that a debug patch has been applied.

This alarm is potentially service affecting depending on the nature of the debug patch.

If the applied debug patch is unexpected, it should be removed. If the applied debug patch is expected, no
action is required.
3.88.3 Attributes
Attribute Value
Severity Clear

This alarm indicates that the PRSM patch audit has detected a debug patch on the system that has not been
applied.
This alarm indicates that the PRSM patch audit has detected that a debug patch is on the system but not ap-
plied.


If the debug patch is supposed to be applied, it needs to be applied. Otherwise, the alarm can be ignored.
3.89.3 Attributes
Attribute Value
Severity Clear
This alarm indicates that the PRSM patch audit has detected a DNR (Do Not Reapply) patch that has not
been applied.
This alarm indicates that the PRSM patch audit has detected that a DNR (Do Not Reapply) patch has not
been applied.



3.90.3 Attributes
Attribute Value
Severity Clear
This alarm indicates that the PRSM patch audit has detected an emergency patch that has not been applied.
This alarm indicates that the PRSM patch audit has detected that an emergency patch has not been applied.


3.91.3 Attributes
Attribute Value
Severity Clear
This alarm indicates that the PRSM patch audit has detected a general purpose patch that has not been ap-
plied.
This alarm indicates that the PRSM patch audit has detected that a general purpose patch has not been ap-
plied.



3.92.3 Attributes
Attribute Value
Severity Clear
This alarm indicates that the PRSM patch audit has detected a limited patch that has not been applied.
This alarm indicates that the PRSM patch audit has detected that a limited patch has not been applied.


3.93.3 Attributes
Attribute Value
Severity Clear

This alarm indicates that the PRSM patch audit has detected a MAN (extended multiprocessor system XPM
operational code) patch that has not been applied.
This alarm indicates that the PRSM patch audit has detected that a MAN (extended multiprocessor system
XPM operational code) patch has not been applied.


3.94.3 Attributes
Attribute Value
Severity Clear
This alarm indicates that the PRSM patch audit has detected a SRC (XPM source code) patch that has not
been applied.
This alarm indicates that the PRSM patch audit has detected that a SRC (XPM source code) patch has not
been applied.



3.95.3 Attributes
Attribute Value
Severity Clear
This alarm indicates that the PRSM patch audit has detected an obsolete patch has not been removed.
This alarm indicates that the PRSM patch audit has detected that an obsolete patch has not been removed.


3.96.3 Attributes
Attribute Value
Severity Clear
This alarm indicates that the PRSM patch audit has detected an obsolete emergency patch has not been
removed.
This alarm indicates that the PRSM patch audit has detected that an obsolete emergency patch has not
been removed



3.97.3 Attributes
Attribute Value
Severity Clear


Load the missing patches on to the system and investigate the cause of the missing patches.
3.98.3 Attributes
Attribute Value
Severity Clear

This alarm indicates that the PRSM patch audit has detected a patch that has been applied but not installed.
This alarm indicates that the PRSM patch audit has detected that a patch has been applied but not installed.

This alarm is potentially service affecting depending on the nature of the patch.

Investigate the cause of the patch installation error and install the patch as needed.
3.98.7 Attributes
Attribute Value
Severity Clear
The group_mismatch alarm is raised when all destinations with the same load name do not contain the same
patch content. These alarms are very useful to detect patches missing due to actions outside of PRSM such
as device reloads. Affected devices can be identified by invoking the SELECT GRPMISMATCH command.
These devices be may corrected by invoking the APPLY GRPMISMATCH command.
This alarm indicates that the PRSM patch audit has detected a group patch mismatch in that all destinations
with the same load name do not contain the same patch content

This alarm is potentially service affecting depending on the nature of the missing patches.

Affected devices can be identified by invoking the SELECT GRPMISMATCH command. These devices be
may corrected by invoking APPLY GRPMISMATCH command.

3.99.3 Attributes
Attribute Value
Severity Clear
The db_entry invalid alarm can be used to identify patches that were discovered by PRSM to be applied to a
dest but the instance of PRSM running now did not actually perform the apply. This situation can occur due
to reloads from images that contain patches applied from another instance of PRSM.
This alarm indicates that the PRSM patch audit has detected that a patch has been applied but not by this
instance of PRSM and thus appears invalid.


Identify the relevant PRSUIDs using SELECT ENTRYVALID, locate or download the missing PRSU files and
validate the PRSUs. Validating these PRSUs on just one device with the entryvalid field set is enough to fix
the alarm.
3.99.7 Attributes
Attribute Value
Severity Clear
The PRSM Patch tool raises this major alarm under the MAP’s EXT banner when a pre-autopatch sanity fail-
ure occurs. Please refer to the associated log for more details.
This alarm indicates that a Pre-AutoPatch Sanity failed.



Investigate the cause of the pre-autopatch sanity error.
3.100.3 Attributes
Attribute Value
Severity • Clear
• Critical
The PRSM Patch tool raises this major alarm under the MAP’s EXT banner when a post-autopatch sanity
failure occurs. Please refer to the associated log for more details.
This alarm indicates that a Post-AutoPatch Sanity failed.


Investigate the cause of the post-autopatch sanity error.
3.101.3 Attributes
Attribute Value
Severity • Clear
• Critical

The PRSM Patch system raises alarms under the MAP’s EXT banner as necessary based on findings from
its daily status audit. The ACTPATCH alarm and its severity is defined in table SFWALARM.
ed.
ed.

This alarm is potentially service affecting depending on the nature of the patch involved.
The alarm severity is set based on the datafill in table SFWALARM. The alarm is raised or cleared via the

3.102.3 Attributes
Attribute Value
Severity Clear



3.103.3 Attributes
Attribute Value
Severity • Clear
• Critical


3.104.3 Attributes
Attribute Value
Severity • Clear
• Major



3.105.3 Attributes
Attribute Value
Severity • Clear
• Minor
when the MRF’s CPU occupancy has surpassed the preset thresholds.
This alarm indicates that the MRF’s CPU occupancy has surpassed the preset thresholds.


tacted.
3.106.3 Attributes
Attribute Value
Severity Clear
Probable cause CPU Cycles Limit Exceeded
The MRF runs a database audit every 3 hours to check the status of the database memory usage. If the

MRF’s database memory usage has surpassed the preset thresholds set in the GHLRPARM table against
the DBMEMLIM parameter key, the alarm is raised and a GHLR308 log is generated.
This alarm indicates that the MRF’s database memory usage has surpassed the preset thresholds.


tacted.
3.107.3 Attributes
Attribute Value
Severity Clear
Probable cause Out of Memory
when the MRF’s Standby times have surpassed the preset thresholds defined in table GHSBYCFG.
This alarm indicates that MRF’s Standby times have surpassed the preset thresholds.


tacted.

3.108.3 Attributes
Attribute Value
Severity Clear
The MRF runs an audit every 5 seconds to monitor the transaction resources high water marks. If the re-
source usages surpasses the set alarm limits (set using the MRFRESOURCES tool), this alarm is raised and
a GHLR308 log is generated. A GHLR306 log is also generated to output the details of the resource usage.
This alarm indicates that MRF’s transaction resources have surpassed the preset thresholds.


tacted.
3.109.3 Attributes
Attribute Value
Severity Clear
The MRF runs a daily audit to monitor the status of the database. If the audit detects a corruption, this alarm
is raised and a GHLR308 log is generated.
This alarm indicates that a corrupt database has been detected on the MRF.



tacted.
3.110.3 Attributes
Attribute Value
Severity Clear
This alarm condition occurs when the MRF third party controller memory utilization has surpassed the preset
thresholds. The switch generates a GHLR308 log to raise and clear this alarm condition.
This alarm indicates that MRF third party controller memory utilization has surpassed the preset thresholds.


tacted.
3.111.3 Attributes
Attribute Value
Severity Clear

If a change has been made to either table GHLRNDSC or GHLRNDCL this alarm is set. Such a change may
result in invalid data being present at one or more VLRs at which subscribers are presently located. As such,
this alarm is raised and an GHLR308 log is generated.
This alarm indicates that table GHLRNDSC or GHLRNDCL have been changed.


tacted.
3.112.3 Attributes
Attribute Value
Severity Clear
If the MRF detects a problem in the zone code datafill, this alarm is raised and an GHLR308 log is generat-
ed. A GHLR680 log is also generated with the details of the zone codes datafill conflict.
This alarm indicates that the MRF has detected a problem in the zone code datafill.


tacted.

3.113.3 Attributes
Attribute Value
Severity Clear
If the MRF detects a problem with the translations datafill, this alarm is raised and a GHLR308 log is gener-
ated. A GHLR663 log is also generated with the details of the translations datafill problem.
This alarm indicates that the MRF has detected a problem in the translations datafill.


tacted.
3.114.3 Attributes
Attribute Value
Severity Clear
If the MRF detects a datafill problem in table GHLRPCC, this alarm is raised and a GHLR308 log is generat-
ed. A GHLR662 log is also generate with the details of the datafill problem.
This alarm indicates that the MRF has detected a datafill problem in table GHLRPCC.



tacted.
3.115.3 Attributes
Attribute Value
Severity Clear
The MRF monitor’s outgoing Invoke messages originated on a Network Appearance basis and if it finds that
the load distribution offered by the MRF to the network reaches alarmable levels, this alarm is raised and a
GHLR308 log is generated.
This alarm indicates that MRF’s load distribution has reached alarmable limits.


tacted.
3.116.3 Attributes
Attribute Value
Severity Clear

If the switch detects that image files are not registered in the two computing module (CM) or two message
switch (MS) ITOCs, a critical ITOC alarm is raised. If the switch detects that image files are registered in one
computing module (CM) ITOC while the other ITOC is empty or one message switch (MS) ITOC while the
other ITOC is empty, a minor ITOC alarm is raised.
This alarm indicates that required image file registrations are missing.

This alarm is potentially service affecting if it is a critical alarm. If a reload is initiated during the ITOC critical
alarm, a loss of service can occur. A minor ITOC alarm is not service affecting.

Using ITOCCI, determine the missing image files. Then load them on the switch and register them. If the
alarm does not go away, contact the next level of support for assistance.
3.117.3 Attributes
Attribute Value
Severity Clear
venting normal operation of DIRP occurs in relation to the DLOG facility. A DIRP101 log is generated with full
details regarding the cause of the alarm. See the Translations Guide for a description of DIRP and its use.
This alarm indicates that the Device Independent Recording Package (DIRP) subsystem has detected an
alarmable condition with the DLOG facility.

The alarm severity is variable depending on the cause. The alarm is raised or cleared via the OAM FM Li-
brary API only.


The repair actions are variable depending on the cause of the alarm. Please refer to the Log Report Refer-
ence for the DIRP101 log for full details.
3.118.3 Attributes
Attribute Value
Severity Clear
venting normal operation of DIRP occurs in relation to the JF facility. A DIRP101 log is generated with full de-
tails regarding the cause of the alarm. See the Translations Guide for a description of DIRP and its use.
This alarm indicates that the Device Independent Recording Package (DIRP) subsystem is unable to open
the required number of journal files for recording.


The repair actions are variable depending on the cause of the alarm. Please refer to the generated DIRP101
log and the Log Report Reference for the DIRP101 log for full details.
3.119.3 Attributes
Attribute Value
Severity Clear
This USP M3UA alarm is raised when the path between the SCA and the SSG goes out of service.
This alarm indicates that the connection between the SCA and SSG is out of service.



Attempt to bring the resource inservice. If the condition persists, please contact next level support for assis-
tance.
3.120.3 Attributes
Attribute Value
Severity • Clear
• Critical
If a CCS7 route set goes SYSB or MANB, this alarm is raised and a CCS153 or CCS154 log is generated
with the details. A routeset may be manual busy or system busy because of
• faults in the peripheral modules that associate with the linksets in the routeset,
• faults on the links that associate with your office, or
• problems on the network.
This alarm indicates that a CCS7 route set is SYSB or MANB.


Bring any related Peripherals or Link Sets inservice and then attempt to bring the routeset inservice. If the
condition persists, contact next level support for assistance. For full details, refer to the Alarm and Perfor-
mance Monitoring Procedures (297-8021-543P1) document for clearing CCS RS critical alarms.

3.121.3 Attributes
Attribute Value
Severity • Clear
• Critical
CCS7 Local SubSystems are defined in table C7LOCSSN. When one of these local subsystems goes SYSB
or MANB, the switch raises this alarm and generates a CCS219 log with the details regarding the affected
subsystem.
This alarm indicates that a CCS7 Local SubSystem is SYSB or MANB.


Access the CCS7 MAP level and attempt to bring the affected subsystem inservice. For full details, refer to
the Alarm and Performance Monitoring Procedures (297-8021-543P1) document for clearing CCS LSSC crit-
ical alarms.
3.122.3 Attributes
Attribute Value
Severity • Clear
• Critical
CCS7 Remote SubSystems are defined in table C7NETSSN. When one of these remote subsystems goes
SYSB or MANB, the switch raises this alarm and generates a CCS213 or CCS214 log with the details re-
garding the affected subsystem.
This alarm indicates that a CCS7 Remote SubSystem is SYSB or MANB.



Access the CCS7 MAP level, and if there’s a critical point code alarm, attempt to clear it and then wait to see
if the remote subsystem alarm clears. If not, work with the remote office in an attempt to clear the alarm. For
full details, refer to the Alarm and Performance Monitoring Procedures (297-8021-543P1) document for
clearing CCS RSSC critical alarms.
3.123.3 Attributes
Attribute Value
Severity • Clear
• Critical
If a CCS7 point code goes SYSB, this alarm is raised and a CCS210 log is generated. Note that a point code
might be SYSB because a route set has gone SYSB, which would be indicated in the CCS210 log.
This alarm indicates that a CCS7 point code is SYSB.


Access the CCS7 MAP level, and if there’s a critical route set alarm, attempt to clear it and then wait to see if
the point code alarm clears. If not, attempt to bring the point code inservice. If unable to bring the point code
inservice, contact next level support for assistance. For full details, refer to the Alarm and Performance Moni-
toring Procedures (297-8021-543P1) document for clearing CCS PCC critical alarms.
3.124.3 Attributes
Attribute Value
Severity • Clear
• Critical


This USP M3UA alarm is raised when the path between the SCA and the SSG in trouble.
This alarm indicates that the connection between the SCA and SSG is in trouble.


If the condition persists, attempt to bring the resource inservice and contact next level support for assistance
if necessary.
3.125.3 Attributes
Attribute Value
Severity • Clear
• Major
If a CCS7 route set goes IsTb, this alarm is raised. A routeset may be IsTb because
• faults in the peripheral modules associated with the linksets in the routeset,
• faults on the links associated with your office,
• problems on the network, or
• problems within a network cluster.
The routeset can continue to carry traffic with the risk of a degraded level of service.
This alarm indicates that a CCS7 route set is IsTb.



Bring any related Peripherals or Link Sets inservice and then wait to see if the routeset returns to inservice. If
the condition persists, contact next level support for assistance. For full details, refer to the Alarm and Per-
formance Monitoring Procedures (297-8021-543P1) document for clearing CCS RS major alarms.
3.126.3 Attributes
Attribute Value
Severity • Clear
• Major
CCS7 Local SubSystems are defined in table C7LOCSSN. When one of these local subsystems goes IsTb,
the switch raises this alarm and generates a CCS231 log with the details regarding the affected subsystem.
This alarm indicates that a CCS7 Local SubSystem is IsTb (inservice trouble)


Access the CCS7 MAP level and investigate the cause of the inservice trouble condition. Wait for the alarm
to clear. If the alarm persists for an extended period of time, contact the next level of support to help investi-
gate the cause of the condition. For full details, refer to the Alarm and Performance Monitoring Procedures
(297-8021-543P1) document for clearing CCS LSSC major alarms.
3.127.3 Attributes
Attribute Value
Severity • Clear
• Major

If a CCS7 point code goes IsTb because of congestion on the routes between the office and the remote of-
fice represented by the point code, this alarm is raised and a CCS229 log is generated with the details.
This alarm indicates that a CCS7 point code is IsTb

This alarm is potentially service affecting. This alarm indicates traffic congestion on the routes between the
office and the remote office indicated by the point code. If this condition persists, and the congestion level is
too high, the can discard messages to the signalling point identified by the point code.

Access the CCS7 MAP level, and if there’s a minor route set alarm, attempt to clear it and then wait to see if
the point code alarm clears. If the condition persists, contact next level support for assistance. For full details,
refer to the Alarm and Performance Monitoring Procedures (297-8021-543P1) document for clearing CCS
PC minor alarms.
3.128.3 Attributes
Attribute Value
Severity • Clear
• Minor
This alarm indicates that there is a mismatch between the OM transfer periods of the SOS image and
KAIROS PM.


Change either the SOS or KAIROS PM collection Periods.

3.129.3 Attributes
Attribute Value
Severity • Clear
• Major
Probable cause Timing Problem
The KAIROS SOS Alarm Agent is likely clearing all alarms because of a loss of communication with the
MRF which makes it is impossible for the KAIROS SOS Alarm Agent to accurately maintain the state of
raised alarms.
This event indicates that the KAIROS SOS Agent has cleared all alarms.
This alarm is generated by the KAIROS SOS Alarm Agent.

The alarm severity is cleared since the application is clearing all alarms.

tacted.
3.130.3 Attributes
Attribute Value
Severity Clear
3.131 MtcAe1300
This alarm is raised when an Aggregate Ethernet interface is locked and cleared when the Aggregate Ether-
net interface is unlocked.
This alarm is classified as an equipment alarm, where the equipment represents an Aggregate Ethernet in-
terface.
Aggregate Ethernet interface.

This alarm has an original severity of minor.


Unlock the Aggregate Ethernet interface.
3.131.3 Attributes
Attribute Value
Severity Minor
Probable cause Out of Service
3.132 MtcAe1301
This alarm is raised when an Aggregate Ethernet interface is failed. Failure of an Aggregate Ethernet inter-
face can be caused by one or more Ethernet interface members failing, such that the minLinks can’t be satis-
fied.
terface.
Aggregate Ethernet interface

This alarm has an original severity of critical.

Repair member Ethernet interfaces. Contact your next level of support.
3.132.3 Attributes
Attribute Value
Severity Critical
Probable cause Equipment Malfunction
3.133 MtcAe1302
This alarm is raised when an Aggregate Ethernet interface is degraded. Degradation of an Aggregate Ether-
net interface can be caused by one or more Ethernet interface members failing, and minLinks is still satisfied.
terface.
Aggregate Ethernet interface.


This alarm has an original severity of major.

Repair member Ethernet interfaces. Contact your next level of support.
3.133.3 Attributes
Attribute Value
Severity Major
3.134 MtcAe1303
This alarm is raised when the minimum links configuration is not satisfied.
terface.


Configure more Ethernet interfaces to be members of the Aggregate Ethernet interface or change the mini-
mum links configuration of the Aggregate Ethernet interface. Contact your next level of support.
3.134.3 Attributes
Attribute Value
3.135 MtcAe1304
This alarm is raised when the number of enabled Ethernet interface members of the Aggregate Ethernet in-
terface does not satisfy the minimum links configuration.
terface.



Repair member Ethernet interfaces so that the minimum links configuration is satisfied. Contact your next
level of support.
3.135.3 Attributes
Attribute Value
3.136 MtcAppBld1300
This is an application blade locked alarm.
This alarm is raised when the application blade locked by a user.
This is an application blade out of service alarm.

This alarm is an initially minor alarm. The alarm severity can be updated to major. The alarm severity is
passed in via the OAM FM Library API only.

The following actions can be taken to clear the alarm:
1. Offline the blade in the case that the blade is to be replaced; or
2. Unlock the blade to return it to service.
3.136.3 Attributes
Attribute Value
Severity • Minor
• Major

3.137 MtcAppBld1301
This is an application blade boot failure alarm.
This alarm is raised when the application blade failed to boot.
This is an application blade configuration error alarm.

This alarm is service affecting. The alarmed blade does not provide service.

1. Check recently applied patches or software changes for the blade.
2. Run hardware app-blade test command to test the hardware on the blade.
3. Replace the blade if the blade does not return to service.
4. Contact your next level of support if the problem persists.
3.137.3 Attributes
Attribute Value
Severity Critical
3.138 MtcAppBld1302
This is an application blade temperature high alarm.
This alarm is raised when the application blade temperature is reaching the top of the operating range al-
lowed for the blade.
This event indicates that the blade temperature is reaching the top of the operating range allowed for the
blade.

This alarm is a minor alarm. The alarm severity is passed in via the OAM FM Library API only.

1. Check room temperature to ensure that the temperature is within the specified operating
range for the equipment.
2. Check to ensure that the shelf Fan Try Modules are functioning properly.

3.138.3 Attributes
Attribute Value
Severity Minor
Probable cause Temperature Unacceptable
3.139 MtcAppBld1303
This is an application blade voltage high alarm.
This alarm is raised when the application blade voltage is reaching the top of the operating range allowed for
the blade.
This event indicates that the blade voltage is reaching the top of the operating range allowed for the blade.


1. Check that the shelf Power Entry Modules are functioning properly.
2. Replace the Power Entry Module if required.
3. Check that the power feeds into the Power Entry Modules are in the correct voltage and cur-
rent operating range.
4. Correct any issues found.
5. Replace the Blade.
3.139.3 Attributes
Attribute Value
Severity Critical
Probable cause Power Problem

3.140 MtcAppBld1304
This is an application blade current out of range alarm.
This alarm is raised when the application blade current is reaching the top of the operating range allowed for
the blade.
This event indicates that the blade current is reaching the operating threshold.


3.140.3 Attributes
Attribute Value
Severity Critical
3.141 MtcAppBld1305
This is an application blade failure alarm.
This alarm is raised when the application blade malfunctioning and not providing service.
This event indicates that the blade failed to provide service.



1. Replace the blade.
3.141.3 Attributes
Attribute Value
Severity Critical
3.142 MtcAppBld1306
This is an application blade malfunction alarm.
This alarm is raised when the application blade malfunctioning.
This event indicates that the blade is malfunctioning.

This alarm is a major alarm. The alarm severity is passed in via the OAM FM Library API only.

1. Replace blade at the next available service window.
3.142.3 Attributes
Attribute Value
Severity Major
3.143 MtcAppBld1307
This is an application blade failure alarm.
This alarm is raised when the application blade malfunctioning and not providing service.
This event indicates that the application blade has reported a service-affecting fault condition.



1. Replace the blade if alarm persists.
2. Contact your next level of support for further analysis.
3.143.3 Attributes
Attribute Value
Severity Critical
3.144 MtcAppBld1308
This is an application blade platform failure alarm.
This alarm is raised when a non service-affecting platform service on the application blade fails and is not
providing service.
This event indicates that a non service-affecting platform service is unavailable on the blade.

This alarm is not service-affecting.
This alarm is major. The alarm severity is passed in via the OAM FM Library API only.

The alarm should clear by itself. Contact your next level of support if the problem persists.
3.144.3 Attributes
Attribute Value
Severity Major
Probable cause Software Program Error

3.145 MtcAppBld1309
This is an application blade platform failure alarm.
This alarm is raised when a critical platform service on the application blade fails and is not providing service.
This event indicates that a service-affecting platform service is unavailable on the blade.

This alarm is service-affecting.
This alarm is major. The alarm severity is passed in via the OAM FM Library API only.

The alarm should clear by itself. Contact your next level of support if the problem persists.
3.145.3 Attributes
Attribute Value
Severity Major
3.146 MtcAppBld1390
This is an alarm clear all event.
This event indicates that all maintenance alarms are cleared.

This alarm is informational. The alarm severity is passed in via the OAM FM Library API only.

No repair action required.
3.146.3 Attributes
Attribute Value

3.147 MtcCpu1300
This is a CPU Load Average crossed threshold alarm.
This alarm is raised when the CPU Load Average crossed the defined threshold.
This is an CPU load average threshold crossed alarm.

This alarm is an initially minor alarm. The alarm severity is passed in via the OAM FM Library API only.

This alarm should be transitory. If this alarm persists please contact your next level of support for further
analysis.
3.147.3 Attributes
Attribute Value
Severity Minor
3.148 MtcCpu1301
This is a CPU Utilization crossed threshold alarm.
This alarm is raised when the CPU Utilization crossed the defined threshold.
This is a CPU utilization threshold crossed alarm.


This alarm should be transitory. If this alarm major please contact your next level of support for further analy-
sis.

3.148.3 Attributes
Attribute Value
Severity Minor
3.149 MtcDisk1300
This is a disk locked alarm.
This alarm is raised when the disk locked by a user.
This is a disk out of service alarm.
The disk is configured in table disk.

This alarm is not service affecting, but does affect redundancy of the system.

1. Offline the blade that houses the disk, in the case that the disk is to be replaced; or
2. Unlock the disk to return it to service.
3.149.3 Attributes
Attribute Value
Severity • Minor
• Major
3.150 MtcDisk1301
This is a disk temperature high alarm.
This alarm is raised when the disk temperature has reached the top of the operating range allowed for the
disk.
This event indicates that the disk temperature has reached the top of the operating range allowed for the disk



1. Check room temperature to ensure that the temperature is within the specified
operating range for the equipment.
3.150.3 Attributes
Attribute Value
Severity Critical
Type Environmental Alarm
Probable cause Heating or Ventilation or Cooling
System Problem
3.151 MtcDisk1302
This is a disk malfunction alarm.
This alarm is raised when the disk malfunctioning.
This event indicates that the disk is malfunctioning.


1. Replace blade that houses the disk at the next available service window.
3.151.3 Attributes
Attribute Value
Severity Major

3.152 MtcDisk1303
This is a disk off-duty alarm.
This alarm is raised when the disk is coming into service, but is not yet finished initialization
This event indicates that the disk is reporting that it is not ready to provide service.

This alarm is not service affecting, but does impact redundancy.

1. Allow 5 minutes to see if the problem clears itself - this state should be transitory.
2. Attempt to lock and unlock the disk.
3.152.3 Attributes
Attribute Value
Severity Major
3.153 MtcDisk1304
This is a disk self test alarm.
This alarm is raised when the disk has failed a self test.
This event indicates that the disk has failed a self test.


1. Offline the blade that houses the disk to be repaired and replace the disk blade.

3.153.3 Attributes
Attribute Value
Severity Major
Type Integrity Violation
Probable cause Input/Output Device Error
3.154 MtcDisk1305
This is a disk write error count alarm.
This alarm is raised when the disk has failed to write data correctly.
This event indicates that the disk has failed to write data correctly.


3.154.3 Attributes
Attribute Value
Severity Major
3.155 MtcDisk1306
This is a disk read error count alarm.
This alarm is raised when the disk has failed to read data correctly from the disk.
This event indicates that the disk has failed to read data correctly.



3.155.3 Attributes
Attribute Value
Severity Major
3.156 MtcDisk1307
This is a disk sensor scan alarm.
This alarm is raised when the disk has failed to supply the requested sensor data.
This event indicates that the disk has failed to provide sensor data within an acceptable time frame.

This alarm may be service affecting if multiple disks are unreachable simultaneously.

The most likely cause is a connectivity issue between the disk blade and the application blade. Verify that the
SCSI cables are connected as documented, that the SCSI terminator is attached to the correct location, and
that the rear transition modules on the disk blade and application blade are secure.
3.156.3 Attributes
Attribute Value
Severity Major
3.157 MtcDisk1308
This is a disk read failed alarm.
This alarm is raised when the disk has failed.
This event indicates that the disk has failed.


This alarm can be service affecting, and impacts redundancy.

3.157.3 Attributes
Attribute Value
Severity Critical
3.158 MtcDisk1309
This is a disk degraded alarm.
This alarm is raised when the disk is degraded.
This event indicates that the disk is functional, but not operating optimally.

This alarm can be service affecting, and will likely impact system performance.

3.158.3 Attributes
Attribute Value
Severity Major
Probable cause Performance Degraded

3.159 MtcDisk1310
This is a disk degraded alarm.
This alarm is raised when the disk is degraded due to a disk mirror rebuild.
This event indicates that the disk is functional, but not operating optimally since a disk mirror is in progress to
restore redundancy.

This alarm is not service affecting, but does degrade system performance.

No repair action required. After the disk completes the mirror rebuild process this alarm will clear. To sup-
press the alarm prior to the completion of the rebuild, the following action can be taken:
1. Offline the blade that houses the disk.
3.159.3 Attributes
Attribute Value
Severity Major
3.160 MtcDisk1311
This is a disk read failed alarm.
This alarm is raised when the disk mirroring has failed.
This event indicates that disk mirroring has failed.

This alarm can be service affecting, and impacts redundancy.


3.160.3 Attributes
Attribute Value
Severity Critical
3.161 MtcEth1300
This alarm is raised when an Ethernet interface is locked and cleared when the Ethernet interface is un-
locked.
This alarm is classified as an equipment alarm, where the equipment represents an Ethernet interface.
Ethernet interface.

This alarm has an original severity of minor.

Unlock the Ethernet interface.
3.161.3 Attributes
Attribute Value
Severity Minor
3.162 MtcEth1301
This alarm is raised when an Ethernet interface is failed.
Ethernet interface.

This alarm has an original severity of critical.


Verify Ethernet interface link cabling. Check link partner. Replace Ethernet interface link cabling. Contact
3.162.3 Attributes
Attribute Value
Severity Critical
3.163 MtcEth1302
This alarm is raised when an Ethernet interface is degraded.
Ethernet interface.

This alarm has an original severity of major.

Verify Ethernet interface link cabling. Check link partner. Replace Ethernet interface link cabling. Contact
3.163.3 Attributes
Attribute Value
Severity Major
3.164 MtcFtm1300
This is a Fan Tray Module voltage high alarm.
This alarm is raised when the Fan Tray Module voltage is reaching the top of the operating range allowed for
the Fan Tray Module.
This event indicates that the Fan Tray Module voltage is reaching the top of the operating range allowed for
the Fan Tray Module



5. Replace the Fan Tray Module.
3.164.3 Attributes
Attribute Value
Severity Critical
3.165 MtcFtm1301
This is a Fan Tray Module failure alarm.
This alarm is raised when the Fan Tray Module malfunctioning and not providing service.
This event indicates that the Fan Tray Module failed to provide service.
The Fan Tray is configured in table pem.


1. Replace the Fan Tray Module.

3.165.3 Attributes
Attribute Value
Severity Critical
3.166 MtcFtm1302
This is a Fan Tray Module degraded alarm.
This alarm is raised when the Fan Tray Module malfunctioning.
This event indicates that the Fan Tray Module is malfunctioning.
The Fan Tray Module is configured in table pem.


1. Replace Fan Tray Module.
3.166.3 Attributes
Attribute Value
Severity Major
3.166.4 MtcLowMem1300 - Low Memory usage report

Low Memory usage report.
This is a low memory usage crossed threshold alarm.
This alarm is raised when the usage crossed the threshold for critical low memory resource level.

This alarm indicates there are potential impacts to service.


analysis.
analysis.
3.166.7 Attributes
Attribute Value
Log name MtcLowMem1300
Severity Critical
Associated component System Maintenance application
3.167 MtcMem1300
This is a memory usage crossed threshold alarm.
This alarm is raised when the usage crossed the defined threshold.
This is a memory usage threshold crossed alarm.


analysis.
3.167.3 Attributes
Attribute Value
Severity Minor
Attribute Value

3.168 MtcPem1300
This is an Power Entry Module temperature high alarm.
This alarm is raised when the Power Entry Module temperature is reaching the top of the operating range al-
lowed for the Shelf and Alarm Manager.
This event indicates that the Power Entry Module temperature is reaching the top of the operating range al-
lowed for the power entry module.
The power entry module is configured in table pem.


3.168.3 Attributes
Attribute Value
Severity Critical
3.169 MtcPem1301
This is a Power Entry Module voltage high alarm.
This alarm is raised when the Power Entry Module voltage is reaching the top of the operating range allowed
for the Power Entry Module.
This event indicates that Power Entry Module voltage is reaching the top of the operating range allowed for
the Power Entry Module.
The Power Entry Modules configured in table app_blade.



2. Replace the Power Entry Module if required

3.169.3 Attributes
Attribute Value
Severity Critical
Attribute Value
3.170 MtcPem1302
This is a Power Entry Module current out of range alarm.
This alarm is raised when the Power Entry Module current is reaching the top of the operating range allowed
for the blade.
This event indicates that the Power Entry Module current is reaching the operating threshold.
The Power Entry Module is configured in table app_blade.



3.170.3 Attributes
Attribute Value
Severity Critical
3.171 MtcPem1303
This is a Power Entry Module failure alarm.
This alarm is raised when the Power Entry Module malfunctioning and not providing service.
This event indicates that the Power Entry Module failed to provide service.
The Power Entry Module is configured in table pem.


1. Replace the Power Entry Module.
3.171.3 Attributes
Attribute Value
Severity Critical
3.172 MtcPem1304
This is a Power Entry Module degraded alarm.
This alarm is raised when the Power Entry Module malfunctioning.
This event indicates that the Power Entry Module is malfunctioning.



1. Replace Power Entry Module.
3.172.3 Attributes
Attribute Value
Severity Major
3.173 MtcPem1305
This is a Power Entry Module failure alarm.
This alarm is raised when the Power Entry Module malfunctioning and not providing service.
This event indicates that the Power Entry Module failed to provide service.


1. Check the Power Entry Module input voltage feed.
3.173.3 Attributes
Attribute Value
Severity Critical
3.174 MtcRAMDisk1300
This is a RAM disk usage crossed threshold alarm.
This alarm is raised when the RAM disk usage crossed the defined threshold.
This is a RAM Disk Usage threshold crossed alarm.



analysis.
3.174.3 Attributes
Attribute Value
Severity Minor
3.175 MtcSam1300
This is a Shelf and Alarm Manager locked alarm.
This alarm is raised when the Shelf and Alarm Manager locked by a user.
This is an Shelf and Alarm Manager out of service alarm.
The Shelf and Alarm Manager is configured in table app_blade.


1. Offline the Shelf and Alarm Manager in the case that the Shelf and Alarm Manager is to be
replaced; or
2. Unlock the Shelf and Alarm Manager to return it to service.
3.175.3 Attributes
Attribute Value
Severity • Minor
• Major

3.176 MtcSam1301
This is a Shelf and Alarm Manager temperature high alarm.
This alarm is raised when the Shelf and Alarm Manager temperature is reaching the top of the operating
range allowed for the Shelf and Alarm Manager.
This event indicates that the Shelf and Alarm Manager temperature is reaching the top of the operating
range allowed for the Shelf and Alarm Manager.

This alarm is a minor alarm. The alarm severity is passed in via the OAM FM Library API only.

3.176.3 Attributes
Attribute Value
Severity Minor
3.177 MtcSam1302
This is a Shelf and Alarm Manager voltage high alarm.
This alarm is raised when the Shelf and Alarm Manager voltage is reaching the top of the operating range al-
lowed for the Shelf and Alarm Manager.
This event indicates that Shelf and Alarm Manager voltage is reaching the top of the operating range allowed
for the Shelf and Alarm Manager.
Shelf and Alarm Manager is configured in table app_blade.




3.177.3 Attributes
Attribute Value
Severity Critical
3.178 MtcSam1303
This is a Shelf and Alarm Manager failure alarm.
This alarm is raised when the Shelf and Alarm Manager malfunctioning and not providing service.
This event indicates that the Shelf and Alarm Manager failed to provide service.
The Shelf and Alarm Manager is configured in table sam.


1. Replace the blade.
3.178.3 Attributes
Attribute Value
Severity Critical
3.179 MtcSam1304
This is a Shelf and Alarm Manager malfunction alarm.

This alarm is raised when the Shelf and Alarm Manager malfunctioning.
This event indicates that the Shelf and Alarm Manager is malfunctioning.
The Shelf and Alarm Manager is configured in table sam.


1. Replace Shelf and Alarm Manager.
3.179.3 Attributes
Attribute Value
Severity Major
Attribute Value
3.180 MtcWDT1300
This is a watchdog hard reset alarm.
This alarm is raised when the watchdog timer expired and the blade has been reset.
This is a watchdog hard reset alarm.

This alarm is an initially critical alarm. The alarm severity is passed in via the OAM FM Library API only.

1. Perform the aim service-unit swact on the applications on the blade to remove
service.
2. Perform the aim service-unit jam command to ensure that applications do not return to the
blade.
3. Perform the hardware app-blade test command and ensure that the blade returns to service
4. Perform the aim service-unit unjam command for the applications on the blade.
5. Contact your next level of support for further analysis.

3.180.3 Attributes
Attribute Value
Severity Critical
3.181 MtcZombie1300
This is a Zombie Processes crossed threshold alarm.
This alarm is raised when the Zombie Processes crossed the defined threshold.
This is a Zombie Processes threshold crossed alarm.


analysis.
3.181.3 Attributes
Attribute Value
Severity Minor
3.182 NTP1300
Possible alarms are:
1. NTP synchronizing,
2. Starting time synchronizing software,
3. Out-of-service condition for time-sync: re-reading NTP configuration,
4. NTP synchronizing, selected server responding with offset greater than 500ms. See Addi-
tional Text for more alarms.
Other alarms are:
5. NTP is not synchronized, selected server responding with offset greater than 500ms,
6. NTP is not synchronized, no servers are responding,

7. Could not start time synchronizing software,

8. No NTP servers are defined,
9. NTP is not synchronized with some servers/peers,
10. Error while reading NTP configuration or status.
This is a NTP alarm.

This alarm can a warning, minor, or major alarm depending on the state of the ntp server.

See reason text.
3.182.3 Attributes
Attribute Value
Severity • Minor
• Major
3.183 NTP1301
This is a log for the Alarm Clear ALL event.
This is a NTP log for the clear all alarm event.

Warning

There is no required Repair Action.
3.183.3 Attributes
Attribute Value

3.184 PmCentral1300 - Failed to transfer a file to a remote host

Failed to transfer a file to a remote host.
The specified file could not be transferred to the specified remote host.
The default system entity is used.

This alarm indicates there are no impacts to service.

1. Check communications between Data Manager and the remote host,
2. Check settings of remote host.
1. Verify that the user is enabled on the remote host.
2. Verify that the protocol ftp/sftp is supported on the remote host and is
available for the user.
3. Verify that the pmreports directory is created off of the user mode directory on the re-
mote host.
4. Verify that the user has write permission to the pmreports directory on the remote host.
5. Verify that disk usage in the pmreports directory is not at or near 100%
usage or that any disk quota has not been exceeded.
6. Verify that the Data Manager and the remote host can talk to one another over the net-
work using the selected protocol.
3.184.3 Attributes
Attribute Value
Log name PmCentral1300
Severity Minor
Associated PmCentral application
component
3.185 SCA1300
Call Agent NFS inactive core indicator key
Niikey is used by Kapsch Installation Services personnel during cutover procedures. It indicates that a Net-
work Filesystem (NFS) inactive core indicator key (Niikey) was detected. If a call processing application re-
start occurs while the Niikey is set, the application will be prevented from becoming the active instance.
This alarm indicates that a cutover procedure is in progress.
Niikey is configured in the SCA configuration data model for the ’sca’ entity. For duplex systems, it is data-
filled based on the niikey setting for the ’sca-sg’ entity. On simplex systems, it is datafilled based on the nii-

key setting for the ’sca-su’ entity.

This alarm is not service affecting. It indicates loss of redundancy of the call processing application during a
cutover procedure.
The alarm severity is initially major. Once raised, it cannot be updated, only cleared. The alarm is raised or

If a cutover is not in progress and this alarm appears, contact your next level of support. Otherwise, at the
end of the cutover procedure, use the cli to disable Niikey.
3.185.3 Attributes
Attribute Value
Severity • Clear
• Major
3.186 SCA1301
Call Agent out of synchronization
This alarm indicates loss of sparing of the call processing application This alarm indicates that the call pro-
cessing applications are out of synchronization.
Sync is configured in the SCA configuration data model for the ’sca’ entity as a field with the name ’sync-
state’.

This alarm is not service affecting. It indicates loss of sparing between the call processing applications.

Investigate cause of out of sync condition. Then, use cli command to sync the call processing application.
3.186.3 Attributes
Attribute Value
Severity • Clear
• Major

3.187 SCA1302
Call Agent is undergoing a RExTst. The RExTst can be initiated manually from the cli, or by the system.
RExTst has two flavors: base or full. Base RExTst steps: image test and sync. Full RExTst steps: image test,
hardware diagnostics and board reset, sync, swact, and sync. Base SRExTst is usually scheduled 6 times a
week at night during low traffic. Full SRExTst is scheduled once per week. Manual RExTst can be run by
craft at any time.
This alarm indicates that the inactive call processing application instance is undergoing a Routine EXercise
Test.
RExTst is not configured in the sca data model.

This alarm is not service affecting. It indicates loss of redundancy of the call processing applications during
the RExTst.

No manual action required. The alarm clears once the RExTst completes.
3.187.3 Attributes
Attribute Value
Severity • Clear
• Major
3.188 SCA1303
One or more manual or system-initiated Call Agent RExTst has failed or manually aborted.
This alarm is raised if any of the steps involved in the manual or system RExTst fails.
This alarm indicates one or more failed or manually aborted Routine EXercise Test of the inactive call pro-
cessing application instance.
RExFlt is not configured in the sca data model.

This alarm is not service affecting. It indicates a failed RExTst of the inactive call processing application in-
stance. Consequently, the unit might not be healthy enough to become the active instance if needed.


Review office records to determine if the fault has occurred in the past. Run a manual RExTst during a peri-
od of low traffic to determine if the fault is intermittent. The alarm clears after a successful RExTst (manual of
system initiated).
3.188.3 Attributes
Attribute Value
Severity • Clear
• Major
3.189 SCA1304
Call Agent RExTst was not automatically scheduled by the system in the last 7 days.
Once a RExTst is automatically scheduled by the system, the alarm clears.
This alarm indicates that RExTst was not automatically scheduled by the system in the last 7 days.
RExSch is not configured in the sca data model.

This alarm is not service affecting. It indicates that the system will less likely to automatically test the sanity
of the inactive call processing application instance.
The alarm severity is initially minor. Once raised, it cannot be updated, only cleared. The alarm is raised or

Check IOAU112 SOS log reports to see if system RExTst has been disabled. If it has, no action required. If
system RExTst has not been disabled, edit SOS table REXSCHED so that automatic scheduling of RExTst
is resumed.
3.189.3 Attributes
Attribute Value
Severity • Clear
• Minor
3.190 SCA1305
Call Agent ImgTst in progress
ImgTst can be manually initiated from the cli, or as part of a manual or system RExTst. During ImgTst, all re-

start flavors are performed on the inactive call processing application instance (warm, cold, and reload).
This alarm indicates that the inactive call processing application instance is undergoing a software image
test.
ImgTst is not configured in the sca data model.

This alarm is not service affecting. It indicates loss of redundancy of the call processing applications during
the ImgTst.

No manual action required. The alarm clears once the ImgTst completes.
3.190.3 Attributes
Attribute Value
Severity • Clear
• Major
3.191 SCA1306
One or more ImgTst has failed. The ImgTst can be manually initiated from the cli, or as part of a system or
manual RExTst.
This alarm is raised if the inactive call processing application instance cannot be successfully restarted
(warm, cold, or reload).
This alarm indicates a failed software image test of the inactive call processing application instance.
This alarm indicates a failed software image test of the inactive call processing application instance.

This alarm is not service affecting. It indicates a failed ImgTst of the inactive call processing application in-
stance. Consequently, the unit might not be healthy enough to become the active instance if needed.

The alarm clears once a successful ImgTst completes. The ImgTst can be manually initiated from the cli, or
as part of a system or manual RExTst. Run a manual ImgTst during a period of low traffic to determine if the
fault is intermittent. The alarm clears after a successful ImgTst.

3.191.3 Attributes
Attribute Value
Severity • Clear
• Major
3.192 SCA1307
Call Agent Application Out of Service
This alarm is raised if the call processing application instance is out of service.
This alarm indicates that the call processing application instance is out of service.

This alarm is service affecting for the active call processing application instance.
The alarm severity is initially critical on the active side, and minor on the standby side. Once raised, it cannot
be updated, only cleared. The alarm is raised or cleared via the OAM FM Library API only.

The alarm clears once the call processing application instance is in service.
3.192.3 Attributes
Attribute Value
Severity • Clear
• Minor
• Critical
3.193 SCA1308
Low memory condition of the call processing application instance.
This alarm is raised during a low memory condition of the call processing application instance.
This alarm indicates a low memory condition of the call processing application instance.

The alarm severity can be either critical, major, or minor. Once raised, the severity can be updated or

cleared. The alarm is managed via the OAM FM Library API only.

The alarm clears once the memory usage of the call processing application resumes to normal.
3.193.3 Attributes
Attribute Value
Severity • Clear
• Minor
• Major
• Critical
3.194 ScaDdm1300
This alarm is set when Data Dictionary Manager is just started allocating resources and setting up the con-
nection but not yet become active This alarm indicates that the DDM is not ready to provide service This
alarm is generated with the entity Type as sos-agent.

This alarm is not service affecting, but indicates that Data Dictionary manager is not in service.
This alarm is a critical alarm.

Allow 10 to 15 minutes to see if the alarm clears. Contact your next level of support if the alarm not clears.
3.194.3 Attributes
Attribute Value
Severity Critical
3.195 ScaDdm1301
The mkdir is failed to create the directory for storing the data dictionary.
This alarm indicates that the creation of the data directory is failed.
This alarm is generated with the entity Type as sos-agent.


This alarm is a major alarm.

Allow 5 mins to see if the alarm clears, because application will keep retrying.Contact your next level of sup-
port if the alarm not clears.
3.195.3 Attributes
Attribute Value
Severity Major
3.196 ScaDdm1302
This alarm is set when there is no connection between Data Dictionary Manager and the CallAgent.
This alarm indicates that the connection between the DDM and CA is broken or not established.


3.196.3 Attributes
Attribute Value
Severity Critical
3.197 ScaDdm1303
This alarm is set when the Data Dictionary is not available and might have started downloading the data dic-
tionary from the CallAgent.
This alarm indicates that the DDM is started downloading the Data Dictionary, but not yet downloaded com-

pletely.

This alarm is service affecting, as the Data Dictionary manager is not in service.

3.197.3 Attributes
Attribute Value
Severity Critical
3.198 ScaDdm1304
All the alarms got cleared now and Data Dictionary Manager is in service.
3.198.1 Attributes
Attribute Value
3.199 ScaDdm1305
This is for clearing any alarms found when this component goes to standby.
3.199.1 Attributes
Attribute Value
3.200 ScaLaq1301
This alarm is raised when the communication between LAQ and the FM Agent is not established.
This alarm indicates that LAQ will not be in service as the FM Agent is not connected.


This alarm is a serviceAffecting.
This alarm is a major one.

No Repair action is required; Contact your next level of support if the alarm not clears.
3.200.3 Attributes
Attribute Value
Severity Major
3.201 ScaLaq1302
This alarm is raised when the communication between LAQ and the Call Agent is not established.
This alarm indicates that LAQ will not be in service as the communication with CA is not established.


No Repair action is required; Contact your next level of support if the alarm not clears.
3.201.3 Attributes
Attribute Value
Severity Major
3.202 ScaLaq1303
This alarm is raised when the CA Log device is not configured.

This alarm indicates that CA log device is not connected.



No Repair action is required.
3.202.3 Attributes
Attribute Value
Severity Major
3.203 ScaLaq1304
All the alarms are cleared and LAQ is in service.
All alarms have been cleared.
3.203.1 Attributes
Attribute Value
3.204 ScaLaq1305
3.204.1 Attributes
Attribute Value
3.205 ScaOma1300
This alarm is set when OM Access Server is just started allocating resources and setting up the connection

but not yet become active.

This alarm will be raised during the startup of the OM Access.

This alarm is service affecting if the condition persists for an extended period of time.

No repair action is required.
3.205.3 Attributes
Attribute Value
Severity Major
3.206 ScaOma1301
This alarm is set when the OM Access connection to the Data Dictionary Manager is lost.
This alarm will be raised when the connection between OM Access and Data Dictionary Manager is down.


3.206.3 Attributes
Attribute Value
Severity Major

3.207 ScaOma1302
This alarm is set when the Data Dictionary is not available and will be cleared when the Data Dictionary
download is completed.
This alarm will be raised when the Data Dictionary is not available.


3.207.3 Attributes
Attribute Value
Severity Major
3.208 ScaOma1303
This alarm is set when the corresponding OM group schema is not available.
This alarm will be raised when the OM Group schema is not available.


3.208.3 Attributes
Attribute Value
Severity Major

3.209 ScaOma1304
This alarm is set when the OM Access connection to the OMAMGMT process goes down.
This alarm will be raised when the connection between OM Access and the corresponding process
(omamgmt) from CA goes down.


3.209.3 Attributes
Attribute Value
Severity Major
3.210 ScaOma1305
This alarm is raised when the OM Access connection to the OMARPT process goes down.
This alarm will be raised when the connection between OM Access and the corresponding process (omarpt)
from CA goes down.



3.210.3 Attributes
Attribute Value
Severity Major
3.211 ScaOma1306
This alarm is set when all the alarms got cleared and OM Access is now in service.
3.211.1 Attributes
Attribute Value
3.212 ScaOma1307
3.212.1 Attributes
Attribute Value
3.213 ScaTam1300
This alarm is set when Table Manager is just started allocating resources and setting up the connection but
not yet inservice.
This alarm indicates that the Table Manager is not ready to provide service.



3.213.3 Attributes
Attribute Value
Severity Critical
3.214 ScaTam1301
The Call Agent is not available.
This alarm indicates that the CA is not available.


3.214.3 Attributes
Attribute Value
Severity Critical
3.215 ScaTam1302
This alarm is set when the Data Dictionary is not available and might have started downloading from the CA.
This alarm indicates that the Data Dictionary is not available.

This alarm is not service affecting, but indicates that Table manager is not in service.


3.215.3 Attributes
Attribute Value
Severity Critical
3.216 ScaTam1303
This alarm is raised when the Table Access Manager connection to the CallAgent is lost.
This alarm indicates that the connection between Table Manager and Call Agent is lost.


3.216.3 Attributes
Attribute Value
Severity Critical
3.217 ScaTam1304
All the alarms got cleared now and Table Manager is in service.
3.217.1 Attributes
Attribute Value
3.218 ScaTam1305

3.218.1 Attributes
Attribute Value
3.219 Storage1330
The alarmed Volume Manager is not synchronized with the Volume Manager on the other Data manager.
Quality of service is degraded.
Storage Service is managed by the system. It cannot be enabled or disabled by the customer.

This is a major alarm.

This alarm indicates that this Volume Manager could not communicate with its counterpart located on the
other Data manager. If this alarm persists, contact your next level of support.
3.219.3 Attributes
Attribute Value
Severity Major
3.220 Storage1331
Volume group low on free space.

This alarm is initially a minor alarm. It may be updated to major or critical.

The following steps may be taken, and are required when the alarm is major or critical:
1. Backup and remove larger file systems.
2. Add new smaller file systems.

3.220.3 Attributes
Attribute Value
Severity • Minor
• Major
• Critical
Probable cause Storage Capacity Problem
3.221 Storage1332
File-system used blocks exceeded threshold.

This alarm is service affecting for every application that writes to this file system. When the alarm is critical, it
may result in a loss of data.

1. Increase size of the alarmed file system.
2. Remove files within the file system.
3.221.3 Attributes
Attribute Value
Severity • Minor
• Major
• Critical
3.222 Storage1333
File-system used inodes exceeded threshold.


This alarm is service affecting for every application that writes to this file system. It may result in a loss of da-
ta.

1. Increase size of file system.
2. Remove files within file system.
3.222.3 Attributes
Attribute Value
Severity • Minor
• Major
• Critical
3.223 Storage1334
File-system failed.
Either a software error occurred or both disks have faulted.

This alarm is service affecting for every application that reads or writes from this file system.
This is a critical alarm.

1. If the disk is failed replace the disk.
3.223.3 Attributes
Attribute Value
Severity Critical

3.224 Storage1335
Replicated file-system trouble.

This may be a minor, major, or critical alarm.

Synchronization in progress, no action required. If disk is failed, replace the disk. If alarm persists, contact
3.224.3 Attributes
Attribute Value
Severity • Minor
• Major
• Critical
3.225 Storage1380
This is a log for the Storage Alarm Clear ALL By Location event.
This is a Storage log for the clear all alarm by location event.

Warning

There is no required Repair Action.
3.225.3 Attributes
Attribute Value

3.226 TimeZone1300
This is a Time zone alarm.
An alarm is raised when the overall system time zone is not set.
The system time zone is configured in the System Time zone Table. This is the overall time zone for the
frame.

This alarm is critical alarm and does not change.

1. From the cli, check to see whether there is an entry in system-time zone.
2. If there is no entry, add the entry to the system-time zone. If this alarm does not clear, contact
3.226.3 Attributes
Attribute Value
Severity Critical
3.227 TimeZone1301
An alarm is raised when a change to either the system time zone or override time zone for a specific card
has not been updated.
The system time zone is configured in the System Time zone Table while the over-ride time zone is config-
ured in the Over-ride Time zone Table.

This alarm is a major alarm and does not change.

1. From the cli, check to see what is provisioned for that specific card location.
2. Modify the entry in the cli once again, and if this alarm is does not clear, contact your next

level of support.
3.227.3 Attributes
Attribute Value
Severity Major
3.228 USM1300
A software ID could not be applied.
KAIROS Software Apply
This is the SoftwareID which identifies the software to be applied.

The softwareID is not successfully applied.
This alarm is to inform that a software parcel was not successfully applied.

Reapply would be required after determining problem or contact your next level of support.
3.228.3 Attributes
Attribute Value
3.229 USM1301
Software ID could not be uninstalled.
KAIROS Software Remove.
This is the SoftwareID identifying the software to be uninstalled.

The softwareID is not successfully uninstalled.
This alarm is to inform that a software parcel has not been successfully uninstalled.


3.229.3 Attributes
Attribute Value
3.230 USM1302
Software ID could not be rollbacked.
KAIROS Software Rollback
This is the SoftwareID identifying the software to be rollbacked.

The softwareID is not successfully rollbacked.
This alarm is to inform that a software parcel was not successfully rollbacked.

3.230.3 Attributes
Attribute Value
3.231 USM1303
Software ID can not be registered.
KAIROS Software Checker
This is the SoftwareID identifying the software to be registered.

The softwareID can not be registered.
This alarm is to inform that a software parcel can not be registered to database.

3.231.3 Attributes
Attribute Value

3.232 USM1304
Indicates backup operation is in progress.
KAIROS Software Backup
KAIROS Software Backup

Provisioning is not allowed.
This alarm is to inform that the backup operation is in progress.
3.232.2 Attributes
Attribute Value
3.233 USM1305
Indicates backup operation has failed.
KAIROS Software Backup Failure.
KAIROS Software Backup Failure.

No service impact.
This alarm is to inform that the backup operation has failed.
3.233.2 Attributes
Attribute Value
3.234 USM1306
Indicates restore operation is in progress.
KAIROS Software Restore.
KAIROS Software Restore.

Provisioning is not allowed.
This alarm is to inform that the restore operation is in progress.


3.234.3 Attributes
Attribute Value
3.235 USM1307
Indicates restore operation has failed.
KAIROS Software Restore Failure.
KAIROS Software Restore Failure.

This alarm is to inform that the restore operation has failed.

3.235.3 Attributes
Attribute Value
3.236 USM1308
A software upgrade is currently in progress on the KAIROS.
The KAIROS base system software or some application software is currently being upgraded on the system.
KAIROS Software Upgrade.
Software Upgrade.

No service affecting condition is noted by this alarm.
This alarm just informs that a software upgrade is currently in progress on the KAIROS platform.

None required. This alarm is for informational purposes only.
3.236.3 Attributes
Attribute Value

3.237 USM1309
Software is not in sync on this system. New software may have been applied on some blades but not on oth-
ers. Action may be required to correct this situation.

Minor severity indicates that a software parcel operation is currently in progress. Major severity indicates that
a software parcel operation has failed and action is required.

3.237.3 Attributes
Attribute Value
3.238 USM1310
Software upgrade in progress.

This alarm is to inform that a software upgrade is in progress.

3.238.3 Attributes
Attribute Value

4 KAIROS based HLR alarms reference

This section provides a reference for the KAIROS alarms for the HLR22 release.
4.1 HLR1300
HLR Network File System Inactive core Indicator Key (Niikey). This alarm is raised when Niikey is enabled
for the HLR application during a cutover procedure.
Niikey is used by Kapsch Installation Services personnel during cutover procedures. It indicates that the
Network File System (NFS) inactive core indicator key (Niikey) was detected as enabled. If a SOS applica-
tion reboot occurs while the Niikey is set, the SOS application will be prevented from becoming the active in-
stance.
This alarm indicates that Niikey has been enabled for the HLR application.
The entity type for this alarm is ’hlr’ defined under the GU_Home_Location _Registry application data model.
4.1.1 System impact

This alarm is not service affecting. It indicates that there is a loss of redundancy of the HLR application while
Niikey is enabled during a cutover procedure.
The alarm is fixed at the major severity level. Once raised, it cannot be updated, only cleared.

If a cutover is not in progress and this alarm appears, contact your next level of support. Otherwise, at the
end of the cutover procedure, use the cli to disable Niikey for the HLR application.
4.1.3 Attributes
Attribute Value
Severity • Clear
• Major
4.2 HLR1301
This alarm indicates that the active and standby instances of the HLR application are not synchronized.
The entity type for this alarm is ’hlr’ defined under the GU_Home_Location _Registry application data model.
4.2.1 System impact

This alarm is not service affecting. It indicates loss of redundancy of the HLR application.

Investigate the cause of the out-of-sync condition. Then, use the ’hlr sync’ cli command to clear the condition
or wait for the system to automatically re-establish synchronization.

4.2.3 Attributes
Attribute Value
Severity • Clear
• Major
4.3 HLR1302
When this alarm is raised, it indicates that the HLR application is undergoing a RExTst. The RExTst can be
initiated manually from the cli, or automatically by the system.
RExTst runs in one of two modes: Base or Full. Base RExTst steps:image test and sync. Full RExTst steps:
image test, hardware diagnostics and board reset, sync, swact, and sync. Base RExTst is usually scheduled
6 times a week at night during low traffic. Full RExTst is scheduled once per week. Manual RExTst can be
run by craft personnel at any time.
This alarm indicates that the standby instance of the HLR application is undergoing a Routine Exercise Test.
The entity type for this alarm is "hlr" defined under the GU_Home_Location _Registry application data model.
4.3.1 System impact

This alarm is not service affecting. It indicates loss of redundancy of the HLR application while the RExTst is
running.

No manual action is required. The alarm clears automatically once the RExTst has completed.
4.3.3 Attributes
Attribute Value
Severity • Clear
• Major
4.4 HLR1303
One or more manual or system-initiated RExTsts have failed or have been manually aborted.
This alarm is raised if any of the steps involved in the manual or system initiated RExTst fails.
This alarm indicates that one or more RExTsts have failed or have been manually aborted for the standby in-
stance of the HLR application.
The entity type for this alarm is ’hlr’ defined under the GU_Home_Location_Registry application data model.

4.4.1 System impact

This alarm is not service affecting. It indicates a failed RExTst of the standby instance of the HLR application.
Consequently, the unit might not be healthy enough to become the active instance if needed.

Review office records to determine if the fault has occurred in the past. Run a manual RExTst during a peri-
od of low traffic to determine if the fault is intermittent. The alarm clears after a successful RExTst is com-
pleted (manual or system initiated).
4.4.3 Attributes
Attribute Value
Severity • Clear
• Major
4.5 HLR1304
HLR RExTst was not automatically scheduled by the system in the last 7 days.
Once a RExTst is automatically scheduled by the system, the alarm clears automatically.
This alarm indicates that RExTst was not automatically scheduled by the system in the last 7 days for the
HLR application.
4.5.1 System impact

This alarm is not service affecting. It indicates that the system will be less likely to automatically test the sani-
ty of the standby instance of the HLR application.
The alarm is fixed at the minor severity level. Once raised, it cannot be updated, only cleared.

Check the SOS IOAU112 log reports to see if system RExTst has been disabled. If it has, no action required.
If system RExTst has not been disabled, edit SOS table REXSCHED so that automatic scheduling of RExTst
is resumed.

4.5.3 Attributes
Attribute Value
Severity • Clear
• Minor
4.6 HLR1305
HLR Image Test (ImgTst) is in progress for the HLR application.
ImgTst can be manually initiated from the cli, or as part of a manual or system RExTst. During ImgTst, all
SOS restart types (warm, cold and reload) are performed on the standby instance of the HLR application.
This alarm indicates that the standby instance of the HLR application is undergoing a software image test.
4.6.1 System impact

This alarm is not service affecting. It indicates loss of redundancy of the HLRAA application during the run-
ning of the image test.

No manual action required. The alarm clears once the ImgTst completes.
4.6.3 Attributes
Attribute Value
Severity • Clear
• Major
4.7 HLR1306
One or more ImgTsts have failed. The ImgTst can be manually initiated from the cli, or as part of a system or
manual initiated RExTst.
This alarm is raised if the standby instance of the HLR application cannot be successfully restarted (warm,
cold or reload).
This alarm indicates a failed software image test of the standby instance of the HLR application.

4.7.1 System impact

This alarm is not service affecting. It indicates a failed ImgTst of the standby instance of the HLR application.
Consequently, the unit might not be healthy enough to become the active instance if needed.

The alarm clears once a successful ImgTst completes. The ImgTst can be manually
initiated from the cli, or as part of a system or manual RExTst. Run a manual ImgTst during a period of low
traffic to determine if the fault is intermittent. The alarm clears after a successful ImgTst has completed.
4.7.3 Attributes
Attribute Value
Severity • Clear
• Major
4.8 HLR1307
HLR Call Processing Application Out of Service.
This alarm is raised if the call processing application instance is out of service.
4.8.1 System impact

This alarm is service affecting for the active call processing application instance.
The alarm severity is initially critical on the active side, and minor on the standby side. Once raised, it cannot
be updated, only cleared. The alarm is raised or cleared via the OAM FM Library API only.

The alarm clears once the call processing application instance is in service.
4.8.3 Attributes
Attribute Value
Severity • Clear
• Minor
• Critical

4.9 HLR1308
Low memory condition of the call processing application instance.
This alarm is raised during a low memory condition of the call processing application instance.
4.9.1 System impact

The alarm severity can be either critical, major, or minor. Once raised, the severity can be updated or
cleared. The alarm is managed via the OAM FM Library API only.

The alarm clears once the memory usage of the call processing application resumes to normal.
4.9.3 Attributes
Attribute Value
Severity • Clear
• Minor
• Major
• Critical
4.10 HLR1350
HLR Service Availability indicates that the service availability of the MSSCA application has been impacted.
This alarm is raised when the HLR application is not in-service, or is in-service but its service level is de-
graded for some reason.
This alarm indicates that an error or other condition exists for the HLR application that is preventing it from
coming fully into service.

When this alarm is raised it means the HLR application’s service has been impacted. If the alarm is raised
with Critical severity, then the HLR application will remain disabled until the fault is cleared. If the alarm is
raised with a Major severity, then the HLR application will have a degraded service level until the problem is
cleared.
The initial severity for this alarm can either be critical (when the HLR is out-of-service) or major (when the
HLR is still in-service, but its service is degraded).

The following are the reason codes potentially generated for this alarm. Based on the reason code, affect the

appropriate repair accordingly as follows:
1. Application health degraded - this reason indicates that the HLR component running in SOS
has reported a degraded state most likely due to a processing overload situation occurring on
the HLR. Try to offload work from the HLR application. Check SOS logs for detailed reasons
for the degraded state. Contact your next level of support for assistance.
2. Application health critical - this indicates that the HLR component running in SOS has report-
ed a critical error or the software was unable to determine the health of the HLR SOS appli-
cation. Check SOS logs for detailed reasons for the critical state. Contact your next level of
support for assistance.
3. Application health not determined - this is a temporary reason code not requiring any repair
action unless it persists. If it does persist, contact your next level of support for assistance.
4. Initial Table Sync not completed - this is a temporary reason code not requiring any repair ac-
tion unless it persists. If it does persist, it indicates failure to start initial table synchronization.
Contact your next level of support for assistance.
5. Initial Table Sync failure - refer to documentation for the HLR 1351 alarm for details on trou-
bleshooting.
6. Table Sync failure - refer to documentation for the HLR 1351 alarm for details on trouble-
shooting.
7. Service Removed - HLR Service can be removed by manual action or system recovery ac-
tion. Manual action is done via locking HLR Service Unit. To repair, unlock the applicable
HLR Service Unit. System recovery action is triggered upon detection of certain types of fail-
ure, no repair action is required in this case.
8. SOS Component unavailable - this is a temporary reason code not requiring any
repair action unless it persists. If it does persist, it indicates failure to initialize
communication with the SOS component of the HLR application. Contact your next level of
support for assistance.
4.10.3 Attributes
Attribute Value
Severity • Major
• Critical
4.11 HLR1351
This alarm is raised when the HLR application is not in-service, or is in-service but its service level is de-
graded, due to a SOS table synchronization issue.
There are two types of table sync failures: Out-of-service sync failure, In-Service sync failure. An Out-of-
service sync failure occurs when the HLR is out-of-service and can not come into service due to this error.
An In-service sync failure occurs when the HLR is already in-service and a table sync failure occurs which
results in a service degradation for the HLR application.
This alarm indicates that a SOS table synchronization error has occurred which has impacted the service of
the HLR application.


When this alarm is raised it means the HLR application service has been impacted. If the alarm is raised due
to an initial table sync failure, then the HLR application will remain out-of-service until the fault is cleared. If
the alarm is raised due to an in-service table sync failure, then the HLR application will have a degraded ser-
vice level until the table sync problem is cleared.
The severity for this alarm can either be Critical (when a table sync failure occurs during initial application
startup) or Major (when a table sync failure occurs when the application is already in-service).

On the affected HLR, check in SOS for TABS logs (in LOGUTIL) and use the TABSYNC CI tool to check the
sync status. Based on this information, the reason for the table sync issue can be found. To repair the issue,
refer to DMS Table Distribution feature documentation.
4.11.3 Attributes
Attribute Value
4.12 HLR1352
This alarm is raised when a tuple apply request from solid is not acked by SOS. This means the SOLID/DMS
table is now out of sync.
Next bulk sync operation can make the tables in sync.
This alarm indicates that SOLID and DMS tables are out of sync.

The HLR application service is not impacted.
The severity for this alarm can either be major (when a table sync failure occurs during bulk sync) or minor
(when a table sync failure occurs during tuple add, modify or delete).

Next scheduled bulk sync can sync the tables.
4.12.3 Attributes
Attribute Value
Severity • Minor
• Major

4.13 HLR1360
This alarm is raised when the HLR application can not come into service due to its administrative state being
set to deactivated and the HLR’s service unit administrative state is unlocked.
This alarm will not be generated while the HLR’s service unit administrative state is offline or locked. When
the HLR’s service unit administrative state is unlocked, this alarm will be generated if the HLR’s administra-
tive state is deactivated.
This alarm is raised when the HLR application’s administrative state is set to deactivated and it prevents the
HLR from coming into service.

When this alarm is raised it means the HLR application can not come into service due to its administrative
state being set to deactivated. Until the HLR is activated it will not be able to come into service even when
the service unit is unlocked.
The alarm is fixed at the critical severity level. Once raised, it cannot be updated, only cleared.

To clear this alarm, activate the HLR application at the cli using the ’HLR activate’ command.
4.13.3 Attributes
Attribute Value
Severity • Clear
• Critical
4.14 HLR1363
This alarm is raised whenever Tabsync audit detects a mismatch for the HLR application.
This alarm is raised when there is a mismatch between MRF and HLR.
This alarm is raised when a mismatch is found on the HLR.

When this alarm is raised there is no service impact. However, there is a mismatch on HLR application.
The alarm is fixed at the minor severity level. Once raised, it cannot be updated, only cleared.

On the affected HLR, check in SOS for TABS logs (in LOGUTIL) and use the TABSYNC CI tool, AUDIT
TABNAME tablename DELTA for details. Based on this information, the reason for the table sync issue can
be found. To repair the issue, refer to DMS Table Distribution feature documentation.

4.14.3 Attributes
Attribute Value
Severity • Clear
• Minor
 END OF DOCUMENT PE/HLR/APP/027903 

Kairos HLR Alarm Reference

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Kairos HLR Alarm Reference

Uploaded by

Copyright:

Available Formats

Kapsch CarrierCom AG

PE/HLR/APP/027903 | Kairos HLR Alarm Reference Page 1 of 161

Kairos HLR Alarm Reference

PE/HLR/APP/027903 | Kairos HLR Alarm Reference Page 2 of 161

Copyright © 2014 Kapsch. All Rights Reserved.

PE/HLR/APP/027903 | Kairos HLR Alarm Reference Page 3 of 161

PE/HLR/APP/027903 | Kairos HLR Alarm Reference Page 4 of 161

PE/HLR/APP/027903 | Kairos HLR Alarm Reference Page 5 of 161

3.107 MrfOamAgent1330 ..................................................................................................................................77

PE/HLR/APP/027903 | Kairos HLR Alarm Reference Page 6 of 161

3.164 MtcFtm1300 ..........................................................................................................................................111

PE/HLR/APP/027903 | Kairos HLR Alarm Reference Page 7 of 161

3.221 Storage1332 ..........................................................................................................................................143

PE/HLR/APP/027903 | Kairos HLR Alarm Reference Page 8 of 161

• state and activity reports

PE/HLR/APP/027903 | Kairos HLR Alarm Reference Page 9 of 161

2 HLR alarms reference

2.1.1 System impact

2.1.2 Remedial action

2.1.4 Associated logs

PE/HLR/APP/027903 | Kairos HLR Alarm Reference Page 10 of 161

3 KAIROS alarms reference

3.1.1 System impact

3.1.2 Remedial action

PE/HLR/APP/027903 | Kairos HLR Alarm Reference Page 11 of 161

This alarm clears once the local node starts to:

3.2.1 Remedial action

3.2.3 Associated logs

3.3.1 System impact

3.3.2 Remedial action

PE/HLR/APP/027903 | Kairos HLR Alarm Reference Page 12 of 161

3.4.1 System impact

3.4.2 Remedial action

3.5.1 System impact

3.5.2 Remedial action

PE/HLR/APP/027903 | Kairos HLR Alarm Reference Page 13 of 161

3.6.1 System impact

3.6.2 Remedial action

3.7.1 System impact

3.7.2 Remedial action

PE/HLR/APP/027903 | Kairos HLR Alarm Reference Page 14 of 161

Suppression setting suppression-allowed

3.8.1 System impact

3.8.2 Remedial action

3.9.1 System impact

3.9.2 Remedial action

PE/HLR/APP/027903 | Kairos HLR Alarm Reference Page 15 of 161

3.10.1 System impact

3.10.2 Remedial action

3.11.1 System impact

PE/HLR/APP/027903 | Kairos HLR Alarm Reference Page 16 of 161

3.11.2 Remedial action

3.12.1 System impact

3.12.2 Remedial action

PE/HLR/APP/027903 | Kairos HLR Alarm Reference Page 17 of 161

3.13.1 System impact

3.13.2 Remedial action

3.14.1 System impact

3.14.2 Remedial action

PE/HLR/APP/027903 | Kairos HLR Alarm Reference Page 18 of 161

3.15.1 System impact

3.15.2 Remedial action

1. Verify the file permissions for the dhcpd.conf files under

3.16.1 System impact