|
|
|
6913602
|
Oracle ILOM Fails to Read DIMM FRU Information When
Host Is On
|
|
Issue:
When configured for sideband (SB) network port sharing, in-chip connectivity
between the service processor (SP) and the host OS is not supported by the
on-board host Gigabit Ethernet controller.
|
|
Affected software:
|
|
Workaround:
Power off the host before setting
reset_to_defaults=factory, then reboot the
SP.
|
|
6779289
|
In-Chip Connectivity Between the SP and the Host OS Is
Not Supported When Using Sideband Network Port Sharing
|
|
Issue:
When configured for sideband (SB) network port sharing, in-chip connectivity
between the service processor (SP) and the host OS is not supported by the
on-board host Gigabit Ethernet controller.
|
|
Affected software:
|
|
Workaround:
Use a different port or route to transmit traffic between the source and
destination targets instead of using L2 bridging/switching.
|
|
6795975
|
When Multiple Oracle ILOM Remote Console Sessions Are
Open on the Same SP, the KVMS Interface Might Not Work
|
|
Issue:
When multiple Oracle ILOM Remote Console sessions are opened to the same
service processor (SP), the additional session's keyboard interface might not
work. The first session's keyboard interface is not affected.
|
|
Affected software:
|
|
Workaround:
-
Double-click in the Oracle ILOM Remote Console dialog to activate the
mouse, then move the mouse.
OR
-
In the Oracle ILOM Remote Console menu bar, select Devices → Mouse,
then move the mouse.
|
|
6800702 6813782
|
64-bit JRE Fails to Launch the Oracle ILOM Remote
Console
|
|
Issue:
An attempt to start Storage Redirection in Oracle ILOM might fail when using a
64-bit Java runtime environment (JRE). Since the 64-bit JRE is the default on a
64-bit system, you might need to download a 32-bit JRE. When using a 64-bit JRE to
start storage redirection, an "Unsupported platform" error will appear.
|
|
Affected software:
|
|
Workaround:
|
|
6873660
|
Property
write_cache
Is Not Available on Oracle ILOM
SP
|
|
Issue:
Certain controllers (for example, Adaptec) enable the user to configure a RAID
with the Write_Cache parameter set to predefined values. Irrespective of what this
parameter is set to, this property is not available to the user from the Oracle
ILOM SP command-line interface (CLI). Ideally this property would reside under
/STORAGE/raid/controller#/raid_id#/. Currently
the Adaptec SDK does not provide this data.
|
|
Affected operating systems and
software:
-
Solaris 10 05/09, RHEL 4.8 and 5.3, SLES 10 SP2, SLES 11, and VMware ESX
3.5 U4
-
Supplemental Release 2.1 through 2.8.1
|
|
Workaround:
There is no workaround. Check for the availability of an update.
|
|
6875715
|
Property
max-disks
Is Always Incorrectly Set to 0 on Oracle ILOM
SP
|
|
Issue:
The maximum number of disks that a controller supports is a property of that
controller and should be available as part of the Storage Viewer functionality
under /STORAGE/raid/controller# on the Oracle
ILOM command-line interface (CLI). Currently this property value is always set to
0.
|
|
Affected operating systems and
software:
-
Solaris 10 05/09, RHEL 4.8 and 5.3, SLES 10 SP2, SLES 11, and VMware ESX
3.5 Update 4
-
Supplemental Releases 1.0 through 2.8.1
|
|
Workaround:
There is no workaround. Check for the availability of an update.
|
|
6877654
|
Property
raid_global_hotspare
Does Not Display the Correct Information for Certain
Controllers and Operating Systems on the Oracle ILOM SP
|
|
Issue:
When a RAID is configured to have a global hotspare using the Adaptec
Configuration, the corresponding raid_global_hotspare parameter in Oracle ILOM SP
command-line interface (CLI) does not indicate that information. Instead the
raid_dedicated_hotspare parameter is displayed as true.
|
|
Affected operating systems and
software:
-
Solaris 10 05/09, RHEL 4.8 and 5.3, SLES 10 SP2, SLES 11, and VMware ESX
3.5 U4
-
Supplemental Releases 1.0 through 2.8.1
|
|
Workaround:
There is no workaround. Check for the availability of an update.
|
|
6882835 6884652
|
Power Management Budget Is Not Supported on RHEL 4.7,
5.3, or 5.4
|
|
Issue:
Multiple issues occur if you try to use the Power Budget feature of Power
Management on servers running Red Hat Enterprise Linux (RHEL) 4.7, 5.3, or 5.4.
These issues can lead to configured power budgets being exceeded or lower than
expected CPU performance.
|
|
Affected operating systems and
software:
-
Red Hat Enterprise Linux (RHEL) 4.7, 5.3, 5.4
-
Supplemental Releases 2.1 through 2.8.1
|
|
Workaround:
Do not use the Power Budget feature when running Red Hat Enterprise Linux
(RHEL) 4.7, 5.3, or 5.4.
|