ISIS/2/SYSTEM_ID_CONFLICT:OID [oid] System ID may conflict.(sysProcIndexofDyname=[integer], hwisisSysInstance=[integer], hwisisSysLevelIndex =[integer], OwnSystemId=[opaque], OwnDynamicName=[string], AdjSystemId=[opaque], AdjDynamicName=[string], LocalIP=[hwIsisLocalIP], AdjIP=[hwIsisAdjIP], RemoteIP=[hwIsisRemoteIP])
Intermediate System to Intermediate System (IS-IS) detected that system IDs conflicted.
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
1.3.6.1.4.1.2011.5.25.24.2.4.1 |
Major |
communicationsAlarm(2) |
| Name | Meaning |
|---|---|
oid |
Indicates the MIB object ID of the alarm. |
sysProcIndexofDyname |
Index of the dynamic hostname of the local router |
hwisisSysInstance |
Conflicting system ID |
hwisisSysLevelIndex |
Level of the process in which system IDs conflicted |
OwnSystemId |
System ID of the local router |
OwnDynamicName |
Dynamic hostname of the local router |
AdjSystemId |
System ID of the neighbor |
AdjDynamicName |
Dynamic hostname of the neighbor |
LocalIP |
Local IP address |
AdjIP |
IP address of a neighbor |
RemoteIP |
IP address of the remote device with the conflicting system ID |
Link state protocol data units (LSPs) are frequently updated, and route flapping occurs.
If the system ID of the local router is the same as the conflicting system ID, change the system ID of the local router. Then check whether the alarm is cleared. If the alarm is cleared, go to step 4. If the alarm persists, go to step 3.
If the system ID of the local router is different from the conflicting system ID, go to step 2.