CONTACT US
1-844-4ZPE-SYS
ZPE CLOUD

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

Home » Uncategorized » Page 4

Part 1: Immutable Infrastructure: Challenges Your Company Needs to Be Aware of

by | Jun 13, 2022 | DevOps, NetDevOps, Network Automation, Network Edge Orchestration, SD-WAN, Uncategorized

shutterstock_1299826528

Immutable infrastructure refers to the critical network resources and systems that make up your infrastructure and that are never updated, changed, or fixed in any way—they stay exactly the same. If something needs to be modified, the entire system or device is replaced by a new one. While this approach has many advantages for organizations, there are still some immutable infrastructure challenges you’ll need to overcome.

Mutable vs immutable infrastructure

Traditional infrastructure deployments are mutable and continuously change in place. Sysadmins and network engineers will constantly deploy patches, modify configurations, and install new software on systems and devices while they’re actively in use. The benefit of this approach is that you don’t need to create entirely new server instances or network deployments every time you want to change something.

However, mutable infrastructure does create some risk. For example, what if you deploy a patch that breaks a core function? What if some new code introduces a security vulnerability to the system? How about if an in-place upgrade fails halfway through and you end up with an unplanned version of the configuration? With mutable infrastructure, you’re stuck troubleshooting the issues and attempting to deploy fixes on systems and devices actively in use.

On the other hand, immutable infrastructure is frequently copied, deleted, and recreated without making changes to the systems currently in use. Configurations are abstracted as software code and managed from a centralized location that’s physically and logically separate from the target infrastructure. This code can be copied and deployed to many different targets as frequently as necessary. The environments themselves are virtualized (and often containerized) which creates an additional abstraction layer from the underlying hardware. This also makes it possible to copy, delete, and recreate instances as needed.

When an infrastructure as code (IaC) or software-defined networking (SDN) configuration needs to be updated, a new version of the code is written, deployed to a new instance, and tested to ensure functionality and security. Then, traffic is redirected to the new instance and the the old one is simply deleted. If a virtualized or containerized environment fails, or is compromised by a hacker, you can delete it and replace it with an exact copy with minimum hassle.

Immutable infrastructure is becoming popular among DevOps and NetDevOps organizations that use IaC and SDN to integrate resource provisioning directly into the software development pipeline. While this approach has clear advantages—including security improvement, IT complexity and failure decrement, and easier troubleshooting than mutable infrastructure—there are also some immutable infrastructure challenges.

Immutable infrastructure challenges

The immutable infrastructure paradigm was initially conceptualized for hyperscale and enterprise data center deployments. It relies on software-defined technology stacks and orchestration solutions that automate deployment and provisioning. The challenge comes when you need to venture outside of this ideal deployment, as is the case for many organizations.

Modern enterprise networks are shifting away from massive, centralized data centers because modern enterprises are themselves less centralized than they used to be. As operations become more globalized and remote, distributed workforces evolve the norm, and enterprises deploy infrastructure closer to the network edge. Edge network infrastructure is deployed to small local data centers, branch offices, remote warehouses, and other distributed locations. Often, these smaller deployments rely on hardware-based appliances, servers, and legacy equipment.

This creates some significant challenges when you try to shift to immutable infrastructure, including:

  1. Extending the software-defined network automation and orchestration to remote locations outside your enterprise network.
  2. Bringing the orchestrator’s hooks into all of your disparate legacy hardware solutions.
  3. Finding a way to apply immutable principles to this mutable hardware-based infrastructure.

Solving immutable infrastructure challenges

Immutable infrastructure requires centralized orchestration of software-defined technology, so you need to apply SDN to WAN architecture to bring immutable to the edge. This is called SD-WAN, or software-defined wide area network. SD-WAN decouples the management of your WAN from the underlying hardware, so you can use orchestration to control distributed WAN architecture.

However, SD-WAN only gets you to the perimeter of your edge networks. To use immutable infrastructure effectively, you also need to extend the orchestrator’s reach into the branch and edge LANs. You can achieve this through SD-Branch technology, which gives you software-defined control over the internal networking infrastructure of remote architectures.

The second goal is to ensure that your orchestration solution can see and control every piece of your edge architecture, even legacy systems not designed with automation in mind. The SD-WAN/SD-Branch gateways and console servers you install at the edge need to support legacy pinouts and integrate with third-party hardware and software. If the edge connectivity solution can’t say yes to every component of your distributed network infrastructure, you’ll have gaps in the software-defined orchestration coverage.

The third task is to turn mutable hardware into immutable infrastructure, which you can accomplish through virtualization. In the same way that a single physical server can be turned into many different virtual machines, you can use network functions virtualization (NFV) to turn physical networking appliances into virtualized solutions. NFV creates an abstraction layer that separates the underlying hardware’s routing, switching, load-balancing, and other management functions. This allows your orchestrator to manage these functions automatically and create, copy, delete, and recreate network configurations at will without worrying about the mutable hardware.

The tricky thing about solving each of these challenges is that you need a truly vendor-neutral solution to make it all work. For example, if you have different branch gateways in different locations, you need to ensure that the SD-WAN/SD-Branch platform will integrate with all of them. Otherwise, you’ll need to manage multiple software-defined technology stacks, or you’ll lose the ability to apply immutable principles consistently across your entire distributed network.

The network functions virtualization platform also needs to support all of your disparate vendor hardware and legacy architecture; otherwise, you won’t be able to turn all mutable infrastructure into virtualized, immutable solutions. Plus, the orchestrator needs to integrate with your NFV platform as well as all edge hardware and software, to have full coverage.

Many immutable infrastructure solutions fall short of true vendor-neutrality. That means, to use them effectively, you have to upgrade your edge infrastructure hardware and software to compatible versions. This is an expensive and time-consuming endeavor and one that creates a massive roadblock for globally distributed enterprises hoping to adopt immutable principles.

Nodegrid brings immutable infrastructure to edge networks

ZPE Systems can help you bring immutable infrastructure to your edge networks with the vendor-neutral Nodegrid platform. Nodegrid’s powerful, all-in-one branch gateways give you the best of both worlds: you can use our powerful SD-WAN and SD-Branch technology or directly host your choice of third-party software-defined networking solutions. The modular design of the Nodegrid Net Services Router (NSR) also gives you added capabilities like edge compute, terminal server, NetDevOps, and more.

The vendor-neutral ZPE Cloud orchestration platform can say yes to every component of your distributed network architecture, including legacy hardware appliances and systems. ZPE Cloud gives you complete control over your mutable hardware, making it possible to apply software-defined orchestration to even the smallest branch deployments.

Plus, all Nodegrid devices run on the vendor-neutral, Linux-based Nodegrid OS with support for NFV. You can use Nodegrid OS to virtualize every piece of the edge networking stack, turning mutable branch hardware into immutable, automated solutions.

Learn how Nodegrid can solve your immutable infrastructure problems.

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

Contact Us

Supply Chain Security Risk Management Best Practices

by | May 31, 2022 | Improve Network Security, Uncategorized, Zero Trust Security

supply chain security risk management

A supply chain attack is when cybercriminals breach your network by compromising an outside vendor or partner. Often, these attacks exploit a weak link in your trusted ecosystem of third-party software, hardware, and integrations. A hacker will, for example, use a compromised vendor service account—one using the same username and password across many different client systems—to infiltrate all the third-party networks with privileged access for the vendor.

Several high-profile incidents like the SolarWinds attack and the Microsoft Exchange exploit illustrated how even the largest and most respected firms can introduce risk to your supply chain. In this post, we’ll use these examples to highlight the security challenges posed by supply chain attacks before providing supply chain security risk management best practices and solutions to protect your enterprise.

Supply chain security risk management challenges

→  SolarWinds attack uses trusted infrastructure monitoring software to compromise customer systems

In early 2020, an advanced persistent threat infiltrated a SolarWinds update server—It was a highly sophisticated group of hackers allegedly acting on behalf of a foreign state. The hackers injected malicious code into new builds of SolarWinds’ Orion platform, which thousands of customers use to monitor their critical IT infrastructure. These infected updates were unknowingly pushed out to over 18,000 customers, creating 18,000 backdoors for hackers to breach.

Once the compromised software was installed on target networks—including U.S. government agencies like the Department of Homeland Security and tech giants like Microsoft—attackers used these backdoors to steal identities and tokens to impersonate real users. Then, they were able to sidestep multi-factor authentication and spread laterally within affected networks, causing untold damage in their wake.

The full fallout and consequences of the SolarWinds attack are still unfolding more than two years later. This supply chain attack was devastating since they used the exploited software to monitor network infrastructure. That means hackers had privileged access to the most sensitive, vulnerable, and critical systems on affected networks. In addition, the advanced persistent threat used sophisticated techniques to bypass MFA and impersonate authorized users, making it extraordinarily difficult to track and prevent their movements.

