nimldr Failed to connect to a Nimsoft Hub! Express install deactivated.
Article ID: 381150
Updated On:
Products
Issue/Introduction
Running nimldr on a Linux host with Express (silent) mode it will fail with:
What is the IP address of the host running a Nimsoft Hub?
==>[] Failed to connect to a Nimsoft Hub! Express install deactivated.
Environment
Version: 20.4, 23.4
Component: robot
Resolution
This can happen under the following circumstances:
- There is a mix of nimldr, and installer file. The nimldr file used should be from the directory that is consistent with the installer that you are using.
- The installer is not in the directory defined in with the -F switch
- The installer name has been changed, from what is expected by the respective nimldr version
Example command:
./nimldr -t /tmp -F /opt -p /opt/nimsoft -I ###.###.###.### -R ###.###.###.### -r -E
In this example (minimum required flags for express installation to work):
| -t <path to use for temporary files during installation> |
default=/opt/nimsoft/tmp |
| -F <directory containing installation file> |
|
| -p <Nimsoft installation path> |
default=/opt/nimsoft |
| -I <IP address of Nimsoft Hub running a Distribution Server> |
NOTE: This will override the -H option |
| -R <IP address for this robot> |
This is mostly useful for systems with multiple network cards |
| -r install Robot only |
(default mode) |
| -E express installation |
(uses defaults or supplied flags) |
Clarity on the -I option. This also would be the hub, be it primary or secondary that you want this robot to. If you were planning to perform an express installation without a local file, than this would be the hub where the installer is pulled from. Also, if the installer is not local, you will need the nimbus user and password required to communicate with the distsrv on that hub to pull down the installation package.
| Installer naming conventions | nimldr from directory |
| install_AIX_6_64.zip | aix-ppc64 |
| install_HPUX_11_ia64.zip | hpux-ia64 |
| install_LINUX_23.zip | linux-x86 |
| install_LINUX_23_64.zip | linux-x64 |
| install_LINUX_23_ppc64le.zip | linux-ppc64le |
| install_SOLARIS_10_amd64.zip | solaris-amd64 |
| install_SOLARIS_10_i386.zip | solaris-i386 |
| install_SOLARIS_10_sparcv9.zip | solaris-sparcv9 |
Additional Information
nimldr flags:
-d <debuglevel 0-5>
default=0
-l <installation logfile>
default=nimldr.log
-t <path to use for temporary files during installation>
default=/opt/nimsoft/tmp
-D <Nimsoft Domain name>
-H <Nimsoft Hub name>
-N <Override Robot name>
-p <Nimsoft installation path>
default=/opt/nimsoft
-f <Override package file name>
default installation file is detected by the program
NOTE: Case sensitive, and without the .zip extension
-u install as current user, not as root
NOTE: This is NOT recommended!
-o <first probe port>
-R <IP address for this robot>
This is mostly useful for systems with multiple network cards
-a set the automatic unregiser flag
-s set the robot to passive mode
-A set robotip_alias for NAT (very special case - use with caution!)
-v prints version of ./nimldr
-h prints this help text
Installation file on local machine:
-F <directory containing installation file>
Installation file on a Nimsoft Distribution Server:
-I <IP address of Nimsoft Hub running a Distribution Server>
NOTE: This will override the -H option
-U <username> for logging into hub (for archive, etc.)
-S <password> for logging into hub
-V <package version>
get the specified version of the package, not the latest one
Installation modes:
-r install Robot only (default mode)
-i install Infrastructure (Robot, Hub, Nas and Distsrv)
-E express installation (uses defaults or supplied flags)
-X silent express installation (fails instead of going to interactive mode)
Cloud installation:
-C <number of restarts until Robot should become active>
-M <DNS name of the machine running the Hub>
Feedback
