Cisco MDS 9000 Series Configuration Guide

- Rewrite the following information:
VSAN to 3
Source ID to 550002
Destination ID to 030001
MDS9148S-2 fc1/1(Target1) - VSAN 3
Entry# Source ID Mask Destination ID Mask Action
1 030001(Target1) ffffff 550002(host) ffffff Permit
- Forward to fc1/2
- Rewrite the following information:
VSAN to 2
Source ID to 360002
Destination ID to 210001
2 000000 000000 000000 000000 Drop
Besides the entries in this example, there are other entries that IVR adds to capture important frames such as
PLOGIs, PRILIs, and ABTS.
Note
The programming on the host and target1 ports is similar to the way it is without IVR, except that the FCIDs
and VSANs are explicitly forwarded to an egress port and are rewritten to values that are appropriate for the
transit VSAN (VSAN 2). These forwarding and rewrite entries are separate and are not included in the
TCAM-usage values.
However, now, on the ISLs in both the switches, programming that did not exist earlier is present. When
frames from Host to Target1 are received by Cisco MDS 9148S-2 fc1/2, they are rewritten to the values in
VSAN 3 where the target resides. In the reverse direction, when frames from Target1 to the Host are received
by Cisco MDS 9148S-1 fc1/2, they are rewritten to the values in VSAN 1 where the Host resides. Thus, for
each VSAN transition on an ISL (that typically occurs across a transit VSAN) there will be TCAM programming
for each device in the IVR zone set.
Consequently, most of the best practices followed for the F and TF port channels should be followed to ensure
that TCAM is utilized as efficiently as possible for the following purposes:
Unlike F and TF port-channels, the ACLTCAM programming on ISLs will be the same quantity regardless
if the ISLs are part of a port-channel or not. If there are "n" ISLs between two MDS switches, then it doesn't
matter if they are in one port-channel, two port-channels or just individual links. The ACLTCAM programming
will be the same.
Note
• Distribute port-channel member interfaces into different forwarding engines, especially on fabric switches.
• Distribute member interfaces into different linecards on director-class switches.
• Distribute member interfaces into forwarding engines with lower TCAM zoning region usage.
• Use single-initiator zones, single-target zones, or Smart Zoning.
Cisco MDS 9000 Series Fabric Configuration Guide, Release 8.x
148
Configuring and Managing Zones
E and TE Port Channels and IVR

Cisco MDS 9000 Series Specifications

General

Category	Switch
Operating System	Cisco NX-OS
Ports	Varies by model
Protocols	Fibre Channel (FC), Fibre Channel over IP (FCIP), iSCSI
Redundancy	Redundant supervisors, power supplies, and fans
Management	Cisco Data Center Network Manager (DCNM), CLI, SNMP
Virtualization Support	VSANs (Virtual SANs)
Security Features	Fibre Channel Security Protocol (FC-SP)
Hot Swappable Components	power supplies, fans
Power Supply Options	AC and DC options available