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).
EFM Troubleshooting

EFM Troubleshooting

This section describes common causes of Ethernet in the First Mile OAM (EFM OAM) faults, and provides the corresponding troubleshooting flowcharts, troubleshooting procedures, alarms, logs, and commands.

An EFM Session Cannot Enter the Detect State

This section describes the troubleshooting flowchart and provides a step-by-step troubleshooting procedure for the fault that prevents an EFM session from entering the Detect state.

Common Causes

An EFM session cannot enter the Detect state after the EFM configurations are complete.

This fault commonly results from one of the following causes:
  • The physical link becomes faulty.
  • The physical status of the interface on the local end is Down.
  • The EFM OAM working modes on the local and remote ends are both passive.
  • EFM is not enabled on the remote end.
Troubleshooting Flowchart

On the network shown in Figure 4-24, an EFM session cannot enter the Detect state.

Figure 4-24 Typical EFM networking

Figure 4-25 shows the troubleshooting flowchart.

Figure 4-25 Troubleshooting flowchart for the fault that prevents an EFM session from entering the Detect state
Troubleshooting Procedure

Context

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 the 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 fails to correct the fault, you will have a record of your actions to present to Huawei.

Procedure

  1. Check whether the physical link between CE1 and PE1 is working properly.

    Ensure that CE1 and PE1 are directly connected. This allows the EFM session to enter the Detect state after being established.

    • If the physical link between CE1 and PE1 is faulty, see "Physical Interconnection Troubleshooting" for details about how to troubleshoot the link fault.
    • If the physical link between CE1 and PE1 is working properly, go to Step 2.
  2. Check whether interfaces connecting CE1 and PE1 are Up.

    Run the display this command in the view of GE 1/0/0 on each end to check whether the interface has been shut down.

    • If GE 1/0/1 has been shut down, run the undo shutdown command in the interface view to enable the interface.
    • If GE 1/0/1 has not been shut down, go to Step 3.
  3. Check whether EFM is enabled on CE1 and PE1.

    Run the display efm { all | interface interface-type interface-number } command in any view on each end. The EFM Enable Flag field in the command output shows the EFM status on GE 1/0/0.

    • If the value of the EFM Enable Flag field is disable, EFM is disabled on GE 1/0/0.
    • If the value of the EFM Enable Flag field is enable, EFM is enabled on GE 1/0/0.

    • If EFM is disabled on GE 1/0/0, run the efm enable command in the system view and interface view to enable EFM.

    • If EFM is enabled on GE 1/0/0 on both ends, go to Step 4.
  4. Check whether EFM working modes on CE1 and PE1 are different.

    Run the display efm { all | interface interface-type interface-number } command in any view on each end. The Mode field in the command output shows the EFM working mode.

    • If the value of the Mode field is passive, the EFM working mode is passive.
    • If the value of the Mode field is active, the EFM working mode is active.

    • If the interfaces connecting CE1 and PE1 both work in passive EFM mode, run the efm mode active command on one of the interfaces to change the working mode from passive to active.

      This change enables the end working in active mode to initiate negotiation.

    • If the two interfaces connecting CE1 and PE1 are not in passive EFM mode, go to Step 5.
  5. Collect the following information and contact technical support personnel.

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

Relevant Alarms and Logs
Relevant Alarms

None

Relevant Logs

EFM_CRITICALLINKEVENT

EFM_CRITICALLINKEVENTCLEAR

EFM Incessantly Generates Errored Frame, Errored Code, or Errored Frame Seconds Summary Events

This section describes the troubleshooting flowchart and provides a step-by-step troubleshooting procedure for the fault that causes EFM to incessantly generate errored frame, errored code, or errored frame seconds summary events.

Common Causes
This fault commonly results from one of the following causes:
  • The period for detecting errored codes, errored frames, or errored frame seconds is not proper.
  • The threshold for the number of errored codes, errored frames, or errored frame seconds is not proper.
Troubleshooting Flowchart

On the network shown in Figure 4-26, EFM incessantly generates errored code, errored frame, or errored frame seconds summary events.

Figure 4-26 Typical EFM networking

Figure 4-27 shows the troubleshooting flowchart.

Figure 4-27 Troubleshooting flowchart for the fault that causes EFM incessantly to generate errored code, errored frame, or errored frame seconds summary events
Troubleshooting Procedure

Context

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 the 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 fails to correct the fault, you will have a record of your actions to present to Huawei.

Procedure

  1. Check whether the set period for detecting errored codes, errored frames, or errored frame seconds is proper.

    Run the display efm interface interface-type interface-number command in any view. The values of the ErrorCodePeriod, ErrFramePeriod, and ErrFrameSecondPeriod fields show the set periods for detecting errored codes, errored frames, and errored frame seconds respectively.

    • If the period for detecting errored codes, errored frames, or errored frame seconds is too short, perform one of the following operations to increase the detection time:
      • Run the efm error-code period period command in the interface view to re-set a period for detecting errored codes.
      • Run the efm error-frame period period command in the interface view to re-set a period for detecting errored frames.
      • Run the efm error-frame-second period period command in the interface view to re-set a period for detecting errored frame seconds.
    • If the period for detecting errored codes, errored frames, or errored frame seconds is proper, go to Step 2.
  2. Check whether the set threshold for the number of errored codes, errored frames, or errored frame seconds is proper.

    Run the display efm interface interface-type interface-number command in any view. The values of the ErrorCodeThreshold, ErrFrameThreshold, and ErrFrameSecondThreshold fields show the set thresholds for the number of errored codes, errored frames, and errored frame seconds respectively.

    • If the threshold for the number of errored codes, errored frames, or errored frame seconds is too low, perform one of the following operations to increase the threshold value:
      • Run the efm error-code threshold threshold command in the interface view to re-set a threshold for the number of errored codes.
      • Run the efm error-frame threshold threshold command in the interface view to re-set a threshold for the number of errored frames.
      • Run the efm error-frame-second threshold threshold command in the interface view to re-set a threshold for the number of errored frame seconds.
    • If the threshold for the number of errored codes, errored frames, or errored frame seconds is proper, go to Step 3.
  3. Collect the following information and contact technical support personnel.

    • Results of this preceding operation procedure
    • Configuration files, log files, and alarm files

Relevant Alarms and Logs
Relevant Alarms

None

Relevant Logs

EFM_LINKEVENT

EFM_LINKEVENTCLEAR

Link Layer Status of the Interface Cannot Change to Up After EFM Detects Fault Rectification

This section describes the troubleshooting flowchart and provides a step-by-step troubleshooting procedure for the fault that prevents the link layer status of the interface from changing to Up after EFM detects fault rectification.

Common Causes

This fault is commonly caused by an incorrect setting of EFM faulty-state hold time.

Troubleshooting Flowchart

None

Troubleshooting Procedure

Context

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 the 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 fails to correct the fault, you will have a record of your actions to present to Huawei.

Procedure

  1. Check whether the set EFM faulty-state hold time is proper.

    Run the display efm interface interface-type interface-number command in any view. The Hold Up Time field in the command output shows the set EFM faulty-state hold time.

    • If the EFM faulty-state hold time is too long, run the efm holdup-timer time command in the interface view to re-set the time.
    • If the set EFM faulty-state hold time is proper, go to Step 2.

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

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

Relevant Alarms and Logs
Relevant Alarms

None

Relevant Logs

None

Translation
Download
Updated: 2019-06-11

Document ID: EDOC1000175918

Views: 4744

Downloads: 209

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