Chandra,
Without knowing your exact devices or topology a good use would be:
2 x 1G - for Service Console & 1000v Control/Packet/Management Traffic
4 x 10G - for vMotion, NFS, VM Traffic
This gives you dedicated redundant connections for Management while reserving your 10G interfaces for the heavy traffic.
In 1000v terms, this means you'd have two "Ethernet" Port Profile. Keep in mind EVERY VLAN can only be allowed on one of the two Ethernet Uplink Port Profiles. So assuming you're going to break up traffic as listed above, each traffic type should be assigned to it's own VLAN (ex. Not sharing Management VLAN with VM traffic etc).
Here's how it would look assuming the following:
1. Service Console & 1000v Management = VLAN 10
2. VMotion = VLAN 20
3. NFS = VLAN 30
4. VM Network = VLAN 40
5. 1000v Control = VLAN 50
6. 1000v Packet = VLAN 60
Uplink Port Profile 1
port-profile type ethernet system-uplink
vmware port-group
switchport trunk allowed vlan 10,50,60
switchport mode trunk
channel-group auto mode on mac-pinning
no shutdown
system vlan 10,50,60
state enabled
Uplink Port Profile 2
port-profile type ethernet vm-uplink
vmware port-group
switchport trunk allowed vlan 20,30,40
switchport mode trunk
channel-group auto mode on mac-pinning
no shutdown
system vlan 30
state enabled
*Note: The only vlans that need to be set as "system vlans" are 1000v Control/Packet, Service Console/Management, and IP Storage (NFS).
**Notice I've used MAC pinning in this example, but you can also use a Port Channel if your upstream switches support it. MAC pinning is much simpler to setup, but a Port channel will provide better balancing to aggregated traffic.
Let me know if you have any other questions.
Regards,
Robert
