![]() The maximum number of routers in one area is mostly dependent on CPU power you have for routing table calculation. It is not recommended separate areas with fewer than 50 routers. However, multi-area setups create additional complexity. This isolation of knowledge makes the protocol more scalable if multiple areas are used routing table calculation takes less CPU resources and routing traffic is reduced. The structure of an area is invisible from other areas. This means that each area has its own link-state database and corresponding shortest path tree. Each area runs a separate copy of the basic link-state routing algorithm. OSPF allows collections of routers to be grouped together. How many external routes were imported into OSPF from this router Number of OSPF database exchanges currently going on Shows how many times Dijkstra's algorithm was executed (i.e. type2 - ospf metric is equal only to the external route cost.Ĭommand /routing ospf monitor will display current OSPF status.įor multi instance OSPF you have to use following command:. ![]() type1 - ospf metric is the sum of the internal OSPF cost and the external route cost.OSPF protocol supports two types of metrics: If parameter is unset then DN bit is used according to RFC. Useful in some CE PE scenarios to inject intra area routes into VRF. The routing table this OSPF instance operates onįorces to use or ignore DN bit. If not specified, OSPF use lowest IP address configured on an active interface is used. Redistribute-static ( as-type-1 | as-type-2 | no Default: no) Redistribute routes learned by the RIP protocol Redistribute-rip ( as-type-1 | as-type-2 | no Default: no) ![]() Redistribute routes learned by other OSPF instances Redistribute-other-ospf ( as-type-1 | as-type-2 | no Default: no) Redistribute-connected ( as-type-1 | as-type-2 | no Default: no) Redistribute routes learned by the BGP protocol Redistribute-bgp ( as-type-1 | as-type-2 | no Default: no) Name of the routing filter chain used for outgoing prefixes Loopback interface from which to take IP address used as Router-ID in MPLS TE Opaque LSAs No more than one OSPF instance can have mpls-te-area configured. TE Opaque LSAs are generated in this area. The area used for MPLS traffic engineering. Static routes are distributed with this metric Routes learned from the RIP protocol are redistributed with this metric If auto is configured, then the cost from previous instance is taken into account, otherwise cost is set to statically configured value. Routes learned from other OSPF instances are redistributed with this metric. Metric-other-ospf ( integer|auto Default: 20) The default route is distributed with this metric Routes to directly connected networks are distributed with this metric ![]() When set to auto, MED attribute value from BGP route will be used, if MED is not set then default value 20 is used. Routes learned from the BGP protocol are redistributed with this metric. Name of the routing filter chain used for incoming prefixes Needed for interoperability with older Cisco systems. If set, then used in route redistribution (as route-tag in all external LSAs generated by this router), and in route calculation (all external LSAs having this route tag are ignored). By default Null domain-id is used, as described in RFC 4577. This value is attached to OSPF routes redistributed in BGP as VPNv4 routes as BGP extended community attribute, and used when BGP VPNv4 routes are redistributed back OSPF to determine whether to generate inter-area or AS-external LSA for that route.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |