1. Home
  2. Network Operating Systems
  3. Cisco NX-OS Reviews
  4. User Review of Cisco NX-OS
NX-OS is Good but not Great
September 10, 2020

NX-OS is Good but not Great

Ramesh K | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Overall Satisfaction with Cisco NX-OS

We are using the NX-OS in our data center across our organization. We use mostly use it to support layer2 requirements within the data center. We are facing memory leak issues and had to do software upgrades very frequently.
  • Cisco NX-OS is very simple to use and user friendly CLI
  • NX-OS has a modular config so easy to configure.
  • NX-OS comes up with copp policy where we can define most of our system level ontrols instead of defining separate ACLs
  • Memory leak issue is one of the major issues that need to be solved.
  • Burst traffic handling needs improvement.
  • The buffer size is too small and module-level issues will be repetitive.
  • It is serving the purpose from last few years.
  • Need to spend multiple manpower cycles to do the reload/code upgrades.
  • We need to request for downtime from the user to do the reload/code upgrades.
Our network is a multi-vendor network design so we have to integrate the Cisco NX-OS switches into our code devices from Juniper. We have not observed any compatibility issues in integration. Overall NX-OS switches are good to integrate with other vendor devices since it supports multiple features like lldp and all active routing protocols.
Nexus is supporting automation for deployment and troubleshooting very well, this is one of the major positive side. Nexus does support the copp policy which gives more control.
Security-wise Nexus is doing a pretty decent job and we have come across situations only
once or twice where we had to do code upgrade due to vulnerability issues.
We use Nexus 3Ks for switching in data centers where we host with 1G and uplink is 10G. This may not be appropriate where we need more host port throughput. NX-OS has a very simple design and CLI to use, but we need to have either reloads or code upgrades to fix the memory leak issues.