Mpls 8360
Mpls 8360
09 MPLS Guide
8360 Switch Series
|2
Contents
Contents
Contents 3
About this document 5
Applicable products 5
Latest version available online 5
Command syntax notation conventions 5
About the examples 6
Identifying switch ports and interfaces 6
Overview 8
MPLS L3 VPN 8
Use cases 22
Use case 1: MPLS L3 VPN with dual homed VSX CE 22
Use case 2: MPLS L3 VPN with hub and spoke VRFs 96
Contents | 4
Chapter 1
About this document
Applicable products
This document applies to the following products:
n Aruba 8360 Switch Series (JL700A, JL701A, JL702A, JL703A, JL704C, JL705C, JL706A, JL707A, JL708A,
JL709A, JL710A, JL711A, JL717C, JL718C)
example-text Identifies commands and their options and operands, code examples,
filenames, pathnames, and output displayed in a command window. Items that
appear like the example text in the previous column are to be entered exactly
as shown and are required unless enclosed in brackets ([ ]).
| Vertical bar. A logical OR that separates multiple items from which you can
choose only one.
Any spaces that are on either side of the vertical bar are included for
readability and are not a required part of the command syntax.
… or Ellipsis:
... n In code and screen examples, a vertical or horizontal ellipsis indicates an
omission of information.
n In syntax using brackets and braces, an ellipsis indicates items that can be
repeated. When an item followed by ellipses is enclosed in brackets, zero
or more items can be specified.
If using breakout cables, the port designation changes to x:y, where x is the physical port and y is the lane when
split to 4 x 10G or 4 x 25G. For example, the logical interface 1/1/4:2 in software is associated with lane 2 on
physical port 4 in slot 1 on member 1.
Overview
Multiprotocol Label Switching (MPLS) is a routing technique in telecommunications networks that directs
data from one node to the next based on short path labels rather than long network addresses. The labels
identify virtual links (paths) between distant nodes rather than endpoints. MPLS can encapsulate packets of
various network protocols, hence the "multiprotocol" reference on its name.
Any features not explicitly mentioned in this document are not supported as of the 10.09 release.
1. At the ingress edge LSR, label imposition or label push is used to classify and label packets.
2. At the transit core LSR, label switching or label swapping is used to forward traffic based on labels
instead of IP.
3. At the egress edge LSR, label disposition or label pop is used to remove labels and forward IP packets.
A unidirectional label switched path (LSP) is a chain of labels that are swapped at each hop to get from one
LSR to another. Label Distribution Protocol (LDP) sessions are established between LSRs to distribute labels.
Penultimate Hop Popping (PHP) optimizes MPLS performance by reducing 1 less lookup at the egress edge
LSR. With PHP, the egress edge LSR will just need to perform IP lookup instead of removing label and
performing IP lookup. The figure below depicts the main MPLS concepts:
MPLS L3 VPN
MPLS L3 VPNs are deployed by service providers to provide L3 network connectivity and multi-tenant traffic
isolation using an MPLS network.
In the figure below, the MPLS L3 VPN uses BGP Autonomous System (AS) 65001, CEs in Virtual Routing and
Forwarding (VRF1) utilize AS 65101/65102, CEs in VRF2 utilize AS 65201/65202. VRF1 and VRF2 may utilize
overlapping IP subnets if desired.
Overview | 9
Chapter 3
Protocol and feature details
Label-based forwarding
Once the labels are allocated in the downstream direction, label based forwarding in the upstream direction
is used next.
1. Data destined for 10.1.1.0/24 arrives at LSR1, LSR1 will refer to the MPLS label table and push 1001
into the packet towards LSR2.
The figure shows label-based forwarding, from the left to right direction:
1. Data destined for 10.1.1.0/24 arrives at PE1, PE1 will refer to the LDP, MPLS BGP VPNv4 tables and
push both 43 (outer) and 2001 (inner) labels into the packet towards P2.
2. Because of PHP from PE3 to P2, P2 will receive the packet, see inbound label 43, remove outer
LDP label and send it towards PE3.
3. PE3 will receive the packet with VPNv4 label, see inbound label 2001, pop it and send the packet
using it's IP routing table to the destination.
The figure below shows MPLS L3 VPN forwarding from the left to right direction:
n Dual standalone Ps
n Dual standalone RRs
n Dual standalone PEs for a site
n Dual CEs (could be VSX or 2 standalone switches)
n Redundant Equal Cost Multi Pathing (ECMP) links
1. If CE1 sends traffic to PE1 with CS6 DSCP marking PE1 will automatically copy the CS6 DSCP marking
to MPLS EXP 6 for both inner and outer labels
2. P2 will remove the outer label and forward traffic to interface towards PE3 with EXP 6 marking
3. PE3 will receive, pop the VPNv4 label and forward traffic with DSCP CS6
1. Traffic from ingress PE to egress PE will be load balanced across the links via the 2 P routers on a per
flow basis
2. On ingress PE, some flows will use outbound label (2001) via top P router, while other flows will use
outbound label (2002) via bottom P router
Same CE AS
Default behaviors
n Defualt QoS mode: Uniform
n Default TTL propagation mode: Uniform
n Default egress label: Explicit null
n Per-VPN/VRF label
Supported features
n MPLS L3 VPN
o IPv4 unicast
n Static LSP
n OSPF between P/RR and PE/P
n LDP between P/RR and PE/P
n MP-BGP VPNv4 RR on PE
n MP-BGP VPNv4 RR client on PE
n QoS uniform mode only
n Label bindings are supported with /32 address
o o E.g. if the network between P and PE is X.0.0.0/24 with an interface address of P as X.0.0.1/24 and
address of PE as X.0.0.2/24, the LDP binding on PE for the X.0.0.0/24 network will be shown as
X.0.0.1/32
n VRFs (intranet and extranet VRF with route leaking)
n Multi-VRF (VRF-Lite) CE
n PE-CE connectivity:
o EBGP
o Static route
o Default route
o Connected route (PE acting as an L3 first hop)
Scale
Profile: Aggregation-Leaf
Profile: Core-Spine
(Default)
Max VPNv4 neighbors/Max routes 256 neighbors/32,000 routes 256 neighbors/600,000 routes
Best practices
Recommended best practices for MPLS configuration are as follows:
n Use single area OSPF within the MPLS network to advertise and learn LSR loopbacks
n Use a single AS for the MPLS network
n Utilize EBGP between CE and PE for dynamic routing, use unique CE AS# if possible
n Use redundant VPNv4 RRs to avoid full mesh IBGP peers
n Use peer groups to simplify configs on both P/RR and PE
n The l3vpn-only command should only be configured under the VRF context
n Implicit null is not supported, explicit null has to be configured on 3rd party egress PE towards AOS-CX P
n If egress PE and P are AOS-CX switches, changing it to explicit null is not required as explicit null is
automatically sent
The descriptions, syntax, and examples for the commands listed above can be found in the IP Routing Guide.
Configuring VPN
Step Command Comments
The descriptions, syntax, and examples for the commands listed above can be found in the IP Routing Guide.
Use cases
The following use cases provide examples of networks using MPLS VPNs.
n An MPLS L3 VPN network with redundant PEs, Ps and VRFs across the MPLS network
n Redundant VSX CEs at Site1 and standalone CE at Site2 with locally significant VRFs
n BGP community is used inbound/outbound on PE1 and PE2 to prevent loops from Site1
n Sample configurations
n Relevant verification commands
CE1 configuration
Use cases | 23
vrf attach vrf_1
description Towards LAN
ip mtu 9000
vsx active-forwarding
ip address 20.0.1.2/24
interface vlan 2002
vrf attach vrf_2
description Towards LAN
ip mtu 9000
vsx active-forwarding
ip address 20.0.1.2/24
interface vlan 2011
vrf attach vrf_1
description Towards PE1
ip mtu 9000
ip address 20.1.1.1/24
interface vlan 2012
vrf attach vrf_2
description Towards PE1
ip mtu 9000
ip address 20.1.1.1/24
interface vlan 2021
vrf attach vrf_1
description Towards PE2
ip mtu 9000
ip address 20.2.1.1/24
interface vlan 2022
vrf attach vrf_2
description Towards PE2
ip mtu 9000
ip address 20.2.1.1/24
vsx
inter-switch-link lag 256
role primary
keepalive peer 99.0.0.2 source 99.0.0.1
!
!
!
!
!
router bgp 100
!
vrf vrf_1
neighbor 20.0.1.1 remote-as 100
neighbor 20.0.1.1 description Towards LAN
neighbor 20.0.1.3 remote-as 100
neighbor 20.0.1.3 description Towards CE2
neighbor 20.1.1.2 remote-as 6488163
neighbor 20.1.1.2 description Towards PE1
neighbor 20.2.1.2 remote-as 6488163
neighbor 20.2.1.2 description Towards PE2
address-family ipv4 unicast
neighbor 20.0.1.1 activate
neighbor 20.0.1.1 next-hop-self
neighbor 20.0.1.1 send-community both
neighbor 20.0.1.1 soft-reconfiguration inbound
neighbor 20.0.1.3 activate
neighbor 20.0.1.3 allowas-in 1
neighbor 20.0.1.3 next-hop-self
neighbor 20.0.1.3 send-community both
neighbor 20.0.1.3 soft-reconfiguration inbound
neighbor 20.1.1.2 activate
CE1 verification
Use cases | 25
VRF : vrf_1
BGP Summary
-----------
Local AS : 100 BGP Router Identifier : 20.2.1.1
Peers : 4 Log Neighbor Changes : No
Cfg. Hold Time : 180 Cfg. Keep Alive : 60
Confederation Id : 0
VRF : vrf_2
BGP Summary
-----------
Local AS : 100 BGP Router Identifier : 20.2.1.1
Peers : 4 Log Neighbor Changes : No
Cfg. Hold Time : 180 Cfg. Keep Alive : 60
Confederation Id : 0
VRF : default
Local Router-ID 99.0.0.1
VRF : vrf_1
Local Router-ID 20.2.1.1
VRF : vrf_2
Local Router-ID 20.2.1.1
VRF: default
VRF: vrf_1
Use cases | 27
Prefix Nexthop Interface VRF(egress) Origin/
Distance/ Age
Type Metric
------------------------------------------------------------------------------------
----------
20.0.1.0/24 - vlan2001 - C [0/0]
-
20.0.1.2/32 - vlan2001 - L [0/0]
-
20.1.1.0/24 - vlan2011 - C [0/0]
-
20.1.1.1/32 - vlan2011 - L [0/0]
-
20.2.1.0/24 - vlan2021 - C [0/0]
-
20.2.1.1/32 - vlan2021 - L [0/0]
-
101.0.0.0/24 20.0.1.1 vlan2001 - B/I
[200/0] 01h:11m:54s
201.0.0.0/24 20.1.1.2 vlan2011 - B/E
[20/0] 01h:10m:33s
20.2.1.2 vlan2021 -
[20/0] 01h:10m:33s
VRF: vrf_2
CE2 configuration
Use cases | 29
vlan trunk allowed 2031-2032
interface 1/1/48
no shutdown
mtu 9000
description Towards PE2
no routing
vlan trunk native 1
vlan trunk allowed 2041-2042
interface vlan 2001
vrf attach vrf_1
description Towards LAN
ip mtu 9000
vsx active-forwarding
ip address 20.0.1.3/24
interface vlan 2002
vrf attach vrf_2
description Towards LAN
ip mtu 9000
vsx active-forwarding
ip address 20.0.1.3/24
interface vlan 2031
vrf attach vrf_1
description Towards PE1
ip mtu 9000
ip address 20.3.1.1/24
interface vlan 2032
vrf attach vrf_2
description Towards PE1
ip mtu 9000
ip address 20.3.1.1/24
interface vlan 2041
vrf attach vrf_1
description Towards PE2
ip mtu 9000
ip address 20.4.1.1/24
interface vlan 2042
vrf attach vrf_2
description Towards PE2
ip mtu 9000
ip address 20.4.1.1/24
vsx
inter-switch-link lag 256
role secondary
keepalive peer 99.0.0.1 source 99.0.0.2
!
!
!
!
!
router bgp 100
!
vrf vrf_1
neighbor 20.0.1.1 remote-as 100
neighbor 20.0.1.1 description Towards LAN
neighbor 20.0.1.2 remote-as 100
neighbor 20.0.1.2 description Towards CE1
neighbor 20.3.1.2 remote-as 6488163
neighbor 20.3.1.2 description Towards PE1
neighbor 20.4.1.2 remote-as 6488163
neighbor 20.4.1.2 description Towards PE2
address-family ipv4 unicast
neighbor 20.0.1.1 activate
CE2 verification
Use cases | 31
Address-family : IPv4 Unicast
-----------------------------
VRF : vrf_1
BGP Summary
-----------
Local AS : 100 BGP Router Identifier : 20.4.1.1
Peers : 4 Log Neighbor Changes : No
Cfg. Hold Time : 180 Cfg. Keep Alive : 60
Confederation Id : 0
VRF : vrf_2
BGP Summary
-----------
Local AS : 100 BGP Router Identifier : 20.4.1.1
Peers : 4 Log Neighbor Changes : No
Cfg. Hold Time : 180 Cfg. Keep Alive : 60
Confederation Id : 0
VRF : default
Local Router-ID 99.0.0.2
VRF : vrf_1
Local Router-ID 20.4.1.1
VRF : vrf_2
Local Router-ID 20.4.1.1
VRF: default
Use cases | 33
------------------------------------------------------------------------------------
----------
99.0.0.0/24 - 1/1/46 - C [0/0]
-
99.0.0.2/32 - 1/1/46 - L [0/0]
-
VRF: vrf_1
VRF: vrf_2
CE3 configuration
Use cases | 35
!
router bgp 100
!
vrf vrf_1
neighbor 20.5.1.1 remote-as 6488163
neighbor 20.5.1.1 description Towards PE3
neighbor 20.6.1.2 remote-as 100
neighbor 20.6.1.2 description Towards LAN
address-family ipv4 unicast
neighbor 20.5.1.1 activate
neighbor 20.5.1.1 allowas-in 1
neighbor 20.5.1.1 send-community both
neighbor 20.5.1.1 soft-reconfiguration inbound
neighbor 20.6.1.2 activate
neighbor 20.6.1.2 next-hop-self
neighbor 20.6.1.2 send-community both
neighbor 20.6.1.2 soft-reconfiguration inbound
exit-address-family
!
vrf vrf_2
neighbor 20.5.1.1 remote-as 6488163
neighbor 20.5.1.1 description Towards PE3
neighbor 20.6.1.2 remote-as 100
neighbor 20.6.1.2 description Towards LAN
address-family ipv4 unicast
neighbor 20.5.1.1 activate
neighbor 20.5.1.1 allowas-in 1
neighbor 20.5.1.1 send-community both
neighbor 20.5.1.1 soft-reconfiguration inbound
neighbor 20.6.1.2 activate
neighbor 20.6.1.2 next-hop-self
neighbor 20.6.1.2 send-community both
neighbor 20.6.1.2 soft-reconfiguration inbound
exit-address-family
!
https-server vrf mgmt
CE3 verification
VRF : vrf_1
BGP Summary
-----------
VRF : vrf_2
BGP Summary
-----------
Local AS : 100 BGP Router Identifier : 20.6.1.1
Peers : 2 Log Neighbor Changes : No
Cfg. Hold Time : 180 Cfg. Keep Alive : 60
Confederation Id : 0
VRF : default
Router-ID not configured
VRF : vrf_1
Local Router-ID 20.6.1.1
Use cases | 37
-----------------------------
Network Nexthop Metric LocPrf Weight Path
*>e 101.0.0.0/24 20.5.1.1 0 100 0 6488163 100 i
*>i 201.0.0.0/24 20.6.1.2 0 0 0 i
Total number of entries 2
VRF : vrf_2
Local Router-ID 20.6.1.1
VRF: vrf_1
VRF: vrf_2
P1 configuration
Use cases | 39
interface 1/1/15
no shutdown
mtu 9198
description Towards PE2
ip mtu 9198
ip address 30.0.1.2/24
ip ospf 1 area 0.0.0.0
mpls enable
mpls ldp enable
interface 1/1/16
no shutdown
mtu 9198
description Towards PE3
lag 99
interface 1/1/17
no shutdown
mtu 9198
description Towards PE3
lag 99
interface 1/1/27
description Towards PE3
interface 1/1/28
description Towards PE3
interface loopback 0
ip address 4.4.4.4/32
ip ospf 1 area 0.0.0.0
!
!
!
!
!
router ospf 1
area 0.0.0.0
router bgp 6488163
neighbor 1.1.1.1 remote-as 6488163
neighbor 1.1.1.1 description Towards PE1
neighbor 1.1.1.1 update-source loopback 0
neighbor 2.2.2.2 remote-as 6488163
neighbor 2.2.2.2 description Towards PE2
neighbor 2.2.2.2 update-source loopback 0
neighbor 3.3.3.3 remote-as 6488163
neighbor 3.3.3.3 description Towards PE2
neighbor 3.3.3.3 update-source loopback 0
neighbor 5.5.5.5 remote-as 6488163
neighbor 5.5.5.5 description Towards RR2
neighbor 5.5.5.5 update-source loopback 0
address-family vpnv4 unicast
neighbor 1.1.1.1 activate
neighbor 1.1.1.1 route-reflector-client
neighbor 1.1.1.1 send-community both
neighbor 2.2.2.2 activate
neighbor 2.2.2.2 route-reflector-client
neighbor 2.2.2.2 send-community both
neighbor 3.3.3.3 activate
neighbor 3.3.3.3 route-reflector-client
neighbor 3.3.3.3 send-community both
neighbor 5.5.5.5 activate
neighbor 5.5.5.5 send-community both
exit-address-family
!
https-server vrf mgmt
mpls
P1 verification
Use cases | 41
local binding: label: exp-null
No remote binding
30.0.0.1/32
No local binding
remote binding: lsr:1.1.1.1:0 label: exp-null
30.0.1.1/32
No local binding
remote binding: lsr:2.2.2.2:0 label: exp-null
30.0.5.2/32
No local binding
remote binding: lsr:3.3.3.3:0 label: exp-null
30.0.2.2/32
No local binding
remote binding: lsr:3.3.3.3:0 label: exp-null
2.2.2.2/32
local binding: label: 18
remote binding: lsr:1.1.1.1:0 label:18
remote binding: lsr:3.3.3.3:0 label:17
remote binding: lsr:2.2.2.2:0 label: exp-null
5.5.5.5/32
local binding: label: 17
remote binding: lsr:1.1.1.1:0 label:17
remote binding: lsr:3.3.3.3:0 label:19
remote binding: lsr:2.2.2.2:0 label:18
30.0.0.2/32
local binding: label: exp-null
No remote binding
3.3.3.3/32
local binding: label: 19
remote binding: lsr:1.1.1.1:0 label:19
remote binding: lsr:3.3.3.3:0 label: exp-null
remote binding: lsr:2.2.2.2:0 label:19
4.4.4.4/32
local binding: label: exp-null
remote binding: lsr:1.1.1.1:0 label:16
remote binding: lsr:3.3.3.3:0 label:18
remote binding: lsr:2.2.2.2:0 label:17
30.0.3.1/32
No local binding
remote binding: lsr:1.1.1.1:0 label: exp-null
1.1.1.1/32
local binding: label: 16
remote binding: lsr:1.1.1.1:0 label: exp-null
remote binding: lsr:3.3.3.3:0 label:16
remote binding: lsr:2.2.2.2:0 label:16
MPLS Bindings
Entry Bindings : 4
Exit Bindings : 2
Transit Bindings : 4
PHP Mode : Explicit-Null
QoS Mode : Uniform
TTL Propagation : Uniform
Entry Bindings:
Exit Bindings:
Transit Bindings:
VRF : default
Use cases | 43
Last Err Rcvd : No Error
Last SubErr Rcvd : No Error
Routemap In :
Routemap Out :
ORF type : Prefix-list
ORF capability :
Routemap In :
Routemap Out :
ORF type : Prefix-list
ORF capability :
Use cases | 45
Last Err Rcvd : No Error
Last SubErr Rcvd : No Error
Routemap In :
Routemap Out :
ORF type : Prefix-list
ORF capability :
Routemap In :
Routemap Out :
ORF type : Prefix-list
ORF capability :
VRF : default
Local Router-ID 4.4.4.4
Use cases | 47
* i 102.0.0.0/24 2.2.2.2 0 100 0 100 i
* i 102.0.0.0/24 1.1.1.1 0 100 0 100 i
VRF : default
Local Router-ID 4.4.4.4
VRF: default
Use cases | 49
-
30.0.2.0/24 - lag99 - C [0/0]
-
30.0.2.1/32 - lag99 - L [0/0]
-
30.0.3.0/24 30.0.0.1 1/1/14 - O
[110/200] 01h:11m:52s
30.0.2.2 lag99 -
[110/200] 01h:11m:52s
30.0.4.0/24 30.0.1.1 1/1/15 - O
[110/200] 01h:11m:52s
30.0.2.2 lag99 -
[110/200] 01h:11m:52s
30.0.5.0/24 30.0.2.2 lag99 - O
[110/100] 01h:11m:57s
P2 configuration
Use cases | 51
router-id loopback0
P2 verification
MPLS Bindings
Entry Bindings : 4
Exit Bindings : 2
Transit Bindings : 4
PHP Mode : Explicit-Null
QoS Mode : Uniform
TTL Propagation : Uniform
Entry Bindings:
Use cases | 53
-------------------------------------
LDP 1.1.1.1/32 default 30.0.3.1 exp-null 1/1/25
default operational
LDP 2.2.2.2/32 default 30.0.4.1 exp-null 1/1/26
default operational
LDP 3.3.3.3/32 default 30.0.5.2 exp-null lag100
default operational
LDP 4.4.4.4/32 default 30.0.5.2 18 lag100
default operational
Exit Bindings:
Transit Bindings:
VRF : default
Routemap In :
Routemap Out :
ORF type : Prefix-list
ORF capability :
Use cases | 55
Graceful-Restart : Enabled Gr. Restart Time : 120
Gr. Stalepath Time : 300 Remove Private-AS : No
TTL : 255 Local Cluster-ID :
Weight : 0 Fall-over : No
Confederation-Peers : No
Routemap In :
Routemap Out :
ORF type : Prefix-list
ORF capability :
Routemap In :
Routemap Out :
ORF type : Prefix-list
ORF capability :
Use cases | 57
Graceful-Restart : Enabled Gr. Restart Time : 120
Gr. Stalepath Time : 300 Remove Private-AS : No
TTL : 255 Local Cluster-ID :
Weight : 0 Fall-over : No
Confederation-Peers : No
Routemap In :
Routemap Out :
ORF type : Prefix-list
ORF capability :
VRF : default
Local Router-ID 5.5.5.5
MPLS Bindings
Entry Bindings : 4
Exit Bindings : 2
Transit Bindings : 4
PHP Mode : Explicit-Null
QoS Mode : Uniform
TTL Propagation : Uniform
Entry Bindings:
Exit Bindings:
Transit Bindings:
Use cases | 59
Origin codes: i - IGP, e - EGP, ? - incomplete
VRF : default
Local Router-ID 5.5.5.5
VRF : default
Local Router-ID 5.5.5.5
VRF: default
Use cases | 61
[110/100] 01h:12m:21s
3.3.3.3/32 30.0.5.2 lag100 - O
[110/50] 01h:11m:52s
4.4.4.4/32 30.0.5.2 lag100 - O
[110/100] 01h:11m:52s
5.5.5.5/32 - loopback0 - L [0/0]
-
30.0.0.0/24 30.0.5.2 lag100 - O
[110/200] 01h:11m:52s
30.0.3.1 1/1/25 -
[110/200] 01h:11m:52s
30.0.1.0/24 30.0.4.1 1/1/26 - O
[110/200] 01h:11m:52s
30.0.5.2 lag100 -
[110/200] 01h:11m:52s
30.0.2.0/24 30.0.5.2 lag100 - O
[110/100] 01h:11m:52s
30.0.3.0/24 - 1/1/25 - C [0/0]
-
30.0.3.2/32 - 1/1/25 - L [0/0]
-
30.0.4.0/24 - 1/1/26 - C [0/0]
-
30.0.4.2/32 - 1/1/26 - L [0/0]
-
30.0.5.0/24 - lag100 - C [0/0]
-
30.0.5.1/32 - lag100 - L [0/0]
-
PE1 configuration
Use cases | 63
ip mtu 9000
ip address 20.3.1.2/24
!
ip community-list standard site1_community description For_setting_community_From_
Site1
ip community-list standard site1_community seq 10 permit 99:99
!
!
!
route-map rmap1 permit seq 10
description For_setting_community_For Site1_Received_EBGP_routes
set community 99:99
route-map rmap2 deny seq 10
description For_Denying_routes_with_Site1_community_To_EBGP_Peer
match community-list site1_community
route-map rmap2 permit seq 20
description For_Allowing_all_other_route
!
router ospf 1
area 0.0.0.0
router bgp 6488163
neighbor 4.4.4.4 remote-as 6488163
neighbor 4.4.4.4 description Towards RR1{P1}
neighbor 4.4.4.4 update-source loopback 0
neighbor 5.5.5.5 remote-as 6488163
neighbor 5.5.5.5 description Towards RR2{P2}
neighbor 5.5.5.5 update-source loopback 0
address-family vpnv4 unicast
neighbor 4.4.4.4 activate
neighbor 4.4.4.4 send-community both
neighbor 5.5.5.5 activate
neighbor 5.5.5.5 send-community both
exit-address-family
!
vrf vrf_1
neighbor 20.1.1.1 remote-as 100
neighbor 20.1.1.1 description Towards CE1
neighbor 20.3.1.1 remote-as 100
neighbor 20.3.1.1 description Towards CE2
address-family ipv4 unicast
neighbor 20.1.1.1 activate
neighbor 20.1.1.1 route-map rmap1 in
neighbor 20.1.1.1 route-map rmap2 out
neighbor 20.1.1.1 send-community both
neighbor 20.1.1.1 soft-reconfiguration inbound
neighbor 20.3.1.1 activate
neighbor 20.3.1.1 route-map rmap1 in
neighbor 20.3.1.1 route-map rmap2 out
neighbor 20.3.1.1 send-community both
neighbor 20.3.1.1 soft-reconfiguration inbound
exit-address-family
!
vrf vrf_2
neighbor 20.1.1.1 remote-as 100
neighbor 20.1.1.1 description Towards CE1
neighbor 20.3.1.1 remote-as 100
neighbor 20.3.1.1 description Towards CE2
address-family ipv4 unicast
neighbor 20.1.1.1 activate
neighbor 20.1.1.1 route-map rmap1 in
neighbor 20.1.1.1 route-map rmap2 out
neighbor 20.1.1.1 send-community both
PE1 verification
Use cases | 65
No local binding
remote binding: lsr:5.5.5.5:0 label: exp-null
30.0.2.1/32
No local binding
remote binding: lsr:4.4.4.4:0 label: exp-null
1.1.1.1/32
local binding: label: exp-null
remote binding: lsr:5.5.5.5:0 label:16
remote binding: lsr:4.4.4.4:0 label:16
4.4.4.4/32
local binding: label: 16
remote binding: lsr:5.5.5.5:0 label:17
remote binding: lsr:4.4.4.4:0 label: exp-null
30.0.0.1/32
local binding: label: exp-null
No remote binding
3.3.3.3/32
local binding: label: 19
remote binding: lsr:5.5.5.5:0 label:19
remote binding: lsr:4.4.4.4:0 label:19
30.0.0.2/32
No local binding
remote binding: lsr:4.4.4.4:0 label: exp-null
30.0.4.2/32
No local binding
remote binding: lsr:5.5.5.5:0 label: exp-null
2.2.2.2/32
local binding: label: 18
remote binding: lsr:5.5.5.5:0 label:18
remote binding: lsr:4.4.4.4:0 label:18
30.0.3.1/32
local binding: label: exp-null
No remote binding
30.0.5.1/32
No local binding
remote binding: lsr:5.5.5.5:0 label: exp-null
MPLS Bindings
Entry Bindings : 8
Exit Bindings : 4
Transit Bindings : 6
PHP Mode : Explicit-Null
QoS Mode : Uniform
TTL Propagation : Uniform
Entry Bindings:
Exit Bindings:
Transit Bindings:
VRF : default
Use cases | 67
Local-AS Prepend : No Alt. Local-AS : 0
BFD : Disabled
Password :
Last Err Sent : No Error
Last SubErr Sent : No Error
Last Err Rcvd : No Error
Last SubErr Rcvd : No Error
Routemap In :
Routemap Out :
ORF type : Prefix-list
ORF capability :
Routemap In :
Routemap Out :
ORF type : Prefix-list
ORF capability :
VRF : default
Local Router-ID 1.1.1.1
Use cases | 69
Route Distinguisher: 2:1 (Label 22)
*> 102.0.0.0/24 0.0.0.0 0 100 0 100 i
VRF : vrf_1
BGP Summary
-----------
Local AS : 6488163 BGP Router Identifier : 20.3.1.2
Peers : 2 Log Neighbor Changes : No
Cfg. Hold Time : 180 Cfg. Keep Alive : 60
Confederation Id : 0
VRF : vrf_2
BGP Summary
-----------
Local AS : 6488163 BGP Router Identifier : 20.3.1.2
Peers : 2 Log Neighbor Changes : No
Cfg. Hold Time : 180 Cfg. Keep Alive : 60
Confederation Id : 0
VRF : default
Local Router-ID 1.1.1.1
VRF : vrf_1
Local Router-ID 20.3.1.2
Use cases | 71
*=e 101.0.0.0/24 20.1.1.1 0 100 0 100 i
*>e 101.0.0.0/24 20.3.1.1 0 100 0 100 i
*> 201.0.0.0/24 3.3.3.3 0 100 0 100 i
Total number of entries 3
VRF : vrf_2
Local Router-ID 20.3.1.2
VRF: default
VRF: vrf_1
VRF: vrf_2
PE2 configuration
Use cases | 73
PE2# show running
Current configuration:
!
!Version ArubaOS-CX LL.10.09.0001BF
!export-password: default
hostname PE2
profile core-spine
logging console severity crit
vrf vrf_1
rd 1:1
l3vpn-only
address-family ipv4 unicast
route-target export 1:1
route-target import 1:1
exit-address-family
vrf vrf_2
rd 2:1
l3vpn-only
address-family ipv4 unicast
route-target export 2:1
route-target import 2:1
exit-address-family
cli-session
timeout 0
!
!
!
!
!
!
ssh server vrf mgmt
vlan 1,2021-2022,2041-2042
interface mgmt
no shutdown
ip dhcp
interface 1/1/43
no shutdown
mtu 9000
description Towards CE1
no routing
vlan trunk native 1
vlan trunk allowed 2021-2022
interface 1/1/44
no shutdown
mtu 9000
description Towards CE2
no routing
vlan trunk native 1
vlan trunk allowed 2041-2042
interface 1/1/45
no shutdown
mtu 9198
description Towards P1
ip mtu 9198
ip address 30.0.1.1/24
ip ospf 1 area 0.0.0.0
mpls enable
mpls ldp enable
interface 1/1/46
no shutdown
mtu 9198
description Towards P2
Use cases | 75
neighbor 20.2.1.1 description Towards CE1
neighbor 20.4.1.1 remote-as 100
neighbor 20.4.1.1 description Towards CE2
address-family ipv4 unicast
neighbor 20.2.1.1 activate
neighbor 20.2.1.1 route-map rmap1 in
neighbor 20.2.1.1 route-map rmap2 out
neighbor 20.2.1.1 send-community both
neighbor 20.2.1.1 soft-reconfiguration inbound
neighbor 20.4.1.1 activate
neighbor 20.4.1.1 route-map rmap1 in
neighbor 20.4.1.1 route-map rmap2 out
neighbor 20.4.1.1 send-community both
neighbor 20.4.1.1 soft-reconfiguration inbound
exit-address-family
!
vrf vrf_2
neighbor 20.2.1.1 remote-as 100
neighbor 20.2.1.1 description Towards CE1
neighbor 20.4.1.1 remote-as 100
neighbor 20.4.1.1 description Towards CE2
address-family ipv4 unicast
neighbor 20.2.1.1 activate
neighbor 20.2.1.1 route-map rmap1 in
neighbor 20.2.1.1 route-map rmap2 out
neighbor 20.2.1.1 send-community both
neighbor 20.2.1.1 soft-reconfiguration inbound
neighbor 20.4.1.1 activate
neighbor 20.4.1.1 route-map rmap1 in
neighbor 20.4.1.1 route-map rmap2 out
neighbor 20.4.1.1 send-community both
neighbor 20.4.1.1 soft-reconfiguration inbound
exit-address-family
!
https-server vrf mgmt
mpls
enable
label-protocol ldp
enable
router-id loopback0
Use cases | 77
MPLS Bindings
Entry Bindings : 8
Exit Bindings : 4
Transit Bindings : 6
PHP Mode : Explicit-Null
QoS Mode : Uniform
TTL Propagation : Uniform
Entry Bindings:
Exit Bindings:
Transit Bindings:
VRF : default
Use cases | 79
Nexthop-Self : Default-Originate :
Cfg. Add-Path :
Neg. Add-Path :
Routemap In :
Routemap Out :
ORF type : Prefix-list
ORF capability :
Routemap In :
Routemap Out :
ORF type : Prefix-list
ORF capability :
VRF : default
Local Router-ID 2.2.2.2
Use cases | 81
-----------------------------
VRF : vrf_1
BGP Summary
-----------
Local AS : 6488163 BGP Router Identifier : 20.4.1.2
Peers : 2 Log Neighbor Changes : No
Cfg. Hold Time : 180 Cfg. Keep Alive : 60
Confederation Id : 0
VRF : vrf_2
BGP Summary
-----------
Local AS : 6488163 BGP Router Identifier : 20.4.1.2
Peers : 2 Log Neighbor Changes : No
Cfg. Hold Time : 180 Cfg. Keep Alive : 60
Confederation Id : 0
VRF : default
Local Router-ID 2.2.2.2
VRF : vrf_1
Local Router-ID 20.4.1.2
VRF : vrf_2
Local Router-ID 20.4.1.2
Use cases | 83
R - RIP, B - BGP, O - OSPF
Type Codes: E - External BGP, I - Internal BGP, V - VPN, EV - EVPN
IA - OSPF internal area, E1 - OSPF external type 1
E2 - OSPF external type 2
VRF: default
VRF: vrf_1
VRF: vrf_2
PE3 configuration
Use cases | 85
vlan 1,2051-2052
interface mgmt
no shutdown
ip dhcp
system interface-group 1 speed 10g
!interface group 1 contains ports 1/1/1-1/1/4
interface lag 99
no shutdown
description Towards P1
ip mtu 9198
ip address 30.0.2.2/24
lacp mode active
ip ospf 1 area 0.0.0.0
mpls enable
mpls ldp enable
interface lag 100
no shutdown
description Towards P2
ip mtu 9198
ip address 30.0.5.2/24
lacp mode active
ip ospf 1 area 0.0.0.0
mpls enable
mpls ldp enable
interface 1/1/19
no shutdown
mtu 9198
description Towards P1
lag 99
interface 1/1/20
no shutdown
mtu 9198
description Towards P1
lag 99
interface 1/1/21
no shutdown
mtu 9000
description Towards CE3
no routing
vlan trunk native 1
vlan trunk allowed 2051-2052
interface 1/1/22
no shutdown
mtu 9198
description Towards P2
lag 100
interface 1/1/23
no shutdown
mtu 9198
description Towards P2
lag 100
interface loopback 0
ip address 3.3.3.3/32
ip ospf 1 area 0.0.0.0
interface vlan 2051
vrf attach vrf_1
description Towards CE3
ip mtu 9000
ip address 20.5.1.1/24
interface vlan 2052
vrf attach vrf_2
description Towards CE3
PE3 verification
Use cases | 87
4.4.4.4 1 FULL/DR 30.0.2.1 lag99
MPLS Bindings
Entry Bindings : 8
Exit Bindings : 4
Transit Bindings : 6
PHP Mode : Explicit-Null
QoS Mode : Uniform
TTL Propagation : Uniform
Entry Bindings:
Exit Bindings:
Transit Bindings:
Use cases | 89
-----------------------------
LDP 1.1.1.1/32 16 lag100 default 30.0.5.1
16 operational
LDP 1.1.1.1/32 16 lag99 default 30.0.2.1
16 operational
LDP 2.2.2.2/32 17 lag100 default 30.0.5.1
18 operational
LDP 2.2.2.2/32 17 lag99 default 30.0.2.1
18 operational
LDP 4.4.4.4/32 18 lag99 default 30.0.2.1
exp-null operational
LDP 5.5.5.5/32 19 lag100 default 30.0.5.1
exp-null operational
VRF : default
Routemap In :
Routemap Out :
ORF type : Prefix-list
ORF capability :
Use cases | 91
Address family IPv4 Unicast No No
Address family IPv6 Unicast No No
Address family VPNv4 Unicast Yes Yes
Address family L2VPN EVPN No No
Routemap In :
Routemap Out :
ORF type : Prefix-list
ORF capability :
VRF : default
Local Router-ID 3.3.3.3
VRF : vrf_1
BGP Summary
-----------
Local AS : 6488163 BGP Router Identifier : 20.5.1.1
Peers : 1 Log Neighbor Changes : No
Cfg. Hold Time : 180 Cfg. Keep Alive : 60
Confederation Id : 0
VRF : vrf_2
BGP Summary
-----------
Local AS : 6488163 BGP Router Identifier : 20.5.1.1
Peers : 1 Log Neighbor Changes : No
Cfg. Hold Time : 180 Cfg. Keep Alive : 60
Confederation Id : 0
VRF : default
Local Router-ID 3.3.3.3
Use cases | 93
Network Nexthop Metric LocPrf Weight Path
VRF : vrf_1
Local Router-ID 20.5.1.1
VRF : vrf_2
Local Router-ID 20.5.1.1
VRF: default
VRF: vrf_1
VRF: vrf_2
Use cases | 95
Type Metric
------------------------------------------------------------------------------------
----------
20.5.1.0/24 - vlan2052 - C [0/0]
-
20.5.1.1/32 - vlan2052 - L [0/0]
-
102.0.0.0/24 1.1.1.1 lag100 default B/V
[200/0] 00h:54m:06s
202.0.0.0/24 20.5.1.2 vlan2052 - B/E
[20/0] 00h:54m:06s
n An MPLS L3 VPN network with a shared hub VRF that has connectivity to spoke VRFs, while spoke VRFs
that are isolated between each other
n CEs in hub VRF are expected to provide hub connectivity between CE spoke subnets (101.0.0.0/24 and
201.0.0.0/24) and hub subnets (151.0.0.0/24 and 0.0.0.0/0 default route)
n PE3 should not allow direct spoke to spoke connectivity, this is achieved through:
o Using hub_import VRF to advertise spoke CE subnets from PE1/PE2 to CE3
o Using hub_export VRF to advertise hub and spoke CE subnets from CE4 to PE1/PE2
n Sample configurations
n Relevant verification commands
CE1 Configuration
CE1 Verification
VRF : default
Use cases | 97
Description : Towards PE1
Peer-group :
Routemap In :
Routemap Out :
ORF type : Prefix-list
ORF capability :
Routemap In :
Routemap Out :
ORF type : Prefix-list
ORF capability :
CE1#
Use cases | 99
VRF : default
Local Router-ID 20.7.1.2
CE1#
CE1#
VRF: default
CE2 Configuration
CE2 Verification
VRF : default
Routemap In :
Routemap Out :
ORF type : Prefix-list
ORF capability :
Routemap In :
Routemap Out :
ORF type : Prefix-list
ORF capability :
CE2#
VRF : default
Local Router-ID 20.8.1.2
CE2#
CE2# show bgp all-vrf all summary
VRF : default
BGP Summary
-----------
Local AS : 101 BGP Router Identifier : 20.8.1.2
Peers : 2 Log Neighbor Changes : No
Cfg. Hold Time : 180 Cfg. Keep Alive : 60
Confederation Id : 0
CE2#
VRF: default
CE3 Configuration
CE3 Verification
VRF : default
Routemap In :
Routemap Out :
ORF type : Prefix-list
ORF capability :
CE3#
VRF : default
Local Router-ID 20.4.1.1
CE3#
CE3#
VRF: default
CE4 Configuration
CE4 Verification
VRF : default
Routemap In :
Routemap Out :
ORF type : Prefix-list
ORF capability :
CE4#
VRF : default
Local Router-ID 20.5.1.1
CE4#
CE4#
VRF: default
PE1 Configuration
PE1 Verification
PE1#
PE1#
MPLS Bindings
Entry Bindings : 9
Exit Bindings : 3
Transit Bindings : 3
PHP Mode : Explicit-Null
QoS Mode : Uniform
TTL Propagation : Uniform
Entry Bindings:
Exit Bindings:
Transit Bindings:
PE1#
VRF : default
Routemap In :
Routemap Out :
ORF type : Prefix-list
ORF capability :
Routemap In :
Routemap Out :
ORF type : Prefix-list
ORF capability :
PE1#
VRF : spoke_1
Routemap In :
Routemap Out :
ORF type : Prefix-list
ORF capability :
PE1#
PE1#
VRF : spoke_1
BGP Summary
-----------
Local AS : 6488163 BGP Router Identifier : 20.0.1.2
Peers : 1 Log Neighbor Changes : No
Cfg. Hold Time : 180 Cfg. Keep Alive : 60
Confederation Id : 0
PE1#
VRF: default
VRF: spoke_1
PE2 Configuration
PE2 Verification
PE2#
PE2# show mpls forwarding
MPLS Bindings
Entry Bindings : 9
Exit Bindings : 3
Transit Bindings : 3
PHP Mode : Explicit-Null
QoS Mode : Uniform
TTL Propagation : Uniform
Entry Bindings:
Exit Bindings:
Transit Bindings:
PE2#
VRF : default
Routemap In :
Routemap Out :
ORF type : Prefix-list
ORF capability :
Routemap In :
Routemap Out :
ORF type : Prefix-list
ORF capability :
PE2#
VRF : spoke_2
Routemap In :
Routemap Out :
ORF type : Prefix-list
ORF capability :
PE2#
VRF : spoke_2
Local Router-ID 20.1.1.2
PE2#
VRF : spoke_2
BGP Summary
-----------
Local AS : 6488163 BGP Router Identifier : 20.1.1.2
Peers : 1 Log Neighbor Changes : No
Cfg. Hold Time : 180 Cfg. Keep Alive : 60
Confederation Id : 0
VRF: default
VRF: spoke_2
PE3 Configuration
PE3 Verification
PE3#
MPLS Bindings
Entry Bindings : 5
Exit Bindings : 3
Transit Bindings : 3
PHP Mode : Explicit-Null
QoS Mode : Uniform
TTL Propagation : Uniform
Entry Bindings:
Exit Bindings:
Transit Bindings:
PE3#
VRF : default
Routemap In :
Routemap Out :
ORF type : Prefix-list
ORF capability :
Routemap In :
Routemap Out :
ORF type : Prefix-list
ORF capability :
PE3#
VRF : hub_import
Routemap In :
Routemap Out :
ORF type : Prefix-list
ORF capability :
PE3# show bgp vrf hub_export ipv4 unicast neighbors
Codes: ^ Inherited from peer-group
VRF : hub_export
Routemap In :
Routemap Out :
ORF type : Prefix-list
ORF capability :
PE3#
VRF : hub_import
Local Router-ID 20.2.1.1
VRF : hub_export
Local Router-ID 20.3.1.1
PE3#
VRF : hub_export
BGP Summary
-----------
Local AS : 6488163 BGP Router Identifier : 20.3.1.1
Peers : 1 Log Neighbor Changes : No
Cfg. Hold Time : 180 Cfg. Keep Alive : 60
Confederation Id : 0
VRF : hub_import
BGP Summary
-----------
Local AS : 6488163 BGP Router Identifier : 20.2.1.1
PE3#
VRF: default
VRF: hub_export
VRF: hub_import
MPLS commands
Description
Performs LSP label imposition by adding label to an ingress packet (push operation).
The no form of this command removes the ingress packet label.
Parameter Description
ipv4 <IP-ADDR> <MASK> Specifies the IPv4 destination in x.x.x.x format, where x is a
decimal value from 0 to 255 and the destination IP subnet
mask in x.x.x.x format, where x is a decimal value from 0 to
255.
Usage
n The no form of both the mpls and static-lsp commands deletes all static LSP bindings.
n The static LSP label range must be allocated before configuring static LSP bindings.
n Specifying an outgoing label outside the range of 16-1048575 is not allowed. An outgoing label is not
bound by allocated static LSP label range.
n Types of valid egress interfaces are: System, LAG, VLAN, and Tunnel.
o Routing must be enabled for egress interfaces.
o Interfaces must be configured before performing the bind command.
o LAG member interfaces are not allowed as egress interfaces.
Examples
Configuring binding:
Unconfiguring binding:
Configuring binding with an interface that does not have an IP address assigned:
Configuring binding with a next hop IP that is not in the same subnet as egress interface:
Configuring binding with a next hop IP that is the same as the egress interface IP:
Command History
Release Modification
Command Information
Description
Performs label disposition by removing label from an egress packet (pop operation).
The no form of this command removes the static LSP binding configuration.
Parameter Description
Usage
n The no form of both the mpls and static-lsp commands deletes all MPLS binding configurations.
n The static LSP label range must be allocated before configuring static LSP bindings.
n Specifying an incoming label outside the range of 16-1048575 is not allowed. An incoming label is bound
by the allocated static LSP label range.
Examples
Configuring static LSP binding for label disposition:
switch(config)# mpls
switch(config-mpls)# static-lsp
switch(config-mpls-static-lsp)# bind ipv4 input 20
switch(config)# mpls
switch(config-mpls)# static-lsp
switch(config-mpls-static-lsp)# no bind ipv4 input 20
Command History
Release Modification
Command Information
8360 config-aruba-central Administrators or local user group members with execution rights
for this command.
Description
Clears MPLS statistics per label for all sessions.
Parameter Description
Examples
Clearing ingress MPLS statistics for a specific label:
Command History
Release Modification
Command Information
8360 Operator (>) or Manager Administrators or local user group members with execution rights
(#) for this command.
Description
Configures a static LSP binding to swap labels and route to the given next hop.
The no form of this command removes the static LSP binding label swap configuration.
Usage
n A static LSP label range must be allocated before configuring static LSP bindings.
n An incoming label must be within the allocated static LSP label range. Outgoing labels are not bound by
the allocated static LSP label range, but must still be within the range of 16-1048575.
n The types of valid outgoing interfaces are: System, LAG, VLAN, and Tunnel.
o Routing must be enabled for egress interfaces.
o LAG member interfaces cannot be used with this command.
n Next hop and outgoing label pairs must be unique for each crossconnect binding.
Examples
Configuring crossconnect with an incoming and outgoing label:
switch(config)# mpls
switch(config-mpls)# static-lsp
switch(config-mpls-static-lsp)# crossconnect input 20 output 1/1/2 11.0.3.2 21
Configuring crossconnect with an interface that does not have routing enabled:
Configuring crossconnect with a nexthop IP that is the same as the egress interface IP:
Configuring crossconect with a nexthop IP and outgoing label of an already existing binding:
Command History
Release Modification
Command Information
Description
Examples
Enabling MPLS forwarding of IPv4 traffic:
switch(config)# mpls
switch(config-mpls)# enable
switch(config)# mpls
switch(config-mpls)# no enable
Command History
Release Modification
Command Information
8360 config-mpls Administrators or local user group members with execution rights
for this command.
Description
Enables MPLS LDP.
The no form of this command disable MPLS LDP.
Usage
n The LDP back off timer cannot be configured. It is set to exponentially back off session retry attempts
with initial value of 15 seconds and a maximum of 2 minutes.
Examples
Enabling MPLS LDP:
switch(config)# mpls
switch(config-mpls)# label-protocol ldp
switch(config-mpls-ldp)# enable
Command History
Release Modification
Command Information
8360 config-mpls-ldp Administrators or local user group members with execution rights
for this command.
Description
Enables MPLS static LSPs.
The no form of this command disables static LSPs.
Usage
A static LSP binding will be processed when MPLS is globally enabled, static LSP is enabled, and the ingress
and egress interface has MPLS enabled.
Examples
Enabling MPLS static LSPs:
switch(config)# mpls
switch(config-mpls)# enable
switch(config-mpls)# static-lsp
switch(config-mpls-static-lsp)# enable
switch(config)# mpls
switch(config-mpls)# static-lsp
switch(config-mpls-static-lsp)# no enable
Command History
Release Modification
Description
Enables MPLS forwarding of IP traffic for the interface.
The no form of this command disables MPLS forwarding of IP traffic for the interface.
Usage
n Routing must be configured before enabling MPLS on an interface.
Examples
Enabling MPLS forwarding:
Command History
Release Modification
Command Information
8360 config-if Administrators or local user group members with execution rights
for this command.
Description
Allocates MPLS labels for use exclusively by static LSP.
The no form of this command removes the configured allocation, returning to the default state with no
labels allocated for static LSP usage.
Parameter Description
<start-label-range> Selects the start of the static LSP label range. Range: 16-1048575.
<end-label-range> Selects the end of the static LSP label range. Range: 16-1048575.
Usage
n The range arguments are inclusive. Configuring a range of 20-30 will allocate the labels 20, 21, ..., 29, 30.
n Static LSP labels must not overlap with labels used by any other protocol, i.e. LDP. This label range
allocation command will fail if any labels are shared between protocols.
n Any change to the static LSP label allocation will fail if any static LSP bindings are configured. All bindings
must be removed before the static LSP label range can be reallocated.
n Allocated label range affects only the ingress packets. Labels for the outgoing packets must be within the
allocated label range of the next hop device.
Examples
Allocating a valid static LSP label range:
Changing the static LSP label range while LSP bindings are configured:
switch(config-mpls-static-lsp)# no label-range
All static LSP bindings must be removed before removing the label range.
Command History
Release Modification
Command Information
label-protocol ldp
label-protocol ldp
no label-protocol ldp
Description
Configures the Label Distribution Protocol (LDP).
The no form of this command removes all LDP-related configuration.
Examples
Configuring LDP:
Continue (y/n)? y
Command History
Release Modification
Command Information
8360 config-mpls Administrators or local user group members with execution rights
for this command.
mpls
mpls
no mpls
Description
Configures MPLS forwarding of IPv4 traffic globally.
The no form of the command removes all MPLS-related configuration.
Examples
Configuring MPLS forwarding for IPv4 traffic:
switch(config)# mpls
switch(config)# no mpls
All MPLS configuration will be deleted.
Continue (y/n)? y
Command History
Release Modification
Command Information
8360 config Administrators or local user group members with execution rights
for this command.
Description
Enables LDP protocol in the interface level.
The no form of this command disables LDP.
Usage
n Routing must be configured before enabling LDP on an interface.
n MPLS must be enabled on the interface prior to enabling LDP.
Examples
Enabling the LDP protocol:
Command History
Release Modification
Command Information
8360 config-if Administrators or local user group members with execution rights
for this command.
Description
Configures MPLS LDP discovery hold time for peers found via hello packets.
The no form of this command resets the discovery hello hold time to its default value of 15 seconds.
Parameter Description
Usage
n The default value of discovery hello hold time is 15 seconds
n The discovery hello hold time configured on an interface supersedes the global configuration.
n The discovery hello interval time is auto-computed as one third of the hello hold time.
Examples
Configuring the MPLS LDP discovery hello hold time:
switch(config)# mpls
switch(config-mpls)# label-protocol ldp
switch(config-mpls-ldp)# discovery hello holdtime 30
switch(config)# mpls
switch(config-mpls)# label-protocol ldp
switch(config-mpls-ldp)# discovery hello holdtime 50
Command History
Release Modification
Command Information
8360 config-mpls-ldp Administrators or local user group members with execution rights
for this command.
Description
Parameter Description
<SECONDS> Specifies the discover hello hold time on an interface. Range: 15-
65535. Default: 15.
Usage
n The interface LDP discovery hello hold time overrides global hello hold time.
n Routing must be configured before changing the LDP discovery hold time on an interface.
Examples
Configuring the interface MPLS LDP discovery hello hold time:
Removing the interface MPLS LDP discovery hello hold time configuration:
Configuring the interface MPLS LDP discovery hello hold time on a Layer 2 interface:
Command History
Release Modification
Command Information
8360 config-if Administrators or local user group members with execution rights
for this command.
Parameter Description
<TIME> Specifies the session hold time for the interface in seconds.
Range: 15-65535. Default: 40.
Usage
n The interface LDP session hold time overrides global hello hold time.
n Routing must be configured before changing LDP session holdtime on an interface.
Examples
Configuring the MPLS LDP session hold time for an interface:
Removing the MPLS LDP session hold time for the interface:
Command History
Release Modification
Command Information
8360 config-if Administrators or local user group members with execution rights
for this command.
Parameter Description
<IFNAME> Specifies the loopback interface for the MPLS LDP router ID.
Usage
n There is a possibility of MPLS traffic disruption whenever a router ID is deleted or updated to another
loopback interface.
n The MPLS router ID interface must be a loopback interface with an IPv4 address configured.
n The confirmation prompt is skipped if the router ID is being configured for the first time by the user.
n Changing the IP address of the loopback interface may interrupt MPLS traffic.
Examples
Configuring an MPLS LDP router ID:
switch(config)# mpls
switch(config-mpls)# enable
switch(config-mpls)# label-protocol ldp
switch(config-mpls-ldp)# enable
switch(config-mpls-ldp)# router-id loopback1
switch(config)# mpls
switch(config-mpls)# label-protocol ldp
switch(config-mpls-ldp)# router-id loopback2
Changing the router ID interface may disrupt MPLS traffic.
Continue (y/n)?
Changing the MPLS LDP router ID interface without prompting for confirmation:
switch(config)# mpls
switch(config-mpls)# label-protocol ldp
switch(config-mpls-ldp)# router-id loopback2 confirm
Continue (y/n)?
Removing the MPLS LDP router ID without providing loopback interface name:
Continue (y/n)?
Removing the configuration of an MPLS LDP router ID with an interface name which is different than the
one configured as router ID:
switch(config)# mpls
switch(config-mpls)# label-protocol ldp
switch(config-mpls-ldp)# enable
switch(config-mpls-ldp)# router-id 1/1/1
The router ID must be a loopback interface with an IP address assigned.
Configuring MPLS LDP router ID with a loopback interface without an IPv4 address configured:
switch(config)# mpls
switch(config-mpls)# label-protocol ldp
switch(config-mpls-ldp)# enable
switch(config-mpls-ldp)# router-id loopback1
The router ID interface must have an IP address assigned.
Command History
Release Modification
Command Information
8360 config-loopback-if Administrators or local user group members with execution rights
config-mpls-ldp for this command.
Description
Configures MPLS LDP session hold time.
The no form of this command resets the session hold time to its default value of 40 seconds.
Parameter Description
Usage
n The default session hold time is 40 seconds
n The session hold time configured on an interface supersedes the global configuration.
n The session keepalive interval time is auto computed as one sixth of the hold time.
Examples
Configuring the MPLS LDP session hold time:
switch(config)# mpls
switch(config-mpls)# label-protocol ldp
switch(config-mpls-ldp)# session holdtime 30
switch(config)# mpls
switch(config-mpls)# label-protocol ldp
switch(switch(config-mpls-ldp)# session holdtime 50)# session holdtime 50
Command History
Release Modification
Command Information
8360 config-mpls-ldp Administrators or local user group members with execution rights
for this command.
Description
Shows all vpnv4 entries in the BGP routing table .
Parameter Description
<IP-ADDR>/<MASK> Specifies the IP network and mask of a specific BGP route in IPv4
format (x.x.x.x/M), where x is a decimal number from 0 to 255 and
M is the number of bits in CIDR format from 0 to 32.
neighbors [<IP-ADDR>] Selects BGP neighbor connection parameters for all neighbors or
the IP address of a specific neighbor in IPv4 format (x.x.x.x) where
x is a decimal number from 0 to 255.
Examples
Showing all VPNv4 entries in the BGP routing table:
VRF : default
Local Router-ID 4.4.4.4
Showing entries in the BGP routing table for the 11.1.3.0/30 network:
VRF : default
BGP Local AS 100 BGP Router-id 4.4.4.4
AS-Path :
Cluster List :
Communities :
Ext-Communities :
Showing entries in the BGP routing table for routes with extended communities:
VRF : default
Local Router-ID 4.4.4.4
VRF : default
Routemap In :
Routemap Out :
ORF type : Prefix-list
ORF capability :
Showing BGP neighbor connection parameters for the neighbor with IP address 1.1.1.1:
VRF : default
------------------------------
Command History
Release Modification
Command Information
8360 Operator (>) or Manager Administrators or local user group members with execution rights
(#) for this command.
Examples
Configuring xxx...:
Showing xxx...:
Command History
Release Modification
Command Information
8360 Manager (#) Administrators or local user group members with execution rights
for this command.
Description
Usage
n Forwarding table filters will be implemented at a later date.
n When running this command on a huge-scale setup, showing the full tables might take a while.
Examples
Showing the MPLS forwarding table:
Command History
Release Modification
Command Information
8360 Operator (>) or Manager Administrators or local user group members with execution rights
(#) for this command.
Description
Shows the range of MPLS labels allocated for use in static LSP bindings and the range of labels currently
used by static LSP bindings.
Examples
Showing the range and usage of static LSp labels on the switch:
Command History
Release Modification
Command Information
8360 Operator (>) or Manager Operators or Administrators or local user group members with
(#) execution rights for this command. Operators can execute this
command from the operator context (>) only.
Description
Shows information about all MPLS LDP bindings.
Examples
Configuring xxx...:
10.10.2.0/24
local binding: label: imp-null
remote binding:lsr:10.255.255.255:0, label:16
remote binding:lsr:10.256.256.256:0, label: exp-null
10.10.3.0/24
local binding: label:20
remote binding:lsr:10.256.256.256:0, label:22
5.43.9.98/32
local binding: label:21
No remote binding
Command History
Release Modification
Command Information
8360 Operator (>) or Manager Administrators or local user group members with execution rights
(#) for this command.
Description
Shows information about discovered LDP peers.
Parameter Description
<IP-ADDR> Specifies the peer MPLS LDP router ID in x.x.x.x format, where x is
a decimal value from 0 to 255.
Examples
Showing information about discovered LDP peers:
Command History
Release Modification
Command Information
8360 Operator (>) or Manager Administrators or local user group members with execution rights
(#) for this command.
Description
Shows information about LDP neighbors in the current session(s).
Examples
Showing LDP neighbors:
Command History
Release Modification
Command Information
8360 Operator (>) or Manager Administrators or local user group members with execution rights
(#) for this command.
static-lsp
static-lsp
no static-lsp
Description
Configures MPLS static Label Switched Paths (LSP).
The no form of this command removes all static LSP configurations including label range allocation and static
LSP binding.
Examples
Configuring MPLS static LSP:
switch(config-mpls)# static-lsp
switch(config-mpls)# no static-lsp
Command History
Release Modification
Command Information
mirror session 1
enable
destination interface 1/1/40
source interface 1/1/51 both
diagnostics
diag-dump mpls basic
VRF: default
If the bolded examples are not seen, verify that remote PE has LDP established.
MPLS Bindings
Entry Bindings:
Origin Prefix Ingress Nexthop Outgoing Egress Egress Status
------------------------------------------------------------------------------------
--
LDP 2.2.2.2/32 default 30.0.0.2 17 1/1/38 default operational
LDP 3.3.3.3/32 default 30.0.0.2 exp-null 1/1/38 default operational
BGP 20.2.0.0/24 vrf_1 2.2.2.2 18 1/1/38 default operational
BGP 201.0.0.0/24 vrf_1 2.2.2.2 18 1/1/38 default operational
Exit Bindings:
VRF : default
Peer-group :
VRF : vrf_1
VRF: vrf_1
VRF: vrf_1
VRF : default
Local Router-ID 2.2.2.2
VRF: vrf_1
VRF: vrf_1
VRF: default
2. Is multicast and IPv6 routing and supported across an MPLS L3 VPN network with 10.09?
No, 10.09 MPLS L3 VPN only supports IPv4 unicast routing. VXLAN can be used on CEs to provide multicast
and IPv6 routing over the MPLS L3 VPN network.
6. Why is BGP peer establishment failing with a non-Aruba device as PE and Aruba device as P
router?
It is important to make sure that explicit-null is correctly configured on the non-Aruba PE device for
forwarding between the Aruba P device and non-Aruba PE device. The Aruba P device requires proper
explicit-null configuration for LDP label distribution. This enables BGP session establishment through the
MPLS core.
7. Why is BGP peer establishment causing intermittent flaps in the MPLS domain?
Accessing Updates
You can access updates from the Aruba Support Portal or the HPE My Networking Website.
My Networking
https://www.hpe.com/networking/support
To view and update your entitlements, and to link your contracts and warranties with your profile, go to the
Hewlett Packard Enterprise Support Center More Information on Access to Support Materials page:
https://support.hpe.com/portal/site/hpsc/aae/home/
Access to some updates might require product entitlement when accessed through the Hewlett Packard
Enterprise Support Center. You must have an HP Passport set up with relevant entitlements.
Some software products provide a mechanism for accessing software updates through the product
interface. Review your product documentation to identify the recommended software update method.
To subscribe to eNewsletters and alerts:
https://asp.arubanetworks.com/notifications/subscriptions (requires an active Aruba Support Portal (ASP)
account to manage subscriptions). Security notices are viewable without an ASP account.
Warranty Information
To view warranty information for your product, go to https://www.arubanetworks.com/support-
services/product-warranties/.
Regulatory Information
To view the regulatory information for your product, view the Safety and Compliance Information for Server,
Storage, Power, Networking, and Rack Products, available at https://www.hpe.com/support/Safety-
Compliance-EnterpriseProducts
Documentation Feedback
Aruba is committed to providing documentation that meets your needs. To help us improve the
documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback-
switching@hpe.com). When submitting your feedback, include the document title, part number, edition,
and publication date located on the front cover of the document. For online help content, include the
product name, product version, help edition, and publication date located on the legal notices page.