ViPR 2.2 - ViPR Inter-VSAN Routing Support with Cisco Switches

Table of Contents

ViPR support for Inter-VSAN Routing with Cisco switches

ViPR includes support for Inter-VSAN Routing (IVR) configurations using Cisco switches. IVR is designed to allow hosts, storage arrays and other devices residing in separate VSANs to communicate without merging the VSANs.

IVR allows separate autonomous VSANs to maintain their own VSAN-wide services and provide the following benefits:

The following figure shows an example of a ViPR-supported datacenter configuration that uses Inter-VSAN routing.

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

Inter-VSAN Routing configuration requirements

The following guidelines apply to all fibre channel routing configurations.

  • For each VSAN, ViPR must successfully discover the Fabric Manager (Cisco switch). Refer to Configure and Add a Cisco Switch to ViPR for the prerequisite information for configuring a Cisco switch for ViPR, and the steps to add the switch, which will be discovered by ViPR.
  • 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 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

ViPR switch and network terminology

ViPR has three external interfaces - a REST API, a Command Line Interface (CLI), and a User Interface. The scripting and programming interfaces (API and CLI) use slightly different terminology to refer to the network elements of your Storage Area Network.

The terminology used in each ViPR Interface is as follows:
  • 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.
Back to Top

Supported Cisco revisions

Refer to the EMC ViPR Support Matrix for a complete list of supported Cisco switches and firmware revisions.

Back to Top