Are vlan translations supported using 3750ME and 7606?
I'm trying to turn up an SVI xconnect between two PE boxes (3750ME and 7606) over our MPLS network, but when I use different interface VLANs with matching VCIDs, the VLAN on the client switch that's attached to the 7606 PE will go into *PVID_Inc. I've built this before between a pair of 7606 PEs but this is the first attempt using a 3750 as a PE.
Below are some of the configs for the devices:
3750ME-pe1#show run int vlan10 Building configuration...
Current configuration : 121 bytes ! interface Vlan10 description *****
no ip address mpls ip xconnect 172.24.100.1 1714 encapsulation mpls end 3750ME-pe1#
7606-pe1#show run int vlan 1714 Building configuration...
Current configuration : 107 bytes ! interface Vlan1714 description ***** mtu 1546 no ip address mpls ip xconnect vfi ***** end
7606-pe1#show run int g2/31 Building configuration...
VLAN1714 Spanning tree enabled protocol rstp Root ID Priority 34482 Address 000e.d766.6880 This bridge is the root Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 34482 (priority 32768 sys-id-ext 1714) Address 000e.d766.6880 Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec Aging Time 300 sec
Interface Role Sts Cost Prio.Nbr Type ------------------- ---- --- --------- -------- -------------------------------- Fa0/24 Desg BKN*19 128.24 P2p *PVID_Inc
Dec 11 07:32:05.256 EST: %SPANTREE-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id 10 on FastEthernet0/24 VLAN1714. Dec 11 07:32:05.256 EST: %SPANTREE-2-BLOCK_PVID_LOCAL: Blocking FastEthernet0/24 on VLAN1714. Inconsistent local vlan.
I guess I should have stated that this is a 3750 Metro switch (ME-C3750-24TE-M). This switch connect to one of our P boxes via the ES ports. What I'm trying to build is an EoMPLS xconnect over SVI. I do agree that on "regular" 3750s MPLS isn't supported.
I think that if this is similar to vlan rewrite you may be able to setup the VC.
This feature is supported on C7600 side with sup720
Sub-interface Xconnect, also called VLAN-edge Xconnect
Sub-interface Xconnect differs from Interface Xconnect because the ingress port is a trunk (such as dot1Q). The switch removes the 1Q header, extracts the VLAN number, determines the associated sub-interface, and performs the cross-connect with the associated VLAN at the other side of the network. This simulates VLAN-to-VLAN switching (at long distance through the MPLS network). VLAN renumbering is possible, but it adds complexity to the design.
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...