Summarization of CCNA2 from

Module 5 to Module 6(Team 2)

Lecturer: Chhit Sokna

Teaching Assistant: Saray Kunly

Group members

• Yeng Visal
• Sor Sophanarith
• Sot Sochetra
• Reth SereyPiseth
 Module 5: STP Concept
• Spanning Tree Protocol (STP) is a loop prevention network protocols that allows for redundancy while
creating a loop free-layer 2 topology. IEE 802.1D is the original IEE MAC bridging standard for STP.
• STP logically block physicals loop in a L2 network, preventing frames from circling the network forever
and it can also compensate for failure in network by recalculating and opening up previous blocked
ports.
• Path redundancy provides multiple network services by eliminating the possibility of a single point of
failure. When multiple paths exist between two devices on an Ethernet network, and there is no spanning
tree implementation on the switches, a Layer 2 loop occurs.
• Without STP enabled, Layer 2 loops can form, causing broadcast, multicast, and unknown unicast
frames to loop endlessly. This can bring down a network within a very short amount of time, sometimes
in just a few seconds.
• A broadcast storm is an abnormally high number of broadcasts overwhelming the network during a
specific amount of time. Broadcast storms can disable a network within seconds by overwhelming
switches and end devices.
• STA stands for Spanning Tree Algorithm. STP stands for Spanning Tree Protocol. STA is the algorithm
that STP uses to prevent bridge loops.
• Using the STA, STP builds a loop-free topology in a four-step process:
1. Elect the root bridge
2. Elect the root ports
3. Elect designated ports
4. Elect alternate (blocked) ports
• During STA and STP functions, switches use Bridge Protocol Data Units (BPDUs) to share information
about themselves and their connections.
• Each BPDU contains a bridge ID (BID) that identifies which switch sent the BPDU.
• BID contains a priority value, an extended system ID, and the MAC address of the switch. The lowest
BID value is determined by the combination of these three fields.

• Bridge Priority: The default priority value for all Cisco switches is the decimal value 32768. The range
is 0 to 61440 in increments of 4096. A lower bridge priority is preferable. A bridge priority of 0 takes
precedence over all other bridge priorities.
• Extended System ID
• MAC address
1. Elect the root bridge.:
 Switch exchange BPDUs to build loop free topology.
 The switch with the lowest BID will be root bridge.
2. Elect the root port:
 Root ports are the ports that provide the shortest path to the root bridge.
 To elect the root ports, each bridge compares the BPDUs it receives from each port. The bridge
selects the port with the lowest root path cost as the root port.
 The root path is calculated based on the port values associated with port speeds for each switch port
along a given path.
  If multiple ports have the same root path cost, the bridge selects the port with the lowest bridge ID as
the root port.
3. Elect designated ports
 All ports on the root bridge are designated ports.
 If one end of a segment is a root port, the other end is a designated port.
 All ports attached to end devices are designated ports.
 On segments between two switches where neither of the switches is the root bridge, the port on the
switch with the least-cost path to the root bridge is a designated port.
4. Elect Alternate (Blocked) Ports
 All ports that are not root ports or designated ports are placed in the blocked state. Blocked ports
cannot forward traffic to other bridges.
• The difference version of STP

• Rapid Spanning Tree Protocol (RSTP), also known as IEEE 802.1w It is an improvement over the
original Spanning Tree Protocol (STP) and provides faster convergence times after network changes or
failures.
• The main reason to use RSTP instead of STP is because it provides faster convergence times after
network changes or failures. This is important because it can minimize the impact of network outages
on users and applications.
• The difference between RSTP and STP
1. The difference in port term:
 An alternate port is a backup port that can be used to forward traffic if the primary port fails.
 backup port in RSTP is a port that is used to forward traffic to a root bridge. It is selected ifthe
primary port to the root bridge fails.
2. The difference port term
 Discarding: The port is discarding all traffic.
3. RSTP new type link
 Point-to-point link: if the link between switches is full duplex.
 Shared link: if the link between switches is half duplex.
 Only P2P benefits from RSTP.
4. Faster topology Change
 Topology Change Notifications (TCNs): are special BPDUs that are used to notify other
switches about a topology change.
5. Faster convergence
 Using proposal/agreement and synchronization
 Module 6: EtherChannel

• A link aggregation technology is needed that allows redundant links between devices that will not be
blocked by STP. That technology is known as EtherChannel.
• EtherChannel is a link aggregation technology that groups multiple physical Ethernet links together into
one single logical link. It is used to provide fault-tolerance, load sharing, increased bandwidth, and
redundancy between switches, routers, and servers.
• When an EtherChannel is configured, the resulting virtual interface is called a port channel.
• The advantage of EtherChannel:
 Increased in bandwidth: by combining multiple physicals link into a single logical links.
 Redundancy: uses multiple logical links to provide redundancy.
 Load balancing: is achieved between links that are part of the same EtherChannel, improving the
