From: Gustavo Novais (gustavo.novais@novabase.pt)
Date: Mon Aug 15 2005 - 15:52:59 GMT-3
Hello group!
I'm doing IPexpert lab 38 on which we have a part on which e should
configure OSPF over ATM SVC "with the appropriate network"
The thing is I tried to do it with network point-multipoint and the adj
comes up great, but some time later it falls to never come up again. To
simplify things I removed authentication and put link on Area 0. I see
all those SVC coming up and down, up and down, each belonging to a
hello.
If I configure ip ospf network point to point the circuit becomes stable
and adjancency remains up without problems.
I've configured (earlier task request) idle timeout on SVC's, so I think
that the issue here is related to timers. In point-to-point I have
hellos every 10 sec which is enough to keep the same SVC up on and on.
When I configure point to multipoint I have hellos every 30 sec which is
enough for the svc be torn out.
My question is, is there any way to make OSPF not sensible to which
VPI/VCI the updates come? My guess here is that OSPF saw initial updates
coming from SVC 0/70 and is waiting for further hellos come from same
SVC, which they won't!
How to work around this issue?
If by any chance we configure ip ospf demand circuit on this scenario
this will always happen, because the hellos will be suppressed long
enough to tear the SVC down.
R6(config-subif)#ip ospf network point-to-multipoint
R6(config-subif)#^Z
R6#deb ip ospf adj
OSPF adjacency events debugging is on
R6#
R6#
R6#
*Mar 2 00:00:01.588: OSPF: Rcv DBD from 138.10.9.9 on ATM1/0.69 seq
0x11FC opt 0x52 flag 0x7 len 32 mtu 4470 state INIT
*Mar 2 00:00:01.588: OSPF: 2 Way Communication to 138.10.9.9 on
ATM1/0.69, state 2WAY
*Mar 2 00:00:01.588: OSPF: Send DBD to 138.10.9.9 on ATM1/0.69 seq
0x199 opt 0x52 flag 0x7 len 32
*Mar 2 00:00:01.592: OSPF: NBR Negotiation Done. We are the SLAVE
*Mar 2 00:00:01.592: OSPF: Send DBD to 138.10.9.9 on ATM1/0.69 seq
0x11FC opt 0x52 flag 0x2 len 212
*Mar 2 00:00:01.596: OSPF: Rcv DBD from 138.10.9.9 on ATM1/0.69 seq
0x11FD opt 0x52 flag 0x3 len 212 mtu 4470 state EXCHANGE
*Mar 2 00:00:01.596: OSPF: Send DBD to 138.10.9.9 on ATM1/0.69 seq
0x11FD opt 0x52 flag 0x0 len 32
*Mar 2 00:00:01.596: OSPF: Database request to 138.10.9.9
*Mar 2 00:00:01.596: OSPF: sent LS REQ packet to 138.10.69.9, length 12
*Mar 2 00:00:01.600: OSPF: Rcv DBD from 138.10.9.9 on ATM1/0.69 seq
0x11FE opt 0x52 flag 0x1 len 32 mtu 4470 state EXCHANGE
*Mar 2 00:00:01.600: OSPF: Exchange Done with 138.10.9.9 on ATM1/0.69
*Mar 2 00:00:01.600: OSPF: Send DBD to 138.10.9.9 on ATM1/0.69 seq
0x11FE opt 0x52 flag 0x0 len 32
*Mar 2 00:00:01.604: OSPF: Synchronized with 138.10.9.9 on ATM1/0.69,
state FULL
*Mar 2 00:00:01.604: %OSPF-5-ADJCHG: Process 1, Nbr 138.10.9.9 on
ATM1/0.69 from LOADING to FULL, Loading Done
*Mar 2 00:00:02.104: OSPF: Build router LSA for area 0, router ID
138.10.6.6, seq 0x8000000A
*Mar 2 00:00:41.938: %ATM-5-UPDOWN: Interface ATM1/0.69, Changing
autovc 0/70 to SVC removed.
*Mar 2 00:00:48.573: %ATM-5-UPDOWN: Interface ATM1/0.69, Changing
autovc 0/71 to SVC created.
*Mar 2 00:00:48.581: %ATM-5-UPDOWN: Interface ATM1/0.69, Changing
autovc 0/71 to SVC activated.
*Mar 2 00:00:58.517: %ATM-5-UPDOWN: Interface ATM1/0.69, Changing
autovc 0/71 to SVC removed.
*Mar 2 00:01:01.602: %ATM-5-UPDOWN: Interface ATM1/0.69, Changing
autovc 0/72 to SVC created.
*Mar 2 00:01:01.606: %ATM-5-UPDOWN: Interface ATM1/0.69, Changing
autovc 0/72 to SVC activated.
*Mar 2 00:01:11.542: %ATM-5-UPDOWN: Interface ATM1/0.69, Changing
autovc 0/72 to SVC removed.
*Mar 2 00:01:18.574: %ATM-5-UPDOWN: Interface ATM1/0.69, Changing
autovc 0/73 to SVC created.
*Mar 2 00:01:18.578: %ATM-5-UPDOWN: Interface ATM1/0.69, Changing
autovc 0/73 to SVC activated.
*Mar 2 00:01:28.542: %ATM-5-UPDOWN: Interface ATM1/0.69, Changing
autovc 0/73 to SVC removed.
*Mar 2 00:01:31.603: %ATM-5-UPDOWN: Interface ATM1/0.69, Changing
autovc 0/74 to SVC created.
*Mar 2 00:01:31.603: %ATM-5-UPDOWN: Interface ATM1/0.69, Changing
autovc 0/74 to SVC activated.
*Mar 2 00:01:41.515: %ATM-5-UPDOWN: Interface ATM1/0.69, Changing
autovc 0/74 to SVC removed.
*Mar 2 00:01:48.575: %ATM-5-UPDOWN: Interface ATM1/0.69, Changing
autovc 0/75 to SVC created.
*Mar 2 00:01:48.579: %ATM-5-UPDOWN: Interface ATM1/0.69, Changing
autovc 0/75 to SVC activated.
*Mar 2 00:01:58.531: %ATM-5-UPDOWN: Interface ATM1/0.69, Changing
autovc 0/75 to SVC removed.
*Mar 2 00:02:01.604: %ATM-5-UPDOWN: Interface ATM1/0.69, Changing
autovc 0/76 to SVC created.
*Mar 2 00:02:01.608: %ATM-5-UPDOWN: Interface ATM1/0.69, Changing
autovc 0/76 to SVC activated.
*Mar 2 00:02:11.541: %ATM-5-UPDOWN: Interface ATM1/0.69, Changing
autovc 0/76 to SVC removed.
*Mar 2 00:02:18.564: OSPF: 138.10.9.9 address 138.10.69.9 on ATM1/0.69
is dead
*Mar 2 00:02:18.564: OSPF: 138.10.9.9 address 138.10.69.9 on ATM1/0.69
is dead, state DOWN
*Mar 2 00:02:18.564: %OSPF-5-ADJCHG: Process 1, Nbr 138.10.9.9 on
ATM1/0.69 from FULL to DOWN, Neighbor Down: Dead timer expired
*Mar 2 00:02:18.572: %ATM-5-UPDOWN: Interface ATM1/0.69, Changing
autovc 0/77 to SVC created.
*Mar 2 00:02:18.576: %ATM-5-UPDOWN: Interface ATM1/0.69, Changing
autovc 0/77 to SVC activated.
*Mar 2 00:02:19.065: OSPF: Build router LSA for area 0, router ID
138.10.6.6, seq 0x8000000B
*Mar 2 00:02:28.520: %ATM-5-UPDOWN: Interface ATM1/0.69, Changing
autovc 0/77 to SVC removed.
ATM config equal on both sides
interface ATM1/0
no ip address
atm ilmi-keepalive 10 retry 2
pvc 0/5 qsaal
!
pvc 0/16 ilmi
ilmi manage
!
!
interface ATM1/0.69 multipoint
ip address 138.10.69.6 255.255.255.0
ip ospf network point-to-point
atm esi-address 666666666666.00
!
svc R9 nsap 47.0091810000000050E200EA01.999999999999.00
protocol ip 138.10.69.9 broadcast
ilmi manage
idle-timeout 10
!
!
svc R6 nsap 47.0091810000000050E200EA01.666666666666.00
protocol ip 138.10.69.6
idle-timeout 10
!
Am I missing something?
Any help would be appreciated.
Thanks
This archive was generated by hypermail 2.1.4 : Sun Sep 04 2005 - 17:01:19 GMT-3