Design Reference

• 5 adjacencies with an LSA_CNT of 200 (Area 3)
Calculate the number as follows:
3*500+10*1000+5*200=12.5K < 16K
This configuration ensures that the switch operates within accepted scalability limits.
OSPF design guidelines
Follow these additional OSPF guidelines:
• OSPF timers must be consistent across the entire network.
• Use OSPF area summarization to reduce routing table sizes.
• Use OSPF passive interfaces to reduce the number of active neighbor adjacencies.
• Use OSPF active interfaces only on intended route paths.
Configure wiring-closet subnets as OSPF passive interfaces unless they form a legitimate
routing path for other routes.
• Minimize the number of OSPF areas for each switch to avoid excessive shortest-path
calculations.
The switch executes the Djikstra algorithm for each area separately.
• Ensure that the OSPF dead interval is at least four times the OSPF hello-interval.
• Use MD5 authentication on untrusted OSPF links.
• Use stub or NSSAs as much as possible to reduce CPU overhead.
OSPF and CPU utilization
After you create an OSPF area route summary on an area border router, the summary route can
attract traffic to the area border router for which the router does not have a specific destination
route. Enabling ICMP unreachable-message generation on the switch can result in a high CPU
utilization rate.
To avoid high CPU utilization, Avaya recommends that you use a black-hole static route
configuration. The black-hole static route is a route (equal to the OSPF summary route) with a next
hop of 255.255.255.255. This configuration ensures that all traffic that does not have a specific next-
hop destination route is dropped.
OSPF network design examples
You can use OSPF routing in the core of a network. For more information, see
Layer 1, 2, and 3
design examples on page 170.
The following figure describes a simple implementation of an OSPF network: enabling OSPF on two
switches (S1 and S2) that are in the same subnet in one OSPF area.
Layer 3 network design
82 Network Design Reference for Avaya VSP 4000 Series June 2015
Comments on this document? [e-mail]