Skip to main content

In Hyperscale Environments Network Visibility Remains Vital

Mike Heumann

Hyperscale infrastructure was once widely considered to be designed for large, web-facing organizations or top-tier colocation and cloud providers. But as the enterprise starts to confront the realities of big data and mobile, dynamic workloads, it seems inevitable that even medium-sized organizations will have to encounter hyperscale environments at some point, either as greenfield deployments or in a hosted/cloud capacity – and we’re seeing this come to fruition. According to an October 2014 Emulex survey of more than 1,600 US and European IT professionals who provided insight into their enterprise data center networking environments, 57 percent of respondents have adopted hyperscale networking environments.

What are the ramifications of this? More than half of these (51 percent) named increasing bandwidth as a major challenge in moving to hyperscale environments, which is driving massive network upgrades. In fact, more than 77 percent of respondents running hyperscale environments say the move to the cloud has already necessitated the upgrade of their networks to at least 40Gb Ethernet. Big data and analytics are driving high volumes of data storage, capture, movement and archiving which all drive an increased need for both higher bandwidth and lower latency on 10Gb and 40Gb Ethernet using RDMA.

We’re seeing hyperscale network environments grow across enterprises because it has a number of benefits: It can be a key piece of smarter, more manageable application ecosystems. On a network level, hyperscale can also aid business continuity and disaster recovery efforts by providing redundant failover architecture and rapid recovery. Hyperscale can also accentuate the benefits that technologies like virtualization and software-defined networking provide, making it a potentially vital configuration in the more scalable data center machinery of the future.

As we know, the loss of application or network services for even a few minutes can mean huge and immediate revenue losses, and can impact long-term customer loyalty. As many enterprises go through these rapid network changes and as hyperscale environments become more common, it is important that IT networking and application staffs prioritize network visibility as a means to identify any network issues that need to be identified quickly. Many organizations are struggling to accurately monitor increasingly complex enterprise networks as they shift to 10Gb Ethernet or even higher speeds.  

For those running hyperscale environments, 97 percent said it has necessitated a move to 10GbE, 40GbE or higher speeds to meet demands of high-performance applications such as big data, analytics and content distribution, compared to only 48 percent of respondents from non-hyperscale organizations. As a result, the underlying communication networks matter, and perhaps not surprisingly, capturing network behavior for incident detection and monitoring network flows for anomalous behavior are just as important. The ability to do both of these is essential in many high-speed networks (such as trading platforms and e-commerce portals) in order to spot cyber threats like DDoS attacks. The migration to larger, faster networks only exacerbates the threat of missing these attacks, and increases the need for clear, deep visibility.

Mike Heumann is VP of Product Marketing and Alliances at Emulex.

Hot Topics

The Latest

Pilots are everywhere, stakeholders are seeking results, businesses are pushing for new tools, and IT teams are being asked to make AI secure, reliable, and useful at scale. But as organizations move from testing AI to operationalizing it, many are discovering that the biggest barrier is not the model, the use case, or even the budget. It is the file data foundation within ...

Fast or cheap? For most of my career in engineering, speed and quality sat on opposite ends of a seesaw. The "OR" in "fast or cheap" was non-negotiable. It was expected that pushing for faster releases meant that something in quality would give way. Tightening quality controls meant the schedule slipped. Every engineering leader I know has lived some version of that tradeoff ... The seesaw is starting to level out ...

I have been building enterprise software for more than 20 years ... One thing stays true across all of it: You do not find out your foundation is wrong during the crisis. You find out when the debt comes due. For a lot of organizations, that bill is arriving now. New research ... puts hard numbers on something practitioners have been sensing for a while. The telemetry problem isn't coming. It's already here ...

The rapid growth of AI workloads is pushing traditional log management approaches to their limits, according to The State of Log Management 2026 report from Dynatrace. Modern logs have become critical to understanding, validating, and securing AI-driven decisions, helping organizations ensure reliability, compliance, and performance at scale. However, the volume and complexity of AI telemetry are overwhelming legacy tools ...

For years, secure connectivity has relied on a familiar pattern: route traffic back to centralized gateways, inspect it, and then allow access. This model worked when applications lived in a handful of data centers and users were largely confined to offices. That model is now under strain. Applications are distributed across clouds, users connect from everywhere, and real-time workloads demand performance that centralized inspection points struggle to deliver. As traffic volumes grow and latency expectations shrink, routing everything through a small number of control points has become both a performance bottleneck and a resilience risk. The future of secure connectivity requires a different approach ...

The AI experimentation phase is over, and the private cloud is where enterprise AI workloads are being deployed for security and scale, according to Private Cloud Outlook 2026, a new report from Broadcom ... 2026 marks an acceleration into a full AI tipping point. The shift is being shaped by three forces — costs, complexity, and control — that public cloud environments are increasingly failing to address for production AI at scale. Key findings from the report include ...

44% of organizations have reported an outage in the past year tied to suppressed or ignored alerts, and 78% had at least one incident where no alert was fired at all ... Engineers learned about failures from customers. That gap between what our tools report and what our customers experience is the problem DevOps teams have been quietly solving with GenAI tooling, even as most enterprises continue to run their NOCs on manual alert triage ...

Cloud outages are usually described as technical failures. When a service goes down, a dependency breaks, or a region has issues, the focus immediately shifts to infrastructure. But if you look closely at how these incidents actually unfold, the root cause is rarely the technology itself. It is almost always tied to decisions made earlier, during design, implementation, or day-to-day operations. The system behaves the way it was built. The real question is how it was built ...

77% of leaders say their teams need AI skills urgently. 64% say their organization plans to train current employees rather than hire new ones. So far, so reasonable. The part that surprised me is who's been put in charge: 34% of those leaders say IT and engineering own the AI skills mandate. Learning and Development or HR own it at 7% of organizations. That's roughly five-to-one in favor of the people who understand the tools, over the people whose actual job is teaching adults how to learn new ones ...

In the ever-evolving digital landscape, enterprises are increasingly focused on enhancing their observability stacks to gain deeper insights into their IT environments. Observability has become a cornerstone of modern IT operations, enabling organizations to monitor, diagnose, and optimize their systems with unprecedented precision. However, a critical piece of the puzzle often goes unnoticed in this transformation: IBM i ...

In Hyperscale Environments Network Visibility Remains Vital

Mike Heumann

Hyperscale infrastructure was once widely considered to be designed for large, web-facing organizations or top-tier colocation and cloud providers. But as the enterprise starts to confront the realities of big data and mobile, dynamic workloads, it seems inevitable that even medium-sized organizations will have to encounter hyperscale environments at some point, either as greenfield deployments or in a hosted/cloud capacity – and we’re seeing this come to fruition. According to an October 2014 Emulex survey of more than 1,600 US and European IT professionals who provided insight into their enterprise data center networking environments, 57 percent of respondents have adopted hyperscale networking environments.

What are the ramifications of this? More than half of these (51 percent) named increasing bandwidth as a major challenge in moving to hyperscale environments, which is driving massive network upgrades. In fact, more than 77 percent of respondents running hyperscale environments say the move to the cloud has already necessitated the upgrade of their networks to at least 40Gb Ethernet. Big data and analytics are driving high volumes of data storage, capture, movement and archiving which all drive an increased need for both higher bandwidth and lower latency on 10Gb and 40Gb Ethernet using RDMA.

We’re seeing hyperscale network environments grow across enterprises because it has a number of benefits: It can be a key piece of smarter, more manageable application ecosystems. On a network level, hyperscale can also aid business continuity and disaster recovery efforts by providing redundant failover architecture and rapid recovery. Hyperscale can also accentuate the benefits that technologies like virtualization and software-defined networking provide, making it a potentially vital configuration in the more scalable data center machinery of the future.

As we know, the loss of application or network services for even a few minutes can mean huge and immediate revenue losses, and can impact long-term customer loyalty. As many enterprises go through these rapid network changes and as hyperscale environments become more common, it is important that IT networking and application staffs prioritize network visibility as a means to identify any network issues that need to be identified quickly. Many organizations are struggling to accurately monitor increasingly complex enterprise networks as they shift to 10Gb Ethernet or even higher speeds.  

For those running hyperscale environments, 97 percent said it has necessitated a move to 10GbE, 40GbE or higher speeds to meet demands of high-performance applications such as big data, analytics and content distribution, compared to only 48 percent of respondents from non-hyperscale organizations. As a result, the underlying communication networks matter, and perhaps not surprisingly, capturing network behavior for incident detection and monitoring network flows for anomalous behavior are just as important. The ability to do both of these is essential in many high-speed networks (such as trading platforms and e-commerce portals) in order to spot cyber threats like DDoS attacks. The migration to larger, faster networks only exacerbates the threat of missing these attacks, and increases the need for clear, deep visibility.

Mike Heumann is VP of Product Marketing and Alliances at Emulex.

Hot Topics

The Latest

Pilots are everywhere, stakeholders are seeking results, businesses are pushing for new tools, and IT teams are being asked to make AI secure, reliable, and useful at scale. But as organizations move from testing AI to operationalizing it, many are discovering that the biggest barrier is not the model, the use case, or even the budget. It is the file data foundation within ...

Fast or cheap? For most of my career in engineering, speed and quality sat on opposite ends of a seesaw. The "OR" in "fast or cheap" was non-negotiable. It was expected that pushing for faster releases meant that something in quality would give way. Tightening quality controls meant the schedule slipped. Every engineering leader I know has lived some version of that tradeoff ... The seesaw is starting to level out ...

I have been building enterprise software for more than 20 years ... One thing stays true across all of it: You do not find out your foundation is wrong during the crisis. You find out when the debt comes due. For a lot of organizations, that bill is arriving now. New research ... puts hard numbers on something practitioners have been sensing for a while. The telemetry problem isn't coming. It's already here ...

The rapid growth of AI workloads is pushing traditional log management approaches to their limits, according to The State of Log Management 2026 report from Dynatrace. Modern logs have become critical to understanding, validating, and securing AI-driven decisions, helping organizations ensure reliability, compliance, and performance at scale. However, the volume and complexity of AI telemetry are overwhelming legacy tools ...

For years, secure connectivity has relied on a familiar pattern: route traffic back to centralized gateways, inspect it, and then allow access. This model worked when applications lived in a handful of data centers and users were largely confined to offices. That model is now under strain. Applications are distributed across clouds, users connect from everywhere, and real-time workloads demand performance that centralized inspection points struggle to deliver. As traffic volumes grow and latency expectations shrink, routing everything through a small number of control points has become both a performance bottleneck and a resilience risk. The future of secure connectivity requires a different approach ...

The AI experimentation phase is over, and the private cloud is where enterprise AI workloads are being deployed for security and scale, according to Private Cloud Outlook 2026, a new report from Broadcom ... 2026 marks an acceleration into a full AI tipping point. The shift is being shaped by three forces — costs, complexity, and control — that public cloud environments are increasingly failing to address for production AI at scale. Key findings from the report include ...

44% of organizations have reported an outage in the past year tied to suppressed or ignored alerts, and 78% had at least one incident where no alert was fired at all ... Engineers learned about failures from customers. That gap between what our tools report and what our customers experience is the problem DevOps teams have been quietly solving with GenAI tooling, even as most enterprises continue to run their NOCs on manual alert triage ...

Cloud outages are usually described as technical failures. When a service goes down, a dependency breaks, or a region has issues, the focus immediately shifts to infrastructure. But if you look closely at how these incidents actually unfold, the root cause is rarely the technology itself. It is almost always tied to decisions made earlier, during design, implementation, or day-to-day operations. The system behaves the way it was built. The real question is how it was built ...

77% of leaders say their teams need AI skills urgently. 64% say their organization plans to train current employees rather than hire new ones. So far, so reasonable. The part that surprised me is who's been put in charge: 34% of those leaders say IT and engineering own the AI skills mandate. Learning and Development or HR own it at 7% of organizations. That's roughly five-to-one in favor of the people who understand the tools, over the people whose actual job is teaching adults how to learn new ones ...

In the ever-evolving digital landscape, enterprises are increasingly focused on enhancing their observability stacks to gain deeper insights into their IT environments. Observability has become a cornerstone of modern IT operations, enabling organizations to monitor, diagnose, and optimize their systems with unprecedented precision. However, a critical piece of the puzzle often goes unnoticed in this transformation: IBM i ...