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

BFD Troubleshooting

This section describes common causes of BFD faults and provides the corresponding troubleshooting flowcharts, troubleshooting procedures, alarms, and logs.

BFD Session Cannot Go Up

This section describes the troubleshooting flowchart and provides a step-by-step troubleshooting procedure for the fault that prevents a BFD session from going Up.

Common Causes
This fault commonly results from one of the following causes:
  • The link detected by the BFD session fails. As a result, BFD packets cannot be exchanged between the two ends of the BFD session.

  • The BFD session status flaps.

Troubleshooting Flowchart
Figure 4-18 Troubleshooting flowchart for the fault that prevents a BFD session from going Up

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 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. Run the display current-configuration configuration bfd-session command to check whether the local discriminator of one end is the same as the remote discriminator of the other end.

    • If the two discriminators are the same, go to Step 2.

    • If the discriminators are different, run the discriminator command to configure the local and remote discriminators for the BFD session and commit the configuration. Then run the display bfd session all command to check whether the BFD session is Up.
      • If the State field is Up, the BFD session Go to Step 6.

      • If the State field is not Up, go to Step 2.

  2. Run the display bfd statistics session all command several times to check the statistics about the BFD packets of the BFD session.

    1. If the value of the Down Count field increases, the BFD session flaps. Go to Step 4.

    2. If the value of the Received Packets field does not increase, check whether the value of the Received Bad Packets field increases.

      • If the value of this field increases, the BFD packets have been received and discarded. Then, go to Step 5.

      • If the value of this field does not increase, the BFD packets have not been received. Go to Step 3.

    3. If the value of the Send Packets field does not increase, check whether the value of the Send Bad Packets field increases.

      • If the value of this field increases, the BFD packets sent by the BFD session have been discarded. Then, go to Step 5.

      • If the value of this field does not increase, the BFD packets failed to be sent. Go to Step 3.

  3. Run the ping command on one end to ping the other end of the BFD session.

    • If the ping fails, the link fails. See the section "The Ping Operation Fails" for help on rectifying the fault on the link and then go to Step 6.

    • If the ping is successful, the link is reachable. Go to Step 4.

  4. Run the display current-configuration configuration bfd-session command to view the min-tx-interval and min-rx-interval fields to check whether the BFD detection period is longer than the delay on the link.

    • If the BFD detection period is shorter than the delay, run the detect-multiplier, min-rx-interval, and min-tx-interval commands in the BFD session view to adjust the values to make the BFD detection timer longer than the delay. Then, go to Step 6.

    • If the BFD detection time is longer than the delay time on the link, go to Step 5.

  5. If the fault persists, collect the following information and contact technical support personnel.

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

  6. End.
Relevant Alarms and Logs
Relevant Alarms

None

Relevant Logs

None

A BFD Session for a Specific PW Cannot Go Up

This section describes common causes of the fault that prevents a BFD session for a specific PW from going Up and provides the corresponding troubleshooting flowcharts, and detailed troubleshooting procedures.

Common Causes
This fault commonly results from one of the following causes:
  • The PW to which BFD is bound cannot go Up.

  • BFD is configured incorrectly, preventing BFD packets from being exchanged.

Troubleshooting Flowchart
Figure 4-19 Troubleshooting flowchart for the fault that prevents a BFD session for a specific PW from going Up

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 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 whether the PW to which BFD is bound is Up by running one of the following commands based on the PW type:

    • To check information about a VSI PW, run the display vsi verbose command to check the Vsi State field in the command output.
      • If the Vsi State field is displayed as Up, go to Step 2.

      • If the Vsi State field is displayed as Down, see "VPLS Troubleshooting" for help.

    • To check information about a VLL, run the display mpls l2vpn connection interface interface-number command to check the local vc state and remote vc state fields.
      • If both the local vc state and remote vc state fields are displayed as Up, go to Step 2.

      • If one of the local vc state and remote vc state fields is displayed as Down, see "VLL Troubleshooting" for help.

    • To check information about a PWE3 tunnel, run the display mpls l2vc command to check the session state, AC status, and VC state fields.
      • If the session state, AC status, and VC state fields are all displayed as Up, go to Step 2.

      • If one of the session state, AC status, and VC state fields is displayed as Down, see "PWE3 Troubleshooting" for help.

  2. Run the display current-configuration configuration bfd-lsp-session command to check whether the local discriminator of one end is the same as the remote discriminator of the other end.

    • If the two discriminators are the same, go to Step 3.

    • If the discriminators are different, run the discriminator command to configure the local and remote discriminators for the BFD session and commit the configuration. Then run the display bfd session all command to check whether the BFD session is Up.
      • If the State field is Up, the BFD session Go to Step 10.

      • If the State field is not Up, go to Step 3.

  3. Run the display current-configuration configuration bfd-lsp-session command to check whether the BFD session configuration has been committed.

    • If the commit field is displayed, the BFD session configuration has been committed. In this case, go to Step 4.

    • If the commit field is not displayed, the BFD session has not been committed. In this case, run the commit command in the BFD session view, and then run the display bfd session all command to check whether the BFD session is Up.
      • If the State field is displayed as Up, the BFD session Go to Step 10.

      • If the State field is not Up, go to Step 4.

  4. Run the display bfd statistics session all slot slot-id command repeatedly to check statistics about the BFD packets.

    • If the value of the Received Packets field does not increase, go to Step 5.

    • If the value of the Send Packets field does not increase, go to Step 6.

    • If the values of both the Received Packets and Send Packets fields increase properly, go to Step 9.

    • If none of the Received Packets, Send Packets, Received Bad Packets, and Send Bad Packets fields increases, go to Step 9.

    • If the value of the Down Count field increases, the BFD session flaps. In this case, go to Step 7.

  5. Run the display bfd statistics session all slot slot-id command repeatedly to check that the value of the Received Bad Packets field increases properly.

    • If the value of the Received Bad Packets field increases, the local end receives but discards the BFD packets sent from the remote end. In this case, go to Step 9.

    • If the value of the Received Bad Packets field does not increase, the local end does not receive BFD packets. In this case, go to Step 7.

  6. Run the display bfd statistics session all slot slot-id command repeatedly to check that the value of the Send Bad Packets field increases properly.

    • If the value of the Send Bad Packets field increases, the BFD packets are sent but discarded. In this case, go to Step 9.

    • If the value of the Send Bad Packets field does not increase, the local end does not send BFD packets to the remote end. In this case, go to Step 7.

  7. Run the ping command to ping the remote end of the BFD session.

    • If the ping operation fails, see "The Ping Operation Fails" to rectify the fault and go to Step 10.

    • If the ping operation succeeds, go to Step 8.

  8. Run the display current-configurationconfiguration bfd-session command to check the values of the min-tx-interval and min-rx-interval fields and determine whether the detection time value is greater than the delay value.

    • If the detection time value is less than the delay value, run one of the detect-multiplier, min-rx-interval, and min-tx-interval commands to set the detection time value of the BFD session to be greater than the delay value. Then, go to Step 10.

    • If the detection time value of the BFD session is greater than the delay value, go to Step 9.

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

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

  10. End.
Relevant Alarms and Logs
Relevant Alarms
BFD/3/BFD_DOWN_TRAP:OID 1.3.6.1.4.1.2011.5.25.38.3.1 Session changes to DOWN. (Index=16389, ConfigurationName=1/0/0, PeerIp=224.0.0.108, BindIfIndex=134217985, BindIfName=GigabitEthernet1/0/0, Diagnosis=1, BindVrfIndex=0, BindVpnName="", SessionType=1, DefaultIp=2, BindType=1, StaticLspName="", PwSecondary=0, NextHop=224.0.0.108, VcId=0, VsiName="", VsiPeerAddress=0.0.0.0, DiscrAuto=2)
BFD/3/BFD_UP_TRAP:OID 1.3.6.1.4.1.2011.5.25.38.3.2 Session changes to UP. (Index=16389, ConfigurationName=1/0/0, PeerIp=224.0.0.108, BindIfIndex=134217985, BindIfName=GigabitEthernet1/0/0, Diagnosis=1, BindVrfIndex=0, BindVpnName="", SessionType=1, DefaultIp=2, BindType=1, StaticLspName="", PwSecondary=0, NextHop=224.0.0.108, VcId=0, VsiName="", VsiPeerAddress=0.0.0.0, DiscrAuto=2)
Relevant Logs
%%01BFD/6/STACHG_TODWN(l):Slot=1;BFD session changed to Down. (SlotNumber=1, Discriminator=18, Diagnostic=DetectDown, Applications=IFNET, ProcessPST=True, BindInterfaceName=GigabitEthernet1/0/1, InterfacePhysicalState=Up, InterfaceProtocolState=Down)
%%01BFD/6/STACHG_TOUP(l):-Slot=2; Slot BFD session changed to Up. (SlotNumber=2, Discriminator=9469, FormerStatus=Init)

Interface Forwarding Is Interrupted After a BFD Session Detects a Fault and Goes Down

This section describes the troubleshooting flowchart and provides a step-by-step troubleshooting procedure for the fault that interrupts interface forwarding after a BFD session detects a fault and goes Down.

Common Causes
This fault commonly results from one of the following causes:
  • The BFD session status is associated with the interface status.

Troubleshooting Flowchart
Figure 4-20 Troubleshooting flowchart for the fault that interrupts the interface forwarding after a BFD session detects a fault and goes Down

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 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. Run the display interface interface-type interface-number command to check the status of the interface to which the BFD session is bound.

    • If the Line protocol current state field displays DOWN(BFD status down), the interface status is set to BFD status down after the BFD session detects a link fault. Then, go to Step 2.

    • If the Line protocol current state field displays UP but the interface cannot forward packets, the forwarding module is faulty. See the section "The Ping Operation Fails" for help on rectifying the forwarding fault.

  2. Run the display bfd session all command to check the status of the BFD session.

    • If the BFD session is Down, go to Step 3.

    • If the BFD session is Up, go to Step 4.

  3. Run the display current-configuration configuration bfd-session command to check whether the process-interface-status command is configured.

    • If the process-interface-status command is configured, the interface is set to DOWN(BFD status down) because the BFD session detects a fault and goes Down. Then, go to Step 5.

    • If the process-interface-status command is not configured, go to Step 4.

  4. If the fault persists, collect the following information and contact technical support personnel.

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

  5. End.
Relevant Alarms and Logs

None

Dynamic BFD Session Fails to Be Created

This section describes the troubleshooting flowchart and provides a step-by-step troubleshooting procedure for the fault that prevents a dynamic BFD session from being created.

Common Causes
This fault commonly results from one of the following causes:
  • BFD is not enabled for the protocol.

  • The route to the peer of the BFD session does not exist in the routing table.

  • The dynamic BFD session is not supported on the interface.

Troubleshooting Flowchart
Figure 4-21 Troubleshooting flowchart for the fault that prevents a dynamic BFD session from being created

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 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. Run the display current-configuration configuration command to check whether BFD is enabled for a specified protocol.

    • If BFD is enabled, go to Step 2.

    • If BFD is not enabled for the specified protocol, enable it. Then, go to Step 5.

  2. Run the display ip routing-table command to check whether the route of the link detected by the BFD session exists.

    • If the route exists, go to Step 3.

    • If the route does not exist, the BFD session associated with the protocol has failed to be created. See the section "The Ping Operation Fails".

  3. Run the display current-configuration configuration command to check whether a command is configured to disable an interface to dynamically create a BFD session.

    • If there is, enable the interface to dynamically create a BFD session. Then, go to Step 5.

    • If there is not, go to Step 4.

  4. If the fault persists, collect the following information and contact technical support personnel.

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

  5. End.
Relevant Alarms and Logs

None

Translation
Download
Updated: 2019-06-11

Document ID: EDOC1000175918

Views: 14807

Downloads: 258

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