The SolarWinds attack proved a few critical things about supply chain security:

  1. The infected software could contaminate customer systems, meaning intrusion prevention and anti-malware software weren’t advanced enough to detect the malicious code.
  2. The hackers were sophisticated enough to bypass MFA and other advanced authentication technologies, showing that these measures alone aren’t sufficient to prevent accounts from being compromised.
  3. The hackers were able to use those compromised accounts to freely move around on breached networks, illustrating the need for internal defenses and trust verification.

 

→  Microsoft Exchange attack exploits vulnerabilities on legacy on-premises systems

In early 2021, hackers used multiple zero day exploits to attack the on-premises version of Microsoft Exchange. They compromised servers at over 30,000 organizations in the United States, accessing email accounts and installing web shell malware. They used this malware to remotely access server functions and jump to other connected systems. In addition, hackers could use compromised email accounts as conduits to infect other organizations. They would look for a high-value contact in a compromised account’s contact list (for example, an executive at a major financial firm) and then send phishing messages and infected attachments to that target, extending their reach even further.

One of the reasons this attack was so successful is because hackers targeted on-premises Exchange implementations on legacy systems. Many organizations that still use legacy Exchange servers are less technically-savvy than those that jumped to the cloud. They may not have a large team of specialist admins and security engineers monitoring servers and applying regular updates to legacy systems. That made it easier for hackers to exploit unpatched vulnerabilities, and gave them more time to execute their endgame (infecting higher-value targets at connected organizations) before being detected.

So, what lessons have we learned from these two incidents, and how can we apply them to supply chain security risk management?

Supply chain security risk management best practices

These high-profile events illustrated a few key challenges:

  1. Many signature-based intrusion detection and security monitoring solutions aren’t sophisticated enough to detect zero-day exploits and novel malware.
  2. Cybercriminals can outsmart MFA and other advanced authentication methods, so they must be layered with other security controls.
  3. Organizations must not neglect internal defenses (including trust re-verification and network segmentation) because they’re crucial for preventing the spread of infections and compromised accounts.
  4. Organizations must have a plan for adequately monitoring, patching, and controlling legacy systems on their enterprise network.

Zero trust security

Zero trust security is a supply chain security risk management best practice due to its guiding principle of “never trust, always verify.” Zero trust creates a multi-layered defense of highly specific security policies and controls that focus on preventing breaches and limiting their damage once they’ve already occurred.

Next-generation firewalls (or NGFWs) use advanced machine learning and artificial intelligence technology to monitor network traffic for threats. Rather than relying on a signature database of known threats (which can’t account for zero-day exploits and novel malware), they use deep learning and other AI technology to analyze traffic with greater accuracy. NGFWs also enable network microsegmentation and may even include UEBA.

Microsegmentation is the zero trust practice of grouping systems and resources into small logical network segments. Microsegmentation allows you to create highly specific micro-perimeters of security policies and controls around each network segment. This ensures that all network resources are accounted for and adequately protected, and also allows you to reverify an account’s trust as they move from microsegment to microsegment.

User and Entity Behavior Analytics (or UEBA) technology monitors the behavior of entities (accounts, devices, applications, etc.) on your network. It uses machine learning to establish baselines of normal behavior, allowing it to analyze entity activity in real-time contextually. If an account or device behaves suspiciously, UEBA can block access, alert security, and/or force that entity to re-establish trust before letting it access another microsegment.

Even if the malicious code injected into the SolarWinds Orion updates made it past your NGFW’s initial defenses, zero trust security tools and practices will limit the attacker’s movement inside your enterprise network. Microsegmentation, aided by technology such as UEBA, would force a compromised account to re-establish trust before accessing additional resources while alerting security personnel to a potential breach.

Legacy modernization

Sounds scary and expensive, but it’s a critical process for securing on-premises and hybrid network environments. Obviously, the best-case scenario would be to replace your existing out-of-date hardware with newer systems or to migrate all your legacy services to the cloud, but that’s not realistic for many organizations. A more cost-effective way to modernize legacy systems is centralized infrastructure management, monitoring, and orchestration.

An infrastructure management platform that can hook into all your legacy, on-premises, data center, and cloud systems will help you ensure your entire architecture is always patched and secure. Your engineers won’t have to jump from box to box or switch between on-premises and cloud monitoring systems, increasing the efficiency they can maintain and control every piece of your infrastructure. Legacy modernization with unified infrastructure orchestration would have enabled engineers to patch on-premises Exchange vulnerabilities and detect the signs of a breach much faster.

