Skip to main content
We are redesigning the NetApp Knowledge Base site to make it easier to use and navigate. The new and improved site will be available the first week of October. Check out our video or read this KB article to know more about changes you’ll see on the site.
NetApp Knowledge Base

How does Unified Manager 5.x determine that a host is down?

Views:
53
Visibility:
Public
Votes:
0
Category:
oncommand-unified-manager-core-package
Specialty:
om
Last Updated:

Applies to

  • Oncommand Unified Manager 5.x

Answer

OnCommand Unified Manager (DFM) uses five different methods to identify whether a host is down

  1. Echo
  2. HTTP
  3. SNMP
  4. NDMP
  5. Echo_SNMP(Default)

The default behavior for a host down monitor run is a ping using a combination of ICMP echo and snmpwalk. OnCommand Unified Manager (DFM) will retry each method a pre-configured number of times with varying timeouts, as shown in the outputs below.
 

pingMonInterval          00:01:00
hostPingMethod           echo_snmp
pingMonTimeout           3
pingMonRetryDelay        3
monSNMPTimeout           60
monSNMPRetries           4

Oncommand Unified Manager(DFM) will perform this check by default every minute. The timeout and retry values are in seconds. Increasing these values will delay the amount of time before Oncommand Unified Manager(DFM)  assumes the host is down. The status of a controller is logged in the pingmon.log with either unknown,up, or down. It will log changes in the status such as up to down, down to up, unknown to up, etc..

Additional Information

additionalInformation_text

 

 

******************************************************* *******************************************************