What is our primary use case?
The QFX was used for Layer 2 connectivity and Layer3 VXLAN overly (ERB/CRB) and DCI between the data center, and the virtual infrastructure. It was used for an IP fabric implementation as well.
How has it helped my organization?
For storage switches only FCOE is support, where it don't have FC (Fiber channel support) like other vendor do, so i have arrange other vendor FC switches.
What is most valuable?
Many customers prefer the QFX series over Cisco's Nexus series. They also appreciate the high density of ports the QFX series offers, such as 1/10/25G and 100/40G options on the same switch. Additionally, the QFX series boasts lower power consumption compared to competitor products.
One key advantage of the QFX series is that Juniper uses Broadcom chipsets in their switches. This offers several advantages, including better performance and cost-effectiveness.
What needs improvement?
I faced issues with the deployment and upgrade. In the QFX5110 series, features like ISSU and TSSQ should be improved. Upgrades should be smoother.
Also, Juniper doesn't offer dedicated fiber connectivity for storage
This can be a pain when designing for Dell or other storage solutions that need dedicated switches. This functionality should be included in the QFX series.
Either enhancement would work. Or they could introduce a new product. Cisco and other vendors offer similar solutions.
For how long have I used the solution?
I've been working with them for seven to eight years.
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
In terms of performance, scalability, and other factors, I would rate them around eight out of ten. I've encountered a few issues during deployments based on customer experiences.
My first deployment was with the QFX5100-48S for a data center customer. I implemented layer-2 connectivity on them. Overall, I would say they're good for small-scale and medium scale so it seems these problems can persist for some time. However, the QFX series is still generally considered a good product and offers more flexibility than other options.
It's very scalable. I haven't heard any customer complaints about scalability. In my experience, even the QFX5110 series extends for many years without needing upgrades. This scalability solves the challenge of needing to upgrade due to unknown internal problems, even when the release is stable.
How are customer service and support?
Usually, I don't face any challenges due to my expertise.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I work with several Juniper solutions currently. For example, I designed a new data center solution for a customer using a Spine-Leaf architecture. The access layer will be handled by ACX switches in the metro area, which are working well.
In the data center itself, I'm using MX2000s for Data Center interconnect, The ACX series is also a good option as it's a joint venture between Juniper and Mist Systems, combining the best of both companies' product lines. The new product ACX has which is temperature-hardened and ideal for network deployments.
I also work with the PTX series for core networks. I have one customer using PTXs, and two more customers considering switching from their current Ethernet switches to the ACX platform. This will allow them to extend their network from the legacy layer to EVPN, providing benefits like load balancing, scalability, and improved performance.
How was the initial setup?
The initial setup is not too complex as Junos, which is generally easy to use. You just need basic knowledge, itself is more data center focused. With good planning and tools like zero-touch programming, deployment can be fast. For IP fabric, with juniper apstra Automation tools make deployment quite smooth.
Maintenance is a different story compared to upgrading one or two switches. It's similar to the MX series.
What about the implementation team?
we are juniper partner , we do deployment for juniper products ourself.
What was our ROI?
For partners and Juniper Networks itself, the QFX Series has significant value. However, customers sometimes face challenges, potentially due to misinformation from Juniper partners or sales representatives.
Customers might start with a basic license and later need to upgrade to a more advanced one, often at full price, missing out on initial discounts.
This pricing model applies to both the hardware and the software components, like advanced licensing, which doesn't have an easy upgrade path. It creates a financial burden when scaling up network capabilities.
Also, it's important to consider customer commitment and satisfaction.
What's my experience with pricing, setup cost, and licensing?
In my experience, the QFX Series excels in scalability. For instance, to utilize new features, additional licenses are required. If the initial device capability is denoted as 'X', for these new features, customers typically pay a cost of 'X plus 20%', approximately. This cost structure is similar across many enterprise-grade network platforms. However, for edge or top-of-rack switches, other models, like the EX4650, ACX7100. The challenges I've encountered include occasional difficulties with software upgrades.
Which other solutions did I evaluate?
What other advice do I have?
Skilled personnel should be involved and have a well-planned approach. Test on virtual QFX before customer environments.
For large-scale deployments, consider using automation tools like Ansible, combined with Zero Touch Provisioning (ZTP) for efficiency.
Additionally, using an apstra for data center automation can provide more flexibility and ease in deployment and management. It's crucial to have a well-thought-out strategy for both the hardware and software aspects of the network infrastructure.
It's not a bad product. I haven't had extensive experience, only about six to seven years, deploying it for a maximum of six to seven customers. So, I can't fairly rate it a ten out of ten due to my limited experience. I have been more familiar with M/MX/ACX/PTX series architectures and E series for a long time.
So, overall, I would rate the solution an nine out of ten.
Which deployment model are you using for this solution?
On-premises
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other