Ixia Software Release Notes
IxOS 8.20 EA
Build Number: 8.20.1300.14 (December, 2016)
IxOS 8.20 EA is an "Early Adopter" release.
Please see the specific IxOS sections below for application compatibility requirements, known issues and the Product Compatibility Matrix for IxOS hardware support.
Application Compatibility
The following application releases support IxOS 8.20 EA:
Application |
IxOS 8.20 EA |
BPS |
8.20 EA |
FLIX OS |
2016.2.0.32 (XGS2-HS & XGS12-HS) 2016.2.74.31 (XGS2-HSL & XGS12-HSL) |
HLTAPI |
8.20 EA |
IxANVL |
9.10 EA |
IxChariot |
Not Supported |
IxLoad |
8.20 EA |
IxNetwork |
8.20 EA |
IxVM |
8.20 EA |
Licensing |
4.50 EA |
Test Conductor |
3.60 GA |
In addition, current interoperability and compatibility coverage for IxOS
8.20 EA can also be retrieved using the on-line compatibility tool:
http://www.ixiacom.com/support-overview/product-support/product-compatibility-matrix
Ixia Licensing
Any chassis which runs IxServer must have an IxOS license installed on it.
IxOS 8.20 EA ships with Ixia Licensing 4.50 EA.
IxLicensing 4.50 EA upgrades IxLicensing 4.40 EA Patch1 and earlier versions. If this is upgraded on release 3.xx,
Ixia Licensing Utility (ILU) and License Server Plus (LS+) will replace Ixia Registration Utility (IRU)
and License Server (LS).
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 EA upgrades Ixia Licensing 4.40 EA Patch1 and prior versions on the
machines. If the setup is upgraded from versions prior to 4.30 to 4.50,
the setup cannot be reverted to the previous version and will need to stay at 4.50 EA after the upgrade.
This upgrade can be performed in below 2 ways:
- Ixia Registration Utility (IRU) to Ixia Licensing Utility (ILU)
- Previous 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, you can perform the upgrade in the following ways:
- Online Migration
- Offline Migration
Prerequisite Installation Notes
Ixia Licensing 4.50 EA installs .Net 4.0 on Chassis and .Net 4.5.1 on Clients and VM Chassis.
NOTE: Ixia Licensing 4.50 EA 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://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.
Installation on XGS2-HS and XGS12-HS chassis
Starting from IxOS 8.13 EA, the XGS2-HS, XGS12-HS chassis can optionally be converted
to run Native IxOS, for improved stability and performance.
The conversion removes the Microsoft Windows OS, and replaces it with IxOS running natively on the chassis (over Linux OS).
Once complete the chassis are effectively converted to XGS2-HSL and XGS12-HSL.
For more information, including the conversion process procedure, please download and
read the Converting_XGS_and_PSOne_to_Native_IxOS.pdf document available on the IxOS Downloads And Update
(https://support.ixiacom.com/support-overview/product-support/downloads-updates/versions/21)
Installation on PerfectStorm ONE appliance
In order to run IxLoad 8.20 EA, the PerfectStorm ONE appliance must be converted to run Native IxOS.
The new Native IxOS provides for improved stability and performance. The conversion removes the Microsoft Windows OS,
and replaces it with IxOS running natively on the appliance (over Linux OS). For more information, including the conversion process procedure,
please download and read the Converting_XGS_and_PSOne_to_Native_IxOS.pdf document available on the IxOS Downloads And Update
(https://support.ixiacom.com/support-overview/product-support/downloads-updates/versions/21)
Windows Chassis Installation Requirements
When installing IxOS 8.20 EA on a chassis, a minimum of 512MB of installed
RAM and a minimum 2GB of free disk space on Drive C: is required.
In addition, be sure that at least 400MB of temporary space is available.
If your chassis does not meet these requirements, please contact Customer Support
at support@ixiacom.com or 1-877-FOR-IXIA about appropriate upgrades.
On heavily loaded chassis configurations, 1GB of RAM is recommended.
NOTE: Non-English versions of the Windows operating system are not supported.
NOTE: When installing from CD, some virus scanning configurations present
a malicious code alert during execution of the Windows autorun feature. If
this occurs, right-click the CD-ROM drive icon in Explorer and 'Explore'
the CD. At the root of the CD, double-click on the index.htm file.
NOTE: "Untrusted publisher" dialog box appears when installing on Windows 7.
Microsoft has issued a hotfix to resolve this issue. It is included in the IxOS installer
and requires a reboot early in the installation process, if not already installed.
Please refer to the following Microsoft knowledgebase item for more information:
2921916
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.
Server Configuration Options
There are three options offered for configuring IxOS server operations: Service,
Startup, and Manual (None).
1. The Service option creates a Windows service for IxServer which can be
managed via the Windows Service Control Manager. Desktop shortcuts are not
created when using this option. However, Start Menu shortcuts are still
available. The usual IxServer user interface is not available. As a result,
configuration of IxServer (or Tcl Server) requires the user to stop the
services and invoke the server via the Start Menu shortcuts. Once the
configuration is complete, the servers can be closed via the user interface,
and the service restarted.
NOTE: Presently, Telnet connectivity is unavailable when Tcl Server is
configured to run as a service.
2. The Startup option starts IxServer when any user logs on to the chassis.
Start Menu shortcuts are also created.
3. The Manual(None) option simply creates Desktop and Start Menu shortcuts.
IxServer and/or Tcl Server are not automatically started when the user logs
in to the machine or the machine is rebooted.
NOTE: Regardless of the service option selection, Demo Server is always configured
to operate manually.
Tcl Version Option
IxOS is now shipping with Active State Tcl 8.5. When Client is selected for
installation, the user is offered to install Tcl 8.5. If you select Tcl 8.5,
be sure that your Tcl-based applications will run under this version.
NOTE: When using IxOS 8.20 EA, the Tix 8.5 Tcl extension is delivered
with the Tcl 8.5 installation.
NOTE: If the Solaris TCL console doesn't start because it's missing libiconv or libgcc,
follow these steps:
1. extract the archives on the Solaris machine
2. run the commands:
pkgadd -d libgcc-3.3-sol10-sparc-local
pkgadd -d libiconv-1.14-sol10-sparc-local
pkgadd -d libintl-3.4.0-sol10-sparc-local
Operating System Support
Client PC
Windows:
- Windows XP Professional 32-bit SP3
- Windows 2008 Server 64-bit
- Windows 7 Enterprise 32-bit
- Windows 7 Enterprise 64-bit
- Windows 7 Professional 32-bit
- Windows 7 Professional 64-bit
- Windows 7 Ultimate 32-bit
- Windows 2012 Server Standard R2 64-bit
- Windows 8.1 Enterprise 32-bit and 64-bit
- Windows 10 Pro
The support for the following Operating System has been dropped starting with IxOS 8.20 EA;
- Windows Vista Enterprise SP2 32-bit and 64-bit - DROPPED
UNIX:
- Fedora Core 14
- RedHat Enterprise 5.0
Other versions of UNIX platforms may operate properly, but are not officially supported.
VMWare:
- Server 1.0.2
- Server 2.0
Chassis
- Windows XP Professional 32-bit SP3
- Windows 7 Ultimate 32-bit
- CentOS Linux 7 (Core)
NOTE: The following foreign languages are supported on the chassis running the
above Windows versions:
- Chinese (traditional and simplified)
- French
- German
- Hebrew
- Italian
- Japanese
- Spanish
- Swedish
UNIX Installation Notes
In order to run the GUI installer, your client machine must be configured with
an operational X-windows server.
Be sure to set your DISPLAY environment variable to the host name or IP address
of the client machine on which you want the installer GUI to display. Below are
examples for setting the DISPLAY environment variable using various shells. If
you need environment configuration assistance beyond this, please consult your
System Administrator.
// enable connections to X Server
xhost + or xhost [remote hostname]
// set DISPLAY environment variable
// determine shell
echo $SHELL
// depending on what shell you use - Bourne shell (bsh or sh),
// Bash (bash- Bourne shell again), C shell (csh) or Korn shell (ksh);
// set DISPLAY environment variable:
// bash:
export DISPLAY=hostname:0
// bsh or ksh:
DISPLAY=hostname:0
export DISPLAY
// csh:
setenv DISPLAY hostname:0
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, using an install location is a network-mounted
file system, ensure the root user has write permission to the file system.
To install the Tcl Client on Linux, perform the following steps: (Note:
the binary file name 'IxOS8.20.XXX.XXXLinux.bin' is used in the example
below. In most cases, the file name will be different.)
3.1 Copy the 'IxOS8.20.XXX.XXXLinux.bin' file to the system.
3.2 Before starting the installation, make sure the IxOS binary is executable.
If not, type "chmod +x 'filename'" (where 'filename' is the binary file name).
Check the permissions of the target directory to make sure full permission
is granted.
3.3 Execute the IxOS installer file (use the gui option if installing via console
or remote shell).
Example: ./IxOS8.20.XXX.XXXLinux.bin
3.4 When the installer prompts, select Tcl version 8.5.
3.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 "df -ak" command.
There must 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
./IxOS8.20.XXX.XXXLinux.bin
To install IxOS using tgz package, perform the following steps:
3.1 Create the destination folder.
3.2 Extract and copy all folders and files from the tgz package into the destination folder.
3.3 After installation, set the following variables:(Note: Examples below match
the sample installation; they must be altered to match user installation.)
IXIA_HOME=/export/home/ixos8.20
IXIA_VERSION=8.20.XXX.XXX
TCLLIBPATH=/export/home/ixos8.20/lib
3.4 Optionally, specify the following environment variables to specify the
location of the log, sample, 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
3.5 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
Downgrading to a previous version of IxOS
When downgrading to a release of IxOS prior to 5.10 SP2 on a chassis, all Ixia
applications must be un-installed from the chassis and re-installed after the
IxOS downgrade is completed. Please perform the following steps using the
Add/Remove Programs application.
1. Un-install current IxOS installation.
2. Un-install all Ixia applications.
3. Un-install StatEngine and all PCPU packages
4. Install IxOS
5. Install previously un-installed application. Note, these application
installations install StatEngine if required. There is no need to
install this separately.
Note, any card, port, stream, etc., files generated by IxOS are forward
compatible but not backward compatible.
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.
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
|
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 |
|
Asia Pacific Customer Support
|
|
Japan Customer Support
|
Hours: |
09:00 to 17:30 local time (Japan), Business days |
Email: |
support-japan@ixiacom.com |
Phone: |
+81-3-5326-1980 |
Fax: |
+81-3-3348-7733 |
|
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.
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.
Installing / Uninstalling Load Modules
Modules in the XGS12-SD, XGS12-HS, XGS12-HSL, XGS2-SD, XGS2-HS, XGS2-HSL, XG12, XM12, and XM2 can be installed/uninstalled
with the chassis 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.
IxOS 8.20 EA Features
Novus 10GE/1GE/100M Dual-PHY Load Modules |
NOVUS10/1GE16DP, 16-port, SFP+/10GBASE-T Dual-PHY 10GE/1GE/100M load module, 1-slot Dual-PHY with 16-ports each of the SFP+ and 10GBASE-T RJ45 physical interfaces, L2-7 support. Compatible with the XGS12-SD rack mount chassis (940-0011), XGS12-HSL rack mount chassis (940-0016), XGS2-SD 2-slot standard performance chassis (940-0010), and 2-slot high performance XGS2-HSL Chassis (940-0014). |
NOVUS10/1GE8DP, 8-port enablement on the 16-port SFP+/10GBASE-T Dual-PHY 10GE/1GE/100M load module (944-1142), 1-slot Dual-PHY with 8-ports each of the SFP+ and 10GBASE-T RJ45 physical interfaces, L2-7 support. Compatible with the XGS12-SD rack mount chassis (940-0011), XGS12-HSL rack mount chassis (940-0016), XGS2-SD 2-slot standard performance chassis (940-0010), and 2-slot high performance XGS2-HSL Chassis (940-0014). |
NOVUS10/1GE/100M-UPGRADE, additional 8-port enablement for FIELD UPGRADE for NOVUS10/1GE16DP, 8-port enabled load module (944-1143) and 8-port enabled Novus One appliance (941-0061). Note1. This creates a total of 16-ports enabled on the load module or appliance. Note2: For the additional 8-port upgrade purchase please provide the serial number of the desired load module or appliance to install the option on at the time of order placement. |
Novus 1GE/100M Dual-PHY Load Modules |
NOVUS1GE16DP, 16-port 1GE/100M SFP+/1000BASE-T Dual-PHY load module. 1-slot Dual-PHY with 16-ports each of the SFP+ and 1000BASE-T RJ45 physical interfaces, L2-7 support. Compatible with the XGS12-SD rack mount chassis (940-0011), XGS12-HSL rack mount chassis (940-0016), XGS2-SD 2-slot standard performance chassis (940-0010), and 2-slot high performance XGS2-HSL Chassis (940-0014). Note. This is the NOVUS10/1GE16DP, 16-port load module (944-1142) enabled for ONLY 1GE/100Mbps operation on all 16-ports. |
Novus ONE 10GE/1GE/100M Appliance |
Novus ONE 10/1GE16DP Appliance (NOVUS10/1GE16DP), 16-port, SFP+/10GBASE-T Dual-PHY 10GE/1GE/100M Appliance, 1-slot Dual-PHY with 16-ports each of the SFP+ and 10GBASE-T RJ45 physical interfaces. L2-7 support. |
Novus ONE 10/1GE16DP Appliance (NOVUS10/1GE8DP), 8-port, SFP+/10GBASE-T Dual-PHY 10GE/1GE/100M Appliance, 1-slot Dual-PHY with 8-ports each of the SFP+ and 10GBASE-T RJ45 physical interfaces. L2-7 support. |
VM |
Support for Web UI for the Virtual Chassis has been added. This new graphical interface greatly simplifies the Virtual Chassis management operations, and is designed to replace Chassis Builder. |
Support for VMware Perl SDK API has been added. This enables automated deployment and initial provisioning in VMware vCenter environments. |
Support for VLAN tagging on SR-IOV interfaces has been added. Users can now exchange VLAN tagged frames on vPorts connected via SR-IOV. Available in IxNetwork and IxLoad, no IxExplorer support. |
Support for secure CLI access to the Virtual Load Module has been enhanced. The root account has been restricted, and a new ixia account has been added. |
Support for new Compatible environments has been added. Ixia NTS VE products are known to be working with VMware vCenter 5.x / 6.x, KVM over Ubuntu 16.04 LTS and OpenStack Newton. |
Support for Windows Virtual Chassis has been discontinued starting with this release. Customers who want to upgrade to new releases can use the Linux Virtual Chassis at no additional cost. |
XGS12-HSL and XGS2-HSL Chassis |
The 944-0083 Xcellon-Ultra NP-01, Application Network Processor Load Module, 1-10G or 12-Port Dual-PHY (RJ45 and SFP) 10/100/1000 Mbps is now supported on the XGS12-HSL 12-SLOT High Speed Chassis BUNDLE (940-0016) and the XGS2-HSL 2-SLOT High Speed Chassis BUNDLE (940-0014). |
The 944-1060 Xcellon FlexAP10G16S 10 Gigabit Ethernet LAN Load Module, L2-7 Accelerated Performance, a 1-slot module with 16-ports of SFP+ interfaces, and the 944-1061 the Xcellon FlexFE10G16S 10 Gigabit Ethernet LAN Load Module, L2-3 Full Emulation Performance, a 1-slot module with 16-ports of SFP+ interfaces are now supported on the XGS12-HSL 12-SLOT High Speed Chassis BUNDLE (940-0016) and the XGS2-HSL 2-SLOT High Speed Chassis BUNDLE (940-0014). |
Chassis Management Console
Bug Number |
Notes |
1413529 |
Web user interface displays approx ~400 latest entries only from the IxServer log. To get more information please download the log file from UI or use Ixia CLI"show log ixServer --latest".
|
1424577 |
When accessing Web UI for the very first time from Safari Browser, users might notice that not all the UI elements are loaded. In that case please follow the instructions from this link: http://blog.marcon.me/post/24874118286/secure-websockets-safari to troubleshoot.
|
1424735 |
Resource Groups are not correctly displayed for PerfectStorm cards in Web User Interface.
|
Miscellaneous
Bug Number |
Notes |
1404716 |
Sometimes when on the same chassis large number of ports are used by other application (like IxNetwork) control of the ports owned by BPS may be lost.
|
NOVUS100GE8Q28+FAN
Bug Number |
Notes |
1389289 |
On some occasions after restarting IxServer port links will come up but IxExplorer will display port links as down. Pressing refresh (F5) in IxExplorer corrects the displayed state.
|
1406987 |
Each PCPU port is rate-limited to 2.5Gbps for fair sharing.
|
1411818 |
Currently there is no message to block the user from performing operations when the card is performing mode switch(for example from 100 to 25G)
|
Novus One
Bug Number |
Notes |
1425964 |
Under rare cases during a IxServer restart and/or Novus Mode switch TEC Communication Failure may occur. Server restart and/or Novus-ONE Cold boot may be required
|
Novus10/1GE16DP
Bug Number |
Notes |
1411035 |
Captured packets not correct when Trigger Position = 0%, 100%
|
1415793 |
Novus 10G support auto-detect between 1G and 10G, which no other Ixia product offers. As a result, we can't differentiate between port mode as 1G or 10G, as this my change dynamically. So, we will leave this as type 1 (kFramingEthernet) which is generic, and does not state specifically 10G or 1G (or 100M).
|
1417209 |
This Load Module does not support rxEqualizerControlValue parameter in TapSettings.
|
1423697 |
Bit Offset feature is not supported on Novus10/1GE Load modules.
|
1424834 |
Port link may remain up if an SFP port is configured for 100 Mbit but does not have the correct SGMII 100Base-FX transceiver and is connected to another 1G port.
|
1425285 |
When internal loopback is configured at 100M in SFP+ mode, L1 link will not come up. Workaround: Change configuration to 1G/10G SFP+ or 100M/1G/10G RJ45 to use Internal Loopback.
|
1425966 |
Rx Active Status LED blinks green rather than red when receiving errors.
|
1427159 |
If PFC has traffic running with max frame size of more than 5000 bytes Q0 on all queues and is paused, it is possible to encounter a condition where FCS and Sequence errors occur.
|
1427547 |
When running with no cable connected, or during mode change the Novus port may report a hardware fault in the IxServer log with an error message of "PacketLengthErr", "RxFaultFilterFramingError" or "RxPktFifoEmptyFault". These messages indicate that the port received invalid data. They do not indicate a physical hardware failure. After the errors are reported, the port can be used as normal once the link has been re-established.
|
VM
Bug Number |
Notes |
1403719 |
Remove old logs from IxNetwork with a Linux chassis does not work. Workaround : use chassis CLI cleanupdiskspace command.
|
1416447 |
Intel X550 SR-IOV driver is not supported by Ixia Virtual Load Modules.
|
1425710 |
The following message might appear in IxServer logs when using Virtual Chassis: "FAIL Release License timeout.". Please note there is no functional impact.
|
XGS12-HS / XGS2-HS
Bug Number |
Notes |
1408098 |
IxServer reboot is required after changing management IP address from IxExplorer.
|
XGS12-HSL / XGS2-HSL Chassis
Bug Number |
Notes |
1427115 |
On a Native IxOS chassis shipped with gold image (8.13 EA), when upgrading IxOS to 8.20 EA and switching IxOS back to 8.13 EA, IxServer sometimes does not come up.
Workaround is to reboot the chassis.
|
1427225 |
On a Native Chassis, when switching from CLI the active IxOS version from 8.13 EA to 8.20 EA or newer releases , you must exit CLI manually and re-login to use the latest CLI version. Failing to do so may result in unpredictable CLI behavior.
|
Miscellaneous
Bug Number |
Notes |
1406064 |
All the IGMP packets now have correct MAC addresses.
|
1421514 |
UDF1 chain is now getting chained to UDF5 correctly.
|
NOVUS100GE8Q28+FAN
Bug Number |
Notes |
1408989 |
Port link up operation is independent for all 4 ports in 4x25G mode for Fiber cable.
|
1410336 |
After changing Novus 25G ports to disable FEC, LT and AN, there should be no CRC error
|
1420541 |
IxNet release port is followed by IxExp change mode is working fine now
|
VM
Bug Number |
Notes |
1426066 |
Fixed an IxServer crash observed while multiple users are deleting same VM cards in paralel from API scripts.
|
XM100GE4QSFP28+ENH
Bug Number |
Notes |
1416574 |
Time to fetch statistics when DUT is rebooting in now within acceptable range.
|