-
Notifications
You must be signed in to change notification settings - Fork 228
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
4 Bytes ASN not supported in Route-map #8009
Comments
@BouchardClaude specific list of operating systems, please? |
Also, are there any global configuration options that change how ASNs are handled or displayed in your configs? Ideally, just share a full config with the issue (anonymized with netconan is okay). |
dhalperi
added a commit
to dhalperi/batfish
that referenced
this issue
Feb 6, 2022
Make sure ASNs are always using typed integers Get rid of some int vs long cases add deprecated int functions to problematic classes to catch future misuses Likely fixes batfish#8009
I just looked at your commit and I think you understood the issue :) will let know as soon as I can test it so we can close this one. |
dhalperi
added a commit
to dhalperi/batfish
that referenced
this issue
Feb 6, 2022
Make sure ASNs are always using typed integers Get rid of some int vs long cases add deprecated int functions to problematic classes to catch future misuses Likely fixes batfish#8009
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I look like 4 Bytes ASN support was added but not for route map.
Example that will fail the device parsing (ARISTA or CISCO at least) is :
Device will parse if 4 bytes AS is in the bgp configuration, but not in a route-map
The text was updated successfully, but these errors were encountered: