Ixia Software Release Notes
IxNetwork 9.00
Build Number: 9.00.1915.16 (July 26, 2019)



About This Release

IxNetwork 9.00 is an alignment release. This release consolidates all releases since last 8.50 alignment release, including IxNetwork 8.50 EA Update 1/Update 2, IxNetwork 8.51 EA and IxNetwork 8.52 EA.
This release is primarily focused on delivering new IxNetwork Web-based UI, advanced SDN technologies, improved internet-scale test capability as well as other key customer requirements. 
For a complete list of all the new features included in this release, please refer to the -What's New- section below.
- Launch of IxNetwork Web UI - Enable user to run IxNetwork test directly from browser. Complete IxNetwork Web Edition for automation in Linux environment.
- Continue to lead innovation with advanced SDN test solution - Upgrade SRv6 test solution with latest specification and more protocol coverage.
- Validate internet routing table scale - 5x BGP route import scale improvement to stress DUT under Internet scale with real Internet routes.
- Expanded Time Synchronization solution for new markets and use cases - 1588v2/PTP SMPTE Profile for Broadcast Industry, enhanced troubleshooting capability and external time source.
- Enhanced TSN solution with endpoint test capability and more conformance test coverage.
- Uplift VE traffic performance - New DPDK-enabled L23 traffic engine to significantly improve throughput for smaller frame sizes.

Application Compatibility

NOTE: When you are using one or more of the applications below on a single chassis configuration, please use the correct application versions so they align to a common version of IxOS.
Application IxNetwork 9.00
BPS 9.00
HLTAPI 9.00
IxANVL Not Supported
IxChariot Not Supported
IxLoad 9.00
IxOS 9.00
IxVM 9.00
Licensing 5.20
Metronome 2.1
Wireshark 1.8
Starting from 7.51-EA release IxNetwork-FT and IxRouter (IxTclProtocol) APIs are declared as End of Development. So user should not use IxNetwork-FT GUI or IxOS TCL client to view or configure Routing Switching protocols. Users also should not try similar use cases using other Ixia tools e.g. IxOS HLT, IxAutomate which underneath uses IxRouter (IxTclProtocol) APIs. From any such client application if an user tries these unsupported use cases, it might also make the corresponding Chassis/IxServer unstable and hence other users who are connected to same chassis may also be impacted. For the latest compatibility information to include releases occurring after this date, please refer to the online Product Compatibility Matrix at the link below. An Ixia website account is required before accessing. http://www.ixiacom.com/support-overview/product-support/product-compatibility-matrix

IxNetwork Load Module Support

