We have a lot of customers that we implement Nexus platforms for.
Pre-Sales Engineer at a tech services company with 5,001-10,000 employees
A high-performance switch that is designed for lossless data and our customers are happy with
Pros and Cons
- "They are very high-performance switches and they are made for lossless data, so they're a good play in the customer environment."
- "There is no feature parity between the 9K and the 5K or 7K, which means that it is harder to position the 9K to future proof them."
What is our primary use case?
How has it helped my organization?
This product is made for lossless data, so it's a very high-performance switch. If there's one place you don't want to lose data, it's in the data center. The 9Ks support speeds of 40-gigabit and 100-gigabit, today. They've got pretty good throughput in the box, they've got virtual output queues, things of that nature, which help contribute to the lossless data.
What is most valuable?
I like a lot about this solution. They are very high-performance switches and they are made for lossless data, so they're a good play in the customer environment.
What needs improvement?
The 9K was developed to support ACI, the software-defined data center technology. For this reason, there is no feature parity between the 9K and the 5K or 7K, which means that it is harder to position the 9K to future proof them. If a customer wants to leverage their investment for ACI in the future then it is difficult. I know that Cisco has added some Fibre Channel over Ethernet capabilities to the 9K line, but there are some other features that it does not have capabilities for. For example, virtual device context is not supported. It would be really nice to see some capabilities like that added to the 9K line so that we can position them to future-proof our customers.
I understand why it is that they don't have some of the features from the older Nexus models, but we get into some scenarios where the customers need those features, and they have to go with a 7K or a 5K. Ideally, I would prefer to position a 9K if I could, to future-proof them and lead them along that path to ACI, eventually.
Buyer's Guide
Cisco Nexus
December 2024
Learn what your peers think about Cisco Nexus. Get advice and tips from experienced pros sharing their opinions. Updated: December 2024.
824,067 professionals have used our research since 2012.
What do I think about the stability of the solution?
With respect to the stability, I can't think of any major issues I've ever come across with it.
What do I think about the scalability of the solution?
I think that these units are made to scale, but it depends on how they're deployed. If they're deployed within an ACI environment and that's the customer's expectation, they work fine.
If they're deployed, say, a 9500 model in a non-ACI role, a traditional data center switching role, and the customer decides that they want a virtual device context then we could not support it in that scenario. In this particular case, it wouldn't really scale. That is why it's tough sometimes, in a non-ACI environment, to implement the 9K.
How are customer service and support?
In general, Cisco has always got good technical support.
They're responsive, their people are always available, and they respond relatively quickly. Compared to competitors such as HP, Aruba, Dell EMC Networking, etc, the support from Cisco is always a head and shoulders above those other competitors.
How was the initial setup?
There is some complexity to the initial setup of this solution.
There are a lot of facets to configure a network. It's one thing to configure VLANs and things like that, but when you're configuring quality of service, for example, on a Nexus device, it's all class maps, service policies, mapping queues, and things like that. There is no auto QOS functionality like you might have on a Catalyst switch line, so they're a little bit more complex.
It is not really a big deal because once people have worked with them a little bit, they master it and move on.
What was our ROI?
They don't see additional revenue from it, but they do see cost savings. With the 9K in NX-OS mode, there's still a lot of touch points with them, although the support for bash and pipe can really simplify that. In an ACI mode, certainly, there are savings because of the orchestration and automation that's occurring as part of the software-defined network.
What's my experience with pricing, setup cost, and licensing?
Cisco's licensing structures can be complex across different technologies, for example, unified communications. The ACI licensing is not so bad.
As they are moving to the DNA Essentials, as opposed to the old Cisco One Advantage-type solution, it is adding a little more complexity to the licensing scenarios. But in general, I think that Cisco is moving toward synching everything up and trying to get everything licensed in a similar way, whether its a data center switch or a campus network switch.
I'm fine with where Cisco is moving to.
Which other solutions did I evaluate?
There are a lot of competitors out there. For example, the VMware NSX, which is a pure overlay, it's more network virtualization. The ACI solution is more full-featured, and you get visibility under the underlying overlay. It's very performing, and where we've deployed it for customers they are extremely happy with it. There's a learning curve in deploying it because you do things a little differently, but overall it's a solid solution.
When we lead with a software-defined data center, we lead with Cisco.
What other advice do I have?
I'm a pre-sales engineer, and I help customers blueprint out and design their future data center. We really like this solution. It's a great switch. If there is a data center switch we try to lead with, it's the 9K. I like the Cisco ACI solution in general, that the Nexus 9K is a foundation of. I would certainly recommend it.
If a competitor like VM or NSX tries to position their solution and they try to say, "You don't really have to replace the network or re-design the network", that's not really true because the overlay is only going to be as performant as the underlay. If they deploy that technology on an old-age network that's not deployed in a spine and left topology, then the customer is going to have to do that anyway. The Cisco solution takes all of that into consideration as part of the deployment, so it is an optimized software-defined network when it's deployed for the customer.
Overall, they are a pretty good switch, although it doesn't have some of the features that some of the previous lines have had.
I would rate this solution an eight out of ten.
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner.
A solid, reliable, stable solution with many features and great scalability
Pros and Cons
- "A very solid and reliable solution."
- "The only thing to improve is to continue to get better."
What is our primary use case?
The primary use case is for a secure and reliable connection to our servers. We use Nexus to connect to servers with a large capacity and high throughput. The solution has high availability which is very important for us, and Nexus provides that.
How has it helped my organization?
Nexus provides the ability to visualize the servers and redundant components, like redundant supervisor modules and power supplies. The technologies like VPC (Virtual Port-Channel) really helps us to provide high availability, high throughput, and continuity to our services. That is what we want to achieve to keep our customers happy.
By improving the stability and availability it improves the way the company functions. That is what we were looking for. For very powerful equipment with a lot of throughputs and a lot of features to provide high availability.
What is most valuable?
For the Nexus solution features that we use most are the VDCs (Virtual Device Contexts) which are the virtual domain, and VPC for trunking and aggregation.
What needs improvement?
There is not much that needs to be improved at this stage. If it were possible to gain even more throughput and more port diversity, that can always be a benefit.
For how long have I used the solution?
We have been using the product for as long as I have been with the company.
What do I think about the stability of the solution?
This solution has very good stability. The Nexus platform was selected because it is very stable with a lot of features. We are very happy with the products and the choice.
What do I think about the scalability of the solution?
This solution scales a lot, easily. The 7000s have a huge capacity. The scalability will depend on the model you have, but the 7000s we have are very versatile. We have a lot of ports installed already and we can still add more.
How are customer service and technical support?
I don't know if we used tech support. It could be that everything went so well that we didn't have to. But I don't know.
Which solution did I use previously and why did I switch?
Previously, we had other switches (I don't know exactly which vendors as that was before I was with the company) and those were very a big investment. These new ones are not cheap, but provide more value for the money.
How was the initial setup?
We had to go through different steps and that made the setup a little more complicated than it would have been if we could have deployed in one shot. We had to deploy in a few steps so it took more effort. It doesn't detract from the value of the end product.
What about the implementation team?
We used partners to do the implementation. It was a very good experience. Their technical knowledge of the product was good and they integrated the box quickly. It was fast and good and would have probably taken us a lot more time had we done it on our own.
What was our ROI?
It is a bit expensive to get started. The solution is more expensive than most of the competitors for sure. But in the end, it is stable and provides a service and that meets our performance goals. So the ROI is very good.
Which other solutions did I evaluate?
When I came to the company they had already made their evaluations and the conversion project was already underway. I know they selected this because they felt it was the most stable solution. The route of Nexus had a lot of throughputs but it is also very reliable. We were looking for reliable, scalable technology. The point of making a change was to avoid failures and that is why we chose Nexus.
What other advice do I have?
I rate the solution as a nine out of ten. The 7000 series switches, especially, I would put at nine out of ten. It is only not a ten because there is always room for improvement.
The Nexus platform is very stable. It has a lot of features and does not fail. So if you are looking for performance, stability, and reliability, the Nexus product seems to me to be the best solution.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Cisco Nexus
December 2024
Learn what your peers think about Cisco Nexus. Get advice and tips from experienced pros sharing their opinions. Updated: December 2024.
824,067 professionals have used our research since 2012.
Sr. Principal Engineer at a comms service provider with 1,001-5,000 employees
One of the most stable solutions, with good support from Cisco
Pros and Cons
- "The most valuable features are extensions and recorded scalability."
- "The initial setup wasn't simple or user-friendly."
What is most valuable?
The most valuable features are extensions and recorded scalability.
What needs improvement?
Areas for improvement would be the delivery timeline for the actual model, the length of which means we have to sacrifice a range of models because we can't wait six months for delivery.
For how long have I used the solution?
I've been working with this solution for a few months.
What do I think about the stability of the solution?
In terms of stability, it's so far so good - we haven't faced any big issues at this point.
What do I think about the scalability of the solution?
We want to extend out to other regions, which is very easy to achieve if compared to the typical traditional legacy layer 2 switch, layer 3 routing approach.
How was the initial setup?
The initial setup wasn't simple or user-friendly. We're still in the process of fully deploying - currently, we've been working on it for around three months.
What about the implementation team?
We used the Cisco team to implement, with whom we've had a good experience. We've also had support from HPE, who are very technically strong and able to answer any questions we have on the spot.
What's my experience with pricing, setup cost, and licensing?
I don't like the Smart Licensing models that Cisco uses.
What other advice do I have?
Cisco is one of the most stable solutions, regardless of which model. I would give this solution a rating of eight out of ten.
Which deployment model are you using for this solution?
Private Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Network Manager at a transportation company with 5,001-10,000 employees
Low latency, good performance, and very stable
Pros and Cons
- "Its low latency is most valuable. Its performance is good, and it is also very stable."
- "The operating system needs to be improved. There should be stability in the operating system, and it should not have as many vulnerabilities."
What is our primary use case?
We are using it for the data center. We have its latest version.
What is most valuable?
Its low latency is most valuable. Its performance is good, and it is also very stable.
What needs improvement?
The operating system needs to be improved. There should be stability in the operating system, and it should not have as many vulnerabilities.
It is very expensive. Its price could be better.
For how long have I used the solution?
I have been using this solution for ten years.
What do I think about the stability of the solution?
It is very stable.
What do I think about the scalability of the solution?
It is a really good scalable product. Currently, we have about 50 users. We don't have any plans to increase its usage.
How are customer service and technical support?
I don't have experience with the technical support of Cisco.
Which solution did I use previously and why did I switch?
We didn't use any other solution previously.
How was the initial setup?
Its installation is straightforward. It only takes 15 minutes.
What about the implementation team?
We do it ourselves. We have about four admins for deployment and maintenance.
What's my experience with pricing, setup cost, and licensing?
It is very expensive. Its licensing is on a yearly basis.
Which other solutions did I evaluate?
We didn't evaluate other options.
What other advice do I have?
I would recommend this solution to others. Cisco is a good vendor to work with.
I would rate Cisco Nexus an eight out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Administrator at a security firm with 1,001-5,000 employees
Has good network visibility that enables us to see all of the devices
Pros and Cons
- "The most valuable feature of the solution is network visibility. It becomes the core switch. All of the devices connected route towards it."
- "The initial setup of the Cisco Nexus platform takes a long time. It's a complex system because we have a lot of security layers."
What is our primary use case?
Our primary use case for Cisco Nexus is for our data center and for collaboration with other switches.
How has it helped my organization?
This product has improved the way our organization functions in the way we communicate with data from devices out there. Everything is on the radar if you deploy it on Nexus.
What is most valuable?
The most valuable feature of the solution is network visibility. It touches all of the switches. It becomes the core switch. All of the devices connected to it route towards it and so we're able to see all of the devices.
What do I think about the stability of the solution?
Cisco Nexus is very stable. It's getting better now. The technology is moving to a fast and very innovative switch. It picks up all these new options and integrates them into the device. It's good for our infrastructure.
How are customer service and technical support?
The solution's technical support is very robust. They're able to resolve any issues very quickly. There were not any issues that Cisco could not resolve for us so far.
Which solution did I use previously and why did I switch?
We were using Nexus 6000 and now we're moving towards 9000. We switched because we are doing a cleanup. We are building up our infrastructure from the ground up, adding more new devices, revamping our infrastructure, and revamping our data center. It's just a need because we got too comfortable using our old devices, which are not supportive so we lost our patching. We ourselves were creating security holes. We have a need now for this solution.
How was the initial setup?
The initial setup of the Cisco Nexus platform takes a long time. It's a complex system because we have a lot of security layers.
What about the implementation team?
We used a reseller for the deployment.
Which other solutions did I evaluate?
We also looked at PCM.
What other advice do I have?
On a scale from 1 to 10, I would rate Cisco Nexus a good nine. Cisco is moving to new technology. It's more advanced. Anyone should invest in it. It's good.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Senior Network Engineer at a tech services company with 10,001+ employees
Easy to use, reliable, and operates at high speeds
Pros and Cons
- "It's pretty easy to use and operates at high speed."
- "The initial setup was somewhat complex."
What is our primary use case?
We use Nexus primarily for our data centers.
How has it helped my organization?
It's pretty easy to use and operates at high speed.
What is most valuable?
The most valuable feature for us is its speed capacity.
What needs improvement?
Upgrade and promote catalyst switches to the Nexus, it's a lot faster.
What do I think about the stability of the solution?
As far as we can tell, it's stable.
What do I think about the scalability of the solution?
They're pretty scalable.
Which solution did I use previously and why did I switch?
All of our old stuff was end of life. We used Catalyst 4948 before.
How was the initial setup?
The initial setup was somewhat complex. There were a lot of moving parts and we needed to get everybody going in the right direction. It didn't take very long though.
What about the implementation team?
We used a reseller called Sirius for the deployment. They were pretty good.
Which other solutions did I evaluate?
We didn't look at any other vendors.
What other advice do I have?
I would rate this product as an eight out of ten, because it's a pretty good product. It's stable and reliable.
It's definitely worth it.
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner.
Unified Network Architect at Barry-Wehmiller
A stable and reliable backbone for our data center
Pros and Cons
- "In terms of stability, this solution is rock solid."
- "In the next release of this solution, I would like to see a focus on backplane deployment, so you can stack more."
What is our primary use case?
This solution is the backbone of our data center. It is the fabric to our UCS blade servers.
What needs improvement?
In the next release of this solution, I would like to see a focus on backplane deployment, so you can stack more.
What do I think about the stability of the solution?
In terms of stability, this solution is rock solid. We've had no issues with it.
What do I think about the scalability of the solution?
I would say that to make this solution more scalable, they need to provide a backplane as they do on a lot of their other network infrastructure equipment.
How are customer service and technical support?
Technical support for this solution is excellent.
Which solution did I use previously and why did I switch?
We have been using the Nexus line for more than ten years. I don't remember what the previous model was, but it had good reliability and everybody knew how to use it, so we just upgraded.
How was the initial setup?
The initial setup of this solution was straightforward.
What about the implementation team?
We used InterVision to assist us with the implementation, and they did an outstanding job.
What's my experience with pricing, setup cost, and licensing?
This solution should be made more affordable.
What other advice do I have?
This is a product that I recommend people look at, but it would be nice if it were more affordable.
I would rate this solution an eight out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Network Engineer at Google
Provides SDN for our access layer, but there are lots of bugs that need to be fixed
Pros and Cons
- "The most valuable features are the access layer security, OpenConfig, and OpenFlow."
- "Stability is not really up to the mark."
What is our primary use case?
We use this solution for the access layer of our network.
How has it helped my organization?
This solution is helping us in terms of providing SDN, software-defined networking.
What is most valuable?
The most valuable features are the access layer security, OpenConfig, and OpenFlow.
What needs improvement?
We would like to see OpenConfig covering most of the industry standards. The YANG models, for example, and also support for OpenFlow.
The areas that need improvement are MACsec, OpenConfig, and OpenFlow.
What do I think about the stability of the solution?
Stability is not really up to the mark. There are a lot of bugs in MACsec and OpenFlow.
What do I think about the scalability of the solution?
Scalability is good enough for now, and not really an issue for us.
How are customer service and technical support?
I have not spoken with technical support.
Which solution did I use previously and why did I switch?
We did use another solution prior to this one. We have had a lot of different switches.
How was the initial setup?
The initial setup of this solution is straightforward. For the configuration, we used zero-touch provisioning, so it was straightforward.
What about the implementation team?
We had assistance with the deployment of the solution.
Which other solutions did I evaluate?
We are multi-vendor, so whoever gives us the best product is the one we purchase from.
What other advice do I have?
My advice for anybody who is implementing this solution is to start their testing early, as the features need time to run.
This solution needs a lot more improvement, such as the bugs that need to be fixed.
I would rate this solution a six out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Download our free Cisco Nexus Report and get advice and tips from experienced pros
sharing their opinions.
Updated: December 2024
Popular Comparisons
NETGEAR Switches
Cisco Catalyst Switches
HPE ProCurve
Aruba Instant On Switches
ExtremeSwitching
Alcatel-Lucent OmniSwitch LAN Switches
Cisco FabricPath
Juniper QFabric
Dell PowerSwitch N-Series
Buyer's Guide
Download our free Cisco Nexus Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- When evaluating LAN Switching, what aspect do you think is the most important to look for?
- Compatibility between Dell PowerConnect 6224 and Cisco SG500x (L3 switches)
- What are your recommended Layer 2 and Layer 3 network switches if the main consideration is performance?
- Does anyone have statistics on how often a fire occurs in a computer room?
- What LAN switching solution do you recommend?
- Managed vs Unmanaged Switches: What should a business take into account when choosing?
- Does FiberHome S6800 switch support bi-directional SFP modules and how to enable them?
- Can someone please help me with Fiberhome 40G S6800 Switches?