Providing Out-of-Band Connectivity to Mission-Critical IT Resources

Vertiv Avocent ACS EOL: Choose Your Replacement Option

Old,Way,Or,New,Way,With,Business,Woman,Using,A

Vertiv discontinued their Avocent ACS6000 line of serial console servers at the end of 2018 and will stop supporting them on July 31, 2023 (or whenever your warranty expires). The Vertiv Avocent ACS EOL guide recommends the ACS8000 series as a direct replacement, but before you make the switch you should consider all your options.

In this blog, we’ll directly compare the ACS6000 to the ACS8000, as well as recommend an alternative replacement option for your EOL serial consoles.

Vertiv Avocent ACS EOL Model: ACS6000

The Vertiv Avocent ACS6000 series is an enterprise data center serial console server with support for remote out-of-band management and zero touch provisioning (ZTP). Vertiv offers on-premises management via their DSView™ management software, CLI (command line interface), and web app. The ACS6000 supports advanced authentication via Radius, TACACS+, LDAP/AD, NIS, and Kerberos, as well as one-time passwords (OTP). However, its automation capabilities are limited to ZTP and auto-sensing ports.

Vertiv Avocent ACS6000 tech specs

Serial console features:
  • SSH direct to consoles
  • Telnet, SSH, or a serial terminal connection
  • Multiple concurrent sessions
  • Automatic device name discovery
Pinout auto-detection: Cyclades and Cisco pinouts
Vendor neutral: No
CPU: PPC440Epx @ 533 MHz
DRAM: 256MB
Maximum ports: 48
Cellular failover: 3G/4G failover and OOB
Sensors: Internal temperature sensor
Operating system: Linux OS and DSViewTM management software
On-premises management: DSViewTM, CLI, web app
Cloud management: No
Automation:
  • Zero touch provisioning
  • Auto-sensing ports
Automation for end devices: No
Guest OS support: No
Authentication servers:
  • Local
  • Radius
  • TACACS+
  • LDAP/AD
  • NIS
  • Kerberos
Hardware security: Embedded FIPS 140-2 module
Two-Factor Authentication: Yes
Power management:
Power management integrated with serial session as well as the Vertiv GXT UPS

 

Vertiv Avocent ACS EOL Replacement Option: ACS8000

Vertiv’s direct replacement for the EOL ACS6000 is the ACS8000 series. To make your migration easier, the ACS8000 supports your existing ACS6000 configuration files and CLI scripts. In addition, the ACS8000 delivers new features such as an upgraded CPU, more RAM, and an environmental sensor port with support for temperature, humidity, leak, pressure, and contact sensors. 

Where the ACS8000 really improves upon the old EOL series is with automation—it supports RESTful API Python and Perl scripts and automated management of PDU (power distribution unit) and UPS (universal power supply) products. However, the ACS8000 still only provides on-premises management, and it doesn’t support integrations with third-party automation and orchestration solutions.

Vertiv Avocent ACS6000 vs. ACS8000 tech specs

 

  Vertiv Avocent ACS6000 Vertiv Avocent ACS8000
Serial console features:
  • SSH direct to consoles
  • Telnet, SSH, or a serial terminal connection
  • Multiple concurrent sessions
  • Automatic device name discovery
    • SSH direct to consoles
  • Keystroke logging
    • Telnet, SSH, or a serial terminal connection
  • Alert on cable disconnects
  • Multiple concurrent sessions
  • Automatic device name discovery
Pinout auto-detection: Cyclades and Cisco pinouts Cyclades and Cisco pinouts
Vendor neutral: No No
CPU: PPC440Epx @ 533 MHz Dual-core ARM® Cortex™-A9 MPCore™ with CoreSight™
DRAM: 256MB 1GB
Maximum ports: 48 48
Cellular failover: 3G/4G failover and OOB 3G/4G failover and OOB
Sensors: Internal temperature sensor
    • Environmental sensor port
    • Internal temperature
  • Door
  • Dry contact
  • Humidity
