Ixia Software Release Notes
IxNetwork 8.31 EA
Build Number: 8.31.1080.11 (October 5, 2017)



About This Release

IxNetwork 8.31-EA is an "Early Adopter" release.
Please see the specific sections below for application compatibility requirements, Whats New, Known Issues and the Product Compatibility Matrix.

Previous Release Notes

Please visit the IxNetwork support web page for more information on previous Release Notes.

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.31 EA
BPS Not Supported
FLIX OS 2017.1.0.1 (XGS2-HS & XGS12-HS)
2017.1.75.6 (XGS2-HSL/XGS12-HSL/NovusONE/PSONE)
HLTAPI 8.31 EA
IxANVL Not Supported
IxChariot Not Supported
IxLoad Not Supported
IxNetwork 8.31 EA
IxVM 8.31 EA
Licensing 4.60 EA
Test Conductor 3.60 GA
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
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
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
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
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
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
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
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
AppLibrary LSM1000XMVDC16NG, LSM1000XMVDC4NG, LSM1000XMVDC4, LSM1000XMVDC8, LSM1000XMVDC12, LSM1000XMVDC16, NOVUS10/1GE16DP, NOVUS10/1GE8DP, NOVUS-NP10/1GE16DP
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 and XGS12-HSL 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
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.31 EA ships with Ixia Licensing 4.60 EA. IxLicensing 4.30 EA and later is Ixia's new license management system. Ixia Licensing Utility (ILU) and License Server Plus (LS+) are replacing Ixia Registration Utility (IRU) and License Server (LS) used in earlier versions of IxLicensing. 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 4.50 upgrades Ixia Licensing 3.x, Ixia Licensing 4.25.x and prior versions on the machines. The reverse is not allowed. 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 4.50 installs .Net 4.0 on Chassis and .Net 4.5.1 on Clients and VM Chassis. NOTE: Ixia Licensing 4.50 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

QuickTest 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. QuickTest 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 QuickTest 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 QuickTests Web
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 2012 Server R2 Standard 64-bit (*) - Windows 2008 Server R2 SP1 Enterprise 64-bit - Windows 2008 Server R2 SP1 Standard 64-bit - Windows 2008 Server Standard SP2 32-bit - Windows 2008 Enterprise SP2 32-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, Perl 5.18, Python 2.7 and 3.3+, Ruby 1.9.3 - CentOS 6.3, 6.4, 6.5 on x64 platform - Tcl 8.5, Perl 5.18, Python 2.7 and 3.3+, 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 7 on x64 platform - Tcl 8.5, Perl 5.16, Python 2.7 - Arch Linux on x64 platform - Tcl 8.6, Perl 5.20, Python 3.4 - 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

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, Perl, Python 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 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. 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.rb 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 Linux API Server Installation Notes

IxNetwork Linux API Server can be installed directly on a Linux Centos machine

please follow the steps below: 1. Download and copy the IxNetwork_API_8.31_EA.tar to the Linux machine where you want to run it. 2. Extract it with tar -xvf command. For example: # tar -xvf IxNetwork_API_8.31_EA.tar 3. Run install.sh to install the IxNetwork API Server 4. Start the IxNetwork API Server using the following command: # mono IxNetwork.Middleware.exe [options] Options: -tclPort PORT IxNetwork will listen on this PORT to serve incoming TCL connections -restPort RESTPORT IxNetwork will listen on this RESTPORT to serve incoming REST calls -username USERNAME IxNetwork will use this USERNAME when taking ownership of the ports -restOnAllInterfaces IxNetwork will bind the rest port to allow rest port access from an external machine ex: mono IxNetwork.Middleware.exe -tclPort 8011 -restPort 11011 -username 8011

IxNetwork Linux API Server can be installed on VMWARE ESXI6.0 or ESXI6.5 via the provided OVA

Please follow the steps below: 1. Deploy API Server OVA directly on to VMWARE ESXI server. 2. Start VM which is deployed. 3. Note IP of VM. 4. Open a Web Browser and connect to API Server 5. Log in with credentials username: admin and password: admin 6. To start a session manually, click "New Session" 7. To start scripting click on download 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 Linux API Server can be installed on KVM via the provided QCOW2 image

please follow the steps below: 1. API Server is supported on KVM with CentOS and Ubuntu Distributions. 2. Deploy Qcow2 image on KVM 3. Start VM 4. Note IP of VM. 5. Open a Web Browser and connect to API Server 6. Log in with credentials username: admin and password: admin 7. To start a session manually, click "New Session" 8. To start scripting click on download client. 9. Make sure that all dependencies are installed before starting scripting. 10. Click on package downloads for corresponding language. 11. Sample codes are given for each language and follow the steps mentioned. IxNetwork Low Level API library is supported on the following operating systems: - Microsoft Windows(OS as stated above) - Tcl 8.5, Perl 5.24 and Python 2.7 - CentOS 7 on x64 platform - Tcl 8.5, Perl 5.24 and Python 2.7. IxNetwork High Level API library is supported on the following operating systems: - Microsoft Windows(OS as stated above) - Tcl 8.5, Perl 5.24 and Python 2.7 - CentOS 7 on x64 platform - Tcl 8.5, Perl 5.24 and Python 2.7.

QuickTest Web Edition Installation Notes

IxNetwork QuickTests Web software is available as a download from the Ixia website. IxNetwork QuickTests Web can be deployed directly on the chassis or run in a separate VM For deploying directly on the chassis, please follow the steps below: 1. Download IxNetwork QuickTests Web software from the Ixia website to a local computer 2. Open a Web Browser and connect to your XGS12-HSL/XGS2-HSL chassis 3. Log in 4. Go to Administration / Updates screen 5. Click on Update Packages button and point to the previously downloaded package for IxNetwork QuickTests Web 6. Follow the on-screen instructions provided by the installer.

QuickTest Web Edition OVA installation

1. Deploy QuickTest Web Edition OVA in ESXi 2. Start Virtual Machine 3. Get connected to link displayed in Console screen

QuickTest Web Edition QCOW installation

1. Deploy QuickTest Web Edition QCOW2 in KVM/Virtual Machine Manager 2. Start Virtual Machine 3. Get connected to link displayed in Console screen

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

USA, Canada and Latin America Customer Support

Hours: 6:00am PST to 6:00pm PST
Email: support@ixiacom.com
Phone: 1-818-595-2599
e-Fax: 1-818-449-0992

Europe, Middle East, and Africa Customer Support

Hours: 07:00 to 17:30 GMT
Email: support-emea@ixiacom.com
Phone: +40-21-301-5699

India Customer Support

Hours: 09:00 to 17:30 local time
Email: support-india@ixiacom.com
Phone: +91-80-4939-6410

Japan Customer Support

Hours: 09:00 to 18:00 local time (Japan), Monday through Friday
Email: support-japan@ixiacom.com
Phone: +81-3-5326-1980
Fax: +81-3-3348-7733

Asia Pacific Customer Support

Hours: 09:00 to 17:30 local time (Singapore)
Email: support-asiapac@ixiacom.com
Phone: +91-80-4939-6410

China Customer Support

Hours: 09:00 - 18:00 local time (Beijing time), Monday through Friday
Email: support-china@ixiacom.com
Phone: 400-898-0598 (Greater China region)
Phone: +86-10-5732-3932 (Hong Kong customers)
Fax: +86-10-8454-9198

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.31 EA Features

Access
PPPOE host-uniq tag is of any Byte - removed earlier restriction of 4 Bytes.

AppLibrary
Now one level HTTP redirect is supported in Applib.

