Network Management
Chapter 4
Chapter 4 SNMPv1: Organization and Information Models
Network Management: Principles and Practice © Mani Subramanian 2000
1
Chapter 4
Case Histories
• AT&T Network Management Centers • Network Operations Center • Network Control Centers • Monitors the network status • Self-healing • CNN World Headquarters • Performance Management • Fault Management • Monitoring alarms • Determines causes of failures (Artificial Intelligence) • Centralized troubleshooting of NIC (remotely) • Performance degradation due to NMS • Network may come down due to NM traffic • Need to manage NM tools • Bell Operating company procedure • NM tools can help in standardization of NM process
Network Management: Principles and Practice © Mani Subramanian 2000
2
Chapter 4
Managed LAN
NMS 192.168.252.110 192.168.252.0
Router 2 Backbone Network
Router 1 172.16.46.0
Hub 1 172.16.46.2 Hub 2 172.16.46.3
Figure 4.1 A Managed LAN Network
Notes
• NMS can automatically discover any component in the network as long as this component has a management agent. • NMS on subnet 192.168.252.1 manages the router and the hubs on subnet 172.16.46.0 across the backbone network
3
Network Management: Principles and Practice © Mani Subramanian 2000
Chapter 4
Managed Hub: System Information
Title: System Information: 172.16.46.2 Name or IP Address: 172.16.46.2 System Name System Description System Contact System Location System Object ID System Up Time : : 3Com LinkBuilder FMS, SW version:3.02 : : : .iso.org.dod.internet.private.enterprises.43.1.8.5 : (2475380437) 286 days, 12:03:24.37
Figure 4.2(a) System Information on 172.16.46.2 Hub
Notes
• Information obtained querying the hub • Data truly reflects what is stored in the hub • System Description and System Object ID are set at the factory and can’t be modified → read-only. • Time unit :1/100th of a second
Network Management: Principles and Practice © Mani Subramanian 2000
4
Chapter 4
Chapter 4 SNMPv1: Organization and Information Models
Network Management: Principles and Practice © Mani Subramanian 2000
1
Chapter 4
Case Histories
• AT&T Network Management Centers • Network Operations Center • Network Control Centers • Monitors the network status • Self-healing • CNN World Headquarters • Performance Management • Fault Management • Monitoring alarms • Determines causes of failures (Artificial Intelligence) • Centralized troubleshooting of NIC (remotely) • Performance degradation due to NMS • Network may come down due to NM traffic • Need to manage NM tools • Bell Operating company procedure • NM tools can help in standardization of NM process
Network Management: Principles and Practice © Mani Subramanian 2000
2
Chapter 4
Managed LAN
NMS 192.168.252.110 192.168.252.0
Router 2 Backbone Network
Router 1 172.16.46.0
Hub 1 172.16.46.2 Hub 2 172.16.46.3
Figure 4.1 A Managed LAN Network
Notes
• NMS can automatically discover any component in the network as long as this component has a management agent. • NMS on subnet 192.168.252.1 manages the router and the hubs on subnet 172.16.46.0 across the backbone network
3
Network Management: Principles and Practice © Mani Subramanian 2000
Chapter 4
Managed Hub: System Information
Title: System Information: 172.16.46.2 Name or IP Address: 172.16.46.2 System Name System Description System Contact System Location System Object ID System Up Time : : 3Com LinkBuilder FMS, SW version:3.02 : : : .iso.org.dod.internet.private.enterprises.43.1.8.5 : (2475380437) 286 days, 12:03:24.37
Figure 4.2(a) System Information on 172.16.46.2 Hub
Notes
• Information obtained querying the hub • Data truly reflects what is stored in the hub • System Description and System Object ID are set at the factory and can’t be modified → read-only. • Time unit :1/100th of a second
Network Management: Principles and Practice © Mani Subramanian 2000
4
Chapter 4