Note: A product listed in this article has either reached hardware End of Life (EOL) OR software End of Engineering (EOE). Refer to End of Life Products & Milestones for the EOL, EOE, and End of Support (EOS) dates.
The job manager output window shows the timeout message below when trying to contact the device:
The device has not responded for XXX seconds or timeout for 40 seconds while sending CLI “get lic".
When the CLI sent a get lic command, the device driver did not respond or a timeout occurred.
While trying to communicate to the device, NSM could not get a response due to one of the reasons below:
- A slow congested network and packet loss, or
- A high rate of logging from the device back to NSM, which competes with the management traffic for NSM.
For a high rate of logging from the device back to NSM:
A workaround for some versions of ScreenOS is to enable this CLI command on the firewall:
set nsm report drop enable.
This will allow the firewall to drop some logs in order for the NSM directive to succeed.
For a slow congested network and packet loss:
Raise the timeouts in NSM to allow for a longer response time back from the device, as follows:
1. Open /usr/netscreen/DevSvr/var/devSvr.cfg.
2. Double the slow/fast CLI timeout values by editing the lines below:
devSvrDirectiveHandler.fastCli.timeout 40000
devSvrDirectiveHandler.fastCli.retry 2
devSvrDirectiveHandler.slowCli.timeout 120000
devSvrDirectiveHandler.slowCli.retry 1
devSvrDirectiveHandler.veryslowCli.timeout 2400000
devSvrDirectiveHandler.veryslowCli.retry 1
3. Restart the device server. To restart the server, consult: KB11263 - Proper order for starting and stopping NSM services.
2020-10-18: Tagged article for EOL/EOE.