HPE FlexNetwork MSR Series User manual

HPE FlexNetwork MSR Router Series
Comware 7 Layer 2 - WAN Access
Configuration Guide
Part number: 5200-2394
Software version: MSR-CMW710-R0411
Document version: 6W101-20161114

© Copyright 2016 Hewlett Packard Enterprise Development LP
The information contained herein is subject to change without notice. The only warranties for Hewlett Packard
Enterprise products and services are set forth in the express warranty statements accompanying such
products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett
Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.
Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or
copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software
Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s
standard commercial license.
Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard
Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise
website.
Acknowledgments
Intel®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks of Intel Corporation in the
United States and other countries.
Microsoft® and Windows® are trademarks of the Microsoft group of companies.
Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.
Java and Oracle are registered trademarks of Oracle and/or its affiliates.
UNIX® is a registered trademark of The Open Group.

i
Contents
Configuring PPP and MP ···································································1
PPP overview······························································································································1
PPP link establishment process ·······························································································1
PPP authentication················································································································2
PPP for IPv4 ························································································································2
PPP for IPv6 ························································································································3
MP overview ·······························································································································4
Compatibility information ···············································································································4
Feature and hardware compatibility ··························································································4
Command and hardware compatibility·······················································································4
Configuring PPP··························································································································5
PPP configuration task list·······································································································5
Enabling PPP encapsulation on an interface ··············································································5
Configuring PPP authentication································································································5
Configuring the polling feature ·································································································9
Configuring PPP negotiation·································································································· 10
Enabling IP header compression···························································································· 17
Enabling PPP link quality monitoring······················································································· 18
Enabling PPP accounting······································································································ 18
Configuring the nas-port-type attribute····················································································· 19
Configuring MP·························································································································· 19
MP configuration task list······································································································ 20
Configuring MP by using a VT interface··················································································· 20
Configuring MP through an MP-group interface········································································· 22
Configuring short sequence number header format negotiation···················································· 24
Configuring the MP endpoint descriptor··················································································· 24
Configuring LFI··················································································································· 25
Displaying and maintaining PPP and MP························································································ 25
PPP and MP configuration examples····························································································· 26
One-way PAP authentication configuration example ·································································· 26
Two-way PAP authentication configuration example ·································································· 28
One-way CHAP authentication configuration example································································ 30
IP address negotiation configuration examples ·········································································32
MP binding mode configuration examples················································································ 36
Configuring PPPoE·········································································44
Overview·································································································································· 44
Command and hardware compatibility···························································································· 44
PPPoE network structure············································································································· 44
Configuring the PPPoE server······································································································ 45
Configuring a PPPoE session································································································ 45
Setting the maximum number of PPPoE sessions ····································································· 46
Limiting the PPPoE access rate ····························································································· 47
Configuring the nas-port-id attribute························································································ 48
Configuring a VA pool ·········································································································· 49
Clearing PPPoE sessions ····································································································· 50
Configuring a PPPoE client·········································································································· 50
Configuring a dialer interface································································································· 51
Configuring a PPPoE session································································································ 52
Resetting a PPPoE session··································································································· 52
Displaying and maintaining PPPoE································································································ 53
Displaying and maintaining PPPoE server················································································ 53
Displaying and maintaining PPPoE client················································································· 53
PPPoE configuration examples····································································································· 54
PPPoE server configuration example······················································································ 54
PPPoE server IP address assignment through the local DHCP server configuration example ············55
PPPoE server IP address assignment through a remote DHCP server configuration example············ 56

ii
PPPoE server RADIUS-based IP address assignment configuration example·································57
PPPoE client in permanent mode configuration example ···························································· 60
PPPoE client in on-demand mode configuration example····························································61
PPPoE client in diagnostic mode configuration example ·····························································62
Configuration example for connecting a LAN to the Internet through an ADSL modem ·····················63
Configuring L2TP···········································································67
Overview·································································································································· 67
Typical L2TP networking······································································································· 67
L2TP message types and encapsulation structure····································································· 67
L2TP tunnel and session ······································································································ 68
L2TP tunneling modes and tunnel establishment process ··························································· 68
L2TP features····················································································································· 71
Protocols and standards······································································································· 73
Command and hardware compatibility···························································································· 73
L2TP configuration task list·········································································································· 73
Configuring basic L2TP capabilities······························································································· 74
Configuring an LAC···················································································································· 75
Configuring an LAC to initiate tunneling requests for a user························································· 75
Specifying LNS IP addresses ································································································ 75
Configuring the source IP address of L2TP tunnel packets·························································· 76
Enabling transferring AVP data in hidden mode ········································································ 76
Configuring AAA authentication on an LAC ·············································································· 76
Configuring an LAC to automatically establish an L2TP tunnel····················································· 77
Configuring an LNS···················································································································· 78
Creating a VT interface········································································································· 78
Configuring a VA pool ·········································································································· 79
Configuring an LNS to accept L2TP tunneling requests from an LAC ············································79
Configuring user authentication on an LNS··············································································· 80
Configuring AAA authentication on an LNS ·············································································· 81
Configuring IMSI/SN binding authentication·············································································· 81
Configuring optional L2TP parameters ··························································································· 82
Configuring L2TP tunnel authentication ··················································································· 82
Setting the Hello interval······································································································· 83
Enabling session flow control································································································· 83
Setting the DSCP value of L2TP packets················································································· 84
Assigning a tunnel peer to a VPN··························································································· 84
Setting the TSA ID of the LTS································································································ 84
Displaying and maintaining L2TP·································································································· 85
L2TP configuration examples ······································································································· 85
Configuration example for NAS-initiated L2TP tunnel································································· 85
Configuration example for client-initiated L2TP tunnel ································································ 87
Configuration example for LAC-auto-initiated L2TP tunnel··························································· 89
Troubleshooting L2TP················································································································· 91
Configuring HDLC··········································································92
Overview·································································································································· 92
Compatibility information ············································································································· 92
Feature and hardware compatibility ························································································ 92
Command and hardware compatibility····················································································· 92
Enabling HDLC encapsulation on an interface················································································· 93
Configuring link status polling······································································································· 93
Displaying and maintaining HDLC································································································· 93
HDLC configuration example········································································································ 94
Network requirements·········································································································· 94
Configuration procedure ······································································································· 94
Verifying the configuration····································································································· 94
Configuring HDLC link bundling·························································96
Overview·································································································································· 96
Basic concepts ··················································································································· 96
States of member interfaces·································································································· 96

