|desc=Value used to calculate blockade state timeout.
}}
}}
Line 70:
Line 70:
|type=integer
|type=integer
|default=3
|default=3
|desc=
|desc=Value used to calculate RSVP timeout. Timeout is calculated using following formula: <code>(K + 0.5)*1.5*R</code>, where K is <code>k-factor</code>, R is <code>refresh-time</code>. [[M:TE_Tunnels_Example | <code>Read more >></code>]]
}}
}}
Line 77:
Line 77:
|type=time
|type=time
|default=30s
|default=30s
|desc=
|desc=Interval in which RSVP Path messages are sent out.
}}
}}
Line 105:
Line 105:
|type=<nowiki>yes | no</nowiki>
|type=<nowiki>yes | no</nowiki>
|default=no
|default=no
|desc=
|desc=An RSVP implementation generally requires the ability to perform "raw" network I/O, i.e., to send and receive IP datagrams using protocol 46. Some systems may not support raw network I/O, in such cases RSVP messages can be encapsulated in UDP datagrams. Ports 1698 and 1699 will be used.
|desc=List of hops that path traverses. Used if <code>use-cspf</code> is not enabled. It is possible to specify <b>strict</b> hop or <b>loose</b> hop:
|desc=List of hops that path traverses. Used if <code>use-cspf</code> is not enabled. It is possible to specify <b>strict</b> hop or <b>loose</b> hop:
Line 183:
Line 184:
<li> <var>loose</var> - there are acceptable other hops between previous hop and defined hop (not fully specified path).
<li> <var>loose</var> - there are acceptable other hops between previous hop and defined hop (not fully specified path).
</ul>
</ul>
[[M:Static TE tunnel path | Read more >>]]
[[M:Static TE tunnel path | <code>Read more >></code>]]
}}
}}
Line 197:
Line 198:
|type=<nowiki>yes | no</nowiki>
|type=<nowiki>yes | no</nowiki>
|default=
|default=
|desc=Defines whether to record routes along the path.
|desc=If enabled, the sender node will receive information about the actual route that the LSP tunnel traverses. Record Route is analogous to a path vector, and hence can be used for loop detection.
|desc=Whether LSP tunnels can share resources, so that the new LSP tunnel can be set up without having to wait for the old LSP tunnel to be cleared. [[M:Interface/Traffic_Engineering#Reoptimization | <code>Read more >></code>]]
Value used to calculate RSVP timeout. Timeout is calculated using following formula: (K + 0.5)*1.5*R, where K is k-factor, R is refresh-time. Read more >>
refresh-time (time; Default: 30s)
Interval in which RSVP Path messages are sent out.
An RSVP implementation generally requires the ability to perform "raw" network I/O, i.e., to send and receive IP datagrams using protocol 46. Some systems may not support raw network I/O, in such cases RSVP messages can be encapsulated in UDP datagrams. Ports 1698 and 1699 will be used.
Read-only properties:
Property
Description
remaining-bw (integer[bps])
Shows currently unallocated bandwidth.
Tunnel Path
Sub-menu:/mpls traffic-eng tunnel-path
Properties:
Property
Description
affinity-exclude (integer; Default: )
Do not use the path if resource-class matches any of specified bits.
affinity-include-all (integer; Default: )
Use the path only if resource-class matches all of specified bits.
affinity-include-any (integer; Default: )
Use the path if resource-class matches any of specified bits.
comment (string; Default: )
Short description of the item
disabled (yes | no; Default: yes)
Defines whether item is ignored or used. By default VPLS interface is disabled.
holding-priority (integer[0..7]; Default: )
Is used to decide whether this path can be preempted by another path. 0 sets the highest priority.
If enabled, the sender node will receive information about the actual route that the LSP tunnel traverses. Record Route is analogous to a path vector, and hence can be used for loop detection.
reoptimize-interval (time; Default: )
Interval in which tunnel path will be re-optimized. Useful if use-cspf is set to yes.
setup-priority (integer[0..7]; Default: )
Parameter is used to decide whether this path can preempt another path. 0 sets the highest priority.
use-cspf (yes | no; Default: yes)
Whether to use CSPF to create dynamic tunnel path.
Monitoring TE Status
Path State
Sub-menu:/mpls traffic-eng path-state
Available read only properties:
Property
Description
bandwidth (integer[bps])
Bandwidth required for the path
dst (address:integer)
Shows TE path destination address and tunnel ID.
egress (yes | no)
Shows if router is egress router of the path
forwarding (yes | no)
Shows if router is forwarding router of the path
in-interface (string)
Interface on which path message is received.
in-previous-hop (IP)
Recorded previous hop
label (integer)
locally-originated (yes | no)
Shows if router is ingress router of the path
out-interface (string)
Interface through which path message is sent out.
out-label (integer)
out-next-hop (IP)
path-in-explicit-route ()
path-in-record-route (List of IPs)
Received recorded routes along the path.
path-out-explicit-route ()
path-out-record-route ()
List of recorded routes along the path that is sent out to next hop.
resv-bandwidth (integer[bps])
bandwidth that TE path is reserving.
resv-out-record-route ()
sending-path (yes | no)
Whether path messages are being sent
sending-resv (yes | no)
Whether resv messages are being sent
src (Address:ID)
Shows source address and LSP ID number
Resv State
Sub-menu:/mpls traffic-eng resv-state
Available read only properties:
Property
Description
active (yes | no)
Shows whether reservation is active.
bandwidth (integer[bps])
Bandwidth that RSVP session is allocating.
dst (address:ID)
Shows TE destination address and tunnel ID from RSVP session.
egress (yes | no)
Shows if router is egress router of the path
interface (string)
Shows an interface on which bandwidth is reserved
label (integer)
next-hop ()
non-output (yes | no)
recorded-route (IP[label])
Shows recorded routes and labels along LSP.
shared (yes | no)
Whether LSP tunnels can share resources, so that the new LSP tunnel can be set up without having to wait for the old LSP tunnel to be cleared. Read more >>
src (address:ID)
Shows TE source address and LSP ID from RSVP session.
