The conflict cause (ReasonID) is described as follows:
1) The same BGP FlowSpec route is configured with both the port type and the source or destination port type.
2) Both the port type, source port type, or destination port type and the TCP flag type are configured in the same BGP FlowSpec route, but no protocol type is configured.
3) The port type, destination port type, source port type, or TCP flag type is configured in the same BGP FlowSpec route, and the ICPMTYPE or ICMPCODE type is also configured.
4) The protocol type configured in the same BGP FlowSpec route is not TCP or UDP, and the port type, source port type, or destination port type is also configured.
5) The protocol type is configured in the same BGP FlowSpec route, but the protocol type is not TCP. In addition, the TCPFLAG type is configured, causing a conflict.
6) The protocol type is configured in the same BGP FlowSpec route, but the protocol type is not ICMP. In addition, the ICMPTYPE or ICMPCODE type is configured.
7) An unsupported traffic matching rule is configured in the BGP FlowSpec route, and the route fails to be delivered.
The following situations are included:
8) A matching rule for BGP FlowSpec routes is configured, but the matching rule is not in the permitted range. As a result, the BGP FlowSpec routes fail to be delivered.
9) The BGP FlowSpec route received a traffic matching rule, but the set of matching rules was empty. As a result, the rule was invalid.
10) In the same BGP FlowSpec route, the rule type matching TCPFLAG, ICPMTYPE, ICMPCODE, port, source port, and destination port is configured, and the rule type matching subsequent fragments is also configured. As a result, a conflict occurs.
1. Check whether a conflict occurs in the BGP Flow Specification route based on the index and the cause of the conflict in the log.
2. Modify or delete the conflicted rule in the BGP Flow Specification route. The route will be resent after reconfiguration.
3. Check whether the conflict persists.
4. Collect the alarm information, log information, and configuration information, and then contact technical support personnel.
5. End.