REDSTONE-HDLC-MIB

All MIBs › REDSTONE-HDLC-MIB

Organization: Redstone Communications, Inc.

Last Updated: 1999-07-28

Category: DSL and Broadband Access

Description: Manages HDLC serial interface configuration and statistics on Redstone Communications edge routers.

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 REDSTONE-HDLC-MIB?

REDSTONE-HDLC-MIB is a Redstone Communications enterprise MIB for configuring and monitoring HDLC (High-Level Data Link Control) serial interfaces on the company's edge routers. It exposes a per-interface HDLC table covering MTU, MRU, CRC size, data polarity, the underlying lower-layer interface index, and row status for interface creation/deletion. Its monitoring relevance is at the data-link layer of software/hardware configuration: verifying rsHdlcIfMtu/rsHdlcIfMru and rsHdlcIfCrcSize match the far-end configuration, since a mismatch would cause framing errors or link instability on the serial circuit. It is a self-contained Redstone enterprise MIB layered on top of standard serial-interface concepts (paralleling but not directly dependent on the IETF's own HDLC-related MIBs). It is deployed on Redstone Communications routers using HDLC-framed serial or leased-line WAN circuits, common in legacy or specialized point-to-point WAN links, where REDSTONE-HDLC-MIB SNMP monitoring helps confirm framing parameters stay in sync between both ends.

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

Redstone Communications edge router

Monitoring Examples

An engineer troubleshooting a flapping serial link would check rsHdlcIfTable (rsHdlcIfEntry) for rsHdlcIfMtu, rsHdlcIfMru, and rsHdlcIfCrcSize on a given rsHdlcIfIndex/rsHdlcIfLowerIfIndex to confirm HDLC framing parameters match what the far end expects. A CRC-size or data-polarity (rsHdlcIfDataPolarity) mismatch between the two ends of the circuit would explain persistent framing errors or an interface that won't come up, and rsHdlcIfRowStatus confirms whether the HDLC binding is currently active.

What Can Be Monitored

HDLC interface MTU/MRU
CRC size configuration
data polarity setting
HDLC interface row status

Imported Objects

From IF-MIB

InterfaceIndex
InterfaceIndexOrZero

From REDSTONE-SMI

rsMgmt

OBJECT-IDENTITY

From REDSTONE-TC

RsNextIfIndex

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Integer32
MODULE-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

RowStatus

OIDs

OID symbolic	OID numeric	Type	Access	Description
rsHdlcMIB	1.3.6.1.4.1.2773.2.9			The HDLC MIB for the Redstone Communications Inc. enterprise.
rsHdlcObjects	1.3.6.1.4.1.2773.2.9.1
RSN rsHdlcNextIfIndex	1.3.6.1.4.1.2773.2.9.1.1	RsNextIfIndex	read-only	Coordinate ifIndex value allocation for entries in rsHdlcIfTable. A GET of this object returns the next available ifIndex value to be used to create an entry in the associated interface table; or zero, if no valid ifIndex value is available. This object also returns a value of zero when it is the lexicographic successor of a varbind presented in an SNMP GETNEXT or GETBULK request, for which circumstance it is assumed that ifIndex allocation is unintended. Successive GETs will typically return different values, thus avoiding collisions among cooperating management clients seeking to create table entries simultaneously.
rsHdlcIfTable	1.3.6.1.4.1.2773.2.9.1.2		not-accessible	This table contains entries for HDLC interfaces present in the system.
rsHdlcIfEntry	1.3.6.1.4.1.2773.2.9.1.2.1		not-accessible	Each entry describes the characteristics of an HDLC interface. Creating/deleting entries in this table causes corresponding entries for be created /deleted in ifTable/ifXTable/rsIfTable.
NUM rsHdlcIfIndex	1.3.6.1.4.1.2773.2.9.1.2.1.1	InterfaceIndex	not-accessible	The ifIndex of the HDLC interface. When creating entries in this table, suitable values for this object are determined by reading rsHdlcNextIfIndex.
ROW rsHdlcIfRowStatus	1.3.6.1.4.1.2773.2.9.1.2.1.2	RowStatus	read-create	Controls creation/deletion of entries in this table according to the RowStatus textual convention, constrained to support the following values only: createAndGo destroy To create an entry in this table, the following entry objects MUST be explicitly configured: rsHdlcIfRowStatus rsHdlcIfLowerIfIndex In addition, when creating an entry the following conditions must hold: A value for rsHdlcIfIndex must have been determined previously, by reading rsHdlcNextIfIndex. The interface identified by rsHdlcIfLowerIfIndex must exist. A corresponding entry in ifTable/ifXTable/rsIfTable is created/destroyed as a result of creating/destroying an entry in this table.
NUM rsHdlcIfLowerIfIndex	1.3.6.1.4.1.2773.2.9.1.2.1.3	InterfaceIndexOrZero	read-create	The ifIndex of an interface over which this HDLC interface is to be layered. A value of zero indicates no layering. An implementation may choose to require that a nonzero value be configured at entry creation.
I32 rsHdlcIfMtu	1.3.6.1.4.1.2773.2.9.1.2.1.4	Integer32	read-create	The Maximum Transmission Unit this interface is permitted to transmit. At creation, if a value for this object is not specified, a suitable default will be chosen for the type of lower interface on which this interface is stacked. This setting plus 2 bytes for HDLC address/control plus the length in bytes of the HDLC CRC cannot exceed 65535. The maximum value for this object reflects the largest possible value when no CRC is used; technology constraints of a particular implementation may further limit the upper bound value.
I32 rsHdlcIfMru	1.3.6.1.4.1.2773.2.9.1.2.1.5	Integer32	read-create	The Maximum Receive Unit this interface is permitted to receive. At creation, if a value for this object is not specified, a suitable default will be chosen for the type of lower interface on which this interface is stacked. This setting plus 2 bytes for HDLC address/control plus the length in bytes of the HDLC CRC cannot exceed 65535. The maximum value for this object reflects the largest possible value when no CRC is used; technology constraints of a particular implementation may further limit the upper bound value.
INT rsHdlcIfCrcSize	1.3.6.1.4.1.2773.2.9.1.2.1.6	INTEGER	read-create	Selects CRC size: none, 16 bits, or 32 bits.
INT rsHdlcIfDataPolarity	1.3.6.1.4.1.2773.2.9.1.2.1.7	INTEGER	read-create	Polarity of data transmitted on this HDLC interface. Inverted data is used for certain line coding configurations to ensure sufficient one's density for timing recovery by the remote end.
rsHdlcConformance	1.3.6.1.4.1.2773.2.9.4
rsHdlcCompliances	1.3.6.1.4.1.2773.2.9.4.1
rsHdlcCompliance	1.3.6.1.4.1.2773.2.9.4.1.1			The compliance statement for entities which implement the Redstone HDLC MIB.
rsHdlcCompliance2	1.3.6.1.4.1.2773.2.9.4.1.2			The compliance statement for entities which implement the Redstone HDLC MIB.
rsHdlcGroups	1.3.6.1.4.1.2773.2.9.4.2
rsHdlcGroup	1.3.6.1.4.1.2773.2.9.4.2.1			A collection of objects providing management of HDLC interfaces in a Redstone product.
rsHdlcGroup2	1.3.6.1.4.1.2773.2.9.4.2.2			A collection of objects providing management of HDLC interfaces in a Redstone product.

RFC description

Manages HDLC interface configuration and status on Redstone Communications network equipment.

Start monitoring Redstone Communications edge router (HDLC serial interface configuration) 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 REDSTONE-HDLC-MIB

What Is REDSTONE-HDLC-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description