Frame-relay lmi-type interface subcommand is used to configure LMI type. A Frame Relay-connected router encapsulates each Layer 3 packet inside a Frame Relay header and trailer before it is sent out an access link. The header and trailer are defined by the Link Access Procedure Frame Bearer Services (LAPF) specification, ITU Q.922-A.
LAPF Header Information LAPF trailer
LAPF header consist of:
- DLCI – 10 bits
- Forward Explicit Congestion Notification (FECN) – 1 bit. This bit is set by router or DCE. It means, that this frame itself has experienced congection.
- Backward Explicit Congestion Notification (BECN) – 1bit - is sent to router, when this router makes congestion.
- Discard Eligibility (DE) – 1 bit - is set to frames with unimportant traffic, the provider can discard this packets, if there is congestion.
BUT there is no protocol type field, there are 2 solutions about this:
- LAPF header, Cisco, Packet,LAPF trailer
- LAPF header, RFC 1490, Packet, LAPF trailer
Two types of encapsulation:
- encapsulation frame-relay ietf
- encapsulation frame-relay cisco
DTEs use and react to the fields specified by these two types of encapsulation, but Frame Relay switches ignore these fields. Because the frames flow from DTE to DTE, both DTEs should agree on the encapsulation used. The switches don’t care. However, each VC can use a different encapsulation. In the configuration, the encapsulation created by Cisco is called cisco, and the other one is called ietf.
Addressing
Local addressing is significant only on local access link on one PVC. Global addressing is simply a way of choosing DLCI numbers when planning a Frame Relay network so that working with DLCIs is much easier. Because local addressing is a fact, global addressing does not change these rules. Source DTE puts DLCI of destination DTE to the header, and the last switch, that is directly connected to the destination DTE, changes DLCI to the source DTE.
The sender treats the DLCI field as a destination address, using the destination’s global DLCI in the header.
The receiver thinks of the DLCI field as the source address, because it contains the global DLCI of the frame’s sender.
It is possible address to physical interface, multipoint or point-to-point subinterfaces.
Network Layer Concerns
3 ways of assigning ip addresses:
- One subnet containing all Frame Relay DTEs
- One subnet per VC - hub and spoke technologie - it avoids split horizon issues.
- A hybrid of the first two options
There is no capability exists for a Frame Relay DTE to send a single frame into the Frame Relay network and have that frame replicated and delivered across multiple VCs to multiple destinations. However, routers need to send broadcasts for several features to work. In particular, routing protocol updates are either broadcasts or multicasts. To map DLCI to ip Inverse ARP is used. Inverse ARP dynamically creates a mapping between the Layer 3 address (for example, the IP address) and the Layer 2 address (the DLCI). After the VC is up, each router announces its network layer address by sending an Inverse ARP message over that VC. To map staticly, you need to enter interface sub command, for instant:
frame-relay map ip 199.1.1.2 52 broadcast
The broadcast keyword is required when the router needs to send broadcasts or multicasts to the neighboring router — for example, to support routing protocol messages such as Hellos.
Configuring Frame Relay
Full meshed with 1 i p network:
interface serial0/0/0
encapsulation frame-relay
ip address 199.1.1.2 255.255.255.0
The LMI type is automatically sensed.
The (default) encapsulation is Cisco instead of IETF.
PVC DLCIs are learned via LMI status messages.
Inverse ARP is enabled (by default) and is triggered when the status message declaring that the VCs are up is received.
Change lmi:
frame-relay lmi-type ansi
Change encapsulation on all VCs on interface:
interface serial0/0/0
encapsulation frame-relay ietf
Change encapsulation for one VC:
frame-relay interface-dlci 53 ietf
Static mapping:
no frame-relay inverse-arp
frame-relay map ip 199.1.1.2 52 broadcast
The broadcast keyword is required when the router needs to send broadcasts or multicasts to the neighboring router—for example, to support routing protocol messages such as Hellos
A Partially Meshed Network with One IP Subnet Per VC
interface serial 0/0/0.1 point-to-point
ip address 140.1.1.2 255.255.255.0
frame-relay interface-dlci 51
Another way to map dlci to subinterface:
frame-relay map ip 140.1.1.2 52 broadcast
First physical interface subcommand encapsulation frame-relay. Then configure ip address(ip address interface subcommand). Define lmi type with frame relay lmi-type command. Manually map ip to DLCI frame-relay map ip.
The LMI setting is a per-physical-interface setting, even if subinterfaces are used, so the frame-relay lmi-type command is always a subcommand under the physical interface.
Show commands:
Show interfaces – shows all info about interface
Show frame-relay pvc - shows information about all PVCs.
Show frame-relay map - it shows IP-to-DLCI mappings.
Show frame-relay lmi
Interface serial 0/1/0.0 point-to point Frame-relay interface-dlci 53 - This command is typically used for subinterfaces DLCI is configured for every sub interface. Cisco IOS software needs to associate the correct PVC with the correct subinterface. This is accomplished with the frame-relay interface-dlci command. In case of sub interfaces DLCI is destination DLCI. This is Global sheme of addressing. If there is only one DLCI on main site router, than this is Global Addressing.