Automation
IxNetwork Low Level API can now call clear statistics synchronously. Two extra attribute ('waitForTrafficStatsRefresh', 'waitForPortStatsRefresh) are provided to make a blocking call for clear statistics exec and wait for Traffic statistics and Port Statistics views to refresh before proceeding to next step.
Introduced ‘IxNetwork Automation: Low Level API Guide Book,’ a collection of best practices in scripting that includes examples and code snippets. This guidebook will allow users to develop IxNetwork test automation efficiently.

MPLS
In NGPF EVPN, sequence number in MAC Mobility extended community is now user configurable.

Novus 8x100GE QSFP28 Load Module - 10GE/40GE Speed Option
905-1026: NOVUS 1x40GE/4x10GE FAN-OUT-UPG FIELD UPGRADE Option purchase of the 1x40GE/4x10GE fan-out option for the NOVUS100GE8Q28+FAN, 8-port, QSFP28 100GE (944-1140) or the NOVUS-R100GE8Q28+FAN 8-port, NOVUS-M100GE8Q28+FAN (944-1156), or the QSFP28 100GE reduced (944-1147) load modules. Note: This option is REQUIRED ON FIELD UPGRADE PURCHASES to enable the 1x40GE/4x10GE speed on the NOVUS100GE8Q28+FAN, NOVUS-M100GE8Q28+FAN, or the NOVUS-R100GE8Q28+FAN 8-port, QSFP28 100GE reduced (944-1147) load modules. Note: For the 1x40GE/4x10GE upgrade purchase please provide the serial number of the desired load module to install the option on at the time of order placement.
905-1025: NOVUS 1x40GE/4x10GE FAN-OUT OPTION for a factory installed 1x40GE/4x10GE fan-out option for new purchases of the NOVUS100GE8Q28+FAN, 8-port, QSFP28 100GE (944-1140), NOVUS-M100GE8Q28+FAN (944-1156), or the NOVUS-R100GE8Q28+FAN 8-port, QSFP28 100GE reduced (944-1147) load modules. Note: This option is REQUIRED ON NEW PURCHASES to enable the 1x40GE/4x10GE speed on the NOVUS100GE8Q28+FAN, NOVUS-M100GE8Q28+FAN and NOVUS-R100GE8Q28+FAN load modules.

QuickTest Web Edition
RFC 7747 BGP Rib-In-Convergence Test support to run with mix of IPv4 and IPv6 interfaces in the same test
RFC 7747 BGP Rib-In-Convergence support to show best iteration in statistics dashboard

Time Sensitive Networking
Enhancements for scheduled traffic as per IEEE 802.1Qbv is added for 100 Mbps link speed.

VM
Support for higher Line Speeds has been added. IxNetwork VE can now emulate protocols and generate traffic with any of the 10G / 20G / 25G / 30G / 40G / 50G speeds.
Support for new Intel Ethernet Controllers running in PCI PT or SR-IOV mode has been added. The list of supported NICs now includes 1G / 10G / 25G / 40G models.
Support for Qualified environments has been improved with the addition of new orchestrators (VMware vCenter 6.X) and vSwitches (VMware Distributed Virtual Switch).
Support for Deployment Wizard has been enhanced, with the ability to create vChassis / vCards inside VMware vCenter 6.X / Distributed Virtual Switch environments.


Known Issues List

Automation

Bug Number Notes
1452417 Clear Statistics call from IxNetwork APIs has option to make it a blocking call, and this operation takes 10-12 sec for a simple 2 port configuration.

IxNetwork-Framework-(Framework)

Bug Number Notes
1458440 Occasionally IP interface setup and ARP may fail on ports if IxTclHal is used directly after IxNetwork. To avoid this issue, always use the IxNetwork standard cleanup API call “unassign” or HLAPI call “cleanup_sesssion” before using the IxTclHal APIs. If the test is already in a bad state with ARP not resolving, a port CPU reboot will clear the issue.

MPLS

Bug Number Notes
1455061 MAC mobility testing in classic emulation of EVPN has known limitations. EVPN should be emulated in Next Generation Protocol Framework (NGPF) instead.
1455566 Wireshark does not decode sequence number properly when sequence number is large enough to occupy more than 6 bytes in MAC Mobility Extended Community.

NewLoadModule

Bug Number Notes
1454330 Retrieving a large number of packets from the capture buffer through IxOS TCL may result in IxServer crash or Load Module disappear. The workaround is to retrieve them in chunks or batches.

Routing/switching

Bug Number Notes
1453989 Performing restart down operation frequently in a configuration with large number of BGP peers may sometimes cause the port to crash.
1455169 Ports might crash if IxNetwork configuration has duplicate IPs.

Test Composer

Bug Number Notes
1453538 Work around for the user is not to use "Same" macro recorder action from the ports grid in a for loop or to set the values individually on each cell in the port grid.

Traffic

Bug Number Notes
1455632 For configurations involving L23 Traffic streams with flow tracking sequence checking turned on, the limits on the sequence UDF were not enforced correctly in IxNetwork in previous release. This has been fixed. The configurations which oversubscribe flow sequence checking limits now will fail when traffic is applied.

VM

Bug Number Notes
1452131 Running traffic with frame sizes above 9000 bytes over Intel boards with i40e / i40evf drivers will result in a buffer overflow and the ports will go down.
1452533 It is recommended that for KVM Ubuntu and KVM Centos hypervisors the minimum ixgbe driver version should be 5.1.3 for the following Ethernet Controllers X520 / X540 / X550 / X552
1453532 Adding SR-IOV interfaces in VMware ESXi 6.5 will result in getting the same MAC addresses on multiple interfaces. Sollution is to manually configure a MAC address.
1454463 Port statistics is counting the dropped packets as RX packets.For correct loss values, please check Traffic Item Statistics.
1455612 Users running tests on SR-IOV 10G can experience static MACs getting configured on some of the VFs while the MACs configured on the VLMs test interfaces are different, This cases communication issues between the test ports. Workaround is to hard reboot the VLMs.


Resolved Defects List

Automation

Bug Number Notes
1456099 Resolved in HLAPI TLV Configuration parameter in DHCP TLV Option 77

VM

Bug Number Notes
1453204 Fixed an issue that caused incorrect checksum for inner UDP.
1453246 Fixed an issue that caused incorrect checksum for inner UDP in a VXLAN traffic.