1.4.2 Notes on monitoring in an IPv6 network environment
This subsection presents notes on performing monitoring in an IPv6 network environment.
- Organization of this subsection
(1) Monitoring processes and services
APM does not support IPv6. Therefore, processes and services on monitoring servers in IPv6 networks cannot be monitored.
(2) Notes on IP addresses of monitoring servers
If you use an IPv6 address to specify a monitoring server via the GUI or a command, make sure that the address conforms to the IPv6 notation defined in RFC 2373. You cannot specify IPv4-compatible IPv6 addresses, link-local addresses, or multicast addresses.
(3) Notes on site-local addresses
Site-local addresses that have a scope ID are not supported. If a site local address that has a scope ID is specified, the scope ID (% + scope ID) is ignored.
(4) IPv6 addresses output to commands, windows, and definition files
The following explains the format of IPv6 addresses that are output to commands, windows, and definition files:
-
Eight groups of 2-byte (16-bit) hexadecimal values delimited by colons (:).
-
All hexadecimal alphabetic characters are output in lowercase.
-
The leading 0s of a 2-byte hexadecimal number are omitted. However, a 2-byte hexadecimal that consists of all 0s is output as 0.
-
Even in the case of consecutive 2-byte hexadecimal numbers that consist of all 0s, the abbreviation :: is not used.
-
If the last 32 bits of an IPv6 address indicate an IPv4 address, the IPv4 address is output with hexadecimal numbers rather than decimal numbers.
For example, rather than 2001:db8::5efe:1.2.3.4, 2001:db8:0:0:0:5efe:102:304 is output.
-
IPv4-mapped IPv6 addresses are output as IPv4 addresses.
The following IPv6 addresses are all displayed as 2001:db8:0:0:1:0:0:1.
-
2001:db8:0:0:1:0:0:1
-
2001:0db8:0:0:1:0:0:1
-
2001:db8::1:0:0:1
-
2001:db8::0:1:0:0:1
-
2001:0db8::1:0:0:1
-
2001:db8:0:0:1::1
-
2001:db8:0000:0:1::1
-
2001:DB8:0:0:1::1