Better explanation of OSPF attributes. But it's still not perfect.
This commit is contained in:
parent
4e8ec66698
commit
f06a219a24
1 changed files with 9 additions and 6 deletions
|
@ -1023,12 +1023,15 @@ protocol ospf <name> {
|
||||||
|
|
||||||
<sect1>Attributes
|
<sect1>Attributes
|
||||||
|
|
||||||
<p>OSPF defines three route attributes. Each internal route has a metric. External
|
<p>OSPF defines three route attributes. Each internal route has a <cf/metric/
|
||||||
routes use metric type 1 or metric type 2. A metric of type 1 is comparable
|
Metric is ranging from 1 to infinity (65535).
|
||||||
with internal metrics, a metric of type 2 is always longer than any metric of type 1
|
External routes use <cf/metric type 1/ or <cf/metric type 2/.
|
||||||
or any internal metric. Each external route can also carry a tag which is
|
A <cf/metric of type 1/ is comparable with internal <cf/metric/, a
|
||||||
a 32-bit integer which is used when exporting routes to other protocols; otherwise,
|
<cf/metric of type 2/ is always longer
|
||||||
it doesn't affect routing inside the OSPF domain at all.
|
than any <cf/metric of type 1/ or any <cf/internal metric/.
|
||||||
|
Each external route can also carry a <cf/tag/ which is a 32-bit
|
||||||
|
integer which is used when exporting routes to other protocols;
|
||||||
|
otherwise, it doesn't affect routing inside the OSPF domain at all.
|
||||||
|
|
||||||
<sect1>Example
|
<sect1>Example
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue