I have recently upgraded to Version : 2.0.1 from a 2.x beta from ~December 2019. After the upgrade I am seeing INTERACTION_ERROR for a zhone MXK. Looking for any insight into what may be causing this new error.
nb
[Solved] INTERACTION_ERROR for Zhone MXK
"INTERACTION_ERROR" means Unimus did not receive any known / recognizable data from the device up until the configured timeout. This can be usually solved by simply increasing the timeouts: https://wiki.unimus.net/display/UNPUB/C ... t+timeouts
For a more detailed explanation:
Unimus supports both paged ("--More--") and non-paged device output.
Note: the real logic in Unimus is a lot more complex than described below, due to handling for many other things (like "Press y to continue", various other device prompts and questions, etc.)
There are 2 separate timeouts for these, one for paged outputs, where each page has a (by default) 20 second timeout.
This means that after sending a command to the device, Unimus expects the device to within 20 seconds send a page of data, or the final prompt that signifies output ended. If a page is received, the timeout is reset - up to a 10000 page safety limit, or until a prompt is received.
For non-paged devices, Unimus will wait (by default) 75 seconds for a prompt.
Now back to Zhone, which is problematic because:
1) Zhone can take 15+ minutes to output a full backup
2) Zhone can output the backup in paged or non-paged format - this is also configurable by users on the Zhone CLI
Since Zhone can take a long time to backup, and it can do paging, Unimus uses the paging approach. Our Zhone MXK driver applies a x30 multiplier to the paging timeout. This means, by default, Unimus will timeout a Zhone backup in 10 minutes. This can be a problem if your Zhone doesn't page, and takes more than 10 minutes to backup.
How to solve this:
1) make sure you are running the latest Unimus release (2.0.2 as of writing of this post)
2) increase the paging timeout to a higher value - "unimus.core.cli-expect-timeout=60000"
For example, to allow for a max backup timeout of 30 minutes, increase the per-page timeout to 60000 (60 sec)
60 * 30 (multiplier) = 1800 seconds = 30 minutes
For a more detailed explanation:
Unimus supports both paged ("--More--") and non-paged device output.
Note: the real logic in Unimus is a lot more complex than described below, due to handling for many other things (like "Press y to continue", various other device prompts and questions, etc.)
There are 2 separate timeouts for these, one for paged outputs, where each page has a (by default) 20 second timeout.
This means that after sending a command to the device, Unimus expects the device to within 20 seconds send a page of data, or the final prompt that signifies output ended. If a page is received, the timeout is reset - up to a 10000 page safety limit, or until a prompt is received.
For non-paged devices, Unimus will wait (by default) 75 seconds for a prompt.
Now back to Zhone, which is problematic because:
1) Zhone can take 15+ minutes to output a full backup
2) Zhone can output the backup in paged or non-paged format - this is also configurable by users on the Zhone CLI
Since Zhone can take a long time to backup, and it can do paging, Unimus uses the paging approach. Our Zhone MXK driver applies a x30 multiplier to the paging timeout. This means, by default, Unimus will timeout a Zhone backup in 10 minutes. This can be a problem if your Zhone doesn't page, and takes more than 10 minutes to backup.
How to solve this:
1) make sure you are running the latest Unimus release (2.0.2 as of writing of this post)
2) increase the paging timeout to a higher value - "unimus.core.cli-expect-timeout=60000"
For example, to allow for a max backup timeout of 30 minutes, increase the per-page timeout to 60000 (60 sec)
60 * 30 (multiplier) = 1800 seconds = 30 minutes