iii
Load balancing modes ········································································································· 98
Compatibility information ············································································································· 98
Feature and hardware compatibility ························································································ 98
Command and hardware compatibility····················································································· 98
Configuring an HDLC link bundle interface······················································································ 99
Configuration restrictions and guidelines·················································································· 99
Configuration procedure ······································································································· 99
Assigning an interface to an HDLC link bundle··············································································· 100
Configuration restrictions and guidelines················································································ 100
Configuration procedure ····································································································· 101
Displaying and maintaining HDLC link bundling ············································································· 101
HDLC link bundling configuration example···················································································· 102
Network requirements········································································································ 102
Configuration procedure ····································································································· 102
Verifying the configuration··································································································· 103
Configuring ISDN········································································· 104
Overview································································································································ 104
ISDN interfaces················································································································· 104
ISDN protocol stacks ········································································································· 105
ISDN application scenarios ································································································· 105
ISDN PRI configuration prerequisites··························································································· 106
ISDN configuration task list········································································································ 106
Setting the ISDN switch type on an ISDN interface········································································· 107
Setting the ISDN functionality of an ISDN interface········································································· 108
Configuring SPID parameters for the NI switch type········································································ 108
Configuring SPID assignment······························································································ 108
Configuring the TSPID timer and INFORMATION retransmission··············································· 109
Enabling NIT mode for NI-type switches incapable of SPID negotiation ······································· 110
Configuring Q.931 negotiation parameters···················································································· 110
Configuring Q.931 call control parameters ···················································································· 112
Configuring B-channel selection··························································································· 112
Configuring calling number verification for incoming calls·························································· 113
Configuring called-number verification for incoming calls ·························································· 113
Configuring ISDN calling number identification········································································ 114
Configuring the Q.921 operating parameters················································································· 114
Configuring the data link type of a BRI interface······································································ 114
Configuring per-channel TEI assignment on a BRI interface ······················································ 115
Configuring the leased line service for an ISDN BRI interface ···················································· 115
Enabling permanent Q.921 link connectivity on an ISDN BRI interface ········································ 116
Enabling persistent Layer 1 activation on a BRI interface·························································· 116
Configuring a BRI interface to supply line power······································································ 117
Configuring the sliding window size on an ISDN BRI interface ··················································· 117
Configuring the sliding window size on an ISDN PRI interface ··················································· 117
Displaying and maintaining ISDN settings····················································································· 118
ISDN configuration examples ····································································································· 118
ISDN PRI configuration example·························································································· 118
NI-enabled ISDN BRI configuration example ·········································································· 120
Troubleshooting······················································································································· 121
Configuring ATM·········································································· 123
Overview································································································································ 123
ATM connections and ATM switching···················································································· 123
ATM architecture··············································································································· 124
ATM service types············································································································· 125
ATM applications··············································································································· 125
ATM OAM························································································································ 126
ATM configuration task list········································································································· 127
Configuring an ATM interface····································································································· 127
Configuring a PVC ··················································································································· 127
Configuring a PVC group··········································································································· 128
Configuring the ATM AAL5 encapsulation type·············································································· 128

