...
During device Discovery (more info here), Unimus will establish multiple consecutive sessions to a device to test credentials (unless credential binding is used). Unimus waits 500 ms between session establishments by default. Especially for older / slower devices, or for purposes of slowing down device logins due to load on a central AAA system, it can be beneficial to increase this inter-connection delay. This timeout delay 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 to the device was successful. In cases this is needed, Unimus has a set duration for each of these checks. This duration should normally NOT be changed by the user - please only change this setting if asked to by our support. This 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 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 on Cisco IOS, 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. Please note some of our drivers for devices we support apply a multiplier to this value. This timeout should normally NOT be changed by the users user - please only change this setting if asked to by our support.
...