[c-nsp] 802.1ad S-TAG - 88a8
Aaron
aaron1 at gvtc.com
Thu May 21 15:06:27 EDT 2015
Thanks Quinn, the following config seems to result in 8100 over 8100 (which I understand to be ctag over ctag in its truest sense). I’m looking to make the outer (top) tag be a true S-TAG, which should have ethertype of 88A8.
eng-lab-3600-2#sh ethernet service instance id 1 interface g0/1 detail | in Encap
Encapsulation: dot1q 2902 vlan protocol type 0x8100 second-dot1q 100 vlan protocol type 0x8100
eng-lab-3600-2#
eng-lab-3600-2#conf t
Enter configuration commands, one per line. End with CNTL/Z.
eng-lab-3600-2(config)#int g0/1
eng-lab-3600-2(config-if)#service instance 1 ethernet
eng-lab-3600-2(config-if-srv)# encapsulation dot1q ?
<1-4094> VLAN id
any For all VLANS [1-4094]
eng-lab-3600-2(config-if-srv)# encapsulation ?
default catch-all unconfigured encapsulation
dot1q IEEE 802.1Q Virtual LAN or S-VLAN
priority-tagged Priority tagged EFP
untagged Untagged encapsulation
eng-lab-3600-2(config-if-srv)# encapsulation do
eng-lab-3600-2(config-if-srv)# encapsulation dot1q 2902 ?
, comma
- hyphen
cos cos Vlan
etype payload ethertype after Vlan Field
second-dot1q inner 802.1Q Virtual LAN or C-VLAN
<cr>
eng-lab-3600-2(config-if-srv)# encapsulation dot1q 2902 e
eng-lab-3600-2(config-if-srv)# encapsulation dot1q 2902 etype ?
ipv4 IPv4
ipv6 IPv6
pppoe-all PPPoE ALL
pppoe-discovery PPPoE Discovery Stage
pppoe-session PPPoE Session Stage
eng-lab-3600-2(config-if-srv)# encapsulation dot1q 2902 etype ip
eng-lab-3600-2(config-if-srv)# encapsulation dot1q 2902 etype ipv?
ipv4 ipv6
eng-lab-3600-2(config-if-srv)# encapsulation dot1q 2902 etype ipv4 ?
, comma
<cr>
eng-lab-3600-2(config-if-srv)# encapsulation dot1q 2902 se
eng-lab-3600-2(config-if-srv)# encapsulation dot1q 2902 second-dot1q ?
<1-4094> VLAN id
any For all VLANS [1-4094]
eng-lab-3600-2(config-if-srv)# encapsulation dot1q 2902 second-dot1q 100 ?
, comma
- hyphen
cos cos Vlan
etype payload ethertype after Vlan Field
<cr>
eng-lab-3600-2(config-if-srv)#
From: quinn snyder [mailto:snyderq at gmail.com]
Sent: Thursday, May 21, 2015 12:58 PM
To: Aaron
Subject: Re: [c-nsp] 802.1ad S-TAG - 88a8
isn’t there an option — rather than ‘encap dot1q’ — that can be an ‘encap dot1ad’ or so in the config?
i don’t have access to my me’s at the moment — but i vaguely remember something of the sort present in there somewhere.
q.
--
quinn snyder
snyderq at gmail.com
On May 21, 2015, at 06:42, Aaron <aaron1 at gvtc.com> wrote:
Does anyone know how to make an ME3600 service instance (efp) tag frames
with 802.1ad s-tagging (88a8 ethertype) instead of the typical 802.1q C-tag
(8100) ?
I see the way I have this config'd it shows that both tags are 8100
ethertype which I think is technically known as c-tag (8100). So I guess
you would call this ctag-in-ctag
But how would I make the outer tag a TRUE provider tag (aka s-tag, aka 88a8
ethertype) and leave the inner (bottom customer tag) remain 8100?
eng-lab-3600-2#sh run in g0/1
interface GigabitEthernet0/1
switchport trunk allowed vlan none
switchport mode trunk
mtu 9202
service instance 1 ethernet
encapsulation dot1q 2902 second-dot1q 100
rewrite ingress tag pop 2 symmetric
l2protocol tunnel
xconnect 10.101.0.254 10000 encapsulation mpls
mtu 1500
!
eng-lab-3600-2#sh ethernet service instance id 1 interface g0/1 detail
Service Instance ID: 1
Service Instance Type: static
Associated Interface: GigabitEthernet0/1
Associated EVC:
L2protocol tunnel
CE-Vlans:
Encapsulation: dot1q 2902 vlan protocol type 0x8100 second-dot1q 100 vlan
protocol type 0x8100
Rewrite: ingress tag pop 2 symmetric
Interface Dot1q Tunnel Ethertype: 0x8100
State: Up
EFP Statistics:
Pkts In Bytes In Pkts Out Bytes Out
112109 16810234 105959 17741577
Aaron
_______________________________________________
cisco-nsp mailing list cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
More information about the cisco-nsp
mailing list