Cisco Ethernet Switches Reviews

We don't work with the latest version, which is why I am currently conducting research. We wish to see if we can move from the existing solution to an upgrade. We have been using 2960 switches for a very long time, say... five, six or seven years, and they have reached the end of their lives, which is why I proposed a change. 

When it comes to switching routing, we have no doubts about Cisco. It's a robust solution. One cannot find latency, such as attenuations, even within our cables. It's really stable. In contrast, some other switches can switch over, but we found Cisco Ethernet Switches to be stable and robust, even taking into account Africa's infrastructure.

I would like for the solution to have more security features and be more user-friendly. It should have a GUI graphical user interface which would allow the person to interact with it. The look and feel should be addressed. As people are in the process of moving away from CLI, it should be something that anybody can manage.

I have been using Cisco Ethernet Switches for more than 10 years.

the solution is really stable. 

We may switch to another solution, although this will depend on the cost. The dollar has multiplied five times over the past ten years, which means that certain things are not affordable in dollars at the moment. I am not saying that the best product would be be cost prohibitive for us. This said, one's budget and the cost of materials must be weighed. 

Cisco is consistently at the top of its game when it comes to quickly routing our security. Other solutions with which I have experience are less so, such as concern identity service engines. The problem with this is the support. Switches are appliances that, once put in place, hardly require support. However, this is needed for firewalls, routers and other security appliances, but is hard to come by in Nigeria

I'm not saying that I am dissatisfied with Cisco's technical support, but I am looking at what is involved in reaching it and having the app escalated to the second party. 

Generally speaking, it is not possible to reach second-line support. One would usually reach the original equipment manufacturer at first-line support. Generally speaking, they would prefer not to escalate an issue. Take, for example, the Cisco security appliance we currently have deployed. It must be unplugged and we are not benefiting from the support that we need. 

The solution can be comparatively cheaper. 

I am currently in the process of comparing the solution with that of Huwei switches, which I know can be cheaper, taking into account the exchange rate with Yuan and the dollar increase in Nigeria. 

Although I am not looking for a cheaper solution, I am doing so for one that is affordable. 

There are between 2,000 and 2,500 people making use of the solution in our company.

I rate Cisco Ethernet Switches as a nine out of ten. 

We use Cisco Ethernet Switches to interconnect the 20 to 25 servers and workstations in our control room.

We use Cisco Ethernet Switches to configure VLANs in the VPN network. We need to put some subsystems in the VLAN so that other terminals will not access these equipment. We do all these configurations on the solution. The solution is easy to configure.

The solution's reliability should be improved. We see that some ports must be reset when in the hang mode. Only after a reset can we make use of those ports. There could be some internal or external reasons for the hang. We are looking for an improved reliability aspect.

I have worked with Cisco Ethernet Switches for over 20 years as an end user.

There are no issues with the solution’s stability.

Our department is quite big. About 50 engineers are accessing different nodes.

The solution’s customer support service is quite good.

The solution is easy to install. They're all plugin modules.

One engineer can complete the solution’s deployment within one to one and a half hours. We are a government department. Our engineers buy the equipment, follow the installation instructions, and do the installation.

The solution’s pricing is reasonable. The solution has a lifetime license because we are not renewing the license every year. It is a one-time purchase.

So far, the failure rate with the solution is very low, and we want to find a spare for the existing unit.

Users must be familiar with the operation and configuration of Cisco Ethernet Switches to use them. They have to familiarize themselves with the solution and know the different configurations and features it supports. Users need to understand the solution properly before using it.

Cisco Ethernet Switches is a good solution.

Overall, I rate Cisco Ethernet Switches ten out of ten.

We are routing with the Cisco switches, so there are a lot of features, but no single one stands out. 

There's are other products that are better for network programmability. Cisco isn't as programmable as some others vendors. For example, on devices running iOS XE, you  dont have candidate configuration datastore when you use netconf like you would have on arista, juniper or others. Changes are directly applied on running configuration so there is no room for error once you commit changes to devices.

So it will be good for them to implement other config datastores because when it go to programming, review it's important so we need to be abe to have at least a candidate configuration datastore.

I've been using Cisco Ethernet Switches for 15 years.

Cisco Ethernet Switches are stable.

Cisco Ethernet Switches are scalable.

Cisco support is good once you reach a technician, but the website is a mess. I don't like the website.

I didn't use previous solution and then swith, but evaluate others vendors sometimes because their was in use in a company we bought, sometimes because their were shipped as a bundle with some hardware vendors solution for private cloud or storage solutions etc. Thought ome of them have some good features, Cisco got a better average rate when you take the whole thing.

The initial setup is really easy.

The price of Cisco switches could be lower. The cost is growing compared to other products, and it's more segmented. A Cisco switch is more expensive than before. For example, stackable models used to be provided with stacking ports and stacking cable. Now it's split you have to buy stacking kit separately. I don't know if they are the only ones like this or if this is standard now.

Yes other options have been evaluated but Cisco appeared to be the more easy to operate through the years regarding the stability of the product series, the CLI, support and documentation.

I rate Cisco Ethernet Switches eight out of 10. 

We have a few different buildings within our premises, and we typically use the Cisco switches as the core backbone of our LAN. They are connected with fiber. We use them for our network to handle security and connectivity mainly.

Our core business is to sell beverages, so we're not your typical telecom or banking institution that would be a typical Cisco client.

The quality of service is one of the main reasons we use Cisco in our organization. It's quite high and very reliable. The switches also end up working for a long time, so there's less need to replace them as often as others. We have some switches in our company that have been running since 2006, for example. They are quite old, but they still work.

The security and the user interface are both good. Mainly, I end up using the command lines, but it's okay for me and the way I work. It's my preference, although it's not ideal for everyone.

There are quite a few features that Cisco offers, but for our business, it's not really necessary. If you are a telecom or a banking institution, you would probably find them to be quite useful.

The cost is very prohibitive both for us as well as other organizations. It's very expensive to buy Cisco switches. Among our colleagues, we find that we're not alone in thinking it's too high. Everyone's complaining about this. 

We have many switches that we've used sine 2006 and that are on the old OS, but we don't want to switch them out because the cost to do so would be quite high.

The graphical user interface could be a bit better. When we have new employees, we want them to onboard quickly and to be able to understand the switches. Having a better graphical interface would help us do that and help them understand the switches faster. While I prefer command line, many are not good with it or do not prefer that method.

We've been using the solution since 2006. It's been more than ten years, so we're quite well versed in the technology.

The solution is quite stable. Cisco is a brand that's known for its stability. Our switches have worked for well over 10 years in some cases, without fail.

We never really directly deal with Cisco, so I can't speak to how well they are from a customer service perspective.

We moved from a different type of switch originally. We found switching over was quite straightforward and didn't run into any difficulties. However, now our office and our infrastructure are much more complex, so there is a bit of a learning curve. Companies with complex infrastructures will find that there will be complexity in the setup. They'll have to sort through that when they get started.

Originally, when our offices were smaller and more straightforward, deployment didn't take to much time. We handled it over a weekend, from Friday to Sunday or Monday. However, at the time, we weren't yet doing segmentation traffic.

We had a consultant in Belgium who came in over the weekend to help us with the process when we originally set up the switches. Normally we work within our own team and have our own in-house workers that handle the configuration.

I don't handle the licensing aspect of the solution, so I can't speak to the exact pricing. However, I am aware it's one of the more expensive options on the market. The last time I bought a 24-port switch, which was a while ago, I paid about five or six thousand Euros. In this part of the world, that's quite expensive for us.

