Hpe Flexnetwork msr series User manual

HPE FlexNetwork MSR Router Series

Comware 5 Layer 2 - WAN Access

Configuration Guide



Part number: 5200-2317

Software version: CMW710-R2516

Document version: 6W107-20160831

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.

Contents

Configuring SLIP····························································································· 1

Hardware compatibility with SLIP ······················································································································1

Configuration guidelines ····································································································································1

Configuration procedure ····································································································································1

SLIP encapsulation on synchronous/asynchronous interfaces configuration example ·····································2

Network requirements································································································································2

Configuration procedure·····························································································································2

Configuring PPP and MP ················································································ 4

PPP overview·····················································································································································4

PPP link establishment process·················································································································4

PPP authentication·····································································································································5

MP overview ······················································································································································6

Configuring PPP ················································································································································6

PPP configuration task list ·························································································································6

Enabling PPP encapsulation on an interface·····························································································6

Configuring PPP authentication ·················································································································6

Configuring the polling interval·················································································································10

Configuring PPP negotiation ····················································································································11

Enabling PPP link quality control ·············································································································16

Enabling PPP traffic statistics collection ··································································································17

Disabling peer route creation ···················································································································17

Configuring MP ················································································································································18

Configuration task list·······························································································································18

Configuring MP by using a VT interface···································································································18

Configuring MP through an MP-group interface·······················································································22

Configuring short sequence number header format negotiation ······························································23

Configuring the MP endpoint descriptor···································································································23

Configuring PPP link efficiency mechanisms···································································································24

Configuring IPHC ·····································································································································24

Configuring Stac LZS compression··········································································································24

Configuring VJ TCP header compression································································································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

PPP IP address negotiation configuration example ·················································································33

MP configuration example························································································································34

MP binding mode configuration examples ·······························································································37

Troubleshooting PPP configuration ·················································································································44

Configuring PPPoE ······················································································· 46

Overview ··························································································································································46

PPPoE network structure ·························································································································46

Protocols and standards ··························································································································47

Configuring a PPPoE server ····························································································································47

Configuring a PPPoE client······························································································································48

Configuring a dialer interface ···················································································································48

Configuring a PPPoE session··················································································································49

Displaying and maintaining PPPoE ·················································································································50

PPPoE configuration examples ·······················································································································50

PPPoE server configuration example ······································································································50

PPPoE client configuration example········································································································52

Configuration example for connecting a LAN to the Internet using an ADSL modem ·····························54

Configuration example for using ADSL to provide backup connections ··················································56

iii

Configuration example for accessing the Internet through an ADSL interface ········································56

Configuring ISDN ·························································································· 58

Configuring ISDN BRI ······································································································································59

Configuring ISDN PRI ······································································································································61

Configuring the negotiation parameters of ISDN layer 3 protocol····································································62

Configuring the ISDN Q.931 protocol version··································································································66

Configuring the SPID of the ISDN NI protocol ·································································································67

Setting the called number or subaddress to be checked during a digital incoming call···································67

Configuring an interface to send calling number during an outgoing call ························································68

Setting the local management ISDN B channel ·······························································································68

Configuring ISDN B channel selection mode···································································································69

Configuring the sliding window size on a BRI interface ···················································································69

Configuring the sliding window size on a PRI interface ···················································································70

Collecting ISDN message statistics ·················································································································70

Configuring an interface to check the calling number when an incoming call comes ······································71

Configuring progress-to-alerting conversion ····································································································71

Configuring ISDN to carry the Calling-Name field in outgoing packets····························································71

Configuring ISDN to carry the Connected-Name field in outgoing packets ·····················································72

Configuring ISDN to carry the Channel-ID field for only once in the responses ··············································72

Configuring the service type in the ISDN bearer compatibility signaling··························································72

Setting the progress indicator value in ISDN signaling messages···································································73

Configuring TEI treatment on the BRI interface ·······························································································73

Configuring an ISDN BRI leased line ···············································································································73

Configuring permanent link function at ISDN BRI link layer·············································································74

Configuring an ISDN BRI interface to be in permanent active state on physical layer ····································74

Configuring deactivation protection for an ISDN BRI interface ········································································75

Enabling remote powering on an ISDN BRI interface ······················································································75

Configuring ISDN call check ····························································································································76

Enabling the trap function ································································································································76

Displaying and maintaining ISDN ····················································································································76

ISDN configuration examples ··························································································································77

Connecting routers through ISDN PRI lines·····························································································77

Connecting routers through ISDN BRI lines running NI ···········································································78

Using ISDN BRI leased lines to implement MP bundling·········································································78

Configuring ISDN 128K leased lines········································································································79

Interoperating with DMS100 switches······································································································82

Troubleshooting ···············································································································································83

Configuring frame relay················································································· 85

Frame relay interface types······················································································································85

Virtual circuit·············································································································································85

Data link connection identifier ··················································································································86

Frame relay address mapping ·················································································································86

LMI protocol ·············································································································································86

Typical application scenarios ···················································································································87

Hardware compatibility with frame relay ··········································································································88

Frame relay configuration task list ···················································································································88

Configuring DTE side frame relay····················································································································89

Configuring basic DTE side frame relay···································································································89

Configuring frame relay address mappings ·····························································································89

Configuring a frame relay local virtual circuit ···························································································91

Configuring a frame relay subinterface ····································································································91

Configuring Annex G································································································································92

Marking the DE bit····································································································································93

Configuring frame relay fragmentation·····································································································94

Configuring DCE side frame relay ···················································································································95

Configuring basic DCE side frame relay ··································································································95

Configuring frame relay address mapping on the DCE side ····································································96

Configuring frame relay local virtual circuit on the DCE side ···································································96

Configuring frame relay subinterface on the DCE side ············································································96

Configuring frame relay switching ············································································································96

Configuring frame relay over IP ···············································································································97

Configuring Annex G································································································································98

Marking the DE bit····································································································································98

Configuring frame relay fragmentation·····································································································99

Displaying and maintaining frame relay ···········································································································99

Frame relay configuration examples··············································································································100

Connecting LANs through a frame relay network (IPv4)········································································100

Connecting LANs through a frame relay network (IPv6)········································································102

Connecting LANs with a dedicated line··································································································103

Connecting LANs through an Annex G DLCI·························································································104

Troubleshooting frame relay ··························································································································105

Configuring frame relay compression ························································· 107

FRF.9 ·····················································································································································107

FRF.20 ···················································································································································107

Configuring FRF.9 compression ····················································································································107

Configuration restrictions and guidelines ·······························································································107

Configuration procedure·························································································································108

Configuring FRF.20 IP header compression··································································································108

Displaying and maintaining frame relay compression····················································································109

Frame relay compression configuration examples ························································································109

Frame relay FRF.9 stac compression configuration example································································109

Frame relay FRF.20 IP header compression configuration example·····················································110

Configuring multilink frame relay································································· 113

Configuring an MFR bundle ···························································································································113

Configuring an MFR bundle link·····················································································································114

Displaying and maintaining multilink frame relay ···························································································114

Multilink frame relay configuration examples ·································································································115

MFR direct connection configuration example ·······················································································115

MFR switched connection configuration example··················································································116

Configuring PPPoFR··················································································· 118

Displaying and maintaining PPPoFR ·············································································································118

PPPoFR configuration example·····················································································································119

Network requirements····························································································································119

Configuration procedure·························································································································119

Configuring MPoFR ···················································································· 120

MPoFR configuration example·······················································································································121

Network requirements····························································································································121

Configuration procedure·························································································································121

Configuring DCC························································································· 123

Approaches to DCC ·······························································································································123

DCC features ·········································································································································125

Configuration prerequisites ····················································································································126

DCC configuration task list·····························································································································126

Configuring basic settings for DCC················································································································127

Setting the operating mode for physical interfaces ················································································127

Configuring link layer/network/routing protocols on the dialup interface ················································127

Associating a DCC dial ACL with the dialup interface············································································128

Configuring C-DCC ········································································································································128

Configuring an interface to place calls to a remote end ·········································································129

Configuring an interface to receive calls from a remote end··································································130

Configuring an interface to place calls to multiple remote ends·····························································131

Configuring an interface to receive calls from multiple remote ends······················································132

Configuring multiple interfaces to place calls to one or multiple remote ends ·······································132

Configuring multiple interfaces to receive calls from one or multiple remote ends ································134

Configuring RS-DCC······································································································································135

Enabling RS-DCC ··································································································································136

Configuring a dial string for the dialer interface······················································································136

Assigning physical interfaces to the dialer bundle ·················································································136

Configuring dial authentication for RS-DCC···························································································137

Configuring MP for DCC ································································································································137

Implementing DCC with MP ···················································································································137

Configuration guidelines·························································································································138

Configuration procedure·························································································································138

Configuring PPP callback ······························································································································139

Configuration guidelines·························································································································139

Configuring PPP callback in the C-DCC implementation·······································································139

Configuring PPP callback with RS-DCC ································································································141

Configuring ISDN caller identification callback·······························································································142

ISDN caller identification callback features ····························································································142

Configuring ISDN caller identification callback with C-DCC···································································143

Configuring ISDN caller identification callback with RS-DCC ································································144

Configuring advanced DCC functions············································································································145

Configuring an ISDN leased line ············································································································145

Configuring auto-dial ······························································································································145

Configuring circular dial string backup ···································································································145

Configuring DCC overlap receiving········································································································146

Configuring DCC timers and buffer queue length ··························································································146

DCC timers and buffer queue length······································································································146

Configuration procedure·························································································································147

Configuring dynamic route backup achieved through DCC ···········································································147

Introduction to dynamic route backup ····································································································147

Creating a dynamic route backup group ································································································148

Enabling dynamic route backup on a backup interface··········································································149

Configuring the delay for disconnecting a backup link ···········································································149

Configuring the warm-up timer for dynamic route backup ·····································································149

Configuring the traffic statistics collecting interval ·························································································150

Displaying and maintaining DCC ···················································································································150

DCC configuration examples ·························································································································150

C-DCC configuration example ···············································································································150

RS-DCC configuration example ·············································································································152

Configuration example for DCC on ISDN·······························································································156

Configuration example for RS-DCC with MP ·························································································160

Configuration example for router-to-router PPP callback with DCC ······················································162

Configuration example for router-to-router ISDN caller identification callback with DCC ······················165

Configuration example for router-to-PC PPP callback with DCC···························································166

Configuration example for NT server-to-router callback with DCC ························································168

Configuration example for circular dial string backup and Internet access with DCC····························170

Dynamic route backup configuration example 1 ····················································································175

Dynamic route backup configuration example 2 ····················································································177

Dynamic route backup configuration example 3 ····················································································179

Dynamic route backup configuration example 4 ····················································································181

Managing a modem ···················································································· 185

Configuring modem management··················································································································185

Setting the modem answer mode ··················································································································186

Issuing an AT command to a modem ············································································································186

Modem management configuration example·································································································186

Configuring ATM ························································································· 188

ATM connections and ATM switching ····································································································188

ATM architecture····································································································································189

IPoA, IPoEoA, PPPoA, and PPPoEoA ··········································································································190

IPoA ·······················································································································································190

IPoEoA ···················································································································································190

PPPoA····················································································································································190

PPPoEoA ···············································································································································190

ATM service types ·········································································································································191

CBR························································································································································191

rt-VBR ····················································································································································191

nrt-VBR ··················································································································································191

UBR························································································································································191

InARP·····························································································································································191

ATM OAM ······················································································································································192

OAM F5 loopback ··································································································································192

OAM continuity check ····························································································································192

Hardware compatibility with ATM···················································································································192

ATM configuration task list·····························································································································193

Configuring an ATM interface ························································································································193

Configuring an ATM subinterface ··················································································································194

Performing basic configurations for an ATM subinterface ·····································································194

Checking PVC status to determine the protocol state of an ATM P2P subinterface······························194

Configuring PVCs and the maximum number of PVCs allowed on an interface············································194

Configuring PVC parameters ·················································································································194

Setting the CLP bit for ATM cells ···········································································································196

Assigning a transmission priority to an ATM PVC··················································································196

Configuring PVC service mapping ·········································································································197

Configuring the maximum number of PVCs allowed on an ATM interface ············································197

Configuring an ATM class······························································································································198

Configuring VP policing··································································································································200

Configuring applications carried by ATM ·······································································································200

Configuring Layer 3 VE interfaces ·········································································································200

Configuring IPoA····································································································································201

Configuring IPoEoA································································································································202

Configuring PPPoA ································································································································202

Configuring PPPoEoA····························································································································203

Displaying and maintaining ATM ···················································································································204

ATM configuration examples ·························································································································205

IPoA configuration example ···················································································································205

IPoEoA configuration example···············································································································206

PPPoA configuration example ···············································································································207

PPPoEoA server configuration example ································································································209

PPPoEoA client configuration example··································································································210

ATM PVC transmit priority configuration example ·················································································212

Troubleshooting ATM·····································································································································213

Link state error in IPoA application ········································································································213

Link report error in PPPoA application ···································································································214

Ping failure ·············································································································································214

ATM interface state error ·······················································································································214

PVC state is down while ATM interface state is up················································································214

Ping failure after PPPoA configuration···································································································215

Packet loss and CRC errors and changes of interface state ·································································215

Configuring HDLC······················································································· 216

HDLC frame format and frame type···············································································································216

Enabling HDLC encapsulation on an interface ······························································································216

Configuring an IP address for an interface ····································································································217

Configuring the link status polling interval······································································································217

vii

Configuring HDLC compression ····················································································································218

Displaying and maintaining HDLC ·················································································································218

HDLC configuration examples ·······················································································································218

Basic HDLC configuration example ·······································································································218

HDLC in conjunction with IP unnumbered interface configuration example ··········································219

Configuring DLSw ······················································································· 221

Differences between DLSw v1.0 and DLSw v2.0···················································································221

Protocols and standards ························································································································223

Hardware compatibility with DLSw·················································································································223

Configuring DLSw in an Ethernet environment······························································································223

Creating DLSw peers ·····························································································································224

Mapping a bridge set to DLSw ···············································································································224

Adding an Ethernet interface to a bridge set··························································································225

Setting DLSw timers·······························································································································225

Configuring LLC2 parameters ················································································································225

Configuring the multicast function of DLSw v2.0····················································································226

Configuring the maximum number of DLSw v2.0 explorer retries··························································227

Applying an ACL in DLSw ······················································································································227

Configuring DLSw Ethernet redundancy································································································228

Configuring DLSw in an SDLC environment··································································································228

Configuring DLSw ··································································································································228

Enabling SDLC encapsulation on an interface·······················································································229

Enabling DLSw forwarding on an SDLC interface ·················································································229

Configuring SDLC roles ·························································································································230

Configuring an SDLC address for a secondary station ··········································································230

Configuring an SDLC peer ·····················································································································231

Configuring an SDLC XID ······················································································································231

Configuring an SDLC virtual MAC address····························································································232

Configuring the properties of a synchronous serial interface ·································································232

Configuring optional SDLC parameters ·································································································233

Configuring local reachable MAC or SAP addresses ····················································································234

Configuring remote reachability information ··································································································234

Configuring DLSw load balancing··················································································································235

Displaying and maintaining DLSw ·················································································································235

DLSw configuration examples ·······················································································································236

Configuring LAN-to-LAN DLSw··············································································································236

Configuring SDLC-to-SDLC DLSw·········································································································237

Configuring DLSw for SDLC-to-LAN remote media translation ·····························································238

Configuring DLSw with VLAN support ···································································································239

DLSw v2.0 configuration example··········································································································241

Ethernet redundancy configuration example for LAN-to-LAN DLSw ·····················································242

Ethernet redundancy configuration example for SDLC-to-LAN DLSw···················································243

Switch support for Ethernet redundancy configuration example for LAN-to-LAN DLSw························245

Load balancing configuration example for LAN-to-LAN DLSw ······························································247

Load balancing configuration example for SDLC-to-LAN DLSw····························································248

SAP address-based filtering configuration example ··············································································250

Troubleshooting DLSw···································································································································251

Unable to establish a TCP connection ···································································································251

Unable to establish a DLSw circuit·········································································································251

Configuring L2TP ························································································ 253

Typical L2TP networking application······································································································253

L2TP message types and encapsulation architecture ···········································································254

L2TP tunnel and session························································································································254

L2TP tunneling modes and tunnel establishment process·····································································255

L2TP features·········································································································································257

L2TP-based EAD ···································································································································257

Protocols and standards ························································································································258

L2TP configuration task list····························································································································258

viii

Configuring basic L2TP capabilities···············································································································259

Configuring an LAC········································································································································260

Configuring an LAC to initiate tunneling requests for specified users····················································260

Configuring an LAC to transfer AVP data in hidden mode·····································································260

Configuring AAA authentication for VPN users on LAC side ·································································261

Configuring an LAC to establish an L2TP tunnel ···················································································262

Configuring an LNS········································································································································263

Creating a VT interface ··························································································································263

Configuring the local address and the address pool for allocation·························································264

Configuring an LNS to grant certain L2TP tunneling requests·······························································264

Configuring user authentication on an LNS ···························································································265

Configuring AAA authentication for VPN users on an LNS····································································266

Enabling L2TP for VPNs ························································································································266

Configuring the LNS to support IMSI or SN in PPP LCP negotiation·····················································267

Configuring L2TP connection parameters ·····································································································268

Configuring L2TP tunnel authentication ·································································································268

Setting the hello interval·························································································································268

Enabling tunnel flow control ···················································································································269

Disconnecting tunnels by force ··············································································································269

Configuring L2TP-based EAD························································································································269

Configuration prerequisites ····················································································································269

Configuration procedure·························································································································269

Displaying and maintaining L2TP ··················································································································270

L2TP configuration examples ························································································································270

Configuration example for NAS-initiated VPN························································································270

Configuration example for client-initiated VPN·······················································································272

Configuration example for LAC-auto-initiated VPN················································································274

Configuration example for L2TP multi-domain application·····································································276

Complicated network application ···········································································································279

Troubleshooting L2TP····································································································································280

Configuring L2TP-based EAD····································································· 281

Displaying and maintaining L2TP-based EAD ·······························································································282

L2TP-based EAD configuration example·······································································································282

Configuring bridging···················································································· 285

Bridge functionality·········································································································································285

Obtaining the bridge table ······················································································································285

Forwarding and filtering··························································································································287

Bridging configuration task list ·······················································································································289

Configuring basic bridging functionalities·······································································································289

Configuration restrictions and guidelines ·······························································································289

Configuration procedure·························································································································290

Configuring bridge table entries ·····················································································································290

Configuring bridge routing······························································································································291

Enabling VLAN transparency·························································································································292

Configuration restrictions and guidelines ·······························································································292

Configuration procedure·························································································································292

Displaying and maintaining bridging ··············································································································293

Transparent bridging configuration examples································································································294

Configuration example for transparent bridging over ATM ····································································294

Configuration example for transparent bridging over PPP·····································································295

Configuration example for transparent bridging over MP·······································································295

Configuration example for transparent bridging over FR ·······································································297

Configuration example for transparent bridging over X.25·····································································297

Configuration example for transparent bridging over HDLC ··································································298

Configuration example for bridging with FR sub-interface support ························································299

Bridge routing configuration example·····································································································301

Configuration example for bridging over dialer interface········································································301

VLAN transparency configuration example····························································································303

Configuring EtoPPP and EtoFR·································································· 305

