Ixia Software Release Notes
IxNetwork 9.20
Build Number: 9.20.2112.6
IxNetwork 9.20 is an alignment release.
This release consolidates all releases since the last alignment release IxNetwork 9.10. It includes IxNetwork 9.10 updates 1 / 2 / 3 / 4, IxNetwork 9.12 / 9.14 / 9.15 / 9.16 / 9.18 and patch releases.
This release is primarily focused on expanding SDN coverage, addressing market demand in broadband access and 5G, enhancing VE infrastructure, improving infrastructure and web edition, as well
as delivering key customer requirements.
For a complete list of all the new features included in this release, please refer to the "What is New" section below.
- Continue to lead innovation with advanced SDN test solution - Introduced OSPFv2 Flex-Algo, OSPFv3-SR, OSPFv3-SRv6, G-SRv6, and gRIBI emulation, enhanced EVPN
with support of type 6/7/8/10 routes, expanded coverage with specification upgrade, and enhancement to existing protocol feature set in ISIS, Flex-algo, Netconf, PCEP, etc.
- Enhanced VE infrastructure - Finalized the DPDK-enabled traffic engine, added support for Google Cloud Platform and Microsoft Azure public clouds, included new drivers
for Intel E810 100G NICs, improved License Aggregation Mode for 100G licenses, refreshed existing platform coverage.
- Addressed new market requirement of disaggregated Broadband Network Gateway - Introduced vBRAS Control and User Plane Separation Protocol Emulation per China
Mobile specification, enhanced DHCPv4/v6 and L2TP emulations.
- Expanded Time Sensitive Network test coverage - Introduced Qbv test specification in Avnu conformance test library, enhanced PTP emulation with new ITU-T G.8275.2
telecom profile support, and added additional PTP statistics.
- Continued improvement in infrastructure and automation - New device wizard to create large configuration, expanded WebUI coverage with L1 settings view and protocol
grid filtering, improved API performance, and Wireshark upgrade.
Please see sections below for application and hardware compatibility, new features, resolved issues, and known issues.
Application Compatibility
The following application releases support IxNetwork 9.20:
Application |
IxNetwork 9.20 |
BPS |
9.20 |
HLTAPI |
9.20 |
IxANVL |
9.32 |
IxLoad |
9.20 |
IxOS |
9.20 |
IxVM |
9.20 |
Licensing |
5.40 |
Metronome |
2.2.1 |
Wireshark |
3.2.6 |
In addition, current interoperability and compatibility coverage for IxNetwork
9.20 can also be retrieved using the on-line compatibility tool.
Please contact Keysight for details.
Starting with version 8.10 EA, you must provide your credentials while starting the IxNetwork User Interfaces.
The credentials are validated using an e-mail based authentication mechanism. For details see Start IxNetwork section in the IxNetwork Getting Started Guide.
You must create an account before you start using IxNetwork. Select the Create new account option on the login page available at: login.ixiacom.com and enter your details.
You will receive an email. You can use the new account only after you verify the email address by opening the link in the verification e-mail received from "Ixia Identity".
If the client machine running IxNetwork is offline, a token is required to sign in. The token is a binary file, that can be obtained by signing in to login.ixiacom.com from a computer with Internet access and downloading the Offline Authentication Token.
Note: When signing in, or managing the account in a web browser, always confirm that you are doing so over a secure connection. Ixia does not ask for user name, password or other personal information via email.
Privacy Matters:
To improve the experience for customers and the quality of Ixia's products, data may be collected and stored by Ixia.
This typically includes data about the product usage and environment (such as operating system, browser, language), and personal data such as user name, email and IP addresses.
Only Ixia's IT, project managers and marketing worldwide will have access to this data.
When you first sign in to either application, you will be asked to consent to such data collection and use, and to the data transfer to Ixia in the United States.
You may withdraw your consent at any time and for any reason. Please refer to our privacy policy for more information and opt-out possibility (available at https://www.ixiacom.com/privacy-policy)
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 IxLicensing system, please refer to the "Ixia Licensing Management User Guide" provided with the Ixia software, or downloadable from the Ixia web site: http://www.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.ix@keysight.com.
Prerequisites
As part of the IxNetwork installation, the installer installs Microsoft SQL Express
and Microsoft .Net Framework on a client machine and Microsoft .Net Framework on a
chassis.
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 Installation
IxNetwork 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 either on a DVD-ROM or 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.
NOTE: If you are upgrading from a DVD-ROM, the installer will be launched
automatically. The files on the DVD-ROM will be the same files as the ones
unzipped by the above process.
Chassis Installation Requirements
When 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 Support
at support@ixiacom.com or 1-877-FOR-IXIA about appropriate upgrades.
NOTE: When installing from the DVD, some virus scanning configurations present
a malicious code alert during the execution of the Windows autorun feature. If
this occurs, right-click the DVD-ROM drive icon in Explorer and 'Explore'
the DVD. At the root of the DVD, double-click on the index.htm file.
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 8.1 Enterprise 64-bit (only for Ixia Virtual Chassis)
- 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.
Chassis Installation Notes
1. Install the required IxOS version.
2. Install IxNetwork, and the IxNetwork installer will automatically install the
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 Requirements
IxNetwork 9.00+ requires the user workstation to have the following minimum
system requirements. It is recommended to use the 'next higher' requirement for
improved performance.
IxNetwork application is qualified for running up to 7 days. It is recommended
to restart the application after 7 days for consistent operation.
System Requirements
Ixia Configuration |
Per User 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 specs
Data 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 server
Multi-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 2019 Server Standard 64-bit
- Windows 2016 Server Standard 64-bit
- Windows 2012 Server R2 Standard 64-bit (*)
- Windows 10 Pro/Enterprise 64-bit
- Windows 8.1 Enterprise 32-bit and 64-bit (*)
- Windows 7 SP1 Enterprise 32-bit and 64-bit
- Windows 7 SP1 Professional 32-bit and 64-bit
- Windows 7 SP1 Ultimate 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 configured
for 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.2
IxNetwork 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 ESXI6.0, or ESXI6.5 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: admin
5. To start the QuickTest session manually, click "New Test".
6. To start the IxNetwork API Server session manually, click "New API Server".
7. To start scripting, click "Download a client".
8. Make sure that all dependencies are installed before starting scripting.
9. Click on package downloads for the corresponding language.
10. Sample codes are given for each language and follow the steps.
Note: 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 Manager
2. 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
5. To start QuickTest session manually, click "New Test".
6. To start IxNetwork API Server session manually, click "New API Server".
7. To start scripting, click "Download a client".
8. Make sure that all dependencies are installed before starting scripting.
9. Click on package downloads for the corresponding language.
10. Sample codes are given for each language and follow the steps.
IxNetwork Web Edition can be deployed as a Docker container via the provided image
Note: IxNetwork Web Edition is supported as Docker container with CentOS and Ubuntu Distributions.
1. Copy the .tar file on the host
2. 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/Ubuntu
3. Decompress the .tar file: tar xjf <file.tar.bz2>
4. Load the image to docker: docker load -i </path/to/tar/file>
5. 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>
6. 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>
7. Open up a browser and connect to the configured IP.
8. Log in with credentials username: admin and password: admin
9. To start QuickTest session manually, click "New Test".
10. To start IxNetwork API Server session manually, click "New API Server".
11. To start scripting, click "Download a client".
12. Make sure that all dependencies are installed before starting scripting.
13. Click on package downloads for corresponding language.
14. Sample codes are given for each language and follow the steps.
15. 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 \
* The ip parameter assigns a specific IP to the container
** Name and Hostname are optional parameters
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
Display Requirements
Recommended screen resolution: 1920 x 1080
If 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 operate
properly, but they are not officially supported.
Linux/UNIX Tcl Client Installation Notes
IxNetwork comes with Linux platforms dedicated installer, which has the TCL
interpreter bundled. The installation instructions are described in the IxNetwork
Help 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.6
Instructions 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 the
same 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 location
varies 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 being
installed 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/IxNetwork
Linux/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 location
varies 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 location
varies 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 -restTrace
Support for: GET, POST, PATCH, DELETE, OPTIONS methods
Automation language of choice must support the above methods
Base URL: http://localhost:<tcp rest port number>/api/v1/sessions/1/ixnetwork
Please refer to the IxNetwork documentation for guidance on its usage.
Ixia Headquarters
|
Support
|
Please refer to our website at https://support.ixiacom.com/support-overview/product-support/downloads-updates.
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 mailto:support.ix@keysight.com.
9.20 Features
Access |
NGPF DHCPv6 client emulation now supports processing of Reconfigure message from DHCPv6 server. |
NGPF DHCPv6 emulation now supports configuring more than two pool sizes on the server side. |
Automation |
StatViewer options in Test Option window is now available in IxNetwork API. This includes StatFilter options, Advanced settings, Data Center settings, and Test Inspector settings. |
Automatically generating rest.py code snippet from a selected configuration object is now supported in WebUI. |
Infrastructure |
Improved the display of long Topology/Device Group/Protocols names with the option to abbreviate in the middle or at the end based on Preference option. |
NGPF SendPing for IPv4 and IPv6 is now enhanced with additional options like, Ping Count, Ping Interval, and Payload Size. |
NGPF now supports running protocols in parallel mode along with other protocols running in sequential mode in the same test. This allows running realistic subscriber emulation along with other routing/MPLS emulation for effective BNG testing. |
NGPF IPv6 emulation is enhanced to support fetching IPv6 Neighbor information and discovering Gateway IP using ICMPv6 Neighbor Solicitation (NS)/Neighbor Advertisement (NA), in addition to existing way of using Router Advertisement (RA) message. |
Advanced traffic wizard now supports configuring Inter Burst Gap with units like seconds, milliseconds, and microseconds in Rate Setup page. |
Advanced traffic wizard Packet Editor tab is enhanced with the new option in List pattern to import data using CSV for fields like IPv4/IPv6/MAC/integer/String. |
NGPF Device wizard is introduced to quickly create or modify large configurations with many components like, topologies, device groups, protocol stacks, and network groups. |
Neighbor discovery is introduced in port selection window to learn and displays connected neighbor through LLDP. |
IxNetwork-FT now supports Novus 100G load modules. |
Auto-negotiation preset is now added to Edit L1 Properties page for AresONE-S. |
NGPF GRE now supports receiving packets over a tunnel and forward it to another tunnel. |
L2 Security |
MACsec Key Agreement (MKA) protocol now supports keychain with timer based rollover of PSKs (CAK,CKN). |
MKA key server priority can now be changed on the fly when protocol is running. |
QuickTest |
Duration column per iteration available in the aggregated results and report |
Routing/Switching/MPLS |
NGPF ISIS emulation now supports a performance mode to gracefully receive large number of LSPs at high rate. This mode is supported for point-to-point networks for all scenarios except interaction with BGP-LS. |
NGPF RSVP-TE ingress LSR emulation is enhanced to create ERO from the RRO that is received in the RESV message and include it in subsequent PATH messages. |
NGPF RSVP-TE egress LSR emulation is enhanced to create RRO from the ERO that is received in the PATH message and include it in subsequent RESV messages. |
SDN |
NGPF OSPFv2 emulation now supports bi-directional configuration of TE (Traffic Engineering) fields for each simulated link. |
gRIBI (gRPC RIB Injection) emulation is introduced to validate injection of IPv4 AFTs, Next-Hop AFTs and Next-Hop-Group AFTs in the target RIB. |
TSN |
Avnu TSN Qbv test specification is now supported as part of IxNetwork Avnu Conformance Test Library. Support for 17 test cases are added in the first phase. |
Timing and Synchronization |
NGPF PTP master emulation is enhanced to support multiple slave IP address patterns so that master can communicate with slaves in multiple subnets. |
VM |
Support for IxNetwork-FT on Virtual Ports has been enhanced to allow test execution in an environment which has the DPDK Performance Acceleration option enabled. |
Support for IxNetwork-FT on Virtual Ports has been enhanced to use a Linux TCL Server deployed stand-alone or integrated into the vChassis / Native Linux Chassis. |
Support for Advanced Sequence Checking statistics for L23 Traffic has been added. These are available with and without DPDK Performance Acceleration enabled. |
Support for CLI Debug Commands has been improved. The user can now see the DMESG logs or the /VAR/LOG files using the CLI of the vChassis / vCard / vAppliance. |
Support for CLI License Server configuration has been improved. The user can now disable License Server validation upon initial configuration via the CLI. |
Support for DPDK Performance Acceleration has been enhanced by improving the performance and compatibility of the traffic engine across multiple AWS Instance Types. |
Support for DPDK Performance Acceleration has been enhanced by exposing multiple settings directly in the IxNetwork Web UI thus bypassing the REST API Browser. |
Support for DPDK Performance Acceleration has been enhanced by qualifying the Mellanox ConnectX-6 NICs running at 200 Gbps line speed on VMware ESXi 7.x platforms. |
Support for DPDK Performance Acceleration has been enhanced by upgrading the internal DPDK libraries from version DPDK 19.11 to version DPDK 20.11. |
Support for DPDK Performance Acceleration has been enhanced by exposing an option which allows users to select the default traffic engine for new configuration files. |
Support for DPDK Performance Acceleration has been enhanced by ensuring similar control plane scalability regardless of which traffic engine is used (Classic / DPDK). |
Support for OVA Image Definition has been improved. Multiple files are supplied for vCard / vAppliance to match the default vCPU values of IxNetwork VE / IxLoad VE. |
Support for Public Cloud platforms has been added for Google Cloud Platform. The product can now emulate protocols and generate traffic in this new environment. |
Support for Public Cloud platforms has been added for Microsoft Azure. The product can now emulate protocols and generate traffic in this new environment. |
Support for Public Cloud platforms has been enhanced within Amazon AWS Marketplace by publishing the products as part of the Keysight Technologies seller profile. |
Support for Public Cloud platforms has been enhanced within Amazon AWS Marketplace by enabling an extended list of common instance types across multiple products. |
Support for Public Cloud platforms has been enhanced within Amazon AWS Marketplace by providing deployment scripts in various formats (Cloud Formation / Terraform). |
Support for increased product security via Linux OS Hardening. The internal operating system has been updated and configured according to security best practices. |
Support for increased product security via Password Policy Enforcement. This ensures users must always change default passwords and no weak passwords are allowed. |
Support for increased product security via improved Log Collection. This is performed via a secure channel and works even if the vCard is disconnected from vChassis. |
Support for new Intel E810 series NICs running in PCI-PT or SR-IOV mode has been added. This includes all Intel E810 NIC models across 25G / 50G / 100G line speeds. |
Support for new TIER-1 1G Perpetual license has been added. This new license can be used when running in Perpetual Licensing mode or in License Aggregation mode. |
Support for new platforms KVM / CentOS 8.x and KVM / RHEL 8.x has been added. The previous versions KVM / CentOS 7.x and KVM / RHEL 7.x continue to be supported. |
Support for new platforms KVM / Ubuntu 20.04 LTS has been added. The previous versions KVM / Ubuntu 18.04 LTS and KVM / Ubuntu 16.04 LTS continue to be supported. |
Support for new platforms OpenStack Wallaby has been added. The previous OpenStack versions continue to be supported (vanilla variants and vendor specific variants). |
Support for new platforms VMware ESXi 7.x / VMware vCenter 7.x has been added. The previous versions VMware ESXi 6.x / VMware vCenter 6.x continue to be supported. |
Web Edition |
Global protocol start button is introduced. It can start all protocol instances, such as BGP, OSPF etc. |
Protocol grid filtering is now available in NGPF grids. |
TAP settings is now available under Advanced settings node in L1 settings view. |
Infrastructure
Bug Number |
Notes |
18922 |
ANCP protocol stack is not getting added properly using the wizard for device groups with an existing ANCP stack. |
18957 |
Support for learning neighbor from multicast Neighbor Solicitation message is not available. |
3777 |
Designer and Data Analysis has been made EOL. |
16864 |
In some scenarios, while running Wireshark with filter, it is unable to set the filter when data traffic is still running. As a workaround, set the filter first, and then start the capture. |
18516 |
LLDP should be disabled while running any kind of performance, regression, long Duration tests. It should be enabled only to fetch Peer information. |
19044 |
The existing attribute of guardrailEnabled has been moved from ::ixNet::OBJ-/statistics to ::ixNet::OBJ-/globals/statistics/advanced/guardRail. It has been renamed as enableGuardrail and the former has been deprecated. |
19076 |
If skip reboot options are enabled in the Debug window, namely, 1)Skip Port reboot in NGPF to NGPF 2)Skip Port reboot in NGPF to Classic, then all the ports should be manually rebooted once after making the changes. |
19255 |
Port may go into bad state if IPv4 traffic over Lag is running without any flow tracking. |
VM
Bug Number |
Notes |
933 |
Please configure VFs in VMware ESXi using the following command: esxcli system module parameters set -a -m i40enu -p "trust_all_vfs=1,1" |
18906 |
If startup of IxVM load module fails with "Invalid memory setting" error, make sure that sufficient memory is reserved. |
19185 |
While running packets with minimum frame size (64Bytes) and VLAN, the vmxnet3 driver from the VMware ESXi hosts add extra 4 bytes of padding at the end of the packet. |
19187 |
On protocol-heavy configurations some protocols like OSPF have a low timeout interval. If they do not receive the response quickly enough, they fail to negotiate. Workaround is to gradually start protocols using a setup rate. This is applicable on runs with SR-IOV. |
19085 |
The Topology Discovery function which displays Peer Information fetched via LLDP is not available on Virtual Ports. |
19182 |
In order to get VLAN and Promiscuous mode to work with Intel NICs (700 and 800 Series) on VMware ESXi environments, use the intnet plugin that can be downloaded from the Intel website. |
19183 |
In order to get VLAN and Promiscuous mode to work with Mellanox NICs (ConnectX-4, ConnectX-5, and ConnectX-6) on VMware ESXi environments, use the nmlxcli plugin that can be downloaded from the Mellanox website. |
19189 |
In KVM environments the NICs need to be unamanaged by Network Manager as NM sends DHCP Discover messages that will appear in Rx. |
19190 |
In KVM environments for Intel 700 and 800 series please make sure that the following settings are applied to the NICs on the host:
ip link set dev NIC_NAME up
ip link set dev NIC_NAME mtu 9000
ip link set dev NIC_NAME promisc off
ip link set dev NIC_NAME allmulticast off
ethtool --set-priv-flags NIC_NAME vf-true-promisc-support on
For SR-IOV VFs please apply the following settings:
ip link set dev NIC_NAME vf VF_ID trust on
ip link set dev NIC_NAME vf VF_ID spoofchk off |
19191 |
The Physical Function (PF) driver on Intel 800 Series NICs can be unstable at times. The symptoms on VM ports can be connectivity issues or link down. When this happens, verify the dmesg output on the KVM hosts and then reboot the host. |
Automation
Bug Number |
Notes |
1342 |
HLAPI calls to start traffic is failing at times. |
917 |
Automation scripts are failing with 503 error when an OPTIONS query is being issued. |
1329 |
Md5Key authentication is not getting set in LDP using RestPy APIs with Python 3.6 version. |
1347 |
A single HLTAPI command is required to disable the automatic negotiation option on Novus 100G Cards. |
3093 |
HLAPI is facing error while configuring traffic over LAG port. |
3104 |
Using HLAPI, Static MACsec traffic frame size cannot be set higher than 200B. |
5260 |
An HLAPI command is required to drill down on Traffic Item names containing space. |
Infrastructure
Bug Number |
Notes |
278 |
PFC response time is slower when running traffic for long durations. |
375 |
There is a Rx statistics mismatch observed between packet group statistics and port statistics. |
1320 |
IxNetwork shows a port speed of 1000 Mbps when 100 Mbps is selected with AN enabled. |
17030 |
In some scenarios unexpected distribution in IMIX traffic is seen. |
18520 |
IxNetwork GUI becomes unresponsive under some race conditions. |
231 |
When all ports in the same resource group are unassigned from IxNetwork configuration, the resource group entry from the configuration is removed. |
462 |
When switching port speed from 100G to 40G using IxNetwork, the speed on the port does not change to 40G. |
17061 |
In IxNetwork web edition, the IEEE Defaults setting should be enabled twice to reset the defaults properly. |
17068 |
FC-FEC statistics are not displayed in IxNetwork for AresONE S400GD ports in 50GE NRZ mode. |
MPLS
Bug Number |
Notes |
708 |
IxNetwork sends MTU size as zero in targeted LDP label mapping message for some of the pseudowires. |
1020 |
In Rosen Draft MVPN emulation, generated traffic carries incorrect multicast destination MAC address. |
1319 |
IPv4 Traffic generation fails in certain scenarios where IxNetwork incorrectly tries to add MPLS labels in traffic. |
3589 |
Traffic generation fails when predefined resource 'EVPN multi-home P-PE' is used. |
Routing
Bug Number |
Notes |
115 |
PCPU error occurs when BGP is running and there is a run-time modification of BGP AS Path parameters in the VPN Route Range(s) followed by a Set for BGP VPN Route Range and BGP VRF Range(VPN Site) from FT Automation. |
1182 |
ISIS sends wrong MSD details in its Node MSD SubTLV on receiving packet containing SR-related sub-TLV: ISIS TLV 242 sub-TLV 23 Node MSD. |
1213 |
Port crashes when IS-IS route range is edited. |
2817 |
BGP emulation is sending incorrect Local-AS number though it is configured to send the AS number 125. |
13941 |
PCPU error happens while recieving high scale packets from the DUT. |
SDN
Bug Number |
Notes |
3092 |
Inter-VLAN traffic is not generated in EVPN VXLAN emulation if there is a default gateway in the data center fabric. |
1409 |
EVPN VXLAN traffic carries wrong VNI and outer IP addresses if custom multiplier for BGP peer is set to more than one. |
3107 |
At times, BGP route constraint capability does not work properly for EVPN VPWS. |
TSN
Bug Number |
Notes |
16941 |
Avnu Automotive conformance test cases fqtss_1_2_9_1 and fqtss_1_2_9_2 incorrectly compute burst time gap between frames. |
3094 |
Avnu Automotive conformance test case gptp_test_auto_1as_com_c_12_1_a becomes unresponsive while running. |
19157 |
TSN conformance test case qbv_1_2_4_b shows incorrect expected frame count for one of the gates under test. |
Timing and Synchronization
Bug Number |
Notes |
2820 |
At times, a very high path delay is reported in PTP Drill Down statistics because of incorrect computation of Neighbor Rate Ratio in gPTP emulation. |
1381 |
IxNetwork PTP master clock emulation sends Pdelay_Resp message twice in response to Pdelay_Req message. |
VM
Bug Number |
Notes |
19181 |
Fixed an issue that caused RFC QuickTests to not start while using Virtual Ports with the DPDK Performance Acceleration option enabled. |
19215 |
Fixed an issue that caused SSH failures into the Virtual Test Appliance after performing deployment on oversubscribed compute hosts. |
19219 |
Fixed an issue that caused the Virtual Load Modules to continuously reboot as soon as they were attached to the Virtual Chassis. |
1226 |
Fixed an issue that caused different values to be displayed for Tx Frames / Rx Frames across the Traffic Item Statistics and Port Statistics views. |
19186 |
Fixed an issue that caused RFC QuickTests to show loss in Aggregated Results although Aggregated Tx Count / Aggregated Rx Count values were identical. |
19192 |
Fixed an issue that caused RFC QuickTests to automatically stop after a short period of time when the DPDK Performance Acceleration option was enabled. |
19220 |
Fixed an issue that caused traffic to continue to be sent although the corresponding Flow Groups were either suspended or paused. |
19196 |
Fixed an issue that caused traffic apply failures when running traffic with Custom Payload on Virtual Ports. |