Xgig Maestro 8.1.1 Patch Release Notes

Build: 8.1.1.169177   Date: January 21, 2016
Overview

Feature Enhancements
& Defect Fixes

System Requirements

Client Installation

Upgrading the Chassis

Compatibility and Interoperability

Known Issues

Previous Releases

Support

Viavi Solutions Inc.
Network and Service Enablement Division
Storage Network Test Group

430 N. McCarthy Blvd
Milpitas, CA 95035

www.viavisolutions.com/snt

Overview

This Readme details information regarding the latest features provided in this release with known issues and other helpful information.

NOTE:

We are in the process of rebranding our products from JDSU to Viavi Solutions. Some areas still has references to JDSU.

As part of rebranding, Maestro installation path has changed in this release.

"C:\Program Files\JDSU\Xgig Maestro" to "C:\Program Files\Viavi\Xgig Maestro" OR
"C:\Program Files (x86)\JDSU\Xgig Maestro" to "C:\Program Files (x86)\Viavi\Xgig Maestro"

NOTE: If you have existing Maestro version already installed, please uninstall old version before installing the latest version. Otherwise, Maestro may still install in the old JDSU path.


Feature Enhancements and Defect Fixes

Jammer

  1. SAS/SATA Jammer - Fixed a problem that the cross path modes were not available for Xgig 6G blade.

Top of Page

System Requirements

Listed below are the recommended system configurations for Xgig Maestro to achieve optimal performance.

OS (32-bit and 64-bit) Windows 7 Professional and Enterprise with Service Pack 1
Windows 8.1 Professional or Enterprise
Windows Server 2008 Standard or Enterprise with Service Pack 2
Windows Server 2008 R2 Standard or Enterprise with Service Pack 1
Windows Server 2012 R2 Update Standard or Essentials
Memory 1GB RAM is minimum and 2GB RAM is recommended
Browser Internet Explorer v6.0+
Firefox v1.5+
Network Interface Card Suitable for communication with remote chassis
Ethernet 100 Mbps on the host network (1000 Mbps recommended)
Xgig Chassis supports 10, 100, and 1000 Mbps data rates.
Subnet All chassis within a sync group must be in the same subnet
Other 1024x768 SVGA display. We recommend a resolution setting to 1280x1024 to have better view.
Serial Port
Pre-requisite Software for
Xgig Maestro client
(included in Xgig Software USB drive)		 Microsoft Windows Installer v3.1
Microsoft .NET Framework v3.5 SP1
Microsoft Visual C++ Redistributable 2008: Service Pack 1

Listed below are the recommendation for Load Tester.

The above recommended system configurations for Xgig Maestro also applies to Load Tester. For users intending to work with large number of ports and exchange replication which will result in large number of streams/exchanges, we recommend a system with higher performance CPU:
Pentium 4 multicore and/or multi processor: clock speed 2GHz+

Listed below are the recommended system configurations for 16G FC Generator SDK.

OS (32-bit and 64-bit) Windows 7 Professional and Enterprise with Service Pack 1
Windows 8.1 Professional or Enterprise
Windows Server 2008 Standard or Enterprise with Service Pack 2
Windows Server 2008 R2 Standard or Enterprise with Service Pack 1
Compiler Microsoft Visual Studio 2008
Memory 512MB RAM is minimum and 1GB RAM is recommended
Network Interface Card Suitable for communication with remote chassis
Ethernet 100 Mbps on the host network (1000 Mbps recommended)
Xgig Chassis supports 10, 100, and 1000 Mbps data rates.

Top of Page

Client Installation

Xgig Maestro Installation

  1. Insert Xgig Software USB drive into your computer.

  2. In the Windows Explorer, run the autorun.exe at the root of the USB drive.

  3. Install Xgig Maestro by clicking on "Install Maestro", then follow the steps in the Install Wizard to load the program to the location of your choosing or use the default.

    Default Installation Directory: C:\Program Files\Viavi\Xgig Maestro

Xgig 16G FC Generator SDK Installation

  1. Insert Xgig Software USB drive into your PC.

  2. In the Windows Explorer, run the autorun.exe at the root of the USB drive

  3. Click "Install Generator SDK".

  4. Click "Install FC SDK".

  5. Follow the steps in the Install Wizard to load the program to a location you choose, or accept the default:
    Default Installation Directory: C:\Program Files\Viavi\Xgig FC Generator SDK

  6. When the installation is complete, you are prompted to click the Finish button on the setup default.

  7. Inside the "Xgig FC Generator SDK" folder, you can find help file, header file, library files and Visual Studio workspace example.

  8. Buildable sample source code is included in the "\Xgig FC Generator SDK\FCG_ExamplClient\FCG_Example.sln".
    The default project contains the simple example "FCG_Example.cpp".

    To use the other script examples, remove FCG_Example.cpp from the example project,
    and add the desired source file "FCG_InitiatorExample.cpp" or "FCG_FabricEmulatorExample.cpp".
    The header files are automatically included, and do not need to be added.

    For additional information on the example project, see the Sample Project Files topic in SDK Help.

Xgig SAS/SATA SDK Installation

  1. Insert Xgig Software USB drive into your PC.

  2. Click "Install Generator SDK".

  3. Click "Install SAS/SATA SDK".

  4. Follow the steps in the Install Wizard to load the program to the location of your choosing or use the default.
    Default Installation Directory: C:\Program Files\Viavi\Xgig SAS Generator SDK

  5. Buildable sample source code is included in the "C:\Program Files\Viavi\Xgig SAS Generator SDK\Programming\VisualC" folder for Visual Studio 2005/2008 and "C:\Program Files\Viavi\Xgig SAS Generator SDK\Programming\BorlandBuilder" for Borland C++ Builder

  6. The sample code includes the discoverTester.cpp file which has two methods, discoverXgig() and discoverLegacyMonarch(), that show how to discover either legacy Monarch Passport or Xgig SAS/SATA Generator systems. Although this release of the Viavi SAS/SATA Generator does not support legacy Monarch Passport systems, this code may be a useful reference for porting discovery code from legacy Monarch to the Xgig system.

    The Borland sample code opens the tester, requests the FPGA version from the tester then outputs the bit file version found to be running on your tester.

    Two VisualC sample projects are provided:

    a) sample: This test opens the tester, requests the FPGA version from the tester then outputs the bit file version found to be running on your tester.
    b) sampleSmp: This test should be run with the tester attached to a SAS Expander device. This test opens the tester and discovers and prints SSP Target and SATA Drives using SMP API routines.

    Prior to building any of the sample programs, you should change the TESTER_NAME mnemonic to the name of your tester. The TESTER_NAME mnemonic is defined in mbs.cpp, sample.cpp, and sampleSmp.cpp.

Top of Page

Upgrading the Chassis

In order to use Maestro, the chassis needs to be updated to the latest system version. Use one of the following methods to upgrade the chassis:

Upgrading chassis from client software applications

  1. Install the Xgig Maestro client software on your PC.

  2. Launch the Xgig Maestro application.

  3. Press Port Selection and Domain Setup button in Xgig Maestro.

  4. In the Port Selection and Domain Setup window, select the Sync Group containing the chassis you need to upgrade.

    a) If the sync group has a compatible Appkit software, all chassis in the sync group will appear. Right-click on the space under the Viavi Xgig label of one of the chassis and select Upgrade Sync Group with latest System/Appkit...” option from the context menu to start the chassis software upgrade.
    b) If the sync group has old and incompatible Appkit software, an Upgrade button is available under the message informing of its incompatibility with the installed client software. Press the Upgrade button to start the chassis software upgrade. Alternately, you can click on the hyperlink of the master chassis of the sync group (i.e. http://Chassis_IP_Address) and use the Xgig Web Utility upgrade method shown below to upgrade the sync group.

  5. If the chassis selected for upgrade is part of a Sync Group that includes multiple chassis, all chassis in the Sync Group will be upgraded.

  6. You will receive a message confirming the upgrade versions. Press Yes to confirm.

  7. The Upgrade Chassis window appears showing the upgrade status of each chassis in the sync group.

  8. A Refresh Discovery window dialog appears upon the completion of the upgrade process.

    a) Press OK to close the Refresh Discovery window dialog.
    b) Press Close to close the Upgrade Chassis window.
    c) Press Close to close the Port Selection and Domain Setup window.

  9. Once the sync group is rebooted, it is ready to be used.

    Note:
    a) The upgrade process above will launch its own FTP server to upgrade the chassis. Make sure your PC is not running any FTP server software. You will receive a warning message when this happens. Just close your running FTP server then proceed with upgrading the chassis.
    b) If the upgrade of the chassis from the client application fails for any reason, use the Web Utility upgrading procedure shown below to upgrade the chassis.

Upgrading via Xgig Web Utility (requires an FTP server)

  1. Install the Xgig Maestro client software on your PC.

  2. Copy the contents of the .../Xgig Maestro/Chassis folder in the Xgig Maestro installation directory on your PC to the FTP server root or default login folder.

  3. Proceed to the section "Upgrading the Xgig System Image and Application Image Software" in the Xgig Family Hardware Guide to perform an upgrade using the Xgig Web Utility.

  4. Once the sync group is rebooted, it is ready to be used.

Top of Page

Compatibility and Interoperability

Software Compatibility

  1. The following software can co-exist on the same System:
    Xgig-Maestro, Xgig-Analyzer, GTX-G, GTX-J, GTX-B, Xgig 10G BERT, Bus Doctor Plus, PacketMaker, Surveyor

  2. The following is a list of released clients, compatible application kits and system versions:

    Client Version
    Application Kit
    OS Version
    Notes
    Xgig Maestro 1.1.0 App Kit 2.0.9362 System 2.0.4  
    Xgig Maestro 1.1.1 App Kit 2.0.11817 System 2.0.6  
    Xgig Maestro 1.2.0 App Kit 2.1.15504 System 2.1.0  
    Xgig Maestro 1.3.0 App Kit 2.5.0.01344 System 2.1.10  
    Xgig Maestro 1.4.0 App Kit 2.5.0.26609 System 2.5.6  
    Xgig Maestro 2.0.0 App Kit 3.0.0.37179 System 2.5.12  
    Xgig Maestro 2.6.0 App Kit 3.1.1.46479 System 3.1.0  
    Xgig Maestro 2.7.0 App Kit 3.5.1.56443 System 3.1.4  
    Xgig Maestro 2.7.1 App Kit 3.6.1.63992 System 3.1.4  
    Xgig Maestro 2.8.0 App Kit 3.7.0.65375 System 3.1.4  
    Xgig Maestro 2.9.0 App Kit 4.1.0.72238 System 3.6.0  
    Xgig Maestro 2.9.0 App Kit 4.1.1.74812 System 3.6.0 Patch Release
    Xgig Maestro 3.0.0 App Kit 7.0.0.77387 System 3.6.0  
    Xgig Maestro 3.0.1 App Kit 7.0.1.79303 System 4.0.0 Patch Release
    Xgig Maestro 3.0.2 App Kit 7.2.1.81215 System 4.0.0 Patch Release
    Xgig Maestro 4.0.0 App Kit 7.1.0.78335 System 3.6.0  
    Xgig Maestro 4.0.1 App Kit 7.1.1.83967 System 4.1.0 Patch Release
    Xgig Maestro 4.0.2 App Kit 7.1.2.88171 System 4.1.2 Patch Release
    Xgig Maestro 4.6.1 App Kit 7.5.1.85489 System 4.1.2 Early Adopter Release
    Xgig Maestro 4.7.0 App Kit 7.6.0.89447 System 4.1.2 Early Adopter Release
    Xgig Maestro 4.8.0 App Kit 7.8.0.90010 System 4.1.2  
    Xgig Maestro 5.0.0 App Kit 8.0.0.92477 System 4.1.2  
    Xgig Maestro 5.1.0 App Kit 8.1.0.94144 System 4.1.2  
    Xgig Maestro 5.1.1 App Kit 8.1.1.95447 System 4.1.2 Patch Release
    Xgig Maestro 5.2.0 App Kit 8.2.0.98503 System 5.0.0  
    Xgig Maestro 5.2.1 App Kit 8.2.1.99302 System 5.0.0 Patch Release
    Xgig Maestro 5.2.2 App Kit 8.2.3.101053 System 5.0.0 Patch Release
    Xgig Maestro 6.0.0 App Kit 8.3.0.102430 System 5.0.0  
    Xgig Maestro 6.1.0 App Kit 8.4.0.105886 System 5.0.0 Early Adopter Release
    Xgig Maestro 6.1.0 App Kit 8.4.0.109039 System 5.0.2 Early Adopter 2 Release
    Xgig Maestro 6.1.0 App Kit 8.5.0.110887 System 5.0.2  
    Xgig Maestro 6.1.1 App Kit 8.6.0.113417 System 5.0.2, System 5000.0.9 Patch Release
    Xgig Maestro 6.1.2 App Kit 8.6.1.113417 System 5.0.2, System 5000.0.9 Patch Release - 10G IO blade can be partially licensed.
    Xgig Maestro 6.1.3 App Kit 8.6.2.114646 System 5.0.2, System 5000.0.9 Patch Release
    Xgig Maestro 6.1.4 App Kit 8.6.4.115713 System 5.0.2, System 5000.0.9 Patch Release
    Xgig Maestro 6.2.0 App Kit 8.7.0.116899 System 5.0.2, System 5000.0.9 Early Adopter for 16G Jammer and LT
    Xgig Maestro 6.2.1 App Kit 8.8.1.118328 System 5.0.2, System 5000.0.9 Patch Release for 16G Jammer and LT
    Xgig Maestro 6.2.2 App Kit 8.8.2.119804 System 5.0.2, System 5000.0.9 Patch Release
    Xgig Maestro 6.2.3 App Kit 8.8.3.120877 System 5.0.2, System 5000.0.9 Early Adopter for 12G Generator and Jammer
    Xgig Maestro 6.2.4 App Kit 8.8.4.121172 System 5.0.2, System 5000.0.9 Early Adopter 2 for 12G Generator and Jammer
    Xgig Maestro 6.2.5 App Kit 8.8.5.121571 System 5.0.2, System 5000.0.9 Early Adopter 3 for 12G Jammer
    Xgig Maestro 6.3.0 App Kit 8.9.0.122978 System 5.0.2, System 5000.0.9  
    Xgig Maestro 6.4.0 App Kit 8.10.0.126474 System 5.0.2, System 5000.0.9, System 1000.0.5 Early Adopter for Xgig1000
    Xgig Maestro 7.0.0 App Kit 9.0.0.126905 System 5.0.2, System 5000.0.9, System 1000.0.7 12G SAS and 16G FC Feature Release. Early Adopter for Xgig1000
    Xgig Maestro 7.0.1 App Kit 9.0.0.126905 System 5.0.2, System 5000.0.9, System 1000.0.7 Early Evaluator Release 1
    Xgig Maestro 7.0.1 App Kit 9.0.2.126914 System 5.0.2, System 5000.0.9, System 1000.0.7 Early Evaluator Release 2
    Xgig Maestro 7.1.0 App Kit 9.1.0.130715 System 5.0.2, System 5000.0.9, System 1000.0.7  
    Xgig Maestro 7.1.1 App Kit 9.1.1.131151 System 5.0.2, System 5000.0.9, System 1000.0.7 Patch Release
    Xgig Maestro 7.2.0 App Kit 9.2.0.131861 System 5.0.2, System 5000.0.9, System 1000.0.7 Pre-Release
    Xgig Maestro 7.1.2 App Kit 9.1.2.131731 System 5.0.2, System 5000.0.9, System 1000.0.7 Patch Release
    Xgig Maestro 7.1.3 App Kit 9.1.3.133217 System 5.0.2, System 5000.0.9, System 1000.0.7 Patch Release
    Xgig Maestro 7.2.0 App Kit 9.2.0.133847 System 5.0.2, System 5000.0.9, System 1000.0.7 Pre-Release2
    Xgig Maestro 7.2.0 App Kit 9.2.0.135803 System 5.1.2, System 5000.0.25, System 1000.0.19  
    Xgig Maestro 7.3.0 App Kit 9.3.0.136241 System 5.1.2, System 5000.0.25, System 1000.0.19 16G FC Generator release
    Xgig Maestro 7.3.1 App Kit 9.3.1.137327 System 5.1.4, System 5000.0.27, System 1000.0.21 Patch Release
    Xgig Maestro 7.5.0 App Kit 9.5.0.139872 System 5.1.6, System 5000.0.29, System 1000.0.23 10/16G Xgig1000 release
    Xgig Maestro 7.5.1 App Kit 9.5.1.140112 System 5.1.6, System 5000.0.29, System 1000.0.23 10/16G Xgig1000 4-port version release.
    Xgig Maestro 7.5.2 App Kit 9.5.2.140207 System 5.1.6, System 5000.0.29, System 1000.0.23 Patch Release
    Xgig Maestro 7.5.3 App Kit 9.5.3.141920 System 5.1.6, System 5000.0.29, System 1000.0.23 Early Evaluator 4
    Xgig Maestro 7.5.3 App Kit 9.5.3.142985 System 5.1.6, System 5000.0.29, System 1000.0.23 Early Evaluator 6
    Xgig Maestro 7.5.3 App Kit 9.5.3.143263 System 5.1.6, System 5000.0.29, System 1000.0.23 Patch Release
    Xgig Maestro 7.6.0 App Kit 9.6.0.145950 System 5.1.6, System 5000.0.29, System 1000.0.23  
    Xgig Maestro 7.7.0 App Kit 9.7.0.148138 System 5.1.6, System 5000.0.29, System 1000.0.23 12G SAS Optical Support for Jammer & Gen, 10GE JA hybrid support, 12G SAS TX training for Jammer
    Xgig Maestro 7.7.1 App Kit 9.7.1.150235 System 5.1.6, System 5000.0.29, System 1000.0.23 Auto-Tune for G-A and J-A. New 12G SAS CLE configurations
    Xgig Maestro 7.8.0 App Kit 9.8.0.150417 System 5.1.6, System 5000.0.29, System 1000.0.29 Xgig1000 Mark2 motherboard and 16G FC FEC Jammer
    Xgig Maestro 7.8.1 App Kit 10.0.0.152368 System 5.1.6, System 5000.0.29, System 1000.0.29 NVMe Analyzer support
    Xgig Maestro 7.8.5 App Kit 9.8.1.153224 System 5.1.6, System 5000.0.29, System 1000.0.31 Patch Release
    Xgig Maestro 7.8.2 App Kit 10.0.1.153504 System 5.1.6, System 5000.0.29, System 1000.0.31 NVMe Analyzer Patch support
    Xgig Maestro 7.8.6 App Kit 9.8.2.153663 System 5.1.6, System 5000.0.29, System 1000.0.31 Patch Release
    Xgig Maestro 7.8.7 App Kit 9.9.0.154077 System 5.1.6, System 5000.0.29, System 1000.0.31 Patch Release
    Xgig Maestro 7.8.3 App Kit 10.0.2.154180 System 5.1.6, System 5000.0.29, System 1000.0.31 NVMe Analyzer Patch support
    Xgig Maestro 7.8.8 App Kit 10.0.3.155273 System 5.1.6, System 5000.0.29, System 1000.0.31 NVMe Analyzer Patch support
    Xgig Maestro 7.9.0 App Kit 10.1.0.156106 System 5.1.6, System 5000.0.29, System 1000.0.31 Pre-release for LT Multicast/Broadcast support
    Xgig Maestro 7.9.0 App Kit 10.1.0.156888 System 5.1.6, System 5000.0.29, System 1000.0.31 Pre-release #2 for LT Multicast/Broadcast support
    Xgig Maestro 7.9.0 App Kit 10.1.0.158188 System 5.1.6, System 5000.0.29, System 1000.0.31 Pre-release for LT Clock Sync support
    Xgig Maestro 7.9.0 App Kit 10.1.0.159477 System 5.1.6, System 5000.0.29, System 1000.0.31  
    Xgig Maestro 7.9.1 App Kit 10.1.1.161785 System 5.1.6, System 5000.0.41, System 1000.0.43 Patch Release
    Xgig Maestro 8.0.0 App Kit 10.3.0.162969 System 5.1.6, System 5000.0.41, System 1000.0.43 PCIe Jammer - Gen1 and 2
    Xgig Maestro 8.0.1 App Kit 10.3.1.164789 System 5.1.6, System 5000.0.41, System 1000.0.43 PCIe Jammer Patch Release 1
    Xgig Maestro 8.0.2 App Kit 10.3.2.166560 System 5.1.6, System 5000.0.41, System 1000.0.43 PCIe Jammer Patch Release 2
    Xgig Maestro 8.1.0 App Kit 10.4.0.167983 System 5.1.6, System 5000.0.41, System 1000.0.43 Pre-release for LT Clock Sync fix
    Xgig Maestro 8.1.0 App Kit 10.4.0.168685 System 5.1.6, System 5000.0.41, System 1000.1.3 Feature Release
    Xgig Maestro 8.1.1 App Kit 10.4.1.169175 System 5.1.6, System 5000.0.41, System 1000.1.3 Patch Release

Hardware Compatibility

  1. Xgig Maestro software does *NOT* support the GTX BERT, GTX Jammer Card(s) and Monarch Card.

Top of Page

Known Issues

NOTE:
If a Windows XP host PC has TREND Micro anti-virus software installed it might “blue screen” when running the new USB software interface application or locking CLE ports. This is not our bug. Please contact your IT department or TREND Micro’s support team to get a patch of the anti-virus software for the host PC system.

Xgig SAS/SATA Generator

  • General

    1. The generator does not support buffer wrapping in this release. If a command reaches the maximum buffer size, it does not wrap to offset zero. As a result, write operations may not write the correct data to the device and read operations may not complete with the expected data in the receive buffer. To workaround this problem, you may use the dmarst() API routines to reset the appropriate buffer pointer back to zero before issuing read or write commands. You may also use the get_g_info(“rd_ptr”) and get_g_info(“wrt_ptr”) routines to query the generator for the current buffer pointers. You need to make sure that the buffer space (from the current pointer to the end of buffer) is enough for the next write/read operation. You may use the get_g_info(“bufsz”) routine to query the generator for the current buffer size.By default, the generator uses 1 Megabyte each of the Transmit and Receive buffers. You can increase the size of the buffer using the resize_buf() routine. However, no wrapping at the end of the buffer will still occur when the maximum buffer size is reached.
    2. Generator software may not set an offset into the receive buffer that is not dword-aligned. If it does, the lowest bits will be ignored by the hardware, and it will behave as if the lowest 2 bits of the offset were 0's.
      For example, the software sets the offset to 0x03, hardware will interpret that as 0x00.
    3. If a SATA device starts to send a frame too soon after speed negotiation has finished, the generator will miss the frame and fail to send R_IP and the R_OK/R_Error primitives.
    4. When running the generator in command queuing mode (after calling cmdque_mode(CMDQUE_AUTO) or cmdque_mode(CMDQUE_STACK) and before calling cmdque_mode(CMDQUE_SINGLE) to return to non-queued mode), you should not issue SCSI IO commands to more than one SAS Target when the generator is connected to an expander device.
    5. The generator may require a power cycle when switching between SAS and SATA devices due to differences in electrical specifications.
    6. The generator may fail speed negotiation on PHY or link resets with certain drives if the set_speed or set_speed_ex are set to autodetect. If this happens, use set_speed or set_speed_ex options to negotiate to a specific speed rather than autodetect and re-try the reset sequence.
    7. The generator will restart OOB and Speed Negation if it fails to receive Identify frame from the DUT due to problems with the receive clock immediately after long periods DC Idle
    8. When executing from compiled test, speed negotiation may not follow the parameters used in API "set_speed_ex" for the first few attempts. Reset will attempt speed negotiation for all windows and use default phy capabilities bits (G1woSSC, G2woSSC, G3woSSC).  After these attempts, reset should successfully execute based on the parameters supplied.
    9. The SATA generator is not officially supported by the 12G SAS blade and Xgig1000 chassis. When the generator is running on the 12G SAS blade or Xgig1000 chassis, and connecting to a SATA drive at 6Gbps, some SATA write commands issued by Generator may fail. The SATA drive may return CRC error.
    10. The Trace To Script Tool does not support Analyzer traces captured with non-default port names.
    11. The Tcl API is a synchronized API. The Tcl GUI is not responding when the Tcl script is running. Users are suggested to run separate short Tcl scripts instead of running a long, time-consuming Tcl script.

  • 12G SAS Generator

    1. In order to use previously saved auto tune profile after unlock/relock Generator port, the user must set the Generator COEFFICIENT to 2 by calling the API: set_tester_modes(0x78, 0x02);
    2. "Auto Tuning" supports configuration "#35 G-A", "#41 G-J-A,A", "#49 G-A,G,G" & "#55 G-A,G-A".
    3. The auto-tuning will normally take about 3 to 8 hours. If it takes more than 24 hours, stop the auto-tuning manually and save the configuration. If the saved configuration does not improve the link quality, please call the tech-support. We strongly recommend that all the components in the setup are 12G rated.
    4. When the user is using a 12G SAS Wide-Port Blade on a Xgig5000 chassis with link configuration #51 G-A, G-A selected, locking port 1 as Generator will fail and the user must reboot the chassis.
    5. When using USB connection, user may encounter “Failed to initialize the connection” pop up and missing Link button on X5K 12G blades in Discovery window. This can occur when USB mode is manually turned off, and Ethernet cable is not connected to chassis. To resolve the issue, please turn on the USB Direct Connect mode.

Xgig BERT/Jammer

  • General

    1. After immediately locking a port pair as a SAS/SATA Jammer, OOB initialization may need to take place twice before the link comes up.
    2. In case the BERT or Jammer lose receiving synchronization with your device (as may be indicated by "CDR loss of lock" on the GUI), the "Force CDR re-lock" option in the context menu of the main view may help to sync up with the device. Also, if CDR loss of lock occurs during a test, the Signal LED cell will be highlighted with yellow. This option is only available on the 8Gbps blade.

  • 6G SAS/SATA Jammer

    1. On some devices, SAS/SATA Jammer may fail to link up to lower speed using Advanced SAS speed negotiation settings.

  • 16G FC Jammer

    1. Duplicate Frame Jam may corrupt frames if too many duplications happen in a short period of time
    2. When FEC mode sets to Auto or On, somtimes the link between two FEC devices is not established properly. Try to make FEC mode Off and back to Auto or On again to make the link up.

  • 12G SAS Jammer

    1. Jammer doesn't work with SATA devices with direct connection.
    2. If auto-tuning takes more than 24 hours, stop the auto-tuning manually and save the configuration. If the saved configuration does not improve the link quality, please call the tech-support. We strongly recommend that all the components in the setup are 12G rated.
    3. When the device recovers from lower power state, Jammer may not pass ALIGN properly after forwarding COMWAKE.

  • PCIe Jammer

    1. For Disparity Error and Code Violation Error Injection, the error may occur again after inserting the error on right position.
    2. Somtimes, Disparity Error may not occur depending on 10B code.
    3. Jammer does not support Gen3 OS Arm/Trigger/Jam yet
    4. If Arm or Trigger condition is set after 6th row for TLP, jamming may not occur at the right position.

Xgig Load Tester

  • General

    1. Locking ports from an Ethernet connected chassis and a USB Direct connection enabled chassis in the same Load Tester session will result in Unknown State for a set of the locked ports. At the moment, You can only lock ports for either the Ethernet connected chassis or USB Direct connection enabled chassis in the same Load Tester session.
    2. Locking of ports using the Xgig 5K chassis after an upgrade would sometimes result to an error. Please reboot the chassis and try to lock the ports again.
    3. Stop/Start a LT test may see one of the LT ports sends traffic at a later time and thus results in less data frame transmitted. To avoid this problem, please use Pause/Resume instead of Stop test. If the issue have occurred, please release and re-lock LT port.
    4. Save/load of User defined payload in a configuration is not supported. Upon saving such a configuration, Load Tester will notify user-defined payload cannot be saved. Continue by clicking Ok to dismiss the prompt. The rest of the configuration are successfully saved.
    5. When using burst mode in a traffic pattern configuration and the burst length value exceeds the maximum value allowed for that configuration (calculated based on the Inter-Frame Gap and Inter-Burst Gap), the system will reduce the burst length value in order for the configuration to run successfully. This automatic change in value will be reflected in the Load Tester log.
    6. When the Load Tester is in the Offline state it sends the OLS primitive sequence ordered set. Some switches respond to receiving OLS by toggling their Optical Laser, OFF then ON which could lead to disparity errors and code violations if a Load Tester user starts a test as the switch toggles the laser.
    7. While performing a test with more than 1 traffic pattern, occasionally the TX counters for traffic patterns not selected are updated much slower than the ones for traffic pattern that are selected.
    8. The RX Physical Ports summary Latency columns will show incorrect max/min/avg values for ports with streams that go between sync-groups. The RX Stream Latency columns will have valid values.
    9. Test Summary Report will be generated when a disconnection to the ports (disconnect session) occurs. When the test is stopped after a reconnection, a Test Summary Report will no longer be generated.
    10. When sending Ethernet traffic with CUSTOM payload, hardware will recalculate the checksum.
    11. In 16G FC, setting to 100% load will see a smaller actual throughput than the desired throughput.
    12. It is possible to see extra streams and negative dropped frames in RX tab after adding ports or changing to extended mode. They are correctly updated once the test is started.
    13. Disparity and data break errors will be seen in 8G LT trace when LR is sent. Try to always enable Tx/Rx credits for all ports if possible.
    14. Combining oversized payload and enabling "None" option of FC/FCOE EOF in the EOF error injection under FC traffic pattern running on 16G ports may result in slightly greater-than-expected throughput, which may result in incorrect RX throughput displayed.
    15. Actual throughput when set to "Random" payload may result in slightly greater-than-expected Tx line rate.
    16. Creating large number of exchange replication may cause for LoadTester to run slow or not respond. In that case, please disable Test Summary Report and/or try to reduce the number of exchange replication.
    17. Creating large number of physical and virtual ports may cause the Ports Selection tab to take a longer time to display the ports available. This may make Maestro seems not responding. In that case, please wait for a while and Maestro will recover. If the GUI become too slow, please try to reduce the number of physical and/or virtual ports created.
    18. Compile and run LT API with "#include <list>" in Visual Studio C++ and project configuration set to “Debug” may cause a Heap Corruption error. Please be advised to use project configuration “Release” when using C++ list.”
    19. Load Tester VS2005 sample project is not yet supported to build in 64-bit. User may get the following compilation error - “fatal error C1007: unrecognized flag '-typedil' in 'p2' LINK : fatal error LNK1257: code generation failed “
    20. When compiling VS2005 sample project using 32 bit library, user may encounter this link error - “Fatal error LNK1103: debugging information corrupt”.
      According to MSDN, this VS bug can be resolved by installing VS2005 Service Pack 1 and apply hotfix KB949009. Please follow the instructions in https://support.microsoft.com/en-us/kb/949009

  • Load Tester Extended Feature Mode

    1. There are situations when 10G Load Tester ports cannot be switched between regular and extended feature modes. These situations include after doing a port configuration change, loading a Tcl script and reconnecting to an offline session.

      In such circumstances, a message will be displayed when you enable or disable extended feature. "An error has occurred processing the request. Error Message: Port Feature set changing has been disabled and will not be available for this Load Tester session. This could be caused by changing a parameter in the Port Configuration tabs, running an in-session Tcl script, or reconnecting to an offline session."

      To change mode in these situations, first release ports and then re-lock ports.

      Reminder: Change to the correct mode (regular or extended) before changing the port configurations.

  • Load Tester Port Capture Feature

    1. Captures made before a test has been started will not be time synchronized across ports.
    2. CRCs are incorrect on the captured TX packets - actual TX packets have correct CRCs.
    3. It may take a while for the captured trace to be processed and launched. During this time, you may see error messages in the console. When the console closes, the trace will be launched successfully.
    4. On the X1K and X5K chassis, 10G captures made with "Link Services Tx/Rx" mode may fail to launch after clicking the Trace View icon. Trace View will report a "CFILE_FILE_NOT_FOUND" error. This suggests the capture is corrupted. In order to successfully capture and view 10G link services frames, please bring the ports offline, start a new capture and use the Link Services buttons in Link Services tab to perform login instead of using the Start Test button.
    5. During Port Capture processing, the user may experience connectivity issue and long capture processing time if there are frequent active logging of messages. If this occurs, please try disabling the active logging feature. The logs will remain collected and should appear when active logging is re-enabled.

  • Load Tester API Shell

    1. Loading Tcl scripts that manages ports on their own (calling lt_xxx functions inside) within an active Load Tester session, either from the “Open Load Tester TCL script” menu item or the API Shell, will interfere with the GUI ports and cause unpredictable results, and is therefore highly discouraged.
    2. There are some Load Tester features that we recommend users to use entirely either GUI or APIs . Using both may cause out of sync updates even after GUI refresh and result in confusion. These features include Single Frame TX/RX and Port Capture.

  • Load Tester Multicast/Broadcast Feature

    1. Multicast Rx stream number and index are not updated correctly if a port belongs to more than 1 destination group. But the actual number of streams created and traffic exchanged are correct.

