Ch5 InterVLAN Routing Flashcards
interVLAN Routing
process of forwarding network traffic between VLANs using a layer 3 network device or routed ports
router-on-a-stick
router configuration where a single physical interface routes traffic between multple VLANs on a network; does not scale beyond 50 VLANs
subinterfaces
software based virtual interfaces associated/linked to a single physical (master) interface
Command Needed to Activate VLAN routing on 2960s
sdm prefer lanbase-routing
Legacy InterVLAN Switch Config
vlan _first_vlan_id interface _interface_id switchport mode access switchport access vlan _first_vlan_id end --repeat for additional VLANs--
Legacy InterVLAN Routing
interface _interface_id
ip address _ip_address subnet_mask
no shutdown
–repeat for additional VLANs–
Router on a Stick Router Setup
Configuring subinterfaces
interface _interface_id.subinterface_id (g0/.2)
encapsulation 1dotq _vlan_id
ip address _ip_address subnet_mask
–repeat for all subinterfaces needed–
interface interface_id_for“master” _interface
no shutdown - activates all subinterfaces
Verifying Subinterfaces Setup on Router (2)
show vlan
show ip route
Verify Switch Configuration
show interface _interface_id switchport
Verify Router Configuration
show interfaces
show running-config
–both useful to check if encapsulation 1dotq is set correctly
Where are Layer 3 Routed Ports Implemented
Between Distribution and Core Layer
Spanning Tree
Protocol used to shut down redundant loops while maintaining flexibility and redundancy in inter-switch connections
Reasons to Configure SVIs
- Provide a gateway for a VLAN
- Provide Layer 3 IP connectivity to a switch
- Support routing protocol and bridging configurations
Advantages of SVI
- Faster than router on a stick or legacy
- No need for external links from switch to router.
- Not limited to one link; EtherChannels can be used between switches to increase bandwidth
- Much lower latency
encapsulation 1dotq _vlan_id
command used to ready subinterfaces for travel on 802.1q trunks
routed port
Physical port that acts similarily to an interface on a router; not associated with a particularly VLAN and does not support subinterfaces
no switchport
command used on routed ports to allow configuration of them for routing
Configure Static Route on Catalyst 2960
sdm prefer lanbase-routing ip routing (activates IP routing) ip route 0.0.0.0 0.0.0.0 {next hop IP or exit-interface}
ip route _ip_address subnet_mask {next hop ip or exit interface
Troubleshooting VLANs (3)
Must be defined across all switches.
Must be enabled on trunk ports.
Ports must be assigned to correct VLANs
Troubleshooting SVIs (3)
Must have correct IP address and subnet.
SVIs must be up.
SVIs must match with VLAN number
Troubleshooting Routing (2)
Routing must be enabled
Each interface or network should be added to routing protocol
Troubleshooting Hosts (2)
Hosts must have correct IP and subnet
Hosts must have a default gateway associated with an SVI or routed port.