NEMO

Why was NEMO built?

NEMO is the result of 25 years of service provider and enterprise network operations experience. During this time, I encountered the same problem again and again: network operations teams were technically proficient, yet could not work with sufficient efficiency. It was not knowledge that was missing — it was information.

Why was it built by a CCIE?

Because the most important question is not what can be displayed, but what actually matters. After twenty-five years of service provider and enterprise operations experience, I know precisely which events require immediate action and which are a natural part of normal network behaviour. This experience is embedded in NEMO's decision logic.

Why focus on the most important events?

Not all events are equal. A user port going down is a natural part of daily operations. A trunk link failure between switches, however, demands immediate investigation. NEMO's goal is not to display every event. The goal is for the right event to appear with the right priority.

Why doesn't it try to solve every problem?

Because no system solves every problem. NEMO does not aspire to be a universal network management platform. Its goal is far simpler: to reduce the time engineers spend on daily routine tasks. If less time goes to searching for information and performing repetitive tasks, more time remains for solving real problems. A simple example A user port inactive for 120 days is not a fault in itself.