ViPR 2.1 - ViPR Inter-VSAN Routing Support with Cisco Switches
Table of Contents
IVR allows separate autonomous VSANs to maintain their own VSAN-wide services and provide the following benefits:
Accesses resources across VSANs without compromising other VSAN benefits.
- Transports data traffic between specific initiators and targets on different VSANs without merging VSANs into a single logical fabric.
- Establishes proper interconnected routes that traverse one or more VSANs across multiple switches. IVR is not limited to VSANs present on a common switch.
- Shares valuable resources across VSANs without compromise. Fibre Channel traffic does not flow between VSANs, nor can initiators access resources across VSANs other than the designated VSAN.
- Provides efficient business continuity or disaster recovery solutions when used in conjunction with FCIP.
- IVR Is in compliance with Fibre Channel standards.
The following figure shows an example of a ViPR-supported datacenter configuration that uses Inter-VSAN routing.
In this example, the IVR switch acts as the router between the devices in VSAN 15 and the devices in VSAN 10. In this simple example, Host 5 in VSAN 10 can consume storage on VNX 1 in VSAN 15.Back to Top
- As a part of the routing setup, at least one IVR zone must be created between each pair of VSANs you expect ViPR to consider. When ViPR discovers the topology, it assumes that if an IVR zone exists between two VSANs, then routing between the VSANs is allowed. If there is no IVR zone between the VSANs, ViPR assumes that routing is not allowed between the VSANs.
- ViPR must successfully discover a switch in each VSAN. From the Admin view, choose to add and discover a Cisco switch.
- ViPR must also discover the IVR-enabled switches that enable routing between ViPR managed VSANs in your data center.
Refer to the Cisco MDS 9000 Family NX-OS Inter-VSAN Routing Configuration Guide for more information on installing and configuring Cisco switches with IVR enabled, and creating IVR zones.Back to Top
- Cisco switches and Brocade CMCNE management stations are called fabric managers in the user interface.
- In the ViPR REST API and the ViPR CLI, Brocade CMCNE management stations and Cisco switches are called network-systems. Cisco VSANs and Brocade fabrics are called networks.