Logical-routers in failed status due to "FRR config failed:: ROUTING_CONFIG_ERROR (-1)"

Products

• VMware NSX

Issue/Introduction

The logical routers (T0, T0-VRF and T1) running on the edge nodes instance are in failed state with error "FRR config failed:: ROUTING_CONFIG_ERROR (-1)"



The Transport node(edge) reporting the error would not contain Tier0 BGP neighbor summary details

 

From the problematic edge node under /var/log/rcpm/frr_logs/frrfailedcfg.<date/time>.txt file, entries similar to the below will be seen:

 Note: The frrfailedcfg.<date/time>.txt logs are contained in a tar.bz2 tarball and will need to be extracted to view them.

ip prefix-list e###5##f-####-####-bf2f-############ seq 1 permit 172.#.#.#/27  le 32 ge 27
ip prefix-list e###5##f-####-####-bf2f-############ seq 2 permit 172.#.#.#/27  le 32 ge 27
ip prefix-list e###5##f-####-####-bf2f-############ seq 3 permit 172.#.#.#/27  le 43 ge 27 <<<<<<<<<<<<<<<<<<<<<<<
ip prefix-list e###5##f-####-####-bf2f-############ seq 4 permit 172.#.#.#/27  le 32 ge 27



Edge node logs

>>Under var/log/rcpm/frr-config.log has below error log lines

<Date and Time> <edge-node-name> NSX 9 SYSTEM [nsx@6876 comp="nsx-edge" subcomp="frr-config" username="frr" level="ERROR"] "Failed to execute: rc=1, out=b'', err=Command '['/usr/lib/frr/frr-reload.py', '--debug', '--reload', '/config/vmware/edge/frr/frrbasecfg.txt']' returned non-zero exit status 1."

>>Under var/log/rcpm/frr-reload.log

<Date and Time> INFO: All daemons connected to vtysh
<Date and Time> INFO: Called via "Namespace(debug=True, filename='/config/vmware/edge/frr/frrbasecfg.txt', input=None, overwrite=False, reload=True, skipdaemoncheck=False, stdout=False, test=False)"
<Date and Time> INFO: Loading Config object from file /config/vmware/edge/frr/frrbasecfg.txt
<Date and Time> ERROR: Command '['/usr/bin/vtysh', '-m', '-f', '/config/vmware/edge/frr/frrbasecfg.txt']' returned non-zero exit status 2.

 

 

Environment

VMware NSX 4.1.x

Cause

Invalid IPv4 prefix length configuration.

The frr process was unable to load the configuration since invalid prefix length was configured by the user

From the above config reference, an invalid IP prefix length "le_val" was set by the user (a value like "43" instead of the maximum valid "32" for IPv4 or "128" for IPv6). This prevents the entire configuration, including all newer entries, from being loaded.

Resolution

Review the prefix length in the Tier 0 Routing - IP Prefix Lists and correct invalid lengths.

For details on configuring IP Prefix List, please review the Create an NSX IP Prefix List.

Additional Information

In the later release 4.2.X and 9.0 from the UI and also API,
for IPv4 prefix list,
customer will NOT be able to configure incorrect values for "le" and "ge", value has to be between 0 to 32
for IPv6 prefix list,
customer will NOT be able to configure incorrect values for "le" and "ge", value has to be between 0 to 128.