H3C Workspace Cloud Desktop
Management Network Editing Configuration Guide

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Document version: 5W101-20240808

Software version: H3C_Workspace-E1xxx

 

Contents

About management network editing· 1

Applicable versions· 2

Restrictions and guidelines· 2

Configuration workflow·· 2

Procedure· 3

Prerequisites· 3

Editing management network configuration· 3

Compute virtualization scenario· 3

HCI scenario (non two-node deployment) 6

HCI scenario (two-node deployment) 11

Restoring the environment 17

Editing the handy IP address (HCI scenario) 17

Removing hosts from maintenance mode· 19

Querying the availability of non-local storages· 20

Editing the VM communication address· 23

Editing the communication address of the PC agent 23

Checking the connectivity of third-party components· 24

Handling host heartbeat abnormal alarms· 24

Starting the campus space· 25

Editing the management relationship on Space Center 25

Editing the security gateway· 25

Viewing configuration records· 25

Appendix· 27

Viewing the reason for failing to edit the management network configuration· 27

Handling a failure to edit the management network configuration caused by stateful failover in HCI scenario  27

Editing the address and name of the server connected to the client 27

Editing the address and name of the server connected to the VDI client 27

Editing the address of the server connected to the IDV, VOI, and UCC clients· 30

Related documentation· 32

About management network editing

After the initial deployment of H3C Space Console is complete, you need to edit the network configurations of the hosts in the cluster in the case of changes in the network planning and the environment. To meet the requirement, H3C Workspace cloud desktop allows users to edit the management network configuration on Space Console.

This document describes how to configure the network configuration of a host and restore the environment after editing the network configuration. 1 shows the supported configuration items.

IMPORTANT: ·     Editing the management network configuration is a high-risk operation. Please do it under the guidance of professionals. This operation might affect the normal operation of services, so do not perform this operation unless necessary. As a best practice, do not edit the management network configuration multiple times. Plan the network in advance before editing the management network configuration. ·     If an edit failure occurs, contact Technical Support in time. ·     In scenarios where a large number of services or important services have been deployed, do not edit the management network configuration as a best practice.

 

1.     Supported configuration items

Type	Configuration item	Compute virtualization	HCI
VIP information	VIP address/mask	√	√
	Service network VIP address/mask	√	√
	Quorum IP address 1	√	√
	Quorum IP address 2	√	√
	Quorum host IP address/mask	√	√
	Quorum host gateway	√	√
	Storage component VIP	×	√
Node information	Management network gateway	√	√
	Management network segment	√	√
	Management IP address/mask	√	√
	Host gateway	√	√
Storage node pool information	Storage component VIP	×	√
	Management network segment	×	√
	Management IP address	×	√
	Storage front-end network	×	×
	Storage back-end network	×	×

 

NOTE: ·     This feature is available only when the Workspace environment contains only compute virtualization clusters or only up to one HCI cluster. ·     If Space Console is deployed in HCI two-node mode (that is, there is a monitor node), you can edit the management network configuration from the CLI of a host. For more information, see "HCI scenario (two-node deployment)." In this case, make sure the Workspace environment contains only up to one HCI two-node cluster. ·     In the separated deployment scenario, you cannot edit the management network configuration from Space Console. To edit the management network configuration, see H3C Workspace Cloud Desktop Maintenance Guide. ·     This feature is not available for hosts with a Kylin OS. ·     This feature is not available for hosts with IPv6 configured. ·     The VIP information is available for modification on the management network configuration page when a stateful failover system is set up. ·     To edit only the storage component VIP, contact Technical Support.

 

Applicable versions

The steps described in this document apply to H3Linux 1.0-based Workspace of E1013P33 and later versions. For the steps for versions between E1010 and E1013P33, see H3C Workspace Cloud Desktop Maintenance Guide.

Restrictions and guidelines

When editing the network configuration of a host, follow the following restrictions and guidelines:

·     This feature is available only when all clusters and hosts are operating correctly.

·     If the IP address of Space Console is edited, the original IP address will be invalid and the server will restart. Therefore, record the new address, and log in with the new address after the server is restarted.

