Developers Club geek daily blog

3 years ago
In one of the articles I told what is architecture of FlexPod DC and what it consists of, treat the physical FlexPod DC components: SHD NetApp of the FAS series, Cisco UCS and Nexus server switches. There is a big variety of the supported designs of FlexPod DC consisting of these three main a component. To use cooperative support from "one hands" existence of the corresponding service of support is necessary for all these a component.

What if you have Cisco SnartNet and NetApp Support Edge services, and in architecture there are no Nexus switches, at this SHD is directly included in UCS Fabric Interconnect?

It is also "a не-FlexPod of DC" architecture about which the speech will go, she can be supported from "one hands" according to the Cisco "Solution Support for Critical Infrastructure" (SSCI) program too.

non-FlexPod DC: Direct-Attached Storage, Support "from one hands"
The general design of a SAN network with a live broadcast

For use of the FC protocol on FI devices it will be required to include FC Switching mode and the FC zoning function, ports connected to SHD it will be necessary to transfer to the Storage Port mode and to create VSAN (not to confuse to VMware vSAN) in the section Storage Cloud:

Configure as FC Storage Port
non-FlexPod DC: Direct-Attached Storage, Support "from one hands"

Configure as FCoE Storage Port
non-FlexPod DC: Direct-Attached Storage, Support "from one hands"

For FI now on the same port it is possible to receive at the same time and "normal" Ethernet a traffic (for example CIFS, iSCSI, NFS), and FCoE. If your storage has CNA or UTA2 ports (all FAS255x and FAS8000 of a series have onboard) and supports, also as well as FI, an opportunity to start Ethernet and FCoE on one link (NetApp FAS with CNA/UTA2 support all), it is possible to switch ports of such devices directly, without switch.

Setup of the unified ports
  • First the version of a firmware not below Cisco UCS firmware 2.1 is necessary
  • Secondly the storage with 10GB CNA ports is necessary

From NetApp storage it is necessary to transfer ports to CNA status (existence of CNA ports, normal Ethernet 1/10Gbs is necessary ports of it do not support), by means of the ucadmin command on SHD (restart of SHD will be required). In system independently "virtual" ports Ethernet and "virtual" FC ports, separately will be displayed (though the physical port for one such "virtual" Ethernet and one "virtual" FC will be used one). Such ports separately as normal physical ports are configured.

On FI it is necessary to include the FC mode in a status of "Switching mode", in the Fabric A/B settings on the Equipment tab. This setup will demand restart of FI.

After restart of FI on the Equipment tab it will be necessary to transfer convergent ports to the Appliance port mode, after several seconds the port will pass into online mode. Then recustomize port in the FCoE Storage Port mode, on the right panel you will see type of Unified Storage port. Now will be vozmozhnocht to select VSAN and VLAN for such port. And the important point created earlier VSAN has to have included "FC zoning" on FI to execute a zoning.

Reverse side of a configuration with a live broadcast is bad scalability, and also not a possibility of setup for all types of a network traffic of fault tolerance and balancing of loading on network links.
For traffic Ethernet as together with a live broadcast and the iSCSI protocol, a live broadcast and the FCoE protocol, and also for the FC protocol with direct connection, balancing of loading on network links and fault tolerance is reached by means of the multipasing which is built in these protocols.

In design of FlexPod DataCenter Nexus series switches on-prezhdnemu are an obligatory component of architecture:
  • first because FlexPod has to be somehow integrated into the existing infrastructure and provide access to clients
  • secondly inclusion via the switches Nexus will allow to scale architecture in the future
  • in the third, unlike a live broadcast with SAN (FC/FCoE/iSCSI), the design of Ethernet of a network for NAS demands existence of an intermediate link between domain SHD and UCS for execution of balancing of loading on network links, and mainly, fault tolerance functions.
  • fourthly access for external clients on Ethernet to FlexPod has to be fault-tolerant

By errors in the text I ask to send messages to a LAN.
Notes and additions, on the contrary, I ask in the comment.

This article is a translation of the original post at
If you have any questions regarding the material covered in the article above, please, contact the original author of the post.
If you have any complaints about this article or you want this article to be deleted, please, drop an email here:

We believe that the knowledge, which is available at the most popular Russian IT blog, should be accessed by everyone, even though it is poorly translated.
Shared knowledge makes the world better.
Best wishes.

comments powered by Disqus