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

Log Reference

S9300, S9300E, and S9300X V200R010C00

This document provides the explanations, causes, and recommended actions of logs on the product.
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).
VBST/4/LOOPPROTECT

VBST/4/LOOPPROTECT

Message

VBST/4/LOOPPROTECT: VBST VLAN [vlan-id]'s LOOP-Protection port [port-name] did not receive message in prescriptive time.

Description

The root port or alternate port in the VLAN enabled VBST and loop protection did not receive BPDUs within the specified time.

Parameters

Parameter Name Parameter Meaning
[vlan-id] Indicates the VLAN ID.
[port-name] Indicates the port name.

Possible Causes

Cause 1: The VBST function was disabled on the peer device.

Cause 2: The links connected to the peer were congested.

Procedure

  1. Cause 1: The VBST function was disabled on the peer device.
    1. Run the display stp [ vlan vlan-id ] [ interface interface-type interface-number | slot slot-id ] [ brief ] command to check whether VBST is disabled on the interfaces that are directly connected.

      • If VBST is disabled on the interfaces that are directly connected, go to Step 2.
      • If VBST is enabled on the interfaces that are directly connected, go to Step 3.

    2. Run the stp vlan vlan-id1 enable command in the interface view to enable VBST. Then, check whether the log persists. If the log persists, go to Step 3.
    3. Collect trap, log, and configuration information, and contact technical support personnel.
  2. Cause 2: The links connected to the peer were congested.
    1. Check whether the link is congested between the local device and the neighbor device.

      • If the link is congested, go to Step 2.
      • If the link is not congested, go to Step 3.

    2. Repair the physical link and then check whether the log persists. If the log persists, go to Step 3.
    3. Collect trap, log, and configuration information, and contact technical support personnel.
Translation
Download
Updated: 2019-08-21

Document ID: EDOC1000142069

Views: 549695

Downloads: 37

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