·     During the modification of the network configuration, do not perform any operations. The modification may take a long time.

·     If there is a backup history of the management data before the management network IP address is edited, do not perform backup recovery after the modification.

·     If the system has a VM with a static IP, you need to manually edit the IP address of the VM after editing the management network IP across network segments.

·     Make sure the edited management network IP is reachable to third-party components such as the LDAP server, domain server, mail server, shared storage, monitor platform address, and license server.

Configuration workflow

1.     Prerequisites

2.     Modifying management network configuration

3.     Restoring the environment

Procedure

This guide uses E1016P02 as an example. The configuration procedure varies by software version.

Prerequisites

Before editing the management network configuration of a host, make sure the following requirements are met:

·     Back up the names and paths of all non-local storage on all hosts, except RBD network storage, so that you can re-add them if an issue occurs after editing.

·     Back up the names and paths of non-local image storage and stateful failover shared storage so that you can re-add them if an issue occurs after editing. In addition, back up IDV and VOI/TCI images in the image pool.

·     Disable all VMs. Navigate to Data Center > Virtualization to make all hosts enter the maintenance mode. Make sure the network of each management node and service node is reachable.

·     If the campus space is deployed in the teaching scenario, stop the campus space from the Applications > Campus Space page on Space Console.

·     To recover to the client environment after editing the IP address or virtual IP address of Space Console, configure the server address to which the client is connected as the edited IP address or virtual IP address of Space Console in advance. For more information, see "Editing the address and name of the server connected to the client." If bulk editing is not necessary, edit the network configuration on the client after network changes.

·     Before editing the management network configuration, make sure all management nodes and service nodes are connected. At the same time, plan the network in advance to ensure the connectivity of the new network. For example, make sure the edited management network IP is reachable to third-party components such as the LDAP server, mail server, shared storage, monitor platform address, and license server.

·     If access node expansion is enabled from the System > Advanced Settings > Access Node Expansion page, delete access node expansion settings before edit the management network VIP. Then, configure access node expansion settings as needed after you edit the management network VIP.

Editing management network configuration

Compute virtualization scenario

1.     From the left navigation pane, select Data Center > Virtualization.

Figure 1 Virtualization

 

2.     Click Management Network Config. For information on parameters on this page, see Table 1.

	NOTE: After accessing this page, the system will query the topology of the current environment. Wait for the data to load.

 

Figure 2 Management Network Configuration page

 

3.     Identify whether the VIP and node information are consistent with the physical topology of the cluster. If not, identify whether the network communication is normal.

4.     Verify that the VIP and node information are correct, and then click Edit.

Figure 3 Edit page

 

5.     Enter the new network information.

	IMPORTANT: Make sure the network information is correct and the network is reachable.

 

6.     Click OK. In the confirmation dialog box that opens, read the alarm information carefully, select I am fully aware of the impacts of this operation, enter the admin password, and then click OK to save the changes.

Figure 4 Confirmation dialog box

 

	IMPORTANT: ·     During the modification of the network configuration, do not perform any operations. The modification may take a long time. ·     If the IP address of Space Console is edited, the original IP address will be invalid and the server will be restarted. Therefore, record the new address, and log in with the new address after the server is restarted.

 

7.     Log in to Space Console with the new IP address, and access the management network configuration page to verify the new network configuration information.

HCI scenario (non two-node deployment)

1.     From the left navigation pane, select Data Center > Virtualization.

2.     Click Manage Network Config. For information on parameters on this page, see Table 1.

	NOTE: After accessing this page, the system will query the topology of the current environment. Wait for the data to load.

 

3.     Manage Network Configuration page

 

Table 1 Parameters

