Network Management

1
Network Management

• SNMPv2
• Minimodule 3, 2006-03-03

By Ole Krog Thomsen TDC
2
SNMPv2 documents

• RCF 1901 Introduction to Community-based SNMPv2
  (SNMPv2c)
• RFC 1902 Structure of Management Information for
  Version 2 of the Simple Network Management
  Protocol (SNMPv2)
• RFC 1903 Textual Conventions for Version 2 of the
  Simple Network Management Protocol (SNMPv2)
• RFC 1904 Conformance Statements for Version 2 of
  the Simple Network Management Protocol (SNMPv2)
• RFC 1905 Protocol Operations for Version 2 of the
  Simple Network Management Protocol (SNMPv2)
• RFC 1906 Transport Mappings for Version 2 of the
  Simple Network Management Protocol (SNMPv2)
• RFC 1907 Management Information Base for Version
  2 of the Simple Network Management Protocol
  (SNMPv2)
• RFC 1908 Coexistence between Version 1 and
  Version 2 of the Internet-standard
  Network Management Framework
• RFC 1909 An Administrative Infrastructure for
  SNMPv2 (SNMPv2u)
• RFC 1910 User-based Security Model for SNMPv2
  (SNMPv2u)

3
SNMPv2 Major Changes

• Bulk data transfer
• Manager-to-manager message
• Enhancements to SMI SMIv2
• Module definitions MODULE-IDENTITY macro
• Object definitions OBJECT-TYPE macro
• Trap definitions NOTIFICATION-TYPE macro
• Textual conventions
• Conformance statements
• Row creation and deletion in table
• MIB enhancements
• Transport mappings

4
SNMPv2 New Messages

• inform-request
• manager-to-manager message
• get-bulk-request
• transfer of large data
• report
• not used

5
SNMPv2 Management Architecture
6
Module Identity Macro
7
Example of MODULE-IDENTITY Macro
8
OBJECT ??

• OBJECT IDENTIFIER defines the administrative
  identification of a node in the MIB
• OBJECT-IDENTITY macro assigns an object
  identifier to an object identifier in the MIB
• OBJECT-TYPE macro defines the type of a
  managed object

9
OBJECT-IDENTITY / OBJECT-TYPE

• OBJECT-IDENTITY is high level description
• OBJECT-TYPE details description needed for
  implementation

10
OBJECT-IDENTITY / OBJECT-TYPE
11
Table Expansion

• Augmentation of a table (dependent table)
  adds additional columns to an existing table
  (base table)
• Dense table enables addition of more rows to
  base table
• Sparse table supplements less rows to a base
  table

12
Textual Convention

• Enables defining new data types
• Makes semantics of data types consistent and
  human readable
• Creates new data types using existing ones and
  applies restrictions to them
• An important textual convention in SNMPv2,
  RowStatus creates and deletes rows

13
DisplayString (rfc 2579)

• DisplayString TEXTUAL-CONVENTION
• DISPLAY-HINT "255a
• STATUS current
• DESCRIPTION
• "Represents textual information taken
  from the NVT ASCII
• character set, as defined in pages 4,
  10-11 of RFC 854
• To summarize RFC 854, the NVT ASCII
  repertoire specifies
• - the use of character codes 0-127
  (decimal)
• - the graphics characters (32-126)
  are interpreted as US ASCII
• - NUL, LF, CR, BEL, BS, HT, VT and
  FF have the special
• meanings specified in RFC 854
• - the other 25 codes have no
  standard interpretation
• - the sequence 'CR LF' means
  newline
• - the sequence 'CR NUL' means
  carriage-return
• - an 'LF' not preceded by a 'CR'
  means moving to the
• same column on the next line.
• - the sequence 'CR x' for any x
  other than LF or NUL is
• illegal. (Note that this also
  means that a string may
• end with either 'CR LF' or 'CR
  NUL', but not with CR.)

14
MacAddress (rfc 2579)

• MacAddress TEXTUAL-CONVENTION
• DISPLAY-HINT "1x
• STATUS current
• DESCRIPTION
• "Represents an 802 MAC address
  represented in the
• canonical' order defined by IEEE
  802.1a, i.e., as if it
• were transmitted least significant
  bit first, even though
• 802.5 (in contrast to other 802.x
  protocols) requires MAC
• addresses to be transmitted most
  significant bit first." SYNTAX OCTET
  STRING (SIZE (6))

15
Date and Time (rfc 2579)

• DateAndTime TEXTUAL-CONVENTION
• DISPLAY-HINT "2d-1d-1d,1d1d1d.1d,1a1d1d
• STATUS current
• DESCRIPTION "A date-time
  specification.
• field octets contents
  range
• ----- ------ --------
  -----
• 1 1-2 year
  0..65536
• 2 3 month
  1..12
• 3 4 day
  1..31
• 4 5 hour
  0..23
• 5 6 minutes
  0..59
• 6 7 seconds
  0..60
• (use 60 for
  leap-second)
• 7 8 deci-seconds
  0..9
• 8 9 direction from UTC
  '' / '-
• 9 10 hours from UTC
  0..13
• 10 11 minutes from UTC
  0..59
• Notes - the value of
  year is in network-byte order
• - daylight saving time in New Zealand
  is 13

16

17
Row Creation and Deletion
18
Create-and-Go Row Creation
19
Row Deletion
20
Create Cross Connection

• Operation Create a PVC on system node 1, subrack
  32, slot position 36,
• port 1, user port VPI value of 32 and user port
  VCI value of 48.
• Example Script
• snmpset cp1 1.3.6.1.4.1.193.18.1.5.6.1.1.7.1.32.36
  .1.32.48 integer 32 \
• 1.3.6.1.4.1.193.18.1.5.6.1.1.8.1.32.36.1.32.48
  integer 1 \
• 1.3.6.1.4.1.193.18.1.5.6.1.1.9.1.32.36.1.32.48
  integer 1 \
• 1.3.6.1.4.1.193.18.1.5.6.1.1.10.1.32.36.1.32.48
  integer 22 \
• 1.3.6.1.4.1.193.18.1.5.6.1.1.11.1.32.36.1.32.48
  integer 48 \
• 1.3.6.1.4.1.193.18.1.5.6.1.1.12.1.32.36.1.32.48
  integer 2 \
• 1.3.6.1.4.1.193.18.1.5.6.1.1.13.1.32.36.1.32.48
  integer 3 \
• 1.3.6.1.4.1.193.18.1.5.6.1.1.14.1.32.36.1.32.48
  integer 500 \
• 1.3.6.1.4.1.193.18.1.5.6.1.1.15.1.32.36.1.32.48
  integer 1000 \
• 1.3.6.1.4.1.193.18.1.5.6.1.1.16.1.32.36.1.32.48
  integer 1 \
• 1.3.6.1.4.1.193.18.1.5.6.1.1.19.1.32.36.1.32.48
  integer 1 \
• 1.3.6.1.4.1.193.18.1.5.6.1.1.25.1.32.36.1.32.48
  integer 1 \
• 1.3.6.1.4.1.193.18.1.5.6.1.1.26.1.32.36.1.32.48
  integer 4 \
• 1.3.6.1.4.1.193.18.1.5.6.1.1.27.1.32.36.1.32.48
  integer 2

21
Conformance OBJECT-GROUP

• Conformance defined by
• OBJECT-GROUP macro
• NOTIFICATION-GROUP macro
• OBJECT-GROUP
• Compiled during implementation, not at run time
• OBJECTS clause names each object
• Every object belongs to an OBJECT-GROUP
• Access defined by MAX-ACCESS, the maximum
  access privilege for the object

22
Example of OBJECT-GROUP Macro
23
Conformance NOTIFICATION-GROUP

• NOTIFICATION-GROUP
• Contains trap entities defined in SMIv1
• NOTIFICATIONS clause identifies the
  notifications in the group
• NOTIFICATIONS-GROUP macro compiled during
  implementation, not at run time

24
Example of NOTIFICATION-GROUP Macro
25
Compliance

• Compliance has two classes of groups
• MANDATORY-GROUPS ... Required
• GROUP Optional

26
Compliance Statements
27
Agent Capabilities

• AGENT-CAPABILITIES macro
• SUPPORTS modules and includes groups
• VARIATION identifies additional features

28
Example of AGENT-CAPABILITIES Macro
29
SNMPv2 PDU
30
(No Transcript)
31
SNMPv2 GetBulkRequest PDU
32
Get-Next-Request Operation
33
Get-Bulk-Request Operation
34
SNMPv2 Trap
35
Example of NOTIFICATION-TYPE Macro
36
Inform-Request

• Inform-Request behaves as trap in that the
  message goes from one manager to another
  unsolicited
• The receiving manager sends response to the
  sending manager

37
Bilingual Manager
38
SNMP Proxy Server
39
SNMP Proxy Server Behaviour