If the Linux access node is available in the list of access node or preferred node for guest file restores in hypervisor details, then you can ignore the following procedure. If not, the access node might have failed to register with the vCenter.
Procedure
-
Turn ON the Linux access node and verify the connection to the vCenter.
-
Open a command line and run the /var/log/init_client.log command.
-
Verify connection between the CommServe server and the access node.
-
If incorrect information is entered for the OVF template deployment (for example, a CS user name with insufficient privileges), then the /var/log/init_client.log file on the access node includes the following lines:
Client failed to register. Please view /var/log/commvault/SimCallWrapper.log for more details.
Note
The init_client.log file is in the /var/log/ directory on the access node. All the other log files can be found in the /var/log/commvault/Log_Files/ unless you specified a different log file folder during installation.
Perform the following additional steps in the vSphere Client:
-
Turn OFF the access node.
-
Go to Edit Settings to modify the properties.
-
On the vApp Options tab in the vSphere Web Client (or Options tab in the vSphere Client), verify and modify the OVA properties.
-
Turn ON the access node.
If the OVA properties specified are correct, the OVA registration will be successful.
-