View
250
Download
1
Tags:
Embed Size (px)
Citation preview
Chapter 14
Web-Based Management
Chapter 14
14-1Network Management: Principles and Practice© Mani Subramanian 2000
Notes
Web-Base Management
Chapter 14
• 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
14-2Network Management: Principles and Practice© Mani Subramanian 2000
Notes
14-3
Web Interface
Chapter 14
NMS
SNMP Manager
Managed Objects SNMP Agent
Web Server
Web Browser
NMS Console
Desktop PC
Figure 14.1 SNMP NMS with Web Interface
SNMP
HTT
P
• 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
Notes
14-4
Proxy Server
Chapter 14
Proxy Server
ManagerApplications
Managed Objects SNMP / OtherAgent
Web Server
Web Browser
Desktop PC
Figure 14.2 Proxy Server with Web Interface
SNMP/Other
HTT
P
• Similar to Web interface• No NMS monitor• No GUI in manager applications
Network Management: Principles and Practice© Mani Subramanian 2000
Notes
14-5
Embedded WBM
Chapter 14
ManagerApplications
Managed Objects Web Server
Web Browser
Workstation/PC
Figure 14.3 Embedded WBM Configuration
HTTP
• 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
Notes
14-6
HP Embedded Agent
Chapter 14
• HP AdvanceStack Assistant® • Web agents act as RMONs• Network element w/o Web agent can be managed• Remote probing of switched LANs
ManagerApplications
Managed Objects
http
Web Agent
Web Browser
Workstation/PC
Figure 14.4 Hewlett-Packard Embedded Agent Configuration
http
SNMP
Non-Web Agent
Network Management: Principles and Practice© Mani Subramanian 2000
Notes
14-7
Desktop Management Interface
Chapter 14
Desktop Management Interface software (DMI)
Management Interface API
Component Interface API
ComponentAgents
Desktop-residentManagement Application
MIFDatabase
Figure 14.5 DMI Infrastructure
• 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
Notes
14-8
DMI Functions
Chapter 14
DMI Service Provider SP/MIFDatabase
Management Interface Server
RPC Support
MI InterfaceClient
IndicationServer
RPC Support
MI InterfaceClient
IndicationServerLocal Block
InterfaceApplication
Data Block MgmtInterface
RPC SUPPORT
Indication Client
Data Block ComponentInterface
Procedural Component Interface
Block CIComponent(HW/SW)
Procedural CIHardware
Component
Procedural CISoftware
Component
Procedural CIFirmware
Component
RPC to/fromRemote Systems
Figure 14.6 DMI Functional Block Diagram
• 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
Notes
14-9
DMI MIB
Chapter 14
enterprises(1)
dmtf(412)
dmiMIB(1)
dmtfStdMifs(2)
dmtfDynOids(3)
dmiConformance(3)
dmiNotification(2)
private{1 3 6 1.4}
dmiObjects(1)
Figure 14.7 DMI MIB
• 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
Notes
14-10
Web-Based Enterprise Management
Chapter 14
Web Client
SNMPManaged Objects
DMI Managed Objects
DMI ProviderSNMP Provider
CIMObject Manager
(CIMOM)CIM
Schema
ManagementApplications
Web Browser
Desktop PC
HTTP HTTP
HTTP
SNMP RPC
CIM Managed Objects
HTTP
Figure 14.8 WBEM Architecture
SNMP Agent
DMI Agent
CIM Agent
• 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
Notes
14-11
WBEM
Chapter 14
Web Client
SNMPManaged Objects
DMI Managed Objects
DMI ProviderSNMP Provider
CIMObject Manager
(CIMOM)CIM
Schema
ManagementApplications
Web Browser
Desktop PC
HTTP HTTP
HTTP
SNMP RPC
CIM Managed Objects
HTTP
Figure 14.8 WBEM Architecture
SNMP Agent
DMI Agent
CIM Agent
• 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
Notes
14-12
Common Information Module
Chapter 14
Application Component
Resource Component
ManagedSystemElement
PhysicalElement LogicalElement
System
Network Component
Logical Device ServiceAccessPointService
Realizes
Component(views)
ServiceSAPDependency
Figure 14.9 WBEM CIM Core Model
SystemDevice
HostedService
ServiceAccessBySAP
SystemComponent
Product
SupportAccess
ProductSupport
ProductPhysicalElements
ProductParentChild
HostedAccessPoint
• 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
Notes
14-13
Microsoft WMI
Chapter 14
• 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)
CIM Object Manager RepositoryMOF Language
COM/DCOM API
Object Providers
WMIObjects
WMI
SNMPObjects
SNMP
DMIObjects
RPC
Win 32Objects
Win 32
OtherObjects
COM/DCOMIWbemServices
ManagementApplications
Snap-inSnap-in
COM/DCOMIWbemServices
Figure 14.10 WMI Architecture
Network Management: Principles and Practice© Mani Subramanian 2000
Notes
14-14
Service Driven Network
Chapter 14
• 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
Network Management: Principles and Practice© Mani Subramanian 2000
Notes
14-15
JDMK
Chapter 14
Core Management Framework / MBean Server
MBe
an
MBe
an
MBe
an
C-B
ean
ProtocolAdaptor
ProtocolAdaptor
Web Server HTML Adaptor
Figure 14.11 Java Dynamic Management Agent Architecture
Manager Web Browser Application
ManagedObject
ManagedObject
ManagedObject
JavaVirtual
Machine
• Java dynamic management tool kit to build Java- based 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
Notes
14-16
Management Bean
Chapter 14
Core ManagementFramework
MB
MB
Agent Profile A
Java DMK
MasterAgent
Manager
MBhttp://URLA/<Management AppletA>http://URLB/<Management AppletB>http://URLC/<Management AppletC>
Web Server
MB
Figure 14.12 Management Bean (MB) FlowDiagram
MB
B C
• 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
Notes
14-17
JMX Architecture
Chapter 14
MBean Server
Service
ProtocolAdaptor
Web Server HTML Adaptor
Figure 14.13 JMX Components
Java Virtual Machine
ManagedObject
Connector
InstrumentationLevel
Agent Level
Web BrowserProprietary
ManagementApplication
ProprietaryManagementApplication
JMX Manager
MBean Server
Service
Java Virtual Machine
Connector
SNMPManager
API
CIM/WBEMAPI
TMNManager
API
AdditionalManager
APIsManager
Level
ManagedObject
ManagedObject
• 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
Notes
14-18
JMX Architecture (cont’d)
Chapter 14
MBean Server
Service
ProtocolAdaptor
Web Server HTML Adaptor
Figure 14.13 JMX Components
Java Virtual Machine
ManagedObject
Connector
InstrumentationLevel
Agent Level
Web BrowserProprietary
ManagementApplication
ProprietaryManagementApplication
JMX Manager
MBean Server
Service
Java Virtual Machine
Connector
SNMPManager
API
CIM/WBEMAPI
TMNManager
API
AdditionalManager
APIsManager
Level
ManagedObject
ManagedObject
• 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
Notes
14-19
JMX Architecture (cont’d)
Chapter 14
MBean Server
Service
ProtocolAdaptor
Web Server HTML Adaptor
Figure 14.13 JMX Components
Java Virtual Machine
ManagedObject
Connector
InstrumentationLevel
Agent Level
Web BrowserProprietary
ManagementApplication
ProprietaryManagementApplication
JMX Manager
MBean Server
Service
Java Virtual Machine
Connector
SNMPManager
API
CIM/WBEMAPI
TMNManager
API
AdditionalManager
APIsManager
Level
ManagedObject
ManagedObject
• 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
Notes
14-20
Storage Area Network: Jiro
Chapter 14
GUIWeb Browser
Jiro Platform
DMI WMI JMX SNMPCIM
Client Tier
Management Logic Tier
Resources Tier
Figure 14.14 Jiro Architecture
Other
• 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
Notes
14-21
Looking Ahead
Chapter 14
• 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
Network Management: Principles and Practice© Mani Subramanian 2000