The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter contains the following sections:
Step 1 | In a web browser, navigate to Cisco.com. |
Step 2 | Under Support, click All Downloads. |
Step 3 | In the center pane, click Cloud and Systems Management. |
Step 4 | If prompted, enter your Cisco.com username and password to log in. |
Step 5 | In the right pane, click Network Controllers and Applications, and then click Cisco Nexus Data Broker. |
Step 6 | Download and extract the Cisco Nexus Data Broker Release 3.2.0 application bundle zip file.
The application bundle zip file contains the following: |
Install the software on a Cisco Nexus 3000, 3100, 3200, 3500, or 9000 Series switch.
This process involves using the GUI to download the configuration, perform the upgrade, and then upload the configuration.
Step 1 | Navigate to the System tab under Administration.
The System Administration window is displayed. |
Step 2 | Click Download Configuration.
It downloads the configuration in a zip file format. The name of the zip file is configuration_startup.zip. |
Step 3 | Download the configuration in Cisco NDB 3.0 or Cisco NDB 3.1. |
Step 4 | Deactivate Cisco NDB and uninstall Cisco NDB using the following steps: |
Step 5 | configure terminal Example: device# configure terminal |
Step 6 | virtual-service virtual-services-name Example: device(config)# virtual-service <virtual-services-name> |
Step 7 | no activate Example: device(config-virt-serv)# no activate |
Step 8 | no virtual-service <virtual-services-name> Example: device(config)# no virtual-service <virtual-services-name> |
Step 9 | end Example: device(config-virt-serv)# end |
Step 10 | virtual-service uninstall name virtual-services-name Example: # virtual-service uninstall name <virtual-services-name> |
Step 11 | copy running-config startup-config Example: # copy running-config startup-config |
Step 12 | Install and activate Cisco NDB 3.2 using the following steps: |
Step 13 | virtual-service install name <virtual-services-name> package bootflash: ndb1000-sw-app-emb-k9-3.2.0.ova |
Step 14 | show virtual-service list Use the show command to check the status of the virtual service installation. After the status of the virtual service becomes listed as Installed, run the following commands to activate the service. |
Step 15 | configure terminal |
Step 16 | device(config)# virtual-service <virtual-services-name> |
Step 17 | device(config)# activate |
Step 18 | device(config)# end |
Step 19 | device(config)# copy running-config startup-config |
Step 20 | Run the ndb_launcher.py script from the ndb directory in the GitHub repository at https://github.com/datacenter/nexus9000/blob/master/nexusdatabroker/NDBActivator1.0.py using the python bootflash:ndb_launcher.py -v ndb command. Example: device# configure terminal device(config)# virtual-service <virtual-services-name> device(config)# no activate device(config)# show virtual-service list (Wait until deactivated complete) device(config)# activate device(config)# show virtual-service list (Wait until activated complete) device(config)# end device(config)# copy running-config startup-config |
Step 21 | Upload Cisco NDB 3.0 or 3.1 configuration that is downloaded in step 1 in the Cisco NDB user interface (UI). |
![]() Note | You cannot install a new version of the Cisco Nexus Data Broker Embedded if you already have an existing Cisco Monitor Manager Embedded application installed and active. |
Before you begin installing a new version of the Cisco Nexus Data Broker Embedded, you must:
Deactivate your current Cisco Monitor Manager Embedded OVA file.
Uninstall the Cisco Monitor Manager Embedded OVA file.
Ensure that you have at least 1 GB of available space in the bootflash. The ofa_mmemb-2.1.4-r2-nxos-SPA-k9.ova and ndb1000-sw-app-emb-k9-3.2.0.ova file require a total of 850 MB of space in the bootflash for the decompression and installation processes.
The Cisco Plug-in for OpenFlow needs to be connected to the Cisco Nexus Data Broker locally running on the Cisco Nexus 3000, 3100, 3200, 3500, or 9000 Series switch.
![]() Note | The steps in this procedure continue the steps that were completed in the previous section. |
Install and activate the Cisco Nexus Data Broker package and the Cisco Plug-in for OpenFlow package.
Enter the following pre-requisite command hardware profile openflow for the Cisco Nexus 3000 and 3100 Series switches. Enter the following pre-requisite command hardware profile forwarding-mode openflow-hybrid for the Cisco Nexus 3500 Series switches.
Step 1 | Enter the
configuration mode on the switch.
configure terminal | ||
Step 2 | Enter the
Cisco Plug-in for
OpenFlow configuration mode on the switch.
switch(config)# openflow | ||
Step 3 | Choose the
switch to which you want to connect.
switch(config-ofa)# switch switch_num
| ||
Step 4 | Choose the
pipeline to which you want to connect.
switch(config-ofa-switch)# pipeline pipeline_num
| ||
Step 5 | Configure the
controller address using vrf management.
switch(config-ofa-switch)# controller ipv4 management_interface_address port port_num vrf management security none
| ||
Step 6 | Assign ports to
the
Cisco Plug-in for
OpenFlow.
switch(config-ofa-switch)# of-port interface ethernet_port_num Example:switch(config-ofa-switch)# of-port interface ethernet1/10 | ||
Step 7 | Exit from the
current configuration command mode and return to EXEC mode.
switch(config-ofa-switch)# end | ||
Step 8 | Verify that the
Cisco Plug-in for
OpenFlow is connected to the
Cisco Nexus Data Broker.
switch# show openflow switch switch_num controllers |
The default HTTPS web link for the Cisco Nexus Data Broker GUI is https://Nexus_Switch_Management_IP:8443/monitor
![]() Note | You must manually specify the https:// protocol in your web browser. The controller must also be configured for HTTPS. |
See the Cisco Nexus Data Broker Configuration Guide for the procedures that you need to configure Cisco Nexus Data Broker.