You are on page 1of 40

Broadband Network Management: ATM Networks

Network Management: Principles and Practice Mani Subramanian 2000

9-1

Chapter 9

Broadband Services
Broadband Integrated Services Digital Network (BISDN) Voice, video, and data services Transport protocol and medium (Basic) Integrated Services Digital Network (ISDN) 2B + D WAN ATM Cell-based Technology SONET / OC-n (n x 51.84 Mbps) SDH / STS LAN ATM LAN Emulation Access Technology Cable modem / HFC DSL Wireless

Notes

Network Management: Principles and Practice Mani Subramanian 2000

9-2

Chapter 9

Broadband Services Network


Residential Customer Network Broadband Access Broadband Access Residential Customer Network

Service Providers

Gateway

SDH / SONET WAN

Campus ATM / LAN Network

OC-n / STS-n Link

OC-n / STS-n Link

Campus ATM / LAN Network

Figure 9.1 Broadband Services Network

Notes
SDH / SONET is WAN Access to corporate and residence / SOHO OC-n used to access institutions HFC and DSL used for residence Wireless technology in early stage
OC-n: Optical Carrier Link SONET STS-n: Electrical carrier Link SONET HFC: Hybrid Fiber Coaxial Network Management: Principles and Practice Mani Subramanian 2000

9-3

Chapter 9

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

Notes
Packets in a session take the same path in VP/VC After initial set up, latency is reduced SDH/ SONET in WAN uses 155.52 Mbps as basic data rate and is universal (in contrast to T1 and E1) Transmission medium primarily optical fiber ATM used in LAN for high speed emulating Ethernet LAN

Network Management: Principles and Practice Mani Subramanian 2000

9-4

Chapter 9

ATM LAN Emulation (LANE)


Difference between ATM and Ethernet ATM is connection-oriented ATM makes one-to-one connection ATM 20-byte addressing scheme different from 6-byte Ethernet MAC address LANE emulates services of a traditional LAN

Notes

Network Management: Principles and Practice Mani Subramanian 2000

9-5

pter 9

LANE Protocol Architecture


Net rk L er

Net

rk L

er

ic l Li k L

er

ic l Li k L

er

L N T

l ti t ti

L L

er

LUNI

L N

l ti

er

er

t ti


er

    

sic l L

i ure .3 L
 

er

sic l L

er

Net

rk

ere Architecture of LAN E ul tio


!  

"

Notes
L N emul ti l er i serted bet een LLC nd L LLC nd b ve represent t pic l TC /I Internet envir nment AT F rum specific ti ns ddress LANE User-Net rk interf ce (LUNI) AT rkst ti n c lled LAN emul ti n client (LEC)

Net rk nagement: rinciples and ractice ani Subramanian 2000

9-6

Chapter 9

LUNI Interface
LE Service LE Configuration server LEC LUNI LE Server Broadcast and nknown Server LEC LUNI

Figure 9.4 LUNI Interface

Notes
LAN emulation services: LE configuration server (LECS) assigns LECs to emulated LANs LE server (LES) performs control and coordination functions for ELANs - registration, address resolution, route descriptors, etc. Broadcast and unknown server (BUS) handles broadcast and multicast packets, and unknown address resolution
9-7

Network Management: Principles and Practice Mani Subramanian 2000

Chapter 9

LUNI Functions
Initialization Obtaining ATM addresses of LESs LEC joining a LANE Ability to handle address resolution requests Registration LES appraised of LEC-to-MAC address LES appraised of source-routing parameters for source-routing bridge Address resolution LEC-MAC address resolution Transport Data encapsulated with ATM frame AAL-5 at LE source and decapsulated at destination

Notes

Network Management: Principles and Practice Mani Subramanian 2000

9-8

Chapter 9

ATM LAN Emulation


Data connection Control connection Interface LEC LECS LES BUS LUNI LAN Emulation Client LAN Emulation Configuration Server LAN Emulation Server Broadcast and Unknown Server LAN User Network Interface

