delay on starting NAS probe due to maintenance

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

On a secondary NAS probe (not HA, but intended for load distribution) I am seeing a delay on startup as the probe searches for maintenance_mode. However, maintenance_mode is on a different hub so this never succeeds.

Mar 6 13:29:24:855 [140298876225344] 0 nas: NAS Terminated.
Mar 6 13:29:34:890 [140362721576768] 0 nas: ****************[ Starting ]****************
Mar 6 13:29:34:891 [140362721576768] 0 nas: nas 9.37, Feb 6 2023
Mar 6 13:29:34:891 [140362721576768] 0 nas: Copyright 2013, CA. All rights reserved.
Mar 6 13:29:34:892 [140362721576768] 1 nas: nimNamedSession: failed lookup nas (4)
Mar 6 13:29:34:895 [140362721576768] 1 nas: port=48012 PID=27315
Mar 6 13:29:34:896 [140362721576768] 0 nas: No longer checking for restricted hub license
Mar 6 13:29:34:896 [140362721576768] 0 nas: NAS Services called using mode: 1
Mar 6 13:29:34:896 [140362721576768] 0 nas: waitForMaintenanceMode : Contacting Maintenance mode. Attempt : 1
Mar 6 13:29:34:897 [140362721576768] 1 nas: nimNamedSession: failed lookup maintenance_mode (4)
Mar 6 13:29:34:897 [140362721576768] 0 nas: waitForMaintenanceMode : Unable to obtain nimNamedSession for registration to maintenance_mode
Mar 6 13:29:34:897 [140362721576768] 0 nas: waitForMaintenanceMode : Sleeping for 30 seconds
Mar 6 13:30:04:924 [140362721576768] 0 nas: waitForMaintenanceMode : Contacting Maintenance mode. Attempt : 2
Mar 6 13:30:04:925 [140362721576768] 1 nas: nimNamedSession: failed lookup maintenance_mode (4)
Mar 6 13:30:04:925 [140362721576768] 0 nas: waitForMaintenanceMode : Unable to obtain nimNamedSession for registration to maintenance_mode
Mar 6 13:30:04:925 [140362721576768] 0 nas: waitForMaintenanceMode : Sleeping for 30 seconds
Mar 6 13:30:34:954 [140362721576768] 0 nas: waitForMaintenanceMode : Contacting Maintenance mode. Attempt : 3
Mar 6 13:30:34:956 [140362721576768] 1 nas: nimNamedSession: failed lookup maintenance_mode (4)
Mar 6 13:30:34:956 [140362721576768] 0 nas: waitForMaintenanceMode : Unable to obtain nimNamedSession for registration to maintenance_mode
Mar 6 13:30:34:956 [140362721576768] 0 nas: waitForMaintenanceMode : Sleeping for 30 seconds
Mar 6 13:31:04:985 [140362721576768] 0 nas: waitForMaintenanceMode : Contacting Maintenance mode. Attempt : 4
Mar 6 13:31:04:986 [140362721576768] 1 nas: nimNamedSession: failed lookup maintenance_mode (4)
Mar 6 13:31:04:986 [140362721576768] 0 nas: waitForMaintenanceMode : Unable to obtain nimNamedSession for registration to maintenance_mode
Mar 6 13:31:04:986 [140362721576768] 0 nas: waitForMaintenanceMode : Sleeping for 30 seconds
Mar 6 13:31:35:015 [140362721576768] 0 nas: waitForMaintenanceMode : Contacting Maintenance mode. Attempt : 5
Mar 6 13:31:35:016 [140362721576768] 1 nas: nimNamedSession: failed lookup maintenance_mode (4)
Mar 6 13:31:35:016 [140362721576768] 0 nas: waitForMaintenanceMode : Unable to obtain nimNamedSession for registration to maintenance_mode
Mar 6 13:31:35:016 [140362721576768] 0 nas: waitForMaintenanceMode : Sleeping for 30 seconds
Mar 6 13:32:05:044 [140362721576768] 0 nas: waitForMaintenanceMode : Contacting Maintenance mode. Attempt : 6
Mar 6 13:32:05:045 [140362721576768] 1 nas: nimNamedSession: failed lookup maintenance_mode (4)
Mar 6 13:32:05:045 [140362721576768] 0 nas: waitForMaintenanceMode : Unable to obtain nimNamedSession for registration to maintenance_mode
Mar 6 13:32:05:045 [140362721576768] 0 nas: waitForMaintenanceMode : Sleeping for 30 seconds

Environment

Release : 20.4

Resolution

NAS is looking for a local maintenance_mode probe as part of new functionality intended to wait for probe activation on a standby/HA hub.

The NAS probe checks for the state of the maintenance mode for a maximum of 6 iterations. The timeout interval is based on the configuration key ‘mm_timeout_interval’ which can be set between 0 and 60 sec. The default value of the timeout is 30 seconds.

The maximum wait time is six times the mm_timeout_interval. For example, if the key mm_timeout_interval is set as 30, the maximum wait time is 180 seconds.

This key should be added to the "setup" section of nas.cfg.

In a future release this will be updated to respect the "maintenance_mode_address" key and look for a non-local maintenance mode.

In the meantime you can set mm_timeout_interval to '0' as a workaround. The attempts will still be logged but will happen instantly so as to avoid delaying the startup.