ETHERNET-CONFIGURATION: View SNMP OID List / Download MIB

VENDOR: ERICSSON AB

Home	MIB: ETHERNET-CONFIGURATION
Download as:		SNMPv2-CONF, SNMPv2-SMI, PEA-INTERFACES-SMI, SNMPv2-TC		Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash). Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded. The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.

Object Name	OID	Type	Access	Info
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
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		no-access	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		no-access	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 \|
vlanPrioToRxPriorityIndex	1.3.6.1.4.1.193.72.600.10.20.20.15.5.5	unsigned32	no-access	This is the index to the vlanPrioToRxPriorityMappingTable.
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.
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		no-access	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		no-access	This is an entry of the rxPriorityStatisticsTable
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.
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.
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.