FRAME_RELAY

Point-to-Point

R1#int s0/0/0
encapsulation frame-relay
ip address 10.0.0.1 255.255.255.248

R2#int s0/0/0
encapsulation frame-relay
ip address 10.0.0.2 255.255.255.248

R3#int s0/0/0
encapsulation frame-relay
ip address 10.0.0.3 255.255.255.248

R4#int s0/0/0
encapsulation frame-relay
ip address 10.0.0.4 255.255.255.248

IOS enables Frame Relay InARP by default, so all four routers learn other routers IP address/DLCI mappings dynamically. 
After creating this configuration, the four routers can ping each other if the PVC link exists between them. For example, in Partial-Mesh design, R2 and R3 can't ping each other.
--------------------------------------------------------------------------------------------------------------------


Multipoint 

When using subinterfaces, IOS needs a command under Frame Relay subinterface that associates each PVC with that subinterface:
frame-relay interface-dlci <number> - just associates DLCI with subinterface, relying on Frame Relay Inverse Arp to discover mappings.
frame-relay map  - statically configures mapping, while also associating DLCI with subint.


R1#int s0/0/0
 no ip-address
encapsulation frame-relay
int s0/0/0.1
ip address 10.0.0.1 255.255.255.248
frame-relay interface-dlci 102
frame-relay interface-dlci 103
frame-relay interface-dlci 104

დანარჩენ 3 როუტერზეც ანალოგიური კონფიგურაცია, და ვიღებთ იგივე შედეგს რაც პირველ ვარიანტში: ერთმანეთთან ვისაც აქვს PVC დაპინგავენ ერთმანეთს, ვისაც არ აქვს – ვერა.