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).
Client Fails to Obtain an IPv6 Address Troubleshooting

Client Fails to Obtain an IPv6 Address Troubleshooting

Troubleshooting in the Scenario Where the ME60 Functions as a Local DHCPv6 Server

This section describes the notes about configuring the ME60 as a local DHCPv6 server, and provides the troubleshooting flowchart and the troubleshooting procedure in a networking where the ME60 functions as a local DHCPv6 server.

Typical Networking

Figure 4-147 shows a typical networking where the ME60 functions as a local DHCPv6 server. The following describes how to perform DHCPv6 server troubleshooting based on this networking.

Figure 4-147 Typical networking where the ME60 functions as a local DHCPv6 server

As shown in Figure 4-147:

  • A client is a Layer 2 access user and needs to apply to the ME60 for an IPv6 address to get online.

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

  • The ME60 is connected to an IPv6 DNS server.

The ME60 functions as a local DHCPv6 server to allocate IPv6 addresses to clients and manage clients.

Troubleshooting Flow

On the network shown in Typical Networking, after a local address pool is configured, a client cannot obtain an IPv6 address and therefore fails to get online. You can troubleshoot the fault based on Figure 4-148.

Figure 4-148 Troubleshooting flowchart for the scenario where the ME60 functions as a local DHCPv6 server

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; otherwise, 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 interface is correctly configured.

    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 "DHCPv6 Access Service Configuration" in the Configuration Guide - BRAS.

    • If the configuration of the interface is incorrect, you need to modify the configuration to be correct. For details, refer to the chapter "DHCPv6 Access Service Configuration" 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 a local prefix pool, enter the local 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 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 a local address pool, enter the local 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 domain to an IPv6 address pool.
    • If the user domain is bound to an IPv6 address pool, go to Step 6.

  6. Check that the server DUID is set.

    Run the display this command in the system view to check configurations.

    • If the command output shows "dhcpv6 duid", it indicates that the server DUID is set; otherwise, run the dhcpv6 duid command to set the server DUID.

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

Troubleshooting in the Scenario Where the ME60 Functions as a Delegating Router

This section describes the notes about configuring the ME60 as a delegating server, and provides the troubleshooting flowchart and the troubleshooting procedure in a networking where the ME60 functions as a delegating server.

Typical Networking

Figure 4-149 shows a typical networking where the ME60 functions as a delegating router. The following describes how to perform delegating router troubleshooting based on this networking.

Figure 4-149 Typical networking where the ME60 functions as a delegating router

Figure 4-149 is a typical networking of DHCPv6 prefix delegation (PD). In this networking:

  • A client is a Layer 2 access user.

  • The requesting router obtains an IPv6 address from the delegating router.

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

  • The ME60 is connected to an IPv6 DNS server.

The ME60 is responsible for allocating IPv6 prefixes for requesting routers and managing requesting routers.

Troubleshooting Flow

As shown in the networking diagram in the section "Typical Networking", after a local address pool is configured, a client cannot obtain an IPv6 address and therefore fails to get online. You can troubleshoot the fault based on Figure 4-150.

Figure 4-150 Troubleshooting flowchart for the scenario where the ME60 functions as a delegating router

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; otherwise, 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 requesting router can normally get online through PPPoE or IPoE.

    Check whether the requesting router can obtain an IPv6 address from the delegating router and get online normally.

    • If the requesting router fails to get online, refer to PPPoE troubleshooting procedure or IPoE troubleshooting procedure in the Troubleshooting - BRAS and ensure that the requesting router can access the delegating router.
    • If the requesting router can normally get online, go to Step 3.

  3. Check that the interface is correctly configured.

    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 "DHCPv6 Access Service Configuration" in the Configuration Guide - BRAS.

    • If the configuration of the interface is incorrect, you need to modify the configuration to be correct. For details, refer to the chapter "DHCPv6 Access Service Configuration" in the Configuration Guide - BRAS.
    • If the configuration of the interface is correct, go to Step 4.

  4. 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 delegation command to create a delegation prefix pool, enter the delegation 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 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 5.

  5. 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 a delegation address pool, enter the local 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 6.

  6. 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 domain to an IPv6 address pool.
    • If the user domain is bound to an IPv6 address pool, go to Step 7.

  7. Check that the server DUID is set.

    Run the display this command in the system view to check configurations.

    • If the command output shows "dhcpv6 duid", it indicates that the server DUID is set; otherwise, run the dhcpv6 duid command to set the server DUID.

    If the problem persists, go to Step 8.

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

