You save $69.98
Two switches have compatible Layer 2 links assigned to Port-channel 56. SW1 is configured `channel-group 56 mode active` and SW2 `channel-group 56 mode passive`. The members remain unbundled after a later template change. Which finding would explain the failure even though the mode pairing itself is valid?
LACP active/passive can negotiate successfully, but physical and Layer 2 configuration compatibility (including trunks/VLANs) is still needed for a bundle.
An LACP active end transmits protocol PDUs and can negotiate with a passive peer; two passive ends would be the problematic pairing.
The group number identifies the logical Port-channel, not the number of physical links expected to join it.
PAgP is a separate aggregation protocol; both ends of this link already use compatible LACP modes.
At an e-commerce platform, the site engineer sees member ports intermittently suspended from negotiated EtherChannel 15 after a template push. Which configuration practice should be checked first?
For a stable LACP EtherChannel 15, member interfaces must be compatible with the logical port-channel policy. Mismatched VLAN or physical parameters may suspend members.
An incompatible speed/duplex member typically cannot join the same working aggregate.
Native VLAN mismatches cause inconsistent untagged-frame classification across the bundle.
VLAN inconsistency between bundled Layer 2 members violates the expected common logical connection.
At an insurance company, the branch support lead wants Layer 3 routed adjacency across LACP Port-channel59, not a multi-VLAN Layer 2 bridge. Which high-level configuration is appropriate?
Layer 3 EtherChannel uses a routed logical Port-channel59 interface; no switchport places it in routed mode, then the aggregate receives a Layer 3 address.
Layer 2 access VLAN configuration cannot represent the requested routed aggregate interface.
Unrelated member interface addresses are not a consistent logical routed bundle.
Trunk allowed VLAN lists are Layer 2 options and do not create a routed port-channel gateway.
A pair of Cisco multilayer switches needs a Layer 3 LACP EtherChannel that runs routing directly over the port-channel rather than bridging VLANs. Which configuration characteristic is required on supported interfaces?
On a supported multilayer platform, a routed EtherChannel uses compatible routed member interfaces and places the IP configuration on the logical Port-channel, which acts as the L3 adjacency.
Separate member IP addresses conflict with the logical-channel model, and an access VLAN does not create a single routed aggregation interface.
An 802.1Q trunk is a Layer 2 aggregation. Without routed configuration it cannot provide the required direct L3 adjacency.
A separate SVI can route a VLAN, but it does not make the specified point-to-point EtherChannel itself a routed interface.
After adding a second switchport to a Layer 2 LACP trunk bundle, only the original member is active. The new member permits VLANs 20,30 while the port-channel and first member permit 20,30,40. What correction is most relevant?
Member interfaces must have compatible Layer 2 parameters for a trunk EtherChannel. A conflicting allowed-VLAN list can prevent proper bundling; correct the mismatch and confirm `(P)` membership.
A Layer 2 trunk EtherChannel does not need separate member IPs, and addressing does not repair VLAN compatibility.
Mixing access and trunk modes makes the channel inconsistent rather than adding VLAN 40 to the aggregate.
A member whose trunk VLAN configuration differs from the bundle may stay suspended; LACP negotiation alone does not fix inconsistency.
At a retail branch, the migration lead is configuring GigabitEthernet1/0/12 in a negotiated LACP EtherChannel 52; the far end uses LACP passive. Which local mode should be set?
Active initiates LACP negotiation for port-channel 52; it can form with a correctly configured active or passive peer if member parameters match.
Mode on forces static aggregation without LACP negotiation; it is not the requested LACP dynamic negotiation.
Passive alone waits for the peer to initiate LACP; if both sides are passive, negotiation will not start.
Desirable belongs to PAgP, not IEEE LACP, and will not negotiate the LACP-only far end.
Two switches each configure two compatible interfaces into Port-channel 13 using `channel-group 13 mode passive`. No LACP neighbors form. Which single configuration change directly initiates negotiation?
Passive/passive does not initiate LACP exchanges. At least one active peer sends PDUs; compatible physical/L2 settings are still required.
An interface description affects administration only; it does not start LACP negotiations.
Static mode on disables LACP negotiation; it is not evidence that the desired protocol adjacency formed.
System priority may affect actor selection but cannot substitute for an active peer that initiates LACP exchange.
An LACP port-channel uses Gi1/0/1 and Gi1/0/2. `show etherchannel summary` shows Gi1/0/1(P) and Gi1/0/2(s) while the port-channel is up. Which observation best explains the operational state?
In the summary, `(P)` denotes a bundled port and `(s)` a suspended port. A healthy port-channel can stay up with one member while the other is excluded; compare parameters and neighbor states.
A suspended member is not automatically forwarding. LACP standby and suspension are distinct states, and this output does not justify counting both links.
An up logical bundle proves at least one usable member, not that every configured interface successfully joined.
`(P)` means the physical interface is in the port-channel, not that it is merely discovered and unused.
Two switches have identical link settings for Port-channel5, but neither member joins after both ends were configured `channel-group 5 mode passive`. Which change directly starts LACP negotiation without forcing a static channel?
LACP active sends negotiation PDUs; passive responds. Two passive peers do not initiate an exchange, while active/passive or active/active can negotiate a bundle.
PAgP and LACP are different protocols. Mixing the negotiation modes does not resolve a passive/passive LACP pair.
Allowed VLANs concern trunk forwarding and do not cause passive LACP peers to initiate PDUs.
Static `on` does not negotiate LACP and may mismatch a passive LACP peer, risking incorrect bundling.
`show etherchannel summary` displays `Po37(SU)`, `Gi1/0/1(P)`, and `Gi1/0/2(I)` after a link replacement. Which conclusion is supported?
`(P)` denotes a port in the aggregate; `(I)` marks a physical interface standing alone. The logical port-channel may be usable with fewer members than intended.
Logical port-channel up does not prove all configured physical interfaces joined the aggregate; member state must be inspected individually.
`(I)` is an individual-port state and does not, by itself, identify the spanning-tree or protection reason for failure.
`S` in Port-channel summary indicates a Layer 2 bundle, not a routed Layer 3 interface or an SVI.
At a supply depot, the migration lead increased the LACP member count for port-channel 4 but observes one large TCP transfer not reaching total summed link rates. Which explanation is correct?
EtherChannel uses a load-balancing hash to select member links per flow/key, so many distinct flows can use aggregate capacity. One long flow often stays on one member to preserve ordering.
LACP aggregates interfaces into a logical forwarding channel; it is more than media testing.
Per-packet round-robin is not the standard Cisco LACP load-distribution guarantee and can reorder packets.
A single hashed flow is not generally able to consume all physical member links as one logical high-rate lane.
or Guarantee your success by buying the full version which covers the full latest pool of questions. (760 Questions, Last Updated on Nov 4, 2026)
Please check your mailbox for a message from support@examlabs.com and follow the directions.
