gobgpdにfull route与えてみた。vultr Tokyoロケーションでいつものbirdの代わりにgobgpd動かしてみた。
そうしたらいまさらながら、メモリが厳しい、ことが分かった。birdだと512Mインスタンスでも取り込みとroute参照とかなんとかいっていたのが、gobgpdの場合、2Gインスタンスでも取り込みでめいいっぱい、な感じ。経路参照とか投入とか(やるならば)にはさらにもう少しメモリ積む必要ありそう。まぁgobgp使うケースというのは元来マルチCPUバリバリつかってこそでってことで。
なお、vultrのvps サービスで使えるbgpは、multiprotocol-bgpではない模様です。
- topの表示比較
(bird,bird6)
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 873 bird 20 0 167420 166392 2068 S 0.0 16.5 36:33.31 bird 875 bird 20 0 28440 27448 2252 S 0.0 2.7 0:40.10 bird6
(gobgpd,IPv4-unicastのみ)
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1501 root 20 0 2171632 1.8g 0 S 15.7 90.5 0:15.80 gobgpd
- summary
root@vultr:~# ./gobgp neighbor
Peer AS Up/Down State |#Received Accepted
169.254.169.254 64515 00:00:25 Establ | 765862 765862
root@vultr:~# ./gobgp nei 169.254.169.254
BGP neighbor is 169.254.169.254, remote AS 64515
BGP version 4, remote router ID 66.42.46.118
BGP state = ESTABLISHED, up for 00:00:49
BGP OutQ = 0, Flops = 0
Hold time is 90, keepalive interval is 30 seconds
Configured hold time is 90, keepalive interval is 30 seconds
Neighbor capabilities:
multiprotocol:
ipv4-unicast: advertised and received
ipv6-unicast: advertised
route-refresh: advertised and received
graceful-restart: received
4-octet-as: advertised and received
add-path: received
Remote:
ipv4-unicast: receive
UnknownCapability(73): received
cisco-route-refresh: received
Message statistics:
Sent Rcvd
Opens: 1 1
Notifications: 0 0
Updates: 0 122576
Keepalives: 2 2
Route Refresh: 0 0
Discarded: 0 0
Total: 3 122579
Route statistics:
Advertised: 0
Received: 765841
Accepted: 765841
