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

NE20E-S2 V800R010C10SPC500 Configuration Guide - Security 01

This is NE20E-S2 V800R010C10SPC500 Configuration Guide - Security
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).
Licensing Requirements and Limitations for BGP Flow Specification--S2E

Licensing Requirements and Limitations for BGP Flow Specification--S2E

Licensing Requirements

This feature is a basic feature and is not under license control.

Restrictions and Guidelines

Restrictions

Guidelines

Impact

BGP Flow Specification does not support the redirect-to-next-hop action of replication.

Plan services.

BGP IPv6 Flow Specification does not support replication as the redirect-to-next-hop action.

If both the redirection next-hop IP address and redirection vpn-target are configured for BGP Flow Specification, redirection vpn-target takes effect.

After configuring the redirection next-hop, do not configure the redirection VPN actions.

The configuration of both the redirection next-hop IP address and redirection vpn-target is affected.

BGP Flow Specification does not deliver the rule with TCP-FLAG being NOT 0.

Do not set TCPFLAG to NOT 0.

BGP Flow Specification does not deliver the rule when TCP-FLAG is NOT 0.

BGP Flow Specification may encounter the following configuration conflicts:
  • If both a port type and a source or destination port type are configured in the same BGP Flow Specification route, a conflict occurs.
  • If a port type or a source or destination port type and a TCP flag type are configured in the same BGP Flow Specification route but no protocol type is configured, a conflict occurs.
  • If a port type, a source or destination port type, or a TCP flag type and an ICMPTYPE or ICMPCODE type is configured in the same BGP Flow Specification route, a conflict occurs.
  • If a non-TCP/UDP protocol type and a port type or a source or destination port type are configured in the same BGP Flow Specification route, a conflict occurs.
  • If a non-TCP protocol type and a TCP flag type are configured in the same BGP Flow Specification route, a conflict occurs.
  • If a non-ICMP protocol type and an ICMPTYPE or ICMPCODE type are configured in the same BGP Flow Specification route, a conflict occurs.
  • The rule type configured in the BGP Flowspec route is not supported.
  • The rule parameter configured in the BGP Flowspec route is out of the valid range.
  • The valid range of same-type rules configured in a BGP Flowspec route is null.

Plan services, and do not perform conflict rule configuration.

After a conflict rule is configured, the rule is not delivered.

BGP Flow Specification does not support last fragment check.

None

None

The flowspec refluence and traffic-policy commands are mutually exclusive on an interface.

The flowspec refluence command and MF classification conflict with each other. After this command is configured, do not configure MF classification on this interface.

Services on the same interface cannot coexist.

BGP IPv6 Flow Specification does not support matching rules based on fragment-type, tcp-flags, packet-length, or dscp.

Prevent the unsupported rules from being configured.

BGP IPv6 Flow Specification does not support matching rules based on fragment-type, tcp-flags, packet-length, or dscp.

BGP IPv6 Flow Specification may encounter the following configuration conflicts:
  • If both a port type and a source or destination port type are configured in the same BGP IPv6 Flow Specification route, a conflict occurs.
  • If a port type or a source or destination port type and an ICMPTYPE or ICMPCODE type is configured in the same BGP Flow Specification route, a conflict occurs.
  • If a non-TCP/UDP protocol type and a port type or a source or destination port type are configured in the same BGP IPv6 Flow Specification route, a conflict occurs.
  • If a non-ICMP protocol type and an ICMPTYPE or ICMPCODE type are configured in the same BGP IPv6 Flow Specification route, a conflict occurs.
  • The rule type configured in the BGP IPv6 Flowspec route is not supported.
  • The rule parameter configured in the BGP IPv6 Flowspec route is out of the valid range.
  • The valid range of same-type rules configured in a BGP IPv6 Flowspec route is null.

Plan services, and do not perform conflict rule configuration.

After a conflict rule is configured, the rule is not delivered.

Translation
Download
Updated: 2019-01-02

Document ID: EDOC1100055397

Views: 20469

Downloads: 39

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