Type	Parameter	Description
Virtual IP Info	Virtual IP/Mask	Specify the IP address and network prefix length. The IP address must be an IP address not in use. As a best practice, use this IP address to access Space Console.
	Service Network Virtual IP/Mask	Configure the virtual IP address of the service network if the management network and the service network are isolated and the VM network is on the service network in a stateful failover system. This ensures that VMs on the service network can correctly communicate with the management platform. Make sure the service network VIP and the service network vSwitch IP addresses of the primary and standby management nodes are on the same network segment.
	Quorum IP 1	You must specify two different quorum IP addresses if you select the Ping quorum mode for the stateful failover system. A quorum IP address is the IP address of a gateway that can be accessed or the IP address of a host that is always reachable. The quorum IP address is used to check the network connectivity of the hosts. As a best practice, specify the IP address of a gateway.
	Quorum IP 2	You must specify two different quorum IP addresses if you select the Ping quorum mode for the stateful failover system. A quorum IP address is the IP address of a gateway that can be accessed or the IP address of a host that is always reachable. The quorum IP address is used to check the network connectivity of the hosts. As a best practice, specify the IP address of a gateway.
	Quorum Host IP/Mask	Specify the IP address and network prefix length of the quorum host when you select the Advanced quorum mode for the stateful failover system. The quorum host must have Space Console installed.
	Quorum Host Gateway	Specify the IP address of the quorum host.
	Quorum Mode	Select a quorum mode for the stateful failover system. Options include Advanced and Ping. ·     Advanced: When the primary and backup hosts cannot communicate with each other, they send their respective state information to the quorum host. The quorum host determines the role of each node and sends the role information to the nodes. The quorum host must have Space Console installed. As a best practice, use a host in the cluster as a quorum host. ·     Ping: Specify two quorum IP addresses. When the primary and backup hosts cannot communicate with each other, they ping the quorum IP addresses. If a node fails to ping any quorum IP address, the node determines that it has network failures and becomes a backup node.
	Storage Component VIP	Virtual IP address used for high availability management of the distributed storage system. It must be an unused IP address in the management network.
Node Info	Management Network Gateway	Gateway address of the management network.
	Management Network Segment	Network segment where the management network resides.
	Management IP/Mask	IP address and network prefix length of the host OS.
	Host Gateway	Gateway address of the host.
	Host Type	Role of the host in the cluster.
Storage Node Pool Info	Storage Component VIP	Virtual IP address used for high availability management of the distributed storage system. It must be an unused IP address in the management network.
	Management Network Segment	Network segment where the management network resides.
	Storage Front-end Network Segment	Storage front-end network segment of the storage cluster.
	Storage Back-end Network Segment	Storage back-end network segment of the storage cluster.
	Management IP	IP address of the host in the management network segment.
	Storage Front-end Network IP	IP address of the host in the storage front-end network segment.
	Storage Back-end Network IP	IP address of the host in the storage back-end network segment.

 

4.     Identify whether information about the VIP, node, and storage node pool is consistent with the physical topology of the cluster. If not, identify whether the network communication is normal.

5.     Verify that information about the VIP, node, and storage node pool is correct, and then click Edit.

Figure 5 Edit page

 

6.     Enter the new network information.

IMPORTANT: To edit the management network configuration, be sure to meet the following requirements: ·     The new network information is correct and the new network is reachable. ·     The VIP address and storage component VIP address in the storage information area must be consistent with that in the storage node pool information area. ·     The management network segment in the node information area should be consistent with that in the storage node pool information area. ·     The management IP address/mask in the node information area should be consistent with the management network IP in the storage node pool information area.

 

NOTE: ·     When you edit the management IP address, make sure the storage component VIP resides on the primary node of the stateful failover system. ·     When you edit the storage component VIP, update the management network IP of at least one storage node pool. In addition, change the corresponding host management IP to the same address. To edit only the storage component VIP, contact Technical Support.

 

7.     Click OK. In the confirmation dialog box that opens, read the alarm information carefully, select I am fully aware of the impacts of this operation, enter the admin password, and then click OK to save the changes.

Figure 6 Confirmation dialog box

 

	IMPORTANT: ·     During the modification of the network configuration, do not perform any operations. The modification may take a long time. ·     If the IP address of Space Console is edited, the original IP address will be invalid and the server will restart. Therefore, record the new address, and log in with the new address after the server is restarted.

 

8.     Log in to Space Console with the new IP address, and access the management network configuration page to verify the new network configuration information.

