Table Of Contents
Configuring Routing Between VLANs with IEEE 802.1Q Encapsulation
Restrictions for Configuring Routing Between VLANs with IEEE 802.1Q Encapsulation
Information About Configuring Routing Between VLANs with IEEE 802.1Q Encapsulation
Configuring Routing Between VLANs with IEEE 802.1Q Encapsulation
How to Configure Routing Between VLANs with IEEE 802.1Q Encapsulation
Configuring IP Routing over IEEE 802.1Q
Defining the VLAN Encapsulation Format
Assigning an IP Address to Network Interface
Monitoring and Maintaining VLAN Subinterfaces
Configuration Examples for Configuring Routing Between VLANs with IEEE 802.1Q Encapsulation
Configuring IP Routing over IEEE 802.1Q: Example
Feature Information for Configuring Routing Between VLANs with IEEE 802.1Q Encapsulation
Configuring Routing Between VLANs with IEEE 802.1Q Encapsulation
First Published: 2002Last Updated: February 22, 2011This chapter describes the required and optional tasks for configuring routing between VLANs with IEEE 802.1Q encapsulation.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for Configuring Routing Between VLANs with IEEE 802.1Q Encapsulation" section.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
Restrictions for Configuring Routing Between VLANs with IEEE 802.1Q Encapsulation
•
Information About Configuring Routing Between VLANs with IEEE 802.1Q Encapsulation
•
How to Configure Routing Between VLANs with IEEE 802.1Q Encapsulation
•
Configuration Examples for Configuring Routing Between VLANs with IEEE 802.1Q Encapsulation
•
Feature Information for Configuring Routing Between VLANs with IEEE 802.1Q Encapsulation
Restrictions for Configuring Routing Between VLANs with IEEE 802.1Q Encapsulation
Shared port adapters (SPAs) on Cisco ASR 1000 Series Aggregation Services Router have a limit of 8,000 TCAM entries, which limits the number of VLANs you can create on a single SPA.
Information About Configuring Routing Between VLANs with IEEE 802.1Q Encapsulation
•
Configuring Routing Between VLANs with IEEE 802.1Q Encapsulation
Configuring Routing Between VLANs with IEEE 802.1Q Encapsulation
The IEEE 802.1Q protocol is used to interconnect multiple switches and routers, and for defining VLAN topologies. The IEEE 802.1Q standard is extremely restrictive to untagged frames. The standard provides only a per-port VLANs solution for untagged frames. For example, assigning untagged frames to VLANs takes into consideration only the port from which they have been received. Each port has a parameter called a permanent virtual identification (Native VLAN) that specifies the VLAN assigned to receive untagged frames.
The main characteristics of IEEE 802.1Q are as follows:
•
Assigns frames to VLANs by filtering.
•
The standard assumes the presence of a single spanning tree and of an explicit tagging scheme with one-level tagging.
How to Configure Routing Between VLANs with IEEE 802.1Q Encapsulation
You can configure routing between any number of VLANs in your network.
This section documents the configuration tasks for each protocol supported with IEEE 802.1Q encapsulation. The basic process is the same, regardless of the protocol being routed. It involves the following tasks:
•
Enabling the protocol on the router
•
Enabling the protocol on the interface
•
Defining the encapsulation format as IEEE 802.1Q
•
Customizing the protocol according to the requirements for your environment
To configure IEEE 802.1Q of your network, perform the tasks described in the following sections:
•
Configuring IP Routing over IEEE 802.1Q (Required)
•
Monitoring and Maintaining VLAN Subinterfaces (Optional)
Configuring IP Routing over IEEE 802.1Q
IP routing over IEEE 802.1Q extends IP routing capabilities to include support for routing IP frame types in VLAN configurations using the IEEE 802.1Q encapsulation.
To route IP over IEEE 802.1Q between VLANs, you need to customize the subinterface to create the environment in which it will be used. Perform the tasks described in the following sections in the order in which they appear:
•
Defining the VLAN Encapsulation Format
•
Assigning an IP Address to Network Interface
Enabling IP Routing
IP routing is automatically enabled in the Cisco IOS XE software for routers. To reenable IP routing if it has been disabled, perform the following steps.
Once you have IP routing enabled on the router, you can customize the characteristics to suit your environment. If necessary, refer to the IP configuration chapters in the Cisco IOS XE IP Routing Protocols Configuration Guide, Release 2, for guidelines on configuring IP.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
ip routing
4.
end
DETAILED STEPS
Defining the VLAN Encapsulation Format
To define the encapsulation format as IEEE 802.1Q, perform the following steps.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface gigabitethernet card/spaslot/port.subinterface-number
4.
encapsulation dot1q vlanid
5.
end
DETAILED STEPS
Assigning an IP Address to Network Interface
An interface can have one primary IP address. To assign a primary IP address and a network mask to a network interface, perform the following steps.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface gigabitethernet card/spaslot/port.subinterface-number
4.
ip address ip-address mask
5.
end
DETAILED STEPS
Monitoring and Maintaining VLAN Subinterfaces
To indicate whether a VLAN is a native VLAN, perform the following steps.
SUMMARY STEPS
1.
enable
2.
show running-config interface type slot/port/number
3.
show interfaces port-channel channel-number etherchannel
4.
show etherchannel channel-number port-channel
5.
end
DETAILED STEPS
Configuration Examples for Configuring Routing Between VLANs with IEEE 802.1Q Encapsulation
Configuration examples for each protocols are provided in the following sections:
•
Configuring IP Routing over IEEE 802.1Q: Example
Configuring IP Routing over IEEE 802.1Q: Example
This configuration example shows IP being routed on VLAN 101:
!ip routing!interface gigabitethernet 4/1/1.101encapsulation dot1q 101ip addr 10.0.0.0 255.0.0.0!Additional References
The following sections provide references related to the Configuring Routing Between VLANs with IEEE 802.1Q Encapsulation feature.
Related Documents
Standards
Standard TitleNo new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
—
MIBs
RFCs
RFC TitleNo new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.
—
Technical Assistance
Feature Information for Configuring Routing Between VLANs with IEEE 802.1Q Encapsulation
Table 1 lists the features in this module and provides links to specific configuration information.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
Table 1 lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2009-2011 Cisco Systems, Inc. All rights reserved.
