14.4.6 System configuration that supports IPv6 hosts
JP1/IM can manage JP1/Base running on IPv6 hosts. You can manage IPv6 hosts on which JP1/Base is running in the same way as IPv4 hosts on which JP1/Base is running. You can collect host information, manage profiles, execute commands, and display JP1 events for IPv6 hosts.
|
-
IPv6 host
Indicates a host with an IPv6 address.
-
IPv4 host
Indicates a host with an IPv4 address.
-
IPv4/IPv6 host
Indicates a host that has both the IPv4 and IPv6 addresses.
A network environment in which IPv4 hosts, IPv6 hosts, and IPv4/IPv6 hosts coexist is called an IPv6 environment.
As shown in the above figure, the viewer hosts and the manager host communicate with each other using IPv4 addresses. The agent hosts and the manager host communicate with each other using IPv4 or IPv6 addresses.
Examples of IPv4 and IPv6 addresses:
-
Example of an IPv4 address
11.22.33.44
-
Example of an IPv6 address
0011:2233:4455:6677:8899:aabb:ccdd:eeff
You cannot specify IPv4-mapped addresses and IPv4-compatible addresses. In addition, some functions do not support the abbreviated format of IPv6 addresses. For details about the functions for which the abbreviated format of IPv6 addresses can be specified, see 14.4.6(3) Functions supported in an IPv6 environment.
-
Example of 11.22.33.44 in IPv4-mapped address format:
::ffff:11.22.33.44
-
Example of 11.22.33.44 in IPv4-compatible address format:
::11.22.33.44
-
Example of 2012:0007:0008:0000:0000:0000:000a:000b in abbreviated IPv6 format:
2012:7:8::a:b
- Organization of this subsection
(1) Prerequisites for monitoring system configuration in an IPv6 environment
Prerequisites differ depending on the network environment for the manager host.
For cluster configuration, the system configuration of the primary node and the standby node must be the same.
(a) When the manager host is an IPv4 host
When the manager host is an IPv4 host, the manager cannot manage IPv6 hosts and IPv4/IPv6 hosts.
(b) When the manager host is an IPv6 host
An IPv6 manager host is not supported.
(c) When the manager host is an IPv4/IPv6 host
|
- Manager host
-
-
The host is an IPv4/IPv6 host.
-
The version of JP1/IM - Manager is 10-00 or later.
-
The version of JP1/Base is 10-00 or later, and jp1hosts2 information has been defined.
-
For the JP1/Base jp1hosts2 definition, the IPv4 address and IPv6 address of the manager host have been defined.
-
The OS is Windows Server 2022, Windows Server 2019, Windows Server 2016, or Linux.
-
- Viewer host
-
-
The host is an IPv4 host or IPv4/IPv6 host.
-
For JP1/IM - View running on an IPv4/IPv6 host, the IPv4 address is used.
-
- Agent hosts
-
-
The hosts are IPv4 hosts, IPv6 hosts, or IPv4/IPv6 hosts.
-
The version of JP1/Base is 10-00 or later.
-
For JP1/Base running on an IPv6 host or IPv4/IPv6 host, jp1hosts2 information has been defined.
-
For JP1/Base running on an IPv6 host or IPv4/IPv6 host, the OS is Windows Server 2022, Windows Server 2019, Windows Server 2016, or Linux.
-
- Remotely monitored hosts and virtualization system configuration
-
-
The host is an IPv4 host.
-
When you want JP1/IM - Manager to link with other products, it can link with products on IPv4 hosts. However, it cannot link with products on IPv6 hosts. The one exception is that JP1/IM - Manager can link with BJEX or JP1/AS on IPv6 hosts in order to manage response-waiting events.
(2) Maximum configuration of the JP1/IM - Manager system for managing an IPv6 environment
The number of agent hosts that can be managed by one JP1/IM - Manager does not depend on whether the agent hosts are IPv4 hosts, IPv6 hosts, or IPv4/IPv6 hosts.
For details about the maximum system configuration, see D.4(1) JP1/IM - Manager limits.
(3) Functions supported in an IPv6 environment
The following describes the functions supported in an IPv6 environment when the version of JP1/IM - Manager is 10-00 or later.
(a) Login
You cannot specify an IPv6 address for the name of a host used for remote login. Specify an IPv4 address or a host name for which an IPv4 address can be resolved.
(b) Event monitoring
You can display and specify JP1 events whose source IP address (B.SOURCEIPADDR) or destination IP address (B.DESTIPADDR) is an IPv6 address.
- Event filtering
-
For a condition of the JP1 event to be filtered, you can specify the source IP address (B.SOURCEIPADDR) in IPv6 format. You can specify the source IPv6 address for the event acquisition filter (common exclusion-conditions in extended mode). For an event condition, you can specify an IPv6 address by using four-digit hexadecimal numbers (0-9 and a-f) as follows:
Example: 0011:2233:4455:6677:8899:aabb:ccdd:eeff
You cannot use upper-case characters, and cannot specify an IPv4-mapped address, IPv4-compatible address, or abbreviated format IPv6 address.
Also, in the Common Exclusion-Condition Settings (Extended) window, if you click the Read From Selected Event button, the source IP address of the JP1 event selected in the event list is automatically set for the event condition. However, if the version of JP1/IM - View is earlier than 10-00 and the source IP address in the common exclusion-condition is an IPv6 address, the source IP address is not automatically set even if you click the Read From Selected Event button in the Common Exclusion-Condition Settings (Extended) window. In that case, manually specify an IPv6 address for the filter condition. When you manually specify an IPv6 address for the filter condition, follow the specification format for an event condition regardless of the version of JP1/IM - View.
Note that the destination IP address (B.DESTIPADDR) cannot be specified for a filter condition in the same way as when IPv4 addresses are managed.
- Display of event details
-
In the Event Details window and the Edit Event Details window, you can display the source IP address (B.SOURCEIPADDR) in IPv6 address format in the Event attributes field. An IPv6 address is specified with four-digit hexadecimal numbers (0-9 and a-f) as follows:
Example: 0011:2233:4455:6677:8899:aabb:ccdd:eeff
Note that the destination IP address is not displayed in the same way as when IPv4 addresses are managed. If the version of JP1/IM - View is earlier than 10-00, the source IP address and the destination IP address are not displayed in the Event attributes field regardless of whether those addresses are IPv4 addresses or IPv6 addresses.
- Display of event guide
-
For a condition for comparing JP1 events, you can specify an IPv6 address for the source IP address (B.SOURCEIPADDR) or the destination IP address (B.DESTIPADDR). You cannot specify the source IP address and the destination IP address for variables for an event guide message. (This is also true for IPv4 addresses.)
- Event search
-
You can specify an IPv6 address or a host name that can be resolved to an IPv6 address for the search host.
For the search host, you can specify IPv6 addresses in the following formats:
-
Four-digit hexadecimal (0-9 and a-f)
Example: 0011:2233:4455:6677:8899:aabb:ccdd:eeff
-
Four-digit hexadecimal (0-9 and A-F)
Example: 0011:2233:4455:6677:8899:AABB:CCDD:EEFF
-
Abbreviated IPv6
Example: 2012:7:8::a:b
If restrictions are set on viewing and operating business groups, specify the host name (domain name) managed by IM Configuration Management. To specify a manager host for the search host, specify the host name or IPv4 address of the manager host.
-
- Event report output
-
You can output JP1 events in which an IPv6 address is specified for the source IP address (B.SOURCEIPADDR) or the destination IP address (B.DESTIPADDR) to a csv file. IPv6 addresses are output to a csv file as sequences of four-digit hexadecimal numbers (0-9 and a-f) as follows:
Example: 0011:2233:4455:6677:8899:aabb:ccdd:eeff
For the output items and event conditions of a report, you cannot specify the source IP address and the destination IP address. (This is also true for IPv4 addresses.)
- Handling status change
-
When executing the jcochstat command to change the handling status, you cannot specify an IPv6 address for the -h option.
- Issuance of correlation events
-
The source IP address and the destination IP address for correlation events are the IPv4 address of the manager host.
(c) Command execution and automated action
You can execute commands or automated actions on IPv6 managed hosts. For the target host name, you can specify IPv6 addresses in the following formats:
-
Four-digit hexadecimal (0-9 and a-f)
Example: 0011:2233:4455:6677:8899:aabb:ccdd:eeff
-
Four-digit hexadecimal (0-9 and A-F)
Example: 0011:2233:4455:6677:8899:AABB:CCDD:EEFF
-
Abbreviated IPv6
Example: 2012:7:8::a:b
If you specify a value that cannot be specified in JP1/Base, the execution fails. If restrictions are set on viewing and operating business groups, specify the host name (domain name) managed by IM Configuration Management.
- Conditions for executing an automated action
-
For the conditions for executing an automated action, you can specify the source IP address (B.SOURCEIPADDR). You cannot specify the destination IP address (B.DESTIPADDR). (This is also true for IPv4 addresses.) Specify the source IP address with four-digit hexadecimal numbers (0-9 and a-f) as follows:
Example: 0011:2233:4455:6677:8899:aabb:ccdd:eeff
You cannot use upper-case characters, and cannot specify an IPv4-mapped address, IPv4-compatible address, or abbreviated IPv6 address.
- Inheritance of event information to command execution and automated action
-
The attribute information of a JP1 event in which an IPv6 address is specified for the source IP address (B.SOURCEIPADDR) can be inherited to command execution contents. The variables EVIPADDR (source IP address) and EVBASE (basic event information) can be inherited. The IPv6 address is output to the command execution contents as four-digit hexadecimal numbers (0-9 and a-f) as follows:
Example: 0011:2233:4455:6677:8899:aabb:ccdd:eeff
The attribute information of the destination IP address (B.DESTIPADDR) cannot be inherited. (This is also true for IPv4 addresses.)
- Acquiring the event source host name
-
You can acquire the event source host name from the source IP address (B.SOURCEIPADDR). This method is also available when the source IP address is an IPv6 address.
For details about how to acquire the event source host name, see Automated action environment definition file (action.conf.update) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.
Note that the value of the source IP address is not guaranteed after it is forwarded. For details, see the description of basic attributes in the JP1/Base User's Guide.
(d) IM Configuration Management
You can manage IPv6 agent hosts. You can collect and manage host information or manage JP1/Base profiles on IPv6 hosts.
You cannot manage remotely monitored IPv6 hosts.
(e) Linked products
- Launch of a linked product by monitor startup
-
You can launch a monitor window of a linked product from a JP1 event in which an IPv6 address is specified for the source IP address (B.SOURCEIPADDR) or the destination IP address (B.DESTIPADDR). If you monitor a system in which IPv4 hosts and IPv6 hosts coexist, however, check the specification of the linked application. Note that you cannot specify the source IP address and the destination IP address for the subkey definition nor for the call interface definition in the definition file for opening monitor windows. For details about the definition file for opening monitor windows, see Automated action environment definition file (action.conf.update) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.
- Registering incidents
-
You can register into JP1/Service Support a JP1 event whose source IP address (B.SOURCEIPADDR) or destination IP address (B.DESTIPADDR) registered in the manager host's event database or integrated monitoring database is an IPv6 address. However, attribute information for the source IP address and destination IP address cannot be set in an incident that is registered into JP1/Service Support.
(f) Web browser
You cannot specify an IPv6 address for the name of the host that the Web browser connects to.
(g) Email notification function
An IPv6 address cannot be specified as the IP address of a mail server that communicates with the email notification function.
(4) Items to be checked when the system configuration is changed
(a) Items to be checked when the manager host is changed from an IPv4 host to an IPv4/IPv6 host
-
Check whether the OS on the manager host supports IPv6 addresses.
-
Check whether JP1/Base on the manager host supports IPv6 addresses.
-
Check and, if necessary, change the connection target host so that the IPv4 address of the connection target host can be acquired on the viewer host when logging into JP1/IM - Manager.
(b) Items to be checked when a monitored host is changed from an IPv4 host to an IPv6 host
-
Check whether the OS on the monitored host supports IPv6 addresses.
-
Check whether JP1/Base on the monitored host supports IPv6 addresses.
-
When filtering events, if the source IP address (B.SOURCEIPADDR) is specified in the event acquisition filter (common exclusion-condition in the extended mode), check the settings of the common exclusion-conditions to determine whether IPv6 address filtering is required.
-
When searching events, check whether the manager host and the search host with an IPv6 address can communicate using IPv6 protocol.
-
When changing the handling status, check and, if necessary, change the connection target host so that the IPv4 address of the connection target host can be acquired on the host on which the jcochstat command is executed.
-
When the attribute information of the source IP address (B.SOURCEIPADDR) is inherited by command execution and automated actions, confirm that there is no problem if an IPv6 address is inherited as attribute information.
-
When a source IP address is specified for the execution conditions for automated actions, check the execution conditions to determine whether IPv6 address filtering is required.
-
When local is specified as the method for acquiring the event source host name, check whether name resolution of a host with an IPv6 address is required.
(c) JP1/Base settings
For details about the items to be checked, see the JP1/Base User's Guide.
(5) Changing system configuration
(a) Changing the manager host from an IPv4 host to an IPv4/IPv6 host
-
JP1/Base
Move from jp1hosts information to jp1hosts2 information. For details about the procedure, see the JP1/Base User's Guide.
-
JP1/IM - Manager
You do not have to change anything.
(b) Changing a monitored host from an IPv4 host to an IPv6 host
-
JP1/Base on the monitored host
Overwrite install JP1/Base to version 10-00 or later.
Then, move from jp1hosts information to jp1hosts2 information. For details about the procedure, see the JP1/Base User's Guide.
-
Manager host
You need to configure the manager host to use IPv6. For details about the procedure, see 14.4.6(5)(a) Changing the manager host from an IPv4 host to an IPv4/IPv6 host.