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).
IPoE Access Troubleshooting

IPoE Access Troubleshooting

Troubleshooting IPoX

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

Typical Networking
Figure 4-129 IPoE networking

Figure 4-130 Networking for IPoEoV and static user

Figure 4-131 Networking for IPoEoQ

Troubleshooting Flowchart
Figure 4-132 IPoX troubleshooting flowchart

Troubleshooting Procedure

Procedure

  1. Check whether the user passes authentication.

    • If user authentication fails, check the authentication domain and pre-authentication domain configurations based on the authentication mode.

    • If user authentication is successful, go to Step 2.

  2. Check whether the user has obtained an IP address.

    The IP addresses of IPoX users can be assigned by the local ME device or the remote DHCP server:

    • If the IP address is assigned by the local device, check the configuration of the local address pool.
    • If the IP address is assigned by the remote DHCP server, check the communication between the local device and the DHCP server.

  3. Enable service tracing to locate the fault through the login process.
  4. Enable debugging.

    The output information of debugging is more specific than the service tracing information. It helps you locate the fault.

    If the fault persists, contact Huawei engineers.

    NOTE:

    Debugging cannot be performed for a single user. Therefore, it is not recommended.

Troubleshooting L3 Access

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

Typical Networking

Figure 4-133 shows the typical networking of L3 users. The troubleshooting procedure is based on this networking.

Figure 4-133 L3 access networking

  • The ordinary L3 user configures an IP address or obtains an IP address from the DHCP server.

  • The user accesses the Internet through the ME device, and the ME device should manage the user.

Troubleshooting Flowchart
Figure 4-134 L3 access troubleshooting flowchart

Troubleshooting Procedure

Procedure

  1. Check the record of login failure.

    Run the display aaa online-fail-record command to check the record of login failure.

    The possible failure causes are as follows:

    • The authentication fails. That is, the authentication packets cannot be sent or start-accounting fails. Check the home domain of the L3 access user. The authentication mode and accounting mode of the domain should be none authentication and none accounting.

    • The virtual private network(VPN) configuration is inconsistent. Check whether the configuration of VPN instance in the domain is consistent with the VPN configuration on the interface.

  2. Check the status of the physical interface.

    Run the display interface command to check the status of the physical interface. Check whether the interface and the protocol are up and the packets are sent and received on the interface.

    <HUAWEI> display interface gigabitethernet 1/0/0
    GigabitEthernet1/0/0 current state : UP
    Line protocol current state : UP
    Description : HUAWEI, GigabitEthernet1/0/0 Interface, Route Port
    The Maximum Transmit Unit is 1500 bytes, Hold timer is 10(sec)
    Internet Address is 192.168.1.2/24
    IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fc12-3456
    the Vendor PN is HFBR-5710L
    Port BW:1G, Transceiver max BW:1G, Transceiver Modes: MutipleMode
    WaveLength:850nm,Transmission Distance:550m
    Loopback:none, full-duplex mode, negotiation: disable
    Statistics last cleared:2006-09-15 17:50:54
        Last 5 minutes input rate: 0 bits/sec, 0 Packets/sec
        Last 5 minutes output rate: 0 bits/sec, 0 Packets/sec
        Input: 0 Bytes, 0 Packets
        Output: 0 Bytes, 0 Packets
        Input:
          Unicast   :        0, Multicast       :        0
          Broadcast :        0, JumboOctets     :        0
          CRC       :        0, Symbol          :        0
          Overrun   :        0, InRangeLength   :        0
          LongPacket:        0, Jabber          :        0, Alignment: 0
          Fragment  :        0, Undersized Frame:        0
          RxPause   :        0
        Output:
          Unicast   :        0, Multicast  :        0
          Broadcast :        0, JumboOctets:        0
          Lost      :        0, Overflow   :        0, Underrun: 0
          TxPause   :        0

  3. Check the configuration of the L3 access user.

    For details, refer to section Troubleshooting L3 Access Check whether the route in the network segment of the L3 access user is added.

  4. Enable service tracing to locate the fault.

    Perform service tracing based on the IP address of the user. Collect the tracing information to locate the fault. For example, if "fail to get domain of layer3 user" is displayed in the tracing information, check whether the VPN configuration of the user is consistent with the VPN configuration on the interface.

