I am troubleshooting an issue with a 920/903 load balancing pseudowires/xconnects. I heard/read that I could use the FAT pseudowire method, but I have to transition my pseudowires from the service instance/xconnects to be defined in the l2vpn section of my config.
Here is an example:
l2vpn xconnect context TestPW
member GigabitEthernet0/0/1 service-instance 1
and the two members of the l2vpn context:
description Test FAT MPLS Load Balancing
neighbor 10.0.0.1 123
no ip address
service instance 1 ethernet
description Test FAT PW Load Balance
The pseudowire/l2vpn is established with the neighbor which has the same mtu size on the other end and vc IDs match, but I am unable to ping across. I just have a test laptop on either end (with firewalls disabled for testing) and am pinging across 192.168.2.1 on one side to 192.168.2.2 to the other side, but the traffic is not seeming to make it across.
Any ideas? Anything that is obviously missing from the config?
Listen: https://smarturl.it/CCRS9E25 Follow us: twitter.com/ciscochampions
With applications and users everywhere, the networks are now, more than ever, being tasked with delivering consistent protection while providing an exceptional user exper...
Listen: https://smarturl.it/CCRS9E24 Follow us: https://twitter.com/CiscoChampion
Cisco Radio Aware Routing addresses several of the challenges faced when merging IP routing and radio communications in mobile networks, especially those exhibiti...
Listen: https://smarturl.it/CCRS9E23 Follow us: https://twitter.com/CiscoChampion The Wi-Fi 6E Catalyst 9136 access point takes advantage of the 6-GHz band to produce a network that is more reliable and secure, with higher throughput, more ...
When moving from OSPFv2 to OSPFv3, there are many changes in the format of the LSAs Type, but the most known changes are: IP prefix informations are no longer carried in Type-1 LSA and Type-2 LSA, new LSAs Type 8 and 9 are added to carry these prefixes.