IBM 26K6477 User Guide - Page 34

Physical, logical, target, addressing, Addressing, associations

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

Physical and logical target addressing As described in "Addressing managed elements" on page 4, SMASH uses SM ME addressing to provide a user-friendly way to accurately address managed elements or objects in a managed system. Objects are divided into physical and logical targets. Physical targets represent actual hardware that a user can touch, for example, a chassis, a blade, or a daughter card and logical targets represent software functions or entities, for example, a network configuration or an event log. Note that a given entity can be represented both logically and physically. For example, a switch has a physical UFcT representation of pkg and a logical UFcT representation of switch. You can address physical or logical targets, for example, a switch component on a BladeCenter enterprise chassis that requires action, as follows: v The switch has a logical UFcT of switch. The enterprise chassis has a logical UFcT of modular. v Because you manage a specific BladeCenter enterprise chassis and its switch, you further define the UFcTs to UFiTs that can be used in a target SM ME address within a CLP command used for managing the switch. In this case, the BladeCenter enterprise chassis unique UFiT identifier is modular1 and the switch's unique UFiT is switch1. v The resulting address to the switch would be: /modular1/switch1. Addressing associations As discussed in "Physical and logical target addressing," objects can be divided into physical and logical targets where physical targets represent actual hardware, for example, a chassis, and logical targets represent software functions or entities, for example, a network configuration. Associations represent relationships between objects with the objects linking to each other through these associations. The Server Management Managed Element Addressing Specification explains that associations can be of two types: addressing and nonaddressing. An addressing association means that you can use it to target an object with the following addressing format: [parent object]/[object] For example, admin1/hdwr1. While a BladeCenter chassis is represented physically as a chassis target, and a BladeCenter blade is represented physically as a bladepkg target, the containment relationship of a blade in a chassis is represented by a PackageInChassis association. These associations can themselves be targets on a SMASH command line: show chassis1=>PackageInChassis=>/hdwr1/chassis1/bladepkg1 Another example, Figure 3 on page 20, shows that the CIM_AdminDomain (UFcT is admin1) links to CIM_ConcreteCollection (UFcT is hdwr1) through the OwningCollectionElement association. 18 SMASH Proxy Installation and User's Guide

  • 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
Physical
and
logical
target
addressing
As
described
in
“Addressing
managed
elements”
on
page
4,
SMASH
uses
SM
ME
addressing
to
provide
a
user-friendly
way
to
accurately
address
managed
elements
or
objects
in
a
managed
system.
Objects
are
divided
into
physical
and
logical
targets.
Physical
targets
represent
actual
hardware
that
a
user
can
touch,
for
example,
a
chassis,
a
blade,
or
a
daughter
card
and
logical
targets
represent
software
functions
or
entities,
for
example,
a
network
configuration
or
an
event
log.
Note
that
a
given
entity
can
be
represented
both
logically
and
physically.
For
example,
a
switch
has
a
physical
UFcT
representation
of
pkg
and
a
logical
UFcT
representation
of
switch
.
You
can
address
physical
or
logical
targets,
for
example,
a
switch
component
on
a
BladeCenter
enterprise
chassis
that
requires
action,
as
follows:
v
The
switch
has
a
logical
UFcT
of
switch
.
The
enterprise
chassis
has
a
logical
UFcT
of
modular
.
v
Because
you
manage
a
specific
BladeCenter
enterprise
chassis
and
its
switch,
you
further
define
the
UFcTs
to
UFiTs
that
can
be
used
in
a
target
SM
ME
address
within
a
CLP
command
used
for
managing
the
switch.
In
this
case,
the
BladeCenter
enterprise
chassis
unique
UFiT
identifier
is
modular1
and
the
switch’s
unique
UFiT
is
switch1
.
v
The
resulting
address
to
the
switch
would
be:
/modular1/switch1
.
Addressing
associations
As
discussed
in
“Physical
and
logical
target
addressing,”
objects
can
be
divided
into
physical
and
logical
targets
where
physical
targets
represent
actual
hardware,
for
example,
a
chassis,
and
logical
targets
represent
software
functions
or
entities,
for
example,
a
network
configuration.
Associations
represent
relationships
between
objects
with
the
objects
linking
to
each
other
through
these
associations.
The
Server
Management
Managed
Element
Addressing
Specification
explains
that
associations
can
be
of
two
types:
addressing
and
nonaddressing.
An
addressing
association
means
that
you
can
use
it
to
target
an
object
with
the
following
addressing
format:
[parent
object]/[object]
For
example,
admin1/hdwr1.
While
a
BladeCenter
chassis
is
represented
physically
as
a
chassis
target,
and
a
BladeCenter
blade
is
represented
physically
as
a
bladepkg
target,
the
containment
relationship
of
a
blade
in
a
chassis
is
represented
by
a
PackageInChassis
association.
These
associations
can
themselves
be
targets
on
a
SMASH
command
line:
show
chassis1=>PackageInChassis=>/hdwr1/chassis1/bladepkg1
Another
example,
Figure
3
on
page
20,
shows
that
the
CIM_AdminDomain
(UFcT
is
admin1)
links
to
CIM_ConcreteCollection
(UFcT
is
hdwr1)
through
the
OwningCollectionElement
association.
18
SMASH
Proxy
Installation
and
User's
Guide