Download Chapter 14

Chapter 14
Chapter 14
Web-Based Management
Network Management: Principles and Practice
© Mani Subramanian 2000
14-1
Chapter 14
Web-Base Management
• Display on Web browser
• Economical displays
• Ubiquitous access
• Reduction in network load for non-polled
configuration
• Web Interface vs Web-base management
• Web-based management
• Desktop management interface
• Web-based enterprise management
• Java management extensions
Notes
Network Management: Principles and Practice
© Mani Subramanian 2000
14-2
Chapter 14
Web Interface
Desktop PC
HTTP
Web Browser
NMS Console
Web Server
SNMP Manager
NMS
SNMP Agent
SNMP
Managed Objects
Figure 14.1 SNMP NMS with Web Interface
Notes
• SNMP-based NMS
• NMS database transferred to Web-server
• View with Web browser
• Protocol between NMS and network elements
is SNMP
• HTTP between Web server and browsers
Network Management: Principles and Practice
© Mani Subramanian 2000
14-3
Chapter 14
Proxy Server
Desktop PC
HTTP
Web Browser
Web Server
Manager
Applications
Proxy Server
SNMP / Other
Agent
SNMP/
Other
Managed Objects
Figure 14.2 Proxy Server with Web Interface
Notes
• Similar to Web interface
• No NMS monitor
• No GUI in manager applications
Network Management: Principles and Practice
© Mani Subramanian 2000
14-4
Chapter 14
Embedded WBM
Workstation/PC
Web Browser
Manager
Applications
HTTP
Web Server
Managed Objects
Figure 14.3 Embedded WBM Configuration
Notes
• Web servers are embedded in managed objects
• Data is pushed by the management agents in
managed objects to the manager applications
• Smart agents
• Portable agents
Network Management: Principles and Practice
© Mani Subramanian 2000
14-5
Chapter 14
HP Embedded Agent
Workstation/PC
Web Browser
Manager
Applications
Web Agent
Non-Web Agent
http
http
SNMP
Managed Objects
Figure 14.4 Hewlett-Packard Embedded Agent Configuration
Notes
• HP AdvanceStack Assistant®
• Web agents act as RMONs
• Network element w/o Web agent can be managed
• Remote probing of switched LANs
Network Management: Principles and Practice
© Mani Subramanian 2000
14-6
Chapter 14
Desktop Management Interface
Desktop-resident
Management Application
Management Interface API
Desktop Management Interface software (DMI)
MIF
Database
Component Interface API
Component
Agents
Figure 14.5 DMI Infrastructure
Notes
• 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
Network Management: Principles and Practice
© Mani Subramanian 2000
14-7
Chapter 14
DMI Functions
MI Interface
Client
Local Block
Interface
Application
Indication
Server
MI Interface
Client
RPC Support
Indication
Server
RPC Support
RPC to/from
Remote Systems
Data Block Mgmt
Interface
RPC SUPPORT
Management Interface Server
Indication Client
SP/MIF
Database
DMI Service Provider
Data Block Component
Interface
Block CI
Component
(HW/SW)
Procedural Component Interface
Procedural CI
Hardware
Component
Procedural CI
Software
Component
Procedural CI
Firmware
Component
Figure 14.6 DMI Functional Block Diagram
Notes
• Architecture has dual representation
• Version 1 with data block component I/F
• Version 2 with procedural component I/F
Network Management: Principles and Practice
© Mani Subramanian 2000
14-8
Chapter 14
DMI MIB
private
{1 3 6 1.4}
enterprises
(1)
dmtf
(412)
dmiMIB
(1)
dmiObjects
(1)
dmiNotification
(2)
dmtfStdMifs
(2)
dmtfDynOids
(3)
dmiConformance
(3)
Figure 14.7 DMI MIB
Notes
• MIF specified using ASN.1 syntax
• Can be managed by an SNMP manager
• DMTF task expanded to specify WBEM Web-based enterprise management
Network Management: Principles and Practice
© Mani Subramanian 2000
14-9
Chapter 14
Web-Based Enterprise
Management
Web Client
Desktop PC
SNMP Agent
Web Browser
DMI Agent
Management
Applications
CIM Agent
HTTP
CIM
Object Manager
(CIMOM)
HTTP
CIM
Schema
HTTP
HTTP
SNMP Provider
DMI Provider
SNMP
RPC
SNMP
Managed Objects
CIM
Managed Objects
DMI
Managed Objects
Figure 14.8 WBEM Architecture
Notes
• 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 specific protocol
Network Management: Principles and Practice
© Mani Subramanian 2000
14-10
Chapter 14
WBEM
Web Client
Desktop PC
SNMP Agent
Web Browser
DMI Agent
Management
Applications
CIM Agent
HTTP
CIM
Object Manager
(CIMOM)
HTTP
CIM
Schema
HTTP
HTTP
SNMP Provider
DMI Provider
SNMP
RPC
SNMP
Managed Objects
CIM
Managed Objects
DMI
Managed Objects
Figure 14.8 WBEM Architecture
Notes
• 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 Component Object Model (DCOM)
• Sun’s CIMOM uses JMX
• CIM modules:
• Core model: high level framework
• Common models: protocol-specific domains
• Extension model: technology specific
Network Management: Principles and Practice
© Mani Subramanian 2000
14-11
Chapter 14
Common Information Module
Application Component
ProductParentChild
Resource Component
Product
ManagedSystemElement
Component
(views)
Network Component
ProductSupport
ProductPhysicalElements
SupportAccess
SystemComponent
PhysicalElement
Realizes
LogicalElement
ServiceSAPDependency
SystemDevice
ServiceAccessBySAP
Logical Device
System
Service
ServiceAccessPoint
HostedService
HostedAccessPoint
Figure 14.9 WBEM CIM Core Model
Notes
• Solid lines indicate inheritances
• Dashed lines indicate associations
• PhysicalElement (e.g. interface card) and
LogicalElement (IP address) subclasses of
ManagedSystemElement
• System is aggregate of managed system elements
• Service access point is management, measurement,
and configuration of a service
• Managed system element considered as groups of
components
Network Management: Principles and Practice
© Mani Subramanian 2000
14-12
Chapter 14
Microsoft WMI
Management
Applications
Snap-in
Snap-in
COM/DCOM
IWbemServices
MOF Language
COM/DCOM API
CIM Object Manager
Repository
COM/DCOM
IWbemServices
Object Providers
WMI
SNMP
RPC
Win 32
WMI
Objects
SNMP
Objects
DMI
Objects
Win 32
Objects
Other
Objects
Figure 14.10 WMI Architecture
Notes
• 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 management agents (e.g. SNMP
agent)
Network Management: Principles and Practice
© Mani Subramanian 2000
14-13
Chapter 14
Service Driven Network
• Network of services (instead of network of
components)
• Service needs provisioning and management
• Webphone is Internet analogy to telephone
• Webphone is network-centric device (thin client,
hand-held device)
• Webphone is a plug-in device in service network
• Java technology calls plug-in JavaBean
• MBean is management JavaBean
Notes
Network Management: Principles and Practice
© Mani Subramanian 2000
14-14
Chapter 14
JDMK
Java
Virtual
Machine
Manager
Web Browser
Application
Protocol
Adaptor
Web Server
HTML Adaptor
Protocol
Adaptor
C-Bean
MBean
MBean
MBean
Core Management Framework / MBean Server
Managed Managed Managed
Object
Object
Object
Figure 14.11 Java Dynamic Management Agent Architecture
Notes
• Java dynamic management tool kit to build Javabased NMS
• MBean is an intelligent agent; does not need polling
as in SNMP 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
Network Management: Principles and Practice
© Mani Subramanian 2000
14-15
Chapter 14
Management Bean
Manager
Web Server
MB
http://URLA/<Management AppletA>
http://URLB/<Management AppletB>
http://URLC/<Management AppletC>
Master
Agent
MB
MB
Agent Profile A
Core Management
Framework
C
MB
MB
B
Java DMK
Figure 14.12 Management Bean (MB) Flow
Diagram
Notes
• JDMK agents are under the control of master JDMK
agent - hierarchical structure
• Manager is NMS
• Web server stores management services as applet
files with the agents’ URL
• MBean pulled out of the Web server at boot time
Network Management: Principles and Practice
© Mani Subramanian 2000
14-16
Chapter 14
JMX Architecture
Manager
Level
Proprietary
Management
Application
Web Browser
Additional
Manager
APIs
Proprietary
Management
Application
SNMP
Manager
API
JMX Manager
Agent Level
CIM/WBEM
API
Protocol
Adaptor
Web Server
HTML Adaptor
Connector
MBean Server
Connector
MBean Server
Service
Service
TMN
Manager
API
Instrumentation
Level
Managed
Object
Managed
Object
Java Virtual Machine
Managed
Object
Java Virtual Machine
Figure 14.13 JMX Components
Notes
• JMX architecture comprises three levels
• Instrumentation
• JMX-manageable resources - network devices,
applications, service entities, and systems
• Developed in Java or Java wrappers as MBeans
• MBeans implemented either static or dynamic
• Agents
• MBean server is a set of services for handling
MBeans
Network Management: Principles and Practice
© Mani Subramanian 2000
14-17
Chapter 14
JMX Architecture (cont’d)
Manager
Level
Proprietary
Management
Application
Web Browser
Additional
Manager
APIs
Proprietary
Management
Application
SNMP
Manager
API
JMX Manager
Agent Level
CIM/WBEM
API
Protocol
Adaptor
Web Server
HTML Adaptor
Connector
MBean Server
Connector
MBean Server
Service
Service
TMN
Manager
API
Instrumentation
Level
Managed
Object
Managed
Object
Java Virtual Machine
Managed
Object
Java Virtual Machine
Figure 14.13 JMX Components
Notes
• 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 SNMP
• Agent-Manager communication infrastructure uses
HTTP, CORBA/IIOP, etc.
Network Management: Principles and Practice
© Mani Subramanian 2000
14-18
Chapter 14
JMX Architecture (cont’d)
Manager
Level
Proprietary
Management
Application
Web Browser
Additional
Manager
APIs
Proprietary
Management
Application
SNMP
Manager
API
JMX Manager
Agent Level
CIM/WBEM
API
Protocol
Adaptor
Web Server
HTML Adaptor
Connector
MBean Server
Connector
MBean Server
Service
Service
TMN
Manager
API
Instrumentation
Level
Managed
Object
Managed
Object
Java Virtual Machine
Managed
Object
Java Virtual Machine
Figure 14.13 JMX Components
Notes
• Manager
• 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)
Network Management: Principles and Practice
© Mani Subramanian 2000
14-19
Chapter 14
Storage Area Network: Jiro
Client Tier
GUI
Web Browser
Management Logic Tier
Jiro Platform
Resources Tier
CIM
DMI
WMI
JMX
SNMP
Other
Figure 14.14 Jiro Architecture
Notes
• Jiro (pronounced gyro) is a platform for managing
storage area network
• Three-tier architecture
• Jiro core specifies Jiro platform
• Object model supports distributed objects based
on Java object model
• Component model is a set of core components
used to build portable applications
Network Management: Principles and Practice
© Mani Subramanian 2000
14-20
Chapter 14
Looking Ahead
• Future network and system management
frameworks should accommodate well-established
SNMP 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
Notes
Network Management: Principles and Practice
© Mani Subramanian 2000
14-21