Allied Telesis AlliedWare Plus Operating System Version 5.4.4C (x310-26FT,x310-26FP,x310-50FT,x310-50FP) - Manual (Page 713)

Route Selection
Software Reference for x310 Series Switches
C613-50046-01 REV A AlliedWare Plus TM Operating System - Version 5.4.4C 28.9
Troubleshooting routes not installed to the RIB
Possible reasons why a route is not installed in the RIB are:
■ The layer 3 interface is not in the Up state.
■ Route oscillation (route flap) is occurring with the route being added and removed
frequently.
■ The routing process from which the route is learned, has deleted the route.
■ A routing protocol has learned the maximum number of routes allowed by the
license, so the routes are not installed to the RIB.
See the max-static-routes command in the System Configuration and Monitoring
Commands chapter for detailed command description and command example
information, where static routes are applied before adding routes to the RIB.
Troubleshooting routes not installed to the FIB
Possible reasons why a route is not installed in the FIB are:
■ The maximum-paths limit may have been reached (currently supports up to eight
equal cost paths being installed).
■ The maximum-paths command may be set to a lower value preventing more paths
being selected as best.
■ The desired route type has a higher AD over another route entry in the RIB, so is not
preferred.
■ The max-fib-routes command is configured and the maximum number of installed
software FIB routes has been reached.
See the max-fib-routes command in the System Configuration and Monitoring
Commands chapter for detailed command description and command example
information to control the maximum number of FIB routes configured.