Could you post the output from a
'debug dialer events' command. Then
we can see the reason that routerB
initiates the call.
__
Thomas Crowe
Senior Systems Engineer / Senior Architect
EMC Proven Master Architect
CTS Professional Services - Atlanta
I only see the BEFORE and not AFTER. Anyway, sho
dialer on rtr-A should tell you the reason why the
call was initiated. Are you running any routing
protocols on the BRI int?
--- Original Message ---
From: Thomas Crowe
To: [EMAIL PROTECTED]
Subject: RE: ISDN -- challenge! [7:46496]
Could
From router B, I pinged a boggus destination. This triggered the bri
interface on router B. Here is the output of the debug dialer events from
Router A. You can see that router A (for no apparent reason) is trying to
call router B (even though it is router B who initiated the call.) Of course
the
No I am not running any routing protocol!
Here are my configs:
isdn1 (router A)
isdn1#show run
Building configuration...
Current configuration : 1166 bytes
!
version 12.2
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname isdn1
!
enable
This may sound daft, and I'm almost embarrassed to suggest it, but will you
humour me and remove the ip host isdn2 2065 1.1.1.1 command from
Router-isdn1.
Distant memories are haunting me.
I haven't got an ISDN simulator to play with at home, but I'm stumped too.
Gaz
Pierre-Alex Guanel
, June 14, 2002 12:19 PM
To: [EMAIL PROTECTED]
Subject: RE: ISDN -- challenge! [7:46496]
No I am not running any routing protocol!
Here are my configs:
isdn1 (router A)
isdn1#show run
Building configuration...
Current configuration : 1166 bytes
!
version 12.2
service timestamps
You have default routes pointed towards one another. You ping an address
that doesn't exist on either router. The first sends it off to the second.
The second doesn't know what to do with it so sends it on to its default
which is the first.
I do agree with your statements ... However, what is
Gaz, you are going to have to educate me on cultural issues ...
What is wrong with those numbers ?
(ip host isdn2 2065 1.1.1.1)
Pierre-Alex
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7i=46631t=46496
--
FAQ, list archives,
suggestion. If that solves it, then try to find the reason of why it behaved
as it did.
-Original Message-
From: Pierre-Alex Guanel [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 14, 2002 3:34 PM
To: [EMAIL PROTECTED]
Subject: RE: ISDN -- challenge! [7:46496]
You have default routes
Oh you had to ruin it and make me explain my half-arsed guestimate shot in
the dark theory :-)
My reasoning was based only on the fact that isdn2 is the exact hostname of
the other router, and I was just wondering whether it was causing confusion
somehow.
But... I think I changed my mind.
Can
Sorry Gaz, I did not mean to spoil to the suspense. I thought you meant the
humbers 2065 1.1.1.1 were unlucky numbers. Something like :) That is
why I asked you to explain if there was any cultural issues with my numbers
...
Anyway,I am redoing the exercise right now with Fast Ethenernet
Ok, here are the result of my tests (cummulative)
1) I gave the loopbacks unique IP addresses and tested
result: no change
2) I assigned isdn1 f0/0 to vlan11 and isdn f0/0 to vlan12
on isdn1 f0/0 ip address was 192.168.10.1/24
on isdn2 f0/0 ip address was 192.168.20.1/24
I left the default
Your dialer map statement associates the IP address 172.16.1.2 with the
telephone number 5554000. All that isdn1 knows is that it must dial 5554000
if it needs to get to 172.16.1.2.
By adding the name statements, when isdn1 receives a call from isdn2 it
associates this call with the dialer map
13 matches
Mail list logo
