Management Agent Resource Monitoring, Polling and SNMP Support

The following table lists the configurable values for polling and thread selection in the hwmgmtd.conf file when SNMP monitoring is used on the host. In addition, there is a memory usage monitoring setting for the management agent to prevent possible memory leak issues.

Note:

The default configuration for polling provides the optimal functionality in systems where SNMP monitoring is not used. Where host-based SNMP monitoring is configured and the Oracle ILOM trap proxy setup using itpconfig, the Hardware Management Agent will perform an initial poll of Oracle ILOM and then listen for Oracle ILOM SNMP traps to decide when a re-pole is needed. Enabling SNMP polling threads increase resources used by the Hardware Management Agent which might affect system performance.

Thread	Description
storage_poller_enabled=<value>	When enabled, the Hardware Management Agent provides up-to-date information about host internal storage to Oracle ILOM. In addition, if SNMP monitoring is enabled on the host, this poller responds to host SNMP requests to the SUN-STORAGE-MIB. Supported values are: 0=disabled; 1=enabled. The default is 1. Note: Disabling this parameter is not recommended as it will prevent storage information from being sent to Oracle ILOM.
inventory_poller_enabled=<value>	When enabled, this poller responds to host SNMP requests to the SUN-HW-MONITORING-MIB. Supported values are: 0=disabled; 1=enabled. The default is 0.
request_thread_enabled=<value>	When enabled, the Hardware Management Agent responds to host SNMP requests and listens for SNMP traps generated by Oracle ILOM. Supported values are: 0=disabled; 1=enabled. The default is 0.
polling_round_delay=<time in seconds>	If needed, this option can be added. When set, this option overrides the default polling delay of every hour, or sooner if a trap is detected when using host-based SNMP monitoring and the Oracle ILOM trap proxy. You might want to add this option if you require more precise real-time data regarding sensor values (temperature/voltage). Set the default sleep time in seconds. Note: When using this option, Oracle recommends not setting it to anything under 60 seconds due to the additional use of system resources.
hwmgmtd_reset_hour=<hour>	To prevent possible memory leaks, the management agent service should be reset once daily. Choose a time when there is little server activity since restarting the agent temporarily increases I/O activity as it performs device discovery. Set the reset time in whole hours. Supported values are: 0-23. The default is 3 (for 3AM local time). Note: In Oracle Solaris 11.4 release SRU 6, this feature has been removed. To monitor possible memory leaks, use the resource_monitor_enabled and resource_monitor_threshold threads.
resource_monitor_enabled=<value>	When enabled, the Hardware Management Agent checks for possible memory leaks caused by unusual memory usage by the agent service itself. Supported values are: 0=disabled; 1=enabled. The default is 1. This thread was introduced in Oracle Solaris 11.4 SRU 6.
resource_monitor_threshold=<value>	When the agent resource monitor is enabled, this setting becomes the basis of an algorithm to define a threshold where the agent will automatically restart if the threshold is reached. The value you enter is used to determine how much memory used by the agent service is too much. For example, if the value you enter is 3, then the threshold would be three times the amount of memory typically required for the agent at service start-up. Set the threshold value in whole numbers. The default is 5 (for five times the typical memory usage at service start-up). This thread was introduced in Oracle Solaris 11.4 SRU 6.