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

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 ActionPurpose
    Step 1 Configure TCAM and reload the switch.  

    The command reboots the system.

     
    Step 2Download 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 3Install both Cisco Nexus Data Broker and OpenFlow.  

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

     
    Step 4Configure 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.