Brief Overview of network: - Our network is pure level-3 level ISP backbone network. It is comprissed of mostly Cisco GSRs, 6500 & 7600 series devices. - IGP used in network is OSPF only and all the links used in backbone network are 10Gige & 1 Gige Ethernet only. - All edge and core routers in our network are receiving full internet routes through BGP but not redistributed in OSPF. - There are multiple leaf areas conneced to backbone area and each area is comprised of almost 10-25 devices. - There is huge database of OSPF and the timers used in OSPF are default.
Problem Description: - Few days back we faced link flap multiple times on one of our backbone router, which caused reconvergence of entire OSPF database. This convergernce took a long while because of huge OSPF database. - In order to achieve faster and stable convergence we are looking to fine tune OSPF timers using OSPF SPF/LSA throttling with default parameters.
Need suggestion, if it is recommended to implement OSPF SPF and LSA throttling in core backbone network of level-3 size ISP and what are the suggested values, which can be used when entire backbone is based on 1/10Gige ethernet links.
The first wait interval between SPF calculations is the amount of time in milliseconds specified by the spf-start argument. Each consecutive wait interval is two times the current hold level in milliseconds until the wait time reaches the maximum time in milliseconds as specified by the spf-max-wait argument. Subsequent wait times remain at the maximum until the values are reset or a link-state advertisement (LSA) is received between SPF calculations.
so you can use the command with a low start and hold time and an high maximum time (third parameter) as in the following example:
This example shows a router configured with the start, hold, and maximum interval values for the timers throttle spf command set at 5, 1,000, and 90,000 milliseconds, respectively.
router ospf 1
timers throttle spf 5 1000 90000
In case of single event the routers are still reactive but in case of flapping the third parameter allow to delay SPF execution to avoid waste of cpu and memory resources
without this commmand the behaviour is not self adaptive, so I think exact values are not important, what counts is the change to a self adaptive behaviour.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...