[c-nsp] Unable to transmit tagged frames over q-in-q tunnel

Keegan Holley keegan.holley at sungard.com
Thu Oct 27 12:41:15 EDT 2011


Your diagram got mangled.  I think your PE facing interface has to be a
tunnel as well depending on the type of router you are connected to.  Are
you the provider or is the MPLS transport a managed service?  Many platforms
have a discard counter that may increment if it's dropping frames because of
the vlan tags.  That would help you at least figure out what device is
dropping the frames.  You should also be using 8100 tags (cisco default).


2011/10/27 Gökhan Gümüş <ggumus at gmail.com>

> Dear folks,
>
> I have an issue with one of our customer service.
>
>                                Gi0/5
> Gi0/27
> Gi5/13                                      Fa3/13
> Customer SW ---------------- Customer Edge Switch-A ----------------PE1
> ----------MPLS Core --------------PE 2--------------Customer Edge Switch-B
> --------------Customer SW
>
> I am using q-in-q tunneling to enable customer traffic. Before, customer
> port on Customer SW facing our edge switch was in ACCESS mode and it was
> working.
> Now they have decided to configure this interface as a TRUNK to transmit
> multiple VLANs over the trunk. But they can not.
> Currently ports are configured as trunk and customer can only transmit
> traffic when they do not tag frames ( native-vlan config )
>
> For note, i am not using " vlan dot1q tag native " command which is also
> double-tagging native vlans.
> MTU is fine and above 1504 bytes.
>
> Please see our configs on Customer Edge Switch below;
>
>
> *Customer Edge Switch A;*
>
> A#sh run interface Gigabit Ethernet0/5
> Building configuration...
>
> Current configuration : 337 bytes
> !
> interface GigabitEthernet0/5
>  switchport access vlan 1106
>  switchport mode dot1q-tunnel
>  switchport nonegotiate
>  load-interval 60
>  speed 100
>  duplex full
>  l2protocol-tunnel cdp
>  l2protocol-tunnel stp
>  l2protocol-tunnel vtp
>  no cdp enable
> end
>
> A#sh run interface GigabitEthernet0/27
> Building configuration...
>
> Current configuration : 251 bytes
> !
> interface GigabitEthernet0/27
>  switchport trunk encapsulation dot1q
>  switchport trunk allowed vlan 1,9,1101,1102,1106
>  switchport mode trunk
>  switchport nonegotiate
> end
>
>
> ---------------------------------------------------------------------------------
>
> *Customer Edge Switch B;*
>
> B#sh run interface fa3/13
> Building configuration...
>
> Current configuration : 366 bytes
> !
> interface FastEthernet3/13
>  mtu 2000
>  load-interval 60
>  switchport
>  switchport access vlan 1106
>  switchport mode dot1q-tunnel
>  switchport nonegotiate
>  l2protocol-tunnel cdp
>  l2protocol-tunnel stp
>  l2protocol-tunnel vtp
>  no cdp enable
>  spanning-tree bpdufilter enable
> end
>
> B#sh run interface gi5/13
> Building configuration...
>
> Current configuration : 298 bytes
> !
> interface GigabitEthernet5/13
>  mtu 2000
>  load-interval 30
>  speed nonegotiate
>  switchport
>  switchport trunk encapsulation dot1q
>  switchport trunk allowed vlan 1101,1102,1106
>  switchport mode trunk
>  no cdp enable
> end
>
>
> Is there anybody who had such issue before?
>
> Thanks and regards,
> Gokhan Gumus
> _______________________________________________
> 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