summaryrefslogtreecommitdiffstats
path: root/pathd/pathd.conf.sample
diff options
context:
space:
mode:
authorSebastien Merle <sebastien@netdef.org>2020-07-31 18:04:20 +0200
committerSebastien Merle <sebastien@netdef.org>2020-12-18 16:34:02 +0100
commit4d7b695d3abe80fbb1b666aed8faa1b9e9387fdb (patch)
tree9dc538cd213acebfe50152a048799f4f09bbcbc9 /pathd/pathd.conf.sample
parentMerge pull request #7717 from ranjanyash54/2368 (diff)
downloadfrr-4d7b695d3abe80fbb1b666aed8faa1b9e9387fdb.tar.xz
frr-4d7b695d3abe80fbb1b666aed8faa1b9e9387fdb.zip
pathd: New SR-TE policy management daemon
This new daemon manages Segment-Routing Traffic-Engineering (SR-TE) Policies and installs them into zebra. It provides the usual yang support and vtysh commands to define or change SR-TE Policies. In a nutshell SR-TE Policies provide the possibility to steer traffic through a (possibly dynamic) list of Segment Routing segments to the endpoint of the policy. This list of segments is part of a Candidate Path which again belongs to the SR-TE Policy. SR-TE Policies are uniquely identified by their color and endpoint. The color can be used to e.g. match BGP communities on incoming traffic. There can be multiple Candidate Paths for a single policy, the active Candidate Path is chosen according to certain conditions of which the most important is its preference. Candidate Paths can be explicit (fixed list of segments) or dynamic (list of segment comes from e.g. PCEP, see below). Configuration example: segment-routing traffic-eng segment-list SL index 10 mpls label 1111 index 20 mpls label 2222 ! policy color 4 endpoint 10.10.10.4 name POL4 binding-sid 104 candidate-path preference 100 name exp explicit segment-list SL candidate-path preference 200 name dyn dynamic ! ! ! There is an important connection between dynamic Candidate Paths and the overall topic of Path Computation. Later on for pathd a dynamic module will be introduced that is capable of communicating via the PCEP protocol with a PCE (Path Computation Element) which again is capable of calculating paths according to its local TED (Traffic Engineering Database). This dynamic module will be able to inject the mentioned dynamic Candidate Paths into pathd based on calculated paths from a PCE. https://tools.ietf.org/html/draft-ietf-spring-segment-routing-policy-06 Co-authored-by: Sebastien Merle <sebastien@netdef.org> Co-authored-by: Renato Westphal <renato@opensourcerouting.org> Co-authored-by: GalaxyGorilla <sascha@netdef.org> Co-authored-by: Emanuele Di Pascale <emanuele@voltanet.io> Signed-off-by: Sebastien Merle <sebastien@netdef.org>
Diffstat (limited to 'pathd/pathd.conf.sample')
-rw-r--r--pathd/pathd.conf.sample33
1 files changed, 33 insertions, 0 deletions
diff --git a/pathd/pathd.conf.sample b/pathd/pathd.conf.sample
new file mode 100644
index 000000000..fc7acafc1
--- /dev/null
+++ b/pathd/pathd.conf.sample
@@ -0,0 +1,33 @@
+! Default pathd configuration sample
+!
+password frr
+log stdout
+
+segment-routing
+ traffic-eng
+ segment-list test1
+ index 10 mpls label 123
+ index 20 mpls label 456
+ !
+ segment-list test2
+ index 10 mpls label 321
+ index 20 mpls label 654
+ !
+ policy color 1 endpoint 1.1.1.1
+ name one
+ binding-sid 100
+ candidate-path preference 100 name test1 explicit segment-list test1
+ candidate-path preference 200 name test2 explicit segment-list test2
+ !
+ policy color 2 endpoint 2.2.2.2
+ name two
+ binding-sid 101
+ candidate-path preference 100 name def explicit segment-list test2
+ candidate-path preference 200 name dyn dynamic
+ bandwidth 12345
+ metric bound abc 16 required
+ metric te 10
+ !
+ !
+ !
+!