Ixia Software Release Notes
IxOS 9.14
Build Number: 9.14.2000.3 (December 15, 2020)



About This Release

Welcome to IxOS 9.14 Release. All IxOS features and bug-fixes introduced in interim releases since IxOS 9.10 have been consolidated into this release.
Please see sections below for application and hardware compatibility, new features, resolved issues, and known issues.
The IxNetwork 9.14 release only supports Virtual Ports and does not support Hardware Ports. The application prevents the user from connecting to Hardware Ports from a physical chassis with IxOS 9.14.
The IxLoad 9.14 release only supports DCS Hardware Ports and does not support Virtual Ports. The application prevents the user from connecting to Virtual Ports from a virtual chassis with IxOS 9.14.

Application Compatibility

The following application releases support IxOS 9.14:
Application IxOS 9.14
HLTAPI 9.10
IxANVL Not Supported
IxLoad 9.14
IxNetwork 9.14
IxVM 9.14
Licensing 5.30
Metronome 2.1
Wireshark 1.8
In addition, current interoperability and compatibility coverage for IxOS 9.14 can also be retrieved using the on-line compatibility tool. Please contact Keysight for details.

Licensing

Ixia Licensing

Any chassis which runs IxServer must have an IxOS license installed on it. IxOS 9.14 ships with Ixia Licensing 5.30, which is installed automatically along with IxOS Installation. Some of the key benefits of this new licensing system are: - Reduced the number of licensing services from 4 to 1 (Ixia nodedv3). - The list of TCP ports required for external connections has been reduced, specifically TCP port 4502 is no longer required. - Improved performance and memory usage.

Installing a License

Ixia Licensing 5.30 upgrades Ixia Licensing 5.20 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_XGS_SD_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 8.50 EA. The conversion procedure is described in Converting_XGS_and_PSOne_to_Native_IxOS.pdf, which can be downloaded from IxOS 8.50 EA Downloads And Update page. NOTE: -For security reasons, we recommend changing the default passwords for chassis.

Installation Requirements On Windows

IxOS 9.14 installation requires 13 GB of free space on chassis' system drive and 5.5 GB of free space on client's system drive. IxExplorer 9.14 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 2008 Server 64-bit - Windows 7 Enterprise 32-bit (Build 7601) - Windows 7 Professional 32-bit (Build 7601) - Windows 7 Professional 64-bit (Build 7601) - Windows 7 Ultimate 32-bit (Build 7601) - Windows 2012 Server Standard R2 64-bit - Windows 8.1 Enterprise 32-bit and 64-bit (Build 9600) - Windows 10 Pro 64-bit (Build 2004) The following versions of Windows operating systems are no longer supported on the client: - Windows Vista Enterprise SP2 32-bit and 64-bit - starting with IxOS 8.21 EA - 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 64-bit (Build 1903) - 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 - XM2 - 400Tv2 - AresONE - Novus ONE PLUS - Novus ONE - PerfectStorm One

Installation Features

The IxOS installation program offers the user a selection of five installation options: Client, Server, Demo Server, Tcl Server, and Hardware Manager. 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 9.14 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 'IxOS9.14.XXX.XXXLinux.bin' is used in the example below. In most cases, the file name will be different): 1. Copy the IxOS9.14.XXX.XXXLinux.bin file to the system. 2. Make the binary executable if it is not already: chmod +x ./IxOS9.14.XXX.XXXLinux.bin Also, make sure target installation directory has full permissions granted. 3. Execute the IxOS installer file: ./IxOS9.14.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 ./IxOS9.14.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/ixos9.14 2. After extraction, set the following variables (please replace sample path with original path): IXIA_HOME=/export/home/ixos9.14 IXIA_VERSION=9.14.XXX.XXX TCLLIBPATH=/export/home/ixos9.14/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 8.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

Ixia Headquarters

+1 877 367 4942 - Toll-free North America
+1 818 871 1800 - Outside North America
+1.818.871.1805 - Fax
www.ixiacom.com/contact/info

Support

Global Support +1 818 595 2599

support@ixiacom.com

APAC Support +91 80 4939 6410

support@ixiacom.com

Australia +61-742434942

support@ixiacom.com

EMEA Support +40 21 301 5699

support-emea@ixiacom.com

Greater China Region

+400 898 0598

support-china@ixiacom.com

Hong Kong +852-30084465

support@ixiacom.com

India Office +91 80 4939 6410

support-india@ixiacom.com

Japan Head Office +81 3 5326 1980

support-japan@ixiacom.com

Korea Office +82 2 3461 0095

support-korea@ixiacom.com

Singapore Office +65-6215-7700

support@ixiacom.com

Taiwan (local toll-free number) 00801856991

support@ixiacom.com


Additional Documentation

Please refer to our website at http://support.ixiacom.com/support-services/product-support/user-guides.

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, and XM2 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 three 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

IxOS 9.14 Features

VM
Support for IxOS REST API for DHCP Server configuration has been added. The user can now configure the Virtual Chassis DHCP Server and its parameters via this API.
Support for IxOS REST API for License Check configuration has been added. It is used to control the IxOS License Check on the Virtual Chassis / Virtual Test Appliance.
Support for IxOS REST API for Layer 1 Information retrieval has been added. The user can now read Layer 1 information related to transceivers / cables / power levels.
Support for [debug --command ethtool -m {iface}] has been added in the CLI. The user can now read Layer 1 information related to transceivers / cables / power levels.


Known Issues List

VM

Bug Number Notes
1552765 Due an Intel NIC limitation, retrieving transceiver L1 information from a Intel XXV710 NIC using IxOS REST API doesn't output any values.
1552796 On certain setups due to limited PCI capabilities (e.g. NIC using PCI Express 2), using IxOS REST API to retrieve transceiver L1 information will not show any values.
1552800 Retrieving transceiver L1 information using IxOS REST API will only output Vendor Name, Vendor SN and input / output power information. If these values are not published by the NIC they will not be present in the output.
1553843 Running high line rates (close to 100%) from IxExplorer can cause packets to be reordered at Tx side on Mellanox configured VE setups.
1554508 When using Mellanox NICs connected in PCI-PT / SR-IOV mode and running on VMware ESXi hypervisors the support for Promiscuous Mode / Trust Mode / VLAN Tagging capabilities is not available.
1554512 When running protocols and/or traffic on Mellanox SR-IOV Virtual Functions we recommend using the following settings on the Physical Functions and Virtual Functions: - Physical Functions ip link set dev PF_INTERFACE_NAME up ip link set dev PF_INTERFACE_NAME mtu 9000 ip link set dev PF_INTERFACE_NAME promisc on ip link set dev PF_INTERFACE_NAME allmulticast on - Virtual Functions ip link set dev PF_INTERFACE_NAME vf VF_INDEX trust on ip link set dev PF_INTERFACE_NAME vf VF_INDEX spoofchk off