Re: [c-nsp] QinQ termination on a Catalyst 6800

On 19/02/2019 16:01, James Bensley wrote: > I looked at 6880 a few years ago, > I'm pretty sure this was one of the reasons we doing for it it, too > similar to the 6500 (including this limitation). I wonder why it's in the docs/supported in the IOS version... Isn't there a newer gen of

Re: [c-nsp] QinQ termination on a Catalyst 6800

--- Begin Message --- For completeness sake, if there are a low number of S-VLANs for your use case then an external loopback cable might suffice. -Steve On Tue, Feb 19, 2019 at 9:02 AM James Bensley wrote: > On Mon, 18 Feb 2019 at 18:14, wrote: > > > > > Cat6K and 6880 support QinQ. > > > We

Re: [c-nsp] QinQ termination on a Catalyst 6800

If there is a way to terminate it directly, let me know, because I'm pretty sure we still have a cable looping back into the same 6807 to terminate an inner tag... yikes. -- Hunter Fuller Router Jockey VBH Annex B-5 +1 256 824 5331 Office of Information Technology The University of Alabama in

Re: [c-nsp] QinQ termination on a Catalyst 6800

On Mon, 18 Feb 2019 at 18:14, wrote: > > > Cat6K and 6880 support QinQ. > > We use it to connect some L3 vlans between our DC. > > I’m not at my desk, but from memory, .. > > 1) on the access port facing the ‘client’ …. > > Switchport mode dot1q-tunnel > > switchport access vlan xxx.Where

Re: [c-nsp] QinQ termination on a Catalyst 6800

he Fillot > Skickat: den 19 februari 2019 09:05 > Till: Peter Rathlev ; Tom Hill > Kopia: cisco-nsp@puck.nether.net > Ämne: Re: [c-nsp] QinQ termination on a Catalyst 6800 > > > On 18/02/2019 23:11, Peter Rathlev wrote: > > On Mon, 2019-02-18 at 20:14 +, To

Re: [c-nsp] QinQ termination on a Catalyst 6800

of this limitation though? //Gustav -Ursprungligt meddelande- Från: cisco-nsp För Christophe Fillot Skickat: den 19 februari 2019 09:05 Till: Peter Rathlev ; Tom Hill Kopia: cisco-nsp@puck.nether.net Ämne: Re: [c-nsp] QinQ termination on a Catalyst 6800 On 18/02/2019 23:11, Peter Rathlev

Re: [c-nsp] QinQ termination on a Catalyst 6800

On 18/02/2019 23:11, Peter Rathlev wrote: On Mon, 2019-02-18 at 20:14 +, Tom Hill wrote: On 14/02/2019 09:01, Christophe Fillot wrote: Anyone knows if this platform supports QinQ termination ? The "encapsulation dot1q X second-dot1q Y" command is not present, but maybe there is another

Re: [c-nsp] QinQ termination on a Catalyst 6800

On Mon, 2019-02-18 at 20:14 +, Tom Hill wrote: > On 14/02/2019 09:01, Christophe Fillot wrote: > > Anyone knows if this platform supports QinQ termination ? > > > > The "encapsulation dot1q X second-dot1q Y" command is not present, > > but > > maybe there is another way to do it ? > > EVCs?

Re: [c-nsp] QinQ termination on a Catalyst 6800

On 14/02/2019 09:01, Christophe Fillot wrote: > Anyone knows if this platform supports QinQ termination ? > > The "encapsulation dot1q X second-dot1q Y" command is not present, but > maybe there is another way to do it ? EVCs?

Re: [c-nsp] QinQ termination on a Catalyst 6800

> Cat6K and 6880 support QinQ. > We use it to connect some L3 vlans between our DC. > I’m not at my desk, but from memory, .. > 1) on the access port facing the ‘client’ …. > Switchport mode dot1q-tunnel > switchport access vlan xxx.Where xxx is the transport/service provider > side vlan

Re: [c-nsp] QinQ termination on a Catalyst 6800

to this client. 2) add the above ‘xxx’ transport vlan to any dot1q trunks used between client sites. On Feb 18, 2019, at 12:00 PM, cisco-nsp-requ...@puck.nether.net<mailto:cisco-nsp-requ...@puck.nether.net> wrote: Re: [c-nsp] QinQ termination on a Catalys

