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
| iscomSwitch | OBJECT-IDENTITY |
From SNMPv2-SMI
| Counter32 | |
| MODULE-IDENTITY | |
| OBJECT-TYPE | |
| Unsigned32 |
From SNMPv2-TC
| MacAddress |
From SWITCH-SYSTEM-MIB
| rcPortIndex | OBJECT-TYPE |
From SWITCH-TC
| EnableVar |
How to Use in IPNetwork Monitor
Example using rcRelayEncapStats OID:
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.