Restart the Symantec Critical System Protection Server service. Follow the same instructions as for the agent connectors.Ħ. Inside the console service tag (look for ), there is a similar SSL connector and commented non-SSL connector. In server.xml, define the SSL connection in the console service tag. To conserve resources, it is not recommended to leave both connectors uncommented unless you need to use both SSL and non-SSL communications.Ĥ. The port that you specify must not be in use by any other programs on the system. To enable non-SSL connections, uncomment the second connection, and change its port number if desired.
Immediately following this is a commented definition for a non-SSL connection. In the Navigator on the left hand side, select Time.
Inside the agent service tag (look for ), a Connector tag defines the default SSL connection. The change can’t be made from logging into the normal vCenter Server Appliance web client you would use for managing the cluster, you have to log directly into the vCenter appliance. In server.xml, define the SSL connection in the agent service tag. Using Notepad or other text editor, edit server.xml.ģ. In the New Server Configuration dialog, clear the Use encrypted communications check box.Ģ. To define the SSL connections in server.xmlġ. The server.xml file is located in the following directory: If you do not want to use SSL X.509 certificate-based channel encryption for Symantec Critical System Protection, you must define the SSL connections in the server.xml file, found on the management server. SSL X.509 certificate-based channel encryption secures communication between the management console and the management server, and between the agent and the management server. You should now be able to successfully contact VMware via the proxy to check for any updates that are available to your vCSA.Defining the SSL connections in server.xml When the vCSA has rebooted log back in to the GUI and check the correct proxy settings are now shown.Ĩ. With the file saved all that is left to do is reboot the appliance, this can be done direct from the putty window or via the GUI.ħ. Once you have navigated to this location open the proxy file with the vi text editor and modify the values shown to match your required proxy settings, don't forget to overwrite the file with "escape, :wq!"Ħ. We now need to find the config file that contains the proxy information presented within the GUI, this can be found under /etc/sysconfig/proxyĥ. Open your SSH Client of choice (I use putty) and connect using the root account to the vCSA, once at the Command prompt type "shell" and hit enterĤ. (Obviously attempt entering the require proxy setting here first as it should work fine, however if you know your details are correct and are still presented with an "error connecting to proxy" or "proxy unreachable" then proceed with the remaining steps)ģ. Under the Networking tab check all proxy settings are configured to disabled. Log in to the GUI and ensure the option for SSH under the Access tab is EnabledĢ.Here is how I manged to work around the issue both for the 6.5 and 6.7 vCSA.
Find service tag from vcenter 6.5 windows#
Having recently moved six vCenter Servers over from Windows to the VMware appliance I ran into an issue with configuring the proxy settings from the GUI to allow the appliance to check for updates online.