Cisco Cisco Firepower Management Center 4000
55-13
FireSIGHT System User Guide
Chapter 55 Using Health Monitoring
Configuring Health Policies
•
To return to the Health Policy page without saving any of your settings for this module, click
Cancel
.
•
To temporarily save your changes to this module and switch to another module’s settings to modify,
select the other module from the list at the left of the page. If you click
select the other module from the list at the left of the page. If you click
Save Policy and Exit
when you
are done, all changes you made will be saved; if you click
Cancel
, you discard all changes.
You must apply the health policy to the appropriate appliances if you want your settings to take effect.
See
See
for more information.
Configuring Card Reset Monitoring
License:
Any
Use the card reset monitoring health status module to track when the network card restarts because of
hardware failure. If a reset occurs, this module generates an alert. That status data feeds into the health
monitor.
hardware failure. If a reset occurs, this module generates an alert. That status data feeds into the health
monitor.
To configure card reset monitoring:
Access:
Admin/Maint
Step 1
In the Health Policy Configuration page, select
Card Reset
.
The Health Policy Configuration — Card Reset Monitoring page appears.
Step 2
Select
On
for the
Enabled
option to enable use of the module for health status testing.
Step 3
You have three options:
•
To save your changes to this module and return to the Health Policy page, click
Save Policy and Exit
.
•
To return to the Health Policy page without saving any of your settings for this module, click
Cancel
.
•
To temporarily save your changes to this module and switch to another module’s settings to modify,
select the other module from the list at the left of the page. If you click
select the other module from the list at the left of the page. If you click
Save Policy and Exit
when you
are done, all changes you made will be saved; if you click
Cancel
, you discard all changes.
You must apply the health policy to the appropriate Defense Center if you want your settings to take
effect. See
effect. See
for more information.
Configuring Discovery Event Status Monitoring
License:
FireSIGHT
Use the Discovery Event Status module to monitor the health of the discovery process on a device from
the Defense Center by generating alerts when too many seconds elapse between discovery events
received by the Defense Center. You can configure the elapsed duration between events, in seconds, that
causes an alert to be generated. If the wait exceeds the number of seconds configured in the Warning
Seconds since last event limit, the status classification for that module changes to Warning. If the wait
exceeds the Critical Seconds since last event limit, the status classification for that module changes to
Critical. That status data feeds into the health monitor.
the Defense Center by generating alerts when too many seconds elapse between discovery events
received by the Defense Center. You can configure the elapsed duration between events, in seconds, that
causes an alert to be generated. If the wait exceeds the number of seconds configured in the Warning
Seconds since last event limit, the status classification for that module changes to Warning. If the wait
exceeds the Critical Seconds since last event limit, the status classification for that module changes to
Critical. That status data feeds into the health monitor.
The maximum number of seconds you can set for either limit is 7200, and the Critical limit must be
higher than the Warning limit. The minimum number of seconds is 3600.
higher than the Warning limit. The minimum number of seconds is 3600.