AIX robot does not auto start when server is rebooted
search cancel

AIX robot does not auto start when server is rebooted

book

Article ID: 205542

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

The Nimbus services on AIX Server do not auto start when the server is rebooted

Environment

Release : 8.x, 9.x, 20.x

Component : UIM - ROBOT_AIX

Cause

There could be different causes like (a) the startup script has not been added (and/or) (b) the environment variables have not been set/recognized

Resolution

Note:
=====

If robot was installed using nimldr utility, the startup script would be found in /etc/rc.tcpip
If robot was installed using ADE (automated_deployment_engine), the startup script would be found in /etc/inittab 


First verify the below commands to start and stop the robot respectively on AIX Server are working:

/usr/bin/startsrc –s nimbus
/usr/bin/stopsrc –s nimbus

 

Assuming the robot was installed using nimldr utility and:
 
(i) if the above commands to start and stop the robot work fine, please refer Section A 
(ii) if the above commands to start and stop the robot do not work fine, please refer Sections B and C respectively

 

---Section A----


The /etc/rc.tcpip should contain the below entry to auto start nimsoft services when the Server reboots:

nimbus:2:respawn:/usr/bin/startsrc -s nimbus 

If the above entry is not present, run the below Nimbus service script as root user on AIX server: 

/opt/nimsoft/install/service-ctrl.sh enable   

The above command should add the entry in startsrc. Run the above command and verify /etc/rc.tcpip contains the entry:

nimbus:2:respawn:/usr/bin/startsrc -s nimbus 

Schedule downtime, reboot the AIX server and verify the Nimbus services start with the AIX server. 

If the Nimbus services still don't start, refer sections B.

 

---Section B----

Edit and run the RobotConfigurer.sh file as described in the resolution section of the below technical document:
 
https://knowledge.broadcom.com/external/article?articleId=130864

 

After following the above technical document, if /etc/rc.tcpip does not contain the below entry:  

nimbus:2:respawn:/usr/bin/startsrc -s nimbus 

Repeat steps of ---Section A----:

 

Schedule downtime, reboot the AIX server and verify the Nimbus services start with the AIX server. 

If the Nimbus services still don't start, refer section C.
 

---Section C----


The other workaround would be to add the following line in the file /etc/rc.tcpip to start robot automatically when the Server restarts:


nimbus:2:respawn:/usr/bin/niminit start

Additional Information

Similarly, to start and stop the Nimbus services, assuming robot is installed in default path /opt/nimsoft, you could also run the below commands respectively:

 

cd /opt/nimsoft/bin/

 

To stop Nimbus:
===============
./niminit stop


To start Nimbus:
===============
./niminit start

 

Please refer the following documents for further Reading:

https://knowledge.broadcom.com/external/article/47132/how-does-an-aix-robot-start-at-reboot.html

https://knowledge.broadcom.com/external/article/14487/what-are-the-commands-necessary-for-sudo.html