Wanguard 6.2 User Guide
Configuration » Components » Quagga / ExaBGP Connector
Operations Tools » <Black Hole> or <Divert Traffic>. If you encounter errors, follow the troubleshooting guide below:
BGP Connector Troubleshooting
✔
Ensure that you have correctly configured the BGP Connector. Each configuration field is described in
depth in this chapter.
✔
Look for warnings or errors produced by the BGP Connector in Reports » Tools » BGP Operations » BGP
Connector Events (details on page 69).
✔
Telnet connection errors on port tcp/2605 in the event log indicate that the Quagga BGPd daemon is not
accessible through telnet. By default, Debian systems bound bgpd to 127.0.0.1, which is why the string
“-A 127.0.0.1” must be deleted from /etc/quagga/debian.conf.
✔
Telnet connection errors on port tcp/2601 indicate that the Quagga BGP Connector was configured with
the Quagga Zebra Local Back Hole feature, but the zebra daemon is not configured or accessible from
the Console server.
✔
Telnet errors about pattern time-outs indicate mismatches between a parameter defined in the BGP
Connector (password, AS number, route-map, AS view) and the similar parameter from bgpd.conf.
✔
You can clear BGP prefix errors from Reports » Tools » BGP Operations » Active BGP Announcements »
<Remove All>, or by clicking the stop button for each announcement.
✔
Errors about “orphaned” announcements indicate that the BGP announcement is active while the
anomaly has ended. The BGP announcements are withdrawn by the Sensor that detected the anomaly,
immediately after the anomaly ends.
Orphaned announcements can have multiple reasons:
◦
The anomaly was ended forcefully by clicking
the <Expire Anomalies> button
◦
The Sensor that detected the anomaly was deleted or had errors
◦
The WANsupervisor was not running at the time of the withdrawal
◦
Networking errors between the Console server and the server running bgpd. If this is the case, you
should see the exact telnet error in the event log.
✔
Make sure you are running the latest version of the software.
- 54 -
Summary of Contents for wanguard 6.2
Page 1: ......