EtherChannel

CCNA · LAB 6

EtherChannel Configuration Using LACP, PAgP and Static

Objectives

• Configure EtherChannel using LACP, PAgP and Static modes.
• Understand the differences between LACP, PAgP and Static EtherChannel.
• Verify EtherChannel formation using Cisco IOS commands.
• Understand how EtherChannel provides increased bandwidth, redundancy and load balancing.

Theory

EtherChannel is a Cisco technology that allows multiple physical Ethernet links to be bundled together into one logical link. This increases available bandwidth and provides redundancy between network devices. If one physical link fails, traffic can continue through the remaining active links.

There are three main methods of configuring EtherChannel: LACP, PAgP and Static. Each method has different negotiation mechanisms and configuration modes.

1. LACP (Link Aggregation Control Protocol)

LACP is an open-standard protocol defined by IEEE 802.3ad, now incorporated into IEEE 802.1AX. It allows devices from different vendors to negotiate and establish an EtherChannel.

Mode	Description
Active	Actively sends LACP packets to negotiate an EtherChannel.
Passive	Waits for the other device to initiate LACP negotiation.

An EtherChannel using LACP can form when one side is Active and the other side is Active or Passive. Two Passive interfaces will not form a channel.

2. PAgP (Port Aggregation Protocol)

PAgP is a Cisco-proprietary protocol used to automatically negotiate EtherChannel formation between compatible Cisco devices.

Mode	Description
Desirable	Actively sends PAgP packets to negotiate an EtherChannel.
Auto	Waits for the other device to initiate PAgP negotiation.

PAgP forms an EtherChannel when at least one side is configured as Desirable. Two Auto interfaces will not form a channel.

3. Static EtherChannel

Static EtherChannel is manually configured without using a negotiation protocol. Both ends must be configured with the same channel settings.

Configuration	Description
Mode on	Manually forces the physical interfaces to join an EtherChannel without negotiation.

Comparison of EtherChannel Protocols

Feature	LACP	PAgP	Static
Standard	IEEE 802.3ad / 802.1AX	Cisco proprietary	No negotiation protocol
Modes	Active / Passive	Desirable / Auto	On
Negotiation	Yes	Yes	No
Vendor support	Multi-vendor	Cisco devices	Compatible devices with matching static configuration

How EtherChannel Load Balancing Works

EtherChannel distributes traffic across its active member links using a hashing algorithm. The algorithm can use information such as source and destination MAC addresses, IP addresses or TCP/UDP port numbers, depending on the switch configuration.

Traffic is not normally distributed packet by packet across all links. Instead, traffic flows are assigned to member links based on the hashing calculation. This helps maintain packet order while sharing traffic across the available links.

Network Topology

Fig 1 — EtherChannel topology using LACP, PAgP and Static configuration

Interface and EtherChannel Mode

Sl. No	Switches	Ports	Port Channel	EtherChannel Type
1	Switch0 and Switch1	Fa0/1 - Fa0/2	Po1	LACP
		Fa0/3 - Fa0/4	Po2	Static
		Fa0/5 - Fa0/6	Po3	PAgP
2	Switch2 and Switch3	Fa0/1 - Fa0/2	Po1	LACP
		Fa0/5 - Fa0/6	Po3	PAgP

Configuration Commands

1. Switch0 and Switch1 Configuration

Switch0 and Switch1

enable
configure terminal

! LACP EtherChannel - Port Channel 1
interface range fa0/1-2
 switchport mode trunk
 channel-group 1 mode active
 exit

interface port-channel 1
 switchport mode trunk
 no shutdown
 exit

! Static EtherChannel - Port Channel 2
interface range fa0/3-4
 switchport mode trunk
 channel-group 2 mode on
 exit

interface port-channel 2
 switchport mode trunk
 no shutdown
 exit

! PAgP EtherChannel - Port Channel 3
interface range fa0/5-6
 switchport mode trunk
 channel-group 3 mode desirable
 exit

interface port-channel 3
 switchport mode trunk
 no shutdown
 exit

end
write memory

2. Switch2 and Switch3 Configuration

Switch2 and Switch3

enable
configure terminal

! LACP EtherChannel - Port Channel 1
interface range fa0/1-2
 switchport mode trunk
 channel-group 1 mode active
 exit

interface port-channel 1
 switchport mode trunk
 no shutdown
 exit