The following load modules are support by IxNetwork application. ***IxNetwork Next Generation Protocol Framework (NGPF) is supported on cards where per port memory is at least 256MB.***
Module Type Supported Function Module Part Number
Virtual Port Control / Stateless Data Plane Testing Ixia Virtual Load Module, Ixia Virtual Test Appliance
AppLibrary Ixia Virtual Load Module, Ixia Virtual Test Appliance
ImpairNet Control Plane Testing/Stateless Data Plane EIM40G2Q, EIM10G4S, EIM1G4S
HSE Control Plane Testing HSE40/100GETSP1-01, HSE40GEQSFP1-01, Xcellon-FlexAP10/4016SQ 10GbE SFP+/ 40GE QSFP+, Xcellon-FlexFE40G4Q 40GE QSFP+, Xcellon-LavaAP40/100GE2RP, Xcellon-Lava AP40/100GE2P-NG FUSION, Xcellon-Flex 10/40G Reduced Performance, Xcellon-Multis XM100GE4CXP 100-Gigabit Ethernet, Xcellon-Multis XM100GE4CXP+FAN 100/40-Gigabit EthernetXcellon-Multis XM40GE12QSFP+FAN 40-Gigabit Ethernet, XMR10GE32SFP+FAN, XMR10GE16SFP+FAN, XMR10GE32SFP+FAN+40G, XMR10GE16SFP+FAN+40G, XMR40GE12QSFP+, XMR40GE6QSFP+, NOVUS100GE8Q28+FAN 8-port QSFP28 100GE, NOVUS-R100GE8Q28+FAN, K400 CFP8-400GE, K400 CFP8-R400GE, K400 QSFP-DD-400GE, K400 QSFP-DD-R400GE, NOVUS10/1GE4DP, AresONE
Stateless Data Plane Test HSE40/100GETSP1-01, HSE40GEQSFP1-01, Xcellon-FlexAP10/4016SQ 10GbE SFP+/ 40GE QSFP, Xcellon-FlexFE40G4Q 40GE QSFP+, Xcellon-LavaAP40/100GE2RP , Xcellon-Lava AP40/100GE2P-NG FUSION, Xcellon-Flex 10/40G Reduced Performance, Xcellon-Multis XM100GE4CXP 100-Gigabit Ethernet, Xcellon-Multis XM100GE4CXP+FAN 100/40-Gigabit Ethernet, Xcellon-Multis XM40GE12QSFP+FAN 40-Gigabit Ethernet, XMR10GE32SFP+FAN, XMR10GE16SFP+FAN, XMR10GE32SFP+FAN+40G, XMR10GE16SFP+FAN+40G, XMR40GE12QSFP+, XMR40GE6QSFP+, NOVUS100GE8Q28+FAN 8-port QSFP28 100GE, NOVUS-R100GE8Q28+FAN, K400 CFP8-400GE, K400 CFP8-R400GE, K400 QSFP-DD-400GE, K400 QSFP-DD-R400GE, NOVUS10/1GE4DP, AresONE
AppLibrary Xcellon-Flex AP10/4016SQ 10GbE SFP+/ 40GE QSFP+, Xcellon-FlexAP10G16S 10GbE SFP+, Xcellon-Lava AP40/100GE2P-NG FUSION 40/100GE CFP 2-ports load module, Xcellon-Multis XM10/40GE12QSFP+FAN 40-Gigabit Ethernet native QSFP, Xcellon-Multis XM10/40GE6QSFP+FAN 40-Gigabit Ethernet native QSFP, 4-ports 100GE, 12-ports 40GE, 100GE QSFP28, 4-port, single rate (Phase 1 HW), Xcellon-Multis XM100GE4CXP 100-Gigabit Ethernet, Xcellon-Multis XM100GE4CXP+FAN 100/40-Gigabit Ethernet, Xcellon-Multis XM40GE12QSFP+FAN 40-Gigabit Ethernet, XM10GE-FAN-OUT 10GE factory installed fan-out option for Xcellon-Multis load modules, NOVUS100GE8Q28+FAN 8-port QSFP28 100GE, K400 CFP8-400GE, K400 CFP8-R400GE, K400 QSFP-DD-400GE, K400 QSFP-DD-R400GE, NOVUS10/1GE4DP, AresONE
10G Ethernet Control Plane Testing LSM10GXM2XP-01, LSM10GXM4XP-01, LSM10GXMR2-01, LSM10GXMR4-01, LSM10GXM8XP-01, LSM10GXMR8.03, 10GBaseT-ADAP-01, LSM10GXM2S-01, LSM10GXM4S-01, LSM10GXM8S-01, LSM10GXMR2S-01, LSM10GXMR4S-01, LSM10GXMR8S-01, NGY-NP2-01, NGY-NP8.03, LSM10GXM2GBT-01, LSM10GXM4GBT-01, LSM10GXM8GBT-01, LSM10GXMR2GBT-01, LSM10GXMR4GBT-01, LSM10GXMR8GBT-01, LSM10GXM8NG-01 NGY Fusion Enabled, LSM10GXM4NG-01 NGY Fusion Enabled, Xcellon-FlexAP10G16S, Xcellon-FlexFE10G16S, Xcellon-FlexAP10/4016SQ 10GbE SFP+/ 40GE QSFP+, Xdensity XDM10G32S, Xdensity XDM10G8S, Xcellon-Flex 10/40G Reduced Performance, LSM10GXM8S-NG NGY Fusion Enabled, LSM10GXM4S-NG NGY Fusion Enabled, LSM10GXM2S-NG NGY Fusion Enabled, NOVUS10/1GE16DP, NOVUS10/1GE8DP, NOVUS-NP10/1GE16DP, NOVUS10/1GE4DP, NovusONE Plus
Stateless Data Plane Test LSM10GXM2XP-01, LSM10GXM4XP-01, LSM10GXMR2-01, LSM10GXMR4-01, LSM10GXM8XP-01, LSM10GXMR8.03, 10GBaseT-ADAP-01, LSM10GXM2S-01, LSM10GXM4S-01, LSM10GXM8S-01, LSM10GXMR2S-01, LSM10GXMR4S-01, LSM10GXMR8S-01, NGY-NP2-01, NGY-NP8.03, LSM10GXM2GBT-01, LSM10GXM4GBT-01, LSM10GXM8GBT-01, LSM10GXMR2GBT-01, LSM10GXMR4GBT-01, LSM10GXMR8GBT-01, LSM10GXM8NG-01 NGY Fusion Enabled, LSM10GXM4NG-01 NGY Fusion Enabled, Xcellon-FlexAP10G16S, Xcellon-FlexFE10G16S, Xcellon-FlexAP10/4016SQ 10GbE SFP+/ 40GE QSFP+, Xdensity XDM10G32S, Xdensity XDM10G8S, Xcellon-Flex 10/40G Reduced Performance, LSM10GXM8S-NG NGY Fusion Enabled, LSM10GXM4S-NG NGY Fusion Enabled, LSM10GXM2S-NG NGY Fusion Enabled, NOVUS10/1GE16DP, NOVUS10/1GE8DP, NOVUS-NP10/1GE16DP, NOVUS10/1GE4DP, NovusONE Plus
AppLibrary LSM10GXM2GBT-02, LSM10GXM2NG-01 NGY - Fusion Enabled, LSM10GXM2S-01, LSM10GXM2SNG, 2-PORT FUSION 10GE SFP+ MODULE, LSM10GXM2XP-01, LSM10GXM4GBT-02, LSM10GXM4NG-01 NGY Fusion Enabled, LSM10GXM4S-01, LSM10GXM4SNG,4-PORT FUSION 10GE SFP+ MODULE, LSM10GXM4XP-01, LSM10GXM8GBT-02, LSM10GXM8NG-01 NGY Fusion Enabled, LSM10GXM8S-01, LSM10GXM8SNG,8-PORT FUSION 10GE SFP+ MODULE, LSM10GXM8XP-01, NGY-NP2-01, NGY-NP8.03, NOVUS10/1GE16DP, NOVUS10/1GE8DP, NOVUS-NP10/1GE16DP, NOVUS10/1GE4DP, NovusONE Plus
10/100/1G Ethernet Control Plane Testing LSM1000XMVR4-01, LSM1000XMVR8.03, LSM1000XMVR12-01, LSM1000XMVR16-01, ACCELERON-NP-01 (Non-Aggregate Mode), LSM1000XMSP12, LSM1000XMVDC4, LSM1000XMVDC4-01, LSM1000XMVDC8.03, LSM1000XMVDC8, LSM1000XMVDC12, LSM1000XMVDC16, LSM1000XMVDC16NG, Xcellon-Ultra NP-01, Xcellon-Ultra XP-01, LSM1000XMVDC4NG - Fusion Enabled, LSM1000XMVAE8, LSM1000XMVAE16, NOVUS10/1GE16DP, NOVUS10/1GE8DP, NOVUS-NP10/1GE16DP, NOVUS10/1GE4DP
Stateless Data Plane Test LSM1000XMVR4-01, LSM1000XMVR8.03, LSM1000XMVR12-01, LSM1000XMVR16-01, ACCELERON-NP-01 (Non-Aggregate Mode), LSM1000XMSP12, LSM1000XMVDC4, LSM1000XMVDC8, LSM1000XMVDC12, LSM1000XMVDC16, Xcellon-Ultra NP-01, Xcellon-Ultra XP-01, LSM1000XMVDC4NG - Fusion Enabled, LSM1000XMVAE8, LSM1000XMVAE16, NOVUS10/1GE16DP, NOVUS10/1GE8DP, NOVUS-NP10/1GE16DP, NOVUS10/1GE4DP, Novus One Plus
AppLibrary LSM1000XMVDC16NG, LSM1000XMVDC4NG, LSM1000XMVDC4, LSM1000XMVDC8, LSM1000XMVDC12, LSM1000XMVDC16, NOVUS10/1GE16DP, NOVUS10/1GE8DP, NOVUS-NP10/1GE16DP, NOVUS10/1GE4DP, Novus One Plus
Fiber Channel Control / Stateless Data Plane Testing FCMGXM4S-01, FCMGXM8S-01
Native IxOS XGS2-HSL / XGS12-HSL / XGS2-SDL / XGS12-SDL NOVUS100GE8Q28+FAN, XMR10GE16SFP+FAN, XMR10GE32SFP+FAN, XMR40GE12QSFP+, XMR40GE6QSFP+, XM10/40GE12QSFP+FAN, XM10/40GE6QSFP+FAN, XM100GE4CFP4 100GE, XM100GE4CFP4+ENH, XM100GE4CXP, XM100GE4CXP+FAN, XM100GE4QSFP28+ENH, XM100GE4QSFP28, XM40GE12QSFP+FAN, NOVUS-R100GE8Q28+FAN, Xcellon-FlexAP10G16S, Xcellon-FlexFE10G16S, Xcellon-FlexAP10/4016SQ 10GbE SFP+/ 40GE QSFP+, Xcellon-Ultra NP, NOVUS10/1GE16DP, NOVUS10/1GE8DP, NOVUS10/5/2.5/1/100M16DP, NOVUS10/1GE4DP
Please contact Ixia for details.

