TN-SAS-SDP-MIB :: sdpBindIngressExtraVlanTagDroppedPackets

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › TN-SAS-SDP-MIB › sdpBindIngressExtraVlanTagDroppedPackets

sdpBindIngressExtraVlanTagDroppedPackets

Module: TN-SAS-SDP-MIB

OID (symbolic): TN-SAS-SDP-MIB::sdpBindIngressExtraVlanTagDroppedPackets

OID (numeric): 1.3.6.1.4.1.7483.7.2.2.2.12.5.1.1

Node type: OBJECT-TYPE

Type: Counter64

Access: read-only

Description: Counter to track of extra v-lan tag dropped packets

What is sdpBindIngressExtraVlanTagDroppedPackets?

This is a 64-bit running counter tallying how many ingress packets on this SDP bind were discarded for carrying an extra or unexpected VLAN tag. An admin diffs successive readings of this counter to quantify how often mistagged traffic is arriving on a service, which usually points to a misconfigured access device or an upstream tagging mismatch. For example, a counter that grows by several hundred per minute would indicate a persistent source of mistagged traffic hitting that bind.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.7483.7.2.2.2.12.5.1.1
snmpwalk -v2c -c public <target> TN-SAS-SDP-MIB::sdpBindIngressExtraVlanTagDroppedPackets

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.7483.7.2.2.2.12.5.1.1.1
snmpget -v2c -c public <target> TN-SAS-SDP-MIB::sdpBindIngressExtraVlanTagDroppedPackets.1

Start monitoring Nokia 7210 SR service access switch (SDP-binding VLAN-tag drop-counter status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TN-SAS-SDP-MIB::sdpBindIngressExtraVlanTagDroppedPackets OID value, configure state conditions and alerts, and monitor any Nokia 7210 SR service access switch (SDP-binding VLAN-tag drop-counter status) from a single console.

How to Use in IPNetwork Monitor

Select a Nokia 7210 SR service access switch (SDP-binding VLAN-tag drop-counter status) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type sdpBindIngressExtraVlanTagDroppedPackets into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. It reports the counter to track of extra v-lan tag dropped packets. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter64-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases between polls, since a rising count of errors, failures, or discards often points to a real underlying problem. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (11 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.7483tropicTROPIC-GLOBAL-REG
1.3.6.1.4.1.7483.7tnSASProductsTROPIC-GLOBAL-REG
1.3.6.1.4.1.7483.7.2tnServiceAccessSwitchesTROPIC-GLOBAL-REG
1.3.6.1.4.1.7483.7.2.2tnSASMIBTROPIC-GLOBAL-REG
1.3.6.1.4.1.7483.7.2.2.2tnSASObjsTROPIC-GLOBAL-REG
Numeric OIDNameModule
1.3.6.1.4.1.7483.7.2.2.2.12tnSASSdpObjsTN-SAS-SDP-MIB
1.3.6.1.4.1.7483.7.2.2.2.12.5sdpBindBaseStatsExtnTableTN-SAS-SDP-MIB
1.3.6.1.4.1.7483.7.2.2.2.12.5.1sdpBindBaseStatsExtnEntryTN-SAS-SDP-MIB
1.3.6.1.4.1.7483.7.2.2.2.12.5.1.1sdpBindIngressExtraVlanTagDroppedPacketsTN-SAS-SDP-MIB