View node Network properties

To view and configure Network properties for a selected node

1. Right-click the name of the node in the console tree to open the shortcut menu.
2. Select Properties to open the Properties dialog box for the selected node, which displays the General tab by default.
3. Select the Network tab.
4. In the Primary Node Name box, enter a unique node name. This information is required and is automatically entered if you selected the node to be managed by dragging and dropping the node name from the Discovered Nodes list to the Nodes list in the Configure Managed Nodes dialog box.

   When this information is entered or changed, the System Type, OS Type, and OS Version are automatically modified in the System tab.

5. Specify your preferences in the Server To Node Communications box. Check Node IP address obtained automatically (DHCP) if you do not want to use a static IP address.

   The server will not cache an IP address it once received for a system, but will do a name resolution every time a system is contacted. This means that if you specify the name of a system as the communication path value, and you have checked this box, the given name is always resolved (using an external name resolution service like DNS) if the node is contacted.

   NOTE:
   If you do not check this box, the server caches the first IP address it received for a node from a name resolution service. On subsequent contacts, the server uses the cached IP address instead of doing another external name resolution. This increases performance for nodes using a static IP address.

   Check Notify management server if node communication address changes if you want the server to be aware of IP address changes.

   The agent checks each time you start the system to see if the IP address of the system you are running on has changed. If the answer is yes, this information is sent to the management server, where the communication path of the corresponding node is updated with the new IP address.

   NOTE:
   If the address space of the managed node is different from the address space of the management server (because they are located in different subnets), it is possible that the management server cannot use the new IP address it received from an agent. In this case, to prevent errors, do not check the Notify management server if node communication address changes check box.

   If you check this box, selections below it in the dialog box appear dimmed and are unavailable.

6. If you did not make a selection in the Server to Node Communications box, click either the IP Address or Domain Name FQDN button to specify a communications path. If you select IP Address, you must enter the IP address manually.

   By default, the Domain Name (FQDN) box displays the primary node name. If you change the primary node name, the change is reflected in the Domain Name (FQDN) box. You can also enter the domain name for the node you are configuring in the space provided. This information is optional.

   If you have multiple IP addresses for a particular node and the communications path would differ from the Primary Node Name, specify the particular IP address or DNS name that you want.

7. Heartbeat Polling sends a signal to the managed node or contacts the agent on the node to check whether the node is offline.

   System Default means that the management server uses the heartbeat polling setting from the Server Configuration dialog box. This setting is valid for all managed nodes and is by default "ICMP & Agent". To override the system default for a managed node, set Polling to Custom, then specify the Ping Protocol you want to use:

   • ICMP & Agent

   • With this option, the server first attempts to contact the node using ICMP packages to find out if the node is reachable. If this succeeds, it will contact the agent on the node to find out if the agent processes are running. When this fails, it will use ICMP packages again to find out if, at least, the system is alive. As soon as this succeeds, the agent is contacted again. This option is not recommended for nodes outside of a firewall because ICMP calls are usually blocked by firewalls.

   • Agent Only

   • The management server does not actively contact the node with ICMP pings, but still contacts the agent on the node. This is the recommended setting for nodes outside of a firewall. The disadvantage is that in the event of a system outage, the network load is higher than with normal heartbeat monitoring because the agent connection is still being tried.

   • ICMP Only

   • The management server sends ping packages (using ICMP) to verify the availability of the agent. This option is not recommended for nodes outside a firewall because ICMP calls are usually blocked by firewalls.

8. Set the polling Interval in seconds. This is the interval at which the management server checks whether the managed node is offline. The minimum is polling interval is 60 seconds, and the maximum is 28800 (8 hours).
9. Clear Enable Auto Deployment if you do not want HPOM to automatically deploy policies to the node. HPOM automatically deploys policies to a node when the agent is correctly installed. For HTTPS agents, a correctly installed certificate is also required; otherwise the deployment job fails.

   By default, HPOM automatically deploys certain core policies to nodes. The core policies include autodiscovery policies that gather service information on nodes. This information is sent back to the management server to generate a service tree. (You can also automatically deploy additional groups of policies by associating policy groups with node groups and service types.)

10. Click Apply to confirm your changes.
11. Click OK to apply your changes and close this dialog box.
12. Click Cancel to close this dialog box without saving your changes.

Related Topics:

• View General information for Node properties
• View Network information for Node properties
• View System information for Node properties
• View Tools information for Node properties
• Agent health checks
• Disable policy autodeployment