[et_pb_section fb_built=”1″ admin_label=”section” _builder_version=”4.16″ custom_margin=”0px||||false|false” custom_padding=”0px||||false|false” da_disable_devices=”off|off|off” global_colors_info=”{}” da_is_popup=”off” da_exit_intent=”off” da_has_close=”on” da_alt_close=”off” da_dark_close=”off” da_not_modal=”on” da_is_singular=”off” da_with_loader=”off” da_has_shadow=”on”][et_pb_row admin_label=”row” _builder_version=”4.27.2″ background_size=”initial” background_position=”top_left” background_repeat=”repeat” width=”100%” custom_margin=”||0px||false|false” custom_padding=”0px||0px||false|false” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.16″ custom_padding=”|||” global_colors_info=”{}” custom_padding__hover=”|||”][et_pb_post_title title=”off” meta=”off” _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”][\/et_pb_post_title][et_pb_text _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”]<\/p>\n
Out-of-band management (OOBM)<\/span><\/a> is a network resilience strategy that involves moving the control plane of critical infrastructure, such as routers, switches, and servers, to a separate network. Doing so isolates the control plane from the production network so it won\u2019t be negatively affected by equipment failures, ISP outages, or ransomware attacks.\u00a0<\/span><\/p>\n This guide describes two out-of-band deployment types and highlights three key best practices to maximize network resilience.<\/span><\/span><\/p>\n <\/span><\/p>\n [\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.27.2″ _module_preset=”default” width=”auto” custom_padding=”1px||||false|false” border_color_top=”#78828A” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.27.2″ _module_preset=”default” global_colors_info=”{}”][dvmd_table_maker tbl_column_header_count=”0″ tbl_chead_cell_color=”#214C64″ _builder_version=”4.27.4″ _module_preset=”default” custom_padding=”50px||50px||true|false” custom_css_free_form=”.icon-red{|| color:red;||}||.icon-green{|| color:#52eb34;||}” global_colors_info=”{}”][dvmd_table_maker_item col_label=”Type” col_content=”Deployment Type [\/et_pb_text][et_pb_image src=”https:\/\/zpesystems.com\/wp-content\/uploads\/2024\/11\/ZPE-Graphic-Request-IR-Nov-4.jpg” alt=”ZPE Graphic Request IR Nov 4″ title_text=”ZPE Graphic Request IR Nov 4″ align=”center” _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”][\/et_pb_image][et_pb_text _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”]<\/p>\n In an end-of-row (EoR) out-of-band deployment, one or more OOBM switches are installed in every row of data center infrastructure, rather than in every single rack. All the serial cables for infrastructure devices in a particular row are run to wherever the OOBM switch (also known as a serial console or console server) is located, which is typically at the end of the row.<\/span><\/p>\n An EoR deployment requires fewer OOBM devices than a ToR deployment, which reduces costs and management complexity. It also simplifies scaling, as new racks full of infrastructure could be added to the row without requiring additional OOBM serial consoles.<\/span><\/p>\n On the other hand, that one serial console becomes a single point of failure for the entire row\u2019s OOBM functionality. If that device becomes unavailable because of a botched update or malware attack, management teams lose OOBM access to the entire row. Cable management is also more difficult because serial cables must run from every device in every cabinet to the EoR console server. Plus, EoR deployments are less flexible, because upgrading or swapping out a single OOBM device affects an entire row of infrastructure.\u00a0\u00a0<\/span><\/p>\n <\/span><\/p>\n [\/et_pb_text][et_pb_image src=”https:\/\/zpesystems.com\/wp-content\/uploads\/2024\/11\/ZPE-Graphic-Request-IR-Nov-4-1.jpg” alt=”ZPE Graphic Request IR Nov 4 (1)” title_text=”ZPE Graphic Request IR Nov 4 (1)” align=”center” _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”][\/et_pb_image][et_pb_text _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”]<\/p>\n In a top-of-rack (ToR) out-of-band deployment, one or more OOBM switches are installed in every single rack in the data center. This keeps all serial cables inside the rack, which simplifies cable management. Instead of a single point of failure for the whole row, each serial console only affects one rack, enhancing <\/span>resilience<\/span><\/a>. Teams can also upgrade or swap out devices without worrying about what\u2019ll happen to the entire row, making ToR deployments a little more flexible.\u00a0<\/span><\/p>\n The main drawback of a top-of-rack deployment is that it requires more OOBM console servers than an EoR architecture. This makes OOBM deployments more expensive and adds more devices for teams to manage and monitor. It also increases the power draw in the data center, further driving up costs (and carbon footprints), and adds more network hops to local traffic, which could affect throughput.<\/span><\/p>\n <\/span><\/p>\n <\/span><\/p>\n [\/et_pb_text][et_pb_image src=”https:\/\/zpesystems.com\/wp-content\/uploads\/2022\/06\/A-diagram-showing-a-multi-layered-out-of-band-isolated-management-infrastructure.jpg” alt=”ZPE Systems \u2013 A diagram showing a multi-layered, out-of-band, isolated management infrastructure” title_text=”ZPE Systems \u2013 A diagram showing a multi-layered, out-of-band, isolated management infrastructure” align=”center” _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”][\/et_pb_image][et_pb_text _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”]<\/p>\n A third, less common approach is to deploy OOBM devices both top-of-rack <\/span>and<\/span><\/i> end-of-row. This makes the OOBM network highly resilient to both outages and ransomware attacks, providing a completely <\/span>isolated management environment<\/span><\/a> while maintaining the flexibility of a ToR deployment.\u00a0<\/span><\/p>\n The following best practices can help improve the flexibility, security, scalability, and resilience of out-of-band deployments.<\/span><\/p>\n Using vendor-neutral OOBM console servers helps consolidate data center management in a single platform. These devices can manage infrastructure from any vendor and integrate with third-party solutions for security, automation, troubleshooting, and more. Vendor-neutral OOBM deployments reduce management complexity and costs, while ensuring easy scalability.<\/span><\/p>\n OOBM devices and networks must be protected against compromise to keep bad actors from commandeering the control plane. The best practice is to use OOBM switches with strong hardware security, SAML integrations for multi-factor authentication (MFA) and single sign-on (SSO), embedded firewalls, and frequent firmware\/software updates to patch new vulnerabilities.\u00a0<\/span><\/p>\n OOBM serial consoles should support automation to improve scalability and efficiency, while reducing complexity and recovery times. At a minimum, they need zero-touch provisioning (ZTP) to automatically configure new infrastructure devices over the network. Advanced solutions like the Nodegrid Serial Console Plus can also host or integrate third-party automation for things like configuration management, security monitoring, troubleshooting, and even AIOps.<\/span><\/p>\n Nodegrid <\/span>OOBM switches<\/span><\/a> can be deployed top-of-rack, end-of-row, or both to improve the resilience of any data center architecture. They have an open architecture that can integrate and host other vendors\u2019 software and virtualized network functions for security, automation, and much more. Nodegrid serial consoles and all connected devices can be remotely managed from a single, <\/span>on-premises<\/span><\/a> or <\/span>cloud-based<\/span><\/a> software platform, significantly reducing management complexity. Plus, Nodegrid is frequently patched and comes back with security features like BIOS protection, UEFI Secure Boot, self-encrypted disk (SED), Trusted Platform Module (TPM) 2.0, an embedded firewall, and SAML 2.0 integrations.<\/span><\/p>\n [\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row use_custom_gutter=”on” _builder_version=”4.27.2″ _module_preset=”default” background_color=”#214C64″ width=”auto” custom_padding=”15px|15px|15px|15px|false|false” locked=”off” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.27.2″ _module_preset=”default” global_colors_info=”{}”][et_pb_text _builder_version=”4.27.2″ _module_preset=”default” text_font=”||||||||” text_text_color=”#FFFFFF” header_3_text_color=”#214C64″ header_4_text_color=”#358AAF” custom_padding=”30px|15px|30px|15px|true|true” global_colors_info=”{}”]<\/p>\n Reach out to ZPE Systems for more help comparing end-of-row vs. top-of-rack deployments or to see a demo of the Nodegrid platform in action.<\/b><\/p>\n [\/et_pb_text][et_pb_button button_url=”https:\/\/zpesystems.com\/contact\/” url_new_window=”on” button_text=”Contact Us” button_alignment=”center” _builder_version=”4.27.2″ _module_preset=”default” button_font=”||||||||” global_colors_info=”{}”][\/et_pb_button][\/et_pb_column][\/et_pb_row][\/et_pb_section]<\/p>\n","protected":false},"excerpt":{"rendered":" This guide describes two out-of-band deployment types and highlights three key best practices to maximize network resilience.<\/p>\n","protected":false},"author":16,"featured_media":227639,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"on","_et_pb_old_content":"","_et_gb_content_width":"","content-type":"","footnotes":""},"categories":[32,87,88,101,84,82,83,99,169,100,90],"tags":[],"class_list":["post-227620","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-datacenter-management","category-data-center-resilience","category-failover-connectivity","category-minimize-impact-of-disruptions","category-monitoring-reporting","category-out-of-band-management","category-power-management","category-remote-network-management","category-serial-consoles","category-streamline-deployments","category-vendor-neutral-platform"],"yoast_head":"\nOut-of-band deployment types<\/span><\/h2>\n
\nEnd-of-Row
\nTop-of-Rock” col_tcell_cell_align_vert=”center” col_chead_cell_color=”#214C64″ col_rhead_cell_color=”#358AAF” _builder_version=”4.27.4″ _module_preset=”default” col_tcell_text_font=”||||||||” col_tcell_text_text_color=”#FFFFFF” col_chead_text_text_color=”#FFFFFF” global_colors_info=”{}”][\/dvmd_table_maker_item][dvmd_table_maker_item col_label=”Description” col_content=”Description
\nDeploying OOBM devices at the end of every row in the data center
\nDeploying OOBM devices at the top of every rack in the data center” col_tcell_cell_align_vert=”center” _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”][\/dvmd_table_maker_item][dvmd_table_maker_item col_label=”Pros and Cons” col_content=”Pros and Cons
\n\u2714<\/i> Requires fewer OOBM switches
\u2714<\/i> Lower cost
\u2714<\/i> Reduced management complexity
\u2718<\/i> EoR device is a single point of failure for the row
\u2718<\/i> Cable management is messier
\u2718<\/i> Less flexibility
\n\u2714<\/i> Cables stay in the rack
\u2714<\/i> Eliminates a single point of failure
\u2714<\/i> Provides greater flexibility to modify, upgrade, or scale
\u2718<\/i> Requires more OOBM switches
\u2718<\/i> Additional switches could affect throughput, power draw, and cost
\u2718<\/i> Increases management complexity” col_tcell_cell_align_vert=”center” col_tcell_cell_padding=”15px||15px||false|false” _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”][\/dvmd_table_maker_item][\/dvmd_table_maker][et_pb_text _builder_version=”4.27.4″ _module_preset=”default” locked=”off” global_colors_info=”{}”]<\/p>\nEnd-of-row OOBM deployments<\/span><\/h2>\n
Top-of-rack OOBM deployments<\/span><\/h2>\n
Multi-layered OOBM deployments<\/span><\/h2>\n
Out-of-band deployment best practices<\/span><\/h2>\n
Vendor-neutral platforms<\/span><\/h3>\n
OOBM security<\/span><\/h3>\n
Infrastructure automation<\/span><\/h3>\n
Streamline your out-of-band deployment with Nodegrid<\/span><\/h2>\n