summaryrefslogtreecommitdiff
path: root/zebra/zebra.conf.sample
diff options
context:
space:
mode:
authorVishal Kumar <vishal3.kumar@gmail.com>2012-12-07 14:47:58 -0800
committerScott Feldman <sfeldma@cumulusnetworks.com>2013-01-07 10:00:00 -0800
commitd265548ffb8da9ba3e1dd327efbff31c7cd15027 (patch)
tree2a44f386797da60d850f27f591a7d5d7d763c710 /zebra/zebra.conf.sample
parent0798cee34f5c436cd2a4b6e1d9a1ca90eee94292 (diff)
ospfd: Corrected ospfd Type-4/Type-5 ls update handling
This fix is for Type-4 LS updates handling at a ABR router where ospf daemon is not distributing Type-4 LS updates with correct LS-Age after learning about a ASBR router in a ospf network. Because of this Type-5 LS updates are not learnt in ospf network. Testing Scenario: This can be re-produced by restarting the ospfd daemon on DUT (mentioned in figure below)before the Hello time interval expires for area 0.0.0.1. ____ _______ ____ _________ | | area: 0.0.0.1 | | area: 0.0.0.0 | | area: 0.0.0.2 | | | R1 |---------------------|DUT/ABR|---------------------| R2 |------------------| R3/ASBR | |____| x.x.x.0/24 |_______| y.y.y.0/64 |____| z.z.z.0/24 |_________| In the above setup when ospfd is restarted (imp:before the Hello interval at R1 expires) and DUT learns about ASBR router R3 (Type-4) in the network from R2, but this ls-update is not propagates in area 0.0.0.1. So R1 never comes to know about the ASBR router in the network, so all the type-5 LS updates coming from R3 are not learnt by R1. Further if we again restart ospfd daemon it starts working fine. With the fix given this issue can be resolved. More Discussion on this is available at: http://www.gossamer-threads.com/lists/quagga/dev/23892 Signed-off-by: Scott Feldman <sfeldma@cumulusnetworks.com>
Diffstat (limited to 'zebra/zebra.conf.sample')
0 files changed, 0 insertions, 0 deletions