Ixia Software Release Notes
IxNetwork 8.40 EA
Build Number: 8.40.1124.8 (December 15, 2017)


About This Release 

IxNetwork 8.40-EA is an "Early Adopter" release for Release Train 2, 2017.
This release consolidates all releases since the last Release Train, including IxNetwork 8.30 EA, 8.30 EA Patch1, 8.31 EA as well as the IxNetwork update release on top of 8.30 EA.

This release is focused on enhancing Infrastructure and Automation to improve overall user experience. For a complete listing of all the new features included in this release please, refer to the 'What's New' section.

- Support Native IxOS on the new XGS2-SDL (940-0013) and XGS12-SDL (940-0015) chassis. IxOS now runs natively on the SDL chassis without Windows Operating System
- Major improvements to NGPF framework - Expose Network Group under NGPF protocol tree in left pane, enhanced Network Group with more flexibility in configuration, ease the Scenario view navigation with name search and undock Scenario view option
- Improved automation capability - Enhance API Browser for easy navigation, IxNetwork configuration in JSON format, Linux API server on HSL chassis, Automation Guide book providing best practice with example and code snippets
- Enhanced VE infrastructure - Support higher NIC speeds (10G / 25G / 40G), new capability to operate inside Docker Container environments, simplified installation (Deployment Wizard improvements for vCenter / DRS and KVM / OVS) and simplified configuration (improved Web UI and CLI)
- QuickTest Web Edition support new BGP Failover Convergence Test and mixed IPv4/IPv6 support
- Continue expand SDN test coverage - PCE support learning and updating synced LSP, PCC support dynamic MPLS traffic, ISIS-SR spec update

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

      
         
          

              BPS
              8.40 EA
          
       
	  

              FLIX OS
              2017.2.0.4 (XGS2-HS & XGS12-HS)
2017.2.77.17 (XGS2-HSL/XGS12-HSL/XGS2-SDL/XGS12-SDL/NovusONE/PSONE)		
          
	 
	  

              HLTAPI
              8.40 EA
          

	  

              IxANVL
              9.17 EA
          

	  

              IxChariot
              Not Supported
          

          

              IxLoad
              8.40 EA
          

          

              IxNetwork
              8.40 EA
          

          

              IxVM
              8.40 EA
          

          

              Licensing
              5.00 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 / 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  
          

      
  



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.40 EA ships with Ixia Licensing 5.00 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 5.00 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 5.00 installs .Net 4.0 on Chassis and .Net 4.5.1 on Clients  and VM Chassis.
 
NOTE: Ixia Licensing 5.00 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.

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

 1. Connect to XGS12-HSL/XGS2-HSL 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 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.

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

AVNU
AVNU conformance test cases are added for Automotive profiles supporting Automotive Generalized Precision Time Protocol (gPTP), Automotive SR Classes and Forwarding and Queuing Enhancements for Time-Sensitive Streams (FQTSS), Automotive Network Device Start-up (STARTUP), Automotive Exception Handling (EXCEPTION), Automotive Diagnostic Counters (COUNTERS), Automotive Media Formats and SR Classes (AVTP)

Access
NGPF DHCP server now send FORCERENEW message with CIADDR field populated as client IP address
A new option of "Skip Release on Apply Change" is added to DHCP Relay Agent TLV Profile. If it is enabled, along with Skip Release on Stop, the client sends DHCP Request to renew the lease upon any change to Relay Agent TLV parameter.
NGPF DHCPv6 is enhanced to support non-EUI-64 derived link local address by providing user configurable custom IPv6 link local address.
A new flapping mode "Stop" is added for NGPF ANCP. When flapping mode is changed from "Reset" to "Stop", all subscriber lines return to "SHOWTIME" state.
NGPF ANCP now support parallel protocol start/stop mode to emulate realistic subscriber behavior along with other subscriber emulations, such as PPPoE, DHCP, etc.

AppLibrary
Applibrary is enhanced to enable consecutive simulated user to take up unique consecutive IPs, until the IP pool is exhausted. This will enable distribution of the flows across all available subscribers much faster.

Automation
Linux API server now support L23 Raw traffic and Quick Flow Groups configuration
Support for installation of IxNetwork Linux API Server on HSL chassis
API Browser for Windows and Linux IxNetwork API Server is enhanced for easy navigation of configuration, methods and operations

High Level API
HL API support has been added for OVSDB Controller emulation.
Added HLAPI support for ISIS SRLG and multiple algorithm.

Infrastructure
Nextgen Protocol Framework (NGPF) now support route increment step in a route range for BGP, ISIS and OSPF protocols.
NGPF Topology/Device Group/Network Group in Scenario view can now be searched with name. Finding the desired configuration object is much easier now.
Network Group in Nextgen Protocol Framework (NGPF) is now available under NGPF Protocol Tree in Left navigation panel.
A new "Repeatable Random (Range)" pattern is added to pattern editor which allows random value generation within a defined range and guarantee unique value generation
BGP IPv4 Statistic Route Generation wizard is enhanced to generate unique routes with prefix distribution in a more effective way. New IPv6 Statistic Route Generation wizard is added with same functionality as IPv4.
Nextgen Protocol Framework (NGPF) now supports API in the scripting path using which all the pre-start activities of a configuration could be completed. This would be useful in scenarios when there is need of starting emulation for all the protocols in configuration in co-timed manner. Suggest update as below: Nextgen Protocol Framework (NGPF) now supports pre-configure option in API to complete configuration task before start protocol emulation. This is useful in the scenario which the start of different protocol emulations need to be aligned for more accurate measurement.
TX Lane configuration is added in Layer 1 Configuration for Novus QSPF28 load module. This allows creation of mapping among physical lanes and virtual lanes. A new statistics view is added named “PCS Lane Statistics” in IxNetwork. User needs to enable Data Collection explicitly in order to see PCS Lane Stats.
IxNetwork configuration now can be export/import in JSON format with the option for full or partial configuration
NextGen Protocols Learned information is changed from pop-up window to new Learned information tabs in protocol grid.
NGPF now support Network Group for a specific protocol instead of sharing by all protocols in the DG. This is supported by BGP Peer/BGP+ Peer, OSPFv2, OSPFv3, and ISIS-L3.
Added option to enable/disable Traffic QuickFlow Group and Egress only Flow Tracking. HLAPI is supported too.
Nextgen Protocol Framework (NGPF) now support running Routing and MPLS protocol emulations over GRE. This feature is Beta quality. MPLS traffic over GRE does not work as expected and will be enhanced in next release
A new "Undock Scenario" button is added in Scenario view ribbon to allow user to undock the whole scenario region, including the protocol grids

MPLS
NGPF EVPN is enhanced to support type 5 route for IP-VRF to IP-VRF interface-less use case in MPLS data plane
A checkbox "Always Include Tunnel Encapsulation ExtComm" is added in EVPN sub-tab of BGP Peer tab. When this checkbox is enabled, EVPN routes are advertised with tunnel encapsulation extended community for MPLS data plane
RSVP-TE LSP is enhanced to support a configurable delay time in switch over during Make Before Break operation
EVPN is enhanced to support user configurable PMSI tunnel ID
NGPF BGP RFC3107 (BGP LU) now support TrueView convergence (CPDP)
EVPN is enhanced to support multicast traffic over mLDP P2MP LSP
EVPN is enhanced to support multicast traffic over RSVP-TE P2MP LSP
NGPF MPLS-OAM is enhanced to support RSVP-TE LSP and L2VPN pseudowires over RSVP-TE LSP

NOVUS100GE8Q28+FAN
Continous Burst support is added under Advanced Stream Scheduler mode for Novus 100GE and 40GE ports.

QuickTest Web Edition
QuickTest Web Edition now supports new RFC7747 BGP Failover Test with Port Down and Withdraw Routes Failover modes
QuickTest Web Edition now supports to populate Traffic UDP/TCP ports, Protocol IP Addresses and VLAN IDs from a CSV

QuickTests
QuickTest now support removing logs older than a specified number of days

Routing/switching
NGPF BGP emulation now support random AS path generation for advertised routes

SDN
PCEP: PCE emulation now support learning sync LSP and updating synced LSPs by PCUpdate message with learned information to show detailed information of LSPs. .
OVSDB Server emulation now supports multiple VNIs per VTEP. The number of VNIs can be configured by using the multiplier for VXLAN stack
BGP SRTE Policy emulation now support dynamic update SRTE policy without stop and restart BGP session. This feature is beta quality.
ISIS SR is updated to support version 13 of draft-ietf-isis-segment-routing-extensions. This includes support for SRMS preference sub TLV, P-flag for Adjacency SID, SR Local Block sub-TLV.
PCEP: PCC emulation now supports updating MPLS Label values dynamically (DMPLS) for data traffic over all types of SR-TE LSPs.
OVSDB Controller: OVSDB Controller is enhanced to support following features: 1) Support for deleting/modifying the bindings on restarting the Controller has been supported for multi-ToR scenario. 2) User can restart the Controller alone. It is assumed that no DB changes will be made to ToR while the Controller is down. 3) Table Value and Table Schema validation has been added. 4) User can now dump the DB Updates received from ToR by triggering Controller Dump DB command. 5) ToR Certificate validation has been supported. User has to tick the checkbox “Verify Peer Certificate” for this validation. 6) User can now stop a specific ToR from connecting to the OVSDB Controller over TCP by using the command “Delete ToR”. Similarly, this ToR can be allowed to connect by using the command “Add ToR”. 7) Users can now attach all the 4000 bindings (for one VM and one Baremetal each binding) in a single batch. The transact timeout should be set to at least 1000s. 8) A new type of certificate validation has been supported that will validate the Server certificate file by comparing it with the locally stored certificate file.
PCEP: PCC emulation now supports data traffic generation when SR-TE LSP has ERO with only NAI information of type "IPv4 Adjacency" or with only SID information of type "SID".
PCEP: PCC now supports including Association object for Path Protection (PPAG) in PCReport messages while reporting SR-TE/RSVP-TE Sync LSPs.

Traffic
On The Novus 100G/50G/40G/25G/10G Load Module family, IxNetwork L23 Traffic Configurations with Weighed Pair Random Frame Size Distributions (namely Random IMIX frame size distribution ranges) will benefit from optimized software hardware resource usage allocations.
Enhancement to achieve 100% line rate when using IMIX frame size pattern in traffic configuration in NOVUS100GE8Q28.

VM
Support for new Mellanox Ethernet Controllers running in PCI PT or SR-IOV mode has been added. The list of supported NICs now includes 10G / 25G / 40G models.
Support for Web UI for the Virtual Test Appliance has been added. This new graphical interface greatly simplifies the Virtual Test Appliance management operations.
Support for Web UI for the Virtual Chassis has been improved. Newly added capabilities include displaying the Port Statistics, Real Time Logs, as well as a Tutorial Mode.
Support for Live Production Networks / SNMP Notifications has been improved, with the ability to Enable / Disable individual traps, as well as to configure Thresholds.
Support for Live Production Networks / Resource Utilization has been improved. The Virtual Chassis Disk Size requirements have been decreased from 40 GB to 8 GB.
Support for Command Line Interface (CLI) Debugging has been improved, with new commands added (arp, ethtool, lspci, netstat, ssh, tcpdump, traceroute, traceroute6).
Support for Deployment Wizard has been improved, with the ability to create vChassis / vCards inside VMware vCenter / Distributed Resource Scheduler environments.
Support for Deployment Wizard has been improved, with the ability to create vChassis / vCards inside stand-alone KVM environments using Open Virtual Switch (OVS).
Support for Docker Containers has been added (BETA). The vChassis / vCards can be deployed as containers with SR-IOV network connectivity, orchestrated with Docker.

Known Issues List

Access

Bug Number Notes
1457685 Under certain configurations with very high scale of access protocols which causes broadcast storms of millions of packets across the configured interfaces due to packet duplication, port instability may be observed during starting/stopping of the protocols. The recommended solution would be to reduce the start/stop rate of the access protocols or to use VLAN (one or more) to prevent broadcast.

Automation

Bug Number Notes
1462017 Occasionally IP interface setup and ARP may fail on ports only if IxTclHal is used to force clearing ownership on ports assigned to 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.

High Level API

Bug Number Notes
1457922 The string values in IxNetwork GUI should be configured using the pattern generator especially if the string value contains spaces. Otherwise, the string values may not be restored properly using HLT API scripts generated by ScriptGen.

Infrastructure

Bug Number Notes
1463124 For default phy mode in Novus 10G/1G cards IxNetwork was giving priority to sgmii, fiber and copper from highest to lowest respectively. That means, if default is copper(as per preference) but copper mode is not available in the port it tries to set sgmii, if sgmii also not available it tries to set fiber. By this fix, this priority would be changed. Revised priority would be copper, fiber and sgmii respectively from highest to lowest. After this change, if default is copper(as per preference) but copper mode is not available in the port it would try to set fiber, if fiber also not available it tries to set sgmii. In general in previous releases a Novus 10G port would be added in IxNetwork in Fiber mode but now it will default to copper or the mode set through preference. No saved configurations will be affected by this. In existing automation scripts if Novus 10G Dual Phy ports are added to IxNetwork and used in Fiber mode (without explicitly changed to fiber) then those scripts will need modification to set to desired mode or use IxNetwork preference to set default mode to Fiber.
1464251 It has been observed that there is an existing issue that when a novus10G card’s port with copper mode is unassigned the mode changed to fiber. If subsequently same port is assigned again the mode remains as fiber. It is expected that in offline mode port should remain in same mode as it was in connected mode.
1466340 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.
1466345 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".

