ccna 2 exam

ccna 2 exam.RouterC# show frame-relay map SerialO/1/1.1 (up): ip 140.1.1.1dlci 501(0xlF5z 0x7C50)f dynamic,broadcastz f status defined, activeSerialO/1/1.1 (up): ip 140 .1.1.2 dlci 502(0xlF6,0x7C60), dynamic,broadcastz, status defined, activeOSPF Issues on Frame Relay Multipoint and Physical InterfacesIn many enterprise networks that use Frame Relay, administrators select only point-to-point subinterfaces for Frame Relay. Many Frame Relay WANs connect remote sites to a central site, and there is no problem with this point-to-point model. Open Shortest Path First (OSPF) and Enhanced Interior Gateway Routing Protocol (EIGRP) also work well with the default settings of using point-to-point Frame Relay subinterfaces.In fact, OSPF requires some additional configuration when using multipoint or physical interfaces configured with Frame Relay. These issues are discussed briefly in this section.If you use only the OSPF configuration discussed in Chapter 8, "IPV4OSPF," a router using OSPF will not become a neighbor on a Frame Relay physical interface or multipoint subinterface. Why? Frame Relay physical and multipoint subinterfaces use a non-broadcast OSPF network type by default. This network type means that the router does not attempt to dynamically discover any OSPF neighbors on that interface.There are many solutions to this OSPF problem, but the simplest of them is to choose a different OSPF network type on that Frame Relay interface. (Chapter 8 introduces the concept of OSPF network types for interfaces, but you also need to know about Frame Relay before you can learn about this little problem and solution.) Concrete solution: modify the OSPF network type to point-to-multipoint so that routers can dynamically discover each other on physical or multipoint subinterfaces.For example, the previous examples (Examples 14-13, 14-14, and 14-15) show that Routers A, B, and C all use multipoint subinterfaces and share the same