Hello Dojo,
I'm experiencing a weird issue with a driver where the elements will start showing certain parameters as "Not Initialized" on Cube after the element runs for an extended period of time. However, when I grab the value of the parameters using SLNet calls, I see that the parameters have the correct value as well as when I log the values being set in the driver.
It also only seems to effect on agent in the DMS as when I connect from another, Cube will show the correct value.
It's worth noting that this driver has is subscribed to Failover event messages on the DMS so it could be related to faulty subscriptions.
Thank you,
Bauti
Sorry if my questions give that impression. I have a driver that is monitoring the failover status and a GQI that subscribes to elements using that driver.
Hi Bautista,
I'm interested in this issue you've discovered, as I have also experienced something similar on our DMS. "Not Initialized" when connected via certain DMAs, but normally fine when connecting via the DMA that is hosting the Element.
We have however noticed that retrieving the parameter on a Dashboard from an affected DMA doesn't have the issue – do you see something similar? It would also be interesting to know which DataMiner version you are running, as we are on an older version, but a newer version of Cube.
This is DataMiner version 10.5.0.0-CU6 and Cube version 10.6.2605.3050
I will note that since adding alarming to these parameters, the issue has gone away
Hi Bautista,
I noticed several questions around failover monitoring.
Instead of subscribing to elements to detect start/stop transitions during a failover, a more efficient option could be to enable a SNMP manager that forward notifications when an element restart after a failover.
Subscribing to elements after a failover switch seems prone to the corner the cases that you are encountering.