Cisco Wireless Reviews

The performance was good. However, most of the issues were due to changes in Cisco versions.

In my last organization, which was a university, we used it for seven years. But in this current organization, we are not using it yet.

It is a stable solution. The performance was good. However, most of the issues were due to changes in Cisco versions. 

There were more than 25,000 students who were using it. It was a good experience for us because Cisco supported us in our workflow. We were facing many problems before Cisco, but after implementing it, we had great functionality. And since then, we haven't changed a single AP.

It was better than other APs in terms of wireless equipment and performance.

It is a straightforward solution. That's why we just required some technical support from a third party. At that time, when we were at the finishing side or during the landing time.

If I make a comparison with Huawei 6.0 with Cisco, Huawei is better. 

The initial setup is straightforward. 

Our in-house team deployed the solution. 

It was expensive. Considering the challenges faced in third-world countries like Pakistan or India, cheaper solutions are preferred. Huawei, for example, is much cheaper compared to Cisco.

We use an annual license model. 

I recommend using Cisco.

Overall, I would rate the solution a seven out of ten. 

Everything I do is generally command line and I use the gooey of the device. I also use a Cisco network assistant to manage the devices. I have a third-party monitor that checks to make sure everything's online — that's it. I don't have any kind of integrated solution where everything is captured within one piece of software.

I prioritize what buildings I can try to upgrade the access points from. I am looking to update my controllers because my controllers are older. They still function fine; I haven't needed to change them yet. I know eventually, they become end-of-life — that's when I'll have to switch them out.

I use Cisco wireless controllers, 2500s. I know they're pretty much going to be end-of-life soon, but I've been using them. They've been solid, I've had them for numerous years. That's what I use to manage those devices. My switches are pretty much a 3650s layer-three and they provide POE over POE plus over 40 access points to be online. It's a big network, but I keep everything in a very basic way. It's easily managed; it's just a very small department.

We're a school district, so every kid has a device. Every teacher has a device and everything is wireless. On a full school day, we can have up to 1,500 devices online at the same time. I try to make sure that everything is connected and that we have enough bandwidth. And if there's an issue that ever comes up, I always try to go there and evaluate it and correct it when needed. With the Cisco product that I've had, I've never had a lot of downtime. So I've been pretty happy with what they provide.

I want to purchase more because I want to update. Wireless standards are changing. You've got to go to WiFi 6, which is 802.11ax. That's in a few years. I don't need to do that yet because our devices won't accommodate that. Everything's still back on 802.11.ac. So there's no point, but in the future, maybe two, three years down the line, when we start getting new devices that accommodate WiFi 6, and I'm going to look for access points to be able to accommodate it as well.

The CleanAir features and the fast transition. They're probably the best things that I enjoy as well as just being able to put multiple SSIDs on those things and being able to segment my network that way. As for authentication, I use a RADIUS server, a third-party RADIUS server, for authentication on the wireless SSIDs.

I have nothing that's outstanding at this point that I think needs to be improved. Cisco has been solid so I don't have much to complain about. It's a little more money, however. I just configure it and it works for years, which is great. That's what I love about it.

I know Cisco has a Meraki brand, which uses a lot of cloud-based technology. I wouldn't mind if Cisco allowed their premiere devices to be able to have that cloud-based support as well, or cloud-based management. That would be a nice feature.

I've been using this solution for over 15 years. 

The stability is fantastic. I can't complain. Not one bit.

Scalability is nice. 

We have SMARTnet contracts with Cisco. On occasion, I've actually called them for technical support, but most of the stuff I just kind of figured out on my own.

The technical support is great. They were very accommodating and if they didn't have the answer, they would get back to me or send me an email with some information that I can refer to. But I've never been left in a lurch where I was waiting an excessively long amount of time. They've always been quick to respond and they've been very courteous as well.

For me, the initial setup is straightforward because I have everything in place. Each VLAN has a wireless controller. When I put Cisco's access point on, dynamically, it basically finds the controller, joins it, and then after joining it, I'll just log in and I'll make any configuration changes that I need to accommodate the area that it's working in.

For me, deployment takes a few days; I've been doing this long enough. If I ever have an issue, I always look it up. 

I pretty much deployed it myself. I try to keep it simple, I don't make things complex. It makes it easier for me to manage it. A couple of times in the past we've had some outside help. A lot of that just had to do with the installation of something because it comes down to timing. Being a very small department, I don't always have the time to be able to put this stuff together. So sometimes it's just helpful to get someone outside to help us out.

It's expensive because a lot of the controls come with licenses. A couple of my controls have 15 or 25 access point licenses. And if it's in a building that I need more, then I have to go out to a vendor and be able to purchase the add-on license and then pop it in. It's not bad putting a license in, it's just the biggest complaint I have about Cisco is the cost.

