SNMP Message Content

Module:

ARH

Error code:

7701

Severity:

(3) Critical

Alarm model description:

arh-module is not in service.

Event type:

1

Probable cause:

612

Alarm Documentation

Alarm description:

arh-module is not in service.

Alarm Object:

arh-module

Alarm raised by:

arh-module unavailable

Alarm cleared by:

arh-module is back in service.

Proposed action:

If the alarm is not automatically ceased, find and correct the error. Then start the arh-module, see System Administrators Guide.

SNMP Message Content

Module:

ARH

Error code:

7702

Severity:

(4) Major

Alarm model description:

The asynchronous request queue is full. ARH stops the receivers on all nodes to avoid running out of database storage.

Event type:

4

Probable cause:

151

Alarm Documentation

Alarm description:

The arh queue is full.

Alarm Object:

arh-module

Alarm raised by:

The items in asynchronous request queue are greater than the threshold.

Alarm cleared by:

The items in asynchronous request queue are back to normal.

Proposed action:

Check that the Asynchronous Request consumer is enabled, see User Guide for Subscriber Activation.

SNMP Message Content

Module:

ARH

Error code:

7703

Severity:

(4) Major

Alarm model description:

ARH failed to send notification.

Event type:

2

Probable cause:

10

Alarm Documentation

Alarm description:

ARH failed to send notification.

Alarm Object:

arh-module

Alarm raised by:

ARH failed to send notification.

Alarm cleared by:

No clear, stateless alarm.

Proposed action:

Check the status of notification receiver.

SNMP Message Content

Module:

BatchHandler

Error code:

8202

Severity:

(4) Major

Alarm model description:

Batch Job status is changed.

Event type:

2

Probable cause:

607

Alarm Documentation

Alarm description:

Batch Job status changed.

Alarm Object:

ema-batch-handler-module

Alarm raised by:

Batch Job status changed

Alarm cleared by:

No clear, stateless alarm.

Proposed action:

No need, stateless alarm.

SNMP Message Content

Module:

CPC

Error code:

7601

Severity:

(3) Critical

Alarm model description:

cpc-module is not in service.

Event type:

1

Probable cause:

612

Alarm Documentation

Alarm description:

cpc-module is not in service.

Alarm Object:

cpc-module

Alarm raised by:

cpc-module unavailable

Alarm cleared by:

cpc-module is back in service.

Proposed action:

If the alarm is not automatically ceased, find and correct the error. Then start the cpc-module, see System Administrators Guide.

SNMP Message Content

Module:

Cassandra

Error code:

3203

Severity:

(4) Major

Alarm model description:

Cassandra server is not in service.

Event type:

4

Probable cause:

612

Alarm Documentation

Alarm description:

Cassandra server is not in service.

Alarm Object:

Connection Cassandra

Alarm raised by:

Cassandra data storage server is down.

Alarm cleared by:

Cassandra server is back in service.

Proposed action:

Check if the Cassandra server is up and running. Refer to the System Administration Guide for details.

SNMP Message Content

Module:

Cassandra

Error code:

3301

Severity:

(4) Major

Alarm model description:

Disk usage high on "/var/cassandra/data". When 90% is reached the oldest processing logs will automatically be cleared.

Event type:

4

Probable cause:

151

Alarm Documentation

Alarm description:

The disk use is high on "/var/cassandra/data".

Alarm Object:

Disk

Alarm raised by:

At least 80% of the storage volume "/var/cassandra/data" is in use.

Alarm cleared by:

Less than 75% of the storage volume "/var/cassandra/data" is used.

Proposed action:

Check the /var/cassandra/data or disk. Consider dimensioning the system based on system usage.
To store processing logs use the Processing Log Admin Tool to export logs. Refer to the System Administration Guide for details.

SNMP Message Content

Module:

Cassandra

Error code:

3302

Severity:

(3) Critical

Alarm model description:

Disk usage too high on "/var/cassandra/data". The oldest processing logs will automatically be cleared.

Event type:

3

Probable cause:

151

Alarm Documentation

Alarm description:

The disk use is too high on "/var/cassandra/data".

Alarm Object:

Disk

Alarm raised by:

At least 90% of the storage volume "/var/cassandra/data" is in use.

Alarm cleared by:

Less than 85% of the storage volume "/var/cassandra/data" is used.

Proposed action:

proclog-cleanup.sh script will be triggered to clean up the database until the partition reaches 70%. Refer to the System Administration Guide for details.

SNMP Message Content

Module:

Cassandra

Error code:

3303

Severity:

(4) Major

Alarm model description:

Disk usage high on "/var/cassandra/commitlog".

Event type:

4

Probable cause:

151

Alarm Documentation

Alarm description:

The disk use is high on "/var/cassandra/commitlog".

Alarm Object:

Disk

Alarm raised by:

At least 80% of the storage volume "/var/cassandra/commitlog" is in use.

Alarm cleared by:

Less than 75% of the storage volume "/var/cassandra/commitlog" is used.

Proposed action:

Commitlog partition can grow temporarily during high volume data writes. No action is needed.

SNMP Message Content

Module:

Cassandra

Error code:

3304

Severity:

(3) Critical

Alarm model description:

Disk usage too high on "/var/cassandra/commitlog".

Event type:

3

Probable cause:

151

Alarm Documentation

Alarm description:

The disk use is too high on "/var/cassandra/commitlog".

Alarm Object:

Disk

Alarm raised by:

At least 90% of the storage volume "/var/cassandra/commitlog" is in use.

Alarm cleared by:

Less than 85% of the storage volume "/var/cassandra/commitlog" is used.

Proposed action:

Commitlog partition can grow temporarily during high volume data writes. If this alarms raises too often, consider flushing the
commitlog. Refer to the System Administration Guide for details. Consider dimensioning the system based on system usage.

SNMP Message Content

Module:

Cassandra

Error code:

3305

Severity:

(5) Minor

Alarm model description:

Disk usage growing high on "/var/cassandra/data". When 90% is reached the oldest processing logs will automatically be cleared.

Event type:

4

Probable cause:

151

Alarm Documentation

Alarm description:

The disk use is growing high on "/var/cassandra/data".

Alarm Object:

Disk

Alarm raised by:

At least 70% of the storage volume "/var/cassandra/data" is in use.

Alarm cleared by:

Less than 65% of the storage volume "/var/cassandra/data" is used.

Proposed action:

Check the /var/cassandra/data or disk. Consider dimensioning the system based on system usage.
To store processing logs use the Processing Log Admin Tool to export logs. Refer to the System Administration Guide for details.

SNMP Message Content

Module:

Cassandra

Error code:

3306

Severity:

(5) Minor

Alarm model description:

Disk usage growing high on "/var/cassandra/commitlog".

Event type:

4

Probable cause:

151

Alarm Documentation

Alarm description:

The disk use is growing high on "/var/cassandra/commitlog".

Alarm Object:

Disk

Alarm raised by:

At least 70% of the storage volume "/var/cassandra/commitlog" is in use.

Alarm cleared by:

Less than 65% of the storage volume "/var/cassandra/commitlog" is used.

Proposed action:

Commitlog partition can grow temporarily during high volume data writes. No action is needed.

SNMP Message Content

Module:

CommonService

Error code:

7005

Severity:

(4) Major

Alarm model description:

Global configuration service is not valid.

Event type:

4

Probable cause:

612

Alarm Documentation

Alarm description:

Global configuration service is not valid.

Alarm Object:

MPE

Alarm raised by:

MPE global configuration unavailable

Alarm cleared by:

Global configuration service is valid

Proposed action:

Check the global configuration service.

SNMP Message Content

Module:

CommonService

Error code:

7006

Severity:

(4) Major

Alarm model description:

Configuration file failed to update.

Event type:

4

Probable cause:

612

Alarm Documentation

Alarm description:

Configuration file failed to update.

Alarm Object:

MPE

Alarm raised by:

MPE configuration service updates configuration files failed

Alarm cleared by:

MPE configuration service updates configuration files successfully

Proposed action:

Check whether the configuration files can be updated, and whether this server is properly communicating with other servers within the same cluster.

SNMP Message Content

Module:

CommonService

Error code:

7007

Severity:

(4) Major

Alarm model description:

Failed to log in.

Event type:

2

Probable cause:

600

Alarm Documentation

Alarm description:

Failed to login.

Alarm Object:

MPE

Alarm raised by:

MPE login failed

Alarm cleared by:

No clear, stateless alarm.

Proposed action:

Check the configuration.

SNMP Message Content

Module:

CommonService

Error code:

7008

Severity:

(6) Warning

Alarm model description:

Notification failed to send in Async Cai3g interface.

Event type:

2

Probable cause:

10

Alarm Documentation

Alarm description:

Notification failed to send in Async Cai3g interface.

Alarm Object:

MPE

Alarm raised by:

MPE notification sending failure.

Alarm cleared by:

No clear, stateless alarm.

Proposed action:

-

SNMP Message Content

Module:

EMA

Error code:

2101

Severity:

(4) Major

Alarm model description:

Failed to connect to network element.

Event type:

2

Probable cause:

22

Alarm Documentation

Alarm description:

EMA failed to connect to a network element.

Alarm Object:

Connection to network element

Alarm raised by:

The connection to the network element is down.

Alarm cleared by:

The connection to the network element is up or the network element is removed.

Proposed action:

Check that the configuration for the specific network element is correct. Check that the network element is reachable and in service. Refer to log file entry field "Alarm Active Description" for network element IP and port.

SNMP Message Content

Module:

EMA

Error code:

2102

Severity:

(4) Major

Alarm model description:

Network element group is down.

Event type:

2

Probable cause:

554

Alarm Documentation

Alarm description:

EMA failed to connect to any network element in the network element group.

Alarm Object:

Network Element Group

Alarm raised by:

All network elements in the network element group is down.

Alarm cleared by:

At least one network element is up for the network element group or all network elements are removed from the group.

Proposed action:

Check that the configuration for the specific network elements in the network element group is correct. Check that the network elements are reachable and in service. Refer to log file entry field "Alarm Active Description" for network element IP and port.

SNMP Message Content

Module:

EMA

Error code:

2103

Severity:

(6) Warning

Alarm model description:

The value of the cluster strategy parameter is changed.

Event type:

1

Probable cause:

607

Alarm Documentation

Alarm description:

The value of the cluster strategy parameter is changed by cluster strategy logic according to the designated criteria.

Alarm Object:

EMA Business Logic

Alarm raised by:

The value of the cluster strategy parameter is changed.

Alarm cleared by:

No clear, stateless alarm.

Proposed action:

No action needed.

SNMP Message Content

Module:

EMA

Error code:

2302

Severity:

(4) Major

Alarm model description:

Can not write the proclog to the storage

Event type:

4

Probable cause:

612

Alarm Documentation

Alarm description:

Can not write the proclog to the storage

Alarm Object:

EMA Application

Alarm raised by:

-

Alarm cleared by:

-

Proposed action:

Check if the Cassandra cluster is up and running. Refer to the System Administrators Guide for Native Deployment, or System Administrators Guide for Virtual Deployment, for details.

