-
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
Limited number of VRFs in VPNv4 #16744
Comments
Hi @mnaiem81 , this looks like a label manager issue in BGP, where BGP does not know:
|
Hi @pguibert6WIND,
|
Is this the same for FRR v10 ? or a plan to fix? |
I think the issue still remains, and a fix needs to be done. No plan to fix as of today. |
Hi @mnaiem81 , Would it be possible to share "show running-config" of problematic node and its one of the peer ? ( peer which has vpnv4 session with problematic node. ) Thanks |
here is config, I just removed one PL named 'PL.NET4.SPECIFIC' which permits some public IPs but nothing fancy there just PL. '''Current configuration: connected VPN config ''' |
r1# show version configured with:
|
if you come up with a stripped down topotest showing the issue, we take a look at if this. |
Could someone please describe a minimal topology + config to show this problem? I don't normally work with mpls but I do have a vanilla linux VM with FRR. Can it be done with a single instance of FRR? I tried just loading the FRR config file containing the running config that mnaiem81 posted above but "show mpls table" was empty. Surely I'm missing some other important pieces. |
Hi @paulzlabn
|
Lou indicated you were working on a topotest - any luck? It might take me a while otherwise to get a working setup. |
Hey, We were able to write the topotest and find the solution. Will commit shortly Thanks |
Description
I see an issue with v9.1 where I deploy +255 VRFs per server with dynamically assigned VPN label using 'label vpn export auto'
Two below scenarios happen here:
What is the problem?
Output of show mpls table below from one FRR with 260 VRFs, the last configured 15 VRFs not working because no labels for them although from table label#466,469,471,472, etc are free from previously deleted VRFs.
VRF config (nothing special)
Version
How to reproduce
To reproduce, run 'show debugg label-table' to check assigned pool chunk.
If it is 128, you need to create more than 128 VRFs and verify from show mpls table.
if it is 256, you need to create more than 256 VRFs and verify from show mpls table.
Delete any VRF to free-up its assigned label and try to get it dynamically assigned again.
Expected behavior
Expected behaviors here:
Actual behavior
Limitation of supported VRFs per server limits its usage
Additional context
No response
Checklist
The text was updated successfully, but these errors were encountered: