Chapter 1. Cisco Nexus Data Broker Embedded Overview

About Cisco Nexus Data Broker Embedded

Supported Web Browsers

Prerequisites for Cisco Nexus 3000, 3100, 3200, 3500, and 9000 Series Switches

Cisco Nexus Data Broker Software Release Filename Matrix

Chapter 2. Deploying Cisco Nexus Data Broker Embedded for OpenFlow

Obtaining the Cisco Nexus Data Broker Embedded Software for OpenFlow

Upgrading From Release 2.x to Release 3.0

Installing and Activating the Cisco Nexus Data Broker Embedded Software for OpenFlow

Configuring the Cisco Plug-in for OpenFlow

Logging in to the Cisco Nexus Data Broker GUI

Chapter 3. Deploying Cisco Nexus Data Broker Embedded for NX-API

Obtaining the Cisco Nexus Data Broker Embedded Software for NX-API

Installing and Activating the Cisco Nexus Data Broker Embedded Software for NX-API Mode

Logging in to the Cisco Nexus Data Broker GUI

Chapter 4. Configuring the Setup for a Use Case in the Embedded Mode

Configuring Cisco Nexus Data Broker For Embedded Mode Using The CLI

Configuring Cisco Nexus Data Broker For A Use Case Using The GUI

Copyright Page

The Java logo is a trademark or registered trademark of Sun Microsystems, Inc. in the U.S. or other countries.

Chapter 1. Cisco Nexus Data Broker Embedded Overview

This chapter contains the following sections:

- About Cisco Nexus Data Broker Embedded

- Supported Web Browsers

- Prerequisites for Cisco Nexus 3000, 3100, 3200, 3500, and 9000 Series Switches

- Cisco Nexus Data Broker Software Release Filename Matrix

About Cisco Nexus Data Broker Embedded

Visibility into application traffic has traditionally been important for infrastructure operations to maintain security, troubleshooting, and compliance mechanisms, and to perform resource planning. With the technological advances and growth in cloud-based applications, it has become imperative to gain increased visibility into the network traffic. Traditional approaches to gain visibility into network traffic are expensive and rigid, making it difficult to do in large-scale deployments.

Cisco Nexus Data Broker Embedded with Cisco Nexus Switches provides a software-defined, programmable solution to aggregate copies of network traffic using Switched Port Analyzer (SPAN) or network Test Access Points (TAP) for monitoring and visibility. As opposed to traditional network taps and monitoring solutions, this packet-brokering approach offers a simple, scalable and cost-effective solution that is well suited for customers who need to monitor higher-volume and business-critical traffic for efficient use of security, compliance, and application performance monitoring tools.

The Cisco Nexus Data Broker Embedded option provides the flexibility for you to run the Cisco Nexus Data Broker software directly on a Cisco Nexus 3000, 3100, 3200, 3500, or 9000 Series switch in a single-switch deployment. This is suitable for smaller, co-located facilities where customers need only a single Cisco Nexus 3000, 3100, 3200, 3500, or 9000 Series switch for TAP/SPAN aggregation, because it eliminates the requirement to have a separate virtual machine for the Cisco Nexus Data Broker application.

The Cisco Nexus Data Broker Embedded solution supports the following:

- Support for the OpenFlow mode or the NX-API mode of operation.

Note

The OpenFlow mode and the NX-API mode are supported on both Cisco Nexus 3000 Series and Cisco Nexus 9000 Series switches. Cisco Nexus 9500 supports only NX-API mode of deployment. Cisco Nexus 3500 supports only Openflow mode of deployment.

You can enable only one mode, either OpenFlow or NX-API mode, at a time.

In order to start or stop the Cisco Nexus Data Broker application in embedded mode, you should activate or de-activate the ofa file. Do not use ./runxnc.sh as it is not the right way to start the application.

Note

Starting with Cisco Nexus 3000 Release 7.x, the NX-API configuration is supported on the following Cisco Nexus 3100 Series switches:

- Cisco Nexus 3172 switches

- Cisco Nexus 3132 switches

- Cisco Nexus 3164 switches

- Cisco Nexus 31128 switches

- Cisco Nexus 3232 switches

- Cisco Nexus 3264 switches

- Starting with Cisco Nexus Data Broker Release 3.x, Java 8 update is supported on Cisco Nexus Data Broker in embedded mode.

- Support for Layer-7 filtering for the HTTP traffic using the HTTP methods.

- Support for VLAN and MPLS tag stripping.

- The ability to aggregate traffic from multiple TAP or SPAN ports connected to a single switch.

- Support for Q-in-Q to tag input source TAP and SPAN ports.

- Symmetric hashing or symmetric load balancing.

- Rules for matching monitoring traffic based on Layer 1 through Layer 4 information.

- The ability to replicate and forward traffic to multiple monitoring tools.

- Timestamp tagging using the Precision Time Protocol.

- Packet truncation beyond a specified number of bytes to discard payload.

- Security features, such as role-based access control (RBAC), and integration with an external Active Directory using RADIUS or TACACS for authentication and authorization.

- End-to-end path visibility and both port and flow level statistics for troubleshooting.

- Robust Representational State Transfer (REST) API and web-based GUI for all functions.

Supported Web Browsers

The following web browsers are supported for Cisco Nexus Data Broker Embedded:

- Firefox 18.x and later versions

- Chrome 24.x and later versions

Note

JavaScript 1.5 or a later version must be enabled in your browser.

Prerequisites for Cisco Nexus 3000, 3100, 3200, 3500, and 9000 Series Switches

Cisco Nexus Data Broker is supported on Cisco Nexus 3000, 3100, 3200, 3500, and 9000 series switches. Before you deploy the software, you must do the following:

- Ensure that you have administrative rights to log in to the switch.

- Verify that the management interface of the switch (mgmt0) has an IP address configured by running the switch# show running-config interface mgmt0 command.

- Add the VLAN range in the database that is to be used in Cisco Nexus Data Broker for tap aggregation and inline monitoring redirection to support VLAN filtering. For example, the syntax is vlan <range of VLAN IDs>. For example, the VLAN range is <1-3967>.

For running the OpenFlow and NX-API mode on the Cisco Nexus 3000, 3100, 3500, and 9000 Series switches, see the following pre-requisites.

Device Models

OpenFlow Mode

NX-API Mode

Nexus 3000 Series switches

Enter the # hardware profile openflow command at the prompt.

Enter the following commands at the prompt:

- # hardware profile tcam region qos 0

- # hardware profile tcam region racl 0

- # hardware profile tcam region vacl 0

- # hardware profile tcam region ifacl 1024 double-wide

- # hardware profile tap-aggregation

Nexus 3164Q switches

The OpenFlow mode is not supported on the Nexus 3164Q switches.

Enter the following commands at the prompt:

- # hardware profile tcam region qos 0

- # hardware profile tcam region racl 0

- # hardware profile tcam region vacl 0

- # hardware profile tcam region ifacl 1024 double-wide

Nexus 3200 Series switches

Enter the hardware access-list tcam region openflow 256 command at the prompt.

Enter the following commands at the prompt:

- # hardware access-list tcam region e-racl 0

- # hardware access-list tcam region span 0

- # hardware access-list tcam region redirect 0

- # hardware access-list tcam region vpc-convergence 0

- # hardware access-list tcam region racl-lite 256

- # hardware access-list tcam region l3qos-intra-lite 0

- # hardware access-list tcam region ifacl 256 double-wide

Nexus 9000 Series switches

Enter the hardware access-list tcam region openflow 512 command at the prompt.

Enter the following commands at the prompt:

- # hardware access-list tcam region qos 0

- # hardware access-list tcam region vacl 0

- # hardware access-list tcam region racl 0

- # hardware access-list tcam region redirect 0

- # hardware access-list tcam region vpc-convergence 0

- #hardware access-list tcam region ifacl 1024 double-wide

- # hardware access-list tcam region mac-ifacl 512

Cisco Nexus Data Broker Software Release Filename Matrix

See the Cisco Nexus Data Broker software release filename matrix for more information on the software images:

Mode of Deployment

OpenFlow

NX-API

N3K

N3500

N9K

File Name

Embedded

N

Y

Y

N

Y

ndb1000-sw-app-emb-nxapi-3.0.0-k9.zip

Embedded

Y

N

Y

Y

N

ndb1000-sw-app-emb-3.0.0-ofa_
mmemb-1.1.5-r3-n3000-SPA-k9.zip

Embedded

Y

N

Y

N

Y

ndb1000-sw-app-emb-3.0.0-ofa_
mmemb-2.1.4-r2-nxos-SPA-k9.zip

Chapter 2. Deploying Cisco Nexus Data Broker Embedded for OpenFlow

This chapter contains the following sections:

- Obtaining the Cisco Nexus Data Broker Embedded Software for OpenFlow

- Upgrading From Release 2.x to Release 3.0

- Installing and Activating the Cisco Nexus Data Broker Embedded Software for OpenFlow

- Configuring the Cisco Plug-in for OpenFlow

- Logging in to the Cisco Nexus Data Broker GUI

Obtaining the Cisco Nexus Data Broker Embedded Software for OpenFlow

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.0.0 application bundle zip file.
The application bundle zip file contains the following:

- The Cisco Nexus Data Broker Software Application package, for example, ndb1000-sw-app-emb-k9-3.0.0.ova

- The Cisco Plug-in for OpenFlow package, ofa_mmemb-2.1.4-r2-nxos-SPA-k9.ova

What to Do Next

Install the software on a Cisco Nexus 3000, 3100, 3200, 3500, or 9000 Series switch.

Upgrading From Release 2.x to Release 3.0

This process involves using the GUI to download the configuration, perform the upgrade, and then upload the configuration.

SUMMARY STEPS

1.    Navigate to the System tab under Administration.

2.    Click Download Configuration.

3.    Save the configuration file on your local desktop.

4.    Stop the Cisco Nexus Data Broker. Deactivate and uninstall the old instance.

5.    Install Cisco Nexus Data Broker 3.0 instance.

6.    Navigate to the System tab under Administration.

7.    Click Upload Configuration.

8.    Restart the Cisco Nexus Data Broker by performing no activate within the virtual service and by activating it again.

DETAILED STEPS

Command or Action

Purpose

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

Save the configuration file on your local desktop.

Step 4

Stop the Cisco Nexus Data Broker. Deactivate and uninstall the old instance.

Step 5

Install Cisco Nexus Data Broker 3.0 instance.

Step 6

Navigate to the System tab under Administration.

The System Administration window is displayed.

Step 7

Click Upload Configuration.

It uploads the configuration that you have downloaded. It restores the configuration in the new version.

Step 8

Restart the Cisco Nexus Data Broker by performing no activate within the virtual service and by activating it again.

Installing and Activating the Cisco Nexus Data Broker Embedded Software for OpenFlow

Before You Begin

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.

Important:
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.0.0.ova file require a total of 850 MB of space in the bootflash for the decompression and installation processes.

Command or Action

Purpose

Step 1

switch# copy [scp: | ftp: | http:] //download_dir ofa_mmemb-2.1.4-r2-nxos-SPA-k9.ova bootflash: vrf management

Copies the Cisco Plug-in for OpenFlow package from the directory where you downloaded it to the switch.

Step 2

switch# copy [scp: | ftp: | http:] //download_dir ndb1000-sw-app-emb-k9-3.0.0.ova bootflash:vrf management

Copies the Cisco Nexus Data Broker Embedded package from the directory where you downloaded it to the switch.

Step 3

switch# show virtual-service list

Monitors the status of the copy processes.

Step 4

switch# virtual-service install name ofa_ndbemb package bootflash:ofa_mmemb-2.1.4-r2-nxos-SPA-k9.ova

Installs the Cisco Plug-in for OpenFlow package on the switch.

Step 5

switch# virtual-service install name ndb_emb package bootflash:ndb1000-sw-app-emb-k9-3.0.0.ova

Installs the Cisco Nexus Data Broker Embedded package on the switch.

Step 6

switch# show virtual-service list

Monitors the status of the installations.

Note:
Do not continue until both OVA files have been successfully installed.

Step 7

switch# configure terminal

Enters global configuration mode on the switch.

Step 8

switch (config)# virtual-service ofa_ndbemb

Starts the virtual service for the Cisco Plug-in for OpenFlow package and enters virtual service configuration mode on the switch.

Step 9

switch(config-virt-serv)# activate

Activates the Cisco Plug-in for OpenFlow package.

Step 10

switch(config-virt-serv)# exit

Returns to global configuration mode.

Step 11

switch(config)# virtual-service ndb_emb

Starts the virtual service for the Cisco Nexus Data Broker Embedded package and enters virtual service configuration mode on the switch.

Step 12

switch(config-virt-serv)# activate

Activates the Cisco Nexus Data Broker Embedded package.

Step 13

switch(config-virt-serv)# exit

Exits virtual service configuration mode on the switch.

Step 14

switch(config)# show virtual-service list

Monitors the status of the package activations.

Configuring the Cisco Plug-in for OpenFlow

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.

Before You Begin

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

Caution:
Set the switch_num to 1. This is the default value. Only expert users should set the switch_num number to any value other than 1.

Step 4

Choose the pipeline to which you want to connect.
switch(config-ofa-switch)# pipeline pipeline_num

Caution:
Set the pipeline_num to 201 for Cisco Nexus 3000, 3100, 3200, and 9300 Series switches. This is the default value. Only expert users should set the pipeline_num number to any value other than 201.

Set the pipeline_num to 203 for Cisco Nexus 3500 Series switches This is the default value. Only expert users should set the pipeline_num number to any value other than 203.

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

Note:

- The controller ipv4 address should match the management interface (mgmt0) address.

- By default, the Cisco Plug-in for OpenFlow listens on port 6653.

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

See the Cisco Plug-in for OpenFlow Configuration Guide 1.3

Logging in to the Cisco Nexus Data Broker GUI

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.

Step 1

In your web browser, enter the Cisco Nexus Data Broker web link, for example, https://Nexus_Switch_Management_IP:8443/monitor.

Step 2

On the launch page, do the following:

1. Enter your username and password.
The default username and password is admin/admin.

2. Click Log In.

What to Do Next

See the Cisco Nexus Data Broker Configuration Guide for the procedures that you need to configure Cisco Nexus Data Broker.

Chapter 3. Deploying Cisco Nexus Data Broker Embedded for NX-API

This chapter contains the following sections:

- Obtaining the Cisco Nexus Data Broker Embedded Software for NX-API

- Installing and Activating the Cisco Nexus Data Broker Embedded Software for NX-API Mode

- Logging in to the Cisco Nexus Data Broker GUI

Obtaining the Cisco Nexus Data Broker Embedded Software for NX-API

Step 1

In a web browser, navigate to Cisco.com.

Step 2

In the center pane, click Cloud and Systems Management.

Step 3

If prompted, enter your Cisco.com username and password to log in.

Step 4

In the right pane, click Network Controllers and Applications, and then click Cisco Nexus Data Broker.

Step 5

Download and extract the Cisco Nexus Data Broker Software Application bundle.
The application bundle zip file contains the following:

- The Cisco Nexus Data Broker Embedded package, ndb1000-sw-app-emb-k9-3.0.0.ova

What to Do Next

Install the software on a Cisco Nexus 3000, 3100, 3200, 3500, or 9000 Series switch.

Installing and Activating the Cisco Nexus Data Broker Embedded Software for NX-API Mode

Before You Begin

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.

Important:
Ensure that you have sufficient space available in the bootflash. The ndb1000-sw-app-emb-k9-3.0.0.ova file require a total of ~55 MB of space in the bootflash for the decompression and installation processes.

Command or Action

Purpose

Step 1

switch# copy [scp: | ftp: | http:] //download_dir ndb1000-sw-app-emb-k9-3.0.0.ova bootflash:vrf management

Copies the Cisco Nexus Data Broker Embedded package from the directory where you downloaded it to the switch.

Step 2

switch# show virtual-service list

Monitors the status of the copy processes.

Step 3

switch# virtual-service install name ndb_emb package bootflash:ndb1000-sw-app-emb-k9-3.0.0.ova

Installs the Cisco Nexus Data Broker Embedded package on the switch.

Step 4

switch# show virtual-service list

Monitors the status of the installations.

Note:
Do not continue until both OVA files have been successfully installed.

Step 5

switch# configure terminal

Enters global configuration mode on the switch.

Step 6

switch(config)# virtual-service ndb_emb

Starts the virtual service for the Cisco Nexus Data Broker Embedded package and enters virtual service configuration mode on the switch.

Step 7

switch(config-virt-serv)# activate

Activates the Cisco Nexus Data Broker Embedded package.

Step 8

switch(config-virt-serv)# exit

Exits virtual service configuration mode on the switch.

Step 9

switch(config)# show virtual-service list

Monitors the status of the package activations.

Logging in to the Cisco Nexus Data Broker GUI

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.

Step 1

In your web browser, enter the Cisco Nexus Data Broker web link, for example, https://Nexus_Switch_Management_IP:8443/monitor.

Step 2

On the launch page, do the following:

1. Enter your username and password.
The default username and password is admin/admin.

2. Click Log In.

What to Do Next

See the Cisco Nexus Data Broker Configuration Guide for the procedures that you need to configure Cisco Nexus Data Broker.

Chapter 4. Configuring the Setup for a Use Case in the Embedded Mode

This chapter contains the following sections:

- Configuring Cisco Nexus Data Broker For Embedded Mode Using The CLI

- Configuring Cisco Nexus Data Broker For A Use Case Using The GUI

Configuring Cisco Nexus Data Broker For Embedded Mode Using The CLI

Complete the following steps to configure Cisco Nexus Data Broker with Cisco Nexus 3500-X Series switches for embedded mode using the CLI.

Note

Limitations: This use case does not consider the support for inline redirection and Q-in-Q.

SUMMARY STEPS

1.    Configure TCAM and reload the switch.

2.    Download and copy the ofa and NDB embedded files to the switch.

3.    Install both Cisco Nexus Data Broker and OpenFlow.

4.    Configure OpenFlow.

DETAILED STEPS

Command or Action

Purpose

Step 1

Configure TCAM and reload the switch.

The command reboots the system.

Step 2

Download and copy the ofa and NDB embedded files to the switch.

Make sure that both ofa and NDB embedded files are in the switch.

Step 3

Install both Cisco Nexus Data Broker and OpenFlow.

Use the show virtual-service list CLI command to view the progress of the installation.

Step 4

Configure OpenFlow.

Configure the OpenFlow switch.

Example: Configuring Cisco Nexus Data Broker For A Use Case Using The CLI

Configure TCAM and reload the switch.

switch# configure
Enter configuration commands, one per line.  End with CNTL/Z.
switch(config)# hardware profile tcam region ifacl 1024 double-wide

switch(config)# copy running-config startup-config
[########################################] 100%
Copy complete, now saving to disk (please wait)...

switch(config)# reload
WARNING: This command will reboot the system
Do you want to continue? (y/n) [n] y

Install both Cisco Nexus Data Broker and OpenFlow.

switch# configure

Enter configuration commands, one per line.  End with CNTL/Z.
switch(config)# virtual-service ndbemb
switch(config-virt-serv)# activate
Note: Activating virtual-service 'ndbemb', this might take a few minutes.
Use 'show virtual-service list' for progress.

switch(config-virt-serv)# show virtual-service list
Virtual Service List:
Name                    Status             Package Name
-----------------------------------------------------------------------
ndbemb                  Activating         ndb1000-sw-app-emb-k9-3.0.0.ova

switch(config-virt-serv)# show virtual-service list
Virtual Service List:
Name                    Status             Package Name
-----------------------------------------------------------------------
ndbemb                  Activating         ndb1000-sw-app-emb-k9-3.0.0.ova

switch(config-virt-serv)# show virtual-service list
Virtual Service List:
Name                    Status             Package Name
-----------------------------------------------------------------------
ndbemb                  Activated          ndb1000-sw-app-emb-k9-3.0.0.ova

switch(config-virt-serv)# exit
switch(config)# exit

switch# virtual-service install name ofa package bootflash:ofa_mmemb-1.1.5-r3-n3000-SPA-k9.ova
Note: Installing package 'bootflash:/ofa_mmemb-1.1.5-r3-n3000-SPA-k9.ova' for virtual service 'ofa'.
Once the install has finished, the VM may be activated.
Use 'show virtual-service list' for progress.

switch# show virtual-service list
Virtual Service List:

Name                    Status             Package Name
-----------------------------------------------------------------------
ndbemb                  Activated          ndb1000-sw-app-emb-k9-3.0.0.ova
ofa                     Installing         ofa_mmemb-1.1.5-r3-n3000-SPA-k9.ova

switch# show virtual-service list
Virtual Service List:

Name                    Status             Package Name
-----------------------------------------------------------------------
ndbemb                  Activated          ndb1000-sw-app-emb-k9-3.0.0.ova
ofa                     Installed          ofa_mmemb-1.1.5-r3-n3000-SPA-k9.ova

switch# configure
Enter configuration commands, one per line.  End with CNTL/Z.
switch(config)# virtual-service ofa
switch(config-virt-serv)# activate
Note: Activating virtual-service 'ofa', this might take a few minutes.
Use 'show virtual-service list' for progress.
switch(config-virt-serv)# show virtual-service list

Virtual Service List:
Name                    Status             Package Name
-----------------------------------------------------------------------
ndbemb                  Activated          ndb1000-sw-app-emb-k9-3.0.0.ova
ofa                     Activating         ofa_mmemb-1.1.5-r3-n3000-SPA-k9.ova

switch(config-virt-serv)# show virtual-service list
Virtual Service List:

Name                    Status             Package Name
-----------------------------------------------------------------------
ndbemb                  Activated          ndb1000-sw-app-emb-k9-3.0.0.ova
ofa                     Activated          ofa_mmemb-1.1.5-r3-n3000-SPA-k9.ova

switch(config-virt-serv)#

Configure OpenFlow.

switch# configure
Enter configuration commands, one per line.  End with CNTL/Z.
switch(config)# openflow
switch(config-ofa)# switch 1
switch(config-ofa-switch)# pipeline 203
switch(config-ofa-switch)# controller ipv4 10.16.206.130  port 6653 vrf management security none
switch(config-ofa-switch)# of-port interface ethernet1/1-2
switch(config-ofa-switch)# of-port interface ethernet1/47
switch(config-ofa-switch)#

What to Do Next

For embedded mode, complete the steps for configuring Cisco Nexus Data Broker using the GUI as outlined in the next section.

Configuring Cisco Nexus Data Broker For A Use Case Using The GUI

Complete the following steps to configure Cisco Nexus Data Broker with Cisco Nexus 3500-X Series switches for a typical use case using the GUI.

Step 1

Open a Web browser window and log into Cisco Nexus Data Broker.
The configured device is available in the Topology window.

Step 2

Click Port Definition.
Verify that all the ports that were added in OpenFlow are displayed in the tab.

Step 3

Click Administration.
The devices learned are displayed in the Nodes Learned tab. Verify that the device that was added in Cisco Nexus Data Broker in OpenFlow configuration is displayed in the tab. The device is automatically added in the Device Connections tab, but it is not connected to NX-API mode.

Step 4

Enable NX-API mode on the device using the feature nxapi CLI command at the prompt.

Step 5

Click Edit device connection and update the user name and the password.
In the Edit Device Connection window, the default user name is XNC and the default password is used. Replace the default user name with the actual user name and the default password with the password of the device. If the device is connected successfully in the NX-API mode, it is highlighted in Blue in the Device Connections tab. If it is not connected successfully in the NX-API mode, it is highlighted in Gray. Make sure that the device is connected successfully in the NX-API mode. In the Nodes Learned tab, two devices are now listed, the same one is in OpenFlow mode and the other is in NX-API mode.

Step 6

Click Port Definition.
Configure the ports as per the use case.

Step 7

Click Configure in Port Eth ½ and add it as a SPAN port.

Step 8

Click Configure in port Eth 1/47 and add it as a Monitoring Device.

Step 9

To configure the time stamp (ttag), edit the monitoring port.

Step 10

Check Enable Timestamp Tagging and click Submit.
In the Port Definition window, the ttag information is displayed next to the monitoring port.

Step 11

Create filters.

Step 12

Click Connections tab.
Create Connection to pass the traffic to the interested traffic. In the use case, only one SPAN and one monitor port is used.

Step 13

Enter the Connection Name, Destination Device, filters, Source Device, and port.

Step 14

Click Install Connection. Now the setup is ready for the use case.

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: Click Here . Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)