A SGW service is operationally down.

A PGW service is operationally up.

A PGW service is operationally down.

A GGSN service is operationally up.

A GGSN service is operationally down.

An APN is available for use by a specific GW service.

An APN is not available for use by a specific GW service.

Indicates whether MCM redundancy is operational. When the standby boots it has 10 minutes to establish redundancy before raising this alarm. If a standby task fails, the system gives 3 minutes to re-established redundancy before raising this alarm.

Indicates whether all tos tasks are operationally UP on this CPU. After a card is booted all tasks have 10 minutes to come up before an alarm is issued. If a task goes down, the system gives 3 minutes for the task to come up before issuing this alarm.

Adding UA profile file failed due to invalid profile file.

Communication over the data fabric is down.

A new core file is detected on the chassis.

Last try to ftp files to remote server failed.

Slot (CSM or SSM) has exceeded reboot frequency threshold.

Indicates a Geo-redundant standby cluster is not ready and the active peer is not currently protected.

Geo-redundant active cluster is not fully functional due to link health status with neighboring network elements.

Forced sync of images from active to standby.

Forced sync failed or timed-out.

Port Status is UP

Port Status is Down

Port Status is UP

Files have been purged from disk since disk purge threshold was crossed (disk was getting close to full).

Failed to connect to SPS server.

SPS server connection lost.

Geo-redundant node designated as HA-Role primary has entered HA-State standby.

Geo-redundant node designated as HA-Role secondary has entered HA-State active.

Kernel options have been automatically modified on the current module. They will take effect on the reboot.

Geo-redundancy link is down.

Geo-redundant peers running incompatible software versions.

Disk format operation took place.

Disk full

The alarm is generated when the transport connection to the CALEA peer is down. It is cleared when connectivity to the CALEA peer is restored.

Indicates when the transport connection to the CALEA peer comes up. It is deprecated and will be removed in future releases, as the anCaleaPeerLinkDown alarm delivers all link status change notifications. It is not used by the existing code.

Node has departed from cluster.

GTP Peer Up Event

Inter-node connectivity health check over data fabric path A is down.

Inter-node connectivity health check over data fabric path B is down.

This alarm is generated when the configured threshold for UE pool utilization is crossed.

Inter-node connectivity health check over base switch path A is down.

Inter-node connectivity health check over base switch path B is down.

Inter-node connectivity health check over base switch paths A and B are down.

Cannot sync with configured NTP servers.

A WarmStart trap signifies that the an3000/MCC is reinitializing itself such that its configuration is unaltered.

A logical link has transitioned from state down to state up.

A logical link has transitioned from state up to state down.

Failed login attempt

The trap is generated when all CALEA targets have been removed and the size of the CALEA target data base becomes zero. It is an informational trap and therefore never cleared.

This alarm is generated when all Legal Intercept Mediation device Interfaces have been deleted. It is an informational alarm and is never cleared.

The alarm is generated when the Configured Legal Intercept Targets Utilization is greater than 60% and less than 70% of the maximum capacity. It is cleared when the utilization becomes less than or equal to 60%.

This Alarm is generated when Configured Legal Intercept Targets are above 70% but below 80% of maximum allowed configurable targets. It is cleared when the utilization is less than or equal to 70%.

This Alarm is generated when Configured Legal Intercept Targets are above 80% but below 90% of maximum allowed targets. It is cleared when the utilization is less than or equal to 80%.

This Alarm is generated when Configured Legal Intercept Targets are above 90% but below 100% of maximum allowed targets. It is cleared when the utilization is less than or equal to 90%.

Base switch node reachability differs between path A and path B.

Map of reachable nodes over data fabric path A differs from path B.

A BGP peering is not in Established state. The alarm is raised when peering starts, restarts, cleared, or when a peering leaves Established state due to a protocol or networking event. The alarm is cleared when a peering enters Established state.

The alarm is generated when the configured size for the CC buffer on the interface group is less than the minimum threshold value (10MB).

An MCM switchover has taken place.

This alarm is generated when the buffer utilization threshold is reached for the CC buffer on the interface group.

This alarm is generated when the buffer utilization threshold is reached for the IRI buffer on the interface group.

The alarm is generated when the number of entries in the target DB reaches the maximum allowed value of 32,768.

The alarm is generated when the configured size for the IRI buffer on the interface group is less than the minimum threshold value (1 MB).

The alarm is raised when the configuration for a CALEA interface/interface group is modified in any way (added, changed or deleted).

The alarm is generated whenever a CALEA Lawful Intercept target is created or deleted.

The alarm is generated whenever the interface group status changes from up to down. It is cleared when the status changes back to up.

The alarm is generated whenever CC buffer data is lost because the buffer size was exceeded and inserting additional data in the buffer caused earlier packets to be lost.

The alarm is generated whenever IRI buffer data is lost because the buffer size was exceeded and inserting additional data in the buffer caused earlier packets to be lost.

