IPv4 Static Routing
- Overview of static routing
Static routes are manually configured entries in the IP routing table. - Configuring a basic IP static route
- Adding metrics to a static route
You can influence route preference by adding a cost metric or an administrative distance to a static route. - Naming an IP static route
IPv4 static route names are optional and non-unique. You can give a group of static routes the same name to help identify them. - Removing a name or a static route
- Configuring a physical interface as next hop
- Configuring a virtual interface as next hop
- Configuring a tunnel as next hop
- Configuring a static route for use with a route map
You can configure a static route with a tag that can be referenced in a route map. - Configuring a null route
You can configure a null static route to drop packets to a certain destination. This is useful when the traffic should not be forwarded if the preferred route is unavailable. - Configuring a default static route
You can manually create a default static route that the router uses if there are no other default routes to a destination. - Resolving a static route using other static routes
You can use next-hop recursive lookup to resolve a static route. - Resolving the next hop through a protocol
You can use routes from a specific protocol to resolve a configured static route. - Creating an IP static route in a non-default VRF
You can configure an IP static route in a non-default VRF. If the VRF is not named, the default VRF is used. - Configuring load sharing and redundancy
You can configure multiple IP static routes to the same destination to set up load sharing or backup routes. - Determining maximum static routes
You can modify the maximum number of static routes. - Displaying IPv4 static routes
You can check configured IPv4 routes, static routes, directly connected routes, routes configured for different protocols, the cost associated with each route, and the time the route has been available.