IBM 26K6477 User Guide - Page 17

Introduction - computers

Get IBM 26K6477 PDF manuals and user guides View all IBM 26K6477 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 17 highlights

Chapter 1. Introduction Large service providers require large quantities of equipment from one or more vendors to meet their computing needs. Most of this equipment must be managed actively. Examples of management activities include starting, configuration, monitoring operational parameters and alarms, executing firmware upgrades, and so on. Typically, management interfaces and procedures to perform such activities are standardized across an equipment vendor's portfolio. However, standardization of management interfaces and procedures across different vendors or even across different product portfolios offered by the same vendor is rare. As a result of the crucial need for this type of industry-wide standardization, the DMTF created a Web Based Enterprise Management (WBEM - pronounced ″web-em″) architecture, based on a Common Information Model (CIM). The CIM strives to define the manageable properties (for example, model number, serial number) and behavior (for example, reset, power on, power off) of entities, be they logical (for example, a software installation service) or physical (for example, a blade, a chassis), through standardized templates. The templates are described formally using a modeling technique and are generally accepted by the industry as being the most common representations of those manageable entities. Having defined models for common manageable entities, a standardized method for accessing the properties (or invoking the behavior) of these entities was required in order to effectively manage them. This implied that an agreed-upon method had to be devised for packaging the request for accessing properties or invoking behaviors, transporting the request across to the managed entity, executing the request on the managed entity, collecting the results of the execution and transporting it back to the requesting entity. In essence, an architecture had to be defined for interfacing system management software with the managed entities. This architecture is the WBEM. In the area of servers, the DMTF has been working to define common models for standalone servers, rack-mounted servers, server blades mounted on a chassis, and so on. The group within the DMTF responsible for addressing the standardization of server management is the server management workgroup. Although the WBEM architecture addressed the need for interfacing GUI-based system management programs (for example, IBM Director or HP OpenView) to the managed entities (for example, servers), a portion of the server management industry felt the need to provide a standardized command line interface (CLI) for managing servers. A standardization effort in this area, by the server management workgroup, produced the SMASH specifications. Through the SMASH CLP, you can run server management operations from a console by keying in standardized commands and options (as opposed to working through a GUI). The standard also enables you to write scripts that can work across equipment provided by different vendors. SMASH includes the following components: v An architectural framework v A specification for a CLP v A grammar for creating unique addresses for CIM objects so that they can serve as CLP command targets © Copyright IBM Corp. 2006 1

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
Chapter
1.
Introduction
Large
service
providers
require
large
quantities
of
equipment
from
one
or
more
vendors
to
meet
their
computing
needs.
Most
of
this
equipment
must
be
managed
actively.
Examples
of
management
activities
include
starting,
configuration,
monitoring
operational
parameters
and
alarms,
executing
firmware
upgrades,
and
so
on.
Typically,
management
interfaces
and
procedures
to
perform
such
activities
are
standardized
across
an
equipment
vendor’s
portfolio.
However,
standardization
of
management
interfaces
and
procedures
across
different
vendors
or
even
across
different
product
portfolios
offered
by
the
same
vendor
is
rare.
As
a
result
of
the
crucial
need
for
this
type
of
industry-wide
standardization,
the
DMTF
created
a
Web
Based
Enterprise
Management
(WBEM
-
pronounced
″
web-em
″
)
architecture,
based
on
a
Common
Information
Model
(CIM).
The
CIM
strives
to
define
the
manageable
properties
(for
example,
model
number,
serial
number)
and
behavior
(for
example,
reset,
power
on,
power
off)
of
entities,
be
they
logical
(for
example,
a
software
installation
service)
or
physical
(for
example,
a
blade,
a
chassis),
through
standardized
templates.
The
templates
are
described
formally
using
a
modeling
technique
and
are
generally
accepted
by
the
industry
as
being
the
most
common
representations
of
those
manageable
entities.
Having
defined
models
for
common
manageable
entities,
a
standardized
method
for
accessing
the
properties
(or
invoking
the
behavior)
of
these
entities
was
required
in
order
to
effectively
manage
them.
This
implied
that
an
agreed-upon
method
had
to
be
devised
for
packaging
the
request
for
accessing
properties
or
invoking
behaviors,
transporting
the
request
across
to
the
managed
entity,
executing
the
request
on
the
managed
entity,
collecting
the
results
of
the
execution
and
transporting
it
back
to
the
requesting
entity.
In
essence,
an
architecture
had
to
be
defined
for
interfacing
system
management
software
with
the
managed
entities.
This
architecture
is
the
WBEM.
In
the
area
of
servers,
the
DMTF
has
been
working
to
define
common
models
for
standalone
servers,
rack-mounted
servers,
server
blades
mounted
on
a
chassis,
and
so
on.
The
group
within
the
DMTF
responsible
for
addressing
the
standardization
of
server
management
is
the
server
management
workgroup.
Although
the
WBEM
architecture
addressed
the
need
for
interfacing
GUI-based
system
management
programs
(for
example,
IBM
Director
or
HP
OpenView)
to
the
managed
entities
(for
example,
servers),
a
portion
of
the
server
management
industry
felt
the
need
to
provide
a
standardized
command
line
interface
(CLI)
for
managing
servers.
A
standardization
effort
in
this
area,
by
the
server
management
workgroup,
produced
the
SMASH
specifications.
Through
the
SMASH
CLP,
you
can
run
server
management
operations
from
a
console
by
keying
in
standardized
commands
and
options
(as
opposed
to
working
through
a
GUI).
The
standard
also
enables
you
to
write
scripts
that
can
work
across
equipment
provided
by
different
vendors.
SMASH
includes
the
following
components:
v
An
architectural
framework
v
A
specification
for
a
CLP
v
A
grammar
for
creating
unique
addresses
for
CIM
objects
so
that
they
can
serve
as
CLP
command
targets
©
Copyright
IBM
Corp.
2006
1