Manual:MPLS/Traffic-eng: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
mNo edit summary |
||
(One intermediate revision by the same user not shown) | |||
Line 1: | Line 1: | ||
{{Versions|v3, v4}} | {{Versions|v3, v4 +}} | ||
<div class=manual> | <div class=manual> | ||
==Summary== | |||
<p> | <p> | ||
</p> | </p> | ||
==Interface== | |||
<p><b>Sub-menu:</b> <code>/mpls traffic-eng interface</code></p> | <p id="shbox"><b>Sub-menu:</b> <code>/mpls traffic-eng interface</code></p> | ||
Line 123: | Line 123: | ||
</table> | </table> | ||
==Tunnel Path== | |||
<p><b>Sub-menu:</b> <code>/mpls traffic-eng tunnel-path</code></p> | <p id="shbox"><b>Sub-menu:</b> <code>/mpls traffic-eng tunnel-path</code></p> | ||
<br /> | |||
<b>Properties:</b> | <b>Properties:</b> | ||
Line 222: | Line 223: | ||
</table> | </table> | ||
==Monitoring TE Status== | |||
===Path State=== | |||
<p id="shbox"><b>Sub-menu:</b> <code>/mpls traffic-eng path-state</code></p> | |||
<br /> | |||
<p> | <p> | ||
</p> | </p> | ||
Line 263: | Line 264: | ||
|arg=in-interface | |arg=in-interface | ||
|type=string | |type=string | ||
|desc= | |desc=Interface on which path message is received. | ||
}} | }} | ||
Line 287: | Line 288: | ||
|arg=out-interface | |arg=out-interface | ||
|type=string | |type=string | ||
|desc= | |desc=Interface through which path message is sent out. | ||
}} | }} | ||
Line 341: | Line 342: | ||
|arg=sending-path | |arg=sending-path | ||
|type=<nowiki>yes | no</nowiki> | |type=<nowiki>yes | no</nowiki> | ||
|desc= | |desc=Whether path messages are being sent | ||
}} | }} | ||
Line 347: | Line 348: | ||
|arg=sending-resv | |arg=sending-resv | ||
|type=<nowiki>yes | no</nowiki> | |type=<nowiki>yes | no</nowiki> | ||
|desc= | |desc=Whether resv messages are being sent | ||
}} | }} | ||
Line 357: | Line 358: | ||
</table> | </table> | ||
===Resv State=== | |||
<p><b>Sub-menu:</b> <code>/mpls traffic-eng resv-state</code></p> | <p id="shbox"><b>Sub-menu:</b> <code>/mpls traffic-eng resv-state</code></p> | ||
<br /> | |||
<p> | <p> | ||
</p> | </p> | ||
Line 372: | Line 373: | ||
|arg=active | |arg=active | ||
|type=<nowiki>yes | no</nowiki> | |type=<nowiki>yes | no</nowiki> | ||
|desc= | |desc=Shows whether reservation is active. | ||
}} | }} | ||
Line 426: | Line 427: | ||
|arg=shared | |arg=shared | ||
|type=<nowiki>yes | no</nowiki> | |type=<nowiki>yes | no</nowiki> | ||
|desc= | |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>]] | ||
}} | }} | ||
Line 436: | Line 437: | ||
</table> | </table> | ||
==See also== | |||
<ul class="bullets"> | <ul class="bullets"> | ||
<li> [[M:MPLSVPLS|MPLSVPLS]] | <li> [[M:MPLSVPLS|MPLSVPLS]] |
Latest revision as of 11:47, 30 April 2010
Applies to RouterOS: v3, v4 +
Summary
Interface
Sub-menu: /mpls traffic-eng interface
Properties:
Property | Description |
---|---|
bandwidth (integer[bps]; Default: 0bps) | Total bandwidth that can be allocated on an interface by TE tunnels. |
blockade-k-factor (integer; Default: 3) | Value used to calculate blockade state timeout. |
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. |
down-flood-thresholds (integer[0..100],interer[0..100],...; Default: 15,30,45,60,75,80,85,90,95,97,98,99,100) | |
igp-flood-period (time; Default: 3m) | |
interface (string; Default: ) | Name of an interface on which to run RSVP. |
k-factor (integer; Default: 3) | 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. |
resource-class (integer[0..FFFFFFFF]; Default: 0) | |
te-metric (integer; Default: 1) | |
up-flood-thresholds (integer[0..100],interer[0..100],...; Default: 15,30,45,60,75,80,85,90,95,97,98,99,100) | |
use-udp (yes | no; Default: no) | 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. |
hops (Address:[strict|loose] [, Address:[strinct|loose]]; Default: ) | List of hops that path traverses. Used if use-cspf is not enabled. It is possible to specify strict hop or loose hop:
Read more >> |
name (string; Default: ) | Descriptive name of tunnel path |
record-route (yes | no; Default: ) | 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. |
See also
[ Top | Back to Content ]