SNMP Message Content

Module:

EMA

Error code:

2402

Severity:

(6) Warning

Alarm model description:

Failed login threshold exceeded.

Event type:

10

Probable cause:

614

Alarm Documentation

Alarm description:

The threshold for maximum failed login attempts has been exceeded for a user.

Alarm Object:

Security

Alarm raised by:

Login Authentication process

Alarm cleared by:

No clear, stateless alarm

Proposed action:

Reset the user by logging into the EMA GUI as admin and in tabs Access Control - Users, choose the locked user and click on the Locked check-box.

SNMP Message Content

Module:

EMA

Error code:

2404

Severity:

(6) Warning

Alarm model description:

CUDB-Block-Proxy not in service.

Event type:

4

Probable cause:

612

Alarm Documentation

Alarm description:

CUDB-Block-Proxy not in service.

Alarm Object:

CUDB-Block-Proxy service

Alarm raised by:

CUDB-Block-Proxy service is down.

Alarm cleared by:

CUDB-Block-Proxy service is up.

Proposed action:

If the alarm is not automatically ceased, find and correct the error. Then start CUDB-Block-Proxy service, see System Administrators Guide.

SNMP Message Content

Module:

EMA

Error code:

2405

Severity:

(4) Major

Alarm model description:

Service Location Register is not in service.

Event type:

4

Probable cause:

1024

Alarm Documentation

Alarm description:

Service Location Register is down.

Alarm Object:

Service Location Register

Alarm raised by:

Service Location Register is down

Alarm cleared by:

Service Location Register is back in service

Proposed action:

If the alarm is not automatically ceased, find
and correct the error. Then start the Service Location
Register(SLR), see System Administration Guide

SNMP Message Content

Module:

EMA

Error code:

2406

Severity:

(4) Major

Alarm model description:

tomcat-server is not in service.

Event type:

4

Probable cause:

612

Alarm Documentation

Alarm description:

The tomcat-server is not in service.

Alarm Object:

tomcat-server

Alarm raised by:

tomcat-server service is down.

Alarm cleared by:

tomcat-server service is up.

Proposed action:

If the alarm is not automatically ceased, find and correct the error. Then start the tomcat-server, see System Administrators Guide.

SNMP Message Content

Module:

EMA

Error code:

2407

Severity:

(4) Major

Alarm model description:

dve-inbound-interfaces-application is not in service.

Event type:

4

Probable cause:

612

Alarm Documentation

Alarm description:

The dve-inbound-interfaces-application is not in service.

Alarm Object:

dve-inbound-interfaces-application

Alarm raised by:

dve-inbound-interfaces-application service is down.

Alarm cleared by:

dve-inbound-interfaces-application service is up.

Proposed action:

If the alarm is not automatically ceased, find and correct the error. Then start the dve-inbound-interfaces-application, see System Administrators Guide.

SNMP Message Content

Module:

EMA

Error code:

2408

Severity:

(4) Major

Alarm model description:

dve-application is not in service.

Event type:

4

Probable cause:

612

Alarm Documentation

Alarm description:

The dve-application is not in service.

Alarm Object:

dve-application

Alarm raised by:

dve-application service is down.

Alarm cleared by:

dve-application service is up.

Proposed action:

If the alarm is not automatically ceased, find and correct the error. Then start the dve-application, see System Administrators Guide.

SNMP Message Content

Module:

EMA

Error code:

2409

Severity:

(4) Major

Alarm model description:

Multi Log Consolidation is not in service.

Event type:

4

Probable cause:

1024

Alarm Documentation

Alarm description:

Multi Log Consolidation is down.

Alarm Object:

Multi Log Consolidation

Alarm raised by:

Multi Log Consolidation is down

Alarm cleared by:

Multi Log Consolidation is back in service

Proposed action:

If the alarm is not automatically ceased, find
and correct the error. Then start the Service Multi Log Consolidation, see System Administration Guide

SNMP Message Content

Module:

EMA

Error code:

2410

Severity:

(5) Minor

Alarm model description:

Lock service is not in service.

Event type:

4

Probable cause:

612

Alarm Documentation

Alarm description:

Lock service not in service.

Alarm Object:

Lock service

Alarm raised by:

Lock service is down.

Alarm cleared by:

Lock service is up.

Proposed action:

If the alarm is not automatically ceased, find and correct the error. Then start the Lock service, see System Administrators Guide.

SNMP Message Content

Module:

EMA

Error code:

2411

Severity:

(4) Major

Alarm model description:

Out of memory

Event type:

4

Probable cause:

162

Alarm Documentation

Alarm description:

Out of memory

Alarm Object:

Module

Alarm raised by:

The module has generated a .hprof file

Alarm cleared by:

No clear, stateless alarm.

Proposed action:

Analyze the generated .hprof file

SNMP Message Content

Module:

EMA

Error code:

4001

Severity:

(5) Minor

Alarm model description:

Partially executed operations.

Event type:

4

Probable cause:

160

Alarm Documentation

Alarm description:

Partially executed operations need manual intervention.

Alarm Object:

EMA Business Logic

Alarm raised by:

Executed operations failed partially

Alarm cleared by:

Manual clear. For information on how to perform a manual clear, see section Configuring ESA in System Administrators Guide for Native Deployment, or System Administrators Guide for Virtual Deployment.

Proposed action:

Partially executed operations may leave inconsistency data stored in data repositories. Manual intervention is needed.

SNMP Message Content

Module:

EMA

Error code:

4002

Severity:

(5) Minor

Alarm model description:

Error creating service entry

