IBM 26K6477 User Guide - Page 45

SMASH, profiles, supported, command, target, properties, Command, editing - stock

Page 45 highlights

Sample path for this tree: To manage the switch's IP endpoint, the target address might be: /modular1/switch1/ipendpt1 where: v modular is the UFcT for a component in CIM Class ComputerSystem with OtherDedicatedDescriptions=Modular v switch is the UFcT for a component in CIM Class ComputerSystem where Dedicated=Switch v ipendpt is the UFcT for the CIM Class IPProtocolEndpoint modular links to switch through the SystemComponent addressing association. switch links to ipendpt through the HostedAccessPoint addressing association. SMASH CLP profiles Management of system elements through SMASH is described using a large number of profiles. A profile is an object model that describes an aspect of the system in terms of classes, associations, aggregations, and inheritances while keeping within the constraints of the CIM core model. SMASH uses profiles to make heterogeneous systems appear similar, define required and recommended properties, and help define addressing and tags. Because addressing in SMASH is based on associations, profiles detail those required associations. SMASH CLP supported command target properties Command target properties are attributes that can contain values associated with a target that the SMASH CLP needs to process the command. Command target properties identify properties of the target class that the command retrieves or modifies. You express property values in property name=value, property name==value, and just property name formats. There can be zero or more property terms per command. For example, chassis properties include Model, SerialNumber, SKU and Version, where: v Model is the vendor system model and machine type of the chassis. v SerialNumber is a manufacturer-allocated number used to identify the chassis. v SKU is the stock-keeping unit number for the chassis. v Version is a string that indicates the version of the chassis. For further details about command target properties, see "SMASH Proxy supported targets (by UFcT) and associated command target properties" on page 72, "SMASH Proxy command target property descriptions" on page 94, and "CIM property types" on page 102. Command line editing The SMASH CLP supports a rich set of command-line editing capabilities that save keystrokes for many typical sessions. Chapter 3. Using the SMASH CLP command line 29

  • 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

Sample
path
for
this
tree:
To
manage
the
switch’s
IP
endpoint,
the
target
address
might
be:
/modular1/switch1/ipendpt1
where:
v
modular
is
the
UFcT
for
a
component
in
CIM
Class
ComputerSystem
with
OtherDedicatedDescriptions=
Modular
v
switch
is
the
UFcT
for
a
component
in
CIM
Class
ComputerSystem
where
Dedicated=
Switch
v
ipendpt
is
the
UFcT
for
the
CIM
Class
IPProtocolEndpoint
modular
links
to
switch
through
the
SystemComponent
addressing
association.
switch
links
to
ipendpt
through
the
HostedAccessPoint
addressing
association.
SMASH
CLP
profiles
Management
of
system
elements
through
SMASH
is
described
using
a
large
number
of
profiles.
A
profile
is
an
object
model
that
describes
an
aspect
of
the
system
in
terms
of
classes,
associations,
aggregations,
and
inheritances
while
keeping
within
the
constraints
of
the
CIM
core
model.
SMASH
uses
profiles
to
make
heterogeneous
systems
appear
similar,
define
required
and
recommended
properties,
and
help
define
addressing
and
tags.
Because
addressing
in
SMASH
is
based
on
associations,
profiles
detail
those
required
associations.
SMASH
CLP
supported
command
target
properties
Command
target
properties
are
attributes
that
can
contain
values
associated
with
a
target
that
the
SMASH
CLP
needs
to
process
the
command.
Command
target
properties
identify
properties
of
the
target
class
that
the
command
retrieves
or
modifies.
You
express
property
values
in
property
name=value
,
property
name==value
,
and
just
property
name
formats.
There
can
be
zero
or
more
property
terms
per
command.
For
example,
chassis
properties
include
Model,
SerialNumber,
SKU
and
Version
,
where:
v
Model
is
the
vendor
system
model
and
machine
type
of
the
chassis.
v
SerialNumber
is
a
manufacturer-allocated
number
used
to
identify
the
chassis.
v
SKU
is
the
stock-keeping
unit
number
for
the
chassis.
v
Version
is
a
string
that
indicates
the
version
of
the
chassis.
For
further
details
about
command
target
properties,
see
“SMASH
Proxy
supported
targets
(by
UFcT)
and
associated
command
target
properties”
on
page
72,
“SMASH
Proxy
command
target
property
descriptions”
on
page
94,
and
“CIM
property
types”
on
page
102.
Command
line
editing
The
SMASH
CLP
supports
a
rich
set
of
command-line
editing
capabilities
that
save
keystrokes
for
many
typical
sessions.
Chapter
3.
Using
the
SMASH
CLP
command
line
29