OptiView XG

Performance Test Remote

Basic
Troubleshooting
Tutorial

11/2013
2013 Fluke Corporation.
All product names are trademarks of their respective companies.

Basic Troubleshooting

Table of Contents
About This Document ............................................................................................................................................................. 2
Document Conventions ...................................................................................................................................................... 2
Performance Test Purpose...................................................................................................................................................... 2
Performance Test Issues and Solutions .................................................................................................................................. 2
1.

Connectivity issues .................................................................................................................................................. 2

2.

Utilization Graph Issues .......................................................................................................................................... 3

3.

Device Stays in Ready Status and a Test does not Run ........................................................................................... 3

4.

Timeout Period Settings Do Not Work.................................................................................................................... 3

5.

Test Does not Run or Fails....................................................................................................................................... 3

6.

Potential Error Messages ........................................................................................................................................ 4

Table of Figures
Figure 1: Duplex mismatch Error...................................................................................................................................... 5
Figure 2: Speed mismatch Error ....................................................................................................................................... 5
Figure 3: No physical link Error ........................................................................................................................................ 5
Figure 4: Stopped by user Error ....................................................................................................................................... 5
Figure 5: Supplicant timeout Error ................................................................................................................................... 5
Figure 6: Supplicant invalid config Error ......................................................................................................................... 5
Figure 7: No IPv4 Address Error ....................................................................................................................................... 5
Figure 8: Duplicate IP address Error ................................................................................................................................. 5
Figure 9: DHCP Failed Error .............................................................................................................................................. 5

Basic Troubleshooting

About This Document

This document describes basic issues you may encounter while working with an OptiView XG Performance Test
Remote and suggests possible solutions. If you require additional assistance consider checking the product
Knowledgebase on www.flukenetworks.com or contacting support (support@flukenetworks.com).

Document Conventions

For simplicity, the OptiView XG Performance Test Remote is referred to as a PTR and the OptiView XG
Network Analysis Tablet is referred to as an XG.
References to Graphical User Interface element labels are in bold text, such as Ready status.
Notes describe useful information and are shown in italics.

Performance Test Purpose

The Performance Test is intended to test a service provider's Service Level Agreement (SLA), or to verify an
enterprise network's data rate capability, at up to a full line-rate of 10 Gbps.
The transmit/receive line utilization can be viewed on the PTR, but intermediate and overall results are only
displayed on the XG.
For more Performance Test information, please visit the following website:
http://www.flukenetworks.com/content/datasheet-optiview-xg-performance-testing

Performance Test Issues and Solutions

1. Connectivity issues
Issue 1: The PTR does not link.
Solution 1: There may be several reasons why the device does not link:

Ensure that you selected the PTRs onscreen START button or the external TEST button (on front
of device).
You may be using a Cisco Catalyst 6500 series chassis with a 1 Gb fiber GBIC or a multiport
GBIC blade with the auto negotiate option disabled. If this is the case, set the PTR speed to
Auto or 1 Gb. Try Auto first, and if it does not link then try the 1 Gb.
To specify a PTR speed go to the PTR home page and select Setup tab>Wired>Speed> Auto
or 1 Gb.

Issue 2: The PTR device seems to be stuck on Linking and never enters Ready status.
Solution 2: There are several possibilities for this behavior:

The PTR is not connected to the network.

A DHCP server is not present, is not operating correctly, or is unreachable.
2

Basic Troubleshooting

The PTR may have a bad cable/bad fiber connection from device to network. Try replacing the
cable/fiber that is connected to the device.
You are not running the test using Auto or the correct speed.
The link partner is transmitting in half duplex.

Note: Copper SFPs are not supported. Use RJ-45 for copper.
In each case the Linking status will eventually timeout (60 seconds) with a Link Error and display a general
description of the cause of failure. The error description will be displayed below the Utilization Graph.
2. Utilization Graph Issues
Issue 1: Utilization graph shows minor activity when the status is Ready and a test has not been initiated
from the XG.
Solution 1: This is normal behavior. The Utilization graph may show minor activity when the device is in
Ready status and connected to a live network.
Issue 2: One graph is shown even though the device should handle up to four streams.
Solution 2: The PTR does handle up to four services/streams; however, all network traffic is represented in a
single consolidated graph.
3. Device Stays in Ready Status and a Test does not Run
Issue: The PTR is in Ready status and does not run a test.
Solution: Typically this is due to the XG not communicating properly with the PTR. This condition can occur
when an incorrectly configured test is initiated from an XG. Review the test configuration on the XG. Look for
things such as a mismatched UDP port number setting; it should be the same on the XG as on the PTR.
Ensure that there is no firewall in the path that might block UDP traffic.
4. Timeout Period Settings Do Not Work
Issue: Timeout Period Settings do not take effect for power savings.
Solution: The Timeout Period settings only apply when the PTR is running on battery power.
5. Test Does not Run or Fails
Issue 1: Test does not run.
Solution 1: Ensure that you selected the onscreen START button or pressed the external TEST button (on front
of the PTR device).
The PTR must first go through two sequential statuses (Linking and Ready) prior to entering the third and
final Running status.
Issue 2: Test fails after it starts running.
3

Basic Troubleshooting
Solution 2: There could be several reasons why a test may fail.

Check the error description on the XG side.

Check the PTR test speed and make sure that the connection to the network is capable of the selected
speed.
Ensure that the selected test speeds are able to run on the PTR and on the XG. For example, if you
intend to run a 1G Performance test, the PTR or the XG cannot be linked at a lesser speed.
Check the test configurations on the XG and look for possible inconsistencies in UDP port numbers.

6. Potential Error Messages

Issue 1: The PTR shows a Duplex mismatch error (Figure 1).
Solution 1: The PTR must be connected to a device (switch or XG) supporting Full duplex.
Issue 2: The PTR shows a Speed Mismatch error (Figure 2).
Solution 2: The selected speed may not be supported by the switch port or by a test configuration on the PTR
or XG.
Issue 3: The PTR shows a No physical link error message (Figure 3).
Solution 3: You may not be connected to the network. If you are connected to the network there may be an
issue with the cable or Fiber.
Issue 4: The PTR shows a Stopped by User message (Figure 4).
Solution 4: This message can be either a state or an error.
It is a state when the PTRs onscreen STOP button or the external TEST button (on front of the PTR) has been
selected while the PTR was in Linking, Ready, or Running status. To restart a test that was stopped by a user,
select the onscreen START button or the external TEST button (on front of device).
It is an error if a screen capture is taken while the device is in the Linking, Ready, or Running status. Once
the screen capture is saved the test will resume and you will be returned to the pre-screen capture location.
Issue 5: The PTR shows a Supplicant timeout error (Figure 5).
Solution 5: Error may appear after configuring the 802.1X security settings on the PTR. The error may be the
result of a/an:

Missing or incorrect username/password than what is configured for the RADIUS server.
Incorrect EAP type than what is configured for the RADIUS server.
Missing or incorrect certificate (applies to TLS EAP types only).
Unreachable RADIUS server.

Basic Troubleshooting
Issue 6: The PTR shows a Supplicant invalid config error (Figure 6).
Solution 6: This error may appear after configuring the 802.1X security settings on the PTR. The error may be
the result of an unspecified username or certificate (only for TLS based EAP configuration). Or, there may be an
instance of an empty username or an empty/unloaded certificate (applies only to TLS based EAP configuration).
Issue 7: The PTR shows a DHCP failed error (Figure 7).
Solution 7: You configured the PTRs IP address as DHCP and a DHCP server is not present, or is unreachable.
To check your PTRs IP address configuration, go to Home screen>SETUP tab>WIRED>Address.
Issue 8: The PTR shows a Duplicate IP address error (Figure 8).
Solution 8: You may have picked a static address that is already in use, or another device on the network uses
a static IP which matches the DHCP IP you have been offered by the DHCP server.
Issue 9: The PTR shows a No IPv4 Address error (Figure 9).
Solution 9: You will see this message if you set the PTRs IP address to static and did not provide an actual IP
address.

Figure 1: Duplex mismatch Error

Figure 2: Speed mismatch Error

Basic Troubleshooting

Figure 3: No physical link Error

Figure 4: Stopped by user Error

Figure 5: Supplicant timeout Error

Figure 6: Supplicant invalid config Error

Basic Troubleshooting

Figure 7: DHCP Failed Error

Figure 8: Duplicate IP address Error

Figure 9: No IPv4 Address Error