search cancel

Changes from updated configuration only package not seen in probe when package deployed to robot managed by a secondary hub

book

Article ID: 134775

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM) Unified Infrastructure Management for Mainframe

Issue/Introduction

The distsrv probe on the primary hub configured with the following options:


Forward Interval:  60

Immediately perform forwarding when a change is detected: yes

Use remote distsrv on distribution:  yes

All versions of all packages to be forwarded to 5 secondary hubs


The distsrv probe on the 5 secondary hubs are configured with the following options:


Accept remote distributions: yes

Use local archive for accepted remote distributions:  yes


A change is made to an existing probe configuration only package, saved in the local archive on the primary hub, then immediately deployed to a robot managed by one of the remote hubs,  The deployment succeeds, but the configuration change from the configuration only package is not seen in the probe's configuration file on the remote robot. 


Deploy the same package an hour later and the configuration change is seen in the probe on the remote robot.

Environment

Release : 8.51 or later

Component : UIM - DISTSRV : any version

Cause

From the loglevel 5 distsrv logs captured on the primary hub, it was seen that it was taking the probe approximately 37 minutes to compare all 643 packages in the archive on the primary hub against the packages found in the local archives on the 5 secondary hubs.  Changes to packages on the primary hub are most likely not going to be immediately available in the archives on the secondary hubs.  It may take up to 37 minutes for the change to be forwarded to any one of the 5 secondary hubs.  This is by design and is affect by how forwarding is configured on the primary hub.

Resolution

According to the distsrv IM GUI Reference -> The Setup Tab -> Forwarding Wiki page, the "Immediately perform forwarding when a change is detected" option will forward the license immediately when a package is added or changed in the archive.  The note for this option also indicates that enabling it does not change the forwarding on interval setting.  It does not affect when a new or modified package will be forwarded.  This is determined by the "Forward Interval" option which defines the interval when licenses can be forwarded and package versions are compared to determine if packages are due for forwarding. 


Package forwarding from the primary hub archive to the local archives on secondary hubs is dependent on how forwarding is configured.  In this particular instance, all versions of all probes were configured to be forwarded to 5 secondary hubs.  There were a total of 643 packages in the local archive on the primary hub and it was taking the distsrv probe on the primary hub approximately 37 minutes to compare all 643 packages against the local archives on the 5 secondary hubs.  Even though the "Forward interval" on the primary distsrv probe is set to 60 seconds, it may take as long as 37 minutes for the distsrv probe to forward a change to a package in the archive on any one of the secondary hubs.  How long it will take, all depends on when the package update is saved to the local archive on the primary hub and where the distsrv probe is in its progress for checking each package in the archives in all 5 remote hubs.


For example, if the distsrv probe just finished verifying that a specific package on one of the secondary hubs is up to date and a change to this package is saved on the primary hub right after this, the distsrv will not get back to this package on this hub until approximately 37 minutes later.  At that time the change will be forwarded to the secondary hub.


Best practice in this case would be to wait at least 40 minutes after saving a change to a package in the local archive on the primary hub before deploying this package to a robot managed by any secondary hub.  

Additional Information

If the distsrv probe on the primary hub is configured to "Immediately perform forwarding when a change is detected". How long does it take distsrv to detect a change?


According to the distsrv Wiki page, the "Immediately perform forwarding when a change is detected" option will forward the license immediately when a package is added or changed in the archive. The note for this option also indicates that enabling it does not change the forwarding on interval setting. It does not affect when a new or modified package will be forwarded. This is determined by the "Forward Interval" option which defines the interval when licenses can be forwarded and package versions are compared to determine if packages are due for forwarding.


How long after the distsrv probe on the primary hub detects the change, does it take to replicate to the secondary?  The assumption is that it is based on the Forwarding interval?


The assumption is correct, but there is a caveat to this.

There are a couple of factors that affect when the changed package will be forwarded to the archive on the secondary hubs.  These include the following:


- the number of packages that are being kept in sync between the archive on the primary hub and the secondary hub(s) (controlled by which packages and which versions should be forwarded)

- the number of secondary hubs with an archive that packages are forwarded to


If the Forwarding interval is set to 60 seconds, but it takes the distsrv probe longer than that to check the current version of all forwarded packages in the archives of all secondary hubs configured are up-to-date, then it can take more than 60 seconds before the package change is forwarded to all secondary hub archives. 


The more packages found in the local archive on the primary hub and the more secondary hubs configured to forward these packages to, the longer it can take for the change to be reflected in the archives on all of the remote hubs.


When configuring forwarding with the distsrv probe, the following should be considered to try and reduce the time it takes to get changed packages forwarded to the archives on the configured remote hubs:


Do not select the "All versions" option when configuring secondary hubs that packages should be forwarded to on the Forwarding tab of the distsrv Configure GUI on the primary hub.  By not selecting this option, the primary hub will only check to see if the current version of a package in the archive on the primary hub is also up-to-date in the archives on the secondary hubs.  The downside of this is that if you import an older version of a probe that already exists in the local archive on your primary hub, it will not be forwarded to the secondary hubs.


If it is desirable to have all versions of all packages forwarded to the archives on the configured secondary hub, a second option would be to delete any unwanted/unused versions of packages found in the archive on the primary hub.  If you are no longer using/deploying specific versions of packages in the archive, then delete them from the archive on the primary hub. 


These 2 strategies will reduce the number of packages that the distsrv probe on the primary hub needs to keep in sync on the secondary hubs.    Neither of these will guarantee that a change to a package in the archive on the primary hub will be immediately available in the archive on your secondary hubs, they will only reduce the amount of time that it takes for the distsrv probe on the primary hub to detect that there is a change in the package and get the new version deployed to the archives on the secondary hubs.