1 / 18

CSEE W4140 Networking Laboratory

CSEE W4140 Networking Laboratory. Lecture 11: SNMP Jong Yul Kim 04.15.2009. Annoucements. Visit to TelioSonera’s NY POP. Network management. Network operators need tools to monitor and manage networks remotely. True even if the network is relatively small. Examples:

philip-avila
Download Presentation

CSEE W4140 Networking Laboratory

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CSEE W4140Networking Laboratory Lecture 11: SNMP Jong Yul Kim 04.15.2009

  2. Annoucements • Visit to TelioSonera’s NY POP

  3. Network management • Network operators need tools to monitor and manage networks remotely. • True even if the network is relatively small. • Examples: • How many IP fragments did this router create? • How long has the server been running? • Which host is about to shutdown? • Types of management • Performance • Fault

  4. Network management architecture

  5. Components of the network management architecture • Managing entity is the central management station within the network: “the administrator’s console” • Managed device is the machine we’re interested in monitoring / controlling • Managed objects are pieces of hardware within the managed device, e.g. network interface card, and the set of configurations for hardward and software • Management Information Base (MIB) is the information of interest related to managed objects, e.g. routing table • Network management agent is a program that runs on the managed device which communicates with the managing entity. • Network management protocol is the protocol used between the agent and the managing entity

  6. Four parts of SNMP • Network management objects • Management Information Base (MIB) • This is the value that we’re interested in monitoring or controlling. • A MIB module is a collection of related MIBs. • Data definition language • Structure of Management Information (SMI) • This defines the format of MIBs such as data type and object model.

  7. Four parts of SNMP • Protocol • Simple Network Management Protocol (SNMP) • This is the protocol used between the managing entity and the agent. • Security and administration capabilities • MIB and SMI are independent of the protocol. The protocol is independent of MIB and SMI.

  8. SMI • SMI is used to define the syntax and semantics of management objects. • It defines basic data types and higher level constructs, such as OBJECT-TYPE and MODULE-TYPE. • SMI is a subset of ASN.1 (Abstract Syntax Notation 1), which adopts a {machine,OS,language}-independent method for describing data and rules for transmitting that data

  9. SMI basic data types

  10. SMI OBJECT-TYPE ipForwDatagrams OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS current DESCRIPTION "The number of input datagrams for which this entity was not their final IP destination, as a result of which an attempt was made to find a route to forward them to that final destination. In entities which do not act as IP Gateways, this counter will include only those packets which were Source-Routed via this entity, and the Source- Route option processing was successful." ::= { ip 6 } Object Identifier (OID) MIB module

  11. Organization of managed objects • Organized in a tree-like hierarchy • Each node is named with an OID. • OIDs reflect the structure of the hierarchy. • The OID 1.3.6.1.2.1 (iso.org.dod.internet.mgmt.mib-2) is at the top of the hierarchy for all managed objects of the MIB-II. • Manufacturers of networking equipment can add product specific objects to the hierarchy.

  12. MIBs • A MIB specifies the managed objects, which have OIDs. • The OID is specified in a MIB file. • In Linux, MIB files are in the directory /usr/share/snmp/mibs • Multiple MIB files • MIB-II (defined in RFC 1213) defines the managed objects of TCP/IP networks • When an SNMP manager requests an object, it sends the OID to the SNMP agent.

  13. UDP Example

  14. SNMP Protocol • SNMP manager and an SNMP agent communicate using the SNMP protocol • Generally: Manager sends queries and agent responds • Exception: Traps are initiated by agent. Notice UDP port 161

  15. SNMP message types

  16. Traps • Traps are messages that are asynchronously sent by an agent to a manager • Traps are triggered by an event • Defined traps include: • linkDown: Even that an interface went down • coldStart - unexpected restart (i.e., system crash) • warmStart - soft reboot • linkUp - the opposite of linkDown • (SNMP) AuthenticationFailure

  17. Homework • Prelab 9 due this Friday • Please write your own answers! • Lab report 8 due next week before labs

  18. Main Points of Lab 9 • SNMP • MIBs • SNMP requests and responses • Security • Traps • Note: You need to download files from web and bring it to the labhttp://www.comm.utoronto.ca/~jorg/teaching/itlab/links/conf/lab9/snmpd.conf

More Related