Outline

1
(No Transcript)
2
Outline

• ?????????????
• WEBM??????

3
???????????????
4
Agenda

• Introduction Motivation
• IP based Network Topology
• Non IP based Network Topology
• Fault Diagnosis Techniques
• Integrating OSGi Platform with Web Services

5
Introduction Motivation(1/2)
6
Introduction Motivation(2/2)

• With the rise of information household
  appliances, the network has already spread to
  every corner of home from the office desk
  gradually
• Effective network management and diagnosis will
  be a significant challenge for users, home
  appliance designers and service providers

7
Two types of network topology

• IP-based network topology
• Ethernet
• Wi-Fi
• Powerline
• Non-IP-based network topology
• IEEE 1394

8
Ethernet

• These early networks are bulky, largely
  point-to-point loop- or star-based systems.
• Based on the IEEE 802.3 standard.
• Copper-pair or coaxial-based transport systems
  are bi-directional, typically have a high degree
  of reliability, and are thus widespread among
  businesses as the standard choice for networking
  office PCs and printers.
• They require the use of bulky cabling, and are
  typically expensive to install.
• Some home networks have Ethernet, but because of
  its expense and difficulty to install, few have
  chosen to use it.

9
Powerline

• Multiple power outlets can be found in each room
• AC outlets are ubiquitous in virtually every
  existing home
• Powerline networking takes advantage of the
  unused capacity of the power cable to transmit
  data over the existing home power cabling
• A low cost solution
• Capable of distributing data as fast as 10 Mbps

10
A Powerline Based Home Network
11
LONWorks

• LONWORKS(Local Operation Networks) technology is
  an important new solution for control networks
  developed by Echelon Corporation

12
HomePlug

• A HomePlug adapter is connected directly or using
  a power cord to a wall power outlet and to
  computer using USB or Ethernet cable (depending
  on the adapter model)
• HomePlug network occupies higher frequencies in
  the powerline spectrum so theoretically it
  doesn't interfere with electricity. In addition,
  certain measures in the HomePlug standard are
  used to avoid interference and noise from
  electricity

13
Simple Network Management Protocol (SNMP)
14
Topology Discovery IP-Based Network
15
Topology Discovery IP-Based Network Topology
16
IP-based Simulated Environment
17
IP-based Diagnosis Algorithm
18
SNMP Switch Topology Change and Diagnosis
19
Non-IP-Based Network Topology Topology Discovery
of IEEE 1394
20
Topology Discovery of IEEE 1394

• The topology of an IEEE1394 system can be
• Daisy chain
• Tree
• Combination of Daisy chain and Tree
• Three phases of configuring an IEEE1394 system
• Step 1. Bus initialize
• leaf or branch
• Step 2. Tree identify
• root is identified
• Step 3. Self identify
• physical node ids are assigned

21
IEEE 1394 (FireWire) (1/2)

• A hardware and software standard for transporting
  data at 100,200, 400, or 800 megabits per second
  (Mbps)
• A digital interface
• there is no need to convert digital data into
  analog and tolerate a loss of data integrity
• Physically small
• the thin serial cable can replace larger and more
  expensive interfaces
• Easy to use
• there is no need for terminators, device IDs, or
  elaborate setup

22
IEEE 1394 (FireWire) (2/2)

• Hot pluggable
• users can add or remove 1394 devices with the bus
  active
• Inexpensive
• priced for consumer products
• Scaleable architecture
• may mix 100, 200, and 400 Mbps devices on a bus
• Flexible topology
• support of daisy chaining and branching for true
  peer-to-peer communication
• Non-proprietary
• there is no licensing problem to use for products

23
1394 Protocol Stack
24
Root of the Topology After Tree Identify
25
IEEE1394 Diagnosis Scenario
26
IEEE1394 Diagnosis Algorithm
27
Fault Diagnosis Techniques

• Model-based Technique
• Application deployment and dependency models
• Network connectivity network topology
• Experience-based Technique
• Heuristic knowledge

28
SOAP

• The SOAP message is the basic unit of
  communication between peers.
• SOAP messages are written in XML, making SOAP
  platform independent any system capable of
  creating and parsing XML documents can send and
  receive SOAP messages
• The power of XML allows SOAP messages to be
  fairly complex in structure and to transmit
  highly complex data types

29
Web Services-Technical View(1/2)
SOAP HTTPXML (Simple Object Access Protocol)
30
Web Services-Technical View(2/2)
31
Web Services-based Diagnosis System
32
WS-HND Bundle Architecture
33
Expert System
34
Web Services-based Diagnosis System Architecture
35
Information Appliance2.0 with Expert System

• Information appliances2.0 is the extension of
  WEB2.0
• In WS_HND system of the expert system contains
  the knowledge and analytical skills that are not
  confining to a general administrator

36
IEEE 1394 Topology Change and Diagnosis
37
WEBM??????
38
Agenda

• Introduction
• Common Information Model (CIM)
• CIM Schema
• WBEM Architecture
• WBEM Is Defined by A Set of Standards
• CIM Operation Example
• Conclusion

39
Introduction

• Web-Based Enterprise Management (WBEM) is A
  platform and resource independent DMTF
  (Distributed Management Task Force) standard
• Pronounced WEB-M
• The WBEM goal is to provide customers with the
  ability to manage all systems regardless of their
  instrumentation type using a common standard

40
Web-Based Enterprise Management
41
Why WBEM
On-Device Comparison of SNMP and WBEM
42
WBEM Features

• Advantages of using WBEM
• Real standard
• Mature implementations exist
• Standard interface for different monitoring
  systems
• Standard interface for information providers
• Can replace log file style providers
• Disadvantages of using WBEM
• No caching or throttle control for providers
• Provider interface can be complex

43
WBEM Applications(1/2)

• Microsoft Outlook Exchange
• WMI offers administrators a very robust way of
  configuring and analyzing system performance and
  settings
• WMI contains the power to access an almost
  endless array of settings and configurations
• Exchange 2003 provides many new features as well
  as improves on existing features and this is true
  of Exchange's WMI as well

44
WBEM Applications(2/2)

• PJ Technologies GoverLan
• Goverlan Feature Offerings Domain Administration
• The extensive list of domain administration tasks
  includes
• Object and Active Directory hierarchy management
• Domain policy management
• Account settings and password management
• Real-time Support, Diagnostics and Administration
  of users and machines

45
WBEM in Operating Systems

• Novell has adopted the OpenWBEM open source
  implementation of WBEM
• Microsoft has developed the WMI technology and
  has included it in Microsoft Windows
• Sun Microsystems has created WBEM-Services for
  the Solaris operating environment
• Hewlett Packard has included WBEM Services CORE
  Product in the HP-UX OS since version 11iv1
• RedHat ships OpenPegasus as part of RedHat
  Enterprise Linux

46
A Table of WBEM History
47
An Example of WBEM
48
Common Information Model (CIM)

• Common Information Model (CIM) is a model for
  describing overall management information
• CIM is comprised of a specification and a schema
• The specification defines the details for
  integration with other management models
• Managed Object Format (MOF) is popular and is
  machine-readable

49
The Structure of CIM
50
CIM Specification

• CIM specification describes an object-oriented
  meta model based on the Unified Modeling Language
  (UML)
• The specification defines the syntax and rules, a
  CIM syntax language based on Interface Definition
  Language (IDL) called Managed Object Format (MOF)

51
CIM Schema

• The CIM Schema is the combination of the Core
  and Common Models.

52
CIM Schema Model

• CIM Schema consists of the following models
• The Core Model
• A set of classes, associations, properties and
  methods that provide a basic vocabulary for
  describing managed systems.
• The Common Model
• Captures notions that are common to particular
  management areas, but which are independent of a
  particular technology or implementation.

53
The Management Gap
54
WBEM Architecture
55
Structure of The WBEM Server
56
Architecture Components

• CIM Client issues CIM Operation requests and
  receives and processes CIM Operation responses.
• CIM Server receives and processes CIM Operation
  requests and issues CIM Operation responses
• CIM Provider It provides the mapping between the
  CIM interface and a resource-specific interface

CMI Client
CMI Server
57
WBEM Provider

• Providers are special classes that communicate
  with managed resources, such as disk drives and
  CPUs, to access data
• The providers then forward the data to the CIM
  Object Manager (CIMOM), the primary WBEM agent
  that coordinates WBEM Services
• It was given in the DMTF Glossary that a provider
  communicates with managed objects to access data
  and event notifications from a variety of sources

58
Provider Architecture for WBEM Service
59
Types of Providers

• Method Providers handle calls to extrinsic
  methods
• Instance Providers handle the creation,
  enumeration and deletion of instances of
  particular classes
• Property Providers handle operator requests for
  getting and setting properties
• Association Providers handle the creation,
  deletion of associations between classes or
  instances
• Indication Providers handle events and alarms
  raised in the system being managed

60
WBEM Is Defined by A Set of Standards

• A Data Description
• CIM Specification the description of a
  meta-language for describing data.
• DMTF CIM Schema a description of managed
  resources.
• An Encoding
• A standard for encoding CIM data and operations.
• A Transport Protocol
• The definition of a protocol for transporting CIM
  encoded requests and responses.

61
CIM-XML WBEM Standard

• A CIM-XML Encoding
• A standard for encoding CIM data and operations
  into XML
• An HTTP Transport Protocol
• The definition of a standard protocol for
  transporting CIM-XML encoded requests and
  responses over HTTP

62
Protocol Adapter

• A Protocol Adapter is responsible for the
  implementation of the encoding and transport
  components of a WBEM Standard.

63
Communication Protocol
64
CIM Operation Overview

• The DMTF has defined a set of CIM Operations.

65
CIM Operation Example
66
CIM Operation
67
CIM-XML Encoding

• Defines a standard encoding of CIM Operations and
  CIM data into XML.

68
CIM-XML Request
69
CIM-XML Response
70
HTTP Transport
71
HTTP Message
72
CIM Operation Flow (I)
CMI Client
CMI Server
73
CIM Operation Flow (II)
CIM Server coordinates the processing of
requests and responses among the Providers and
sends CIM Operation responses back to the CIM
Client.
CIM Provider translates CIM formatted requests
into resource specific operations and translates
resource-specific responses into CIM formatted
responses.
Managed Resource is a manageable entity (e.g.,
memory, process, system, application, network)
plus the resource-specific instrumentation
capable of monitoring and controlling the
resource.
74
Other Open Source WBEM Implementations

• WBEM Services (Java)
• The Open Group's Pegasus (C)
• SNIA Open Source CIMOM (Java)
• OpenWBEM (C)
• SBLIM (Standards Based Linux Instrumentation for
  Manageability)

75
Conclusion

• Some advantages of CIM and WBEM
• Independence from platform, programming
  language and compiler
• Independence from information model
• Extensibility
• Easy integration of new management capabilities
• Security and Internet accessibility