What is our primary use case?
I use the solution in our typical university network, which is not very sophisticated. In our university, we have some virtual networks within the labs, but normally, we have a very simple configuration without too many rules because it's supposed to be very flexible for us to use. The end users always ask something like how they would like to test one server over the other, making it really hard for our university's network administrator to manage it all day. Our university's network is pretty much open, and there is always a danger of intruders, but currently, we don't have such problems.
What needs improvement?
The high price of the tool is an area of concern where improvements are required.
For how long have I used the solution?
I have been using Cisco Ethernet Switches for over twenty years.
What do I think about the stability of the solution?
I haven't experienced any stability problems with the product, making it a perfect solution for me. I don't care about the other factors involving network administrators who use the tool since, for me, the service provided by the solution is okay.
It is a stable solution since I have not seen any network failures when using the product. Normally, there are no problems with the networks in our university. If there are some general problems in our university's network, it's mainly due to the provider facing some issues due to a cut-off in some fiber switches, which may be the result of some construction work somewhere. Under normal circumstances, everything functions perfectly.
What do I think about the scalability of the solution?
It is a scalable solution.
There are around 3,000 to 4,000 users of the solution, considering that all the students in our university use it.
How was the initial setup?
The product's initial setup phase is not easy, considering that there is a need to plan the virtual networks and see how you are connected. I think that network administrators can manage the setup phase since they have been through Cisco-centric courses, making them capable of handling the setup phase if they are able to define what you want.
During the setup phase, challenges arise when we have to define what we want and the services we expect from our network.
The solution is deployed on an on-premises model.
What's my experience with pricing, setup cost, and licensing?
It is an expensive product since it is used in a large network where you cannot rely on some cheaply priced solution. The solution primarily stays stable, so we don't face any problems with the product.
If you are looking at something really stable, then you will buy Cisco. If you want to buy a product for some offices or small buildings, then you can go for a cheaper tool that you can maintain and replace easily.
What other advice do I have?
Though I wanted to use the product, there were no opportunities at the university that would allow me to use the solution.
The product does have some security features, but I don't get involved with the security area since I don't need it.
There are two to three people to maintain the solution, but we outsource the maintenance services when we face some major issues.
I recommend the product to those who plan to use it.
I rate the tool an eight to nine out of ten.
Which deployment model are you using for this solution?
On-premises
*Disclosure: I am a real user, and this review is based on my own experience and opinions.
