IBM 26R0881 User Guide - Page 63

command, Events

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

Page 63 highlights

CLI command You can apply a new configuration using the bofm CLI command. To use the command, you must have a tftp server available for uploading the configuration file. Format bofm -d [on|off] | -i |-l | -p [on|off] | -v Options -d: check duplicate [on|off] -i: ip of tftp server -l: configuration file name -p: check blade power state [on|off] -v: verbose mode Usage You will need to supply the tftp server IP address in the -i option, and the configuration file name in the -l (similar to the update CLI command). Adding the -d off option will cause OFM to ignore duplicate addresses in the configuration file. Adding the -p off option causes the OFM to apply the configuration even on powered-on blades. These parameters default to ″on″. Events There are a few OFM-related events: 1. If the OFM configuration changes for a slot, then an information event is generated for that slot. 2. If a slot has OFM configuration enabled and the system management processor of the blade in that slot does not support OFM, then a warning event is generated. 3. If a slot has OFM configuration enabled and the blade's BIOS in that slot does not support OFM, then a warning event is generated. 4. If a slot has OFM configuration enabled and any device in that slot does not support OFM, thean a warning event is generated. 5. If any of the adapters reported a OFM error, then a warning event is generated. 6. If the AMM was unable to apply a OFM configuration to a blade for which the system management processor supports OFM, then the blade is not given power permission and an error event is generated for that blade. 7. If the AMM cleared the OFM configuration after moving to a new chassis, then a warning alert is generated. 8. If the AMM discovered that a OFM configuration is in use by a blade that is powered on and it is different from the configuration defined on the AMM, then a warning event is generated. Chapter 7. Reference 51

  • 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
CLI
command
You
can
apply
a
new
configuration
using
the
bofm
CLI
command.
To
use
the
command,
you
must
have
a
tftp
server
available
for
uploading
the
configuration
file.
Format
bofm
-d
[on|off]
|
-i
<ip>
|-l
<file
name>
|
-p
[on|off]
|
-v
Options
-d:
check
duplicate
[on|off]
-i:
ip
of
tftp
server
-l:
configuration
file
name
-p:
check
blade
power
state
[on|off]
-v:
verbose
mode
Usage
You
will
need
to
supply
the
tftp
server
IP
address
in
the
–i
option,
and
the
configuration
file
name
in
the
–l
(similar
to
the
update
CLI
command).
Adding
the
–d
off
option
will
cause
OFM
to
ignore
duplicate
addresses
in
the
configuration
file.
Adding
the
–p
off
option
causes
the
OFM
to
apply
the
configuration
even
on
powered-on
blades.
These
parameters
default
to
″
on
″
.
Events
There
are
a
few
OFM-related
events:
1.
If
the
OFM
configuration
changes
for
a
slot,
then
an
information
event
is
generated
for
that
slot.
2.
If
a
slot
has
OFM
configuration
enabled
and
the
system
management
processor
of
the
blade
in
that
slot
does
not
support
OFM,
then
a
warning
event
is
generated.
3.
If
a
slot
has
OFM
configuration
enabled
and
the
blade’s
BIOS
in
that
slot
does
not
support
OFM,
then
a
warning
event
is
generated.
4.
If
a
slot
has
OFM
configuration
enabled
and
any
device
in
that
slot
does
not
support
OFM,
thean
a
warning
event
is
generated.
5.
If
any
of
the
adapters
reported
a
OFM
error,
then
a
warning
event
is
generated.
6.
If
the
AMM
was
unable
to
apply
a
OFM
configuration
to
a
blade
for
which
the
system
management
processor
supports
OFM,
then
the
blade
is
not
given
power
permission
and
an
error
event
is
generated
for
that
blade.
7.
If
the
AMM
cleared
the
OFM
configuration
after
moving
to
a
new
chassis,
then
a
warning
alert
is
generated.
8.
If
the
AMM
discovered
that
a
OFM
configuration
is
in
use
by
a
blade
that
is
powered
on
and
it
is
different
from
the
configuration
defined
on
the
AMM,
then
a
warning
event
is
generated.
Chapter
7.
Reference
51