Page 1: Configuration Guide
HPE FlexNetwork MSR Router Series Comware 7 Layer 2 - WAN Access Configuration Guide Part number: 5200-2394 Software version: MSR-CMW710-R0411 Document version: 6W101-20161114...
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 PPP and MP ···································································1 PPP overview ······························································································································ 1 PPP link establishment process ······························································································· 1 PPP authentication ················································································································ 2 PPP for IPv4 ························································································································ 2 PPP for IPv6 ························································································································ 3 MP overview ······························································································································· 4 Compatibility information ··············································································································· 4 Feature and hardware compatibility ·························································································· 4 Command and hardware compatibility ·······················································································...
Page 4 PPPoE server RADIUS-based IP address assignment configuration example ································· 57 PPPoE client in permanent mode configuration example ···························································· 60 PPPoE client in on-demand mode configuration example ···························································· 61 PPPoE client in diagnostic mode configuration example ····························································· 62 Configuration example for connecting a LAN to the Internet through an ADSL modem ····················· 63 Configuring L2TP ···········································································...
Page 5 Load balancing modes ········································································································· 98 Compatibility information ············································································································· 98 Feature and hardware compatibility ························································································ 98 Command and hardware compatibility ····················································································· 98 Configuring an HDLC link bundle interface ······················································································ 99 Configuration restrictions and guidelines ·················································································· 99 Configuration procedure ······································································································· 99 Assigning an interface to an HDLC link bundle··············································································· 100 Configuration restrictions and guidelines ················································································...
Page 6 Configuring the ATM service type ································································································ 129 Configuring applications carried by ATM ······················································································· 130 Configuring a VE interface ·································································································· 131 Configuring IPoA ··············································································································· 132 Configuring IPoEoA ··········································································································· 133 Configuring PPPoA ············································································································ 134 Configuring PPPoEoA ········································································································ 134 Configuring VP policing ············································································································· 135 Re-marking the CLP flag value of ATM cells ··················································································...
Page 7 Troubleshooting 3G and 4G modem management ········································································· 163 3G/4G modem failure················································································································ 163 Configuring DDR ·········································································· 165 Overview ································································································································ 165 Interfaces in DDR ·············································································································· 165 DDR implementations ········································································································ 165 DDR types ······················································································································· 167 Command and hardware compatibility·························································································· 167 DDR configuration task lists ······································································································· 168 Packet-triggered DDR configuration task list ···········································································...
Page 8 Configuring Frame Relay ······························································· 221 Overview ································································································································ 221 Frame Relay interface types ································································································ 221 Virtual circuit ···················································································································· 222 DLCI ······························································································································· 222 Frame Relay address mapping ···························································································· 223 LMI protocol ····················································································································· 223 Application scenarios ········································································································· 225 Feature and hardware compatibility ····························································································· 225 Frame Relay configuration task list ······························································································...
Page 9 Remote support ················································································································ 246 Documentation feedback ···································································································· 246 Index ························································································· 248...
Page 10: Configuring Ppp And
Configuring PPP and MP PPP overview Point-to-Point Protocol (PPP) is a point-to-point link layer protocol. It provides user authentication, supports synchronous/asynchronous communication, and allows for easy extension. PPP includes the following protocols: • Link control protocol (LCP)—Establishes, tears down, and monitors data links. •...
Page 11: Ppp Authentication
If the NCP negotiation succeeds, the link goes up and becomes ready to carry negotiated  network-layer protocol packets. If the NCP negotiation fails, NCP reports a Down event and enters the Link Termination  phase. If the interface is configured with an IP address, the IPCP negotiation is performed. IPCP configuration options include IP addresses and DNS server IP addresses.
Page 12: Ppp For Ipv6
An interface can act as a client or a server during IP address negotiation: • Client—Obtains an IP address from the server. Use the client mode when the device accesses the Internet through an ISP. • Server—Assigns an IP address to the client. Before you configure the IP address of the server, you must perform one of the following tasks: Configure a local address pool and associate the pool with the ISP domain.
Page 13: Mp Overview
• When the host connects to the device directly or through a bridge device, the device can use method 1 or method 2. • When the host accesses the device through a router, the device can use method 3 to assign an IPv6 prefix to the router.
Page 14: Configuring Ppp
• MSR2003. • MSR2004-24/2004-48. • MSR3012/3024/3044/3064. • MSR954(JH296A/JH297A/JH298A/JH299A/JH373A). • MSR958(JH300A/JH301A). Commands and descriptions for distributed devices apply to MSR4060 and MSR4080 routers. Configuring PPP PPP configuration task list Tasks at a glance (Required.) Enabling PPP encapsulation on an interface (Optional.) Configuring PPP authentication (Optional.) Configuring the polling feature...
Page 15 Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Configure the authenticator ppp authentication-mode pap By default, PPP authentication is to authenticate the peer by [ [ call-in ] domain isp-name ] disabled. using PAP. For local AAA authentication, the username and password of the peer must be configured on the authenticator.
Page 16 Step Command Remarks configure for the authenticator on the peer. For local AAA authentication, the username and password of the peer must be configured on the The username configured for the authenticator. peer must be the same as that For remote AAA authentication, configured on the peer.
Page 17 Step Command Remarks username and password of the for the authenticator and peer must be the same. peer must be configured on the remote AAA server. For more information about AAA authentication, Security Configuration Guide. To configure the peer: Step Command Remarks Enter system view.
Page 18: Configuring The Polling Feature
Step Command Remarks configured on the peer. For remote AAA authentication, the username and password of the peer must be configured on the remote AAA server. For more information about AAA authentication, Security Configuration Guide. To configure MS-CHAP or MS-CHAP-V2 authentication when no authenticator name is configured: Step Command Remarks...
Page 19: Configuring Ppp Negotiation
Step Command Remarks Set the keepalive interval. timer-hold seconds The default setting is 10 seconds. Set the keepalive retry limit. timer-hold retry retries The default setting is 5. Configuring PPP negotiation PPP negotiation includes the following parameters: • Negotiation timeout time. •...
Page 20 Step Command Remarks about the ip address command, Layer 3—IP Services Command Reference. Configure the server to assign an IP address to a client by using the following methods: • Method 1: Specify an IP address for the client on the server interface. •...
Page 21 Step Command Remarks By default, no IP address is configured on an interface. Configure an IP address for the This command is optional when ip address ip-address interface. the PPP address pool has been configured with gateway address. To configure the device as the server (Method 2: Specify a DHCP address pool): Step Command Remarks...
Page 22 Step Command Remarks the configured PPP address pool-name pool is associated. pool for address assignment. For more information about this command, Security Command Reference. Return to system view. quit interface interface-type Enter interface view. interface-number By default, no IP address is configured on an interface.
Page 23 Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number default, this feature Enable IP segment match. ppp ipcp remote-address match disabled. Configuring DNS server IP address negotiation Configure DNS server settings depending on the role of your device in PPP negotiation. •...
Page 24 Configuring ACCM negotiation PPP uses the escape mechanism on asynchronous links to avoid treating payload characters as control characters. The escape mechanism converts all one-byte asynchronous control characters into two-byte characters. This mechanism increases the size of asynchronous control characters and reduces the payload size.
Page 25 To configure the local end to reject ACFC requests received from the peer: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number By default, the local end accepts Configure the local end to the ACFC requests from the reject ACFC requests...
Page 26: Enabling Ip Header Compression
The nonstandard option must be Enable IP header compression. enable [ nonstandard ] specified when device communicates with a non-HPE device. Set the maximum number of connections for which an interface compression iphc The default setting is 16. perform...
Page 27: Enabling Ppp Link Quality Monitoring
Step Command Remarks compression. Enabling PPP link quality monitoring PPP link quality monitoring (LQM) monitors the quality (packet loss ratio and packet error ratio) of PPP links (including those in MP bundles) in real time. If PPP LQM is not enabled, each end of a PPP link periodically sends keepalives to its peer. If PPP LQM is enabled, Link Quality Reports (LQRs) packets replace keepalives to monitor the link.
Page 28: Configuring The Nas-Port-Type Attribute
Configuring the nas-port-type attribute The nas-port-type attribute is used for RADIUS authentication and accounting. For information about the nas-port-type attribute, see RFC 2865. To configure the nas-port-type attribute: Step Command Remarks Enter system view. system-view interface virtual-template Enter VT interface view. number nas-port-type { 802.11 | adsl-cap | adsl-dmt | async | cable |...
Page 29: Mp Configuration Task List
both—Binds links by using both the authentication username and descriptor.  • MP-group interfaces—MP-group interfaces are intended only for MP. On an MP-group interface, only one bundle is allowed, and links cannot be bundled according to the peer descriptor. Compared with VT interfaces, the configuration of MP-group interfaces is more efficient and easier to configure and understand.
Page 30 Step Command Remarks Interface. The default setting is 10 Set the keepalive interval. timer-hold seconds seconds. Set the keepalive retry limit. timer-hold retry retries The default setting is 5. Set the MTU size of the The default setting is 1500 mtu size interface.
Page 31: Configuring Mp Through An Mp-Group Interface
Step Command Remarks f. Enable MP for the interface: ppp mp g. Configure authentication (see "Configuring authentication.") 13. Configure other "Configuring other optional parameters. parameters." Configuring other optional parameters Step Command Remarks Enter system view. system-view more information about Enter MP VT interface or interface dialer configuring MP parameters in...
Page 32 Step Command Remarks Create MP-group If the MP-group interface already interface mp-group mp-number interface and enter its view. exists, you enter its view directly. The default setting is 16. For this command to take effect on an MP bundle, you must (Optional.) Set the maximum re-enable physical...
Page 33: 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 34: Configuring Lfi
Configuring LFI Real-time packets, such as Telnet and VoIP packets, might be blocked or delayed on a low-speed interface. To reduce delays and jitters on low-speed links, LFI fragments large packets into small fragments. The fragments are reassembled at the destination. Figure 2 illustrates the LFI process.
Page 35: Ppp And Mp Configuration Examples
Task Command display ppp access-user { interface interface-type interface-number [ count ] | ip-address ip-address | Display information about PPP access users. ipv6-address ipv6-address | username user-name | user-type { lac | lns | pppoa | pppoe } [ count ] } display ip pool [ pool-name ] [ group group-name ] Display PPP address pools.
Page 36 # Set the service type of the user account to PPP. [RouterA-luser-network-userb] service-type ppp [RouterA-luser-network-userb] quit # Enable PPP encapsulation on Serial 2/1/0. By default, an interface uses PPP encapsulation. [RouterA] interface serial 2/1/0 [RouterA-Serial2/1/0] link-protocol ppp # Set the authentication mode to PAP. [RouterA-Serial2/1/0] ppp authentication-mode pap domain system # Assign an IP address to Serial 2/1/0.
Page 37: Two-Way Pap Authentication Configuration Example
56 bytes from 200.1.1.1: icmp_seq=3 ttl=128 time=1.738 ms 56 bytes from 200.1.1.1: icmp_seq=4 ttl=128 time=1.744 ms --- Ping statistics for 200.1.1.1 --- 5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss round-trip min/avg/max/std-dev = 1.738/2.402/3.197/0.576 ms Two-way PAP authentication configuration example Network requirements As shown in Figure...
Page 38 # Set the service type of the user account to PPP. [RouterB-luser-network-usera] service-type ppp [RouterB-luser-network-usera] quit # Enable PPP encapsulation on Serial 2/1/0. By default, an interface uses PPP encapsulation. [RouterB] interface serial 2/1/0 [RouterB-Serial2/1/0] link-protocol ppp # Set the authentication mode to PAP. [RouterB-Serial2/1/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 39: One-Way Chap Authentication Configuration Example
One-way CHAP authentication configuration example Network requirements As shown in Figure 5, configure Router A to authenticate Router B by using CHAP. Figure 5 Network diagram Ser2/1/0 Ser2/1/0 200.1.1.1/16 200.1.1.2/16 Router A Router B Configuration procedure (Method 1) The authenticator configured with a username authenticates the peer by using CHAP.
Page 40 # Configure the username for Router B when Router B is authenticated. [RouterB-Serial2/1/0] ppp chap user userb # Assign an IP address to Serial 2/1/0 of Router B. [RouterB-Serial2/1/0] ip address 200.1.1.2 16 (Method 2) The authenticator with no username configured authenticates the peer by using CHAP.
Page 41: Ip Address Negotiation Configuration Examples
The output shows that: The physical layer status and link layer status of the interface are both up.  The states of LCP and IPCP are both Opened, indicating that PPP negotiation has  succeeded. # Verify that Router A and Router B can ping each other. [RouterB-Serial2/1/0] ping 200.1.1.1 Ping 200.1.1.1 (200.1.1.1): 56 data bytes, press CTRL_C to break 56 bytes from 200.1.1.1: icmp_seq=0 ttl=128 time=3.197 ms...
Page 42 Interface Link Protocol Main IP Description S2/1/0 200.1.1.10 The output shows Serial 2/1/0 obtains IP address 200.1.1.10 through PPP negotiation. # Verify that Router B can ping Serial 2/1/0 of Router A. [RouterB-Serial2/1/0] ping 200.1.1.1 Ping 200.1.1.1 (200.1.1.1): 56 data bytes, press CTRL_C to break 56 bytes from 200.1.1.1: icmp_seq=0 ttl=128 time=3.197 ms 56 bytes from 200.1.1.1: icmp_seq=1 ttl=128 time=2.594 ms 56 bytes from 200.1.1.1: icmp_seq=2 ttl=128 time=2.739 ms...
Page 43 Protocol: (s) - spoofing Interface Link Protocol Main IP Description S2/1/0 200.1.1.10 The output shows that Serial 2/1/0 has obtained IP address 200.1.1.10 through PPP negotiation. # Verify that Router B can ping Serial 2/1/0 of Router A. [RouterB-Serial2/0] ping 200.1.1.1 Ping 200.1.1.1 (200.1.1.1): 56 data bytes, press CTRL_C to break 56 bytes from 200.1.1.1: icmp_seq=0 ttl=128 time=3.197 ms 56 bytes from 200.1.1.1: icmp_seq=1 ttl=128 time=2.594 ms...
Page 44 [RouterA-luser-network-userb] password simple 123 # Set the service type to PPP for the local user. [RouterA-luser-network-userb] service-type ppp [RouterA-luser-network-userb] quit # Create ISP domain bbb and associate aaa with bbb. [RouterA] domain bbb [RouterA-isp-bbb] authorization-attribute ip-pool aaa [RouterA-isp-bbb] quit # Configure Serial 2/1/0 to authenticate the peer interface in bbb by using PAP. [RouterA] interface serial 2/1/0 [RouterA-Serial2/1/0] ppp authentication-mode pap domain bbb # Configure an IP address for Serial 2/1/0.
Page 45: Mp Binding Mode Configuration Examples
Pool name Start IP address End IP address Free In use 200.1.1.10 200.1.1.20 In use IP addresses: IP address Interface 200.1.1.10 S2/1/0 The output shows that one IP address of aaa has been assigned. MP binding mode configuration examples Network requirements As shown in Figure 9, to enable MP for Serial 2/1/0 and Serial 2/1/1, use one of the following...
Page 46 # Display MP information on Router A. [RouterA] display ppp mp Template: Virtual-Template1 max-bind: 16, fragment: enabled, min-fragment: 128 Master link: Virtual-Access0, Active members: 2, Bundle HPE Peer's endPoint descriptor: HPE Sequence format: long (rcv)/long (sent) Bundle Up Time: 2013/01/10...
Page 47 56 bytes from 8.1.1.1: icmp_seq=2 ttl=255 time=0.000 ms 56 bytes from 8.1.1.1: icmp_seq=3 ttl=255 time=0.000 ms 56 bytes from 8.1.1.1: icmp_seq=4 ttl=255 time=1.000 ms --- Ping statistics for 8.1.1.1 --- 5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss round-trip min/avg/max/std-dev = 0.000/1.000/4.000/1.549 ms (Method 2) Associating remote usernames with a VT interface Configure Router A: # Configure the usernames, and passwords of remote users.
Page 48 [RouterA] display ppp mp Template: Virtual-Template1 max-bind: 16, fragment: enabled, min-fragment: 128 Master link: Virtual-Access0, Active members: 1, Bundle usera Peer's endPoint descriptor: HPE Sequence format: long (rcv)/long (sent) Bundle Up Time: 2013/01/10 08:02:34:881 0 lost fragments, 0 reordered, 0 unassigned, 0 interleaved...
Page 49 [RouterB] display ppp mp Template: Virtual-Template1 max-bind: 16, fragment: enabled, min-fragment: 128 Master link: Virtual-Access2, Active members: 1, Bundle userc Peer's endPoint descriptor: HPE Sequence format: long (rcv)/long (sent) Bundle Up Time: 2013/01/10 12:31:13:391 0 lost fragments, 0 reordered, 0 unassigned, 0 interleaved...
Page 50 Hold timer: 10 seconds, retry times: 5 Internet Address is 8.1.1.2/24 Primary Link layer protocol: PPP LCP: opened, MP: opened, IPCP: opened Physical: MP, baudrate: 64000 bps Main interface: Virtual-Template1 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 rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec Last 300 seconds output rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec...
Page 51 # Create an MP-group interface, and configure an IP address for it. [RouterB] interface mp-group 2/0/0 [RouterB-Mp-group2/0/0] ip address 1.1.1.2 24 [RouterB-Mp-group2/0/0] quit # Configure interface Serial 2/1/1. [RouterB] interface serial 2/1/1 [RouterB-Serial2/1/1] link-protocol ppp [RouterB-Serial2/1/1] ppp mp mp-group 2/0/0 [RouterB-Serial2/1/1] shutdown [RouterB-Serial2/1/1] undo shutdown [RouterB-Serial2/1/1] quit...
Page 52 Last link flapping: Never Last clearing of counters: Never Last 300 seconds input rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec Last 300 seconds output rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec Input: 2 packets, 80 bytes, 0 drops Output: 2 packets, 24 bytes, 0 drops # Ping Router B from Router A.
Page 53: Configuring Pppoe
Configuring PPPoE Overview Point-to-Point Protocol over Ethernet (PPPoE) extends PPP by transporting PPP frames encapsulated in Ethernet over point-to-point links. PPPoE specifies the methods for establishing PPPoE sessions and encapsulating PPP frames over Ethernet. PPPoE requires a point-to-point relationship between peers instead of a point-to-multipoint relationship as in multi-access environments such as Ethernet.
Page 54: Configuring The Pppoe Server
Figure 10 Network structure 1 DSLAM PPPoE server Carrier device Internet Router B Modem Client device Router A PPPoE client Host A Host B Host C • As shown in Figure 11, a PPPoE session is established between each host (PPPoE client) and the carrier router (PPPoE server).
Page 55: Setting The Maximum Number Of Pppoe Sessions
Step Command Remarks [ minimum value ] disabled. Return to system view. quit Enter Layer Ethernet interface/subinterface, Layer virtual Ethernet interface/subinterface, VLAN interface, Layer 3 aggregate interface interface-type interface/subinterface, interface-number VE-L3VPN interface/subinterface, EFM interface/subinterface view. Enable the PPPoE server on the interface and bind this pppoe-server bind...
Page 56: Limiting The Pppoe Access Rate
The maximum number of PPPoE sessions supported by a device varies by license or device model. The maximum number of PPPoE sessions set for a device cannot be greater than the maximum number of PPPoE sessions supported by the device. (Centralized devices in standalone mode.) The total maximum number of PPPoE sessions set for all cards or IRF member devices cannot be greater than the maximum number of PPPoE sessions supported by the device.
Page 57: Configuring The Nas-Port-Id Attribute
configured threshold, the device discards the excessive requests, and outputs log messages. If the blocking time is set to 0, the device does not block any requests, and it only outputs log messages. The device uses a monitoring table and a blocking table to control PPP access rates: •...
Page 58: Configuring A Va Pool
remote-id. The RADIUS server compares the received nas-port-id attribute with the local line ID information to verify the location of the user. You can configure the content of the nas-port-id attribute that the PPPoE server sends to the RADIUS server. To configure the nas-port-id attribute: Step Command...
Page 59: Clearing Pppoe Sessions
• The regional VA pool contains VA interfaces for interfaces that do not span multiple devices, such as Ethernet interfaces. When you configure a VA pool, follow these guidelines: • To change the capacity of a VA pool, you must delete the previous configuration, and reconfigure the VA pool.
Page 60: Configuring A Dialer Interface
• Diagnostic mode—A PPPoE session is established immediately after the device configurations finish. The device automatically terminates the PPPoE session and then tries to re-establish a PPPoE session at a pre-configured interval. By establishing and terminating PPPoE sessions periodically, you can monitor the operating status of the PPPoE link. The PPPoE session operating mode is determined by your configuration on the dialer interface: •...
Page 61: Configuring A Pppoe Session
Step Command Remarks seconds. In permanent or diagnostic mode, starts auto-dial timer after the link is disconnected and originates a new call when the auto-dial timer expires. As a best practice, set a shorter auto-dial interval for DDR to soon originate a new call.
Page 62: Displaying And Maintaining Pppoe
Step Command Remarks reset pppoe-client Reset a PPPoE session. Available in user view. dial-bundle-number number } Displaying and maintaining PPPoE Displaying and maintaining PPPoE server Execute display commands in any view. Task Command Display summary information for PPPoE display pppoe-server session summary [ interface sessions (centralized devices in standalone interface-type interface-number ] mode).
Page 63: Pppoe Configuration Examples
Task Command Clear the protocol packet statistics for a PPPoE reset pppoe-client session packet session. [ dial-bundle-number number ] PPPoE configuration examples PPPoE server configuration example Network requirements As shown in Figure 12, Host A and Host B run PPPoE client dialup software. The PPPoE server on the router performs local authentication and assigns IP addresses to the clients.
Page 64: Pppoe Server Ip Address Assignment Through The Local Dhcp Server Configuration Example
[Router] domain system [Router-isp-system] authentication ppp local [Router-isp-system] quit Verifying the configuration # Verify that Host A and Host B can access the Internet by using username user1 and password pass1. (Details not shown.) PPPoE server IP address assignment through the local DHCP server configuration example Network requirements As shown in...
Page 65: Pppoe Server Ip Address Assignment Through A Remote Dhcp Server Configuration Example
# Display information about IP addresses assigned by the DHCP server. [Router] display dhcp server ip-in-use IP address Client identifier/ Lease expiration Type Hardware address 1.1.1.2 3030-3030-2e30-3030- Unlimited Auto(C) 662e-3030-3033-2d45- 7468-6572-6e65-74 The output shows that the router has assigned an IP address to the host. PPPoE server IP address assignment through a remote DHCP server configuration example Network requirements...
Page 66: Pppoe Server Radius-Based Ip Address Assignment Configuration Example
# Specify an IP address for GigabitEthernet 1/0/2. [RouterA] interface gigabitethernet 1/0/2 [RouterA-GigabitEthernet1/0/2] ip address 10.1.1.2 24 [RouterA-GigabitEthernet1/0/2] quit # Create a PPPoE user. [RouterA] local-user user1 class network [RouterA-luser-network-user1] password simple pass1 [RouterA-luser-network-user1] service-type ppp [RouterA-luser-network-user1] quit Configure Router B as a DHCP server: # Enable DHCP.
Page 67 Auth-Type == CHAP,User-Password := pass1 Service-Type = Framed-User, Framed-Protocol = PPP, Framed-IPv6-Pool = "pool1", HPE-VPN-Instance = "vpn1", Configure Router A: a. Configure the PPPoE server: # Configure Virtual-Template 1 to use CHAP for authentication and use ISP domain dm1 as the authentication domain.
Page 68 [RouterA-Virtual-Template1] ppp authentication-mode chap domain dm1 [RouterA-Virtual-Template1] quit # Create a PPP address pool that contains nine assignable IP addresses. [RouterA] ip pool pool1 1.1.1.2 1.1.1.10 group 1 # Specify gateway address 1.1.1.1 and VPN instance vpn1 for pool1. [RouterA] ip pool pool1 gateway 1.1.1.1 vpn-instance vpn1 # Configure a PPP address pool route for pool1.
Page 69: Pppoe Client In Permanent Mode Configuration Example
PPPoE client in permanent mode configuration example Network requirements As shown in Figure 16, Router A serves as a PPPoE server. Configure Router B as a PPPoE client operating in permanent mode. Figure 16 Network diagram PPPoE Server PPPoE Client GE1/0/1 GE1/0/1 Router A...
Page 70: Pppoe Client In On-Demand Mode Configuration Example
[RouterB-Dialer1] quit # Configure a static route. [RouterB] ip route-static 1.1.1.1 255.0.0.0 dialer 1 Verifying the configuration # Display summary information about the PPPoE session established between Router B and Router A (PPPoE server). [RouterB-Dialer1] display pppoe-client session summary Bundle ID Interface RemoteMAC LocalMAC...
Page 71: Pppoe Client In Diagnostic Mode Configuration Example
# Configure a PPPoE session that corresponds to dialer bundle 1 (dialer bundle 1 corresponds to Dialer 1). [RouterB] interface gigabitethernet 1/0/1 [RouterB-GigabitEthernet1/0/1] pppoe-client dial-bundle-number 1 [RouterB-GigabitEthernet1/0/1] quit # Configure a static route. [RouterB] ip route-static 1.1.1.1 255.0.0.0 dialer 1 # Set the link-idle timeout timer to 150 seconds.
Page 72: Configuration Example For Connecting A Lan To The Internet Through An Adsl Modem
[RouterB] interface dialer 1 [RouterB-Dialer1] dialer bundle enable # Associate Dialer 1 with dialer access group 1. [RouterB-Dialer1] dialer-group 1 [RouterB-Dialer1] quit # Configure Dialer 1 to obtain an IP address through PPP negotiation. [RouterB-Dialer1] ip address ppp-negotiate # Configure a PPPoE session that corresponds to dialer bundle 1 (dialer bundle 1 corresponds to Dialer 1).
Page 73 Figure 19 Network diagram RADIUS Server 11.110.91.146 DSLAM Router B ATM2/4/0 Internet PPPoE Server Modem GE1/0/1 Router A PPPoE Client GE1/0/2 192.168.1.1/24 Host A Host B Host C Configuration procedure Configure Router A as a PPPoE client: # Create dialer access group 1 and configure a dial access control rule for it. <RouterA>...
Page 74 [RouterA] ip route-static 0.0.0.0 0 dialer 1 If the hosts in the LAN use private addresses, configure NAT on Router A. For more information about NAT, see Layer 3—IP Services Configuration Guide. Configure Router B as the PPPoE server: # Configure Virtual-Template 1 to use PAP for authentication and use a PPP address pool to assign IP addresses.
Page 75 [RouterA] display pppoe-client session summary Bundle ID Interface RemoteMAC LocalMAC State GE1/0/1 0001-0000-0001 00e0-1500-4100 SESSION Host A, Host B, and Host C can thus access the Internet. For example, they can browse a web page through IE.
Page 76: Configuring L2Tp
Configuring L2TP Overview The Layer 2 Tunneling Protocol (L2TP) is a Virtual Private Dialup Network (VPDN) tunneling protocol. L2TP sets up point-to-point tunnels across a public network (for example, the Internet) and transmits encapsulated PPP frames (L2TP packets) over the tunnels. With L2TP, remote users can access the private networks through L2TP tunnels after connecting to a public network by using PPP.
Page 77: L2Tp Tunnel And Session
• Control messages—Used to establish, maintain, and delete L2TP tunnels and sessions. Control messages are transmitted over a reliable control channel, which supports flow control and congestion control. • Data messages—Used to encapsulate PPP frames, as shown in Figure 21. Data messages are transmitted over an unreliable data channel and are not retransmitted when packet loss occurs.
Page 78 • The remote system only needs to support PPP, and it does not need to support L2TP. • Authentication and accounting of the remote system can be implemented on the LAC or LNS. Figure 24 NAS-initiated tunnel establishment process Remote system RADIUS server A RADIUS server B Host A...
Page 79 In steps 12 and 13, the LAC forwards packets for the remote system and LNS. Host A and LAC exchange PPP frames, and the LAC and LNS exchange L2TP packets. Client-initiated tunneling mode As shown in Figure 25, a remote system running L2TP (LAC client) has a public IP address to communicate with the LNS through the Internet.
Page 80: L2Tp Features
Figure 27 LAC-auto-initiated tunneling mode LAC auto initiated L2TP tunnel Private Internet network Remote system Device A Device B Host A RADIUS server An LAC-auto-initiated tunnel has the following characteristics: • The connection between a remote system and the LAC is not confined to a dial-up connection and can be any IP-based connection.
Page 81 • Private address allocation—An LNS can dynamically allocate private addresses to remote users. This facilitates address allocation for private internets (RFC 1918) and improves security. • Flexible accounting—Accounting can be simultaneously performed on the LAC and LNS. This allows bills to be generated on the ISP side and charging and auditing to be processed on the enterprise gateway.
Page 82: Protocols And Standards
L2TP tunnel sharing—Different users can share the same L2TP tunnel between the LAC  and the LTS. The LTS distributes data of different users to different LNSs. Figure 29 L2TP tunnel switching network diagram Private PPPoE/ISDN network Remote user Internet Internet Private PPPoE/ISDN...
Page 83: Configuring Basic L2Tp Capabilities
Tasks at a glance Remarks Configuring an LAC: • (Required.) Configuring an LAC to initiate tunneling requests for a The first and fifth tasks are user required for NAS-initiated mode • (Required.) Specifying LNS IP addresses unnecessary • LAC-auto-initiated mode. (Optional) Configuring the source IP address of L2TP tunnel packets...
Page 84: Configuring An Lac
• Configuring the local tunnel name—The local tunnel name identifies the tunnel at the local end during tunnel negotiation between an LAC and an LNS. To configure basic L2TP capabilities: Step Command Remarks Enter system view. system-view Enable L2TP. l2tp enable By default, L2TP is disabled.
Page 85: Configuring The Source Ip Address Of L2Tp Tunnel Packets
Step Command Remarks Enter system view. system-view Enter L2TP group view in l2tp-group group-number [ mode LAC mode. lac ] By default, no LNS IP addresses Specify LNS IP addresses. lns-ip { ip-address }&<1-5> are specified. Configuring the source IP address of L2TP tunnel packets As a best practice to ensure high availability, use the IP address of a loopback interface as the source IP address of L2TP tunnel packets on the LAC.
Page 86: Configuring An Lac To Automatically Establish An L2Tp Tunnel
• For local AAA authentication, create a local user and configure a password for each remote user on the LAC. The LAC then authenticates a remote user by matching the provided username and password with those configured locally. • For remote AAA authentication, configure the username and password of each user on the RADIUS/HWTACACS server.
Page 87: Configuring An Lns
Step Command Remarks Interface. Set the MTU size of the mtu size The default setting is 1500 bytes. interface. (Optional.) Set the keepalive timer-hold seconds The default setting is 10 seconds. interval. (Optional.) Set the keepalive timer-hold retry retries The default setting is 5. retry limit.
Page 88: Configuring A Va Pool
For information about configuring VT interfaces, see "Configuring PPP and MP" and Layer 3—IP Services Configuration Guide. Configuring a VA pool A VA pool contains a group of VA interfaces. You can configure a VA pool to improve the performance of establishing or terminating L2TP connections.
Page 89: Configuring User Authentication On An Lns
Step Command Remarks • If the L2TP group number allow l2tp default, denies virtual-template tunneling requests from any LAC. Configure the LNS to accept virtual-template-number tunneling requests from an If the L2TP group number is 1, the [ remote remote-name ] specify remote remote-name option is •...
Page 90: Configuring Aaa Authentication On An Lns
Step Command Remarks authentication. is not performed on an LNS. This command is effective only on NAS-initiated L2TP tunnels. Configuring LCP renegotiation To establish a NAS-initiated L2TP tunnel, a user first negotiates with the LAC at the start of a PPP session.
Page 91: Configuring Optional L2Tp Parameters
Step Command Remarks interface virtual-template By default, no VT interface is Enter VT interface view. virtual-template-number created. Enable the LNS to initiate By default, the LNS does not IMSI binding ppp lcp { imsi | sn } request initiate IMSI binding authentication requests.
Page 92: Setting The Hello Interval
To ensure tunnel security, enable tunnel authentication. For the tunnel authentication key change to take effect, change the tunnel authentication key before tunnel negotiation is performed. To configure L2TP tunnel authentication: Step Command Remarks Enter system view. system-view l2tp-group group-number [ mode Enter L2TP group view.
Page 93: Setting The Dscp Value Of L2Tp Packets
Setting the DSCP value of L2TP packets The DSCP field is the first 6 bits of the IP ToS byte. This field marks the priority of IP packets for forwarding. This feature sets the DSCP value for the IP packet when L2TP encapsulates a PPP frame into an IP packet.
Page 94: Displaying And Maintaining L2Tp
Step Command Remarks Enter system view. system-view Set the TSA ID of the LTS By default, the TSA ID of the LTS enable L2TP loop l2tp tsa-id tsa-id is not configured, and L2TP loop detection on the LTS. detection is disabled on the LTS. Displaying and maintaining L2TP Execute display commands in any view and reset commands in user view.
Page 95 [LAC-luser-network-vpdnuser] service-type ppp [LAC-luser-network-vpdnuser] quit # Configure local authentication for PPP users in ISP domain system. [LAC] domain system [LAC-isp-system] authentication ppp local [LAC-isp-system] quit # Configure CHAP authentication on Async 2/1/0. [LAC] interface async 2/1/0 [LAC-Async2/1/0] ppp authentication-mode chap [LAC-Async2/1/0] quit # Enable L2TP.
Page 96: Configuration Example For Client-Initiated L2Tp Tunnel
# Create L2TP group 1 in LNS mode. [LNS] l2tp-group 1 mode lns # Configure the local tunnel name as LNS. [LNS-l2tp1] tunnel name LNS # Specify Virtual-Template 1 for receiving calls from an LAC. [LNS-l2tp1] allow l2tp virtual-template 1 remote LAC # Enable tunnel authentication, and specify the tunnel authentication key as aabbcc.
Page 97 # Configure local authentication for PPP users in ISP domain system. [LNS] domain system [LNS-isp-system] authentication ppp local [LNS-isp-system] quit # Enable L2TP. [LNS] l2tp enable # Create a PPP address pool. [LNS] ip pool aaa 192.168.0.10 192.168.0.20 [LNS] ip pool aaa gateway 192.168.0.1 # Create Virtual-Template 1, specify its PPP authentication mode as CHAP, and use address pool aaa to assign IP addresses to the PPP users.
Page 98: Configuration Example For Lac-Auto-Initiated L2Tp Tunnel
Configuration example for LAC-auto-initiated L2TP tunnel Network requirements As shown in Figure 32, configure the LAC to establish an L2TP tunnel with the LNS in LAC-auto-initiated mode. When the PPP user initiates a connection, it uses the established tunnel to access the corporate network.
Page 99 # Configure a static route so that packets destined for the PPP user will be forwarded through the L2TP tunnel. [LNS] ip route-static 10.2.0.0 16 192.168.0.10 Configure the LAC: # Configure IP addresses for the interfaces. (Details not shown.) # Enable L2TP. <LAC>...
Page 100: Troubleshooting L2Tp
56 bytes from 10.2.0.1: icmp_seq=3 ttl=128 time=1.000 ms 56 bytes from 10.2.0.1: icmp_seq=4 ttl=128 time=1.000 ms --- Ping statistics for 10.2.0.1 --- 5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss round-trip min/avg/max/std-dev = 1.000/1.000/1.000/0.000 ms Troubleshooting L2TP Symptom 1: Failure to access the private network The remote system cannot access the private network.
Page 101: Configuring Hdlc
Configuring HDLC Overview High-level Data Link Control (HDLC) is a bit-oriented link layer protocol. HDLC can transmit any types of bit stream transparently. HDLC supports only point-to-point link and does not support point-to-multipoint link. HDLC supports neither IP address negotiation nor authentication. It uses keepalives to check link status.
Page 102: Enabling Hdlc Encapsulation On An Interface
Enabling HDLC encapsulation on an interface Step Command Remarks Enter system view. system-view Enter synchronous-mode interface interface-type serial interface view or POS interface-number interface view. Enable HDLC encapsulation PPP encapsulation is enabled by link-protocol hdlc on the interface. default. Configuring link status polling An HDLC-enabled interface can regularly check link status by sending keepalives to the peer at the keepalive interval at the link layer.
Page 103: Hdlc Configuration Example
Task Command display interface pos interface-number Clear the statistics and restart reset counters interface [ serial [ interface-number ] ] statistics collection reset counters interface [ pos [ interface-number ] ] interfaces. HDLC configuration example Network requirements As shown in Figure 33, Router A and Router B are connected by POS interfaces.
Page 104 56 bytes from 12.1.1.2: icmp_seq=1 ttl=254 time=2.051 ms 56 bytes from 12.1.1.2: icmp_seq=2 ttl=254 time=1.996 ms 56 bytes from 12.1.1.2: icmp_seq=3 ttl=254 time=1.963 ms 56 bytes from 12.1.1.2: icmp_seq=4 ttl=254 time=1.991 ms --- Ping statistics for 12.1.1.2 --- 5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss round-trip min/avg/max/std-dev = 1.963/2.028/2.137/0.062 ms The output shows that Router A can successfully ping Router B.
Page 105: Configuring Hdlc Link Bundling
Configuring HDLC link bundling Overview HDLC link bundling bundles multiple interfaces using HDLC encapsulation (also known as HDLC interfaces) together to form one logical link. HDLC link bundling delivers the following benefits: • Load balancing—Incoming/outgoing traffic is distributed across multiple HDLC link bundle member interfaces.
Page 106 Not Selected yet due to the following restrictions:  − The maximum number of Selected interfaces. − The minimum number of Selected interfaces required for bringing up the HDLC link bundle. − The minimum bandwidth required for bringing up the HDLC link bundle. •...
Page 107: Load Balancing Modes
Load balancing modes An HDLC link bundle forwards traffic through its Selected interfaces. When multiple Selected interfaces exist in an HDLC link bundle, the device chooses the Selected interfaces to forward traffic according to its load balancing mode. The following load balancing modes are available: •...
Page 108: Configuring An Hdlc Link Bundle Interface
Configuring an HDLC link bundle interface Configuration restrictions and guidelines When you configure an HDLC link bundle interface, follow these restrictions and guidelines: • The minimum number of Selected interfaces required cannot be greater than the maximum number of Selected interfaces allowed in the HDLC link bundle. •...
Page 109: Assigning An Interface To An Hdlc Link Bundle
Step Command Remarks bundle. (Optional.) Set the maximum default setting number Selected maximum number of Selected bundle max-active links number interfaces allowed in the interfaces supported, which varies HDLC link bundle. by device model. (Optional.) Set the minimum default, minimum bandwidth required bundle min-active bandwidth...
Page 110: Configuration Procedure
• You can assign interfaces on different cards to the same HDLC link bundle. • Changing the bundling priority of a member interface might cause the device to determine the state of each member interface. • The peer interface directly connected to a local HDLC link bundle member interface must also join the same HDLC link bundle.
Page 111: Hdlc Link Bundling Configuration Example
HDLC link bundling configuration example Network requirements As shown in Figure 34, to increase bandwidth and enhance connection reliability between Router A and Router B, create an HDLC link bundle. Figure 34 Network diagram Router A Router B HDLC-B1 1.1.1.1/24 Pos2/2/1 Pos2/2/1 Pos2/2/2...
Page 112: Verifying The Configuration
[RouterB-Pos2/2/1] quit # Assign POS interfaces POS 2/2/2 to HDLC link bundle 1. [RouterB] interface pos 2/2/2 [RouterB-Pos2/2/2] link-protocol hdlc [RouterB-Pos2/2/2] bundle id 1 [RouterB-Pos2/2/2] quit Verifying the configuration # Verify that the HDLC link bundle interfaces on Router A and Router B can ping each other. [RouterA] ping –a 1.1.1.1 1.1.1.2 Ping 1.1.1.2 (1.1.1.2) from 1.1.1.1: 56 data bytes, press CTRL_C to break 56 bytes from 1.1.1.2: icmp_seq=0 ttl=255 time=0.000 ms...
Page 113: Configuring Isdn
Configuring ISDN This feature is supported only on routers installed with BS, E1, or T1 interface modules. Overview Integrated Services Digital Network (ISDN) is a circuit-switched telephone network system that provides high-quality end-to-end digital connectivity at high rates over copper wire. ISDN transmits all information in the digital form.
Page 114: Isdn Protocol Stacks
ISDN protocol stacks ISDN provides dial-on-demand links. It sets up and maintains a link only when traffic is present. The B-channels and the D-channel use separate protocol stacks, as shown in Table Table 4 ISDN protocol stacks and OSI reference model OSI model ISDN layer D-channel...
Page 115: Isdn Pri Configuration Prerequisites
Figure 37 Voice ISDN application scenario IP network ISDN Router ISDN Router ISDN PRI configuration prerequisites Before you can use a CE1/PRI or CT1/PRI interface to provide ISDN PRI services, you must use the pri-set command to bundle timeslots into channel sets on the interface. For each PRI set, the system creates a serial interface automatically.
Page 116: Setting The Isdn Switch Type On An Isdn Interface
Tasks at a glance Remarks BRI interface (Optional.) Configuring a BRI interface to supply line  power (Required.) Configuring the sliding window size on an  ISDN BRI interface • interface: (Required.) Configuring the sliding window size on an ISDN PRI interface Setting the ISDN switch type on an ISDN interface ISDN service providers in different countries implement variants of ISDN to provide varied ISDN...
Page 117: Setting The Isdn Functionality Of An Isdn Interface
Step Command Remarks operating on the user side. Setting the ISDN functionality of an ISDN interface An ISDN interface can provide the ISDN user-side or network-side functionality. For two ISDN devices to communicate with each other, you must configure one end as the network side and configure the other end as the user side.
Page 118: Configuring The Tspid Timer And Information Retransmission
Configuring dynamic SPID negotiation You cannot perform this task when SPID negotiation is present on the ISDN BRI interface. To configure dynamic SPID negotiation on a BRI interface: Step Command Remarks Enter system view. system-view Enter ISDN interface bri interface-number interface view.
Page 119: Enabling Nit Mode For Ni-Type Switches Incapable Of Spid Negotiation
The TSPID timer sets the maximum interval that ISDN waits for a response after it sends an INFORMATION message. The timer starts when the device initiates a SPID negotiation or Layer 3 initialization. The interface retransmits the INFORMATION message if it has not received a response from the service provider switch before the TSPID timer expires.
Page 120 Step Command Remarks interfaces and 1 byte for the BRI interface. The call reference identifies a call registration or cancellation request on the local interface. By default: • After sending a CONNECT request, ISDN waits for a CONNECT before Configure the CONNECT isdn ignore connect-ack...
Page 121: Configuring Q.931 Call Control Parameters
Step Command Remarks number information is absent or incomplete in the outgoing SETUP message. 11. Configure ISDN to include By default, ISDN does not include the calling-name field in isdn carry calling-name the calling-name field in outgoing outgoing packets. packets. 12.
Page 122: Configuring Calling Number Verification For Incoming Calls
Step Command Remarks select B-channels [ exclusive ] service provider switch selects calls. B-channels for calls. By default, an ISDN interface selects B-channels in ascending order. isdn bch-select-way Set a B-channel selection ascending This command takes effect only when the method.
Page 123: Configuring Isdn Calling Number Identification
Configuring ISDN calling number identification ISDN calling number identification enables an ISDN interface to include the call number of a calling party in the outgoing call SETUP messages. The calling number information can be used for various purposes. For example, the service provider can use this information to identify the pricing scheme for the calling party.
Page 124: Configuring Per-Channel Tei Assignment On A Bri Interface
Step Command Remarks undo isdn link-mode Configuring per-channel TEI assignment on a BRI interface Terminal endpoint identifiers (TEIs) are assigned by the service provider to identify terminal devices. A TEI identifies one terminal device on a point-to-point link and identifies more than one terminal device on a point-to-multipoint link.
Page 125: Enabling Permanent Q.921 Link Connectivity On An Isdn Bri Interface
Enabling permanent Q.921 link connectivity on an ISDN BRI interface You can enable permanent Q.921 link connectivity only on user-side ISDN BRI interfaces. When this feature is enabled, the ISDN BRI interface establishes and maintains permanent data link connections automatically, regardless of whether or not a call is present. When this feature is disabled, the ISDN BRI interface transits to the multiframe established state only when a call is present.
Page 126: Configuring A Bri Interface To Supply Line Power
Configuring a BRI interface to supply line power You can configure only network-side BRI interfaces to supply line power to the terminal equipment. NOTE: Only ISDN BRI interfaces on the BSV module can operate on the network side. You can perform this task only when no call is present. To enable remote powering on an ISDN BRI interface: Step Command...
Page 127: Displaying And Maintaining Isdn Settings
unacknowledged frames. You can tune the size depending on the link status to maximize the throughput. When sending a frame, Q.921 checks the number of unacknowledged frames. Suppose V(A) is the sequence number of the previous acknowledged frame, V(S) is the sequence number of the frame to be sent, and k is the sliding window size.
Page 128 Figure 38 Network diagram Router A CE1/Pri 2/3/0 202.38.154.1/16 8810152 ISDN network CE1/Pri 2/3/0 202.38.154.2/16 8810154 Router B Configuration procedure In this example, the ISDN PRI interfaces on Router A and Router B are operating as the user side (the default). You must configure the ISDN PRI interfaces as the network side on the service provider switches connected to the routers.
Page 129: Ni-Enabled Isdn Bri Configuration Example
[RouterB-Serial2/3/0:15] dialer route ip 202.38.154.1 8810152 [RouterB-Serial2/3/0:15] dialer-group 1 Verify the configuration: # Ping 202.38.154.2 from Router A to verify that the state of a B-channel on E1 2/3/0 changes to Line up. # Ping 202.38.154.2 again to verify that the ISDN PRI line transfers data without any losses. NI-enabled ISDN BRI configuration example Network requirements As shown in...
Page 130: Troubleshooting
[RouterA-Bri2/4/0] isdn spid resend 2 Configure Router B: # Configure dialer-group 1 to allow any IP packets to trigger a call setup. <RouterB> system-view [RouterB] dialer-group 1 rule ip permit # Assign interface BRI 2/4/0 an IP address. [RouterB] interface bri 2/4/0 [RouterB-Bri2/4/0] ip address 202.38.154.2 255.255.0.0 # Enable C-DDR on the interface, configure the route to Router A, and assign the interface to dialer-group 1.
Page 131 − If the Q.921 state is correct, verify the dialup configuration. Verify that the physical layer is active: a. Enable Q.921 debugging. b. If the system displays a "Failed to send" message, execute the shutdown and undo shutdown command to re-enable the interface. Verify that the dial-up configuration is correct.
Page 132: Configuring Atm
Configuring ATM ATM is supported only by MSR routers installed with an ATM-OC3, ADSL2+, G.SHDSL, or G.SHDSL.BIS interface module. Overview Asynchronous Transfer Mode (ATM) is a technology based on packet transmission mode, and it also incorporates the high speed of circuit transmission mode. Due to its flexibility and support for multimedia services, ATM is regarded as a core broadband technology.
Page 133: Atm Architecture
Figure 41 ATM switching Router A ATM switch B Router C ATM2/4/1 ATM2/4/1 ATM2/4/2 ATM2/4/1 PVC 0/100 PVC 0/100 PVC 2/101 PVC 2/101 GE1/0/1 GE1/0/1 Port VPI/VCI Port VPI/VCI ATM2/4/1 0/100 ATM2/4/2 2/101 ATM architecture ATM has a three-dimensional architecture. It contains the user plane, control plane, and management plane.
Page 134: Atm Service Types
• 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. AAL passes 48-byte payloads, which are called segmentation and reassembly protocol data units (SAR-PDUs) to the ATM layer.
Page 135: Atm Oam
IPoA IP over ATM (IPoA) enables ATM to carry IP packets. In an IPoA implementation, ATM acts as the data link layer protocol for the IP hosts on the same network. To enable these hosts to communicate across an ATM network, IP packets must be encapsulated in ATM cells. By making full use of the advantages of ATM, IPoA delivers excellent network performance and mature QoS assurance.
Page 136: Atm Configuration Task List
comes up when the specified number of successive OAM F5 Loopback cells are received. The PVC goes down when the specified number of successive OAM F5 Loopback cells are not received. • OAM F5 end-to-end—Sends OAM F5 end-to-end cells through the specified PVC on the specified ATM interface.
Page 137: Configuring A Pvc Group
Step Command Remarks Create a PVC and enter pvc { pvc-name [ vpi/vci ] | vpi/vci } By default, no PVCs exist. PVC view. Bring up the PVC. undo shutdown By default, the PVC is up. Configuring a PVC group A PVC group can share traffic load among PVCs in it by transmitting IP packets of different priorities through different PVCs.
Page 138: Configuring The Atm Service Type
• aal5nlpid—Supports only IPoA mappings. Follow these guidelines when you configure ATM AAL5 encapsulation types: • Devices on the two ends must be configured with the same ATM AAL5 encapsulation types. • Only aal5snap supports InARP. You cannot configure InARP when aal5mux or aal5nlpid is used.
Page 139: Configuring Applications Carried By Atm
Step Command Remarks • Set the service type to CBR configure related parameters: service cbr output-pcr [ cdvt cdvt-value ] • Set the service type to UBR The default service type is configure related UBR. parameters: The newly configured service service ubr output-pcr Configure the service type and type overwrites the existing...
Page 140: Configuring A Ve Interface
Configuring a VE interface Before you configure IPoEoA and PPPoEoA, you must specify a VE interface. To configure a VE interface: Step Command Remarks Enter system view. system-view If the interface already exists, use this command to enter the VE Create a VE interface and interface virtual-ethernet...
Page 141: Configuring Ipoa
Configuring IPoA To enable the upper-layer protocols to find a remote device by its IP address, map the IP address of the remote device to the local PVC or PVC group. To configure an IP mapping, use one of the following methods: •...
Page 142: Configuring Ipoeoa
Step Command Remarks • Enter view: pvc { pvc-name [ vpi/vci ] | Enter PVC view or vpi/vci } PVC group view. • Enter group view: pvc-group group-number Configure IPoA mapping to enable the map ip { ip-address | default | By default, no mappings exist.
Page 143: Configuring Pppoa
Configuring PPPoA When two routers are connected by using DSL interfaces through a dial-up connection, configure them as a PPPoA server and client. The PPPoA server acts as the PPP server, and you must configure an address pool for it to assign an IP address to the remote node. The PPPoA client acts as the PPP client, and you must configure address negotiation on it to accept the IP address assigned by the server end.
Page 144: Configuring Vp Policing
Step Command Remarks Create a VT interface. interface virtual-template vt-number Configure PPP authentication and IP address on the VT interface instead of an ATM Configure interface. The IP address authentication configuration does not take address. effect on ATM interfaces. server, configure address pool to assign an When you configure a static...
Page 145: Re-Marking The Clp Flag Value Of Atm Cells
Step Command Remarks Enter system system-view view. Enter interface atm interface-number interface view. Configure By default, VP policing is parameters vp limit vpi scr disabled. VP policing. Re-marking the CLP flag value of ATM cells You can re-mark the cell loss priority (CLP) flag value of ATM cells to specify the drop precedence for the cells.
Page 146: Configuring Atm Oam Functions
Step Command Remarks 13. Apply the QoS policy to the apply policy policy-name By default, no QoS policy PVC. outbound is applied to the PVC. NOTE: For more information about traffic class, traffic behavior, and QoS policy, see ACL and QoS Configuration Guide.
Page 147: Atm Configuration Examples
Task Command information about PVCs interface-number.subnumber } [ pvc { pvc-name | vpi/vci } | pvc-group or PVC groups. group-number ] ] display interface [ virtual-ethernet [ interface-number ] ] [ brief [ description | Display interface down ] ] information.
Page 148: Ipoeoa Configuration Example
[RouterA] interface atm 2/4/0 [RouterA-ATM2/4/0] ip address 202.38.160.1 255.255.255.0 # Create PVCs, and enable them to carry IP. [RouterA-ATM2/4/0] pvc to_b 0/40 [RouterA-ATM2/4/0-pvc-to_b-0/40] map ip 202.38.160.2 [RouterA-ATM2/4/0-pvc-to_b-0/40] quit [RouterA-ATM2/4/0] pvc to_c 0/41 [RouterA-ATM2/4/0-pvc-to_c-0/41] map ip 202.38.160.3 Configure Router B: # Enter the view of interface ATM 2/4/0 and configure an IP address for it. <RouterB>...
Page 149 Figure 45 Network diagram ADSL Router A Host A VEth2/4/0 202.38.160.1/24 DSLAM Host B Router C ATM2/4/0.1 VPI/VCI: To Router A:0/60 To Router B:0/61 Host C ADSL Router B Host D Configuration procedure Configure Router C: # Create a VE interface and configure an IP address for it. <RouterC>...
Page 150: Pppoa Configuration Example
PPPoA configuration example Network requirements As shown in Figure 46, two hosts dial into the ATM network each through an ADSL router, and communicate with Router C through DSLAM. This configuration example has the following requirements: • Create VT for multiuser on Router C, and configure PPP mapping on VT. •...
Page 151: Pppoeoa Configuration Example
<RouterA> system-view [RouterA] interface virtual-template 0 [RouterA-Virtual-Template0] ip address ppp-negotiate [RouterA-Virtual-Template0] quit # Create a PVC, and enable it to carry PPP. [RouterA] interface atm 2/4/0 [RouterA-ATM2/4/0] pvc pppoa 0/60 [RouterA-ATM2/4/0-pvc-pppoa-0/60] map ppp virtual-template 0 [RouterA-ATM2/4/0-pvc-pppoa-0/60] quit [RouterA-ATM2/4/0] quit Configure ADSL Router B in the same way ADSL Router A is configured. Verifying the configuration Both ADSL Router A and ADSL Router B can ping Router C successfully.
Page 152 [RouterC-Virtual-Template10] ip address 202.38.160.1 255.255.255.0 [RouterC-Virtual-Template10] remote address 202.38.162.1 [RouterC-Virtual-Template10] quit [RouterC] interface virtual-template 11 [RouterC-Virtual-Template11] ip address 202.38.161.1 255.255.255.0 [RouterC-Virtual-Template11] remote address 202.38.162.2 [RouterC-Virtual-Template11] quit # Create VE interfaces, and enable them to carry PPP. [RouterC] interface virtual-ethernet 2/4/1 [RouterC-Virtual-Ethernet2/4/1] pppoe-server bind virtual-template 10 [RouterC-Virtual-Ethernet2/4/1] quit [RouterC] interface virtual-ethernet 2/4/0...
Page 153: Atm Pvc Transmission Priority Configuration Example
Verifying the configuration Both ADSL Router A and ADSL Router B can ping Router C successfully. ATM PVC transmission priority configuration example Network requirements As shown in Figure 48, create PVC 1 and PVC 2 on the same ATM 155 Mbps interface. Each PVC is assigned 100 Mbps of bandwidth and is associated with the UBR service.
Page 154: Troubleshooting Atm
Troubleshooting ATM Link state error in IPoA application Symptom When IPoA is used, the link state is down. Solution • Verify that the optical fiber is connected correctly. • Verify that the local IP address is configured. • Verify that the PVC is successfully created. Link report error in PPPoA application Symptom When PPPoA is used, the link cannot be up.
Page 155: Ping Failure After Pppoa Configuration
Solution Determine if this fault results from enabling OAM F5 Loopback cell transmission and retransmission detection. When two routers are connected, the VPI/VCI values of the PVCs on the two routers must be the same. If OAM F5 cell transmission and retransmission detection is enabled, and the VPI/VCI values of the two directly connected nodes are not the same, the local PVC state cannot change to Ping failure after PPPoA configuration Symptom...
Page 156: Managing A Modem
Managing a modem This chapter describes how to manage and control the modems connected to the device. Feature and hardware compatibility This feature is available only on the following interface modules and interfaces: • AM interface modules. • ASE interface modules. •...
Page 157: Setting The Answer Timeout Timer
Step Command Remarks This command is available on the following user lines: • TTY lines for the following interfaces: AM interface  Asynchronous serial interface  Asynchronous/synchronous serial line { first-num1 [ last-num1 ] |  Enter user line interface operating in asynchronous first-num2 view.
Page 158: Setting The Modem Answer Mode
Setting the modem answer mode To ensure correct operation of the modem, set the auto-answer mode on the user line to be the same as the modem. • Enable auto-answer mode if the modem is in auto-answer mode (the AA LED of the modem lights up).
Page 159: Enabling Modem Callback
Step Command Remarks line view of an AM [ last-num2 ] } interface. Enable the modem By default, a modem does not modem caller-number resolve obtain caller obtain the caller number when it [ ata-waiting-time time ] number. accepts a call from a terminal. Enabling modem callback The callback function enables a modem to disconnect an incoming call and calls back the calling party on request.
Page 160: Setting The Country Code Of A Modem
Setting the country code of a modem CAUTION: This task disconnects the modem connection. Modem encoding format differs with countries. You must configure the correct country code for a modem to function correctly. This task is available only on AM interfaces. To set the country code of a modem: Step Command...
Page 161: Verifying The Configuration
An external modem is in an abnormal state. For example, the dial tone or busy tone keeps humming. Solution To resolve the problem: Execute the shutdown and undo shutdown commands on the physical interface connected to the modem. Power-cycle the modem. If the problem persists, contact HPE Support.
Page 162: Managing A 3G/4G Modem
Managing a 3G/4G modem A 3G/4G modem connects a device to a 3G/4G network. 3G/4G modem modules include USB 3G/4G modem modules and SIC-3G/4G modem modules. They are managed in cellular interface view. • A USB 3G/4G modem module is hot swappable. It is managed in a fixed cellular interface view. The cellular interface varies by the device model.
Page 163: 4G Modem Management Configuration Task List
Tasks at a glance (Optional.) Configuring manual reboot 4G modem management configuration task list Tasks at a glance Configuring a cellular interface for a 4G modem Configuring an Eth-channel interface for a 4G modem Configuring an IP address for an Eth-channel interface of a 4G modem Configuring a 3G/4G network Configuring parameter profiles (Optional.)
Page 164: Configuring An Eth-Channel Interface For A 4G Modem
Step Command Remarks the cellular interface. cellular interface is interface name Interface, for example, Cellular 2/4/0 Interface. This command names Channelize cellular Eth-channel interface interface into an Eth-channel eth-channel channel-number eth-channel interface. cellular-number:channel-number. Bring cellular By default, the cellular interface is undo shutdown interface.
Page 165: Configuring A 3G/4G Network
The ways for the Eth-channel interface to obtain an IP address are mutually exclusive. The most recent configuration overrides the previous one. TIP: Changing the IP address will result in dialup interruption. Immediate re-dialup upon interruption might not be supported by service providers. To configure an IP address for an Eth-channel interface: Step Command...
Page 166: Configuring Parameter Profiles
Step Command Remarks mode. mnc } the modem model. mode { 1xrtt | auto | evdo | gsm | default setting this Specify the network service gsm-precedence | hybrid | lte | command and support for the which modem td | td-precedence | wcdma | arguments depend on the modem connects.
Page 167: Specifying The Primary And Backup Profiles
Step Command Remarks Return to system view quit (Optional.) Delete the profile. undo apn-profile profile-name Specifying the primary and backup profiles By default, profile 1 is used for 3G/4G modem dialup. The dialup fails if profile 1 does not exist. You can also specify the primary and backup profiles for 3G/4G modem dialup.
Page 168: Configuring Dm
If PIN verification fails after a maximum number of attempts, the SIM/UIM card is locked, and a PIN Unlocking Key (PUK) is required to unlock the card. The maximum number of attempts depends on the 3G/4G modem model. To configure PIN verification: Step Command Remarks...
Page 169: Issuing A Configuration Directive To A 3G/4G Modem
Step Command Remarks Enter system view. system-view controller cellular Enter cellular interface view. interface-number The default setting depends on the modem model. The value of lowthreshold cannot rssi { gsm | 1xrtt | evdo | lte } Set RSSI thresholds for the be smaller than the value of { low lowthreshold | medium 3G/4G modem.
Page 170: Configuring Manual Reboot
Step Command Remarks timeout and the threshold for auto-recovery threshold seconds the number of consecutive consecutive timeout threshold is timeouts to enable automatic reboot of the 3G/4G modem. The configuration is saved on the device rather than the 3G/4G modem. Configuring manual reboot Step Command...
Page 171: 4G Modem Management Configuration Examples
3G/4G modem management configuration examples 3G modem management configuration example Network requirements As shown in Figure • The router provides a USB 3G or SIC-3G modem. • The PC dials up to access a 3G network through Dial-on-Demand Routing (DDR). For more information about DDR dialup, see "Configuring DDR."...
Page 172: Modem Management Configuration Example
4G modem management configuration example Network requirements As shown in Figure • The router provides a USB 4G or SIC-4G modem. • The PC dials up to access an LTE network through Dial-on-Demand Routing (DDR). For more information about DDR dialup, see "Configuring DDR." Figure 51 Network diagram LTE network Router...
Page 173 If the 3G/4G modem still fails to function, execute the modem reboot command on the cellular interface. If the problem persists, contact HPE Support.
Page 174: Configuring Ddr
Configuring DDR Overview As shown in Figure 52, routers use dial-on-demand routing (DDR) for the following purposes: • Setting up a dialup connection over PSTN/ISDN when communication needs arise. • Tearing down the connection when the communication is complete. Figure 52 DDR communication process PSTN line ISDN line Telephone...
Page 175 The physical interface can have one or more call destinations. This method applies when only one interface places or receives calls. • Configure DDR parameters on a dialer interface. A dialer interface is associated with a group of physical interfaces and selects a physical interface to place or receive calls.
Page 176: Ddr Types
Figure 54 Relationships among physical interfaces, dialer interfaces, and call destinations in bundle DDR Physical interface Dialer interface Dialer bundle 1 Ser2/1/0 Call destination A Dialer 1 Bri2/4/0 Dialer bundle 2 Ser2/1/1 Call destination B Dialer 2 Bri2/4/1 Ser2/1/2 Dialer bundle 3 Asy2/5/0 Dialer 3 Call destination C...
Page 177: Ddr Configuration Task Lists
• MSR2004-24/2004-48. • MSR3012/3024/3044/3064. • MSR954(JH296A/JH297A/JH298A/JH299A/JH373A) • MSR958(JH300A/JH301A) Commands and descriptions for distributed devices apply to MSR4060 and MSR4080 routers. DDR configuration task lists Packet-triggered DDR configuration task list Tasks at a glance (Required.) Configuring basic settings for DDR • Configuring physical interfaces •...
Page 178: Route-Triggered Ddr Configuration Task List
Tasks at a glance (Required.) Configuring auto-dial (Optional.) Disconnecting a dialup link Route-triggered DDR configuration task list Tasks at a glance (Required.) Configuring basic settings for DDR • Configuring physical interfaces • Configuring link layer/network/routing protocols on the dialup interface (Required.) Perform one of the following tasks: •...
Page 179: Configuring Link Layer/Network/Routing Protocols On The Dialup Interface
Configuring link layer/network/routing protocols on the dialup interface Dialup interfaces support PPP, IP, RIP, and OSPF. For information about configuring these protocols, see "Configuring PPP and MP," Layer 3—IP Services Configuration Guide, and Layer 3—IP Routing Configuration Guide. When you configure PPP, follow these guidelines: •...
Page 180: Configuring Traditional Ddr
Configuring traditional DDR For traditional DDR, you can configure PAP or CHAP authentication (see "Configuring PPP and MP"). As a best practice, configure PAP or CHAP authentication for security purposes. When you configure PAP or CHAP authentication, follow these guidelines: •...
Page 181: Configuring An Interface To Receive Calls
Step Command Remarks • dialer number dial-number • dialer route next-hop-address mask network-mask-length By default, no dial string is vpn-instance Configure a dial string. configured. vpn-instance-name dial-number dial-number interface interface-type interface-number [ broadcast ] Return to system view. quit interface interface-type Enter physical interface view.
Page 182: Configuring Bundle Ddr
Step Command Remarks interface-number Enable traditional DDR on By default, traditional DDR is dialer circular enable the interface. disabled on an interface. To receive calls from multiple dialer route ip next-hop-address remote sites, configure this (Optional.) Configure [ mask network-mask-length ] command multiple times.
Page 183: Configuring A Dialer Interface To Receive Calls
To configure a dialer interface to place calls: Step Command Remarks Enter system view. system-view Create a dialer interface and interface dialer number enter its view. Enable bundle DDR on the default, bundle dialer bundle enable interface. disabled. Specify a dial string. dialer number dial-number Return to system view.
Page 184: Configuring Attributes For A Dialup Interface
Step Command Remarks By default, a physical interface does not belong to a dialer bundle. Assign the physical interface dialer bundle-member number Make sure number to a dialer bundle. [ priority priority ] arguments interface dialer dialer bundle-member commands use the same value.
Page 185: Configuring Mp For Ddr
Step Command Remarks The default setting is five. 10. Set the keepalive retry limit. timer-hold retry retries A link is removed after the keepalive retry limit is reached. 11. Set the polling interval. timer-hold period The default setting is 10 seconds. 12.
Page 186: Configuration Restrictions And Guidelines
• The percentage of traffic to the bandwidth of (n-1) activated links is equal to or higher than the traffic threshold. For more information about MP, see "Configuring PPP and MP." Configuration restrictions and guidelines When you configure MP for DDR, follow these restrictions and guidelines: •...
Page 187: Configuring The Callback Client
return call. If a return call is needed, the callback server disconnects the call and places a return call according to the username or callback number. PPP callback has the following benefits: • Enhanced security—The server places a return call to the locally configured number, which prevents caller number spoofing.
Page 188: Configuring The Callback Server
Step Command Remarks Windows server requires callback clients to send callback numbers. Configuring the callback server You can configure the callback server to use traditional DDR or bundle DDR. The configuration differences are as follows: • Traditional DDR—The callback server can place return calls according to either of the following: Dial string configured with the dialer route command (PPP authentication must be ...
Page 189: Configuring Isdn Caller Number Callback
Step Command Remarks dial-number dial-number interface interface-type interface-number ] [ broadcast | user hostname ] * Configuring the callback server by using bundle DDR Step Command Remarks Enter system view. system-view Enter dialer interface view. interface dialer number Enable interface By default, an interface does not ppp callback server accept callback requests.
Page 190: Configuration Restrictions And Guidelines
• Reduced charges—The charge payer can be changed when the charge rates are different in the two directions. ISDN caller number callback uses the following process: When a server receives a call, it determines the configured dialer call-in command relevant to the dial-in number.
Page 191: Configuring A Callback Server By Using Bundle Ddr
Step Command Remarks calling number. Configuring a callback server by using bundle DDR Step Command Remarks Enter system view. system-view Enter dialer interface view. interface dialer interface-number Configure the interface to accept incoming calls from dialer call-in remote-number By default, calls are not filtered by the specified calling number [ callback ] calling number.
Page 192: Creating A Dynamic Route Backup Group
To use this feature, you must create a dynamic route backup group and define a network to be monitored. When a dialup interface is assigned to the dynamic route backup group, the system monitors the routes by using the following process: The system identifies whether a minimum of one valid route exists to the monitored network.
Page 193: Setting The Secondary Link Disconnection Delay
Step Command Remarks interface interface-type Enter dialup interface view. interface-number By default, a dialup interface is not Assign the interface to a standby routing-group assigned to a dynamic route dynamic route backup group. group-number backup group. Setting the secondary link disconnection delay Typically, the secondary link will be disconnected when the primary link recovers.
Page 194: Displaying And Maintaining Ddr
Displaying and maintaining DDR Execute display commands in any view and reset commands in user view. Task Command Display DDR information for a specified dialup display dialer interface interface-type interface or all dialup interfaces. interface-number ] display interface [ dialer [ interface-number ] ] [ brief Display information about dialer interfaces.
Page 195 [RouterA-Dialer0] dialer-group 1 # Configure dial strings for calling Router B and Router C. [RouterA-Dialer0] dialer route ip 100.1.1.2 8810052 [RouterA-Dialer0] dialer route ip 100.1.1.3 8810063 [RouterA-Dialer0] quit # Configure Serial 2/1/0 to operate as an asynchronous interface in protocol mode. [RouterA] interface serial 2/1/0 [RouterA-Serial2/1/0] physical-mode async [RouterA-Serial2/1/0] async-mode protocol...
Page 196: Pstn-Based Bundle Ddr Configuration Example
# Create dialer group 1 and configure a dial rule for it. <RouterC> system-view [RouterC] dialer-group 1 rule ip permit # Configure Serial 2/1/0 to operate as an asynchronous interface in protocol mode. [RouterC] interface serial 2/1/0 [RouterC-Serial2/1/0] physical-mode async [RouterC-Serial2/1/0] async-mode protocol # Configure an IP address for the interface.
Page 197 Figure 56 Network diagram Router B Ser2/1/0 8810048 8810052 Modem Dialer 0 Modem 100.1.1.2/24 Dialer 0 100.1.1.1/24 Ser2/1/0 Router A PSTN Ser2/1/1 Dialer 1 122.1.1.1/24 8810049 8810063 Modem Modem Router C Ser2/1/0 Dialer 0 122.1.1.2/24 Configuration procedure Configure Router A: # Create dialer group 1 and configure a dial rule for it.
Page 198 [RouterA] interface dialer 1 [RouterA-Dialer1] ip address 122.1.1.1 255.255.255.0 # Enable bundle DDR on the interface. [RouterA-Dialer1] dialer bundle enable # Specify the host name of the remote router allowed to call in. [RouterA-Dialer1] dialer peer-name userc # Associate the interface with dialer group 1. [RouterA-Dialer1] dialer-group 1 # Configure PAP authentication on the interface.
Page 199 # Create dialer group 2 and configure a dial rule for it. <RouterB> system-view [RouterB] dialer-group 2 rule ip permit # Create a local user usera for authenticating Router A, and configure the service type as PPP. [RouterB] local-user usera class network [RouterB-luser-network-usera] password simple usera [RouterB-luser-network-usera] service-type ppp [RouterB-luser-network-usera] quit...
Page 200: Isdn-Based Traditional Ddr Configuration Example
# Configure an IP address for Dialer 0. [RouterC] interface dialer 0 [RouterC-Dialer0] ip address 122.1.1.2 255.255.255.0 # Enable bundle DDR on the interface. [RouterC-Dialer0] dialer bundle enable # Configure the Specify the host name of the remote router allowed to call in. [RouterC-Dialer0] dialer peer-name usera # Configure the dial string for calling Serial 2/1/1 on Router A.
Page 201 Figure 57 Network diagram NT 1 Router B Bri2/4/0 8810052 100.1.1.2/24 Router A NT 1 8810048 ISDN Bri2/4/0 100.1.1.1/24 NT 1 Router C 8810063 Bri2/4/0 100.1.1.3/24 Configuration procedure Configure Router A: # Create dialer group 1 and configure a dial rule for it. <RouterA>...
Page 202: Isdn-Based Bundle Ddr Configuration Example
# Configure an IP address for interface BRI 2/4/0. [RouterC] interface bri 2/4/0 [RouterC-Bri2/4/0] ip address 100.1.1.3 255.255.255.0 # Enable traditional DDR on the interface. [RouterC-Bri2/4/0] dialer circular enable # Associate the interface with dialer group 1. [RouterC-Bri2/4/0] dialer-group 1 # Configure the dial string for calling Router A.
Page 203 [RouterA-luser-network-userb] quit [RouterA] local-user userc class network [RouterA-luser-network-userc] password simple userc [RouterA-luser-network-userc] service-type ppp [RouterA-luser-network-userc] quit # Configure an IP address for Dialer 0. [RouterA] interface dialer 0 [RouterA-Dialer0] ip address 100.1.1.1 255.255.255.0 # Enable bundle DDR on the interface. [RouterA-Dialer0] dialer bundle enable # Specify the host name of the remote router allowed to call in.
Page 204 [RouterB] dialer-group 2 rule ip permit # Create a local user usera for authenticating Router A, and configure the service type as PPP. [RouterB] local-user usera class network [RouterB-luser-network-usera] password simple usera [RouterB-luser-network-usera] service-type ppp [RouterB-luser-network-usera] quit # Configure an IP address for Dialer 0. [RouterB] interface dialer 0 [RouterB-Dialer0] ip address 100.1.1.2 255.255.255.0 # Enable bundle DDR on the interface.
Page 205: Mp For Ddr Configuration Example
# Configure the dial string for calling Router A. [RouterC-Dialer0] dialer number 8810048 # Configure PAP authentication on the interface. [RouterC-Dialer0] ppp authentication-mode pap [RouterC-Dialer0] ppp pap local-user userc password simple userc [RouterC-Dialer0] quit # Assign the interface to dialer bundle 0. [RouterC] interface bri 2/4/0 [RouterC-Bri2/4/0] dialer bundle-member 0 # Enable PPP encapsulation on the interface.
Page 206 [RouterA-luser-network-userb] password simple userb [RouterA-luser-network-userb] service-type ppp [RouterA-luser-network-userb] quit # Set the traffic statistics collection interval to 3 seconds. [RouterA] dialer flow-interval 3 # Configure an IP address for Dialer 0, enable bundle DDR, and configure MP. [RouterA] interface dialer 0 [RouterA-Dialer0] ip address 100.1.1.1 255.255.255.0 [RouterA-Dialer0] dialer bundle enable [RouterA-Dialer0] ppp mp...
Page 207: Isdn Caller Number Callback Configuration Example
[RouterB] local-user usera class network [RouterB-luser-network-usera] password simple usera [RouterB-luser-network-usera] service-type ppp [RouterB-luser-network-usera] quit # Set the traffic statistics collection interval to 3 seconds. [RouterB] dialer flow-interval 3 # Configure an IP address for Dialer 0. [RouterB] interface dialer 0 [RouterB-Dialer0] ip address 100.1.1.2 255.255.255.0 # Enable traditional DDR on the interface.
Page 208: Router-To-Router Ppp Callback Configuration Example
NOTE: Make sure the stored program controlled switch (SPCS) in the ISDN network supports sending ISDN calling numbers. Configuration procedure Configure Router A: # Create dialer group 1 and configure a dial rule for it. <RouterA> system-view [RouterA] dialer-group 1 rule ip permit # Configure an IP address for interface BRI 2/4/0.
Page 209 Figure 61 Network diagram Router A Modem Modem Router B Ser2/1/0 Ser2/1/0 8810048 8810052 100.1.1.1/24 100.1.1.2/24 PSTN Callback server Callback client Configuration procedure Method 1: Use the dial string configured in the dialer route command to call back the client. Configure Router A: # Create dialer group 1 and configure a dial rule for it.
Page 210 [RouterB-Serial2/1/0] ip address 100.1.1.2 255.255.255.0 # Configure the interface as an asynchronous interface in protocol mode. [RouterB-Serial2/1/0] physical-mode async [RouterB-Serial2/1/0] async-mode protocol # Enable traditional DDR on the interface. [RouterB-Serial2/1/0] dialer circular enable # Associate the interface with dialer group 2. [RouterB-Serial2/1/0] dialer-group 2 # Enable PPP encapsulation on the interface.
Page 211: Router-To-Pc Ppp Callback Configuration Example
# Set the holddown timer to 15 seconds. [RouterA-Serial2/1/0] dialer timer enable 15 [RouterA-Serial2/1/0] quit # Configure the user line to be used, and enable modem dial-in and dial-out on it. [RouterA] line tty1 [RouterA-line-tty1] modem enable both Configure Router B: # Create dialer group 2 and configure a dial rule for it.
Page 212 Figure 62 Network diagram Modem Modem Router Ser2/1/0 8810048 8810052 100.1.1.2/24 100.1.1.1/24 PSTN Callback client Callback server Configuring the PC (installed with Windows XP for example) To create a dialup connection with callback capability enabled: Place the modem connected to PC in auto answer mode. Select Start >...
Page 213: Windows Server-To-Router Ppp Callback Configuration Example
The callback server will always place return calls at the number or numbers already set. Configuring the router # Create dialer group 1 and configure a dial rule for it. <Router> system-view [Router] dialer-rule 1 ip permit # Create a local user userpc for the PC, and configure the service type as PPP. [Router] local-user userpc [Router-luser-userpc] password simple userpc [Router-luser-userpc] service-type ppp...
Page 214: Configuring The Router
Configure PPP callback for traditional DDR between the router and Windows server. Then, the Windows server can use the specified dial string to make a return call when the router calls the Windows server. Figure 63 Network diagram NT Server Router Modem Modem...
Page 215 Configuring the Windows server For Microsoft Windows users, the server must be Windows 2000 or later such as Windows XP. This example uses Windows XP. To create a dialup connection with callback capability enabled: Right-click the My Network Places icon, and select the Properties option from the menu that appears.
Page 216: Configuration Example For Circular Dial String Backup And Internet Access
Configuration example for circular dial string backup and Internet access Network requirements As shown in Figure • 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. The PSTN dial strings available on it are 8810048 through 8810055, allowing the router to provide services to 16 online users.
Page 217 Figure 65 Network diagram for dial string backup/Internet access service (ISDN mode) Router C Bri2/4/0 NT 1 Ser2/3/0:15 Router D 100.1.1.254/24 …… ISDN Internet 8810048 NT 1 Configuration procedure for PSTN mode On Router A on the dialup side, configure circular dial string backup. On Router B, perform the following tasks: •...
Page 218 [RouterA-Serial2/1/0] dialer route ip 100.1.1.254 8810055 [RouterA-Serial2/1/0] quit # Configure the user line to be used, and enable modem dial-in and dial-out on it. [RouterA] line tty1 [RouterA-line-tty1] modem enable both Configure Router B: # Create dialer group 2 and configure a dial rule for it. <RouterB>...
Page 219 # Configure PAP authentication on the interface. [RouterB-Async2/4/0] ppp authentication-mode pap [RouterB-Async2/4/0] ppp pap local-user userb password simple userb [RouterB-Async2/4/0] quit # Repeat the steps to configure physical and link layer parameters for interfaces Async 2/4/1 through Async 2/4/7. (Details not shown.) # Configure user lines TTY 1 through TTY 7 for interfaces Async 2/4/0 through Async 2/4/7, and enable modem dial-in and dial-out on them.
Page 220 m. 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 select the No callback option. n.
Page 221: Dynamic Route Backup For Traditional Ddr Configuration Example
[RouterD] local-user user16 class network [RouterD-luser-network-user16] password simple user16 [RouterD-luser-network-user16] service-type ppp [RouterD-luser-network-user16] quit # Bundle timeslots on CE1/PRI interface E1 2/3/0 into a PRI group. [RouterD] controller e1 2/3/0 [RouterD-E1 2/3/0] pri-set [RouterD-E1 2/3/0] quit # Enable traditional DDR on Serial 2/3/0:15. (This interface is automatically created on CE1/PRI interface E1 2/3/0.) [RouterD-E1 2/3/0] interface serial 2/3/0:15 [RouterD-Serial2/3/0:15] dialer circular enable...
Page 222 Figure 66 Network diagram Router A Router B Ser2/1/0 Ser2/1/0 10.0.0.1/8 10.0.0.2/8 Loop1 40.0.0.1/32 Bri2/4/0 Bri2/4/0 20.0.0.1/8 20.0.0.2/8 ISDN Configuration procedure Configure Router A: # Create dialer group 1 and configure a dial rule for it. <RouterA> system-view [RouterA] dialer-group 1 rule ip permit # Configure an IP address for interface BRI 2/4/0.
Page 223: Dynamic Route Backup For Bundle Ddr Configuration Example
[RouterA-Bri2/4/0] ospf network-type broadcast # Enable dynamic route backup on BRI 2/4/0. [RouterA-Bri2/4/0] standby routing-group 1 Configure Router B: # Create dialer group 1 and configure a dial rule for it. <RouterB> system-view [RouterB] dialer-group 1 rule ip permit # Configure an IP address for interface BRI 2/4/0. [RouterB] interface bri 2/4/0 [RouterB-Bri2/4/0] ip address 20.0.0.2 8 # Enable traditional DDR on the interface.
Page 224 Figure 67 Network diagram Router A Ser2/1/0 Router B Ser2/1/0 Loop1 10.0.0.1/8 10.0.0.2/8 30.0.0.0/8 Bri2/4/0 Bri2/4/0 20.0.0.1/24 20.0.0.2/24 ISDN Configuration procedure Configure Router A: # Create dialer group 1 and configure a dial rule for it. <RouterA> system-view [RouterA] dialer-group 1 rule ip permit Create a local user userb for Router B, and configure the service type as PPP.
Page 225 # Configure PAP authentication on BRI 2/4/0. [RouterA-Bri2/4/0] ppp authentication-mode pap [RouterA-Bri2/4/0] ppp pap local-user usera password simple usera [RouterA-Bri2/4/0] quit # Configure an IP address for Serial 2/1/0. [RouterA] interface serial 2/1/0 [RouterA-Serial2/1/0] ip address 10.0.0.1 8 # Enable PPP encapsulation on the interface. [RouterA-Serial2/1/0] link-protocol ppp [RouterA-Serial2/1/0] quit # Configure RIP.
Page 226: Configuration Example For Dynamic Route Backup For Multiple Networks
[RouterB] interface bri 2/4/0 [RouterB-Bri2/4/0] dialer bundle-member 0 # Configure PAP authentication on the interface. [RouterB-Bri2/4/0] ppp authentication-mode pap [RouterB-Bri2/4/0] ppp pap local-user userb password simple userb [RouterB-Bri2/4/0] quit # Configure an IP address for Serial 2/1/0. [RouterB] interface serial 2/1/0 [RouterB-Serial2/1/0] ip address 10.0.0.2 8 # Enable PPP encapsulation on the interface.
Page 227 Figure 68 Network diagram XGE1/0/1 10.0.0.1/8 Router A Ser2/1/0 Router B Ser2/1/0 XGE1/0/2 1.0.0.1/8 1.0.0.2/8 11.0.0.1/8 XGE1/0/3 Ser2/3/1:15 Ser2/3/1:15 12.0.0.1/8 2.0.0.2/8 2.0.0.1/8 ISDN 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 networks can be connected to multiple devices.
Page 228 [RouterA-Serial2/3/1:15] quit # Configure RIP. [RouterA] rip [RouterA-rip-1] network 1.0.0.0 [RouterA-rip-1] network 2.0.0.0 [RouterA-rip-1] import-route direct # Configure the routes used by the serial interface to adopt higher priorities than those used by the dialup interface. [RouterA] interface serial 2/3/1:15 [RouterA-Serial2/3/1:15] rip metricin 2 Configure Router B: # Create dialer group 1 and configure a dial rule for it.
Page 229: Troubleshooting
[RouterB-rip-1] network 2.0.0.0 [RouterB-rip-1] network 10.0.0.0 [RouterB-rip-1] network 11.0.0.0 [RouterB-rip-1] network 12.0.0.0 [RouterB-rip-1] import-route direct Troubleshooting Failure to establish a dialup connection Symptom DDR dialup connection cannot be established because the modem does not dial when the router forwards data. Solution To resolve the problem: Verify that the modem and phone cable connections are correct, and that the modem...
Page 230: Configuring Frame Relay
Configuring Frame Relay Overview Frame Relay uses statistical multiplexing technology and can establish multiple virtual circuits over a single physical cable to fully utilize network bandwidth. Frame Relay uses data link connection identifiers (DLCIs) to identify virtual circuits. Frame Relay uses the Local Management Interface (LMI) protocol to maintain the status of each virtual circuit.
Page 231: Virtual Circuit
Figure 69 Frame Relay network Frame relay network Router A Router B Router C Router D Ser2/1/0 Ser2/1/0 Ser2/1/1 Ser2/1/0 Ser2/1/1 Ser2/1/0 DLCI=100 DLCI=200 DLCI=300 Virtual circuit Virtual circuits are logical connections established between two devices. Depending on how they are established, virtual circuits include the following types: •...
Page 232: Frame Relay Address Mapping
Frame Relay address mapping Frame Relay address mapping associates the protocol address of a peer device with a Frame Relay address (local DLCI). Then, the upper-layer protocol, for example, IP, can locate the peer device. For example, an IPv4 or IPv6 packet is transmitted across a Frame Relay network as follows: When a DTE device receives an IPv4 or IPv6 packet, the DTE device looks up the IP routing table for the outgoing interface and next-hop address.
Page 233 • ITU-T Q.933 Annex A. • ANSI T1.617 Annex D. • Nonstandard LMI (compatible with other vendors). To communicate properly, the DTE and the DCE must use the same type of LMI. LMI messages LMI messages include the following types: •...
Page 234: Application Scenarios
When a DTE physically goes up, it sends a full status enquiry message to a DCE to request the virtual circuit status. At the same time, the T391 timer and the V391 counter start. The T391 timer specifies the polling interval at which the DTE sends status enquiry messages. When V391<N391, the DTE sends a link integrity verification message and requests only ...
Page 235: Frame Relay Configuration Task List
• CE3. • CPOS. • CT3. • • E1-F. • POS. • SAE. • • T1-F. Frame Relay configuration task list Tasks at a glance Configure DTE-side Frame Relay: • (Required.) Configuring basic DTE-side Frame Relay • (Required.) Configuring local Frame Relay virtual circuits •...
Page 236: Configuring Basic Dce-Side Frame Relay
Step Command Remarks (Optional.) Set the Frame fr interface-type dte The default setting is DTE. Relay interface type to DTE. (Optional.) Configure fr lmi type { ansi | nonstandard | Frame Relay LMI protocol The default setting is q933a. q933a } type.
Page 237: Configuration Restrictions And Guidelines
Configuration restrictions and guidelines When you configure local Frame Relay virtual circuits, follow these restrictions and guidelines: • When manually creating virtual circuits on a DTE interface, make sure their DLCIs are the same as those used on the DCE. •...
Page 238: Configuring Static Address-To-Dlci Maps
Configuring static address-to-DLCI maps Step Command Remarks Enter system view. system-view interface interface-type The interface can be a main Enter interface view. interface-number interface or P2MP subinterface. • Create IPv4 address-to-DLCI map: By default, no static Frame Relay fr map ip { ip-address | address-to-DLCI maps exist.
Page 239: Configuring Frame Relay Iphc
multiple subinterfaces. The subinterfaces and main interfaces can all be configured with virtual circuits to connect to peer devices. Frame Relay subinterfaces include the following types: • Point-to-point (P2P) subinterface—A P2P subinterface connects to a single peer device. • Point-to-multipoint (P2MP) subinterface—A P2MP subinterface connects to multiple peer devices.
Page 240: Configuration Restrictions And Guidelines
Configuration restrictions and guidelines When you configure Frame Relay IPHC, follow these restrictions and guidelines: • To make IPHC take effect on a link, you must enable Frame Relay IPHC on both ends of the link. • You can configure Frame Relay IPHC on either an interface or a virtual circuit. The settings on an interface take effect on all virtual circuits of the interface.
Page 241: Configuring Frame Relay Stac Compression
Step Command Remarks interface interface-type The interface can be a main Enter interface view. interface-number interface or a subinterface. Create a virtual circuit on the By default, no virtual circuits exist fr dlci dlci-number interface. on an interface. By default, Frame Relay IPHC is disabled.
Page 242: Configuring Frame Relay Frf.12 Fragmentation
Step Command Remarks on an interface. Enable STAC compression By default, STAC compression is fr compression stac enable on the virtual circuit. disabled on a virtual circuit. Configuring Frame Relay FRF.12 fragmentation FRF.12 fragmentation divides large packets into smaller fragments at the sending end and reassembles the fragments at the receiving end.
Page 243: Displaying And Maintaining Frame Relay
To enable SNMP notifications for Frame Relay: Step Command Remarks Enter system view. system-view Enable SNMP By default, SNMP notifications are notifications for Frame snmp-agent trap enable fr disabled for Frame Relay. Relay. Displaying and maintaining Frame Relay Execute the display commands in any view and the reset commands in user view. Task Command Display Frame...
Page 244: Frame Relay Configuration Example
Frame Relay configuration example Network requirements As shown in Figure 72, configure Frame Relay so that Router A and Router B can communicate. Figure 72 Network diagram Ser2/1/0 Ser2/1/0 202.38.163.251/24 202.38.163.252/24 DLCI=100 Router A Router B Configuration procedure (Method 1) Using main interfaces Configure Router A: # Assign an IP address to interface Serial 2/1/0.
Page 245: Verifying The Configuration
[RouterA] interface serial 2/1/0.1 p2p # Configure the IP address and create a virtual circuit for the subinterface Serial 2/1/0.1. [RouterA-Serial2/1/0.1] ip address 202.38.163.251 255.255.255.0 [RouterA-Serial2/1/0.1] fr dlci 100 Configure Router B: # Enable Frame Relay encapsulation on interface Serial 2/1/0. <RouterB>...
Page 246: Troubleshooting Frame Relay
Troubleshooting Frame Relay The physical layer is down Symptom The physical layer is down. Solution To resolve this problem: Verify that the physical line is working correctly. Verify that the peer device is working correctly. If the problem persists, contact Hewlett Packard Enterprise Support. The physical layer is already up, but the link layer protocol is down Symptom...
Page 247: Configuring Multilink Frame Relay
Configuring Multilink Frame Relay Multilink Frame Relay (MFR) is a cost-effective bandwidth solution that is based on Frame Relay Forum Multilink Frame Relay UNI/NNI Implementation Agreement (FRF.16.1). This feature increases bandwidth by bundling multiple physical links into a logical link. MFR uses the following concepts: •...
Page 248: Configuring An Mfr Bundle
Configuring an MFR bundle As a best practice to maximize bandwidth that can be used, bundle physical interfaces of the same speed in one bundle. To configure an MFR bundle: Step Command Remarks Enter system view. system-view By default, no MFR interfaces or subinterfaces exist.
Page 249: Displaying And Maintaining Mfr
Step Command Remarks default, synchronous serial Enable MFR encapsulation link-protocol mfr interfaces and POS interfaces use PPP on the interface. encapsulation. Assign the interface to an By default, an interface is not assigned fr mfr interface-number MFR interface. to any MFR interfaces. (Optional.) Set the MFR By default, the name of the current mfr link-name name...
Page 250: Configuration Procedure
Configuration procedure Configure Router A: # Create interface MFR 0/0/2, and assign an IP address to the interface. <RouterA> system-view [RouterA] interface mfr0/0/2 [RouterA-MFR0/0/2] ip address 10.140.10.1 255.255.255.0 # Set the type of the interface to DTE. [RouterA-MFR0/0/2] fr interface-type dte # Configure a static Frame Relay address-to-DLCI map for the interface.
Page 251 [RouterA] display fr pvc PVC information for interface MFR0/0/2 (DTE, physically up) DLCI: 100 Type: Static Interface: MFR0/0/2 Encapsulation: IETF Creation time: 2014/08/18 06:38:00 Status: Active Input: 0 packets, 0 bytes, 0 dropped Output: 0 packets, 0 bytes, 0 dropped # Verify that Router A and Router B can ping each other.
Page 252: 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 Boldface Bold text represents commands and keywords that you enter literally as shown.
Page 253: 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 254: 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 255: 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 256 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 257 Index PPP PAP authentication configuration, Numerics AAL5 encapsulation (ATM), 1-way ACCM PPP authentication configuration (1-way PPP negotiation, CHAP), accounting PPP authentication configuration (1-way PPP RADIUS NAS-Port-Type attribute, PAP), ACFC 2-way PPP negotiation, PPP authentication configuration (2-way PAP), DDR dial rule+interface association, 3G modem address 3G/4G network configuration,...
Page 258 display, interface configuration, backing up IPoA configuration, 132, 138 3G/4G modem backup profile, IPoEoA configuration, 133, 139 bundle DDR dynamic route backup, maintain, DDR circular dial string backup+Internet access, OAM function configuration, OAM functions, DDR dial-up interface assignment to dynamic PPPoA configuration, 134, 141 route backup group,...
Page 259 physical interface configuration, PPPoE session, PPP callback client, client PPP callback configuration, DDR callback server (traditional DDR), PPP callback server, DDR PPP callback server (bundle DDR), bundling DDR PPP callback server (traditional DDR), MFR bundle configuration, IMSI/SN binding authentication, MFR bundle link configuration, L2TP tunnel configuration (client-initiated), PPPoE client configuration (diagnostic mode), PPPoE client configuration (on-demand mode),...
Page 260 bundle DDR (ISDN-based), Frame Relay mapping (static address-to-DLCI map), bundle DDR (PSTN-based), Frame Relay SNMP notification, bundle DDR dialer interface (sending), Frame Relay STAC compression, bundle DDR dialer interface calls (receiving), Frame Relay STAC compression (virtual circuit), bundle DDR dynamic route backup, Frame Relay subinterface, DDR, 165, 168, 185...
Page 261 L2TP LNS LCP renegotiation, PPPoE server, 45, 54 L2TP LNS mandatory CHAP authentication, PPPoE server IP address assignment (local DHCP server), L2TP LNS user authentication, PPPoE server IP address assignment (RADIUS-based), L2TP optional parameters, PPPoE server IP address assignment (remote L2TP tunnel (client-initiated), DHCP server), L2TP tunnel (LAC-auto-initiated),...
Page 262 comparison of traditional+bundle DDR, traditional DDR interface call (receiving), configuration, 165, 168, 185 traditional DDR interface call (sending), dial rule+interface association, troubleshoot, dial-up interface assignment to dynamic route troubleshoot dialup connection failure, backup group, troubleshoot remote end ping failure, dialup interface attribute configuration, type, dialup interface link layer/network/routing delaying...
Page 263 DDR PPP callback (Windows DHCP server-to-router), 4G modem Eth-channel interface IP address, DDR secondary link disconnect delay, PPP IPCPv6 negotiation (IPv6), Frame Relay configuration, 221, 226, 235 PPPoE server IP address assignment (local DHCP server), Frame Relay DCE-side configuration, Frame Relay DTE-side configuration, PPPoE server IP address assignment (remote DHCP server), HDLC configuration,...
Page 264 bundle DDR dynamic route backup, ATM PVC transmission priority configuration, DDR dial-up interface assignment to dynamic PPPoE configuration, 44, 54 route backup group, PPPoE server configuration, DDR dynamic route backup, DDR dynamic route backup (multiple flag networks), ATM cell CLP flag value, DDR dynamic route backup group, flow DDR dynamic route backup warm-up timer,...
Page 265 STAC compression configuration, link bundling basic concepts, STAC compression configuration (virtual link bundling display, circuit), link bundling load balancing mode, STAC compression configuration restrictions, link bundling maintain, link bundling member interface state, subinterface configuration, link bundlingconfiguration, 96, 102 troubleshoot, link status polling, troubleshoot link layer protocol down, maintain, troubleshoot peer cannot be pinged,...
Page 266 L2TP LAC source IP address configuration, B-channel selection, PPP IP address negotiation, 10, 32 BRI interface leased line service configuration, PPP IPCP IP segment match enable, bundle DDR configuration (ISDN-based), PPP negotiation, called number verification, PPP negotiation (DNS server IP address), calling number identification, PPPoE configuration, 44, 54...
Page 267 encapsulation structure, L2TP LAC-auto-initiated tunneling, features, L2TP LNS LAC tunneling request acceptance, hello interval configuration, L2TP network component, LAC AAA authentication, L2TP source IP address configuration, LAC automatic tunnel establishment, L2TP tunnel configuration (LAC-auto-initiated), LAC configuration, Layer 2 LAC source IP address configuration, tunneling protocol.
Page 268 Frame Relay protocol, Frame Relay IPv6 address mapping configuration (dynamic), how it works, Frame Relay mapping configuration (static message type, address-to-DLCI map), negotiation parameter, matching PPP IPCP IP segment match enable, AAA authentication, member configuration, HDLC link bundling member interface, IMSI/SN binding authentication, 81, 81 HDLC link bundling member interface state,...
Page 269 services on user line, PPP negotiation (DNS server IP address), troubleshoot modem faults, PPP negotiation (PFC), monitoring network 3G/4G modem DM, 3G modem cellular interface, 3G/4G modem RSSI threshold, 3G modem management, 153, 162 PPP link quality monitoring, 3G/4G network configuration, PPPoE monitoring table, 4G modem cellular interface, 4G modem Eth-channel interface,...
Page 270 DDR physical interface configuration, ISDN Q.921 PRI interface sliding window size, DDR PPP callback (router-to-PC), ISDN Q.931 call control parameter configuration, DDR PPP callback (router-to-router), DDR type, ISDN Q.931 negotiation parameter configuration, Frame Relay address mapping configuration, ISDN switch type, Frame Relay DCE-side configuration, L2TP AVP data transfer in hidden mode, Frame Relay DTE-side configuration,...
Page 271 PPP IP address negotiation configuration, PPP IPCP negotiation (IPv4), ATM, PPP IPCPv6 negotiation (IPv6), ATM configuration, 123, 127, 138 PPP link establishment process, ATM IPoA configuration, PPP link quality monitoring, ATM IPoEoA configuration, PPPoE client configuration, ATM OAM functions, PPPoE client configuration (diagnostic mode), ATM PPPoA configuration, ATM PPPoEoA configuration, PPPoE client configuration (on-demand...
Page 272 ISDN Q.921 BRI interface data link type ATM VP policing, configuration, polling ISDN Q.921 BRI interface line power, HDLC link status polling, ISDN Q.921 BRI interface link connectivity, PPP polling, pool ISDN Q.921 BRI interface per-channel TEI L2TP VA pool configuration, assignment, PPPoE VA pool configuration, ISDN Q.921 BRI interface persistent Layer 1...
Page 273 IPHC enable, client display, L2TP configuration, 67, 73, 85 client LAN connection configuration (ADSL modem), L2TP packet DSCP value, client maintain, L2TP tunnel configuration (client-initiated), client session configuration, L2TP tunnel configuration (LAC-auto-initiated), configuration, 44, 54 DDR dialer interface configuration, L2TP tunnel configuration (NAS-initiated), display, link establishment process, maintain,...
Page 274 configuring 3G/4G modem reboot (automatic), configuring DDR dialup interface attribute, configuring DDR dialup interface link layer configuring 3G/4G modem reboot (manual), protocols, configuring DDR dialup interface network configuring 3G/4G modem RSSI threshold, protocols, configuring DDR dialup interface routing configuring 3G/4G network, protocols, configuring 4G modem cellular interface, configuring DDR dynamic route backup,...
Page 275 configuring Frame Relay subinterface, configuring L2TP IMSI/SN binding authentication on the LNS, configuring HDLC, configuring L2TP LAC, configuring HDLC link bundle interface, configuring L2TP LAC AAA authentication, configuring HDLC link bundling, configuring L2TP LAC automatic tunnel configuring HDLC link status polling, establishment, configuring ISDN, configuring L2TP LAC tunnel request initiation,...
Page 276 configuring PPP negotiation (DNS server IP displaying L2TP, address), displaying MP, configuring PPP negotiation (PFC), displaying Multilink Frame Relay (MFR), configuring PPP negotiation timeout time, displaying PPP, configuring PPP PAP authentication, displaying PPPoE, configuring PPP polling, displaying PPPoE client, configuring PPPoE access rate limit, displaying PPPoE server, configuring PPPoE client, enabling Frame Relay SNMP notification,...
Page 277 specifying L2TP IP addresses, ISDN Q.921 BRI interface data link type configuration, troubleshooting 3G/4G modem, 163, 163 ISDN Q.921 BRI interface line power, troubleshooting ATM IPoA link state error, ISDN Q.921 BRI interface link connectivity, troubleshooting ATM ping failure, ISDN Q.921 BRI interface per-channel TEI troubleshooting ATM ping failure after PPPoA assignment, configuration,...
Page 278 DDR MP configuration, DDR PPP callback (Windows server-to-router), Frame Relay IPHC configuration, L2TP basic configuration, Frame Relay local virtual circuit configuration, L2TP configuration, 67, 73, 85 L2TP LAC configuration, Frame Relay STAC compression configuration, L2TP LNS configuration, Frame RelayFRF.12 fragmentation L2TP tunnel configuration (client-initiated), configuration, L2TP tunnel configuration (LAC-auto-initiated),...
Page 279 L2TP session, static L2TP session flow control, Frame Relay address mapping, PPPoE access rate limit, Frame Relay mapping configuration (static address-to-DLCI map), PPPoE client DDR session reset, status PPPoE client session configuration, HDLC link status polling, PPPoE session clear, subinterface PPPoE session configuration, Frame Relay configuration, PPPoE session max,...
Page 280 bundle DDR configuration (PSTN-based), DDR (route-triggered), troubleshooting bundle DDR dynamic route backup, DDR basic configuration, 3G/4G modem abnormal status, DDR callback (Windows server-to-router), ATM, ATM IPoA link state error, DDR circular dial string backup+Internet access, ATM ping failure, DDR configuration, 165, 168, 185 ATM ping failure after PPPoA configuration, DDR dial rule+interface association,...
Page 281 type WAN access 3G modem cellular interface, ISDN switch, 3G modem management, 153, 162 3G/4G modem backup profile, 3G/4G modem configuration directive, ATM service type, 3G/4G modem DM configuration, 3G/4G modem management, 153, 162 Frame Relay interface type, 3G/4G modem parameter profile, user-to-network interface.
Page 282 DDR basic configuration, HDLC link bundling maintain, DDR callback (Windows server-to-router), HDLC link status polling, DDR circular dial string backup+Internet HDLC maintain, access, ISDN application scenario, DDR configuration, 165, 168, 185 ISDN configuration, 104, 106, 118 DDR configuration (auto-dial), ISDN interface functionality, DDR dial rule+interface association, ISDN interfaces, DDR dial-up interface assignment to dynamic...
Page 283 PPP IPCPv6 negotiation (IPv6), troubleshooting Frame Relay physical layer down, PPP maintain, troubleshooting ISDN devices cannot ping each PPP negotiation configuration, other, PPP polling configuration, troubleshooting L2TP, PPP RADIUS NAS-Port-Type attribute, troubleshooting L2TP data transmission failure, PPPoE client configuration (diagnostic mode), troubleshooting L2TP remote system network PPPoE client configuration (on-demand access failure,...

HPE FlexNetwork MSR series Configuration Manual

Configuring PPP and

Configuring Pppoe

Configuring L2TP

Configuring HDLC

Configuring HDLC Link Bundling

Configuring ISDN

Configuring ATM

Managing a Modem

Managing a 3G/4G Modem

Configuring DDR

Configuring Frame Relay

Quick Links

Configuration Guide

Troubleshooting

Need help?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for HPE FlexNetwork MSR series

Summary of Contents for HPE FlexNetwork MSR series