Inter-VLAN Routing
Inter-VLAN Routing is the process of allowing communication between different VLANs in a
network
Methods of Inter-VLAN Routing
1. Router-on-a-Stick (RoAS)
o A single physical router interface handles multiple VLANs using subinterfaces.
o Each subinterface is assigned an IP address and tagged with the VLAN ID using
802.1Q encapsulation.
2. Layer 3 Switch (SVI - Switch Virtual Interfaces)
o A Layer 3 switch creates virtual interfaces for each VLAN.
o Routing happens internally on the switch without needing an external router.
.Hardware على مستوى الـRouting لسرعة الـCEF االعتماد على
Assume:
VLAN 10: [Link]/24
VLAN 20: [Link]/24
Router interface: GigabitEthernet0/0
On Router:
interface GigabitEthernet0/0
no shutdown
interface GigabitEthernet0/0.10
encapsulation dot1Q 10
ip address [Link] [Link]
interface GigabitEthernet0/0.20
encapsulation dot1Q 20
ip address [Link] [Link]
On Switch:
interface FastEthernet0/1
switchport mode trunk
Layer 3 Switch Configuration Example
ip routing
interface vlan 10
ip address [Link] [Link]
no shutdown
interface vlan 20
ip address [Link] [Link]
no shutdown
Gateway Redundancy
FHRP (First Hop Redundancy Protocol) is a family of protocols that provide gateway
redundancy for hosts in a LAN. The goal is to ensure that if the primary gateway fails, another
device can take over seamlessly without requiring manual reconfiguration on the hosts.
Why FHRP?
Hosts typically have one default gateway.
If that gateway fails, connectivity to other networks breaks.
FHRP solves this by creating a virtual IP and MAC address shared among multiple
routers.
Types of FHRP
1. HSRP (Hot Standby Router Protocol) – Cisco proprietary
Active/Standby model.
o
o Virtual IP is configured; one router is active, the other is standby.
o Uses hello packets to monitor state.
2. VRRP (Virtual Router Redundancy Protocol) – Open standard
Similar to HSRP but supports multiple vendors.
o
o Master/Backup model.
3. GLBP (Gateway Load Balancing Protocol) – Cisco proprietary
o Provides redundancy and load balancing.
o Multiple routers can actively forward traffic using different virtual MACs.
HSRP Example
On CoreSw1:
interface vlan 10
ip address [Link] [Link]
standby 1 ip [Link]
standby 1 priority 110
standby 1 preempt
On CoreSw2:
interface vlan 10
ip address [Link] [Link]
standby 1 ip [Link]
standby 1 priority 100
standby 1 preempt
Virtual IP is the default gateway for hosts.
Preempt allows a higher-priority router to take over when it comes back online.
Design for Networking:
Best Practice: For large networks, use Layer 3 switches at the core layer for inter-VLAN routing
and redundancy (e.g., HSRP/VRRP), also to configure Stacking or virtual Switching System
(VSS)
Key Differences
Feature Stacking VSS
Physical/Logical Physical stack cables Logical link over high-speed ports
Scale Up to 8 switches 2 chassis
Layer Access/Distribution Core/Distribution
Management Single IP Single IP
Redundancy Yes Yes
CEF (Cisco Express Forwarding)
CEF uses a Forwarding Information Base (FIB) and Adjacency Table to make packet forwarding
decisions in hardware rather than software.
tshooting Enterprise Networking :
task #1 : why pc 10.10 can’t ping to 20.20
task#2 : convert static route to RIPv2
Routing Protocols
The two main types of routing protocols are dynamic and static.
Scope of Distance Vector is with Neighbors only
Scope of link state with All routers in area
A static route with a different Administrative Distance (AD) is used to create a backup or
"floating" route that is only used when the preferred, lower-AD route becomes unavailable
Scenario 1
ISP1 Gateway: [Link]/30
ISP2 Gateway: [Link]/30
LAN Subnet: [Link]/24 , [Link]/24
Goal:
Send LAN traffic to ISP1 as Primary ISP then then ISP2 in case ISP1 be down.
ip route [Link] [Link] [Link]
ip route [Link] [Link] [Link] 10
Scenario 2
ISP1 Gateway: [Link]/30
ISP2 Gateway: [Link]/30
LAN Subnet: [Link]/24 , [Link]/24
Goal:
Send specific LAN traffic ([Link]/24) to ISP1 as Primary ISP , LAN traffic
([Link]/24) to ISP2 as a load balancing between two ISPs.
Step 1 : Create ACLs for Each Subnet
access-list 101 permit ip [Link] [Link] any
access-list 102 permit ip [Link] [Link] any
Step 2: Create Route Maps
route-map PBR-ISP1 permit 10
match ip address 101
set ip next-hop [Link]
route-map PBR-ISP2 permit 10
match ip address 102
set ip next-hop [Link]
Step 3 : Apply Route Maps to Sub-Interfaces
interface GigabitEthernet0/0.10
encapsulation dot1Q 10
ip address [Link] [Link]
ip policy route-map PBR-ISP1
interface GigabitEthernet0/0.20
encapsulation dot1Q 20
ip address [Link] [Link]
ip policy route-map PBR-ISP2
Step 4: Default Routes
ip route [Link] [Link] [Link]
ip route [Link] [Link] [Link] 254
Result:
Traffic from [Link]/24 → ISP1.
Traffic from [Link]/24 → ISP2.
No automatic failover (if ISP1 fails, traffic from VLAN 10 will still try ISP1).
Automatic failover using IP SLA tracking.
IP SLA for ISP Reachability
ip sla 1
icmp-echo [Link] source-interface GigabitEthernet0/1
frequency 10
ip sla schedule 1 life forever start-time now
track 1 ip sla 1 reachability
ip sla 2
icmp-echo [Link] source-interface GigabitEthernet0/2
frequency 10
ip sla schedule 2 life forever start-time now
track 2 ip sla 2 reachability
Route Maps with IP SLA Failover
route-map PBR-ISP1 permit 10
match ip address 101
set ip next-hop verify-availability [Link] 1 track 1
set ip next-hop [Link]
route-map PBR-ISP2 permit 10
match ip address 102
set ip next-hop verify-availability [Link] 1 track 2
set ip next-hop [Link]
Result:
Traffic from [Link]/24 → ISP1 (failover to ISP2 if ISP1 fails).
Traffic from [Link]/24 → ISP2 (failover to ISP1 if ISP2 fails).