Ixia Software Release Notes
IxNetwork 8.50 EA
Build Number: 8.50.1501.9 (September 14, 2018)



About This Release

IxNetwork 8.50 EA is an "Early Adopter" release. This release consolidates all releases since the last release train, including IxNetwork 8.41 EA, IxNetwork 8.41 EA Update 1 and IxNetwork 8.42 EA. 
This release is focused on delivering advanced SDN technologies, address key customer requirements and continuing to improve automation capabilities.
For a complete listing of all the new features included in this release, please refer to the 'What's New' section below.

- Continue to lead innovation with advanced SDN test solution - new test capabilities for NETCONF/  YANG, SRv6 network programming, and BIER (Bit Indexed Explicit Routing)

- Address key customer requirements - enhanced LAG test solution with single LAG configuration element and flow-based data traffic distribution and fail over across LAG member links

- Continue to enhance NGPF infrastructure - improved usability of navigating large configurations which simplify overall workflow and accelerates NGPF adoption

- Improved automation capability - support for Linux API server on IxNetwork Virtual Edition (VE), API Browser Traffic Widget support with Traffic Items and Flow Groups, merge Windows and Linux API
 server client libraries to a single one, simplified deployment, IxNetwork API support for TCL-8.6 and Python-3.6

- Continue to enhance VE infrastructure - Support IxNetwork VE inside Amazon AWS Public Cloud, improved capabilities for the Virtual Chassis Web UI (Broadcast Discovery / Mass Operations / 
Quick test web Edition / IxNetwork API server), and better support for Live Production Networks

- Addition of conformance capabilities for the evolving TSN ecosystem - a new test package designed containing conformance tests for IEEE 802.1Qbv, IEEE 802.1AS, IEEE 802.1CB.

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 IxOS 8.50 EA
BPS 8.50-EA
FLIX OS 2018.1.0.3 (XGS2-HS & XGS12-HS)
2018.1.78.12 (XGS2-HSL/XGS12-HSL/XGS2-SDL/XGS12-SDL/NovusONE/PSONE)
HLTAPI 8.50 EA
IxANVL 9.20 EA
IxChariot Not Supported
IxLoad 8.50 EA
IxNetwork 8.50 EA
IxVM 8.50 EA
Licensing 5.10 EA
Metronome 1.2 EA
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
OTN Control Plane Testing XOTN 100G OTN-Chassis Unit for OTU4/ODU4, XOTN 40G OTN-Chassis Unit for OTU3/ODU3, XOTN 40G/100G OTN-Chassis Unit for OTU3/OTU4
ImpairNet Control Plane Testing/Stateless Data Plane EIM40G2Q, EIM10G4S, EIM1G4S
HSE Control Plane Testing HSE40/100GETSP1-01, HSE40GETSP1-01, HSE100GETSP1-01, HSE40GEQSFP1-01, Xcellon-FlexAP10/4016SQ 10GbE SFP+/ 40GE QSFP+, Xcellon-FlexFE40G4Q 40GE QSFP+, Xcellon-Lava AP40/100GE2P, 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+, XMAVB10/40GE6QSFP+FAN, Xcellon-Multis XM100GE4CFP4 100GE CFP4 4-port single rate (Phase 1 HW), Xcellon-Multis XM100GE4QSFP28 100GE QSFP28 4-port single rate (Phase 1 HW), 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
Stateless Data Plane Test HSE40/100GETSP1-01, HSE40/100GETSPR1-01 40/100 GE Data Plane Only, HSE40GETSP1-01, HSE100GETSP1-01, HSE40GEQSFP1-01, Xcellon-FlexAP10/4016SQ 10GbE SFP+/ 40GE QSFP, Xcellon-FlexFE40G4Q 40GE QSFP+, Xcellon-Lava AP40/100GE2P, 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+, XMAVB10/40GE6QSFP+FAN, Xcellon-Multis XM100GE4CFP4 100GE CFP4 4-port single rate (Phase 1 HW), Xcellon-Multis XM100GE4QSFP28 100GE QSFP28 4-port single rate (Phase 1 HW), 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
AppLibrary Xcellon-Flex AP10/4016SQ 10GbE SFP+/ 40GE QSFP+, Xcellon-FlexAP10G16S 10GbE SFP+, Xcellon-Lava AP40/100GE2P 40/100 Gigabit Ethernet CFP load module 2-ports, 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, Xcellon-Multis XM100GE4CFP4 100GE CFP4 4-port single rate (Phase 1 HW), Xcellon-Multis XM100GE4CXP 100-Gigabit Ethernet, 4-ports Xcellon-Multis XM100GE4CXP+FAN 100/40-Gigabit Ethernet, 4-ports 100GE, 12-ports 40GE, Xcellon-Multis XM100GE4QSFP28, 100GE QSFP28, 4-port, single rate (Phase 1 HW), Xcellon-Multis XM40GE12QSFP+FAN 40-Gigabit Ethernet, Xcellon-Multis XM100GE4QSFP28+ENH, Xcellon-Multis XM100GE4CFP4+ENH, 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
10G Ethernet Control Plane Testing LSM10G1-01, LSM10GXM2XP-01, LSM10GXM4XP-01, LSM10GXMR2-01, LSM10GXMR4-01, LSM10GXM8XP-01, LSM10GXMR8.03, LSM10GR1-01, 10GBaseT-ADAP-01, LSM10GXM2S-01, LSM10GXM4S-01, LSM10GXM8S-01, LSM10GXMR2S-01, LSM10GXMR4S-01, LSM10GXMR8S-01, NGY-NP2-01, NGY-NP4-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
Stateless Data Plane Test LSM10G1-01, LSM10GXM2XP-01, LSM10GXM4XP-01, LSM10GXMR2-01, LSM10GXMR4-01, LSM10GXM8XP-01, LSM10GXMR8.03, LSM10GR1-01, 10GBaseT-ADAP-01, LSM10GXM2S-01, LSM10GXM4S-01, LSM10GXM8S-01, LSM10GXMR2S-01, LSM10GXMR4S-01, LSM10GXMR8S-01, NGY-NP2-01, NGY-NP4-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
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-NP4-01, NGY-NP8.03, NOVUS10/1GE16DP, NOVUS10/1GE8DP, NOVUS-NP10/1GE16DP, NOVUS10/1GE4DP
10/100/1G Ethernet Control Plane Testing LM1000STXS2, LM1000STXR4, ALM1000T8, ELM1000ST2, 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 NG (FUSION), 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 LM1000STXR4, LSM1000XMVR4-01, LSM1000XMVR8.03, LSM1000XMVR12-01, LSM1000XMVR16-01, ACCELERON-NP-01 (Non-Aggregate Mode), LSM1000XMSP12, LSM1000XMVDC4, LSM1000XMVDC8, LSM1000XMVDC12, LSM1000XMVDC16, LSM1000XMVDC16NG, Xcellon-Ultra NG (FUSION), Xcellon-Ultra NP-01, Xcellon-Ultra XP-01, LSM1000XMVDC4NG - Fusion Enabled, LSM1000XMVAE8, LSM1000XMVAE16, NOVUS10/1GE16DP, NOVUS10/1GE8DP, NOVUS-NP10/1GE16DP, NOVUS10/1GE4DP
AppLibrary LSM1000XMVDC16NG, LSM1000XMVDC4NG, LSM1000XMVDC4, LSM1000XMVDC8, LSM1000XMVDC12, LSM1000XMVDC16, NOVUS10/1GE16DP, NOVUS10/1GE8DP, NOVUS-NP10/1GE16DP, NOVUS10/1GE4DP
Fiber Channel Control / Stateless Data Plane Testing FCMGXM4S-01, FCMGXM8S-01
OC192 SONET Control / Stateless Data Plane Testing MSM10G1-01, MSM10G1-02
OC48 SONET Control / Stateless Data Plane Testing MSM2.5G1-01
OC3/12 SONET/ATM Control / Stateless Data Plane Testing LM622MR, LM622MR-512
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-Ultra NP, NOVUS10/1GE16DP, NOVUS10/1GE8DP, NOVUS10/5/2.5/1/100M16DP, NOVUS10/1GE4DP
Load modules with 32MB or less of memory are not supported by IxNetwork 6.20 EA or later. There are several models of Ixia OC-192 and 10G Ethernet modules in this category. Memory upgrades are available: - TRI-045: LMOC192c 128MB Memory Upgrade - TRI-046: LM10GE 128 MB Memory Upgrade 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

Ixia 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. NOTE: IxOS 5.00 SP2 and later versions of IxOS also require a license. Please read the IxOS release notes for license operation and installation instructions. IxNetwork 8.50 EA ships with Ixia Licensing 5.00 EA SP1 IxLicensing 5.00 EA SP1 upgrades IxLicensing 5.0 EA and earlier versions. If this is upgraded on release 3.xx, Ixia Licensing Utility (ILU) and License Server Plus (LS+) will replace Ixia Registration Utility (IRU) and License Server (LS). Some of the key benefits of this new licensing system are: - Simplified activation procedure - Improves offline activation using Request files. - Enhanced Host ID calculation to increase uniqueness of Host ID. - Allows remote activation of licenses - Allows configuration of Proxy settings 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.

Installing a License

Ixia Licensing 5.00 EA SP1 upgrades Ixia Licensing 5.0 EA and prior versions on the machines. If the setup is upgraded from versions prior to 5.00 EA SP1, the setup cannot be reverted to the previous version and will need to stay at 5.00 EA SP1 after the upgrade. Upgrade can be performed for following scenarios: - Ixia Registration Utility (IRU) to Ixia Licensing Utility (ILU) - Old version of Ixia Licensing Utility (ILU) to the latest version of Ixia Licensing Utility (ILU) In case of IRU to ILU upgrade, ILU will override IRU and its registration numbers will be migrated as activation codes in ILU. During installation the system checks the connectivity with Ixia Licensing web servers. Based on the connectivity, the migration can be performed using following methods: - Online Migration - Offline Migration

Prerequisite Installation Notes

Ixia Licensing 5.00 SP1 installs .Net 4.0 on Chassis and .Net 4.5.1 on Clients and VM Chassis. NOTE: Ixia Licensing 5.00 SP1 installs .Net 4.5.1 on client machines. If an older release of an Ixia product containing .Net 4.0 hotfix is installed on top of this release, .Net 4.0 hotfix installation may fail. The workaround is to uninstall .Net 4.5.1 and then reinstall the older release of Ixia product and then modify this release of Ixia Licensing.

Additional Documentation for Licensing

Please refer to our website at 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

  

Upgrading from a release prior to IXOS 5.10 SP2

To ensure proper operation of an Ixia chassis with IxOS 5.10 EA SP3 or later versions of IxOS 5.10 EA, prior to installing this release you must un-install all previous versions of Ixia applications, Ixia StatEngine, Ixia StatEngine PCPU packages and IxOS. You should use the Add/Remove utility in the Windows Control Panel. After the un-installations are complete the chassis must be rebooted.

Installation Notes for Windows

As part of the IxNetwork installation, the installer installs Microsoft SQL 2008 Express R2 SP2, Microsoft .Net Framework 2.0/3.5 SP1 and Microsoft .Net Framework 4.5.1 on a Client machine and Microsoft .Net Framework 4.0 on a Chassis. If you experience any issue related to the installation of these prerequisites, please refer to the following notes. NOTE: During installation you may be presented with a error dialog declaring a 1935 error has occurred. One possible cause of this is the presence of anti-adware or anti-virus software running on the target machine. Please disable these applications prior to your next installation attempt. NOTE: Microsoft .NET and Microsoft SQL 2008 Express can take several minutes to install. NOTE: Installation of .NET Framework service packs is not completed if you first install security update MS05-004. Please refer to the following Microsoft knowledgebase item to attempt resolution: 899619. NOTE: This release of IxNetwork installs .Net 4.5.1 on client machines. If an older release of IxNetwork containing .Net 4.0 hotfix is installed on top of this release, .Net 4.0 hotfix installation may fail. The workaround is to uninstall .Net 4.5.1 and then install the older release of IxNetwork and then modify/repair this release of IxNetwork. NOTE: On some Windows 2008 R2 systems, the installation may become blocked and the message "Please wait while the application is preparing for the first use" will be displayed. If this happens, please follow these steps: 1. Cancel the current installation. 2. Logon as an Administrator and open Control Panel, search for Group Policy and open Edit Group Policy link. 3. Navigate to Computer Configuration - Administrative Templates - Windows Components - Remote Desktop Services - Remote Desktop Session Host - Application Compatibility. 4. Double click on "Turn off Windows Installer RDS Compatibility" and make sure the option "Disabled" is selected. Click Apply and OK. 5. Restart the installation. NOTE: IxNetwork is supported only on machines having C: as system drive. Users may experience installation issues or functional issues in case the system drive is not C: on the destination machine.

IxNetwork Installation

IxNetwork has two components. The 'chassis' component needs to be installed on the Ixia chassis being used. The 'client' component needs to be installed on the user workstation where the IxNetwork GUI will be run. The installer will determine which is appropriate depending on which IxOS components are installed. Generally, when IxServer is installed, the IxNetwork 'chassis' component is installed. It is also required to install IxOS before installing the IxNetwork 'chassis' component. Since the IxNetwork 5.40 EA release, multi-version installation is supported. This release can be installed without uninstalling the 5.40 EA releases. If the client or server components are earlier releases than IxNetwork 5.40 EA, the software must be uninstalled before installing IxNetwork 7.40 EA+.

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. The installer package is in the form of a self-extracting ZIP file. To unzip the file, 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 7.40 EA+ on a chassis, a minimum of 512MB of installed RAM and 1.5GB of free disk space on Drive C: is required. In addition, be sure to have 1GB of temporary space available. In heavily-loaded chassis configurations, it is recommended to have 1GB RAM installed on the chassis. 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 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 XP Professional 32-bit SP3 (*) - Windows 7 Ultimate 32-bit - Windows 8.1 Enterprise 64-bit (only for Ixia Virtual Chassis) - CentOS 7 64-bit (only for Ixia Linux Virtual Chassis) (*) The following foreign languages are supported only on Windows XP Professional: - Chinese (traditional and simplified) - French - German - Hebrew - Italian - Japanese - Spanish - Swedish 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 Chassis. 3. If the required IxOS was already installed and running, restart IxServer.

Client Installation Requirements

IxNetwork 7.40 EA+ 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.

Single User - Minimum System Requirements

