Adding and Managing Static Routes
The figure below shows the network configuration for the example:
In this example Gateway 1 (GW-1) is connected to the Internet. There
is no routing occurring on the interface connected to the Internet (no
OSPF, or BGP). Between Switch 1 (SW-1) and Switch 2 (SW-2) there is a corporate
WAN. There is also no routing occurring on this link. We want the remote
PC LAN to have Internet access. To reduce the amount of traffic on the
corporate WAN and comply with the Internet provider, we will use static
routes.
Static routes are routes that are administered manually. They do not
change and are not dynamic (hence the name). If a link goes down, there
is no fail over method for static routes. Although this is not a issue
on single link connections (connections that rely on one link for connectivity)
it makes debugging of link failures more difficult. You do however reduce
the amount of traffic by eliminating the routing updates that routing protocols
require.
There are many areas where static routes apply, such as in connections
to the Internet, across corporate WANs, and to create routing boundaries
between two areas.
Creating/Removing Static Routes
For the above example we will create one static default route to the
Internet through 22.1/22, and a static route across the Corporate WAN to
the remote PC LAN across 26.68/30.
Static Default Route
Static Routes (non default)
If you have configured OSPF or RIP on your remote office network then you will now have connectivity to the Internet.