From: Pavel Bykov (slidersv@gmail.com)
Date: Sun Dec 07 2008 - 10:03:57 ARST
4- what if you add new routers to the network? How are they going to be
discovered? And if you have 50 devices on multiaccess network, are you going
to send hello 50x50 = 2500 times? wouldn't it be easier to send just 50
times?
Seems logical to me.
On Sat, Dec 6, 2008 at 10:30 PM, Luca Tosolini <l.tosolini@chello.nl> wrote:
> Hi Experts,
> I captured the adjacency establishment on a p2m-broadcast network and
> the following appears:
> 1- first hellos multicast
> 2- then the neighbor is discovered and hello switches to unicast
> 3- dd, lsr, lsu and lsa all unicast to neighbor address
> 4- once the db are synchronized, the hellos move back to multicast
> While steps 1, 2, 3 make perfect sense to me, step 4 is total
> nosense :-(
>
> Any idea while it switches back to multicast? see capture below
> Thanks,
> bit.
>
> No. Time Source Destination Protocol
> Info
> 1 0.000000 192.168.0.1 224.0.0.5 OSPF
> Hello Packet
>
> No. Time Source Destination Protocol
> Info
> 2 30.036926 192.168.0.1 224.0.0.5 OSPF
> Hello Packet
>
> No. Time Source Destination Protocol
> Info
> 3 47.602189 Inverse
> ARP Who is 0401? Tell 0000
>
> No. Time Source Destination Protocol
> Info
> 5 60.184209 192.168.0.1 224.0.0.5 OSPF
> Hello Packet
>
> No. Time Source Destination Protocol
> Info
> 6 60.194623 192.168.0.2 192.168.0.1 OSPF
> Hello Packet
>
> No. Time Source Destination Protocol
> Info
> 7 60.217233 192.168.0.1 192.168.0.2 OSPF
> DB Descr.
>
> No. Time Source Destination Protocol
> Info
> 8 60.217619 192.168.0.1 192.168.0.2 OSPF
> Hello Packet
>
> No. Time Source Destination Protocol
> Info
> 9 60.231960 192.168.0.2 192.168.0.1 OSPF
> DB Descr.
>
> No. Time Source Destination Protocol
> Info
> 10 60.232854 192.168.0.2 192.168.0.1 OSPF
> DB Descr.
>
> No. Time Source Destination Protocol
> Info
> 11 60.254059 192.168.0.1 192.168.0.2 OSPF
> DB Descr.
>
> No. Time Source Destination Protocol
> Info
> 12 60.266698 192.168.0.2 192.168.0.1 OSPF
> DB Descr.
>
> No. Time Source Destination Protocol
> Info
> 13 60.287051 192.168.0.1 192.168.0.2 OSPF
> DB Descr.
>
> No. Time Source Destination Protocol
> Info
> 14 60.287485 192.168.0.1 192.168.0.2 OSPF
> LS Request
>
> No. Time Source Destination Protocol
> Info
> 15 60.302372 192.168.0.2 192.168.0.1 OSPF
> LS Request
>
> No. Time Source Destination Protocol
> Info
> 16 60.302500 192.168.0.2 192.168.0.1 OSPF
> DB Descr.
>
> No. Time Source Destination Protocol
> Info
> 17 60.302695 192.168.0.2 192.168.0.1 OSPF
> LS Update
>
> No. Time Source Destination Protocol
> Info
> 18 60.323451 192.168.0.1 192.168.0.2 OSPF
> LS Update
>
> No. Time Source Destination Protocol
> Info
> 19 60.823180 192.168.0.1 192.168.0.2 OSPF
> LS Update
>
> No. Time Source Destination Protocol
> Info
> 20 60.839132 192.168.0.2 192.168.0.1 OSPF
> LS Update
>
> No. Time Source Destination Protocol
> Info
> 21 62.828848 192.168.0.1 192.168.0.2 OSPF
> LS Acknowledge
>
> No. Time Source Destination Protocol
> Info
> 22 62.852114 192.168.0.2 192.168.0.1 OSPF
> LS Acknowledge
>
> No. Time Source Destination Protocol
> Info
> 23 75.659995 192.168.0.2 224.0.0.5 OSPF
> Hello Packet
>
> No. Time Source Destination Protocol
> Info
> 24 90.328088 192.168.0.1 224.0.0.5 OSPF
> Hello Packet
>
> No. Time Source Destination Protocol
> Info
> 25 105.837465 192.168.0.2 224.0.0.5 OSPF
> Hello Packet
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
>
-- Pavel Bykov ---------------- Don't forget to help stopping the braindumps, use of which reduces value of your certifications. Sign the petition at http://www.stopbraindumps.com/Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Thu Jan 01 2009 - 12:53:07 ARST