RSVP-TE Tunnel Support
Capability |
Notes |
---|---|
PCE-initiated tunnels (provisioned or discovered by Crosswork Optimization Engine) |
— |
PCC-initiated tunnels (discovered by Crosswork Optimization Engine) |
— |
ERO strict hops |
— |
ERO loose hops (PCC-initiated only) |
— |
FRR protection on tunnels provisioned by Crosswork Optimization Engine |
— |
Path optimization objective min-metric (IGP,TE, or Latency) |
— |
Path constraints (affinity and disjointness) |
Only 2 RSVP tunnels per disjoint group or sub-id is supported |
Binding Label for explicit and dynamic tunnels |
— |
Signaled Bandwidth |
— |
Setup/Hold Priority |
— |
Description |
Notes |
---|---|
Configuring loose hop ERO in COE |
Only strict hops can be configured. If strict hops are not configured for every hop along the path and those hops are not remote interface IPs or loopback IPs, unexpected behavior may occur. For example, a tunnel may remain operationally down, hops may be modified, and so on. |
Named tunnels configured on PCCs |
These tunnels are not discovered by Crosswork Optimization Engine. |
Tunnels with Loopback IPs other than TE router ID for headend or endpoint and path hops |
— |
Display of active FRR protected paths in the topology map. |
Crosswork Optimization Engine discovers FRR tunnels which are displayed in the topology map, but will not associate an actively protected tunnel with the FRR tunnel being used. The path in the topology map will not include FRR protected paths when protection is active. |
P2MP tunnels |
— |