Configure NSX plug-in

Load Balancer-as-a-Service and Firewall-as-a-Service

Procedure 7.5. To configure OpenStack Networking to use the NSX plug-in

While the instructions in this section refer to the VMware NSX platform, this is formerly known as Nicira NVP.

Install the NSX plug-in, as follows:
```
# apt-get install neutron-plugin-vmware
```

Edit /etc/neutron/neutron.conf and set:

core_plugin = vmware

Example neutron.conf file for NSX:

core_plugin = vmware
rabbit_host = 192.168.203.10
allow_overlapping_ips = True

To configure the NSX controller cluster for the OpenStack Networking Service, locate the [default] section in the /etc/neutron/plugins/vmware/nsx.ini file, and add the following entries (for database configuration, see Install Networking Services in Installation Guide):

To establish and configure the connection with the controller cluster you must set some parameters, including NSX API endpoints, access credentials, and settings for HTTP redirects and retries in case of connection failures:
```
nsx_user = <admin user name>
nsx_password = <password for nsx_user>
req_timeout = <timeout in seconds for NSX_requests> # default 30 seconds
http_timeout = <tiemout in seconds for single HTTP request> # default 10 seconds
retries = <number of HTTP request retries> # default 2
redirects = <maximum allowed redirects for a HTTP request> # default 3
nsx_controllers = <comma separated list of API endpoints>
```
To ensure correct operations, the nsx_user user must have administrator credentials on the NSX platform.
A controller API endpoint consists of the IP address and port for the controller; if you omit the port, port 443 is used. If multiple API endpoints are specified, it is up to the user to ensure that all these endpoints belong to the same controller cluster. The OpenStack Networking VMware NSX plug-in does not perform this check, and results might be unpredictable.
When you specify multiple API endpoints, the plug-in load-balances requests on the various API endpoints.
The UUID of the NSX Transport Zone that should be used by default when a tenant creates a network. You can get this value from the NSX Manager's Transport Zones page:
```
default_tz_uuid = <uuid_of_the_transport_zone>
```

default_l3_gw_service_uuid = <uuid_of_the_gateway_service>

Warning

	Warning
Ubuntu packaging currently does not update the Neutron init script to point to the NSX configuration file. Instead, you must manually update `/etc/default/neutron-server` to add this line: NEUTRON_PLUGIN_CONFIG = /etc/neutron/plugins/vmware/nsx.ini

Ubuntu packaging currently does not update the Neutron init script to point to the NSX configuration file. Instead, you must manually update /etc/default/neutron-server to add this line:

NEUTRON_PLUGIN_CONFIG = /etc/neutron/plugins/vmware/nsx.ini

Restart neutron-server to apply new settings:
```
# service neutron-server restart
```

Example nsx.ini file:

[DEFAULT]
default_tz_uuid = d3afb164-b263-4aaa-a3e4-48e0e09bb33c
default_l3_gw_service_uuid=5c8622cc-240a-40a1-9693-e6a5fca4e3cf
nsx_user=admin
nsx_password=changeme
nsx_controllers=10.127.0.100,10.127.0.200:8888

Note

	Note
To debug `nsx.ini` configuration issues, run this command from the host that runs `neutron-server`: # neutron-check-nsx-config <path/to/nsx.ini> This command tests whether `neutron-server` can log into all of the NSX Controllers and the SQL server, and whether all UUID values are correct.

To debug nsx.ini configuration issues, run this command from the host that runs neutron-server:

# neutron-check-nsx-config <path/to/nsx.ini>

This command tests whether neutron-server can log into all of the NSX Controllers and the SQL server, and whether all UUID values are correct.

Questions? Discuss on ask.openstack.org
Found an error? Report a bug against this page

Legal notices