It was pretty straightforward. The license space deployed in Nexus was about CGS. I used to be a field engineer, so deploying access wasn't really challenging. It was not so hard; it was straightforward.

We have both chassis on-premises. We actually have a hybrid data center. We have on-premises equipment and a Microsoft Azure environment with three subscriptions. It took a week to fully deploy Nexus. 

The setup is straightforward. I'd like to see the firmware and code upgradability to be slightly more intuitive. We are buying a new line of data center products from Cisco.

It takes two fully functional days to deploy the solution. 

The deployment of the solution took two weeks. Three two four engineers were required for the deployment. The maintenance is done by Cisco Partners.

If you know the basics of the requirements of the customer the implementation can be done with no issues. If you are preplanned for the implementation the process will not take long, but if you do not have a plan then it could take some more time.

If you have a large setup with a lot of configuration with many active ports then it could take a few hours to complete the implementation.

The product's initial setup phase is very easy. If a company uses SDN, which is usually used for HCI environments, then the setup phase can get a bit complex.

For deployment, you have to connect the console port to a laptop and then take care of the password setup phase before taking care of the other configurations. If your IP addresses are made local to a VPC network with high availability, you have to configure it through the console.

The solution is deployed on an on-premises model.

The initial setup is not too diffcult. I wouldn't describe it as complex. It's quite straightforward to execute. We simply program it over the CLI, command-line interface, and it's pretty easy to do.

We initially started a couple of years ago with Cisco Nexus. We started the design with 9Ks and 5Ks, we ended up reevaluating the situation features and going with more 2Ks to lower the costs for what we need. 

I rate the ease of setup an eight out of ten. The deployment requires two to three months. It’s a heavy setup. Around three to four people were involved in the setup.

Nexus is straightforward. The time needed to deploy depends on what you're doing and your knowledge of Cisco systems. 

I did not handle any of the initial setup. I can't speak to if it was complex or straightforward. 

The initial setup of this solution was only complex because we didn't have Nexus switches in our data center. We had a multi-vendor data center and the Cisco switches that we did have in there were the Catalyst series. So, it was only complex for us because we were learning a new platform. After we got through the learning phase, it was very simple and easy to set up.

The setup is straightforward. Nexus uses options that our engineers are familiar with. The advantages were that we could leverage the knowledge that we already had.

The setup was very easy, but managing it in operations was very complex. The VLANs are different. We have a network outside and inside of the ASA infrastructure.

It is not possible to provide privileged access to L1 or L2 engineers. If you provide L3 access, there is a chance that they mess up the network by making smaller changes that you don't want. 

Installation is unduly long, with the entire process lasting 16 to 24 hours. 

I did not handle the initial setup myself as I am not an engineer. Someone else handled that part. Therefore, I can't speak to how easy or difficult it might be. My colleague is much more versed in installation protocols. 

The initial setup was straightforward on Cisco's part. Other customers that we work with didn't understand their equipment.

I was not involved in the implementation of our current solution. However, I have set up Nexus switches before and it is is pretty straightforward.

The initial setup was a little bit more complex because it was a new technology that we were adopting. The learning curve was a little steeper. However, the actual deployment was pretty straightforward.

The initial setup of this solution is not very complex. The problem is reliability. We get help from Cisco technical support and Cisco sales, and the deployment has to be coordinated with the Cisco architectural team to get it working on our network. There are a lot of people involved in the deployment, and before anything, it has to be tested.

We have advanced engineering, where they do the testing to make sure that the problems are being captured. If there are any issues then they are sent back to operations before they can deploy.

We found that the initial setup isn't very complex at all. It's rather straightforward.

We only need one person to manage the solution. We technically have two workers, so that we can always have one for redundancy.

The initial setup was straightforward. I'm the senior engineer so I've had to go through my bumps and bruises, but it's pretty much straightforward if you know what you're doing.

The initial setup, if you know what you are doing, is very straightforward. You have to know what a switch is and what routing protocols are, like any other device.

If you are familiar with the IOS it is a little bit easier to translate to NX-OS and use the switch.

The initial setup of the Cisco Nexus series is very straightforward. We didn't have any issues. 

We already had a 5K, 7K, and 2K environment. Going to the 9Ks was straightforward. We were experienced in the Nexus area. It wasn't anything new.

The setup wasn't really complex beyond the fact that we switched to a different platform that has a totally different operating system. It was a bit of a learning curve for us. We weren't heavily into Nexus, so current staff didn't have skills using that iOS screen immediately. But now it's a lesson learned, always very easy to get around after a little while.

I think that the initial setup would be complex for someone that does not know the technology. You do have to know some of the underlying technologies in order to use this solution because it's not something that you can just unbox and start using. There is a learning curve.

The installation was not as easy as it was with Catalyst. The configuration was more difficult.

They have a similar CLI, but different components and features.

We need a team of four to maintain this solution. The team consists of one manager, two technicians, and one installer.

The setup of the solution was easy.

The setup can be easy and complex depending on the product and features we're using. 

The initial setup took place before I joined the company.

The initial setup seemed pretty straightforward. These units were a little different, compared to the Nexus 5K that I came from. Some commands are a little different, but other than that, it was easy to do.

There are a lot of more complex features in the Nexus class that we aren't using today, so maybe it would have been harder if we were using some of those. But, for a basic setup, it was easy enough.

The product's initial setup phase needs one to use the user interface based on Cisco IOS CLI. The user base is the same for Cisco Nexus and Cisco Catalyst. The user interfaces offered by Cisco Nexus and Cisco Catalyst are the same.

The solution can be deployed in two to three years.

The initial setup is easy. It can take a bit of time to test for specific scenarios, but as you become more experienced with configuring for particular services, it can be fast. 

The installation is very easy and it took me approximately 10 minutes to install.

The installations were easy. The time to deploy depends on the model and the size of the product you will be using. But it will definitely take hours. We have ten people in our team to implement and maintain this solution. But it depends on the project. Sometimes we will have 15 people working on it.

I wasn't there at the time, but I know who put it in and it was straightforward.

It took a couple of weeks to deploy.

We have two engineers to maintain this solution.

Setup is fairly straightforward. We are a Cisco shop. This is for a lifecycle upgrade from the previous generations, i.e. 3750/3850 to 9000. It's excellent. We are using the 3700.

Cisco Nexus is straightforward for deployment. If we had to have any kind of hands-on support, we could access them. If you want to you can always pay for someone to come for services. 

We may need to have services on site to be able to help us with deployment. We've used that in the past. For some of this equipment, we have enough experience within our team to be able to deploy it. Then if we run into problems, we can just call in for help.

The initial setup was pretty complex, mostly because of our environment, having to do multi-context. That's where you have a lot of different logical routes that are in one physical device, and it can get kind of complex trying to think about how to set all that up. You really have to whiteboard it out a lot.

The initial setup of this solution is pretty straightforward.

If you came from the Legacy OS, it is easy to access and move around, even though the command lines are a little bit different.

It could be easier to install.

It takes approximately two weeks to deploy.

I have a team of 10 IT people in the IT department to maintain this solution.

The initial setup with the Nexus switch is somewhere in the middle. I hate to call a Nexus switch simple, but at the same time, it's got a lot of platform legacy. You can reapply your knowledge from what you've done before. 

I don't call it complex. I don't call it simple either. Somewhere in the middle.

The initial setup of Cisco Nexus was straightforward. It was good. It wasn't that complex because we already had the 7000. 

Its installation is straightforward. It only takes 15 minutes.

The initial setup was straightforward. It has a simple routing protocol, not very many static routes.

The initial setup of this solution is straightforward. The similarities between the 9K and the older 7K helped with the transition. It didn't complicate things because the functionalities are so similar that it was easy enough to transfer our current configuration over. We were even able to make slight adjustments for improvement.

The initial setup for this solution is a bit complex. Not just anybody without the technical know-how can set it up.

The initial setup of this solution is straightforward.

Something like this always goes through a pre-planning stage. Kicking off the project requires that all of the prerequisites are in place. All of the information is gathered and the final scope is identified. This can be something that is straightforward or very complex.

In the bank that I have been working with, we were building the infrastructure from scratch. This is the reason it has been a straightforward project, rather than a complex one.

The initial setup is easy.

The initial setup is really straightforward and if you use ACI, running on top of the Nexus 9K, you don't really have to do anything but plug the switches in. The software manages all of the policy.

Without ACI, setup requires the use of the command line, which is the same as it's always been.

The initial setup of this solution is straightforward.

The initial setup is easy. For the current setup, we're just dealing with updates already.

My understanding is that the initial setup was pretty straightforward.

The initial setup was pretty straightforward. They had a couple of issues setting up the ports on the switches, but other than that it was pretty good.

The initial setup is straightforward with the right training. Search out there, find a lot of knowledge before you begin.

The initial installation is pretty straightforward, it takes approximately an hour. When you start with the configuration and moving forward from there, which is not only a matter of technical configuration or the key component but the integration into the environment, this can take several hours.

It was straightforward and easy.

The initial setup was rather complex because it was my first time deploying Nexus, and you have to turn on all the features to make them all work and that's something that you don't have in any other Cisco switch. It threw me for a loop. But once you figure out the resources and setting up the VDCs and everything, you're good.

The initial setup of this solution is fairly complex. That's one thing about ACI; it takes a bit to wrap your mind around how it works. It's not overly complicated once you understand the concepts, but coming from somewhere that had never worked with anything like ACI, it was difficult for me, initially, to grasp the complexity of it. Once I did, I realized that it's not actually as complicated as it looks when you first log in.

The initial setup of this solution is complex, but that is expected. You have to put a lot of thought into it.

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.

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.

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.

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. 

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.

The initial setup of this solution was straightforward.

The initial setup of this solution is straightforward. For the configuration, we used zero-touch provisioning, so it was straightforward.

The initial setup is pretty straightforward. There is a pre-configuration wizard that will prompt you whenever you connect any device for the first time. It is pretty simple that way.

Our initial setup was complex because we were installing the other data center equipment at the same time.

The initial setup is complex, but we have a lot of very good documentation.

The initial shttps://www.itcentralstation.c... of the Cisco Nexus platform is straightforward. 

If you know what you're doing, there are a lot of examples for configuration. There are a lot of best practices out there.

This initial setup of this solution was very simple.

The initial setup was straightforward, and the deployment was easy.

The initial setup is always complex. It's a new box, so everything has to be set up because migration is a tricky part. It's not just a plug-and-play device. It's a difficult task.

Installation and deployment of the product are pretty straightforward.

The initial setup was pretty straightforward. The implementors that we would source to assist us knew exactly what they were doing. They were not stalled with questions, so it just worked.

The initial set up was very straightforward. It is easy to follow and we didn't have any obstacles during the implementation.

The initial setup of this solution is fairly straightforward. It is very user-friendly.

The initial setup was straightforward, it was simple.

Cisco Nexus is straightforward to set up. We just pointed our logs to it. It's pretty easy. 

The initial set was fairly straightforward. It's a basic set up that we have. It's not an overly complex network that it's being used in. It was primarily used to support channels.

The installation is straightforward. If you have someone who is certified to do the implementation of Cisco Nexus they can do it quickly. 

All other switches, such as distributed switches and access switches connect to the Cisco Nexus switch. If you have done everything correctly including the sizing, there should not be an issue at the time of installation.

The initial setup was relatively simple.

Cisco Nexus is more complex than your standard Catalyst. It's a whole different environment.

The development and the program configuration is not like what you're used to after doing Catalyst for 20 years. It has a little bit of a learning curve.

Straightforward setup.

The initial setup was very straightforward.

The installation was completely straightforward. We were familiar with previous models so this was the same or very similar.

The initial setup of the Cisco Nexus platform is straightforward. It's complex, but it's not more complex than anything else.

This solution was deployed before I joined the company, so I do not know.

The initial setup of this solution is straightforward.

The initial setup of this solution is straightforward.