cc/td/doc/product/software/ios121/121newft/121limit
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table Of Contents

Cisco MPLS VPN Mapping of RFC 1483 Routed Sessions

Feature Overview

Benefits

Comparison of Conventional VPNs and MPLS VPNs

Supported MPLS Features

Restrictions

Related Documents

New Terminology for MPLS

New Terminology for MPLS VPN Mapping of RFC 1483 Routed Sessions

Supported Platforms

Supported Standards, MIBs, and RFCs

Configuration Prerequisites

Configuration Tasks

Installing Cisco IOS Release 12.1(4)DA

Enabling Cisco Express Forwarding

Configuring a VPN Forwarding Routing Instance

Creating a Loopback Interface and Associating It with a VRF

Creating a Loopback Interface to be Associated with the Uplink Interface

Creating Uplink ATM Subinterfaces and VP Tunnels and Enabling MPLS

Configuring the PE to CE Interface

Configuring Routing Sessions

Verifying VPN Operation

Configuration Samples

Command Reference

Command Conventions

address-family

clear ip route vrf

exit-address-family

import map

ip route vrf

ip vrf

ip vrf forwarding

neighbor activate

rd

route-target

show ip bgp vpnv4

show ip cef vrf

show ip protocols vrf

show ip route vrf

show ip vrf

show tag-switching forwarding vrf

Debug Command

debug ip bgp


Cisco MPLS VPN Mapping of RFC 1483 Routed Sessions


This feature module describes the Cisco Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN) Mapping of RFC1483 Routed Sessions feature for all Cisco Digital Subscriber Line Access Multiplexers (DSLAMs) using the second-generation network interface module (NI-2). It includes information this new feature and supported platforms. This features first appears in Cisco IOS Release 12.1(4)DA.

This document contains the following sections:

Feature Overview

Supported MPLS Features

Supported Platforms

New Terminology for MPLS

Configuration Prerequisites

Configuration Tasks

Configuration Samples

Command Reference

Command Conventions

Debug Command

Feature Overview

The Cisco MPLS VPN Mapping of RFC 1483 Routed Sessions feature enables Cisco DSLAMs with NI-2 controller cards and connected customer premises equipment (CPE) to participate in MPLS VPNs. This feature promotes the rapid deployment of secure IP VPNs that enable revenue generating services such as:

Intranets

Extranets

Application and data hosting

Network commerce

Secure telecommuter access to corporate networks

Figure 1 shows an example of an MPLS VPN with a service provider (P) backbone network, service provider edge routers (PE), and customer edge routers (CE).

Figure 1

VPNs with a Service Provider Backbone

Benefits

In local area networks (LAN), IP-based intranets have had an impact on the way companies conduct business. Companies meet the needs of their customers, suppliers, and partners by using extranets (an intranet that encompasses multiple businesses). Using extranets, companies reduce business process costs through supply-chain automation, electronic data interchange (EDI), and content hosting services. Virtual Private Networks address these needs by providing secure, private network services over the public Internet.

Cisco provides Layer 2 mechanisms that enable Service Providers (SPs) to deploy VPNs.To meet the scalability challenges inherent in provisioning fully-meshed Layer 2 VPNs, SPs must:

Scale their networks to support an explosion of broadband subscribers.

Quickly deploy value-added services, such as secure telecommuter access and extranets that differentiate their positions in a competitive marketplace.

MPLS VPN Mapping of RFC 1483 Routed Sessions provides a solution to both of these problems:

1. Because MPLS VPNs are created in Layer 3, they are more scalable and easier to configure than Layer 2 VPNs.

2. MPLS VPNs offer an advanced, revenue-generating service.

The MPLS VPN mapping of RFC 1483 routed sessions also:

Leverage existing NI-2 based DSLAM hardware in the SP network

Provide a platform for the rapid deployment of managed IP services, including intranets and extranets

Reduce the cost of connecting branch offices, telecommuters, and mobile users to a corporate intranet

Provide a more cost-effective solution than private WANs constructed with leased lines

Comparison of Conventional VPNs and MPLS VPNs

Conventional VPNs

Conventional VPNs do not scale well. Layer 2 VPNs are provisioned by creating and maintaining a full mesh of tunnels or permanent virtual circuits among all sites belonging to a particular VPN, using:

IPSec

Layer 2 tunneling protocol (L2TP)

Layer 2 forwarding (L2F) protocol

generic routing encapsulation (GRE)

Frame Relay

ATM protocols

The resources and equipment required to provision and manage connection-based schemes cannot be supported in an SP network that must support hundreds or thousands of VPNs, each with multiple sites and thousands or tens of thousands of routes.

MPLS VPNs

MPLS VPNs offer all of the value of traditional VPNs. Furthermore, since MPLS VPNs are created in Layer 3, they are more scalable, and easier to configure and manage than Layer 2 VPNs.

MPLS VPNs offer:

Privacy and security equal to that provided by Layer-2 VPNs by limiting the distribution of a VPN's routes to only those routers that are members of the VPN

Seamless integration with customer intranets

Increased scalability over current VPN implementations

Easy management of VPN membership and provisioning of new VPNs for rapid deployment

Scalable any-to-any connectivity for extended intranets and extranets that encompass multiple businesses

Supported MPLS Features

The following features are supported to deliver MPLS VPN Mapping of RFC 1483 Routed Sessions:

IP Routing protocols:

Static routing

Routing Information Protocol (RIP)

Border Gateway Protocol (BGP)

Open Shortest Path First (OSPF)

IS-IS

Enhanced Interior Gateway Routing Protocol (EIGRP)

Interior Gateway Routing Protocol (IGRP)

MPLS Label Edge Router functionality (LER)

Routed termination of Multiprotocol Encapsulation over AAL5 (Commonly referred to as RFC 1483)

Cisco Express Forwarding (CEF)

Restrictions

This section describes restrictions to Cisco MPLS VPN mapping of RFC 1483 routed sessions.

Number of Configurable MPLS VPNs Limited to 50

Each IP DSL switch can support up to 50 MPLS VPNs.

Integrated Routing and Bridging Not Supported

MPLS VPN mapping of RFC 1483 routed sessions must not be confused with Integrated Routing and Bridging (IRB). IRB is not supported by MPLS VPN mapping of RFC 1483 routed sessions.

VPN Interfaces Restricted to Trunk Interfaces

Do not configure subtended interfaces for MPLS VPN services. Only trunk interfaces support MPLS VPN mapping of RFC 1483 routed sessions.

MPLS ATM-Label Switch Router Functionality Not Supported

IP DSL switches are not meant for use as MPLS ATM-Label Switch Routers (ATM-LSRs). When designing your network, keep in mind that IP DSL switches act only as Label Edge Routers (LER).

Performance Restrictions for MPLS VPN Traffic

MPLS VPN-enabled interfaces do not perform as well as switched VCs. Please take this into consideration when deploying MPLS VPNs in your networks.

Restricted Layer 3 Services

The following Layer 3 services are not supported in Cisco IOS Release 12.1(4)DA:

IP Quality of Service

IP Queueing

IP Multicast

Restricted MPLS Features

The following are MPLS-related features that are not a part of the MPLS VPN mapping of RFC 1483 routed sessions feature:

MPLS Traffic Engineering

MPLS Multicast

DSL Interface Limitations

In IP DSL switches, each DSL interface can support multiple Permanent Virtual Circuits (PVCs), but only one routed MPLS VC.

Configuration of MPLS VPN Mapping of RFC 1483 Routed Sessions not Supported by Cisco DSL Manager (CDM)

CDM users can provision switched VCs, but CDM does not support configuring routed termination of RFC 1483 sessions.

MPLS VPN Mapping of RFC 1483 Routed Sessions not Supported on the Eight-Port IDSL ITU-C Line Card

Routed termination of IDSL connections is not supported in Cisco IOS Release 12.1(4)DA.

Related Documents

Cisco IOS IP and IP Routing Configuration Guide, Release 12.1

Cisco MPLS Virtual Private Networks Feature Module

Cisco MPLS Virtual Private Network Enhancements Feature Module

Cisco IOS Switching Services Configuration Guide

New Terminology for MPLS

Table 1 lists old tag switching and more current MPLS terms:

Table 1 MPLS Terminology 

Old Designation
New Designation

Tag Switching

MPLS, Multiprotocol Label Switching

Tag (short for Tag Switching)

MPLS

Tag (item or packet)

Label

TDP (Tag Distribution Protocol)

LDP (Label Distribution Protocol)

Cisco TDP and LDP (MPLS Label Distribution Protocol) are nearly identical in function, but use incompatible message formats and some different procedures. Cisco now implements a standards compliant LDP.

Tag Switched

Label Switched

TFIB (Tag Forwarding Information Base)

LFIB (Label Forwarding Information Base)

TSR (Tag Switching Router)

LSR (Label Switching Router)

TSC (Tag Switch Controller)

LSC (Label Switch Controller)

ATM-TSR (ATM Tag Switch Router)

ATM-LSR (ATM Label Switch Router, such as the Cisco BPX 8650 switch)

TVC (Tag VC, Tag Virtual Circuit)

LVC (Label VC, Label Virtual Circuit)

XTag ATM (extended Tag ATM port)

XmplsATM (extended MPLS ATM port)


New Terminology for MPLS VPN Mapping of RFC 1483 Routed Sessions

DSLAMs running the MPLS VPN mapping of RFC 1483 routed sessions feature are referred to as IP DSL switches.

Supported Platforms

The following DSLAM platforms support MPLS VPN mapping of RFC 1483 routed sessions:

Cisco 6260 DSLAM with NI-2

Cisco 6160 DSLAM with NI-2

Cisco 6130 DSLAM with NI-2

Cisco 6015 DSLAM with NI-2

Supported Standards, MIBs, and RFCs

MIB Support

No new or modified MIBs are supported by this feature.

RFC Support

RFC 1163, A Border Gateway Protocol

RFC 1164, Application of the Border Gateway Protocol in the Internet

RFC 2283, Multiprotocol Extensions for BGP-4

RFC 2547, BGP/MPLS VPNs

Supported Standards

No new or modified standards are supported by this feature.

Configuration Prerequisites

Your network must be running the following services before you configure MPLS VPN mapping of RFC 1483 routed sessions:

MPLS in provider backbone routers

MPLS with VPN code running in provider edge (PE) routers

BGP in all routers providing an MPLS VPN service

Cisco Express Forwarding (CEF) in every MPLS-enabled router

RFC 1483 encapsulation on any DSL CPE devices participating in an MPLS VPN

IOS Release 12.1(4)DA on NI-2 based DSLAMs participating in MPLS VPNs

Configuration Tasks

This section describes the configuration tasks for enabling MPLS VPN mapping on supported DSLAM platforms.

Configuring MPLS VPN mapping of RFC 1483 routed sessions is similar to configuring MPLS VPNs on other Cisco MPLS platforms. For general MPLS VPN configuration tasks, examples, and command references, consult the MPLS Virtual Private Networks and MPLS Virtual Private Network Enhancements feature modules.

To enable MPLS VPN Mapping of RFC 1483 Routed Sessions, perform the following configuration tasks:

Installing Cisco IOS Release 12.1(4)DA

Enabling Cisco Express Forwarding

Configuring a VPN Forwarding Routing Instance

Creating a Loopback Interface and Associating It with a VRF

Creating a Loopback Interface to be Associated with the Uplink Interface

Creating Uplink ATM Subinterfaces and VP Tunnels and Enabling MPLS

Configuring the PE to CE Interface

Configuring Routing Sessions

Verifying VPN Operation

Installing Cisco IOS Release 12.1(4)DA

Refer to the software installation documentation for the DSLAM platform on which MPLS VPN mapping of RFC 1483 routed sessions will be installed.

Enabling Cisco Express Forwarding

To enable Cisco Express Forwarding (CEF) on NI-2 based DSLAMs, enter the following command:

Step
Command
Purpose

1.

DSLAM(config)#ip cef

This command enables Cisco Express Forwarding (CEF).

Command Usage Example

DSLAM(config)#ip cef
DSLAM(config)#end
DSLAM#

Configuring a VPN Forwarding Routing Instance

To define VPN forwarding routing instances (VRFs), use the following commands in router configuration mode on a PE router:

Step
Command
Purpose

1.

DSLAM(config)# ip vrf vrf-name

Enters VRF configuration mode and defines the VPN routing instance by assigning a VRF name.

2.

DSLAM(config-vrf)# rd route-distinguisher

Creates routing and forwarding tables.

3.

DSLAM(config-vrf)# route-target {import | export | both} route-target-ext-community

Creates a list of import and export route target communities for the specified VRF.

4.

DSLAM(config-vrf)# import map route-map

(Optional) Associates the specified route map with the VRF.

Command Usage Example

DSLAM(config)#ip vrf vpn1
DSLAM(config-vrf)#rd 100:1
DSLAM(config-vrf)#route-target export 100:1
DSLAM(config-vrf)#route-target import 100:1
DSLAM(config-vrf)#end
DSLAM#

Creating a Loopback Interface and Associating It with a VRF

To create a loopback interface and associate it with a VRF, enter the following commands:

Step
Command
Purpose

1.

DSLAM(config)#interface loopback loopback_interface_number

Creates a loopback interface to associate with the VRF.

2.

DSLAM(config-if)#ip vrf forwarding vrf-name

Associates the interface with the VRF.

3.

DSLAM(config-if)#ip address ip-address subnet-mask

Assigns an IP address to the loopback interface.

Command Usage Example

DSLAM(config)#interface Loopback1
DSLAM(config-if)#ip vrf forwarding vpn1
DSLAM(config-if)#ip address 6.6.6.6 255.255.255.255
DSLAM(config-if)#end
DSLAM#

Creating a Loopback Interface to be Associated with the Uplink Interface

You should configure a loopback interface on DSLAMs running MPLS VPN mapping of RFC 1483 routed sessions configured for label switching. This virtual interface is always active.

The IP address you assign to the loopback interface is used as the Label Distribution Protocol (LDP) identifier for the IP DSL switch.

If a loopback interface:

Does not exist—The LDP identifier is associated with the highest IP address configured on the IP DSL switch.

Is administratively shut down—All LDP sessions through the IP DSL switch restart.

Therefore, we recommend that you configure a loopback interface. You must associate the VRF with a routed interface using the following commands:

Step
Command
Purpose

1.

DSLAM(config)#interface loopback_interface_number

Enters interface configuration mode.

2.

DSLAM(config-if)#ip address ip-address subnet-mask

Assigns an IP address and subnet mask to the loopback interface.

Command Usage Example

DSLAM(config)#interface Loopback0
DSLAM(config-if)#ip address 172.16.1.6 255.255.255.255
DSLAM(config-if)#end

DSLAM#

Creating Uplink ATM Subinterfaces and VP Tunnels and Enabling MPLS

To create a VP tunnel from the MPLS uplink port to the Service Provider network, enter the following commands:

Step
Command
Purpose

1.

DSLAM(config)#interface atm slot/port

Enters interface configuration mode.

2.

DSLAM(config-if)#atm pvp vpi

Creates the VP tunnel that connecting the uplink interface to the SP network.

Note The vpi value created here must match that of the connected MPLS core router.

3.

DSLAM(config-if)#exit

Returns to global configuration mode.

4.

DSLAM(config)#interface atm slot/port.vpi point-to-point

Enters configuration mode for the PVP.

5.

DSLAM(config-subif)#ip unnumbered loopback loopback_interface_number

Enables IP processing for this subinterface.


Note Insert the loopback_interface_number parameter that you configured in Step 1 of the "Creating a Loopback Interface to be Associated with the Uplink Interface" section above.


6.

DSLAM(config-subif)#tag-switching ip

Enables MPLS for IPv4 packets on this subinterface.

Command Usage Example

DSLAM(config)#interface ATM0/1
DSLAM(config-if)#atm pvp 61
DSLAM(config-if)#tag-switching ip
DSLAM(config-if)#exit
DSLAM(config)#interface ATM0/1.61 point-to-point
DSLAM(config-subif)#ip unnumbered Loopback0
DSLAM(config-subif)#end

DSLAM#

Configuring the PE to CE Interface

To create the PE to CE DSL interface and configure it for membership in an MPLS VPN, enter the following commands:

Step
Command
Purpose

1.

DSLAM(config)#interface atm slot/port

Creates the ATM interface.

2.

