CoD: Frame Relay

1) Multipoint Interfaces
Assign MAP statements automatically assigns Circuit (DLCI) to the interface.
So frame-relay map ... config applied ==> No need to do frame-relay interface-dlci .....

2) Layer 3 to Layer 2 Resoultion is only Locally Significatnt.
==> You can use IARP at one end and frame-relay map at other and viceversa

3) sh frame-relay map cmd o/p on Point-to-point interface
When the configuration is verified with the show frame-relay map command, a unicast
layer 3 address is not associated with the DLCI. Instead, the output point-to-point dlci
indicates that any traffic transiting the subinterface will use the DLCI specified on the
interface. In addition to this, broadcast support is automatically enabled on point-to-point
NBMA circuits. This can be seen by the output of the show frame-relay map command,
as the broadcast keyword is associated with the mapping.

4) Not only is layer 3 to layer 2 resolution only locally significant, the type of interface,
whether a main interface, multipoint subinterface, or point-to-point subinterface, is also
only locally significant.

5) no frame-relay inverse-arp ip 405 ==> to remove Mappings for Unused DLCI

6) V V IMP: Minimise Redundant Broadcast Between Hub-Spoke

--Note that on R4 and R5, multiple mapping statements resolve to the same layer 2
address. This is due to the fact that in order for traffic to pass between R4 and R5, it
must first transit R1. Also, note that the broadcast keyword on the end of their frame relay map statements is only used on one mapping. This prevents the spokes from
duplicating the same broadcast or multicast packet that is sent to the interface out the
same circuit.

--Note that the mapping that the broadcast keyword is associated with is
arbitrary, and could be moved to the mapping for R4 and R5's addresses respectively.
This is due to the fact that the broadcast resolution does not relate to the unicast
address, but instead only relates to the layer 2 circuit address.