 | | Introduction |
Polling Tasks track system status for systems in the System List. It provides a simple means of assessing system health in the event that an SNMP Trap or other event was not properly delivered to the Management console. System Status Polling must occur continuously to determine when systems go offline or performance degrades. You can customize Polling Tasks for specific systems to run at scheduled times. You can also create new Polling Tasks with different System or Event Lists to match your specific requirements. There are two default Polling Tasks:
Software Status Polling. Use Software Status Polling to determine software version update status. This task is set to run every seven days, on Wednesday at midnight, by default. You can edit the task and run it at any time. This task:
Retrieves software and firmware inventory from systems Determines the software and firmware update status Sorts versions in the database
To access Software Status Polling, select Options Status PollingSoftware Status Polling. Hardware Status Polling. Used to track system status. There are two types of Hardware Status Polling Tasks:
Hardware Status Polling for Non-Servers
. Used to collect status information for SNMP systems that are not of a server, cluster, or management processor type. This task is configured to poll every 10 minutes and at startup by default and does not send status change events.
Hardware Status Polling for Servers
. Used to collect status information for SNMP systems of type server, cluster, or management processor. This task is configured to poll every 5 minutes and at startup by default and sends status change events where you can set up a Notification Task based on the event.
To access Hardware Status Polling, select OptionsStatus PollingHardware Status Polling.
| | Related Procedures |
|
