SNMP

Print version

2. SNMP

2.1. Simple Network Management Protocol

SNMP is a simple, widely used and useful standardised protocol typically used by Network Management Software (NMS) to read values from devices. Values can be obtained at regular intervals or on requests, saved to a database and then displayed as graphs or tables.

SNMP also enables devices to generate (trigger) the alarms by themselves and notify the NMS explicitly (SNMP traps).

2.1.1. How does SNMP work?

SNMP requires two parties for communication:

  1. SNMP “manager” (software installed at your computer)

    • You can use commercial software or free software such as Zabbix, Zenoss, Nagios, Cacti, etc. If you want to read values manually, you can use tools such as snmpwalk, snmpget or Mibbrowser software.

  2. SNMP “agent” (a part of firmware in remote devices such as RipEX)

    • The agent receives SNMP requests to query information and responds to the manager. Several managers may read values at once and they can send their requests at any time. Alternatively, the agent sends SNMP traps whenever the monitored values (watched values in RipEX, e.g. temperature) are outside the threshold range. RipEX is capable of sending SNMP traps to up to two SNMP managers (since the firmware release 1.3).

2.1.2. SNMP communication

In SNMP, each value is uniquely identified using Object Identifier (OID). Standard communication starts by sending a request and then the response is returned. Alternatively, an agent can send an SNMP trap.

SNMP Communication

Fig. 2.1: SNMP Communication

A request is sent

the manager sets message-type to GET, includes OID for the required value and sets this value to NULL.

A response is returned

the agent sets message-type to RESPONSE and sends the requested value along with its OID back to the manager.

A trap is sent

to the manager without its request.

Basic Message Types

GetRequest

returns a single value.

GetNextRequest

returns the next value (using the next OID).

GetBulkRequest

returns several values in a single packet (for example, temperature, voltage, number of transmitted messages or bytes per second, etc.).

Trap

sent from the agent to the manager whenever any monitored value is beyond its thresholds.

SetRequest

used to set various parameters (unsupported by RipEX).

2.1.3. MIB database – Management Information Base

The MIB is a virtual database used for managing the entities in a communications network.

The MIB hierarchy can be depicted as a tree with a nameless root, the levels of which are assigned by different organizations. “Higher-level” MIB OIDs belong to different standards organizations, while “lower-level” OIDs are allocated by associated organizations (e.g. RACOM).

OID example:

RIPEX::serialNumber
serialNumber OBJECT-TYPE
-- FROM RIPEX
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "Product serial number."
::= { iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) racom(33555) ripex(2) station(1) device(1) 4 }

As you can see, numbers 1.3.6.1.4.1.33555 are the “higher-level” OIDs. The “lower-level” OIDs are .2.1.1.4 which are allocated by RACOM.

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, …)

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

RipEX utilises SNMP versions SNMPv1 and SNMPv2c – using a community string for authentication, which is by default “public“, but can be changed. SNMP uses UDP protocol for communication; delivery checks are implemented from version 2 onwards.

[Note]Note

The RipEX MIB module complies with Severity level 3 validation.

By default RipEX 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. RipEX replies from port 161 to the port dynamically selected by the manager.

RipEX launches SNMP agent automatically on start-up if enabled. RipEX also sends alarm states (traps) to the manager via the port 162 (SNMPTRAP). Users can change this port number in RipEX. Traps’ behaviour can be influenced (see Alarm management settings, RipEX manual, Adv. config.).

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 irretrievably lost.

2.2.1. Limitations

SNMP is primarily designed for Ethernet networks, where generally, bandwidth capacity is not an issue. By contrast, radio bandwidth capacity is very limited and RipEX mostly works over the radio channel. For this reason, special care is recommended while configuring NMS. If badly configured, NMS can take a significant portion of the network capacity or can even overload the network completely.

Bandwidth Consumption

It is important to realise that the average size of a single request and response to a specific OID is approximately 184 Bytes each. The entire MIB for a single RipEX with one neighbouring RipEX is approximately 48 kilobytes. Based on the limitations and the MIB size, we recommend to query only carefully selected OIDs over the radio channel and not all possible data. Set SNMP query time intervals in your NMS as long as possible. The shortest recommended interval ranges from several minutes to tens of minutes.

Wherever possible, use the RipEX Ethernet interface for SNMP communication to free up the radio channel.

[Note]Note

There are many Network Management Systems available on the market. Whichever you choose, keep in mind the described limitations. E.g. never use NMS, which can download only the entire remote device MIB and not single OIDs.

Bandwidth Efficiency Tip

If you wish to monitor many watched values (VSWR, Temperature, UCC, …) from remote stations connected over the radio channel and you have a star topology network, you can improve bandwidth efficiency by reading OID values only from the Master (Repeater) RipEX station.

The advantage of the above is that the watched values from remote stations are broadcast in regular intervals and saved in the Master (Repeater) RipEX. These values from neighbouring stations have their own OID’s and can be downloaded from the Master (Repeater) RipEX.

In the picture below – Master RipEX station periodically reads watched values from its neighbouring Slave stations. Whenever the NMS requests any value mentioned, the reply is sent only from the Master station (over Ethernet) saving radio bandwidth. SNMP uses radio link only for sending SNMP Traps from any Slave to the NMS.

NMS communication with Slave stations

Fig. 2.2: NMS communication with Slave stations

[Note]Note

In such a case, watched values from neighbouring stations are displayed as part of the Master (Repeater) station.

The OID of individual remote stations is based on the order in the Neighbours menu of RipEX web interface (i.e. 1st neighbour has the last OID digit set to 1, 2nd neighbour to 2, etc.). Due to its dynamic character, it may happen that the order might be changed each period (e.g. once a day), keep this in mind!

[Important]Important

To avoid this confusion, using Zabbix “dynamic indexes” is suggested. See the the section called “Reading Remote Watched Values” for more details about dynamic indexes and their usage with RipEX units.

2.2.2. RipEX SNMP Settings

SNMP agent is switched off by default. To enable it, go to the settings menu and click on the SNMP button. You can set the Community, turn on SNMP traps and define two trap destination IP addresses and ports.

[Important]Important

