TN-VLAN-MGMT-MIB :: tnVlanServiceTranslation

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › TN-VLAN-MGMT-MIB › tnVlanServiceTranslation

tnVlanServiceTranslation

Module: TN-VLAN-MGMT-MIB

OID (symbolic): TN-VLAN-MGMT-MIB::tnVlanServiceTranslation

OID (numeric): 1.3.6.1.4.1.868.2.5.4.1.5.4

Node type: OBJECT-TYPE

Type: TnVlanServiceTranslationType

Access: read-write

Description: This determines the service or flow type between the two terminations.
The translation type as the flow passes the termination points from Customer edge to provider edge
are detailed below :


 <----- Provider Side ----->                                <----- Customer Side ----->
                                        Device
                            +------------------------------+
                ---->       |  P |                    |  P |     ---->
                ---->       |  o |                    |  o |     ---->
                <----       |  r |                    |  r |     <----
                <----       |  t |                    |  t |     <----
                            |(PE)|                    |(CE)|
                            +------------------------------+


 noTranslation(1) :-
 The ingress flow might contain any kind of frames, untagged or single or double tagged.
 The egress flow will be exactly the same, no translation is done.

untaggedUntagged(2) :-
The traffic should be untagged, all tagged frames will be discarded.
The traffic that egress the device contain the untagged flow without any modification.

untaggedSingleTagged(3) :-
At the CE the traffic should be untagged.
At the PE the traffic will contain a single tag with the VID specified in tnVlanServiceVIDForTag.

singleTaggedSingleTagged(4) :-
The traffic should be single tagged on ingress and on egress with no translation.

singleTaggedTranslation(5) :-
The traffic should be single tagged on ingress and on egress.
The only changes from the singleTaggedSingleTagged(4), there is a translation.
The Vlan Id that came on ingress is translated to a different Vlan Id on egress.

singleTaggedDoubleTagged(6) :-
At the CE the traffic should be single tagged.
At the PE the traffic will contain an extra tag with the VID specified in tnVlanServiceVIDForTag.

doubleTaggedDoubleTagged(7) :-
The traffic should be double tagged on ingress and on egress with no translation.

doubleTaggedTranslation(8) :-
The traffic should be double tagged on ingress and on egress.
The only changes from the doubleTaggedDoubleTagged(7), there is a translation.
The Vlan Id in outer tag that came on CE is translated to a different Vlan Id on PE.
The inner tag remains intact.

addProviderTag(9) :-
This option adds an extra tag on the PE interface, no matter what kind of traffic at CE.
This strips the outer tag for traffic from PE interface egressing the CE interface.

What is tnVlanServiceTranslation?

Selects the VLAN tag translation applied as traffic crosses this 2-port service device between customer and provider edges, ranging from noTranslation(1), which passes frames through unchanged, to modes like singleTaggedTranslation(5), which swap the ingress VLAN ID for a different one on egress, to addProviderTag(9), which stamps an extra provider tag onto whatever arrives. An admin picks the mode matching how the service needs to map customer VLANs onto the provider network.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.868.2.5.4.1.5.4
snmpwalk -v2c -c public <target> TN-VLAN-MGMT-MIB::tnVlanServiceTranslation

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.868.2.5.4.1.5.4.1
snmpget -v2c -c public <target> TN-VLAN-MGMT-MIB::tnVlanServiceTranslation.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.868.2.5.4.1.5.4.1 s <value>

Start monitoring Transition Networks, Inc. equipment (VLAN/QoS management config status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TN-VLAN-MGMT-MIB::tnVlanServiceTranslation OID value, configure state conditions and alerts, and monitor any Transition Networks, Inc. equipment (VLAN/QoS management config status) from a single console.

OID Breakdown

Upper-level ancestors (9 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.868transitionTRANSITION-SMI
1.3.6.1.4.1.868.2productsTRANSITION-SMI
1.3.6.1.4.1.868.2.5tnProductsTRANSITION-SMI
Numeric OIDNameModule
1.3.6.1.4.1.868.2.5.4tnVlanQoSMgmtMIBTN-VLAN-MGMT-MIB
1.3.6.1.4.1.868.2.5.4.1tnVlanQoSMgmtObjectsTN-VLAN-MGMT-MIB
1.3.6.1.4.1.868.2.5.4.1.5tnVlanServiceMgmtTN-VLAN-MGMT-MIB
1.3.6.1.4.1.868.2.5.4.1.5.4tnVlanServiceTranslationTN-VLAN-MGMT-MIB