Better ospf metric explanation.
This commit is contained in:
parent
5a063efeea
commit
94e2bbcc72
1 changed files with 2 additions and 0 deletions
|
@ -1118,9 +1118,11 @@ External routes use <cf/metric type 1/ or <cf/metric type 2/.
|
||||||
A <cf/metric of type 1/ is comparable with internal <cf/metric/, a
|
A <cf/metric of type 1/ is comparable with internal <cf/metric/, a
|
||||||
<cf/metric of type 2/ is always longer
|
<cf/metric of type 2/ is always longer
|
||||||
than any <cf/metric of type 1/ or any <cf/internal metric/.
|
than any <cf/metric of type 1/ or any <cf/internal metric/.
|
||||||
|
If you specify both metrics only metric1 is used.
|
||||||
Each external route can also carry a <cf/tag/ which is a 32-bit
|
Each external route can also carry a <cf/tag/ which is a 32-bit
|
||||||
integer which is used when exporting routes to other protocols;
|
integer which is used when exporting routes to other protocols;
|
||||||
otherwise, it doesn't affect routing inside the OSPF domain at all.
|
otherwise, it doesn't affect routing inside the OSPF domain at all.
|
||||||
|
Default is <cf/metric of type 2 = 10000/ and <cf/tag = 0/.
|
||||||
|
|
||||||
<sect1>Example
|
<sect1>Example
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue