Skip to content

Overview

This chapter describes the installation process for the xSpace management component and access gateway. For installation instructions of other system components, please refer to the following paths:

1. Deployment Environment Preparation

The various functional components of the xSpace management component adopt a microservice architecture and are deployed in virtual machines provided by the underlying hyper-converged or cloud platform IaaS environment. Before installation and startup, please confirm that the following basic conditions are met:

  • Infrastructure Ready: The hyper-converged or cloud platform environment is ready and running normally, with sufficient computing resources, storage space, and network connectivity to support the operation of the management component.
  • IP Resource Planning: If the environment requires long-term stable and legitimate local area network IP addresses, please apply to network administrators for a sufficient list of addresses in advance and configure them in the corresponding virtualization network components.

2. Network and IP Configuration Specifications

The persistence and stability of network addresses are the core prerequisites for the normal interconnection of various management component.

2.1 Management Component Internal IP

  • Quantity Requirements: 3 internal IP addresses need to be provided for the xSpace management component.
  • Persistence Requirements: After the virtual machines used to deploy the management component are created, their internal interconnected IP addresses must not be arbitrarily changed. Please ensure that the addresses remain persistently available throughout their lifecycle.

2.2 External Network Access Scenarios (Optional)

If the business scenario requires external or public network access, in addition to deploying the management component, gateway service nodes also need to be planned and deployed:

  • Internal IP Planning: For SDWAN gateway servers, each access gateway node requires 1 independent internal IP address.
  • Public IP Planning: Corresponding public IP addresses need to be configured for each gateway node based on actual access requirements.