When a compute note 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 Virtual Compute Appliance Dashboard to reboot the server and restart the provisioning process.

Bug 16985965

For VLAN support, the Oracle Fabric Interconnect F1-15 Director Switches are set to trunking mode to allow tagged data traffic. Depending on the design of your data center network and the networking within the Oracle Virtual Compute Appliance environment, you may not be able to connect to systems outside the appliance, even though the outbound network cabling is connected correctly. Your data center switches should be reconfigured to appropriately handle tagged and untagged data traffic from the Oracle Virtual Compute Appliance.

Workaround: Adjust the configuration of your next-level data center switches, by enabling tagged and untagged traffic to share the connection.

Bug 17641780 and 17703144

If the Oracle Virtual Compute Appliance needs to be powered down and restarted for maintenance or in the event of a power failure, bring up the components in this order: first the Oracle Fabric Interconnect F1-15 Director Switches, then the Sun ZFS Storage Appliance 7320 storage heads, and then the management nodes. Wait at least 30 seconds between components.

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