NSX-T Edge stop routing traffic

Products

• VMware NSX

Issue/Introduction

On a newly created Namespace, Pods cannot communicate with traffic North of the T0 Router.
Previous workload are working fine.
Newly added routes on the T0 are not reflected on the T0 SR.
New routes advertised by the T1 routers are not reflected on the T0 SR.
In the Active NSX Edge TN syslog logs, you can see: /var/log/syslog*

syslog.1:<29>1 2020-09-10T12:20:15.936138+00:00 ###edge## NSX 2874 ROUTING [nsx@6876 comp="nsx-edge" subcomp="nsx-edge-rcpm.frr_config" level="INFO"] status of frr config buf  output ROUTING_CONFIG_ERROR  ret 0
syslog.1:<30>1 2020-09-10T12:20:15.936265+00:00 ###edge## start-stop-daemon 2870 - -  2020-09-10T12:20:15Z nsx-edge-rcpm 2874 frr_config [ERROR] FRR config failed:: ROUTING_CONFIG_ERROR (-1)  errorCode="EDG0200030"
syslog.1:<27>1 2020-09-10T12:20:15.936303+00:00 ###edge## NSX 2874 ROUTING [nsx@6876 comp="nsx-edge" subcomp="nsx-edge-rcpm.frr_config" level="ERROR" errorCode="EDG0200030"] FRR config failed:: 
ROUTING_CONFIG_ERROR (-1)

Edge TN root password could have expired prior to this event.

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment

Environment

VMware NSX-T Data Center 2.5.x
VMware NSX-T Data Center

Resolution

This issue is fixed in NSX-T 2.5.2 and 3.0.1

Additional Information

New created workloads may not be able to access the network behind the NSX-T T0 Router.