For more details, please see ourCookie Policy.

Design & Build

Data Center Infrastructure-Validation Test: Brocade VCS Fabric TechnologyTest Cases for Feature-Function Validation

by ‎02-27-2013 09:18 AM - edited ‎07-22-2014 09:07 AM (1,988 Views)

Synopsis: Contains a comprehensive set of tests validating features of Brocade's VCS Fabric Technology with Brocade VDX Switches.



This document provides a series of test cases that demonstrate and validate features and functions provided in Brocade VDX Switches running Brocade Network Operating System (NOS).  VDX switches include Brocade VCS Fabric technology that removes many of the limitations facing datacenter networks supporting virtualization, cloud computing and ever larger amounts of data storage.


The test cases demonstrate the benefits of a VCS Fabric including improved performance, availability, and simple configuration and management, and also show interoperability of a VCS Fabric with classic Ethernet environments using Spanning Tree Protocol (STP).


For environments where Fiber Channel over Ethernet (FCoE) is used, there are configuration and test cases covering FCoE and FCoE to Fibre Channel connectivity.


The commands listed in the various test cases are provided as working examples. Other NOS commands may be accomplish similar test results. Test cases do not cover every configuration step required to run a particular test, but show key commands with sufficient description to create a complete test case . It is expected that the engineer conducting testing will have a working knowledge of Brocade VDX Switches, Brocade NOS and have access to the latest Brocade Network Operating System Administrator Guide.


The following documents are valuable resources for the designer. In addition, any Brocade release notes that have been published for NOS, FOS the Fibre Channel switching and VDX Switch products should be at hand before conducting these test cases.


Below is the Table of Contents following which is a link to the document.



1      Brocade VCS Fabric Layer 2 Functionality

1.1     Topology used

1.2     Configure VCS ID and RBridge IDs

1.3     Automatic Creation of VCS Fabric

1.4     Automatic Creation of ISLs and Trunk Groups

1.5     MAC Address Learning

1.6     Shortest-path Forwarding, ECMP and Load Balancing

1.7     Verify Traffic Flows When Links and ISL Trunks Fail

1.8     Ethernet Fabric Vs. Spanning Tree Protocol (STP)

1.9     Ethernet LAG Vs. Brocade ISL Trunking

2      Automatic Migration of Port Profiles

2.1     Topology used

2.2     AMPP Test Considerations

2.3     Setup and Verify Procedure: Create, Associate, Activate and Apply a Port Profile

2.4     Validation of Port Profile Capabilities:VLAN, ACL, QoS and FCoE port

2.4.1          Validation of VLAN Configuration

2.4.2          Validation of ACL Configuration

2.4.3          Validation of QoS

2.4.4          Validation of FCoE

2.5     Migration of Virtual Machine(s) and validation of AMPP

2.5.1          Single MAC from One Port to Another Port in the Same Switch

2.5.2          Single MAC From One Port to a Port in a Different Switch in the VCS Fabric

2.5.3          Multiple MACs From One Port to Another port in the Same Port Profile

2.5.4          Multiple MACs From One Port to Another Port in a Different Port Profile

2.5.5          Multiple MACs From Different Ports in Same Port Profile to Port in Same or Different Switch

2.5.6          Multiple MACs From Different Ports to One Interface Using Different Port Profiles

3      VMware Network Automation

3.1     Configuring and Verifying vCenter/NOS Integration

3.2     Verifying That Data is Gathered from vCenter by NOS

3.2.1          Verify “show vnetwork hosts” Shows All Hosts Discovered by vCenter

3.2.2          Verify “show vnetwork vms” Shows All Virtual Machines in vCenter

3.2.3          Verify “show vnetwork vmpolicy macaddr” Shows all VM/vmkernel MAC Addresses

3.2.4          show vnetwork vss

3.2.5          show vnetwork pgs

3.2.6          show vnetwork dvs

3.2.7          show vnetwork dvpgs

4      Brocade VCS Fabric Layer 3 Features

4.1     OSPF

4.1.1          Topology used

4.1.2          Validation of OSPF

4.2     VRRP/VRRP-E

4.2.1          VRRP vs. VRRP-E

4.2.2          VRRP-E Parameters and Configuration

4.2.3          VRRP-E Verification and Statistics

4.2.4          Test Scenarios

5      Brocade VCS Fabric Integration with Classic Ethernet Architectures

5.1     Integration with Classic Layer 2 Ethernet

5.1.1          Create a vLAG Between VCS Fabric and Nexus 7000 Core

5.1.2          Create a vLAG Between VCS Fabric and a Server

5.2     Integration with Classic Layer 3 IP

5.2.1          Test Topology

5.2.2          Build Two-Node VCS Fabric with OSFP

5.2.3          Create OSFP Neighbors Between Nexus 7000 and VCS

6      Multi-hop FCoE

6.1     Install FCoE License

6.2     Enabling FCoE port on interface TenGigabitEthernet

6.3     Creating LUNs

6.4     Discovering LUNs

6.5     Starting FCoE traffic through a Windows Host

7      FCoE-to-FC Bridging

7.1     Supported Topologies

7.1.1          VCS Fabrics as Fibre Channel Edge Fabrics with Fibre Channel Backbone Fabric

7.1.2          Edge-to-Edge Sharing Using a Single Fibre Channel Backbone Fabric

7.1.3          Edge-to-Edge Sharing Ssing Dual Backbone

7.2     Configuring FCoE-FC Interconnect

7.2.1          Installing FCoE BASE License on VDX 6720/6730

7.2.2          Viewing and Configuring FCoE ports on VDX 6720/6730

7.2.3          Viewing and Configuring FC Ports on a VDX 6730

7.2.4          Defining and Enabling LSAN Zoning Configuration in a VCS Fabric

7.2.5          Creating and Enabling LSAN Zoning Configuration in Fibre Channel SAN Fabric

7.2.6          Enabling Fibre Channel Routing (FCR) Service on FOS Switch

7.2.7          Configuring Inter-fabric link (IFL) on the Fibre Channel Router (FCR)

7.2.8          Verifying Connectivity Between the Backbone and Edge Fabrics

7.2.9          Verifying Devices are Correctly Shared Between Edge Fabrics

8      Hardware Resiliency Testing

8.1     Power Supply Unit (PSU) and fan failover and serviceability

9      Systems Management Testing

9.1     Out-of-band Management via the Ethernet Management Interface

9.1.1          Configure a Static IPv4 Address on the Management Interface

9.1.2          Configure a Dynamic IPv4 Address Using DHCP

9.1.3          Configure a Static IPv6 Address

9.1.4          Configure a Dynamic IPv6 Address

9.2     VCS Fabric IP address

9.3     In-band management via VLAN, Physical or Port Channel Interfaces

9.3.1          Configure In-band Management via VLAN

9.3.2          Configure In-band Management via Physical Interface

9.3.3          Configure In-band Management via Port Channel

9.4     Supportsave Automation

9.4.1          Supportsave to a USB drive

9.4.2          Supportsave to an External Host

9.5     Network Time Protocol (NTP) and Local Clock

9.5.1          Verify NTP Operation

9.5.2          Verify Local Clock Operation

9.5.3          Configure Time Zone

9.6     Syslog

9.7     sFlow

9.8     Simple Network Management Protocol (SNMP)

9.9     Host Name

9.10  Switched Port Analyzer (SPAN)

9.10.1        Bi-directional Mirroring

9.10.2        Ingress Mirroring

9.10.3        Egress Mirroring

9.11  Remote Monitoring (RMON)

9.12  RADIUS

9.13  Terminal Access Controller Access-Control System Plus (TACACS+)

9.14  Role-Based Access Control (RBAC)

9.14.1        Create a New role

9.14.2        Create a New User

9.14.3        Create Rules for a Role

9.15  Licensing


by kelvin1
on ‎03-22-2013 02:11 PM

Great paper thus far, haven't read in entirety yet.  In Section 1.3, there is a statement that "...we just need to connect the cables between them and the fabric will automatically form."  That is exactly what I have seen, but the procedure then includes commands to do a 'no shutdown' on the ports as if that is needed to bring the ISLup.  I'd suggest pulling this from the procedure and noting that one can shutdown ports if desired.  Same for Section 1.4, contradicting description and CLI action.

Also, regarding the first action in 1.3, not sure why there is a 'fastboot' after the 'show fabric all' command.