Scribd
Upload
6 views

Chapter28 SNMP

Uploaded by

Huy Truong Dinh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
6 views

Chapter28 SNMP

Uploaded by

Huy Truong Dinh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 39

Chapter 28

Network Management:
SNMP

28.1 Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or display.
28--1 NETWORK MANAGEMENT SYSTEM
28

We can say that the functions performed by a network


management system can be divided into five broad
categories::
categories configuration management,
management fault
management, performance management, security
management and accounting management
management, management..
Topics discussed in this section:
Configuration Management
Fault Management
Performance Management
Security Management
Accounting Management

28.2
Figure 28.1 Functions of a network management system

28.3
28--2 SIMPLE NETWORK MANAGEMENT
28
PROTOCOL (SNMP)

The Simple Network Management Protocol (SNMP) is a


framework for managing devices in an internet using
the TCP/IP protocol suite
suite.. It provides a set of
fundamental operations for monitoring and maintaining
an internet
internet..
Topics discussed in this section:
Concept
Management Components
Structure of Management Information (SMI)
Management Information Base (MIB)
SNMP

28.4
Figure 28.2 SNMP concept

28.5
Figure 28.3 Components of network management on the Internet

28.6
Note

SNMP defines the format of packets


exchanged between a manager and
an agent.
agent It reads and changes the
status (values) of objects (variables)
i SNMP packets.
in k t

28.7
Note

SMI defines the general rules for naming


objects defining object types (including
objects,
range and length), and showing how to
encode objects and values. SMI does
j
not define the number of objects an
entity should manage or name the
objects to be managed or define the
association between the objects and
their values
values.
28.8
Note

MIB creates
t a collection
ll ti off namedd
objects, their types, and their
relationships to each other
in a
an e
entity
t ty to be managed.
a aged

28.9
Note

We can compare the task of network


management to the task of writing a program.

❏ Both tasks need rules. In network


management this is handled by SMI.
❏ Both tasks need variable declarations. In
network management this is handled by MIB.
❏ Both tasks have actions performed by
statements. In network management this is
handled by SNMP.

28.10
Figure 28.4 Management overview

28.11
Figure 28.5 Object attributes

28.12
Figure 28.6 Object identifier

28.13
Note

All objects
j managed
g by y SNMP are given
g
an object identifier.

The object identifier always starts with


136121
1.3.6.1.2.1.

28.14
Figure 28.7 Data type

28.15
Table 28.1 Data types

28.16
Figure 28.8 Conceptual data types

28.17
Figure 28.9 Encoding format

28.18
T bl 28.2
Table 28 2 Codes
C d for
f data
d types

28.19
Figure 28.10 Length format

28.20
Example 28.1

Figure 28.11 shows how to define INTEGER 14.

Figure 28.11 Example 28.1, INTEGER 14

28.21
Example 28.2

Figure 28.12 shows how to define the OCTET STRING


“HI”.

Figure 28.12 Example 28.2, OCTET STRING “HI”


HI

28.22
Example 28.3

Figure 28.13 shows how to define ObjectIdentifier


1.3.6.1 (iso.org.dod.internet).

Fi
Figure 28 13 Example 28.3, ObjectIdentifier 1.3.6.1
28.13

28.23
Example 28.4

Figure 28.14 shows how to define IPAddress 131.21.14.8..

Figure
g 28.14 Example
p 28.4, IPAddress 131.21.14.8.

28.24
Figure 28.15 mib-2

28.25
Figure 28.16 udp group

28.26
Figure 28.17 udp variables and tables

28.27
Figure 28.18 Indexes for udpTable

28.28
Figure 28.19 Lexicographic ordering

28.29
Figure 28.20 SNMP PDUs

28.30
Figure 28.21 SNMP PDU format

28.31
Table 28.3 Types of errors

28.32
Figure 28.22 SNMP message

28.33
Table 28.4 Codes for SNMP messages

28.34
Example 28.5

In this example, a manager station (SNMP client) uses


the GetRequest message to retrieve the number of UDP
datagrams that a router has received. There is only one
VarBind
i d entity.
i The h corresponding
di MIB variable
i bl related
l d
to this information is udpInDatagrams with the object
id ifi 1.3.6.1.2.1.7.1.0.
identifier 1 3 6 1 2 1 1 0 Theh manager wants to retrieve
i
a value (not to store a value), so the value defines a null
entity.
i Figure
Fi 28 23 shows
28.23 h the
h conceptuall view
i off the
h
packet and the hierarchical nature of sequences. We have
used
d white
hi andd colored
l d boxes
b f the
for h sequences andd a
gray one for the PDU. The VarBind list has only one
V Bi d
VarBind.
28.35
Example 28.5 (continued)

The variable is of type 06 and length 09. The value is of


type 05 and length 00. The whole VarBind is a sequence
of length 0D (13). The VarBind list is also a sequence of
l
length
h 0F (15).
( ) Theh GetRequest
G PDU is
i off length
l h ID (29).
( 9)
Now we have three OCTET STRINGs related to the
security
i parameter, security
i model,
d l andd flags.
fl Then
h we
have two integers defining maximum size (1024) and
message ID (64).
(64) The
Th header
h d is i a sequence off length
l h 12,
12
which we left blank for simplicity. There is one integer,
version
i (version
( i 3).3) The
Th whole
h l message isi a sequence off
52 bytes. Figure 28.24 shows the actual message sent by
the
h manager station
i (client)
( li ) to the
h agent (server).
( )
28.36
Figure 28.23 Example 28.5

28.37
Figure 28.24 GetRequest message

28.38
Figure 28.25 Port numbers for SNMP

28.39

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy