IBM 26R0881 User Guide - Page 55

Reference

Page 55 highlights

Chapter 7. Reference This section provides reference information for OFM, including accessibility, the CLI command and events. BladeCenter Open Fabric Manager components The OFM configuration file and AMM Web interface are essential for OFM functionality. Configuration file The OFM configuration file is the central tool for managing the OFM domain and contains the definitions that you need for a domain of up to 100 BladeCenters. You can generate it automatically, save it and edit it to conform to the needs of a specific domain and then apply it to the domain. You also have the option of creating your own configuration file. The configuration file is a Comma Separated Value (CSV) file. Each non-blank and non-comment line defines a single entity within a domain of BladeCenters. The entities currently defined are BladeCenters, Slots and Port Entries, where a port is a single network device within a slot, which can have multiple definitions - one for each interface type. The file is organized hierarchically by BladeCenters, Slots and Ports, with ample comment lines included to act as a guide to editing the file if needed. IBM recommends that you maintain the original structure as much as possible in order to retain the readability of the file. For certain purposes it might be appropriate to extract a smaller section of the domain into a new file so that you can update a particular BladeCenter or a particular blade individually. To view an example of a configuration file, see "Example: Configuration file" on page 48. Comments section There are two types of comments: line comments and field comments. // this is a line comment localhost/# this is a field comment ,bladecenter ,apply Line comments start with two slashes (//). The system ignores anything between this symbol and the end of the line. You can insert line comments anywhere in the file. However, inserting a comment inside a pair of quote marks results in a No closing quote error. You can insert field comments in any field. Field comments start with a slash-hash (/#). The system ignores anything between this symbol and the end of the field. Inserting a field comment inside a pair of quotes does not cause an error. Comments are included in the maximum line-length (currently 512 bytes including newlines). Very long comments should be broken over several lines to improve readability and to prevent exceeding the line-length limit. If you exceed the line-length limit, the system issues the following error: Input line is too long. © Copyright IBM Corp. 2007, 2008 43

  • 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

Chapter
7.
Reference
This
section
provides
reference
information
for
OFM,
including
accessibility,
the
CLI
command
and
events.
BladeCenter
Open
Fabric
Manager
components
The
OFM
configuration
file
and
AMM
Web
interface
are
essential
for
OFM
functionality.
Configuration
file
The
OFM
configuration
file
is
the
central
tool
for
managing
the
OFM
domain
and
contains
the
definitions
that
you
need
for
a
domain
of
up
to
100
BladeCenters.
You
can
generate
it
automatically,
save
it
and
edit
it
to
conform
to
the
needs
of
a
specific
domain
and
then
apply
it
to
the
domain.
You
also
have
the
option
of
creating
your
own
configuration
file.
The
configuration
file
is
a
Comma
Separated
Value
(CSV)
file.
Each
non-blank
and
non-comment
line
defines
a
single
entity
within
a
domain
of
BladeCenters.
The
entities
currently
defined
are
BladeCenters
,
Slots
and
Port
Entries
,
where
a
port
is
a
single
network
device
within
a
slot,
which
can
have
multiple
definitions
one
for
each
interface
type.
The
file
is
organized
hierarchically
by
BladeCenters,
Slots
and
Ports,
with
ample
comment
lines
included
to
act
as
a
guide
to
editing
the
file
if
needed.
IBM
recommends
that
you
maintain
the
original
structure
as
much
as
possible
in
order
to
retain
the
readability
of
the
file.
For
certain
purposes
it
might
be
appropriate
to
extract
a
smaller
section
of
the
domain
into
a
new
file
so
that
you
can
update
a
particular
BladeCenter
or
a
particular
blade
individually.
To
view
an
example
of
a
configuration
file,
see
“Example:
Configuration
file”
on
page
48.
Comments
section
There
are
two
types
of
comments:
line
comments
and
field
comments
.
//
this
is
a
line
comment
localhost/#
this
is
a
field
comment
,bladecenter
,apply
Line
comments
start
with
two
slashes
(//).
The
system
ignores
anything
between
this
symbol
and
the
end
of
the
line.
You
can
insert
line
comments
anywhere
in
the
file.
However,
inserting
a
comment
inside
a
pair
of
quote
marks
results
in
a
No
closing
quote
error.
You
can
insert
field
comments
in
any
field.
Field
comments
start
with
a
slash-hash
(/#).
The
system
ignores
anything
between
this
symbol
and
the
end
of
the
field.
Inserting
a
field
comment
inside
a
pair
of
quotes
does
not
cause
an
error.
Comments
are
included
in
the
maximum
line-length
(currently
512
bytes
including
newlines).
Very
long
comments
should
be
broken
over
several
lines
to
improve
readability
and
to
prevent
exceeding
the
line-length
limit.
If
you
exceed
the
line-length
limit,
the
system
issues
the
following
error:
Input
line
is
too
long
.
©
Copyright
IBM
Corp.
2007,
2008
43