This trap indicates that a Network Timing Protocol Server is in service.

This trap indicates that a Network Timing Protocol Server is out of service.

This trap indicates that Network Timing Protocol Server is Up.

This trap indicates that Network Timing Protocol is down.

This trap indicates that all Network Timing Protocol Servers are Out of Sync.

This trap indicates that a Network Timing Protocol Server is out of Sync.

This trap indicates that a Network Timing Protocol Server is in Sync.

This trap indicates that a Network Timing Protocol Server is Reachable.

The license for the virtual machine application is invalid.

The virtual machine application data sync is in progress.

This trap indicates a VM Redundancy Mode

The license for the virtual machine application is valid.

The virtual machine application is running.

The virtual machine application is not running.

This trap indicates that a VM software upgrade 
has been initiated.

This trap indicates that a VM software upgrade has terminated 
for the specified reason.

This trap indicates that a VM software upgrade has succeeded
for the specified reason.

This trap indicates that a VM Software Upgrade
is reverting to the previous release.

The virtual machine application data sync is completed.

This trap indicates SSH host keys are zeroized.

This trap indicates SSH host keys are regenerated.

This trap indicates CDB encryption keys are zeroized.

This trap indicates CDB encryption keys are regenerated.

This trap indicates OpenSSL Continuous Random Number Generator Test has failed.

This trap indicates OpenSSL Pairwise Consistency Test has failed.

This trap indicates Package Integrity Test has failed.

This trap indicates major System Security events.

This trap indicates that an account has been assigned to a group.

This trap indicates that an account has been enabled after being disabled.

This trap indicates that an OS account has been enabled after being disabled.

This trap indicates that there has been a change to the SSH keys for a user.

This trap indicates that an account has had its configuration changed.

This trap indicates that an account has been locked after a potential brute force attack.

This trap indicates that an OS account has been locked after a potential brute force attack.

This trap indicates that a Console Session Log file has reached at least 1GB in size.

This trap indicates that a new key will now be used to hash the event log files when they are rolled.

This trap indicates that an account has been auto re-enabled after being disabled due to bad passwords.

This trap indicates that Ehternet Errors are below the threshold level

This trap indicates that an OS account has been auto re-enabled after being disabled due to bad passwords.

This trap indicates high error rate on ethernet ports.

This trap indicates that Media Errors are below the threshold level

This trap indicates high error rate of NP Media Errors.

This trap indicates that the account has been automatically disabled as it has not been used during the accountAgingPeriod.

This trap indicates that the account has been automatically removed as it has not been used during the accountRemovalPeriod.

This trap indicates that an account has been created.

This trap indicates that an account has been manually deleted.

This trap indicates that the data agent made a new connection to the data node.

This trap indicates that the data agent was unable to connect to the data node.

This trap indicates that the data agent added a new stream

This trap indicates that the data agent removed a stream

This trap indicates that the data agent has started running

This trap indicates that the data agent was stopped gracefully.

This trap indicates about new SWe Traffic Profile Commit.

This trap indicates about Capacity Estimate Difference are more than 10% in sweCapacityEstimate, with the new base file.

This trap indicates about Capacity Estimate Difference are more than 10% in sweVcpuAllocation, with the new base file.

This trap indicates that a new traffic profile is activated after reboot.

This trap indicates that a first packet is dropped due to matching entries in blocking entries of Fault Avalanche Detection and Control Feature.

This trap indicates a server module redundancy switchover has occurred.
The standby server module has become active.  
The previous active server module, and group
information are included.  For 1+1 the redundancy model, there
is no group name.

This trap indicates that the specified redundancy group has
no redundancy protection.

This trap indicates that the specified redundancy group has
full redundancy protection.

This trap indicates that a software upgrade 
has been initiated.

This trap indicates that a software upgrade has terminated 
for the specified reason.

This trap indicates that a software upgrade has succeeded
for the specified reason.

This trap indicates that a Live Software Upgrade
revert to the previous release has occured.

This trap indicates that Live Software Upgrade
commit is pending.

This trap indicates that Live Software Upgrade is committed.

This trap indicates the current state of event file logging.

This Trap indicates that the location where events are saved is being changed

This trap indicates that the maximum size of the memory event log buffer is changed

This trap indicates that the level of event logging for this event type is changed

This trap indicates that the inability of the system to create a directory for event logging.
This could also indicate an generic error with the NFS server.

This trap indicates that event log for this log type is scheduled to rollover.

