Ixia Software Release Notes
IxChariot Release 6.60 EA
June 2008
IxChariot 6.60 EA is an "early adopter" release. This version of the product
is now compatible with the Microsoft Windows Vista operating system.
Please read the Installation Notes below for some important information on
upgrading to IxChariot 6.60 EA from previous versions.
Ixia Application Compatibility
IxChariot 6.60 EA requires IxOS 5.00 GA or IxOS 5.10 SP5 (minimum) and
is compatible with the following Ixia application releases:
- IxOS 5.0 GA and IxOS 5.10 EA SP5
- IxAuthenticate 2.00 GA SP2 and SP2 Patch1
- IxVPN 3.00 GA SP1 Patch6 and SP2
- Test Conductor 1.10 GA P2
- IxLoad 3.30 EA SP3 and 4.0 EA SP1
- IxNetwork 5.30 EA SP1 Patch2 and SP2
- IxANVL 7.40 EA SP1 and SP2
- IxProfile 1.15 GA
- IxAutomate 6.30 GA and 6.40 EA
- IxAccess 2.30 GA SP3 Patch 1 and 2.40 EA
- Licensing 2.60 GA
For additional product compatibility information please refer to the following
online utility. An Ixia website account is required before accessing.
http://www.ixiacom.com/support/product_compatibility_matrix
Ixia Licensing
IxChariot utilizes Ixia Licensing 2.60.
Upgrades from Previous Versions of IxChariot
Please use a machine that is within specifications given in the documentation
for the console.
Please remember that the Ixia floating license server should not be co-located
with the IxChariot console.
General Installation Instructions
NOTE: The user is required to have administrator privileges on the machine on
which he or she is attempting to install or operate IxChariot.
If you have an engineering build (EB) of IxChariot or one of its components, you
must de-install it before installing IxChariot 6.60 EA.
NOTE: Running or installing the IxChariot console on an Ixia chassis is not
recommended and may cause interoperability issues with other Ixia
applications using common application components.
Terminal Services - Before installation
To install on a Win2K / Win2K3 Server with Terminal Services the following
command should be entered in a command window: 'change user /install'.
To return the setting back to the default, the user executes the following
command in a command window: 'change user /execute'.
Former NetIQ Chariot Customers - After Installation
Please note that the installation creates an "IxChariot" Program folder. If you
are installing this version of IxChariot over a previous version of NetIQ's
Chariot, the installation program detects the older version and uses the same
Program folder. You can change the destination folder during the installation
process.
Also, tests and script default directories can be changed in the Console
(Options->Change User Settings->Directories).
Please refer to our website at http://www.ixiacom.com/library. PDF and HTML
versions of all documentation are available there.
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.
6.60 EA Features
| IxChariot Console |
| The IxChariot Console now supports the Windows Vista operating system. This version has been tested to work with Vista Business, Enterprise and Ultimate editions with SP1 installed. |
IPTV
| Bug Number |
Notes |
| 334330 |
IPTV pairs do not finish when set to run until all/any pair ends and collect CPU utilization is enabled.
|
SDK
| Bug Number |
Notes |
| 334520 |
Error code should be returned when trying to check-in pairs from API and there is no connection to the license server.
|
Stack Manager
| Bug Number |
Notes |
| 333444 |
The LSM 10G LAN XFP load module is not recognized by IxChariot.
|
Endpoints
| Bug Number |
Notes |
| 244084 |
Ixia Performance Endpoints for IxOS may not be able to establish connectivity with the IxChariot Console to report statistics when the SOCKS proxy on the Ixia chassis is used. Therefore, we do not recommend running a large pair count test using Performance Endpoints for IxOS in conjunction with the SOCKS server. A direct route must be established to the Ixia endpoint from the console to ensure delivery of timing records.
|
| 245595 |
Multiple endpoint processes may not be run on the same device simultaneously.
You must delete the existing endpoint from the device before you install this endpoint.
|
| 252218 |
A test with multiple Windows Endpoints may run pairs sequentially, rather than concurrently. In the GUI this appears as multiple pairs graphed one after another. This problem only occurs when very small amounts of data are being transmitted from E2 to E1 using Windows Endpoints.
|
| 265140 |
Tested versions of Windows Vista show high performance timer errors on long duration tests.
|
| 268861 |
During script execution a failure can occur on a CONNECT. This occurs with short-connection scripts with endpoints running on Windows XP 64-bit on Opteron processors. A workaround is to use a non-AUTO port, or use a long-connection script.
|
| 272810 |
If an RTP test is run over a network with insufficient bandwidth, IxChariot will send packets at the scheduled data rate until the buffer is full and then it will stop sending until the buffer has space. This can cause inaccurate results for one-way delay and timing.
|
| 277307 |
Only one pair at a time can use a given port number for a given datagram protocol (that is, RTP, IPX or UDP). For example, only one endpoint at a time can use port number 1234 with UDP.
|
| 284714 |
In measuring TCP statistics, we measure statistics only within a timing record. This means that in a long connection script the initial 3-way handshake and the termination of the connection may not be recorded. This is in line with the IxChariot paradigm wherein we measure all statistics only between the START_TIMER and the END_TIMER statements. In IxChariot, TCP statistics measurements are only half-duplex and are in the Endpoint 1 to Endpoint 2 direction.
|
| 288763 |
Windows CE show the wrong value for 'Maximum disk usage for payload files' when you select 'Show EP configuration' in the IxChariot console.
|
| 305811 |
Short connection script with a small send buffer sizes sent from E2 to E1 may not stop when running for a fixed duration.
|
| 308496 |
Throughput measurements reported by IxChariot using IPSec plugin on ELM cards are lower than ALM cards. IPv6 traffic throughput values are lower as compared to IPv4.
|
| 309582 |
In some cases, reinitialization of multicast pairs may cause additional multicast sources to appear, sending traffic to the same multicast channel from different ports. Restarting the test will reset system to initial conditions.
|
| 309899 |
PSAPI.DLL missing from Windows NT installation should be downloaded from Microsoft web site (search for
"Platform SDK Redistributable: PSAPI for Windows NT") and installed using instructions provided by Microsoft.
|
| 326721 |
The Ixia port CPU's do not have support for setting the MSS under IPv6.
|
| 327422 |
RTP streaming pairs do not support the normal, poisson, and exponential distributions. RTP streams are used to send fixed-size media segments at a fixed rate.
|
| 327690 |
Sending payload data in chunks larger than 1900 bytes will potentially crash the Port CPU when using IPSec UDP tests over ELM ST2 load modules.
To avoid this you have to either set the SEND and RECEIVE buffer size in the IxChariot script at most 1900 bytes or set the size of the record to send at most 1900 bytes.
|
| 327931 |
IxChariot Port crash when running IPTVv pairs across two ports
|
| 329784 |
IxChariot Throughput BW is reduced to half when IxLoad 3.20 is installed on Chassis
|
| 332123 |
When running streaming tests with 10GELSM and XM3 ports as senders on IxOS 5.0SP4 (or earlier IxOS 5.0 build), data loss will be reported.
|
| 333174 |
In some tests with a Mac endpoint as E1 extremely high one-way delay values (3,000,000 ms) may be encountered.
|
| 337898 |
Proxy Endpoint: Installing a newer version does not trigger an 'upgrade' installation.
|
| 342966 |
After creating an RTP test using two or more chasiss connected in a chain configuration it is possible to see that the one-way delay values will keep increasing throughout the test. To workaround this issue one has to save the test after it is created, load it and run it again.
|
| 415362 |
IxChariot QoS on IPv6 from responder to initiator may not work on Linux-based systems. We have found some systems where 'ACK' traffic from the responder is not correctly marked with the configured TOS/DSCP value.
|
| 416501 |
On Windows platforms, users may experience failures when jumbo frames (9000 bytes) are enabled, socket buffers are set to 1024 bytes, and Nagle's algorithm is disabled. This is seen in other TCP/IP applications as well.
|
| 416881 |
There is an issue on LSM10G1 and LSM10GXM3 cards that occasionally causes IPv6 datagrams to be sent with a UDP checksum of zero. These frames will be marked as lost by IxChariot since the checksum is invalid.
|
| 419509 |
Mac endpoint not marking some SynAck packets with QoS
|
| 419510 |
IBM AIX endpoint not marking some SynAck packets with QoS
|
| 419511 |
IxChariot doesn't support QoS on IPv6 from the responding party in a TCP connection.
|
| 430428 |
When an IxChariot script defines a flow with a very high packet rate, some endpoints may not be powerful enough to receive, classify and measure the packets at the same rate. In this case some packets may be reported as lost. This only occurs at very high packet rates (] 2000 PPS). Increasing the receive_buffer on Endpoint 2 may resolve this issue in some cases.
|
| 439904 |
Ixia Performance Endpoints for IxOS do not support changing the MSS from the script. As a workaround, the MTU size may be changed in StackManager to restrict overall packet size.
|
Hardware Performance Pairs
| Bug Number |
Notes |
| 229623 |
If a test involving a Hardware Performance Pair fails abnormally or the endpoint is abandoned, the Ixia port continues to transmit data. It should be stopped as described in the Troubleshooting Guide of the IxChariot User's Guide.
|
| 230381 |
Hardware Performance Pairs will always report results in Real Time. There is currently no batch feature.
|
| 230416 |
Hardware Performance Pairs transmit some latent data after initiating the test stop sequence. When the IxChariot Stop button is pressed or a test stops, the Hardware Performance Pairs stop reporting results. However, there may be some data transmitted by the Ixia ports during this time that is found on the wire, but not accounted for in the statistics. The statistics up until the Stop command was pressed are accurate.
|
| 230467 |
Only one IxChariot Console may own and use a given Ixia Chassis's Port for any given test. Users should not try to run tests with multiple consoles using Hardware Performance Pairs.
|
| 230644 |
Hardware Performance Pair streams must use Fixed or Random frame sizes. Stream files (.str) used for Hardware Performance Pairs may only contain streams whose frame sizes are fixed (no less than 74 bytes) or random (minimum 74 bytes).
|
| 233087 |
When running a test with Hardware Performance Pairs, the capture mode of the Ixia port may be reset. If the port on which capture is to take place is an Endpoint 1 of a test pair, the port will reset during test setup. This includes a reset of the capture mode.
|
| 238413 |
Endpoint Pairs should avoid using UDP port numbers used by Hardware Performance Pairs. When using LM100TXS8 load modules, use of the same UDP port # by a Hardware Performance Pair and a standard IxChariot Endpoint Pair will cause erroneous results in UDP Endpoint Pairs. Please ensure that UDP port numbers for Hardware Performance Pairs and Endpoint Pairs differ.
|
| 238783 |
Hardware Performance Pair latency statistics will be smooth over very long duration tests. The Ixia Hardware reports average latency over all time and IxChariot calculates timing records based on this cumulative average. This will cause the results to be presented artificially smoothed.
|
| 249806 |
For Hardware Performance Pairs, selecting the "Measure statistics" option will prevent setting the Reject Pattern filter on E2. This can cause E2's Port CPU to become overwhelmed with traffic. Performance Endpoints will not run effectively on the E2 port.
|
| 258591 |
IxChariot's Hardware Performance Pairs may not be run against chassis running IxTclServer as a service. IxTclServer must be run as an application.
|
| 272685 |
If you deploy an Ixia stream (.sdf) file that does not define any streams, IxChariot will issue a CHR5601 error message ("Internal error in TCL API when running HPP test").
|
| 303339 |
Hardware performance pairs do not support the DHCP plugin in Stack Manager
|
| 307083 |
Hardware performance pairs in IxChariot need to have specific IP addresses assigned when using a port group with a mixture of IPv4 and IPv6 addresses. HPPs and VHPPs may pick up a wrong IP address and hence may not run if set using the port group name.
|
| 307950 |
IPv6 hardware performance pairs do not support neighbor discovery and hence may not work through a DUT
|
| 344892 |
Hardware performance pairs using DHCPv4 IP addressing will not pass data through a DUT.
|
IPTV
| Bug Number |
Notes |
| 330285 |
If one pair in the IPTV switching group encounters an error, the switch process will continue among the remaining pairs if the number of errors in run options is bigger than the current number of failed pairs and "run until all pairs ends" is checked.
|
Installation
| Bug Number |
Notes |
| 257720 |
If the Windows Installer Service has been stopped on the target machine the user will receive an installation error indicating that the Windows Installer Service could not be accessed. After the user starts the service, they can attempt the product installation.
|
| 259161 |
The user is required to have administrator rights on the machine on which he or she is attempting to install or operate IxChariot.
|
| 260192 |
When the user removes the console by selecting the 'Remove' button on the IxChariot entry in the Windows Add/Remove Programs applet, the un-installation does
not provide the option to preserve data files. Instead
files are always preserved.
|
| 260455 |
The installation for .NET 1.1 SP1 indicates that .NET is optional for IxChariot. This is misleading; .NET is required for IxChariot to operate. The IxChariot Installation will provide an error later in the installation process if .NET is not correctly installed.
|
| 260621 |
Occasionally during installation of the web version of the installer package, the user may be presented with an error dialog indicating there is not enough space on the system drive. In fact, there could be more than sufficient space available. In these cases, the user will need to delete temporary files from the directory specified by their TEMP environment variable. Once the space is freed in TEMP, the user should re-attempt the installation.
|
| 261126 |
To update an existing installation using a IxChariot.msi file, the user will need to use the following command line:
msiexec /I IxChariot.msi REINSTALL=ALL REINSTALLMODE=vomus
|
| 261350 |
The user is presented with a 1603 error code while attempting to install IxChariot 6.10 on a 64-bit operating system.
The IxChariot installer requires Microsoft .Net Framework 1.1 be installed on the target machine. At the moment, Microsoft does not support installation of the 1.1 framework
release on 64-bit Windows operating system.
|
| 290288 |
You can remove IxChariot by selecting the 'Change' button. This will initiate the maintenance screens that allows you to select 'Remove' to uninstall.
|
| 298602 |
When Test Conductor and IxChariot are installed on the same host computer, it is possible to uninstall IxChariot while an Test Conductor is running an IxChariot regression check. This will result in Test Conductor runtime failures.
|
| 307850 |
When viewing the Support Info of an application via the Add/Remove Programs applet, the 'Close' button does not dismiss the Support Info dialog. The user move close the window via the 'x' button.
|
| 320033 |
The installer informs that Micosoft .Net Framework 1.1 installation is optional. This is not the case. If the user decides not to install Microsoft .Net Framework 1.1, the IxChariot application will not funtion properly.
|
IxChariot Console
| Bug Number |
Notes |
| 249907 |
Scripts from older versions of IxChariot will be upgraded such that constant buffer_type variables are replaced with a variable.
|
| 261084 |
Starting with the 6.10 release, automatic downgrades are not supported for Console and Viewer installation. The user is presented with a dialog indicating the current release must be removed (un-installed). This can be accomplished via the Windows Add/Remove Programs application.
|
| 262868 |
Running a test with multiple chassis can require PCPU routes be set up to communicate between chassis in some configurations. When the test is configured such that E1 and E2 reside on ports on different chassis, and E1 knows E2 is set to use the chassis management network, the routing tables on the PCPUs must be set to include the PCPU management address on the other chassis.
|
| 263952 |
Video pair functionality in IxChariot lets you emulate single program streams (SPTS) with constant bit rates and constant packet sizes. Variable bit rate and variable packet size encoding schemes such as MPEG-4 cannot be emulated. Also, the MDI standards draft does not propose a method to generate MDI for variable bit rate streaming media.
|
| 267593 |
IxOS TCP stats will not increment the "ACK to FIN" counter if the ACK is paired with a RESET flag.
|
| 268074 |
For configurations using "localhost" as the E1 test address, 802.11 statistics will be unavailable.
|
| 268141 |
If the IxChariot console loses focus while a long-running activity is taking place and a progress bar is displayed, the console screen stops refreshing and it is marked as 'Not Responding' by Windows.
|
| 272680 |
In the event a synchronized pair fails during a test, all waiting events will be signaled to prevent deadlocks.
|
| 280745 |
TXS-8 cards do not support the new hardware timestamp clock synching.
|
| 283199 |
It is not possible to open more than approximately five large scale test files in multiple IxChariot consoles simultaneously. We recommend only opening a maximum of four test windows in order to avoid this problem.
|
| 286664 |
The IxChariot console window does not remember its size and position between runs.
|
| 290640 |
This issue occurs when the same console machine is used with IxApplifier to configure the ports. There is no way to view, change, or delete the SOCKS configuration from within IxChariot. The customer must use IxApplifier or edit/delete the configuration file manually. To get around this issue, delete socks.cnf file from user settings directory (typically, C:\Documents and Setting\[username]).
|
| 309453 |
Help topics are not available from IxChariot console registration dialog. Information on registering the product and managing your license can be found on page 3-10 of IxChariot Getting Started Guide.
|
| 339927 |
When running UDP tests, some test results may not be returned to the console if multiple console windows are open.
|
| 341256 |
The traceroute function does not work for pairs that have out-of-band management addresses.
|
License Management
| Bug Number |
Notes |
| 279582 |
When a license server is used to obtain floating licenses and the name of the license server (as opposed to its IP address) is used to reference the server, a slow DNS environment will slow down product operation. Either repair the DNS system or use the license server's IP address.
|
| 279587 |
Using a license server with Licensing Version 2.0 requires an IPv4 address on the license server.
|
| 279607 |
The Itanium 64 platform is not supported for installation of Licensing Management software.
|
| 425290 |
Under some conditions when connectivity to the floating license server is disrupted, user may need to restart Ixia licensing service before starting IxChariot console.
|
| 425954 |
When the user checks out a number of pairs from a Floating License Server by using 'Release on Exit' option and then tries to check in the pairs when the connectivity with FLS is down, the console will release all pairs without returning them to FLS. There is an workaround for restoring the pairs on FLS by restarting the 'IxiaLicenseServer' service.
Note: Restarting the service will not restore the borrowed pairs; only the pairs that were checked out using 'Release on Exit' option.
|
| 436279 |
When the user (e.g. [chariot_user_1]) tries to check in the pairs borrowed from a Floating License Server, but during the borrowing period the Administrator of the Floating License Server configures a MAX limit of pairs for this user ([chariot_user_1]), then IxChariot console will throw an exception. In order to avoid this behavior, the user have to clear the registry key 'Borrow' from \\HKCU\Software\Flexlm License Manager\.
|
SDK
| Bug Number |
Notes |
| 275255 |
To create a test using IxChariot Tcl API, you must make the IxChariot installation directory your current working directory. Without this you will get an error 'could not load library chariotext: this library or a dependent library could not be found in the library path'.
|
| 281043 |
In IxChariot 6.25 an IP Plugin is created by default when using the APIs. In later versions of IxChariot, TestServer does not create the IP Plugin by default. All customers using 6.25 API scripts need to change their code to add IP Plugin for the same scripts to work on versions later than 6.25.
|
| 288347 |
If you are developing a .NET application that uses the IxChariot SDK with floating licenses your Application.UserAppDataPath property should be set to point to '../[documents and settings]/[profile name]/Application Data' directory, before any calls to the IxChariot SDK are made.
For both the TCL and C APIs, if you have .NET 2.0 installed, you should also ensure that the application uses v1.1.4322 of the .NET framework by creating a .config file. IxChariot.exe.config may be used as a template.
|
Stack Manager API
| Bug Number |
Notes |
| 262348 |
The test server can be started manually in the background by using the standard Tcl "exec" command e.g.:
exec "/aptxia-install-directory/bin/win/TestServer.exe" --service
note the two dashes for --service.
|
| 262470 |
The Stack Manager TCL API has a minimum TCL version requirement of 8.4.
|
Stack Manager
| Bug Number |
Notes |
| 259432 |
IxApplifier .ITS files may only be imported to an Ixia Hardware Configuration using the option in Stack Manager. You cannot load an .ITS file directly into IxChariot.
|
| 259841 |
When running an IxChariot test with an Ixia Hardware Configuration, and SOCKS is disabled, static routes must be mapped from the Console to each E1 used in the test.
|
| 260213 |
IxChariot does not currently release ownership of ports used in an IxChariot test. For tests that use Ixia hardware configurations or Hardware Performance Pairs, the user must manually release ownership in Stack Manager.
|
| 261993 |
Stack Manager configuration is specific to a test. If pairs are copied from one test to another then the corresponding Stack Manager configuration must also be copied.
|
| 262096 |
On a filter plugin, user cannot apply enable/disable PPPoE settings on the Ixia port. By default, PPPoE settings are always enabled.
|
| 262374 |
Increasing the dpi to 120 in the graphic card settings causes the Stack Manager GUI to display incorrectly. Using large font from the appearance tab of display settings works fine.
|
| 262586 |
In order to release ownership all non-active chassis need to be removed from the port picker dialog.
|
| 263102 |
When taking advantage of IxImpair with IxChariot Video Pairs, the Run Option "Use Ixia Hardware Timestamps" must be disabled.
|
| 265395 |
If the port in a Stack Manager configuration is rebooted between IxChariot test-runs, the configuration will not be automatically re-applied. Open Stack Manager and click OK, to force a reconfiguration of the ports that have been rebooted.
|
| 269858 |
Stack Manager will fail to open on any machine whose default language is not US English. The workaround is to set the system default language to US English.
|
| 270854 |
Currently Stack Manager cannot configure a port on E2 when the same pair's E1 is a non-IxOS performance endpoint.
|
| 272262 |
Stack manager configurations will not run Hardware Performance Pairs in physical chassis chain setups of 3 or more chassis. This will be resolved in an upcoming release.
|
| 286231 |
When using ALM1000T8 load modules in a PPP test, the first test after a fresh port reboot will fail. To resolve this issue, use the Filters plugin in StackManager to "Enable All".
|
| 287182 |
The Ixia hardware timestamp feature is not compatible with the IPSEC plugin since the FPGA cannot write the timestamp to an encrypted packet. This only applies to tests using RTP pairs.
|
| 342773 |
When testing using an Ixia AFD-1 as the external clock source, the user must manually reset the hardware timestamps using IxExplorer. To do this, open IxExplorer and add all chassis to a chassis chain. After this is complete, right-click on the root of the chassis chain and select "Clear Timestamps".
|
| 406065 |
Port Groups, or networks, in StackManager should not have an IP address as their name.
|
| 419942 |
Only ASM1000XMV12X and LSM1000XMVx modules currently support the 0x88a8 TPID for 802.1ad VLAN tagging.
|
Test Scheduler
| Bug Number |
Notes |
| 284156 |
It is not possible to delete a single instance of a recurring test. For example, if you create a daily test, it is not possible to select a single day and delete the tests only for that day.
|
| 284552 |
If a test fails, error messages generated are not currently integrated with the IxChariot help system. You must open the saved test file and use existing IxChariot features to retrieve the saved error messages.
|
IxChariot Runtime
The IxChariot Runtime Console is designed with the needs of a field service or
manufacturing organization in mind. Tests are designed on a centralized
fully-featured IxChariot Console. IxChariot Runtime can be used to run
existing tests again after modifying the addresses of the Ixia Performance
Endpoints of the pairs. Its functionality is very similar to that of the
IxChariot Console, with a few limitations.
Main restrictions in IxChariot Runtime:
- Tests cannot be created, only read and repeated
- Pairs cannot be added or deleted
- Script files are not provided, nor can the scripts used in previous
tests be modified.
For detailed information about IxChariot Runtime, refer to the printed User Guide
for IxChariot Runtime.
IxChariot Test Viewer Capabilities
The IxChariot Test Viewer is a free utility that enhances the IxChariot Console.
It is designed to allow you to view existing IxChariot test results when you are
away from the IxChariot Console computer. With the IxChariot Test Viewer, you can
review and print results, as well as make modifications to the way IxChariot test
data is displayed. You can also modify the sorting and grouping options for
endpoint pairs to analyze and view the data from different perspectives.
In addition to calling up results of previous tests, the Viewer has the following
capabilities:
- IxChariot's Compare Tests feature is enabled in the Test Viewer.
- Results can be saved in different formats, for different versions of
IxChariot.
- Results can be exported to any of several formats.
- Unlike the IxChariot Console, the IxChariot Test Viewer is not designed to
configure or execute tests.
Main restrictions of the IxChariot Test Viewer:
- Tests cannot be created or run.
- Pairs cannot be added.
- The Viewer cannot be installed on the same computer as the IxChariot
Console.
- Script files are not provided, nor can test scripts used in previous tests
be edited.
- The IxChariot Application Programming Interface is not supported.
- The Viewer only reads previously saved test files.
Additional Information
- Comparing real-time and batch reporting
Under some conditions, you can run the same test using real-time and batch
reporting and get numbers that say the transaction rate and throughput are
poorer with real-time than with batch reporting. This is because real-time
reporting is much more disruptive, generating more network traffic than batch
reporting. This condition can occur because you are generating far too many
timing records; - the port's CPU spends more time generating timing records
than doing the work inside the scripts. Because of queuing effects, a script
can appear to run faster with real-time reporting than with batch reporting.
This behavior can also occur when you are running a large number of endpoint
pairs in a network or on a single computer. For reliable performance results,
always use batch reporting. In addition, Ixia always recommends using batch
reporting when running tests on an Ixia chassis.
- One-way (network) delay measurement is currently supported on IxOS, Windows,
Linux, and Solaris platforms.
In addition, the accuracy with which endpoints can measure one-way delay
depends on the accuracy of the high-performance timers on these platforms. The
timers on Windows 2000, Windows NT, and Sun ULTRA platforms provide the best
performance, while timers on Windows 98, Windows Me, Sun x86, and pre-ULTRA
SPARCs are less accurate; they report generally higher estimated and maximum
clock errors on IxChariot's One-Way Delay tab. For the most precise,
high-resolution one-way delay measurements on high-speed LANs, test with
endpoints running on IxOS, Windows XP, Windows 2000, Windows NT, and Sun ULTRA
platforms. A hardware bug on some PCs occasionally causes the high-performance
timer to leap ahead unexpectedly. IxChariot detects this problem if it occurs
during a test, and fails the involved pair(s) with error CHR0359. For more
information about this bug and a list of affected hardware, see
http://msdn.microsoft.com/bugs, article Q274323.
- Disable your screen saver
Screen savers in Windows can significantly lower the throughput that is measured
by an endpoint. We recommend disabling your screen saver on endpoint computers
while running tests.
- Script support
Ixia ships a wide variety of application scripts with IxChariot to help you
emulate most popular applications. Our IxProfile 1.15 is the best way to get
custom scripts of other applications in your network.
*IxChariot is a registered trademark of Ixia. United States Patent Numbers
5,838,919, 5,881,237, 5,937,165, and 6,061,725. Other patents pending.
*IxChariot is a registered trademark of Ixia. United States Patent Numbers
5,838,919, 5,881,237, 5,937,165, and 6,061,725. Other patents pending.
CONTAINS
IBM VisualAge for C++ for Windows, Version 3.5
Runtime Modules
Copyright IBM Corporation 1996
All Rights Reserved
Software written and copyrighted by Henry Spencer:
Copyright 1992 Henry Spencer.
Copyright 1992, 1993
The Regents of the University of California.
All rights reserved.
Redistribution and use in source and binary forms, with or without modification,
are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this
list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must
display the following acknowledgement: This product includes software
developed by the University of California, Berkeley and its contributors.
4. Neither the name of the University nor the names of its contributors may be
used to endorse or promote products derived from this software without
specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS "AS IS" AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Ixia
26601 W. Agoura Road
Calabasas, CA 91302 U.S.A.
Web: www.ixiacom.com
www.ixiacom.com
Phone: +1 818 871-1800 or + 1 877 FOR IXIA
Fax: +1 818 871 1805
General information:
Email: info@ixiacom.com
IxChariot Technical support:
Email: support@ixiacom.com
Ixia support hours are 6:00AM PST to 6:00PM PST.
For technical assistance, including product repairs/RMA's, please email us at:
support@ixiacom.com or phone us at (877) 367-4942. Outside the United States
phone us at 1-818-871-1800 (Option 1).
For technical assistance in Europe, Middle East, and Africa, please email us at:
eurosupport@ixiacom.com or phone us at +44 (0) 1628 405797.
For technical assistance in India, please email us at: support-india@ixiacom.com
or phone us at +91-80-32918500.
For technical assistance in Asia Pacific, please email us at:
Support-Field-Asia-Pacific@ixiacom.com or phone us at: +65-6332-0126 or Fax at:
+65-6332-0127.