Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

'Number must not be null' when creating a new Routed Network or modifying an existing Routed Network (67193)

Last Updated: 2/28/2020Categories: TroubleshootingTotal Views: 3568Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

'Number must not be null' when creating a new Routed Network or modifying an existing Routed Network

Cause

This issue occurs when NAT rules configured on the Edge Gateway are missing their appropriate <ruleTag> element.

Resolution

This is a known issue affecting vCloud Director 9.5.

This issue is resolved in 9.5.0.4 and 9.7.

Workaround

To workaround the issue you will need to follow the steps below:
Note: The steps below will require the use of tools to interact with the NSX API such as Postman or cURL

Unless specified, the following Headers are required for all of the REST API calls to the NSX Manager:

Authentication - Basic Authentication: (admin, <admin.password>)

Accept: application/xml

Content-type: application/xml

1. Use the NSX API to retrieve a list of Edge Gateways

GET https://NSX_FQDN/api/4.0/edges

2. Take note of the <edge-id> of the affected Edge Gateway
Note: <edge-id> is the unique identifier for the edge e.g. edge-7, which will have been present in the output of the previous API Request.

3. Use the NSX API to retrieve the configuration of the affected Edge Gateway

GET https://NSX_FQDN/api/4.0/edges/<edge-id>

4. Copy the Response XML to a notepad file so you can revert the configuration if needed
5. Locate the <natRule> element in the Response XML
6. Locate the NAT rules that have missing <ruleTag> elements
7. Create a <ruleTag> element, using the same value as the <ruleId>.

<ruleId>196646</ruleId>
<ruleTag>196646</ruleTag>

8. Update the Edge Gateway using the Updated Response XML

PUT https://NSX_FQDN/api/4.0/edges/edge-id

Note: The Updated Response XML is used as the Body of your PUT request

9. Once the Update succeeds, navigate to the vCloud Director UI
10. You will now be able to create a new Routed Network or modifying an existing Routed Network

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud Director for Service Provider

VMware Cloud Director

Related Versions:

VMware Cloud Director for Service Provider 9.5.x

Take Our Survey

Support Assistant