Xgig Delay Emulator

  1. Sometimes locking Delay Emulator port fails with error message. In this case, please try to lock again.
  2. Delay Emulator only passes frames and Idles. Order sets won't be passed through Delay Emulator.
  3. Changing the real time value for delay or drop rate for queue 2 and above won't be set properly. Try to select the queue row first and then change the value.

Xgig Target Emulator

  1. SATA TE - Auto speed negotiation for SATA is not supported. Only the highest speed will be attempted for speed negotiation. Even if lower speeds are supported, they won't be used.
  2. SATA TE - It is not likely but possible that while locking a TE port, it shows up as "Disconnected". Please reboot chassis and the port will be good to use again
  3. SATA TE - When using Generator with TE, reset may timeout with error "No Identify frame received". When this happens, please re-lock the port and try again.

Top of Page

Previous Releases

Click here to view the history of previous releases.

Top of Page

Support

Online Support

Web: www.viavisolutions.com/snt

Support and Maintenance

If you require technical assistance
Voice: +1 844 GO VIAVI (1-844-468-4284)
E-Mail: techsupport-snt@viavisolutions.com (Preferred method of communication)

For the latest TAC information, go to www.viavisolutions.com/TechnicalAssistanceInfo.

Top of Page
Copyright 2016 © Viavi Solutions Inc. All rights reserved

Viavi and the Viavi logo are trademarks of Viavi Solutions Inc. (Viavi)
Microsoft Windows is a registered trademark of Microsoft Corporation.
Acrobat and the Acrobat logo are trademarks of Adobe Systems Incorporated.
Viavi reserves the right to revise these specifications without notice or penalty.