ETHERNET-CONFIGURATION

All MIBs › ETHERNET-CONFIGURATION

Organization: Ericsson Danmark A/S

Last Updated: 2006-01-20

Category: Device Management, Network Interfaces

Description: Defines configuration objects for Ethernet interface parameters including speed, duplex, and autonegotiation settings.

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 ETHERNET-CONFIGURATION?

ETHERNET-CONFIGURATION is a vendor-specific MIB from Ericsson (Diax) scoped under the PEA-INTERFACES-SMI tree, providing configuration and statistics for the downstream overload-protection scheduler on the uplink Ethernet interface of Ericsson access/aggregation network elements. Its vlanPrioToRxPriorityMappingTable lets an operator map incoming VLAN p-bit priority values (vlanPriority, 0-7) to an internal receive priority (rxPriority) so that high-priority downstream traffic (e.g. voice, video) is processed ahead of best-effort data when the element is oversubscribed, with untagged packets defaulting to the highest receive priority. A companion rxPriorityStatisticsTable, indexed by rxPriority, exposes rxPriorityStatisticsPkts, rxPriorityStatisticsDiscards, and rxPriorityStatisticsErrors counters per priority queue, alongside a top-level numberOfRxPriorities object describing how many receive priorities the platform supports. This makes it a QoS-scheduling and overload-protection MIB rather than a general interface-status MIB, useful for confirming that VLAN priority classification is correctly mapped and that no priority queue is silently dropping traffic under load. Operators use the ETHERNET-CONFIGURATION MIB to audit priority-to-queue mappings and discard counters on Ericsson access nodes.

IPNetwork Monitor allows you to monitor SNMP objects defined in ETHERNET-CONFIGURATION. 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

Ericsson Diax access/aggregation network elements

Monitoring Examples

An operator polls rxPriorityStatisticsDiscards for each rxPriority value and cross-references vlanPrioToRxPriorityMappingTable to confirm which VLAN p-bit values feed that queue; a steadily climbing rxPriorityStatisticsDiscards count on the highest-priority queue (rxPriority=1) would indicate the aggregation link is oversubscribed even for voice/video-class traffic.

What Can Be Monitored

VLAN priority to receive-priority mapping table
per-priority received packet counters
per-priority discard counters
per-priority error counters
number of supported receive priorities

Imported Objects

From PEA-INTERFACES-SMI

peaInterfaces

MODULE-IDENTITY

From SNMPv2-SMI

MODULE-IDENTITY
OBJECT-TYPE
Unsigned32

OIDs

OID symbolic	OID numeric	Type	Access	Description
ethernetConfiguration	1.3.6.1.4.1.193.72.600.10.20			The public Ethernet access software supports a number of standard and proprietary MIBs. This MIB module defines objects for reading/writing common Ethernet information. In cases where the network element is overloaded with traffic, it must be ensured that the high priority packets are always processed first. This is done using an overload protection mechanism that is always active. The downstream traffic from the aggregate uplink Ethernet will be processed according to priority. The overload protection is only in use if there is more than one packet waiting to be processed. There are a number of receive priorities in the network element downstream overload protection. This MIB can be used to configure the mapping between VLAN priority of downstream packets and the receive priority in the network element. Statistics for the receive priorities can also be read with this MIB.
uplinkEthernetRxScheduling	1.3.6.1.4.1.193.72.600.10.20.20
U32 numberOfRxPriorities	1.3.6.1.4.1.193.72.600.10.20.20.10	Unsigned32	read-only	With this parameter it is possible to read the number of available receive priorities, which can be used when mapping VLAN tagged incoming downstream packets from the aggregation network to different receive priorities. vlanPrioToRxPriorityMappingTable is used to do the actual mapping between VLAN priority and receive priority.
vlanPrioToRxPriorityMappingTable	1.3.6.1.4.1.193.72.600.10.20.20.15		not-accessible	Different operators uses different VLAN p-bit classification of services. In addition to voice, video and best effort data services, it may also be required to distinguish between various data services, and to classify traffic based on other criteria's than just service. As a consequence, utilization of the entire range of VLAN p-bit values from 0 to 7 is needed. More incoming traffic may arrive from the uplink Ethernet interface, than it is possible to forward on the downlink interface. In this case it is important to forward traffic with highest priority first and drop low priority traffic if necessary. With this table it is possible to configure which receive priority (rxPriority) is used for incoming downstream traffic carrying specific VLAN p-bit values. It is possible to specify, per VLAN p-bit value, which receive priority incoming downstream traffic is allocated to. If more than one VLAN tag is included in the received packets, only the first VLAN tags priority is taken into account when mapping to receive priority. Any packets received without VLAN tag are mapped to the highest receive priority (rxPriority=1). Below is an illustration of how the VLAN priority could be mapped to the receive priorities. The illustration is just and example, any combinations of mappings are valid. Note that the number of receive priorities may vary from one product to another. ___________________________________ \| \| \| \| \| -- p-bit 7 ----> rxPriority 1 \| \| / \| Incoming traffic from \| / \| the aggregation network \| /---- p-bit 6 ----> rxPriority 2 \| (VLAN p-bit 0-7) \|/ \| ----------------------->\|\ \| \| \---- p-bit 5 ----> rxPriority 3 \| \| \ \| \| \ \| \| -- p-bit 0-4 --> rxPriority 4 \| \| \| \|___________________________________\|
vlanPrioToRxPriorityMappingEntry	1.3.6.1.4.1.193.72.600.10.20.20.15.5		not-accessible	This is an entry of the vlanPrioToRxPriorityMappingTable Following example map highest VLAN priority to highest rxPriority. Any combinations of mappings are valid. The vlanPrioToRxPriorityMappingTable will be searched from index 1 and onwards and for first match of VLAN priority the corresponding rxPriority will be used. Note that the valid range of rxPriority may vary from one product to another. vlanPrioToRxPriorityMappingEntry =================================================== \|vlanPrioToRxPriorityIndex\|vlanPriority\|rxPriority\| \| 1 \| 0 \| 8 \| \| 2 \| 1 \| 7 \| \| 3 \| 2 \| 6 \| \| 4 \| 3 \| 5 \| \| 5 \| 4 \| 4 \| \| 6 \| 5 \| 3 \| \| 7 \| 6 \| 2 \| \| 8 \| 7 \| 1 \|
U32 vlanPrioToRxPriorityIndex	1.3.6.1.4.1.193.72.600.10.20.20.15.5.5	Unsigned32	not-accessible	This is the index to the vlanPrioToRxPriorityMappingTable.
U32 vlanPriority	1.3.6.1.4.1.193.72.600.10.20.20.15.5.10	Unsigned32	read-only	This is the VLAN priority to be mapped to a receive queue priority. VLAN priority zero is the lowest priority.
U32 rxPriority	1.3.6.1.4.1.193.72.600.10.20.20.15.5.15	Unsigned32	read-write	Incoming packets received on the uplink interface with the VLAN priority equal to vlanPriority in the vlanPrioToRxQueuePrioMappingEntry, are mapped to the receive queue priority specified with this parameter. Note: Different products may implement different number of receive priorities. One is the highest receive priority.
rxPriorityStatisticsTable	1.3.6.1.4.1.193.72.600.10.20.20.20		not-accessible	This table is used to read out statistics counters per receive priority. Statistics are available for packets delivered to a higher-layer, packets discarded due to no available buffers and packets discarded due to errors.
rxPriorityStatisticsEntry	1.3.6.1.4.1.193.72.600.10.20.20.20.5		not-accessible	This is an entry of the rxPriorityStatisticsTable
U32 rxPriorityStatisticsPkts	1.3.6.1.4.1.193.72.600.10.20.20.20.5.5	Unsigned32	read-only	Number of successfully received packets for the specific receive priority.
U32 rxPriorityStatisticsDiscards	1.3.6.1.4.1.193.72.600.10.20.20.20.5.10	Unsigned32	read-only	Number of packets discarded due to no available buffers for the specific receive priority.
U32 rxPriorityStatisticsErrors	1.3.6.1.4.1.193.72.600.10.20.20.20.5.15	Unsigned32	read-only	Number of packets discarded due to any other reason than no buffers available for the specific receive priority.

RFC description

Ethernet access software configuration MIB for Ericsson DIAX platform, managing VLAN priority mapping and receive scheduling on uplink interfaces.

Start monitoring Ericsson Diax access/aggregation network element (downstream overload protection) 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 ETHERNET-CONFIGURATION

What Is ETHERNET-CONFIGURATION?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description