OPTIX-RMON-MIB: View SNMP OID List / Download MIB

This module describes the private Rmon of Huawei transmit platform.

alarmIndex

alarmVariable

alarmSampleType Enumeration: 'absoluteValue': 1, 'deltaValue': 2.

alarmValue

alarmRisingThreshold

alarmFallingThreshold

alarmInterval

Date and time.

The SNMP trap that is generated when an alarm entry crosses its rising threshold and generates an event that is configured for sending SNMP traps.

The SNMP trap that is generated when an alarm entry crosses its falling threshold and generates an event that is configured for sending SNMP traps.

A list of Ethernet statistics entries.

A collection of statistics kept for a particular Ethernet interface. As an example, an instance of the etherStatsPkts object might be named etherStatsPkts.1

The value of this object uniquely identifies this etherStats entry. etherStatsIndex of huawei optix devices can be described as following, etherStatsIndex consists of SLOT_ID,PORT_ID and SUB_PORT_ID. etherStatsIndex = SUB_PORT_ID<<31 + SLOT_ID<<24 + PORT_ID; 1) bit31(1bit) SUB_PORT_ID: 0 - SUB_PORT_1(east), 1 - SUB_PORT_2(west), for sonet,this para is 0 ,no other means; 2) 24bit~30bit(7bits) SLOT_ID: slot id; 3) 0bit~15bit(16bits) PORT_ID: mac port id; For example: 1:etherStatsIndex.83886081 (gauge) 83886081 83886081 = 0x05000001 can be translated as Slot-5, Port-1; 2:etherStatsIndex.83886082 (gauge) 83886082 83886082 = 0x05000002 can be translated as Slot-5, Port-2;

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.

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.

The total number of packets (including bad packets, broadcast packets, and multicast packets) received.

The total number of good packets received that were directed to the broadcast address. Note that this does not include multicast packets.

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.

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

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.

The total number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets) and were otherwise well formed.

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.

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.

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.

The total number of packets (including bad packets) received that were 64 octets in length (excluding framing bits but including FCS octets).

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

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

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

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

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

A list of Ethernet statistics entries.

A collection of statistics kept for a particular Ethernet interface. As an example, an instance of the etherStatsPkts object might be named etherStatsPkts.1

The value of this object uniquely identifies this etherExStats entry. etherExStatsIndex of huawei optix devices can be described as following, etherExStatsIndex consists of SLOT_ID,PORT_ID and SUB_PORT_ID. etherExStatsIndex = SUB_PORT_ID<<31 + SLOT_ID<<24 + PORT_ID; 1) bit31(1bit) SUB_PORT_ID: 0 - SUB_PORT_1(east), 1 - SUB_PORT_2(west), for sonet,this para is 0 ,no other means; 2) 24bit~30bit(7bits) SLOT_ID: slot id; 3) 0bit~15bit(16bits) PORT_ID: mac port id; For example: 1: etherExStatsIndex.117440513 (gauge) 117440513 117440513 = 0x07000001(hex) can be translated as Slot-7, Port-1; 2: etherExStatsIndex.117440514 (gauge) 117440514 117440514 = 0x07000002 can be translated as Slot-7, Port-2;

A list of history control entries.

A list of parameters that set up a periodic sampling of statistics. As an example, an instance of the historyControlInterval object might be named historyControlInterval.2

An index that uniquely identifies an entry in the historyControl table. Each such entry defines a set of samples at a particular interval for an interface on the device. historyControlIndex of huawei optix devices can be described as following, historyControlIndex consists of SLOT_ID,PORT_ID,SUB_PORT_ID and PERIOD_TYPE. historyControlIndex = SUB_PORT_ID<<31 + SLOT_ID<<24 + PERIOD_TYPE<<16 + PORT_ID; 1) 31bit(1bit) SUB_PORT_ID 1bit: 0 - SUB_PORT_1(east), 1 - SUB_PORT_2(west) for sonet,this para is 0 ,no other means; 2) 24bit~30bit(7bits) SLOT_ID: slot id; 3) 16bit~23(8bits) PERIOD_TYPE: period type; 0x1 - 30s(30 seconds) 0x2 - 30m(30 minutes) 0x3 - prdvar(var period) 4) 0bit~15bit(16bits) PORT_ID: mac port id; For example: 1: historyControlIndex.83951617 (gauge) 83951617 83951617 = 0x05010001 can be translated as Slot-5,PrdType-30s,Port-1; 2: historyControlIndex.84017153 (gauge) 84017153 84017153 = 0x05020001 can be translated as Slot-5,PrdType-30m,Port-1; 3: historyControlIndex.84082696 (gauge) 84082696 84082696 = 0x05030008 can be translated as Slot-5,PrdType-prdvar,Port-8;