LECS Ethernet Bridge LEC LES


Unicast Pkt

BUS
Multicast / Broadcast Pkt

ATM Workstation LEC LUNI Interface Figure 9.5 LAN Emulation Client Connections across LUNI

Notes
ATM workstation communicates with Ethernet workstation using LE services ATM workstation behaves as an LE client and interfaces via LUNI Ethernet workstation interfaces via a bridge acting as LEC LECS, LES, and BUS could be stand-alone devices or part of ATM switch Control connections established before data transfer
Network Management: Principles and Practice Mani Subramanian 2000

9-9

Chapter 9

LANE Protocol Architecture


Bridge LEC Net rk Layer L gical Link Layer LAN Emulati n Layer
$ $ # $

L gical Link Layer LAN Emulati n Layer AT


% & $

Net AC
%

rk Layer

Adaptati n Layer
$

AT
%

Adaptati n Layer
$

L gical Link Layer


$

AT ysical Layer
%

AT Physical Layer
% %

AC Physical Layer Physical Layer

Notes

'

AT
%

ELAN

Ethernet LAN

i ure .6 Protocol Architecture of A


0 )

ELAN

ith Ether et LAN


4

Net rk anagement: Principles and Practice ani Subramanian 2000

9-10

Chapter 9

ATM Campus Network


Router

Router

... ...
Hub Hub

FDDI Backbone Network Router Router

ATM Switch

Router

Router Figure 9.7 ATM Switch as Bridge in Campus Network

Notes
Collapsed backbone design comprises backbone built inside a router with ATM switch acting as bridge to other nodes. FDDI backbone shown above uses external ATM switch as bridge between the router and other nodes; LE services are built in the switch

Network Management: Principles and Practice Mani Subramanian 2000

9-11

Chapter 9

ATM VLAN Configuration


LAN Emulation Configuration Ser er

VLAN Workstation

VLAN Workstation

VLAN Workstation

AT

Back ne ELAN

VLAN Workstation

VLAN Workstation igur

VLAN Workstation .8 ATM VLAN Configuration

Not s
LECS configured to form VLAN groups Each AT switch has an interface to AT ELAN The ELAN ack one and all LANs on it are on VLAN environment

Network anagement: Principles and Practice ani Subramanian 2000

9-12

Chapter 9

ATM WAN Reference Model


Private ATM Network
ATM Switch ATM Switch

Public ATM Network Public UNI


ATM Switch ATM Switch

Private UNI ATM User ATM User

Public UNI ATM User ATM User

UNI ... User Network Interface

re .

ri

te nd

lic ATM Net or

ser Net or Interf ces

Notes
WAN service provided by public service providers Private networks use public WAN facilities Management functions (OAM&P) Operations Administration Maintenance Provisioning Public and private User Network Interface (UNI) define user interfaces
9-13

Network Management: Principles and Practice Mani Subramanian 2000

Chapter 9

ATM WAN Management


Private Network Manager (NMS) M1 M2 M4 M4 M3 Public Network Manager (NMS) M5 Public Network Manager (NMS)

End User

Private UNI

Private ATM Network

Public UNI

Public ATM Network

BICI

Public ATM Network

BICI Broadband inter-carrier interface


Figure 9.10 ATM Forum Management Interface Reference Architecture

Notes
Management interface architecture defined by ATM Forum Public and private NMS responsible to manage respective domains OSI has defined five management interfaces: M1 Interface between private NMS and end user M2 Interface between private NMS and network M3 Interface between private NMS and public NMS M4 Interface between public NMS and network M5 Interface between public NMSs
Network Management: Principles and Practice Mani Subramanian 2000

9-14

Chapter 9

Integrated Local Management Interface (ILMI)


