Clearing The Ivr Zone Database; Configuring Ivr Using Read-Only Zoning; System Image Downgrading Considerations; Database Merge Guidelines - Cisco AP775A - Nexus Converged Network Switch 5010 Configuration Manual

Chapter 29 Configuring Inter-VSAN Routing
S e n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a c k - d o c @ c i s c o . c o m
Click a zone or zone set in the left pane.
Step 2
Choose Edit > Rename.
Step 3
An edit box appears around the zone or zone set name.
Enter a new name.
Step 4
Click Activate or Commit Changes.
Step 5

Clearing the IVR Zone Database

Clearing a zone set only erases the configured zone database, not the active zone database.
To clear the IVR zone database, refer to the Cisco MDS 9000 CLI Configuration Guide.

Configuring IVR Using Read-Only Zoning

Read-only zoning (with or without LUNs) can be used between members of active IVR zones. To
configure this service, you must create and activate read-only zones between the desired IVR zone
members in all relevant edge VSANs using the zoning interface.
Read-only zoning cannot be configured in an IVR zone set setup.
Note

System Image Downgrading Considerations

As of Cisco MDS SAN-OS Release 3.0(3), you can configure 8000 IVR zones and 20,000 IVR zone
members. If you want to downgrade to a release prior to Cisco SAN-OS Release 3.0(3), the number of
IVR zones cannot exceed 2000 and the number of IVR zone members cannot exceed 10,000.

Database Merge Guidelines

A database merge refers to a union of the configuration database and static (unlearned) entries in the
active database. See the
•
OL-17256-03, Cisco MDS NX-OS Release 4.x
"CFS Merge Support" section on page 13-9
Be aware of the following conditions when merging two IVR fabrics:
– The IVR configurations are merged even if two fabrics contain different configurations.
If dissimilar zones exist in two merged fabrics, the zone from each fabric is cloned in the
–
distributed zone set with appropriate names (see Figure 29-25).
Cisco MDS 9000 Family Fabric Manager Configuration Guide
Database Merge Guidelines
for detailed concepts.
29-31