Configure LSP Routing in a Network Slice by Using a Path Computation Profile
A path computation profile defines the set of traffic
engineering (TE) constraints (for example, admin color, cost, and delay)
that Paragon Pathfinder
uses to compute
label-switched-paths (LSPs).
Note:
To configure LSP routing in a network slice by using computation profiles, you must have prior knowledge about:
- General TE concepts
- RFC7950, The YANG 1.1 Data Modeling Language
- RFC7951, JSON Encoding of Data Modeled with YANG
- RFC8040, Internet Web Replication and Caching Taxonomy
- RESTCONF protocol
You can use
path
computation profiles for deciding the routing of LSPs within a network slice. For example, you
can define a
profile
for routing LSPs with admin color 150 through a slice with
the slice
ID 100
or, you can also define a
profile
to route LSPs with slice ID 100 with a delay of 10 ms.
Note:
You can route PCC-delegated and PCC-controlled LSPs by using path computation profiles. You cannot route RSVP LSPs and PCE-initiated LSPs by using computational profiles.
Before you create a
profile, ensure that you have access to and understand the following:
-
juniper-pathfinder-lsp-policy.yang
-
juniper-pathfinder-profile.yang
-
lsp.json (REST LSP model)
To use a path computation profile for configuring network slices, you must:
- Create a profile (defined by the juniper-pathfinder-profile YANG model) in the RESTCONF interface .
- Configure a policy (defined by the juniper-pathfinder-lsp-policy YANG model) to map the LSP to the profile by using the RESCONF interface .
The following
example
profile
routes
LSPs on links that have lower delay.
{
"juniper-pathfinder-profile:computation-profiles": [
{
"comment": "Profile low-delay in use",
"id": "low-delay",
"path-affinities-values": {
"path-affinities-value": [
{
"usage": "resource-aff-include-any",
"value": "02"
}
]
}
}
]
}The following
sample
of a
policy
uses
the low-delay computation profile on LSPs that have
- String DEMO in their name, or
- SR-TE policy defined with admin color or SR-TE color between 100 and 200
You can interpret the policy condition by using grule. The LSP data follows the Paragon Pathfinder REST API model.
{
"juniper-pathfinder-lsp-policy:lsp-policy": {
"policy-definitions": {
"policy-definition": [{
"actions": {
"path-computation-profiles": [
"low-delay",
"prio-5"
]
},
"comment": "Use low delay for some LSPs(testMe)",
"conditions": {
"condition": "( (LSP.liveProperties != nil) && (LSP.liveProperties.srPolicy != nil) && ((LSP.liveProperties.srPolicy.color >= 100 || LSP.liveProperties.srPolicy.color <= 200 ))) || LSP.name.Contains(\"DEMO\")"
},
"name": "UseLowDelay",
"priority": 20,
"terminal": true
}]
}
}
}