Right now there's no subscription. That's the other thing I like about it. We buy it and that's it. The only thing I purchase is the SMARTnet that allows me to do software upgrades for my equipment. I'm paying about $6,000 or $7,000 a year in SMARTnet contracts for that support. Basically, I use it more for the software updates that allow me to keep everything up to date.

Like anything in life, if you're familiar with it, it's easy. Can it get complicated? Of course. But I would just say, just do your research. And make sure you count the cost too. There are two things that are in play here; do your research. Once you get on a comfort level, then you can proceed with it. It works. It's pretty solid. And then the cost. Make sure that if you've got to expand that you have the financial flexibility to be able to accommodate any expansion you need, if not, then you may want to turn to another solution that might be a little cheaper.

Overall, on a scale from one to ten, I would give this solution a rating of nine. 

Solve WiFi problems, getting the best WiFi coverage. This was our challenge. The addition of different WLANs by division pushed us to change the configuration of our controller, DHCP and the RADIUS server with NPS.

Between 2011 and 2013, we had a lot of problems with our WiFi, especially with the AD. However, with the addition of the RADIUS, it helped. In 2014, it was made better with the configuration of five new WLANs in FlexConnect mode and our environment improved.

Our number of students increased by 35% (more than 600 students) and we used different devices (Mac OS X, Windows, Chrome OS for grade 4 through grade 12, Android, and iOS), which need a very good roaming sensitivity between access points. The separation of our WiFi for guest, staff, SP staff and two for students, and setting up one IP address for user help to have visibility on our network.

Everything is online NWEA TestTaker, Google classroom and courses. This is why we need to have better WiFi coverage. 

We really have good stability. Because classes and work work well.

Everything in the cloud and the cloud printing are working find. 

Customer service is only good for money. While technical support is more flexible and they go straight as needed.

Yes, the network was horrible and everything was cascading. That's why we use cisco.

The initial setup was straightforward because we only had one WLAN SSID.

And after we went in second step by adding a radius for the certificates only.

Yes, we implemented that through with vendor team. Their level of expertise is very good.

Cisco is good but it expensive. That's why for me there is no better.

We have 10 Cisco 1552E and i ordered 10 more. 

Now, i have the release for 8.0 and 8.5 for my wlc but i stay with 7.4.100 software version.

I will stay with Cisco and see next time Insha ALLAH.

The coverage will be extended and the dead zones will be covered.

For the first configuration, we used apple access points and the HP procurve and D'Link switches.

I noticed with the 1552E access points, the local mode has more coverage than the flexconnect mode.

We used Cisco wireless for medical centers, including remote locations where the regional GMO and RMO are situated. They required real-time connectivity to maintain in-patient reports.

Cisco is one of the leading brands, particularly in the commercial sector. Other brands such as Extreme, cater to different categories at lower levels. Cisco maintains a comprehensive product range across all levels and excels in comparison to other networking sites. They also boast a team of highly qualified professionals, a feature that sets them apart from competitors like Netgear, which lacks such expertise.

The solution is stable.

The solution is scalable but they have a limitation to each and every product based on the price points. If you go beyond that, there is a proxy error.
Five people are using this solution. 

We have good support from Cisco Wireless. We've never encountered any technical issues when going through them because once we follow the deployment plan and its steps, any repairs or detections are usually straightforward. If we deviate from the plan, we might encounter difficulties, as we lack the necessary tools.

The initial setup is straightforward unless it's a manageable task; otherwise, we must configure their own parameters.

For deployment, there are manuals available with instructions for both manual setup and automated setup. Based on these instructions, the technician will proceed to configure the Cisco wireless system using the provided panels.

Most devices are connected wirelessly. Previously, there were few security features, but now security measures are robust. They offer protection, so people trust the technology and use it.

The product is expensive.

They have to have a permanent license. Without a license, we can't access the cloud. There is cloud management available, but it comes with a cost.

These devices are not very complicated. They have a standard but extensive functionality that is really helpful. The standard feature is reliable data connectivity followed by bandwidth. However, the devices are almost the same because they meet the user requirements.

Mostly, government or any corporate clients will prefer a standard product in their infrastructure.

I recommend the solution depending on their budget. If they are willing to opt for a brand with prestige and reliability, then they can choose Cisco. Additionally, for a budget-friendly option, Alibaba is also available. So, if they aim to keep costs within certain limits, they can consider these options. However, government institutions may face constraints due to their funding limitations. In such environments, they may not prioritize premium solutions. Let's delve deeper into this. They might include that particular brand in a closed-end project. However, companies typically prioritize their annual costs and overall expenses.

Overall, I rate the solution a nine to ten out of ten.

When we transitioned to using Cisco Wireless for our network access, it significantly improved our reliability and coverage. Previously, we had sporadic access points and inconsistent configurations, leading to security issues and disruptions. We implemented a policy-based infrastructure, securing our Wi-Fi network and ensuring connectivity to our ERP and email systems.

The most valuable features for network security with Cisco Wireless were the policy enforcement capabilities. Once the approved policy was implemented, it ensured secure access and control over the network, which was crucial for maintaining security standards.       

The deployment of Cisco Wireless is centralized, offering native security features at the access points. Regarding price, it might be considered expensive, but if the features and ease of use are proven effective, it's worth it.

I have been using Cisco Wireless since the least 10 years.

The stability of Cisco Wireless was excellent, with no complaints about downtime.

Regarding scalability, our organization, being a public sector entity, didn't face scalability issues as we were already optimized. There were no plans for expansion or increasing device numbers.

We never had to contact tech support for Cisco Wireless as we didn't encounter any issues requiring assistance. Maintenance services weren't utilized, so I can't comment on their impact. 

Deploying Cisco Wireless was straightforward for us as it was managed by the IT department. We didn't encounter any major issues during deployment. The process involved assessing placement for access points across the campus to ensure seamless coverage. Deployment could be done on-premises if needed.

One piece of advice I'd give is to understand the deployment process thoroughly before starting. It's important to have a solid infrastructure design in place before implementing Cisco Wireless. Regarding cost, while it may seem expensive initially, if the features align with your needs, it's worth considering. 

We primarily use the solution for our handheld devices. We have about 30 most likely that are medical hand-held devices. We do have a lot of wireless devices out there, including carts. We've got Vocera Badges that we use.

The support offered by Cisco is excellent. They are very responsive and knowledgeable.

The functionality of the solution is very good.

The most difficult part of the solution is us juggling everything. There are eight access points that we have to deal with. They have a tendency to age out. After five years, they go off sale. Then, five years after that, that they're out of support. Usually, when you get a new access point, we have to get to a certain version to get everything to work. However, on top of that, the ones we had 10 years ago are no longer functioning. They make it a complicated battle to try to keep your equipment at proper revisions, all at the time. They kind of force you to upgrade now. 

Apple is definitely causing a lot of issues by turning on more security features on its equipment. It is causing more problems on the business side. One is what they call a randomized Mac address that Apple has put out. As far as I know, Cisco doesn't have a fix for that. In other words, it's there to protect the end-user when they're on a guest network or they use randomized Mac addresses. We were trying to implement an employee group that would track the individual via the Mac. Now that it's rotating, we don't have a way to configure that.

I need to figure out how to handle security features that product lines have that offer a non-standard type of security feature that is being turned on constantly by different vendors. iPad also gives us isses. They have it set up so that you don't see the Mac address and the wireless at all. You can't even track your device anymore. I just discovered that last week.

We've been using the solution for about 15 years at this point It's been a good long while.

The solution is pretty solid in terms of stability. Out of a rating of ten, I would give them a nine. It's reliable and doesn't crash or freeze. It's not buggy at all.

I would describe the solution as scalable. If a company needs to grow it out they can do so pretty easily.

We're big fans of technical support. It's one of the solution's big selling features. We've very satisfied with the level of support they provide us.

I also have experience with Aruba. I'd say that Cisco is a bit more complicated to set up.

That said, we went to Cisco from day one - even before they had wireless controllers. Cisco is our go-to solution.

The initial setup is probably a little bit more complex than Aruba from what I've seen so far. It's not simple per se.

I don't handle the pricing. I don't have it in front of me. I'm not sure what the monthly costs are for our organization.

We're just a customer.

The solution is fairly up-to-date, however, we aren't using the most recent version of the solution right now.

Overall, I'd rate the solution nine out of ten. We've used it for years and it's worked quite well for us with very little issues to speak of.

We have to set up the whole solution. The wireless network is a big part of the solution because of the mobility within the hospital. Doctors use their smartphones to access the system, so they need very stable and strong wireless connectivity. 

The hospital layout means a doctor might be quite far from the room, and there could potentially be a significant signal problem. With Cisco, we don't have this problem.

Cisco Wireless improves mobility and flexibility. The only case we are working on is with hospitals, focusing on the mobility of doctors within the hospital.

Everywhere, doctors need to be connected to the network, even within the operating theater, patient rooms, and even the basement, like the radiology department. As far as the solution goes, the coverage is usually very comprehensive.

I would rate the impact of the implementation of Cisco Wireless on the overall IT infrastructure and user experience a seven out of ten, with ten being very positive impact. 

It offers good security, coverage, and stability. I like these aspects.

For pricing, Cisco has to make an effort, or Cisco has to improve the distribution channel.

It means when I send an email or when I have a complaint, for example, there is a Cisco distributor, and it's in competition with others. 

I have to escalate this case to Cisco, and it will help us to improve our business with Cisco and prevent us from going to other solutions like Aruba or now Fortinet. We have some good switches and access point controllers now.

So, sometimes, when we find some problems with Cisco's distribution channel, we switch our customers to other brands.

I would rate the stability a nine out of ten. Within our customers, the hospital infrastructure is established from the first day, and it's still stable. 

The hospital was 100 beds and still is, for ten years. So, we didn't really experience the scalability of this kind of solution.

So, I don't have experience with the scalability of the solution. We usually have medium-sized businesses. We work ith hospitals that have 100 to 200 beds. This is our market. We have the same kind of clients. 

The initial setup was difficult the first time, but now it's easy for us.

We have to test the coverage area; the configuration will take us one day. But to test the coverage area, it will take maybe ten days to two weeks.

We set up the whole network, including the privileged network, wireless network, and security with firewalling.

It is an expensive product. I would rate the pricing a nine out of ten, with ten being expensive. 

Overall, I would rate the solution a nine out of ten. 

I would recommend using it because of my good experience with it. They are stable and secure. All good experiences.

We as a system integrators provide wireless solution for big enterprise and PSU's. This solution primarily focuses on giving secured wireless access to employees and internet access to guests. 

We have seen that Our organization and many other organization for whom we have provided wireless solution have improved using this product because it helps enhance user experience. We use video communication a lot, like Skype, lync, etc and earlier we used to get a lot of jitters and faced lot of issues during voice or video calls. Presently the technology as moved to 802.11ac wave 2 which gives more bandwidth to the end users connecting to the 5ghz band.

From a technical point of view, I think the major difference in feature set has been the granular application visibility and control that an wireless administrator has over the wireless network. The other valuable point would the ease with which one can give secured access to anyone coming with a laptop, mobile , tabs etc..

I think the technology is already at a level where it's good enough. In some ways, it's better than wired. But there is always a backlash when it comes to lack of accessibility. It's not the solution itself, as much as how it's deployed.

The product could be improved with interference reduction. Because wireless frequency interferes with microwave or Bluetooth technologies, which are hindrances to a genuine wireless connection. A lot of users still use legacy wireless adapters and they do not experience the speed that they could get using the latest technologies. The number of devices on the market makes wireless communications complex. If the problem of interference could be reduced it would further improve utility and ease of system design.

The latest version of this technology is stable. It is stable but, the devices that are accessing the network are very dynamic. It is not as much the solution that is unstable as that the devices accessing it are constantly changing.

The scalability of the solution is excellent. Wireless used to be a non-critical part of the network earlier and it started with speeds as low as 11 Mbps. Now you're seeing the speeds of five gigabits with Wifi 6. Wireless is an innovative technology, and it has been changing. Scaling is something we need to do very frequently to meet the demands for higher speeds, higher bandwidth, and higher coverages. 

You need wireless expertise during the design phase, but I think a typical network engineer with fundamental knowledge can take care of day to day operations quiet easily. Once it is deployed and implemented, the operational costs are very low.

We get help from Cisco support whenever it is required. The level of service is excellent.

We definitely tried many solutions before going mainly with Cisco Wireless, including Ruckus and Aruba.

The major reason to go with cisco has been the support system. Nobody can beat Cisco when it comes to their support infrastructure and the SLA (Service Level Agreement) that they provide. The number of engineers who are available who are Cisco certified is much greater than those certified in Aruba or Ruckus. So anybody who deploys Cisco can easily get a Cisco Certified Engineer to take care of there wireless network.

We do the entire deployment as well as the design. It takes around an average 20 days to complete the entire deployment for a 1000-user network.

Cisco support has been a major help because right from the beginning Cisco support strength and the technical licensing centers played a major part in the success of deploying in the Enterprise Network. People buy it because of this. There are other, cheaper products available with a lifetime guarantee but without any support. Cisco took care of the critical issues whenever we needed them to. 

We are system integrators and we do have our own team who design and implement wireless solution..

We have definitely received a return on our investment because the major part of any wireless solution is the quality of connectivity. When you have good connectivity, you can access the environment, go inside the network and access production resources from a mobile device sitting basically anywhere. 

Cisco licensing is usually provided for 1 year, 3 years, or 5 years. You can get a hardware SLA or hardware and software SLA for a period of 5 years. Longer terms of SLA influences  the pricing.

License pricing also depends on the features that are being used.

Though cisco is our first choice, we have evaluated other options like Aruba and Ruckus.

Whatever solution used, the design of the wireless network is the most important part of how well it works. I would plan on putting in 60% of the effort to the design and 40% to the deployment. In the designing phase, you must actually get into the network, look for interference issues, create proper wireless heat maps and place the wireless network connection points in the exact location where it is required. 

I would rate it an eight out of ten.