BGP/4/BGPFLOWSPEC_V6

Message

BGP/4/BGPFLOWSPEC_V6: The ipv6 route [REIndex] includes conflict rules (ReasonID is [ReasonID]).

Description

Rules contained in the IPv6 route with a specified index conflicted.

Parameters

Parameter Name Parameter Meaning

REIndex

Route index

ReasonID

Conflict reason

Possible Causes

The mapping causes of reason IDs are as follows:

  • ReasonID = 1: Both the port type and source or destination port type were configured in the same BGP FlowSpec IPv6 route.
  • ReasonID = 2: Both the port type, destination port type, or source port type and ICMP type or ICMP code type were configured in the same BGP FlowSpec IPv6 route.
  • ReasonID = 3: The protocol type was configured in the same BGP FlowSpec IPv6 route, but the protocol type was not TCP or UDP. In addition, the port type, source port type, or destination port type was configured.
  • ReasonID = 4: Both a non-ICMP protocol type and an ICMPTYPE or ICMPCODE protocol type were configured in the same BGP FlowSpec IPv6 route.
  • ReasonID = 5: The rule type configured in the BGP FlowSpec IPv6 route was not supported.
  • ReasonID = 6: The rule parameters configured for the BGP FlowSpec IPv6 route exceeded the valid range.
  • ReasonID = 7: The valid range of the same type of rules configured in the BGP FlowSpec IPv6 route was empty.
  • ReasonID = 8: The protocol type was configured in the same BGP FlowSpec IPv6 route, but the protocol type value was not TCP. In addition, the TCPFLAG type was configured. As a result, a conflict occurred, the rule was not delivered, and a log was recorded.
  • ReasonID = 9: The port type, source port type, or destination port type was configured in the same BGP FlowSpec IPv6 route, and the TCP flag type was also configured, but the protocol type was not configured. As a result, a conflict occurred, the rule was not delivered, and a log was recorded.
  • ReasonID = 10: Both TCPFLAG and ICPMTYPE or ICMPCODE were configured in the same BGP FlowSpec IPv6 route, causing a conflict. As a result, the BGP FlowSpec IPv6 route failed to be delivered, and a log was generated.
  • ReasonID = 11: Both the TCP flag type and fragment type were configured in the same BGP FlowSpec IPv6 route. As a result, a conflict occurred, the rule was not delivered, and a log was recorded.
  • ReasonID = 12: Both the port type, source port type, destination port type, ICMP type, or ICMP code and the fragment packet type were configured for the same BGP FlowSpec IPv6 route.
  • ReasonID = 13: The protocol type was configured in the same BGP FlowSpec IPv6 route, but the protocol type value was not 44. In addition, the fragment packet type was configured, causing a conflict.
  • ReasonID = 14: Both the protocol type 44 and non-fragmented packet type were configured in the same BGP FlowSpec IPv6 route.

Procedure

1. Check whether a conflict occurs in the BGP FlowSpec IPv6 route based on the mapping reasons of the indexes and reason IDs in the log information.

2. Modify or delete the conflicting rules and re-send the BGP FlowSpec IPv6 route.

3. Run the display logbuffer slot | include BGPFLOW command to check whether the conflict is continuously reported through logs.

  • If yes, go to Step 4.
  • If not, go to Step 5.

4. Collect trap, log, and configuration information, and contact technical support personnel.

5. End.

Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >