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 for 1588 ACR

Troubleshooting for 1588 ACR

This section provides the flowchart and procedure for troubleshooting of the 1588 ACR function.

1588 ACR Negotiation Fails

Common Causes

This section describes common causes of the 1588 ACR negotiation failure.

After 1588 ACR is configured on both the server and client, the Negotiate state field in the display ptp-adaptive all command output is displayed as Nego error, indicating a negotiation failure.

This fault is commonly caused by one of the following:
  • Unicast negotiation or 1588 ACR is disabled on the client or server.

  • The server and client are unroutable.

  • The physical link becomes faulty or the route between the server and client is deleted after the link has been used for negotiation.

Troubleshooting Procedure

This section describes the troubleshooting procedure of the 1588 ACR negotiation failure.

Procedure

  1. Identify the problem based on the Nego error field in the display ptp-adaptive all command output.

    • Prompt information: Nego error (reason: delete link)

      Common cause: Unicast negotiation is disabled on the client.

      Troubleshooting procedure: Run the display ptp-adaptive all command on the client to check the "Sync mode" field in the command output.
      • If the Sync mode field is displayed as none, unicast negotiation is disabled. Run the ptp-adaptive acr unicast-negotiate enable command in the system view on the client to enable unicast negotiation.

      • If the Sync mode field is not displayed as none, unicast negotiation has been enabled. Go to Step 2.

    • Prompt information: Nego error (reason: route unreachable)

      Common cause: The client and server are unroutable.

      Troubleshooting procedure: Run the ping command to check the connectivity between the client and server.
      • If the ping operation fails, see The Ping Operation Fails in the Troubleshooting - IP Service.

      • If the ping operation is successful, run the display ip routing-table command on the client and server to check whether the routing table on each end is correct. If the routing table on the client or server is incorrect, see the Troubleshooting - IP Routing.

    • Prompt information: Nego error (reason: announce grant timeout)

      Common cause: 1588 ACR or unicast negotiation is disabled on the server.

      Troubleshooting procedure: Run the display ptp-adaptive all command on the server to check the Ptp adaptive state and Sync mode fields in the command output.
      • If the Ptp adaptive state field is displayed as Disable, 1588 ACR is disabled. Run the ptp-adaptive enable command in the system view on the server to enable 1588 ACR.

      • If the Sync mode field is displayed as none, unicast negotiation is disabled. Run the ptp-adaptive acr unicast-negotiate enable command in the system view on the server to enable unicast negotiation.

      • If both 1588 ACR and unicast negotiation have been enabled on the server, go to Step 2.

    • Prompt information: Nego error (reason: announce timeout)

      Common causes:
      • 1588 ACR or unicast negotiation enabled on the server becomes Disabled.

      • The working mode of the 1588 ACR-capable board on the server is incorrect.

      • The physical link becomes faulty or the route between the server and client is deleted after the link has been used for negotiation.

      Troubleshooting procedure:
      1. Run the display ptp-adaptive all command on the server to check the Ptp adaptive state and Sync mode fields in the command output.

        If the Ptp adaptive state field is displayed as Disable, 1588 ACR is disabled. Run the ptp-adaptive enable command in the system view on the server to enable 1588 ACR.

        If the Sync mode field is displayed as none, unicast negotiation is disabled. Run the ptp-adaptive acr unicast-negotiate enable command in the system view on the server to enable unicast negotiation.

        If both 1588 ACR and unicast negotiation have been enabled on the server, go to the next step.

      2. Run the ping command to check the connectivity between the client and server.

        If the ping operation fails, see The Ping Operation Fails in the Troubleshooting - IP Service.

        If the ping operation is successful, run the display ip routing-table command on the client and server to check whether the routing table is correct. If the routing table on the client or server is incorrect, see the Troubleshooting - IP Routing.

      3. If the connectivity between the client and server is normal, go to Step 2.

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

    • Results of the troubleshooting procedure

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

Relevant Alarms and Logs

This section describes relevant alarms and logs of the 1588 ACR negotiation failure.

Relevant Alarms

None

Relevant Logs

None

Clock Synchronization Fails After the 1588 ACR Negotiation

Common Causes

This section describes common causes of the clock synchronization failure after 1588 ACR negotiation succeeds.

After the negotiation, the Frequency lock success field in the output of the display clock command running on the client displays no, and clock synchronization on the client fails.

This fault is commonly caused by one of the following:
  • PTP clock source synchronization is disabled on the client.

  • PTP clock source configurations on the client are incorrect.

  • The sending and receiving of clock packets are unstable due to a too-large Packet Delay Variation (PDV) value.

Troubleshooting Procedure

This section describes the troubleshooting procedure of the clock synchronization failure after 1588 ACR negotiation succeeds.

Procedure

  1. Run the display clock (all views) config command on the client to check whether the PTP clock source is in the Sync enable state.

    • If the PTP clock source is in the Sync disable state, run the clock source ptp synchronization enable command to enable PTP clock source synchronization.

    • If the PTP clock source is in the Sync enable state, go to Step 2.

  2. Run the display clock (all views) source command on the client to check whether PTP clock source configurations are correct.

    • If the clock source is selected based on the SSM levels on the client, check whether the In-SSM value of the PTP clock source is correct. If the In-SSM value is incorrect, run the clock source ptp ssm command in the system view to set a correct In-SSM value.

    • If the clock source is selected based on the priorities on the client, check whether the priority of the PTP clock source, identified by the Pri(sys) field, is correct. If the priority is incorrect, run the clock source ptp priority priority-value command in the system view to set a correct priority.

    If PTP clock source configurations are correct, go to Step 3.

  3. Run the display ptp-adaptive server command on the client to check whether the Sync packet statistics are displayed in the Receive packet statistics field.

    NOTE:

    If the frequency recovery mode of the client is two-way, check whether the statistics about Delay_resp packets are collected.

    • If the statistics about both Sync and Delay_resp packets are collected, go to Step 4.

    • If the statistics about Sync packets are not collected, the client fails to receive Sync packets, go to Step 5.

  4. Check whether the clock synchronization negotiation on the client has been successful for 30 minutes.

    • If the clock synchronization negotiation has been successful for less than 30 minutes, the clock synchronization on the subcard may not be complete.

    • If the clock synchronization negotiation has been successful for 30 minutes, go to Step 5.

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

    • Results of the troubleshooting procedure

    • Configuration files, log files, and alarm files, and PDV data statistics for the devices

      NOTE:

      PDV data statistics are saved in /opt/vrpv8/var/log/pdv1, /opt/vrpv8/var/log/pdv2, /opt/vrpv8/var/log/pdv3. PDV data statistics about both the master and slave MPUs need to be collected.

    • Type of the subcard on the client

Relevant Alarms and Logs

This section describes relevant alarms and logs of the clock synchronization failure after 1588 ACR negotiation succeeds.

Relevant Alarms

PTP_1.3.6.1.4.1.2011.5.25.187.5.17 hwPtpFrequencyLockFail

PTP_1.3.6.1.4.1.2011.5.25.187.5.18 hwPtpFrequencyLockResume

PTP_1.3.6.1.4.1.2011.5.25.187.5.24 hwPtpAcrSyncBad

PTP_1.3.6.1.4.1.2011.5.25.187.5.25 hwPtpAcrSyncBadResume

PTP_1.3.6.1.4.1.2011.5.25.187.5.26 hwPtpPdvLimitExceed

Relevant Logs

None

Translation
Download
Updated: 2019-06-11

Document ID: EDOC1000175918

Views: 4785

Downloads: 210

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