Skip Navigation Links
Exit Print View
| SPARC T3-1 Server ### Product Notes

Search Scope:

- This Document
- Entire Library

## Disk Zoning Rules for Backplanes With Sixteen-Disk Capacity

If your SPARC T3-1 server has a sixteen-disk capacity backplane and uses the onboard SAS-2 controllers to manage the disks, you must apply patch 147034-01 to the LSI firmware on the disk backplane.

| Caution - Be certain to back up any data stored on the disks before you apply the patch. You can restore the files after the patch is applied.

Patch 147034-01 causes the backplane to be partitioned into two disk zones, which have the following characteristics:

- Zone A consists of backplane slots 0 through 7. Disks in zone A are managed exclusively by onboard SAS-2 controller 0. They are visible only to each other and to controller 0. Disks in zone A are not visible to any devices in zone B.

- Zone B consists of backplane slots 8 through 15. Disks in zone B are managed exclusively by onboard SAS-2 controller 1. They are visible only to each other and to controller 1. Disks in zone B not visible to any devices in zone A.

Note - When zoning is enabled, `devalias` for slots 8-15 will be incorrect unless the system firmware is updated to either 8.0.5.b (or a higher 8.0 level) or to 8.1.0 (or higher). See Minimum System Firmware for Valid `devalias` in Upper Disk Locations for more information.

These disk zone definitions are persistent. Their configuration cannot be modified and they remain in effect across power cycles and reboot operations. They must be active whenever the SAS-2 onboard controllers are used to manage disks in a sixteen-disk capable backplane.

However, if you use an internal PCIe RAID HBA instead of the onboard SAS-2 controllers, you must disable disk zoning. You do this with the following command:

    # zoningcli disable zoning

The `zoningcli` command is contained in versions 2.1.1 and 2.2 of the Oracle Hardware Management Pack. See Oracle Hardware Management Pack 2.1.1 and 2.2 Support SPARC Platforms for more information.

The `zoningcli` command syntax also supports an `enable` subcommand, which you can use to re-enable disk zones A and B if they are ever disabled. For example, this step would be necessary if you remove an internal PCIe RAID HBA card and return control of the disks to the onboard SAS-2 controllers.

Because the zones are logically isolated from each other, RAID volumes created by controller 0 are restricted to disks in zone A. Likewise, RAID volumes created by controller 1 are restricted to disks in zone B.

Each onboard SAS-2 controller can create up to two hardware RAID volumes. That is, the maximum number of RAID volumes per disk zone is two.

Copyright © 2010, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |