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

Virtual Access Troubleshooting

This chapter describes how to troubleshoot common virtual access faults.

NOTE:

This feature is supported only on the Admin-VS.

Primary and Secondary Masters Fail to Be Elected for an AP

This section provides a troubleshooting flowchart and procedure for primary and secondary masters' failure to be elected for an AP in a virtual access system.

Common Causes

Common causes are as follows:

  • The AP configuration is incorrect.

  • An IS-IS neighbor relationship fails to be established.

Troubleshooting Flowchart
The troubleshooting roadmap is as follows:
  • Check that the AP configuration on a master is correct.

  • Check that the IS-IS neighbor relationship between a master and the AP is successfully established.

Figure 4-108 shows the troubleshooting flowchart.

Figure 4-108 Flowchart for troubleshooting primary and secondary masters' failure to be elected for an AP

Troubleshooting Procedure
NOTE:

After the commands are configured to troubleshoot the faults, check the configuration validation mode to ensure that the configurations take effect. Unless otherwise specified, this manual defaults to immediate validation mode.

  • In immediate validation mode, the configurations take effect after the commands are entered.
  • In two-phase validation mode, after the commands are configured, the commit command needs to be run to commit the configurations.

Save the results of each troubleshooting step so that if your troubleshooting attempts fail to correct the fault, you will have a record of your actions to present to Huawei.

Procedure

  1. Check that the AP configuration on a master is correct.
    1. Run the display this command in the virtual access view of a master to check whether the AP of the corresponding ID has been configured.

      • If the AP of the corresponding ID has been configured, go to Step b.

      • If the AP of the corresponding ID has not been configured, configure it and go to Step b.

    2. Run the display this command in the AP view on a master to check whether a correct management IP address and management priority have been configured.

      • If a correct management IP address and management priority have been configured, go to Step c.

      • If a correct management IP address and management priority have not been configured, modify them correctly and go to Step c.

    3. Run the display virtual-access ap command on a master to check whether the AP's primary and secondary master information is correct.

      • If the AP's primary and secondary master information is correct, no further action is required.

      • If the AP's primary and secondary master information is incorrect, go to Step 2.

  2. Check that the IS-IS neighbor relationship between a master and the AP is successfully established.
    1. Run the display isis process-id interface command on a master to check whether any interface exists in the virtual access IS-IS process (the default process ID is 65534).

      • If any interface exists in the virtual access IS-IS process, go to Step b.

      • If no interface exists in the virtual access IS-IS process, enable virtual access on an internal communication interface of the master and go to Step b.

    2. Run the display ip interface [ interface-type interface-number ] command on a master to check whether the IS-IS interface status is Up.

      • If the IS-IS interface status is Up, go to Step c.

      • If the IS-IS interface status is Down, perform troubleshooting according to "Physical Interconnection and Interface Protocol Troubleshooting" and go to Step c.

    3. Run the display virtual-access ap command on a master to check whether the AP's primary and secondary master information is correct.

      • If the AP's primary and secondary master information is correct, no further action is required.

      • If the AP's primary and secondary master information is incorrect, go to Step 3.

  3. Run the reset isis virtual-access all command on a master and AP to restart the virtual access IS-IS process.

    Run the display virtual-access ap command on a master to check whether the AP's primary and secondary master information is correct.

    • If the AP's primary and secondary master information is correct, no further action is required.

    • If the AP's primary and secondary master information is incorrect, go to Step 4.

  4. Please contact technical support personnel and provide the following information:

    • Results of this troubleshooting procedure
    • Configuration, log, and alarm files

Relevant Alarms and Logs
Relevant Alarms

VIRTUAL-ACCESS_1.3.6.1.4.1.2011.5.25.343.2.5.1 hwVirtualAccessApSelectedMaster

Relevant Logs

VIRTUAL-ACCESS/4/hwVirtualAccessApSelectedMasterTrap

An AP Fails to Go Online Automatically

This section provides a troubleshooting flowchart and procedure for an AP's failure to go online automatically in a virtual access system.

Common Causes

Common causes are as follows:

  • Primary and secondary masters fail to be elected for the AP.

  • A control channel fails to be established from a master to the AP.

Troubleshooting Flowchart
The troubleshooting roadmap is as follows:
  • Check that primary and secondary masters are successfully elected for the AP.

  • Check that a control channel is successfully established from a master to the AP.

Figure 4-109 shows the troubleshooting flowchart.

Figure 4-109 Flowchart for troubleshooting an AP's failure to go online automatically
Troubleshooting Procedure
NOTE:

After the commands are configured to troubleshoot the faults, check the configuration validation mode to ensure that the configurations take effect. Unless otherwise specified, this manual defaults to immediate validation mode.

  • In immediate validation mode, the configurations take effect after the commands are entered.
  • In two-phase validation mode, after the commands are configured, the commit command needs to be run to commit the configurations.

Save the results of each troubleshooting step so that if your troubleshooting attempts fail to correct the fault, you will have a record of your actions to present to Huawei.

Procedure

  1. Check that primary and secondary masters are successfully elected for the AP.
    1. Run the display virtual-access ap command on a master to check whether the AP's primary and secondary master information is correct.

    2. Run the display virtual-access ap command on a master to check whether State is Online in the command output.

      • If State is Online in the command output, no further action is required.

      • If State is not Online in the command output, go to Step 2.

  2. Check that an OpenFlow channel is successfully established from a master to the AP.
    1. Run the display control-tunnel session command on a master to check whether State is REGISTERED in the command output.

      • If State is REGISTERED in the command output, go to Step 3.

      • If State is not REGISTERED in the command output, run the reset control-tunnel session peer-ip ip-addr command on the master and go to Step b.

    2. Run the display virtual-access ap command on a master to check whether State is Online in the command output.

      • If State is Online in the command output, no further action is required.

      • If State is not Online in the command output, go to Step 3.

  3. Please contact technical support personnel and provide the following information:

    • Results of this troubleshooting procedure
    • Configuration, log, and alarm files

Relevant Alarms and Logs
Relevant Alarms

None

Relevant Logs

None

Virtual Access Tunnel Goes Down

This section provides a troubleshooting flowchart and procedure for virtual access tunnel Down in a virtual access system.

Common Causes

Common causes are as follows:

  • The IS-IS link information is incomplete.

  • The BFD for vaLSP session goes Down.

Troubleshooting Flowchart
The troubleshooting roadmap is as follows:
  • Check that the IS-IS link information is complete.

  • Check that the BFD for vaLSP session goes Up.

Figure 4-110 shows the troubleshooting flowchart.

Figure 4-110 Flowchart for troubleshooting virtual access tunnel Down

Troubleshooting Procedure
NOTE:

After the commands are configured to troubleshoot the faults, check the configuration validation mode to ensure that the configurations take effect. Unless otherwise specified, this manual defaults to immediate validation mode.

  • In immediate validation mode, the configurations take effect after the commands are entered.
  • In two-phase validation mode, after the commands are configured, the commit command needs to be run to commit the configurations.

Save the results of each troubleshooting step so that if your troubleshooting attempts fail to correct the fault, you will have a record of your actions to present to Huawei.

Procedure

  1. Check that the IS-IS link information is complete.
    1. Run the display isis virtual-access advertisements command on a master to view the ISIS EXTEND INTERFACE field and check whether link information exists between two nodes based on Nbr ID.

    2. Run the display virtual-access va-tunnel p2p command on a master to check whether State is Up in the command output.

      • If State is Up in the command output, no further action is required.

      • If State is not Up in the command output, go to Step 2.

  2. Check that the BFD for vaLSP session goes Up.
    1. Run the display bfd session all command on a master to check whether the status of the BFD for vaLSP session between the master and AP is Up.

      • If the status of the BFD for vaLSP session between the master and AP is Up, go to Step 3.

      • If the status of the BFD for vaLSP session between the master and AP is not Up, perform troubleshooting according to BFD Session Cannot Go Up and go to Step b.

    2. Run the display virtual-access va-tunnel p2p command on a master to check whether State is Up in the command output.

      • If State is Up in the command output, no further action is required.

      • If State is not Up in the command output, go to Step 3.

  3. Please contact technical support personnel and provide the following information:

    • Results of this troubleshooting procedure
    • Configuration, log, and alarm files

Relevant Alarms and Logs
Relevant Alarms

VIRTUAL-ACCESS_1.3.6.1.4.1.2011.5.25.343.2.2.1 hwVirtualAccessTunnelDown

Relevant Logs

VIRTUAL-ACCESS/2/hwVirtualAccessTunnelDown_active

VIRTUAL-ACCESS/2/hwVirtualAccessTunnelDown_clear

Diameter Session Fails to Be Established

This section provides a troubleshooting flowchart and procedure for a Diameter session's failure to be established in a virtual access system.

Common Causes

Common causes are as follows:

  • The management IP address of the peer master is unreachable.

  • The authentication configurations for Diameter are different on the local and peer masters.

  • The primary and secondary configurations for an AP are different on the local and peer masters.

Troubleshooting Flowchart
The troubleshooting roadmap is as follows:
  • Check that the management IP address of the peer master is reachable.

  • Check that the authentication configurations for Diameter are the same on the local and peer masters.

  • Check that the primary and secondary configurations for an AP are the same on the local and peer masters.

Figure 4-111 shows the troubleshooting flowchart.

Figure 4-111 Flowchart for troubleshooting a Diameter session's failure to be established

Troubleshooting Procedure
NOTE:

After the commands are configured to troubleshoot the faults, check the configuration validation mode to ensure that the configurations take effect. Unless otherwise specified, this manual defaults to immediate validation mode.

  • In immediate validation mode, the configurations take effect after the commands are entered.
  • In two-phase validation mode, after the commands are configured, the commit command needs to be run to commit the configurations.

Save the results of each troubleshooting step so that if your troubleshooting attempts fail to correct the fault, you will have a record of your actions to present to Huawei.

Procedure

  1. Check that the management IP address of the peer master is reachable.
    1. Run the ping -vpn-instance __dcn_vpn__ ip-address command on a master to check whether the management IP address of the peer master is reachable.

      • If the management IP address of the peer master is reachable, go to Step 2.

      • If the management IP address of the peer master is unreachable, perform troubleshooting according to The Ping Operation Fails and go to Step b.

    2. Run the display virtual-access master command on a master to check whether DiameterState is Up in the command output.

      • If DiameterState is Up in the command output, no further action is required.

      • If DiameterState is not Up in the command output, go to Step 2.

  2. Check that the authentication configurations for Diameter are the same on the local and peer masters.
    1. Run the display this command on the local and peer masters to check whether the authentication configurations for Diameter are the same on the local and peer masters.

      • If the authentication configurations for Diameter are the same on the local and peer masters, go to Step 3.

      • If the authentication configurations for Diameter are different on the local and peer masters, modify them correctly and go to Step b.

    2. Run the display virtual-access master command on a master to check whether DiameterState is Up in the command output.

      • If DiameterState is Up in the command output, no further action is required.

      • If DiameterState is not Up in the command output, go to Step 3.

  3. Check that the primary and secondary configurations for an AP are the same on the local and peer masters.
    1. Run the display virtual-access ap command on the local and peer masters to check whether the primary and secondary configurations for an AP are the same on the local and peer masters.

      • If the primary and secondary configurations for an AP are the same on the local and peer masters, go to Step 4.

      • If the primary and secondary configurations for an AP are different on the local and peer masters, modify them correctly and go to Step b.

    2. Run the display virtual-access master command on a master to check whether DiameterState is Up in the command output.

      • If DiameterState is Up in the command output, no further action is required.

      • If DiameterState is not Up in the command output, go to Step 4.

  4. Please contact technical support personnel and provide the following information:

    • Results of this troubleshooting procedure
    • Configuration, log, and alarm files

Relevant Alarms and Logs
Relevant Alarms

None

Relevant Logs

DIAMETER/6/hwDiameterDown

DIAMETER/6/hwDiameterUp

Translation
Download
Updated: 2019-06-11

Document ID: EDOC1000175918

Views: 13813

Downloads: 257

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