HP MSR SERIES User manual
HP MSR Router Series
Layer 2 - WAN Access
Configuration Guide(V7)
Part number: 5998-7721b
Software version: CMW710-R0304
Document version: 6PW104-20150914
i
Legal and notice information
© Copyright 2015 Hewlett-Packard Development Company, L.P.
No part of this documentation may be reproduced or transmitted in any form or by any means without
prior written consent of Hewlett-Packard Development Company, L.P.
The information contained herein is subject to change without notice.
HEWLETT-PACKARD COMPANY MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS
MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard shall not be liable for errors contained
herein or for incidental or consequential damages in connection with the furnishing, performance, or use
of this material.
The only warranties for HP 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. HP shall not be liable for technical or editorial errors or omissions contained herein.
i
Contents
Configuring PPP and MP ············································································································································· 1
PPP overview······································································································································································1
PPP link establishment process ································································································································1
PPP authentication ····················································································································································2
PPP for IPv4 ·······························································································································································3
PPP for IPv6 ·······························································································································································3
MP overview ······································································································································································4
Compatibility information·················································································································································4
Feature and hardware compatibility······················································································································4
Command and hardware compatibility·················································································································5
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 ······································································································································ 19
Configuring the nas-port-type attribute················································································································ 19
Configuring MP ······························································································································································ 20
MP configuration task list······································································································································ 20
Configuring MP by using a VT interface············································································································· 21
Configuring MP through an MP-group interface································································································ 23
Configuring short sequence number header format negotiation ····································································· 24
Configuring the MP endpoint descriptor············································································································· 25
Configuring LFI······················································································································································· 25
Displaying and maintaining PPP and MP···················································································································· 26
PPP and MP configuration examples ··························································································································· 27
One-way PAP authentication configuration example ························································································ 27
Two-way PAP authentication configuration example ························································································ 29
One-way CHAP authentication configuration example ···················································································· 31
IP address negotiation configuration examples ································································································· 33
MP binding mode configuration examples········································································································· 37
Configuring PPPoE ·····················································································································································45
Overview········································································································································································· 45
PPPoE network structure················································································································································· 45
Command and hardware compatibility ······················································································································ 46
Configuring the PPPoE server········································································································································ 46
Configuring a PPPoE session································································································································ 46
Setting the maximum number of PPPoE sessions································································································ 47
Limiting the PPPoE access rate ····························································································································· 48
Configuring the nas-port-id attribute···················································································································· 49
Configuring a VA pool ········································································································································· 50
Clearing PPPoE sessions ······································································································································· 51
Configuring a PPPoE client············································································································································ 51
Configuring a dialer interface ····························································································································· 52
Configuring a PPPoE session································································································································ 53
ii
Resetting a PPPoE session····································································································································· 53
Displaying and maintaining PPPoE ······························································································································ 54
Displaying and maintaining PPPoE server·········································································································· 54
Displaying and maintaining PPPoE client ··········································································································· 54
PPPoE configuration examples······································································································································ 55
PPPoE server configuration example ··················································································································· 55
PPPoE server IP address assignment through the local DHCP server configuration example ······················· 56
PPPoE server IP address assignment through a remote DHCP server configuration example······················· 57
PPPoE server IPv6 address assignment through ND and IPv6CP negotiation configuration example········· 59
PPPoE server IPv6 address assignment through DHCPv6 configuration example·········································· 60
Example for configuring PPPoE server IPv6 address assignment through prefix delegation by DHCPv6 ··· 61
PPPoE client in permanent mode configuration example·················································································· 62
PPPoE client in on-demand mode configuration example················································································· 64
PPPoE client in diagnostic mode configuration example ·················································································· 65
Configuration example for connecting a LAN to the Internet through an ADSL modem······························· 66
Configuring L2TP························································································································································70
Overview········································································································································································· 70
Typical L2TP networking ······································································································································· 70
L2TP message types and encapsulation structure ······························································································ 71
L2TP tunnel and session ········································································································································ 71
L2TP tunneling modes and tunnel establishment process ·················································································· 71
L2TP features ·························································································································································· 75
Protocols and standards ······································································································································· 77
Command and hardware compatibility ······················································································································ 77
L2TP configuration task list ············································································································································ 77
Configuring basic L2TP capabilities····························································································································· 78
Configuring an LAC······················································································································································· 79
Configuring an LAC to initiate tunneling requests for a user············································································ 79
Specifying LNS IP addresses································································································································ 79
Configuring the source IP address of L2TP tunnel packets················································································ 80
Enabling transferring AVP data in hidden mode······························································································· 80
Configuring AAA authentication on an LAC ······································································································ 80
Configuring an LAC to automatically establish an L2TP tunnel········································································ 81
Configuring an LNS ······················································································································································· 82
Creating a VT interface ········································································································································ 82
Configuring a VA pool ········································································································································· 83
Configuring an LNS to accept L2TP tunneling requests from a specific LAC·················································· 83
Configuring user authentication on an LNS ······································································································· 84
Configuring AAA authentication on an LNS ······································································································ 85
Configuring optional L2TP parameters ························································································································ 86
Configuring L2TP tunnel authentication··············································································································· 86
Setting the Hello interval······································································································································· 86
Enabling session flow control······························································································································· 86
Setting the DSCP value of L2TP packets·············································································································· 87
Assigning a tunnel peer to a VPN······················································································································· 87
Setting the TSA ID of the LTS ································································································································ 88
Displaying and maintaining L2TP································································································································· 88
L2TP configuration examples ········································································································································ 89
Configuration example for NAS-initiated L2TP tunnel······················································································· 89
Configuration example for client-initiated L2TP tunnel ······················································································ 91
Configuration example for LAC-auto-initiated L2TP tunnel················································································ 92
Troubleshooting L2TP ····················································································································································· 94
iii
Configuring HDLC······················································································································································96
Overview········································································································································································· 96
Command and hardware compatibility ······················································································································ 96
Enabling HDLC encapsulation on an interface ··········································································································· 96
Configuring link status polling ······································································································································ 97
Displaying and maintaining HDLC······························································································································· 97
HDLC configuration example········································································································································ 98
Network requirements··········································································································································· 98
Configuration procedure ······································································································································ 98
Verifying the configuration··································································································································· 98
Configuring HDLC link bundling···························································································································· 100
Overview·······································································································································································100
Basic concepts ·····················································································································································100
States of member interfaces ·······························································································································101
Load balancing modes ·······································································································································102
Command and hardware compatibility ····················································································································102
Configuring an HDLC link bundle interface ··············································································································103
Configuration restrictions and guidelines ·········································································································103
Configuration procedure ····································································································································103
Assigning an interface to an HDLC link bundle········································································································105
Configuration restrictions and guidelines ·········································································································105
Configuration procedure ····································································································································105
Displaying and maintaining HDLC link bundling ·····································································································106
HDLC link bundling configuration example ··············································································································106
Network requirements·········································································································································106
Configuration procedure ····································································································································107
Verifying the configuration·································································································································107
Configuring ISDN ··················································································································································· 109
Overview·······································································································································································109
ISDN interfaces····················································································································································109
ISDN protocol stacks···········································································································································110
ISDN application scenarios································································································································110
Feature and hardware compatibility··························································································································111
ISDN PRI configuration prerequisites ·························································································································111
ISDN configuration task list·········································································································································111
Setting the ISDN switch type on an ISDN interface ·································································································112
Setting the ISDN functionality of an ISDN interface·································································································113
Configuring SPID parameters for the NI switch type ·······························································································114
Configuring SPID assignment·····························································································································114
Configuring the TSPID timer and INFORMATION retransmission ·································································115
Enabling NIT mode for NI-type switches incapable of SPID negotiation ······················································115
Configuring Q.931 negotiation parameters·············································································································116
Configuring Q.931 call control parameters ·············································································································118
Configuring B-channel selection ························································································································118
Configuring calling number verification for incoming calls············································································118
Configuring called-number verification for incoming calls ·············································································119
Configuring ISDN calling number identification······························································································119
Configuring the Q.921 operating parameters ·········································································································120
Configuring the data link type of a BRI interface·····························································································120
Configuring per-channel TEI assignment on a BRI interface ···········································································120
Enabling permanent Q.921 link connectivity on an ISDN BRI interface ······················································121
Enabling persistent Layer 1 activation on a BRI interface···············································································121
Configuring a BRI interface to supply line power····························································································122
iv
Configuring the sliding window size on an ISDN BRI interface ····································································122
Configuring the sliding window size on an ISDN PRI interface·····································································123
Displaying and maintaining ISDN settings················································································································123
ISDN configuration examples·····································································································································124
ISDN PRI configuration example ·······················································································································124
NI-enabled ISDN BRI configuration example···································································································125
Troubleshooting····························································································································································127
Configuring ATM ···················································································································································· 128
Overview·······································································································································································128
ATM connections and ATM switching ··············································································································128
ATM architecture ·················································································································································129
ATM service types ···············································································································································130
ATM applications ················································································································································131
ATM OAM ···························································································································································131
Compatibility information············································································································································132
ATM configuration task list··········································································································································132
Configuring an ATM interface····································································································································133
Configuring a PVC·······················································································································································133
Configuring a PVC-group············································································································································133
Configuring the ATM AAL5 encapsulation type ·······································································································134
Configuring the ATM service type······························································································································135
Configuring applications carried by ATM ················································································································136
Configuring a VE interface·································································································································137
Configuring IPoA·················································································································································138
Configuring IPoEoA·············································································································································139
Configuring PPPoA··············································································································································140
Configuring PPPoEoA··········································································································································141
Configuring VP policing ··············································································································································142
Re-marking the CLP flag value of ATM cells··············································································································142
Configuring ATM OAM functions ······························································································································143
Displaying and maintaining ATM ······························································································································144
ATM configuration examples······································································································································144
IPoA configuration example·······························································································································144
IPoEoA configuration example···························································································································146
PPPoA configuration example····························································································································147
PPPoEoA configuration example························································································································148
ATM PVC transmission priority configuration example···················································································150
Troubleshooting ATM···················································································································································151
Link state error in IPoA application ···················································································································151
Link report error in PPPoA application ··············································································································151
Ping failure ···························································································································································151
PVC state is down when ATM interface state is up ·························································································152
Ping failure after PPPoA configuration ··············································································································152
Managing a modem··············································································································································· 153
Feature and hardware compatibility··························································································································153
Modem management configuration task list ·············································································································153
Configuring modem access services on a user line ·································································································153
Setting the answer timeout timer·································································································································154
Setting the modem answer mode·······························································································································155
Enabling a modem to obtain caller numbers ············································································································155
Enabling modem callback···········································································································································156
Issuing an AT command to a modem ························································································································156
Setting the country code of a modem ························································································································157
v
Modem management configuration example···········································································································157
Network requirements·········································································································································157
Configuration procedure ····································································································································157
Verifying the configuration·································································································································158
Troubleshooting modem faults ····································································································································159
Managing a 3G/4G modem ································································································································ 160
Configuration restrictions and guidelines··················································································································160
3G modem management configuration task list·······································································································160
4G modem management configuration task list·······································································································161
Configuring a cellular interface for a 3G modem····································································································161
Configuring a cellular interface for a 4G modem····································································································162
Configuring an Eth-channel interface for a 4G modem···························································································162
Configuring an IP address for an Eth-channel interface of a 4G modem······························································163
Configuring a 3G/4G network··································································································································163
Configuring parameter profiles ··································································································································164
Configuring a parameter profile························································································································164
Specifying the primary and backup profiles ····································································································165
Configuring PIN verification ·······································································································································165
Configuring DM ···························································································································································166
Issuing a configuration directive to a 3G/4G modem····························································································166
Configuring automatic reboot·····································································································································167
Configuring manual reboot·········································································································································167
Displaying and maintaining 3G/4G modem information ······················································································168
3G/4G modem management configuration examples ···························································································168
3G modem management configuration example····························································································168
4G modem management configuration example····························································································169
Troubleshooting····························································································································································170
Symptom·······························································································································································170
Solution·································································································································································170
Configuring DDR ····················································································································································· 171
Overview·······································································································································································171
Interfaces in DDR ·················································································································································171
DDR implementations ··········································································································································171
DDR types·····························································································································································173
Command and hardware compatibility ····················································································································174
DDR configuration task list ··········································································································································174
Packet-triggered DDR configuration task list·····································································································174
Auto-dial DDR configuration task list ·················································································································175
Route-triggered DDR configuration task list ······································································································175
Configuring basic settings for DDR ····························································································································176
Configuring physical interfaces ·························································································································176
Configuring link layer/network/routing protocols on the dialup interface···················································176
Associating a dial rule with a dialup interface·········································································································177
Configuring traditional DDR ·······································································································································177
Configuring an interface to place calls·············································································································178
Configuring an interface to receive calls··········································································································179
Configuring bundle DDR ·············································································································································180
Configuring a dialer interface to place calls····································································································180
Configuring a dialer interface to receive calls·································································································181
Configuring attributes for a dialup interface·············································································································182
Configuring MP for DDR ·············································································································································183
Configuration restrictions and guidelines ·········································································································184
Configuration procedure ····································································································································185
vi
Configuring PPP callback ············································································································································185
Configuring the callback client ··························································································································186
Configuring the callback server·························································································································187
Configuring ISDN caller number callback ················································································································188
Overview······························································································································································188
Configuration restrictions and guidelines ·········································································································189
Configuring a callback server by using traditional DDR·················································································189
Configuring a callback server by using bundle DDR ······················································································189
Configuring auto-dial···················································································································································190
Configuring dynamic route backup through DDR ····································································································190
Creating a dynamic route backup group ·········································································································191
Assigning a dialup interface to a dynamic route backup group ···································································191
Setting the delay for disconnecting a backup link···························································································192
Setting the warm-up timer for dynamic route backup······················································································192
Disconnecting a dialup link·········································································································································192
Displaying and maintaining DDR·······························································································································193
DDR configuration examples ······································································································································193
PSTN-based traditional DDR configuration example·······················································································193
PSTN-based bundle DDR configuration example·····························································································195
ISDN-based traditional DDR configuration example ·······················································································199
ISDN-based bundle DDR configuration example·····························································································201
MP for DDR configuration example···················································································································204
ISDN caller number callback configuration example······················································································207
Router-to-router PPP callback configuration example·······················································································208
Router-to-PC PPP callback configuration example····························································································211
NT server-to-router PPP callback configuration example·················································································213
Configuration example for circular dial string backup and Internet access ·················································215
Dynamic route backup for traditional DDR configuration example ·······························································221
Dynamic route backup for bundle DDR configuration example·····································································223
Configuration example for dynamic route backup for multiple networks ·····················································226
Troubleshooting····························································································································································228
Symptom 1: Failure to establish a dialup connection ·····················································································228
Solution·································································································································································228
Symptom 2: Ping failure ·····································································································································229
Solution·································································································································································229
Configuring Frame Relay········································································································································ 230
Overview·······································································································································································230
Frame Relay interface types ·······························································································································230
Virtual circuit ························································································································································231
DLCI ······································································································································································231
Frame Relay address mapping ··························································································································232
LMI protocol ·························································································································································232
Application scenarios ·········································································································································234
Command and hardware compatibility ····················································································································235
Frame Relay configuration task list·····························································································································235
Configuring basic DTE-side Frame Relay ··················································································································236
Configuring basic DCE-side Frame Relay ·················································································································237
Configuring local Frame Relay virtual circuits ··········································································································237
Configuration restrictions and guidelines ·········································································································237
Configuration procedure ····································································································································238
Configuring Frame Relay address mapping ·············································································································238
Configuring static address-to-DLCI maps ··········································································································238
Configuring dynamic address mapping ···········································································································239
Configuring Frame Relay subinterfaces·····················································································································239
vii
Configuring Frame Relay IPHC···································································································································240
Configuration restrictions and guidelines ·········································································································240
Configuring Frame Relay IPHC on an interface·······························································································241
Configuring Frame Relay IPHC on a VC ··········································································································241
Configuring Frame Relay STAC compression···········································································································242
Configuration restrictions and guidelines ·········································································································242
Configuring Frame Relay STAC compression on a virtual circuit ··································································242
Configuring Frame Relay FRF.12 fragmentation ······································································································242
Configuration restrictions and guidelines ·········································································································243
Configuring Frame Relay FRF.12 fragmentation on an interface ··································································243
Displaying and maintaining Frame Relay ·················································································································243
Frame Relay configuration example ··························································································································244
Network requirements·········································································································································244
Configuration procedure ····································································································································244
Verifying the configuration·································································································································245
Troubleshooting Frame Relay······································································································································246
The physical layer is down·································································································································246
The physical layer is already up, but the link layer protocol is down···························································246
The link layer protocol is up, but the peer cannot be pinged ········································································246
Configuring Multilink Frame Relay ························································································································ 248
MFR configuration task list ··········································································································································248
Configuring an MFR bundle········································································································································248
Configuring an MFR bundle link ································································································································249
Displaying and maintaining MFR·······························································································································250
MFR configuration example········································································································································250
Network requirements·········································································································································250
Configuration procedure ····································································································································251
Verifying the configuration·································································································································252
Support and other resources ·································································································································· 253
Contacting HP ······························································································································································253
Subscription service ············································································································································253
Related information······················································································································································253
Documents····························································································································································253
Websites·······························································································································································253
Conventions ··································································································································································254
Index ········································································································································································ 256
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.
Dead Establish
Up Authenticate
Opened
Terminate Network
Down
Fail Fail Success
/None
Closing
2
{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.
{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. HP recommends that you
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 three times at most.
•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 three times at most.
3
{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.
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:
4
{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:
•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.
After receiving a packet larger than the minimum packet size for fragmentation, MP fragments the packet
and distributes the fragments across multiple PPP links to the peer. After the peer receives these fragments,
it 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, PPPoA, or PPPoFR) interfaces. In MP configuration, however, HP
recommends that you include only one type of interfaces in an MP bundle.
Compatibility information
Feature and hardware compatibility
PPP and MP are supported on routers that are installed with an SAE, AS, ASE, BS, E1, E1-F, T1, T1-F, POS,
CPOS, CE3, or AM interface module.
5
Command and hardware compatibility
Commands and descriptions for centralized devices apply to the following routers:
•MSR1002-4/1003-8S.
•MSR2003.
•MSR2004-24/2004-48.
•MSR3012/3024/3044/3064.
Commands and descriptions for distributed devices apply to MSR4060 and MSR4080 routers.
Configuring PPP
PPP configuration task list
Tasks at a
g
lance
(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
Ste
p
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.
6
Configuring PAP authentication
To configure the authenticator:
Ste
p
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:
Ste
p
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 peer is
authenticated by the
authenticator by using PAP.
ppp pap local-user username
password { cipher | simple }
password
By default, when being
authenticated by the authenticator
by using PAP, the peer sends null
username and password to the
authenticator.
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:
Ste
p
Command Remarks
1. Enter system view. system-view N/A
2. Enter interface view. interface interface-type
interface-number N/A
7
Ste
p
Command Remarks
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
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:
Ste
p
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:
8
Ste
p
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 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:
Ste
p
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 } password
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.
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:
Ste
p
Command Remarks
1. Enter system view. system-view N/A
9
Ste
p
Command Remarks
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.
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.
To configure MS-CHAP or MS-CHAP-V2 authentication when no authenticator name is configured:
Ste
p
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.
10
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.
To disable sending of keepalives, set the keepalive interval to 0.
To configure the polling feature:
Ste
p
Command
Remarks
1. Enter system view. system-view N/A
2. Enter interface view. interface interface-type
interface-number N/A
3. Set the keepalive interval. timer-hold seconds The default setting is 10 seconds.
4. Set the keepalive retry limit. timer-hold retry retry 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.
To configure the PPP negotiation timeout time:
Ste
p
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.
Configuring IP address negotiation
To configure the device as the client:
Ste
p
Command
Remarks
1. Enter system view. system-view N/A
11
Ste
p
Command
Remarks
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.
This command is mutually
exclusive with the ip address
command. For more information
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):
Ste
p
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):
Ste
p
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.
Other manuals for MSR SERIES
14
Table of contents
Other HP Network Router manuals
HP
HP HPE 6125G User instructions
HP
HP FlexNetwork MSR3012 User manual
HP
HP A5830 Series User manual
HP
HP ProCurve MSM317 User manual
HP
HP 5820X Series User manual
HP
HP J2600A User manual
HP
HP A8800 Series User manual
HP
HP MSR930 Series Assembly instructions
HP
HP N1200 - StorageWorks Network Storage Router User manual
HP
HP MSR SERIES Installation manual
HP
HP J4093A User manual
HP
HP MSR1003-8S Installation manual
HP
HP FlexNetwork HSR6800 User manual
HP
HP MSR930 Series User manual
HP
HP VSR1000 User manual
HP
HP MSR SERIES User manual
HP
HP Series 200 User manual
HP
HP A58x0AF Bck(pwr)-Frt(ports) Assembly instructions
HP
HP ProCurve MSM317 Operator's manual
HP
HP FlexNetwork MSR3064 User manual