Hardware compatibility with EtoFR ················································································································305

How EtoPPP and EtoFR work ·······················································································································305

EtoPPP and EtoFR translation tables ····································································································305

How EtoPPP and EtoFR handle IP packets···························································································305

Creating an EtoPPP translation mapping ······································································································305

Creating an EtoFR translation mapping·········································································································306

Displaying and maintaining EtoPPP and EtoFR ····························································································306

EtoPPP and EtoFR configuration examples ··································································································307

EtoPPP configuration example ··············································································································307

EtoFR configuration example·················································································································308

Configuring LAPB and X.25 ········································································ 310

X.25························································································································································310

LAPB······················································································································································311

X.25 switching ········································································································································312

Hardware compatibility with LAPB and X.25··································································································312

Configuring LAPB ··········································································································································312

LAPB parameters···································································································································312

Configuration procedure·························································································································313

Configuring an X.25 interface ························································································································314

Configuring the basic parameters of an X.25 interface ··········································································314

Configuring X.25 interface supplementary parameters··········································································318

Configuring an X.25 subinterface···········································································································320

Configuring X.25 datagram transmission·······································································································321

Configuring basic X.25 datagram transmission functionality··································································321

Configuring additional parameters for X.25 datagram transmission ······················································322

Configuring X.25 switching ····························································································································327

Configuring the basic X.25 switching functionality ·················································································327

Configuring flow control negotiation of X.25 switching···········································································328

Configuring X.25 load sharing························································································································329

Configuring X.25 closed user group···············································································································331

Configuring X.25 PAD remote access service ·······························································································333

PAD························································································································································333

Configuring X.25 PAD ····························································································································333

Configuring XOT ············································································································································334

XOT························································································································································334

Configuration procedure·························································································································335

Configuring X.25 over FR ······························································································································338

X.25 over FR ··········································································································································338

Configuring an SVC application of X.25 over FR ···················································································338

Configuring a PVC application of X.25 over FR ·····················································································339

Configuring X2T ·············································································································································340

Configuration guidelines·························································································································340

Configuration procedure·························································································································340

Displaying and maintaining LAPB and X.25 ··································································································341

LAPB configuration example··························································································································342

X.25 configuration examples··························································································································344

Direct connection of two routers connecting through serial interfaces (one address mapping)·············344

Direct connection of two routers connecting through serial interfaces (two address mappings) ···········346

Connecting the router to X.25 public packet network·············································································349

Configuring virtual circuit range··············································································································350

Transmitting IP datagrams through X.25 PVCs ·····················································································351

X.25 subinterface configuration example ·······························································································353

SVC application of XOT ·························································································································356

PVC application of XOT ·························································································································357

SVC application of X.25 over FR ···········································································································359

PVC application of X.25 over FR ···········································································································360

X.25 load sharing application ·················································································································362

Implementing X.25 load sharing function for IP datagram transmission ················································365

TCP/IP header compression protocol application ··················································································368

X.25 PAD configuration example ···········································································································369

X2T SVC configuration example ············································································································370

X2T PVC configuration example ············································································································371

Troubleshooting LAPB configuration ·············································································································371

LAPB (or X.25) of two sides always being down····················································································371

Failed to ping the other side with X.25 on both sides being up······························································372

Troubleshooting X.25 configuration ···············································································································372

X.25 of two sides always being down with LAPB of two sides being up ················································372

Failed to ping the other side with X.25 on both sides being up······························································372

Continuous resets and clears of the virtual circuit established ······························································373

PVC setup request rejected ···················································································································373

Troubleshooting X.25 PAD·····················································································································373

Failed to ping XOT SVCs ·······················································································································373

Failed to ping XOT PVCs ·······················································································································374

Document conventions and icons ······························································· 375

Conventions ···················································································································································375

Network topology icons··································································································································376

Support and other resources ······································································ 377

Accessing Hewlett Packard Enterprise Support ····························································································377

Accessing updates·········································································································································377

Websites ················································································································································378

Customer self repair·······························································································································378

Remote support······································································································································378

Documentation feedback ·······················································································································378

Index ··········································································································· 380

Configuring SLIP

The Serial Line Internet Protocol (SLIP) is a link layer protocol transmitting network layer data

packets over serial lines. It is documented in RFC 1055. SLIP is easy to implement and supported

only on asynchronous interfaces.

Hardware compatibility with SLIP

SLIP is not available on the following routers:

•MSR900.

•MSR93X.

•MSR1000.

Configuration guidelines

•You can enable SLIP encapsulation only on asynchronous interfaces. For a

synchronous/asynchronous interface, you can switch it to the asynchronous mode and then

enable SLIP encapsulation on it.

•Some asynchronous interfaces do not support the SLIP protocol, but you can still configure the

link-protocol slip command on it. When you do that, the system informs you that the operation

of SLIP encapsulation fails. By then, no encapsulation is enabled on the interface. You must use

the link-protocol ppp command to enable PPP encapsulation on the interface to make it

available again.

Configuration procedure

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