! PAgP EtherChannel - Port Channel 3
interface range fa0/5-6
 switchport mode trunk
 channel-group 3 mode desirable
 exit

interface port-channel 3
 switchport mode trunk
 no shutdown
 exit

end
write memory

Important: Apply the Switch0 and Switch1 configuration separately on both switches. Likewise, apply the Switch2 and Switch3 configuration separately on both switches. The connected switches must have matching channel-group numbers, compatible protocols and compatible interface settings.

Verification Commands & Outputs

After configuring EtherChannel on both ends, use the following commands to check whether the port channels have formed successfully.

1. Verify EtherChannel Summary

Switch# show etherchannel summary

Flags:  D - down        P - bundled in port-channel
        I - stand-alone s - suspended
        H - Hot-standby (LACP only)
        R - Layer3       S - Layer2
        U - in use       f - failed to allocate aggregator

Group  Port-channel  Protocol    Ports
------+-------------+-----------+-------------------------
1      Po1(SU)       LACP        Fa0/1(P) Fa0/2(P)
2      Po2(SU)       -           Fa0/3(P) Fa0/4(P)
3      Po3(SU)       PAgP        Fa0/5(P) Fa0/6(P)

Explanation: The SU status indicates that the Layer 2 port channel is in use. The P flag beside each interface indicates that the physical interface is successfully bundled into the EtherChannel.

2. Verify EtherChannel Details

Switch# show etherchannel detail

Group state = L2
Ports: 2   Maxports = 8
Port-channels: 1 Max Port-channels = 16

Port state = Port-channel Ag-Inuse
Protocol = LACP

Ports in the group:
-------------------
Port: Fa0/1
Port state = Up Mstr In-Bndl

Port: Fa0/2
Port state = Up Mstr In-Bndl

This command displays detailed information about the EtherChannel groups, member interfaces and negotiation protocols. The exact output depends on the switch model and IOS version.

3. Verify LACP Counters

Switch# show lacp counters

Port       LACP PDU       Marker PDU
           Sent  Recv     Sent  Recv
Fa0/1      100   100      0     0
Fa0/2      100   100      0     0

4. Verify PAgP Counters

Switch# show pagp counters

Port       PAgP PDU       Marker PDU
           Sent  Recv     Sent  Recv
Fa0/5      100   100      0     0
Fa0/6      100   100      0     0

5. Verify LACP Neighbors

Switch# show lacp neighbor

Flags: S - Device is requesting Slow LACPDUs
       F - Device is requesting Fast LACPDUs
       A - Active   P - Passive

Channel group 1 neighbors

Partner's information:

                 Partner   Partner
Port      Flags  System ID Port Number
Fa0/1     SA     xxxx.xxxx.xxxx  1
Fa0/2     SA     xxxx.xxxx.xxxx  2

Note: The outputs above are illustrative examples. Actual counters, system IDs, flags and port states will differ depending on the switch model, configuration and lab environment. Some Packet Tracer switch models may not support every detailed verification command.

Learning Outcomes

Learned how to configure EtherChannel using LACP, PAgP and Static modes.

Understood the differences between LACP, PAgP and Static EtherChannel, including their negotiation methods and configuration modes.

Learned how EtherChannel provides increased bandwidth and redundancy by combining multiple physical links into one logical link.

Understood that traffic is load balanced across member links using a hashing algorithm rather than being distributed packet by packet.

Learned how to verify EtherChannel operation using show commands and identify whether interfaces are successfully bundled.

Spanning Tree Protocol

CCNA · LAB 5

Spanning Tree Protocol and Configuring PortFast

Objectives

• Identify the Root Bridge, Link Cost, Root Port, Designated Port, and Alternate (Blocked) Port in an STP topology.
• Understand how Spanning Tree Protocol prevents Layer 2 switching loops.
• Configure PortFast on switch ports connected to end devices such as servers.
• Verify STP operation and PortFast configuration using Cisco IOS commands.

Theory

Spanning Tree Protocol (STP) is a Layer 2 protocol used in switched networks to prevent switching loops. It identifies redundant paths and blocks selected ports to ensure that there is only one active forwarding path between network segments.

1. Root Bridge

