2. Change the encapsulation
Go in interface mode and select the Frame Relay
encapsulation on the interface. There are two types of
Frame Relay encapsulations: Cisco and IETF. Cisco is the
default. Syntax to set your encapsulation is
encapsulation frame-relay [ietf]
Configure LMI type
The three LMI types are Cisco, Ansi, and Q933a. For IOS
11.2 and higher, the LMI type is automatically detected
frame-relay lmi-type [cisco | ansi | 933a]
3. Configure Frame Relay map
configuring a static Frame Relay map, is optional unless you are
using subinterfaces. The Frame Relay map will map a Layer 3
address to a local DLCI. This step is optional because inverse-arp
will automatically perform this map for you. The syntax for a
Frame Relay map is as follows:
frame-relay map protocol address dlci [broadcast] [cisco |
ietf]
4. Configure subinterfaces
If you are using a routing protocol in a hub-and-spoke topology,
you will probably want to use subinterfaces to avoid the split-
horizon problem. To configure a subinterface, remove the IP
address off the main interface and put it under the subinterface.
Configuring a subinterface involves assigning it a number and
specifying the type. The following command creates point-to-
point subinterface serial0/0.1
Router(config)#interface serial0/0.1 point-to-point
To create a multipoint subinterface, enter multipoint instead:
Router(config)#interface serial0/0.1 multipoint
5. Assign IP address to subinterface
After entering one of these commands you will be taken to the
subinterface configuration mode where you can enter your IP
address:
Router(config-subif)#ip address 10.0.0.2 255.0.0.0
If you are using a multipoint subinterface, you will need to
configure frame-relay maps and you cannot rely on inverse-arp.
If you are using a point-to-point subinterface, you will need to
assign a DLCI to the subinterface. This is only for point-to-point
subinterfaces; this is not needed on the main interface or on
multipoint subinterfaces. To assign a DLCI to a point-to-point
subinterface, enter the following command under the
subinterface:
frame-relay interface-dlci dlci
6.
7. Now first configure R1. Fast Ethernet port and hostname is
already configured. Double click on R1 and configure serial port
for frame relay encapsulation and further create sub interface
for connecting R2, R3, R4. Configure also static route for
connecting remaining network.
Configure R1
R1>enable
R1#configure terminal
R1(config)#interface serial 0/0/0
R1(config-if)#encapsulation frame-relay
R1(config-if)#no shutdown
R1(config-if)#exit
12. Router(config)#interface serial 0/0/0 Enter in interface mode
Router(config-if)#encapsulation frame-relay
Turns on Frame Relay encapsulation with the default
encapsulation type of cisco
Router(config-if)#frame-relay lmitype {ansi | cisco |
q933a}
Depending on the option you select, this command sets
the LMI type to the ANSI standard, the Cisco standard,
or the ITU-T Q.933 Annex A standard.
Router(config-if)#frame-relay interface-dlci 110
Sets the DLCI number of 110 on the local interface and
enters Frame Relay DLCI configuration mode
Router(config-fr-dlci)#exit Returns to interface configuration mode
Router(config-if)#frame-relay map ip 192.168.100.1 110
broadcast
Maps the remote IP address (192.168.100.1) to the local
DLCI number (110). The optional broadcast keyword
specifies that broadcasts across IP should be forwarded
to this address. This is necessary when using dynamic
routing protocols.
13. Router(config-if)#no frame-relay inverse
arp
Turns off Inverse ARP.
Router#show frame-relay map Displays IP/DLCI map entries
Router#show frame-relay pvc Displays the status of all PVCs configured
Router#show frame-relay lmi Displays LMI statistics
Router#clear frame-relay counters Clears and resets all Frame Relay counters
Router#clear frame-relay inarp
Clears all Inverse ARP entries from the map
table
Router#debug frame-relay lmi
Used to help determine whether a router
and Frame Relay switch are exchanging LMI
packets properly