RAISECOM-RELAY-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › RAISECOM-RELAY-MIB

Organization: Raisecom, Inc.

Last Updated: 2012--0-3-

Category: Raisecom Networks

Description: Manages relay contact and dry-contact output control for environmental alarm signaling.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is RAISECOM-RELAY-MIB?

RAISECOM-RELAY-MIB is a vendor-specific module for Raisecom network devices (switches and access equipment) that manages relay/dry-contact outputs typically wired to external alarm or environmental sensors. It exposes configuration data such as relay MAC address, class-of-service tagging, transparent-forwarding behavior, and a protocol table governing how relay-related traffic (including MPLS-tunneled traffic) is switched and tagged on specific ports. Its primary monitoring value is in tracking the operational status of each configured relay protocol entry (rcRelayProtocolPortStatus) and MPLS tunnel status, which can reveal whether an environmental alarm relay path or VLAN/MPLS transport for relay signaling is up or has failed. It is a self-contained enterprise MIB with no strong dependency on other standard MIBs beyond baseline SNMP SMI conventions. It is typically deployed in Raisecom-based metro/access networks where relay contacts feed alarm systems (door, power, temperature) that need centralized SNMP visibility, making RAISECOM-RELAY-MIB SNMP monitoring a standard part of that alarm-relay oversight.

IPNetwork Monitor allows you to monitor SNMP objects defined in RAISECOM-RELAY-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

  • Raisecom switch
  • Raisecom access/aggregation device

Monitoring Examples

An administrator would poll rcRelayProtocolTable/rcRelayProtocolEntry, checking rcRelayProtocolPortStatus and rcRelayProtocolMplsStatus per rcRelayProtocolType entry to confirm that relay traffic paths across a given rcRelayProtocolEgressPort and rcRelayProtocolVlan are operating normally. A status change from up to down on rcRelayProtocolPortStatus would indicate the relay/dry-contact signaling path (or its MPLS tunnel, rcRelayProtocolMplsVlan) has failed, warranting investigation of the physical relay connection or transport link. rcRelayMacAddress and rcRelayCos are typically checked to verify the relay's identity and traffic prioritization are configured as expected.

What Can Be Monitored

  • relay protocol port status
  • MPLS tunnel status for relay traffic
  • relay MAC address
  • relay traffic class of service
  • transparent forwarding enable state
  • relay egress port and VLAN mapping
Imported Objects

From RAISECOM-BASE-MIB

iscomSwitchOBJECT-IDENTITY

From SNMPv2-SMI

Counter32
MODULE-IDENTITY
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

MacAddress

From SWITCH-SYSTEM-MIB

rcPortIndexOBJECT-TYPE

From SWITCH-TC

EnableVar

How to Use in IPNetwork Monitor

Example using rcRelayEncapStats OID:

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.
OIDs

RFC description

BPDU and transparent frame relay protocol management for network bridges.

Start monitoring Raisecom switch, access/aggregation device (relay/dry-contact alarm outputs) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download RAISECOM-RELAY-MIB