IxNetwork 8.20 GA is an "General Availability" release. Please see the specific IxNetwork sections below for application compatibility requirements, known issues and the Product Compatibility Matrix for IxNetwork hardware support.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.20 GA |
---|---|
BPS | 8.20 GA |
FLIX OS | 2017.1.0.1 (XGS2-HS & XGS12-HS) 2017.1.75.6 (XGS2-HSL & XGS12-HSL) |
HLTAPI | 8.20 GA |
IxANVL | 9.10 GA |
IxChariot | Not Supported |
IxLoad | 8.20 GA |
IxNetwork | 8.20 GA |
Licensing | 4.50 EA |
Test Conductor | 3.60 GA |
Module Type | Supported Function | Module Part Number |
---|---|---|
Virtual Port | Control / Stateless Data Plane Testing | Ixia Virtual Load Module |
AppLibrary | Ixia Virtual Load Module | |
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 |
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 | |
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 | |
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 |
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 | |
AppLibrary | LSM1000XMVDC16NG, LSM1000XMVDC4NG, LSM1000XMVDC4, LSM1000XMVDC8, LSM1000XMVDC12, LSM1000XMVDC16, NOVUS10/1GE16DP, NOVUS10/1GE8DP | |
Fiber Channel | Control / Stateless Data Plane Testing | FCMGXM4S-01, FCMGXM8S-01 |
OC192 SONET | Control / Stateless Data Plane Testing | MSM10G1-01, MSM10G1-02 |
OC48 SONET | Control / Stateless Data Plane Testing | MSM2.5G1-01 |
OC3/12 SONET/ATM | Control / Stateless Data Plane Testing | LM622MR, LM622MR-512 |
Native IxOS | XGS2-HSL and XGS12-HSL | NOVUS100GE8Q28+FAN, XMR10GE16SFP+FAN, XMR10GE32SFP+FAN, XMR40GE12QSFP+, XMR40GE6QSFP+, XM10/40GE12QSFP+FAN, XM10/40GE6QSFP+FAN, XM100GE4CFP4 100GE, XM100GE4CFP4+ENH, XM100GE4CXP, XM100GE4CXP+FAN, XM100GE4QSFP28+ENH, XM100GE4QSFP28, XM40GE12QSFP+FAN, NOVUS-R100GE8Q28+FAN, Xcellon-FlexAP10G16S, Xcellon-FlexFE10G16S, Xcellon-Ultra NP |
Starting with version 8.10GA, 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)
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.20 GA ships with Ixia Licensing 4.50 GA. IxLicensing 4.30 GA and later is Ixia's new license management system. Ixia Licensing Utility (ILU) and License Server Plus (LS+) are replacing Ixia Registration Utility (IRU) and License Server (LS) used in earlier versions of IxLicensing. Some of the key benefits of this new licensing system are: - Simplified activation procedure - Improves offline activation using Request files. - Enhanced Host ID calculation to increase uniqueness of Host ID. - Allows remote activation of licenses - Allows configuration of Proxy settings For more information about the new IxLicensing system, please refer to the "Ixia Licensing Management User Guide" provided with the Ixia software, or downloadable from the Ixia web site.Installing a License
Ixia Licensing 4.50 upgrades Ixia Licensing 3.x, Ixia Licensing 4.25.x and prior versions on the machines. The reverse is not allowed. Upgrade can be performed for following scenarios: - Ixia Registration Utility (IRU) to Ixia Licensing Utility (ILU) - Old version of Ixia Licensing Utility (ILU) to the latest version of Ixia Licensing Utility (ILU) In case of IRU to ILU upgrade, ILU will override IRU and its registration numbers will be migrated as activation codes in ILU. During installation the system checks the connectivity with Ixia Licensing web servers. Based on the connectivity, the migration can be performed using following methods: - Online Migration - Offline MigrationPrerequisite Installation Notes
Ixia Licensing 4.50 installs .Net 4.0 on Chassis and .Net 4.5.1 on Clients and VM Chassis. NOTE: Ixia Licensing 4.50 installs .Net 4.5.1 on client machines. If an older release of an Ixia product containing .Net 4.0 hotfix is installed on top of this release, .Net 4.0 hotfix installation may fail. The workaround is to uninstall .Net 4.5.1 and then reinstall the older release of Ixia product and then modify this release of Ixia Licensing.Additional Documentation for Licensing
Please refer to our website at http://www.ixiacom.com/support-services/product-support/user-guides You will be required to provide a login and password to enter this section of the web site. If you do not have the username and password, please forward your request to support@ixiacom.com.
Upgrading from a release prior to IXOS 5.10 SP2
To ensure proper operation of an Ixia chassis with IxOS 5.10 GA SP3 or later versions of IxOS 5.10 GA, 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 GA release, multi-version installation is supported. This release can be installed without uninstalling the 5.40 GA releases. If the client or server components are earlier releases than IxNetwork 5.40 GA, the software must be uninstalled before installing IxNetwork 7.40 GA+.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 GA+ 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 GA+ 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 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 |
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.
Contact List Change: 4150211; Date: 2013/09/24 | |||||||||||
USA, Canada and Latin America Customer Support |
|
||||||||||
Europe, Middle East, and Africa Customer Support |
|
||||||||||
India Customer Support |
|
||||||||||
China Customer Support |
|
||||||||||
Asia Pacific Customer Support |
|
||||||||||
Japan Customer Support |
|
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.
Bug Number | Notes |
---|---|
1453941 | Packet Group Statistics view can sometimes show invalid PGIDs - other than the ones configured in the streams. Workaround to this problem is to reboot the Virtual Chassis. |
Bug Number | Notes |
---|---|
1446265 | The IAID for each interface in the DHCPv6 client is fixed. IAID and IAPD must be unique. It can be configured by patterns in the “IA ID” column on the GUI. |
Bug Number | Notes |
---|---|
1440651 | IxNetwork-OSPF: Differences in IxTclNetwork parameter order in OSPF do not influence setting the actual SDM parameter. |
1440670 | Resolved HL Command Interface_Config argument "autonegotiate" and speed option for Novus10/1/100M Module. |
1440673 | Updated HL API : traffic_config in case of circuit_endpoint_type FC for module FCM GXM8. |
1448671 | Resolved in HLAPI TLV Configuration parameter in DHCP TLV Option 77. |
1449042 | multiple issues have been fixed to address an issue where ixiangpf.connect will sometimes fail when ran in a loop. |
1449246 | Fixed the HL Command - ptp_over_ip_config communication_mode attribute value as mixedmode. |
1449253 | User can not specify more than one Rx port in HL API of quick flow traffic. |
1449605 | ixNet.execute('getTopologyStatus') now works correctly in python. |
1450132 | Resolved invalid protocol handle in RSVP egress Tunnel Configuration with HL Command : emulation_rsvp_tunnel_config. |
Bug Number | Notes |
---|---|
1437980 | Issues were fixed where GUI used to crash in some scenarios while using IxNetwork. |
1437982 | Fixed the GUI freeze issue in some scenarios while creating IxNetwork Stream. |
1448279 | In certain corrupted configurations where global start protocol was not getting started is fixed. |
1448281 | An issue of the application crash in certain scenarios is fixed. |
1448282 | An issue of the application crash in certain scenarios is fixed. |
1448287 | Fixed issue when IxN UI could hang on newConfig API call. |
Bug Number | Notes |
---|---|
1449598 | In a multi user environment if one user is doing a hot swap or mode change etc resource intensive operations on a Windows chassis, other users running test on the same chassis may experience temporary slowness or failures in operations like traffic start/stop. |
Bug Number | Notes |
---|---|
1442577 | Creating any IxNetwork Report using IxReporter was throwing exception. This issue is resolved currently with 8.20GA. |
Bug Number | Notes |
---|---|
1438716 | Use would be able to add distribute IPv4 or IPv6 FEC's behind targeted IPv4 or IPv6 LDP peer. |
1440635 | Fixed an issue where large scale configurations involving RSVP-TE Make Before Break (MBB) resulted in failed MBB action or failed protocol stop action. |
1440636 | IxNetwork is now able to bring down all RSVP-TE tunnels (25K), after make before break is performed for all of them. |
1440637 | Fixed an issue in RSVP Make-Before-Break (MBB) triggered with invalid indexes. Now if MBB is triggered with invalid index, GUI will throw an error. |
1440649 | Issue with port getting stuck in stopping state while stopping RSVP/ISIS protocol session is fixed now. |
1447259 | Traffic generation is proper for BGP+ IPv6 unicast endpoints. |
1449604 | In Symmetric Inter-subnet forwarding of EVPN, issue of traffic picking up wrong MPLS label has been fixed. |
Bug Number | Notes |
---|---|
1445221 | Fixed an issue where RFC2544 QT IMIX settings were not saved in IxNetwork 8.10. |
Bug Number | Notes |
---|---|
1438131 | Fixed an issue where IPv6 Router Solicitation message was not being sent while configuring it behind a Device Group. |
1440638 | For eBGP sessions the local preference option was set by default in NGPF. This has been corrected now. |
1440640 | Sometimes PCPU crashes while running IPTV. |
1440648 | IPTV zapping causes PCPU crash. |
1440762 | IxNetwork-EVPN: On the fly change of any parameters in MAC-pool will work properly. |
1440814 | Tcl Attributes -enableIncludeLoopback and -enableIncludeMulticast are added for the object vpnRouteRange. |
1440958 | BGP now handles Open message containing GR capability with empty AFI/SAFI list. Protocol doesn't stuck on start/stop. |
1444266 | Repeatable Random pattern works fine for BGP IP Route Range. |
1446630 | Sometimes unexpected prefixes were getting advertised while performing restart down operations on a configuration with multiple BGP peers. This issue has now been fixed. |
1446671 | E-bit is set in the OSPFv2 and OSPFv3 LS Update packets and the NSSA routes are properly attached. |
1447790 | IxNetwork-EVPN: Both MAC-mobility feature and Route Type-5 can be tested using same configuration. |
1449088 | Attributes under networkTe and rangeTe on a ISIS Network Range are set properly and don't require any specific order. |
Bug Number | Notes |
---|---|
1440633 | An issue with adding IPv6 Segment Routing header on top of IPv6 header through API has been resolved. |
1440634 | A port crash issue while fetching learned info or applying traffic on high scale ISIS-SR configuration is fixed now. |
1440641 | IxNetwork doesn't ask for Segment Routing license to run BGP 3107. |
1440644 | ISIS is shown up in the Network Group(NG) cloud only when the Connector is connected to Ethernet or Device Group. ISIS will not be present in NG if Connector is connected to any other upper layer protocol. |
1440647 | ISIS Learned Info now shows Adjacency SIDs. |
Bug Number | Notes |
---|---|
1438576 | Port crash may be seen when using PIM protocol and the workaround is to disable the PIM related statistics views. |
Bug Number | Notes |
---|---|
1437979 | Under rare circumstances IxNetwork GUI was crashing when editing traffic item in multiuser scenario. The issue has been fixed. |
1445222 | GUI hang issue in some scenarios is fixed while closing Traffic Wizard. |
1448283 | An issue where some TCP fields were not getting set properly when configured from IxNetwork traffic packet editor is fixed. For old configurations where this issue was happening user has to delete TCP options and add it again. |
1448286 | GUI option for Ingress Tracking is fixed for quick flow groups. |
1448401 | An issue related to traffic apply in a specific setup where it was taking a little longer time is fixed. |
1449597 | Multicast destination mac is now on sync with the multicast destination IP when user drop the link to the Ixia Tx port for a period of time and then do link up. |
1449601 | Enable DA MAC change on the fly option from IxNetwork working properly with the Linux chassis. |
1452045 | GENEVE Header option is added under Protocol menu of raw traffic. |
Bug Number | Notes |
---|---|
1446623 | Fixed an issue that was causing Traffic Apply failures, when the Device Group pattern was configured as Subset. |
1447086 | Fixed a port crash issue visible when starting the traffic which was caused by an invalid memory access from kernel. |
1451052 | Fixed an issue that caused negative latency values caused by poor NTP synchronization. |