Hi Kumar!
Your chassis connectivity policy works hand-in-hand with the chassis discovery policy. Your chassis discovery policy is global to the FI, and basically determines two key things:
1.) How many links need to be connected between an IOM and an FI before the UCS Domain will "see" the chassis as healthy, and
2.) How do we want to handle the connectivity between the IOM and the FI (referred to as "Link Grouping"). If Link Grouping is set to "Port Channel", the links between the IOM and the FI are bundled into an port-channel. If set to None, then the UCS proceeds to pin VNICs to the individual NIFs between the IOMs and the FIs (similar to how a 2200 would distribute its HIF pinning when you have multiple uplinks that aren't port-channeled).
Chassis connectivity policy allows us to overwrite the behavior set in point 2 on a per-chassis basis. So, your options are:
Global - Inherit the link grouping setting from the chassis discovery policy
Port Channel - Ignore the discovery policy and ensure that the links between the IOMs and the FI are bundled logically
None - Ignore the discovery policy and perform pinning based on the usual distribution mechanism.
As for benefits, the main impact is your total throughput. If you are set to "None", you have 1/2/4/8 (on a 2208 anyways) 10Gbe links, which means that at most your vNIC will be able to pass 10Gbe of traffic. Whereas if you are set to port-channel your vNIC gets pinned to a port-channel of all the links, so theoretically you get more throughput
Let me know if this helps!
Devin
