I was looking in to the connect command after posting. Unfortunately the only supported interfaces types are showing up on the switch is Dialer and MFR on the 6500
So the reason that i am not setting this up as a vlan is the following. We have multiple GE circuits to different carriers that are setup as "L2 NNIs". The carriers deliver circuits (T1s to MetroE) to our customers put the traffic for each customer on a VLAN on the GE. Depending on the customers' needs they get Internet Access, L3VPN MPLS, or EoMPLS L2 P-P Service. With the multiple carriers going into this same chassis we have a lot of overlapping VLAN id's. (Config example at end of email) So the need for a L2 connection between two carriers are on the same switch has come up and that is why i need to create the Local L2 switching between the two subinterfaces. Here is what i am looking for in the XR Software but i am looking to be able to do the same thing on the Cat6500, but it doesn't support L2VPNv3 l2vpn xconnect group examples p2p example1 interface TenGigE0/7/0/6.5 interface GigabitEthernet0/4/0/30 The only other work around i can think of is to backhaul the need Switch subinterface to a subinterface on our PE router then having a xcossover cable between the two interfaces on our PE. But i am not a fan of this idea of mine. So it would look like the following SWg1/2.3000----EoMPLS--PE1g0/0/0.10 Xconnect cable between the GE interface on our PE1 or using the connect command. SWg1/3.100----EoMPLS--PE1g0/0/1.10 Below is an example of how our switch is configured for each carrier. interface GigabitEthernet1/2 no ip address ! interface GigabitEthernet1/2.111 description Internet Customer ip address 1.1.1.1 255.255.255.252 ! interface GigabitEthernet1/2.222 description MPLS Customer ip vrf forwarding L3VPN-CUST1 ip address 2.2.2.2 255.255.255.252 ! interface GigabitEthernet1/2.333 description EoMPLS Customer encapsulation dot1Q 2000 xconnect 192.168.0.1 1 encapsulation mpls ! Interface GigabitEthernet1/2.3000 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Need to connect to GigabitEthernet1/3.100 encapsulation dot1Q 3000 ! interface GigabitEthernet1/3 no ip address ! Interface GigabitEthernet1/3.100 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Need to connect to G1/2.3000 encapsulation dot1Q 100 ________________________________________ From: Jason Lixfeld [ja...@lixfeld.ca] Sent: Sunday, June 17, 2012 12:48 AM To: Erik Sundberg Cc: cisco-nsp@puck.nether.net Subject: Re: [c-nsp] 6500 L2 Switch Traffic locally between two SubInterfaces on different ports? conf t connect ? ? -- Sent from my mobile device On 2012-06-17, at 1:09 AM, Erik Sundberg <esundb...@nitelusa.com> wrote: > I need to switch traffic at L2 between two sub interfaces G1/2.3000 and > G1/3.100 > > I was thinking I can do this with EoMPLS but.... no so much I get the > following error and I understand why. > > SWITCH(config)#int g1/3.100 > SWITCH(config-subif)#encapsulation dot1Q 100 > SWITCH(config-subif)#xconnect 192.168.0.2 3 encapsulation mpls > Local switching to peer address 192.168.0.2 is not supported > > Is there any way to switch L2 traffic between two subinterface on the same of > different ports? > > > > > Cisco 6500 Sup720-3bxl using WS-x6724-SFP module, > s72033_rp-ADVIPSERVICESK9_WAN-M, Version 12.2(33)SXH8b > ------------- > > > interface GigabitEthernet1/2 > no ip address > ! > interface GigabitEthernet1/2.2000 > !To other MPLS Device on network EoMPLS > encapsulation dot1Q 2000 > xconnect 192.168.0.1 1 encapsulation mpls > ! > Interface GigabitEthernet1/2.3000 > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Need to connect to > GigabitEthernet1/3.100 > encapsulation dot1Q 3000 > ! > interface GigabitEthernet1/3 > no ip address > ! > Interface GigabitEthernet1/3.100 > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Need to connect to G1/2.3000 > encapsulation dot1Q 100 > > Thanks > > Erik > > > > ________________________________ > CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files or > previous e-mail messages attached to it may contain confidential information > that is legally privileged. If you are not the intended recipient, or a > person responsible for delivering it to the intended recipient, you are > hereby notified that any disclosure, copying, distribution or use of any of > the information contained in or attached to this transmission is STRICTLY > PROHIBITED. If you have received this transmission in error please notify the > sender immediately by replying to this e-mail. You must destroy the original > transmission and its attachments without reading or saving in any manner. > Thank you. > _______________________________________________ > cisco-nsp mailing list cisco-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files or previous e-mail messages attached to it may contain confidential information that is legally privileged. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this transmission is STRICTLY PROHIBITED. If you have received this transmission in error please notify the sender immediately by replying to this e-mail. You must destroy the original transmission and its attachments without reading or saving in any manner. Thank you. _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
