In addition to connecting non-discoverable endpoints to JetPatch Agent Manager in the Console, the following alternative methods are available.
Connecting Non-Discoverable Endpoints with the API Client
You can add non-discoverable endpoints to JetPatch Agent Manager with a supplied API client to the server, as follows:
- Grant API permission to a user.
- Open a CLI interface to the JetPatch Manager Console (a vSphere console, or via SSH), and run:
/root/intigua_client.py --user <username> --apikey <API_key> server-add --ip <target_IP> --name <name> --dnsname <hostname> --osname <OS>
where the above parameters are as in the table below.
Alternatively, if you have a copy of the client (intigua_rest_cmd_client.py) on another machine, you can run it remotely from there, in which case you need to adjust the path to the client accordingly, and the command needs to include:
--url https://<server>/vmanage-server/rest/rest-api/ , where
<server> is the IP address or resolvable hostname of the server.
Optionally, you could incorporate the command in a script, such as for adding multiple machines.
The command parameters are:
Username and API key of a user with API permissions (from previous step)
Endpoint's IP address
A descriptive name for the endpoint, which will appear in the endpoint list, in the Name column
Endpoint's DNS hostname
Endpoint's operating system. Use either a guest OS identifier as defined in the VMware vSphere SDK, or any string containing the OS' commercial name and the phrase 64-bit or 32-bit
- 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 Agent Manager will attempt to install the connector on the machine.
Manually Connecting Non-Discoverable Endpoints
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:
- Make sure organizational firewalls allow HTTPS (port 443) communication from the endpoint to the JetPatch Manager Console.
- Copy the supplied connector file to the endpoint. Find the connector file on the Server:
- For Windows endpoints: /usr/share/intigua/bin/vlink-win-win32_x64-<version>.exe
- For Linux endpoints: /usr/share/intigua/bin/vlink_installer_linux_x64_<version>_Release.bsx
- On the endpoint, run (make sure to copy all quote signs and slashes correctly):
<connector> is the path and filename of the connector file executable, and
<hostIP> is the IP address (not name) of the server host.
If the endpoint is already listed in the Console endpoint list, and you still need to locally install the connector (for example, there is a temporary access problem), you must add to the above command:
-coreid "<ID>" , replacing
<ID> with the ID displayed in the endpoint's Server core ID column in the endpoint list (some of the ID may be hidden; to get the whole string, triple-click it and copy).
The connector is installed, and initiates communication with JetPatch Agent Manager.
- 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
- In Windows: C:\Program Files\..... (all log files) and in Linux: /usr/loca/intigua/.... (all log files)