Lecture 19: Web Based Management

Transcription

1 Lecture 19: Web Based Management Prof. Shervin Shirmohammadi SITE, University of Ottawa Prof. Shervin Shirmohammadi CEG Using the Web for Management Web browser UI connects with the management system, allowing NMS functionality from any node browser that has access to the network. Economical Ubiquitous access Not to confuse Web Interface and Web-based management Web Interface to Management System still primarily -based, web interface an added feature Web-based management Desktop management interface Web-based enterprise management Java management extensions Prof. Shervin Shirmohammadi CEG

2 Web Interface -based NMS NMS database transferred to Web-server View with Web browser Protocol between NMS and network elements is between Web server and browsers Desktop PC Desktop PC Proxy Method NMS Console NMS Proxy Server Applications / Other Agent / Other Agent Prof. Shervin Shirmohammadi CEG Figure 14.1 NMS with Web Interface Figure 14.2 Proxy Server with Web Interface Web servers are embedded in managed objects Data is pushed by the management agents in managed objects to the manager applications These management agents can have extra computing capabilities Opens the market for proprietary solutions that are customized to the product. Advantages? Disadvantages? Embedded WBM Workstation/PC Applications Figure 14.3 Embedded WBM Configuration Prof. Shervin Shirmohammadi CEG

3 HP Embedded Agent HP AdvanceStack Assistant Web agents act as RMONs Network element w/o Web agent can be managed Remote probing of switched LANs Workstation/PC Applications Web Agent Non-Web Agent http http Prof. Shervin Shirmohammadi CEG Figure 14.4 Hewlett-Packard Embedded Agent Configuration Desktop Management Interface (DMI) Industry standard generated by Desktop Management Task Force (DTMF) Started in 1992 to manage PCs Manages both hardware and software Two standards Management information format (MIF), similar to MIB Program interface with two APIs The DMI is in between the component and the application software that manages them. DMI 1.0 Desktop management DMI 2.0 Distributed desktop management. Desktop-resident Management Application Management Interface API Desktop Management Interface software (DMI) Interface API Agents Figure 14.5 DMI Infrastructure MIF Database Prof. Shervin Shirmohammadi CEG

4 DMI 2.0 Functions Architecture has dual representation Version 1 with data block component I/F Version 2 with procedural component I/F Local Block Interface Application MI Interface Client RPC Support Indication Server MI Interface Client RPC Support Indication Server Data Block Mgmt Interface RPC SUPPORT Management Interface Server Indication Client RPC to/from Remote Systems DMI Service Provider SP/MIF Database Data Block Interface Procedural Interface Block CI (HW/SW) Procedural CI Hardware Procedural CI Software Procedural CI Firmware Prof. Shervin Shirmohammadi CEG Figure 14.6 DMI Functional Block Diagram DMI MIB MIF specified using ASN.1 syntax Can be managed by an manager DMTF task expanded to specify WBEM (Web-Based Enterprise Management) Integrate existing standards, such as, CMIP, DMI, and. private { } enterprises (1) Reserved for Future Specs dmtf (412) dmimib (1) dmtfstdmifs (2) dmtfdynoids (3) dmiobjects (1) dminotification (2) dmiconformance (3) Prof. Shervin Shirmohammadi CEG Figure 14.7 DMI MIB 4

5 Web-Based Enterprise Management 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 protocolspecific agents Provider Web Client DMI Provider DMI Prof. Shervin Shirmohammadi CEG Desktop PC Management Applications CIM Object (CIMOM) CIM Figure 14.8 WBEM Architecture CIM Schema Agent DMI Agent CIM Agent RPC WBEM Web client is Web browser with management applications: Application requests use CIM schema Multiple instances of Web clients feasible CIM object manger mediates between Web clients, managed objects, and CIM schema Microsoft Windows Management Instrumentation uses Distributed Object Model (DCOM) Sun s CIMOM uses JMX The CIM Schema is used to determine which protocol system the managed object belongs to as well as perform MIB translations. CIM modules: Core model: high level framework applicable to all management domains. Common models: applicable to protocol-specific domains. Includes information on systems, applications, devices, users, and networks. Extension model: technology-specific extensions of the common model, such as UNIX or MS Windows OS specifics. Prof. Shervin Shirmohammadi CEG

6 Common Information Module Core Model Solid lines indicate inheritance, dashed lines indicate association PhysicalElement (e.g. interface card) and LogicalElement (e.g IP address) subclasses of ManagedSystemElement Logical Device is the functionality that the Physical Element supports. e.g. a network card can support modem or NIC. Product ProductSupport ProductParentChild ManagedSystemElement (views) Application Resource Network SupportAccess ProductPhysicalElements System PhysicalElement LogicalElement Realizes ServiceSAPDependency SystemDevice ServiceAccessBySAP Logical Device System Service ServiceAccessPoint HostedService HostedAccessPoint Figure 14.9 WBEM CIM Core Model System is aggregate of managed system elements Service access point is management, measurement, and configuration of a service Managed system elements may be considered as groups of components, for example network, resource, and applications. Prof. Shervin Shirmohammadi CEG Windows Management Instrumentation WMI is Microsoft infrastructure to support WBEM CIM WMI comprises management infrastructure, applications, and agents CIMOM has plug-in management applications COM/DCOM API specifies interface to CIMOM CIM is the CIM schema Object providers are WMI WMI Objects management agents (e.g. agent) Management Applications Objects COM/DCOM IWbemServices CIM Object Object Providers RPC DMI Objects Snap-in COM/DCOM IWbemServices Snap-in Win 32 Win 32 Objects Figure WMI Architecture MOF Language COM/DCOM API Other Objects Repository Prof. Shervin Shirmohammadi CEG

7 Java Management Extensions JMX is another approach for total management using Web technology JMX defines Management architecture APIs Management services Based on Java Dynamic Management Kit, a technology introduced by Sun Microsystems for the development of Service Driven Networks Prof. Shervin Shirmohammadi CEG Service Driven Network Service Driven Network: network of services (instead of network of components) Service needs provisioning and management Let s use as an examplewebphone: Internet analogy to telephone Webphone is network-centric device thin client hand-held device a plug-in device in service network Java technology calls plug-in JavaBean MBean is management JavaBean Prof. Shervin Shirmohammadi CEG

8 JDMK Java dynamic management tool kit to build Java-based NMS MBean is an intelligent agent; does not need polling as in agent JDMK library of core management services implemented as MBeans Java Dynamic Management agent comprises MBeans: core management framework, MBean server Protocol adaptors: interfaces to applications An MBean can be dynamically loaded. For example, an MBean can be downloaded to an agent to take statistical samples of a router. It can then be removed after the problem has been diagnosed. This is similar to the concept of software blades. The term blade designates a standardized module which one can plug in to a computer system Java Virtual Machine Application Protocol Adaptor Core Management Framework / MBean Server Prof. Shervin Shirmohammadi CEG Figure Java Dynamic Management Agent Architecture MBean Managed Object HTML Adaptor MBean MBean Managed Managed Object Object Protocol Adaptor C-Bean Management Bean JDMK agents are under the control of master JDMK agent hierarchical structure is NMS Web server stores management services as applet files with the agents URL MBean pulled out of the Web server at boot time AppletA> AppletB> AppletC> MB Master Agent MB MB Agent Profile A Core Management Framework MB MB B C Java DMK Figure Management Bean (MB) Flow Prof. Shervin Shirmohammadi CEG 4395 Diagram

9 JMX Architecture JMX architecture comprises three levels Instrumentation JMX-manageable resources - network devices, applications, service entities, and systems Developed in Java or Java wrappers as MBeans Level MBeans implemented either static or dynamic Agents MBean server is a set of services for handling MBeans Agent Level Proprietary Management Application Protocol Adaptor HTML Adaptor MBean Server Service Connector Proprietary Management Application JMX Connector MBean Server Service Additional APIs API CIM/WBEM API TMN API Instrumentation Level Managed Object Managed Object Managed Object Java Virtual Machine Java Virtual Machine Prof. Shervin Shirmohammadi CEG Figure JMX s JMX Agents Agents MBean server is a set of services for handling MBeans JMX-manageable resources register with an agent I/F adaptor to Web browser contains a Web server I/F to JMX manager called a connector Protocol adaptors represents MBeans in another protocol, such as Agent- communication infrastructure uses, CORBA/IIOP, etc. Prof. Shervin Shirmohammadi CEG

10 JMX Comprises management applications, network manager, and browser Interfaces with agents via the connector (JMX manager) or protocol adaptors CIM/WBEM APIs are grouped into CIM, client, and provider. CIM API represents CIM elements as Java class objects JMX manager interfaces with external database using JDBC (SQL databases) Prof. Shervin Shirmohammadi CEG Looking Ahead Future network and system management frameworks should accommodate well-established entities Web agents are intelligent and future points to the use of Web technology Web-based management offers two options WBEM is comprehensive and centralized approach to enterprise management; accommodates both scalar and object-oriented schemes JMX is decentralized and uses Java technology; agents embedded in objects and can be downloaded from NMS; platform independent Future NMS environment could be a merger of the old and the new - at least in the near future Prof. Shervin Shirmohammadi CEG