GroupStudy.com GroupStudy.com - A virtual community of network engineers
 Home  BookStore  StudyNotes  Links  Archives  StudyRooms  HelpWanted  Discounts  Login
RE: RIP triggered posted 10/26/2005
[Chronological Index] [Thread Index] [Top] [Date Prev][Date Next] [Thread Prev][Thread Next]


Are you 100% sure that the BRI actually goes down from a routing
protocol perspective?  I would recommend that you lab it up.

Rack2R4#sho run int br0/0
Building configuration...

Current configuration : 229 bytes
!
interface BRI0/0
 ip address 10.1.1.4 255.255.255.0
 ip rip triggered
 encapsulation ppp
 dialer idle-timeout 60
 dialer string 5272025
 dialer-group 1
 isdn switch-type basic-ni
 isdn spid1 5272024
end

Rack2R4#sho int br0/0   
BRI0/0 is up, line protocol is up (spoofing)
  Hardware is PQUICC BRI with U interface
  Internet address is 10.1.1.4/24
  MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec, 
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation PPP, loopback not set
  Last input 00:00:04, output never, output hang never
  Last clearing of "show interface" counters 00:13:53
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
  Queueing strategy: weighted fair
  Output queue: 0/1000/64/0 (size/max total/threshold/drops) 
     Conversations  0/1/16 (active/max active/max total)
     Reserved Conversations 0/0 (allocated/max allocated)
     Available Bandwidth 48 kilobits/sec
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     95 packets input, 433 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     94 packets output, 423 bytes, 0 underruns
     0 output errors, 0 collisions, 2 interface resets
     0 output buffer failures, 0 output buffers swapped out
     8 carrier transitions
Rack2R4#
Rack2R4#sho ip rout rip
     10.0.0.0/24 is subnetted, 3 subnets
R       10.5.5.0 [120/1] via 10.1.1.5, 00:08:24, BRI0/0
Rack2R4#
Rack2R4#sho ip int brie bri0/0
Interface        IP-Address      OK? Method Status       Protocol
BRI0/0           10.1.1.4        YES manual up           up      
Rack2R4#




As you can see here the router doesn't call after the BRI goes down.


Rack2R4#sho clock
*01:49:05.201 UTC Mon Mar 1 1993
Rack2R4#ping 10.1.1.5

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.1.5, timeout is 2 seconds:
..
%LINK-3-UPDOWN: Interface BRI0/0:1, changed state to up.!!
Success rate is 40 percent (2/5), round-trip min/avg/max = 32/32/32 ms
Rack2R4#
%LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/0:1, changed state
to up
%ISDN-6-CONNECT: Interface BRI0/0:1 is now connected to 5272025 
Rack2R4#
Rack2R4#sho clock    
*01:49:45.479 UTC Mon Mar 1 1993
Rack2R4#sho clock
*01:50:05.640 UTC Mon Mar 1 1993
Rack2R4#sho isd act
------------------------------------------------------------------------
--------
                                ISDN ACTIVE CALLS
------------------------------------------------------------------------
--------
Call    Calling      Called       Remote  Seconds Seconds Seconds
Charges
Type    Number       Number       Name    Used    Left    Idle
Units/Currency
------------------------------------------------------------------------
--------
Out   ---N/A---     5272025                    55       5      54      0

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

Rack2R4#
%ISDN-6-DISCONNECT: Interface BRI0/0:1  disconnected from 5272025 , call
lasted 61 seconds
%LINK-3-UPDOWN: Interface BRI0/0:1, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/0:1, changed state
to down
Rack2R4#
Rack2R4#sho clock  
*01:51:19.257 UTC Mon Mar 1 1993
Rack2R4#sho ip rout rip
     10.0.0.0/24 is subnetted, 3 subnets
R       10.5.5.0 [120/1] via 10.1.1.5, 00:23:19, BRI0/0
Rack2R4#sho clock
*01:57:45.422 UTC Mon Mar 1 1993
Rack2R4#
Rack2R4#sho ip rout rip
     10.0.0.0/24 is subnetted, 3 subnets
R       10.5.5.0 [120/1] via 10.1.1.5, 00:32:14, BRI0/0
Rack2R4#

HTH,

Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)
bdennis@xxxxxxxxxxxxxxxxxxxxxx 
 
Internetwork Expert, Inc. 
http://www.InternetworkExpert.com 
Toll Free: 877-224-8987 
Direct: 775-745-6404 (Outside the US and Canada) 
 

-----Original Message-----
From: nobody@xxxxxxxxxxxxxx [mailto:nobody@xxxxxxxxxxxxxx] On Behalf Of
ronald.kaduwa@xxxxxxx
Sent: Tuesday, October 25, 2005 7:39 PM
To: ccielab@xxxxxxxxxxxxxx
Subject: RIP triggered

Hi,



I don't see how "ip rip triggered" is the solution to prevent an ISDN
link from constantly flapping, given that RIP is running across it.
Because when the link goes down, this constitutes a change in topology
and therefore a triggered update. This is the result I keep getting, so
how do you prevent it if snapshot routing is not an option? Do you
exclude RIP from the interesting traffic? But then that would mean no
updates unless the link is up...quoi faire?



Thanks,



Roni.

_______________________________________________________________________
Subscription information may be found at: 
http://www.groupstudy.com/list/CCIELab.html