ECS: OBS: Pre‑Upgrade: ObjectScale 4.1.x to ObjectScale 4.2 Routing Requirements

Summary: When upgrading from ObjectScale (OBS) 4.1.x to ObjectScale 4.2 or later, it is critical to ensure that every Virtual Local Area Network (VLAN) interface has a properly configured gateway. ObjectScale 4.2 and later versions incorporates a newer Linux kernel (6.4). This enforces strict, standards‑compliant routing behavior, including refusing to ARP for off‑subnet (different subnet) destinations unless a valid gateway or static route is defined. As a result, environments that previously relied on permissive ARP or switch proxy‑ARP behavior in ObjectScale 4.1.x will see that those routes stop working immediately after the upgrade if a gateway is not configured for one or more interfaces. ...

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Instructions

Before upgrading ObjectScale from version 4.1.x to 4.2 or later versions, gather the following information to identify any VLAN‑separated interfaces that require a gateway configuration and to ensure that routing remains functional post‑upgrade.

In environments where data, replication, or management interfaces reside on separate VLANs, missing gateway configurations can lead to significant service impact after the upgrade. Data interfaces without valid routing may prevent clients from reaching the nodes, causing data unavailability (DU). Replication interfaces may lose connectivity to remote sites or peer clusters, potentially triggering Temporary Site Outages (TSO) immediately after the upgrade. Management interfaces without proper gateways may fail to reach DNS or NTP services. This can break essential platform dependencies required for ObjectScale to operate, which can also lead to DU. Ensuring every VLAN interface has a correctly defined gateway is critical to maintain stability during and after upgrades.
 

  1. Network Topology and VLAN Information
    1. The following information is required:
      1. IP address set for the interfaces
      2. Gateways needed for each interface
      3. VLAN IDs set for the interfaces
    2. Confirmation of which interfaces are connected networks are L2‑only compare with L3‑routed.
      Command: # getrackinfo -n
      This example shows public.repl and public.data missing the gateway address:  
      admin@obs1:~> getrackinfo -n
Named networks
==============
Node ID       Network          Ip Address        Netmask            Gateway            VLAN               Interface
1            repl              10.X.X.X          255.255.255.0      -                  1234               public
1            data              10.X.X.X          255.255.255.0      -                  1235               public
1            mgmt              10.X.X.X          255.255.255.0      10.X.X.X           1236               public
  2. Once this information is gathered open a support service request (SR) case to assist with the necessary pre-upgrade requirements to add the gateway IP to the nodes.
     

Affected Products

ObjectScale Software with Encryption

Products

ObjectScale Software without Encryption, ObjectScale Software Series
Article Properties
Article Number: 000442042
Article Type: How To
Last Modified: 19 مايو 2026
Version:  2
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.