DN NMS

dev · AS399646

Overview

Dashboard

Daemons

Edge Daemons Daemon Peers Customers

Routing

Looking Glass ASN Lookup Policies Shared Lists Shared Firewall Communities

Infrastructure

POP Setup Routers Backbone Waves Deployer

System

System & Config Logout

Backbone Waves

Route registry · the NMS is the source of truth

0

Waves

0

Healthy

0

Down / Degraded

0G

Total Capacity

-

Avg Wave RTT

Topology

Wave IP Allocation

Loading…

Point-to-point pool (/31 per wave) Loopback pool (one /32 per POP)

Point-to-point /31s

Backbone loopbacks

Route	Wave	Path	Capacity	Status	Health	RTT	Geometry	Updated
Loading…

New Wave

Code Name Capacity (Gbps) IS-IS Metric MPLS Mode Status Provider Circuit ID

A end (local) POP Router host Interface P2P address Backbone loopback Agg switch host (optional) Switch: wave port Switch: router port Handoff VLAN

Z end (remote) POP Router host Interface P2P address Backbone loopback Agg switch host (optional) Switch: wave port Switch: router port Handoff VLAN

Leave P2P / loopback / VLAN blank and the registry allocates them from the tracked pools — a POP always keeps its existing loopback. Set an agg switch host to also generate + push the switch-side VLAN config over SSH (register the switch on the Routers page with role "switch").

Notes

Import Fiber-Route Geometry from Snaju

One-time migration: pulls the circuit traces out of the Snaju network-map feed and stores each one on the wave you pick — after this the NMS is the system of record for route geometry (the status page and the Snaju View displays read it back from here).

Feed URL

Loading circuits…

Turn-up JunOS