You are here: Home / Basics / Basics: Three Types of Cisco UCS Network Adapters

Basics: Three Types of Cisco UCS Network Adapters

13th August 2012 by 9 Comments

In the Cisco UCS servers, there are three classes or categories of Network Adapters for B-series and C-Server servers.

The network adapters are all connected to a PCI Slot on the motherboard in the form of a proprietary card called a”mezzanine adapter” which connects to a “mezzanine slot” or “mezz slot” for short. The term mezzanine is widely used by most vendors and refers to the physical way it ‘stacks’ onto the motherboard like a mezzanine level in a physical building.

The three categories are;

Three categories of Cisco UCS Network Adapters
Category Description My Observations
Ethernet Adapters Network silicon from Intel and Broadcom providing conventional networking capabilities. Can present up to two Ethernet interfaces to a server when two cards are installed. When using hypervisor,  resources of the card  handled in software. 
Converged Network Adapters Network silicon from Emulex and QLogic that has FC and Ethernet with software drivers for FC interfaces that storage admins care about. Network cards that have FibreChannel and Ethernet adapters on a single card with fancy silicon for hardware acceleration. One Ethernet network interface per card and one FC interface. When using hypervisor, it shares the resources of the card in software. 
Virtual Interface Cards Network silicon from Cisco that is bathed in Unicorn Tears in the final production phase.

Supports FEX features via VN-Link/802.1BR technology that allows each virtual adapter to appear as a separate Virtual Interface (VIF) on the fabric interconnects.

The architecture of the Virtual Interface Card is capable of supporting up to 128 total virtual network adapters split between vNICs and vHBAs.

Configuration of the VIC is handled in UCS Manager. The hypervisor sees as many “physical NICs” as are configured.

Can allocate multiple NICs to multiple software switches according to whatever policy you need to create. 

I write this down because it’s pretty hard to find this summary anywhere is Cisco’s documentation and I keep having to tell people the difference. Now I can point them at this blog post.

Filed Under: Basics, Tech Notes Tagged With: , ,
About Greg Ferro

Greg Ferro is a Network Engineer/Architect, mostly focussed on Data Centre, Security Infrastructure, and recently Virtualization. He has over 20 years in IT, in wide range of employers working as a freelance consultant including Finance, Service Providers and Online Companies. He is CCIE#6920 and has a few ideas about the world, but not enough to really count.

He is a host on the Packet Pushers Podcast, blogger at EtherealMind.com and on Twitter @etherealmind and Google Plus

  • http://blogstu.wordpress.com stu

    When Cisco first launched UCS, the partner ecosystem made a big deal about all of the options. I’ve heard that around 95% of adapters sold over the last could of quarters have been of the Cisco (VIC) variety. Since UCS is still only 1-2% of overall server sales, the Cisco adapters don’t have significant market adoption compared to Intel, Broadcom, Emulex and QLogic, but I was still a bit surprised at how dominant the Cisco adapter on the UCS platform.

    • http://etherealmind.com Etherealmind

      The VIC is the “magic sauce” of the UCS platform and about the only thing that is a clear differentiator. “stateless computing” is nice, but it’s a hard sell. The network integration is what makes UCS attractive to customers I think.

      • http://twitter.com/DmitriKalintsev Dmitri Kalintsev

        From what I understand, UCS is much more stateless than other “stateless” alternatives. I had a document somewhere that compared the number of configuration points that UCS had in server profile, compared to HP’s blade system. UCS had about twice the number, IIRC.

  • Jim Leach

    Don’t forget about the new VIC-1240 mLOM (modular LAN on Motherboard-doohicky) and the VIC-1280, which supports 256 virtualised interfaces. The mLOM initially has 40GE connection to the fabric which can be extended up to 80GE by replacing the Mezz card with a ‘port extender’. There’s also a VIC-1225 which is an actual PCIe card for the C-series UCS.

    How many more options could you possible ask for??

    • http://etherealmind.com Etherealmind

      Less options! That’s too many choices and causes decision paralysis when buying.

      Keep it simple.

    • http://twitter.com/DmitriKalintsev Dmitri Kalintsev

      Apparently with 8 uplinks you can have up to 502 VIFs per blade. See vmguru (dot) nl website for a nice summary article on that.

  • http://twitter.com/#!/Daniel_Bowers Daniel Bowers

    If you don’t like vendor docs, write your own!

    The adapters that plug into C-Series servers (pizza-box type rack servers) are physically shaped different than the adapters that plug into B-Series servers (blades).

    The adapters for B-Series are ‘proprietary’ in their shape; they physically can only connect to Cisco B-Series servers.

    The Ethernet and CNA adapters for C-Series are standard half- or full-height PCI Express cards, so perhaps they aren’t ‘proprietary’. (Unless Cisco is doing something strange, those C-Series Ethernet and CNA adapters are physically the same Broadcom, Intel, Emulex, and Qlogic cards that other vendors use, but with firmware customized for Cisco.).

    Until recently, I’d only heard vendors call to the adapter cards that plug into blades “mezzanines”. Cisco docs still don’t call the C-series adapters “mezzanines”, they’re still just “cards”.

    • http://etherealmind.com Etherealmind

      I just did.

      I still call them “mezz cards” but I’m rebellious like that.

  • http://twitter.com/tbourke tbourke

    Small correction: All mezzanine cards have access to two connections on the backplane, so all cards have at least the ability to have two NICs, and the CNAs/VICs have also can have (at least) two native FC interfaces. One connection goes to the A IOM and thus A Fabric Interconnect, and the other goes to the B IOM and thus B Fabric Interconnect.