IxChariot Reviews

We use this tool as a traffic generator tool. It is used to test the performance KPIs and throughput numbers. It is also used in long-run stability test cases where you want continuous bandwidth data traffic. For example, if you're going to run a 12-hour overnight period, you can configure it in the IxChariot window and create a pace. You can generate traffic between whom, what, and the endpoints. So if you put it in that window and run it for 12 hours, it'll run and give you results in graph format, histograms or even pie charts. You can determine the throughput units if you want Mbps or Gbps. You may have some initial difficulties configuring if you are not used to the tools, but it gets easier as you become more familiar.

The most valuable feature is multimedia testing. We can easily simulate voice traffic, video traffic, and networking control traffic in IxChariot. When you install IxChariot, it will simulate video traffic, and scripts are also available.

The graphical user interface needs to be improved. But this issue may depend on the host machine. For example, if we want to host using a desktop, we can run it for 20 to 72 hours without issues. But, if it's in a virtual machine, after about 24 hours, we cannot see the graph, and it hangs and sometimes crashes.

We are currently using this solution at my company as a digital company license. On our local server, we deploy every endpoint with a test setup on the main system. We install the endpoint, and the server gives us the license for how many payers are on the IxChariot. It tells us the networks where we have to run the traffic, and the information is stored on the server. For example, if we have 200 licenses for 200 payers, we may need 20 payers in our setup. So the IxChariot machine will ask how many payers we want, and we can select 20 payers. That will leave 180 payers we can use in other setups.

It is a stable solution, and there are no issues. However, some difficulties may exist depending on the machine you choose to complete the run.

It is very scalable. You can easily increase the payers in the license activation. If you have any issues, the IxChariot host system can be rebooted.

We currently have about 100 setups in our lab. Out of those 100 setups, around 90 are being used. So overall, 90% of the setups use a minimum of 10 paces where we test the range versus rate. In addition, we are building up several test bits, which will increase the usage.

No maintenance is required for this solution unless the host system has a problem. Once IxChariot is installed, it automatically updates if you set it to auto-update.

The technical support is good. We have also included Ix in our automation, so it is very easy to incorporate this utility. If you want to run traffic, you call the solution, which is straightforward. You create a TST file, run it in the background, and it usually gives results.

We currently also use Iperf traffic. The only drawback between IxChariot and Iperf is that it drops in between. For some reason, a drop in throughput that can only be caught in the Ixia. So sometimes, while running the traffic, it produces zero bites if we hit zero traffic. It is an issue for WLAN, but those things may not be caught in Ixia. So they will treat it as 0.1 per Mbps, whereas in Iperf, it shows perfect and zero means zero.

I rate the initial setup a six out of ten. It was not complicated, but it took some time to become familiar with the solution.

In addition, the unicast date, between one point to another, is straightforward. However, the licenses are given based on the number of paces, which can be costly. If you are using multiple clients, you can create a duty but need to run all the available points rapidly. For example, if you have 100 clients, you can create and run 100 paces using IxChariot in one shot. Whereas with a solution like Iperf, you must press enter for every client, which is complicated as you have to go to 100 windows and start 100 paces simultaneously. With IxChariot, you only have to create one run and push one button, and it is completed.

Regarding deployment, if you have a single-user license, you will be given a license key with the product. The utility must be installed and downloaded onto the system, run like any Windows machine, and have the license key incorporated. The IxChariot machine will talk to the server and get the license. It's very easy to install. We only required one person for deployment, which took barely half an hour.

I don't believe we have measured the ROI as this is a test tool. But, so far, it is a good investment. We plan to observe what products the company is making and how they work in the market.

I don't know specific details about licensing, but I believe the licensing is annual. So I rate the pricing an eight out of ten, with ten being very reasonable pricing.

I rate this solution an eight out of ten. It is user-friendly but requires a little hand-holding for a new user. Aside from that, almost everything is available with this solution. You can get data like the error rate, the loss percentage, throughput numbers, the TID, and the WLAN traffic.

Implementing IxChariot is very easy and user-friendly. Whatever is required for wireless LANs is available in IxChariot. It is in the test range of Wi-Fi test labs, so any changes in the feature operations in the Wi-Fi will directly impact it. Currently, this Wi-Fi mostly works in layer two, and if they want to use layer three traffic in the future, they will need to incorporate those features in Chariot by Ixia.