Chapter 4 SNMPv1 Network Management: Organization and Information Models

Chapter 4

SNMPv1 Network Management:

Organization and Information Models

1
Network Management: Principles and Practice
© Mani Subramanian 2011
Chapter 4 SNMPv1 Network Management: Organization and Information Models

Objectives
• IETF SNMP standard
• History
• RFC, STD, and FYI
• Organization Model
• 2- and 3-tier models
• Manager and agent
• Management messages
• Structure of management information, SMI
• Object type and instance
• Scalar and aggregate managed objects
• Management information base, MIB
• NMS physical and virtual databases

• IETF MIB-2 standard

2
Network Management: Principles and Practice
© Mani Subramanian 2011
Chapter 4 SNMPv1 Network Management: Organization and Information Models

Case Histories
• AT&T Network Management Centers
• Network Operations Center
• Network Control Centers
• Monitors the network status
• Self-healing
• CNN World Headquarters
• Performance Management
• Fault Management
• Monitoring alarms
• Determines causes of failures
(Artificial Intelligence)
• Centralized troubleshooting of NIC (remotely)
• Performance degradation due to NMS
• Network may come down due to NM traffic
• Need to manage NM tools
• Bell Operating company procedure
• NM tools can help in standardization of NM
process

3
Network Management: Principles and Practice
© Mani Subramanian 2011
 Chapter 4 SNMPv1 Network Management: Organization and Information Models

Managed LAN
NMS
192.168.252.110

192.168.252.1

Router 2

Backbone Network

Router 1
172.16.46.1
Hub 1 Hub 2
172.16.46.2 172.16.46.3

Figure 4.1 A Managed LAN Network

Notes
• NMS can automatically discover any component in the
network as long as this component has a management agent.

• NMS on subnet 192.168.252.1 manages the router and

the hubs on subnet 172.16.46.1 across the backbone
network

4
Network Management: Principles and Practice
© Mani Subramanian 2011
 Chapter 4 SNMPv1 Network Management: Organization and Information Models

Managed Hub:
System Information
Title: System Information: 172.16.46.2
Name or IP Address: 172.16.46.2

System Name:
System Description: 3Com LinkBuilder FMS, SW version:3.02
System Contact:
System Location:
System Object ID: iso.org.dod.internet.private.enterprises.43.1.8.5
System Up Time: (2475380437) 286 days, 12:03:24.37

Figure 4.2(a) System Information on 172.16.46.2 Hub

Notes
• Information obtained querying the hub
• Data truly reflects what is stored in the hub

• System Description and System Object ID are set

at the factory and can’t be modified → read-only.

• Time unit :1/100th of a second

5
Network Management: Principles and Practice
© Mani Subramanian 2011
 Chapter 4 SNMPv1 Network Management: Organization and Information Models

Managed Router:
System Information
Title: System Information: router1.gatech.edu
Name or IP Address: 172.16.252.1

System Name : router1.gatech.edu

System Description : Cisco Internetwork Operating System Software
: IOS (tm) 7000 Software (C7000-JS-M), Version
: 11.2(6),RELEASE SOFTWARE (ge1)
: Copyright (c) 1986-1997 by Cisco Systems, Inc.
: Compiled Tue 06-May-97 19:11 by kuong
System Contact
System Location :
System Object ID : iso.org.dod.internet.private.enterprises.cisco.ciscoProducts.
cisco 7000
System Up Time : (315131795) 36 days, 11:21:57.95

Figure 4.2(c) System Information on Router

Notes

6
Network Management: Principles and Practice
© Mani Subramanian 2011
 Chapter 4 SNMPv1 Network Management: Organization and Information Models

Managed Hub:
Port Addresses

Index Interface IP address Network Mask Network Link Address

Address

1 3Com 172.16.46.2 255.255.255.0 172.16 46.0 0x08004E07C25C

2 3Com 192.168.101.1 255.255.255.0 192.168.101.0 <none>

Notes
• Information acquired by the NMS on hub interfaces
• Index refers to the interface on the hub
• Link address is the MAC address
• The second row data is a serial link

7
Network Management: Principles and Practice
© Mani Subramanian 2011
 Chapter 4 SNMPv1 Network Management: Organization and Information Models

Managed Router:
Port Addresses
Index Interface IP address Network Mask Network Link Address
Address

23 LEC.1.0 192.168.3.1 255.255.255.0 192.168.3.0 0x00000C3920B4

25 LEC.3.9 192.168.252.15 255.255.255.0 192.168.252.0 0x00000C3920B4
13 Ethernet2/0 172.16..46.1 255.255.255.0 172.16..46.0 0x00000C3920AC
16 Ethernet2/3 172.16.49.1 255.255.255.0 172.16.49.0 0x00000C3920AF
17 Ethernet2/4 172.16.52.1 255.255.255.0 172.16.52.0 0x00000C3920B0
9 Ethernet1/2 172.16.55.1 255.255.255.0 172.16.55.0 0x00000C3920A6
2 Ethernet 0/1 172.16.56.1 255.255.255.0 172.16.56.0 0x00000C39209D
15 Ethernet2/2 172.16.57.1 255.255.255.0 172.16.57.0 0x00000C3920AE
8 Ethernet1/1 172.16.58.1 255.255.255.0 172.16.58.0 0x00000C3920A5
14 Ethernet2/1 172.16.60.1 255.255.255.0 172.16.60.0 0x00000C3920AD

Notes
• Information acquired by NMS on the router interfaces
• Index refers to the interface on the router
• LEC is the ATM LAN emulation card
•Ethernet 2/0 interface refers to the interface card 2
and port 0 in that card

8
Network Management: Principles and Practice
© Mani Subramanian 2011
 Chapter 4 SNMPv1 Network Management: Organization and Information Models

Internet SNMP Management

• 1970 - Internet control Message Protocol (ICMP)
• To manage ARPANET (Advanced Research
Project Agency Network)
• Transfers control messages between nodes
• Example: ping

• 1984: ARPANET → Internet

• Simple Gateway Monitoring Protocol (SGMP)
• To monitor and configure gateways remotely
• Interim solution

• Simple Network Management Protocol (SNMP)

• Enhancement of SGMP
• Recommended by IAB (Internet Advisory Board)
• Intended as an interim solution
• Plan to migrate to OSI (CMIP/CMIS)
• Became the de facto standard due to its simplicity

