%OSPF-5-NBR_RETRANSMISSIONS: message nexus 9000

[ShijuJose85082]

After upgrading to 10.3(6) we are seeing the following messages ,

%OSPF-5-NBR_RETRANSMISSIONS: ospf-<process id> [7644] Process re-originates LSA ID 1 LSA Type Network adv-rtr 10.42.42.1 in area 0.0.0.0 for Nbr X.X.X.X.

As per the following, this is the error message from 10.3(5) version,

https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/103x/system-messages/n9k-syslogs-routing-10-3-5-m.html

Is there any specific fix for this ? It keeps clogging the logs and unnecessary alerts. 

[marce1000]

  @ShijuJose85082                  >...OSPF-5-NBR_RETRANSMISSIONS...
                                    As you are saying these numbers are derived from syslog levels where 5 is a notice-alert only.
                                    Check if this can help you to mute them  : https://community.cisco.com/t5/switching/nexus-command-for-logging-discriminator/m-p/4908154/highlight/true#M550017

  M.                                

[Joseph W. Doherty]

---

@ShijuJose85082 wrote:

After upgrading to 10.3(6) we are seeing the following messages ,

%OSPF-5-NBR_RETRANSMISSIONS: ospf-<process id> [7644] Process re-originates LSA ID 1 LSA Type Network adv-rtr 10.42.42.1 in area 0.0.0.0 for Nbr X.X.X.X.

As per the following, this is the error message from 10.3(5) version,

https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/103x/system-messages/n9k-syslogs-routing-10-3-5-m.html

Is there any specific fix for this ? It keeps clogging the logs and unnecessary alerts. 

---

The ideal fix would be to identify and mitigate the reason for OSPF the retransmissions, if truly happening.

I presume you believe this issue was caused solely by the IOS version upgrade?  If so, perhaps moving back to 10.3(5) or moving forward to 10.3(7) or 10.4(4) (the latter, Cisco's suggested release).

[Pavel Tarakanov]

One of the possible reason:

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwc99335

There are several software defects related to this issue and to mitigate them it's better to upgrade to 10.4(4).

[Sergey Minsky]

Hi Pavel, 

We have upgraded to 10.4(5)M and the issue is still there. I don't see this version is in Affected Releases list. Do you know if that's still applied to 10.4(5)M?

Thanks,

Sergey

[Joseph W. Doherty]

---

@Sergey Minsky wrote:

Hi Pavel, 

We have upgraded to 10.4(5)M and the issue is still there. I don't see this version is in Affected Releases list. Do you know if that's still applied to 10.4(5)M?

Thanks,

Sergey

---

---

Well, no guarantees, but the reason I suggested 10.4(4) and NOT 10.4(5):

'cause (4) is the recommended release.

[MHM Cisco World]

This message appear for vPC nexus or standalone ?

MHM

[MHM Cisco World]

Any news about this issue 

MHM

[paul driver]

Hello
Check 10.42.42.1 rtr as the probable root cause for any of its links in area 0 towards  X.X.X.X. rtr, if necessarily isolate those links until error stops.

[Sergey Minsky]

We are seeing exactly the same issue started after we upgraded to 10.4(5)M

[Sergey Minsky]

What we tried over the weekend: We downgraded one of the NX-OS devices running 10.4(5)M to 10.4(4), and the messages flooding the logs stopped. When we upgraded it back to 10.4(5)M, everything cleared up, and we no longer see those messages. I believe this issue might be related to the router being isolated during the downgrades/upgrades.