Manual:MPLS/Traffic-eng: Difference between revisions

From MikroTik Wiki
Jump to navigation Jump to search
No edit summary
mNo edit summary
 
(13 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{Versions|v3, v4}}
{{Versions|v3, v4 +}}


<div class=manual>
<div class=manual>


<h2>Summary</h2>
==Summary==
<p>
<p>
</p>
</p>


<h2>Interface</h2>
==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 28: Line 28:
|type=integer
|type=integer
|default=3
|default=3
|desc=
|desc=Value used to calculate blockade state timeout.
}}
}}


Line 63: Line 63:
|type=string
|type=string
|default=
|default=
|desc=Name of an interface on which to run TE.
|desc=Name of an interface on which to run RSVP.
}}
}}


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.
}}
</table>
 
 
<b>Read-only properties:</b>
{{Mr-arg-table-h
|prop=Property
|desc=Description
}}
 
{{Mr-arg-ro-table
|arg=remaining-bw
|type=integer[bps]
|desc=Shows currently unallocated bandwidth.
}}
}}
</table>
</table>


<h2>Tunnel Path</h2>
==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 122: Line 137:
|type=integer
|type=integer
|default=
|default=
|desc=
|desc=Do not use the path if [[#Interface | <code>resource-class</code>]] matches any of specified bits.
}}
}}


Line 129: Line 144:
|type=integer
|type=integer
|default=
|default=
|desc=
|desc=Use the path only if [[#Interface | <code>resource-class</code>]] matches all of specified bits.
}}
}}


Line 136: Line 151:
|type=integer
|type=integer
|default=
|default=
|desc=
|desc=Use the path if [[#Interface | <code>resource-class</code>]] matches any of specified bits.
}}
}}


Line 157: Line 172:
|type=integer[0..7]
|type=integer[0..7]
|default=
|default=
|desc=
|desc=Is used to decide whether this path can be preempted by another path. 0 sets the highest priority.
}}
}}


{{Mr-arg-table
{{Mr-arg-table
|arg=hops
|arg=hops
|type=Address:[strict|loose] [, Address:[strinct|loose]]
|type=<nowiki>Address:[strict|loose] [, Address:[strinct|loose]]</nowiki>
|default=
|default=
|desc=
|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:
<ul class="bullets">
<li> <var>strict</var> - defines that there must not be any other hops between previous hop and "strict" hop (fully specified path).
<li> <var>loose</var> - there are acceptable other hops between previous hop and defined hop (not fully specified path).
</ul>
[[M:Static TE tunnel path | <code>Read more >></code>]]
}}
}}


Line 178: Line 198:
|type=<nowiki>yes | no</nowiki>
|type=<nowiki>yes | no</nowiki>
|default=
|default=
|desc=
|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.
}}
}}


Line 185: Line 205:
|type=time
|type=time
|default=
|default=
|desc=
|desc=Interval in which tunnel path will be re-optimized. Useful if <code>use-cspf</code> is set to <b>yes</b>.
}}
}}


Line 192: Line 212:
|type=integer[0..7]
|type=integer[0..7]
|default=
|default=
|desc=
|desc=Parameter is used to decide whether this path can preempt another path. 0 sets the highest priority.
}}
}}


Line 203: Line 223:
</table>
</table>


<h2>Monitoring TE Status</h2>
==Monitoring TE Status==
 
<h3>Path State</h3>
<p><b>Sub-menu:</b> <code>/mpls traffic-eng path-state</code></p>


===Path State===
<p id="shbox"><b>Sub-menu:</b> <code>/mpls traffic-eng path-state</code></p>
<br />
<p>
<p>
</p>
</p>
Line 220: Line 240:
|arg=bandwidth
|arg=bandwidth
|type=integer[bps]
|type=integer[bps]
|desc=
|desc=Bandwidth required for the path
}}
}}


{{Mr-arg-ro-table
{{Mr-arg-ro-table
|arg=dst
|arg=dst
|type=
|type=address:integer
|desc=
|desc=Shows TE path destination address and tunnel ID.
}}
}}


{{Mr-arg-ro-table
{{Mr-arg-ro-table
|arg=egress
|arg=egress
|type=
|type=<nowiki>yes | no</nowiki>
|desc=
|desc=Shows if router is egress router of the path
}}
}}


{{Mr-arg-ro-table
{{Mr-arg-ro-table
|arg=forwarding
|arg=forwarding
|type=
|type=<nowiki>yes | no</nowiki>
|desc=
|desc=Shows if router is forwarding router of the path
}}
}}


{{Mr-arg-ro-table
{{Mr-arg-ro-table
|arg=in-interface
|arg=in-interface
|type=
|type=string
|desc=
|desc=Interface on which path message is received.
}}
}}


{{Mr-arg-ro-table
{{Mr-arg-ro-table
|arg=in-previous-hop
|arg=in-previous-hop
|type=
|type=IP
|desc=
|desc=Recorded previous hop
}}
}}


