ELTEX-MES-IF-EXTENSION-MIB

All MIBs › ELTEX-MES-IF-EXTENSION-MIB

Category: Vendor: Eltex

Description: Eltex MES interface extension MIB providing proprietary per-interface objects extending the standard IF-MIB for MES switches.

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 ELTEX-MES-IF-EXTENSION-MIB?

ELTEX-MES-IF-EXTENSION-MIB is a vendor-specific Eltex Networks MIB that proprietarily extends the standard IETF IF-MIB with additional per-interface objects for MES-series switches. It exposes tables for custom 802.1Q egress and ingress EtherType configuration and ingress C-VLAN tag settings, used for QinQ/VLAN tunneling scenarios. Its monitoring value is largely configuration-status verification rather than fault counters, letting an admin confirm the actual custom EtherType/tag values programmed on each interface match the intended VLAN tunneling design, which is important software-configuration state for services relying on non-standard tag protocol identifiers. As its name and short description indicate, it explicitly builds on and extends the standard IF-MIB. It is typically deployed on Eltex MES-series access/aggregation switches offering QinQ or custom EtherType VLAN tunneling services, and administrators can download the ELTEX-MES-IF-EXTENSION-MIB file to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in ELTEX-MES-IF-EXTENSION-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

Eltex MES-series Ethernet switch

Monitoring Examples

eltIfDot1qCustomEgressEtherTypeTable/eltIfDot1qCustomEgressEtherTypeEntry reports eltIfDot1qCustomEgressEtherType per interface, letting an admin confirm a port configured for QinQ tunneling has the correct custom TPID for egress tagging. Similarly, eltIfDot1qIngressCvlanTable/eltIfDot1qIngressCvlanEntry exposes eltIfDot1qIngressCvlanTag, and eltIfDot1qCustomIngressEtherTypeTable holds up to four configurable ingress EtherTypes (eltIfDot1qCustomIngressEtherType1-4); a mismatch between the configured ingress EtherType and what upstream equipment sends would show up as VLAN tag misclassification on that interface.

What Can Be Monitored

custom egress EtherType per interface
custom ingress EtherType per interface
ingress C-VLAN tag configuration
802.1Q custom EtherType feature support per interface

Imported Objects

From ELTEX-MES-MNG-MIB

eltMesIfExtensionMIB

OBJECT-IDENTITY

From IF-MIB

InterfaceIndex
InterfaceIndexOrZero
ifIndex	OBJECT-TYPE

From Q-BRIDGE-MIB

PortList

From RFC1155-SMI

Counter

From SNMPv2-SMI

Counter32
Integer32
MODULE-IDENTITY
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

RowStatus

OIDs

OID symbolic	OID numeric	Type	Access	Description
eltMesIfExtensionMIBObjects	1.3.6.1.4.1.35265.1.23.1.276.1
eltMesIfExtDot1qCustomEtherType	1.3.6.1.4.1.35265.1.23.1.276.1.3
eltIfDot1qCustomEgressEtherTypeTable	1.3.6.1.4.1.35265.1.23.1.276.1.3.1		not-accessible	A list of the interfaces that support the 802.1q custom egress ethertype feature.
eltIfDot1qCustomEgressEtherTypeEntry	1.3.6.1.4.1.35265.1.23.1.276.1.3.1.1		not-accessible	An entry containing the custom egress EtherType information for the interface. Only interfaces with custom 802.1q ethertype control are listed in the table.
I32 eltIfDot1qCustomEgressEtherType	1.3.6.1.4.1.35265.1.23.1.276.1.3.1.1.1	Integer32	read-write	The Dot1qEtherType allow administrator to select a non-standard (other than 0x8100) 2-byte ethertype for the interface to interoperate with third party vendor's system that do not use the standard 0x8100 ethertype to identify 802.1q-tagged frames. The current administrative value of the 802.1q ethertype for the interface. The administrative 802.1q ethertype value may differ from the operational 802.1q ethertype value. On some platforms, 802.1q ethertype may be assigned per group rather than per port. If multiple ports belong to a port group, the 802.1q ethertype assigned to any of the ports in such group will apply to all ports in the same group. To configure non-standard dot1q egress ethertype is only recommended when the Eltex device is connected to any third party vendor device.
eltIfDot1qCustomIngressEtherTypeTable	1.3.6.1.4.1.35265.1.23.1.276.1.3.2		not-accessible	A list of the interfaces that support the 802.1q custom ingress ethertype feature.
eltIfDot1qCustomIngressEtherTypeEntry	1.3.6.1.4.1.35265.1.23.1.276.1.3.2.1		not-accessible	An entry containing the custom ingress EtherTypes set for the interface to classify stag and ctag. Only interfaces with custom 802.1q ethertype control are listed in the table.
I32 eltIfDot1qCustomIngressEtherType1	1.3.6.1.4.1.35265.1.23.1.276.1.3.2.1.1	Integer32	read-write	This fields holds default ethertype 0x8100 or zero if ethertype 0x8100 is not used to classify SVLAN on current interface.
I32 eltIfDot1qCustomIngressEtherType2	1.3.6.1.4.1.35265.1.23.1.276.1.3.2.1.2	Integer32	read-write	The custom ethertype to classify ingress vlan tags (SVLAN) for the interface to interoperate with third party vendor's system that do not use the standard 0x8100 ethertype to identify 802.1q-tagged frames.
I32 eltIfDot1qCustomIngressEtherType3	1.3.6.1.4.1.35265.1.23.1.276.1.3.2.1.3	Integer32	read-write	The custom ethertype to classify ingress vlan tags (SVLAN) for the interface to interoperate with third party vendor's system that do not use the standard 0x8100 ethertype to identify 802.1q-tagged frames.
I32 eltIfDot1qCustomIngressEtherType4	1.3.6.1.4.1.35265.1.23.1.276.1.3.2.1.4	Integer32	read-write	The custom ethertype to classify ingress vlan tags (SVLAN) for the interface to interoperate with third party vendor's system that do not use the standard 0x8100 ethertype to identify 802.1q-tagged frames.
I32 eltIfDot1qCustomIngressEtherType5	1.3.6.1.4.1.35265.1.23.1.276.1.3.2.1.5	Integer32	read-write	The custom ethertype to classify ingress vlan tags (SVLAN) for the interface to interoperate with third party vendor's system that do not use the standard 0x8100 ethertype to identify 802.1q-tagged frames.
I32 eltIfDot1qCustomIngressEtherType6	1.3.6.1.4.1.35265.1.23.1.276.1.3.2.1.6	Integer32	read-write	The custom ethertype to classify ingress vlan tags (SVLAN) for the interface to interoperate with third party vendor's system that do not use the standard 0x8100 ethertype to identify 802.1q-tagged frames.
I32 eltIfDot1qCustomIngressEtherType7	1.3.6.1.4.1.35265.1.23.1.276.1.3.2.1.7	Integer32	read-write	The custom ethertype to classify ingress vlan tags (SVLAN) for the interface to interoperate with third party vendor's system that do not use the standard 0x8100 ethertype to identify 802.1q-tagged frames.
eltMesIfExtDot1q	1.3.6.1.4.1.35265.1.23.1.276.1.4
eltIfDot1qIngressCvlanTable	1.3.6.1.4.1.35265.1.23.1.276.1.4.1		not-accessible	A list of the interfaces ingress C-VLAN settings.
eltIfDot1qIngressCvlanEntry	1.3.6.1.4.1.35265.1.23.1.276.1.4.1.1		not-accessible	An entry containing ingress C-VLAN assignment for the interface.
I32 eltIfDot1qIngressCvlanTag	1.3.6.1.4.1.35265.1.23.1.276.1.4.1.1.1	Integer32	read-write	C-VLAN tag for the interface assigned in ingress pipe. 0 means no C-VLAN assignment.

RFC description

Manages interface extension features on ELTEX MES network switches including custom 802.1q ethertype configuration and VLAN settings.

Start monitoring Eltex MES-series Ethernet switch (custom 802.1Q EtherType/QinQ) 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 ELTEX-MES-IF-EXTENSION-MIB

What Is ELTEX-MES-IF-EXTENSION-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description