Difference between revisions of "Mellanox-Neutron-Juno-Ubuntu-InfiniBand"
Line 8: | Line 8: | ||
This driver supports Mellanox embedded switch functionality as part of the VPI (Ethernet/InfiniBand) HCA. Mellanox ML2 Mechanism Driver provides functional parity with Mellanox Neutron plugin. | This driver supports Mellanox embedded switch functionality as part of the VPI (Ethernet/InfiniBand) HCA. Mellanox ML2 Mechanism Driver provides functional parity with Mellanox Neutron plugin. | ||
− | Mellanox ML2 Mechanism Driver supports DIRECT (pci passthrough) vnic type. For vnic type configuration API details, please refer to configuration reference guide | + | Mellanox ML2 Mechanism Driver supports DIRECT (pci passthrough) vnic type. For vnic type configuration API details, please refer to configuration reference guide. |
+ | Hardware vNICs mapped to the guest VMs allow higher performance and advanced features such as RDMA (remote direct memory access). | ||
The driver supports VLAN network type to facilitate virtual networks either on Ethernet or InfiniBand fabrics. | The driver supports VLAN network type to facilitate virtual networks either on Ethernet or InfiniBand fabrics. | ||
Line 24: | Line 25: | ||
* The software package iproute2 - (http://www.linuxfoundation.org/collaborate/workgroups/networking/iproute2 ) installed on all Compute nodes | * The software package iproute2 - (http://www.linuxfoundation.org/collaborate/workgroups/networking/iproute2 ) installed on all Compute nodes | ||
* Add repository | * Add repository | ||
− | + | sudo add-apt-repository http://www.mellanox.com/repository/solutions/openstack/juno/ubuntu/ | |
=InfiniBand Network= | =InfiniBand Network= | ||
Line 35: | Line 36: | ||
To configure OpenSM: | To configure OpenSM: | ||
− | 1. Make sure that all the PKeys are predefined in the | + | 1. Make sure that all the PKeys are predefined in the '''/etc/opensm/partitions.conf'''. |
− | |||
− | |||
management=0xffff,ipoib, sl=0, defmember=full: ALL, ALL_SWITCHES=full,SELF=full; | management=0xffff,ipoib, sl=0, defmember=full: ALL, ALL_SWITCHES=full,SELF=full; | ||
− | + | 2. For every network you want to configure in Neutron, you have to configure the PKey associated with the VLAN of this network (defined in Neutron): vlan1=0x1, ipoib, sl=0, defmember=full : ALL; | |
Below is an example of the configuration of the partitions.conf file in case you have 10 VLANs defined in the configuration of the file: | Below is an example of the configuration of the partitions.conf file in case you have 10 VLANs defined in the configuration of the file: | ||
− | /etc/neutron/plugins/mlnx/mlnx_conf.ini. ( network_vlan_ranges = physnet1:1:10) | + | '''/etc/neutron/plugins/mlnx/mlnx_conf.ini'''. ( network_vlan_ranges = physnet1:1:10) |
− | + | management=0x7fff,ipoib, sl=0, defmember=full : ALL, ALL_SWITCHES=full,SELF=full; | |
− | management=0x7fff,ipoib, sl=0, defmember=full : ALL, ALL_SWITCHES=full,SELF=full; | + | vlan1=0x1, ipoib, sl=0, defmember=full: ALL_CAS; |
− | vlan1=0x1, ipoib, sl=0, defmember=full: ALL_CAS; | + | vlan2=0x2, ipoib, sl=0, defmember=full: ALL_CAS; |
− | vlan2=0x2, ipoib, sl=0, defmember=full: ALL_CAS; | + | vlan3=0x3, ipoib, sl=0, defmember=full: ALL_CAS; |
− | vlan3=0x3, ipoib, sl=0, defmember=full: ALL_CAS; | + | vlan4=0x4, ipoib, sl=0, defmember=full: ALL_CAS; |
− | vlan4=0x4, ipoib, sl=0, defmember=full: ALL_CAS; | + | vlan5=0x5, ipoib, sl=0, defmember=full: ALL_CAS; |
− | vlan5=0x5, ipoib, sl=0, defmember=full: ALL_CAS; | + | vlan6=0x6, ipoib, sl=0, defmember=full: ALL_CAS; |
− | vlan6=0x6, ipoib, sl=0, defmember=full: ALL_CAS; | + | vlan7=0x7, ipoib, sl=0, defmember=full: ALL_CAS; |
− | vlan7=0x7, ipoib, sl=0, defmember=full: ALL_CAS; | + | vlan8=0x8, ipoib, sl=0, defmember=full: ALL_CAS; |
− | vlan8=0x8, ipoib, sl=0, defmember=full: ALL_CAS; | + | vlan9=0x9, ipoib, sl=0, defmember=full: ALL_CAS; |
− | vlan9=0x9, ipoib, sl=0, defmember=full: ALL_CAS; | + | vlan10=0xa, ipoib, sl=0, defmember=full: ALL_CAS; |
− | vlan10=0xa, ipoib, sl=0, defmember=full: ALL_CAS; | ||
− | |||
− | + | 3. Modify the following line in the file '''/etc/opensm/opensm.conf''' from FALSE to TRUE: | |
− | + | allow_both_pkeys TRUE | |
− | allow_both_pkeys TRUE | ||
− | |||
5. Restart the OpenSM: | 5. Restart the OpenSM: | ||
− | + | # /etc/init.d/opensmd restart | |
− | #/etc/init.d/opensmd restart | ||
− | |||
==Controller Node== | ==Controller Node== | ||
2. Install Mellanox RPMs: | 2. Install Mellanox RPMs: | ||
− | + | #apt-get install -y openstack-neutron-mellanox eswitchd mlnx-dnsmasq | |
− | |||
− | # | ||
− | |||
3. Edit the following file: '''/usr/lib/systemd/system/neutron-mlnx-agent.service''' | 3. Edit the following file: '''/usr/lib/systemd/system/neutron-mlnx-agent.service''' | ||
− | + | Change the /etc/neutron/plugins/mlnx/mlnx.ini to /etc/neutron/plugins/mlnx/mlnx_conf.ini | |
− | Change the | ||
− | |||
4. Run: | 4. Run: | ||
− | + | # /etc/init.d/neutron-plugin-mlnx-agent start | |
− | #/etc/init.d/neutron-plugin-mlnx-agent start | ||
− | |||
5. Run: | 5. Run: | ||
− | + | # service daemon-reload | |
− | #service daemon-reload | ||
− | |||
6. Make sure ML2 is the current Neutron plugin by checking the core_plugin parameter in '''/etc/neutron/neutron.conf''': | 6. Make sure ML2 is the current Neutron plugin by checking the core_plugin parameter in '''/etc/neutron/neutron.conf''': | ||
− | + | core_plugin = neutron.plugins.ml2.plugin.Ml2Plugin | |
− | core_plugin = neutron.plugins.ml2.plugin.Ml2Plugin | ||
− | |||
7. Make sure /etc/neutron/plugin.ini is pointing to '''/etc/neutron/plugins/ml2/ml2_conf.ini''' (symbolic link) | 7. Make sure /etc/neutron/plugin.ini is pointing to '''/etc/neutron/plugins/ml2/ml2_conf.ini''' (symbolic link) | ||
8. Modify /etc/neutron/plugins/ml2/ml2_conf.ini by adding the following: | 8. Modify /etc/neutron/plugins/ml2/ml2_conf.ini by adding the following: | ||
− | + | [ml2] | |
− | [ml2] | + | type_drivers = vlan,flat |
− | type_drivers = vlan,flat | + | tenant_network_types = vlan |
− | tenant_network_types = vlan | + | mechanism_drivers = mlnx, openvswitch |
− | mechanism_drivers = mlnx, openvswitch | + | # or mechanism_drivers = mlnx, linuxbridge |
− | # or mechanism_drivers = mlnx, linuxbridge | + | [ml2_type_vlan] |
− | [ml2_type_vlan] | + | network_vlan_ranges = physnet1:1:10 |
− | network_vlan_ranges = physnet1:1:10 | + | [eswitch] |
− | [eswitch] | + | # (StrOpt) Type of Network Interface to allocate for VM: |
− | # (StrOpt) Type of Network Interface to allocate for VM: | + | # mlnx_direct or hostdev according to libvirt terminology |
− | # mlnx_direct or hostdev according to libvirt terminology | + | vnic_type = hostdev |
− | vnic_type = hostdev | + | |
− | |||
9. Start (or restart) the Neutron server: | 9. Start (or restart) the Neutron server: | ||
− | + | # /etc/init.d/neutron-server restart | |
− | #/etc/init.d/neutron-server restart | ||
− | |||
== Network Node== | == Network Node== | ||
Line 121: | Line 100: | ||
Prerequisites: | Prerequisites: | ||
− | + | E_IPoIB port is configured and up | |
− | + | ||
1. Make sure that eIPoIB module is up and configured in '''/etc/infiniband/openib.conf''': For more information, please refer to eIPoIB configuration in Mellanox OFED User Manual. | 1. Make sure that eIPoIB module is up and configured in '''/etc/infiniband/openib.conf''': For more information, please refer to eIPoIB configuration in Mellanox OFED User Manual. | ||
E_IPOIB_LOAD=yes | E_IPOIB_LOAD=yes | ||
+ | |||
+ | |||
2. Restart openibd: | 2. Restart openibd: | ||
− | + | # service openibd restart | |
− | #service openibd restart | + | |
− | + | ||
− | 3. Modify the | + | 3. Modify the network bridge configuration according to the use of OpenVswitch or LinuxBridge |
− | + | * 3.1 OpenVswitch '''/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini''' | |
− | [ | + | [ovs] |
− | + | bridge_mappings = physnet1:br-<eIPoIB interface> | |
− | + | * 3.2 LinuxBridge file '''/etc/neutron/plugins/linuxbridge/linuxbridge_conf.ini''': | |
− | + | [linux_bridge] | |
− | + | physical_interface_mappings = physnet1:<eIPoIB interface> | |
− | [ | + | |
− | |||
− | |||
NOTE: In order to obtain the eIPoIB interface name, run the ethtool tool command (see below) and check that driver name is eth_ipoib: | NOTE: In order to obtain the eIPoIB interface name, run the ethtool tool command (see below) and check that driver name is eth_ipoib: | ||
− | #ethtool -i <eIPoIB_interface> | + | # ethtool -i <eIPoIB_interface> |
driver: eth_ipoib | driver: eth_ipoib | ||
− | + | ..... | |
− | + | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
4. Restart neutron-linuxbridge-agent and neutron-dhcp-agent: | 4. Restart neutron-linuxbridge-agent and neutron-dhcp-agent: | ||
− | #service neutron-linuxbridge-agent | + | # service neutron-linuxbridge-agent restart |
− | #service neutron-openvswitch-agent | + | # service neutron-openvswitch-agent restart |
NOTE: For DHCP support, the Network node should use the Mellanox Dnsmasq driver as the DHCP driver. | NOTE: For DHCP support, the Network node should use the Mellanox Dnsmasq driver as the DHCP driver. | ||
+ | |||
===DHCP Server (Usually part of the Network node)=== | ===DHCP Server (Usually part of the Network node)=== | ||
+ | |||
1. Modify '''/etc/neutron/dhcp_agent.ini''' as follows and according to OVS or Linuxbridge: | 1. Modify '''/etc/neutron/dhcp_agent.ini''' as follows and according to OVS or Linuxbridge: | ||
− | + | dhcp_driver = mlnx_dhcp.MlnxDnsmasq | |
− | dhcp_driver = mlnx_dhcp.MlnxDnsmasq | + | # or interface_driver = neutron.agent.linux.interface.BridgeInterfaceDriver |
− | #or interface_driver = neutron.agent.linux.interface.BridgeInterfaceDriver | + | interface_driver = neutron.agent.linux.interface.OVSInterfaceDriver |
− | interface_driver = neutron.agent.linux.interface.OVSInterfaceDriver | + | |
− | + | ||
2. Start DHCP server: | 2. Start DHCP server: | ||
− | + | # service neutron-dhcp-agent restart | |
− | #service neutron-dhcp-agent | ||
− | |||
==Compute Nodes== | ==Compute Nodes== | ||
Line 173: | Line 146: | ||
To configure the Compute Node: | To configure the Compute Node: | ||
− | 1.Configure | + | 1.Configure Mellanox OpenStack Juno repository |
− | + | # sudo add-apt-repository http://www.mellanox.com/repository/solutions/openstack/juno/rhel7 | |
− | # | ||
− | |||
2. Install Mellanox RPMs: | 2. Install Mellanox RPMs: | ||
− | + | # apt-get install -y openstack-neutron-mellanox eswitchd mlnx-dnsmasq | |
− | |||
− | #apt-get install -y openstack-neutron-mellanox eswitchd mlnx-dnsmasq | ||
− | |||
3. Edit the following file: '''/usr/lib/systemd/system/neutron-mlnx-agent.service''' | 3. Edit the following file: '''/usr/lib/systemd/system/neutron-mlnx-agent.service''' | ||
− | + | Change the /etc/neutron/plugins/mlnx/mlnx.ini to /etc/neutron/plugins/mlnx/mlnx_conf.ini | |
− | Change the /etc/neutron/plugins/mlnx/mlnx.ini to /etc/neutron/plugins/mlnx/mlnx_conf.ini | ||
− | |||
4. Run: | 4. Run: | ||
− | + | # service enable neutron-mlnx-agent | |
− | #service enable neutron-mlnx-agent | ||
− | |||
5. Run: | 5. Run: | ||
− | + | # service daemon-reload | |
− | #service daemon-reload | ||
− | |||
6. Apply MLNX patch for Juno: | 6. Apply MLNX patch for Juno: | ||
− | + | # pushd /usr/lib/python2.7/site-packages/nova/virt/libvirt/ | |
− | #pushd /usr/lib/python2.7/site-packages/nova/virt/libvirt/ | + | # wget http://www.mellanox.com/repository/solutions/openstack/juno/rhel7/patch/mlnx_juno.patch |
− | #wget http://www.mellanox.com/repository/solutions/openstack/juno/rhel7/patch/mlnx_juno.patch | + | # patch < mlnx_juno.patch |
− | #patch < mlnx_juno.patch | + | # popd |
− | #popd | ||
− | |||
7. Create the file '''/etc/modprobe.d/mlx4_ib.conf''' and add the following: | 7. Create the file '''/etc/modprobe.d/mlx4_ib.conf''' and add the following: | ||
− | + | options mlx4_ib sm_guid_assign=0 | |
− | options mlx4_ib sm_guid_assign=0 | ||
− | |||
8. Restart Nova: | 8. Restart Nova: | ||
− | + | # /etc/init.d/nova-compute restart | |
− | #/etc/init.d/nova-compute restart | ||
− | |||
9. Restart the driver: | 9. Restart the driver: | ||
− | + | # /etc/init.d/opensm restart | |
− | # /etc/init.d/opensm restart | + | # /etc/init.d/openibd restart |
− | # /etc/init.d/openibd restart | ||
− | |||
10. In the file '''/etc/neutron/plugins/mlnx/mlnx_conf.ini''', the parameters tenant_network_type , and network_vlan_ranges should be configured as the controllers: | 10. In the file '''/etc/neutron/plugins/mlnx/mlnx_conf.ini''', the parameters tenant_network_type , and network_vlan_ranges should be configured as the controllers: | ||
− | + | physical_interface_mappings = physnet1:<ib_interface>(for example physnet1:ib0) | |
− | physical_interface_mappings = physnet1:<ib_interface>(for example physnet1:ib0) | ||
− | |||
11. Modify the file '''/etc/eswitchd/eswitchd.conf''' as follows: | 11. Modify the file '''/etc/eswitchd/eswitchd.conf''' as follows: | ||
− | |||
fabrics = physnet1:<ib_interface> (for example physnet1:ib0) | fabrics = physnet1:<ib_interface> (for example physnet1:ib0) | ||
− | |||
12. Start eSwitchd: | 12. Start eSwitchd: | ||
− | + | # service eswitchd restart | |
− | #service eswitchd restart | ||
− | |||
13. Start the Neutron agent: | 13. Start the Neutron agent: | ||
− | + | # service neutron-mlnx-agent restart | |
− | #service neutron-mlnx-agent restart | ||
− | |||
==Known issues and Troubleshooting== | ==Known issues and Troubleshooting== | ||
For known issues and troubleshooting options refer to [https://community.mellanox.com/docs/DOC-1127 Mellanox OpenStack Troubleshooting] | For known issues and troubleshooting options refer to [https://community.mellanox.com/docs/DOC-1127 Mellanox OpenStack Troubleshooting] |
Revision as of 11:38, 23 July 2015
Contents
Overview
Mellanox Neutron ML2 Driver
Mellanox ML2 Mechanism Driver implements the ML2 Plugin Mechanism Driver API.
This driver supports Mellanox embedded switch functionality as part of the VPI (Ethernet/InfiniBand) HCA. Mellanox ML2 Mechanism Driver provides functional parity with Mellanox Neutron plugin.
Mellanox ML2 Mechanism Driver supports DIRECT (pci passthrough) vnic type. For vnic type configuration API details, please refer to configuration reference guide. Hardware vNICs mapped to the guest VMs allow higher performance and advanced features such as RDMA (remote direct memory access).
The driver supports VLAN network type to facilitate virtual networks either on Ethernet or InfiniBand fabrics.
- Mellanox OpenStack Neutron Agent (L2 Agent) runs on each compute node.
- Agent should apply VIF connectivity based on mapping between a VIF (VM vNIC) and Embedded Switch port.
Mellanox Neutron Plugin
For details regarding Mellanox Neutron plugin, please refer to https://wiki.openstack.org/wiki/Mellanox-Neutron-Havana-Ubuntu.
Prerequisites
- A running OpenStack environment installed with the ML2 plugin on top of Linux Bridge.
- All nodes equipped with Mellanox ConnectX®-3 Network Adapter (http://www.mellanox.com/page/products_dyn?product_family=119)
- Mellanox OFED 2.4 or greater installed on all nodes. Please refer to Mellanox website for the latest OFED: http://www.mellanox.com/page/products_dyn?product_family=26&mtag=linux_sw_drivers
- SR-IOV enabled on all compute nodes. For more information, please refer to Mellanox Community click [1].
- The software package iproute2 - (http://www.linuxfoundation.org/collaborate/workgroups/networking/iproute2 ) installed on all Compute nodes
- Add repository
sudo add-apt-repository http://www.mellanox.com/repository/solutions/openstack/juno/ubuntu/
InfiniBand Network
The Mellanox Neutron Plugin use InfiniBand Partitions (PKeys) to separate Networks.
SM Node
OpenSM Configuration – Without UFM
To configure OpenSM:
1. Make sure that all the PKeys are predefined in the /etc/opensm/partitions.conf.
management=0xffff,ipoib, sl=0, defmember=full: ALL, ALL_SWITCHES=full,SELF=full;
2. For every network you want to configure in Neutron, you have to configure the PKey associated with the VLAN of this network (defined in Neutron): vlan1=0x1, ipoib, sl=0, defmember=full : ALL;
Below is an example of the configuration of the partitions.conf file in case you have 10 VLANs defined in the configuration of the file: /etc/neutron/plugins/mlnx/mlnx_conf.ini. ( network_vlan_ranges = physnet1:1:10)
management=0x7fff,ipoib, sl=0, defmember=full : ALL, ALL_SWITCHES=full,SELF=full; vlan1=0x1, ipoib, sl=0, defmember=full: ALL_CAS; vlan2=0x2, ipoib, sl=0, defmember=full: ALL_CAS; vlan3=0x3, ipoib, sl=0, defmember=full: ALL_CAS; vlan4=0x4, ipoib, sl=0, defmember=full: ALL_CAS; vlan5=0x5, ipoib, sl=0, defmember=full: ALL_CAS; vlan6=0x6, ipoib, sl=0, defmember=full: ALL_CAS; vlan7=0x7, ipoib, sl=0, defmember=full: ALL_CAS; vlan8=0x8, ipoib, sl=0, defmember=full: ALL_CAS; vlan9=0x9, ipoib, sl=0, defmember=full: ALL_CAS; vlan10=0xa, ipoib, sl=0, defmember=full: ALL_CAS;
3. Modify the following line in the file /etc/opensm/opensm.conf from FALSE to TRUE:
allow_both_pkeys TRUE
5. Restart the OpenSM:
# /etc/init.d/opensmd restart
Controller Node
2. Install Mellanox RPMs:
#apt-get install -y openstack-neutron-mellanox eswitchd mlnx-dnsmasq
3. Edit the following file: /usr/lib/systemd/system/neutron-mlnx-agent.service
Change the /etc/neutron/plugins/mlnx/mlnx.ini to /etc/neutron/plugins/mlnx/mlnx_conf.ini
4. Run:
# /etc/init.d/neutron-plugin-mlnx-agent start
5. Run:
# service daemon-reload
6. Make sure ML2 is the current Neutron plugin by checking the core_plugin parameter in /etc/neutron/neutron.conf:
core_plugin = neutron.plugins.ml2.plugin.Ml2Plugin
7. Make sure /etc/neutron/plugin.ini is pointing to /etc/neutron/plugins/ml2/ml2_conf.ini (symbolic link)
8. Modify /etc/neutron/plugins/ml2/ml2_conf.ini by adding the following:
[ml2] type_drivers = vlan,flat tenant_network_types = vlan mechanism_drivers = mlnx, openvswitch # or mechanism_drivers = mlnx, linuxbridge [ml2_type_vlan] network_vlan_ranges = physnet1:1:10 [eswitch] # (StrOpt) Type of Network Interface to allocate for VM: # mlnx_direct or hostdev according to libvirt terminology vnic_type = hostdev
9. Start (or restart) the Neutron server:
# /etc/init.d/neutron-server restart
Network Node
To configure the Network node:
Prerequisites:
E_IPoIB port is configured and up
1. Make sure that eIPoIB module is up and configured in /etc/infiniband/openib.conf: For more information, please refer to eIPoIB configuration in Mellanox OFED User Manual.
E_IPOIB_LOAD=yes
2. Restart openibd:
# service openibd restart
3. Modify the network bridge configuration according to the use of OpenVswitch or LinuxBridge
- 3.1 OpenVswitch /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini
[ovs] bridge_mappings = physnet1:br-<eIPoIB interface>
- 3.2 LinuxBridge file /etc/neutron/plugins/linuxbridge/linuxbridge_conf.ini:
[linux_bridge] physical_interface_mappings = physnet1:<eIPoIB interface>
NOTE: In order to obtain the eIPoIB interface name, run the ethtool tool command (see below) and check that driver name is eth_ipoib:
# ethtool -i <eIPoIB_interface> driver: eth_ipoib .....
4. Restart neutron-linuxbridge-agent and neutron-dhcp-agent:
# service neutron-linuxbridge-agent restart # service neutron-openvswitch-agent restart
NOTE: For DHCP support, the Network node should use the Mellanox Dnsmasq driver as the DHCP driver.
DHCP Server (Usually part of the Network node)
1. Modify /etc/neutron/dhcp_agent.ini as follows and according to OVS or Linuxbridge:
dhcp_driver = mlnx_dhcp.MlnxDnsmasq # or interface_driver = neutron.agent.linux.interface.BridgeInterfaceDriver interface_driver = neutron.agent.linux.interface.OVSInterfaceDriver
2. Start DHCP server:
# service neutron-dhcp-agent restart
Compute Nodes
To configure the Compute Node:
1.Configure Mellanox OpenStack Juno repository
# sudo add-apt-repository http://www.mellanox.com/repository/solutions/openstack/juno/rhel7
2. Install Mellanox RPMs:
# apt-get install -y openstack-neutron-mellanox eswitchd mlnx-dnsmasq
3. Edit the following file: /usr/lib/systemd/system/neutron-mlnx-agent.service
Change the /etc/neutron/plugins/mlnx/mlnx.ini to /etc/neutron/plugins/mlnx/mlnx_conf.ini
4. Run:
# service enable neutron-mlnx-agent
5. Run:
# service daemon-reload
6. Apply MLNX patch for Juno:
# pushd /usr/lib/python2.7/site-packages/nova/virt/libvirt/ # wget http://www.mellanox.com/repository/solutions/openstack/juno/rhel7/patch/mlnx_juno.patch # patch < mlnx_juno.patch # popd
7. Create the file /etc/modprobe.d/mlx4_ib.conf and add the following:
options mlx4_ib sm_guid_assign=0
8. Restart Nova:
# /etc/init.d/nova-compute restart
9. Restart the driver:
# /etc/init.d/opensm restart # /etc/init.d/openibd restart
10. In the file /etc/neutron/plugins/mlnx/mlnx_conf.ini, the parameters tenant_network_type , and network_vlan_ranges should be configured as the controllers:
physical_interface_mappings = physnet1:<ib_interface>(for example physnet1:ib0)
11. Modify the file /etc/eswitchd/eswitchd.conf as follows:
fabrics = physnet1:<ib_interface> (for example physnet1:ib0)
12. Start eSwitchd:
# service eswitchd restart
13. Start the Neutron agent:
- service neutron-mlnx-agent restart
Known issues and Troubleshooting
For known issues and troubleshooting options refer to Mellanox OpenStack Troubleshooting