NOTE: In the HCI scenario, the command line will execute the ONEStor script modification command after the system is restarted, so the management network configuration page may fail to read the management network configuration information after the modification of the management network configuration. This process takes a while. After the command execution is completed, the management network configuration page will read the new management network configuration information. To identify whether the command execution is complete, go to Monitor Reports > Logs > System Logs > Desktop Logs.

 

HCI scenario (two-node deployment)

1.     Confirm the current worker node of ONEStor. Execute the sudo onestor cm query -t handyha command at the CLI of the management node. The master node is the current worker node of ONEStor.

Figure 7 Confirming the current worker node

 

2.     Use the SSH tool to access the CLI of the worker node of ONEStor, and execute the onestor modify modify_ip export command to export the host information to the /opt/h3c/modify_ip/ path.

Figure 8 Exporting host information successfully

 

3.     Execute the vim /opt/h3c/modify_ip/cluster_ip_infos.json command to open the host information file, and then press i to edit the host information. Add the parameter information of the fields shown in Table 2 below the original fields. Keep other fields unchanged if they do not require modification. After the modification is completed, execute the :wq! command to save the changes.

Table 2 Field description

Field	Description
new_handy_vip	Storage component VIP
new_manage_ip	Management IP addresses
new_manage_network	Management network segment in the format of IP/network prefix bits.

 

Figure 9 Editing host information

 

4.     Execute the preprocessing command for editing an IP address on the current worker node of ONEStor.

onestor modify modify_ip prepare.

Figure 10 Preprocessing operation succeeded

 

	NOTE: If a prompt displaying "Prepare request has accomplished, please do not execute prepare again." appears, execute the onestor edit edit_ip rollback command first, and then execute the preprocessing command.

 

5.     Use the SSH tool to access the CLI of the management node or the primary node of the stateful failover system and execute the cd /opt/vdi/ command to enter the corresponding directory.

6.     Execute the ./modify_hosts_ip.sh command to export all host information to the current path in the name of hosts_network_info.

Figure 11 Exporting host information

 

7.     Execute the cat hosts_network_info command to view the exported hosts_network_info file. This step uses the file content in the stateful failover system as an example:

"vip":"10.125.60.39/23","new_vip":""

"vb_ip":"10.125.60.87/23","new_vb_ip":""

"quorum_ip_1":"10.125.60.1","new_quorum_ip_1":"","quorum_ip_2":"10.125.112.210","new_quorum_ip_2":"","type_quorum":"ping"

"storage_ip":"10.125.60.85","new_storage_ip":""

"cluster_id":"1","cluster_name":"cluster_0","start_ip_mask":"10.125.60.50/23","new_start_ip_mask":"","cluster_gateway":"10.125.60.1,"cluster_new_gateway":""

"cluster_id":"3","cluster_name":"1010TestCluster","start_ip_mask":"10.125.60.100/23","new_start_ip_mask":"","cluster_gateway":"10.125.60.1,"cluster_new_gateway":""

"hostname":"cvknode1","ip_mask":"10.125.60.86/23","gateway":"10.125.60.1","new_ip_mask":"","new_gateway":"","type":"cvm_master","cluster_name":"cluster_0"

"hostname":"cvknode2","ip_mask":"10.125.60.123/23","gateway":"10.125.60.1","new_ip_mask":"","new_gateway":"","type":"cvm_slave","cluster_name":"cluster_0"

"hostname":"cvknode3","ip_mask":"10.125.60.122/23","gateway":"10.125.60.1","new_ip_mask":"","new_gateway":"","type":"cvk","cluster_name":"cluster_0"

"hostname":"cvknode4","ip_mask":"10.125.60.107/23","gateway":"10.125.60.1","new_ip_mask":"","new_gateway":"","type":"cvk","cluster_name":"1010TestCluster"

"hostname":"cvknode5","ip_mask":"10.125.60.108/23","gateway":"10.125.60.1","new_ip_mask":"","new_gateway":"","type":"cvk","cluster_name":"1010TestCluster"

"hostname":"cvknode6","ip_mask":"10.125.60.109/23","gateway":"10.125.60.1","new_ip_mask":"","new_gateway":"","type":"cvk","cluster_name":"1010TestCluster"

Table 3 Field description

