Network Events, Alarms, and Alerts in Network Management
This paper examines the categories of network events and event-based transactions that trigger alarms and alerts within network management systems. It focuses on RMON (Remote Network Monitoring) alarms as a common alert mechanism, explaining how CPU utilization thresholds, polling intervals, and rate-based monitoring can generate notifications for network managers. The paper also explores multi-level alarm structures, including alarm chains where the failure of an expected secondary alarm itself triggers a notification. Together, these examples illustrate the complexity and breadth of network event monitoring and underscore the importance of informed network management practices.
- Introduction to Network Events and Alarms: Scope and breadth of network event categories
- RMON Alarms and CPU Utilization Monitoring: Threshold-based RMON polling triggers explained
- Rate-Based RMON and Bandwidth Efficiency: Interval-based alarms improve efficiency over polling
- Hierarchical and Cascading Alarm Structures: Alarms that trigger further layered alarm events
- Complex Alarm Logic: When Missing Alarms Trigger Alerts: Missing secondary alarms themselves generate notifications
- Conclusion: Acknowledges breadth and importance of alarm knowledge
✍️ How to write this paper — guide, tools & examples ▾
What makes this paper effective
- Uses a concrete, relatable example — CPU utilization monitoring — to ground abstract networking concepts in a practical context readers can follow.
- Builds complexity progressively, moving from simple threshold-based alarms to multi-level and cascading alarm structures, creating a logical arc.
- Acknowledges system limitations (e.g., bandwidth drain from continuous polling) and presents alternatives, demonstrating analytical rather than purely descriptive thinking.
Key academic technique demonstrated
The paper demonstrates concept elaboration through contrast: it introduces a standard approach (continuous RMON polling), identifies a drawback (bandwidth inefficiency), and then presents an improved alternative (rate-based interval monitoring). This compare-and-contrast method at the sentence and paragraph level is an effective way to develop an argument without requiring extensive external evidence.
Structure breakdown
The paper opens with a scoping introduction that acknowledges the breadth of the topic before narrowing focus. It then moves through two distinct RMON alarm types, transitions to hierarchical alarm structures, and concludes with a more complex scenario involving missing-alarm triggers. The conclusion is brief and functional, reinforcing the paper's limited scope. Citations are concentrated in the technical middle sections where claims require support.
Introduction to Network Events and Alarms
It is not at all difficult to name and describe an event category or event-based transaction that can trigger an alert, alarm, or otherwise cause a network management system to bring something to the attention of a network manager; the difficulty is in limiting the scope of such categories and transactions. Depending on the specific needs and architectures of the network and its users, the type of event or event-based transaction that might lead to the notification of a network manager could be virtually anything. There are, however, some common event categories and event-based transactions that will trigger alarms or other notifications in the network management system and require attention from network managers. Several of these event and transaction types are identified and described below, with their relevance discussed.
References
Cisco. (2007). Network Management System: Best Practices White Paper. Retrieved November 20, 2011, from http://www.cisco.com/en/US/tech/tk869/tk769/technologieswhitepaper09186a00800aea9c.shtml
Tang, C., Li, X., & Zhou, X. (2008). Advanced Data Mining and Applications. New York: Springer.
Create your account
Always verify citation format against your institution’s current style guide requirements.