User Authentication

Starting with version 8.10EA, users of IxNetwork applications are required to authenticate when starting the applications' user interfaces, using an e-mail based authentication mechanism. 
A login window is presented when a user starts IxNetwork and the user will need to enter the registered e-mail address and the associated password. 
 
First time users need to create a new account, which can be done online at login.ixiacom.com; 
this link is available on the login window. A new account can be used only after the user verifies the e-mail 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 at 
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)

 

Licensing

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@ixiacom.com.
 

Installation Notes

  

Prerequisites

As part of the IxNetwork installation, the installer installs Microsoft SQL Express and Microsoft .Net Framework 4.8 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 15
ESXi 6.0+/KVM V/Docker 15
* on chassis assumes only that same chassis is used in 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 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 75 or newer
Mozilla Firefox 49 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.

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. Make sure the interface has promiscous mode enabled 3. 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: docker run --net <bridge name> \ --ip <container ip> \ --hostname <hostname> \ --name <container name> \ --privileged \ --restart=always \ --cap-add=SYS_ADMIN \ --cap-add=SYS_TIME \ --cap-add=NET_ADMIN \ --cap-add=SYS_PTRACE \ -i -d \ -v /sys/fs/cgroup:/sys/fs/cgroup \ -v /var/crash/=/var/crash \ -v <host configs location>:/root/.local/share/Ixia/sdmStreamManager/common \ -v <host results location>:/root/.local/share/Ixia/IxNetwork/data/result \ -v <host settingslocation>:/root/.local/share/IXIA/IxNetwork.Globals \ --tmpfs /run \ <image name> 6. Open up a browser and connect to the configured IP. 7. Log in with credentials username: admin and password: admin 8. To start QuickTest session manually, click "New Test". 9. To start IxNetwork API Server session manually, click "New API Server". 10. To start scripting, click "Download a client". 11. Make sure that all dependencies are installed before starting scripting. 12. Click on package downloads for corresponding language. 13. Sample codes are given for each language and follow the steps. * 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

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

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. Make sure the interface has promiscous mode enabled 3. 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: docker run --net <bridge name> \ --ip <container ip> \ --hostname <hostname> \ --name <container name> \ --privileged \ --restart=always \ --cap-add=SYS_ADMIN \ --cap-add=SYS_TIME \ --cap-add=NET_ADMIN \ --cap-add=SYS_PTRACE \ -i -d \ -v /sys/fs/cgroup:/sys/fs/cgroup \ -v /var/crash/=/var/crash \ -v <host configs location>:/root/.local/share/Ixia/sdmStreamManager/common \ -v <host results location>:/root/.local/share/Ixia/IxNetwork/data/result \ -v <host settingslocation>:/root/.local/share/IXIA/IxNetwork.Globals \ --tmpfs /run \ <image name> 6. Open up a browser and connect to the configured IP. 7. Log in with credentials username: admin and password: admin 8. To start QuickTest session manually, click "New Test". 9. To start IxNetwork API Server session manually, click "New API Server". 10. To start scripting, click "Download a client". 11. Make sure that all dependencies are installed before starting scripting. 12. Click on package downloads for corresponding language. 13. Sample codes are given for each language and follow the steps. * 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

Tcl/Perl/Python/Ruby/REST Support for Client Applications

IxNetwork Windows GUI client must be started in API Server mode. 

Tcl/Perl/Python/Ruby : 
IxNetwork.exe process must be started with the following argument: -tclPort {tcp port number}

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

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 mailto:support@ixiacom.com.

What's New in IxNetwork

9.00 Features

5G
eCPRI message generation now supports eCPRI over Ethernet.

Access
Bonded GRE HG (Home Gateway) emulation has been added as per RFC 8157 to test Hybrid Access Aggregation Point (also known as Hybrid Access Gateway). This emulation enables DHCP subscriber over Bonded GRE tunnels of fixed network and mobile network connections for increased access capacity and improved reliability.
NGPF IPTV emulation now allows user to send Join and Leave in a single packet for IGMPv3 and MLDv2
NGPF PPPoE emulation now supports custom TLV profile with a set of build-in TLVs. The G.FAST TLVs and PON TLVs defined in draft-lihawi-ancp-protocol-access-extension-01 are included in built-in TLVs. If the same TLV is configured in both PPPoE protocol grid and TLV profile, then TLV profile will take precedence and will be included in PPPoE messages.
NGPF ANCP emulation now allow infinite re-dial on receiving TCP RST from DUT.
NGPF 802.1x emulation is enhanced to support different authentication modes for different ports to allow more flexibility
NGPF ANCP emulation now allow sending PON type TLV and/or DSL type TLV regardless of Tech Type to emulate various OLT behaviour.
Broadband Control plane QT session capacity test is now supported in NGPF.
NGPF ANCP emulation now supports 'None' as Tech Type for Subscriber Line Characteristics.
NGPF DHCPv6 emulation now support sending Request message immediately after receiving Advertisement message
Session Lifetime feature for Access protocols is enhanced to support large scale of subscribers to mimic real world condition

AresONE QSFP-DD and AresONE QSFP-DD High Performance fixed chassis
IxNetwork now supports Pre2, Post2, and Post3 tap settings for AresONE QSFP-DD, AresONE QSFP-DD High Performance, and AresONE OSFP.
Added support for the new AresONE T400GP-4P-QDD, 4-port, 400GE high performance fixed chassis model with native QSFP-DD 400GE physical interfaces, with L1-3 support. Provides complete protocol coverage with very high scale performance protocol emulation for routing, switching and access protocols. (944-1178)
Support for the new Common Management Interface Specification (CMIS) 4.0 has been added to all AresONE products. CMIS auto-detection of inserted CMIS 3.0 or 4.0 programmed transceivers has also been added.

Automation
High Level API support of Bonded GRE
High Level API support for BGP large communities
IxNetwork Linux API server now supports running classic routing/bridging scripts.
High Level API support has been added for the BGP Random AS Path.

Data Center
VXLAN emulation now supports running over IPv6 as per RFC 7348 in unicast mode.

Hardware
NGPF control plane protocols support has been added for Novus-w

Infrastructure
NGPF Network Group now supports a route count per route range
Advanced Traffic wizard now includes binary and decimal value for IPv4 DSCP Class selector PHB for easy mapping using different formats
NGPF Scenario tree now allows user to rename Topology/Device Group/Network Group by pressing F2 or by right-click context menu
Improved value list UDF usage for Novus100/50/40/25/10G QSFP28 load module family and AresONE fixed chassis to support millions of traffic flows for various use cases
NGPF protocol grid now supports filter capability for easy management of configuration and learned info
A new option is added to allow use of an external capture viewer in addition to the default ixia provided Wireshark
NGPF Ethernet/IP stack now supports sending GARP or RARP to emulate VM mobility behavior in VMware and KVM environment
Traffic wizard now has a "UDF Resource Summary" which enables user to inspect User defined field (UDF) being used by the traffic configuration.
IxNetwork Protocol Grid pattern editor Custom pattern options are mutually exclusive but its not intuitive from the UI
Starting 9.00 release following features are supported only on non-EOD and non-EOL Load modules - SRv6 ISIS/L3VPN/EVPN/PCEP,1588/PTP SMPTE and eCPRI
IxNetwork now offers a new Web-based UI to open a test session from your browser. Together with QuickTest Web and API browser, IxNetwork now offers a Web Edition for protocol emulation and traffic test for manual and automated tests in Linux environment

MPLS
LDP emulation in both Classic and NGPF has been updated with default keepalive interval to be 60 seconds and default keepalive hold time to be 180 seconds.

QuickTest Web Edition
QuickTest Web now supports RFC 3918 Mixed Class Throughput
QuickTest Web now supports IMIX Frame Size for RFC2544 suite
QuickTest Web now supports CloudStorm 10/25/40/50/100G speed modes for RFC2544 suite
Simplified OVA/KVM IP change from the CLI by making all the parameters optional and use the initial value instead. Now the user is not required to provide all the parameters in order to change the IP address.
QuickTest Web now supports Packet Editor to create custom traffic encapsulation
RFC 2544 Throughput/Latency test now supports enhanced binary search with loss verification to separate resource exhaustion and transient (intermittent) event in virtual environment. It supports extra user configurable retries for binary search algorithm to reduce rate upon loss. This is available for both QuickTest and QuickTest Web
QuickTest Web report is enhanced with additional information including IxOS version, Load module used, and Tx Mode, as well as summary statistics for RFC2544 and RFC3918 Mixed Class Throughput test

QuickTests
QuickTest now supports RFC benchmark test over LAG ports with NGPF using existing mode

Routing/switching
NGPF BGP Route Import is enhanced to support millions of imported routes with better performance for high scale internet routing table test.
Enhanced LAG emulation now support automatic adjustment of the User configured traffic rate to avoid over-subscription of LAG member links and re-balancing of traffic streams after LAG member link up followed by fail over.
BGP large community (RFC 8092) support is now added for NGPF BGP IPv4 Unicast, IPv6 unicast and BGP FlowSpec. It is also added for BGP Labeled Unicast as beta quality.
An external link is added in BGP route import wizard to view internet routing information in a browser window. User can copy the routes from the link into a file and then import it through the wizard.
A guard-rail has been implemented for running BGP internet route import tests. This guard-rail functionality provides guidance to user on the supported number of routes that can be imported on a per-port or per-GUI instance basis.

SDN
NGPF MPLS OAM is enhanced to support Seamless BFD Initiator and Responder. Emulated Responder is supported over ISIS-SR LSP. Emulated Initiator is supported over any type of MPLS LSP with manually configured MPLS label(s) for the LSP
PCEP emulation is enhanced to support the SRv6 control plane as per draft-negi-pce-segment-routing-ipv6-03.
NGPF EVPN and NG-MVPN are enhanced to support tenant routed multicast(TRM) which enables IP multicast forwarding in VXLAN fabric. The underlay multicast tunnel types supported in TRM mode are PIM-SM, PIM-SSM and ingress replication.
SRv6 emulation for ISIS SRv6 underlay and L3VPN service is updated to support draft-bashandy-isis-srv6-extensions-04 and draft-dawra-idr-srv6-vpn-04/05.
OSPFv2 SR performance has been improved significantly to support learning large number of Node/Prefix/Adjacency SIDs . It is now much faster to generate traffic and retrieve learned info.
SRv6 EVPN emulation is added for both EVPN VPWS and VPLS. This enables EVPN running over SRv6 underlay. It supports both version 04 and version 05 of draft-dawra-idr-srv6-vpn
NGPF ISIS emulation now sends multicast P2P Hello with 3-way Handshake enabled as a default behavior.
PCE emulation is enhanced to support stateless PCEP session by sending Open message without STATEFUL-PCE-CAPABILITY TLV.
NETCONF emulation now supports multiple sessions between same client and server using different user name and/or authentication type.
OSPFv2 SR information is now added in opaque LSA learned info.

Statistics
Statistics graph can now be saved as an image file in image formats bmp, wmf, emf, gif, jpeg, png, tiff
IxNetwork CSV Viewer now supports sorting of the data in statistics columns

TSN
Both split and merge functionality of a 802.1CB enabled switch, talker and listener can now be validated using IxNetwork. IxNetwork can act as a stream replicator and insert R Tag as defined in the 802.1CB standard. IxNetwork can also calculate loss between replicated flows and merged flows by using “FRER Duplicate Elimination” feature.
The TSN conformance package now has larger coverage in terms of new test cases for Frame Preemption, 802.1Qbv guard band validation, additional test coverage for 802.1CB and 802.1Qci standards.
IxNetwork 9.0 introduces the custom test case generation feature based on scenarios. The phase 1 implementation supports only 802.1Qbv scenarios.
Frame preemption feature in IxNetwork is now enhanced to support capability negotiation using SMD-V and SMD-R packet exchange.

Time Synchronization
NGPF 1588v2 (PTP) now supports Offset triggered logging for enhanced debugability.
NGPF 1588v2 (PTP) now supports sync with external time source through Metronome/GPS.
NGPF 1588v2 (PTP) now supports SMPTE ST-2059-2 profile for Professional Broadcast Application.

VM
IxNetwork VE is now support in AWS Public Cloud with Bring Your Own License (BYOL) model. The following features are supported 1. Unicast IPv4/IPv6 traffic with existing traffic engine as well as new DPDK-enabled traffic engine (Beta quality) 2. BGP4/BGP+ protocol emulation
New DPDK-traffic engine significantly boosts small frame performance and delivers line rate 10 Gbps using 128-bytes frames and line rate 40 Gbps using 1024-bytes frames. Includes support for VMware, KVM and OpenStack for all Intel NICs 1G / 10G / 25G / 40G and support for VMXNET3 and VIRTIO vSwitch drivers


Known Issue List

Access

Bug Number Notes
1490866 At times, ports might go to bad state when BGP, ISIS and few access protocols (like PPPoX) are running together. This issue happens only when all the following three conditions are met: (A) Ixia Load Modules with the Multi-NIC architecture are used. (B) The secondary port of a Resource Group (RG) 1 is connected to another secondary port of RG2. (C) An access protocol is configured on the Device Group (DG).
1501354 "Start All" is not supported for BondedGRE. As a workaround start BondedGRE devices and ensure tunnels are up before starting DHCP device.
1502809 Traffic based state change is not supported in BondedGRE. As a workaround, state change can be triggered through right click action.
1502810 In BondedGRE right click actions for home gateway are defined at both the Device Groups(DG). But it should be treated as action for one home gateway session. Due to this limitation, the right click actions triggered from either DG will have the identical functionality.
1511177 HLAPI configuration of NGPF ANCP emulation saved in 8.50-Update2,will not work in 9.00. But configuration saved in ixncfg format in 8.50-Update2 will continue to work in 9.00.

Automation

Bug Number Notes
1511462 Using API Server Quick Test is currently supported for NGPF protocols and Use Existing mode: RFC2544, RFC2889 fully meshed, one to many, many to one, partially meshed, RFC3918 Mixed Class Throughput. For QT Web the following tests are supported: RFC2544, RFC2889 Address Rate, Address Cache, RFC3918 Mixed Class Throughput, Group Join/Leave Delay, Traffic Test, RFC7747 BGP Rib-In-Convergence, Failover Convergence
1516390 Setting the flag -closeserverondisconect to false while connecting to Linux API server may result in a memory leak after running many tests in same session.
1516532 IxNetwork file upload, config load from script against Linux API server or REST port of Windows API server will fail from TCL distribution with http package of version 2.9.0 ( https://core.tcl-lang.org/tcl/tktview/f81beca7afabb3d2d395bd979607eda184622f7a ). Recommend to use http package lower than 2.9.0 or Keysight provided TCL distribution.
1516554 TCL-8.6 TLS package version needs to be 1.6.7 for secure connection with IxNetwork Linux API server.

Capture

Bug Number Notes
1505034 In 9.00 release, Ixia Wireshark must be installed to have full capture capabilities in IxNetwork. Ixia Wireshark can be downloaded from Ixia download site. If there is no compatible Ixia Wireshark installed on the system, attempting to view a capture will result in following error: "There was an error while opening Wireshark: This feature requires Wireshark integration. Please install Wireshark from Ixia website".

Data Center

Bug Number Notes
1510932 On the same Ethernet stack, VXLAN over IPv4 and VXLAN over IPv6 are not supported.
1516878 Data Center Mode is not supported in IxNetwork for K400 load module on 400G mode.

Infrastructure

Bug Number Notes
1490447 Running a large number of tests with IxNetwork Web installed on an XGS SDL chassis can result in intermittent failures due to the WebSocket connection being closed.
1507898 In certain operations (like capture browsing), Linux API Server is slower than Windows API Server.
1511609 In IxNetwork CSV Viewer, to apply "Group By This Column" option on another column, first ungroup the previously grouped columns.

Installation

Bug Number Notes
1517470 KB2919355 and KB3172729 updates are mandatory for IxNetwork installation on Windows Server 2012 R2 Standard.

Native IxOS

Bug Number Notes
1529342 When restoring saved tap settings with different values per lane, the value of the first lane gets applied to all lanes. In order to update the lanes each with their custom settings, select a lane from the drop down just after the restoring the custom setting, and then press OK.

NewLoadModule

Bug Number Notes
1512780 For AresONE, portType name is changed from "atlasFourHundredGigLan" to "aresOneFourHundredGigLan" .
1525899 Classic 802.1x emulation is not supported on AresONE-P.
1530127 Sometimes port can go to unresponsive state while starting protocols over L2VPN in a scaled scenario.
1536669 AresONE-HP - In large port configuration while starting traffic we may see some residual stats for a few moments.Workaround is to wait for some time or stopping traffic will result in proper stats.

QuickTest Web Edition

Bug Number Notes
1495394 In some cases, when using Custom IMIX with RFC 2544 Back to Back test, the Iteration Graph is empty.
1500444 Selecting a particular Iteration graph in a QuickTest Web session may not always result in corresponding iteration in left pane being selected for display.
1501579 Sometimes selecting last page number in Flow Details view may not result in corresponding page to be displayed. As a workaround repeat the same action.
1502461 Sometimes traffic statistics of the previous iteration is shown prior to starting traffic for the current iteration.
1502631 During Apply Traffic phase, certain statistics may be shown in Summary Stats view. This may be ignored.
1504863 While using QuickTest Web in Google Chrome, if any GUI flickering is experienced, disabling hardware acceleration in settings may solve the problem.
1513147 True View Convergence values differ when RFC 7747 Convergence test is run against ECMP and in Distributed modes.
1515732 In QuickTest Web, after starting Capture, the Capture Panel needs to be closed and reopened again so as to a) either stop capture or b) view the capture files.
1527755 When QuickTest run is in progress, if browser is refreshed QuickTest might show a message "Missing SRC/DST, Invalid Traffic". This message can be ignored as it does not affect the test run.

Routing/switching

Bug Number Notes
1487314 In a network group connected to BGP, OTF (On-the-fly) operations may not work correctly in a large selection of route ranges (few hundred thousands). User can break it down to multiple OTF operations, each containing around 100K route entries. If the requirement is to withdraw/re-advertise selection of all routes at one go, then use the "Age Out Routes" and "Readvertise Routes" options from right-click menu.
1495280 IxNetwork GUI may become unresponsive when configuring high number (~1 million) of BGP routes using statistical route distribution with (A) “Skip Loopback” and “Skip Multicast” options are enabled and (B) “Address Count per Route Range” set to non-default. For generating high number of SRD routes without loopback or multicast addresses, keep the “Address Count per Route Range” to minimum (suggested default value of 1) and increase “Route Range Count per Device” to get the desired scale.
1502390 Importing BGP routes for multiple peers in round-robin way through the NGPF BGP route import wizard works well for upto 500 peers. If there are more peers, then routes get imported but few routes may get missed out during withdrawal or re-advertisement operations.
1503800 Port CPU may go to bad state if BGP protocol is attempted to stop while a previously initiated route withdrawal or re-advertisement is still under process for large number of routes. As a workaround, wait for the withdrawal/re-advertisement to complete.
1505904 A GUI exception occurs when trying to delete BGP peer in dual stack scenario with network group connected to BGP peer.
1508578 NGPF BGP Route Import guard rail functionality is not available for Multi-NIC HW/VM load modules.
1512105 It takes significantly more time to stop OSPF protocol than to start it if high number of simulated topology routers are configured. For example, with 100K simulated topology nodes configured, it takes 1 minute to start the protocols and about 4 minutes to stop it.
1531365 While running scaled config in 50G speed mode and decreasing the multiplier on the fly, for PIM stacks the ports can go to bad state.

SDN

Bug Number Notes
1487750 Sourcing a low-level scriptgen file with OSPF Segment Routing configuration where mapping server is enabled does not load back the original configuration correctly. To avoid this issue, use ixncfg config files or scriptgen file with base64 serialization.
1501007 NETCONF: XML command snippet files cannot be sent at less than 1 second interval by the Controller, when triggered using low level API.
1515455 IxNetwork GUI may temporarily become sluggish and take time to load if BGP SRTE policy is enabled and device group multiplier is scaled to a high value like 10000 or more.
1516093 The resource "OSPFv2 Segment Routing Mapping Server" has been removed from resource repository in this release due to a problem with the resource not loading correctly.

Statistics

Bug Number Notes
1528357 The 'Fec Symbol Error Rate' and 'Fec Corrected bit Rate' values under "PCS Stats" may show the wrong value in IxNetwork. As a workaround, IxExplorer can be used to see these statistics. The values are correct in IxExplorer.

TCL

Bug Number Notes
1508705 For stopping BGP route ranges through API, "ageOutRoutes" exec needs to be used instead of "stop" exec.
1514999 The parameters of hexadecimal data type returned by getAttribute API for BGP Ethernet Segment will contain leading zeros.

Test Composer

Bug Number Notes
1517508 For packet decoder module in Test Composer to work properly, user might have to re-install Wireshark.

Traffic

Bug Number Notes
1499544 Performing Clear Statistics operation when traffic is running over LAG ports stops the traffic. The workaround is to enable Transmit Ignore Link Status in Port properties.
1511739 Deprecated API trafficStatViewBrowser is not supported in LinuxAPI Server.
1526259 Traffic configurations might fail to apply if the minimum frame size required is larger than predefined configuration even though they used to work in EOF timestamp mode.
1536828 In order to perform re-convergence tests, use clear statistics ribbon button instead of clear cp/dp convergence stats.

VM

Bug Number Notes
1483910 Selecting Floating Auto Instrumentation on VM ports will cause the latencies to display incorrect values. Latency testing is not recommended on this setting. Please use End of Frame setting for valid latency measurements.
1489639 Using the IxTclHal API for controlling a virtual chassis which contains a large scale virtual environment might lead to slowness in configuring the Ixia Virtual Load Modules. Please use the IxVM Deployment Wizard and the IxVM Chassis Builder to configure the virtual chassis in such a scenario.
1508909 The ESX vSwitch will truncate packets with bad IPv4 checksum, and will strip any payload that may follow after the TCP header. The Ixia Auto Instrumentation Signature is located inside the payload, and because the payload is removed then the AIS is not found, thus having 100% loss. The workaround is to run the same test on a KVM setup, on which the packets are forwarded correctly.
1509843 Due to underlying Host configuration L2-3 traffic performance might vary and may not be able to reach 10 Gbps L1 rate at 64 Bytes frame size.
1510229 IxNetwork VE does not support Quick Tests when using the performance accelerated DPDK-based Traffic Engine.
1511899 STP packets are dropped in SR-IOV due to using multicast MAC addresses.
1511982 If the driver does not support xstats (i40e, ixgbe) and at least one UDS is enabled, the i40e/i40evf driver drops bad packets (oversized / undersized / length errors / bad crc) and they do not reach Virtual Ports thus showing loss in traffic statistics.
1511984 Due to a limitation in DPDK all oversized frames( greater than 1518 Bytes) will be reported as good packets in Port Statistics, but 100% loss will be reported in Traffic View Statistics.
1512037 Due to incompatibility between the DPDK used by the New Traffic Engine and the i40e Intel driver on the Host you may see driver crashes. Workaround to this is using the i40e version 2.9.21 on the host.
1512039 Running AppLib traffic with Radius flows on Multi-NIC vCards will not show any TCP throughput. UDP Throughput will be visible. Workaround is to use separate vCards with single ports in the AppLib test topology.
1512422 AppLib L4-7 Traffic is not supported currently on the new DPDK Traffic Engine.
1513788 In order for multicast traffic to pass through Virtual Functions, configure the ALLMULTI flag on the Physical Function interface (ifconfig PF_INTERFACE allmulti).
1514171 IxNetwork VE traffic using existing non-DPDK traffic engine in AWS C5 instance does not go beyond 48000 frames per second even though C5 instances offer more bandwidth.
1515225 With DPDK-enabled new traffic engine in IxNetwork VE on AWS, jumbo frames Rx rate in Traffic Items Statistics might be incorrect.
1515441 With DPDK-enabled new traffic engine in IxNetwork VE on AWS C4 instances, IPv6 neighbor discovery does not work.
1517007 Before pressing the New Configuration button, make sure that all VXLAN protocols are stopped.
1517529 On Intel X550 boards communication between NIC ports may not work if DPDK VF is used based on kernel PF. Workaround on KVM based hypervisors is to disable MDD by running insmod ixgbe.ko MDD=0,0. On VMware hypervisors follow these steps: esxcfg-module --set-options "max_vfs=2,2 MDD=0,0" ixgbe, and then reboot host.

Web Edition

Bug Number Notes
1512841 When using Packet Editor in IxNetwork Web UI some parameters may be missing from the drop down list and are not available for editing.The workaround is to edit the parameters using the REST API interface.
1516359 In IxNetwork Web Edition, IPv4 addresses are not supported for ISIS-L3 Simulated topology.
1516365 When taking ownership of already owned ports, there is no notification sent to the owner of the ports.
1516436 TLV profile is not supported in this release of IxNetwork Web UI.
1516438 If one or more of the license servers used in the License settings are unreachable, it will take a while for the ports to connect. The user should wait for the ports to be connected before performing any other action in the UI.
1516439 Configuration files, captures and diagnostics cannot be downloaded when using an old Safari version(10.1). Version used should be 12.1.1 or higher.
1516444 In IxNetwork Web Edition, sometimes it takes longer to display "Chassis not available" message for unreachable chassis. During that time the page remains in loading state.
1531660 In IxNetwork WebUI, Port Summary and Per Port Stats may not be available if port speed mode is changed, reverted back and reconnected without clearing port ownership while traffic is running.
1536647 After the first install of the IxNetwork WebUI product, please go to the web platform administration page and manually restart the freshly installed IxNetwork WebUI application. Only after restarting the application you can use it properly.


Resolved Defect List

Access

Bug Number Notes
1503248 On Native IxOS chassis, classic 802.1x certificate based protocols were not coming up as the certificate directory structure was wrong.
1503976 Intermittently, port goes into bad state while running 802.1x tests on multi-Core Load Module.
1507539 PCPU goes into bad state when NGPF ANCP emulation is run on multi-Core Load Module.
1510434 PCPU goes into bad state when NGPF PPP is run on any Load Module.
1513295 NGPF ANCP flapping functionality does not work while doing OTF.
1516630 At times, IxNetwork GUI becomes unresponsive while running a classic PPPoE configuration in regression.
1516670 At times, NGPF DHCPv6 emulation stops sending packets while requesting for IPv6 address.

Automation

Bug Number Notes
1466592 When starting BGP VRF using API, from device level, some BGP peers do not start.
1504174 AS Number attribute in BGP Route Config modification from HLAPI does not work without setting Number of AS Number attribute.

Infrastructure