Re: [c-nsp] QinQ termination on a Catalyst 6800

I am almost certain it doesn't support it. The Cat6500 definitely did not (even though the 7600 did), so I think the 6800 inherited this. -- Hunter Fuller Router Jockey VBH Annex B-5 +1 256 824 5331 Office of Information Technology The University of Alabama in Huntsville Network Engineering

[c-nsp] QinQ termination on a Catalyst 6800

Hello, Anyone knows if this platform supports QinQ termination ? The "encapsulation dot1q X second-dot1q Y" command is not present, but maybe there is another way to do it ? Thanks in advance, Christophe ___ cisco-nsp mailing list

Re: [c-nsp] QinQ on NS-OX/Nexus

Yeah TAC have confimred it is not possible. The only way is to use a looped cable between two ports but with a carrier NNI and many end sites comming in to the DC each over QinQ it would mean a looped cable (and thus 2 ports used) per end site (per S-VLAN) so it's a no go basically. I was hoping

Re: [c-nsp] QinQ on NS-OX/Nexus

I've searched for this before and I was not able to find the functionality, even on the 5ks. The reason being in my belief is the Nexus platform is designed for datacenter switching. QinQ is more of a metro/carrier type functionality. With the QinQ SVI your egress interface would need to be

Re: [c-nsp] QinQ on NS-OX/Nexus

On 09/06/16 09:50, James Bensley wrote: You say it's not in 6.2 on your M1 cards, the firmware can be upgraded on the live box if required, however do you know if it is actually supported on these line cards in a later version? I'd like to know if QinQ is even possible on this hardware, if not

Re: [c-nsp] QinQ on NS-OX/Nexus

On 9 June 2016 at 09:11, Phil Mayers wrote: > Which Nexus? They very wildly in their capabilities. > > It's entirely possible you can't do what you want on that platform. I'm not > sure Q-in-Q termination is supported. It requires more of the equipment than > Q-in-Q

Re: [c-nsp] QinQ on NS-OX/Nexus

On 09/06/16 08:41, James Bensley wrote: Hi All, I have a typical ethernet NNI from a carrier with end sites being handed over to me as QinQ tagged frames, the S-VLAN is the end-site seperator and the C-VLANs are the customer VLANs. I'm searching the Cisco documentation but I can't find any

[c-nsp] QinQ on NS-OX/Nexus

Hi All, I have a typical ethernet NNI from a carrier with end sites being handed over to me as QinQ tagged frames, the S-VLAN is the end-site seperator and the C-VLANs are the customer VLANs. I'm searching the Cisco documentation but I can't find any examples of how to terminate a QinQ SVI on a

Re: [c-nsp] QinQ layer 3 port channel

Standard ether channel between the A client and A core/pe switch. But just a single link at the B end. L3 connection between A and B clients over qinq. I know end-end ether channel works. It's this mismatch that is confusing me. Sent from my iPhone > On May 2, 2016, at 12:09 AM,

Re: [c-nsp] QinQ layer 3 port channel

So you want to run some sort of link aggregation on top of a standard dot1q frame type? On May 1, 2016 18:01, "Wes Smith" wrote: > Hi > I have two sites connected by l2 vlan trunk. > On the A end, the A-client switch has multiple gig ports connecting to the > "A" core/pe. > >

[c-nsp] QinQ layer 3 port channel

Hi I have two sites connected by l2 vlan trunk. On the A end, the A-client switch has multiple gig ports connecting to the "A" core/pe. On the B end, the "B-client" switch connects by a single 10g to the "B" core. All equipment is Cisco 6800 or 6509 sup720/Sup2t. The question is how to

Re: [c-nsp] QinQ 4500X -> ME3600 and access(pop) multiple inner vlans

s tag pop 1 symmetric xconnect 3.4.5.6 275 encapsulation mpls pw-class L2VPN xconnect I hope this helps. -Original Message- From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of CiscoNSP List Sent: Tuesday, February 02, 2016 3:28 AM To: cisco-nsp@puck.nether.n

Re: [c-nsp] QinQ 4500X -> ME3600 and access(pop) multiple inner vlans

On 3 February 2016 at 06:05, CiscoNSP List wrote: Thanks Eric, > > We have no visibility into the remote end, but I have setup the following > on one of our ME's (Test service, that has supposedly been configured by > carrier, and remote end) > > Vlans are: > > 940

Re: [c-nsp] QinQ 4500X -> ME3600 and access(pop) multiple inner vlans

ess tag pop 1 symmetric xconnect 3.4.5.6 275 encapsulation mpls pw-class L2VPN xconnect I hope this helps. -Original Message- From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of CiscoNSP List Sent: Tuesday, February 02, 2016 3:28 AM To: cisco-nsp@puck.nether.net

Re: [c-nsp] QinQ 4500X -> ME3600 and access(pop) multiple inner vlans

> Sent: Thursday, 4 February 2016 6:52 AM To: Erik Sundberg; cisco-nsp@puck.nether.net Subject: Re: [c-nsp] QinQ 4500X -> ME3600 and access(pop) multiple inner vlans Thanks for confirming Eric (Re the 4500X) - I have another question...4500X will receive frame from carrier with outer tag

Re: [c-nsp] QinQ 4500X -> ME3600 and access(pop) multiple inner vlans

for all who assisted. From: cisco-nsp <cisco-nsp-boun...@puck.nether.net> on behalf of CiscoNSP List <cisconsp_l...@hotmail.com> Sent: Thursday, 4 February 2016 4:12 PM To: Erik Sundberg; cisco-nsp@puck.nether.net Subject: Re: [c-nsp] QinQ 4500X -> ME3600 and acces

Re: [c-nsp] QinQ 4500X -> ME3600 and access(pop) multiple inner vlans

ip address 192.168.0.2 255.255.255.0 Does this help??? -Original Message- From: CiscoNSP List [mailto:cisconsp_l...@hotmail.com] Sent: Wednesday, February 03, 2016 4:47 PM To: Erik Sundberg <esundb...@nitelusa.com>; cisco-nsp@puck.nether.net Subject: Re: [c-nsp] QinQ 4500X -> ME

Re: [c-nsp] QinQ 4500X -> ME3600 and access(pop) multiple inner vlans

PM To: CiscoNSP List; cisco-nsp@puck.nether.net Subject: RE: [c-nsp] QinQ 4500X -> ME3600 and access(pop) multiple inner vlans Rememer you removed\popped off both vlan tags of 800 and 20 on the interface, then put the untagged frame in bridge group 820. The bridge group could have b

Re: [c-nsp] QinQ 4500X -> ME3600 and access(pop) multiple inner vlans

service instance 117 ethernet encapsulation dot1q 117 rewrite ingress tag pop 1 symmetric xconnect 3.4.5.6 275 encapsulation mpls pw-class L2VPN xconnect I hope this helps. -Original Message- From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of CiscoNSP List Sent:

Re: [c-nsp] QinQ 4500X -> ME3600 and access(pop) multiple inner vlans

I hope this helps. -Original Message- From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of CiscoNSP List Sent: Tuesday, February 02, 2016 3:28 AM To: cisco-nsp@puck.nether.net Subject: [c-nsp] QinQ 4500X -> ME3600 and access(pop) multiple inner vlans Hi Eve

[c-nsp] QinQ 4500X -> ME3600 and access(pop) multiple inner vlans

Hi Everyone, We have an AGG port(Standard trunk port) to a carrier on a 4500X - Port has multiple customer vlans for p-t-p eth services. A service they have released will allow us to connect to azure/office 365 via QinQ(Carrier doing QinQ, not us) - i.e. We agree to an outer vlan tag with the

Re: [c-nsp] QinQ 4500X -> ME3600 and access(pop) multiple inner vlans

symmetric xconnect 3.4.5.6 275 encapsulation mpls pw-class L2VPN xconnect I hope this helps. -Original Message- From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of CiscoNSP List Sent: Tuesday, February 02, 2016 3:28 AM To: cisco-nsp@puck.nether.net Subject: [c-nsp

Re: [c-nsp] QinQ 4500X -> ME3600 and access(pop) multiple inner vlans

cisco-nsp@puck.nether.net Subject: [c-nsp] QinQ 4500X -> ME3600 and access(pop) multiple inner vlans Hi Everyone, We have an AGG port(Standard trunk port) to a carrier on a 4500X - Port has multiple customer vlans for p-t-p eth services. A service they have released will allow us to connect to azur

Re: [c-nsp] QinQ 4500X -> ME3600 and access(pop) multiple inner vlans

Message- From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of CiscoNSP List Sent: Tuesday, February 02, 2016 3:28 AM To: cisco-nsp@puck.nether.net Subject: [c-nsp] QinQ 4500X -> ME3600 and access(pop) multiple inner vlans Hi Everyone, We have an AGG port(Standard tru

Re: [c-nsp] QinQ 4500X -> ME3600 and access(pop) multiple inner vlans

nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of CiscoNSP List Sent: Tuesday, February 02, 2016 3:28 AM To: cisco-nsp@puck.nether.net Subject: [c-nsp] QinQ 4500X -> ME3600 and access(pop) multiple inner vlans Hi Everyone, We have an AGG port(Standard trunk port) to a carrier

Re: [c-nsp] QinQ and Bridging

. -Original Message- From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Garry Sent: 11 August 2015 05:01 To: cisco-nsp@puck.nether.net Subject: [c-nsp] QinQ and Bridging Hi, on a multi-site installation, I've got some additional requirements to implement

[c-nsp] QinQ and Bridging

Hi, on a multi-site installation, I've got some additional requirements to implement. Currently, two site (CPE) have a tagged ethernet service to a central site (PE). Now, apart from the L3 traffic, I need to bridge an additional VLAN from site 2 to site 1 in order to provide a guest WLAN which

[c-nsp] QinQ

Hi list I am new to QinQ. Any idea about QinQ basic configuration for testing CDP, Spanning, MTU etc which r connected to different switches.   Ami ___ cisco-nsp mailing list cisco-nsp@puck.nether.net

Re: [c-nsp] QinQ question

CiscoNSP_list [mailto:cisconsp_l...@hotmail.com] Sent: 20 November 2012 05:59 To: Iftikhar Mehar; cisco-nsp@puck.nether.net Subject: RE: [c-nsp] QinQ question That's right, using QinQ the provider will tag all frames (customer's various VLAN ID frames) using the same VLAN ID at all edges

Re: [c-nsp] QinQ question

? Subject: RE: [c-nsp] QinQ question Date: Tue, 20 Nov 2012 11:52:13 + From: iftikhar.me...@redstone.com To: cisconsp_l...@hotmail.com; cisco-nsp@puck.nether.net Hi, Service Provider port will be QinQ and your port facing provider’s QinQ port will always remain as trunk port. Same would apply

Re: [c-nsp] QinQ question

That's right, using QinQ the provider will tag all frames (customer's various VLAN ID frames) using the same VLAN ID at all edges. Thanks Iftikhar - The provider also offers a service where we do the QinQ(we control all client(tails) vlans)would we configure the Agg port connecting to

[c-nsp] QinQ question

Hi, We are provided a QinQ service from a carrier - Each customer tail is a vlan chosen by us(we inform the carrier of the vlan), which we place into L3 dot1q Int, and then trunk to the Carrier Agg(carrier connecting port is QinQ.) Would the carrier have a single outer tag configured for all

Re: [c-nsp] QinQ...inQ? question

: [c-nsp] QinQ...inQ? question To: cisconsp_l...@hotmail.com; cisco-nsp@puck.nether.net Hi, 802.1ad supports an arbitrary number of tags in the header (not limited to 2), so in theory it should work. There is obviously MTU considerations to be had (each extra VLAN tag adds another 4 bytes). What I

Re: [c-nsp] QinQ...inQ? question

] On Behalf Of CiscoNSP_list CiscoNSP_list Sent: August-17-12 2:03 AM To: td_mi...@yahoo.com; cisco-nsp@puck.nether.net Subject: Re: [c-nsp] QinQ...inQ? question Thanks Tony - So from a config perspective, can you please provide an example? i.e. From our existing (config) trunk port to carrier

Re: [c-nsp] QinQ...inQ? question

: [c-nsp] QinQ...inQ? question Only the port that does the actual double-tagging will need to be configured. From a 3750 I just set up for a customer: system mtu 1998 system mtu jumbo 9000 ! interface FastEthernet1/0/1 description TAGGED UPLINK switchport trunk encapsulation dot1q switchport

[c-nsp] QinQ...inQ? question

Hi Guys, We typically get QinQ links from our upstreams for p-t-p links between our POPs - Upstream carrier does the QinQ and we simply configure a trunk port to them and tag whatever vlans we need. (i.e. dont need to engage upstream for the vlans we want to use) We have a new POP, with our

Re: [c-nsp] QinQ...inQ? question

. From: CiscoNSP_list CiscoNSP_list cisconsp_l...@hotmail.com To: cisco-nsp@puck.nether.net cisco-nsp@puck.nether.net Sent: Friday, 17 August 2012 1:09 PM Subject: [c-nsp] QinQ...inQ? question Hi Guys, We typically get QinQ links from our upstreams for p-t-p links between our POPs

[c-nsp] QinQ Cisco 3750 ?

Hi I am search a solution for this project: Cisco 7301 connected to a Cisco 3750 A by a Fiber Gig port. Port is in trunk C7301 == C3750 port gig 0/24 The cisco 3750 A is connecter in trunk to a carrier by the Gig 0/23. The carrier supply 4 ports: 1 Central Port connected to C3750 A

Re: [c-nsp] QinQ Cisco 3750 ?

Hi Oliver, I think what you are wanting to do is called selective QinQ. For this you are looking at hardware such as ME3400 (http://www.cisco.com/en/US/docs/switches/metro/me3400e/software/release/12.2_50_se/configuration/guide/swtunnel.html#wp1059629) For port A you would end up with

[c-nsp] QinQ Question

Hi, I am trying to configure a QinQ link between two building. Building1 -- ServiceProvider -- Building2 ServiceProvider won't do QinQ in their equipment. In Building1 and Building2 there is only one 3560 switch. I did some test and it's working with a loop between gig0/23 and gig0/24 but i am

Re: [c-nsp] QinQ config sample on Cisco 7600/6500

Hi To add up with complete configurations: define a transport vlan: vlan 1285 name qinq-transport configure QinQ port. Increase mtu (7600 does not inherit system mtu when configuring qinq port) If any layer 2 transport required, configure this. interface GigabitEthernet4/2 description QinQ

Re: [c-nsp] QinQ config sample on Cisco 7600/6500

Hi, nobody an idea about this ? Cannot be i am the first one trying to run/built such setup or migrating from a platform that can do it. ;) kind regards Rolf Hello, I am quite new to Cisco and look for some configuration help. We used Foundry last 5 years and now started to add/integrate

Re: [c-nsp] QinQ config sample on Cisco 7600/6500

Hello, that is why I ask if there is an alternative for this card. ;) But the other questions stay the same as I could use the WS-X6724-SFP + copper SFP. The article describes what I found (i.e. the switchport mode dot1q-tunnel command) but not how to configure the vlan-id that will be used on

Re: [c-nsp] QinQ config sample on Cisco 7600/6500

On Thu, 2011-08-25 at 23:37 +0200, Rolf Hanßen wrote: nobody an idea about this ? Cannot be i am the first one trying to run/built such setup or migrating from a platform that can do it. ;) Okay then, I'll bite. :-) On Wed, 2011-08-24 at 18:46 +0200, Rolf Hanßen wrote: All I can find is

Re: [c-nsp] QinQ config sample on Cisco 7600/6500

Rolf wrote (in short): switchport mode dot1q-tunnel When trying to set the above commands I get that error: Gi4/48 doesn't support 802.1q tunneling. My linecard is a WS-X6548-GE-TX, does that mean I cannot use QinQ here or is there another way ? Same config on a WS-X6724-SFP is accepted.

[c-nsp] QinQ config sample on Cisco 7600/6500

