Network Management and SNMP

(Simple Network Management Protocol)

1
 Network Management
 Any complex system with many interacting components must
be monitored, managed and controlled

 In the early 1980 networks expansion prompted the need for

automated network management

2
 Network management
scenarios
 Detecting failure of an interface card in a device

 Host monitoring

 Traffic monitoring to optimize resource deployment

 Detecting rapid changes in routing tables

 Intrusion detection
3
 ISO Network Management Model
FCAPS:

 Fault management

 Configuration management

 Accounting management

 Performance management

 Security Management
4
 ISO Network Management Model
 Fault management – Network faults and problems are
found and fixed
 Configuration management – track devices and their H/w
and S/w configurations
 Accounting management - Network resources are
distributed, and departments are charged for their
network use
 Performance management – quantify, measure, report,
analyze and control performance of network components
to minimize congestion and bottlenecks
 Security Management – control access to network
resources according to some well-defined policy
5
Network Management Architecture

6
Simple Network Management Protocol

 Protocol for network management, part of TCP/IP suite

 Current version SNMPv3

 Includes communication protocol, set of data definitions and

database schema

 Basic components:
Managers/NMS
Managed devices
SNMP Agents
MIB (Management Information Base)

7
SNMP

 Simple Network Management Protocol (SNMP) is a

set of protocols for network management and
monitoring. These protocols are supported by many
typical network devices such as routers, hubs, bridges,
switches, servers, workstations, printers, modem racks
and other network components and devices
 The SNMP protocol is included in the application
layer of TCP/IP as defined by the Internet Engineering
Task Force (IETF).

8
Network Management Architecture

9
MIB (Management Information Base)
 MIB – virtual information store for a collection of
managed objects

 Describes structure of management data on managed

device

 Each variable that describes some part of device

configuration is identified by a unique OID (object
ID)

 Vendors define MIB variables for their own use

 MIB II – standard MIB implemented by all managed

objects
10
SMI (Structure of management information)

 SMI is the language used to define the management

information residing in a managed object – logically

 SMI states that each managed object should have a

name, syntax and encoding

 SMI is a subset of ASN.1 - a standard for describing

data that is independent of machine-specific encoding.

11
SNMP Transport

12
SNMP Transport

13
SNMP Operations

 get
 getnext
 getbulk (SNMPv2 and SNMPv3)
 getresponse
 set
 trap
 inform (SNMPv2 and SNMPv3)

14
SNMP Operations

 Get and getresponse

15
SNMP Operations
 Getnext – retrieve a group of values

16
SNMP Operations

 Getbulk – retreive a section of a table

17
SNMP Operations

 Set – change value or create a new row in the table

18
SNMP Operations

 Trap – asynchronous operation

19
Primary Goals of SNMP

■ Check message integrity - To verify that each received message has not
been modified during its transmission .

■ User authentication - To verify the identity of the user on whose behalf a

received message claims to have been generated .

■ Message timestamp – to detect outdated messages

■ Message confidentiality - To assure that the contents of each received

message are protected/encrypted.

20
Primary Goals of SNMPv3

21