Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Problem with RIP

Status
Not open for further replies.

ash786

Technical User
Jun 20, 2001
38
0
0
GB
We have a London office where our headquarters are based, we also have 22 branches connected to the London office via Kilostream connection. All branches have ISDN running as backup to the primary lines. We have a another subnets that both the London users and the branch users have to connect to via a CISCO router.

At present the CISCO router has a list of static routes for all our branches, if the Kilostream connection to a branch goes down the ISDN is mannually kicked in and we physically change the route on the CISCO router. When the Kilostream link comes back up we change the route back on the CISCO. To avoid this tedious task I enabled RIP on the CISCO router. We mannually took down a Kilostream connection to a branch and enabled ISDN the CISCO router picked up the new route and worked OK, but when we reverted back to the kilostream connection the CISCO router failed to change it's routing information.

Any ideas

Thnks
 
think you should be configuring the isdn's as 'backup interfaces' to the serials, this should cause them to drop after the dialer idle timeout is reached, an alternative is to use floating statics with a metric of say 200 (assuming you're using default metrics)
 
RIP should work fine once the ISDN is set as a backup interface to the primary

ex:
backup delay 5 60
backup int bri0
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top