instability in the RIP routing table McAfee sidewinder
The FW presented instability in the RIP routing table. Which was possible to observe that the networks trailed RIP TIMEOUT not receive UPDATE within 180 seconds, the strange thing is that the UPDATE if received by the interface indicated.
The idea is to solve two questions presented to us in the activity.
1. The FW is able to withstand 5000 or more routes learned by RIP, or has a limit.
2. For the FW UPDATE ignores sent, by the large number of packages ¿? CPU processing priority ¿?
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.
Community Help Hub
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.