Page 1
HP MSR Router Series Layer 2 - WAN Access Configuration Guide(V7) Part number: 5998-7721b Software version: CMW710-R0304 Document version: 6PW104-20150914...
Page 2
The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an...
Contents Configuring PPP and MP ············································································································································· 1 PPP overview ······································································································································································ 1 PPP link establishment process ································································································································ 1 PPP authentication ···················································································································································· 2 PPP for IPv4 ······························································································································································· 3 PPP for IPv6 ······························································································································································· 3 MP overview ······································································································································································ 4 ...
Page 4
Resetting a PPPoE session ····································································································································· 53 Displaying and maintaining PPPoE ······························································································································ 54 Displaying and maintaining PPPoE server ·········································································································· 54 Displaying and maintaining PPPoE client ··········································································································· 54 PPPoE configuration examples ······································································································································ 55 PPPoE server configuration example ··················································································································· 55 ...
Page 5
Configuring HDLC ······················································································································································ 96 Overview ········································································································································································· 96 Command and hardware compatibility ······················································································································ 96 Enabling HDLC encapsulation on an interface ··········································································································· 96 Configuring link status polling ······································································································································ 97 Displaying and maintaining HDLC ······························································································································· 97 HDLC configuration example ········································································································································ 98 ...
Page 6
Configuring the sliding window size on an ISDN BRI interface ···································································· 122 Configuring the sliding window size on an ISDN PRI interface ····································································· 123 Displaying and maintaining ISDN settings ················································································································ 123 ISDN configuration examples ····································································································································· 124 ISDN PRI configuration example ·······················································································································...
Page 7
Modem management configuration example ··········································································································· 157 Network requirements ········································································································································· 157 Configuration procedure ···································································································································· 157 Verifying the configuration ································································································································· 158 Troubleshooting modem faults ···································································································································· 159 Managing a 3G/4G modem ································································································································ 160 Configuration restrictions and guidelines ·················································································································· 160 ...
Page 8
Configuring PPP callback ············································································································································ 185 Configuring the callback client ·························································································································· 186 Configuring the callback server ························································································································· 187 Configuring ISDN caller number callback ················································································································ 188 Overview ······························································································································································ 188 Configuration restrictions and guidelines ········································································································· 189 Configuring a callback server by using traditional DDR ················································································· 189 ...
Page 9
Network requirements ········································································································································· 250 Configuration procedure ···································································································································· 251 Verifying the configuration ································································································································· 252 Support and other resources ·································································································································· 253 Contacting HP ······························································································································································ 253 Subscription service ············································································································································ 253 Related information ······················································································································································ 253 Documents ···························································································································································· 253 ...
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. •...
ID by using the MD5 algorithm. It is more secure than PAP. The authenticator may or may not be configured with a username. HP recommends that you configure a username for the authenticator, which makes it easier for the peer to verify the identity of the authenticator.
MS-CHAP-V2 supports password change. If the peer fails authentication because of an expired password, it will send the new password entered by the user to the authenticator for reauthentication. PPP for IPv4 On IPv4 networks, PPP negotiates the IP address and DNS server address during IPCP negotiation. IP address negotiation IP address negotiation enables one end to assign an IP address to the other.
MP is available to all physical or virtual interfaces with PPP encapsulation enabled, including serial, ISDN BRI/PRI, and PPPoX (PPPoE, PPPoA, or PPPoFR) interfaces. In MP configuration, however, HP recommends that you include only one type of interfaces in an MP bundle.
Command and hardware compatibility Commands and descriptions for centralized devices apply to the following routers: • MSR1002-4/1003-8S. MSR2003. • MSR2004-24/2004-48. • MSR3012/3024/3044/3064. • Commands and descriptions for distributed devices apply to MSR4060 and MSR4080 routers. Configuring PPP PPP configuration task list Tasks at a glance (Required.) Enabling PPP encapsulation on an interface...
Page 15
Configuring PAP authentication To configure the authenticator: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Configure the authenticator to ppp authentication-mode pap By default, PPP authentication is authenticate the peer by using [ [ call-in ] domain isp-name ] disabled.
Page 16
Step Command Remarks Configure the authenticator ppp authentication-mode chap By default, PPP authentication is to authenticate the peer by [ [ call-in ] domain isp-name ] disabled. using CHAP. The default setting is null. The username you configure for Configure a username for the authenticator must be the ppp chap user username the CHAP authenticator.
Page 17
Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number Configure the authenticator to ppp authentication-mode chap By default, PPP authenticate the peer by using [ [ call-in ] domain isp-name ] authentication is disabled. CHAP. For local AAA authentication, the username and password of the peer must be configured on the The username configured...
Step Command Remarks interface interface-type Enter interface view. interface-number Configure the authenticator to ppp authentication-mode By default, PPP authentication is authenticate the peer by using { ms-chap | ms-chap-v2 } disabled. MS-CHAP or MS-CHAP-V2. [ [ call-in ] domain isp-name ] Configure a username for the The username for the authenticator MS-CHAP or MS-CHAP-V2...
To set the keepalive retry limit, use the timer-hold retry command. On a slow link, increase the keepalive interval to prevent false shutdown of the interface. This situation might occur when keepalives are delayed because a large packet is being transmitted on the link. To disable sending of keepalives, set the keepalive interval to 0.
Page 20
Step Command Remarks interface interface-type Enter interface view. interface-number By default, IP address negotiation is not enabled. This command is mutually Enable IP address exclusive with the ip address ip address ppp-negotiate negotiation. command. For more information about the ip address command, see Layer 3—IP Services Command Reference.
Page 21
Step Command Remarks By default, no PPP address pool ppp ip-pool route ip-address route exists. { mask-length | mask } (Optional.) Configure a PPP [ vpn-instance vpn-instance-name ] The destination network of the address pool route. [ vsrp-instance PPP address pool route must vsrp-instance-name ] include the PPP address pool.
Page 22
Step Command Remarks Enter system view. system-view ip pool pool-name start-ip-address By default, no PPP address pool Configure a PPP address pool. [ end-ip-address ] [ group is configured. group-name ] (Optional.) Configure a ip pool pool-name gateway By default, the PPP address pool gateway address for the PPP ip-address [ vpn-instance is not configured with a gateway...
Page 23
Step Command Remarks By default, no DHCP address pool is associated. Associate the ISP domain with authorization-attribute ip-pool the configured DHCP address For more information about this pool-name pool for address assignment. command, see Security Command Reference. Return to system view. quit interface interface-type Enter interface view.
Page 24
Step Command Remarks By default, a device does not accept the DNS server IP Configure the device to addresses assigned by the peer accept the DNS server IP if it does not request the peer for addresses assigned by the ppp ipcp dns admit-any the DNS server IP addresses.
Page 25
PPP does not include the address and control fields in non-LCP packets. To ensure successful LCP negotiation, PPP does not apply the compression to LCP packets. HP recommends that you use the ACFC configuration option on low-speed links. To configure the local end to send ACFC requests:...
To ensure successful LCP negotiation, PPP does not apply the compression to LCP packets. HP recommends that you use this configuration option on low-speed links. To configure the local end to send PFC requests:...
Typically, there is no need to enable PPP LQM on both sides of a PPP link. HP recommends not enabling PPP LQM on a DDR dial-up link because DDR tears the link down when the link is closed by LQM. Then LQM cannot send LQR packets to resume the link.
Step Command Remarks Enter system view. system-view Enter interface view. interface interface-type interface-number ppp lqm close-percentage By default, PPP LQM is Enable PPP LQM. close-percentage [ resume-percentage disabled. resume-percentage ] Configure the interface to By default, the interface does periodically send LCP echo ppp lqm lcp-echo [ packet size ] not send LCP echo packets packets when LQM detects a...
Table 1 Default nas-port-type attribute Nas-port-type Service type Link type attribute Layer 3 virtual Ethernet interface xdsl PPPoE Other interfaces ethernet PPPoA xdsl L2TP virtual Configuring MP The device does not support MP binding for interfaces on different SPUs. You can configure MP by using virtual template (VT) or MP-group interfaces: VT interfaces—VT interfaces are used to configure VA interfaces.
Configuring MP by using a VT interface You can use either of the following methods to configure MP by using a VT interface: • Bind physical interfaces to the VT interface by using the ppp mp virtual-template command. If authentication is not configured, the system binds links according to the descriptor of the peer. If authentication is configured, the system binds links according to the username, the descriptor of the peer, or both.
Page 31
Step Command Remarks • Distributed devices in standalone mode/centralized devices in IRF mode: (Optional.) Specify a backup By default, no backup traffic service standby slot slot-number traffic processing unit for the VA processing unit is specified. interfaces of the VT interface. •...
Step Command Remarks By default, both the username ppp mp binding-mode Set the binding mode. and the descriptor are used for { authentication | both | descriptor } MP binding. (Optional.) Set the maximum number of links in an MP ppp mp max-bind max-bind-num The default setting is 16.
Step Command Remarks (Optional.) Start the timer for ppp mp timer lost-fragment waiting for the expected By default, the timer is not started. seconds fragment. By default, MP fragmentation is enabled. After you configure this command (Optional.) Disable MP on an interface, the settings ppp mp fragment disable fragmentation.
To negotiate the use of short sequence numbers on a dialer MP bundle, configure the command on the dialer interfaces and the ISDN D channels. To negotiate the use of short sequence numbers on a common MP bundle, use the command on all its channels. Note that the command will cause PPP re-negotiation.
Fragments the large packets into small fragments. • • Adds the fragments to the queues along with the voice packets. Figure 2 LFI Fragmentation Large packet Output queue Traffic Voice packet classifying To configure LFI: Step Command Remarks Enter system view. system-view interface { dialer | mp-group Enter VT interface, MP-group...
Task Command display interface [ virtual-template [ interface-number ] ] Display information about VT interfaces. [ brief [ description | down ] ] Display information about VA interfaces on a display interface [ virtual-access [ interface-number ] ] [ brief VT interface.
Page 37
[RouterA-Serial2/1/0] ppp authentication-mode pap domain system # Assign an IP address to Serial 2/1/0. [RouterA-Serial2/1/0] ip address 200.1.1.1 16 [RouterA-Serial2/1/0] quit # Configure local authentication for the PPP users in the default ISP domain system. [RouterA] domain system [RouterA-isp-system] authentication ppp local Configure Router B: # Enable PPP encapsulation on Serial 2/1/0 (optional, because an interface uses PPP encapsulation by default).
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 4, configure Router A and Router B to authenticate each other. Figure 4 Network diagram Configuration procedure Configure Router A: # Create a user account for Router B.
Page 39
[RouterB-luser-network-usera] service-type ppp [RouterB-luser-network-usera] quit # Enable PPP encapsulation on Serial 2/1/0 (optional, as an interface uses PPP encapsulation by default). [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.
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 Configuration procedure (Method 1) The authenticator configured with a username authenticates the peer by using CHAP. Configure Router A: # Create a user account for Router B.
Page 41
# Enable PPP encapsulation on Serial 2/1/0 (optional, as an interface uses PPP encapsulation by default). [RouterB] interface serial 2/1/0 [RouterB-Serial2/1/0] link-protocol ppp # 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.
Internet Address: 200.1.1.2/16 Primary Link layer protocol: PPP LCP opened, IPCP opened 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.
Page 43
Verify the configuration: # Display summary information about Serial 2/1/0 on Router B. [RouterB-Serial2/1/0] display interface serial 2/1/0 brief Brief information on interface(s) under route mode: Link: ADM - administratively down; Stby - standby Protocol: (s) - spoofing Interface Link Protocol Main IP Description S2/1/0 200.1.1.10...
Page 44
Enable IP address negotiation on Serial 2/1/0 of Router B. <RouterB> system-view [RouterB] interface serial 2/1/0 [RouterB-Serial2/1/0] ip address ppp-negotiate Verify the configuration: # Display summary information about Serial 2/1/0 on Router B. [RouterB-Serial2/1/0] display interface serial 2/1/0 brief Brief information on interface(s) under route mode: Link: ADM - administratively down;...
Page 45
Configure Router A: # Configure PPP address pool aaa that contains IP addresses 200.1.1.10 through 200.1.1.20 for the group AAA. <RouterA> system-view [RouterA] ip pool aaa 200.1.1.10 200.1.1.20 group AAA # Configure a PPP address pool route. [RouterA] ppp ip-pool route 200.1.1.1 24 # Create a local user for Router B.
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 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 # Display the address pools on Serial 2/1/0 of Router A.
Page 47
# 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 HP Peer's endPoint descriptor: HP Sequence format: long (rcv)/long (sent) Bundle Up Time: 2013/01/10...
Page 53
Serial2/1/1 Up-Time:2012/11/04 09:03:16:613 Serial2/1/0 Up-Time:2012/11/04 09:03:42:945 # Display information about interface MP-group 1 on Router A. [RouterA] display interface mp-group 1 MP-group1 Current state: UP Line protocol state: UP Description: MP-group1 Interface Bandwidth: 2048kbps Maximum Transmit Unit: 1500 Hold timer: 10 seconds, retry times: 5 Internet Address is 1.1.1.1/24 Primary Link layer protocol: PPP LCP: opened, MP: opened, IPCP: opened...
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.
As shown in Figure 1 1, a PPPoE session is established between each host (PPPoE client) and the • carrier router (PPPoE server). The service provider assigns an account to each host for billing and control. The host must be installed with PPPoE client software. Figure 11 Network structure 2 PPPoE Client Host A...
(AC) name pppoe-server tag ac-name name PPPoE server according to the for the PPPoE server. AC name. The PPPoE client on HP devices do not support this feature. (Optional.) Enable the PPPoE server to support the pppoe-server tag ppp-max-payload...
To configure the maximum number of PPPoE sessions: Step Command Remarks Enter system view. system-view Enter Layer 3 Ethernet interface/subinterface, Layer 3 virtual Ethernet interface/subinterface, Layer 3 aggregate interface interface-type The PPPoE server is enabled on the interface/subinterface, interface-number interface. VE-L3VPN interface/subinterface, or EFM interface/subinterface...
time of monitoring entries is determined by the session-request-period argument. When the timer expires, the system starts a new round of monitoring for the user. Blocking table—Stores a maximum of 8000 blocking entries. The system creates a blocking entry • if the access rate of a user reaches the threshold, and blocks requests from that user.
To configure the nas-port-id attribute: Step Command Remarks Enter system view. system-view Enter Layer 3 Ethernet interface/subinterface, Layer 3 virtual Ethernet interface/subinterface, Layer 3 aggregate interface interface-type The PPPoE server is enabled on the interface/subinterface, interface-number interface. VE-L3VPN interface/subinterface, or EFM interface/subinterface view.
Creating or removing a VA pool takes time. During the process of creating or removing a VA pool, • users can go online or offline, but the VA pool does not take effect. The system might create a VA pool that contains VA interfaces less than the specified number •...
Permanent mode—Used when you set the link idle time to 0 by using the dialer timer idle command • and do not configure the dialer diagnose command. On-demand mode—Used when you set the link idle time to a non-zero value by using the dialer •...
Set the auto-dial interval. dialer timer autodial autodial-interval new call when the auto-dial timer expires. HP recommends that you set a shorter auto-dial interval for DDR to soon originate a new call. By default, the MTU on a dialer interface is 1500 bytes.
After you reset a PPPoE session in on-demand mode, the device establishes a new PPPoE session when there is a demand for data transmission. To reset a PPPoE session: Step Command Remarks reset pppoe-client { all | Reset a PPPoE session. Available in user view.
Task Command Display summary information for a PPPoE display pppoe-client session summary [ dial-bundle-number session. number ] Display the protocol packet statistics for a PPPoE display pppoe-client session packet [ dial-bundle-number session. number ] Clear the protocol packet statistics for a PPPoE reset pppoe-client session packet [ dial-bundle-number session.
# Enable the PPPoE server on GigabitEthernet 1/0/1, and bind the interface to Virtual-Template 1. [Router] interface gigabitethernet 1/0/1 [Router-GigabitEthernet1/0/1] pppoe-server bind virtual-template 1 [Router-GigabitEthernet1/0/1] quit # Configure local authentication for the default ISP domain system. [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 the username user1 and password pass1.
[Router-dhcp-pool-pool1] quit # Create a PPPoE user. [Router] local-user user1 class network [Router-luser-network-user1] password simple pass1 [Router-luser-network-user1] service-type ppp [Router-luser-network-user1] quit Verifying the configuration # Log in to the router by using username user1 and password pass1. # Display information about IP addresses assigned by the DHCP server. [Router] display dhcp server ip-in-use IP address Client identifier/...
Page 67
[RouterA-GigabitEthernet1/0/1] pppoe-server bind virtual-template 10 [RouterA-GigabitEthernet1/0/1] quit # Enable DHCP. [RouterA] dhcp enable # Enable recording of relay entries on the relay agent. [RouterA] dhcp relay client-information record # Create a DHCP relay address pool pool1. [RouterA] dhcp server ip-pool pool1 # Specify a gateway address for the clients in pool1.
IP address MAC address Type Interface VPN name 2.2.2.3 00e0-0000-0001 Dynamic # Display information about the assigned IP addresses on Router B. [RouterB] display dhcp server ip-in-use IP address Client identifier/ Lease expiration Type Hardware address 2.2.2.3 00e0-0000-0001 May 1 14:02:49 2009 Auto(C) The output shows that Router B has assigned an IP address to the host.
[Router-luser-network-user1] service-type ppp [Router-luser-network-user1] quit # Configure an IPv6 prefix authorized to the user in the ISP domain. [Router] domain system [Router-isp-system] authorization-attribute ipv6-prefix 2003:: 64 [Router-isp-system] quit Verifying the configuration # Display PPP user information on GigabitEthernet 1/0/1. [Router] display ppp access-user interface gigabitethernet 1/0/1 Interface Username MAC address...
[Router-GigabitEthernet1/0/1] quit # Configure DHCPv6 address pool 1 with network 3001::/32. [Router] ipv6 dhcp pool pool1 [Router-dhcp6-pool-pool1] network 3001::/32 [Router-dhcp6-pool-pool1] quit # Configure a PPPoE user. [Router] local-user user1 class network [Router-luser-network-user1] password simple pass1 [Router-luser-network-user1] service-type ppp [Router-luser-network-user1] quit # Configure an IPv6 pool attribute authorized to the user in the ISP domain.
# Enable the DHCPv6 server feature. [RouterB-Virtual-Template10] ipv6 dhcp select server [RouterB-Virtual-Template10] quit # Enable the PPPoE sever on GigabitEthernet 1/0/1, and bind the interface to interface Virtual-Template [RouterB] interface gigabitethernet 1/0/1 [RouterB-GigabitEthernet1/0/1] pppoe-server bind virtual-template 10 [RouterB-GigabitEthernet1/0/1] quit # Create prefix pool 6, and specify prefix 4001::/32 with assigned prefix length 42. [RouterB] ipv6 dhcp prefix-pool 6 prefix 4001::/32 assign-len 42 # Create address pool 1, and apply prefix pool 6 to address pool 1.
Page 72
Configuration procedure Configure Router A as the PPPoE server: # Configure an IP address for interface Virtual-Template 1 and specify an IP address for the peer. <RouterA> system-view [RouterA] interface virtual-template 1 [RouterA-Virtual-Template1] ip address 1.1.1.1 255.0.0.0 [RouterA-Virtual-Template1] remote address 1.1.1.2 [RouterA-Virtual-Template1] quit # Enable the PPPoE server on GigabitEthernet 1/0/1, and bind the interface to Virtual-Template 1.
PPPoE client in on-demand mode configuration example Network requirements As shown in Figure 19, Router A serves as a PPPoE server. Configure Router B as a PPPoE client operating in on-demand mode, and set the link idle-timeout timer to 150 seconds. Figure 19 Network diagram Configuration procedure Configure Router A as the PPPoE server:...
[RouterB-Dialer1] dialer timer idle 150 [RouterB-Dialer1] quit 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 State GE1/0/1 00e0-1400-4300 00e0-1500-4100 SESSION PPPoE client in diagnostic mode configuration example Network requirements As shown in...
# 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 the PPPoE session to operate in diagnostic mode, and set the diagnostic interval to 200 seconds.
Page 76
Figure 21 Network diagram Configuration procedure Configure Router A as a PPPoE client: # Create dialer access group 1 and configure a dial access control rule for it. <RouterA> system-view [RouterA] dialer-group 1 rule ip permit # Enable bundle DDR on interface Dialer 1. [RouterA] interface dialer 1 [RouterA-Dialer1] dialer bundle enable # Associate Dialer 1 with dialer access group 1.
Page 77
# Configure a default route. [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 78
Verifying the configuration # Display summary information for the PPPoE session between Router A and Router B. [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.
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.
L2TP message types and encapsulation structure L2TP uses the following types of messages: • 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 23.
Page 81
Figure 25 NAS-initiated tunneling mode A NAS-initiated tunnel has the following characteristics: 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 26 NAS-initiated tunnel establishment process As shown in Figure...
Page 82
The LAC sends the authentication information (username and password) to its RADIUS server (RADIUS server A) for authentication. RADIUS server A authenticates the user and returns the result. The LAC initiates an L2TP tunneling request to the LNS (Device B) when the following conditions exist: The user passes the authentication.
Page 83
A client-initiated tunnel has higher security because it is established between a remote system and • the LNS. The remote system must support L2TP and be able to communicate with the LNS. This causes poor • expandability. As shown in Figure 28, the workflow for establishing a client-initiated tunnel is similar to that for establishing a NAS-initiated tunnel.
The LNS assigns a private IP address to the LAC instead of to the remote system. • As shown in Figure 30, the workflow for establishing an LAC-auto-initiated tunnel is similar to that for establishing a NAS-initiated tunnel. (Details not shown.) Figure 30 Establishment process for LAC-auto-initiated tunnels L2TP features Flexible identity authentication mechanism and high security—L2TP by itself does not provide...
Page 85
Table 2 Tunnel attributes that can be issued by the RADIUS server Attribute number Attribute name Description Tunnel-Type Tunnel type, which can only be L2TP. Transmission medium type for the tunnel, which can Tunnel-Medium-Type only be IPv4. Tunnel-Server-Endpoint IP address of the LNS. Tunnel-Password Key used to authenticate a peer of the tunnel.
Protocols and standards RFC 1661, The Point-to-Point Protocol (PPP) • • RFC 1918, Address Allocation for Private Internets RFC 2661, Layer Two Tunneling Protocol "L2TP" • RFC 2868, RADIUS Attributes for Tunnel Protocol Support • Command and hardware compatibility Commands and descriptions for centralized devices apply to the following routers: MSR1002-4/1003-8S.
Tasks at a glance Remarks (Optional.) Configuring optional L2TP parameters: • Configuring L2TP tunnel authentication • Setting the Hello interval • Enabling session flow control • Setting the DSCP value of L2TP packets • Assigning a tunnel peer to a VPN •...
Step Command Remarks Enable L2TP. l2tp enable By default, L2TP is disabled. By default, no L2TP group exists. Create an L2TP group, specify l2tp-group group-number mode Specify the mode as lac on the LAC its mode, and enter its view. { lac | lns } side and as lns on the LNS side.
Configuring the source IP address of L2TP tunnel packets For high availability, HP recommends using the IP address of a loopback interface as the source IP address of L2TP tunnel packets on the LAC. To configure the source IP address of L2TP tunnel packets:...
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.
Step Command Remarks By default, the description of an interface is in the format of (Optional.) Set the description description text interface-name Interface, for for the interface. example, Virtual-PPP254 Interface. Set the MTU size of the mtu size The default setting is 1500 bytes. interface.
(VT) interface. To configure an LNS, first create a VT interface and configure the following parameters for Interface IP address. • Authentication mode for PPP users. • IP addresses allocated by the LNS to PPP users. • For information about configuring VT interfaces, see "Configuring PPP and MP" and Layer 3—IP Services Configuration Guide.
Step Command Remarks Enter system view. system-view Enter L2TP group view in LNS l2tp-group group-number [ mode mode. lns ] • If the L2TP group number is 1: allow l2tp virtual-template By default, an LNS denies virtual-template-number tunneling requests from any LAC. Configure the LNS to accept [ remote remote-name ] tunneling requests from a...
Step Command Remarks Enter system view. system-view Enter L2TP group view in LNS l2tp-group group-number [ mode mode. lns ] By default, CHAP authentication is not performed on an LNS. Configure mandatory CHAP mandatory-chap authentication. This command is effective only on NAS-initiated L2TP tunnels.
Configuring optional L2TP parameters The optional L2TP parameter configuration tasks apply to both LACs and LNSs. Configuring L2TP tunnel authentication Tunnel authentication allows the LAC and LNS to authenticate each other. Either the LAC or the LNS can initiate a tunnel authentication request. To implement tunnel authentication, enable tunnel authentication on both the LAC and LNS, and configure the same non-null key on them.
This feature takes effect on both sent and received L2TP data messages. The L2TP sessions support this feature if either the LAC or LNS is enabled with this feature. To enable session flow control: Step Command Remarks Enter system view. system-view l2tp-group group-number [ mode { lac Enter L2TP group view.
Step Command Remarks By default, a tunnel peer belongs to the public network. The tunnel peer and the physical port connecting to the tunnel peer Assign the tunnel peer to a vpn-instance vpn-instance-name should belong to the same VPN. VPN. The VPN to which this physical port belongs is configured by using the ip binding vpn-instance...
L2TP configuration examples Configuration example for NAS-initiated L2TP tunnel Network requirements As shown in Figure 32, a PPP user is connected to an LNS through an LAC. Set up an L2TP tunnel between the LAC and LNS to allow the PPP user to access the corporate network. Figure 32 Network diagram Configuration procedure Configure the LAC:...
Page 99
[LAC-l2tp1] tunnel password simple aabbcc [LAC-l2tp1] quit Configure the LNS: # Configure IP addresses for the interfaces. (Details not shown.) # Create a local user named vpdnuser, set the password, and enable the PPP service. <LNS> system-view [LNS] local-user vpdnuser class network [LNS-luser-network-vpdnuser] password simple Hello [LNS-luser-network-vpdnuser] service-type ppp [LNS-luser-network-vpdnuser] quit...
# On the LNS, use the display l2tp session command to check the established L2TP sessions. [LNS] display l2tp session LocalSID RemoteSID LocalTID State 2041 Established Configuration example for client-initiated L2TP tunnel Network requirements As shown in Figure 33, a PPP user directly initiates a tunneling request to the LNS to access the corporate network.
# Configure the local tunnel name as LNS. [LNS-l2tp1] tunnel name LNS # Specify Virtual-Template 1 for receiving calls. [LNS-l2tp1] allow l2tp virtual-template 1 # Disable tunnel authentication. [LNS-l2tp1] undo tunnel authentication Configure the remote host: # Configure the IP address of the remote host as 2.1.1.1, and configure a route to the LNS (1.1.2.2).
Page 102
# Configure IP addresses for the interfaces. (Details not shown.) # Create a local user named vpdnuser, set the password, and enable the PPP service. <LNS> system-view [LNS] local-user vpdnuser class network [LNS-luser-network-vpdnuser] password simple Hello [LNS-luser-network-vpdnuser] service-type ppp [LNS-luser-network-vpdnuser] quit # Configure PPP address pool.
[LAC-l2tp1] tunnel authentication [LAC-l2tp1] tunnel password simple aabbcc [LAC-l2tp1] quit # Create virtual PPP interface Virtual-PPP 1. Configure its username and password as vpdnuser and Hello and PPP authentication as PAP. [LAC] interface virtual-ppp 1 [LAC-Virtual-PPP1] ip address ppp-negotiate [LAC-Virtual-PPP1] ppp pap local-user vpdnuser password simple Hello [LAC-Virtual-PPP1] quit # Configure a static route so that packets destined for the corporate network will be forwarded through the L2TP tunnel.
Page 104
Analysis and solution Possible reasons for the access failure include the following: • Tunnel setup failure, which might occur in the following cases: The address of the LNS is set incorrectly on the LAC (see the lns-ip command). No L2TP group is configured on the LNS to receive tunneling requests from the tunnel peer (see the allow command).
Configuring HDLC This feature is supported only on routers installed with the following interface modules: CE3. • CPOS. • CT3. • • E1-F. • POS. • SAE. • • • T1-F. Overview High-level Data Link Control (HDLC) is a bit-oriented link layer protocol. HDLC can transmit any type of bit stream transparently.
When you configure link status polling, follows these restrictions and guidelines: Link status check is disabled if you set the keepalive interval to 0. • HP recommends that you set the same keepalive interval for the two ends of a link. • •...
Task Command Clear the statistics and restart reset counters interface [ serial [ interface-number ] ] statistics collection on reset counters interface [ pos [ interface-number ] ] interfaces. HDLC configuration example Network requirements As shown in Figure 35, Router A and Router B are connected by POS interfaces. Run HDLC on the link between them.
Page 108
Ping 12.1.1.2 (12.1.1.2): 56 data bytes, press CTRL_C to break 56 bytes from 12.1.1.2: icmp_seq=0 ttl=254 time=2.137 ms 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...
Configuring HDLC link bundling This feature is supported only on routers installed with the following interface modules: CE3. • CPOS. • CT3. • • E1-F. • POS. • SAE. • • • T1-F. Overview HDLC link bundling bundles multiple interfaces using HDLC encapsulation (also known as HDLC interfaces) together to form one logical link.
After an interface is assigned to an HDLC link bundle, it is placed in the down state at the network layer. Layer 3 service configurations on the interface do not take effect. The interface processes services based on the Layer 3 service configurations of the HDLC link bundle interface. States of member interfaces An HDLC link bundle member interface can be in one of the following states: Initial—The member interface is down at the link layer.
The first N member interfaces enter the Selected state, and the remaining (M-N) member interfaces enter the Ready state. For example, the number of member interfaces meeting the conditions for being Selected is P. The minimum number of Selected interfaces required for bringing up the HDLC link bundle is set to Q. The P interfaces will be Selected when any of the following conditions exist: P is not smaller than Q.
Maximum number of Selected interfaces allowed in the HDLC link bundle. Minimum bandwidth required for bringing up the HDLC link bundle. HP recommends that you set the same load balancing mode at both ends of an HDLC link bundle. •...
Page 113
Step Command Remarks (Optional.) Specify a backup traffic processing card for the By default, no backup traffic HDLC link bundle interface. service standby slot slot-number processing card for the HDLC link (Distributed devices in bundle interface is specified. standalone mode.) (Optional.) Specify a backup traffic processing device for By default, no backup traffic...
HDLC link bundle. A HDLC link bundle ID is locally significant. The ID on the peer device can be different from the local one. HP recommends that you use the bundle member-priority command and the bundle max-active •...
Step Command Remarks Assign the interface to an By default, an interface is not bundle id bundle-id HDLC link bundle. assigned to any HDLC link bundle. Set the bundling priority for bundle member-priority priority The default setting is 32768. the member interface. Displaying and maintaining HDLC link bundling Execute display commands in any view and reset commands in user view.
Configuration procedure Configuring Router A # Create HDLC link bundle interface 1 and assign an IP address to it. <RouterA> system-view [RouterA] interface hdlc-bundle 1 [RouterA-HDLC-bundle1] ip address 1.1.1.1 24 [RouterA-HDLC-bundle1] quit # Assign POS interfaces POS 2/2/1 to HDLC link bundle 1, and configure the interface to use the master clock mode.
Page 117
56 bytes from 1.1.1.2: icmp_seq=1 ttl=255 time=0.000 ms 56 bytes from 1.1.1.2: icmp_seq=2 ttl=255 time=0.000 ms 56 bytes from 1.1.1.2: icmp_seq=3 ttl=255 time=0.000 ms 56 bytes from 1.1.1.2: icmp_seq=4 ttl=255 time=0.000 ms --- Ping statistics for 1.1.1.2 --- 5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss round-trip min/avg/max/std-dev = 0.000/0.000/0.000/0.000 ms # Verify that: POS 2/2/1 and POS 2/2/2 are in Selected state and can perform load balancing.
Configuring ISDN 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. It enables a single pair of telephone wires to transmit data and voice simultaneously at high rates.
Item CE1 PRI (30B + D) CT1 PRI (23B + D) • North America (including USA and Canada) • Most Asia countries (including China) Countries/areas • Hong Kong • Europe • Japan 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...
Figure 38 Data ISDN application scenario Figure 39 Voice ISDN application scenario Feature and hardware compatibility ISDN is supported only on the BS, E1, and T1 interface modules. 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.
NOTE: The device provides full support for DSS1. For any other variants of ISDN, the device only provides the basic call functionality. You cannot perform this task when a call is present on the ISDN interface. To set the service provider switch type on an ISDN interface: Step Command Remarks...
Configuring SPID parameters for the NI switch type NI service provider switches use service profile identifications (SPIDs) to identify services (audio, data, or speech) subscribed to by ISDN devices. The service provider assigns one SPID for each B-channel. The device cannot place or receive calls until it sends a valid SPID when it initializes a connection to the service provider switch.
To configure SPIDs on a BRI interface: Step Command Remarks Enter system view. system-view Enter ISDN BRI interface interface bri interface-number view. By default, no SPID or LDN is Assign a SPID to the B1 isdn spid1 spid [ ldn ] configured for the B1 channel on a channel.
You must enable Not Initial Terminal (NIT) mode on the BRI interface if the NI-type service provider switch does not support SPID negotiation. To enable NIT mode: Step Command Remarks Enter system view. system-view Enter ISDN BRI interface bri interface-number interface view.
Page 126
Step Command Remarks By default, all ISDN protocols except 5ESS and QSIG include the LLC information element in the SETUP message. (Optional.) Exclude the LLC The lower layer compatibility (LLC) information element from the isdn ignore llc element provides low layer outgoing SETUP message.
Configuring Q.931 call control parameters To ensure successful call setup, make sure the call control parameters match the service provider's settings. Configuring B-channel selection Efficient B-channel selection for calls improves call establishment efficiency and reduces call losses on ISDN lines, especially PRI ISDN lines. By default, ISDN interfaces on the device are operating as the user side, and they do not select B-channels for calls.
For the called party to receive the calling number, the connected service provider switch must support transmitting calling numbers. HP recommends that you do not configure the calling number to be sent for voice services. To configure calling number identification:...
Step Command Remarks Enter ISDN BRI or PRI interface interface-type interface-number interface view. By default, ISDN interfaces do not send a calling number Specify a calling number. isdn calling calling-number in outgoing SETUP messages for any services except voice services. Configuring the Q.921 operating parameters Except for the sliding window configuration, all the Q.921 operating parameter configuration tasks are available only on BRI interfaces.
request a TEI from the switch before the interface can establish a call on a B-channel. If per-channel TEI assignment is not configured, only one B-channel can be brought up. For example, you must configure per-channel TEI assignment when a BRI interface is connected to an ISDN NI compliant DMS- 1 00 switch in the North America.
For energy efficiency, a network-side ISDN interface typically deactivates the physical layer when the data link layer connection is disconnected. To maintain physical layer connectivity when the data link connection is lost, enable persistent Layer 1 activation. This function prevents Q.921 from sending deactivation requests to the physical layer.
When sending a frame, Q.921 checks the number of unacknowledged frames. For example, 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. If V(A) + k = V(S), the system stops sending frames. To configure the sliding window size on an ISDN BRI interface: Step Command...
[RouterA-Serial2/3/0:15] dialer route ip 202.38.154.2 8810154 [RouterA-Serial2/3/0:15] dialer-group 1 Configure Router B: # Bundle timeslots into a PRI set on the CE1/PRI interface E1 2/3/0. <RouterB> system-view [RouterB] controller e1 2/3/0 [RouterB-E1 2/3/0] pri-set [RouterB-E1 2/3/0] quit # Create dialer access group 1 to allow any IP packets to trigger a call setup. [RouterB] dialer-group 1 rule ip permit # Assign Serial 2/3/0:15 an IP address.
Page 135
Configure Router A: # Configure dialer-group 1 to allow any IP packets to trigger a call setup. <RouterA> system-view [RouterA] dialer-group 1 rule ip permit # Assign the interface BRI 2/4/0 an IP address. [RouterA] interface bri 2/4/0 [RouterA-Bri2/4/0] ip address 202.38.154.1 255.255.0.0 # Enable C-DDR on the interface, configure the route to Router B, and assign the interface to dialer-group 1.
Troubleshooting Symptom Two devices cannot ping each other over an ISDN PRI or BRI line. Analysis The following are typical ISDN call failure causes: • The ISDN interface is not configured or activated. The dial-up configuration is incorrect. • The line is not well connected. •...
Configuring ATM 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. As defined by the ITU-T, data is encapsulated in cells in ATM.
Figure 43 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.
ATM layer and upper-layer protocols. Four types of AAL are available: AAL1, AAL2, AAL3/4, and AAL5, each of which supports specific services provided in an ATM network. HP uses AAL5 for data communication services. ATM upper-layer protocols—Responsible for WAN interconnection, Layer 3 interconnection, and •...
ATM applications An ATM interface can implement IPoA, IPoEoA, PPPoA, and PPPoEoA to carry data encapsulated in IP, PPP, or Ethernet across an ATM network. 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.
OAM Alarm Indication Signal/Remote Defect Indication—The PVC goes down when specific • number of successive AIS/RDI alarm cells are received. The PVC comes up when no AIS/RDI alarm cells are received within the specified time. • OAM Continuity Check—OAM CC requires that one end of the PVC must be configured as the CC cell source and the other end as the CC cell sink.
Tasks at a glance Remarks (Optional.) Configuring ATM OAM functions Configuring an ATM interface Depending on the actual networking environment and system requirements, you might be required to modify certain parameters of ATM interfaces and subinterfaces. For more information about ATM interface configuration, see Interface Configuration Guide.
Step Command Remarks Enter system view. system-view Enter ATM interface view interface atm { interface-number | or ATM subinterface interface-number.subnumber } view. Create a PVC-group and By default, no PVC-group is pvc-group group-number enter PVC-group view. created. Create a PVC and enter pvc { pvc-name [ vpi/vci ] | vpi/vci } By default, no PVC is created.
Step Command Remarks • Set the service type to CBR and configure related parameters: service cbr output-pcr [ cdvt cdvt-value ] • Set the service type to UBR and configure related parameters: The default service type is UBR. service ubr output-pcr The newly configured service •...
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 Create a VE command to enter the VE interface view. interface virtual-ethernet interface and enter interface-number...
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: Static IP address mapping—Maps the IP address of the remote interface to the PVC or PVC-group.
Step Command Remarks • Enter PVC view: pvc { pvc-name [ vpi/vci ] | Enter PVC view or vpi/vci } PVC-group view. • Enter PVC-group view: pvc-group group-number Configure an IPoA mapping to enable the map ip { ip-address | default | By default, no mapping is configured.
Step Command Remarks By default, no mapping is configured. Configure an map bridge virtual-ethernet interface-number This command references the IPoEoA mapping. VE interface previously created. Configuring PPPoA When two routers are connected by using DSL interfaces through a dial-up connection, configure them as a PPPoA server and client.
Configuring PPPoEoA PPPoE uses the Client/Server model. It encapsulates PPP packets into Ethernet frames and provides point-to-point connection on Ethernet. Perform this task to enable a PVC or PVC-group to carry PPPoE and configure a PPPoE mapping for the PVC or PVC-group. To configure PPPoEoA: Step Command...
Configuring VP policing A VP is the collection of all PVCs with the same VPI value. VP policing is used to manage the maximum bandwidth of the VP, and monitor the traffic of the inbound and outbound directions of the VP on a physical interface.
Step Command Remarks Create a QoS policy and enter qos policy policy-name its view. Associate a traffic class with a By default, a traffic class is classifier classifier-name behavior traffic behavior in the QoS not associated with a behavior-name [ mode dcbx ] policy.
Step Command Remarks By default, the PVC goes down when the system receives successive Configure related oam ais-rdi up up-seconds down AIS/RDI alarm cells in one second. parameters for AIS/RDI down-seconds The PVC comes up when the system alarm cell detection. does not receive any AIS/RDI alarm cells in 3 seconds.
Page 154
The VPIs/VCIs of Router C are 0/60 and 0/61, connected to Router A and Router B, respectively. • All the PVCs on ATM interfaces of the three routers operate in IPoA application mode. Figure 46 Network diagram Configuration procedure Configure Router A: # Enter the view of interface ATM 2/4/0 and configure an IP address for it.
# Create PVCs, and enable them to carry IP. [RouterC-ATM2/4/0] pvc to_a 0/60 [RouterC-ATM2/4/0-pvc-to_a-0/60] map ip 202.38.160.1 [RouterC-ATM2/4/0-pvc-to_a-0/60] quit [RouterC-ATM2/4/0] pvc to_b 0/61 [RouterC-ATM2/4/0-pvc-to_b-0/61] map ip 202.38.160.2 Verifying the configuration # Use the ping command to verify that the three routers can ping each other successfully. (Details not shown.) IPoEoA configuration example Network requirements...
[RouterC-ATM2/4/0.1-pvc-to_adsl_a-0/60] map bridge virtual-ethernet 1 [RouterC-ATM2/4/0.1-pvc-to_adsl_a-0/60] quit [RouterC-ATM2/4/0.1] pvc to_adsl_b 0/61 [RouterC-ATM2/4/0.1-pvc-to_adsl_b-0/61] map bridge virtual-ethernet 1 Configure ADSL Router A: # Create a VE interface and configure an IP address for it. <RouterA> system-view [RouterA] interface virtual-ethernet 1 [RouterA-Virtual-Ethernet1] ip address 202.38.160.2 255.255.255.0 [RouterA-Virtual-Ethernet1] quit # Create a PVC and enable it to carry IPoE.
# Create dialer interface Dialer 1 and enable bundle DDR on the interface. [RouterA] interface dialer 1 [RouterA-Dialer1] dialer bundle enable # Assign interface Dialer 1 to dialer access group 1. [RouterA-Dialer1] dialer-group 1 # Configure the PPPoE client to operate in permanent online mode. [RouterA-Dialer1] dialer timer idle 0 # Set the auto-dial interval of DDR to 1 second.
Solution If IPoA is used, make sure the IP protocol address mapping is configured correctly. If the interfaces • of two routers are connected back-to-back, the local PVC mapped to the remote IP address must have the same VPI/VCI value as the remote PVC mapped to the local IP address. •...
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 modules or interfaces: AM interface modules. • ASE interface modules • •...
Step Command Remarks Enter system view. system-view 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 { aux | tty } first-num2 view.
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).
Step Command Remarks Enter system view. system-view Enter the TTY user line line { first-num1 [ last-num1 ] | tty first-num2 view of an AM [ last-num2 ] } interface. By default, a modem does not Enable the modem to modem caller-number resolve obtain the caller number when it obtain caller number.
Step Command Remarks One sendat command can issue one Issue an AT command to a AT command. To send multiple AT sendat at-string modem. commands to a modem, repeat the sendat command. Setting the country code of a modem CAUTION: This task disconnects the modem connection.
# Configure the asynchronous/synchronous serial interface Serial 2/1/0 to operate in asynchronous mode and protocol mode. [RouterA] interface serial 2/1/0 [RouterA-Serial2/1/0] physical-mode async [RouterA-Serial2/1/0] async-mode protocol # Assign the IP address 1.1.1.1/16 to Serial 2/1/0. [RouterA-Serial2/1/0] ip address 1.1.1.1 255.255.0.0 # Enable traditional DDR on Serial 2/1/0.
Troubleshooting modem faults Symptom An external modem is in an abnormal state. For example, the dial tone or busy tone keeps humming. Solution To resolve the issue: Execute the shutdown and undo shutdown commands on the physical interface connected to the modem.
Configuration restrictions and guidelines Follow these restrictions and guidelines when you configure 3G/4G modem management: Do not remove a USB 3G/4G modem while it is transmitting data. HP recommends that you • execute the shutdown command to shut down the USB 3G/4G modem before removing it.
Tasks at a glance (Optional.) Configuring PIN verification (Optional.) Configuring DM (Optional.) Issuing a configuration directive to a 3G/4G modem (Optional.) Configuring automatic reboot (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 a cellular interface for a 4G modem Step Command Remarks Enter system view. system-view Enter cellular interface view. controller cellular cellular-number By default, the description for a Configure a description for cellular interface is interface name description text the cellular interface. Interface, for example, Cellular 2/4/0 Interface.
Configuring an IP address for an Eth-channel interface of a 4G modem An Eth-channel interface can communicate with other devices only after it obtains an IP address. You can configure an IP address for an Eth-channel interface in the following ways: •...
Some 3G/4G modems can automatically access a mobile network. To manually specify a mobile network for a 3G modem, first search for available mobile networks. To configure a 3G/4G network: Step Command Remarks Enter system view. system-view Enter cellular interface view. controller cellular interface-number (Optional.) Search for plmn search...
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. The primary profile always has priority over the backup profile.
Step Command Remarks The default setting depends on the modem model. Enable PIN verification. pin verification enable [ pin ] Requirement for the current PIN varies by device model. By default, no PIN is configured on a device for 3G/4G modem Specify the PIN for pin verify { cipher ciphered-pin | verification.
To issue a configuration directive to a 3G/4G modem: Step Command Remarks Enter system view. system-view Enter cellular interface view. controller cellular interface-number Issue a configuration directive sendat at-string to the 3G/4G modem. Configuring automatic reboot The 3G modem might malfunction in an unstable 3G network or when the application environment changes.
Displaying and maintaining 3G/4G modem information Execute display commands in any view and the reset command in user view. Task Command Display the call connection information display cellular [ interface-number ] for the 3G/4G modem. Display information about a cellular display controller [ cellular [ interface-number ] ] interface.
[Router-Cellular2/4/0] quit # Assign an IP address to interface Serial 2/4/0:0. [Router] interface serial 2/4/0:0 [Router-Serial2/4/0:0] ip address 1.1.1.1 255.255.0.0 # Enable traditional DDR on interface Serial 2/4/0:0. [Router-Serial2/4/0:0] dialer circular enable # Associate interface Serial 2/4/0:0 with dialer group 1. [Router-Serial2/4/0:0] dialer-group 1 # Set the interval for DDR to make the next call attempt to 5 seconds.
To resolve the problem: Execute the shutdown command and the undo shutdown command on the cellular interface. If the 3G/4G modem still fails to function, execute the modem reboot command on the cellular interface. If the problem persists, contact HP Support.
Configuring DDR Overview As shown in Figure 54, 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 54 DDR communication process In addition to PSTN/ISDN, Ethernet and ATM use DDR to implement access control.
Page 181
Traditional DDR You can configure traditional DDR by using the following methods: • Configure DDR parameters directly on a physical interface. The router places or receives calls through the physical interface. The physical interface can correspond to one or more call destinations. This method applies when only one interface places or receives calls.
Figure 55 Relationships among physical interfaces, dialer interfaces, and call destinations Bundle DDR is simpler and more flexible than traditional DDR. Bundle DDR separates physical interface configuration and logical configuration for calls and allows one-to-many bindings between dial services and physical interfaces. A physical interface can serve multiple dial services. Figure 56 Relationships among physical interfaces, dialer interfaces, and call destinations DDR types Depending on how DDR calls are triggered, DDR includes packet-triggered DDR, auto-dial DDR, and...
For more information about interesting and uninteresting packets, see "Associating a dial rule with a dialup interface." Auto-dial DDR DDR automatically initiates a dialup connection to the remote end upon router startup without requiring a triggering packet. If the connection cannot be established, it will retry at certain intervals. The established connection will not disconnect due to timeout of the idle-timeout timer.
Tasks at a glance (Optional.) Configuring ISDN caller number callback (Optional.) Disconnecting a dialup link Auto-dial 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: •...
Tasks at a glance (Required.) Configuring dynamic route backup through DDR • Creating a dynamic route backup group • Assigning a dialup interface to a dynamic route backup group • Setting the delay for disconnecting a backup link • Setting the warm-up timer for dynamic route backup (Optional.) Disconnecting a dialup link Configuring basic settings for DDR...
Configuring traditional DDR For traditional DDR, you can configure PAP or CHAP authentication (see "Configuring PPP and MP"). HP recommends that you configure PAP or CHAP authentication for security purposes. When you configure PAP or CHAP authentication, follow these guidelines: •...
Configuring an interface to place calls To configure an interface to place calls, enable DDR and configure dial strings. When you configure an interface to place calls, follow these guidelines: To configure an interface to place calls to a single site, use the dialer number or dialer route •...
Step Command Remarks Return to system view. quit interface interface-type Enter physical interface view. interface-number By default, a physical interface does not belong to any dialer circular group. Assign the physical interface to the specified dialer circular dialer circular group number Make sure the number arguments group.
Step Command Remarks To receive calls from multiple remote sites, configure this dialer route ip next-hop-address (Optional.) Configure the command multiple times. [ mask network-mask-length ] interface to authenticate the [ vpn-instance vpn-instance-name ] You must specify the user hostname caller.
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 By default, bundle DDR is dialer bundle enable interface. disabled.
Step Command Remarks The device compares the remote username obtained in PPP authentication with the host names configured by using the dialer peer-name commands. Then, the device determines which dialer interface receives Configure the host name of the dialer peer-name username which call.
Step Command Remarks Enter system view. system-view interface interface-type Enter dialup interface view. interface-number By default, the timer is 120 Set the link idle-timeout timer. dialer timer idle idle [ in | in-out ] seconds, and only outgoing interesting packets reset this timer. Set the holddown timer.
When the percentage of the traffic rate on a link to bandwidth exceeds the defined load threshold, the system automatically brings up a second link and assigns the two links to an MP bundle. When the percentage of the traffic rate on these two links to bandwidth exceeds the defined load threshold, the system brings up a third link, and assigns it to the MP bundle, and so on.
HP recommends that you configure the dialer threshold, ppp mp max-bind, and ppp mp min-bind • commands on one end of the call. When the configured values are not the same on the two ends of the call, the following values take effect: The smaller threshold value.
To provide enough time for a server to call back, make sure the holddown timer on the client is at • least 10 seconds longer than that on the server. HP recommends setting the holddown timer to 5 seconds (the default) on the server and to 15 seconds on the client.
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 configured). Username for PPP authentication.
Configuring the callback server by using bundle DDR Step Command Remarks Enter system view. system-view Enter dialer interface view. interface dialer number Enable the interface to accept By default, an interface does not ppp callback server callback requests. accept callback requests. Configure the interface to determine the dial string for By default, callback is not...
To leave enough time for a server to call back, set the holddown timer on the client at least 10 seconds longer than the holddown timer on the server. HP recommends that you set this timer to 5 seconds (the default) on the server and to 15 seconds on the client.
Step Command Remarks 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. or to call back to the specified calling number. Configuring auto-dial Auto-dial can be used with traditional DDR or bundle DDR.
If a minimum of one valid route exists with an egress interface that is not assigned to the dynamic route backup group, the primary link is considered as up. If no valid route exists, the primary link is considered as down and unusable. Then DDR creates a backup link on the backup interface to forward traffic.
Step Command Remarks Enter system view. system-view Enter the view of the backup interface interface-type interface. interface-number By default, a dialup interface is not Assign a dialup interface to a standby routing-group assigned to any dynamic route dynamic route backup group group-number backup groups.
Step Command Disconnect a dialup link. dialer disconnect [ interface interface-type interface-number ] 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-number ] interface or all dialup interfaces.
Page 203
# Enable traditional DDR on interface Dialer 0. [RouterA] interface dialer 0 [RouterA-Dialer0] dialer circular enable # Configure an IP address for the interface. [RouterA-Dialer0] ip address 100.1.1.1 255.255.255.0 # Associate dialer group 1 with the interface. [RouterA-Dialer0] dialer-group 1 # Configure dial strings for calling Router B and Router C.
# Configure the dial strings for calling Router A. [RouterB-Serial2/1/0] dialer route ip 100.1.1.1 8810048 [RouterB-Serial2/1/0] dialer route ip 100.1.1.1 8810049 [RouterB-Serial2/1/0] quit # Configure the user line to be used, and enable modem dial-in and dial-out on it. [RouterB] line tty1 [RouterB-line-tty1] modem enable both Configure Router C: # Create dialer group 1 and configure a dial rule for it.
Page 205
Figure 58 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 206
# Configure an IP address for interface Dialer 1. [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.
Page 207
[RouterA] line tty2 [RouterA-line-tty2] modem enable both Configure Router B: # 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...
# Create a local user usera for authenticating Router A, and configure the service type as PPP. [RouterC] local-user usera class network [RouterC-luser-network-usera] password simple usera [RouterC-luser-network-usera] service-type ppp [RouterC-luser-network-usera] quit # Configure an IP address for interface Dialer 0. [RouterC] interface dialer 0 [RouterC-Dialer0] ip address 122.1.1.2 255.255.255.0 # Enable bundle DDR on the interface.
Page 209
Configure traditional DDR to meet the following requirements: • Allow Router A to call Router B and Router C from multiple interfaces. Disable Router B and Router C from calling each other. • Figure 59 Network diagram Configuration procedure Configure Router A: # Create dialer group 1 and configure a dial rule for it.
[RouterB-Bri2/4/0] dialer route ip 100.1.1.1 8810048 Configure Router C: # Create dialer group 1 and configure a dial rule for it. <RouterC> system-view [RouterC] dialer-group 1 rule ip permit # 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.
Page 211
# Create dialer group 1 and configure a dial rule for it. <RouterA> system-view [RouterA] dialer-group 1 rule ip permit # Create local users userb and userc for authenticating Router B and Router C, and configure the service type as PPP for them. [RouterA] local-user userb class network [RouterA-luser-network-userb] password simple userb [RouterA-luser-network-userb] service-type ppp...
Page 212
[RouterA-Bri2/4/0] dialer bundle-member 0 [RouterA-Bri2/4/0] dialer bundle-member 1 # Enable PPP encapsulation on the interface. [RouterA-Bri2/4/0] link-protocol ppp # Configure PAP authentication on the interface. [RouterA-Bri2/4/0] ppp authentication-mode pap [RouterA-Bri2/4/0] ppp pap local-user usera password simple usera Configure Router B: # Create dialer group 2 and configure a dial rule for it.
[RouterC-luser-network-usera] password simple usera [RouterC-luser-network-usera] service-type ppp [RouterC-luser-network-usera] quit # Configure an IP address for interface 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 # Specify the host name of the remote router allowed to call in. [RouterC-Dialer0] dialer peer-name usera # Associate the interface with dialer group 1.
Page 214
Figure 61 Network diagram 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 authenticating Router B, and configure the service type as PPP. [RouterA] local-user userb class network [RouterA-luser-network-userb] password simple userb [RouterA-luser-network-userb] service-type ppp...
Page 215
[RouterA-Bri2/4/1] ppp mp # Enable PPP encapsulation on the interface. [RouterA-Bri2/4/1] link-protocol ppp # Configure PAP authentication on the interface. [RouterA-Bri2/4/1] ppp authentication-mode pap [RouterA-Bri2/4/1] ppp pap local-user usera password simple usera [RouterA-Bri2/4/1] quit # Configure PPP authentication on BRI 2/4/0, and assign BRI 2/4/0 to dialer bundle 0. [RouterA-Bri2/4/0] interface bri 2/4/0 [RouterA-Bri2/4/0] dialer bundle-member 0 # Enable MP for the interface.
[RouterB] controller e1 2/3/0 [RouterB-E1 2/3/0] pri-set [RouterB-E1-2/3/0] quit # Assign interface Serial 2/1/0:15 created on E1 2/3/0 to dialer circular group 0, which is associated with interface Dialer 0. [RouterB] interface serial 2/1/0:15 [RouterB-Serial2/1/0:15] dialer circular-group 0 ISDN caller number callback configuration example Network requirements As shown in Figure...
# Create dialer group 2 and configure a dial rule for it. <RouterB> system-view [RouterB] dialer-group 2 rule ip permit # Configure an IP address to interface BRI 2/4/0. [RouterB] interface bri 2/4/0 [RouterB-Bri2/4/0] ip address 100.1.1.2 255.255.255.0 # Enable traditional DDR on the interface. [RouterB-Bri2/4/0] dialer circular enable # Associate the interface with dialer group 2.
Page 218
# Enable PPP encapsulation on the interface. [RouterA-Serial2/1/0] link-protocol ppp # Configure PAP authentication on the interface. [RouterA-Serial2/1/0] ppp pap local-user usera password simple usera # Enable the interface to initiate callback requests as the callback client. [RouterA-Serial2/1/0] ppp callback client # Set the holddown timer to 15 seconds.
Page 219
Method 2: Use the callback number configured in the authorization-attribute callback-number command to call back the client. 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 Serial 2/1/0.
# Configure the interface to operate 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 221
The Internet Connection Wizard dialog appears. Select I want to set up my Internet connection manually or I want to connect through a local area network. Click Next. The Setting up your Internet connection dialog box appears. Select the I connect through a phone line and a modem option, and click Next. Enter the phone number for dialing to the callback server, and click Next.
# Configure the interface to operate as an asynchronous interface in protocol mode. [Router-Serial2/1/0] physical-mode async [Router-Serial2/1/0] async mode protocol # Enable PPP encapsulation on the interface. [Router-Serial2/1/0] link-protocol ppp # Configure PAP authentication on the interface. [Router-Serial2/1/0] ppp authentication-mode pap [Router-Serial2/1/0] ppp pap local-user Router password simple Router # Configure the interface to assign an IP address to the peer.
Page 223
[Router] local-user usernt class network [Router-luser-network-userc] password simple usernt [Router-luser-network-userc] service-type ppp [Router-luser-network-userc] quit # Configure interface Serial 2/1/0 to operate as an asynchronous interface in protocol mode. [Router] interface serial 2/1/0 [Router-Serial2/1/0] physical-mode async [Router-Serial2/1/0] async-mode protocol # Enable PPP encapsulation on the interface. [Router-Serial2/1/0] link-protocol ppp # Configure PAP authentication on the interface.
Select the Accept incoming connections option, and click Next to set the devices for incoming connections. Click Next. The Incoming Virtual Private Network (VPN) Connection window appears. Select the Allow virtual private connections option if the server is connected to the Internet to provide Internet access requests for the client.
Page 225
As shown in Figure 67, Router C and Router D have the same configurations as Router A and Router B. The only difference is that Router D uses an ISDN dial string 8810048 rather than PSTN dial strings to provide services. Configure Router C and Router D to implement DDR with one dial string and use CHAP for authentication.
Page 226
[RouterA] dialer-group 1 rule ip permit # Create a local user userb for authenticating Router B, and configure the service type as PPP. [RouterA] local-user userb class network [RouterA-luser-network-userb] password simple userb [RouterA-luser-network-userb] service-type ppp [RouterA-luser-network-userb] 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 227
[RouterB-luser-network-user16] password simple user16 [RouterB-luser-network-user16] service-type ppp [RouterB-luser-network-user16] quit # Enable PPP encapsulation on Dialer 0. [RouterB] interface dialer 0 [RouterB-Dialer0] link-protocol ppp # Configure PAP authentication on the interface. [RouterB-Dialer0] ppp authentication-mode pap [RouterB-Dialer0] ppp pap local-user userb password simple userb # Configure an IP address for the interface.
Page 228
Place the modem connected to PC in auto answer mode. Right-click the My Network Places icon and select the Properties option from the menu that appears. The Network and Dial-up Connections window appears. Right-click the Make New Connection icon and select the New Connection…option from the menu that appears.
Page 229
[RouterC-luser-network-userd] password simple user1 [RouterC-luser-network-userd] service-type ppp [RouterC-luser-network-userd] quit # Enable PPP address negotiation on BRI 2/4/0. [RouterC] interface bri 2/4/0 [RouterC-Bri2/4/0] ip address ppp-negotiate # Enable PPP encapsulation on the interface. [RouterC-Bri2/4/0] link-protocol ppp # Configure CHAP authentication on the interface. [RouterC-Bri2/4/0] ppp authentication-mode chap [RouterC-Bri2/4/0] ppp chap user user1 # Enable traditional DDR on the interface.
# Configure an IP address for the interface. [RouterD-Serial2/3/0:15] ip address 100.1.1.254 255.255.255.0 # Enable PPP encapsulation on the interface. [RouterD-Serial2/3/0:15] link-protocol ppp # Configure CHAP authentication on the interface. [RouterD-Serial2/3/0:15] ppp authentication-mode chap [RouterD-Serial2/3/0:15] ppp chap user userd # Configure the interface to assign IP addresses to PPP users. [RouterD-Serial2/3/0:15] remote address pool 1 [RouterD-Serial2/3/0:15] quit # Configure an IP address pool for assigning addresses in the system domain.
Page 231
[RouterA-Bri2/4/0] ip address 20.0.0.1 8 # Enable traditional DDR on the interface. [RouterA-Bri2/4/0] dialer circular enable # Associate the interface with dialer group 1. [RouterA-Bri2/4/0] dialer-group 1 # Configure the dial string for calling 40.0.0.1. [RouterA-Bri2/4/0] dialer route ip 40.0.0.1 8810052 [RouterA-Bri2/4/0] quit # Configure an IP address for interface Serial 2/1/0.
[RouterB-Serial2/1/0] ip address 10.0.0.2 8 # Enable PPP encapsulation on the interface. [RouterB-Serial2/1/0] link-protocol ppp [RouterB-Serial2/1/0] quit # Configure an IP address for interface Loopback 1. [RouterB] interface loopback 1 [RouterB-Loopback1] ip address 40.0.0.1 32 [RouterB-Loopback1] quit # Configure OSPF. [RouterB] ospf [RouterB-ospf-1] area 0 [RouterB-ospf-1-area-0.0.0.0] network 10.0.0.0 0.255.255.255...
Page 233
[RouterA-luser-network-userb] service-type ppp [RouterA-luser-network-userb] quit # Create a dynamic route backup group on Dialer 0. [RouterA] interface dialer 0 [RouterA] standby routing-group 1 rule ip 30.0.0.1 32 # Configure an IP address for the interface. [RouterA-Dialer0] ip address 20.0.0.1 24 # Enable PPP encapsulation on the interface.
Page 234
[RouterA-Bri2/4/0] rip metricin 2 Configure Router B: # Create dialer group 1 and configure a dial rule for it. <RouterB> system-view [RouterB] dialer-group 1 rule ip permit # Create a local user usera for 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] rip [RouterB-rip-1] network 10.0.0.0 [RouterB-rip-1] network 20.0.0.0 [RouterB-rip-1] network 30.0.0.0 [RouterB-rip-1] import-route direct Configuration example for dynamic route backup for multiple networks Network requirements As shown in Figure 70, Router A and Router B are directly connected through serial interfaces running PPP. They are also connected through an ISDN switched network, enabling them to call each other by using traditional DDR.
Page 236
[RouterA-E1 2/3/1] quit # Configure an IP address for interface Serial 2/1/0. [RouterA] interface serial 2/1/0 [RouterA-Serial2/1/0] ip address 1.0.0.1 255.0.0.0 # Enable PPP encapsulation on the interface. [RouterA-Serial2/1/0] link-protocol ppp [RouterA-Serial2/1/0] quit # Configure an IP address for interface Serial 2/3/1:15. [RouterA] interface serial 2/3/1:15 [RouterA-Serial2/3/1:15] ip address 2.0.0.1 255.0.0.0 # Enable traditional DDR on the interface.
[RouterB-Serial2/3/1:15] ip address 2.0.0.2 255.0.0.0 # Enable traditional DDR on the interface. [RouterB-Serial2/3/1:15] dialer circular enable # Associate the interface with dialer group 1. [RouterB-Serial2/3/1:15] dialer-group 1 # Configure the dial string for calling Serial 2/3/1:15 on Router A. [RouterB-Serial2/3/1:15] dialer route ip 2.0.0.1 mask 8 660330 [RouterB-Serial2/3/1:15] quit # Configure the Ethernet interfaces connecting to the networks.
Symptom 2: Ping failure The remote end cannot be pinged after the modem is connected. Solution To resolve the problem: Use the debugging ppp all command to verify that the same link layer encapsulation is used at the two ends and correct PPP parameters are configured for authentication. Verify that a correct IP address is assigned to the dialup interface.
Configuring Frame Relay This feature is supported only on the following modules: CE3. • CPOS. • CT3. • • E1-F. • • SAE. • • • T1-F. Overview Frame Relay uses statistical multiplexing technology and can establish multiple virtual circuits over a single physical cable to make full use of network bandwidth.
As shown in Figure • Router B and Router C form a simple Frame Relay network. DTE devices Router A and Router D are attached to the network. • The interface type DTE or DCE is identified only for the UNI interfaces. A virtual circuit between two DTE devices can be assigned different DLCIs on different segments.
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 IP packet is transmitted across a Frame Relay network as follows: When a DTE device receives an IP packet, the DTE device looks up the IP routing table for the outgoing interface and next-hop address.
Page 242
Monitor PVC status changes. • • Verify link integrity. The system supports the following LMI standards: 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: Status enquiry message—A DTE sends status enquiry messages regularly to a DCE to request the...
Device Value Default Timer/counter Description role range value Sets the interval (in seconds) for receiving a Keepalive (polling status enquiry message. If a DCE has not verification) timer 5 to 30 received any status enquiry messages when the (T392) timer expires, an error is recorded. How LMI works LMI works in the following process: When a DTE physically goes up, it sends a full status enquiry message to a DCE to request the...
Figure 72 Interconnecting LANs through a Frame Relay network Router A Router B Ser2/1/0 Ser2/1/0 202.38.163.251/24 202.38.163.252/24 DLCI=50 DLCI=70 Router C DLCI=60 Ser2/1/0 202.38.163.253/24 DLCI=80 Figure 73 Interconnecting LANs through a dedicated line Command and hardware compatibility Commands and descriptions for centralized devices apply to the following routers: MSR1002-4/1003-8S.
Configuring basic DCE-side Frame Relay Step Command Remarks Enter system view. system-view Enter the view of the interface interface interface-type connecting to the Frame Relay interface-number network. By default, PPP encapsulation is Enable Frame Relay enabled on interfaces except encapsulation on the link-protocol fr Ethernet interfaces, VLAN interface.
The DLCI of a virtual circuit must be unique on a main interface and all its subinterfaces. • Configuration procedure To configure a local Frame Relay virtual circuit: Step Command Remarks Enter system view. system-view interface interface-type The interface can be a main Enter interface view.
Step Command Remarks By default, no static Frame Relay address-to-DLCI maps are configured. Create a static Frame Relay fr map ip { ip-address | default } address-to-DLCI map. dlci-number When the DLCI specified in this command does not exist, the DLCI is automatically created.
Step Command Remarks Enter system view. system-view By default, no Frame Relay subinterface exists. interface interface-type Create a subinterface and If you do not specify a interface-number.subnumber [ p2mp enter subinterface view. subinterface type when you | p2p ] create a Frame Relay interface, a P2MP subinterface is created.
The maximum number of RTP/TCP header-compression connections configured on an interface is • inherited by all VCs of the interface. If you set a different maximum number on a VC of the interface, the configuration on the VC takes effect. •...
Configuring Frame Relay STAC compression STAC compression is a payload compression method that applies to Frame Relay packets and InARP packets. STAC compression cannot compress LMI messages. The two ends of a PVC negotiate the PVC state by using STAC control messages after STAC compression is enabled.
Configuration restrictions and guidelines When you configure Frame Relay FRF.12 fragmentation, follow these restrictions and guidelines: • FRF.12 fragmentation and Frame Relay traffic shaping are mutually exclusive on an interface. For more information about Frame Relay traffic shaping, see ACL and QoS Configuration Guide. An MFR interface does not support FRF.12 fragmentation.
(Method 2) Using subinterfaces Configure Router A: # Enable Frame Relay encapsulation on the interface Serial 2/1/0. <RouterA> system-view [RouterA] interface serial 2/1/0 [RouterA-Serial2/1/0] link-protocol fr # Set the type of the interface Serial 2/1/0 to DCE. [RouterA-Serial2/1/0] fr interface-type dce [RouterA-Serial2/1/0] quit # Create a subinterface Serial 2/1/0.1.
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 HP Support. The physical layer is already up, but the link layer protocol is down Symptom The physical layer is already up, but the link layer protocol is down.
Page 256
Verify that the devices at both ends have configured correct address-to-DLCI maps for the peer. Verify that a route to the peer exists if the devices are not on the same subnet segment. If the problem persists, contact HP Support.
Configuring an MFR bundle (Required.) Configuring an MFR bundle link Configuring an MFR bundle To maximize bandwidth that can be used, HP recommends that you bundle physical interfaces of the same speed in one bundle. To configure an MFR bundle: Step...
Step Command Remarks By default, no MFR interface or subinterface exists. Create an MFR interface interface mfr { interface-number | and enter MFR interface interface-number.subnumber Before creating an MFR subinterface, view. [ p2mp | p2p ] } make sure the main MFR interface already exists.
Step Command Remarks Assign the interface to an By default, an interface is not assigned to fr mfr interface-number MFR interface. any MFR interfaces. (Optional.) Set the MFR By default, the name of the current mfr link-name name bundle link identifier. interface is used.
Configuration procedure Configure Router A: # Create interface MFR 4, and assign an IP address to the interface. <RouterA> system-view [RouterA] interface mfr 4 [RouterA-MFR4] ip address 10.140.10.1 255.255.255.0 # Set the type of the interface to DTE. [RouterA-MFR4] fr interface-type dte # Configure a static Frame Relay address-to-DLCI map for the interface.
Verifying the configuration # On Router A, verify that the PVC is active. [RouterA] display fr pvc PVC information for interface MFR4 (DTE, physically up) DLCI: 100 Type: Static Interface: MFR4 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.
Related information Documents To find related documents, browse to the Manuals page of the HP Business Support Center website: http://www.hp.com/support/manuals For related documentation, navigate to the Networking section, and select a networking category. •...
Conventions This section describes the conventions used in this documentation set. Command conventions Convention Description Boldface Bold text represents commands and keywords that you enter literally as shown. Italic Italic text represents arguments that you replace with actual values. Square brackets enclose syntax choices (keywords or arguments) that are optional. Braces enclose a set of required syntax choices separated by vertical bars, from which { x | y | ...
Page 264
Network topology icons 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 273
feature and hardware compatibility STAC compression configuration (interface), 242, ISDN, STAC compression configuration restrictions, flag subinterface configuration, ATM cell CLP flag value, troubleshoot, flow troubleshoot link layer protocol down, L2TP session flow control, troubleshoot peer cannot be pinged, Frame Relay troubleshoot physical layer down, address mapping, virtual circuit,...
Page 274
link bundle interface configuration header compression. Use IPHC restrictions, IP address link bundling basic concepts, IP segment match enable, link bundling display, IP addressing link bundling load balancing mode, 4G modem Eth-channel interface IP address, link bundling maintain, L2TP IP address specification, link bundling member interface, L2TP LAC source IP address configuration, link bundling member interface state,...
Page 275
PPP IPCPv6 negotiation, traditional DDR configuration (ISDN-based), IPv6 addressing troubleshoot devices cannot ping each other, PPPoE server IPv6 address assignment issuing (DHCPv6), 3G/4G modem configuration directive, IPv6CP negotiation modem AT command, PPPoE server IPv6 address assignment (ND+IPv6CP negotiation), keepalive ISDN PPP polling, application scenario, B-channel selection,...
Page 276
troubleshoot remote system network access HDLC link status polling, failure, ISDN Q.921 BRI interface link connectivity, tunnel, MP binding mode configuration, tunnel authentication configuration, MP configuration, tunnel configuration (client-initiated), Multilink Frame Relay configuration, 248, tunnel configuration (LAC-auto-initiated), PPP and MP configuration, tunnel configuration (NAS-initiated), PPP CHAP authentication 1-way configuration, tunnel establishment,...
Need help?
Do you have a question about the MSR Router Series and is the answer not in the manual?
Questions and answers