|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.100 |
A SGW service is operationally down.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.101 |
A PGW service is operationally up.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.102 |
A PGW service is operationally down.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.103 |
A GGSN service is operationally up.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.104 |
A GGSN service is operationally down.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.105 |
An APN is available for use by a specific GW service.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.106 |
An APN is not available for use by a specific GW service.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.107 |
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.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.108 |
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.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.109 |
Adding UA profile file failed due to invalid profile file.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.110 |
Communication over the data fabric is down.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.111 |
A new core file is detected on the chassis.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.112 |
Last try to ftp files to remote server failed.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.114 |
Slot (CSM or SSM) has exceeded reboot frequency threshold.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.117 |
Indicates a Geo-redundant standby cluster is not ready and the active peer is not currently protected.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.118 |
Geo-redundant active cluster is not fully functional due to link health status with neighboring network elements.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.125 |
Forced sync of images from active to standby.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.126 |
Forced sync failed or timed-out.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.127 |
Port Status is UP
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.128 |
Port Status is Down
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.129 |
Port Status is UP
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.130 |
Files have been purged from disk since disk purge threshold was crossed (disk was getting close to full).
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.131 |
Failed to connect to SPS server.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.132 |
SPS server connection lost.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.133 |
Geo-redundant node designated as HA-Role primary has entered HA-State standby.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.134 |
Geo-redundant node designated as HA-Role secondary has entered HA-State active.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.135 |
Kernel options have been automatically modified on the current module. They will take effect on the reboot.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.136 |
Geo-redundancy link is down.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.137 |
Geo-redundant peers running incompatible software versions.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.138 |
Disk format operation took place.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.139 |
Disk full
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.140 |
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.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.141 |
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.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.142 |
Node has departed from cluster.
|
anGtpPeerUp
deprecated
|
.1.3.6.1.4.1.37963.4.0.4.3.0.143 |
GTP Peer Up Event
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.144 |
Inter-node connectivity health check over data fabric path A is down.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.145 |
Inter-node connectivity health check over data fabric path B is down.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.146 |
This alarm is generated when the configured threshold for UE pool utilization is crossed.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.147 |
Inter-node connectivity health check over base switch path A is down.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.148 |
Inter-node connectivity health check over base switch path B is down.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.149 |
Inter-node connectivity health check over base switch paths A and B are down.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.151 |
Cannot sync with configured NTP servers.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.152 |
A WarmStart trap signifies that the an3000/MCC is reinitializing itself such that its configuration is unaltered.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.153 |
A logical link has transitioned from state down to state up.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.154 |
A logical link has transitioned from state up to state down.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.155 |
Failed login attempt
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.162 |
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.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.163 |
This alarm is generated when all Legal Intercept Mediation device Interfaces have been deleted. It is an informational alarm and is never cleared.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.164 |
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%.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.165 |
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%.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.166 |
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%.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.167 |
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%.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.168 |
Base switch node reachability differs between path A and path B.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.169 |
Map of reachable nodes over data fabric path A differs from path B.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.186 |
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.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.189 |
The alarm is generated when the configured size for the CC buffer on the interface group is less than the minimum threshold value (10MB).
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.19 |
An MCM switchover has taken place.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.190 |
This alarm is generated when the buffer utilization threshold is reached for the CC buffer on the interface group.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.191 |
This alarm is generated when the buffer utilization threshold is reached for the IRI buffer on the interface group.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.192 |
The alarm is generated when the number of entries in the target DB reaches the maximum allowed value of 32,768.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.193 |
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).
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.194 |
The alarm is raised when the configuration for a CALEA interface/interface group is modified in any way (added, changed or deleted).
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.195 |
The alarm is generated whenever a CALEA Lawful Intercept target is created or deleted.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.196 |
The alarm is generated whenever the interface group status changes from up to down. It is cleared when the status changes back to up.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.197 |
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.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.198 |
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.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.199 |
Failure during the creation of an extended-storage disk partition
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.200 |
Alarm is generated when the extended-storage disk size is not matched between the Active and Standby MCMs
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.201 |
This alarm is generated when an ext-storage disk is required but none has been created
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.202 |
Lack of sufficient free storage space available
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.203 |
Event generated when moving files from one storage site to another exceeds timeout.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.204 |
Event generated when waiting for files to close on a disk partition exceeds a timeout
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.205 |
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.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.206 |
The network packet engine has encountered an error preventing any data plane communication on the current node (control plane is not affected)
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.207 |
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.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.208 |
Fru entered Extraction pending state
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.209 |
Fru entered insertion pending state
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.210 |
Inter-node connectivity health check detects partial connectivity with peer nodes over data plane path A.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.211 |
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.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.214 |
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.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.215 |
This alarm is generated when active emergency bearers are deactivated due to operator intervention such as deactivation initiated through CLI.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.218 |
Online Categorization Database Installation Failed
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.220 |
A WAG service is operationally down.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.221 |
A WAG service is operationally up.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.222 |
The connection to the EDR server has failed.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.223 |
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.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.224 |
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.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.225 |
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.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.226 |
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.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.227 |
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.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.228 |
Connection to the PLS server has not reestablished within the grace period so license-able services are terminated.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.23 |
A ColdStart trap signifies that the an3000/MCC is reinitializing itself and that its configuration may have been altered.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.230 |
An ePDG service is operationally up.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.231 |
An ePDG service is operationally down.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.232 |
An X509 certificate is approaching expiration
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.233 |
An X509 certificate has expired
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.234 |
An X509 certificate has been revoked
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.235 |
Attempts to update a pki object from a remote source have failed for more than 24 hours
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.236 |
A new pki object has been added to the system
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.237 |
An existing pki object has been updated
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.238 |
A pki object has been removed from the system
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.239 |
The packet network engine has experienced a critical error that is preventing packet processing. Packet processing is stopped.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.24 |
A test event
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.240 |
The next update of this x509 certificate revocation list is available
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.241 |
A mismatch exists between the provisioned packet processing resources and what node booted with.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.242 |
Incorrect number of Isol Cpus for this platform
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.244 |
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.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.246 |
IPsec TUNNEL-DOWN
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.247 |
IPsec TUNNEL-UP
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.248 |
Attempts to get an updated version of a pki object from a remote source have failed for more than 24 hours
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.249 |
An ssh public key has been configured to authenticate ssh for a user
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.25 |
An NMD configuration has been committed.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.250 |
An ssh public key has been removed from those that may authenticate ssh for a user
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.251 |
An ssh public key has been configured to authenticate ssh for all users in a group
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.252 |
An ssh public key has been removed from those that may authenticate ssh for all users in a group
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.253 |
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
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.254 |
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
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.255 |
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
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.256 |
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
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.257 |
A user has been added to the group list of authorized principals
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.258 |
A user has been removed from the group list of authorized principals
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.259 |
All users in a group have been added to the group list of authorized principals
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.260 |
All users in a group have been removed from the group list of authorized principals
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.261 |
Last try to export files to the export directory (as per configuration) failed.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.262 |
One or mores names have been added to a group authorized principals list
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.263 |
An error has occurred converting pki ssh configuration to ssh authorizedkeys/authorizedprincipals/trustedusercakeys files
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.264 |
One or mores names have been removed from a user authorized principals list
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.265 |
One or mores names have been added to a user authorized principals list
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.266 |
One or mores names have been removed from a group authorized principals list
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.267 |
The ssh security level for the cluster has been changed to maximum
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.268 |
The ssh security level for the cluster has been changed to compatible
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.269 |
The ssh strict host key checking for the cluster has been changed to no
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.270 |
The ssh strict host key checking for the cluster has been changed to ask
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.271 |
The ssh strict host key checking for the cluster has been changed to yes
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.272 |
The ssh verify host key with dns for the cluster has been changed to no
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.273 |
The ssh verify host key with dns for the cluster has been changed to yes
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.274 |
The ssh verify host key with dns for the cluster has been changed to ask
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.275 |
The ssh public key of a certificate authority has been removed from ssh_known_hosts.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.276 |
The ssh public key of a certificate authority has been added to ssh_known_hosts to validate the host certificates presented on connection by ssh/scp/sftp to external servers
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.277 |
An ssh public key has been removed from ssh_known_hosts.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.278 |
An ssh public key has been added to ssh_known_hosts to validate connections by ssh/scp/sftp to external servers
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.279 |
The previous local ssh host certificate has been replaced by a new ssh certificate.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.28 |
CSM cache operationally down.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.280 |
The local ssh host certificate has been removed.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.281 |
The local ssh host certificate has been added.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.282 |
An ssh key or certificate has been revoked by an ssh krl file
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.283 |
An ssh key or certificate has been manually reported as revoked by a revoke cli command
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.285 |
A new or updated pki ssh krl file has replaced the previous ssh krl as the RevokedKeys file to the sshd servers.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.286 |
A pki ssh krl file has been added as the RevokedKeys file to the sshd servers.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.287 |
The ssh krl file that was providing a list of revoked ssh keys has been removed from RevokedKeys on the sshd servers.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.288 |
An ssh certificate is approaching expiration
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.289 |
An ssh certificate has expired
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.29 |
HW sensor raising temperature alarm.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.291 |
Adding filterHashList got error as file has invalid entry.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.292 |
Adding filterHashList failed as file does not exist on NE.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.293 |
Adding FilterHashList failed as exceeded max supported filter entries per filter database size.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.294 |
Adding filterHashList failed as file is too big.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.296 |
File containing Subscriber IDs configured for the subscriber-group does not exist on the MCC.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.298 |
A new memory image file is detected on the chassis
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.299 |
This alarm is generated when admin state of Calea User Ban Feature is changed
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.30 |
HW sensor raising voltage alarm.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.300 |
The alarm is generated when CC data is first lost on an interface which is down (and no interface-group is provisioned for target)
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.301 |
The alarm is generated when IRI data is first lost on an interface which is down (and no interface-group is provisioned for target)
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.302 |
An OSPFv2 neighbor is not in Full/2-Way state. The alarm will be generated when a neighbor leaves Full/2-Way state. The alarm is cleared when neighbor enters Full/2-Way state.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.303 |
An OSPFv3 neighbor is not in Full/2-Way state. The alarm will be generated when a neighbor leaves Full/2-Way state. The alarm is cleared when neighbor enters Full/2-Way state.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.304 |
The nat-pool session utilization has exceeded threshold. This may potentially lead to session or connection setup failures.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.305 |
The nat-pool IP address utilization has exceeded threshold. This may potentially lead to session or connection setup failures.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.306 |
The nat-pool Port chunk utilization has exceeded threshold. This may potentially lead to session or connection setup failures.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.309 |
A new fault file has been detected on the chassis
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.31 |
HW sensor raising hot swap alarm.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.32 |
HW Sensor Raising Telco Alarm
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.320 |
The service monitored by content health check is not reachable.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.321 |
PFCP Peer down indicates that the remote PFCP Peer is not responding to any of the PFCP messages sent to it.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.322 |
PFCP Peer is up, running and reachable.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.323 |
The alarm is raised when the configuration for a CALEA interface-group-source-profile is modified in any way (added, changed or deleted).
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.324 |
The alarm is raised when the CALEA subsystem is unable to find an interface-group-source-profile for a dynamic target interface/group.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.329 |
This event is generated when a BFD session goes down. It is cleared when the BFD session goes up. A gratuitous clear will happen the first time the BFD session goes up. Toggled by ip-protocols/bfd/enable-bfd-session-down-alarms
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.33 |
HW Sensor Raising Watchdog Alarm
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.332 |
Node needs to be rebooted because one or more of the following have changed on the node. 1. isolcpus 2. core-layout
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.333 |
The network ports are not in the correct order, which causes connectivity to the desired network to appear broken.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.334 |
PGW is not accepting sessions using RADIUS towards peer Radius server due to operator configuration
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.335 |
One or multiple CA (Certificate Authority) certificates have expired.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.338 |
The cluster needs to be rebooted because one or more of the following have changed on one or more nodes in the cluster. 1. isolcpus 2. core-layout 3. max-packet-size
|
anFanAlarm
deprecated
|
.1.3.6.1.4.1.37963.4.0.4.3.0.34 |
HW Sensor Raising Fan Alarm
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.342 |
This alarm is generated to indicate control plane will not deliver PDHIR events when CALEA target config is having PDHIR enabled in SX3LIF mode
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.343 |
The alarm is generated when encrypted CALEA Lawful Intercept data can not be decrypted (could be security key mismatch between CPF and UPF)
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.348 |
Loading the config file for Dns Server Failed.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.349 |
Hard quota for recursive clients reached. Incoming requests are dropped, and for each one, a pending request is dropped.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.35 |
HW sensor raising air filter alarm.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.350 |
Soft quota for recursive clients reached. Incoming requests are accepted, but for each one, a pending request is dropped. If recursive-clients is set greater than 1000, soft quota is recursive-clients minus 100; else it is 90% of recursive-clients.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.351 |
Loading the zone file for Dns Server Failed.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.354 |
A task has been terminated
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.36 |
HW sensor raising tach alarm..
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.37 |
HW sensor raising hardware alarm.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.39 |
Adding CF category failed as file is too large.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.40 |
Adding CF category failed as file does not exist on NE.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.41 |
Adding CF category failed as exceeded max supported filter entries per filter database size.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.42 |
Adding CF blacklist failed as exceeded max supported filter entries per filter database size.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.44 |
Adding CF blacklist failed as file is too large.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.45 |
Adding CF blacklist failed as file does not exist on NE.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.46 |
Card is plugged in but not operational
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.47 |
Adding CF category got error as file has invalid entry.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.48 |
Adding CF blacklist got error as file has invalid entry.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.49 |
http-proxy failed to connect server.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.56 |
Adding CF whitelist got error as file has invalid entry.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.57 |
Adding CF whitelist failed as exceeded max supported filter entries per filter database size.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.58 |
Adding CF whitelist failed as file is too large.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.59 |
Adding CF whitelist failed as file does not exist on NE.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.60 |
GTP peer down. This indicates that the remote GTP peer is not responding to any GTP messages sent to it. If the peer is statically provisioned, the severity is Major. If the peer is dynamic, the severity is Info.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.61 |
Monitor the cache SSD operational state.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.62 |
Adding urlList got error as file has invalid entry.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.63 |
Adding UrlList failed as exceeded max supported filter entries per filter database size.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.64 |
Adding urlList failed as file does not exist on NE.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.65 |
Adding urlList failed as file is too big.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.67 |
Policy lists agent failed to download a policy file from external server.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.68 |
A threshold has been crossed.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.69 |
A task has generated an overload event.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.70 |
This blade has generated an overload event.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.71 |
This system has generated an overload event
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.73 |
FP ran out of paging buffers
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.74 |
LED state change.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.78 |
Module rebooted.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.79 |
Monitor the Cache SSD read/write error state.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.80 |
The specified payload has experienced a hardware or firmware failure.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.81 |
Failed to connect LDAP server.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.82 |
LDAP server connection lost.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.83 |
LDAP profile does not have a connection to remote server.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.86 |
Missing required attributes in the default UA profile.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.88 |
The operational status of an IP interface is down.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.89 |
Transport connection to the diameter peer is down.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.90 |
Diameter Peer Transport Connection Up Event
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.91 |
The RADIUS peer health check failed and this RADIUS peer is declared down.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.92 |
Radius Peer Up Event
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.93 |
The Transport connection to Gtpp peer is down.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.94 |
Gtpp Peer Up Event
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.95 |
Failed to connect to SMSC server.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.96 |
SMSC profile not found.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.97 |
SMSC server connection lost.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.98 |
The UE sent an IP packet with an unassigned source address.
|
|
|
.1.3.6.1.4.1.37963.4.0.4.3.0.99 |
A SGW service is operationally up.
|
Table
Row
Column
Scalar
Node