Operating system: Linux OS and DSViewTM management software Linux OS and DSViewTM management software
On-premises management: DSViewTM, CLI, web app DSViewTM, CLI, web app
Cloud management: No No
Automation:
  • Zero touch provisioning
  • Auto-sensing ports
    • Zero touch provisioning
    • Auto-sensing ports
  • RESTful API
  • Python
  • Perl
Automation for end devices No
  • Avocent Power Management
  • Vertiv MPH2 Rack PDU
  • Cyclades PM
  • Intelligent PDU
  • Avocent SPC power control devices
  • Server Technology
  • SentryTM Server Technology
  • SentryTM Power Tower
  • Eaton
  • Raritan
  • APC
Guest OS support: No No
Authentication servers:
  • Local
  • Radius
  • TACACS+
  • LDAP/AD
  • NIS
  • Kerberos
  • Local
  • Radius
  • TACACS+
  • LDAP/AD
  • NIS
  • Kerberos
Hardware security: Embedded FIPS 140-2 module Embedded FIPS 140-2 module
Two-Factor Authentication: Yes Yes
Power management: Power management integrated with serial session as well as the Vertiv GXT UPS Power management integrated with serial session as well as the Vertiv GXT UPS

 

Vertiv Avocent ACS EOL Replacement Option: Nodegrid Serial Console Plus (NSCP)

The ACS8000 addresses some of the weaknesses of the EOL ACS6000 series. However, if your enterprise needs a NetDevOps data center solution with next-gen features like cloud management and vendor-neutral orchestration support, then Vertiv’s models fall short.

The Nodegrid Serial Console Plus (NSCP) from ZPE Solutions delivers these features and more in a high-density, 96-port 1U rackmount design. The NSCP also provides hardened device security with on-board features like secure boot, encrypted disk, TPM 2.0 and geofencing, as well as embedded firewall security and SAML 2.0 authentication. Plus, the NSCP runs on Nodegrid OS, an open Linux-based architecture with full support for NetDevOps automation and orchestration solutions like Docker, Chef, Puppet, and Ansible.

Head-to-head: ACS6000 vs. ACS8000 vs. NSCP tech specs

 

  Vertiv Avocent ACS6000 Vertiv Avocent ACS8000 Nodegrid Serial Console Plus (NSCP)
Serial console features:
  • SSH direct to consoles
  • Telnet, SSH, or a serial terminal connection
  • Multiple concurrent sessions
  • Automatic device name discovery
  • SSH direct to consoles
  • Keystroke logging
  • Telnet, SSH, or a serial terminal connection
  • Alert on cable disconnects
  • Multiple concurrent sessions
  • Automatic device name discovery
    • SSH direct to consoles
  • Keystroke logging to ZPE Cloud
    • Alert on cable disconnects
  • Text pattern match
  • Multiple concurrent sessions
  • Automatic device name discovery
Pinout auto-detection: Cyclades and Cisco pinouts Cyclades and Cisco pinouts Cisco pinout
Vendor neutral: No No Yes
CPU: PPC440Epx @ 533 MHz Dual-core ARM® Cortex™-A9 MPCore™ with CoreSight™ Intel x86, 64 bit
DRAM: 256MB 1GB 4GB
Maximum ports: 48 48 96
Cellular failover: 3G/4G failover and OOB 3G/4G failover and OOB 5G/4G/LTE and Wifi failover and OOB
Sensors: Internal temperature sensor
  • Environmental sensor port
  • Internal temperature
  • Door
  • Dry contact
  • Humidity

External USB attached sensors:

  • Particulate
  • Smoke detector
  • Airflow and temperature
  • Proximity/door
  • Temperature
  • Humidity

Plus, a 7-port USB hub

