You could use VLAN groups, but the easiest solution is to use the LAN uplinks manager to pin VLAN 11 and 12 to uplink2 and the other VLANs will continue to flow using uplink1. VLAN groups are typically used for large deployments with hundreds of VLANs. You cannot pin a VLAN to multiple disjointed uplinks.    https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ucs-manager/GUI-User-Guides/Network-Mgmt/3-2/b_UCSM_Network_Mgmt_Guide_3_2/b_UCSM_Network_Mgmt_Guide_3_2_chapter_0100.pdf   https://www.cisco.com/c/en/us/solutions/collateral/data-center-virtualization/unified-computing/white_paper_c11-692008.html   LAN Tab > LAN Cloud > Launch LAN uplinks manager     VLANs tab > VLAN Manager > Fabric A|B     On the left select uplink1 and pin the VLANs accordingly and select add VLAN. Do the same for uplink2 and apply changes on both fabrics.   You should now be able to run 'show interface X' from nxos cli and see the VLANs only applied to the uplinks specified.  ... View more

A server pool is typically used when you do not have a preference for what profile is tied to what blade.   If you want to manually assign a service profile to specific piece of hardware, you can remove the server pool to accomplish this. Otherwise, you may still have to manipulate the profiles as you did this go around to get the profile you want on the blade you want. ... View more