Thresholds for all SNMP traps can be configured in the RipEX web interface, Settings → Alarm management. Since detailed description of RipEX SNMP traps settings can vary based on the current firmware, please kindly refer to the online Help accessible through the RipEX web interface or see the User manual, Chapter Settings (http://www.racom.eu/eng/products/m/ripex/h-menu.html#settings).

2.2.3. RipEX Traps Description

The trap is sent whenever any of the following watched values are beyond their threshold ranges:

  • RSS (Received Signal Strength)

  • DQ (Data Quality)

  • TX Lost (The probability of a transmitted frame being lost)

  • UCC (Power voltage [V])

  • Temperature [C]

  • RF Power [W]

  • VSWR (Voltage Standing Wave Ratio, 1.0 = the best ratio, 1.0 – 1.8 = acceptable ratio, > 2.5 = indicates a serious problem in antenna or feeder)

  • Ethernet RX/TX Packets ratio (Ratio between received and sent packets over Ethernet)

  • COM1/2 RX/TX Packets ratio (Ratio between received and sent packets over COM ports)

  • HW Alarm input

  • Hot-Standby (SNMP trap containing active station identity – sent by the active station)

  • Backup paths system (Backup path state and Alternative path state changes)

  • Unit ready (the hardware alarm output or the SNMP trap indicates that the RipEX radio is ready to operate)

2.3. Network Management System – ZABBIX

To access our SNMP values, any Network Management System (NMS) can be used. However, we recommend using the ZABBIX open source monitoring system. It can be downloaded at: http://www.zabbix.com/download.php.

The Zabbix website provides the following short description:
Zabbix is the ultimate enterprise-level software designed for monitoring availability and performance of IT infrastructure components. Zabbix is open source and comes at no cost.

If you have chosen the Zabbix software, please read the following pages where we offer a basic Starting Guide to RAy2 and Zabbix co-working.

Whatever your choice of NMS, these sections may provide general hints and tips.

[Note]Note

The following guide was tested with Zabbix release 3.0.1. If you use any older release, refer to the previous version of this Application note (in the Archive section).

Take the opportunity to remotely access and test a live Zabbix demo. Contact us for access details.

2.3.1. Installation and Documentation

Due to security requirements and the mission-critical nature of the monitoring server, we believe UNIX is the only operating system that can consistently deliver the necessary performance, fault tolerance and resilience.

Zabbix has been tested on the following platforms:

  • AIX

  • FreeBSD

  • HP-UX

  • Linux

  • Mac OS X

  • Open BSD

  • SCO Open Server

  • Solaris

  • Tru64/OSF

  • Windows 2000, Windows Server 2003, Windows XP, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2012, Windows 8 (Zabbix Agent only)

For further details, visit Zabbix Documentation at http://www.zabbix.com/documentation.php. It contains a large body of information about installation steps, configuration, performance etc. If you are unsure how to proceed with any task, refer to the Zabbix documentation first. You can find an installation guide there, too.

This Guide does not present all Zabbix settings, but should help you incorporate the RAy2 SNMP functionality into the Zabbix software.

[Note]Note

The following guide requires the use of MySQL database in Zabbix. If you choose other software, you will need to alter at least the trap handling bash script provided. This guide was tested in the CentOS 7 Operating System; some tasks may require a different approach in other systems.

Windows Installation

If you choose to use the Windows platform as the host operating system for Zabbix, VMware/VirtualBox software and then the Zabbix Appliance. The Zabbix Appliance can be downloaded from
http://www.zabbix.com/download.php
. Please remember that Zabbix Appliance is not intended for serious production use at this time.

VMware download: https://www.vmware.com/support/
VirtualBox download: https://www.virtualbox.org/wiki/Downloads
See the respective documentation to install and use virtualisation software.

2.3.2. Templates

After successful installation, you can import any of the predefined templates. Each template is the collection of Zabbix Items corresponding to a set of OIDs, triggers, graphs and applications. The template can be easily linked to any monitored host (RipEX) and you can have access to the desired values very quickly.

What Templates do we Provide?

The Templates list:

  • Name: RipEX Template

    • Consists of all specific OIDs provided by RACOM

    • Implements one neighbouring RipEX monitoring

  • Name: RipEX – RFC1213 Template

    • Consists of supported RFC1213 OIDs

  • Name: RipEX – RS232 Template

    • Consists of supported RS232 OIDs

  • Name: RipEX – SNMP Trapper Template

    • Consists of SNMP trapper items, which are triggered by 15 kinds of traps

  • Name: PING Template

    • Pings a defined host and triggers whenever the host is unreachable

All templates can be downloaded from the RipEX Download site at http://www.racom.eu/download/hw/ripex/free/eng/3_fw/RipEX_Zabbix_templ.zip.

How do I Import the RipEX Templates?

In order to import the template, click on the Configuration → Templates button at the top of the Zabbix web page. Select the Import Template button at the top right corner.

Importing Template button

Fig. 2.3: Importing Template button

[Note]Note

With Zabbix 3, Value mappings can be imported together with the template.

Select the RipEX template file and Import that file. Repeat this step for each template.

Importing Template options

Fig. 2.4: Importing Template options

Now you can see the RipEX template in the Template list window along with the other default templates.

[Note]Note

If you already imported the template and you need to update it, just import the newer version with the same name and the current template will be automatically overwriten.

Each Item has its Description, SNMP OID number, community string, UDP port (161), key, update interval and other parameters. One of the key parameter is the update interval, because it defines how often Zabbix will request various replies from the RipEX stations. This interval is predefined to 30 minutes, but you should consider changing it to suit your radio network infrastructure.

The individual items can be in an active or disabled state. By default, only some items are active based on their importance – see the next chapter for more information. If you wish to monitor more values, activate the desired ones. But as already mentioned, preferably use the RipEX Ethernet interface for SNMP communication to free up the radio channel. If this is not possible, consider carefully whether monitoring other values is necessary.

Only monitor the values which you really need and with reasonable update times.

The items are divided into the usage groups, called Applications in Zabbix. These applications serve for better clarification of the defined items.

If you wish to be notified whenever any monitored value is out of its threshold range, you can define a Trigger for it. These notifications are viewable on the Zabbix dashboard, item history or you can have e-mail/jabber/sms notifications enabled. Each notification can have one of six predefined severity levels (warning, critical, …).

We also provide several triggers within the templates. Triggers defined in templates cannot be edited within individual hosts, which means you cannot define various threshold ranges for hosts and each host would have the same threshold range. Please define your own triggers within each individual host.

[Note]Note

You can use a Clone option to create a copy of any template item or trigger for an individual host. In this case, you can edit its predefined values to meet your requirements for each host separately.

Graphs are automatically created for each monitored numeric value, but you can also create special graphs with several values on a single graph. We provide 4 predefined graphs containing some basic watched values like temperature, UCC etc.

For more information, see the Zabbix documentation. You can delete, add or edit any template component. The predefined state serves as a quick start, but you do not have to use them at all and you can create your own set of monitored values/items.

Which Values/Items Should I Monitor?

The templates themselves are fully scalable and consist of many items. However, monitoring all of them is not required in a routine situation. Pre-activated items in RipEX default templates are:

  • RipEX Template

    • Pre-activated Items: 5

    • Modem temperature (°C), RF power (W), TX lost (%), UCC (V), VSWR

  • RipEX – RFC1213 Template

    • All items are disabled by default

  • RipEX – RS232 Template

    • All items are disabled by default

  • RipEX – SNMP Trapper Template

    • Five SNMP trap items and triggers are enabled by default. DQ and RSS triggers need to be cloned for individual hosts, because we cannot predefine remote hosts IP addresses. See Section 2.4.2, “SNMP Traps” for more information.

  • PING Template

    • Pre-activated Items: 1

    • Default Update Time: 30 minutes

    • The only active item checks the host reachability and triggers an alarm if the host is not reachable.

[Note]Note

If you need to monitor more than one remote RipEX station, you need to “clone” existing items for the remote station watched values.

Reading Remote Watched Values

Remote Watched values are read by Zabbix using the Dynamic indexes. This works on a basis of “snmpwalk” through all available remote units (neighbours) of specific RipEX (host). When it finds the correct neighbour (correct IP), it reads the watched value for this neighbour. E.g. local RipEX has 3 neighbours (10.10.10.1, .2 and .3) and we need to know the RSS level for the 10.10.10.2 host. Zabbix sends several “snmpgetnext” requests until it reaches the end of this SNMP branch (in our example, 4 snmpgetnext requests are sent). Thanks to this, Zabbix finds out that 10.10.10.2 has for example ID “2” and thus, Zabbix knows how to ask for the RSS value of this particular neighbour and sends the correct snmpget request. All values are readable by OID ending with this previously “unknown” ID.

[Note]Note

Without dynamic indexes, values for several remote units could be mixed together, because each History period, the IDs can be different for particular neighbours.

[Note]Note

Do not read remote watched values and remote statistic values from RipEX unit which is not reachable via Ethernet. If you read it from RipEX reachable via the Radio channel, it could send too much of data over the Radio channel and cause a decrease of available bandwidth for this link. Do it on your own risk and requirements (it is supported).

Each Host linked with a RipEX template automatically obtains {$NEIGHBOUR.1} user MACRO needed for reading remote watched values. This MACRO defines the IP address of the first RipEX neighbour of the particular “local” RipEX (host). If the monitored RipEX has more than one neighbour, you need to add additional neighbours to its MACRO list. Go to the Configuration -> Hosts -> choose the particular RipEX -> Macros -> Inherited and host macros -> Click on the “Add” button and define other neighbours.

Host MACROs

Fig. 2.5: Host MACROs

Each Neighbour IP can be set as required. The default value for the first one is 192.168.169.169.

The {$NEIGHBOUR.1} user MACRO is also used for reading statistics of particular neighbours. The IP addresses are the same (since the firmware 1.6.x) and thus they do not need to be set separately. The only difference is that you also have a “RADIO BROADCAST” line is Statistics which is NOT in the Neighbours menu (RipEX GUI). Configure it as a separate neighbour MACRO, but do not use it for remote watched values.

By default, reading the watched values is disabled. To enable it, go to the Configuration -> Hosts -> choose the host -> Go to the Applications -> Choose “Watched values – Remotes” and enable required values. If more than one neighbour is required, you need to “Clone” the existing Items and change the ID of the specific Neighbour. For example, if you have 3 neighbours, for each Item (RSS, DQ, Temperature, …) you need to:

  • Open this particular Item within the Host’s (local RipEX) watched values Items

  • Click on the “Clone” button

  • Change the ID from 1 to X, where X is the neighbour’s ID (2, 3, …), in the Name, Key and SNMP OID parameters!

  • Click on the “Update” button

  • Repeat the steps for the third neighbour as well

  • Repeat the steps for all required Items

Remote Wached values - Item Cloning

Fig. 2.6: Remote Wached values – Item Cloning

[Note]Note

The same procedure must be done for Radio Statistics. By default, only the first neighbour and Total numbers are pre-defined. Broadcast and other hosts must be defined manually.

Valus from any neighbour can now be displayed in the Latest data menu.

Remote watched values - Latest values

Fig. 2.7: Remote watched values – Latest values

2.3.3. How to Import Monitored RipEX Stations?

Now you have a working template, but you need to define hosts (RipEX stations). Each RipEX station has its own IP address. The following steps will guide you through the Host Configuration.

To create a host, go to Configuration → Hosts and click on the Create Host button. Define the Host name and its IP address.

Defining the Host name and its IP address

Fig. 2.8: Defining the Host name and its IP address

Alternatively you can define a Group for the hosts. Creating a Group is straightforward. You can create a new one while creating a host or you can do so by going to the Configuration → Groups tab and clicking on the Create Group button.

Linking a template to the host(s) is achieved under the same tab or you can open Template settings and link any desired host to it.

You have to set the IP address and the port number (161) for the SNMP interface. Otherwise, you won’t be able to use any SNMP item.

The option “Use bulk requests” can be enabled with RipEX units. This feature enables sending multiple SNMP queries within one UDP datagram.

Defining the SNMP interface

Fig. 2.9: Defining the SNMP interface

[Note]Note

In this Host configuration menu, configure the Host Inventory to be filled in automatically.

Where can I See the RipEX Monitored Values?

To check monitored values, go to the Monitoring → Latest data tab and choose the desired host from the Menu.

RipEX latest data

Fig. 2.10: RipEX latest data

For each item, you can see a graph or a history table. If a trigger is configured for the item, the graph shows a line with a threshold value.

RipEX graph

Fig. 2.11: RipEX graph

2.3.4. Value Mappings

Responses from Several OID objects are unsigned integers, but these values do have a special meaning.

Example 2.1. deviceMode

  • “1” stands for “bridge” mode.

  • “2” stands for “router” mode.

Unfortunately, by default, you can see only the numeric values at the Zabbix front-end. The Value mappings are automatically imported with the RipEX template or it can be imported separately in the Administration – General – Value Mappings menu.

[Note]Note

This syntax feature is used throughout all MIB tables, not only the RipEX MIB table.

If you create any Value map manually, follow this procedure.

To add new value mappings, go to Administration → General → Value Mapping. Click on the “Create value map” button and insert the values, which are mentioned on the following lines. There is an Item list, which uses these value mappings (either link them manually or automatically by importing the template).

[Note]Note

There are also several value mappings used at RFC1213 and RS232.

Value Mappings List

RipEX.AlmStateItems:
-1 ⇒ unknownAlarm state – COM1 interface Rx to Tx packets ratio
0 ⇒ inactiveAlarm state – COM2 interface Rx to Tx packets ratio
1 ⇒ activeAlarm state – Device temperature
 Alarm state – DQ
 Alarm state – ETH interface Rx to Tx packets ratio
 Alarm state – HW Input
 Alarm state – RF Power
 Alarm state – RSS
 Alarm state – Tx lost
 Alarm state – UCC
 Alarm state – Unit ready
 Alarm state – VSWR
RipEX.BackupPathsStateItems:
0 ⇒ unknownBackup Paths 1 – Alternative Paths – Currently passive paths State
1 ⇒ upBackup Paths 2 – Alternative Paths – Currently passive paths State
2 ⇒ downBackup Paths 1 – Alternative Paths – Currently used path State
 Backup Paths 2 – Alternative Paths – Currently used path State
RipEX.comProtocol:Items:
0 ⇒ noneCOM1 – Protocol
3 ⇒ AsyncLinkCOM2 – Protocol
4 ⇒ ModbusTS 1 COM user protocol type
5 ⇒ IEC101TS 2 COM user protocol type
6 ⇒ DNP3TS 3 COM user protocol type
7 ⇒ UNITS 4 COM user protocol type
8 ⇒ ComliTS 5 COM user protocol type
9 ⇒ DF1 
10 ⇒ Profibus 
12 ⇒ C24 
13 ⇒ RP570 
14 ⇒ Cactus 
15 ⇒ ITT Flygt 
18 ⇒ SLIP 
19 ⇒ Siemens 3964 (R) 
20 ⇒ PR2000 
RipEX.deviceModeItems:
1 ⇒ bridgeStation working mode
2 ⇒ router 
RipEX.eDhcpItems:
0 ⇒ offEthernet interface DHCP mode
1 ⇒ server 
2 ⇒ client 
RipEX.eSpeedItems:
0 ⇒ autoEthernet interface bit rate and duplex settings
1 ⇒ s-100baseTX-Full 
2 ⇒ s-100baseTX-Half 
3 ⇒ s-10baseT-Full 
4 ⇒ s-10baseT-Half 
RipEX.ifTmATMItems:
0 ⇒ maskTCP Modbus COM protocol address translation mode
1 ⇒ table 
RipEX.IOStateItems:
-1 ⇒ unknownHW alarm input contact state
0 ⇒ off 
1 ⇒ on 
RipEX.RelayContactTypeItems:
0 ⇒ offHW alarm input contact type
1 ⇒ normally-closed 
2 ⇒ normally-open 
RipEX.rEncryptionItems:
0 ⇒ offRadio interface encryption method
1 ⇒ aes256 
RipEX.rRfPwrItems:
0 ⇒ mE-100mWRadio interface RF power
1 ⇒ mEr-200mW 
2 ⇒ mE-500mW 
3 ⇒ mE-1W 
4 ⇒ mE-2W 
5 ⇒ mE-3W 
6 ⇒ mE-4W 
7 ⇒ mE-5W 
8 ⇒ mE-10W 
9 ⇒ mE-8W 
17 ⇒ mL-200W 
18 ⇒ mL-500mW 
19 ⇒ mL-1W 
20 ⇒ mL-2W 
RipEX.SettingStateItems:
0 ⇒ offEthernet interface broadcast and multicast status
1 ⇒ onEthernet interface shaping status
 Terminal server status
 TCP Modbus COM protocol broadcast accept
 Radio interface FEC
 TS 1 on/off
 TS 2 on/off
 TS 3 on/off
 TS 4 on/off
 TS 5 on/off
RipEX.tsEthProtTypeItems:
0 ⇒ tcpTS 1 Ethernet protocol type
1 ⇒ udpTS 2 Ethernet protocol type
 TS 3 Ethernet protocol type
 TS 4 Ethernet protocol type
 TS 5 Ethernet protocol type
RFC1213.ifTypeItems:
1 ⇒ otherRFC1213 – Interface 1 – The type of interface (physical/link protocol)
2 ⇒ regular1822RFC1213 – Interface 2 – The type of interface (physical/link protocol)
3 ⇒ hdh1822 
4 ⇒ ddn-x25 
5 ⇒ rfc877-x25 
6 ⇒ ethernet-csmacd 
7 ⇒ iso88023-csmacd 
8 ⇒ iso88024-tokenBus 
9 ⇒ iso88025-tokenRing 
10 ⇒ iso88026-man 
11 ⇒ starLan 
12 ⇒ proteon-10Mbit 
13 ⇒ proteon-80Mbit 
14 ⇒ hyperchannel 
15 ⇒ fddi 
16 ⇒ lapb 
17 ⇒ sdlc 
18 ⇒ ds1 
19 ⇒ e1 
20 ⇒ basicISDN 
21 ⇒ primaryISDN 
22 ⇒ propPointToPointSerial 
23 ⇒ ppp 
24 ⇒ softwareLoopback 
25 ⇒ eon 
26 ⇒ ethernet-3Mbit 
27 ⇒ nsip 
28 ⇒ slip 
29 ⇒ ultra 
30 ⇒ ds3 
31 ⇒ sip 
32 ⇒ frame-relay 
RFC1213.ipForwardingItems:
1 ⇒ forwardingRFC1213 – The indication of whether this entity is acting as an IP gateway
2 ⇒ not-forwarding 
RFC1213.snmpEnableAuthenTrapsItems:
1 ⇒ enabledRFC1213 – SNMP – Indicates whether the SNMP agent process is permitted to generate authentication-failure traps
2 ⇒ disabled 
RS232.rs232AsyncPortParityItems:
1 ⇒ noneRS232 port 1 – The port’s sense of a character parity bit
2 ⇒ oddRS232 port 2 – The port’s sense of a character parity bit
3 ⇒ even 
4 ⇒ mark 
5 ⇒ space 
RS232.rs232AsyncPortStopBitsItems:
1 ⇒ oneRS232 port 1 – The port’s number of stop bits
2 ⇒ twoRS232 port 2 – The port’s number of stop bits
3 ⇒ oneAndHalf 
4 ⇒ dynamic 
RS232.rs232PortInFlowTypeItems:
1 ⇒ noneRS232 port 1 – The port’s type of input flow control
2 ⇒ ctsRtsRS232 port 2 – The port’s type of input flow control
3 ⇒ dsrDtrRS232 port 1 – The port’s type of output flow control
 RS232 port 2 – The port’s type of output flow control
RS232.rs232PortTypeItems:
1 ⇒ otherRS232 port 1 – The port’s hardware type
2 ⇒ rs232RS232 port 2 – The port’s hardware type
3 ⇒ rs422 
4 ⇒ rs423 
5 ⇒ v35 
6 ⇒ x21 
ICMP ping – AccessibilityItems:
0 ⇒ ICMP ping failsICMP ping – Accessibility
1 ⇒ ICMP ping successful 
[Note]Note

Two value mappings should already be included in the Zabbix itself, see “SNMP interface status (ifAdminStatus)” and “SNMP interface status (ifOperStatus)” in the Value mapping menu. Four Items from the RFC1213 template use these mappings.

How can I Edit an Item to Link with a Value Map?

Go to Configuration → Templates and choose one of the imported template. Open the item configuration window and click on the chosen item to view and edit its settings.

Choose the appropriate value map in the Menu “Show value” and save the changes.

Example: RipEX.eDhpc

Linking a value map to an item

Fig. 2.12: Linking a value map to an item

2.4. How do I Know that Something Has Happened to the RipEX Station?

There are two ways to check the RipEX stations. You can actively query the station in the defined time intervals or you can just wait for the trap to be received.

2.4.1. Active Querying

If you have a defined item which is updated e.g. every 10 seconds. Zabbix requests a reply to the SNMP GET message for the specific OID object and it stores this value in the database at 10 second intervals.

A trigger can also be configured for each item. For instance, temperature threshold alarm is set to 50°C. Whenever Zabbix receives an SNMP RESPONSE message from any monitored host with temperature higher than 50°C, an alarm is triggered. If the alarm is triggered, it is displayed at the Zabbix Dashboard. The Alarm will be visible in the “Last 20 issues” table and you will see which host is having an issue in the “Host status” table.

When the temperature falls back into the allowed range, the issue will be deleted from the Zabbix dashboard.

Displaying of RipEX trap

Fig. 2.13: Displaying of RipEX trap

2.4.2. SNMP Traps

The key aspect of the SNMP are the TRAPS. These OID objects are not actively monitored by the Zabbix manager but by the RipEX itself. This behaviour is described in the on-line help on RipEX web Settings page or in the User manual, Chapter 7.3.

How to Configure Traps in Zabbix?

This, unfortunately, is a somewhat complex procedure. There are several ways to configure traps – only one of them will be explained in this guide.

[Note]Note

Another approach could be using SNMPTT functionality.

You have to install an snmptrapd, a daemon which receives SNMP traps and pass them into the Zabbix front-end.

You can use the script (snmptrap.sh) which is included in the RipEX_Zabbix_templ.zip file downloadable from http://www.racom.eu/eng/products/radio-modem-ripex.html#download website. Copy the script file into //usr/lib/zabbix/externalscripts/ directory and change the file privileges and make it executable.

# mkdir -p /usr/lib/zabbix/externalscripts; chown zabbix /home/zabbix
# cp misc/snmptrap/snmptrapd.sh /home/zabbix/bin
# chmod +x /usr/lib/zabbix/externalscripts/snmptrapd.sh

After that, you need to edit the file. By executing

$ which zabbix_sender

you will find the full path to this executable binary file. Change the path in the file, e.g.

ZABBIX_SENDER="/usr/bin/zabbix_sender";

The script parses the output of each received SNMP trap, selects the appropriate host and declares an associative array containing trap descriptions. Eventually, it sends the whole message to your Zabbix server.

The script logs trap information into the /tmp/trap_messages.log file.

You should also check the LOG destination, which should be: /var/log/snmptrap/snmptrap.log. Create the directory if not already created and edit this in the snmptrap.sh script file.

LOGFILE=/var/log/snmptrap/snmptrap.log
[Note]Note

The log file could also be located in /var/log/zabbix/snmptrap.log if required.

Now we have our script prepared, let’s configure the Zabbix front-end:

If you have not yet done so, import the RipEX templates. One application is called TRAPS and it consists of all traps. Link the templates to desired hosts.

[Note]Note

If Zabbix receives a trap for an unknown host it will not be displayed.

The host MUST to be configured using the IP address as the Host name, e.g.:

Host name:

192.168.10.1

Visible name:

RipEX1

SNMP interface:

192.168.10.1, port 161, IP

Along with this template, 15 new items and triggers appear at each used host. That is exactly the number of SNMP traps defined at the RipEX. Each trap should be recognized and the Zabbix should display the correct information message at the dashboard.

Definition of RipEX traps

Fig. 2.14: Definition of RipEX traps

RipEX sends a trap whenever the watched value is out of range (or other configured condition is met) and whenever the value falls back within the corresponding range.

Every trap has two states in Zabbix. Each trap can either be in the alarm state or in the OK state.

RSS and DQ trap items are disabled in the template by default. The reason is that we need to define remote RipEX IP addresses first. See the following example for enabling a DQ trap:

Go to the Zabbix web front-end and select a RipEX host for which you want to process DQ traps. Click on the Items button and find an item with the following key: trpDqX.Y.Z.W.

Default DQ trap item

Fig. 2.15: Default DQ trap item

Click on the item and then click on the Clone button. Now you can edit the item. Replace the “X.Y.Z.W” string in the item Name with the remote RipEX IP address (e.g. 192.168.131.55). Do the same in the Key field and select the Enabled option in the Status field. See the following example:

Edited DQ trap item

Fig. 2.16: Edited DQ trap item

Save the changes and open the host Triggers list. Repeat the above steps for the DQ trigger and save the changes. You should see the trigger with the enabled status.

Enabled DQ trap trigger

Fig. 2.17: Enabled DQ trap trigger

Follow the same procedure (DQ and RSS) for other remote RipEX units as needed.

You can also define Zabbix to send you an e-mail whenever any trap is triggered. See the Zabbix Documentation or Section Section 2.7, “Zabbix Alerting via e-mail” of this Application not for the e-mail configuration.

Please, find the file snmptrapd.conf usually it’s in the /etc/snmp/ directory. Edit or create the file as root with the following lines:

authCommunity execute public
authCommunity execute PUBLIC
traphandle default /usr/lib/zabbix/externalscripts/snmptrap.sh

The first two lines will allow all received traps with community public or PUBLIC to be parsed and the third line will force the snmptrapd to use our script.

If you do not know what community names you will receive, add the following line to accept all community names.

disableAuthorization yes

Do not forget to restart snmptrapd. You should have similar snmptrapd parameters in the /etc/sysconfig/ snmptrapd file:

OPTIONS=”-Lsd -p /var/run/snmptrapd.pid -On”

This ensures that snmptrapd daemon will not translate the numerical OID numbers which is important for our script to run properly.

[Important]Important

If you install Zabbix on the CentOS distribution, do not forget to enable snmptrapd within SELinux security rules.

SELinux is an important security part of CentOS. Running all the functionality of Zabbix will require configuring these rules. If you do not understand it, consult the required changes with our technical support.

[Note]Note

RipEX default Community string name is “public”, however it can be changed (since firmware release 1.3). All RipEX stations within the network must have the same Community string. Otherwise disableAuthorization has to be set to “yes” (or set authCommunity variables for all allowed Community string names).

Basic Trap Functionality Tests

Now Zabbix is ready to receive SNMP traps from all RipEX stations and enter them into the database properly. In order to test it, force the trap to be sent from any RipEX and see whether it appears in the Zabbix front-end. If not, check that the respective UDP port (162) is enabled at your firewall and check the settings again. You can also execute Tcpdump or Wireshark at the selected interface of your Zabbix server or somewhere along the intended packet path.

Another basic test can be run using the following command:

zabbix_sender -z localhost -p 10051 -s "192.168.10.1" -k trpTemp -o "trpTemp, ALARM: UP"

The IP address of your RAy2 station is 192.168.10.1, key is “trpTemp” and the message for the Zabbix server is “trpTemp, ALARM: UP”. The command should trigger the host’s ” temperature exceeded the threshold” alarm. Note that you need to have a host configured with this IP address, otherwise the trap will not be shown.

It is important to set the KEY value correctly, otherwise the trap would not match the trigger. See more KEY values with their description below:

  • trpRssIPAddress – Remote station RSS value out of range (Replace the IPAddress with a real remote RipEX IP address)

  • trpDqIPAddress – Remote station DQ value out of range (Replace the IPAddress with a real remote RipEX IP address)

  • ttrpTxLost – TX Lost value out of range

  • trpUcc – UCC value out of range

  • trpTemp – Modem temperature value out of range

  • trpRfpwr – RF power value out of range

  • trpLanPr – Ethernet RX/TX packet ratio out of range

  • trpCom1Pr – COM1 RX/TX packet ratio out of range

  • trpCom2Pr – COM2 RX/TX packet ratio out of range

  • trpHwIn – HW input in the alarm state

  • trpHotStby – Modem becomes active in a Hot-Standby mode

  • trpBpath – Backup path state has changed

  • trpBpathAlt – Alternative path state has changed

  • trpUnitReady – Unit ready signal has changed

If you want to clear the trap alarm, just repeat the same zabbix_sender command, but change the message to contain the word “OFF”. E.g. “ALARM OFF”.

Zabbix dashboard – Status of units

Fig. 2.18: Zabbix dashboard – Status of units

You can also see Trap’s output in Monitoring → Latest Data → TRAPS of your RipEX station → History. The displayed information differs based on the trap received. See the detailed description in the respective Zabbix item.

2.5. What Else does Zabbix Offer?

There are many features provided by the Zabbix software. They are described in the Zabbix Documentation. Below are just a few of them.

You can create Screens. A Screen is a set of various graphs on one page for better overview of your network (temperature, UCC, RF power, …).

You can create Maps. If you administer many stations in many locations, a Map can be a good choice. You can define the background picture (e.g. real maps), various station pictures, station status, various statistics, etc. You can import any icon or background picture you want to use.

Basic map with two RipEX stations

Fig. 2.19: Basic map with two RipEX stations

A short example of RipEX station configuration in Maps:

{HOSTNAME}
Temp = {{HOSTNAME}:wvTempAvg.last(0)}
RSS = {{HOSTNAME}:wvRemRssAvg[1].last(0)}
DQ = {{HOSTNAME}:wvRemDqAvg[1].last(0)}
Definition of RipEX station in maps

Fig. 2.20: Definition of RipEX station in maps

Each map can be divided into several sub-maps. It can be useful for various levels of detail.

2.6. How to Access RipEX GUI from Zabbix

Zabbix can offer various ways of accessing the RipEX web interface by clicking on the link within the Zabbix front-end.

[Note]Note

This chapter consists of RAy2 screenshots, but the procedure is completely the same for RipEX as well.

2.6.1. Map URL

For every Host depicted in Maps, you can define its URL.

Map URL definition

Fig. 2.21: Map URL definition

After clicking on the Host, a new Item appears (URL), defined with the Name and the actual link. And when you click on this URL, the RAy2 web interface appears.

RAy2 URL Link in maps

Fig. 2.22: RAy2 URL Link in maps

2.6.2. Trigger URL

Every host can have as many Triggers as required. And for every Trigger, the respective URL can be defined. Just add the URL in the Trigger configuration page.

Trigger URL definition

Fig. 2.23: Trigger URL definition

After you do so, every time the trigger is activated, you can click on the Issue description within Dashboard’s “Last 20 Issues” window and then on the URL link.

Issue description used as a link

Fig. 2.24: Issue description used as a link

A simple click can forward you to the RAy2 web interface.

2.6.3. Inventory URL

The third option is to use Inventory for configuring URL. For every Host, you can enable the Inventory (serial number, OS, host type, …). Within many Inventory options, the URL can be defined.

Inventory URL definition

Fig. 2.25: Inventory URL definition

Every host’s Inventory can be opened from the Dashboard’s “Last 20 Issues” window. And in the Details, there is the configured URL displayed.

RAy2 URL link in the Inventory

Fig. 2.26: RAy2 URL link in the Inventory

2.7. Zabbix Alerting via e-mail

In case of any issue within your network, e.g. drop in the signal quality, or the unit being unreachable, Zabbix can automatically send an e-mail to predefined e-mail addresses. The following example will show just one procedure, other ways are possible (e.g. via the script).

2.7.1. E-mail Configuration

The e-mail can be set in the the Administration – Media Types menu. Edit the E-mail type corresponding to your server settings. In our example, we use our own SMTP server reachable from Zabbix server. No special security or password is required. You should be able to use any SMTP server.

E-mail configuration

Fig. 2.27: E-mail configuration

2.7.2. Users Configuration

The e-mails are sent to the users’ e-mail addresses. Go to the Administration – Users menu and configure the required e-mail addresses within the user’s details (Media).

User’s e-mail

Fig. 2.28: User’s e-mail

You define the time when the e-mail will be sent (e.g. do not send it over the night) and the severity of the issue (e.g. send me the e-mail just in case of a critical issue).

2.7.3. Actions

The last step is to configure the action – configure which issue causes the e-mail to be sent. Go the Configuration – Actions menu and create a new Action.

Action

Fig. 2.29: Action

Usually, you will use the MACROs for the e-mail body/subject. In this example, the Subject of the e-mail will consist of the host’s Name, Trigger status (Problem, OK) and Trigger Name. Within the body of the message, there are additional information such as the Trigger Severity, URL and the Issue details.

If the issue is fixed, we also send a recovery message. It is the same message, but saying “OK” instead of “PROBLEM”.

Action conditions

Fig. 2.30: Action conditions

The action is executed if it meets the conditions, e.g. the trigger value is “PROBLEM” and the host is a RipEX (or RAy2 unit). The conditions can be combined with AND or OR statements.

Action Operation

Fig. 2.31: Action Operation

The operation does not need to be just an e-mail, but it can consist of sending SMS or jabber messages. Or based on the issue duration, it can perform different tasks. In the example above, we send the e-mail to the user “servis” immediately when the issue occurs. There are no additional steps.

2.8. RipEX Scripts in Zabbix

By default, there are no ready-to-be-used actions in Zabbix such as configuration backup or firmware upgrade. The Zabbix NMS is a general system which requires special features to be implemented by RACOM or by the user himself.

We provide the user with a guide how to use and define these special features and within the RipEX template, we already prepared several examples:

  • Configuration backup

  • Displaying the current RSS

  • Reading watched values correctly

[Note]Note

If you have troubles running those scripts or making your own, contact us on .

The whole implementation can be quite time consuming, but once you successfully run the first script, the others are very similar and its implementation is straightforward.

Within the Template, there are three scripts. As you know realize, having the configuration backup files can be crucial if replacing the unit. There is nothing easier than just uploading the configuration file into a brand new RipEX unit.

[Note]Note

Reading the watched values script uses a different approach. It is enough to upload the script file to the correct directory (as other scripts) and then, edit the individual Items from the Web interface. See the details ….

2.8.1. Zabbix Configuration

Before creating and running the first scripts, you need to prepare the Zabbix server (and the Linux operating system). In this example, we configure the CentOS 7 operating system with Zabbix 3 installed via packaging system.

The following steps can be done in different order, but following this order is absolutely fine.

Zabbix Server Configuration File

By default, the zabbix_server configuration file is located in the /etc/zabbix/zabbix_server.conf file. Find the line with “SSHKeyLocation” parameter and define it with this value:

SSHKeyLocation=/home/zabbix/.ssh

This is the location of the RSA private SSH key which will be used to access the RipEX units.

Restart the Zabbix server afterwards.

# systemctl restart zabbix-server

Uploading the Template Scripts

The scripts must be uploaded manually to a correct directory manually. The default directory is /usr/lib/zabbix/externalscripts/. Copy the script files from the ZIP Template file to this directory. The target state should look similar to this output:

# ls -l /usr/lib/zabbix/externalscripts/
total 48
-rwxr-xr-x. 1 zabbix zabbix   1112 Oct 20 11:12 read_wv.sh
-rwxr-xr-x. 1 zabbix zabbix    680 Mar  9 17:28 ripex_cli_cnf_textfile_get.sh
-rwxr-xr-x. 1 zabbix zabbix    111 Mar  8 15:56 ripex_cli_rss_show.sh
-rw-r--r--. 1 zabbix zabbix    77 Mar 15 08:31 script-log.txt
-rwxr-xr-x. 1 zabbix zabbix 17200 Mar  1 13:24 snmptrap.sh

There are two executable scripts via the Zabbix web interface (starting with “ripex_”). The LOG output of those scripts is in script-log.txt file. There is also the snmptrap.sh file which you should have there for the SNMP TRAP functionality and a script for reading the watched values correctly.

Make sure that the files have the zabbix user/group and are executable.

# chown zabbix:zabbix /usr/lib/zabbix/externalscripts/*
# chmod +x /usr/lib/zabbix/externalscripts/*

Zabbix User Configuration

The Zabbix user cannot login to the bash by default. We need modify the /etc/passwd file as follows:

# chsh -s /bin/bash zabbix
# cat /etc/passwd
zabbix:x:996:994:Zabbix Monitoring System:/home/zabbix:/bin/bash

Make sure that the last part after the “:” has a correct path to the bash binary.

If not already created, create the HOME directory for the Zabbix user.

# usermod -m -d /home/zabbix zabbix
# chown zabbix:zabbix /home/zabbix
# chmod 700 /home/zabbix
[Note]Note

You may need to run the “usermod” command once again.

Create the directories for the saved configuration and firmware files and change the access rights.

# mkdir /home/zabbix/configuration-backup
# mkdir /home/zabbix/firmware
# mkdir /home/zabbix/configuration-backup/ripex
# mkdir /home/zabbix/firmware/ripex
# chown zabbix:zabbix –R /home/zabbix/

SSH Access to RipEX units

The directory for the SSH key should now be located in /home/zabbix/.ssh directory. Change the current directory to this one and login as zabbix.

# su zabbix

A new prompt appears. Because, we cannot access the RipEX units using their password via scripts, we need to upload the SSH keys into every unit we want to control. You can either have you own RSA/DSA key or you can create a new one following this example. Run

bash-4.2$ ssh-keygen -t rsa

Follow the guide of the ssh-keygen application and leave the passphrase empty.

To copy our RSA key into the RipEX units, run the following command:

bash-4.2$ ssh-copy-id admin@10.250.2.225

Just replace 10.250.2.225 with the correct RipEX IP address. The prompt will ask for the Admin password, fill it in and click Enter. Now, you should have the access into the unit without using a password. Check it via this command:

bash-4.2$ ssh admin@10.250.2.225

You should be logged in the RipEX unit without writing the password.

Scripts in the Zabbix Web Interface

The script files can be downloaded within the template ZIP file. Save them in the correct direktory (/usr/lib/zabbix/externalscripts/) of your Zabbix distribution. Then, the scripts must be manually created in the Zabbix Administration – Scripts menu. See the example below and create Zabbix scripts for all RipEX scripts.

RipEX scripts

Fig. 2.32: RipEX scripts

If you open one of them, you can modify them as required.

Script configuration

Fig. 2.33: Script configuration

The Type must be set to “Script” and the Execute on parameter to “Zabbix server”. The command can be modified as required. There is a full path to the script saved on the server and the parameters. The script output is appended to the mentioned log file.

The script can apply to ALL hosts or just one group – in our example, the group name is “RipEX”.

The parameters are MACROs which should be enabled by default due to our Template. Each RipEX unit uses the SSH port 22 and the SSH key saved in /home/zabbix/.ssh/id_rsa file by default. If you need to modify any of these parameters, go to the Configuration – Hosts menu and edit the particular Host’s MACROs (Inherited and host macros submenu).

Host MACROs

Fig. 2.34: Host MACROs

To edit any of the parameters, click on the “Change” button and Update the Host.

SELinux Restrictions

If the operating system is CentOS 7 and has the SELinux security option enabled, the scripts will not run properly due to these restrictions.

If you run the script, but it will not run properly, check the following output via the command line:

# ausearch -m avc|tail -n 3

It can display a similar output:

time->Tue Mar  8 14:12:31 2016
type=SYSCALL msg=audit(1457442751.052:8277): arch=c000003e syscall=42 success=no exit=-13 a0=3 a1=7f11466de620 a2=10 a3=56decfbf items=0 ppid=4929 pid=2936 auid=4294967295 uid=996 gid=994 euid=996 suid=996 fsuid=996 egid=994 sgid=994 fsgid=994 tty=(none) ses=4294967295 comm="ssh" exe="/usr/bin/ssh" subj=system_u:system_r:zabbix_t:s0 key=(null)
type=AVC msg=audit(1457442751.052:8277): avc:  denied  { name_connect } for  pid=2936 comm="ssh" dest=8021 scontext=system_u:system_r:zabbix_t:s0 tcontext=system_u:object_r:zope_port_t:s0 tclass=tcp_socket

The issue here is that the SSH cannot be run from the Web interface. To enable it, you can run the following commands. Note that the first command installs some binaries to control SELinux rules. If already installed, you do not need them.

# yum install policycoreutils-devel
# mkdir -p /root/local-policy-modules/zabbix
# cd /root/local-policy-modules/zabbix
# grep "denied" /var/log/audit/audit.log|tail -n 2 > avc.log
# audit2allow -M zabbix_script_ssh -R -i avc.log
# semodule -i zabbix_script_ssh.pp
[Important]Important

Do not rush with SELinux rules, if you understand the SELinux, make the required changes. If not, please consult us.

A similar approach is required for the Bash, SNMP traps, logging the script output, etc.

Testing Scripts

The scripts can be tested via clicking on the Hosts in the Web interface. You can click on them when they are displayed within the Last 20 Issues on your Dashboard, or within Maps where they are always displayed.

Scripts in the Maps

Fig. 2.35: Scripts in the Maps

If you click on any of the script, the corresponding script runs and the output is displayed in the pop-up window. You can test the Zabbix general ones such as “Ping” or “Traceroute” first.

[Note]Note

You may be required to change the SELinux rules or to install “traceroute” application via the command line (yum install).

The easiest script displays the current RSS level. The level (in dBm) should be displayed within several seconds in the pop-up window.

Another script is the Configuration backup. The expected output should display a full path to the stored file (in the /home/zabbix/configuration-backup/ripex directory).

Reading the watched values script is working in a different manner. It is used as an external check Item. If you open the Application called “Watched value via script”, you will see 17 readable watched values.

Watched Values - application

Fig. 2.36: Watched Values – application

For each query for particular watched value, the script “read_wv.sh” is executed.

Watched Values - items

Fig. 2.37: Watched Values – items

It accepts the following parameters:

{HOST.IP}the MACRO for the host IP address (the IP address of your Master station)
{$SNMP.PORT}the user MACRO for an SNMP UDP port (by default 161)
{$NEIGHBOUR.1}the user MACRO for the IP address of the first neighbour (by default 192.168.169.169)
Watched value IDID for a particular watched value (e.g. 17 for the average modem temperature)
{$NEIGHBOUR.COUNT}The number of all neighbouring units of your Master radio

The {HOST.IP} MACRO is automatically derived from the SNMP interface of your host. Other three user MACROs are defined in the Host MACRO configuration page (go to Configuration – Hosts – open the particular Host – Macros). Watched value ID represents the number within the OID string to refer to a particular watched value. See the IDs for the first neighbour which are within the template automatically.

Macros

Fig. 2.38: Macros

After you define the correct MACROs, the watched values query can start working out of the box, but only for the first neighbour. If the Master unit has more neighbours, you need to define other MACROs – {$NEIGHBOUR.X} where X is the neighbour’s ID and increase {$NEIGHBOUR.COUNT} MACRO to a correct number, e.g. if you have 3 neighbours, set this macro to 3 and create MACROS called {$NEIGHBOUR.2} and {$NEIGHBOUR.3} with the correct IP addresses.

Macros 2

Fig. 2.39: Macros 2

After this step, you need to “Clone” each Item in this Application and replace the {$NEIGHBOUR.1} with {$NEIGHBOUR.2} or {$NEIGHBOUR.3} in the Key field and also in the Name field.

Cloning

Fig. 2.40: Cloning

NOTE: Do not forget to enable required Items.

[Important]Important

The update interval should not be quicker than the Watched values broadcasting period (configurable in the RipEX Settings web interface menu). Watched values are updated only upon receiving a broadcast packets from a particular neighbour. This broadcast is sent every 2 hours by default, but can be configured as required at each remote RipEX unit. By default, the Zabbix update interval should also be 2 hours.

Neighbours

Fig. 2.41: Neighbours

Once configured correctly, running the scripts is easy. If you need to add a new host, just copy the SSH key and you are ready to use it. And if a new script is required, see these examples and create your own scripts or consult creating them with our technical support at .

2.9. RipEX MIB Table

2.9.1. RipEX

OIDNameAccessStateDescription
33555.2.1.1.1stationNameread-onlycurrentStation Name.
33555.2.1.1.2deviceTyperead-onlycurrentDevice type.
33555.2.1.1.3deviceCoderead-onlycurrentDevice code.
33555.2.1.1.4serialNumberread-onlycurrentProduct serial number.
33555.2.1.1.5deviceModeread-onlycurrentStation working mode.
33555.2.1.1.6.1hwVerModemread-onlycurrentModem HW version.
33555.2.1.1.6.2hwVerRadioread-onlycurrentRadio HW version.
33555.2.1.1.7.1swVermodemread-onlycurrentModem firmware version.
33555.2.1.1.7.2swVerSDDRread-onlycurrentSDDR firmware version.
33555.2.1.1.7.3swVerDriverread-onlycurrentDriver firmware version.
33555.2.1.1.7.4swVerBootloaderread-onlycurrentBootloader version.
33555.2.2.1.1rRxFrequencyread-onlycurrentRadio interface Rx frequency in Hz.
33555.2.2.1.2rTxFrequencyread-onlycurrentRadio interface Tx frequency in Hz.
33555.2.2.1.3rRfPwrread-onlycurrentRadio interface RF Power.
33555.2.2.1.4rEncryptionread-onlycurrentRadio interface encryption method.
33555.2.2.1.5rFECread-onlycurrentRadio interface FEC state.
33555.2.2.2.1eGatewayread-onlycurrentEthernet interface gateway address.
33555.2.2.2.2eDhcpread-onlycurrentEthernet interface DHCP mode.
33555.2.2.2.3eShapingread-onlycurrentEthernet interface shaping state.
33555.2.2.2.4eBCastMCastread-onlycurrentEthernet interface broadcast and multicast state.
33555.2.2.2.5eSpeedread-onlycurrentEthernet interface bit rate and duplex settings.
33555.2.2.3.1ifTmEnableread-onlycurrentTCP Modbus state.
33555.2.2.3.2ifTmPortread-onlycurrentTCP Modbus port.
33555.2.2.3.3ifTmTimeoutread-onlycurrentTCP Modbus socket timeout in seconds.
33555.2.2.3.4ifTmBCastread-onlycurrentTCP Modbus COM protocol broadcast accept.
33555.2.2.3.5ifTmATMread-onlycurrentTCP Modbus COM protocol address translation mode.
33555.2.2.4.1ifTsEnableread-onlycurrentTerminal server state.
33555.2.2.4.2ifTsNumberread-onlycurrentNumber of Terminal server interfaces.
33555.2.2.4.3ifTsTablenot-accessiblecurrentList of Terminal server interface entries.
33555.2.2.4.3.1ifTsEntrynot-accessiblecurrentTerminal server interface entry.
33555.2.2.4.3.1.1.XtsIndexread-onlycurrentUnique index for each interface.
33555.2.2.4.3.1.2.XtsEnableread-onlycurrentTerminal server interface state.
33555.2.2.4.3.1.3.XtsEthProtTyperead-onlycurrentTerminal server Ethernet protocol type.
33555.2.2.4.3.1.4.XtsEthProtTimeoutread-onlycurrentTerminal server Ethernet protocol socket timeout in seconds.
33555.2.2.4.3.1.5.XtsEthProtMyPortread-onlycurrentTerminal server Ethernet protocol socket TCP/UDP port.
33555.2.2.4.3.1.6.XtsEthProtDestIPread-onlycurrentTerminal server partner’s IP address.
33555.2.2.4.3.1.7.XtsEthProtDestPortread-onlycurrentTerminal server partner’s destination TCP/UDP port.
33555.2.2.4.3.1.8.XtsComProtTyperead-onlycurrentTerminal server COM user protocol type.
33555.2.2.5.1ifComNumberread-onlycurrentNumber of COM interfaces.
33555.2.2.5.2ifComTablenot-accessiblecurrentList of COM interface entries.
33555.2.2.5.2.1ifComEntrynot-accessiblecurrentCOM interface entry.
33555.2.2.5.2.1.1.XcomIndexread-onlycurrentUnique index for each interface.
33555.2.2.5.2.1.2.XcomIdleread-onlycurrentCOM interface idle in bytes.
33555.2.2.5.2.1.3.XcomMturead-onlycurrentCOM interface MTU in bytes.
33555.2.2.5.2.1.4.XcomProtocolread-onlycurrentCOM interface protocol.
33555.2.2.21.1ifHwAInputTyperead-onlycurrentHW alarm input contact type.
33555.2.2.21.2ifHwAInputStateread-onlycurrentHW alarm input contact state.
33555.2.3.1.1.1stRadioTotDuplicatesread-onlycurrentTotal radio duplicate packets counter.
33555.2.3.1.1.2stRadioTotRepeatsread-onlycurrentTotal radio repeated packets counter.
33555.2.3.1.1.3stRadioTotLostread-onlycurrentTotal radio lost packets counter.
33555.2.3.1.1.4stRadioTotCtlPacketsRxread-onlycurrentTotal Rx radio control packets counter.
33555.2.3.1.1.5stRadioTotCtlPacketsTxread-onlycurrentTotal Tx radio control packets counter.
33555.2.3.1.1.6stRadioTotDataErrread-onlycurrentTotal radio data error packets counter.
33555.2.3.1.1.7stRadioTotRejectedread-onlycurrentTotal radio rejected packets counter.
33555.2.3.1.1.8stRadioTotPacketsRxread-onlycurrentRemote station total Rx packets counter.
33555.2.3.1.1.9stRadioTotPacketsTxread-onlycurrentRemote station total Tx packets counter.
33555.2.3.1.1.10stRadioTotBytesRxread-onlycurrentRemote station total Rx bytes counter.
33555.2.3.1.1.11stRadioTotBytesTxread-onlycurrentRemote station total Tx bytes counter.
33555.2.3.1.1.12stRadioTotIpErrread-onlycurrentTotal radio IP error packets counter.
33555.2.3.1.1.13stRadioTotSubHeadErrread-onlycurrentTotal radio subheader error packets counter.
33555.2.3.1.1.14stRadioTotHeadErrread-onlycurrentTotal radio header error packets counter.
33555.2.3.1.1.15stRadioTotFalseSyncread-onlycurrentTotal radio false sync counter.
33555.2.3.1.2stRadioRemNumberread-onlycurrentNumber of remote stations.
33555.2.3.1.3stRadioRemTablenot-accessiblecurrentList of remote station entries.
33555.2.3.1.3.1stRadioRemEntrynot-accessiblecurrentRadio remote station entry.
33555.2.3.1.3.1.1.XstRemIndexread-onlycurrentRemote station index.
33555.2.3.1.3.1.2.XstRemIpAddrread-onlycurrentRemote station IP address.
33555.2.3.1.3.1.3.XstRemPacketsRxread-onlycurrentRemote station Rx packets counter.
33555.2.3.1.3.1.4.XstRemPacketsTxread-onlycurrentRemote station Tx packets counter.
33555.2.3.1.3.1.5.XstRemBytesRxread-onlycurrentRemote station Rx bytes counter.
33555.2.3.1.3.1.6.XstRemBytesTxread-onlycurrentRemote station Tx bytes counter.
33555.2.3.1.3.1.7.XstRemDuplicatesread-onlycurrentRemote station duplicate packets counter.
33555.2.3.1.3.1.8.XstRemRepeatsread-onlycurrentRemote station repeated packets counter.
33555.2.3.1.3.1.9.XstRemLostread-onlycurrentRemote station lost packets counter.
33555.2.3.1.3.1.10.XstRemCtlPacketsRxread-onlycurrentRemote station Rx radio control packets counter.
33555.2.3.1.3.1.11.XstRemCtlPacketsTxread-onlycurrentRemote station Tx radio control packets counter.
33555.2.3.1.3.1.12.XstRemDataErrread-onlycurrentRemote station data error packets counter.
33555.2.3.1.3.1.13.XstRemRejectedread-onlycurrentRemote station rejected packets counter.
33555.2.3.1.3.1.14.XstRemTotalPacketsRxread-onlycurrentRemote station total Rx packets counter.
33555.2.3.1.3.1.15.XstRemTotalPacketsTxread-onlycurrentRemote station total Tx packets counter.
33555.2.3.1.3.1.16.XstRemTotalBytesRxread-onlycurrentRemote station total Rx bytes counter.
33555.2.3.1.3.1.17.XstRemTotalBytesTxread-onlycurrentRemote station total Tx bytes counter.
33555.2.3.2.1stTcpModNumberread-onlycurrentNumber of TCP Modbus ports.
33555.2.3.2.2stTcpModTablenot-accessiblecurrentList of TCP Modbus port entries.
33555.2.3.2.2.1stTcpModEntrynot-accessiblecurrentTCP Modbus port entry.
33555.2.3.2.2.1.1.XstTcpModIndexread-onlycurrentTCP Modbus port index.
33555.2.3.2.2.1.2.XstTcpModPacketsRxread-onlycurrentTCP Modbus Rx packets counter.
33555.2.3.2.2.1.3.XstTcpModPacketsTxread-onlycurrentTCP Modbus Tx packets counter.
33555.2.3.2.2.1.4.XstTcpModBytesRxread-onlycurrentTCP Modbus Rx bytes counter.
33555.2.3.2.2.1.5.XstTcpModBytesTxread-onlycurrentTCP Modbus Tx bytes counter.
33555.2.3.3.1stTermServNumberread-onlycurrentNumber of Terminal Server ports.
33555.2.3.3.2stTermServTablenot-accessiblecurrentList of Terminal Server port entries.
33555.2.3.3.2.1stTermServEntrynot-accessiblecurrentTerminal Server port entry.
33555.2.3.3.2.1.1.XstTermServIndexread-onlycurrentTerminal Server port index.
33555.2.3.3.2.1.2.XstTermServPacketsRxread-onlycurrentTerminal Server Rx packets counter.
33555.2.3.3.2.1.3.XstTermServPacketsTxread-onlycurrentTerminal Server Tx packets counter.
33555.2.3.3.2.1.4.XstTermServBytesRxread-onlycurrentTerminal Server Rx bytes counter.
33555.2.3.3.2.1.5.XstTermServBytesTxread-onlycurrentTerminal Server Tx bytes counter.
33555.2.3.4.1stComNumberread-onlycurrentNumber of COM ports.
33555.2.3.4.2stComTablenot-accessiblecurrentList of COM port entries.
33555.2.3.4.2.1stComEntrynot-accessiblecurrentCOM port entry.
33555.2.3.4.2.1.1.XstComIndexread-onlycurrentCOM port index.
33555.2.3.4.2.1.2.XstComPacketsRxread-onlycurrentCOM Rx packets counter.
33555.2.3.4.2.1.3.XstComPacketsTxread-onlycurrentCOM Tx packets counter.
33555.2.3.4.2.1.4.XstComBytesRxread-onlycurrentCOM Rx bytes counter.
33555.2.3.4.2.1.5.XstComBytesTxread-onlycurrentCOM Tx bytes counter.
33555.2.3.5.1stTcpProxyNumberread-onlycurrentNumber of TCP proxy ports.
33555.2.3.5.2stTcpProxyTablenot-accessiblecurrentList of TCP proxy port entries.
33555.2.3.5.2.1stTcpProxyEntrynot-accessiblecurrentTCP proxy port entry.
33555.2.3.5.2.1.1.XstTcpProxyIndexread-onlycurrentTCP proxy port index.
33555.2.3.5.2.1.2.XstTcpProxyPacketsRxread-onlycurrentTCP proxy Rx packets counter.
33555.2.3.5.2.1.3.XstTcpProxyPacketsTxread-onlycurrentTCP proxy Tx packets counter.
33555.2.3.5.2.1.4.XstTcpProxyBytesRxread-onlycurrentTCP proxy Rx bytes counter.
33555.2.3.5.2.1.5.XstTcpProxyBytesTxread-onlycurrentTCP proxy Tx bytes counter.
33555.2.4.1.5wvTxLostLastread-onlycurrentLocal station – Last Tx lost value in %.
33555.2.4.1.6wvTxLostAvgread-onlycurrentLocal station – Average Tx lost value in hundredths of %.
33555.2.4.1.7wvUccLastread-onlycurrentLocal station – Last UCC value in tenths of Volt (V).
33555.2.4.1.8wvUccAvgread-onlycurrentLocal station – Average UCC value in thousandths of Volt (V).
33555.2.4.1.9wvTempLastread-onlycurrentLocal station – Last device temperature value in tenths of Celsius (C).
33555.2.4.1.10wvTempAvgread-onlycurrentLocal station – Average device temperature value in thousandths of Celsius (C).
33555.2.4.1.11wvRfPwrLastread-onlycurrentLocal station – Last RF power value in tenths of Watt (W).
33555.2.4.1.12wvRfPwrAvgread-onlycurrentLocal station – Average RF power value in thousandths of Watt (W).
33555.2.4.1.13wvVswrLastread-onlycurrentLocal station – Last VSWR value from interval <3, 25> in tenths.
33555.2.4.1.14wvVswrAvgread-onlycurrentLocal station – Average VSWR value from interval <300, 2500> in thousandths.
33555.2.4.1.41wvRxTxEthread-onlycurrentLocal station – ETH interface Rx to Tx packets ratio value from interval <1, 10000> in hundredths.
33555.2.4.1.42wvRxTxCom1read-onlycurrentLocal station – COM1 interface Rx to Tx packets ratio value from interval <1, 10000> in hundredths.
33555.2.4.1.43wvRxTxCom2read-onlycurrentLocal station – COM2 interface Rx to Tx packets ratio value from interval <1, 10000> in hundredths.
33555.2.4.2wvRemoteNumberread-onlycurrentNumber of remote stations.
33555.2.4.3wvRemoteTablenot-accessiblecurrentList of remote stations.
33555.2.4.3.1wvRemoteEntrynot-accessiblecurrentRemote station watched values entry.
33555.2.4.3.1.1.XwvRemIndexread-onlycurrentRemote station – Unique index.
33555.2.4.3.1.2.XwvRemIpAddrread-onlycurrentRemote station – IP address.
33555.2.4.3.1.3.XwvRemHearingsread-onlycurrentRemote station – Total heard packets from the remote station.
33555.2.4.3.1.4.XwvRemRssLastread-onlycurrentRemote station – Last RSS value in dBm.
33555.2.4.3.1.5.XwvRemRssAvgread-onlycurrentRemote station – Average RSS value in hundredths of dBm.
33555.2.4.3.1.6.XwvRemDqLastread-onlycurrentRemote station – Last DQ value.
33555.2.4.3.1.7.XwvRemDqAvgread-onlycurrentRemote station – Average DQ value in hundredths.
33555.2.4.3.1.12.XwvRemTxLostLastread-onlycurrentRemote station – Last Tx lost value in %.
33555.2.4.3.1.13.XwvRemTxLostAvgread-onlycurrentRemote station – Average Tx lost value in hundredths of %.
33555.2.4.3.1.14.XwvRemUccLastread-onlycurrentRemote station – Last UCC value in tenths of Volt (V).
33555.2.4.3.1.15.XwvRemUccAvgread-onlycurrentRemote station – Average UCC value in thousandths of Volt (V).
33555.2.4.3.1.16.XwvRemTempLastread-onlycurrentRemote station – Last device temperature value in tenths of Celsius (C).
33555.2.4.3.1.17.XwvRemTempAvgread-onlycurrentRemote station – Average device temperature value in thousandths of Celsius (C).
33555.2.4.3.1.18.XwvRemRfPwrLastread-onlycurrentRemote station – Last RF power value in tenths of Watt (W).
33555.2.4.3.1.19.XwvRemRfPwrAvgread-onlycurrentRemote station – Average RF power value in thousandths of Watt (W).
33555.2.4.3.1.20.XwvRemVswrLastread-onlycurrentRemote station – Last VSWR value from interval <3, 25> in tenths.
33555.2.4.3.1.21.XwvRemVswrAvgread-onlycurrentRemote station – Average VSWR value from interval <300, 2500> in thousandths.
33555.2.5.1.1alarmThrRssMinread-onlycurrentAlarm threshold – minimum – RSS value in dBm.
33555.2.5.1.2alarmThrRssMaxread-onlycurrentAlarm threshold – maximum – RSS value in dBm.
33555.2.5.1.3alarmThrDqMinread-onlycurrentAlarm threshold – minimum – DQ value.
33555.2.5.1.4alarmThrDqMaxread-onlycurrentAlarm threshold – maximum – DQ value.
33555.2.5.1.9alarmThrTxLostMinread-onlycurrentAlarm threshold – minimum – Tx lost value in %.
33555.2.5.1.10alarmThrTxLostMaxread-onlycurrentAlarm threshold – maximum – Tx lost value in %.
33555.2.5.1.11alarmThrUccMinread-onlycurrentAlarm threshold – minimum – UCC value in tenths of Volt (V).
33555.2.5.1.12alarmThrUccMaxread-onlycurrentAlarm threshold – maximum – UCC value in tenths of Volt (V).
33555.2.5.1.13alarmThrTempMinread-onlycurrentAlarm threshold – minimum – device temperature value in tenths of Celsius (C).
33555.2.5.1.14alarmThrTempMaxread-onlycurrentAlarm threshold – maximum – device temperature value in tenths of Celsius (C).
33555.2.5.1.15alarmThrRfPwrMinread-onlycurrentAlarm threshold – minimum – RF power value in tenths of Watt (W).
33555.2.5.1.16alarmThrRfPwrMaxread-onlycurrentAlarm threshold – maximum – RF power value in tenths of Watt (W).
33555.2.5.1.17alarmThrVswrMinread-onlycurrentAlarm threshold – minimum – VSWR value from interval <3, 25> in tenths.
33555.2.5.1.18alarmThrVswrMaxread-onlycurrentAlarm threshold – maximum – VSWR value from interval <3, 25> in tenths.
33555.2.5.1.31alarmThrRxTxEthMinread-onlycurrentAlarm threshold – minimum – ETH interface Rx to Tx packets ratio value in hundredths.
33555.2.5.1.32alarmThrRxTxEthMaxread-onlycurrentAlarm threshold – maximum – ETH interface Rx to Tx packets ratio value in hundredths.
33555.2.5.1.33alarmThrRxTxCom1Minread-onlycurrentAlarm threshold – minimum – COM1 interface Rx to Tx packets ratio value in hundredths.
33555.2.5.1.34alarmThrRxTxCom1Maxread-onlycurrentAlarm threshold – maximum – COM1 interface Rx to Tx packets ratio value in hundredths.
33555.2.5.1.35alarmThrRxTxCom2Minread-onlycurrentAlarm threshold – minimum – COM2 interface Rx to Tx packets ratio value in hundredths.
33555.2.5.1.36alarmThrRxTxCom2Maxread-onlycurrentAlarm threshold – maximum – COM2 interface Rx to Tx packets ratio value in hundredths.
33555.2.5.2.1alarmStateRssread-onlycurrentAlarm state – RSS.
33555.2.5.2.2alarmStateDqread-onlycurrentAlarm state – DQ.
33555.2.5.2.5alarmStateTxLostread-onlycurrentAlarm state – Tx lost.
33555.2.5.2.6alarmStateUccread-onlycurrentAlarm state – UCC.
33555.2.5.2.7alarmStateTempread-onlycurrentAlarm state – device temperature.
33555.2.5.2.8alarmStateRfPwrread-onlycurrentAlarm state – RF power.
33555.2.5.2.9alarmStateVswrread-onlycurrentAlarm state – VSWR.
33555.2.5.2.16alarmStateRxTxEthread-onlycurrentAlarm state – ETH interface Rx to Tx packets ratio.
33555.2.5.2.17alarmStateRxTxCom1read-onlycurrentAlarm state – COM1 interface Rx to Tx packets ratio.
33555.2.5.2.18alarmStateRxTxCom2read-onlycurrentAlarm state – COM2 interface Rx to Tx packets ratio.
33555.2.5.2.31alarmStateHwInputread-onlycurrentAlarm state – HW Input.
33555.2.5.2.32alarmStateUnitReadyread-onlycurrentAlarm state – Unit ready.
33555.2.6.1bpathsNumberread-onlycurrentNumber of Backup Paths.
33555.2.6.2bpathsTablenot-accessiblecurrentList of Backup Paths entries.
33555.2.6.2.1bpathsEntrynot-accessiblecurrentBackup Paths entry.
33555.2.6.2.1.1.XbpathsIndexread-onlycurrentBackup Paths index.
33555.2.6.2.1.2.XbpathsPeerIpread-onlycurrentBackup Paths – Peer IP address.
33555.2.6.2.1.3.XbpathsNameread-onlycurrentBackup Paths – Symbolic Name.
33555.2.6.2.1.4.XbpathsAltUsedPrioread-onlycurrentBackup Paths – Alternative Paths – Currently used path priority.
33555.2.6.2.1.5.XbpathsAltUsedGwread-onlycurrentBackup Paths – Alternative Paths – Currently used path Gateway IP address.
33555.2.6.2.1.6.XbpathsAltUsedStateread-onlycurrentBackup Paths – Alternative Paths – Currently used path State.
33555.2.6.2.1.7.XbpathsAltPassiveStateread-onlycurrentBackup Paths – Alternative Paths – Currently passive paths State.
33555.2.10.1trpRss currentA notification to indicate that average RSS value has exceeded threshold limits. This notification sends additional information about the event by including the following objects in its varbinding list. – alarmStateRss: RSS alarm state. – wvRemRssAvg: Remote station – Average RSS value in hundredths of dBm. – wvRemIpAddr: Remote station IP address.
33555.2.10.2trpDq currentA notification to indicate that average DQ value has exceeded threshold limits. This notification sends additional information about the event by including the following objects in its varbinding list. – alarmStateDq: DQ alarm state. – wvRemDqAvg: Remote station – Average DQ value in hundredths. – wvRemIpAddr: Remote station IP address.
33555.2.10.5trpTxLost currentA notification to indicate that average Tx lost value has exceeded threshold limits. This notification sends additional information about the event by including the following objects in its varbinding list. – alarmStateTxLost: Tx lost alarm state. – wvTxLostAvg: Local station – Average Tx lost value in hundredths of %.
33555.2.10.6trpUcc currentA notification to indicate that average UCC value has exceeded threshold limits. This notification sends additional information about the event by including the following objects in its varbinding list. – alarmStateUcc: UCC alarm state. – wvUccAvg: Local station – Average UCC value in thousandths of Volt (V).
33555.2.10.7trpTemp currentA notification to indicate that average device temperature value has exceeded threshold limits. This notification sends additional information about the event by including the following objects in its varbinding list. – alarmStateTemp: Device temperature alarm state. – wvTempAvg: Local station – Average device temperature value in thousandths of Celsius (C).
33555.2.10.8trpRfPwr currentA notification to indicate that average RF power value has exceeded threshold limits. This notification sends additional information about the event by including the following objects in its varbinding list. – alarmStateRfPwr: RF power alarm state. – wvRfPwrAvg: Local station – Average RF power value in thousandths of Watt (W).
33555.2.10.9trpVswr currentA notification to indicate that average VSWR value has exceeded threshold limits. This notification sends additional information about the event by including the following objects in its varbinding list. – alarmStateVswr: VSWR alarm state. – wvVswrAvg: Local station – Average VSWR value from interval <300, 2500> in thousandths.
33555.2.10.10trpEthPr currentA notification to indicate that average ETH interface Rx to Tx packets ratio value has exceeded threshold limits. This notification sends additional information about the event by including the following objects in its varbinding list. – alarmStateRxTxEth: Alarm state of ETH Rx to Tx packets ratio value. – wvRxTxEth: Local station – ETH Rx to Tx packets ratio value from interval <1, 10000> in hundredths.
33555.2.10.11trpCom1Pr currentA notification to indicate that average COM1 interface Rx to Tx packets ratio value has exceeded threshold limits. This notification sends additional information about the event by including the following objects in its varbinding list. – alarmStateRxTxCom1: Alarm state of COM1 Rx to Tx packets ratio value. – wvRxTxCom1: Local station – COM1 Rx to Tx packets ratio value from interval <1, 10000> in hundredths.
33555.2.10.12trpCom2Pr currentA notification to indicate that average COM2 interface Rx to Tx packets ratio value has exceeded threshold limits. This notification sends additional information about the event by including the following objects in its varbinding list. – alarmStateRxTxCom2: Alarm state of COM2 Rx to Tx packets ratio value. – wvRxTxCom2: Local station – COM2 Rx to Tx packets ratio value from interval <1, 10000> in hundredths.
33555.2.10.13trpHwIn currentA notification to indicate that HW alarm input state has changed. This notification sends additional information about the event by including the following objects in its varbinding list. – ifHwAInputState: HW alarm input contact state. – ifHwAInputType: HW alarm input contact type.
33555.2.10.14trpHotStby currentA notification to indicate that device in Hot Standby mode has been activated. This notification sends additional information about the event by including the following objects in its varbinding list. – serialNumber: Product serial number. – stationName: Station name.
33555.2.10.15trpBpath currentA notification to indicate a change in Backup paths system – backup path state has changed. This notification sends additional information about the event by including the following objects in its varbinding list. – bpathsPeerIp: Backup path peer IP address. – bpathsName: Backup path symbolic name. – bpathsAltUsedPrio: Currently used alternative path priority number. – bpathsAltUsedGw: Currently used alternative path gateway IP address. – bpathsAltUsedState: Currently used alternative path state.
33555.2.10.16trpBpathAlt currentA notification to indicate a change in Backup paths system – alternative path state has changed. This notification sends additional information about the event by including the following objects in its varbinding list. – bpathsPeerIp: Backup path peer IP address. – bpathsName: Backup path symbolic name. – bpathsAltUsedPrio: Currently used alternative path priority number. – bpathsAltUsedGw: Currently used alternative path gateway IP address. – bpathsAltUsedState: Currently used alternative path state.
33555.2.10.17trpUnitReady currentA notification to indicate that Unit ready signal has changed. This notification sends additional information about the event by including the following objects in its varbinding list. – alarmStateUnitReady: alarm input state.