Operating system: Linux OS and DSViewTM management software Linux OS and DSViewTM management software Flexible, open, 64-bit Linux-based Nodegrid OS optimized for integration with third-party automation and orchestration tools
On-premises management: DSViewTM, CLI, web app DSViewTM, CLI, web app Nodegrid Manager
Cloud management: No No ZPE Cloud Manager
Automation:
  • Zero touch provisioning
  • Auto-sensing ports
  • Zero touch provisioning
  • Auto-sensing ports
  • RESTful API
  • Python
  • Perl
    • Zero touch provisioning
    • Auto-sensing ports
    • Python
  • ZPE Cloud
  • Chef
  • Docker
  • KVM Hypervisor
  • Puppet
  • RedHat Ansible
  • Ruby
  • ShellScript
Automation for end devices No
  • Avocent Power Management
  • Vertiv MPH2 Rack PDU
  • Cyclades PM
  • Intelligent PDU
  • Avocent SPC power control devices
  • Server Technology
  • SentryTM Server Technology
  • SentryTM Power Tower
  • Eaton
  • Raritan
  • APC
  • ZPE Cloud
  • Chef
  • Docker
  • KVM Hypervisor
  • Puppet
  • RedHat Ansible
  • Ruby
  • ShellScript
Guest OS support: No No Ability to run VMs and Docker
Authentication servers:
  • Local
  • Radius
  • TACACS+
  • LDAP/AD
  • NIS
  • Kerberos
  • Local
  • Radius
  • TACACS+
  • LDAP/AD
  • NIS
  • Kerberos
    • Local
    • Radius
    • TACACS+
    • LDAP/AD
    • NIS
    • Kerberos
  • SAML 2.0 (Okta, DUO, PINGID, ADFS)
Hardware security: Embedded FIPS 140-2 module Embedded FIPS 140-2 module
  • TPM 2.0
  • BIOS protection
  • UEFI Secure Boot
  • Geofencing
