Transcript Network Management System and The Application in WiMAX

by Dedi Rahmawan Putra
Advisor: Dr. Kai-Wei Ke
March, 11 2008
Network Management and Its Application
1
Outline
 Network Management
 Simple Network Management Protocol (SNMP)
 Structure of Management Information (SMI)
 Management Information Bases (MIBs)
 SNMP Manager and Agent(s) Application on 802.16
device
March, 11 2008
Network Management and Its Application
2
March, 11 2008
Network Management and Its Application
3
by IETF (for INTERNET)
 Defining the standard (deciding on the content)
 IESG: decides on formal status
 Important area includes :
Operations and Managements
 Standard made by this group:
Simple Network Management Protocol (SNMP)
March, 11 2008
Network Management and Its Application
4
by ISO
 important for the definition of Network Management
Standard
 defined by: ISO-IEC/JTC1/WG4
 Part of OPEN SYSTEM INTERCONNECTION (OSI)
 OSI has little practical function
 Protocol defined for management:
 CMIP: Common Management Information Protocol
 CMIS: Common Management Information Service
March, 11 2008
Network Management and Its Application
5
by ITU-T
 defined by SG-IV
 Standard for network made by this group:
TMN: Telecommunication Management Network
 Another groups within ITU-T also work on
management
March, 11 2008
Network Management and Its Application
6
Other Groups
 DMTF (Distributed Management Task Force)
 WBEM: Web Based Enterprise Management
 CIM: Common Information Model
 TM-Forum (Tele-Management Forum)
 Originally based on OSI
 OMG (Object Management Group)
 looking at CORBA for management
 IEEE
March, 11 2008
Network Management and Its Application
7
Differences
IETF
ISO
TMN
Management should be
simple
Management should be
powerful
Define management
architecture only
Variable Oriented
Approach
Object Oriented
Approach
Using OSI protocol
(CMIP & CMIS)
Unreliable transport
mechanisms
Reliable underlying
transport
Management Information
is exchanged out-of-band
March, 11 2008
Network Management and Its Application
8
COPIED:
• Manager-Agent concept
• MIBS
• ASN.1
• TERMINOLOGY
History
starting as temporary solution
many ideas were copied from OSI
Management framework
OSI introduced new ideas
Real object orientation
OSI Protocol Copied
March, 11 2008
Network Management and Its Application
9
Simple Network Management Protocol
March, 11 2008
Network Management and Its Application
10
SNMP Milestone
SGMP SNMP
draft
SNMP
SNMPv2
Security SMP (parties)
full
standard
SNMPv2
(community)
SNMPv3
implementation
experience
proposed
draft
standard
standard
draft
standard
proposed
standard
March, 11 2008
Network Management and Its Application
11
Standard
 SMI (Structure of Management Information)
Define how management information may look like
 SMIv1: RFC 1155
 SMIv2: RFC2578 (currently used)
 MIBs (Management Information Bases)
Tell what management information exists
 MIB-I: RFC1156
 MIB-II: RFC1213
 SNMP (Simple Network Management Protocol)
Define how information is exchanged
 SNMPv1: RFC1157
 SNMPv2: RFC1901, 1905, 1906
 SNMPv3: RFC2571-2575
March, 11 2008
Network Management and Its Application
12
Goals of SNMP
 Ubiquity
 Inclusion of SNMP functionality should be easy
 Small code
 Limited functionality
 Management Extension should be easy
 Management Information is modular
 Adding new MIBs is easy
 Management should be robust
 Using connectionless transport
March, 11 2008
Network Management and Its Application
13
Principle Operation
Transport SNMP
v1 : unreliable
v2/v3: reliable alternatives
Manager
poll
GET/SET
poll
poll
TRAPS
Agents
variable
MIB
table
March, 11 2008
Network Management and Its Application
14
SNMP Layering
REAL VALUE
Manager knows
definition
MIB
Agents
Manager
SNMP PDUs
Connectionless Transport Service Provider (UDP)
March, 11 2008
Network Management and Its Application
15
SNMPv1 Command
Command
Operational Result
GetRequest
Request the values of one or more MIB variables
GetNextRequest
Enables MIB variables to be read sequentially, one
variable at a time
SetRequest
Permits one or more MIB values to be updated
GetResponse
Used to respond to a GetRequest, GetNextRequest, or
SetRequest
Trap
Indicates the occurence of a predefined condition
March, 11 2008
Network Management and Its Application
16
SNMPv2 Command (mod. to v1)
Command
Operational Result
GetBulkRequest
Almost similar with GetNextRequest, except it tells the
agent to return as much data as possible that can fit into a
response message commencing with the next larger value
than the requested managed object.
InformRequest
Enable the communication between managers.
Response
Similar with GetResponse command in SNMPv1, only the
the command was renamed.
March, 11 2008
Network Management and Its Application
17
Remote Monitoring (RMON)
 An extension of the network manager’s operation.
 Monitor the data flowing on the remote network using




probe or RMON agents.
RMON agents or probe has MIBs (v1:RFC1757; v2:RFC2021)
Overcomes degradation of lower operating rate WAN
bandwidth when monitoring geographically separated
networks.
Reduces the amount of information required to be
transmitted to NMS.
Reduces the potential bandwidth saturation of the WAN
circuit.
March, 11 2008
Network Management and Its Application
18
RMON Principle Operation
Network
Management
Station
RMON Agent/Probe
WAN circuit
RMON-MIBs
Agent
MIB
March, 11 2008
Network Management and Its Application
19
Structure of Management Information
and
Management Information Bases
March, 11 2008
Network Management and Its Application
20
SMI
 Denotes :
 How MIB variables in an MIB are related to one another.
 How variables are formatted.
 Information to obtain the standardization of the MIB.
 Additional RFC:
 1212: concise MIB definition (extends SMIv1)
 2578: textual convention (definition of new types)
 Purpose: to make the definition of new MIBs easier
 Help to guide MIB designer
 Define the syntax
 Allow tools to be built
March, 11 2008
Network Management and Its Application
21
How Mngmt Information is Stored?
 Management information within managed systems
may be represented as:
 SCALAR
 eg. Current time, number of packet arrived
 Type: integer, character, etc.
 TABLES
 eg. Two dimensional array of scalar.
 Create a structure of scalars (size can be
dynamic).
March, 11 2008
Network Management and Its Application
22
How Mngmt Info. is Exchanged?
 Can only exchange (a list of) scalars.
 Cannot read/write a table with an operation.
 To get a table one should reach each individual
elements (quite complex).
March, 11 2008
Network Management and Its Application
23
SMI vs. OSI
 OSI management may have arbitrary structures.
 OSI supports the retrieval a complete table in one
command.
 SMI is defined based on 1988 ASN.1 constructs
inherited from OSI.
 The SMI research group tried to get rid of ASN.1
 There’s no OSI standard for that version anymore, it has
been removed from OSI
 Building tools with ASN.1 is relatively difficult
 SMIv2 improves SMIv1
March, 11 2008
Network Management and Its Application
24
SMIv2 Data Types of Scalars
SMIv2
SIMPLE TYPES
APPLICATION WIDE TYPES
PSEUDOTYPES
March, 11 2008
SMIv1
INTEGER
INTEGER
OCTET STRING
OCTET STRING
OBJECT IDENTIFIER
OBJECT IDENTIFIER
Integer32
-
Unsigned32
-
Gauge32
Gauge32
Counter32
Counter32
Counter64
-
TimeTicks
TimeTicks
IpAddress
IpAddress
Opaque
Opaque
-
Network Address
BITS
-
Network Management and Its Application
25
Example of Scalar Object
OCTET STRING
IpAddress
name
TimeTicks
uptime
address
SNMP
MANAGER
March, 11 2008
AGENT
Network Management and Its Application
26
Object Naming
1.2
1.1
1.2.1
March, 11 2008
Network Management and Its Application
1.2.2
27
Object and Instance
 Object is the definition of something
 Instance has value
 In scalar, no distinction between object and instances
 But in terms of table, object may have multiple
instances, multiple rows
 The case of table it’s useful to make distinction
 To denote the instance, we need to add zero “0” after
the ID of the object to get its value
March, 11 2008
Network Management and Its Application
28
Get the value
1.1.0
1.2.1.0
March, 11 2008
Network Management and Its Application
1.2.2.0
29
Standard Naming Tree
March, 11 2008
Network Management and Its Application
30
Object Type Definition
OBJECT-TYPE:
March, 11 2008
SYNTAX
INTEGER
OCTET STRING
OBJECT IDENTIFIER
BITS
IpAddress
Integer32
Counter32
Counter64
Gauge32
TimeTicks
Opaque
New Type
MAX-ACCESS
read-only
read-write
read-create
accessible-for-notify
not-accessible
STATUS
current
deprecated
obsolete
DESCRIPTION
“”
Network Management and Its Application
31
e.g. Definition of Leaf Object
-- Definition of address
address OBJECT-TYPE
SYNTAX
IpAddress
MAX-ACCESS
read-write
STATUS
current
DESCRIPTION “Internet Address of this system”
::= {NEW-MIB 1}
March, 11 2008
Network Management and Its Application
32
e.g. Definition of Non-Leaf Object
 Using OBJECT IDENTIFIER
info OBJECT-IDENTIFIER ::= {NEW-MIB 2}
 Using OBJECT IDENTITY
info OBJECT-IDENTITY
STATUS
current
DESCRIPTION “The intermediate node”
::= {NEW-MIB 2}
March, 11 2008
Network Management and Its Application
33
Definition of A MIB
NEW-MIB DEFINITIONS ::=
BEGIN
import statement(s)
module identity definition
definition of all node and leaf objects
definition of implementation requirements
END
March, 11 2008
Network Management and Its Application
34
e.g. Module Identity Definition
newMIBModule MODULE-IDENTITY
LAST-UPDATED “200803111600Z”
ORGANIZATION “NTUH”
CONTACT-INFO ”
National Taiwan University Hospital
Taiwan
DESCRIPTION
“An Example of MIB Module”
:= {enterprises ntuh(20510) 2}
March, 11 2008
Network Management and Its Application
35
e.g. Import Statement Definition
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE,
TimeTicks, enterprises
FROM SNMPv2-SMI;
March, 11 2008
Network Management and Its Application
36
Retrieve Value from Table Entries
Way 1 (not being used by SNMP)
1.3.2.5 = 3
Way 2: X.C.I (used by SNMP)
new-MIB.routeTable.next.8 = 3
destination
March, 11 2008
Network Management and Its Application
37
Table Indexing
 We also can use GetNext to retrieve table elements.
 Index not need to be a consecutive number.
 Not only Integer, any data type in SMI is allowed.
 If index value is not unique:
 add more index value which means we add another
column to make it unique (multiple indexes).
 The formula becomes X.C.I1.I2.
March, 11 2008
Network Management and Its Application
38
Table Definition
-- Definition of the route table
routeTable OBJECT-TYPE
SYNTAX
SEQUENCE OF RouteEntry
MAX-ACCESS
not-accessible
STATUS
current
DESCRIPTION
“This entity’s routing table”
::={NEW-MIB 3}
routeEntry OBJECT-TYPE
SYNTAX
RouteEntry
MAX-ACCESS
not-accessible
STATUS
current
DESCRIPTION
“A route to a particular destination”
INDEX
{dest}
::={routeTable 1}
March, 11 2008
Network Management and Its Application
39
Table Definition (cont. 1)
-- Definition of the new type for the row
RouteEntry ::=
SEQUENCE{
dest IpAddress,
next IpAddress
}
March, 11 2008
Network Management and Its Application
40
Table Definition (cont. 2)
dest OBJECT-TYPE
SYNTAX
MAX-ACCESS
STATUS
DESCRIPTION
destination”
::={route-entry 1}
IpAddress
read-only
current
“The address of a particular
next OBJECT-TYPE
SYNTAX
MAX-ACCESS
STATUS
DESCRIPTION
::={route-entry 2}
IpAddress
read-write
current
“The internet address of the next hop”
March, 11 2008
Network Management and Its Application
41
Textual Convention
 To refine semantics of existing types.
 Example:
RunState ::= TEXTUAL CONVENTION
STATUS
current
DESCRIPTION
“…”
SYNTAX
INTEGER {
running (1)
runable (2)
waiting (3)
exiting (4)
}
March, 11 2008
Network Management and Its Application
42
Notification Type
 With SMIv2 and SNMPv2, there is a condition defined
in MIB which if they happen, lead to a notification at
the manager
 Example:
linkUp NOTIFICATION-TYPE
OBJECTS
{ifIndex}
STATUS
current
DESCRIPTION
“A linkUp trap signifies that the entity has detected
that the ifOperStatus object has changed to Up”
::={snmpTraps 4}
March, 11 2008
Network Management and Its Application
43
March, 11 2008
Network Management and Its Application
44
MIB-II
 Defines the variables to manage the TCP/IP Protocol
Stack.
 Doesn’t define the layer below IP, nor the application
on the top of transport layer.
 There are 170 variables being defined in MIB-II, mostly
read-only.
 Defined based on SMIv1.
March, 11 2008
Network Management and Its Application
45
Design Criteria
 Essential for Fault or Configuration Management
 Only weak control objects
 Small number of object are defined
 Avoid Redundancy
 Evidence on utility
 Do not disturb normal operation
 No implementation specific issues
March, 11 2008
Network Management and Its Application
46
Structure
March, 11 2008
Network Management and Its Application
47
MIB-II Groups in a Protocol Stack
SYSTEM
INTERFACES
TRANSMISSION
March, 11 2008
Network Management and Its Application
48
System Group
March, 11 2008
Network Management and Its Application
49
sysServices
physical layer (e.g. repeaters)
data-link layer (e.g. bridges)
internet layer (e.g. IP routers)
end-to-end (e.g. IP hosts)
application (e.g. nfs servers)
March, 11 2008
Network Management and Its Application
50
System Group Example
sysDescr:
Hardware: x86 Family 15 Model 4
Stepping 7 AT/AT COMPATIBLE Software: Windows 2000 Version 5.1
(Build 2600 Multiprocessor Free)
sysObjectID: 1.3.6.1.4.1.311.1.1.3.1.1
sysUpTime: 37153422 (4 days, 7 h, 12 min, 14.22 s)
sysContact: [email protected]
sysName:
DEDI
sysLocation: Lab407-2
sysServices: 76
March, 11 2008
Network Management and Its Application
51
Conclusion
 SNMP become the most popular Network
Management System for INTERNET world.
 The current SNMP used: SNMPv1, SNMPv2c, and
some SNMPv3.
 The current SMI used: SMIv2
 The current MIB used: MIB-2
March, 11 2008
Network Management and Its Application
52
References
 Aiko Pras, (2000). Internet Management Protocol,
http://www.simpleweb.org . Centre for Telematics and
Information Technology, University of Twente,
Netherland.
 Gilbert Held, (2000). Managing TCP/IP Networks:
Technique, Tools and Security Consideration. John
Wiley&Sons Ltd.
March, 11 2008
Network Management and Its Application
53