There is room for improvement in the software part of Cisco UCS Manager. It should be more user-friendly, especially when creating policies. For example, if I am putting a maintenance policy, the software should be more descriptive and user-friendly, especially when dealing with policies in UCS Manager.
Cisco UCS Manager is slightly more complicated to deploy and requires technical expertise that small organizations probably won't have. Cisco UCS Manager is expensive and it could be made cheaper. Cisco UCS Manager should have a simplified deployment in the sense of not having multiple machines, demilitarized zones, and on-premise options. Also, the ability to configure, maintain, and support could be more intuitive and user-friendly.
Technical Engineer/Pre Sales Security, Data Center at a tech services company with 10,001+ employees
Real User
2023-01-26T19:12:21Z
Jan 26, 2023
The integration with other solutions could be better. I think Cisco can only integrate using Intersight. There is a second interface available as a SaaS platform, in the cloud, or on-premise. It's based on the Redfish protocol, which is standard for all the B-series servers in the market. We can integrate other solutions using API. Cisco is somewhat inflexible. It's not full HTML or XML. It uses a Java-based language, so you need a browser that supports Java. Intersight has a full web interface, and it's open to other systems with the API. It can just generate API from the side of other solutions. For example, Splunk and SIEMs can integrate with UCS via Intersight.
When we are creating profiles for servers, it would be nice to have the ability to copy features of the profile we created for the previous server, so we don't need to create a new profile for each one.
Solution Designer at a consultancy with self employed
Real User
Top 20
2022-12-20T19:34:00Z
Dec 20, 2022
There are quite a few components when it comes to operating servers, and the process has to be done in a sequence. If UCS provided a functionality to set up all of my sequences in one go, for example, I want to apply this piece of software now, and once this is done, I want to apply this piece of software, it would be great. I want to be able to schedule multiple sequential updates in one go. Also, I've been trying the solution on a mobile device, and it doesn't work that great. They could probably do with redesigning the interface so it works for different device sizes and resolutions.
Senior System Engineer at a tech services company with 10,001+ employees
Real User
Top 5
2022-11-22T15:45:32Z
Nov 22, 2022
What's lacking in Cisco UCS Manager is the performance dashboard. If a blade has any performance issues, you should be able to create a dashboard on Cisco UCS Manager. Currently, this feature isn't present, so it's an area for improvement in Cisco UCS Manager. Cisco UCS Manager has an alert feature, so you can configure alerts when an error occurs, but what's missing is the alert for blade performance issues, such as CPU, memory, or network issues. For example, if the CPU utilization goes beyond eighty or ninety percent, the Cisco UCS Manager should be able to alert you, but that's not available now. I want to add more chassis to help with scalability in the next release to Cisco UCS Manager. The platform also needs performance monitoring for the hardware.
The automation within the solution needs to be simplified. In the next release, the solution should have a central view center or offer administration capabilities for different environments.
IT Infrastructure Architect at a tech services company with 11-50 employees
Real User
2020-02-04T09:59:56Z
Feb 4, 2020
The interface and the way it is constructed is very complex. They should work to simplify it. It's quite difficult for somebody who doesn't know the product very well. Users should be able to get proficient with it faster. There's definitely room for improvement there.
Data Engineer at a media company with 10,001+ employees
Real User
2020-02-02T10:42:00Z
Feb 2, 2020
In terms of what can be improved, the help dashboard could. Usually, we use vCenter. If I go to an option called Performance Monitoring, it gives us metrics in real-time. The performance dashboard should be out in front of the UCS Manager - as soon as you log in you should see the dashboard. That should be improved. Another thing is the inventory management dashboard. Inventory is like a configuration database. So we should also be able to pull all the details which can give answers so we do not wonder about the HCI data. Also, scalability could be improved in this solution. Lastly, it should be more user-friendly because Cisco is a bit of a complex solution. So we are running the VMware environment and it has added capabilities of management.
Sr. Lead Consultant - Infrastructure | Virtualization & Cloud Computing | SDN |NFV at a computer software company with 1,001-5,000 employees
Consultant
2020-01-22T12:44:00Z
Jan 22, 2020
I would like to see Cisco UCS optionally work as a hyper-converged system because right now, it only operates as a converged system. Adding another layer of embedded virtualization would allow us to sell this as one unit, like Nutanix or VxRail.
Infrastructure Architect at a transportation company with 1,001-5,000 employees
Real User
2020-01-16T08:44:00Z
Jan 16, 2020
So far the only challenge we face with Cisco UCS is during firmware upgrades. If it happens that there is a failover, and we need to change something in the system, this is where we can run into problems. We can't upgrade the firmware for each component one-at-a-time. It is not a method that will work in a practical way in a larger or global network. Nowadays it is some sort of a status symbol or a business necessity for a customer to be in various geographical locations. Because the client can have locations in Australia and the U.S. — in different regions of the world — that tends to make the maintenance of the firmware more difficult. The various business locations offer challenges in that way. Usually, when we procure the blades, everything has the same firmware level. This makes sense and is fine if installing in a singular location and for new installations. Everything will match. If it is a new installation and the hardware was not procured at the same time, the firmware for all the components can easily be upgraded because it is still before the implementation. But later — say after one year — a customer needs to expand. If we are procuring a new blade, the new blade will come with the new firmware. When the new blade is mounted into the chassis, the old alignment will not understand the new blade because it has new firmware. In that case, you need to downgrade the firmware for the new blade or upgrade the firmware for the entire environment. During the firmware upgrades, we would definitely need to take downtime in some cases and the downtime would take too long. We face that challenge all the time in having to choose which path to take during the upgrade. But because of the obvious issues with upgrading the entire environment, it often looks like a better solution to just downgrade the one new blade. We need the option to downgrade or choose the firmware for the component because we cannot upgrade the entire environment. In many cases, we cannot take the downtime for the entire environment because of what it means to the network and the business. We should have chances to work with firmware levels in one or two firmware versions and it should be easier to do. Everyone would be comfortable with that. Otherwise, in some cases, there is no point in providing a new blade. Customers will hopefully grow and need new blades. We don't want any extra risk with downtime. So Cisco should make an improvement in the firmware upgrade process. No one is providing this kind of solution. But if Cisco would improve that firmware issue, that would be great. A new feature that I would suggest is to have the possibility of different types of connections. Within the full-width blade, there are two types of blade: full-width and half-width blade. In the full-width blade, when one link fails, the other link will take care of the entire load. The half-width blade doesn't have that kind of input. It has only one link. If one link goes down, the entire blade goes down. So Cisco should include the feature like that in the half-width blade so it functions more like the full-width blade and is not prone to failure.
Senior System Engineer at a financial services firm with 10,001+ employees
Real User
2019-12-30T06:00:00Z
Dec 30, 2019
Integration can always be improved, but that is not an issue for me because I work in a bank in Turkey. In Turkey, there are some regulations regarding Co//ab in the banking industry. Authorities are not permitted to use Co//ab for banking, so integration is not a use case for us. The stability could use some improvements. We have three data centers and if we could manage all three data centers using one interface, it would be great.
Network and Security Manager at a energy/utilities company with 5,001-10,000 employees
Real User
2019-10-20T10:33:00Z
Oct 20, 2019
Firepower has weaknesses. I had to load several partitions to improve it. A smart office solution provided us with a demo showing us the camera qualities. I believe that Cisco is moving forward with this. In the next release, I would like to see improvements made to their security. Also, they have to introduce firewall compatibility in the UCS, as with Firepower where they have a dedicated box with their software, switches, and routing. It's a one-box solution and it would be a huge benefit for Cisco. Cisco depends on other vendors like IBM and HP for the hardware. Cisco should improve its hardware manufacturing in regards to the UCS and the use of other vendor's hardware.
If there were a way to make the upgrade process better, it would be great. Our most important issue right now is to resolve the installation barrier so we can use the product features fully. We needed to phase in new hardware and try again with Cisco HyperFlex M5. Also if we had one interface, it would solve some operating issues. If we can control all devices from one interface, I think it would help a lot.
I found it a bit of a challenge to get training on UCSM. I've been trying to get that for some time now. I feel like I have to figure out a lot of things myself. For years I've to log calls with support whenever I've got challenges that I cannot resolve. If I had some training or more manuals, I'd be better able to handle more things on my own. They should work to simplify the server creation template.
Cisco UCS Manager helps significantly reduce management and administration expenses by automating routine tasks to increase operational agility. Customers can extend the benefits of Cisco UCS Manager globally across an enterprise to thousands of servers in multiple domains with Cisco UCS Central Software.
There is room for improvement in the software part of Cisco UCS Manager. It should be more user-friendly, especially when creating policies. For example, if I am putting a maintenance policy, the software should be more descriptive and user-friendly, especially when dealing with policies in UCS Manager.
Cisco UCS Manager is slightly more complicated to deploy and requires technical expertise that small organizations probably won't have. Cisco UCS Manager is expensive and it could be made cheaper. Cisco UCS Manager should have a simplified deployment in the sense of not having multiple machines, demilitarized zones, and on-premise options. Also, the ability to configure, maintain, and support could be more intuitive and user-friendly.
The integration with other solutions could be better. I think Cisco can only integrate using Intersight. There is a second interface available as a SaaS platform, in the cloud, or on-premise. It's based on the Redfish protocol, which is standard for all the B-series servers in the market. We can integrate other solutions using API. Cisco is somewhat inflexible. It's not full HTML or XML. It uses a Java-based language, so you need a browser that supports Java. Intersight has a full web interface, and it's open to other systems with the API. It can just generate API from the side of other solutions. For example, Splunk and SIEMs can integrate with UCS via Intersight.
When we are creating profiles for servers, it would be nice to have the ability to copy features of the profile we created for the previous server, so we don't need to create a new profile for each one.
There are quite a few components when it comes to operating servers, and the process has to be done in a sequence. If UCS provided a functionality to set up all of my sequences in one go, for example, I want to apply this piece of software now, and once this is done, I want to apply this piece of software, it would be great. I want to be able to schedule multiple sequential updates in one go. Also, I've been trying the solution on a mobile device, and it doesn't work that great. They could probably do with redesigning the interface so it works for different device sizes and resolutions.
What's lacking in Cisco UCS Manager is the performance dashboard. If a blade has any performance issues, you should be able to create a dashboard on Cisco UCS Manager. Currently, this feature isn't present, so it's an area for improvement in Cisco UCS Manager. Cisco UCS Manager has an alert feature, so you can configure alerts when an error occurs, but what's missing is the alert for blade performance issues, such as CPU, memory, or network issues. For example, if the CPU utilization goes beyond eighty or ninety percent, the Cisco UCS Manager should be able to alert you, but that's not available now. I want to add more chassis to help with scalability in the next release to Cisco UCS Manager. The platform also needs performance monitoring for the hardware.
Its user interface can be improved. It can be more user-friendly.
The automation within the solution needs to be simplified. In the next release, the solution should have a central view center or offer administration capabilities for different environments.
The interface and the way it is constructed is very complex. They should work to simplify it. It's quite difficult for somebody who doesn't know the product very well. Users should be able to get proficient with it faster. There's definitely room for improvement there.
In terms of what can be improved, the help dashboard could. Usually, we use vCenter. If I go to an option called Performance Monitoring, it gives us metrics in real-time. The performance dashboard should be out in front of the UCS Manager - as soon as you log in you should see the dashboard. That should be improved. Another thing is the inventory management dashboard. Inventory is like a configuration database. So we should also be able to pull all the details which can give answers so we do not wonder about the HCI data. Also, scalability could be improved in this solution. Lastly, it should be more user-friendly because Cisco is a bit of a complex solution. So we are running the VMware environment and it has added capabilities of management.
I would like to see Cisco UCS optionally work as a hyper-converged system because right now, it only operates as a converged system. Adding another layer of embedded virtualization would allow us to sell this as one unit, like Nutanix or VxRail.
So far the only challenge we face with Cisco UCS is during firmware upgrades. If it happens that there is a failover, and we need to change something in the system, this is where we can run into problems. We can't upgrade the firmware for each component one-at-a-time. It is not a method that will work in a practical way in a larger or global network. Nowadays it is some sort of a status symbol or a business necessity for a customer to be in various geographical locations. Because the client can have locations in Australia and the U.S. — in different regions of the world — that tends to make the maintenance of the firmware more difficult. The various business locations offer challenges in that way. Usually, when we procure the blades, everything has the same firmware level. This makes sense and is fine if installing in a singular location and for new installations. Everything will match. If it is a new installation and the hardware was not procured at the same time, the firmware for all the components can easily be upgraded because it is still before the implementation. But later — say after one year — a customer needs to expand. If we are procuring a new blade, the new blade will come with the new firmware. When the new blade is mounted into the chassis, the old alignment will not understand the new blade because it has new firmware. In that case, you need to downgrade the firmware for the new blade or upgrade the firmware for the entire environment. During the firmware upgrades, we would definitely need to take downtime in some cases and the downtime would take too long. We face that challenge all the time in having to choose which path to take during the upgrade. But because of the obvious issues with upgrading the entire environment, it often looks like a better solution to just downgrade the one new blade. We need the option to downgrade or choose the firmware for the component because we cannot upgrade the entire environment. In many cases, we cannot take the downtime for the entire environment because of what it means to the network and the business. We should have chances to work with firmware levels in one or two firmware versions and it should be easier to do. Everyone would be comfortable with that. Otherwise, in some cases, there is no point in providing a new blade. Customers will hopefully grow and need new blades. We don't want any extra risk with downtime. So Cisco should make an improvement in the firmware upgrade process. No one is providing this kind of solution. But if Cisco would improve that firmware issue, that would be great. A new feature that I would suggest is to have the possibility of different types of connections. Within the full-width blade, there are two types of blade: full-width and half-width blade. In the full-width blade, when one link fails, the other link will take care of the entire load. The half-width blade doesn't have that kind of input. It has only one link. If one link goes down, the entire blade goes down. So Cisco should include the feature like that in the half-width blade so it functions more like the full-width blade and is not prone to failure.
Integration can always be improved, but that is not an issue for me because I work in a bank in Turkey. In Turkey, there are some regulations regarding Co//ab in the banking industry. Authorities are not permitted to use Co//ab for banking, so integration is not a use case for us. The stability could use some improvements. We have three data centers and if we could manage all three data centers using one interface, it would be great.
Firepower has weaknesses. I had to load several partitions to improve it. A smart office solution provided us with a demo showing us the camera qualities. I believe that Cisco is moving forward with this. In the next release, I would like to see improvements made to their security. Also, they have to introduce firewall compatibility in the UCS, as with Firepower where they have a dedicated box with their software, switches, and routing. It's a one-box solution and it would be a huge benefit for Cisco. Cisco depends on other vendors like IBM and HP for the hardware. Cisco should improve its hardware manufacturing in regards to the UCS and the use of other vendor's hardware.
If there were a way to make the upgrade process better, it would be great. Our most important issue right now is to resolve the installation barrier so we can use the product features fully. We needed to phase in new hardware and try again with Cisco HyperFlex M5. Also if we had one interface, it would solve some operating issues. If we can control all devices from one interface, I think it would help a lot.
I found it a bit of a challenge to get training on UCSM. I've been trying to get that for some time now. I feel like I have to figure out a lot of things myself. For years I've to log calls with support whenever I've got challenges that I cannot resolve. If I had some training or more manuals, I'd be better able to handle more things on my own. They should work to simplify the server creation template.