From: marc van hoof (mvh@marcvanhoof.com)
Date: Mon Aug 23 2004 - 02:54:27 GMT-3
Cool - thanks for that Brian - I was going by the output of Show isdn
Activity, which seemed to be counting down.
At the moment I'm having an issue where R4 is dialing into R5, without any
ppp encaps or authentication, and unless I have the remote phone number
configured on R5 (the router being called), I get encapsulation failed
messages from a debug ip packet.
Any idea why ?
I assume it has something to do with layer 3 to layer 2 mappings on the
interface, but I thought that could be taken care of with the name xxx field
on the dialer map statement.
Current conf:
R4:
interface BRI0/0
ip address 187.2.45.4 255.255.255.0
encapsulation ppp
dialer map ip 187.2.45.5 name Rack2R5 broadcast 8358662
dialer-group 1
isdn switch-type basic-ni
isdn spid1 0835866101
isdn spid2 0835866301
end
R5:
interface BRI0/0
ip address 187.2.45.5 255.255.255.0
encapsulation ppp
dialer idle-timeout 0
dialer map ip 187.2.45.4 name Rack2R4 broadcast
isdn switch-type basic-ni
isdn spid1 0835866201
isdn spid2 0835866401
end
Output below:
Rack2R4#ping 187.2.45.5
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 187.2.45.5, timeout is 2 seconds:
*Mar 1 04:11:26.186: %LINK-3-UPDOWN: Interface BRI0/0:1, changed state to
up.
*Mar 1 04:11:27.210: %LINEPROTO-5-UPDOWN: Line protocol on Interface
BRI0/0:1, changed state to up
Rack_Time_10>5
[Resuming connection 5 to r5 ... ]
*Mar 1 04:11:26.450: %LINK-3-UPDOWN: Interface BRI0/0:1, changed state to
up
*Mar 1 04:11:27.638: %LINEPROTO-5-UPDOWN: Line protocol on Interface
BRI0/0:1, changed state to up
Rack2R5#
*Mar 1 04:11:28.278: IP: tableid=0, s=187.2.45.4 (BRI0/0), d=187.2.45.5
(BRI0/0), routed via RIB
*Mar 1 04:11:28.282: IP: s=187.2.45.4 (BRI0/0), d=187.2.45.5 (BRI0/0), len
100, rcvd 3
*Mar 1 04:11:28.282: IP: tableid=0, s=187.2.45.5 (local), d=187.2.45.4
(BRI0/0), routed via FIB
*Mar 1 04:11:28.282: IP: s=187.2.45.5 (local), d=187.2.45.4 (BRI0/0), len
100, sending
*Mar 1 04:11:28.282: IP: s=187.2.45.5 (local), d=187.2.45.4 (BRI0/0), len
100, encapsulation failed
Rack2R5#
*Mar 1 04:11:30.278: IP: tableid=0, s=187.2.45.4 (BRI0/0), d=187.2.45.5
(BRI0/0), routed via RIB
*Mar 1 04:11:30.278: IP: s=187.2.45.4 (BRI0/0), d=187.2.45.5 (BRI0/0), len
100, rcvd 3
*Mar 1 04:11:30.282: IP: tableid=0, s=187.2.45.5 (local), d=187.2.45.4
(BRI0/0), routed via FIB
*Mar 1 04:11:30.282: IP: s=187.2.45.5 (local), d=187.2.45.4 (BRI0/0), len
100, sending
*Mar 1 04:11:30.282: IP: s=187.2.45.5 (local), d=187.2.45.4 (BRI0/0), len
100, encapsulation failed
Rack2R5#
> -----Original Message-----
> From: Brian Dennis [mailto:bdennis@internetworkexpert.com]
> Sent: Monday, 23 August 2004 3:49 PM
> To: marc van hoof; ccielab@groupstudy.com
> Subject: RE: isdn timers and dialer maps
>
> Outside of dialer watch and dialer persistence, without the dialer-group
> command the router will drop the call after the idle-timeout expires
> (default 120 seconds).
>
> As far as using dialer idle-timeout 0 command, have you tested it to see
> if it ever drops? Look at the output of the show dialer command below:
>
> Rack1R4#sho dialer
>
> BRI0/0 - dialer type = ISDN
>
> Dial String Successes Failures Last DNIS Last status
> 0 incoming call(s) have been screened.
> 0 incoming call(s) rejected for callback.
>
> BRI0/0:1 - dialer type = ISDN
> Idle timer (never), Fast idle timer (20 secs)
> Wait for carrier (30 secs), Re-enable (15 secs)
> Dialer state is data link layer up
> Dial reason: ip (s=183.1.45.4, d=183.1.45.5)
> Interface bound to profile Di1
> Time until disconnect never <-----------------
> Current call connected 00:00:53
> Connected to 5272015 (5272015)
>
> Notice that the time until disconnect is "never".
>
> Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)
> bdennis@internetworkexpert.com
> 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@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> marc van hoof
> Sent: Sunday, August 22, 2004 10:30 PM
> To: ccielab@groupstudy.com
> Subject: isdn timers and dialer maps
>
> If dialer idle-timeout is set to 0, the interface sets the idle timer to
> the
> max 2147483 and starts counting down. It seems like dialer idle-timeout
> 0
> means doesn't mean it will never disconnect, it just means "make the
> timer
> so long that the chance of not getting interesting traffic is next to
> nothing"
>
>
>
> If I apply this to an interface which has no dialer-group command on it,
> and
> hence the interface doesn't know what is interesting traffic and what
> isn't,
> does that mean that one day the link WILL disconnect ?
>
>
>
> Thanks,
>
> -marc.
>
> _______________________________________________________________________
> Please help support GroupStudy by purchasing your study materials from:
> http://shop.groupstudy.com
>
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Fri Sep 03 2004 - 07:02:47 GMT-3