Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Install Packet Flow Accelerator Diagnostics Software

Packet Flow Accelerator Diagnostics Software Overview

You can use Packet Flow Accelerator Diagnostics software to test the FPGA module in the QFX-PFA-4Q module installed on the QFX5100-24Q-AA switch as well as the data paths between the FPGA module and the QFX5100-24Q-AA switch. The Packet Flow Accelerator Diagnostics software contains standard diagnostics, orchestration diagnostics, and Precision Time Protocol (PTP) and synchronization diagnostics. In addition to the Packet Flow Accelerator Diagnostics software tests, there are utilities included in the Packet Flow Accelerator Diagnostics software that you can use to further diagnose issues on the QFX-PFA-4Q module. For information on how to install the QFX-PFA-4Q module, see Installing an Expansion Module in a QFX5100 Device.

To run the orchestration diagnostics, PTP and synchronization diagnostics, and utilities contained in the Packet Flow Accelerator Diagnostics software, you need to have a Junos OS Release 14.1X53-D27 software or later with enhanced automation installed on your QFX5100 switch. For information on how to download and install Junos OS software, see Installing Software Packages on QFX Series Devices.

The Packet Flow Accelerator Diagnostics software runs in a guest VM on the switch and requires that you configure guest VM options in the Junos OS CLI.

Verify That the QFX-PFA-4Q Expansion Module Is Installed

Before you install the Packet Flow Accelerator Diagnostics software, verify that the QFX-PFA-4Q module is installed.

From the CLI prompt, issue the show chassis hardware command.

From the CLI output, you can see that the four QSFP+ interfaces (4x40G QSFP+) contained in the QFX-PFA-4Q module. are installed.

Download the Packet Flow Diagnostics Software

Note:

To access the download site, you must have a service contract with Juniper Networks and an access account. If you need help obtaining an account, complete the registration form at the Juniper Networks website https://www.juniper.net/registration/Register.jsp .

To download the Packet Flow Diagnostics software package from the Juniper Networks Support website, go to https://www.juniper.net/support/ :

  1. Using a Web browser, navigate to https://www.juniper.net/support .
  2. Click Download Software.
  3. In the Switching box, click Junos OS Platforms.
  4. In the QFX Series section, click the name of the platform for which you want to download software.
  5. Click the Software tab and select the release number from the Release drop-down list.
  6. In the Install Package section on the Software tab, select the Install Package for the release.

    A login screen appears.

  7. Enter your name and password and press Enter.
  8. Read the End User License Agreement, click the I agree radio button, and then click Proceed.
  9. Save the pfadiag_vm-rXXXXX.img.gz file on your computer.
  10. Open or save the Packet Flow Diagnostics software package either to the local system in the var/tmp directory or to a remote location. If you are saving the installation package to a remote system, make sure that you can access it using HTTP, TFTP, FTP, or scp.

Copy the Packet Flow Diagnostics Software Package to the Switch

To copy the packet flow diagnostics software package to the switch:

Copy the packet flow diagnostics package to the switch using any file transfer protocol:

For example:

Install the Packet Flow Diagnostics Software on the Switch

To install the packet flow diagnostics software package on the switch:

  1. Install the Packet Flow Diagnostics software on the switch.

    This might take a few minutes.

    If the Packet Flow Diagnostics software resides locally on the switch, issue the following command:

  2. Issue the show version command to verify that the installation was successful.

    The CLI output shows that the Packet Flow Accelerator Diagnostics software was installed.

Configure the Guest VM Options to Launch the Guest VM on the Host

To configure the guest VM options:

  1. Configure the following options for guest VM support in the Junos OS CLI at the [edit] hierarchy.
    • Compute cluster name

    • Compute node name

    • VM instance name

    • Dedicated management interface for guest VM

    • Third-party package name

    • Internal IP address of the guest VM

  2. Configure the name of the compute cluster and compute node.

    The name of the compute cluster must be default-cluster, and the name of the name of the compute node must be default-node; otherwise, launching the guest VM fails.

  3. Configure the name of the VM instance and the name of the third party application.
    Note:

    The package names in the show app-engine virtual-machine-package command and the show version command should match.

  4. Associate the VM instance with the configured compute cluster and compute node.
    Note:

    The name of the compute cluster must be default-cluster, and the name of the compute node must be default-node; otherwise, launching the guest VM fails.

  5. Configure the local management IP address.

    This IP address is used for the internal bridging interface. The host uses this IP address to check the availability of the guest VM.

    Note:

    Do not use 192.168.1.1 and 192.168.1.2 as IP addresses because they are used by the Host-OS and Junos OS respectively.

  6. Configure the management interface for the guest VM.

    This management interface is separate from the one used for Junos OS.

    Note:

    The management interface name must be either em0 or em1. The configuration will fail if you do not configure a management interface and then commit the configuration.

    The new management interface is provisioned for the guest VM.

  7. Commit the configuration.

    Here are the results of the configuration:

Verify That the Guest VM is Working

To verify that the guest VM is working:

Issue the following show commands to verify that everything is working correctly:
  • root> show app-engine status

    The status should be Online.

  • root> show app-engine virtual-machine instance

    The VM status should be active.

  • root> show app-engine virtual-machine package

Access the Guest VM

To access the guest VM:

  1. Log into the guest VM.
    • Specify the guest VM name using the request app-engine virtual-machine-shell guest-VM-name command. The maximum length for the guest VM name is 255 characters. Make sure you are logged in as root when you enter this command.

    • Enter a valid username and password combination for the guest VM.

      Note:

      The first time you log in, the username is root. There is no password. After you log in, you will be prompted to create a password.

      For example:

  2. Issue the ifconfig -a command to see the names of the management interface that is used to access the guest VM from outside of the network, name of the management interface that is used for internal use, and the NIC ports used in the diagnostics VM.

    In this example, the heartbeat address is the IP address that is used for internal use , the management interface is used for external communications, and the xe-0/0/40 and xe-0/0/41 interfaces are the NIC ports used in the diagnostics VM. The heartbeat is configured by default. The IP address of the heartbeat is the same as the IP address you configured for Junos OS.

    You can associate one of the interfaces to the guest VM by issuing the set services app-engine virtual-machines instance name management-interface interface-name. command. Use the same IP address as the one you configured using the set services app-engine virtual-machines instance test local-management family inet address 192.168.1.10. The MAC addresses associated with these interfaces are used for internal bridging.

Verify That the FPGA Module Is Working

You can use the following utilities to verify that the FPGA module on the QFX-PFA-4Q module is working.

To verify that the FPGA module is working:

  1. Issue the lspci |grep "RAM memory" command at the guest VM login prompt.

    The output shows that Juniper Networks Device 0078 is working.

  2. Issue the lspci |grep Co-processor command at the guest VM login prompt:

    The output shows that Maxeler Technologies Ltd. Device 0006 is working.

  3. Issue the maxtop command at the guest VM login prompt:
    Note:

    If there are errors in the command output, relaunch the guest VM.

Validate the Connections Between QFX5100-24Q-AA Switch Network Ports and QFX-PFA-4Q Module Ports

You can use the ikon_eth_util –all-pass-through utility to validate the connections between the QFX5100-24Q-AA switch network ports and the QFX-PFA-4Q module ports.

In this example, the ikon_eth_util --all-pass-through utility will validate the following connections between the F-ports, A-ports, B-ports, and C-ports. Table 1 provides the ports that are validated in this example.

Table 1: Validating Ports

F-Ports

A-Ports

B-Ports

C-Ports

xe-0/0/10:2

This interface is one of the 10-Gigabit Ethernet ports on the QFX5100-24Q-AA switch. You can manage these ports through the Junos OS.

xe-0/0/32

This interface connects the PFE of the QFX5100-24Q-AA switch to the B-ports on the FPGA module on the QFX-PFA-4Q module.

JDFE_XE32_10G

This interface is an Internal 10-Gigabit Ethernet port on the FPGA module on the QFX-PFA-4Q module and connects to the A-ports on the PFE of the QFX5100-24Q-AA switch.

JDFE_QSFP0_10G_PORT0 [External Port 0-0]

This interface is one of the front-facing 40-Gigabit Ethernet ports on the QFX-PFA-4Q module and connects to the guest VM running on the QFX5100-24Q-AA switch and the F-ports on the QFX5100-24Q-AA switch.

To validate the connections between the QFX5100-24Q-AA switch network ports and the QFX-PFA-4Q module ports:

  1. Configure a VLAN and VLAN ID:
  2. Associate the F-port and A-port in this VLAN so that the FPGA and PFE can communicate:
  3. Commit the configuration:
  4. Verify that the VLAN has been created.
  5. Issue the ikon_eth_util --all-pass-through command at the guest VM login prompt:
  6. Send traffic to xe-0/0/10:2 on the QFX5100-24Q-AA switch and receive traffic on the front panel port 0-0 on the QFX-PFA-4Q module.
  7. Send traffic to the front panel port 0-0 on the QFX-PFA-4Q module and receive traffic on xe-0/0/10:2 on the QFX5100-24Q-AA switch.
  8. Verify the statistics for the xe-0/0/10:2 and xe-0/0/32 interfaces by issuing the show interfaces xe-0/0/10:2 extensive and show interfaces xe-0/0/32 extensive commands.
  9. Verify the statistics for the JDFE_XE32_10G and JDFE_QSFP0_10G_PORT0 interfaces by issuing the maxnet link commands at the guest VM prompt for the Packet Flow Accelerator Diagnostics software.

    [root@ikondiag ~]# maxnet link show JDFE_XE32_10G

    [root@ikondiag ~]# maxnet link show JDFE_QSFP0_10G_PORT0

Uninstall the Guest VM

To remove the guest VM:

  1. Delete the configuration statements and uninstall the Packet Flow Accelerator Diagnostics software package.

    For example, to remove the app-engine statement:

  2. Commit the configuration.
  3. (Optional) Issue the show version command to learn the name of the Packet Flow Accelerator Diagnostics software package.
  4. Issue the request system software delete virtual-machine-package <package-name> command to uninstall the Packet Flow Accelerator Diagnostics software.