Fault, Alarm, Trap, and SNMP Errors
The following table lists all fault, alarm, trap, and SNMP errors, the reason the error is displayed, and recommended actions to take, if applicable.
| Error Code | Reason For the Error |
|---|---|
| 7001 | Could not start. This error occurs due to a network or connectivity issue with a service or device.
Recommended action: Try again. If the error recurs, contact your system administrator. |
| 7002 | Could not display requested stats. This error occurs due to a network or connectivity issue with a service or device.
Recommended action: Try again. If the error recurs, contact your system administrator. |
| 7003 | Could not find the requested MIB object. This error occurs when the requested object or record does not exist in the system.
Recommended action: Try again. If the error recurs, contact your system administrator. |
| 7004 | Could not find the requested MIB index. This error occurs when the requested object or record does not exist in the system.
Recommended action: Contact your system administrator. |
| 7005 | Could not retrieve the SNMP values from due to a timeout error. This error occurs due to a network or connectivity issue with a service or device.
Recommended action: Try again. If the error recurs please check device status. |
| 7006 | Cannot get event id(s) from local cache. This error occurs due to a network or connectivity issue with a service or device.
Recommended action: Try again. If the error recurs please check database manager. |
| 7007 | Cannot get northbound trap receivers. This error occurs due to a network or connectivity issue with a service or device.
Recommended action: Try again. If the error recurs please check database manager. |
| 7008 | The trap receiver exists already. This error occurs due to a network or connectivity issue with a service or device.
Recommended action: Enter new values again. |
| 7009 | Cannot find trap receiver for. This error occurs due to a network or connectivity issue with a service or device.
Recommended action: Try again. If the error recurs please check database manager. |
| 7010 | Failed to delete trap receiver(s). This error occurs due to a network or connectivity issue with a service or device.
Recommended action: Try again. If the error recurs please check database manager. |
| 7011 | Cannot get email notification list. This error occurs due to a network or connectivity issue with a service or device.
Recommended action: Try again. If the error recurs please check database manager. |
| 7012 | The email notification exists already. This error occurs due to a network or connectivity issue with a service or device.
Recommended action: Enter new values again. |
| 7013 | The trap synchronization failed for group, devices. This error occurs due to a network or connectivity issue with a service or device.
Recommended action: Enter new values again. |
| 7014 | Could not get TrapManager. This error occurs due to a network or connectivity issue with a service or device.
Recommended action: Try again. If the error recurs please check SNMP service. |
| 7015 | Could not get device FSM lock for ip, device name. This error occurs due to a network or connectivity issue with a service or device.
Recommended action: Try again. If the error recurs please check FSM service. |
| 7016 | Could not get device trap-receiver community name. This error occurs due to a network or connectivity issue with a service or device.
Recommended action: Check database manager. |
| 7017 | Could not get community name from device details for. This error occurs due to a network or connectivity issue with a service or device.
Recommended action: Check database manager. |
| 7018 | Unknown SNMP protocal version for. This error occurs due to a network or connectivity issue with a service or device.
Recommended action: Check SNMP supported version. |
| 7019 | Could not get community name from load LCC for. This error occurs due to a network or connectivity issue with a service or device.
Recommended action: Check database manager. |
| 7020 | Failed to update trap receiver(s). This error occurs due to a network or connectivity issue with a service or device.
Recommended action: Try again. If the error recurs please check system administrator. |
| 7021 | Failed to synchronize trap receiver(s). This error occurs due to a network or connectivity issue with a service or device.
Recommended action: Try again. If the error recurs please check system administrator. |
| 7022 | The max number trap receivers are allowed. This error occurs due to a network or connectivity issue with a service or device.
Recommended action: Delete some unused trap receivers, then add new ones. |
| 7023 | Could not retrieve the SNMP values from due to bad data. This error occurs due to a network or connectivity issue with a service or device.
Recommended action: Try again. If the error recurs please check device status. |
| 7024 | Failed to load SNMP resource for Plugin. This error occurs due to a network or connectivity issue with a service or device.
Recommended action: Try again. If the error recurs please check Plugin service. |
| 7025 | Failed to retrieve trap map info for. This error occurs due to a network or connectivity issue with a service or device.
Recommended action: Try again. If the error recurs please check SNMP service. |
| 7026 | Invalid SNMP resource for plugin. This error occurs when a required input is missing, empty, or incorrectly formatted.
Recommended action: Try again. If the error recurs please check SNMP service. |
| 7027 | Failed to retrieve SNMP values from. This error occurs due to a network or connectivity issue with a service or device.
Recommended action: Try again. If the error recurs please check SNMP service. |
| 7029 | Response PDU is null. This may be caused by interrupted thread from ExecutorCompletionService. This error occurs when a required input is missing, empty, or incorrectly formatted.
Recommended action: Try again. If the error recurs please check SNMP service. |
| 8001 | TrapRelay could not bind requested port. This error occurs due to an unexpected internal system condition.
Recommended action: Confirm port is available and try again. |
| 9001 | Could not start. This error occurs due to a service startup, shutdown, or lifecycle failure.
Recommended action: Try again. |
| 9002 | Database out of sync. This error occurs due to a database read or write failure.
Recommended action: Shutdown forced to initiate recovery. |
| 9003 | Could not delete (s) due to database error. This error occurs due to an unexpected internal system condition.
Recommended action: Try again. |
| 9004 | Could not get access to the SNMP service. This error occurs due to a network or connectivity issue with a service or device.
Recommended action: Contact your system administrator. |
| 9005 | Database error. This error occurs due to a database read or write failure.
Recommended action: Try again. |
| 9006 | EMSException thrown. This error occurs due to an unexpected internal system condition.
Recommended action: Contact your system administrator. |
| 9007 | Cannot get event global ID(s) from database. This error occurs due to an unexpected internal system condition.
Recommended action: Check database manager. |
| 9008 | Cannot get enough event IDs block from database. This error occurs due to an unexpected internal system condition.
Recommended action: Check database manager. |
| 9009 | Cannot get event ID(s) from local cache. This error occurs due to an unexpected internal system condition.
Recommended action: Check fault manager. |
| 9010 | Cannot release fault event lock for host. This error occurs due to permission restrictions or resource locking.
Recommended action: Check fault manager. |
| 9011 | Cannot acknowledge alarm(s). This error occurs due to an unexpected internal system condition.
Recommended action: Check fault manager. |
| 9013 | Cannot get details. This error occurs due to an unexpected internal system condition.
Recommended action: Check fault manager. |
| 9014 | Cannot update alarm annotation. This error occurs due to an unexpected internal system condition.
Recommended action: Check fault manager. |
| 9015 | Cannot get attribute names from database. This error occurs due to an unexpected internal system condition.
Recommended action: Check database manager. |
| 9017 | Cannot retrieve mail server configuration from database. This error occurs due to an unexpected internal system condition.
Recommended action: Check database and fault manager. |
| 9018 | Retrieved mail server configuration from database. Should be one and only one. This error occurs due to an unexpected internal system condition.
Recommended action: Check fault manager. |
| 9019 | Failed to schedule the Fault clean up task. This error occurs due to an unexpected internal system condition.
Recommended action: Check fault manager. |
| 9020 | Failed to add the event into the database with category-, FailedResource-, sourceHost- trap name-, severity. This error occurs due to an unexpected internal system condition.
Recommended action: Check fault manager. |
| 9021 | Failed to lookup probable cause with the given name. This error occurs when the requested object or record does not exist in the system.
Recommended action: Check fault manager. |
| 9022 | Failed to lookup fault source with the given name. This error occurs when the requested object or record does not exist in the system.
Recommended action: Check fault manager. |
| 9023 | Failed to lookup event type with the given name. This error occurs when the requested object or record does not exist in the system.
Recommended action: Check fault manager. |
| 9024 | Failed to lookup severity with the given name. This error occurs when the requested object or record does not exist in the system.
Recommended action: Check fault manager. |
| 9030 | Failed to deliver update trap source information to MCE. This error occurs due to an unexpected internal system condition.
Recommended action: Check fault manager. |
| 9031 | Failed to hand NF managing status update with added NF- and removed NF. This error occurs due to an unexpected internal system condition.
Recommended action: Check fault manager. |
| 9032 | Failed to handle trap load balancing when MCE- is connected. This error occurs due to a network or connectivity issue with a service or device.
Recommended action: Check fault manager. |
| 9033 | Failed to process new trap for device. This error occurs due to an unexpected internal system condition.
Recommended action: Check fault manager. |
| 9034 | Failed to find associated MC for network function. This error occurs due to an unexpected internal system condition.
Recommended action: Check fault manager. |
| 9035 | Entries to delete is and exceeds the maximum allowed. This error occurs due to an unexpected internal system condition.
Recommended action: Adjust the criteria for deletion and try again. |
| 9036 | Unable to process request. A maximum of entries can be saved to file. This error occurs due to an unexpected internal system condition.
Recommended action: Adjust your criteria and try again. |
| 9037 | Failed to retrieve Trap Source information for MCE. This error occurs due to an unexpected internal system condition.
Recommended action: Adjust your criteria and try again. |
| 9039 | Failed to lookup Trap Forwarding Format of the type. This error occurs when the requested object or record does not exist in the system.
Recommended action: Check the selected trap forwarding format and try again. |
| 9040 | Failed to lookup Trap Receiver with the ID. This error occurs when the requested object or record does not exist in the system.
Recommended action: Check the selected trap receiver and try again. |
| 9041 | Failed to add Trap receiver. One with the same IP already exists. This error occurs when a duplicate object already exists with the same identifier or name.
Recommended action: Create Trap receiver with a unique IP and try again. |
| 9042 | Failed to add Trap receiver. Maximum Trap Receiver Limit reached. This error occurs due to an unexpected internal system condition.
Recommended action: Delete any unused Trap Receiver and try again. |
| 9043 | Failed to add Trap receiver. IP/FQDN not found. This error occurs when a required input is missing, empty, or incorrectly formatted.
Recommended action: Please add the trap receiver IP/FQDN and try again. |
| 9044 | Failed to edit Trap receiver. IP/FQDN cannot be edited. This error occurs due to an unexpected internal system condition.
Recommended action: Do not change the IP/FQDN and try again. |
| 9045 | Failed to fetch MCE for Trap Receiver. This error occurs when the requested object or record does not exist in the system.
Recommended action: Check that associated MCE exists and try again. |
| 9046 | Failed to fetch MCE association with Trap Receiver. This error occurs when the requested object or record does not exist in the system.
Recommended action: Check that association exists and try again. |
| 9047 | Failed to associate Trap Receiver(s) with MCE(s). Following associations already exist. This error occurs when a duplicate object already exists with the same identifier or name.
Recommended action: Check that there is no existing association and try again. |
| 9048 | Failed to associate Trap Receiver(s) with MCE(s). This error occurs due to an unexpected internal system condition.
Recommended action: Try again. |
| 9049 | Failed to associate Trap Receiver(s) with MCE(s). Can't associate more than 3 Trap Receiver per MCE. This error occurs due to an unexpected internal system condition.
Recommended action: Select 3 or lesser Trap receivers and try again. |
| 9050 | Failed to add Trap Filter. One with the same name already exists. This error occurs when a duplicate object already exists with the same identifier or name.
Recommended action: Create Trap filter with a unique name and try again. |
| 9051 | Failed to add Trap Filter. Maximum Trap Filter Limit reached. This error occurs due to an unexpected internal system condition.
Recommended action: Delete any unused Trap Filter and try again. |
| 9052 | Failed to add Trap filter. Trap Filter Name not found. This error occurs when a required input is missing, empty, or incorrectly formatted.
Recommended action: Add the trap filter name and try again. |
| 9053 | Failed to lookup Trap Filter with the ID. This error occurs when the requested object or record does not exist in the system.
Recommended action: Check the selected trap filter and try again. |
| 9054 | Failed to edit Trap filter. Trap Filter Name cannot be edited. This error occurs due to an unexpected internal system condition.
Recommended action: Change an attribute other than the trap filter name and try again. |
| 9055 | Failed to fetch MCE association with Trap Filter. This error occurs when the requested object or record does not exist in the system. Recommended action: Check that association exists and try again. |
| 9056 | Failed to associate Trap Filter(s) with MCE(s). Following associations already exist. This error occurs when a duplicate object already exists with the same identifier or name.
Recommended action: Check that there is no existing association and try again. |
| 9057 | Failed to associate Trap Filter(s) with MCE(s). This error occurs due to an unexpected internal system condition.
Recommended action: Try again. |
| 9058 | Failed to associate Trap Filter(s) with MCE(s). Cannot associate more than 50 Trap Filter(s) per MCE. This error occurs due to an unexpected internal system condition.
Recommended action: Select 50 or lesser Trap Filters and try again. |
| 9059 | Failed to lookup Trap Filter with the name. This error occurs when the requested object or record does not exist in the system.
Recommended action: Check the selected trap filter and try again. |
| 9060 | Failed to lookup Trap Receivers. This error occurs due to an unexpected internal system condition.
Recommended action: Access denied! This is an authorization breach. |
| 9061 | Failed to fetch SNMP Parameters for the SNMP mode. This error occurs when a required input is missing, empty, or incorrectly formatted.
Recommended action: Make sure you have selected valid SNMP Mode and try again. |
| 9062 | Failed to add Trap receiver. Invalid value for SNMP port. This error occurs when a required input is missing, empty, or incorrectly formatted.
Recommended action: Add the trap receiver with valid SNMP Port and try again. |
| 9063 | Failed to add Trap receiver. SNMP Community Name not found. This error occurs when a required input is missing, empty, or incorrectly formatted.
Recommended action: Add the trap receiver SNMP Community Name and try again. |
| 9064 | Failed to add Trap receiver. Invalid SNMP v2/v3 configuration. This error occurs when a required input is missing, empty, or incorrectly formatted.
Recommended action: Add valid SNMP Configuration and try again. |
| 9065 | Failed to find Trap receiver. This error occurs when the requested object or record does not exist in the system.
Recommended action: Try again. |
| 9068 | Failed to associate MCE(s) with Trap Receiver(s). More than 3 Trap Receivers selected. This error occurs due to an unexpected internal system condition.
Recommended action: Ensure that you select a maximum of 3 Trap Receivers and try again. |
| 9069 | Failed to associate MCE(s) with Trap Filter(s). More than 50 Trap Filters selected. This error occurs due to an unexpected internal system condition.
Recommended action: Ensure that you select a maximum of 50 Trap Filters and try again. |
| 9070 | Failed to synchronize traps. Start Time/End Time not selected. This error occurs when a required input is missing, empty, or incorrectly formatted.
Recommended action: Select both Start Time and End Time for synchronization and try again. |
| 9071 | Failed to synchronize traps. The selected Start Time is later than the End Time. This error occurs when a required input is missing, empty, or incorrectly formatted.
Recommended action: Choose a valid time range for synchronization and try again. |
| 9072 | Failed to generate Test Trap for the Trap Receiver. This error occurs due to an unexpected internal system condition.
Recommended action: Try again. |
| 9073 | Failed to fetch latest test trap event for the Trap Receiver. This error occurs due to an unexpected internal system condition.
Recommended action: Try again. |
| 9074 | Failed to fetch the Trap Receiver. This error occurs due to an unexpected internal system condition.
Recommended action: Ensure that selected trap receiver has valid ip/fqdn. |
| 9075 | Trap Receiver is not accessible by user group. This error occurs due to permission restrictions or resource locking.
Recommended action: Ensure that selected trap receiver is in the same user group as the user. |
| 9076 | Failed to Synchronize Traps. Sync duration must be within days from now. This error occurs due to an unexpected internal system condition.
Recommended action: Select a start/end date within purge interval days from now and try again. |
| 9077 | Failed to Synchronize Traps. Trap Receiver is not associated with any MCE. This error occurs due to an unexpected internal system condition.
Recommended action: Associate the Trap Receiver with an MCE. |
| 9078 | Failed to add Trap Receiver. The Authentication Password should be 6-15 characters long. This error occurs due to an unexpected internal system condition.
Recommended action: Enter a password that is 6-15 characters long. |
| 9079 | Failed to add Trap Receiver. The Privacy Password should be 6-15 characters long. This error occurs due to an unexpected internal system condition.
Recommended action: Enter a password that is 6-15 characters long. |
| 9080 | Failed to edit Trap Receiver. The Authentication Password should be 6-15 characters long. This error occurs due to an unexpected internal system condition.
Recommended action: Enter a password that is 6-15 characters long. |
| 9081 | Failed to edit Trap Receiver. The Privacy Password should be 6-15 characters long. This error occurs due to an unexpected internal system condition.
Recommended action: Enter a password that is 6-15 characters long. |
| 10028 | Version of is not supported for alarm synchronization. This error occurs due to an unexpected internal system condition.
Recommended action: Check SBC software image version. |
| 20000 | Could not look up fault manager registry. This error occurs due to a network or connectivity issue with a service or device.
Recommended action: Check the connection between FEApp fault and database manager. |
| 20001 | Error occurred in. This error occurs due to an unexpected internal system condition.
Recommended action: Check the FEApp fault. |
| 20002 | Could not get instance(s) for. This error occurs due to an unexpected internal system condition.
Recommended action: Please check the fault manager. |
| 20003 | Could not get instances for. This error occurs due to an unexpected internal system condition.
Recommended action: Check the fault manager. |
| 20004 | Could not delete (s). This error occurs due to an unexpected internal system condition.
Recommended action: Check the fault manager. |
| 20005 | Could not acknowledge alarm(s). This error occurs due to an unexpected internal system condition.
Recommended action: Check the fault manager. |
| 20006 | Could not clear alarm(s). This error occurs due to an unexpected internal system condition.
Recommended action: Check the fault manager. |
| 20007 | Could not look up device manager registry. This error occurs due to a network or connectivity issue with a service or device.
Recommended action: Check the connection between FEApp device and database manager. |
| 20008 | Search criteria "Date from" should be earlier than or equal to "Date to". This error occurs due to a service startup, shutdown, or lifecycle failure.
Recommended action: Correct the search criteria. |
| 20009 | Submit Heartbeat Trap task failed. This error occurs due to a service startup, shutdown, or lifecycle failure.
Recommended action: Check the fault manager. |
| 20010 | Failed to stop Heartbeat Trap task. This error occurs due to a service startup, shutdown, or lifecycle failure.
Recommended action: Check the fault manager. |
| 20011 | Failed to update Heartbeat Trap task. This error occurs due to an unexpected internal system condition.
Recommended action: Check the fault manager. |
| 20012 | Failed to retrieve the trap group list. This error occurs due to an unexpected internal system condition.
Recommended action: Check the fault manager. |
| 27043 | Unable to add default sub-element for. This error occurs due to an unexpected internal system condition.
Recommended action: Check with database service. |
| 39001 | Unable to restore all log levels. This error occurs due to an unexpected internal system condition.
Recommended action: Please try again. If the error recurs, contact your system administrator. |
| 49006 | Failure to retrieve ALarm KHI statistics error for. This error occurs due to an unexpected internal system condition.
Recommended action: Contact system administrator. |
| 100031 | The trap receiver with ip: is not in valid state for alarm sync. This error occurs when a required input is missing, empty, or incorrectly formatted.
Recommended action: Wait for the trap receiver to valid state and try again. |
| 100032 | The trap receiver with ip: admin state is disabled. This error occurs due to an unexpected internal system condition.
Recommended action: Enable the admin state and try again. |
| 100033 | The trap receiver with ip: is NNC format that does not support alarm sync. This error occurs due to an unexpected internal system condition.
Recommended action: Select other trap receivers. |
| 100034 | Sync alarm request must have valid start and end date. This error occurs due to a service startup, shutdown, or lifecycle failure.
Recommended action: Select other trap receivers. |
| 100293 | No alarms found for given parameters. This error occurs due to an unexpected internal system condition.
Recommended action: Provide a valid param. |