Ixia Software Release Notes
IxNetwork 9.10 Update 2
Build Number: 9.10.2011.152 (April 27, 2021)
IxNetwork 9.10 Update 2 is an update release on top of IxNetwork 9.10.
For a complete list of all the new features included in this release, please refer to the 'What's New' section below.
Application Compatibility
As an update release, IxNetwork 9.10 Update 2 has the same compatibility as that of IxNetwork 9.10 release.
For IxNetwork 9.10 Update 2, use 1.8.32120.12 version of Wireshark.
For Protocol Wizards, we need Windows 10 or higher as the client operating system.
For additional product compatibility information, refer to the following online utility on Ixia's website. You must provide your Ixia account credentials to access the Ixia website.
http://www.ixiacom.com/support-overview/product-support/product-compatibility-matrix
Installation procedure for Classic Protocols
Note: The following installers are only relevant if you want to use classic protocols.
The installers are available in the "IxNetwork Classic Protocol Installers" section of the support page at https://www.support.ixiacom.com
1. For Windows Client, use the installer "IxNetwork-Protocols.msi" available in the support page.
2. For Windows Chassis, use the installer "IxNetwork-ProtocolsChassis.msi" available in the support page.
3. For Hogan Chassis, use "ixnprotocolschassishw-9.10.2500.1.i686.rpm" available in the support page.
4. VM and VMOne Builds with Classic Protocols is also available in the support page.
Starting with version 8.10 EA, you must provide your credentials while starting the IxNetwork User Interfaces.
The credentials are validated using an e-mail based authentication mechanism. For details see Start IxNetwork section in the IxNetwork Getting Started Guide.
You must create an account before you start using IxNetwork. Select the Create new account option on the login page available at: login.ixiacom.com and enter your details.
You will receive an email. You can use the new account only after you verify the email 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 to 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)
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.
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: 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.ix@keysight.com.
To install this update, you must have the IxNetwork 9.10 'client' component installed on the user workstation where the IxNetwork GUI will be run.
IxNetwork update notifications are available through Ixia Update Manager.
Select and apply the update to the existing IxNetwork 9.10 or download the update installer for manually installing the updates at a later time.
Installed updates are visible under control panel -> installed updates for IxNetwork 9.10
Refer to the following notes to rectify the problems that may arise during installation.
NOTE: During installation of an update, if the Update Manager status does not change even after several minutes or if the update fails to install, then restart the system and reinstall the update.
NOTE: Once an update is installed, it disappears from the Update Manager until it is manually uninstalled from the control panel.
Please contact Ixia customer support for upgrades if needed.
IxNetwork Web Edition
1. IxNetwork Web Edition supports IxNetwork web based user interface, QuickTest, and API Browser.
2. IxNetwork Web Edition can be installed on VM (ESXi and KVM), Native IxOS chassis.
3. IxNetwork Web Edition software (OVA, QCOW2, Docker, and HSL package) are available as downloads from the Ixia website.
| IxNetwork Web Edition |
OS |
Network |
Storage |
| ESXi OVA |
ESXi 6.0 Update 2 or ESXi 6.5 (64 bit only) |
VMXNET3 |
128 GB |
| KVM QCOW2 |
Ubuntu 18.04 LTS or CentOS 7.6.1810 (64 bit only) |
virtio |
128 GB |
| Docker |
Ubuntu 18.04 LTS or CentOS 7.6.1810 (64 bit only) |
Promiscuous mode enabled |
128 GB |
| Application |
IxNetwork Web Edition |
| Google Chrome |
75 or newer |
| Mozilla Firefox |
70 or newer |
| Microsoft Edge |
44.17763.1.0 or newer |
| Apple Safari |
12.1.1 or newer |
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 the link displayed on the console screen (from the browser).
4. Log in with credentials username: admin and password: admin
5. To start the QuickTest session manually, click "New Test".
6. To start the 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 the 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 the link displayed in the console screen (from the 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 the corresponding language.
10. Sample codes are given for each language and follow the steps.
IxNetwork Web Edition can be deployed as a Docker container via the provided image
Note: IxNetwork Web Edition is supported as Docker container with CentOS and Ubuntu Distributions.
1. Copy the .tar file on the host
2. Make sure the interface has promiscous mode enabled
3. Load the image to docker: docker load -i </path/to/tar/file>
4. Create the macvlan bridge to be used by IxNetwork Web Edition: docker network create -d macvlan -o parent=<interface> --subnet <subnet> --gateway=<gateway> <bridge_name>
5. Deploy the IxNetwork Web Edition container using the following command:
a. When using MAC VLAN BRIDGE:
docker run --net <BRIDGE NAME> \
--ip <CONTAINER IP> \
--hostname <HOSTNAME> \
--name <CONTAINER NAME> \
--cap-add=SYS_ADMIN \
--cap-add=NET_ADMIN \
-i -d \
-v /sys/fs/cgroup:/sys/fs/cgroup \
<IMAGE NAME>
b. When using HTTPS on a specific external port and host IP:
docker run \
- p <EXTERNAL PORT>:443 \
--cap-add=SYS_ADMIN \
--cap-add=NET_ADMIN \
-i -d \
-v /sys/fs/cgroup:/sys/fs/cgroup \
<IMAGE NAME>
6. Open up a browser and connect to the configured IP.
7. Log in with credentials username: admin and password: admin
8. To start QuickTest session manually, click "New Test".
9. To start IxNetwork API Server session manually, click "New API Server".
10. To start scripting, click "Download a client".
11. Make sure that all dependencies are installed before starting scripting.
12. Click on package downloads for corresponding language.
13. Sample codes are given for each language and follow the steps.
14. Optional mapping of configuration files, results and settings to external folders on host add the following parameters to the command:
-v <HOST CONFIGS LOCATION>:/root/.local/share/Ixia/sdmStreamManager/common \
-v <HOST RESULTSLOCATION>:/root/.local/share/Ixia/IxNetwork/data/result \
-v <HOST SETTINGS LOCATION>:/root/.local/share/IXIA/IxNetwork.Globals \
* The ip parameter assigns a specific IP to the container
** Name and Hostname are optional parameters
IxNetwork Web Edition can be installed on HSL/SDL/AresONE/Novus ONE chassis
1. Connect to XGS12-HSL/XGS2-HSL/XGS12-SDL/XGS2-SDL/AresONE/Novus ONE 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 the 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 the 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
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.
Please refer to the IxNetwork documentation for guidance on its usage.
|
Ixia Headquarters
|
|
Support
|
Please refer to our website at https://support.ixiacom.com/support-overview/product-support/downloads-updates.
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.ix@keysight.com.
9.10 Update 2 Features
| Access |
| NGPF DHCP emulation now allows padding bytes length based on user input. |
| Automation |
| SRv6 EVPN emulation now supports High Level APIs. |
| SRv6 L3VPN emulation now supports High Level APIs. |
| Infrastructure |
| Support for disabling IPv6 Link-local address is added to reduce Neighbor Solicitation in scaled environment. |
| Routing/switching |
| BGP Add-Path feature now supports VPNv4 and VPNv6 routes. |
| SDN |
| Flexible Algorithm support for OSPFv2 is introduced to test constraint-based SR path computation (draft-ietf-lsr-flex-algo-13). Traffic Engineering for OSPFv2 is also enhanced to support Extended Admin Group as per RFC 7308. |
| EVPN VXLAN is enhanced to support emulation of EVPN SMET route (route type 6), EVPN Multicast Join Synch route (route type 7), EVPN Multicast Leave Synch route (route type 8), and EVPN S-PMSI A-D route (route type 10). PIM-SM and PIM-SSM tunnel types in control plane and traffic for EVPN S-PMSI A-D route are supported. |
| NETCONF Server emulation now supports sending periodic unsolicited notifications. |
| G-SRv6 support is introduced to test SRv6 header compression optimization scheme. This includes control-plane support for ISIS, BGP-LS, and BGP SR Policy protocols, along with data-plane support for IPv4/IPv6 L3VPNs. |
| PCEP emulation is enhanced to support RFC 8664 (PCEP extension for segment routing). |
| PCE emulation now supports updating PPAG information of the learned Sync LSPs through PCUpdate message. |
| TSN |
| TSN Conformance suite for IEEE 802.1Qbv is enhanced with support for configuring gate control list on the DUT after time synchronization is established. |
| Timing and Synchronization |
| NGPF PTP emulation now supports PTP telecom profile defined in ITU-T G.8275.2. |
SDN
| Bug Number |
Notes |
| 1557706 |
The tab “Additional Algo/SID” in Network Group for ISIS/OSPFv2 routes with flex-algo is not visible from the protocol tree view in GUI. Use the scenario view to see this tab.
|
Access
| Bug Number |
Notes |
| 1556485 |
PCPU encounters error while collecting results after test run.
|
| 1559076 |
For NGPF DHCP Relay Agent emulation the information request Option 82 is not acting according to RFC 3046.
|
High Level API
| Bug Number |
Notes |
| 1555818 |
Connection to port is intermittently lost while executing running automated regression cases.
|
Infrastructure
| Bug Number |
Notes |
| 1559525 |
Classic Protocols are not visible on restored configuration where configuration was created using IxNetwork 9.0 Update 3 version.
|
| 1560295 |
ISIS L3 prefix SID tab is not visible on the NextGen Framework panel view.
|
| 1560387 |
Protocol Server set API fails on card types other than Novus cards. (Applicable for IxNetwork Classic only)
|
MPLS
| Bug Number |
Notes |
| 1556892 |
While performing a series of protocol operations for a long time, port becomes unresponsive at times.
|
| 1556914 |
IxNetwork is unable to create L2 traffic item when L3 VPN service is present in the topology.
|
| 1560457 |
The outer MAC address of the traffic from PE to CE direction of MVPN following Rosen draft was taking MAC address of CE instead of PE. (Applicable for IxNetwork Classic only)
|
Routing/switching
| Bug Number |
Notes |
| 1556479 |
Ixia port sends malformed OSPFv3 LSA update message due to extra 4 bytes introduced in the packet.
|
| 1559301 |
Ixia port sends malformed BGP update messages when Unicast Add Path capabilities are enabled for large number of routes.
|
| 1559558 |
Due to unpacked SUB-TLV in ISIS LSP, DUT is unable to install traffic engineering prefix forwarding reachability.
|
| 1560257 |
Ixia port drops OSPFv3 PDUs with zero checksum when authentication is enabled.
|
| 1560459 |
Toggling the "TYPE" column from "External" to "Internal" under "BGP-Peer" tab was not automatically toggling the "AS# Set Mode" column value to "Do not include local AS#".
|
| 1560470 |
When L3Site is enabled, there is unexpected port behavior on BGP withdraw action. (Applicable for IxNetwork Classic only)
|
| 1560594 |
Ixia BGP emulation does not learn Discovered DUT IP - link local when Unnumbered BGP is not configured as the first session.
|
SDN
| Bug Number |
Notes |
| 1555643 |
BGP-LS learned information displays only one node when multiple node NLRIs with same Router ID but different Area IDs are received.
|
| 1560315 |
IxNetwork ISIS emulation with Flexible Algorithm becomes unresponsive while performing failover operation at DUT side.
|
Timing and Synchronization
| Bug Number |
Notes |
| 1557367 |
Per device group statistics were not getting fetched through HLTAPI for NGPF PTP.
|