1.4.3 Changing the IP Address of Access Gateway Appliance

To change the IP address of Access Gateway, you need to configure Access Gateway for this change. This is especially significant when Access Gateway Appliance has only one IP address.

IMPORTANT:The new IP address must be configured in Administration Console before you change it on Access Gateway. If you change the address on Access Gateway first, Administration Console does not trust Access Gateway and cannot establish the communication.

  1. Click Devices > Access Gateways > Edit > Adapter List.

  2. (Conditional) If the machine belongs to a cluster, select Access Gateway from Cluster Member.

  3. From the Adapter List, select the subnet mask that contains the IP address you want to change.

  4. Select the old IP address, click Change IP Address, specify the new IP address, then click OK.

    This option changes all configuration instances of the old IP address to the new IP address. For example, any reverse proxies that have been assigned the old IP address as a listening address are modified to use the new IP address as the listening address.

  5. Click OK.

  6. To apply your changes, click the Access Gateways link, then click Update > OK.

  7. If you are physically moving the machine, move it before completing the rest of these steps.

  8. Check the IP address that Administration Console uses for managing Access Gateway. Click Access Gateways > [Name of Access Gateway] > Edit.

  9. If the old IP address is listed as the Management IP Address, select the new IP address. If your Access Gateway has multiple IP addresses, select the one that you want Administration Console to use for communication with Access Gateway.

    The port must only be modified if there is another device on Access Gateway that is using the default port of 1443.

  10. If the name of Access Gateway is the old IP address, modify the Name option.

  11. Click OK.

    Administration Console uses the configured IP address to find Access Gateway.

  12. On the Access Gateway server, restart Tomcat:

    /etc/init.d/novell-mag restart OR systemctl restart -mag

    For the Docker deployment, perform the following steps:

    1. Run the kubectl get pods command to view the Access Manager pods.

    2. Go to the Access Gateway pod by running the kubectl exec --namespace <name-of-the-namespace> -it pod/<name-of-the-access-gateway-pod> -- sh command.

    3. Run the /etc/init.d/novell-mag restart or systemctl restart -mag command.

If your Access Gateway stops reporting to Administration Console after completing these steps, trigger an auto-import. See Triggering an Import Retry in the NetIQ Access Manager 5.0 Installation and Upgrade Guide.