Can't configure adapter-fex on Broadcom 57810 in a C220 M3 server
I'm attempting to setup Adapter-FEX between a Cisco C220 M3 server with a Broadcom BCM57810 (Cisco P/N UCSC-PCIE-B3SFP) and a pair of Nexus 5596 switches. The server is running Windows 2012 R2 (also tried 2008 R2). I've setup both the Nexus switches and Broadcom card according to what documentation that I could find (which isn't much). When configuring the Broadcom card, the port profiles do show up so that I can choose them (so it is seeing the Nexus switch). I've tried various combinations of assigning the profiles to different channels on the Broadcom card. However, when the server is booted up, both uplinks go into a down state and show "link failure" in the system log of the Nexus. Yet when the system is undergoing POST tests and such (pre-Windows boot), both links are active and online. Is there a configuration setting that I may be missing? The Broadcom card is setup for AFEX mode with DCB enabled, and flow control is turned off for the channels that I was configuring. The Nexus switches each have the VM-Fex license installed.
The setup that I'm trying to accomplish is rather simple. I just need to have a minimum of two virtual adapters created which are on two separate VLANs. One physical port on the Broadcom card goes to Nexus switch #1, and the second port goes to Nexus switch #2. The Nexus switches are setup in a redundant fashion with VPCs between them. All drivers on the Windows server are up-to-date from Cisco's website. The Nexus switches never show any vethernet interfaces being created. And manually created vethernet interfaces don't come online either.
Commands entered into the Nexus switches(and synced between them):
install feature-set virtualization
port-profile type vethernet PRIMARY_DATA_VLAN103
switchport access vlan 103
port-profile type vethernet BACKUP_DATA_VLAN400
switchport access vlan 400
description New Backups Server
switchport mode vntag
Output of Nexus switch interface after server is booted up:
Thanks. Actually I've had a TAC case open on this pretty much since I originally posted it, and it was a confirmed bug in the Broadcom firmware. The CNA isn't sending the proper requests to the Nexus switch to setup the virtual adapters. QLogic (which owns part of Broadcom) is supposedly working on a fix, but I have yet to see it.
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
In the Previous articles of ACI Automation, we are using Postman/Newman as the Rest API tool to automate the ACI Configuration.
In this article I’m going to discuss on usin...
One of the first steps in building your ACI Fabric is to go through Fabric Discovery. While Fabric Discovery is usually a straightforward process, there are various issues that may prevent you from discovering an ACI switch. This article wil...