Description
The IC high-level logical design pattern for network availability management illustrates how monitoring systems will monitor clients, servers, printers and network devices within an IC network; address space; and forward the appropriate messages and alerts to the central monitoring system. This approach allows information about network availability to be passed from within a private IP address space to the Central Network Management System to address existing private IP address spaces. No new private IP address spaces will be deployed, as CIT administers and centrally manages IP addresses within NIH. The Central Network Management System will have direct access through firewalls to monitor and manage the respective network devices. Please refer to the Security Architecture for instructions on how to enable secure SNMP traversal over the firewall. All local management systems must be configured to send out management and monitor messages to the local management console and the central management system simultaneously.
Diagram
Benefits
- Supports the NIH Network Operations Center (NOC) Capability and allows for performance monitoring and availability management across NIHnet
- By establishing procedures and criteria for forwarding system performance information and alerts to a central network management capability, critical outages may be prevented through proactive Fault Prediction and Problem Management
- This solution allows ICs to have their own Logical Network Views while providing backup management capabilities with 24/7 network monitoring through the NIH NOC
- This approach allows for predictive traffic analysis to enhance capacity planning
Limitations
- Development of such a system may be complex
- As the implementation of ESM progresses, this pattern will be expanded so that selected alarms and notifications are also passed to a Manager of Managers (MoM) that can incorporate network status into problem management and user-support activities.
Time Table
This architecture definition approved on:
February 8, 2005
The next review is scheduled in:
TBD
