The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes how to configure VPLS over MPLS-TP and includes the following sections:
For more information, see the MPLS Transport Profile.
The sections below provide an overview of VPLS over MPLS-TP:
The Multiprotocol Label Switching (MPLS) Transport Profile (TP) enables you to create tunnels that provide the transport network service layer over which IP and MPLS traffic traverse. MPLS-TP tunnels enable a transition from Synchronous Optical Networking (SONET) and Synchronous Digital Hierarchy (SDH) time-division multiplexing (TDM) technologies to packet switching to support services with high bandwidth requirements, such as video.
uses the provider core to join multiple attachment circuits together to simulate a virtual bridge that connects the multiple attachment circuits together. From a customer point of view, there is no topology for VPLS. All of the CE devices appear to connect to a logical bridge emulated by the provider core. See figure below.
VPLS over MPLS-TP allows you to deploy a multipoint-to-multipoint layer 2 operating environment over an MPLS-TP network for services such as Ethernet connectivity and multicast video.
For detailed information about the commands, see:
Cisco IOS XE 3.5 MPLS Command Reference: http://www.cisco.com/en/US/docs/ios/cether/command/reference/ce_book.html
Master Command Index for Cisco IOS XE Release 3.5: http://www.cisco.com/en/US/docs/ios/mcl/allreleasemcl/all_book.html
The sections below describe how to configure VPLS over MPLS-TP:
VPLS over MPLS-TP is only supported on Gigabit Ethernet and Ten Gigabit Ethernet interfaces.
You must specify a static range of MPLS labels using the mpls label range command with the static keyword.
1. enable
2. configure terminal
3. mpls label range minimum-value maximum-value{ staticminimum-static-value maximum-static-value}
1. enable
2. configure terminal
3. mpls tp
4. router-id node-id
5. global-id num
When you create the pseudowire class, you specify the parameters of the pseudowire, such as the use of the control word, and preferred path.
1. enable
2. configure terminal
3. pseudowire-class class-name
4. encapsulation mpls
5. control-word
6. protocol {l2tpv2 | l2tpv3 | none}[l2tp-class-name]
7. preferred-path {interface tunnel tunnel-number | peer {ip-address | host-name}} [disable-fallback]
8. end
1. enable
2. configure terminal
3. bfd-template single-hop template-name
4. interval microseconds {both microseconds | min-tx microseconds min-rx microseconds} [multiplier multiplier-value]
5. interval {both milliseconds | min-tx milliseconds min-rx milliseconds} [multiplier multiplier-value]
6. end
On the endpoint routers, create an MPLS TP tunnel and configure its parameters. See the interface tunnel-tp command for information on the parameters.
1. enable
2. configure terminal
3. interface tunnel-tp number
4. description tunnel-description
5. tp tunnel-name name
6. tp source node-id [global-id num]
7. tp destination node-id [[ tunnel-tpnum] global-id num]
8. bfd bfd-template
9. working-lsp
10. in-label num
11. out-label num out-link num
12. exit
13. protect-lsp
14. in-label num
15. out-label num out-link num
16. exit
MPLS-TP link numbers may be assigned to physical interfaces only. Bundled interfaces and virtual interfaces are not supported for MPLS-TP link numbers.
The sections below describe how to configure physical interfaces for a VPLS over MPLS-TP link.
1. enable
2. configure terminal
3. interface type/num
4. no ip address
5. negotiation auto
6. mpls tp link link-num {ipv4 ip-address | tx-mac mac-address}
7. exit
8. exit
9. show mpls tp link-numbers
1. enable
2. configure terminal
3. interface type/num
4. no ip address
5. negotiation auto
6. service instance id service-type
7. encapsulation dot1q vlan-id second-dot1q {any | vlan-id | vlan-id-vlan-id[,vlan-id-vlan-id]}
8. bridge-domain vlan-id [access | dot1q [tag] | dot1q-tunnel] [broadcast] [ignore-bpdu-pid] [pvst-tlvCE-vlan] [increment] [lan-fcs] [split-horizon]
9. exit
The virtual switch instance (VFI) specifies the VPN ID of a VPLS domain, the addresses of other PE routers in this domain, and the type of tunnel signaling and encapsulation mechanism for each peer. (This is where you create the VSI and associated VCs.) Configure a VFI as follows:
Note | Only MPLS encapsulation is supported. |
1. l2 vfi name manual
2. vpn id vpn-id
3. bridge-domain vlan-id [access | dot1q [tag] | dot1q-tunnel] [broadcast] [ignore-bpdu-pid] [pvst-tlv CE-vlan] [increment] [lan-fcs] [split-horizon]
4. neighbor remote router id [vc-id-value] {encapsulation mpls}[no-split-horizon]
5. shutdown
This task explains how to configure a basic loopback interface.
The IP address of a loopback interface must be unique across all routers on the network. It must not be used by another interface on the router, and it must not be used by an interface on any other router on the network.
1.
configure terminal
2.
interface loopback interface-path-id
3.
ipv4 address ip-address
4.
end
5.
show interfaces
type interface-path-id
Command or Action | Purpose | |||
---|---|---|---|---|
Step 1 |
configure terminal
Example: Router# configure terminal |
Enters global configuration mode. | ||
Step 2 |
interface loopback interface-path-id
Example: Router#(config)# interface Loopback 3 |
Enters interface configuration mode and names the new loopback interface. | ||
Step 3 |
ipv4 address ip-address
Example: Router(config-if)# ipv4 address 172.18.189.38 |
Assigns an IP address and subnet mask to the virtual loopback interface using the ipv4 address configuration command. | ||
Step 4 |
end
Example: Router(config-if)# end |
Uncommitted changes found, commit them before exiting(yes/no/cancel)? [cancel]:
| ||
Step 5 |
show interfaces
type interface-path-id
Example: router# show interfaces Loopback 3 |
(Optional) Displays the configuration of the loopback interface. |
You can use the following commands to verify your configuration:
show mpls l2transport vc—Displays information about Any Transport over MPLS (AToM) virtual circuits (VCs) and static pseudowires that have been enabled to route Layer 2 packets on the router.
show mpls tp—Displays information about Multiprotocol Label Switching (MPLS) transport profile (TP) tunnels.
show bfd summary—Displays summary information for Bidirectional Forwarding Protocol (BFD).
show xconnect—Displays information about xconnect attachment circuits and pseudowires.
You can use the following commands to debug your configuration:
! mpls label range 1001 4000 static 16 1000 mpls tp router-id 10.10.10.10 ! bfd-template single-hop testbfd interval microseconds min-tx 50000 min-rx 50000 multiplier 3 ! ! Output link interface GigabitEthernet0/0/0 no ip address negotiation auto mpls tp link 2 tx-mac 88f0.7768.2300 ! ! Output link interface GigabitEthernet0/2/0 no ip address negotiation auto mpls tp link 1 tx-mac 88f0.7768.2310 ! ! interface Tunnel-tp1 ip unnumbered Loopback0 no keepalive tp source 10.10.10.10 global-id 0 tp destination 192.168.1.1 global-id 0 bfd testbfd working-lsp out-label 100 out-link 1 in-label 200 lsp-number 0 protect-lsp out-label 300 out-link 2 in-label 400 lsp-number 102 ! ! pseudowire-class myclass encapsulation mpls preferred-path interface Tunnel-tp1 ! ! !VFI definition l2 vfi VPLS manual vpn id 1000 bridge-domain 1000 neighbor 192.168.1.1 pw-class myclass ! ! interface Loopback0 ip address 10.10.10.10 255.255.255.255 ! ! Access interface interface GigabitEthernet0/1/0 no ip address negotiation auto service instance 1 ethernet encapsulation dot1q 2 bridge-domain 1000 !
! interface loopback 0 ip address 9.9.9.9 255.255.255.255 ! mpls label range 1001 4000 static 16 1000 mpls t router-id 9.9.9.9 ! mpls tp lsp source 10.10.10.10 tunnel-tp 1 lsp working destination 192.168.1.1 tunnel-tp 1 forward-lsp in-label 100 out-label 300 out-link 1 reverse-lsp in-label 400 out-label 200 out-link 2 ! out-link 1 connected to 192.168.1.1 out-link 2 connected to 10.10.10.10
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Feature Name |
Release |
Feature Information |
---|---|---|
VPLS Configuration over MPLS-TP |
IOS XE 3.5 |
This feature was introduced on the Cisco RSP1 Module in this release. |
VPLS Configuration over MPLS-TP |
IOS XE 3.13 |
This feature was introduced on the Cisco RSP2 Module in this release. |
VPLS Configuration over MPLS-TP |
IOS XE 3.16 |
This feature was introduced on the Cisco RSP3 Module in this release. |
Feature Name |
Release |
Feature Information |
VPLS Configuration over MPLS-TP |
IOS XE 3.13 |
This feature was introduced on the Cisco ASR 920 Series Aggregation Services Router. |