Use the lb_connection_v6 statement to specify the IPv6 address and port the Advisor should listen on for IPv6 connections from load balancers.
This statement is optional. However, if neither an lb_connection_v4 nor an lb_connection_v6 statement is present in the configuration file, a terminating error results.
Syntax
.-..3860------. >>-lb_connection_v6 --host_ipaddr--+-------------+------------->< '-..host_port-'
Parameters
- host_ipaddr..host_port
- Use host_ipaddr..host_port to specify
which IPv6 address and optionally the port the Advisor listens on
for IPv6 connections from a load balancer. This address and port
must be coordinated on any load balancers that wish to connect to
this Advisor. The port is optional and defaults to 3860.
Rule: There should be no spaces between the IP address, the two ellipses (..) and the port. The host_ipaddr..host_port pair must be specified on one line. It cannot be continued to a subsequent line.
The valid range of port values is 1 - 65 535.
Guideline: For higher availability, specify a unique application-instance DVIPA.
Restrictions:- If the host where the Advisor is running has only a single interface IP address, do not specify the same port on the agent_connection_port and lb_connection_v4 or lb_connection_v6 statements. Having only a single IP address means both the z/OS® Load Balancer and the Agent would need to be configured with that address, and both would end up connecting to the Advisor's socket for z/OS Load Balancer connections.
- In general, most IPv6 listening sockets accept IPv4 connections if the listening socket is using the IPv6 unspecified address (::). However, for this listening socket, only IPv6 connections are accepted, even if you use the IPv6 unspecified address. If you expect to receive IPv4 connections from load balancers, you must specify the lb_connection_v4 statement.