Content deleted Content added
m unpiped links using script |
m Disambiguating links to Template engine (link changed to Template processor) using DisamAssist. |
||
Line 22:
Static routing can have some potential disadvantages:<ref>{{Cite web |title=Cisco Networking Articles |url=https://www.dummies.com/category/articles/cisco-33583/ |access-date=2013-11-05 |website=dummies |language=en |archive-url=https://web.archive.org/web/20131105090942/http://www.dummies.com/how-to/content/pros-and-cons-of-static-routing.html |archive-date=2013-11-05}}</ref>
* '''Human error:''' As the routes have to be manually configured this may be a source of human error in the absence of automated configuration management.
* '''Administrative overhead:''' Similarly the routes have to be provided to the devices. This can be remedied by configuration management, but also using simpler means of using a [[Template processor|template engine]] to generate configuration using repetition or [[IP address management]] software.
* '''Fault tolerance:''' While static routes not being removed during a network failure can be good in that routes continue to function, however, most implementations continue to use a static route as long as the interface the gateway is on is in an ''up'' state. When [[Failure of electronic components|network hardware fails]] it is not necessary ''down''; a [[Hang (computing)|hang]] may cause interfaces to keep running but not accept traffic. Routing protocols usually implement timeouts after which routes are removed or have integration with additional protocols such as [[Bidirectional Forwarding Detection]] to reduce the time the faulty route is present to sub-second.
* '''Observability:''' Static routes themselves do not propagate, which means that in a network built using only static routes it is hard to get a big picture of all present routes unless [[Event monitoring|monitored]]. Dynamic routing protocols often transmit topology information or can be connected to debugging tools such as a [[Looking Glass server]].
|