Cisco Systems MDS 9000 Zone-Based Traffic Priority

Send documentation comments to mdsfeedback-doc@cisco.com.
15-20
Cisco MDS 9000 Family Fabric Manager Configuration Guide
OL-6965-03, Cisco MDS SAN-OS Release 2.x
Chapter 15 Zone Configuration
Zone-Based Traffic Priority
Copying a Full Zone Database
You can recover a database by copying the active zone database or the full zone database.
To copy a zone database, follow these steps:
Step 1 From Fabric Manager, choose Zone > Copy Full Zone Database from the Zone menu.
You see the Recover Full Zone Database dialog box.
Step 2 Select the Copy Active or the Copy Full radio button, depending on which type of database you want
to copy.
Step 3 Select the source VSAN from which to copy the information from the drop-down list.
Step 4 If you selected Copy Full, select the source switch and the destination VSAN from those drop-down
lists.
Step 5 Select the destination switch from the drop-down list.
Step 6 Click Copy to copy the database, or click Close to close the dialog box without copying.
Migrating a Non-MDS Database
To use the Zone Migration Wizard to migrate a non-MDS database, follow these steps:
Step 1 From Fabric Manager, choose Zone > Migrate Non-MDS Database from the Zone menu.
You see the Zone Migration Wizard.
Step 2 Follow the prompts in the wizard to migrate the database.
Note All alphanumeric characters or one of the following symbols ($, -, ^, _) are supported.
Zone-Based Traffic Priority
As of Cisco MDS SAN-OS 2.0, the zoning feature provides an additional segregation mechanism to
prioritize select zones in a fabric and set up access control between devices. Using this feature, you can
configure the Quality of Service (QoS) priority as a zone attribute. You can assign the QoS traffic priority
attribute to be high, medium, or low. By default, zones with no specified priority are implicitly assigned
a low priority.
To use this feature, you need to obtain the ENTERPRISE_PKG license and you must enable QoS in the
switch.
This feature allows SAN administrators to configure QoS in terms of a familiar data flow identification
paradigm. You can configure this attribute on a zone-wide basis, rather than between zone members.