Solved: Frame-relay network with floating route

feroz syed · ‎09-17-2013

hi,

i have this frame relay network running rip protocol and aslo have a static route directly connect to R3 from R1, now the problem is when i close serial interface connected to frame-relay switchi lose connectivity from 192.168.1.0 network.

Here is my output files

R1#sh running-config

Building configuration...

Current configuration : 1844 bytes

!

upgrade fpd auto

version 12.4

service timestamps debug datetime msec

service timestamps log datetime msec

no service password-encryption

!

hostname R1

!

boot-start-marker

boot-end-marker

!

logging message-counter syslog

!

no aaa new-model

ip source-route

no ip icmp rate-limit unreachable

ip cef

!

no ip domain lookup

no ipv6 cef

!

multilink bundle-name authenticated

!

archive

log config

hidekeys

!

ip tcp synwait-time 5

!

interface Loopback1

ip address 3.3.3.3 255.255.255.255

!

interface FastEthernet0/0

ip address 172.12.23.2 255.255.255.224

duplex half

!

interface Serial1/0

ip address 192.168.1.3 255.255.255.0

encapsulation frame-relay

serial restart-delay 0

frame-relay map ip 192.168.1.2 301 broadcast

frame-relay map ip 192.168.1.1 301 broadcast

!

interface Serial1/1

ip address 210.1.1.2 255.255.255.0

serial restart-delay 0

!

interface Serial1/2

no ip address

shutdown

serial restart-delay 0

!

interface Serial1/3

no ip address

shutdown

serial restart-delay 0

!

interface Serial1/4

no ip address

shutdown

serial restart-delay 0

!

interface Serial1/5

no ip address

shutdown

serial restart-delay 0

!

interface Serial1/6

no ip address

shutdown

serial restart-delay 0

!

interface Serial1/7

no ip address

shutdown

serial restart-delay 0

!

router rip

version 2

network 172.12.0.0

network 192.168.1.0

network 210.1.1.0

no auto-summary

!

ip forward-protocol nd

ip route 1.1.1.1 255.255.255.255 192.168.1.1

ip route 2.2.2.2 255.255.255.255 192.168.1.1

no ip http server

no ip http secure-server

------------------------------------------------------------------------------------------------------------------------------------------------

R1#sh ip route

Gateway of last resort is not set

1.0.0.0/32 is subnetted, 1 subnets

C 1.1.1.1 is directly connected, Loopback1

2.0.0.0/32 is subnetted, 1 subnets

S 2.2.2.2 [1/0] via 192.168.1.2

3.0.0.0/32 is subnetted, 1 subnets

S 3.3.3.3 [1/0] via 192.168.1.3

172.12.0.0/27 is subnetted, 1 subnets

R 172.12.23.0 [120/1] via 210.1.1.2, 00:00:15, Serial1/1

R 192.168.1.0/24 [120/1] via 210.1.1.2, 00:00:15, Serial1/1

C 210.1.1.0/24 is directly connected, Serial1/1

R2#sh ip route

Gateway of last resort is not set

1.0.0.0/32 is subnetted, 1 subnets

S 1.1.1.1 [1/0] via 192.168.1.1

2.0.0.0/32 is subnetted, 1 subnets

C 2.2.2.2 is directly connected, Loopback1

3.0.0.0/32 is subnetted, 1 subnets

S 3.3.3.3 [1/0] via 192.168.1.1

172.12.0.0/27 is subnetted, 1 subnets

C 172.12.23.0 is directly connected, FastEthernet0/0

C 192.168.1.0/24 is directly connected, Serial1/0

R 210.1.1.0/24 [120/1] via 172.12.23.2, 00:00:19, FastEthernet0/0

R3#sh ip route

Gateway of last resort is not set

1.0.0.0/32 is subnetted, 1 subnets

S 1.1.1.1 [1/0] via 192.168.1.1

2.0.0.0/32 is subnetted, 1 subnets

S 2.2.2.2 [1/0] via 192.168.1.1

3.0.0.0/32 is subnetted, 1 subnets

C 3.3.3.3 is directly connected, Loopback1

172.12.0.0/27 is subnetted, 1 subnets

C 172.12.23.0 is directly connected, FastEthernet0/0

C 192.168.1.0/24 is directly connected, Serial1/0

C 210.1.1.0/24 is directly connected, Serial1/1

paul driver · ‎09-18-2013

Hello

"Router 1 has learned rip routes via R3 and R2 so router R1 know how to reach 192.168.1.2 and 172.12.23.2 destinations. R1 send rip updates via serial interface 1/1 (210.1.1.1)"

- Wrong
R1 has a valid next hop to reach R3 loopback because of the rip routes it learned from r3 via ser1/1 which included 192.168.1.0/24 and the subnet between r2&r3

However r2 k r3 still thinks to get to r1 loopback they need to go via ser0/1 and because these two rtrs are not aware 192.168 1.0/24 is not available due to their ser0/1 interfaces still being up this subnet is still being advertised are directly connected by both of them

This is not the case for r1 as its ser0/1 interface is down so the 192.168.10/24 isnt advertised in it rib table as directly connected and is now learned via rip over ser1/1

Res
Paul

Sent from Cisco Technical Support iPad App

Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

View solution in original post

cadet alain · ‎09-18-2013

Hi,

I don't see any floating route here as all your static routes have an AD of 1 which is the default, furthermure if you want to do failover then your static routes must be using the HDLC link between R1 and R3 and be for the same prefix advertised by your routing protocol.

What are you trying to achieve ? ping the loopback on R1 from R2 or R3 not using the frame-relay cloud when the frame-relay interface of R1 comes down ? if this is what you want then I'll post the configs to achieve this.

Regards

Alain

Don't forget to rate helpful posts.

feroz syed · ‎09-18-2013

well forget about the floating route, why i can't ping from network 210.1.1.1 to 192.168.1.2 or 1.3. but all loopback ping each other.

cadet alain · ‎09-18-2013

Hi,

So you're pinging R2 and R3 frame-relay IP sourcing from the hdlc link on R1 and it is failing but pinging the loopbacks on R2 and R3 from the same source is succeeding ?

Regards

Alain

Don't forget to rate helpful posts.

feroz syed · ‎09-18-2013

Sorry by mistake my prevoius post wrongly said tht all loopback pinging each other, now router 1 has ping connectivity to 3.3.3.3 and 210.1.1.2 and 172.12.23.2 and router 2 has ping connectivity to 172.12.23.2 and 210.1.1.1. and router 3 has only ping connectivity to 210.1.1.1

R1#ping 192.168.1.2