I did compare Cisco to Ubiquiti. I was doing this research for a friend who was trying to open a resort but had limited funding. He didn't want to deal with Cisco as he knew the pricing would be out of his budget, so he asked me to look into another option. He asked that I look at Ubiquiti. For him, Ubiquiti ended up being a good option and was quite affordable. I believe you can also use Ubiquiti at an enterprise level as well. 

We mainly work with Cisco ethernet switches at our organization.

Aside from the cost, the Cisco switches are quite stable and easy to use. 

If you have the money as an organization, I would highly recommend Cisco.

We are just a customer of Cisco. We don't have a special relationship with the company in any way shape or form.

I would rate the solution 8.5 out of ten. I would rate it higher, but the price is too high, in my opinion. It's quite good for me in terms of the usage I get out of it, but I find that I don't use other features that Cisco offers now.

Versatility and streamlined IOS

Availability of expertise on the market (resources)

Streamlined IOS helped to develop templates for Ethernet Switches without worrying of compatibility of commands in regards to hardware platforms.

Modularity of Industrial switches (IE3000) provides flexibility in solutions yet based on one platform.

Vast array of Industrial models (IE2000, IE3000, IE4000, IE5000).

Acceptance of open source trends (there is slight move already - just keep going)

10 years overall for all switching/routing products. Industrial switches for last 5 years.

No

No

Well, need more pro-active option to add PoE modules to Industrial switches.

We deal with a Cisco partner - 4.5 out of 5.

We deal with a Cisco partner - 4.0 out of 5. Sometimes we find the solution before we get an answer from the Cisco partner.

Everything is driven by business requirements, which in turn different from one project to another. Major points are: availability of support/expertise beyond internal resources, territorial coverage, performance and support of multiple options from enterprise to industrial environment

Straightforward.

90 % in house. Vendor team has sufficient skills.

Cisco should look into more flexible licensing for hardware/IOS. It is hard to beat some vendors' lifetime warranty even they offer less in functionality compare to Cisco.

There are multiple vendors but they are very specialized and do not support versatile solutions. For example, we had to move from Schneider switches as they were just a marketing move by vendor and did not provided better performance or compatibility with SCADA products.

Start from your business requirements (what would you like to have) and budget (what can you afford).

I am using Cisco Ethernet Switches in my company.

The solutions meet my sign and safety requirements, integrate easily with my firewall device, and ensure the stability of our network.

The IP routing is the most important feature. It has saved my devices and PC printers and it is a very important feature.

AI technology must be involved in the future. Also, it would be better to have a little bit lower price or another licensing model.

I have been working with Cisco Ethernet Switches for about 14 years.

Till now, I have not placed any maintenance requests because this device is stable all the time.

Cisco Ethernet Switches are scalable.

I haven't needed technical support because the device is stable all the time.

Positive

Before Cisco Switches, I worked with 3Com devices, but only a few. I switched because Cisco is the most popular company.

The integration was easy.

Cisco is more expensive in my country. It is usually just one payment, and I do not need to pay for maintenance or support.

I strongly recommend Cisco Ethernet Switches.

I'd rate the solution nine out of ten.

Our primary use case is for ethernet switches. We mainly use switches and routers as edge distribution switches. Some of the plants have been with the big pharmaceutical company Aragon. We have also been with a North American company, and others. Most of their switches were Cisco in pharmaceutical company where I worked for 10 years.

Some of the switches in the plants were used as a core. Many of them, especially in Bulgaria and in Europe, I installed myself. Others in America are responsible during the shift time for the configuration changes and so on. They are used in any level, as a Layer 3, Layer 2, whatever. All kinds of switches are used in the different places in our LAN. 

Cisco Ethernet Switches are great devices. I remember when we decided to replace all the HP switches from the American company when they acquired us. We replaced all the core switches with 3850, except in the bigger and biggest sites where we used the 4745 switches. That was great. They are very useful and very easy to configure. It was not much trouble at all and we got a more stable network.

We have been very satisfied with using Cisco 2960 series X with EIGRP Cisco proprietary protocol. This saved us much money and worked very stably.

