Difference between revisions of "VPP/Segment Routing for MPLS"
(→Configuration on C1) |
(→Configuration on C2) |
||
| Line 47: | Line 47: | ||
==== Configuration on C2 ==== | ==== Configuration on C2 ==== | ||
| − | vpp# | + | The nodal SID |
| + | vpp# mpls local-label add 102 non-eos via mpls-llokup-in-table 0 | ||
| + | vpp# mpls local-label add 102 eos via ip4-lookup-in-table 0 | ||
| + | Reachability to other nodes | ||
| + | vpp# mpls local-label add 103 non-eos via 10.0.2.2 GigEthernet0/0/0 | ||
| + | vpp# mpls local-label add 103 eos via 10.0.2.2 GigEthernet0/0/0 | ||
| + | vpp# mpls local-label add 104 non-eos via 10.0.2.2 GigEthernet0/0/0 | ||
| + | vpp# mpls local-label add 104 eos via 10.0.2.2 GigEthernet0/0/0 | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | This configuration can be verified with the CLI: | |
| − | vpp# | + | vpp# show mpls fib |
| + | [todo] | ||
==== Configuration on C3 ==== | ==== Configuration on C3 ==== | ||
Revision as of 07:59, 29 November 2017
This example shows how to use the VPP platform to setup a L3VPN with SR MPLS. For further information regarding the SR MPLS implementation and CLI please visit the doxygen documentation. For further information on SRv6, tutorials and videos please visit www.segment-routing.net.
Contents
Introduction
Please see [https://wiki.fd.io/index.php?title=VPP/Segment_Routing_for_IPV6.
Topology Diagram
Our topology is simply going to be four VPP nodes with both, an IPv4 and IPv6 clients and servers attached to this core network. The 'core' network is running IPv4 only.
L3VPN for IPv6 traffic
On all nodes we will configure the nodal SID for that node (value 100 + node) and reachability to each of the other nodal SIDS.
In this example what we will do is on C1 create a SR Policy with only one SID list. This SID list will be <C2, C4>. On C1 I will add an steering policy to steer all the L3 traffic destined to B::/112 via the BindingSID of the SR policy we just created before.
Note that this is a L3VPN for all traffic from A:: to B::. In this example the returning path is not shown. The user must create another SR policy at C4 with the appropriate SR LocalSIDs at the different nodes for the returning path.
Configuration on C1
vpp# mpls local-label add 102 non-eos via 10.0.0.2 GigEthernet0/0/0 vpp# mpls local-label add 102 os via 10.0.0.2 GigEthernet0/0/0 vpp# mpls local-label add 103 non-eos via 10.0.1.2 GigEthernet0/0/1 vpp# mpls local-label add 103 eos via 10.0.1.2 GigEthernet0/0/1 vpp# mpls local-label add 104 non-eos via 10.0.1.2 GigEthernet0/0/1 vpp# mpls local-label add 104 eos via 10.0.1.2 GigEthernet0/0/1 vpp# sr mpls policy add bsid 999 next 102 104 vpp# sr steer l3 B::/112 via sr policy bsid 999
This configuration can be verified with the CLI:
vpp# show sr mpls pol [todo] ----------- vpp# show sr mpls steering policies [todo]
Configuration on C2
The nodal SID
vpp# mpls local-label add 102 non-eos via mpls-llokup-in-table 0 vpp# mpls local-label add 102 eos via ip4-lookup-in-table 0
Reachability to other nodes
vpp# mpls local-label add 103 non-eos via 10.0.2.2 GigEthernet0/0/0 vpp# mpls local-label add 103 eos via 10.0.2.2 GigEthernet0/0/0 vpp# mpls local-label add 104 non-eos via 10.0.2.2 GigEthernet0/0/0 vpp# mpls local-label add 104 eos via 10.0.2.2 GigEthernet0/0/0
This configuration can be verified with the CLI:
vpp# show mpls fib [todo]
Configuration on C3
None
Configuration on C4
vpp# sr localsid address C4::6 behavior end.dx6 GigabitEthernet0/5/0 B:C5::B vpp# show sr localsid SRv6 - My LocalSID Table: ========================= Address: c4::6 Behavior: DX6 (Endpoint with decapsulation and IPv6 cross-connect) Iface: GigabitEthernet0/5/0 Next hop: b:c5::b Good traffic: [6686 packets : 678832 bytes] Bad traffic: [0 packets : 0 bytes] --------------------
L3VPN for IPv4 traffic
In this example what we will do is on C1 create a SR Policy with only one SID list. This SID list will be <C2::, C4::4>. The SR policy will be using encapsulation. On C1 I will add an steering policy to steer all the L3 traffic destined to 2.2.2.0/24 via the BindingSID of the SR policy we just created before.
On C2 I will create one SR LocalSID with behavior End. (Endpoint)
On C4 I will create one SR LocalSID with behavior End.DX4 (Endpoint with Decapsulation and IPv4 cross-connect).
Note that this is a L3VPN for all traffic from 1.1.1.0/24 to 2.2.2.0/24. In this example the returning path is not shown. The user must create another SR policy at C4 with the appropriate SR LocalSIDs at the different nodes for the returning path.
Configuration on C1
vpp# set sr encaps source addr C1:: vpp# sr policy add bsid C1::999:2 next C2:: next C4::4 encap vpp# sr steer l3 2.2.2.0/24 via sr policy bsid C1::999:2
Configuration on C2
vpp# sr localsid address C2:: behavior end
Note here that this is the same SR LocalSID as the one created for the L3VPN for IPv6 traffic. Hence, you don't need to type this again.
Configuration on C3
None
Configuration on C4
vpp# sr localsid address C4::4 behavior end.dx4 GigabitEthernet0/6/0 2.2.2.2 vpp# show sr localsid SRv6 - My LocalSID Table: ========================= Address: c4::4 Behavior: DX4 (Endpoint with decapsulation and IPv4 cross-connect) Iface: GigabitEthernet0/6/0 Next hop: 2.2.2.2 Good traffic: [0 packets : 0 bytes] Bad traffic: [0 packets : 0 bytes] --------------------
