The Advisor can use multiple TCP/IP stacks in a CINET environment. The addresses specified in the lb_connection_v4 and lb_connection_v6 statements can belong to different TCP/IP stacks. Moreover, because the socket that listens for Agent connections uses the IPv4 or IPv6 unspecified address, the TCP/IP stack or stacks that incoming Agent connections use depends upon the IP addresses specified in the Agents' agent_id_list statements. To simplify your configuration and to make Advisor outages that are the result of a TCP/IP stack failure or termination more predictable and recoverable, all incoming connections to the Advisor should use a single TCP/IP stack. Therefore, the addresses you specify in the lb_connection_v4 and lb_connection_v6 statements should belong to the same TCP/IP stack, and you should configure all load balancers and Agents to use these same IP addresses when connecting to the Advisor. The addresses you specify should be dynamic VIPAs to enable the movement of the Advisor in case of failure. This implies that these dynamic VIPAs should be defined in the TCP/IP profiles of all the stacks using a VIPARANGE statement. If the Advisor is restarted as a result of failure in a given TCP/IP stack, the dynamic VIPAs are then activated on another TCP/IP stack in that system. If you decide to use the IPv4 or IPv6 unspecified addresses for the lb_connection_v4 and lb_connection_v6 statements, you should use the BIND parameter on the PORT reservation statement to bind these sockets to the dynamic VIPA on the one TCP/IP stack you have decided to use.