Specifications

2.1.3. MIB database – Management Information Base

OID, which uniquely identifies every value in SNMP, is formed by a sequence of numbers divided by

points. This number is derived from superordinate element's OID, divided by a full stop from the current

number. The entire tree structure is saved to MIB database. In addition, MIB database contains the

names and descriptions of individual values (OID). Other values can be added to MIB database using

part of the structure saved in the MIB file.

An example of OID is 1.3.6.1.4.1.33555.2.1.1.3 in RipEX MIB database which corresponds to serial-

Number – (Unsigned32) – Manufacturing serial number of the product.

SNMP does not require an MIB database to work as SNMP packets only include OID; if you don't know

the right OID, however, database can help you retrieve it.

2.2. SNMP in RipEX

In RipEX SNMP protocol can be used to:

• Read configuration parameters from MIB,

• Read operation statistics on the radio channel, and

• Sends traps when set thresholds for monitored values are exceeded (TxLost [%], Ucc, Temp, PWR,

VSWR, ETH [Rx/Tx], COM1 [Rx/Tx], COM2[Rx/Tx])

For detailed description of individual values refer to section RipEX MIB bellow.

RipEX utilises SNMP versions SNMPv1 and SNMPv2c – it uses community string for authentication,

which is fixed to "public" and cannot be changed. SNMP uses UDP protocol for communication; delivery

checks are implemented from version 2.

By default RipEX uses UDP port 161 (SNMP) for queries. Manager, which sends the query, dynamically

chooses a port from which it sends its query to RipEX port 161. RipEX replies from port 161 to the dy-

namically selected port of the manager.

RipEX launches SNMP agent automatically on start-up and it cannot be switched off by user. Only

traps' behaviour can be influenced (see Alarm management settings, RipEX manual, Adv. config.

RipEX sends alarm states (traps) to manager from port 162 (SNMPTRAP). Users cannot change this

port number in RipEX.

When using SNMP over radio channel we recommend setting RipEX to router mode. From the point

of radio network, SNMP is typically a standalone application sharing the radio channel with others.

Thus it causes collisions, which are automatically resolved by the radio channel protocol in router mode.

The radio channel uses no protocol in bridge mode, meaning two competing applications can only be

run at a great risk of collisions and with the knowledge that packets from both applications may be irre-

trievably lost.

http://www.racom.eu/eng/products/m/ripex/h-menu.html

SNMP for RACOM RipEX