- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-10-2011 10:31 AM - edited 03-01-2019 09:47 AM
All,
We use b250 M2 full width blades with 2 Palo cards installed. When I create a placement policy I am presented with 4 vcons. In my reading there should only be 2 vcons (vCon1 for Palo 1 and vCon2 for Palo 2). Am I missing something? We are running 1.4.1i firmware.
Thanks,
Ken
Solved! Go to Solution.
- Labels:
-
Unified Computing System (UCS)
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-10-2011 11:17 AM
oh, I see. I have also noticed those additonal vCons after updating to 1.4. I believe those are for rack-mount C-Series that can have more adapaters than the B-Series.
I am still recommending the ESX NIC failover/teaming so that both fabrics get used on the network side. The new FabricSync feature is more for Hyper-V because it has limited NIC configurations.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-10-2011 11:03 AM
Take a look at the blog post I did on this. It explains how to to use and distribute vNICs/vHBAs across those 2 slots.
http://jeremywaldrop.wordpress.com/2010/08/26/cisco-ucs-vnicvhba-placement-policies/
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-10-2011 11:10 AM
Jeremy,
Thanks for the reply. I have read your post. In fact I have used yours and Brad's sites for my UCS configuration as a whole. What I am questioning is why am I seeing 4 vCons when only two are used? I am attaching a screenshot of what I see when I right click and choose to create a new conncection policy. Should I just delete vCon 3 and 4?
On another note I read on your failover post that 1.4 firmware now supports the learned MAC address syncing so the failover switch in UCS can now be used with ESXi. Do you recommend to let the fabric control failover or do you still prefer to let ESXi handle failovers by using redundant vNICS?
Thanks for your help,
Ken
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-10-2011 11:17 AM
oh, I see. I have also noticed those additonal vCons after updating to 1.4. I believe those are for rack-mount C-Series that can have more adapaters than the B-Series.
I am still recommending the ESX NIC failover/teaming so that both fabrics get used on the network side. The new FabricSync feature is more for Hyper-V because it has limited NIC configurations.
