APNOMS 2003 An Efficient Service Management Architecture in Virtual Active Network Using Script MIB School of Electronics and Information Kyung Hee University Kyung Deok Seo, Choong Seon Hong

APNOMS Introduction (1/2) Several Problems of Todays Networks The difficulty of integrating new technologies and standards into the shared network infrastructure. Poor performance due to redundant operations at several protocol layers. Difficulty accommodating new services in the existing architectural model. Active Network Discussed by DARPA (The Defense Advanced Research Projects Agency) research community from 1994 Store – – Forward Provide flexibility in new protocol and service deployment Process

APNOMS Introduction (2/2) Figure 1. Architectural framework of active node : DARPA AN WG (1999)

APNOMS Virtual Active Network (1/2) Concept of the VAN (Virtual Active Network) VAN can be described as a graph of virtual active nodes interconnected by Virtual Links Management EE Customer 1 EE Customer 3 EE Node A Node E Node D Node C Node B Management EE Customer 2 EE Management EE Customer 1 EE Management EE Physical Active Network Virtual Active Network EE Figure 3. Example of VANFigure 2. Concept of VAN

APNOMS Virtual Active Network (2/2) Architecture of a Active Node for VAN A node operating system layer configures and provides access to the nodes resources Customer can create a new service and manage a service using SPI Provider can manage active node using LVMI Figure 4. Architecture of a active node for VAN

APNOMS Script MIB (1/2) Overview of the Script MIB Developed by the IETF DISMAN (Distributed Network Management) working group and published in May 1999 as a proposed standard. Script MIB provides the following capabilities. Transfer of management scripts to a distributed manager. Initiating, suspending, resuming and terminating management scripts. Transfer of arguments for management scripts. Monitoring and control running management scripts. Transfer of the results produced by running management scripts.

APNOMS Script MIB (2/2) Structure of the Script MIB smLangTable (& smExtsnTable) smScriptTable (& smCodeTable) smLaunchTable smRunTable Figure 5. Usage of the Script MIB

APNOMS Service Management Architecture Using Script MIB (1/2) SPI that provided by VAN provider is very limited for managing private VAN service. Our Constructions VAN Manager consists of Service Info. Table Node Info. Table Script Repository Table GUI Generator Authentication Module ANEP Packet Generator Figure 6. VAN Manager

APNOMS Service Management Architecture Using Script MIB (2/2) Active network node for VAN based Service consists of ANEP Daemon Packet Analyzer Script MIB Implementation SNMP Agent Customers EE Management EE Back UP Manager Management Script Repository Figure 7. Active network node for VAN

APNOMS Service Management Scenario using Proposed Architecture Back Up Manager VAN Manager Management EE Customer 1 EE Management EE Customer 2 EE Management EE Customer 2 EE Management EE Customer 1 EE Customer 2 EE Management EE Customer 3 EE Node A Node E Node D Node C Node B Customer 2 Provider Management Script Repository S S S S S S S Figure 8. Service Management Scenario

APNOMS Implementation Figure 9. Main ModulesFigure 10. Testbed Using Toolkits Active Network Node Implementation Using ANTS (University of Utah & University of Washington) Script MIB Implementation Using JASMIN (NEC Europe C&C Lab. & TU Braunschweig) SNMP Agent Using Net-SNMP Programming Language JDK 1.1.8

APNOMS Conclusions & Future Works Conclusions Active networks using the VAN concept give customers new possibilities and benefits Service management using Script MIB is fit for service in VAN Service management architecture in VAN using Script MIB is dynamic and flexible Future Works Performance evaluation Study of VAN based service and managed objects