RAISECOM-RELAY-MIB :: rcRelayEncapStats

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › RAISECOM-RELAY-MIB › rcRelayEncapStats

rcRelayEncapStats

Module: RAISECOM-RELAY-MIB

OID (symbolic): RAISECOM-RELAY-MIB::rcRelayEncapStats

OID (numeric): 1.3.6.1.4.1.8886.6.1.35.4.1.2

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: The tunneled PDU encapsulation statistics of an interface. These statistics cover the number of tunneled ingress PDUs.

What is rcRelayEncapStats?

rcRelayEncapStats is a Counter32 tracking the number of ingress PDUs that have been encapsulated for tunneling on an interface, for a given protocol. Admins monitor this counter to confirm that expected control-plane traffic (like BPDUs) is actually being picked up and tunneled rather than dropped or ignored. For example, a steadily incrementing rcRelayEncapStats for the stp protocol confirms spanning-tree frames are being encapsulated for relay across the network.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.8886.6.1.35.4.1.2
snmpwalk -v2c -c public <target> RAISECOM-RELAY-MIB::rcRelayEncapStats

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.8886.6.1.35.4.1.2.1
snmpget -v2c -c public <target> RAISECOM-RELAY-MIB::rcRelayEncapStats.1

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> rcRelayEncapStats.1

Start monitoring Raisecom switch, access/aggregation device (relay/dry-contact alarm outputs) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the RAISECOM-RELAY-MIB::rcRelayEncapStats OID value, configure state conditions and alerts, and monitor any Raisecom switch, access/aggregation device (relay/dry-contact alarm outputs) from a single console.

How to Use in IPNetwork Monitor

Select a Raisecom switch, access/aggregation device (relay/dry-contact alarm outputs) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type rcRelayEncapStats into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The tunneled PDU encapsulation statistics of an interface. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline (in encapsulated PDUs), since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (9 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.8886raisecomRAISECOM-BASE-MIB
1.3.6.1.4.1.8886.6iscomSeriesRAISECOM-BASE-MIB
1.3.6.1.4.1.8886.6.1iscomSwitchRAISECOM-BASE-MIB
Numeric OIDNameModule
1.3.6.1.4.1.8886.6.1.35rcRelayRAISECOM-RELAY-MIB
1.3.6.1.4.1.8886.6.1.35.4rcRelayStatisticsTableRAISECOM-RELAY-MIB
1.3.6.1.4.1.8886.6.1.35.4.1rcRelayStatisticsEntryRAISECOM-RELAY-MIB
1.3.6.1.4.1.8886.6.1.35.4.1.2rcRelayEncapStatsRAISECOM-RELAY-MIB