The Broker can support IPv4 and IPv6 protocols. If the component applications in your deployment are identified by IPv4 and IPv6 addresses, the Broker must reside on a dual-stack host so that it has both an IPv4 address and an IPv6 address.

If all component applications in your deployment use the same IP protocol version, the Broker must reside on a host with an IP address that accepts that protocol version. For example, if all component applications in your deployment support the IPv6 protocol, the Broker must reside on a host with an IPv6 address. That host may be dual-stack or IPv6-only.

Broker and server-to-server communications are also controlled by the SM_IP_VERSIONS environment variable. If all component applications in your deployment are communicating with the same IP protocol version, the SM_IP_VERSIONS variable should be set to the same value in each component application’s BASEDIR/smarts/local/conf/runcmd_env.sh file. In an IPv6-only environment, for example, the SM_IP_VERSIONS environment variable should be set to v6 or v6v4, as shown in IPv6-only environment example and variable settings.

Table 1. IPv6-only environment example and variable settings

SM_IP_VERSIONS setting

Product suite

Components

SM_IP_VERSIONS=v6-or-SM_IP_VERSIONS=v6v4

IP Manager version 9.1

  • IP Availability Manager

  • IP Performance Manager

  • IP Server Performance Manager

  • IP Availability Manager Extension for NAS

VMware Smart Assurance IP Manager User Guide provides information for setting the SM_IP_VERSIONS environment variable for IP Manager components.

SM_IP_VERSIONS=v6-or-SM_IP_VERSIONS=v6v4

Service Assurance Manager version 9.1

  • Global Manager

  • Global Console

  • Adapter Platform

  • SNMP Trap Adapter

The VMware Smart Assurance Service Assurance Manager Configuration Guide provides information for setting the SM_IP_VERSIONS environment variable for Service Assurance components.

SM_IP_VERSIONS=v6-or-SM_IP_VERSIONS=v6v4

Either suite listed above

Broker