Cisco Wireless Reviews

I use Cisco Wireless for education as I am managing a school. We use it for connectivity for students and teachers. It is an international private school. This is why we have to get high speed connectivity.

I have not used the solution for enough time to give a full evaluation but I will tell you the estimate - I estimate that it will reduce the time for a student to do their work and reduce the time for copying and transferring data through the local network. That's the reason that what we needed to get this hardware.

The features that I have found most valuable with Cisco Wireless is that the average connectivity for this WIFI access point is 2.5 gigabytes. That's the highest technology and highest connectivity. They started using the new technology and WIFI to get you a faster connectivity. All companies jumped from Wave 2 to WIFI 6 for the high speed.

I selected Cisco Wireless because I found they improved everything, but there is still a gap in Cisco reporting. It did not invest more into giving accurate reports. That's the missing thing in the solution. 

In the next release, they should add a better reporting feature. The reporting will tell you if you have a problem. That will make the diagnostics easier. Although, we have not had problems that required a lot of diagnostics.

I just implemented the Cisco Wireless WiFi 6 last weekend.

I would be liar if I answered if it is stable because it has only been up for two days.

But the Cisco solution overall, and Cisco Wireless generally, are 100% stable.

It is scalable. We have around 2000 students and teachers using it because we are an educational institution.

I'm the IT manager. My role as IT manager is managing the whole technology results.

We require three staff people for deployment and maintenance of Cisco Wireless - a network administrator and two IT specialists.

They are good.

I have been using the Cisco solution since 2011.

The initial setup right now of the access points to the WIFI, and to the switches are managed by FortiGate firewall and the wireless controller. So the routing is through the FortiGate firewall and the activity is through the Cisco switches managed through the wireless controller.

The plan was to upgrade the firewall and remove the old non-supported access point from the system because I used hybrid between these two and WIFI 6. Because this hardware is very expensive to get all at one time, we have a plan to replace all access points for these.

The development takes three days. But the delivery takes a long time. They take a lot of time to deliver hardware. 

We implemented with a Cisco partner. They were experts. They did all they were supposed to do and it was active within the time as planned.

Two days is not enough to see ROI.

But for the previous experience, yes, I can see ROI. The old access points stayed with us since 2015. I have some working since 2017. I removed some from the system, so I have all 2017 access points still working. That is quite a reliable system.

Any people who are looking to get a stable solution with and long life and long time connectivity should go with Cisco.

The big lesson is that when you invest in expensive hardware, you have to understand that it should be a trusted hardware to give you stability and to make sure that your investment will be returned soon. The cost of implementation and downtime with Cisco are less than with other solutions.

On a scale of one to ten, I would give Cisco Wireless a nine.

We work at a courthouse, however, we manage the data for the entire county. We have them at the Sheriff's office. They use them in commissary purchases, which is a separate SSI and separate VLAN. That's to segregate wireless traffic for different groups of people per their needs. 

We have lawyers that maybe need to reach back into the network and access their documents when they take a laptop to the courtroom with them. And so through that, we've done some radius authentication. Therefore, it's not just an SSI ID. They actually have to log in with credentials as well. 

Then, we have a guest SSID just for general public access, and that's basically running wide open. We do have a simple password audit, however, everybody knows it, and that's separated by VLAN as well and run through Palo Alto. We also have a whole different SSID for patrol units for the Sheriff's office, where they upload car videos and update their car computers wirelessly. We use it broadly. 

The solution has let us get network access to more people in different locations where wires aren't feasible - like in a garage or for the Sheriff's office uploads in courtrooms. In some of these courtrooms, you can't run additional wire due to the fact that they're historical buildings. You have to have wireless. Also, you have lawyers walking around and you don't want them tripping over stuff. It's useful in every aspect of getting public access - even for when there are events in the square, across from the courthouse. It's basically helped us better serve everybody and provided them with network access.

It always runs, and it's very reliable in terms of performance. They are very, very robust, very rugged, and can handle indoor or outdoor coverage. We typically don't have too many problems with the hardware.

The wireless LAN controllers at the time when we started rolling out, we went with it simply due to the fact that everything else worked that was Cisco. We figured, if everything else works and we're satisfied with it, let's go that route. However, now people want more access points and more spots. And if you give everybody coverage, the cost is crazy high. You can either say, "No, we can't," or you can go with the cheaper product, even slightly cheaper, plus you get more APs out there for more coverage.

At least with the WLC 2500 that we've been using, you can't take just the stock AP from them. You have to use lightweight firmware. You turn it into a lightweight AP and then you can join it to, or provision it to, the wireless controller, which should be automatic. In most cases, it works pretty well, however, it's still not there yet, as far as plugging it into this network that's going to tunnel back to the controller. I would say it works 7 out of 10 times. For the price, it should be a 10 out of 10. Especially with Cisco running an entire Cisco network with CDP all over the place, there should be no reason it doesn't tunnel back every single time. And yet, there are a few times where it doesn't.

It got to the point where, when I prevent in APs, I just take them directly to the switch that the controller is plugged into and provision them there instead of just plugging them in like you should be able to. 

The software on offer is not great. Cisco lacks in software updates, surprisingly. They don't update their firmware too much for the controller. This is not something you want to be done constantly as it does make downtime, however, I would like to see them more than once a year. Unless there's a critical flaw, or you're running an early release. They're their main releases, I want to say year after year, it's been maybe once a year, and then you have to push it out to all your APs. 

Their software's really clunky. It's not very user-friendly, which you can see that as a good thing and a bad thing. We should learn this stuff, but at the same time, it shouldn't be overly difficult. You shouldn't have your options hidden in menus. You shouldn't have to go 25 minutes deep to get to some security options for a specific SSID. 

Also the way the group their security settings is a little bit backward to me. It's not done by SSID. There's just a security tab. Then, you have to link back and forth through that. However, that's something that you're going to fight with through every controller, every different type of device. We all wish they were organized differently. 

We originally started using the solution in 2014.

We had one before then as well. Since we've gone wireless, or implemented wireless throughout the buildings here, we've always used Cisco. This is just a Cisco shop. 

The solution is extremely stable. There are no bugs or glitches. It doesn't crash or freeze. It's reliable. 

The one issue we did have was with their mesh radios. I'm not sure that it was with the radio itself, the software in the radio. They run two different firmware. One is autonomous firmware, which they use with their AP line and then lightweight APs. With the autonomous one, there's no consistency there. For the indoor APs, you'll have lightweight firmware that you need on them. And then for the outdoor mesh radios, they're not fully autonomous, yet you have to have the autonomous software on them for the mesh feature to function. That's a little bit convoluted and I kind of wished that would just have it one way or the other.

The solution scales easily.

The number of users varies. Some days we have court cases and then you have jurors, lawyers, the media people. It varies widely. I would say on average, we have possibly 200 people a day on a slow day using it. And then on an extremely busy day, it could double that.

We use the solution quite extensively.

We do plan to increase usage, however, it won't necessarily be with this product. We'll probably like to go with a different product based on price and licensing.

Technical support is 10 out of 10. Cisco tech support is one of the best supports I've ever dealt with.

The initial setup was very straightforward. As we have added SSIDs, when we have had a hardware failure, the re-setup, for instance, is a bit more involved. When the controller itself was acting kind of finicky, we did an overnight request and got one in. Re-uploading that configuration was not as easy if that makes sense. If you're setting up a brand new device, it's very easy, very straightforward. If you're trying to restore from a backup configuration, it's not as easy. We ended up actually just resetting it up from scratch.

The deployment itself likely took three hours.

We had some bugs to work out after that, however, the majority of it was up and running within three hours.

For maintenance, you only need one person (a network admin) and then a backup person, just in case that person is on vacation or something.

We handled the setup all in-house. We do have their tech support. At one point, we did get tech on the phone and were working with them. It basically came down to firmware. The one they shipped us could not downgrade its firmware to the firmware we were running on. There was no good way to make it upload the config from an older firmware. They wanted the same firmware restorations. That was kind of a pain, however, we just ended up manually going through and resetting everything, which was not too terrible.

Cisco's APs are licensed and you need to buy them. Basically, for every AP, you have to have a license. Some of the other devices do it so that they support X amount and you can buy the licenses for zero to 20, 20 to 40, et cetera, and it's a little bit more affordable. That's kind of why I was trending towards Ruckus. They handle their licensing a little bit differently. 

Every time somebody asks "How much is a wireless access point? We need wireless in this room." Well, then you tell them the cost and mention "Oh yeah, and there's a license." It's expensive.

Users purchase each AP, and that's until the end of that product's life. If you break it down over a year, it's fairly affordable. However, nobody replaces one AP, we replace them all typically at the same time. Unless one dies or they need one expanded, as far as specific costs go, it's different for indoor and outdoor ones. It might be around $100 for a license. The internal ones are far cheaper than that. 

We had looked at Meraki before, however, the cost is just astronomical. We're a local government, so there's no money. The cost of Cisco wireless controllers has always been kind of clunky. I had heard a lot of good things about Aruba, and then I heard they were bought out by HP, however, it seems like it's still good. I was leaning more towards Ruckus based on just how it handles traffic and handles the guest VLANs and that it can do SSI de-scheduling. I still need to go back and do an in-depth read on the Ruckus option. I am leaning towards that one, even though it seems like it's a close tie.

I also looked at Ubiquity, however, from what I've read, their hardware is not really up to par when you hit saturation, and on certain days of the week here, we definitely have saturated APs due to the fact that we have court cases. You can go from the usual 10 people on an AP to possibly 40 plus people, all trying to check their internet over the wireless. It gets kind of crazy on those days.

We're just a customer and an end-user.

We use the 2500 wireless controller and all the APs that go with it. 

We have Cisco switches and routers as well. We were using Cisco firewalls up until about three years ago. And then we switched to Palo Alto. As far as switching goes, still happy with their switches. They're extremely pricey, however, they last forever, and they meet a lot of government requirements that we have.

I'd recommend the solution I wouldn't hesitate to do install it if the company can afford it.

I would rate the solution at an eight out of ten for its ease of setup, ease of scalability, and robustness.

We provide solutions to a university and Cisco Wireless is one of them. 

The solution offers central management, reliability, and signal, ensures the bandwidth, and segregates the network. It also maintains the authentication process in the compass solution, which is good regarding multiple software.

The solution should introduce natural language troubleshooting processes. It will identify possible problems or errors due to the symptoms.

The product is stable.

I rate the solution’s stability a nine out of ten.

The solution is good for expansion. We cater the solution to enterprise businesses.

I rate the solution’s scalability a seven out of ten.

Sometimes, the solution has lingering issues with the other dependencies.

Neutral

The initial setup is a bit complex. It depends on the project size and requirements. It takes almost a day, excluding the infrastructure part.

I rate the initial setup an eight out of ten, where one is difficult and ten is easy.

Cisco’s pricing is top ranking in the market and the competition out of 300 products. It is moderate. Cisco Wireless has a complex licensing model. While some features are offered without a license for integration and central management, others require licensing for activation. SmartNet support and other tools are also necessary, adding to the complexity. Segregating the costs into one-time payments for integration licenses and separate payments for SmartNet could reduce overall costs.

We recommend Cisco for enterprise customers because they are already invested in Cisco solutions. Once the setup is complete, they can utilize existing accessories. Additionally, Cisco provides fantastic support and robust product features, making it a reliable, high-performance solution for network needs.

Overall, I rate the solution an eight out of ten.

We use the product for user access. 

The tool's most valuable features are security, flexibility, user activity, and high bandwidth. 

Cisco Wireless needs to improve compatibility with Apple devices. Its deployment should also be made easier. It should also reduce the complexity around security. 

I have been using the product for more than ten years. 

I rate the product's stability an eight out of ten. 

I rate Cisco Wireless' scalability a nine out of ten. My company has 5000 users. 

I rate the tool's deployment a seven out of ten. We encounter challenges setting up attributed domain groups, country portals, and consoles. It takes six months to complete. Initially, our process involves identifying the requirements, evaluating different brands, and selecting a suitable solution. Once we finalize the details, we will create a digital deployment plan. The actual deployment starts based on this plan.

Regarding the deployment team, we require four engineers for the deployment process. You need security engineers to handle the deployment. 

I rate the tool's pricing a seven out of ten. 

We evaluated Aruba and Fortinet products before choosing the solution. We chose it because of the stability and local support. 

Reviewing the security requirements is essential because security is complex and requires detailed policies to control access to the network environment. I rate the product an eight out of ten. 

Our primary use case is for a guest portal type of scenario where different types of users can connect. We use SAML authentication for that. We are customers of Cisco via a third-party vendor and I'm a network specialist.

It's valuable to us that creating policies is simple. We use Cisco ISE and it works well with the product. 

I've found that the media stream and Mojo settings are not sufficiently supported. The other issue we have is that when the access point goes down, we don't get any indication of the reason. This has to be fine-tuned so that a trigger is sent to the Cisco Server or any third-party server, and we get the alerts. I'd really like to see bug-free software.

I've been using this solution for over a year. 

Stability could be improved but it's not bad. 

The solution is easy to scale and if you have the latest wireless controller, you can really extend the coverage and extend the APs.

Technical support is awesome, we're very satisfied. 

I know that Aruba is better than Cisco, they really need to improve things. 

We carried out the implementation ourselves and it was quite straightforward. It took around six to eight months to implement the entire solution, install access points, configure and fine-tune. There's no specific maintenance required, it's mostly the operational aspect, upgrading software, and hardware support. We currently have around 6,000 users. 

Cisco is a bit pricey compared to other vendors like Ruckus which have pretty decent pricing. If a customer asks me for a cost-effective solution, I may go with Huawei but if it's in the enterprise dev environment, then I'd go with Cisco, Aruba, or Ruckus as a third choice.

I rate this solution eight out of 10. 

One of the main advantages of Cisco Wireless is its DNAT compatibility. When we have dynamic segmentation, or the DNAT enabled on the LAN, Cisco Access Point integrates with the DNAT architecture. Aruba Switches cannot integrate with the Cisco DNAT architecture. However, if we have an all-Aruba framework in offices where we have implemented this with the complete dynamic segmentation using Aruba Dynamic Segmentation, only Aruba AP works.

Cisco can't block specific sites on the internet like Aruba, so we're in the process of replacing them. We have already placed lots of orders with Aruba. Aruba has the ClearPass NAT solution, and Cisco has its ISE policy engine. Cisco won't work with any other vendors. That is a significant problem with Cisco. It can't integrate with ClearPass. We already tried this in a POC for ClearPass. Aruba is becoming integrated with ISE, but Cisco will not integrate with ClearPass.

We've been using Cisco Wireless for more than 10 years.

Cisco Wireless has not been that stable. In the past, Cisco Wireless could handle only a small number of users per access point. Once the number of users per access point increases beyond 10 or 15, you start facing disconnection issues with the users, and the performance slows. This has been my experience in the past five years, but Cisco has made a lot of improvements in their access points over the past two years.

Now it's a multi-band network, so they have improved on that front. The connections are stable. The performance still degrades if the number of users per access point increases, but now it's 20 or 30 users on the same access point. So you have to plan your access point design and placement so no more than 20 users will be connected to one access point.

