Re: Backup Interface and Routing!

2000-11-08 Thread lawrence sculark

are you using any snmp applications that monitor this backup link???
if so, you will need to use an access-list or place the isdn interface in 
standy-mode by [backup interface bri1/0] [backup delay]to prevent the snmp 
activity from polling your backup interface$lawrence


>From: "Hans Schimek" <[EMAIL PROTECTED]>
>Reply-To: "Hans Schimek" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Subject: Backup Interface and Routing!
>Date: Wed, 8 Nov 2000 22:32:16 +0100
>MIME-Version: 1.0
>Received: from [208.32.175.78] by hotmail.com (3.2) with ESMTP id 
>MHotMailBBD313A400B2D820F3B6D020AF4E0B3024; Wed Nov 08 13:44:50 2000
>Received: from localhost (mail@localhost)by groupstudy.com (8.9.3/8.9.3) 
>with SMTP id QAA16000;Wed, 8 Nov 2000 16:41:55 -0500
>Received: by groupstudy.com (bulk_mailer v1.12); Wed, 8 Nov 2000 16:35:33 
>-0500
>Received: (from listserver@localhost)by groupstudy.com (8.9.3/8.9.3) id 
>QAA14075GroupStudy Mailer; Wed, 8 Nov 2000 16:35:32 -0500
>Received: from email01.aon.at (WARSL401PIP1.highway.telekom.at 
>[195.3.96.69])by groupstudy.com (8.9.3/8.9.3) with SMTP id 
>QAA14048GroupStudy Mailer; Wed, 8 Nov 2000 16:35:29 -0500
>Received: (qmail 374726 invoked from network); 8 Nov 2000 21:31:15 -
>Received: from n229p018.adsl.highway.telekom.at (HELO homer) 
>([213.33.28.146]) (envelope-sender <[EMAIL PROTECTED]>)  by 
>qmail1.highway.telekom.at (qmail-ldap-1.03) with SMTP  for 
><[EMAIL PROTECTED]>; 8 Nov 2000 21:31:15 -
>From [EMAIL PROTECTED] Wed Nov 08 13:46:11 2000
>Message-ID: <[EMAIL PROTECTED]>
>X-Priority: 3 (Normal)
>X-MSMail-Priority: Normal
>X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
>X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
>Importance: Normal
>Sender: [EMAIL PROTECTED]
>Precedence: bulk
>X-MIME-Autoconverted: from 8bit to quoted-printable by groupstudy.com id 
>QAA16000
>
>Hi!
>
>i configured a serial link and an ISDN link between two routers.
>the serial line is the primary line. if it fails the backup line
>  ISDN-Interface)
>takes over.
>i configured RIP -
>To prevent Routing Updates from establishing the call
>i set the ISDN-Interface as PASSIVE.
>Updates didn`t initate the call anymore.
>BUT !
>what about the routing information. if the primary fails, no routing 
>updates
>won`t flow. so i configured static routes with a higher administrative
>distance
>-
>
>IS THERE ANOTHER SOLUTION FOR THAT PROBLEM !
>
>
>thanx in advance
>
>
>
>
>=
>Hans Schimek
>
>Student
>Fachhochschule St. Pölten f.
>Telekommunikation und Medien
>
>mailto: [EMAIL PROTECTED]
>  gsm  : +43 699 10605315
>  fax  : +43 3613 2311 4
>  icq  : 22308773
>  www  : www.schimek.net
>
>=
>
>_
>FAQ, list archives, and subscription info: 
>http://www.groupstudy.com/list/cisco.html
>Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

_
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

Share information about yourself, create your own public profile at 
http://profiles.msn.com.

_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Backup Interface and Routing!

2000-11-08 Thread Brian

On Wed, 8 Nov 2000, Hans Schimek wrote:

> Hi!
> 
> i configured a serial link and an ISDN link between two routers.
> the serial line is the primary line. if it fails the backup line
>  ISDN-Interface)
> takes over.
> i configured RIP -
> To prevent Routing Updates from establishing the call
> i set the ISDN-Interface as PASSIVE.
> Updates didn`t initate the call anymore.
> BUT !
> what about the routing information. if the primary fails, no routing updates
> won`t flow. so i configured static routes with a higher administrative
> distance
> -

configure the static route with a high AD like you did.  Don't make the
BRI passive, instead just use a dialer-list to define RIP as
"uninteresting".  Something like this:


interface BRI0
 ip address 192.168.1.1 255.255.255.240
 encapsulation ppp
 bandwidth 128
 isdn spid2 00055512130101
 dialer map ip 192.168.1.2 5551212
 dialer-group 1
!
router rip
 network 192.168.1.0
!
ip route 0.0.0.0 0.0.0.0 192.168.1.2 240
access-list 101 deny udp any any eq rip
access-list 101 permit ip any any
!
dialer-list 1 protocol ip list 101




> 
> IS THERE ANOTHER SOLUTION FOR THAT PROBLEM !
> 
> 
> thanx in advance
> 
> 
> 
> 
> =
> Hans Schimek
> 
> Student
> Fachhochschule St. Pölten f.
> Telekommunikation und Medien
> 
> mailto: [EMAIL PROTECTED]
>  gsm  : +43 699 10605315
>  fax  : +43 3613 2311 4
>  icq  : 22308773
>  www  : www.schimek.net
> 
> =
> 
> _
> FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
> 

---
Brian Feeny, CCNP, CCDP   [EMAIL PROTECTED]   
Network Administrator 
ShreveNet Inc. (ASN 11881)

_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: Backup Interface and Routing!

2000-11-09 Thread McCallum, Robert

Remember to add the word "broadcast" on to the end of your dialer map
statement or else the routing updates will not traverse your ISDN line.

-Original Message-
From: Brian [mailto:[EMAIL PROTECTED]]
Sent: 08 November 2000 22:19
To: Hans Schimek
Cc: [EMAIL PROTECTED]
Subject: Re: Backup Interface and Routing!


On Wed, 8 Nov 2000, Hans Schimek wrote:

> Hi!
> 
> i configured a serial link and an ISDN link between two routers.
> the serial line is the primary line. if it fails the backup line
>  ISDN-Interface)
> takes over.
> i configured RIP -
> To prevent Routing Updates from establishing the call
> i set the ISDN-Interface as PASSIVE.
> Updates didn`t initate the call anymore.
> BUT !
> what about the routing information. if the primary fails, no routing
updates
> won`t flow. so i configured static routes with a higher administrative
> distance
> -

configure the static route with a high AD like you did.  Don't make the
BRI passive, instead just use a dialer-list to define RIP as
"uninteresting".  Something like this:


interface BRI0
 ip address 192.168.1.1 255.255.255.240
 encapsulation ppp
 bandwidth 128
 isdn spid2 00055512130101
 dialer map ip 192.168.1.2 5551212
 dialer-group 1
!
router rip
 network 192.168.1.0
!
ip route 0.0.0.0 0.0.0.0 192.168.1.2 240
access-list 101 deny udp any any eq rip
access-list 101 permit ip any any
!
dialer-list 1 protocol ip list 101




> 
> IS THERE ANOTHER SOLUTION FOR THAT PROBLEM !
> 
> 
> thanx in advance
> 
> 
> 
> 
> =
> Hans Schimek
> 
> Student
> Fachhochschule St. Pölten f.
> Telekommunikation und Medien
> 
> mailto: [EMAIL PROTECTED]
>  gsm  : +43 699 10605315
>  fax  : +43 3613 2311 4
>  icq  : 22308773
>  www  : www.schimek.net
> 
> =
> 
> _
> FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
> 

---
Brian Feeny, CCNP, CCDP   [EMAIL PROTECTED]   
Network Administrator 
ShreveNet Inc. (ASN 11881)

_
FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]