This trap indicates that event log rollover for this log type is stopped.

This trap indicates that event log rollover is occuring frequently.

This trap indicates that the number of event log files has dropped below the either the 100% or 75% threshold

This trap indicates the name of the event file which has been skipped because of file errors.

This trap indicates that an accountng file has been deleted because the maximum file count has been reached

This trap indicates the name of the event file which has been created for logging.

This trap indicates that an alarm has been manually cleared

This trap indicates that an accountng file has been renamed to remove the open file extension

This trap indicates that the level of event logging for this event type is changed

This trap indicates that the security or audit logging is enabled

This trap indicates that the security or audit logging is disabled

This trap indicates the name of the event file which could not write an event.

This trap indicates that info level logging has been disabled because of system congestion.

This trap indicates that info level logging has been re-enabled.

This trap indicates that the alarm Ids acknowledge state has changed.

This trap indicates that the alarm Ids comment field has been updated.

This trap indicates that file event logging has been automatically restarted.

This trap indicates that the debug event log filter level has been set to INFO.

This trap indicates that the debug event log filter level is no longer set to INFO and clears sonusCpEventLogFileDebugLevelInfoNotification.

This trap indicates the name of the event file which has been closed.

This trap indicates that a shutdown of file event logging has occurred.

This trap indicates that the number of event log files is approaching the configured maximum.

This trap indicates the number of Event Log files that will be maintained for this event type is changed

This trap indicates that the maximum size of a single event log file has changed.

This trap indicates that the number event log message entries to the buffer changed

This trap indicates that the node boot is requested.

This trap indicates that space on the hard disk is low.

This trap indicates that there are too many files on the hard disk.

This trap indicates that a hard disk is unavailable on the indicated server.

This trap indicates that space on a hard disk is above normal limit and disk is now writable.

This trap indicates that a hard disk synchronization is started on a server.

This trap indicates that a hard disk synchronization is completed on a server.

This trap indicates that a Server is disabled.

This trap indicates that a Server is enabled.

This trap indicates that a Server is operational.

This trap indicates that the CE/server boot is requested.

This trap indicates that the node is active after a reboot.

This trap indicates that the CE/server is active after a reboot.

This trap indicates that the CE/server soft boot is requested.

This trap indicates that the CE/server is active after a soft reboot.

This trap indicates that the CE/server temperature is higher than normal.

This trap indicates that the CE/server temperature is normal.

This trap indicates that the CE/server temperature is reaching critical level.

This trap indicates that a configuration commit has suceeded.

This trap indicates that a configuration commit has failed.

This trap indicates that all the hard disks are unavailable on the indicated server.

This trap indicates that the Apache service failed to start.

This trap indicates that the node soft boot is requested.

This trap indicates the reason for the service restarting.

This trap indicates that the CE/server NP temperature is higher than normal.

This trap indicates that the CE/server NP temperature is normal.

This trap indicates that the CE/server NP temperature is reaching critical level.

This trap indicates that a coredump is generated for a process running on the indicated server.

This trap indicates that a system is running low on coredump space.

This trap indicates that the node standby server is disabled.

This trap indicates that the node standby server is enabled.

This trap indicates that the node is active after a soft reboot.

This trap indicates that a high availability port is down.

This trap indicates that a high availability port is up.

This trap indicates that the bonding device is down.

This trap indicates that the bonding device is up.

This trap indicates that a high availability port is down.

This trap indicates that the RAID array has degraded due to a failure on the specified disk.

This trap indicates that the configuration restoration from specified config file is in progress.

This trap indicates that the system is running with a set of MAC addresses that doesn't belog to this system. This is possible if a server is replaced.

This trap indicates that the system is running out of memory and will soon reboot.

This trap indicates that the specified server is running with a product capability that is not compatible with the peer capabilities.

This trap indicates that a hard disk of a server is available.

This trap indicates that the system has fallen below the memory threshold

This trap indicates that the system received an error from  Self-Monitoring, Analysis and Reporting Technology (SMART) which is built into many hard drives

This trap indicates that the system cleared an error cleared from Self-Monitoring, Analysis and Reporting Technology (SMART) which is built into many hard drives

This trap indicates that the system received a life remaining threshold exceeded event from  Self-Monitoring, Analysis and Reporting Technology (SMART) which is built into many hard drives

This trap indicates that the system cleared life remaining threshold alarm from Self-Monitoring, Analysis and Reporting Technology (SMART) which is built into many hard drives

