From: Steven Weber (itweber@xxxxxxxxxxxxx)
Date: Sun Mar 04 2001 - 11:53:00 GMT-3
I was thinking abou this some more and I realized that just allowing ping
througj the access-list is not sufficient because this will not let routing
updates through between them. Rather you must permit ospf updates through as
well and use ip ospf demand circuit to make sure it doesn't keep the line up. O
r
maybe I don't have to define ospf in the access-list because it will update the
other side on the ping because interesting traffic brings the line up but other
traffic can go through after the line has been brought up. However if there is
a
topology change isdn won't let it through because ospf isn't interesting
and it will have to wait for a ping before the update is sent. Anyway, I think
that ospf would be required in the access-list in order to make sure updates go
through when they should be. Can someone please comment on my trend of
thought.
Thanks,
Steve
P.S. Here are my configs, notice I have not yet added ospf to my access
list.
r5#
interface BRI0
ip address 172.168.65.2
255.255.255.0
encapsulation ppp
no logging event
subif-link-status
dialer string 384020
dialer-group
1
!
router ospf 1
redistribute igrp 1 metric-type 1
subnets
network 137.20.20.0 0.0.0.255 area 0
network
172.168.100.0 0.0.0.255 area 10
network 172.168.65.0 0.0.0.255 area
10
distribute-list 4 out igrp 1
area 10 virtual-link
172.168.30.97
!
router igrp 1
redistribute ospf 1 metric 1544 10
255 1 1500
passive-interface Serial0.1
network
172.168.0.0
distribute-list 3 out ospf 1
distribute-list 4 in
Serial0.2
!
no ip classless
ip route 0.0.0.0 0.0.0.0 172.168.65.1
119
access-list 1 permit 172.168.100.0 0.0.0.255
access-list 1 permit
172.168.30.0 0.0.0.255
access-list 1 permit 172.168.60.0
0.0.0.255
access-list 1 permit 172.168.65.0 0.0.0.255
access-list 2 permit
any
access-list 3 deny 172.168.40.0
access-list 3
deny 172.168.200.0
access-list 3 permit any
access-list 4
permit 172.168.40.0
access-list 4 permit 172.168.200.0
access-list 100
permit icmp any any echo
route-map ROUTES permit 20
match ip address
2
!
dialer-list 1 protocol ip list 100
!
r6#
interface BRI0
ip address 172.168.65.1
255.255.255.0
encapsulation ppp
no logging event
subif-link-status
dialer string 384000
dialer-group
1
!
router ospf 1
network 172.168.100.0 0.0.0.255 area
10
network 172.168.60.0 0.0.0.255 area 10
network 172.168.65.0
0.0.0.255 area 10
!
no ip classless
ip route 0.0.0.0 0.0.0.0
172.168.65.2 119
access-list 100 permit icmp any any echo
dialer-list 1
protocol ip list 100
!
----- Original Message -----
From: Troy
Edington
To: CCIE GROUP ;Steven
Weber
Sent: 3/4/01 12:31:38 AM
Subject: RE: isdn floating
statics...(ccbootcamp lab #5a)
Can you post your relevant configs
Troy
-----Original Message-----
From: Steven Weber [mailto:itweber@earthlink.net ]
Sent: Saturday, March 03, 2001 9:20 PM
To: CCIE GROUP
Subject: isdn floating statics...(ccbootcamp lab #5a)
Can somebody please explain to me why I can only get the ping to work when
I set up a floating static in one direction at a time. I shut the
frame
switch
on one side and tried a ping and it worked, the ISDN line came up. When
I
went
to the other side to try it it didn't work so I figured that either I
configured
it wrong or it sees the frame switch so maybe it was spoofing it or
something. I
went to the frame switch shut down the other end and it still didn't
work.I
then
opened up both ports on the frame switch to make sure the other side
can
ping
and that worked as well, went back to the frame-switch and shut down
the
other
side and it was able to ping using the ISDN line. I went back to the
first
side
again and it was giving me the same problems I had in the first place.
I
hope I
explained well. I don't understand why this isn't working. Can
somebody
please
explain.
Thanks
--- Steven Weber
--- EarthLink: It's your Internet.
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:29:19 GMT-3