Add Network Systems (Fabric Managers) and SAN Networks to ViPR using the ViPR REST API

TOC

BacktoTop

Overview

This article provides the ViPR support requirements, and prerequisite information to prepare SAN (Brocade and Cisco) switches for ViPR integration using the ViPR REST API. Also includes the steps to add and configure the Fibre Channel (FC) networks in ViPR using the REST API.

This article applies to EMC ViPR 2.0.

A network system for:
  • Cisco = MDS switch
  • Brocade = CMCNE
When you add a SAN switch to ViPR, ViPR discovers and registers the Fibre Channel networks (Brocade Fabrics or Cisco VSANs). Through discovery of the SAN topology, ViPR can identify which hosts and storage systems that were added to ViPR, are connected through the same fibre channel network. This allows ViPR to automatically build the connectivity between the hosts and storage systems when you provision a service, such as creating a block volume for a host.

After the network system is added and discovered, it is re-discovered periodically. ViPR continues to update its networks as host and storage system ports are added and removed. Once a network system is discovered, ViPR creates and removes SAN zones when block volumes are exported/unexported. If that is not the intended behavior, then set the auto-zoning flag false in the virtual array associated with this network.

This article is part of a series

You can add Brocade and Cisco switches to ViPR at anytime. If, however, you are setting up the ViPR Controller virtual data center for the first time, before you continue to provision storage, complete the following steps.
  1. Authenticate with the ViPR REST API
  2. Add physical assets to ViPR:
  3. Create ViPR virtual assets:
    1. Create and configure a virtual array
    2. Create virtual pools:

BacktoTop

Fibre Channel switch (Fabric Manager) support

ViPR supports Brocade and Cisco switches that the following requirements:

BacktoTop

Collect Brocade and Cisco switch information

To add Brocade fabrics, and Cisco switches to ViPR, you need the following information.

Record the following information for each Brocade EMC Connectrix Manager Converged Network Edition (CMCNE)

Record the following information for each Cisco swtich

BacktoTop

Preconfiguration requirements and recommendations

Before you add SAN Switches to ViPR, you must configure the following.

Brocade CMCNE configuration requirements and recommendations

EMC Connectrix Manager Converged Network Edition (CMCNE) is installed, and configured as follows:
  • CMCNE can be downloaded from EMC Support Zone (https://support.emc.com). Refer to Fibre Channel switch (Fabric Manager) support for the CMCNE version support.
  • CMCNE must be installed on a different host than the storage system SMI-S provider. CMCNE uses the same port as the SMI-S provider, and therefore causes a port conflict if CMCNE and the SMI-S provider are installed on the same machine.
  • The SMI Agent (SMIA) must have been installed and started as part of the CMCNE installation. To validate if the SMIA is installed correctly:
    • Enter the CMCNE IP in a browser, and validate the SMI Agent (provider) is installed. CMCNE SMIA appears on the CMCNE Start page, if SMIA has been installed.

      If CMCNE SMIA does not appear in the start page if it was not installed with CMCNE.

    • If it is installed, and not functioning as expected, check the C:\<installation path>\cimom\server\logs\smia-provider.log file for any errors.
  • CMCNE must have access to the switches with administrator privileges.
  • Use the CMCNE UI to prediscover the fabrics.
  • You must have created the necessary fabrics that will be used by ViPR, assigned the ports to the fabrics, and configured any ISL links needed to connect a fabric between multiple switches.
  • It is highly recommended that you implement redundant connections among ISL connections, so that the failure of a single ISL link does not partition fabrics.
  • There is no restriction on the number of fabrics.
  • Zones do not need to be created.

Cisco MDS/Nexus switch configuration requirements and recommendations

Routing requirements

BacktoTop

Add a network system (fabric manager)

Before you begin

Authenticate with the ViPR REST API as a System Administrator.

Depending on the type of switch you are adding, you will need the following information:

Type Required Information
Brocade
  • SMI-S Host address
  • Enable/disable SSL
  • SMI-S Port
  • Credentials for an account that has administrator privileges to the SMI-S host
Cisco
  • Host address for the switch
  • Port
  • Credentials for an account that has administrator privileges to the switch

The EMC ViPR REST API Reference provides a description and complete list of parameters for the REST API methods used in this article.

Procedure

  1. Add a network system (fabric manager) using POST /vdc/network-systems.
    The request returns a task.
    In this example, a Brocade switch is being added to ViPR.
    Request

    POST https://<ViPR_VIP>:4443/vdc/network-systems Content-Type: application/xml X-SDS-AUTH-TOKEN: <AUTH_TOKEN> <network_system_create> <name>br_switch_east</name> <system_type>brocade</system_type> <smis_provider_ip>10.247.99.250</smis_provider_ip> <smis_port_number>5989</smis_port_number> <smis_user_name>administrator</smis_user_name> <smis_password>password</smis_password> <smis_use_ssl>false</smis_use_ssl> </network_system_create>

    Response

    HTTP 202 Accepted Content-Type: application/xml <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <task> <associated_resources/> <description>DISCOVER_NETWORK_SYSTEM</description> <op_id>dc005a4e-d1ed-4ec6-836c-75c1468e4801</op_id> <resource> <id>urn:storageos:NetworkSystem:e80351f5-9769-4c71-9c48-5acf76c83775:vdc1</id> <link rel="self" href="/vdc/network-systems/urn:storageos:NetworkSystem:e80351f5-9769-4c71-9c48-5acf76c83775:vdc1"/> <name>br_switch_east</name> </resource> <link rel="self" href="/vdc/network-systems/urn:storageos:NetworkSystem:e80351f5-9769-4c71-9c48-5acf76c83775:vdc1/tasks/dc005a4e-d1ed-4ec6-836c-75c1468e4801"/> <start_time>1399921151084</start_time> <state>pending</state> </task>

    ViPR discovers, and registers the fabric manager and the associated networks.
  2. Query the discover network system task URI until the message attribute of the task is Operation completed successfully.
    Request

    GET https://<ViPR_VIP>:4443/vdc/network-systems/urn:storageos:NetworkSystem:e80351f5-9769-4c71-9c48-5acf76c83775:vdc1/tasks/dc005a4e-d1ed-4ec6-836c-75c1468e4801 Content-Type: application/xml X-SDS-AUTH-TOKEN: <AUTH_TOKEN>

    Response

    HTTP 200 OK Content-Type: application/xml <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <task> <associated_resources/> <description>DISCOVER_NETWORK_SYSTEM</description> <message>Operation completed successfully</message> <op_id>dc005a4e-d1ed-4ec6-836c-75c1468e4801</op_id> <resource> <id>urn:storageos:NetworkSystem:e80351f5-9769-4c71-9c48-5acf76c83775:vdc1</id> <link rel="self" href="/vdc/network-systems/urn:storageos:NetworkSystem:e80351f5-9769-4c71-9c48-5acf76c83775:vdc1"/> <name>br_switch_east</name> </resource> <link rel="self" href="/vdc/network-systems/urn:storageos:NetworkSystem:e80351f5-9769-4c71-9c48-5acf76c83775:vdc1/tasks/dc005a4e-d1ed-4ec6-836c-75c1468e4801"/> <start_time>1399921151084</start_time> <state>ready</state> </task>

BacktoTop

Manually creating and updating networks in ViPR

Manually add storage ports, and host ports to the Fibre Channel network (Brocade Fabrics and Cisco VSANs) to define the connectivity ViPR will use when storage is provisioned to the hosts. When ports are not assigned to the Fibre Channel network, ViPR will automatically assign the ports when the storage is provisioned to the hosts.

  • Only system administrators can assign storage and host ports to Fibre Channel networks.
  • Fibre Channel networks are automatically added, discovered, and registered in ViPR when the associated Brocade or Cisco switch is added to ViPR using the POST /vdc/network-systems REST API call.
  • Storage ports, host ports, or both can be defined for the Fibre Channel network by adding or removing network endpoints, using PUT /vdc/networks/{Network_URN}.
The table list some of the important REST API calls for managing the storage and host ports, and the Fibre Channel network.
BacktoTop

Important REST API calls for managing network systems (fabric managers)

The table lists some of the important REST API calls for managing network systems (fabric managers).