Case Histories
AT&T Network Management Centers
Network Control Centers
Network Operations Center CNN World Headquarters Centralized troubleshooting of NIC
Performance degradation due to NMS
Bell Operating company procedure
Managed LAN
NMS [Link] [Link]
Router 2 Backbone Network
Router 1 [Link]
Hub 1 [Link] Hub 2 [Link]
Figur e 4.1 A M an age d LAN Ne twork
NMS on subnet [Link] manages the router and the hubs on subnet [Link] across the backbone network
Internet SNMP Management
1970 Advanced Research Project Agency Network (ARPANET) Internet control Message Protocol (ICMP)
Internet Engineering Task Force (IETF) 1990 SNMPv1 1995 SNMPv2 1998 SNMPv3 Internet documents: Request for Comments (RFC) IETF STD Internet Standard FYI For your information Source for RFCs [Link]
[Link]
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 Communication services addressed by messages Security framework community-based model
SNMP Model
Two-Tier Organization Model
SNMP Manager SNMP Manager SNMP Manager
SNMPAgent Network Element
Network Agent Network Element
(a) One M anag e r - One Age nt M od e ( l b ) M ultiple M anage rs - On e Age n t M ode l
Any host that could query an agent is a manager
Three-Tier Organization Model: RMON
SNMP Manager
RMON Probe Managed Objects
Managed object comprises network element and management agent RMON acts as an agent and a manager RMON (Remote Monitoring) gathers data from MO, analyses the data, and stores the data Communicates the statistics to the manager
Three-Tier Organization Model: Proxy Server
SNMP Manager
Proxy Server
Non-SNMP Managed Objects
SNMP Managed Objects
Proxy server converts non-SNMP data from non-SNMP objects to SNMP compatible objects and messages
System Architecture
SNMP Manager SNMP Agent
M anagem ent Data
SNMP Manager Application
SNMP Agent Application
GetNext-Request
GetNext-Request
Get-Response
Get-Request
Get-Request
Set-Request
Set-Request
Get-Response
Trap
SNMP UDP IP DLC PHY
SNMP UDP IP DLC PHY
Physical Medium Figur e 4.9 SNM P Ne twork M anage me nt Arch ite ctur e
Messages between manager and agent Direction of messages - 3 from manager and 2 from agent
Trap
Get-Request Sent by manager requesting data from agent Get-Next-Request Sent by manager requesting data on the next object to the one specified Set-Request Initializes or changes the value of network element Get-Response Agent responds with data for get and set requests from the manager Trap Alarm generated by an agent
SNMP Messages
Information
Structure of Management Information (SMI) (RFC 1155)
Managed Object Scalar Aggregate or tabular object
Management Information Base (RFC 1213)
RFCs can be downloaded from
[Link]
Managed Object
Object
Object Type
Object Instance
Name: OBJECT IDENTIFIER
Syntax: ASN.1
Encoding: BER
Figure 4.10 M anage d Obje ct : Type and Instance
Object type and data type are synonymous Object identifier is data type, not instance Object instance IP address (See Figure 4.2)
Private MIB Example
Internet {1 3 6 1}
private (4)
enterprises (1)
cisco (9)
hp (11)
3Com (43)
Cabletron (52)
Figure 4.14 Priv ate Subtre e for Comme rcial Ve ndors
private MIB intended for vendor equipment IANA (Internet Assigned Numbers Authority) assigns identifiers
Encoding
Basic Encoding Rules (BER) Tag, Length, and Value (TLV)
Type Length Value
Class (7-8th bits)
P/C (6th bit)
Tag Number (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 00000110 00000011 00101011 00000110 00000001 would be the BER for the object identifier {1 3 6 1} Type = 6, length = 3, and the value is {1 3 6 1} where {1 3} is represented by the octet 43 (00101011)
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 | 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 systems 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]
MIB
Internet {1 3 6 1}
directory (1)
mgmt (2)
experimental (3)
private (4)
mib-2 (1)
system (1) interfaces (2) at (3) ip (4) icmp (5) tcp (6)
snmp (11) transmission (10) cmot (9) egp (8) udp (7)
Figu re 4.26 Inte rne t M IB-II Group
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
TCP Group
tcp (mib-2 6)
tcpRtoAlgorithm (1) tcpRtoMin (2)
tcpOutRsts (15) tcpInErrors (14) tcpConnTable 13) tcpRetranSegs (12)
tcpRtoMax (3) tcpMaxConn (4) tcpActiveOpens (5) tcpOutSegs (11) tcpPassiveOpens (6) tcpInSegs (10) tcpAttemptF ails (7) tcpCurrEstab (9) tcpEstabResets (8)
Figur e 4.35 TCP Grou p
Connection-oriented transport protocol group Has one table
