using corba for network management of next … · corba for ne management 2001-jan-18 ©2001...

25
Using CORBA for Network Management of Next Generation Networking Equipment Ken Black Ken Black Founder and President Founder and President Highlander Engineering Highlander Engineering January 18, 2001 January 18, 2001

Upload: ngonga

Post on 25-Sep-2018

217 views

Category:

Documents


0 download

TRANSCRIPT

Using CORBA for Network Management of Next

Generation Networking Equipment

Ken BlackKen BlackFounder and PresidentFounder and PresidentHighlander EngineeringHighlander Engineering

January 18, 2001January 18, 2001

2001-Jan-18CORBA for NE Management©2001 Highlander Engineering, Inc.

2

Agenda

• Why CORBA is used• How CORBA is used• Agent architectures

2001-Jan-18CORBA for NE Management©2001 Highlander Engineering, Inc.

3

Network Elements

Enterprise World Embedded World

UserInterface

(GUI)

NetworkManager

Telnetclient

HTTP

Telnet, TL-1

SNMP, CMIP

Traditional Approaches to Network Management

2001-Jan-18CORBA for NE Management©2001 Highlander Engineering, Inc.

4

Network Management Today

Management App(s)Management App(s)

Management Management ObjectsObjects

Billing AppBilling App

Billing Object

Customer App(s)Customer App(s)User Interface User Interface

(GUI) C++ or Java(GUI) C++ or Java

Application Application ObjectsObjects

Internet/Internet/Intranet/Intranet/ExtranetExtranet

Windows or Windows or Java ClientJava Client

UsersUsers

BrowserBrowser

GatewayGateway

WebServerWebServer

2001-Jan-18CORBA for NE Management©2001 Highlander Engineering, Inc.

5

Network Element

NetworkManagement

Agent

ORB

CPU ORB

CPU ORB

CPU ORB

CORBA in the Network Element

InternalDistribution

Enterprise Component Integration

Network Management

2001-Jan-18CORBA for NE Management©2001 Highlander Engineering, Inc.

6

Motivations for CORBA Management

• Suitability of CORBA for next generation technologies: optical, wireless, ATM, VoIP…– Object-oriented CORBA/IDL well-suited to modeling– SNMP inefficient due to simplicity, lack of object

orientation– CMIP/GDMO too complex, expensive and scarce

• Economics of CORBA being a broadly deployed, general-purpose IT standard– Tools are lower cost and more broadly available– Greater # of knowledgeable engineers, more training

and literature

2001-Jan-18CORBA for NE Management©2001 Highlander Engineering, Inc.

7

Agenda

• Why CORBA is used• How CORBA is used• Agent architectures

2001-Jan-18CORBA for NE Management©2001 Highlander Engineering, Inc.

8

Network Management Uses

Interface for custom management apps– Including Web-based

Standard interface for element & network management systems

2001-Jan-18CORBA for NE Management©2001 Highlander Engineering, Inc.

9

CORBA for Custom Management Apps

Device

EmbeddedAgent

(C++ & C)

ORB

CardCard

ManagementApplication

(usually Java)

ORB

Web browser

ManagementApplet

ORB

2001-Jan-18CORBA for NE Management©2001 Highlander Engineering, Inc.

10

Management with Java and CORBA

• Java is well-suited to custom management applications– Platform independence– Easily build sophisticated GUIs

• Java includes CORBA– From Java 2 (JDK 1.2)

• With CORBA, embedded C++ objects look native to Java-based manager

RFC1213_MIB.system s = …;System.out.println(“Sys Admin: “ + s.sysContact);

2001-Jan-18CORBA for NE Management©2001 Highlander Engineering, Inc.

11

Web-based Management

• Java applets served via HTTP– Simple distribution

• VM not required in device, uses browser’s

Web browser

JavaUI

ORB

Device

C++Application

ORB

StoredUI applet

HTTP

2001-Jan-18CORBA for NE Management©2001 Highlander Engineering, Inc.

12

CORBA As An Open Interface

• IDL provides safe programmability to customers

• Augments or replaces a command-line/scripting interface–Write Java apps instead of scripts

2001-Jan-18CORBA for NE Management©2001 Highlander Engineering, Inc.

13

Information Modeling for Custom Management Apps

• Define CORBA objects and operations to reflect real-world use

// IDLinterface IPStack {

boolean DeleteRoute(in string interface,in string destination);

};

// Java Management ApplicationIPStack myIP = … ;boolean OK;

OK = myIP.DeleteRoute(“149.101.10.32”, “microsoft.com”);

2001-Jan-18CORBA for NE Management©2001 Highlander Engineering, Inc.

14

SNMP Equivalent-- the IP routing tableipRouteTable OBJECT-TYPE

SYNTAX SEQUENCE OF IpRouteEntryACCESS not-accessibleSTATUS mandatoryDESCRIPTION

“The IP Routing table.”::= { ip 21 }

ipRouteEntry OBJECT-TYPESYNTAX IpRouteEntryACCESS not-accessibleSTATUS mandatoryDESCRIPTION

“A route ...”INDEX { ipRouteDest }::= { ipRouteTable 1 }

-- Only relevant entries shownIpRouteEntry ::=

SEQUENCE {ipRouteDest IpAddress,ipRouteIfIndex INTEGER,ipRouteType INTEGER,

}

ipRouteType OBJECT-TYPESYNTAX INTEGER {

other(1),invalid(2),direct(3),indirect(4)

}ACCESS read-writeSTATUS mandatoryDESCRIPTION

“…Setting this objectto the value invalid(2)has the effect ofinvalidating thecorresponding entryin the ipRouteTable…”

::= { ipRouteEntry 8 }

2001-Jan-18CORBA for NE Management©2001 Highlander Engineering, Inc.

15

SNMP Algorithm

1. Scan the ipAddrTable to identify the ipRouteIfIndex corresponding to the interface of the route to be deleted

2. Scan the ipRouteTable to identify the row with the appropriate ipRouteIfIndex and ipRouteDest

3. Set the value of ipRouteType in that row to invalid(2)

2001-Jan-18CORBA for NE Management©2001 Highlander Engineering, Inc.

16

Network Management Uses

Interface for custom management apps– Including Web-based

Standard interface for element & network management systems

2001-Jan-18CORBA for NE Management©2001 Highlander Engineering, Inc.

17

CORBA Is Already Broadly Used for Mgmt

Network Elements

Element Mgmt

Network Mgmt

Service CORBABusiness

CMIP SNMP TL1

CORBA

2001-Jan-18CORBA for NE Management©2001 Highlander Engineering, Inc.

18

CORBA Management Standards

• Joint Inter-Domain Management (JIDM)–Mapping from SNMP and GDMO/CMIP– From TMF & OMG, adopted by X/Open

• Native CORBA standards–Developed by ITU and technology-

specific organizations

2001-Jan-18CORBA for NE Management©2001 Highlander Engineering, Inc.

19

JIDM Scenarios

From www.jidm.org

2001-Jan-18CORBA for NE Management©2001 Highlander Engineering, Inc.

20

JIDM ExampleIDL Mapping of MIB-II System Group

interface system : SNMPMgmt::SmiEntry {readonly attribute DisplayStringType sysDescr;readonly attribute ASN1_ObjectIdentifier sysObjectID;readonly attribute TimeTicksType sysUpTime;attribute DisplayStringType sysContact;attribute DisplayStringType sysName;attribute DisplayStringType sysLocation;readonly attribute ASN1_Unsigned16 sysServices;

};

2001-Jan-18CORBA for NE Management©2001 Highlander Engineering, Inc.

21

Native CORBA Standardization

• ITU-T, based on T1M1– X.780: Guidelines for defining CORBA Managed Objects– Q.816: CORBA-based TMN Services– M.3120: CORBA network information model

• 3GPP• ATM Forum• DSL Forum (formerly ADSL Forum)• Network and Service Integration Forum (NSIF)• Software Defined Radio (SDR) Forum

– Joint Tactical Radio System (JTRS)

2001-Jan-18CORBA for NE Management©2001 Highlander Engineering, Inc.

22

Agenda

• Why CORBA is used• How CORBA is used• Agent architectures

2001-Jan-18CORBA for NE Management©2001 Highlander Engineering, Inc.

23

Agent Architecture

Network Element

CORBAManager

ORB IIOP

ORB

ORBORBORB

LineCards

ORB

Shelf Ctlr

System Ctlr

2001-Jan-18CORBA for NE Management©2001 Highlander Engineering, Inc.

24

Agent Architecture

Network Element

CORBAManager

ORB IIOP

IIOP

xxIOP

System Ctlr

ORB

Shelf Ctlr

ORBORBORB

LineCards

2001-Jan-18CORBA for NE Management©2001 Highlander Engineering, Inc.

25

CORBA Management Summary

• Same middleware can be leveraged for:– Network management– Internal distribution– General-purpose enterprise integration– Programmability interface

• Well-suited to Next Generation network technologies & topologies

• Fully distributed, not point-to-point• Endorsed by international standards bodies