There should not be a difference between end-host mode or switch mod for this configuration. If you are having problems getting your port-channel to form on the N1Kv there a few things you can look at some of it is UCSM version dependent.
If you are using port-profile config with channel-group auto mode on subgroup cdp you need to enable CDP on the UCS Service Profile NICS for each host. Enabling CDP on the VNIC I think requires 1.02d code or later. If you are using an earlier code you need to manually define the subgroup ID for each VETH on the N1K corresponding to your Host uplinks.
I believe the new recommended method is to use channel-group mode on mac-pinning which is available AV N1Kv release.
If you do show int brief on the N1Kv and your Port-Channel interfaces are all up then you are good to go.
thanks, I was looking at the Nexus 1000v Interface Configuration Guide, there is a whole section regarding port channel, but not mentioning mac-pinning, probably because it's a port-profile command
I wonder why it is "new recommended" way for PortChannel as you said, what is the benefit doing this way? All I can find in the doc is that it is used when upstream switch does not support port channel:
mac-pinning—Specifies that Ethernet member ports are assigned to subgroups automatically, one subgroup per member port. This option is used if the upstream switch does not support port channels.
mac pinning is a new feature of the latest software release and therefore wasn't available previously. Before that, VPC HM was recommended in the prior release.
The benefit of using mac-pinning is you don't create separate subgroups for each uplink interface. Hence less complexity and configuration. Essentially VPC HM and mac-pinning work in similar ways anyway.
Unfortunately what the configuration guide does not indicate is that although in earlier releases prior to 1.02d where the VNIC doesn't support CDP, the only way to successfully configure vPC-HM was to configure the port-profile system-uplink with CDP and also manually define the subgroup ID for each VETH. This may not be case in later releases but this was what I discovered, and Cisco recommended to do as shown the extract below:-
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
==================== VIC FNIC driver does not support Virtual Volumes (
second level LUN ID ) An enhancement request has been created to track
this feature - CSCux64473 UPDATE - 12-14-2016 We made some traction on
the enhancement request - The Fix is in t...