HP DL360 HP VMware ESXi management environment - Page 21

Common Information Model

Get HP DL360 - ProLiant - G3 PDF manuals and user guides
UPC - 613326948835
View all HP DL360 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 21 highlights

WBEM has been broadened to include Web Services for Management (WS-Management) as an alternative management protocol. WBEM is generally viewed as more versatile than previous management standards such as SNMP because of its richer data model, which includes associations and inheritance, and its web-based protocols. Security can be built into WBEM more simply than into SNMP because it can leverage more secure, web-based protocols such as HTTPS. Common Information Model CIM is defined by the DMTF. It is the data model standard used in many management applications. A data model represents the elements of a system, including hardware, OS, and applications. It defines elements from network and storage hardware, as well as servers. It also defines the associations between those elements. Because it defines the management data in a common way, it enables management tools from a variety of vendors to be platform independent. CIM is a conceptual information model for describing management that is not bound to a particular implementation. This allows for the interchange of management information between management systems and applications. This can be either "agent-to-manager" or "manager-to-manager" communication that provides for Distributed System Management (DSM). CIM is the underlying data model for management initiatives such as SMASH and SMI-S. CIM is also the data model used by tools such as HP Systems Insight Manager (HP SIM) and HP OpenView. Systems Management Architecture for Server Hardware SMASH is a management initiative driven by the DMTF that specifies the data model (based on CIM) and protocols to be used for managing server hardware. It is a comprehensive management initiative, designed to address a need for cross-platform standards to manage servers from multiple vendors. It is routable, secure, and uses common industry-standard protocols. SMASH is specifically designed to manage servers using a lightweight CIM object model that is a subset of the CIM Schema. The Server Management Command Line Protocol (SM CLP) is one of the protocols specified by SMASH. It consists of human-oriented commands that are also suitable for use with scripts. SM CLP supports network access through Telnet and also Secure Shell v2 (SSHv2) for secure access. The SM CLP provides a lightweight command line syntax that allows systems from different vendors to be represented in similar ways. Products from server vendors, including standalone servers, server blades, rack servers, and partitionable servers, can support SM CLP commands. As a result, users on a management station or a client can execute common operations such as system power-on and power-off, system log display, boot configuration, and text-based remote console using the same commands across disparate vendor platforms. Since SMASH standardizes only the messages exchanged with management applications, it provides a high degree of interoperability for performing functions, regardless of the actual feature implementation. 21

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
WBEM has been broadened to include Web Services for Management (WS-Management) as an
alternative management protocol.
WBEM is generally viewed as more versatile than previous management standards such as SNMP
because of its richer data model, which includes associations and inheritance, and its web-based
protocols. Security can be built into WBEM more simply than into SNMP because it can leverage
more secure, web-based protocols such as HTTPS.
Common Information Model
CIM is defined by the DMTF. It is the data model standard used in many management applications. A
data model represents the elements of a system, including hardware, OS, and applications. It defines
elements from network and storage hardware, as well as servers. It also defines the associations
between those elements. Because it defines the management data in a common way, it enables
management tools from a variety of vendors to be platform independent. CIM is a conceptual
information model for describing management that is not bound to a particular implementation. This
allows for the interchange of management information between management systems and
applications. This can be either "agent-to-manager" or "manager-to-manager" communication that
provides for Distributed System Management (DSM). CIM is the underlying data model for
management initiatives such as SMASH and SMI-S. CIM is also the data model used by tools such as
HP Systems Insight Manager (HP SIM) and HP OpenView.
Systems Management Architecture for Server Hardware
SMASH is a management initiative driven by the DMTF that specifies the data model (based on CIM)
and protocols to be used for managing server hardware. It is a comprehensive management initiative,
designed to address a need for cross-platform standards to manage servers from multiple vendors. It is
routable, secure, and uses common industry-standard protocols. SMASH is specifically designed to
manage servers using a lightweight CIM object model that is a subset of the CIM Schema.
The Server Management Command Line Protocol (SM CLP) is one of the protocols specified by
SMASH.
It consists of human-oriented commands that are also suitable for use with scripts. SM CLP
supports network access through Telnet and also Secure Shell v2 (SSHv2) for secure access. The SM
CLP provides a lightweight command line syntax that allows systems from different vendors to be
represented in similar ways. Products from server vendors, including standalone servers, server
blades, rack servers, and partitionable servers, can support SM CLP commands. As a result, users on
a management station or a client can execute common operations such as system power-on and
power-off, system log display, boot configuration, and text-based remote console using the same
commands across disparate vendor platforms. Since SMASH standardizes only the messages
exchanged with management applications, it provides a high degree of interoperability for
performing functions, regardless of the actual feature implementation.
21