Hi all,
I have to poll an SNMP device and provide support to two different MIBs, depending on the device's software version. In most parameters, I have used dynamic OIDs to allow for this behavior however, there is a discreet parameter that I'm having trouble adjusting.
In the first image you can see that, in an older MIB version, there are 7 possible values, which are then mapped to a set of display values in a discreet parameter. However, on the second image (related to a newer MIB version), there are 9 possibilities and the translation to the display values is different.
I’ve tried to fix this issue by using dependency Ids (parameter with the device's software version) and values:
But this is not working as I expected. DIS validator shows duplicated param major issues and it seems that the display value of the parameter will always be the last one in the discreet list for a given value (i.e., value 3 is assigned to both “Charging” and “Low”, but despite the newer MIB version (dependencyValue=”7”) being in use and not the older one (dependencyValue=”1”), the result is “Low”).
Is there an alternative approach in situations like these or is this the correct one and I’m just doing something wrong? Note that the solution must be applicable to DataMiner version 10.1.0.0-11319. I have also thought about creating an extra parameter to read the value, but that would damage alarm templates associated with this specific parameter.
Thank you in advance!
Hi Diogo,
What you tried there with dependencyValues there was a very good try making full sense.
However, the dependencyValues feature was very likely not designed to work that way and expects unique Discreet/Value tags.
As far as I can tell, your best shot will be to indeed add an extra (hidden) parameter for the polling, processing the value in a QAction and updating the displayed parameter from there.
You should be able to avoid the breaking changes (avoid breaking existing alarm templates) by re-using the current parameter as the displayed one, not updating current Discreet tags and adding new ones with new Discreet/Values for the new values to be supported.
Regards,