IBM 26K6477 User Guide - Page 119

Managing, multiple, chassis, Handling, credentials

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

v s is a plus sign (+ ) or a dash (-), indicating the sign of the Universal Coordinated Time (UTC), which for all intents and purposes, is the same as Greenwich Mean Time correction field. The correction field is in minutes. For example, you would represent Monday, May 25, 1998, at 1:30:15 PM EST as: 19980525133015.0000000-300 Managing multiple chassis The SMASH Proxy allows management of all BladeCenter chassis in an environment from a single management station. All BladeCenter units are discovered through SLP using the oemiicmdiscover command (for details, see "OEM verbs" on page 49). After they have been discovered, the BladeCenter chassis, and their components, show up as CLP manageable objects and can be targeted by CLP commands either physically (/hdwr1/chassis1, /hdwr1/chassis2.../hdwr1/chassisn) or logically (/modular1, /modular2.../ modularn). Handling chassis credentials All chassis management functions require the CLP user to enter valid credentials for the managed chassis. The SMASH Proxy manages credentials by using a Linux stack paradigm such that only one set of credentials is active at a time. When a user first establishes a CLP session, the user gets a login prompt that requests a user name and password. The user name and password become the active set of credentials. If a user wishes to manage a system with a different set of credentials, he or she must use the oemiicmlogin command. When a user runs the oemiicmlogin command, the SMASH Proxy pushes the new set of credentials on the stack and they become the active set. When a user runs the oemiicmlogoff command, the SMASH Proxy discards the current set of credentials and the previous set becomes the active set. See the following procedure as an example: 1. A user is managing an environment with five chassis. Two of these chassis (chassis1 and chassis2) have their MM user name and password set to user1/password1. The other three chassis (chassis3, chassis4, and chassis5) have their MM username and/password set to user2/password2. 2. The user does an SSH to the SMASH Proxy system and gets a login prompt. The user logs in as clpuser/clppw: oemiicmlogin -userid user1 -password password1 The password stack now looks as follows: clpuser/clppw

  • 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
s
is
a
plus
sign
(
+
)
or
a
dash
(
-
),
indicating
the
sign
of
the
Universal
Coordinated
Time
(UTC),
which
for
all
intents
and
purposes,
is
the
same
as
Greenwich
Mean
Time
correction
field.
The
correction
field
is
in
minutes.
For
example,
you
would
represent
Monday,
May
25,
1998,
at
1:30:15
PM
EST
as:
19980525133015.0000000-300
Managing
multiple
chassis
The
SMASH
Proxy
allows
management
of
all
BladeCenter
chassis
in
an
environment
from
a
single
management
station.
All
BladeCenter
units
are
discovered
through
SLP
using
the
oemiicmdiscover
command
(for
details,
see
“OEM
verbs”
on
page
49).
After
they
have
been
discovered,
the
BladeCenter
chassis,
and
their
components,
show
up
as
CLP
manageable
objects
and
can
be
targeted
by
CLP
commands
either
physically
(/hdwr1/chassis1,
/hdwr1/chassis2.../hdwr1/chassisn)
or
logically
(/modular1,
/modular2.../
modular
n
).
Handling
chassis
credentials
All
chassis
management
functions
require
the
CLP
user
to
enter
valid
credentials
for
the
managed
chassis.
The
SMASH
Proxy
manages
credentials
by
using
a
Linux
stack
paradigm
such
that
only
one
set
of
credentials
is
active
at
a
time.
When
a
user
first
establishes
a
CLP
session,
the
user
gets
a
login
prompt
that
requests
a
user
name
and
password.
The
user
name
and
password
become
the
active
set
of
credentials.
If
a
user
wishes
to
manage
a
system
with
a
different
set
of
credentials,
he
or
she
must
use
the
oemiicmlogin
command.
When
a
user
runs
the
oemiicmlogin
command,
the
SMASH
Proxy
pushes
the
new
set
of
credentials
on
the
stack
and
they
become
the
active
set.
When
a
user
runs
the
oemiicmlogoff
command,
the
SMASH
Proxy
discards
the
current
set
of
credentials
and
the
previous
set
becomes
the
active
set.
See
the
following
procedure
as
an
example:
1.
A
user
is
managing
an
environment
with
five
chassis.
Two
of
these
chassis
(chassis1
and
chassis2)
have
their
MM
user
name
and
password
set
to
user1/password1
.
The
other
three
chassis
(chassis3,
chassis4,
and
chassis5)
have
their
MM
username
and/password
set
to
user2/password2
.
2.
The
user
does
an
SSH
to
the
SMASH
Proxy
system
and
gets
a
login
prompt.
The
user
logs
in
as
clpuser/clppw:
oemiicmlogin
-userid
user1
-password
password1
The
password
stack
now
looks
as
follows:
clpuser/clppw
<=
top
(active
credentials)
3.
The
user
runs
the
following
commands:
show
/hdwr1/chassis1
(due
to
invalid
credentials)
show
/hdwr1/chassis2
(due
to
invalid
credentials)
show
/hdwr1/chassis3
(due
to
invalid
credentials)
4.
The
user
enters
oemiicmlogin
to
log
in
as
user1/password1
.
The
password
stack
now
looks
as
follows:
user1/password1
<=
top
(active
credentials)
clpuser/clppw1
5.
The
user
runs
the
following
commands:
show
/hdwr1/chassis1
(succeeds)
Chapter
6.
Using
SMASH
Proxy
functionality
103