Bug Number Notes
1424391 In certain cases NGPF RFC2544 QT throws error with XMR2S ports when used port has less than required 256MB memory.
1462351 GlobalStream control for sequential scheduler configuration is not consistent between UI and automation.
1476817 Sometimes PCPU goes to a bad state when running DHCP.
1483011 Deleting a running quick flow group through API causes unpredictable traffic behavior.
1488235 CP/DP convergence statistics is not available.
1489555 Default CP/DP description displayed in IxNetwork GUI is incorrect.
1490830 Raw Traffic Item is unable to send streams of frame size 9216 Bytes when PFC is enabled.
1498215 In some corner cases, "Save As" IxNetwork configuration fails.
1500807 Device groups in the IxNetwork Scenario Editor re-position themselves after changing the multiplier.
1501311 IxNetwork GUI at times becomes unresponsive when 5 ports are added in classic configuration.
1503159 Traffic cannot be run on TSN enabled port when non-TSN ports available in the configuration are not part of topology.
1503195 While other streams are running, stopping Traffic stream through API becomes unresponsive,
1504389 When advanced sequence checking is enabled, all packets are declared as duplicates.
1506386 At times IxNetwork application closes unexpectedly while switching between BGP C-MAC Properties.
1507231 When LDP is running, IPv4 traffic flow cannot be generated.
1507799 QoS value in IP priority in Traffic Wizard Packet Editor is not getting updated when the value is changed.
1508287 IxNetwork GUI becomes unresponsive at times while opening and closing traffic options page and minimizing or maximizing the popup dialog box.
1510441 IxNetwork GUI becomes unresponsive when dialogue boxes pertaining to L1 Properties Tab goes out of screen.
1511380 Few columns in the Mac Pool Tab Grid are missing in IxNetwork GUI.
1512199 Linux API server becomes unresponsive when trying to generate a raw traffic item.
1512611 Unable to modify valueType to "repeatableRandomRange" through Rest.Py.

MPLS

Bug Number Notes
1486909 At times port goes to bad state on stopping RSVP-TE configured in scale.
1500454 IPv6 traffic is not generated between protocol interfaces of the device groups where LDP is also configured.
1500811 Port goes to bad state on starting RSVP-TE when RSVP-TE LSP configured in chained device group is connected to OSPF or IS-IS instead of Ethernet stack in the connected device group.
1507165 Traffic wizard does not create all flows if MPLS labels for some of the destination IPv4 addresses are not learned in LDP.
1511704 IxNetwork throws exception while trying to create IPv4 traffic in a topology where both RSVP-TE and BGP are present.
1512682 In MPLS label imposed on BGP/targeted LDP control packets, the MPLS EXP bit carries 1 instead of 6 .

Routing/switching

Bug Number Notes
1486444 Port goes to bad state if same "My Discriminator" is configured for more than one configured BFD session.
1488027 Port goes to bad state when BGP stack with a connected network group is deleted and the protocol is started.
1496286 BGP Flowspec routes are not re-advertised after session flap.
1499758 SR 830634 - Changing the multiplier of the Device Group leads to wrong ISIS MT-ID values.
1501640 For OSPFv3, incorrect number of intra-area routes are sent when interfaces are configured with both IPv4 and IPv6 addresses.
1501824 Four-Byte AS number in Export RT of BGP VRF sends out wrong value of 0 in packet.
1504951 The IPv6 L3VPN Route Range connected to the IPv4 BGP VRF is not started automatically when the BGP stack is started and therefore the IPv6 L3VPN routes are not advertised.
1506564 When ISIS stack is present in NGPF GUI, sometimes the GUI becomes unresponsive when all protocols are stopped from global stop option.
1509187 In OSPFv3 configured with large simulated topology configuration, not all LSA updates are generated at refresh time.
1513962 Unsolicited MLDv2 reports are sent to allow new source do not include configured source list.

SDN

Bug Number Notes
1490753 When advertising the BGP SRv6 VPN SID's locator in ISIS, the metric value of ISIS IPv6 reachability TLV for that locator route gets advertised wrongly. This issue is specific to IxNetwork VE ports only.
1502185 Few of the advertised EVPN routes do not carry configured communities in them.
1504148 With "Enable VLAN Aware Service" checkbox disabled, advertised EVPN routes still carry non-zero Ethernet Tag ID if configured so.
1504330 NETCONF Server fails to establish NETCONF session if it receives non-standard hello XMLs.
1511487 Port may go to bad state while stopping a topology with Tenant Routed Multicast configuration.
1512704 SR 804276 - Plain IP traffic Item contains MPLS stack when ISIS-SR is present along with BGP.

TSN

Bug Number Notes
1503126 The gate control list entry for test case qbv_c_1_1_1_a is incorrectly populated resulting in test case failure for Qbv conformance suite.
1503825 cleanDUT() utility function is not getting invoked at the end of test case run resulting in inconsistent DUT behavior.
1510447 Port speeds are not getting set to user defined values when auto negotiation is marked as disabled for TSN Conformance.
1511838 Dissector reports incorrect mCRC for fragments generated as part of Frame Preemption emulation.
1514598 Capture analysis fails for test case qbv_c_1_1_2_b due to incorrect parameter for Qbv conformance suite.
1514599 The gate control list entry for test case qbv_c_1_1_1_b is incorrectly populated resulting in test case failure for Qbv conformance suite.

Time Synchronization

Bug Number Notes
1501335 PTP Slaves are unable to handle negative value in correction field for PTP message header.
1510205 IP address mask and gateway fields are getting reconfigured while adding PTP protocol using HLAPI.
1511417 PTP throws "Failed clearing 1588 timestamp" error for a topology which consists of unavailable and unassigned ports.

VM

Bug Number Notes
1496539 During vMotion Operation, while Virtual Load Modules sends L23 Stateless Traffic, Virtual Load Module goes to bad state.
1514042 At times traffic is stopped while clearing statistics views.