The use case for this tool is generally for enterprise customers who have more than two monitoring tools. These customers obtain information from switches that have a limitation of up to two-point mirroring or span ports. Therefore, if I have more than two monitoring tools, I need a network packet broker.
What is our primary use case?
How has it helped my organization?
By using the Bitbox as a medium for capturing data, my organization can reduce the pricing for the probe solution.
What is most valuable?
The most valuable features for me include deduplication, metadata processing, and the ability to perform media services. I typically offer these features to my customers.
What needs improvement?
The data center facet of IxNetwork Packet Broker can be improved, particularly concerning mapping from the cache.
For how long have I used the solution?
I have recently started using IxNetwork VE after moving to my company about three to four months ago.
What do I think about the stability of the solution?
The stability of IxNetwork is consistent for me, particularly considering the different processing needs for different modules. It is very stable.
What do I think about the scalability of the solution?
I would rate the scalability of this solution as high scalability.
How was the initial setup?
The initial setup of my Network Packet Broker implementation was not too complicated. It is straightforward.
What was our ROI?
Regarding ROI, using Keysight for the KRF is beneficial for me because the probe solution can function with lower specifications.
What's my experience with pricing, setup cost, and licensing?
The pricing of this solution is usually quite high.
What other advice do I have?
I would recommend IxNetwork VE to others. By using the Network Packet Broker, especially for enterprise customers, it can reduce the pricing for the probe solution and make monitoring more efficient.
I would rate the solution an eight out of ten.
Which deployment model are you using for this solution?
On-premises