MPLS

Bug Number Notes
1461562 When port is stressed due to very large number of BFD sessions, sometimes port crash could happen. If any such issue is faced, workaround could be scaling down the number of BFD sessions on that port. This issue only happens in case of standalone BFD sessions and does not occur when BFD is bootstrapped by other protocols such as OSPF, BGP etc.

Misc (include Analyzer, license, installation, etc)

Bug Number Notes
1457573 In IxNetwork, PCS statistics are only available for Novus 100G and later cards.

QuickTest Web Edition

Bug Number Notes
1463447 IxNetwork Web Edition QuickTest RFC7747 (Failover mode), when run for multiple trials, may, at times, terminate prematurely before completing the provisioned number of trials.
1464625 IxNetwork Web Edition QuickTest RFC7747 (Failover mode), when run for multiple trials, may, at times, terminate prematurely before completing the provisioned number of trials.

Routing/switching

Bug Number Notes
1456647 The API for configuing IP address step value used in statistical route distribution (bgpIPRouteProperty) for BGP routes now takes input in integer format instead of dotted decimal format.
1456940 ISIS protocol does not advertise non-unicast IP addresses. If addresses in the network range are configured in multicast range or broadcast, then these are advertised starting from 0.0.0.0.
1464263 Drilldown Stats per Session is not working for BGP+ when both BGP BGP+ are present on the same port.

SDN

Bug Number Notes
1405932 PCEP: PCC emulation now sends PCReport message with updated RRO information for an RSVP-TE LSP, if the RRO is changed by a RESV Refresh message without any change in LSP State.
1457437 NGPF Openflow Controller supports only these learned infos in 8.40 EA release- Channel, Auxiliary Channel, and Topology. Other learned infos including PacketOut (triggered from PacketOut info) are not supported in this release.
1458485 PCEP: Low level API to configure "send PCUpdate" trigger parameters for SR/RSVP Sync LSPs from PCE Learned Info is not supported.
1460170 The control event "StartAll" is not supported for OVSDB Controller, hence while generating HLT API script for OVSDB Controller, the option "Include Control Event" should be unchecked.
1464264 Traffic configured with IPv6 Segment Routing Header (SRH) does not work in HSL/SDL chassis with Xcellon-Flex type of load modules.

Traffic

Bug Number Notes
1459317 Improvements were made in this release to achieve 100% line rate when using IMIX frame pattern in Novus 100G caards. However those improvements are limited to Interleaved mode and does not apply to sequential mode. For Sequential mode the same performance as previous releases will persist.
1460166 Traffic Start time taking 53% higher with metronome with respect to legacy chain.
1462253 Improvements were done to get to 100% line rate incase of IMIX for Novus boards in 8.40. However in some corner cases (like having too many flow groups with different rates) user may see rates not achieving 100% line rate consistently.
1463622 Join Latency and Leave latencies will come as N/A for few flows if hosts are listening to same multicast group in Multinic scenario

VM

Bug Number Notes
1451216 Performing release / connect ports from IxNetwork after changing the Promiscuous Mode settings will revert these settings to the original values.
1456753 Performing on the fly changes on traffic running on top of multiple Virtual Ports (50+) will cause traffic rate instability caused by the packets scheduling in the Virtual Load Module kernel. Some Virtual Ports are sending more packets than they should in interleaved move per flow. Workaround is to reduce the number of ports in test or switch to the sequential transmit mode.
1456867 Running L2-3 traffic with Fixed Packet / Iteration Count rate settings will sometimes show an incorrect number of total packets sent. This is a legacy behavior and there is no available workaround.
1458729 Running Raw or Quick Flow Groups traffic on ports with promiscuous mode disabled will cause 100% loss if the flows are not configured with the test port MAC address.
1458998 Starting L2-3 traffic in IxNetwork will cause ports configured with Mellanox 10Gbps mlx4 drivers to go down and back up for 1 second. This is a Mellanox driver limitation.
1459154 Multicast protocols and traffic running on SR-IOV Mellanox configured test ports will not function properly due to a 3rd party driver limitation.
1459605 Mellanox 25Gbps SR-IOV Ethernet Controllers has no support for VLAN on VMware ESXi hypervisors.
1462408 Due to an internal VEPA switch in the Intel XXV710 Ethernet Controller - sending traffic into VFs of the same Physical Function will cause the switch to reflect back traffic meant for the same port and result in much higher throughput. VEPA is by default enabled.

Resolved Defects List

Automation

Bug Number Notes
1461072 Establishing a connection to the SDM server port is not supported. This can cause IxNetwork to crash. This is an internal port only to be used by ixia software. The port can be identified on the caption of the GUI as SDM:xxxx Customer applications such as port scanners can cause the crash condition and should be setup to avoid scanning the SDM port.
1463879 Protocol attributes like session status or learned info are deprecated for performance reasons starting in 8.40 and replaced by corresponding execs. The change only affects REST scripts but a user can still use the deprecated attributes in REST by asking for deprecates in the query string parameters (ex: deprecated=true) or by explicitly asking the attributes the user is interested in (ex: include=sessionStatus)
1463932 Resolved unwanted clearing of ownership of ports of Novus five speed dual Phy module from HL Connect API
1464111 Resolved return value of stream id of quick flow traffic item in HL API of traffic_config
1464122 Resolved file permission issue in HL API command ixiangpf.emulation_bgp_route_config mode for import_route argument

Infrastructure

Bug Number Notes
1453294 Added extra logging for this issue so if this is happening again to be able to understand what has happened.
1455085 The hang was caused by few controls created on the wrong thread. In 8.40 we've found all the incorrect controls and moved them on the correct thread.
1455870 Removed the "Starting/stopping protocols" legacy progress bar that was causing the crash.

MPLS

Bug Number Notes
1426057 Dynamic MPLS label update support in traffic is added for Inter-AS Option C scenarios in L2VPN and L3VPN.
1450472 In NGMVPN simulation, Ixia does not match DUT's RD with its own RD.
1450473 Ixia Does not advertise source tree join upon reception of Source Active AD route when receiver site is configured with shared tree C-Multicast route type when "Send Triggered Multicast Route" is enabled.
1454897 Sometime numbering of EVIs in MAC pool is inconsistent
1458898 Peer IP Address in BGP C-MAC property displays wrong IP address when 2x stack multiplier is used between IPv4 loopback and BGP peer
1462097 Route type 2 withdrawal with MAC/IP and two MPLS labels causes DUT to treat it as malformed update and bring down BGP session
1462409 Port crash in LDP occurs when transport address is changed from loopback to interface IP

QuickTests

Bug Number Notes
1452768 Fixed an issue where IGMP emulated hosts did not send an extra join extra join before the leave messages. This is because we do not start IGMP protocol on this test and no response is sent to query messages.
1455993 RFC3918 Join/Leave Delay quick test may report larger than expected delay if the timing port fails to set to loopback mode. This issue is fixed.

Routing/switching

Bug Number Notes
1446632 An issue with BGP emulation sometime advertising wrong prefixes during multiple protocol reconnect is resolved now.
1450578 A GUI crash on configuring Ixia BGP emulation over loopback interface.
1452627 Using HLAPI the value of a field sid_count in ISIS Segment Routing could not be set to more than 65000.
1452631 ISIS Area ID in Hello Packet is now fetched properly from Analyzer using API.
1459464 Resolved a port crash due to frequent restart down operation when multiple BGP peers are configured using stack multipler.
1459532 Starting the IP stack may trigger the the starting the BGP stack on legacy cards.
1462982 An issue with ISIS Simulated Topology external link page has been fixed. If an external link was deleted then going back to the edit page sometime did not show all the available nodes.

SDN

Bug Number Notes
1433838 PCEP: If PCE (DUT) includes any ISIS-TE nodes as ERO in an SR-TE LSP which are configured within the Ixia Ingress port (data traffic source), Ixia PCC ignores them and generates data traffic without the corresponding MPLS labels.
1446458 PCEP: PCC now reports proper operational state as "Active" for RSVP LSPs if SREFRESH is enabled.
1462816 In BGP SRTE Policy GUI, there was an issue with multiple back-and-forth changes in the field "Number of SR TE Policies". This resulted in incorrect number of segment lists/segments getting configured in the GUI config, and ultimately lead to port crash.

Statistics

Bug Number Notes
1439588 Proper csv snapshot is generated now as per the help.
1450730 Fixed Egress tracking for Flat Egress views.
1461094 Fixed the issue of no stats in traffic item stat view in IxNetwork when one or multiple hotfixes were installed over IxOS after chassis reboot.

Traffic

Bug Number Notes
1460225 Fixed the integration between traffic endpoint selection and DHCPv6 for ports down use case.

VM

Bug Number Notes
1453206 Fixed an issue causing incorrect UDP checksums on traffic running with GTPu / IPv4 / UDP headers.
1453247 Fixed an issue causing incorrect Inner UDP Checksum when running UDP / IP over VXLAN traffic.