From: Brown, Patrick (NSOC-OCF} (PBrown4@chartercom.com)
Date: Sun Mar 30 2003 - 02:11:10 GMT-3
What is the other sides dialer threshold limit, because when it comes up the
bandwidth of the link will change, therefore changing the ospf cost. This
will generate a change and bring the link up and down indefinitely. Hard
code the ospf cost on both sides if you generate enough traffic to bring up
the second link. From the show dialer command it didn't look like you 2nd B
channel dialed out. Is your DNA bit set for the ospf adjacency over the BRI?
If you think it's a bug try taking it off interface and putting it back on.
Tx,
Patrick
-----Original Message-----
From: Fan Shan [mailto:shanf@public.jn.sd.cn]
Sent: Saturday, March 29, 2003 8:58 PM
To: ccielab@groupstudy.com
Subject: isdn up and down question in detail
Hello, this is my isdn config:
interface BRI0/0
ip address 133.1.35.5 255.255.255.252
encapsulation ppp
ip ospf demand-circuit
dialer map ip 133.1.35.6 name rack01r3 broadcast 62194683
dialer load-threshold 128 either
dialer-group 1
isdn switch-type basic-net3
no peer neighbor-route
no cdp enable
ppp authentication chap callin
ppp chap hostname user01
ppp multilink
router ospf 100
router-id 133.1.5.5
log-adjacency-changes
area 0 authentication message-digest
area 5 virtual-link 133.1.6.6
redistribute connected metric 100 subnets route-map connect
redistribute isis level-2 metric 100 subnets
network 133.1.5.5 0.0.0.0 area 0
network 133.1.35.5 0.0.0.0 area 0
network 133.1.56.5 0.0.0.0 area 5
network 133.1.235.5 0.0.0.0 area 0
neighbor 133.1.235.3
neighbor 133.1.235.2
router isis
redistribute ospf 100 metric 30 metric-type external
net 47.0001.0002.b910.cb60.00
This is the result of show dialer:
r5#show dialer
BRI0/0 - dialer type = ISDN
Dial String Successes Failures Last DNIS Last status
62194683 478 47 00:00:20 successful
0 incoming call(s) have been screened.
0 incoming call(s) rejected for callback.
BRI0/0:1 - dialer type = ISDN
Idle timer (120 secs), Fast idle timer (20 secs)
Wait for carrier (30 secs), Re-enable (15 secs)
Dialer state is multilink member
Dial reason: ip (s=133.1.35.5, d=224.0.0.5)
Connected to 62194683 (rack01r3)
BRI0/0:2 - dialer type = ISDN
Idle timer (120 secs), Fast idle timer (20 secs)
Wait for carrier (30 secs), Re-enable (15 secs)
Dialer state is idle
and this is routing table :
O E2 199.172.2.0/24 [110/100] via 133.1.235.2, 08:44:04, Serial0/0.1
O E2 192.1.1.0/24 [110/20] via 133.1.235.2, 08:44:04, Serial0/0.1
133.1.0.0/16 is variably subnetted, 13 subnets, 3 masks
C 133.1.235.0/24 is directly connected, Serial0/0.1
i L1 133.1.4.0/24 [115/20] via 133.1.45.4, Serial0/0.2
C 133.1.5.0/24 is directly connected, Loopback0
O 133.1.6.0/24 [110/65] via 133.1.56.6, 08:44:14, Serial0/1
O E2 133.1.1.0/24 [110/100] via 133.1.235.2, 08:44:04, Serial0/0.1
O 133.1.2.0/24 [110/65] via 133.1.235.2, 08:44:05, Serial0/0.1
O 133.1.3.0/24 [110/65] via 133.1.235.3, 08:44:05, Serial0/0.1
O IA 133.1.23.0/25 [110/74] via 133.1.235.2, 08:44:05, Serial0/0.1
[110/74] via 133.1.235.3, 08:44:05, Serial0/0.1
C 133.1.35.4/30 is directly connected, BRI0/0
C 133.1.45.0/24 is directly connected, Serial0/0.2
C 133.1.55.0/24 is directly connected, Ethernet0/0
C 133.1.56.0/24 is directly connected, Serial0/1
O IA 133.1.66.0/24 [110/65] via 133.1.56.6, 08:44:09, Serial0/1
151.100.0.0/22 is subnetted, 1 subnets
O E2 151.100.32.0 [110/100] via 133.1.235.2, 08:44:09, Serial0/0.1
150.100.0.0/24 is subnetted, 2 subnets
i L1 150.100.2.0 [115/20] via 133.1.45.4, Serial0/0.2
O E2 150.100.1.0 [110/100] via 133.1.235.2, 08:44:09, Serial0/0.1
O E2 199.172.4.0/24 [110/100] via 133.1.235.2, 08:44:09, Serial0/0
very stable,and no /32 mask ,as you can see
but when I use "debug ip ospf monitor", it shows continuous message like
this every 60 seconds:
>09:35:39: OSPF: Syncing Routing table with OSPF Database
>09:35:39: OSPF: Completed Syncing and runtime is 8 msec
>
>09:36:39: OSPF: Syncing Routing table with OSPF Database
>09:36:39: OSPF: Completed Syncing and runtime is 8 msec
>
>09:37:39: OSPF: Syncing Routing table with OSPF Database
>09:37:39: OSPF: Completed Syncing and runtime is 8 msec
This is my version:
Version 12.1(5)T9
Now I am curious if there is a bug in this version? I referenced a doc in
cco:
http://www.cisco.com/en/US/tech/tk826/tk365/technologies_tech_note09186a0080
09481b.shtml
But I didn't find any one of these reasons it lists .
This archive was generated by hypermail 2.1.4 : Sat Apr 05 2003 - 08:51:46 GMT-3