switch# show port-channel compatibility-parameters
- port mode
Members must have the same port mode configured, either E,F or AUTO. If
they are configured in AUTO port mode, they have to negotiate E or F mode
when they come up. If a member negotiates a different mode, it will be
suspended.
- speed
Members must have the same speed configured. If they are configured in AUTO
speed, they have to negotiate the same speed when they come up. If a member
negotiates a different speed, it will be suspended.
- MTU
Members have to have the same MTU configured. This only applies to ethernet
port-channel.
- MEDIUM
Members have to have the same medium type configured. This only applies to
ethernet port-channel.
- Span mode
Members must have the same span mode.
- load interval
Member must have same load interval configured.
- span port headers
The exclude header span config must either be present or absent on all
members.
- sub interfaces
Members must not have sub-interfaces.
- Duplex Mode
Members must have same Duplex Mode configured.
- Ethernet Layer
Members must have same Ethernet Layer (switchport/no-switchport) configured.
- Span Port
Members cannot be SPAN ports.
- Storm Control
Members must have same storm-control configured.
- Flow Control
Members must have same flowctrl configured.
- Capabilities
Members must have common capabilities.
- Capabilities speed
Members must have common speed capabilities.
- Capabilities duplex
Members must have common speed duplex capabilities.
- rate mode
Members must have the same rate mode configured.
- Capabilities FabricPath
Members must have common fabricpath capability.
- Port has PVLAN config
Members must have same pvlan configuration
- 1G port is not capable of acting as peer-link
Members must be 10G to become part of a vPC peer-link.
- EthType
Members must have same EthType configured.
- shared interface
Members can not be shared-interfaces.
- Capabilities SpanDest
Members must be capable of span destination configuration
- Module Type Incompatible
Module type for interfaces is not compatible.
- Port Mode Fabricpath Incompatible
Members are Fabricpath Enforce locked, not compatible.
- Rewrite Translate – Rate Mode shared, Incompatible
Members have rate mode shared,and rewrite translate exists on the channel
group,Not compatible.
- FEX – PVLAN promiscuous config
FEX ports cannot have private VLAN promiscuous or promiscuous trunk configs
- vmtracker enable mismatch
Members have vmtracker enable mismatch
- port
Members port VLAN info.
- port
Members port does not exist.
- switching port
Members must be switching port, Layer 2.
- port access VLAN
Members must have the same port access VLAN.
- port native VLAN
Members must have the same port native VLAN.
- port allowed VLAN list
Members must have the same port allowed VLAN list.
- VLAN translation mapping list
Members must have the same VLAN translation list.
- Members should have same fex config
Members must have same FEX configuration.
- FEX pinning max-links not one
FEX pinning max-links config is not one.
- Multiple port-channels with same Fex-id
Multiple port-channels to same FEX not allowed.
- Pinning Params
Members must have the same pinning parameters.
- All HIF member ports not in same pinning group
All HIF member ports not in same pinning group
- Slot in host vpc mode
Cannot add cfged slot member to fabric po vpc.
- Members in multiple FEX
Members must belong to same FEX.
- Members are of different type
Members must of same interface type.
- port egress queuing policy
10G port-channel members must have the same egress queuing policy as the
port-channel.
- Port Security policy
Members must have the same port-security enable status as port-channel
- Port priority-flow-control
PFC config should be the same for all the members
- Dot1x policy
Members must have host mode as multi-host with no mab configuration. Dot1X
cannot be enabled on members when Port Security is configured on port
channel
- PC Queuing policy
Queuing policy for Non-DCE PC should be non-dce
- PC Queuing policy
Queuing policy for the PC should be same as system queuing policy
- PVLAN port config
Members must have same PVLAN port configuration.
- Emulated switch port type policy
vPC ports in emulated switch complex should be L2MP capable.
- VFC bound to port
Members cannot have VFCs bound to them.
- VFC bound to port channel
Port Channels that have VFCs bound to them cannot have more than one member
- VFC bound to FCoE capable port channel
Port Channels that have VFCs bound to them cannot have non fcoe capable
member
- VFC bound to FCoE capable port channel
Port Channels that have VFCs bound to them cannot have non fcoe licensed
member
- EVC EFP configured under port channel member
Port Channel members cannot have EVC EFP configured under them
- Fex ports for span
Port-Channel is already a SPAN source. Cannot add FEX ports connected
through F2/F2E series line cards to this PC
- shut lan
Members cannot have shut lan configured
- VPC orphan port suspend configured under port channel member
Port channel members cannot have vPC orphan port suspend configured under
them
- tag native
Members must have same native vlan tagging configured
- VNSEG VSI configured under port channel member
Port Channel members cannot have VNSEG VSI configured under them
- VNSEG VSI Id for FEX > 62
VNSEG VSI Id greater than 62 not allowed on FEX Ports
- VNSEG VSI configured under port channel and VSI under FEX member have overlapp
ing mappings
VNSEG VSI configured under port channel and VSI under FEX member should not
have overlapping mappings
- VNSEG VSI Id and profile name mismatch on FEX member with those on Port-channe
l
FEX Port Channel members and port-channel configuration for VSI Id and
profile name should match
- VNSEG VSI type mismatch on FEX member with those on Port-channel
All FEX ports should have same VSI Type – STATIC/VDP/DFS
- PLSM EDP port type policy
EDP ports should fail to be part of Port Channel
- Port priority-flow-control long-distance
PFC_LD config should be the same for all the members
- Port channel LFC-PFC compat check fail
PFC of PC to be turned OFF when LFC is ON or LFC of PC to be default, to
add DCE member
- CTS mode
Members must have the same CTS mode configured (either “cts manual” or “cts
dot1x” or no cts)
- CTS SGT propagation
SGT propagation must either be enabled or disabled on all members
- CTS SGT policy
Members must all have either “policy static” or “policy dynamic” or no
policy configured
- CTS peer identity
Members must all have the same peer identity configured
- CTS SGT configuration
Members must all have the same SGT configured
- CTS replay protection
Replay protection must either be enabled or disabled on all members