iv
Configuring the ATM service type································································································ 129
Configuring applications carried by ATM······················································································· 130
Configuring a VE interface ·································································································· 131
Configuring IPoA··············································································································· 132
Configuring IPoEoA ··········································································································· 133
Configuring PPPoA············································································································ 134
Configuring PPPoEoA········································································································ 134
Configuring VP policing············································································································· 135
Re-marking the CLP flag value of ATM cells·················································································· 136
Configuring ATM OAM functions································································································· 137
Displaying and maintaining ATM································································································· 137
ATM configuration examples······································································································ 138
IPoA configuration example································································································· 138
IPoEoA configuration example····························································································· 139
PPPoA configuration example ····························································································· 141
PPPoEoA configuration example·························································································· 142
ATM PVC transmission priority configuration example······························································ 144
Troubleshooting ATM················································································································ 145
Link state error in IPoA application························································································ 145
Link report error in PPPoA application··················································································· 145
Ping failure······················································································································· 145
PVC state is down when ATM interface state is up ·································································· 145
Ping failure after PPPoA configuration··················································································· 146
Managing a modem······································································ 147
Feature and hardware compatibility····························································································· 147
Modem management configuration task list··················································································· 147
Configuring modem services on a user line··················································································· 147
Setting the answer timeout timer································································································· 148
Setting the modem answer mode································································································ 149
Enabling a modem to obtain caller numbers·················································································· 149
Enabling modem callback·········································································································· 150
Issuing an AT command to a modem··························································································· 150
Setting the country code of a modem··························································································· 151
Modem management configuration example ················································································· 151
Network requirements········································································································ 151
Configuration procedure ····································································································· 151
Verifying the configuration··································································································· 152
Troubleshooting modem faults···································································································· 152
Managing a 3G/4G modem ···························································· 153
Configuration restrictions and guidelines ······················································································ 153
3G modem management configuration task list·············································································· 153
4G modem management configuration task list·············································································· 154
Configuring a cellular interface for a 3G modem············································································· 154
Configuring a cellular interface for a 4G modem············································································· 154
Configuring an Eth-channel interface for a 4G modem ···································································· 155
Configuring an IP address for an Eth-channel interface of a 4G modem ············································· 155
Configuring a 3G/4G network ····································································································· 156
Configuring parameter profiles···································································································· 157
Configuring a parameter profile···························································································· 157
Specifying the primary and backup profiles············································································· 158
Configuring PIN verification········································································································ 158
Configuring DM ······················································································································· 159
Setting RSSI thresholds for a 3G/4G modem················································································· 159
Issuing a configuration directive to a 3G/4G modem ······································································· 160
Configuring automatic reboot······································································································ 160
Configuring manual reboot········································································································· 161
Displaying and maintaining 3G/4G modem information···································································· 161
3G/4G modem management configuration examples······································································ 162
3G modem management configuration example······································································ 162
4G modem management configuration example······································································ 163

v
Troubleshooting 3G and 4G modem management ········································································· 163
3G/4G modem failure················································································································ 163
Configuring DDR·········································································· 165
Overview································································································································ 165
Interfaces in DDR·············································································································· 165
DDR implementations ········································································································ 165
DDR types ······················································································································· 167
Command and hardware compatibility·························································································· 167
DDR configuration task lists ······································································································· 168
Packet-triggered DDR configuration task list··········································································· 168
Auto-dial DDR configuration task list····················································································· 168
Route-triggered DDR configuration task list············································································ 169
Configuring basic settings for DDR······························································································ 169
Configuring physical interfaces ···························································································· 169
Configuring link layer/network/routing protocols on the dialup interface········································ 170
Associating a dial rule with a dialup interface················································································· 170
Configuring traditional DDR········································································································ 171
Configuring an interface to place calls··················································································· 171
Configuring an interface to receive calls················································································· 172
Configuring bundle DDR············································································································ 173
Configuring a dialer interface to place calls············································································· 173
Configuring a dialer interface to receive calls·········································································· 174
Configuring attributes for a dialup interface ··················································································· 175
Configuring MP for DDR············································································································ 176
Configuration restrictions and guidelines················································································ 177
Configuration procedure ····································································································· 177
Configuring PPP callback ·········································································································· 177
Configuring the callback client ····························································································· 178
Configuring the callback server···························································································· 179
Configuring ISDN caller number callback······················································································ 180
Overview ························································································································· 180
Configuration restrictions and guidelines················································································ 181
Configuring a callback server by using traditional DDR····························································· 181
Configuring a callback server by using bundle DDR································································· 182
Configuring auto-dial················································································································· 182
Configuring dynamic route backup through DDR············································································ 182
Creating a dynamic route backup group················································································· 183
Assigning a dialup interface to a dynamic route backup group ··················································· 183
Setting the secondary link disconnection delay ······································································· 184
Setting the warm-up timer for dynamic route backup································································ 184
Disconnecting a dialup link········································································································· 184
Displaying and maintaining DDR································································································· 185
DDR configuration examples······································································································ 185
PSTN-based traditional DDR configuration example ································································ 185
PSTN-based bundle DDR configuration example ···································································· 187
ISDN-based traditional DDR configuration example ································································· 191
ISDN-based bundle DDR configuration example ····································································· 193
MP for DDR configuration example······················································································· 196
ISDN caller number callback configuration example································································· 198
Router-to-router PPP callback configuration example······························································· 199
Router-to-PC PPP callback configuration example··································································· 202
Windows server-to-router PPP callback configuration example ·················································· 204
Configuration example for circular dial string backup and Internet access ···································· 207
Dynamic route backup for traditional DDR configuration example··············································· 212
Dynamic route backup for bundle DDR configuration example ··················································· 214
Configuration example for dynamic route backup for multiple networks········································ 217
Troubleshooting······················································································································· 220
Failure to establish a dialup connection ················································································· 220
Ping failure······················································································································· 220

vi
Configuring Frame Relay ······························································· 221
Overview································································································································ 221
Frame Relay interface types································································································ 221
Virtual circuit ···················································································································· 222
DLCI······························································································································· 222
Frame Relay address mapping ···························································································· 223
LMI protocol ····················································································································· 223
Application scenarios········································································································· 225
Feature and hardware compatibility····························································································· 225
Frame Relay configuration task list······························································································ 226
Configuring basic DTE-side Frame Relay ····················································································· 226
Configuring basic DCE-side Frame Relay····················································································· 227
Configuring local Frame Relay virtual circuits ················································································ 227
Configuration restrictions and guidelines················································································ 228
Configuration procedure ····································································································· 228
Configuring Frame Relay address mapping··················································································· 228
Configuring static address-to-DLCI maps··············································································· 229
Configuring dynamic IPv4 address mapping··········································································· 229
Configuring dynamic IPv6 address mapping··········································································· 229
Configuring Frame Relay subinterfaces························································································ 229
Configuring Frame Relay IPHC··································································································· 230
Configuration restrictions and guidelines················································································ 231
Configuring Frame Relay IPHC on an interface······································································· 231
Configuring Frame Relay IPHC on a virtual circuit ··································································· 231
Configuring Frame Relay STAC compression················································································ 232
Configuration restrictions and guidelines················································································ 232
Configuring Frame Relay STAC compression on a virtual circuit ················································ 232
Configuring Frame Relay FRF.12 fragmentation ············································································ 233
Configuration restrictions and guidelines················································································ 233
Configuring Frame Relay FRF.12 fragmentation on an interface················································· 233
Enabling SNMP notifications for Frame Relay················································································ 233
Displaying and maintaining Frame Relay······················································································ 234
Frame Relay configuration example····························································································· 235
Network requirements········································································································ 235
Configuration procedure ····································································································· 235
Verifying the configuration··································································································· 236
Troubleshooting Frame Relay····································································································· 237
The physical layer is down·································································································· 237
The physical layer is already up, but the link layer protocol is down············································· 237
The link layer protocol is up, but the peer cannot be pinged······················································· 237
Configuring Multilink Frame Relay···················································· 238
Feature and hardware compatibility····························································································· 238
MFR configuration task list········································································································· 238
Configuring an MFR bundle ······································································································· 239
Configuring an MFR bundle link·································································································· 239
Displaying and maintaining MFR································································································· 240
MFR configuration example ······································································································· 240
Network requirements········································································································ 240
Configuration procedure ····································································································· 241
Verifying the configuration··································································································· 241
Document conventions and icons ···················································· 243
Conventions···························································································································· 243
Network topology icons ············································································································· 244
Support and other resources··························································· 245
Accessing Hewlett Packard Enterprise Support·············································································· 245
Accessing updates··················································································································· 245
Websites ························································································································· 246
Customer self repair ·········································································································· 246

vii
Remote support ················································································································ 246
Documentation feedback ···································································································· 246
Index························································································· 248

1
Configuring PPP and MP
PPP overview
Point-to-Point Protocol (PPP) is a point-to-point link layer protocol. It provides user authentication,
supports synchronous/asynchronous communication, and allows for easy extension.
PPP includes the following protocols:
•
Link control protocol (LCP)—Establishes, tears down, and monitors data links.
•
Network control protocol (NCP)—Negotiates the packet format and type for data links.
•
Authentication protocols—Authenticate users. Protocols include the following:
Password Authentication Protocol (PAP).
Challenge Handshake Authentication Protocol (CHAP).
Microsoft CHAP (MS-CHAP).
Microsoft CHAP Version 2 (MS-CHAP-V2).
PPP link establishment process
Figure 1 shows the PPP link establishment process.
Figure 1 PPP link establishment process
1. Initially, PPP is in Link Dead phase. After the physical layer goes up, PPP enters the Link
Establishment phase (Establish).
2. In the Link Establishment phase, the LCP negotiation is performed. The LCP configuration
options include Authentication-Protocol, Async-Control-Character-Map (ACCM),
Maximum-Receive-Unit (MRU), Magic-Number, Protocol-Field-Compression (PFC),
Address-and-Control-Field-Compression (ACFC), and MP.
If the negotiation fails, LCP reports a Fail event, and PPP returns to the Dead phase.
If the negotiation succeeds, LCP enters the Opened state and reports an Up event,
indicating that the underlying layer link has been established. At this time, the PPP link is not
established for the network layer, and network layer packets cannot be transmitted over the
link.
3. If authentication is configured, the PPP link enters the Authentication phase, where PAP, CHAP,
MS-CHAP, or MS-CHAP-V2 authentication is performed.
If the client fails to pass the authentication, LCP reports a Fail event and enters the Link
Termination phase. In this phase, the link is torn down and LCP goes down.
If the client passes the authentication, LCP reports a Success event.
4. If a network layer protocol is configured, the PPP link enters the Network-Layer Protocol phase
for NCP negotiation, such as IPCP negotiation and IPv6CP negotiation.
Dead Establish
Up Authenticate Opened
Terminate Network
Down
Fail Fail Success
/None
Closing

2
If the NCP negotiation succeeds, the link goes up and becomes ready to carry negotiated
network-layer protocol packets.
If the NCP negotiation fails, NCP reports a Down event and enters the Link Termination
phase.
If the interface is configured with an IP address, the IPCP negotiation is performed. IPCP
configuration options include IP addresses and DNS server IP addresses. After the IPCP
negotiation succeeds, the link can carry IP packets.
5. After the NCP negotiation is performed, the PPP link remains active until either of the following
events occurs:
Explicit LCP or NCP frames close the link.
Some external events take place (for example, the intervention of a user).
For more information about PPP, see RFC 1661.
PPP authentication
PPP supports the following authentication methods:
•
PAP—PAP is a two-way handshake authentication protocol using the username and password.
PAP sends username/password pairs in plain text over the network. If authentication packets
are intercepted in transit, network security might be threatened. For this reason, it is suitable
only for low-security environments.
•
CHAP—CHAP is a three-way handshake authentication protocol.
CHAP transmits usernames but not passwords over the network. It transmits the result
calculated from the password and random packet ID by using the MD5 algorithm. It is more
secure than PAP. The authenticator may or may not be configured with a username. As a best
practice, configure a username for the authenticator, which makes it easier for the peer to verify
the identity of the authenticator.
•
MS-CHAP—MS-CHAP is a three-way handshake authentication protocol.
MS-CHAP differs from CHAP as follows:
MS-CHAP uses CHAP Algorithm 0x80.
MS-CHAP provides authentication retry. If the peer fails authentication, it is allowed to
retransmit authentication information to the authenticator for reauthentication. The
authenticator allows a peer to retransmit a maximum of three times.
•
MS-CHAP-V2—MS-CHAP-V2 is a three-way handshake authentication protocol.
MS-CHAP-V2 differs from CHAP as follows:
MS-CHAP-V2 uses CHAP Algorithm 0x81.
MS-CHAP-V2 provides two-way authentication by piggybacking a peer challenge on the
Response packet and an authenticator response on the Acknowledge packet.
MS-CHAP-V2 supports authentication retry. If the peer fails authentication, it is allowed to
retransmit authentication information to the authenticator for reauthentication. The
authenticator allows a peer to retransmit a maximum of three times.
MS-CHAP-V2 supports password change. If the peer fails authentication because of an
expired password, it will send the new password entered by the user to the authenticator for
reauthentication.
PPP for IPv4
On IPv4 networks, PPP negotiates the IP address and DNS server address during IPCP negotiation.
IP address negotiation
IP address negotiation enables one end to assign an IP address to the other.

3
An interface can act as a client or a server during IP address negotiation:
•
Client—Obtains an IP address from the server. Use the client mode when the device accesses
the Internet through an ISP.
•
Server—Assigns an IP address to the client. Before you configure the IP address of the server,
you must perform one of the following tasks:
Configure a local address pool and associate the pool with the ISP domain.
Specify an IP address or an address pool for the client on the interface.
When IP address negotiation is enabled on a client, the server selects an IP address for the client in
the following sequence:
1. If the AAA server configures an IP address or address pool for the client, the server selects that
IP address or an IP address from the pool. The IP address or address pool is configured on the
AAA server instead of the PPP server. For information about AAA, see Security Configuration
Guide.
2. If an address pool is associated with the ISP domain used during client authentication, the
server selects an IP address from the pool.
3. If an IP address or address pool is specified for the client on the interface of the server, the
server selects that IP address or an IP address from that pool.
DNS server address negotiation
IPCP negotiation can determine the DNS server IP address.
When the device is connected to a host, configure the device as the server to assign the DNS server
IP address to the host.
When the device is connected to an ISP access server, configure the device as the client. Then, the
device can obtain the DNS server IP address from the ISP access server.
PPP for IPv6
On IPv6 networks, PPP negotiates only the IPv6 interface identifier instead of the IPv6 address and
IPv6 DNS server address during IPv6CP negotiation.
IPv6 address assignment
PPP cannot negotiate the IPv6 address.
The client can get an IPv6 global unicast address through the following methods:
•
Method 1—The client obtains an IPv6 prefix in an RA message. The client then generates an
IPv6 global unicast address by combining the IPv6 prefix and the negotiated IPv6 interface
identifier. The IPv6 prefix in the RA message is determined in the following sequence:
IPv6 prefix authorized by AAA.
RA prefix configured on the interface.
Prefix of the IPv6 global unicast address configured on the interface.
For information about the ND protocol, see Layer 3—IP Services Configuration Guide.
•
Method 2—The client requests an IPv6 global unicast address through DHCPv6. The server
assigns an IPv6 address to the client from the address pool authorized by AAA. If no
AAA-authorized address pool exists, DHCPv6 uses the address pool that matches the server's
IPv6 address to assign an IPv6 address to the client. For information about DHCPv6, see Layer
3—IP Services Configuration Guide.
•
Method 3—The client requests prefixes through DHCPv6 and assigns them to downstream
hosts. The hosts then uses the prefixes to generate global IPv6 addresses. This method uses
the same principle of selecting address pools as method 2.
The device can assign a host an IPv6 address in either of the following ways:

