Guided turn-up of a new edge POP: give it the daemon host's IP and this panel generates an SSH deploy key,
installs and configures the dn-bgp edge daemon over SSH, walks you through onboarding the local
Juniper MX204, and finishes with the backbone wave to an existing POP (e.g. Boston → Kansas City).
POP & Host
Authorize Key
Deploy Daemon
Router (MX204)
Backbone Wave
Done
1 · New POP & daemon host
2 · Authorize the deploy key
Run this once on the host (console, IPMI, or an existing SSH session) to authorize the control plane. The private key never leaves this server; the host key is pinned on first contact.
3 · Deploy the daemon
The control plane now installs the daemon over SSH: binary upload (sha256-verified + self-test), edge config, systemd unit, start & health check — then registers the edge and waits for iBGP.
Edge registered in central
iBGP session established
4 · Onboard the local router (MX204)
Register the POP's Juniper MX204 so the panel can generate its iBGP/backbone config, push wave turn-ups, and health-check the box. You'll paste a few set commands on the router to authorize the key.
Paste on the router (configure mode), then commit:
5 · Backbone wave to an existing POP
The wave registry lives in Vader (PHP owns intent; this panel executes turn-up and monitors health).
Create the wave there — e.g. Boston ↔ Kansas City with both ends' interfaces, point-to-point
addresses and backbone loopbacks — and it appears here via the control-plane sync.
Don't forget the PHP side: the POP registry (BGPPop, incl. daemonPeerV4/V6
customers will peer with) and customer sessions live in Vader — the daemon pulls them from the
control-plane document.