Ixia Software Release Notes
IxNetwork 9.20 Update 3
Build Number: 9.20.2206.84 (September 2022)
IxNetwork 9.20 Update 3 is an update release on top of IxNetwork 9.20. Update 3 is cumulative and includes contents from Update 1 and 2.
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.20 Update 3 has the same compatibility as that of IxNetwork 9.20 release.
For IxNetwork 9.20 Update 3, use
- Wireshark 3.2.6.210
- IxOS 9.20, 9.20 Patch1, 9.20 Patch2
- Licensing 5.50
For Protocol Wizards, we need Windows 10 or higher as the client operating system.
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://support.ixiacom.com/version/ixnetwork-920-update3
1. For Windows client, use "Client Installer (Windows)".
2. For Windows chassis, use "Chassis Installer (Windows)".
3. For Native IxOS chassis, use "Chassis Installer (Native IxOS) Offline Update Package".
4. No additional installer is needed for IxNetwork VE.
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: https://ksm.software.keysight.com/content/KSMQuickReferenceGuide.pdf
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.20 'client' component installed on the user workstation where the IxNetwork GUI will be run.
Download IxNetwork Update software from the Ixia website and Double-click on the file from within Windows Explorer.
Installed updates are visible under control panel -> installed updates for IxNetwork 9.20
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. Decompress the .tar file: tar xjf <file.tar.bz2>
4. Load the image to docker: docker load -i </path/to/tar/file>
5. 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>
6. 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>
7. Open up a browser and connect to the configured IP.
8. Log in with credentials username: admin and password: admin
9. To start QuickTest session manually, click "New Test".
10. To start IxNetwork API Server session manually, click "New API Server".
11. To start scripting, click "Download a client".
12. Make sure that all dependencies are installed before starting scripting.
13. Click on package downloads for corresponding language.
14. Sample codes are given for each language and follow the steps.
15. 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
*** Docker containers need sufficient space on the host, if not the sessions will not start
**** If the container needs to be launched with the full list of capabilities, launch the container in --privileged mode
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.20 Update 3 Features
| Access |
| vBRAS CP emulation now shows data traffic information received in event message from vBRAS UP as Learned info. |
| NGPF PPPoE emulation now supports requesting specific IPv4 address for a user configurable count when requested IPv4 address is not learned in NAK sent by Server. |
| NGPF PPPoE emulation now supports configuration to send LCP configuration request for a configurable number of times with the local configuration. With these options, PPPoE client can choose not to remove the configuration in the reject packets sent by the Server/Peer in the subsequent LCP configuration requests. |
| NGPF PPPoE emulation now supports configuration for PPPoE clients to abort after successful LCP authentication phase. |
| NGPF PPPoE emulation now supports IPv6CP compression protocol options. It supports IP header compression and Robust header Compression protocols. |
| Infrastructure |
| The retransmission values for Neighbor Solicitation (NS) and Address Resolution Protocol (ARP) have been increased. |
| IPv6 stack now supports custom link local address. |
| L2 Security |
| Wireshark version delivered with IxNetwork is now enhanced to decrypt captured MACsec packets by providing necessary decryption parameters in ‘MACsec’ protocol option under Wireshark ‘Edit -> Preferences’. |
| MKA emulation is enhanced such that it does not bring up MKA session when acting as non-key server, if the cipher suite advertised by the key server (DUT) is not supported by it. |
| IPsec raw packet template is now added to generate MACsec encrypted IPsec frames. |
| Routing/Switching/MPLS |
| NGPF ISIS emulation now packs multiple sub-TLVs in top-level Extended IS Reachability TLV (type 22/222) upto maximum TLV length for optimal TLV space utilization. |
| NGPF BGP emulation now supports custom configuration of extended communities. |
| NGPF ISIS emulation in performance mode now supports network type "broadcast". |
| RSVP-TE Head End emulation now also accepts RESV message with loopback IP address as source IP. |
| SDN |
| EVPN VXLAN emulation now supports simulated IPv4 hosts behind simulated VTEP. The simulated host can send and respond to ARP, Ping, as well as IGMP messages. |
| Bidirectional Forwarding Detection (BFD) is introduced for SRv6/G-SRv6 OAM. |
| TSN |
| Avnu Silicon AS-2020 test specification is now supported as part of IxNetwork Avnu Conformance Test Library. Support for all 155 test cases are present. All the test cases are fully backward compatible with AS-2011 specification. |
Infrastructure
| Bug Number |
Notes |
| 22629 |
BGP Basic tab does not appear in WebUI when multiple DHCP clients are configured. |
| 22698 |
IxNetwork API Library and IxNetwork API Server versions do not match. |
| 23245 |
Novus 10/1GE4DP load module does not support LAG configuration. |
Routing/Switching/MPLS
| Bug Number |
Notes |
| 22858 |
Port CPUs sometimes become unresponsive on high-scale ISIS configurations with long-duration testing. |
| 22527 |
Port CPU becomes unresponsive if routes configured for an ISIS router cannot be accommodated in 255 LSPs. |
| 22650 |
OSPFv3 emulation advertises wrong route in Update message after lapse of LSA Refresh Time. |
| 22659 |
High Level API for configuring OSPFv3 Area ID returns error. |
| 23147 |
OSPFv3 emulation does not advertise Intra-Area-Prefix-LSA for simulated IPv6 links. |
SDN
| Bug Number |
Notes |
| 22633 |
BGP Link State Learned Information shows zero for TE Reservable BW (Bps) field if the received value is larger than 32 bits. |
| 22652 |
A withdraw message is sent for BGP SR Policy routes when BGP session comes up after a flap. |
| 22828 |
The hop limit field value in the outer IPv6 header of SRv6 BFD echo reply packets is wrongly set to 1. |
| 22932 |
BGP Link State Learned Information for SR Policy shows wrong values for Weight and CP Flags. |
| 23135 |
BGP Flowspec Redirect IP address field is ignored. |
| 23252 |
The custom pattern for Ethernet Segment ID does not work in EVPN VXLAN Wizard. |
| 23399 |
Port becomes unresponsive on fetching BGP-LS SR Policy learned info if the SR policy segment list is empty. |