Zero trust security and legacy modernization would have reduced the impact of these supply chain attacks and are critical for preventing similar events from occurring in the future. ZPE Systems can help you implement supply chain security risk management best practices through our Nodegrid family of secure infrastructure management solutions.

All Nodegrid hardware and software are protected by the Zero Trust Security Framework Foundation, with features like secure boot, geofencing, and up-to-date OS kernels and encryption modules. Nodegrid is vendor-neutral and supports integrations with your choice of NGFW and security software. Plus, Nodegrid supports legacy pinouts, so you can connect your on-premises infrastructure to the Nodegrid Manager or ZPE Cloud network orchestration solutions.

Learn more about supply chain security risk management best practices:

→   What Are the Key Zero Trust Security Principles?
→   The Importance of Micro-Segmentation for Zero Trust Networks
→   Data Center Modernization Strategy: How to Streamline Your Legacy Environment

Learn how Nodegrid supports supply chain security risk management best practices.

Call 1-844-4ZPE-SYS or contact us to view a demo.

Contact Us

Why You Need a Next-Gen OOB Console Server

by | May 26, 2022 | Data Center Management, Failover Connectivity, Increase Productivity, Minimize Impact of Disruptions, NetDevOps, NetDevOps Transformation, Network Automation, Out of Band Management, Remote Network Management, Serial Consoles, Uncategorized

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

by | May 23, 2022 | Data Center Management, EdgeOps, Improve Network Security, Minimize Impact of Disruptions, Network Edge Orchestration, Remote Network Management, Uncategorized

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

O que é EDGE COMPUTING e como ele pode reduzir seus custos de TI?

by | Apr 19, 2022 | Uncategorized

Edge Computing ou Computação de Borda trata-se do processamento de dados mais próximo ao usuário local, criando maior fluidez e rapidez. É uma arquitetura de TI distribuída, onde os dados dos clientes são processados perifericamente.

Esta nova tendencia ou tecnologia está rompendo um dos principais paradigmas tradicionais da computação de dados, a existente de um data center centralizado. Atualmente o mundo é mais conectado que há 5, isso mesmo, apenas 5 anos atrás, necessitamos de novas tecnologias que consigam processar e trafegar os oceanos de dados existentes na internet.

Limitações como as larguras de bandas, problemas de latência e downtime de servidores (veja o artigo “Você sabe quanto custa para a sua empresa um servidor fora do ar?”). O uso do Edge Computing ou Computação de Borda vem justamente responder este desafio.

Em termos mais simples, o Edge Computing transfere uma parte dos recursos de armazenamento e computação para fora do data center central, ficando mais próximo da fonte dos dados. Em vez de transmitir dados brutos para um data center central para processamento e análise, esse trabalho é executado onde os dados são realmente gerados – seja em uma farmácia, loja, supermercado, praça de pedágio, unidade fabril, um posto de serviço público, um terminal de ônibus ou em uma cidade inteligente.

O resultado da solução de Edge Computing, gera comunicação em tempo real de novos negócios, processos, projetos, melhor gestão de manutenção de equipamentos ou outras respostas acionáveis, é enviado de volta ao data center principal para revisão e outras interações humanas.

A ZPE SYSTEMS possui a solução para gerência de equipamentos instalados nos sites remotos de Edge Computing, permitindo ativamente monitorar e atuar nos equipamentos aumentando a eficiência operacional dos locais remotos. As soluções ZPE oferecem muito mais benefícios, uma vez que todos os nossos equipamentos rodam em arquitetura Linux® com processadores Intel® x86 Dual, Quad e Octa Core, executar máquinas virtuais com acesso adicional via rede móvel 4G ou 5G permitindo muito mais funcionalidades e processamento de aplicações.

A integração da solução ZPE SYSTEMS com soluções de segurança e conectividade existentes no mercado permite uma gestão mais efetiva de administração de equipamentos de rede e melhoria operacional com total segurança de acesso.

Conheça mais a ZPE SYSTEMS no www.zpesystems.com/products

Estudo de Caso: Automação e Gerência Remota

Como aumentar o controle e gerenciamento em um Supermercado, gerando economia e melhor serviço

Supermercados são estabelecimentos que precisam que a rede de comunicação de dados esteja ativa e operando estavelmente para suportar a demanda de vendas. Contudo, tendo grandes centros de distribuição, enormes showrooms e lojas pode exigir bastante energia e esforço operacionais para manter os equipamentos conectados e ativos em todos os locais.

Operações internas se baseiam fortemente nos dados para tomar decisões em logística, inventário, compra e venda, enquanto mantendo ativa interação face a face com o cliente. Os sistemas precisam de uma rede de dados estruturada e robusta para suportar as necessidades de verificar disponibilidade de produtos e processar as transações e pagamento o mais rápido possível.

Assim, para acomodar um rápido e estável crescimento dos negócios, o executivo deve buscar uma solução que pode ajuda-lo em aproveitar cada oportunidade de melhoria e economia.

O Desafio

Com as soluções tradicionais, companhias se acostumam com a necessidade de muito suporte local, aumentando os custos de manutenção e atrasos devido a deslocamentos de técnicos. Com o crescimento exponencial dos negócios e de áreas operacionais, esta expansão se torna cara e critica, e as tradicionais maneiras do TI suportar estas atividades se tornam onerosas e lentas. Tendo que ativar dispositivos “gateways” com tecnologia 4G em cada departamento acaba encarecendo a operação. Também, serviço on-site acaba sendo lento devido as necessidades de deslocamento para executar atividades básicas, além de dificultar gerência de conectividade secundária. Além disso, muitas vezes temos que instalar uma longa rede de cabos limitados pela distância operacional ou dificuldades de instalação. Este model se torna inadequado em alguns lugares pois acaba interrompendo a operação com novas instalações.

Além disso, o time de suporte do supermercado precisa se deslocar ao site e ter acesso físico aos servidores e equipamentos de rede para uma ação reparadora de falhas, caso não seja possível pela rede IP e se necessite acesso via porta de console.

Em casos mais sofisticados, as empresas estão integrando sensores de monitoramento ambiental, controle de temperatura e outros dispositivos. Por isso, a empresa precisa de uma solução integrada que permita:

  • Prover conveniente acesso remoto aos equipamentos para os times de suporte
  • Infraestrutura interconectada para reduzir custos locais de conectividade celular
  • Automação de atividades, suporte e provisionamento remoto

A Solução

Seguindo praticas modernas de arquitetura de redes, o uso da solução escalável da ZPE Systems NODEGRID é a única que permite entregar todas estas funcionalidades para permitir um crescimento rápido e controlado de sua estrutura de rede.

Usando uma combinação de produtos, podemos utilizar varias soluções NODEGRID para atender cada necessidade e especificidade dos locais.

No caso do principal centro de distribuição e controle, utilizamos a solução modular NSR, que usa pouco espaço no gabinete de rede executando funções de interconexão com a internet via fibra e fallback em LTE /4G de alta velocidade. O NSR pode executar as funções de rede e servir de serial console para controlar os outros equipamentos instalados no gabinete de rede local, como servidores, PDUs , roteadores, entre outros. além disso, podemos instalar dispositivos menores ZPE BSR em cada departamento, com tecnologia WiFI criando redes locais sem fio, interconectando-os via fibra ótica para reduzir custo de conectividade celular.

Para as Lojas/Supermercados, foram utilizados seriais consoles se conectando com todos os equipamentos conectados via rede IP e outros através da porta console, como por exemplo, servidores locais, roteadores, switches, frentes de caixa, sistemas de iluminação e energia, medidores de temperatura, câmeras de vigilância e outros sistemas de controle de ambiente.

Os resultados

A solução Nodegrid ajudou a rede de dados da EMPRESA a brilhar, suportando as demandas de rápido crescimento, acesso remoto e controle.

Ao invés de necessitar vários dispositivos pra cada departamento, foi criada uma rede integrada, com acesso via WIFI ou cabeamento estruturado, com economia no acesso a internet, minimizando custos de celular por departamento.

Além disso, o time de suporte tem acesso adequado aos servidores e outros dispositivos mesmo quando a rede de dados esteja instável, usando acesso OOB via porta de console com conexão LTE 4G.

As expansões e novas instalações são simplificadas porque os equipamentos NODEGRID suportam automação tanto para minimizar a necessidade de tarefas manuais para gerenciamento, como permite que configurações iniciais em nossos dispositivos sejam feitas remotamente através do ZTP (zero touch provisioning), aumentando a velocidade de expansão e configuração remota.
Pelo simples acesso ao NSR, o departamento de IT pode provisionar, monitorar e gerenciar todos os dispositivos físicos e virtuais (como máquinas virtuais) conectados na rede. Mais do que isso, como a plataforma Nodegrid opera independente do equipamento, quaisquer dispositivos podem ser controlados, independente do fabricante.

