Ixia Software Release Notes
IxNetwork 8.50 EA SP1
Build Number: 8.50.1501.15 (February 15, 2019)



About This Release

IxNetwork 8.50 EA-SP1 is an Early Adopter release. This release consolidates all releases since the last release.
For a complete listing of all the new features included in this release, please refer to the 'What's New' section below.

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 SP1
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.21 EA
IxChariot Not Supported
IxLoad 8.50 EA
IxNetwork 8.50 EA SP1
IxVM Not Supported
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 SP1 ships with Ixia Licensing 5.10 EA. IxLicensing 5.10 EA 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.10 EA upgrades Ixia Licensing 5.0 EA and prior versions on the machines. If the setup is upgraded from versions prior to 5.10 EA, the setup cannot be reverted to the previous version and will need to stay at 5.10 EA 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.10 EA installs .Net 4.0 on Chassis and .Net 4.5.1 on Clients and VM Chassis. NOTE: Ixia Licensing 5.10 EA 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 SP1 Features

Infrastructure
Statistic views now support sorting for custom column similar as regular columns


Known Issue List

Automation

Bug Number Notes
1500677 GUI doesn’t allow users to add any out of range index of the overlay items. But using API users were allowed to add out of range index of the overlay items. For example, users were allowed to add an overlay item with index 3 where multiplier is 2. This issue was fixed and adding overlays on out of range items through API is blocked by validation. IxNetwork would show error if user attempt to add an overlay item with out of range value for the index of the overlay item. This validation is applicable for the existing scripts which where were created manually or generated through Script Gen utility .

Novus 10G

Bug Number Notes
1501031 Latency calibration is not correct.


Resolved Defect List

Access

Bug Number Notes
1499663 For NGPF PPPoE Solution there was no mapping for adsl_2 in dsl_type_tlv for HLT. So script in HLT use to fail. This was fixed.
1499664 While configuring traffic on top of DHCPv6 interfaces, the endpoints were configured not on the session information, so as a matter some rows show incorrect ipv6 address causing a session mismatch. This issue got fixed.

Automation

Bug Number Notes
1496886 IxNetwork REST API server used to return error when executing back to back REST commands for start/stop protocols. This issue is fixed.
1500096 Backward compatibility for HLAPI scripts which uses obsolete attribute "g_filter_mode" has been implemented.
1500455 Now HL API option get_nodrop_rate will retrieve proper value when run against IxOS
1500495 PDF report generation for IxNetwork Quick Test use to fail on Linux API server. This issue is fixed.
1502799 IxNetwork 8.50 changed the REST API Server default from unsecured (HTTP) to secured (HTTPs). Users can now configure the default mode during the IxNetwork installation.

Carrier Ethernet

Bug Number Notes
1500470 NGPF PTP was not considering the correction field value of follow-up msg as t1 residence time while calculating offset. It was fixed by taking into consideration correction field values of both Sync and FollowUp messages for offset calculation.
1500472 NGPF PTP Slave emulation now accepts clock classes which are mentioned as valid per specification.
1500474 With BMCA enabled in NGPF PTP , PTP state machine becomes unresponsive when priority is changed and PTP Master is made a Slave, the issue is addressed as bug fix inside the state machine.
1500909 PTP Master was not propagating accurate timestamps during stopping and restarting protocols for One Step PTP in NON-TSN scenarios, This issue was fixed by taking the accurate timestamps into account against a free running Ixia Chassis.

Infrastructure

Bug Number Notes
1491377 IxNetwork client crashed after clicking on Add L2-3 Traffic after long running test over 63 hours. This issue got fixed now.
1495662 In 8.50 SAVE AS option was giving some exception for some configs saved in 8.40 release. This issue got fixed now.
1497094 GUI crash was there while using protocol filter search to add protocol in NGPF. Now this issue got fixed.
1499720 In statistics some values was showing like '#VALUE!' or '#DIV/0!.' for Quick Test. This issue got fixed now.

MPLS

Bug Number Notes
1499647 While adding RSVP-TE behind the Network Group connected to OSPF, RSVP-TE IF was not getting added. The workaround was to connect the Network Group at Ethernet Layer. In this release, we have fixed the issue. Now, even if the Network Group is connected to OSPF Layer, RSVP-TE can be successfully added to the topology.

QuickTest Web Edition

Bug Number Notes
1502957 Fixed an issue where IxNetwork Web QT was not displaying the configuration page when using a browser on a machine with Simple Chinese.

QuickTests

Bug Number Notes
1500506 Fixed an issue where for RFC2889 Address Cache the MAC Address configuration was not applied properly in the QT Wizard.

Routing/switching

Bug Number Notes
1499869 Starting Protocol was causing PCPU errors for some of the specific configurations on XMVDC and NGY Family.

SDN

Bug Number Notes
1499555 PCE now verifies the existence of LSP IDENTIFIERS TLV in report messages.
1499567 PCE now includes SRP object in PCUpdate message for RSVP Sync LSPs, even if the Sync Report sent by the PCC did not have the optional SRP object.
1499568 PCE is now able to parse PCReport directly with operational state "Up" without receiving "Going Up" prior to that in case of RSVP make before break scenario.
1500473 Sometimes on-the-fly operations of certain fields (e.g AS Number) on large number of BGP sessions (around 5000) were not successful, resulting in few session not getting re-established.
1500476 Sometime malformed BGP update message was sent out for BGP SR policy after BGP session was restarted from DUT.
1500482 ISIS SR was not learning labels from DUT if the SRGB information not present in first LSP.
1500483 In OSPFv2 SR, some received prefixes were not shown in learned information display.

TSN

Bug Number Notes
1500481 TSN Conformance test case was wrongly stating the outcome as FAILED, it was fixed by taking into account the correct field from the Pdelay Req message.