|
|
|
24673478
|
A direct firmware upgrade from 1.3 to 2.1.7, 2.1.8, or 2.1.9
fails.
|
Upgrading a gateway switch directly from 1.3 to 2.1.7 or later
fails.
Workaround: Perform a firmware
upgrade from 1.3 to 2.1.6, and then upgrade to 2.1.7, 2.1.8, or
2.1.9.
|
22195180
|
Firmware upgrade from 2.1.8 to 2.1.8 without
–force option causes fwverify
command to fail.
|
When reinstalling firmware 2.1.7, 2.1.8, or 2.1.9, neither as an
upgrade or a downgrade, the process completes without errors.
However, the fwverify command indicates that the
installation has failed.
|
20714591
|
All Subnet Managers segfault at 54 ip 080ba543 sp
xxxxxxxx
error 4 displayed.
|
An InfiniBand fabric that is not a pure Fat Tree topology might
experience a segmentation fault across all Subnet Managers in the
fabric. This can occur when cabling or decabling an active gateway
or switch configured for Fat Tree topology, as the actual topology
at that instant is not pure Fat Tree.
Workaround: Either use the
setsmrouting command to set the Subnet
Managers to Min Hop routing, or ensure a pure Fat Tree topology and
power off the gateway before cabling or decabling it. See Replace a Gateway.
|
20649071
|
Fabric Director is filling up the gateway root file system.
|
If the hostname of a management controller exceeds 26 characters,
the Fabric Director incessantly writes errors to the log file which
can fill the root filesystem if left unchecked.
Workaround: Do not use more
than 26 characters for the hostname of the management
controller.
Note -
The maximum number of characters for the node description
field is 17.
|
18129290
|
smpartition command fails from firmware version
2.0 switch with firmware version 2.1 peer.
|
In a mixed firmware fabric where the master Subnet Manager is on a
gateway with firmware version 2.0 and other gateways or switches in
the fabric are firmware version 2.1, issuing the
smpartition commit command fails.
Workaround: When you use the
smpartition commands to partition the mixed
firmware fabric, issue the commands from a master Subnet Manager on
a switch or gateway with firmware version 2.1.
|
17408412
|
connector command not fully functional from
Fabric_Mgmt restricted shell.
|
When the –info or –dump options of the
connector command are issued in the
Fabric_Mgmt,
Gateway_Mgmt, or
Switch_Diag restricted shells, the
command fails.
Workaround: Use the Fabric
Monitor feature of the Oracle ILOM web interface to retrieve
connector information.
|
17159243
|
VNICs with MAC addresses having eight leading zeros are disabled
after a reboot.
|
VNICs with MAC addresses having four or more leading bytes which
are zero (00:00:00:00:12:34) are not persistent after a reboot,
including reboots that occur during a firmware downgrade or
upgrade.
Workaround: Do not create VNICs
with MAC addresses having four or more leading bytes which are zero
(eight or more leading zeros).
|
16847481
|
Setting time zone changes permissions of time zone file.
|
After setting the time zone, the permissions of the time zone file
are changed and must be reset to their original values. Otherwise,
the fwverify command returns an error.
Workaround: Change the
permissions on the time zone file.
-
After setting the time zone, become the
root user.
-
Set the permissions for the time zone file.
#
chmod 644 /conf/localtime
|
15755727
|
Need tool to display InfiniBand topology with physical InfiniBand
entities.
|
At present, no command provides the relationship of InfiniBand
fabric GUIDs, LIDs, and IB ports to each other in a simplified
manner.
Workaround: Use the
ibnetdiscover command.
|
15703751
|
No way to set Fabric Monitor console timeout.
|
The Fabric Monitor will timeout after 15 minutes of idle
time.
Workaround: You must log in to
the web interface and start the Fabric Monitor again.
|
15560533
|
Setting an alert rule to ipmipet sometimes does
not work.
|
There is no impact to the InfiniBand fabric.
Workaround: After setting the
alert rule to ipmipet, set the level to
disable, and then set the level to the
desired value.
|