NMS Course Modified)

Network Management Systems (elective)
B.TECH IV-IT Department of INFORMATION TECHNOLOGY
Course File
LECTURE & MICRO PLAN

1.1 Introduction to the Subject Network Management Systems: A Network Management System (NMS) is a
combination of hardware and software used to monitor and administer a network.. Individual Network Elements (NEs) in a network are managed by an element management system..
NMS systems make use of various protocols for the purpose they serve. For example, SNMP protocol allows them to simply gather the information from the various devices down the network hierarchy. NMS software is responsible for identification of a problem, the exact source(s) of the problem, and solving them. NMS systems not only are responsible for the detection of faults, but also for collecting device statistics over a period of time. An NMS may include a library of previous network statistics along with problems and solutions that were successful in the pastuseful if faults recur. NMS software can then search its library for the best possible method to resolve a particular problem. An NMS manages the Network Elements. These elements or devices are managed by the NMS, so these devices used to call as managed devices. Device management includes Faults, Accounting, Configuration, Performance, and Security (FCAPS) management. Each of these five functions is specific to an organization, but the basic idea to manage these devices is FCAPS.
1.2 Objectives of the subject:

This course presents an overview of networking and network management. It addresses network management architectures and protocols, focuses on tools and systems for monitoring and managing networks, systems, applications and services. Explains the basic foundations of standards, models, and language, which are needed to build various network management architectures and protocols. Gives the concept of SNMP protocol, Telecommunication Management Network, Remote Monitoring, Web-based Management system and tools that monitor the NMS.

Course File
1.3. JNTU Syllabus with Additional Topics

Sl.No Unit No 1 Topic Data Communication and Network Management Overview: Analogy of Telephone Network Management Communications and Protocol Standards, Case Histories of Networking and Management, Challenges of Information Technology Managers Network Management: Goals, Organizations , and Functions, Network and System Management, Network Management System Platform Current status and future of Network Management 2 2 SNMPV1 Network Management: Organization and Information and Information Models Managed Network: Case Histories and Examples, The history of SNMP Management, The SNMP Model, The Organizational Model System Overview, The Information Model 3 3 SNMPV1 Network Management: Communication and Function Models The SNMP Communication Model Functional Model SNMP Management:SNMPV2:Major Changes in SNMPV2, SNMPV2 System Architecture, SNMPV2 Structure of Management Information
2
Additional Topic

Course File
The SNMPV2 Management Information Base SNMPV2 Protocol, Compatibility with SNMPV1 5 5 SNMP Management RMON: What is Remote Monitoring? RMON, SMI and MIB, RMON1, RMON2 ATM Remote Monitoring, A case study of Internet Traffic using RMON 6 6 Telecommunications Management Network: Why TMN? Operations Systems, TMN Conceptual Models TMN Standards, TMN Architecture, TMN Management Service Architecture An Integrated view of TMN, Implementation issues Network Management Tools and Systems: Network Statistics Measurement Systems, History of Enterprise Management, Network Management Systems Commercial Network Management Systems System Management, Enterprise Management Solutions Web-Based Management: NMS with web interface and Web-Based Management, Web interface to SNMP Management, Embedded Web based management, Desktop Management Interface Web-Based Enterprise Management, WBEM: Windows Management Instrumentation, Java Management Extensions, Management of Storage Area Network, Future Directions

Course File
1.4 Sources of Information 1.4.1 Text Books 1. Network Management, Principles and Practice, Mani Subramanian, Pearson Education. 1.4.2 Reference Text Books
1. Network management, Morris, Pearson Education. 2. Principles of Network System Administration, Mark Burges, Wiley Dreamtech. 3. Distributed Network Management, Paul, John Wiley.
Websites 1. http://www.spiceworks.com/it-articles/network-management-system/
2. http://www.wisegeek.com/what-is-network-management.htm
3.http://www.tcpipguide.com/free/t_NameSystemsNameRegistrationandNameResolu tionTCPIPD.htm
4 http://gabrielstein.org/blog/?p=22

B.TECH IV-IT Department of INFORMATION TECHNOLOGY 1.4.4. Journals; 1. 2. 3.
Course File
1.5.Unit wise Summary

Sl. No 1 Unit No 1 Total Periods Topic Data Communications & Network Management overview, analogy of telephone network management Communication protocols and standards, case histories of networking and management Network managemen t overview BB PPT Reg/Additio nal LCD/O HP/BB Remark
15
Challenges of Information Technology managers
Network Management: Goals, organization and functions, network and system management Network management system and platform , current status and future of network management SNMPV1 network management organization and information models, Managed Network: Case histories and Examples, The history of SNMP Management SNMP Model: The Organization model, System Overview The Information Model 3 3 SNMP PPT
SNMPV1: Network Management Communication and Functional Models The SNMP Communication and Functional Model 5

Course File
SNMPV2: Major changes in SNMPV2,SNMPV2 System Architecture. SNMPV2: System Architecture, SNMPV2->Structure of management, information, snmpv2,Abstract syntax notation concept. SNMPV2 protocol, compatibility with SNMPV1
Network management systems:- Remote monitoring. RMON SMI and MIB, RMON1, RMON2. ATM Remote monitoring; A Case study of internet traffic using RMON.
Telecommunication Management Networking; Why TMN, operation system, TMN conceptual model. TMN conceptual model, TMN standards, TMN Artichecture. TMN Architecture, TMN standards. NMS-Networks management Tools, Network statistics measurement system, history of enterprise management. NMS: Commercial NMS, system management. Enterprise management solutions.
Web-based management NMS with web interface. Web interface to SNMP,Embedded Web based management, Data management interface WB enterprise Manager Web based enterprise management.

B.TECH IV-IT Department of INFORMATION TECHNOLOGY Windows Manager Installation. Java management extension. Management of storage area networks, future directions.
Course File
1.6.Micro plan
Sl. Unit Date No No 1 Topic to be covered in one lecture
Data communications and network management overview. Analogy of telephone networking management.
Reg/Addi LCD/ tional OHP/ BB PPT
Remark
1 1 1 1 1 1 1 1 1 1
6.12.10
2 3 4 5 6 7 8 9 10
Communication protocols and standards
7.12.10
Communication protocols and standards Case histories of networking and management.
15.12.10
Challenges of information technology managers, Challenges of information technology managers,
21.12.10
Network management: Goals, Organization and functions., Network management: Goals, Organization and functions.,
27.12.10
Networking and system management.

Course File
11 12 13 14 15 16 17 18 19 18 20 21
1 1 1 1 1 2 2 2 2 2 2 3 3 4 4 4
25.1.11 24.1.11 18.1.11 11.1.11 10.1.11 4.1.11 3.1.11
Networking and system management. Network management system and platform Network management system and platform Current status and future of network management. Current status and future of network management. SNMPV1 Network management organization and Information models. SNMPV1 Network management organization and Information models SNMPV1 Network management organization and Information models SNMPV1 Network management organization and Information models
PPT
SNMP model The organization model, system over view Information model. SNMPV 1 Networking management communication an functions models. The SNMP communication and Functional model.
SNMPV2:Major changes in SNMP2. SNMPV2 system architecture. SNMPV2 System Architecture
PPT
22 23 24 25
PPT

Course File
26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44
4 4 4 4 5 5 5 5 5 5 5 6 6 6 6 6 6 6 6
01.3.11 28.2.11 21.2.11 15.2.11 14.2.11 07.2.11 08.2.11
SNMPV2Structure of management, Information.
SNMPV2 Abstract Syntax notation concept.

SNMPV2 protocol,compability with SNMPV1.
Network management systems

Remote monitoring. RMON SMI and MIB, RMON1, RMON2. RMON SMI and MIB, RMON1, RMON2. RMON SMI and MIB, RMON1, RMON2.
PPT
ATM Remote Monitoring. A case study of internet traffic using RMON.

Telecommunication management Network: Why TMN? Operation Systems TMN conceptual model. TMN conceptual model TMN standards
PPT
TMN Architecture TMN Architecture TMN Standards

9

Course File
PPT
45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
7 7 7 7 7 7 7 7 7
8 8 8 8
07.3.11
NMS Networking management Tools Network statistics measurement system. History of enterprise management. NMS: Commercial NMS, system management. NMS: Commercial NMS, system management. NMS: Commercial NMS, system management. NMS: Commercial NMS, system management.
08.3.11
Enterprise Management solutions Enterprise Management solutions Web-based management NMS with web interface. Web-based management NMS with web interface.
PPT
11.3.11
Web interface to SNMP, Embedded Web based management Data management interface WB enterprise Manager Web based enterprise management.
8 8
16.3.11 16.3.11
Windows Manager Installation. Java management extension. Management of storage area networks, future directions.
10

B.TECH IV-IT Department of INFORMATION TECHNOLOGY Revision of Old question papers Revision of Old question papers Revision of Old question papers Revision of Old question papers
Course File
1.7. Subject Contents
1.7.1. Synopsis page for each period (62 pages)
1.7.2. Detailed Lecture notes containing
1.PPTS
2.OHP slides
3.Subjective type questions (approximately 5 to 8 /unit)
4.Objective type questions (approximately 20 to 30 /unit
5.Any simulations
11

B.TECH IV-IT Department of INFORMATION TECHNOLOGY 1.8. Course Review (By the concerned Faculty):
Course File
(i) Aims
(ii) Sample Check
(iii)End of the course report by the concerned faculty
GUIDELINES:
Distribution of periods: No. of Classes required to cover JNTU syllabus No. of Classes required to cover Additional topics No. of Classes required to cover Assignment tests No. of Classes required to cover tutorials No. of Classes required to cover Mid tests revision No. of Classes required to solve University Question papers Total periods :40 :2 :4 :8 :2 :4 : --------60
12

Course File
Geethanjali College of Engineering and Technology

DEPARTMENT OF INFORMATION TECHNOLOGY (Name of the Subject/Lab Course): Network Management Systems (JNTU CODE: Branch: Year: ) Programme: UG/PG Version No: Updated on:23/10/2010 No. of Pages: 60
INFORMATION TECHNOLOGY 2010-11
Semester: IV-IT Classification status (Unrestricted/Restricted ) Distribution List:
Prepared by : 1) Name : 2) Sign : ASSISTANT PROFESSOR Y.KETHAN HARISH
3) Design : 4) Date :
Verified by : 1) Name : 2) Sign :
*For Q.C only 1)Name 2) Sign 3) Design : 4) Date : : :
3) Design : 4) Date :
Approved by (HOD) : 1) Name: 2) Sign : 3) Date :
13

Course File
Geethanjali College of Engineering and Technology

CHEERYAL (V), KEESARA (M),R R (Dist).
Department Information Technology Course File

Name of the Subject:
NETWORK MANAGEMENT SYSTEMS IV IT 2nd Semester
Year & Semester to Whom Subject is offered: Prepared by (Name of the Faculty): Designation:
Y.KETHAN HARISH
ASSISTANT PROFESSOR
Introduction to Subject:
Network Management Systems: A Network Management System (NMS) is a combination of hardware and software used to monitor and administer a network.. Individual Network Elements (NEs) in a network are managed by an element management system.
NMS systems make use of various protocols for the purpose they serve. For example, SNMP protocol allows them to simply gather the information from the various devices down the network hierarchy. NMS software is responsible for identification of a problem, the exact source(s) of the problem, and solving them. NMS systems not only are responsible for the detection of faults, but also for collecting device statistics over a period of time. An NMS may include a library of previous network statistics along with problems and solutions that were
14

Course File
successful in the pastuseful if faults recur. NMS software can then search its library for the best possible method to resolve a particular problem. An NMS manages the Network Elements. These elements or devices are managed by the NMS, so these devices used to call as managed devices. Device management includes Faults, Accounting, Configuration, Performance, and Security (FCAPS) management. Each of these five functions is specific to an organization, but the basic idea to manage these devices is FCAPS.
Objectives of the Subject:

This course presents an overview of networking and network management. It addresses network management architectures and protocols, focuses on tools and systems for monitoring and managing networks, systems, applications and services. Explains the basic foundations of standards, models, and language, which are needed to build various network management architectures and protocols. Gives the concept of SNMP protocol, Telecommunication Management Network, Remote Monitoring, Web-based Management system and tools that monitor the NMS.
Course Objectives

To identify and explain the core elements of computer networks and the Internet. To understand the fundamentals of network management in metropolitan and core networks reviewing relevant protocols and techniques. To work with open source applications that deal with database and website development. To explain the fundamental principles and mechanisms of network infrastructure. To identify the key protocols of TCP/IP and explain how they enable the common Internet applications in use today. To design and develop basic network applications. To develop the capability to perform network programming using sockets.
15

Course File
Course Outcomes
Graduate will get ability to:
Understand a range of underlying principles and techniques in developing, designing and marketing network applications. Understand of the underlying principles of computer networks. Write programs for developing network applications. Evaluate different network design strategies; compose digital design, design for the market, and design in a global environment.
Mapping of course objectives with outcomes

Course Objectives I II III IV V VI VII a b Course Outcomes c d
16

Course File
SYLLABUS
UNIT-I Data communications and Network Management Overview : Analogy of Telephone Network Management, Communications protocols and Standards, Case Histories of Networking and Management, Challenges of Information Technology Managers, Network Management: Goals, Organization, and Functions, Network and System Management, Network Management System Platform, Current Status and future of Network Management. UNIT-II SNMPV1 Network Management: Organization and Information Models. Managed network: Case Histories and Examples, the History of SNMP Management, The SNMP Model, The Organization Model, System Overview, The Information Model. UNIT-III SNMPv1 Network Management: Communication and Functional Models. The SNMP Communication Model, Functional model UNIT-IV SNMP Management: SNMPv2 : Major Changes in SNMPv2, SNMPv2 System Architecture, SNMPv2 Structure of Management Information, The SNMPv2 Management Information Base, SNMPv2 Protocol, Compatibility With SNMPv1 UNIT-V SNMP Management: RMON: What is Remote Monitoring? , RMON SMI and MIB, RMON1, RMON2, ATM Remote Monitoring, A Case Study of Internet Traffic Using RMON UNIT-VI Telecommunications Management Network: Why TMN? Operations Systems, TMN Conceptual Model, TMN Standards, TMN Architecture, TMN Management Service Architecture, An Integrated View of TMN, Implementation Issues.
17

Course File
UNIT-VII Network Management Tools and Systems: Network Management Tools, Network Statistics Measurement Systems, History of Enterprise Management, Network Management systems, Commercial Network management Systems, System Management, Enterprise Management Solutions. UNIT-VIII Web-Based Management : NMS with Web Interface and Web-Based Management, Web Interface to SNMP Management, Embedded Web-Based Management, Desktop management Interface, Web-Based Enterprise Management, WBEM: Windows Management Instrumentation, Java management Extensions, Management of a Storage Area Network: , Future Directions TEXT BOOK : 1. Network Management, Principles and Practice, Mani Subramanian, Pearson Education. REFERENCES: 1. Network management, Morris, Pearson Education. 2. Principles of Network System Administration, Mark Burges, Wiley Dreamtech. 3. Distributed Network Management, Paul, John Wiley.
COURSE OVERVIEW This course presents an overview of networking and network management. It addresses network management architectures and protocols, focuses on tools and systems for monitoring and managing networks, systems, applications and services, Explains the basic foundations of standards, models, and language, which are needed to build various network management architectures and protocols. Gives the concept of SNMP protocol, Telecommunication Management network, Remote Monitoring, Web-based Management system and tools that monitor the NMS.
18

Course File
UNIT-I OVERVIEW: Unit-1 demonstrates the necessity of network and system management in providing information technology services. Gives the history of computer communication, walks through some realworld case histories, and then present an overview of network and system management. Successive management of telephone network and its usage in Computer communications is explained. Information about the internet, importance of communication protocols and standards. Functional groups that perform the functions Engineering, Operations, and Installation and Maintenance (I & M). This unit focuses on the network management system goals and relationships among its various components. CONTENTS: Data Communications and Network Management Overview 1.1) 1.2) 1.3) 1.4) 1.5) Analogy of Telephone Network Management Data and Telecommunication Network Distributed Computing Environments TCP/IP- Based Networks : The Internet and Intranets Communications Protocols and Standards 1.5.1) Communication Architectures 1.5.2) Protocol Layers and Services 1.6) Case Histories of Networking and Management 1.6.1) Case History 1: The Importance of Topology 1.6.2) Case History 2: Filtering Does Not Reduce on Node 1.6.3) Some Common Network Problems
1.7) 1.8)
Challenges of Information Technology Managers Network Management: Goals, Organization, and Functions 1.8.1) Goals of Network Management 1.8.2) Network Provisioning
19

Course File
1.8.3) Network Operations and NOC 1.8.4) Network Installation and Maintenance 1.9) Network and System Management
1.10) Network Management System Platform 1.11) Current Status and Future of Network Management Definition of NMS: Network Management Systems: A Network Management System (NMS) is a combination of hardware and software used to monitor and administer a network.. Individual Network Elements (NEs) in a network are managed by an element management system. In this unit an overview of data and telecommunication networks and how these networks are managed. The telephone network was shown as a model to be followed in accomplishing a reliable, dependable, and quality data communication network. Differences between data communication and telecommunication networks, although this distinction is fast disappearing. The desktop processors and LAN technology have contributed to the client/server distributed computing environment, which has changed the direction of data communication. Adoption of standards has played a significant part in the popularity of the Internet. The OSI and Internet protocols are very important in data communication today. This unit describes how network components and networks are managed by network management systems. The concept of network management to managing networks and systems and all of IT services is extended. IT management is undergoing changes due to the advancement in software and information technology. Analogy of Telephone network management: The need for data or computer communication network management is best illustrated by an analogy of telephone network management. The telephone network is reliable and dependable, and the quality and speed of the connection is good. The reason for such reliability, dependability, and quality is more than the careful planning, design, and implementation of a good telephone network using good reliable components. The analogy of the telephone network is very well explained by the following Teelphone network model.
20

Course File
To other Regional centers Sectional centers Primary centers Toll centers End offices To other Primary centers Toll centers End offices To other Class 4 toll points End offices
Regional Center Class 1 switch
Regional Center Class 1 switch
Sectional Center Class 2 switch
Sectional Center Class 2 switch
Primary Center Class 3 switch
Primary Center Class 3 switch
Toll Center Class 4 switch
Toll Center Class 4 switch
End Office Class 5 switch
End Office Class 5 switch Legend: Loop Direct Trunk Toll-Connecting Trunk
Voice
Voice
Toll Trunk
Figure 1.1 Te le phone Ne twork M ode l
Operation Systems/NOC Monitor telephone network parameters o S/N ratio, transmission loss, calls blockage, etc. Real-time management of network Trunk (logical entity between switches) maintenance system measures loss and S/N. Trunks not meeting QoS are removed before customer notices poor quality Traffic measurement systems measure call blockage. Additional switch planned to keep the call blockage below acceptable level Operations systems are distributed at central offices Network management done centrally from Network Operations Center (NOC)
21

Course File
Data (computer) and Telecommunication Network Computer data is carried over long distance by telephone (telecommunication network) Output of telephone is analog and output of computers is digital Modem is used to modulate and demodulate computer data to analog format and back Clear distinction between the two networks is getting fuzzier with modern multimedia networks Distributed Computing Environments: Any work station can communicate with any host on the LAN; depending upon the type of LAN, there can be large number of workstations and hosts. DTEs (any digital terminal equipment that generates and processes digital data) connected to different LANs that are geographically far apart can communicate via a telecommunication network, either public or private switched. The system of links that connect remote LANs is called wide-area network (WAN). A LAN is physically connected to a WAN link by a bridge or router at each end.
The first aspect is the question
22

Course File
Subjective Questions: 1) What are the goals of the Network Management? 2) What are the challenges of Information Technology Managers? 3) Explain about the communication protocol and standards in the Communication Architectures? 4) Describe the Network and System Management? 5) Write about some common Network Problems? 6) Write about the perspectives of Network Managers? Objective Questions: 1) The functions of Network operations are a) Fault Management b) Trouble Ticket Administration c) Configuration Management d) Security Management e) Performance Management f) Accounting Management 2) The current form of Network Management Systems is based on SNMP 3) Computer communication technology radically changed with the advent of desktop computing power and distributed computing environments using local-area networks 4) DTE stands for Data Terminal Equipment 5) Data can be transmitted in either analog or digital format. 6) ISDN stands for Integrated Services Digital Network 7) IBM developed a communication architecture for data communication control network which is called System Network Architecture(SNA) 8) The complement to TCP is the User Datagram Protocol (UDP). 9) Architecture can be defined as the basic structure of a system that shows its functional components and the relationships among them. 10) ITU stands for International Telecommunication Union 11) A router, or a routing bridge, at the nodes of a network performs the function of routing and switching the data. 12) A common syntax that is used for semantics is Abstract Syntax Notation Number One(ASN.1) in the protocol communication 13) SMTP stands for Simple Mail Transfer Protocol 14) The most common and serious problems of networks are connectivity failures which are in the category of fault management. 15) Fault is generally interpreted to mean failures in accessing networks and systems by the users.
23

Course File
16) The network I & M group takes care of all installation and maintenance of equipment and cables. 17) MIB stands for Management Information Base. 18) A network management system manages all the components that are connected to a network. 19) The communication between two NMS components takes place through Network Agents 20) The SNMP-based management is a polling-based system.
UNIT-II OVERVIEW: Unit-II gives an overview about the organization and information aspects of SNMP management. The historical development of SNMP standards and documents are briefly reviewed. SNMP management is organized as a two-tier management, in which a manager process and agent process communicate with each other. The agent process resides in the network element. The manager process is built into network management stations. All the management operations are done using the five messages in SNMPv1 which is explained in the unit. Other concepts related to SNMP v1 are Structure of Management Information (SMI) which is a message specification based on which messages are exchanged. The syntax uses Abstract Syntax Notation 1(ASN.1) and encoding is done using the basic encoding rules (BER) are also discussed in this chapter. The other topics like scalar objects, Management Information Base (MIB) a virtual database where managed objects are organized and MIB groups were included. CONTENTS: SNMPv1 Network Management: Organization and Information Models 2.1) Managed Network: Case Histories and Examples 2.2) The History of SNMP Management
24

Course File
2.3) Internet Organizations and Standards 2.3.1) Organizations 2.3.2) Internet Documents 2.4) The SNMP Model 2.5) The Organization Model 2.6) The Information Model 2.6.1) Introduction 2.6.2) The structure of Management Information 2.6.3) Managed Objects 2.6.4) Management Information Base
The History of SNMP Management: SNMP stands for Simple Network Management Protocol and its management began in the year 1970s. Internet Control Message Protocol (ICMP) was developed to manage ARPANET. The ARPANET which started in the year 1969 was developed into the Internet with the advent of UNIX and the popularization of client/server architecture. National Science Foundation officially dropped the name ARPANET and adopted the name Internet. An Internet Advisory Board (IAB) was formed to administer Internet activities. With the growth of the Internet, it became essential to have the capability to monitor and configure gateways remotely. The Simple Gateway Monitoring Protocol (SGMP) was developed for this purpose as an interim solution. The Internet Advisory Board recommended the development of SNMP, which is an enhancement of SGMP. Even SNMP was intended to be another solution, with the long-term solution being migration to the OSI standard CMIP/CMIS. SNMPv2 was developed to make it independent of the OSI standard, as well as to add features of SNMPv2 has only partially overcome some of the limitations of SNMP. The final version of the SNMPv2 was released without one of the major enhancements on its security feature. Internet Organizations and Standards Organizations
25

Course File
The Internet Advisory Board (IAB) recommended the development of SNMP. The IAB was founded informally in 1983 by researchers working on TCP/IP networks. Its name was changed from the Internet Advisory Board to the Internet Architecture Board in 1989 and it was charged with the responsibility to manage two task force-the Internet Engineering Task Force (IETF) and the Internet Research Task Force (IRTF). With the growth of the Internet, the IETF has grown to be the protocol engineering, development, and standardization arm of the IAB. The Inter NIC (Internet Network Information Center) is an organization that maintains several archives of documents related to the Internet and the IETFs activities. The archives include, among other documents, Request for Comments (RFC), Standard RFC (STD), and For Your Information RFC (FYI). Internet Documents: Originally RFC was just the name implies, a Request for Comments. The early RFCs were messages between the ARPANET architects about how to resolve certain problems. The three forms of Internet Documents are 1) Request for Comments (RFC) 2) IETF STD Internet Standard 3) FYI For Your Information Source for RFCs http://www.nic.mil/dodnic/RFC/ http://www.rfc-editor.org/rfc.html The SNMP Model: The SNMP Model is comprises of three types. 1) The Organization Model 2) The Information Model 3) The Communication Model The Organization Model: The initial organization model of SNMP management is a simple two-tier model. It consists of a network agent process, which resides in the managed object. It gives the relationship between network element agent and manager. Both the manager and the agent are software modules. Two-Tier Organization Model
26

Course File
SNMP Manager SNMP Manager
SNMP Manager
SNMPAgent Network Element
Network Agent Network Element
(a) One M anage r - One Age nt M ode (b) M ultiple M anage rs - One Age nt M ode l l
Three-tier Organization Model (RMON)

SNMP Manager
Managed object comprises network element and management agent RMON Probe RMON acts as an agent and a manager
Managed Objects
RMON (Remote Monitoring) gathers data from MO, analyses the data, and stores the data Communicates the statistics to the manager
Three-tier Organization Model (Proxy Server):
SNMP Manager
Proxy Server
Non-SNMP Managed Objects
SNMP Managed Objects
27

Course File
Proxy server converts non-SNMP data from non-SNMP objects to SNMP compatible objects and messages. An SNMP management system can behave as an agent as well as manager. This is similar to client/server architecture, where a host can function as both server and client. In the RMON, while collecting the data from network objects, performs some of the functions (network monitoring) of a network manager. However, the preprocessed data by RMON may be requested by the network manager or sent unsolicited by RMON to the network manager to integrate with the rest of the network data and display it to the user. In latter situation the RMON acts as a network agent.
System Overview: The below figure shows the SNMP Network Management Architecture. It portrays the data path between the manager application process and agent application process via the four transport function protocols: UDP, IP, DLC (Data Link Control), PHY (Physical). The three application layers above the transport layer are integrated in the SNMP process. The communication of management information among management entities is realized through exchange of just five protocol messages. Three of these (get-request, get-next request, and set-request) are initiated by the manager application process. The other two messages (get-response and trap) are generated by the agent process. The get-request message is generated by the management process requesting the value of an object. The value of an object is a scalar variable. The get-next request, or simply get-next, is very similar to get-request. In many situations, an object may have multiple values because of multiple instances of the object. The set-request is generated by the management process to initialize or reset the value of an object variable.
28

Course File
The get-response message is generated by an agent process. It is generated only on the receipt of a get-request, get-next request, or set-request message from a management process. The getresponse process involves filling the value of the requested object with any success or error message associated with the response. The other message that the agent generates is trap. A trap is an unsolicited message generated by an agent process without a message or event arriving from the manager process.
SNMP Manager
SNMP Agent
Management Data
SNMP Manager Application
SNMP Agent Application
GetNext-Request
GetNext-Request
Get-Response
Get-Request
Get-Request
Set-Request
Set-Request
Get-Response
Trap
SNMP UDP IP DLC PHY
SNMP UDP IP DLC PHY
Physical Medium Figure 4.9 SNM P Ne twork M anage me nt Archite cture
Trap
29

Course File
The Information Model: The information model deals with the Structure of Management Information (SMI) and Management Information Base (MIB). For information to be exchanged intelligently between manager and agent processes, there has to be common understanding of both the syntax and semantics. The syntax is used to describe management information in ASN.1 and a general introduction to it. The specification of managed objects and the grouping of, and relationship between, managed objects are addressed in Management Information Base.
There are generic objects that are defined by IETF and can be managed by any SNMPcompatible network management system. Objects that are defined by private vendors, if they conform to SMI defined by RFC 1155, and have MIBs specified by RFC 1213, can be managed by SNMP-compatible network management systems.
Managed Object:
Object
Object Type
Object Instance
Name: OBJECT IDENTIFIER
Syntax: ASN.1
Encoding: BER
Figure 4.10 M anage d Obje ct : Type and Instance

30

Course File
Object type and data type are synonymous Object identifier is data type, not instance Object instance IP address
Management Information Base (MIB): MIB is a virtual information base. Managed objects are accessed via this virtual information base. Objects in MIB are defined using ASN.1
Internet {1 3 6 1}
directory (1)
mgmt (2)
experimental (3)
private (4)
mib-2 (1)
system (1) interfaces (2) at (3) ip (4) icmp (5) tcp (6)
snmp (11) transmission (10) cmot (9) egp (8) udp (7)
31
Figu re 4.26 Inte rne t M IB-II Group

Course File
The structure of the management information defines the mechanism for describing these objects. The definition consists of three components:- name (OBJECT DESCRIPTOR), syntax (ASN.1), and encoding (BER). The objects defined in MIB-II have the OBJECT IDENTIFIER prefix: mib-2 OBJECT IDENTIFIER :: = {mgmt 1}
Subjective Questions: 1) Explain about the system architecture of SNMP management? 2) What are the four types of SNMP Models? 3) Describe the Structure of Management Information and Management Information Base in detail 4) What are the various MIB groups that are implemented in the SNMP network management? 5) Write about the organizational model in brief? 6) How Object Identifiers are defined in the Management Information Base? Objective Questions: 1. 2. 3. 4. 5. SNMP management is the most widely used network management system (NMS). ICMP is a mechanism used to transfer control messages between nodes. RFC stands for Request for Comments. RFC 1157 defines SNMP system architecture. A trap occurs when the agent observes the occurrence of a present parameter in the agent module. 6. SMI stands for Structure of Management Information. 7. The acronym for BER is Basic Encoding Rules. 8. The ASN.1 syntax is used to define the structure of object types. 9. SNMP based ASN.1 Data Types are a) Primitive types b) Defined types c) Constructor types. 10. Opaque is an application-wide data type that supports the capability to pass arbitrary ASN.1 Syntax.
32

Course File
11. SNMPv1 has adopted the basic encoding rules, BER, with its tag, length, and value (TLV) for encoding the information to be transmitted between the agent and the manager processes. 12. OBJECT IDENTIFIER is a unique name and number in the management information tree. 13. Network Address, IP Address and Counter are the defined data types. 14. Objects that are related are grouped into object groups. 15. The System group is the basic group in the Internet standard MIB. 16. SNMP management is organized as a two-tier management, in which a manager process and agent process communicate with each other. 17. All management operations can be done using five messages in SNMPv1. 18. The messages are exchanged according to the specifications defined in the Structure of Management Information. 19. The Syntax uses the Abstract Syntax Notation 1 (ASN.1) language. 20. The Internet Engineering Task Force is the standards organization and RFC, STD, and FYI are IETF documents on standards development.
UNIT-III OVERVIEW: Unit-III gives an overview about the communication model. The SNMP communication model deals with the administrative structure and the five SNMP message protocol data units (PDU). The administrative model defines the community within which messages can be exchanged. Specifications about the functional models are described in this chapter. CONTENTS: SNMPv1 Network Management: Communication and Functional Models 3.1 The SNMP Communication Model 3.1.1 The SNMP Architecture 3.1.2 The Administrative Model 3.1.3 SNMP Protocol Specifications 3.1.4 SNMP Operations
33

Course File
3.2
3.1.5 The SNMP MIB Group Functional Model
The SNMP Communication Model: The SNMP communication model defines the specifications of four aspects of SNMP communication: the architecture, the administrative model that defines data access policy, SNMP protocol, and the SNMP MIB. The architecture specifies the management messages between the management system and the management agents. Security in SNMP is managed by defining community, and only members of the same community can communicate with each other. The SNMP Architecture: The SNMP architecture consists of communications between network management stations and managed network elements, or objects. Network elements have built-in management agents if they are managed elements. The SNMP communications protocol is used to communicate information between the network management stations and the management agents in the elements. The SNMP manages the network with five messages. The SNMP messages are exchanged using the connectionless UDP transport protocol in order to be consistent with simplicity of the model, as well as to reduce the traffic. However, the mechanisms of the SNMP are suitable for a variety of protocols.
SNMP Manager
SNMP Agent
Management Data
GetNext-Request
GetNext-Request
Get-Response
Get-Request
Get-Request
Set-Request
Set-Request
Get-Response
Trap
SNMP UDP IP DLC PHY
SNMP UDP
Trap
34
IP DLC PHY

Course File
SNMP Messages: Get-Request Get-Next-Request Set-Request Get-Response Trap Generic Trap Specific Trap Time Stamp Generic trap Specific trap Time stamp
Cold start Warm start Link down Link up Authentication failure egpNeighborLoss For special measurements such as statistics Indicates the time since last initialization
The Administrative Model: It is based on the community profile and policy SNMP Entities
35

Course File
o SNMP Application Entities o Reside in management stations and network elements o Manager and Agent SNMP Protocol Entities o Communication processes (PDU handlers) o Peer processes that support application entities
SNMP Community: Security in SNMPv1 is community-based Authentication scheme in manager and agent Community: Pairing of two application entities Community name: String of octets Two applications in the same community communicate with each other Application could have multiple community names Communication is not secured in SNMPv1-no encryption
SNMP Manager Authentication Scheme
SNMP Manager Authentication Scheme Authentic Messages Authentication Scheme SNMP Agent
SNMP Manager Authentication Scheme
Figure 5.1 SNM P Commu nity
Functional Model: There are no formal specifications of functions in SNMPv1 management. OSI model addresses the functional model as Configuration configuration management in general is addressed by the specific network management system or by the use of telnet or console to set configurable parameters.
36

Course File
Fault-fault management is addressed by the error counters built into the agents Performance- performance counters are part of the SNMP agent MIB. It is the function of the SNMP manager to do the performance analysis. Security-The administrative model in protocol entity specifications addresses security function in basic SNMP Accounting-The accounting function is not addressed by the SNMP model Subjective Questions: 1) Explain about the SNMP operations in detail? 2) Brief out the functions present in the Functional Model? 3) Write about the SNMP Protocol Specifications? 4) Discuss about the SNMP communication and administrative model? 5) Write about the SNMP Architecture? 6) Explain about the SNMP MIB Group
Objective Questions: 1. Security in SNMP is managed by defining community, and only members of the same community can communicate with each other. 2. Only non aggregate objects are communicated using SNMP. 3. A management agent may be permitted to view only a subset of the network elements managed objects. This is called the community MIB view. 4. The SNMP authorization is implemented as part of managed-object MIB specifications. 5. A pairing of an SNMP community with an SNMP community profile is defined as SNMP access policy. 6. The SNMP agent with READ WRITE SNMP access mode can perform operations-get, set and trap. 7. The SNMP agent associated with the proxy policy is called a proxy agent, or commercially a proxy server. 8. The peer processes, which implement the SNMP, and thus support the SNMP application entities, are called protocol entities. 9. Communication among protocol entities is accomplished using messages encapsulated in UDP datagrams.
37

Course File
10. The increasing order of entity used in SNMP operations is in lexicographic order. 11. The pairing of variable and the value is called variable binding or VarBind. 12. ErrorIndex is used to provide additional information on the error status. 13. The SNMP communication model deals with the administrative structure and five snmp message protocol protocol data units. 14. The five protocol entities are defined in ASN.1 format and macros. 15. An SNMP protocol entity is received on port 161 on the host except for trap, which is received on port 162. 16. The VarBindList comprises the two VarBind name-value pairs, sysUpTime and atPhyAddress. 17. A nonzero ErrorStatus is used to indicate that an error occurred. 18. The get-response-request is the response from the agent to get (get-request and get-next request) and set(set-request) messages from the manager. 19. The set-request is used to initialize and edit the parameters of the network element. 20. Cold Start (0) is of generic trap type.
UNIT-IV OVERVIEW: Unit-IV gives an overview about the topic SNMPv2 and it enhancement for SNMP network management. The enhancements to SNMP architecture are the formalization of manager-tomanager communication and the inclusion of traps as part of the SMI and messages, instead of an appendix to SMI as in SNMPv1. Three messages have been added: get-bulk-request, informrequest, and report. There are several changes to SMI in SMIv2. Modules are formally introduced using the MODULE-IDENTITY macro.SMIV2 was introduced in which it split into three parts, each is defined in a separate RFC: module definitions, textual conventions, and conformance specifications. Object groups are introduced to group a number of related entities. The conformance specifications are intended to interpret what the vendor is specifying in the network component with regard to compliance with SNMP management. Two modules have been added to Internet Module: security and SNMPV2 in this unit. All the protocol PDUs including trap, have been unified into a common data format. The new get-bulk-request is intended to improve the efficiency of the get-next request in SNMPV1 by
38

Course File
retrieving the data in large quantities. The interoperatablility of management systems has been facilitated by a new message, inform-request. CONTENTS: SNMP Management: SNMPv2 4.1 Major Changes in SNMPv2 4.2 SNMPv2 System Architecture 4.3 SNMPv2 Structure of Management Information 4.3.1 SMI Definitions for SNMPv2 4.3.2 Information Modules 4.3.3 SNMP Keywords 4.3.4 Module Definitions 4.3.5 Object Definitions 4.3.6 Textual Conventions 4.3.7 Creation and Deletion of Rows in Tables 4.3.8 Notification Definitions 4.3.9 Conformance Statements 4.4 The SNMPv2 Management Information Base 4.4.1 Changes to the System Group in SNMPv2 4.4.2 Changes to the SNMP Group in SNMPv2 4.4.3 Information for Notification in SNMPv2 4.4.4 Conformance Information in SNMPv2 4.45 Expanded Internet MIB-II 4.5 SNMPv2 Protocol 4.5.1 The Data Structure of SNMPv2 PDUs 4.5.2 SNMPv2 Protocol Operations 4.6 Compatibility with SNMPv1 4.6.1 The Bilingual Manager 4.6.2 The SNMP Proxy Server Key Concepts:
39

Course File
Bulk Data Transfer Message: Two significant messages were added. The first is the ability to request and receive bulk data using the get-bulk message. This speeds up the get-next-request process and is especially useful to retrieve data from tables. Manager-to-Manager Message: The second additional message deals with interoperatability of two network management systems. This message extends the communication of management messages between management systems and thus makes network management systems interoperable. Structure of Management Information (SMI) : In SNMPv1, SMI is defined as STD 16, which is described in RFCs 1155 and 1212, along with RFC 1215, which describes traps. They have been consolidated and rewritten in RFCs 1902 through 1904 for SMI in SNMPv2. RFC 1902 deals with SMIv2, RFC 1903 with textual conventions, and RFC 1904 with conformances. SMIv2 is divided into three parts: module definitions, object definitions, and trap definitions. An ASN.1 macro, MODULE-IDENTITY, is used to define an information module. It concisely conveys the semantics of the information module. OBJECT-TYPE macro defines the syntax and semantics of a managed object. Trap is also termed notification and defined by NOTIFICATION-TYPE macro. Textual Conventions are designed to help define new data types. They are also intended to make the semantics consistent and clear to the human reader. Although new data types could have been created using new ASN.1 classes and tags, the decision was made to use the existing defined class types and apply restrictions to them. Conformance Statements help the customer objectively compare the features of the various products. It also keeps the vendors honest in claiming their products are compatible with a given SNMP version. Compliance defines a minimum set of capabilities. Vendors can offer additional capabilities as options. Table Enhancements: Using a newly defined columnar object with a Syntax clause, RowStatus, conceptual rows can be added to or deleted from an aggregate object table. Further, a table can be expanded by augmenting another table to it, which is helpful in adding columnar objects to an existing aggregate object.
40

Course File
MIB Enhancements: In SNMPv2, the Internet node in the MIB has two new subgroups: security and SNMpv2. There are significant changes to the system and SNMP group of version 1. Changes to the system group are under the mib-2 node in the MIB. The SNMP entities in version 2 are a hybrid, with some of the entities from the SNMP group, and the rest from the groups under the newly created SNMPv2 node. Transport Mappings: There are several changes to the communication model in SNMPv2. Although UDP is the preferred transport protocol mechanism for SNMP management, other transport protocols can be used with SNMpv2. The mappings needed to define other protocols on to UDP are the subject of RFC 1906. SNMPv2 System Architecture: The SNMPv2 system architecture looks essentially the same as that of version 1, However, there are two significant enhancements in the SNMPv2 architecture. First there are seven messages instead of five. Second, two manager applications can communicate with each other at peer level. The messages get-request, get-next request, and set-request are the same as in version 1 and are generated by the manager application. The message response is also same as getresponse in version 1, and is now generated by both the agent and the manager applications. It is also generated by the manager application in response to an inform-request message from another manager application. An inform-request message is generated by a manager application and transmitted to another manager application. The receiving manager application responds with a response message. This set of communication messages is a powerful enhancement in SNMPv2, because it makes two network management systems interoperable. The message get-bulk-request is generated by a manager application. It is used to transfer large amounts of data from the agent to the manager, especially if it includes retrieval of table data. The retrieval is fast and efficient. The receiving entity generates and fills data for each entry in the request and transmits all the data as a response message to the originator of the request. An SNMPv2 trap event known as trap in version 1, is generated and transmitted by an agent process when an exceptional situation occurs.
41

Course File
Another enhancement to SNMPv2 over version 1 is mapping of SNMP layer over multiple transport domains. Subjective Questions: 1.) Explain about the SNMPv2 System Architecture? 2.) Describe the following? a. Information Modules b. SNMP Keywords c. Module Definitions d. Object Definitions 3.) What are the major changes in SNMPv2? Explain? 4.) What are the Textual Conventions and where it is used? 5.) Write about the SNMPv2 Structure of Management Information? 6.) Explain the SNMpv2 Management Information Base
Objective Questions: 1) What are the module definitions? 2) What are the textual conventions? 3) Define SNMPv2 trap event? 4) Why the message inform-request is used? 5) Why the get-bulk-request is generated? 6) What do a get-next request do? 7) Define Information module? 8) What are the notification definitions? 9) Write the Conformance Statements? 10) What are the SNMPv2 Protocol Operations? 11) What does the SNMP proxy server do?
42

Course File
12) Write about the use of OBJECT-IDENTITY macro? 13) Uses of The SNMPv2- Trap-PDU and Inform Request-PDU operations? 14) What does the Bilingual Manager do? 15) How many messages we use in the SNMPv2 system architecture? 16) Expand PDU? 17) What are the aggregate objects? 18) What is Sparse Dependent Table? 19) Mention at least two data types of SMIv2 Textual Conventions? 20) Which RFC document defines the SNMPv2 conformance statements?
MID EXAM-1
Class: IV-IT SEM-II Subject: Network Management Systems

1) 2) 3) 4) 5) 6)
SET N0-01
Explain about the protocol data unit communication model between end systems. Describe the SNMP network management architecture with the help of a neat diagram. Write about the goals of the network management. Explain about the four network models in detail? Write about the SNMP protocol specifications? Describe the SNMP Get-Next Request with indices?
Answers: 1) Communication architecture Modeling of communication systems, comprising functional components and operations interfaces between them Communication protocols Operational procedures intra- and inter-modules Communication standards
43

Course File
Agreement between manufacturers on protocols of communication equipment on physical characteristics and operational procedures
Communication between users (human beings who use a system) and applications (Programs that run in a system) occurs at various levels. They can communicate at the application level, the highest level of communication architecture. Or, they can exchange information at the lowest level, the physical medium. Each system can be divided into two broad sets of communication layers. The top set of layers consists of the application layers and the bottom set of transport layers. The users and users include application programs- interface with the application-level layer and the communication equipment interfaces with the physical medium. The figure given below shows the end systems communicating via an intermediate system N, which enables the use of different physical media for the two end systems. System N converts the transport layer information into the appropriate protocols. Thus, system A could be on a copper-wire LAN and system Z could be on a fiber-optic cable.
User A Peer-Protocol Interface Application Layers Transport Layers
User Z
Application Layers Transport Layers
Physical Medium (a) Dire ct Communicatio n be twe e n End Syste ms System A Intermediate system System Z
User A Peer-Protocol Interface Application Layers Transport Layer Transport Layers Conversion Physical Medium Physical Medium
User Z
Application Layers
Transport Layers
(b ) Communicatio n be twe e n End Syste ms v ia an Inte rme diate Syste m
Figur e 1.11 Basic Communication Arch ite ctur e
Inter-layer interface: user and service provider Peer-layer protocol interface

44

Course File
Analogy of hearing-impaired student Role of intermediate systems Gateway: Router with protocol conversion as gateway to an autonomous network or subnet
2) SNMP Network Management Architecture: The SNMP Architecture: The SNMP architecture consists of communications between network management stations and managed network elements, or objects. Network elements have built-in management agents if they are managed elements. The SNMP communications protocol is used to communicate information between the network management stations and the management agents in the elements. The SNMP manages the network with five messages. The SNMP messages are exchanged using the connectionless UDP transport protocol in order to be consistent with simplicity of the model, as well as to reduce the traffic. However, the mechanisms of the SNMP are suitable for a variety of protocols.
SNMP Manager
SNMP Agent
Management Data
GetNext-Request
GetNext-Request
Get-Response
Get-Request
Get-Request
Set-Request
Set-Request
Get-Response
Trap
SNMP UDP IP DLC PHY
SNMP UDP IP DLC PHY
Trap
45
Physical Medium

Course File
SNMP Messages: Get-Request Get-Next-Request Set-Request Get-Response Trap Generic Trap Specific Trap Time Stamp Generic trap Specific trap Time stamp
Cold start Warm start Link down Link up Authentication failure egpNeighborLoss For special measurements such as statistics Indicates the time since last initialization
3) Goals of the Network Management: The goals of the network management are to ensure that the users of a network receive the information technology services with the quality of service that they expect. Toward meeting this goal, management should establish policy to either formally or informally contract a Service Level Agreement with the users.
46

Course File
From a business administration point of view, network management involves strategic and tactical planning of the engineering, operations, and maintenance of a network and network services for current and future needs at minimum overall cost.
Network Management
Network Provisioning Planning Design
Network Operations Fault Management / Service Restoration Configuration Management
Network Maintenance Fault Management Trouble Ticket Administration Performance Management / Traffic Management Network Installation Security Management Network Repairs Accounting Management Reports Management Inventory Management Data Gathering & Analyses Facilities Installation & Maintenance Routine Network Tests
Figure 1.21 Network Management Functional Groupings
The above figure presents a top-down view of network management functions. It comprises three major groups: 1) Network Provisioning 2) Network Operations, and 3) Network Installation and Maintenance (I & M). It is useful to consider the different functions as belonging to specific administrative groups, although there are other ways of assigning responsibilities based on organizational structure. Network provisioning is the primary responsibility of the engineering group; and network I & M is the primary responsibility of the plant facilities group. The interactions among the groups are shown in the above figure. The normal daily operations are the function of the network operations group, which controls and administers a network operation center (NOC), the nerve center of network management operations. The functions of the NOC are concerned primarily with network operations; its secondary responsibilities are network provisioning and network I & M. 4) Network Management Models:
47

Course File
The OSI network model is an ISO standard and is the most superior of all the models, it is structured and it addresses all aspects of management. The below figure shows an OSI network management architecture model that comprises four models:
Network Mangement
Organization Model
Information Model
Communication Model
Functional Model
Figur e 3.1
OSl Ne twork M anage me nt M od e l
1) Organization Model: The organization model describes the following Network management components Functions of components Relationships
The organizational model is defined in ISO 10040 OSI Systems Management Overview. It defines the terms object, agent, and manager.
MDB
Manager
Managed objects Unmanaged objects MDB Management Database Agent process Figure 3.2 Two-Tie r Ne twork M ang e me nt Organizatio n M ode l
Network objects consist of network elements such as hosts, hubs, bridges, routers, and so on. They can be classified into managed objects and unmanaged objects or elements. The managed
48

Course File
elements have a management process running in them, called an agent. The manager manages the managed element. Manager o Sends requests to agents o Monitors alarms o Houses applications o Provides user interface Agent o Gathers information from objects o Configures parameters of objects o Responds to managers requests o Generates alarms and sends them to mangers Managed object o Network element that is managed o Houses management agent o All objects are not managed / manageable 2) Information Model: An information model is concerned with the structure and the storage of the information. The representation of objects and information relevant to their management form the management information model. The information model specifies the information base to describe managed object and their relationships. The Structure of Management Information (SMI) defines the syntax and semantics of management information stored in the Management Information Base (MIB). The MIB is used by both agent and management processes to store and exchange management information. The MIB associated with an agent is called the agent MIB and the MIB associated with a manager is designated the manager MIB.
MDB
Manager
MIB
MDB Management Database MIB Management Information Base

Managed objects
Agent process
49

Course File
Distinction between MDB and MIB MDB physical database; e.g.. Oracle, Sybase MIB virtual database; schema compiled into management software An NMS can automatically discover a managed object, such as a hub, when added to the network The NMS can identify the new object as hub only after the MIB schema of the hub is compiled into NMS software
Structure of Management Information (SMI): SMI defines for a managed object Syntax Semantics plus additional information such as status Example sysDescr: { system 1 } Syntax: OCTET STRING Definition: "A textual description of the entity. " Access: read-only Status: mandatory Managed Object: Managed objects can be Network elements (hardware, system) hubs, bridges, routers, transmission facilities Software (non-physical) programs, algorithms Administrative information contact person, name of group of objects (IP group)
3) Communication Model:
50

Course File
Management data is communicated between agent and manager processes, as well as between manager processes. Three aspects need to be addressed in the communication of information between two entities transport medium of the message exchange (transport protocol), message format of communication (application) protocol, and the actual message (commands and responses).
Operations / Requests Manager Applications Responses Notifications / Traps Agent Network Elements / Managed Objects
Figure 3.11 M anagement M e ssage Communication M ode l
4) Functional Model: The functional model component of the OSI model addresses the user-oriented applications, which are formally specified in the OSI model and are shown in the below figure. The functional model consists of five sub models: configuration management, fault management, performance management, security management, and accounting management.
OSI Functional Model
Configuration Management
Fault Management
Performance Management
Security Management
Accounting Management
51

Course File
Configuration management o set and change network configuration and component parameters o Set up alarm thresholds Fault management o Detection and isolation of failures in network o Trouble ticket administration Performance management o Monitor performance of network Security management o Authentication o Authorization o Encryption Accounting management o Functional accounting of network usage 5) SNMP Protocol Specifications: The peer processes, which implement the SNMP; and thus support the SNMP application entities, are called protocol entities. Communication among protocol entities is accomplished using messages encapsulated in UDP data grams. An SNMP message consists of a version identifier, an SNMP community name, and a protocol data unit (PDU). The version and the community name are added to the data PDU and along with the application header and the entire message is passed on to the transport layer an SNMP PDU. The UDP header is added at the transport layer, which then forms the transport PDU for the network layer. Addition of an IP header to the transport PDU forms the network PDU for the data link layer.
SNMP PDU Application PDU Transport PDU Network PDU Data Link PDU DLC Header IP Header UDP Header Application Version Header
Community
Data
SNMP PDU
Application PDU Transport PDU Network PDU
52
Figure 5.5 Encapsulate d SNM P M e ssage

Course File
The network or data link layer (DLC) header is added before the frame is transmitted on to the physical medium. An SNMP protocol entity is received on port 161 on the host except for trap, which is received on port 162. 6) SNMP Get-Next Request with Indices: GetNextRequest PDU Operation: A get-next-request operation is very similar to a get-request, except the requested record is the one next to the OBJECT IDENTIFIER specified in the request. The figure shows the operations associated with retrieving data for the System group by the manager process using the get-next-request. The first message is a GetRequest-PDU for sysDescr and the response returns the value SunOS. The manager process then issues a GetNextRequest-PDU with the OBJECT IDENTIFIER sysDescr. The agent processes the name of the next OBJECT IDENTIFIER sysObjectID and its value enterprises.112.2.3.10.1.2. The sequence terminates when the manager issues get-next-request for the object identifier next to sysServices and the agent process returns the error message noSuchName.
Manager Process
GetNextRequest (sysUpTime, atPhysAddress) GetResponse( (sysUpTime.0 = "315131795"), (atPhysAddress.13.172.16.46.1 = "0000000C3920AC"))
Agent Process
GetNextRequest (sysUpTime, atPhysAddress.13.172.16.46.1)
GetResponse( (sysUpTime.0 = "315131800"), (atPhysAddress.16.172.16.49.1 = "0000000C3920AF") )
53
GetNextRequest (sysUpTime, atPhysAddress.16.172.16.49.1)
GetResponse( (sysUpTime.0 = "315131805"), (atPhysAddress.23.192.168.3.1 = "0000000C3920B4") )

Course File
UNIT-V OVERVIEW: Unit-V gives you an overview about the network management using the RMON (Remote Monitoring). Network Performance which is managed in SNMP version 1 was limited. The performance is maintained well in the Remote Monitoring. Effective monitoring of NOC (Network Operations Center) is discussed using the RMONv1, RMONv2 and ATM Remote Monitoring.
54

Course File
CONTENTS: SNMP Management: RMON 5.1 What is Remote Monitoring? 5.2 RMON SMI and MIB 5.3 RMON1 5.3.1 RMON1 Textual Conventions 5.3.2 RMON1 Groups and Functions 5.3.3 Relationship between Control and Data Tables 5.3.4 RMON1 Common and Ethernet Groups 5.3.5 RMON Token Ring Extension Groups 5.4 RMON2 5.4.1 The RMON2 Management Information Base 5.4.2 RMON2 Conformance Specifications 5.5 ATM Monitoring 5.6 A case study of Internet Traffic using RMON
RMON Components:
Data Analyzer
SNMP Traffic
Router
BACKBONE NETWORK
Router
SNMP Traffic
RMON Probe
RMON Probe o Data gatherer- a physical device Data Analyzer o Processor that analyzes data
LAN
RMON: Remote Monitoring It is a standard based network management protocol

55

Course File
Allows network information to be gathered at a single workstation Defines additional MIBs to provide a richer set of data about network usage RMON Benefits: RMON2: Applicable to layer 3 and above Functions are similar to RMON1 Enhancements to RMON1 Defined Conformance and Compliance Monitors and Analyzes locally and relays data, Less load on the network Needs no direct visibility by NMS More reliable information Permits monitoring on a more frequent basis and hence faster fault diagnosis Increases productivity for administrators
ATM RMON:
Application Layer
Upper Layer Protocols RMON-2 (RFC 2021, 2074)
Netw ork Layer
ATM Protocol IDs for RMON-2 (Additions to RFC 2074)
Ethernet RMON (RFC 1757)
Token Ring RMON (RFC 1513)
'Base' Layer
Switch Extensions for RMON
ATM RMON
IETF MIBs
Additional MIBs
56
Figure 8.7 RM ON M IB Frame work (1995 ATM Forum)

Course File
Key Points: ATM Forum extended RMON to ATM Switch Extensions and ATM RMON define objects at the base layer ATM protocol IDs for RMON2 define additional objects at the higher levels ATM devices require cell-based measurements and statistics Probe should be able to handle high speed
ATM Technology: ATM Technology is based on: Virtual Path/ Virtual Circuit Fixed Packet Size or Cell Small Packet Size ( 53 bytes) Statistical multiplexing Integrated services Packets in a session take the same path in VP/VC After initial set up, latency is reduced SDH/SONET in WAN uses 155.52 Mbps as basic data rate and is universal ( in contrast to T1 and E1) Transmission medium primarily used in ATM is optical fiber ATM used in LAN for high speed emulating Ethernet LAN
Subjective Questions: 1. 2. 3. 4. What is Remote Monitoring and explain about RMON SMI and MIB? Write about the RMON1 Textual Conventions? Explain about the RMON1 Common and Ethernet Groups? Describe RMON2 and its Management Information Base?
57

Course File
5. Explain ATM Remote Monitoring? 6. Write about RMON1 Groups and Functions?
Objective Questions: 1. What does FDDI stands for? 2. Write about one benefit for implementing RMON technology in a network? 3. What is the advantage of using RMON devices? 4. What is the use of textual conventions? 5. What are the two newly defined data types in the textual conventions? 6. Where the RMON1 does performs functions? 7. What are the specifications of the Filter Group? 8. In how many groups RMON2 MIB is arranged? 9. RMON1 deals with which layer? 10. What is the technology which ATM is based on? 11. Name the four groups present in the ATM RMON MIB? 12. What is the difference between RMON1 and RMON2? 13. What are the conformance specifications? 14. Which group is used to measure incoming and outgoing traffic? 15. What is required to copy the cells on to the probe in RMON MIB?
UNIT-VI OVERVIEW: Unit-V1 gives an overview about the Telecommunication Management Network which is one form of the network management system where data transfer is done using the telecommunication technology. In this chapter operation systems of the TMN were introduced, which forms the building blocks of TMN. The concept of TMN is addressed. It is based on large number of standards which are delineated. TMN architecture is described. TMN management service architecture is covered and an integrated view is presented.
58

Course File
CONTENTS: Telecommunications Management Network 6.1 Why TMN? 6.2 Operations Systems 6.3 TMN Conceptual Model 6.4 TMN Standards 6.5 TMN Architecture 6.5.1 Functional Architecture 6.5.2 Physical Architecture 6.5.3 Information Architecture 6.6 TMN Management Service Architecture 6.7 An Integrated View of TMN 6.8 Implementation Issues TMN: Necessity for interoperability basis for TMN Need for management of more than just the network components Networks / sub networks need to be managed Services-internal and external need management Business Management needs to be addressed TMN joint effort by ITU-T and ISO
TMN Conceptual Model: From a TMN point of view, the network management system (NMS) is treated as an operations system. It manages the data communication and telecommunications network, although from a TMN perspective. The telecommunication network shown consists of switching exchange and transmission system network elements. It is primarily the WAN of communications. The switching systems are both analog and digital and include all transport facility modes, including twisted pair, coaxial, fiber optics, and wireless.
59

Course File
TMN Conceptual Model:

Service provider A Service provider B
Customers
Customers
Services provided by Telecommunications Provider
Network
Network
Q3
Q3
Operations Systems Q3 OS OS F Workstation System Operators
Figure 11.4 TM N Co nce ptual M o de l
TMN Architecture: TMN Architecture is defined in M.3010, which describes the principles for a TMN. Three architectural perspectives are presented: functional, physical, and information. The functional architecture identifies functional modules, or blocks, in the TMN environment, including the reference points between them, and specifies interface requirements. The physical architecture defines the physical blocks and interfaces between them. The information architecture deals with the information exchange between managed objects and management systems, using a distributed object-oriented approach.
60

Course File
TMN Architecture:
TMN Architecture
Functional Architecture
Physical Architecture Figure 11.6 TM N Archite ctu re
Informational Architecture
TMN Reference Point:

Function Block Reference Point Function Block
Figure 11.8 TM N Re fe re nce Point
Functional Blocks connected by conceptual interfaces, called reference point Designated by lower case letters ( upper case letter for physical interfaces) x: Interface between operation systems that belong to different domains; e.g., interface between two NMSs belonging to two different domains q3: Interface between two OSFs in the same domain qx: Interface between mediation function such as RMON and agent in the network element f : Interface to the workstation TMN Service Architecture: TMN service architecture consists of four layers of management and a fifth layer of network elements. The four layers of management are element management, network management, service management, and business management. It presents an integrated view of the components, showing how they all fit together to form the TMN environment.
61

Course File
TMN Service Architecture:
Bu sine ss Man a ge me nt q3 Se rvice Ma na ge me nt q3 Ne twor k Ma na ge me nt q3 Ele me n t Man ag eme nt q3 Man ag ed Netwo rk Ele men t
F ig u r e 11 .11
TM N Se r v ic e Ar c h ite c tu r e
Subjective Questions: 1. Why do we need Telecommunication Management Network and how effectively it supports as Network Management Systems? 2. What are the TMN standards that are followed? 3. Explain about the TMN Architecture? 4. Write about the TMN Management Service Architecture? 5. Describe TMN Reference points? 6. What are the Implementation issues in the TMN?
62

Course File
Objective Questions: 1. What does TMN stands for? 2. What is TMN operation systems function (OSF)? 3. What is TMN network element function (NEF)? 4. What is TMN mediation function (MF)? 5. How many types is the TMN architecture divided into? 6. What does the physical architecture indicate? 7. What does the functional architecture of TMN indicate? 8. What does the Information architecture of TMN indicate? 9. What does DCF stands for? 10. Define TMN Interfaces? 11. What does the TMN workstation function do? 12. What is the role of the service management layer? 13. How many OSI system management functional areas does a TMN management service have? 14. Acronym for OMNI Point? 15. What are the two forums that have actively promoted implementation of TMN? 16. What is the role of Network Element Layer? 17. What is the role of element management layer? 18. Acronym for CMIS? 19. What is a trunk? 20. What does the NMF stands for?
UNIT-VII OVERVIEW: In this unit the tools and systems used to monitor and manage a network. The available tools help people who work on and manage networks and those who are network users. Some generalpurpose tools used in daily network maintenance are explained. Tools that measure the bit error rate is explained. Numerous software tools exist for obtaining information on networks are also discussed. Protocol analyzer as a system tool for gathering statistics is also covered.The history of enterprise management systems is recounted. Enterprise management covers a spectrum of functions. Multiple network management systems are configured for managing an enterprise
63

Course File
network are discussed. Basic requirements are specified for a manager of managers network management system for enterprise use. CONTENTS: Network Management Tools and Systems 7.1 Network Management Tools 7.1.1 Tools Catalog 7.1.2 Bit Error Rate Tester 7.1.3 Basic Software Tools 7.1.4 SNMP MIB Tools 7.1.5 Protocol Analyzer 7.2 Network Statistics Measurement System 7.2.1 Traffic Load Monitoring 7.2.2 Protocol Statistics 7.2.3 Data and Error Statistics 7.2.4 Using MRTG to collect Traffic Statistics 7.3 History of Enterprise Management 7.4 Network Management Systems 7.4.1 Functional Components 7.4.2 Multiple NMS Configuration 7.4.3 Network Management System Requirements 7.5 Commercial Network Management Systems 7.5.1 HPs Open View Network Node Manager 7.5.2 Cabletrons Spectrum Platform 7.5.3 Sun Network Management Systems Family 7.6 System Management 7.6.1 High-End System Management 7.6.2 Low-End System Management 7.7 Enterprise Management Solutions 7.7.1 Computer Associates Uni center TNG 7.7.2 Tivoli Enterprise Manager
BERT:
64

Course File
BERT A
Modem A Loop Back
Modem B Loop Back
BERT B
Figure 12.2 Bit Error Rate Te ste r (BERT)
BERT is a physical layer monitoring tool Generates and detects bits Bit Error Rate(BER) is calculated by comparing the transmitted pattern with received pattern Loop back is a feature of the modem BER can be measured for a modem or two modems and the link in between If Config: Used to assign/ read an address to/ of an interface Option a is to display all interfaces Notice two interface loop-back (lo0) and Ethernet (hme0)
Example: Netman: ifconfig -a lo0: flags=849<UP,LOOPBACK,RUNNING,MULTICAST> mtu 8232 inet 127.0.0.1 netmask ff000000 hme0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500 inet 192.207.8.31 netmask ffffff00 broadcast 192.207.8. Ping:
Most basic tool for internet management Based on ICMP ECHO_REQUEST message Available on all TCP/IP stacks Based on ICMP ECHO_REQUEST message
65

Course File
Useful for measuring connectivity Useful for measuring Packet Loss Can do auto-discovery of TCP/IP equipped stations on single segment Example: Most basic tool for internet management Based on ICMP ECHO_REQUEST message Available on all TCP/IP stacks Useful for measuring connectivity Useful for measuring packet loss Can do auto-discovery of TCP/IP equipped stations on single segment Nslookup: An interactive program for querying Internet Domain Name System Servers Converts a host name into an IP address and vice versa querying DNS Useful to identify the subnet a host or node belongs to Lists contents of a domain, displaying DNS record Available with BSD UNIX; FTP from uunet.uu.net Available in Windows NT
Example: noc2% nslookup 172.152.8.138 Server: ada.btc.gatech.edu Address: 192.77.147.28 Host: Command : Host Displays host names using DNS Available from ftp.nikhef.nl:/pub/network/host.tar.Z
Example: % host -a sun4-gw.cc.gatech.edu

66

Course File
Trying null domain rcode = 0 (Success), ancount=1 The following answer is not authoritative: Sun4-gw.cc.gatech.edu 85851 IN A 130.207.111.100
Snoop: Puts a network interface in promiscuous mode Logs data on o Protocol type o Length o Source address o Destination address o Reading of user data limited to superuser Example: Options: -d for device interface and -c for counts TCP Dump: Command: tcpdump Interprets and prints headers for: o Ethernet IP ICMP o TCP UDP NFS o ND ARP o AppleTalk Useful for examining and evaluating the TCP based traffic Available in UNIX system; FTP from ftp.ee.lbl.gov SNMP Command Tools: snmptest snmpget snmpgetnext snmpset
67

Course File
snmptrap snmpwalk snmpnetstat
Test tool is an interactive tool to get values of several managed objects, one at a time. Get, Get-next and Set are the SNMP commands that we learned under SNMP architecture / messages. Execution of these will return an SNMP Response message. SNMPWalk uses snmpgetnext to trace the entire MIB. Network status command is used to test the status of network connections of a host. Protocol Analyzer:
Data Capture Device Raw data transferred on Modem / WAN or LAN Link
PROTOCOL ANALYZER
LAN
Figur e 12.13 Pro tocol Analyze r Basic Configuration
Analyzes data packets on any transmission line including LAN Measurements made locally or remotely Probe (data capture device) captures data and transfers to the protocol analyzer (no storage) Data link between probe and protocol analyzer either dial-up or dedicated link or LAN Protocol analyzer analyzes data at all protocol levels RMON Probe:
PROTOCOL ANALYZER
SNMP Traffic
Router
BACKBONE NETWORK
Router
SNMP Traffic
RMON Probe
LAN
Figure 12.14 Protocol Analyze r with RM ON Probe
68

Course File
Network Associates Sniffer o Stand-alone and Networked HP NetMetrix / HP OpenView o Communication between probe and analyzer is using SNMP Data gathered and stored for an extended period of time and analyzed later Used for gathering traffic statistics and used for configuration management for performance tuning Network Monitoring with RMON Probe:
Protocol Analyzer
Ethernet Probe Ethernet LAN
Router
FDDI LAN Router
Backbone Network
Router FDDI Probe Token Ring LAN Token Ring Probe
Backbone Probe
Figur e 12.15 M on itoring of Total Ne twork with Ind iv id ual RM ON Prob e s
Subjective Questions:
1. Explain about the Bit Error Rate Testor? 2. What are the basic software tools that are used in Network Management System? Explain. 3. Write about the Protocol Analyzer in Detail? 4. Write about the History of Enterprise Management? 5. Discuss various Network Statistics Measurement Systems? 6. Write about the network management system requirements?
Objective Questions:
69

Course File
1. What is a Tool Catalog? 2. Define BERT? 3. What are the Basic Software Tools? 4. List out the Route Monitoring Tools? 5. How many types of SNMP MIB Tools? What are they? 6. What does MRTG stands for? 7. When did the Enterprise Management evolved? 8. List the Network Management System Functional Components. 9. What is the specification of the SNMP Set Command? 10. What is the specification of the Trap Command? 11. What is the specification of the SNMP Sniff Tool? 12. What is the protocol Analyzer? 13. How many types of trap messages are there? 14. What are the community administration parameters? 15. Define Drilling? 16. How many types of SNMP Command Tools are there? 17. What is Ping Command? 18. What is Nslookup Command? 19. What is TCP Dump Command? 20. Write IfConfig Command?
UNIT-VIII OVERVIEW: Unit-VIII gives you an overview about the Web-Based Management. In this chapter the multi router traffic grapher (MRTG) performance tool, which is used to gather traffic statistics and is based on Web Technology. Various Web Based managements are discussed in the unit. The use of Web Technology in system management and presents the examples of Big Brother and Spong. Some of the concepts like Web Interface to SNMP Management, Web-based enterprise management, Windows Management Instrumentation are included in this unit which will give more information on managing a NMS using Web.
70

Course File
CONTENTS: Web-Based Management: 8.1 NMS with Web Interface and Web-Based Management 8.2 Web Interface to SNMP Management 8.3 Embedded Web-Based Management 8.4 Desktop Management Interface 8.5 Web-Based Enterprise Management 8.6 WBEM: Windows Management Instrumentation 8.7 Java Management Extensions 8.7.1 Service-Driven Network 8.7.2 Java Dynamic Management 8.7.3 JMX Architecture 8.8 Management of Storage Area Network The Jiro Platform 8.9 Future Directions
Web-Base Management: Display on Web browser Economical displays Ubiquitous access Reduction in network load for non-polled configuration Web Interface vs. Web-base management Web-based management o Desktop management interface o Web-based enterprise management o Java management extensions
Web Interface:
71

Course File
Desktop PC Web Browser
HTTP
NMS Console
Web Server
SNMP Manager SNMP
NMS
SNMP Agent
Managed Objects
Figure 14.1 SNM P NM S with We b Inte rface
SNMP-based NMS NMS database transferred to Web-server View with Web browser Protocol between NMS and network elements is SNMP HTTP between Web server and browsers
Proxy Server:
Desktop PC Web Bro wser
HTTP
Web Ser ver
Man age r Ap plica tio ns SNMP/ Oth er
Pr oxy Ser ver
SNMP / Oth er Ag en t
Man age d Objects
F ig u r e 1 4.2 Pr o xy Se r v e r w ith We b In te r fa ce
72

Course File
Proxy Server: Similar to Web interface No NMS monitor No GUI in manager applications Embedded WBM:
Workstation/PC Web Browser Manager Applications HTT P
Web Server
Managed Objects
Figu re 14.3 Embe dd e d WBM Config uration
Web servers are embedded in managed objects Data is pushed by the management agents in managed objects to the manager applications Smart agents Portable agents Web-Based Enterprise Management: WBEM based on Common Information Module, developed by Microsoft CIM is information-modeling framework intended to accommodate all protocols and frameworks Object-oriented
73

Course File
Five components: Web client CIM object manager (CIMOM) CIM schema Management protocol Managed objects with specific protocol
Web Client
Desktop PC SNMP Agent Web Browser DMI Agent Management Applications CIM Agent
HTT P
CIM Object Manager (CIMOM)
CIM Schema
HTT P HTT P SNMP Provider SNMP
HTT P
DMI Provider
RPC
SNMP Managed Objects
CIM Managed Objects
DMI Managed Objects
Figur e 14.8 WBEM Archite ctur e
Subjective Questions: 1. 2. 3. 4. 5. 6. Explain about the NMS using Web-Based Interface and Web-Based Management? Write about the Web Interface to SNMP Management? How Desktop Management Interface is used in Network Management System? Write about Web-Based Enterprise Management? What are the Java Management Extensions? Brief out the Windows Management Instrumentation with a diagram?
Objective Questions: 1. What does WBEM stands for?

74

Course File
2. 3. 4. 5.
What does CIM stands for? How many components do a WBEM consists of? Define Web Client? What is the second approach to develop a common model for total management using Web Technology? 6. Define Java Bean or MBean? 7. What are protocol adapters? 8. The other name for protocol adapters is also called? 9. Who developed Desktop Management Interface (DMI)? 10. Acronym for JMX? 11. How many approaches are available to implement the web interface on existing SNMP based management system? 12. What are the two MIBs that are reserved for future use in the Desktop Management Interface (DMI) MIB? 13. Define a Web phone? 14. List out the three Common Information Model (CIM) modules? 15. What is Jiro Platform? 16. Define MBean Server? 17. WMI stands for? 18. What is the objective for Jiro platform? 19. WBEM is based on which model? 20. Who developed the CIM framework? MID EXAM-II
Class: IV-IT SEM-II
SET N0-02
1) 2) 3) 4) 5) 6)
Explain about the Telecommunication Management Network Conceptual Model Write a short notes on Bit Error Rate Tester and protocol analyzer Describe the concept of RMON using ATM What is RMON and give a brief note on textual conventions of RMON1 Explain about the Telecommunication Management Network Architecture and its types. Write about the Web Interface to SNMP management
Answers:
75

Course File
1) Telecommunication Management Network Conceptual Model: Telecommunication Management Network has Necessity for interoperability basis for TMN Need for management of more than just the network components Networks / sub networks need to be managed Services - internal and external need management Business management needs to be addressed TMN joint effort by ITU-T and ISO TMN Conceptual Model: From a TMN point of view, the network management system (NMS) is treated as an operation system. It manages the data communication and telecommunications network. The data communication network components consist of LANs, bridges, routers, gateways, and hosts. ITU-T Recommendation M.3010 defines TMN as a conceptually separate network that interfaces with one or more individual telecommunications networks at several points in order to send or receive information to or from them and control their operation. It consists of a network of operations systems, including a network management system.
Service provider A Service provider B
Customers
Customers
Network
Network
Q3
Q3
76
Figure 11.4 TM N Co nce ptual M o de l

Course File
The two columns in the figure show the identical components of two service providers, A and B. These components are workstations, Oss, networks, services, and interfaces, operations of the systems, and customers who use the services. Customers buy services from service providers, and providing quality customer services should be a key part of a service providers business. Thus service management is an important consideration in the TMN model. The service provider sells the communication services to customers, which means that the telecommunications network needs to be operated efficiently and economically. The OAM & P of a network needs to be automated as much as possible to decrease both response time and costs. Cost considerations lead to business management, which also is addressed by the TMN model.
Service Management, business management, and network management can all be accomplished, partially or totally, by using the Oss shown in the figure. System operators interface with the Oss via workstations. The interfaces associated with the various functions and services have been standardized in the TMN model. The interfaces are Q3, F and X. Q3 is the interface between an operations systems and a network element. F is the interface between a workstation and an operations system. Information exchange between operations systems within a TMN is accomplished with the Q3 interface, whereas Oss belonging to different TMNs communicate via the X interface. 2) a. Bit Error Rate Tester: BERT:
77

Course File
BERT A
Modem A Loop Back
Modem B Loop Back
BERT B
Figure 12.2 Bit Error Rate Te ste r (BERT)
BERT is a physical layer monitoring tool Generates and detects bits Bit Error Rate(BER) is calculated by comparing the transmitted pattern with received pattern Loop back is a feature of the modem BER can be measured for a modem or two modems and the link in between b. Protocol Analyzer:
PROTOCOL ANALYZER Raw data transferred on Modem / WAN or LAN Link Data Capture Device
LAN Figur e Analyzes data packets on12.13transmission line includingConfiguration any Pro tocol Analyze r Basic LAN Measurements made locally or remotely Probe (data capture device) captures data and transfers to the protocol analyzer (no storage) Data link between probe and protocol analyzer either dial-up or dedicated link or LAN Protocol analyzer analyzes data at all protocol levels
3) RMON using the ATM: ATM RMON:

Application Layer
Upper Layer Protocols RMON-2 (RFC 2021, 2074)
Netw ork Layer
ATM Protocol IDs for RMON-2 (Additions to RFC 2074)
78
Ethernet RMON (RFC 1757) Token Ring RMON (RFC 1513)
'Base' Layer
Switch Extensions for RMON
ATM RMON
IETF MIBs
Additional MIBs

Course File
Key Points: ATM Forum extended RMON to ATM Switch Extensions and ATM RMON define objects at the base layer ATM protocol IDs for RMON2 define additional objects at the higher levels ATM devices require cell-based measurements and statistics Probe should be able to handle high speed
ATM Technology: ATM Technology is based on: Virtual Path/ Virtual Circuit Fixed Packet Size or Cell Small Packet Size ( 53 bytes) Statistical multiplexing Integrated services Packets in a session take the same path in VP/VC After initial set up, latency is reduced SDH/SONET in WAN uses 155.52 Mbps as basic data rate and is universal ( in contrast to T1 and E1) Transmission medium primarily used in ATM is optical fiber ATM used in LAN for high speed emulating Ethernet LAN
79

Course File
4) RMON1 and its textual conventions: RMON Components:
Data Analyzer
SNMP Traffic
Router
BACKBONE NETWORK
Router
SNMP Traffic
RMON Probe
RMON Probe o Data gatherer- a physical device Data Analyzer o Processor that analyzes data
LAN
RMON: Remote Monitoring It is a standard based network management protocol Allows network information to be gathered at a single workstation Defines additional MIBs to provide a richer set of data about network usage
RMON Benefits: Monitors and Analyzes locally and relays data, Less load on the network Needs no direct visibility by NMS More reliable information Permits monitoring on a more frequent basis and hence faster fault diagnosis Increases productivity for administrators
RMON1 Textual Conventions: Two new data types defined in the RMON1 textual conventions were OwnerString and EntryStatus. Both are extremely useful in the operation of RMON devices, which are used by management systems to measure and produce statistics on network elements. Typically, a network has more than one management elements to create, use and delete the control
80

