IBM 87302RU Installation Guide - Page 94

Virtual

Get IBM 87302RU PDF manuals and user guides View all IBM 87302RU manuals
Add to My Manuals
Save this manual to your list of manuals

Page 94 highlights

- User. Read-only access to all switch module settings. - User+. Read-only access to all switch settings, plus the ability to restart the switch module. TFTP Determine the location of the Trivial File Transfer Protocol (TFTP) servers (as well as the path and file name) to be used for the download configuration file, firmware code file, upload configuration file, and log file. v TFTP server software must be running for TFTP services to work. v For the configuration file that is uploaded to a TFTP server to be saved correctly, you must first save switch module configurations to non-volatile random access memory (NVRAM). v Before the switch can upload its history log file to the TFTP server, an empty history log file must exist on the TFTP server. Virtual LANs Virtual LANs (VLANs) allow multiple blade servers to be part of a logical group and prevent other servers that do not belong to a given group from gaining direct access to the group resources and data. The BladeCenter Ethernet switches can append a 4-byte VLAN tag to incoming frames on a per-port basis, and use the tag on certain frames to permit or block access to those frames at other ports. VLAN traffic can be restricted to a single BladeCenter T unit or can extend across multiple BladeCenter T units. When VLANs are extended across multiple BladeCenter T units, intermediate switches use the VLAN tag to block frames from nonmember destinations. When defining VLANs that span a chassis, consider the following points: v Blade server ports that are in the same VLAN must have the same VLAN ID. v Define the same VLAN ID on both Ethernet switches for blade servers that use both switches to connect to the same external network. v Ethernet switch ports used to span multiple BladeCenter T units must be configured as Tagged, with a specific default VLAN ID for any untagged packets. v The external ports and Link Aggregation Groups (LAGs) must be members of all VLANs that span multiple BladeCenter T units. v The intermediate network device that interconnects the BladeCenter T units must be configured to handle tagged VLAN packets for all applicable VLAN traffic that should be passed through the device. The BladeCenter T unit default VLAN ID is 1 and includes all blade servers in the chassis. If multiple VLANs are required, additional VLAN IDs must be configured. Review the following example to understand how VLANs can be configured. VLAN example The example shown in Figure 44 on page 81 defines three VLANs within a single BladeCenter T unit and multiple VLANs extended to multiple BladeCenter T units. Table 23 on page 81 shows the defined VLAN parameters that are set to support this configuration. Outgoing packets for internal blade server ports must be untagged. 80 BladeCenter T Types 8720 and 8730: Planning and Installation 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
–
User.
Read-only
access
to
all
switch
module
settings.
–
User+.
Read-only
access
to
all
switch
settings,
plus
the
ability
to
restart
the
switch
module.
TFTP
Determine
the
location
of
the
Trivial
File
Transfer
Protocol
(TFTP)
servers
(as
well
as
the
path
and
file
name)
to
be
used
for
the
download
configuration
file,
firmware
code
file,
upload
configuration
file,
and
log
file.
v
TFTP
server
software
must
be
running
for
TFTP
services
to
work.
v
For
the
configuration
file
that
is
uploaded
to
a
TFTP
server
to
be
saved
correctly,
you
must
first
save
switch
module
configurations
to
non-volatile
random
access
memory
(NVRAM).
v
Before
the
switch
can
upload
its
history
log
file
to
the
TFTP
server,
an
empty
history
log
file
must
exist
on
the
TFTP
server.
Virtual
LANs
Virtual
LANs
(VLANs)
allow
multiple
blade
servers
to
be
part
of
a
logical
group
and
prevent
other
servers
that
do
not
belong
to
a
given
group
from
gaining
direct
access
to
the
group
resources
and
data.
The
BladeCenter
Ethernet
switches
can
append
a
4-byte
VLAN
tag
to
incoming
frames
on
a
per-port
basis,
and
use
the
tag
on
certain
frames
to
permit
or
block
access
to
those
frames
at
other
ports.
VLAN
traffic
can
be
restricted
to
a
single
BladeCenter
T
unit
or
can
extend
across
multiple
BladeCenter
T
units.
When
VLANs
are
extended
across
multiple
BladeCenter
T
units,
intermediate
switches
use
the
VLAN
tag
to
block
frames
from
nonmember
destinations.
When
defining
VLANs
that
span
a
chassis,
consider
the
following
points:
v
Blade
server
ports
that
are
in
the
same
VLAN
must
have
the
same
VLAN
ID.
v
Define
the
same
VLAN
ID
on
both
Ethernet
switches
for
blade
servers
that
use
both
switches
to
connect
to
the
same
external
network.
v
Ethernet
switch
ports
used
to
span
multiple
BladeCenter
T
units
must
be
configured
as
Tagged
,
with
a
specific
default
VLAN
ID
for
any
untagged
packets.
v
The
external
ports
and
Link
Aggregation
Groups
(LAGs)
must
be
members
of
all
VLANs
that
span
multiple
BladeCenter
T
units.
v
The
intermediate
network
device
that
interconnects
the
BladeCenter
T
units
must
be
configured
to
handle
tagged
VLAN
packets
for
all
applicable
VLAN
traffic
that
should
be
passed
through
the
device.
The
BladeCenter
T
unit
default
VLAN
ID
is
1
and
includes
all
blade
servers
in
the
chassis.
If
multiple
VLANs
are
required,
additional
VLAN
IDs
must
be
configured.
Review
the
following
example
to
understand
how
VLANs
can
be
configured.
VLAN
example
The
example
shown
in
Figure
44
on
page
81
defines
three
VLANs
within
a
single
BladeCenter
T
unit
and
multiple
VLANs
extended
to
multiple
BladeCenter
T
units.
Table
23
on
page
81
shows
the
defined
VLAN
parameters
that
are
set
to
support
this
configuration.
Outgoing
packets
for
internal
blade
server
ports
must
be
untagged.
80
BladeCenter
T
Types
8720
and
8730:
Planning
and
Installation
Guide