Structure Of Management Information Version 2 example essay topic

Computer Network & ManagementAssignmentTitle: Structure of Management Information (SMI) Structure of Management Information (SMI): In the context of network management, for the Structure of Management Information (SMI): a) Name its three hierarchical layers. The Structure of Management Information (SMI) standard is responsible for defining the rules for how the Management Information Base (MIB) objects are structured, described and organized. SMI is a data definition language allows dissimilar devices to communicate by ensuring that they use a universal data representation for all management information. SMI is needed to ensure the syntax and semantics of the network management data are well defined and unambiguous. [TCP / IP Guide] The three hierarchical layers of the Structure of Management Information are the base data types, object-type and module-identity. b) Explain the function of each layer. The Base Data Type layer is use in the SYNTAX clause of the OBJECT-TYPE macro that must be present.

It defines the abstract data structure corresponding to the object. It includes the following eleven basic data types: INTEGER, Integer 32, Unsigned 32, OCTET STRING, OBJECT IDENTIFIER, IPaddress, Counter 32, Counter 64, Gauge 32, Time Ticks, and Opaque. Any restriction on size, range or enumerations specified in this SYNTAX clause represents the maximal level of support which makes 'protocol sense'. [RFC 2578] The OBJECT-TYPE layer is use to specify the data type, status, and the semantics of managed objects. It has basic of five mandatory characteristics namely, OBJECT-NAME, SYNTAX, MAX ACCESS, STATUS, and DESCRIPTION, optionally with OPTIONAL-CHARACTERISTICS. The OBJECT-NAME is obviously.

The SYNTAX clause specifies the basic data type of the object. The MAX-ACCESS clause specifies the managed object either can be read-create, read-write, read-only, accessible for notify only, or not accessible. The STATUS clause specifies the object is current, obsolete or deprecated. The DESCRIPTION clause contains a textual definition of the object.

[RFC 2578] [RFC 2013] The MODULE-IDENTITY layer is used to express concisely the semantics of an information module. It groups related object into a Management Information Base (MIB) module. Each MODULE-IDENTITY contains a number of clauses like the LAST-UPDATED clause, ORGANIZATION clause, CONTACT-INFO clause, DESCRIPTION clause and REVISION clause. Theses clauses document the date of last updated, the organization and contact information of the author of the module, and a textual description of the module, and the revision information such as the date of revision and the revision description. [RFC 2012] [TCP-IP Guide] c) For each layer, give four examples of defined entities. Four examples of Base Data Types 1.

Integer / Integer 32 [RFC 2578] Integer / Integer 32 is a 32-bit signed integer in two's complement notation, capable of holding a value between! V 2,147,483,648 and +2,147,483,647.2. Network Address / IpAddress [RFC 2578] It is an IP address, encoded as a 4-byte octet string. 3. Time Ticks [RFC 2578] Time Ticks is a 32-bit unsigned integer that indicates the number of hundredths of seconds since some arbitrary start date.

Used for time stamping and to compute elapsed time. 4. Four examples of Object Type 1) Total number of input data grams successfully delivered ipInDelivers OBJECT-TYPESYNTAX Counter 32 MAX-ACCESS read-onlySTATUS currentDESCRIPTION " The total number of input data grams successfully delivered to IP user-protocols (including ICMP). ' : : = { ip 9 } [RFC 2011] 2) TCP Maximum number of connectionstcpMaxConn OBJECT-TYPESYNTAX Integer 32 (-1 | 0... 2147483647) MAX-ACCESS read-onlySTATUS currentDESCRIPTION " The limit on the total number of TCP connections the entity can support.

In entities where the maximum number of connections is dynamic, this object should contain the value -1. ' : : = { tcp 4 } [RFC 4022] 3) UDP Local port numberudpLocalPort OBJECT-TYPESYNTAX INTEGER (0... 65535) MAX-ACCESS read-onlySTATUS currentDESCRIPTION " The local port number for this UDP listener. ' : : = { udp Entry 2 } [RFC 2013] 4) Object counter on total number of packets counted on this priority levelsmonPrioStatsPkts OBJECT-TYPESYNTAX Counter 32 UNITS 'packets " MAX-ACCESS read-onlySTATUS currentDESCRIPTION " The total number of packets counted on this priority level. ' : : = { smonPrioStatsEntry 2 } [RFC 2613] Four examples of Module Identity 1) Internet Protocol MIBipMIB MODULE-IDENTITYLAST-UPDATED '9411010000 Z'ORGANIZATION 'IETF SNMPv 2 Working Group " CONTACT-INFO' Keith McCloghriePostal: Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USPhone: +1 408 526 5260 Email: 'DESCRIPTION " The MIB module for managing IP and ICMP implementations, but excluding their management of IP routes. ' REVISION '9103310000 Z'DESCRIPTION " The initial revision of this MIB module was part of MIB-II. ' : : = { m ib-2 48} [RFC 2011] 2) Transmission Control Protocol MIBtcpMIB MODULE-IDENTITYLAST-UPDATED '200502180000 Z' -- 18 February 2005 ORGANIZATION " IETF IPv 6 MIB Revision Team web 'CONTACT-INFO " Rajiv Raghunarayan (editor) Cisco Systems Inc. 170 West Tasman Drive San Jose, CA 95134 Phone: +1 408 853 9612 Email: Send comments to 'DESCRIPTION " The MIB module for managing TCP implementations. Copyright (C) The Internet Society (2005).

