You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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?
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 matt@hyperglass.io
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.
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
The text was updated successfully, but these errors were encountered: