Pierre-Alex GUANEL wrote: > > On a non broadcast network, using the keyword "neighbour" will > allow the DR > to start the adjacency with the indicated neighbours. Once the > adjacency is > completed, all ospf traffic between neighbours will be unicast. > Therefore on > such networks, you do not need to add the keyword "broadcast" > on the > frame-relay map statement for OSPF to work. > > [ However not having the keyword broadcast may affect other > network > functions that depend on the broadcast traffic, therefore it is > a good idea > to put the keyword "broadcast" in the frame-map statement]. > > > Any flaw in my logic?
Nope, no flaw in your logic as far as I know, but I'm wondering, what other broadcast traffic does a router need to forward or generate on a Frame Relay link? Other than a routing protocol, what other broadcast traffic would there be (for IP that is)? I bet you can safely leave off the broadcast keyword if you are using the neighbor command to let the router know about its OSPF neighbors, at least in a typical situation. Priscilla > > Evidence: (you can see here that r1 is sending to r2 (10.10.1.2 > ) , r3 > (10.10.1.3) and r5 (10.10.10.5) via unicast. You can see that > r2 is > responded with unicast. > > r1#debug ip pac > 08:26:51: IP: s=10.10.1.1 (local), d=10.10.1.3 (Serial0/0.1), > len 76, > sending > 08:26:51: IP: s=10.10.1.1 (local), d=10.10.1.5 (Serial0/0.1), > len 76, > sending > 08:26:51: IP: s=10.10.1.1 (local), d=10.10.1.2 (Serial0/0.1), > len 76, > sending > 08:26:51: IP: s=10.1.1.1 (local), d=224.0.0.5 (Ethernet0/0), > len 64, sending > broad/multica > > r1#debug frame pack int ser 0/0.1 > > 08:32:51: Serial0/0.1(o): dlci 103(0x1871), NLPID 0x3CC(IP), > datagramsize 80 > 08:32:51: Serial0/0.1(o): dlci 105(0x1891), NLPID 0x3CC(IP), > datagramsize 80 > 08:32:51: Serial0/0.1(o): dlci 102(0x1861), NLPID 0x3CC(IP), > datagramsize 80 > --- > > on R2# > > 08:43:16: IP: s=10.10.1.1 (Serial0/0), d=10.10.1.2, len 76, > rcvd 0 > 08:43:25: IP: s=10.10.1.2 (local), d=10.10.1.1 (Serial0/0), len > 68, sending > 08:43:25: IP: s=137.20.20.1 (local), d=224.0.0.5 (Ethernet0/0), > len 64, > sending broad/mult > icast > > ------------------------- router configuration -------- > > r1#show run int ser 0/0.1 > Building configuration... > > Current configuration : 198 bytes > ! > interface Serial0/0.1 multipoint > ip address 10.10.1.1 255.255.0.0 > ip ospf priority 200 > frame-relay map ip 10.10.1.2 102 > frame-relay map ip 10.10.1.3 103 > frame-relay map ip 10.10.1.5 105 > end > > > r2#show run int ser 0/0 > Building configuration... > > Current configuration : 216 bytes > ! > interface Serial0/0 > ip address 10.10.1.2 255.255.0.0 > encapsulation frame-relay IETF > ip ospf priority 0 > ip policy route-map 10 > clockrate 128000 > frame-relay map ip 10.10.1.1 201 > frame-relay lmi-type ansi > > r3#show run int ser 0/1 > Building configuration... > > Current configuration : 216 bytes > ! > interface Serial0/1 > ip address 10.10.1.3 255.255.0.0 > encapsulation frame-relay IETF > ip ospf priority 0 > ip policy route-map 10 > clockrate 128000 > frame-relay map ip 10.10.1.1 301 > frame-relay lmi-type ansi > > r5#show run int ser 6/0 > Building configuration... > > Current configuration : 222 bytes > ! > interface Serial6/0 > ip address 10.10.1.5 255.255.0.0 > encapsulation frame-relay IETF > ip ospf priority 0 > ip policy route-map 10 > serial restart-delay 0 > frame-relay map ip 10.10.1.1 501 > frame-relay lmi-type ansi > end > > Thank you, > > Pierre-Alex Guanel > > Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=60722&t=60715 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
