Nexus Mechanism Driver Installation Guide¶
This is an installation guide for enabling the Nexus Mechanism Driver (MD) support on OpenStack. This guide only covers details on the Nexus MD install and does not cover OpenStack or Nexus 9K switch installation. The Prerequisites section contains links for this.
The prerequisites for installing the ML2 Nexus MD are as follows:
Requires neutron installation as described in Neutron Install documentation.
The ML2 Nexus MD have been tested on these OSs.
- RHEL 6.1 or above
- Ubuntu 14.04 or above
Your Nexus switch must be set-up as described in the next section Nexus Switch Setup.
Cisco Nexus 9K image version - NX-OS 7.0(3)I5(2) (minimum required for REST API Driver). Refer to Nexus 9K documents for upgrade/downgrade instructions. From this link, select the ‘Support’ option in the middle of the page for information on upgrade/downgrade guides, configuration and technical references.
Nexus Switch Setup¶
This section lists what is required to prepare the Nexus switch for operation with the Nexus Driver.
Your Nexus switch must be connected to a management network separate from the OpenStack data network. The Nexus MD must be able to access this network so it can communicate with the switch to set up your data flows.
The ML2 Nexus Rest API Driver requires feature nxapi to be enabled on the switch.
Each OpenStack compute host on the cloud must be connected to the switch using an interface dedicated solely to OpenStack data traffic. Connecting the OpenStack Network-Node(s) may also be needed depending on your network configuration. If Network Nodes are connected, you can pre-configure the tenant vlan range on the Nexus switchport; otherwise, like all compute nodes you can configure the Nexus ML2 Driver to manage the switchports by configuring the hostname to Nexus switchport mapping using the configuration option host_ports_mapping beneath the section [ml2_mech_cisco_nexus] of the neutron start-up config file.
Some pre-configuration must be performed by the Nexus switch administrator. For instance:
All participating OpenStack hosts interfaces must be enabled with no shutdown. If additional trunk vlans are needed for an interface, the administrator should manually apply these extra vlans using switchport trunk allowed vlan add <vlanid> and also include switchport mode trunk.
Possible port-channels pre-configuration:
- Peer-link configuration must always be pre-configured.
- The port-channel configuration must be preconfigured for all
non-baremetal cases. For baremetal cases, when administrator prefers
to have port-channels learned versus automatically creating
vpc-poolNexus driver config.
- When port-channels are learned, the interfaces must also be configured as members of the port-channel.
For VXLAN Overlay Configurations, enable the feature using the following Nexus CLI:
feature nv overlay feature vn-segment-vlan-based interface nve1 no shutdown source-interface loopback x # where x is same value as Nexus driver config 'nve_src_intf'
ML2 Nexus MD Installation¶
Install networking-cisco package as described in the section Installing the networking-cisco Package.
Configure Nexus ML2 Driver. Once the networking-cisco code is installed, it needs to be configured and enabled in neutron, the Nexus Mechanism Driver Administration Guide provides full details on how to create the neutron configs for various use cases. For details on each configuration parameters, refer to Nexus Configuration Reference.
Below is a simple VLAN configuration which can be applied to ML2 neutron config files
ml2_conf_cisco.inilocated in directory
/etc/neutron/plugins/ml2. The file
ml2_conf_cisco.iniis optional if you’d like to isolate cisco specific parameters.
[ml2] #- This neutron config specifies to use vlan type driver and use # cisco nexus mechanism driver. type_drivers = vlan tenant_network_types = vlan mechanism_drivers = openvswitch,cisco_nexus #- This neutron config specifies the vlan range to use. [ml2_type_vlan] network_vlan_ranges = physnet1:1400:3900 #- Provide Nexus credentials, OpenStack hostname, and nexus interface [ml2_mech_cisco_nexus:192.168.1.1] username=admin password=mySecretPasswordForNexus host_ports_mapping=host-1:[1/2] # deprecates config `host-1=1/2`
Restart neutron to pick-up configuration changes.
$ service neutron-server restart