IBM 26K6477 User Guide - Page 21

admin, chassis, modular, fanpkg, system, ntempsensor, system1, system2, system3, admin1/modular1/

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

v Blades are containers for sensors. v A chassis is a container for blades and cooling fans. v An administrative domain is a logical entity that is the access point for managing a chassis. Figure 2. Example of managed element addressing Given this hierarchy, suppose that: v The administrative domain is specified in the CLP specification with the name admin. v The physical aspect of a chassis is specified with the name chassis. The logical aspect of a chassis is specified with the name modular. v A fan is specified with the name fanpkg. v The logical aspect of a blade is specified with the name system. v A temperature sensor is specified with the name ntempsensor. As examples, you can specify the following SM ME addresses: /admin1/chassis1/fanpkg1 /admin1/modular1/system1/ntempsensor1 Each of these given names (admin, chassis, modular, fanpkg, system, and ntempsensor) only specify a certain type (or class) of object. But the object names are very intuitive and, in the SMASH CLP, are termed user-friendly class tags (UFcT). However, as seen in Figure 2, CLP commands refer to a specific instance of an object type, for example, a particular blade. To differentiate between two blades, we can take the UFcT and add an instance number to the end of it. The result, system1, system2, system3, and so on, is called a user-friendly instance tag (UFiT), in SMASH terminology. Specifying an instance does not always make the managed element unambiguous. For example, system1 can reside in modular1 and another system1 can reside in modular6. To avoid ambiguity, you need to specify that the operation be performed on system1 residing in modular1 of admin1, for example. To specify this to a CLP program, you can write the target element as: /admin1/modular1/system1 In SMASH CLP terminology, /admin1/modular1/system1 is the user-friendly instance path (UFiP). In circumstances when all instances of a managed element need to be addressed, there is a short-hand notation for making such a selection: user-friendly selection tags Chapter 2. SMASH: An overview 5

  • 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
v
Blades
are
containers
for
sensors.
v
A
chassis
is
a
container
for
blades
and
cooling
fans.
v
An
administrative
domain
is
a
logical
entity
that
is
the
access
point
for
managing
a
chassis.
Given
this
hierarchy,
suppose
that:
v
The
administrative
domain
is
specified
in
the
CLP
specification
with
the
name
admin
.
v
The
physical
aspect
of
a
chassis
is
specified
with
the
name
chassis
.
The
logical
aspect
of
a
chassis
is
specified
with
the
name
modular
.
v
A
fan
is
specified
with
the
name
fanpkg
.
v
The
logical
aspect
of
a
blade
is
specified
with
the
name
system
.
v
A
temperature
sensor
is
specified
with
the
name
ntempsensor
.
As
examples,
you
can
specify
the
following
SM
ME
addresses:
/admin1/chassis1/fanpkg1
/admin1/modular1/system1/ntempsensor1
Each
of
these
given
names
(admin,
chassis,
modular,
fanpkg,
system,
and
ntempsensor)
only
specify
a
certain
type
(or
class)
of
object.
But
the
object
names
are
very
intuitive
and,
in
the
SMASH
CLP,
are
termed
user-friendly
class
tags
(UFcT)
.
However,
as
seen
in
Figure
2,
CLP
commands
refer
to
a
specific
instance
of
an
object
type,
for
example,
a
particular
blade.
To
differentiate
between
two
blades,
we
can
take
the
UFcT
and
add
an
instance
number
to
the
end
of
it.
The
result,
system1
,
system2
,
system3
,
and
so
on,
is
called
a
user-friendly
instance
tag
(UFiT)
,
in
SMASH
terminology.
Specifying
an
instance
does
not
always
make
the
managed
element
unambiguous.
For
example,
system1
can
reside
in
modular1
and
another
system1
can
reside
in
modular6.
To
avoid
ambiguity,
you
need
to
specify
that
the
operation
be
performed
on
system1
residing
in
modular1
of
admin1,
for
example.
To
specify
this
to
a
CLP
program,
you
can
write
the
target
element
as:
/admin1/modular1/system1
In
SMASH
CLP
terminology,
/admin1/modular1/system1
is
the
user-friendly
instance
path
(UFiP)
.
In
circumstances
when
all
instances
of
a
managed
element
need
to
be
addressed,
there
is
a
short-hand
notation
for
making
such
a
selection:
user-friendly
selection
tags
Figure
2.
Example
of
managed
element
addressing
Chapter
2.
SMASH:
An
overview
5