InfoScale Operations Manager 9.2 — Gendeploy Script Replacement Procedure for Managed Host Registration Without Manual Refresh

book

Article ID: 1000766242

calendar_today

Updated On:

Description

When a new managed host is added to an IOM 9.2 Central Management Server using the standard gendeploy workflow, the generated deployment script output, in this example addviom.pl, is copied to the target host and executed. The script performs the following operations on the managed host: it validates the MH version compatibility, initiates communication with the CMS, extracts the authentication credential, and runs configure_mh to write the new VRTSat security context and trusted certificates to disk.

In the original IOM 9.2 release, the deployment script does not restart the xprtld daemon after configure_mh completes. The xprtld process continues to serve connections using its stale pre-configuration trust settings. Because the CMS cannot authenticate against the managed host using the newly written credentials — which xprtld has not yet loaded — the host appears as disconnected in the VIOM console. The host remains in this state until an administrator manually refreshes the host entry from the CMS GUI (Settings → Host → Right-click → Refresh), or until xprtld is manually restarted on the managed host.

This behavior affects all IOM 9.2 environments where managed hosts are being added for the first time or re-registered after a fresh CMS installation. It does not affect hosts that were already registered and communicating prior to the deployment.

The updated gendeploy.pl is delivered as a standalone replacement script. Customers running IOM 9.2 can apply the fix by replacing the single script on the CMS and regenerating deployment perl script for their managed hosts.

Cause

The root cause is a missing service restart step in the managed host deployment workflow. When the generated addviom.pl script runs configure_mh on the target host, the VRTSat authentication credentials and the CMS broker certificate are written to disk under /var/opt/VRTSsfmh/sec/ and /var/opt/VRTSsfmh/trusted/. However, the xprtld daemon — which serves as the transport layer for CMS-to-MH communication over port 5634 — is not restarted after this credential write operation.

Because xprtld loads its trust configuration only at startup, it continues operating with the old (self-signed, pre-configure) certificate context. The CMS attempts to establish an authenticated TLS 1.3 connection to the managed host on port 5634, but the handshake fails because xprtld is still presenting credentials that the CMS does not recognize as belonging to a registered host. The host therefore appears as disconnected or idle in the VIOM console, typically timing out after approximately 10 minutes.

The existing gendeploy.pl logic does invoke catalog.pl refresh for catalog synchronization, but this catalog refresh does not address the xprtld trust state. The service restart was the missing step.

Resolution

The resolution is to replace the existing gendeploy.pl on the IOM 9.2 CMS with the updated version and regenerate deployment packages for all managed hosts that need to be added or re-registered.

Prerequisites:

  • IOM 9.2 Central Management Server is installed and operational.

  • Root or equivalent administrative access to the CMS.

  • The updated gendeploy.pl script can be obtained by contacting infoscale support. They will provide the binary via case attachment.

Procedure:

On the CMS (e.g., vmu-viom-01):

Back up the existing gendeploy script before replacement:

 
 
 
cp /opt/VRTSsfmh/bin/gendeploy.pl /opt/VRTSsfmh/bin/gendeploy.pl.bak_$(date +%Y%m%d)

Replace the script with the updated version:

 
 
 
cp /path/to/new/gendeploy.pl /opt/VRTSsfmh/bin/gendeploy.pl chmod 755 /opt/VRTSsfmh/bin/gendeploy.pl

Generate a new deployment script for the target managed host:

 
 
 
/opt/VRTSsfmh/bin/gendeploy.pl --out addviom.pl chmod +x addviom.pl

Transfer the generated addviom.pl to each target managed host:

 
 
 
scp addviom.pl root@<managed-host>:/app/

On each Managed Host (e.g., vmu-bck-01, vmu-bck-02):

If the managed host was previously registered with this CMS or a prior CMS, rename the old resolver configuration to prevent conflicts:

 
 
 
mv /etc/default/sfm_resolv.conf /etc/default/sfm_resolv.conf.old

Verify the MH package integrity matches across all nodes:

 
 
 
rpm -q --dump VRTSsfmh-9.2.0-0.x86_64 | sha256sum

All nodes (CMS and MHs) should return the same checksum. For the current IOM 9.2 release, the expected value is 64e18674151986c64f4d902b065660913c364acf5288f6e5925d35eee2c127d3.

Execute the deployment script:

 
 
 
cd /app ./addviom.pl

The script will display progress including MH version validation, hostname resolution, CMS reachability check, credential extraction, and managed host configuration. Upon successful completion, the host will be fully registered and xprtld will be restarted automatically with the correct trust context.

Validation:

Confirm xprtld is running and listening on port 5634:

 
 
 
/opt/VRTSsfmh/adm/xprtldctrl status netstat -an | grep 5634

Verify the CMS broker certificate is trusted on the managed host:

 
 
 
openssl s_client -connect <cms-hostname>:5634 -showcerts </dev/null 2>&1 | head -30

Confirm the managed host certificate is valid:

 
 
 
openssl x509 -in /var/opt/VRTSsfmh/sec/VRTSat_lhc/*.0 -noout -issuer -subject

From the CMS, verify the host appears as connected in the VIOM GUI (Settings → Managed Hosts). No manual refresh should be required.

If the error "Duplicate Virtual Machine ID found in database for this host" is encountered:

Remove the stale host entry from the CMS database before re-running the deployment:

 
 
 
/opt/VRTSsfmh/bin/vomadm host-mgmt --list | grep -i <hostname> /opt/VRTSsfmh/bin/vomadm host-mgmt --remove --host <hostname-fqdn>

Then re-execute addviom.pl on the managed host.

Issue/Introduction

InfoScale Operations Manager (IOM) 9.2 ships with a version of gendeploy.pl on the Central Management Server (CMS) that does not restart the xprtld transport daemon on the Managed Host (MH) after writing authentication credentials during deployment. As a result, newly deployed managed hosts appear disconnected from the CMS and require a manual "Refresh Host" action from the VIOM GUI to become fully operational. An updated gendeploy.pl script is available separately for IOM 9.2 environments that corrects this behavior. After replacing the script on the CMS, newly generated deploy packages will complete the full host registration cycle — including the xprtld restart — without requiring manual intervention from the GUI.

This article describes the problem, its root cause, the resolution procedure for applying the updated script, and validation steps to confirm the fix.