Vous êtes sur la page 1sur 48

Telecommunications

Networks
Management
Credit hours: 03

TNM: Telecommunication Network Management

Simple Network
Management Protocol
Lecture: 8

TNM: Telecommunication Network Management

Contents
Network

management architectures
SNMP basic concepts
SNMP versions and security
SNMP and UDP
Structure of Management Information
SNMP operation
Conclusion

TNM: Telecommunication Network Management

Network management
architectures
Several

organizations have developed network


management architectures, including

International Telecommunication Union (ITU)

International Organization of Standardization (ISO)

Telecommunication Management Network (TMN)


OSI management

Internet Engineering Task Force (IETF)

Simple Network Management Protocol (SNMP)

TNM: Telecommunication Network Management

SNMP basic concepts

SNMP is a framework that provides facilities for


managing and monitoring network resources on the
Internet.
Components of SNMP:
SNMP agents
SNMP managers
Management Information Bases (MIBs)
SNMP
manager
SNMP protocol itself
SNMP
protocol
messages

SNMP agent

SNMP agent

SNMP agent

TNM: Telecommunication Network Management

SNMP basic concepts

SNMP agent is software that runs on network equipment


and that maintains information about its configuration and
current state
Information in the database is described by Management
Information Bases (MIBs)
An SNMP manager is an application program that contacts
an SNMP agent to query or modify the database at the
agent
SNMP protocol is the application layer protocol used by
SNMP agents and managers to send and receive data.

TNM: Telecommunication Network Management

SNMP versions and security

TNM: Telecommunication Network Management

SNMP Versions
Three

SNMPv1 (1990)
SNMPv2c (1996)

versions are in use today:

Adds GetBulk function and some new types


Adds RMON (remote monitoring) capability

SNMPv3 (2002)

SNMPv3 started from SNMPv1 (and not SNMPv2c)


Addresses security

All

versions are still used today


Many SNMP agents and managers support all
three versions of the protocol
TNM: Telecommunication Network Management

SNMP Security

SNMPv1 uses plain text community strings for


authentication without encryption

SNMPv2 was supposed to fix security problems,


but effort de-railed (The c in SNMPv2c stands
for community).

TNM: Telecommunication Network Management

Security levels in SNMPv2


SNMP has three security levels:
noAuthNoPriv: Authentication with matching a user name
authNoPriv: Authentication with MD5 or SHA message
digests
authPriv: Authentication with MD5 or SHA message
digests, and encryption with DES encryption
Compare this to SNMPv1 and SNMPv2c:
SNMPv1, SNMPv2: Authentication with matching a
community string.
TNM: Telecommunication Network Management

Security levels in SNMPv3


Security

model of SNMPv3 has two components:

1. Instead of granting access rights to a community,


SNMPv3 grants access to users.
2. Access can be restricted to sections of the MIB
(Version-based Access Control Module (VACM).
Access rights can be limited

by specifying a range of valid IP addresses for a user or


community,
or by specifying the part of the MIB tree that can be
accessed.

TNM: Telecommunication Network Management

SNMP and UDP

TNM: Telecommunication Network Management

SNMP and UDP


SNMP

uses UDP as transport protocol


between manager and user

le
b
ea
g
an
UDP port 161 for sending and receiving manager information
h
c
r
UDP port 162 for receiving traps from agents ed o
Fix

Connectionless

is unreliable

Timeout by manager
Agent has no mean to know

TNM: Telecommunication Network Management

SNMP and UDP


Application

Request to SNMP agent


Trap to NMS

UDP

UDP header with port


address

IP

Deliver SNMP to destination

MAC

Getting packet from physical


Forward to upper stack

Pen pal
Intent to write (app)
Envelop address (UDP)
Postal stamp (IP)
Mailman pick (MAC)

TNM: Telecommunication Network Management

SNMP communities

TNM: Telecommunication Network Management

SNMP communities
Notion

of Communities to ensure trust


between agent and manager
Community names are used to define where
an SNMP message is destined for
Set up your management applications to
monitor and receive traps from certain
community names

TNM: Telecommunication Network Management

SNMP communities
Set

up your agents to belong to certain


communities
Agent has three communities

Read only, read-write, trap

Security

of information

Agent: Configure firewall


161 from NMS
Manager
162 only from selected managed stations

TNM: Telecommunication Network Management

SNMP communities

TNM: Telecommunication Network Management

Structure of management
information

TNM: Telecommunication Network Management

Structure of management
information
Representation

of data in the context of

SNMP
Place restriction on the types of variables
allowed in MIB
Specify the rules for naming those variables
Create rules for defining variable type
SMI types

SMIv1
SMIv2
TNM: Telecommunication Network Management

Structure of management
information
The

definition of SMI can be broken into three


attributes

Name: Uniquely defines managed object

Type and syntax: The managed objects data type is


defined using Abstract Syntax Notation (ANS.1)

Numeric form
Human readable

Manner of data representation and transmission


Machine independent

Encoding: Instance of managed objects are encoded


using Basic Encoding Rules (BER)

Encoding and decoding for transport


TNM: Telecommunication Network Management

Structure of management
information . Naming OID
Tree

like hierarchy
Series of integers/names based on node in
tree, separated by dots

Node at tope => Root node


Node with children => Subtree node
Node without children => Leaf node

TNM: Telecommunication Network Management

Structure of management
information .. Type and syntax
The

syntax provide definitions of the managed


objects through ASN.1
Why ASN.1

Keep standards documents unambiguous


simplify the implementation of network management
protocols
guarantee interoperability

TNM: Telecommunication Network Management

Structure of management
information .. Basic encoding rules
Basic

Encoding Rules

The relationship between ASN.1 and BER


parallels that of source code and machine code.

CCITT X.209 specifies the Basic Encoding Rules

All SNMP messages are converted / serialized


from ASN.1 notation into smaller, binary data
(BER)

TNM: Telecommunication Network Management

SMI in SNMP versions

TNM: Telecommunication Network Management

Structure of management
information
--------- SMIv1
SMIv1 is described in RFCs 1155, 1212, 1215
These RFCs describe:

The subset of the ASN.1 language that is used in


MIBs

definition of the high-level structure of the Internet


branch (iso(1).org(3).dod(6).internet(1)) of the MIB
naming tree

the definition and description of an SNMP managed


object
TNM: Telecommunication Network Management

Structure of management
information
--------- SMIv1
Textual

and numneric

Iso.org.dod.internet
1.3.6.1

Directory branch is not used


Mgnt is used for management
Experimental branch for research
Private is for individual or
organization to define

TNM: Telecommunication Network Management

Structure of management
information --------- Syntax and coding
S. no Data type

Description

Integer

Signed 32-bit integer. Specify enumerated type within the context of a single managed object

Octet string

used to represent text strings, but also sometimes used to represent physical addresses

Counter

32 bits; used to track information such as the number of octets sent and received on an interface or the
number of errors and discards seen on interface

Object identifier

A dotted-decimal string that represents a managed object within the object tree. For example,
1.3.6.1.4.1.9 represents Cisco Systems private enterprise OID

NULL

Not currently used in SNMP

IpAddress

Represents a 32-bit IPv4 address. Neither SMIv1 nor SMIv2 discusses 128-bit IPv6 addresses

Network address

Same as the IpAddress type, but can represent different network address types

Gauge

Unlike a Counter, a Gauge can increase and decrease at will, but it can never exceed its maximum
value. The interface speed on a router is measured with a Gauge

TimeTicks

TimeTicks measures time in hundredths of a second. Uptime on a device is measured using this
datatype.

Opaque

TimeTicks measures time in hundredths of a second. Uptime on a device is measured using this
datatype.

TNM: Telecommunication Network Management

Structure of management
information --------- SNMPv2

SMIv1 is described in RFCs 1442, 1443, 1444


These RFCs describe:

SMIv2 is a backward compatible update to SMIv1

The only exception is the Counter64 type defined by


SMIv2

Counter64 cannot be created in SMIv2

RFC 2089 defines how bilingual (SMIv1 & SMIv2)


agents handle the Counter64 data type

TNM: Telecommunication Network Management

Extension to SMI in SNMPv2


Added

snmpv2
OID of the new branch

1.3.6.1..6.3.1.1

Iso.org.dod.internet,snmpv2.snmpModule

TNM: Telecommunication Network Management

Structure of management
information --------- Syntax and coding
S. no Data type

Description

Integer32

Same as integer

Counter32

Same as counter

Gauge32

Same as Gauge

Counter64

Similar to Counter32, but its maximum value is 18,446,744,073,709,551,615. Counter64 is ideal


for situations in which a Counter32 may wrap back to 0 in a short amount of time.

Bits

An enumeration of nonnegative named bits.

TNM: Telecommunication Network Management

Structure of management
information --------- Syntax and coding
S. no Textual

Description

DisplayString

A string of NVT ASCII characters. A DisplayString can be no more than 255 characters in
length

PhysAddress

A media- or physical-level address, represented as an OCTET STRING

MacAddress

Defines the media-access address for IEEE 802 (the standard for LANs) in canonicala order. (In
everyday language, this means the Ethernet address.) This address is represented as six octets

TruthValue

Defines both true and false Boolean values.

TestAndIncr

Used to keep two management stations from modifying the same managed object at the same
time.

TimeStamp

Measures the amount of time elapsed between the devices system uptime and some event or
occurrence.

TimeInterval

Measures a period of time in hundredths of a second. TimeInterval can take any integer value
from 02147483647

TNM: Telecommunication Network Management

Structure of management
information --------- Example
ASN.1 is nothing more than a language definition. It is
similar to C/C++ and other programming languages.
Syntax examples:
-- two dashes is a comment -- The C equivalent is written in the comment
MostSevereAlarm ::= INTEGER

-- typedef MostSevereAlarm int;

circuitAlarms MostSevereAlarm ::= 3

-- MostSevereAlarm circuitAlarms = 3;

MostSevereAlarm ::= INTEGER (1..5) -- specify a valid range


ErrorCounts ::= SEQUENCE {
circuitID

OCTET STRING,

erroredSeconds

INTEGER,

unavailableSeconds INTEGER
}

-- data structures are defined using the SEQUENCE keyword


TNM: Telecommunication Network Management

SNMP operations

TNM: Telecommunication Network Management

SNMP operations

Basic Message format


Message Length
Message Version
Community String

Message Preamble

PDU Header

PDU Body

SNMP Protocol
Data Unit

TNM: Telecommunication Network Management

SNMP operations
Protocol

Data Unit (PDU) is the message


format that manager and agent use
Standard PDU format for SNM operations

Get
Get-next
Get-bulk (SNMPv2 and SNMPv3)
Set
Get-response
Trap
Notification (SNMPv2 and SNMPv3)
Inform (SNMPv2 and SNMPv3)
Report (SNMPv2 and SNMPv3)
TNM: Telecommunication Network Management

The get operation

Initiated

by NMS
Agent responds to the best of its ability
How does the agent know, what NMS is
looking for?

Variable binding:

Agent

respond by get-response
TNM: Telecommunication Network Management

The getnext operation


Retrieve

a group of values from MIB

For each MIB value generated commands are

Getnext request; Getnext response

OID

is sequence of integers

Depth-first search

Getnext

commands are issued in a loop

Loop terminate when end of MIB is reached

TNM: Telecommunication Network Management

The snmwalk operation


snmwalk

is based on
lexicographic order of
MIB tree
At each node in tree, visit
the lowest number in the
branch FIRST

TNM: Telecommunication Network Management

The snmwalk operation

TNM: Telecommunication Network Management

The getbulk operation

Retrieve

large section of a table at once


Message size is limited by the agent ability
getbulk must contain

nonrepeater
max-repititions

Getbulk

(N+(M*R))

TNM: Telecommunication Network Management

The set operation


The

set operation
Change value of a managed object
Create new row in table

TNM: Telecommunication Network Management

SNMP Traps
Traps

are sent to a management system by


an SNMP agent process
When a trappable event occurs, a trap
message is generated by the agent and is
sent to a trap destination
Traps have a priority associated with them -Critical, Major, Minor, Warning, Marginal,
Informational, Normal, Unknown

TNM: Telecommunication Network Management

Traps generation
Traps

are generated by the agent


Destined to the destination
No acknowledgement
Cases of traps generation

Network interface get down


Network interface came back up
The fan on a switch or a router has failed

TNM: Telecommunication Network Management

Traps handling
Traps

are received by a management


application
Traps handling

Poll the agent that sent the trap for more information about the event

Log the reception of the trap.

Completely ignore the trap

NMS

can send an email/voice call to the


network administrator.

TNM: Telecommunication Network Management

Traps handling
Traps

are identified by its generic trap number

Trap

Description

coldStart (0)

the agent has rebooted. All management variables will be reset;

warmStart (1)

the agent has reinitialized itself. None of the management variables


will be reset.

linkDown (2)

Sent when an interface on a device goes down.

linkUp (3)

Sent when an interface on a device comes back up.

authenticationFailure (4)

Indicates that someone has tried to query your agent with an incorrect
community
string;

egpNeighborLoss (5)

Indicates that an EGP neighbor has gone down

enterpriseSpecific (6)

Indicates that the trap is enterprise-specific.

TNM: Telecommunication Network Management

Conclusions
SNMP

is software based network control


SNMP is in upgradation stages
SNMPs SMI is expanding
SNMP operations are becoming complex

TNM: Telecommunication Network Management

Questions??

TNM: Telecommunication Network Management

Vous aimerez peut-être aussi