HPE FlexNetwork MSR Series Comware 5 Layer 2 - Wan Access Configuration Manual
  1. Manuals
  2. Brands
  3. HPE Manuals
  4. Network Router
  5. FlexNetwork MSR Series
  6. Comware 5 layer 2 - wan access configuration manual

HPE FlexNetwork MSR Series Comware 5 Layer 2 - Wan Access Configuration Manual

Hide thumbs Also See for FlexNetwork MSR Series:
1
2
Table Of Contents
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
Table of Contents

Advertisement

Quick Links

Download this manual See also: Configuration 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

Advertisement

Table of Contents
loading

Related Manuals for HPE FlexNetwork MSR Series

Summary of Contents for HPE FlexNetwork MSR Series

  • Page 1: Configuration Guide

    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...
  • Page 2 © Copyright 2016 Hewlett Packard Enterprise Development LP The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.

  • Page 3: Table Of Contents

    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  ...
  • Page 4 Configuration example for accessing the Internet through an ADSL interface ········································ 56   Configuring ISDN ·························································································· 58   Overview ·························································································································································· 58   Configuring ISDN BRI ······································································································································ 59   Configuring ISDN PRI ······································································································································ 61   Configuring the negotiation parameters of ISDN layer 3 protocol ···································································· 62  ...
  • Page 5 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  ...
  • Page 6 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  ...
  • Page 7 Configuring ATM ························································································· 188   Overview ························································································································································ 188   ATM connections and ATM switching ···································································································· 188   ATM architecture ···································································································································· 189   IPoA, IPoEoA, PPPoA, and PPPoEoA ·········································································································· 190   IPoA ······················································································································································· 190   IPoEoA ··················································································································································· 190   PPPoA ···················································································································································· 190  ...
  • Page 8 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  ...
  • Page 9 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  ...
  • Page 10 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  ...
  • Page 11 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  ...

  • Page 12: Configuring Slip

    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: •...

  • Page 13: Slip Encapsulation On Synchronous/Asynchronous Interfaces Configuration Example

    SLIP encapsulation on synchronous/asynchronous interfaces configuration example Network requirements Figure 1, Router A and Router B are connected by synchronous/asynchronous interface As shown in Serial 2/0. The link layer protocol is SLIP. Figure 1 Network diagram Configuration procedure Configure Router A: # Configure interface Serial 2/0 to operate in asynchronous and protocol mode.
  • Page 14 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...

  • Page 15: Configuring Ppp And Mp

    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: •...

  • Page 16: Ppp Authentication

    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. 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).

  • Page 17: Mp Overview

    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.
  • Page 18 Configuring PAP authentication Configuring the authenticator Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Configure the local device By default, PPP authentication ppp authentication-mode pap to authenticate the [ [ call-in ] domain isp-name ] is disabled.
  • Page 19 Step Command Remarks The username you assign to the authenticator must be the same Assign a username to the as the local username you ppp chap user username CHAP authenticator. assign to the authenticator on the supplicant. For local AAA authentication, the username and password of the supplicant must be The username configured for...
  • Page 20 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.

  • Page 21: Configuring The Polling Interval

    Step Command Remarks The username you assign to the Assign a username to the authenticator here must be the MS-CHAP or same as the local username you ppp chap user username MS-CHAP-V2 assign to the authenticator on authenticator. the supplicant. For local AAA authentication, the username and password of the supplicant must be...

  • Page 22: Configuring Ppp Negotiation

    Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Optional. Configure the timer hold seconds polling interval. The default setting is 10 seconds. Configuring PPP negotiation PPP negotiation parameters that can be configured are as follows: •...
  • Page 23 Step Command Remarks interface interface-type Enter interface view. interface-number Enable IP address ip address ppp-negotiate negotiation. To configure the local end as the server when PPP authentication is not enabled: Step Command Remarks Enter system view. system-view • (Method 1) Define a global address pool and bind it to the interface: a.
  • Page 24 Step Command Remarks Optional. By default, the peer end is allowed to use the locally Disable the peer end from ppp ipcp remote-address configured IP address. In this using the locally configured forced case, the local end does not IP address. allocate an IP address to the peer end if the latter already has an IP address.
  • Page 25 Step Command Remarks By default, a device does not assign a DNS server IP address to the peer. Enable the local end to ppp ipcp dns assign a DNS server IP primary-dns-address The server specifies a DNS address to the peer. [ secondary-dns-address ] server IP address for a client only after receiving a request...
  • Page 26 payload bandwidth on the link. To ensure successful LCP negotiation, do not apply the compression to LCP packets. Hewlett Packard Enterprise recommends that you use the ACFC configuration option on low-speed links. • Configuring the local end to send ACFC requests Step Command Remarks...

  • Page 27: Enabling Ppp Link Quality Control

    Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Configure the local end to By default, the local end does send PFC requests, that is, not include the PFC option in its to include the PFC option ppp pfc local request outbound LCP negotiation in its outbound LCP...

  • Page 28: Enabling Ppp Traffic Statistics Collection

    (in terms of the number of bytes and the number of packets) on a link. The information can be used by AAA application modules for accounting and control purposes. For more information about AAA accounting, see HPE FlexNetwork MSR Router Series Comware 5 Security Configuration Guide.

  • Page 29: Configuring Mp

    Configuring MP Configuration task list You can configure MP by using VT or MP-group interfaces. • VT interface VT interfaces are used to configure VA interfaces. After bundling multiple PPP links into an MP link, create a VA interface for the MP link to exchange data with the peers. Configuring MP by using VT interfaces can involve an authentication process.
  • Page 30 • Associating a username to the virtual template. After a user passes the authentication, the system searches for the VT interface associated to the username and bundles links according to the username and the descriptor of the peer. To ensure a successful link negotiation, configure the ppp mp command and two-way authentication (PAP, CHAP, MS-CHAP, or MS-CHAP-V2) on the bundled interfaces.
  • Page 31 Step Command Remarks • (Method 1) Bind a physical interface to the VT interface: a. interface interface-type interface-number b. Specify the number of the VT interface to which the interface is to be bound, and specify that the interface operate in MP mode: ppp mp virtual-template number...
  • Page 32 • After you configure the undo ppp mp fragment enable command on an interface, the settings configured with the ppp mp lfi and ppp mp min-fragment commands become invalid on the interface. • When MP binding is based on descriptor only, users cannot be differentiated. To bind users to different MP bundles, set the binding mode to both.

  • Page 33: Configuring Mp Through An Mp-Group Interface

    Configuring MP through an MP-group interface When you configure MP through an MP-group interface, follow these guidelines: • The ppp mp max-bind command and the ppp mp min-fragment command you configured can take effect on an MP bundle only after you re-enable all the physical interfaces in the MP bundle by executing the shutdown command and then the undo shutdown command.

  • Page 34: Configuring Short Sequence Number Header Format Negotiation

    Configuring short sequence number header format negotiation By default, an MP bundle receives and transmits fragments with long sequence numbers. • To receive fragments with short sequence numbers, the local end should request the peer to transmit short sequence numbers during LCP negotiation. After the negotiation succeeds, the peer transmits fragments with short sequence numbers.

  • Page 35: Configuring Ppp Link Efficiency Mechanisms

    Step Command Remarks interface interface-type Enter interface view. interface-number Configure the MP endpoint Optional. ppp mp endpoint string char-string descriptor. Configuring PPP link efficiency mechanisms Four mechanisms are available for improving transmission efficiency on PPP links: • IP Header Compression (IPHC) •...

  • Page 36: Configuring Vj Tcp Header Compression

    Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number By default, Stac LZS compression is disabled. Stac LZS compression takes effect on a link only after you enable Stac LZS Enable Stac LZS compression at both ends of the link. ppp compression compression.

  • Page 37: Displaying And Maintaining Ppp And Mp

    Figure 3 LFI Fragmentation Large packet Output queue Traffic Voice packet classifying To configure LFI: Step Command Remarks Enter system view. system-view • interface virtual-template Enter VT interface view or number MP-group interface view. • interface mp-group mp-number Enable LFI. By default, LFI is disabled.

  • Page 38: Ppp And Mp Configuration Examples

    Task Command Remarks display ppp mp [ interface interface-type Display information about an MP interface-number ] [ | { begin | exclude | Available in any view. interface. include } regular-expression ] display ppp compression iphc tcp Display the statistics on TCP [ interface-type interface-number ] [ | Available in any view.
  • Page 39 [RouterA-luser-userb] quit # Enable PPP encapsulation on Serial 2/0. [RouterA] interface serial 2/0 [RouterA-Serial2/0] link-protocol ppp # Set the authentication mode to PAP. [RouterA-Serial2/0] ppp authentication-mode pap domain system # Assign an IP address to Serial 2/0. [RouterA-Serial2/0] ip address 200.1.1.1 16 [RouterA-Serial2/0] quit # Configure local authentication for the PPP users in the default ISP domain system.

  • Page 40: Two-Way Pap Authentication Configuration Example

    --- 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 Two-way PAP authentication configuration example Network requirements Figure 5, Router A and Router B are interconnected through their Serial 2/0 interfaces. As shown in Configure Router A and Router B to authenticate each other.
  • Page 41 [RouterB-luser-usera] password simple passa # Set the service type of the user account to PPP. [RouterB-luser-usera] service-type ppp [RouterB-luser-usera] quit # Enable PPP encapsulation on Serial 2/0. [RouterB] interface serial 2/0 [RouterB-Serial2/0] link-protocol ppp # Set the authentication mode to PAP. [RouterB-Serial2/0] ppp authentication-mode pap domain system # Configure the PAP username and password sent from Router B to Router A when Router B is authenticated by Router A using PAP.

  • Page 42: One-Way Chap Authentication Configuration Example

    0.00% packet loss round-trip min/avg/max = 1/23/103 ms One-way CHAP authentication configuration example Network requirements Figure 6, configure Router A to authenticate Router B by using CHAP. As shown in Figure 6 Network diagram Configuration procedure (Method 1) The authenticator configured with a username authenticates the supplicant by using CHAP.
  • Page 43 # Enable PPP encapsulation on Serial 2/0. [RouterB] interface serial 2/0 [RouterB-Serial2/0] link-protocol ppp # Configure the username for Router B when Router B is authenticated. [RouterB-Serial2/0] ppp chap user userb # Assign an IP address to Serial 2/0 of Router B. [RouterB-Serial2/0] ip address 200.1.1.2 16 (Method 2) The authenticator with no username configured authenticates the supplicant by using CHAP.

  • Page 44: Ppp Ip Address Negotiation Configuration Example

    Link layer protocol is PPP LCP opened, IPCP opened 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 Interface is V35 206 packets input, 2496 bytes 206 packets output, 2492 bytes [RouterB-Serial2/0] ping 200.1.1.1...

  • Page 45: Mp Configuration Example

    Verify the configuration: # After the configuration is complete, display summary information about Serial 2/0 on Router [RouterB-Serial2/0] display interface serial 2/0 brief The brief information of interface(s) under route mode: Link: ADM - administratively down; Stby - standby Protocol: (s) - spoofing Interface Link Protocol Main IP Description...
  • Page 46 Figure 8 Network diagram Configuration procedure Configure Router A: # Create user accounts for Router B and Router C and set the passwords. <RouterA> system-view [RouterA] local-user router-b [RouterA-luser-router-b] password simple router-b [RouterA-luser-router-b] service-type ppp [RouterA-luser-router-b] quit [RouterA] local-user router-c [RouterA-luser-router-c] password simple router-c [RouterA-luser-router-c] service-type ppp [RouterA-luser-router-c] quit...
  • Page 47 # Create a user account for Router A. <RouterB> system-view [RouterB] local-user router-a [RouterB-luser-router-a] password simple router-a [RouterB-luser-router-a] service-type ppp [RouterB-luser-router-a] quit # Create a VT interface for the user and specify to use the NCP information of this interface for PPP negotiation.

  • Page 48: Mp Binding Mode Configuration Examples

    MP binding mode configuration examples Network requirements Figure 9, bind the links in the three MP binding modes. As shown in Figure 9 Network diagram Configuration procedure (Method 1) Directly bind the physical interfaces to a VT interface. Configure Router A: # Configure the username and password of Router B.
  • Page 49 # Configure the username and password of Router A. <RouterB> system-view [RouterB] local-user rta [RouterB-luser-rta] password simple rta [RouterB-luser-rta] service-type ppp [RouterB-luser-rta] quit # Create a VT interface and assign an IP address to it. [RouterB] interface virtual-template 1 [RouterB-Virtual-Template1] ip address 8.1.1.2 24 [RouterB-Virtual-Template1] ppp mp binding-mode authentication [RouterB-Virtual-Template1] quit # Configure Serial 2/1.
  • Page 50 Link layer protocol is PPP LCP opened, MP opened, IPCP opened, OSICP opened Physical is MP, baudrate: 64000 bps 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 Last 300 seconds input: 0 bytes/sec 0 packets/sec...
  • Page 51 [RouterA-Serial2/1] ppp authentication-mode pap domain system [RouterA-Serial2/1] ppp pap local-user rta password simple rta [RouterA-Serial2/1] ppp mp [RouterA-Serial2/1] shutdown [RouterA-Serial2/1] undo shutdown [RouterA-Serial2/1] quit # Configure Serial 2/0. [RouterA] interface serial 2/0 [RouterA-Serial2/0] link-protocol ppp [RouterA-Serial2/0] ppp authentication-mode pap domain system [RouterA-Serial2/0] ppp pap local-user rta password simple rta [RouterA-Serial2/0] ppp mp [RouterA-Serial2/0] shutdown...
  • Page 52 [RouterB-Serial2/0] shutdown [RouterB-Serial2/0] undo shutdown [RouterB-Serial2/0] quit # Configure the user in the domain to use the local authentication scheme. [RouterB] domain system [RouterB-isp-system] authentication ppp local [RouterB-isp-system] quit Verify the configuration on Router A: <RouterA> display ppp mp Template is Virtual-Template1 Bundle rtb, 2 member, Master link is Virtual-Template1:0 0 lost fragments, 0 reordered, 0 unassigned, 0 interleaved, sequence 0/0 rcvd/sent...
  • Page 53 --- 8.1.1.1 ping statistics --- 5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 29/30/31 ms When you bind interfaces Serial 2/1 and Serial 2/0 to the same MP, if you configure one interface as ppp mp and the other as ppp mp virtual-template 1, the system will bind the two interfaces to different MPs.
  • Page 54 [RouterB] local-user rta [RouterB-luser-rta] password simple rta [RouterB-luser-rta] service-type ppp [RouterB-luser-rta] quit # Create an MP-group interface and assign an IP address to it. [RouterB] interface mp-group 1 [RouterB-Mp-group1] ip address 111.1.1.2 24 [RouterB-Mp-group1] quit # Configure Serial 2/1. [RouterB] interface serial 2/1 [RouterB-Serial2/1] link-protocol ppp [RouterB-Serial2/1] ppp authentication-mode pap domain system [RouterB-Serial2/1] ppp pap local-user rtb password simple rtb...

  • Page 55: Troubleshooting Ppp Configuration

    Physical is MP Output queue : (Urgent queue : Size/Length/Discards) 0/500/0 Output queue : (FIFO queuing : Size/Length/Discards) 0/75/0 5 minutes input rate 0 bytes/sec, 0 packets/sec 5 minutes output rate 0 bytes/sec, 0 packets/sec 5 packets input, 58 bytes, 0 drops 5 packets output, 54 bytes, 0 drops # Ping the IP address 111.1.1.2 on Router A.
  • Page 56 • —Indicates that the interface is not activated serial number is down, line protocol is down or the physical layer has not gone up yet. • —Indicates that LCP negotiation succeeded. serial number is up, line protocol is up • —Indicates that the interface is active, but LCP serial number is up, line protocol is down negotiation failed.

  • Page 57: Configuring Pppoe

    Configuring PPPoE "Configuring a PPPoE server" for the configuration When the device serves as a PPPoE server, see procedure. "Configuring a PPPoE client" for the configuration When the device serves as a PPPoE client, see procedure. Overview Point-to-Point Protocol over Ethernet (PPPoE) extends PPP by transporting PPP packets encapsulated in Ethernet over point-to-point links.

  • Page 58: Protocols And Standards

    billing and control. The host must be installed with PPPoE client dialup software. This network structure is applicable to campus and residential environments. Figure 11 Network structure 2 PPPoE client Host A PPPoE server Internet PPPoE client Router Host B Protocols and standards RFC 2516, A Method for Transmitting PPP Over Ethernet (PPPoE) Configuring a PPPoE server...

  • Page 59: Configuring A Pppoe Client

    Step Command Remarks Return to system view. quit 10. Set the maximum number of Optional. pppoe-server max-sessions PPPoE sessions allowed for remote-mac number 100 by default. a peer MAC address. 11. Set the maximum number of Optional. pppoe-server max-sessions PPPoE sessions allowed for local-mac number 100 by default.

  • Page 60: Configuring A Pppoe Session

    You can also configure PPP authentication or set other parameters on the dialer interface as needed. For more information about dialer interfaces, see "Configuring DCC." For information about more IPv6-related commands, see HPE FlexNetwork MSR Router Series — Comware 5 Layer 3 IP Services Command Reference.

  • Page 61: Displaying And Maintaining Pppoe

    Step Command Remarks Enter system view. system-view interface interface-type Enter Ethernet interface view. interface-number Configure the PPPoE session The default is 10 pppoe-client timer negotiation negotiation timer. seconds. seconds By default, no PPPoE sessions are created. You can establish multiple PPPoE sessions Create a PPPoE session, and pppoe-client dial-bundle-number on an Ethernet interface.
  • Page 62 Figure 12 Network diagram Configuration procedure Configure CHAP authentication: # Add a PPPoE user. <Router> system-view [Router] local-user user1 [Router-luser-user1] password simple pass1 [Router-luser-user1] service-type ppp [Router-luser-user1] quit # Configure virtual-template 1 on the Router. [Router] interface virtual-template 1 [Router-Virtual-Template1] ppp authentication-mode chap domain system [Router-Virtual-Template1] ppp chap user user1 [Router-Virtual-Template1] remote address pool 1 [Router-Virtual-Template1] ip address 1.1.1.1 255.0.0.0...

  • Page 63: Pppoe Client Configuration Example

    If you specify the authentication scheme as radius-scheme or hwtacacs-scheme by using the authentication ppp command, you must configure RADIUS/HWTACACS settings to enable AAA. For more information, see HPE FlexNetwork MSR Router Series Comware 5 Security Configuration Guide. PPPoE client configuration example...
  • Page 64 Configure Router B as the PPPoE client: <RouterB> system-view [RouterB] dialer-rule 1 ip permit [RouterB] interface dialer 1 [RouterB-Dialer1] dialer user user2 [RouterB-Dialer1] dialer-group 1 [RouterB-Dialer1] dialer bundle 1 [RouterB-Dialer1] ip address ppp-negotiate [RouterB-Dialer1] ppp pap local-user user2 password simple hello [RouterB-Dialer1] quit # Configure the PPPoE session.

  • Page 65: Configuration Example For Connecting A Lan To The Internet Using An Adsl Modem

    Configuration example for connecting a LAN to the Internet using an ADSL modem Network requirements Figure As shown in • Router A provides Internet access for Host A, Host B, and Host C. It connects to DSLAM through an ADSL modem and a permanent PPPoE session. •...
  • Page 66 [RouterA] ip route-static 0.0.0.0 0 dialer 1 If the IP addresses of the hosts in the LAN are private addresses, configure NAT on Router A. For more information about NAT, see HPE FlexNetwork MSR Router Series Comware 5 Layer 3—IP Services Configuration Guide.

  • Page 67: Configuration Example For Using Adsl To Provide Backup Connections

    Configuration example for using ADSL to provide backup connections Network requirements Figure 15, Router is connected to Network Center through a DDN dedicated line and an As shown in ADSL connection, where the ADSL connection provides backup for the DDN dedicated line. When the DDN dedicated line fails, the Router initiates a PPPoE call to establish an ADSL connection to the Network Center on the demand of data transmitting.
  • Page 68 Figure 16 Network diagram Configuration procedure # Configure a dialer interface. <Router> system-view [Router] dialer-rule 1 ip permit [Router] interface dialer 1 [Router-Dialer1] dialer user mypppoe [Router-Dialer1] dialer-group 1 [Router-Dialer1] dialer bundle 1 [Router-Dialer1] ip address ppp-negotiate # Configure interface VE 1. [Router-Dialer1] interface virtual-ethernet 1 [Router-Virtual-Ethernet1] mac-address 0001-0002-0003 [Router-Virtual-Ethernet1] quit...

  • Page 69: Configuring Isdn

    Configuring ISDN The MSR900 and MSR93X(except the JG597A) routers do not support ISDN BRI interfaces. Overview Integrated Services Digital Network (ISDN) evolved from IDN. It provides end-to-end digital connectivity and supports an extensive range of services, covering both voice and non-voice services.

  • Page 70: Configuring Isdn Bri

    • 14-digit SPID (Generic SPID Format). The former 10 digits are entered by the user, and the latter 4 digits can only be 0101. • Allocate by Stored Program Control Switching System (SPCS) through automated SPID selection regulation. The former two ways to obtain SPID are regarded as static configuration methods, and the third one is taken as dynamic negotiation method.
  • Page 71 Step Command Remarks "Configuring ISDN B channel 13. Configure ISDN B channel Optional. selection mode. selection mode." "Configuring the sliding 14. Configure ISDN BRI sliding Optional. window size. window size on a BRI interface." 15. Configure statistics about "Collecting ISDN message ISDN message receiving Optional.

  • Page 72: Configuring Isdn Pri

    Configuring ISDN PRI Step Command Remarks Enter system view. system-view Optional. Configure PRI interfaces to By default, a PRI interface send ISDN RESTART isdn send-restart actively sends ISDN RESTART messages actively. messages to the peer end before B channel maintenance. Enter ISDN PRI interface interface interface-type view.

  • Page 73: Configuring The Negotiation Parameters Of Isdn Layer 3 Protocol

    Step Command Remarks "Configuring ISDN to carry 16. Configure ISDN to carry the Calling-Name field in the Calling-Name field in outgoing Optional. outgoing packets. packets." "Configuring ISDN to carry 17. Configure ISDN to carry the Connected-Name field in the Connected-Name field in Optional.
  • Page 74 Step Command Remarks Optional. Disable ISDN from carrying By default, HLC information the HLC information element isdn ignore hlc element is carried in SETUP in SETUP messages when messages when placing voice placing voice calls. call. Optional. Disable ISDN from carrying By default, LLC information the LLC information element isdn ignore llc...
  • Page 75 Step Command Remarks Optional. Set the type and code By default, the system selects isdn number-property scheme of calling or called ISDN number type and code number-property [ calling | numbers in incoming or scheme depending on upper layer called ] [ in | out ] outgoing ISDN calls.
  • Page 76 Field (Bit) value Protocol Definition Type Code scheme Unknown International number National number Network specific number Subscriber number Abbreviated number Reserved for extension DSS1 Unknown ISDN/telephony numbering plan (Recommendation E.164) Data numbering plan (Recommendation X.121) Telex numbering plan (Recommendation F.69) National standard numbering plan Private numbering plan Reserved for extension...

  • Page 77: Configuring The Isdn Q.931 Protocol Version

    Field (Bit) value Protocol Definition Type Code scheme Local (directory) number in ISDN numbering plan (Recommendation E.164) Abbreviated number in private numbering plan Unknown National number Network specific number Subscriber number Unknown ISDN/telephony numbering plan (Recommendation E.164) Private numbering plan Unknown number in Unknown numbering plan Unknown number in ISDN/Telephony numbering plan (ITU-T Recommendation E.164/E.163)

  • Page 78: Configuring The Spid Of The Isdn Ni Protocol

    Configuring the SPID of the ISDN NI protocol You can configure SPID on the BRI interfaces that are running the ISDN NI protocol. To configure the SPID parameters of the ISDN NI protocol: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view.

  • Page 79: Configuring An Interface To Send Calling Number During An Outgoing Call

    Step Command Remarks interface interface-type Enter interface view. interface-number Optional. No called number or subaddress Set the called number or isdn check-called-number is configured by default. When subaddress to be checked check-index called-party-number you configure this command, the during a digital incoming call. [ : subaddress ] called number and subaddress are separated with string "space:...

  • Page 80: Configuring Isdn B Channel Selection Mode

    Step Command Remarks Local ISDN B channel management is not configured and the remote end is responsible for B channel management by default. Exclusive local management mode for ISDN B channels is Set the local management isdn bch-local-manage applied to the network side for the ISDN B channel.

  • Page 81: Configuring The Sliding Window Size On A Pri Interface

    Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Optional. Configure the sliding window isdn bri-slipwnd-size The sliding window on the BRI size on the BRI interface. window-size interface defaults to 1. Configuring the sliding window size on a PRI interface Frames in the Q.921 buffer are sent in sequence.

  • Page 82: Configuring An Interface To Check The Calling Number When An Incoming Call Comes

    Step Command Remarks Clear ISDN statistics. Optional. isdn statistics clear Configuring an interface to check the calling number when an incoming call comes Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Configure the interface to check the calling number Execute this command to isdn caller-number...

  • Page 83: Configuring Isdn To Carry The Connected-Name Field In Outgoing Packets

    Step Command Remarks Optional. Configure ISDN to carry the By default, ISDN does not carry the Calling-Name field in isdn carry calling-name Calling-Name field in outgoing outgoing packets. packets. Configuring ISDN to carry the Connected-Name field in outgoing packets Step Command Remarks Enter system view.

  • Page 84: Setting The Progress Indicator Value In Isdn Signaling Messages

    Step Command Description Enter system view. system-view interface interface-type Enter interface view. interface-number Configure the service type in Optional. isdn service [ audio | data | the ISDN bearer compatibility speech ] The default service type is speech. signaling. Setting the progress indicator value in ISDN signaling messages Step Command...

  • Page 85: Configuring Permanent Link Function At Isdn Bri Link Layer

    Step Command Remarks No B channel on the ISDN BRI Configure the B channel for dialer isdn-leased { number | interface is configured for leased ISDN leased line connection. 128k } line connection by default. Configuring permanent link function at ISDN BRI link layer With the isdn q921-permanent command, the BRI interface sets up a data link connection automatically and maintain the connection even when no calls are received from the network layer.

  • Page 86: Configuring Deactivation Protection For An Isdn Bri Interface

    Step Command Remarks Enter system view. system-view Enter BRI interface view. interface bri interface-number Optional. Configure the BRI interface By default, a BRI interface is not to be in permanent active permanent-active in permanent active state on state on physical layer. physical layer.

  • Page 87: Configuring Isdn Call Check

    [ call-clear | call-setup | the ISDN module. Enabled by default. lapd-status ] For more information about the snmp-agent trap enable isdn command, see HPE FlexNetwork MSR Router Series Comware 5 Network Management and Monitoring Command Reference. Displaying and maintaining ISDN Task...

  • Page 88: Isdn Configuration Examples

    Task Command Remarks display isdn parameters { protocol | interface Display the system parameters of interface-type interface-number ] ISDN protocol Layer 2 and Layer Available in any view. [ | { begin | exclude | include } 3 running on the interface. regular-expression ] regular-expression ] display isdn spid interface...

  • Page 89: Connecting Routers Through Isdn Bri Lines Running Ni

    Configure Router B: Follow the same procedures to configure Router B. Connecting routers through ISDN BRI lines running NI Network requirements Figure 19, Router A is connected to Router B through NI protocol of ISDN BRI lines. As shown in Figure 19 Network diagram Router A BRI2/0...

  • Page 90: Configuring Isdn 128K Leased Lines

    Figure 20 Network diagram Configuration procedure Configure Router A: <RouterA> system-view [RouterA] interface bri 2/0 [RouterA-Bri2/0] link-protocol ppp [RouterA-Bri2/0] ppp mp virtual-template 5 [RouterA-Bri2/0] dialer enable-circular [RouterA-Bri2/0] dialer isdn-leased 0 [RouterA-Bri2/0] dialer isdn-leased 1 [RouterA-Bri2/0] quit [RouterA] interface virtual-template 5 [RouterA-Virtual-Template5] ip address 202.38.154.1 255.255.0.0 Configure Router B: <RouterB>...

  • Page 91: Figure 21 Network Diagram

    Figure 21 Network diagram Configuration procedure Configure Router A: <RouterA> system-view [RouterA] dialer-rule 1 ip permit [RouterA] interface bri 2/0 [RouterA-Bri2/0] ip address 100.1.1.1 255.255.255.0 [RouterA-Bri2/0] link-protocol ppp [RouterA-Bri2/0] dialer enable-circular [RouterA-Bri2/0] dialer-group 1 [RouterA-Bri2/0] dialer isdn-leased 128k Configure Router B: <RouterB>...
  • Page 92 2 errors, 0 runts, 0 giants, 2 CRC, 0 align errors, 0 overruns, 0 dribbles, 0 aborts, 0 no buffers 0 frame errors Output:0 packets, 0 bytes 0 errors, 0 underruns, 0 collisions 0 deferred <RouterA> display interface bri 2/0:1 Bri2/0:1 current state :UP Line protocol current state :UP (spoofing) Description : Bri2/0:1 Interface...

  • Page 93: Interoperating With Dms100 Switches

    0 dribbles, 0 aborts, 0 no buffers 0 frame errors Output:16634 packets, 201465 bytes 0 errors, 0 underruns, 0 collisions 0 deferred As you can see, the state of interface Bri 2/0:1 is up, its speed is 128 kbps, and channels (timeslots used) B1 and B2 are in use;...

  • Page 94: Troubleshooting

    [Router-Bri2/0] isdn spid service speech [Router-Bri2/0] quit # Configure a dialer interface. [Router] interface dialer 1 [Router-Dialer1] link-protocol ppp [Router-Dialer1] ppp pap local-user user password simple hello [Router-Dialer1] dialer threshold 0 in-out [Router-Dialer1] ppp mp [Router-Dialer1] ip address ppp-negotiate [Router-Dialer1] dialer enable-circular [Router-Dialer1] dialer-group 1 [Router-Dialer1] dialer number 8810148 [Router-Dialer1] quit...
  • Page 95 • Check whether the dial-up configuration is correct. If dial-up is correctly configured and the maintaining information "Q921 send data fail (L1 return failure)." is not output, the ISDN line might be not connected well.

  • Page 96: Configuring Frame Relay

    Configuring frame relay The MSR 900 routers do not support frame relay. Of the MSR93X series routers, only the JG514A, JG514B, JG515A, JG531A and JG531B routers support frame relay. Overview Frame relay is essentially simplified X.25 WAN technology. It uses statistical multiplexing technology and can establish multiple virtual circuits over a single physical cable to make full use of network bandwidth.

  • Page 97: Data Link Connection Identifier

    • Permanent virtual circuits (PVCs)—Preconfigured by network administrators and maintain until being manually removed. • Switched virtual circuits (SVCs)—Analogous to dialup connections. They are dynamically set up or cleared on an as-needed basis through protocol negotiation. PVCs are used far more than SVCs. Data link connection identifier A DLCI is a unique number assigned to a virtual circuit endpoint in a frame relay network for the addressing purpose.

  • Page 98: Typical Application Scenarios

    • ANSI T1.617 Annex D • Nonstandard LMI (compatible with other vendors) To communicate, the DTE and the DCE must use the same type of LMI. LMI uses the status inquiry message and the status messages to maintain the link status and PVC status, for example, to advertise new PVCs, detect deleted PVCs, monitor PVC status changes, and verify link integrity.

  • Page 99: Hardware Compatibility With Frame Relay

    Figure 24 Interconnecting LANs through a frame relay cloud Figure 25 Interconnecting LANs through a dedicated line Hardware compatibility with frame relay Frame relay is not available on the following routers: • MSR900. • MSR93X except for JG514A, JG514B, JG515A, JG531A and JG531B. Frame relay configuration task list Task Remarks...

  • Page 100: Configuring Dte Side Frame Relay

    Task Remarks Configuring Annex G Optional Marking the DE bit Optional Configuring frame relay fragmentation Optional Enabling the trap function Optional You can configure an NNI interface in the same way a DCE interface is configured. For the "Configuring DCE side frame relay."...
  • Page 101 • Use InARP or IND to dynamically create mappings between peer IP addresses and local DLCIs. Use this method in complicated networks and make sure the peer device also supports InARP or IND. Configuration guidelines • Do not configure DLCIs for PVCs if IPv4 or IPv6 static address mappings are configured. •...

  • Page 102: Configuring A Frame Relay Local Virtual Circuit

    Step Command Remarks interface interface-type Enter interface view. interface-number Optional. Enable IND for IPv6 dynamic By default, IND is enabled for frame relay address fr ipv6 ind [ dlci-number ] IPv6 dynamic frame relay mappings. address mappings. Optional. Set the IND packet By default, the IND packet transmission interval after ipv6 ind holdtime time-value...

  • Page 103: Configuring Annex G

    A P2P subinterface connects a single remote device and a P2MP subinterface connects multiple remote devices. A P2MP subinterface can be configured with multiple virtual circuits, each of which sets up an address map with its connected remote network address to distinguish different connections.

  • Page 104: Marking The De Bit

    Step Command Remarks Enable frame relay encapsulation on the link-protocol fr [ ietf | nonstandard ] The default setting is PPP. interface. This operation also leads you to interface DLCI view. Create a virtual fr dlci dlci-number circuit. By default, no virtual circuit is created on an interface.

  • Page 105: Configuring Frame Relay Fragmentation

    Associate the FR class with the FR PVC: fr-class class-name For more information about configuring traffic classes, traffic behaviors, and QoS policies, see HPE FlexNetwork MSR Router Series Comware 5 ACL and QoS Configuration Guide. For more information about configuring FR classes, see HPE FlexNetwork MSR Router Series Comware 5 ACL and QoS Configuration Guide.

  • Page 106: Configuring Dce Side Frame Relay

    The FRF.12 fragmentation function is mutually exclusive with FRTS configured by using the fr traffic-shaping command. For more information about FRTS, see HPE FlexNetwork MSR Router Series Comware 5 ACL and QoS Configuration Guide.

  • Page 107: Configuring Frame Relay Address Mapping On The Dce Side

    Step Command Remarks Optional. Configure network side fr lmi t392dce t392-value T392. The default setting is 15 seconds. Configuring frame relay address mapping on the DCE side "Configuring frame relay address mappings." Configuring frame relay local virtual circuit on the DCE side "Configuring a frame relay local virtual circuit."...

  • Page 108: Configuring Frame Relay Over Ip

    Step Command Remarks Configure a PVC b. fr switch name interface for frame relay interface-type A PVC created in this switching in system interface-number dlci dlci1 method is bidirectional. view. interface interface-type interface-number dlci dlci2 Optional. Enter frame relay switching c.

  • Page 109: Configuring Annex G

    • The virtual circuit must be assigned the same DLCI (out-dlci) on the tunnel interfaces at both ends of the GRE tunnel. Configuration procedure To configure frame relay over IP: Step Command Remarks 14. Enter system view. system-view 15. Create a tunnel interface For more information about creating and in system view and configuring a tunnel interface, see Layer...

  • Page 110: Configuring Frame Relay Fragmentation

    By default, trap is enabled relay. for frame relay. For more information about the snmp-agent trap enable fr command, see HPE FlexNetwork MSR Router Series Comware 5 Network Management and Monitoring Command Reference. Displaying and maintaining frame relay Task...

  • Page 111: Frame Relay Configuration Examples

    Task Command Remarks display fr statistics [ interface Display incoming and outgoing interface-type interface-number ] [ | Available in any view. frame relay data statistics. { begin | exclude | include } regular-expression ] display fr pvc-info [ interface interface-type { interface-number | Display frame relay permanent interface-number.subnumber } ] Available in any view.
  • Page 112 Figure 27 Network diagram Configuration procedure Configure Router A: # Assign an IP address to interface Serial 2/0. <RouterA> system-view [RouterA] interface serial 2/0 [RouterA-Serial2/0] ip address 202.38.163.251 255.255.255.0 # Enable frame relay on the interface. [RouterA-Serial2/0] link-protocol fr [RouterA-Serial2/0] fr interface-type dte # If the peer router supports InARP, configure dynamic address mappings.

  • Page 113: Connecting Lans Through A Frame Relay Network (Ipv6)

    # If the peer router supports InARP, configure dynamic address mappings. [RouterC-Serial2/0] fr inarp # Otherwise, configure a static address mapping. [RouterC-Serial2/0] fr map ip 202.38.163.251 80 Connecting LANs through a frame relay network (IPv6) Network requirements Figure 27, connect LANs through a public frame relay network. The routers can only As shown in operate as DTE.

  • Page 114: Connecting Lans With A Dedicated Line

    [RouterB-Serial2/0] fr inarp # Otherwise, configure a static address mapping. [RouterB-Serial2/0] fr map ip 202.38.163.251 70 Configure Router C: # Assign an IP address to interface Serial 2/0. <RouterC> system-view [RouterC] interface serial 2/0 [RouterC-Serial2/0] ip address 202.38.163.253 255.255.255.0 # Enable frame relay on the interface. [RouterC-Serial2/0] link-protocol fr [RouterC-Serial2/0] fr interface-type dte # If the peer router supports IND, configure dynamic address mappings.

  • Page 115: Connecting Lans Through An Annex G Dlci

    [RouterB-Serial2/0] fr interface-type dte Method 2: On subinterfaces Configure Router A: # Enable frame relay on interface Serial 2/0 and configure the interface to operate in DCE mode. <RouterA> system-view [RouterA] interface serial 2/0 [RouterA-Serial2/0] link-protocol fr [RouterA-Serial2/0] fr interface-type dce [RouterA-Serial2/0] quit # Configure the IP address and DLCI of the subinterface Serial 2/0.1.

  • Page 116: Troubleshooting Frame Relay

    [RouterA-x25-vofr] x25 map ip 202.38.163.252 x121-address 20094 [RouterA-x25-vofr] quit # Assign an IP address to the local interface. [RouterA] interface serial 2/0 [RouterA–Serial2/0] ip address 202.38.163.251 255.255.255.0 # Enable frame relay on the interface and configure the interface to operate in DCE mode. [RouterA–Serial2/0] link-protocol fr [RouterA–Serial2/0] fr interface-type dce # Create a PVC.
  • Page 117 Solution Check the following items: • Check the physical line. • Check that the remote device is working correctly. Symptom 2 The physical layer is already up, but the link layer protocol is down. Solution Check the following items: • Frame relay is enabled on the peer devices.

  • Page 118: Configuring Frame Relay Compression

    Configuring frame relay compression Overview Frame relay compression technique compresses frame relay packets to save network bandwidth, reduces network load, and improves the data transfer efficiency on the frame relay network. The device supports FRF.9 stac compression (called FRF.9) and FRF.20 IPHC (called FRF.20). FRF.9 FRF.9 classifies packets into two types: control packets and data packets.

  • Page 119: Configuration Procedure

    Configuration procedure To configure FRF.9 compression: Step Command Remarks Enter system view. system-view interface interface-type interface-number Enter frame relay interface or subinterface view. interface serial interface-number.subnumber Optional. Configure By default, For P2P subinterface, enable FRF.9 fr compression frf9 FRF.9 FRF.9 compression. compressio compression is n (use...

  • Page 120: Displaying And Maintaining Frame Relay Compression

    Displaying and maintaining frame relay compression Task Command Remarks display fr compress [ interface Display statistics about FRF.9 interface-type interface-number ] Available in any view. compression. [ | { begin | exclude | include } regular-expression ] display fr iphc [ interface Display statistics about FRF.20 IP interface-type interface-number ] Available in any view.

  • Page 121: Frame Relay Frf.20 Ip Header Compression Configuration Example

    # Configure interface Serial 2/0 to operate in DTE mode. [RouterB-Serial2/0] fr interface-type dte # Create an IP address map entry and enable FRF.9 compression on interface Serial 2/0. [RouterB-Serial2/0] fr map ip 10.110.40.1 100 compression frf9 Verifying the configuration # Ping Router B from Router A.
  • Page 122 [RouterA-Serial2/0] link-protocol fr # Configure an IP address for interface Serial 2/0. [RouterA-Serial2/0] ip address 10.1.1.1 24 # Configure interface Serial 2/0 to operate in DTE mode. [RouterA-Serial2/0] fr interface-type dte [RouterA-Serial2/0] quit # Configure a static route, setting the destination IP address to 12.1.1.2/24 and next hop IP address to 10.1.1.2.
  • Page 123 [RouterB-Serial2/0] fr compression iphc [RouterB-Serial2/0] fr iphc tcp-include [RouterC-Serial2/0] quit # Configure a static route, setting the destination IP address to 10.1.1.1/24 and next hop IP address to 12.1.1.1. [RouterC] ip route-static 10.1.1.1 24 12.1.1.1 Verifying the configuration # Telnet to Router C from Router A. <RouterA>...

  • Page 124: Configuring Multilink Frame Relay

    Configuring multilink frame relay Overview Multilink frame relay (MFR) is a cost effective bandwidth solution. It is based on the FRF.16 protocol of the frame relay forum and implemented on DTE/DCE interfaces. MFR provides MFR interfaces, a type of logical interface. An MFR interface is formed by a bundle of frame relay physical links to provide high transmission speed and bandwidth beyond the capabilities of a single link.

  • Page 125: Configuring An Mfr Bundle Link

    Step Command Remarks Optional. Enable MFR mfr fragment By default, MFR fragmentation is fragmentation. disabled. Optional. Configure the size of By default, the size of the MFR sliding the MFR sliding mfr window-size number window is equal to the number of window.

  • Page 126: Multilink Frame Relay Configuration Examples

    Task Command Remarks Display configuration and display mfr [ interface interface-type statistics of an MFR bundle interface-number | verbose ] [ | { begin | Available in any view. and bundle links. exclude | include } regular-expression ] reset counters interface [ mfr Clear statistics of MFR [ interface-number | Available in user view.

  • Page 127: Mfr Switched Connection Configuration Example

    # Bundle Serial 2/0 and Serial 2/1 to MFR4. [RouterB] interface serial 2/0 [RouterB-Serial2/0] link-protocol fr mfr 4 [RouterB-Serial2/0] quit [RouterB] interface serial 2/1 [RouterB-Serial2/1] link-protocol fr mfr 4 MFR switched connection configuration example Network requirements Figure 35, Router A and Router C are connected through MFR to Router B where MFR As shown in switching is enabled.
  • Page 128 [RouterB-MFR2] quit # Add Serial 2/0 and Serial 2/1 to interface MFR1. [RouterB] interface serial 2/0 [RouterB-Serial2/0] link-protocol fr mfr 1 [RouterB] quit [RouterB] interface serial 2/1 [RouterB-Serial2/1] link-protocol fr mfr 1 [RouterB-Serial2/1] quit # Add Serial 2/2 and Serial 2/3 to interface MFR2. [RouterB] interface serial 2/2 [RouterB-Serial2/2] link-protocol fr mfr 2 [RouterB-Serial 2/2] quit...

  • Page 129: Configuring Pppofr

    Configuring PPPoFR PPP over frame relay (PPPoFR) enables routers to establish end-to-end PPP sessions on a frame relay network, allowing frame relay stations to use PPP features such as LCP, NCP, authentication, and MP fragmentation. Configuration procedure To configure PPPoFR: Step Command Remarks...

  • Page 130: Pppofr Configuration Example

    PPPoFR configuration example Network requirements Figure 36, Router A and Router B connect through the frame relay network. Enable As shown in PPPoFR between them. Figure 36 Network diagram 10.1.1.2/8 10.1.1.1/8 S2/0 S2/0 Router A Router B Configuration procedure Configure Router A: # Create and configure virtual template interface Virtual-Template 1.

  • Page 131: Configuring Mpofr

    To ensure transmission quality over virtual template interfaces, configure queue-independent QoS features on the virtual interfaces and queue-dependent QoS features on the FR interface. For more information, see HPE FlexNetwork MSR Router Series Comware 5 ACL and QoS Configuration Guide.

  • Page 132: Mpofr Configuration Example

    Step Command Remarks 13. Map the frame relay fr map ppp dlci-number interface DLCI to the PPPoFR virtual-template interface-number virtual template. In system view, repeat steps 6 to 14. Return to system view. 13 to configure multiple PPPoFR quit virtual templates. MPoFR configuration example Network requirements Figure...
  • Page 133 Configure Router A: # Create Virtual-Template 1 for PPPoFR and bind it to the MP template Virtual-Template 3. <RouterA> system-view [RouterA] interface virtual-template 1 [RouterA-Virtual-Template1] ppp mp virtual-template 3 [RouterA-Virtual-Template1] quit # Create Virtual-Template 2 for PPPoFR and bind it to the MP template Virtual-Template 3. [RouterA] interface virtual-template 2 [RouterA-Virtual-Template2] ppp mp virtual-template 3 [RouterA-Virtual-Template2] quit...

  • Page 134: Configuring Dcc

    Configuring DCC Overview Dial Control Center (DCC) is a routing technology used when routers interconnect through a public switched network, such as a PSTN or an ISDN. It can provide the dial-on-demand service where any two routers dial to set up a connection when data needs transferring instead of setting up a connection before that.
  • Page 135 Figure 38 Association between physical interfaces and dialer interfaces Figure 38, a physical interface can be assigned to only one dialer interface, but each dialer interface can contain multiple physical interfaces and be mapped to multiple destination addresses. In addition, a physical interface does not necessarily belong to any dialer interface. You can directly map it to one or multiple destination addresses.

  • Page 136: Dcc Features

    Figure 39 Association of physical interfaces, dialer bundles, and dialer interfaces Figure 39, a physical interface can be assigned to multiple dialer bundles and serve multiple dialer interfaces, but each dialer interface can use only one dialer bundle and configured with one dial string.

  • Page 137: Configuration Prerequisites

    • Payer change—This is useful for saving cost in the case that the call rates in two directions are different. • Consolidated call charge bills—Facilitating settlement. PPP callback and ISDN caller identification callback features are available. The PPP callback conforms to RFC 1570 specifications and can be used where both client and server own fixed network addresses, or the client accepts dynamic network address assignment.

  • Page 138: Configuring Basic Settings For Dcc

    By default, a synchronous/asynchronous serial interface operates in synchronous mode, and an asynchronous serial interface operates in asynchronous mode. For more information, see HPE FlexNetwork MSR Router Series Comware 5 Interface Configuration Guide and "Managing a modem." Configuring link layer/network/routing protocols on the dialup...

  • Page 139: Associating A Dcc Dial Acl With The Dialup Interface

    For more information, see HPE FlexNetwork MSR Router Series Comware 5 Layer 2 — Configuration Guide, HPE FlexNetwork MSR Router Series Comware 5 Layer 3—IP Services Configuration Guide, and HPE FlexNetwork MSR Router Series Comware 5 Layer 3—IP Routing...

  • Page 140: Configuring An Interface To Place Calls To A Remote End

    associated with multiple destinations, any physical interface in the group can call any of these destinations. Depending on your network topology and dial needs, for example, to allow one or multiple interfaces to both place and receive calls, you can use any combinations of the following C-DCC configuration approaches: Configuring an interface to place calls to a remote end •...

  • Page 141: Configuring An Interface To Receive Calls From A Remote End

    Step Command Remarks Enter system view. system-view Enter dialup interface interface interface-type (physical or dialer interface) interface-number view. Enable C-DCC. By default, C-DCC is disabled. dialer enable-circular • dialer number dial-number • dialer route protocol next-hop-address [ mask Configure a dial string for network-mask-length ] [ user Use either command.

  • Page 142: Configuring An Interface To Place Calls To Multiple Remote Ends

    Step Command Remarks Optional. If the dialer route ip dialer route protocol next-hop-address user hostname Configure the interface to next-hop-address [ mask command is configured at the receive calls from a remote network-mask-length ] [ user called end, the called party will end.

  • Page 143: Configuring An Interface To Receive Calls From Multiple Remote Ends

    Configuring an interface to receive calls from multiple remote ends Figure 43, an interface at the local end receives calls from multiple remote ends (the components in inverse color represent the routers irrelevant to the networking). Figure 43 Network diagram In this scenario, a single local interface if0 receives DCC calls from multiple remote interfaces including if1, if2, if3, and if4.
  • Page 144 Figure 44 Multiple interfaces place calls to one or multiple remote ends In this scenario, interfaces if0, if1, and if2 at the local end place DCC calls to interfaces if1, if2, and if3 at the remote ends. If only one remote end is involved, use the dialer number command to configure a dial string.

  • Page 145: Configuring Multiple Interfaces To Receive Calls From One Or Multiple Remote Ends

    Configuring multiple interfaces to receive calls from one or multiple remote ends Figure 45, multiple interfaces at the local end receive calls from one or multiple remote ends (the components in inverse color represent the routers irrelevant to the networking). Figure 45 Multiple interfaces receive calls from one or multiple remote ends In this scenario, interfaces if0, if1, and if2 at the local end receive DCC calls from multiple remote interfaces including if1, if2, if3, and if4.

  • Page 146: Configuring Rs-Dcc

    Configuring RS-DCC In the RS-DCC approach, physical interface configuration is separated from logical configuration for calls and they can be combined dynamically for each call. When you configure RS-DCC for on-demand dial, configure RS-DCC sets. Each RS-DCC set is an attribute collection containing a dialer interface, dialer interface attributes, and a dialer bundle.

  • Page 147: Enabling Rs-Dcc

    Task Remarks Enabling RS-DCC Required. Configuring a dial string for the dialer interface Required. Assigning physical interfaces to the dialer bundle Required. Configuring dial authentication for RS-DCC Required. Enabling RS-DCC Step Command Enter system view. system-view Create a dialer interface and enter dialer interface dialer number interface view.

  • Page 148: Configuring Dial Authentication For Rs-Dcc

    Step Command Remarks Physical interfaces do not belong to any dialer bundle by default. Assign the interface to the dialer bundle-member number After a physical interface is dialer bundle. [ priority priority ] assigned without priority to a dialer bundle, it takes the default priority of 1.

  • Page 149: Configuration Guidelines

    To implement MP with DCC, use dialer interfaces. The following shows how MP operates after you configure the ppp mp and dialer threshold commands on a dialer interface: • When the ratio of traffic to bandwidth on a physical interface assigned to the dialer interface exceeds the configured load threshold, DCC brings up another physical interface in the dialer interface, and assigns these links to an MP bundle.

  • Page 150: Configuring Ppp Callback

    Step Command Remarks Optional. Set the upper limit of links in ppp mp max-bind max-bind-num an MP bundle. The default setting is 16. Optional. Set the lower limit of links in By default, the lower limit is 0, and ppp mp min-bind min-bind-num an MP bundle.
  • Page 151 Step Command Remarks Enter dialer interface interface interface-type (physical or dialer interface) interface-number view. Enable PPP encapsulation. link-protocol ppp Configure authentication See "Configuring PPP and MP." parameters. By default, PPP callback client is Enable PPP callback client. ppp callback client disabled.

  • Page 152: Configuring Ppp Callback With Rs-Dcc

    Step Command Remarks • If the dial-number keyword is configured, create a local user and enter local user view to configure a callback user and the dial string for callback: a. local-user user-name b. service-type ppp Configure either command c. authorization-attribute depending on the keyword callback-number Use either method.

  • Page 153: Configuring Isdn Caller Identification Callback

    Step Command Remarks Optional. Set the interval for DCC to Hewlett Packard Enterprise dialer timer enable seconds make the next call attempt. recommends that you use 15 seconds. Configuring a PPP callback server with RS-DCC Configuring a PPP callback server in RS-DCC is the same as that in C-DCC, except the callback reference can only be dial-number in RS-DCC and dial strings for callback must be configured with the authorization-attribute callback-number command.

  • Page 154: Configuring Isdn Caller Identification Callback With C-Dcc

    character. If a dial-in number matches multiple dialer call-in commands, the best match is selected in the following order: The one with the fewest asterisks (*). The one that is found first. At the server end, identify the dialer call-in commands matching incoming calls. In C-DCC, upon receipt of an incoming call, the server compares the incoming number against the dialer call-in commands configured on the physical dialup interface or its corresponding dialer interface for a match.

  • Page 155: Configuring Isdn Caller Identification Callback With Rs-Dcc

    Step Command Remarks dialer route protocol next-hop-address Configure one or multiple [ mask network-mask-length ] [ user destination addresses and hostname | broadcast ] * dial-number dial strings. [ autodial | interface interface-type interface-number ] * Optional. Use this command instead Configure a dial number for of the dialer route placing calls to a single...

  • Page 156: Configuring Advanced Dcc Functions

    Configuring advanced DCC functions Configuring an ISDN leased line An ISDN leased line can be configured with C-DCC but not RS-DCC. This function is fulfilled through establishing semi-permanent ISDN MP connections. Such an application requires a leased line to be established on the PBX of your telecom service provider and has been connected to the remote device.

  • Page 157: Configuring Dcc Overlap Receiving

    To configure circular dial string backup: Step Command Enter system view. system-view Enter dialup interface (physical or dialer interface interface-type interface-number interface) view. dialer route protocol next-hop-address [ mask Repeat this step to associate multiple dial network-mask-length ] [ user hostname | broadcast ] * strings with the same next-hop-address.

  • Page 158: Configuration Procedure

    timer for the link. When the idle time of the link reaches the setting of this compete-idle timer, the link disconnects. • Wait-carrier timer—Sometimes, the time DCC waits for a connection to be established varies call by call. To handle this situation, use a wait-carrier timer. A wait-carrier timer starts when a call is placed.

  • Page 159: Creating A Dynamic Route Backup Group

    The dynamic route backup function is mainly used to back up dynamic routes. Moreover, it can also back up static routes and directly connected routes. The dynamic route backup function is suitable for scenarios with multiple interfaces and multiple routers. It is not dedicated to a specific interface or link. With dynamic route backup enabled, the backup link will be activated automatically when the primary link fails.

  • Page 160: Enabling Dynamic Route Backup On A Backup Interface

    Step Command Remarks Enter system view. system-view By default, no dynamic route backup group is created. Create a dynamic route standby routing-rule The IP address specified in the backup group and add a group-number ip ip-address standby routing-rule command network segment to be { mask | mask-length } must be the same as that monitored to the group.

  • Page 161: Configuring The Traffic Statistics Collecting Interval

    Step Command Remarks Enter system view. system-view Optional. The default setting is 30 seconds. Configure the warm-up time dialer timer warmup seconds Hewlett Packard Enterprise for dynamic route backup. recommends that you use the default setting. Configuring the traffic statistics collecting interval Step Command Remarks...
  • Page 162 Figure 47 Network diagram Configuration procedure Configure Router A: # Configure a dial access control rule for dialer access group 1. <RouterA> system-view [RouterA] dialer-rule 1 ip permit # Assign an IP address to interface Dialer0, associate dialer access group 1 with the interface, enable C-DCC, and configure dial strings for calling Router B and Router C.

  • Page 163: Rs-Dcc Configuration Example

    [RouterA-ui-tty2] modem both Configure Router B: # Configure a dial access control rule for dialer access group 1. <RouterB> system-view [RouterB] dialer-rule 1 ip permit # Configure interface Serial 2/0 to operate in asynchronous protocol mode. [RouterB] interface serial 2/0 [RouterB-Serial2/0] physical-mode async [RouterB-Serial2/0] async mode protocol # Assign an IP address to interface Serial 2/0, associate dialer access group 1 with the interface,...
  • Page 164 • On Router C, interface Dialer0 is assigned an IP address 122.1.1.2/24. • The Dialer0 interfaces on Router A and Router B are located on the same network segment, so are the Dialer1 interface on Router A and the Dialer0 interface on Router C. Configure RS-DCC to allow Router A to call Router B and Router C from multiple interfaces but disable Router B and Router C from calling each other.
  • Page 165 # Assign an IP address to interface Dialer1, enable RS-DCC, and configure the remote username allowed to call in. [RouterA] interface dialer 1 [RouterA-Dialer1] ip address 122.1.1.1 255.255.255.0 [RouterA-Dialer1] dialer user userc [RouterA-Dialer1] dialer bundle 2 # Configure information for PPP authentication and the dial strings on interface Dialer 1. (Assume PAP is used at the local end.) [RouterA-Dialer1] dialer-group 1 [RouterA-Dialer1] ppp authentication-mode pap...
  • Page 166 [RouterB-luser-usera] quit # Assign an IP address to interface Dialer0, enable RS-DCC, and configure the remote username allowed to call in and the dial string for placing calls. [RouterB] interface dialer 0 [RouterB-Dialer0] ip address 100.1.1.2 255.255.255.0 [RouterB-Dialer0] dialer user usera [RouterB-Dialer0] dialer bundle 1 [RouterB-Dialer0] dialer number 8810048 # Configure information for PPP authentication.

  • Page 167: Configuration Example For Dcc On Isdn

    # Set interface Serial 2/0 to operate in asynchronous protocol mode, configure information for PPP authentication, and assign the interface to dialer bundle 1. [RouterC] interface serial 2/0 [RouterC-Serial2/0] physical-mode async [RouterC-Serial2/0] async mode protocol [RouterC-Serial2/0] dialer bundle-member 1 [RouterC-Serial2/0] link-protocol ppp [RouterC-Serial2/0] ppp authentication-mode pap [RouterC-Serial2/0] ppp pap local-user userc password simple userc [RouterC-Serial2/0] quit...
  • Page 168 Figure 50 Network diagram for RS-DCC application on ISDN Configuration procedure • Method 1: Use C-DCC to set up a connection through ISDN BRI or PRI and configure DCC parameters on physical interfaces. a. Configure Router A: # Configure a dial access control rule for dialer access group 1. <RouterA>...
  • Page 169 [RouterC-Bri1/0] ip address 100.1.1.3 255.255.255.0 [RouterC-Bri1/0] dialer enable-circular [RouterC-Bri1/0] dialer-group 1 [RouterC-Bri1/0] dialer route ip 100.1.1.1 8810048 • Method 2: Use RS-DCC to set up a connection through ISDN BRI or PRI and configure DCC parameters on dialer interfaces. d. Configure Router A: # Configure a dial access control rule for dialer access group 1.
  • Page 170 [RouterA-Bri1/0] link-protocol ppp [RouterA-Bri1/0] ppp authentication-mode pap [RouterA-Bri1/0] ppp pap local-user usera password simple usera e. Configure Router B: # Configure a dial access control rule for dialer access group 2. Create a local user account usera for Router A, and configure PPP authentication for it. <RouterB>...

  • Page 171: Configuration Example For Rs-Dcc With Mp

    [RouterC-Dialer0] ppp authentication-mode pap [RouterC-Dialer0] ppp pap local-user userc password simple userc [RouterC-Dialer0] quit # Configure information for PPP authentication on interface BRI 1/0 and assign the interface to dialer bundle 1. [RouterC] interface bri 1/0 [RouterC-Bri1/0] dialer bundle-member 1 [RouterC-Bri1/0] link-protocol ppp [RouterC-Bri1/0] ppp authentication-mode pap [RouterC-Bri1/0] ppp pap local-user usera password simple usera...
  • Page 172 # Assign an IP address to interface Dialer0, enable RS-DCC, and configure MP. [RouterA] interface dialer 0 [RouterA-Dialer0] ip address 100.1.1.1 255.255.255.0 [RouterA-Dialer0] dialer bundle 1 [RouterA-Dialer0] ppp mp [RouterA-Dialer0] dialer threshold 50 # Configure information for PPP authentication, the remote user allowed to call in, and the dial strings on interface Dialer0.

  • Page 173: Configuration Example For Router-To-Router Ppp Callback With Dcc

    [RouterB-Dialer0] ppp pap local-user userb password simple userb [RouterB-Dialer0] quit # Bundle timeslots on CE1/PRI interface E1 2/0 into a PRI group. [RouterB] controller e1 2/0 [RouterB-E1 2/0] pri-set [RouterB-E1-2/0] quit # Enable C-DCC on interface Serial 2/0:15 created on interface E1 2/0 and assign the serial interface to interface Dialer 0.
  • Page 174 # Specify interface Serial 2/0 as the callback client. [RouterA-Serial2/0] ppp callback client [RouterA-Serial2/0] dialer timer enable 15 [RouterA-Serial2/0] quit # Configure the user interface to be used and enable modem dial-in and dial-out on it. [RouterA] user-interface tty1 [RouterA-ui-tty1] modem both b.
  • Page 175 [RouterA-Serial2/0] dialer enable-circular [RouterA-Serial2/0] dialer-group 1 [RouterA-Serial2/0] dialer route ip 100.1.1.2 8810052 [RouterA-Serial2/0] link-protocol ppp [RouterA-Serial2/0] ppp pap local-user usera password simple usera # Specify interface Serial 2/0 as the callback client. [RouterA-Serial2/0] ppp callback client [RouterA-Serial2/0] dialer timer enable 15 [RouterA-Serial2/0] quit # Configure the user interface to be used and enable modem dial-in and dial-out on it.

  • Page 176: Configuration Example For Router-To-Router Isdn Caller Identification Callback With Dcc

    Configuration example for router-to-router ISDN caller identification callback with DCC Network requirements Figure As shown in • Router A and Router B are interconnected through ISDN BRI interfaces across an ISDN network. • Interface BRI 1/0 on Router A is assigned the IP address of 100.1.1.1/24 and interface BRI 1/0 on Router B is assigned the IP address of 100.1.1.2/24.

  • Page 177: Configuration Example For Router-To-Pc Ppp Callback With Dcc

    Configuration example for router-to-PC PPP callback with Network requirements Figure As shown in • PC and Router are interconnected through modems across a PSTN network. • Interface Serial 2/0 on Router is assigned the IP address of 100.1.1.1/24. • PC accepts the address assigned by Router. Configure PPP callback with C-DCC between Router and PC, specifying PC as the callback client and Router as the callback server to make return calls according to dialer routes.
  • Page 178 b. Clear the Enable software compression box. c. Clear the Negotiate multi-link for single link connections box. d. Click OK. 13. Turn to the Network and Dial-up Connections window. Click the connection icon you just created. Then, from the menu bar, select Advanced > Dial-up Preferences. In the Dial-up Preferences dialog box, select the Callback tab and do one of the following: Select the No callback option.

  • Page 179: Configuration Example For Nt Server-To-Router Callback With Dcc

    Configuration example for NT server-to-router callback with Network requirements Figure As shown in • Router and NT Server are interconnected through modems across a PSTN network. • NT Server is assigned the IP address of 100.1.1.254/24. • Router accepts the address assigned by NT Server. Configure PPP callback with C-DCC between Router and PC, specifying Router as the callback client and NT Server as the callback server to make return calls according to dialer routes.
  • Page 180 # Configure the user interface to be used and enable modem dial-in and dial-out on it. [Router] user-interface tty1 [Router-ui-tty1] modem both Configuring NT Server For Microsoft Windows users, the server must be Windows 2000 and a later version such as Windows XP.

  • Page 181: Configuration Example For Circular Dial String Backup And Internet Access With Dcc

    Configuration example for circular dial string backup and Internet access with DCC Network requirements Figure As shown in • Router A and Router B are connected across a PSTN network. • Router B operates as an access server and is configured with an IP address of 100.1.1.254/24. It uses the address range of 100.1.1.1/24 to 100.1.1.16/24 for address assignment.
  • Page 182 Figure 57 Network diagram for dial string backup/access service with DCC (ISDN) Configuration procedure for method 1 On Router A on the dialup side, configure circular dial string backup. On Router B, configure C-DCC to allow the router to set up connections on eight asynchronous serial interfaces, and configure C-DCC parameters on a dialer interface.
  • Page 183 [RouterA-ui-tty1] modem both Configure Router B: # Configure a dial access control rule for dialer access group 2. Create local user accounts user1 through user16 and configure PPP authentication for the accounts. <RouterB> system-view [RouterB] dialer-rule 2 ip permit [RouterB] local-user user1 [RouterB-luser-user1] password simple user1 [RouterB-luser-user1] service-type ppp [RouterB-luser-user1] quit...
  • Page 184 [RouterB-ui-tty8] quit # Configure the address for address assignment. [RouterB] domain system [RouterB-isp-system] ip pool 1 100.1.1.1 100.1.1.16 [RouterB-isp-system] quit Configure the user PC: a. Place the modem connected to PC in auto answer mode. b. Right-click the My Network Places icon and select the Properties option from the popup menu.
  • Page 185 [RouterC-luser-userd] password simple user1 [RouterC-luser-userd] service-type ppp [RouterC-luser-userd] quit # Configure physical layer parameters for interface BRI 1/0 and enable PPP address negotiation. [RouterC] interface bri 1/0 [RouterC-Bri1/0] ip address ppp-negotiate # Configure PPP encapsulation and PPP CHAP authentication on the interface. [RouterC-Bri1/0] link-protocol ppp [RouterC-Bri1/0] ppp authentication-mode chap [RouterC-Bri1/0] ppp chap user user1...

  • Page 186: Dynamic Route Backup Configuration Example 1

    [RouterD-Serial2/0:15] ppp chap user userd [RouterD-Serial2/0:15] remote address pool 1 [RouterD-Serial2/0:15] quit # Configure an IP address pool for assigning addresses to PPP users. [RouterD] domain system [RouterD-isp-system] ip pool 1 100.1.1.1 100.1.1.16 [RouterD-isp-system] quit Dynamic route backup configuration example 1 Network requirements Figure As shown in...
  • Page 187 [RouterA-Serial2/0] link-protocol x25 dte ietf [RouterA-Serial2/0] x25 x121-address 10 [RouterA-Serial2/0] x25 map ip 10.0.0.2 x121-address 15 broadcast [RouterA-Serial2/0] ip address 10.0.0.1 8 [RouterA-Serial2/0] quit # Configure RIP. [RouterA] rip [RouterA-rip-1] network 10.0.0.0 [RouterA-rip-1] network 20.0.0.0 [RouterA-rip-1] import-route direct [RouterA-rip-1] quit # Create a dynamic route backup group.

  • Page 188: Dynamic Route Backup Configuration Example 2

    [RouterC-Serial2/1] x25 map ip 10.0.0.1 x121-address 10 broadcast [RouterC-Serial2/1] ip address 10.0.0.2 8 [RouterC-Serial2/1] quit # Configure interface Loopback 1. [RouterC] interface loopback 1 [RouterC-Loopback1] ip address 30.0.0.1 32 [RouterC-Loopback1] quit # Configure RIP. [RouterC] rip [RouterC-rip-1] network 10.0.0.0 [RouterC-rip-1] network 20.0.0.0 [RouterC-rip-1] network 30.0.0.0 [RouterC-rip-1] import-route direct Dynamic route backup configuration example 2...
  • Page 189 [RouterA-Bri3/0] dialer route ip 40.0.0.1 8810052 [RouterA-Bri3/0] quit # Configure interface Serial 2/0. [RouterA] interface serial 2/0 [RouterA-Serial2/0] ip address 10.0.0.1 8 [RouterA-Serial2/0] quit # Configure OSPF. [RouterA] ospf [RouterA-ospf-1] area 0 [RouterA-ospf-1-area-0.0.0.0] network 10.0.0.0 0.255.255.255 [RouterA-ospf-1-area-0.0.0.0] network 20.0.0.0 0.255.255.255 [RouterA-ospf-1-area-0.0.0.0] import-route direct [RouterA-ospf-1-area-0.0.0.0] quit [RouterA-ospf-1] quit...

  • Page 190: Dynamic Route Backup Configuration Example 3

    [RouterB-ospf-1-area-0.0.0.0] import-route direct Dynamic route backup configuration example 3 Network requirements Figure As shown in • Router A and Router B are connected through an X.25 network. • Router A and Router B are connected to the same ISDN switched network through their ISDN BRI interfaces, each of which has two B channels bound in it.

  • Page 191: Configure Rip

    [RouterA-Dialer0] dialer number 8810052 [RouterA-Dialer0] ppp authentication-mode pap [RouterA-Dialer0] ppp pap local-user usera password simple usera [RouterA-Dialer0] standby routing-group 1 [RouterA-Dialer0] quit # Bind BRI 3/0 to Dialer 0. [RouterA] interface bri 3/0 [RouterA-Bri3/0] dialer bundle-member 1 [RouterA-Bri3/0] ppp authentication-mode pap [RouterA-Bri3/0] ppp pap local-user usera password simple usera [RouterA-Bri3/0] quit # Configure interface Serial 2/0 and enable X.25 encapsulation on the interface.

  • Page 192: Dynamic Route Backup Configuration Example 4

    [RouterB] interface bri 3/0 [RouterB-Bri3/0] dialer bundle-member 1 [RouterB-Bri3/0] ppp authentication-mode pap [RouterB-Bri3/0] ppp pap local-user userb password simple userb [RouterB-Bri3/0] quit # Configure interface Serial 2/1 and enable X.25 encapsulation on the interface. [RouterB] interface serial 2/0 [RouterB-Serial2/0] link-protocol x25 dte ietf [RouterB-Serial2/0] x25 x121-address 20 [RouterB-Serial2/0] x25 map ip 10.0.0.1 x121-address 10 broadcast [RouterB-Serial2/0] ip address 10.0.0.2 8...
  • Page 193 This network diagram only illustrates a simple application where a dynamic route backup group is used to monitor multiple subnets. In actual use, the monitored network segments can be connected to multiple devices. Configuration procedure Configure Router A: # Create a dialer access group rule. <RouterA>...

  • Page 194: Troubleshooting

    [RouterB-E1 2/1] pri-set [RouterB-E1 2/1] quit # Configure Serial 2/0 as an FR interface. [RouterB] interface serial 2/0 [RouterB-Serial2/0] ip address 1.0.0.2 255.0.0.0 [RouterB-Serial2/0] link-protocol fr [RouterB-Serial2/0] fr interface-type dte [RouterB-Serial2/0] fr inarp [RouterB-Serial2/0] fr map ip 1.0.0.1 200 [RouterB-Serial2/0] quit # Configure C-DCC on PRI interface Serial 2/1:15.
  • Page 195 • DCC is enabled on the dialup interface. • A dialer route or dialer number command is available for the packets. Symptom 2 The remote end cannot be pinged after the modem is connected. Solution Check that: • The same link layer encapsulation is used at the two ends, and correct PPP parameters are configured for authentication.

  • Page 196: Managing A Modem

    Managing a modem A modem is a widely used network device. It is important for a device to correctly manage and control the use of modems in a network. Many modem manufacturers and various modem models exist. Even though all of them support the AT command set and are compliant with the industry standard, each type of modem differs somewhat on the implementations and command details.

  • Page 197: Setting The Modem Answer Mode

    Setting the modem answer mode Set the modem answer mode according to the actual answer mode of the modem: • If the modem is in auto-answer mode (a modem is in auto-answer mode if its AA LED lights are on), use the modem auto-answer command to prevent the device from issuing answer instructions.

  • Page 198: Troubleshooting

    # Enables both modem call-in and modem call-out on user-interface TTY 1. [Router] user-interface tty 1 [Router-ui-tty1] modem both For information about DCC commands, see HPE FlexNetwork MSR Router Series Comware 5 Layer 2—WAN Command Reference. Configure the Cisco router: For more information, see Cisco documentation.

  • Page 199: Configuring Atm

    Configuring ATM Overview Asynchronous Transfer Mode (ATM) is a technology based on packet transmission mode while incorporating the high-speed of circuit transmission mode. ATM was adopted as the transmission and switching mode for broadband ISDN by the ITU-T in June 1992. Due to its flexibility and support for multimedia services, ATM is regarded as core broadband technology.

  • Page 200: Atm Architecture

    Figure 64 ATM switching ATM interfaces support only manually created permanent virtual circuits (PVCs) and permanent virtual paths (PVPs), not switched virtual circuits (SVCs) created through the exchange of signals. ATM architecture ATM has a three-dimensional architecture. It consists of three planes: user plane, control plane, and management plane.

  • Page 201: Ipoa, Ipoeoa, Pppoa, And Pppoeoa

    • ATM layer—Resides over the physical layer, and implements cell-based communication with its peer layer by invoking the services provided by the physical layer. It is independent of physical media, implementation of the physical layer, and types of services being carried. Data passed to this layer takes the form of 48-byte payloads, which are segmentation and reassembly protocol data units (SAR-PDUs);...

  • Page 202: Atm Service Types

    introduced. The VE interface has Ethernet characteristics and can be dynamically created. The following is the protocol stack adopted by the VE interface: • ATM PVC (the bottom layer) • Ethernet (the link layer) • Network layer and other upper layers (the same as those for common Ethernet interfaces) ATM service types ATM supports four service types: constant bit rate (CBR), unspecified bit rate (UBR), Real-Time Variable Bit Rate (rt-VBR) and Non-Real-Time Variable Bit Rate (nrt-VBR).

  • Page 203: Atm Oam

    Figure 66 Inverse address resolution procedure of InARP ATM OAM OAM in the ITU-T I.610 recommendation (02/99) and Operation Administration and Maintenance in LUCENT APC User Manual (03/99). Whichever expansion is adopted, OAM provides a way of detecting faults, isolating faults, and monitoring network performance without interrupting ongoing services.

  • Page 204: Atm Configuration Task List

    Except the mtu command, which can be configured on a subinterface, the ATM settings in this section must be modified in ATM main interface view, although they apply to both the main ATM interface and its subinterfaces. For more information about ATM interface configuration, see HPE FlexNetwork MSR Router Series Comware 5 Interface Configuration Guide.

  • Page 205: Configuring An Atm Subinterface

    Configuring an ATM subinterface Performing basic configurations for an ATM subinterface Step Command Remarks Enter system view. system-view By default, the connection type of a subinterface is point-to-multipoint (p2mp). The keywords p2mp and p2p are interface atm available with the interface atm Create an ATM subinterface interface-number.subnumber interface-number.subnumber...
  • Page 206 Step Command Remarks interface atm Enter ATM interface view or { interface-number | ATM subinterface view. interface-number.subnumber } Create a PVC and enter PVC pvc { pvc-name [ vpi/vci ] | By default, no PVC is created. view. vpi/vci } Optional.

  • Page 207: Setting The Clp Bit For Atm Cells

    PVC. { inbound | outbound } For more information about classes, traffic behaviors, and policies, see HPE FlexNetwork MSR Router Series Comware 5 ACL and QoS Configuration Guide. Assigning a transmission priority to an ATM PVC You can assign transmission priorities to ATM PVCs associated with the UBR, rt-VBR, or nrt-VBR service.

  • Page 208: Configuring Pvc Service Mapping

    To assign a transmission priority to an ATM PVC: Step Command Remarks Enter system view. system-view Enter ATM subinterface interface atm { interface-number view. | interface-number.subnumber } Create a PVC and enter pvc { pvc-name [ vpi/vci ] | PVC view. vpi/vci } Optional.

  • Page 209: Configuring An Atm Class

    Step Command Remarks Optional. The maximum number of PVCs allowed on an ATM interface Configure the maximum depends on the interface type. number of PVCs allowed pvc max-number max-number This command applies to both a on the ATM interface. main ATM interface and its subinterfaces.
  • Page 210 Step Command Remarks Optional. By default, OAM F5 Loopback cell transmission is disabled. Start transmission of OAM F5 oam frequency frequency [ up However, if an OAM F5 Loopback Loopback cells or up-count down down-count cell is received, it should be retransmission check of OAM retry-frequency responded.

  • Page 211: Configuring Vp Policing

    Step Command Remarks • Enter ATM interface view: interface atm { interface-number | Enter ATM interface view or interface-number.subnumbe PVC view • Enter PVC view: pvc { pvc-name [ vpi/vci ] | vpi/vci } Enable the ATM class on the atm-class atm-class-name interface or PVC Configuring VP policing...

  • Page 212: Configuring Ipoa

    Configure the map ip default broadcast command on PVCs created on P2P ATM subinterfaces. • You can configure PVC mapping in PVC view. For more information, see HPE FlexNetwork MSR Router Series Comware 5 MPLS Configuration Guide. To configure IPoA:...

  • Page 213: Configuring Ipoeoa

    In an IPoEoA application, Class Based Queuing (CBQ) should be configured on PVCs. • You can configure PVC mapping in PVC view. For information about the configuration, see HPE FlexNetwork MSR Router Series Comware 5 MPLS Configuration Guide. To configure IPoEoA on a PVC:...

  • Page 214: Configuring Pppoeoa

    The following configurations enable the PVC to carry PPP and configure a PPP mapping for the PVC. To configure PPPoA: Step Command Remarks Enter system view. system-view Configure PPP authentication and IP address on the VT interface interface virtual-template Create a VT interface. (the IP address is invalid if vt-number configured on the ATM interface).

  • Page 215: Displaying And Maintaining Atm

    Step Command Remarks Set the PPP authentication mode and IP address; with the PPPoE server, an address pool should be configured to allocate IP address for the peer end; See "Configuring PPP and MP." with the PPPoE client, address negotiation should be configured to accept the IP address allocated by the server end..

  • Page 216: Atm Configuration Examples

    Task Command Remarks display atm class [ atm-class-name ] [ | Display information about an ATM { begin | exclude | include } Available in any view. class. regular-expression ] Send OAM cells on the specified PVC on the interface to test Available in ATM oamping interface atm interface-number connectivity of the link depending...

  • Page 217: Ipoeoa Configuration Example

    Configuration procedure Configure Router A: # Enter the view of the ATM 1/0 interface and configure an IP address for it. <RouterA> system-view [RouterA] interface atm 1/0 [RouterA-Atm1/0] ip address 202.38.160.1 255.255.255.0 # Establish a PVC and enable it to carry IP. [RouterA-Atm1/0] pvc to_b 0/40 [RouterA-atm-pvc-Atm1/0-0/40-to_b] map ip 202.38.160.2 [RouterA-atm-pvc-Atm1/0-0/40-to_b] quit...

  • Page 218: Pppoa Configuration Example

    Figure 68 Network diagram Configuration procedure Configure Router C: # Create a VE interface and configure an IP address for it. <RouterC> system-view [RouterC] interface virtual-ethernet 1 [RouterC-Virtual-Ethernet1] ip address 202.38.160.1 255.255.255.0 [RouterC-Virtual-Ethernet1] quit # Create a PVC and enable IPoEoA on it. [RouterC] interface atm 1/0.1 [RouterC-Atm1/0.1] pvc to_adsl_a 0/60 [RouterC-atm-pvc-Atm1/0.1-0/60-to_adsl_a] map bridge virtual-ethernet 1...
  • Page 219 Figure 69 Network diagram Configuration procedure CAUTION: If the client cancels the IP address it has received through address negotiation, or the client is configured with a fixed IP address, the communication between the server and the client will fail. You must shut down the ATM interface first by using the shutdown command, and delete the IP address pool on the server.

  • Page 220: Pppoeoa Server Configuration Example

    [RouterC] interface atm 1/0.1 [RouterC-Atm1/0.1] pvc to_adsl_a 0/60 [RouterC-atm-pvc-Atm1/0.1-0/60-to_adsl_a] map ppp virtual-template 10 [RouterC-atm-pvc-Atm1/0.1-0/60-to_adsl_a] quit [RouterC-Atm1/0.1] pvc to_adsl_b 0/61 [RouterC-atm-pvc-Atm1/0.1-0/61-to_adsl_b] map ppp virtual-template 11 Configure ADSL Router A (PPPoA Client): # Create a VT interface, and configure PAP authentication and IP address negotiation. <RouterA>...

  • Page 221: Pppoeoa Client Configuration Example

    [RouterC-atm-pvc-Atm1/0.1-0/60-to_adsl_a] map bridge virtual-ethernet 1 [RouterC-atm-pvc-Atm1/0.1-0/60-to_adsl_a] quit [RouterC-Atm1/0.1] pvc to_adsl_b 0/61 [RouterC-atm-pvc-Atm1/0.1-0/61-to_adsl_b] map bridge virtual-ethernet 2 For more information about configuring a RADIUS scheme, see HPE FlexNetwork MSR Router Series Comware 5 Security Configuration Guide. PPPoEoA client configuration example Network requirements...
  • Page 222 Server, PPPoEoA authentication server of public network, is used to authenticate user information through CHAP. Figure 71 Network diagram Configuration procedure Configure Router A: # Configure user name and password. <RouterA> system-view [RouterA] local-user Sysname [RouterA-luser-Sysname] password simple hello [RouterA-luser-Sysname] service-type ppp [RouterA-luser-Sysname] quit # Configure dialing access control list.

  • Page 223: Atm Pvc Transmit Priority Configuration Example

    If the PPPoEoA Server is of the same type of router, its PPPoEoA can be configured as follow: # Configure user features. <Sysname> system-view [Sysname] local-user user1 [Sysname-luser-user1] password simple hello [Sysname-luser-user1] service-type ppp # Create a virtual-template, set the authentication mode to CHAP, and configure the IP address.

  • Page 224: Troubleshooting Atm

    Figure 72 Network diagram Configuration procedure Configure Router A # Configure the ATM interface. <RouterA> system-view [RouterA] interface atm 1/0 [RouterA-Atm1/0] ip address 202.38.160.1 255.255.255.0 # Create two PVCs and assign them different transmission priority values. [RouterA-Atm1/0] pvc 1 0/33 [RouterA-atm-pvc-Atm1/0-0/33-1] map ip 202.38.160.2 [RouterA-atm-pvc-Atm1/0-0/33-1] service ubr 100000 [RouterA-atm-pvc-Atm1/0-0/33-1] transmit-priority 1...

  • Page 225: Link Report Error In Pppoa Application

    Link report error in PPPoA application Symptom When PPPoA is used, the link does not report UP. Solution "Link state error in IPoA application." Ping failure Symptom The physical layer of the interfaces and the line protocol are both UP, but when tested with the ping command, the two ends are mutually unreachable.

  • Page 226: Ping Failure After Pppoa Configuration

    Solution Determine if this fault results from enabling OAM F5 Loopback cell transmission and retransmission detection or OAM continuity check. When two ATM devices are connected, the VPI/VCI value of the PVCs on the two devices must be the same. If OAM F5 cell transmission and retransmission detection or OAM continuity check is enabled, and the VPI/VCI value of the remote node (connected directly with the local node) is not the same as the local node, the local PVC state cannot change into Ping failure after PPPoA configuration...

  • Page 227: Configuring Hdlc

    Configuring HDLC The MSR900 and MSR93X routers do not support HDLC. Overview High-level Data Link Control (HDLC) is a bit-oriented link layer protocol. Its most prominent feature is that it can transmit any type of bit stream transparently. • HDLC supports point-to-point link only and does not support point-to-multipoint link. •...

  • Page 228: Configuring An Ip Address For An Interface

    For more information about interface IP address configuration, see HPE FlexNetwork MSR Router Series Comware 5 Layer 3—IP Services Configuration Guide. Configuring the link status polling interval HDLC can regularly check link status. The link status polling interval is user configurable. It is a good practice to set the same interval for the two ends of a link.

  • Page 229: Configuring Hdlc Compression

    Configuring HDLC compression The STAC-LZ compression compresses the payload of packets on an HDLC link. Because it does not rely on history packet information, it can achieve a smaller compression ratio. The STAC-LZ compression increases data transmission efficiency on low-speed links, saves network bandwidth, and reduces network load.

  • Page 230: Hdlc In Conjunction With Ip Unnumbered Interface Configuration Example

    Configuration procedure Configure Router A: <RouterA> system-view [RouterA] interface pos 5/0 [RouterA-Pos5/0] clock master [RouterA-Pos5/0] link-protocol hdlc [RouterA-Pos5/0] ip address 12.1.1.1 24 [RouterA-Pos5/0] quit Configure Router B: <RouterB> system-view [RouterB] interface pos 5/0 [RouterB-Pos5/0] link-protocol hdlc [RouterB-Pos5/0] ip address 12.1.1.2 24 After the configuration, Router A and Router B should be able to ping each other.
  • Page 231 Configuration procedure Configure Router A: <RouterA> system-view [RouterA] interface loopback 1 [RouterA-LoopBack1] ip address 12.1.1.2 32 [RouterA-LoopBack1] quit [RouterA] interface pos 5/0 [RouterA-Pos5/0] clock master [RouterA-Pos5/0] link-protocol hdlc [RouterA-Pos5/0] ip address unnumbered interface loopback 1 [RouterA-Pos5/0] quit Configure Router B: <RouterB>...

  • Page 232: Configuring Dlsw

    Configuring DLSw Overview The APPN AIW developed Data Link Switching (DLSw) for tunneling unroutable, non-IP based protocol such as IBM SNA over a TCP/IP network. Figure 75 shows the DLSw mechanism. Figure 75 DLSw mechanism The local DLSw router converts the LLC2 frames from the local SNA device into SSP frames that can be encapsulated in TCP packets.
  • Page 233 • Excessive broadcasts—Although a local acknowledgement mechanism is provided in DLSw v1.0, explorer frames might flood the WAN over the established TCP connections if the reachability table of DLSw contains a small number of entries or no entries. • Low maintainability—When a circuit is disconnected, DLSw v1.0 uses two types of messages to notify the peer but cannot tell the disconnection cause.

  • Page 234: Protocols And Standards

    Protocols and standards • RFC 1795, Data Link Switching: Switch-to-Switch Protocol AIW DLSw RIG: DLSw Closed Pages, DLSw Standard Version 1.0 • RFC 2166, APPN Implementer's Workshop Closed Pages Document DLSw V2.0 Enhancements Hardware compatibility with DLSw DLSw is not available on the following routers: •...

  • Page 235: Creating Dlsw Peers

    Step Command Remarks 15. Configure the remote "Configuring remote reachability information for Optional. reachability information." the router. "Configuring DLSw load 16. Configure DLSw load Optional. balancing. balancing." For more information on bridging and bridge set configuration, see "Configuring bridging." Creating DLSw peers Establishing a TCP connection is the first step in establishing a DLSw circuit.

  • Page 236: Adding An Ethernet Interface To A Bridge Set

    Step Command Remarks Enter system view. system-view By default, no bridge set is mapped to DLSw. This command should be used in Map a bridge set to DLSw. dlsw bridge-set bridge-set conjunction with the bridge bridge-set enable command, with the same bridge-set value in both commands.

  • Page 237: Configuring The Multicast Function Of Dlsw V2.0

    Step Command Remarks Configure the maximum number of information frames the router can receive 3 by default. llc2 max-ack length before it must send an acknowledgement. Configure the maximum number of consecutive Optional. information frames the router llc2 receive-window length can send before receiving an 7 by default.

  • Page 238: Configuring The Maximum Number Of Dlsw V2.0 Explorer Retries

    • dlsw ethernet-frame-filter traffic can be configured at the traffic, or both. acl-number outbound same time. For more information about creating a Layer 2 ACL, see HPE FlexNetwork MSR Router Series Comware 5 ACL and QoS Configuration Guide.

  • Page 239: Configuring Dlsw Ethernet Redundancy

    Configuring DLSw Ethernet redundancy DLSw Ethernet redundancy implements backup and load sharing, and enables multiple DLSw routers to connect to the same Ethernet. To prevent two or more DLSw routers connected to the same Ethernet from establishing multiple circuits for the same SNA session, DLSw Ethernet redundancy uniformly manages all DLSw routers connected to the same Ethernet.

  • Page 240: Enabling Sdlc Encapsulation On An Interface

    Step Command Remarks Configure an SDLC peer. "Configuring an SDLC peer." Optional (required for PU2.0 "Configuring an SDLC XID." Configure the XID of SDLC. devices). "Configuring an SDLC virtual 10. Configure an SDLC virtual Optional. MAC address. address." "Configuring the properties of 11.

  • Page 241: Configuring Sdlc Roles

    Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Enable DLSw forwarding on Disabled by default. sdlc enable dlsw the interface. Configuring SDLC roles In contrast with HDLC, SDLC is an "unbalanced" link layer protocol. The ends of a TCP connection are not equal in the positions: one is primary and the other is secondary.

  • Page 242: Configuring An Sdlc Peer

    To configure an SDLC address: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Configure the address of a By default, no secondary SDLC sdlc controller sdlc-address secondary SDLC station. station address is configured. Configuring an SDLC peer You can specify the MAC address for the peer end of an SDLC virtual circuit, and the MAC address is used as the destination MAC address of the LLC2 frames converted from SDLC frames.

  • Page 243: Configuring An Sdlc Virtual Mac Address

    Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Optional. By default, no SDLC XID is Configure an SDLC XID. sdlc xid sdlc-address xid-number configured on a synchronous serial interface. Configuring an SDLC virtual MAC address Initially designed for LLC2 protocols, DLSw establishes mappings with virtual circuits through MAC addresses.

  • Page 244: Configuring Optional Sdlc Parameters

    Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Configure the baud rate of Optional. the synchronous serial baudrate baudrate 9600 bps by default. interface. Configure the synchronous Optional. serial interface to use NRZI code { nrz | nrzi } NRZ encoding by default.

  • Page 245: Configuring Local Reachable Mac Or Sap Addresses

    Step Command Remarks Optional. Enable SDLC simultaneous Alternate mode by default. sdlc simultaneous mode. Generally, this configuration is not required. Optional. 10. Configure the SDLC polling sdlc timer poll mseconds interval. 1000 ms by default. 11. Configure the amount of time the primary SDLC station Optional.

  • Page 246: Configuring Dlsw Load Balancing

    Configuring DLSw load balancing When multiple remote peers can reach a MAC address, you can enable DLSw load balancing, and assign circuits according to the weights of remote peers and the number of existing virtual circuits. The DLSw load balancing function avoids establishing too many circuits on one remote peer. To enable DLSw load balancing: Step Command...

  • Page 247: Dlsw Configuration Examples

    Task Command Remarks Clear the virtual circuit information reset dlsw ethernet-backup Available in user view. of Ethernet redundancy. circuit Clear the mapping rules learned reset dlsw ethernet-backup by the backup MAC address Available in user view. mapping device. DLSw configuration examples Configuring LAN-to-LAN DLSw Network requirements Figure...

  • Page 248: Configuring Sdlc-To-Sdlc Dlsw

    [RouterB] bridge enable [RouterB] bridge 7 enable [RouterB] dlsw local 2.2.2.2 [RouterB] dlsw remote 1.1.1.1 [RouterB] dlsw bridge-set 7 [RouterB] interface ethernet 1/0 [RouterB-Ethernet1/0] bridge-set 7 After this configuration, the two SNA LANs across the Internet are interconnected. Configuring SDLC-to-SDLC DLSw Network requirements Figure 78, DLSw works in an SDLC-to-SDLC environment.

  • Page 249: Configuring Dlsw For Sdlc-To-Lan Remote Media Translation

    <RouterB> system-view [RouterB] dlsw local 2.2.2.2 [RouterB] dlsw remote 1.1.1.1 [RouterB] interface serial 2/0 [RouterB-Serial2/0] link-protocol sdlc [RouterB-Serial2/0] sdlc enable dlsw [RouterB-Serial2/0] sdlc status primary [RouterB-Serial2/0] sdlc controller c1 [RouterB-Serial2/0] sdlc mac-map remote 0000-1111-00c1 c1 [RouterB-Serial2/0] sdlc mac-map local 0000-2222-0000 [RouterB-Serial2/0] baudrate 9600 [RouterB-Serial2/0] code nrzi After this step, the SDLC LANs across the WAN are interconnected.

  • Page 250: Configuring Dlsw With Vlan Support

    [RouterA-Ethernet1/0] bridge-set 1 Configure Router B: # Configure interfaces on Router B to make sure that the local DLSw peer 2.2.2.2 and remote peer 1.1.1.1 can reach each other. (Details not shown.) # Configure DLSw on Router B. <RouterB> system-view [RouterB] dlsw local 2.2.2.2 [RouterB] dlsw remote 1.1.1.1 [RouterB] interface serial 2/0...
  • Page 251 • Assign Ethernet 1/1 to VLAN 2, configure Ethernet 1/0 as a trunk port and assign it to VLAN 2. • Configure a sub-interface Ethernet 1/1.1 on Ethernet 1/1 of Router A and assign this sub-interface to VLAN 2. Configure DLSw on Router A and Router B. Figure 80 Network diagram Configuration procedure Configure Router A:...

  • Page 252: Dlsw V2.0 Configuration Example

    [LSW-Ethernet1/0] port trunk permit vlan 2 DLSw v2.0 configuration example Network requirements Figure 81, Router A is DLSw v2.0 capable, connected with an IBM host. Router B and As shown in Router C are DLSw v1.0 or DLSw v2.0 capable, connected with PC1 and PC2, respectively. CISCO is a DLSw-capable router of Cisco, connected with PC3.

  • Page 253: Ethernet Redundancy Configuration Example For Lan-To-Lan Dlsw

    Before configuring Router B and Router C, first identify which DLSw version they support. If they are DLSw v2.0 capable, the configuration is similar as on Router A. If they are DLSw v1.0 capable, remove the multicast and explorer frame retransmission part from the configuration. For the configuration on the Cisco router, see Cisco documentation.

  • Page 254: Ethernet Redundancy Configuration Example For Sdlc-To-Lan Dlsw

    Configure Router B: # Configure interfaces on Router B to make sure that the local DLSw peer 2.2.2.2 and remote peer 1.1.1.1 can reach each other. (Details not shown.) # Configure DLSw on Router B. <RouterB> system-view [RouterB] dlsw local 2.2.2.2 [RouterB] dlsw remote 1.1.1.1 # Enable DLSw Ethernet redundancy on interface Ethernet 1/0, and configure the multicast address as 9999-9999-9999 and set the priority to 10 for primary/secondary router election.
  • Page 255 Figure 83 Network diagram Router B Eth1/0 2.2.2.2/24 Router A LLC2 1.1.1.1/24 Internet S2/0 Router C 3.3.3.3/24 SDLC Eth1/0 IBM AS/400 Host (SNA) Configuration procedures Configure Router A: # Configure interfaces on Router A to make sure that the local DLSw peer 1.1.1.1 and remote peers 2.2.2.2 and 3.3.3.3 can reach each other.

  • Page 256: Switch Support For Ethernet Redundancy Configuration Example For Lan-To-Lan Dlsw

    # Configure interfaces on Router C to make sure that the local DLSw peer 3.3.3.3 and remote peer 1.1.1.1 can reach each other. (Details not shown.) # Configure DLSw on Router C. <RouterC> system-view [RouterC] dlsw local 3.3.3.3 [RouterC] dlsw remote 1.1.1.1 # Enable DLSw Ethernet redundancy on Ethernet 1/0, and configure the multicast address as 9999-9999-9999 for primary/secondary router election.
  • Page 257 and the device which will take over to perform MAC address mapping to 00f0-47b8-a5df when the current device is not available. [RouterA-Ethernet1/0] dlsw ethernet-backup map local-mac 0500-0001-0000 remote-mac 0200-0008-0080 neighbor 00f0-47b8-a5df Configure Router B: # Configure interfaces on Router B to make sure that the local DLSw peer 2.2.2.2 and remote peer 3.3.3.3 can reach each other.

  • Page 258: Load Balancing Configuration Example For Lan-To-Lan Dlsw

    Load balancing configuration example for LAN-to-LAN DLSw Network requirements Figure As shown in • DLSw operates in LAN-to-LAN mode. • Configure DLSw on Router A, Router B, and Router C to connect the IBM host with the SNA host through the Internet. •...

  • Page 259: Load Balancing Configuration Example For Sdlc-To-Lan Dlsw

    [RouterB] bridge 5 enable [RouterB] dlsw local 2.2.2.2 [RouterB] dlsw remote 1.1.1.1 [RouterB] dlsw bridge-set 5 [RouterB] interface ethernet 1/0 [RouterB-Ethernet1/0] bridge-set 5 Configure Router C: # Configure interfaces on Router C to make sure that the local DLSw peer 3.3.3.3 and remote peer 1.1.1.1 can reach each other.
  • Page 260 Configuration procedures Configure Router A: # Configure interfaces on Router A to make sure that the local DLSw peer 1.1.1.1 and remote peers 2.2.2.2 and 3.3.3.3 can reach each other. (Details not shown.) # Configure DLSw and enable DLSw load balancing on Router A. <RouterA>...

  • Page 261: Sap Address-Based Filtering Configuration Example

    SAP address-based filtering configuration example Network requirements Figure As shown in • DLSw operates in LAN-to-LAN mode. • Configure DLSw on Router A and Router B to connect the IBM host with the SNA host through the Internet. • Configure SAP-rule-based ACLs on Router A to filter the packets sent to the remote peer. Figure 87 Network diagram Configuration procedures Configure Router A:...

  • Page 262: Troubleshooting Dlsw

    [RouterB] dlsw remote 1.1.1.1 [RouterB] dlsw bridge-set 7 [RouterB] interface ethernet 1/0 [RouterB-Ethernet1/0] bridge-set 7 Configure an ACL and apply it to the remote peer to implement SAP address filtering. This function also applies to the SDLC network. Troubleshooting DLSw Proper communication of the DLSw requires sound cooperation between involved SNA devices and DLSw-capable routers.
  • Page 263 If the PU type is correct, use the display dlsw circuit verbose command to check whether the virtual circuit can enter the CIRCUIT_EST state. If not, the MAC address of the SDLC peer is not correctly configured. Use the sdlc mac-map remote command to modify the configuration parameters.

  • Page 264: Configuring L2Tp

    Configuring L2TP Overview A VPDN is a VPN utilizing the dial-up function of public networks such as ISDN or PSTN networks to provide access services for enterprises, small ISPs, and telecommuters. VPDN provides an economical and effective point-to-point method for remote users to connect to their home LANs. VPDN technology uses a tunneling protocol to build secure VPNs for enterprises across public networks.

  • Page 265: L2Tp Message Types And Encapsulation Architecture

    • LNS—An L2TP network server (LNS) functions as both the L2TP server and the PPP end system. It is usually an edge device on an enterprise network. An LNS is the other endpoint of an L2TP tunnel and is a peer to the LAC. It is the logical termination point of a PPP session tunneled by the LAC.

  • Page 266: L2Tp Tunneling Modes And Tunnel Establishment Process

    Both control messages and PPP frames are transferred on the tunnel. L2TP uses hello packets to check a tunnel's connectivity. The LAC and the LNS regularly send hello packets to each other. If no response packet is received within a given amount of time, the tunnel is torn down. L2TP tunneling modes and tunnel establishment process Three typical L2TP tunneling modes Typical L2TP tunneling modes include the following:...
  • Page 267 L2TP tunnel establishment process Figure 94 Typical L2TP network Figure 95 shows an L2TP call's setup procedure in NAS-initiated mode. Figure 95 L2TP call setup procedure Remote system RADIUS server Host A Router A RADIUS server Router B (1) Call setup (2) PPP LCP setup (3) PAP or CHAP authenticaion...

  • Page 268: L2Tp Features

    The LAC sends the authentication information (the username and password) to its RADIUS server for authentication. The LAC RADIUS server authenticates the user. If the user passes authentication, the LAC initiates a tunneling request to the LNS. If tunnel authentication is required, the LAC sends a CHAP challenge to the LNS. The LNS returns a CHAP response and sends its CHAP challenge to the LAC.

  • Page 269: Protocols And Standards

    ACL. • L2TP-based EAD is usually used for remote users. For LAN users, deploy portal authentication. For information about packet-filter firewalls, AAA, RADIUS, and portal authentication, see HPE FlexNetwork MSR Router Series Comware 5 Security Configuration Guide. Protocols and standards •...

  • Page 270: Configuring Basic L2Tp Capabilities

    Task Remarks • Required in Configuring an LAC to establish an LAC-auto-initiated mode. L2TP tunnel • No need to configure in NAS-initiated mode. Configuring L2TP tunnel authentication Configuring L2TP connection Setting the hello interval Optional. parameters Enabling tunnel flow control Disconnecting tunnels by force To configure a device as an LNS in NAS-initiated, client-initiated, or LAC-auto-initiated mode, complete the following tasks:...

  • Page 271: Configuring An Lac

    LAC and LNS match. For example, the local tunnel name configured on the LAC must match the remote tunnel name configured on the LNS. L2TP must be enabled for L2TP configuration to take effect. Tunnel names are used during tunnel negotiation between an LAC and an LNS.

  • Page 272: Configuring Aaa Authentication For Vpn Users On Lac Side

    Step Command Remarks Enter system view. system-view Enter L2TP group view. l2tp-group group-number Optional. By default, AVP data is Specify that AVP data be transferred in plain text. tunnel avp-hidden transferred in hidden mode. This command takes effect when tunnel authentication is enabled. Configuring AAA authentication for VPN users on LAC side You can configure an LAC to perform AAA authentication for VPN users and initiate a tunneling request only for qualified users.

  • Page 273: Configuring An Lac To Establish An L2Tp Tunnel

    For information about AAA configuration commands and remote AAA authentication method configuration, see HPE FlexNetwork MSR Router Series Comware 5 Security Configuration Guide. Configuring an LAC to establish an L2TP tunnel To establish an L2TP tunnel in LAC-auto-initiated mode, you must create a virtual PPP user on the LAC.

  • Page 274: Configuring An Lns

    L2TP tunnel with the LNS. establish an L2TP tunnel. For more information about commands interface virtual-template, ppp authentication-mode, ppp pap, and ppp chap, see HPE FlexNetwork MSR Router Series Comware 5 Layer 2—WAN Command Reference. Configuring an LNS An LNS responds to the tunneling requests from an LAC, authenticates users, and assigns IP addresses to users.

  • Page 275: Configuring The Local Address And The Address Pool For Allocation

    ISP domain view. For a VPN user not requiring authentication, the IP address will be selected from the global address pool defined in system view. For details about the ip pool command, see HPE FlexNetwork MSR Router Series Comware 5 Security Command Reference.

  • Page 276: Configuring User Authentication On An Lns

    Step Command Remarks • If the L2TP group number is 1 (the default): allow l2tp Use either command. virtual-template By default, an LNS denies all virtual-template-number incoming calls. [ remote remote-name ] Specify the VT interface for [ domain domain-name ] receiving calls, the tunnel If the L2TP group number is 1, do name on the LAC, and the...

  • Page 277: Configuring Aaa Authentication For Vpn Users On An Lns

    Step Command Remarks Configure mandatory CHAP By default, CHAP authentication mandatory-chap authentication. is not performed on an LNS. Configuring LCP renegotiation In a NAS-initiated dial-up VPDN, a user first negotiates with the NAS at the start of a PPP session. If the negotiation succeeds, the NAS initiates an L2TP tunneling request and sends user information to the LNS.

  • Page 278: Configuring The Lns To Support Imsi Or Sn In Ppp Lcp Negotiation

    name match, the LNS establishes a session according to the group configuration. Thus, different sessions can be established for VPN users of different domains. If multiple L2TP groups on the LNS are configured with the same remote tunnel name, make sure that their tunnel authentication settings are the same.

  • Page 279: Configuring L2Tp Connection Parameters

    Step Command Remarks Required. Accept the IMSI or SN By default, the client does not negotiation requests from ppp lcp { imsi | sn } accept accept IMSI or SN negotiation the LNS. requests. Optional. Configure IMSI or SN ppp lcp { imsi | sn } string info By default, IMSI or SN information information.

  • Page 280: Enabling Tunnel Flow Control

    Step Command Remarks Enter system view. system-view Enter L2TP group view. l2tp-group group-number Optional. Set the hello interval. tunnel timer hello hello-interval 60 seconds by default. Enabling tunnel flow control The L2TP tunnel flow control function controls data packet transmission by buffering and adjusting data packets arriving out of order.

  • Page 281: Displaying And Maintaining L2Tp

    Step Command Remarks Enable the L2TP-based EAD This function is disabled by ppp access-control enable function. default. Specify the fragment match Optional. ppp access-control mode for all packet-filter match-fragments { exactly | Standard mode applies by firewalls on the VA interfaces normally } default.
  • Page 282 # Create a local user named vpdnuser, set the password, and enable the PPP service. <LAC> system-view [LAC] local-user vpdnuser [LAC-luser-vpdnuser] password simple Hello [LAC-luser-vpdnuser] service-type ppp [LAC-luser-vpdnuser] quit # Configure interface Async 1/0. [LAC] interface async 1/0 [LAC-Async1/0] ip address 1.1.1.1 255.255.255.0 [LAC-Async1/0] ppp authentication-mode chap [LAC-Async1/0] quit # Enable L2TP.

  • Page 283: Configuration Example For Client-Initiated Vpn

    [LNS-l2tp1] tunnel authentication [LNS-l2tp1] tunnel password simple aabbcc Configure the user: In the dial-up network window, enter vpdnuser as the username and Hello as the password. Verify the configuration: # After the dial-up connection is established, the user host can obtain an IP address (for example, 192.168.0.2) and can ping the private IP address of the LNS (192.168.0.1).
  • Page 284 [LNS-luser-vpdnuser] password simple Hello [LNS-luser-vpdnuser] service-type ppp [LNS-luser-vpdnuser] quit # Configure local authentication for the VPN user. [LNS] domain system [LNS-isp-system] authentication ppp local [LNS-isp-system] ip pool 1 192.168.0.2 192.168.0.100 [LNS-isp-system] quit # Enable L2TP. [LNS] l2tp enable # Configure the VT interface. [LNS] interface virtual-template 1 [LNS-virtual-template1] ip address 192.168.0.1 255.255.255.0 [LNS-virtual-template1] ppp authentication-mode chap domain system...

  • Page 285: Configuration Example For Lac-Auto-Initiated Vpn

    2.1.1.1 1701 l2tpuser Configuration example for LAC-auto-initiated VPN Network requirements Figure 98, create a virtual PPP user on the LAC and configure the LAC to initiate a As shown in tunneling request to the LNS to establish an L2TP tunnel for the virtual PPP user. When a VPN user accesses the corporate network, all packets between the VPN user and the corporate network are transmitted through the L2TP tunnel.
  • Page 286 # Enable tunnel authentication and configure the authentication key. [LNS-l2tp1] tunnel authentication [LNS-l2tp1] tunnel password simple aabbcc [LNS-l2tp1] quit # Configure a static route so that packets destined for the VPN will be forwarded through the L2TP tunnel. [LNS] ip route-static 10.2.0.0 16 virtual-template 1 Configure the LAC: # Configure IP addresses for the interfaces.

  • Page 287: Configuration Example For L2Tp Multi-Domain Application

    LocalSID RemoteSID LocalTID 8279 6822 # On the LNS, perform the display l2tp tunnel command to view the established L2TP tunnel. [LNS] display l2tp tunnel Total tunnel = 1 LocalTID RemoteTID RemoteAddress Port Sessions RemoteName 3.3.3.1 1701 # On the LNS, you should be able to ping 10.2.0.1, a private network address on the LAC side. This indicates that hosts on 10.2.0.0/16 and those on 10.1.0.0/16 can communicate with each other through the L2TP tunnel.
  • Page 288 In this example, Ethernet 1/1 and Ethernet 1/3 on the LAC are both user access interfaces. The IP address of Ethernet 1/2, through which the LAC connects to the tunnel, is 1.1.2.1. The IP address of Ethernet 1/1, through which the LNS connects to the tunnel, is 1.1.2.2. # Create two local users, set the passwords, and enable the PPP service.
  • Page 289 [LAC-l2tp2] tunnel authentication [LAC-l2tp2] tunnel password simple 12345 [LAC-l2tp2] quit [LAC] l2tp-group 1 [LAC-l2tp1] tunnel authentication [LAC-l2tp1] tunnel password simple 12345 Configure the LNS: # Enable L2TP. <LNS> system-view [LNS] l2tp enable # Enable L2TP for VPNs. [LNS] l2tpmoreexam enable # Create two local users, set the passwords, and enable the PPP service.

  • Page 290: Complicated Network Application

    [LNS-l2tp4] allow l2tp virtual-template 2 remote LAC-1 domain bbb.net [LNS-l2tp4] tunnel password simple 12345 If RADIUS authentication is required on the LNS, modify the AAA configurations as needed. For AAA configuration details, see HPE FlexNetwork MSR Router Series Comware 5 Security Configuration Guide. Configure the users: Create a dial-up connection on each host: On Host A, enter vpdn1@aaa.net as the username and 11111 as the password in the...

  • Page 291: Troubleshooting L2Tp

    Troubleshooting L2TP The VPN connection setup process is complex. The following presents an analysis of some common faults that might occur in the process. Before troubleshooting the VPN, make sure the LAC and LNS are connected correctly across the public network. Symptom 1 Users cannot log in.

  • Page 292: Configuring L2Tp-Based Ead

    L2TP-based EAD is usually used for remote users. For LAN users, deploy portal authentication. For information about packet filtering firewalls, AAA and RADIUS, and portal authentication, see HPE FlexNetwork MSR Router Series Comware 5 Security Configuration Guide. Configuration procedure Before configuring L2TP-based EAD, AAA, RADIUS, L2TP, packet filtering firewall, and PPP related configurations must be complete.

  • Page 293: Displaying And Maintaining L2Tp-Based Ead

    Displaying and maintaining L2TP-based EAD Task Command Remarks display ppp access-control Display statistics about dynamic { interface interface-type firewalls on the VA interfaces interface-number } [ | { begin | Available in any view created on the specified VT exclude | include } interface.
  • Page 294 [Router-Ethernet1/2] ip address 172.21.1.1 255.255.0.0 [Router-Ethernet1/2] quit # Assign an IP address to Ethernet 1/3. [Router] interface ethernet1/3 [Router-Ethernet1/3] ip address 10.22.2.10 255.255.255.0 [Router-Ethernet1/3] quit # Configure a RADIUS scheme that uses the CAMS/IMC server, setting the IP address to 10.110.91.146/24, and the keys to sysname.
  • Page 295 # Configure isolation ACL 3000 so that users failing security authentication can access only the quarantine area 10.22.2.0/24. [Router] acl number 3000 [Router-acl-adv-3000] rule 0 permit ip destination 10.22.2.0 0.0.0.255 Configure the CAMS/IMC server. Specify ACL 2000 as the security ACL and ACL 3000 as the isolation ACL in the security policy for the user.

  • Page 296: Configuring Bridging

    Major bridging technologies include transparent bridging, source-route bridging (SRB), translational bridging, and source-route translational bridging (SR/TLB). HPE devices support only transparent bridging. Transparent bridging bridges LAN segments of the same physical media type, primarily in Ethernet environments.
  • Page 297 Figure 101 Host A sends an Ethernet frame to Host B on LAN segment 1 Figure 102, when the bridge receives the Ethernet frame on bridge interface 1, it As shown in determines Host A is attached to bridge interface 1 and creates a mapping between the MAC address of Host A and bridge interface 1 in its bridge table.

  • Page 298: Forwarding And Filtering

    Figure 103 The bridge determines Host B is also attached to interface 1 MAC address: 00e0.fcbb.bbbb MAC address: 00e0.fcaa.aaaa Host B Host A Source address Destination address 00e0.fcbb. bbbb 00e0.fcaa.aaaa LAN segment 1 Bridge table MAC address Interface Bridge interface 1 00e 0.fcaa.aaaa Bridge 00e 0.fcbb.bbbb...
  • Page 299 Figure 105 Forwarding MAC address: 00e0.fcbb.bbbb MAC address: 00e0. fcaa.aaaa Host B Host A Source address Destination address 00e0.fcaa.aaaa 00e0. fccc. cccc Bridge table LAN segment 1 MAC address Interface Bridge interface 1 00e0.fcaa.aaaa Bridge 00e0.fcbb.bbbb 00e0.fccc.cccc Bridge interface 2 00e0.fcdd.dddd LAN segment 2 Source address Destination address...

  • Page 300: Bridging Configuration Task List

    Figure 107 The proper MAC-to-interface mapping is not found in the bridge table When a bridge receives a broadcast or multicast frame, it forwards the frame to all interfaces other than the receiving interface. Bridging configuration task list Task Remarks Configuring basic bridging functionalities Required.

  • Page 301: Configuration Procedure

    • When you configure transparent bridging over X.25, you must configure X.25 on the interface as the link layer protocol for interface encapsulation and configure the operating mode and datagram format of the interface. When establishing transparent bridging over X.25, you must configure mappings between bridge addresses and X.25 addresses defined in X.121.

  • Page 302: Configuring Bridge Routing

    Step Command Remarks Enter system view. system-view Optional. Enable dynamic address bridge bridge-set learning learning. Enabled by default. bridge bridge-set mac-address Optional. Configure a static bridge mac-address { deny | permit } No static table entry is configured table entry. [ dlsw | interface interface-type by default.

  • Page 303: Enabling Vlan Transparency

    Step Command Remarks Optional. Configure a description for By default, the description of an the bridge-template description text interface uses the format interface. interface name Interface. Configure an IP address for ip address ip-address { mask | By default, an interface does not the bridge-template mask-length } [ sub ] have an IP address.

  • Page 304: Displaying And Maintaining Bridging

    Step Command Remarks Enter system view. system-view Enable bridging. Bridging is disabled by default. bridge enable A bridge-set is disabled by Enable a bridge-set. bridge bridge-set enable default. interface interface-type Enter interface view. interface-number Add the interface to the No interface is in any bridge-set bridge-set bridge-set bridge-set.

  • Page 305: Transparent Bridging Configuration Examples

    Task Command Remarks reset counters interface Clear statistics for [ bridge-template Available in user view. bridge-template interfaces. [ interface-number ] ] Transparent bridging configuration examples Configuration example for transparent bridging over ATM Network requirements Figure 108, two LAN segments, LAN 1 and LAN 2, are attached to Router A and Router As shown in B, respectively, which are interconnected through their respective ATM interfaces.

  • Page 306: Configuration Example For Transparent Bridging Over Ppp

    Configuration example for transparent bridging over PPP Network requirements Figure 109, two LAN segments, LAN 1 and LAN 2, are attached to Router A and Router As shown in B, respectively, which are interconnected over PPP. Configure the two routers to enable transparent bridging over PPP between the two LAN segments.
  • Page 307 Figure 110 Network diagram Configuration procedure Configure Router A: <RouterA> system-view [RouterA] bridge enable [RouterA] bridge 1 enable [RouterA] interface virtual-template 1 [RouterA-Virtual-Template1] bridge-set 1 [RouterA-Virtual-Template1] quit [RouterA] interface ethernet 1/1 [RouterA-Ethernet1/1] bridge-set 1 [RouterA-Ethernet1/1] quit [RouterA] interface serial 2/1 [RouterA-Serial2/1] link-protocol ppp [RouterA-Serial2/1] ppp mp virtual-template 1 [RouterA-Serial2/1] quit...

  • Page 308: Configuration Example For Transparent Bridging Over Fr

    Configuration example for transparent bridging over FR Network requirements Figure 1 1 1, two LAN segments, LAN 1 and LAN 2, are attached to Router A and Router B, As shown in respectively, which are interconnected over FR. Configure the two routers to enable transparent bridging over FR between the two LAN segments.

  • Page 309: Configuration Example For Transparent Bridging Over Hdlc

    Figure 112 Network diagram Configuration procedure Configure Router A: <RouterA> system-view [RouterA] bridge enable [RouterA] bridge 1 enable [RouterA] interface ethernet 1/1 [RouterA-Ethernet1/1] bridge-set 1 [RouterA-Ethernet1/1] quit [RouterA] interface serial 2/0 [RouterA-Serial2/0] link-protocol x25 dce [RouterA-Serial2/0] x25 x121-address 100 [RouterA-Serial2/0] x25 map bridge x121-address 200 broadcast [RouterA-Serial2/0] bridge-set 1 Configure Router B: <RouterB>...

  • Page 310: Configuration Example For Bridging With Fr Sub-Interface Support

    Configuration procedure Configure Router A: <RouterA> system-view [RouterA] bridge enable [RouterA] bridge 1 enable [RouterA] interface ethernet 1/1 [RouterA-Ethernet1/1] bridge-set 1 [RouterA-Ethernet1/1] quit [RouterA] interface serial 2/0 [RouterA-Serial2/0] link-protocol hdlc [RouterA-Serial2/0] bridge-set 1 Configure Router B: <RouterB> system-view [RouterB] bridge enable [RouterB] bridge 1 enable [RouterB] interface ethernet 1/1 [RouterB-Ethernet1/1] bridge-set 1...
  • Page 311 Configuration procedure Configure Router A: <RouterA> system-view [RouterA] bridge enable [RouterA] bridge 1 enable [RouterA] bridge 2 enable [RouterA] interface ethernet 1/1 [RouterA-Ethernet1/1] bridge-set 1 [RouterA-Ethernet1/1] quit [RouterA] interface ethernet 1/2 [RouterA-Ethernet1/2] bridge-set 2 [RouterA-Ethernet1/2] quit [RouterA] interface serial 2/0 [RouterA-Serial2/0] link-protocol fr [RouterA-Serial2/0] quit [RouterA] interface serial 2/0.1...

  • Page 312: Bridge Routing Configuration Example

    However, you must configure the same DLCI on both the DCE and DTE sides by using the fr dlci command. This is an alternative method of configuring bridging over FR. For more information about frame relay, see "Configuring frame relay." Bridge routing configuration example Network requirements Figure 1...
  • Page 313 Figure 116 Network diagram Configuration procedure Configure Router A: # Enable bridging globally. [RouterA] bridge enable [RouterA] bridge 1 enable # Configure a dialup access control list. [RouterA] dialer-rule 1 bridge permit # Configure dialing on the ISDN BRI interface BRI 2/0. [RouterA] interface bri2/0 [RouterA-Bri2/0] link-protocol ppp [RouterA-Bri2/0] dialer enable-circular...

  • Page 314: Vlan Transparency Configuration Example

    [RouterB-Dialer2] link-protocol ppp [RouterB-Dialer2] bridge-set 1 [RouterB-Dialer2] dialer enable-circular [RouterB-Dialer2] dialer-group 1 [RouterB-Dialer2] dialer number 660206 [RouterB-Dialer2] quit # Add Ethernet 1/1 to bridge set 1. [RouterB] interface ethernet1/1 [RouterB-Ethernet1/1] bridge-set 1 VLAN transparency configuration example Network requirements Figure 1 17, the trunk interfaces of Switch A and Switch B are assigned to the same As shown in VLAN.
  • Page 315 # Enable the bridging function. <RouterB> system-view [RouterB] bridge enable [RouterB] bridge 2 enable # Add Ethernet 1/1 to bridge set 2 and enable VLAN transparency on Ethernet 1/1. Add ATM 5/0 to bridge-set 2 and enable VLAN transparency. [RouterA] interface ethernet 1/1 [RouterB-Ethernet1/1] bridge-set 2 [RouterB-Ethernet1/1] bridge vlanid-transparent-transmit enable [RouterB-Ethernet1/1] quit...

  • Page 316: Configuring Etoppp And Etofr

    Configuring EtoPPP and EtoFR Ethernet to PPP (EtoPPP) converts on the data link layer between Ethernet and PPP for IP packets. Similarly, Ethernet to Frame Relay (EtoFR) converts on the link layer between Ethernet and Frame Relay for IP packets. With EtoPPP or EtoFR, a device encapsulates an Ethernet-encapsulated IP packet with PPP or FR encapsulation, and then forwards the packet rather than routes the packet.

  • Page 317: Creating An Etofr Translation Mapping

    • The interface specified by interface-type1 interface-number1 can only be a Layer 3 Ethernet interface, Ethernet subinterface, or VLAN interface. • The interface specified by interface-type2 interface-number2 must be configured with PPP encapsulation. This interface can only be an MP group interface, synchronous serial interface, POS interface, or POS subinterface.

  • Page 318: Etoppp And Etofr Configuration Examples

    Task Command Remarks Clear the statistics about the EtoPPP translation mapping entry for an reset etoppp translate [ interface Available in user interface or all EtoPPP translation interface-type interface-number ] view. mapping entries if no interface is specified. display etofr translate [ interface Display EtoFR translation mapping interface-type interface-number ] [ | Available in any...

  • Page 319: Etofr Configuration Example

    # Configure the IP address of the synchronous serial interface formed by timeslot bundling on interface T1 2/0. <RouterC> system-view [RouterC] controller t1 2/0 [RouterC-T1 2/0] channel-set 0 timeslot-list 1-24 [RouterC-T1 2/0] quit [RouterC] interface serial 2/0:0 [RouterC-Serial2/0:0] ip address 1.1.1.2 24 Configure the EtoPPP device (Router B): # Create the EtoPPP mapping for forwarding the traffic between the CE and the PE.
  • Page 320 # Configure the IP address of the synchronous serial interface formed by timeslot bundling on interface T1 2/0. <RouterC> system-view [RouterC] controller t1 2/0 [RouterC-T1 2/0] channel-set 0 timeslot-list 1-24 [RouterC-T1 2/0] quit [RouterC] interface serial 2/0:0 [RouterC-Serial2/0:0] link-protocol fr [RouterC-Serial2/0:0] fr interface-type dce [RouterC-Serial2/0:0] fr dlci 20 [RouterC-Serial2/0:0] ip address 1.1.1.2 24...

  • Page 321: Configuring Lapb And X.25

    Configuring LAPB and X.25 Overview X.25 X.25 is an ITU-T standard protocol suite for packet switched WAN communications. It defines how connections are established and maintained between user devices and network devices. The first draft of X.25 was released in 1974. It incorporated the experience and recommendations from Telenet and Tymnet in the USA and the Datapac packet-switched network in Canada.

  • Page 322: Lapb

    • The X.25 physical layer defines the physical and electrical specifications between DTE and DCE. • The X.25 data link layer defines the format and specifications of the frames exchanged between DTE and DCE. Link Access Procedure, Balanced (LAPB) is the data link protocol of X.25. •...

  • Page 323: X.25 Switching

    X.25 virtual circuits are logical links rather than physical links as in circuit switching networks. They include two categories: • PVCs—Which are suitable for frequent, constant data transmission. • SVCs—Which are suitable for bursty data transmission. Each virtual circuit is uniquely identified by a virtual circuit ID. Each packet sent by a DTE carries a virtual circuit ID, which enables the DCEs in the switched network to forward the packet correctly to its destination.

  • Page 324: Configuration Procedure

    LAPB N1 parameter The LAPB N1 parameter specifies the maximum number of bits that an I frame can hold. The maximum N1 value is calculated by using the following formula: (hardware MTU + protocol header) × 8 LAPB N2 parameter N2 sets the maximum number of times a data frame can be sent from DCE to DTE or vice versa.

  • Page 325: Configuring An X.25 Interface

    Step Command Remarks Optional. The default N1 is calculated according to the MTU, the upper Configure LAPB parameter layer protocol, and the modulus lapb max-frame n1-value value. You can configure this command only when LAPB carries the upper layer protocol X.25. Optional.
  • Page 326 • X.25 virtual circuit range The X.25 protocol can create multiple logical virtual connections over a physical link between DTE and DCE. These virtual connections are called virtual circuits or logical channels. Up to 4095 virtual circuits can be established by X.25, and the virtual circuit number is in the range of 1 to 4095.
  • Page 327 Parameter Description Highest Two-way Channel. Lowest Outgoing-only Channel. Highest Outgoing-only Channel. Each range (except PVC range) is defined by two parameters operating as the upper limit and lower limit. The parameters are in the range of 1 to 4095 (including 1 and 4095), but they are regarded correct only if they meet the following conditions: In strict ascending order, 1 ≤...
  • Page 328 Reset an interface by using the shutdown and undo shutdown commands to make a new configuration take effect Configuration procedure To configure an X.25 interface: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number The default setting is PPP. Enable X.25 encapsulation link-protocol x25 [ dce |dte ] With X.25 encapsulation enabled,...

  • Page 329: Configuring X.25 Interface Supplementary Parameters

    Configuring X.25 interface supplementary parameters Introduction to X.25 interface supplementary parameters It is necessary to configure certain supplementary X.25 parameters in some special network environments. The following sections are related to the following supplementary parameters. • X.25 layer 3 delay timer X.25 protocol defines a series of timers to facilitate its procedure.
  • Page 330 Matching mode Description Example Extended left-most matching "$1234 …" will match 1234679 left-ext mode, in which the alias string is and 1234872, but will not match in the form of $1234…. 123468 and 12346890. Right-most matching mode, in "1234$" will match 791234 and right which the alias string is in the 6901234, but will not match...

  • Page 331: Configuring An X.25 Subinterface

    Step Command Remarks interface interface-type Enter interface view. interface-number Optional. By default, the value for DTE is Set the restart timer delay value. x25 timer tx0 seconds 180 seconds, and the value for DCE is 60 seconds. Optional. Set the call request timer for DTE By default, the value for DTE is or the call indication timer for x25 timer tx1 seconds...

  • Page 332: Configuring X.25 Datagram Transmission

    Step Command Remarks Enter system view. system-view Enter main interface view. interface serial interface-number Enable X.25. link-protocol x25 Return to system view. quit interface serial Create an X.25 p2mp applies by default. interface-number.subnumber subinterface. [ p2mp | p2p ] If the link layer protocol of an interface is LAPB, HDLC, or PPP, no subinterface can be created on it. Configuring X.25 datagram transmission Configuring basic X.25 datagram transmission functionality Introduction to X.25 datagram transmission...

  • Page 333: Configuring Additional Parameters For X.25 Datagram Transmission

    Configuration guidelines • Because the default two-way channel range (LTC=1, HTC=1024) does not support PVC configuration, specify a virtual circuit range by using the x25 vc-range command to create a PVC. • If a PVC has no related parameters configured, its traffic control parameters are the same as its X.25 interface set by using the x25 packet-size and x25 window-size commands.
  • Page 334 Task Remarks Enabling the sending of broadcast packets through Optional. X.25 Restricting the use of address mapping Optional. Setting the maximum SVC idle interval For the sake of cost saving, specify an SVC idle time on the expiration of which the SVC will be disconnected.
  • Page 335 Setting the packet acknowledgement threshold By setting the packet acknowledgement threshold (also called "receive-threshold"), you enable the receiving router to send acknowledgement packets before the input window gets full. According to the X.25 protocol, the receiver sends an acknowledgement when the input window (set with the window-size input-window-size command) gets full.
  • Page 336 Step Command Remarks Perform window size x25 call-facility window-size Optional. negotiation when initiating input-window-size Not configured by default. a call. output-window-size Optional. Request reverse charging x25 call-facility when initiating a call. reverse-charge-request Not configured by default. Optional. Receive calls with reverse x25 reverse-charge-accept charging requests.
  • Page 337 Step Command Remarks x25 map protocol-type 10. Carry transmission delay Optional. protocol-address x121-address request when initiating a x.121-address send-delay Not configured by default. call. milliseconds x25 map protocol-type Optional. 11. Specify the ROA. protocol-address x121-address Not configured by default. x.121-address roa-list name "Configuring X.25 closed user group."...

  • Page 338: Configuring X.25 Switching

    some cases, some address mappings are used for only outgoing calls, and others are used for only incoming calls. To restrict the use of an address mapping: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number x25 map protocol-type Disable initiating calls using protocol-address x121-address...

  • Page 339: Configuring Flow Control Negotiation Of X.25 Switching

    Step Command Remarks • Add a PVC: a. interface interface-type interface-number b. x25 vc-range { bi-channel ltc htc [ out-channel loc hoc ] | in-channel lic hic [ bi-channel ltc htc ] [ out-channel loc hoc ] | out-channel loc hoc } c.

  • Page 340: Configuring X.25 Load Sharing

    refragment the packets depending on the flow control parameters of the link between Router B and Router C. By default, flow control negotiation is enabled for X.25 switching. To configure flow control negotiation on an X.25 interface: Step Command Remarks Enter system view.
  • Page 341 Figure 128 X.25 load sharing scenario Figure 128, server A and server B, which are providing identical services, are assigned to hunt group HG 1. Server A and server B use the address 9999, and the hunt group uses the address 8888. Enable destination address substitution on Router A to replace the address 8888 with the address 9999.

  • Page 342: Configuring X.25 Closed User Group

    Step Command Remarks channel interface interface-type Add an interface or Annex G interface-number [ dlci DLCI to the hunt group dlci-number ] Add an XOT channel to the channel xot ip-address hunt group. Exit to system view. quit x25 switch svc x.121-address [ sub-dest destination-address | Create an X.25 switching sub-source source-address ] *...
  • Page 343 the system removes the CUG facilities only of those incoming calls matching the mapping specified as preference rule, but let other incoming calls with CUG facilities pass through. The details are as follows: Incoming suppression policy—The system lets the incoming calls without CUG facilities pass through, but suppresses the incoming calls with CUG facilities but without access configuration configured by the CUG mapping rule.

  • Page 344: Configuring X.25 Pad Remote Access Service

    Configuring X.25 PAD remote access service Packet Assembly/Disassembly (PAD) is an X.25-specific concept. Traditionally, only X.25 terminals could connect to an X.25 network. These terminals must be packet terminals that support X.25 procedures in terms of hardware and software. However, many terminals in common use are non-X.25 terminals.

  • Page 345: Configuring Xot

    You can nest a pad command within another pad command or a telnet command. By nesting commands, you can do the following on your router: • Place an X.25 PAD call to log in to another router; and from that router, place another X.25 PAD call to log in to a third router, and so on.

  • Page 346: Configuration Procedure

    Figure 132 Typical XOT application X.25 depends on its link layer protocol LAPB to provide reliable links. To ensure link reliability within the IP network, XOT uses TCP, which offers reliable transmission and window flow control mechanisms, to tunnel X.25 packets across the IP network as application payload. In this case, TCP works at the link layer for X.25 and the IP network is analogous to a big X.25 switch.
  • Page 347 • In SVC mode, X.25 routes are required. • Because the default two-way channel range (LTC=1, HTC=1024) does not support PVC configuration, you must specify a virtual circuit range by using the x25 vc-range command to create a PVC. To configure XOT: Step Command Remarks...
  • Page 348 Optional. attributes. attributes." For more information about IP address configuration, see HPE FlexNetwork MSR Router Series Comware 5 Layer 3—IP Services Command Reference. Configuring XOT optional attributes After a TCP link is established, TCP will also not be cleared easily even if the link is interrupted.

  • Page 349: Configuring X.25 Over Fr

    Configuring X.25 over FR X.25 over FR X.25 over FR carries X.25 packets over FR to interconnect two X.25 networks across an FR network, Figure 133. as shown in Figure 133 X.25 over FR network diagram Configuring an SVC application of X.25 over FR X.25 over FR is an extension to X.25 switching, so you must enable X.25 switch first.

  • Page 350: Configuring A Pvc Application Of X.25 Over Fr

    Step Command Remarks x25 switch svc [ -number ] x.121-address [ sub-dest Configure the X.25 over FR destination-address | sub-source SVC route source-address ] * interface interface-type interface-number dlci dlci-number Configuring a PVC application of X.25 over FR X.25 over FR is an extension to X.25 switching, so you must enable X.25 switch first. To configure a PVC application of X.25 over FR: Step Command...

  • Page 351: Configuring X2T

    Configuring X2T X.25 to TCP switch (X2T) connects X.25 to TCP/IP networks, allowing the access between X.25 and Figure 134 IP hosts. shows a typical X2T application scenario. Figure 134 Typical X2T application scenario The X.25 terminal has an X.121 address on the IP host. Whenever the router receives an X.25 call request packet, it checks the destination address of X.121 in the packet and looks up in the X2T routing table for a match.

  • Page 352: Displaying And Maintaining Lapb And X.25

    Step Command Remarks Configure an X.25-to-IP X2T translate x25 x.121-address ip forwarding route. ip-address port port-number • Configure a PVC forwarding route for a PVC link: translate ip ip-address port port-number pvc interface-type interface-number pvc-number • Configure an SVC route and a forwarding route for an SVC link: a.

  • Page 353: Lapb Configuration Example

    Task Command Remarks display x25 vc [ lci-number ] [ | Display the specified X.25 virtual { begin | exclude | include } Available in any view. circuit. regular-expression ] display x25 xot [ | { begin | Display X.25 XOT connection exclude | include } Available in any view.
  • Page 354 [RouterA-Serial2/0] lapb window-size 127 [RouterA-Serial2/0] shutdown [RouterA-Serial2/0] undo shutdown Configure Router B: # Enter interface view. <RouterB> system-view [RouterB] interface serial 2/0 # Assign an IP address for the interface. [RouterB-Serial2/0] ip address 10.1.1.1 255.0.0.0 # Configure the link layer protocol of the interface as LAPB, and specify it to operate in DCE mode.

  • Page 355: X.25 Configuration Examples

    0 frame errors Output:633 packets, 7737 bytes 0 errors, 0 underruns, 0 collisions 0 deferred DCD=UP DTR=UP DSR=UP RTS=UP CTS=UP # Display information about interface Serial 2/0 on Router B. [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 10.1.1.1/8 Primary...
  • Page 356 Figure 136 Network diagram Configuration procedure Configure Router A: # Enter interface view. <RouterA> system-view [RouterA] interface serial 2/0 # Assign an IP address for the interface. [RouterA-Serial2/0] ip address 202.38.60.1 255.255.255.0 # Configure the link layer protocol of the interface as X.25, and configure the interface to operate in DTE mode.

  • Page 357: Direct Connection Of Two Routers Connecting Through Serial Interfaces (Two Address Mappings)

    Verifying the configuration The virtual circuit configured in this example is an SVC. The routers establish it only when they need to communicate. # Ping Router B from Router A. [RouterA-Serial2/0] ping 202.38.60.2 PING 202.38.60.2: 56 data bytes, press CTRL_C to break Reply from 202.38.60.2: bytes=56 Sequence=1 ttl=255 time=33 ms Reply from 202.38.60.2: bytes=56 Sequence=2 ttl=255 time=27 ms Reply from 202.38.60.2: bytes=56 Sequence=3 ttl=255 time=26 ms...
  • Page 358 Figure 137 Network diagram S2/0 S2/0 202.38.160.1/24 202.38.160.2/24 X121 address: 20112451 X121 address: 20112452 Router A Router B Configuration procedure Configure Router A: # Enter interface view. <RouterA> system-view [RouterA] interface serial 2/0 # Assign an IP address for the interface. [RouterA-Serial2/0] ip address 202.38.160.1 255.255.255.0 # Configure the link layer protocol as X.25 and the interface to operate in DTE mode.
  • Page 359 [RouterB-Serial2/0] x25 vc-per-map 2 Verifying the configuration The virtual circuit configured in this example is an SVC. The routers establish it only when they must communicate. # Ping Router B from Router A. [RouterA-Serial2/0] ping 202.38.160.2 PING 202.38.160.2: 56 data bytes, press CTRL_C to break Reply from 202.38.160.2: bytes=56 Sequence=1 ttl=255 time=33 ms Reply from 202.38.160.2: bytes=56 Sequence=2 ttl=255 time=26 ms Reply from 202.38.160.2: bytes=56 Sequence=3 ttl=255 time=27 ms...

  • Page 360: Connecting The Router To X.25 Public Packet Network

    Connecting the router to X.25 public packet network Network requirements Figure 138, Router A, Router B, and Router C are connected to the same X.25 network. As shown in The requirements are: • The IP addresses of the interfaces Serial 2/0 of the three routers are 168.173.24.1/24, 168.173.24.2/24, and 168.173.24.3/24.

  • Page 361: Configuring Virtual Circuit Range

    [RouterB] interface serial 2/0 [RouterB-Serial2/0] ip address 168.173.24.2 255.255.255.0 # Access the public packet network, and configure the router to operate in DTE mode. [RouterB-Serial2/0] link-protocol x25 dte [RouterB-Serial2/0] x25 x121-address 30561002 [RouterB-Serial2/0] x25 window-size 5 5 [RouterB-Serial2/0] x25 packet-size 512 512 [RouterB-Serial2/0] x25 vc-range bi-channel 1 32 [RouterB-Serial2/0] x25 map ip 168.173.24.1 x121-address 30561001 [RouterB-Serial2/0] x25 map ip 168.173.24.3 x121-address 30561003...

  • Page 362: Transmitting Ip Datagrams Through X.25 Pvcs

    [Router] interface serial 2/0 [Router-Serial2/0] link-protocol x25 [Router-Serial2/0] x25 vc-range in-channel 9 16 bi-channel 17 1024 [Router-Serial2/0] shutdown [Router-Serial2/0] undo shutdown Verifying the configuration # Display the configuration of interface Serial2/0. [Router-Serial2/0] display this interface Serial2/0 link-protocol x25 x25 vc-range in-channel 9 16 bi-channel 17 1024 return Transmitting IP datagrams through X.25 PVCs Network requirements...
  • Page 363 [RouterA] interface ethernet 1/1 [RouterA-Ethernet1/1] ip address 202.38.165.1 255.255.255.0 [RouterA-Ethernet1/1] quit # Configure interface Serial 2/0. [RouterA] interface serial 2/0 [RouterA-Serial2/0] ip address 192.149.13.1 255.255.255.0 [RouterA-Serial2/0] link-protocol x25 [RouterA-Serial2/0] x25 x121-address 1004358901 [RouterA-Serial2/0] x25 vc-range bi-channel 9 1024 [RouterA-Serial2/0] x25 pvc 3 ip 192.149.13.2 x121-address 1004358902 broadcast packet-size 512 512 window-size 5 5 [RouterA-Serial2/0] shutdown [RouterA-Serial2/0] undo shutdown...

  • Page 364: X.25 Subinterface Configuration Example

    Figure 140 One virtual circuit consisting of several logical channels The PVC 3 and PVC 4 mentioned in the example refer to the numbers of the logical channels between the routers and the PBXs directly connected. The two sides of the PVC can identify the same PVC by using their logical channel numbers, however, without the likelihood of causing any mistake.
  • Page 365 Figure 141 Network diagram Configuration procedure Configure Router A: <RouterA> system-view [RouterA] interface serial 2/0 [RouterA-Serial2/0] link-protocol x25 dte [RouterA-Serial2/0] x25 x121-address 100 [RouterA-Serial2/0] quit # Configure subinterface Serial 2/0.1, and X.25 mapping to Router B. [RouterA] interface serial 2/0.1 [RouterA-Serial2/0.1] ip address 10.1.1.2 255.255.0.0 [RouterA-Serial2/0.1] x25 map ip 10.1.1.1 x121-address 200 [RouterA-Serial2/0.1] quit...
  • Page 366 [RouterD-Serial2/0] quit [RouterD] interface serial 2/1 [RouterD-Serial2/1] link-protocol x25 dce [RouterD-Serial2/1] quit [RouterD] interface serial 2/2 [RouterD-Serial2/2] link-protocol x25 dce [RouterD-Serial2/2] quit # Configure SVC switching routes. [RouterD] x25 switching [RouterD] x25 switch svc 100 interface serial 2/0 [RouterD] x25 switch svc 200 interface serial 2/1 [RouterD] x25 switch svc 300 interface serial 2/2 Verifying the configuration The virtual circuit configured in this example is an SVC.

  • Page 367: Svc Application Of Xot

    Packet Size: input 128 output 128 Local PS: 5 Local PR: 5 Remote PS: 4 Remote PR: 5 Local Busy: FALSE Reset times: 0 Input/Output: DATA 5/5 INTERRUPT 0/0 RR 0/0 RNR 0/0 REJ 0/0 Bytes 420/420 Send Queue(Current/Max): 0/200 # Display the X.25 SVC switching table of Router D.

  • Page 368: Pvc Application Of Xot

    Configure Router D: # Configure basic X.25. <RouterD> system-view [RouterD] interface serial 2/0 [RouterD-Serial2/0] link-protocol x25 dte ietf [RouterD-Serial2/0] x25 x121-address 2 [RouterD-Serial2/0] x25 map ip 1.1.1.1 x121-address 1 [RouterD-Serial2/0] ip address 1.1.1.2 255.0.0.0 Configure Router B: # Enable X.25 switching. <RouterB>...
  • Page 369 Figure 143 Network diagram Configuration procedure Configure Router A: # Configure basic X.25. <RouterA> system-view [RouterA] interface serial 2/0 [RouterA-Serial2/0] link-protocol x25 dte ietf [RouterA-Serial2/0] x25 x121-address 1111 [RouterA-Serial2/0] x25 vc-range in-channel 10 20 bi-channel 30 1024 [RouterA-Serial2/0] x25 pvc 1 ip 1.1.1.2 x121-address 2222 [RouterA-Serial2/0] ip address 1.1.1.1 255.0.0.0 Configure Router D: # Configure basic X.25.

  • Page 370: Svc Application Of X.25 Over Fr

    # Configure Serial 2/0 and an XOT route. [RouterC] interface serial 2/0 [RouterC-Serial2/0] link-protocol x25 dce ietf [RouterC-Serial2/0] x25 vc-range in-channel 10 20 bi-channel 30 1024 [RouterC-Serial2/0] x25 xot pvc 2 10.1.1.1 interface serial 2/0 pvc 1 # Configure Ethernet 1/1. [RouterC] interface ethernet 1/1 [RouterC-Ethernet1/1] ip address 10.1.1.2 255.0.0.0 SVC application of X.25 over FR...

  • Page 371: Pvc Application Of X.25 Over Fr

    [RouterB] x25 switching # Configure Serial 2/0 as an X.25 interface. [RouterB] interface serial 2/0 [RouterB-Serial2/0] link-protocol x25 dce # Configure Serial 2/1 as an FR interface. [RouterB] interface serial 2/1 [RouterB-Serial2/1] link-protocol fr [RouterB-Serial2/1] fr interface-type dce # Configure the FR Annex G DLCI. [RouterB-Serial2/1] fr dlci 100 [RouterB-fr-dlci-Serial2/1-100] annexg dce # Configure X.25 local switching.
  • Page 372 Figure 145 Network diagram Configuration procedure Configure Router A: # Configure X.25 basic functions. <RouterA> system-view [RouterA] interface serial 2/0 [RouterA-Serial2/0] link-protocol x25 dte [RouterA-Serial2/0] x25 x121-address 1 [RouterA-Serial2/0] x25 vc-range bi-channel 10 20 [RouterA-Serial2/0] x25 pvc 1 ip 1.1.1.2 x121-address 2 [RouterA-Serial2/0] ip address 1.1.1.1 255.255.255.0 Configure Router D: # Configure X.25 basic functions.

  • Page 373: X.25 Load Sharing Application

    [RouterB-Serial2/1] fr interface-type dce # Configure the FR Annex G DLCI. [RouterB-Serial2/1] fr dlci 100 [RouterB-fr-dlci-Serial2/1-100] annexg dce # Apply the X.25 template to the FR Annex G DLCI. [RouterB-fr-dlci-Serial2/1-100] x25-template switch Configure Router C: # Enable X.25 switching. <RouterC> system-view [RouterC] x25 switching # Configure the PVC switching route on the X.25 interface Serial 2/0.
  • Page 374 Figure 146 Network diagram Configuration procedure Configure Router A: # Configure the link layer protocol of interface Serial 2/0 as X.25, and configure it to operate in DCE mode. <RouterA> system-view [RouterA] interface serial 2/0 [RouterA-Serial2/0] link-protocol x25 dce # In the same way, configure the link layer protocol of the interface Serial 2/2, Serial 2/3, and Serial 2/4 as X.25 and configure them to operate in DCE mode.
  • Page 375 [RouterA-hg-hg1] channel interface serial 2/2 [RouterA-hg-hg1] channel interface serial 2/1 dlci 100 [RouterA-hg-hg1] channel xot 10.1.1.2 [RouterA-hg-hg1] quit # Configure a X.25 switching route forwarded towards the hunt group hg1, and enable destination address and source address substitution, substituting 3333 and 8888 for source and destination addresses of packets destined to hunt group address 2222.

  • Page 376: Implementing X.25 Load Sharing Function For Ip Datagram Transmission

    [RouterD-Serial2/0] link-protocol x25 dce [RouterD-Serial2/0] quit # Assign an IP address for interface Ethernet 1/1. [RouterD] interface ethernet 1/1 [RouterD-Ethernet1/1] ip address 10.1.1.2 255.255.255.0 [RouterD-Ethernet1/1] quit # Configure an X.25 switching route to an XOT channel. [RouterD] x25 switch svc 3333 xot 10.1.1.1 # Configure an X.25 switching route to Router E.
  • Page 377 Configuration procedure In this example, because the network providers have configured load sharing on the packet switch, you only need to configure X.25 switching. Two lines have been connected to the same peer on Router C, so you must configure a virtual IP address and two static routes on interface Serial 2/1 to "cheat"...
  • Page 378 [RouterC-Serial2/0] x25 map ip 1.1.1.1 x121-address 1111 [RouterC-Serial2/0] x25 map ip 2.1.1.1 x121-address 1111 [RouterC-Serial2/0] x25 map ip 1.1.1.2 x121-address 2222 [RouterC-Serial2/0] x25 map ip 2.1.1.2 x121-address 2222 # Configure interface Serial 2/1. [RouterC] interface serial 2/1 [RouterC-Serial2/1] link-protocol x25 dte [RouterC-Serial2/1] x25 x121-address 3333 [RouterC-Serial2/1] ip address 2.1.1.3 255.255.255.0 [RouterC-Serial2/1] x25 map ip 1.1.1.1 x121-address 1111...

  • Page 379: Tcp/Ip Header Compression Protocol Application

    TCP/IP header compression protocol application Network requirements Figure 148, two routers are directly connected. As shown in Figure 148 Network diagram Configuration procedure Configure RouterA: # Configure the link layer protocol of Serial 2/0 as X.25, and configure the interface to operate in DTE mode.

  • Page 380: X.25 Pad Configuration Example

    --- 16.16.16.2 ping statistics --- 5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 26/28/36 ms X.25 PAD configuration example Network requirements Figure 149, configure X.25 PAD so that Router B could place X.25 PAD calls to log in to As shown in Router A and then configure Router A.

  • Page 381: X2T Svc Configuration Example

    [RouterB-Serial2/0] x25 x121-address 2 [RouterB-Serial2/0] quit [RouterB] quit # Place an X.25 PAD call to Router A. <RouterB> pad 1 Calling 1 ... ****************************************************************************** * Copyright (c) 2004-2010 Hangzhou H3C Tech. Co., Ltd. All rights reserved. * Without the owner's prior written consent, * no decompiling or reverse-engineering shall be allowed.

  • Page 382: X2T Pvc Configuration Example

    X2T PVC configuration example Network requirements Figure 151, the router connects X.25 and IP networks together. As shown in In this connection, the X.25 terminal communicates with the router through PVC and the X2T technology applied on the router enables the communication between the IP host and the X.25 terminal.

  • Page 383: Failed To Ping The Other Side With X.25 On Both Sides Being Up

    Failed to ping the other side with X.25 on both sides being up Symptom Despite X.25 being up on both sides, the other side cannot be pinged. Analysis The maximum length of frames set at one side is too small. Solution Enable the debugging on both sides.

  • Page 384: Continuous Resets And Clears Of The Virtual Circuit Established

    Continuous resets and clears of the virtual circuit established Symptom The virtual circuit can be set up, but is frequently reset or cleared during data transmission. Analysis The symptom might be caused by incorrect flow control parameter settings. Solution • If the two sides are connected directly, verify the output window and input window of the local end match the remote end.

  • Page 385: Failed To Ping Xot Pvcs

    Analysis The physical status and protocol status of the interface are not up, or the SVC/XOT configuration is not correct. Solution Perform the following procedure to remove the fault: • Verify the physical connection status and protocol status of the interface are UP. •...

  • Page 386: Document Conventions And Icons

    Document conventions and icons Conventions This section describes the conventions used in the documentation. Port numbering in examples The port numbers in this document are for illustration only and might be unavailable on your device. Command conventions Convention Description Bold text represents commands and keywords that you enter literally as shown. Boldface Italic text represents arguments that you replace with actual values.

  • Page 387: Network Topology Icons

    Network topology icons Convention Description Represents a generic network device, such as a router, switch, or firewall. Represents a routing-capable device, such as a router or Layer 3 switch. Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that supports Layer 2 forwarding and other Layer 2 features.

  • Page 388: Support And Other Resources

    Support and other resources Accessing Hewlett Packard Enterprise Support • For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website: www.hpe.com/assistance • To access documentation and support services, go to the Hewlett Packard Enterprise Support Center website: www.hpe.com/support/hpesc Information to collect •...

  • Page 389: Websites

    For more information and device support details, go to the following website: www.hpe.com/info/insightremotesupport/docs Documentation feedback Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hpe.com). When submitting your feedback, include the document title,...
  • Page 390 part number, edition, and publication date located on the front cover of the document. For online help content, include the product name, product version, help edition, and publication date located on the legal notices page.

  • Page 391: Index

    Index assigning transmission priority to PVC, 196, CBR, checking PVC status to determine protocol state authentication configuration, of P2P subinterface, authentication configuration (LNS), class configuration, PPP traffic statistics collection, configuration task list, WAN PPP authentication, configuring, 188, WAN PPP CHAP authentication configuring PVC service mapping, configuration, configuring PVCs and the maximum number of...
  • Page 392 WAN PPP authentication methods, transparent bridging configuration over X.25, auto bundle DCC L2TP tunnel configuration basic configuration, (LAC-auto-initiated), WAN DCC auto-dial circular dial string backup called number configuration, setting, WAN DCC auto-dial configuration, calling WAN C-DCC interface calls from a remote backing up end, WAN DCC circular dial string backup+Internet...
  • Page 393 DCC PPP callback configuration WAN DCC PPP callback client configuration (C-DCC), (C-DCC), DCC PPP callback configuration WAN DCC PPP callback client configuration (RS-DCC), (RS-DCC), DCC PPP callback server configuration, WAN DCC PPP callback server configuration (C-DCC), dialup interface link layer/network/routing protocols, WAN DCC PPP callback server configuration (RS-DCC),...
  • Page 394 connecting router to X.25 public packet IPoA, 201, network, IPoEoA, 202, DCC overlap receiving, ISDN, 58, DCC timers and buffer queue length, ISDN B channel management, deactivation protection for ISDN BRI, ISDN B channel selection mode, dial authentication for RS-DCC, ISDN BRI, dial string for dialer interface (RS-DCC), ISDN BRI leased line,...
  • Page 395 LNS to grant L2TP tunneling requests, transparent bridging, local reachable MAC or SAP address transparent bridging over ATM, (DLSw), transparent bridging over FR, maximum number of DLSw v2.0 explorer transparent bridging over HDLC, retries, transparent bridging over MP, modem management, 185, 185, transparent bridging over PPP, MPoFR, 120, transparent bridging over X.25,...
  • Page 396 WAN DCC ISDN caller ID callback client WAN PPP ACFC negotiation, (C-DCC), WAN PPP authentication, WAN DCC ISDN caller ID callback client WAN PPP CHAP authentication, (RS-DCC), WAN PPP CHAP one-way authentication, WAN DCC ISDN caller ID callback server WAN PPP DNS server IP address negotiation, (C-DCC), WAN PPP IP address negotiation, 11, WAN DCC ISDN caller ID callback server...
  • Page 397 data ISDN caller ID callback server configuration (C-DCC), L2TP data message type, ISDN caller ID callback server configuration data link connection identifier (RS-DCC), WAN frame relay, ISDN configuration, Data Link Switching. Use DLSw ISDN leased line configuration, maintaining, advanced functions configuration, MP configuration, approach, MP implementation,...
  • Page 398 WAN IPv4 PPPoE dialer interface transparent bridging configuration over PPP, configuration, transparent bridging configuration over X.25, WAN IPv6 PPPoE dialer interface WAN C-DCC configuration, configuration, WAN C-DCC interface calls from a remote WAN PPPoE dialer interface configuration, end, WAN PPPoE session configuration, WAN C-DCC interface calls from multiple remote DE bit ends,...
  • Page 399 WAN PPPoE DDR dialer interface configuring maximum number of DLSw v2.0 configuration, explorer retries, WAN PPPoE DDR session configuration, configuring switch support for LAN-to-LAN DLSw Ethernet redundancy, WAN PPPoE server configuration, 47, configuring VLAN support, WAN RS-DCC configuration, differences between DLSw v1.0 and DLSw Dial Control Center.
  • Page 400 TCP/IP header compression configuration L2TP encapsulation structure, (X.25), LAN-to-LAN DLSw configuration, WAN frame relay configuration, LAN-to-LAN DLSw Ethernet redundancy WAN frame relay interface types, configuration, X.25 closed user group configuration, LAPB and X.25 configuration, X.25 load sharing configuration, 329, SDLC-to-LAN DLSw Ethernet redundancy configuration, X.25 load sharing configuration for IP datagram transmission,...
  • Page 401 ATM, virtual circuit, Frame relay address mapping configuring bridging with FR sub-interface InARP, support, frame relay address mapping on DCE side. See see EtoFR configuration, also Configuring frame relay address mappings EtoFR translation mapping creation, frame relay compression PVC application of X.25 over FR configuration, configuration, 339, FRF.20,...
  • Page 402 transparent bridging configuration over X.25 load sharing configuration for IP datagram HDLC, transmission, hello interval IP addressing setting, WAN PPP ACCM negotiation, hidden mode WAN PPP ACFC negotiation, AVP data transfer configuration, WAN PPP DNS server IP address negotiation, High-Level Data Link Control. Use HDLC WAN PPP IP address negotiation, 11, WAN PPP negotiation parameters,...
  • Page 403 WAN DCC ISDN caller ID callback enabling tunnel flow control, configuration, encapsulation structure, WAN DCC ISDN caller ID callback features, configuration (C-DCC), hello interval setting, WAN DCC ISDN caller ID callback L2TP-based EAD configuration, configuration (RS-DCC), LAC configuration, WAN DCC ISDN caller ID callback server LAC tunnel request initiation, configuration (C-DCC), LNS configuration,...
  • Page 404 disconnection, LCP renegotiation hello interval setting, AAA authentication configuration (LNS), L2TP tunnel establishment configuring, configuration, L2TP tunneling mode link client-initiated, bridging configuration, LAC-auto-initiated, bridging configuration over dialer interface, NAS-initiated, configuring bridging with FR sub-interface support, configuring DLSw for SDLC-to-LAN remote media configuring AVP data transfer in hidden translation, mode,...
  • Page 405 WAN PPP CHAP authentication one-way LAPB, configuration, WAN PPP configuration, 4, multilink frame relay, WAN PPP establishment process, PPP, WAN PPP PAP authentication one-way PPPoE, configuration, PPPoFR, WAN PPP PAP authentication two-way X.25, configuration, managing WAN PPPoE configuration, ISDN B channel management, WAN SLIP configuration, 1, 1, 1, 1, 2, ISDN B channel selection mode, LMI protocol...
  • Page 406 MPoFR L2TP LAC tunnel request initiation, configuration, 120, L2TP LNS configuration, MS-CHAP L2TP LNS LCP renegotiation, L2TP tunnel establishment process, L2TP LNS mandatory CHAP authentication, multilink L2TP LNS user authentication, WAN frame relay configuration, L2TP LNS VT interface creation, Multilink frame relay. See see also Use MFR L2TP tunnel authentication, multilink frame relay WAN C-DCC configuration,...
  • Page 407 configuring switch support for LAN-to-LAN WAN DCC RS-DCC configuration, DLSw Ethernet redundancy, WAN DCC RS-DCC with MP configuration, DLSw configuration, 221, WAN frame relay compression configuration, EtoFR configuration, WAN frame relay configuration, 85, EtoPPP and EtoFR configuration, WAN frame relay LAN configuration, 103, EtoPPP configuration, WAN frame relay LAN configuration (IPv4), frame relay compression configuration,...
  • Page 408 EtoPPP and EtoFR configuration, path EtoPPP configuration, WAN frame relay virtual circuit, HDLC basic configuration, peer HDLC configuration, 216, WAN PPP authentication, HDLC IP unnumbered interface WAN PPP CHAP authentication configuration, configuration, WAN PPP MS-CHAP or MS-CHAP-V2 LAN-to-LAN DLSw configuration, authentication configuration, LAN-to-LAN DLSw Ethernet redundancy WAN PPP PAP authentication configuration,...
  • Page 409 maintaining, Internet access using an ADSL interface, MP binding mode configuration, IPv4 DDR dialer interface configuration, MS-CHAP or MS-CHAP-V2 authentication IPv6 DDR dialer interface configuration, configuration, maintaining, negotiation parameter configuration, network structure, PAP authentication configuration, PPPoEoA, PAP authentication one-way configuration, PPPoEoA client configuration, PAP authentication two-way configuration, PPPoEoA configuration,...
  • Page 410 configuring bridge table entries, configuring ISDN Layer 3 negotiation parameter, configuring DCC overlap receiving, configuring ISDN leased line, configuring DCC timers and buffer queue length, configuring ISDN NI protocol SPID, configuring deactivation protection for ISDN configuring ISDN PRI, BRI, configuring ISDN PRI sliding window size, configuring dial string the dialer interface configuring ISDN progress-to-alerting (RS-DCC),...
  • Page 411 configuring permitted calling number for configuring WAN DCC, incoming calls, configuring WAN DCC auto-dial, configuring PPP IPHC, configuring WAN DCC auto-dial circular dial string configuring PPP link efficiency backup, mechanisms, configuring WAN DCC basics, configuring PPPoA, 202, configuring WAN DCC C-DCC, configuring PPPoEoA, configuring WAN DCC C-DCC interfaces (multiple) configuring PPPoEoA client,...
  • Page 412 configuring WAN DCC router-to-PC PPP configuring WAN PPP PAP two-way callback, 166, authentication, configuring WAN DCC router-to-router ISDN configuring WAN PPP PFC negotiation, caller ID callback, configuring WAN PPP polling interval, configuring WAN DCC router-to-router PPP configuring WAN PPPoE client, 48, callback, configuring WAN PPPoE DDR dialer interface, configuring WAN DCC RS-DCC, 135,...
  • Page 413 displaying PPP, setting delay waiting for response to Invite Clear message, displaying PPPoE, setting DLSw timer, displaying PPPoFR, setting hello interval, displaying X.25, setting ISDN protocol, enabling DLSw forwarding on SDLC interface, setting maximum number of SVCs associated with one address mapping, enabling frame relay trap, setting maximum SVC idle interval, enabling HDLC encapsulation,...
  • Page 414 OAM F5 loopback, WAN DCC router-to-router ISDN caller ID callback, PPPoA configuration, 202, WAN DCC router-to-router PPP callback, PPPoEoA, routing PPPoEoA client configuration, basic bridging functionalities, PPPoEoA configuration, bridge routing configuration, 291, PPPoEoA server configuration, L2TP basic configuration, PVC application of X.25 over FR configuration, 339, L2TP configuration, 253, 258, PVC application of XOT configuration,...
  • Page 415 DCC PPP callback server configuration, connecting router to X.25 public packet network, dial authentication configuration, one address mapping configuration (X.25), dial string configuration for dialer interface, two address mappings configuration (X.25), dialup interface link layer/network/routing virtual circuit range configuration (X.25), protocols, Serial Line Internet Protocol.
  • Page 416 SVC application of X.25 over FR WAN DCC router-to-router ISDN caller ID configuration, 338, callback, SVC application of XOT configuration, WAN DCC router-to-router PPP callback, WAN frame relay virtual circuit, WAN DCC RS-DCC configuration, 135, XOT configuration, 334, WAN DCC RS-DCC with MP configuration, XOT optional attributes configuration, WAN RS-DCC configuration, switched connection...
  • Page 417 UBR. See unspecified bit rate applying ACL in DLSw, assigning physical interfaces to dialer bundle (RS-DCC), ISDN configuration, 58, associating DCC dial ACL with dialup interface, virtual basic parameter configuration, access. See VA basic X.25 switching configuration, private dialup network. Use VPDN bridge functionality, template.
  • Page 418 DCC dynamic route frame relay compression configuration, 107, backup, 147, 175, 177, 179, frame relay configuration, 85, DCC dynamic route backup group, frame relay DCE side configuration, DCC dynamic route backup interface, frame relay DTE side configuration, DCC dynamic route backup link disconnect frame relay LAN configuration, 103, delay, frame relay LAN configuration (IPv4),...
  • Page 419 PPP PAP authentication two-way two address mappings configuration (X.25), configuration, virtual circuit range configuration (X.25), PPP polling interval configuration, VJ TCP header compression configuration, PPPoE client configuration, X.25 closed user group configuration, PPPoE configuration, X.25 configuration, PPPoE server configuration, 47, X.25 datagram transmission basic property configuration for synchronous serial configuration,...
  • Page 420 placing PAD call for remote login, PVC application of X.25 over FR configuration, 339, PVC application of XOT configuration, restricting the use of address mapping, setting delay waiting for response to Invite Clear message, setting maximum number of SVCs associated with one address mapping, setting maximum SVC idle interval, setting packet acknowledgement...

Table of Contents