DSLAM(config-if)#ip vrf forwarding vrf-name

Associates the DSL interface with the configured VRF.

3.

DSLAM(config-if)#ip unnumbered loopback loopback_interface_number

Enables IP unnumbered on the ATM interface and assigns the unnumbered interface to the loopback interface that you have created.

4.

DSLAM(config-if)#pvc vpi/vci

Creates an ATM PVC on the DSL interface.

5.

DSLAM(config-if-atm-vc)#encapsulation encapsulation_type

Configures the required RFC 1483 encapsulation on the DSL to IP DSL switch interface.

Note The default encapsulation type is aal5snap. Cisco 600 series CPE devices support only aal5snap encapsulation. The Cisco 827 supports both aal5snap and aal5mux ip encapsulation.

Command Usage Example

DSLAM(config)#interface ATM1/2
DSLAM(config-if)#ip vrf forwarding vpn1
DSLAM(config-if)#ip unnumbered Loopback1
DSLAM(config-if)#pvc 1/32
DSLAM(config-if-atm-vc)#encapsulation aal5snap
DSLAM(config-if-atm-vc)#end
DSLAM#

Configuring Routing Sessions

This section describes the routing protocol configuration tasks necessary to enable MPLS VPNs in your network.

To configure an operational MPLS VPN, you must:

Configure BGP routing sessions

Configure a MPLS core routing protocol (OSPF is used in the example in the Configuring MPLS Core Routing Protocols section below)

Configure a PE to CE routing instance (In the example below, RIP is used, but you can configure static routes or BGP routing sessions).

Configuring BGP Routing Sessions

To configure BGP routing sessions in a provider network, use the following commands in router configuration mode on the PE router:

Step
Command
Purpose

1.

DSLAM(config)# router bgp autonomous_system_number

Configures the BGP routing process with the autonomous system number passed along to other BGP routers.

2.

DSLAM(config-router)# neighbor {ip-address | peer-group-name} remote-as number

Specifies a neighbor's IP address or BGP peer group, identifying it to the local autonomous system.

3.

DSLAM(config-router)#neighbor ip-address update-source loopback-interface

Specifies a loopback interface as the source for routing updates.

4.

DSLAM(config-router)# address-family vpnv4 [unicast]

Defines IBGP parameters for VPNv4 Network Layer Reachability Information (NLRI) exchange.

5.

DSLAM(config-router-af)# neighbor address send-community both

Defines an IBGP session to exchange VPNv4 NLRIs.

6.

DSLAM(config-router-af)# neighbor address activate

Activates the advertisement of the IPv4 address family.

Command Usage Example

DSLAM(config)# router bgp 100
DSLAM(config-router)# neighbor 172.16.0.8 remote-as 100
DSLAM(config-router)# neighbor 172.16.0.8 update-source Loopback0
DSLAM(config-router)# address-family vpnv4
DSLAM(config-router-af)# neighbor 172.16.0.8 send-community both
DSLAM(config-router-af)# neighbor 172.16.0.8 activate
DSLAM(config-router-af)# exit-address-family

Configuring MPLS Core Routing Protocols

Though there are several routing protocols to choose from, the configuration example below uses OSPF as an IGP:

Step
Command
Purpose

1.

DSLAM(config)#router ospf process-id

Create an OSPF routing process between the IP DSL switch and the core MPLS routers.

2.

DSLAM(config-router)#network ipaddress wildcard-mask area area-id

Defines an interface on which OSPF runs and also defines the area ID for that interface.

For information on configuring other routing protocols, consult the Cisco IOS IP and IP Routing Command Reference for Cisco IOS Release 12.1.

Command Usage Example

DSLAM(config)#router ospf 6
DSLAM(config-router)#network 172.16.0.0 0.0.255.255 area 0
DSLAM(config-router)#end
DSLAM#

Configuring RIP PE to CE Routing Sessions

To configure BGP PE to CE routing sessions, use the following commands in router configuration mode on the PE router:

Step
Command
Purpose

1.

DSLAM(config)#router rip

Enables RIP.

2.

DSLAM(config-router)#address-family ipv4 [unicast] vrf vrf-name

Defines RIP parameters for PE to CE routing sessions.

Note The default is Off for auto-summary and synchronization in the VRF address-family submode.

3.

DSLAM(config-router-af)#redistribute bgp [autonomous-system] [metric metric-value] transparent

Redistributes VRF BGP routes into the VRF RIP table.

4.

DSLAM(config-router-af)# network ip_address_prefix

Enables RIP on the PE to CE link.

Command Usage Example

DSLAM(config)#router rip
DSLAM(config-router)# address-family ipv4 vrf vpn1
DSLAM(config-router-af)#redistribute bgp 100 metric transparent
DSLAM(config-router-af)#network 6.0.0.0
DSLAM(config-router-af)#exit-address-family
DSLAM(config-router)#end
DSLAM#

Verifying VPN Operation

To verify the proper operation of an MPLS VPN, use the following commands:

 
Command
Purpose

1.

DSLAM# show ip vrf

Displays the set of defined VRFs and interfaces.

2.

DSLAM# show ip vrf [{brief | detail | interfaces}] vrf-name

Displays information about defined VRFs and associated interfaces.

3.

DSLAM# show ip route vrf vrf-name

Displays the IP routing table for a VRF.

4.

DSLAM# show ip protocols vrf vrf-name

Displays the routing protocol information for a VRF.

5.

DSLAM# show ip cef vrf vrf-name

Displays the CEF forwarding table associated with a VRF.

6.

DSLAM# show ip interface interface-number

Displays the VRF table associated with an interface.

7.

DSLAM# show ip bgp vpnv4 all [tags]

Displays information about all BGPs.

8.

DSLAM# show tag-switching forwarding vrf vrf-name [prefix mask/length][detail]

Displays label forwarding entries that correspond to VRF routes advertised by the DSLAM.

Configuration Samples

This section provides sample configurations of MPLS VPN Mapping of RFC 1483 Routed Sessions.

The configuration samples represent a simple hub-and-spoke network with two adjacent IP DSL switches. Figure 2 illustrates the network topology for the sample configurations below.


Note Comments are highlighted with a series of three exclamation points. For example, !!!This is a comment.!!! Comments appear before the configurations they describe.


Figure 2 Simple Hub and Spoke MPLS VPN Network Diagram

Site 1-PE1 Configuration—Cisco 6160 DSLAM

hostname dsl-6
!
boot system flash:ni2-dslp5-mz.ni2_mpls.20000720
slot 1 ATUC-4FLEXIDMT
!
dsl-profile 4dmt2func
dmt training-mode standard
dmt overhead-framing mode1
dmt bitrate minimum interleaved downstream 8032 upstream 864
dmt bitrate maximum interleaved downstream 8032 upstream 864
!
network-clock-select 1 system
ip subnet-zero
!
!!!Define and configure the VRF. Refer to the "Configuring a VPN Forwarding Routing Instance" section.!!!
ip vrf vpn1
rd 100:1
route-target export 100:1
route-target import 100:1
!
!!!The following command enables Cisco Express Forwarding. See the "Enabling Cisco Express Forwarding" section.!!!
ip cef
!
atm address 47.0091.8100.0000.0010.06ec.9102.0010.06ec.9102.00
atm router pnni
no aesa embedded-number left-justified
node 1 level 56 lowest
 redistribute atm-static
!
!!!Create an uplink loopback interface. Refer to the "Creating a Loopback Interface to be Associated with the Uplink Interface" section.!!!
!
interface Loopback0
ip address 172.16.1.6 255.255.255.255
!
!!!Configure a loopback interface and associate it with a VRF. Refer to the "Creating a Loopback Interface and Associating It with a VRF" section.!!!

interface Loopback1
 ip vrf forwarding vpn1
ip address 6.6.6.6 255.255.255.255

interface ATM0/0
no ip address
atm cac service-category abr deny
atm maxvp-number 0
atm maxvc-number 4096
atm maxvci-bits 12
!
interface Ethernet0/0
ip address 10.1.1.56 255.255.255.0
!
interface ATM0/1
no ip address
no atm ilmi-keepalive
atm cac service-category abr deny

 !!!Create Uplink ATM Subinterfaces. Refer to the   "Creating Uplink ATM Subinterfaces and VP Tunnels and Enabling MPLS" section.!!!
