Dear Support, I have Unimus version 2.0.6 and problems with mass config push.
I got INTERACTION_ERROR with my HP/Aruba switches.
The Discovery and the backup functions work fine with these devices.
The debug log shows only like this:
2020-10-16 10:14:11.945 WARN 5886 --- [ interact-6] n.u.c.service.push.CliConfigPushService : Config push to 'xxx.xxx.xxx.xxx' failed
net.sf.expectit.ExpectIOException: Timed out waiting for any known data from device (timeout: 20000 ms)
at net.unimus.core.cli.interaction.CliOutputCollectionHandler.collect(CliOutputCollectionHandler.java:200)
at net.unimus.core.cli.interaction.CliOutputCollectorImpl.getOutput(CliOutputCollectorImpl.java:157)
at net.unimus.core.cli.interaction.CliOutputCollectorImpl.getOutputOf(CliOutputCollectorImpl.java:114)
at net.unimus.core.cli.interaction.CliOutputCollectorImpl.getOutputOf(CliOutputCollectorImpl.java:54)
at net.unimus.core.service.push.CommandPushHandler.pushCommands(CommandPushHandler.java:48)
at net.unimus.core.service.push.CliConfigPushService.pushCommands(CliConfigPushService.java:254)
at net.unimus.core.api.job.PushJob.doRun(PushJob.java:49)
at net.unimus.core.api.job.AbstractJob.run(AbstractJob.java:96)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Mass config push probleme
Hello,
Apologies for the late reply.
Can you please enable "Device output logging" in "Zones > Your Zone > Debug mode"?
Re-run the push, and please post how the device communication looks like.
As the log suggest, Unimus was not able to recognize any known output from the device:
https://wiki.unimus.net/display/UNPUB/Mass+Config+Push
Likely you will need to utilize "$[no-wait]" or other control mechanisms we have available, but that depends on what you are trying to push, and how the device communication looks like.
Apologies for the late reply.
Can you please enable "Device output logging" in "Zones > Your Zone > Debug mode"?
Re-run the push, and please post how the device communication looks like.
As the log suggest, Unimus was not able to recognize any known output from the device:
Full Config Push behavior is documented on our wiki:Timed out waiting for any known data from device (timeout: 20000 ms)
https://wiki.unimus.net/display/UNPUB/Mass+Config+Push
Likely you will need to utilize "$[no-wait]" or other control mechanisms we have available, but that depends on what you are trying to push, and how the device communication looks like.