ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Unable to install UIM Agent on Solaris servers.

book

Article ID: 212790

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM) NIMSOFT PROBES Unified Infrastructure Management for Mainframe CA Unified Infrastructure Management On-Premise (Nimsoft / UIM) CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

We are unable to install UIM Agent on Solaris server .

gethostbyname returns loopback address!
please check your /etc/hosts file
Error detecting your IP settings. Please check the installation log for more details!
Unable to continue!

Environment

Release : 9.1.0

Component : UIM - ROBOT

Resolution

Please use the latest nimldr version which supports all of the most current robot versions.

http://support.nimsoft.com/Files/Archive/00056/nimldr-9.31.tar.Z

See Release notes:
http://support.nimsoft.com/unsecure/archive.aspx?id=56

Please make the first entry for the server, the external IP address in the /etc/hosts file on that Solaris machine and try again.

When nimldr is run, we try to figure out what ip a system has by doing a lookup of the hostname, then using that hostname to resolve the ip that goes with it. It's possible that either your DNS name resolution is not set up properly or the /etc/hosts file has the first entry set to the hostname listed as the loopback address 127.0.0.1.

Verify that the system /etc/hostsfile maps 127.0.0.1 to localhost, and its own IP address to its hostname.

You can follow the steps to use nimldr here:

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/unified-infrastructure-management/20-3/installing/install-secondary-hubs/deploy-secondary-hubs-and-robots-on-linux-or-solaris.html

-d 5 argument for nimldr sets it to debug mode so you can see more detail in the nimldr.log.

If the robot cannot reach the hub, you can copy the installation file to the local system and reference it there during the install when prompted.