From: Logan, Harold (loganh@mccfl.edu)
Date: Tue Nov 12 2002 - 14:00:22 GMT-3
If it works the same as the name option in the dialer map command, it simply names the isdn session. Since some ISDN switches append an additional digit when calls are dialed, you can have both B channels hogged up by a simple ping request:
R1----------ISDN-----------R2
5551234 5554321
R1 dials R2 using 5554321
R2 sees an incoming call from 95551234 (The 9 is appended by the isdn switch)
R2 receives data from R1, and wants to send a reply. It checks to see if it has an ISDN call set up with R1, but since R2's dialer maps are pointing to 5551234, it determines that it isn't connected to R1.
R2 dials R1 using its second B channel.
This goes on pretty much ad infinitum... as long as R1 and R2 are sending data to each other, both B channels are going to stay up.
The way to fix this is to use PPP authentication, and use the name option in your dialer maps (or dialer remote-name in your profiles). The result is that the router tracks its incoming calls by the hostname of the calling router, not by its LDN. R2 will then correctly determine that it's already connected to R1, and the two routers will exchange data on 1 B channel.
Hal Logan CCAI, CCDP, CCNP: Voice
Network Specialist / Adjunct Faculty
Computing & Engineering Technology
Manatee Community College
> -----Original Message-----
> From: Nathan Chessin [mailto:nchessin@cisco.com]
> Sent: Tuesday, November 12, 2002 12:56 AM
> To: ccielab@groupstudy.com
> Subject: Dialer Profiles - remote-name
>
>
> Hi All,
>
> What is the reasoning for having a remote-name X with dialer
> profiles? I am
> doing chap authentication, and no matter what I out as a
> string in these, it
> seems to work.
>
>
> Nate
This archive was generated by hypermail 2.1.4 : Tue Dec 03 2002 - 07:22:57 GMT-3