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


To have a better experience, please upgrade your IE browser.


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).
Control channel Establishment and Maintenance

Control channel Establishment and Maintenance

a control channel is established over a TCP connection. Devices on both ends of a channel exchange heartbeat packets to maintain the connection. Figure 20-2 shows the process of control channel establishment and maintenance.

  1. After the controller and forwarder are both configured, the controller and forwarder establish a TCP connection.
  2. The controller and forwarder exchange Hello packets carrying version information over the TCP connection to negotiate a channel with each other.
  3. After the negotiation is complete, the controller sends a Features Request packet to query the attribute information of the forwarder. Upon receipt of the packet, the forwarder replies with the requested attribute information, such as the flow table format and buffer size, to the controller. Then, a control channel is successfully established.
  4. The controller and forwarder periodically send Echo Request packets to each other to detect the connection status. After receiving an Echo Request packet sent from the initiator, the peer returns an Echo Reply packet. If the initiator neither receives an Echo_Reply packet nor receives any other valid CUSP packet after a specified number of attempts, the initiator considers the peer faulty and tears down the connection. If the initiator does not receive any Echo_Reply packet but receives another valid CUSP packet, it does not tear down the connection.
Figure 20-2 Flowchart for establishing and maintaining a CUSP connection

Updated: 2019-01-04

Document ID: EDOC1100059466

Views: 10577

Downloads: 7

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