1
a static route is a means to get to the specified destination
"static" comes from the fact that the route is user-configured and the decision of that path is not decided dynamically by a routING protocol
ip route 10.1.1.0 255.255.255.0 172.18.1.2
is a static route that says "in order to get to 10.1.1.0/24 network, you have to find 172.18.1.2 first"
172.18.1.2 could be the ip address of a directly connected router interface
2 nope, if they do the routing tables will get messed up
3 Yes but only if you use "floating" static routes
ip route 10.1.1.0 255.255.255.0 172.18.1.2
ip route 10.1.1.0 255.255.255.0 172.17.1.2 100
this basically says "in order to get to 10.1.1.0/24 network, you have to find 172.18.1.2 first, BUT if that route is unreachable use 172.17.1.2" and if that 2nd gateway (172.17.1.2) is unereachable, well, you are screwed.
the 100 represents "the administrative distance". the lower the better/more preferred. the default for static routes is 1
the beauty in using dynamic routING protocols is that paths to destinations are determine by availabilty of other routers on down the line to that destination. The majority of the routers on the Internet communicate using a routING protocol called BGP. if a major router goes down, BGP in other Internet routers will recalculate their routing tables and find an alternate way around the problem device. using static routes is fine in smaller networks, but when they get to be more than say, 4 routers, it's time to start using a dynamic routING protocol.
4
if i understand you correctly that can be done using Hot Standby Routing protocol and IP Unnumberred.
Get Connected - I.T.