Appliance
Process Failure
|
FTP, MATLAB,
TFTP
|
Whenever the
FTP, MATLAB, or TFTP process on Prime Infrastructure server fails, the server
will generate a failure trap and the server's instance of Health Monitor will
try to restart the process automatically. If Health Monitor cannot restart it
after 3 tries, the HA server will send another failure trap.
|
Appliance
Process Failure
|
NMS
|
Whenever the
NMS process on a server starts or fails, the Prime Infrastructure server's
Health Monitor thread will generate a corresponding trap.
To stop or
restart the process, connect to the server via CLI and log in as admin. Then
execute the nms stop or nms start command, as appropriate.
|
HA Operations
|
Registration
Trigger
|
Prime
Infrastructure generates this trap whenever the primary server initiates HA
registration (whether registration fails or succeeds).Once HA registration is
triggered, the primary server generates the trap, indicating the start of the
operation.
|
HA Operations
|
Registration
Success
|
When HA
registration is successful, the primary server generates this trap, indicating
success.
|
HA Operations
|
Registration
Failure
|
When HA
registration fails for any reason, the primary or secondary server on which the
failure occurred, generates a trap indicating the failure. The trap contains
details about the failure. For assistance, contact the Cisco Technical
Assistance Center (TAC).
|
HA Operations
|
Failover
Trigger
|
This trap is
generated whenever the Prime Infrastructure primary server fails and, as part
of a failover, the secondary server tries to become active (whether failover
fails or succeeds, and whether the secondary server comes up or fails to do
so). If the HA configuration (set during registration) has a Manual failover
type, users must trigger the failover. Otherwise, the Health Monitor will
trigger failover to the secondary server automatically.
One trap will
be generated to indicate that the failover was triggered. Because the trap is
sent before the failover completes, it will not be logged on the secondary
server.
|
HA Operations
|
Failover
Success
|
When the
triggered failover operation is successful, the secondary server generates a
trap indicating success. Users can view the trap in the secondary server's
alarm browser.
|
HA Operations
|
Failover
Failure
|
When the
triggered failover operation fails, a trap will be generated indicating the
failure. Users can view the trap in the hm-#-#.log (see
How to Troubleshoot Prime Infrastructure SNMP Traps).
The trap contains details about the failure. For assistance, contact Cisco TAC.
As with other failure traps, alarms and a “clear” trap are sent if the failure
corrects itself.
|
HA Operations
|
Failback
Trigger
|
This trap is
generated whenever a failback to the primary server is triggered on the
secondary server (whether or not the failback is successful). Once the primary
server is restored, a user must trigger a failback from the secondary server to
the primary server using the Failback button on the secondary server Health
Monitor web page (there is no automatic Failback option). Once triggered, the
secondary server generates the trap indicating the start of the operation.
|
HA Operations
|
Failback
Success
|
When the
triggered failback operation is successful, the secondary server generates a
trap indicating success. Failback success sets the primary server to the
‘Active’ state and the secondary server to the ‘Sync’ state.
|
HA Operations
|
Failback
Failure
|
When the
triggered failback operation fails, a trap will be generated indicating this
failure. Since the failure can occur on either server, the server on which it
occurred will generate the trap. Users can view the trap in the hm-#-#.log and
on the northbound management server.
A failback
failure triggers an automatic rollback, in which the secondary server tries to
return to its previous ‘Active’ state. Failure of this operation will cause the
secondary server to generate an additional trap indicating rollback failure.
The failure traps contain details about the failures. For assistance, contact
Cisco TAC. As with other failure traps, alarms and a “clear” trap are sent if
the failure corrects itself.
|
Hardware
Traps
|
CPU
Utilization
|
Traps will be
sent only when the usage exceeds the preset threshold value for CPU
utilization. To view these traps, check the jobs and active sessions for the
server that generated the trap.
|
Hardware
Traps
|
Disk
Utilization
|
Traps will be
sent only when the disk usage exceeds the set threshold limit for Disk
utilization. To respond, try to free up disk space under the /opt and
/localdisk partitions. Do not delete folders under /opt/CSCOlumos without
guidance from Cisco TAC.
|
Hardware
Traps
|
Memory
Utilization
|
Traps will
be sent to the SNMP trap receiver, only when memory usage exceeds the set
threshold limit for memory utilization.
|
Hardware
Traps
|
Disk
Failure
|
Traps will
be sent to the SNMP trap receiver when disk failure is detected. Contact your
local system administrator for corrective action. As with other failure traps,
alarms and a “clear” trap are sent if the failure corrects itself.
|
Hardware
Traps
|
Fan Failure
|
Traps will
be sent to the SNMP trap receiver when fan failure is detected. The bad or
missing fan will be identified in the trap or alarm message. Contact your local
system administrator for corrective action. As with other failure traps, alarms
and a “clear” trap are sent if the failure corrects itself.
|
Hardware
Traps
|
PSU Failure
|
Traps will
be sent to the SNMP trap receiver when PSU failure is detected. The problematic
power supply will be identified in the trap or alarm message. Contact your
local system administrator for corrective action. As with other failure traps,
alarms and a “clear” trap are sent if the failure corrects itself.
|
Threshold
Traps
|
Backup
Failure
|
Traps will
be sent to the SNMP trap receiver when failure of the daily background task of
Prime Infrastructure server backup is detected. The background task runs
everyday and takes a backup of the server at the scheduled time. If the backup
fails due to insufficient disk space, the event will be processed. If the
backup is taken successfully, the alarm will be cleared.
|
Threshold
Traps
|
Backup
Threshold
|
Informs
users when Prime Infrastructure scheduled daily backup has not been taken for a
threshold number of days. The default threshold is seven days. If no backup has
been taken for seven days, users are notified by this event.
|
Threshold
Traps
|
Certificate
Expiry
|
Traps will
be sent to the SNMP trap receiver when the certificate is about to expire. A
critical trap is sent when the certificate is set to expire in 15 days and a
major trap is sent when the certificate expiry is in 60 days.
|
System
Traps
|
Lifecycle
|
Lifecycle
license is used to manage devices. Alarm is generated when the license usage
exceeds the configured threshold percentage. By default, traps will be sent
when the usage exceeds 80%. However, this can be customized.
|
System
Traps
|
Assurance
|
Assurance
License is used to display the devices that pump NetFlow to Prime
Infrastructure. Alarm is generated when the license usage exceeds the
configured threshold percentage. By default, traps will be sent when the usage
exceeds 80%. However, this can be customized.
|
System
Traps
|
Collector
|
Collector
License is used to display the volume of NetFlow pumped to Prime
Infrastructure. Alarm is generated when the license usage exceeds the
configured threshold percentage. By default, traps will be sent when the usage
exceeds 80%. However, this can be customized.
|
System
Traps
|
Lifecycle
License
|
Traps will
be sent when the expiry period of the License goes below the threshold limit.
By default, traps will be sent when the limit is 30 days. However, you can
customize the limit between 1-99 days. This event is considered only when you
use Evaluation License.
|
System
Traps
|
Assurance
License
|
Traps will
be sent when the expiry period of the License goes below the threshold limit.
By default, traps will be sent when the limit is 30 days. However, you can
customize the limit between 1-99 days. This event is considered only when you
use Evaluation License.
|
System
Traps
|
Collector
License
|
Traps will
be sent when the expiry period of the License goes below the threshold limit.
By default, traps will be sent when the limit is 30 days. However, you can
customize the limit between 1-99 days. This event is considered only when you
use Evaluation License.
|