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.


Configuration Guide - SFC

CloudEngine 6800 and 5800 V200R002C50

This document describes the configurations of Service function chain (SFC).

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).
Basic Concepts of SFC

Basic Concepts of SFC

Table 2-1 describes basic service function chain (SFC) concepts.
Table 2-1  Basic concepts of SFC



SFC domain

SFC devices form an SFC domain.

Service classifier (SC)

An SC is located at the ingress of an SFC domain and classifies incoming traffic to the SFC domain. The classification granularity is determined by the SC capability and SFC policy. For example, in coarse-grained scenarios, all packets on a port match an SFC rule and are forwarded along SFP A; in fine-grained scenarios, only packets meeting 5-tuple requirements can match an SFC rule and are forwarded along SFP B.

Service function (SF)

An SF list includes but is not limited to firewalls (FWs), load balancers (LBs), application accelerators, lawful interception (LI) devices, and network address translation (NAT) devices. Multiple SFs may exist in an SFC domain.

Depending on network service header (NSH) encapsulation awareness, SFs are classified into NSH-aware SFs and NSH-unaware SFs. NSH-aware SFs can identify and process received NSH packets, while NSH-unaware SFs cannot identify NSH packets and discard them.

Service function forwarder (SFF)

An SFF forwards received packets to SFs associated with it based on NSH encapsulation information. SFs process the packets and return them to the associated SFF. The SFF then determines whether to send the packets back to the network.

SFC proxy

An SFC proxy is located between an SFF and NSH-unaware SFs associated with the SFF. The SFC proxy receives packets from the SFF on behalf of SFs. After deleting NSH encapsulation information, the SFC proxy sends packets to NSH-unaware SFs through the local logical component. When receiving packets from NSH-unaware SFs, the SFC proxy adds NSH encapsulation information to the packets and sends the packets to the SFF. To the SFF, the SFC proxy is an NSH-aware SF.

Service function path (SFP)

An SFP is calculated based on the user configuration, precisely defining the location of each SF.

Updated: 2019-03-21

Document ID: EDOC1000166642

Views: 8745

Downloads: 184

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next