4
•
When the host connects to the device directly or through a bridge device, the device can use
method 1 or method 2.
•
When the host accesses the device through a router, the device can use method 3 to assign an
IPv6 prefix to the router. The router assigns the prefix to the host to generate an IPv6 global
unicast address.
IPv6 DNS server address assignment
On IPv6 networks, two methods are available for the IPv6 DNS address assignment:
•
AAA authorizes the IPv6 DNS address and assigns this address to the host through RA
messages.
•
The DHCPv6 client requests an IPv6 DNS address from the DHCPv6 server.
MP overview
Multilink PPP (MP) allows you to bind multiple PPP links into one MP bundle for increasing
bandwidth. If a packet is larger than the minimum packet size for fragmentation, MP fragments the
packet and distributes the fragments across multiple PPP links to the peer. The peer reassembles
them into one packet and passes the packet to the network layer.
In addition to increasing bandwidth, MP also provides link-layer load sharing, which can implement
backup. MP fragmentation can reduce transmission delay, especially on low-speed links.
MP is available to all physical or virtual interfaces with PPP encapsulation enabled, including serial,
ISDN BRI/PRI, and PPPoX (PPPoE or PPPoA) interfaces. In MP configuration, as a best practice,
include only one type of interfaces in an MP bundle.
Compatibility information
Feature and hardware compatibility
This feature is supported only on Layer 2 Ethernet ports on the following modules:
•
AM.
•
AS.
•
ASE.
•
BS.
•
CE3.
•
CPOS.
•
E1.
•
E1-F.
•
POS.
•
SAE.
•
T1.
•
T1-F.
Command and hardware compatibility
Commands and descriptions for centralized devices apply to the following routers:
•
MSR1002-4/1003-8S.

5
•
MSR2003.
•
MSR2004-24/2004-48.
•
MSR3012/3024/3044/3064.
•
MSR954(JH296A/JH297A/JH298A/JH299A/JH373A).
•
MSR958(JH300A/JH301A).
Commands and descriptions for distributed devices apply to MSR4060 and MSR4080 routers.
Configuring PPP
PPP configuration task list
Tasks at a glance
(Required.) Enabling PPP encapsulation on an interface
(Optional.) Configuring PPP authentication
(Optional.) Configuring the polling feature
(Optional.) Configuring PPP negotiation
(Optional.) Enabling IP header compression
(Optional.) Enabling PPP link quality monitoring
(Optional.) Enabling PPP accounting
(Optional.) Configuring the nas-port-type attribute
Enabling PPP encapsulation on an interface
Step
Command
Remarks
1. Enter system view. system-view N/A
2. Enter interface view. interface interface-type
interface-number N/A
3.
Enable PPP encapsulation
on the interface. link-protocol ppp
By default, all
interfaces except
Ethernet interfaces, VLAN
interfaces, and ATM interfaces
use PPP as the link layer protocol.
Configuring PPP authentication
You can configure several authentication modes simultaneously. In LCP negotiation, the
authenticator negotiates with the peer in the sequence of configured authentication modes until the
LCP negotiation succeeds. If the response packet from the peer carries a recommended
authentication mode, the authenticator directly uses the authentication mode if it finds the mode
configured.
Configuring PAP authentication
To configure the authenticator:

6
Step
Command
Remarks
1. Enter system view. system-view N/A
2. Enter interface view. interface interface-type
interface-number N/A
3. Configure the authenticator
to authenticate the peer by
using PAP. ppp authentication-mode pap
[ [ call-in ] domain isp-name ] By default, PPP authentication is
disabled.
4.
Configure local or remote
AAA authentication.
For local AAA authentication, the
username and password of the
peer must be configured on the
authenticator.
For remote AAA authentication,
the username and
password of
the peer must be configured on
the remote AAA server.
For more information about AAA
authentication, see Security
Configuration Guide.
The username and password
configured for the peer must be
the same as those configured on
the peer.
To configure the peer:
Step
Command
Remarks
1. Enter system view. system-view N/A
2. Enter interface view. interface interface-type
interface-number N/A
3. Configure the PAP username
and password sent from the
peer to the authenticator
when the pe
er is
authenticated by the
authenticator by using PAP.
ppp pap local-user username
password { cipher | simple }
string
By default, when being
authenticated by the authenticator
by using PAP, the peer sends null
username and password to the
authenticator.
For security purposes, the
password specified
in plaintext
form and ciphertext form will be
stored in encrypted form.
Configuring CHAP authentication
Depending on whether the authenticator is configured with a username, the configuration of CHAP
authentication includes the following types:
•
Configuring CHAP authentication when the authenticator name is configured
To configure the authenticator:
Step
Command
Remarks
1. Enter system view. system-view N/A
2. Enter interface view. interface interface-type
interface-number N/A
3. Configure the authenticator
to authenticate the peer by
using CHAP. ppp authentication-mode chap
[ [ call-in ] domain isp-name ] By default, PPP authentication is
disabled.
4. Configure a username for the
CHAP authenticator. ppp chap user username
The default setting is null.
The username you configure for
the authenticator must be the
same as the local username you

7
Step
Command
Remarks
configure for the authenticator on
the peer.
5.
Configure local or remote
AAA authentication.
For local AAA authentication, the
username and password of the
peer must be configured on the
authenticator.
For remote AAA authentication,
the username and password of
the peer must be configured on
the remote AAA server.
For more information about AAA
authentication, see Security
Configuration Guide.
The username configured for the
peer must be the same as that
configured on the peer.
The passwords configured for the
authenticator and peer must be
the same.
To configure the peer:
Step
Command
Remarks
1. Enter system view. system-view N/A
2. Enter interface view. interface interface-type
interface-number N/A
3. Configure a username for
the CHAP peer. ppp chap user username
The default setting is null.
The username you configure for
the peer here must be the same
as the local username you
configure for the peer
on the
authenticator.
4.
Configure local or remote
AAA authentication.
For local AAA authentication, the
username and password of the
authenticator must be configured on
the peer.
For remote AAA authentication, the
username and password of the
authenticator must be configured on
the remote AAA server.
For more information about AAA
authentication, see Security
Configuration Guide.
The username configured for the
authenticator must be the same
as that configured on the
authenticator.
The passwords configured for
the authenticator and peer must
be the same.
•
Configuring CHAP authentication when no authenticator name is configured
To configure the authenticator:
Step
Command
Remarks
1. Enter system view. system-view N/A
2. Enter interface view. interface interface-type
interface-number N/A
3. Configure the authenticator to
authenticate the peer by using
CHAP. ppp authentication-mode chap
[ [ call-in ] domain isp-name ]
By default, PPP
authentication is disabled.
4.
Configure local or remote AAA
authentication.
For local AAA authentication, the
username and password of the
peer
must be configured on the
authenticator.
For remote AAA authentication, the
The username configured
for the peer must be the
same as that configured on
the peer.
The passwords configured

8
Step
Command
Remarks
username and password of the
peer must be configured on the
remote AAA server.
For more information about AAA
authentication, see Security
Configuration Guide.
for the authenticator and
peer must be the same.
To configure the peer:
Step
Command
Remarks
1. Enter system view. system-view N/A
2. Enter interface view. interface interface-type
interface-number N/A
3.
Configure a username for
the CHAP peer. ppp chap user username
The default setting is null.
The username you configure on
the peer must be the same as the
local username you configure for
the peer on the authenticator.
4.
Set the CHAP
authentication password. ppp chap password { cipher |
simple } string
The default setting is null.
The password you set on the peer
must be the same as the
password you set for the peer on
the authenticator.
For security purposes, the
password specified in plaintext
form and ciphertext form will be
stored in encrypted form.
Configuring MS-CHAP or MS-CHAP-V2 authentication
When you configure MS-CHAP or MS-CHAP-V2 authentication, follow these guidelines:
•
The device can only act as an authenticator for MS-CHAP or MS-CHAP-V2 authentication.
•
L2TP supports only MS-CHAP authentication.
•
MS-CHAP-V2 authentication supports password change only when using RADIUS.
To configure MS-CHAP or MS-CHAP-V2 authentication when the authenticator name is configured:
Step
Command
Remarks
1. Enter system view. system-view N/A
2. Enter interface view. interface interface-type
interface-number N/A
3.
Configure the authenticator
to authenticate the peer by
using MS-
CHAP or
MS-CHAP-V2.
ppp authentication-mode
{ ms-chap | ms-chap-v2 }
[ [ call-in ] domain isp-name ] By default, PPP authentication is
disabled.
4. Configure a username for the
MS-CHAP or MS-CHAP-V2
authenticator. ppp chap user username
The username for the
authenticator must be the same
on the local and peer devices.
5.
Configure local or remote
AAA authentication.
For local AAA authentication, the
username and password of the
peer must be configured on the
authenticator.
The username and password of
the
peer configured on the
authenticator or remote AAA
server must be the same as those

