'Number must not be null' when creating a new Routed Network or modifying an existing Routed Network
Article ID: 341432
Updated On:
Products
VMware Cloud Director
Issue/Introduction
Symptoms:
'Number must not be null' when creating a new Routed Network or modifying an existing Routed Network
'Number must not be null' when creating a new Routed Network or modifying an existing Routed Network
Environment
VMware Cloud Director for Service Provider 9.5.x
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:
1. Use the NSX API to retrieve a list of Edge Gateways
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>.
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
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.
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 needed5. 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<ruleTag>196646</ruleTag>
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
Feedback
Yes
No
Powered by
