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

Troubleshooting Guide

CloudEngine 16800, 12800, 12800E, 8800, 7800, 6800, and 5800 Series Switches

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).
Why the Stack Configuration of the CE12800, CE12800E, and CE16800 with Stack Member ID 2 Does Not Take Effect When the Stack Has the Next Startup Configuration File Cleared and Starts with a New Configuration File?

Why the Stack Configuration of the CE12800, CE12800E, and CE16800 with Stack Member ID 2 Does Not Take Effect When the Stack Has the Next Startup Configuration File Cleared and Starts with a New Configuration File?

The following operations have been performed before this problem occurs:
  1. Run the reset saved-configuration command in the stack to clear the next startup configuration file.
  2. Specify a new configuration file for the stack and restart the stack. In the new configuration file, the stack configuration is as follows:
     #
     stack member 1 domain 10
     stack member 1 priority 150
     #
     stack member 2 domain 10
     stack member 2 priority 120
     #
    
  3. Check the stack configuration after the stack restarts, finding that the stack priority of the switch with stack member ID 2 is the same as that of the switch with stack member ID 1 but not the configured one.
    <HUAWEI> display stack configuration
    Oper          : Operation
    Conf          : Configuration
    *             : Offline configuration
    Isolated Port : The port is in stack mode, but does not belong to any Stack-Port
    
    Attribute Configuration:
    -----------------------------------------
     MemberID      Domain         Priority
    Oper(Conf)   Oper(Conf)      Oper(Conf)
    -----------------------------------------
    1(1)         10(10)          150(150)
    2(2)         10(10)          150(120)
     -----------------------------------------
    ......
    
Possible causes for this problem include:
  1. After the next startup configuration file is cleared for a stack, the stack member ID for the next startup of each member switch becomes the default value 1. After the next startup configuration file is specified for the stack and the stack restarts, each member switch parses the configuration file based on their stack member IDs.
  2. When the stack restarts, because of stack member ID conflicts, the master switch re-assigns stack member ID 2 to the switch that fails the competition, and then the switch that fails the competition restarts.
  3. After the switch starts with stack member ID 2, it still parses the configuration of stack member 1 to ensure that a stack can be set up normally because the stack configuration of stack member 2 may not be included in the new configuration file or cannot set up a stack. As a result, the stack configuration of stack member 2 in the configuration file does not take effect.
Translation
Download
Updated: 2020-01-07

Document ID: EDOC1000060766

Views: 611802

Downloads: 2956

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next