9
Step
Command
Remarks
For remote AAA authentication,
the username and password of
the peer must be configured on
the remote AAA server.
For more information about AAA
authentication, see Security
Configuration Guide.
configured on the peer.
To configure MS-CHAP or MS-CHAP-V2 authentication when no authenticator name is configured:
Step
Command
Remarks
1. Enter system view.system-view N/A
2. Enter interface view. interface interface-type
interface-number N/A
3.
Configure the
authenticator to
authenticate the
peer by using
MS-
CHAP or
MS-CHAP-V2.
ppp authentication-mode { ms-chap |
ms-chap-v2 } [ [ call-in ] domain
isp-name ]
By default, PPP authentication is
disabled.
4.
Configure local or
remote AAA
authentication.
For local AAA authentication
, the
username and password of the peer
must be configured on the authenticator.
For remote AAA authentication
, the
username and password of the peer
must be configured on the remote AAA
server.
For more information about AAA
authentication, see Security
Configuration Guide.
The username and password of the
peer configured on the
authenticator or remote AAA server
must be the same as those
configured on the peer.
Configuring the polling feature
The polling feature checks PPP link state.
On an interface that uses PPP encapsulation, the link layer sends keepalives at keepalive intervals
to detect the availability of the peer. If the interface fails to receive keepalives when the keepalive
retry limit is reached, it tears down the link and reports a link layer down event.
To set the keepalive retry limit, use the timer-hold retry command.
On a slow link, increase the keepalive interval to prevent false shutdown of the interface. This
situation might occur when keepalives are delayed because a large packet is being transmitted on
the link.
The keepalive interval must be smaller than the negotiation timeout time.
To disable sending of keepalives, set the keepalive interval to 0.
To configure the polling feature:
Step
Command
Remarks
1. Enter system view.system-view N/A
2. Enter interface view. interface interface-type
interface-number N/A

10
Step
Command
Remarks
3. Set the keepalive interval. timer-hold secondsThe default setting is 10 seconds.
4. Set the keepalive retry limit. timer-hold retry retries The default setting is 5.
Configuring PPP negotiation
PPP negotiation includes the following parameters:
•
Negotiation timeout time.
•
IP address negotiation.
•
IP segment match.
•
DNS server IP address negotiation.
•
ACCM negotiation.
•
ACFC negotiation.
•
PFC negotiation.
Configuring the PPP negotiation timeout time
The device starts the PPP negotiation timeout timer after sending a packet. If no response is
received before the timer expires, the device sends the packet again.
If two ends of a PPP link vary greatly in the LCP negotiation packet processing rate, configure the
LCP negotiation delay timer on the end with a higher processing rate. The LCP negotiation delay
timer prevents frequent LCP negotiation packet retransmissions. After the physical layer comes up,
PPP starts LCP negotiation when the delay timer expires. If PPP receives LCP negotiation packets
before the delay timer expires, it starts LCP negotiation immediately.
To configure the PPP negotiation timeout time:
Step
Command
Remarks
1. Enter system view. system-view N/A
2. Enter interface view. interface interface-type
interface-number N/A
3. Configure the negotiation
timeout time. ppp timer negotiate seconds The default setting is 3 seconds.
4.
(Optional.) Configure the
LCP negotiation delay timer. ppp lcp delay milliseconds By default
, PPP starts LCP
negotiation immediately after the
physical layer is up.
Configuring IP address negotiation
To configure the device as the client:
Step
Command
Remarks
1. Enter system view. system-view N/A
2. Enter interface view. interface interface-type
interface-number N/A
3. Enable
IP address
negotiation. ip address ppp-negotiate
By default, IP address negotiation
is not enabled.
T
his command is mutually
exclusive with the ip address
command. For more information

11
Step
Command
Remarks
about the ip address command,
see Layer 3—
IP Services
Command Reference.
Configure the server to assign an IP address to a client by using the following methods:
•
Method 1: Specify an IP address for the client on the server interface.
•
Method 2: Specify a PPP or DHCP address pool on the server interface.
•
Method 3: Associate a PPP or DHCP address pool with an ISP domain.
For clients requiring no authentication, you can use either method 1 or method 2, but not both.
For clients requiring authentication, you can use one or more of the three methods, but cannot use
method 1 and method 2 at the same time. When multiple methods are configured, method 3 takes
precedence over method 1 or method 2.
PPP supports IP address assignment from a PPP or DHCP address pool. If you use a pool name that
identifies both a PPP address pool and a DHCP address pool, the system uses the PPP address
pool.
To configure the device as the server (Method 1):
Step
Command
Remarks
1. Enter system view. system-view N/A
2. Enter interface view. interface interface-type
interface-number N/A
3.
Configure the interface to
assign an IP address to the
peer. remote address ip-address
By default, an interface does
not assign an IP address to the
peer.
4. Configure an IP address for the
interface. ip address ip-address
By default, no IP address is
configured on an interface.
To configure the device as the server (Method 2: Specify a PPP address pool):
Step
Command
Remarks
1. Enter system view. system-view N/A
2. Configure a PPP address pool. ip pool pool-name
start-ip-address [ end-ip-address ]
[ group group-name ]
By default,
no PPP address
pool is configured.
3.
(Optional.) Configure a
gateway address for the PPP
address pool.
ip pool pool-name gateway
ip-address [ vpn-instance
vpn-instance-name ]
By default, the PPP address
pool is not configured with a
gateway address.
4. (Optional.) Configure a PPP
address pool route.
ppp ip-pool route ip-address
{ mask-length | mask }
[ vpn-instance
vpn-instance-name ]
By default, no PPP address
pool route exists.
The destination network of the
PPP address pool route must
include the PPP address pool.
5. Enter interface view. interface interface-type
interface-number N/A
6. Configure
the interface to
assign an IP address from the
configured PPP address pool
to the peer. remote address pool pool-name
By default, an interface does
not assign an IP address to the
peer.