OPTIX-HK-RMON-MIB

All MIBs › OPTIX-HK-RMON-MIB

Organization: Huawei Optix OSP Working Group

Last Updated: 2004-12-01

Category: Optical Networking

Description: Provides RMON-based traffic monitoring extensions for the Huawei OptiX SDH/SONET optical transport platform.

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 OPTIX-HK-RMON-MIB?

OPTIX-HK-RMON-MIB is a Huawei-proprietary SNMP module that provides RMON (Remote Network Monitoring)-based traffic monitoring extensions for the Huawei OptiX SDH/SONET optical transport platform. It belongs to the performance/traffic-monitoring category of MIBs, extending the standard RMON model with Huawei-specific statistics tailored to optical transport port traffic. Functionally, it supports monitoring the operational performance of the transport platform's ports and links, tracking traffic volumes, errors, and utilization trends that can reveal congestion, degraded links, or abnormal traffic patterns on the optical transmission equipment, though it is used for traffic/performance status rather than physical sensors like temperature. As an 'RMON' extension, it inherently depends on and extends concepts from the standard IETF RMON MIB (RFC 2819), adapted to Huawei's private OID space for its OptiX platform. It is typically deployed by carriers and network operators running Huawei OptiX SDH/SONET transport equipment who want RMON-style traffic visibility integrated with their existing RMON-based monitoring tools. Network engineers evaluating or troubleshooting this functionality can download the OPTIX-HK-RMON-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in OPTIX-HK-RMON-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

Huawei OptiX SDH/SONET optical transport platform

Monitoring Examples

No sample objects were captured for this MIB in the available metadata, so specific table/object names cannot be confirmed, but consistent with standard RMON conventions extended here, an operator would expect to poll port-level traffic statistics, history, and threshold-alarm objects analogous to RMON's stats/history/alarm groups. A sustained rise in error or utilization counters on a given OptiX port would indicate a degrading optical link or oversubscribed traffic path. This description should be treated as inferred from the module's stated purpose rather than verified against concrete object names.

What Can Be Monitored

port traffic statistics counters
traffic utilization/history trends
RMON-style alarm thresholds

Imported Objects

From OPTIX-OID-MIB

optixCommon

OBJECT-IDENTITY

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter64
Integer32
MODULE-IDENTITY
OBJECT-TYPE
mib-2

OIDs

OID symbolic	OID numeric	Type	Access	Description
optixHKRmonMib	1.3.6.1.4.1.2011.2.25.3.30			This module describes the private Rmon statics of Huawei transmit platform.
statistics	1.3.6.1.4.1.2011.2.25.3.30.10
etherStatsTable	1.3.6.1.4.1.2011.2.25.3.30.10.1		not-accessible	A list of Ethernet statistics entries.
etherStatsEntry	1.3.6.1.4.1.2011.2.25.3.30.10.1.1		not-accessible	A collection of statistics kept for a particular Ethernet interface. As an example, an instance of the etherStatsPkts object might be named etherStatsPkts.1
I32 etherStatsIndex	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.1	Integer32	read-only	The value of this object uniquely identifies this etherStats entry.
C64 etherStatsDropEvents	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.3	Counter64	read-only	The total number of events in which packets were dropped by the probe due to lack of resources. Note that this number is not necessarily the number of packets dropped; it is just the number of times this condition has been detected.
C64 etherStatsOctets	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.4	Counter64	read-only	The total number of octets of data (including those in bad packets) received on the network (excluding framing bits but including FCS octets). This object can be used as a reasonable estimate of 10-Megabit ethernet utilization. If greater precision is desired, the etherStatsPkts and etherStatsOctets objects should be sampled before and after a common interval. The differences in the sampled values are Pkts and Octets, respectively, and the number of seconds in the interval is Interval. These values are used to calculate the Utilization as follows: Pkts * (9.6 + 6.4) + (Octets * .8) Utilization = ------------------------------------- Interval * 10,000 The result of this equation is the value Utilization which is the percent utilization of the ethernet segment on a scale of 0 to 100 percent.
C64 etherStatsPkts	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.5	Counter64	read-only	The total number of packets (including bad packets, broadcast packets, and multicast packets) received.
C64 etherStatsBroadcastPkts	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.6	Counter64	read-only	The total number of good packets received that were directed to the broadcast address. Note that this does not include multicast packets.
C64 etherStatsMulticastPkts	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.7	Counter64	read-only	The total number of good packets received that were directed to a multicast address. Note that this number does not include packets directed to the broadcast address.
C64 etherStatsCRCAlignErrors	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.8	Counter64	read-only	The total number of packets received that had a length (excluding framing bits, but including FCS octets) of between 64 and 1518 octets, inclusive, but had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error).
C64 etherStatsUndersizePkts	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.9	Counter64	read-only	The total number of packets received that were less than 64 octets long (excluding framing bits, but including FCS octets) and were otherwise well formed.
C64 etherStatsOversizePkts	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.10	Counter64	read-only	The total number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets) and were otherwise well formed.
C64 etherStatsFragments	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.11	Counter64	read-only	The total number of packets received that were less than 64 octets in length (excluding framing bits but including FCS octets) and had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error). Note that it is entirely normal for etherStatsFragments to increment. This is because it counts both runts (which are normal occurrences due to collisions) and noise hits.
C64 etherStatsJabbers	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.12	Counter64	read-only	The total number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets), and had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error). Note that this definition of jabber is different than the definition in IEEE-802.3 section 8.2.1.5 (10BASE5) and section 10.3.1.4 (10BASE2). These documents define jabber as the condition where any packet exceeds 20 ms. The allowed range to detect jabber is between 20 ms and 150 ms.
C64 etherStatsCollisions	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.13	Counter64	read-only	The best estimate of the total number of collisions on this Ethernet segment. The value returned will depend on the location of the RMON probe. Section 8.2.1.3 (10BASE-5) and section 10.3.1.3 (10BASE-2) of IEEE standard 802.3 states that a station must detect a collision, in the receive mode, if three or more stations are transmitting simultaneously. A repeater port must detect a collision when two or more stations are transmitting simultaneously. Thus a probe placed on a repeater port could record more collisions than a probe connected to a station on the same segment would. Probe location plays a much smaller role when considering 10BASE-T. 14.2.1.4 (10BASE-T) of IEEE standard 802.3 defines a collision as the simultaneous presence of signals on the DO and RD circuits (transmitting and receiving at the same time). A 10BASE-T station can only detect collisions when it is transmitting. Thus probes placed on a station and a repeater, should report the same number of collisions. Note also that an RMON probe inside a repeater should ideally report collisions between the repeater and one or more other hosts (transmit collisions as defined by IEEE 802.3k) plus receiver collisions observed on any coax segments to which the repeater is connected.
C64 etherStatsPkts64Octets	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.14	Counter64	read-only	The total number of packets (including bad packets) received that were 64 octets in length (excluding framing bits but including FCS octets).
C64 etherStatsPkts65to127Octets	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.15	Counter64	read-only	The total number of packets (including bad packets) received that were between 65 and 127 octets in length inclusive (excluding framing bits but including FCS octets).
C64 etherStatsPkts128to255Octets	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.16	Counter64	read-only	The total number of packets (including bad packets) received that were between 128 and 255 octets in length inclusive (excluding framing bits but including FCS octets).
C64 etherStatsPkts256to511Octets	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.17	Counter64	read-only	The total number of packets (including bad packets) received that were between 256 and 511 octets in length inclusive (excluding framing bits but including FCS octets).
C64 etherStatsPkts512to1023Octets	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.18	Counter64	read-only	The total number of packets (including bad packets) received that were between 512 and 1023 octets in length inclusive (excluding framing bits but including FCS octets).
C64 etherStatsPkts1024to1518Octets	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.19	Counter64	read-only	The total number of packets (including bad packets) received that were between 1024 and 1518 octets in length inclusive (excluding framing bits but including FCS octets).
C64 etherStatsPkts1519toMtuOctets	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.22	Counter64	read-only
C64 etherStatsTranPkts64Octets	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.23	Counter64	read-only
C64 etherStatsTranPkts65to127Octets	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.24	Counter64	read-only
C64 etherStatsTranPkts128to255Octets	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.25	Counter64	read-only
C64 etherStatsTranPkts256to511Octets	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.26	Counter64	read-only
C64 etherStatsTranPkts512to1023Octets	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.27	Counter64	read-only
C64 etherStatsTranPkts1024to1518Octets	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.28	Counter64	read-only
C64 etherStatsTranPkts1519toMtuOctets	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.29	Counter64	read-only
C64 etherStatsRxTxPkts64Octets	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.30	Counter64	read-only
C64 etherStatsRxTxPkts65to127Octets	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.31	Counter64	read-only
C64 etherStatsRxTxPkts128to255Octets	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.32	Counter64	read-only
C64 etherStatsRxTxPkts256to511Octets	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.33	Counter64	read-only
C64 etherStatsRxTxPkts512to1023Octets	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.34	Counter64	read-only
C64 etherStatsRxTxPkts1024to1518Octets	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.35	Counter64	read-only
C64 etherStatsRxTxPkts1519toMtuOctets	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.36	Counter64	read-only
C64 etherStatsInUcastPkts	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.37	Counter64	read-only
C64 etherStatsOutUcastPkts	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.38	Counter64	read-only
C64 etherStatsInPauseFrames	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.39	Counter64	read-only
C64 etherStatsOutPauseFrames	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.40	Counter64	read-only
C64 etherStatsOutMulticastPkts	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.41	Counter64	read-only
C64 etherStatsOutBroadcastPkts	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.42	Counter64	read-only
C64 etherStatsInGoodOctets	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.43	Counter64	read-only
C64 etherStatsOutGoodOctets	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.44	Counter64	read-only
C64 etherStatsInBadOctets	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.45	Counter64	read-only
C64 etherStatsOutBadOctets	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.46	Counter64	read-only
C64 etherStatsAlignmentErrors	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.47	Counter64	read-only
C64 etherStatsFCSErrors	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.48	Counter64	read-only
C64 etherStatsSingleCollisionFrames	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.49	Counter64	read-only
C64 etherStatsMultipleCollisionFrames	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.50	Counter64	read-only
C64 etherStatsLateCollisions	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.51	Counter64	read-only
C64 etherStatsExcessiveCollisions	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.52	Counter64	read-only
C64 etherStatsDeferredTransmissions	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.53	Counter64	read-only
C64 etherStatsCarrierSenseErrors	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.54	Counter64	read-only
C64 etherStatsInControlFrames	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.55	Counter64	read-only
C64 etherStatsOutControlFrames	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.56	Counter64	read-only
C64 etherStatsOutDropEvents	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.57	Counter64	read-only
C64 etherStatsOutOversizePkts	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.58	Counter64	read-only
C64 etherStatsOutPkts	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.59	Counter64	read-only
C64 etherStatsOutOctets	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.60	Counter64	read-only
C64 etherStatsRxFullGoodOcetcs	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.61	Counter64	read-only	The total number of received octets of good packets(including framing bits and FCS octets).
C64 etherStatsTxFullGoodOctecs	1.3.6.1.4.1.2011.2.25.3.30.10.1.1.62	Counter64	read-only	The total number of transmited octets of good packets(including framing bits and FCS octets).
optixRmonMibConformance	1.3.6.1.4.1.2011.2.25.3.30.99
optixRmonMibGroups	1.3.6.1.4.1.2011.2.25.3.30.99.1
currentObjectGroup	1.3.6.1.4.1.2011.2.25.3.30.99.1.1			Enter the description of the created OBJECT-GROUP.
optixRmonMibCompliances	1.3.6.1.4.1.2011.2.25.3.30.99.2
basicCompliance	1.3.6.1.4.1.2011.2.25.3.30.99.2.1			Enter the description of the created MODULE-COMPLIANCE.

RFC description

Provides RMON statistics for Huawei OPTIX SONET transmission platform alarm and performance monitoring.

Start monitoring Huawei OptiX SDH/SONET optical transport platform (private RMON traffic statistics) 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 OPTIX-HK-RMON-MIB

What Is OPTIX-HK-RMON-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description