Cisco Wireless is scalable, but that depends on the definition of "scalable." I can deploy it at two offices and I can scale it to 200 offices. However, when you integrate the access point and the controller with the DNAT across multiple sites, you need a DNAT cluster, which is a costly solution. Every site has a controller, and a DNAT cluster is not a good option in a global framework. It's okay for a small office or a few offices. But when you're talking about 500 offices, the cost becomes enormous. We're using Cisco Wireless extensively right now because none of our offices are on the wired network, and we have roughly 25,000 users.

Technical support is okay. It takes some time to resolve a complex issue. But if it's a known issue, it gets settled within the time limit set by the SLA.

We have a mix of Cisco and Aruba. Aruba hardware is superior to Cisco's. Cisco cannot come close to matching Aruba in throughput, performance, and coverage area. Cisco's main advantage is integration with ISE because many organizations can't shift the NAT or the authentication part. It's very difficult or not advisable to do it.

The Access Point configuration is plug-and-play, but the controller configuration is complex. You need some skilled people to configure Cisco Wireless. The deployment strategy is it deploy the controllers initially and upgrade them over time. Our last upgrade was three years ago when Cisco released its latest OS. The DNAT integration is ongoing. 

We have our in-house network team, but we also get support from Cisco and Aruba. We have vendor support in addition to our own set of team members who are working on the deployment.

Cisco Wireless is complex, and it's not cost-effective.

I rate Cisco Wireless eight out of 10. They still need to improve in a lot of areas. For example, Cisco needs to raise the throughput. At the same time, they've made a lot of advancements in the past two years. The access points are performing better. It's stable. They've added a multi-gig port, which is increasing the throughput of the users. 

In our warehouse, we use a wireless solution for every job we have there. For example, we have dispatch trucks or picking. They call it picking when you choose the products and go to the warehouse site of our clients. All of that operation is wireless.

They use a Vocollect solution for warehouse sites. If we don't have wireless, they don't have Vocollect and without it, they don't know how to offer dispatch for the trucks.

For plants, we have solutions for tablets. The tablets manage all of our equipment, our principal machines. That's why we need the wireless option that Cisco provides.

We use the solution for connectivity for our employees.

The deep knowledge of Cisco is its most valuable aspect. The Wireless Cisco solution has been in development for many years. That gives users trust in the solution. 

There are many engineers that know how to operate Cisco. If I choose another vendor or another solution, I have to be very careful about how much knowledge is actually there in the market. For example, if I have a problem, how easy is it to find someone, an expert, in order to do a solution for a problem? That's why we choose Cisco. There's deep knowledge there that doesn't exist elsewhere. Also, Cisco has commercial representatives in our country, in our city. It's easy to communicate with Cisco directly. With others, it's not that easy.

The integration is great. For all Cisco environments, the integration is easy. W have a lot of Cisco products. The integration between them all is simple. That's why the other company we work for or we as a team choose Cisco as a vendor.

The initial setup is easy.

We've found the solution to be scalable.

The price needs improvement. The bad thing about Cisco is about price. Nowadays it's all about delays in equipment as well. Any hardware is delayed. 

There's a delay in equipment that comes to Columbia, to our country, and that lasts almost six months. I have a project in which we have to wait for six months, seven months in order to get the equipment. That is the bad aspect nowadays.

The company I work for has been using Cisco for 20 to 25 years.

My company has so many brands and so many plants and factories. We are a multi-Latina company. We have brands in Chile, Argentina, Ecuador, Colombia, Dominican Republic, et cetera. Our inventory of Cisco equipment is almost 300 to 500 devices. There are many series there. The new branch has 91 or 92 Wireless, however, they also have old series such as the 12,000 series. It's old, too old, however, this year we are planning to fix that.

It's so scalable. For example, if I update the series, I don't have to change all my environment. I only have to change the parts that I need.

We have 5,000 employees on the product. All of them use wireless. For example, we use wireless for daily operations of the factory. 

We do plan to increase usage. This year we are planning to open a new warehouse. They are going to need a Cisco solution. Even at this moment, we have the design, or we are checking the design. We maybe will buy the solution in next month or two. That is the roadmap.

Technical support is very helpful. It's easy to reach them. We are satisfied with the level of service. 

We just have Cisco solutions. We don't have any other vendors in our network.

The initial setup is simple.

The knowledge is easy to locate. You need to click or look for a special website. You have so much information on the cloud and so much information, documents, et cetera. That's why developing a project with Cisco is easy.

If I have a big project it could take maybe four to five months, however, that's for a big project.

For deployment, maybe for a big project, we have ten people. For the operations, for support solutions, my team is comprised of five people. That's five engineers that make up my personal team.

I contract a partner to help with implementation. If I have a big project, I contract the design. 

As the first step, we contract the design. For the design, sometimes Cisco gives us the special engineers. However, in other cases, we contract the design. That design comes with a WiFi heat design. They have visual material.

The other step is to contract the solution with a partner. We send to the market an RFP, a request in order to have the best price in the market and the best partner in the market. The other step is to implement or to develop the project.

The licensing is expensive. The cost of licenses is expensive, as are other solutions. When we have a project, we have to clarify to our financial staff why we chose Cisco, as there are other, cheaper solutions. The cost of equipment is expensive.

For example, for new brand equipment, Cisco Wireless equipment, it costs $1,500 for one piece of equipment. That includes licenses, installation, and equipment. 

We looked at Meraki, however, we decided our organization was a bit too large for that particular solution. We prefer to have on-premises options.

I also test other solutions, for example, Aruba or Ubiquiti.

I am an end-user. I work for a manufacturing company. I manage the networking solution for that company.

At this moment, we are choosing Cisco as a continuous technology. Nowadays just we have our roadmap. Our plan for the next two months is to open a new branch office, and no more.

I'd rate this solution at a ten out of ten.

We have a business center with about 600 tenants. We use Cisco wireless throughout our business center. We have a coverage shortfall for WiFi access for our customers.

We have 600 users in our building spread between roughly 20 to 25 different companies. We all have different needs and different security issues. 

The flexibility on the controllers isn't that great.

We always have to inject a third-party if we want to do things on social media, etc. If you have a guest network, you can make some connections with guest networks within your social media account — that's not the case with the standard solution from Cisco. You always have to get a third-party solution.

Our solution is prehistoric — it's seven years old. Still, they have perfectly served all of our needs. But now the market is changing. Because of COVID-19, more and more people are using wireless solutions. They're using Teams. They have bandwidth issues. That's a limitation with Cisco — you have to change all your APs again.

There's no way to upgrade it to make it faster and better, overall. The only thing you can do is add more access points, but then you have to license each access point. 

This solution is highly stable. We have only had one issue in seven years. We had one issue with our controllers. We upgraded our controllers and there was a little bug, but that was solved very quickly.

Also, we've never experienced any downtime.

It's scalable, but there is a break-level replacement cost.

We expanded seven years ago. If we want to expand further, we'll have to replace our controllers and add new access points. So expandable? Yes, but it's pricey.

Cisco has a great support team. We pay a lot for support, but they are very accurate. They are very fast. They are very good and they have great knowledge.

We have a very good partner for technical support. We have a contract with them. The support is always great but it's limited to just one product.  

The initial setup is fairly complex because we have a lot of VLANs in order to enhance our customers' user experience.

This solution is expensive, but you get value for your money.

Cisco is not cheap. That's actually an understatement. Our Cisco partners want us to partner with Cisco Meraki solutions because their cloud platform is monthly-based. We pay roughly $2,000 a year with our current subscription.

I would recommend this solution to other users. If you're interested in Cisco, Meraki is a good choice, but they are lagging a little bit behind in terms of technology. If you compare Aruba with Mist, Mist has the most advanced wireless solutions that you can possibly get at the moment.

After over seven years of use, overall, on a scale from one to ten, I would give this solution a rating of seven.