MICOM-RFC1604-MIB

MIB Reference — IPNetwork Monitor · Updated September 09, 2026

All MIBsMICOM-RFC1604-MIB

Category: Frame Relay, WAN

Description: Provides MICOM-specific extensions to RFC 1604 Frame Relay DTE objects.

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 MICOM-RFC1604-MIB?

This is a MICOM Communications vendor MIB module providing MICOM-specific extensions to the standard RFC 1604 Frame Relay DTE (Data Terminal Equipment) MIB. It exposes per-port frame relay logical port (Lport) configuration such as numbering plan, DLCI addressing length, and VC signaling protocol, plus a management VC signaling table tracking signaling procedure and network-side timer (N392) settings. Its monitoring value is largely in frame relay service configuration/signaling health, letting an operator confirm signaling protocol and procedure parameters are consistent for a frame relay port, which affects whether PVC/SVC signaling operates correctly. As its name states, it is explicitly built as an extension to the IETF RFC 1604 Frame Relay DTE MIB, adding MICOM-specific fields on top of that standard. It would be deployed on MICOM frame relay access equipment interoperating with carrier frame relay networks. Engineers can download the MICOM-RFC1604-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in MICOM-RFC1604-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

  • MICOM frame relay access equipment

Monitoring Examples

An operator would poll mcmFrLportTable / mcmFrLportEntry indexed by mcmFrLportIfIndex to check mcmFrLportType and mcmFrLportVCSigProtocol, confirming the frame relay port is configured with the expected signaling protocol for its carrier connection. mcmFrLportAddrDLCILen and mcmFrLportNumPlan would be checked when diagnosing a DLCI addressing mismatch. mcmFrMgtVCSigTable / Entry with mcmFrMgtVCSigProced and mcmFrMgtVCSigNetN392 let an admin verify signaling procedure and retry-counter settings affecting PVC/SVC establishment reliability.

What Can Be Monitored

  • frame relay port type/signaling protocol
  • DLCI addressing length
  • numbering plan
  • VC signaling procedure and N392 timer
Imported Objects

From MICOM-OSCAR-MIB

micom-oscar

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

Counter
OIDs

RFC description

Provides MICOM gateway and router management functions based on RFC 1604 remote access protocols.

Start monitoring MICOM frame relay access equipment (RFC 1604 DTE extension) 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 MICOM-RFC1604-MIB