Narayana Engineering College (AFFILIATED TO J.N.T.

U) NELLORE-524004
A TECHNICAL PAPER PRESENTATION ON
NETWORK MANAGEMENT SYSTEMS BY
Nazeer Basha.A 05711A1222, III B.Tech, IT Narayana Engineering college Nellore -524002 nazeer1222@gmail.com amaranath18@gmail.com A.V.S Amaranath 05711A1202, III B.Tech, IT Narayana Engineering college Nellore -524002

CONTENTS:
INTRODUCTION HISTORY NETWORK MANAGEMENT ARCHITECTURE FUNCTIONAL AREAS EXAMPLE SYSTEM FEATURES ADVANTAGES DISADVANTAGES CONCLUSION

ABSTRACT:

Service providers today face many challenges. Network topologies are growing more complex, new technologies for IP-based service delivery must be integrated into their networks, and customers are more demanding and fickle than ever before. One of the most important requirements for assuring the timely delivery of services without interruption is a network management system that is flexible enough to provide visibility within a complex network while anticipating network issues before customers become aware of them. Because today's network management systems require improved price/performance, high density and low power consumption, programmability for flexibility, systems. This Paper describes functions common to most network-management architectures and protocols. It also presents the five conceptual areas of management as defined by the International Organization for Standardization (ISO).Specific network management technologies, protocols, and platforms are also described in detail. modularity for scalability, and carrier-grade availability, modular communications platforms and AdvancedTCA* technology are ideal vehicles for such

INTRODUCTION

Network management means different things to different people. In some cases, it involves a solitary network consultant monitoring network activity with an outdated protocol analyzer. In other cases, network management involves a distributed database, auto polling of network devices, and high-end workstations generating real-time graphical views of network topology changes and traffic. In general, network management is a service that employs a variety of tools, applications, and devices to assist human network managers in monitoring and maintaining networks. A Network Management System (NMS) is a combination of hardware and software used to monitor and administer a network. A group of interconnected network elements form a network. Individual network elements (NEs) in a network are managed by an element management system. A network element (NE) is telecommunications hardware equipment that is addressable and manageable. NEs provide support or services to the user and can be managed through an element manager (EMS). It is related to OSS (Operation and Support System). A network element is a combination of hardware and software that primarily performs a telecommunications service function. Telecommunication is the transmission of signals over a distance for the purpose of communication. An element management system (EMS) manages one or more of a specific type of network elements (NEs). An EMS allows the user to manage all the features of each NE individually, but not the communication between NEs - this is done by the network management system (NMS).

HISTORY

The early 1980s there was a tremendous expansion in the area of network deployment. As companies realized the cost benefits and productivity gains created by network technology, they began to add networks and expand existing networks almost as rapidly as new network technologies and products were introduced. By the mid-1980s, certain companies were experiencing growing pains from deploying many different and incompatible network technologies. The problems associated with network expansion affect both day-to-day network operation management and strategic network growth planning. Each new network technology requires its own set of experts. In the early 1980s, the staffing requirements alone for managing large, heterogeneous networks created a crisis for many organizations. An urgent need arose for automated network management (including what is typically called network capacity planning) integrated across diverse environments. Network Management Architecture Most network management architectures use the same basic structure and set of relationships. End stations (managed devices), such as computer systems and other network devices, run software that enables them to send alerts when they recognize problems (for example, when one or more user-determined thresholds are exceeded). Upon receiving these alerts, management entities are programmed to react by executing one, several, or a group of actions, including operator notification, event logging, system shutdown, and automatic attempts at system repair. Management entities also can poll end stations to check the values of certain variables. Polling can be automatic or user-initiated, but agents in the managed devices respond to all polls. Agents are software modules that first compile information about the managed devices in which they reside, then store this information in a management database, and finally provide it (proactively or reactively) to management entities within network management systems (NMSs) via a network management protocol. Well-known network management protocols include the Simple Network Management Protocol (SNMP) and

Common Management Information Protocol (CMIP). Management proxies are entities that provide management information on behalf of other entities. Figure depicts a typical network management architecture maintaining many relationships

The architecture consists of the following elements:

Network Management Station(s): The network management station runs the

network management application4 that gathers information about managed devices from the management agent5 which resides within a managed device. The network management application typically must process large amounts of data, react to events, and prepare relevant information for display. It usually has a control console with a GUI interface which allows the operator to view a graphical representation of the network, control managed devices on the network and program the network management application. Some network management applications can be programmed to react to information collected from management agents and/or set thresholds with the following actions:
o

Perform tests and automatic corrective actions (reconfiguration, shutdown of a managed device)

o o

Logging network events Present status information and alerts to operator

Managed Devices: A managed device can be any type of node residing on a network, such as a computer, printer or router. Managed devices contain a management agent.

Management agents: Provides information about the managed device to the network management application(s) and may also accept control information. Network management protocol: Protocol used by the network management application(s) and the management agent to exchange management information. Management Information: The information that is exchanged between the network management application(s) and the management agents that allows the monitoring and control of a managed device.

The two most common network management protocols are the

Simple Network Management Protocol (SNMP) Common Management Information Protocol (CMPI)

SNMP: SNMP is a communication specification that defines how management information is exchanged between network management applications and management agents. SNMP is by far the most widely used network management protocol and use is widespread in LAN environments. CMPI: CMIP is a well designed protocol that defines how network management information is exchanged between network management applications and management agents. It uses an ISO reliable connection-oriented transport mechanism and has built in security that supports access control, authorization and security logs. The management information is exchanged between the network management application and management agents thru

managed objects. Managed objects are a characteristic of a managed device that can be monitored, modified or controlled and can be used to perform tasks. CMIP is used extensively in telecommunication environments, where networks tend to be large and complex. The major advantages of CMIP over SNMP are :

CMIP variables not only relay information, but also can be used to perform tasks. This is impossible under SNMP. CMIP is a safer system as it has built in security that supports authorization, access control, and security logs. CMIP provides powerful capabilities that allow management applications to accomplish more with a single request. CMIP provides better reporting of unusual network conditions.

FUNCTIONAL AREAS: Performance Management The goal of performance management is to measure and make available various aspects of network performance so that internetwork performance can be maintained at an acceptable level. Examples of performance variables that might be provided include network throughput, user response times, and line utilization. Performance management involves three main steps. First, performance data is gathered on variables of interest to network administrators. Second, the data is analyzed to determine normal (baseline) levels. Finally, appropriate performance thresholds are determined for each important variable so that exceeding these thresholds indicates a network problem worthy of attention. Management entities continually monitor performance variables. When a performance threshold is exceeded, an alert is generated and sent to the network management system.

Each of the steps just described is part of the process to set up a reactive system. When performance becomes unacceptable because of an exceeded user-defined threshold, the system reacts by sending a message. Performance management also permits proactive methods: For example, network simulation can be used to project how network growth will affect performance metrics. Such simulation can alert administrators to impending problems so that counteractive measures can be taken. Configuration Management The goal of configuration management is 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. Each network device has a variety of version information associated with it. An engineering workstation, for example, may be configured as follows: Operating system, Version 3.2 Ethernet interface, Version 5.4 TCP/IP software, Version 2.0

Configuration management subsystems store this information in a database for easy access. When a problem occurs, this database can be searched for clues that may help solve the problem.

Accounting Management

The goal of accounting management is to measure network utilization parameters so that individual or group uses on the network can be regulated appropriately. Such regulation minimizes network problems (because network resources can be apportioned based on resource capacities) and maximizes the fairness of network access across all users. As with performance management, the first step toward appropriate accounting management is to measure utilization of all important network resources. Analysis of the results provides insight into current usage patterns, and usage quotas can be set at this point. Some correction, of course, will be required to reach optimal access practices. From this point, ongoing measurement of resource use can yield billing information as well as information used to assess continued fair and optimal resource utilization. Fault Management The goal of fault management is to detect, log, notify users of, and (to the extent possible) automatically fix network problems to keep the network running effectively. Because faults can cause downtime or unacceptable network degradation, fault management is perhaps the most widely implemented of the ISO network management elements. Fault management involves first determining symptoms and isolating the problem. Then the problem is fixed and the solution is tested on all-important subsystems. Finally, the detection and resolution of the problem is recorded. Security Management The goal of security management is to control access to network resources according to local guidelines so that the network cannot be sabotaged (intentionally or unintentionally) and sensitive information cannot be accessed by those without appropriate authorization. A security management subsystem, for example, can monitor users logging on to a network resource and can refuse access to those who enter inappropriate access codes.

Security management subsystems work by partitioning network resources into authorized and unauthorized areas. For some users, access to any network resource is inappropriate, mostly because such users are usually company outsiders. For other (internal) network users, access to information originating from a particular department is inappropriate. Access to Human Resource files, for example, is inappropriate for most users outside the Human Resources department. Security management subsystems perform several functions. They identify sensitive network resources (including systems, files, and other entities) and determine mappings between sensitive network resources and user sets. They also monitor access points to sensitive network resources and log inappropriate access to sensitive network resources. EXAMPLE SYSTEM: The following diagram shows a reference architecture that Cisco Systems believes should be the minimal solution for managing a data network. This architecture includes a Cisco Call Manager server for those who plan to manage Voice over Internet Protocol (VoIP): The diagram shows how you would integrate the Call Manager server into the NMS topology.

The network management architecture includes the following:

Simple Network Management Protocol (SNMP) platform for fault management

Performance monitoring platform for long term performance management and trending CiscoWorks2000 server for configuration management, syslog collection, and hardware and software inventory management

Some SNMP platforms can directly share data with the CiscoWorks2000 server using Common Information Model/extensible Markup Language (CIM/XML) methods. CIM is a common data model of an implementation-neutral schema for describing overall management information in a network/enterprise environment. CIM is comprised of a specification and a schema. The specification defines the details for integration with other management models such as SNMP MIBs or Desktop Management Task Force Management Information Files (DMTF MIFs), while the schema provides the actual model descriptions. XML is a markup language used for representing structured data in textual form. A specific goal of XML was to keep most of the descriptive power of SGML whilst removing as much of the complexity as possible. XML is similar in concept to HTML, but whereas HTML is used to convey graphical information about a document, XML is used to represent structured data in a document. Cisco's advanced services customers would also include Cisco's NATkit server for additional proactive monitoring and troubleshooting. The NATkit server would either have a remote disk mount (rmount) or file transfer protocol (FTP) access to the data residing on the CiscoWorks2000 server.

FEATURES: The key features that any network management system must have.

 One simple interface: Everything that you need to see should be easily accessible. There should be no need to switch between screens to gather information. Look for a network management system that utilizes a Web-based interface that can be customized for different administrators.

Ability to set a baseline: To report errors and security-related events, the network management system needs to be able to recognize normal network operations through an established baseline. The ability to distinguish between normal and abnormal events cuts down on the false positive reports.

Reporting of actionable information: Simply stated, if your network management system can report an event to you, it should also have the tools to act upon that information. If your system flags a spike in abnormal traffic, that same screen should also have the information/tool to deal with it at well.

Auto discovery: This discovers computers and components on your IT infrastructure without input from a person. It sends a packet to various devices on the network, and when a packet is acknowledged, an event in the management system is raised. Certain systems enhance this feature by visually mapping all of the components on the network or exporting/importing data to/from Excel spreadsheets or XML files.

Configuration import and analysis: Configuring and optimizing a network can take hundreds of hours, and one wrong setting can lose all of your previous work. An import and analysis feature lets you seamlessly integrate existing configurations and device policies into your network. It should also let you return your configuration to its original settings.

Policy-based configuration & deployment: An effective network management system should save you time, and this feature is designed to do just that. By writing one policy that can be applied to multiple devices, time and resources can be spent on other tasks. The ability to write policies from preexisting templates can also be useful.

Once policies are in place, it's also helpful to be able to update or change them with little interruption. Some tools let you update a policy simultaneously on all the devices on a network that subscribe to that policy. The ability to set specific update times is important, as you can set update times to coincide with periods of low network traffic.

Policy-based auditing: The auditing process periodically confirms that all the configurations put into place meet the standards that have been set for the network. It also detects errors and inconsistencies across the network. A nice feature is the ability to send alerts to e-mail or cell phones.

ADVANTAGES: Network management systems range from free, open-source tools such as OpenNMS to the pricey HP Open View. They can be extremely powerful, complex and sophisticated. So it's important to choose the right tool for the job . Choosing a network management system hinges not only on price and user preference, but functionality as well. DISADVANTAGES Usage Considerations A considerable amount of time is usually required to effectively deploy and learn to use network management software. This is because network managers must be extremely familiar with the network management protocol and the data structures associated with the network management information. Network management protocols and the data structures associated with the network management information are typically complex.

Many network management implementations do not provide support for network devices which use vendor specific protocols. A network management system for a small isolated network may not be cost effective or needed. This of course depends on functionality, reliability and performance requirements of the network and attached systems. Maturity Network management software often lacks the functionality needed to effectively manage a network. Some of this can be attributed to the deficiencies in the network management protocols. Numerous network management packages are available from a wide variety of vendors. Some packages are simple and provide network management facilities for a single network; others can be complex and handle multiple types of networks. New products and enhancements to existing network management packages are announced frequently. Costs and Limitations Network management systems can be quite expensive, and are often complex. Personnel with specialized training are often required to effectively configure, maintain and operate the network management system. CONCLUSION: Finally, we conclude that, computer networks began to grow and be interconnected. As the size of these networks grew, they became harder to manage and maintain, thus the need for network management was realized. One of the oldest forms of network management is the use of the remote login to monitor or configure a network device; however, today more sophisticated network management tools are available. Network

management is a requirement for anyone who wants to control and monitor their networks.