frame-relay interface-dlci dlci [ietf | cisco] [voice-encap size]
no frame-relay interface-dlci dlci [ietf | cisco] [voice-encap size]
BOOTP server only:
frame-relay interface-dlci dlci [protocol ip ip-address]
DLCI number to be used on the specified subinterface.
ietf | cisco
(Optional) Encapsulation type: Internet Engineering Task Force (IETF) Frame Relay encapsulation or Cisco Frame Relay encapsulation.
protocol ip ip-address
(Optional) Indicates the IP address of the main interface of a new router or access server onto which a router configuration file is to be automatically installed over a Frame Relay network. Use this option only when this device will act as the BOOTP server for automatic installation over Frame Relay.
(Supported on the Cisco MC3810 only.) Specifies that data segmentation will be used to support Voice over Frame Relay. The voice encapsulation size denotes the data segmentation size. For a list of recommended data segmentation sizes, see Usage Guidelines.
To assign a data link connection identifier (DLCI) to a specified Frame Relay subinterface on the router or access server, use the frame-relay interface-dlci interface configuration command. To remove this assignment, use the no form of this command.
This command is typically used for subinterfaces. However, it can also be used on main interfaces. Using the frame-relay interface-dlci command on main interfaces will enable the use of routing protocols on interfaces that use Inverse ARP . The frame-relay interface-dlci command on a main interface is also valuable for assigning a specific class to a single PVC where special characteristics are desired. Subinterfaces are logical interfaces associated with a physical interface. You must specify the interface and subinterface before you can use this command to assign any DLCIs and any encapsulation or broadcast options. See the "Examples" section for the sequence of commands.
This command is required for all point-to-point subinterfaces; it is also required for multipoint subinterfaces for which dynamic address resolution is enabled. It is not required for multipoint subinterfaces configured with static address mappings.
Use the protocol ip ip-address option only when this router or access server will act as the BOOTP server for auto installation over Frame Relay.
For the voice-encap option on the Cisco MC3810, set the data segmentation size based on the port access rate. The table below lists recommended data segmentation sizes for different port access rates. Also, when the voice-encap option is configured on the Cisco MC3810, all priority queuing, custom queuing, and weighted fair queuing is disabled on the interface.
Table: Recommended Data Segmentation Sizes for Port Access Rates
Port Access Rate The data segmentation size is based for back-to-back Frame Relay. If sending traffic through an IGX with standard Frame Relay, add an extra 15 bytes to the recommended data segmentation size. 64 kbps 80 bytes 128 kbps 160 bytes 256 kbps 320 bytes 512 kbps 640 bytes 1536 kbps (full T1) 1600 bytes 2048 kbps (full E1) 1600 bytes
The following example assigns DLCI 100 to serial subinterface 0/0.17:! Enter interface configuration and begin assignments on interface serial 0/0 Router#interface serial 0/0 ! Enter subinterface configuration by assigning subinterface 17 interface serial 0/0.17 ! Now assign a DLCI number to subinterface 0/0.17 Router(config-if)#frame-relay interface-dlci 100
� Cisco Systems, Inc. 2001, 2002, 2003
World Wide Education
|Converted from CHM to HTML with chm2web Pro 2.85 (unicode)|