We have a few C240 M4s with the MLOM VIC and the VIC1225 installed in a PICe slot, we are doing single wire/direct connect to the FIs (which are 6248UP running 5.2(3)N2(2.23c))
It doesn't look like the path from the VIC 1225s is showing up properly, the service profile is attempting to put vHBAs/vNICs onto the 1225 and those paths don't appear to work. This is obviously causing all sorts of issues with booting and paths.
Has anyone configured a c240 m4 with dual VICs if so what is the proper process to do so, I have searched through the documentation and there is very little useful information.
Reading your issue, I am assuming you are talking about the placement of the vNICs is not showing-up properly, not anything to do with the hardware itself?
With Dual Cards, you are going to need a vCon Placement Policy to further define what vNICs are being placed on what Physical Cards.
Correct, I have read up on the placement and ideally we would like to have network and storage traffic split across the 2 vics. I have adjusted the placement policy and the root issue appears to be that the pcie vic 1225 is not getting recognized properly by ucsm. Was wondering if I am missing some configuration or a software update or what in the world would cause the pcie vic not to work properly (i have to confirm they are in the correct pcie slot, we also have fusion io in the servers and that is currently in pcie slot 1)
Eric - Please verify your Config….
From the C240-M4 Install/Config Guide….
Special Considerations for Cisco UCS Virtual Interface Cards
Table 3-10 <http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/c/hw/C240M4/install/C240M4/replace.html#65312> describes the requirements for the supported Cisco UCS virtual interface cards (VICs).
Added: After conferring with my colleague Jeff Foster, he recommended installing the Fusion IO Card in PCIE #1, and Installing the VIC in either PCIE Slot #2, or Slot #5.
Our config is correct based on the documentation and the suggestion of the fusion card in slot 1 and vic in slot 2.
I have a few more coming online in the next week or so and i'll see if ucsm picks up the secondary vics properly.
Matthew Faiello | UCS Technical Marketing Engineer | .:|:.:|:. Cisco Systems, Inc.
email@example.com| Phone: 727-540-1432 | Twitter: @mfaiello
UCS Communities: http://communities.cisco.com/ucs
UCS Platform Emulator: http://communities.cisco.com/ucspe
UCS Developed Integrations: http://communities.cisco.com/ucsintegrations
the issue was the order which the vHBAs were being assigned, it was causing problems when assigning the vCon policy. It has been resolved and so far so good. mfaiello thanks for the help.