Reference
Interfaces, Planning and Unidentified
Interface utilization against capacity, 95th percentiles, capacity forecasts, the transit view, and the traffic Heimnull couldn't name.
Interfaces
Section titled “Interfaces”Traffic → Interfaces shows the interfaces you’ve listed (Configure → Interface settings → Show on the Interfaces page), grouped by exporter, filtered by role:
- in and out traffic against capacity, with a sparkline;
- the 30-day 95th percentile of 5-minute averages, as transit is billed (from SNMP, else from flows);
- errors and discards per second, from SNMP;
- flows against SNMP: the traffic the flow records account for, as a share of what the interface counters measured.
Capacity is the interface’s subscribed rate if you set one, else its port speed from SNMP.
The accuracy check
Section titled “The accuracy check”An interface’s page overlays the flow-estimated rate on the SNMP-measured one, in and out, and shows the ratio. Near 1 is right. A ratio far from 1, sustained, means the flows miss traffic or count it wrong: a wrong sampling rate, sampling on more than one interface, flow export missing on that interface, or (on MikroTik) FastTrack. See Common problems.
Planning
Section titled “Planning”Traffic → Planning has two tabs. Both use the interfaces you’ve listed, and those with the Transit or Peering role.
Capacity forecasts
Section titled “Capacity forecasts”Each interface’s daily 95th percentile of 5-minute averages (SNMP, else flows) over 30 to 365 days (90 by default), with a trend line through the busier direction. For each interface: its level today against capacity, its growth per month, and the dates it would reach 80% and 100% of capacity (within 3 years). Needs at least 14 days of data.
Transit and peering
Section titled “Transit and peering”For each Transit and Peering interface, this month and the two before: the 95th percentile in and out, the billed rate (the busier direction), and the billed rate against the commit (the subscribed rate, else the port speed).
Below it, peering candidates: the 25 remote ASes sending the most over your transit links in the last 30 days, with their share of transit traffic and their PeeringDB type, peering policy (Open, Selective, Restrictive, No), and how many exchanges and facilities they’re at.
Unidentified
Section titled “Unidentified”Traffic → Unidentified is the traffic no rule named, grouped by ASN, by prefix or by port pattern. From any row you can start a rule pre-filled with that AS, prefix or port, at the usual weight for its kind. See Classification.