Take over the OMS in split mode

This topic describes how to take over the OMS in split mode by using OAT. After the new version of OAT was restructured, earlier versions cannot be smoothly upgraded. The OMS previously deployed in split mode by using OAT must be taken over by the new version of OAT to enable status monitoring, upgrades, and other management tasks.

Prerequisites

Before you take over OMS in split mode, confirm the following:

• You have added the OMS Console image and OMS Component image.
• You have taken over the components (MetaDB, InfluxDB) that OMS depends on.
• You have added the server for taking over OMS. For more information, see Add a server.
• Your server meets the requirements for taking over OMS. For more information, see OMS resource configuration specifications.

Considerations

• In a multi-region deployment, each region must have a Management Container and a Component Container.
• Both the console (8089) and CM (8088) services reside in the Management Container. When configuring load balancing, follow the deployment pattern of the Management Container, setting up one load balancing rule per region.
• The Management Container supports setting a primary region: after setting a primary region, only the first management node in the primary region starts the console and CM services; other management container nodes start only the CM service.

Procedure

To take over OMS in split mode, perform the following steps:

1. In the left navigation bar, click Product Service > Product Management.

2. On the Product management page, click Take over the product in the upper-right corner, and select Take over OMS.

3. In the pop-up window, select Separate mode. Management and components are deployed using different images.

4. On the Take over OMS page, for Console Configuration:

   Parameter	Description
   OMS Console Image	Select the OMS Console image.
   Product Name	Specify the product name, which must be unique.
   Server	Select the IP address of the server for taking over the OMS Console.
   CPU	Set the number of CPU cores available to OMS Console on each server. Default is 8C.
   Memory	Set the memory available to OMS Console on each server. Default is 32G.
   HTTP Port	The port for the product's external HTTP service. Default is 8089 and cannot be modified.

5. On the Take over OMS page, for Component Configuration:

   Parameter	Description
   OMS Component Image	Select the OMS Component image.
   Server	Select the IP address of the server for taking over the OMS Component.
   CPU	Set the number of CPU cores available to OMS Component on each server. Default is 8C.
   Memory	Set the memory available to OMS Component on each server. Default is 32G.

6. On the Take over OMS page, for MetaDB Configuration:

   Parameter	Description
   MetaDB Type	Select the type of MetaDB. Options: <li Created MetaDB<li Other OB_MySQL
   Select Created MetaDB	Select an existing MetaDB for OMS. This option appears when MetaDB Type is set to Existing MetaDB. You can select from a drop-down list or click +Create MetaDB to create a new MetaDB.

7. On the Take over OMS page, for InfluxDB Configuration:

   Parameter	Description
   Time Series Database Storage	Select the type of InfluxDB. Options: Created InfluxDB Other InfluxDB
   Select Created InfluxDB	Select an existing InfluxDB for OMS. This option is displayed when Time Series Database Storage is set to InfluxDB has been created.. You can select an existing InfluxDB from the drop-down list.

8. On the Take over OMS page, for Load Balancing Configuration:

   The load balancing modes are as follows:

   • Created NLB: NLB automatically adds a load rule for the product's actual HTTP service address based on the VIP and VPORT you entered.

     Parameter	Description
     Select Created NLB	Select an existing NLB.
     Console VIP	The Console VIP is automatically filled in and cannot be edited.
     Console Service Port	Specify the Console service port number.
     CM VIP	The CM VIP is automatically filled in and cannot be edited.
     CM Service Port	Specify the CM service port number.

   • Existing OBDNS: OBDNS automatically adds a load rule for the product's actual HTTP service address based on the Domain Name and VPORT you entered.

     Parameter	Description
     Select Created OBDNS	Select an existing OBDNS.
     OMS Console HTTP Proxy Domain Name	Specify the OMS console HTTP proxy domain name.
     OMS Console HTTP Proxy Port	Specify the OMS console HTTP proxy port.
     OMS CM Component HTTP Proxy Domain Name	Specify the OMS CM component HTTP proxy domain name.
     OMS CM Component HTTP Proxy Port	Specify the OMS CM component HTTP proxy port. The default value is 8088.

   • Other load balancer:

     Parameter	Description
     MetaDB TCP Proxy Address	Specify the MetaDB TCP proxy address.
     MetaDB TCP Proxy Port	Specify the MetaDB TCP proxy port. The default value is 3306.
     OMS Console HTTP Proxy IP	Specify the OMS console HTTP proxy IP.
     OMS Console HTTP Proxy Port	Specify the OMS console HTTP proxy port.
     OMS CM Component HTTP Proxy IP	Specify the OMS CM component HTTP proxy IP.
     OMS CM Component HTTP Proxy Port	Specify the OMS CM component HTTP proxy port.

   • Do Not Use: If you choose not to use load balancing, high availability will not be available. By default, the IP address of the first server is used as the connection information.

9. After completing the OMS takeover configuration, click Submit.

   If your configuration is incorrect, click Reset to restore the default configuration with one click.

What to do next

After taking over OMS in split mode, you can upgrade OMS. For more information, see Upgrade OMS.