AMAX ServMax vs. HPE BladeSystem

HPE BladeSystem is functional for standard Windows and ESXi host usage. Although the design is over a decade old, its parts are up to current with today's processors and networks. BladeSystem is not suitable for applications that necessitate local storage, hyper-converged, or any other type of specialized PCI cards. Some of these use cases are better suited to the HPE Synergy platform, however that design is not without its own limitations.

Incentivized

• It ensures substantial process and system security in terms of infrastructure by keeping things running smoothly all the time.
• There are few things that are more helpful in day-to-day living than having straightforward controls and configurations.
• Capacity to keep a highly redundant system operating reliably.

Incentivized

• When using virtual connect, you, and not the network team, are in charge of managing the local area network and wide area network.
• In terms of fan management, when only a portion of the Blade Enclosure is in use, it is imperative that all Blades be located in the same area.
• It's not easy and is somewhat dated to manage FW.

Incentivized

We do not intend to make new investments in HPE BladeSystem as it is in the end-of-life phase and we have continued with the new HPE Synergy environment. It is therefore not a process of discarding, but of evolution. This environment will possibly continue to be used in the institution, but for less critical purposes and more related to the development of new solutions.

Incentivized

Incorporating HPE Blades Systems In order to house 16 physical servers, you just need 10 rack units instead of 32, which reduces the amount of heat produced and, in turn, the cost to cool the site. To have multiple Esx servers that can all be managed centrally, VMware virtualization is a must. HPE Blade Systems simplify the administration of several servers. You can develop pretty great projects with Onboard admin and Virtual connect. Virtualization is the best option.

Incentivized

• The number of ports required for connectivity to 16 physical server is reduced with BladeSystem, without compromising flexibility - so there is a 16x savings on the number of ports required on physical switching infrastructure.
• In-place upgrades to newer hardware are accommodated by virtualized MAC addresses and WWN's in the fabric of the BladeSystem.
• On a couple occasions, large scale outages have affected the environment because of an issue at the core of BladeSystem. Users should be aware of the fault domain caused by a single chassis and plan accordingly. Our issues were mitigated due to a second, separate chassis where we spread workloads.

Incentivized