> # F and TF PortChannel Limitations

> The following guidelines and restrictions are applicable for F and TF PortChannels:

> - The ports must be in F mode.
> - Automatic creation is not supported.
> - The PortChannel interface must be in ACTIVE mode when multiple FCIP interfaces are grouped with WA.
> - ON mode is not supported. Only ACTIVE-ACTIVE mode is supported. By default, the mode is ACTIVE on the NPV switches.
> - Devices logged in through F PortChannel on an MDS switch are not supported in IVR non-NAT configuration. The devices are supported only in IVR NAT configuration.
> - Port security rules are enforced only on physical pWWNs at the single link level.
> - FC-SP authenticates only the first physical FLOGI of every PortChannel member.
> - Since the FLOGI payload carries only the VF bits to trigger the use of a protocol after the FLOGI exchange, those bits will be overridden. In the case of the NPV switches, the core has a Cisco WWN and will try to initiate the PCP protocol.
> - The name server registration of the N ports logging in through an F PortChannel will use the fWWN of the PortChannel interface.
> - DPVM configuration is not supported.
> - The PortChannel port VSAN cannot be configured using DPVM.
> - The Dynamic Port VSAN Management (DPVM) database will be queried only for the first physical FLOGI of each member, so that the port VSAN can be configured automatically.
> - DPVM does not bind FC_IDs to VSANs, but pWWNs to VSANs. It will be queried only for the physical FLOGI.

> Copyright 2010-2013, Cisco Systems, Inc. All rights reserved.