rame-relay map ip 192.168.1.1 201 broadcast Configuring Frame Relay Router C: Router-C(config-if)#frame-relay map ip 192.168.1.1 301 broadcast At the end of each frame-relay map command, you'll notice the keyword broadcast. This keyword should be included anytime you execute this command. The broadcast keyword maps broadcasts, multicasts, and unicasts over the PVC. Broadcasts and multicasts are an integral part of most routing protocols, SO if you have a Frame Relay WAN up and you can't figure out why EIGRP or OSPF isn't establishing adjacencies, check to make sure you've included the broadcast keyword in your map statements. The way IP-DLCI mapping works includes one odd little side effect. With a network configured as you'd expect, you cannot ping your own Frame Relay interface: Router-A#ping 192.168.1.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 192.168.1.1, timeout is 2 seconds: Success rate is 0 percent (0/5) This can burn you during troubleshooting, because you may expect to be able to ping your own interface like you can with Ethernet. You cannot ping your own interface, because there is no predefined Layer-2 address. While Ethernet interfaces have per- manent MAC addresses, Frame Relay interfaces do not. With Frame Relay, all Layer-2 addresses are configured manually. To ping yourself, you must map your own IP address to a remote router. As odd as this seems, it will work-as soon as the packet arrives at the remote router, that router will send it back, because it has a mapping for your IP address. Because there is no local Layer-2 address, only a DLCI being advertised by the frame cloud, this is the only way to make it work. Beware that ping times to your local Frame Relay interface will actually reflect the round-trip time for the PVC you specify in the mapping. Here's an example: Router-A(config-if)#frame-relay map ip 192.168.1.1 102 Router-A#ping 192.168.1.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 192.168.1.1, timeout is 2 seconds !!!!! Success rate is 10