IBM 26K6477 User Guide - Page 87

Handling, general, UFcTs, compared, specific

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 87 highlights

Table 41. Supported collections (continued) BladeCenter component Logical target UFiT Logical target UFiP Nonaddressing associations Collection of all logs logs1 /modularX /chassismgr1/logs1 none Collection of all capabilities for a management module capabilities1 /modularX/chassismgr1 none /capabilities1 Collection of all capabilities1 capabilities for a blade /modularX/systemY /capabilities1 none Collection of all component capacities for a chassis capacities1 /modularX/capacities1 none Switch Capacity configcapacity1 /modularX/capacities1 none /configcapacity1 Management module configcapacity2 /modularX/capacities1 none capacity /configcapacity2 Fan capacity configcapacity3 /modularX/capacities1 none /configcapacity3 Blade capacity configcapacity4 /modularX/capacities1 none /configcapacity4 Power supply capacity configcapacity5 /modularX/capacities1 none /configcapacity5 Target of nonaddressing associations Verbs help, show help, show help, show help, show help, show help, show help, show help, show help, show Handling general UFcTs compared to specific UFcTs The Server Management Managed Element Addressing Specification maps each CIM class modeled by an SMWG profile to a general UFcT. Additionally, a CIM instance can be mapped to a more specific UFcT based on the value of a particular property. For example, the CIM class CIM_ComputerSystem is mapped to the general UFcT: system However, if a computer system's instance has a Dedicated property equal to "Switch", it is given the specific UFcT: switch If its Dedicated property is equal to "Chassis Manager" (MM), it is given the specific UFcT: chassismgr If its Dedicated property is equal to "Management Controller" (Blade System Management Processor), it is given the specific UFcT: sp Within the SMASH Proxy, a user can identify and target objects by their most-specific UFcT. However, they also show up in a list of the general UFcTs. For example, if a user has two switches, one MM, and two blades in his chassis and does a show -d targets=system /modular1, the user sees the following output: Success UFiT: modular1 UFiT: chassismgr1 UFiT: switch1 UFiT: switch2 UFiT: switch3 UFiT: system1 UFiT: system2 UFiT: system4 UFiT: system6 UFiT: system7 Chapter 6. Using SMASH Proxy functionality 71

  • 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
Table
41.
Supported
collections
(continued)
BladeCenter
component
Logical
target
UFiT
Logical
target
UFiP
Nonaddressing
associations
Target
of
nonaddressing
associations
Verbs
Collection
of
all
logs
logs1
/modularX
/chassismgr1/logs1
none
help,
show
Collection
of
all
capabilities
for
a
management
module
capabilities1
/modularX/chassismgr1
/capabilities1
none
help,
show
Collection
of
all
capabilities
for
a
blade
capabilities1
/modularX/systemY
/capabilities1
none
help,
show
Collection
of
all
component
capacities
for
a
chassis
capacities1
/modularX/capacities1
none
help,
show
Switch
Capacity
configcapacity1
/modularX/capacities1
/configcapacity1
none
help,
show
Management
module
capacity
configcapacity2
/modularX/capacities1
/configcapacity2
none
help,
show
Fan
capacity
configcapacity3
/modularX/capacities1
/configcapacity3
none
help,
show
Blade
capacity
configcapacity4
/modularX/capacities1
/configcapacity4
none
help,
show
Power
supply
capacity
configcapacity5
/modularX/capacities1
/configcapacity5
none
help,
show
Handling
general
UFcTs
compared
to
specific
UFcTs
The
Server
Management
Managed
Element
Addressing
Specification
maps
each
CIM
class
modeled
by
an
SMWG
profile
to
a
general
UFcT.
Additionally,
a
CIM
instance
can
be
mapped
to
a
more
specific
UFcT
based
on
the
value
of
a
particular
property.
For
example,
the
CIM
class
CIM_ComputerSystem
is
mapped
to
the
general
UFcT:
system
However,
if
a
computer
system’s
instance
has
a
Dedicated
property
equal
to
“Switch”,
it
is
given
the
specific
UFcT:
switch
If
its
Dedicated
property
is
equal
to
“Chassis
Manager”
(MM),
it
is
given
the
specific
UFcT:
chassismgr
If
its
Dedicated
property
is
equal
to
“Management
Controller”
(Blade
System
Management
Processor),
it
is
given
the
specific
UFcT:
sp
Within
the
SMASH
Proxy,
a
user
can
identify
and
target
objects
by
their
most-specific
UFcT.
However,
they
also
show
up
in
a
list
of
the
general
UFcTs.
For
example,
if
a
user
has
two
switches,
one
MM,
and
two
blades
in
his
chassis
and
does
a
show
-d
targets=system
/modular1
,
the
user
sees
the
following
output:
Success
UFiT:
modular1
UFiT:
chassismgr1
UFiT:
switch1
UFiT:
switch2
UFiT:
switch3
UFiT:
system1
UFiT:
system2
UFiT:
system4
UFiT:
system6
UFiT:
system7
Chapter
6.
Using
SMASH
Proxy
functionality
71