Supported SNMP traps

Supported SNMP traps
		GO

Purpose

This topic describes the SNMP traps that are supported by the Lucent CM system.

Faul clearance procedures

For SNMP traps that provide fault information, possible root causes and fault clearance information is provided.

SNMP Trap parameters default values

The following table shows the default values for SNMP trap parameters:

Parameter	Value
`SNMP Trap Severity`	Refer to SNMP traps
`SNMP Trap Threshold`	1
`SNMP Trap Allowed`	True

SNMP traps

SNMP Trap description	Default SNMP Trap severity	Description	Manual action Root causes and fault clearance procedure
Application state change	Major	The status of an application changed from an <old state> to a <new state>. The alarm indicates the loss or recovery of a Lucent CM process.	Application recovers automatically. When the state change results from craft action, no action is required. The alarm is cleared automatically when the application state changes back.
DN Extension Provisioning mismatch between FS 5000 and Lucent CM	Major	A provisioning mismatch for DN Extension PSI service is detected between the FS 5000 and Lucent CM.	Compare provision for the DN Extension PSI service. Determine the correct provision values and correct the mismatches
Host state change	Major	The status of a Lucent CM node changed from an <old state> to a <new state>	Verify IP connectivity Check for power failure Check for hardware failure The alarm is cleared automatically when the host state changes back.
Call Server connection failed	Minor	The connection between the Lucent CM node and the call server fails.	Verify IP connectivity Check for FS 5000 server failure
OMC-P connection failed	Minor	The connection between the Lucent CM node and the OMC-P fails.	Possible root causes Verify IP connectivity Check for OMC-P server failure
ISG Call log Server connection failed	Minor	The connection between the Lucent CM node and the ISG fails.	Possible root causes Verify IP connectivity Check for ISG server failure
Enter overload protection status	Minor	The Lucent CM system went into overload protection status. The system and will reject end-user client and Enterprise Administrator API requests.	Possible root causes Lucent CM node is not correctly engineered. Abnormal number of API request. Failure to release resources.
Account disabled due to log on failure	Event	An end-user account is disabled due to multiple log on failures.	Enable the user account, when requested by the end user.
Application failed to come DOWN in some seconds	Event	An application crashed due to an abnormal situation.	Contact Lucent Technical support.
Application failed to come UP in some seconds	Event	An application crashed due to an abnormal situation.	Contact Lucent Technical support.
Application is not allowed to run right now, so we will stop it	Event	This is an auxiliary message when HA comes up.	No action required.
Application is running, but is ADMIN-DOWN, so we will stop it	Event	An application is being shut down via CLI commands.	Results from craft action. No action required.
Both HA Servers are MASTER, going to SLAVE	Event	The state of the HA servers change.	Results from craft action. No action required.
Both HA Servers are SLAVE, going to MASTER	Event	The state of the HA servers change.	Results from craft action. No action required.
Both HA Servers are SLAVE, staying SLAVE	Event	The state of the HA servers change.	Results from craft action. No action required.
Completing HA Resources Update	Event	An update of HA resources is completed.	Results from craft action. No action required.
Force killing application	Event	An application is killed forcefully via a CLI command.	Results from craft action. No action required.
Force starting application	Event	An application is started forcefully via a CLI command.	Results from craft action. No action required.
Going into master mode by command	Event	HA server starts to go to MASTER mode because of a craft action.	Results from craft action. No action required.
Going into slave mode by command	Event	HA server starts to go to SLAVE mode because of a craft action.	Results from craft action. No action required.
HA Server is now MASTER	Event	HA server has changed to MASTER mode	Results from craft action. No action required.
HA Server is now SLAVE	Event	HA server has changed to SLAVE mode	Results from craft action. No action required.
HA system clock alert was cleared	Event	A system clock alert has been cleared using the command `clear_clock_warning`	Alarm clearance event, no action is required.
HA system clock alert went backward	Event	System time is updated using NTP	Verify if the system time is abnormal. If the time is abnormal, check NTP server. If time is normal, no action is required. To clear the alarm: Log in to the node Type the following command and press ENTER: `clear_clock_warning`
HA system clock alert went backward by some seconds	Event	System time is updated using NTP	Verify if the system time is abnormal. If the time is abnormal, check NTP server. If time is normal, no action is required. To clear the alarm: Log in to the node Type the following command and press ENTER: `clear_clock_warning`
MLHG Provisioning mismatch between FS 5000 and Lucent CM	Event	A provisioning mismatch for the MLHG service is detected between the FS 5000 and Lucent CM.	Compare provision for the MLHG service. Determine the correct provision values and correct the mismatches
Reloading HA resources, list of resources may change	Event	This is an auxiliary message when HA comes up.	No action required.
Restarting node	Event	A Lucent CM node is started via a CLI command.	Results from craft action. No action required.
Setting applications from Admin stat to a given application state	Event	An application is being shut down via CLI commands.	Results from craft action. No action required.
Setting to master mode due to extended period of no peer communication.	Event		Results from craft action. No action required.
Setting to master mode for simplex system	Event	HA server on a simplex system starts to go to MASTER mode because of a craft action.	Results from craft action. No action required.
Shutting down HA server on command	Event	The HA server shuts down.	Results from craft action. No action required.
Starting HA resources update	Event	An update of HA resources is started.	Results from craft action. No action required.
Stopping node	Event	A Lucent CM node is stopped via a CLI command.	Results from craft action. No action required.
Unable to communicate with the DB Tie-Breaker	Event	The Lucent CM node cannot communicate with the database tie-breaker.	Possible root causes Verify IP connectivity

		GO
© Lucent Technologies