Hello @Muhammad-ly
To troubleshoot and resolve the issue with traffic not flowing between the routers, let's break this down step by step. Based on your description, the issue seems to be related to the encapsulation mismatch or configuration on the VPLS or xconnect setup. Here's how you can approach the problem:
1. Verify the VPLS Configuration
Ensure that the VPLS configuration on both routers (.61 and .83) matches. A mismatch in encapsulation or VLAN tagging can cause traffic to drop.
On Router 10.2.1.61:
Check the VPLS configuration:
show running-config | section l2vpn
Look for the xconnect or VPLS configuration and verify the encapsulation type. Since you mentioned using encapsulation untagged on .61, ensure that this is consistent with the configuration on .83.
On Router 10.2.1.83:
Similarly, check the VPLS configuration:
show running-config | section l2vpn
If you are using encapsulation default on .83, this might be causing the issue. The encapsulation type must match between the two routers. If .61 is using untagged, .83 should also use untagged.
2. Check the xconnect Status
Verify the xconnect status on both routers to ensure the pseudowire is up and operational.
On Router 10.2.1.61:
On Router 10.2.1.83:
The output should show the xconnect status as UP. If it is not UP, there may be an issue with the configuration or the underlying transport.
3. Verify the Encapsulation
The encapsulation type must match on both ends of the VPLS. If one side is using encapsulation untagged and the other is using encapsulation default, traffic will not flow.
On Router 10.2.1.61:
Check the encapsulation configuration:
show running-config interface <interface>
Ensure that the encapsulation is set to untagged if that is what you are using.
On Router 10.2.1.83:
Check the encapsulation configuration:
show running-config interface <interface>
If the encapsulation is set to default, change it to untagged to match .61.
To change the encapsulation on .83:
interface <interface>
encapsulation untagged
4. Verify VLAN Configuration
If you are using VLANs, ensure that the VLAN configuration is consistent across all routers. For example, if you are using VLAN 100 for the VPLS, ensure that VLAN 100 is configured on all interfaces participating in the VPLS.
On Router 10.2.1.61:
On Router 10.2.1.83:
If VLANs are not consistent, update the configuration to match.
5. Check for MTU Mismatch
An MTU mismatch can cause traffic to drop. Ensure that the MTU is consistent across all interfaces participating in the VPLS.
On Router 10.2.1.61:
show interface <interface> | include MTU
On Router 10.2.1.83:
show interface <interface> | include MTU
If there is an MTU mismatch, update the MTU to match on both routers:
interface <interface>
mtu <value>
6. Verify Connectivity
After making the necessary changes, test connectivity between the routers.
Ping from .61 to .83:
Ping from .83 to .61:
If the pings are successful, the issue is resolved.
7. Debugging (If Needed)
If the issue persists, enable debugging to gather more information.
On Router 10.2.1.61:
debug l2vpn xconnect
debug mpls ldp
On Router 10.2.1.83:
debug l2vpn xconnect
debug mpls ldp
Monitor the logs for any errors or issues.
8. Final Notes
- Ensure that the transport network (MPLS or IP) between the routers is functioning correctly.
- If you are using MPLS, verify that LDP is operational and labels are being exchanged:
show mpls ldp neighbor
show mpls ldp bindings
By ensuring that the encapsulation, VLANs, MTU, and transport network are consistent and operational, you should be able to resolve the issue with traffic not flowing to .83.
Hope This Helps!!!
AshSe
Community Etiquette:
- Insert photos/images inline - don't attach.
- Always mark helpful and correct answers, it helps others find what they need.
- For a prompt reply, kindly tag @name. An email will be automatically sent to the member.