• Internet Engineering Task Force (IETF)

• 1990 SNMPv1
• 1995 SNMPv2 (independent of the OSI standard)
• 1998 SNMPv3 (addresses the security feature)

9
Network Management: Principles and Practice
© Mani Subramanian 2011
 Chapter 4 SNMPv1 Network Management: Organization and Information Models

Internet Organizations & Standards

• Internet documents (archived by the InterNIC (Internet
Network Information Center)):
• Request for Comments (RFC)
• IETF STD: Internet Standard RFC
• FYI: For Your Information RFC

• IANA (Internet Assigned Numbers Authority)

• Assigns and coordinates the use of Internet protocol
parameters: IP addresses, domain names, AS
numbers, MIB OIDs, etc.

• Source for RFCs

• ftp://nic.mil/rfc
• ftp://ftp.internic.net/rfc
• http://nic/internet.net/

10
Network Management: Principles and Practice
© Mani Subramanian 2011
 Chapter 4 SNMPv1 Network Management: Organization and Information Models

SNMPv1 & SNMPv2

Documents
SNMP
Management
Documents

RFC 1065 RFC 1066 RFC 1067

SMI MIB I RFC 1098
RFC 1155 RFC 1156 SNMPv1
STD 16 RFC 1157
SNMPv1 Concise SMI STD 15
Traps RFC 1212
RFC 1215 STD 16

RFC 1158
MIB II
RFC 1213
STD 17

RFC 1442 RFC 1443 RFC 1444 RFC 1448 RFC 1449
RFC 1905 RFC 1906
RFC 1902 RFC 1903 RFC 1904
SNMPv2 SNMPv2
SMIv2 Txt SMIv2 Protocol Ops Transport Map.
SMIv2
Conventions Conformances RFC 3416 RFC 3417
RFC 2578
RFC 2579 RFC 2580

RFC 1907
MIB II for
SNMPv2
RFC 3418

Figure 4.4 SNMP Document Evolution

11
Network Management: Principles and Practice
© Mani Subramanian 2011
 Chapter 4 SNMPv1 Network Management: Organization and Information Models

SNMP Model
• Organization Model
• Relationship between network element,
agent, and manager
• Hierarchical architecture
• Information Model
• Uses ASN.1 syntax
• SMI (Structure of Management Information)
• MIB ( Management Information Base)
• Communication Model
• Transfer syntax
• SNMP over TCP/IP (more specifically, UDP)
• Communication services addressed by messages
• Security framework community-based model

Notes

12
Network Management: Principles and Practice
© Mani Subramanian 2011
 Chapter 4 SNMPv1 Network Management: Organization and Information Models

Two-Tier Organization Model

SNMP SNMP SNMP

Manager Manager Manager

SNMPAgent Network Agent

Network Network
Element Element

(a) One Manager-One Agent Model (b) Multiple Managers-One Agent Model

Figure 4.5 Two-Tier Organization Model

Notes
• Any host that could query an agent is a manager.

13
Network Management: Principles and Practice
© Mani Subramanian 2011
 Chapter 4 SNMPv1 Network Management: Organization and Information Models

Three-Tier Organization Model:

RMON

SNMP
Manager

RMON
Probe

Managed
Objects

Figure 4.6 Three-Tier Organization Model

Notes
• Managed object comprises network element and
management agent
•RMON (Remote Monitoring) acts as an agent and a
manager
•RMON gathers data from MO, analyses the data, and
stores the data
•Communicates the statistics to the manager (solicited
or unsolicited)

14
Network Management: Principles and Practice
© Mani Subramanian 2011
Chapter 4 SNMPv1 Network Management: Organization and Information Models

Three-Tier Organization Model:

Proxy Server
SNMP
Manager

Proxy
Server

Non-SNMP SNMP
Managed Managed
Objects Objects

Figure 4.7 Proxy Server Organization Model

Notes
• Proxy server converts non-SNMP data from
non-SNMP objects to SNMP compatible objects
and messages

15
Network Management: Principles and Practice
© Mani Subramanian 2011
 Chapter 4 SNMPv1 Network Management: Organization and Information Models

Two-Tier Organization Model

SNMP SNMP SNMP SNMP

Manager Agent Agent Manager

SNMPAgent SNMPAgent

Network Network
Element Element

An NMS behaving as Manager and Agent

Notes
Exchange of management information, for example,
between two service providers managing their
respective networks.

16
Network Management: Principles and Practice
© Mani Subramanian 2011
 Chapter 4 SNMPv1 Network Management: Organization and Information Models

System Architecture
SNMP Manager SNMP Agent

Manage- SNMP Manager SNMP Agent

ment Application Application
Data

Trap

Set-Request
Get-Request

Set-Request

Get-Request
GetNext-Request

GetNext-Request

Trap
Get-Response

Get-Response
SNMP SNMP

UDP UDP

IP IP

DLC DLC

PHY PHY

Physical Mediu m

Figure 4.9 SNMP Network Management Architecture

Notes
• Messages between manager and agent
• Direction of messages - 3 from manager and
2 from agent
17
Network Management: Principles and Practice
© Mani Subramanian 2011
 Chapter 4 SNMPv1 Network Management: Organization and Information Models

SNMP Messages
• Get-Request
• Sent by manager requesting data from agent
(e.g., sysDescr)
• Get-Next-Request
• Sent by manager requesting data on the next
MO to the one specified (e.g., table with
multiple instances of the same object)
• Set-Request
• Initializes or changes the value of network
element
• Get-Response
• Agent responds with data for get and set
requests from the manager
• Includes values, and error info if any.
• Trap
• Alarm generated by an agent (unsolicited)

Notes
• Manager monitors network by polling agents about
status and characteristics

• Generation of unsolicited alarm messages increased

efficiency
18
Network Management: Principles and Practice
© Mani Subramanian 2011
 Chapter 4 SNMPv1 Network Management: Organization and Information Models

Information Model
• Structure of Management Information (SMI)
(RFC 1155)
• Specification and organizational aspects of MOs

• Managed Object
• Scalar
• Aggregate or tabular object

• Management Information Base (RFC 1213)

• Definition of MOs
• Grouping of MOs
• Relationship between MOs

Notes
• RFCs can be downloaded from ftp.internic.net/rfc
• Some address standard network objects
• Others address specialized network objects,
e.g., OSPF (RFC 1253), ATM (RFC 1695), etc.

• Private vendor objects are specified in the private MIBs

• Provided by vendors for their products

19
Network Management: Principles and Practice
© Mani Subramanian 2011
 Chapter 4 SNMPv1 Network Management: Organization and Information Models

Managed Object

Object

Object Object
Type Instance

Name:
Syntax: Encoding:
OBJECT
ASN.1 BER
IDENTIFIER

Figure 4.10 Managed Object : Type and Instance

Notes
• SMI is concerned only with object type and not object
instance
• Object type and data type are synonymous
• Object identifier is data type, not instance
• Object instance: IP address
• Two identical hubs have the same object type with
the same OID, but each one represents a different
object instance with a different IP address. (See Figure 4.2)
20
Network Management: Principles and Practice
© Mani Subramanian 2011
 Chapter 4 SNMPv1 Network Management: Organization and Information Models

Managed Object: Multiple Instances

Object

Object Object
Type Instance 3
Object
Instance 2
Name:
Syntax: Encoding: Object
OBJECT
ASN.1 BER Instance 1
IDENTIFIER

Figure 4.11 Managed Object : Type with Multiple Instances

Notes
• All 3 Com hubs of the same version have identical
identifier; they are distinguished by the IP address.

• Each IP address is an instance of the object.

21
Network Management: Principles and Practice
© Mani Subramanian 2011
 Chapter 4 SNMPv1 Network Management: Organization and Information Models

Name
Uniquely defined by:
• DESCRIPTOR, and
• OBJECT IDENTIFIER

internet OBJECT IDENTIFIER ::= {iso org(3) dod(6) 1 }

internet OBJECT IDENTIFIER ::= {iso(1) standard(3) dod(6) internet(1)}

internet OBJECT IDENTIFIER ::= {1 3 6 1}
internet OBJECT IDENTIFIER ::= {iso standard dod internet }
internet OBJECT IDENTIFIER ::= { iso standard dod(6) internet(1) }
internet OBJECT IDENTIFIER ::= { iso(1) standard(3) 6 1 }

Notes
• Example: ipAddrTable ip 20
• DESCRIPTOR → ipAddrTable
• OBJECT IDENTIFIER → ip 20

• DESCRIPTOR is a mnemonic name that:

• Has to be unique
• Begins with a lowercase letter

22
Network Management: Principles and Practice
© Mani Subramanian 2011
 Chapter 4 SNMPv1 Network Management: Organization and Information Models

Internet Subnodes

Internet
{1 3 6 1}

directory mgmt experimental private

(1) (2) (3) (4)

Figure 4.13 Subnodes under Internet Node in SNMPv1

Notes

• directory OBJECT IDENTIFIER ::= {internet 1}

mgmt OBJECT IDENTIFIER ::= {internet 2}
experimental OBJECT IDENTIFIER ::= {internet 3}
private OBJECT IDENTIFIER ::= {internet 4}

• mib-2 OBJECT IDENTIFIER ::= {mgmt 1}

23
Network Management: Principles and Practice
© Mani Subramanian 2011
 Chapter 4 SNMPv1 Network Management: Organization and Information Models

Private MIB Example

internet
{1 3 6 1}

private
(4)

enterprises
(1)

cisco hp 3Com Cabletron

(9) (11) (43) (52)

Figure 4.14 Private Subtree for Commercial Vendors

Notes
• private MIB intended for vendor equipment
• The objects to be included are left to the discretion
of the vendors

• IANA (Internet Assigned Numbers Authority) assigns

identifiers

24
Network Management: Principles and Practice
© Mani Subramanian 2011
 Chapter 4 SNMPv1 Network Management: Organization and Information Models

SNMP ASN.1 Data Type

SNMP ASN.1
Data Type

Tag

Structure

Number

Class

Simple Defined Constructor

or or or
Primitive Application Structured

Context-
Universal Application Private
specific

Figure 4.15 SNMP ASN.1 Data Type

Notes
• Not all ASN.1 constructs are used in SNMP

• Tagged type not explicitly used

• However, IMPLICIT and EXTERNAL keywords
are used for derived application data types.

• CHOICE is used as well

25
Network Management: Principles and Practice
© Mani Subramanian 2011
 Chapter 4 SNMPv1 Network Management: Organization and Information Models

Primitive Data Types

Structure Data Type Comments
Primitive types INTEGER Subtype INTEGER (n1..nN)
Special case: Enumerated
INTEGER type
OCTET STRING 8-bit bytes binary and textual data
Subtypes can be specified by
either range or fixed
OBJECT IDENTIFIER Object position in MIB
NULL Placeholder

Notes
• get-request message has NULL for value fields
and get-response from agent has the values filled

in subtype:
• INTEGER (0..255)
• OCTET STRING (SIZE 0..255)
• OCTET STRING (SIZE 8)

26
Network Management: Principles and Practice
© Mani Subramanian 2011
 Chapter 4 SNMPv1 Network Management: Organization and Information Models

Enumerated
• Special case of INTEGER data type

error-status INTEGER {
noError(0)
tooBig(1)
genErr(5)
authorizationError(16)
}

Notes
• noError NULL by convention

27
Network Management: Principles and Practice
© Mani Subramanian 2011
 Chapter 4 SNMPv1 Network Management: Organization and Information Models

Defined or Application Data Type

Defined Types NetworkAddress Not used
IpAddress Dotted decimal IP address
Counter Wrap-around, non-negative
integer, monotonically increasing,
max 2^32 -1
Gauge Capped, non-negative integer,
increase or decrease
TimeTicks Non-negative integer in
hundredths of second units
Opaque Application-wide arbitrary ASN.1
syntax, double wrapped OCTET
STRING

Notes

• Defined data types are simple or base types

• Opaque is used to create data types based on

previously defined data types
• TLV for the new definition is wrapped around the
TLV of the previously defined type
• Supports the capability to pass arbitrary ASN.1
syntax

28
Network Management: Principles and Practice
© Mani Subramanian 2011
 Chapter 4 SNMPv1 Network Management: Organization and Information Models

Constructor or Structured Data Type:

SEQUENCE
• List maker

SEQUENCE { <type1>, <type2>,…, <typeN> }

Object OBJECT IDENTIFIER ObjectSyntax

