From: cebuano (cebu2ccie@cox.net)
Date: Fri Dec 20 2002 - 02:46:56 GMT-3
Tim,
Have you tried version 12.0? This bug only refers to 12.1 releases.
There is NO mention of any 12.0 and newer IOS.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Tim Fletcher
Sent: Thursday, December 19, 2002 12:34 PM
To: Matthew Poole; Scott Livingston; ccielab@groupstudy.com
Subject: Re: ISDN Frustrations
At 03:56 PM 12/19/2002 +0000, Matthew Poole wrote:
>I'm not the only one having ISDN frustrations then!
>
>I just tried your scenario.
>
>1st Q - it works without dialer map statements at the Hub.
>2nd Q - as above, how far do you go, because it will also work without
>dialer-list/group on the hub??
dialer-list/group is used to initiate a call, and for idle timeout.
Since
the hub cannot make call, it would only be used with idle timeout
>3rd Q - Multilink brings up both lines with just one dialer map.
This is dependent on the ISDN switch. If a call rolls over to the 2nd B
channel, 1 number will do. Most, but not all ISDN switches do this.
>interface BRI0/0
> ip address 192.168.1.2 255.255.255.0
> encapsulation ppp
> dialer idle-timeout 20
> dialer map ip 192.168.1.1 325500
> dialer load-threshold 1 outbound
> dialer-group 1
> isdn switch-type basic-net3
> ppp multilink
>end
>
>Router#ping
>Protocol [ip]:
>Target IP address: 192.168.1.1
>Repeat count [5]:
>Datagram size [100]: 1500
>Timeout in seconds [2]:
>Extended commands [n]:
>Sweep range of sizes [n]:
>Type escape sequence to abort.
>Sending 5, 1500-byte ICMP Echos to 192.168.1.1, timeout is 2 seconds:
>.
>00:15:204029776952: %LINK-3-UPDOWN: Interface BRI0/0:1, changed state
to
>up!!
>00:15:48: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/0:1,
changed
>stat
>e to up!!
>Success rate is 80 percent (4/5), round-trip min/avg/max = 380/381/385
ms
>Router#
>00:15:227633266687: %LINK-3-UPDOWN: Interface BRI0/0:2, changed state
to up
>Router#
>00:15:225511851936: %ISDN-6-CONNECT: Interface BRI0/0:1 is now
connected to
>3255
>00
>Router#
>00:15:53: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/0:2,
changed
>stat
>e to up
>Router#
>
>HTH
>----- Original Message -----
>From: "Scott Livingston" <scottl@sprinthosting.net>
>To: <ccielab@groupstudy.com>
>Sent: Thursday, December 19, 2002 3:11 PM
>Subject: ISDN Frustrations
>
>
> > Good Morning,
> >
> > Have some big time ISDN frustrations.
> >
> > If spoke is to call hub, but the task doesn't explicitly tell me
that
> > the hub is to be able to call the spoke and there isn't any callback
> > stuff needed to complete the task then do I configure dialer map
> > statements on the hub for the spoke?
> >
> > I know I can configure a dialer map on the hub without the LDN to
make
> > it so the hub cannot call the spoke or as we know we can slap the
LDN on
> > there and give the hub that option.
> >
> > What would you do in the lab if the requirement was for the spoke to
be
> > able to call the hub, but the hub wasn't supposed to call the spoke?
> > Would you configure ANY kind of dialer map on the hub? I am afraid
that
> > if I configure the hub with dialer map statements (over configuring)
I
> > might give the proctor the perception that I don't know how to
configure
> > ISDN optimally for the requirement - lets assume the proctor wont
help
> > to clarify on this point - its all up to me.
> >
> > Also, for bringing up the second B channel.. I have seen so many
> > different examples of configuring ppp multilink on CCO and
IPEXPERTS. In
> > the lab would you configure two dialer maps on the spoke or would
you
> > use just one? I unfortunately am having problems at home with my
ISDN
> > simulator and can not give myself a definitive answer on whether I
can
> > even bring up the second B if I have only 1 dialer map statement in
the
> > spoke.
> >
> > Sorry for the long post.
> >
> > Scott
> > .
>.
.
.
This archive was generated by hypermail 2.1.4 : Fri Jan 17 2003 - 17:21:50 GMT-3