rcc: Configuration Verifier

Example Output

More detailed instructions for running the verifier are in the manual, but it's essentially as easy as running a script. The output will look something like the examples below.

Next-hop reachability test. Test that, for an eBGP session, either set next-hop-self is used or that the network associated with the BGP session is injected into the interior routing protocol. Output for this test looks roughly like this:
found ebgp on atlga-gw1 (AS 65000)
ebgp: no next-hop-self atlga-gw1 (
ERROR: not in iBGP/IGP (eBGP session)
The first two lines are debugging lines and will typically not print unless the debugging flag is turned on. The last line indicates an error condition: the IP address of the eBGP neighbor is not present in the interior routing protocol. This is an error, because, as indicated by the previous line, next-hop-self is not used on the session.

Dangling BGP session test. Test that, for each attempted iBGP session (i.e., bgp neighbor statement), Output for this test looks roughly like this:
ERROR: no _r2 with loopback (from bosma-gw)
ERROR: no _r2 with loopback (from bosma-rr1)
ERROR: no _r2 with loopback (from bosma-rr2)
ERROR: laxca-gw has NO "router bgp" statement
The first three lines show example violations. The error condition for a particular line indicates that there is a bgp neighbor statement on a particular router (e.g., bosma-gw) that attempts to establish an iBGP session to an IP address that is not the loopback address of any router in the AS.

The fourth error line indicates that there is a router in the AS that has no router bgp statement at all (thus, not even attempting to establish BGP connectivity). As this example shows, the yacc-style rules can be network-wide, and complex enough to show exactly where (and how) a particular error is occurring.

Back to Overview