RE: Async interface triggered by 224.0.0.5 using ip ospf demand circuit

From: McNutt, Steve (Steve.McNutt@xxxxxxxxxxx)
Date: Fri Oct 27 2000 - 12:44:35 GMT-3


   
1. where is your ospf router definition?
2. for async interfaces, I use dialer profiles with ospf demmand circuit.
I do this because it seems like async interfaces don't want to spoof
properly and when the line drops it triggers a LSA which in turn, brings the
line back up.
3. since Ospf demmand circuits are triggerd by LSA's a good trouleshooting
procedure is to do a debug LSA-generation to see the timing of the LSA in
relationship to other events (like primary link failure), and then find the
LSA that was created in the OSPF database. I get good results with this.
Often I find another routing protocol is feeding back or advertising
connected networks into OSPF, causing OSPF to generate type 5's for the DDR
link.

HTH,
-steve

-----Original Message-----
From: khalid siddiq [mailto:khalidsi@hotmail.com]
Sent: Friday, October 27, 2000 11:02 AM
To: ccielab@groupstudy.com
Subject: Async interface triggered by 224.0.0.5 using ip ospf demand
circuit

hi,
I have some problem with the ip ospf demand circuit, async interface is
triggered by the hello packet of ospf.
clearify someone what i am missing.
i am attacing the configuration and debug.
thanks in advance,

version 11.3
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname R3
!
enable secret 5 $1$.Mob$wqm3UAh15deSHcmj0GHmO0
enable password k
!
ip name-server 207.238.183.71
ip name-server 207.238.183.72
appletalk routing eigrp 3
appletalk route-redistribution
ipx routing 0000.0000.3333
clock timezone GMT 5
!
dlsw local-peer peer-id 172.168.30.65 promiscuous
dlsw bridge-group 1
ip address 172.168.30.65 255.255.255.224
ipx network 331
!
interface Loopback1
ip address 172.168.30.97 255.255.255.224
ipx network 330
!
interface Ethernet0
ip address 172.168.30.33 255.255.255.224
no keepalive
appletalk cable-range 3-3 3.3
appletalk zone r3l
ipx network 3333
bridge-group 1
!
interface Ethernet0.1
ipx network 3331 encapsulation SAP
!
interface Ethernet0.2
ipx network 3332 encapsulation SNAP
!
interface Serial0
ip address 172.168.100.3 255.255.255.0
encapsulation frame-relay
ip ospf network point-to-multipoint
no ip mroute-cache
bandwidth 1562
ntp broadcast client
appletalk cable-range 536-536 536.3
appletalk zone r5r3r6w

appletalk protocol eigrp
no appletalk protocol rtmp
ipx network 55536
clockrate 64000
frame-relay map ipx 55536.0000.0000.6666 301 broadcast
frame-relay map appletalk 536.6 301 broadcast
!
interface Serial1
no ip address
clockrate 64000
!
interface Serial2
no ip address
!
interface Serial3
no ip address
shutdown
!
interface BRI0
no ip address
shutdown
!
interface Async4
ip address 173.168.65.1 255.255.255.0
encapsulation ppp
ip ospf cost 5000
ip ospf demand-circuit
dialer in-band
dialer string 4313053
dialer-group 1
async default routing
no peer neighbor-route
router ospf 1
network 0.0.0.0 255.255.255.255 area 10
!
router bgp 1
neighbor 172.168.100.5 remote-as 1
!
ip classless
ip route 3.3.3.3 255.255.255.255 Async4
!
no logging buffered
dialer-list 1 protocol ip permit
!
!
!
ipx router eigrp 1
network 55536
!
!
ipx router rip
no network 55536
!
!
!
bridge 1 protocol ieee
!
line con 0
exec-timeout 0 0
line aux 0
modem InOut
modem autoconfigure discovery
transport input all

R3#
00:19:46: Async4: re-enable timeout
00:19:46: As4: Dialer Watch: Redialing by Secondary
00:19:46: Async4: Dialing cause ip (s=173.168.65.1, d=224.0.0.5)
00:19:46: Async4: Attempting to dial 4313053
00:19:46: CHAT4: Attempting async line dialer script
00:19:46: CHAT4: no matching chat script found for 4313053
00:19:46: CHAT4: Attempting async line dialer script
00:19:46: CHAT4: no matching chat script found for 4313053
00:19:46: CHAT4: Dialing using Modem script: d0efault-d0ials0cript & System
scri
pt: none
00:19:46: CHAT4: process started
00:19:46: CHAT4: Asserting DTR
00:19:46: CHAT4: Chat script d0efault-d0ials0cript started
00:20:07: CHAT4: Chat script d0efault-d0ials0cript finished, status =
Success
00:20:09: %LINK-3-UPDOWN: Interface Async4, changed state to up
00:20:10: dialer Protocol up for As4
00:20:10: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async4, changed
state
to up



This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:25:31 GMT-3