Course File
parameters in the table. The EntryStatus is used to resolve the conflicts that might arise between management systems in the manipulation of the control tables. The OwnerString is specified in the NVT ASCII character set as DisplayString. The information content of Ownerstring contains the information about the owner, such as IP address, management station name, network managers name, location, or telephone number.
5) TMN Architecture:
TMN Architecture is defined in M.3010, which describes the principles for a TMN. Three architectural perspectives are presented: functional, physical, and information. The functional architecture identifies functional modules, or blocks, in the TMN environment, including the reference points between them, and specifies interface requirements. The physical architecture defines the physical blocks and interfaces between them. The information architecture deals with the information exchange between managed objects and management systems, using a distributed object-oriented approach.
TMN Architecture:
TMN Architecture
Functional Architecture
Physical Architecture Figure 11.6 TM N Archite ctu re
Informational Architecture
TMN Reference Point:

81

Course File
Function Block Reference Point
Function Block
Figure 11.8 TM N Re fe re nce Point
Functional Blocks connected by conceptual interfaces, called reference point Designated by lower case letters ( upper case letter for physical interfaces) x: Interface between operation systems that belong to different domains; e.g., interface between two NMSs belonging to two different domains q3: Interface between two OSFs in the same domain qx: Interface between mediation function such as RMON and agent in the network element f : Interface to the workstation 6) Web Interface to SNMP Management: Two approaches are available to implement a Web Interface on existing SNMP-based management systems. The first and short-term approach is to add a Web Interface to an existing management system. The second is to have a Web-based system with embedded Web agents in the network components. The most common implementation is to establish a Web server on an NMS platform with an interface to the NMS, as shown in the figure. The SNMP NMS implementation is platform and operating system-specific, and the agents in managed objects are SNMP agents. The protocol between the agents and the manager is the SNMP communication protocol, traversing over UDP/IP. The basic architecture of the proxy server is also the same as that in the SNMP NMS with a Web interface. The NMS is replaced with the proxy server, and the NMS console is eliminated, which is an economic advantage. The local Web browser becomes the NMS console for the operation center. Web Interface:
Desktop PC Web Browser
HTTP
NMS Console
82
Web Server SNMP Manager SNMP NMS
SNMP Agent
Managed Objects

Course File
SNMP-based NMS NMS database transferred to Web-server View with Web browser Protocol between NMS and network elements is SNMP HTTP between Web server and browser
Proxy Server:
Desktop PC Web Bro wser
HTTP
Web Ser ver
Man age r Ap plica tio ns SNMP/ Oth er
Pr oxy Ser ver
SNMP / Oth er Ag en t
Man age d Objects
F ig u r e 1 4.2 Pr o xy Se r v e r w ith We b In te r fa ce
83

Course File
Proxy Server: Similar to Web interface No NMS monitor No GUI in manager applications
JNTU SEMESTER EXAM QUESTION PAPERS: The following are the Semester exam question papers conducted by the JNTU for the B.Tech IV IT students. It is the regular exam semester.
Code No: 07A81202
R07
Set No.1
IV B.Tech II Semester Examinations, APRIL 2011 NETWORK MANAGEMENT SYSTEMS Information Technology Time: 3 hours Max Marks: 80 Answer any FIVE Questions All Questions carry equal marks ****** 1. What is meant by MIB (Management Information Base).Give the genetic representation of range information? [16] 2. Give brief description about the following: a) Core application services
84

Course File
[4+6+6]
b) Functional components c) tcpdump
3. a) Give brief description about DMIs MIB b) What are the standards that are available for managing of Management Ap-plication? [8+8] 4. a) Compare the functionalities of TMN functional architecture and TMN Physical architecture b) Discuss about the Implementation Issues of TMN. [10+6]
5. Describe the SNMPv2 Network Management Architecture on Multiple Transport Domains. [16] 6. a) What enhancements are made to RMON2 MIB Group? Explain b) Explain the new data types defined in RMON1 textual conventions. [8+8] 7. Gigabit Ethernet using CSMA/CD is specified to have a 100-meter drop cable. Show that this corresponds to a slot time of 512 bytes to detect collision. Assume a repeater delay of two microseconds. [16] 8. An SNMP manager sends a request for the values of the sysUpTime in the System group and ifType in the interfaces group for ifNumber value of 3. Write the PDUs with the fields in for a) The get-request PDU, and b) The get-response PDU with noSuchName error messages for ifType. [16] ******
Code No: 07A81202
R07
Set No.2
85

Course File
IV B.Tech II Semester Examinations, APRIL 2011 NETWORK MANAGEMENT SYSTEMS Information Technology Time: 3 hours Max Marks: 80 Answer any FIVE Questions All Questions carry equal marks ****** 1. a) Explain the data gathering module in RMON1. b) Describe briefly about functions and tables related to network layer matrix and application level matrix group of RMON2 MIB [8+8] 2. What are objects identifications? Explain the differences between modules identity macro and objects identity macro with an example. [16]
3. Define ranged object, also explain the conceptual views of a managed object. [16]
4. Draw the MIB tree for the SNMP group and explain entities.
[16]
5. a) The bit error rate tester has been used for long time as a network test tool that can test bit error rate and block error rate. Justify? b) List and explain the different network status tools. [10+6]
6. a) Explain the operations system for testing transmission with a neat diagram b) Discuss the operations system for testing transmission. c) Explain the trunk systems of TMN model. [6+6+4] 7. You are given a class B IP address of 145.45.x.y for your network node. As a network engineer, you are asked to configure your network for 126 subnets (Remember that 0 and 1 are reserved). a) How would you configure your address for subnets and hosts?
86

Course File
b) What is the maximum number of hosts that each subnet can accommodate? [8+8] 8. a) With the help of a flow diagram, illustrate how MBeans are accessed. b) Write the differences between CIM managed Objects and DMI managed objects. [10+6] ******
Code No: 07A81202
R07
Set No.3
IV B.Tech II Semester Examinations, APRIL 2011 NETWORK MANAGEMENT SYSTEMS Information Technology Time: 3 hours Max Marks: 80 Answer any FIVE Questions All Questions carry equal marks ****** 1. Describe the SNMP network management architecture with the help of a neat diagram. [16]
87

Course File
[16]
2. Explain the TMN Conceptual Model with neat diagrams.
3. a) What are the advantages of using CIM in WBEM. b) List and explain the various components of web based enterprise management. [6+10] 4. Explain the case histories of networking and management. [16]
5. What are the agent capabilities? Give the skeleton of Agent capabilities macro and explain it with the help of an example. [16] 6. a) Explain the RMON MIB framework for the extensions, as portrayed by the Forum b) Draw the different perspectives of ATM RMON. [8+8] ATM
7. Explain in detail the basic software tools that aid in obtaining network parameters or diagnosing network problem. [16] 8. The following data response information is received by the manager for a get-request with a varBindlist. Compose: a) the get-request PDU, and b) the get-response PDU. Object Error Status Error Index udplnDatagrams udpNoPorts udplnErrors udpOutDatagrams Value Too big udplnErrors 500,000 1,000 5,000 300,000
[16]
******
88

Course File
Set No.4
Code No: 07A81202
R07
IV B.Tech II Semester Examinations, APRIL 2011 NETWORK MANAGEMENT SYSTEMS Information Technology Time: 3 hours Max Marks: 80 Answer any FIVE Questions All Questions carry equal marks ****** 1. a) With the help of a neat diagram explain the WMI architecture. b) Explain briefly about Desktop management interface block diagram. [8+8] 2. Explain the current status and future of Network Management. [16]
3. Explain the evolution of internet Management documents related to SNMPv1?[16] 4. What are the operations of SNMP? Also explain about the genetic maps involved? [16] 5. a) Describe briefly about functions and tables that are related to network layer matrix and application level matrix group of RMON2 MIB. b) Explain the different alarms and events generated by filters of RMON1. [8+8] 6.a) Mention the reasons for using operations system for Traffic Measurement. b) Discuss the operations system for testing transmission. c) List the advantages of TMN. [6+6+4] 7. What are the different network statistics measurement systems? Explain them in detail. [16] 8. Generate as ASN.1 OBJECT-GROUP macro for the address translation group in SNMPv2 implementation. [16]
******
89

NMS Course Modified)

Transféré par

Informations du document

Description originale:

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

NMS Course Modified)

Transféré par

Droits d'auteur :

Formats disponibles

Network Management Systems (elective)

B.TECH IV-IT Department of INFORMATION TECHNOLOGY

LECTURE & MICRO PLAN

1.2 Objectives of the subject:

Network Management Systems (elective)

1.3. JNTU Syllabus with Additional Topics

Network Management Systems (elective)

Network Management Systems (elective)

Network Management Systems (elective)

1.5.Unit wise Summary

Challenges of Information Technology managers

Network Management Systems (elective)

Network Management Systems (elective)

Reg/Addi LCD/ tional OHP/ BB PPT

Communication protocols and standards

Communication protocols and standards Case histories of networking and management.

Challenges of information technology managers, Challenges of information technology managers,

Networking and system management.

Network Management Systems (elective)

Network Management Systems (elective)

SNMPV2Structure of management, Information.

SNMPV2 Abstract Syntax notation concept.

Network management systems

ATM Remote Monitoring. A case study of internet traffic using RMON.

TMN Architecture TMN Architecture TMN Standards

Network Management Systems (elective)

Network Management Systems (elective)

1.7. Subject Contents

1.7.1. Synopsis page for each period (62 pages)

1.7.2. Detailed Lecture notes containing

3.Subjective type questions (approximately 5 to 8 /unit)

4.Objective type questions (approximately 20 to 30 /unit

Network Management Systems (elective)

(ii) Sample Check

(iii)End of the course report by the concerned faculty

Network Management Systems (elective)

Geethanjali College of Engineering and Technology

INFORMATION TECHNOLOGY 2010-11

Semester: IV-IT Classification status (Unrestricted/Restricted ) Distribution List:

Prepared by : 1) Name : 2) Sign : ASSISTANT PROFESSOR Y.KETHAN HARISH

Verified by : 1) Name : 2) Sign :

*For Q.C only 1)Name 2) Sign 3) Design : 4) Date : : :

Approved by (HOD) : 1) Name: 2) Sign : 3) Date :

Network Management Systems (elective)

Geethanjali College of Engineering and Technology

Department Information Technology Course File

NETWORK MANAGEMENT SYSTEMS IV IT 2nd Semester

Network Management Systems (elective)

Objectives of the Subject:

Network Management Systems (elective)

Mapping of course objectives with outcomes

Network Management Systems (elective)

Network Management Systems (elective)

Network Management Systems (elective)

Network Management Systems (elective)

Network Management Systems (elective)

Regional Center Class 1 switch

Regional Center Class 1 switch

Sectional Center Class 2 switch

Sectional Center Class 2 switch

Primary Center Class 3 switch

Primary Center Class 3 switch

Toll Center Class 4 switch