We were doing some tests on ospf, and we noticed that the firewall dont flush his ospf adjacency table even if a nheibour goes down, and this for a duration of one hour, in wich it continue to include the wrong information (concerning the gone neibour) into it's advertisement, wich cause inconsistency in routing politique.
Is ther any idea, is it a known bug?
We took a look at this in our lab and found that this is a limitation on the PAN box. Spoke with one of the engineers and it seems as if the age-out value for the routes is a feature that was not made configurable from the CLI/GUI. Please open up an enhancment request with your sales contact.
Thank you for the answers, but the problem here is not the age out of routes, but the issue is that the PAN device don't flush LSAs in the lsdb concerning a neighbour wich is gone (down), what we noticed, is that whene the PAN loose the neighbourship with the router, it marks it down as a neighbour, it flush the routes, but it does not flush the LSAs, and continue incrementing there age and advertising them to other neighbours, hope my clarifications will be useful to a more precise understanding of the issue and more efficient fix :smileyplain:
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!