synchronous/asynchronou

s interface to operate in

asynchronous mode.

physical-mode async

Optional.

You must configure this command for

synchronous/asynchronous interfaces,

but not for asynchronous interfaces.

4. Configure the

asynchronous interface to

operate in protocol mode. async mode protocol Optional.

Protocol mode by default.

5. Enable SLIP

encapsulation on the

interface. link-protocol slip Optional.

PPP by default.

SLIP encapsulation on

synchronous/asynchronous interfaces

configuration example

Network requirements

As shown in Figure 1, Router A and Router B are connected by synchronous/asynchronous interface

Serial 2/0. The link layer protocol is SLIP.

Figure 1 Network diagram

Configuration procedure

1. Configure Router A:

# Configure interface Serial 2/0 to operate in asynchronous and protocol mode.

<RouterA> system-view

[RouterA] interface serial 2/0

[RouterA-Serial2/0] physical-mode async

[RouterA-Serial2/0] async mode protocol

# Enable SLIP encapsulation on interface Serial 2/0.

[RouterA-Serial2/0] link-protocol slip

# Assign an IP address to interface Serial 2/0.

[RouterA-Serial2/0] ip address 200.1.1.1 16

2. Configure Router B:

# Configure interface Serial 2/0 to operate in asynchronous and protocol mode.

<RouterB> system-view

[RouterB] interface serial 2/0

[RouterB-Serial2/0] physical-mode async

[RouterB-Serial2/0] async mode protocol

# Enable SLIP encapsulation on interface Serial 2/0.

[RouterB-Serial2/0] link-protocol slip

# Assign an IP address to interface Serial 2/0.

[RouterB-Serial2/0] ip address 200.1.1.2 16

3. Verify the configuration:

Use the display interface command to view the information about interface Serial 2/0. The

physical layer status and link layer status of Serial 2/0 are both up, and Router A and Router B

can successfully ping each other.

[RouterB-Serial2/0] display interface serial 2/0

Serial2/0 current state: UP

Line protocol current state: UP

Description: Serial2/0 Interface

The Maximum Transmit Unit is 1500, Hold timer is 10(sec)

Internet Address is 200.1.1.2/16 Primary

Link layer protocol is SLIP

Output queue : (Urgent queuing : Size/Length/Discards) 0/100/0

Output queue : (Protocol queuing : Size/Length/Discards) 0/500/0

Output queue : (FIFO queuing : Size/Length/Discards) 0/75/0

Physical layer is asynchronous, Baudrate is 9600 bps

Last clearing of counters: Never

Last 300 seconds input rate 0.00 bytes/sec, 0 bits/sec, 0.00 packets/sec

Last 300 seconds output rate 0.00 bytes/sec, 0 bits/sec, 0.00 packets/sec

Input: 11753 packets, 147028 bytes

0 broadcasts, 0 multicasts

16 errors, 0 runts, 3 giants

1 CRC, 0 align errors, 0 overruns

0 dribbles, 0 aborts, 0 no buffers

12 frame errors

Output:11741 packets, 142014 bytes

0 errors, 0 underruns, 0 collisions

0 deferred

DCD=DOWN DTR=UP DSR=UP RTS=UP CTS=UP

[RouterB-Serial2/0] ping 200.1.1.1

PING 200.1.1.1: 56 data bytes, press CTRL_C to break

Reply from 200.1.1.1: bytes=56 Sequence=1 ttl=255 time=103 ms

Reply from 200.1.1.1: bytes=56 Sequence=2 ttl=255 time=1 ms

Reply from 200.1.1.1: bytes=56 Sequence=3 ttl=255 time=1 ms

Reply from 200.1.1.1: bytes=56 Sequence=4 ttl=255 time=1 ms

Reply from 200.1.1.1: bytes=56 Sequence=5 ttl=255 time=10 ms

--- 200.1.1.1 ping statistics ---

5 packet(s) transmitted

5 packet(s) received

0.00% packet loss

round-trip min/avg/max = 1/23/103 ms

Configuring PPP and MP

The MSR93X router does not support MP.

PPP overview

Point-to-Point Protocol (PPP) is a link layer protocol that carries network layer packets over

point-to-point links. 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—Provide network security. Protocols include Password

Authentication Protocol (PAP), Challenge Handshake Authentication Protocol (CHAP),

Microsoft CHAP (MS-CHAP), and Microsoft CHAP Version 2 (MS-CHAP-V2).

PPP link establishment process

Figure 2 shows the PPP link establishment process.

Figure 2 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),

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 supplicant fails to pass the

authentication, the link reports a Fail event and enters the Link Termination phase, where the

link is torn down and LCP goes down. If the supplicant passes the authentication, a Success

event is reported.

4. If a network layer protocol is configured, the PPP link enters the Network-Layer Protocol phase

for NCP negotiation, such as IPCP negotiation or 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.

Dead Establish

Up Authenticate

Opened

Terminate Network

Down

Fail Fail Success

/None

Closing

5. If the interface is configured with an IP address, the IPCP negotiation is performed. IPCP

configuration options include IP addresses of the two ends, IP compression protocol, and DNS

server IP address. After the IPCP negotiation succeeds, the link can carry IP packets.

6. After the NCP negotiation is performed, the PPP link remains active until explicit LCP or NCP

frames close the link, or until some external events take place (for example, the intervention of

a user).

For more information about PPP, see RFC 1661.

PPP authentication

PPP provides authentication methods, which makes it viable to implement AAA on PPP links.

Combining PPP with AAA can perform authentication and accounting for supplicants and assign IP

addresses to the supplicants based on the authentication.

PPP supports the following authentication methods:

•PAP—PAP is a two-way handshake authentication protocol using the username and password.

PAP sends passwords 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 using ciphertext passwords.

Two types of CHAP authentication exist: one-way CHAP authentication and two-way CHAP

authentication. In one-way CHAP authentication, the authenticator can be optionally configured

with a username. Hewlett Packard Enterprise recommends that you configure a username for

the authenticator, which makes it easier for the supplicant to verify the identity of the

authenticator.

CHAP transmits usernames but not passwords over the network; or rather, it does not directly

transmit passwords and transmits the result calculated from the password and random packet

ID by using the MD5 algorithm. Therefore, it is more secure than PAP.

•MS-CHAP—MS-CHAP is a three-way handshake authentication.

MS-CHAP differs from CHAP as follows:

{MS-CHAP is enabled by negotiating CHAP Algorithm 0x80 in LCP option 3, Authentication

Protocol.

{MS-CHAP provides authentication retry. With this mechanism, if the supplicant fails

authentication, it is allowed to retransmit authentication information to the authenticator for

reauthentication. The authenticator allows a supplicant to retransmit three times.

•MS-CHAP-V2—MS-CHAP-V2 is a three-way handshake authentication protocol.

MS-CHAP differs from CHAP as follows:

{MS-CHAP-V2 is enabled by negotiating CHAP Algorithm 0x81 in LCP option 3,

Authentication Protocol.

{MS-CHAP-V2 provides two-way authentication by piggybacking a supplicant challenge on

the Response packet and an authenticator response on the Acknowledge packet.

{MS-CHAP-V2 supports authentication retry. With this mechanism, if the supplicant fails

authentication, it is allowed to retransmit authentication information to the authenticator for

reauthentication. The authenticator allows a supplicant to retransmit three times.

{MS-CHAP-V2 supports password changing. If the supplicant fails authentication because of

an expired password, it will send the new password entered by the user to the authenticator

for reauthentication.

MP overview

Multilink PPP (MP) enables you to bind multiple PPP links into one MP bundle for increasing

bandwidth. After receiving a packet that is larger than the minimum packet size for fragmentation,

MP fragments the packet and distributes the fragments across multiple PPP links to the peer end.

After the peer end 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,

it is preferred that an MP bundle include only one type of interface.

Configuring PPP

PPP configuration task list

Task Remarks

Enabling PPP encapsulation on an interface Required.

Configuring PPP authentication Optional.

Configuring the polling interval Optional.

Configuring PPP negotiation Optional.

Enabling PPP link quality control Optional.

Enabling PPP traffic statistics collection Optional.

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

Optional.

By default, all interfaces except

Ethernet interfaces and VLAN

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 supplicant in the sequence of configured authentication modes until

the LCP negotiation succeeds. If the response packet from the supplicant carries a recommended

authentication mode, the authenticator directly uses the authentication mode if it finds the mode

configured.

Configuring PAP authentication

1. Configuring 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 local device

to authenticate the

supplicant 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 supplicant must be

configured on the authenticator.

For remote AAA authentication,

the username and password of

the supplicant 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 supplicant

must be the same as those

configured on the supplicant.

2. Configuring the supplicant

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 local device

to the authenticator when

the local device 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

local device sends null

username and password to the

authenticator.

Configuring CHAP authentication

According to whether the authenticator is configured with a username or not, the configuration of

CHAP authentication includes the following two 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 local device

to authenticate the

supplicant by using CHAP.

ppp authentication-mode

chap [ [ call-in ] domain

isp-name ]

By default, PPP authentication

is disabled.

Step Command Remarks

4. Assign a username to the

CHAP authenticator. ppp chap user username

The username you assign to the

authenticator must be the same

as the local username you

assign to the authenticator on

the supplicant.

5. Configure local or remote

AAA authentication.

For local AAA authentication,

the username and password of

the supplicant must be

configured on the authenticator.

For remote AAA authentication,

the username and password of

the supplicant must be

configured on the remote AAA

server.

For more information about

AAA authentication, see

Security Configuration Guide.

The username configured for

the supplicant must be the same

as that configured on the

supplicant.

The passwords configured for

the authenticator and supplicant

must be the same.

To configure the supplicant:

Step Command Remarks

1. Enter system view. system-view N/A

2. Enter interface view. interface interface-type

interface-number N/A

3. Assign a username to the

CHAP supplicant. ppp chap user username

The username you assign to

the supplicant here must be the

same as the local username

you assign to the supplicant on

the authenticator.

4. Configure local or remote

AAA authentication.

For local AAA authentication, the

username and password of the

supplicant must be configured on

the authenticator.

For remote AAA authentication,

the username and password of

the supplicant must be configured

on the remote AAA server.

For more information about AAA

authentication, see Security

Configuration Guide.

The username configured for

the supplicant must be the

same as that configured on the

supplicant.

The passwords configured for

the authenticator and

supplicant 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 local device to

authenticate the supplicant by

using CHAP.

ppp authentication-mode chap

[ [ call-in ] domain isp-name ]

By default, PPP

authentication is disabled.

Step Command Remarks

4. Configure local or remote AAA

authentication.

For local AAA authentication, the

username and password of the

supplicant must be configured on

the authenticator.

For remote AAA authentication,

the username and password of

the supplicant must be

configured on the remote AAA

server.

For more information about AAA

authentication, see Security

Configuration Guide.

The username configured

for the supplicant must be

the same as that

configured on the

supplicant.

The passwords

configured for the

authenticator and

supplicant must be the

same.

To configure the supplicant:

Step Command Remarks

1. Enter system view. system-view N/A

2. Enter interface view. interface interface-type

interface-number N/A

3. Assign a username to

the CHAP supplicant. ppp chap user username

The username you assign to

the supplicant must be the

same as the local username

you assign to the supplicant on

the authenticator.

4. Set the CHAP

authentication password. ppp chap password { cipher |

simple } password

The password you set for the

supplicant must be the same as

the password you set for the

supplicant on the authenticator.

Configuring MS-CHAP or MS-CHAP-V2 authentication

When you configure MS-CHAP or MS-CHAP-V2 authentication, follow these guidelines:

•In MS-CHAP or MS-CHAP-V2 authentication, an HPE device can only be an authenticator

•L2TP supports the MS-CHAP authentication but does not support the MS-CHAP-V2

authentication.

•MS-CHAP-V2 authentication supports password changing only when using RADIUS.

Depending on whether the authenticator is configured with a username, the configuration of

MS-CHAP or MS-CHAP-V2 authentication includes the following two types:

•Configuring 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 local router

to authenticate the

supplicant 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 not performed.

Other manuals for FlexNetwork MSR Series

Table of contents

Other HPE Network Router manuals

HPE

HPE FlexNetwork 5510 HI Series User manual

HPE

HPE FlexFabric 5930 Series User manual

HPE

HPE FlexNetwork VSR1000 User manual

HPE

HPE FlexNetwork VSR1000 User manual

HPE

HPE FlexNetwork HSR6800 series User manual

HPE

HPE FlexNetwork 5130 EI Series User manual

HPE

HPE 6127XLG User manual

HPE

HPE FlexNetwork 5130 Series User manual

HPE

HPE FlexNetwork HSR6600 User manual

HPE

HPE FlexNetwork MSR Series User manual

HPE

HPE FlexNetwork HSR6600 User manual

HPE

HPE MSR1000 How to use

HPE

HPE FlexFabric 7900 Series User manual

HPE

HPE FlexNetwork 6600 Installation manual

HPE

HPE FlexNetwork HSR6800 series Installation manual

HPE

HPE FlexNetwork HSR6600 User manual

HPE

HPE FlexNetwork 10500 SERIES User manual

HPE

HPE FlexNetwork HSR6800 series Installation manual

HPE

HPE FlexNetwork MSR958 User manual

HPE

HPE FlexNetwork MSR4060 User manual

HPE

HPE MSR1000 User manual

HPE

HPE FlexNetwork HSR6800 series User manual

HPE

HPE FlexNetwork 5510 HI Series User manual

HPE

HPE FlexNetwork MSR954 Installation manual

Popular Network Router manuals by other brands

Netopia

Netopia 4686-XL Specifications

Juniper

Juniper ACX5448 quick start guide

Cisco

Cisco Unified Communications Manager 8.5(1) Guide

Conel

Conel LR77 v2 SL Configuration manual

LevelOne

LevelOne GSW-2473 user manual

ADTRAN

ADTRAN NetVanta 3305 Specifications

TP-Link

TP-Link TD-W8101G Quick installation guide

Nokia

Nokia G-240W-C quick start guide

Teldat

Teldat M2 installation manual

MikroTik

MikroTik RouterBOARD 751U-2HnD Quick setup guide and warranty information

ZyXEL Communications

ZyXEL Communications ZyAIR G-3000H Firmware release notes

Bkav

Bkav QCS605 user manual

Enterasys

Enterasys X-Pedition XSR-3150 Getting started guide

D-Link

D-Link DWR-712 Quick installation guide

Onq

Onq 364772-01 user guide

ADDON

ADDON Magic r9000 Quick installation guide

Black Box

Black Box LW001A manual

Black Box

Black Box WRT750A user manual