Explanation
The EMS Ethernet interface has a problem. The ping utility did not receive a response from the interface associated with the EMS.
Recovery
Consult with your network administrator.
Event Details
|
GUI Notification |
|
|
Severity |
None |
|
Text |
|
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - EMS interface failure |
|
Source |
Both servers |
|
Frequency |
Every 2.5 minutes as long as condition exists |
|
Trap |
|
|
Trap ID |
16 |
|
Trap MIB Name |
emsInterfaceFailure |
Explanation
The EMS, which is indicated in the System field on the GUI or whose CLLI has the value that replaces <CLLI> in the Surveillance notification text, requires a resynchronization with the LSMS that cannot be accomplished by automatic resynchronization between the LSMS and the EMS.
Recovery
Perform one of the synchronization procedures described in the LNP Database Synchronization User's Guide.
Event Details
|
GUI Notification |
|
|
Severity |
Critical |
|
Text |
DB Maintenance Required |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - NE CLLI=<CLLI> |
|
Source |
Active server |
|
Frequency |
As soon as condition occurs, and at five-minute intervals as long as condition exists |
|
Trap |
|
|
Trap ID |
33 |
|
Trap MIB Name |
emsRequiresResynchWithLSMS |
Explanation
The LSMS has lost association with the primary EMS of the network element, which is indicated in the System field on the GUI or whose CLLI has the value that replaces <CLLI> in the Surveillance notification text; the association with the secondary EMS is established.
Recovery
Determine why the primary association failed (connectivity problem, EMS software problems, NE software problem, etc.). Correct the problem. Association will be automatically retried.
Event Details
|
GUI Notification |
|
|
Severity |
Major |
|
Text |
Primary Association Failed |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - NE CLLI=<CLLI> |
|
Source |
Active server |
|
Frequency |
As soon as condition occurs, and at five-minute intervals as long as condition exists |
|
Trap |
|
|
Trap ID |
5 |
|
Trap MIB Name |
primaryEMSAssocLostSecEstablished |
Explanation
The LSMS has lost association with the primary EMS of the network element, which is indicated in the System field on the GUI or whose CLLI has the value that replaces <CLLI> in the Surveillance notification text; the association with the secondary EMS is not established.
Recovery
Determine why the primary association failed (connectivity problem, EMS software problems, NE software problem, etc.). Correct the problem, and then reestablish the association with the primary EMS.
Event Details
|
GUI Notification |
|
|
Severity |
Critical |
|
Text |
Primary Association Failed |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - NE CLLI=<CLLI> |
|
Source |
Active server |
|
Frequency |
As soon as condition occurs, and at five-minute intervals as long as condition exists |
|
Trap |
|
|
Trap ID |
36 |
|
Trap MIB Name |
primaryEMSAssocLostNoSec |
Explanation
The pending queue used to hold transactions to be sent to the EMS/NE, which is indicated in the System field on the GUI or whose CLLI has the value that replaces <CLLI> in the Surveillance notification text, is full. To help ensure that no updates are lost, the eagleagent will abort associations with both the primary EMS and secondary EMS. Updates will be queued in a resynchronization log until the EMS reassociates.
Recovery
Determine why the EMS/NE is not receiving LNP updates, and correct the problem.
Event Details
|
GUI Notification |
|
|
Severity |
Critical |
|
Text |
All Association(s) Aborted: Pending Queue Full |
|
Surveillance Notification |
|
|
Text |
None |
|
Source |
|
|
Frequency |
|
|
Trap |
|
|
Trap ID |
97 |
|
Trap MIB Name |
emsAssociationAbortedQueueFull |
Explanation
The network element, which is indicated in the System field on the GUI or whose CLLI has the value that replaces <CLLI> in the Surveillance notification text, is busy and is sending ’retry later’ in response to a message sent by the eagleagent. The eagleagent has already tried resending the same message the maximum number of times. The eagleagent has aborted associations with both the primary EMS and secondary EMS.
Recovery
Correct the problem at the network element. When the EMS reconnects with the LSMS, the LSMS will automatically resynchronize the network element’s LNP database.
Event Details
|
GUI Notification |
|
|
Severity |
Critical |
|
Text |
All Association(s) Aborted: Retries Exhausted |
|
Surveillance Notification |
|
|
Text |
None |
|
Source |
|
|
Frequency |
|
|
Trap |
|
|
Trap ID |
98 |
|
Trap MIB Name |
emsAssocAbortedMaxResend |
Explanation
The LSMS has lost association with the secondary EMS which is indicated in the System field on the GUI or whose CLLI has the value that replaces <CLLI> in the Surveillance notification text. The association with the primary EMS is still up.
Recovery
Determine why the secondary association failed (connectivity problem, EMS software problems, NE software problem, etc.) and then reestablish the association with the secondary EMS.
Event Details
|
GUI Notification |
|
|
Severity |
Major |
|
Text |
Secondary Association Failed |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - NE CLLI=<CLLI> |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
130 |
|
Trap MIB Name |
secondaryEMSAssocLost |
Explanation
The LSMS has established the first association with the network element (NE) which is indicated in the System field on the GUI or whose CLLI has the value that replaces <CLLI> in the Surveillance notification text. The first association established is called the primary association. This EMS is called the primary EMS.
Recovery
No action required; this notification is for information only.
Event Details
|
GUI Notification |
|
|
Severity |
Cleared |
|
Text |
Primary Association Established |
|
Surveillance Notification |
|
|
Text |
None |
|
Source |
|
|
Frequency |
|
|
Trap |
|
|
Trap ID |
8 |
|
Trap MIB Name |
primaryEMSAssocEstablished |
Explanation
The LSMS has established the second association with the network element (NE) which is indicated in the System field on the GUI or whose CLLI has the value that replaces <CLLI> in the Surveillance notification text. The association is established only if a primary association already exists. This EMS is called the secondary EMS.
Recovery
No action required; this notification is for information only.
Event Details
|
GUI Notification |
|
|
Severity |
Cleared |
|
Text |
Secondary Association Established |
|
Surveillance Notification |
|
|
Text |
None |
|
Source |
|
|
Frequency |
|
|
Trap |
|
|
Trap ID |
134 |
|
Trap MIB Name |
secondaryEMSAssocEstablished |
Explanation
The primary association for the EMS/NE, which is indicated in the System field on the GUI or whose CLLI has the value that replaces <CLLI> in the Surveillance notification text, is either down or is inhibited, such that transactions sent to the primary EMS will not be received by the NE. Transactions are being sent to the secondary EMS instead of the primary EMS.
Recovery
Determine why the primary association failed (connectivity problem, EMS software problem, NE software problem, or other problem). Correct the problem. Association will be automatically retried. When the association is reestablished, it will be a secondary association, and the EMS will be the secondary EMS.
Event Details
|
GUI Notification |
|
|
Severity |
Cleared |
|
Text |
Successful Switchover Occurred to Secondary EMS |
|
Surveillance Notification |
|
|
Text |
None |
|
Source |
|
|
Frequency |
|
|
Trap |
|
|
Trap ID |
139 |
|
Trap MIB Name |
transactionToSecondary |
Explanation
The NPAC Ethernet interface has a problem. The ping utility did not receive a response from the interface associated with the NPAC.
Recovery
Consult with your network administrator.
Event Details
|
GUI Notification |
|
|
Severity |
None |
|
Text |
|
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - NPAC interface failure |
|
Source |
Both primary and secondary servers |
|
Frequency |
Every 2.5 minutes as long as condition exists |
|
Trap |
|
|
Trap ID |
15 |
|
Trap MIB Name |
npacInterfaceFailure |
Explanation
The association with the NPAC identified by <NPAC_region_ID> has been disconnected by the user.
Recovery
Examine additional GUI notifications to determine whether the LSMS is retrying the association. Follow the recovery actions described for the GUI notification.
Event Details
|
GUI Notification |
|
|
Severity |
Critical |
|
Text |
NPAC [<PRIMARY|SECONDARY>-<NPAC_region_ID>] Connection Disconnected |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - NPAC=<PRIMARY|SECONDARY>-<NPAC_region_ID> |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
37 |
|
Trap MIB Name |
lostNPACAssoc |
Explanation
The LSMS is not able to confirm the physical connectivity with the NPAC, which is specified in the System field on the GUI or is indicated by <NPAC_region_ID> in the Surveillance notification.
Recovery
Check the physical connection between the LSMS and the NPAC. The problem may be in the network, a router, or both.
Event Details
|
GUI Notification |
|
|
Severity |
Critical |
|
Text |
LSMS Physical Disconnect with NPAC |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - NPAC=<NPAC_region_ID> |
|
Source |
Active server |
|
Frequency |
As soon as condition occurs, and at five-minute intervals as long as condition exists |
|
Trap |
|
|
Trap ID |
45 |
|
Trap MIB Name |
failedNPACConnectivity |
Explanation
The NPAC (PRIMARY or SECONDARY, as indicated) identified by <NPAC_region_ID> rejected the association because it received a message from the LSMS that failed security checks. This can be due to one of the following:
The CMIP departure time is more than five minutes out of synchronization with the NPAC servers.
The security key is not valid.
The CMIP sequence number is out of sequence (messages must be returned to the NPAC in the same order in which they were received).
Recovery
Do the following:
Log in as lsmsadm to the active server.
Enter the following command to determine what the LSMS system time is:
$ dateContact the NPAC administrator to determine what the NPAC time is. If the NPAC time is more than five minutes different from the LSMS time, reset the LSMS system time on both servers and on the administration console using one of the procedures described in “Managing the System Clock”.
After you have verified that the NPAC and LSMS times are within five minutes of each other, cause a different security key to be used by stopping and restarting the regional agent. Enter the following commands, where <region> is the name of the region in which this notification occurred:
$LSMS_DIR/lsms stop <region> $LSMS_DIR/lsms start <region>Start the GUI again.
Attempt to reassociate with the NPAC. For information about associating with an NPAC, refer to the Configuration Guide.
If the problem persists, contact Oracle Technical Service.
Event Details
|
GUI Notification |
|
|
Severity |
Critical |
|
Text |
NPAC [<PRIMARY|SECONDARY>-<NPAC_region_ID>] Connection Aborted by PEER: Access Control Failure |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - NPAC=<PRIMARY|SECONDARY>-<NPAC_region_ID> |
|
Source |
Active server |
|
Frequency |
As soon as condition occurs, and at five-minute intervals as long as condition exists |
|
Trap |
|
|
Trap ID |
95 |
|
Trap MIB Name |
npacRejectedAssocAccessCtrlFail |
Explanation
The primary or secondary NPAC, identified by <NPAC_region_ID>, rejected the association because it received data that was not valid.
Recovery
Contact the NPAC administrator.
Event Details
|
GUI Notification |
|
|
Severity |
Critical |
|
Text |
NPAC [<PRIMARY|SECONDARY>-<NPAC_region_ID>] Connection Aborted by PEER: Invalid Data Received |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - NPAC= <PRIMARY|SECONDARY>-<NPAC_region_ID> |
|
Source |
Active server |
|
Frequency |
As soon as condition occurs, and at five-minute intervals as long as condition exists |
|
Trap |
|
|
Trap ID |
96 |
|
Trap MIB Name |
npacRejectedAssocInvalidData |
Explanation
The LSMS has lost association with the primary or secondary NPAC identified by <NPAC_region_ID> because the user aborted the association.
Recovery
Reassociate with the NPAC when the reason for aborting the association no longer exists. For information about associating with an NPAC, refer to the Configuration Guide.
Event Details
|
GUI Notification |
|
|
Severity |
Critical |
|
Text |
NPAC [<PRIMARY|SECONDARY>]-<NPAC_region_ID> Association Aborted by User |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - NPAC= <PRIMARY|SECONDARY>-<NPAC_region_ID> |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
9 |
|
Trap MIB Name |
npacAbortByUser |
Explanation
The LSMS did not receive an association response from the NPAC within the timeout period. The LSMS will attempt the association with the NPAC again after an interval that defaults to two minutes, but can be configured to a different value by Oracle.
Recovery
Determine whether there is a network connection problem and/or contact the NPAC administrator to determine whether the NPAC is up and running.
Event Details
|
GUI Notification |
|
|
Severity |
Critical |
|
Text |
NPAC [<PRIMARY|SECONDARY>-<NPAC_region_ID>] Bind Timed Out - Auto Retry After NPAC_RETRY_INTERVAL |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - NPAC= <PRIMARY|SECONDARY>-<NPAC_region_ID> |
|
Source |
Active server |
|
Frequency |
As soon as condition occurs, and at two-minute intervals as long as condition exists |
|
Trap |
|
|
Trap ID |
100 |
|
Trap MIB Name |
assocRespNPACTimeout |
Explanation
The NPAC association attempt was rejected by the NPAC, and the LSMS was informed to attempt the NPAC association again to the same NPAC host after an interval that defaults to two minutes, but can be configured to a different value by Oracle.
Recovery
No action required; the LSMS will automatically try to associate again.
Event Details
|
GUI Notification |
|
|
Severity |
Critical |
|
Text |
NPAC [<PRIMARY|SECONDARY>-<NPAC_region_ID>] Connection Aborted by PEER - Auto Retry Same Host After NPAC_RETRY_INTERVAL |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - NPAC=< PRIMARY|SECONDARY>-<NPAC_region_ID> |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
101 |
|
Trap MIB Name |
assocRejectedRetrySameHost |
Explanation
The NPAC association attempt was rejected by the NPAC, and the LSMS was informed to attempt the NPAC association again to the other NPAC host after an interval that defaults to two minutes, but can be configured to a different value by Oracle.
Recovery
No action required; the LSMS will automatically try to associate again.
Event Details
|
GUI Notification |
|
|
Severity |
Critical |
|
Text |
NPAC [<PRIMARY|SECONDARY>]-<NPAC_region_ID>- Connection Aborted by PEER - Auto Retry Other Host After NPAC_RETRY_INTERVAL |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - NPAC= <PRIMARY|SECONDARY>-<NPAC_region_ID> |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
102 |
|
Trap MIB Name |
assocRejectedRetryOtherHost |
Explanation
A problem exists in the network connectivity. The LSMS will attempt the association with the NPAC again after an interval that defaults to two minutes, but can be configured to a different value by Oracle.
Recovery
Check the network connectivity for errors. Verify the ability to ping the NPAC from the LSMS.
Event Details
|
GUI Notification |
|
|
Severity |
Critical |
|
Text |
NPAC [<PRIMARY|SECONDARY>-<NPAC_region_ID>] Connection Aborted by PROVIDER - Auto Retry Same Host After NPAC_RETRY_INTERVAL |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - NPAC= <PRIMARY|SECONDARY>-<NPAC_region_ID> |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
103 |
|
Trap MIB Name |
nwtkProblemRetryNPACAssoc |
Explanation
The LSMS received three consecutive responses from the NPAC with a download status of failure from a recovery action request. The LSMS has aborted the association and will attempt to associate again after a retry interval that defaults to five minutes, but can be configured to a different value by Oracle. The LSMS will retry the recovery action after the association is reestablished.
Recovery
No action required; the LSMS will automatically try to associate again.
Event Details
|
GUI Notification |
|
|
Severity |
Critical |
|
Text |
NPAC [<PRIMARY|SECONDARY>-<NPAC_region_ID>] Connection Aborted Due to Recovery Failure - Auto Retry After NPAC_RETRY_INTERVAL |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - NPAC= <PRIMARY|SECONDARY>-<NPAC_region_ID> |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
104 |
|
Trap MIB Name |
lsmsAbortedNPACassocDowRecFail |
Explanation
The LSMS has disconnected the association with the NPAC region in question due to the lack of a response to heartbeat messages from the LSMS to the NPAC.
Recovery
Contact the My Oracle Support (MOS).
Event Details
|
GUI Notification |
|
|
Severity |
Critical |
|
Text |
NPAC [<PRIMARY|SECONDARY>-<NPAC_region_ID>] Connection Disconnected by Heartbeat |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - NPAC= <PRIMARY|SECONDARY>-<NPAC_region_ID> |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
111 |
|
Trap MIB Name |
lostNPACAssoc |
Explanation
The NPAC (primary or secondary, as indicated) identified by <NPAC_region_ID> rejected the association because of an access control failure. This can be due to one of the following:
The OSI Presentation Address is incorrect.
The Service Provider ID in the regional configuration file is incorrect.
The CMIP departure time is more than five minutes out of synchronization with the NPAC servers.
The security key is not valid.
Recovery
Do the following:
Verify that the correct PSEL, SSEL, TSEL, and NSAP values have been configured for the OSI Presentation Address (for more information, refer to “Viewing a Configured NPAC Component” in the Configuration Guide). If you need to change the values, use the procedure described in “Modifying an NPAC Component” in the Configuration Guide.
Verify that the configured Service Provider ID (SPID) is the same as the SPID assigned by the NPAC. For more information about this configuration file, refer to “Modifying LSMS Configuration Components” in the Configuration Guide.
Verify that the configured NPAC_SMS_NAME is the same as the value assigned by the NPAC (this field is case-sensitive). For more information about this configuration file, refer to “Modifying an NPAC Component” in the Configuration Guide.
Log in as lsmsadm to the active server.
Enter the following command to determine what the LSMS system time is:
$ dateContact the NPAC administrator to determine what the NPAC time is. If the NPAC time is more than five minutes different from the LSMS time, reset the LSMS system time on both servers and on the administration console by performing one of the procedures described in “Managing the System Clock”.
After you have verified that the NPAC and LSMS times are within five minutes of each other, cause a different security key to be used by stopping and restarting the regional agent. Enter the following commands, where <region> is the name of the region in which this notification occurred:
$ $LSMS_DIR/lsms stop <region> $ $LSMS_DIR/lsms start <region>Start the GUI again.
Attempt to reassociate with the NPAC.
If the problem persists, contact Oracle Technical Service.
Event Details
|
GUI Notification |
|
|
Severity |
Critical |
|
Text |
NPAC [<PRIMARY|SECONDARY>-<NPAC_region_ID>] Connection Attempt Failed: Access Control Failure |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - NPAC= <PRIMARY|SECONDARY>-<NPAC_region_ID> |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
106 |
|
Trap MIB Name |
assocRejDueToAccessControl |
Explanation
The userInfo value in the cmipUserInfo portion of the NPAC association response CMIP message is not valid.
Recovery
Contact the NPAC administrator to determine why the NPAC is sending an invalid association response.
Event Details
|
GUI Notification |
|
|
Severity |
Critical |
|
Text |
NPAC [<PRIMARY|SECONDARY>-<NPAC_region_ID>] Connection Attempt Failed: Invalid Data Received |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - NPAC= <PRIMARY|SECONDARY>-<NPAC_region_ID> |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
108 |
|
Trap MIB Name |
npacConnFailedCMIP |
Explanation
The NPAC association was terminated gracefully by the NPAC.
Recovery
According to the NANC specifications, this should never occur; if this message is seen, contact the NPAC administrator for the reason for the association unbind.
Event Details
|
GUI Notification |
|
|
Severity |
Critical |
|
Text |
NPAC [<PRIMARY|SECONDARY>-<NPAC_region_ID>] Connection Disconnected by NPAC |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - NPAC= <PRIMARY|SECONDARY>-<NPAC_region_ID> |
|
Source |
Active server |
|
Frequency |
As soon as condition occurs, and at five-minute intervals as long as condition exists |
|
Trap |
|
|
Trap ID |
109 |
|
Trap MIB Name |
npacAssocGracefullyTerminated |
Explanation
The LSMS was unable to properly resynchronize (with the NPAC) the data that was lost while the LSMS was not associated with the NPAC.
Recovery
Do the following:
Abort the NPAC association (refer to the Configuration Guide).
Attempt to reassociate with the NPAC (refer to the Configuration Guide).
If the reassociation is not successful, contact the NPAC and contact the My Oracle Support (MOS).
Event Details
|
GUI Notification |
|
|
Severity |
Critical |
|
Text |
NPAC [<PRIMARY|SECONDARY>-<NPAC_region_ID>] Recovery Failed |
|
Surveillance Notification |
|
|
Text |
None |
|
Source |
|
|
Frequency |
|
|
Trap |
|
|
Trap ID |
112 |
|
Trap MIB Name |
lsmsDataLostBadResynch |
Explanation
The LSMS data lost during the resynchronization time was not resynchronized properly with the NPAC.
Recovery
Do the following:
Abort the NPAC association (refer to the Configuration Guide).
Reestablish the NPAC association (refer to the Configuration Guide).
Determine whether notification 8055 NPAC <PRIMARY|SECONDARY> Recovery Complete is posted. If instead notification 2019 reappears, perform a resynchronization for a period of time starting one hour before the 2019 notification first appeared, using either the GUI (refer to “Resynchronizing for a Defined Period of Time Using the GUI” in the Database Administrator's Guide).
If 2019 continues to appear, contact the My Oracle Support (MOS).
Event Details
|
GUI Notification |
|
|
Severity |
Critical |
|
Text |
NPAC [<PRIMARY|SECONDARY>-<NPAC_region_ID>] Recovery Partial Failure |
|
Surveillance Notification |
|
|
Text |
NPAC [<PRIMARY|SECONDARY>-<NPAC_region_ID>] Recovery Failure |
|
Source |
Active server |
|
Frequency |
Once , as soon as condition occurs |
|
Trap |
|
|
Trap ID |
113 |
|
Trap MIB Name |
badNPACresynchTime |
Explanation
The LSMS aborted the NPAC association because the LSMS received a message from the NPAC that did not have the correct LSMS key signature.
Recovery
Verify that the correct keys are being used by both the NPAC and the LSMS.
Event Details
|
GUI Notification |
|
|
Severity |
Critical |
|
Text |
NPAC [<PRIMARY|SECONDARY>-<NPAC_region_ID>] Security Violation. Association Aborted. Retrying |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - NPAC= <PRIMARY|SECONDARY>-<NPAC_region_ID> |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
114 |
|
Trap MIB Name |
assocAbortedBadKeys |
Explanation
An associate retry timer was in effect. The retry attempt was canceled because a GUI user issued an Associate, Abort or Disconnect request. If an Associate request was issued, the association is attempted immediately.
Recovery
No action required; for information only.
Event Details
|
GUI Notification |
|
|
Severity |
Major |
|
Text |
NPAC [<PRIMARY|SECONDARY>-<NPAC_region_ID>] Automatic Association Retry Canceled |
|
Surveillance Notification |
|
|
Text |
None |
|
Source |
|
|
Frequency |
|
|
Trap |
|
|
Trap ID |
122 |
|
Trap MIB Name |
npacAutoAssociationRetryCanceled |
Explanation
Either the LSMS did not receive any response from the NPAC before a timeout expired or the LSMS received a response from the NPAC with a download status of failure from a recovery action request. The NPAC is unable to process the recovery action due to a temporary resource limitation. The LSMS will retry the request for the number of times indicated by <retry_number> with the interval between each retry indicated by <retry_interval> minutes. If recovery is not successful after the indicated number of retries, the LSMS will abort the association and post the following notification:
[Critical]: <Timestamp> 2010 : NPAC [<PRIMARY|SECONDARY>-<NPAC_region_ID>] Connection Aborted Due to Recovery Failure - Auto Retry After NPAC_RETRY_INTERVAL
Recovery
No action required; for information only.
Event Details
|
GUI Notification |
|
|
Severity |
Major |
|
Text |
NPAC [<PRIMARY|SECONDARY>-<NPAC_region_ID>] Fail/No Response from NPAC Recovery - Auto Retry <retry_number> Times in <retry_interval> Minutes |
|
Surveillance Notification |
|
|
Text |
None |
|
Source |
|
|
Frequency |
|
|
Trap |
|
|
Trap ID |
123 |
|
Trap MIB Name |
npacRecoveryFailureResourceLimit |
Explanation
The NPAC association will be down for the specified period of time (from the first time field shown in the notification to the second time field shown in the notification) due to NPAC-scheduled down time.
Recovery
When the scheduled down time is over, manually reestablish the NPAC association. For information about aborting and reestablishing an association, refer to the Configuration Guide.
Event Details
|
GUI Notification |
|
|
Severity |
Major |
|
Text |
NPAC [<PRIMARY|SECONDARY>-<NPAC_region_ID>] ScheduleDownTime from [<YYYYMMDDhhmmss>] to [<YYYYMMDDhhmmss>] |
|
Surveillance Notification |
|
|
Text |
None |
|
Source |
|
|
Frequency |
|
|
Trap |
|
|
Trap ID |
124 |
|
Trap MIB Name |
npacAssocPeriodDown |
Explanation
An Associate request has been sent to the NPAC after a retry timer expired.
Recovery
No action required; for information only.
Event Details
|
GUI Notification |
|
|
Severity |
Major |
|
Text |
NPAC [<PRIMARY|SECONDARY>-<NPAC_region_ID>] Timer Expired - Resending Association Request |
|
Surveillance Notification |
|
|
Text |
None |
|
Source |
|
|
Frequency |
|
|
Trap |
|
|
Trap ID |
125 |
|
Trap MIB Name |
npacAssocRequestSentAfterRetryTimer |
Explanation
The NPAC association was successfully established.
Recovery
No action required; for information only.
Event Details
|
GUI Notification |
|
|
Severity |
Cleared |
|
Text |
NPAC [<PRIMARY|SECONDARY>-<NPAC_region_ID>] Connection Successfully Established |
|
Surveillance Notification |
|
|
Text |
None |
|
Source |
|
|
Frequency |
|
|
Trap |
|
|
Trap ID |
7 |
|
Trap MIB Name |
npacAssocEstablished |
Explanation
The active server has initiated an automatic switchover to the inactive server.
Recovery
No action required; for information only.
Event Details
|
GUI Notification |
|
|
Severity |
Event |
|
Text |
Switchover Initiated |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - Switchover initiated |
|
Source |
Active server |
|
Frequency |
Once, soon as condition occurs. |
|
Trap |
|
|
Trap ID |
11 |
|
Trap MIB Name |
switchOverStarted |
Explanation
LSMS service has been switched over.
Recovery
No action required; for information only.
Event Details
|
GUI Notification |
|
|
Severity |
Event |
|
Text |
Switchover complete |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - Switchover complete |
|
Source |
Active server |
|
Frequency |
Once, soon as condition occurs. |
|
Trap |
|
|
Trap ID |
12 |
|
Trap MIB Name |
switchOverCompleted |
Explanation
LSMS service could not be switched over to the inactive server; the inactive server was not able to start LSMS service.
Recovery
Contact the My Oracle Support (MOS).
Event Details
|
GUI Notification |
|
|
Severity |
Event |
|
Text |
Switchover Failed |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - Switchover Failed |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs. |
|
Trap |
|
|
Trap ID |
13 |
|
Trap MIB Name |
switchOverFailed |
Explanation
The Ethernet interface used to connect to the application network has a problem. This interface usually connects to network-connected workstations. The ping utility did not receive a response from the interface associated with the application network.
Recovery
Consult with your network administrator.
Event Details
|
GUI Notification |
|
|
Severity |
None |
|
Text |
|
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - APP interface failure |
|
Source |
Either server |
|
Frequency |
Every 2.5 minutes as long as condition exists |
|
Trap |
|
|
Trap ID |
17 |
|
Trap MIB Name |
appsInterfaceFailure |
Explanation
Database replication has failed.
Recovery
Contact the My Oracle Support (MOS).
Event Details
|
GUI Notification |
|
|
Severity |
Critical |
|
Text |
DB Repl Err - <dbReplErr> |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - DB repl error |
|
Source |
Both servers |
|
Frequency |
Every minute as long as condition exists. |
|
Trap |
|
|
Trap ID |
21 |
|
Trap MIB Name |
dataReplError |
Explanation
The database replication process monitor has failed.
Recovery
Contact the My Oracle Support (MOS).
Event Details
|
GUI Notification |
|
|
Severity |
Critical |
|
Text |
DB Proc Mon Err - <dbMonErr> |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - DB monitor failure |
|
Source |
Active server |
|
Frequency |
Every five minutes as long as condition exists. |
|
Trap |
|
|
Trap ID |
22 |
|
Trap MIB Name |
dbMonitorFail |
Explanation
The server has an internal disk error.
Recovery
Contact the My Oracle Support (MOS).
Event Details
|
GUI Notification |
|
|
Severity |
None |
|
Text |
|
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - Internal Disk Error |
|
Source |
Either server |
|
Frequency |
Within five minutes of the condition occurring and at five-minute intervals as long as condition exists |
|
Trap |
|
|
Trap ID |
23 |
|
Trap MIB Name |
internalDiskError |
Explanation
This notification indicates that LSMS database replication is delayed.
Recovery
No action required.
Event Details
|
GUI Notification |
|
|
Severity |
N/A |
|
Text |
DB Repl Info |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - DB repl info |
|
Source |
Either server |
|
Frequency |
Within five minutes of the condition occurring and every minute thereafter as long as condition exists. |
|
Trap |
|
|
Trap ID |
25 |
|
Trap MIB Name |
dataReplInfo |
Explanation
A process specified by <process_name> is utilizing 40 percent or more of the LSMS’s CPU resource and the <second_ID> indicates a specific instance of the process, as follows:
When the <process_name> is eagleagent, the <second_ID> specifies the Common Language Location Indicator (CLLI) of the network element
When the <process_name> is npacagent, the <second_ID> specifies the name of the region
When the <process_name> is not eagleagent or npacagent, the <second_ID> specifies the process ID (PID) of the process.
Recovery
Because this notification is posted every five minutes as long as the condition exists, you may choose to ignore this notification the first time that it appears. However, if this notification is repeated several times in a row, do one of the following:
If the <process_name> is not npacagent, go to step 4. Otherwise, determine whether the npacagent is still using 40% or more of the CPU resource by entering the following command, where <region> can be optionally specified (it is the name of the region as displayed at the end of the notification text):
$ ps -eo pid,pcpu,args | grep npacagent | grep <region>If the npacagent is still using 40% or more of the CPU resource, enter the following commands to stop the npacagent and restart it, where <region> is the name of the NPAC region whose npacagent is using 40% or more of the CPU resource:
$ cd $LSMS_DIR$ lsms stop <region>
$ lsms start <region>
Repeat step 1. If the npacagent you tried to stop is still using 40% or more of the CPU resource, contact the My Oracle Support (MOS).
If the <process_name> is not eagleagent, go to step 7. Otherwise, determine whether the eagleagent is still using 40% or more of the CPU resource by entering the following command, where <CLLI> can be optionally specified (it is the name of the network element as displayed at the end of the notification text):
$ ps -eo pid,pcpu,args | grep eagleagent | grep <CLLI>If the eagleagent is still using 40% or more of the CPU resource, enter the following commands to stop the eagleagent and restart it, where <CLLI> is the Common Language Location Indicator (CLLI) of the network element whose eagleagent is using 40% or more of the CPU resource:
$ cd $LSMS_DIR$ eagle stop <CLLI>
$ eagle start <region>
Repeat step 1. If the process you tried to stop is still using 40% or more of the CPU resource, contact the My Oracle Support (MOS).
If the <process_name> is not eagleagent or npacagent, contact the My Oracle Support (MOS).
Event Details
|
GUI Notification |
|
|
Severity |
Major |
|
Text |
Process [<process_name>-<second_ID>] Utilizing High Percentage of CPU |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - [<process_name>-<second_ID>] |
|
Source |
Either server |
|
Frequency |
Every five minutes as long as condition exists |
|
Trap |
|
|
Trap ID |
26 |
|
Trap MIB Name |
cpuUtilitzationOver39 |
Explanation
The LSMS server with default hostname lsmspri has been inhibited.
Recovery
As soon as possible, start the server by performing the procedure described in “Starting a Server”.
Event Details
|
GUI Notification |
|
|
Severity |
Major |
|
Text |
Primary Server Inhibited |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - Primary inhibited |
|
Source |
Server with default hostname lsmspri |
|
Frequency |
As soon as condition occurs, and at five-minute intervals as long as condition exists |
|
Trap |
|
|
Trap ID |
27 |
|
Trap MIB Name |
primaryServerInhibited |
Explanation
The LSMS server with default hostname lsmssec has been inhibited.
Recovery
As soon as possible, start the server by performing the procedure described in “Starting a Server”.
Event Details
|
GUI Notification |
|
|
Severity |
Major |
|
Text |
Secondary Server Inhibited |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - Secondary inhibited |
|
Source |
Server with default hostname lsmssec |
|
Frequency |
As soon as condition occurs, and at five-minute intervals as long as condition exists |
|
Trap |
|
|
Trap ID |
28 |
|
Trap MIB Name |
secondaryServerInhibited |
Explanation
A heartbeat link is down.
Recovery
Contact the My Oracle Support (MOS).
Event Details
|
GUI Notification |
|
|
Severity |
None |
|
Text |
|
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - Heartbeat failure |
|
Source |
Both servers |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
29 |
|
Trap MIB Name |
heartbeatLinkDown |
Explanation
The server’s swap space has exceeded the critical usage threshold (default = 95%).
Recovery
If the problem persists, contact the My Oracle Support (MOS).
Event Details
|
GUI Notification |
|
|
Severity |
Critical |
|
Text |
Swap space exceeds Critical |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - Swap space Critical |
|
Source |
Either server |
|
Frequency |
Every five minutes as long as condition exists |
|
Trap |
|
|
Trap ID |
39 |
|
Trap MIB Name |
swapSpaceCritical |
Explanation
The LSMS application or system daemon whose name has <process_name> as the first 12 characters is not running.
Recovery
No user action is necessary. The Surveillance process automatically restarts the Service Assurance process (sacw) and the sentryd process automatically restarts other processes.
Event Details
|
GUI Notification |
|
|
Severity |
None |
|
Text |
|
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - <process_name> failed |
|
Source |
Active server |
|
Frequency |
As soon as condition occurs, and at five-minute intervals as long as condition exists |
|
Trap |
|
|
Trap ID |
40 |
|
Trap MIB Name |
lsmsAppsNotRunning |
Explanation
The backup of the LSMS database has completed successfully.
Recovery
No action required; for information only.
Event Details
|
GUI Notification |
|
|
Severity |
None |
|
Text |
|
|
Surveillance Notification |
|
|
Text |
DATABASE backup complete |
|
Source |
Standby server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
41 |
|
Trap MIB Name |
backupCompleted |
Explanation
The backup of the LSMS database has failed.
Recovery
Review backup output to determine why backup failed, correct the problems, and run backup script again manually.
Event Details
|
GUI Notification |
|
|
Severity |
None |
|
Text |
|
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - DATABASE backup failed |
|
Source |
Standby server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
42 |
|
Trap MIB Name |
backupFailed |
Explanation
The primary LSMS server (Server 1A) is not providing the LSMS service.
Recovery
No action required; for information only.
Event Details
|
GUI Notification |
|
|
Severity |
None |
|
Text |
|
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - Primary not online |
|
Source |
Both primary and secondary servers |
|
Frequency |
Every five minutes as long as condition exists |
|
Trap |
|
|
Trap ID |
63 |
|
Trap MIB Name |
primaryServerNotOnline |
Explanation
The standby server is not prepared to take over LSMS service.
Recovery
Contact the My Oracle Support (MOS).
Event Details
|
GUI Notification |
|
|
Severity |
None |
|
Text |
|
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - Can't switch to standby |
|
Source |
Standby server |
|
Frequency |
Every five minutes as long as condition exists |
|
Trap |
|
|
Trap ID |
64 |
|
Trap MIB Name |
standbyNotReadyForSwitchover |
Explanation
The secondary LSMS server (Server 1B) is currently providing the LSMS service.
Recovery
No action required; for information only.
Event Details
|
GUI Notification |
|
|
Severity |
None |
|
Text |
|
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - Secondary online |
|
Source |
Both primary and secondary servers |
|
Frequency |
Every five minutes as long as condition exists |
|
Trap |
|
|
Trap ID |
65 |
|
Trap MIB Name |
secServerProvidingLSMSService |
Explanation
The standby LSMS server cannot determine the availability of the LSMS service on the active server.
Recovery
Determine if the other server is working normally. Also, verify that the heartbeat connections (eth2, eth3, and the serial cable) are connected and functioning properly
Event Details
|
GUI Notification |
|
|
Severity |
None |
|
Text |
|
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - Primary status unknown |
|
Source |
Standby server |
|
Frequency |
Every five minutes as long as condition exists |
|
Trap |
|
|
Trap ID |
66 |
|
Trap MIB Name |
secServerCannotDeterminePrimAvailability |
Explanation
The server’s swap space has exceeded the major usage threshold (default = 80%).
Recovery
If the problem persists, contact the My Oracle Support (MOS).
Event Details
|
GUI Notification |
|
|
Severity |
Major |
|
Text |
Swap Space Warning |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - Swap space warning |
|
Source |
Both servers |
|
Frequency |
Every five minutes as long as condition exists |
|
Trap |
|
|
Trap ID |
190 |
|
Trap MIB Name |
swapSpaceWarning |
Explanation
A database replication error that was reported earlier by the 4007 event has now been cleared.
Recovery
No action necessary.
Event Details
|
GUI Notification |
|
|
Severity |
Cleared |
|
Text |
Database Replication cleared - <dbReplErr> |
|
Surveillance Notification |
|
|
Text |
None |
|
Source |
|
|
Frequency |
|
|
Trap |
|
|
Trap ID |
195 |
|
Trap MIB Name |
dataReplClear |
Explanation
A database process monitor error that was reported earlier by the 4008 event has now been cleared.
Recovery
No action necessary.
Event Details
|
GUI Notification |
|
|
Severity |
Cleared |
|
Text |
Database Replication cleared - <dbMonErr> |
|
Surveillance Notification |
|
|
Text |
None |
|
Source |
|
|
Frequency |
|
|
Trap |
|
|
Trap ID |
196 |
|
Trap MIB Name |
dbMonitorCLear |
Explanation
The LSMS database failed count operation, which suggests a corrupt MySQL index.
Recovery
Contact the My Oracle Support (MOS).
Event Details
|
GUI Notification |
|
|
Severity |
Critical |
|
Text |
Database Corrupt Index |
|
Surveillance Notification |
|
|
Text |
None |
|
Source |
Both servers |
|
Frequency |
Every 30 minutes. |
|
Trap |
|
|
Trap ID |
200 |
|
Trap MIB Name |
dbCorruptIndex |
Explanation
The mate server is down.
Recovery
Contact the My Oracle Support (MOS).
Event Details
|
GUI Notification |
|
|
Severity |
Critical |
|
Text |
Mate Server Down |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - Mate Server Down |
|
Source |
Both servers |
|
Frequency |
Every minute as long as condition exists |
|
Trap |
|
|
Trap ID |
205 |
|
Trap MIB Name |
mateServerDown |
Explanation
The mate server is up.
Recovery
No action is required.
Event Details
|
GUI Notification |
|
|
Severity |
Cleared |
|
Text |
Mate Server Up |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - Mate Server Up |
|
Source |
Both servers |
|
Frequency |
As soon as condition clears |
|
Trap |
|
|
Trap ID |
206 |
|
Trap MIB Name |
mateServerUp |
Explanation
One or more platform alarms in the minor category exists. To determine which minor platform alarms are being reported, see “How to Decode Platform Alarms”. When the active server reports minor platform alarms that originated on the other server, the hostname of the other server is inserted before the alarm string.
Recovery
Contact the My Oracle Support (MOS).
Event Details
|
GUI Notification |
|
|
Severity |
Minor |
|
Text |
Minor Platform Alarm [hostname]: <alarm_string> |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - ALM <alarm_string> |
|
Source |
Both servers |
|
Frequency |
Every five minutes as long as condition exists |
|
Trap |
|
|
Trap ID |
191 |
|
Trap MIB Name |
minorPlatAlarmMask |
Explanation
All platform alarms in the minor category have been cleared. When the active server reports that all minor platform alarms have cleared on the other server, the hostname of the other server is inserted before the alarm string.
Recovery
No action necessary.
Event Details
|
GUI Notification |
|
|
Severity |
Cleared |
|
Text |
Minor Platform Alarms Cleared |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - Minor Plat alrms clear |
|
Source |
Both servers |
|
Frequency |
Every five minutes as long as condition exists |
|
Trap |
|
|
Trap ID |
197 |
|
Trap MIB Name |
minorPlatAlarmClear |
Explanation
One or more platform alarms in the major category exists. To determine which major platform alarms are being reported, see “How to Decode Platform Alarms”. When the active server reports major platform alarms that originated on the other server, the hostname of the other server is inserted before the alarm string.
Recovery
Contact the My Oracle Support (MOS).
Event Details
|
GUI Notification |
|
|
Severity |
Major |
|
Text |
Major Platform Alarm [hostname]: <alarm_string> |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - ALM <alarm_string> |
|
Source |
Both servers |
|
Frequency |
Every five minutes as long as condition exists |
|
Trap |
|
|
Trap ID |
192 |
|
Trap MIB Name |
majorPlatAlarmMask |
Explanation
All platform alarms in the major category have been cleared. When the active server reports that all major platform alarms have cleared on the other server, the hostname of the other server is inserted before the alarm string.
Recovery
No action necessary.
Event Details
|
GUI Notification |
|
|
Severity |
Cleared |
|
Text |
Major Platform Alarms Cleared |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - Major Plat alrms clear |
|
Source |
Both servers |
|
Frequency |
Once |
|
Trap |
|
|
Trap ID |
198 |
|
Trap MIB Name |
majorPlatAlarmClear |
Explanation
One or more platform alarms in the critical category exists. To determine which critical platform alarms are being reported, see “How to Decode Platform Alarms”. When the active server reports critical platform alarms that originated on the other server, the hostname of the other server is inserted before the alarm string.
Recovery
Contact the My Oracle Support (MOS).
Event Details
|
GUI Notification |
|
|
Severity |
Critical |
|
Text |
Critical Platform Alarm [hostname]: <alarm_string> |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - ALM <alarm_string> |
|
Source |
Both servers |
|
Frequency |
Once |
|
Trap |
|
|
Trap ID |
193 |
|
Trap MIB Name |
criticalPlatAlarmMask |
Explanation
All platform alarms in the major category have been cleared. When the active server reports that all major platform alarms have cleared on the other server, the hostname of the other server is inserted before the alarm string.
Recovery
No action necessary.
Event Details
|
GUI Notification |
|
|
Severity |
Cleared |
|
Text |
Critical Platform Alarms Cleared |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - Crit Plat alrms clear |
|
Source |
Both servers |
|
Frequency |
Once |
|
Trap |
|
|
Trap ID |
199 |
|
Trap MIB Name |
criticalPlatAlarmClear |
Explanation
The eagleagent process has been started.
Recovery
No action required; for information only.
Event Details
|
GUI Notification |
|
|
Severity |
Cleared |
|
Text |
Eagleagent <CLLI> Has Been Started |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - <CLLI> started |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
1 |
|
Trap MIB Name |
eagleAgentStarted |
Explanation
The eagleagent process has been stopped by the eagle script.
Recovery
No action required; for information only.
Event Details
|
GUI Notification |
|
|
Severity |
Critical |
|
Text |
Eagleagent <CLLI> Has Been Stopped by User |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - <CLLI> norm exit |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
2 |
|
Trap MIB Name |
eagleAgentStoppedbyscript |
Explanation
The npacagent for the region indicated by <NPAC_region_ID> has been started.
Recovery
No action required; for information only.
Event Details
|
GUI Notification |
|
|
Severity |
Cleared |
|
Text |
NPACagent Has Been Started |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - <NPAC_region_ID> NPACagent started |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
3 |
|
Trap MIB Name |
NPACAgentStarted |
Explanation
The npacagent for the region indicated by <region> has been stopped using the lsms command.
Recovery
No action required; for information only. If you desire to restart the agent, do the following:
Log in to the active server as lsmsadm.
Enter the following commands to start the npacagent where <region> is the name of the NPAC region:
$ cd $LSMS_DIR$ lsms start <region>
Event Details
|
GUI Notification |
|
|
Severity |
Critical |
|
Text |
NPACAgent Has Been Stopped by User |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - <NPAC_region_ID> norm exit |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
4 |
|
Trap MIB Name |
lsmsCommandStoppedNPACAgent |
Explanation
The eagleagent process for the network element identified by <CLLI> has failed. The sentryd process will attempt to restart.
Recovery
No action required; the sentryd process will attempt to restart the eagleagent process.
Event Details
|
GUI Notification |
|
|
Severity |
Critical |
|
Text |
Eagleagent [<CLLI>] Has Failed |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - FAILD: <CLLI> |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
74 |
|
Trap MIB Name |
lsmsEagleAgentFailed |
Explanation
The eagleagent process for the network element identified by <CLLI> has been successfully restarted by the sentryd process.
Recovery
No action required.
Event Details
|
GUI Notification |
|
|
Severity |
None |
|
Text |
|
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - RECOV: <CLLI> |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
75 |
|
Trap MIB Name |
lsmsEagleAgentRestarted |
Explanation
The sentryd process was unable to restart the eagleagent process for the network element identified by <CLLI>.
Recovery
Contact the My Oracle Support (MOS).
Event Details
|
GUI Notification |
|
|
Severity |
Critical |
|
Text |
Failure Restarting Eagleagent [<CLLI>] |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - RFAILD: <CLLI> |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
76 |
|
Trap MIB Name |
failureToRestartEagleAgent |
Explanation
The npacagent process for the region specified by <NPAC_region_ID> has failed. The sentryd process will attempt to restart.
Recovery
No action required; the sentryd process will attempt to restart the npacagent process.
Event Details
|
GUI Notification |
|
|
Severity |
Critical |
|
Text |
NPACagent [<NPAC_region_ID>] Failure |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - FAILD: <NPAC_region_ID> agent |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
78 |
|
Trap MIB Name |
NPACagentForRegionFailure |
Explanation
The npacagent process for the region specified by <NPAC_region_ID> has been successfully restarted by the sentryd process.
Recovery
No action required. Any active LSMS GUI processes will automatically reconnect.
Event Details
|
GUI Notification |
|
|
Severity |
None |
|
Text |
|
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - RECOV: <NPAC_region_ID> agent |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
79 |
|
Trap MIB Name |
NPACagentForRegionRestarted |
Explanation
The sentryd process was unable to restart the npacagent process for the region specified by <NPAC_region_ID>.
Recovery
Contact the My Oracle Support (MOS).
Event Details
|
GUI Notification |
|
|
Severity |
Critical |
|
Text |
Failure Restarting NPACagent [<NPAC_region_ID>] |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - RFAILD: <NPAC_region_ID> agent |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
80 |
|
Trap MIB Name |
failureToRestartNPACagentRegion |
Explanation
The npacagent process has been stopped due to a fault in accessing the regional database.
Recovery
A database error has occurred. Contact the My Oracle Support (MOS).
Event Details
|
GUI Notification |
|
|
Severity |
Critical |
|
Text |
NPACagent Has Been Shut Down - Database Access Error |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - <NPAC_region_ID> DB error |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
189 |
|
Trap MIB Name |
NPACagentStopRegDBaccessFault |
Explanation
The LSMS Surveillance feature is in operation.
Recovery
No action required; for information only.
Event Details
|
GUI Notification |
|
|
Severity |
None |
|
Text |
|
|
Surveillance Notification |
|
|
Text |
Keep alive |
|
Source |
Both primary and secondary servers |
|
Frequency |
Every five minutes as long as condition exists |
|
Trap |
|
|
Trap ID |
19 |
|
Trap MIB Name |
survFeatureOn |
Explanation
The network element resynchronization database contains more than 1 million entries.
Recovery
Each day, as part of a cron job, the LSMS trims the resynchronization database so that it contains 768,000 entries. The occurrence of this event means that more than 232,000 transactions have been received since the last cron job. If this event occurs early in the day, contact the My Oracle Support (MOS).
Event Details
|
GUI Notification |
|
|
Severity |
Major |
|
Text |
ResyncDB Contains 1 Mil Entries |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - ResyncDB 1 Mil |
|
Source |
Active server |
|
Frequency |
Once |
|
Trap |
|
|
Trap ID |
34 |
|
Trap MIB Name |
resynchLogMidFull |
Explanation
The pending queue, used to hold the transactions to send to the network element (which is indicated in the System field on the GUI or whose CLLI has the value that replaces <CLLI> in the Surveillance notification text), is over half full.
Recovery
No recovery is required. Informational only.
Event Details
|
GUI Notification |
|
|
Severity |
Major |
|
Text |
EMS Pending Queue Is Half full |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - CLLI=<CLLI> |
|
Source |
Active server |
|
Frequency |
As soon as condition occurs, and at five-minute intervals as long as condition exists |
|
Trap |
|
|
Trap ID |
43 |
|
Trap MIB Name |
ensPendingQueueHalfFull |
Explanation
The pending queue, used to hold the transactions to send to the network element (which is indicated in the System field on the GUI or whose CLLI has the value that replaces <CLLI> in the Surveillance notification text), is completely full. The association to that EMS will be broken.
Recovery
No manual recovery required. The LSMS will automatically re-establish the association to the EMS and synchronization will take place.
Event Details
|
GUI Notification |
|
|
Severity |
Critical |
|
Text |
EMS Pending Queue Is Full |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - CLLI=<CLLI> |
|
Source |
Active server |
|
Frequency |
As soon as condition occurs, and at five-minute intervals as long as condition exists |
|
Trap |
|
|
Trap ID |
44 |
|
Trap MIB Name |
emsPendingQueueMaxReached |
Explanation
There was a data error in a record that prevented the LSMS eagleagent from sending the record to the network element.
Recovery
Both the error and the ignored record are written to the file /var/TKLC/lsms/logs/trace/LsmsTrace.log.<mmdd>, where <mmdd> indicates the month and day the error occurred. Examine the log file for the month and day this error was reported to determine what the error was. Enter the data manually or send it again.
Event Details
|
GUI Notification |
|
|
Severity |
Minor |
|
Text |
Eagleagent <CLLI> Ignoring Record: <DataError> |
|
Surveillance Notification |
|
|
Text |
None |
|
Source |
|
|
Frequency |
|
|
Trap |
|
|
Trap ID |
84 |
|
Trap MIB Name |
eagleAgentIgnoredRecord |
Explanation
The Service Assurance agent has started successfully.
Recovery
No action required; for information only.
Event Details
|
GUI Notification |
|
|
Severity |
None |
|
Text |
|
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
67 |
|
Trap MIB Name |
serviceAssuranceAgentStarted |
Explanation
Association with the Service Assurance Manager, identified by <Service_Assurance_Manager_Name>, has been established successfully.
Recovery
No action required; for information only.
Event Details
|
GUI Notification |
|
|
Severity |
None |
|
Text |
|
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - <Service_Assurance_Manager_Name> |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
68 |
|
Trap MIB Name |
establishServAssuranceMgrAssoc |
Explanation
Association with the Service Assurance Manager, identified by <Service_Assurance_Manager_Name>, has been stopped or disconnected.
Recovery
Contact the Service Assurance system administrator to determine the cause of disconnection, then have Service Assurance system administrator reassociate the Service Assurance Manager to the Service Assurance Agent.
Event Details
|
GUI Notification |
|
|
Severity |
None |
|
Text |
|
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - <Service_Assurance_Manager_Name> |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
69 |
|
Trap MIB Name |
servAssuranceMgrAssocBroken |
Explanation
The Service Assurance agent is not currently running.
Recovery
No action required; the Service Assurance agent should be restarted automatically.
Event Details
|
GUI Notification |
|
|
Severity |
None |
|
Text |
|
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
70 |
|
Trap MIB Name |
servAssuranceAgentNotRunning |
Explanation
The OSI process has failed. The sentryd process will attempt to restart.
Recovery
No action required; the sentryd process will attempt to restart the failed process.
Event Details
|
GUI Notification |
|
|
Severity |
None |
|
Text |
|
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - FAILD: OSI |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
88 |
|
Trap MIB Name |
osiDaemonFailure |
Explanation
The OSI process has been successfully restarted by the sentryd process.
Recovery
No action required. The sentryd process will attempt to restart the npacagent processes for all active regions. Any active LSMS GUI processes will automatically reconnect.
Event Details
|
GUI Notification |
|
|
Severity |
None |
|
Text |
|
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - RECOV: OSI |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
89 |
|
Trap MIB Name |
osiDaemonRestarted |
Explanation
The sentryd process was not able to restart the OSI process.
Recovery
Contact the My Oracle Support (MOS).
Event Details
|
GUI Notification |
|
|
Severity |
None |
|
Text |
|
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - RFAILD: OSI |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
90 |
|
Trap MIB Name |
osiDaemonRestartFailure |
Explanation
The Surveillance feature has detected that the sentryd process is no longer running.
Recovery
No action required; the LSMS HA software will attempt to restart the sentryd process.
Event Details
|
GUI Notification |
|
|
Severity |
None |
|
Text |
|
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - FAILD: sentryd |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
91 |
|
Trap MIB Name |
sentrydFailure |
Explanation
The EMS/NE has rejected the NPANXX GTT creation, deletion, or modification transaction, and the NPANXX value in the transaction could not be determined.
Recovery
Look in the transaction log file, /var/TKLC/lsms/logs/<CLLI>/LsmsTrans.log.MMDD, and locate the NE’s response to the NPANXX GTT command to determine why the command failed. Re-enter the NPANXX GTT data correctly, which will cause the LSMS to try to command again.
Event Details
|
GUI Notification |
|
|
Severity |
Major |
|
Text |
<CLLI>: NPANXX GTT <type_of_operation> Failed |
|
Surveillance Notification |
|
|
Text |
None |
|
Source |
|
|
Frequency |
|
|
Trap |
|
|
Trap ID |
126 |
|
Trap MIB Name |
npanxxGTTValueNotFound |
Explanation
The EMS/NE has rejected the NPANXX GTT creation, deletion, or modification transaction for the specified NPANXX value.
Recovery
Look in the transaction log file, /var/TKLC/lsms/logs/<CLLI>/LsmsTrans.log.MMDD, and locate the NE’s response to the NPANXX GTT command to determine why the command failed. Re-enter the NPANXX GTT data correctly, which will cause the LSMS to try to command again.
Event Details
|
GUI Notification |
|
|
Severity |
Major |
|
Text |
<CLLI>: NPANXX GTT <type_of_operation> Failed for NPANXX <NPANXX_value> |
|
Surveillance Notification |
|
|
Text |
None |
|
Source |
|
|
Frequency |
|
|
Trap |
|
|
Trap ID |
127 |
|
Trap MIB Name |
npanxxGTTValueRejected |
Explanation
The EMS/NE has rejected the Override GTT creation, deletion, or modification transaction, and the LRN value in the transaction could not be determined.
Recovery
Look in the transaction log file, /var/TKLC/lsms/logs/<CLLI>/LsmsTrans.log.MMDD, and locate the NE’s response to the Override GTT command to determine why the command failed. Re-enter the Override GTT data correctly, which will cause the LSMS to try to command again.
Event Details
|
GUI Notification |
|
|
Severity |
Major |
|
Text |
<CLLI>: Override GTT <type_of_operation> Failed |
|
Surveillance Notification |
|
|
Text |
None |
|
Source |
|
|
Frequency |
|
|
Trap |
|
|
Trap ID |
128 |
|
Trap MIB Name |
overrideGTTValueNotFound |
Explanation
The EMS/NE has rejected the Override GTT creation, deletion, or modification transaction for the specified LRN value.
Recovery
Look in the transaction log file, /var/TKLC/lsms/logs/<CLLI>/LsmsTrans.log.MMDD, and locate the NE’s response to the Override GTT command to determine why the command failed. Re-enter the Override GTT data correctly, which will cause the LSMS to try to command again.
Event Details
|
GUI Notification |
|
|
Severity |
Major |
|
Text |
<CLLI>: Override GTT <type_of_operation> Failed for LRN <LRN_value> |
|
Surveillance Notification |
|
|
Text |
None |
|
Source |
|
|
Frequency |
|
|
Trap |
|
|
Trap ID |
129 |
|
Trap MIB Name |
overrideGTTValueRejected |
Explanation
The LSMS was not able to complete the automatic synchronization with the EMS/NE. Possible reasons include:
The network failed temporarily but not long enough to cause the association with the EMS to fail.
The EMS/NE rejected the data because it is busy updating its databases.
Recovery
Verify the connection between the LSMS and the EMS; then reinitialize the MPS. If this notification appears again, perform one of the bulk download procedures in the LNP Database Synchronization User's Guide.
Event Details
|
GUI Notification |
|
|
Severity |
Major |
|
Text |
Short Synchronization Failed |
|
Surveillance Notification |
|
|
Text |
None |
|
Source |
|
|
Frequency |
|
|
Trap |
|
|
Trap ID |
131 |
|
Trap MIB Name |
unableToCompleteAutoResynch |
Explanation
The LSMS has started its automatic synchronization with the EMS/NE.
Recovery
No action required; for information only.
Event Details
|
GUI Notification |
|
|
Severity |
Major |
|
Text |
Short Synchronization Started |
|
Surveillance Notification |
|
|
Text |
None |
|
Source |
|
|
Frequency |
|
|
Trap |
|
|
Trap ID |
132 |
|
Trap MIB Name |
autoResynchNEStarted |
Explanation
The automatic resynchronization of databases after an outage between the LSMS and the NPAC has completed successfully.
Recovery
No action required; for information only.
Event Details
|
GUI Notification |
|
|
Severity |
Cleared |
|
Text |
Recovery Complete |
|
Surveillance Notification |
|
|
Text |
None |
|
Source |
|
|
Frequency |
|
|
Trap |
|
|
Trap ID |
133 |
|
Trap MIB Name |
dbResynchCompleted |
Explanation
The LSMS has completed its automatic synchronization with the EMS/NE.
Recovery
No action required; for information only.
Event Details
|
GUI Notification |
|
|
Severity |
Cleared |
|
Text |
Short Synchronization Complete |
|
Surveillance Notification |
|
|
Text |
None |
|
Source |
|
|
Frequency |
|
|
Trap |
|
|
Trap ID |
138 |
|
Trap MIB Name |
emsShortSynchCompleted |
Explanation
The EMS pending queue used to hold the transactions to send to the EMS/NE identified by <CLLI> in the Survellance notification, has fallen sufficiently below the halfway full point.
Recovery
No action required; for information only.
Event Details
|
GUI Notification |
|
|
Severity |
Cleared |
|
Text |
EMS Pending Queue Less Than Half Full |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - CLLI=<CLLI> |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
141 |
|
Trap MIB Name |
pendingQueueHalfFull |
Explanation
The EMS pending queue used to hold the transactions to send to the EMS/NE identified by <CLLI> in the Survellance notification, has fallen sufficiently below the full point.
Recovery
No action required; for information only.
Event Details
|
GUI Notification |
|
|
Severity |
Cleared |
|
Text |
EMS Pending Queue No Longer Full |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - CLLI=<CLLI> |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
142 |
|
Trap MIB Name |
pendingQueueNotFull |
Explanation
The specified NPA-NXX is opened for portability starting at the value of the <EffectiveTimestamp> field.
Recovery
No action required; for information only.
Event Details
|
GUI Notification |
|
|
Severity |
Event |
|
Text |
New NPA-NXX: SPID [<SPID>], NPANXX [<NPANXX>], TS [<EffectiveTimestamp>] |
|
Surveillance Notification |
|
|
Text |
None |
|
Source |
|
|
Frequency |
|
|
Trap |
|
|
Trap ID |
145 |
|
Trap MIB Name |
npaNxxOpenedForPortabilityAtTS |
Explanation
The first telephone number in the specified NPA-NXX is ported starting at the value of the <EffectiveTimestamp> field.
Recovery
No action required; for information only.
Event Details
|
GUI Notification |
|
|
Severity |
Event |
|
Text |
First use of NPA-NXX: SPID [<SPID>], NPANXX [<NPANXX>], TS [<EffectiveTimestamp>] |
|
Surveillance Notification |
|
|
Text |
None |
|
Source |
|
|
Frequency |
|
|
Trap |
|
|
Trap ID |
146 |
|
Trap MIB Name |
npaNxxPortedAtTS |
Explanation
An audit of the network element identified by <CLLI> has begun.
Recovery
No action required; for information only.
Event Details
|
GUI Notification |
|
|
Severity |
Cleared |
|
Text |
Audit LNP DB Synchronization Started |
|
Surveillance Notification |
|
|
Text |
NE <CLLI> Audit started |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
147 |
|
Trap MIB Name |
ebdaAuditActive |
Explanation
An audit of the network element identified by <CLLI> has completed successfully.
Recovery
No action required; for information only.
Event Details
|
GUI Notification |
|
|
Severity |
Cleared |
|
Text |
Audit LNP DB Synchronization Completed |
|
Surveillance Notification |
|
|
Text |
NE <CLLI> Audit completed |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
148 |
|
Trap MIB Name |
ebdaAuditSuccess |
Explanation
An audit of the network element identified by <CLLI> has failed.
Recovery
Inspect the log file /var/TKLC/lsms/logs/<CLLI>/LsmsTrans.log.MMDD for details as to the cause of the error. After clearing the cause of the error, start the audit again.
Event Details
|
GUI Notification |
|
|
Severity |
Critical |
|
Text |
Audit LNP DB Synchronization Failed |
|
Surveillance Notification |
|
|
Text |
NE <CLLI> Audit failed |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
149 |
|
Trap MIB Name |
ebdaAuditFailure |
Explanation
The user aborted an audit of the network element identified by <CLLI> before it had completed.
Recovery
No action required; for information only.
Event Details
|
GUI Notification |
|
|
Severity |
Cleared |
|
Text |
Audit LNP DB Synchronization Aborted |
|
Surveillance Notification |
|
|
Text |
NE <CLLI> Audit aborted |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
150 |
|
Trap MIB Name |
ebdaAuditAbortedByUser |
Explanation
A reconcile has started at the completion of an audit.
Recovery
No action required; for information only.
Event Details
|
GUI Notification |
|
|
Severity |
Cleared |
|
Text |
Reconcile LNP DB Synchronization Started |
|
Surveillance Notification |
|
|
Text |
NE <CLLI> Reconcile started |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
151 |
|
Trap MIB Name |
ebdaReconcileActive |
Explanation
A reconcile, which was performed at the end of an audit, has completed.
Recovery
No action required; for information only.
Event Details
|
GUI Notification |
|
|
Severity |
Cleared |
|
Text |
Reconcile LNP DB Synchronization Complete |
|
Surveillance Notification |
|
|
Text |
NE <CLLI> Reconcile completed |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
152 |
|
Trap MIB Name |
ebdaReconcileSuccess |
Explanation
A reconcile, which was performed at the end of an audit, has failed before it completed.
Recovery
Inspect the log file /var/TKLC/lsms/logs/<CLLI>/LsmsAudit.log.MMDD for details as to the cause of the error. After clearing the cause of the error, start the reconcile again.
Event Details
|
GUI Notification |
|
|
Severity |
Critical |
|
Text |
Reconcile LNP DB Synchronization Failed |
|
Surveillance Notification |
|
|
Text |
NE <CLLI> Reconcile failed |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
153 |
|
Trap MIB Name |
ebdaReconcileFailure |
Explanation
The user has stopped a reconcile before it completed.
Recovery
No action required; for information only.
Event Details
|
GUI Notification |
|
|
Severity |
Cleared |
|
Text |
Reconcile LNP DB Synchronization Aborted |
|
Surveillance Notification |
|
|
Text |
NE <CLLI> Reconcile aborted |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
154 |
|
Trap MIB Name |
ebdaReconcileAbortedByUser |
Explanation
A bulk download is currently running.
Recovery
No action required; for information only.
Event Details
|
GUI Notification |
|
|
Severity |
Cleared |
|
Text |
Bulk Load LNP DB Synchronization Started |
|
Surveillance Notification |
|
|
Text |
NE <CLLI> Bulk load started |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
159 |
|
Trap MIB Name |
ebdaBulkLoadActive |
Explanation
A bulk download has completed successfully.
Recovery
No action required; for information only.
Event Details
|
GUI Notification |
|
|
Severity |
Cleared |
|
Text |
Bulk Load LNP DB Synchronization Complete |
|
Surveillance Notification |
|
|
Text |
NE <CLLI> Bulk load completed |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
160 |
|
Trap MIB Name |
ebdaBulkLoadSuccess |
Explanation
A bulk download has failed before it completed.
Recovery
Inspect the log file /var/TKLC/lsms/logs/<CLLI>/LsmsBulkLoad.log.MMDD for details as to the cause of the error. After clearing the cause of the error, start the bulk download again.
Event Details
|
GUI Notification |
|
|
Severity |
Critical |
|
Text |
Bulk Load LNP DB Synchronization Failed |
|
Surveillance Notification |
|
|
Text |
NE <CLLI> Bulk load failed |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
161 |
|
Trap MIB Name |
ebdaBulkLoadFailure |
Explanation
The user has stopped a bulk download before it completed.
Recovery
No action required; for information only.
Event Details
|
GUI Notification |
|
|
Severity |
Cleared |
|
Text |
Bulk Load LNP DB Synchronization Aborted |
|
Surveillance Notification |
|
|
Text |
NE <CLLI> Bulk load aborted |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
162 |
|
Trap MIB Name |
ebdaBulkLoadAbortedByUser |
Explanation
A user-initiated resynchronization is currently running.
Recovery
No action required; for information only.
Event Details
|
GUI Notification |
|
|
Severity |
Cleared |
|
Text |
Re-sync LNP DB Synchronization Started |
|
Surveillance Notification |
|
|
Text |
NE <CLLI> Re-sync started |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
163 |
|
Trap MIB Name |
ebdaResyncActive |
Explanation
A user-initiated resynchronization has completed successfully.
Recovery
No action required; for information only.
Event Details
|
GUI Notification |
|
|
Severity |
Cleared |
|
Text |
Re-sync LNP DB Synchronization Complete |
|
Surveillance Notification |
|
|
Text |
NE <CLLI> Re-sync completed |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
164 |
|
Trap MIB Name |
ebdaResyncSuccess |
Explanation
A user-initiated resynchronization has failed before it completed.
Recovery
Inspect the contents of the file /var/TKLC/lsms/logs/<CLLI>/LsmsResync.log.MMDD to determine the cause of the error. After clearing the cause of the error, start the user-initiated resynchronization again.
Event Details
|
GUI Notification |
|
|
Severity |
Critical |
|
Text |
Re-sync LNP DB Synchronization Failed |
|
Surveillance Notification |
|
|
Text |
NE <CLLI> Re-sync failed |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
165 |
|
Trap MIB Name |
ebdaResyncFailure |
Explanation
The user has stopped a user-initiated resynchronization before it completed.
Recovery
No action required; for information only.
Event Details
|
GUI Notification |
|
|
Severity |
Cleared |
|
Text |
Re-sync LNP DB Synchronization Aborted |
|
Surveillance Notification |
|
|
Text |
NE <CLLI> Re-sync aborted |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
166 |
|
Trap MIB Name |
ebdaResyncAbortedByUser |
Explanation
A scheduled file transfer has failed.
Recovery
Inspect the error log file/var/TKLC/lsms/logs/aft/aft.log.MMDD for details as to the cause of the error.
Event Details
|
GUI Notification |
|
|
Severity |
Major |
|
Text |
Automatic File Transfer Failure - See Log for Details |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin- Auto xfer Failure |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
171 |
|
Trap MIB Name |
automaticFileTransferFeatureFailure |
Explanation
An NPA-NXX split activation completed successfully.
Recovery
No action required; for information only.
Event Details
|
GUI Notification |
|
|
Severity |
Cleared |
|
Text |
Activate Split Successful OldNPA=<old_NPA> NewNPA=<new_NPA> NXX=<NXX> |
|
Surveillance Notification |
|
|
Text |
None |
|
Source |
|
|
Frequency |
|
|
Trap |
|
|
Trap ID |
10 |
|
Trap MIB Name |
npaSplitActOk |
Explanation
An NPA-NXX split activation failed.
Recovery
Perform and audit and reconcile of NPA Split information at the network element.
Event Details
|
GUI Notification |
|
|
Severity |
Critical |
|
Text |
Activate Split Failed OldNPA=<old_NPA> NewNPA=<new_NPA> NXX=<NXX> |
|
Surveillance Notification |
|
|
Text |
None |
|
Source |
|
|
Frequency |
|
|
Trap |
|
|
Trap ID |
172 |
|
Trap MIB Name |
npaSplitActFailed |
Explanation
At least one active NPA-NXX split is past its end date and needs to be deleted.
Recovery
Do the following:
View all split objects (for information, refer to the Database Administrator's Guide) to determine which objects have end dates that have already passed.
Delete the objects whose end dates have passed (for information, refer to the Database Administrator's Guide).
Event Details
|
GUI Notification |
|
|
Severity |
Major |
|
Text |
Active Splits Are Past Their End Dates |
|
Surveillance Notification |
|
|
Text |
None |
|
Source |
|
|
Frequency |
|
|
Trap |
|
|
Trap ID |
173 |
|
Trap MIB Name |
activeSplitsPastEndDates |
Explanation
The EMS/NE has rejected the NPANXX Split operation indicated by <operation>, and the NPANXX value in the transaction could not be determined.
Recovery
Look in the transaction log file, /var/TKLC/lsms/logs/<CLLI>/LsmsTrans.log.MMDD, and locate the NE’s response to the NPANXX Split command to determine why the command failed. Delete and re-enter the NPANXX Split data correctly, which will cause the LSMS to try to command again.
Event Details
|
GUI Notification |
|
|
Severity |
Major |
|
Text |
<CLLI>: NPANXX Split <operation> Failed |
|
Surveillance Notification |
|
|
Text |
None |
|
Source |
|
|
Frequency |
|
|
Trap |
|
|
Trap ID |
178 |
|
Trap MIB Name |
EmsNeRejNpaNxxSplitNotDetermined |
Explanation
The EMS/NE has rejected the NPANXX Split operation indicated by <operation> for the indicated NPANXX value.
Recovery
Look in the transaction log file, /var/TKLC/lsms/logs/<CLLI>/LsmsTrans.log.MMDD, and locate the NE’s response to the NPANXX Split command to determine why the command failed. Delete and re-enter the NPANXX Split data correctly, which will cause the LSMS to try to command again.
Event Details
|
GUI Notification |
|
|
Severity |
Major |
|
Text |
<CLLI>: NPANXX Split <operation> Failed for New NPANXX <NPANXX> |
|
Surveillance Notification |
|
|
Text |
None |
|
Source |
|
|
Frequency |
|
|
Trap |
|
|
Trap ID |
179 |
|
Trap MIB Name |
EmsNeRejectedNpaNxxSplit |
Explanation
The LSMS is not able to confirm the physical connectivity with the directly connected query server identified by <hostname>. The problem may be one of the following:
Physical connectivity issues between the LSMS and directly connected Query Server.
The query server host name is not associated with the appropriate Internet Protocol (IP) address in /etc/hosts file.
The Internet Protocol (IP) address specified for the special replication user for the for the query server is incorrect.
The proper TCP/IP ports are not open in the firewall(s) between the LSMS and the query servers.
Recovery
Check the physical connectivity of the LSMS to the query server.
Check that the query server hosts name is associated with corresponding Internet Protocol (IP) addresses in /etc/hosts file.
Verify that the IP address for the query server is correct. Display the IP address of all configured query servers by using the $LSMS_TOOLS_DIR/lsmsdb -c queryservers command.
Verify that the firewall TCP/IP port configuration is set correctly for both the LSMS and query servers directly connected to the LSMS (refer to Appendix A, “Configuring the Query Server,” of the Configuration Guide for information about port configuration for firewall protocol filtering).
Event Details
|
GUI Notification |
|
|
Severity |
Major |
|
Text |
Query Server <hostname> Physical Connection Lost |
|
Surveillance Notification |
|
|
Text |
Query Server=<hostname> Physical Conn Lost |
|
Source |
Active Server |
|
Frequency |
As soon as condition occurs, and at five-minute intervals as long as condition exists |
|
SNMP Trap |
|
|
Trap ID |
180 |
|
Trap MIB Name |
physicalConnectivityWithQueryServerLost |
Explanation
The query server identified by <hostname> does not have a replication connection established with the LSMS. The problem may be one of the following:
Query server cannot establish a connection with the master.
Query server not properly configured to connect to the master.
A query that succeeded on the master failed on the query server.
The binary log(s) that are needed by the query server to resynchronize itself to its master no longer exist.
Data on the query server does not agree with what is on the master when the binary log was started.
Replication was stopped at the query server by a user.
Recovery
At the query server, perform the following substeps:
Start the MySQL command line utility on the slave server:
# cd /opt/mysql/mysql/bin# mysql -u root -p
Enter password:<Query Server/s MySql root user password>
Determine whether the query server is running by entering the following command and looking at the Slave_IO_Running and Slave_SQL_Running column values.
mysql> SHOW SLAVE STATUS \G;If the Slave_IO_Running and Slave_SQL_Running column values show that the slave is not running, verify the query server's /usr/mysql1/my.cnf option file (refer to “MySQL Replication Configuration for Query Servers,” in Appendix A, “Configuring the Query Server,” of the Configuration Guide) and check the error log (/usr/mysql1/<hostname>.err) for messages.
If the Slave_IO_Running and Slave_SQL_Running column values show that the slave (query server) is running, enter the following command to verify whether the slave established a connection with the master (LSMS or another query server acting as a master/slave).
mysql> SHOW PROCESSLIST;
Find the thread with the system user value in the User column and none in the Host column, and check the State column. If the State column says “connecting to master,” verify that the master hostname is correct, that the DNS is properly set up, whether the master is actually running, and whether it is reachable from the slave (refer to Appendix A, “Configuring the Query Server,” of the Configuration Guide for information about port configuration for firewall protocol filtering if the master and slave are connecting through a firewall).
If the slave was running, but then stopped, enter the following command:
mysql> SHOW SLAVE STATUS;
Look at the output. This error can happen when some query that succeeded on the master fails on the slave, but this situation should never happen while the replication is active if you have taken a proper snapshot of the master and never modify the data on the slave outside of the slave thread.
However, if this is not the case, or if the failed items are not needed and there are only a few of them, try the following:
First see if there is some stray record in the way on the query server. Understand how it got there, then delete it from the query server database and run start slave.
If the above does not work or does not apply, try to understand if it would be safe to make the update manually (if needed) and then ignore the next query from the LSMS.
If you have decided you can skip the next query, enter one of the following command sequences:
To skip a query that uses AUTO_INCREMENT or LAST_INSERT_ID(), enter:
mysql> SET GLOBAL SQL_SLAVE_SKIP_COUNTER=2;mysql> start slave;
Queries that use AUTO_INCREMENT or LAST_INSERT_ID() take two events in the binary log of the master.
Otherwise, enter:
mysql> SET GLOBAL SQL_SLAVE_SKIP_COUNTER=1;mysql> start slave;
If you are sure the query server database started out perfectly in sync with the LSMS database, and no one has updated the tables involved outside of the slave thread, contact the My Oracle Support (MOS) so you will not have to do the above steps again.
If all else fails, read the error log, /usr/mysql/<hostname>.err. If the log is big, run the following command on the slave:
grep -i slave /usr/mysql1/<hostname>.err
(There is no generic pattern to search for on the master, as the only errors it logs are general system errors. If it can, the master will send the error to the slave when things go wrong.)
If the error log on the slave conveys that it could not find a binary log file, this indicates that the binary log files on the master have been removed (purged). Binary logs are periodically purged from the master to prevent them from growing unbounded and consuming large amounts of disk resources. However, if a query server was not replicating and one of the binary log files it wants to read is purged, it will be unable to replicate once it comes up. If this occurs, the query server is required to be reset with another snapshot of data from the master or another query server (see “Reload a Query Server Database from the LSMS” and “Reload a Query Server Database from Another Query Server”).
When you have determined that there is no user error involved, and replication still either does not work at all or is unstable, please contact the My Oracle Support (MOS).
Event Details
|
GUI Notification |
|
|
Severity |
Major |
|
Text |
Query Server <hostname> Replication Connection Lost |
|
Surveillance Notification |
|
|
Text |
Query Server=<hostname> Replication Conn Lost |
|
Source |
Active Server |
|
Frequency |
As soon as condition occurs, and at five-minute intervals as long as condition exists |
|
SNMP Trap |
|
|
Trap ID |
181 |
|
Trap MIB Name |
queryServerConnectionWithLsmsLost |
Explanation
The SV/NPB storage database has exceeded the configured percent usage threshhold.
Recovery
Contact the My Oracle Support (MOS).
Event Details
|
GUI Notification |
|
|
Severity |
Event |
|
Text |
SV/NPB Storage Exceeds <%> percent |
|
Surveillance Notification |
|
|
Text |
Notify:Sys Admin - SV/NPB threshold % |
|
Source |
Both servers |
|
Frequency |
Every 5 minutes after condition occurs |
|
Trap |
|
|
Trap ID |
194 |
|
Trap MIB Name |
svNpbPercentUsage |
Explanation
This event indicates that the SV/NPB storage database usage is below the configured percent usage threshold.
Recovery
No action is required
Event Details
|
GUI Notification |
|
|
Severity |
Cleared |
|
Text |
SV/NPB storage falls below <%> percent |
|
Surveillance Notification |
|
|
Text |
Notify: Sys Admin - SV/NPB cleared |
|
Source |
Both servers |
|
Frequency |
As soon as condition clears |
|
Trap |
|
|
Trap ID |
207 |
|
Trap MIB Name |
svNpbBelowLimit |
Explanation
The event number present in the untilClear filter list is cleared. The event number is removed from the untilClear filter list.
Recovery
No action is required.
Event Details
|
GUI Notification |
|
|
Severity |
Event |
|
Text |
<Event number> in the untilClear filter list, event clear received at <%s> |
|
Surveillance Notification |
|
|
Text |
None |
|
Source |
|
|
Frequency |
|
|
Trap |
|
|
Trap ID |
None |
|
Trap MIB Name |
|
Explanation
The alarm filter counter has reached its limit; the counter will start again from one.
Recovery
No action is required.
Event Details
|
GUI Notification |
|
|
Severity |
Event |
|
Text |
Counter associated with event <event number> exceeds limit <%s>. Resetting counter. |
|
Surveillance Notification |
|
|
Text |
None |
|
Source |
|
|
Frequency |
|
|
Trap |
|
|
Trap ID |
None |
|
Trap MIB Name |
|
Explanation
The event number present in the untilTimeout filter list is cleared. The event number is removed from the untilTimeout filter list.
Recovery
No action is required.
Event Details
|
GUI Notification |
|
|
Severity |
Event |
|
Text |
<Event number> in the untilTimeout filter list, event timeout at <%s> |
|
Surveillance Notification |
|
|
Text |
None |
|
Source |
|
|
Frequency |
|
|
Trap |
|
|
Trap ID |
None |
|
Trap MIB Name |
|
Explanation
The log capture started by the user has failed.
Recovery
Contact the My Oracle Support (MOS).
Event Details
|
GUI Notification |
|
|
Severity |
Minor |
|
Text |
Logs Capture Failed |
|
Surveillance Notification |
|
|
Text |
None |
|
Source |
|
|
Frequency |
|
|
Trap |
|
|
Trap ID |
None |
|
Trap MIB Name |
|
Explanation
The MySQL Port has been updated. The LSMS application must be restarted.
Recovery
The application must be restarted. Restart the LSMS application first on the active server and then on the standby server. For more information, refer to the Configuration Guide.
Event Details
|
GUI Notification |
|
|
Severity |
Event |
|
Text |
MySQL Port changed from <%s> to <%s>. LSMS application restart required. |
|
Surveillance Notification |
|
|
Text |
Notify: Sys Admin - LSMS restart required |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
208 |
|
Trap MIB Name |
mysqlPortUpdated |
Explanation
The MySQL Port has been updated. The Query Server configuration needs to be updated with the new MySQL port.
Recovery
Configure the Query Server with the updated MySQL port. For more information, refer to the Configuration Guide.
Event Details
|
GUI Notification |
|
|
Severity |
Event |
|
Text |
MySQL Port changed from <%s> to <%s>. Query Server configuration updated required. |
|
Surveillance Notification |
|
|
Text |
Notify: Sys Admin - QS updated required |
|
Source |
Active server |
|
Frequency |
Once, as soon as condition occurs |
|
Trap |
|
|
Trap ID |
209 |
|
Trap MIB Name |
queryServerResetConfiguration |
Explanation
At least one of the connected Query Servers is out of sync, and the binary logs cannot be purged without user confirmation.
Recovery
pruneBinaryLogs -force
Event Details
|
GUI Notification |
|
|
Severity |
Minor |
|
Text |
Automatic purging of binary logs cannot be done. User confirmation required. |
|
Surveillance Notification |
|
|
Text |
Notify: Sys Admin - Purge need confirmation |
|
Source |
Both servers |
|
Frequency |
Every 45 minutes |
|
Trap |
|
|
Trap ID |
210 |
|
Trap MIB Name |
purgeConfirmRequired |
Explanation
Disk usage is reaching the capacity threshold, and an automatic purge of binary logs is imminent.
Recovery
No action is required.
Event Details
|
GUI Notification |
|
|
Severity |
Minor |
|
Text |
Disk usage reaching <%> percent. Purging of binary logs is imminent. |
|
Surveillance Notification |
|
|
Text |
Notify: Sys Admin - Purging is imminent |
|
Source |
Both servers |
|
Frequency |
Every 45 minutes |
|
Trap |
|
|
Trap ID |
211 |
|
Trap MIB Name |
purgeImminent |
Explanation
Logs capture has been started by the user.
Recovery
No action is required.
Event Details
|
GUI Notification |
|
|
Severity |
Cleared |
|
Text |
Logs Capture Started |
|
Surveillance Notification |
|
|
Text |
None |
|
Source |
|
|
Frequency |
|
|
Trap |
|
|
Trap ID |
None |
|
Trap MIB Name |
|
Explanation
The logs capture started by the user completed successfully.
Recovery
No action is required.
Event Details
|
GUI Notification |
|
|
Severity |
Minor |
|
Text |
Logs Captured Successfully |
|
Surveillance Notification |
|
|
Text |
None |
|
Source |
|
|
Frequency |
|
|
Trap |
|
|
Trap ID |
None |
|
Trap MIB Name |
|
Explanation
Syscheck was not able to restart automatically by the cron job.
Recovery
Contact the My Oracle Support (MOS).
Event Details
|
GUI Notification |
|
|
Severity |
Event |
|
Text |
Failed to restart syscheck services |
|
Surveillance Notification |
|
|
Text |
None |
|
Source |
|
|
Frequency |
|
|
Trap |
|
|
Trap ID |
None |
|
Trap MIB Name |
|
Explanation
The HTTP protocol is enabled but secure HTTP (HTTPS) is recommended.
Recovery
For information on configuring the protocols, see Starting an LSMS GUI Session.
Event Details
|
GUI Notification |
|
|
Severity |
Event |
|
Text |
HTTP is enabled and it is recommended to use HTTPS. |
|
Surveillance Notification |
|
|
Text |
None |
|
Source |
|
|
Frequency |
|
|
Trap |
|
|
Trap ID |
None |
|
Trap MIB Name |
|
Explanation
HTTP is disabled and HTTPS is enabled.
Recovery
No recovery required; only HTTPS is enabled now.
Event Details
|
GUI Notification |
|
|
Severity |
Event |
|
Text |
Only HTTPS is enabled now. |
|
Surveillance Notification |
|
|
Text |
None |
|
Source |
|
|
Frequency |
|
|
Trap |
|
|
Trap ID |
None |
|
Trap MIB Name |
|
Explanation
Both HTTP and HTTPS are enabled, but using only HTTPS is recommended.
Recovery
For information on configuring the protocols, see Starting an LSMS GUI Session.
Event Details
|
GUI Notification |
|
|
Severity |
Event |
|
Text |
Both HTTP and HTTPS are enabled and it is recommended to use HTTPS. |
|
Surveillance Notification |
|
|
Text |
None |
|
Source |
|
|
Frequency |
|
|
Trap |
|
|
Trap ID |
None |
|
Trap MIB Name |
|
| Trap Id | Trap MIB Name | Notification Description | Trap variables def | Retry Interval | Severity | Event Num | GUI Event Text | Pair Event Num |
|---|---|---|---|---|---|---|---|---|
| 25 | dataReplInfo | This notification indicates that database replication is delayed. | eventNbr = Oracle specific unique identifier for event notification. This eventNbr field can be used to reference Oracle documentation. dbReplInfo = Info message from database replication. | Every 5 mins | event_notif_event | 4011 | DB Repl Info - %s | 0 |
| 201 | snapInvalidErr | This notification indicates that the Invalid Snapshot has been detected. | eventNbr = Oracle specific unique identifier for event notification. This eventNbr field can be used to reference Oracle documentation. snapName = Name of the invalid snapshot. | Every 30 mins | event_notif_critical | 4034 | Invalid Snapshot - %s | 4035 |
| 203 | snapFullErr | This notification indicates that the Snapshot is greater than 80% full. | eventNbr = Oracle specific unique identifier for event notification. This eventNbr field can be used to reference Oracle documentation. snapName = Name of the invalid/hanging snapshot. | Every 30 mins | event_notif_critical | 4036 | Full Snapshot - %s | 4037 |
| Trap Id | Trap MIB Name | Notification Description | Frequency | Source | Clearing behavior |
|---|---|---|---|---|---|
| 212 | resyncStartTrap | The trap is sent by the LSMS to NMS when the LSMS is about to start resynchronization | Every time when starting a resynchronization with a NMS | /vobs/lsms/apps/snmp/ lsmsSNMPResyncHandler.pl | None |
| 213 | resyncStopTrap | The trap is sent by the LSMS to NMS when resynchronization is complete | Every time when a resynchronization with a NMS is complete | /vobs/lsms/apps/snmp/ lsmsSNMPResyncHandler.pl | None |
| 214 | resyncRejectTrap | The trap is sent by the LSMS to NMS when a resynchronization request is rejected by LSMS | Every time when a resynchronization request is initialized while an existing resynchronization is still being processed | /vobs/lsms/apps/snmp/ lsmsSNMPResyncHandler.pl | None |
| 215 | resyncRequiredTrap | The trap is sent by the LSMS to NMS when the LSMS is rebooted or LSMS is started | Every time when LSM S is rebooted or restarted | /vobs/lsms/apps/snmp/ lsmsSNMPResyncHandler.pl | None |
| 216 | heartBeatTrap | The trap is sent by the LSMS to NMS periodically to indicate that the LSMS is up | Per the configured value in second (0, 5-7200), where 0 indicates the heartbeat trap is disabled. | /vobs/lsms/apps/snmp/ lsmsSnmpHeartbeatSender.pl | None |
| 217 | lsmsAlarmTrapV3 | The trap will indicate that the following information is for a particular event | Every v3 trap message sent to nms will carry this OID | /vobs/lsms/apps/snmp/ lsmsSNMPResyncHandler.pl | None |
| 218 | resyncErrCode | errorCode = 0, Resynchronization completed successfully. errorCode = 1, Resynchronization aborted by NMS. errorCode = 2, Resynchronization already in progress for the NMS. errorCode = 3, Resynchronization Aborted, Database error occurred. errorCode = 4, Resynchronization not in progress. | Every time when either resyncStopTrap or resyncRejectTrap sent to NMS | /vobs/lsms/apps/snmp/ lsmsSNMPResyncHandler.pl | None |