...
We use timeout multipliers in cases where we know that a device behaves in a very inconsistent way, or we know that the device by default takes extremely long to output it's backups. Please note these multipliers only apply to Backups jobs, NOT to Mass Config Push. If you wish to change timeouts for Config Push, either change the default settings, or use Advanced Settings for Config Push. Here are 2 examples why multipliers need to be used for backups:
1) MikroTik RouterOS and inconsistent paging
...
| Device type / family | Supports paging | Used timeout type | Default timeout | Multiplier | Actual timeout (using defaults) |
|---|---|---|---|---|---|
| Cisco WLC | Yes | unimus.core.cli-expect-timeout | 20 seconds | 3 | 60 seconds |
| Datacom switches | Yes | unimus.core.cli-expect-timeout | 20 seconds | 3 | 60 seconds |
| Ericsson IPOS | Yes | unimus.core.cli-expect-timeout | 20 seconds | 3 | 60 seconds |
| Ericsson SGSN | Yes | unimus.core.cli-expect-timeout | 20 seconds | 3 | 60 seconds |
| Exinda | Yes | unimus.core.cli-expect-timeout | 20 seconds | 15 | 300 seconds (5 minutes) |
| Extreme WLC | No | unimus.core.max-backup-timeout | 75 seconds | 5 | 375 seconds |
| Fortinet FortiOS (FortiGate, FortiWeb, etc.) | Yes | unimus.core.cli-expect-timeout | 20 seconds | 5 | 100 seconds |
| MikroTik RouterOS | Yes | unimus.core.cli-expect-timeout | 20 seconds | 5 | 100 seconds |
| Perle IOLAN | Yes | unimus.core.cli-expect-timeout | 20 seconds | 2 | 40 seconds |
| RedCarrierSwitch | Yes | unimus.core.cli-expect-timeout | 20 seconds | 3 | 60 seconds |
| Ruckus SmartOS (Unleashed / ZoneDirector) | No | unimus.core.max-backup-timeout | 75 seconds | 15 | 1125 seconds (18 minutes 45 seconds) |
| Watchguard Fireware | No | unimus.core.max-backup-timeout | 75 seconds | 5 | 375 seconds (6 minutes 15 seconds) |
| Zhone | Yes | unimus.core.cli-expect-timeout | 20 seconds | 30 | 600 seconds (10 minutes) |