Table Of Contents
Prerequisites for MPLS VPN Half-Duplex VRF
Restrictions for MPLS VPN Half-Duplex VRF
Information about MPLS VPN Half-Duplex VRF
MPLS VPN Half-Duplex VRF Overview
How to Configure MPLS VPN Half-Duplex VRF
Configuring the Upstream and Downstream VRFs on the PE Router or the Spoke PE Router
Configuring the RADIUS Server for MPLS VPN Half-Duplex VRF Support
Verifying MPLS VPN Half-Duplex VRF Configuration
Configuration Examples for MPLS VPN Half-Duplex VRF
Configuring the Upstream and Downstream VRFs on the PE Router and the Spoke PE Router: Example
Configuring Half-Duplex VRF Support—Basic Configuration: Example
Configuring Hub-and-Spoke Routers with Half-Duplex VRFs: Example
ip vrf forwarding (interface configuration)
MPLS VPN Half-Duplex VRF
The Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN) Half-Duplex Virtual Routing and Forwarding (VRF) feature provides scalable hub-and-spoke connectivity for subscribers of an MPLS VPN service. This feature addresses the limitations previously imposed on hub-and-spoke topologies by removing the requirement of one VRF per spoke. This feature also ensures that subscriber traffic always traverses the central link between the wholesale service provider and the ISP, whether the subscriber traffic is being routed to a remote network by way of the upstream ISP or to another locally or remotely connected subscriber.
Feature History for MPLS VPN Half-Duplex VRF
Finding Support Information for Platforms and Cisco IOS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.
Contents
•
Prerequisites for MPLS VPN Half-Duplex VRF
•
Restrictions for MPLS VPN Half-Duplex VRF
•
Information about MPLS VPN Half-Duplex VRF
•
How to Configure MPLS VPN Half-Duplex VRF
•
Configuration Examples for MPLS VPN Half-Duplex VRF
Prerequisites for MPLS VPN Half-Duplex VRF
•
You must have a working MPLS core network.
Restrictions for MPLS VPN Half-Duplex VRF
•
In both the upstream and downstream VRFs, routing protocols are not supported on interfaces configured for half-duplex VRFs. Interfaces that are not configured for half-duplex VRFs, however, do not have this restriction for the upstream or downstream VRFs.
•
Half-duplex VRFs apply only to virtual access interfaces (VAIs) and virtual template interfaces (VTIs).
•
Only unnumbered interfaces are supported.
Information about MPLS VPN Half-Duplex VRF
To configure the MPLS VPN half-duplex VRF feature, you need to understand the following concepts:
•
MPLS VPN Half-Duplex VRF Overview
•
Reverse Path Forwarding Check
MPLS VPN Half-Duplex VRF Overview
The MPLS VPN Half-Duplex VRF feature provides the following benefits:
•
The MPLS VPN Half-Duplex VRF feature prevents local connectivity between subscribers at the spoke provider edge (PE) router and ensures that a hub site provides subscriber connectivity. Any sites that connect to the same PE router must forward intersite traffic using the hub site. This ensures that the routing done at the spoke site moves from the access-side interface to the network-side interface or from the network-side interface to the access-side interface, but never from the access-side interface to the access-side interface.
The MPLS VPN Half-Duplex VRF feature prevents situations where the PE router locally switches the spokes without passing the traffic through the upstream Internet service provider (ISP). This prevents subscribers from directly connecting to each other, which causes the wholesale service provider to lose revenue.
•
The MPLS VPN Half-Duplex VRF feature improves scalability by removing the requirement of one VRF per spoke. In prior releases, when spokes connected to the same PE router, each spoke was configured in a separate VRF to ensure that the traffic between the spokes traversed the central link between the wholesale service provider and the ISP. However, this solution was not scalable. When many spokes connected to the same PE router, configuration of VRFs for each spoke became quite complex and greatly increased memory usage. This was especially true in large-scale wholesale service provider environments that supported high-density remote access to Layer 3 VPNs.
Figure 1 shows a sample hub-and-spoke topology for MPLS VPN Half-Duplex VRF.
Figure 1 Hub-and-Spoke Topology for MPLS VPN Half-Duplex VRF
Upstream and Downstream VRFs
The MPLS VPN Half-Duplex VRF feature uses two unidirectional VRFs to forward IP traffic between the spokes and the hub PE router:
•
The upstream VRF forwards the IP traffic from the spokes toward the MPLS VPN backbone. This VRF typically contains only a default route but might also contain summary routes and multiple default routes. The default route points to the interface on the hub PE router that connects to the upstream ISP. The router dynamically learns about the default route from the routing updates that the hub PE router or home gateway sends. The upstream VRF also contains the VAIs that connect the spokes, but it contains no other local interfaces.
•
The downstream VRF forwards traffic from the MPLS core back to the spokes. This VRF contains Point-to-Point Protocol (PPP) peer routes for the spokes and per-user static routes received from the Authentication, Authorization, and Accounting (AAA) server. It also contains the routes imported from the hub PE router. These routes are the dynamically allocated VAIs of the subscribers associated with a particular service.
The router redistributes routes from the downstream VRF into Multiprotocol Border Gateway Protocol (MP-BGP). The spoke PE router typically advertises a summary route across the MPLS core for the connected spokes. The VRF configured on the hub PE router imports the advertised summary route.
Reverse Path Forwarding Check
The Reverse Path Forwarding (RPF) check ensures that an IP packet that enters a router uses the correct inbound interface. The MPLS VPN Half-Duplex VRF feature supports unicast RPF check on the spoke-side interfaces. Because different VRFs are used for downstream and upstream forwarding, the RPF mechanism ensures that source address checks occur in the downstream VRF.
How to Configure MPLS VPN Half-Duplex VRF
This section contains the following procedures:
•
Configuring the Upstream and Downstream VRFs on the PE Router or the Spoke PE Router (required)
•
Associating VRFs (required)
•
Configuring the RADIUS Server for MPLS VPN Half-Duplex VRF Support (optional)
•
Verifying MPLS VPN Half-Duplex VRF Configuration (optional)
Configuring the Upstream and Downstream VRFs on the PE Router or the Spoke PE Router
To configure the upstream and downstream VRFs on the PE router or on the spoke PE router, use the following procedure.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
ip vrf vrf-name
4.
rd route-distinguisher
5.
route-target {import | export | both} route-target-ext-community
DETAILED STEPS
Associating VRFs
The virtual template interface is used to create and configure a virtual access interface (VAI). After you define and configure the VRFs on the PE routers, associate each VRF with the following:
•
Interface or subinterface
•
Virtual template interface
To associate a VRF, enter the following commands on the PE router.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface virtual-template number
4.
ip vrf forwarding vrf-name1 [downstream vrf-name2]
5.
ip unnumbered type number
6.
exit
DETAILED STEPS
Configuring the RADIUS Server for MPLS VPN Half-Duplex VRF Support
To configure the downstream VRF for an AAA server, enter the following Cisco attribute value:
lcp:interface-config=ip vrf forwarding U downstream D
For more information about configuring a RADIUS server, see Configuring Virtual Template Interfaces.
Verifying MPLS VPN Half-Duplex VRF Configuration
To verify the MPLS VPN half-duplex VRF configuration, perform the following steps.
SUMMARY STEPS
1.
show ip vrf [brief | detail | interfaces | id] [vrf-name] [output-modifiers]
2.
show ip route vrf vrf-name
3.
show running-config [interface type number]
DETAILED STEPS
Step 1
show ip vrf [brief | detail | interfaces | id] [vrf-name] [output-modifiers]
Use this command to display information about all of the VRFs configured on the router, including the downstream VRF for each associated VAI.
Router# show ip vrfName Default RD InterfaceD 2:0 Loopback2Virtual-Access3 [D]Virtual-Access4 [D]U 2:1 Virtual-Access3Virtual-Access4show ip vrf detail vrf-name
Use this command to display detailed information about the VRF you specify, including all of the VAIs associated with the VRF.
If you do not specify a value for vrf-name, detailed information about all of the VRFs configured on the router appears, including all of the VAIs associated with each VRF.
The following example shows how to display detailed information for the VRF called vrf1.
Router# show ip vrf detail vrf1VRF D; default RD 2:0; default VPNID <not set>Interfaces:Loopback2 Virtual-Access3 [D] Virtual-Access4 [D]Connected addresses are not in global routing tableExport VPN route-target communitiesRT:2:0Import VPN route-target communitiesRT:2:1No import route-mapNo export route-mapVRF U; default RD 2:1; default VPNID <not set>Interfaces:Virtual-Access3 Virtual-Access4Connected addresses are not in global routing tableNo Export VPN route-target communitiesImport VPN route-target communitiesRT:2:1No import route-mapNo export route-map
Note
For a description of each output display field, see the "Command Reference" section.
Step 2
show ip route vrf vrf-name
Use this command to display the IP routing table for the VRF you specify, and information about the per-user static routes installed in the downstream VRF.
The following example shows how to display the routing table for the downstream VRF named D.
Router# show ip route vrf DRouting Table: DCodes: C - connected, S - static, R - RIP, M - mobile, B - BGPD - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter areaN1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2E1 - OSPF external type 1, E2 - OSPF external type 2i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS interarea* - candidate default, U - per-user static route, o - ODRP - periodic downloaded static routeGateway of last resort is not set2.0.0.0/8 is variably subnetted, 5 subnets, 2 masksU 2.0.0.2/32 [1/0] via 2.8.1.1S 2.0.0.0/8 is directly connected, Null0U 2.0.0.5/32 [1/0] via 2.8.1.2C 2.8.1.2/32 is directly connected, Virtual-Access4C 2.8.1.1/32 is directly connected, Virtual-Access3The following example shows how to display the routing table for the upstream VRF named U.
Router# show ip route vrf URouting Table: UCodes: C - connected, S - static, R - RIP, M - mobile, B - BGPD - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter areaN1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2E1 - OSPF external type 1, E2 - OSPF external type 2i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS interarea* - candidate default, U - per-user static route, o - ODRP - periodic downloaded static routeGateway of last resort is 100.0.0.20 to network 0.0.0.02.0.0.0/32 is subnetted, 1 subnetsC 2.0.0.8 is directly connected, Loopback2B* 0.0.0.0/0 [200/0] via 100.0.0.20, 1w5d
Note
For a description of each output display field, see the show ip route vrf command in the Cisco IOS Switching Services Command Reference document.
Step 3
show running-config [interface type number]
Use this command to display information about the virtual access interface you specify, including information about the upstream and downstream VRFs.
The following example shows how to display information about the interface named virtual-access 3.
Router# show running-config interface virtual-access 3Building configuration...Current configuration : 92 bytes!interface Virtual-Access3ip vrf forwarding U downstream Dip unnumbered Loopback2endThe following example shows how to display information about the interface named virtual-access 4.
Router# show running-config interface virtual-access 4Building configuration...Current configuration : 92 bytes!interface Virtual-Access4ip vrf forwarding U downstream Dip unnumbered Loopback2end
Configuration Examples for MPLS VPN Half-Duplex VRF
This section provides the following configuration examples:
•
Configuring the Upstream and Downstream VRFs on the PE Router and the Spoke PE Router: Example
•
Configuring Half-Duplex VRF Support—Basic Configuration: Example
•
Configuring Hub-and-Spoke Routers with Half-Duplex VRFs: Example
Configuring the Upstream and Downstream VRFs on the PE Router and the Spoke PE Router: Example
The following example configures an upstream VRF named U:
Router> enableRouter# configure terminalRouter(config)# ip vrf URouter(config-vrf)# rd 1:0Router(config-vrf)# route-target import 1:0The following example configures a downstream VRF named D:
Router> enableRouter# configure terminalRouter(config)# ip vrf DRouter(config-vrf)# rd 1:8Router(config-vrf)# route-target export 1:100Associating VRFs: Example
The following example associates the VRF named U with the virtual-template 1 interface and specifies the downstream VRF named D:
Router> enableRouter# configure terminalRouter(config)# interface virtual-template 1Router(config-if)# ip vrf forwarding U downstream DRouter(config-if)# ip unnumbered Loopback1Configuring Half-Duplex VRF Support—Basic Configuration: Example
In this example, local authentication is used; that is, the RADIUS server is not used.
This example and the "Configuring Hub-and-Spoke Routers with Half-Duplex VRFs: Example" section use the hub-and-spoke topology shown in Figure 2.
Figure 2 Sample Topology for Half-Duplex Configuration
ip vrf Drd 1:8route-target export 1:100!ip vrf Urd 1:0route-target import 1:0!ip cefvpdn enable!vpdn-group Uaccept-dialinprotocol pppoevirtual-template 1!interface Loopback2ip vrf forwarding Uip address 2.0.0.8 255.255.255.255!interface ATM2/0description Mze ATM3/1/2no ip addressno atm ilmi-keepalivepvc 0/16 ilmi!pvc 3/100protocol pppoe!pvc 3/101protocol pppoe!interface Virtual-Template1ip vrf forwarding U downstream Dip unnumbered Loopback2peer default ip address pool U-poolppp authentication chapConfiguring Hub-and-Spoke Routers with Half-Duplex VRFs: Example
The following example shows how to connect two Point-to-Point Protocol over Ethernet (PPPoE) clients to a single VRF pair on the spoke PE router named Lipno. Although both PPPoE clients are configured in the same VRF, all communication occurs using the hub PE router. Half-duplex VRFs are configured on the spoke PE. The client configuration is downloaded to the spoke PE from the RADIUS server.
Note
The wholesale provider can forward the user authentication request to the corresponding ISP. If the ISP authenticates the user, the wholesale provider appends the VRF information to the request that goes back to the PE router.
aaa new-model!aaa group server radius Rserver 22.0.20.26 auth-port 1812 acct-port 1813!aaa authentication ppp default group radiusaaa authorization network default group radius!ip vrf Ddescription Downstream VRF - to spokesrd 1:8route-target export 1:100!ip vrf Udescription Upstream VRF - to hubrd 1:0route-target import 1:0!ip cefvpdn enable!vpdn-group Uaccept-dialinprotocol pppoevirtual-template 1!interface Loopback2ip vrf forwarding Uip address 2.0.0.8 255.255.255.255!interface ATM2/0pvc 3/100protocol pppoe!pvc 3/101protocol pppoe!interface virtual-template 1no ip addressppp authentication chap!router bgp 1no synchronizationneighbor 100.0.0.34 remote-as 1neighbor 100.0.0.34 update-source Loopback0no auto-summary!address-family vpnv4neighbor 100.0.0.34 activateneighbor 100.0.0.34 send-community extendedauto-summaryexit-address-family!address-family ipv4 vrf Uno auto-summaryno synchronizationexit-address-family!address-family ipv4 vrf Dredistribute staticno auto-summaryno synchronizationexit-address-family!ip local pool U-pool 2.8.1.1 2.8.1.100ip route vrf D 2.0.0.0 255.0.0.0 Null0!radius-server host 22.0.20.26 auth-port 1812 acct-port 1813radius-server key ciscoAdditional References
The following sections provide references related to MPLS VPN Half-Duplex VRF.
Related Documents
Standards
Standards TitleNo new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
—
MIBs
RFCs
Technical Assistance
Command Reference
This section describes the following modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.3T command reference publications.
•
ip vrf forwarding (interface configuration)
ip vrf forwarding (interface configuration)
To associate a Virtual Private Network (VPN) routing/forwarding instance (VRF) with an interface or subinterface, use the ip vrf forwarding command in interface configuration mode. To disassociate a VRF, use the no form of this command.
ip vrf forwarding vrf-name [downstream vrf-name2]
no ip vrf forwarding vrf-name [downstream vrf-name2]
Syntax Description
Defaults
The default for an interface is the global routing table.
Command Modes
Interface configuration
Command History
Release Modification12.0(5)T
This command was introduced.
12.3(6)
This command was updated with the downstream keyword to support MPLS VPN Half-Duplex VRFs.
Usage Guidelines
•
Use this command to associate an interface with a VRF. Executing this command on an interface removes the IP address. The IP address should be reconfigured.
•
The downstream keyword is available on supported platforms with virtual interfaces.
•
The downstream keyword associates the interfaces with a downstream VRF, which enables Half Duplex VRF functionality on the interface. Some functions operate in the upstream VRF, while others operate in the downstream VRFs. The following functions operate in the downstream VRFs:
–
Point-to-Point Protocol (PPP) peer routes are installed in the downstream VRF.
–
Authentication, Authorization, and Accounting (AAA) per-user routes are installed in the downstream VRF.
–
A Reverse Path Forwarding (RPF) check is performed in the downstream VRF.
Examples
The following example shows how to link a VRF to ATM interface 0/0:
Router(config)# interface atm0/0Router(config-if)# ip vrf forwarding vpn1The following example associates the VRF named U with the virtual-template 1 interface and specifies the downstream VRF named D:
Router> enableRouter# configure terminalRouter(config)# interface virtual-template 1Router(config-if)# ip vrf forwarding U downstream DRouter(config-if)# ip unnumbered Loopback1Related Commands
show ip interface
To display the usability status of interfaces configured for IP, use the show ip interface command in privileged EXEC mode.
show ip interface [type number] [brief]
Syntax Description
type
(Optional) Interface type.
number
(Optional) Interface number.
brief
(Optional) Displays a summary of the usability status information for each interface.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The Cisco IOS software automatically enters a directly connected route in the routing table if the interface is usable. A usable interface can send and receive packets. If an interface is not usable, the directly connected routing entry is removed from the routing table. Removing the entry allows the software to use dynamic routing protocols to determine backup routes to the network, if any.
If the interface can provide two-way communication, the line protocol is marked "up." If the interface hardware is usable, the interface is marked "up."
If you specify an optional interface type, you see information for that specific interface.
If you specify no optional arguments, you see information on all the interfaces.
When an asynchronous interface is encapsulated with PPP or Serial Line Internet Protocol (SLIP), IP fast switching is enabled. A show ip interface command on an asynchronous interface encapsulated with PPP or SLIP displays a message indicating that IP fast switching is enabled.
Examples
The following example identifies a downstream VRF. The highlighted line (for documentation purposes only) identifies the downstream VRF.
Router# show ip interface vi 3Virtual-Access3 is up, line protocol is upInterface is unnumbered. Using address of Loopback2 (2.0.0.8)Broadcast address is 255.255.255.255Peer address is 2.8.1.1MTU is 1492 bytesHelper address is not setDirected broadcast forwarding is disabledOutgoing access list is not setInbound access list is not setProxy ARP is enabledLocal Proxy ARP is disabledSecurity level is defaultSplit horizon is enabledICMP redirects are always sentICMP unreachables are always sentICMP mask replies are never sentIP fast switching is enabledIP fast switching on the same interface is enabledIP Flow switching is disabledIP CEF switching is enabledIP Feature Fast switching turbo vectorIP VPN CEF switching turbo vectorVPN Routing/Forwarding "U"Downstream VPN Routing/Forwarding "D"IP multicast fast switching is disabledIP multicast distributed fast switching is disabledIP route-cache flags are Fast, CEFRouter Discovery is disabledIP output packet accounting is disabledIP access violation accounting is disabledTCP/IP header compression is disabledRTP/IP header compression is disabledPolicy routing is disabledNetwork address translation is disabledWCCP Redirect outbound is disabledWCCP Redirect inbound is disabledWCCP Redirect exclude is disabledBGP Policy Mapping is disabledTable 1 describes the significant fields shown in the display.
The following is sample output from the show ip interface brief command:
Router# show ip interface briefInterface IP-Address OK? Method Status ProtocolEthernet0 151.108.0.5 YES NVRAM up upEthernet1 unassigned YES unset administratively down downLoopback0 152.108.20.5 YES NVRAM up upSerial0 162.108.10.5 YES NVRAM up upSerial1 162.108.4.5 YES NVRAM up upSerial2 152.108.10.5 YES manual up upSerial3 unassigned YES unset administratively down downThe method field has the following possible values:
•
RARP or SLARP—Reverse Address Resolution Protocol (RARP) or Serial Line Address Resolution Protocol (SLARP) request
•
BOOTP—Bootstrap protocol
•
TFTP—Configuration file obtained from Trivial File Transfer Protocol (TFTP) server
•
manual—Manually changed by CLI command
•
NVRAM—Configuration file in nonvolatile RAM (NVRAM)
•
IPCP—ip address negotiated command
•
DHCP—ip address dhcp command
•
unassigned—No IP address
•
unset—Unset
•
other—Unknown
show ip vrf
To display the set of defined Virtual Private Network (VPN) routing/forwarding instances (VRFs) and associated interfaces, use the show ip vrf command in privileged EXEC mode.
show ip vrf [brief | detail | interfaces | id] [vrf-name] [output-modifiers]
Syntax Description
Defaults
When no keywords or arguments are specified, the command shows concise information about all configured VRFs.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to display information about VRFs. Two levels of detail are available:
•
The brief keyword (or no keyword) displays concise information.
•
The detail keyword displays all information.
To display information about all interfaces bound to a particular VRF, or to any VRF, use the interfaces keyword. To display information about VPN IDs assigned to a PE router, use the id keyword.
Examples
The following example displays information about all the VRFs configured on the router, including the downstream VRF for each associated VAI. The lines that are highlighted (for documentation purposes only) indicate the downstream VRF.
Router# show ip vrfName Default RD InterfaceD 2:0 Loopback2Virtual-Access3 [D]Virtual-Access4 [D]U 2:1 Virtual-Access3Virtual-Access4Table 2 describes the significant fields shown in the display.
Table 2 show ip vrf Field Descriptions
Field DescriptionName
Specifies the VRF name.
Default RD
Specifies the default route distinguisher.
Interfaces
Specifies the network interfaces.
The following example displays detailed information about all of the VRFs configured on the router, including all of the VAIs associated with each VRF:
Router# show ip vrf detailVRF D; default RD 2:0; default VPNID <not set>Interfaces:Loopback2 Virtual-Access3 [D] Virtual-Access4 [D]Connected addresses are not in global routing tableExport VPN route-target communitiesRT:2:0Import VPN route-target communitiesRT:2:1No import route-mapNo export route-mapVRF U; default RD 2:1; default VPNID <not set>Interfaces:Virtual-Access3 Virtual-Access4Connected addresses are not in global routing tableNo Export VPN route-target communitiesImport VPN route-target communitiesRT:2:1No import route-mapNo export route-mapTable 3 describes the significant fields shown in the display.
The following example shows the interfaces bound to a particular VRF:
Router# show ip vrf interfacesInterface IP-Address VRF ProtocolEthernet2 130.22.0.33 blue_vrf upEthernet4 130.77.0.33 hub upRouter#Table 4 describes the significant fields shown in the display.
The following is sample output that shows all the VPN IDs that are configured in the router and their associated VRF names and VRF route distinguishers (RDs):
Router# show ip vrf idVPN Id Name RD2:3 vpn2 <not set>A1:3F6C vpn1 100:1Table 5 describes the significant fields shown in the display.
Table 5 show ip vrf id Field Descriptions
Field DescriptionVPN ID
Specifies the VPN ID assigned to the VRF.
Name
Specifies the VRF name.
RD
Specifies the route distinguisher.
Related Commands
Glossary
BGP—Border Gateway Protocol. An interdomain routing protocol that replaces Exterior Gateway Protocol (EGP). BGP exchanges reachability information with other BGP systems. It is defined by RFC 1163.
CE router—customer edge router. A router that is part of a customer network and that interfaces to a provider edge (PE) router.
hub—The center of a star-topology network. A hub is a hardware or software device that contains multiple independent but connected modules of network and internetwork equipment. Hubs can be active (where they repeat signals sent through them) or passive (where they do not repeat, but merely split, signals sent through them).
MPLS—Multiprotocol Label Switching. A packet-forwarding technology, used in the network core, that applies data link layer labels to tell switching nodes how to forward data, resulting in faster and more scalable forwarding than network layer routing normally can do.
PE router—provider edge router. A router at the edge of a service provider network that interfaces to customer edge (CE) routers.
PPPoE—Point-to-Point Protocol over Ethernet. A protocol that provides the ability to connect a network of hosts over a simple bridging access device to a remote access concentrator or aggregation concentrator. Each host uses its own PPP stack, thus presenting the user with familiar user interfaces.
router—A network layer device that uses one or more metrics to determine the optimal path along which network traffic should be forwarded. Routers forward packets from one network to another based on network layer information.
static route—A route that is explicitly configured and entered into the routing table. Static routes take precedence over routes chosen by dynamic routing protocols.
VAI—virtual access interface. An instance of a unique virtual interface that is created dynamically and exists temporarily. Virtual access interfaces can be created and configured differently by different applications, such as virtual profiles and virtual private dialup networks. Virtual access interfaces are cloned from virtual template interfaces.
VPN—Virtual Private Network. A communication network that enables IP traffic to travel securely over a public TCP/IP network by encrypting all traffic from one network to another. A VPN uses tunneling to encrypt all information at the IP level.
VRF—A VPN routing/forwarding instance. A VRF consists of an IP routing table, a derived forwarding table, a set of interfaces that use the forwarding table, and a set of rules and routing protocols that determine what goes into the forwarding table. In general, a VRF includes the routing information that defines a customer VPN site that is attached to a PE router.
VTI—virtual template interface. A logical interface configured with generic configuration information for a specific purpose or configuration common to specific users, plus router-dependent information. The template takes the form of a list of Cisco IOS interface commands that are applied to virtual access interfaces, as needed.
Note
Refer to the Internetworking Terms and Acronyms for terms not included in this glossary.
CCIP, CCSP, the Cisco Arrow logo, the Cisco Powered Network mark, Cisco Unity, Follow Me Browsing, FormShare, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, Fast Step, GigaStack, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MGX, MICA, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, ScriptShare, SlideCast, SMARTnet, StrataView Plus, Stratm, SwitchProbe, TeleRouter, The Fastest Way to Increase Your Internet Quotient, TransPath, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website 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. (0402R)
Copyright ©2004 Cisco Systems, Inc. All rights reserved.


