Chapter 17 - IP Routing in the LAN Flashcards
True or False. Physical ports in an EtherChannel must all match speed and duplex.
True.
What is ROAS?
Router On A Stick - When you have a router that trunks all VLANs to a switch over a single connection.
What is an SVI?
- Switched Virtual Interface is a virtual interface that you can assign an IP address to on a layer 3 switch that corresponds to a VLAN.
- SVI functions at layer 3 whereas a VLAN functions at layer 2.
- They are used on layer 3 switches (except for management on layer 2 switches) to allow inter VLAN routing so that traffic that wants to go between VLANs doesn’t have to be sent back to a router to be routed since a PC in some VLAN can use the SVI as its gateway.
- They can also be setup on layer 2 switches for management.
What is a Subinterface?
- A Subinterface is a virtual router interface that is a sub division of a physical router interface.
- This allows each VLAN to have its own subinterface that can have an IP address configured against it, thereby allowing the VLAN to have an IP configured against it.
- This is used when trunking VLANs to a switch (e.g. ROAS)
True or False. You need to create a sub interface per VLAN if you want to use ROAS and also want to allow interVLAN routing.
True. However if you are using a layer-3 switch the IP address can be assigned directly to the VLAN interface (SVI) as they don’t necessarily need to be trunked anywhere else. In order to setup a sub interface you will:
- Use the ‘interface <type>' command to create the sub interface (e.g. fa0/1.10 for VLAN 10, fa0/1.20 for VLAN 20)
- Use the 'encapsulation dot1q <vlan_id>' command in subinterface configuration mode for the relevant subinterface to be associated with the relevant VLAN and enable 802.1Q
- Use the ip address command while in subinterface configuration mode for the relevant subinterface to assign a subnet to that subinterface, and by exension, the VLAN associated with that subinterface.</vlan_id></type>
How would you set up a subinterface for a VLAN?
- Use the ‘interface <type>' command to create the sub interface (e.g. fa0/1.10 for VLAN 10, fa0/1.20 for VLAN 20)</type>
- Use the ‘encapsulation dot1q <vlan_id>' command in subinterface configuration mode for the relevant subinterface to be associated with the relevant VLAN and enable 802.1Q</vlan_id>
- Use the ip address command while in subinterface configuration mode for the relevant subinterface to assign a subnet to that subinterface, and by exension, the VLAN associated with that subinterface.
True or False. If you have a subinterface number in use on one physical interface, you can’t then use that same subinterface number on another physical interface.
False. As long as the subinterface numbers are unique on the same physical interface this won’t cause problems. For example you could have fa0/1.10 and fa0/2.10 on the same router without a problem.
What two sequences of commands could you use to allow the native VLAN to be configured on a physical interface that currently acts as an 802.1Q trunk?
- Simply configure the subnet of the native VLAN on the physical interface using the ‘ip address’ command in interface configuration mode. All traffic in this subnet will be untagged when going across the trunk.
- Configure the subnet of the native VLAN on a subinterface but use the ‘encapsulation dot1q <vlan_ID> native' command to tell the router that this subinterface is used for the native VLAN and to define the native VLAN ID.</vlan_ID>
True or False. If an interface is down, any subinterfaces of that interface will also be down.
True. However you can change the state of a subinterface without it changing the state of the main interface. For example configuring shutdown on fa0/1.1 would set fa0/1.1 to administratively down but wouldn’t change the state of fa0/1.
What commands could you use to verify that ROAS is functioning how you want it?
- ‘show vlans’ - This allows you to ensure that all VLANs are being trunked over the correct interface and that all VLANs have the correct networks configured against them.
- ‘show ip route connected’ - This allows you to ensure that all networks are connected on the correct interfaces and sub interfaces.
If ROAS is not functioning how you want it to, what should you check?
- That each VLAN is configured on a subinterface on the router and these same VLANs exist on the device on the other side of the trunk.
- That the VLANs have not been pruned by VTP (VLAN Trunking Protocol) or blocked by STP (Spanning Tree Protocol).
- That each sub interface has the correct network configured against it.
- That the native VLAN (if used) is configured on a sub interface or implied on the physical interface on the router and is also configured on the device on the other side of the trunk.
- That none of the physical or sub interfaces are down or administratively down.
How would you enable IP routing on a layer 3 switch?
- (Optional and dependent on the model of switch) Use the ‘sdm prefer lanbase-routing’ command in global config which changes the switch forwarding ASIC settings to allow memory for IPv4 routing.
- (Optional depending on the outcome of the first step) Use the ‘reload’ command to reboot the switch and allow it to pickup the new setting.
- Once the switch has rebooted, use the ‘ip routing’ command to enable ip routing.
True or False. You require one SVI per VLAN that you would like to be routable at layer 3. (Decribe how to create an SVI)
True. To create the SVI you will:
- Use the ‘interface vlan <vlan_id>' command to create a VLAN interface and consequently give the switch's routing logic a virtual layer 2 interface that an SVI can be configured against.
- Use the 'ip address' command in VLAN interface configuration mode to configure an IP address on the SVI allowing the VLAN to be routable at layer 3.</vlan_id>
What is another name for an SVI?
A VLAN interface.
What could cause a VLAN interface to be down?
- The VLAN itsself is not defined on the local switch.
- The VLAN must have at least one up/up interface, this can be an access interface or a trunk interface for which the VLAN has not been pruned by VTP or blocked by STP.
- The VLAN itsself nor the VLAN interface cannot not be administratively disabled.