Configure an sla_engine Probe as a Slave on a Secondary Hub

Products

• NIMSOFT PROBES
• DX Infrastructure Management

Issue/Introduction

Cannot configure sla_engine as a slave on a secondary hub. sla_engine throws max restarts error and will not start after it is is configured as a slave.

Environment

Release : 9.0.2

Component : UIM - UMP

sla_engine v9.10

Robot: 9.10 / 9.20HF5

Resolution

If an sla_engine probe is installed on a secondary Hub, it will not automatically become a Slave to the Master sla_engine probe on the Primary Hub. The secondary sla_engine must be configured manually using the sla_engine Raw Configure menu.

Follow these steps:

Open the Raw Configure menu for the sla_engine on the secondary Hub, click setup.
Click the Master Key item, Edit Key.
Change 'yes' to 'no' in the
Enter new value: field.
Click the data_engine_address Key,
Edit Key.
Enter the address for the data_engine probe in the following format:
/<Domain>/<hub>/<robot>/data_engine

Note that in UIM v9.0.2 or higher the cryptkey file must be copied from the Primary hub to the Secondary hub where the sla_engine slave is deployed and its location configured in the robot.cfg.

Activate the sla_engine and check the sla_engine.log to make sure there are no errors.

If you see no errors in the log, except a max restarts error, make sure you check the java_jre version and upgrade it if required.

For example, java_jre v2.02.