ATTO Technology diamond array v Manual Do Utilizador

Página de 117
70
Zones
and edit the Active configuration, use the 
ZoneRetrieve
 command. The information from the 
Active configuration is copied into the Planned 
configuration.
To determine what is in the Planned 
configuration, type 
ZoneInfo Planned
.
Active configuration  
is persistent and establishes 
the Diamond zoning configuration after power-
up.
The Planned configuration becomes the Active 
configuration after successful execution of the 
ZoneCommit 
command. The Active configuration 
is replicated as the Planned configuration after the 
successful 
ZoneCommit
, after power-up and after 
ZoneRetrieve
. This replication eases incremental 
modifications to the current zone configuration: 
you only need to enter changes. Modifications to 
the Planned Configuration made before 
ZoneCommit are not persistent and are lost in the 
case of power-up. 
To determine what is in the Active Configuration, 
type 
ZoneInfo.
Factors to consider
Several factors must be considered when 
configuring a array with zones:
•  You must be careful when changing array 
zoning configurations. Internal validation logic 
cannot detect misconfigurations.
•  The array zoning may be driven by external 
applications which handle considerations such 
as aliasing of parameters. 
•  Stopping or pausing I/O operations during 
zoning changes is the responsibility of the host 
computer, external to the array.
•  You must refer to a device by a consistent LUN 
across zones in accordance with Fibre Channel 
specifications.
•  JBOD/RAID configuration changes require 
planning and preparation independent of 
whether any zones are enabled. Such changes 
affect data integrity, and any write to an incorrect 
LUN may result in data corruption.
•  Degraded operation and RAID rebuilding occur 
at a lower level than the Zoning features. SCSI 
command operation continues to operate, and 
you can modify the Zoning configuration via the 
ZoneCommit command at any time.
•  Zone validation of switch/fabric routing is not 
supported. The array operates within a SAN 
environment including host systems, host bus 
adapters, switches and other devices. The 
Operating System you use may limit zoning 
flexibility in your SAN.
•  You may create up to 32 zones. Each zone may 
have up to two ports, up to 24 devices and up to 
32 hosts.
Status and Sense Data
Commands sent to a device may be rejected with sense key, code, qualifier as follows: 
LOGICAL UNIT NOT CONFIGURED: 68 00 00
No such LUN exists; the initiator does not have access 
to this LUN
LOGICAL UNIT NOT SUPPORTED: 25 00 00
The Logical unit is not in an accessible zone
LOGICAL UNIT NOT READY: 04 03 00
The Logical unit is in an accessible zone, but is not 
available; it may be offline or busy
If the logical unit inventory changes for any reason, including completion of initialization, 
removal of a logical unit, or creation of a logical unit, the device server generates a Unit Attention 
command for all initiators, telling them a ZoneCommit procedure has been successful. The device 
server sets the additional sense code to 
REPORTED LUNS DATA HAS CHANGED: 3F 0E 00 (LUN has been added to or removed from the zone)