Two-Factor Authentication: Yes Yes Yes
Power management: Power management integrated with serial session as well as the Vertiv GXT UPS Power management integrated with serial session as well as the Vertiv GXT UPS
    • Power management integrated with serial session (escape sequence in the serial session or power buttons in web serial session
  • Power control of VMs
  • Access rights for users and user groups

 Though the Vertiv Avocent ACS8000 series provides a close match to the capabilities of the EOL ACS6000 series, it fails to deliver the advanced features you need to achieve NetDevOps transformation. Only the Nodegrid Serial Console Plus gives you intuitive cloud management, hardened device security, and full automation and orchestration support.

Ready to replace your Vertiv Avocent ACS EOL serial console server with the Nodegrid Serial Console Plus?

Contact ZPE Systems online or call 1-844-ZPE-SYS.

Contact Us

How to Achieve Network Security: 4 Essential Steps for IT Professionals

shutterstock_356286569(1)
How critical is network security today?. According to IBM, the cost of a data breach rose to $4.24 million in 2021, and that figure continues to rise. In this blog, we’ll describe how to achieve network security through micro-segmentation, zero trust principles, cloud-based edge security, and network automation.

How to achieve network security: 4 essential steps for IT professionals

1. Shrink your perimeter

The traditional strategy for network security involves creating one large security perimeter around your entire enterprise network to protect all the data, accounts, devices, and applications contained within—even those hosted in the cloud, at remote branch offices, and in small edge data centers. The security controls and policies in use by this perimeter need to account for every single vulnerability and attack surface. Often, that leaves you with a complex, bloated patchwork of security appliances and services that are difficult to manage across multiple vendors and platforms. The harder it is to manage your security perimeter, the more likely you are to accidentally leave gaps in your coverage or miss the subtler signs of a potential breach.

To achieve network security in your enterprise, you need to shrink your perimeter and focus on protecting the individual data, applications, assets, and services at risk. You do this by micro-segmenting your network to logically separate your data, applications, assets, and services. This allows you to create micro-perimeters of highly specific policies and controls that account for the security risks, vulnerabilities, sensitivity, and value of each of your enterprise resources.

Shrinking your security perimeter and micro-segmenting your network also facilitates the implementation of zero trust security. Learn more about the importance of micro-segmentation for zero trust networks.

2. Never trust, always verify

Zero trust security is a proven strategy for protecting enterprise networks – in fact, the President signed an executive order in 2021 urging organizations to adopt a zero trust architecture. Zero trust security follows the principle of “never trust, always verify.” That means you don’t automatically assume the trustworthiness of any network entities even if they’re on your internal enterprise network. You also reduce the privileges granted to any individual account, making sure each network entity has access to the specific resources they need and nothing more. This reduces the lateral movement of a compromised account and limits the amount of damage that can be inflicted during an attack.

To apply and enforce zero trust access policies, you need an identity and access management (IAM) solution that allows you to dynamically and consistently assess an entity’s trustworthiness based on the context of the situation. Many IAM platforms utilize user and entity behavior analytics (UEBA), which monitors the activity of accounts and devices on your network to establish a baseline of behavior. UEBA can then use that baseline to determine when a network entity is behaving in a risky or unusual way, and then force that entity to reestablish trust before it accesses any new resources.

Zero trust security uses the methodology of “never trust, always verify” to limit the damage done by compromised user accounts and devices on your network. Learn more in our ultimate guide to a zero trust security model for an enterprise.

3. Secure your network edge

If your enterprise includes branch offices, work-from-home employees, small data centers, and other remote locations, you need a strategy to secure your network edge. Typically, that means backhauling all remote traffic through a firewall in the central data center, even if that traffic is bound for cloud resources. This can create bottlenecks in your enterprise network and reduce productivity.

Security service edge, or SSE, uses a cloud-based security stack to monitor and protect your remote, cloud-destined traffic without needing to route through your data center. SSE uses technologies like zero trust network access (ZTNA), secure web gateways (SWG), cloud access security brokers (CASB), and firewall as a service (FWaaS) to secure your edge traffic. Each of these security controls is delivered as a cloud-based service, so your remote users and devices can access your cloud resources securely without routing through your main firewall.

Security service edge, or SSE, provides enterprise-grade protection to your edge networks without impacting network performance or productivity. Learn more in What is security service edge (SSE)? Everything you need to know.

4. Reduce human error

According to Gartner, up to 99% of firewall breaches are caused by human error. When IT professionals need to manually configure and manage many different devices in a complex enterprise network, the risk of human error increases. A misconfigured security setting or user account could create vulnerabilities and leave you exposed to attacks. One way to reduce human error and the associated risk of a security breach is through network automation.

For example, zero touch provisioning can be leveraged to automatically configure and deploy network appliances. Software-defined networking (SDN) and infrastructure as code (IaC) are methods for decoupling device configurations from the underlying hardware, which allows you to use automated scripts to configure, update, and manage appliances and computing resources. Software-defined wide area networking, or SD-WAN, provides the same software abstraction and automation capabilities for your remote edge network infrastructure.

Network automation reduces the risk of configuration mistakes, which contributes to a more secure enterprise network. Plus, network automation is critical if you want to implement NetDevOps. Learn more about the importance of NetDevOps automation for modern networks.

To achieve network security, you need to rethink the old “castle and moat” strategy in which you have one big security perimeter (the moat) surrounding your entire enterprise and you assume everything within that perimeter (the castle) is safe and trustworthy. You should also consider a cloud-based approach to protecting your remote, cloud-destined traffic to improve the security and performance of your entire enterprise. Finally, you should use network automation to reduce the time you’re spending on tedious configurations, which will help eliminate configuration mistakes.

Achieve network security with the right solution

When you’re following the steps above, you’re likely to face a few challenges. For example, vendor lock-in can make it difficult to apply zero trust security controls or integrate third-party automation solutions. Additionally, to route your edge traffic through an SSE technology stack such as Zscaler or Cloudflare, you need an SD-WAN on-ramp with the ability to intelligently identify and re-route cloud-destined traffic. Plus, implementing all these security technologies can leave you with many different solutions to manage, increasing the complexity and difficulty of your enterprise network management.

ZPE Systems solves all these challenges with an innovative and vendor-neutral family of network management solutions. ZPE’s line of network edge routers and data center serial consoles runs on the Nodegrid OS, an open, x86 Linux-based operating system that allows easy integrations with zero trust security solutions and supports third-party automation via tools like Ansible and Chef. ZPE’s SD-WAN platform is the best on-ramp to your SSE stack, providing a secure, lightweight cloud solution from which to manage your edge network. Plus, with ZPE Cloud, you can consolidate management of your entire network behind one pane of glass, allowing you to efficiently deploy and orchestrate your network security strategy.

Want to learn more about how to achieve network security?

Visit our network security blog or contact ZPE Systems today.

Contact Us

ZPE Systems Announces TD SYNNEX Partnership to Bolster Growth Strategy

ZPETDS2

Fremont, CA  March 17, 2022 — ZPE Systems Inc., a leader in network infrastructure management and orchestration solutions, today announced a partnership with TD SYNNEX (NYSE: SNX), a leading global distributor and solutions aggregator for IT ecosystems. This agreement gives partners access to ZPE’s Intel-based Gen 3 out-of-band serial consoles & modular services router gateways, to serve large enterprises and MSPs with a platform for 3rd party applications and end-to-end automation for datacenter & branch edge deployments.

Legacy fixed-function devices do not meet modern requirements for scaling, automating, and securing enterprise networks, due to interoperability issues and closed architectures. As customers struggle against security and downtime-inducing network challenges, this partnership will enable them to deploy ZPE’s platform to address disaster recovery, human error, and ransomware, using their choice of best-of-breed vendor solutions. ZPE’s cloud managed Linux-based Nodegrid® is an open platform of programmable hardware and software that extends the capabilities of infrastructure, connectivity, and cybersecurity teams.

“Cyber and physical systems are increasingly connected,” said Reyna Thompson, Senior Vice President, Product Management at TD SYNNEX. “This means organizations across all verticals are now calling for a networking platform that enables them to mix and match the solutions that work best for their use case. This partnership strengthens our portfolio. Customers can now deploy ZPE’s platform to integrate the physical and virtual solutions they need, to make their networks secure, reliable, and easy to use.”

The Linux-based Nodegrid OS, which runs on every Nodegrid Serial Console and Services Router device, enables multi-vendor freedom in IT. This allows infrastructure, connectivity, and cybersecurity teams to deploy and manage their choice of hardware, software, and SaaS solutions — from cooling and smart PDUs, to switches and servers, to NGFWs, SD-WAN and SASE integrations. The Nodegrid platform integrates with new and existing infrastructure, providing secure out-of-band access, NetDevOps automation capabilities, and enterprise-grade security that address modern business demands.

“Teaming up with TD SYNNEX is a huge value add to ZPE ​​Systems’ Edge Transformation Partner Program,” said Steven Jehring, Vice President, Global Sales, ZPE Systems. “This gives partners greater financing options, while customers get more freedom to choose a partner that’s right for them. TD SYNNEX’s world-class support, pre-sales services, and global fulfillment capabilities will be instrumental in accelerating partner sales and transforming customer networks at the data center and edge.”

To learn more or become a ZPE Systems partner, visit partners.zpesystems.com.

Read the source version on Business Wire.

Data Lake Use Cases for Edge Networking

Stock,Trading,Concept,With,Downtown,Chicago,Cityscape,Skyline,With,Lake

Data lakes are a powerful tool for capturing, storing and analyzing data from many different sources. A data lake provides an inexpensive, flat storage architecture in which to house massive amounts of unstructured data, which can then be easily accessed by your data analysis applications, data scientists, or artificial intelligence (AI) programs.

There are many potential data lake use cases for edge networking, which generate a lot of data from many different sources. In this blog, we’ll describe how data lakes can help process your edge data from remote environmental monitoring solutions and internet of things (IoT) devices.

 

Data lake use cases for edge networking

Internet of Things (IoT) data from isolated locations

Internet,Of,Things,And,Home,Automation,Concept:,User,Connecting,With

Internet of things (IoT) devices relies on sensors to capture and process the data necessary for their function. However, most of this data is irrelevant for the task at hand, and may not have a critical use at the time it’s collected. However, as in the example above, that doesn’t mean this data has no value—and if you delete it, you may miss crucial warnings or key opportunities.

When your IoT devices are at your network edge, especially in remote or dangerous locations, that makes data collection and processing even more challenging. For example, many offshore oil rigs are in the deep ocean, miles away from the nearest land. Much of the critical machinery is underwater and inaccessible to humans. IoT sensors and actuators can monitor, control, and collect data from this equipment without putting any engineers in harm’s way.

Some IoT sensor data is immediately actionable, but what do you do with the rest? With a data lake, you can store all this valuable information, even if you’re not sure what to do with it yet. Or, you can integrate a big data solution that uses AI to inspect and analyze sensor data in real-time, helping you spot issues and opportunities that you weren’t even looking for.

Let’s say you remotely manage several rural factories that use industrial printers equipped with IoT sensors. These sensors track consumable usage, detect nozzle clogs, and alert you when there’s an error. The printer manufacturer recommends that you take these machines offline every 90 days for maintenance, which causes significant production delays. However, your data lake analytics show that, according to sensor logs, these printers are capable of operating for at least 120 days before any maintenance-related issues pop up. You could use this information to extend the period between maintenance windows, increasing plant efficiency and reducing production delays without ever setting foot on the factory floor. Plus, having sensors enables you to pinpoint exactly what part of the printer needs maintenance, which shortens maintenance times.

You can use a data lake to store and analyze data from your edge network IoT devices, which helps you prevent and detect issues as well as improve your operational efficiency.

 

Environmental monitoring data from remote infrastructure

Cloud,Computing,Technology,Network,With,Computer,Monitor,,Laptop,,And,Mobile
Edge networks can be highly geographically distributed, which means you may not have physical eyes on all of your equipment. That makes it difficult to spot environmental risks like water leaks or rising temperatures that could bring down your edge infrastructure if left unmitigated.

One way to monitor the condition of your equipment from far away is with environmental sensors, which can detect things like moisture, overheating, and physical tampering. However, environmental monitoring systems produce a lot of data. Often, network engineers weed out the “irrelevant” data by creating alarms and workflows that are triggered when environmental conditions pass a certain threshold. While this works well enough for reacting to issues that are already occurring, it limits your ability to predict future problems or find opportunities for optimization.

Connecting your environmental monitoring solution to a data lake gives you the ability to efficiently store all your raw sensor data, so you don’t have to throw out any potentially valuable information. With a data lake, you don’t have to strictly prioritize which environmental monitoring data you keep. Even if you don’t have a specific use for that information right now, you may find one later. Historical data is often invaluable for troubleshooting systemic issues or finding ways to use resources more efficiently.

For example, let’s say you want to lower your energy costs by using air cooling systems more efficiently. With a data lake, you can collect and store temperature data from all your locations over the course of months or even years without worrying about running out of space on your local SAN. You can then use data analytics to view temperatures over time and correlate them with your energy bills to determine how expensive it is to cool your infrastructure in each location. Perhaps you could reduce A/C usage in your Minnesota branch, or maybe you need to invest in a more efficient cooling system for your Nevada warehouse.

Using a data lake for your edge infrastructure environmental monitoring means you can store and use all your valuable sensor data to prevent issues, spot trends, and optimize processes even from thousands of miles away.

Nodegrid Data Lake for Your Edge Networking Use Case

Though data lakes are a powerful tool, many solutions have limitations when it comes to edge networking. For example, some data lakes use an on-premises appliance that must be accessed from the enterprise network, which means your edge infrastructure has to connect over a VPN or WAN link. Other data lake solutions provide only storage, and don’t offer any built-in organization tools, analytics, or visualizations.

Nodegrid Data Lake is a solution built for the edge, with an entirely cloud-based interface that your users and devices can connect to from anywhere in the world. The Nodegrid control panel provides visual analytics on six key data points, including infrastructure, application, security, environmental, networking, and system logs. Nodegrid Data Lake even collects previously hidden server and switch logs from IPMI and RS232 serial consoles.

Plus, with Nodegrid environmental sensors and ZPE Cloud, you can monitor and manage your entire edge infrastructure from behind one pane of glass. The Nodegrid family of hardware and software is a complete edge networking solution.

To learn more about data lakes, read What Is a Data Lake, and Who Needs It? For more information about Nodegrid Data Lake use cases for edge networking, call 1-844-4ZPE-SYS or contact ZPE Systems online.

Data Center Temperature & Humidity Best Practices: A Complete Checklist

Businessman,Holding,Pencil,At,Complete,Checklist,With,Tick,Marks.,Business

Temperature and humidity have a significant impact on your data center infrastructure. High temperatures can cause devices to overheat, whereas extreme low temperatures can cause mechanical and electrical failures. High humidity can lead to moisture build-up, corrosion, and shorts, but low humidity can lead to electrostatic discharge. That’s why it’s critical that you monitor the environment in your cabinets and follow data center temperature and humidity best practices.

Data center temperature and humidity guidelines

Each piece of data center equipment—including enterprise servers, storage devices, switches, firewalls, and other appliances—has a recommended temperature and humidity range at which it operates most efficiently. However, you can’t create individual climates for each piece of gear, because it all needs to coexist in the same space. That’s why broader guidelines exist, such as those provided by ASHRAE (the American Society of Heating, Refrigerating and Air-Conditioning Engineers).

ASHRAE outlines four classes, based on temperature and humidity sensitivity, into which you can organize your data center equipment. Plus, arranging the layout of your data center to account for these classes can help you manage environmental conditions more efficiently (more on that later). The four equipment classes are:

A1: The most sensitive enterprise servers, legacy hardware, and specialty equipment that requires the strictest level of environmental control.

  • Temperature range: 15°C (59°F) to 32°C (89.6°F)
  • Relative humidity range: 20% to 80%

A2: Most modern servers, appliances, storage devices, and personal workstations fall into this class.

  • Temperature range: 10°C (50°F) to 35°C (95°F)
  • Relative humidity range: 20% to 80%

A3: Some newer equipment that’s designed to withstand a broader range of temperatures and humidity.

  • Temperature range: 5°C (41°F) to 40°C (104°F)
  • Relative humidity range: 8% to 85%

A4: Equipment that’s specifically made to operate in extreme environments.

  • Temperature range: 5°C (41°F) to 45°C (113°F)
  • Relative humidity range: 8% to 90%

It’s important to note that there is still a “sweet spot” where a piece of equipment will perform best even within these recommended temperature ranges. The key is to balance that performance against other devices’ cooling costs and needs in the same rack or cabinet.

Data center temperature and humidity best practices: a complete checklist

Now, let’s dig into the data center temperature and humidity best practices to help you achieve these standards.

1. Monitor rack conditions, not just room conditions

The location of your sensors matters a lot. Simply monitoring the ambient temperature and humidity in the room doesn’t give you an accurate picture of the conditions in each rack. Different spots within the room may report different readings depending on the location of the cooling system vents, how particular hot machines are running, and other factors.

Instead, data center temperature and humidity best practices recommend installing multiple sensors in each cabinet. You need to monitor the air that’s flowing into your equipment, so to get the most accurate readings you should place your sensors near the air intake vents (typically at the front of a rack-mount chassis).

2. Calculate and optimize your power usage effectiveness (PUE)

Power usage effectiveness, or PUE, is a metric that data center infrastructure management (DCIM) engineers track to determine their data center’s energy efficiency. You calculate data center PUE by dividing the amount of power flowing into the facility by the power usage of the devices and infrastructure contained within. The higher your PUE number, the less efficiently you’re using your power. According to Uptime Institute’s annual Global Data Center Survey, the average PUE was 1.57 in 2021. You want your PUE to be as close to 1 as possible, but at the bare minimum, you should strive to meet that average number.

Data center HVAC (heating, ventilation, and air conditioning) systems are notorious power hogs. You need to keep temperature and humidity within acceptable limits, but you also need to consider the power costs—both in terms of money and your data center carbon footprint. Keeping an eye on your PUE will help you determine that balance.

3. Design for more efficient cooling

If your PUE is too high, you should look into more efficient cooling techniques to build on that last point. Data center cooling systems are known as CRACs (computer room air conditioners) or CRAHs (computer room air handlers). CRACs use refrigerants and compressors to cool the air, whereas CRAHs blow air across chilled water. Both systems require a lot of power, but there are ways to increase your cooling efficiency without increasing your energy consumption.

For example, you can strategically arrange your data center equipment to maximize cooling efficiency. In a smaller server room, you could place your highly sensitive, A1-class equipment closest to your cooling system. The best practice is in large data centers and colocation facilities to have “hot and cold aisles.” That means arranging cabinet aisles back-to-back, so all the hot air venting out the back of your equipment flows to the exit vents in one concentrated stream.

It would be best if you always strived to stay within the temperature and humidity guidelines specified by device manufacturers, and your data center should follow the environmental standards outlined by ASHRAE. These data center temperature and humidity best practices for environmental monitoring, power usage tracking, and efficient cooling will help you meet those standards while saving money and optimizing performance.

4. Monitor the environment in your cabinets

Environmental monitoring sensors collect data on the conditions in your rack so you can ensure that the temperature and humidity are within recommended limits. Some best practices for data center environmental monitoring include:

  • If you’re managing remote data center infrastructure, you should implement remote out-of-band management, which provides a dedicated connection to your environmental sensors even during a network outage.
  • Temperature and humidity aren’t the only data center environmental risks. Your environmental monitoring solution should also include sensors for tampering, smoke, airflow, dust, and particulates.
  • You can’t keep your eyes on your monitoring logs 24/7, so you should set up automatic alerts, so you’ll be notified if conditions exceed expected thresholds. To gain even more control, you should look for an environmental monitoring solution that includes web dashboards with visualizations so you can track conditions over time and spot opportunities for optimization.

Achieve comprehensive data center temperature and humidity monitoring with Nodegrid

Nodegrid’s line of environmental monitoring sensors gives you a complete picture of the conditions in your rack so you can follow data center temperature and humidity best practices. With sensors for airflow and temperature, particulates, smoke, proximity, temperature, and humidity, you can keep a close eye on your physical equipment even from thousands of miles away.

ZPE Cloud provides a cloud-based web portal to monitor and manage your sensors, with analytics and visualizations to help you monitor power usage trends, detecting temperature spikes, and more. Plus, when you connect your rack infrastructure to Nodegrid Serial Consoles, you get reliable, secure out-of-band access to your environmental sensors and other data center devices, even during a network outage.

Learn more about data center environmental monitoring

Learn more about Nodegrid’s data center solutions

Need more help achieving data center temperature and humidity best practices with Nodegrid?

Reach out to contact ZPE Systems online or call 1-844-4ZPE-SYS.

Contact Us