These files must be edited with information related to the NSX-T environment to enable the Neutron plugin to interact with the NSX-T deployment.


  1. Edit the neutron.conf file to set the core Neutron plugin [DEFAULT] core_plugin = vmware_nsxp. To enable the NSX-T Manager plugin: [DEFAULT] core_plugin = vmware_nsxv3
  2. Edit the nsx.ini configuration file to configure the plugin for your NSX deployment.
    NSX-T OpenStack Plugin properties go under the [nsx_p] section of the nsx.ini configuration file.

    The configuration properties below also apply to the NSX-T Manager plugin, and are specified in the [nsx_v3] configuration section.

    The minimal set of configuration properties that need to be defined are:
    Variable Description
    nsx_api_managers This parameter allows a list of comma separated manager endpoints.
    nsx_api_user Administrator NSX-T Manager user name, usually admin.
    nsx_api_password Administrator NSX-T Manager password.
    insecure Set to False to enforce verification of NSX Manager server certificate. Defaults to True.
    ca_file CA bundle files to use in verifying the NSX Manager server certificate. This option is ignored if "insecure" is set to True. If "insecure" is set to False and this option is unset, the system root CAs will be used to verify the server certificate.
    nsx_api_managers The name or UUID of the default NSX overlay transport zone that will be used for creating Neutron networks. It needs to be created in NSX before starting Neutron.
    default_tier0_router This must be a Policy Manager NSX-T Tier0 name gateway router or UUID to which future OpenStack Logical Routers (NSX-T Tier1) will be connected (under “Routing/Routers”).
    dhcp_profile Enter either a UUID or name. See Create a DHCP Profile in NSX Manager.
    metadata_proxy Enter either a UUID or name. See Create a Metadata Proxy.
  3. Restart Neutron to pick-up the changes in the nsx.ini file by running the command: ps-aux |grep neutron.
  4. Verify that nsx.ini and neutron.conf are present in the output. Note that Neutron accepts one or more configuration files in the command line. These files are merged when the configuration is parsed so that the configuration file structure can reflect a particular user’s preferences.
    ps -aux |grep neutron 
    stack     7688  0.0  1.8 311332 148904 ?       Ss   Nov26  21:10 
    /usr/bin/python /usr/local/bin/neutron-server --config-file  
    /etc/neutron/neutron.conf --config-file