Configuring MP by using a VT interface
When you configure MP by using a VT interface, you can do one of the following:
Binding physical interfaces to the VT interface by using the ppp mp virtual-template command. In this case, the configuration of authentication is optional. If the authentication is not configured, the system binds links according to the descriptor of the peer end. If the authentication is configured, the system binds links according to the username, the descriptor of the peer, or both.
Associating a username to the virtual template. After a user passes the authentication, the system searches for the VT interface associated to the username and bundles links according to the username and the descriptor of the peer. To ensure a successful link negotiation, configure the ppp mp command and two-way authentication (PAP, CHAP, MS-CHAP, or MS-CHAP-V2) on the bundled interfaces.
Configuration restrictions and guidelines
The ppp mp command and the ppp mp virtual-template command are mutually exclusive on an interface.
You must configure the interfaces to be bundled in the same way.
In actual use, you can configure one-way authentication, where one end associates physical interfaces to a VT interface and the other end searches for the VT interface by username.
A VT interface is intended to provide only one service, such as MP, L2TP, or PPPoE.
Configuration procedure
To configure MP by using a VT interface:
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Create a VT interface and enter VT interface view. | interface virtual-template number | N/A |
3. Set the interface description. | description text | Optional. By default, the description of a VT interface is interface name Interface. |
4. Set the MTU size of the interface. | mtu size | Optional. 1500 bytes by default. |
5. Configure the MP sort buffer size factor. | ppp mp sort-buffer-size size | Optional. 1 by default. The MP sort buffer size = The number of channels in the current MP bundle × size. |
6. Set the maximum number of links that can be used for transmitting multicast or broadcast packets supported on the VT interface. | broadcast-limit link number | Optional. 30 by default. |
7. Set the intended bandwidth for the VT interface. | bandwidth bandwidth-value | Optional. |
8. Restore the default settings for the VT interface. | default | Optional. |
9. Return to system view. | quit | N/A |
10. Associate a physical interface or a username to the VT interface. |
| Use either method. By default, a physical interface is not bound to any VT interface and operates in PPP mode. PPP authentication has no effect on the setup of MP. By default, an interface with PPP encapsulation enabled operates in PPP mode. By default, MP binding is supported in hardware. Software support for MP binding can only be configured on CPOS interfaces. |
11. Configure other MP parameters. | Optional. |
Configuring other optional parameters
When you configure other optional parameters, follow these guidelines:
The ppp mp max-bind, ppp mp min-bind, and ppp mp min-fragment commands can take effect on an MP bundle only after you re-enable all the physical interfaces in the MP bundle by executing the shutdown command and then the undo shutdown command.
The maximum number of links allowed in an MP bundle configured with the ppp mp max-bind command must be greater than or at least equal to the minimum number of links required in the MP bundle configured with the ppp mp min-bind command.
After you configure the undo ppp mp fragment enable command on an interface, the settings configured with the ppp mp lfi and ppp mp min-fragment commands become invalid on the interface.
When MP binding is based on descriptor only, users cannot be differentiated. To bind users to different MP bundles, set the binding mode to both.
When MP binding is based on authentication username only, peer devices cannot be differentiated. If an MP bundle involves multiple devices, set the binding mode to both.
For a VT interface, if a static route is used, specify the next hop rather than the outgoing interface. If the outgoing interface must be specified, make sure that the physical interfaces bound to the VT are active to ensure normal transport of packets.
For more information about configuring MP parameters in Dialer interface view, see "Configuring DCC."
To configure other optional parameters:
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Create an MP VT interface or enter dialer interface view. | interface { dialer | virtual-template } number | The interface virtual-template command also leads you to VT interface view. |
3. Set the binding mode. | ppp mp binding-mode { authentication | both | descriptor } | Optional. By default, MP binding is based on both the PPP authentication username and the descriptor. |
4. Set the maximum number of links allowed in an MP bundle. | ppp mp max-bind max-bind-num | Optional. 16 by default. This command is available in VT interface view and dialer interface view. Inappropriate use of this command can cause PPP performance degradation. Make sure you understand the impact of this command on your network before you use it. |
5. Set the minimum number of links required in an MP bundle. | ppp mp min-bind min-bind-num | Optional. This command is available only in dialer interface view. By default, the minimum number of links in an MP bundle is 0, that is, MP dialup depends on traffic detection. |
6. Configure the MP sort buffer size factor. | ppp mp sort-buffer-size size | Optional. 1 by default. The MP sort buffer size = The number of channels in the current MP bundle × size. |
7. Enable MP fragmentation. | ppp mp fragment enable | Optional. Enabled by default. |
8. Set the minimum size of MP fragments. | ppp mp min-fragment size | Optional. 128 bytes by default. |