...

By default, Unimus uses 10 second timeouts for SSH / Telnet connections. This means that if your device takes longer than 10 second to establish an SSH / Telnet session, Unimus will not connect to it (fail the connection attempt). This timeout is controlled by the unimus.core.connect-timeout setting. After successful connection, if the connection is SSH, Unimus waits for up to unimus.core.ssh-version-validation-timeout to receive the SSH server identification.

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 delay is controlled by the unimus.core.inter-connection-delay setting.

...

-Dunimus.core.connect-timeout=20000 -Dunimus.core.ssh-version-validation-timeout=20000 -Dunimus.core.inter-connection-delay=1000 -Dunimus.core.cli-expect-timeout=30000

...

Restart Unimus to apply the new timeouts.

Note: If your network devices are managed via a remote Unimus Core, you must apply the timeout configuration settings on the remote Core instance. Edit the configuration file located at: /etc/default/unimus-core.

On Windows:

For portable:
Create a file named Unimus.l4j.ini in the same directory as the Unimus executable.
Change Unimus in the above file name to exactly match the name of the Unimus executable.

...

-Dunimus.core.connect-timeout=20000
-Dunimus.core.ssh-version-validation-timeout=20000
-Dunimus.core.inter-connection-delay=1000
-Dunimus.core.cli-expect-timeout=30000

...

Restart Unimus to apply the new timeouts.

Note: If your network devices are managed via a remote Unimus Core, you must apply the timeout configuration settings on the remote Core instance. Edit the Unimus.l4j.ini file in: 'C:\Program Files\Unimus-Core\'.