Guest

Cisco UCS B-Series Blade Server Software

Cisco usNIC Deployment Guide for Cisco UCS B-Series Blade Servers, Release 2.2

  • Viewing Options

  • PDF (1.4 MB)
  • EPUB (174.5 KB)
  • MOBI (279.3 KB)
  • Feedback
Overview of Cisco usNIC

Overview of Cisco usNIC

The Cisco user-space NIC (Cisco usNIC) feature improves the performance of software applications that run on the Cisco UCS servers in your data center by bypassing the kernel when sending and receiving networking packets. The applications interact directly with a Cisco UCS VIC second generation or later adapter, which improves the networking performance of your high-performance computing cluster. To benefit from Cisco usNIC, your applications must use the Message Passing Interface (MPI) instead of sockets or other communication APIs.

Cisco usNIC offers the following benefits for your MPI applications:

  • Provides a low-latency and high-throughput communication transport.

  • Employs the standard and application-independent Ethernet protocol.

  • Takes advantage of low­latency forwarding, Unified Fabric, and integrated management support in the following Cisco data center platforms:
    • Cisco UCS server

    • Cisco UCS VIC second generation or later generation adapter

    • 10 or 40GbE networks

Standard Ethernet applications use user-space socket libraries, which invoke the networking stack in the Linux kernel. The networking stack then uses the Cisco eNIC driver to communicate with the Cisco VIC hardware. The following figure shows the contrast between a regular software application and an MPI application that uses usNIC.

Figure 1. Kernel-Based Network Communication versus Cisco usNIC-Based Communication

Cisco usNIC Prerequisites

To benefit from Cisco usNIC, your configuration has the following prerequisites:

Configuring Cisco usNIC in Cisco UCS Manager


Note


The Cisco usNIC scripts do not support the upgrade or degrade of an operating system. To update the operating system, first ensure you uninstall the usNIC drives, update your operating system, and then reinstall the usNIC drivers. The other option is to update the operating system, uninstall the usNIC drivers, and reinstall the usNIC drivers .


Before You Begin
Make sure that the following software and hardware components are installed on the Cisco UCS server:
  • A supported Linux operating system distribution release. For more information, see the appropriate Hardware and Software Interoperability guide.

  • GCC, G++, and Gfortran must be installed

  • rdma-3.6 or later RPMs

  • Cisco UCS VIC second generation or later adapter

  • If you install Open MPI in a non-default location, depending on the particular OS distribution release installed on your server, you will also need libibverbs-devel and libnl1-devel or libnl3-devel. If you have libnl1 installed, then you will need libnl1-devel and if you have libnl3 installed, then you will need libnl3-devel. If you have do not have libnl1-devel or libnl3-devel installed, then you will need to install both libnl3 and libnl3-devel.

Important:

For information on supported Linux operating system distributions, see the content of the usNIC folder that is included in the UCS Drivers ISO bundle. See Cisco UCS Virtual Interface Card Drivers for Linux Installation Guide.

Procedure
    Step 1   Configure the Cisco usNIC properties and BIOS settings using Cisco UCS Manager GUI or Cisco UCS Manager CLI.
    Step 2   Ensure the kernel option CONFIG_INTEL_IOMMU is selected in the kernel. Enable the Intel IOMMU driver in the Linux kernel by manually adding 'intel_iommu =on' in the grub.conf file (/boot/grub/grub.conf):
     KEYBOARDTYPE=pc KEYTABLE=us rd NO DM rhgb quiet intel_iommu=on
    Step 3   Verify if the running kernel has booted with the intel_iommu=on option.
    $ cat /proc/cmdline | grep iommu
    Step 4   Reboot your Cisco UCS server.

    You must reboot your server for the changes to take effect after you configure Cisco usNIC.

    Step 5   Install the Cisco usNIC Linux drivers.

    For more information about installing the drivers, see Installing Linux Drivers for Cisco usNIC.


    What to Do Next

    After you complete configuring Cisco usNIC and installing the Linux drivers, verify that Cisco usNIC is functioning properly. For more information about how to verify the installation, see Verifying the Cisco usNIC Installation.

    Creating a usNIC Connection Policy using the Cisco Manager GUI

    Procedure
      Step 1   In the Navigation pane, click the LAN tab.
      Step 2   On the LAN tab, expand LAN > Policies.
      Step 3   Expand the root node.
      Step 4   Right-click usNIC Connection Policies and choose Create usNIC Connection Policy.
      Step 5   In the Create usNIC Connection Policy dialog box, complete the following fields:
      Name Description

      Name field

      The name of the policy.

      This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the object has been saved.

      Description field

      A description of the policy. We recommend that you include information about where and when the policy should be used.

      Number of usNICs field

      The number of usNICs that you want to create.

      Each MPI process running on the server requires a dedicated usNIC. You can create up to 116 usNICs on one adapter to sustain 116 MPI processes running simultaneously. We recommend that you create at least as many usNICs, per usNIC-enabled vNIC, as there are physical cores on your server. For example, if you have 8 physical cores on your server, create 8 usNICs.

      Adapter Policy drop-down list

      The adapter policy that you want to specify for the usNIC. Cisco recommends that you choose the usNIC adapter policy, which is created by default.

      Configuring a usNIC Ethernet Adapter Policy

      Procedure
        Step 1   In the Navigation pane, click the Servers tab.
        Step 2   On the Servers tab, expand Servers > Policies > root > Adapter Policies.
        Step 3   Click Eth Adapter Policy usNIC.
        Step 4   In the Work pane, click the General tab.
        Step 5   (Optional)Modify the details in the Resources and Options sections as needed. For more information about configuring Ethernet adapter policies, see the Cisco UCS Manager Configuration Guide.

        Modifying a usNIC using the Cisco UCS Manager GUI

        Procedure
          Step 1   In the Navigation pane, click the Servers tab.
          Step 2   On the Servers tab, expand Servers > Service Profiles > root.
          Step 3   Expand the service profile node where you want to configure the usNIC and click vNICs.
          Step 4   In the Work pane, click the Network tab.
          Step 5   In the vNICs area, choose a vNIC and click Modify.
          Step 6   In the Adapter Performance Profile area of the Modify vNIC dialog box, choose Linux from the Adapter Policy drop-down list.
          Step 7   In the Connection Policies area, click the usNIC radio button.
          Step 8   Choose the usNIC connection policy that you created from the usNIC Connection Policy drop-down list.
          Step 9   Click OK.
          Step 10   Click Save Changes.
          Step 11   In the Navigation pane, click the service profile that you just modified.
          Step 12   In the Work pane, click the Policies tab.
          Step 13   Expand the BIOS Policy bar and choose usNIC in the BIOS Policy drop-down list.
          Step 14   Click Save Changes.

          Creating a usNIC using the Cisco UCS Manager CLI

          Before You Begin

          You must log in with admin privileges to perform this task.

          Procedure
             Command or ActionPurpose
            Step 1 UCS-A # scope service-profile server chassis-id / blade-id or rack_server-id  

            Enters the service profile for the specified chassis, blade or UCS managed rack server ID.

             
            Step 2 UCS-A /org/service-profile # show vnic   Displays the vnics that are available on the server. A usNIC vNIC is available by default when you upgrade to Cisco UCS Manager, release 2.2.  
            Step 3 UCS-A /org/service-profile # scope vnic vnic name   Enters the vNIC mode for the specified vNIC.  
            Step 4UCS-A /org/service-profile/vnic # set adapter-policy Linux   Specifies Linux and the adapter policy for the usNIC.  
            Step 5 UCS-A /org/service-profile/vnic # enter usnic-conn-policy-ref usnic connection policy reference name   Creates the usNIC connection policy reference for the vNIC with the specified name. The maximum size for the connection policy name is 16 characters.  
            Step 6 UCS-A /org/service-profile/vnic/usnic-conn-policy-ref* # commit-buffer   Commits the transaction to the system configuration.  
            Step 7 UCS-A /org/service-profile/vnic/usnic-conn-policy-ref # top   Enters the top-level mode.  
            Step 8 UCS-A # scope org   Enters the root organization mode.  
            Step 9 UCS-A /org # create usnic-conn-policy usnic connection policy name   Creates a usNIC connection policy with the specified name.  
            Step 10 UCS-A /org/usnic-conn-policy* # set usnic-count number of usnics  

            Specifies the number of Cisco usNICs to create. It is recommended that you enter 58 for this value.

             
            Step 11 UCS-A /org/usnic-conn-policy* # set adaptor-profile usNIC   Specifies the usNIC Ethernet adaptor profile for the usNIC connection policy. This usNIC adaptor profile is created by default when you upgrade from previous versions of Cisco UCS Manager to release 2.2.  
            Step 12 UCS-A /org/usnic-conn-policy* # commit-buffer   Commits the transaction to the system configuration.  

            This example shows how to create a Cisco usNIC and specify its properties:

            Server # scope org
            Server /org # create usnic-conn-policy usnic1
            Server /org/usnic-conn-policy* # set usnic-count 58
            Server /org/usnic-conn-policy* # set adaptor-profile usNIC
            Server /org/usnic-conn-policy* # commit-buffer
            Server /org/usnic-conn-policy # top
            
            
            Server # scope service-profile server 1/1
            Server /org/service-profile # show vnic
            
            vNIC:
            Name Fabric ID Dynamic MAC Addr Virtualization Preference
            ------------------ --------- ------------------ -------------------------
            eth0 A 00:25:B5:00:00:A1 NONE
            eth1 B 00:25:B5:00:00:A2 NONE
            eth2 A 00:25:B5:00:00:A3 NONE
            Server /org/service-profile # scope vnic eth0
            Server /org/service-profile/vnic # set adapter-policy Linux
            Server /org/service-profile/vnic # enter usnic-conn-policy-ref usnic1
            Server /org/service-profile/vnic/usnic-conn-policy-ref* # commit-buffer
            Server /org/service-profile/vnic/usnic-conn-policy-ref # exit 
            
            

            Modifying a usNIC using the Cisco UCS Manager CLI

            Before You Begin

            You must log in with admin privileges to perform this task.

            Procedure
               Command or ActionPurpose
              Step 1 UCS-A # scope service-profile server chassis-id / blade-id or rack_server-id  

              Enters the service profile for the specified chassis, blade or UCS managed rack server ID.

               
              Step 2 UCS-A /org/service-profile # show vnic   Displays the vnics that are available on the server. A usnic vnic is available by default when you upgrade to Cisco UCS Manager, release 2.2.  
              Step 3 UCS-A /org/service-profile # scope vnic vnic name   Enters the vnic mode for the specified vNIC.  
              Step 4 UCS-A /org/service-profile/vnic # enter usnic-conn-policy-ref usnic connection policy reference name   Specifies the usnic connection policy reference for the vNIC that you want to use.  
              Step 5 UCS-A /org/service-profile/vnic/usnic-conn-policy-ref* # commit-buffer   Commits the transaction to the system configuration.  

              This example shows how to modify Cisco usNIC properties:

              Server # scope service-profile server 1/1
              Server /org/service-profile # show vnic
              
              vNIC:
              Name Fabric ID Dynamic MAC Addr Virtualization Preference
              ------------------ --------- ------------------ -------------------------
              eth0 A 00:25:B5:00:00:A1 SRIOV USNIC
              eth1 B 00:25:B5:00:00:A2 NONE
              eth2 A 00:25:B5:00:00:A3 NONE
              Server /org/service-profile # scope vnic eth0
              Server /org/service-profile/vnic # enter usnic-conn-policy-ref usnic2
              Server /org/service-profile/vnic/usnic-conn-policy-ref* # commit-buffer
              Server /org/service-profile/vnic/usnic-conn-policy-ref # exit
              
              

              Deleting a usNIC using the Cisco UCS Manager CLI

              Before You Begin

              You must log in with admin privileges to perform this task.

              Procedure
                 Command or ActionPurpose
                Step 1 UCS-A # scope service-profile server chassis-id / blade-id or rack_server-id  

                Enters the service profile for the specified chassis, blade or UCS managed rack server ID.

                 
                Step 2 UCS-A /org/service-profile # show vnic   Displays the vNICs that are available on the server. A usNIC vNIC is available by default when you upgrade to Cisco UCS Manager, release 2.2.  
                Step 3 UCS-A /org/service-profile # scope vnic vnic name   Enters the vNIC mode for the specified vNIC.  
                Step 4 UCS-A /org/service-profile/vnic # show usnic-conn-policy-ref usnic connection policy reference name   Specifies the usNIC connection policy reference for the vNIC that you want to use.  
                Step 5 UCS-A /org/service-profile/vnic # delete usnic-conn-policy-ref usnic connection policy reference name   Deletes the specified usNIC connection policy reference.  
                Step 6 UCS-A /org/service-profile/vnic/usnic-conn-policy-ref* # commit-buffer   Commits the transaction to the system configuration.  

                This example shows how to modify Cisco usNIC properties:

                Server # scope service-profile server 1/1
                Server /org/service-profile # show vnic
                
                vNIC:
                Name Fabric ID Dynamic MAC Addr Virtualization Preference
                ------------------ --------- ------------------ -------------------------
                eth0 A 00:25:B5:00:00:A1 SRIOV USNIC
                eth1 B 00:25:B5:00:00:A2 NONE
                eth2 A 00:25:B5:00:00:A3 NONE
                Server /org/service-profile # scope vnic eth0
                Server /org/service-profile/vnic # show usnic-conn-policy-ref
                
                usNIC Connection Policy Reference:
                usNIC Connection Policy Name
                ----------------------------
                usnic2
                Server /org/service-profile/vnic # delete usnic-conn-policy-ref usnic2
                Server /org/service-profile/vnic* # commit-buffer
                Server /org/service-profile/vnic # exit 
                
                

                Installing Linux Drivers for Cisco usNIC

                The following section lists the content of the usNIC folder, specific for each supported Linux operating system distribution that is included in the UCS Drivers ISO bundle. Documentation about known issues and installation instructions are also included in the README file in the usNIC folder.


                Note


                To prevent the OS from swapping out the memory that is allocated to the Cisco usNIC applications, the installation software increases the locked memory system setting of the OS to Unlimited.


                • kmod-usnic_verbs-{version}.x86_64.rpm—Linux kernel verbs driver for the usNIC feature of the Cisco VIC SR-IOV Ethernet NIC.

                • libusnic_verbs-{version}.x86_64.rpm —User space library libibverbs plugin for usNIC.

                • openmpi-cisco-{version}.x86 _64.rpmCisco usNIC Open MPI—Open MPI with the Cisco usNIC BTL MPI transport.

                • usnic_tools-{version}.x86_64.rpm —Utility programs for usNIC.

                • usnic_installer.sh—Script for installing the Cisco usNIC packages listed in the section.

                • usnic_uninstaller.sh—Script for uninstalling the Cisco usNIC packages listed in the section.

                Before You Begin

                Make sure that you have configured the Cisco usNIC properties in Cisco UCS Manager. For more information about how to configure the properties, see Configuring Cisco usNIC in Cisco UCS Manager.

                You must also make sure that the host OS distribution on which you want to install Cisco usNIC has a supported version of the Cisco enic driver installed. The Cisco enic driver is the Linux kernel networking driver for the Cisco VIC SR-IOV Ethernet NIC.
                Procedure
                  Step 1   # ./usnic_installer.sh

                  Execute the installer script from the directory where the installation files are located for Cisco usNIC.

                  Note   

                  You require admin privileges to execute the script at the root (#) prompt.

                  Step 2   # chkconfig rdma on

                  Enables rdma and, once enabled, it will be started automatically after a system reboot.

                  Note   

                  You may need to perform this step on some Linux operating systems distributions, such as RHEL 6.4.

                  Step 3   # service rdma start

                  Verify that the rdma service is started. This service is required for the usnic_verbs kernel module.

                  Note   

                  You can use the above commands on systemcl if you have the latest versions of RHEL and SLES migrated to systemd.

                  Step 4   Reboot your server for the installation changes to take effect automatically.
                  Important:

                  If you do not want to reboot your server, you can manually load the kernel modules to ensure the system loads the correct version of the driver and enforce the new memory lock configurations. For more information about how to load the modules, see Manually Loading the Kernel Modules for Cisco usNIC.


                  Installing Linux Drivers for usNIC using the Source Tarball

                  The usnic_installer.sh, usnic_uninstaller.sh, and usnic_verbs_check scripts provided by Cisco supports only RPM installations. When you install one or more drivers using the tarball installations, the Cisco scripts cannot determine the system configuration and the installation might not be successful. It is recommended not to mix the tarball and RPM installations and to always have one version of the required drivers.

                  Manually Loading the Kernel Modules for Cisco usNIC

                  If you do not want to reboot your server, you can manually load the Cisco usNIC kernel modules by using the following steps.

                  Before You Begin

                  Ensure you delete all the existing versions of the driver before you load the latest version of the driver. This will help you configure the system successfully.

                  Procedure
                     Command or ActionPurpose
                    Step 1# rmmod enic
                     

                    Unloads the existing enic driver module.

                    Note   

                    Make sure that you are not logged into the OS using the network, for example, via SSH. Otherwise, your network connection might get permanently disconnected. Alternatively, you can log in to the server using the Cisco UCS Manager KVM to perform this step.

                     
                    Step 2# modprobe enic
                     

                    Loads the enic driver module.

                     
                    Step 3# modprobe usnic_verbs
                     

                    Loads the usnic_verbs driver module.

                     

                    Upgrading the Linux Drivers for Cisco usNIC

                    You can use the usnic_installer.sh to upgrade the drivers. This script will replace the existing version of the drivers with the latest version of the drivers.

                    Procedure
                      Step 1   # ./usnic_uninstaller.sh

                      Execute the uninstaller script from the bin folder in the directory where the Cisco usNIC installation files are located to uninstall the existing drivers on your system.

                      Step 2   # ./usnic_installer.sh

                      Execute the installer script from the directory where the installation files are located for Cisco usNIC.

                      Note   

                      You require admin privileges to execute the script at the root (#) prompt.

                      Step 3   # chkconfig rdma on

                      Enables rdma and, once enabled, it will be started automatically after a system reboot.

                      Step 4   # service rdma start

                      Verify that the rdma service is started. This service is required for the usnic_verbs kernel module.

                      Step 5   Reboot your server for the installation changes to take effect automatically.
                      Important:

                      If you do not want to reboot your server, you can manually load the kernel modules to ensure the system loads the correct version of the driver and enforce the new memory lock configurations. For more information about how to load the modules, see Manually Loading the Kernel Modules for Cisco usNIC.


                      Uninstalling Linux Drivers for Cisco usNIC

                      Procedure
                        Step 1   # ./usnic_uninstaller.sh

                        Execute the uninstaller script from the bin folder in the directory where the Cisco usNIC installation files are located.

                        Step 2   Reboot your Cisco UCS server.

                        Verifying the Cisco usNIC Installation

                        After you install the required Linux drivers for Cisco usNIC, perform the following procedure at the Linux prompt to make sure that the installation completed successfully.

                        Note


                        The examples shown below are configurations verified on Cisco UCS Manager Release 2.2(3) and Linux operating system distribution RHEL 6.4.


                        Procedure
                          Step 1   Search and verify if the usnic_verbs kernel module was loaded during the OS driver installation.
                          Note   

                          You should use the # prompt for install or uninstall commands and you should use the $ prompt to display the configurations.

                          $ lsmod | grep usnic_verbs

                          The following details are displayed when you enter the lsmod | grep usnic_verbs command. The kernel modules listed on your console may differ based on the modules that you have currently loaded in your OS.

                          usnic_verbs            73762  2 
                          ib_core                74355  11 ib_ipoib,rdma_ucm,ib_ucm,ib_uverbs,ib_umad,rdma_cm,ib_cm,iw_cm,ib_sa,ib_mad,usnic_verbs
                          enic                   73723  1 usnic_verbs
                          
                          
                          Step 2   View the configuration of Cisco usNIC-enabled NICs.
                          $ ibv_devinfo
                          The following section is a brief example of the results that are displayed when you execute the ibv_devinfo command. The results may differ based on your current installations. When the results are displayed on your console, make sure that the state for each of the listed ports are shown as PORT_ACTIVE. The following example shows two ports (usnic_1 and usnic_0) that are configured on a Cisco UCS VIC adapter. If you configured only one usNIC-enabled vNIC, you will see a listing for only usnic_0.
                          Note   

                          The ibv_devinfo command displays the value for the transport parameter as iWARP. However, Cisco usNIC does not utilize the iWARP transport and uses the UDP-based protocol for transport.

                          hca_id: usnic_1
                                  transport:                      iWARP (1)
                                  fw_ver:                         4.0(1b)
                                  node_guid:                      0200:00ff:fe00:0000
                                  sys_image_guid:                 0225:b5ff:fec1:b520
                                  vendor_id:                      0x1137
                                  vendor_part_id:                 207
                                  hw_ver:                         0x4F
                                  board_id:                       79
                                  phys_port_cnt:                  1
                                          port:   1
                                                  state:                  PORT_ACTIVE (4)
                                                  max_mtu:                4096 (5)
                                                  active_mtu:             4096 (5)
                                                  sm_lid:                 0
                                                  port_lid:               0
                                                  port_lmc:               0x01
                                                  link_layer:             Ethernet
                          
                          hca_id: usnic_0
                                  transport:                      iWARP (1)
                                  fw_ver:                         4.0(1b)
                                  node_guid:                      0200:00ff:fe00:0000
                                  sys_image_guid:                 0225:b5ff:fec1:b510
                                  vendor_id:                      0x1137
                                  vendor_part_id:                 207
                                  hw_ver:                         0x4F
                                  board_id:                       79
                                  phys_port_cnt:                  1
                                          port:   1
                                                  state:                  PORT_ACTIVE (4)
                                                  max_mtu:                4096 (5)
                                                  active_mtu:             4096 (5)
                                                  sm_lid:                 0
                                                  port_lid:               0
                                                  port_lmc:               0x01
                                                  link_layer:             Ethernet
                          
                              
                          
                          Step 3   Run the usnic_verbs_check script to view the installed RPMs and their versions.
                          $ /opt/cisco/usnic/bin/usnic_verbs_check
                          

                          If any errors occurred during the OS driver installation, warnings are generated.

                          If the usnic_verbs module failed to load, the following brief example shows the warnings that are generated:

                          $ /opt/cisco/usnic/bin/usnic_verbs_check 
                          enic RPM version 2.1.1.75-rhel6u4.el6 installed
                          usnic_verbs RPM version 1.0.4.241.rhel6u4-1 installed
                          WARNING: usnic_verbs module not loaded
                          libusnic_verbs RPM version 1.1.0.237.rhel6u4-1 installed
                          Using /opt/cisco/openmpi/bin/ompi_info to check Open MPI info...
                          Open MPI version 1.8.2cisco1.0.0.245.rhel6u4 installed
                          WARNING: No usnic verbs devices found
                          WARNING: No usnic verbs devices found
                          3 warnings
                          
                          
                          Step 4   Verify that the Cisco usNIC network packets are being transmitted correctly between the client and server hosts.
                          1. Determine the name of the Ethernet interface associated with the Cisco usNIC on the server host.
                            <server>$ /opt/cisco/usnic/bin/usnic_status
                            
                            usnic_0: 0000:07:0.0, eth1, aa:ff:bb:01:01:10, 32 VFs
                            Per VF: 2 WQ, 2 RQ, 4 CQ, 6 INT
                            
                            In use:
                            0 VFs, 0 QPs, 0 CQs
                            
                            
                            usnic_1: 0000:08:0.0, eth2, aa:ff:bb:01:01:20, 32 VFs
                            Per VF: 2 WQ, 2 RQ, 4 CQ, 6 INT
                            
                            In use:
                            0 VFs, 0 QPs, 0 CQs
                          2. Determine the IP address for the Ethernet interface.
                            <server>$ ip addr show dev eth4 | grep "inet[^6]"
                                inet 10.1.0.1/16 brd 10.1.255.255 scope global eth4
                          3. Run the usnic_udp_pingpong program on the server host.
                            <server>$ usnic_udp_pingpong -s 200 -d usnic_0 

                            For more information about the command line options used with the usnic_udp_pingpong program, see the ibv_ud_pingpong(1) man page.

                          4. Execute the usnic_udp_pingpong program on the client host by using the IP address that corresponds to the Cisco usNIC on the server host.
                            <client>$ usnic_udp_pingpong -s 200 -d usnic_0 10.43.10.1
                          The following example shows the results that are displayed when you run the usnic_udp_pingpong program.
                          Server-side:
                          <server>$ ./usnic_udp_pingpong -s 200 -d usnic_0
                            local address:  IP: 10.43.10.1, QPN 0x0086ba
                            remote address: IP: 10.43.10.2, QPN 0x00a9fe
                          400000 bytes in 0.01 seconds = 302.92 Mbit/sec
                          1000 iters in 0.01 seconds = 5.28 usec/half-round-trip
                          
                          
                          Client-side:
                          <client># ./usnic_udp_pingpong 10.43.10.1 -s 200 -d usnic_0
                            local address:  IP: 10.43.10.2, QPN 0x00a9fe
                            remote address: IP: 10.43.10.1, QPN 0x0086ba
                          400000 bytes in 0.01 seconds = 313.20 Mbit/sec
                          1000 iters in 0.01 seconds = 5.11 usec/half-round-trip
                          
                          
                          Step 5   Download, compile, and execute the ring_c test program to validate that the MPI traffic is correctly transmitted between the client and server hosts.

                          You can obtain the ring_c test program from this link: https:/​/​raw.githubusercontent.com/​open-mpi/​ompi-release/​v1.8/​examples/​ring_​c.c .

                          The following example shows how to use the wget utility to obtain, compile, and execute the ring_c. Alternatively, you can use other methods of obtaining and running the test program.

                          $ wget http://svn.open-mpi.org/svn/ompi/branches/v1.8/examples/ring_c.c
                           --2013-08-06 15:27:33--  http://svn.open-mpi.org/svn/ompi/branches/v1.8/examples/ring_c.c
                           Resolving svn.open-mpi.org... 129.79.13.24 Connecting to 
                           svn.open-mpi.org|129.79.13.24|:80... connected.
                           HTTP request sent, awaiting response... 200 OK
                           Length: 2418 (2.4K) [text/plain]
                           Saving to: “ring_c.c”
                           
                           100%[======================================>] 2,418       --.-K/s   in 0s      
                           
                           Last-modified header invalid -- time-stamp ignored.
                           2013-08-06 15:27:33 (10.7 MB/s) - “ring_c.c” saved [2418/2418]
                           
                           $ mpicc ring_c.c -o ring_c
                           [no output]
                           
                           $ mpiexec --host host1,host2 -n 4 ./ring_c 
                           Process 0 sending 10 to 1, tag 201 (4 processes in ring) 
                           Process 0 sent to 1 
                           Process 0 decremented value: 9 
                           Process 0 decremented value: 8 
                           Process 0 decremented value: 7 
                           Process 0 decremented value: 6 
                           Process 0 decremented value: 5 
                           Process 0 decremented value: 4 
                           Process 0 decremented value: 3 
                           Process 0 decremented value: 2 
                           Process 0 decremented value: 1 
                           Process 0 decremented value: 0 
                           Process 0 exiting 
                           Process 2 exiting 
                           Process 1 exiting 
                           Process 3 exiting ...  
                           
                          
                          

                          If the usnic_udp_pingpong program and the ring_c program executed successfully, you should now be able to run MPI applications over Cisco usNIC.