Event type:

4

Probable cause:

160

Alarm Documentation

Alarm description:

EMA tried to create an entry and failed.

Alarm Object:

EMA Business Logic

Alarm raised by:

Failure to create an entry in CUDB

Alarm cleared by:

No clear, stateless alarm

Proposed action:

Please, check the interface documentations and run proposed command to repair/delete the failed subscription.

SNMP Message Content

Module:

EMA

Error code:

4003

Severity:

(5) Minor

Alarm model description:

Error deleting service entry

Event type:

4

Probable cause:

160

Alarm Documentation

Alarm description:

EMA tried to delete an entry and failed.

Alarm Object:

EMA Business Logic

Alarm raised by:

Failure to delete an entry in CUDB

Alarm cleared by:

No clear, stateless alarm

Proposed action:

Please, check the interface documentations and run proposed command to repair/delete the failed subscription.

SNMP Message Content

Module:

EMA

Error code:

4004

Severity:

(5) Minor

Alarm model description:

Error updating service entry

Event type:

4

Probable cause:

160

Alarm Documentation

Alarm description:

EMA tried to update an entry and failed.

Alarm Object:

EMA Business Logic

Alarm raised by:

Failure to update an entry in CUDB

Alarm cleared by:

No clear, stateless alarm

Proposed action:

Please, check the interface documentations and run proposed command to repair/delete the failed subscription.

SNMP Message Content

Module:

EMA

Error code:

4005

Severity:

(6) Warning

Alarm model description:

Failed to take subscriber lock

Event type:

4

Probable cause:

165

Alarm Documentation

Alarm description:

PG timed out when trying to take a subscriber lock (protection for concurrent commands).
Continued without subscriber locking.

Alarm Object:

PG Business Logic

Alarm raised by:

Failed to take subscriber lock

Alarm cleared by:

No clear, stateless alarm

Proposed action:

If the failure to take a subscriber lock caused a CUDB inconsistency, please see the
documentation on how to manually repair/delete the failed subscription.

SNMP Message Content

Module:

EMA

Error code:

4103

Severity:

(5) Minor

Alarm model description:

Error creating AUC entry

Event type:

4

Probable cause:

160

Alarm Documentation

Alarm description:

EMA tried to create an entry and failed.

Alarm Object:

AUC

Alarm raised by:

Failure to create an entry in CUDB

Alarm cleared by:

No clear, stateless alarm

Proposed action:

Please check the interface documentation and run proposed command to repair/delete the failed subscription.

SNMP Message Content

Module:

EMA

Error code:

4104

Severity:

(5) Minor

Alarm model description:

Error deleting AUC entry

Event type:

4

Probable cause:

160

Alarm Documentation

Alarm description:

EMA tried to delete an entry and failed.

Alarm Object:

AUC

Alarm raised by:

Failure to delete an entry in CUDB

Alarm cleared by:

No clear, stateless alarm

Proposed action:

Please check the interface documentation and run proposed command to repair/delete the failed subscription.

SNMP Message Content

Module:

EMA

Error code:

4105

Severity:

(5) Minor

Alarm model description:

Error updating AUC entry

Event type:

4

Probable cause:

160

Alarm Documentation

Alarm description:

EMA tried to update an entry and failed.

Alarm Object:

AUC

Alarm raised by:

Failure to update an entry in CUDB

Alarm cleared by:

No clear, stateless alarm

Proposed action:

Please check the interface documentation and run proposed command to repair/delete the failed subscription.

SNMP Message Content

Module:

EMA

Error code:

4205

Severity:

(5) Minor

Alarm model description:

Error creating HLR entry

Event type:

4

Probable cause:

160

Alarm Documentation

Alarm description:

EMA tried to create an entry and failed.

Alarm Object:

HLR

Alarm raised by:

Failure to create an entry in CUDB

Alarm cleared by:

No clear, stateless alarm

Proposed action:

Please check the interface documentation and run proposed command to repair/delete the failed subscription.

SNMP Message Content

Module:

EMA

Error code:

4206

Severity:

(5) Minor

Alarm model description:

Error deleting HLR entry

Event type:

4

Probable cause:

160

Alarm Documentation

Alarm description:

EMA tried to delete an entry and failed.

Alarm Object:

HLR

Alarm raised by:

Failure to delete an entry in CUDB

Alarm cleared by:

No clear, stateless alarm

Proposed action:

Please check the interface documentation and run proposed command to repair/delete the failed subscription.

SNMP Message Content

Module:

EMA

Error code:

4207

Severity:

(5) Minor

Alarm model description:

Error updating HLR entry

Event type:

4

Probable cause:

160

Alarm Documentation

Alarm description:

EMA tried to update an entry and failed.

Alarm Object:

HLR

Alarm raised by:

Failure to update an entry in CUDB

Alarm cleared by:

No clear, stateless alarm

Proposed action:

Please check the interface documentation and run proposed command to repair/delete the failed subscription.

SNMP Message Content

Module:

EMA

Error code:

4208

Severity:

(5) Minor

Alarm model description:

Error provisioning HLR exchange data type 1

Event type:

4

Probable cause:

160

Alarm Documentation

Alarm description:

An error occurred during provisioning of Exchange Data Type 1.

Alarm Object:

HLR

Alarm raised by:

Failure to provision

Alarm cleared by:

No clear, stateless alarm

Proposed action:

Resend the command with the failed HLRFEID.

SNMP Message Content

Module:

EMA

Error code:

4209

Severity:

(5) Minor

Alarm model description:

Error provisioning HLR subscriber profile

Event type:

4

Probable cause:

160

Alarm Documentation

Alarm description:

An error occurred during provisioning of Subscriber Profile.

Alarm Object:

HLR

Alarm raised by:

Failure to provision

Alarm cleared by:

No clear, stateless alarm

Proposed action:

Resend the command with the failed HLRFEID.

SNMP Message Content

Module:

EMA

Error code:

4301

Severity:

(5) Minor

Alarm model description:

Error in notification rule file or SOAP notification to/from HSS-FE

Event type:

2

Probable cause:

612

Alarm Documentation

Alarm description:

EMA failed to load notification rule file or EMA received a "client" SOAP faultcode from HSS-FE

Alarm Object:

EMA

Alarm raised by:

Failed to load notification rule file or received client SOAP faultcode from HSS-FE

Alarm cleared by:

No clear, stateless alarm

Proposed action:

Check if content of rule is correct. Refer to the System Administrators Guide for Native Deployment, or System Administrators Guide for Virtual Deployment, for details.

SNMP Message Content

Module:

EMA

Error code:

4303

Severity:

(5) Minor

Alarm model description:

Error creating HSS entry

Event type:

4

Probable cause:

160

Alarm Documentation

Alarm description:

EMA tried to create an entry and failed.

Alarm Object:

HSS

Alarm raised by:

Failure to create an entry in CUDB

Alarm cleared by:

No clear, stateless alarm

Proposed action:

Please check the interface documentation and run proposed command to repair/delete the failed subscription.

SNMP Message Content

Module:

EMA

Error code:

4304

Severity:

(5) Minor

Alarm model description:

Error deleting HSS entry

Event type:

4

Probable cause:

160

Alarm Documentation

Alarm description:

EMA tried to delete an entry and failed.

Alarm Object:

HSS

Alarm raised by:

Failure to delete an entry in CUDB

Alarm cleared by:

No clear, stateless alarm

Proposed action:

Please check the interface documentation and run proposed command to repair/delete the failed subscription.

SNMP Message Content

Module:

EMA

Error code:

4305

Severity:

(5) Minor

Alarm model description:

Error updating HSS entry

Event type:

4

Probable cause:

160

Alarm Documentation

Alarm description:

EMA tried to update an entry and failed.

Alarm Object:

HSS

Alarm raised by:

Failure to update an entry in CUDB

Alarm cleared by:

No clear, stateless alarm

Proposed action:

Please check the interface documentation and run proposed command to repair/delete the failed subscription.

SNMP Message Content

Module:

EMA

Error code:

4403

Severity:

(5) Minor

Alarm model description:

Error creating EIR entry

Event type:

4

Probable cause:

160

Alarm Documentation

Alarm description:

EMA tried to create an entry and failed.

Alarm Object:

EIR

Alarm raised by:

Failure to create an entry in CUDB

Alarm cleared by:

No clear, stateless alarm

Proposed action:

Use the document UDC Subscription Repair and Remove Procedures and use the identifiers from this event to manually repair/delete the failed subscription.

SNMP Message Content

Module:

EMA

Error code:

4404

Severity:

(5) Minor

Alarm model description:

Error deleting EIR entry

Event type:

4

Probable cause:

160

Alarm Documentation

Alarm description:

EMA tried to delete an entry and failed.

Alarm Object:

EIR

Alarm raised by:

Failure to delete an entry in CUDB

Alarm cleared by:

No clear, stateless alarm

Proposed action:

Use the document UDC Subscription Repair and Remove Procedures and use the identifiers from this event to manually repair/delete the failed subscription.

SNMP Message Content

Module:

EMA

Error code:

4405

Severity:

(5) Minor

Alarm model description:

Error updating EIR entry

Event type:

4

Probable cause:

160

Alarm Documentation

Alarm description:

EMA tried to update an entry and failed.

Alarm Object:

EIR

Alarm raised by:

Failure to update an entry in CUDB

Alarm cleared by:

No clear, stateless alarm

Proposed action:

Use the document UDC Subscription Repair and Remove Procedures and use the identifiers from this event to manually repair/delete the failed subscription.

SNMP Message Content

Module:

EMA

Error code:

4501

Severity:

(5) Minor

Alarm model description:

Error in notification rule file or SOAP notification to/from DAE-FE

Event type:

2

Probable cause:

612

Alarm Documentation

Alarm description:

EMA failed to load notification rule file or EMA received a "client" SOAP faultcode from DAE-FE

Alarm Object:

EMA

Alarm raised by:

Failed to load notification rule file or received client SOAP faultcode from DAE-FE

Alarm cleared by:

No clear, stateless alarm

Proposed action:

Check if content of rule is correct. Refer to the System Administrators Guide for Native Deployment, or System Administrators Guide for Virtual Deployment, for details.

SNMP Message Content

Module:

EMA

Error code:

4503

Severity:

(5) Minor

Alarm model description:

Error creating DAE entry

Event type:

4

Probable cause:

160

Alarm Documentation

Alarm description:

EMA tried to create an entry and failed.

Alarm Object:

DAE

Alarm raised by:

Failure to create an entry in CUDB

Alarm cleared by:

No clear, stateless alarm

Proposed action:

Use the document UDC Subscription Repair and Remove Procedures and use the identifiers from this event to manually repair/delete the failed subscription.

SNMP Message Content

Module:

EMA

Error code:

4504

Severity:

(5) Minor

Alarm model description:

Error deleting DAE entry

Event type:

4

Probable cause:

160

Alarm Documentation

Alarm description:

EMA tried to delete an entry and failed.

Alarm Object:

DAE

Alarm raised by:

Failure to delete an entry in CUDB

