Administrative private vlan trunk normal vlans none

Administrative private-vlan trunk normal VLANs: none
Administrative private-vlan trunk associations:
3 (VLAN0003) 301 (VLAN0301)
Administrative private-vlan trunk mappings: none
Operational private-vlan: none
Operational Normal VLANs: none
Trunking VLANs Enabled: ALL
Pruning VLANs Enabled: 2-1001

61
pVLAN Edge (Protected Port) Feature
 The PVLAN edge (protected port)
feature has only local significance to
the switch (unlike pVLANs), and there
is no isolation provided between two
protected ports located on different
switches.
 A protected port does not forward any
traffic to any other port that is also a
protected port on the same switch.
 Traffic cannot be forwarded between
protected ports at L2, all traffic passing
between protected ports must be
forwarded through an L3 device.
Switch(config-if)# switchport protected

62
Configuring Link
Aggregation with
Etherchannel

63
EtherChannel Technology
 Up to 8 physical links can be
bundled into a single logical
EtherChannel link.
 Usually EtherChannel is used for
trunk links.
 Configuration applied to port channel
interface affects all physical
interfaces assigned to the port
channel.
 Load balancing takes place between
the physical links in an
EtherChannel.
 EtherChannels can be L2 or L3
interfaces.

64
EtherChannel Management Protocols
 Port Aggregation Protocol (PAgP) is a Cisco-proprietary protocol that aids in
the automatic creation of Fast EtherChannel links.
• When an EtherChannel link is configured using PAgP, PAgP packets are sent between
Fast EtherChannel-capable ports to negotiate the forming of a channel.
• When PAgP identifies matched Ethernet links, it groups the links into an EtherChannel. Spanning
tree adds the EtherChannel as a single bridge port.
 Link Aggregation Control Protocol (LACP) is part of an IEEE specification
(802.3ad) that also enables several physical ports to be bundled together to
form an EtherChannel.
• LACP enables a switch to negotiate an automatic bundle by sending LACP packets to
the peer.
• It performs a similar function as PAgP with Cisco EtherChannel.
• Because LACP is an IEEE standard, you can use it to facilitate EtherChannels in
mixed-switch environments. In a Cisco environment, both protocols are supported.

65
PAgP Modes
Mode Purpose
Auto Places an interface in a passive negotiating state in which the interface responds to the
PAgP packets that it receives but does not initiate PAgP negotiation (default).
Desirable Places an interface in an active negotiating state in which the interface initiates negotiations
with other interfaces by sending PAgP packets. Interfaces configured in the “on” mode do
not exchange PAgP packets.
On Forces the interface to channel without PAgP.
Non-silent If a switch is connected to a partner that is PAgP-capable, configure the switch interface for
non-silent operation. The non-silent keyword is always used with the auto or desirable mode.