Labs / Under Load / Management & monitoring: LLDP, out of band, errors & SNMP

Lab 3 of 4 · Management & monitoring: LLDP, out of band, errors & SNMP

Interface errors: reading the counters

Read an interface's counters to find drops, giants, bad frames and flaps.

Open this lab Pro 5 steps

The idea

pc reaches a server through a Router. Every card counts what went wrong: drops, errors, oversized frames and flaps. Read the counters twice and compare.

Each drop is counted where it happens
Each drop is counted where it happens
A duplex mismatch: each end counts a different error
A duplex mismatch: each end counts a different error

Steps

  1. Where the counters are

    A card records trouble in its counters, so find them before anything breaks. Read the counters of the router's card on the servers network: packets and bytes, and beside them the errors and drops, each by kind.

    router:~# ip -s -s link show dev servers
  2. A full link: utilization and output drops

    A busy link loses packets with nothing broken, and only the counters say so. The router's card to the servers now sends at most 10 Mbit/s, and pc pushes 20 Mbit/s through it. Read the queue in front of the card, before and after the burst.

    router:~# tc -s qdisc show dev servers
    router:~# tc -s qdisc show dev servers
    router:~# ip -s link show dev servers

Pro

3 more steps in the app

  1. Giants: a frame bigger than the MTU
  2. Damaged frames: CRC on a wire, checksums here
  3. Flaps: the line going down and up
Get Pro

Learn it on real machines.

Every lab is a small network of real Linux machines in your browser. Start with a free account: Google or email, no card.

Open this lab