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

From: khalid siddiq (khalidsi@xxxxxxxxxxx)
Date: Sat Oct 28 2000 - 05:27:28 GMT-3


   

Thank Tony,
why i neet dialer profile, you mean that ip ospf demand circuit don't work
with legacy DDR??

hello triggered the link, when idle timer expired after 120 second it bring
the link down and during that interval it show that ospf neighbor adjacency
is formed and hello are suppressed,
is that some bug or ????? ,i am using Version 11.3(7)T
any help is appricated.

00:25:58: OSPF: Dead event ignored for 192.168.21.1 on demand circuit
Async4sh ip osp ne

R3#sh ip osp inter
Async4 is up, line protocol is up
  Internet Address 173.168.65.1/24, Area 10
  Process ID 1, Router ID 172.168.30.97, Network Type POINT_TO_POINT, Cost:
5000
  Configured as demand circuit.
  Run as demand circuit.
  DoNotAge LSA allowed.
  Transmit Delay is 1 sec, State POINT_TO_POINT,
  Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
    Hello due in 00:00:02
  Neighbor Count is 1, Adjacent neighbor count is 1
    Adjacent with neighbor 192.168.21.1 (Hello suppressed)
  Suppress hello for 1 neighbor(s)

R3#sh ip osp
Routing Process "ospf 1" with ID 172.168.30.97
Supports only single TOS(TOS0) routes
SPF schedule delay 5 secs, Hold time between two SPFs 10 secs
Number of DCbitless external LSA 0
Number of DoNotAge external LSA 0
Number of areas in this router is 1. 1 normal 0 stub 0 nssa
    Area 10
        Number of interfaces in this area is 5
        Area has no authentication
        SPF algorithm executed 8 times
        Area ranges are
        Link State Update Interval is 00:30:00 and due in 00:08:15
        Link State Age Interval is 00:20:00 and due in 00:18:14
        Number of DCbitless LSA 0
        Number of indication LSA 0
        Number of DoNotAge LSA 0

R3#sh ip osp ne

Neighbor ID Pri State Dead Time Address Interface
192.168.21.1 1 FULL/ - - 173.168.65.2 Async4
192.168.21.1 100 FULL/ - 00:01:43 172.168.100.5 Serial0

>From: "Tony Olzak" <aolzak@buckeye-express.com>
>To: "khalid siddiq" <khalidsi@hotmail.com>, <ccielab@groupstudy.com>
>Subject: Re: Async interface triggered by 224.0.0.5 using ip ospf demand
>circuit
>Date: Fri, 27 Oct 2000 18:22:46 -0400
>
>Try using a dialer profile. It looks like you're triggering a topology
>change when your async line goes down. The dialer profile will spoof the
>interface as up.
>
>
>Tony
>
>----- Original Message -----
>From: "khalid siddiq" <khalidsi@hotmail.com>
>To: <ccielab@groupstudy.com>
>Sent: Friday, October 27, 2000 11:01 AM
>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