Device CLI connection timeout and inter-connection delay
By default, Unimus uses 10 second timeouts for SSH / Telnet connections.
This means that if your device takes longer than this to establish an SSH session, Unimus will not connect to it.
(This timeout is controlled by the unimus.core.connect-timeout setting).
During device discovery Discovery (more info here), Unimus will establish multiple session to a device to test credentials.
Unimus waits 250ms 500 ms between session establishments by default.
Especially for older / slower devices, it can be beneficial to increase this inter-connection delay.
(This timeout is controlled by the unimus.core.inter-connection-delay setting)For device interaction, Unimus has a 20 second timeout on each command it issues to the device.
.
Finally, during device login, in certain cases Unimus needs to validate the device prompt - to be sure that the login was successful. This timeout should normally NOT be changed by the users - please only change this setting if asked to by our support.
This timeout is controlled by the unimus.core.login-prompt-validation-limit setting.
Data retrieval from the CLI
For device interaction, timeouts depend on the format of output from the device. Many devices output in 'paged' format - output is separated into multiple pages, each ending in a " – More – " or similar message, requiring some key to be sent to continue. Unimus fully supports this for all devices on our Supported vendors/devices list.
For devices that use paging, Unimus uses a 20 second timeout to wait for the output of each command it sends to the device. For example, if the device takes longer than 20 seconds to respond finish outputting a response to a 'show version' command, Unimus will consider this a timeout.
(controlled by the unimus.core.cli-expect-timeout setting)
...