From: André Bersvendsen (an-bersv@xxxxxxxxx)
Date: Sun Apr 07 2002 - 06:04:54 GMT-3
Hi,
The only thing that you do not have configured on R3 is 'dialer-group'.
You have only configured that on R5. If you for a minute forget the
encapsulation failed problem, and assume that the packet is forwarded,
then I think one problem you will get without 'dialer-group' is that R3
will hang up after the default idle timer is expired.
But on your configuration the "encapsulation failed" problem must be
solved before the above scenario is showing.
It might be that you need the 'dialer-group' to get it to forward the IP
packet. But for me that is not logical because I do not think that
'dialer-group' will deny/permit traffic to be sent over the line. It is
only for bringing up the line and to reset the idle timer when
interesting traffic is sent.
Try to configure 'dialer-group'. Then you have solved one of the
problems. It might solve both.
Best Regards,
Andri Bersvendsen
-----Original Message-----
From: Richard Furda [mailto:riso@furda.net]
Sent: 6. april 2002 10:24
To: Andri Bersvendsen
Subject: RE: 1 BRI and 2 routers
Hi,
thanks for your speedy reply. Indeed it works. Now I seem to have
some odd problem, when the peers are unable to communicate on IP layer.
Here is some relevant info:
R3:
interface BRI0
ip address 10.10.10.3 255.255.255.0
no ip directed-broadcast
encapsulation ppp
isdn switch-type basic-net3
isdn answer1 44642773
!
R5:
interface BRI0
ip address 10.10.10.5 255.255.255.0
encapsulation ppp
dialer string 44642773
dialer-group 1
isdn switch-type basic-net3
isdn answer1 44642771
ppp authentication chap callin
When 'ping 10.10.10.3' is issued on R5, R5 initiates a call and
successfully authententicates.
R5#sh debug
Generic IP:
IP packet debugging is on
PPP:
PPP authentication debugging is on
R5#
R5#ping 10.10.10.3
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.10.10.3, timeout is 2 seconds:
01:07:49: IP: s=10.10.10.5 (local), d=10.10.10.3 (BRI0), len 100,
sending
01:07:49: IP: s=10.10.10.5 (local), d=10.10.10.3 (BRI0), len 100,
encapsulation failed.
01:07:50: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0, TEI 84 changed to
up
01:07:51: %LINK-3-UPDOWN: Interface BRI0:1, changed state to up
01:07:51: BR0:1 PPP: Treating connection as a callout
01:07:51: IP: s=10.10.10.5 (local), d=10.10.10.3 (BRI0), len 100,
sending.
01:07:52: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0:1,
changed state to up
01:07:53: IP: s=10.10.10.5 (local), d=10.10.10.3 (BRI0), len 100,
sending.
01:07:55: IP: s=10.10.10.5 (local), d=10.10.10.3 (BRI0), len 100,
sending.
01:07:57: %ISDN-6-CONNECT: Interface BRI0:1 is now connected to 44642773
01:07:57: IP: s=10.10.10.5 (local), d=10.10.10.3 (BRI0), len 100,
sending.
Success rate is 0 percent (0/5)
R5#
After 2 packets, r5 seems to sending out IP packets out of the BRI0
interface. R3, on the other hand seems to fail, with 'encap failed' as
observed below.
R3#sh debug
Generic IP:
IP packet debugging is on
PPP:
PPP authentication debugging is on
R3#
01:07:15: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0, TEI 85 changed to
up
01:07:16: %LINK-3-UPDOWN: Interface BRI0:2, changed state to up
01:07:16: %ISDN-6-CONNECT: Interface BRI0:2 is now connected to
0244642771
01:07:16: BR0:2 PPP: Treating connection as a callin
01:07:17: IP: s=10.10.10.5 (BRI0), d=10.10.10.3 (BRI0), len 100, rcvd 3
01:07:17: IP: s=10.10.10.3 (local), d=10.10.10.5 (BRI0), len 100,
sending
01:07:17: IP: s=10.10.10.3 (local), d=10.10.10.5 (BRI0), len 100,
encapsulation failed
01:07:17: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0:2,
changed state to up
01:07:19: IP: s=10.10.10.5 (BRI0), d=10.10.10.3 (BRI0), len 100, rcvd 3
01:07:19: IP: s=10.10.10.3 (local), d=10.10.10.5 (BRI0), len 100,
sending
01:07:19: IP: s=10.10.10.3 (local), d=10.10.10.5 (BRI0), len 100,
encapsulation failed
01:07:21: IP: s=10.10.10.5 (BRI0), d=10.10.10.3 (BRI0), len 100, rcvd 3
01:07:21: IP: s=10.10.10.3 (local), d=10.10.10.5 (BRI0), len 100,
sending
01:07:21: IP: s=10.10.10.3 (local), d=10.10.10.5 (BRI0), len 100,
encapsulation failed
01:07:22: %ISDN-6-CONNECT: Interface BRI0:2 is now connected to
0244642771 0244642771
01:07:23: IP: s=10.10.10.5 (BRI0), d=10.10.10.3 (BRI0), len 100, rcvd 3
01:07:23: IP: s=10.10.10.3 (local), d=10.10.10.5 (BRI0), len 100,
sending
01:07:23: IP: s=10.10.10.3 (local), d=10.10.10.5 (BRI0), len 100,
encapsulation failed
Why would R3 fail, when it has ppp encapsulated set?
Thanks,
On Sat, 6 Apr 2002, [iso-8859-1] Andri Bersvendsen wrote:
> Hi Richard,
>
>
> I have no problem when I use more than one BRI interface on an ISDN
> line.
> It is possible to call from one router to another on the same line.
>
> You have to assign witch number the router shall answer to. It is as
you
> mention the command 'isdn answer1 <num>' you must use.
>
> You can however get a problem if you are configuring ISDN callback
> (based on the telephone number). The problem is that RouterA is seting
> up a call to RouterB and the ISDN switch will give RouterA one
B-channel
> and RouterB the other (not used but signaled to be used when call is
set
> up). RouterB reject the call. Then RouterB want to call back to
RouterA.
> In this situation the switch might not be ready to handle this. - The
> B-channels are not available yet. After some retries you will normally
> get the expected callback.
> (Observe this with debug isdn q931)
>
>
> Regards,
> Andri Bersvendsen
>
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
Of
> Richard Furda
> Sent: 6. april 2002 09:14
> To: CCIE Lab
> Subject: 1 BRI and 2 routers
>
> Hello,
>
> Has anyone successfully used 1 BRI line with 2 routers?
> More preciselly, calling one router (on 1 B channel) from other
> router (on the second B channel)? I've been assiged 3 phone numbers
> for this line. Almost identical output (healthy call setup) from
> 'debug isdn q931' is shown on both routers when one of the 3 numbers
is
> called. I haven't got deep into the ISDN dialer configs yet, just
> wondering before i start. I believe 'isdn answer1 <num>' is the answer
> to my question?
>
> Thanks,
> Rich
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:57:58 GMT-3