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

ME60 Troubleshooting Guide V1.0 (VRPv8)

This document provides the maintenance guide of the device, including daily maintenance, emergence maintenance, and typical 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).
Troubleshooting PPPoX

Troubleshooting PPPoX

IPv4 PPPoE Access Troubleshooting

This section describes the configuration notes, flows, and procedures for PPPoX troubleshooting based on the typical PPPoX networking.

Typical Networking
Figure 4-153 PPPoE networking

Figure 4-154 Networking for PPPoEoV

Figure 4-155 Networking for PPPoEoQ

Troubleshooting Flowchart
Figure 4-156 PPPoX troubleshooting flowchart

Troubleshooting Procedure

Procedure

  1. Run the display aaa online-fail-record command to display the cause of online failure.

    <HUAWEI> display aaa online-fail-record username test@hauwei
    -------------------------------------------------------------------
      User name          : test@radius
      User MAC           : 00e0-fc12-3456
      User access type   : PPPoE
      User interface     : Atm4/0/2
      User Pe Vlan       : 99
      User Ce Vlan       : 99
      User IP address    : -
      User ID            : 233
      User authen state  : Authened
      User acct state    : AcctIdle
      User author state  : AuthorIdle
      User login time    : 2009-09-04 15:14:14
      Online fail reason : PPP with authentication fail
      -------------------------------------------------------------------   
    

    Here, User online fail reason indicates why the user fails to go online. From the information, you can judge the fault and find out how to locate the fault.

    Table 4-4 Reasons for online failure

    User online fail reason

    Meaning

    PPP with authentication fail

    Indicates the PPP authentication failure.

    IP address alloc fail

    Indicates the failure to assign IP addresses.

    IP address conflict

    Indicates the IP address conflict.

    mac address conflict

    Indicates the MAC address conflict.

    Start accounting fail

    Indicates the failure to start accounting.

    Domain or user access limit

    Indicates the limit on domain or user access.

    Port access limit

    Indicates the access limit on the port.

    PPP negotiate fail

    Indicates the PPP negotiation failure.

    Send authentication request fail

    Indicates the failure to send the authentication request.

    Radius authentication reject

    Indicates that the RADUIS server rejects the authentication request.

    Radius authentication send fail

    Indicates the failure to send the RADIUS authentication request.

    Local authentication reject

    Indicates that the local authentication is rejected.

    Local authentication no user

    Indicates that the user cannot be found in the local authentication domain.

    Local Authentication user type not match

    Indicates that the user type does not match with the local domain.

    Local Authentication user block

    Indicates that the account is not activated in the local authentication.

  2. Check the configuration.

    From step 1, you can learn that some failures are caused by configurations, for example, "Local authentication no user" and "Domain or user access limit." In this case, modify the configuration.

    Sometimes, the user fails to go online because no PPPoX link is set up. It is possible that the user is still offline, so there is no offline record of the user.

  3. Check whether the user has been forbidden to access the device.

    Run the display ppp [ slot slot-number ] chasten-user [ [ mac-address mac-address ] | [ option105 [ circuit-id circuit-id ] [ remote-id remote-id ] ] ] command to check whether the user has been forbidden to access the device.

    • If the user access is forbidden, dial up again after the user access is not forbidden.
    • If the user access is not forbidden, go to Step 4.
  4. Enable service tracing.

    Run the trace mac command to enable service tracing and test the online process. When the user gets offline, display the output information of service tracing.

    If the ME device does not receive the PADI or PADR packet. Check the layer 2 network connectivity, the port state, the access type (layer2-subscriber), the authentication method (PPP must be allowed), and the VT bound to the interface.

    NOTE:

    If the service tracing function outputs no information, it indicates that the user sends no packets to the ME device. The possible causes are as follows:

    • User access type is incorrect.

    • The authentication method is incorrect.

    • The physical port is not bound to any VT.

    • The physical connections on the device are incorrect.

    • The layer 2 devices are configured incorrectly.

  5. Check the configuration.

    If the service tracing function does not output any information, check whether:

    • The devices are connected to each other correctly.

    • The configurations on the ME60are correct.

    • The layer-2 devices are configured correctly.

    • The user packets can reach the ME60.

    If the incorrect configurations cause the online failure, check the related local configurations

    • Run the display access-user mac-address [ mac ] command to see whether a user has already gone online by using the MAC address.

    • Check the configuration of the authentication method. If the user is authenticated by the RADIUS server, the RADIUS configurations on the ME60 must be correct. The user name must be included in the correct domain and the RADIUS server operates normally. Check whether the local account is configured properly and the number of access users is not limited.

  6. Obtain the packets at the client to check whether the LCP negotiation is complete.

    By obtaining packets, you can learn whether the LCP negotiation failure is caused by the ME60, the client, or the improper interoperation between them.

    The following lists the common faults:

    1. A non-standard PPPoE client sends the config-request packet to the ME60. The ME60 responds with a config-nak/config-reject packet. If the client keeps the attributes in the config-request packet unmodified, the LCP negotiation fails.
    2. The ME60 is configured with the Challenge-Handshake Authentication Protocol (CHAP) authentication while the client is configured with the PAP authentication. The LCP negotiation fails.
  7. Check whether the authentication succeeds.

    If the local authentication for some reasons, for example, invalid local account, inactive domain, inactive account, inconsistent account type, or access limit, you can see the cause of the failure in authentication messages.

    In case of RADIUS authentication, the service tracing function also outputs the information that can help you locate the fault.

    The failure may be caused by the RADIUS server, because the RADIUS server fails to respond to the ME device. If you cannot judge the fault from the output, check the RADIUS server.

    For details, see 5 "RADIUS Troubleshooting."

  8. Check whether the NCP negotiation succeeds.

    The key of PPPoE NCP negotiation is the IP address, and therefore NCP negotiation equals the address negotiation..

    Check IP address assignment.

    • The IP address is assigned by the ME60.

      Check the configuration of the domain: the referenced IP address pool and the availability of IP addresses. If the IP address pool is specified by the RADIUS server, make sure that the RADIUS server delivers the correct attribute (88, Framed-Pool), If the delivered string contains @ or #, the characters before @ or # are used as the address pool name. In addition, the specified address pool must be configured on the ME60.

    • The IP address is assigned by the RADIUS server.

      Check the Framed-IP-Address attribute in the RADIUS response packet.

      If the Framed-IP-Address attribute is 255.255.255.255 or 255.255.255.254, it indicates that the IP address is assigned by the ME60, and the domain need reference the correct address pool. If the RADUIS response does not contain this attribute, it also indicates the IP address is assigned by the ME60. If the attribute value is incorrect, no IP address is assigned to the user.

    • The ME60 serves as the client, requiring the external DHCP server to assign IP addresses.

      If the IP assignment procedure is incorrect, check whether:

      • The DHCP server group is configured correctly on the ME60 and referenced by the correct address pool.

      • There is a reachable route to the DHCP server group.

      • The DHCP server group operates well.

      • The IP address assigned by the DHCP server is valid.

      • The assigned IP address falls into the address pool configured on the ME60.

      • The mask is the same as that of the address pool configured on the ME60.

      • The IP address is already used by another online user.

      If the fault persists, contact the Huawei customer service center.

  9. Check the accounting.

    If the user is still offline, it indicates that a fault has occurred on the accounting.The common fault is "Start accounting fail."

    The ME60 supports RADIUS accounting, HWTACAS accounting, and no accounting. That is, the ME60 cannot conduct accounting for users locally.

    NOTE:

    If the RADIUS accounting or HWTACACS accounting fails, the ME60 stores the accounting data locally and generates CDRs. When the accounting server recovers, the ME60 sends the CDRs to the accounting server. If the local storage space is full, while the accounting server does not recover, the ME60 discards the latter accounting data.

Follow-up Procedure

If the fault persists, contact Huawei engineers.

IPv6 PPPoE Access Troubleshooting

This section describes the notes about configuring PPPoE access, and provides the PPPoE access troubleshooting flowchart and the troubleshooting procedure in a typical PPPoE access networking.

Typical Networking

Figure 4-157 shows the typical networking of PPPoE access. PPPoE access troubleshooting is based on this networking.

Figure 4-157 Typical networking diagram of PPPoE access

As shown in Figure 4-157:

  • The user is connected to the ME60 through a Layer 2 network, and the user gets online by dialing in through PPP.

  • The ME60 is connected to the RADIUS server to implement authentication and accounting for users.

  • The ME60 is connected to an IPv6 DNS server.

The user accesses the ME60 through PPPoE. The ME60 assigns an IPv6 address to the user and manages the user.

Troubleshooting Flowchart

On the network shown in Typical Networking, a user accesses the ME device through PPPoE; however, the user cannot obtain an IPv6 address and therefore fails to get online. You can locate the fault based on the following troubleshooting flowchart.

Figure 4-158 Troubleshooting flowchart of PPPoE access

Troubleshooting Procedure

Procedure

  1. Check that the physical connection between the client and server works properly.

    Check whether the client and server can ping through each other. If they can ping through each other, the physical connection between them works properly. If they fail to ping through each other, rectify the fault on the physical connection, and then check whether the problem persists. If the problem persists, go to Step 2.

  2. Check that the configuration of the interface connecting the server to the client is correct.

    Run the display this command in the interface view to check whether the configuration of the interface is correct. For the correct interface configuration, refer to the chapter "Configuring the IPv6 Access Service" in the Configuration Guide - BRAS.

    • If the interface configuration is incorrect, modify the interface configuration to be correct. For details, refer to the chapter "Configuring the IPv6 Access Service" in the Configuration Guide - BRAS.
    • If the interface configuration is correct, go to Step 3.

  3. Check that the prefix pool is correctly configured.

    Run the display ipv6 prefix command in the system view to check whether an IPv6 prefix pool is configured.

    • If there is no IPv6 prefix pool, run the ipv6 prefix prefix-name local command to create the local prefix pool, enter the prefix pool view, and then run the prefix prefix-address prefix-length command to configure an IPv6 prefix address.
    • If there is an IPv6 prefix pool, run the ipv6 prefix prefix-name command to enter the prefix pool view, and then run the display this command to check whether an IPv6 prefix address is configured in this prefix pool. If no IPv6 prefix address is configured in this prefix pool, run the prefix prefix-address prefix-length command to configure an IPv6 prefix address.

    If the problem persists, go to Step 4.

  4. Check that the address pool is correctly configured.

    Run the display ipv6 pool command in the system view to check whether an IPv6 address pool is configured.

    • If there is no IPv6 address pool, run the ipv6 pool pool-name bas local command to create the local address pool, enter the address pool view, and then run the prefix prefix-name command to bind the prefix pool in Step 3 to this address pool.
    • If there is an IPv6 address pool, run the ipv6 pool pool-name command to enter the address pool view, and then run the display this command to check whether this address pool is bound to the prefix pool in Step 3. If they are not bound, run the prefix prefix-name command to bind the prefix pool in Step 3 to this address pool.

    If the problem persists, go to Step 5.

  5. Check that the user domain is bound to the IPv6 address pool.

    Run the display this command in the AAA view to check whether the user domain is bound to an IPv6 address pool.

    • If the user domain is not bound to the IPv6 address pool, run the ipv6-pool pool-name command in the domain view to bind the user domain to the IPv6 address pool.
    • If the user domain is bound to the IPv6 address pool, go to Step 6.

  6. Check that there are assignable IPv6 addresses in the address pool.

    Run the display ipv6 prefix prefix-name all command in the system view to check whether the number of online users in the prefix pool reaches 1024.

    • If the value of the Online-user field is displayed as 1024, there are no assignable addresses in this prefix pool. In this case, configure a new prefix pool and a new address pool and then bind the new address pool to the user domain.
    • If the value of the Online-user field is less than 1024, there are assignable addresses in this prefix pool.

    If the client still cannot obtain an IPv6 address, contact Huawei technical personnel.

  7. Check that the system is not suppressed from advertising RA messages.

    Run the display this command in the AAA domain view to check whether the router is suppressed from sending RA messages in the user domain.

    If the client needs to obtain IPv6 addresses using stateless address autoconfiguration, the router cannot be suppressed from sending RA messages. If the router is not suppressed from sending RA messages and the client still cannot obtain an IPv6 address, contact Huawei technical support personnel.

IPv6 PPPoE Stateful Access Troubleshooting

This section describes the troubleshooting flowchart and provides a step-by-step troubleshooting procedure for the fault that the user cannot get online or the user's access type is incorrect when the ME60 is configured with PPPoE IPv6 stateful access.

Common Causes

This fault is commonly caused by one of the following:

  • The DUID function is not globally enabled.
  • The IPv6 address pool is incorrectly configured.
  • The address allocation mode is not configured.
  • The authentication mode is not set to PPP on the BAS interface.
Troubleshooting Flowchart

The user information indicates that the user cannot get online when the ME60 is configured with PPPoE IPv6 stateful access.

The troubleshooting roadmap is as follows:

  • Check that the DUID function is enabled in the system view.
  • Check that a correct IPv6 address pool has been configured.
  • Check that the authentication mode has been set to PPP on the BAS interface.

The user successfully gets online. Query the status of the online user. The results, however, indicate that the address allocation mode is incorrect.

The troubleshooting roadmap is as follows:

  • Check that the address allocation mode has been configured in the domain view.

Figure 4-159 shows the troubleshooting flowchart.

Figure 4-159 Troubleshooting flowchart for the fault that the user cannot get online or the address allocation mode is incorrect in the case of IPv6 PPPoE stateful access

Troubleshooting Procedure

Before performing the following steps, you can refer to Common Causes for Failing to Get Online and correct the fault according to prompts displayed by the device.

NOTE:
Saving the results of each troubleshooting step is recommended. If your 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 DHCPv6 DUID function is globally enabled.

    Run the display current-configuration command to check whether the DHCPv6 DUID function is globally enabled.

    • If dhcpv6 duid is not displayed, run the dhcpv6 duid llt command in the system view.
    • If dhcpv6 duid is displayed, go to step 3.

  2. Check that the IPv6 address pool has been correctly configured.

    Run the display this command in the authentication domain view to check whether a correct IPv6 address pool has been configured.

    • If the configured IPv6 address pool is incorrect, configure a correct IPv6 address pool in the authentication domain view.
    • If the IPv6 address pool has been correctly configured, go to step 4.

  3. Check that the authentication mode has been set to PPP on the BAS interface.

    Run the display this command on the user access interface to check whether the authentication mode has been set to PPP on the interface with the BAS.

    • If the authentication mode is not ppp, run the authentication-method-ipv6 ppp command on the interface with the BAS to change the authentication mode to PPP.
    • If authentication-method-ipv6 is not displayed, the authentication mode is PPP by default. Go to step 5.

  4. Check that the address allocation mode has been configured in the domain view.

    If the user properly gets online, run the display access-user user-id user-id command. If the display information indicates that the way to obtain the user address is incorrect, check whether the address allocation mode has been configured in the domain view. If the ipv6 nd autoconfig managed-address-flag command is displayed, the address allocation mode has been configured.

    • If the address allocation mode is not configured, run relevant commands to correctly configure it.
    • If the address allocation mode has been configured, go to step 6.

  5. Collect the following information and contact Huawei technical support personnel.

    • Results of the preceding troubleshooting procedure
    • Configuration files, log files, and alarm files of the devices

Relevant Alarms and Logs

Relevant Alarms

None.

Relevant Logs

None.

Translation
Download
Updated: 2019-06-11

Document ID: EDOC1000175918

Views: 13631

Downloads: 257

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