• The Root Bridge is the central reference switch in the STP topology.
• It is elected based on the lowest Bridge ID (Bridge Priority + MAC Address).
• The default bridge priority is 32768.
• All path calculations in the network start from the Root Bridge.
• Every active STP topology has only one Root Bridge per VLAN or spanning-tree instance.

2. Link Cost

• Link Cost is a value assigned to each interface to determine the best path to the Root Bridge.
• Lower cost means a more preferred path.
• It is based on interface bandwidth: higher bandwidth generally has lower STP cost.
• Switches use the accumulated path cost to calculate the best route toward the Root Bridge.

Interface Name	Interface Speed	STP Cost
Ethernet	10 Mbps	100
FastEthernet	100 Mbps	19
GigabitEthernet	1 Gbps	4
TenGigabitEthernet	10 Gbps	2

3. Root Port

• The Root Port is the port on a non-root switch that has the lowest-cost path to the Root Bridge.
• Each non-root switch has only one Root Port per spanning-tree instance.
• It operates in a forwarding state.

4. Designated Port

• A Designated Port is the port on a network segment that provides the best path to the Root Bridge.
• There is one Designated Port per network segment.
• It operates in a forwarding state.
• It sends and receives BPDUs for that segment.

5. Alternate (Blocked) Port

• An Alternate Port provides a backup path to the Root Bridge.
• It does not forward normal user traffic while in the blocking/discarding state.
• It continues to receive BPDUs.
• If the active topology changes, it may transition to a forwarding state.

6. PortFast

• PortFast allows an access port connected to an end device, such as a server or PC, to move immediately to the forwarding state instead of waiting through normal STP transitions.
• It reduces the time required for an end device to access the network after the link comes up.
• PortFast should normally be enabled only on ports connected to end devices, not switch-to-switch links.

Network Topology

Fig 1 — Spanning Tree Protocol topology

Root Bridge Election Details

To identify the Root Bridge, use the show spanning-tree command on each switch. Note down the Bridge Priority and MAC Address.

Sl.No	Switch	Priority	MAC Address
1	S1	32769	0060.7094.A032
2	S2	32769	0009.7C16.25EE
3	S3	32769	00D0.9757.60B6
4	S4	32769	0060.47E9.B26A

Since all switches have the same Bridge Priority, the switch with the lowest MAC address becomes the Root Bridge.

Root Bridge: S2 — MAC Address: 0009.7C16.25EE

STP Port Roles and Link Cost

Use show spanning-tree on each switch to identify the Root Port, Designated Port, Alternate Port, and their corresponding costs.

Sl.No	Device	Port	Role	Cost
1	S1	Fa0/1	Root	19
		Fa0/2	Designated	19
		Fa0/3	Alternate (Blocked)	19
2	S2	Fa0/1	Designated	19
		Fa0/2	Designated	19
		Fa0/3	Designated	19
3	S3	Fa0/1	Root	19
		Fa0/2	Alternate (Blocked)	19
		Fa0/3	Alternate (Blocked)	19
		Fa0/4	Designated	19
4	S4	Fa0/1	Root	19
		Fa0/2	Designated	19
		Fa0/3	Designated	19

Link Cost Information:

• S1–S2: Cost 19
• S1–S3: Cost 19
• S1–S4: Cost 19
• S2–S3: Cost 19

Note: STP cost is assigned per interface. The switch calculates the total path cost by adding the costs of the links along the path to the Root Bridge. It is not simply the cost of an entire cable.

Configuration Commands

1. Identify the Root Bridge

Switch 1

enable

! Display STP information
show spanning-tree

! Note the Bridge ID and Root ID
! Compare the Bridge Priority and MAC Address

Switch 2

enable

show spanning-tree

! Check whether this switch is the Root Bridge

Switch 3

enable

show spanning-tree

! Identify the Root Port and path cost

Switch 4

enable

show spanning-tree

! Identify the Root Port and path cost

2. Configure PortFast on Server Port

Switch – Interface Connected to Server

enable
configure terminal

! Select the port connected to the server
interface FastEthernet0/4

! Configure the port as an access port
switchport mode access

! Enable PortFast
spanning-tree portfast

no shutdown

end
write memory

Verification Commands & Outputs

1. Verify Root Bridge

S2# show spanning-tree

VLAN0001
  Spanning tree enabled protocol ieee
  Root ID    Priority    32769
             Address     0009.7C16.25EE
             This bridge is the root

  Bridge ID  Priority    32769
             Address     0009.7C16.25EE

2. Verify Root Port and Link Cost

S1# show spanning-tree

Interface        Role Sts Cost      Prio.Nbr Type
---------------- ---- --- --------- -------- ----------------
Fa0/1            Root FWD 19        128.1    P2p
Fa0/2            Desg FWD 19        128.2    P2p
Fa0/3            Altn BLK 19        128.3    P2p

S3# show spanning-tree

Interface        Role Sts Cost      Prio.Nbr Type
---------------- ---- --- --------- -------- ----------------
Fa0/1            Root FWD 19        128.1    P2p
Fa0/2            Altn BLK 19        128.2    P2p
Fa0/3            Altn BLK 19        128.3    P2p
Fa0/4            Desg FWD 19        128.4    P2p

3. Verify Designated Ports on Root Bridge

S2# show spanning-tree

Interface        Role Sts Cost      Prio.Nbr Type
---------------- ---- --- --------- -------- ----------------
Fa0/1            Desg FWD 19        128.1    P2p
Fa0/2            Desg FWD 19        128.2    P2p
Fa0/3            Desg FWD 19        128.3    P2p

4. Verify STP Summary

S1# show spanning-tree summary

Switch is in rapid-pvst mode
Root bridge for: VLAN0001
PortFast Default is disabled
PortFast Edge BPDU Guard Default is disabled
Portfast Edge BPDU Filter Default is disabled
Loopguard Default is disabled
EtherChannel misconfiguration guard is enabled

5. Verify PortFast Configuration

S1# show spanning-tree interface Fa0/4 detail

Port 4 (FastEthernet0/4) of VLAN0001 is designated forwarding
  Port path cost 19
  Port priority 128, Port Identifier 128.4
  The port is in the portfast mode
  Link type is point-to-point by default

S1# show running-config

interface FastEthernet0/4
 switchport mode access
 spanning-tree portfast

Verification checklist:

• S2 should be identified as the Root Bridge.
• Every non-root switch should have one Root Port per STP instance.
• Designated Ports should be in forwarding state.
• Alternate Ports should be in blocking/discarding state.
• Link costs should match the interface speeds and configured STP cost method.
• PortFast should be enabled on the interface connected to the server.

Important: The verification outputs are illustrative. Actual port roles and costs depend on the physical topology, STP mode, interface configuration, and switch model.

Learning Outcomes

Understood how STP elects a Root Bridge based on Bridge ID, consisting of priority and MAC address.

Learned how link cost is determined by interface bandwidth and how switches use path cost to select the best route to the Root Bridge.

Identified Root Ports, Designated Ports, and Alternate (Blocked) Ports in a switched network.

Understood how STP prevents Layer 2 switching loops by blocking redundant paths.

Learned the difference between forwarding and blocking port states.

Configured PortFast on an access port connected to a server to allow faster transition to forwarding.

Verified STP topology, port roles, link costs, and PortFast configuration using Cisco IOS show commands.

VTP and DTP

CCNA · LAB 4

Dynamic Trunking and Virtual Trunking Protocol

Objectives

• Understand Dynamic Trunking Protocol (DTP) and how switches automatically negotiate trunk connections.
• Configure and understand the three VTP modes: Server, Client, and Transparent.
• Verify trunk connections and automatic VLAN distribution between switches.

Theory

Dynamic Trunking Protocol (DTP) is a Cisco proprietary protocol used to automatically negotiate whether a switch port should become a trunk port or remain an access port. It simplifies trunk configuration between Cisco switches.

Common DTP Modes:

Mode	Description
Dynamic Auto	Passively waits for the neighboring switch to initiate trunk negotiation. It forms a trunk when connected to a port configured as trunk or dynamic desirable.
Dynamic Desirable	Actively attempts to establish a trunk connection with the neighboring switch.
Trunk	Forces the interface to operate as a trunk port.
Access	Forces the interface to operate as an access port.

VLAN Trunking Protocol (VTP) is a Cisco proprietary Layer 2 protocol used to distribute VLAN information between switches in the same VTP domain. It reduces the need to manually create VLANs on every switch by synchronizing VLAN databases through trunk links.

Three VTP Modes:

VTP Mode	Description	Function
Server	Can create, modify, and delete VLANs and advertise these changes to other switches in the VTP domain.	Create and distribute VLANs
Client	Receives VLAN information from VTP servers but cannot create, modify, or delete VLANs.	Receive VLAN information
Transparent	Maintains its own independent VLAN database and forwards VTP advertisements without synchronizing its own VLAN database.	Independent VLAN management

Important: All switches participating in the same VTP domain must have the same domain name. Trunk links are required for VTP advertisements to travel between switches.

Network Topology

Fig 1 — Network topology

Interface Details & VTP Modes

Sl.No	Device	Interface	VTP Mode
1	S1	Gi1/0/1	Server
2	S2	Gi1/0/1	Transparent
		Gi1/0/2
3	S3	Gi1/0/1	Client

Configuration Commands

1. VTP Server Configuration

Switch 1 – Server

enable
configure terminal

! Configure VTP domain and mode
vtp domain CCNA
vtp mode server

! Create VLANs
vlan 10
 name Engineering
exit

vlan 20
 name Doctor
exit

vlan 30
 name Teacher
exit

! Configure trunk interface
interface GigabitEthernet1/0/1
 switchport mode trunk
 no shutdown

end

2. VTP Transparent Configuration

Switch 2 – Transparent

enable
configure terminal

! Configure VTP domain and mode
vtp domain CCNA
vtp mode transparent

! Configure trunk interfaces
interface range GigabitEthernet1/0/1-2
 switchport mode trunk
 no shutdown

end

3. VTP Client Configuration

Switch 3 – Client

enable
configure terminal

! Configure VTP domain and mode
vtp domain CCNA
vtp mode client

! Configure trunk interface
interface GigabitEthernet1/0/1
 switchport mode trunk
 no shutdown

end

4. DTP Dynamic Desirable and Dynamic Auto

Example – Configure DTP on two connected switches

! On Switch 1
enable
configure terminal

interface GigabitEthernet1/0/1
 switchport mode dynamic desirable
 no shutdown

end

! On Switch 2
enable
configure terminal

interface GigabitEthernet1/0/1
 switchport mode dynamic auto
 no shutdown

end

Verification Commands & Outputs

1. Verify VTP Server on S1

S1# show vtp status

VTP Version                     : 2
Configuration Revision          : 3
Maximum VLANs supported locally : 1005
Number of existing VLANs        : 8
VTP Operating Mode              : Server
VTP Domain Name                 : CCNA

S1# show vlan brief

VLAN Name                             Status
---- -------------------------------- ---------
1    default                          active
10   Engineering                      active
20   Doctor                           active
30   Teacher                          active

2. Verify VTP Transparent on S2

S2# show vtp status

VTP Operating Mode              : Transparent
VTP Domain Name                 : CCNA

3. Verify VTP Client on S3

S3# show vtp status

VTP Operating Mode              : Client
VTP Domain Name                 : CCNA

S3# show vlan brief

VLAN Name                             Status
---- -------------------------------- ---------
1    default                          active
10   Engineering                      active
20   Doctor                           active
30   Teacher                          active

4. Verify Trunk Connections

S1# show interfaces trunk

Port        Mode         Encapsulation  Status
Gi1/0/1     on           802.1q         trunking

S2# show interfaces trunk

Port        Mode         Encapsulation  Status
Gi1/0/1     on           802.1q         trunking
Gi1/0/2     on           802.1q         trunking

5. Verify DTP Negotiation

S1# show dtp interface Gi1/0/1

! Displays DTP information for the selected interface.
! Check the operational mode and negotiation status.
! Exact output depends on switch model and IOS version.

6. General Verification Checklist

Commands to verify the lab

show vtp status
show vlan brief
show interfaces trunk
show dtp interface
show running-config

Check the following:

• All switches have the same VTP domain name: CCNA.
• S1 operates in VTP Server mode.
• S2 operates in VTP Transparent mode.
• S3 operates in VTP Client mode.
• Trunk links are successfully established between switches.
• VLANs 10, 20, and 30 are automatically learned by S3 through VTP advertisements.

Note: S2 in Transparent mode maintains its own VLAN database. It forwards VTP advertisements between switches but does not synchronize its own VLAN database with S1. The example outputs are illustrative and may vary depending on the switch model and IOS version.

Learning Outcomes

Understood the purpose of Dynamic Trunking Protocol and how switches negotiate trunk connections.

Learned the four DTP modes: Dynamic Auto, Dynamic Desirable, Trunk, and Access.

Understood the differences between VTP Server, Client, and Transparent modes.

Configured VTP domain settings and created VLANs on a VTP Server switch.

Understood how VTP advertisements distribute VLAN information through trunk links.

Verified VTP modes, VLAN information, and trunk connections using Cisco IOS show commands.

CCNA · LAB 3

Intervlan Routing

Objectives

• Configure intervlan routing using : Layer 3 Switch (SVI Method), Routed Ports Method (Physical Interfaces as L3) ,Router on a Stick(ROAS)
• Understanding the advantages and disadvantage of each of the technique used for intervlan routing

Theory

PCS in different Vlans cannot communicate with each other. To make Communication between two vlans we need a L3 device that routes traffic between different Vlans

Method	How it Works	Advantages	Disadvantages
Router-on-a-Stick (ROAS)	One router interface with multiple subinterfaces using 802.1Q VLAN tagging.	Cost-effective, uses a single router port, easy to configure in labs.	Single point of failure, limited scalability, and the router link can become a bottleneck.
SVI (Layer 3 Switch)	VLAN interfaces (SVIs) are created on a multilayer switch to perform inter-VLAN routing.	Fast hardware-based routing, scalable, and no external router is required for local routing.	Requires a Layer 3 switch, higher initial cost, and more complex configuration.
Legacy Router (Multiple Interfaces)	Each VLAN connects to a separate physical router interface, with each interface acting as its VLAN's gateway.	Simple concept and easy to understand.	Not scalable, requires many physical router ports, and is expensive for larger networks.

Network Topology

Fig 1 — Network topology

Interface Details & IP Addresses

Sl.No	Device	Interface	IP Address
1	MLS	Fa0/0	192.168.10.1
		Fa0/1	192.168.20.1
2	R1	Gi0/0	192.168.10.1
		Gi0/1	192.168.20.1
3	S1	Fa0/3	NA
		Fa0/4	NA
4	R2	Gi0/0.10	192.168.10.1
		Gi0/0.20	192.168.20.1
5	S1	Fa0/3	NA
		Fa0/4	NA

Configuration Commands

1. Router-on-a-Stick (ROAS) Method

Switch

enable
configure terminal

vlan 10
 name VLAN10
vlan 20
 name VLAN20

interface FastEthernet0/1
 switchport mode access
 switchport access vlan 10

interface FastEthernet0/2
 switchport mode access
 switchport access vlan 20

interface FastEthernet0/3
 switchport mode trunk
 switchport trunk allowed vlan 10,20

end

Router

enable
configure terminal

interface GigabitEthernet0/0/0
 no shutdown

interface GigabitEthernet0/0/0.10
 encapsulation dot1Q 10
 ip address 192.168.10.1 255.255.255.0

interface GigabitEthernet0/0/0.20
 encapsulation dot1Q 20
 ip address 192.168.20.1 255.255.255.0

end

2. Routed Ports Method

Switch

enable
configure terminal

vlan 10
 name VLAN10
vlan 20
 name VLAN20

interface FastEthernet0/1
 switchport access vlan 10
 switchport mode access

interface FastEthernet0/2
 switchport access vlan 20
 switchport mode access

interface FastEthernet0/3
 switchport access vlan 10
 switchport mode access

interface FastEthernet0/4
 switchport access vlan 20
 switchport mode access

end

Router

enable
configure terminal

ip routing

interface FastEthernet0/3
 no switchport
 ip address 192.168.10.1 255.255.255.0
 no shutdown

interface FastEthernet0/4
 no switchport
 ip address 192.168.20.1 255.255.255.0
 no shutdown

end

3. Layer 3 Switch (SVI) Method

L3 Switch

enable
configure terminal

vlan 10
 name VLAN10
vlan 20
 name VLAN20

ip routing

interface FastEthernet0/1
 switchport mode access
 switchport access vlan 10

interface FastEthernet0/2
 switchport mode access
 switchport access vlan 20

interface Vlan10
 ip address 192.168.10.1 255.255.255.0
 no shutdown

interface Vlan20
 ip address 192.168.20.1 255.255.255.0
 no shutdown

end

Verification Commands & Outputs

1. Router-on-a-Stick (ROAS) Method

On Switch (S1)

S1# show vlan brief

VLAN Name                             Status    Ports
1    default                          active
10   VLAN10                           active    Fa0/1
20   VLAN20                           active    Fa0/2

S1# show interfaces trunk

Port        Mode         Encapsulation  Status        Native vlan
Fa0/3       on           802.1q         trunking      1

Port        Vlans allowed on trunk
Fa0/3       10,20

Port        Vlans allowed and active in management domain
Fa0/3       10,20

On Router (R2)

R2# show ip interface brief

Interface              IP-Address      OK? Method Status                Protocol
GigabitEthernet0/0/0   unassigned      YES unset  up                    up
GigabitEthernet0/0/0.10 192.168.10.1   YES manual up                    up
GigabitEthernet0/0/0.20 192.168.20.1   YES manual up                    up

R2# show ip route

Gateway of last resort is not set

C    192.168.10.0/24 is directly connected,
     GigabitEthernet0/0/0.10
L    192.168.10.1/32 is directly connected,
     GigabitEthernet0/0/0.10
C    192.168.20.0/24 is directly connected,
     GigabitEthernet0/0/0.20
L    192.168.20.1/32 is directly connected,
     GigabitEthernet0/0/0.20

PC1> ping 192.168.20.10

Reply from 192.168.20.10: bytes=32 time=1ms TTL=127
Reply from 192.168.20.10: bytes=32 time=1ms TTL=127
Reply from 192.168.20.10: bytes=32 time=1ms TTL=127
Reply from 192.168.20.10: bytes=32 time=1ms TTL=127

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)

2. Routed Ports Method

On Switch (S1)

S1# show vlan brief

VLAN Name                             Status    Ports
1    default                          active
10   VLAN10                           active    Fa0/1, Fa0/3
20   VLAN20                           active    Fa0/2, Fa0/4

On Multilayer Switch (MLS)

MLS# show ip interface brief

Interface              IP-Address      OK? Method Status                Protocol
FastEthernet0/3        192.168.10.1    YES manual up                    up
FastEthernet0/4        192.168.20.1    YES manual up                    up

MLS# show ip route

Gateway of last resort is not set

C    192.168.10.0/24 is directly connected, FastEthernet0/3
L    192.168.10.1/32 is directly connected, FastEthernet0/3
C    192.168.20.0/24 is directly connected, FastEthernet0/4
L    192.168.20.1/32 is directly connected, FastEthernet0/4

MLS# show running-config

!
ip routing
!
interface FastEthernet0/3
 no switchport
 ip address 192.168.10.1 255.255.255.0
!
interface FastEthernet0/4
 no switchport
 ip address 192.168.20.1 255.255.255.0
!

PC1> ping 192.168.20.10

Reply from 192.168.20.10: bytes=32 time=1ms TTL=127
Reply from 192.168.20.10: bytes=32 time=1ms TTL=127
Reply from 192.168.20.10: bytes=32 time=1ms TTL=127
Reply from 192.168.20.10: bytes=32 time=1ms TTL=127

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)

3. Layer 3 Switch (SVI) Method

On Multilayer Switch (MLS)

MLS# show vlan brief

VLAN Name                             Status    Ports
1    default                          active
10   VLAN10                           active    Fa0/1
20   VLAN20                           active    Fa0/2

MLS# show ip interface brief

Interface              IP-Address      OK? Method Status                Protocol
Vlan10                 192.168.10.1    YES manual up                    up
Vlan20                 192.168.20.1    YES manual up                    up
FastEthernet0/1        unassigned      YES unset  up                    up
FastEthernet0/2        unassigned      YES unset  up                    up

MLS# show ip route

Gateway of last resort is not set

C    192.168.10.0/24 is directly connected, Vlan10
L    192.168.10.1/32 is directly connected, Vlan10
C    192.168.20.0/24 is directly connected, Vlan20
L    192.168.20.1/32 is directly connected, Vlan20

MLS# show running-config

!
ip routing
!
interface Vlan10
 ip address 192.168.10.1 255.255.255.0
!
interface Vlan20
 ip address 192.168.20.1 255.255.255.0
!

PC1> ping 192.168.20.10

Reply from 192.168.20.10: bytes=32 time=1ms TTL=127
Reply from 192.168.20.10: bytes=32 time=1ms TTL=127
Reply from 192.168.20.10: bytes=32 time=1ms TTL=127
Reply from 192.168.20.10: bytes=32 time=1ms TTL=127

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)

Learning Outcomes

Understood the advantage and disadvantage of various intervlan technology

Verify configurations using Cisco IOS show commands and test connectivity between different VLANs using ping.

CCNA · LAB 02

VLANS

Objectives

• Configuring VLAN
• Understanding Access port, Native VLAN , Trunk port and Vlan numbers

Theory / Background

• VLANS are used to logically segment a network at Layer 2, even when everything is connected to the same physical switch infrastructure. The goal is control—over traffic, security, and scalability.
• VLAN ID identifies and separates VLANs on a switch (0 and 4095 is reserved, 1 is default, 1006-4096 is extended VLANS.
  
• Trunking port(tagged port) : it carries multiple VLANS over the same physical connection. It uses 802.1q or ISL
• Access port(untagged port): it carries a single VLAN on a single physical interface Native VLAN: The native VLAN is the VLAN on a trunk port whose traffic is sent without VLAN tagging (untagged).

Network Topology

Fig 1 — Network topology

Configuration Commands

Switch_1

interface FastEthernet0/1                                                                      
switchport mode trunk
interface FastEthernet0/2
switchport mode trunk
interface FastEthernet0/3
switchport access vlan 20
switchport mode access
interface FastEthernet0/4
switchport access vlan 20
switchport mode access
interface FastEthernet0/5
switchport access vlan 30
switchport mode access
interface FastEthernet0/6
switchport mode trunk

Switch_2

interface FastEthernet0/1
 switchport mode trunk
interface FastEthernet0/2
 switchport access vlan 10
 switchport mode access
interface FastEthernet0/3
 switchport access vlan 30
 switchport mode access
interface FastEthernet0/4
 switchport access vlan 30
 switchport mode access

Switch_3

interface FastEthernet0/1
switchport mode trunk
interface FastEthernet0/2
switchport access vlan 10
switchport mode access
interface FastEthernet0/3
switchport access vlan 10
switchport mode access
interface FastEthernet0/4
switchport access vlan 20
switchport mode access

Verification Commands & Outputs

Show vlan Show interface status

Notice that PCS in same vlan can communicate with each pther but PCS in different vlans cannot communicate with each other

Learning Outcomes

Understood the basic configuration of vlans

Understood access and trunk ports, native vlans

CCNA · LAB 01

Basic Device Configuration

Objectives

• Understanding the differnce between User EXEC Mode,Privileged Exec Mode and Global Configuration Mode
• Configuring basic device setup(username,passwords,banner.etc)
• Understanding the difference between Password,and Secret

Theory / Background

• User Exec Mode it is the first mode when we enter the networking device. It allows basic commands and does not allow change in configuration. It is represented by >
• Privileged Exec ModeProvides more advanced commands including debugging and the viewing of detailed device information. It is represented by #
• Global Configuration Mode is the CLI mode in which you can begin to configure the device. It is represented by config
  
• Password is used to protect access to a networking device by requiring users to enter a password before accessing certain modes or connecting to the device. It helps prevent unauthorized access.
• Secret is used to secure privileged EXEC mode on a networking device. It stores the password in an encrypted form and provides better security than the regular password command.

Network Topology

Fig 1 — Network topology

Configuration Commands

Switch

en
conf t
hostname SWITCH_1
banner motd !NOT PERMITTED TO ACCESS WITHOUT PERMISSION!
username sk priviledge 15 password sksk
username sks priviledge 15 secret sksk
line console 0
login local
wr

Router

en
conf t
hostname ROUTER_1
banner motd !NOT PERMITTED TO ACCESS WITHOUT PERMISSION!
username sk priviledge 15 password sksk
username sks priviledge 15 secret sksk
line console 0
login local
wr

Verification Commands & Outputs

show running-config | sec username

username sk privilege 15 password 0 sksk
username sks secret 5 $1$mERr$TkCGNxXhxXu3Phdk/9PPS.

Notice the difference between enable password and secret. The secret encrypts the password using MD5 algorithm while passwords are stored in plain text. To encrypt password we can use enable service password-encryption command in configuration mode

Learning Outcomes

Understood the basic configuration of network devices

Understood different modes in cisco CLI

Difference between password and secret

 Smart Car parking system