Whats the meaning of `802.1Q tunnel customer VLAN mapping` and `802.1Q tunnel provider VLAN mapping`?
Whats the meaning of 802.1Q tunnel customer VLAN mapping
and 802.1Q tunnel provider VLAN mapping
?
Shows 802.1Q (QinQ) tunnel information.
802.1Q tunneling allows layer 2 VPN connectivity between sites by encapsulating 802.1Q trunk traffic inside another 802.1Q trunk.
Command Syntax
Command Modes Syntax Description
show dot1q-tunnel [interface {<interfaceName>| {port-channel <portChannel>}}]
show dot1q-tunnel {customer | provider} vlan mapping [interface {<interfaceName>| {port-channel <portChannel>}}]
show dot1q-tunnel encapsulation [interface {<interfaceName>| {port- channel <portChannel>}}]
Command Default Examples
#show dot1q-tunnel interface xe1
#show dot1q-tunnel interface port-channel 3800 #show dot1q-tunnel customer vlan mapping
118
Privileged Mode
interface
interfaceName
port-channel
portChannel
#
Show 802.1Q tunnel configuration on the specified interface.
Interface to show information for.
Show 802.1Q tunnel configuration on the specified port channel.
Port channel to show 802.1Q tunnel configuration information for.
encapsulation
vlan mapping
customer
provider
interfaceName
This command has no default settings.
ONP – Layer 2 Commands
Displays 802.1Q tunnel stacked VLAN configuration.
Displays 802.1Q tunnel VLAN mapping information.
Displays 802.1Q tunnel customer VLAN mapping information.
Displays 802.1Q tunnel provider VLAN mapping information.
Name of an interface port. For example, xe1.
I do not understand the four lines:
Displays 802.1Q tunnel stacked VLAN configuration.
Displays 802.1Q tunnel VLAN mapping information.
Displays 802.1Q tunnel customer VLAN mapping information.
Displays 802.1Q tunnel provider VLAN mapping information.
sdn ieee-802.1x ovs
add a comment |
Whats the meaning of 802.1Q tunnel customer VLAN mapping
and 802.1Q tunnel provider VLAN mapping
?
Shows 802.1Q (QinQ) tunnel information.
802.1Q tunneling allows layer 2 VPN connectivity between sites by encapsulating 802.1Q trunk traffic inside another 802.1Q trunk.
Command Syntax
Command Modes Syntax Description
show dot1q-tunnel [interface {<interfaceName>| {port-channel <portChannel>}}]
show dot1q-tunnel {customer | provider} vlan mapping [interface {<interfaceName>| {port-channel <portChannel>}}]
show dot1q-tunnel encapsulation [interface {<interfaceName>| {port- channel <portChannel>}}]
Command Default Examples
#show dot1q-tunnel interface xe1
#show dot1q-tunnel interface port-channel 3800 #show dot1q-tunnel customer vlan mapping
118
Privileged Mode
interface
interfaceName
port-channel
portChannel
#
Show 802.1Q tunnel configuration on the specified interface.
Interface to show information for.
Show 802.1Q tunnel configuration on the specified port channel.
Port channel to show 802.1Q tunnel configuration information for.
encapsulation
vlan mapping
customer
provider
interfaceName
This command has no default settings.
ONP – Layer 2 Commands
Displays 802.1Q tunnel stacked VLAN configuration.
Displays 802.1Q tunnel VLAN mapping information.
Displays 802.1Q tunnel customer VLAN mapping information.
Displays 802.1Q tunnel provider VLAN mapping information.
Name of an interface port. For example, xe1.
I do not understand the four lines:
Displays 802.1Q tunnel stacked VLAN configuration.
Displays 802.1Q tunnel VLAN mapping information.
Displays 802.1Q tunnel customer VLAN mapping information.
Displays 802.1Q tunnel provider VLAN mapping information.
sdn ieee-802.1x ovs
add a comment |
Whats the meaning of 802.1Q tunnel customer VLAN mapping
and 802.1Q tunnel provider VLAN mapping
?
Shows 802.1Q (QinQ) tunnel information.
802.1Q tunneling allows layer 2 VPN connectivity between sites by encapsulating 802.1Q trunk traffic inside another 802.1Q trunk.
Command Syntax
Command Modes Syntax Description
show dot1q-tunnel [interface {<interfaceName>| {port-channel <portChannel>}}]
show dot1q-tunnel {customer | provider} vlan mapping [interface {<interfaceName>| {port-channel <portChannel>}}]
show dot1q-tunnel encapsulation [interface {<interfaceName>| {port- channel <portChannel>}}]
Command Default Examples
#show dot1q-tunnel interface xe1
#show dot1q-tunnel interface port-channel 3800 #show dot1q-tunnel customer vlan mapping
118
Privileged Mode
interface
interfaceName
port-channel
portChannel
#
Show 802.1Q tunnel configuration on the specified interface.
Interface to show information for.
Show 802.1Q tunnel configuration on the specified port channel.
Port channel to show 802.1Q tunnel configuration information for.
encapsulation
vlan mapping
customer
provider
interfaceName
This command has no default settings.
ONP – Layer 2 Commands
Displays 802.1Q tunnel stacked VLAN configuration.
Displays 802.1Q tunnel VLAN mapping information.
Displays 802.1Q tunnel customer VLAN mapping information.
Displays 802.1Q tunnel provider VLAN mapping information.
Name of an interface port. For example, xe1.
I do not understand the four lines:
Displays 802.1Q tunnel stacked VLAN configuration.
Displays 802.1Q tunnel VLAN mapping information.
Displays 802.1Q tunnel customer VLAN mapping information.
Displays 802.1Q tunnel provider VLAN mapping information.
sdn ieee-802.1x ovs
Whats the meaning of 802.1Q tunnel customer VLAN mapping
and 802.1Q tunnel provider VLAN mapping
?
Shows 802.1Q (QinQ) tunnel information.
802.1Q tunneling allows layer 2 VPN connectivity between sites by encapsulating 802.1Q trunk traffic inside another 802.1Q trunk.
Command Syntax
Command Modes Syntax Description
show dot1q-tunnel [interface {<interfaceName>| {port-channel <portChannel>}}]
show dot1q-tunnel {customer | provider} vlan mapping [interface {<interfaceName>| {port-channel <portChannel>}}]
show dot1q-tunnel encapsulation [interface {<interfaceName>| {port- channel <portChannel>}}]
Command Default Examples
#show dot1q-tunnel interface xe1
#show dot1q-tunnel interface port-channel 3800 #show dot1q-tunnel customer vlan mapping
118
Privileged Mode
interface
interfaceName
port-channel
portChannel
#
Show 802.1Q tunnel configuration on the specified interface.
Interface to show information for.
Show 802.1Q tunnel configuration on the specified port channel.
Port channel to show 802.1Q tunnel configuration information for.
encapsulation
vlan mapping
customer
provider
interfaceName
This command has no default settings.
ONP – Layer 2 Commands
Displays 802.1Q tunnel stacked VLAN configuration.
Displays 802.1Q tunnel VLAN mapping information.
Displays 802.1Q tunnel customer VLAN mapping information.
Displays 802.1Q tunnel provider VLAN mapping information.
Name of an interface port. For example, xe1.
I do not understand the four lines:
Displays 802.1Q tunnel stacked VLAN configuration.
Displays 802.1Q tunnel VLAN mapping information.
Displays 802.1Q tunnel customer VLAN mapping information.
Displays 802.1Q tunnel provider VLAN mapping information.
sdn ieee-802.1x ovs
sdn ieee-802.1x ovs
asked Jan 5 at 19:47
244boy244boy
3138
3138
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Using QinQ (802.1ad) double tagging, you can use an inner (customer) VLAN ID and an outer (provider) VLAN ID.
The point is that a provider can provide full, 802.1Q-tagged services to each client and still use the outer tag for their own VLAN infrastructure.
Double tags can be used in plain frames or inside a (VPN) tunnel.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "496"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fnetworkengineering.stackexchange.com%2fquestions%2f55892%2fwhats-the-meaning-of-802-1q-tunnel-customer-vlan-mapping-and-802-1q-tunnel-pr%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Using QinQ (802.1ad) double tagging, you can use an inner (customer) VLAN ID and an outer (provider) VLAN ID.
The point is that a provider can provide full, 802.1Q-tagged services to each client and still use the outer tag for their own VLAN infrastructure.
Double tags can be used in plain frames or inside a (VPN) tunnel.
add a comment |
Using QinQ (802.1ad) double tagging, you can use an inner (customer) VLAN ID and an outer (provider) VLAN ID.
The point is that a provider can provide full, 802.1Q-tagged services to each client and still use the outer tag for their own VLAN infrastructure.
Double tags can be used in plain frames or inside a (VPN) tunnel.
add a comment |
Using QinQ (802.1ad) double tagging, you can use an inner (customer) VLAN ID and an outer (provider) VLAN ID.
The point is that a provider can provide full, 802.1Q-tagged services to each client and still use the outer tag for their own VLAN infrastructure.
Double tags can be used in plain frames or inside a (VPN) tunnel.
Using QinQ (802.1ad) double tagging, you can use an inner (customer) VLAN ID and an outer (provider) VLAN ID.
The point is that a provider can provide full, 802.1Q-tagged services to each client and still use the outer tag for their own VLAN infrastructure.
Double tags can be used in plain frames or inside a (VPN) tunnel.
answered Jan 5 at 21:07
Zac67Zac67
27.6k21456
27.6k21456
add a comment |
add a comment |
Thanks for contributing an answer to Network Engineering Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fnetworkengineering.stackexchange.com%2fquestions%2f55892%2fwhats-the-meaning-of-802-1q-tunnel-customer-vlan-mapping-and-802-1q-tunnel-pr%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown