-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EVPN-MPLS T1 Label lost #15678
Comments
Can confirm I am able to reproduce this with a client |
@baldoarturo If you can provide some PCAPs with generic data, that might help make it easier for someone to tackle this issue. |
This issue is stale because it has been open 180 days with no activity. Comment or remove the |
This issue will be automatically closed in the specified period unless there is further activity. |
This issue still exists. Unfortunately, I do not have a lab to test it at this time. |
This issue will no longer be automatically closed. |
@murrant , do you have the evpn configuration to share, pls? for instance, ios xr config? |
#17985 should help |
This is a sample config from a couple IP Infusion OcNOS boxes
|
Description
I'm attempting to use FRR as a route reflector for our EVPN/MPLS/ISIS-SR network.
It seems to be losing the label for type 1 circuits and sending 1048575 instead (binary 11111111111111111111).
Update received by FRR:
![image](https://private-user-images.githubusercontent.com/39462/319353462-e3a5b3db-f89d-4ccf-88da-be30b6e56669.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzg4MDc1NTksIm5iZiI6MTczODgwNzI1OSwicGF0aCI6Ii8zOTQ2Mi8zMTkzNTM0NjItZTNhNWIzZGItZjg5ZC00Y2NmLTg4ZGEtYmUzMGI2ZTU2NjY5LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMDYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjA2VDAyMDA1OVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTE5YTNhNjk3ZDAyYjQ5NTQxOTFjMTE5ZGE5YzkyYWE3MTM0NmIyYzI3OTFmYmUzYTdmYTM3NmMwYzA5NzM5ZTEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.iMWKn7zpPgSX_WUXMZaw5K3OzLGtPohc6iNtB4R00As)
Update sent by FRR:
![image](https://private-user-images.githubusercontent.com/39462/319353011-945bbc74-0781-40f5-a390-fd801780e1af.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzg4MDc1NTksIm5iZiI6MTczODgwNzI1OSwicGF0aCI6Ii8zOTQ2Mi8zMTkzNTMwMTEtOTQ1YmJjNzQtMDc4MS00MGY1LWEzOTAtZmQ4MDE3ODBlMWFmLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMDYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjA2VDAyMDA1OVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWU1OTZkN2NmYWVlZjkxZDVlMDJjODUwYWQwNWU3YmE5ZDBkOTUyNjE1NDlhMDUwNmQ3ODBlZjFmZDEyN2QxY2UmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.Y7kfm8lEUbUSvs8YoSbOGPEbW_UmjfFrU2wzaD3Xj9c)
Version
How to reproduce
Set up EVPN-MPLS VPWS circuit on equipment with BGP peering and confirm functionality.
Add FRR as route reflector and remove peering. The VPWS no long functions because the devices receive the wrong remote labels.
Expected behavior
Correct labels are sent.
Actual behavior
Labels are sent as 1048575
Additional context
Unclear if this is related to #7292
I have a packet capture with some moderately sensitive data (ASN) in it I can provide access to.
Checklist
The text was updated successfully, but these errors were encountered: