OSPF adjacencies are deleted with MD5 authentication after NSX Edge HA failover

Products

• VMware NSX for vSphere

Issue/Introduction

Symptoms:

In an NSX for vSphere 6.2.4 environment where the NSX Edge is configured for HA with OSPF graceful restart configured and MD5 is used for authentication, OSPF fails to start gracefully. Adjacencies forms only after the dead timer expires on the OSPF neighbor nodes.

Environment

VMware NSX for vSphere 6.2.x

Resolution

This issue is resolved in VMware NSX for vSphere 6.4.1

Additional Information

• During the time the OSPF Dead-Timer runs down to 0, the NSX Edge logs displays an error similar to:
  
  2016-10-12T11:43:18+00:00 NSX-MER1B-ESGA.vumc.nl-0 routing[997]: [user.emerg] EXCEPTION 0x3e02-42 (0000): OSPF 1 Counterfeit packet received.
  
  Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

To be alerted when this document is updated, click the Subscribe to Article link in the Actions box