Nms Atm Network

Broadband Network Management:

ATM Networks

Network Management: Principles and Practice© Mani Subramanian 2000

9-1

Notes

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

Chapter 9


9-2

Notes

Broadband Services Network

SDH / SONETWAN

CampusATM / LAN

Network

CampusATM / LAN

Network

ResidentialCustomerNetwork

ResidentialCustomerNetwork

OC-n /STS-n

Link

OC-n /STS-n

Link

Figure 9.1 Broadband Services Network

ServiceProviders

Gateway

BroadbandAccess

BroadbandAccess

• 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

Chapter 9


9-3

OC-n: Optical Carrier Link SONET STS-n: Electrical carrier Link SONETHFC: Hybrid Fiber Coaxial

Notes

ATM Technology• ATM technology based on:

• VP / VC• Fixed packet size or cell• Small packet size (53 bytes)• Statistical multiplexing• Integrated services

• 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

Chapter 9


9-4

Notes

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

Chapter 9


9-5

Notes

LANE Protocol ArchitectureNetwork Layer

Logical Link Layer

LAN Emulation Layer

ATM Adaptation Layer

ATM

Physical Layer

ATM Network

Figure 9.3 Layered Architecture of LAN Emulation

LUNI

Network Layer

Logical Link Layer

LAN Emulation Layer


ATM

Physical Layer

• LAN emulation layer inserted between LLC and AAL• LLC and above represent typical TCP/IP Internet environment• ATM Forum specifications address LANE User-Network interface (LUNI)• ATM workstation called LAN emulation client (LEC)

Chapter 9


9-6

Notes

LUNI Interface

LEC LEC

LE Service

LE Configuration server

LE Server

Broadcast and UnknownServer

Figure 9.4 LUNI Interface

LUNI LUNI

• 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

Chapter 9


9-7

Notes

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

Chapter 9


9-8

ATM LAN Emulation

Eth

erne

t

BridgeLEC

LES

LECS

BUS

ATM WorkstationLEC

Unicast Pkt

Multicast / Broadcast Pkt

LUNI Interface

LEC LAN Emulation ClientLECS LAN Emulation Configuration ServerLES LAN Emulation ServerBUS Broadcast and Unknown ServerLUNI LAN User Network Interface

Figure 9.5 LAN Emulation Client Connections across LUNI

Data connection

Control connection

Interface

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

Chapter 9


9-9

LANE Protocol Architecture

Network Layer

Logical Link Layer

LAN Emulation Layer


ATM

Physical Layer

Network Layer

Logical Link Layer

MAC

Physical Layer

LAN EmulationLayer

ATM AdaptationLayer

ATM

Physical Layer

MAC

Physical Layer

Logical Link Layer

ATM ELAN Ethernet LAN

Figure 9.6 Protocol Architecture of ATM ELAN with Ethernet LAN

Bridge LEC

Notes

Chapter 9


9-10

ATM Campus Network

FDDI BackboneNetwork

Router

ATM Switch

Router

Router

Hub

Hub

Figure 9.7 ATM Switch as Bridge in Campus Network

...

...

Router

Router

Router

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

Chapter 9


9-11

ATM VLAN Configuration

ATM BackboneELAN

VLAN

Workstation

VLAN

Workstation

VLAN

Workstation

VLAN

Workstation

VLAN

Workstation

VLAN

Workstation

Figure 9.8 ATM VLAN Configuration

LAN EmulationConfiguration

Server

Notes• LECS configured to form VLAN groups• Each ATM switch has an interface to ATM ELAN• The ELAN backbone and all LANs on it are on VLAN environment

Chapter 9


9-12

Notes

ATM WAN Reference Model

• 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

Private ATM Network

ATMUser

ATMUser

ATMUser

ATMUser

PublicUNI

PublicUNI

PrivateUNI

Figure 9.9 Private and Public ATM Network User Network Interfaces

UNI ... User Network Interface

ATMSwitch

ATMSwitch

Public ATM Network

ATMSwitch

ATMSwitch

Chapter 9


9-13

Notes

ATM WAN Management

Figure 9.10 ATM Forum Management Interface Reference Architecture

PrivateNetworkManager

(NMS)

PrivateATM

Network

EndUser

M2

PublicNetworkManager

(NMS)

PublicATM

Network

M4

PublicNetworkManager

(NMS)

PublicATM

Network

M4

M5M3

M1

BICIPublic

UNIPrivate

UNI

• 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

BICI Broadband inter-carrier interface

Chapter 9


9-14

Notes

Integrated Local Management Interface (ILMI)

• ATM Forum defines additional interface (ILMI)• UNI User network interface• NNI Network-Network interface

Private NetworkATM Switch


Private PVCCross-Connect

IME(Sym)

Public NetworkATM Switch

ATMEnd System

IME(User)


IME(Sym)

ATMEnd System

IME(User)


IME(User)

ATMEnd System

IME(User)

ATMEnd System

IME(User)

Public VPCCross-connect

IME(Net)

IME(Net)

IME(Net)

IME(Net)

IME(Net)


IME(Sym))

IME(Usr))

IME(Sym))

IME(Usr))

PrivateUNI

IME(Net)

IME(Sym))

IME(Net)

IME(Sym))ILMI

ILMI

PublicNNI

PublicUNI

PrivateNNI

PrivateNNI

PrivateUNI

ILMI

ILMI

ILMI

ILMI

ILMI

PublicUNI

PublicUNI

PublicUNI

ILMI

ILMI

Physical Link

Virtual Path Connections

Figure 9.11 Definitions and Context of ILMI

PrivateNNI

Chapter 9


9-15

Notes

ATM MIB

atmForumNetworkManagement (5)

atmfLanEmulation (4)

mgmt(2)

private(4)

Internet{1 3 6 1}

atmForumAdmin (1)

atmForumUni (2)

atmUniDxi (3)

mib-2(1)

interfaces(2)

ifMIB(31)

enterprises(1)

atmForum(353)

transmission(10)

atmMIB(37)

atmMIBObjects(1)

system(1)

ifMIBObjects(1)

• 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)

Chapter 9


9-16

Notes

SNMP ATM Management

NMS

ATM Device

SNMP

RFC 1213RFC 1573RFC 1695

Figure 9.13 SNMP ATM Management (M1 Interface)

SNMP Agent

M1

• 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, T3, SONET), and ATM object groups are monitored

Chapter 9


9-17

SNMP and ILMI

NMS

ATM Device A

SNMPInterface

RFC 1213RFC 1573RFC 1695

Transport MIB

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

SNMP Agent

Proxy

AgentMgmt Entity ILMI

MIB

ATM Device B

AgentMgmt Entity

ILMIMIB

ATMInterface

ILMI

Private ATM Network

M2

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

Chapter 9


9-18

Notes

M1 Interface Management

• M1 management interface is across an ATM device• Additional MIBs created using ifMIB group to handle sublayers

ifMIB( 31)

ifMIBObjects(1)

ifRecvAddressTable (4)ifXTable (1)

Figure 9.15 Interfaces Group Tables for Sublayers

ifStackTable (2) ifTestTable (3)

mib-2(mgmt 1)

interfaces(2)

ifTable(2)

ifNumber(1)

Table 9.4 Interfaces Group Tables for Sublayers

Entity OID Description (brief)ifXTable ifMIBObjects 1 Additional objects for the interface

tableifStackTable ifMIBObjects 2 Information on relationship between

sublayersifTestTable ifMIBObjects 3 Tests that NMS instructs agent to

performifRecvAddressTable ifMIBObjects 4 Information on type of packets / frames

accepted on an interface

Chapter 9


9-19

Notes

ATM Transmission Groups

transmission(10)

ds1(18)

sonet(39)

ds3(30)

Figure 9.16 Transmission Groups for ATM

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

Chapter 9


9-20

ATM Managed Objects Group

atmNoTrafficDescriptor (1) aal5VccTable (12)

atmVcCrossconnectTable (11)

atVcCrossConnectIndexNext (10)

atmInterfaceConfTable (2)

atmInterfaceDs3PlcpEntry (3)

atmInterfaceTCTable (4) atmvpCrossConnectTable (9)

atmTrafficDescrParamTable (5) atmVpCrossConnectIndexNext (8)

atmVplTable (6) atmVclTable (7)

atmMIBObjects(1)

Figure 9.17 ATM Managed Objects Group

Entity OID Description (brief)atmNoTrafficDescriptor atmMIBObjects 1 ATM traffic descriptor typeatmInterfaceConfTable atmMIBObjects 2 ATM local interface

configuration parametertable

atmInterfaceDs3PlcpEntry atmMIBObjects 3 ATM interface DS3 PLCPparameters and statevariables table

atmInterfaceTCTable atmMIBObjects 4 ATM TC sublayerconfiguration and stateparameters table

atmTrafficDescrParamTable atmMIBObjects 5 ATM traffic descriptor typeand associated parameters

atmVplTable atmMIBObjects 6 Virtual path link tableatmVclTable atmMIBObjects 7 Virtual channel link tableatmVpCrossConnectNext atmMIBObjects 8 Index for virtual path cross-

connect tableatmVpCrossConnectTable atmMIBObjects 9 Virtual path cross-connect

tableatmVcCrossConnectNext atmMIBObjects 10 Index for virtual channel

cross-connect tableatmVcCrossConnectTable atmMIBObjects 11 Virtual cross-connect tableaal5VccTable atmMIBObjects 12 AAL VCC performance

parameters table

Chapter 9


9-21

Notes

M2 Interface Management

• 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• DXI (Data Exchange Interface)• LAN Emulation• NNI

atmForumNetworkManagement (5)

atmfLanEmulation (4)

atmForumAdmin (1)

atmForumUni (2)

atmUniDxi (3)

atmForum(353)

Chapter 9


9-22

ATM UNI Group

atmfAddressRegistrationAdminGroup (11)

atmfVccAbrGroup (10)

atmfVpcAbrGroup (9)

atmfSrvcRegistryGroup (8)

atmfNetPrefixGroup (7)

atmfPhysicalGroup (1)

atmForumUNI(2)

atmfAtmLayerGroup (2)

atmfAtmStatsGroup (3)

atmfVpcGroup (4)

Figure 9.18 ATM UNI MIB Object Group

atmForum{enterprises 353}

atmfVccGroup (5) atmfAddressGroup (6)

Entity OID Description (brief)atmfPhysicalGroup atmForumUni 1 Defines a table of physical

layer status and parameterinformation

atmfAtmLayerGroup atmForumUni 2 Defines a table of ATM layerstatus and parameterinformation

atmfAtmStatsGroup atmForumUni 3 DeprecatedatmfVpcGroup atmForumUni 4 Defines a table of status and

parameter information on thevirtual path connections

atmfVccGroup atmForumUni 5 Defines a table of status andparameter information on thevirtual channel connections

atmfAddressGroup atmForumUni 6 Defines the network-sideIME table containing theuser-side ATM-layeraddresses

atmfNetPrefixGroup atmForumUni 7 Defines a user-side IMEtable of network prefixes

atmfSrvcRegistrryGroup atmForumUni 8 Defines the network-sideIME table containing allservices available to theuser-side IME

atmfVpcAbrGroup atmForumUni 9 Defines a table ofoperational parametersrelated to ABR virtual pathconnections

atmfVccAbrGroup atmForumUni 10 Defines a table ofoperational parametersrelated to ABR virtualchannel connections

AtmfAddressRegistrationAdminGroup

atmForumUni 11

Chapter 9


9-23

Notes

M3 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

• 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

Chapter 9


9-24

Notes

Customer Network Management (CNM)

• 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.

Carrier Management System

IStatus &

ConfigurationMonitoring

IIVirtual

ConfigurationControl

PublicATM

Network

Customer XNetwork

ManagementSystem

PrivateATM

Network

Customer X Site 1

PrivateATM

Network

Customer X Site 2Private

ATMNetwork

Customer X Site 4

ATMDevice

M3 Link

M2 Link PublicUNI

PublicUNI

PublicUNI

PublicUNI

Figure 9.19 Customer Management of Private and Public Networks

M4 link

Customer X Site 3

Chapter 9


9-25

Notes

M3 Class I Management General UNI Protocol Stackinformation

system group (RFC 1213),interfaces group, including ifTable andifStackTable (RFC 1213, RFC 1573),SNMP group (RFC 1213)

ATM Performanceinformation on customer'sUNI

ifTable (RFC 1573)

Physical-layer performanceand status information

all tables except dsx3ConfigTable (RFC 1407),all tables except dsx1ConfigTable (RFC 1406),all tables except the configuration tables and VTtables of SONET MIB (RFC 1595),atmInterfaceDs3PlcpTable /atmInterfaceTCTable of ATM MIB (RFC 1695)

ATM-Level informationconfiguration information

atmInterfaceConfTable of ATM MIB (RFC 1695)

Physical-layer configurationinformation

dsx3ConfigTable (RFC 1407)dsx1ConfigTable (RFC 1406)all configuration tables except thesonetVtConfigTable of SONET MIB (RFC 1595)

ATM-layer virtual path linkconfiguration and statusinformation

atmVplTable of ATM MIB (RFC 1695)

ATM-layer virtual channellink configuration and statusinformation

atmVclTable of ATM MIB (RFC 1695)

ATM-layer virtual pathconnection configuration andstatus information

atmVpCrossConnectTable andatmVpCrossConnectIndexNext of ATM MIB(RFC 1695)

ATM layer virtual channelconnection configuration andstatus information

atmVcCrossConnectTable andatmVcCrossConnectIndexNext of ATM MIB (RFC1695)

ATM-layer trafficcharacterization (trafficdescriptors for customer'sUNIs) information

atmTrafficDescrParamTable of ATM MIB (RFC1695)

Event notifications on ATMlink going up or down

warmStart, coldStart, linkUp, linkDown of SNMPgroup (RFC 1695)

• Class I requirements used by customer NMS from carrier NMS• The MIB access is “read-only”

Chapter 9


9-26

Notes

M3 Class II ManagementATM level information configuration information atmInterfaceConfTable in ATM

MIB (RFC 1695)Virtual path link configuration and statusconfiguration information

atmVplTable in ATM MIB (RFC1695)

Virtual channel link configuration and statusinformation

atmVclTable in ATM MIB (RFC1695)

Virtual path connection configuration andstatus information

atmVpCrossConnectTable andatmVpCrossConnectIndexNextof ATM MIB (RFC 1695)

Virtual channel connection configuration andstatus information

atmVcCrossConnectTable andatmVcCrossConnectIndexNextof ATM MIB (RFC 1695)

Traffic descriptors and information objects forvirtual path and channel connections

atmTrafficDescrParamTable inATM MIB (RFC 1695)

• 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

Chapter 9


9-27

Notes

ATM Relationship to TMNBusiness Management Layer

Service Management Layer

Network Management Layer

Element Management Layer

Element Layer

Figure 9.20 ATM Relationship to TMN Layered Architecture

NML/EML reference point

EML/EL reference point

ATM Management

• 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

Chapter 9


9-28

Notes

M4 Interface

and /or

M4 Interface

ATM NetworkView

ATM NEView

Managing SystemEnvironment

Managed SystemEnvironment

Figure 9.21 Dual Views of the M4 Interface

• 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

Chapter 9


9-29

Notes

Network Element View

NMSEnvironment

ATMNE

ATMNE

ATMNE

ATMNE

ATMNE

M4 Interface(ATM NE View Only)

Figure 9.22 NE-View Management Architecture

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

Chapter 9


9-30

Notes

Network View

Multi-SupplierSubnetwork

ATMNE

NMSEnvironment

ATMNE

ATMNE

SubNMS


Single-SupplierSubnetwork

ATMNE

ATMNE

ATMNE

SubNMS

M4 Interface(ATM Network View Only)

Figure 9.23 Example of Network-View Management Physical Configuration

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

Chapter 9


9-31

Notes

Combined NE and Network Views

Multi-SupplierSubnetwork

ATMNE

NMSEnvironment

ATMNE

ATMNE

SubNMS


Single-SupplierSubnetwork

ATMNE

ATMNE

ATMNE

SubNMS

M4 Interface(ATM Network View Only)

Figure 9.24 Example of NE + Network-View Management Physical Configuration



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

Chapter 9


9-32

Notes

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 system2. Configuration of UNIs, BICIs, and BISSIs3. Configuration of VPL/VCL termination points

and cross-connections4. Configuration of VPC and VCC OAM

segment end-points5. Event flow control - event forwarding

discriminator function

Chapter 9


9-33

Notes

M4 NE View Requirements:Fault Management

1. Notifying the network management system of a detected failure

2. Logging failure reports3. Isolating faults via demand testing

The specific functions are:Failure reporting of the various alarms. OAM(Operations, Administration and Maintenance)cell loopback testing

Chapter 9


9-34

Notes

M4 NE View Requirements:Performance Management

The functions of performance monitoring for anATM network are:1. Performance monitoring2. Traffic management3. UPC (User Parameter Control) / NPC

(Network Parameter Control) disagreement monitoring

4. Performance management control5. Network data collection

To accomplish these general functions, thefollowing specific functions are specified:1. Physical layer performance monitoring2. ATM cell level protocol monitoring3. UPC/NPC disagreement monitoring

Chapter 9


9-35

Notes

M4 Network View Requirements1. 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

Chapter 9


9-36

M4 Network View Requirements:Security Management

Table 9.10 Mapping of Threats and Objectives

Threat Confidentiality Data Integrity Accountability AvailabilityMasquerade x x x x

Eavesdropping x - - -Unauthorized

accessx x x x

Loss orcorruption ofinformation

- x x -

Repudiation - - x -Forgery x - x -Denial ofService

- - - x

Table 9.11 Mapping of Security Requirements and Services

Functional Security Requirements Security ServicesVerification of Identities User authentication

Peer entity authenticationData origin authentication

Controlled access and authorization Access controlProtection of confidentiality Stored data ----------------------- Transferred data

Access control------------------------------------------Confidentiality

Protection of data integrity Stored data ----------------------- Transferred data

Access control------------------------------------------Integrity

Strong Accountability Non-repudiationActivity logging Security alarm, audit trail and

recoveryAlarm reporting Security alarm, audit trail and

recoveryAudit Security alarm, audit trail and

recoverySecurity recovery / Management of Security -

Chapter 9


9-37

Notes

Management of LANE

atmfLanEmulation(4)

atmForum{enterprises 353}

busMIB(4)

elanMIB(2)

lesMIB(3)

elanLecsGroup (3)elanAdminGroup (1)

elanConfGroup(2)

Figure 9.25 ATM LAN Emulation MIB

busFaultGroup (3)busConfGroup (1)

busStatGroup (2)

lesFaultGroup (4)lesConfGroup (1)

lesStatGroup (2) lesLecStatGroup (3)

Chapter 9

• 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


9-38

Notes

LAN Emulation

Chapter 9

• 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

Table 9.12 LAN Emulation Module

Entity OID Description (brief)elanMIB atmfLanEmulation 2 Information required for

LEC to join ELANelanAdminGroup elanMIB 1 Registry for LEC

assignment policy typeselanConfGroup elanMIB 2 Construct and destroy

ELAN configurationelanLecsGroup elanMIB 3 Configure and monitor

LECslesMIB atmfLanEmulation 3 Information to create and

configure LESlesConfGroup lesMIB 1 LES configuration and

topology informationlesStatGroup lesMIB 2 Used to measure

performance and faultstatistics

lesLecStatGroup lesMIB 3 Information on LE-ARPand error statistics onLEC-LES pairs

lesFaultGroup lesMIB 4 Information on faultsbusMIB atmfLanEmulation 4 Information on BUSbusConfGroup busMIB 1 Information on BUS

configurationbusStatGroup busMIB 2 Information on BUS and

BUS-LEC statisticsbusFaultGroup busMIB 3 Maintains BUS error

statistics


9-39

Notes

ATM DXI Management

Chapter 9

Figure 9.26 ATM DXI Interface

DTE DCEATMDXI

ATMSwitch

ATMUNI

Figure 9.27 ATM DXI Local Management Interface

DTE DCEATMDXI

ATMSwitch

ATMUNI

NMS

SNMPDXI ILMI

ILMI

• 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 DXI and ATM UNI done using ILMI specifications• NMS manager uses SNMP with proxy agent for ILMI management objects


9-40

Documents

Nms Atm Network