Floating Static for Redanduncy

A Floating static route is a route that  used for a backup route ,and it  has a higher administrative distance then the current route and dynamic routing protocol being used in a routing table.In this way, the floating static route will only appear in the routing table if the dynamically learned route is lost.

Configuring a floating static route is very easy with this command ip route n.n.n.n s.s.s.s nh.nh.nh.nh
but need to add a number to the end of the command ranging between 1-255 whereas 255 is “unreachable”.Any route given the administrative distance of 255 WILL NOT be installed in the routing table under any circumstances. Keep in mind the default administrative distance of a static route is 1.

Configuring floating static

R2(config)#do sh run | s route
ip route 3.3.3.3 255.255.255.255 10.1.13.3
ip route 3.3.3.3 255.255.255.255 10.1.14.3 30

R2(config)#do sh ip route | b Gate
Gateway of last resort is not set

     3.0.0.0/32 is subnetted, 1 subnets
S       3.3.3.3 [1/0] via 10.1.13.3
     10.0.0.0/24 is subnetted, 2 subnets
C       10.1.14.0 is directly connected, FastEthernet2/0
C       10.1.13.0 is directly connected, FastEthernet1/0

Verify the routing table

R2(config-if)#do sh ip route 3.3.3.3

Routing entry for 3.3.3.3/32

  Known via "static", distance 1, metric 0

  Routing Descriptor Blocks:

  * 10.1.13.3

      Route metric is 0, traffic share count is 1

R2#ping 3.3.3.3

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 3.3.3.3, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 20/40/64 ms

Tracing the route to 3.3.3.3 network

R2#traceroute 3.3.3.3

Type escape sequence to abort.

Tracing the route to 3.3.3.3

  1 10.1.13.3 112 msec 36 msec 24 msec

After Shuting down the interface fa 1/0 of R2

Traffic will go from backup route 10.1.14.3

R2(config)#int f 1/0
R2(config-if)#shutdown
R2(config-if)#
*Mar 1 00:07:03.235: %LINK-5-CHANGED: Interface FastEthernet1/0, changed state to administratively down
*Mar 1 00:07:04.235: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1/0, changed state to down


R2(config-if)#do sh ip route 3.3.3.3
Routing entry for 3.3.3.3/32
Known via "static", distance 30, metric 0
Routing Descriptor Blocks:
* 10.1.14.3
Route metric is 0, traffic share count is 1


R2#traceroute 3.3.3.3

Type escape sequence to abort.
Tracing the route to 3.3.3.3

  1 10.1.14.3 120 msec 60 msec 48 msec

R2(config-if)#do sh ip route | b Gate

Gateway of last resort is not set

     3.0.0.0/32 is subnetted, 1 subnets

S       3.3.3.3 [30/0] via 10.1.14.3

     10.0.0.0/24 is subnetted, 1 subnets

C       10.1.14.0 is directly connected, FastEthernet 2/0

Verify the output 2 of RIP v2

 

R2#debug ip rip ?

  database  RIP database events

  events    RIP protocol events

  trigger   RIP trigger extension

  <cr>

R2#debug ip rip

RIP protocol debugging is on

R2#

*Mar  1 00:13:10.147: RIP: received v2 update from 10.1.12.1 on FastEthernet0/0

*Mar  1 00:13:10.151:      1.1.1.0/24 via 0.0.0.0 in 1 hops

R2#

*Mar  1 00:13:13.891: RIP: sending v2 update to 224.0.0.9 via Loopback0 (2.2.2.2)

*Mar  1 00:13:13.891: RIP: build update entries

*Mar  1 00:13:13.891:   1.1.1.0/24 via 0.0.0.0, metric 2, tag 0

*Mar  1 00:13:13.891:   3.3.3.0/24 via 0.0.0.0, metric 2, tag 0

*Mar  1 00:13:13.891:   10.1.12.0/24 via 0.0.0.0, metric 1, tag 0

*Mar  1 00:13:13.891:   10.1.13.0/24 via 0.0.0.0, metric 1, tag 0

*Mar  1 00:13:13.899: RIP: ignored v2 packet from 2.2.2.2 (sourced from one of our addresses)

R2#

*Mar  1 00:13:15.191: RIP: sending v2 update to 224.0.0.9 via FastEthernet1/0 (10.1.13.2)

*Mar  1 00:13:15.195: RIP: build update entries

*Mar  1 00:13:15.195:   1.1.1.0/24 via 0.0.0.0, metric 2, tag 0

*Mar  1 00:13:15.199:   2.2.2.0/24 via 0.0.0.0, metric 1, tag 0

*Mar  1 00:13:15.199:   10.1.12.0/24 via 0.0.0.0, metric 1, tag 0

*Mar  1 00:13:15.331: RIP: received v2 update from 10.1.13.3 on FastEthernet1/0

*Mar  1 00:13:15.331:      3.3.3.0/24 via 0.0.0.0 in 1 hops

R2#

*Mar  1 00:13:25.999: RIP: sending v2 update to 224.0.0.9 via FastEthernet0/0 (10.1.12.2)

*Mar  1 00:13:26.003: RIP: build update entries

*Mar  1 00:13:26.003:   2.2.2.0/24 via 0.0.0.0, metric 1, tag 0

*Mar  1 00:13:26.007:   3.3.3.0/24 via 0.0.0.0, metric 2, tag 0

*Mar  1 00:13:26.007:   10.1.13.0/24 via 0.0.0.0, metric 1, tag 0

R2#debug ip rip database

RIP database events debugging is on

R2#

*Mar  1 00:19:09.203: RIP-DB: network_update with 1.1.1.0/24 succeeds

*Mar  1 00:19:09.207: RIP-DB: adding 1.1.1.0/24 (metric 1) via 10.1.12.1 on FastEthernet0/0 to RIP database

R2#

*Mar  1 00:19:19.207: RIP-DB: network_update with 3.3.3.0/24 succeeds

*Mar  1 00:19:19.211: RIP-DB: adding 3.3.3.0/24 (metric 1) via 10.1.13.3 on FastEthernet1/0 to RIP database

R2#debug ip rip events

RIP event debugging is on

R2#

*Mar  1 00:21:06.799: RIP: received v2 update from 10.1.13.3 on FastEthernet1/0

*Mar  1 00:21:06.799: RIP: Update contains 1 routes

R2#

*Mar  1 00:21:10.047: RIP: sending v2 update to 224.0.0.9 via Loopback0 (2.2.2.2)

*Mar  1 00:21:10.051: RIP: Update contains 4 routes

*Mar  1 00:21:10.051: RIP: Update queued

*Mar  1 00:21:10.055: RIP: Update sent via Loopback0

*Mar  1 00:21:10.063: RIP: ignored v2 packet from 2.2.2.2 (sourced from one of our addresses)

R2#

*Mar  1 00:21:12.275: RIP: sending v2 update to 224.0.0.9 via FastEthernet0/0 (10.1.12.2)

*Mar  1 00:21:12.279: RIP: Update contains 3 routes

*Mar  1 00:21:12.279: RIP: Update queued

*Mar  1 00:21:12.283: RIP: Update sent via FastEthernet0/0

R2#

*Mar  1 00:21:16.343: RIP: sending v2 update to 224.0.0.9 via FastEthernet1/0 (10.1.13.2)

*Mar  1 00:21:16.343: RIP: Update contains 3 routes

*Mar  1 00:21:16.343: RIP: Update queued

*Mar  1 00:21:16.343: RIP: Update sent via FastEthernet1/0

R2#

*Mar  1 00:21:28.731: RIP: received v2 update from 10.1.12.1 on FastEthernet0/0

*Mar  1 00:21:28.735: RIP: Update contains 1 routes

R2#

*Mar  1 00:21:35.191: RIP: received v2 update from 10.1.13.3 on FastEthernet1/0

Verify the output 1 of RIP v2

R2#sh run | s rip

router rip

 version 2

 network 2.0.0.0

 network 10.0.0.0

 no auto-summary

R3#sh run |  s rip

router rip

 version 2

 network 3.0.0.0

 network 10.0.0.0

 no auto-summary

R3#sh ip route rip

     1.0.0.0/24 is subnetted, 1 subnets
R       1.1.1.0 [120/2] via 10.1.13.2, 00:00:08, FastEthernet0/0
     2.0.0.0/24 is subnetted, 1 subnets
R       2.2.2.0 [120/1] via 10.1.13.2, 00:00:08, FastEthernet0/0
     10.0.0.0/24 is subnetted, 2 subnets
R       10.1.12.0 [120/1] via 10.1.13.2, 00:00:08, FastEthernet0/0

R2#sh ip rip database

1.0.0.0/8    auto-summary

1.1.1.0/24

    [1] via 10.1.12.1, 00:00:15, FastEthernet0/0

2.0.0.0/8    auto-summary

2.2.2.0/24    directly connected, Loopback0

3.0.0.0/8    auto-summary

3.0.0.0/8

    [1] via 10.1.13.3, 00:01:12, FastEthernet1/0

3.3.3.0/24

    [1] via 10.1.13.3, 00:00:15, FastEthernet1/0

10.0.0.0/8    auto-summary

10.1.12.0/24    directly connected, FastEthernet0/0

10.1.13.0/24    directly connected, FastEthernet1/0

R2#sh ip protocols

Routing Protocol is "rip"

  Outgoing update filter list for all interfaces is not set

  Incoming update filter list for all interfaces is not set

  Sending updates every 30 seconds, next due in 7 seconds

  Invalid after 180 seconds, hold down 180, flushed after 240

  Redistributing: rip

  Default version control: send version 2, receive version 2

    Interface             Send  Recv  Triggered RIP  Key-chain

    FastEthernet0/0       2     2

    FastEthernet1/0       2     2

    Loopback0               2     2

  Automatic network summarization is not in effect

  Maximum path: 4

  Routing for Networks:

    2.0.0.0

    10.0.0.0

  Routing Information Sources:

    Gateway         Distance      Last Update

    10.1.13.3            120      00:00:22

    10.1.12.1            120      00:00:25   

Distance: (default is 120)