Automatic Restoration After the Number of Routes Exceeds the Upper Limit

A local core routing table stores routes of different routing protocols. If the number of routes in the local core routing table reaches the upper limit, no more route can be added to the table. The local core routing table has the following route limitations:
System route limit: specifies the maximum number of routes supported by the system.
System route prefix limit: specifies the range of prefixes for all the routes supported by the system.
Multicast IGP route limit: specifies the maximum number of multicast IGP routes.
Multi-topology route limit: specifies the maximum number of multi-topology routes.
Private network route limit: specifies the maximum number of private network routes supported by the system.
VPN route limit: specifies the maximum number of VPN routes supported by the system.
VPN route prefix limit: specifies the range of prefixes for all the VPN routes supported by the system.
If a protocol fails to add routes to the local core routing table due to a specific route limitation, the system records the failure with the protocol name and routing table ID.

After routes of protocols are deleted from the local core routing table, and the number of routes falls below the upper limit, the system prompts all the protocols that failed to add routes to the local core routing table to re-add the routes to the local core routing table. This process restores most of the routes in the local core routing table. The size of released table space determines whether all routes in the local core routing table can be restored.