HP Cisco Nexus 5000 Cisco Nexus 5000 Series Switch CLI Software Configuration - Page 535

Chapter 38 Configuring and Managing Zones Enhanced Zoning Send feedback to [email protected] • Modifying the Zone Database, page 38-21 • Releasing Zone Database Locks, page 38-21 • Merging the Database, page 38-22 • Configuring Zone Merge Control Policies, page 38-23 • Default Zone Policies, page 38-23 • Configuring System Default Zoning Settings, page 38-23 • Verifying Enhanced Zone Information, page 38-24 About Enhanced Zoning Table 38-4 lists the advantages of the enhanced zoning feature in all switches in the Cisco Nexus 5000 Series. Table 38-4 Advantages of Enhanced Zoning Basic Zoning Enhanced Zoning Enhanced Zoning Advantages Administrators can make simultaneous configuration changes. Upon activation, one administrator can overwrite another administrator's changes. Performs all configurations within a single configuration session. When you begin a session, the switch locks the entire fabric to implement the change. One configuration session for the entire fabric to ensure consistency within the fabric. If a zone is part of multiple zone sets, you create an instance of this zone in each zone set References to the zone are used by the zone sets as required once you define the zone. Reduced payload size as the zone is referenced. The size is more pronounced with bigger databases. The default zone policy is defined per switch. To Enforces and exchanges the default ensure smooth fabric operation, all switches in the zone setting throughout the fabric. fabric must have the same default zone setting. Fabric-wide policy enforcement reduces troubleshooting time. To retrieve the results of the activation on a per switch basis, the managing switch provides a combined status about the activation. It does not identify the failure switch. Retrieves the activation results and the Enhanced error reporting nature of the problem from each remote eases the troubleshooting switch. process To distribute the zoning database, you must reactivate the same zone set. The reactivation may affect hardware changes for hard zoning on the local switch and on remote switches. Implements changes to the zoning database and distributes it without reactivation. Distribution of zone sets without activation avoids hardware changes for hard zoning in the switches. The Cisco-specific zone member types (symbolic node name, and other types) may be used by other non-Cisco switches. During a merge, the Cisco-specific types can be misunderstood by the non-Cisco switches. Provides a vendor ID along with a Unique vendor type. vendor-specific type value to uniquely identify a member type. The fWWN-based zone membership is only supported in Cisco interop mode. Supports fWWN-based membership in The fWWN-based member the standard interop mode (interop type is standardized. mode 1). OL-16597-01 Cisco Nexus 5000 Series Switch CLI Software Configuration Guide 38-19