...
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 (more info here), Unimus will establish multiple session to a device to test credentials. Unimus waits 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.
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.
...
For devices that use paging, Unimus uses a 20 second timeout after sending a command to wait for a device to respond device with pagination or a prompt. Each page has its own 20 second timeout. For example, if the device takes longer than 20 seconds to finish outputting a response or offer pagination to a 'show version' command, Unimus will consider this a timeout.
(This is controlled by the unimus.core.cli-expect-timeout setting).
For devices that do not output using paging, Unimus uses a 75 second timeout. So for devices without paging, they need to output the full output for a command and return a prompt in under 75 seconds, or Unimus considers the operation failed.
(This is controlled by the unimus.core.max-backup-timeout setting).
All of these values can be adjusted.
...