handling signed integers greater than 31 bits

13 years ago

Hi Tim,

Thank you for your interest in our product.

Normally our SNMP API gives the negative value if it receives a value higher than the range for Integer32.It is the actual behavior according to the standards.If your require positive values even for the values which is out of range for Integer32 you can handle it in your code after receiving the values.

If you get the value which exceeds the range from your server you will be receiving the negative value from our SNMPAPI.You can convert the value to positive by adding 2^32 for the value received ,so that you will be getting the exact value which you require.

But this workaround will be having a problem when the server originally sends the negative value.You will be facing a problem with wrong values when server originally sends the negative value.In order to avoid this type of problem you should definetly define the correct data types accordingly.

Trust the information provided is helpful,

Thanks & Regards,
Jyothi.

tjyothi

handling signed integers greater than 31 bits

13 years ago

Hi Tim,

Thank you for your interest in our product.

Normally our SNMP API gives the negative value if it receives a value higher than the range for Integer32.It is the actual behavior according to the standards.If your require positive values even for the values which is out of range for Integer32 you can handle it in your code after receiving the values.

If you get the value which exceeds the range from your server you will be receiving the negative value from our SNMPAPI.You can convert the value to positive by adding 2^32 for the value received ,so that you will be getting the exact value which you require.

But this workaround will be having a problem when the server originally sends the negative value.You will be facing a problem with wrong values when server originally sends the negative value.In order to avoid this type of problem you should definetly define the correct data types accordingly.

Trust the information provided is helpful,

Thanks & Regards,
Jyothi.

tjyothi

handling signed integers greater than 31 bits

13 years ago

Hi Tim,

Thank you for your interest in our product.

Normally our SNMP API gives the negative value if it receives a value higher than the range for Integer32.It is the actual behavior according to the standards.If your require positive values even for the values which is out of range for Integer32 you can handle it in your code after receiving the values.

If you get the value which exceeds the range from your server you will be receiving the negative value from our SNMPAPI.You can convert the value to positive by adding 2^32 for the value received ,so that you will be getting the exact value which you require.

But this workaround will be having a problem when the server originally sends the negative value.You will be facing a problem with wrong values when server originally sends the negative value.In order to avoid this type of problem you should definetly define the correct data types accordingly.

Trust the information provided is helpful,

Thanks & Regards,
Jyothi.

Guest

handling signed integers greater than 31 bits

13 years ago

Hi Jyothi,

Unfortunately I don't think you've really answered my question. the backend servers that my snmp server is monitoring do not return negative status counter values themselves. However, the snmp server assigns constant negative values such as -1 or -2 to certain status counters (usually to indicate they are not supported or are invalid). My backend servers use the equivalent of 32 bit unsigned integers for their status counters, which means they can hold positive integers in excess of 4 billion.

My problem is that my snmp server correctly handles integer values returned from the backend servers which are larger than 31 bits. But the NIB definition for the counters uses a syntax of Integer32. We need the Integer32 syntax so that we can store both positive and negative integers, i.e. both normal counter values and those constants set like -1 and -2 set internally by my snmp server. So, what I want to do is to find a syntax for my NIB definitions which can hold positive integers greater than 4 billion, but can also cope with negative numbers. Unsigned32, Counter32 and Counter64 don't currently do this.

I hope this makes sense, and if not please feel free to ask me for clarification.

Regards,

Tim

tjyothi

handling signed integers greater than 31 bits

13 years ago

Hi Tim,

Greetings!!!

There is no such data type available which holds positive integers greater than 4 billion, but can also cope with negative numbers.

Thank you for your understanding,

Thanks & Regards,
Jyothi.

Response title

Attachments

New to this Portal?