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 - SFC

CloudEngine 6800 and 5800 V200R003C00

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).
Configuring an SC

Configuring an SC

Context

An SC is located at the ingress of an SFC domain and classifies incoming traffic to the SFC domain based on the specified policy. Packets matching the classification rule are transmitted on the specified SFP, reducing performance requirements for SFs to process peak traffic.

The classification granularity is determined by the SC capability and SFC policy, and can be coarse or fine as required.

On a centralized VXLAN network, the SC and SFF are deployed both on the centralized VXLAN gateway. On a distributed VXLAN network, the VXLAN gateway connected to a tenant server is used as the SC.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run service-chain enable

    The SFC function is enabled.

    By default, the SFC function is disabled.

  3. Run commit

    The configuration is committed.

  4. Run service-chain service-path path-id

    An SFP is created and the service chain view is displayed.

    The value of path-id must be the same as the SPI configured on the SFF.

  5. (Optional) Run description description-content

    Description is configured for the SFP.

  6. Run service-index si-id next-hop sff { vtep-ip vtep-ip-address vni vni-id | remote-ip remote-ip-address [ vpn-instance vpn-instance-name ] }

    The next hop type is set to SFF.

    NOTE:

    The vtep-ip parameter needs to be configured only in the distributed VXLAN gateway scenario.

  7. Run commit

    The configuration is committed.

  8. Configure a traffic classifier.
    1. Run traffic classifier classifier-name [ type { and | or } ]

      A traffic classifier is created and the traffic classifier view is displayed, or the view of an existing traffic classifier is displayed.

      The parameter and indicates that rules in the traffic classifier are in AND relationship. After this parameter is specified, the following situations occur:
      • If a traffic classifier contains ACL rules, packets match the traffic classifier only when the packets match one ACL rule and all the non-ACL rules.

      • If a traffic classifier does not contain ACL rules, packets match the traffic classifier only when the packets match all the non-ACL rules.

      The parameter or indicates that rules in the traffic classifier are in OR relationship. After this parameter is specified, packets match a traffic classifier if the packets match one or more rules.

      By default, the relationship between rules in a traffic classifier is OR.

    2. Run if-match

      Matching rules in the traffic classifier are configured.

      You can configure multiple matching rules in a traffic classifier. For details, see "MQC Configuration - Configuring a Traffic Classifier" in the CloudEngine 8800, 7800, 6800, and 5800 Series Configuration Guide - QoS Configuration Guide.
      • Only if-match vxlan [ transit ] [ tag-format { none | single } ] acl { acl-number | acl-name } can be configured on a centralized VXLAN gateway network.

      • Only if-match acl can be configured on a distributed VXLAN gateway network.

    3. Run commit

      The configuration is committed.

    4. Run quit

      Exit from the traffic classifier view.

  9. Configure a traffic behavior.
    1. Run traffic behavior behavior-name

      A traffic behavior is created and the traffic behavior view is displayed, or the view of an existing traffic behavior is displayed.

    2. Run redirect service-path path-id service-index si-id

      Traffic is redirected to the specified SFP.

      By default, traffic is not redirected to any SFPs.

      The value of path-id is the same as that created in Step 4, and the specified si-id must exist.

    3. Run commit

      The configuration is committed.

    4. Run quit

      Exit from the traffic behavior view.

  10. Configure a traffic policy.
    1. Run traffic policy policy-name

      A traffic policy is created and the traffic policy view is displayed, or the view of an existing traffic policy is displayed.

    2. Run classifier classifier-name behavior behavior-name [ precedence precedence-value ]

      A traffic behavior is bound to a traffic classifier in the traffic policy.

    3. Run commit

      The configuration is committed.

    4. Run quit

      Exit from the traffic policy view.

  11. Apply the traffic policy.

    NOTE:

    For details about the configuration guidelines of applying traffic policies in different views on the CE switches excluding CE6870EI and CE6875EI, see Licensing Requirements and Limitations for MQC (CE Switches Excluding CE6870EI and CE6875EI).

    1. Enter the interface view.

      • On a VXLAN network, run: interface vbdif bd-id

        The VBDIF interface view is displayed.

      • On a VLAN network, run: interface interface-type interface-number[.subinterface-number ]

        The interface view is displayed.

    2. Run traffic-policy policy-name inbound

      The traffic policy is applied to the interface.

    3. Run commit

      The configuration is committed.

Translation
Download
Updated: 2019-05-08

Document ID: EDOC1100004362

Views: 4687

Downloads: 82

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