Configuring DLCIs on Link Services Logical Interfaces
For link services interfaces only, you can configure multiple DLCIs for MLFR FRF.16 or MLPPP bundles.
DLCIs are not supported on multilink interfaces.
Configuring Point-to-Point DLCIs for MLFR FRF.16 and MLPPP Bundles
For link services interfaces only, you can configure multiple point-to-point DLCIs for each MLFR FRF.16 or MLPPP bundle. A channelized interface, such as ls-1/1/1:0, denotes a single MLFR FRF.16 bundle. To configure a DLCI, include the dlci statement:
You can include this statement at the following hierarchy levels:
- [edit interfaces interface-name unit logical-unit-number]
- [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]
The DLCI identifier is a value from 16 through 1022. Numbers 1 through 15 are reserved for future use.
When you configure point-to-point connections, the maximum transmission unit (MTU) sizes on both sides of the connection must be the same.
Configuring Multicast-Capable DLCIs for MLFR FRF.16 Bundles
For link services interfaces only, you can configure multiple multicast-capable DLCIs for each MLFR FRF.16 bundle. A channelized interface, such as ls-1/1/1:0, denotes a single MLFR FRF.16 bundle. By default, Frame Relay connections assume unicast traffic. If your Frame Relay switch performs multicast replication, you can configure the link services connection to support multicast traffic by including the multicast-dlci statement:
You can include this statement at the following hierarchy levels:
- [edit interfaces interface-name unit logical-unit-number]
- [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]
The DLCI identifier is a value from 16 through 1022 that defines the Frame Relay DLCI over which the switch expects to receive multicast packets for replication.
You can configure multicast support only on point-to-multipoint link services connections. Multicast-capable DLCIs are not supported on multilink interfaces.
If keepalives are enabled, causing the interface to send Local Management Interface (LMI) messages during idle times, the number of possible DLCI configurations is limited by the MTU selected for the interface. For more information, see Configuring Keepalives on Link Services Physical Interfaces.
