When installing Systemwalker Runbook Automation in an IPv6 environment, design the operation taking the following notes into consideration.
IPv6 addresses that can be used
Operation is possible using the following addresses:
Global unicast addresses
Unique local unicast addresses
Operation using link-local unicast addresses is not possible.
Operation is not supported for an environment where temporary addresses (privacy extensions) are enabled. Refer to the operating system manuals for information on temporary addresses (privacy extensions).
Operating environment
Operation is possible in the following operating environment.
The possible operating environment for Linked Servers, Relay Servers, and Development Computers are shown below. Operation is only possible by IPv4 address.
IPv4 single-stack environment | IPv6 single-stack environment | IPv4/IPv6 dual-stack environment | |
---|---|---|---|
Linked Servers | Y | N | N |
Relay Servers | Y | N | N |
Development Computers | Y | N | N |
Y: Operation is possible, N: Operation is not possible
The possible operating environment for Linked Servers, Relay Servers, and Development Computers are shown below. Operation is only possible by mixed IPv4 address and IPv6 address.
IPv4 single-stack environment | IPv6 single-stack environment | IPv4/IPv6 dual-stack environment | |
---|---|---|---|
Linked Servers | Y | Y | Y |
Relay Servers | Y | Y | Y |
Development Computers | Y | Y | Y |
Y: Operation is possible, N: Operation is not possible
Note
Operation is not possible when installing Management Server in an IPv6 single-stack environment
Notes for features
When using Systemwalker Runbook Automation features in IPv6 environments, take the following notes into consideration.
When configuration information is automatically collected and a node that has an IPv6 address is detected, configure the DNS server. Also, register the IPv6 address of the detected node on the DNS server.
When configuration information is automatically collected, IP addresses are stored in the RFC 5952 format in the Systemwalker Runbook Automation Configuration Management Database (CMDB).
When collecting configuration information in IPv4/IPv6 dual-stack environments, IPv4 address are preferentially stored by default. For how to store IPv6 address preferentially, refer to the "Definition File for Agent" in the Systemwalker Runbook Automation Reference Guide.
Use specified format when manually updating or registering the IPv6 address of the configuration information with the Configuration Management window or the ciimport command.
Refer to "Libraries Provided by the Product" in the Systemwalker Runbook Automation Reference Guide for information on the communication methods and libraries that can be used in IPv6 environments.