Static routing is a form of routing that occurs when a router uses a manually-configured routing entry, rather than information from dynamic routing traffic.[1] In many cases, static routes are manually configured by a network administrator by adding in entries into a routing table, though this may not always be the case.[2] Unlike dynamic routing, static routes are fixed and do not change if the network is changed or reconfigured. Static routing and dynamic routing are not mutually exclusive. Both dynamic routing and static routing are usually used on a router to maximise routing efficiency and to provide backups in case dynamic routing information fails to be exchanged. Static routing can also be used in stub networks, or to provide a gateway of last resort.
Static routing may have the following uses:
Static routing, if used without dynamic routing, has the following advantages:[citation needed] Static routing can have some potential disadvantages:[3] To route IP traffic destined for the network 10.10.20.0/24 via the next-hop router with the IPv4 address of 192.168.100.1, the following configuration commands or steps can be used:
In most Linux distributions, a static route can be added using the iproute2 command. The following is typed at a terminal:-[5] root@router:~# ip route add 10.10.20.0 via 192.168.100.1
Enterprise-level Cisco routers are configurable using the Cisco IOS command line, rather than a web management interface.
The commands to add a static route are as follows:[6] Network configurations are not restricted to a single static route per destination:[6] Router> enable Router# configure terminal Router(config)# ip route 197.164.73.0 255.255.255.0 197.164.72.2 Router(config)# ip route 197.164.74.0 255.255.255.0 197.164.72.2Configuring administrative distanceThe administrative distance can be manually (re)configured so that the static route can be configured as a backup route, to be used only if the dynamic route is unavailable.[7] Router(config)# ip route 10.10.20.0 255.255.255.0 exampleRoute 1 254 Setting the administrative distance to 254 will result in the route being used only as a backup.
What is a floating static route, and what are its characteristics? This post will show how to configure a floating static route and provide a workflow and example configuration for real-world scenarios. What is a floating static route?As the name suggests, a floating static route is used in lifesaving situations as a float when the primary route to a destination network is down. A floating static route is a type of static route that can provide a backup path for a primary static or dynamic route in the event of a link failure. Because lower AD (Administrative Distance) is always preferred, you must configure it with a higher administrative distance than the original routing protocol to ensure that it is only used when the primary route (dynamic or static) is unavailable. What is a characteristic of a floating static route?Below are some of the characteristics of a floating static route.
Why is a floating static route important?A floating static route is important because it is used as a backup link to a destination network. If a route to the primary link fails, the floating static route will take over. This ensures a route is always available, and traffic can flow even if the primary route fails. A floating static route with IP SLA also allows a network administrator to dynamically change the route without reconfiguring anything in the entire network. This route is often used with a default route to provide better redundancy toward a destination network. How to configure a floating static route?Floating Static Route Example without IP SLA A simple floating static route is easier to configure. You create two identical routes with different next-hop addresses and administrative distances. – Configuration Example:
Always remember that the local interface status does not represent end-to-end transport, especially on multipoint interfaces or if any layer2 devices (switch or hub) in-between reside and fail. This will work if you do a recursive lookup that gives end-to-end next-hop reachability. However, a black hole (when the packets loop till the TTL expires) will create in this situation if there is no end-to-end next-hop reachability. Let’s take an example; assume the first route above is going across a layer2 switch. If the switchport facing the Router2 fails but the other local interface connected to the switch stays up, the local interface would still appear as UP/UP, creating a black hole for some duration. You can use Enhanced object tracking (IP SLA) to tackle these situations. Although generally advised is to use IP SLA tracking with floating static routes. Floating static route Cisco example use caseLet’s take a more practical approach and include IP SLA to track the reachability. What is a Floating Static Route – Example with IP SLA I have used cisco routers here for this example. If you use any device other than Cisco, please check with the vendor if they support this feature.
Show commands.
A Quick Floating Static Route Workflow
ConclusionIn summary, if you want to quickly create a high availability or redundancy route across your network, floating static routes are one of the best solutions. I hope you liked the article; please share. |