Hello, I am quite new to Cisco and look for some configuration help. We used Foundry last 5 years and now started to add/integrate 7600/6500 boxes to the existing network. What I am searching for is a Cisco/IOS version of Foundry style hardcoded QinQ transport vlan like: vlan 123 tagged e 1/1

Re: [c-nsp] QinQ on 3550 not working?

On Thu, Jan 20, 2011 at 8:00 PM, Tony td_mi...@yahoo.com wrote: ] When the Customer site switch is a 3560, I can ping 172.30.1.1 and ping vrf network2 172.40.1.1 without problem. When the Customer site switch is a 3550, I can ping 172.30.1.1 fine, but trying to ping vrf network2 172.40.1.1

Re: [c-nsp] QinQ on 3550 not working?

How about the System MTU? Should be something like this: system mtu 1504 Andras 2011/1/22 Simon Lockhart si...@slimey.org: On Fri Jan 21, 2011 at 11:51:26PM +0100, Tth Andrs wrote: Did you enable the extended routing SDM template on the 3550 switch? Note that while on the 3560 it's only

Re: [c-nsp] QinQ on 3550 not working?

Hi Simon, Did you enable the extended routing SDM template on the 3550 switch? Note that while on the 3560 it's only called routing, the 3550 has an extended routing version, which has to be enabled for VRF to work. Best regards, Andras On Thu, Jan 20, 2011 at 12:13 PM, Simon Lockhart

Re: [c-nsp] QinQ on 3550 not working?

On Fri Jan 21, 2011 at 11:51:26PM +0100, Tth Andrs wrote: Did you enable the extended routing SDM template on the 3550 switch? Note that while on the 3560 it's only called routing, the 3550 has an extended routing version, which has to be enabled for VRF to work. Yes - I did that (as the

[c-nsp] QinQ on 3550 not working?

All, I've got a requirement for one of our customers to run two seperate networks over the same ethernet based WAN. The WAN is provided by the carrier as single VLAN per site, dot1q tagged at each end (both the customer site and our central PoP). The customer sites are all live currently with a

Re: [c-nsp] QinQ on 3550 not working?

Hi Simon, --- On Thu, 20/1/11, Simon Lockhart si...@slimey.org wrote: ---snip-- When the Customer site switch is a 3560, I can ping 172.30.1.1 and ping vrf network2 172.40.1.1 without problem. When the Customer site switch is a 3550, I can ping 172.30.1.1 fine, but trying to ping vrf

[c-nsp] QinQ Layer2 QoS - 3550?

Hi Guys, We have a number of Cisco 3550's doing QinQ on a Metro-E network. I was wondering whether anybody is succesfully copying the 802.1P info from the Inner Tag, to the Outer Tag. From the following doc:

Re: [c-nsp] QinQ Layer2 QoS - 3550?

On Mon, 11 Jan 2010 15:36:30 +0100, you wrote: What does one need to support Layer-2 QoS on QinQ, newer Juniper EX switches? Cisco 3750's? ME-3400E supports copying inner CoS to outer CoS. -A ___ cisco-nsp mailing list cisco-nsp@puck.nether.net

Re: [c-nsp] QinQ Layer2 QoS - 3550?

Hi. We have a number of Cisco 3550's doing QinQ on a Metro-E network. I was wondering whether anybody is succesfully copying the 802.1P info from the Inner Tag, to the Outer Tag. Sorry, but that's not possible on a 3550-class of switch. Only standard Catalyst (that I'm aware of) supporting

Re: [c-nsp] QinQ on SRB4

I have dot1q-tunnel working fine on SRB4, SRB5, SRD2. QinQ is somewhat different from dot1q-tunnel, because it usually refers to the termination of double-tagged traffic (vs dot1q-tunnel which refers to the addition of an extra tag), something that is not supported on the 67xx cards. -- Tassos

[c-nsp] QinQ on SRB4

Hi, Has anyone got dot1q-tunnel to work on SRC, because Same config but between 6500 (12.1(27b)E3) and 7600 (12.2(33)SRB) works fine, But when I try to do it between 7600 (12.2(33)SRB) and 7600 (12.2(33)SRC). Any ideas? ___ cisco-nsp mailing list