network performance.
 Cost-Effective: There is no need to upgrade links to faster connections to increase bandwidth.
 Faulth-Tolerance: Even if one physical link fails within EtherChannel, the overall functionality is still
intact.
• Implementation Restrictions:
 Interface types cannot be mixed.
 Each EtherChannel can consist of up to eight compatibly configured Ethernet ports.
 The configuration of each EtherChannel group member port must be consistent on both devices.
 Each EtherChannel has a logical port channel interface. A configuration applied to the port channel
interface affects all physical interfaces that are assigned to that interface.
• AutoNegotiation Protocols can be form using the Pot Aggregation Protocol (PAgP) or the Link
Aggregation Control protocol (LACP).
• PAgP is a Cisco protocol that aids in the automatic creation of EtherChannel Links, It enables ports to
negotiate the formation of an EtherChannel.
• There are three modes for PAgP:
1. On: This mode forces the interface to channel without PAgP.
2. PAgP desirable: This mode places the interface in an active negotiating state.
3. PAgP auto: This mode places the interface in a passive negotiating state. The modes must be
compatible on each side. If they are not, the EtherChannel will not form.
• LACP, a standardized protocol, provide a similar functionality to PAgP and allows for interoperability
with devices from different vendors.
• LACP has three modes: on, LACP active, and LACP passive.
1. On mode forces the interface to channel without LACP. Interfaces configured in the on mode do
not exchange LACP packets.
2. LACP active mode places a port in an active negotiating state. In this state, the port initiates
negotiations with other ports by sending LACP packets.
3. LACP passive mode places a port in a passive negotiating state. In this state, the port responds
to the LACP packets that it receives but does not initiate LACP packet negotiation.
• Configuring EtherChannel using the Link Aggregation Control Protocol (LACP) is a
straightforward process. By following a few simple steps, you can set up EtherChannel and
benefit from increased bandwidth and redundancy:
1. Specify the interfaces that will compose the EtherChannel group using the "interface range"
command.
2. Create the port channel interface using the "channel-group" command in interface range
configuration mode. Specify the mode as active to enable LACP.
3. Make additional L2 settings on the port channel interface by entering port channel interface
configuration mode using the "interface port-channel" command.
 • Some guidelines and restrictions:
1. All ethernet interface must support EtherChannel.
2. Configure all interface in an EtherChannel to operate at the same speed and duplex mode.
3. All interfaces in the EtherChannel bundle must be assigned to the same VLAN or configured
as a trunk.
4. Ensure that the allowed range of VLANs is the same on all the interface in a trunking
EtherChannel.
6.3 Verify and Troubleshoot EtherChannel:
• Verify EtherChannel:
• To verify an EtherChannel configuration, you can use the following commands:
• show interfaces port-channel: Displays the general status of the port channel interface.
• show etherchannel summary: Displays one line of information per port channel.
• show etherchannel port-channel: Displays information about a specific port channel interface.
• show interfaces etherchannel: Can provide information about the role of a physical member interface
of the EtherChannel.
• Common Issues with EtherChannel Configurations:
• To avoid network problems related to EtherChannel, ensure that all interfaces within an EtherChannel
have the same configuration of speed and duplex mode, native and allowed VLANs on trunks, and
access VLAN on access ports. Common issues include:
• Assigned ports in the EtherChannel are not part of the same VLAN or not configured as trunks.
• Trunking was configured on some of the ports that make up the EtherChannel, but not all of them.
• The allowed range of VLANs is not the same, and PAgP is set to the auto or desirable mode.
• The dynamic negotiation options for PAgP and LACP are not compatibly configured on both ends of the
EtherChannel.
• Troubleshoot EtherChannel Example:
• Step 1. View the EtherChannel Summary Information: The output of the show etherchannel
summary command indicates that the EtherChannel is down.
• Step 2. View Port Channel Configuration: In the show run | begin interface port-channel output, more
detailed output indicates that there are incompatible PAgP modes configured on S1 and S2.
• Step 3. to correct the misconfiguration: change the PAgP mode on the EtherChannel to desirable.
Note that the order in which EtherChannel-related commands are entered is important. In this case,
interface Port-Channel 1 is removed and then re-added with the channel-group command, as opposed to
directly changed. This is because EtherChannel and STP must interoperate. If one tries to change the
configuration directly, STP errors cause the associated ports to go into blocking or errdisabled state.
• Step 4. Verify EtherChannel is Operational: The EtherChannel is now active as verified by the output
of the show etherchannel summary command.CP