Follow-up Procedure

If the fault persists, contact Huawei technical personnel.

Users Go Offline at Low Speed

This section describes how to troubleshoot the problem that users go offline at low speed on a BRAS device.

Common Causes

This fault is commonly caused by one of the following:

  • A limit is configured on the user offline speed.
Troubleshooting Flowchart

The default user offline speed is 256 users per second on a BRAS. If users go offline at a speed lower than 256 users per second, the user offline speed is low. To monitor the user offline speed, run the display access-user online-total-number command repeatedly.

Figure 4-135 shows the troubleshooting flowchart.

Figure 4-135 Troubleshooting flowchart for the problem that users go offline at low speed

Troubleshooting Procedure

Before you perform the following steps, run the display aaa configuration command to check whether a smaller value is configured for the user offline speed. The default user offline speed is 256 users per second.

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 the current user offline speed.

    Run the display access-user online-total-number command repeatedly to estimate the current user offline speed.

    • If the user offline speed is about 256 users per second, the users go offline at a normal speed.
    • If the user offline speed is far less than 256 users per second, the users go offline at a low speed. Go to step 2.
  2. Check whether a limit is configured for the user offline speed.

    Run the display aaa configuration command in the user view to check the user offline speed configured on the device.

    • If the configured user offline speed is less than 256 users per second, go to Step 3.
    • If the configured user offline speed is 256 users per second, go to Step 4.
  3. Reset the user offline speed.

    Check that the configured user offline speed is not required and run the offline-speed 256 command in the AAA view. Then, run the display access-user online-total-number command repeatedly to check the current user offline speed.

    • If the user offline speed is normal, the problem is solved.
    • If the user offline speed is abnormal, go to Step 4.
  4. Collect the following information and contact Huawei technical support personnel.

    • Result of the preceding procedure
    • Trap, log, and configuration information

Relevant Alarms and Logs

Relevant Alarms

None

Relevant Logs

None

User Cannot Get Online in the Case of IPoE Stateful PD

This section describes the troubleshooting flowchart and provides a step-by-step troubleshooting procedure for the fault that the user cannot get online when the ME60 is configured with IPoE stateful PD.

Common Causes

This fault is commonly caused by one of the following:

  • The IPv6 function is not globally enabled.
  • DUID is not configured globally.
  • The IPv6 protocol on the user-side interface is Down.
  • The M/O value has been configured on the user-side interface.
  • Bind authentication is not configured on the user-side interface with the BAS.
  • The prefix pool is incorrectly configured.
Troubleshooting Flowchart

This section describes the troubleshooting flowchart for the fault that the user cannot get online when the ME60 is configured with IPoE stateful PD.

The troubleshooting roadmap is as follows:

  • Check that the IPv6 protocol is Up on the user-side interface.
  • Check that the M/O value has been configured on the user-side interface.
  • Check that bind authentication has been configured on the interface with the BAS.
  • Check that address pools have been correctly configured.

Figure 4-136 shows the troubleshooting flowchart.

