nms total slides

7/31/2019 NMS Total Slides

1/213


2/213


3/213

L1-2 3

R e g i o n a l C e n t e r

C l a s s 1 s w i t c h

S e c t i o n a l C e n t e r


P r i m a r y C e n t e r


T o l l C e n t e r

C l a s s 4 s w i tc h

E n d O f f i c e


R e g i o n a l C e n t e r


S e c t i o n a l C e n t e r


P r i m a r y C e n t e r


T o l l C e n t e r

C l a s s 4 s w i tc h

E n d O f f i c e


V o ic e V o ic e

T o o t h e r

R e g i o n a l c e n t e r s

S e c t i o n a l c e n t e r s

P r i m a r y c e n t e r s

T o l l c e n t e r s

E n d o f fi c e s

T o o t h e r P r i m a r y c e n t e r s

T o l l c e n t e r s

E n d o f fi c e s

T o o t h e r

C l a s s 4 t o l l p o i n t s

E n d o f fi c e s

F i g u r e 1 . 1 T e l e p h o n e N e t w o r k M o d e l

L e g e n d :

L o o p

D i re c t T r u n k

T o l l - C o n n e c t i n g T r u n k

T o l l T r u n k


4/213

L1-3 4

Notice the hierarchy of switches

Primary and secondary routes programmed

Automatic routing

Where is the most likely failure?

Use of Operations Systems to ensure QoS


5/213

L1-4 5

Operations Systems / NOC

Monitor telephone network parameters S/N ratio, transmission loss, call blockage, etc.

Real-time management of network

Trunk (logical entity between switches) maintenance

system measures loss and S/N. Trunks not meeting

QoS are removed before customer notices poorquality


6/213


7/213

L2-1 7

Data and Telecommunication Network

T e r m i n a l

M o d e m

V o i c e

T e r m i n a l

M o d e m M o d e m

V o i c e

H o s t

D a t a c o m m u n i c a t i o n n e t w o r k

T e l e c o m m u n i c a t i o n n e t w o r k

F i g u r e 1 . 3 D a t a a n d T e l e c o m m u n i c a t i o n N e t w o r k s

L o o p L o o p L o o p


8/213


9/213


10/213


11/213

L2-5 11

U s e r A

A p p li c a ti o n L a y e r s

T r a n s p o r t L a y e r s

U s e r Z

A p p li c a ti o n L a y e rs


P h y s i c a l M e d i u m

P e e r - P r o t o c o l I n t e r f a c e

( a) D i re c t C o m m u n ic a ti o n b e tw e e n E n d S y s t e m s

U s e r A



U s e r Z




P e e r - P r o t o c o l I n t e r f a c e

( b ) C o m m u n ic a ti o n b e t w e e n E n d S y s te m s v i a a n I n t e rm e d i a te S y s t e m

T r a n s p o r t L a y e r

C o n v e r s i o n

F i g u r e 1 .1 1 B a s i c C o m m u n i c a ti o n A r c h i te c t u r e

S y s te m A In t e rm e d i a t e s y s te m S y s te m Z



12/213

L2-6 12

Inter-layer interface: user and service provider

Peer-layer protocol interface

Analogy of hearing-impaired student

Role of intermediate systems

Gateway: Router with protocol conversion asgateway to an autonomous network or subnet


13/213


14/213


15/213


16/213

L3-2 16

NM Case Histories The case of the Footprint

Case of the crashing bridge

R epeater R epea te r R epea te r R ep eater

B ridge

Mai l ServerBackup Server

ISP

R ep ea te r R epea te r R epe ate r R e pe a te r

B ridge

Mai l ServerBackup Server

ISP

Bridge

M a i l S e r v e r Backup Server

ISP

Hub Hub Hub

(a) Mult i-Segment Bus LAN with Single Port Bridge Connect ion

(b) Dual Mult i-Segment Bus LANs with Two-port Bridge Connect ion

(c) Mult i-Segment Hub Conf iguration

Figure 1.20 Case History 2: Network Conf iguration Evolut ion


17/213


18/213


19/213

L4-2 19

Network ManagementN e t w o r k

M a n a g e m e n t

N e t w o r k

P r ov i s i on i ng

N e t w o r k

Op e r a t i ons

N e t w o r k

M a i n t e n a n c e

P l a n n i n g

D e s i gn

F a u l t M a n a g e m e n t

T r ou b l e T i c k e t

Ad m in is tra tio n

Network Ins tal lat ion

N e t w o r k R e p a i r s

Fac i l i t ies Ins tal lat ion

& M a i n t e n a n c e

R ou t i ne N e t w o r k

T e s t s

F au l t M anage m e n t / Se r v i c e R e s t o r a ti on

C o n f ig u r a ti o n M a n a g e m e n t

Pe r f o r m anc e M anage m e n t / T r a f f i c M anage m e n t

S e c u r it y M a n a g e m e n t

Ac co un tin g M an ag em en t

R e p o r ts M a n a g e m e n t

I n v e n to r y M a n a g e m e n t

D a t a Ga t he r i ng & Ana l y s e s

Figure 1.21 Network Management Functional Groupings

