Updating the network configuration of Cluster Control Manager and cluster nodes

Last Updated : Jul 13, 2022 |
Prolog information
Metadata
Keywords:
Use this procedure to update the network-related settings of Cluster Control Manager and the cluster nodes:
  • CCM network settings:
    • Host Fully Qualified Domain Name (FQDN)
    • Network domain search list
    • Public interface
      • IP address
      • Netmask
      • Gateway IP address
    • Primary Domain Name Server (DNS) server IP address
    • Secondary Domain Name Server (DNS) server IP address
    • Time zone and date format
    • Turn on or off the Network Time Protocol (NTP) server
    • IP/FQDN of primary NTP Server
    • IP/FQDN of secondary NTP Server
  • Cluster node settings
    • Cluster node primary DNS server IP address
    • Cluster node secondary DNS server IP address
    • Network domain search list
    • IP/FQDN of cluster node primary NTP Server
    • IP/FQDN of cluster node secondary NTP Server
    • Time zone
Before you begin
  • Perform a full backup of Common Services and application data.
  • If you are changing the hostname or FQDN:
    • If Cluster Control Manager currently has a third-party signed identity certificate, you must have an updated identity certificate for Cluster Control Manager with the new hostname or FQDN.
    • Make sure the new hostname or FQDN is updated on your DNS with the correct Cluster Control Manager IP address.
  • If you are changing the IP address:
    • Make sure the new IP address is updated on your DNS with the Cluster Control Manager FQDN.
    • Make sure the new IP address is compatible with the current/new gateway and netmask.
  1. Log in to Cluster Control Manager.
  2. Run the ccmNetSetup command.
    ADDITIONAL INFORMATION:
    At each step you can choose to change a value or keep the current value.
    Note:
    When changing the Cluster Control Manager IP address, netmask, and gateway IP address, make sure the new values work on the network where Cluster Control Manager is currently connected. If any of the values are not properly configured, you might lose connectivity to the Cluster Control Manager. If you do, you will need to log into the Cluster Control Manager console via vCenter and run this command again with the correct values.
  3. If you changed the Cluster Control Manager hostname or FQDN:
  4. If you are using a third-party signed certificate for Cluster Control Manager, upload the new identity certificate with the updated FQDN to the Certificate Manager running in the cluster.
    ADDITIONAL INFORMATION:
    Upload this certificate only after you run the ccmNetSetup command.
  5. Complete the Product Initial Registration process again.