Message-ID: <1527972647.4158.1711620779322.JavaMail.confluence@unimus-dev1> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_4157_58707526.1711620779321" ------=_Part_4157_58707526.1711620779321 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html Driver timeout multipliers

Driver timeout multipliers

As described in our Changing default timeouts article, some drivers use a multipli= er for their relevant CLI data retrieval timeout. This article lists all dr= ivers using such multipliers.

Why are multipli= ers used?

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 ext= remely long to output it's backups. Please note these multipliers only appl= y to Backups jobs, NOT to Mass Config Push. If you wish to= change timeouts for Config Push, either change the default settings, or us= e Advanced Set= tings for Config Push. Here are 2 examples why multipliers need to be u= sed for backups:

1) MikroTik RouterOS and inconsistent paging

MikroTik ROS normally uses paging for output (for example, try running "= /interface print" on a router with multiple interfaces when the terminal ve= rtical size is low). This means our ROS driver must support paging, or Mass= Config Push would not work as expected. However, the backup command on ROS= ("/export") is NOT paged. On MikroTiks with very long config, high CPU loa= d, or if many items in the config database on the device exist (such as ful= l BGP route tables), the output of "/export" will take a long time. Since t= he default per-page timeout is 20 seconds, backups would routinely fail on = such routers. This is why we introduced a multiplier to the timeout value.<= /p>

= 2) Ruckus SmartOS and extremely long backups

Ruckus devices running SmartOS - such as Ruckus Unleashed and Ruckus Zon= eDirector, can take over 15 minutes to output their full backups. You can t= est this by yourself by logging into one of these devices using your usual = SSH client, and running "show config". Since we know these devices output t= heir config extremely slow, we use a timeout modifier to make sure these de= vices work properly with Unimus.

Full documentation

 

Device type / family Supports paging Used timeout type Default timeout Multiplier Actual timeout (using defaults)
Cisco WLC Yes unimus.core.cli-expect-timeo= ut 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-timeo= ut 20 seconds 3 60 seconds
Ericsson SGSN Yes unimus.core.cli-expect-timeo= ut 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
(6 minutes 15 se= conds)

Fortinet FortiOS
(FortiGate, FortiWeb, etc.)<= /td>
Yes

unimus.core.cli-expect-timeout

20 seconds 5 100 seconds
MikroTik RouterOS Yes

unimus.core.cli-expect-timeout<= /p>

20 seconds 5 100 seconds
Perle IOLAN Yes

unimus.core.cli-expect-timeout<= /p>

20 seconds 2 40 seconds
RedCarrierSwitch Yes unimus.core.cli-expect-timeo= ut 20 seconds 3 60 seconds
Ruckus SmartOS
(Unleashed / Zon= eDirector)
No unimus.core.max-backup-timeout 75 seconds 15 1125 seconds
(18 minutes 45 sec= onds)
Watchguard Fireware No unimus.core.max-backup-timeout 75 seconds 5 375 seconds
(6 minutes 15 secon= ds)
Zhone Yes

unimus.core.cli-expect-timeout<= /p>

20 seconds 30 600 seconds
(10 minutes)

------=_Part_4157_58707526.1711620779321--