Ixia Software Release Notes
IxOS 10.00 Patch1
Build Number: 10.00.1000.14 (June 2024)


About This Release

Welcome to IxOS 10.00 Patch1 Release. 
This patch release incorporates bug fixes and a new feature for the previous 10.0 IxOS release.
Please refer to the 'What is New' section and resolved defect list for a complete list of all the new features and bug fixes.

Application Compatibility

The following application releases support IxOS 10.00 Patch1:
Application IxOS 10.00 Patch1
BPS 10.00
HLTAPI 10.00
IxANVL 9.37
IxLoad 10.00
IxNetwork 10.00
IxVM 10.00
Licensing 5.70
Metronome 2.3
Wireshark 3.2.6
In addition, current interoperability and compatibility coverage for IxOS 
10.00 Patch1 can also be retrieved using the on-line compatibility tool.
It is compatible with IxOS 10.00 release.    

Licensing

Ixia Licensing

Any chassis which runs IxServer must have an IxOS license installed on it.
IxOS 10.00 Patch1 ships with Ixia Licensing 5.70, which is installed automatically along with IxOS Installation.

Some of the key benefits of this new licensing system are: - Supports Keysight's new KSM Licensing structure ( refer to Licensing Software Upgrade Required Customer Notice )

Installing a License

Ixia Licensing 5.70 upgrades Ixia Licensing 5.60 and prior versions. 
Once upgraded, Ixia Licensing cannot be downgraded to previous versions. 

If upgrading from the Ixia Registration Utility (IRU) used in IxOS 8.00 and earlier releases, note that 
automatic license migration is no longer possible. Please contact Support to assist you with the upgrade and with license retrieval.

For more information about the IxLicensing system, please refer to the "Ixia Licensing Management User Guide" 
provided with the Ixia software, or downloadable from the Ixia web site.


Installation Notes

Installation on XGS2-SD and XGS12-SD chassis

Starting from IxOS 8.40 EA, the XGS2-SD and XGS12-SD chassis can optionally be converted to run Native IxOS, 
for improved stability and performance. The conversion removes the Microsoft Windows Operating System, and 
replaces it with IxOS running natively on the chassis. Once complete the chassis are effectively converted to 
XGS2-SDL and XGS12-SDL. For more information, including the conversion process procedure, please read 
the Converting XGS2-SD and XGS12-SD Chassis to Native IxOS.pdf document available on IxOS Downloads And Update page.

Starting from IxOS 9.00, XGS2-SD and XGS12-SD chassis can optionally be converted to run Windows 10 Pro 64-bit, 
which allows the installation of the latest security and stability updates from Microsoft. For more information,
including the conversion process, please read the Windows 10 Upgrade Guide and  the Windows 10 Datasheet.  
Requires the purchase of IXIA IXOS AND WINDOWS 10 FIELD UPGRADE 943-0014.

Installation on PSOne, XGS2-HS and XGS12-HS chassis

Starting from IxOS 9.00, IxOS installation is no longer supported on the PSOne, XGS2-HS and XGS12-HS chassis with 
Windows OS. To install IxOS and compatible Ixia Applications on these platforms, the management operating system must
first be converted to Native IxOS 10.00 Patch1. The conversion procedure is described in Converting_XGS_and_PSOne_to_Native_IxOS.pdf,
which can be downloaded from IxOS 10.00 Downloads And Update page.

NOTE:
     -For security reasons, we recommend changing the default passwords for chassis.

Installation Requirements On Windows

IxOS 10.00 Patch1 installation requires 13 GB of free space on chassis' system drive and 5.5 GB of free space on client's system drive.
IxExplorer 10.00 Patch1 installation requires 2.5 GB of free space on client's system drive.



NOTE:
   - IxOS installer automatically installs a Microsoft Hotfix 2921916 (if not already installed) for an issue due to which 
     "Untrusted publisher" dialog would appear when installing IxOS on Windows 7.

Operating System Support

Windows Client PC: 
- Windows 2019 Server Standard 64-bit
  - Windows 11 Enterprise Edition 64-bit
- Windows 10 64-bit (Build 21H2)


   The following versions of Windows operating systems are no longer supported on the client: - Windows 7 - starting with IxOS 9.30 - Windows XP Professional 32-bit SP3 - starting with IxOS 8.30 EA UNIX Client PC: - Fedora Core 14.0 and above - RedHat Enterprise 5.0 and above - Centos 6.0 and above - Ubuntu 16.0 and above Other versions of UNIX platforms may operate properly, but are not officially supported. VMware - Server 1.0.2 - Server 2.0 Windows Chassis - Windows 10 Pro Version 22H2 - Windows 7 Ultimate 32-bit NOTE: IxOS is no longer supported on a Windows XP Professional Chassis, starting with IxOS 9.00. Languages supported are English, Chinese (traditional and simplified), French, German Hebrew, Italian, Japanese, Spanish and Swedish.

Supported Chassis

This release supports the following chassis:
 - XGS12-SD Windows 10 and Windows 7
 - XGS2-SD Windows 10 and Windows 7
 - XGS12-SDL
 - XGS2-SDL
 - XGS12-HSL
 - XGS2-HSL
 - AresOne
 - AresONE-S
 - AresONE-800G
 - Novus ONE PLUS 
 - Novus ONE
-  PerfectStorm One

Installation Features

The IxOS installation program offers the user a selection of four installation 
options: Client, Server, Demo Server and Tcl Server. The 
Server option is normally chosen for installation on Ixia chassis. The Demo 
Server option should NOT be chosen for chassis installations: it is used for 
client installations.

IxServer on Windows Chassis

In IxOS 9.00 High Performance Mode was introduced to the Windows chassis as an option, with the alternative to revert to Legacy Mode to support a wider range of load modules.
Besides significantly improving performance in multi-user test beds, High Performance Mode also enables chassis STAR or Metronome synchronization capability between Native IxOS and Windows Chassis.
With 9.10, only High Performance Mode exists, and it has been enhanced to support the wider range of load modules.  The Native IxOS chassis has always supported High Performance mode. 

Startup Configuration Options

There are three options offered for configuring IxOS server startup:

1. Service: A Windows Service for IxServer (or TCL Server) will be created which can be started/stopped
    from Windows Service Control Manager. Desktop Shortcuts and IxServer User Interface are not available.
    Any configuration of IxServer or TCL Server requires user to stop the service, manually invoke server
    from Start Menu shortcuts, close the server and restart service.
2. Startup: IxServer starts when user logs on to the chassis or when it is rebooted.
3. Manual: IxServer or TCL Server can only be started or stopped manually from
    Desktop or Start Menu shortcuts.
 
    NOTE:
       - Telnet connectivity is unavailable when TCL Server is configured to run as a service.
       - Demo Server is configured to operate manually even if service option is selected.

Tcl Version Option

IxOS 10.00 Patch1 is shipping with Tcl 8.5 and 8.6. Both of them will be installed and the option
of using either of the version can be set for usage as follows:
1. On Windows Chassis, open TCL Server and select appropriate TCL version from options.
2. On Windows Client, select appropriate TCL version from Desktop or Start Menu shortcut.
3. On Native IxOS Chassis, login to IxOS CLI using SSH and execute:    set tcl active-version 8.x
4. On Unix Client, execute a script inside installed directory:    ./bin/set_tcl_active_version.sh 8.x

Chassis Management Console

 
Chassis Management Console (CMC) is a web application that provides access to Ixia Native IxOS Chassis and its components 
(i.e. load modules and ports) and enables users to control and monitor the chassis by means of any client computer connected to it. 
CMC is supported on following browsers:
Application Version
Google Chrome 75 or newer
Mozilla Firefox 67 or newer
Microsoft Edge 38 or newer
Apple Safari 12.1.1 or newer

UNIX Client Installation Notes

Using .bin Installer:

This installs packages for IxOS TCL API and Ixia TCL Interpreter. If you are updating an existing 
installation, be sure to run the installer as the same user who initially installed the software. Always 
run the uninstaller prior to removing any files manually. If installing as the root user and install 
location is a network-mounted file system, ensure the root user has write permission to the file system.

To proceed with installation, perform following steps (Note: the binary file name 'IxOS10.00.XXX.XXXLinux.bin' 
is used in the example below. In most cases, the file name will be different):

1. Copy the IxOS10.00.XXX.XXXLinux.bin file to the system.
2. Make the binary executable if it is not already:    chmod +x ./IxOS10.00.XXX.XXXLinux.bin
    Also, make sure target installation directory has full permissions granted.
3. Execute the IxOS installer file:    ./IxOS10.00.XXX.XXXLinux.bin
4. When the installer prompts, select appropriate Tcl version (e.g. 8.5 or 8.6)
5. Follow the installation prompts to complete the installation.

If the installation fails, check that there is enough disk space on the system  by using the command: df -ak
There must be enough space in the /tmp folder (to extract the files), and in the target folder (where files are 
to be installed). If the /tmp dir does not have enough space, specify the dir by setting IATEMPDIR environment 
with path to the folder where you have enough free space. The following example show the use of the options:

export IATEMPDIR=/tempdir
./IxOS10.00.XXX.XXXLinux.bin

Using .tar.gz:

This installs packages for IxOS TCL API only. To install, perform the following steps:

1. Create a destination folder and extract contents of .tar.gz file into it. e.g. /export/home/ixos10.00
2. After extraction, set the following variables (please replace sample path with original path):
        IXIA_HOME=/export/home/ixos10.00
        IXIA_VERSION=10.00.XXX.XXX
        TCLLIBPATH=/export/home/ixos10.00/lib
3. Optionally, specify the following environment variables to specify the location of logs, samples and results files for IxOS:
	IXIA_LOGS_DIR=$IXIA_HOME/logs
	IXIA_RESULTS_DIR=$IXIA_HOME/results
	IXIA_SAMPLES=$IXIA_HOME/samples
	IXIA_TCL_DIR=$IXIA_HOME/lib
4. If the Tcl option was installed with an IxOS installation, add Ixia's bin 
    and lib directory to the PATH and LD_LIBRARY_PATH variable in order to use it. 
    For example:
        IxiaLibPath=$IXIA_HOME/lib
        IxiaBinPath=$IXIA_HOME/bin
        PATH=$IxiaBinPath:$PATH
        LD_LIBRARY_PATH=$IxiaLibPath:$LD_LIBRARY_PATH

Multiple IxOS versions

Multiple IxOS versions can co-exist on an Ixia Chassis or client. Installing another IxOS version does not affect the existing versions.
On Windows Chassis, to set active IxOS version, users are required to close any running instance of
IxServer or TCL Server and start the intended IxServer version from Start Menu or Desktop Shortcuts.
On Native IxOS Chassis, users can login to IxOS CLI via SSH and set active IxOS version using
the command: set ixos active-version 10.x.x.x

NOTE: Any card, port, stream, etc., files generated by IxOS are forward compatible but not backward compatible. 

Tcl/Tk Support for Client Applications

Tcl Server was first supplied free of charge starting with IxOS 3.80 EA. 
Installation of this feature is optional; it should only be installed if 
required for specific application.
 
Installation and operation of the Tcl Server is required for IxChariot when 
running hardware performance pairs, for IxANVL when running VNIC (Virtual 
Network Interface Card) and for IxAuthenticate. The Tcl Server can be installed 
on either the Ixia chassis or a separate Windows workstation. 

The following limitations exist with respect to Wish and Tcl shell support:

   Tcl shell does not run on any version of Windows with Ixia software. Under
   Linux or Solaris, the Tcl shell runs on any version of Tcl greater than or 
   equal to 8.3.

How to Report Problems

 

Please follow the link below for details to contact Keysight Support using email & phone and for business hours:

https://support.ixiacom.com/contact

 

 

Additional Documentation

Please refer to our website at https://support.ixiacom.com/ixos-1000-Patch1.

You will be required to provide a login and password to enter this section of 
the web site. If you do not have the username and password, please forward your 
request to support@ixiacom.com.

Field Notices

Laser Warnings

The 10G load modules may use a Class III laser. Precautions should be 
taken to prevent personal injury. The spring-loaded safety cover should always be 
securely in place over the port when there is no cable installed. Avoid exposure
and never look directly into an open port aperture.

Inserting / Removing Load Modules

Modules in the XGS12-SD, XGS12-HSL, XGS12-SDL, XGS2-SD, XGS2-HSL, XGS2-SDL can be inserted/removed while the chassis is still operational.  

For all chassis types, use caution when inserting or removing multi-slot modules 
to evenly insert and remove. Load modules are tightly spaced; avoid contacting 
the adjoining modules while inserting and removing.

Safety Notice Regarding Ixia Load Modules

WARNING: In order to prevent accidental injury to personnel, do not leave transceiver 
(SFP/SFP+/QSFP/QSFP28/CXP/CFP4) cages uncovered on Ixia load modules. When transceivers 
are not installed, port end caps (Part No. 503-006) must be used. The metal edge of 
the transceiver cage is SHARP. To avoid injury, ALWAYS keep the transceiver cage covered.
   
Contact Ixia Technical Support to obtain end caps. Please reference Ixia Product
safety notice Part No. 913-0715 Rev A, June 2009. For additional information
refer to Chapter two of the IXOS Getting Started Guide under the section, 
Notes, Cautions and Warnings.

Use Ejector Tabs Properly

Ejector tabs on load modules are to be used only to eject a load module from
the chassis backplane connector. They are not designed to support the weight
of the load module. Ejector tabs can bend or break if used improperly as handles
to push, pull, or carry a load module.

What's New in IxOS

 

 
NOVUS10GDP 5-Speed
 
Note
For Novus10G Load Module, two new stats added in statistic view i.e Minimum IFG and Average IFG*
 

 


Known Issues List

 

 
AresONE 800GE-QDD-OSFP-M
 
Bug Number Note
IXOS-13048 There is a noticeable Auto Negotiation (AN) completion time degradation especially in 106G per lane CR application. In most cases, the degradation is around 2 seconds. In some extreme case, it may go up to 10 seconds.
 
Miscellaneous
 
Bug Number Note
IXOS-13093 In some corner cases build installation may fail while installing from chassis web UI, workaround is to install from CLI

 

 


 

Resolved Defects List

 

 
NOVUS10GDP 5-Speed
 
Bug Number Note
IXOS-9887 On Reduced variant, priority flow control queues 2-7 fails to configure on streams.
IXOS-12836 IEEE802.1Qbv - Qbv Gate Statistics does not show up
IXOS-12857 The L1 Line Rate Transmit value is greater than 100% when the links are set to internal loopback and traffic is started.
 
FlexAP1040SQ
 
Bug Number Note
IXOS-12345 Unable to apply traffic when traffic items are configured with random, repeatable random range and repeatable random bitmask.
 
CLI
 
Bug Number Note
IXOS-12771 Proxy connection request is failing on using IP address.
 
NOVUS10G32S
 
Bug Number Note
IXOS-12796 For few boards, MSD failures are observed during card boot up.
 
AresONE 800GE
 
Bug Number Note
IXOS-12858 On 800G ports, Packet loss is observed when pause frames are sent to a traffic stream using frame size greater then 4906 Bytes
 
AresONE
 
Bug Number Note
IXOS-12863 In AresONE load module, TCP checksums were seen in captured packets if "auto correct payload checksum in L4 header" options is disabled in IxNetwork.
 
AresONE S400GD
 
Bug Number Note
IXOS-12999 Packet group frame rate shows negative value after running traffic over 100 seconds.
 
NOVUS10GDP 3-Speed
 
Bug Number Note
IXOS-13034 Latency values are out of range when sending traffic between Novus10/1GE16DP (10GE) and XMR10GR32SFP+FAN+40G (40GE) ports.
 
AresONE 800GE-QSFP-DD800-M
 
Bug Number Note
IXOS-13039 Port link is not coming up with DUT on 200G-PAM4-53G with auto negotiation enabled.
 
Infrastructure
 
Bug Number Note
IXOS-13047 IxOS-Client installation requires the chassis to have internet connectivity.