Fusion User Guide 4.1
Fusion User Guide 4.1
Release 4.1
December 2018
Fusion User Guide
Release 4.1
December 2018
Viavi Solutions
1-844-GO-VIAVI
www.viavisolutions.com
Notice
Every effort was made to ensure that the information in this manual was accurate at the
time of printing. However, information is subject to change without notice, and Viavi
reserves the right to provide an addendum to this manual with information not available at
the time that this manual was created.
Copyright/Trademarks
© Copyright 2018 Viavi Solutions Inc. All rights reserved. No part of this guide may be
reproduced or transmitted, electronically or otherwise, without written permission of the
publisher. Viavi Solutions and the Viavi logo are trademarks of ViaviSolutions Inc. (“Viavi”).
All other trademarks and registered trademarks are the property of their respective
owners.
Copyright release
Ordering information
This guide is a product of Viavi's Technical Publications Department, issued as part of the
Fusion. The catalog number for a published guide is Catalog Number - printed. The catalog
number for an electronic guide on USB is Catalog Number - electronic.
Specifications, terms, and conditions are subject to change without notice. The provision
of hardware, services, and/or software are subject to Viavi’s standard terms and condi-
tions, available at www.viavisolutions.com/en/terms-and-conditions.
Fusion includes third party software licensed under the terms of separate open source soft-
ware licenses. By using this software you agree to comply with the terms and conditions
of the applicable open source software licenses. Software originated by Viavi is not
subject to third party licenses. Terms of the Viavi Software License different from appli-
cable third party licenses are offered by Viavi alone.
Chapter 1 Introduction 1
About Fusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
This prefix explains how to use this manual. Topics discussed include the following:
• “Purpose and scope” on page ix
• “Assumptions” on page ix
• “Related information” on page x
• “Conventions” on page xi
• “Technical assistance” on page xii
Assumptions
This guide is intended for novice, intermediate, and experienced users who want to use
the Fusion effectively and efficiently. We are assuming that you have basic computer and
mouse/track ball experience and are familiar with basic telecommunication concepts and
terminology.
Related information
This is the getting started manual for the Fusion. It provides instructions for testing Y.1564,
Two-Way Active Measurement Protocol (TWAMP) Initiator, and UDP. Read this manual
carefully before attempting to configure and run the tests.
Document History
This table provides a revision history for this document.
Conventions
This guide uses typographical and symbols conventions as described in the following
tables.
Item(s) Example(s)
Buttons, keys, or switches that you Press the On button.
press or flip on a physical device. – Press the Enter key.
Buttons, links, menus, menu options, Click Start.
tabs, or fields on a PC-based or Web- – Click File > Properties.
based user interface that you click, – Click the Properties tab.
select, or type information into.
– Type the name of the probe in the Probe Name field.
Directory names, file names, and code $NANGT_DATA_DIR/results (directory)
and output messages that appear in a – test_products/users/defaultUser.xml (file
command line interface or in some name)
graphical user interfaces (GUIs). – All results okay. (output message)
Text you must type exactly as shown – Restart the applications on the server using the following
into a command line interface, text file, command:
or a GUI text field. $BASEDIR/startup/npiu_init restart
Type: a:\set.exe in the dialog box.
References to guides, books, and Refer to Newton’s Telecom Dictionary.
other publications appear in this type-
face.
Command line option separators. platform [a|b|e]
Optional arguments (text variables in login [platform name]
code).
Required arguments (text variables in <password>
code).
NOTE
This symbol indicates a note that includes important supplemental information or tips related
to the main text.
CAUTION
Applies to software actions. Indicates a situation that could possibly lead to loss of data or a
disruption of software operation if indicated precautions are not taken.
Technical assistance
If you require technical assistance, call 1-844-GO-VIAVI / 1.844.468.4284.
Chapter 1 Introduction
About Fusion
The Viavi Solutions™ Fusion is powered by Network Integrated Test, Real-time analytics
and Optimization ( NITRO) Virtual Newtwork (vNet) and provides operators and enterprise
users with a set of virtual and legacy tools, implementing repeatable, standards based test
methodologies to monitor and ensure network performance and verify Service Level
Agreements (SLA) in virtual and legacy networks.
Software Defined Networks (SDN) and Network Function Virtualization (NFV) is a software
based solution that is built on a standard x86 compute platforms and uses Virtual Network
Functions (VNF) to implement the desired network element. Fusion is dynamic, making the
core networking functions virtual. This technology also allows for proactive monitoring and
real-time intelligence and analytics.
Operators can add virtual test and performance monitoring probes into their network wher-
ever required, immediately with Viavi’s Fusion and the click of a mouse. The large installed
legacy network is still supported by integrating all of Viavi’s legacy test sets into this solu-
tion.
Virtual probes running on x86 server or compute platforms are the foundation of the solu-
tion by providing test functionality for network Layers 2-4. The network performance quality
can be measured as a neutral third party using Viavi’s industry-acknowledged Y.1564
SamComplete and the RFC6349 UDP technology, Virtual agents can be added for Perfor-
mance Monitoring (PM) when running a TWAMP.
This chapter describes the functionality of the instrument. Topics discussed in this chapter
are as follows:
• “Logging into Fusion” on page 3
• “Fusion Settings” on page 4
• “Choosing Test Point Details” on page 11
• “Customizing the Reports” on page 15
• “Running and Stopping a Test” on page 16
• “Marking and Deleting Tests” on page 18
• “Viewing the Test List” on page 18
• “Completed Test Options” on page 20
If you are using the internal BUILT-IN mode of authentication, do the following:
1 Open a Web browser and enter: https://<IP address or FQDN>:9443. The
Fusion login window appears.
2 Enter a valid user name and password (the defaults are admin and eaxuser).
3 Click LOGIN.
The home screen appears.
Figure 1 Fusion Home Screen
Fusion Settings
NOTE
You must have administrative privileges to make any changes to the settings.
To access the Fusion settings, select this icon in the upper right corner.
Figure 2 Settings
Devices
This shows all of the devices that are registered with the controller. In order for the devices
to register with the controller, the license for the device must be installed. The devices that
Fusion recognizes are vTA, vPMA, vPMA v2, QT600-10, and T-BERD/MTS. There are
nine different T-BERD/MTS devices that Fusion supports. These are:
• SC4800 • MTS-5882
• SC4800P • MAP-2100
• TB-5800v2 • TB-5800-100G
• MTS-5800v2 • MTS-5800-100G
• TB-5882
Go to “Choosing Test Point Details” on page 11 for more information on Show Specs.
With administrative privileges, you can add a new test, rename the device, or delete the
device. Non-admin users do not have this ability and the commands do not show in their
view.
NOTE
• If someone changes your device name after you run your test, the TEST
LIST still shows the previous agent name in the Test Point column for all
tests that were run before the device name change. For any rerun of those
tests using the Rerun function for the agent, you will need to know the
previous agent name to locate your tests. Tests that were created after the
device rename will show the new device name in the Test Point column of
the Test List.
• If someone changes the port name of your QT600-10 after you run your
test, the TEST LIST still shows the previous port name in the Test Point
column for all tests that were run before the hardware port name change.
For any rerun of those tests using the Rerun function for the QT600-10, you
will need to know the name of the previous device agent to locate your test.
Tests that were created after the port rename will show the new port name
in the Test Point column of the Test List. The ports are configured in the QT-
600-10 Gigabit Ethernet Probe Installation Guide or the NetComplete Ether-
ASSURE Test & Turn-up Solution User Guide.
Services
Services shows the IP addresses and ports used for test execution.
• Controller - Has the IP address the UI will use to interact with the Controller. The UI
and Controller are required to be installed on the same server. If that server only has
one Ethernet interface then its IP address will be used automatically. Otherwise, an
IP address must be specified.
• Collector - The IP address the UI will give to the agents when the tests are started.
The agent will send its test results to this IP address so it must be reachable from all
agents. The UI also uses this to retrieve test results. The UI and Collector are
required to be installed on the same server. If that server only has one Ethernet inter-
face then its IP address will be used automatically. Otherwise, an IP address must be
specified.
• Inventory - Has the IP address the UI uses to retrieve the list of agents. The UI and
Inventory service are required to be installed on the same server. If that server only
has one Ethernet interface then its IP address will be used automatically. Otherwise,
an IP address must be specified.
• Authentication Management - The IP address the UI uses when taking the user to
the Single Sign On page or User Management page. The UI and Single Sign On
service are required to be installed on the same server. If that server only has one
Ethernet interface then its IP address will be used automatically. Otherwise, an IP
address must be specified.
• Public Access - The IP address used in the Client URL that is displayed in the test
configuration for Client to Agent TrueSpeed and UDP tests. This IP address should
be entered manually and needs to be the IP address that the client will use to initiate
contact with Fusion. If a separate instance of the web server has been configured
using the steps in section “NGINX Installation on a Remote Public Machine to
Connect to the Fusion Controller” in the Fusion Installation and Administration Guide,
the public IP address of that remote server should be entered.
• Saved Test Datastore - The location of the of where the saved tests are stored.
Licensing
Licensing is where the licenses are installed. Only admin users can upload licenses and
see the view showing the Version, Locking Code, and Upload License File. All user
types can see the installed licenses (Installed License). See “Obtaining a Fusion or
Options License” in Chapter 5 of the Fusion Installation and Administrative Guide for the
instructions on how to obtain and upload a license.
Reports
Reports allows admin users to upload a company logo, image files, and input messages
to display in the header and footer of the reports. Non-admin users can only see the image
and message in their view.
Users
Admin users manage all the user accounts and privileges. Users - Users with admin rights
will see a button labeled 'Manage Users'. Selecting this will open a new tab that contains
the User Management application. Non-admin users cannot access this function.
1 Click Manage Users.
You are redirected to a new browser tab.
2 Log in with your admin credentials again.
The New User window appears..
Security
For information on security - See “Enabling LDAP Security in Fusion (Optional)” in Chapter
5 of the Fusion Installation and Administrative Guide for information on setting the security.
Configure a Test
From the home screen (see Figure 1 on page 4), click New Test.
The Choose Your Test window appears (see Figure 3 on page 12). Choose your test from
the list. For specific details on setting up each test, refer to the appropriate chapter.
Configure Test window. When both ports of the QT600-10 are configured for a TrueSpeed
Client to Test Point test, there are different overall status combinations for the device.
Table 3 on page 13 is a condition table showing the overall device status based on the
status of each port.
Table 3 QT600-10 Overall Status
The status condition display of the QT600-10 differs from the vTA display because the
QT600-10 has a Select Port dropdown menu. Clicking Select Port opens the menu so
you can see the status of the ports that are configured for TrueSpeed tests.
Show Specs shows the specifications for the test devices (see Figure 5 on page 14).
Notice that the phy is now phy-list because it shows the configuration of Port 1 and Port
2. If public access is set to “true”, the port appears in the Select Port menu. If set to
“false,” it does not appear in the menu.
NOTE
If only one port of the hardware device is configured for a TrueSpeed test, only
that port shows in Show Specs.
• Test Name
NOTE
The slash character “/” cannot be used as part of the test name because it will
cause the test to not generate results.
• Customer
• Technician
An administrator can also upload a company logo and specify a message that
will appear in the test reports. For more information, see Chapter 6 “Fusion
Administrative GUI Tasks” of the Installation and Administration Guide.
When the test starts running, the green play button changes to the red stop one.
A running test can be permanently stopped or paused. Press the red stop button and then
click Yes to stop the test and No to resume running the test.
NOTE
To delete tests from the list you need to log in as the administrator.
If you logged in as the administrator, you can mark and delete tests from the test list by
manually selecting the tests check boxes or clicking the Select All check box and then
pressing the Delete Selected Test(s) button. This will permanently delete the selected
tests, test results, and test reports.
.
NOTE
Users with administrative rights see the full list of tests that are running or have
run in the Test List. Users without administrative rights see only the tests that are
linked to their User ID.
You can also use different types of filters to simplify your Test List search.
• The Items Per Page drop-down box displays 10, 30, or 50 items per page.
• The Status drop-down box offers a choice between ALL, READY, QUEUED,
RUNNING, LOST, FINISHED, ABORTED, CANELLED tests to be displayed.
• The Test Type check boxes let you choose which of the four groups of Fusion tests
to display.
• The SEARCH capability allows you to search for test points using the device type.
For example, you can search for all of the vPMAs in the Test List or all of the Port 1’s
in the Test List.
NOTE
When a search is performed, the results of the search are cached and will not
get updated to reflect latest agent status. To get the latest agent status, exit the
search and repeat.
• When the test is running, as indicated by the running person icon in the figure below,
the following options on the Test List screen are available to the user.
– Click the Back to Test button to return to the running test.
– Click the Clone button to clone the test and configure the data.
When the test is not running, other options in the same locations become available to
the user.
– Run Test. The last configuration for this test will be executed again. The results
of the new execution will be listed under the existing entry for this test in the Test
List.
– Edit. Edit the view of the last configuration for this test. The test type, test mode,
and test points are not editable but other settings are. The results of the test will
be listed under the existing entry for this test in the Test List.
– Clone. Clone the view of the last configuration for this test but allow everything
to be edited. This includes test type, test mode, and test points. Once the test is
started, its results will be shown in a new entry in the Test List.
• The report can also be printed. The Print button is in the top left of the report page.
This chapter provides task-based instructions for using the Fusion Virtual Test Agent (vTA)
or a T-BERD/MTS to configure a measurement adapter for Y.1564 testing. Topics
discussed in this chapter are as follows:
• “Overview of Y.1564 Testing” on page 23
• “Configuring a Y.1564 Test” on page 25
• “Configuring a Y.1564 Test using T-BERD/MTS Test” on page 39
• “Running a Test” on page 47
NOTE
Fusion supports multiple tests for Y.1564 on a single vTA/Measurement Agent
(MA).
The Y.1564 test uses a two-phased approach in testing carrier Ethernet-based services:
• Service Configuration Test:
Each defined service is tested individually to validate network configuration. Service
attributes such as Committed Information Rate (CIR), rate limiting, traffic shaping,
and committed burst size are tested to ensure that they are configured correctly.
• Service Performance Test:
– Validates the quality of the Ethernet-based services over time.
– Is a long-term test conducted and compared to specified pass/fail criteria.
– Quality of Service (QoS), Frame Delay, Frame Delay Variation, Frame Loss, and
Out-of-Sequence (OoS) packets are validated.
– All services are tested simultaneously.
The ITU-T Y.1564 defines test streams (individually called a Test Flow) with service attri-
butes linked to the Metro Ethernet Forum (MEF) 10.2 definitions.
• Test Flows are traffic streams with specific attributes identified by different classifiers
such as 802.1q Virtual Local Area Network (VLAN), 802.1ad, Differentiated Services
Code Point (DSCP) and Class of Service (CoS) profiles.
• These services are defined at the User Network Interface (UNI) level with different
frame and bandwidth profiles such as the service Maximum Transmission Unit
(MTU), CIR, and excess information rate (EIR).
The VIAVI version of the Y.1564 test product accommodates and complies with the Y.1564
specification that was approved March 1, 2011 by the ITU (Ethernet Service Activation Test
Methodology).
NOTE
• The ability to configure a T-BERD/MTS as a test point controlled by the Fusion test
Controller is new in Fusion 4.0. However, the full interoperability connection to the
T-BERD/MTS is available starting in the 26.3 release. For more information on how
to utilize this feature on the T-BERD/MTS, refer to the 26.3 version of the T-BERD/
MTS/SC/MAP-2100 Ethernet and Fibre Channel Testing Manual.
• T-BERD/MTS is not a vTA. However, in this document, when the term vTA is used,
it is synonymous with a T-BERD/MTS. In other words, vTA will mean that you are
using some form of a test agent to perform the test. The only time that T-BERD/
MTS is references is in the sections specific to the device.
• The MTS must be configured to match the Public Access port. For a Remote
Public Access/DMZ (separate VM) the default port is 10443. If the Public Access/
DMZ is co-located with the Controller, then the default port is 9443. The port can
be changed to something other than default. Please check with Fusion Adminis-
trator to make sure you have the correct Public Access port.
Test Setup
1 To configure a new test, click the New Test button.
2 To configure a Y.1564 test, click SAMComplete Y.1564 from the list of tests.
4 Click Select
Choose a test point (Configure Test) window appears.
5 Find the vTA for your test in the list, click Select.
The selected vTA disappears from the list.
6 If you need two test points, repeat step 5 on page 28
NOTE
If two test points are required, you will know because the Choose a test point
window will not transition to the next Configure Test window. It is waiting for you
to select the second test point.
NOTE
If using a T-BERD/MTS agent, Layer to Test defaults to Layer 3 and cannot be
changed.
The Stream Rate Convention uses the Information Rate (IR) to interpret the CIR,
EIR, and Excess as L2 data rates. The Utilized Line Rate (ULR) interprets the CIR,
EIR, and Excess as L1 data rates. The L2 Mbps option (IR) means the tested band-
width is the specified bandwidth plus an additional 20 bytes per frame to account for
the Ethernet overhead. The L1 Mbps option (ULR) means the tested bandwidth will
be the specified value.
When the IR values are entered, the total IR and maximum ULR required by the test
are shown in the gauges at the footer of the Setup tab.
Suppress Loop Commands sends a Viavi proprietary loop-up request to the desti-
nation/loopback device at test start and a corresponding loop-down request at the
end of the test. There are ways to configure 3rd-party devices to be in loopback
mode outside of Viavi system. The Suppress Loop Commands button provides an
option to disable the sending of Viavi proprietary loop-up loop-down requests.
NOTE
• Since the L3 Y.1564 Loopback test is actually executed as a L4 Y.1564
Loopback test, the standard Loopback commands are not supported.
• If you want to loop up devices like a JMEP, QT600, or T-BERD/MTS5800,
you need to use an external system such as NetComplete. For more infor-
mation on Loopback testing using JMEP, see chapter “Using JMEP for
Loopback” in the NetComplete EtherASSURE EMS Solution User Guide.
For more information on using a QT600, see chapter “Running Loopback
Tests” in the QT-600 and QT-60010 Gigabit Ethernet Probe User Interface
Guide. For using T-BERD/MTS as a loopback device, refer to T-BERD/MTS/
SC/MAP-2100 Ethernet and Fibre Channel Testing Manual on how to put T-
BERT/MTS into loopback mode.
Configuring Connections
To configure the Connections for a test using the T-BERD/MTS, follow the proce-
dures in “Configuring T-BERD/MTS Connections” on page 39
Test points and streams are configured in the Connections tab.The Connections
tab defines the network configuration for the source and destination test points for a
Y.1564 tests. For a Layer 2 test, the source MAC address that is used in the test
packets is preconfigured on the test point. For a Layer 3 test, the source and destina-
tion IP addresses are either preconfigured or manually configured. The manual
configuration requires a Source Address, Subnet Mask, and the Gateway
Address. Source Address defines the IP address for the stream. Subnet Mask
defines the IPv4 subnet mask. Gateway Address defines the gateway IPv4 address.
To configure the Connections for a test using the T-BERD/MTS, follow the proce-
dures in “Configuring T-BERD/MTS Connections” on page 39
A window appears.
a If this is a Layer 3 test, go to step b on page 33. For a Layer 2 test, the message
in the window tells you that the MAC address has been preconfigured on the test
point. Click Done.
i The default for Define address using is Preconfigured IP. To change the
defaults, select Manual Entry.
ii Enter a Source Address, Subnet Mask, and Gateway Address.
iii Click Done.
2 Repeat step 1 on page 32 to configure the Connections for the destination.
3 If you are testing with a T-BERD/MTS, follow the procedure starting at step 2 on
page 40 when you have finished configuring Test Point A/Test Point B. If you are
using any other vTA, go to “Configuring Streams” on page 34
1 Click Destination.
The Edit Destination window appears.
Configuring Streams
Below the Test Point configuration is the Streams configuration. Stream 1 is the default
stream.
1 To edit Stream 1, put your cursor anywhere on the stream line and click.
The window opens. Go to step 4 on page 35 to complete the setup of Stream 1.
2 To add additional streams, click + add stream or click copy to duplicate Stream 1.
NOTE
To add additional streams, click + add stream. A maximum of 10 streams can be
added.
3 Put your cursor anywhere on the new stream header and click.
The configure window opens.
NOTE
Maximum Load is calculated and not editable. It is the maximum ULR needed
by the stream. ULR includes Ethernet overhead. It is the maximum CIR + EIR +
Policing algorithm converted to ULR for smallest frame size.
f For a Loopback test only, click to turn on Enabled FTD (Frame Transfer Delay)
For detailed information about Class Selector (CS) per-hop behavior, see RFC2474
(http://www.ietf.org/rfc/rfc2474.txt).
For detailed information about Assured Forwarding (AF) per-hop behavior, see
RFC2597 (http://www.ietf.org/rfc/rfc2597.txt).
For detailed information about Expedited Forwarding (EF) per-hop behavior, see
RFC2598 (http://www.ietf.org/rfc/rfc2598.txt).
2 Enter the TTL (Time To Live).
TTL is the number of router hops a packet is allowed before it is discarded for having
been in the network too long. Each router that receives the packet subtracts one from
the count in the TTL field. When the count reaches zero, the router detecting it
discards the packet and sends an Internet Control Message Protocol message back
to the originating host.
3 In Advanced Settings, select the Payload Type.
– Fill byte transmits the packets with payload populated with a specific pattern of
bytes. A repeated value of 0xAA is repeated when selected.
– PRBS (Pseudo-Random Binary Sequence) is the PRBS payload.
4 Click Done.
To configure more streams, return to “Configuring Streams” on page 34. If you are
ready to run your test, go to “Running a Test” on page 47.
T-BERD/MTS Setup
Follow procedure “Test Setup” on page 25 for the steps to set up the T-BERD/MTS test.
Setting up the test points for a T-BERD/MTS device works differently than setting up
the test points for a vTA. When a T-BERD/MTS is selected as a test point, the ability
to edit is disabled if the T-BERD/MTS uses the same IP to communicate to both the
Controller and a remote device. Disabling the ability to edit is a safety precaution to
prevent the user from accidentally changing the T-BERD/MTS IP address, causing
the T-BERD/MTS to disconnect from server.
NOTE
If the T-BERD/MTS uses a different IP address to connect to the Controller
instead of connecting to a remote MA (for example, a MAP-2100 device), the
ability to edit is enabled to allow the user to change the Source Test IP address in
the test setup.
2 To set up the VLAN for the T-BERD/MTS device, click the pencil icon next to
Network Access.
3 Number of VLAN.
Untagged means that no VLANs are used in the test. Single VLAN means there is
only one VLAN used in the test. Q-in-Q has two VLANS. S-VLAN defines the VLAN
used by the service provider. C-VLAN defines the VLAN used by the customer.
a Select Untagged, Single VLAN, or Q-in-Q.
b If Untagged is selected, click Done.
The Connections window appears.
c If Single VLAN is selected, you have to make a choice between defining a sepa-
rate VLAN for every stream or using the same VLAN for all streams.
i If you want to define a VLAN for each stream follow step d on page 42.
ii If you want to define one VLAN for all streams, select Define for All
Streams to define the VLAN for all streams.
NOTE
To add additional streams, click + add stream. A maximum of 9 streams can be
added for T-BERD/MTS.
You can specify one or more frame size to test in the Select Frame Sizes to
Test box. (You must specify at least one.)
NOTE
When a T-BERD/MTS device is the originator, the minimum Frame size is 66.
e Click Done.
3 Select the Frame Type. Choices are DIX and 802.3.
DIX is Digital, Intel, and Xerox. It is the Ethernet Frame Format that describes the
internal structure of a data packet on the wire and the frame as its payload consist of
binary data. This is the most often used frame type.
802.3 is the Ethernet Frame Format describing the internal structure of a data packet
on the wire and the frame as its payload consist of binary data.
4 For the instructions on configuring Layer 3, follow step 10 through step 4 on
page 39.
5 For Advanced Settings, go to step 3 and step 4 on page 39.
Running a Test
1 To run a test, click the green run button in the top left corner of the Configure Test
screen.
3 The Service Configuration Test runs first. This screen shot is an example of a Test
Point (A) to Test Point (B) test.
.
NOTE
There will be a 100% packet loss reported when the configured/selected frame
size is larger than the MTU configured on the agent. See the Fusion Installation
and Administrative Guide for information on how to adjust the MTU on the
agent.
4 The Service Performance Test runs. This screen shot is an example of a Sequen-
tial Bidirectional test.
Figure 6 Service Performance Test
5 Trending shows the one second real-time samples for the running Service Perfor-
mance Test. Click Trending (Figure 6) to view the results.
6 After all of the existing samples have been retrieved, an icon will appear next to each
of the stream’s names.
Figure 7 Another Option to View Trending Information
7 Selecting the bar graph icon (see Figure 7) shows a chart that trends the current
Frame Loss (FL) Count for the stream. It also shows the transmission data (Tx)
count and the receiving data (Rx) count. The chart updates automatically as new
data is available. Click and drag in the plot area to zoom in on the data. Click the
labels in the legend to toggle the information displayed.
Out of Sequence frames are counted as lost until they are received. Therefore, they
can be counted as lost in one sample and then reclassified as Out of Sequence in the
next. When this happens the current FLR and frame loss count can decrease,
possibly becoming negative.
NOTE
Tx and Rx counts could be different while the test is running. When the test
stops running, Tx will equal Rx plus FL (Tx = Rx + FL).
9 When the Service Performance Test is executed, there is an option at the top of the
report screen labeled Add Trend Charts. Selecting it will retrieve all of the one
second real time samples for the Service Performance Test and create a chart of
the Current Frame Loss values over the duration of the test. A chart is created for
each stream. See Figure 8 on page 50 for an example of what a Trend Chart looks
like.
Out of Sequence frames are counted as lost until they are received. Therefore, they
can be counted as lost in one sample and then classified as Out of Sequence in the
next. When this happens the current FLR and frames lost count can decrease,
possible becoming negative.
This chapter provides task-based instructions for using the Fusion interface to configure a
Virtual Performance Measurement Agent (vPMA) as a TWAMP Reflector. Topics
discussed in this chapter are as follows:
• “Overview of TWAMP” on page 55
• “Configuring and Starting a Full or Light TWAMP Reflector” on page 56
• “Stopping the TWAMP and TWAMP Light Reflector” on page 62
Overview of TWAMP
TWAMP, defined in RFC5357, is based on the One-Way Active Measurement Protocol
(OWAMP) specified in RFC4656. OWAMP provides a common protocol for measuring
bidirectional one-way metrics in both directions between two network elements. These
metrics require synchronization between local and remote clocks which is a shortcoming
with OWAMP because accurate synchronization is not possible.The information is echoed
back from the remote to the local host without an accurate time-stamp. TWAMP uses the
methodology and architecture of OWAMP to define an open protocol for the measurement
of two-way or round-trip metrics, in addition to the one-way metrics of OWAMP. One of
TWAMP's selling points is the ability to validate SLA which is not possible with OWAMP.
TWAMP employs time-stamps applied at the echo destination, known as the reflector, to
enable greater accuracy. The TWAMP Reflector and TWAMP Initiator monitor the perfor-
mance of Layer 3 core networks focusing on Packet Delay, Inter-Packet Delay Variation
(or Jitter), and Packet Loss.
TWAMP uses the Control Protocol. The Control Protocol initiates, starts, and stops a test
session. A session is a group of TWAMP Flows going to the same destination. The
maximum number of sessions is 175. Within one session, there is a maximum number of
10 TWAMP Flows. There is a session setup and negotiation protocol used between the
Initiator and the Reflector before the measurement traffic begins. The TWAMP Initiator test
sets up a session and flows, sends the packets, and then stops the session. The Reflector
knows the Initiator state and responds to the Initiator by transmitting packets back for every
packet it receives from the Initiator.
There is also a "lite" version of a TWAMP Reflector called TWAMP Light. TWAMP Light
does not use the Control Protocol, therefore, reducing the overhead associated with a
TWAMP Reflector. The Light Reflector is started and reflects the received test packets on
the specified UDP port until the reflector is stopped. The TWAMP Initiator simply sends test
packets, receives and processes the reflected packets until the test is stopped.
A TWAMP Initiator test and TWAMP Reflector test can run on vPMAs and QT600-10
devices. If running a TWAMP Light test using a vPMA, the vPMA must be version 2. A
TWAMP Reflector and TWAMP Light Reflector test cannot run concurrently on the same
vPMA or the same port of the QT600-10. A TWAMP Initiator test may be configured to
send traffic to both a Reflector and Light Reflector. You choose the type of reflector when
you define the session. Initiator and Reflector tests may run concurrently on a single vPMA
or QT600-10.
The QT600-10 is configured via the QT600-10 Craft Interface. For more information on
setting up the ports for a QT device, see the QT-600-10 Gigabit Ethernet Probe Installation
Guide or NetComplete EtherASSURE Test & Turn-up Solution User Guide. See the Fusion
Installation and Administration Guide for the vPMA installation procedure.
NOTE
You need to use a QT600-10 software version 11.7 with a baseline of at least
QT600-10-BL1356.
Purpose
Use this procedure to configure and start a TWAMP or a TWAMP Light Reflector.
• The Reflector must be up and running before the TWAMP Initiator can be
configured.
• The TWAMP Light Reflector requires vPMA version 2.
Procedure
The Endpoint window appears. This is where the TWAMP and TWAMP Light
Reflector are configured.
3 Configure the TWAMP or TWAMP Light Reflector.
The default is TWAMP Reflector. (To configure a TWAMP Light Reflector test, skip
this step and move to step c.)
NOTE
The TWAMP Light Reflector status screen looks similar to the TWAMP Reflector
screen with the same update messages.
When the message states that the test is starting, the message will then transition to
the “Reflector is running” message.
5 Click OK.
The Reflector is running screen transitions into STOP REFLECTOR.
6 The next step is to configure the TWAMP Initiator and start the test. Follow the steps
in Chapter 5 “Configuring a TWAMP Initiator.”
3 If you do stop the reflector, the status is confirmed in another pop-up window.
This chapter provides task-based instructions for using the Fusion interface to configure
the vPMA as a TWAMP Initiator. For a description of the TWAMP Initiator, see “Overview
of TWAMP” in Chapter 4 on page 55.
The QT600-10 is configured via the QT600-10 Craft Interface. For more information on
setting up the ports for a QT device, see the QT-600-10 Gigabit Ethernet Probe Installation
Guide or NetComplete EtherASSURE Test & Turn-up Solution User Guide. See the Fusion
Installation and Administration Guide for the vPMA installation procedure.
NOTE
• You need to use a QT600-10 software version 11.7 with a baseline of at least
QT600-10-BL1356.
• The Reflector must be up and running before the TWAMP Initiator can be
configured.
NOTE
For more information on ToS/Diffserve, see “ToS/DiffServ” in Chapter 6 on page
91
The Sessions tab is for adding, removing, or editing the Control Sessions and their
TWAMP Flows for the TWAMP and TWAMP Light Reflector.
– The maximum number of Control Sessions that can be defined is 175.
– Within one Control Session, there is a maximum number of 10 TWAMP Flows
allowed to be defined in each TWAMP Reflector or TWAMP Light Reflector test
configuration.
– A vPMA supports a total of 500 TWAMP Flows across simultaneous TWAMP
Initiator tests and the TWAMP Reflector functionality.
Therefore, if you are adding a TWAMP Reflector to your TWAMP Initiator, you can
configure any number of Control Sessions up to 175 with any number of TWAMP
Flows up to 10 as long as the total of TWAMP Flows is 500 or less.
TWAMP Light does not use Controls Sessions, but you have to go into the
Sessions tab in Fusion to configure the TWAMP Light Reflector and the flows.
TWAMP Light also supports a maximum of 500 flows.
NOTE
Packet processing performance and jitter was observed during testing and
varies widely based on several factors. These factors include the virtual machine
(VM) host monitoring and processing, network traffic applying to other guest VM,
and performance and number of cores in the host platform. Viavi recommends
that the user slowly scales up the number of flows in the long-term performance
monitoring testing to determine under what conditions the measurement
accuracy starts to degrade. The network interrupt handling in virtualized
environments causes the lack of predictability which is not a problem in
traditional measurement hardware devices.
The default is TWAMP Reflector. (To configure a TWAMP Light Reflector, skip
this step and move to step c.) To configure a TWAMP Reflector, enter the
following information.
- Enter the Control Server/Reflector IP Address.
- Enter the Control Server TCP Port for the reflector’s TCP port to establish
the Control Session.
- Click Done to save your entries and return to the Control Sessions tab.
c To configure a TWAMP Light Reflector, click the Control Server/Reflector icon
(See numbers 1 and 2 in Figure 10 on Page 68).
The Edit Control Server/Reflector window pops up and defaults to the TWAMP
configuration parameters (See numbers 1 and 2 in Figure on Page 69).
i Click the check box for Use TWAMP Light.
The TWAMP Light Reflector IP Address input box appears.
d TWAMP Flows
All Sessions have one default flow. This flow can be edited and more flows can
be defined.
To edit the default TWAMP Flow configuration, click anywhere on the flow
display. (See numbers 1 and 2 in Figure 10 on Page 68)
The edit screen pops up.
i Enter the Flow Name. Each flow must have a unique name because the
result data shows the measurements by flow name.
ii Packet Structure specifies the packet details for this flow.
• Select the desired Service/DSCP from the drop-down list. Default is
Best Effort (0).
• Choose Packet Length or Padding for Size Defined By
Padding is the number of bytes of padding that should be added to the
UDP test packets generated by the sender. Choose a byte size
between 0 and 1431.
Packet Length is the total number of bytes in the UDP test packets
generated by the sender. Choose a byte size between 87 and 1518.
• Reflector UDP Port is the port used in the test and is used during
session initialization. The Control Server may alter the specified value.
The value range is 1 to 65535, and the default is 50000.
For TWAMP, the value configured is used as a suggested reflector port
number during the negotiation done at session initialization. The
reflector (control server) may alter the port number.
For TWAMP Light, the value in this field is used in the test and must
match the value configured in the reflector’s UDP Port. In this case,
there is no session initialization.
– 10 ms – 1 sec
– 20 ms – 2 sec
– 100 ms (default)
• Click Done to save your entries and return to the Sessions tab.
iv Click +add flow to enter details for additional flows. Then go back to step d
on page 70 and repeat the steps until you have configured all of the flows
you need for the TWAMP Reflector. When you have finished entering all of
the flows, proceed to step 5.
5 Click the green run button (numbers 1 and 2 in Figure 10 on Page 68).
The TWAMP Initiator is a long-running test. Fusion provides interactive options to view the
test and flow information as well as NRT results.
NOTE
The intermediate results user interface supports tests with up to 500 flows.
Procedure
1 Find your test in the list. Click either the running person icon or the Back to Test
icon.
Click on TWAMP in the upper left corner to view the TWAMP Initiator test configuration
information.
Click on the + Add Flows to Monitor (see numbers 1 and 2 in Figure 11 on Page 73)
in the Near Real-time Monitor section to add additional test information. Click the check
boxes under the Monitor column to choose up to four flows.
Additional information about the flows can be viewed. Select more... (numbers 1 and 2 in
Figure 12 on Page 75) in the Details column to see addiditonal Flow Information about
the selected flow.
The Dest Port column will contain the word “obtaining” until the Control
Session is successfully established. Afterwards, it will contain the port that
resulted from the Control Session negotiation. The original port that was
requested can be seen in the Details.
Click the icon in the PM Stats column to see the PM Stats for Flow x for that selected flow.
Click Done to close the PM Stats for Flow x window.
Click Select after viewing the additional data for the flow.
The NRT Monitor will open and begin displaying the results for the selected flows.
The NRT feed can be paused and resumed. The reported NRT data can also be inter-
rupted by the system or equipment events such as network connectivity issues. Regard-
less of why the NRT data is paused, the screen will indicate the pause with this message.
“NRT Monitoring is Paused. Press Play to resume” (numbers 1 and 2 in Figure 14 on
Page 78).
Figure 14 Current Results Window
The NRT is paused while generating a report. Therefore, after returning to the
main view, any NRT charts will show a Paused event (purple vertical line in the
charts).
Near Real-time monitoring can be extended for 30 minutes if renewed prior to the current
results expiring for that test. There is a five minute window right before the current moni-
toring period ends when the Renew Monitoring button appears in two locations on the
Current Results Screen (numbers 1 and 2 in Figure 15 on Page 79). Renewing the moni-
toring prevents a gap in the data.
Figure 15 Renew Monitoring
• Click on the Run Report to select up to 10 flows and specify how many days worth of
data to include in the report. The range is the last 1-7 days. Click Select.
• A new Current Results window displays the report results.Scroll the screen to see the
entire report.
The the next two pages are an example of what a printed report might look like.
• Display SLA/Remove SLA - this toggles whether the user defined SLA thresholds
specified on the main view are displayed in the charts.
• Print/Save allows the user to print or save the report to a PDF file.
• Close Report returns the user back to the Current Results screen.
NOTE
If the TWAMP NRT test results status does not get updated, make sure that the
PDF report window is closed.
This chapter provides task-based instructions for using the Fusion vTA to configure True-
Speed testing. Topics discussed in this chapter are as follows:
• “Overview of the TrueSpeed Test” on page 87
• “Configuring a TrueSpeed Test Point to Test Point Test” on page 89
• “Configuring a Client to Test Point Test” on page 101
Many variables are involved in TCP Throughput performance, but TrueSpeed focuses on
the following:
• Bottleneck Bandwidth (BB)
• Round-Trip Time (RTT)
• Send and Receive Socket Buffers
• Minimum TCP Receiver Window (RWND)
• Path Maximum Transmission Unit (MTU)
TCP is connection oriented, and at the transmitting side, it uses a congestion window (TCP
CWND). At the receiving end, TCP uses a receive window (TCP RWND) to inform the
transmitting end of how many bytes it is capable of accepting at a given time.
Derived from RTT and network BB, the Bandwidth-Delay Product (BDP) determines the
Send and Received Socket buffer sizes required to achieve the maximum TCP
Throughput. Then, with the help of slow start and congestion avoidance algorithms, a TCP
CWND is calculated based on the IP network path loss rate.
Finally, the minimum value between the calculated TCP CWND and the TCP RWND
advertised by the opposite end will determine how many bytes can actually be sent by the
transmitting side at a given time.
RFC 6349 Maximum Segment Size ((MSS) equals TCP payload length) detects the
minimum of the PC’s Network Interface Card (NIC) card setting and network path interface
settings (smallest MTU on any device in the path.) If the NIC MTU is set to 1300 bytes, the
report will explicitly show this in the Client Configuration section. Lower MTU size may
reduce throughput if the PC hardware cannot process the higher packets/sec rate. Table 7
on page 143 Appendix B provides recommendations for the client PC computer hardware
specifications. Smaller MTU sizes may merit more powerful PC benchmarks as shown in
the table.
A QT600-10 is configured via the QT600-10 Craft Interface. For more information on
configuring the ports for a QT device, see the QT-600-10 Gigabit Ethernet Probe Installa-
tion Guide or NetComplete EtherASSURE Test & Turn-up Solution User Guide. See the
Fusion Installation and Administration Guide for the vTA installation procedure.
NOTE
You need to use a QT600-10 software version 11.7 with a baseline of at least
QT600-10-BL1356.
Mode Description
Test Point to Test Point Tests vTA to vTA and QT600-10 device to vTA and runs
inside the service providers network.
Client to Test Point The client is typically the end customer’s laptop. This
test checks the network running between a laptop and a
vTA or QT600-10 device.
1 Select TrueSpeed.
3 Select the first test agent from the list of available test points. Click Select.
The selected test point is removed from the list.
4 Select the second test point from the same list.
The Configure Test window appears.
The ToS default is 00000000. This field shows the binary number repre-
senting the ToS value. If you know the hexadecimal value you want to enter,
you can do so. For example, if you type the value 0x28 and click enter, the
value will show its binary equivalence 00101000.
- DiffServ redefined the entire definition of ToS in RFC2474. The DiffServ
field and the upper six bits contain a value called DSCP, which define how
specific packets should be moved through the network. The DSCP triggers
a per-hop behavior for the packet and provides the appropriate QoS
treatment.
For detailed information about Class Selector (CS) per-hop behavior, see
RFC2474 (http://www.ietf.org/rfc/rfc2474.txt).
For detailed information about Assured Forwarding (AF) per-hop behavior,
see RFC2597 (http://www.ietf.org/rfc/rfc2597.txt).
For detailed information about Expedited Forwarding (EF) per-hop behavior,
see RFC2598 (http://www.ietf.org/rfc/rfc2598.txt).
d Select a TCP Port
This specifies the port to be used for the test. Only one test at a time can run on
a port. If there is an attempt to run a test on the same port, the second test is
queued and runs after the first test completes. The port numbers range from
8080 to 8089. The UI choices include these numbers but also provide a First
Available instead of specifying a port in which case the device will select it’s
available TCP Port. You may see all of the ports in the TCP Port menu or only
one depending on the TCP Port configuration for the test device. In Figure 4 on
page 12, all of the port numbers have been added and will show in the UI. In
Figure 5 on page 14, only one port has been added.
e Click Run Exclusive
Turning this option on makes the test run exclusively on the measurement agent.
6 Setting up the Window Walk parameters.
a Enter Starting % of CIR
A step load test is used to gradually reach and exceed the CIR. Each step
represents a throughput value in percent of CIR (% of CIR). The user can define
the starting value (in % of CIR), and depending on the amount of throughput
steps defined (number of walks, see below) the system will calculate the distribu-
tion of throughput steps. The default value is 50.
b Enter Number of Walks
Specifies the number of walks (throughput steps) to run in each direction. If the
Run Saturation Window option is Yes, then the walk value must be 0. If the
Starting % of CIR is 100, then this walk value must be 1. Otherwise, the value
must be in the range from 1 to 10.
NOTE
If the starting point of % of CIR is less than 100 and the Number of Walks is 1,
then the test will always be executed at % of CIR at 100% regardless of what is
selected.
When set to Yes, the Boost Window By and Boost Connection By can be
configured. Boost Window By percentage is a multiplier of how much to
increase the BDP window (last window run). Boost Connection By percentage
is a multiplier for how much to increase the BDP connection count. Both have a
minimum value of 0 and a maximum of 100.
i Enter Boost Window By
ii Enter Boost Connection By
7 To run the test, click the green run button at the top left corner of the Configure Test
window (see Figure 17 on page 91). There are two choices for stopping the running
test. The first is during the Initialization phase and the second is during the Interme-
diate Results phase. (see Figure 19 on page 96).
3 The Running RTT Test screen appears indicating that the RTT is being calculated.
Client configuration is page 5 when using the Expert View option and running a
Client to Test Point test.
Figure 23 Client configuration page 5
There are also graphs for each upstream and downstream window test. When you
view the graph reports, you can hover over each point for additional trending informa-
tion at that point of time during the test.
Client Process Snapshot is the last page when using the Expert View option and
running a Client to Test Point test.
Figure 25 Client Process Snapshot last page
1 Click TrueSpeed.
3 Select one test agent or one device port from the list of available test points. Click
Select.
The Configure Test window appears.
NOTE
If Public Access is false, then the device is only configured for a QT to QT test.
If Public Access is true, then the QT is configured to run both QT to QT and QT
to PC client test. For information on where Public Access is defined, refer to the
QT-600-10 Gigabit Ethernet Probe Installation Guide or NetComplete
EtherASSURE Test & Turn-up Solution User Guide. To see where you can check
the value of Public Access in Fusion, refer to Figure 5 on page 14.
The ToS default is 00000000. This field shows the binary number repre-
senting the ToS value. If you know the hexadecimal value you want to enter,
you can do so. For example, if you type the value 0x28 and click enter, the
value will show its binary equivalence 00101000.
- DiffServ redefined the entire definition of ToS in RFC2474. The DiffServ
field and the upper six bits contain a value called DSCP, which define how
specific packets should be moved through the network. The DSCP triggers
a per-hop behavior for the packet and provides the appropriate QoS
treatment.
For detailed information about Class Selector (CS) per-hop behavior, see
RFC2474 (http://www.ietf.org/rfc/rfc2474.txt).
For detailed information about Assured Forwarding (AF) per-hop behavior,
see RFC2597 (http://www.ietf.org/rfc/rfc2597.txt).
For detailed information about Expedited Forwarding (EF) per-hop behavior,
see RFC2598 (http://www.ietf.org/rfc/rfc2598.txt).
d Select a TCP Port
This specifies the port to be used for the test. Only one test at a time can run on
a port. If there is an attempt to run a test on the same port, the second test is
queued and runs after the first test completes. The port numbers range from
8080 to 8089. The UI choices include these numbers but also provide a First
Available instead of specifying a port. You may see all of the ports in the TCP
Port menu or only one depending on the TCP Port is configuration for the test
device. In Figure 4 on page 12, all of the port numbers have been added and will
show in the UI. In Figure 5 on page 14, only one port has been added.
e Expiration Time (UTC)
This option states how long the test URL is valid. The Expiration Time choices
are in hours, days, or Unlimited. The timestamp always defaults to 24 hours
from the current date.
NOTE
If you want the URL to never expire, then set Expiration Time and Maximum
Execution Counts to Unlimited.
NOTE
If the starting point of % of CIR is less than 100 and the Number of Walks is 1,
then the test will always be executed at % of CIR at 100% regardless of what is
selected.
Selecting this runs one additional TCP test in each direction that is configured to
run a TCP window greater than one based on the CIR to determine the
maximum network bandwidth. The boost settings can be used to deflate or
inflate the window size and/or connection count used by the saturation window
test from 0% to 100%. This parameter attempts to fully utilize the specified CIR.
When set to Yes, the Boost Window By and Boost Connection By can be
configured. Boost Window By percentage is a multiplier of how much to
increase the BDP window (last window run). Boost Connection By percentage
is a multiplier for how much to increase the BDP connection count. Both have a
minimum value of 0 and a maximum of 100.
i Enter Boost Window By
ii Enter Boost Connection By
Figure 27 Run Saturation Window
6 Click Generate URL for Client button to generate a URL with the test parameters.
7 Click Copy URL.
8 Paste the URL in an email and send it to the person who will run the test.
2 Click the link in Step 1 (Figure 28 on page 107) Download Windows (64-bit)
Installer to download pctestclient-windows-x64.exe, or click Download
Other Installer to find your operating system. See Table 6 on page 142 in
Appendix B for information on the supported operating systems.
The executable file downloads to your computer.
3 Locate downloaded file and run your computer’s software installation procedure to
install the Viavi Test Client Setup software.
The Setup - VIAVI Test Client window appears.
4 Click Next
The Installation Folder window appears.
6 Make sure the Viavi Solutions Test Client box is selected (checked) and click Next.
7 After the PC client installation completes, return to the browser and locate Step 2
(Figure 28 on page 107). Click Download Config File setting.test to your
computer.
8 Save the setting.test file.
9 Click setting.test file to launch the test.
The Throughput Test TCP/UDP screen appears.
If there are no network issues between the PC client and the Fusion server, the test
should run successfully.
Go to “View a Running Test on the Client Computer” on page 110 for information on
how to view a running TrueSpeed test.
2 The Waiting for test resource to be ready window transitions to the Initializing
screen.
You can stop the test from running via the client computer by clicking the STOP
TEST button.
4 The Intermediate Results screen appears.
The detailed report is created and resides on the Test Point server. See examples of
the report starting with Figure 20 on page 96.
This chapter provides task-based instructions for using the Fusion vTA to configure UDP
testing. Topics discussed in this chapter are as follows:
• “Overview of UDP testing” on page 113
• “Configuring a UDP Test Point to Test Point Test” on page 114
• “Configuring a Client to Test Point Test” on page 123
The UDP testing algorithm in the Fusion solution is implemented very similar to the Layer3
Y.1564 performance test. The user can define multiple UDP traffic streams, simulating the
behavior of different applications. Depending on the chosen application type and direction
(unidirectional or bidirectional) the corresponding bandwidth is reserved on the transmis-
sion link during the test. It is important to mention that the test is NOT trying to simulate
actual application traffic but it is only blocking/reserving the corresponding amount of
bandwidth.
While the test is executed, all traffic streams for one direction are run simultaneously
testing the link for its bandwidth and throughput capabilities. The related parameters are
throughput and packet loss. In addition, the test is also measuring round trip delay and jitter
for each stream
There are two modes in the drop-down menu: Test Point to Test Point and Client to
Test Point. Test Point to Test Point is the default.
Mode Description
Test Point to Test Point Tests vTA to vTA and runs inside the service providers
network consisting of two vTAs.
Client to Test Point The client is typically the end customer’s laptop. This
test checks the network running between a laptop and a
vTA.
NOTE
A Client to Test Point test is only allowed when Public Access in Show Specs
for UDP is set to true. When Public Access is false, Client to Test Point does
not appear in the drop-down Mode when you choose the UDP test from the
Configure Test window.
2 Click Select.
The Choose a test point window appears.
Figure 32 Choose a test point
3 For the Test Point to Test Point test, choose two test points from the list of available
agents by clicking Select for each test point.
The Configure Test screen displays.
- IR
This is the rate at which layer 2 (Ethernet) frames are transmitted. It
includes the entire layer 2 Ethernet frame, the 14-byte header (for frames)
and the 4-byte FCS (CRC).
– VLAN Present?
Select Yes or No. This box permits you to override the default value that marks
VLAN as present if one MA (in Client to Test Point test) or both MAs (in Test
Point to Test Point test) is/are tagged. In all other cases the default option is No.
5 My Connection
This area lists the values of Preconfigured IP, Subnet Mask, and Gateway for both
test points that were registered by the Controller.
6 Streams
This area contains the table for configuring the streams. All entries are configurable.
Clicking them will open the stream configuration editor window with editing options.
Hover the mouse over the icons in the left column to see their functions. You can
configure up to 10 streams for the MA-to-MA test and up to 5 streams for the PC-to-
MA test.
NOTE
• One bidirectional stream on the user interface equates to two streams on
the MA. A total MA streams of > 10, for the MA-to-MA test, may affect the
performance of the test.
• One bidirectional stream on the user interface equates to two streams on
the MA. A total MA streams of > 5, for the PC-to-MA test, may affect the
performance of the test.
7 Aggregate
This area sums up the cumulative of the streams direction, ULR or IR bandwidth and
UDP bandwidth. The aggregates are grouped by direction. In the example of an MA
to MA test below, the aggregate will sum up all of the streams with A to B direction
(blue arrow) and all of the streams with B to A (yellow arrow). Then the Aggregate
takes into account the bidirectional streams in both A to B and B to A entries (green
arrow) by adding their values to both of the unidirectional entries.
8 Click any value in each stream to open the Stream Configuration Editor window.
The fields on the editor window change based on the stream type selected. Enter the
Name, Stream Type, and Stream Direction. The next three values are part of a
formula. ULR/L1 or IR/L2 bandwidth are calculated from the user-defined UDP band-
width and frame size. Changing either of these two values will cause this field to be
recalculated.
– UDP BW (bandwidth)
This is derived based on the service type of Data, Voice, and Video. Data: 10,
Video: 7 (HDTV, MPEG-4, 1 Channel), Voice: 1.264 (G.711, 10 Sampling, 10
Calls).
– Frame Size
This is derived also based on the service type of Data/Voice/Video. Data: 512,
Video: 1392 (HDTV, MPEG-4, 1 Channel), Voice:138 (G.711, 10 Sampling, 10
Calls). The default frame size for the Stream Type is 512. The user can pick
frame size from the frame size selection popup, and override the default for Data
or Video stream types. In the case of the Voice stream, this field is computed by
the system and cannot be overridden.
WARNING
The frame size must be equal or less than MTU size. When the frame size is
larger than the MTU size, the test will fail with the error “Test communication
lost”. Typically for Point-to-Point Protocol over Ethernet (PPPoE) connections,
the MTU size is 1492 bytes.
9 Click the green Run button at the top left corner of the Configure Test screen to run
the Test Point to Test Point test (Figure 33 on page 116).
If you need to stop the test, click the red stop button in the upper left corner that
appears in the Intermediate Results screen (Figure 34 on page 121).
1 The splash screen appears and informs you that the Test Point has received your
test request.
NOTE
There will be a 100% packet loss reported when the configured/selected frame
size is larger than the MTU configured on the agent. See the Fusion Installation
and Administrative Guide for information on how to adjust the MTU on the
agent.
Mouse over the gear icon next to stream name to see the stream configuration
information
4 After the test concludes, the reports window appears. On the left side, you can
enable or disable the following reports: Throughput, Packet Loss Ratio, Round
Trip Time, and Jitter. Here are samples from the report:
Figure 35 First page example of the UDP test
The Test Report screen states whether the test passed or failed and lists the
duration, date, test points, and technician’s name.
The next screen that follows is the Results screen and lists the streams grouped by
direction and provide the Packet Loss, Packet Counts, RTT Results, and Jitter
results per each stream. The aggregate throughput is the sum of the individual
stream throughput values.
Figure 36 UDP graph example
3 Locate the Test Point to use for your test (Figure 32 on page 115). Remember that
the Client to Test Point only uses one Test Point.
The Configure Test screen appears.
Figure 38 Client to Test Point Configure Test
NOTE
If you want the URL to never expire, then set Expiration Time and Maximum
Execution Counts to Unlimited.
5 My Connection. This area lists the values of Preconfigured IP, Subnet Mask and
Gateway for both test points that were registered by the Controller.
6 Streams. This area contains the table for configuring the streams. All entries are
configurable. Clicking them opens the stream configuration editor window with
editing options. Hover the mouse over the icons in the left column to see their func-
tions. You can configure up to 10 streams for the MA-to-MA test and up to 5 streams
for the PC-to-MA test.
NOTE
• One bidirectional stream on the user interface equates to two streams on
the MA. A total MA streams of > 10, for the MA-to-MA test, may affect the
performance of the test.
• One bidirectional stream on the user interface equates to two streams on
the MA. A total MA streams of > 5, for the PC-to-MA test, may affect the
performance of the test.
7 Aggregate
This area sums up the cumulative of the streams direction, ULR or IR bandwidth and
UDP bandwidth. The aggregates are grouped by direction. In the example of an MA
to MA test below, the aggregate will sum up all of the streams with A to B direction
(blue arrow) and all of the streams with B to A (yellow arrow). Then the Aggregate
takes into account the bidirectional streams in both A to B and B to A entries (green
arrow) by adding their values to both of the unidirectional entries.
8 Click any value in each stream to open the Stream Configuration Editor window.
The fields on the editor window change based on the stream type selected. Enter the
Name, Stream Type, and Stream Direction. The next three values are part of a
formula. ULR/L1 or IR/L2 bandwidth are calculated from the user-defined UDP band-
width and frame size. Changing either of these two values will cause this field to be
recalculated.
– UDP BW (bandwidth)
This is derived based on the service type of Data, Voice, and Video. Data: 10,
Video: 7 (HDTV, MPEG-4, 1 Channel), Voice: 1.264 (G.711, 10 Sampling, 10
Calls).
– Frame Size
This is derived also based on the service type of Data/Voice/Video. Data: 512,
Video: 1392 (HDTV, MPEG-4, 1 Channel), Voice:138 (G.711, 10 Sampling, 10
Calls). The default frame size for the Stream Type is 512. The user can pick
frame size from the frame size selection popup, and override the default for Data
or Video stream types. In the case of the Voice stream, this field is computed by
the system and cannot be overridden.
WARNING
The frame size must be equal or less than MTU size. When the frame size is
larger than the MTU size, the test will fail with the error “Test communication
lost”. Typically for PPPoE connections, the MTU size is 1492 bytes.
9 Click the blue Generate URL for Client (Figure 38 on page 124) button to generate
a URL with the test parameters.
10 Click Copy URL.
11 Paste the URL in an email and send it to the person who will run the test.
2 Click the link in Step 1 (Figure 39 on page 128) Download Windows (64-bit)
Installer to download pctestclient-windows-x64.exe, or click Download
Other Installer to find your operating system. See Table 6 on page 142 in in
Appendix B for information on the supported operating systems.
The executable file downloads to your computer.
3 Locate downloaded file and run your computer’s software installation procedure to
install the Viavi Test Client Setup software.
The Setup - VIAVI Test Client window appears.
4 Click Next
The Installation Folder window appears.
6 Make sure the Viavi Solutions Test Client box is selected (checked) and click Next.
7 After the PC client installation completes, return to the browser and locate Step 2
(Figure 39 on page 128). Click Download Config File setting.test to your
computer.
8 Save the setting.test file.
If there are no network issues between the PC client and the Fusion server, the test
should run successfully.
Go to “Viewing a Running Test on the Client Computer” on page 131 for information
on how to view a running UDP test.
You can stop the test from running via the client computer by clicking the STOP
TEST button (Figure 42 on page 132).
NOTE
If you stop the test before any intermediate test results are displayed, duplicate
confirmation dialog boxes will appear.
At this point, you can restart the test from the client computer by clicking the Start
Over button (Figure 43 on page 133).
This chapter describes how to maintain, identify, and correct problems related to the
Fusion. Topics discussed in this chapter are as follows:
• “Troubleshooting” on page 135
• “Interpreting alarms” on page 135
• “Solving problems” on page 135
Troubleshooting
The Fusion includes control panel indicators and error messages to help you troubleshoot
problems. Strategies for troubleshooting are also discussed in this chapter. If you are
unable to resolve problems related to the Fusion, refer to “Technical assistance” on
page xii.
Interpreting alarms
The Fusion includes control panel indicators and error messages to help you troubleshoot
problems.
Solving problems
If you experience difficulties using the Fusion, refer to the related topic. Each topic
describes problems and solutions that may be pertinent to your task. If you are unable to
resolve your problem, please contact “Technical assistance” on page xii.
Controller/Collector
1 Test cancelled. Failed to contact probe <Probe name>, reason =
transfer request failed.
Lost the communication with the probe < Probe name>. Check the
connectivity with the probe.
2 License for < License Name> Not Available
Apply the license at the window Setting -> License
3 Exceed the maximum capacity of the license Maximum Number of
Flows.
Decrease the number of flows in the test request or apply the
license to increase the number of flows.
4 Exceed the maximum capacity of the License Aggregate Bandwidth.
The bandwidth of the test request exceed the maximum capacity
of the License Aggregate Bandwidth. Decrease the bandwidth of
the test request or apply the license to increase the aggre-
gated bandwidth.
5 Same license is already added
Can't apply the same license file. Check the license file at
the license portal.
6 License is already expired.
Can't apply the license which is already expired. Check the
license end date at the license portal.
7 Resource unavailable: Not found the valid license for UDP test
Check the license for UDP test and apply the license when need.
8 Resource unavailable: Can't access a probe <Probe name>
Check the probe status of inventory information and check the
connectivity of probe
9 Resource unavailable: probe queue is full
Exceed the maximum outstanding request counts for probe. The
default maximum counts is 20. Issue the request later.
10 Resource unavailable: Test is expired. <schedule id>
The test is already expired to execute. This is only for UDP
test.
11 Test cancelled: No Contact with probe
User Interface
1 Timed out receiving status for test request. Check test list to
see if test actually started or stopped
Did not receive the expected status for test request from the
controller. Check the test status in the test list.
2 The provided user name and password cannot be authenticated
Session Count Exceeded
Exceeded the license Number of Users. Apply the license to
increase the number of concurrent users login.
3 Service Temporarily Unavailable
The server application is not reachable. This could be due to
network issues or because the application is not running.
Probe
1 Probe: Request Conflict(409): Schedule < Schedule Name>
already running.
A test that has the same schedule name is running. Check the
running test.
2 Probe: Request Conflict(409): Request resources unavailable:
too many active tests
Exceed the maximum concurrent running test count. Issue the
test later.
3 Probe: Request Conflict(409) no new test can be started right
now.
Probe is not ready. Issue the request later.
4 Test cancelled. Probe: FAILED_LOOP_UP_TIMEOUT
This chapter provides the requirements for the client computer. Topics discussed in this
chapter are as follows:
• “Controller/Collector Hardware Requirements” on page 141
• “Client PC Hardware and Software Requirements” on page 142
• “Client PC Security Software Considerations” on page 143
NOTE
ARM and Tile-GX architectures are NOT supported.
Operating Internet
Edge Firefox Chrome
System Explorer 111
Windows 7 X X X
Windows 7 - 32 bit X X X
Windows 8.1 X X X
Windows 10 X X X
Ubuntu 12.042, X X
14.04, and 16.04
1.
2.
~Processor
CIR Comments
Benchmark Score
700 – 1000 Mbps > 4500 This is usually an i7 or newer family i5
(https://www.cpubenchmark.net/
high_end_cpus.html)
400 – 700 Mbps 3000 - 4500 Mbps Most i5s, some i3s (https://www.cpu-
benchmark.net/mid_range_cpus.html)
Below 400 Mbps < 3000 i3s, older i5s (https://www.cpubench-
mark.net/midlow_range_cpus.html
Maximum ULR
~Processor
for Frame Size Comments
Benchmark Score
1518 Bytes
300 - 600 Mbps > 4500 This is usually an i7 or newer
family i5 (http:// www.cpubench-
mark.net/ high_end_cpus.html)
300 - 200 Mbps 3000 - 4500 Most i5s, some i3s (http://
www.cpubenchmark.net/
mid_range_cpus.html)
Below 200 Mbps < 3000 i3s, older i5s (http:// www.cpu-
benchmark.net/ mid-
low_range_cpus.html
3 For GigE tests, it is imperative that the end customer or field technician has a laptop
with ALL security software disabled. For lower speed tests like 200+ Mbps, etc., this
may not cause a problem.
Appendix C Benchmarks
UDP Benchmarks
Benchmarks for SR-IOV and VIRTIO testing were conducted on SuperServer 5028D-
TN4T has the Intel(R) Xeon(R) CPU D-1541 @ 2.10GHz. The networking was provided by
Intel Corporation Ethernet Controller X710 for 10GbE SFP+. The system were running 64-
bit Linux with Kernel-based Virtual Machine (KVM).
Loopback Benchmarks
Benchmarks for SR-IOV and VIRTIO testing were conducted on SuperServer 5028D-
TN4T has the Intel(R) Xeon(R) CPU D-1541 @ 2.10GHz. The networking was provided by
Intel Corporation Ethernet Controller X710 for 10GbE SFP+. The system were running 64-
bit Linux with Kernel-based Virtual Machine (KVM).
The vPMA uses eth0 for management and eth1 for testing. The network attached to eth1
was locally routed within OpenStack.
Table 9 Default VIRTIO driver used for eth1
# ethtool -i eth1
driver: virtio net
version: 1.0.0
firmware-version:
expansion-rom-version:
bus-info: 0000:00:04.0
supports-statistics no
supports-test: no
supports-eeprom-access: no
supports-register-dump no
supports-priv-flags: no
# cat /proc/cpuinfo
processor: 0
vender ID: GenuineIntel
CPU family: 6
model: 58
model name: Intel Xeon E3-12xx v2 (Ivy Bridge, IBRS)
stepping: 9
microcode: 0x1
CPU MHz: 2693.508
cache size: 4096 KB
Viavi Solutions
North America: 1.844.GO VIAVI / 1.844.468.4284
Latin America +52 55 5543 6644
EMEA +49 7121 862273
APAC +1 512 201 6534
All Other Regions: viavisolutions.com/contacts
email [email protected]