ATM End System IME (User) ATM End System IME (User) Private Network ATM Switch IME (User) ATM End System IME (User) Private Network ATM Switch IME (Sym) ATM End System IME (User)
Private NNI ILMI Private UNI Public UNI ILMI Public UNI

Public Network ATM Switch IME (Net)

Public VPC Cross-connect


ILMI

IME (Net)

Public UNI

ILMI

IME (Net) Private Network ATM Switch

Private UNI ILMI

Public UNI

Public NNI

IME (Net)

IME (Usr))

ILMI Private NNI

IME (Net)

IME (Net)

IME (Sym))

IME (Sym))

Private PVC Cross-Connect


ILMI

ILMI

IME (Net)

Private Network ATM Switch IME (Sym))

Private Network ATM Switch IME (Sym)

Private NNI

ILMI

IME (Sym)) Physical Link Virtual Path Connections

IME (Usr))

ig re .
6 7

Definitions and ontext of ILMI


9

Notes
ATM Forum defines additional interface (ILMI) UNI User network interface NNI Network-Network interface
Network Management: Principles and Practice Mani Subramanian 2000

9-15

Chapter 9

ATM MIB
Internet {1 3 6 1}

mgmt (2) mib-2 (1)

private (4)

system (1)

interfaces (2)

transmission (10)

ifMIB (31)

atmMIB (37)

enterprises (1)

ifMIBObjects (1)

atmMIBObjects (1)

atmForum (353)

atmForumAdmin (1) atmForumUni (2)

atmForumNetworkManagement (5) atmfLanEmulation (4)

atmUniDxi (3)

Notes
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 remote monitoring (covered in Chapter 8)
Network Management: Principles and Practice Mani Subramanian 2000

9-16

Chapter

SNMP ATM Management


NMS

SNMP M1 SNMP Agent ATM evice


RFC RFC RFC
@ @ @ E F C C D B A @ B

ig re . 3 SNMP ATM Management (M Interfa e)

Notes
ATM Management specifications available for both SNMP and OSI management implementations SNMP agent built in ATM device System, Interfaces, Interface types, transmission carrier groups (T1, T , SONET), and ATM object groups are monitored

Network Management: Principles and Practice Mani Subramanian 000

-17

Chapter 9

SNMP and ILMI


NMS M2 SNMP Interface

SNMP Agent ATM Device B Agent Mgmt Entity


ATM Interface
ILMI

Proxy ATM Device A

RFC 1213 RFC 1573 RFC 1695 Transport MIB

ILMI MIB

Agent Mgmt Entity

ILMI MIB

Private ATM Network

Figure 9.14 Role of SNMP and ILMI in ATM Management (M2 Interface)

Notes
ILMI MIB used to gather data between ATM devices Proxy agents convert ILMI objects to SNMP objects

Network Management: Principles and Practice Mani Subramanian 2000

9-18

Chapter 9

M1 Interface Management
mib(mgmt 1) interfaces ( ) ifMIB ( 1) ifMIB b ects (1)

ifNumber (1)

ifTable ( )

ifXTable (1) ifStackTable ( )

ifRecvAddressTable ( ) ifTestTable ( )

ig re .1 Interfaces Gro

a les for

la ers

Notes
M1 management interface is across an ATM device Additional MIBs created using ifMIB group to handle sublayers
a le .4 Interfaces Gro Entity ifXTable ifStackTable ifTestTable ifRecvAddressTable ID ifMIB b ects 1 ifMIB b ects ifMIB b ects ifMIB b ects a les for la ers Description (brief) Additional ob ects for the interface table Information on relationship between sublayers Tests that NMS instructs agent to perform Information on type of packets / frames accepted on an interface

Network Management: Principles and Practice Mani Subramanian 000

9-19

Chapter 9

ATM Transmission
transmission (10)

roups

ds1 (18)

ds3 (30)

sonet (39)

Figure 9.1 Transmission

roups for ATM

Notes
Three transmission modes used for ATM in US DS1 1.544 Mbps T1 carrier DS3 44.736 Mbps T3 carrier SONET n 155.52 Optical fiber

Network Management: Principles and Practice Mani Subramanian 2000

9-20

Chapter

ATM Managed Objects


atmMIBObjects (1)

roup

atmNoTraffic escriptor (1) atmInterfaceConfTable (2) atmInterfaceDs PlcpEntry ( ) atmInterfaceTCTable ( ) atmTrafficDescrParamTable ( ) atmVplTable ( )

aal VccTable (12) atmVcCrossconnectTable (11) atVcCrossConnectIndexNext (10) atmvpCrossConnectTable ( ) atmVpCrossConnectIndexNext ( ) atmVclTable (7)

igure .

ATM Managed Objects

roup

Entity atmNoTrafficDescriptor atmInterfaceConfTable

OID atmMIBObjects 1 atmMIBObjects 2

atmInterfaceDs PlcpEntry

atmMIBObjects

atmInterfaceTCTable

atmMIBObjects

atmTrafficDescrParamTable atmVplTable atmVclTable atmVpCrossConnectNext atmVpCrossConnectTable atmVcCrossConnectNext atmVcCrossConnectTable aal VccTable

atmMIBObjects atmMIBObjects atmMIBObjects 7 atmMIBObjects atmMIBObjects atmMIBObjects 10 atmMIBObjects 11 atmMIBObjects 12

Description (brief) ATM traffic descriptor type ATM local interface configuration parameter table ATM interface DS3 PLCP parameters and state variables table ATM TC sublayer configuration and state parameters table ATM traffic descriptor type and associated parameters Virtual path link table Virtual channel link table Index for virtual path crossconnect table Virtual path cross-connect table Index for virtual channel cross-connect table Virtual cross-connect table AAL VCC performance parameters table

Network Management: Principles and Practice Mani Subramanian 2000

9-21

Chapter 9

M2 Interface Management
atmForum (353)

atmForumAdmin (1) atmForumUni (2)

atmForumNetworkManagement (5) atmfLanEmulation (4)

atmUniDxi (3)

Notes
M2 interface used to manage private networks ATM link management data gathered using ILMI MIB ILMI addresses: Administrative information (atmForumAdmin) - registry to locate ATM network services such as LECS and ANS UNI D I (Data Exchange Interface) LAN Emulation NNI
Network Management: Principles and Practice Mani Subramanian 2000

9-22

Chapter 9

ATM UNI
atmForum {enterprises 353} atmForumUNI (2)

roup

atmfAddressRegistrationAdminGroup (11) atmfPhysicalGroup (1) atmfAtmLayerGroup (2) atmfAtmStatsGroup (3) atmfVpcGroup ( ) atmfVccGroup (5)
H

atmfVccAbrGroup (10) atmfVpcAbrGroup (9) atmfSrvcRegistryGroup ( )


G

atmfNetPrefixGroup (7) atmfAddressGroup ( )


Y

i ur
P

. 8 ATM UNI MI
S

roup

E n tity a tm fP h ysica lG ro u p

a tm fA tm L a ye rG ro u p

a tm fA tm S ta tsG ro u p a tm fV p cG ro u p

a tm fV ccG ro u p

a tm fA d d re ssG ro u p

a tm fN e tP re fixG ro u p a tm fS rvcR e g istrryG ro u p

a tm fV p cA b rG ro u p

a tm fV ccA b rG ro u p

A tm fA d d re ssR e g istra tio n A d m in G ro u p

Net ork Management: Principles and Practice Mani Subramanian 2000

O ID a tm F o ru m U n i 1

a tm F o ru m U n i 2

a tm F o ru m U n i 3 a tm F o ru m U n i
`

a tm F o ru m U n i 5

a tm F o ru m U n i

a tm F o ru m U n i 7 a tm F o ru m U n i
c

a tm F o ru m U n i 9

a tm F o ru m U n i 1 0

a tm F o ru m U n i 1 1

D e scrip tio n (b rie f) D e fin e s a ta b le o f p h ysica l la ye r sta tu s a n d p a ra m e te r in fo rm a tio n D e fin e s a ta b le o f A T M la ye r sta tu s a n d p a ra m e te r in fo rm a tio n D e p re ca te d D e fin e s a ta b le o f sta tu s a n d p a ra m e te r in fo rm a tio n o n th e virtu a l p a th co n n e ctio n s D e fin e s a ta b le o f sta tu s a n d p a ra m e te r in fo rm a tio n o n th e virtu a l ch a n n e l co n n e ctio n s D e fin e s th e n e t o rk-sid e IM E ta b le co n ta in in g th e u se r-sid e A T M -la ye r a d d re sse s D e fin e s a u se r-sid e IM E ta b le o f n e t o rk p re fixe s D e fin e s th e n e t o rk-sid e IM E ta b le co n ta in in g a ll se rvice s a va ila b le to th e u se r-sid e IM E D e fin e s a ta b le o f o p e ra tio n a l p a ra m e te rs re la te d to A B R virtu a l p a th co n n e ctio n s D e fin e s a ta b le o f o p e ra tio n a l p a ra m e te rs re la te d to A B R virtu a l ch a n n e l co n n e ctio n s
b b b

9-23

Chapter 9

M Interface
Services offered by public NMS to customer on PVCs Two classes Class I: Status and configuration management Class II: Virtual configuration control Class I: Functions offered by public NMS to customer monitoring and management of configuration, fault, and performance Class II: User ability to add, delete, and change VC between customer UNIs Class I mandatory and Class II optional

Notes
Class I examples Retrieving performance and configuration for UNI link Public NMS reporting of a UNI link failure Class II examples Establishing a new VP Increase the number of VCs in a VP
9-24

Network Management: Principles and Practice Mani Subramanian 2000

Chapter 9

Customer Network Management (CNM)


Carrier Management System I Status Configuration Monitoring II Virtual Configuration Control

M3 Link Customer X Network Management System M2 Link Private ATM Network Customer X Site 1 ATM Device Customer X Site 2 Public UNI Public UNI

M4 link

Public ATM Network

Public UNI Private ATM Network

Public UNI Private ATM Network Customer X Site 4

Customer X Site 3

igure .

Customer Management of ri ate an

u li Networks

Notes
CNM manages both private and public networks CNM agent in public network provides M3 service CNM manages its own ATM networks at sites 1, 3, and 4.
Network Management: Principles and Practice Mani Subramanian 2000

9-25

Chapter 9

M Class I Management
G e n e ra l U N I P ro to c o l S ta c k in fo rm a tio n A T M P e rfo rm a n c e in fo rm a tio n o n c u s to m e r's UNI P h y s ic a l-la y e r p e rfo rm a n c e a n d s ta tu s in fo rm a tio n s y s te m g ro u p (R F C 1 2 1 3 ), in te rfa c e s g ro u p , in c lu d in g ifT a b le a n d ifS ta c k T a b le (R F C 1 2 1 3 , R F C 1 5 7 3 ), S N M P g ro u p (R F C 1 2 1 3 ) ifT a b le (R F C 1 5 7 3 )

A T M -L e v e l in fo rm a tio n c o n fig u ra tio n in fo rm a tio n P h y s ic a l-la y e r c o n fig u ra tio n in fo rm a tio n

a ll ta b le s e xc e p t d s x3 C o n fig T a b le (R F C 1 4 0 7 ), a ll ta b le s e xc e p t d s x1 C o n fig T a b le (R F C 1 4 0 6 ), a ll ta b le s e xc e p t th e c o n fig u ra tio n ta b le s a n d V T ta b le s o f S O N E T M IB (R F C 1 5 9 5 ), a tm In te rfa c e D s 3 P lc p T a b le / a tm In te rfa c e T C T a b le o f A T M M IB (R F C 1 6 9 5 ) a tm In te rfa c e C o n fT a b le o f A T M M IB (R F C 1 6 9 5 ) d s x3 C o n fig T a b le (R F C 1 4 0 7 ) d s x1 C o n fig T a b le (R F C 1 4 0 6 ) a ll c o n fig u ra tio n ta b le s e xc e p t th e s o n e tV tC o n fig T a b le o f S O N E T M IB (R F C 1 5 9 5 ) a tm V p lT a b le o f A T M M IB (R F C 1 6 9 5 )

A T M -la y e r v irtu a l p a th lin k c o n fig u ra tio n a n d s ta tu s in fo rm a tio n A T M -la y e r v irtu a l c h a n n e l lin k c o n fig u ra tio n a n d s ta tu s in fo rm a tio n A T M -la y e r v irtu a l p a th c o n n e c tio n c o n fig u ra tio n a n d s ta tu s in fo rm a tio n A T M la y e r v irtu a l c h a n n e l c o n n e c tio n c o n fig u ra tio n a n d s ta tu s in fo rm a tio n A T M -la y e r tra ffic c h a ra c te riz a tio n (tra ffic d e s c rip to rs fo r c u s to m e r's U N Is ) in fo rm a tio n E v e n t n o tific a tio n s o n A T M lin k g o in g u p o r d o w n

a tm V c lT a b le o f A T M M IB (R F C 1 6 9 5 )

a tm V p C ro s s C o n n e c tT a b le a n d a tm V p C ro s s C o n n e c tIn d e xN e xt o f A T M M IB (R F C 1 6 9 5 ) a tm V c C ro s s C o n n e c tT a b le a n d a tm V c C ro s s C o n n e c tIn d e xN e xt o f A T M M IB (R F C 1695) a tm T ra ffic D e s c rP a ra m T a b le o f A T M M IB (R F C 1695)

w a rm S ta rt, c o ld S ta rt, lin k U p , lin k D o w n o f S N M P g ro u p (R F C 1 6 9 5 )

Notes
Class I requirements used by customer NMS from carrier NMS The MIB access is read-only
Network Management: Principles and Practice Mani Subramanian 2000

9-26

Chapter 9

M Class II Management
ATM level information configuration information Virtual path link configuration and status configuration information Virtual channel link configuration and status information Virtual path connection configuration and status information Virtual channel connection configuration and status information Traffic descriptors and information objects for virtual path and channel connections atmInterfaceConfTable in ATM MIB (RFC 1695) atmVplTable in ATM MIB (RFC 1695) atmVclTable in ATM MIB (RFC 1695) atmVpCrossConnectTable and atmVpCrossConnectIndexNext of ATM MIB (RFC 1695) atmVcCrossConnectTable and atmVcCrossConnectIndexNext of ATM MIB (RFC 1695) atmTrafficDescrParamTable in ATM MIB (RFC 1695)

Notes
Management information falls into three subgroups ATM-level subgroup: configuration modification VPC/VCC-level subgroup: configuration modification and status information of VP/VC link and connection Traffic subgroup: modification of traffic descriptors and information for VP/VC connections

Network Management: Principles and Practice Mani Subramanian 2000

9-27

Chapter 9

ATM Relationship to TMN


Business Management Layer

Service Management Layer

ATM Management Network Management Layer NML/EML reference point Element Management Layer EML/EL reference point Element Layer

Figure 9.20 ATM Relationship to TMN Layered Architecture

Notes
ITU-T definition of five-layer model to manage telecommunications network ATM heavily used in WAN, responsibility of public service providers The bottom three layers apply to ATM management Reference points are abstract interfaces between layers
Network Management: Principles and Practice Mani Subramanian 2000

9-28

Chapter 9

M4 Interface
Managing System Environment M4 Interface and / or

Managed System Environment

ATM Net ork View

ATM NE View i re . D al ie s of t e M4 Interface

Notes
M4 interface defines dual views Network element view Network view Two NMSs interface at network view level Each NMS interfaces with network elements using network element view
Network Management: Principles and Practice Mani Subramanian 2000

9-29

Chapter 9

Network Element View


NMS Environment M4 Interface (ATM NE View Only) ATM NE ATM NE ATM NE ATM NE ATM NE

Figure 9.22 NE-View Management Architecture

Notes
Network element view architecture proposed by ATM Forum Multiple agent layers - SNMP and ILMI agents implied in the representation

Network Management: Principles and Practice Mani Subramanian 2000

9-30

Chapter 9

Network View
NMS Environment
M4 Interface (ATM Network View Only)

SubNMS

SubNMS

M4 Interface (ATM NE View Only)

ATM NE

ATM NE
Multi-Supplier Subnetwork

ATM NE

ATM NE

ATM NE
Single-Supplier Subnetwork

ATM NE

re . 3 x

le of Network-View

e e t

si

l o fi

r tio

Notes
Three-tier architecture Each subNMS manages its respective domains SubNMS communicates with MoM at network view level

Network Management: Principles and Practice Mani Subramanian 2000

9-31

Chapter 9

Combined NE and Network Views


NMS Environment
M4 Interface (ATM NE View Only) M4 Interface (ATM Network View Only) M4 Interface (ATM NE View Only)

SubNMS

SubNMS

M4 Interface (ATM NE View Only)

ATM NE

ATM NE
Multi-Supplier Subnetwork

ATM NE

ATM NE

ATM NE
Single-Supplier Subnetwork

ATM NE

Figure 9.24 E ample of NE + Network-View Management Physical Configuration

Notes
An NMS could function at both levels simultaneously Local elements can be managed using NE view and remote elements using network view with subNMS

Network Management: Principles and Practice Mani Subramanian 2000

9-32

Chapter 9

M4 NE View Requirements: Configuration Management


1. ATM NE configuration identification and change reporting, which involves: (a) Operations performed over the craft interface (b) Human intervention (removal/insertion of equipment modules) (c) Customer control channels (e.g., ILMI) (d) Network failures (e) Protection switching events (f) Sub-ATM NE component initialization (g) Secondary effects of atomic operations performed by the management system 2. Configuration of UNIs, BICIs, and BISSIs 3. Configuration of VPL/VCL termination points and cross-connections 4. Configuration of VPC and VCC OAM segment end-points 5. Event flow control - event forwarding discriminator function

Notes

Network Management: Principles and Practice Mani Subramanian 2000

9-33

Chapter 9

M4 NE View Requirements: Fault Management


1. Notifying the network management system of a detected failure 2. Logging failure reports 3. Isolating faults via demand testing The specific functions are: Failure reporting of the various alarms. OAM (Operations, Administration and Maintenance) cell loopback testing

Notes

Network Management: Principles and Practice Mani Subramanian 2000

9-34

Chapter 9

M4 NE View Requirements: Performance Management


The functions of performance monitoring for an ATM network are: 1. Performance monitoring 2. Traffic management 3. UPC (User Parameter Control) / NPC (Network Parameter Control) disagreement monitoring 4. Performance management control 5. Network data collection To accomplish these general functions, the following specific functions are specified: 1. Physical layer performance monitoring 2. ATM cell level protocol monitoring 3. UPC/NPC disagreement monitoring

Notes

Network Management: Principles and Practice Mani Subramanian 2000

9-35

Chapter 9

M4 Network View Requirements


1. Transport network configuration provisioning (including subnetwork provisioning, and link provisioning) 2. Transport network connection management (including set-up/ reservation/ modification for subnetwork connection, link connection, trails and segments) 3. Network fault management (including congestion monitoring, and connection and segment monitoring) 4. Network security management

Notes

Network Management: Principles and Practice Mani Subramanian 2000

9-36

Chapter 9

M4 Network View Requirements: Security Management


Table 9.10 Mapping of Threats and Objectives Threat Masquerade Eavesdropping Unauthorized access Loss or corruption of information Repudiation Forgery Denial of Service Confidentiality x x x Data Integrity x x x Accountability x x x Availability x x -

x -

x x -

Table 9.11 Mapping of Security Requirements and Services Functional Security Requirements Verification of Identities Security Services User authentication Peer entity authentication Data origin authentication Access control Access control -----------------------------------------Confidentiality Access control -----------------------------------------Integrity Non-repudiation Security alarm, audit trail and recovery Security alarm, audit trail and recovery Security alarm, audit trail and recovery -

Controlled access and authorization Protection of confidentiality Stored data ----------------------Transferred data Protection of data integrity Stored data ----------------------Transferred data Strong Accountability Activity logging Alarm reporting Audit Security recovery / Management of Security

Network Management: Principles and Practice Mani Subramanian 2000

9-37

Chapter 9

Management of LANE
atmForum {enterprises 353} atmfLanEmulation (4)

elanMIB (2)

lesMIB (3)

busMIB (4)

elanAdminGroup (1) elanConfGroup (2)

elanLecsGroup (3)

busConfGroup (1) busStatGroup (2)

busFaultGroup (3)

lesConfGroup (1) lesStatGroup (2)

lesFaultGroup (4) lesLecStatGroup (3)

ig re .
e f

A M LAN Em lation MI
i e

g h

Notes
ATM LAN managed by SNMP MIBs defined by IETF
LES, LECS, BUS, and LEC are managed by ATM Forum MIB ELAN MIB deals with information for a LEC to join an ELAN LES MIB used to create, configure, and monitor LESs BUS MIB used to create, destroy, configure, and determine BUS status; also ELAN topology

Network Management: Principles and Practice Mani Subramanian 2000

9-38

Chapter 9

LAN Emulation
Table 9.12 LAN Emulation Module Entity elanMIB elanAdminGroup elanConfGroup elanLecsGroup lesMIB lesConfGroup lesStatGroup OI atmfLanEmulation 2 elanMIB 1 elanMIB 2 elanMIB 3 atmfLanEmulation 3 lesMIB 1 lesMIB 2 escription (brief) Information required for LEC to join ELAN Registry for LEC assignment policy types Construct and destroy ELAN configuration Configure and monitor LECs Information to create and configure LES LES configuration and topology information Used to measure performance and fault statistics Information on LE-ARP and error statistics on LEC-LES pairs Information on faults Information on BUS Information on BUS configuration Information on BUS and BUS-LEC statistics Maintains BUS error statistics

lesLecStatGroup

lesMIB 3

lesFaultGroup busMIB busConfGroup busStatGroup busFaultGroup

lesMIB 4 atmfLanEmulation 4 busMIB 1 busMIB 2 busMIB 3

Notes
ELAN created by creating a new ELAN using elanMIB creating a LES entry for that ELAN using lesMIB creating a BUS entry for that ELAN using busMIB
Network Management: Principles and Practice Mani Subramanian 2000

9-39

Chapter 9

ATM
DTE

XI Management
ATM D I DCE ATM UNI ATM Switch

Figure 9.2 ATM XI Interface

ILMI ATM D I D I ILMI ATM UNI

DTE
SNMP

DCE

ATM Switch

NMS

Figure 9.2 ATM XI ocal Management Interface

Notes
Digital Exchange Interface defined between DTE (digital terminating equipment) and DCE (digital circuit equipment) Example of DTE is hub and DCE is DSU (digital service unit); ATM switch is part of public network Management of D I and ATM UNI done using ILMI specifications NMS manager uses SNMP with proxy agent for ILMI management objects
Network Management: Principles and Practice Mani Subramanian 2000

9-40

You might also like