atm pvp 61
atm pvp 62
atm pvp 67
!
!!!Create VP tunnels and enable MPLS. Refer to the "Creating Uplink ATM Subinterfaces and VP Tunnels and Enabling MPLS" section.!!!

interface ATM0/1.61 point-to-point
ip unnumbered Loopback0
tag-switching ip
!
!!!Create VP tunnels and enable MPLS. Refer to the "Creating Uplink ATM Subinterfaces and VP Tunnels and Enabling MPLS" section.!!!
!
interface ATM0/1.62 point-to-point
ip unnumbered Loopback0
 tag-switching ip
!
!!!Create VP tunnels and enable MPLS. Refer to the "Creating Uplink ATM Subinterfaces and VP Tunnels and Enabling MPLS" section.!!!
!
interface ATM0/1.67 point-to-point
ip unnumbered Loopback0
 tag-switching ip
!
!!!Create a DSL interface and associate it with a VRF. Refer to the "Configuring the PE to CE Interface" section.!!!
!
interface ATM1/2
ip vrf forwarding vpn1
 ip unnumbered Loopback1
dsl profile 4dmt2func
no atm ilmi-keepalive
pvc 1/32
!
!!!Configure OSPF as the MPLS core routing protocol. Configuring MPLS Core Routing Protocols
router ospf 6
network 172.16.0.0 0.0.255.255 area 0
 !
!!!Configure RIP PE to CE routing sessions. Refer to the "Configuring RIP PE to CE Routing Sessions" section.!!!
!
router rip
 address-family ipv4 vrf vpn1
redistribute bgp 100 metric transparent
network 6.0.0.0
no auto-summary
exit-address-family
!
!!!Configure BGP. Refer to the "Configuring BGP Routing Sessions" section.!!!
!
router bgp 100
no synchronization
 neighbor 172.16.1.7 remote-as 100
neighbor 172.16.1.7 update-source Loopback0
!
address-family ipv4 vrf vpn1
redistribute connected
redistribute static
redistribute rip
no auto-summary
no synchronization
exit-address-family
!
 !!!Enable PE to PE routing sessions. Refer to the   "Configuring BGP Routing Sessions" section.!!!
 address-family vpnv4
neighbor 172.16.1.7 activate
 neighbor 172.16.1.7 send-community both
exit-address-family
!
ip classless
no ip http server
!
!
line con 0
exec-timeout 0 0
privilege level 15
transport input none
line aux 0
line vty 0 4
login
!
end

Site 2-PE2 Configuration—Cisco 6260 DSLAM

hostname dsl-7
!
boot system flash:ni2-dslp5-mz.ni2_mpls.20000720
slot 1 ATUC-1-4DMT
slot 2 ATUC-1-4DMT
slot 3 ATUC-1-4DMT
slot 4 ATUC-1-4DMT
slot 5 ATUC-1-4DMT
!
dsl-profile 4dmt2func
dmt training-mode standard
dmt overhead-framing mode1
dmt margin downstream 3 upstream 3
dmt bitrate minimum interleaved downstream 8032 upstream 864
dmt bitrate maximum interleaved downstream 8032 upstream 864
network-clock-select 1 system
ip subnet-zero
!
!!!Define and configure the VRF. Refer to the "Configuring a VPN Forwarding Routing Instance" section.!!!
ip vrf vpn1
rd 100:1
route-target export 100:1
route-target import 100:1
!
!!!The following command enables Cisco Express Forwarding. See the "Enabling Cisco Express Forwarding" section.!!!
ip cef
!
atm address 47.0091.8100.0000.0010.06ec.8b02.0010.06ec.8b02.00
atm address 47.0091.8100.0000.0030.b688.3801.0030.b688.3801.00
atm address 47.0091.8100.0000.0060.3e0f.0301.0060.3e0f.0301.00
atm address 47.0091.8100.0000.0060.3e0f.2b01.0060.3e0f.2b01.00
atm address 47.0091.8100.0000.0073.9a88.6301.0073.9a88.6301.00
atm router pnni
no aesa embedded-number left-justified
node 1 level 56 lowest
redistribute atm-static
!
!!!Create an uplink loopback interface. Refer to the "Creating a Loopback Interface to be Associated with the Uplink Interface" section.!!!
!
interface Loopback0
ip address 172.16.1.7 255.255.255.255
!
!!!Configure a loopback interface and associate it with a VRF. Refer to the "Creating a Loopback Interface and Associating It with a VRF" section.!!!
!
interface Loopback1
ip vrf forwarding vpn1
ip address 7.7.7.7 255.255.255.255
!
interface ATM0/0
no ip address
atm cac service-category abr deny
atm maxvp-number 0
atm maxvc-number 4096
atm maxvci-bits 12
!
interface Ethernet0/0
ip address 10.1.1.57 255.255.255.0
!
interface ATM0/1
no ip address
no atm ilmi-keepalive
atm cac service-category abr deny
 !!!Create Uplink ATM Subinterfaces. Refer to the   "Creating Uplink ATM Subinterfaces and VP Tunnels and Enabling MPLS" section.!!!
atm pvp 67
atm pvp 72
!
!!!Create VP tunnels and enable MPLS. Refer to the "Creating Uplink ATM Subinterfaces and VP Tunnels and Enabling MPLS" section.!!!
!
interface ATM0/1.67 point-to-point
ip unnumbered Loopback0
 tag-switching ip
!
!!!Create VP tunnels and enable MPLS. Refer to the "Creating Uplink ATM Subinterfaces and VP Tunnels and Enabling MPLS" section.!!!
!
interface ATM0/1.72 point-to-point
ip unnumbered Loopback0
 tag-switching ip
!
!!!Create a DSL interface and associate it with a VRF. Refer to the "Configuring the PE to CE Interface" section.!!!
!
interface ATM1/1
ip vrf forwarding vpn1
ip unnumbered Loopback1
dsl profile 4dmt2func
no atm ilmi-keepalive
atm cac service-category abr deny
pvc 1/33
!
!!!Configure OSPF as the MPLS core routing protocol. Configuring MPLS Core Routing Protocols
!
router ospf 7
router-id 172.16.1.7
network 172.16.0.0 0.0.255.255 area 0
!
!!!Configure RIP PE to CE routing sessions. Refer to the "Configuring RIP PE to CE Routing Sessions" section.!!!
!
router rip
 address-family ipv4 vrf vpn1
redistribute bgp 100 metric transparent
network 7.0.0.0
no auto-summary
exit-address-family
!
!!!Configure BGP. Refer to the "Configuring BGP Routing Sessions" section.!!!
!
router bgp 100
no synchronization
network 10.1.1.0 mask 255.255.255.0
neighbor 172.16.1.6 remote-as 100
neighbor 172.16.1.6 update-source Loopback0

address-family ipv4 vrf vpn1
redistribute connected
redistribute static
redistribute rip
no auto-summary
no synchronization
exit-address-family
 address-family ipv4 vrf vpn
no auto-summary
no synchronization
exit-address-family
!
 !!!Enable PE to PE routing sessions. Refer to the   "Configuring BGP Routing Sessions" section.!!!
 !
address-family vpnv4
neighbor 172.16.1.6 activate
neighbor 172.16.1.6 send-community both
exit-address-family
!
ip classless
no ip http server
!
line con 0
transport input none
line aux 0
line vty 0 4
login
!
end

Command Reference

This section documents commands relevant to the configuration of MPLS VPN mapping of RFC 1483 routed sessions. All other commands used with this feature are documented in Cisco IOS Release 12.1 command reference documentation.

address-family

clear ip route vrf

exit-address-family

import map

ip route vrf

ip vrf

ip vrf forwarding

neighbor activate

rd

route-target

show ip bgp vpnv4

show ip cef vrf

show ip protocols vrf

show ip route vrf

show ip vrf

show tag-switching forwarding vrf

You can search and filter command output for show and more commands. This is useful for sorting through large amounts of output, or if you want to exclude output that you do not need to see.

To use this functionality, enter a show or more command followed by the "pipe" character (|), one of the keywords begin, include, or exclude, and an expression that you want to search or filter on:

command | {begin | include | exclude} regular-expression

The following is an example of the show atm vc command in which you want the command output to begin with the first line where the expression "PeakRate" appears:

show atm vc | begin PeakRate

For more information on the search and filter functionality, refer to the Cisco IOS Release 12.0(1)T feature module titled CLI String Search.

Command Conventions

boldface font

Commands and keywords are in boldface.

italic font

Arguments for which you supply values are in italics. In contexts that do not allow italics, arguments are enclosed in angle brackets < >.

[ ]

Elements in square brackets are optional.

{ x | y | z }

Required alternative keywords are grouped in braces and separated by vertical bars.

[ x | y | z ]

Optional alternative keywords are grouped in brackets and separated by vertical bars.


address-family

To enter the address family submode for configuring routing protocols, such as BGP, RIP, and static routing, use the address-family global configuration command. To disable the address family submode for configuring routing protocols, use the no form of this command.

VPN-IPv4 unicast

address-family vpnv4 [unicast]

no address-family vpnv4 [unicast]

IPv4 unicast

address-family ipv4 [unicast]

no address-family ipv4 [unicast]

IPv4 unicast with CE router

address-family ipv4 [unicast] vrf vrf-name

no address-family ipv4 [unicast] vrf vrf-name

Syntax Description

ipv4

Configures sessions that carry standard IPv4 address prefixes.

vpnv4

Configures sessions that carry customer VPN-IPv4 prefixes, each of which is globally unique because of an 8-byte route distinguisher.

unicast

(Optional) Specifies unicast prefixes.

vrf vrf-name

Specifies the name of a VPN routing/forwarding instance (VRF) to associate with submode commands.


Defaults

Routing information for address family IPv4 is advertised by default when you configure a BGP session using the neighbor...remote-as command, unless you execute the no bgp default ipv4-activate command.

Command Modes

Address family configuration submode

Command History

Release
Modification

12.0(5)T

This command was introduced.


Usage Guidelines

If you use the address-family command, you enter address family configuration submode (prompt: (config-router-af)# ). Within this submode, you can configure address-family specific parameters for routing protocols, such as BGP, that can accommodate multiple Layer 3 address families.

To exit address family configuration submode and return to router configuration mode, type exit-address-family, or exit.

Examples

The address-family command in the following example places the router into address family configuration submode for the VPNv4 address family. Within the submode, you can configure advertisement of NLRI for the VPNv4 address family using the neighbor activate command and other related commands:

(config)# router bgp 100
(config-router)# address-family vpnv4
(config-router-af)#

The command in the following example places the router into address family configuration submode for the IPv4 address family. Use this form of the command, which specifies a VRF, only to configure routing exchanges between PE and CE devices. This address-family command causes subsequent commands entered in the submode to be executed in the context of VRF vrf2. Within the submode, you can use the neighbor activate command and other related commands to accomplish the following:

Configure advertisement of IPv4 NLRI between the PE and CE routers.

Configure translation of the IPv4 NLRI (that is, translate IPv4 into VPNv4 for NLRI received from the CE, and translate VPNv4 into IPv4 for NLRI to be sent from the PE to the CE).

Enter the routing parameters that apply to this VRF.

Enter the address family configuration submode as follows:

(config)# router bgp 100
(config-router)# address-family ipv4 unicast vrf vrf2
(config-router-af)#

Related Commands

Command
Description

exit-address-family

Exits address family submode.

neighbor activate

Exchanges an address with a neighboring router.


clear ip route vrf

To remove routes from the VRF routing table, use the clear ip route vrf EXEC command.

clear ip route vrf vrf-name {* | network [mask]}

Syntax Description

vrf-name

Name of the VPN routing/forwarding instance (VRF) for the static route.

*

Deletes all routes for a VRF.

network

Specifies destination routes to be removed.

mask

(Optional) Mask for the specified network destination, in dotted-decimal format.


Defaults

No default behavior or values.

Command Modes

EXEC

Command History

Release
Modification

12.0(5)T

This command was introduced.


Usage Guidelines

Use this command to clear routes from the routing table. Use the asterisk (*) to delete all routes from the forwarding table for a specified VRF, or enter the address and mask of a particular network to delete the route to that network.

Examples

The following example shows how to remove the route to the network 10.13.0.0 in the vpn1 routing table.

Router# clear ip route vrf vpn1 10.13.0.0

Related Commands

Command
Description

show ip route vrf

Displays the IP routing table associated with a VRF.


exit-address-family

To exit from the address family submode, use the exit-address-family address family submode command.

exit-address-family

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values.

Command Modes

Address family submode

Command History

Release
Modification

12.0(5)T

This command was introduced.


Usage Guidelines

This command can be abbreviated to exit.

Examples

The following example shows how to exit the address-family command mode.

(config-router-af)# exit-address-family

Related Commands

Command
Description

address-family

Enters the address family submode used to configure routing protocols.


import map

To configure an import route map for a VRF, use the import VRF submode command.

import map route-map

Syntax Description

route-map

Specifies the route map to be used as an import route map for the VRF.


Defaults

There is no default. A VRF has no import route map unless you configure one using the import map command.

Command Modes

VRF submode

Command History

Release
Modification

12.0(5)T

This command was introduced.


Usage Guidelines

Use an import route map when you require finer control over the routes imported into a VRF than provided by the import and export extended communities configured for the importing and exporting VRF.

The import-map command associates a route map with the specified VRF. You can filter routes that are eligible for import into a VRF, based on the route target extended community attributes of the route, through the use of a route map.

Examples

The following example shows how to configure an import route map for a VRF:

(config)# ip vrf vrf_blue
(config-vrf)# import map blue_import_map

Related Commands

Command
Description

ip vrf

Enters VRF configuration mode.

route-target

Configures import and export extended community attributes for the VRF.

show ip vrf

Displays information about a VRF or all VRFs.


ip route vrf

To establish static routes for a VRF, use the ip route vrf global configuration command. To disable static routes, use the no form of this command.

ip route vrf vrf-name prefix mask [next-hop-address] [interface {interface-number}]

[global] [distance] [permanent] [tag tag]

no ip route vrf vrf-name prefix mask [next-hop-address] [interface {interface-number}]

[global] [distance] [permanent] [tag tag]

Syntax Description

vrf-name

Name of the VPN routing/forwarding instance (VRF) for the static route.

prefix

IP route prefix for the destination, in dotted-decimal format.

mask

Prefix mask for the destination, in dotted-decimal format.

next-hop-address

(Optional) IP address of the next hop (the forwarding router that can be used to reach that network).

interface

(Optional) Type of network interface to use: ATM, Ethernet, loopback, POS (packet over SONET), or null.

interface-number

Number identifying the network interface to use.

global

Specifies that the given next hop address is in the non-VRF routing table.

distance

(Optional) An administrative distance for this route.

permanent

(Optional) Specifies that this route will not be removed, even if the interface shuts down.

tag tag

(Optional) Label value that can be used for controlling redistribution of routes through route maps.


Defaults

No default behavior or values.

Command Modes

Global configuration

Command History

Release
Modification

12.0(5)T

This command was introduced.


Usage Guidelines

Use a static route if the Cisco IOS software cannot dynamically build a route to the destination.

If you specify an administrative distance when you set up a route, you are flagging a static route that can be overridden by dynamic information. For example, IGRP-derived routes are configured with a default administrative distance of 100. To set a static route to be overridden by an IGRP dynamic route, specify an administrative distance greater than 100. Static routes each have a default administrative distance of 1.

Static routes that point to an interface are advertised through RIP, IGRP, and other dynamic routing protocols, regardless of whether or not the routes are redistributed into those routing protocols. That is, static routes configured by specifying an interface lose their static nature when installed into the routing table.

However, if you define a static route to an interface not defined in a network command, no dynamic routing protocols advertise the route unless you specify a redistribute static command for these protocols.

Examples

The following command shows how to reroute packets addressed to network 137.23.0.0 in VRF vpn3 to router 131.108.6.6:

(config)# ip route vrf vpn3 137.23.0.0 255.255.0.0 131.108.6.6

Related Commands

Command
Description

show ip route vrf

Displays the IP routing table associated with a VRF.


ip vrf

To configure a VRF routing table, use the ip vrf global configuration command. To remove a VRF routing table, use the no form of this command.

ip vrf vrf-name

no ip vrf vrf-name

Syntax Description

vrf-name

Name assigned to a VRF.


Defaults

No VRFs are defined. No import or export lists are associated with a VRF. No route maps are associated with a VRF.

Command Modes

Router configuration

Global configuration

Command History

Release
Modification

12.0(5)T

This command was introduced.


Usage Guidelines

The ip vrf vrf-name command creates a VRF routing table and a CEF (forwarding) table, both named vrf-name. The default route distinguisher value route-distinguisher is associated with these tables.

Examples

The following example shows how to import a route map to a VRF:

(Router-config)# ip vrf vpn1 (config-vrf)# rd 100:2
route-target both 100:2
route-target import 100:1

Related Commands

Command
Description

ip vrf forwarding

Associates a VRF with an interface or subinterface.


ip vrf forwarding

To associate a VRF with an interface or subinterface, use the ip vrf forwarding interface configuration command. To disassociate a VRF, use the no form of this command.

ip vrf forwarding vrf-name

no ip vrf forwarding vrf-name

Syntax Description

vrf-name

Name assigned to a VRF.


Defaults

The default for an interface is the global routing table.

Command Modes

Global configuration

Interface configuration

Command History

Release
Modification

12.0(5)T

This command was introduced.


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.

Examples

The following example shows how to link a VRF to ATM interface 1/1:

(config)# interface atm1/1
(config-if)# ip vrf forwarding vpn1

Related Commands

Command
Description

ip vrf

Defines a VRF.

ip route vrf

Establishes static routes for a VRF.


neighbor activate

To enable the exchange of information with a BGP neighboring router, use the neighbor activate router configuration command. To disable the exchange of an address with a neighboring router, use the no form of this command.

neighbor {ip-address | peer-group-name} activate

no neighbor {ip-address | peer-group-name} activate

Syntax Description

ip-address

IP address of the neighboring router.

peer-group-name

Name of BGP peer group.


Defaults

The exchange of addresses with neighbors is enabled by default for the VPN IPv4 address family. You can disable IPv4 address exchange using the general command no default bgp ipv4 activate, or you can disable it for a particular neighbor using the no form of this command.

For all other address families, address exchange is disabled by default. You can explicitly activate the default command using the appropriate address family submode.

Command Modes

Router configuration

Command History

Release
Modification

12.0(5)T

This command was introduced.


Usage Guidelines

Use this command to enable or disable the exchange of addresses with a neighboring router.

Examples

In the following example, a BGP router activates the exchange of a customer's IP address 10.15.0.15 to a neighboring router.

router bgp 100
 neighbor 10.15.0.15 remote-as 100
 neighbor 10.15.0.15 update-source loopback0
 address-family vpnv4 unicast
 neighbor 10.15.0.15 activate
 exit-address-family

Related Commands

Command
Description

address-family

Enters the address family submode.

exit-address-family

Exits the address family submode.


rd

To create routing and forwarding tables for a VRF, use the rd VRF submode command.

rd route-distinguisher

Syntax Description

route-distinguisher

Adds an 8-byte value to an IPv4 prefix to create a VPN IPv4 prefix.


Defaults

There is no default. An RD must be configured for a VRF to be functional.

Command Modes

VRF submode

Command History

Release
Modification

12.0(5)T

This command was introduced.


Usage Guidelines

A route distinguisher (RD) creates routing and forwarding tables and specifies the default route-distinguisher for a VPN. The RD is added to the beginning of the customer's IPv4 prefixes to making the prefixes globally unique VPN-IPv4 prefixes.

An RD is either ASN-relative, in which case it is composed of an autonomous system number and an arbitrary number, or it is IP-address-relative, in which case it is composed of an IP address and an arbitrary number.

You can enter an RD in either of these formats:

16-bit AS number: your 32-bit number
For example, 101:3

32-bit IP address: your 16-bit number
For example, 192.168.122.15:1

Examples

The following example shows how to configure a default RD for two VRFs. It illustrates the use of both AS-relative and IP address-relative RDs:

(config)# ip vrf vrf_blue
(config-vrf)# rd 100:3
(config-vrf)# ip vrf vrf_red
(config-vrf)# rd 173.13.0.12:200

Related Commands

Command
Description

ip vrf

Enters VRF configuration mode.

show ip vrf

Displays information about a VRF.


route-target

To create a route-target extended community for a VRF, use the route-target VRF submode command. To disable the configuration of a route-target community option, use the no form of this command.

route-target {import | export | both} route-target-ext-community

no route-target {import | export | both} route-target-ext-community

Syntax Description

import

Imports routing information from the target VPN extended community.

export

Exports routing information to the target VPN extended community.

both

Imports both import and export routing information to the target VPN extended community.

route-target-ext-community

Adds the route-target extended community attributes to the VRF's list of import, export, or both (import and export) route-target extended communities.


Defaults

There are no defaults. A VRF is not associated with any route-target extended community attributes until you specify so using the route-target command.

Command Modes

VRF submode

Command History

Release
Modification

12.0(5)T

This command was introduced.


Usage Guidelines

The route-target command creates lists of import and export route target extended communities for the specified VRF. Execute the command one time for each target community. Learned routes that carry a specific route target extended community are imported into all VRFs configured with that extended community as an import route target. Learned routes from a VRF site (for example, by BGP, RIP, or static route configuration) contain export route targets for extended communities configured for the VRF added as route attributes to control the VRFs into which the route is imported.

The route-target specifies a target VPN extended community. Like a route-distinguisher, an extended community is composed of either an autonomous system number and an arbitrary number, or an IP address and an arbitrary number. You can enter the numbers in either of these formats:

16-bit AS number: your 32-bit number
For example, 101:3

32-bit IP address: your 16-bit number
For example, 192.168.122.15:1

Examples

The following example shows how to configure route-target extended community attributes for a VRF. The result of the command sequence is that VRF vrf_blue has two export extended communities (1000:1 and 1000:2) and two import extended communities (1000:1 and 173.27.0.130:200).

(config)# ip vrf vrf_blue
(config-vrf)# route-target both 1000:1
(config-vrf)# route-target export 1000:2
(config-vrf)# route-target import 173.27.0.130:200

Related Commands

Command
Description

ip vrf

Enters VRF configuration mode.

import

Configures an import route map for the VRF.


show ip bgp vpnv4

To display VPN address information from the BGP table, use the show ip bgp vpnv4 EXEC command.

show ip bgp vpnv4 {all | rd route-distinguisher | vrf vrf-name}
[ip-prefix/length [longer-prefixes] [output-modifiers]]
[network-address [mask] [longer-prefixes] [output-modifiers]] [cidr-only] [community]
[community-list] [dampened-paths] [filter-list] [flap-statistics] [inconsistent-as]
[neighbors] [paths [line]] [peer-group] [quote-regexp] [regexp] [summary] [tags]

Syntax Description

all

Displays the complete VPNv4 database.

rd route-distinguisher

Displays NLRIs that have a matching route distinguisher.

vrf vrf-name

Displays NLRIs associated with the named VRF.

ip-prefix/length

(Optional) IP prefix address (in dotted decimal format) and length of mask (0 to 32).

longer-prefixes

(Optional) Displays the entry, if any, that exactly matches the specified prefix parameter, as well as all entries that match the prefix in a "longest-match" sense. That is, prefixes for which the specified prefix is an initial substring.

output-modifiers

(Optional) For a list of associated keywords and arguments, use context-sensitive help.

network-address

(Optional) IP address of a network in the BGP routing table.

mask

(Optional) Mask of the network address, in dotted decimal format.

cidr-only

(Optional) Displays only routes that have nonnatural net masks.

community

(Optional) Displays routes matching this community.

community-list

(Optional) Displays routes matching this community list.

dampened-paths

(Optional) Displays paths suppressed due to dampening (BGP route from peer is up and down).

filter-list

(Optional) Displays routes conforming to the filter list.

flap-statistics

(Optional) Displays flap statistics of routes.

inconsistent-as

(Optional) Displays only routes that have inconsistent autonomous systems of origin.

neighbors

(Optional) Displays details about TCP and BGP neighbor connections.

paths

(Optional) Displays path information.

line

(Optional) A regular expression to match the BGP AS paths.

peer-group

(Optional) Displays information about peer groups.

quote-regexp

(Optional) Displays routes matching the AS path "regular expression."

regexp

(Optional) Displays routes matching the AS path regular expression.

summary

(Optional) Displays BGP neighbor status.

tags

(Optional) Displays incoming and outgoing BGP labels for each NLRI.


Defaults

No default behavior or values.

Command Modes

EXEC

Command History

Release
Modification

12.0(5)T

This command was introduced.


Usage Guidelines

Use this command to display VPNv4 information from the BGP database. The command show ip bgp vpnv4 all displays all available VPNv4 information. The command show ip bgp vpnv4 summary displays BGP neighbor status.

Examples

The following example shows output for all available VPNv4 information in a BGP routing table:

DSLAM# show ip bgp vpnv4 all
BGP table version is 18, local router ID is 14.14.14.14
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal
Origin codes: i - IGP, e - EGP,? - incomplete

Network Next Hop Metric LocPrf Weight Path
Route Distinguisher: 100:1 (vrf1)
*> 11.0.0.0 50.0.0.1 0 0 101 i
*>i12.0.0.0 13.13.13.13 0 100 0 102 i
*> 50.0.0.0 50.0.0.1 0 0 101 i
*>i51.0.0.0 13.13.13.13 0 100 0 102 i

Table 2 describes the fields shown in this example.

Table 2 Show IP BGP VPNv4 Field Descriptions

Field
Description

Network

Displays the network address from the BGP table.

Next Hop

Displays the address of the BGP next hop.

Metric

Displays the BGP metric.

LocPrf

Displays the local preference.

Weight

Displays the BGP weight.

Path

Displays the BGP path per route.


The following example shows how to display a table of labels for NLRIs that have a route-distinguisher value of 100:1.

DSLAM# show ip bgp vpnv4 rd 100:1 tags
Network Next Hop In tag/Out tag
Route Distinguisher: 100:1 (vrf1)
2.0.0.0 10.20.0.60 34/notag
10.0.0.0 10.20.0.60 35/notag
12.0.0.0 10.20.0.60 26/notag
10.20.0.60 26/notag
13.0.0.0 10.15.0.15 notag/26

Table 3 describes the fields shown in this example.

Table 3 Show IP BGP VPNv4 rd Tags Field Descriptions 

Field
Description

Network

Displays the network address from the BGP table.

Next Hop

Specifies the BGP next hop address.

In Tag

Displays the label (if any) assigned by this router.

Out Tag

Displays the label assigned by the BGP next hop router.


The following example shows VPNv4 routing entries for the VRF called vrf1.

DSLAM# show ip bgp vpnv4 vrf vrf1
BGP table version is 18, local router ID is 14.14.14.14
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal
Origin codes: i - IGP, e - EGP,? - incomplete
Network Next Hop Metric LocPrf Weight Path
Route Distinguisher: 100:1 (vrf1)
*> 11.0.0.0 50.0.0.1 0 0 101 i
*>i12.0.0.0 13.13.13.13 0 100 0 102 i
*> 50.0.0.0 50.0.0.1 0 0 101 i
*>i51.0.0.0 13.13.13.13 0 100 0 102 i

Table 4 describes the fields shown in this example.

Table 4 Show IP BGP VPNv4 Field Descriptions

Field
Description

Network

Displays network address from the BGP table.

Next Hop

Displays address of the BGP next hop.

Metric

Displays the BGP metric.

LocPrf

Displays the local preference.

Weight

Displays the BGP weight.

Path

Displays the BGP path per route.


Related Commands

Command
Description

show ip vrf

Displays VRFs and associated interfaces.


show ip cef vrf

To display the CEF forwarding table associated with a VRF, use the show ip cef vrf EXEC command.

show ip cef vrf vrf-name [ip-prefix [mask [longer-prefixes]] [detail] [output-modifiers]]
[interface interface-number] [adjacency [interface interface-number] [detail] [discard]
[drop] [glean] [null] [punt] [output-modifiers]] [detail [output-modifiers]]
[non-recursive [detail] [output-modifiers]] [summary [output-modifiers]]
[traffic [prefix-length] [output-modifiers]] [unresolved [detail] [output-modifiers]]

Syntax Description

vrf-name

Name assigned to the VRF.

ip-prefix

(Optional) IP prefix of entries to show, in dotted decimal format (A.B.C.D).

mask

(Optional) Mask of the IP prefix, in dotted decimal format.

longer-prefixes

(Optional) Displays table entries for all of the more specific routes.

detail

(Optional) Displays detailed information for each CEF table entry.

output-modifiers

(Optional) For a list of associated keywords and arguments, use context-sensitive help.

interface

(Optional) Type of network interface to use: ATM, Ethernet, Loopback, POS (packet over SONET), or Null.

interface-number

Number identifying the network interface to use.

adjacency

(Optional) Displays all prefixes resolving through adjacency.

discard

Discards adjacency.

drop

Drops adjacency.

glean

Gleans adjacency.

null

Null adjacency.

punt

Punts adjacency.

non-recursive

(Optional) Displays only nonrecursive routes.

summary

(Optional) Displays a CEF table summary.

traffic

(Optional) Displays traffic statistics.

prefix-length

(Optional) Displays traffic statistics by prefix size.

unresolved

(Optional) Displays only unresolved routes.


Defaults

No default behavior or values.

Command Modes

EXEC

Command History

Release
Modification

12.0(5)T

This command was introduced.


Usage Guidelines

Used with only the vrf-name argument, the show ip cef vrf command shows a shortened display of the CEF table.

Used with the detail argument, the show ip cef vrf command shows detailed information for all CEF table entries.

Examples

This example shows the forwarding table associated with the VRF called vrf1.

DSLAM# show ip cef vrf vrf1
Prefix Next Hop Interface
0.0.0.0/32 receive
11.0.0.0/8 50.0.0.1 Ethernet1/3
12.0.0.0/8 52.0.0.2 POS6/0
50.0.0.0/8 attached Ethernet1/3
50.0.0.0/32 receive
50.0.0.1/32 50.0.0.1 Ethernet1/3
50.0.0.2/32 receive
50.255.255.255/32 receive
51.0.0.0/8 52.0.0.2 POS6/0
224.0.0.0/24 receive
255.255.255.255/32 receive

Table 5 describes the fields shown in this example.

Table 5 Show IP CEF vrf Field Descriptions

Field
Description

Prefix

Specifies the network prefix.

Next Hop

Specifies the BGP next hop address.

Interface

Specifies the VRF interface.


Related Commands

Command
Description

show ip route vrf

Displays the IP routing table associated with a VRF.

show ip vrf

Displays VRF interfaces.


show ip protocols vrf

To display the routing protocol information associated with a VRF, use the show ip protocols vrf EXEC command.

show ip protocols vrf vrf-name

Syntax Description

vrf-name

Name assigned to a VRF.


Defaults

No default behavior or values.

Command Modes

EXEC

Command History

Release
Modification

12.0(5)T

This command was introduced.


Usage Guidelines

Use this command to display routing information associated with a VRF.

Examples

The following example shows information about a VRF called vpn1.

DSLAM# show ip protocols vrf vpn2
Routing Protocol is "bgp 100"
Sending updates every 60 seconds, next due in 0 sec
Outgoing update filter list for all interfaces is
Incoming update filter list for all interfaces is
IGP synchronization is disabled
Automatic route summarization is disabled
Redistributing:connected, static
Routing for Networks:
Routing Information Sources:
Gateway Distance Last Update
13.13.13.13 200 02:20:54
18.18.18.18 200 03:26:15
Distance:external 20 internal 200 local 200

Table 6 describes the fields shown in this example.

Table 6 Show IP Protocols vrf Field Descriptions

Field
Description

Gateway

Displays the IP address of the router identifier for all routers in the network.

Distance

Displays the metric used to access the destination route.

Last update

Displays the last time the routing table was updated from the source.


Related Commands

Command
Description

show ip vrf

Displays VRF interfaces.


show ip route vrf

To display the IP routing table associated with a VRF (VPN routing/forwarding instance), use the show ip route vrf EXEC command.

show ip route vrf vrf-name [connected] [protocol [as-number] [tag] [output-modifiers]]
[list number [output-modifiers]] [profile] [static [output-modifiers]]
[summary [output-modifiers]] [supernets-only [output-modifiers]]

Syntax Description

vrf-name

Name assigned to the VRF.

connected

Displays all connected routes in a VRF.

protocol

To specify a routing protocol, use one of the following keywords: bgp, egp, eigrp, igrp, isis, ospf, or rip.

as-number

Autonomous system number.

tag

IOS routing area label.

output-modifiers

(Optional) For a list of associated keywords and arguments, use context-sensitive help.

list number

Specifies the IP access list to display.

profile

Displays the IP routing table profile.

static

Displays static routes.

summary

Displays a summary of routes.

supernets-only

Displays supernet entries only.


Defaults

No default behavior or values.

Command Modes

EXEC

Command History

Release
Modification

12.0(5)T

This command was introduced.


Usage Guidelines

This command displays specified information from the IP routing table of a VRF.

Examples

This example shows the IP routing table associated with the VRF called vrf1.

DSLAM# show ip route vrf vrf1
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate default
U - per-user static route, o - ODR
T - traffic engineered route
Gateway of last resort is not set
B 51.0.0.0/8 [200/0] via 13.13.13.13, 00:24:19
C 50.0.0.0/8 is directly connected, Ethernet1/3
B 11.0.0.0/8 [20/0] via 50.0.0.1, 02:10:22
B 12.0.0.0/8 [200/0] via 13.13.13.13, 00:24:20

This example shows BGP entries in the IP routing table associated with the VRF called vrf1.

DSLAM# show ip route vrf vrf1 bgp
B 51.0.0.0/8 [200/0] via 13.13.13.13, 03:44:14
B 11.0.0.0/8 [20/0] via 51.0.0.1, 03:44:12
B 12.0.0.0/8 [200/0] via 13.13.13.13, 03:43:14

Related Commands

Command
Description

show ip cef vrf

Displays the CEF forwarding table associated with a VRF.

show ip vrf

Displays VRFs and associated interfaces.


show ip vrf

To display the set of defined VRFs (VPN routing/forwarding instances) and associated interfaces, use the show ip vrf EXEC command.

show ip vrf [{brief | detail | interfaces}] [vrf-name] [output-modifiers]

Syntax Description

brief

(Optional) Displays concise information on the VRFs and associated interfaces.

detail

(Optional) Displays detailed information on the VRFs and associated interfaces.

interfaces

(Optional) Displays detailed information about all interfaces bound to a particular VRF, or any VRF.

vrf-name

Name assigned to a VRF.

output-modifiers

(Optional) For a list of associated keywords and arguments, use context-sensitive help.


Defaults

When no optional parameters are specified the command shows concise information about all configured VRFs.

Command Modes

EXEC

Command History

Release
Modification

12.0(5)T

This command was introduced.


Usage Guidelines

Use this command to display information about VRFs. Two levels of detail are available: use the brief keyword or no keyword to display concise information, or use the detail keyword to display all information. To display information about all interfaces bound to a particular VRF, or to any VRF, use the interfaces keyword.

Examples

This example shows brief information for the VRFs currently configured.

DSLAM# show ip vrf
Name Default RD Interfaces
vrf1 100:1 Ethernet1/3
vrf2 100:2 Ethernet0/3

Table 7 describes the fields shown in this example.

Table 7 Show vrf Field Descriptions

Field
Description

Name

Specifies the VRF name.

Default RD

Specifies the default route distinguisher.

Interfaces

Specifies the network interfaces.


This example shows detailed information for the VRF called vrf1.

DSLAM# show ip vrf detail vrf1
VRF vrf1; default RD 100:1
Interfaces:
Ethernet1/3
Connected addresses are in global routing table
Export VPN route-target communities
RT:100:1
Import VPN route-target communities
RT:100:1
No import route-map

Table 8 describes the fields shown in this example.

Table 8 Show IP vrf Detail Field Descriptions

Field
Description

Interfaces

Specifies the network interfaces.

Export

Specifies VPN route-target export communities.

Import

Specifies VPN route-target import communities.


This example shows the interfaces bound to a particular VRF.

DSLAM# show ip vrf interfaces
Interface IP-Address VRF Protocol
Ethernet2 130.22.0.33 blue_vrf up
Ethernet4 130.77.0.33 hub up
DSLAM#

Table 9 describes the fields shown in this example.

Table 9 Show IP vrf Interfaces Field Descriptions

Field
Description

Interface

Specifies the network interfaces for a VRF.

IP-Address

Specifies the IP address of a VRF interface.

VRF

Specifies the VRF name.

Protocol

Displays the state of the protocol (up/down) for each VRF interface.


Related Commands

Command
Description

ip vrf

Enters VRF configuration mode.

rd

Configures a default route distinguisher (RD) for a VRF.

route-target

Configures import and export extended community attributes for the VRF.

import

Configures an import route map for a VRF.

ip vrf forwarding

Associates a VRF with an interface or subinterface.


show tag-switching forwarding vrf

To display label forwarding information for advertised VRF routes, use the show tag-switching forwarding vrf EXEC command. To disable the display of label forwarding information, use the no form of this command.

show tag-switching forwarding vrf vrf-name [ip-prefix/length [mask]] [detail]
[output-modifiers]

no show tag-switching forwarding vrf vrf-name [ip-prefix/length [mask]] [detail]
[output-modifiers]

Syntax Description

vrf-name

Displays NLRIs associated with the named VRF.

ip-prefix/length

(Optional) IP prefix address (in dotted- decimal format) and length of mask (0 to 32).

mask

(Optional) Destination network mask, in dotted-decimal format.

detail

(Optional) Displays detailed information on the VRF routes.

output-modifiers

(Optional) For a list of associated keywords and arguments, use context-sensitive help.


Defaults

No default behavior or values.

Command Modes

EXEC

Command History

Release
Modification

12.0(5)T

This command was introduced.


Usage Guidelines

Use this command to display label forwarding entries associated with a particular VRF or IP prefix.

Examples

The following example shows label forwarding entries that correspond to the VRF called vpn1.

DSLAM# show tag-switching forwarding vrf vrf1 detail

Command History

Command
Description

show tag-switching forwarding

Displays label forwarding information.

show ip cef vrf

Displays VRFs and associated interfaces.


Debug Command

This section documents the debug ip bgp command. All other commands used with this feature are documented in the Cisco IOS Release 12.1 command references.

debug ip bgp

To display information related to processing BGPs, use the debug ip bgp EXEC command. To disable the display of BGP information, use the no form of this command.

debug ip bgp [A.B.C.D. | dampening | events | in | keepalives | out | updates | vpnv4]

no debug ip bgp [A.B.C.D. | dampening | events | in | keepalives | out | updates | vpnv4]

Syntax Description

A.B.C.D.

(Optional) Displays the BGP neighbor IP address.

dampening

(Optional) Displays BGP dampening.

events

(Optional) Displays BGP events.

in

(Optional) BGP inbound information.

keepalives

(Optional) Displays BGP keepalives.

out

(Optional) Displays BGP outbound information.

updates

(Optional) Displays BGP updates.

vpnv4

(Optional) Displays VPNv4 NLRI information.


Defaults

No default behavior or values.

Command Modes

EXEC

Command History

Release
Modification

12.0(5)T

This command was introduced.


Examples

The following example displays the output from this command:

DSLAM# debug ip bgp vpnv4
03:47:14:vpn:bgp_vpnv4_bnetinit:100:2:58.0.0.0/8
03:47:14:vpn:bnettable add:100:2:58.0.0.0 / 8
03:47:14:vpn:bestpath_hook route_tag_change for vpn2:58.0.0.0/255.0.0.0(ok)
03:47:14:vpn:bgp_vpnv4_bnetinit:100:2:57.0.0.0/8
03:47:14:vpn:bnettable add:100:2:57.0.0.0 / 8
03:47:14:vpn:bestpath_hook route_tag_change for vpn2:57.0.0.0/255.0.0.0(ok)
03:47:14:vpn:bgp_vpnv4_bnetinit:100:2:14.0.0.0/8
03:47:14:vpn:bnettable add:100:2:14.0.0.0 / 8
03:47:14:vpn:bestpath_hook route_tag_chacle ip bgp *nge for vpn2:14.0.0.0/255.0.0.0(ok)

hometocprevnextglossaryfeedbacksearchhelp

Posted: Thu Jun 22 17:52:11 PDT 2006
All contents are Copyright © 1992--2006 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.