Cross devices correlation (demo with BGP troubleshooting)
The devices rule check-bgp-state-using-openconfig collects BGP details and monitor sessions state.
The playbook bgp-using-openconfig uses the rule check-bgp-state-using-openconfig
The network rule compare-peer-type queries the database updated by the rule check-bgp-state-using-openconfig, and compares the BGP peer type configured on 2 BGP peers (same peer type should be used)
The network rule compare-as queries the database updated by the rule check-bgp-state-using-openconfig, and compares the local-as configured on a router with the peer-as configured on one of his BGP peer (same AS should be used)
The playbook bgp-troubleshooting uses the rule compare-peer-type and the rule rule compare-as
Instanciate the playbook bgp-using-openconfig
Run the python script bgp_troubleshooting.py to instanciate the playbook bgp-troubleshooting for:
- vmx1 <-> vmx4
- vmx1 <-> vmx5
- vmx1 <-> vmx6
- vmx1 <-> vmx7
- vmx2 <-> vmx4
- vmx2 <-> vmx5
- vmx2 <-> vmx6
- vmx2 <-> vmx7
- vmx3 <-> vmx4
- vmx3 <-> vmx5
- vmx3 <-> vmx6
- vmx3 <-> vmx7
Healthbot shows the root cause of the issue (AS configuration mismatch between vMX4 local-as and vMX1 remote-as)
