From: enginedrive2002 (enginedrive2002@yahoo.ca)
Date: Tue Jan 07 2003 - 22:14:38 GMT-3
I guess in your first scenario, it's pingable because the called router use
the dial string to bring up the second B channel. At that time, both B
channels work like a simplex link. The reason called router bring up second
B channel to call the other end, it's because it cannot match the ICMP echo
reply destination IP address with the existing call. For the same reason, in
your second scenario, one router without dial string configuration, it
cannot match the destination IP address with the existing call and doesn't
have a string to call, the PING fail.
E.D.
----- Original Message -----
From: "Tony Schaffran" <tschaffran@cconlinelabs.com>
To: "Jeffery S Kimes" <kimes@us.ibm.com>
Cc: <ccielab@groupstudy.com>
Sent: January 7, 2003 4:44 PM
Subject: Re: ISDN issue
> Everything is the way it should be. I have interesting traffic specified
> and everything works just the way it should with that config.
>
> My issue is, if I remove the dialer string on the called router, the call
> will complete, but I will not be able to ping.
>
> On the called router, the dialer string should be irrelevant and should
not
> be needed. But, for some reason, it is needed. This is what I am trying
to
> figure out.
>
>
>
> Tony Schaffran
> Network Analyst
> CCNP, CCNA, CCDA,
> NNCSS, NNCDS, CNE, MCSE
>
> www.cconlinelabs.com
> "Your #1 choice for Cisco rack rentals."
>
>
> ----- Original Message -----
> From: "Jeffery S Kimes" <kimes@us.ibm.com>
> To: "Tony Schaffran" <tschaffran@cconlinelabs.com>
> Cc: <ccielab@groupstudy.com>; <nobody@groupstudy.com>
> Sent: Tuesday, January 07, 2003 12:31 PM
> Subject: Re: ISDN issue
>
>
> >
> >
> >
> >
> > This maybe a stupid question, but I see that you have dialer-groups
> set-up,
> > but I don't see dialer lists???
> >
> > Also, you should be able to debug isdn q921 or q931 and determine
whether
> > or not a connection is being established. Use a sh isdn stat to
determine
> > if TEI's were received...
> >
> > Regards,
> >
> > Jeff Kimes
> > Senior I/T Specialist
> > I/T Consulting & Implementation Services
> > Direct (858)587-5154
> > Tie Line 339-5154
> > Cell (909)551-3578
> > kimes@us.ibm.com
> >
> >
> >
> >
> > "Tony Schaffran"
> > <tschaffran@cconli To:
> <ccielab@groupstudy.com>
> > nelabs.com> cc:
> > Sent by: Subject: ISDN issue
> > nobody@groupstudy.
> > com
> >
> >
> > 01/07/2003 01:37
> > PM
> > Please respond to
> > "Tony Schaffran"
> >
> >
> >
> >
> >
> >
> > Is ther a problem with my ISDN switch, or am I just doing something
wrong?
> >
> > This is my basic isdn configuration:
> >
> > R6
> > interface BRI1/0
> > ip address 133.10.80.1 255.255.255.0
> > encapsulation ppp
> > dialer string 5555001
> > dialer-group 1
> > isdn switch-type basic-ni
> > isdn spid1 50355560010101 5556001
> > isdn spid2 50355560020101 5556002
> >
> > R5
> > interface BRI0
> > ip address 133.10.80.2 255.255.255.0
> > encapsulation ppp
> > dialer string 5556001
> > dialer-group 1
> > isdn switch-type basic-ni
> > isdn spid1 50355550010101 5555001
> > isdn spid2 50355550020101 5555002
> >
> > Pretty simple, right? I have ping connectivity from either side to the
> > other.
> > If I remove the dialer string from one side or the other, ISDN seems to
> > come
> > up normally, but I can no longer ping. Is this normal?
> >
> > Thanks
> > .
> .
This archive was generated by hypermail 2.1.4 : Sat Feb 01 2003 - 07:33:45 GMT-3