Field	Description
new_vip	Virtual IP address of the stateful failover system in the format of IP/mask. This field is available in the stateful failover scenario.
new_vb_ip	Service network virtual IP address in the format of IP/mask.
controller_new_ip_mask	Quorum host IP for the stateful failover system. This field is available when the Advanced quorum mode is specified in the stateful failover scenario.
new_quorum_ip_1	Quorum IP address 1 for the stateful failover system. This field is available when the Ping quorum mode is specified in the stateful failover scenario.
new_quorum_ip_2	Quorum IP address 2 for the stateful failover system. This field is available when the Ping quorum mode is specified in the stateful failover scenario.
new_storage_ip	Storage component VIP. This field is available in the stateful failover scenario.
new_start_ip_mask	Start management network segment in a clutser in the format of IP/mask. If multiple clusters are configured in the HCI scenario, the file displays this field for each cluster.
cluster_new_gateway	IP address of the gateway for the management network in a cluster. If multiple clusters are configured in the HCI scenario, the file displays this field for each cluster. Make sure this IP address resides on the same network segment as the new_manage_network field.
new_ip_mask	Host IP address in the format of IP/mask.
new_gateway	IP address of the host gateway

 

8.     Execute the vim hosts_network_info command to open the file, and press i to enter the editing mode. Enter the values for the gray fields in the previous step as needed. Keep other fields unchanged if they do not require modification. _Ref118361195 shows the fields in the file.

IMPORTANT: Make sure the new IP addresses specified in this step are the same as those in step 3.

 

9.     Press Esc to exit the editing mode. Then, enter :wq! and press Enter to save the modification.

The following is an example to edit the content:

a.     Change the sevice network VIP to 10.125.60.89/23, and enter 10.125.60.89/23 for new_vb_vip.

b.     Change the storage component VIP to 10.125.60.37, and enter 10.125.60.37 for new_storage_ip.

c.     Change the host IP address of cvknode1 to 10.125.60.36/23, and enter 10.125.12.37/22 for new_ip_mask.

d.     Follow the step for cvknode1 to edit the IP address of cvknode5.

Figure 12 File content before modification

 

Figure 13 File content after modification

 

10.     Execute the following command to edit the host network information file.

./modify_hosts_ip.sh hosts_network_info

Figure 14 Executing the modification command

 

11.     The information to be edited is automatically printed in the window. Verify the information, and then enter yes as prompted to start the modification.

The host restarts automatically after the modification.

Figure 15 Confirming the modification

 

12.     If ONEStor has a monitor node, edit the network information in the /etc/sysconfig/network-scripts/ifcfg-vswitch0 file on the monitor node, and then execute the service network restart command to restart the network.

13.     After the network configuration is edited, Execute the onestor modify modify_ip modify command at the CLI the original worker node of ONEStor.

NOTE: The original worker node of ONEStor refers to the master node obtained in step 1 before you edit network configuration.

 

Figure 16 Editing the ONEStor IP address successfully

 

Restoring the environment

After the management network configuration is edited, use the new IP address to log in to Space Console. Then, check and restore the environment as needed.

Editing the handy IP address (HCI scenario)

If the storage component VIP has changed, edit the handy IP address for distributed storage as follows:

1.     From the left navigation pane, select Data Center > Virtualization.

Figure 17 Virtualization page

 

2.     Click Distributed Storage.

3.     Click Edit in the Actions column for a distributed storage resource.

Figure 18 Clicking Edit

 

4.     Enter the new handy IP, and then click OK.

	NOTE: Specify the handy IP as the storage component VIP in the VIP information area.

 

Figure 19 Editing the handy IP address

 

5.     Click More in the Actions column for the distributed storage edited in the previous step, and select Sync ONEStor Settings from the drop-down menu.

Figure 20 Synchronizing the ONEStor configuration

 

Removing hosts from maintenance mode

1.     From the left navigation pane, select Data Center > Virtualization.

2.     Click a cluster name from the left navigation pane, click More, and then select Connect to All Hosts. In the confirmation dialog box that opens, click OK.

Figure 21 Connecting all hosts

 

