Skip to content
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

BGP ASpath for Junos returns "field required" error #54

Closed
brevius opened this issue Jul 10, 2020 · 4 comments
Closed

BGP ASpath for Junos returns "field required" error #54

brevius opened this issue Jul 10, 2020 · 4 comments
Assignees
Labels
possible-bug Something isn't working

Comments

@brevius
Copy link

brevius commented Jul 10, 2020

The commands sent to router looks good:
"show route protocol bgp table inet.0 aspath-regex ".* ASnum" detail | display xml"
The XML output is returned from the router, but on the GUI the "field required" is shown. No other error is generated by hyperglass.
Tested JunOS version - 18.4R3

@brevius brevius added the possible-bug Something isn't working label Jul 10, 2020
@thatmattlove
Copy link
Owner

This should be fixed in 1.0.0-beta.50 - release published just a few minutes ago. Can you update and test again, please?

Thanks,
Matt

@brevius
Copy link
Author

brevius commented Jul 13, 2020

After upgrade to beta.50 no change. However I noticed the same problem with BGP route query. If the route is not found in the table the output is The query completed, but no matching results were found. But when the route exists field required is given back. RPC output looks good for all commands.
Maybe I have to try with fresh install - not upgrade?

@thatmattlove
Copy link
Owner

Is the XML output something you can share? I’m wondering if there’s something unique about one of the routes that requires an adjustment in the parser. If needed you can email it to [email protected]

@thatmattlove
Copy link
Owner

Thanks for sending the XML - that helped me narrow this down. Looks like it was because the route had no communities at all, and Junos left the communities key out of the response entirely. This should be fixed in 1.0.0-beta.51, but let me know if not.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
possible-bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants