Overview

This Readme details information regarding the latest features provided in this release with known issues and other helpful information. Please review the Feature Enhancements and Defect Fixes as well as the Known Issues sections for more details.

For full instructions on using Xgig Analyzer, please refer to the Xgig Analyzer User's Guide and other documents included on the product's released media.

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

Feature Enhancements and Defect Fixes

Feature Enhancements:

This XgigA - 7.3.1 patch release includes new firmware to fix issues found with 25G Ethernet and 32G Fibre Channel protocol board.

PCIe specific features:

A new option to capture traces with compression of TS1 and TS2 events.

The Xgig can capture the PERST# and CLKREQ# signal transitions and produce the L1 substates in the LTSSM.

The Devices And Addresses dialog now draws the PCIe topology in the Topology tab.

New equalization presets are available for the SFF 8639 interposer.

Detects and support the NVMe Dual Port configuration on the SFF 8639, when the DualPortEn# pin is low.

Support the new Right-angle and Left-angle interposers.

First cut of the PCIe Tuning Wizard in TraceControl allowing to change the Equalization settings manually and semi-automatically.

NVMe over ROCE/ROCEv2/IBXoE is now decoded when the following TraceView menu is checked:
View/Decode Switches/RDMA Payload Interpretation/NVMe Protocol

Other new features:

Xgig-Expert can now skip optional Ethernet headers (like the VnTag) and Fibre Channel headers when present and produce proper metrics.

TraceView now has a new Quick Find "Not" option to find anything that doesn't match the criterions.

TraceView now has a new Quick Find "rgn" operator to search for address ranges.

New 12G SAS preset for link config#32.

Supporting 32Gbps Fibre Channel and 25Gbps Ethernet protocol analyzers.

NOTE: Please see the Constraints section for any limitations.

8-stage Advanced Triggering on all speeds and protocols.
With proper licenses, any port pairs in the chassis can be used either as Fibre Channel or as Gigabit Ethernet personality.
16GB of capture memory per port.

Decode and other Improvements

For a complete list of decode improvements, please read the "CurrentProtocolVersions.txt" file. This file is located in the following folder: Xgig Analyzer install location \Viavi\XgigAnalyzer\CurrentProtocols\. Highlighted for this release include:

TraceView has Side A/B and "Exchange View" replaced by Downstream/Upstream and "Transaction View".
Added the option to display DWORDs without spaces between the bytes, and byte-swapped or not ...
When no data is available for LTSSM processing a pop up dialog will indicate in such situation.
Improved handling of CLKREQ during LTSSM power management.
TCG: TCG Storage Architecture Core Specification
Implemented:
http://www.trustedcomputinggroup.org/files/resource_files/80211A55-1A4B-B294-D0C8041451A58524/Storage_Architecture_Core_Spec_v2%2000_r2%2000-Final%20(2).pdf November 4, 2011
http://www.trustedcomputinggroup.org/files/static_page_files/9399002E-1A4B-B294-D03DB5A23BCB229C/Pyrite_SSC_v1.00_r1.09_public_draft.pdf February 16, 2015
http://www.trustedcomputinggroup.org/files/resource_files/B15EDC5D-1A4B-B294-D09D63D980D27808/TCG_Storage-Opal_Feature_Set_Single_User_Mode_v1%2000_r1%2000-Final.pdf February 24, 2012
http://www.trustedcomputinggroup.org/files/static_page_files/B157EB00-1A4B-B294-D0FD3CA9345FFCD4/TCG_Storage-Opal_Feature_Set-Additional_DataStore_Tables_v1_00_r1_00_Final.pdf February 24, 2012
Specs implemented in prior releases:
http://www.trustedcomputinggroup.org/files/static_page_files/9FE14508-1D09-3519-AD7D21A695E9B8EE/Opal_SSC_1.00_rev3.00-Final.pdf
TCG_SWG_SSC_Enterprise_DRAFT-rev 92.pdf June 10 2008

NC-SI/NC-SI over MCTP: implemented fully:
http://www.dmtf.org/sites/default/files/standards/documents/DSP0222_1.0.1.pdf 2013-01-24
http://www.dmtf.org/sites/default/files/standards/documents/DSP2037_1.0.0.pdf 2014-02-20
http://dmtf.org/sites/default/files/standards/documents/DSP0261_1.0.0.pdf 2013-08-22

ECN for IP: Implemented fully:
https://tools.ietf.org/html/rfc3168 Sept 2001
https://www.rfc-editor.org/rfc/rfc2474.txt 1998

MCTP: Implemented fully:
http://www.dmtf.org/sites/default/files/standards/documents/DSP0236_1.0.0.pdf 28 July 2009
http://dmtf.org/sites/default/files/standards/documents/DSP0238_1.0.2.pdf 2014-12-07
http://www.dmtf.org/sites/default/files/standards/documents/DSP0239_1.0.0.pdf 28 July 2009

NVMe 1.2: implemented fully:
http://nvmexpress.org/wp-content/uploads/NVM_Express_1_2_Gold_20141209.pdf Nov 3 2014

ECN for IP: Implemented fully
https://tools.ietf.org/html/rfc3168 Sept 2001
https://www.rfc-editor.org/rfc/rfc2474.txt 1998

ZAC: implemented except
6.3 IDENTIFY DEVICE data log (Log Address 30h) (we don't decode the log pages themselves)
http://www.t13.org/Documents/UploadedDocuments/docs2015/f14183r5-ZAC_Zone_State_Machine_et_aliae.pdf 3 April 2015

ZBC: implemented fully:
http://www.t10.org/cgi-bin/ac.pl?t=f&f=zbc-r03.pdf November 12, 2014

SMC-3: implemented fully:
http://www.t10.org/cgi-bin/ac.pl?t=f&f=smc3r16.pdf 11 Jan 2012

L1 PM Substates with CLKREQ: implemented fully:
https://www.pcisig.com/specifications/pciexpress/specifications/ECN_L1_PM_Substates_with_CLKREQ_31_May_2013_Rev10a.pdf 31 May 2013

Defect Fixes:

The following bugs have been fixed for this release.

Xgig-Expert needs to support VN Tagging.
Issue with several RCVR EQ sub-states were mis-identified when TS1/2 were compressed.
Problem with NOT trigger for PCIe register has been corrected.
Delta Calculator display is not a valid time value.
Missed capturing the 2CRCs before the EOF after the truncation point in 40G Ethernet buffer.
LTSSM GUI: It is not possible to resize it to a usable size on a 900-pixel high laptop.
Failed at detecting reversed polarity for certain PCIe Gen 2 x 1 traces.
On a clean install, the Synchronize Grids button in TraceView was disabled, it is enabled now.
Saved trace which used Chinese Windows OS with Chinese name cannot be opened with US Windows OS.
Xgig-Expert gave incorrect analysis for Response Code 72h for Check Condition frame.
Xgig-TraceView's Quick Find hangs on Reverse search.

Top of Page

System Requirements

Listed below are the basics and recommended system configurations for Xgig Analyzer to achieve optimal performance.

Basic Requirements:

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
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 and use the same TCP port number.
Browser	Internet Explorer v6.0+ Firefox v1.5+
Media	USB port
Other	1024x768 SVGA Serial data port or use USB-RS232 adapter Standard type A to type B USB cable for Xgig applications using USB functions USB-RS232 adapter for using the floating license serial dongle with Xgig1000 and Xgig5000 chassis
Pre-requisite Software for Xgig Analyzer client (included on product's released media)	Microsoft Windows Installer 3.1 Microsoft .NET Framework 3.5 with Service Pack 1 Microsoft Visual C++ Redistributable 2008 with Service Pack 1 Visual Basic Power Packs version 1.2

For use with sync groups of up to 16 ports:

CPU	Pentium III: clock speed 1GHz+ (Dual core recommended)
Memory	4GB RAM (8GB is recommended) If the Xgig blades have the (optional) larger memory modules installed or post capture processes such as Traffic Summary View and Exchange View are to be done, additional RAM helps optimize trace processing.
Hard Drive	80GB+ Xgig Analyzer software application requires about 500MB of disk space which includes samples of configurations and protocol traces. The Pre-Requisites - Microsoft .NET Framework and Microsoft Visual C++ Redistributable software require additional 200MB of disk space. Future trace files to be saved will require more disk space depending on the size of the captures.

The following is the recommendation of client PC for best performance

CPU	Core i5 class CPU
Memory	At least 8GB RAM with a 64-bit version of Windows. If the Xgig blades have the (optional) larger memory modules installed, additional RAM helps optimize trace processing. When Traffic Summary View and Exchange View processing are employed in standard work flow, we recommend at least 16GB of RAM installed.
Hard Drive	At least 256GB SATA3 SSD Future trace files to be saved will require more disk space depending on the size of the captures.
Monitor	1600x1200 SVGA Multi-Monitor is highly recommended

Top of Page

Previous Releases

Click here to view the history of previous releases.

Top of Page

Constraints

Following are setup, configuration, and software constraints for Xgig 7.3.1

PCIe Tuning Wizard

Saving EQ settings to the chassis will be loss at the next SW App Kit upgrade. It is best practice to save to both files on the local client PC for future uses and to the chassis for ease of access while using the current app kit.
After saving the tuned EQ settings to chassis, in order to see the new settings on the pull down list in the Lane Control tab of the Configuration Editor, it is necessary to either reboot the chassis or disconnect then reconnect the cables between the chassis and the interposer.
Tuning in USB Direct Connect mode is not supported yet.
In Dual-Link environment, EQ tuning is not supported yet.

The initial release of the Xgig1000 32Gbps FC/ 25Gbps Ethernet chassis has a few limitations :

TraceView TrafficSummaryView (TSV) is not available for ports on XG1 chassis.
Expect an extra 3 minute delay from power on to ports available for locking as compared to Xgig1000 10/16/40 chassis.
Forward Error Correction (FEC) counters are not yet supported.
Starting time sync with other chassis has not yet been calibrated - and is expected to change.
An Analog Pass-Through (APT) unit is required if Copper cables are used. It is also required for fiber optical cables if a fiberotptic tab or an optical signal splitter is not used.
4G FC speed will not be supported on this chassis.
8G FC speed is planned, but not yet available.
Starting a capture may take up to 45 seconds after you hit the Start Capture button.

The USB Direct Connection feature has a few limitations in this initial release:

Only USB 2.0 data rate is currently supported in this release.
A chassis in USB mode cannot be part of a multi-chassis sync group.
Only the Xgig Analyzer and certain Xgig Maestro SW applications are supported in this release. This means that if other Xgig Maestro SW application like Jammer is also needed for certain test configurations, the standard Ethernet connection must be used.
System and App Kit upgrading processes from the client PC are not supported through the USB Direct Connect.
System shutdown option is not available in the Discovery window.

Long Tuning Operations dialog - When using the Auto-Select Best Preset function for autotuning at 12Gbps on the 12G SAS Xgig1000 or the 12G SAS Wide blade, the system will become unresponsive during the process duration until it is finished.

Port-pair swapping - When using the Autotuning function to autotune at 12Gbps on the 12G SAS Xgig1000, the SAS Analyzer port pairs may be swapped in order to obtain better signal results. When ports are swapped, this means the traffic to ports A and B of an analyzer have been switched. The Analyzer port labels will be swapped as well. However the CLE image will not change to reflect this. Port-pair swapping is only supported on the 12G SAS Xgig1000 on CLE Configuration 41 on Analyzer ports 1 & 2.

PCIe support in TC API is not fully implemented in this release.

Since specialty drivers are not installed in the OS for the various kinds of external USB drives, please note that if an external USB drive prompts for a HW installation, it will not be usable on the Xgig chassis. Only those drives that will operate with the standard USB storage class system drivers without prompting for a HW install will operate on the chassis.

TraceView application software of version 7.3.1 can view old capture buffers and files but old versions of TraceView client software may not be able to open capture buffers or files from this version.

When a pair of ports of the dual-personality is changed to a different personality, all four ports will be shown as "Unavailable (Function changed)" in the Resource Browser of the Performance Monitor software window.

We changed the way we count and navigate physical layer Code Violations (CV) in Fibre Channel (FC) frames. Only the first of these errors is counted per frame. Capture files made with earlier versions of the Xgig Analyzer will not show the RD/CV counter. Navigation of RD/CV errors is disabled when opening these older traces.

The 6G blade should not be installed in the same chassis of a 12G blade even though the two can be in the same domain.

TDIO_API user should make sure that the Client Authentication feature is disabled. The program will fail with a message saying authentication failed if the feature is enabled. At this time there is no API to allow the user to programmatically pass in an authentication password.

In SAS/SATA traces, if the analyzer does not capture the beginning of a Primitive Sequence then that sequence will not be included in the Traffic Summary counters.

Note: When in doubt, look into the Icon column in Dword View for a cyan colored background. This indicates the beginning of a sequence. If there is no such color shading then the sequence will not be included in the TSV's counters.

Certain services on all chassis types would not be initialized on boot-up if an Ethernet link is not present on the management port. Therefore the port LED will not light up.

To fix this problem, connect an Ethernet link on the management port of the chassis (no need to reboot).

Surveyor captures of up to 2GB in size can be converted to ".tgp" (Xgig TraceView) format. If an attempt is made to convert captures larger than this, a valid capture file of the first 2GB of data will be created.

Xgig TraceView 7.3.1 supports configuration files from previous releases. However, configuration files created with Xgig TraceView of this version may not be compatible with ones in earlier releases.

Xgig Analyzer 7.3.1 software cannot be installed on a network share. It has to be installed on a local hard drive. If you install the software on a network share, the Discovery dialog will not function.

In this case, you should uninstall the software completely, and then re-install it on a local disk following the installation procedure in the Xgig Installation Guide.

Automated link creation for SAS/SATA ports will put selected wide ports into a single link and selected narrow ports into another link. These links are created when a domain is "Create and Lock". However, this feature requires 3 conditions on the links to be met and thus can be overridden when there are no suitable links found. Please refer to Xgig Analyzer User’s Guide for more information.

Top of Page

Known Issues

The following issues will be addressed in the near future:

25GE and 32G FC specifics:

There maybe problem using the chassis in the slave mode. The workaround is to use the chassis as the master chassis in a sync group.
The Create Domain button "Blink LED" crashes the chassis. You have to powercycle the chassis to recover from the crash.

Using previously released software to open a trace which was captured with this 7.3.1 has a minor issue. Quick-search operation in the forward direction of a trace file for an event that is not present in the trace would result with the process to never terminate, i.e. Find Result message of event not found won't be displayed, until some other action is taken. To overcome this issue, monitor the search progress in the histogram pane at the bottom of the Xgig Tracview window. When the indicator reaches the end, stop the search by closing the Quick Find/Filter/Hide window or start a new task.

Saving an LTSSM processed trace does not save the LTSSM data with the saving trace.

The Xgig Analyzer does not recognize the PCIe Compliance Pattern and reports it as a Primitive/OS Error.

3G traffic is not captured reliably in Auto (12/6/3G). It is recommended that users to select Auto (6/3G) option when using 3G devices.

When using Analog Pass-through on the 10G/16G Xgig1000 chassis, changing the transceiver rate might affect the traffic between host and device.

For 12G and 16G blades, buffers with large number of segments and having Trace Summary View (TSV) enabled might pose a couple of problems:

Extraction - saving all segments at once might be interrupted. Try saving only few segments at a time.
Viewing - switching rapidly between segments without waiting for Trace Summary View (TSV) to finish loading might result with overloading the server. Try waiting for the TSV loading to complete before moving to next segment.

Using Performance Monitor to change data rate for any port pair in a chassis will interrupt trace viewing or trace processing. It is strongly recommended that changing data rate for any ports should only be done via TraceControl.

Sometimes exchanges may not show frames under them after scrolling. Collapsing and re-expanding them will fix the display.

When cascading the CLEs together, making changes to their configurations before they finish initializing may result with inconsistent in the displays in the sync group discovery window. To avoid this, wait for the units to finish initializing first.

The last primitive in a wrapped capture may not be included in the FC TSV data.

With certain traffic captured, the OOB graphical display's time interval window may show a speed negotiation period that is not found in the OOB sequence. However, the OOB Sequence graph will show the correct data. Other discrepancies may also appear when viewing directly from the buffers. If this is the case then try saving the buffers to files and view it from there before contacting support.

Certain steps in maneuvering through the traces could cause the server to misbehave. The indication for this is when message windows keep showing up informing of some missing events. To correct this, close the trace then reopen in a new window. To avoid this totally, save the trace to files before working on them.

In some cases, TraceView may not show the TSV view until you manually re-size it. After enabling it in TV, user may have to manually re-size it from zero pixels.

“Go To exchange in Exchange View” option may sometimes only get you close to the Exchange you are looking for.

When capturing traces on both sides of an expander in the same domain using two blades, inaccuracies in the time stamp may occur when the capturing traces contain OOB traffic.

In order to work around this issue, the user should start the capture after links have been established. Then OOB traffic can be generated by re-initializing either link or both. Re-initialization can be accomplished by power cycling the devices including the expander, HBA, drives or drive enclosure, or by pulling and re-inserting the cables.

The following list shows potential problems which have been identified and the recommendations to avoid or correct the issues.

The Xgig-A 6.5.2/Xgig Maestro 7.5.2 and OLDER clients ARE NOT able to discover chassis with AppKit 9.6.0.145950 and NEWER. In that case, both client applications popup the error message:

Discovery cannot find 'XGIGCHASSIS-X ( w.x.y.z )'. Check the spelling and try again.
Under this scenario, you need to upgrade the client applications to Xgig-A 6.5.3/Xgig-Maestro 7.5.3 or newer. When you get that message, you can run the following command line utilities to detect the chassis connectivity:
ping CHASSIS_IP_ADDRESS
c:\program files (x86)\Viavi\Xgig Analyzer\pullremotesll.exe CHASSIS_IP_ADDRESS
If ping can connect to the chassis, and if pullremotesll.exe dumps a big XML output on the command line, it means the chassis is accessible and you should call customer support for further instructions.

If a 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.

Repeatedly canceling any kind of operations could put the server in a catch up mode. This includes opening/closing trace rapidly or canceling a save or a search operation. Avoid doing these as at the worst case, the server may lock up resulting in loss of data. Most of the time the server will recover if it is left idle for a while.

In TraceView, heavy filtering on large channel counts traces could result with displaying blanks in the DT/Port column. To overcome this, perform page down and page up again using either the keyboard or by clicking the mouse in the main events grid’s vertical scroll bar.

Moving a chassis from one subnet to another might result with unexpected behavior of the server software. To avoid this, perform a soft reboot whenever the sync group configuration is changed. This action can be done via the web interface.

Run-disconnected feature works properly when TraceControl application is closed before disconnecting the client from the server. Ports might not be unlocked if the client is disconnected from the server without closing the TraceControl application first. For example, the Ethernet cable connecting the PC or laptop to the network is removed abruptly while TraceControl application is still running. To avoid having ports in the locked state with no clients connected, always close the application before disconnect the client. In the case that the problem has already happened, try to reclaim the domain by using the same client.

For 8Gbps FC blade, when capture in scrambling mode, any unframed data on the wire would require 2-3 subsequent good frames before it would re-sync.

OOB decodes for 3Gbps data from the 3Gbps and 6Gbps blades will both follow SAS-2 specifications. However, no Begin/End markers are shown for OOB traffic captured on 3G blade.

When using Windows 2003 Server, the "Go Back" button in the Equalization Setting Result dialog box maybe non-functional. Turn off Internet Explorer Enhanced Security Configuration to make the button work. Another workaround for this issue is to right-click any where in the window and select the "Back" option instead of using the "Go Back" button on the page.

Top of Page

Compatibility & Interoperability

Software Compatibility

Client release 7.1.0 and app kit release 10.1.0 are compatible with this patch release using the regular Ethernet connection only.
Previous versions of Xgig Analyzer or any viewer/trial software versions must be uninstalled , prior to installation of Xgig 7.3.1 software. Refer to the Xgig Installation Guide for detailed instructions on installing the software.

Terminal Service Users: To install the software under a Terminal Server session, you must select Start> Settings>Control Panel>Add or Remove Programs, then click "Add New Programs", then the "USB drive" to locate the Xgig Analyzer 7.3.1 installation software to install. Otherwise, the software may not run correctly.

The following software can co-exist with Xgig Analyzer 7.3.1 on the same system: Surveyor and Xgig Maestro.

Traces captured from previous versions of Xgig are fully compatible with Xgig Analyzer 7.3.1. However, 66-bit data of previously captured 10G traces won't be displayed. This will be corrected in the near future.

Xgig Analyzer client versions 7.3.1 and server software version 10.4.1 are NOT compatible with previous client versions and theirs associated server software.

Graphical PDK version 2.3.0 is compatible with Xgig Analyzer 7.3.1.

FRunner version 4.0.1 is compatible with Xgig Analyzer 7.3.1.

NOTE: FRunner software application version 3.7.0 is the first release which has been updated to reflect our changes from the old company Finisar to the new company JDS Uniphase.

The following is a list of released clients and their compatible application kits. The Operating System versions are also shown for reference.

NOTE: This is not an exhaustive list and we recommend that you use the last listed pair of versions of the client and the server software.

Client Version	Application Kit	OS Version	Notes
Older Xgig-A Clients	Previous released App Kits	Legacy Xgig OS Systems	Refer to the Previous Releases document.
Xgig-A 5.0.0.98660	App Kit 8.2.0.98582	System 5.0.0	EA release - SAS/SATA Advanced Triggering and FC Traffic Summary View.
Xgig-A 5.0.0.102410	App Kit 8.3.0.102430	System 5.0.0	EA Release - SATA Auto speed-negotiation for 6G/3G and 3G/1.5G data rates.
Xgig-A 5.0.0.108610	App Kit 8.4.0.1009039	System 5.0.2	RTM Release - Exchange View for SAS/SATA.
Xgig-A 5.1.0.110728	App Kit 8.5.0.110887	System 5.0.2 / System 5000.0.7	Introducing new Xgig5000 chassis and 8-port 10G Ethernet IO blade. Early Adopter release
Xgig-A 5.1.0.111275	App Kit 8.5.1.111289	System 5.0.2 / System 5000.0.7	Introducing 2-port 16G rev A SERDES Fibre Channel IO blade. Early Adopter release
Xgig-A 5.1.0.113377	App Kit 8.6.0.113417	System 5.0.2 / System 5000.0.9	RTM release for Analyzer 5.1.0 and Patch release for Maestro 6.1.1
Xgig-A 5.1.0.113417	App Kit 8.6.1.113417	System 5.0.2 / System 5000.0.9	Patch release for Analyzer and Maestro, partial blade licensing
Xgig-A 5.1.2.116691	App Kit 8.7.0.116899	System 5.0.2 / System 5000.0.9	Introducing 16G FC 4-port rev B SERDES for Analyzer and Maestro's Jammer and LoadTester applications.
Xgig-A 5.1.3.118147	App Kit 8.8.1.118328	System 5.0.2 / System 5000.0.9	Patch release for Analyzer and Maestro
Xgig-A 5.1.4.119438	App Kit 8.8.2.119804	System 5.0.2 / System 5000.0.9	Patch release for Analyzer and Maestro
Xgig-A 5.2.0.117141	App Kit 8.8.0.117172	System 5.0.2 / System 5000.0.9	EA1 release for 12G Analyzer
Xgig-A 5.2.2.120877	App Kit 8.8.3.120877	System 5.0.2 / System 5000.0.9	EA3 release for 12G Analyzer
Xgig-A 5.3.0.123070	App Kit 8.9.0.122978	System 5.0.2 / System 5000.0.9	Major feature release for Analyzer
Xgig-A 5.3.1.124168	App Kit 8.10.0.124098	System 5.0.2 / System 5000.0.9	Patch release for Analyzer T1/T2 feature.
Xgig-A 5.4.0.126474	App Kit 8.10.0.126474	System 5.0.2 / System 1000.0.5 / System 5000.0.9	Introducing new Xgig1000 chassis with 12G SAS protocol board as Early Adopter release.
Xgig-A 6.0.0.126905	App Kit 9.0.0.126905	System 5.0.2 / System 1000.0.7 / System 5000.0.9	Introducing new Xgig1000 chassis with 12G SAS protocol board and new 40G Ethernet as Early Adopter release Features release including 12G SAS and 16G FC enhancements.
Xgig-A 6.1.0.130664	App Kit 9.1.0.130935	System 5.0.2 / System 1000.0.7 / System 5000.0.9	Features release - 12G SAS Auto-Speed Negotiation 16G FC Training Events support and bug fixes.
Xgig-A 6.2.0.135803	App Kit 9.2.0.135803	System 5.1.2 / System 1000.0.19 / System 5000.0.25	Features release - Chassis admin via LCD display and control Save to chassis USB attached disk Timed and Floating licensing via the external dongles 10G Ethernet FEC support - Xgig blade only, 12G SAS 64-bit Sliding Pattern Search, 16G FC Training Events compression, 66-bit block non-error data display, Advanced Triggering, Traffic Summary View, and bug fixes.
Xgig-A 6.2.0.135803	App Kit 9.3.0.136241	System 5.1.2 / System 1000.0.19 / System 5000.0.25	This is Xgig-A version 6.3.0 release which was released with 16G FC Generator release - old client but new app kit SW.
Xgig-A 6.3.1.137327	App Kit 9.3.1.137327	System 5.1.4 / System 1000.0.21 / System 5000.0.27	Patch release for Analyzer and Maestro.
Xgig-A 6.3.2.138194	App Kit 9.3.2.138150	System 5.1.4 / System 1000.0.21 / System 5000.0.27	Patch release for Analyzer - CLE config #0 available for 12G blade.
Xgig-A 6.5.0.139847	App Kit 9.5.0.139872	System 5.1.6 / System 1000.0.23 / System 5000.0.29	Introducing 10G Ethernet and 16G FC on Xgig1000 platform.
Xgig-A 6.5.0.139847	App Kit 9.5.1.140112	System 5.1.6 / System 1000.0.23 / System 5000.0.29	Add 4-port version of 10G Ethernet and 16G FC on Xgig1000 platform.
Xgig-A 6.5.2.140131	App Kit 9.5.2.140207	System 5.1.6 / System 1000.0.23 / System 5000.0.29	Patch release for API support of FRunner script conversion.
Xgig-A 6.5.3.141043	App Kit 9.5.3.141043	System 5.1.6 / System 1000.0.23 / System 5000.0.29	EE2 release for various 16G FC bug fixes.
Xgig-A 6.5.3.141346	App Kit 9.5.3.141346	System 5.1.6 / System 1000.0.23 / System 5000.0.29	EE3 release for various 12G SAS bug fixes.
Xgig-A 6.5.3.141958	App Kit 9.5.3.141994	System 5.1.6 / System 1000.0.23 / System 5000.0.29	EE5 release for auto-tuning.
Xgig-A 6.5.3.143225	App Kit 9.5.3.143263	System 5.1.6 / System 1000.0.23 / System 5000.0.29	Official patch release for 12G SAS auto-tuning and power management, and 16G FC dual-personality of the 4-port FPGA.
Xgig-A 6.6.0.145982	App Kit 9.6.0.145982	System 5.1.6 / System 1000.0.23 / System 5000.0.29	Xgig1000 platform supports: 40G with QSFP+, 10GE/16G FC dual-personality of the 4-port FPGA, 10GE channels from QSFP ports, and port-pair licensing, 12G SAS Optical support and Tx Training display.
Xgig-A 6.6.1.146637	App Kit 9.6.1.146637	System 5.1.6 / System 1000.0.23 / System 5000.0.29	Patch release to fix issues with Auto-Tuning and Tx Training Summary events using the 12G SAS protocol board.
Xgig-A 6.7.0.147997	App Kit 9.7.0.148138	System 5.1.6 / System 1000.0.23 / System 5000.0.29	Features release which includes 10GE AJ and TC API Python.
Xgig-A 6.7.1.150162	App Kit 9.7.1.150235	System 5.1.6 / System 1000.0.23 / System 5000.0.29	New CLE configurations for X1K 12G SAS: “J,J,J,J”, “A-J-J-A”, “G-A, G-A” and “J-A,J-A”.
Xgig-A 6.8.0.150381	App Kit 9.8.0.150417	System 5.1.6 / System 1000.0.29 / System 5000.0.29	New revision of the motherboard of the Xgig 1000 chassis.
Xgig-A 6.8.1.153211	App Kit 9.8.1.153224	System 5.1.6 / System 1000.0.31 / System 5000.0.29	Patch release with bug fixes.
Xgig-A 7.0.0.152368	App Kit 10.0.0.152368	System 5.1.6 / System 1000.0.29 / System 5000.0.29	Introducing PCIe 3.0 X8 on Xgig1000 platform with NVMe support.
Xgig-A 7.0.1.153504	App Kit 10.0.1.153504	System 5.1.6 / System 1000.0.31 / System 5000.0.29	Patch release with enhancements for PCIe/NVMe support.
Xgig-A 7.0.2.154180	App Kit 10.0.2.154180	System 5.1.6 / System 1000.0.31 / System 5000.0.29	Patch release with enhancements for PCIe/NVMe support.
Xgig-A 7.0.3.155448	App Kit 10.0.3.155273	System 5.1.6 / System 1000.0.31 / System 5000.0.29	Patch release for bug fixes and enhancements for PCIe/NVMe support.
Xgig-A 7.0.4.156991	App Kit 10.0.4.156991	System 5.1.6 / System 1000.0.31 / System 5000.0.29	Patch release with bug fixes and enhancements for ASPM and PCIe x4 licensing option.
Xgig-A 7.0.5.158012	App Kit 10.0.5.158012	System 5.1.6 / System 1000.0.31 / System 5000.0.29	Patch release with bug fixes for Expert and memory diagnostic tool.
Xgig-A 7.1.0.159520	App Kit 10.1.0.159477	System 5.1.6 / System 1000.0.31 / System 5000.0.29	12G SAS HW supports for 6G SATA & Power Management, 8GB/port buffer size for 10G/16G, 12G, and 16GB/port buffer size for 40G. Many improvement related to PCIe such as Decodes for NVMe, AHCI, and SOP. Support LTSSM, ASPM, and new inteproser for SFF-8639 connector type.
Xgig-A 7.1.1.162078	App Kit 10.1.161785	System 5.1.6 / System 1000.0.43 / System 5000.0.41	USB Direct Connect Save buffer to a sub-directory. Bug fixes.
Xgig-A 7.2.0.162787	App Kit 10.3.0.162969	System 5.1.6 / System 1000.0.43 / System 5000.0.41	PCIe Jammer release support
Xgig-A A7.3.0.168685	App Kit 10.4.0.168685	System 5.1.6 / System 1000.1.3 / System 5000.0.41	PCIe's TS1/TS2 Compression, CLKREQ#/PERST# capture, L1 substates. Expert skips optional FC/Ethernet headers. Decode Improvements. Bug fixes.
Xgig-A 7.3.1.169226	App Kit 10.4.1.169175	System 5.1.6 / System 1000.1.3 / System 5000.0.41	Firmware upgrade for 25GE and 32G FC protocol board.

Hardware Compatibility

New hardware blades require matching server and client version.

Supports all existing Xgig Multi-Function blades.

Supports all existing wide blades (8-port) and narrow blades (4-port and 2-port) Xgig blades.

All Xgig Multi-Funcion blades are supported in Xgig5000 chassis using the adapter trays.

Platforms Tested

Various makes and models of laptops and desktop PCs with the following Operating Systems were used to test the software. The client software can also be installed and used on 64-bit machines and Windows OS. However, it is operated as 32-bit software. All pre-requisites must be installed prior to installing the software.

Windows 7 with SP1 - Professional and Enterprise editions

Windows 8 - Professional and Enterprise editions

Windows Server 2008 with SP2 - Standard and Enterprise editions

Windows Server 2008 R2 with SP1 - Standard and Enterprise editions

Windows Server 2012 R2 Update - Standard and Essentials editions

Bus Doctor and I-Tech:

In addition to Xgig file formats and other well known Ethernet capture file formats, the Xgig Analyzer supports SAS/SATA, Fibre Channel, and Ethernet with Bus Doctor and I-Tech trace file formats. However, they cannot work directly with Bus Doctor or I-Tech hardware. They only work with saved trace files.
Xgig Expert and Xgig TraceView now support SAS v1.1 - Serial Attached SCSI captures taken from the Bus Doctor RX-108, RX-252 and I-Tech PowerFrame analyzer platforms. Xgig Expert provides full SAS Link Layer (SL), Serial SCSI Protocol (SSP), Serial ATA (Native and STP) experts and metrics for both single transmit/receive links as well as wide links of up to the number of physical capture lanes available on the analyzer (8 lanes/4 links on the RX-252 and 32 lanes/16 links on the PowerFrame).
It is recommended to use JDSU Bus Doctor Plus v3.2 or higher versions of the software for trace capture from the Bus Doctor Platform.
It is recommended to use I-Tech Satellite Software v2.10.1 for trace capture from either the PowerFrame or the legacy platforms.
To convert a trace, simply open the trace with either Xgig Expert or Xgig TraceView:

Select File/Open from the Xgig application.

Change the Files Of Type selector to "Bus Doctor (*.trace)". For I-Tech traces, select "I-Tech (*.SAT)".

Navigate to the directory where the trace is stored. NOTE: This will vary somewhat for Bus Doctor and Bus Doctor Plus. Bus Doctor files are typically a single .trace file with a name of mytrace.trace. Bus Doctor Plus files are comprised of several files stored within a directory named mytrace.trc\, which contains the file _data.trace along with some other supporting files.

Double-click on the saved file which you want to convert.

If the trace has been previously converted, you will be prompted to overwrite the trace.

Once the trace file has been converted, the files can be reopened by simply opening the .TGP file in the same directory that the original trace file was converted from. In the example above, this would be C:\traces\mytrace.trc\mytrace.tgp. This file can be opened with Xgig Expert via the File/Open menu or in Xgig TraceView by simply double-clicking on the TGP file in explorer or using File/Open.

The trace will then be converted to Xgig trace format and automatically opened once the conversion is completed.
NOTE: Xgig TraceView and Xgig Expert will not work directly with the Bus Doctor or I-Tech hardware platforms. Refer to the Xgig Analyzer User's Guide for more details.

Top of Page

Upgrading the chassis

Use one of the following methods to upgrade the Xgig chassis:

NOTE: After finishing the app kit upgrading process, the Xgig5000 and Xgig1000 might go through the firmware upgrading for the blades installed and the chassis. Please pay attention to the following details.

Status LED lights of the blades are blinking GREEN or alternating RED and PURPLE - Firmware upgrading or recovering is in progress. Please do not disturb! The Status page of the chassis web interface will display the orange banner indicating that firmware upgrading is in progress as well.
Status LED lights of the blades are blinking RED - Firmware upgrading is complete and it requires that the chassis to be power cycled. Please turn the chassis OFF and wait for 10 seconds before applying power to the chassis to turn it ON. Un-predictable behavior might result if the chassis is not properly power cycled.
Downgrading an Xgig5000 or Xgig1000 chassis from app kit version 9.1.0 to any earlier versions requires the chassis to be power cycled for the downgrade process to complete. However, the Status LED lights of the blades will not blink RED to indicate this requirement. Monitor the Status LED lights of the blades as the firmware downgrade process proceeds. The LEDs will blink GREEN for several minutes (approximately 10 minutes per blade). Once all the Blade Status LEDs turn steady BLUE and all ports LEDs are off in the case of Xgig1000 chassis, power cycle the chassis before using it. When the chassis boots, the Blade Status LEDs will return to steady BLUE, this time indicating that the chassis is ready for use.

Upgrading the chassis from client software applications:

Install the Xgig Analyzer 7.3.1 client software on your PC by following the instructions in the Xgig Analyzer Installation Guide.

Launch the Xgig TraceControl or Xgig Performance Monitor application.

Click the "Create Domain" button in Xgig TraceControl or the "Select Sync Group" button in Xgig Performance Monitor.

In the "Select Ports for …" window, select the Sync Group containing the chassis you need to upgrade.

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. Either the System or Appkit or both will be upgraded depending on the status of each chassis in the sync group.

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.

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.

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

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

If both the System and Appkit software are to be upgraded, the Appkit software will be upgraded first then the chassis is rebooted. After two minutes delay, the System software will be upgraded. It would take a little longer for a chassis to reboot after a System software upgrade.

An "Upgrade Complete" dialog appears to notify the completion of the upgrade process.

Press "OK" to close the "Upgrade Complete" dialog.

Press "Close" to close the "Upgrade Chassis" window.

Press "Cancel" to close the "Select Ports …" window.

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

NOTE:

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.
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):

Install the Xgig Analyzer 7.3.1 client software on your PC by following the instructions in the Xgig Analyzer Installation Guide.

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

Proceed to the section "Upgrading the Xgig System Image and Application Image Software" in the "XgigFamilyHardware.pdf" to perform an upgrade using the Xgig Web Utility.

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

Top of Page

Support

Online Support

A trial version of software release is available on the Viavi’s web site as a free download. This software provides a convenient way to share traces with multiple users that are not required to have the Xgig hardware.

Click here to download the trial software version:

www.viavisolutions.com/XgigAnalyzerTrialSoftware

Technical Support

If you require technical assistance

Voice :	+1 844 GO VIAVI (1-844-468-4284)
E-Mail:	techsupport-snt@viavisolutions.com

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

Top of Page