v
Communication
error
to
the
blade
or
user
doesn’t
have
permission
for
OFM
on
a
blade.
v
HBA
firmware
needs
to
be
upgraded
to
support
OFM.
Parsing
errors
This
table
contains
a
list
of
the
parsing
errors
that
can
be
generated
when
processing
the
OFM
configuration
file,
with
an
explanation
of
the
cause
of
each
error.
Table
11.
Parsing
errors
Error
message
Description
Assuming
boot
type
`None`
The
“Boot
Type”
field
has
been
left
empty
–
the
system
will
assume
a
value
of
“none”
and
continue
processing
the
line.
Assuming
mode
`Ignore`
The
“Mode”
field
has
been
left
empty
–
the
system
will
assume
a
value
of
“Ignore”
and
continue
processing.
Attempt
to
add
multiple
boot
targets
to
a
blade
with
the
same
priority
A
single
priority
value
for
a
target
can
only
be
used
once
for
a
given
slot.
Attempt
to
redefine
slot
There
are
multiple
lines
defining
a
slot.
A
slot
must
be
defined
before
it
is
used
and
cannot
be
defined
more
than
once.
Attempt
to
use
a
slot
that
has
not
yet
been
defined
A
slot
must
be
defined
before
it
used.
The
OFM
configuration
file
contains
a
reference
to
a
slot
that
has
not
been
defined
when
referenced.
Attempt
to
write
non-Ethernet
data
to
Ethernet
port
The
OFM
configuration
file
includes
an
attempt
to
define
a
non-Ethernet
port
to
an
Ethernet-only
port
number
(1
or
2).
Bad
boot
type
The
“Boot
type”
string
cannot
be
parsed.
Bad
entry
type
The
entry
type
(One
of:
BladeCenter,
Slot,
Eth,
FC,
FCTarget)
was
not
recognized.
Bad
IP
address
The
IP
address
was
incorrectly
formed
or,
in
the
case
of
a
hostname,
the
DNS
lookup
failed.
Bad
offset
number
Cannot
parse
the
offset
number,
or
the
number
is
out
of
range.
(Offsets
must
be
in
the
range
0-3)
Bad
port
number
Cannot
parse
the
port
number,
or
the
number
is
out
of
range.
(Ports
must
be
in
the
range
1-8
for
Ethernet
ports
or
3-8
for
all
other
types)
Bad
slot
number
Cannot
correctly
parse
the
slot
number
or
it
is
out
of
range.
The
exact
range
depends
on
the
BladeCenter
type
(BCH,
BCS,
BCHT),
but
is
never
less
than
1
or
more
than
14.
This
error
can
also
occur
when
the
slot
field
does
not
have
a
closing
comma.
Bad
target
priority
-
must
be
first
or
second
Cannot
parse
the
target
priority,
or
it
was
out
of
range
(first/second).
Targets
can
only
be
set
as
the
first
or
second
priority.
Chapter
6.
Troubleshooting
35
Summary of Contents for 26R0881
Page 1: ...IBM Systems IBM BladeCenter Open Fabric Manager Installation and User s Guide Version 2 1...
Page 2: ......
Page 3: ...IBM Systems IBM BladeCenter Open Fabric Manager Installation and User s Guide Version 2 1...
Page 6: ...iv IBM BladeCenter Open Fabric Manager Installation and User s Guide...
Page 8: ...vi IBM BladeCenter Open Fabric Manager Installation and User s Guide...
Page 10: ...viii IBM BladeCenter Open Fabric Manager Installation and User s Guide...
Page 12: ...x IBM BladeCenter Open Fabric Manager Installation and User s Guide...
Page 26: ...14 IBM BladeCenter Open Fabric Manager Installation and User s Guide...
Page 64: ...52 IBM BladeCenter Open Fabric Manager Installation and User s Guide...
Page 70: ...58 IBM BladeCenter Open Fabric Manager Installation and User s Guide...
Page 77: ......
Page 78: ...Part Number xxxxxxx Printed in USA 1P P N xxxxxxx...