We also installed 47 and 3850 Switches to the main servers on the 10-gig in some places and Nexus devices using 40-gig connectivity.

We are less in the Cloud because the Cloud technologies didn't work so well. That happened in all of the companies where I've been engaged.

I have been using Cisco Ethernet Switches for a few months in my current position but I would say 20 years or more in other companies.

The stability is great. Some Aruba devices are more stable, but with Cisco, we never had problems, with some little exceptions. It is very stable.

It is very scalable.

In this company we have a single usage. I first started with Cisco routers in 1997, now we install Cisco routers all the time.

The technical support for the core switches especially, but for the rest as well, is very good. It's excellent support. Especially for the core switches we had 24/7 support. On some sites in Bulgaria we one time had a problem at midnight and they delivered that switch in time. They brought the switch very fast. Very good, excellent, technical support solution.

Also, with previous accounts with the pharmaceutical company we had access to a dedicated engineer for the project. We had access to their WAP environment. So, all told, tech support is brilliant.

I have used Aruba which is very similar to Cisco. It is also easy to manage and to install. Installing it is straightforward but I don't have too much experience with the priority. We were responsible for their LAN but they have some special requirements which we didn't touch. We didn't use all functionalities in the Aruba. We just used them as Layer 2 switches or as access switches on the main site, and on the bigger sites they had still some old HP switches.

Also, if I remember correctly, Comware had all those old HP switches. We used Aruba just as Layer 2 access devices and didn't use much of the functionalities.

I prefer Cisco. Of course, Aruba is cheaper overall but not necessarily for those small Layer 2 device access switches. I don't know what the price is now, I didn't compare each comparable device. If I had to choose, I would definitely go with the Cisco.

In terms of the initial setup, for me, with much experience, it's straightforward. With most of the switches we had a good team and prepared more than the configuration on the access sheet and then automatically generated the configuration file, just moved it to the note part, visually checking for a minute. Then copy, paste, and done. Start installing. Mounting and connecting. Straightforward.

It takes about one day for the device, if you don't count the cabling and the rack mounting and moving those and so on, and including the break, between 30 and 60 minutes, not more, for each switch. If they are stackable with some stack devices, for all of them, let's say an hour to hour and a half. Not more because we had all the configurations prepared in advance.

I you have a big client or if you have a big project and register it, the discount is good. In the companies that I have worked for, mostly for switching, we had a 55% discount or more. So with that good discount, who cares? It's cheap enough.

Cisco Ethernet Switches are appropriate for small and medium businesses. They also are large enough for our data centers which we had in Tel Aviv, Israel and in California. We had such big devices there.

On a scale of one to ten, I would give Cisco Ethernet Switches a 10.

I would advise others who are looking into implementing Cisco to buy and implement it.

I have been using the newest line of Cisco switches, the 9300 series, for two or three years.

We have two different models for deployment. One is the SDN deployment model, which has to do with Software-Defined Networking and is the more recent.

The other is the traditional three-tier, via core access aggregation layer five switches with an Independent Architecture Designed environment or access layer switches where you just use them to connect users to a specific service. It depends on what the nature of the work would be and the scope of work. But generally, most traditional networks have three layers. You have switches in a core of the network, switches in the distribution or aggregation layer, or switches in the access layer. This is the Three-tier module. If it is a collapsed core then it would be just simply the core and the access.

A primary use case is you could use it to connect mostly end-users and host systems. Systems could be servers, systems could be printers, systems could be telephones, and systems could be video conferencing equipment. That's one end use of it.

Another is the use in the data center. Ethernet Switches can be used in a data center out to provide connectivity, wired connectivity for servers, database systems, platforms, other platforms systems, and storage systems. With Ethernet you could have different speeds, so you can have Ethernet running at 1Gig, you can have Ethernet at 10Gig, you can have Ethernet at 40Gig, and you have Ethernet at 100Gig. So, depending on the nature of connectivity, you have that in the data center, you can have that also in an office environment. Then you go up to have it in industrial space, monitoring of industrial machines and control systems. So again, Ethernet is widely used.

