Ease of Use: Users have appreciated the platform's simplicity in task execution and straightforward management, making their operations more efficient. For instance, the intuitive interface allows users to navigate seamlessly and complete tasks with ease.
Customizable Dashboard and Inventory Features: Users found the customizable dashboard and tag search inventory feature beneficial, as it provides them with a personalized experience tailored to their specific needs. This customization empowers users to prioritize important information and access relevant data quickly.
Centralized Management Capabilities: The centralized management aspect of the platform has been praised by users for enabling efficient orchestration and optimization recommendations, streamlining their processes effectively. By having all management tools in one place, users can easily oversee multiple aspects of their system without switching between different interfaces.
We are just beginning to migrated from UCS Central to Cisco Intersight. We will be using it to manage our UCS Infrastructure.
It seems like a very comprehensive management tool for system in IMM.
Cisco Intersight is now our primary pane of glass for managing our fabric interconnects and compute nodes.
The roadmap for Cisco Intersight features far offsets any present roadblocks.
Use Intersight to manage and monitor our large foot print of Cisco UCS blades and rack servers. It is one view dash.
I have used this products for last five years and it has evolved over time and lots of new features and additions.
We use Cisco Intersight to manage the UCS servers. It solves the problem of managing multiple data centers via one management solution.
If a customer has multiple data centers no matter locally or around the world
In our organization, We are using Cisco Intersight with a Cisco UCS (unified computing system) Blade 9K for configuration and monitoring.
The limited monitoring feature is when it comes to the observability to some problems special in case of troubleshooting.
In our organization, We use Cisco Intersight to manage our UCS (unified computing system) Infrastructure and leverage Automation.
If asked, I think I am likely to recommend Cisco Intersight to a colleague because, in my experience, Cisco Intersight is well suited for managing your data center
We use Cisco Intersight to manage our UCS and Hyperflex clusters.
From Operations and management perspective it's a single pane to centrally manage all our clusters both DC and remote including HX clusters. Deploy, build and manage in single pane.
Deployed multiple HX clusters from 1 single pane with policies.
For anomalies detection and incident management.
Very good for detecting anomalies
Managing the UCS chassis and the fabric interconnect switches
Easy to manage and rollout new equipment
We have been using Cisco UCS in legacy UMM (UCSM managed mode) for over 13 years. When Cisco released a newer generation of product (Cisco UCS-X), we were steered in the direction of Cisco Intersight Infrastructure Service and domains in Intersight Managed Mode. We use Cisco UCS domains in UMM to give us a single pane of glass of all our servers and domains, even though in UMM the domain is read-only. The base (free) features in Cisco Intersight Infrastructure Service give us all the features we need for our legacy domains (Connected TAC, auto Support Request generation and TAC's ability to extract log files). For the domains that we have built in UMM and then transitioned to IMM, the IMM Transition Tool has been indispensable. We found it easier to transition an existing domain with settings that have been in use for years, than configuring policies and profiles from scratch. We heavily rely on Cisco PowerTool commandlets to extract and configure settings on our UMM domains and service profiles and were concerned that we had to adopt usage of the Intersight API to get feature equivalency. This ended up not being an issue in Intersight Managed Mode, since all profiles (domain, server, chassis, etc) are associated with updating templates for each, and consume policies which can be reused. Being "nudged" to use server updating templates (this is the only option, whereas in UMM and Cisco UCS Central we always used initial templates only) allowed for a high level of standardisation in our footprint.
It is highly suited for an organisation pushing for a standardised and centralised configuration of settings using policies, profiles and templates. It is highly suited for customers used to legacy UMM that need to refresh their environment, but instead of deploying them in UMM (which is still possible), to take the time and effort to learn Cisco Intersight Infrastructure Service and IMM as well as familiarise themselves with the differences between UMM and IMM, and the issues in UMM which IMM addresses and improves upon. We deployed in UMM initially then transitioned to IMM with the transition too. I cannot think of a scenario where Cisco Intersight Infrastructure Service would not be suited. Even for small-scale deployments, it provides significant benefits. Maybe if you come from another server vendor management environment, the learning curve may feel steep (e.g. many new concepts and constructs that one has to master).