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>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

OSPF router ID conflict with itself

Publication Date:  2017-09-14 Views:  1602 Downloads:  16
Issue Description

        Customer find internal network ping intermittent and check the log in core switch with software Version  V200R005C00SPC500 , it keeps to show messages as below:

 

Jul 26 2017 06:50:48+07:00 SMBPZ-CORE-UG %%01OSPF/4/CONFLICT_ROUTERID_INTF(l)[20]:OSPF Router id conflict is detected on interface. (ProcessId=1, RouterId=10.110.87.158, AreaId=0.0.0.0, InterfaceName=Eth-Trunk5,  IpAddr=10.110.87.90, PacketSrcIp=10.110.87.90)

Jul 26 2017 06:48:41+07:00 SMBPZ-CORE-UG %%01OSPF/4/CONFLICT_ROUTERID_INTF(l)[21]:OSPF Router id conflict is detected on interface. (ProcessId=1, RouterId=10.110.87.158, AreaId=0.0.0.0, InterfaceName=Eth-Trunk5,  IpAddr=10.110.87.90, PacketSrcIp=10.110.87.90)

 

            Access switch with software version V200R005C00SPC500 keeps to show below alarm:

 

Jul 25 2017 20:47:01 SMBPZ-SF-UG-01 %%01OSPF/4/CONFLICT_ROUTERID_INTF(l)[3]:OSPF Router id conflict is detected on interface. (ProcessId=1, RouterId=10.110.87.89, AreaId=0.0.0.0, InterfaceName=Vlanif1,  IpAddr=10.110.87.89, PacketSrcIp=10.110.87.89)

Jul 25 2017 20:46:16 SMBPZ-SF-UG-01 %%01OSPF/4/CONFLICT_ROUTERID_INTF(l)[4]:OSPF Router id conflict is detected on interface. (ProcessId=1, RouterId=10.110.87.89, AreaId=0.0.0.0, InterfaceName=Vlanif95,  IpAddr=10.110.87.190, PacketSrcIp=10.110.87.190)

Jul 25 2017 20:44:55 SMBPZ-SF-UG-01 %%01OSPF/4/CONFLICT_ROUTERID_INTF(l)[5]:OSPF Router id conflict is detected on interface. (ProcessId=1, RouterId=10.110.87.89, AreaId=0.0.0.0, InterfaceName=Vlanif1,  IpAddr=10.110.87.89, PacketSrcIp=10.110.87.89)

Jul 25 2017 20:44:54 SMBPZ-SF-UG-01 %%01OSPF/4/CONFLICT_ROUTERID_INTF(l)[6]:OSPF Router id conflict is detected on interface. (ProcessId=1, RouterId=10.110.87.89, AreaId=0.0.0.0, InterfaceName=Vlanif99,  IpAddr=192.168.83.254, PacketSrcIp=192.168.83.254)

Jul 25 2017 20:44:11 SMBPZ-SF-UG-01 %%01OSPF/4/CONFLICT_ROUTERID_INTF(l)[7]:OSPF Router id conflict is detected on interface. (ProcessId=1, RouterId=10.110.87.89, AreaId=0.0.0.0, InterfaceName=Vlanif95,  IpAddr=10.110.87.190, PacketSrcIp=10.110.87.190)

Alarm Information

Jul 25 2017 20:47:03 SMBPZ-SF-UG-01 %%01OSPF/4/CONFLICT_ROUTERID_INTF(l)[2]:OSPF Router id conflict is detected on interface. (ProcessId=1, RouterId=10.110.87.89, AreaId=0.0.0.0, InterfaceName=Vlanif99,  IpAddr=192.168.83.254, PacketSrcIp=192.168.83.254)

Jul 25 2017 20:47:01 SMBPZ-SF-UG-01 %%01OSPF/4/CONFLICT_ROUTERID_INTF(l)[3]:OSPF Router id conflict is detected on interface. (ProcessId=1, RouterId=10.110.87.89, AreaId=0.0.0.0, InterfaceName=Vlanif1,  IpAddr=10.110.87.89, PacketSrcIp=10.110.87.89)

Jul 25 2017 20:46:16 SMBPZ-SF-UG-01 %%01OSPF/4/CONFLICT_ROUTERID_INTF(l)[4]:OSPF Router id conflict is detected on interface. (ProcessId=1, RouterId=10.110.87.89, AreaId=0.0.0.0, InterfaceName=Vlanif95,  IpAddr=10.110.87.190, PacketSrcIp=10.110.87.190)

Jul 25 2017 20:44:55 SMBPZ-SF-UG-01 %%01OSPF/4/CONFLICT_ROUTERID_INTF(l)[5]:OSPF Router id conflict is detected on interface. (ProcessId=1, RouterId=10.110.87.89, AreaId=0.0.0.0, InterfaceName=Vlanif1,  IpAddr=10.110.87.89, PacketSrcIp=10.110.87.89)

Jul 25 2017 20:44:54 SMBPZ-SF-UG-01 %%01OSPF/4/CONFLICT_ROUTERID_INTF(l)[6]:OSPF Router id conflict is detected on interface. (ProcessId=1, RouterId=10.110.87.89, AreaId=0.0.0.0, InterfaceName=Vlanif99,  IpAddr=192.168.83.254, PacketSrcIp=192.168.83.254)

Jul 25 2017 20:44:11 SMBPZ-SF-UG-01 %%01OSPF/4/CONFLICT_ROUTERID_INTF(l)[7]:OSPF Router id conflict is detected on interface. (ProcessId=1, RouterId=10.110.87.89, AreaId=0.0.0.0, InterfaceName=Vlanif95,  IpAddr=10.110.87.190, PacketSrcIp=10.110.87.190)

Handling Process

        Ask the customer to change the router id as we think there is a same router id in the network.

But even we changed the router id there is also new alarm that the OSPF router id conflict with the new IP address.

Do capture on the access switch finding that the OSPF packets go out the interface and go back on the same interface, which causing OSPF router id conflict itself.

Solution
        There is a loop in the network , causing router receives the OSPF packets sending out itself. Checking the device one by one , solve the loop issue , then it works well.

END