There are several situations where these switches are used. Most times if they want to move off the main site, or they want to move locations, or they want to have temporary spaces, they can use a switch. Temporary means they may want to expand connectivity from their network to a small branch office that is temporary. Temporary means they're going to run something there for six months and then after that the business won't be there.

With switches, you can expand your network with a connection aside but you can extend your network to a particular area. You can also develop a campus network, campus meaning you may have one building in there and then the company acquires another building, and then it's easy to connect the two buildings together with Fiber and a switch if you have that available. 

There is also multi-tenancy, if you're in a building when you have multiple floors, it's easy to extend the premises from one floor to another floor using a switch as well.

In terms of projects, technical projects, they are several, I mean even down to connectivity to third parties inside the data center. For example, you may find out that you need to connect to BT or you need to connect to your telco provider. Switches will facilitate your ability to connect to a third party to allow communications between two separate environments that are managed differently.

I've done projects where the switches are also used for translation. For example, one part is using Fibre, the other part is using Ethernet, and the switch can be used to communicate between the two technologies. The switch will transform the physical characteristics of the link from Fiber to Ethernet.

There are two things about this solution that I find valuable. One valuable feature is that you can string a number of switches together, and the fact that there are various methods to connect them, such as by stacking. A stack means that they operate as one switch spot. You have multiple physical switches in the stack. For example, you could have one particular physical switch and you can have many of them all connected together as if they're one switch.

Another valuable feature is that the switches can operate at different layers of the networking environment. You can have switches that operate at layer three, you can have layer four switches and also obviously layer two, data layer, is their normal operation.

These switches are versatile. They can operate as a router, but they can also operate as a switch as well. The fact that you can run routing protocols on them, and you can also run data link protocols, means that they are quite versatile enough.

At the moment the switches that you have can't scale because they've got their control plane and data plane in the same device. The problem with that is you're limited to the number of switches you can string along because of limitations with VLAN. VLAN does have limitations, but with Software-Defined Networking there is no limitation. This is bringing about changes in the networking field that are long-needed. Ultimately, I would like to see all of the switches support SDN.

Switches should be made stackable, even if they are not of the same model. Now stacking is another technology that a lot of switches can benefit from, but not all switches are capable of stacking. There are some switches that are capable of stacking, but not all switches. As a rule, in my view, I feel stacking should work between different switches and at the moment it doesn't. For example, if you want to build a stack, all the switches in the stack have to be literally the same. So that another area of technology which could be different. You could stack switches, even if they're not exactly the same, but they have a way of operating such that they can work together. It would be nice because it means people don't have to throw away things just because they can't meet what they want.

I think this solution is very stable.

These switches have been around for a long time. Before that, all the technologies used couplers, which were called BNC connectors, network taps, all those things that existed. Couplers that existed before the arrival of Ethernet, they didn't last even two, three years, whereas Ethernet has been around for more than fifteen years.

Ethernet will continue to be around, and it's a very stable technology in terms of the operation. As well, Ethernet is the way forward, and it will still be around for another ten or fifteen years.

Ethernet does not scale very well because you've got distance limitations. Ethernet can only run for about one hundred meters or less, so you have to use Couplers. This distance limitation is why we use Fibre. Fibre optics is actually a better technology than Ethernet, but it's more expensive. Everything about it, the equipment, the nature of the way the Fibre cables are prepared, is a lot more expensive compared to Ethernet.

Ideally, everybody would like to run Fiber switches because it's a better technology that carries more bandwidth. The high price is due in part to the components. All the components that make Fibre work are expensive to produce. It can be relatively cheap for what we use it for but overall, it's way more expensive than Ethernet. If it wasn't for that then Fibre would have been the best solution. Ethernet, as it is right now, the cost price point for Ethernet is very good, so it won't be going anywhere fast soon. In terms of scalability, don't have limits. If you want to scale, you need to use Fiber to scale.