3.     Click a host name on the left, click Exit Maintenance Mode at the right side of the page, and then click OK in the confirmation dialog box that opens.

4.     Repeat the step on other hosts until all hosts exit the maintenance mode.

Figure 22 Removing hosts from maintenance mode

 

Querying the availability of non-local storages

Identify whether the non-local storage, non-local image storage, and two-node cluster storage are active or available. If not, delete them and add them again. To add them again:

1.     From the left navigation pane, select Data Center > Virtualization.

2.     Click a host name in the cluster from the left navigation pane, and then click the Storage tab.

3.     Click Create. On the page that opens, configure relevant parameters to add a non-local storage. For detailed operations, see the cluster management tasks in H3C Workspace Space Console User Manual.

Figure 23 Virtualization page

 

Figure 24 Adding a storage pool

 

4.     From the left navigation pane, select Images.

5.     Click the Image Pools tab. Click Create Image Pool. In the dialog box that opens, configure relevant parameters to add a non-local storage. For detailed operations, see the image pool tasks in H3C Workspace Space Console User Manual.

Figure 25 Image Pools page

 

Figure 26 Creating an image pool

 

6.     From the left navigation pane, select System > Failover System Management > Shared Storage.

7.     Click Create. In the dialog box that opens, configure relevant parameters to add a shared storage. For detailed operations, see H3C Workspace Space Console User Manual.

Figure 27 Shared storage page

 

Figure 28 Adding a shared storage

 

Editing the VM communication address

After changing the IP address of Space Console, you need to edit the VM communication address. The VM will restart and the Agent will automatically edit the address after the VM communication address is changed.

1.     From the left navigation pane, select System > Advanced Settings > Cloud Desktop Parameters.

2.     Click the Edit icon in the bottom of the page, set the VM communication address, and then click OK.

Figure 29 Editing the VM communication address

 

Editing the communication address of the PC agent

To edit the communication address of the physical host after changing the IP address of Space Console:

1.     Access the C:\Program Files (x86)\H3C\PCAgent\conf path.

Figure 30 Accessing the path

 

2.     Open the file named grpc_config.cfgw with a tool such as Notepad or Notepad++.

3.     Change GrpcAddress to the new Space Console IP address or VIP address, save it, and then exit.

Figure 31 Editing GrpcAddress

 

Checking the connectivity of third-party components

Perform this task to identify whether Space Console is reachable to third-party components such as the LDAP server, mail server, shared storage, monitor platform address, and license server.

Handling host heartbeat abnormal alarms

Perform the following operations if Space Console has host heartbeat abnormal alarms.

1.     Access the CLI of the management node through an SSH tool.

2.     Execute the service cas_mon restart command to restore the host heartbeat.

Starting the campus space

If the campus space is deployed before you edit the management network configuration, you need to restart the campus space after the modification.

1.     From the left navigation pane, select Applications > Campus Space.

2.     Click Start All, and then click OK in the confirmation dialog box that opens.

Figure 32 Campus space page

 

Editing the management relationship on Space Center

If Space Console is managed by Space Center before you edit its management network configuration, you need to manage Space Console again on Space Center after the modification. For specific operations, see H3C Space Center Hierarchical Management System User Manual.

Editing the security gateway

If a security gateway is configured before you edit the management network configuration, you need to edit the security gateway after the modification.

1.     Log in to the command line of the security gateway VM through an SSH tool.

2.     Execute the gateway proxy -c new_ip command on the security gateway. The new_ip field represents the new IP address of Space Console.

Viewing configuration records

After the management network configuration is edited, you can view history configuration records and information such as editing time of the page, operators, and operation details on Space Console.

1.     From the left navigation pane, select System > Advanced Settings > Manage Network Configuration.

2.     Click the Configuration Record tab, and then all the history configuration records are listed.

Figure 33 Configuration records

 

3.     Click View in the Actions column for the target configuration record item. In the verification dialog box that opens, select I am fully aware of the impacts of this operation, enter the admin password, Click OK, and then the detailed configuration records are displayed.

Figure 34 Verification dialog box

 

Figure 35 Detailed operations

 

Appendix

Viewing the reason for failing to edit the management network configuration

If the management network configuration fails to be edited, you can view the admin operation logs on Space Console. To view the operation logs:

1.     From the left navigation pane, select Monitor Reports > Logs > Admin Operation Logs > Cloud Desktop Logs.

2.     View the related logs for the failure reason.

Handling a failure to edit the management network configuration caused by stateful failover in HCI scenario

In the HCI scenario, after the management network configuration is edited, the server automatically restarts. During the restart process, the primary and backup management nodes in the stateful failover system may be switched over, which causes the management network configuration fails to be edited. To solve the problem:

1.     Select System > Failover System Management > Stateful Failover System from the left navigation pane. If the primary and backup management nodes have been switched over, click Primary/Backup Switchover, and then click OK in the confirmation box that opens.

2.     Log in to the command line of the main node through an SSH tool after the switchover between the primary and backup management nodes of the stateful failover system.

3.     Execute the onestor edit edit_ip edit command.

4.     The configuration is completed after executing the command.

Editing the address and name of the server connected to the client

To recover to the client environment after editing the IP address or virtual IP address of Space Console, you need to configure the server address to which the client is connected as the edited IP address or virtual IP address of Space Console in advance.

	NOTE: This method takes effect only on SpaceOS endpoints. On endpoints with Windows OSs installed, change the address according to the actual situation. The user profile is stored in the user directory and the address is set by the user. Therefore, the address of the user profile is different.

 

Editing the address and name of the server connected to the VDI client

	IMPORTANT: Disable the client on the endpoints before executing any commands.

 

To edit the address and name of the server connected to the VDI client:

1.     From the left navigation pane, select System > Issuing Commands.

Figure 36 Issuing the commands

 

2.     Click Create. On the page that opens, configure relevant parameters such as command name and command, and issue the commands shown in Table 4 in sequence.

Figure 37 Creating commands

 

Table 4 Adding commands

Command name	Command	Description
Updata_SeverIP_1	sed –i 's/SERVERIP=<old IP address of the server>/SERVERIP=<new IP address of the server>/g'/home/spaceos/Documents/Workspace/settings.ini	Edit the address of the server connected to the client.
Updata_SeverIP_2	sed -i 's/SERVERNAME=<old IP address of the server>/SERVERNAME=<new IP address of the server>/g'/home/spaceos/Documents/Workspace/settings.ini	Edit the name of the server connected to the client.
Updata_SeverIP_3	sync	Sync
Updata_SeverIP_4	reboot	Reboot

 

3.     Select Endpoints for the issuing target, click Add Endpoints or Add Endpoint Groups, select the endpoint or group to be edited, and then click OK.

Figure 38 Selecting the endpoint

 

Figure 39 Selecting the endpoint group

 

4.     Click OK.

Figure 40 Issuing the commands successfully

 

5.     The endpoint will restart automatically after all commands are issued. After the endpoint is restarted, identify whether the address and name of the server connected to the client are edited successfully, and identify whether the login and other features of the cloud desktop are normal.

Figure 41 Modification of the endpoint server completed

 

Editing the address of the server connected to the IDV, VOI, and UCC clients

1.     From the left navigation pane, select System > Issuing Commands.

Figure 42 Issuing the commands

 

2.     Click Create. On the page that opens, configure relevant parameters such as command name and command, and enter the following command.

service u3client stop && sed -i "s/<old IP address of the server>/<new IP address of the server>/g" /etc/u3client/u3client_cfg.db && service u3client start

Figure 43 Creating commands

 

3.     Select Endpoints for the issuing target, click Add Endpoints or Add Endpoint Groups, select the endpoint or group to be edited, and then click OK.

Figure 44 Selecting the endpoint

 

Figure 45 Selecting the endpoint group

 

4.     Click OK.

Figure 46 Issuing the commands successfully

 

Related documentation

Document	Obtaining method
H3C Workspace Space Console User Manual	https://www.h3c.com/cn/Service/Document_Software/Document_Center/H3Cloud/Catalog/H3C_Cloud_YZM/H3C_Workspace/
H3C Space Center Hierarchical Management System User Manual