Newly Created Segment connected to a T1 not present in T1's Forwarding Table

Products

• VMware NSX

Issue/Introduction

- When Tier-1 forwarding table is checked, the newly connected segments or any changes are not displayed. 

- If a new segment is created and attached to the same T1, we can't see the newly created segment's subnet under the T1's forwarding table.

-Any new updates to the policy is not published to the transport nodes 

Environment

VMware NSX
Impacted Versions: 3.2.2.0

Cause

- A static route was added on a T0/T1 Gateway with white space in the subnet.

For example,

when we add 10.0.0.1 /24, there is a space between 1 and /24.

- The NSX manager will allow you to save it with space. No error will be thrown.

- When the change is processed by the manager, an exception is hit and any new updates will fail to publish to the CCP, and thereby transport nodes.

- In the NSX manager logs, we can see "InvalidFormatException" in var/log/syslog*

---snip---

com.vmware.nsx.management.common.ip.utils.InvalidIPFormatException: null
        at com.vmware.nsx.management.common.ip.utils.IPv4Address.<init>(IPv4Address.java:241) ~[?:?]
        at com.vmware.nsx.management.common.ip.utils.IPObjectFactory.createIPAddress(IPObjectFactory.java:102) ~[?:?]
        at com.vmware.nsx.management.edge.publish.worker.RAPublisherHelper.isNetworkAllowedForAdvertisement(RAPublisherHelper.java:339) ~[?:?]

---snip---

 

 

 

Resolution

Issue is resolved in 3.2.4, 4.2.1 and higher releases. Upcoming releases will not let you to save the configuration with space. 

Workaround:

- Any space in the route advertisement with space should be manually removed and saved.