Single User Ixia Configuration System Requirements
Ports Flow Groups Flows CPU (# or cores) Memory (GB) HDD (GB) Operating System
Install Temporary Running
4 4 500 1 2 7GB 3GB 10GB 32 bit
8 8 4,000 2 2 7GB 3GB 10GB 32 bit
16 16 8,000 2 3 7GB 3GB 10GB 64 bit
32 32 16,000 2 4 7GB 3GB 10GB 64 bit
64 64 32,000 4 6 7GB 3GB 10GB 64 bit
128 16,000 4,000,000 4 8 7GB 3GB 10GB 64 bit
1200 16,000 4,000,000 12 24 7GB 3GB 40GB 64 bit

Multi User - Minimum System Requirements

Multi User Ixia Configuration (15 Users) System Requirements
Ports Flow Groups Flows CPU (# or cores) Memory (GB) HDD (GB) Operating System
Install Temporary Running
128 Total 1,000 per user 16,000 per user 12 24 7GB 3GB per user 10GB per user 64 bit

IxNetwork Web Edition System Requirements

Maximum number of users supported: 10 Maximum number of ports: - 384 (fully loaded chassis) when QuickTest Web Edition runs on the chassis - 1200 (chassis chain) when QuickTest Web Edition runs off chassis ( QuickTest Web Edition OVA) * all other IxNetwork system requirements apply. ** when deployed on SDL chassis, QuickTest Web Edition and IxNetwork Linux API Server support maximum 4 users with up to 32 ports each, or 1 user with up to 128 ports *** when deployed on VE Chassis depending on the provisioned resources the number of users is variable, for 4vCPUs / 8 GB RAM, QuickTest Web Edition uses half (2 vCPUs / 4 GB RAM) we support maximum 1 session with 32 ports IxNetwork Web Edition OVA requirements: - ESXi 6.0 Update 2 or ESXi 6.5 (64 bit only) - VMXNET3 virtual network adapter - 128 GB available disk space IxNetwork Web Edition QCOW2 requirements: - Ubuntu 16.04 or CentOS 7 1611 (64 bit only) - virtio virtual network adapter - 128 GB available disk space
Application IxNetwork Web Edition
Google Chrome 53 or newer
Mozilla Firefox 49 or newer
Microsoft Internet Explorer 11 or newer
Microsoft Edge 25.10586.0.0 or newer
Apple Safari 9.1.3 or newer

Virtual Machine (VM) System Requirements

When running IxNetwork inside a Virtual Machine, use the same information provided above for each Virtual Machine. Additionally, the following requirements specific to a virtual environment must be met: - Virtual Machine resource reservation for CPU / Memory must match the minimum CPU / Memory specified above - Data storage must provide at least 25 IOPS for each Virtual Machine / user - Data storage must present local storage instead of NFS - A Graphics Card compatible with the hypervisor must be present on the server

Operating System Support

The following versions of Windows operating systems are supported on the client: - Windows 2016 Server Standard 64-bit (*) - Windows 2012 Server R2 Standard 64-bit (*) - Windows 10 Pro - 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.6 - 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/2008 - 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

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 interfact (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 have 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 both QuickTest and IxNetwork API Server. 2. IxNetwork Web Edition can be installed on VM (ESXi and KVM) and HSL chassis. 3. IxNetwork Web Edition software (OVA, QCOW2, 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 link displayed in console screen (from 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 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 link displayed in console screen (from 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 corresponding language. 10. Sample codes are given for each language and follow the steps.

IxNetwork Web Edition can be installed on HSL/SDL chassis

1. Connect to XGS12-HSL/XGS2-HSL/XGS12-SDL/XGS2-SDL 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 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 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/Tk Support for Client Applications

Installation of Tcl Server is required to support execution of Linux/UNIX-based legacy
Tcl scripts. Installation of Tcl Server is not required to support execution of
Linux/UNIX-based IxNetwork API (new) Tcl scripting, but utilizes a IxNetwork GUI client
started in Tcl Server mode. 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
https://www.ixiacom.com/contact/info

Support

Global Support support@ixiacom.com +1 818 595 2599
APAC Support support-asiapac@ixiacom.com +91 80 4939 6410
EMEA Support support-emea@ixiacom.com +40 21 301 5699
Greater China Region support-china@ixiacom.com +400 898 0598
India Office support-india@ixiacom.com +91 80 4939 6410
Japan Head Office support-japan@ixiacom.com +81 3 5326 1980
Korea Office support-korea@ixiacom.com +82 2 3461 0095
Singapore Office support-asiapac@ixiacom.com +656 494 8910

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

8.50 EA Features

Access
Inclusion of NGPF BBA QT rate based test scenarios.
A TLV (Access-Aggregation-Circuit-ID-ASCII) is added in PPPoE Client. This parameter enables or disables the insertion of sub-options 0x91 (Server Signal DSL-Type TLV) into the DSL tag in PADO and PADS packets. It inserts the exact values received from the client (in the PADI / PADR packets).
Added a TLV (PON type) in PPPoE. This parameter enables or disables the insertion of sub-options 0x92 (Serve Signal PON-Type TLV) into the DSL tag in PADO and PADS packets. It inserts the exact values received from the client (in the PADI / PADR packets).
Added a feature where the TLV parameters of DHCP client can be changed and applied on the fly without making DHCP client to send RELEASE. Subsequent messages from DHCP client will reflect this TLV.
NGPF ANCP now supports PON type as well apart from DSL type. It can now send PON type TLV on most of the messages.

AppLibrary
Applibrary now support 3 new APIs to fetch the count of installed, available and in-use of Applibrary slot license.

Automation
High Level automation client to connect securely with Linux API server using session parameter.
Next Generation Protocol Framework (NGPF) now allows users to invoke Trigger on Fetched Learned Info through API. Users also have the ability to modify or update Learned Info Trigger Parameters which are used for Learned Info Trigger through API.
IxNetwork Linux API Server now supports API for Packet Capture Browsing
API Browser now supports Traffic Widget to view Traffic Items and Flow Groups, edit properties and preview packets
Support of IxNetwork Low Level and High Level API in TCL-8.6 and Python-3.6
IxNetwork Windows and Linux client libraries are now merged into one, making it simpler to deploy in automation environments
API browser now supports editing protocol properties in Topology Widget
IxNetwork Linux API Server can now be installed on an Ixia Virtual Chassis
IxNetwork API automation libraries are published to GitHub in the following repositories: ixiacom/ixnetwork-api-py ixiacom/ixnetwork-api-tcl ixiacom/ixnetwork-api-pl ixiacom/ixnetwork-api-rb

High Level API
HLT API support for DHCPv6 Server reconfigure Command
High Level API support for mLDP has been added.
High Level API support for LDPv6 has been added.
High Level API support for 802.1X has been added.
High Level API support has been added for BGP Segment Routing (BGP-SR).
High level API support has been added for NGPF BGP Flowspec.

Infrastructure
A navigation tree has been added under Scenario in left panel for Scenario items including Topology, Device Group and Network Group. One-click navigation from left panel NGPF Grid to corresponding Topology/Device Group/Network Groups in Scenario Editor has been added. Sticky note has been added for Topology in Scenario Editor to allow for more descriptive notes.
IxNetwork QuickFlowGroup now supports auto-resolve MAC for IPv6 interface.
Nextgen Protocol Framework (NGPF) now supports association of multiple IPv4 addresses to same MAC using stack multiplier value greater than 1. Association of multiple IP addresses to same MAC is viable when there is no other protocol layer on top of IP Stack.
IxNetwork Diagnostics utility has been enhanced to add option for the user to delete older logs for a specific module. This feature is available from "Remove old logs" section of the Diagnostics utility. When user clicks remove logs on client there will be a dropdown menu to select which specific module's log are to be removed.

MPLS
Dynamic MPLS label update when BGP next hop in L3VPN route changes has been added for L3VPN traffic over IS-IS SR LSP.
NGPF BGP Labelled Unicast emulation has been enhanced to support multiple MPLS labels per RFC 8277 both in control plane and stateless traffic.
NGPF NG-MVPN has been enhanced to support mLDP P2MP LSP as P-tunnel. This is EA quality now.

QuickTest Web Edition
QuickTest Web Edition can now be installed directly on an Ixia Virtual Chassis
QuickTest Web Edition RFC2544 now support CloudStorm 100 / 40G non-aggregated ports
QuickTest Web Edition has a new simplified ‘Traffic Test’, enabling users to easily create and run a basic L2 or L3 traffic test
QuickTest Web Edition now supports RFC3918 Group Join / Leave Delay Test
QuickTest Web Edition has now support for randomizing the sequence of packets that hash uniformly based on XOR values of user configurable pool of source and destination VLANs/IPs/Ports. The feature is beta quality.

Routing/switching
LAG: An enhanced NGPF LAG emulation has been added with a single LAG configuration element and stream based data traffic distribution and failover across LAG member links.
LAG: A new LAG configuration model added with a user friendly enhanced workflow to configure LAGs and L2/L3 protocols behind LAG.

SDN
PCEP emulation has been enhanced to support Primary and Backup PCEs by the PCC as per Centralized Path Computation model (RFC4655) for all types of SR-TE LSPs.
BGP SRTE Policy emulation supports dynamic update of SRTE policy without stop and restart BGP session.
BIER (Bit Indexed Explicit Routing) emulation is now EA quality. The BIER emulation includes ISIS as the routing underlay and NG-MVPN for multicast flow overlay.
NETCONF emulation has been introduced in this release. A full-fledged NETCONF client emulation supports sending NETCONF Requests agnostic to Yang data model to help with analysing responses, validate DUT response times and stress management plane. It also provides a unique decrypted SSH packet capture integrated with Wireshark to help troubleshooting. A basic NETCONF Server emulation helps to validate NETCONF Controller session scale capacity.
NGPF OpenFlow now supports TLS 1.1/TLS 1.2 and certification files with SHA512 signature.
BIER emulation now supports OSPF as the routing underlay. This feature is released as beta quality.
L3VPN over SRv6 core emulation is now EA quality. This feature enables customers to test early SRv6 (IPv6 Segment Routing) Network Programming implementation. It includes ISIS support for new SRv6 draft and BGP L3VPN (both v4 and v6) over SRv6 core.
NGPF EVPN now supports warning message for misconfigured Multicast / Broadcast MAC address in EVPN MAC pool at the time of starting the protocol.
BGP Segment Routing has been enhanced to support multiple originator Segment Routing Global Block (SRGB).
Telemetry: INT over Geneve and UDP traffic generation using raw traffic template editor and INT packet decoding using Wireshark have been introduced in this release.
BGP SRTE Policy feature has been enhanced to support up to 64 paths per policy.
NGPF EVPN support for multi-site EVPN Border Gateway emulation is now EA quality.
PCEP: IPv4-IDENTIFIER-TLV is included in PCUpdate message sent out by the PCE.

TSN
IxNetwork TSN Conformance Test Library includes conformance test cases for the following IEEE Standards : (1) IEEE 802.1AS (gPTP) - Timing and Synchronization for Time-Sensitive Applications in Bridged Local Area Networks. (2) IEEE 802.1Qbv - Time Aware Shaper (Enhancements for Scheduled Traffic). (3) IEEE 802.1CB - Frame Replication and Elimination for Reliability.

VM
Support for Web UI on the Virtual Chassis has been improved with Broadcast Discovery and Mass Operations capabilities, simplifying operation in large scale topologies.
Support for Live Production Networks / Resource Utilization has been improved. The Virtual Chassis Disk Size can be increased by the user from 8 GB to higher values.
Support for Live Production Networks / Security Updates has been improved, with the Guest OS updated to CentOS 7.4 and the latest security patches applied.
Support for Live Production Networks / SNMP Notifications has been improved, with new capabilities for configuring the SNMP Trap Interval and the SNMP Trap Priority.
Support for Live Production Networks / Installation Documentation has been improved, explaining the TCP / UDP Ports used to communicate between system elements.
Support for Deployment Wizard has been improved, with a new capability to perform deployment in KVM environments using non-root lower privileged user accounts.
Support for Command Line Interface (CLI) Configuration has been improved, with the ability to configure the Host Name of the Virtual Chassis / Virtual Test Appliance.
Support for Chassis Builder has been discontinued starting with this release. This functionality is replaced by the Web UI for the Virtual Chassis / Virtual Test Appliance.
Support for IxNetwork VE inside Amazon AWS Public Cloud has been added (BETA), with the Bring Your Own License (BYOL) model and IPv4 traffic emulation capability.
Support for installing IxNetwork Web Edition on the Virtual Chassis has been added. This includes the Quick Test Web Edition and the IxNetwork API Server.
Support for new NGPF Access / Routing / MPLS / SDN / Data Center protocols (including 802.1x, BIER, NETCONF, NTP, SRv6) has been added.
Support for configuring Promiscuous Mode inside the Ports Grid has been added. This simplifies the configuration and allows saving these settings inside the IXNCFG file.


Known Issues List

AVNU

Bug Number Notes
1487738 Ixia Hardware for AVB/TSN does not support 10Mbps link partner . As a result any test case requiring these speeds will not be supported. Impacted Test Cases from Avnu Conformance Coverage Test Package, 1. FQTSS_34_3_3_a
1487739 Ixia Hardware for AVB/TSN does not support 100Mbps half duplex link partner . As a result any test case requiring these speeds will not be supported. Impacted Test Cases from Avnu Conformance Coverage Test Package, 1. FQTSS_34_3_2_a

Access

Bug Number Notes
1480807 802.1X GUI, API and HLPAPI do not support list values for key_usage_extensions field/switch.

Automation

Bug Number Notes
1471484 By default, different API clients can connect to the same IxNetwork session, except for sessions controlled by Connection Manager. For disallowing connections to a session in use, please run 'connect' command with '-allowOnlyOneConnection' parameter. In previous releases, for sessions controlled by Connection Manager, connecting to a session in use would have started another session. This has been fixed and now and the following error is thrown "::ixNet::ERROR: The requested session is currently in use."
1471619 Python 3.6.4 is not recommended to be used for connecting to IxNetwork REST Port, Connection Manager SSL Port, or IxNetwork Web Edition. Connection to IxNetwork might fail due to the following Python bug 32394: https://bugs.python.org/issue32394 This affects Windows 10, Windows Server 2016 clients if the Windows version is less than 1703. The workaround is to update Windows to 1703 or newer versions or use any other python version ([=3.6.3 or ]=3.6.5).
1474684 Automation libraries no longer allow you to connect to multiple IxNetwork server sessions from the same object/console. In order to connect to another server session please first disconnect from the current session.
1476007 API connections to IxNetwork REST Port, Connection Manager SSL Port, or IxNetwork Web Edition are now secured. As a consequence, API communication may be slower due to the encryption of the channel.
1476323 The path for the TCL IxNetwork low level library on Linux environments has changed from [IxNetwork_install_path]/lib to [IxNetwork_install_path]/lib/TCLApi. TCLLIBPATH environment variable needs to be update correspondingly.
1476452 If the user is facing this issue ie. a generated script using the old ixNet exec scriptgen method is not getting sourced back ( having errors) ,the user needs to move to the new model of scriptgen. The user must generate the script using the new scritgen method. The guideline is to use the new scriptgen api as documented by ixia api guide available at https://support.ixiacom.com/user-guide/ixnetwork
1476719 Two LearnedInfoUpdate objects will get created for parent-child relations i.e. Channel - Auxiliary LI, Group-Buckets, Meter-Bands, etc, and second level triggered Learned Info. The second LearnedInfoUpdate object should be ignored in the APIs.
1478140 API communication to IxNetwork REST Port, Connection Manager SSL Port, or IxNetwork Web Edition is secured. It is not recommended to run API clients with non-Ixia interpreters. However, if the user desires to do so, third party libraries need to be installed for each API in order to ensure the secure communication. - For TCL install tcltls and tcllib (http, json, websocket, logger, base64, sha1). - For Python, install the dependencies listed in the requirements.txt file in the library directory by issuing the following command: pip install -r [install path]/ixia/ixnetwork/[version]/lib/PythonApi/requirements.txt This will install the following: requests, websocket-client. - For Perl, install the dependencies listed in the cpanfile file in the library directory by issuing the following command from the library directory: cpanm --installdeps . This will install the following: IO::Socket::SSL, LWP::UserAgent, Protocol::WebSocket::Client, JSON::PP, Time::Seconds, LWP::Protocol::https
1478637 Automation clients are no longer allowed to connect to IxNetwork Linux API Server using other port than the default one. The client should either connect without specifying the '-port' parameter, or by using the 443 port.
1481938 For NGPF OSPF and ISIS protocols, a scriptgen-ed configuration file from old release may not restore to 8.50 properly. Follow these steps for a workaround - 1) source the scriptgen config in old IxNetwork build. 2) save the config file from GUI as ixncfg 3) Load the ixncfg in latest 8.50-EA. 4) Scriptgen it back.
1482461 saveCapture API return type changed from void to kArray[kString] in order to return the list of capture files saved with the new location
1485176 If running TCL API automation client on MacOS for connections to IxNetwork REST Port, Connection Manager SSL Port, or IxNetwork Web Edition, ActiveState TCL needs to be used. The native TCL from Apple is known to have issue with SSL due the fact the Apple ships with LIbreSSL instead of OpenSSL
1485425 If running API Python automation client on MacOS for connections to IxNetwork REST Port, Connection Manager SSL Port, or IxNetwork Web Edition,Python 2.7.15 or newer needs to be used. This is a Python issue on MacOS: older Python versions do not ship with a builtin copy of OpenSSL and MacOS provides LIbreSSL instead of OpenSSL
1486716 If running Perl API automation client using non-Ixia interpreter for connections to IxNetwork REST Port, Connection Manager SSL Port, or IxNetwork Web Edition, the user needs to ensure that IO:Socket:IP and IO:Socket:SSL are compatible. It is recommended to install the latest version of IO:Socket::SSL after installing all the other dependencies listed in the cpanfile file located in the library directory. This is due to a Perl bug (https://rt.cpan.org/Public/Bug/Display.html?id=103422 ) which in case of our API will determine the failure of secure connections without providing any error.
1487453 When configuring LAG using API browser, the port link will not show UP in topology grid view
1487595 API browser widget view - the edit field in any of the fields of topology widget view will show the latest changes if the change is done in IxNetwork config in client. However the rows in topology widget view will reflect the changes properly if auto refresh is enabled.Workaround to get the edit field to reflect the latest changes is to refresh the browser page.
1489133 In very rare cases, when a system is under heavy use, the IxNetwork Web server may become unresponsive. In those cases, an administrator may run `ssh admin@IP chassis restart-service ixia-web-platform` to work around the issue. This shouldn’t impact running tests.
1489525 Executing a high number of tests with IxNetwork Web installed on an SDL chassis may result in intermittent failures due to the websocket connection being closed.
1489546 Sometimes, in very rare conditions, when chassis is under heavy load, an IxNetwork Linux API Server session may stop prematurely
1490616 Sometimes, on older Windows systems like WIN 2008 R2, when running IxNetwork API Server as secured HTTP and trying to open the API Browser, it will timeout The errors/reason why it happens, can be found in the Windows Event Viewer under system logs as the following entries: - A TLS 1.2 connection request was received from a remote client application, but none of the cipher suites supported by the client application are supported by the server. The SSL connection request has failed. - The following fatal alert was generated: 40. The internal error state is 1205. The reason for that error is that the cipher mode TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 is not supported by WIN 2008 R2 To solve the issue, and be able to successfully open API Browser with IxNetwork API Server running in secure mode, you will need to patch the system to bypass TLS 1.2 and use TLS 1.1 as follows: - Add the following registry key or ensure an existing registry key looks like the following: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server] "Enabled"=dword:00000000 - Restart the system

High Level API

Bug Number Notes
1480522 If an HLAPI call tries to change global settings in 802.1X after the protocols are started to the same value as previous, the global setting values will remain unchanged even if the API call does not return error.
1482117 Only Python 32 bit variant of 2.7.x and 3.6.x version gets installed in IxNetwork/HLT windows environment

Infrastructure

Bug Number Notes
1466349 If procdump application is put into "C:/temp" directory in IxNetwork client machine then there is a watchdog service that takes IxNetwork application dump and kills the application if a hang is detected by the watchdog service. Workaround is to avoid putting procdump in the location "c:/temp".

QuickTest Web Edition

Bug Number Notes
1466845 In very rare cases, when a system is under heavy use, the Web Server may become unresponsive. As a workaround, an administrator may run "ssh admin@IP chassis restart-service ixia-web-platform" to restart the Web Server. This will not impact running tests.
1469007 Flow Group Tracking is mandatory for Traffic Test in QuickTest Web Edition and it cannot be disabled from the Traffic Item configuration.
1475741 Packet capture needs to be stopped before any packet analysis can be initiated.
1477023 Browsing captured packets is 3x slower in IxNetwork Linux API server compared to Regular IxNetwork Windows api Server.
1477827 When running QuickTest Web Edition tests using Jumbo frames on CloudStorm 10GE platform, statistics may flap.
1478277 Rx byte statistics are not reported correctly in IxNetwork when compared to the statistics displayed in IxExplorer.
1478465 When running a Traffic Test and "Calculate Jitter" is selected, "Average Latency" will not be displayed in summary statistics view or graph view
1481716 For Traffic Test, the statistics chart has a precision of 8 digits after the decimal point. In certain cases where loss value is smaller than 0.00000001%, there may be multiple, same values on the Y axis label.
1487109 When installing IxNetwork Web Edition on a VE chassis with limited network access, an extra reboot of the application is needed in order to the application to start properly.
1487574 For a RFC3918 QuickTest Web Edition run that is longer than a day, it is possible that Statistics may not be available at the end of the run. As a workaround, it is recommended to refresh the web page.

Routing/switching

Bug Number Notes
1377148 When IPv4 and IPv6 Prefix Pools are attached in same Network Group, user tries to change any attribute in route range after selecting entire NG, the change get effected only in IPv6 Prefix Pools. Workaround is to change Route Range attribute after selecting IPv4 IPv6 Prefix pools individually.
1462997 When both TWAMP and Traffic are running, it may cause other emulations to flap, as Data Plane traffic is forwarded to Port CPU due to TWAMP design.
1469361 Enabled string input fields cannot be empty, So need to provided a blank space as default value for Address Ranges to Skip.
1476400 LAG: Stopping LACP on Tx ports does not switch over the data traffic to other ports of the LAG, it will continue flowing on the same port.
1479031 Under some specific scenarios with a configuration having mix of BGP, ISIS and access protocols like PPPoX in multi-NIC load module where secondary port of a resource group1 is connected to another secondary port of resource group2 sometimes port CPU can go to a bad state while performing stop protocol on a device group over some iterations.
1490009 In a configuration with LAG-Ports, changing the number of emulated devices while the protocols are running may cause some protocol sessions to not come up. The workaround is to Stop the protocol and Start it in-order to bring the sessions up.

SDN

Bug Number Notes
1482692 ecdsa public key is not supported by netconf server.
1484516 There is an issue with scriptgen and sourcing back of OSPF segment routing mapping server configuration. Low-level scriptgen of such configuration with IxNetwork serialization does not load back correctly. To avoid this issue, use ixncfg config files or scriptgen with base64 serialization.
1487923 In BIER, automatic traffic can be generated for a maximum of 4096 BFRs per sub-domain.
1490599 The color attribute value is shown incorrectly in BGP SRv6 VPN learned information display. This issue is seen only for virtual ports, not in hardware ports.
1490609 When user chooses to advertise the BGP SRv6 VPN SID's locator in ISIS, then the metric value of ISIS IPv6 reachability TLV for that locator route gets advertised wrongly. This issue is seen only for the virtual IxNetwork VE ports, not in hardware ports.

Statistics

Bug Number Notes
1483934 This performance issue appears in several Client UI screens: - Statistics view - takes a long time to retrieve the chart, usability issue - Editor - takes a long time to retrieve config, usability issue - QT timeline - remains empty, functional issue Fixing this issue will require an analysis across Client UI and IxNetwork Middleware. Considering the current stage of the release, I propose to track the performance improvements into the next big release. This should not have a big impact on our clients because the it appears on large configs.

Traffic

Bug Number Notes
1475362 Rate and Frame size change on the fly is not supported for traffic configured over Link Aggregation groups.
1487328 When Advanced sequence check is enabled from the Test Options window and if the Rx port doesn't receive any frames while the traffic is running, Loss percentage and Lost Frames statistics may show as 0% loss instead of 100% loss and 0 lost frames respectively .

VM

Bug Number Notes
1467512 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.
1467647 Licenses might still get checked out for license unavaible ports after an IxServer restart in case you do not have enough licenses for all ports from a newly attached card.


Resolved Defects List

Audio Video Bridging

Bug Number Notes
1470979 As per customer requirement, 1588v2 unicast/peer delay mechanism with "Don't Send" has been implemented in the PTPv2 Telecom profile.
1487740 The test case demands configuration of 1000 contiguous MAC addresses from the talker and sending traffic over them to make sure line rate is achieved. Currently Novus can only support 512 flow group configuration hence configuring 1000 parallel flow groups for this test case will not be possible.

Automation

Bug Number Notes
1466738 API not exposed for the BGP Extended Community Type AdministratorAs2OctetLinkBw.
1482322 ixNet.getApiKey ([hostname], "-username", [user], "-password", [pass] [,"-port", [443]] [, "-apiKeyFile", [api.key]] This needs to be documented and included in release notes as we changed the way it was released in 8.40 (for consistency purposes)
1483311 When connecting a web browser to an instance of ixnetwork https rest port the user will be presented with security warning indicating that the security certificate is not trusted by your computer's operating system. This is a result of the certificate being self-signed.
1483407 Fixed an issue with Connection Manager error: "LOCK PORT: Failed to aquire TCP port 8013. Exception reported"

Data Center

Bug Number Notes
1463469 Earlier the traffic Outer IP was set to Multicast IP, even when VxLAN "Outer Destination IP Mode" is set to Unicast. This issue has been fixed now.
1464590 Duplicate VNI check has been added as a fix, so the VNI and IP Address pair can not be same for two VxLAN Tunnels.

High Level API

Bug Number Notes
1465602 Enhanced user documentation of NGPF HL API of emulation_igmp_control
1472865 Added new argument as 'get_capture_buffer_state' in HLAPI command packet_control to know the status of packet capture
1472868 HLPython - traffic_stats mode = 'user_defined_stats' not able to pass in the tracking filters and traffic item filters
1474877 HLAPI - ixiangpf.emulation_bgp_config disable_received_update_validation = "1" does not select the "Disable Received Update Validation" checkbox
1477816 HLT API connect with option -break_locks as value 0 will not take port owned by other users

Infrastructure

Bug Number Notes
1466347 If IxNetwork is run with real time monitoring feature enabled from "Test Inspector Settings", there is a chance that the application may run into a crash. Workaround is to turn off real time monitoring or use the feature for short time periods only.

Misc (include Analyzer, license, installation, etc)

Bug Number Notes
1483097 customer wants to fetch help for other Bit Sting Objects he/she needs to goto the 1st one and press F1"

QuickTest Web Edition

Bug Number Notes
1473465 To work with IxNetwork Web QuickTest or IxNetwork Web Linux API Server using Internet Explorer browser, user may need to disable protected mode
1482193 getApiKey method call has been updated to be consistent across API languages. The method has the following mandatory arguments and their value pair • "hostname" – string containing the hostname or IP address of the target server • "-username" – string containing the username • "-password" – string containing the password (in clear) The following arguments are optional: • "-apiKeyFile" – the full or relative path to a file where the API key will be written, in clear, after it is obtained. By default, if only a file name is provided, the file will be saved in the current working directory. If the file cannot be saved in the current working directory, it will be saved in the directory where the automation library resides. If the file cannot be saved at all (for example, if the user doesn’t have the right to write files to any of these locations) a warning is printed out. If no file name is supplied, the file name will be api.key. • "-port" – the target port for the connection to the Windows/Linux API Server Tcl ixNet getApiKey hostname -username user -password pass [-port 443] [-apiKeyFile api.key] Perl $ixNet-]getApiKey (hostname, "-username", "user", "-password", "pass" [,“-port”, 443] [, “-apiKeyFile”, ”api.key”]); Python ixNet.getApiKey (hostname, "-username", "user", "-password", "pass" [, “-port”, 443] [, “-apiKeyFile”, ”api.key”] )

QuickTests

Bug Number Notes
1460673 Fixed an issue when port L1 properties were getting modified while applying QT
1462953 Fixed an issue when running QT the first time and it has its associated traffic item disabled, the generate will not put the correct configured frame sizes on flow groups - it will always put 64
1465253 Fixed an issue when in a certain scenario flow group setting in QT are not saved
1467370 Fixed an issue where RFC 2544 Test had a 3 minutes delay on each iteration

Routing/switching

Bug Number Notes
1476415 Sometimes BGP update message for VPN route does not include configured attributes like extended communities.
1477906 In NGPF, though Simulated Topology could be connected to OSPF or IS-IS layer connector, it may not work. As a workaround always connect Simulated Topology to Ethernet connector.
1490653 CCM does not get transmitted after some time when control capture is enabled

SDN

Bug Number Notes
1467081 A port crash in BGP flowspec due to memory corruption while performing on-the-fly operations.
1482331 NETCONF: Port may go into bad state due to out of memory if Netconf PDU TX rate is higher and unable to process the Netconf PDU RX.
1484637 PCEP: Ixia PCC no more responds to NOPATH PCReply messages with any Report message.
1486591 PCEP: Ixia PCC no more responds to NOPATH PCReply messages with any Report message.

Traffic

Bug Number Notes
1413806 IxNetwork:IPv6 packet with extension header is not counted in IXIA statistics
1446412 Traffic item adding IPv6 extended hop by hop option header was causing 100% packet lost
1467244 Incompatible with 100GE ports error is coming when there is difference in regional setting between chassis and IxN host.
1473335 Resolved the modification of the Indexes of traffic flow group after regeneration of traffic flow.

VM

Bug Number Notes
1431090 Fixed an issue that caused the apply traffic operation to fail on Virtual Ports.