This version of this MIB module is a part of RFC 4022; see the RFC itself for full legal notices. ' REVISION '200502180000 Z' -- 18 February 2005 DESCRIPTION " IP version neutral revision, published as RFC 4022. ' REVISION '9411010000 Z'DESCRIPTION " Initial SMIv 2 version, published as RFC 2012. ' REVISION '9103310000 Z'DESCRIPTION " The initial revision of this MIB module was part of MIB-II. ' : : = { m ib-2 49 } [RFC 4022] 3) User Datagram Protocol MIBudpMIB MODULE-IDENTITYLAST-UPDATED '9411010000 Z'ORGANIZATION 'IETF SNMPv 2 Working Group " CONTACT-INFO' Keith McCloghriePostal: Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USPhone: +1 408 526 5260 Email: 'DESCRIPTION " The MIB module for managing UDP implementations. ' REVISION '9103310000 Z'DESCRIPTION " The initial revision of this MIB module was part of MIB-II. ' : : = { m ib-2 50 } [RFC 2013] 4) MIB module for managing Remote Monitoring device implementations for Switched NetworksswitchRMON MODULE-IDENTITYLAST-UPDATED '9812160000 Z'ORGANIZATION 'IETF RMON MIB Working Group " CONTACT-INFO " IETF RMON MIB WG Mailing list: Rich Waterman Allot Networks Inc.

Tel: +1-408-559-0253 Email: Bill LahayeXylan Corp. Tel: +1-800-995-2612 Email: Dan RomascanuLucent Technologies Tel: +972-3-645-8414 Email: Steven WaldbusserInternational Network Services (INS) Tel: +1-650-318-1251 Email: 'DESCRIPTION " The MIB module for managing remote monitoring device implementations for Switched Networks' -- revision history REVISION '9812160000 Z' -- 16 Dec 1998 midemightDESCRIPTION 'Initial Version, published as RFC 2613. ' : : = { rm on 22 } [RFC 2613] Reference List [Bradley] Tony Bradley, VPN's: IPSec vs. SSL, web p. htm, 2005 [D CCP] E. Kohler, M. Handley & S. Floyd, Datagram Congestion Control Protocol, Internet Engineering Task Fore, November 2004 [Ixia, IPv 6] Dean Lee, Elliott Stewart, Internet Protocol version 6 (IPv 6) Conformance and Performance Testing, White Paper, Ixia, 2004 [Ixia, IPSec] Ixia, IPSec Virtual Private Networks Conformance and Performance Testing, White Paper, Ixia, 2003 [Kurose & Ross] James F Kurose & Keith W Ross, Computer Networking! V A Top Down Approach Featuring the Internet, (2nd Edition), Addision-Wesley, ISBN: 0 321 17644-8 (the International Edition), ISBN 0-201-97699-4. [Netilla 1] Netilla Networks Inc, A Comparison of VPN Solutions: SSL vs. IPSec: A Netilla Networks White Paper, 2003 [Netilla 2] Netilla Networks Inc, A Functional and Cost Comparison of VPN Solutions: SSL vs. IPSec, 2002 [Perkins] Colin Perkins, Building Adaptive Applications: On The Need For Congestion Control, Dec 2004 [POP 3] POP 3, web g ci 212805, 00. html [RFC 768] J. Postel, User Datagram Protocol, RFC 768, Aug 1980 [RFC 1752] S. Bradner & A. Mankind, The Recommendation for the IP Next Generation Protocol, RFC 1752, January 1995 [RFC 1939] J. Myers, Carnegie Mellon & M. Rose, Post Office Protocol - Version 3, RFC 1939, May 1996 [RFC 2011] K. McCloghrie, SNMPv 2 Management Information Base for the Internet Protocol using SMIv 2, RFC 2011, November 1996 [RFC 2013] K. McCloghrie, SNMPv 2 Management Information Base for the User Datagram Protocol using SMIv 2, RFC 2013, November 1996 [RFC 2131] N R. Drops, Dynamic Host Configuration Protocol, RFC 2131, March 1997 [RFC 2401] S. Kent, R. Atkinson, Security Architecture for the Internet Protocol, November 1998 [RFC 2460] S. Deering, Internet Protocol, Version 6 (IPv 6), RFC 2460, December 1998 [RFC 2578] K. McCloghrie, D. Perkins, J. Schoenwaelder, Structure of Management Information Version 2 (SMIv 2), RFC 2578, April 1999 [RFC 2579] K. McCloghrie, D. Perkins, J. Schoenwaelder, Textual Conventions for SMIv 2, RFC 2579, April 1999 [RFC 2580] K. McCloghrie, D. Perkins, J. Schoenwaelder, Conformance Statements for SMIv 2, RFC 2580, April 1999 [RFC 2613] R. Waterman, B. Lahaye, D. Romascanu, S. Waldbusser, Remote Network Monitoring MIB Extensions for Switched Networks Version 1.0, RFC 2613, June 1999 [RFC 4022] R. Raghunarayan, Transmission Control Protocol (TCP), RFC 4022, Mar 2005 [Router] Curt Franklin, How Routers Work? web 2003 [TCP / IP Guide] Charles M. Kozierok, The TCP / IP Guide, web Version 2.0, June 7, 2004. [UTP Cable] Cabling, web 2/cabling. htm [UDP Apps] web 1] Roger A. Grimes, UDP vs. TCP, web Oct 2003 [VPN] Peter Southwick, Virtual Private Network Implementation and Concepts, web August 2003

Bibliography

James F Kurose & Keith W Ross, Computer Networking! Michael J. Palmer & Robert Bruce Sinclair, Advanced Networking Concepts, Course Technology, ISBN 0-7895-0195-3 Houston H. Carr & Charles A. Snyder, The Management of Telecommunications- Business Solutions to Business Problems, The McGraw-Hill Companies, ISBN 0-256-21961-3 William Stallings & Richard Van S lyke, Business Data Communications, (Third Edition), Prentice Hall, ISBN 0-13-594581-X.