Manual:MPLS: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
==Sub Categories== | |||
{{ycgu-cooltable-3 | {{ycgu-cooltable-3 | ||
| Line 68: | Line 64: | ||
==Summary== | |||
'''[http://mikrotik.com/software.html MikroTik RouterOS] supports MPLS. | |||
All [http://routerboard.com MikroTik RouterBOARD] hardware products support MPLS.''' | |||
==General Porperties== | |||
{{Mr-arg-table-h | |||
|prop=Property | |||
|desc=Description | |||
}} | |||
{{Mr-arg-table | |||
|arg=dynamic-label-range | |||
|type=range of integer[16..1048575] | |||
|default=16-1048575 | |||
|desc=Range of Label numbers used for dynamic allocation. First 16 labels are reserved for special purposes (as defined in RFC). If you intend to configure labels statically then adjust dynamic default range not to include numbers that will be used in static configuration. | |||
}} | |||
{{Mr-arg-table-end | |||
|arg=propagate-ttl | |||
|type=yes {{!}} no | |||
|default=yes | |||
|desc=Whether to copy TTL values from IP header to MPLS header. If this option is set to '''no''' then hops inside MPLS cloud will be invisible from traceroutes. | |||
}} | |||
==Forwarding Table== | |||
==Interface== | |||
==Local Bindings== | |||
==Remote Bindings== | |||
{{cont}} | |||
[[Category:Manual]] | [[Category:Manual]] | ||
[[Category:Internetworking]] | [[Category:Internetworking]] | ||
[[Category:MPLS]] | [[Category:MPLS]] | ||
Revision as of 10:49, 3 October 2011
Sub Categories
|
List of reference sub-pages |
Case studies |
List of examples |
|
General
|
General
|
Summary
MikroTik RouterOS supports MPLS. All MikroTik RouterBOARD hardware products support MPLS.
General Porperties
| Property | Description |
|---|---|
| dynamic-label-range (range of integer[16..1048575]; Default: 16-1048575) | Range of Label numbers used for dynamic allocation. First 16 labels are reserved for special purposes (as defined in RFC). If you intend to configure labels statically then adjust dynamic default range not to include numbers that will be used in static configuration. |
| propagate-ttl (yes | no; Default: yes) | Whether to copy TTL values from IP header to MPLS header. If this option is set to no then hops inside MPLS cloud will be invisible from traceroutes. |
Forwarding Table
Interface
Local Bindings
Remote Bindings
[ Top | Back to Content ]