Snmp - Report free essay sample

The objectives of this report are to provide the reader with a clearer understanding of network management, the concepts inherent in the Simple Network Management Protocol (SNMP), comparisons of SNMP with other network management protocols, how SNMPs are used in network management, and, finally, to provide the results of experiments carried out using several different modem configurations. SNMP is an internet-standard system of digital message format, or protocol, for managing devices on Internet Protocol (IP) networks. Routers, switches, servers, workstations, printers, modems are examples of such devices that support SNMP. It was introduced in 1988 to meet the growing need for managing Internet Protocol (IP) devices [2] and is used mostly in network management systems to monitor network-attached devices for conditions that warrant administrative attention. SNMP includes an application layer protocol, a database schema, and a set of data objects [1]. Network management is a general concept that employs the use of various tools and techniques, and systems to aid human beings in managing various devices, system, or networks. We will write a custom essay sample on Snmp Report or any similar topic specifically for you Do Not WasteYour Time HIRE WRITER Only 13.90 / page One such model of network management is called FCAPS, or Fault Management, Configuration Management, Accounting Management, Performance Management, and Security Management. Under the SNMP system and the FCAPS model, one or more administrative computers, called managers, are tasked to monitor and/or manage one or more pieces of software, called agents, which run on the network device. Specifically, the manager is a server which is running some kind of software system that can handle management tasks for a network. SNMP uses the User Datagram Protocol (UDP) as the transport protocol for passing data between managers and agents. The upside to the unreliable nature of UDP is that it requires low overhead, so the impact on the network’s performance is reduced. Management information is the operational parameters of SNMP-capable devices. The definition of managed objects can be broken down into three attributes: Name, Type and syntax, and Encoding. Managed objects are organized into a treelike hierarchy, this is the basis for SNMP’s naming scheme. Care must be taken when identifying managed objects or Object Identifiers (OIDs), across different versions of SNMP as there are enhancements to the naming scheme. Table of Contents Summary faults, collecting long term performance data, remote configuration of devices, and the remote control of a device. Another aspect of SNMP is network monitoring, or the monitoring of an entire network as opposed to individual routers, hosts, and other devices. This is called Remote Network Monitoring (RMON) and it can be used to monitor not only LAN traffic, but WAN interfaces as well. In the SNMP system, there are two kinds of entities: managers and agents. A manager is a server running some kind of software system that can handle management tasks for a network. Managers are often referred to as Network Management Stations (NMSs). An NMS is responsible for polling and receiving traps from agents in the network. A poll, in the context of network management, is the act of querying an agent (router, switch, Unix server, etc. ) for some piece of information. A trap, on the other hand, is a way for the agent to tell the NMS that something has happened. The agent is a piece of software that runs on the network devices that are being managed. It can be a separate program or it can be incorporated into the operating system. Today, most IP devices come with some kind of SNMP agent built in. The agent also provides management information to the NMS by keeping track of various operational aspects of the device. When the agent notices that something bad has happened, it can send a trap to the NMS, where it is handled appropriately. Figure 1: Relationship between an NMS and an Agent Network Management SNMP is really about network management. Network management is a general concept that employs the use of various tools, techniques, and systems to aid human beings in managing various devices, systems, or networks. One such model for network management is called FCAPS, or Fault Management, Configuration Management, Accounting Management, Performance Management, and Security Management. Fault management is used to detect, log, and notify users of systems or networks of problems as downtime of any kind is usually not acceptable. Fault management dictates that fault resolution first isolates the problem by using tools to determine symptoms, tries to resolve the problem, and then finally record the process that was used to detect and resolve the problem. Configuration management is used to monitor network and system configuration information so that the effects on network operation of various versions of hardware and software elements can be tracked and managed. This information generally is stored in a database of some kind. As configuration parameters change for systems, this database is updated. This data store can also aid in problem resolution. Accounting Management is used to ensure that computing and network resources are sued fairly by all groups or individuals who access them. Through this form of regulation, network problems can be minimized since resources are divided based on capacities. Performance management is used to measure and report on various aspects of network or system performance. Performance management usually starts when performance data is first gathered. Baseline levels are then established based on analysis of the data gathered. Finally, performance thresholds are established. A problem usually happens when these thresholds are exceeded. The last aspect of FCAPS is Security Management which is used to control access to some resources, such as a network and its hosts, and to help detect and prevent attacks that can compromise networks and hosts. Security management does not only involve network security systems but also physical security. This is usually accomplished through the use of various tools and systems such as firewalls, Intrusion Detection Systems (IDSs), Intrusion Prevention Systems (IPSs), antivirus systems and policy management. Applying the Concepts of Network Management The endeavor of network management involves solving a business problem through an implementation of some sort. The basic idea is to reduce costs and increase effectiveness. There are four different possible levels of activity when it comes to managing a specific service or device. Inactive, where no monitoring is being done, reactive, where a problem is dealt with only after it occurs, interactive, where components are monitored and interacted with to troubleshoot them, and finally, proactive, where the system provides a root-cause alarm then initiates predefined automatic restoral processes all while being monitored. However, the ability to monitor a service or system interactively or proactively begins with trend analysis and reporting. Accounting Accounting Security Security Performance Performance Fault Fault Configuration Configuration Network Management Network Management Change Management Change Management Proactive Proactive Inactive Inactive Reactive Reactive Interactive Interactive Trend Analysis Trend Analysis Response Time Reporting Response Time Reporting Alarm Correlation Alarm Correlation Figure 2: Concept of Network Management Trend Analysis and Reporting In general, the goal of trend analysis is to identify when systems, services, or networks are beginning to reach their maximum capacity, with enough lead time to do something about it before it becomes a real problem for end users. Trend analysis is aided by Response Time Reporting which measures how various aspects of the network (including systems) are performing with respect to responsiveness. To narrow down the many alerts and events into a single alert or several events that depict the real problem, Alarm Correlation is used. Alarm Correlation is also used to help operators know that an agent is indeed up and operational after being in a bad state. Trending also helps determine which device is constantly unreliable for investigation. The key to trouble resolution for the operator is knowing which information provided is valuable and can help resolve the problem. If possible, alerts and alarms should provide the operator with enough detail so that he or she can effectively troubleshoot and resolve a problem. However, in the event that the network is altered, planned or not, change management is used to prevent unreliable networks and systems, and ensure the correct level of notification with minimal user impact. The key steps for change management are: 1. Assigning a change controller. 2. Holding periodic change review meetings. Documenting change input requirements. 4. Documenting change output requirements. 5. Defining a change approval process. 6. Holding post-mortem meetings. 7. Developing an emergency change procedure. Subsequently, change planning is a process that identifies the risk level of a change and builds change planning requirements to ensure that the change is successful. The eight key steps for change planning are: 1. Assigning all potential changes a risk level prior to scheduling the change. 2. Documenting at least three risk levels with corresponding change planning requirements. Identifying risk levels for software and hardware upgrades, topology changes, routing changes, configuration changes, and new deployments. 4. Assigning higher risk levels to nonstandard add, move, or change types of activity. 5. Including lab validation, vendor review, peer review, and detailed configuration and design documentation. 6. Creating solution templates for deployments affecting multiple sites. 7. Including information about physical layout, logical design, configuration, software versions, acceptable hardware chassis and modules, and deployment guidelines. 8. Documenting network standards for configuration, software version, supported hardware, and DNS. Finally, caution must be taken when implementing a network management system as this can mean adding more staff to handle the increased load of maintaining and operating such an environment. On the other hand, this monitoring should reduce the workload of the system administration staff. The Structure of Management Information The Structure of Management Information (SMI) provides a way to define managed objects and their behavior. An agent has in its possession a list of the objects that it tracks.