OSPF/3/hwSrPrefixSidConflict_active: The prefix-sid conflict is detected. (SrProtocol=[hwSrProtocol],SrProcessId=[hwSrProcessId],SrPrefixSid=[hwSrPrefixSid],SrPrefixAddress=[hwSrPrefixAddress],SrPrefixAddressMask=[hwSrPrefixAddressMask],SrConflictType=[hwSrConflictType],SrConflictState=[hwSrConflictState])
Parameter Name | Parameter Meaning |
---|---|
hwSrProtocol |
Segment Routing protocol that raised the alarm.
|
hwSrProcessId |
Process ID |
hwSrPrefixSid |
Prefix Sid |
hwSrPrefixAddress |
The Prefix Address configured in the Loopback Interface. |
hwSrPrefixAddressMask |
Prefix Ip Address Mask. |
hwSrConflictType |
Conflict type can be Prefix Sid conflict or Prefix conflict.
|
hwSrConflictState |
Conflict state indicates the current conflict state. |
Cause 1: The configuration is incorrect.
Cause 2: The prefix on a loopback interface is the same as the address of a loopback interface on another device.
Cause 3: The SID configured on a loopback interface is the same as the SID on another router.
1. If an OSPF prefix-SID conflict occurs, run the ospf prefix-sid { absolute sid-value | index index-value } [ node-disable ] command on the source device to modify the SID configuration.
2. If an IS-IS prefix-SID conflict occurs, run the isis prefix-sid { absolute sid-value | index index-value } [ node-disable ] command on the source device to modify the SID configuration.
3. If an OSPF-SR / ISIS-SR prefix-SID conflict occurs, indicating a conflict between protocols or processes, run the display segment-routing conflict-db segr { { prefix [ dest-ip mask ] } | { sid [ sid ] } } command to find the details of conflict, then run the ospf prefix-sid { absolute sid-value | index index-value } [ node-disable ] command or the isis prefix-sid { absolute sid-value | index index-value } [ node-disable ] command on the source device to modify the SID configuration.
4. Collect alarm and configuration information, and contact technical support engineers.