search cancel

nas not connecting to alarm queue in MS cluster environment


Article ID: 34002


Updated On:


DX Unified Infrastructure Management (Nimsoft / UIM) CA Unified Infrastructure Management On-Premise (Nimsoft / UIM)


Errors in the hub log similar to the following:
hub: Consumer for 'nas' sent an unexpected response code 11 in acknowledgement
hub: Queue subscriber for 'nas' sent unexpected response (2,11) on attempt 1 after 0 ms, will retry in 100 ms

Errors in the nas log similar to the following:

nas: The subscriber-channel disconnected by HUB

Audit probe recording an error about the connection string being too long even though the data_engine is working ok and the audit probe is finding the data_engine ok.


Component: UIMNAS


Check and verify that the NIMBUS_LOCAL_IP system variable is set to the virtual IP address of the cluster.

Add the following 2 keyword/value pairs to the hub configuration under the hub section using the hub probe's Raw Configure GUI:
bulk_size_floor = 1
default_bulk_size = 1

It may be necessary to fail over to the backup node and then back again to the primary node to make sure the system environment variable is in place when the Nimsoft service is restarted.