From: Brian McGahan (bmcgahan@internetworkexpert.com)
Date: Fri Mar 11 2005 - 14:15:53 GMT-3
Simon,
The problem has to do with layer 2 to layer 3 resolution. Some
IOS versions have problems mapping remote layer 3 addresses to dialer
maps that do not have dialer strings applied to them. What you can do
is add the dialer string on to the end of the dialer map, then either
remove the dialer-list from the interface or configure a dialer-list
that says "dialer-list 1 protocol ip deny".
HTH,
Brian McGahan, CCIE #8593
bmcgahan@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987 x 705
Outside US: 775-826-4344 x 705
24/7 Support: http://forum.internetworkexpert.com
Live Chat: http://www.internetworkexpert.com/chat/
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
Of
> simon hart
> Sent: Friday, March 11, 2005 11:02 AM
> To: Group Study
> Subject: ISDN problem
>
> Hi all,
>
> I am having a bit of a nightmare with some simple ISDN configuration:
I
> am
> trying to establish a connection between two routers R4 and R5. R5
should
> not be able to initiate a call - only R4. I am using legacy DDR,
configs
> below
>
> Frame_R4#
> !
> interface BRI0
> ip address 187.1.45.4 255.255.255.0
> encapsulation ppp
> dialer map ip 187.1.45.5 name Rack1R5 broadcast 2222
> dialer-group 1
> isdn switch-type basic-ni
> isdn spid1 1211
> end
> !
> dialer-list 1 protocol ip permit
>
>
>
> Rack1R5#
> !
> interface BRI0/0
> ip address 187.1.45.5 255.255.255.0
> encapsulation ppp
> dialer idle-timeout 0
> dialer map ip 187.1.45.4 name Rack1R5 broadcast
> isdn switch-type basic-ni
> isdn spid1 2122
> end
>
>
> If I ping from Frame_R4 then the ISDN line is brought up but no
response
> to
> the pings. If I debug IP packet on R5 I notice that I have an
> encapsulation
> failure:
> Rack1R5#
> *Mar 1 07:52:46.460: IP: s=187.1.45.4 (BRI0/0), d=187.1.45.5
(BRI0/0),
> len
> 100, rcvd 3
> *Mar 1 07:52:46.460: IP: s=187.1.45.5 (local), d=187.1.45.4 (BRI0/0),
len
> 100, sending
> *Mar 1 07:52:46.460: IP: s=187.1.45.5 (local), d=187.1.45.4 (BRI0/0),
len
> 100, encapsulation failed
> Rack1R5#
> *Mar 1 07:52:48.459: IP: s=187.1.45.4 (BRI0/0), d=187.1.45.5
(BRI0/0),
> len
> 100, rcvd 3
> *Mar 1 07:52:48.459: IP: s=187.1.45.5 (local), d=187.1.45.4 (BRI0/0),
len
> 100, sending
> *Mar 1 07:52:48.463: IP: s=187.1.45.5 (local), d=187.1.45.4 (BRI0/0),
len
> 100, encapsulation failed
>
> As you can see it is showing an encapsulation failure, however the map
> looks
> fine and the config is exactly as dictated within the solution guide
of
> the
> Internetwork expert solution guide
>
> Any comments most welcome
>
> S.
>
> --
> No virus found in this outgoing message.
> Checked by AVG Anti-Virus.
> Version: 7.0.308 / Virus Database: 266.7.1 - Release Date: 09/03/2005
>
>
This archive was generated by hypermail 2.1.4 : Sun Apr 03 2005 - 17:56:44 GMT-3