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

Configuration Guide - Device Management

S7700 and S9700 V200R013C00

This document describes the configurations of Device Management, including device status query, hardware management, CSS, SVF, PoE, OPS, OIDS, energy-saving management, information center, fault management, NTP, synchronous ethernet, PTP.
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).
Master/Standby Switchover

Master/Standby Switchover

Many factors may cause master/standby switchover events in a CSS. This section describes master/standby switchover events triggered by MPU failures, and those triggered by commands.

Master/Standby Switchover Triggered by MPU Failures

Roles in a CSS may change if a CSS system MPU fails. The switchover process differs depending on whether the MPU was the system master, the system standby, or a candidate standby.

  • The system master MPU fails.

    Figure 3-19 shows how the roles in both chassis 1 and 2 change after the system master MPU fails.

    Figure 3-19  Changes of roles after a failure of the system master MPU
    • The previous standby switch becomes the master switch, and the previous system standby MPU becomes the system master MPU.
    • The previous master switch becomes the standby switch.
    • The standby MPU of the previous master switch becomes the system standby MPU and synchronizes data with the system master MPU.
  • The system standby MPU fails.

    Figure 3-20 shows how the roles in both chassis 1 and 2 change after the system standby MPU fails.

    Figure 3-20  Change of roles after a failure of the system standby MPU
    • The master and standby switches retain their roles.
    • The standby MPU of the standby switch becomes the system standby MPU and synchronizes data with the system master MPU.
  • A candidate system standby MPU fails.

    Failures of candidate standby MPUs do not cause any change of roles in the CSS.

Master/Standby Switchover Triggered by a Command

Figure 3-21 shows how the roles in both chassis 1 and 2 change after a master/standby switchover is triggered by a command.
Figure 3-21  Change of roles after a command-triggered master/standby switchover
  • The previous standby switch becomes the master switch, and the previous system standby MPU becomes the system master MPU.
  • The previous system master MPU becomes a candidate system standby MPU, and the previous master switch becomes the standby switch.
  • The standby MPU of the previous master switch becomes the system standby MPU and synchronizes data with the system master MPU.
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100065738

Views: 40951

Downloads: 37

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