Page 1 of 1
[Fixed in 2.2.2] Observium NMS sync
Posted: Thu Mar 10, 2022 3:44 pm
by kingtrw
I'm experimenting with the NMS sync option - I've created a connection and specified our observium server, and credentials -- but the 'run sync now' button is greyed out.
I have the option to provide new sync rules, but the documentation
https://wiki.unimus.net/display/UNPUB/O ... m+importer implies that specifying group IDs is optional. I don't know what group IDs are (I don't have any groups configured in observium) so I'm not sure what's missing.
Many thanks!
P.S. Using 2.2.1
Re: Observium NMS sync
Posted: Sat Mar 12, 2022 9:17 pm
by kingtrw
Update - I've found that if I include a group of "#1" then I can save and initiate a sync - but the sync instantly fails with a 501 error. If I try specifying the server using https instead (which I know to be incorrect, as I don't have https enabled on observium) it shows that it's trying to connect, but then fails.
Re: Observium NMS sync
Posted: Mon Mar 14, 2022 12:45 pm
by Vik@Unimus
No need to test, we can confirm there is a bug. The device group field should not require an input as it is not a required field.
Our team is working on a fix and it should be included in the upcoming release coming out this week.
Re: Observium NMS sync
Posted: Wed Mar 16, 2022 1:20 pm
by kingtrw
Awesome, thanks!
Re: Observium NMS sync
Posted: Thu Mar 17, 2022 9:16 pm
by Vik@Unimus
We have a new Unimus version 2.2.2 live now, which contains a fix for Observium and the requirement not allowing keeping the device field empty. You can find a new version below
https://unimus.net/download
If you get a chance, give it a try and let us know if it worked as expected.
Re: [Fixed in 2.2.2] Observium NMS sync
Posted: Fri Mar 18, 2022 9:57 am
by kingtrw
I've just checked and while an issue with requiring group IDs has been fixed, it's still not working - but I'll create a new post for that
