From: Dillon Yang (gzdillon@hotmail.com)
Date: Tue Mar 22 2005 - 13:23:32 GMT-3
Thanks, Brian:
But the first question?
Why the R1 can respond without a dial string?
TIA
dillon
----- Original Message -----
From: "Brian Dennis" <bdennis@internetworkexpert.com>
To: "Dillon Yang" <gzdillon@hotmail.com>; "Scott Morris" <swm@emanon.com>
Cc: "Group Study" <ccielab@groupstudy.com>
Sent: Tuesday, March 22, 2005 5:21 AM
Subject: RE: ISDN problem (ppp multilink???)
> Dillon,
>
> <Quote>
> And I can not understand why this message is brought up by "ppp
> multilink".
>
> *Mar 1 00:01:40: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> Virtual-Access2, changed state to up
> </Quote>
>
> Just do a "show ppp multilink" when the interface is connected to the
> remote side and it will answer your question.
>
> 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
> Dillon Yang
> Sent: Monday, March 21, 2005 2:45 AM
> To: Scott Morris
> Cc: Group Study
> Subject: Re: ISDN problem (ppp multilink???)
>
> Hi, scott:
>
> I met the same situation in one-way calling, but I happened to resolve
> it by "ppp multilink" and did not know why, maybe you can clarify it?
> And I can not understand why this message is brought up by "ppp
> multilink".
>
> *Mar 1 00:01:40: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> Virtual-Access2, changed state to up
>
> TIA
> dillon
>
>
> ====================== Connected without traffic =================
> hostname r1
> interface BRI0/0
> ip address 172.16.12.1 255.255.255.0
> encapsulation ppp
> dialer idle-timeout 180
> dialer map ip 172.16.12.2 name r2 broadcast
> dialer load-threshold 10 outbound
> dialer-group 3
> isdn switch-type basic-ni
> isdn spid1 0555011101
> isdn spid2 0555033301
> ppp multilink
> !
> hostname r2
> !
> interface BRI0/0
> ip address 172.16.12.2 255.255.255.0
> encapsulation ppp
> dialer idle-timeout 180
> dialer map ip 172.16.12.1 name r1 broadcast 5550111
> dialer map ip 172.16.12.1 name r1 broadcast 5550333
> dialer load-threshold 10 outbound
> dialer-group 3
> isdn switch-type basic-ni
> isdn spid1 0555022201 5550222
> isdn spid2 0555044401 5550444
> end
> *Mar 1 00:31:27: %ISDN-6-CONNECT: Interface BRI0/0:1 is now connected
> to 5550111 r1.
> Success rate is 0 percent (0/5)
> r2#p 172.16.12.1
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 172.16.12.1, timeout is 2 seconds:
> .....
> Success rate is 0 percent (0/5)
>
>
>
>
>
> =========================Connected with
> traffic==============================
> r1#s run int BRI0/0
> Building configuration...
>
> Current configuration : 291 bytes
> !
> interface BRI0/0
> ip address 172.16.12.1 255.255.255.0
> encapsulation ppp
> dialer idle-timeout 180
> dialer map ip 172.16.12.2 name r2 broadcast
> dialer load-threshold 10 outbound
> dialer-group 3
> isdn switch-type basic-ni
> isdn spid1 0555011101
> isdn spid2 0555033301
> ppp multilink
> end
> Current configuration : 298 bytes
> !
> interface BRI0/0
> ip address 172.16.12.2 255.255.255.0
> encapsulation ppp
> dialer idle-timeout 180
> dialer map ip 172.16.12.1 name r1 broadcast 5550111
> dialer load-threshold 10 outbound
> dialer-group 3
> isdn switch-type basic-ni
> isdn spid1 0555022201
> isdn spid2 0555044401
> ppp multilink
> end
>
> r2#p 172.16.12.1
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 172.16.12.1, timeout is 2 seconds:
>
> *Mar 1 00:01:55: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/0, TEI 82
> changed to up
> *Mar 1 00:01:55: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/0, TEI 83
> changed to up.!!!!
> Success rate is 80 percent (4/5), round-trip min/avg/max = 32/32/32 ms
> r2#
> *Mar 1 00:01:56: %LINK-3-UPDOWN: Interface BRI0/0:1, changed state to
> up
> *Mar 1 00:01:56: %LINK-3-UPDOWN: Interface Virtual-Access2, changed
> state to up
> r2#
> *Mar 1 00:01:57: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> BRI0/0:1, changed state to up
> *Mar 1 00:01:57: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> Virtual-Access2, changed state to up
> r2#p 172.16.12.1
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 172.16.12.1, timeout is 2 seconds:
> !!!!!
> Success rate is 100 percent (5/5), round-trip min/avg/max = 32/32/32 ms
> r2#
> *Mar 1 00:02:02: %ISDN-6-CONNECT: Interface BRI0/0:1 is now connected
> to 5550111 r1
> r2#cle Interface BRI0/0
>
> === I cleared the link !!! ====
>
> r2#
> r2#
> *Mar 1 00:02:18: %ISDN-6-DISCONNECT: Interface BRI0/0:1 disconnected
> from 5550111 r1, call lasted 21 seconds
> *Mar 1 00:02:18: %LINK-3-UPDOWN: Interface BRI0/0:1, changed state to
> down
> *Mar 1 00:02:18: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/0, TEI
> 82 changed to down
> *Mar 1 00:02:18: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/0, TEI
> 83 changed to down
> *Mar 1 00:02:18: %LINK-3-UPDOWN: Interface Virtual-Access2, changed
> state to down
> r2#
> *Mar 1 00:02:18: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/0, TEI 82
> changed to up
> *Mar 1 00:02:18: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/0, TEI 83
> changed to up
> r2#
> *Mar 1 00:02:19: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> BRI0/0:1, changed state to down
> *Mar 1 00:02:19: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> Virtual-Access2, changed state to down
> r2#conf t
> Enter configuration commands, one per line. End with CNTL/Z.
> r2(config)#Interface BRI0/0
> r2(config-if)#no ppp mul
>
> === I removed the command !!! ====
>
> r2(config-if)#end
> r2#
> *Mar 1 00:02:36: %SYS-5-CONFIG_I: Configured from console by console
> r2#p 172.16.12.1
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 172.16.12.1, timeout is 2 seconds:
> .
> *Mar 1 00:03:15: %LINK-3-UPDOWN: Interface BRI0/0:1, changed state to
> up
> *Mar 1 00:03:16: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> BRI0/0:1, changed state to up...
> *Mar 1 00:03:21: %ISDN-6-CONNECT: Interface BRI0/0:1 is now connected
> to 5550111 r1.
> Success rate is 0 percent (0/5)
> r2#p 172.16.12.1
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 172.16.12.1, timeout is 2 seconds:
> .....
> Success rate is 0 percent (0/5)
>
> =====================================================
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> ----- Original Message -----
> From: "Scott Morris" <swm@emanon.com>
> To: "'Roy Dempsey'" <roy.dempsey@gmail.com>; <ccielab@groupstudy.com>
> Sent: Saturday, March 12, 2005 3:15 AM
> Subject: RE: ISDN problem
>
>
> > Since you are not doing any authentication, this is exactly correct.
> >
> > When you ping from R4, the line will go up, because R4 knows where to
> send
> > to and where to go. So the packet goes to R5.
> >
> > R5 looks at the incoming ICMP and tries to respond, but needs to look
> at
> > where to send it. It sees a dialer map, but that gives noplace to go.
> >
> > If you were running CHAP, then the name part would actually correlate
> (see
> > "show dialer" output). Until that time though, you'll need a phone
> number
> > to give it some way to say "Oh, I'm already connected to that guy!"
> and send
> > the packet back.
> >
> > HTH,
> >
> > Scott
> >
> >
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
> Of Roy
> > Dempsey
> > Sent: Friday, March 11, 2005 12:16 PM
> > To: ccielab@groupstudy.com
> > Subject: Re: ISDN problem
> >
> > Hi Simon,
> >
> > Had this EXACT problem yesterday. This should work, according to my
> > understanding. However, the only way I could get it to work is to add
> the
> > dialer string to the R5 router, thus breaking the requirement you
> mention.
> >
> > However, if you then go on and configure PPP encapsulation and
> > authentication on the interface, you can remove the dialer string.
> >
> > I think its related to R5 not knowing what to do with the traffic,
> even
> > though there is only one configured interface and the debug shows it
> being
> > sent to this Interface. Once you configure authentication, the router
> can
> > map the traffic to the interface using the hostname of the calling
> router
> >
> > On Fri, 11 Mar 2005 17:02:28 -0000, simon hart
> <simon.hart@btinternet.com>
> > wrote:
> > > 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
> > >
> > >
> ______________________________________________________________________
> > > _ Subscription information may be found at:
> > > http://www.groupstudy.com/list/CCIELab.html
> >
> >
> _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
> >
> >
> _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sun Apr 03 2005 - 17:56:50 GMT-3