Administrators can send a request to add the appliance to the Central Management System appliance. A rendezvous process enables the appliance to attempt the request and allows the Central Management System administrator to see the list of pending requests.
Requirements for establishing a successful connection
To send a management request and successfully establish and maintain the connection, the following must be in place:
Automatic rendezvous attempts are enabled on the requesting Intelligent Virtual Execution - Server appliance (disabled by default).
The auto connect feature is enabled on the requesting Intelligent Virtual Execution - Server appliance so it automatically tries to connect to the Central Management System appliance after the rendezvous attempt succeeds (enabled by default).
Note
See Preparing an Intelligent Virtual Execution - Server appliance to send a management request in a NAT deployment to verify and enable these settings.
The Intelligent Virtual Execution - Server appliance has a unique and permanent hostname. Pending requests from appliances with the same hostname or IP address will be rejected. If the hostname is changed, the connection will be broken and cannot be reset. If this happens, the appliance must be removed from the Central Management System appliance and then added again using the new hostname.
The Central Management System appliance and the Intelligent Virtual Execution - Server appliance have the same rendezvous service name. The rendezvous process has an identifier (known as service name) that is set to "cmc" by default. The Central Management System appliance and the requesting appliance must have the same service name; if you change the service name on one, you must change it on the other as well. The
cmc rendezvous service-name <hostname>command changes the service name; theno cmc rendezvous service-namecommand restores the default value. For details, see the CLI Command Reference.Important
Appliance-initiated connections are not supported in Central Management System high availability (HA) deployments.
Prerequisites
Operator or Admin access
Network address translation (NAT) mapping, as described in Address mapping
If the requesting appliance is behind a NAT gateway: The virtual NAT address and port that map to the requesting appliance internal IP address and SSH port
If the Central Management System appliance is behind a NAT gateway:
The virtual NAT address and port that map to the Central Management System internal IP address and SSH port
One of the following:
The accessible Central Management System IP address and port, described in Configuring and activating an accessible DTI server address
Single-port communication enabled on the appliance, described in Changing the address type for DTI network service requests