- About This Release
- User Authentication
- Installation Notes
- Tcl/Perl/Python/Ruby/REST Support for Client Applications
- How to Report Problems
- Additional Documentation
- What's New in IxNetwork
- Known Issue List
- Resolved Defect List
Welcome to IxNetwork 9.33 Release. This release is primarily focused on enhancements made for MACsec 400GE/200GE on the AresONE-P platform. For a complete listing of all the new features included in this release, please refer to the 'What is New' section.
Application Compatibility The following application releases support IxNetwork 9.33:
|Application ||IxNetwork 9.33 |
|BPS ||Not Supported |
|HLTAPI ||9.33 |
|IxANVL ||Not Supported |
|IxLoad ||Not Supported |
|IxOS ||9.33 |
|IxVM ||Not Supported |
|Licensing ||5.60 |
|Metronome ||2.3 |
|Wireshark ||3.2.6 |
IxNetwork requires that a license for its use be installed for each chassis used by IxNetwork. That license may be installed on each chassis or on a server on your network, referred to as the central license server.For more information about the new Licensing system, please refer to the "Ixia Licensing Management User Guide" provided with the Ixia software, or downloadable from the Ixia web site: https://ksm.software.keysight.com/content/KSMQuickReferenceGuide.pdf
PrerequisitesAs part of the IxNetwork installation, the installer installs Microsoft SQL Express and Microsoft .Net Framework on a client machine and Microsoft .Net Framework on achassis.Windows client and chassis should have all the Windows updates installed.If you experience any issue related to the installation of these prerequisites, please uninstall any existing versions, reboot, and reattempt installation.
IxNetwork InstallationIxNetwork has two components: - The 'chassis' component needs to be installed on the Ixia windows chassis being used or when using a native IxOS chassis it is included in the IxOS install package. It is required to install IxOS before installing the IxNetwork 'chassis' component.- The 'client' component needs to be installed on the user-provided Windows workstation where the IxNetwork GUI will be run. The Web Edition 'client' component can be deployed on VMware ESXi, KVM, Docker or directly on a Native IxOS chassis.
IxNetwork Download from Ixia Website IxNetwork software is available as a download from the Ixia website. 1. Download IxNetwork software from the Ixia website to an Ixia chassis or client PC. Double-click on the file from within Windows Explorer. 2. Follow the on-screen instructions provided by the installer.
IxNetwork Chassis Installation RequirementsWhen installing IxNetwork 9.00 + on a chassis, a minimum of 4GB of installed RAM and 30GB of free disk space is required.If your chassis does not meet these requirements, please contact Customer Supportat email@example.com or +1 818 595 2599.NOTE: IxNetwork installs the Ixia Stat Engine component. This component is shared by other Ixia applications. It can be manually uninstalled from the target machine by using the Windows Add/Remove Programs applet.
Operating System Support The following operating systems are supported on the chassis - Windows 7 Ultimate 32-bit - Windows 10 Pro 64-bit - CentOS 7 64-bit (only for Ixia Linux Chassis) For other foreign language support, please change the default to US English. Note: Regardless of configured OS language, the keyboard must be configured for US English.
IxNetwork Chassis Installation Notes 1. Install the required IxOS version. 2. Use the IxNetwork chassis installer to install the IxNetwork chassis component. The client component of IxNetwork cannot be installed on the Ixia Windows chassis. 3. If the required IxOS was already installed and running, restart IxServer.
Client Installation RequirementsIxNetwork 9.00+ requires the user workstation to have the following minimumsystem requirements. It is recommended to use the 'next higher' requirement forimproved performance.IxNetwork application has been qualified with full load stress test up to 7 days.
|Ixia Configuration ||Per User/Per Session System Requirements |
|Ports ||Flow Groups ||Flows ||CPU (# or cores) ||Memory (GB) ||HDD (GB) ||Operating System |
|Install ||Temporary ||Running |
|4 ||4 ||500 ||1 ||2 ||14GB ||3GB ||10GB ||64 bit |
|8 ||8 ||4,000 ||2 ||2 ||14GB ||3GB ||20GB ||64 bit |
|16 ||16 ||8,000 ||2 ||3 ||14GB ||3GB ||20GB ||64 bit |
|32 ||32 ||16,000 ||2 ||4 ||14GB ||3GB ||20GB ||64 bit |
|64 ||64 ||32,000 ||4 ||6 ||14GB ||3GB ||20GB ||64 bit |
|128 ||16,000 ||4,000,000 ||4 ||8 ||14GB ||3GB ||30GB ||64 bit |
|1200 ||16,000 ||4,000,000 ||12 ||24 ||14GB ||3GB ||40GB ||64 bit |
|Platform ||Qualified no. of users |
|On chassis * |
|Ares One ||2 |
|Novus One Plus ||2 |
|XGS-SDL ||4 |
|XGS-HSL ||8 |
|Virtual Chassis ** ||1 |
|Off Chassis |
|Windows App Server ||48 |
|ESXi 6.0+/KVM V/Docker ||48 |
* on chassis assumes only that same chassis is used in the test.** the VM resources must be increased with the per user specsData storage must present local storage instead of NFS~ 25 IOPS per user are needed at minimum (HDD max 4 users, SSD up to 15 users, 15+ NVME/OPTANE drive)A compatible Graphics Card must be present on the serverMulti-user support is directly dependent on the available hardware resources.The system must meet the required operating system requirements + per user requirements * no. of users.EX: If we want to run 4 lite users on a Windows 2019 server: Windows needs minimum 2 GB RAM + 4 users * 2 GB/user = 10 GB RAM is needed at a minimum.
Operating System Support
The following versions of Windows operating systems are supported on the client: - Windows 2022 Server Standard 64-bit - Windows 2019 Server Standard 64-bit - Windows 2016 Server Standard 64-bit - Windows 2012 Server R2 Standard 64-bit (*) - Windows 11 Consumer/Business Edition 64-bit - Windows 10 Pro/Enterprise 64-bit - Windows 8.1 Enterprise 32-bit and 64-bit (*) (*) The following foreign languages are supported only on Windows 8.1 Enterprise and Windows 2012 Server R2 SP1 Standard: - Chinese (traditional and simplified) - Japanese For other foreign language support, please change the default to US English.Note: Regardless of configured OS language, the keyboard must be configuredfor US English.IxNetwork Low Level API library is supported on the following operating systems: - Microsoft Windows(OS as stated above) - Tcl 8.5 and 8.6, Perl 5.18, Python 2.7 and 3.6, Ruby 1.9.3 - CentOS 7 on x64 platform - Tcl 8.5 and 8.6, Perl 5.18, Python 2.7 and 3.6, Ruby 1.9.3 IxNetwork Low Level API library has been tried but is not officially supported, on the following operating systems/language version combination: - CentOS 6.3, 6.4, 6.5 on x64 platform - Tcl 8.5, Perl 5.18, Python 2.7, Ruby 1.9.3 - Arch Linux on x64 platform - Tcl 8.6, Perl 5.26, Python 3.7 - Free BSD 10.1 on x64 platform - Tcl 8.6, Perl 5.18, Python 2.7 - OS X Yosemite on x64 platform - Tcl 8.6, Perl 5.18, Python 2.7 - Windows 8.1/2012 - Ruby 1.8.7, Ruby 2.2.2IxNetwork High Level API library is supported on the following operating systems:- Microsoft Windows(OS as stated above) - Tcl 8.5 and 8.6, Perl 5.24 and Python 2.7 and 3.6- CentOS 7 on x64 platform - Tcl 8.5 and 8.6 , Perl 5.24 and Python 2.7 and 3.6
IxNetwork Web Edition
1. IxNetwork Web Edition supports IxNetwork web based user interface, QuickTest and API Browser.2. IxNetwork Web Edition can be installed on VM (ESXi and KVM), Native IxOS chassis.3. IxNetwork Web Edition software (OVA, QCOW2, Docker, and HSL package) are available as downloads from the Ixia website.
|IxNetwork Web Edition ||OS ||Network ||Storage |
|ESXi OVA ||ESXi 6.0 Update 2 or ESXi 6.5 (64 bit only) ||VMXNET3 ||128 GB |
|KVM QCOW2 ||Ubuntu 18.04 LTS or CentOS 7.6.1810 (64 bit only) ||virtio ||128 GB |
|Docker ||Ubuntu 18.04 LTS or CentOS 7.6.1810 (64 bit only) ||Promiscuous mode enabled ||128 GB |
|Application ||IxNetwork Web Edition |
|Google Chrome ||80 or newer |
|Mozilla Firefox ||79 or newer |
|Microsoft Internet Explorer ||11 or newer |
|Microsoft Edge ||44.17763.1.0 or newer |
|Apple Safari ||12.1.1 or newer |
IxNetwork Web Edition can be installed on VMWARE ESXI via the provided OVA
1. Deploy IxNetwork Web Edition OVA directly on VMWARE ESXI server.2. Start the deployed VM.3. Get connected to the link displayed on the console screen (from the browser).4. Log in with credentials username: admin and password: adminNote: to use BGP protocol with VM ports, please change the VLAN from VSwitch in 4095
IxNetwork Web Edition can be installed on KVM via the provided QCOW2 image
Note: IxNetwork Web Edition is supported on KVM with CentOS and Ubuntu Distributions.1. Deploy QuickTest Web Edition QCOW2 in KVM/Virtual Machine Manager2. Start the deployed VM.3. Get connected to the link displayed in the console screen (from the browser).4. Log in with credentials username: admin and password: admin
IxNetwork Web Edition can be deployed as a Docker container via the provided imageNote
: IxNetwork Web Edition is supported as Docker container with CentOS and Ubuntu Distributions. 1. Copy the .tar file on the host2. Please make sure that the following will have promiscuous enabled:- network adapter from the host (CentOS/Ubuntu) or the virtual switch - the interface of the CentOS/Ubuntu3. Load the image to docker: docker load -i </path/to/tar/file>4. Create the macvlan bridge to be used by IxNetwork Web Edition: docker network create -d macvlan -o parent=<interface> --subnet <subnet> --gateway=<gateway> <bridge_name>5. Deploy the IxNetwork Web Edition container using the following command: a. When using MAC VLAN BRIDGE: docker run --net <BRIDGE NAME> \ --ip <CONTAINER IP> \ --hostname <HOSTNAME> \ --name <CONTAINER NAME> \ --cap-add=SYS_ADMIN \ --cap-add=NET_ADMIN \ -i -d \ -v /sys/fs/cgroup:/sys/fs/cgroup \ <IMAGE NAME> b. When using HTTPS on a specific external port and host IP: docker run \ - p <EXTERNAL PORT>:443 \ --cap-add=SYS_ADMIN \ --cap-add=NET_ADMIN \ -i -d \ -v /sys/fs/cgroup:/sys/fs/cgroup \ <IMAGE NAME>6. Open up a browser and connect to the configured IP.7. Log in with credentials username: admin and password: adminNotes:Optional mapping of configuration files, results and settings to external folders on host add the following parameters to the command: -v <HOST CONFIGS LOCATION>:/root/.local/share/Ixia/sdmStreamManager/common \ -v <HOST RESULTSLOCATION>:/root/.local/share/Ixia/IxNetwork/data/result \ -v <HOST SETTINGS LOCATION>:/root/.local/share/IXIA/IxNetwork.Globals \ Starting with version 9.33, IxNetwork Web UI Docker Container can only host cloud edition licenses and does no longer support regular licenses like it used to do in previous versions. Optional mapping for Cloud Edition Licenses installation on initialization add the following parameter to the command -v <CLOUD EDITION LICENSE ON HOST>/:/etc/keysight/licenses \ * The ip parameter assigns a specific IP to the container ** Name and Hostname are optional parameters *** Docker containers need sufficient space on the host, if not the sessions will not start **** If the container needs to be launched with the full list of capabilities, launch the container in --privileged mode
IxNetwork Web Edition can be installed on HSL/SDL/AresONE/Novus ONE chassis
1. Connect to XGS12-HSL/XGS2-HSL/XGS12-SDL/XGS2-SDL/AresONE/Novus ONE chassis. 2. Log in with credentials username: admin and password: admin 3. Go to Administration - IxNetwork Web Edition screen. 4. Click on "Manual Updates" and point to IxNetwork Web Edition HSL package file. 5. Follow the on-screen instructions provided by the installer.
IxNetwork Web Edition can be installed on VE Chassis
1. Connect to VE chassis. 2. Log in with credentials username: admin and password: admin 3. Click on the Install New Application button. 4. Click on "Browse" and point to the IxNetwork Web Edition package file. 5. Follow the on-screen instructions provided by the installer.Notes:- The first time IxNetwork Web Edition is installed on the VE Chassis the installation will take longer due to the installation of dependencies- The VE Chassis virtual machine must be provisioned with at least 4 vCPUs / 8 GB RAM for the install to be complete, IxNetwork Web Edition will use half of the provisioned resources- The vdisk size will have to be increased to at least 40GB to make room for the test results - The disk drive performance can influence the application performance, having a faster drive will provide the best results
Multi-session support is directly dependent on the available hardware resources.The system must meet the required operating system requirements + minimum per session requirements * no. of sessions.EX: If we want to run 4 sessions of IxNetwork Web Edition: Linux setup needs minimum 2 GB RAM + 4 sessions * 2 GB/session = 10 GB RAM is needed at a minimum.
Recommended screen resolution: 1920 x 1080If a display device with high resolution is used, it is recommended to change the text size to 100% from the display settings of the operating system for best usability experience.For Microsoft Windows 10 operating system: It is recommended to update at least to Windows 10 April 2018 Update release for best usability experience.
Linux/UNIX Installation Notes
The binary Linux installer will hang indefinitely if being started from an account without root or administrative privileges or at least R(read)W(write)X(execute) permissions on the /opt folder.Support on Linux/UNIX operating systems is for Tcl 8.5 & 8.6, Perl, Python 2.7 & 3.6 or Ruby API only,there is no graphical user interface (GUI) provided.Versions of Linux/UNIX platforms other than the ones enumerated above may operateproperly, but they are not officially supported.
Linux/UNIX Tcl Client Installation Notes
IxNetwork comes with Linux platforms dedicated installer, which has the TCLinterpreter bundled. The installation instructions are described in the IxNetworkHelp guide. IxNetwork also ships a Platform Independent installer (compressed tar) for Linux/UNIX platforms. Information about dependencies and installation instructions of this Platform Independent installer is as below. Dependencies: - TCL interpreter version 8.5 & 8.6Instructions for installation and testing: 1. Download and copy the IxNetwork Platform Independent Client installer to the client machine with TCL interpreter version 8.5 & 8.6 2. Extract it with tar -zxvf command. For example: # tar -zxvf IxNetworkPITclClient[version].tar.gz 3. Start the TCL shell or wish console on the client system and execute the following commands: - lappend auto_path [directory where the compressed tar file was extracted to] - package req IxTclNetwork (this should return a version number) - ixNet connect [IxNetwork TCL Server address] (this should return ::ixNet::OK) If you are updating an existing installation, be sure to run the installer as thesame user which initially installed the software.Always run the uninstaller prior to removing any files manually.If installing as root and the install location is a network-mounted file system,ensure root has write permission to the file system prior to starting the installer.
Linux/UNIX Python API Installation Notes
IxNetwork Linux/UNIX installer also delivers the Python API under the installation directory [install_dir]/ixia/ixnetwork/[version]/lib/PythonApi. User will need to manually install the IxNetwork.py file. Normally, the file will be installed to the standard location for third-party Python modules. This locationvaries by platform and by how Python was built/installed. On Linux/UNIX (and Mac OS X, which is also /UNIX-based), it also depends on whether the module distribution beinginstalled is pure Python or contains extensions ("non-pure"): Platform Standard installation location Default value-------- ------------------------------ -------------Linux/UNIX(pure) prefix/lib/pythonX.Y/site-packages /usr/local/lib/pythonX.Y/site-packages/IxNetworkLinux/UNIX(non-pure) exec-prefix/lib/pythonX.Y/site-packages /usr/local/lib/pythonX.Y/site-packages/IxNetworkTCL
Linux/UNIX Ruby API Installation Notes
IxNetwork Linux/UNIX installer also delivers the Ruby API under the installation directory [install_dir]/ixia/ixnetwork/[version]/lib/RubyApi. User will need to manually install the IxNetwork.rb file. Normally, the file will be installed to the standard location for third-party Ruby modules. This locationvaries by platform and by how Ruby was built/installed. User can also add in the script the location to the IxNetwork Ruby library $:.unshift '<the folder where IxNetwork.rb is>'require 'IxNetwork'
Linux/UNIX Perl API Installation Notes
IxNetwork Linux/UNIX installer also delivers the Perl API under the installation directory [install_dir]/ixia/ixnetwork/[version]/lib/PerlApi. User will need to manually install the IxNetwork.pl file. Normally, the file will be installed to the standard location for third-party Perl modules. This locationvaries by platform and by how Perl was built/installed. User can also add in the script the location to the IxNetwork Perl library use lib "<the folder where IxNetwork.pl is>";use IxNetwork;
REST API Installation Notes
IxNetwork.exe process must be started with the following argument: -restPort [tcp port number]Optional arguments: -restOnAllInterfaces -restTraceSupport for: GET, POST, PATCH, DELETE, OPTIONS methodsAutomation language of choice must support the above methodsBase URL: http://localhost:<tcp rest port number>/api/v1/sessions/1/ixnetworkNotes:- The first time IxNetwork Web Edition is installed on the VE Chassis the installation will take longer due to the installation of dependencies- The VE Chassis virtual machine must be provisioned with at least 4 vCPUs / 8 GB RAM for the install to be complete, IxNetwork Web Edition will use half of the provisioned resources- The vdisk size will have to be increased to at least 40GB to make room for the test results - The disk drive performance can influence the application performance, having a faster drive will provide the best results
Please refer to the IxNetwork documentation for guidance on its usage.
|+1 877 367 4942 - Toll-free North America|
|+1 818 871 1800 - Outside North America|
|+1.818.871.1805 - Fax|
|Global Support ||+1 818 595 2599 || |
|APAC Support ||+91 80 4939 6410 || |
|Australia ||+61-742434942 || |
|EMEA Support ||+40 21 301 5699 || |
|Greater ChinaRegion || |
+400 898 0598
|Hong Kong ||+852-30084465 || |
|India Office ||+91 80 4939 6410 || |
|Japan Head Office ||+81 3 5326 1980 || |
|Korea Office ||+82 2 3461 0095 || |
|Singapore Office ||+65-6215-7700 || |
|Taiwan (local toll-free number) ||00801856991 || |
Please refer to our website at https://support.ixiacom.com/version/ixnetwork-933.You will be required to provide a login and password to enter this section of the website. If you do not have the username and password, please forward your request to mail to: firstname.lastname@example.org.
|AresONE and AresONE-High Performance 400GE chassis now support the new dotted port numbering format in common with all AresONE-S/AresONE-800G fixed chassis.|
|Interleaved FEC Support (RS-FEC-Int) per IEEE 802.3 Clause 161 has been added in IxExplorer and IxNetwork for AresONE 800GE QDD-C and AresONE 800GE OSFP800-C fixed chassis for 100GBASE-CR1 Mode.|
|KP4 FEC error insertion and PCS lane error generation support has been added in Novus and AresONE families of load modules along with support for restpy.|
|Hardware based MACsec solution over AresONE-P 400G/200G speed modes now supports the following features:•Dynamic key provisioning with MKA •MACsec traffic encryption/decryption at line rate with minimum frame size 64 bytes with Static SAK •MACsec traffic encryption/decryption at line rate with minimum frame size 64 bytes for 200G and 128 bytes for 400G, with MKA •GCM-AES-128/256 and GCM-AES-XPN-128/256 cipher support for both MKA and Static SAK •Non-zero Confidentiality Offset (30/50)•256 MACsec sessions per port|
|IXNETWORK-24774||In 400G MACsec mode with MKA, the minimum supported frame size is 256B for GCM-AES-128/256.|
|IXNETWORK-25328||When payload size of transmitted MACsec frames is less than or equal to the confidentiality offset value, Packet Tx and Byte Tx under MACsec Global Port Statistics are getting updated as 'Protected Packet Tx' and 'Protected Bytes Tx'. These should have been updated as 'Encrypted Packet Tx' and 'Encrypted Bytes Tx'.|
|IXNETWORK-25329||When MACsec payload size is less than or equal to the confidentiality offset value, E/C bits are not set for PCPU generated MACsec frames, for example: ARP.|
|IXNETWORK-25492||On restarting MACsec protocol, MACsec per port statistics does not always reset to 0. In such a case, the user needs to manually clear statistics after protocol start.|
|IXNETWORK-26283||In 400G MACsec mode with static SAK, the minimum supported frame size is 128B for GCM-AES-XPN-256 cipher.|
|IXNETWORK-25037||In 400G/200G MACsec mode, Inter Arrival Time does not show proper value.|
|IXNETWORK-26786||MKA peer rejects non-zero confidentiality offset distributed by a key server running MKA version 1.|
|IXNETWORK-25021||Latency values are higher than expected for both 400G and 200G MACSec modes.|
|IXNETWORK-26785||MKA session does not come up, if the configured 'CAK Name' data length is not in multiples of 4 bytes.|