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 Software Application bundle.
The application bundle zip file contains the following: |
Install the software on a Cisco Nexus 3000, 3100, 3500, or 9000 Series switch.
Note | You cannot install a new version of the Cisco Nexus Data Broker Embedded if you already have an existing Cisco Nexus Data Broker 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 sufficient space available in the bootflash. The ndb1000-sw-app-emb-k9-2.2.0.ova file require a total of ~55 MB of space in the bootflash for the decompression and installation processes.
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, Release 2.2 for the procedures that you need to configure Cisco Nexus Data Broker.
Complete the following steps to change the connection type from ONEPK to NX-API:
Step 1 | Select Admin and click Management. |
Step 2 | In the
Devices tab,
select
Edit against
the embedded device.
The Edit Device Connection dialog is displayed. |
Step 3 | Change the Connection Type from ONEPK to NX-API. |
Step 4 | Click
Edit Device
Connection to confirm the change and save the setting.
Verify that the device name is updated to display the NX prefix. See the Cisco Nexus Data Broker Configuration Guide, Release 2.2 for more information. |