To complete a multilink or link services interface configuration, you need to configure both the physical interface and the multilink or link services bundle. For multilink interfaces, you configure the link bundle on the logical unit. For link services interfaces, you configure the link bundle as a channel (see Figure 13). The physical interface is usually connected to networks capable of supporting MLPPP or MLFR (FRF.15 or FRF.16).
Figure 13: Multilink Interface Configuration
Using the topology in Figure 13 as an example, configure a multilink or link services bundle over a T1 connection (for which you have already configured the T1 physical interface) with the following additional configuration statements:
- unit 0 {
-
- family mlppp {
- bundle (ml-fpc/pic/port | ls-fpc/pic/port);
- }
- }
You do not need to configure an IP address on this link.
To configure a physical T1 link for MLFR FRF.16, include the following statements at the [edit interfaces t1-fpc/pic/port] hierarchy level:
- encapsulation multilink-frame-relay-uni-nni;
- unit 0 {
-
- family mlfr-uni-nni {
- bundle ls-fpc/pic/port:channel;
- }
- }
You do not need to configure an IP address or a DLCI on this link.
- address address {
- destination address;
- }
You can include these statements at the following hierarchy levels:
When you add statements such as mrru to the configuration and commit, the T1 interface becomes part of the multilink bundle.
 |
Note: For MLPPP and MLFR (FRF.15 and FRF.16) links, you must specify the subnet address as /32 or /30. Any other subnet designation is treated as a mismatch. |