Figure 4-136 Troubleshooting flowchart for the fault that the user cannot get online in the case of IPoE stateful PD

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 IPv6 function is globally enabled.

    Run the display this command in the system view to check whether the IPv6 function is globally enabled. The IPv6 function is disabled by default.

    • If ipv6 is not displayed, the IPv6 function is not globally enabled. Run the ipv6 command in the system view.
    • If ipv6 is displayed, the IPv6 function is globally enabled. Go to step 2.

  2. Check that the DUID function is globally enabled.

    Run the display this command in the system view to check whether the DUID function is enabled. The DUID function is disabled by default.

    • If dhcpv6 duid is not displayed, the DUID function is disabled. Run the dhcpv6 duidduid-value command in the system view to enable the DUID function.
    • If dhcpv6 duid is displayed, go to step 3.

  3. Check that the user-side interface is physically Up.

    Run the display this ipv6 interface command in the user-side interface view to check whether the interface is physically Up.

    • If current state is down, the physical link is faulty. Remove the link fault.
    • If current state is up, the physical link is working properly. Go to step 4.

  4. Check that the IPv6 protocol is Up on the user-side interface.

    Run the display this ipv6 interface command in the user-side interface view to check whether the IPv6 protocol is Up.

    • If IPv6 protocol current state is down, check whether the configured link-local address conflicts with that of the peer device.
    • If IPv6 protocol current state is up, go to step 5.

  5. Check that the M/O value has been correctly configured on the user-side interface. That is, check what the ipv6 nd autoconfig managed-address-flag or ipv6 nd autoconfig other-flag command is displayed.

    Run the display this command in the user-side interface view to check whether the M/O value has been configured.

    • If ipv6 nd autoconfig managed-address-flag or ipv6 nd autoconfig other-flag is displayed, go to step 6.
    • Otherwise, run the ipv6 nd autoconfig managed-address-flag or ipv6 nd autoconfig other-flag command to correctly configure the M/O value.

  6. Check that bind authentication has been configured on the user-side interface with the BAS.

    Run the display this command on the user-side interface with the BAS to check whether bind authentication has been configured.

    • If no bind authentication information is displayed, run the authentication-method-ipv6 bind command to configure bind authentication.
    • If authentication-method-ipv6 bind is displayed, go to step 7.

  7. Check that address pools have been correctly configured.

    Run the display ipv6 pool [ pool-name ] command in the system view to check whether a local address pool and a delegation address pool already associated with prefix pools have been configured.

    • If one of the two address pools is missing, refer to the configuration manual to properly configure the address pool.
    • If both address pools have been configured, go to step 8.

  8. Check that the authentication domain has been correctly configured.

    Run the display this command in the AAA domain view to check whether the authentication domain has been correctly configured.

    • If the local address pool or the delegation pool is not configured, run the ipv6-pool pool-name command to configure the pool.
    • If the configuration is correct, go to step 9.

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

    Run the display ipv6 prefix prefix-name command in the system view to view the Free Prefix Count field. This field displays the number of assignable addresses in the prefix pool.

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

User Cannot Get Online in the Case of IPoE Stateless PD

This section describes the troubleshooting flowchart and provides a step-by-step troubleshooting procedure for the fault that the user cannot get online when the ME60 is configured with IPoE stateless PD.

Common Causes

This fault is commonly caused by one of the following:

  • The IPv6 function is not globally enabled.
  • DUID is not configured globally.
  • The IPv6 protocol on the user-side interface is Down.
  • Bind authentication is not configured on the user-side interface with the BAS.
  • The prefix pool is incorrectly configured.
  • The unshared mode of prefix assignment is not configured in the domain view.
Troubleshooting Flowchart

This section describes the troubleshooting flowchart for the fault that the user cannot get online when the ME60 is configured with IPoE stateless PD.

The troubleshooting roadmap is as follows:

  • Check that the IPv6 protocol is Up on the user-side interface.
  • Check that bind authentication has been configured on the interface with the BAS.
  • Check that a correct prefix pool has been configured.
  • Check that the unshared mode of prefix assignment has been configured in the domain view.

Figure 4-137 shows the troubleshooting flowchart.

