Considerations For Zoning Architecture; Table 54 Considerations For Zoning Architecture - HP StoreFabric SN6500B Administrator's Manual

Fabric os administrator's guide, 7.1.0 (53-1002745-02, march 2013)
Hide thumbs Also See for StoreFabric SN6500B:
Table of Contents

Advertisement

Identifying the enforced zone type
Use the following procedure to identify zones and zone types:
1. Connect to the switch and log in using an account with admin permissions.
2. Enter the portZoneShow command, using the following syntax:

Considerations for zoning architecture

Table 54
TABLE 54
Item
Type of zoning
enforcement: frame-
or session-based
Use of aliases
Effect of changes in a
production fabric
Testing
Confirming operation
Zoning can be implemented and administered from any switch in the fabric, although it is
recommended that you use a switch running the latest Fabric OS version.
The zone configuration is managed on a fabric basis. When a change in the configuration is saved,
enabled, or disabled according to the transactional model, it is automatically (by closing the
transaction) distributed to all switches in the fabric, preventing a single point of failure for zone
information.
NOTE
Zoning commands make changes that affect the entire fabric. When executing fabric-level
configuration tasks, allow time for the changes to propagate across the fabric before executing any
subsequent commands. For a large fabric, you should wait several minutes between commands.
Fabric OS Administrator's Guide
53-1002745-02
portzoneshow
lists considerations for zoning architecture.
Considerations for zoning architecture
Description
If security is a priority, frame-based hardware enforcement is recommended. The best way
to do this is to use WWN identification exclusively for all zoning configurations.
The use of aliases is optional with zoning. Using aliases requires structure when defining
zones. Aliases aid administrators of zoned fabrics in understanding the structure and
context.
Zone changes in a production fabric can result in a disruption of I/O under conditions
when an RSCN is issued because of the zone change and the HBA is unable to process the
RSCN fast enough. Although RSCNs are a normal part of a functioning SAN, the pause in
I/O might not be acceptable. For these reasons, you should perform zone changes only
when the resulting behavior is predictable and acceptable. Ensuring that the HBA drivers
are current can shorten the response time in relation to the RSCN.
Before implementing a new zone, you should run the Zone Analyzer from Web Tools to
isolate any possible problems. This is especially useful as fabrics increase in size.
After changing or enabling a zone configuration, you should confirm that the nodes and
storage can identify and access one another. Depending on the platform, you might need
to reboot one or more nodes in the fabric with the new changes.
11
Zoning overview
309

Hide quick links:

Advertisement

Table of Contents
loading

This manual is also suitable for:

Fabric os 7.1.0

Table of Contents