05-06-2017 05:34 AM - edited 03-08-2019 10:28 AM
Hai
I need to extend layer 2 vlan between two 4500X distribution switches connected to a core .core and distribution are layer 3.
Is there a way to do this .What licence/feature required for 4500x
Best regards
05-06-2017 08:15 AM
You would need to create the same VLAN on all your switches, this would then also stretch the subnet out across all these same switches as well.
Please rate if useful.
05-07-2017 05:22 AM
05-08-2017 01:47 AM
Hello
This can be accomplished by using a VPLS connection provided by your ISP, From your perspective this connection between each site would be as if the two switches are in the same closet.
However this type of connection would obviously incurr additional cost to your company to procure such a link.
res
Paul
05-06-2017 08:26 AM
Hello,
unfortunately, you have limited options for VLAN extension on 4500. It neither supports MPLS nor L2tp tunnel.
The only thing comes to my mind is to connect two routers to the 4500 switches and configure L2TPv3 on them, which is not very practical and adds complexity.
Lets see what others suggest.
Masoud
05-06-2017 11:20 PM
05-07-2017 07:14 AM
I do not see any options as far as I know. At least, you need ASR or 1841 for L2TPv3. It is dirty but you can add a link between 2960s if you do not have physical constrain and allow only vlans you want or make it access.
Masoud
05-06-2017 11:44 PM
Hello,
in addition to the other posts, there is a feature called Local Area Mobility (LAM) which basically lets hosts within a subnet/Vlan move to different locations and still maintain connectivity. I am not sure if the 4500X switches support that feature. Either way, it might be worth looking at:
http://www.cisco.com/en/US/products/ps9390/products_white_paper09186a00800a3ca5.shtml
05-07-2017 04:57 AM
I just wanted to add that VTP V3 supports extended vlans so by using vtp v3 you won't have to manually create extended vlans on other switches. With manual configuration it's possible to create extended vlan on one switch and not the other, down the road you can have an issue where you configure an SVI on the switch that doesn't have extended vlan configured is using the same extended vlan number in the backend as the other switches with manual configuration of extended vlans. You will start having issues with that extended vlan/SVI and usually there are no log messages so could be pretty tough to troubleshoot an issue like that. But if your team follows a policy/procedure then you can definitely avoid an issue like this without using a feature like VTP v3.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide