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

How to Use a Cloud Managed Gateway Router to Optimize OT Automation

cloud managed gateway router

The right cloud managed gateway router simplifies edge network management and unlocks remote access to operational technology (OT). In this blog, we’ll explain what OT automation is, how to manage it with a gateway router, and what to look for in an ideal solution.

What is operational technology (OT)?

Operational technology, or OT, controls equipment interacting with the physical world. The term is used to differentiate these systems and devices from information technology (IT), focused on non-physical data computing.

OT manages the physical equipment used for industrial manufacturing, water and energy utilities, medical procedures, building management, and other physical processes.

Some examples of operational technology include:

  • Programmable logic controller (PLC) – Controls assembly lines, industrial machines, robotic devices, and other manufacturing processes.
  • Supervisory control and data acquisition (SCADA) – A control system for high-level supervision of industrial machines and processes, including PLCs.
  • Building management system (BMS) and Building automation system (BAS) – manage a building’s mechanical and electrical equipment such as lighting and HVAC.

OT facilitates industrial automation, by reducing manual intervention required to control and optimize physical technology. OT automation systems are traditionally isolated from IT networks, running on specialized industrial computers. However, modern OT systems are converging with IT to allow operators to manage them via network-connected PC or even from a cloud platform.

Using a cloud managed gateway router to optimize OT automation

Frequently, OT devices operate outside your main headquarters, in remote facilities such as factories, warehouses, data centers, and branch offices. In the past, that meant you needed operational technology installed at each location, with operators on-site to monitor OT automation computers. However, IT/OT convergence enables you to connect operational technology to edge network gateway routers, facilitating remote control via specialized software or a cloud-based application.

Gateway routers connect remote facilities to WAN or SD-WAN architectures, providing seamless and secure access to enterprise network resources. They also provide administrators with access to monitor and manage edge network routing and security. Some gateway routers also function as serial console routers, which means they can be used to directly manage the devices connected to them—including operational technology. A cloud managed gateway router with serial console capabilities gives administrators the ability to control remote networking and OT systems anywhere.

One of the issues with remote OT automation is that it may consist of several different systems and applications. For example, a managed service provider (MSP) may need to control HVAC, power distribution, security systems, and other infrastructure for many different clients using a variety of OT computers. They may even have some old analog gauges in place which they monitor with a cheap IoT camera.

Each of these disparate OT systems has its own application or cloud portal that operators must learn, configure, and manage, which is inefficient and creates risk of human error. A vendor-neutral cloud managed gateway router can solve this problem by bringing all your OT applications together under one unified platform.

What to look for in a cloud managed gateway router

Not all cloud managed gateway routers are optimized for OT automation. Let’s examine what an ideal solution looks like.

★ Hardware

The gateway router itself should use high quality hardware, and it should integrate with high quality operational technology hardware as well. You should secure the router hardware with features like cryptographic modules and geofencing to prevent tampering if the devices are stolen or intercepted in transit. A vendor neutral gateway router also needs to support various hardware connections such as RS-232, RJ-45, USB, and IPMI so you can ensure compatibility with your various OT systems, including analog and IoT solutions.

★ Operating System

The OS that runs on the cloud managed gateway router should be hardened and frequently patched to prevent hackers from exploiting vulnerabilities. The provider will update an ideal solution, so you don’t have to constantly stay abreast of all new security vulnerabilities or keep on top of the vendor’s patch schedule. A vendor neutral gateway router should run on an open, Linux-based OS to allow easy integrations with OT software.

★ Zero touch provisioning

Zero touch provisioning (ZTP) allows you to automatically deploy device configurations over a network connection. A cloud managed gateway router should have ZTP capabilities both for itself and for other connected devices. This eliminates the need for pre-staging so that you won’t risk a configured device falling into the wrong hands during shipping. It also reduces the need for engineers to travel on-site to install and configure new devices, saving time and money.

★ Connectivity

The gateway router’s primary job is to provide remote systems and users with a reliable connection to the enterprise network, ideally using SD-WAN technology. It should also provide a dedicated out-of-band (OOB) management connection, so administrators have reliable access to control and troubleshoot the remote network. An ideal solution includes high-speed failover via 4G/5G to ensure seamless connectivity for both administrators and end-users.

★ OOB provisioning and management

Provisioning and changing device configurations over the production network is risky. There’s always the chance that a configuration mistake could take the whole network offline. That’s another reason why a cloud managed gateway router should provide an OOB network connection, so you can deploy and modify device configurations without affecting the production network.

★ Orchestration

A cloud managed gateway router should provide orchestration so you can coordinate automated tasks and workflows across all your OT systems. This brings all OT applications together behind one pane of glass, facilitating efficient management and powerful optimization. End-to-end OT automation at the edge is only possible with a truly vendor-neutral gateway router that supports integrations with your choice of OT solutions, automation tools, and scripting languages.

A cloud managed gateway router with these features will empower efficient OT automation at the edge.

Why choose the Nodegrid cloud managed gateway router solution?

The Nodegrid line of cloud managed gateway routers delivers powerful edge network management optimized for operational technology automation. Features like secure zero touch provisioning and gen 3 OOB management support efficient and low-risk operational technology deployments while ensuring constant availability. Nodegrid’s vendor-neutral hardware, operating system, and cloud-based management platform can integrate all your OT solutions for true end-to-end orchestration.

Learn more about edge network orchestration:

→  Simplifying Network Edge Orchestration with a Single Platform
→  Edge Computing Trends to Expect in the Post-Covid World
→  Out-of-Band Is a Lifesaver for Critical Edge Networking. Here’s Why…

Learn more about the Nodegrid cloud managed gateway router.

Call 1-844-4ZPE-SYS or  Contact us online!

Contact Us

Part 2: Immutable Infrastructure: Best Practices for Network Professionals

immutable infrastructure best practices
Immutable infrastructure involves servers, network appliances, and other devices which are never updated or changed. In part 1 of our blog series, we discussed the most inherent challenges with the immutable infrastructure paradigm. This post will cover immutable infrastructure best practices that you should follow to overcome these challenges and fully embrace immutable principles in your enterprise.

Immutable infrastructure best practices for network professionals

Infrastructure as Code (IaC)

Infrastructure as code, or IaC, uses software abstraction to separate infrastructure configurations from the underlying hardware, allowing you to write configurations as repeatable scripts that you can deploy to many different devices. It also facilitates automation and orchestration through tools like RedHat Ansible, which stores and automatically executes configuration scripts according to predefined playbooks.

IaC is used traditionally for physical and virtual server configurations, but you can also use it to create and maintain virtualized network device configurations. This is sometimes called network infrastructure as code or software-defined networking (SDN). SDN goes beyond just abstracting configurations from the underlying networking hardware. It virtualizes your entire network, creating an overlay for managing and optimizing network routing, load balancing, segmentation, and more.

IaC is an immutable infrastructure best practice because it allows you to create and deploy configurations quickly and at scale. It enables truly immutable infrastructure that you can copy, delete, and replace at will. Without IaC, you must provision each new and updated instance manually. Even with a large team of engineers, updates could take a long time, and intermediate periods during which different versions of the same server or network configuration were active simultaneously will appear. Plus, manual configurations are error-prone, and mistakes could create vulnerabilities in your network.

Infrastructure as code and network infrastructure as code allow you to deploy virtual configurations programmatically and automatically. For immutable infrastructure, IaC is frequently used to deploy and configure images for containers and other virtualized environments.

Golden images

A golden image is a standardized template for physical or virtualized infrastructure. You start with a base image with only the software and settings required universally across all instances of that device. Then, you install any agents or services needed for monitoring, threat detection, analysis, etc. Finally, you harden the image with security policies and tools, and patch any known security vulnerabilities. Once the golden image is complete, you freeze it so no further changes can be made.

Best practices for creating, securing, and updating golden images for immutable infrastructure include:

  • Incorporate as many dependencies and settings as possible in your golden image to reduce the amount of configuration that needs to happen at deployment. This will ensure that the golden image you’ve tested and validated is as close as possible to the final production configuration. It will also make it faster and easier to scale.
  • Continuously scan and analyze golden images for new security vulnerabilities. That way, you can create and deploy patched versions as soon as possible, hopefully before a malicious actor has time to exploit those vulnerabilities.
  • Fully decommission old images once they’ve been replaced with newer, more secure versions. This will ensure a consistent and secure environment, and decrease the risk of accidentally spinning up new instances with old images.
  • Store golden images in multiple locations on a micro-segmented network. Use zero trust security to create granular policies and build  customized micro-perimeters around your golden images. This will protect your images from exfiltration or unauthorized modifications. It will also ensure access to golden images for recovery purposes even if you must isolate particular micro-segments during a breach.

Golden images for virtualized servers and network devices can be deployed, modified, and updated through IaC orchestration platforms—Like AWS, Azure, etc. This further streamlines the provisioning of immutable infrastructure, ensures consistent configurations across instances, and facilitates fast and easy scaling.

Stateful and persistent data

You should strive to make infrastructure and data as ephemeral as possible. Still, there are cases where you’ll need data to persist as you’re creating, deleting, and copying immutable resources. For stateful and persistent data, you should use mountable storage attachable to new instances when old ones are terminated.

Make sure you separate the ephemeral data from stateful/persistent data, so you only keep what you absolutely need to. This will help you reduce storage costs and simplify your overall operations. In addition, you should ship log files off immutable instances and send them to a centralized monitoring server as frequently as possible to ensure they persist.

Implementing immutable infrastructure best practices in your enterprise

Many of these immutable infrastructure best practices rely on modern, software-defined technology stacks, making it challenging to apply them to legacy infrastructure. You also need clear, centralized orchestration to see and control every piece of your immutable infrastructure, even across highly distributed networks with remote branch and edge locations. Finally, all of your immutable infrastructure solutions must work together seamlessly regardless of vendor or ecosystem.

ZPE Systems can solve all these challenges with the Nodegrid network orchestration solution. Nodegrid supports network functions virtualization (NFV), which turns your physical networking appliances into virtualized solutions you can configure and manage through IaC and SDN. Nodegrid’s vendor-neutral serial console servers also support legacy pinouts, so you can bring your legacy physical infrastructure under your immutable orchestration umbrella.

The ZPE Cloud network orchestration platform can also control remote data center, branch, and edge infrastructure. You can host your choice of SD-WAN (software-defined wide area networking) solution on your Nodegrid devices or use ZPE Cloud’s SD-WAN app. This technology allows you to extend the reach of your virtualized network orchestration to your WAN architecture. To dig even deeper, you can use the SD-Branch app to control branch and edge LANs as well.

The ZPE Cloud platform and all Nodegrid devices are truly vendor-neutral, allowing integrations with leading third-party IaC, SDN, and security providers. Nodegrid empowers you to create a tightly-integrated, seamless immutable infrastructure solution for total network control.

See how Nodegrid can help you implement immutable infrastructure best practices in your enterprise.

Call 1-844-4ZPE-SYS to view a free demo.

Contact Us

Why You Need a Next-Gen OOB Console Server

oob console server

An OOB (out-of-band) console server is a fundamental data center tool that allows you to view, manage, and troubleshoot critical remote infrastructure on a dedicated network connection.

While the functionality of generation 1 console servers is limited, generation 2 models evolved to include features like automation and security. Now, as more enterprises embrace NetDevOps, there’s a need for greater automation and orchestration, which is why next-generation or generation 3 console servers are emerging.

In this post, we’ll discuss the advantages of a next-gen OOB console server and how these devices address the challenges and limitations of previous generations.

The importance of an OOB console server

An out-of-band console server may also be referred to as a serial console, serial console server, or serial console switch. There are also OOB serial console routers which include gateway routing functionality for small branch offices and use cases for edge data centers.

OOB console servers are tools fundamental for data center infrastructure management; they connect to all your remote network devices and give you the ability to control them on a dedicated management network remotely. This network is completely separate from the WAN circuit and internal LAN, and is accessed typically via cellular, dial-up, or DSL modem.

Out-of-band data center access is crucial for a few key reasons:

  1. It provides 24/7 remote access to your critical data center infrastructure even if your WAN link goes down, allowing you to troubleshoot and recover without expensive truck rolls.
  2. You can still view and manage remote devices even if malicious actors compromise your production network or data center infrastructure without exposing yourself.
  3. Conducting resource-intensive network orchestration on a dedicated management plane reduces the performance impact on your production network and end-users.

Why do you need a next-gen OOB console server?

As modern enterprise networks have grown more complex and distributed, so have network and data center management workflows. This complexity makes it harder for engineers to efficiently manage their workloads and increases the risk of human error, especially with multi-vendor and hybrid network infrastructures.

These pain points led to the evolution of automated network management tools and solutions. Automation increases the speed and efficiency with which network administrators can provision, monitor, and optimize an infrastructure while reducing the risk of human error. Gen 2 OOB console servers have automation capabilities and scripting support that help fill the gap for data center management. Plus, Gen 2 serial consoles automate tasks like infrastructure provisioning (via zero touch provisioning, or ZTP) and basic troubleshooting (such as refreshing DNS or power-cycling) to reduce the amount of tedious manual work.

However, the needs and pain points of modern enterprises continue to evolve. It’s not enough to use individual, disparate scripts and solutions to automate specific tasks or workloads, especially to achieve NetOps or NetDevOps transformation. Gen 2 OOB console servers offer some automation support, but typically limit you to a particular vendor ecosystem or API library. Since enterprise networks consist of many different vendor solutions and devices, this rigidity leaves you with gaps in your automation coverage.

That’s why a new generation of console servers is rising to meet this challenge. Next-gen OOB console servers, also known as Gen 3, promise to deliver end-to-end automation and NetDevOps data center orchestration.

What to look for in a next-gen OOB console server

For an OOB console server to be truly next-gen, it must be able to dig its automation hooks into every device and solution in your rack. That means it needs to be vendor-neutral and include support for legacy systems not originally designed for automation.

In addition, a next-gen OOB serial console switch should support integrations with the third-party automation and orchestration tools of your choosing. That means both the hardware and software need to be vendor-neutral.

A next-gen console server should also provide high-speed OOB access and failover. Many Gen 1 and Gen 2 solutions use dial-up or 3G cellular connections, which can be slow and unreliable. Plus, 3G will be phased out (in the United States) by the end of this year. This leads to frustration when engineers try to troubleshoot and restore remote data center infrastructure as quickly as possible, and also hampers automation and orchestration efforts.

Another issue to consider is scalability. A next-gen OOB console server needs to provide enough managed ports for you to grow your data center infrastructure without needing to upgrade your management device continuously. You can even get modular serial consoles that allow you to expand or swap out port configurations as needed.

Last but not least, your next-gen console server needs to include and support advanced security controls. Imagine installing a preconfigured device that has unknowingly been infected. This could be like installing a trojan horse into your infrastructure. A next-gen OOB console server should include enterprise-grade security features and integrate with zero trust security controls and policies.

Orchestrating critical data center infrastructure with a next-gen OOB console server

Next-gen or Gen 3 OOB console servers deliver end-to-end automation and orchestration capabilities, so you can efficiently control complex data center infrastructure. A next-gen solution includes vendor-neutral hardware and software, high-speed OOB access and failover, the ability to scale up or down as needed, and enterprise security features and functionality.

The Nodegrid next-gen OOB console server solution from ZPE Systems delivers true end-to-end automation for critical data center infrastructure. Nodegrid’s vendor-neutral hardware and software can control all your vendor solutions, so there are no barriers to automating anything and everything. For example, Nodegrid zero touch provisioning (ZTP) can extend to all connected devices, allowing you to deploy remote data center infrastructure with the push of a button.

The Nodegrid Serial Console S Series can even control legacy and mixed environments, so you can upgrade your data center infrastructure at your own pace without losing automation capabilities. The open architecture, Linux-based Nodegrid OS supports integrations with third-party automation solutions so you can create a customized orchestration platform that suits your enterprise’s unique use cases and staff skillsets.

Nodegrid delivers high-speed remote out-of-band access and failover via two dual-SIM high-speed 4G/5G/LTE slots, plus you can upgrade to 5G without having to do a forklift upgrade. With up to 96 managed ports in a streamlined 1U rack-mounted device, the Nodegrid Serial Console Plus can handle enterprise-scale deployments or scale with you as you grow. The Nodegrid next-gen OOB console server also keeps management and orchestration secure, with onboard security features like UEFI secure boot, properly integrated TPM 2.0 security, encrypted solid-state disks, and geofencing.

The Nodegrid Serial Console from ZPE Systems is a true next-gen OOB console server. It delivers end-to-end automation, high-speed OOB access and failover, scalable port configurations, and enterprise-grade zero trust security features.

Learn more about OOB console servers:

★  Comparing the Best Console Servers for Data Centers in 2022
★  Out-of-Band Network Management: Fundamental Principles & Use Cases
★  How to Choose Secure Out-of-Band Management

See the Nodegrid OOB console server at work.

Call 1-844-4ZPE-SYS to request a demo. 

Watch A Demo

Network Disaster Recovery Plan Checklist

shutterstock_309021146

Your organization may feel secure now, but a disaster could occur at any moment. For example, the war in Ukraine took the world by surprise and left many organizations scrambling to protect and recover critical infrastructure, applications, and data from Ukrainian facilities.

To ensure you’re ready to weather any crisis, you need a robust disaster recovery (DR) plan that accounts for many different scenarios and challenges. This blog provides a network disaster recovery plan checklist to help you establish protocols for protecting your systems, data, and business.

Your network disaster recovery plan checklist

Identify potential disasters

There’s no one-size-fits-all disaster recovery plan—recovering from ransomware is a much different process than recovering from a tornado. You need to determine what types of disasters are most likely to occur and assess each scenario’s individual risk to your facilities, systems, and data.

Network disaster recovery plan checklist:

□   Make a list of disasters (natural, man-made, and otherwise) that could pose a threat to your organization.

□   Briefly describe what each disaster would look like and how they would impact your company.

□   Prioritize your list of disasters based on how likely they are to occur.

Establish the potential impact of a disaster

You should conduct what’s known as a business impact analysis to define how each of these disaster scenarios would impact your organization.

Network disaster recovery plan checklist:

□   Determine which business processes, systems, and data are affected by each disaster scenario on your list.

★  Tip: Don’t forget your cloud and edge resources

□   Outline precisely how operations will be disrupted by losing or disrupting critical business services.

□   Analyze the impact on every aspect of your organization, including productivity, revenue, reputation, etc.

□   Calculate the estimated cost of each disaster, both in terms of lost revenue and recovery costs.

Create recovery protocols

What steps do you need to take to recover from a disaster, and what technology will you use to do it? You should create specific recovery protocols for each high-priority disaster scenario on your list.

Network disaster recovery plan checklist:

□   Make a detailed list of all recovery procedures and who is responsible for each.

□   Make a list of all the technology that will be leveraged in a disaster (e.g., backup data solutions, network failover)

□   Outline instructions for every step in every recovery procedure, including branching recovery paths in case one or more of your recovery systems is unavailable.

Set expectations and timelines

Once you know how you’ll recover from each potential disaster scenario, you need to determine the realistic timeline for recovery. This timeline should be based on data and information from the individual team members involved in recovery efforts, as well as the business impact analysis you performed earlier.

Network disaster recovery plan checklist:

□   Define how long it would take to complete the recovery procedures for each disaster.

□   Compare this to the business impact analysis showing the estimated cost of a disaster to see if your recovery protocols will work quickly enough to prevent unacceptable losses.

★  Tip: If your recovery protocols are too time-consuming, you may need to return to step 3 and re-evaluate your technologies and procedures.

Define individual roles and responsibilities

When disaster strikes, it’s crucial to take action immediately. This is only possible if everyone involved in disaster recovery knows their responsibilities clearly and who is in charge of decision-making.

Network disaster recovery plan checklist:

□   Identify disaster recovery team members and determine how they should be contacted when there’s an emergency.

□   List the stakeholders who must be kept updated on the recovery status.

□   Assign a person (or team) responsible for monitoring the business impact of an ongoing disaster.

□   Assign people at each site who will decide on evacuation or relocation of staff and assets.

□   Identify the people who have access to secure systems and/or can grant access to others.

Establish lines of communication

Everyone in your organization needs to know who’s in charge of communicating vital information and how to get in touch with key members of the disaster recovery team. You should also identify a single person (or small team of people) responsible for communicating relevant updates to the public to ensure consistent messaging.

Network disaster recovery plan checklist:

□   Determine how to communicate with the disaster recovery team (and the rest of the organization) if email and phones are down.

□   Create a flowchart outlining who should be contacted in what order for each specific disaster scenario and recovery step.

□   Identify a single point of contact responsible for disseminating critical information to staff.

□   Make a list (in multiple locations to ensure constant availability) of vendor and support phone numbers to call in case of a cloud or service-related outage.

★  Tip: Also include the support numbers for all your recovery-related technology.

□   Identify a single point of contact through which all information about your disaster will be disseminated to the public/customers.

Create a disaster recovery playbook

You should collect all of the information gathered and analyzed in the previous steps into a single playbook that will act as the source of truth for your disaster recovery efforts. This playbook should be made readily available to everyone involved in the disaster recovery plan and duplicated across redundant systems to ensure it’s accessible when a disaster occurs. Essential information from the playbook (such as points of contact) should be shared with everyone in your organization, even if they don’t have a role to play in recovery.

Test your plan regularly

How do you know your plan actually works? You need to test your plan after implementation and then test again on a regular basis. Conduct employee drills to make sure everyone involved knows what they need to do if a disaster occurs. Test your processes and technologies to make sure they still function correctly and that you can recover within the timeline outlined above. Regular testing will let you know if any processes, instructions, or contact points are outdated.

The challenge of network disaster recovery

Even with the most robust network disaster recovery plan, you’re likely to face some hurdles when it comes time to execute your protocols.

For example, what if a disaster occurs at a remote branch office or data center? If you lose network access to your remote infrastructure, do you have a way to remotely troubleshoot and recover, or do you need to lose time and money to truck rolls or local consultants?

How do you deploy replacement devices if remote hardware fails or is irreparably damaged? Do you have staff on-site who can install and configure new devices?  If you stage new equipment at HQ and then ship it to the remote site, what happens if a malicious actor intercepts the package?

Do you have a way to monitor your infrastructure centrally and orchestrate your disaster recovery efforts? Can that system dig its hooks into every network architecture component, including legacy systems?

How ZPE Systems empowers streamlined network disaster recovery

The Nodegrid solution from ZPE Systems helps you execute your disaster recovery plan while avoiding all the most common challenges. Remote out-of-band management gives you access to all your remote network infrastructure via a dedicated link so you can still view, troubleshoot, and recover systems during an outage.

Ultra-secure zero touch provisioning (ZTP) allows you to ship factory-default equipment to remote sites and deploy configurations in a matter of moments, so you can recover faster. Plus, the vendor-neutral ZPE Cloud management platform gives you complete control and visibility on your distributed network infrastructure so you can monitor for issues and implement recovery protocols from anywhere in the world.

Learn more about network disaster recovery:

★  Customer Strategies in Ukraine to Protect Privacy and IP
★  Data Center Environmental Monitoring: How to Stop Disaster Before It Strikes
★  3 Tips to Improve Edge Network Resilience

Execute your network disaster recovery plan checklist with the Nodegrid solution from ZPE Systems.

Get in contact with us or call 1-844-4ZPE-SYS for a free demo.

Contact Us

Branch-in-a-Box: Why All-in-One Devices Are the Future of Networking

shutterstock_588813473(1)

A branch network consists of many moving pieces that need to be remotely deployed, managed, and supported. That typically means separate devices for all the key functions like routing, switching, security, etc. However, as data and applications grow more distributed—especially due to the popularity of edge computing—it becomes harder for IT teams to keep up with the growing number of vendors and solutions at the branch. Branch-in-a-box seeks to solve that problem by delivering all your branch networking functions in an all-in-one device.

What is branch-in-a-box?

Branch-in-a-box consolidates an entire branch networking technology stack into one piece of hardware. A branch-in-a-box solution might include gateway routing, voice and data switching, firewall, Wi-Fi, and other crucial functionalities. Instead of learning, installing, managing, and troubleshooting five different boxes at each branch location, you only have to worry about one core device.

Next-generation branch-in-a-box solutions typically rely on the following branch networking technologies:

  • SD-WAN: Software-defined wide area networking, or SD-WAN, abstracts WAN management from the underlying MPLS, broadband, fiber, and cellular connection hardware. You can create intelligent routing policies to distribute and route WAN traffic for optimal network performance, with SD-WAN. SD-WAN intelligent routing also facilitates cloud-based edge security technologies like SSE (security service edge) and SASE (secure access service edge).
  • SD-Branch: The limitation of SD-WAN is that its capabilities generally end at the branch gateway. SD-Branch extends your software-defined networking functionality into the individual LANs so you can automatically manage and optimize traffic within the branch.
  • Compute: Some branch-in-a-box solutions also come with compute capabilities or modules. Meanign you can run guest operating systems—like VMs (virtual machines) and containers—without needing to install additional server hardware.
  • Out-of-Band: Out-of-band (OOB) separates your branch network’s management plane from the data plane so you can remotely manage and troubleshoot your branch infrastructure from a dedicated connection. With OOB, you get one unified control panel from which to remotely monitor and administer all your branch networking devices. OOB also provides an alternative path to your branch network, often over a cellular connection, so you don’t need to rely on the primary WAN link. You can troubleshoot and recover from outages remotely, reducing costly truck rolls.

SD-WAN optimizes traffic to and from the branch, ensuring optimal performance and productivity in all your remote locations. SD-Branch extends your reach into the individual branch LANs to give you more control over network routing and performance. Compute capabilities let you run VMs and containers without deploying additional servers. Finally, OOB ensures you always have access to your branch infrastructure, even during a WAN outage. A branch-in-a-box solution harnesses those technologies to give you control over a consolidated networking stack including routing, switching, firewall, and Wi-Fi capabilities.

Where did the concept of branch-in-a-box come from?

Let’s say the typical branch network relies on five boxes—a gateway router, a voice switch, a data switch, a wireless access point (AP), and a firewall. Five devices may not seem like a lot; and using a separate box for each branch networking job means you can, theoretically, choose the best-of-breed solution for each. If you only have one or two branch locations and a large, well-trained IT staff, then supporting multiple branch networking devices probably won’t be a problem.

But what happens when your business grows, and you need to scale up to 10 branches? And then 100 branches? And then 1,000? Suddenly, five best-of-breed devices turns into 5,000 individual boxes you need to purchase, configure, maintain, and troubleshoot.

Branch-in-a-box solves this problem by rolling-up all your crucial branch networking devices into one consolidated solution. This helps you save money on equipment, both in terms of the up-front costs and the recurring costs of licensing, software, and support. Device consolidation can also decrease the power consumption at your branches, saving you energy costs and reducing your carbon footprint. Deploying a branch-in-a-box is often faster and easier since you only need to ship and install one box instead of five.

Plus, an all-in-one branch networking solution reduces the overall complexity of your enterprise network by decreasing the number of devices and platforms that your engineers need to learn, manage, and support. That means your IT operations team can work more efficiently, spending less time on individual maintenance tasks and more time optimizing your branch networking. It also reduces the risk of configuration mistakes and other human errors that could potentially bring down your branches.

The challenge of branch-in-a-box

Of course, when you replace many different boxes with one solution, you run the risk of vendor lock-in. Suppose your branch-in-a-box solution runs in a closed ecosystem. In that case, it’s critical for that one box to truly cover every branch networking capability you need, because you won’t be able to extend its capabilities with third-party tools and devices. Plus, you’ll be forced to follow that vendor’s feature and support roadmap, which may diverge from your organization’s future goals and requirements.

To avoid these issues, it’s crucial to select a vendor-neutral branch-in-a-box that runs on an open platform, like Nodegrid.

Innovative and vendor-neutral branch networking

Nodegrid is a family of open-architecture, vendor-neutral networking solutions for branch, edge, and datacenter. All Nodegrid Services Routers consolidate multiple features and functionalities into one box so you can streamline your network infrastructure and reduce the complexity of your branches. For example, the Hive SR is a next-generation branch-in-a-box that can host many essential functions on one compact device, including:



Gateway routing



SD-WAN with AutoVPN



Wi-FI Access Point



5G/4G/LTE



Secure out-of-band access



Firewall

Nodegrid also simplifies branch network management by providing a centralized, vendor-neutral platform from which to monitor, control, and troubleshoot your global network. ZPE Cloud gives your team access to all Nodegrid-connected devices from anywhere in the world through a secure, cloud-based web portal. Or you can use the on-premises Nodegrid Manager to gain complete control over every aspect of your branch network.

Plus, Nodegrid devices like the Hive SR run on the Linux-based Nodegrid OS. This open architecture supports easy integrations with third-party solutions. That means you can extend the device’s capabilities to include automation, orchestration, SSE, and other functions, allowing Nodegrid to scale with your organization.

Nodegrid delivers branch-in-a-box solutions through all-in-one hardware, consolidated management, and a completely open and extensible platform that scales on-demand.

Contact ZPE Systems today to view a free demo of Nodegrid branch-in-a-box in action.

Contact Us

Top Data Center Infrastructure Management (DCIM) Trends of 2022

shutterstock_2075585047(1)

Data center infrastructure management (DCIM) keeps evolving to address enterprises’ changing goals, requirements, and concerns. We spoke with DCIM sales engineers to find out which pain points are on their customer’s minds, and which emerging technologies their enterprises are currently excited about:

  • Providing 24/7 remote access with a virtual presence.
  • Consolidating infrastructure for simpler management.
  • Strategically automating DCIM workflows and equipment.

This blog will discuss why enterprises implement these DCIM tools and technologies and provide the best advice about using them within your data center environment.

The Top 3 DCIM trends of 2022

Remote DCIM

The Covid-19 pandemic has accelerated the existing trend towards remote DCIM with minimal on-site staff. Many organizations are cutting budgets and downsizing their staffing, and many  of the people they keep on board are working remotely. If you don’t have subject matter experts physically at your data centers, you need to be able to deploy, manage, and troubleshoot your infrastructure remotely.

One way to ensure you have 24/7 remote access to your data center infrastructure is with out-of-band (OOB) management. OOB separates the network management plane from the data plane and provides a dedicated connection to your management device, which means you always have access to your infrastructure even if there’s an ISP outage. A complementary component to having a virtual presence  is environmental monitoring, which uses sensors to detect temperature, humidity, tampering, and other data center conditions.

When an on-site visit is unavoidable, remote DCIM helps you determine the root cause of the issue beforehand so you can ensure you already have the parts and tools you need to fix it. Doing so prevents your engineers from making multiple trips or wasting time diagnosing problems on-site. Remote DCIM not only allows you to efficiently monitor and manage data center infrastructure, but it also helps minimize the amount of time and money spent traveling to remote sites to troubleshoot and fix issues.

Consolidated solutions

One of the biggest challenges in DCIM is dealing with many different appliances, solutions, and vendors. This means engineers and technicians need to be trained in deploying, managing, and troubleshooting all these disparate solutions. Vendor lock-in may prevent all these systems from working together or integrating with a central DCIM tool, which means engineers have to jump from box to box to monitor issues or perform maintenance. Plus, there’s the hassle of license management, and different vendor contracts coming up for renewal at different times.

That’s why many organizations are moving towards consolidated DCIM solutions with all-in-one devices. Instead of looking for best-of-breed solutions for routing, out-of-band access, infrastructure management, server/compute, and other data center devices, you can get all of these functions rolled-up into a single box. An all-in-one data center solution is like the Swiss Army Knife of DCIM—it may not be the absolute best at any one feature, but you get all the tools you need in one device.

Another way that organizations overcome vendor lock-in and infrastructure complexity is through vendor-neutral DCIM platforms. With an open-architecture platform, you can integrate all your disparate devices and solutions into one centralized control panel. This increases the ease and efficiency of your engineers to manage your entire data center infrastructure.

All-in-one devices and vendor-neutral DCIM platforms both help reduce the complexity of your data center infrastructure, saving you time, money, and frustration.

DCIM automation

Many organizations are beginning or continuing their DCIM automation initiatives in 2022. Some examples of the data center management workflows that are frequently automated include:

  • Power load balancing and management
  • VM (virtual machine) deployment and management
  • Environmental monitoring and analysis
  • Network load balancing
  • Issue remediation

DCIM automation reduces the amount of time your engineers spend performing tedious, repeatable, and manual tasks. This, in turn, reduces the risk of human error, so you can ensure optimal performance and uptime in your data center.

Often, organizations make the mistake of automating the low-hanging fruit first (whichever tasks are easily automated by their chosen solution) rather than analyzing and prioritizing DCIM workflows based on what will help them achieve their specific business goals. This may not make DCIM any easier or more efficient for them in the long run. Other enterprises assume that DCIM automation is an all-or-nothing proposition that requires orchestration and highly complicated scripts and tooling. This leaves them feeling too intimidated to even begin their automation efforts.

DCIM automation doesn’t have to be difficult. Suppose you start with a complete understanding of your data center infrastructure and which workflows are most critical to your business. In that case, you can then automate them in the order that’s most beneficial to your team and your enterprise. And it doesn’t need to happen all at once—you can begin by creating a simple script to handle a single process, then move on to using technology like zero touch provisioning (ZTP) to automatically configure new data center devices. It is important to use DCIM devices and solutions that provide all the automation capabilities you need without locking you into a single vendor’s ecosystem or feature roadmap. This way, your automation initiatives can scale with you in exactly the way you need them to.

When you take the right approach, DCIM automation can help your organization run more efficiently to save time and resources.

In 2022, many enterprises are prioritizing remote DCIM solutions that give them a 24/7 virtual presence in their data center. They’re also consolidating their data center infrastructure with all-in-one solutions that provide centralized monitoring and management. Finally, organizations are looking for ways to automate DCIM workflows without adding to the complexity of their data center infrastructure and management.

Achieve your DCIM goals in 2022 with Nodegrid

Nodegrid is an innovative data center infrastructure management platform that can help you stay ahead of DCIM trends in 2022 and beyond.

shutterstock_2129974520(1)
The Nodegrid Serial Console delivers remote OOB management of up to 96 connected devices in a single 1U rack-mounted device, ensuring you have 24/7 access to monitor and manage your data center infrastructure. Nodegrid’s modular design means you can create a customized data center management solution with all the functionality you need in one box. You can also use Nodegrid’s environmental monitoring sensors to keep an eye on environmental conditions in your rack, even from thousands of miles away.

Any data center infrastructure connected to a Nodegrid box can be deployed, managed, and monitored from one consolidated software platform—Nodegrid Manager for fully on-premises deployments, or ZPE Cloud for hybrid and cloud-based infrastructure.

Finally, Nodegrid enables and simplifies DCIM automation through features like zero touch provisioning and network scripting support. With the vendor-neutral, Linux-based Nodegrid OS, you can automate and orchestrate your data center infrastructure without vendor lock-in hampering your efforts. Nodegrid allows you to create a completely customized automation architecture using third-party tools like Ansible, Docker, and RESTful.

Want to learn more about DCIM? Read our Q&A with a 20-year DCIM expert.

See how Nodegrid can help you take advantage of DCIM trends in 2022.

Contact ZPE Systems to view a free demo.

Contact Us