External Router Status: False, while creating External Network during VIO 3.0.x deployment in VDS mode.

Products

• VMware
• VMware Integrated OpenStack

Issue/Introduction

Symptoms:

· External router status shows false while creating External Network

· Running neutron net-create EXTNET --debug --provider:network_type=portgroup --provider:physical_network=dvportgroup-153 --router:external=True

Results in router:external false.

· +--------------------------+--------------------------------------+
| Field | Value |
+---------------------------+--------------------------------------+
| admin_state_up | True |
| created_at | 2016-12-28T08:01:37 |
| description | |
| id | XXXXXaXb-XXXX-XcdX-beXX-aeddeaXXXXcd |
| name | EXTNET |
| port_security_enabled | True |
| provider:network_type | portgroup |
| provider:physical_network | dvportgroup-XXX |
| provider:segmentation_id | 0 |
| router:external | False |
| shared | False |
| status | ACTIVE |
| subnets | |
| tags | |
| tenant_id | XXXXXXXXXXXeX2dXaXfabXXbXXccXXfc |
| updated_at | XXXX-XX-XXT00:00:00 |
+---------------------------+--------------------------------------+

· Router status stays same if network is created using CLI mode or from the Horizon Dashboard.

In the Neutron Server logs you see entries similar to:

#The request to the Neutron serves shows correct.

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

Environment

VMware Integrated OpenStack 3.0.x
VMware Integrated OpenStack 2.0.x
VMware Integrated OpenStack 2.5.x

Cause

It is because External network providers are for floating IPs and NATing which are NSX mode features.

Resolution

The product is working as designed. This feature is part of a deployment that uses the NSX mode. External network providers are for floating IP's and NATing which are NSX mode feature sets.

Additional Information