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

Alarm Handling

CloudEngine 12800 and 12800E V200R005C00

This document provides the explanations, causes, and recommended actions of alarms on the product.
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).
OSPF_1.3.6.1.4.1.2011.5.25.353.2.1 hwSrPrefixSidConflict

OSPF_1.3.6.1.4.1.2011.5.25.353.2.1 hwSrPrefixSidConflict

Description

The prefix-sid conflict is detected. (SrProtocol=[hwSrProtocol], SrProcessId=[hwSrProcessId], SrPrefixSid=[hwSrPrefixSid], SrPrefixAddress=[hwSrPrefixAddress], SrPrefixAddressMask=[hwSrPrefixAddressMask], SrConflictType=[hwSrConflictType], SrConflictState=[hwSrConflictState])

The prefix or SID conflict was detected.

Attributes

Attributes

Description

Alarm or Event

Alarm

Trap Severity

Minor

Mnemonic Code

hwSrPrefixSidConflict

Trap OID

1.3.6.1.4.1.2011.5.25.353.2.1

Alarm ID

0x00F10274

Alarm Type

communicationsAlarm

Raise or Clear

None

Match trap

The fault trap and service restoration trap share trap information and are distinguished using the SrConflictState field. If SrConflictState is inConflict, a fault trap is generated. If SrConflictState is conflictResolved, a service restoration trap is generated.

Parameters

Parameter

Description

SrProtocol
Involved SR protocol:
  • 1: OSPF
  • 2: ISIS
  • 3: SEGR
SrProcessId

ID of a process

SrPrefixSid

SR prefix SID

SrPrefixAddress

SR prefix address

SrPrefixAddressMask

SR prefix address mask

SrConflictType
SR conflict type:
  • 1: SidConflict
  • 2: PrefixConflict
  • 3: ConflictResloved
SrConflictState
SR conflict status:
  • 1: inConflict
  • 2: conflictResolved

VB Parameters

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.353.1.6

hwSrProtocol

N/A

1.3.6.1.4.1.2011.5.25.353.1.2

hwSrProcessId

N/A

1.3.6.1.4.1.2011.5.25.353.1.3

hwSrPrefixSid

N/A

1.3.6.1.4.1.2011.5.25.353.1.5

hwSrPrefixAddress

N/A

1.3.6.1.4.1.2011.5.25.353.1.4

hwSrPrefixAddressMask

N/A

1.3.6.1.4.1.2011.5.25.353.1.8

hwSrConflictType

N/A

1.3.6.1.4.1.2011.5.25.353.1.9

hwSrConflictState

N/A

Impact on the System

Conflicting routes are not used in SR.
  • If a prefix conflict occurs, the system selects a single prefix and ignores the same prefixes advertised by the other devices.
  • If a SID conflict occurs, the system selects a single SID and ignores the same SIDs advertised by the other devices.

Possible Causes

  • The configuration is incorrect.
  • The prefix on a loopback interface is the same as the address of a loopback interface on another device.
  • The SID configured on a loopback interface is the same as the SID on another router.

Procedure

  1. Run the isis prefix-sid { absolute sid-value | index index-value } [ node-disable ] command to set a different SID on the advertisement source device.
  2. Collect alarm information and configuration information, and then contact technical support personnel.
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100039527

Views: 68841

Downloads: 21

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