Alarm cleared by:

No clear, stateless alarm

Proposed action:

Use the document UDC Subscription Repair and Remove Procedures and use the identifiers from this event to manually repair/delete the failed subscription.

SNMP Message Content

Module:

EMA

Error code:

4505

Severity:

(5) Minor

Alarm model description:

Error updating DAE entry

Event type:

4

Probable cause:

160

Alarm Documentation

Alarm description:

EMA tried to update an entry and failed.

Alarm Object:

DAE

Alarm raised by:

Failure to update an entry in CUDB

Alarm cleared by:

No clear, stateless alarm

Proposed action:

Use the document UDC Subscription Repair and Remove Procedures and use the identifiers from this event to manually repair/delete the failed subscription.

SNMP Message Content

Module:

EMA

Error code:

4603

Severity:

(5) Minor

Alarm model description:

Error creating SAPC entry

Event type:

4

Probable cause:

160

Alarm Documentation

Alarm description:

EMA tried to create an entry and failed.

Alarm Object:

SAPC

Alarm raised by:

Failure to create an entry in CUDB

Alarm cleared by:

No clear, stateless alarm

Proposed action:

Please check the interface documentation and run proposed command to repair/delete the failed subscription.

SNMP Message Content

Module:

EMA

Error code:

4604

Severity:

(5) Minor

Alarm model description:

Error deleting SAPC entry

Event type:

4

Probable cause:

160

Alarm Documentation

Alarm description:

EMA tried to delete an entry and failed.

Alarm Object:

SAPC

Alarm raised by:

Failure to delete an entry in CUDB

Alarm cleared by:

No clear, stateless alarm

Proposed action:

Please check the interface documentation and run proposed command to repair/delete the failed subscription.

SNMP Message Content

Module:

EMA

Error code:

4605

Severity:

(5) Minor

Alarm model description:

Error updating SAPC entry

Event type:

4

Probable cause:

160

Alarm Documentation

Alarm description:

EMA tried to update an entry and failed.

Alarm Object:

SAPC

Alarm raised by:

Failure to update an entry in CUDB

Alarm cleared by:

No clear, stateless alarm

Proposed action:

Please check the interface documentation and run proposed command to repair/delete the failed subscription.

SNMP Message Content

Module:

EMA

Error code:

4703

Severity:

(5) Minor

Alarm model description:

Error creating AAA entry

Event type:

4

Probable cause:

160

Alarm Documentation

Alarm description:

EMA tried to create an entry and failed.

Alarm Object:

AAA

Alarm raised by:

Failure to create an entry in CUDB

Alarm cleared by:

No clear, stateless alarm

Proposed action:

Use the document UDC Subscription Repair and Remove Procedures and use the identifiers from this event to manually repair/delete the failed AAA Data.

SNMP Message Content

Module:

EMA

Error code:

4704

Severity:

(5) Minor

Alarm model description:

Error deleting AAA entry

Event type:

4

Probable cause:

160

Alarm Documentation

Alarm description:

EMA tried to delete an entry and failed.

Alarm Object:

AAA

Alarm raised by:

Failure to delete an entry in CUDB

Alarm cleared by:

No clear, stateless alarm

Proposed action:

Use the document UDC Subscription Repair and Remove Procedures and use the identifiers from this event to manually repair/delete the failed AAA Data.

SNMP Message Content

Module:

EMA

Error code:

4705

Severity:

(5) Minor

Alarm model description:

Error updating AAA entry

Event type:

4

Probable cause:

160

Alarm Documentation

Alarm description:

EMA tried to update an entry and failed.

Alarm Object:

AAA

Alarm raised by:

Failure to update an entry in CUDB

Alarm cleared by:

No clear, stateless alarm

Proposed action:

Use the document UDC Subscription Repair and Remove Procedures and use the identifiers from this event to manually repair/delete the failed AAA Data.

SNMP Message Content

Module:

EMA

Error code:

4803

Severity:

(5) Minor

Alarm model description:

Error creating ENUM entry

Event type:

4

Probable cause:

160

Alarm Documentation

Alarm description:

EMA tried to create an entry and failed.

Alarm Object:

ENUM

Alarm raised by:

Failure to create an entry in CUDB

Alarm cleared by:

No clear, stateless alarm

Proposed action:

Use the document UDC Subscription Repair and Remove Procedures and use the identifiers from this event to manually repair/delete the failed ENUM Data.

SNMP Message Content

Module:

EMA

Error code:

4804

Severity:

(5) Minor

Alarm model description:

Error deleting ENUM entry

Event type:

4

Probable cause:

160

Alarm Documentation

Alarm description:

EMA tried to delete an entry and failed.

Alarm Object:

ENUM

Alarm raised by:

Failure to delete an entry in CUDB

Alarm cleared by:

No clear, stateless alarm

Proposed action:

Use the document UDC Subscription Repair and Remove Procedures and use the identifiers from this event to manually repair/delete the failed ENUM Data.

SNMP Message Content

Module:

EMA

Error code:

4805

Severity:

(5) Minor

Alarm model description:

Error updating ENUM entry

Event type:

4

Probable cause:

160

Alarm Documentation

Alarm description:

EMA tried to update an entry and failed.

Alarm Object:

ENUM

Alarm raised by:

Failure to update an entry in CUDB

Alarm cleared by:

No clear, stateless alarm

Proposed action:

Use the document UDC Subscription Repair and Remove Procedures and use the identifiers from this event to manually repair/delete the failed ENUM Data.

SNMP Message Content

Module:

EMA

Error code:

5101

Severity:

(4) Major

Alarm model description:

