Rule number simply tells you where you're at on the list of OID maps. Click "next" and "prev" to scroll
through the list. To advance directly to a specific map, enter the desired number in the "Map #" box, then
click Update.
The local object data may be written periodically, or when it changes, or both. To send upon change (send
on delta), check the first box and enter the amount by which the local object must change before being
written to the remote device. To guarantee that the remote OID will be written at least occasionally even if
the data does not change, check the second box and enter some amount of time. This time period will be
referred to as the "maximum quiet time".
Data from the local object may be manipulated before being written to the remote OID. The local data is
first multiplied by the scale factor. The offset is then added to it. The data is then sent to the remote SNMP
agent. Enter the full OID to be written, the SNMP ASN data type to be written (select from list), and the
location (device). The names in the device list are defined in the Devices page.
Important note about data type: SNMP does not have a universally accepted representation for floating
point. The most commonly used means of representing real data is scaled integers, and this method is
supported by BB2-7010. IEEE 754 is not recognized as an SNMP standard and is not used. X.690 defines
an encoding for real data, but it is inefficient and little used. A common recommendation is to use
ASCII string representation of floating point data, and this method is supported by BB2-7010 (Octet String
Num). Another known but application specific implementation is the ASN OPAQUE FLOAT used in netsnmp
applications. This method is also supported by BB2-7010 but should be tested to confirm compatibility.
11. Using the BB2-7010-02 as an SNMP Client (Manager)
file:///C:/AAA_CSI/Literature/2015 User Guides/BB2-7010/BB2-7010 ...
6 of 8
10/16/2015 12:46 PM