Internal Events

This application generates the following internal events in response to its working:

[spacer]

Trap name

Trap OID

Severity

What causes the trap

redcellAppServerDownNotification

.1.3.6.1.4.1.3477.1.6.1.2

Critical

Generated when one of the application server in the cluster goes down. The alarm is cleared when the application server comes back up.

redcellAppServerLicenseExpNotification

.1.3.6.1.4.1.3477.1.6.1.4

Critical

The license is scheduled to expire in 15 days. The trap may occur multiple times if the license is not renewed.

redcellMedServerDownNotification

.1.3.6.1.4.1.3477.1.6.2.1

Critical

Generated when the mediation server goes down, the alarm is cleared when the mediation server comes back up.

redcellNoRemoteMedServerAvailableNotification

.1.3.6.1.4.1.3477.1.6.2.3

Critical

Generated where no mediation server is available in the network. This alarm is only generated when the application server is not configured to listen for traps.

redcellDBCapacityThresholdExceededNotification

.1.3.6.1.4.1.3477.1.6.3.1

Major

N/A -Reserved for future functionality:

redcellDeviceDownHeatBeatNotification

.1.3.6.1.4.1.3477.1.6.5.1

Critical

Generated when the device managed by Redcell fails to the respond to the heartbeat. The alarm is cleared when the heartbeat is successful.

redcellNetConfigBackupFailureNotification

.1.3.6.1.4.1.3477.1.6.6.1

Major

Generated when a device backup fails. This alarms required manual clearing.

redcellJobFailureNotification

.1.3.6.1.4.1.3477.1.6.7.2

Major

Generated when a Job fails. For example, if a device resync fails then the application generates a job failure notification notifying about the resync job failure. The Job Failure alarm requires manual clearing.