{{Mr-arg-ro-table
{{Mr-arg-ro-table
|arg=label
|arg=label
|type=
|type=integer
|desc=
|desc=
}}
}}
Line 261: Line 281:
{{Mr-arg-ro-table
{{Mr-arg-ro-table
|arg=locally-originated
|arg=locally-originated
|type=
|type=<nowiki>yes | no</nowiki>
|desc=
|desc=Shows if router is ingress router of the path
}}
}}


{{Mr-arg-ro-table
{{Mr-arg-ro-table
|arg=out-interface
|arg=out-interface
|type=
|type=string
|desc=
|desc=Interface through which path message is sent out.
}}
}}


{{Mr-arg-ro-table
{{Mr-arg-ro-table
|arg=out-label
|arg=out-label
|type=
|type=integer
|desc=
|desc=
}}
}}
Line 279: Line 299:
{{Mr-arg-ro-table
{{Mr-arg-ro-table
|arg=out-next-hop
|arg=out-next-hop
|type=
|type=IP
|desc=
|desc=
}}
}}
Line 291: Line 311:
{{Mr-arg-ro-table
{{Mr-arg-ro-table
|arg=path-in-record-route
|arg=path-in-record-route
|type=
|type=List of IPs
|desc=
|desc=Received recorded routes along the path.
}}
}}


Line 304: Line 324:
|arg=path-out-record-route
|arg=path-out-record-route
|type=
|type=
|desc=
|desc=List of recorded routes along the path that is sent out to next hop.
}}
}}


{{Mr-arg-ro-table
{{Mr-arg-ro-table
|arg=resv-bandwidth
|arg=resv-bandwidth
|type=
|type=integer[bps]
|desc=
|desc=bandwidth that TE path is reserving.
}}
}}


Line 321: Line 341:
{{Mr-arg-ro-table
{{Mr-arg-ro-table
|arg=sending-path
|arg=sending-path
|type=
|type=<nowiki>yes | no</nowiki>
|desc=
|desc=Whether path messages are being sent
}}
}}


{{Mr-arg-ro-table
{{Mr-arg-ro-table
|arg=sending-resv
|arg=sending-resv
|type=
|type=<nowiki>yes | no</nowiki>
|desc=
|desc=Whether resv messages are being sent
}}
}}


{{Mr-arg-ro-table
{{Mr-arg-ro-table
|arg=src
|arg=src
|type=
|type=Address:ID
|desc=
|desc=Shows source address and LSP ID number
}}
}}
</table>
</table>


<h3>Resv State</h3>
===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 352: Line 372:
{{Mr-arg-ro-table
{{Mr-arg-ro-table
|arg=active
|arg=active
|type=
|type=<nowiki>yes | no</nowiki>
|desc=
|desc=Shows whether reservation is active.
}}
}}


Line 359: Line 379:
|arg=bandwidth
|arg=bandwidth
|type=integer[bps]
|type=integer[bps]
|desc=
|desc=Bandwidth that RSVP session is allocating.
}}
}}


{{Mr-arg-ro-table
{{Mr-arg-ro-table
|arg=dst
|arg=dst
|type=
|type=address:ID
|desc=
|desc=Shows TE destination address and tunnel ID from RSVP session.
}}
}}


{{Mr-arg-ro-table
{{Mr-arg-ro-table
|arg=egress
|arg=egress
|type=
|type=<nowiki>yes | no</nowiki>
|desc=
|desc=Shows if router is egress router of the path
}}
}}


{{Mr-arg-ro-table
{{Mr-arg-ro-table
|arg=interface
|arg=interface
|type=
|type=string
|desc=
|desc=Shows an interface on which bandwidth is reserved
}}
}}


{{Mr-arg-ro-table
{{Mr-arg-ro-table
|arg=label
|arg=label
|type=
|type=integer
|desc=
|desc=
}}
}}
Line 394: Line 414:
{{Mr-arg-ro-table
{{Mr-arg-ro-table
|arg=non-output
|arg=non-output
|type=
|type=<nowiki>yes | no</nowiki>
|desc=
|desc=
}}
}}
Line 400: Line 420:
{{Mr-arg-ro-table
{{Mr-arg-ro-table
|arg=recorded-route
|arg=recorded-route
|type=
|type=IP[label]
|desc=
|desc=Shows recorded routes and labels along LSP.
}}
}}


{{Mr-arg-ro-table
{{Mr-arg-ro-table
|arg=shared
|arg=shared
|type=
|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>]]
}}
}}


{{Mr-arg-ro-table
{{Mr-arg-ro-table
|arg=src
|arg=src
|type=
|type=address:ID
|desc=
|desc=Shows TE source address and LSP ID from RSVP session.
}}
}}
</table>
</table>


<h2>See also</h2>
==See also==
<ul class="bullets">
<ul class="bullets">
<li> [[M:MPLSVPLS|MPLSVPLS]]
<li> [[M:MPLSVPLS|MPLSVPLS]]

Latest revision as of 09:47, 30 April 2010

Version.png

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:
  • strict - defines that there must not be any other hops between previous hop and "strict" hop (fully specified path).
  • loose - there are acceptable other hops between previous hop and defined hop (not fully specified path).
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 ]

Retrieved from "https://wiki.mikrotik.com/index.php?title=Manual:MPLS/Traffic-eng&oldid=17239"