Cisco Cisco IOS Software Release 12.2(14)S

To enable fragmentation of Frame Relay frames on an interface, use the frame-relay fragment 
end-to-end command in interface configuration mode. To disable Frame Relay fragmentation, use the 
no form of this command.

frame-relay fragment fragment-size end-to-end

Disabled

Interface configuration

Interface fragmentation and class-based fragmentation cannot be configured at the same time. To 
configure class-based fragmentation that can be applied to individual permanent virtual circuits (PVCs), 
use the frame-relay fragment command in map-class configuration mode.

Interface fragmentation supports the following types of fragment formats:

End-to-end FRF.12 format

FRF.11 Annex C format

Cisco proprietary format

When fragmentation is enabled on an interface, all PVCs on the main interface and its subinterfaces will 
have fragmentation enabled with the same configured fragment size. 

When configuring fragmentation on an interface with low- latency queueing, configure the fragment size 
to be greater than the largest high-priority frame that would be expected. This configuration will prevent 
higher priority traffic from being fragmented and queued up behind lower priority fragmented frames. 
If the size of a priority frame is larger than the configured fragment size, the priority frame will be 
fragmented.

Local Management Interface (LMI) traffic will not be fragmented.

Specifies the number of payload bytes from the original Frame Relay frame that 
will go into each fragment. This number excludes the Frame Relay header of the 
original frame. 

All the fragments of a Frame Relay frame except the last will have a payload size 
equal to fragment-size; the last fragment will have a payload less than or equal to 
fragment-size. Valid values are from 16 to 1600 bytes; the default is 53.

12.2(14)S

This command was introduced to enable fragmentation on a Frame Relay 
interface.