The requested number of discrete time intervals over which data is to be saved in the part of the media-specific table associated with this historyControlEntry. When this object is created or modified, the probe should set historyControlBucketsGranted as closely to this object as is possible for the particular probe implementation and available resources.

The interval in seconds over which the data is sampled for each bucket in the part of the media-specific table associated with this historyControlEntry. Because the counters in a bucket may overflow at their maximum value with no indication, a prudent manager will take into account the possibility of overflow in any of the associated counters. It is important to consider the minimum time in which any counter could overflow on a particular media type and set the historyControlInterval object to a value less than this interval. This is typically most important for the 'octets' counter in any media-specific table. For example, on an Ethernet network, the etherHistoryOctets counter could overflow in about one hour at the Ethernet's maximum utilization. This object may not be modified if the associated historyControlStatus object is equal to valid(1).

The status of this historyControl . Enumeration: 'valid': 1, 'invalid': 4.

A list of Ethernet history entries.

An historical sample of Ethernet statistics on a particular Ethernet interface. This sample is associated with the historyControlEntry which set up the parameters for a regular collection of these samples. As an example, an instance of the etherHistoryPkts object might be named etherHistoryPkts.2.89

The history of which this entry is a part. The history identified by a particular value of this index is the same history as identified by the same value of historyControlIndex. etherHistoryIndex of huawei optix devices can be described as following, etherHistoryIndex consists of SLOT_ID,PORT_ID,SUB_PORT_ID and PERIOD_TYPE. etherHistoryIndex = SUB_PORT_ID<<31 + SLOT_ID<<24 + PERIOD_TYPE<<16 + PORT_ID; 1) 31bit(1bit) SUB_PORT_ID 1bit: 0 - SUB_PORT_1(east), 1 - SUB_PORT_2(west) for sonet,this para is 0 ,no other means; 2) 24bit~30bit(7bits) SLOT_ID: slot id; 3) 16bit~23(8bits) PERIOD_TYPE: period type; 0x1 - 30s(30 seconds) 0x2 - 30m(30 minutes) 0x3 - prdvar(var period) 4) 0bit~15bit(16bits) PORT_ID: mac port id; For example: 1: etherHistoryIndex.83951617 (gauge) 83951617 83951617 = 0x05010001 can be translated as Slot-5,PrdType-30s,Port-1; 2: etherHistoryIndex.84017153 (gauge) 84017153 84017153 = 0x05020001 can be translated as Slot-5,PrdType-30m,Port-1; 3: etherHistoryIndex.84082696 (gauge) 84082696 84082696 = 0x05030008 can be translated as Slot-5,PrdType-prdvar,Port-8;

An index that uniquely identifies the particular sample this entry represents among all samples associated with the same historyControlEntry. This index starts at 1 and increases by one as each new sample is taken.

The total number of events in which packets were dropped by the probe due to lack of resources during this sampling interval. Note that this number is not necessarily the number of packets dropped, it is just the number of times this condition has been detected.

The total number of octets of data (including those in bad packets) received on the network (excluding framing bits but including FCS octets).

The number of packets (including bad packets) received during this sampling interval.

The number of good packets received during this sampling interval that were directed to the broadcast address.

The number of good packets received during this sampling interval that were directed to a multicast address. Note that this number does not include packets addressed to the broadcast address.

The number of packets received during this sampling interval that had a length (excluding framing bits but including FCS octets) 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).

The number of packets received during this sampling interval that were less than 64 octets long (excluding framing bits but including FCS octets) and were otherwise well formed.

The number of packets received during this sampling interval that were longer than 1518 octets (excluding framing bits but including FCS octets) but were otherwise well formed.

The total number of packets received during this sampling interval that were less than 64 octets in length (excluding framing bits but including FCS octets) 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 etherHistoryFragments to increment. This is because it counts both runts (which are normal occurrences due to collisions) and noise hits.

The number of packets received during this sampling interval 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.

The best estimate of the total number of collisions on this Ethernet segment during this sampling interval. 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.

The best estimate of the mean physical layer network utilization on this interface during this sampling interval, in hundredths of a percent.

A list of Exetend Ethernet history entries.

A collection of statistics kept for a particular Ethernet interface. As an example, an instance of the etherStatsPkts object might be named etherStatsPkts.1

The history of which this entry is a part. The history identified by a particular value of this index is the same history as identified by the same value of historyControlIndex. etherExHistoryIndex of huawei optix devices can be described as following, etherExHistoryIndex consists of SLOT_ID,PORT_ID,SUB_PORT_ID and PERIOD_TYPE. etherExHistoryIndex = SUB_PORT_ID<<31 + SLOT_ID<<24 + PERIOD_TYPE<<16 + PORT_ID; 1) 31bit(1bit) SUB_PORT_ID 1bit: 0 - SUB_PORT_1(east), 1 - SUB_PORT_2(west) for sonet,this para is 0 ,no other means; 2) 24bit~30bit(7bits) SLOT_ID: slot id; 3) 16bit~23(8bits) PERIOD_TYPE: period type; 0x1 - 30s(30 seconds) 0x2 - 30m(30 minutes) 0x3 - prdvar(var period) 4) 0bit~15bit(16bits) PORT_ID: mac port id; For example: 1: etherExHistoryIndex.83951617 (gauge) 83951617 83951617 = 0x05010001 can be translated as Slot-5,PrdType-30s,Port-1; 2: etherExHistoryIndex.84017153 (gauge) 84017153 84017153 = 0x05020001 can be translated as Slot-5,PrdType-30m,Port-1; 3: etherExHistoryIndex.84082696 (gauge) 84082696 84082696 = 0x05030008 can be translated as Slot-5,PrdType-prdvar,Port-8;

An index that uniquely identifies the particular sample this entry represents among all samples associated with the same historyControlEntry. This index starts at 1 and increases by one as each new sample is taken.

A list of alarm entries.

A list of parameters that set up a periodic checking for alarm conditions. For example, an instance of the alarmValue object might be named alarmValue.8

An index that uniquely identifies an entry in the alarm table. Each such entry defines a diagnostic sample at a particular interval for an object on the device. alarmIndex of huawei optix devices can be described as following, alarmIndex consists of SLOT_ID,PORT_ID and SUB_PORT_ID. alarmIndex = SUB_PORT_ID<<31 + SLOT_ID<<24 + PORT_ID; 1) bit31(1bit) SUB_PORT_ID: 0 - SUB_PORT_1(east), 1 - SUB_PORT_2(west), for sonet,this para is 0 ,no other means; 2) 24bit~30bit(7bits) SLOT_ID: slot id; 3) 0bit~15bit(16bits) PORT_ID: mac port id; For example: 1:alarmIndex.83886081.122 (gauge) 83886081 83886081 = 0x05000001 can be translated as Slot-5, Port-1; 2:alarmIndex.83886082.122 (gauge) 83886082 83886082 = 0x05000002 can be translated as Slot-5, Port-2;

Enumeration: 'absoluteValue': 1, 'deltaValue': 2.

The alarm that may be sent when this entry is first set to valid. If the first sample after this entry becomes valid is greater than or equal to the risingThreshold and alarmStartupAlarm is equal to risingAlarm(1) or risingOrFallingAlarm(3), then a single rising alarm will be generated. If the first sample after this entry becomes valid is less than or equal to the fallingThreshold and alarmStartupAlarm is equal to fallingAlarm(2) or risingOrFallingAlarm(3), then a single falling alarm will be generated. This object may not be modified if the associated alarmStatus object is equal to valid(1). Enumeration: 'fallingAlarm': 2, 'risingAlarm': 1, 'risingOrFallingAlarm': 3.

A threshold for the sampled statistic. When the current sampled value is greater than or equal to this threshold, and the value at the last sampling interval was less than this threshold, a single event will be generated. A single event will also be generated if the first sample after this entry becomes valid is greater than or equal to this threshold and the associated alarmStartupAlarm is equal to risingAlarm(1) or risingOrFallingAlarm(3). After a rising event is generated, another such event will not be generated until the sampled value falls below this threshold and reaches the alarmFallingThreshold. This object may not be modified if the associated alarmStatus object is equal to valid(1).

A threshold for the sampled statistic. When the current sampled value is less than or equal to this threshold, and the value at the last sampling interval was greater than this threshold, a single event will be generated. A single event will also be generated if the first sample after this entry becomes valid is less than or equal to this threshold and the associated alarmStartupAlarm is equal to fallingAlarm(2) or risingOrFallingAlarm(3). After a falling event is generated, another such event will not be generated until the sampled value rises above this threshold and reaches the alarmRisingThreshold. This object may not be modified if the associated alarmStatus object is equal to valid(1).

The status of this alarm variable. Enumeration: 'valid': 1, 'invalid': 4.

Enter the description of the created OBJECT-GROUP.

Enter the description of the created NOTIFICATION-GROUP.

Enter the description of the created MODULE-COMPLIANCE.