RAy3 utilises SNMP versions SNMPv1 and SNMPv2c – using a community string for authentication, which is by default “mwl-snmp“, but can be changed. SNMP uses UDP protocol for communication; delivery checks are implemented from version 2 onwards.
The RAy3 MIB module complies with Severity level 3 validation.
By default RAy3 uses UDP port 161 (SNMP) for queries. The manager, which sends the query, dynamically chooses the source port. The use of destination port 161 is fixed. RAy3 replies from port 161 to the port dynamically selected by the manager.
RAy3 launches the SNMP agent automatically on start-up if enabled. RAy3 also sends alarm states (traps) to the manager via the port 162 (SNMPTRAP).
To see the RAy3 MIB table, download it from the RAy3 web interface () and use any document reader you prefer.
Since RAy3 FW 18.104.22.168, the SNMP non-table items OIDs are defined in accordance with the RFC (ending ‘.0’) – to improve SolarWinds compatibility. Keep this in mind when upgrading RAy3 firmware. Firmwares < 22.214.171.124. are able to reply to SNMP queries with OIDs ending with .0, but the reply does not contain .0 in its OID. This works fine (for example) with Zabbix NMS, but (for example) SolarWinds does not accept such replies.
Since RAy3 FW 126.96.36.199, the SNMP product OID of RAy3 changed from ‘1’ to ‘4’. Keep this in mind and replace the older RAy3 NMS configuration. Find more details in Section 188.8.131.52, “RAy3 Firmware and Template Compatibility”.
MIB can be read via any text editor, but it might be better to browse it (see the trap’s variable bindings, OID’s unit, descriptions, OID tree, getting values from RAy3 units, receiving and testing traps, etc.) in some special SNMP browser such as MIBBrowser from iReasoning. The following section explains some details about RAy3 MIB for firmware version 184.108.40.206. MIB consists of “revision history” information so you can quickly find out what has been changed.
CSV file containing all proprietary RAy3 OIDs can be sent upon request, or exported from MIBBrowser software.
The RAy3 MIB module complies with the Severity level 3 validation.
Supported MIBs and its OIDs:
Values from general MIBs such as SNMPv2-MIB, IF-MIB, RMON, …
Proprietary MIB – RacomRay3
Alarm states, services states
Environmental information (e.g., temperature, voltage, …)
Reading configuration parameters
Reading operation statistics (reliability, BER, ETH throughput, RSS, …)
Sending traps (thresholds are configurable)
RAy3 MIB utilizes custom types declaration so that SNMP reply is numeric, but each number corresponds to a particular meaning. E.g., Alarm states:
0 – na
1 – up
2 – down
3 – ack
Make sure your NMS is configured to translate numeric values to their meaning correctly (Value mapping in Zabbix).
Some of the returned values are in decimal notations. E.g., temperature returned as 4800 means 48. If a particular value requires it, it also has a predefined unit such as degrees of Celsius, Volts, decibels, percent, … Again, make sure you utilize your NMS with correct unit.
Current MIB can always be downloaded from RACOM website together with Zabbix templates.
The SNMP agent is switched off by default. You can enable or disable it in themenu.
The SNMP community string is “mwl-snmp” by default, but can be changed to another string.
All system alarms are listed on this screen. Inactive alarms are colored white with an “OK” text label. Active alarms are colored according to the severity of the alarm with a text message describing the measured value status.
Alarm severity scale:
If you click on the “Alarm” text (if any Alarm is UP) on the top of the screen (next to the exclamation mark), you will be redirected to this Alarms – Status screen.
Alarm acknowledgement is a way to let the operator confirm the system is in alarm state. Only an active alarm can be acknowledged.
Multiple selection of active alarms (to acknowledge groups of alarms) can be performed using Shift or Ctrl keys.
The link diagnostic system monitors the operation of the unit. It generates various output of events – system warnings and alarms. The event is always written to the system log and indicated in the status bar and Alarm – Status screen. Some events have adjustable thresholds. Events with no adjustable thresholds may either be Enabled or Disabled. If they are Disabled, the system event is not activated even if the system status is changed. For each event you can choose whether the SNMP trap should be sent if the event occurs.
Configurable Alarms / Events:
Inside temperature [°C]
Temperature inside the unit (on the modem board)
Voltage min [V]
Supply voltage Lower threshold
Voltage max [V]
Supply voltage Upper threshold
Received Signal Strength
Mean square error
Bit Error Rate is registered at the receiving end; instantaneous value
Net bitrate [Mbps]
The system warning is generated when the radio channel current transfer capacity drops below the set threshold
Air link down
Radio link interruption
Eth1/Eth2 link down
Corresponding user Eth link (Eth1/Eth2) on station interrupted
Warning is generated when WiFi passphrase is not set or WiFi adapter is permanently enabled
Event is generated when Net bitrate of the air channel changes (e.g. because of ACM operation)
For all these traps, there are also special OIDs for the alarm states. The states can be one of “n/a”, “up”, “down”, “ack”. See the Application “Alarms” within the RAy3 template.