Os benefícios e Economias

Com a solução NODEGRID, a EMPRESA conseguiu tornar a infraestrutura de rede mais robusta, simples e mais poderosa. Os produtos NSR e BSR demandam pequeno espaço nos gabinetes de rede, porem são poderosos e podem fornecer funcionalidades criticas, como roteamento, switching, cellular failover e conectividade WIFI, permitindo:

  • Economia de tempo e menores custos com suporte com soluções de acesso remoto
  • Aumento do SLA e reduzindo deslocamentos
  • Redução do número de equipamentos, com isso, espaço e energia.
  • Redução de custos de backup celular para acesso LTE
  • Novos implementações mais rápidas e mais fáceis de serem executadas devido ao uso de automação.

A equipe de TI e suporte pode minimizar a necessidade de estar o tempo todo no local de operação e manutenção nos gabinetes de equipamentos, diminuindo deslocamentos. Além disso, o suporte pode responder proativamente a potenciais problemas independentemente do modelo e fabricante, através de acesso tradicional, banda larga ou via conexão celular.

Também temos economias de escala com redução de cabeamento estruturado e amplificadores de sinal, pois as áreas internas da central de armazenamento e distribuição serão conectadas ao gabinete central através de fibra ótica e o o NSR pode concentrar o acesso remoto via celular com um plano único haja vista o modem de dados tem capacidade de velocidade de 600Mbps, podendo ate ter 2 modems ativos ou redundantes, e 2 SIM cards de dados cada um, permitindo bastante flexibilidade e opção de melhores custos de serviços.

Esta solução implementada não apenas melhora a gerência de equipamentos nas lojas existentes, mas devido a arquitetura da solução Nodegrid, permite novas implementações serem facilmente executadas.

A empresa pode se beneficiar do uso de automação do NODEGRID, eliminando a necessidade de configuração manual e no local, reduzindo erros e mantendo controle remoto. Ao invés de enviar técnicos especializados para instalações remotas e distantes, através da solução de provisionamento ZTP (zero touch provisioning), permitindo todo o processo automático e a customização dos equipamentos acontecer remotamente.

Escalabilidade rapidamente se transformou em uma capacidade de auxiliar o crescimento dos negócios, novas instalações e migrações. A companhia aproveitou a vantagem de facilidade de conectividade e expansão da rede, permitindo gerenciamento mais fácil e eficiente.

Por que usar a solução de SD-WAN?

by | Apr 19, 2022 | Uncategorized

As soluções de SD-Wan chegaram para mudar o paradigma advindo do risco de uso de links de internet para conectividade entre empresas e filiais. Ela é uma solução que integra muitas características e serviços de uma rede como gestão, segurança e load balance, tudo isso integrando regras e políticas de segurança mesmo em um serviço de nuvem aberta ou internet permitindo o acesso e replicação de politicas de segurança em todas as suas filiais.

Outros benefícios do uso da solução de SD-WAN (Software Defined Wire Area Networking) está na possibilidade de separação do tráfego, facilidade e simplicidade de configuração, segurança/ compliance PCI, melhor experiência do usuário em suas aplicações (locais ou em nuvens), high performance, gestão de rede, flexibilidade, alta disponibilidade, escalabilidade e eficiência, permitindo utilizar qualquer link de dados existente como também incorporar a sua banda larga com MPLS existentes, trazendo a redução de custos, tema impactante na área de TI.

A solução SD-WAN pode ser utilizada em todos os segmentos empresariais desde PMEs até Corporações Mundiais.

O baixo custo da solução aliada a lista de benefícios de gestão e segurança da rede, proporciona hoje um aumento do uso do SD-WAN em farmácias, supermercados, lojas, postos de gasolina, escritórios, centros logísticos, transporte público e muitos outros locais.
A ZPE SYSTEMS possui a solução SD-WAN com muito mais benefícios que os atuais players de mercado, uma vez que todos os nossos equipamentos rodam em arquitetura Linux® com processadores Intel® Dual, Quad e OctaCore permitindo muito mais flexibilidades e funcionalidades processamento de aplicações.

A integração da solução SD-WAN com soluções de segurança e conectividade existentes no mercado permite até mesmo a administração de equipamentos de rede de outros players pela plataforma ZPE CLOUD.

Conheça mais a ZPE SYSTEMS no www.zpesystems.com/products