This trap indicates that the links for the specified server has dried up. Applicable to SGX4000 only.

This trap indicates that the CE/server is deactivating.

This trap indicates that the system memory usage is high. This trap is only applicable for SGX4000

This trap indicates that the system memory usage is at a safe level. This trap is only applicable for SGX4000

This trap indicates that the management active CE is no longer able to communicate configuration changes to the standby. This trap is only applicable for SGX4000

This trap indicates that bad volume is detected on hard disk of a server.

This trap indicates drbd partition format has completed. A full disk sync will start

This trap indicates that the drbd partition is being resized and reformatted to match the peer partition.

This trap indicates that the active server has requested the standby to become active, allowing the current active to reconfigure its drbd partition

This trap indicates that the drbd process encountered an error during reconfiguration

This trap indicates that the drbd process is backing up configuration and accounting files in preparation for a drbd partition reformat

This trap is the user generated major severity trap. This trap is only applicable for SGX4000.

This trap is the user generated minor severity trap. This trap is only applicable for SGX4000.

This trap is the user generated info severity trap. This trap is only applicable for SGX4000.

This trap indicates that the drbd partition is being resized and reformatted to match the peer partition. This trap is only applicable for SBX.

This trap indicates that the active server has requested the standby to become active, allowing the current active to reconfigure its drbd partition. This trap is only applicable for SBX.

This trap indicates that an incorrect hard disk is inserted on a server.

This trap indicates that the drbd process encountered an error during reconfiguration. This trap is only applicable for SBX.

This trap indicates that the drbd process is backing up configuration and accounting files in preparation for a drbd partition reformat. This trap is only applicable for SBX.

This trap indicates drbd partition format has completed. A full disk sync will start. This trap is only applicable for SBX.

This trap indicates that a server memory module maybe faulty. This trap is only applicable for SGX4000.

This trap indicates that the file system has gone into a read only state and nothing can be written to disk.

This trap indicates that a hard disk maybe faulty.

This trap indicates that the management active CE is in sync with the standby for configuration changes. This trap is only applicable for SGX4000.

This trap is the user generated critical severity trap. This trap is only applicable for SGX4000.

This trap indicates that space on the hard disk is low.

This trap indicates that space on the hard disk is low.

This trap indicates that space on the hard disk in with in the limits of normal operation.

This trap clears all previous disk space usage alarms before issuing fresh ones.

This trap is the user generated critical severity trap. This trap is only applicable for SGX4000.

This trap is the user generated major severity trap. This trap is only applicable for SGX4000.

This trap is the user generated minor severity trap. This trap is only applicable for SGX4000.

This trap is the user generated info severity trap. This trap is only applicable for SGX4000.

This trap indicates the reason for the service restarting.

This trap indicates indicates that this CE started to switchover but the process did not complete, leaving the system in an undefined state. This trap is only applicable for SGX4000.

This trap indicates there is a connection issue with the remote server being used for rsyslog.

This trap indicates that connection has been established for the remote server being used for rsyslog

This trap indicates that space on the hard disk is low and no more data can be written and operating in read only mode.

This trap indicates that CRC error rate has exceeded set threshold for the set duration.

This trap indicates that the RCR error rate gone below the clear threshold for the clear duration.

This trap indicates that the Resource Error rate has exceeded set threshold for the set duration.

This trap indicates that the Resource Error rate gone below the clear threshold for the clear duration.

This trap indicates that the Overflow Error Rate rate has exceeded set threshold for the set duration.

This trap indicates that the Overflow Error Rate rate gone below the clear threshold for the clear duration.

This trap indicates that the Dropped Packets rate has exceeded set threshold for the set duration.

This trap indicates that the Dropped Packets rate gone below the clear threshold for the clear duration.

This trap indicates that the RBR Prefetch Empty rate has exceeded set threshold for the set duration.

This trap indicates that the RBR Prefetch Empty rate gone below the clear threshold for the clear duration.

This trap indicates that the RBR Empty rate has exceeded set threshold for the set duration.

This trap indicates that CRC error rate gone below the clear threshold for the clear duration.

This trap indicates that the RBR Empty rate gone below the clear threshold for the clear duration.

This trap indicates that the WRED Dropped Packets rate has exceeded set threshold for the set duration.

This trap indicates that the WRED Dropped Packets rate gone below the clear threshold for the clear duration.

This trap indicates a fatal mailbox error.

This trap indicates a fatal NACK Packet Read Error.

This trap indicates a fatal NACK Prefetch Error.