Brocade MLX Series and Brocade NetIron XMR Diagnostic Guide ...

4LACP trunkingType: ServerPorts_Configured: 2Base FID: 0x0400FID count: 16Ports 14/6 14/8Port Names ve4012 TestCa*Port_Status disable disableOperational trunks:Trunk ID: 1Type: ServerDuplex: NoneSpeed: NoneTag: DualPriority: level0Active Ports: 0Ports 14/6 14/8Link_Status down downTrunk debug commandsThere are no debug commands specific to LACP trunking.Configuration notes• You cannot use 802.3ad link aggregation on a port configured as a member of a static trunkgroup.• When LACP dynamically adds or changes a trunk group, the show lag command displays thetrunk as both configured and active. However, the show running-config or write terminalcommands do not contain a trunk command defining the new or changed trunk group.• You can enable link aggregation on 802.1q tagged ports (ports that belong to more than oneport-based VLAN).• LACP cannot be configured on a VPLS endpoint port, and a VPLS endpoint cannot beconfigured on a physical port that has LACP enabled. This restriction is enforced by the CLI. If aVPLS endpoint receives any LACP traffic, this traffic will be dropped by the router at ingress.However, if the VPLS has CPU protection enabled, this traffic will be hardware flooded.• Brocade recommends that you disable or remove the cables from the ports you plan to enablefor dynamic link aggregation. Doing so prevents the possibility that LACP will use a partialconfiguration to talk to the other side of a link. A partial configuration does not cause errors,but sometimes requires LACP to be disabled and re-enabled on both sides of the link to ensurethat a full configuration is used. It is easier to disable a port or remove its cable first. Thisapplies both for active link aggregation and passive link aggregation.94 Brocade MLX Series and Brocade NetIron XMR Diagnostic Guide53-1002426-02