I have a SNMP Parameter (PID 21) of type double. The device sends in exception value "-".
This character is of a different interprete type.
I'd like to add it as an exception but am not able to, even after adding the Others tag.
The parameter only reflects "Not Initialized" when testing.
I referred to the information on exceptions found here and here.
I can't change the interprete type of Parameter 21 as it needs to be trended.
Currently, I tested with the below:
<Param id="21" trending="true">
<Name>sensor1Value</Name>
<Description>Sensor 1 Value</Description>
<Information>
<Subtext>
<![CDATA[Value of Sensor]]>
</Subtext>
</Information>
<Type>read</Type>
<Interprete>
<RawType>other</RawType>
<Type>double</Type>
<LengthType>next param</LengthType>
<Exceptions>
<Exception id="1" value="-1">
<Display state="disabled">N/A</Display>
<Value>-1</Value>
</Exception>
</Exceptions>
<Others>
<Other id="5521">
<Display state="disabled">N/A</Display>
<Value>-</Value>
</Other>
</Others>
</Interprete>
<Alarm>
<Monitored>true</Monitored>
</Alarm>
<SNMP>
</SNMP>
<Display>
<RTDisplay>true</RTDisplay>
<Decimals>3</Decimals>
<Positions>
<Position>
<Page>Control</Page>
<Column>0</Column>
<Row>2</Row>
</Position>
</Positions>
</Display>
<Measurement>
<Type>number</Type>
</Measurement>
</Param>
The parameter that the incoming symbol is compared with:
<Param id="5521">
<Name>exceptionParam</Name>
<Description>Exception</Description>
<Type>fixed</Type>
<Interprete>
<RawType>other</RawType>
<Type>string</Type>
<LengthType>fixed</LengthType>
<Length>1</Length>
<Value>-</Value>
</Interprete>
</Param>
It would be highly appreciated if anyone can share how the exception can be implemented for this scenario. Thank you in advance!
Hi Rajesh,
I just tested a couple of parameters with a similar situation.
If you add this XML to your parameter 21 and remove the tag "Other" this should work fine.
<Exceptions>
<Exception id="1" value="-">
<Display state="disabled">N/A</Display>
<Value>-</Value>
</Exception>
</Exceptions>
Hi Rajesh,
After reading the documentation you added, I think the issue is the <Value> tag inside <Other>. Although the parameter will be shown as N/A on DataMiner in case '-' comes in, this tag represents the value that will be assigned in the background (for alarming or trending). In this case, you are setting the parameter to '-' when '-' comes in, which causes the same conflict you were trying to handle and might be the reason DataMiner can not resolve this in the background and won't show the N/A. Can you try changing the <Value> to a numeric value?
Thank you for the suggestion Robin. I’ve attempted that too and some other combinations too as we discussed and tested over the call. Unfortunately, it still does not work at this point in time.