In terms of users, the organization right now has more than a thousand, and the previous one had approximately five thousand.

With respect to user roles, some are call center personnel, some platform systems guys, some are software developers, some project managers, some are marketing managers, some are sales managers, and some are professional services. Department-wise you have your legal, HR, and your finance department.

To my knowledge, our business is focused on doing work for clients so I expect that our usage of Ethernet Switches will be expanding.

The technical support for this solution is very good. They're very responsive.

I have also used the Meraki MX switches, but they are more like routers and used to support the wireless systems for Meraki.

With respect to the initial setup, the complexity depends on the topology. Most times they're not complicated. What's complicated is if you need to use them as a layer three switch, then you could have some complex configurations to do. However, if it's layer two, which is data layer connectivity only, then it's easy. If it's layer three then it's a little more challenging because you combine layer two and layer three and it could involve routing protocols. It's a lot more complex. 

Generally speaking, it depends on the manner in which you want to use the switch. Some deployments took maybe two weeks, some three days, some a month, and some even up to three months.

When it comes to my implementation strategy, first of all, you have to get the physical hardware into the data center or location where it needs to be. Make sure the right structured cabling was in place to connect this equipment so that it can work in that environment. Both from a power perspective and from a cabling perspective. I got to cable this switch to other systems and make sure that the right type of cabling is in place. Also, I have to make sure of the configurations that I'm going to use and get them organized upfront. In other words, I have the configurations I am going to put on a device and the software version. 

Another important thing is the software version. Make sure that the version is the appropriate one to put on there. Ensure that it doesn't have bugs or things, the type of configuration I want to put on there doesn't have bugs or anything that could impact the operation of those configurations.

After that is complete, I make sure that all of the connectors or transceivers that I've brought are the right type of transceivers for the systems. I'm able to connect them onto the network. Now that's just the physical connectivity.

There are other things you would do in implementation to test that the switch is working fine once it's operational. There are other tests that you conduct like Ping test, IP test, or whatever to show basic connectivity exists to that switch from the management perspective. You may also have tools, such as monitoring tools that you would use. You would also configure the monitoring tools to be able to recognize that particular device on the network and maybe things like memory, CPU, all the things to do with power, all these environmental conditions around that device are being monitored as well.

Then obviously you've got documentation as part of it. If you're putting a new set of equipment in there, the site probably has existing documentation that needs to be updated to reflect the fact that the typologies changed or you're introducing new equipment into that topology. In some cases, you've done this all upfront before you start the implementation. While in some cases, some companies, for the rush of time they want you to implement first and then do the documentation later. So again, it's still part of that strategy. Implementation wise, that's the approach you would go with in my opinion. Obviously there are different implementation approaches, and the stuff we're talking about here is just hardware.

I am a specialist, and in most cases, I handle the implementation and deployment.

The time I would use another person is if the data center was far away when it's not conceivable that I would travel to that location. I'd probably use somebody from the data center or use a data center engineer who would set up the hardware. He would put the hardware in the rack, the network cage, or rack where the equipment is going to be located. He would help me physically screw the equipment, take it out of the box, and connect it into the cage, and then I'd give him instructions on where to put cable or where to plug the various cables that come with the equipment. So once he's done that, I'm able to remotely connect to the device.

Those are remote working situations where you're not physically able to go to the site and do the work there. Then yes, I would work with other people sometimes and give them some instructions on what I want to have done at that location.

What is happening in the industry is that they are separating two things that traditionally held back the growth of switches, which is the control plane aspect of the switch from the data point. What you're finding is that the newer generation of switches, you can control them with a different device separately from the switch itself. In terms of the improvements, the improvements that are going on right now, Software Defined Networking creates the basis for you to have switches that can scale, and can scale very well.

I would rate this solution a nine out of ten.