Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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.

Data retrieval from the CLI

For device CLI communication / 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 and requires 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 after sending a command to wait for the output of each command it sends to the device. 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.
(controlled by the unimus.core.cli-expect-timeout setting)

For backups, this however works differently.
Many devices output backups in 'paged' format.
Each page therefore has its own 20 second timeout.For devices that do not output backups using paging, Unimus uses a 75 second timeout.
So for devices without paging, they need to output their backup contents the full output for a command and return a prompt in  under 75 seconds, or Unimus considers the backup operation failed.
(controlled by the unimus.core.max-backup-timeout setting)

...