All MIBs › H3C-QINQV2-MIB
Organization: Hangzhou H3C Tech. Co., Ltd.
Last Updated: 2013-03-08
Category: Technology: VLAN, Vendor: H3C/HH3C
Description: H3C MIB version 2 for QinQ double-tagging with enhanced selective and flexible QinQ configuration options.
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 H3C-QINQV2-MIB?
H3C-QINQV2-MIB is an H3C proprietary MIB (version 2) for the 802.1 QinQ double-VLAN-tagging feature, allowing service-provider VLAN tags to be stacked over customer VLAN tags for VLAN scalability across metro/carrier Ethernet networks. It exposes global TPID (Tag Protocol Identifier) settings for both service and customer tags, plus a per-interface configuration table controlling QinQ state, per-interface TPIDs, and VLAN translation lists. This is a configuration/status MIB for Layer 2 VLAN encapsulation rather than hardware health — it lets operators confirm QinQ is enabled correctly on trunk interfaces and that TPID values match across the network to avoid tag-parsing mismatches. It builds on the IEEE 802.1 VLAN tagging standard (802.1Q/QinQ), extending it with H3C-specific per-interface controls. It's deployed on H3C Ethernet switches at the network edge, aggregating multiple customer VLANs into single provider VLANs for carrier or large enterprise networks. Engineers can download the H3C-QINQV2-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in H3C-QINQV2-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
- H3C Ethernet switches (metro/carrier edge)
Monitoring Examples
An admin would check h3cQinQv2IfCfgTable/h3cQinQv2IfCfgEntry for a given interface's h3cQinQv2IfState to confirm QinQ is enabled, and compare h3cQinQv2IfServiceTPID/h3cQinQv2IfCustomerTPID against the global h3cQinQv2ServiceTPID/h3cQinQv2CustomerTPID to catch a TPID mismatch that would cause double-tagged frames to be misinterpreted. Reviewing h3cQinQv2IfTransVlanList would confirm which customer VLANs are being translated/mapped on a selective QinQ trunk, useful when troubleshooting a customer reporting VLAN traffic not passing correctly.
What Can Be Monitored
- per-interface QinQ enable state
- per-interface service/customer TPID
- global service/customer TPID
- VLAN translation list per interface
Imported Objects
From HUAWEI-3COM-OID-MIB
| h3cCommon | OBJECT-IDENTITY |
From IF-MIB
| ifIndex | OBJECT-TYPE |
From SNMPv2-SMI
| Integer32 | |
| MODULE-IDENTITY | |
| OBJECT-TYPE |
From SNMPv2-TC
| TruthValue |
OIDs
RFC description
802.1 QinQ (VLAN stacking) MIB for H3C/Huawei devices, configuring service and customer VLAN tag priorities and settings.
Start monitoring H3C Ethernet switch, metro/carrier edge (QinQ v2 double-tagging) 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.