License expired

Event type:

4

Probable cause:

609

Alarm Documentation

Alarm description:

The license for EMA has expired, or is about to expire.

Alarm Object:

Licenses

Alarm raised by:

Invalid/Expired license

Alarm cleared by:

No clear, stateless alarm

Proposed action:

Contact your local support organization to order a new license. For more information about licenses, see Function Specification Subscriber Activation.

SNMP Message Content

Module:

EMA

Error code:

5201

Severity:

(4) Major

Alarm model description:

Licensed capacity about to exceed

Event type:

4

Probable cause:

1024

Alarm Documentation

Alarm description:

Warning level reached for capacity license.

Alarm Object:

Licenses

Alarm raised by:

Warning level reached. Treshold value: 80%.

Alarm cleared by:

No clear, stateless alarm

Proposed action:

Contact your local support organization to order a new license. For more information about licenses, see Function Specification Subscriber Activation.

SNMP Message Content

Module:

EMA

Error code:

5202

Severity:

(3) Critical

Alarm model description:

Licensed capacity exceeded

Event type:

4

Probable cause:

1024

Alarm Documentation

Alarm description:

The usage level for one of the licenses is exceeding the licensed capacity.

Alarm Object:

Licenses

Alarm raised by:

Exceeded capacity

Alarm cleared by:

Order/apply new license

Proposed action:

Contact your local support organization to order a new license. For more information about licenses, see Function Specification Subscriber Activation.

SNMP Message Content

Module:

EMA

Error code:

5401

Severity:

(5) Minor

Alarm model description:

Not possible to synchronize licenses between clusters

Event type:

2

Probable cause:

4

Alarm Documentation

Alarm description:

The licenses could not be synchronized between redundant clusters

Alarm Object:

License synchronizer service

Alarm raised by:

Not possible to synchronize licenses for 24 hours

Alarm cleared by:

Licenses has been synchronized within the latest 24 hours

Proposed action:

Check connectivity between clusters and check logs for syncuser

SNMP Message Content

Module:

EMA

Error code:

5601

Severity:

(4) Major

Alarm model description:

ema-authentication-module is not in service.

Event type:

4

Probable cause:

612

Alarm Documentation

Alarm description:

The ema-authentication-module is not in service.

Alarm Object:

ema-authentication-module

Alarm raised by:

ema-authentication-module service is down.

Alarm cleared by:

ema-authentication-module service is up.

Proposed action:

If the alarm is not automatically ceased, find and correct the error.
Then start the ema-authentication-module, see System Administrators Guide.

SNMP Message Content

Module:

EMA

Error code:

5701

Severity:

(4) Major

Alarm model description:

ema-faultmgmt-module is not in service.

Event type:

4

Probable cause:

612

Alarm Documentation

Alarm description:

The ema-faultmgmt-module is not in service.

Alarm Object:

ema-faultmgmt-module

Alarm raised by:

EMA fault management module is down

Alarm cleared by:

EMA fault management module is started

Proposed action:

If the alarm is not automatically ceased, find and correct the error.
Then start the ema-faultmgmt-module, see System Administrators Guide.

SNMP Message Content

Module:

EMA

Error code:

8201

Severity:

(4) Major

Alarm model description:

ema-batch-handler-module is not in service.

Event type:

4

Probable cause:

612

Alarm Documentation

Alarm description:

The ema-batch-handler-module is not in service.

Alarm Object:

ema-batch-handler-module

Alarm raised by:

ema-batch-handler-module service is down.

Alarm cleared by:

ema-batch-handler-module service is up.

Proposed action:

If the alarm is not automatically ceased, find and correct the error.
Then start the ema-batch-handler-module, see System Administrators Guide.

SNMP Message Content

Module:

LDEwS

Error code:

11001

Severity:

(4) Major

Alarm model description:

Disk replication communication error.

Event type:

5

Probable cause:

505

Alarm Documentation

Alarm description:

The control node pair has been operating in a non-redundant mode for more than 20 minutes.

Alarm Object:

Disk Replication

Alarm raised by:

Hardware or network failure.

Alarm cleared by:

Disk synchronization is completed.

Proposed action:

If the alarm is not automatically ceased, consult the next level of maintenance support.

SNMP Message Content

Module:

LDEwS

Error code:

11004

Severity:

(5) Minor

Alarm model description:

Disk replication inconsistent.

Event type:

5

Probable cause:

505

Alarm Documentation

Alarm description:

The control node pair has been operating in a non-redundant mode for more than 20 minutes.

Alarm Object:

Disk Replication

Alarm raised by:

Disk mirroring failure leading to disk inconsistency between the control nodes.

Alarm cleared by:

Disk synchronization is completed.

Proposed action:

If the alarm is not automatically ceased, consult the next level of maintenance support.

SNMP Message Content

Module:

LDEwS

Error code:

11012

Severity:

(4) Major

Alarm model description:

Ethernet bonding failure.

Event type:

2

Probable cause:

505

Alarm Documentation

Alarm description:

An Ethernet interface belonging to a bonded interface fails.

Alarm Object:

Ethernet Bonding

Alarm raised by:

Faulty Ethernet interface, faulty Ethernet switch, or faulty Ethernet cable.

Alarm cleared by:

Ethernet bonding back to normal.

Proposed action:

Replace the Ethernet cable between the faulty Ethernet interface and the external device.

SNMP Message Content

Module:

LDEwS

Error code:

11013

Severity:

(3) Critical

Alarm model description:

Ethernet bonding complete failure.

Event type:

2

Probable cause:

505

Alarm Documentation

Alarm description:

Both Ethernet interfaces belonging to a bonded interface fail.

Alarm Object:

Ethernet Bonding

Alarm raised by:

Faulty Ethernet interface, faulty Ethernet switch, or faulty Ethernet cable.

Alarm cleared by:

Both Ethernet interfaces are back to normal.

Proposed action:

Replace the Ethernet cable between the faulty Ethernet interface and the external device.

SNMP Message Content

Module:

LDEwS

Error code:

11021

Severity:

(5) Minor

Alarm model description:

Time server unreachable.

Event type:

1

Probable cause:

505

Alarm Documentation

Alarm description:

Some of the configured NTP servers are unreachable.

Alarm Object:

Time Synchronization

Alarm raised by:

Time servers not reachable.

Alarm cleared by:

Time synchronization back to normal.

Proposed action:

Check that the NTP server(s) listed in the cluster configuration are correct and have network connectivity from the cluster nodes, then restart the NTP service.

SNMP Message Content

Module:

LDEwS

Error code:

11022

Severity:

(4) Major

Alarm model description:

All time servers unreachable.

Event type:

1

Probable cause:

505

Alarm Documentation

Alarm description:

The NTP servers from cluster.conf are not accepted by ntpd (unusable), no NTP server is reachable (unreachable) or a peer cannot be selected (rejected).

Alarm Object:

Time Synchronization

Alarm raised by:

Time servers not reachable.

Alarm cleared by:

Time synchronization back to normal.

Proposed action:

Check that the NTP server(s) listed in the cluster configuration are correct and have network connectivity from the cluster nodes, then restart the NTP service.

SNMP Message Content

Module:

LDEwS

Error code:

11023

Severity:

(3) Critical

Alarm model description:

Time synchronization error.

Event type:

1

Probable cause:

505

Alarm Documentation

Alarm description:

There are time differences between the blades in the cluster that exceeds the threshold value.

Alarm Object:

Time Synchronization

Alarm raised by:

The time difference between the local system time and the remote time server is greater than a threshold (10 seconds).

Alarm cleared by:

Time synchronization back to normal.

Proposed action:

Check that the NTP server(s) listed in the cluster configuration are correct and have network connectivity from the cluster nodes, then restart the NTP service.

SNMP Message Content

Module:

LOGGENERATION

Error code:

1350

Severity:

(3) Critical

Alarm model description:

AAA provisioning Error log is found

Event type:

4

Probable cause:

1024

Alarm Documentation

Alarm description:

EMA fails to provision the second AAA node.

Alarm Object:

/opt/links/asuser/domains/dve-domain/logs/request/aaa.

Alarm raised by:

Finding Error log in directory /opt/links/asuser/domains/dve-domain/logs/request/aaa. This error log is generated when EMA fails to provision the second AAA node.

Alarm cleared by:

Manual clear. Executing the command consolidateAAAErrorCommand.sh -c -d.

Proposed action:

Perform repair actions for AAA, see Non-Sim User Guide.

SNMP Message Content

Module:

NAC

Error code:

7801

Severity:

(4) Major

Alarm model description:

activation-orchestration-module is not in service.

Event type:

4

Probable cause:

612

Alarm Documentation

Alarm description:

activation-orchestration-module is not in service.

Alarm Object:

activation-orchestration-module

Alarm raised by:

activation-orchestration-module service is down.

Alarm cleared by:

activation-orchestration-module service is up.

Proposed action:

If the alarm is not automatically ceased, find and correct the error. Then start the activation-orchestration-module, see System Administrators Guide.

SNMP Message Content

Module:

NAC

Error code:

7802

Severity:

(5) Minor

Alarm model description:

Requests in expired state for network element in queue.

Event type:

4

Probable cause:

203

Alarm Documentation

Alarm description:

Requests in expired state for the network element queue need manual intervention.

Alarm Object:

Network element queue

Alarm raised by:

One or several requests are in expired state for the network element queue.

Alarm cleared by:

Trigger or cancel all expired requests for the network element queue.

Proposed action:

Trigger or cancel all expired requests for the network element queue, see User Guide Subscriber Activation.

SNMP Message Content

Module:

NAC

Error code:

7803

Severity:

(6) Warning

Alarm model description:

Event triggered by request in network element queue with a specific error code, error message or error details.

Event type:

4

Probable cause:

1024

Alarm Documentation

Alarm description:

Event triggered by request in network element queue with a specific error code, error message or error details need manual
intervention.

Alarm Object:

Network element queue

Alarm raised by:

Failed request with specific error code, error message or error details.

Alarm cleared by:

No clear, stateless alarm

Proposed action:

Check current state for the specific request using MessageId identifier, see User Guide Subscriber Activation.

SNMP Message Content

Module:

NBIA

Error code:

7001

Severity:

(3) Critical

Alarm model description:

nbia-module is not in service.

Event type:

1

Probable cause:

612

Alarm Documentation

Alarm description:

nbia-module is not in service.

Alarm Object:

nbia-module

Alarm raised by:

nbia-module unavailable

Alarm cleared by:

nbia-module is back in service.

Proposed action:

If the alarm is not automatically ceased, find and correct the error. Then start the nbia-module, see System Administrators Guide.

SNMP Message Content

Module:

NBIA

Error code:

7002

Severity:

(4) Major

Alarm model description:

Failed to log in.

Event type:

2

Probable cause:

600

Alarm Documentation

Alarm description:

Failed to login.

Alarm Object:

nbia-module

Alarm raised by:

nbia-module login failed

Alarm cleared by:

No clear, stateless alarm.

Proposed action:

Check the user configuration.

SNMP Message Content

Module: