Ixia Software Release Notes
IxOS 9.00
Build Number: 9.00.1900.10 (July 17, 2019)



About This Release

Welcome to IxOS 9.00 Release. All IxOS features and bug-fixes introduced in interim releases since IxOS 8.50 EA have been consolidated into this release.
Please see sections below for application and hardware compatibility, new features, resolved issues, and known issues.

Application Compatibility

The following application releases support IxOS 9.00:
Application IxOS 9.00
BPS 9.00
HLTAPI 9.00
IxANVL Not Supported
IxChariot Not Supported
IxLoad 9.00
IxNetwork 9.00
IxVM 9.00
Licensing 5.20
Metronome 2.1
Wireshark 1.8
In addition, current interoperability and compatibility coverage for IxOS 9.00 can also be retrieved using the on-line compatibility tool. Please contact Ixia for details.

Licensing

Ixia Licensing

Any chassis which runs IxServer must have an IxOS license installed on it. IxOS 9.00 ships with Ixia Licensing 5.20, which is installed automatically along with IxOS Installation. Some of the key benefits of this new licensing system are: - Reduced the number of licensing services from 4 to 1 (Ixia nodedv3). - The list of TCP ports required for external connections has been reduced, specifically TCP port 4502 is no longer required. - Improved performance and memory usage.

Installing a License

Ixia Licensing 5.20 upgrades Ixia Licensing 5.10 EA and prior versions. Once upgraded, Ixia Licensing cannot be downgraded to previous versions. The upgrade will proceed in either of following two ways: - Ixia Registration Utility (IRU) will be replaced by Ixia Licensing Utility (ILU) if upgrade is performed on 3.xx release. Registration Numbers in IRU will be migrated as activation codes in ILU. - Previous version of Ixia Licensing Utility (ILU) will be upgraded to latest version of Ixia Licensing Utility (ILU). The upgrade will also attempt to migrate existing licenses to latest version of ILU. If your system is connected to the Internet, this migration will be transparent. Otherwise, you will be prompted to follow an "Offline Migration" method. For more information about the IxLicensing system, please refer to the "Ixia Licensing Management User Guide" provided with the Ixia software, or downloadable from the Ixia web site.

Installation Notes

Installation on XGS2-SD and XGS12-SD chassis

Starting from IxOS 8.40 EA, the XGS2-SD and XGS12-SD chassis can optionally be converted to run Native IxOS, for improved stability and performance. The conversion removes the Microsoft Windows Operating System, and replaces it with IxOS running natively on the chassis. Once complete the chassis are effectively converted to XGS2-SDL and XGS12-SDL. For more information, including the conversion process procedure, please read the Converting_XGS_SD_to_Native_IxOS.pdf document available on IxOS Downloads And Update page. Starting from IxOS 9.00, XGS2-SD and XGS12-SD chassis can optionally be converted to run Windows 10 Pro 64-bit, to continue receiving latest security and stability updates from Microsoft. For more information, including the conversion process, please read the PENDING DOC AND LINK UPDATE.

Installation on PSOne, XGS2-HS and XGS12-HS chassis

Starting from IxOS 9.00, IxOS installation is no longer supported on the PSOne, XGS2-HS and XGS12-HS chassis with Windows OS. To install IxOS and compatible Ixia Applications on these platforms, the management operating system must first be converted to Native IxOS 8.50 EA. The conversion procedure is described in Converting_XGS_and_PSOne_to_Native_IxOS.pdf, which can be downloaded from IxOS 8.50 EA Downloads And Update page.

Installation Requirements On Windows

IxOS 9.00 installation requires 13 GB of free space on chassis' system drive and 5.5 GB of free space on client's system drive. IxExplorer 9.00 installation requires 2.5 GB of free space on client's system drive. A minimum of 1GB RAM is recommended on chassis and client. 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 CD, some virus scanning configurations present a malicious code alert during execution of the Windows auto-run feature. If this occurs, please double click open the index.htm file present inside CD-ROM drive. - IxOS installer automatically installs a Microsoft Hotfix 2921916 (if not already installed) for an issue due to which "Untrusted publisher" dialog would appear when installing IxOS on Windows 7.

Operating System Support

Windows Client PC: - Windows 2008 Server 64-bit - Windows 7 Enterprise 32-bit (Build 7601) - Windows 7 Professional 32-bit (Build 7601) - Windows 7 Professional 64-bit (Build 7601) - Windows 7 Ultimate 32-bit (Build 7601) - Windows 2012 Server Standard R2 64-bit - Windows 8.1 Enterprise 32-bit and 64-bit (Build 9600) - Windows 10 Pro 64-bit (Build 1903) The following versions of Windows operating systems are no longer supported on the client: - Windows Vista Enterprise SP2 32-bit and 64-bit - starting with IxOS 8.21 EA - Windows XP Professional 32-bit SP3 - starting with IxOS 8.30 EA UNIX Client PC: - Fedora Core 14.0 and above - RedHat Enterprise 5.0 and above - Centos 6.0 and above - Ubuntu 16.0 and above Other versions of UNIX platforms may operate properly, but are not officially supported. VMware - Server 1.0.2 - Server 2.0 Windows Chassis - Windows 10 Pro 64-bit (Build 1903) - Windows 7 Ultimate 32-bit NOTE: IxOS is no longer supported on a Windows XP Professional Chassis, starting with IxOS 9.00. Languages supported are English, Chinese (traditional and simplified), French, German Hebrew, Italian, Japanese, Spanish and Swedish.

Installation Features

The IxOS installation program offers the user a selection of five installation options: Client, Server, Demo Server, Tcl Server, and Hardware Manager. The Server option is normally chosen for installation on Ixia chassis. The Demo Server option should NOT be chosen for chassis installations: it is used for client installations.

IxServer on Windows Chassis

Starting from IxOS 9.00, IxServer will boot up in High Performance Mode by default on Windows Chassis. Besides significantly improving performance in multi user test bed, this also enables chassis chain capability between a Native IxOS and Windows Chassis. High Performance Mode has always been a default on Native IxOS Chassis. NOTE: - Load Modules that are End-Of-Development starting from IxOS 9.00 are not supported in High Performance Mode, a detailed list of which can be found at on-line compatibility tool. - To use these load modules, High Performance Mode can be disabled from IxServer Options to boot in Legacy Mode, next time it is restarted. Startup Configuration Options There are three options offered for configuring IxOS server startup: 1. Service: A Windows Service for IxServer (or TCL Server) will be created which can be started/stopped from Windows Service Control Manager. Desktop Shortcuts and IxServer User Interface are not available. Any configuration of IxServer or TCL Server requires user to stop the service, manually invoke server from Start Menu shortcuts, close the server and restart service. 2. Startup: IxServer starts when user logs on to the chassis or when it is rebooted. 3. Manual: IxServer or TCL Server can only be started or stopped manually from Desktop or Start Menu shortcuts. NOTE: - Telnet connectivity is unavailable when TCL Server is configured to run as a service. - Demo Server is configured to operate manually even if service option is selected.

Tcl Version Option

IxOS 9.00 is shipping with Tcl 8.5 and 8.6. Both of them will be installed and the option of using either of the version can be set for usage as follows: 1. On Windows Chassis, open TCL Server and select appropriate TCL version from options. 2. On Windows Client, select appropriate TCL version from Desktop or Start Menu shortcut. 3. On Native IxOS Chassis, login to IxOS CLI using SSH and execute: set tcl active-version 8.x 4. On Unix Client, execute a script inside installed directory: ./bin/set_tcl_active_version.sh 8.x

Chassis Management Console

Chassis Management Console (CMC) is a web application that provides access to Ixia Native IxOS Chassis and its components (i.e. load modules and ports) and enables users to control and monitor the chassis by means of any client computer connected to it. CMC is supported on following browsers:
Application Version
Google Chrome 75 or newer
Mozilla Firefox 67 or newer
Microsoft Edge 38 or newer
Apple Safari 12.1.1 or newer

UNIX Client Installation Notes

Using .bin Installer: This installs packages for IxOS TCL API and Ixia TCL Interpreter. If you are updating an existing installation, be sure to run the installer as the same user who initially installed the software. Always run the uninstaller prior to removing any files manually. If installing as the root user and install location is a network-mounted file system, ensure the root user has write permission to the file system. To proceed with installation, perform following steps (Note: the binary file name 'IxOS9.00.XXX.XXXLinux.bin' is used in the example below. In most cases, the file name will be different): 1. Copy the IxOS9.00.XXX.XXXLinux.bin file to the system. 2. Make the binary executable if it is not already: chmod +x ./IxOS9.00.XXX.XXXLinux.bin Also, make sure target installation directory has full permissions granted. 3. Execute the IxOS installer file: ./IxOS9.00.XXX.XXXLinux.bin 4. When the installer prompts, select appropriate Tcl version (e.g. 8.5 or 8.6) 5. Follow the installation prompts to complete the installation. If the installation fails, check that there is enough disk space on the system by using the command: df -ak There must be enough space in the /tmp folder (to extract the files), and in the target folder (where files are to be installed). If the /tmp dir does not have enough space, specify the dir by setting IATEMPDIR environment with path to the folder where you have enough free space. The following example show the use of the options: export IATEMPDIR=/tempdir ./IxOS9.00.XXX.XXXLinux.bin Using .tar.gz: This installs packages for IxOS TCL API only. To install, perform the following steps: 1. Create a destination folder and extract contents of .tar.gz file into it. e.g. /export/home/ixos9.00 2. After extraction, set the following variables (please replace sample path with original path): IXIA_HOME=/export/home/ixos9.00 IXIA_VERSION=9.00.XXX.XXX TCLLIBPATH=/export/home/ixos9.00/lib 3. Optionally, specify the following environment variables to specify the location of logs, samples and results files for IxOS: IXIA_LOGS_DIR=$IXIA_HOME/logs IXIA_RESULTS_DIR=$IXIA_HOME/results IXIA_SAMPLES=$IXIA_HOME/samples IXIA_TCL_DIR=$IXIA_HOME/lib 4. If the Tcl option was installed with an IxOS installation, add Ixia's bin and lib directory to the PATH and LD_LIBRARY_PATH variable in order to use it. For example: IxiaLibPath=$IXIA_HOME/lib IxiaBinPath=$IXIA_HOME/bin PATH=$IxiaBinPath:$PATH LD_LIBRARY_PATH=$IxiaLibPath:$LD_LIBRARY_PATH

Multiple IxOS versions

Multiple IxOS versions can co-exist on an Ixia Chassis or client. Installing another IxOS version does not affect the existing versions. On Windows Chassis, to set active IxOS version, users are required to close any running instance of IxServer or TCL Server and start the intended IxServer version from Start Menu or Desktop Shortcuts. On Native IxOS Chassis, users can login to IxOS CLI via SSH and set active IxOS version using the command: set ixos active-version 8.x.x.x NOTE: Any card, port, stream, etc., files generated by IxOS are forward compatible but not backward compatible.

Tcl/Tk Support for Client Applications

Tcl Server was first supplied free of charge starting with IxOS 3.80 EA. 
Installation of this feature is optional; it should only be installed if 
required for specific application.
 
Installation and operation of the Tcl Server is required for IxChariot when 
running hardware performance pairs, for IxANVL when running VNIC (Virtual 
Network Interface Card) and for IxAuthenticate. The Tcl Server can be installed 
on either the Ixia chassis or a separate Windows workstation. 

The following limitations exist with respect to Wish and Tcl shell support:

   Tcl shell does not run on any version of Windows with Ixia software. Under
   Linux or Solaris, the Tcl shell runs on any version of Tcl greater than or 
   equal to 8.3.

How to Report Problems

Ixia Headquarters

+1 877 367 4942 - Toll-free North America
+1 818 871 1800 - Outside North America
+1.818.871.1805 - Fax
www.ixiacom.com/contact/info

Support

Global Support +1 818 595 2599

support@ixiacom.com

APAC Support +91 80 4939 6410

support@ixiacom.com

Australia +61-742434942

support@ixiacom.com

EMEA Support +40 21 301 5699

support-emea@ixiacom.com

Greater China Region

+400 898 0598

support-china@ixiacom.com

Hong Kong +852-30084465

support@ixiacom.com

India Office +91 80 4939 6410

support-india@ixiacom.com

Japan Head Office +81 3 5326 1980

support-japan@ixiacom.com

Korea Office +82 2 3461 0095

support-korea@ixiacom.com

Singapore Office +65-6215-7700

support@ixiacom.com

Taiwan (local toll-free number) 00801856991

support@ixiacom.com


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 support@ixiacom.com.

Field Notices

Laser Warnings

The 10G load modules may use a Class III laser. Precautions should be taken to prevent personal injury. The spring-loaded safety cover should always be securely in place over the port when there is no cable installed. Avoid exposure and never look directly into an open port aperture.

Inserting / Removing Load Modules

Modules in the XGS12-SD, XGS12-HSL, XGS12-SDL, XGS2-SD, XGS2-HSL, XGS2-SDL, XG12, XM12, and XM2 can be inserted/removed while the chassis is still operational. For all chassis types, use caution when inserting or removing multi-slot modules to evenly insert and remove. Load modules are tightly spaced; avoid contacting the adjoining modules while inserting and removing.

Safety Notice Regarding Ixia Load Modules

WARNING: In order to prevent accidental injury to personnel, do not leave transceiver (SFP/SFP+/QSFP/QSFP28/CXP/CFP4) cages uncovered on Ixia load modules. When transceivers are not installed, port end caps (Part No. 503-006) must be used. The metal edge of the transceiver cage is SHARP. To avoid injury, ALWAYS keep the transceiver cage covered. Contact Ixia Technical Support to obtain end caps. Please reference Ixia Product safety notice Part No. 913-0715 Rev A, June 2009. For additional information refer to Chapter three of the IXOS Getting Started Guide under the section, Notes, Cautions and Warnings.

Use Ejector Tabs Properly

Ejector tabs on load modules are to be used only to eject a load module from the chassis backplane connector. They are not designed to support the weight of the load module. Ejector tabs can bend or break if used improperly as handles to push, pull, or carry a load module.

What's New in IxOS

IxOS 9.00 Features

AresONE
The AN/LT or LT status is now displayed in realtime in IxExplorer's port properties, as well as the AN success/failure of the advertised capabilities of the link partners

IxOS
IxOS and the compatible Ixia applications are now supported on Windows 10 Pro 64-bit XGS2-SD and XGS12-SD Chassis. These Chassis can now be officially converted from Windows 7 Ultimate 32-bit to Windows 10 Pro 64-bit by purchasing 943-0014 IXIA IXOS AND WINDOWS 10 FIELD UPGRADE for XGS products 940-0010, 940-0011 and 940-0110.
Ixia Native IxOS Chassis now supports Secure File Transfer Protocol (SFTP) access for API operations requiring file transfer, uploading offline IxOS update package, and downloading chassis diagnostics.
Ixia Native IxOS Hardware Chassis and Fixed Form Chassis can now be configured with static or dynamic IPv6 management address, enabling compatible Ixia Applications to function in IPv4-only, IPv6-only and Dual IPv4/IPv6 network.
Ixia Native IxOS Hardware Chassis and Fixed Form Chassis now support automated IxOS upgrade across multiple systems connected (or not connected) in chain from Chassis Management Console (CMC).
IxExplorer now supports Ixia Wireshark for viewing and analyzing captured packets, when Iatter is installed separately on the same system.
IxServer will now boot up in High Performance Mode by default on Windows Chassis, offering significant performance improvements over Legacy Mode and enabling chassis chain capability between Native IxOS and Windows chassis. Since end-of-development load modules are not supported in High Performance Mode, it can be disabled from IxServer Options to boot IxServer in Legacy Mode next time it is restarted.

PS-ONE
941-0057 IXIA PerfectStorm Starter Kit, 10 GigE 8-port SFP+ appliance (PS10GE8QT)
905-2041 Ixia Field Hardware Upgrade from 941-0057 (PS10G8QT) to 941-0027 (PS10GE8NG)

Time Sensitive Networking (TSN)
When frame preemption is enabled on a port, it will now have the capability to automatically respond with SMD-R packet upon receiving a valid SMD-V request from frame preemption capable link partner.

VM
New DPDK-traffic engine significantly boosts small frame performance and delivers line rate 10 Gbps using 128-bytes frames and line rate 40 Gbps using 1024-bytes frames
Option to deploy the Virtual Test Appliance from Amazon’s AWS Marketplace. Includes support for C4 and C5 instance types
NTP Server Settings on Virtual Chassis and Virtual Test Appliance has been enhanced to allow adding / removing multiple NTP Servers, querying a specified NTP Server and verifying status of existing NTP Servers.


Known Issues List

AresONE

Bug Number Notes
1512740 Upon port initialization, non-zero statistics may be seen for FEC Transcoding Uncorrectable Events even when there are no FEC Uncorrectable Codewords. Please clear the stats once link is up.
1515864 When a transceiver having a saved custom profile is re-plugged with the IxExplorer Port Properties dialog open, the displayed equalization parameters might not get properly refreshed unless the dialog is closed and reopened.
1515879 In 400GE mode, an Auto-Negotiation re-start may occasionally take around 60s to complete.
1517714 AresONE field upgrades cannot be applied using IxOS 9.00 EA, and IxServer will report an EepromBlockWrite failure if attempted. As a workaround, field upgrades may be applied by running IxOS 8.52. Once upgrades are applied with 8.52, they will work as expected with 9.00. This issue will be fixed with IxOS 9.00 Patch 1.

CLI

Bug Number Notes
1503149 Setting Proxy using IPv6 address succeeds but prints error messages.

Chassis Management Console

Bug Number Notes
1511596 Discovery operations are only supported on Native IxOS Hardware Chassis and Fixed Form Chassis.
1512980 Discovery Operation may not work correctly when chassis is only configured with IPv6 address.
1513507 Refreshing systems may fail when a blocking operation is already in progress
1513558 IxOS Installation is not supported from Microsoft Edge and Internet Explorer.

Cloud Storm

Bug Number Notes
1496783 In rare occasions, running arbitrary IxLoad test cases might result in hardware fault, which can be recovered by performing hotswap operation on the affected card.

Installation

Bug Number Notes
1514991 Under certain remote desktop connections the windows 10 search bar may not populate best match entries. workaround will be to restart explorer.exe
1516216 On Windows 7, due to a Microsoft bug, the conversion script cannot be extracted successfully with Microsoft native utility. More information here : https://answers.microsoft.com/en-us/windows/forum/all/windows-extracts-a-3gb-file-to-734-million-gb/8194bc2a-b19b-4e33-ae8e-ed4a293092e9 Please extract the .zip file on Windows 10 or use a 3rdparty tool.
1516609 When switching IxOS versions, IxServer may intermittently display PCIC errors after startup. IxServer can be restarted to clear these errors.
1517255 Installation of IxOS 8.20 EA, 8.20 EA-Patch-1 and 8.20 GA on 9.00 version fails. The workaround is to do a factory image restore (if the factory installed version is earlier than 9.00) and then install 8.20 GA.

IxExplorer

Bug Number Notes
1502243 Opening capture view on a port with ongoing capture operation will effectively stop the capture operation.
1513337 IxExplorer does support importing captures saved from Wireshark in Microsoft NetMon .cap format.

IxTCL

Bug Number Notes
1501914 IxOS TCL APIs requiring file transfer with chassis (e.g. configuration export / import) may fail to execute if TCL interpreter in use is not the one provided by Ixia.

K400

Bug Number Notes
1501037 A chassis refresh operation must be performed after IxServer re-start or transceiver insertion in order to correctly display the transceiver tap settings on IxExplorer.
1509911 In 100GE mode, the port sends alignment markers formatted for four-lane PMD's (such as 100GBASE-CR4) instead of the two-lane PMD's described in 802.3cd Clause 91.5.2.6 (100GBASE-CR2/SR2.).
1516085 Performing many link flaps in the K400 CFP8 card may result in the receiver flagging PCS Illegal Idles and PCS Code Errors. To go back to normal operation, the card should be reset or hot-swapped.

Novus ONE PLUS 10/5/2.5/1/100M Fixed Chassis

Bug Number Notes
1512288 For a rare case, in chassis chain scenario where Novus ONE PLUS is connected to NOVUS10/5/2.5/1/100M16DP in a XGS chassis, CRC errors are seen for the first few frames after link flap.

NovusOne

Bug Number Notes
1486858 Novus ONE may intermittently (less than 1%) fail while switching between Aggregate to Non-Aggregate mode. Restarting IxServer would fix the issue.

VM

Bug Number Notes
1480554 Support for Sequence Errors, Asynchronous Frames Sent, Port CPU Frames Sent on Virtual Ports is not available.
1496448 In Public Cloud, password authentication on Virtual Test Appliance is not supported. Please use the private key file selected when launching the instance.
1501104 PGID Statistics View is not populated with expected PGIDs when running streams with Split PGID configuration.
1501111 PGID 255 tracked by IPv6 traffic class max value will not be displayed sometimes in the PGID Statistics Views.
1505321 Virtual Test Appliance releases 8.30EA and 8.40EA should not be used as NTP servers for time synchronization starting from this release.
1508429 Inter Burst Gap (IBG) is not correctly set in continuous burst mode when using the new DPDK Traffic Engine.
1510195 Making changes to frame rate and frame size and performing suspend operation and pause operation on the fly (when traffic is in progress) is not supported when using the new DPDK Traffic Engine.
1510440 L2-3 traffic rates can have minor variations when using the new DPDK Traffic Engine.
1512121 Advance Sequence Checking feature is not supported on the new DPDK Traffic Engine.
1512239 IxExplorer crashes when changing the rate on the fly from the Gap/Rate Control tab.
1512250 Chained UDFs feature is not supported on the new DPDK Traffic Engine.
1513659 IPv4, UDP and TCP Checksum Error stats do not increment upon occurrence of actual checksum errors when using the new Traffic Engine .
1514036 Per PGID Checksum statistics are not supported on the new DPDK Traffic Engine.
1514958 VM deployed on ESXi 6.7U2, which uses i40en VMware driver instead of i40e, does not function correctly unless it is disabled using command "esxcli software vib remove -n i40en" and rebooted.
1515703 Activating licenses on Windows machines running is AWS is not supported in this release. Please use a Virtual Test Appliance as a license server.
1516417 While using the new DPDK Traffic Engine, modifying trust properties on a VF on the hypervisor requires a Virtual Load Module reboot in order for the settings to be applied.
1516810 CPUs codenames older than Westmere are not supported on the new DPDK Traffic Engine.
1516815 Data Center protocols are not supported on top of SR-IOV configured Virtual Load Modules.
1517519 On Intel X550 boards communication between NIC ports may not work if we use DPDK VF based on kernel PF. The reason is kernel PF enables a new feature "malicious driver detection". Workaround on KVM based hypervisors is to disable MDD by running insmod ixgbe.ko MDD=0,0. On VMware hypervisors you will need to follow these steps: esxcfg-module --set-options "max_vfs=2,2 MDD=0,0" ixgbe and then reboot host.

Wireshark

Bug Number Notes
1503886 Opening PRBS Capture View is not supported.
1515768 IxExplorer needs to be restarted after installing Ixia Wireshark in order to use latter as a external analyzer.


Resolved Defects List

AresONE

Bug Number Notes
1507776 200G AN/LT occasionally times out before completing. To resolve issue, have reduced transition time between completing AN and starting LT for 400G and 200G.
1508537 In BERT mode, the TCL command "bert config -enableInvertTxPattern" does not invert the current pattern. The corresponding inverted pattern needs to be specified instead via 'bert -config txPatternIndex'.
1508560 OSFP transceivers that require Hardware Init are not supported. The CMIS v3.0 Software Init sequence must be used.
1508562 In BERT mode, the TCL command "bert config -enableInvertRxPattern" does not invert the current pattern. The corresponding inverted pattern needs to be specified instead via 'bert -config rxPatternIndex'.
1509361 Ports proceed with Link Training even though there is a mismatch in Auto-negotiation capabilities.
1509678 Link is not established successfully when AresONE 100G port is connected to DUT using CR2 instead of CR4 alignment markers. To address the issue, a UI and API selection was added to choose either CR2 or CR4 markers. (See IEEE 802.3cd clause 91.5.2.6)
1510039 400G/200G Port links stuck down after many AN/LT cycles.
1510891 In 400GE and 200GE Auto-Negotiation or Link Training port modes, a link-up may result in a PCS lane exhibiting a high bit error rate. Condition will be cleared by performing a link flap.
1511930 Could not read optical transceiver management registers in upper pages via TCL until after pages were read in IxExplorer.

CS100GE2Q28

Bug Number Notes
1506737 QSFP+-PLR4 transceiver shows failure for 40G in IxServer.

FlexAP10/40G

Bug Number Notes
1511801 When applying specific PTP Config on10G speed, PCPU crash happened.

FlexFE10G16S

Bug Number Notes
1506533 Multiple port failures are seen in IxServer log and crash dump is generated while running tests.

K400

Bug Number Notes
1498644 Loopback test running for 44 hours causes packet loss

Miscellaneous

Bug Number Notes
1491825 Lava - CFP to Dual QSFP 40G link down after a day of usage.
1503246 Adding or deleting a DNS Server does not take effect unless CLI session is restarted.
1509786 Executing "package require ftp" fails after tel-netting to Ixia TCL Server
1511938 Capture mode checkbox is not getting enabled for XMVDC ports.
1512102 PTP path delay statistics are always zero on XM8S 10GE ports
1515423 Traffic stops while clearing statistics

NOVUS10/5/2.5/1/100M16DP

Bug Number Notes
1498228 Hardware Fault is seen for some PFC test case.
1511811 Extra link toggling occurs in 1G/100M to 2.5G/5G mode switch.
1513018 During Auto-Negotiation process, a "Downshift" occurs if the highest speed fails multiple (5-6) times on a device which supports two or more speeds. The next time, the PHY does not advertise the highest (failing) speed.

NOVUS100GE8Q28+FAN

Bug Number Notes
1497895 Sequence packets are not detected when issuing clear timestamp operation with TxRxSync running on the ports
1499125 25GbE mode fails to link up when autonegotiation is used while connected to Intel DUT
1505995 IxServer response time for some tcl commands (like: port write , stat get) is increased by a huge value when 4 or more load modules are used to run the tests.
1506226 DHCP checksum is incorrect on configuring DHCP UDP IP encapsulation

VM

Bug Number Notes
1480120 Fixed an issue where the CLI commands used on the Virtual Chassis / Virtual Test Appliance did not display enough information for troubleshooting erroneous scenarios. The show journal [service] command can now be used to display additional information regarding service errors.
1485490 Fixed an issue where the [set hostname] / [show hostname] commands were missing from the CLI on the Virtual Load Module.
1488050 Fixed an issue that caused raw tagged traffic to be dropped when using PCI-PT with promiscuous mode enabled.