How to Configure and Verify OmniWatch Connectivity. Overview. Resolution

Size: px

Start display at page:

Download "How to Configure and Verify OmniWatch Connectivity. Overview. Resolution"

Lora West
5 years ago
Views:

1 How to Configure and Verify OmniWatch Connectivity How To#: Title: How to Configure and Verify OmniWatch Connectivity Table of Contents Overview Resolution OmniWatch Agent Utility System Requirements Test OmniWatch Agent Connectivity Configure the OmniWatch Agent to Communicate with a Proxy Server Customer Support Reconfigure the OmniWatch Agent Check the Settings Article Information Properties Server Platform: All server platforms OmniStack Software Version: v2.1.4 and later Information Level: 1 Date Created: Tuesday, September 13, 2016 Date Revised: Friday, May 26, 2017 Overview OmniWatch agent is SimpliVity's proactive support solution for nodes in your federation running OmniStack. OmniWatch agent gathers and transmits monitoring data about your federation and transmits that data efficiently and securely to OmniWatch, the SimpliVity remote monitoring service. The OmniWatch agent, which runs on the OmniStack Virtual Controllers (OVC) in your federation, requires network connectivity between the OVCs and the SimpliVity Cloud. SimpliVity provides a support utility that allows you to check if there is connectivity between the OVCs and the SimpliVity Cloud. Also, if your federation network is using a proxy server to allow external network communication, you can use this utility to configure the OmniWatch agent with the proxy server. This article explains how to use the support utility for these purposes. Resolution Download the OmniWatch agent utility to a Windows computer on your network. OmniWatch Agent Utility System Requirements To run the support utility from your Windows computer, your computer must meet the following system requirements: 1. Network access on port 22 to all the OVCs that are being tested or updated 2. Windows Management Framework 4.0 or later 1

3. Microsoft.NET Framework 4.5 or later Test OmniWatch Agent Connectivity To test the connectivity status of the OmniWatch agent on an OVC, follow this procedure. 1.

$the utility. 2. Enter the following information, and click Login. a. vsphere Username vsphere Administrator account (domain\username) b.$

2 3. Microsoft.NET Framework 4.5 or later Test OmniWatch Agent Connectivity To test the connectivity status of the OmniWatch agent on an OVC, follow this procedure. 1. Right-click the SupportAgentProxy_v1.3.0.exe file, and click Run as administrator from the pop-up menu. If you receive the following warning message regarding the required Windows Management Framework software version, install the required software version, restart Windows, and rerun the utility. 2. Enter the following information, and click Login. a. vsphere Username vsphere Administrator account (domain\username) b. vsphere Password Password for the vsphere account c. OmniStack Virtual Controller (OVC) IP Address Any OVC Management IP address in the Federation 2

3. After you log in, all online OmniStack nodes in the Federation are populated on the left-hand side of the screen. Select the nodes to be tested. 4. Click Test SimpliVity Cloud Connection. 5.

3 3. After you log in, all online OmniStack nodes in the Federation are populated on the left-hand side of the screen. Select the nodes to be tested. 4. Click Test SimpliVity Cloud Connection. 5. After all selected nodes have been tested, the results from each node display at the bottom of the screen. If the OmniWatch Agent is unable to communicate with the SimpliVity Cloud, ensure the OVC Management IP address is able to communicate through the network with simplivity.axeda.com on port

Configure the OmniWatch Agent to Communicate with a Proxy Server To configure the OmniWatch agent to communicate with a proxy server, follow this procedure: 1.

4 Configure the OmniWatch Agent to Communicate with a Proxy Server To configure the OmniWatch agent to communicate with a proxy server, follow this procedure: 1. Log in to the support utility using the steps in the previous procedure. 2. Select the nodes you want to configure with the proxy server. 3. Enter the following proxy information and click Update to configure the proxy server for each selected node. a. Proxy Server the URL or IP of the network proxy server b. Proxy Port the proxy port to use with the proxy server c. Proxy Username and Password Username and password to access the proxy server. These fields are optional and not required if your proxy server doesn't require authentication. 4. If your network previously used a proxy server but it is no longer in use, select Disable Proxy to remove the proxy server from the configuration. 5. After all selected nodes have been configured, the results from each node display at the bottom of the screen. 4

5 6. After the nodes are successfully configured, wait 3 minutes and then click Test SimpliVity Cloud Connection to ensure the proxy settings are working. Customer Support Reconfigure the OmniWatch Agent 1. Log on to the OmniStack Virtual Controller (OVC) and elevate to root, then change to axeda user. # sudo su axeda 2. Change directory to the configuration directory: # cd /var/svtfs/axeda 3. Run the DeployConfig command to configure the network proxy: # /opt/axeda/deployconfig -home /var/svtfs/axeda -model "Virtual Controller" -serial <serial> -host simplivity.axeda.com -port 443 -ssl -http-proxy-host <proxy_server> -http-proxy-port <proxy_port> [-http-proxy-user <user> -http-proxypass <pass>] Where: If the proxy server requires a user name and password, add the following options to the DeployConfig command above: -http-proxy-user <username> -http-proxy-pass <password/></username> 1. <serial> is the serial number of the host (such as: EG45YZ1-VC).</serial> 2. <proxy_server> is the URL or IP of the network proxy server.</proxy_server> 3. <proxy_port> is the proxy port to use with the proxy server.</proxy_port> 4. The DeployConfig utility does not generate the xgdeployconfig.xml file correctly. This is a known defect. Run the following command to fix the file. # cat xgdeployconfig.xml sed -e 's/certificate="true"/certificate="false"/' > xgdeployconfig.xml.new # mv xgdeployconfig.xml.new xgdeployconfig.xml 5

6 5. Use the EProtect utility to regenerate the sign the xgdeployconfig.xml file. # /opt/axeda/eprotect -home /var/svtfs/axeda -target DeployConfig -mac -stdin <./xgdeployconfig.xml > xgdeployconfig.dat 6. Type exit to become root user. # exit 7. Restart the OmniWatch agent: # restart svt-axeda Check the Settings 1. Verify the OmniWatch agent status: # ps el grep xgate 2. Check the log for any errors connecting to the Axeda cloud server: /var/log/axeda/xgate.log 3. If there are errors, verify that the proxy host and port are correct in: /var/svtfs/axeda/xgdeployconfig.xml Article Information Article Author: Tim Fisher Article approved by: Jason DePardo Approval date: 2016/09/13 PIR approval date: 2016/09/13 Specify the information level: 1 Customers 6

Corrective Action for Failures with Either ESXi Host or vcenter Credentials

Corrective Action for Failures with Either ESXi Host or vcenter Credentials How to Update Identitystore How To#: 11753 Title: How to Update Identitystore Table of Contents Overview Resolution IdentityStore Update Utility System Requirements Verify IdentityStore Credentials Update