What is our primary use case?
The first use case is to build a hybrid cloud. The first thing is to configure the server. The server could be located either on an edge location or on the data center, or it could be a remote office branch office. Cisco Intersight gives us a single pane of glass through which we can configure and monitor a server which is geographically spread, based on different locations.
Another use case involves certain workflows that we can run using Cisco Intersight. For example, it has cloud orchestration capabilities. We use it to run NetApp-related day-to-day operations. For example, we can do some volume-related, storage-related tasks directly from Cisco Intersight. It invokes a Terraform-based script through which you can just do your day-to-day operational tasks.
Another use case is that we also leverage Cisco Intersight for installing ESXi, as well as it has tight integration with Red Hat OpenShift. For the customers who are going into Kubernetes, for that we leverage Cisco Intersight, and we can directly boot those servers using the Red Hat operating system. Basically, it's a core operating system of Red Hat.
What is most valuable?
In Cisco Intersight, if you compare it from Cisco UCS Manager, it's local to a single UCS domain. But with Cisco Intersight, if you have a large data center, you can manage it and you have great visibility using Cisco Intersight. You can do a lot of automation using Cisco Intersight, and the consistent policy can be applied thoroughly to your resource group. It always gives you a cloud experience, especially when you talk about compute.
I particularly appreciate the policy feature. For example, I have two or three different stacks. For the first stack, I'm running a bare metal where I need to deploy Oracle Linux or Red Hat Enterprise Linux. And in the second stack, I need to deploy a VMware-based workload. And the third could be a Kubernetes distribution. With Cisco Intersight, you get flexibility through which you can create different policies, because everything is policy-based. And you can still have a consistent configuration and apply those policies based on your requirement. This is one of the best features because if you look into the VIC card of a Cisco server, which is a Virtual Interface Card, for each operating system, you need to have a specific configuration. There are certain templates which are already there. For example, if I need to select a VIC card of 15,000 series VIC card, there will be a predefined template for VMware, which I can select and use it for my server profile. That is one of the best benefits I can think of having Cisco Intersight.
What needs improvement?
The challenge could be if there are any bugs. Most of the time, you may feel that the TCAM resources are getting full on the Nexus just because of some bug or the configuration is not supported. Or sometimes, if there are any vulnerabilities happening on the current running firmware, those are challenges we have. And if you talk about from the compute side, there were initial bugs such as a CPU throttle issue. Because of that, the chassis was not running in an optimum way. You may see performance issues during that time. For that, Cisco released a patch, and it got fixed.
I think Cisco Intersight should allow more automation capabilities. It should be more open, and it should provide more automation capabilities. I think there is also a scope of making it a little bit simpler because a lot of policy and config sometimes becomes confusing for the user because it has a lot of config. Maybe they can do a little bit of simplification with Cisco Intersight.
For how long have I used the solution?
I have been using this for more than seven years.
What do I think about the stability of the solution?
In general, it's good when I compare it. From Cisco Intersight, you will not face any issue. But if you look into the hardware side, if you are not getting proper cooling, if the cooling in the data center is not that efficient, then you might see some temperature-related issue which can impact the performance, and you will get a lot of alerts. But the good thing is that Cisco Intersight will be able to capture everything in detail, and even you can configure the call home. So you will get notified if anything is going wrong. Even if one port is also down in one of your fabric interconnects, you can immediately get an email. That is a good thing.
What do I think about the scalability of the solution?
It's very smooth. If you talk about scalability, you can create a server profile immediately, and you can map to multiple servers the moment you try to scale. Similarly, scaling down goes the same way. You can just disassociate those server profiles and remove it. Those servers are free for use again. It's quite good.
How are customer service and support?
Cisco TAC in general is quite good. But sometimes, it totally depends upon the reason of that TAC case. For example, if I'm opening a case and that case is getting landed to one of the US engineers, or it's in South America or North America, I expect the quality of support will be very good. But sometimes because of the locality or the region specific, if the case gets landed into some other queue, some other region, I might feel that inefficiency from the support side. But overall, it's good. If it's very urgent, you can immediately ask the duty manager to escalate this issue. They will put a lot of attention into solving the things. Overall, I can say that the support side is good.
Which solution did I use previously and why did I switch?
I am currently working with NetApp. I work on Cisco and NetApp products, both. I have used NetApp BlueXP, which is rebranded with the name NetApp Console.
How was the initial setup?
For the beginner, definitely it's not that straightforward. You need to read the document properly. If there are any deployment guides, such as how to set up Cisco Intersight environment, you need to work through thoroughly. It's not straightforward if you compare it with how UCS Manager used to be. Definitely, it's a little bit complex because of multiple policies, and you need to know how you are calling the objects, because it's kind of object-oriented based. First you create a policy, then you need to call that policy in some different object. Those things are there. But once you get accustomed and practiced on Cisco Intersight, then it's easy for you. But for a starter, definitely it's a little bit complex.
What's my experience with pricing, setup cost, and licensing?
It totally depends upon what you want from Cisco Intersight, because they have different categories of licenses. For example, you have Advantage license and Essential licenses. Definitely, if you want to do a lot of automation using Cisco Intersight, you need to go with the Advantage license, and that can be a little bit pricey.
What other advice do I have?
I work as a partner. For optimizing, Cisco has various tools. If you talk from a network point of view, they have recently launched Nexus One. That gives enterprise an opportunity to configure a heterogeneous environment. For example, if you're having a campus networking and data center using different devices such as Catalyst, Nexus switches, you can still manage everything. And at the same time, if you still have software-defined network, which is the ACI product from Cisco, you can still manage that. With that, you will get a single pane of glass to configure and to automate the things. You don't need to log in to multiple setups to look into each device. And on top of that, they also have telemetry. That tells you how the traffic pattern is going, and based on that, you can apply configuration on your devices.
In our lab also, we have Cisco switches. You can develop a lot of automation because Cisco is rapidly working on DevNet. You have different options. You can use NSO also to configure the devices, or you can integrate with Terraform, or they also have infrastructure as code. You can leverage those playbooks if you're dealing with Ansible, and you can also do the automation on your day-to-day ops. Recently, Cisco also has some announcement with Quali. It's a stack automation. We are doing the testing with Quali. Basically, this will help for Day 0, Day 1, and Day 2 deployment or Day 2 operations as well. It supports multiple stacks. And suppose, as per looking into engineering effort, suppose some team has already developed a lot of playbooks for different tasks. If suppose moving into a different tool, can say that so we are wasting a lot of engineering effort. But with the stack automation Quali, you can still use those playbooks and can do your Day 2 operation. I think that will definitely help an organization in their Day 2 operation and can help the efficiency in their operations.
With Splunk, it's very good. Splunk has a very great capability. You can do log analysis. You can have a deep visibility. And you can also have Cisco ThousandEyes. That helps you the entire network packet flow. It can even look into the application side of it and tell a network engineer that the problem is not on the network side, it's the application itself is having some issues. Visibility-wise, they have different tools, different offerings. You need to get the right tool for yourself. And Splunk is a great tool if you want to get a lot of logging, telemetry data. You can put everything into Splunk and you can get a dashboard that helps in improving your operational visibility, helps you to detect the threat as well. You can create different dashboards. And the best part is that if you're having a converged infrastructure in your data center, you can have a visibility of each stack. It's not only about having compute, network, storage. You can still look into GPU, NVIDIA side of it, or any Kubernetes that you're running, for example, Red Hat OpenShift. It's very good visibility if you're going with Splunk.
It definitely enhances the troubleshooting capabilities. And also, suppose you have built a SOC team, a Security Operations Center. If you have a proper Splunk dashboard setup, it will help the SOC team directly also because they can immediately look into if there are any abnormality happening, a sudden spike happening within the network or any application is getting compromised. The SOC team also can get heavily benefited if you have a proper Splunk setup in your environment.
Cisco Intersight definitely enhances the troubleshooting capabilities. Because as I mentioned, the first is you can directly work with TAC seamlessly. Cisco Technical Assistance Center is the TAC. In the old days, during the old time, we needed to work on an individual server, provide the logs from a single domain. It was a very cumbersome task, and it was lots of time-consuming. But with Cisco Intersight, now you can directly create the support bundle, and it can be fed directly to Cisco TAC. That helps you in getting engaged with the Cisco TAC or getting proper support from Cisco. Apart from that, doing the upgrades. Since now it's a SaaS and it's a centralized product, if you plan to upgrade your Cisco Intersight, if you plan to upgrade your UCS domain through Cisco Intersight, you can directly do it. You don't need to log in locally to each domain. That is one of the great enhancements that I can see.
I purchased Cisco ASA-V from Marketplace. My overall review rating for this product is 8.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other