Figure 4-137 Troubleshooting flowchart for the fault that the user cannot get online in the case of IPoE stateless PD

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 IPv6 function is globally enabled.

    Run the display this command in the system view to check whether the IPv6 function is globally enabled. The IPv6 function is disabled by default.

    • If ipv6 is not displayed, the IPv6 function is not globally enabled. Run the ipv6 command to enable the IPv6 function in the system view.
    • If ipv6 is displayed, the IPv6 function is globally enabled. Go to step 2.

  2. Check that the DUID function is globally enabled.

    Run the display this command in the system view to check whether the DUID function is enabled. The DUID function is disabled by default.

    • If dhcpv6 duid is not displayed, the DUID function is disabled. Run the dhcpv6 duidduid-value command in the system view to enable the DUID function.
    • If dhcpv6 duid is displayed, go to step 3.

  3. Check that the user-side interface is physically Up.

    Run the display this ipv6 interface command in the user-side interface view to check whether the interface is physically Up.

    • If current state is down, the physical link is faulty. Remove the link fault.
    • If current state is up, the physical link is working properly. Go to step 4.

  4. Check that the IPv6 protocol is Up on the user-side interface.

    Run the display this ipv6 interface command in the user-side interface view to check whether the IPv6 protocol is Up.

    • If IPv6 protocol current state is down, check whether the configured link-local address conflicts with that of the peer device.
    • If IPv6 protocol current state is up, go to step 5.

  5. Check that bind authentication has been configured on the user-side interface with the BAS.

    Run the display this command on the user-side interface with the BAS to check whether bind authentication has been configured.

    • If no bind authentication information is displayed, run the authentication-method-ipv6 bind command to configure bind authentication.
    • If authentication-method-ipv6 bind is displayed, go to step 6.

  6. Check that a correct ND-unshared prefix pool has been configured.

    Run the display ipv6 prefix [ prefix-name [ all | used ] ] command in the system view to check whether a correct ND-unshared prefix pool has been configured.

    • If slaac-unshare-only is FALSE, run the slaac-unshare-only command to correct the configuration.
    • If slaac-unshare-only is TRUE, go to step 7.

  7. Check that a correct PD prefix pool has been configured.

    Run the display ipv6 pool [ pool-name ] command in the system view to check whether a correct PD prefix pool has been configured.

    • If pd-unshare-only is FALSE, run the pd-unshare-only command in the address pool view to correct the configuration.
    • If pd-unshare-only is TRUE, go to step 8.

  8. Check that the authentication domain has been correctly configured.

    Run the display this command in the AAA domain view to check whether the authentication domain has been correctly configured.

    • If prefix-assign-mode unshared is not displayed, run the prefix-assign-mode unshared command to configure the unshared mode of prefix assignment.
    • If the local address pool or the delegation pool is not configured, run the ipv6-poolpool-name command to configure the pool.
    • If the configuration is correct, go to step 9.

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

    Run the display ipv6 prefixprefix-name command in the system view to view the Free Prefix Count field. This field displays the number of assignable addresses in the prefix pool.

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

User Cannot Get Online in IPv6 IPoE Stateful Access Mode with a DSLAM Serving as the LDRA

A digital subscriber line access multiplexer (DSLAM) can serve as a layer 2 (L2) forwarding device capable of handling DHCPv6 relay packets to encapsulate device information in the header of a DHCPv6 relay packet to be sent to the server. 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 status type is incorrect when the ME60 is configured with IPv6 stateful access and a DSLAM serves as the LDRA.

Common Causes

This fault is commonly caused by one of the following:

  • The IPv6 function is not globally enabled.
  • The DUID function is not globally enabled.
  • The IPv6 address pool is incorrectly configured.
  • The address allocation mode is not configured on the user-side interface.
  • Bind authentication is not configured on the user-side interface.
Troubleshooting Flowchart

This section describes the troubleshooting flowchart for the fault that the user cannot get online when the ME60 is configured with IPv6 IPOE stateful access.

The troubleshooting roadmap is as follows:

  • Check that the IPv6 function is globally enabled.
  • Check that the DUID function is enabled in the system view.
  • Check that a correct IPv6 address pool has been configured.
  • Check that bind authentication has been configured on the user-side interface.
  • Check that the address allocation mode has been configured on the user-side interface. (If the user successfully gets online, check the state of the online user. The address allocation mode is incorrect.)

Figure 4-138 shows the troubleshooting flowchart.

Figure 4-138 Troubleshooting flowchart for the fault that the user cannot get online or the address allocation mode is incorrect in the case of IPv6 IPOE 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 IPv6 function is globally enabled.

    Run the display this command in the system view to check whether the IPv6 function is globally enabled. The IPv6 function is disabled by default.

    • If ipv6 is not displayed, the IPv6 function is not globally enabled. Run the ipv6 command in the system view.
    • If ipv6 is displayed, the IPv6 function is globally enabled. Go to step 2.

  2. Check that the DHCPv6 DUID generation mode is globally enabled.

    Run the display this command in the system view 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.

  3. Check that an IPv6 address pool has been correctly configured.

    Run the display this command in the AAA 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 AAA domain.
    • If the IPv6 address pool has been correctly configured, go to step 4.

  4. Check that bind authentication has been configured on the user-side interface.

    Run the display this command in the user-side interface view to check whether bind authentication has been configured. That is, check whether authentication-method-ipv6 bind is displayed.

    • If bind authentication is not configured, run relevant commands to configure it.
    • If bind authentication has been configured, go to step 5.

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

    Run the display access-user user-iduser-id [ verbose ] command after the user gets online. If the command output indicates that the user address is not obtained using DHCP, enter the user-side interface view and run the display this command to check whether the address allocation mode has been configured. 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 the ipv6 nd autoconfig managed-address-flag command in the user-side interface view to configure the address allocation mode.
    • If the address allocation mode has been configured, go to step 6.

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

DHCPv6 User Fails to Get Online Through the Remote Address Pool

This section describes the troubleshooting flowchart and provides a step-by-step troubleshooting procedure for the fault that the user cannot get online in remote address pool mode through the ME60.

Common Causes

This fault is commonly caused by one of the following:

  • The IPv6 function was not globally enabled.
  • The DUID function was not globally enabled.
  • The remote address pool was incorrectly configured.
  • The remote server was incorrectly configured.
  • Bind authentication was not configured on the user-side interface.
  • The address allocation mode was incorrectly configured on the user-side interface.
  • The IPv6 address configured for the network-side interface and the IPv6 address of the remote DHCPv6 server were in different network segments.
Troubleshooting Flowchart

This section describes the troubleshooting flowchart for the fault that the user cannot get online in DHCPv6 remote address pool mode through the ME60.

The troubleshooting roadmap is as follows:

  • Check that the IPv6 function is globally enabled.
  • Check that the DUID function is enabled in the system view.
  • Check that the remote address pool has been correctly configured.
  • Check that the remote server has been correctly configured.
  • Check that bind authentication has been configured on the user-side interface.
  • Check that the address allocation mode has been correctly configured on the user-side interface.

Figure 4-139 shows the troubleshooting flowchart.

Figure 4-139 Troubleshooting flowchart for the fault that the user cannot get online in DHCPv6 remote address pool mode

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 IPv6 function is globally enabled.

    Run the display current-configuration command to check whether the IPv6 function is globally enabled. The IPv6 function is disabled by default.

    • If ipv6 is not displayed, the IPv6 function is not globally enabled. Run the ipv6 command in the system view to enable the IPv6 function.
    • If ipv6 is displayed, the IPv6 function is globally enabled. Go to step 2.

  2. Check that the DHCPv6 DUID function is globally enabled.

    Run the display this command to check whether the DHCPv6 DUID function is globally enabled.

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

  3. Check that the remote address pool has been correctly configured.

    Verify that a remote prefix pool is configured. Run the display this command in the remote prefix pool view to check whether a correct link address has been configured.

    • If the link address is not configured, run the link-address link-address/prefix-length command to correctly configure the link address.
    • If the link address has been correctly configured, go to step 4.

  4. Check that the remote server has been correctly configured.

    Run the display dhcpv6-server group group-name command in the system view to check the status of the remote server.

    • If the remote server is not Up, correctly configure the remote server group and associate the group with the remote address pool.
    • If the remote server is Up, go to step 5.

  5. Check that bind authentication has been configured on the user-side interface.

    Run the display this command in the user-side interface view to check whether bind authentication has been configured. If the authentication-method-ipv6 bind command is displayed, bind authentication has been configured.

    • If bind authentication is not configured, run the authentication-method-ipv6 bind command to configure bind authentication in the user-side interface view.
    • If bind authentication has been configured, go to step 6.

  6. Check that the M value has been correctly configured on the interface.

    Run the display this command in the user-side interface view to check whether the address allocation mode has been configured. 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 the ipv6 nd autoconfig managed-address-flag command to configure the address allocation mode in the user-side interface view.
    • If the address allocation mode has been configured, go to step 7.

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

IPv6 ND Access Troubleshooting

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

Typical Networking

Figure 4-140 shows the typical networking of ND access. ND access troubleshooting is based on this networking.

Figure 4-140 Typical networking diagram of ND access

As shown in Figure 4-140:

  • The user accesses the ME60 through a Layer 2 network.

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

  • The ME60 is connected to an IPv6 DNS server.

The user accesses the ME60 in ND mode. The ME60 assigns an IPv6 prefix to the user and manages the user.

Troubleshooting Flowchart

On the network shown in Typical Networking, after a local address pool is configured, 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-141 Troubleshooting flowchart of ND 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, it indicates that the physical connection between them works properly. If they fail to ping through each other, you need to 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, you need to 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 ND 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 delegation command to create a delegation prefix pool, enter the prefix pool view, and then run the prefix prefix-address delegating-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 delegating-prefix-length command to configure an IPv6 prefix address.

    Run the display this command to view configurations. Check whether the slaac-unshare-only command is displayed. If the command is not displayed, run the slaac-unshare-only command.

    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 delegation command to create the delegation 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 an 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 used command in the system view to check whether the number of assignable IPv6 prefixes is 0.

    • If the value of the Free Prefix Count field is displayed as 0, there is no assignable address 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 domain to which the client belongs.
    • If the value of the Free Prefix Count field is not displayed as 0, there are assignable addresses. If the client still cannot obtain an IPv6 address, contact Huawei technical personnel.

ND-Unshared User Cannot Get Online

This section describes the troubleshooting flowchart and provides a step-by-step troubleshooting procedure for the fault that the user cannot get online when the ME60 is configured with ND-unshared access.

Common Causes

This fault is commonly caused by one of the following:

  • The IPv6 function is not globally enabled.
  • The IPv6 protocol on the user-side interface is Down.
  • The M/O value has been configured on the user-side interface.
  • Bind authentication is not configured on the user-side interface with the BAS.
  • The prefix pool is incorrectly configured.
  • The unshared mode of prefix assignment is not configured in the domain view.
Troubleshooting Flowchart

This section describes the troubleshooting flowchart for the fault that the user cannot get online when the ME60 is configured with ND-unshared access.

The troubleshooting roadmap is as follows:

  • Check that the IPv6 protocol is Up on the user-side interface.
  • Check that the M/O value is disabled on the user-side interface. The M/O value is disabled by default.
  • Check that bind authentication has been configured on the interface with the BAS.
  • Check that a correct prefix pool has been configured.
  • Check that the unshared mode of prefix assignment has been configured in the domain view.

Figure 4-142 shows the troubleshooting flowchart.

Figure 4-142 Troubleshooting flowchart for the fault that the ND-unshared user cannot get online

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 IPv6 function is globally enabled.

    Run the display this command in the system view to check whether the IPv6 function is globally enabled. The IPv6 function is disabled by default.

    • If ipv6 is not displayed, the IPv6 function is not globally enabled. Run the ipv6 command in the system view.
    • If ipv6 is displayed, the IPv6 function is globally enabled. Go to step 2.

  2. Check that the user-side interface is physically Up.

    Run the display this interface command in the user-side interface view to check whether the interface is physically Up.

    • If current state is down, the physical link is faulty. Remove the link fault.
    • If current state is up, the physical link is working properly. Go to step 3.

  3. Check that the IPv6 protocol is Up on the user-side interface.

    Run the display this ipv6 interface command in the user-side interface view to check whether the IPv6 protocol is Up.

    • If IPv6 protocol current state is down, check whether the configured link-local address conflicts with that of the peer device.
    • If IPv6 protocol current state is up, go to step 4.

  4. Check that the M/O value is disabled on the user-side interface.

    Run the display this command in the user-side interface view to check whether the M/O value is configured. If ipv6 nd autoconfig managed-address-flag or ipv6 nd autoconfig other-flag is displayed, the M/O value is configured.

    • If the M/O value has been configured, delete the configuration.
    • If the M/O value is not configured, go to step 5.

  5. Check that bind authentication has been configured on the user-side interface with the BAS.

    Run the display this command on the user-side interface with the BAS to check whether bind authentication has been configured.

    • If no bind authentication information is displayed, run the authentication-method-ipv6 bind command to configure bind authentication.
    • If authentication-method-ipv6 bind is displayed, go to step 6.

  6. Check that a correct prefix pool has been configured.

    Run the display ipv6 prefix [ prefix-name [ all | used ] ] command in the system view to check whether a correct prefix pool has been configured.

    • If slaac-unshare-only is FALSE, run the slaac-unshare-only command to correct the configuration.
    • If slaac-unshare-only is TRUE, go to step 7.

  7. Check that the unshared mode of prefix assignment has been configured in the authentication domain view.

    Run the display this command in the AAA domain view to check whether the authentication domain has been correctly configured.

    • If prefix-assign-mode unshared is not displayed, run the prefix-assign-mode unshared command to configure the unshared mode of prefix assignment.
    • If prefix-assign-mode unshared is displayed, go to step 8.

  8. 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: 13764

Downloads: 257

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