No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

AR Router Troubleshooting Guide

This Product Documentation provides guidance for maintaining AR Enterprise Router, covering common information collection and fault diagnostic commands, typical fault troubleshooting guide, and troubleshooting.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
PPPoE Dialup Fails

PPPoE Dialup Fails

Common Causes

The application of PPPoE involves PPPoE client and PPPoE server.

This fault is commonly caused by one of the following:
  • The interface configuration is incorrect.
  • The physical interface frequently alternates between Up and Down states.
  • User authentication fails.
  • No IP address is assigned to the PPPoE client.
  • No echo message is received.

Troubleshooting Flowchart

Figure 17-9 shows the troubleshooting flowchart.
Figure 17-9  Troubleshooting flowchart for failed PPPoE dialup

Troubleshooting Procedure

NOTE:

Saving the results of each troubleshooting step is recommended. If troubleshooting fails to correct the fault, you will have a record of your actions to provide Huawei technical support personnel.

Procedure

  1. Check that the physical interface is working properly.

    Run the display this interface command on the physical interface to check whether the physical interface frequently alternates between Up and Down states.

    • If the physical interface frequently alternates between Up and Down states, check the physical connection or replace the cable.
    • If the physical interface is working properly, go to step 2.
  2. Check that the configuration is correct.

    On the PPPoE server, check the configurations of the virtual template interface and Ethernet physical interface. On the PPPoE client, check the configurations of the dialer interface and Ethernet physical interface. Run the display this command in the interface view to check the interface configuration.

    On the PPPoE server:
    [Huawei-A-Virtual-Template10]display this                                       
    ppp authentication-mode chap      
    
    [Huawei-A-aaa]display this                                                      
    local-user ub password cipher %$%$yYr|IcpfX4V8pb$"ueOS%>5,%$%$
    
    On the PPPoE client:
    [Huawei-B-Dialer10]display this                                                   
     ppp chap user ub                                                               
     ppp chap password simple ub 
     dialer-group 5                
    
    [Huawei-B-GigabitEthernet0/0/1]display this                                     
    pppoe-client dial-bundle-number 10                                                        
    
    [Huawei-B-dialer-rule]display this                                              
    dialer-rule                                                                    
    dialer-rule 5 ip permit    
    

    • If authentication is configured on the PPPoE server, check whether the user name and password are correctly configured on the PPPoE client. If the dial-on-demand function is configured on the PPPoE client, the PPP link is torn down when there is no traffic to be transmitted. Ensure that the dialer-rule-number value in the dialer-rule command is the same as the group-number value in the dialer-group command.

    • If the preceding configurations are all correct but the fault persists, go to step 3.

  3. Find out the dial-in failure cause.

    On the PPPoE client, check whether the PPP protocol frequently alternates between Up and Down states because authentication fails. Run the following commands to check the displayed information. The dialer interface is the dialup interface of the PPP connection.
    <Huawei-B>terminal monitor                                                      
    Info: Current terminal monitor is on.   
    
    <Huawei-B>terminal debugging                                                    
    Info: Current terminal debugging is on. 
    Info: Current terminal monitor is on.   
    
    <Huawei-B>debugging ppp all interface Dialer 10                                   
    
    If the following information is displayed, authentication fails.
    <Huawei-B>Jan 21 2008 17:40:56.420.1+08:00 AR1220-B MID_PPP/7/debug2:            
      PPP Packet:                                                                   
          Dialer10:0 Input  CHAP(c223) Pkt, Len 33                                  
          State SendResponse, code FAILURE(04), id 2, len 29                        
          Message: Illegal User or password. 
    
    <Huawei-B>Jan 21 2008 17:40:56.420.1+08:00 AR1220-S-B MID_PPP/7/debug2:            
      PPP Packet:                                                                   
          Dialer10:0 Input  CHAP(c223) Pkt, Len 33                                  
          State SendResponse, code FAILURE(04), id 2, len 29                        
          Message: Illegal User or password. 
    
    <Huawei-B>Jan 21 2008 17:42:37.520.4+08:00 AR1220-B MID_PPP/7/debug2:            
      PPP Packet:                                                                   
          Dialer10:0 Output LCP(c021) Pkt, Len 13                                   
          State reqsent, code ConfRej(04), id 1, len 9                              
          AuthProto(3), len 5, CHAP c22305                                          
    
    
    <Huawei-B>Jan 21 2008 17:42:37.520.4+08:00 AR1220-S-B MID_PPP/7/debug2:            
      PPP Packet:                                                                   
          Dialer10:0 Output LCP(c021) Pkt, Len 13                                   
          State reqsent, code ConfRej(04), id 1, len 9                              
          AuthProto(3), len 5, CHAP c22305                                          
    
    
    <Huawei-B>Jan 21 2008 17:42:37.530.6+08:00 AR1220-B MID_PPP/7/debug2:             
      PPP Packet:                                                                   
          Dialer10:0 Input  LCP(c021) Pkt, Len 8                                    
          State opened, code TermReq(05), id 3, len 4  
                 
    
    <Huawei-B>Jan 21 2008 17:42:37.530.6+08:00 AR1220-S-B MID_PPP/7/debug2:             
      PPP Packet:                                                                   
          Dialer10:0 Input  LCP(c021) Pkt, Len 8                                    
          State opened, code TermReq(05), id 3, len 4  
                 
    

    In the preceding command output, the first part of information indicates that a CHAP user name is configured on the PPPoE client and the PPP client receives a Challenge message from the PPPoE server and replies with a Response message. Because the CHAP password is incorrect or the user name or password does not exist, the PPPoE server sends a Response Failed message to the PPPoE client. The second part of information indicates that no authentication information is configured on the PPPoE client or the authentication mode configured on the PPPoE client is different from that configured on the PPPoE server so the client refuses the authentication request from the server in LCP negotiation. If the client fails to be authenticated four times, the third part of information is displayed, indicating that the PPPoE server sends a request to tear down the PPP connection between the server and client.

    • If authentication fails, check the authentication configuration and configure correct authentication user name and password for the PPPoE client.

    • If authentication succeeds but the fault persists, go to step 4.

  4. Check that an IP address is correctly assigned to the PPPoE client.

    If an IP address is incorrectly assigned to the PPPoE client, check the related configuration of the PPPoE server. If IP addresses are assigned to the PPPoE client from a remote IP address pool, check whether there are available IP addresses in the remote IP address pool. Log in to the PPPoE server and run the following command to check the IP address pool.
    [Huawei-A-ip-pool-mypoo]display ip pool name mypool                            
      Pool-name      : mypool                                                       
      Pool-No        : 0                                                            
      Lease          : 1 Days 0 Hours 0 Minutes                                     
      Domain-name    : -                                                            
      DNS-server0    : -                                                            
      NBNS-server0   : -                                                            
      Netbios-type   : -                                                            
      Position       : Local           Status           : Unlocked                  
      Gateway-0      : 20.1.1.1                                                     
      Mask           : 255.255.255.0                                                
      VPN instance   : --                                                           
     -----------------------------------------------------------------------------  
             Start           End     Total  Used  Idle(Expired)  Conflict  Disable  
     -----------------------------------------------------------------------------  
            20.1.1.1      20.1.1.254   253     1   252       0         0        0   
     -----------------------------------------------------------------------------  
    

    If the Idle field is displayed as 0, there are no available IP addresses. Use an IP address pool with available IP addresses instead of the IP address pool configured on the virtual template interface of the PPPoE server. If the negotiated IP address of the PPPoE client conflicts with another local IP address, the PPP protocol also frequently alternates between Up and Down states.

    • If the PPPoE server fails to assign IP addresses to the PPPoE client, check the IP address pool usage and use another IP address pool.

    • If the PPPoE server correctly assigns IP addresses to the PPPoE client, go to step 5.

  5. Check whether the PPPoE client correctly receives heartbeat messages.

    Log in to the PPPoE client and run the following commands to check the command output.
    <Huawei-B>terminal monitor                                                      
    Info: Current terminal monitor is on.   
    
    <Huawei-B>terminal debugging                                                    
    Info: Current terminal debugging is on. 
    
    <Huawei-B>debugging ppp lcp all interface Dialer 10                                    
    
    If outgoing Echo Request messages are displayed but no incoming Echo Reply message is displayed, the client cannot receive heartbeat messages.
    [Huawei-B]
    Jan 21 2008 19:20:37.790.2+08:00 AR1220-B MID_PPP/7/debug2:                     
      PPP Packet:                                                                   
          Dialer10:0 Output LCP(c021) Pkt, Len 12                                   
          State opened, code EchoRequest(09), id c0, len 8                          
          Magic Number 0560b017                                                     
    

    If the client does not receive any response to its consecutive four heartbeat messages, it tears down the link with the server. If the client has received heartbeat messages but the fault persists, go to step 6.

  6. Collect the following information and contact technical support personnel.
    • Results of the preceding troubleshooting procedure

    • Configuration files, log files, and alarm files of the device

Translation
Download
Updated: 2019-05-10

Document ID: EDOC1000079719

Views: 452890

Downloads: 4311

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next