Deploying Connector on the Endpoint Itself Overview
Linux Installation
- Verify pre-reqs (very important)
- Download the latest Linux connector
- Alternatively, copy the latest Linux BSX from JetPatch Server (/usr/share/intigua/bin/)
- Once copied to endpoint, you need to change the permission of the file to run it (via chmod +x)
- The JetPatch Connector installation files installs to /usr/local by default.
- Lastly, run the following command (make sure you modify the command to point to your JetPatch server)
For Enterprise Linux (incl. RHEL, OL, etc) and SLES
For versions Prior to 5.0:
./vlink_installer_linux_x64_Release*.bsx -out=install_state.log -coreserverurl="https://Your_JetPatch_Server_IP_or_Hostname/vmanage-server/"Post 5.0 (assuming default port 8443):
./vlink_installer_linux_x64_Release*.bsx -out=install_state.log -coreserverurl="https://Your_JetPatch_Server_IP_or_Hostname:8443"For Debian Linux (incl. Debian and Ubuntu)
For versions Prior to 5.0:
./vlink_installer_linux_x64_Release*.bsx --out=install_state.log --coreserverurl="https://Your_JetPatch_Server_IP_or_Hostname/vmanage-server/"Post 5.0 (assuming default port 8443):
./vlink_installer_linux_x64_Release*.bsx --out=install_state.log --coreserverurl="https://Your_JetPatch_Server_IP_or_Hostname:8443"Note: Typically, connector installs in /usr/local . If you want a different location use, add the following parameter to the command:
For Enterprise Linux (incl. RHEL, OL, etc) and SLES:
-locations=/usr/bla/For Debian Linux (incl. Debian and Ubuntu)
--locations=/usr/bla/AIX Installation
- Verify pre-reqs (very important)
- Verify that the endpoint has unzip installed
- Download the AIX connector
- Alternatively, copy the latest AIX BSX from JetPatch Server (/usr/share/intigua/bin/) or configure NGINX to point to connector folder to download from UI
- Once copied to endpoint, you need to change the permission of the file to run it (via chmod +x)
- Lastly, run the following command (make sure you modify the command to point to your JetPatch server)
For versions Prior to 5.0:
./vlink_installer_AIX_power_Release*.bsx -no-kill-session /tmp -out=install_state.log -coreserverurl="https://Your_JetPatch_Server_IP_or_ /vmanage-server/"Hostname Post 5.0 (assuming default port 8443):
./vlink_installer_AIX_power_Release*.bsx -no-kill-session /tmp -out=install_state.log -coreserverurl="https://Your_JetPatch_Server_IP_or_Hostname:8443"Solaris Installation
-
Solaris 10
- Verify pre-reqs (very important)
- Verify that the endpoint has unzip installed
- Download the latest Solaris 10 connector
- Alternatively, copy the latest Solaris 10 BSX from JetPatch Server (/usr/share/intigua/bin/) or configure NGINX to point to connector folder to download from UI
- Once copied to endpoint, you need to change the permission of the file to run it (via chmod +x)
- Lastly, run the following command (make sure you modify the command to point to your JetPatch server)
For versions Prior to 5.0:
./vlink_installer_solaris11_sparc64_Release*.bsx -no-kill-session /tmp -out=install_state.log -coreserverurl="https://Your_JetPatch_Server_IP_or_ /vmanage-server/"Hostname Post 5.0 (assuming default port 8443):
./vlink_installer_solaris11_sparc64_Release*.bsx -no-kill-session /tmp -out=install_state.log -coreserverurl="https://Your_JetPatch_Server_IP_or_Hostname:8443/"
-
Solaris 11
- Verify pre-reqs (very important)
- Verify that the endpoint has unzip installed
- Download the Solaris 11 connector
- Alternatively, copy the latest Solaris 11 BSX from JetPatch Server (/usr/share/intigua/bin/) or configure NGINX to point to connector folder to download from UI
- Once copied to endpoint, you need to change the permission of the file to run it (via chmod +x)
- Lastly, run the following command (make sure you modify the command to point to your JetPatch server)
For versions Prior to 5.0:
./vlink_installer_solaris11_sparc64_Release*.bsx -no-kill-session /tmp -out=install_state.log -coreserverurl="https://Your_JetPatch_Server_IP_or_ /vmanage-server/"Hostname Post 5.0 (assuming default port 8443):
./vlink_installer_solaris11_sparc64_Release*.bsx -no-kill-session /tmp -out=install_state.log -coreserverurl="https://Your_JetPatch_Server_IP_or_Hostname:8443/"
Verification and Troubleshooting
Now connect to your JetPatch Console and check that you can see the machine on the "Servers" tab.
1. To verify that the connector has been properly installed, check if the service is running:
/etc/init.d/intigua status2. If the coreserverurl needs to be modified, see this article.
If there are still issues, generate connector logs from the endpoint and contact the Support Team.
Comments
0 comments
Article is closed for comments.