When a compute node is powered off for an extended period of time, a week or longer, the LSI BIOS may stop because of a battery error, waiting for the user to press a key in order to continue.

Workaround: Wait for approximately 10 minutes to confirm that the compute node is stuck in boot. Use the Reprovision button in the Oracle PCA Dashboard to reboot the server and restart the provisioning process.

Bug 16985965

If the Oracle PCA needs to be powered down and restarted for maintenance or in the event of a power failure, the components should come back up in this order: first networking, then storage, and then the management and compute nodes. For detailed instructions to bring the appliance offline and return it to operation, refer to the section Powering Down Oracle Private Cloud Appliance in the Oracle Private Cloud Appliance Administrator's Guide.

It may occur that the management nodes complete their boot sequence before the appliance network configuration is up. In that case, the management nodes are unreachable because their bond0 and bond2 interfaces are down.

Workaround: Reboot the management nodes again. When they come back online, their network interfaces should be correctly configured.

Bug 17648454

Do not connect port 24 of both internal Oracle Switch ES1-24 Ethernet switches to the next-level switch of your data center network. This causes spanning tree issues and provisioning failures. Only one IP address in this appliance management network range is available for customer use: 192.168.4.254. Make sure that the upstream network is configured to protect the appliance management network against DHCP leaks.

The upstream link from an Oracle Switch ES1-24 may only be used for out-of-band management of the Oracle PCA. It must never be used as a data path for virtual machines.

Workaround: Connect only one Oracle Switch ES1-24 (port 24) to the next-level data center switch. If provisioning failures have occurred, reprovision the affected compute nodes.

Bug 21554535

The Oracle PCA Release 2.0.2 software contains firmware upgrades for a number of appliance hardware components. If you are using a base rack with Sun Server X3-2 management nodes and Sun ZFS Storage Appliance 7320, the firmware upgrade is likely to cause storage connectivity issues.

Workaround: Make sure that the Release 2.0.2 software is installed on the management nodes before you upgrade the ZFS storage appliance firmware.

Bug 20319302

During the controller software update to Release 2.1.1 an automated firmware upgrade takes place on the ZFS Storage Appliance. This upgrade, and the network configuration of the storage appliance, could fail if there is another user or process taking control of the console. Also, it has been observed that the text strings passed in the Pexpect commands sometimes have wrong or missing characters, which result in configuration errors.

Workaround: Make sure that there is no other activity on the ZFS Storage Appliance console, and that any external backup activity is suspended for the duration of the software update and firmware upgrade. If the firmware upgrade fails, retrying the same procedure could resolve the problem.

Bug 22269393

Most Oracle PCA components are equipped with an Oracle Integrated Lights Out Manager (ILOM). Each ILOM Service Processor (SP) contains its own clock, which is synchronized with the operating system (OS) clock before it leaves the factory. However, when new expansion nodes are installed or when parts in a component have been repaired or replaced, SP clocks could be out-of-sync. The problem may also be the result of a configuration error or normal clock drift.

If necessary, the SP clock can be synchronized manually. There is no need to continually update the hardware clock, because it only serves as a reference point for the host OS. Once the systems are up and running the OS obtains the correct time through NTP.

Workaround: After configuring the NTP server in the Oracle PCA Dashboard, synchronize the ILOM SPs with the OS clock. The easiest way is to log into the host and run this command: hwclock --systohc.

Bug 17664050

After the upgrade of the Oracle Switch ES1-24 firmware to version 1.3.1.7 the switch configuration can only be partially restored. The problem is caused by a bug in this particular version of the switch firmware. The following error message is output: "Load partially successful, please view the event log". The event log contains entries like the ones shown in the example below:

23764  Tue May 19 14:14:43 2015  Restore   Log       major
Config restore: Unable to restore property '/SP/clients/tacacs+/alternate servers/2/port' (Invalid port).
23763  Tue May 19 14:14:43 2015  Restore   Log        major
Config restore: Unable to restore property '/SP/clients/tacacs+/alternate servers/1/port' (Invalid port).

Workaround: Until a fix is available for the firmware bug, you should set up port numbers for the TACACS+ alternate servers of the Oracle Switch ES1-24. When these ports are configured, the switch configuration restore operation completes successfully.

Bug 21114405