OAM&P Operations Administration Maintenance Provisioning


20/213


21/213


22/213


23/213

L5-3 23

Status and Future Trends

Future trends: Object-oriented approach

Service and policy management

Business management

Web-based management


24/213


25/213


26/213

M d H b


27/213

L1-3 27

Managed Hub:

System Information

Information obtained querying the hub

Data truly reflects what is stored in the hub

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.02System Contact :

System Location :System Object ID :.iso.org.dod.internet.private.enterprises.43.1.8.5System Up Time : (2475380437 ) 286 days, 12:03:24.37

Figure 4.2(a) System Information on 172.16.46.2 Hub


28/213

L1-4 28

Managed Router:

System Information

Tit le: System Information: router1.gatech.eduNam e or IP A ddress: 172.16.252.1

S yste m N am e : rou te r1 .g atech.eduS yste m De scription: Cisc oInternetwork Operat ing S ystem S oftware

: IO S (tm) 7000 Software (C7000 -JS-M), Ve rsion

: 11.2(6),REL EASE S O FTW ARE (g e 1 ): Copyr ight (c) 198 6-1997 by Cisco System s, Inc.: Compi ledTue 06-May-97 19 :11 bykuong

System ContactS yste m L oca tio n :System O bject ID : iso.org.dod. in ternet .pr ivate.enterpr ises.c isco.c iscoP roducts.

c isco 7 000S yste m U p T im e : (3 15 13 17 95) 36 days, 11:21:57.95

Figure 4.2(c) System Information on Router


29/213


30/213


31/213


32/213


33/213

L2-4 33

SNMP Model

Communication Model

Transfer syntax

SNMP over TCP/IP

Communication services addressed by messages

Security framework community-based model


34/213

L3-1 34

Two-Tier Organization Model

N e t w o r k

E l e m e n t

S N M P A g e n t

S N M PM a n a g e r

N e t w o r k

E l e m e n t

N e t w o r k A g e n t

S N M PM a n a g e r S N M PM a n a g e r

( a ) O n e M a n a g e r - O n e A g e n t M o d e l( b ) M u l t i p l e M a n a g e r s - O n e A g e

Any host that could query an agent is a manager


35/213

Three Tier Organization Model:


36/213

L3-3 36

Three-Tier Organization Model:

RMON

Managed object comprises network

element an 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


37/213

System Architecture


38/213

L3-5 38

System Architecture

S N M P M a n a g e r

Ap p li ca ti on

Get-Response

Get-Request

GetNext-Request

Set-Request

Trap


S N M P

U DP

IP

DL C

P H Y

S N M P A g e n t

Ap p lic a tio n

Get-Response

Trap

S N M P A g e n t

S N M P

U D P

IP

D L C

PH Y


Figure 4.9 SNMP N etwork Management Architecture

Manage-

ment

Data

Get-Request

GetNext-Request

Set-Request

Messages between manager and agent Direction of messages - 3 from manager and

2 from agent


39/213

L3-6 39

SNMP Messages

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


40/213

L4-1 40

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

http://www.nic.mil/dodnic/RFC/

Managed Object


41/213

L4-2 41

Managed Object

Object type and data type are synonymous

Object identifier is data type, not instance

Object instance IP address

O b j e c t

O b j e c tI n s t a n c e

O b j e c tT y p e

E n c o d i n g :B E R

S y n t a x :A S N . 1

N a m e :O B J E C TI D E N T I F I E R

F i g u r e 4 . 1 0 M a n a g e d O b j e c t : T y p e a n d I n s t a n c e

P i t MIB E l


42/213

L4-3 42

Private MIB Example

e n t e r p r i s e s

(1 )

p r i v a t e

(4 )

h p

( 1 1 )

c i s c o

( 9 )3 C o m

( 4 3 )

C a b l e t r o n

( 5 2 )

F i g u r e 4 . 1 4 P r iv a t e S u b t r e e f o r C o m m e r c ia l V e n d o r s

I n t e r n e t

{ 1 3 6 1 }

private MIB intended for vendor equipment IANA (Internet Assigned Numbers Authority) assigns

identifiers


43/213

E di C td


44/213

L4-5 44

Encoding- Contd.

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)


45/213

L5-1 45

OBJECT-TYPE MACRO::=

BEGIN

TYPE NOTATION::=SYNTAX type(TYPE ObjectSyntax)

ACCESS Access

STATUS StatusVALUE NOTATION::=value(VALUE ObjectName)

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

Status ::=mandatory | optional | obsolete

END

Figure4.18(a) OBJECT-TYPEMacro[RFC1155]

Managed Object: Macro

sy sDescr OBJECT-TYPESYNTAX DisplayString(SIZE(0 ..255))

ACCESSread-onlySTATUS mandatoryDESCRIPTION

Atextual descriptionof theentity. This valueshouldincludethefull nameandversionidentificationof the

systems hardwaretype, software operating-system, andnetworkingsoftware. It is mandatorythat this onlycontainprintableASCII characters.

::={system1}

Figure4.18(b) Scalar or SingleInstanceMacro: sysDescr

[RFC1213]


46/213

L5-2 46

MIB

m g m t

(2 )

directory

(1 )

e xp e r i m e n ta l

(3 )

p r iva te

(4)

In te rne t

{1 3 6 1 }

mib -2

(1 )

Figure 4.26 Internet M IB-II Group

sys te m ( 1 )

in te r faces (2 )at (3)

ip (4)

i cm p ( 5 )

sn m p (1 1 )

t ransmiss ion (10 )cm ot (9 )

egp (8 )

udp (7 )

tcp (6)

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


47/213

L5-3 47

TCP Group

tc p

(m ib -2 6 )

t c pR t oA lgo r i t hm (1 )

t c pR t oM in (2 )

t c pR t oMax (3 )

tc p M a x C o n n ( 4)t c pAc ti v eOpe ns (5 )

t c pOut R s t s (15 )

tcpInErrors (14)

t c pC onnT ab le 13 )

t c pR e t ranS egs (12 )

t c pOut Segs (11 )

tc p P a s s iv e O p e n s (6 ) tc p In Se gs (1 0 )

tcpCurrEstab (9)tcpAt temptFa i ls (7)

t c pEs t abR es e t s (8 )

Figure 4.35 TCP Group

Connection-oriented transport protocol group Has one table


48/213


49/213

L1-1 49

Introduction

Standards

Standards organizations

Protocol standards of transport layers

Protocol standards of management

(application) layer

Management Models

Language


50/213

L1-2 50

Table3.1NetworkManagement Standards

Standard Salient Points

OSI / CMIP International standard(ISO/ OSI)

Management of datacommunications network - LANand

WAN

Deals withall 7layers

Most complete

Object oriented

Well structuredandlayered

Consumes largeresourceinimplementation

SNMP/Internet

Industry standard(IETF)

Originally intendedfor management of Internet components,currently adoptedfor WANandtelecommunicationsystems

Easy toimplement

Most widely implemented

TMN International standard(ITU-T)

Management of telecommunications network

BasedonOSI network management framework

Addresses bothnetwork andadministrativeaspects ofmanagement

IEEE IEEEstandards adoptedinternationally

Addresses LANandMANmanagement

Adopts OSI standards significantly

Deals withfirst twolayers of OSI RM

Web-basedManagement

Web-BasedEnterpriseManagement (WBEM)

JavaManagement ApplicationProgramInterface(JMAPI)


51/213

L1-3 51

OSI Architecture and Model

N e t w o r k

M a n g e m e n t

I n f o r m a t i o n

M o d e l

O r g a n i z a t i o n

M o d e l

F u n c t i o n a l

M o d e l

C o m m u n i c a t i o n

M o d e l

F i g u r e 3 . 1 O S l N e t w o r k M a n a g e m e n t M o d e l

Organization

Network management components Functions of components Relationships


52/213


53/213

L2-1 53

OSI Architecture and Model

N e t w o r k

M a n g e m e n t

I n f o r m a t i o nM o d e lO r g a n i z a t i o nM o d e l F u n c t i o n a lM o d e lC o m m u n i c a t i o nM o d e l


Communication Transfer syntax with bi-directional messages Transfer structure (PDU)


54/213

SNMP Architecture and Model


55/213

L2-3 55

SNMP Architecture and ModelN e t w o r k

M a n g e m e n t

In fo r m a t io nM o d e l

O r g a n i z a t i o nM o d e l

F u n c t i o n a lM o d e l

C o m m u n i c a t i o nM o d e l


Organization Same as OSI model

Information Same as OSI, but scalar

Communication Messages less complex than OSI

and unidirectional

Transfer structure (PDU) Functions

Application functions Operations Administration

Security


56/213

L2-4 56

TMN Architecture

Addresses management of telecommunication

networks

Based on OSI model

Superstructure on OSI network

Addresses network, service, and business

management


57/213

L3-1 57

Organizational Model

Manager Sends requests to agents

Monitors alarms Houses applications Provides user interface

Agent

Gathers information from objects Configures parameters of objects Responds to managers requests Generates alarms and sends them to

mangers

Managed object Network element that is managed Houses management agent All objects are not managed / manageable


58/213


59/213


60/213

L3-4 60

A g e n t / M a n a g e r

M a n a g e d o b j e c t s

A g e n t p r o c e s s

M a n a g e r

F i g u r e 3 . 3 T h r e e - T i e r N e t w o r k M a n g e m e n t O r g a n i z a t i o n M o d e l

M D B

M D B

M D B M a n a g e m e n t D a t a b a s e

Three-Tier Model


61/213

L3-5 61

Three-Tier Model

Middle layer plays the dual role

Agent to the top-level manager

Manager to the managed objects

Example of middle level:

Remote monitoring agent (RMON)


62/213

L3-6 62

M o M

A g e n t

A g e n t N M SM a n a g e r



F i g u r e 3 . 4 N e t w o r k M a n g e m e n t O r g a n i z a ti o n M o d e l w i th M o M

A g e n t p r o c e s s

M D B

M D B M D B

M o M M a n a g e r o f M a n a g e rsM D B M a n a g e m e n t D a t a b a s e

A g e n tM a n a g e r

A g e n t N M S

A g e n t

A g e n t N M SM a n a g e r

Manager of Managers

Agent NMS manages the domain MoM presents integrated view of domains Domain may be geographical, administrative,

vendor-specific products, etc.


63/213

L4-1 63

Structure of Management Information(SMI)

SMI defines for a managed object Syntax Semantics plus additional information such as status

Example

sysDescr: { system 1 }

Syntax: OCTET STRING

Definition: "A textual description of the entity. "

Access: read-onlyStatus: mandatory


64/213


65/213

L4-3 65

Management Data Base / Information Base

Distinction between MDB and MIB

MDB physical database; e.g.. Oracle, Sybase

MIB virtual database; schema compiled into

management software

An NMS can automatically discover a managedobject, such as a hub, when added to the network

The NMS can identify the new object as hubonly after the MIB schema of the hub is compiled

into NMS software


66/213

L4-4 66

Managed Object

Managed objects can be

Network elements (hardware, system)

hubs, bridges, routers, transmission facilities

Software (non-physical)

programs, algorithms

Administrative information

contact person, name of group of objects

(IP group)


67/213


68/213

Obj t T d I t


69/213

L5-1 69

Type

Name

Syntax

Definition

Status

Access

Instance

Object Type and Instance

Example of a circle circle is syntax Semantics is definition from dictionary

A plane figure bounded by a single curvedline, every point of which is of equal distance

from the center of the figure. Analogy of nursery school (i.e. rings, donuts, )


70/213


71/213

Managed Object:


72/213

L5-4 72

B e h a v i o u r

O b j e c t C l a s s :

C i r c u l a r o b j e c t

ObjectClass:

Elliptical

object

A t t r i b u t e s :c i rc l e , d i m e n s i o n

O p e r a t i o n s :P u s h

A t t r i b u t e s :e l l i p s e , d i m e n s i o n

N o t i f i c a t i o n s :N o t i fy c h a n g e s i n

a t tr ib u t e v a l u e s

F i g u r e 3 . 9 ( b ) O S I P e r s p e c t i v e

Managed Object:

OSI Perspective


73/213


74/213


75/213

ASN 1 Symbols


76/213

L6-3 76

ASN.1 Symbols

Symbol Meaning

::= Defined as

| or, alternative, options of a list

- Signed number

-- Following the symbol are comments

{} Start and end of a list

[] Start and end of a tag

() Start and end of subtype

.. Range


77/213


78/213


79/213


80/213


81/213


82/213

SNMP Architecture


83/213

L1-1 83

SNMP Architecture


Ap p li ca ti on

Get-Response

Get-Request

GetNext-Request

Set-Request

Trap


S N M P

U DP

IP

DL C

P H Y

S N M P A g e n t

Ap p lic a tio n

Get-Response

Trap

S N M P A g e n t

S N M P

U D P

IP

D L C

PH Y


Figure 4.9 SNMP N etwork Management Architecture

Manage-

ment

Data

Get-Request

GetNext-Request

Set-Request

Truly simple network management protocol Five messages, three from manager and two from agent

SNMP Messages


84/213

L1-2 84

SNMP Messages

Get-Request Get-Next-Request Set-Request Get-Response

Trap Generic trap Specific trap Time stamp

Generic trap coldStart warmStart linkDown linkUp authenticationfailure

egpNeighborLoss enterpriseSpecific

Specific trap for special measurements such asstatistics

Time stamp: Time since last initialization

Administrative Model


85/213

L2-1 85

Administrative Model

Based on community profile and policy

SNMP Entities: SNMP application entities

- Reside in management stations and networkelements

- Manager and agent

SNMP protocol entities

- Communication processes (PDU handlers)- Peer processes that support application entities

SNMP Community


86/213

L2-2 86


A u t h e n t i c a t i o n S c h e m e





S N M P A g e n t


A u t h e n t i c M e s s a g e s

F i g u r e 5 . 1 S N M P C o m m u n i t y


87/213


88/213

C it P fil C td


89/213

L2-5 89

Community Profile-Contd.

MIB view An agent is programmed to view only a subset

of managed objects of a network element

Access mode Each community name is assigned an access

mode:: read-only and read-write

Community profile: MIB view + access mode

Operations on an object determined by communityprofile and the access mode of the object

Total of four access privileges Some objects, such as table and table entry are

non-accessible

Administration Model


90/213

L3-1 90

Administration Model

Administration model is SNMP access policy SNMP community paired with SNMP

community profile is SNMP access policy

Parameters:

Community / communities

Agent / Agents

Manager / managers

Access Policy


91/213

L3-2 91

Access Policy

C o m m u n i t y

C o m m u n i t y P r o f i l e 1

C o m m u n i t y P r o f i l e 2 A g e n t 2

A g e n t 1

M a n a g e r

Access Policy


92/213

L3-3 92

Access Policy

Manager manages Community 1 and 2 network

components via Agents 1 and 2 Agent 1 has only view of Community Profile 1,

e.g. Cisco components Agent 2 has only view of Community Profile 2,

e.g. 3Com components Manager has total view of both Cisco and 3Com

components

Generalized Administration Model


93/213

L3-4 93

C o m m u n i t y 1

C om m un i t y P ro fi l e 1

C om mu n i t y P ro fi le 2

M a n a g e r 3

( C o m m u n i ty 1 , C o m m u n i t y 2 )

A g en t 2

A g e n t 1

C o m m u n i t y 2

C om m un i t y P ro fi l e 3

C o m m u n i ty P ro fi le 4 A g en t 4

A g e n t 3

M a n a g e r 2

(C o m m u n i t y 2 )

M a n a g e r 1

(C o m m u n i t y 1 )

Figure 5.3 SNM P Access Policy

Manager 1 manages community 1, manager 2community 2,and manager 3 (MoM) both communities1 and 2

Protocol Entities


94/213

L4-1 94

Protocol Entities

Protocol entities support application entities

Communication between remote peer processes

Message consists of

Version identifier Community name

Protocol Data Unit

Message encapsulated and transmitted

A p p li ca ti on

H e a d e r

IP

H e a d e r

U D P

H e a d e r

Vers ion Comm unit y SNMP PDU

A p p li c a ti o n P D U

D L C

H e a d e r

T rans por t PD U

N et w ork PD U

A pp li c a ti o n

P D U

T rans por t

P D U

N et w ork

P D U

D at a L ink

P D U

Figure 5.5 Encapsulated SNM P Message

DataS N M P

P D U


95/213

SNMP Operations


96/213

L4-3 96

p

F i g u r e 5 . 1 0 G e t - R e q u e s t O p e r a t i o n f o r S y s t e m G r o u p

G e t R e q u e s t ( s y s D e s c r . 0 )

G e t R e s p o n s e ( s y s D e s c r . 0 = " S u n O S " )

G e t R e q u e s t ( s y s O b j e c t I D . 0 )

G e t R e s p o n s e ( s y s O b j e c t I D . 0 = e n t e r p r i s e s . 1 1 . 2 . 3 . 1 0 . 1 . 2 )

G e t R e q u e s t ( s y s U p T i m e . 0 )

G e t R e s p o n s e ( s y s U p T i m e . 0 = 2 2 4 7 3 4 9 5 3 0 )

G e t R e q u e s t ( s y s C o n t a c t . 0 )

G e t R e s p o n s e ( s y s C o n t a c t . 0 = " " )

G e t R e q u e s t ( s y s N a m e . 0 )

G e t R e s p o n s e ( s y s N a m e . 0 = " n o c 1 " )

G e t R e q u e s t ( s y s L o c a t i o n . 0 )

G e t R e s p o n s e ( s y s L o c a t i o n . 0 = " " )

G e t R e q u e s t ( s y s S e r v i c e s . 0 )

G e t R e s p o n s e ( s y s S e r v i c e s . 0 = 7 2 )

M a n a g e r P r o c e s s

A g e n t

P r o c e s s


97/213


98/213


99/213


100/213

Lecture Plan


101/213

101

Unit-5

1. RMON Components

2. RMON MIB

3. RMON2 & MIB4. ATM RMON

5. A Case Study

6. ATM MIB

RMON Components


102/213

L1-1 102

p

RMON Probe Data gatherer - a physical device

Data analyzer Processor that analyzes data

D a t a

A n a l y z e r

R M O N

P r o b e

B A C K B O N E

N E T W O R K

S N M P

T r a f f i c

S N M P

T r a f f i c

L A N

R o u t e rR o u t e r

RMON Components Contd


103/213

L1-2 103

RMON Components-Contd.

RMON Remote Network Monitoring

Standards-based network management

protocol

Allows network information to be gathered

at a single workstation

Defines additional MIBs to provide a richer

set of data about network usage


104/213


105/213


106/213


107/213

L2-3 107

RMON2

Applicable to Layers 3 and above

Functions similar to RMON1

Enhancement to RMON1

Defined conformance and compliance


108/213


109/213


110/213

A Case Study


111/213

L3-1 111

A Case Study

A study at Georgia Tech on Internet traffic

Objectives Traffic growth and trend Traffic patterns

Network comprising Ethernet and FDDI LANs


112/213


113/213

ATM Technology


114/213

L4-1 114

ATM technology based on: VP / VC Fixed packet size or cell Small packet size (53 bytes) Statistical multiplexing Integrated services


115/213

ATM LAN Emulation (LANE)


116/213

L4-3 116

ATM LAN Emulation (LANE)

Difference between ATM and Ethernet

ATM is connection-oriented ATM makes one-to-one connection

ATM 20-byte addressing schemedifferent from 6-byte Ethernet MAC

address

LANE emulates services of a traditional LAN

LANE Protocol ArchitectureN e t w o r k L a y e r

N e t w o r k L a y e r


117/213

L4-4 117

L o g i c a l L i n k L a y e r

L A N E m u l a t i o n L a y e r

A T M A d a p t a t i o n L a y e r

A T M

P h y s i c a l L a y e r

A T M N e t w o r k

F i g u r e 9 . 3 L a y e r e d A r c h i t e c t u r e o f L A N E m u l a t i o n

L U N I




A T M



118/213

ATM LAN Emulation

D t t i


119/213

L5-1 119

Ethernet

Bridge

LEC

L E S

L E C S

B U S

A T M W o r k s t a t i o nL E C

U n i c a s t P k t

M u l t i c a s t / B r o a d c a s t P k t

L U N I I n t e r f a c e

L E C L A N E m u l a t i o n C l i e n t

L E C S L A N E m u l a t i o n C o n f i g u r a t i o n S e r v e r L E S L A N E m u l a t i o n S e r v e r

B U S B r o a d c a s t a n d U n k n o w n S e r v e r L U N I L A N U s e r N e t w o r k I n t e r f a c e

F i g u r e 9 . 5 L A N E m u l a t i o n C l i e n t C o n n e c t i o n s a c r o s s L U N I

D a t a c o n n e c t i o n

C o n t r o l c o n n e c t i o n

I n t e r f a c e


120/213

LANE Protocol Architecture


121/213

L5-3 121





A T M




M A C


L A N E m u l a t i o nL a y e r

A T M A d a p t a t i o n

L a y e r

A T M


M A C



A T M E L A N E t h e r n e t L A N

F i g u r e 9 . 6 P r o t o c o l A r c h i t e c t u r e o f A T M E L A N w i t h E t h e r n e t L A N

B r i d g e L E C

ATM Campus Network


122/213

L5-4 122

F D D I B a c k b o n e

N e t w o r k

R o u t e r

A T M S w i t c h

R o u t e r

R o u t e r

H u b

H u b

F i g u r e 9 . 7 A T M S w i t c h a s B r i d g e i n C a m p u s N e t w o r k

. . .

. . .

R o u t e r

R o u t e r

R o u t e r


123/213


124/213


125/213

ATM WAN Management

P i t P b l i P b l i


126/213

L6-1 126

F i g u r e 9 . 1 0 A T M F o r u m M a n a g e m e n t I n t e r f a c e R e f e r e n c e A r c h i t e c t

P r i v a t e

N e t w o r k

M a n a g e r

( N M S )

P r i v a t e

A T M

N e t w o r k

E n d

U s e r

M 2

P u b l i c

N e t w o r k

M a n a g e r

( N M S )

P u b l i c

A T M

N e t w o r k

M 4

P u b l i c

N e t w o r k

M a n a g e r

( N M S )

P u b l i c

A T M

N e t w o r k

M 4

M 5M 3

M 1

B I C IP u b l i c

U N I

P r i v a t e

U N I

BICI Broadband inter-carrier interface


127/213

ATM MIB


128/213

L6-3 128

a t m F o r u m N e t w o r k M a n a g e m e n t ( 5 )

a t m f L a n E m u l a t io n ( 4 )

m g m t( 2 )

p r i v a t e( 4 )

I n t e r n e t{ 1 3 6 1 }

a t m F o r u m A d m i n ( 1 )

a t m F o r u m U n i ( 2 )

a t m U n i D x i ( 3 )

m i b - 2( 1 )

i n t e r fa c e s

( 2 )

i fM I B

( 3 1 )

e n t e r p r i s e s

( 1 )

a t m F o r u m( 3 5 3 )

t r a n s m i s s i o n

( 1 0 )

a t m M I B

( 3 7 )

a t m M I B O b j e c t s( 1 )

s y s t e m

( 1 )

i fM I B O b j e c t s( 1 )

ATM MIB


129/213

L6-4 129

MIBs defined in two sets of documents - IETF(5 nodes) & ATM Forum (1 node)

ATM MIBs address ATM sublayer parameters only

ifMIB contains additional objects not covered in

interfaces MIB atmMIB contains ATM objects

atmForum specifies interfaces, LANE, Mx, and ILMI

atmRMON (experimental) address ATM remotemonitoring (covered in Chapter 8)


130/213


131/213


132/213


133/213


134/213


135/213


136/213


137/213

ATM UNI Group


138/213

L8-3 138

a t m f A d d r e s s R e g i s t r a t i o n A d m i n G r o u p ( 1 1 )

a t m f V c c A b r G r o u p ( 1 0 )

a t m f V p c A b r G r o u p ( 9 )

a t m f S r v c R e g i s t r y G r o u p ( 8 )

a t m f N e t P r e f i x G r o u p ( 7 )

a t m f P h y s i c a l G r o u p ( 1 )

a t m F o r u m U N I( 2 )

a t m f A t m L a y e r G r o u p ( 2 )

a t m f A t m S t a t s G r o u p ( 3 )

a t m f V p c G r o u p ( 4 )

F i g u r e 9 . 1 8 A T M U N I M I B O b j e c t G r o u p

a t m F o r u m{ e n t e r p r i s e s 3 5 3 }

a t m f V c c G r o u p ( 5 ) a t m f A d d r e s s G r o u p ( 6 )


139/213


140/213


141/213


142/213

Network Element ViewN M S


143/213

L8-8 143

N M S

E n v i r o n m e n t

A T M

N E

A T M

N E

A T M

N E

A T M

N E

A T M

N E

M 4 I n t e r f a c e

( A T M N E V i e w O n l y )

F i g u r e 9 . 2 2 N E - V i e w M a n a g e m e n t A r c h i t e c t u r e

Network element view architecture proposed byATM Forum

Multiple agent layers - SNMP and ILMI agents

implied in the representation


144/213


145/213

OS: Trunk Testing SystemT r u n k


146/213

L1-1 146

T e l e c o m m u n i c a t i o n N e t w o r k

F i g u r e 1 1 . 1 O p e r a t i o n s S y s t e m f o r N e t w o r k T r a n s m i s s i o n

P u b l i c S w i t c h

T r a n s m i s s i o nT e s t S y s t e m

T r a n s m i s s i o nT e s t S y s t e m

P u b l i c S w i t c h

T e s t S y s t e m

V o i c e V o i c e

N o d e s

T r a n s m i s s i o n L i n k s


147/213


148/213


149/213


150/213


151/213


152/213

L2-2 152

Functional architecture: Functional modules or blocks Reference points between modules

Physical architecture: Physical blocks Physical interfaces between the blocks

Informational architecture: Information exchange between entities Object oriented

TMN Architecture


153/213


154/213


155/213


156/213


157/213

Information Architecture


158/213

L3-4 158

M a n a g e r A g e n t

O p e r a t i o n s / R e q u e s t s

R e s p o n s e s

N o t i f i c a t i o n s / T r a p s

F i g u r e 1 1 . 1 0 T M N I n f o r m a t i o n A r

Service Architecture

B u s in e s s M a n a g e m e n t


159/213

L3-5 159

S e rv i c e M a n a g e m e n t

N e t w o rk M a n a g e m e n t

E l e m e n t M a n a g e m e n t

M a n a g e d N e t w o rk E le m e n t

q 3

q 3

q 3

q 3

Figure 11.11 TMN S ervice Architecture


160/213


161/213


162/213


163/213

L1-3 163

BERT

Physical layer monitoring tool Generates and detects bits

Bit error rate (BER) is calculated by comparingthe transmitted pattern with received pattern

Loop back is a feature of the modem BER can be measured for a modem or two modems

and the link in between


164/213


165/213


166/213


167/213


168/213


169/213

Host


170/213

L3-1 170

Command: host

Displays host names using DNS

Available from ftp.nikhef.nl:/pub/network/host.tar.Z

% host -a sun4-gw.cc.gatech.edu

Trying null domain

rcode = 0 (Success), ancount=1

The following answer is not authoritative:

sun4-gw.cc.gatech.edu 85851 IN A 130.207.111.100

Example:


171/213


172/213


173/213


174/213


175/213


176/213

tcpdump


177/213

L4-4 177

14:03:36.798269 noc1.btc.gatech.edu.snmp > noc3.btc.gatech.edu.164:Co mm uni ty = pub l icGetResponse(196)Reques t ID = 4

system.sysDescr .0 = "SunO S noc1 5 .5 .1 G ener ic_103640-08 sun4u"system.sysO b jectID.0 = E:hp.2.3.10.1.2system.sysUpT ime.0 = 24739645 3system.sysCon tact.0 = "Brandon R hodes"system.sysNa me .0 = "noc1"system.sysLocat ion.0 = "B T C N M L a b "

system.sysServ ices.0 = 72

Figure 5.17(b) Get-Response M essag e from Ag ent-to-M anag er (After

Example: SNMP message

Network Routing Tools


178/213

L4-5 178

Table 12.7 Route-Monitoring ToolsName Operating System Description

netstat UNIX Displays the contents of various network-

related data structures

arprarp

UNIX, Windows95/x/00NT

Displays and modifies the Internet-to-Ethernetaddress translation tables

traceroute

tracert

UNIX

Windows

Traces route to a destination with routing

delays


179/213

L4-6 179

Network Management Tools

SNMP command tools

MIB Walk

snmpsniff

SNMP Command Tools


180/213

L5-1 180

snmptest

snmpget

snmpgetnext

snmpset

snmptrap

snmpwalk

snmpnetstat

SNMP Command Tools


181/213

L5-2 181

SNMP Command Tools

Test tool is an interactive tool to get values of severalmanaged objects, one at a time.

Get, Get-next and Set are the SNMP commands thatwe learned under SNMP architecture / messages.Execution of these will return an SNMP Responsemessage.

SNMPWalk uses snmpgetnext to trace the entire MIB.

Network status command is used to test the status ofnetwork connections of a host.


182/213

SNMP Set Command


183/213

L5-4 183

SNMP Get Next Command

% snmpgetnext noc5.btc.gatech.edu public

interfaces.ifTable.ifEntry.ifIndex.1

interfaces.ifTable.ifEntry.ifIndex. 2 = INTEGER: 2

Command: snmpset host community


184/213

Protocol Analyzer


185/213

L6-2 185

Analyzes data packets on any transmission line

including LAN Measurements made locally or remotely

Probe (data capture device) captures data andtransfers to the protocol analyzer (no storage)

Data link between probe and protocol analyzer

either dial-up or dedicated link or LAN Protocol analyzer analyzes data at all protocol levels


186/213

RMON Probe


187/213

L6-4 187

Network Associates Sniffer Stand-alone and Networked

HP NetMetrix / HP OpenView

Communication between probe and analyzeris using SNMP

Data gathered and stored for an extended period

of time and analyzed later Used for gathering traffic statistics and used for

configuration management for performance tuning

Network Monitoring with RMON Probe

E t he r ne t


188/213

L6-5 188

T o k e n R i n g

L AN

Protoco l

A n a ly z e r

Rou t e r

Rou t e r

T o k e n R i n g

Probe

E t he r ne t

Probe

E t he r ne t LA N

F DDI LA N

B a c k b o n e

Probe

Rou t e r

FDDI Probe

Figure 12.15 Monitoring of Total Network with Individual RM ON P robes

B a c k b o n e

Ne t wo r k


189/213

L7-1 189

Network Statistics

Protocol Analyzers RMON Probe / Protocol analyzer MRTG (Multi router traffic grouper)

see notes for chapter 8 Home-grown program using tcpdump

Protocol Distribution


190/213

L7-2 190

Figure 12.19 Protocol Distribution (NetMetrix)

NMS Components


191/213

L7-3 191

Ven dor Spec i fi c N MS Serv i c es

C o m m o n S N M P S e r v ic e s

C ore App l i c a t i on Serv i c es

Opera t i ng Sy s t em

H ardw are


192/213


193/213


194/213


195/213


196/213

Web-Base ManagementDisplay on Web browser


197/213

L1-1 197

Economical displays

Ubiquitous access

Reduction in network load for non-polled

configuration

Web Interface vs Web-base management

Web-based management Desktop management interface

Web-based enterprise management Java management extensions


198/213

Web Interface


199/213

L1-3 199

SNMP-based NMS

NMS database transferred to Web-server

View with Web browser

Protocol between NMS and network elements

is SNMP

HTTP between Web server and browsers

Proxy Server

D e s k t o p P C

Similar to Web interface


200/213

L2-1 200

P r o x y S e r v e r

M a n a g e r

A p p l i c a t i o n s

M a n a g e d O b je c tsS N M P / O t h e r

A g e n t

W e b S e rv e r

W e b B ro w s e r

p

F i g u r e 1 4 . 2 P r o x y S e r v e r w i th W e b I n t e r fa c e

S N M P /O t h e r

HTT

P

No NMS monitor

No GUI in manager applications


201/213

Desktop Management InterfaceD e s k t o p - r e s i d e n t

M a n a g e m e n t A p p li c a ti o n


202/213

L2-3 202

D e s k t o p M a n a g e m e n t I n t e rfa c e s o f tw a re (D M I )

M a n a g e m e n t In t e rfa c e A P I

C o m p o n e n t In t e rfa c e A P I

C o m p o n e n t

A g e n ts

M IF

D a t a b a s e

Figure 14.5 DMI Infrastructure


203/213


204/213

DMI MIB

enterpr ises

(1 )

pr ivate

{1 3 6 1 .4}


205/213

L3-3 205

(1 )

dm t f

(412)

d m i M I B

(1 )

dmt fS tdMi f s

(2 )

dm t f Dy nO ids

(3 )

d m i C o n f o r m a n c e

(3 )

dmiNot i f ica t ion

(2 )

dm iO b jec t s

(1 )

Figure 14.7 DMI MIB

MIF specified using ASN.1 syntax Can be managed by an SNMP manager DMTF task expanded to specify WBEM -

Web-based enterprise management


206/213

Web-Based Enterprise Management


207/213

L4-2 207

WBEM based on Common Information Module,developed by Microsoft

CIM is information-modeling framework intended

to accommodate all protocols and frameworks

Object-oriented

Five components: Web client CIM object manager (CIMOM) CIM schema

Management protocol Managed objects with specific protocol

WBEM

Web client is Web browser with management

applications: Application requests use CIM schema


208/213

L4-3 208

Multiple instances of Web clients feasible

CIM object manger mediates between Web clients,

managed objects, and CIM schema

Microsoft Windows Management Instrumentationuses Distributed Component Object Model (DCOM)

Suns CIMOM uses JMX

CIM modules: Core model: high level framework Common models: protocol-specific domains Extension model: technology specific


209/213

Solid lines indicate inheritances

Common Information Module


210/213

L5-2 210

Dashed lines indicate associations

PhysicalElement (e.g. interface card) and

LogicalElement (IP address) subclasses of

ManagedSystemElement

System is aggregate of managed system elements

Service access point is management, measurement,

and configuration of a service

Managed system element considered as groups of

components


211/213


212/213

Looking Ahead Future network and system management

frameworks should accommodate well-established

SNMP entities


213/213

Web agents are intelligent and future points to

the use of Web technology

Web-based management offers two options

WBEM is comprehensive and centralized approachto enterprise management; accommodates both

scalar and object-oriented schemes

JMX is decentralized and uses Java technology;

nms total slides

Documents