1 ipAdEntAddr {ipAddrEntry 1} IpAddress
2 ipAdEntIfIndex {ipAddrEntry 2} INTEGER
3 ipAdEntNetMask {ipAddrEntry 3} IpAddress
4 ipAdEntBcastAddr {ipAddrEntry 4} INTEGER
5 ipAdEntReasmMaxSize {ipAddrEntry 5} INTEGER
6 ipAddrEntry {ipAddrTable 1} SEQUENCE

List: IpAddrEntry ::=

SEQUENCE {
ipAdEntAddr IpAddress
ipAdEntIfIndex INTEGER
ipAdEntNetMask IpAddress
ipAdEntBcastAddr INTEGER
ipAdEntReasmMaxSize INTEGER (0..65535)
}
Managed Object IpAddrEntry as a list

Notes
• SEQUENCE is used to build a list
• SEQUENCE OF is used to build a table
• SET and SET OF are not included in SNMP-based
management syntax

29
Network Management: Principles and Practice
© Mani Subramanian 2011
 Chapter 4 SNMPv1 Network Management: Organization and Information Models

Constructor or Structured Data Type:

SEQUENCE OF

SEQUENCE OF <entry>
where <entry> is a list constructor

Object Name OBJECT IDENTIFIER Syntax

7 ipAddrTable {ip 20} SEQUENCE OF

Table:
IpAddrTable ::= SEQUENCE OF IpAddrEntry

Managed Object ipAddrTable as a table

Notes

30
Network Management: Principles and Practice
© Mani Subramanian 2011
 Chapter 4 SNMPv1 Network Management: Organization and Information Models

“SEQUENCE OF” Example

Title: System Information : router1.gatech.edu
Name or IP Address: 172.16252.1

Index Interface IP address Network Mask Network Link Address

Address

23 LEC.1.0 192.168.3.1 255.255.255.0 192.168.3.0 0x00000C3920B4

25 LEC.3.9 192.168.252.1 255.255.255.0 192.168.252. 0x00000C3920B4
5 0
13 Ethernet2/0 172.16..46.1 255.255.255.0 172.16..46.0 0x00000C3920AC
16 Ethernet2/3 172.16.49.1 255.255.255.0 172.16.49.0 0x00000C3920AF
17 Ethernet2/4 172.16.52.1 255.255.255.0 172.16.52.0 0x00000C3920B0
9 Ethernet1/2 172.16.55.1 255.255.255.0 172.16.55.0 0x00000C3920A6
2 Ethernet 0/1 172.16.56.1 255.255.255.0 172.16.56.0 0x00000C39209D
15 Ethernet2/2 172.16.57.1 255.255.255.0 172.16.57.0 0x00000C3920AE
8 Ethernet1/1 172.16.58.1 255.255.255.0 172.16.58.0 0x00000C3920A5
14 Ethernet2/1 172.16.60.1 255.255.255.0 172.16.60.0 0x00000C3920AD

Notes
• The above example (Figure 4.3) uses part of the
IP MIB discussed for SEQUENCE OF construct.

31
Network Management: Principles and Practice
© Mani Subramanian 2011
 Chapter 4 SNMPv1 Network Management: Organization and Information Models

Encoding
• Basic Encoding Rules (BER)
• Tag, Length, and Value (TLV)
Type Length Value

Class P/C Tag Number

(7-8th bits) (6th bit) (1-5th bits)

• SNMP Data Types and Tags

Type Tag
OBJECT IDENTIFIER UNIVERSAL 6
SEQUENCE UNIVERSAL 16
IpAddress APPLICATION 0
Counter APPLICATION 1
Gauge APPLICATION 2
TimeTicks APPLICATION 3
Opaque APPLICATION 4
Notes
• SEQUENCE Encoding:
• P/C = 1
• Value: contains the concatenation of the complete
BER encoding (TLV) of the components of the value
32
Network Management: Principles and Practice
© Mani Subramanian 2011
Chapter 4 SNMPv1 Network Management: Organization and Information Models

OBJECT IDENTIFIER and IP

Encoding
• Each subidentifier is encoded as an octet
• All subidentifiers are concatenated to form the
object identifier
• If subidentifier > 127 → first octet represents the
number of subsequent octets representing the
subidentifier. In this case, the 8th bit of the first
octet is set to 1.
• Exception to this rule is for iso(1) and standard
(3) → both are coded as one subidentifier = 43
• Example: internet {1 3 6 1}
00000110 00000011 00101011 00000110 00000001
Type Length 43 6 1

• IP Address is encoded as straight octet strings

• Example: 10.11.10.11 →

01000000 00000100 00001010 00001011 00001010 00001011

Type Length 10 11 10 11
33
Network Management: Principles and Practice
© Mani Subramanian 2011
 Chapter 4 SNMPv1 Network Management: Organization and Information Models

Managed Object: Structure

OBJECT:
sysDescr: { system 1 }
Syntax: OCTET STRING
Definition: "A textual description of the entity. This value
should include the full name and version
identification of the system's hardware type,
software operating-system, and networking
software. It is mandatory that this only contain
printable ASCII characters."
Access: read-only
Status: mandatory
Figure 4.17 Specifications for System Description

Notes

34
Network Management: Principles and Practice
© Mani Subramanian 2011
Chapter 4 SNMPv1 Network Management: Organization and Information Models

Managed Object: Macro

OBJECT-TYPE MACRO ::=
BEGIN
TYPE NOTATION ::= “SYNTAX” type(TYPE ObjectSyntax)
“ACCESS” Access
“STATUS” Status
VALUE NOTATION ::= value(VALUE ObjectName)

Access ::= “read-only” | “read-write” | “write-only” | “not-accessible”

Status ::= “mandatory” | “optional” | “obsolete”

END

Figure 4.18(a) OBJECT-TYPE Macro [RFC 1155]

sysDescr OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..255))
ACCESS read-only
STATUS mandatory
DESCRIPTION
“A textual description of the entity. This value should
include the full name and version identification of the
system’s hardware type, software operating-system, and
networking software. It is mandatory that this only
contain printable ASCII characters.”
::= {system 1 }

Figure 4.18(b) Scalar or Single Instance Macro: sysDescr

[RFC 1213]

35
Network Management: Principles and Practice
© Mani Subramanian 2011
Chapter 4 SNMPv1 Network Management: Organization and Information Models

Aggregate Managed Object

• A group of objects
• Also called tabular objects
• Can be represented by a table with
• Columns of objects
• Rows of instances
Table of Objects

List of Objects

Objects

Notes
• Example: IP address table
• Consists of objects:
• IP address
• Interface
• Subnet mask (which subnet this address
belongs to)
• Broadcast address (value of l.s.b. in IP
broadcast address)
• Largest IP datagram that can be assembled
• Multiple instances of these objects associated
with the node
36
Network Management: Principles and Practice
© Mani Subramanian 2011
Chapter 4 SNMPv1 Network Management: Organization and Information Models

Aggregate M.O. Macro:

Table Object
ipAddrTable OBJECT-TYPE
SYNTAX SEQUENCE OF IpAddrEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"The table of addressing
information relevant to this entity's IP
addresses."
::= {ip 20}

ipAddrTable OBJECT-TYPE
::= {ip 20}
ipAddrEntry OBJECT-TYPE
::= {ipAddrTable 1}

37
Network Management: Principles and Practice
© Mani Subramanian 2011
Chapter 4 SNMPv1 Network Management: Organization and Information Models

Aggregate M.O. Macro:

Entry Object
ipAddrEntry OBJECT-TYPE
SYNTAX IpAddrEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"The addressing information for one of this
entity's IP addresses."

INDEX { ipAdEntAddr }
::= { ipAddrTable 1 }

IpAddrEntry ::=
SEQUENCE {
ipAdEntAddr
IpAddress,
ipAdEntIfIndex
INTEGER,
ipAdEntNetMask
IpAddress,
ipAdEntBcastAddr
INTEGER,
ipAdEntReasmMaxSize
INTEGER (0..65535) }

Notes
• Index ipAdEntAddr uniquely identifies an instance
• May require more than one object in the instance to
uniquely identify it
38
Network Management: Principles and Practice
© Mani Subramanian 2011
Chapter 4 SNMPv1 Network Management: Organization and Information Models

Aggregate M.O. Macro:

Columnar Objects
ipAdEntAddr OBJECT-TYPE
SYNTAX IpAddress
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The IP address to which this entry's
addressing information pertains."

::= { ipAddrEntry 1 }

ipAdEntReasmMaxSize OBJECT-TYPE
SYNTAX INTEGER (0..65535)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The size of the largest IP datagram which this
entity can re-assemble from incoming IP
fragmented datagrams received on this interface."
::= { ipAddrEntry 5 }

Notes

39
Network Management: Principles and Practice
© Mani Subramanian 2011
 Chapter 4 SNMPv1 Network Management: Organization and Information Models

Tabular Representation of
Aggregate Object
TABLE
T

ENTRY
E

COLUMNAR COLUMNAR COLUMNAR COLUMNAR COLUMNAR

OBJECT 1 OBJECT 2 OBJECT 3 OBJECT 4 OBJECT 5

Figure 4.22(a) Multiple Instance Managed Object

Notes
• The objects TABLE T and ENTRY E are objects that
are logical objects. They define the grouping and are
not accessible
• Columnar objects are objects that represent the
attributes and hence are accessible
• Each instance of E is a row of columnar objects
1 through 5
• Multiple instances of E are represented by multiple rows

40
Network Management: Principles and Practice
© Mani Subramanian 2011
Chapter 4 SNMPv1 Network Management: Organization and Information Models

Tabular Representation of
Aggregate Object (cont.)
T

T.E

T.E.1.1 T.E.2.1 T.E.3.1 T.E.4.1 T.E.5.1

T.E.1.2 T.E.2.2 T.E.3.2 T.E.4.2 T.E.5.2

T.E.1.3 T.E.2.3 T.E.3.3 T.E.4.3 T.E.5.3

T.E.1.4 T.E.2.4 T.E.3.4 T.E.4.4 T.E.5.4

Figure 4.22(b) Example of 5 Columnar Object with 4 Instances (rows)

Notes
• Notice that the column-row numeric designation
is reverse of what we are used to as row-column

41
Network Management: Principles and Practice
© Mani Subramanian 2011
Chapter 4 SNMPv1 Network Management: Organization and Information Models

Multiple Instances of
Aggregate Managed Object
ipAddrTable {1.3.6.1.2.1.4.20}
ipAddrEntry (1)
ipAdEntAddr (1)
ipAdEntIfIndex (2)
ipAdEntNetMask (3)
ipAdEntBcastAddr (4)
ipAdEntReasmMaxSize (5)

Columnar object ID of ipAdEntBcastAddr is (1.3.6.1.2.1.4.20.1.4):

iso org dod internet mgmt mib ip ipAddrTable ipAddrEntry ipAdEntBcastAddr

1 3 6 1 2 1 4 20 1 4
Figure 4.23(a) Columnar objects under ipAddrEntry

Row ipAdEntAddr ipAdEntIfIndex IpAdEntNetMask IpAdEntBcastAddr IpAdEntReasmMaxSize

1 123.45.2.1 1 255.255.255.0 0 12000

2 123.45.3.4 3 255.255.0.0 1 12000
3 165.8.9.25 2 255.255.255.0 0 10000
4 9.96.8.138 4 255.255.255.0 0 15000

Figure 4.23(b) Object instances of ipAddrTable (1.3.6.1.2.1.4.20)

Columnar Object Row # in (b) Object Identifier

ipAdEntAddr 2 {1.3.6.1.2.1.4.20.1.1.123.45.3.4}
1.3.6.1.2.1.4.20.1.1
ipAdEntIfIndex 3 {1.3.6.1.2.1.4.20.1.2.165.8.9.25}
1.3.6.1.2.1.4.20.1.2
ipAdEntBcastAddr 1 {1.3.6.1.2.1.4.20.1.4.123.45.2.1}
1.3.6.1.2.1.4.20.1.4
IpAdEntReasmMaxSize 4 {1.3.6.1.2.1.4.20.1.5.9.96.8.138}
1.3.6.1.2.1.4.20.1.5

Figure 4.23(c) Object Id for specific instance

42
Network Management: Principles and Practice
© Mani Subramanian 2011
Chapter 4 SNMPv1 Network Management: Organization and Information Models

SMI Definition STD 16 / 1155 RFC

RFC1155-SMI DEFINITIONS ::= BEGIN

EXPORTS -- EVERYTHING
internet, directory, mgmt, experimental, private, enterprises,
OBJECT-TYPE, ObjectName, ObjectSyntax, SimpleSyntax,
ApplicationSyntax, NetworkAddress, IpAddress, Counter, Gauge,
TimeTicks, Opaque;

-- the path to the root

internet OBJECT IDENTIFIER ::= { iso org(3) dod(6) 1 }

directory OBJECT IDENTIFIER ::= { internet 1 }

mgmt OBJECT IDENTIFIER ::= { internet 2 }
experimental OBJECT IDENTIFIER ::= { internet 3 }
private OBJECT IDENTIFIER ::= { internet 4 }

enterprises OBJECT IDENTIFIER ::= { private 1 }

Notes
• EXPORTS identifies the objects that any other
module could import.

43
Network Management: Principles and Practice
© Mani Subramanian 2011
 Chapter 4 SNMPv1 Network Management: Organization and Information Models

SMI Definition STD 16 / 1155 RFC (cont.)

-- definition of object types

OBJECT-TYPE MACRO ::=

BEGIN
TYPE NOTATION ::= "SYNTAX" type (TYPE ObjectSyntax)
"ACCESS" Access
"STATUS" Status
VALUE NOTATION ::= value (VALUE ObjectName)

Access ::= "read-only" | "read-write" | "write-only" | "not-accessible"

Status ::= "mandatory" | "optional" | "obsolete"
END

Notes

44
Network Management: Principles and Practice
© Mani Subramanian 2011
Chapter 4 SNMPv1 Network Management: Organization and Information Models

SMI Definition STD 16 / 1155 RFC (cont.)

-- names of objects in the MIB

ObjectName ::=
OBJECT IDENTIFIER

-- syntax of objects in the MIB

ObjectSyntax ::=
CHOICE {
simple
SimpleSyntax,

application-wide
ApplicationSyntax
}

Notes

45
Network Management: Principles and Practice
© Mani Subramanian 2011
Chapter 4 SNMPv1 Network Management: Organization and Information Models

SMI Definition STD 16 / 1155 RFC (cont.)

SimpleSyntax ::=
CHOICE {
number
INTEGER,
string
OCTET STRING,
object
OBJECT IDENTIFIER,
empty
NULL
}

ApplicationSyntax ::=
CHOICE {
address
NetworkAddress,
counter
Counter,
gauge
Gauge,
ticks
TimeTicks,
arbitrary
Opaque

-- other application-wide types, as they are defined,

will be added here
}

46
Network Management: Principles and Practice
© Mani Subramanian 2011
Chapter 4 SNMPv1 Network Management: Organization and Information Models

SMI Definition STD 16 / 1155 RFC (cont.)

-- application-wide types

NetworkAddress ::=
CHOICE {
internet
IpAddress
}
IpAddress ::=
[APPLICATION 0] -- in network-byte order
IMPLICIT OCTET STRING (SIZE (4))
Counter ::=
[APPLICATION 1]
IMPLICIT INTEGER (0..4294967295)
Gauge ::=
[APPLICATION 2]
IMPLICIT INTEGER (0..4294967295)
TimeTicks ::=
[APPLICATION 3]
IMPLICIT INTEGER (0..4294967295)
Opaque ::=
[APPLICATION 4] -- arbitrary ASN.1 value,
IMPLICIT OCTET STRING -- "double-wrapped"

END

Notes

47
Network Management: Principles and Practice
© Mani Subramanian 2011
 Chapter 4 SNMPv1 Network Management: Organization and Information Models

Criteria for including an object in MIB-II

[RFC 1213/ STD 17]
(1) An object needed to be essential for either fault
or configuration management

(2) Only weak control objects were permitted (by weak,

it is meant that tampering with them can do only limited
damage). This criterion reflects the fact that the current
management protocols are not sufficiently secure to do
more powerful control operations.

(3) Evidence of current use and utility was required.

(4) In MIB-I, an attempt was made to limit the number

of objects to about 100 to make it easier for vendors to
fully instrument their software. In MIB-II, this limit was
raised given the wide technological base now
implementing MIB-I.

(5) To avoid redundant variables, it was required that

no object be included that can be derived from others
in the MIB.

(6) Implementation specific objects (e.g., for BSD UNIX)

were excluded.

(7) It was agreed to avoid heavily instrumenting critical

sections of code. The general guideline was one counter
per critical section per layer.
48
Network Management: Principles and Practice
© Mani Subramanian 2011
Chapter 4 SNMPv1 Network Management: Organization and Information Models

MIB
internet
{1 3 6 1}

directory mgmt experimental private

(1) (2) (3) (4)

mib-2
(1)

system (1) snmp (11)

interfaces (2) transmission (10)
at (3) cmot (9)
ip (4) egp (8)
icmp (5) udp (7)
tcp (6)

Figure 4.26 Internet MIB-II Group

Notes
• MIB-II (RFC 1213) is superset of MIB-I.
• Objects that are related grouped into object groups.
• MIB module comprises module name, imports from
other modules, and definitions of current module.
• RFC 1213 defines eleven groups; expanded later.

49
Network Management: Principles and Practice
© Mani Subramanian 2011
Chapter 4 SNMPv1 Network Management: Organization and Information Models

System Group
system
(mib-2 1)

sysDescr (1) sysServices (7)

sysObjectId
sysLocation (6)
(2)
sysUpTime (3) sysName (5)

sysContact (4)

Figure 4.27 System Group

Notes
Entity OID Description (brief)
sysDescr system 1 Textual description
sysObjectID system 2 OBJECT IDENTIFIER of the entity
sysUpTime system 3 Time (in hundredths of a second since last reset)
sysContact system 4 Contact person for the node
sysName system 5 Administrative name of the system
sysLocation system 6 Physical location of the node
sysServices system 7 Value designating the layer services provided by the
entity

50
Network Management: Principles and Practice
© Mani Subramanian 2011
 Chapter 4 SNMPv1 Network Management: Organization and Information Models

sysServices
sysServices OBJECT-TYPE
SYNTAX INTEGER (0..127)
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A value which indicates the set of services that
this entity primarily offers.

The value is a sum. This sum initially takes the

value zero, Then, for each layer, L, in the range
1 through 7, that this node performs transactions
for, 2 raised to (L - 1) is added to the sum. For
example, a node which performs primarily routing
functions would have a value of 4 (2^(3-1)). In
contrast, a node which is a host offering
application services would have a value of 72
(2^(4-1) + 2^(7-1)). Note that in the context of
the Internet suite of protocols, values should be
calculated accordingly:

layer functionality
1 physical (e.g., repeaters)
2 datalink/subnetwork (e.g., bridges)
3 internet (e.g., IP gateways)
4 end-to-end (e.g., IP hosts)
7 applications (e.g., mail relays)

For systems including OSI protocols, layers 5 and

6 may also be counted."
::= { system 7 }

Notes

51
Network Management: Principles and Practice
© Mani Subramanian 2011
 Chapter 4 SNMPv1 Network Management: Organization and Information Models

Interfaces Group
interfaces
(mib-2 2)

ifNumber ifTable
(1) (2)

ifEntry
(1)

ifIndex (1) ifSpecific (22)

ifDescr (2) ifOutQLen (21)
ifType (3) ifOutErrors (20)
ifMtu (4) ifOutDiscards (19)
ifSpeed (5) ifOutNUcastPkts (18)
ifPhysAddress (6) ifOutUcastPkts (17)
ifAdminstatus (7) ifOutOctets (16)
ifOperStatus (8) ifUnknownProtos (15)
ifLastChange (9) ifInErrors (14)
ifInOctets (10) ifInDiscards (13)
ifInUcastPkts (11) ifInNUcastPkts (12)

Legend: INDEX in bold

Figure 4.28 Interfaces Group

Notes
• Info about specific interfaces addressed in specific MIBs
• Example: dot3 OBJECT IDENTIFER ::= { transmission 7 }
[RFC 2358, Definitions of Managed Objects for
the Ethernet-like Interface Types]
52
Network Management: Principles and Practice
© Mani Subramanian 2011
Chapter 4 SNMPv1 Network Management: Organization and Information Models

ifEntry
IfEntry OBJECT-TYPE
SYNTAX IfEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"An interface entry containing
objects at the subnetwork layer and
below for a particular interface."
INDEX {ifIndex}
::= {ifTable 1}

Notes
• ifEntry specifies the objects in a row in the ifTable.
• Each interface is defined as a row in the table.

53
Network Management: Principles and Practice
© Mani Subramanian 2011
Chapter 4 SNMPv1 Network Management: Organization and Information Models

ifType
ifType OBJECT-TYPE
SYNTAX INTEGER {
other(1), -- none of the following
regular1822(2),
hdh1822(3),
ddn-x25(4),
rfc877-x25(5),
ethernet-csmacd(6),
iso88023-csmacd(7),
iso88024-tokenBus(8),
iso88025-tokenRing(9),
iso88026-man(10),
starLan(11),
proteon-10Mbit(12),
proteon-80Mbit(13),
hyperchannel(14),
fddi(15),
lapb(16),
sdlc(17),
ds1(18), -- T-1
e1(19), -- european equiv. of T-1
basicISDN(20),
primaryISDN(21), -- proprietary serial
propPointToPointSerial(22),
ppp(23),
……….
Notes
• Type of interface below the network layer defined

as enumerated integer.
54
Network Management: Principles and Practice
© Mani Subramanian 2011
 Chapter 4 SNMPv1 Network Management: Organization and Information Models

IP Group
ip
(mib-2 4)

ipForwarding (1) ipRoutingDiscards (23)

ipDefaultTTL (2) ipNetToMediaTable (22)
ipInReceives (3) ipRouteTable (21)
ipInHdrErrors (4) ipAddrTable (20)
ipInAddrErrors (5) ipFragCreates (19)
ipForwDatagrams (6) ipFragFails (18)
ipInUnknownProtos (7) ipFragOKs (17)
ipInDiscards (8) ipReasmFails (16)
ipInDelivers (9) ipReasmOKs (15)
ipOutRequests(10) ip ReasmReqds (14)
ipOutDiscards (11) ipReasmTimeout (13)

ipOutNoRoutes (12)

Figure 4.29 IP Group

Notes
• ipForwarding: Forwarding Router/Gateway (1) and
non-forwarding/host (2)
• IP Address Table contains table of IP addresses
• IP Route Table contains an entry for each route
• IP Network-to-Media Table is address translation table
mapping IP addresses to physical addresses
55
Network Management: Principles and Practice
© Mani Subramanian 2011
Chapter 4 SNMPv1 Network Management: Organization and Information Models

IP Address Table
ipAddrTable
(ip 20)

ipAddrEntry
(ipAddrTable 1)

ipAdEntReasmMaxSize (5)
ipAdEntAddr (1)
ipAdEntBcastAddr (4)
ipAdEntIfIndex (2)
ipAdEntNetMask
(3)

Legend: INDEX in bold

Figure 4.30 IP Address Table

Notes
Entity OID Description (brief)
ipAddrTable ip 20 Table of IP addresses
ipAddrEntry IpAddrTable 1 One of the entries in the IP address
table
ipAdEntAddr IpAddrEntry 1 The IP address to which this entry's
addressing information pertains
ipAdEntIfIndex IpAddrEntry 2 Index value of the entry, same as
ifIndex
ipAdEntNetMask IpAddrEntry 3 Subnet mask for the IP address of
the entry
ipAdEntBcastAddr IpAddrEntry 4 Broadcast address indicator bit
ipAdEntReasmMaxSize IpAddrEntry 5 Largest IP datagram that can be
reassembled on this interface

56
Network Management: Principles and Practice
© Mani Subramanian 2011
Chapter 4 SNMPv1 Network Management: Organization and Information Models

IP Routing Table
ipRouteTable
(ip 21)

ipRouteEntry
ipRouteTable (1)

ipRouteDest (1) ipRouteInfo (13)

ipRouteMetric5
ipRouteIfIndex (2)
(12)
ipRouteMetric1 (3) ipRouteMask 11)
ipRouteMetric2 (4) ipRouteAge (10)
ipRouteMetric3 (5) ipRouteProto (9)
ipRouteMetric4 (6) ipRouteType (8)
ipRouteNextHop (7)

Figure 4.31 IP Routing Table

Entity OID Description (brief)

