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
When using structured on Juniper for show bgp route I am getting back
rt, 0, rt_entry, 0, peerAs
When I set structured to false it works fine. (log attached)
Also I noticed that if I set structured as false I see 2 versions of BGP route in the drop down, one does the non xml command, one does the xml command. I assume that is a bug of some sort (image attached of that)
looked into this error a bit more. It seems like on my Juniper installs the active route does not display the parameters for peer-as and local-as. It does show them for all the other inactive routes though. not sure what the fix would bee though. I am am not sure if this has to do with the fact we are using reflectors or if the the issue has to do with certain juniper code versions missing those parameters
Worked on this a bit tonight and did a workaround for now and it seems to work properly
edited the juniper parser within the docker container
-vi /opt/hyperglass/hyperglass/parsing/juniper.py
-change the following lines to look like the following
peer_as: int = 0
source_as: int = OUR AS NUMBER
-type in exit
-Get docker container ID
sudo docker ps -a
copy container ID for hyperglass-hyperglass
-commit docker changes
sudo docker commit hyperglass-hyperglass
-restart service
Deployment Type
Docker
Version
v2.0.4
Steps to Reproduce
When using structured on Juniper for show bgp route I am getting back
rt, 0, rt_entry, 0, peerAs
When I set structured to false it works fine. (log attached)
Also I noticed that if I set structured as false I see 2 versions of BGP route in the drop down, one does the non xml command, one does the xml command. I assume that is a bug of some sort (image attached of that)
debug.txt
Expected Behavior
router to produce expected results
Observed Behavior
router did not product expected results
Configuration
Devices
Logs
attached
The text was updated successfully, but these errors were encountered: