Hello,
I would like to alarm when a certain build version is lower than the current approved build version for software on a card. For example, 9.42.2.198127 is approved and anything less will need to be upgraded to the new version and anything higher should not be allowed which will need to be reverted back.
I have tried using wildcards such as 9.42.2.* being NORMAL and 9.42.3.* being CRIT HI, but that doesn't work.
Any ideas on how to get this to work?
Thanks,
Kevin
Hi Kevin,
Since this is a string, it won't be possible to use "higher than" or "lower than". Instead, you would need to use wildcards, like you already do, but then you need to make sure you match everything you want to capture...
So, instead of having higher than 9.42.3.*, you can click on the plus icon while editing this CRI HI field and have more wildcards you can enter, this way you can add 9.42.4.* ; 9.42.5.*; 9.42.6.* ; 9.43.* ; 9.5* ; 10.* ; etc.
It might require you to specify a lot more possibilities, but hopefully this can help you to move forward.
Note that it's technically not required to specify a NORMAL value. Everything which doesn't match the alarm thresholds, will be considered normal. The order of checking the wildcards, is from the high to low severity zone. First DataMiner will check if it matches CRI, if not, then DataMiner checks MAJ, etc.
Also a question mark is supported for one character, this is documented here: Configuring normal alarm thresholds | DataMiner Docs
Bert
Hi Kevin,
Can you try something like this?
In other word, you only define critical alarms for the non-approved version.
Let me know if this fix your request.
Thank you for confirming.
The build version parameter is of String type. To set an alarm for a String type parameter, we need to define the possible string values, as string values do not have thresholds. If you can define the possible strings, you can then include them in the multiple alarms.
Hi Kevin,
Another option, which implies updating the connector, is processing the software version and splitting this information in 4 numeric parameters. Following your example, the connector should implement the following parameters:
- Software Major version: 9
- Software Minor version: 42
- Software Revision: 2
- Software Build: 198127
In this way, you can monitor the version as a number.
Hope it helps.
Hi Jeeva,
I tried that, but unfortunately that did not work. It still shows the build version of 9.41.3.196733 as Normal or Green.
I have the CRIT LO as 9.42.1.* and the CRIT HI as 9.42.3.*.