An administrator is working on a server with two CPUs. The administrator runs the uptime command and sees the following: 17:52 3 days 12 users 12.0 15.2 17.2 Several users are complaining that their…

The `top` command displays the `wa` (I/O wait) percentage for each process, indicating how long processes are stalled waiting for disk or other I/O operations. On a 2-CPU system, a healthy load average should stay near 2.0, so values of 12.0 to 17.2 indicate the system is heavily overloaded - most likely due to I/O contention causing high wait states. Running `top` allows the administrator to identify the specific processes responsible and determine the appropriate remediation.

`who -r` outputs the current system run level, which is unrelated to identifying which processes or users are consuming CPU or causing I/O contention.

A tool for finding users consuming excess network bandwidth would not address the cause of high CPU load averages reported by `uptime`, which reflect CPU scheduling and I/O wait pressure rather than network utilization.