I started on a frame relay lab but got side tracked with the “broadcast” keyword.

gotchas:

1. PVC deleted means that frame switch does not have the dlci configured
2. PVC inactive means you have a typo in your config
3. use debug frame packet
4. point-to-point <> physical use map statements with the broadcast keyword. Broadcast enables the dlci to forward both broadcast and multicast traffic. (think RIP, OSPF, mcast, etc..)
5. set the DE bit on packets greater then 1024 bytes on dlci 502 = (global) frame-relay de-list 1 protocol ip gt 1024 (int) frame-relay de-group  1 502
6. chap = ppp over frame-relay. (virtual int, ppp authen chap, (global) username R1 password xx) ( don’t forget to remove the pertinent frame config from the serial interface and move it to the virtual-template along with the ip address!).
7. req: send full status updates of dlci’s every 180 seconds solution: doc cd = frame-relay lmi-n391dte 18
8. I went the wrong way the last question. The solution was to search the doc cd with the keywords in the question ” bytes per second & packets per second” frame-relay broadcast-queue 50 36000 90
9. DO NOT mix DR and NON-DR network types. Even though you can tweak the hello’s to form an adjacency the neighbors will not be functioning. ie sho ip route ospf = nothing
10. Ospf is not running right – check your frame-relay map statements and add broadcast where needed.
11. If your lab scenerio forbids you from using the broadcast keyword you will have to use ip ospf net non-broadcast or ip ospf net point-to-multi non-broadcast.
12. IOS will not permit OSPF neighbor statements for network types broadcast or point-to-point – only for non-broadcast and for point-to-multipoint

Broadcast keyword

Physical / multipoint interfaces = add the broadcast keyword

hub to spoke = add the broadcast keyword

spoke to hub = add the broadcast keyword

spoke to spoke = do not add the broadcast keyword

ip ospf net non-broadcast – sends unicast. You need the neighbor command.  Adding the broadcast keyword is not necessary.

side note: make sure your timers match for different ip ospf network types.

Here network types work together:

Broadcast to Broadcast
Non-Broadcast to Non-Broadcast
Point-to-Point to Point-to-Point
Point-to-Multipoint to Point-to-Multipoint
Broadcast to Non-Broadcast (adjust hello/dead timers)
Point-to-Point to Point-to-Multipoint (adjust hello/dead timers)

broadcast = 10 hello 40 dead

non-broadcast = 30 hello 120 dead

You can tweak the hello/dead with ip ospf hello-interval or ip ospf dead commands.
* An adjacency will be formed with routers running OSPF, as long as the authentication is the same, the stub flag is the same, the area is the same, and the timers are the same.

* If you mix and match network types we might need to modify the timers so we can form an adjacency. This is done with the ip ospf hello-interval and ip ospf dead-interval commands.

* You can mix and match network types as long as the network types involved have the same DR relationship. You can’t mix network types that require a DR with those that don’t require a DR.

Dont Need a DR:
Point-to-Point and Point-to-Multipoint (if you adjust timers)
Point-to-Point and Point-to-Multipoint non-broadcast (if you adjust timers)
Point-to-Multipoint and Point-to-Multipoint non-broadcast

Need a DR:
Broadcast and Non-Broadcast (if you adjust timers)

Frame relay interfaces..

1- broadcast network: no need for neighbor command, if given under the frame relay interface Broadcast keyword should be enabled on the frame relay map statements

2- non broadcast network u have to specify the neighbors statically under the ospf process… on frame relay mapping it doesn’t cares about the broadcast keyword (because the updates are going as unicast)

but it is mostly used if in frame relay due to a restriction u r not allowed to use the the broadcast keyword

3- p2mp: this network type is specially used for NBMA networks, so this is best suitable for the hub and spoke networks on frame relay…

u don’t have to give the neighbor command in ospf process, for the neighbor to come up…

u NEED BROADCAST keyword on the frame relay map statements for this to work

4- p2mp non broadcast (cisco propriety)  u need to specify the neighbor command in ospf process and on frame relay mappings u don’t need broadcast keyword.