Routers

The XRTG Routers page is where you register the devices you want to monitor. You add each router to an XRTG server, hand XRTG the SNMP details it needs to poll it, and then pick which of the router's interfaces to graph. This is the starting point for everything on the Graphs and Diagnosis pages.

Servers and routers

The top of the page shows a card for each XRTG server with its status and how many routers it holds, followed by a table of routers per active server. Each router row lists its Name, Host, SNMP Port and when it was Last Polled. If no servers appear, deploy one from the Client Portal first.

Adding a router

Click Add Router and fill in the XRTG Server to attach it to, a Router Name, the Host IP, and the SNMP Community and SNMP Port (161 by default) used for monitoring. On save, XRTG reaches out to the router and discovers its interfaces automatically — give it a moment, then the router appears in the table. Use the Poll Now action any time to re-discover interfaces, and the pencil icon to edit a router's details.

Interfaces (probes)

Open a router's Interfaces panel (the gear icon) to see every interface XRTG discovered, each with its name and index. Toggle an interface on to start graphing it — each enabled interface becomes a probe that shows up on the Graphs page. Leave interfaces you don't care about switched off to keep the graph tree tidy. If the list is empty, run Poll Now on the router first.

Enabling ping and traceroute

Editing a router reveals an optional Enable ping / traceroute switch that lets it run on-demand tests from the Diagnosis page. Turn it on and choose the router's vendor. MikroTik uses the RouterOS API (username, password and API port, default 8728). SNMP-driven vendors — Cisco IOS/IOS-XE (ping only), Juniper, Huawei and H3C — need a read-write SNMP community (v2c) or an SNMPv3 user. Vendors that can't be triggered over SNMP (Nokia SR OS, Arista, Ubiquiti, Aruba CX) are shown but disabled.