services/Anycast-Wiki.md
... ...
@@ -93,9 +93,10 @@ server {
93 93
94 94
The prefix AS-PATH should show the announcement is originating from your AS. After peering ExaBGP to the nearest speaker(s), check if the prefix is routing properly inside your network. Try not to blackhole the passing traffic (e.g. no static routes to `172.23.0.80/28`). Test the whole thing by shutting down nginx/gollum and watch what happens.
95 95
96
-##### exabgp.conf:
96
+##### Configuration
97 97
98 98
```
99
+# exabgp.conf
99 100
100 101
group gollum-watchdog {
101 102
neighbor <peer1> {
... ...
@@ -122,11 +123,11 @@ group gollum-watchdog {
122 123
123 124
```
124 125
125
-##### gollum-watchdog.sh:
126
+##### Watchdog script
126 127
127 128
Watchdog runs in an infinite loop, sending the appropriate commands to stdout. [ExaBGP](https://github.com/Exa-Networks/exabgp) attaches to the process' stdout and listens for instructions. Watchdog sends either a route announce or widthdraw.
128 129
129
-Run the script in a shell first to validate it's working.
130
+Run `gollum-watchdog.sh` in a shell first to validate it's working:
130 131
131 132
```
132 133
#!/bin/bash
... ...
@@ -189,9 +190,10 @@ exit 0
189 190
190 191
```
191 192
193
+##### Run
194
+
192 195
Normally SIGUSR1 to the exabgp process triggers a configuration update, but at occasion the process might need to be restarted - since its gracefull shutdown can be glitchy , this might be a bit difficult. Sending SIGKILL to the child(ren) and immediately after, the parent, does the job (quick-and-dirty).
193 196
194
-##### /etc/exabgp/run.sh:
195 197
`USAGE: /etc/exabgp/run.sh [start|stop|restart]`
196 198
197 199
```