IBM 26K6477 User Guide - Page 51

Using, SMASH, Proxy

Page 51 highlights

Chapter 5. Using the SMASH Proxy This section details SMASH Proxy utilization and includes discussion of the following topics: v "Before you begin" v "SMASH Proxy supported BladeCenter components" on page 36 v "Installing the SMASH Proxy" on page 37 v "Configuring SNMPv3 in the SMASH Proxy" on page 39 v "SNMPv3 configuration in the MM" on page 40 v "SLP configuration in the MM" on page 44 v "Configuring the credentials server" on page 45 v "Accessing the SMASH Proxy: Remote user access" on page 45 v "Accessing the SMASH Proxy: Local user access" on page 47 v "Uninstalling the SMASH Proxy" on page 48 Before you begin You must correctly configure the BladeCenter unit before you can use the SMASH Proxy CLI to manage it. Hardware and software required for the SMASH Proxy CLI are as follows: SMASH Proxy hardware The SMASH Proxy requires a network connection to the BladeCenter chassis that are management targets. The IBM server that the Proxy resides on should have at least 512 MB of memory and 40 MB of available disk space. SMASH Proxy software The SMASH Proxy requires Red Hat Enterprise Linux ES 4.0 Update 1 and SUSE Linux Enterprise Server 9.0 Service Pack 1 (SLES 9). BladeCenter hardware The SMASH Proxy requires no special hardware other than a network connection to use it with a BladeCenter chassis. To use the SOL feature with a blade, the blade must support SOL functionality. BladeCenter firmware Make sure you are using the latest version of firmware for your blade servers, management modules, and other BladeCenter components for all chassis that the SMASH Proxy will manage. Go to the IBM Support Web site (www.ibm.com/pc/support/) for the latest information about upgrading the firmware for BladeCenter components. The latest instructions are in the documentation that comes with the updates. The SMASH Proxy CLI is supported on: v BladeCenter management module firmware level 1.21F and later v BladeCenter T management module firmware level 1.07G and later v BladeCenter H management module firmware level 1.01 and later © Copyright IBM Corp. 2006 35

  • 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

Chapter
5.
Using
the
SMASH
Proxy
This
section
details
SMASH
Proxy
utilization
and
includes
discussion
of
the
following
topics:
v
“Before
you
begin”
v
“SMASH
Proxy
supported
BladeCenter
components”
on
page
36
v
“Installing
the
SMASH
Proxy”
on
page
37
v
“Configuring
SNMPv3
in
the
SMASH
Proxy”
on
page
39
v
“SNMPv3
configuration
in
the
MM”
on
page
40
v
“SLP
configuration
in
the
MM”
on
page
44
v
“Configuring
the
credentials
server”
on
page
45
v
“Accessing
the
SMASH
Proxy:
Remote
user
access”
on
page
45
v
“Accessing
the
SMASH
Proxy:
Local
user
access”
on
page
47
v
“Uninstalling
the
SMASH
Proxy”
on
page
48
Before
you
begin
You
must
correctly
configure
the
BladeCenter
unit
before
you
can
use
the
SMASH
Proxy
CLI
to
manage
it.
Hardware
and
software
required
for
the
SMASH
Proxy
CLI
are
as
follows:
SMASH
Proxy
hardware
The
SMASH
Proxy
requires
a
network
connection
to
the
BladeCenter
chassis
that
are
management
targets.
The
IBM
server
that
the
Proxy
resides
on
should
have
at
least
512
MB
of
memory
and
40
MB
of
available
disk
space.
SMASH
Proxy
software
The
SMASH
Proxy
requires
Red
Hat
Enterprise
Linux
ES
4.0
Update
1
and
SUSE
Linux
Enterprise
Server
9.0
Service
Pack
1
(SLES
9).
BladeCenter
hardware
The
SMASH
Proxy
requires
no
special
hardware
other
than
a
network
connection
to
use
it
with
a
BladeCenter
chassis.
To
use
the
SOL
feature
with
a
blade,
the
blade
must
support
SOL
functionality.
BladeCenter
firmware
Make
sure
you
are
using
the
latest
version
of
firmware
for
your
blade
servers,
management
modules,
and
other
BladeCenter
components
for
all
chassis
that
the
SMASH
Proxy
will
manage.
Go
to
the
IBM
Support
Web
site
(www.ibm.com/pc/support/)
for
the
latest
information
about
upgrading
the
firmware
for
BladeCenter
components.
The
latest
instructions
are
in
the
documentation
that
comes
with
the
updates.
The
SMASH
Proxy
CLI
is
supported
on:
v
BladeCenter
management
module
firmware
level
1.21F
and
later
v
BladeCenter
T
management
module
firmware
level
1.07G
and
later
v
BladeCenter
H
management
module
firmware
level
1.01
and
later
©
Copyright
IBM
Corp.
2006
35