Unimus forum

neoprogger wrote: ↑

Mon May 14, 2018 7:47 am

Hi,
Any chance to support our Aruba 2930f?
Should be compatible to procurve switches, but it's stuck at "Discovery"

Hi,

Could you please contact me over a PM to setup a debugging session to look at this?

Thanks!

Just an update, 1.7.1 is out:
viewtopic.php?p=1137#p1137

Unimus version 1.7.1 is being released today! 1.7.1 is a hotfix release for issues found in the original 1.7.0 release. We highly encourage all users to update to this version. The 1.7.0 release brings 4 new major features: - mass config push (network automation) - network scanning (device discovery...

Thanks, this is much appreciated!

Will let you know as soon as implementation is finished.

We found the issue, it was caused by devices that have multiple available connectors (SSH + Telnet). The push invoker would tell the push handler to push twice to those devices (once per connector). We fixed this, so the push invoker will properly use the most secure available connector for each dev...

Got the logs, thank you. It seems Unimus internal components are not communicating properly to each other. We are investigating. The log shows push to 28 devices! How do we know the other 8 it just decided to pick? The Config Push handler receives some devices twice. (internally, 8 devices are dupli...

Could you please run Unimus in debug mode and try to replicate an incorrect run like this? Please send me the logs afterwards.

Thanks!

We created tickets for this from the Beta thread, so indeed it wont be lost

We created a ticket for this:
https://tracker.unimus.net/browse/UN-322

One question tho, would it be enough to schedule a Config Push to run one time, or do we actually want it to have scheduled repeatedly (using the schedules from the "Schedules" configuration)?

Hi,

We would be happy to add support.
Please PM me to work out the access.

Thanks!