Polling tasks track health status for systems in the associated collections. Hardware Status Polling needs to occur periodically in order to determine when systems go offline or hardware degrades. You can customize polling tasks for specific systems to run at scheduled times. You can also create new polling tasks with different collections to match your specific requirements.
Data Collection Tasks are included with other polling tasks. Data Collection finds more specific system information, such as asset data.
You can configure the polling tasks to take place based on the receipt of an event. Event Polling Tasks are associated with event collections. For example, you might set up a Hardware status polling task for when traps are received from a system.
When a polling task is set up to run as the result of a change in an event collection, the polling task is applied to all systems generating events that match the given collection.
The following default polling tasks are available on the View All Scheduled Tasks page:
Bi Weekly Data CollectionThe Bi Weekly Data Collection task runs on all of the systems in the Data Collection List collection. The default schedule is to run every other Saturday at noon.
Daily Device IdentificationUse the Daily Device Identification task to identify information about systems like networking systems. This task runs once a day by default and the information is stored in the database. The following information is identified:
Determines Single Login and Secure Task Execution (STE) support on a managed system
Type of management protocol on the system (HTTP, SNMP, DMI, WBEM)
Type and subtype of system (server, storage, switch, router, and so on)
Product name of the system
Operating system name and version
Web Agents running on the system
Web-based software running on the system, for example, printer management software
System associations with management processors, for example, a system and it's Remove Insight Board
Storage proxies and related storage systems
Hardware Status Polling for non ServersThis task collects status information through management protocols (SNMP, WBEM, and so on) for 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.
Hardware Status Polling for ServersThis task collects status information for SNMP systems of type Server, Cluster, or Management Processor. This task is configured to poll every five minutes and at startup by default.
Hardware Status Polling for Systems no Longer DisabledThis task runs when a system goes from a disabled state to an enabled state. You could use this task to get the latest status after a planned maintenance window on a system that was set to disabled..
Initial Data CollectionThis task collects static information from a number of systems that have WBEM, DMI, or SNMP running. For example, serial numbers and model numbers. This task is set to run by default when a new system matches the data collection. For more information on what data is collected, refer to HP Systems Insight Manager Technical Reference Guide - Reference Information.
Initial Hardware Status PollingThis task runs hardware status polling on systems that are newly discovered. Therefore, you do not need to wait for the periodic tasks to run before the system has a valid status..
Software Version Status PollingThis task determines software version update status and is set to run every seven days, on Wednesday at Midnight, but default. You can edit this task or manually run it at any time. Refer to Status Polling - Software Status Polling for more information.
Software Version Status Polling for Systems no Longer DisabledThis task runs the software version tool when a system goes from a disabled state to an enabled state, so that the status of the software loaded on the system is kept up to date in HP Systems Insight Manager (HP SIM). Refer to Status Polling - Software Status Polling for more information.
Related Procedures
Related Topic
|