Troubleshooting in the Scenario Where the ME60 Functions as a DHCPv6 Relay Agent

This section describes the notes about configuring the ME60 as a DHCPv6 relay agent, and provides the troubleshooting flowchart and the troubleshooting procedure in a networking where the ME60 functions as a DHCPv6 relay agent.

Typical Networking

Figure 4-151 shows a typical networking where the ME60 functions as a DHCPv6 relay agent. The following describes how to perform DHCPv6 relay agent troubleshooting based on this networking.

Figure 4-151 Typical networking where the ME60 functions as a DHCPv6 relay agent

As shown in Figure 4-151:

  • The Device B functions as a DHCPv6 relay agent.

  • The Device A is connected to the RADIUS server to implement authentication and accounting for clients.

  • The Device A is connected to an IPv6 DNS server.

Users can access the network through one or multiple relay agents. In the preceding figure, the ME60 (Device B) functions as a DHCPv6 relay agent.

Troubleshooting Flow

On the network shown in Typical Networking, after a relay address pool is configured, a client cannot obtain an IPv6 address and therefore fails to get online. You can troubleshoot the fault based on Figure 4-152.

Figure 4-152 Troubleshooting flowchart for the scenario where the ME60 functions as a local DHCPv6 server

Troubleshooting Procedure

Procedure

  1. Check that the physical connections work properly.

    Check whether the connection between the DHCPv6 relay agent and the client (or the superior relay agent) and the connection between the DHCPv6 relay agent and the DHCPv6 server (or the subordinate relay agent) work normally. If the connection fails, 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 inbound and outbound interfaces of the DHCPv6 relay agent are correctly configured.

    Run the display this command in the inbound interface view to check the following:

    • Whether the IPv6 function is enabled
    • Whether a link-local address is configured
    • Whether an IPv6 address is configured
      NOTE:

      If the DHCPv6 relay agent is a first relay agent, the IPv6 address assigned to the relay agent must be on the same network segment with the addresses in the address pool configured on the DHCPv6 server. If the DHCPv6 relay agent is not a first relay agent, any IPv6 address can be assigned to the relay agent based on the network planning.

    • Whether DHCPv6 is enabled
    • Whether the relay function is enabled and the address of the DHCPv6 server or outbound interface of DHCPv6 packet is set

    Run the display this command in the outbound interface view to check the following:

    • Whether the IPv6 function is enabled
    • Whether a link-local address is configured
    • Whether an IPv6 address is configured

    If the configuration of the interface is incorrect, modify the configuration based on "Configuration Notes".

    If the configuration of the interface is correct, go to Step 3.

  3. Check that the inbound interface has received packets.

    Run the display interface interface-type interface-number command in the system view to check whether the inbound interface has received packets and view statistics on input packets.

    NOTE:

    If the DHCPv6 relay agent is a first relay agent, check whether the statistics on multicast packets increase; if the DHCPv6 relay agent is not a first relay agent, check whether the statistics on unicast packets increase.

    • If the inbound interface of the DHCPv6 relay agent receives no packets (that is, the "Input" field is displayed as 0), check the connection between the relay agent and the superior device and then check whether the superior device can forward packets normally.
    • If the inbound interface of the DHCPv6 relay agent has received packets, go to Step 4.

  4. Check that the outbound interface forwards packets normally.

    Run the display interface interface-type interface-number command in the system view to check whether the outbound interface has forwarded packets and view statistics on the output packets.

    • If packet forwarding on the outbound interface fails (that is, the "Output" field is displayed as 0), check the physical connection between the DHCPv6 relay agent and the subordinate device and check whether the IPv6 address of this interface is on the same network segment with that of the inbound interface of the superior device.
    • If packet forwarding succeeds, it indicates that the DHCPv6 relay agent works normally. Then, check whether other devices work normally.

    If the client still cannot get online, contact Huawei technical support personnel.

  5. Check whether the number of access users exceeds the maximum number allowed by the DHCPv6 relay agent.

    Run the display dhcpv6 relay userinfo table [ { interface interface-type interface-number [.subinterface-number ] [ pevlan pevlan-id [ end-pevlan-id ] [ cevlan cevlan-id [ end-cevlan-id ] ] ] | slot slot-id [ card card-id ] } | mac-address mac-address | index index | client-duid client-duid | server-duid server-duid | server-address ipv6-address [ vpn-instance vpn-instance-name ] | client-address ipv6-address [ vpn-instance vpn-instance-name ] ] [ statistics ] command in the system view to check whether the number of access users exceeds the maximum number allowed by the DHCPv6 relay agent.

    • If the number of access users exceeds the maximum number allowed by the DHCPv6 relay agent, log out some users based on the situations on the live network.
    • If the number of access users does not exceed the maximum number allowed by the DHCPv6 relay agent, go to Step 6.

  6. Check the reason why the user entry is deleted.

    Run the display dhcpv6 relay client-info [ interface interface-type interface-number [.subinterface-number ] [ pevlan pevlan-id [ end-pevlan-id ] [ cevlan cevlan-id [ end-cevlan-id ] ] ] | mac-address mac-address | client-duid client-duid ] command in the system view.

    • If the DHCPv6 server allocates conflicted IPv6 addresses or prefixes or responds with a Reply packet whose lifetime is 0 or status is not Success, rectify any faults on the DHCPv6 server.
    • If the client does not receive a Reply packet from the DHCPv6 server within the timeout period, rectify any faults on the DHCPv6 server.
    • If the DHCPv6 relay agent does not receive a packet from the client within the timeout period, rectify any faults on the client.

    After the preceding steps, if the client still cannot acquire an IP address, 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

User Cannot Obtain an Address from the Address Pool According to the Pool ID Delivered by the RADIUS Server

This section describes the troubleshooting flowchart and provides a step-by-step troubleshooting procedure for the fault that the ME60 cannot allocate an address from the corresponding address pool to the user after the RADIUS server delivers No.100 attribute Framed-IPv6-Pool or HUAWEI No.191 attribute Delegated-IPv6-Prefix-Pool.

Common Causes

This fault is commonly caused by one of the following:

  • The address pool with the specified pool ID is not configured on the device.
  • The address pool type does not match the pool ID delivered by the RADIUS server. If the RADIUS server delivers No.100 attribute Framed-IPv6-Pool, the address pool can be a local or delegation address pool. If the RADIUS server delivers HUAWEI No.191 attribute Delegated-IPv6-Prefix-Pool, the address pool can be a delegation address pool only.
  • No prefixes are available in the prefix pool.
Troubleshooting Flowchart

This section describes the troubleshooting flowchart for the fault that the user cannot obtain an address from the address pool after the RADIUS server delivers the pool ID.

The troubleshooting roadmap is as follows:

  • Check that the address pool with the specified pool ID has been configured on the device.
  • Check that the address pool type matches the pool ID delivered by the RADIUS server.
  • Check that no prefixes are available in the prefix pool.
Troubleshooting Procedure

Before performing the following steps, you can refer to User Login and Logout Cause 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 an address pool with the specified pool ID has been configured on the device.

    Run the display ipv6 pool pool-name command in the system view to check whether an address pool with the specified pool ID has been configured on the device.

    • If This pool does not exist is displayed, the address pool is not configured. Run the ipv6 pool pool-name { bas { local | delegation } } command on the device to configure the address pool.
    • If information about the address pool is displayed, the address pool has already been configured. Go to step 2.

  2. Check that the address pool type configured on the device matches the pool ID delivered by the RADIUS server.

    Run the display ipv6 pool pool-name command in the system view to check whether the pool type indicated in the command output information matches the pool ID delivered by the RADIUS server. If the RADIUS server delivers No.100 attribute Framed-IPv6-Pool, the address pool can be a local or delegation address pool. If the RADIUS server delivers HUAWEI No.191 attribute Delegated-IPv6-Prefix-Pool, the address pool can be a delegation address pool only.

    • If the pool type does not match the pool ID delivered by the RADIUS server, reconfigure the address pool type. If the RADIUS server delivers HUAWEI No.191 attribute Delegated-IPv6-Prefix-Pool, run the ipv6 pool pool-name bas delegation command to configure the address pool as a delegation address pool. If the RADIUS server delivers No.100 attribute Framed-IPv6-Pool, the address pool can be a local or delegation address pool.
    • If the pool type matches the pool ID delivered by the RADIUS server, go to step 3.

  3. Check that no prefixes are available in the address pool.

    If the address pool is a delegation address pool, run the display ipv6 prefix prefix-name used command in the system view to check whether the value of Free Prefix Count is 0.

    • If the value of Free Prefix Count is 0, no prefixes are available in the prefix pool. Run the ipv6 prefix prefix-name [ local | delegation ] command in the system view to enter the prefix pool view, and then run the prefix prefix-address/prefix-length [ delegating-prefix-length length ] command to configure the address pool.
    • If the value of Free Prefix Count is not 0, go to step 4.

  4. 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: 12271

Downloads: 246

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