Adding Non-Discoverable Endpoints

You can add non-discoverable (non-vSphere, non-EC2) endpoints to JetPatch server from either the JetPatch server or from the Endpoint itself.

From the JetPatch Console

To add an endpoint:

1. In the Servers tab, go to Server Actions > Add Physical Server:

   

2. Configure the following:

   

   • The endpoint's Hostname and IP Address
   • The endpoint's Operating System
   • Access Credentials: If the credentials to this endpoint have already been provided, you can assign them to the endpoint here. Otherwise, you can do this later.
3. Click Save.
4. Configure endpoint user accounts.

Newly-added endpoints appear in the endpoint list with the initial status of Untested. Upon first vAgent deployment or upon a manual Refresh status from the Servers tab, the connection status will be updated and JetPatch server will attempt to install the connector on the machine.

-- 

From the Endpoint

You can locally install the connector on any endpoint server. This is useful for connecting servers which are not otherwise accessible to the management server, and also for adding the connector to a base image that will be used to spawn multiple servers later.

To install the connector on a supported endpoint:

1. Make sure organizational firewalls allow HTTPS (port 443) communication from the endpoint to the JetPatch server.
2. Copy the Connector installation file (can be found in the JetPatch server file system in /usr/share/intigua/bin/)
   For Windows - vlink-win-win32_x64-<version>.exe
   For Linux - vlink_installer_linux_x64_<version>_Release.bsx
   into the endpoint.
   • For Windows put the file in a tmp or download directory
   • For Linux put the installation file in /tmp
3. On the endpoint, run the following command (make sure to copy all quote signs and slashes correctly):

   <connector> -coreserverurl="https://<host>/vmanage-server/"

   where

   <connector> is the path and filename of the connector file executable, and

   <host> is the IP address or DNS Name of the server host.

   For example:

   vlink-win-win32_x64-Release-3.2.exe -coreserverurl="https://<host>/vmanage-server/"

   After that, the connector is installed and initiates communication with the JetPatch server.  If the coreserverurl needs to be modified, see article.  If there are still issues, generate connector logs from the endpoint.

1. To test that the connector has been properly installed, check that the service is running:
   • In Windows:
     • Service name: vAgentManager
     • Display Name: Intigua vAgentManager Service
     • Process name: vlinkservice64.exe
   • In Linux, run:
     • /etc/init.d/intigua status

When installing the connector as part of creating a base image, some cleanups should be made before snapshotting the base image. Stop the service, and delete the following files:

• Files in the directory where connector installation was initiated
  • post_install_log.txt
  • status.bin
  • vlink_installer_*.txt
• In Windows: C:\Program Files\..... (all log files) and in Linux: /usr/loca/intigua/.... (all log files)
  • vAgentManager/channel/status/*.txt
  • vAgentManager/log/*.txt
  • vAgentManager/PackageManager/vlink/log/connector_stdout.txt

Relevant Articles

• Deploying the Connector
• Removing the Connector