Ospfv2 Implementation In Lenovo N/Os; Configurable Parameters; Defining Areas - Lenovo Flex System Fabric CN4093 Application Manual

OSPFv2 Implementation in Lenovo N/OS

Configurable Parameters

Defining Areas

© Copyright Lenovo 2015
Lenovo N/OS supports a single instance of OSPF and up to 2K routes on the
network. The following sections describe OSPF implementation in Lenovo N/OS:
"Configurable Parameters" on page 427

 "Defining Areas" on page 427
 "Interface Cost" on page 429
 "Electing the Designated Router and Backup" on page 429
 "Summarizing Routes" on page 430
 "Default Routes" on page 430
 "Virtual Links" on page 432
 "Router ID" on page 433
 "Authentication" on page 433
In Lenovo N/OS, OSPF parameters can be configured through the Command Line
Interfaces (CLI/ISCLI), Browser‐Based Interface (BBI), or through SNMP. For more
information, see "Switch Administration" on page
The CLI supports the following parameters: interface output cost, interface
priority, dead and hello intervals, retransmission interval, and interface transmit
delay.
In addition to the preceding parameters, you can specify the following:
 Shortest Path First (SPF) interval—Time interval between successive calculations
of the shortest path tree using the Dijkstra's algorithm.
Stub area metric—A stub area can be configured to send a numeric metric value

such that all routes received via that stub area carry the configured metric to
potentially influence routing decisions.
 Default routes—Default routes with weight metrics can be manually injected
into transit areas. This helps establish a preferred route when multiple routing
devices exist between two areas. It also helps route traffic to external networks.
 Passive—When enabled, the interface sends LSAs to upstream devices, but does
not otherwise participate in OSPF protocol exchanges.
 Point‐to‐Point—For LANs that have only two OSPF routing agents (the CN4093
and one other device), this option allows the switch to significantly reduce the
amount of routing information it must carry and manage.
If you are configuring multiple areas in your OSPF domain, one of the areas must
be designated as area 0, known as the backbone. The backbone is the central OSPF
area and is usually physically connected to all other areas. The areas inject routing
information into the backbone which, in turn, disseminates the information into
other areas.
27."
Chapter 31: OSPF
427