HPE XP7 Automation Director User Manual page 351

Server on which Hyper-V is installed.
• Virtual server
Virtual server managed by Hyper-V
Prerequisites
• The name of each virtual server must be unique within a single Hyper-V server.
• The Data Exchange service of the Hyper-V Integration Service on the target virtual server must be
enabled.
• If the network connection check is enabled, you must specify the address of the connection destination
for agentless monitoring. Make sure to specify a loopback address that can be resolved from the name
"localhost".
• If the network connection check is enabled, the firewall for the target virtual server must permit ICMP
(ECHO) replies.
Usage guidelines
• When the network connection check is performed, depending on the system environment, the task
might not be able to obtain all IP addresses immediately after the virtual servers are started. As a
result, even if all virtual servers are running, the plug-in osSendIcmp might not be able to confirm
network connection for all IP addresses (IPv4) set on the virtual servers, and the task might end
abnormally. To ensure that all IP addresses can be obtained, adjust the value (in seconds) of the
property hyperv.waitTime, which specifies the amount of time to wait between starting a virtual server
to obtaining an IP address.
• To perform the network connection check, make sure that the total length of the IP addresses (IPv4)
set for all NICs on a virtual server does not exceed 1,024 characters (The maximum length of one IP
address (IPv4) including the comma used as an address separator is 16 characters.). If the total length
exceeds 1,024 characters, an error might occur in the plug-in osSendIcmp, causing the task to end
abnormally.
• If you enable the network connection check, adjust the value of the property
common.icmpEchoTimeout based on your environmental requirements.
Service Definition Properties
The following table lists the properties shown in the Service Definition window.
Additional service templates 351