Failure during the creation of an extended-storage disk partition

Alarm is generated when the extended-storage disk size is not matched between the Active and Standby MCMs

This alarm is generated when an ext-storage disk is required but none has been created

Lack of sufficient free storage space available

Event generated when moving files from one storage site to another exceeds timeout.

Event generated when waiting for files to close on a disk partition exceeds a timeout

The system failed to log a data record (i.e. local CDR, HTDR or other such data records).  This failure can occur either at the source generating the data record or at the agent which is responsible for flush the data record to the disk.

The network packet engine has encountered an error preventing any data plane communication on the current node (control plane is not affected)

The packet network engine is experiencing congestion, no impact at warning level. At critical alarm level, priority based packet drops are possible. Reception is affected until packet memory returns to an acceptable level.

Fru entered Extraction pending state

Fru entered insertion pending state

Inter-node connectivity health check detects partial connectivity with peer nodes over data plane path A.

This alarm is raised when a node cannot reach over the nfs mount to the disk on peer MCM.   For active MCM, the peer MCM is the standby MCM.  For all nodes, the peer MCM is the active MCM.

This alarm is generated when the system fails to setup emergency bearers for a session due to reasons such as lack of resources or memory or other call processing errors.

This alarm is generated when active emergency bearers are deactivated due to operator intervention such as deactivation initiated through CLI.

Online Categorization Database Installation Failed

A WAG service is operationally down.

A WAG service is operationally up.

The connection to the EDR server has failed.

Approaching or crossed licensed service capacity enforcement level. Upon reaching X percent of the capacity enforcement level, a major event will be generated. The event will become critical as the enforcement level is crossed.

Approaching or crossed licensed service capacity limit. Upon reaching X percent of the capacity limit, a major event will be generated. The event will become critical as the limit is crossed.

Approaching or passed licensed service enforcement expiration date. Upon reaching X percent of the license expiration date, a major event will be generated. The event will become critical as the expiration is passed.

Approaching or passed licensed service lifetime. Upon reaching X percent of the license lifetime, a major event will be generated. The event will become critical as the lifetime is passed.

The MCC has separated from the PLS server and enter local license management state. During this period, the MCC will manage licenses based on the last PLS view. Services will be impacted if the server is not restored within the grace period.

Connection to the PLS server has not reestablished within the grace period so license-able services are terminated.

A ColdStart trap signifies that the an3000/MCC is reinitializing itself and that its configuration may have been altered.

An ePDG service is operationally up.

An ePDG service is operationally down.

An X509 certificate is approaching expiration

An X509 certificate has expired

An X509 certificate has been revoked

Attempts to update a pki object from a remote source have failed for more than 24 hours

A new pki object has been added to the system

An existing pki object has been updated

A pki object has been removed from the system

The packet network engine has experienced a critical error that is preventing packet processing.  Packet processing is stopped.

A test event

The next update of this x509 certificate revocation list is available

A mismatch exists between the provisioned packet processing resources and what node booted with.

Incorrect number of Isol Cpus for this platform

one or more nodes are running a different tos release than they are intended to be running and neither an upgrade nor a rollback is in progress.

IPsec TUNNEL-DOWN

IPsec TUNNEL-UP

Attempts to get an updated version of a pki object from a remote source have failed for more than 24 hours

An ssh public key has been configured to authenticate ssh for a user

An NMD configuration has been committed.

An ssh public key has been removed from those that may authenticate ssh for a user

An ssh public key has been configured to authenticate ssh for all users in a group

An ssh public key has been removed from those that may authenticate ssh for all users in a group

An ssh public key has been trusted as a certificate authority key to validate certificates used to authenticate ssh for any user in the cluster

An ssh public key that had been trusted as a certificate authority key to validate certificates used to authenticate ssh for any user in the cluster has been removed

An ssh public key has been trusted as a certificate authority key to validate certificates used to authenticate ssh for all users in a group

An ssh public key that had been trusted as a certificate authority key to validate certificates used to authenticate ssh for all users in a group has been removed

A user has been added to the group list of authorized principals

A user has been removed from the group list of authorized principals

All users in a group have been added to the group list of authorized principals

All users in a group have been removed from the group list of authorized principals

Last try to export files to the export directory (as per configuration) failed.

One or mores names have been added to a group authorized principals list

An error has occurred converting pki ssh configuration to ssh authorizedkeys/authorizedprincipals/trustedusercakeys files

One or mores names have been removed from a user authorized principals list

One or mores names have been added to a user authorized principals list

One or mores names have been removed from a group authorized principals list

The ssh security level for the cluster has been changed to maximum

The ssh security level for the cluster has been changed to compatible

The ssh strict host key checking for the cluster has been changed to no

The ssh strict host key checking for the cluster has been changed to ask

The ssh strict host key checking for the cluster has been changed to yes

The ssh verify host key with dns for the cluster has been changed to no

The ssh verify host key with dns for the cluster has been changed to yes