All MIBs › TPLINK-VLAN-QINQ-MIB
Organization: TPLINK
Last Updated: 2008-12-16
Category: VLAN Management
Description: Manages TP-Link switch QinQ 802.1ad double-tag VLAN configuration for provider network tunneling.
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 TPLINK-VLAN-QINQ-MIB?
TPLINK-VLAN-QINQ-MIB is a vendor-specific TP-Link MIB for managing 802.1ad QinQ (VLAN-in-VLAN, "VLAN-VPN") double-tagging on TP-Link switches, a Layer 2 tunneling technique that lets a service provider carry customer VLAN-tagged traffic across a shared public network using an outer provider tag. It exposes configuration data for global QinQ mode, TPID (tag protocol identifier), uplink port designation, per-port QinQ enable state, and VLAN tag mapping rules. This is primarily a configuration-oriented MIB rather than a hardware/environmental health MIB, though per-port enable status and uplink port state provide software/service-level status of the QinQ feature on each port. It builds on standard 802.1Q/802.1ad VLAN tagging concepts and typically depends on the switch's underlying interface/VLAN MIBs (e.g. Q-BRIDGE-MIB) for port and VLAN identity. Typical deployment is in service-provider or metro-Ethernet access networks using TP-Link switches to tunnel customer VLANs across a shared uplink. Engineers can download the TPLINK-VLAN-QINQ-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in TPLINK-VLAN-QINQ-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
- TP-Link managed switches (metro-Ethernet / service-provider access switches)
Monitoring Examples
An operator would check vpnConfigVpnMode and vpnConfigTpid to confirm QinQ is enabled and using the expected outer tag protocol ID, then inspect vpnConfigUplinkPortTable and vpnConfigPortEnableTable to verify which ports are designated uplinks and which have QinQ tagging active. Rows in vpnConfigVlanMappingTable (vpnConfigVlanMappingEntry) show the configured mapping between customer VLAN and mapped provider VLAN; an unexpected or missing vpnConfigVlanMappingMode entry would explain customer traffic failing to reach the provider network correctly. The tplinkQinqVlanMIBNotifications branch suggests the device can also raise traps on QinQ configuration changes.
What Can Be Monitored
- QinQ mode enabled/disabled
- outer VLAN TPID
- uplink port designation
- per-port QinQ enable status
- VLAN tag mapping table entries
Imported Objects
From RFC1213-MIB
| ifIndex |
From SNMPv2-SMI
| Counter32 | |
| Integer32 | |
| MODULE-IDENTITY | |
| OBJECT-IDENTITY | |
| OBJECT-TYPE |
From SNMPv2-TC
| DisplayString | |
| MacAddress |
From TPLINK-MIB
| tplinkMgmt | OBJECT-IDENTITY |
From TPLINK-TC-MIB
| TPRowStatus |
OIDs
RFC description
QinQ VLAN tagging configuration for TP-Link switches supporting double-tagged VPN networks.
Start monitoring TP-Link managed switches, metro-Ethernet/service-provider access (QinQ double-tag config 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.