Environment

• Product: ZCF
• Component: ZCE-X
• Affected objects: Environments without block storage, the object service platform, gateway networks, and host gateway_ips
• Version: 5.2.115.6
• Trigger condition: An online cluster must add an OSP gateway network segment so that the object service platform can be accessed from different gateway networks.

Symptoms

• The object service platform currently supports access only from the existing gateway network segment.
• A gateway network segment must be added because access requirements have changed.
• After adding the segment, the gateway_ips field in the host table must also be updated.

Diagnosis

1. Confirm that the current environment is within the scope of this article, and record key information such as versions, system architecture, operating system, deployment mode, and storage type.
2. Use xms-cli to view the object service platform or host ID.
3. Check whether the new and current gateway network segments can communicate with each other.

Cause

To access the object service platform from different gateway networks, add an OSP gateway network segment to the online cluster and update the gateway network configurations of the platform and hosts.

Resolution

1. Prerequisites

• Risk level: Medium
• Confirm that the new gateway segment can communicate with the current gateway segment.
• Plan static routes in advance if Layer 3 communication across network segments is required.
• Confirm permission to run xms-cli, zs-vlan, and zs-network-setting.

2. Procedure

1. View the object service platform ID for the subsequent xms-cli network change.

• Expected result: The required platform or host ID is obtained.

2. Add a VLAN NIC on each object service platform node.

• The following example uses server ZS05s01; change the remaining storage servers in sequence.

   zs-vlan -c bond0 61
   zs-network-setting -i bond0.61 192.168.61.13 255.255.255.0

• Expected result: The VLAN NIC is created successfully.

3. Configure a static route if Layer 3 communication across network segments is required.

• Expected result: The new gateway segment is reachable.

4. Change the object service platform gateway network.

   xms-cli --user admin --password Zstack@123 cluster set network --gateway 192.168.63.0/24,192.168.61.0/24

• Expected result: The platform gateway network is updated.

5. View the host IDs.

   xms-cli --user admin --password admin host list

• Expected result: The host ID of every node is identified.

6. Add the new gateway_ips value for each node.

   xms-cli --user admin --password admin host set --gateway-ips 192.168.63.13,192.168.61.13 1

• Here, 1 is the host ID. Run the command separately for each remaining node.
• Expected result: The gateway_ips field in the host table is updated.

7. Check in the UI or platform that the new gateway network is displayed correctly.

• Expected result: The new gateway network is visible and effective.

Verification

• Use xms-cli to recheck the cluster network and host gateway_ips configurations.
• Confirm that the new and current gateway segments can communicate with each other.
• Confirm that the object service platform is accessible from the new gateway network.

Risks and rollback

• Risk: An incorrect gateway network or static route may make the object service platform inaccessible.
• Risk: An incomplete gateway_ips update may cause inconsistent access behavior across nodes.
• Rollback: No separate rollback command is provided. If an abnormality occurs, delete the new gateway configuration, restore the original cluster set network and host set --gateway-ips configurations, and verify network reachability again.