ipRouteTable ip 21 IP routing table
ipRouteEntry ipRouteTable 1 Route to a particular destination
ipRouteDest ipRouteEntry 1 Destination IP address of this route
ipRouteIfIndex ipRouteEntry 2 Index of interface, same as ifIndex
ipRouteMetric1 ipRouteEntry 3 Primary routing metric for this route
ipRouteMetric2 ipRouteEntry 4 An alternative routing metric for this route
ipRouteMetric3 ipRouteEntry 5 An alternative routing metric for this route
ipRouteMetric4 ipRouteEntry 6 An alternative routing metric for this route
ipRouteNextHop ipRouteEntry 7 IP address of the next hop
ipRouteType ipRouteEntry 8 Type of route
ipRouteProto ipRouteEntry 9 Routing mechanism by which this route was
learned
ipRouteAge ipRouteEntry 10 Number of seconds since routing was last updated
ipRouteMask ipRouteEntry 11 Mask to be logically ANDed with the destination
address before comparing with the ipRouteDest
field
ipRouteMetric5 ipRouteEntry 12 An alternative metric for this route
ipRouteInfo ipRouteEntry 13 Reference to MIB definition specific to the routing
protocol

57
Network Management: Principles and Practice
© Mani Subramanian 2011
 Chapter 4 SNMPv1 Network Management: Organization and Information Models

IP Address Translation Table

ipNetToMediaTable
(ip 22)

ipNetToMediaEntry (1)

ipNetToMediaIfIndex (1) ipNetToMediaType (4)

ipNetToMediaPhysAddress (2) ipNetToMediaNetAddress (3)

Figure 4.32 IP Address Translation Table

Notes
Entity OID Description (brief)
ipNetToMediaTable ip 22 Table mapping IP addresses to
physical addresses
ipNetToMediaEntry IpNetToMediaTable 1 IP address to physical address
for the particular interface
ipNetToMediaIfIndex IpNetToMediaEntry 1 Interfaces on which this entry's
equivalence is effective; same
as ifIndex
ipNetToMediaPhysAddress IpNetToMediaEntry 2 Media dependent physical
address
ipNetToMediaNetAddress IpNetToMediaEntry 3 IP address
ipNetToMediaType IpNetToMediaEntry 4 Type of mapping

58
Network Management: Principles and Practice
© Mani Subramanian 2011
 Chapter 4 SNMPv1 Network Management: Organization and Information Models

ICMP Group
icmp
(mib -2 5)

icmpInMsgs (1) icmpOutAddrMaskReps (26)

icmpInErrors (2) icmpOutAddrMasks (25)
icmpInDestUnreachs (3) icmpOutTimestampReps (24)
icmpInTimeExcds (4) icmpOutTimestamps (23)
icmpInParmProbe (5) icmpOutEchoReps (22)
icmpInSrcQuenchs (6) icmpOutEchos (21)
icmpInRedirects (7) icmpOutRedirects (20)
icmpInEchos (8) icmpOutSrcQuenchs (19)
icmpInEchoReps (9) icmpOutParmProbe (18)
icmpInTimestamps (10) icmpOutTimeExcds (17)
icmpInTimestampReps (11) icmpOutDestUnreachs (16)
icmpInAddrMasks (12) icmpOutErrors (15)
icmpInAddrMaskReps (13) icmpInMsgs (14)

Figure 4.34 ICMP Group

Notes
• Objects associated with ping
• icmpOutEchos # ICMP echo messages sent
• icmpInEchoReps # ICMP echo reply messages
received
• Objects associated with traceroute/tracert
• icmpInTimeExcs # ICMP time exceeded
messages received

59
Network Management: Principles and Practice
© Mani Subramanian 2011
 Chapter 4 SNMPv1 Network Management: Organization and Information Models

TCP Group
tcp
(mib-2 6)

tcpOutRsts (15)
tcpRtoAlgorithm (1)
tcpInErrors (14)
tcpRtoMin (2)
tcpConnTable 13)
tcpRtoMax (3)
tcpRetranSegs (12)
tcpMaxConn (4)
tcpActiveOpens (5) tcpOutSegs (11)
tcpPassiveOpens (6) tcpInSegs (10)
tcpAttemptFails (7) tcpCurrEstab (9)
tcpEstabResets (8)

Figure 4.35 TCP Group

Notes
• Connection-oriented transport protocol group
• Has one table

60
Network Management: Principles and Practice
© Mani Subramanian 2011
Chapter 4 SNMPv1 Network Management: Organization and Information Models

TCP Connection Table

tcpConnTable
(tcp 13)

tcpConnEntry
(1)

tcpConnState (1) tcpCommRemPort (5)

tcpConnLocalAddress (2) tcpConnRemAddress(4)

tcpConnLocalPort (3)

Figure 4.36 TCP Connection Table

Notes
Entity OID Description (brief)

tcpConnTable tcp 13 TCO connection table

tcpconnEntry TcpConnTable 1 Information about a particular TCP
connection
tcpConnState TcpConnEntry 1 State of the TCP connection
tcpConnLocalAddress TcpConnEntry 2 Local IP address
tcpConnLocalPort TcpConnEntry 3 Local port number
tcpConnRemAddress TcpConnEntry 4 Remote IP address
tcpConnRemPort TcpConnEntry 5 Remote port number

61
Network Management: Principles and Practice
© Mani Subramanian 2011
 Chapter 4 SNMPv1 Network Management: Organization and Information Models

UDP Group
udp
(mib-2 7)

udpInDatagrams udpNoPorts udpInErrors udpOutDatagrams udpTable

(1) (2) (3) (4) (5)

udpEntry
(1)

udpLocAddress udpLocalPort
(1) (2)

Figure 4.37 UDP Group

Notes
• Connectionless transport protocol group
• Has one table, UDP table
Entity OID Description (brief)
udpInDatagrams udp 1 Total number of datagrams delivered to the
users
udpNoPorts udp 2 Total number of received datagrams for
which there is no application
udpInErrors udp 3 Number of received datagrams with errors
udpOutDatagrams udp 4 Total number of datagrams sent
udpTable udp 5 UDP Listener table
udpEntry udpTable 1 Information about a particular connection or
UDP listener
udpLocalAddress udpEntry 1 Local IP address
udpLocalPort udpEntry 2 Local UDP port

62
Network Management: Principles and Practice
© Mani Subramanian 2011