Previous Topic: Error Messages Appear in pdm_tomcat_REST.log During REST Web Services DeploymentNext Topic: PKI Login Fails with CA Workflow Configuration on AIX


IPV6 Address Fails to Connect

Valid on all operating systems

Symptom:

A primary or secondary server is configured for either mixed mode or IPV6-only mode and the browser or standard logs show connection failure messages.

Solution:

Verify that the primary server, secondary server, or client can resolve the IPV6 address by name. Verify that the CA SDM address is a valid IPV6 address. For example, the IPV6 address is a routable IPV6 global address instead of an unrouted FE80 address.

To resolve IPV6 address connection issues on the servers or clients, do the following:

  1. On the primary or secondary server, run the following CA SDM Java 1.7 command-line utility:
    java -cp $NX_ROOT/java/lib/checkprotocols.jar com.ca.ServicePlus.ipv6.tools.getByAddress [address] [slump_port] [protocol]
    

    For example, to obtain IPV4 addresses for the Sd16 node, enter java –cp $NX_ROOT/java/lib/checkprotocols.jar com.ca.ServicePlus.ipv6.tools.getByAddress Sd16 2100 IPV4.

    address/node

    Specifies the named address/node name of the primary or secondary server (either local or remote).

    slump port

    Specifies the TCP slump port number. For example, 2100.

    protocol

    (Optional) Specifies the IPV4 or IPV6 protocol. When you omit the protocol, the default supplies both IPV4 and IPV6 addresses.

    The utility lists information for the specified server node.

  2. Use the data from the command line utility to verify that the routable CA SDM addresses are correct and are the same addresses that are on the DNS or name resolving servers entries.
  3. If the addresses still do not resolve, specify the local and remote addresses for the CA SDM servers in one of the following files:

    Note: Use the server information from the command line utility to update the hosts file. Follow the instructions in the hosts file to add the CA SDM server node names.

  4. If remote clients cannot connect to CA SDM, do one or more of the following: