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 V800R010C10SPC500 Feature Description - System Management 01

This is ME60 V800R010C10SPC500 Feature Description - System Management
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).
CUSP Reliability

CUSP Reliability

A controller generates service data based on information (such as interface information) reported by a forwarder and then delivers the service data to the forwarder through a control channel. To minimize service interruptions caused by a CUSP connection or controller fault, CUSP supports the following reliability solutions.
Table 20-2 CUSP reliability solutions

Reliability Solution

Usage Scenario

CUSP connection reliability

This solution is used in CUSP connection fault scenarios. The controller backs up data. Before a CUSP connection is reestablished, the controller uses the backup data to process services, which ensures the continuity of services that have been generated on the controller after connection reestablishment.

CUSP non-stop routing (NSR)

CUSP NSR applies to scenarios in which a controller fails or an active/standby control plane switchover is performed. The active control plane backs up data. If the active control plane fails or an active/standby control plane switchover is performed, the standby control plane takes over, and the service process continues to work based on the data that was backed up before the active control plane fails, which ensures CUSP service continuity.

CUSP Connection Reliability

The CUSP connection reliability solution backs up collected forwarder interface information, bindings between the controller's logical interfaces and the forwarder's physical interfaces, and the forwarder's connection management information. The data is used to implement controller service functions.

In CUSP connection fault scenarios, CUSP connection reliability is implemented as follows:
  • Before a CUSP connection is reestablished, the controller uses the backed up data to process services.
  • After the CUSP connection is reestablished, the controller re-collects forwarder information and updates original information to ensure that services are properly processed.

CUSP NSR

The implementation process is as follows:

  1. The active control plane backs up the following data in batches and in real time:

    • TCP and CUSP connection information. This backup ensures that the CUSP connection is not interrupted after an active/standby control plane switchover.

    • Resource information reported by a forwarder. This backup ensures that resource information is consistent before and after an active/standby control plane switchover.

    • Flow table data delivered by the controller. This backup ensures that flow table data is consistent before and after an active/standby control plane switchover.

  2. If the active control plane fails or an active/standby control plane switchover is performed, the standby control plane takes over, and the service process continues to work based on the data that was backed up before the active control plane fails and responds to service changes, which ensures service continuity.

    • If resource information changes during an active/standby control plane switchover, the controller re-collects resource information from the forwarder after the switchover and completes synchronization and aging.
    • If flow table information changes during an active/standby control plane switchover, the controller uses Experimenter packets to re-deliver all FES entries to the forwarder after the switchover. The forwarder then synchronizes and ages flow entry information.
    • After an active/standby control plane switchover, the controller and forwarder continue to send service protocol packets (such as ARP, ICMP, and OSPF packets) to each other through the control channel.

Translation
Download
Updated: 2019-01-04

Document ID: EDOC1100059466

Views: 10194

Downloads: 6

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