Shulou(Shulou.com)05/31 Report--

Editor to share with you how DM7 uses DMASM to install DMRAC. I hope you will get something after reading this article. Let's discuss it together.

one。 Environmental preparation

Host IP address (external service) IP address (internal communication) instance name operating system

Dmrac1 10.18.13.161 10.10.10.161 rac0 Redhat 6.7

Dmrac2 10.18.13.162 10.10.10.162 rac1 Redhat 6.7

Shared storage

/ dev/sdb / dev/raw/raw1 dcr disk 2G

/ dev/sdc / dev/raw/raw2 voting disk 2G

/ dev/sdd / dev/raw/raw3 log disk 10G

/ dev/sde / dev/raw/raw4 data disk1 10G

/ dev/sdf / dev/raw/raw5 data disk2 10G

II. Operating system configuration

1. Turn off the firewall and SELINUX

[root@cs ~] # service iptables stopiptables: Setting chains to policy ACCEPT: nat mangle filter [OK] iptables: Flushing firewall rules: [OK] iptables: Unloading modules: [OK] [root@cs ~] # chkconfig iptables off [root@cs ~] # setenforce 0 [root@cs ~] # sed-is: ^ Selinus =. * $: SELINUX=disabled:g / etc/selinux/config [root@cs ~] # service iptables stopiptables: Setting chains to policy ACCEPT: nat mangle filter [OK] iptables: Flushing firewall rules: [OK] Iptables: Unloading modules: [OK] [root@cs ~] # chkconfig iptables off [root@cs ~] # setenforce 0 [root@cs ~] # sed-is: ^ Selinux =. * $: SELINUX=disabled:g / etc/selinux/config

2. Modify the host name

[root@cs ~] # hostname dmrac1 [root@cs ~] # hostname dmrac2 [root@cs ~] # sed-I s: ^ hostname =. * $: HOSTNAME=dmrac1:g / etc/sysconfig/network [root@cs ~] # sed-I s: ^ hostname =. * $: HOSTNAME=dmrac2:g / etc/sysconfig/network

3. Modify hosts file

[root@cs ~] # echo "> 10.18.13.161 dmrac1 > 10.18.13.162 dmrac2" > / etc/hosts [root@cs ~] # echo "> 10.18.13.161 dmrac1 > 10.18.13.162 dmrac2" > > / etc/hosts

Third, install Dameng software

In order to reduce the impact on the operating system, users should not install and run DM as root system users. Users can create a dedicated system user for DM prior to installation. For more information, please see installing Dameng database DM7 in Oracle Linux 7.1for more information.

4. Bind UDEV

[root@dmrac1 rules.d] # vi 99dmmurf devices.rulesAction = "add", KERNEL== "sdb", RUN+= "/ bin/raw / dev/raw/raw1% N" ACTION== "add", KERNEL== "sdc", RUN+= "/ bin/raw / dev/raw/raw2% N" ACTION== "add", KERNEL== "sdd", RUN+= "/ bin/raw / dev/raw/raw3% N" ACTION== "add", KERNEL== "sde", RUN+= "/ bin/raw / dev/raw/raw4% N" ACTION== "add", KERNEL== "sdf" RUN+= "/ bin/raw / dev/raw/raw5% N" ACTION== "add", KERNEL== "raw [1-5]", OWNER= "dmdba", GROUP= "dinstall", MODE= "660" ~ [root@dmrac1 rules.d] # start_udevStarting udev: [OK] [root@dmrac1 rules.d] # ls-lrt / dev/raw/total 0crwMuk. 1 root disk 162, 0 Apr 24 14:08 rawctlcrw-rw----. 1 dmdba dinstall 162, 2 Apr 24 14:08 raw2crw-rw----. 1 dmdba dinstall 162, 1 Apr 24 14:08 raw1crw-rw----. 1 dmdba dinstall 162, 4 Apr 24 14:08 raw4crw-rw----. 1 dmdba dinstall 162, 3 Apr 24 14:08 raw3crw-rw----. 1 dmdba dinstall 162,5 Apr 24 14:08 raw5 [root@dmrac2 rules.d] # vi 99Merdlydevices.rulesAction = "add", KERNEL== "sdb", RUN+= "/ bin/raw / dev/raw/raw1% N" ACTION== "add", KERNEL== "sdc", RUN+= "/ bin/raw / dev/raw/raw2% N" ACTION== "add", KERNEL== "sdd", RUN+= "/ bin/raw / dev/raw/raw3% N" ACTION== "add", KERNEL== "sde" RUN+= "/ bin/raw / dev/raw/raw4% N" ACTION== "add", KERNEL== "sdf", RUN+= "/ bin/raw / dev/raw/raw5% N" ACTION== "add", KERNEL== "raw [1-5]", OWNER= "dmdba", GROUP= "dinstall", MODE= "660" ~ [root@dmrac2 rules.d] # start_udevStarting udev: [OK] [root@dmrac2 rules.d] # ls-lrt / dev/raw/total 0crwMusure. 1 root disk 162, 0 Apr 24 14:08 rawctlcrw-rw----. 1 dmdba dinstall 162, 2 Apr 24 14:08 raw2crw-rw----. 1 dmdba dinstall 162, 1 Apr 24 14:08 raw1crw-rw----. 1 dmdba dinstall 162, 4 Apr 24 14:08 raw4crw-rw----. 1 dmdba dinstall 162, 3 Apr 24 14:08 raw3crw-rw----. 1 dmdba dinstall 162, 5 Apr 24 14:08 raw5

You can view the size of bare devices by using the blockdev-- getsize64 / dev/raw/raw1 command

[root@dmrac1 rules.d] # blockdev-getsize64 / dev/raw/raw12147483648 [root@dmrac1 rules.d] # blockdev-getsize64 / dev/raw/raw22147483648 [root@dmrac1 rules.d] # blockdev-getsize64 / dev/raw/raw310737418240 [root@dmrac1 rules.d] # blockdev-getsize64 / dev/raw/raw410737418240 [root@dmrac1 rules.d] # blockdev-getsize64 / dev/raw/raw510737418240 [root@dmrac2 rules.d] # blockdev-getsize64 / dev/raw/raw12147483648 [root@dmrac2 rules. D] # blockdev-- getsize64 / dev/raw/raw22147483648 [root@dmrac2 rules.d] # blockdev-- getsize64 / dev/raw/raw310737418240 [root@dmrac2 rules.d] # blockdev-- getsize64 / dev/raw/raw410737418240 [root@dmrac2 rules.d] # blockdev-- getsize64 / dev/raw/raw510737418240

6. Configure dmdcr_cfg.ini file

Create the configuration file dmdcr_cfg.ini under the / dm7/data directory of the 2 nodes and add the following to the file:

[root@dmrac1 /] # su-dmdba [dmdba@dmrac1 ~] $mkdir / dm7/data [dmdba@dmrac1 ~] $cd / dm7/data [dmdba@dmrac1 data] $cat dmdcr_cfg.iniDCR_N_GRP = 3DCR_VTD_PATH = / dev/raw/raw2DCR_OGUID = 63635 [GRP] DCR_GRP_TYPE = CSSDCR_GRP_NAME = GRP_CSSDCR_GRP_N_EP = 2DCR_GRP_DSKCHK_CNT = 60 [GRP_CSS] DCR_EP_NAME = CSS0DCR_EP_HOST = 10. 10.10.161DCR_EP_PORT = 9541 [GRP_CSS] DCR_EP_NAME = CSS1DCR_EP_HOST = 10.10.10.162DCR_EP_PORT = 9542 [GRP] DCR_GRP_TYPE = ASMDCR_GRP_NAME = GRP_ASMDCR_GRP_N_EP = 2DCR_GRP_DSKCHK_CNT = 60 [GRP_ASM] DCR_EP_NAME = ASM0DCR_EP_SHM_KEY = 93360DCR_EP_SHM_SIZE = 10DCR_EP_HOST = 10.18.13.161DCR_EP_PORT = 9641DCR_EP_ASM_LOAD_PATH = / dev/ raw [GRP _ ASM] DCR_EP_NAME = ASM1DCR_EP_SHM_KEY = 93361DCR_EP_SHM_SIZE = 10DCR_EP_HOST = 10.18.13.162DCR_EP_PORT = 9642DCR_EP_ASM_LOAD_PATH = / dev/ raw [GRP] DCR_GRP_TYPE = DBDCR_GRP_NAME = GRP_RACDCR_GRP_N_EP = 2DCR_GRP_DSKCHK_CNT = 60 [GRP_RAC] DCR_EP_NAME = RAC0DCR_ EP_SEQNO = 0DCR_EP_PORT = 5236DCR_CHECK_PORT = 9741 [GRP_RAC] DCR_EP_NAME = RAC1DCR_EP_SEQNO = 1DCR_EP_PORT = 5236DCR_CHECK_PORT = 9742 [root@dmrac2 /] # su-dmdba [dmdba@dmrac2 ~] $mkdir / dm7/data [dmdba@dmrac2 ~] $cd / dm7/data [dmdba@dmrac2 data] $cat dmdcr_cfg.iniDCR_N_GRP = 3DCR_VTD_PATH = / dev/raw/raw2DCR_OGUID = 63635 [GRP] DCR_GRP _ TYPE = CSSDCR_GRP_NAME = GRP_CSSDCR_GRP_N_EP = 2DCR_GRP_DSKCHK_CNT = 60 [GRP_CSS] DCR_EP_NAME = CSS0DCR_EP_HOST = 10.10.10.161DCR_EP_PORT = 9541 [GRP_CSS] DCR_EP_NAME = CSS1DCR_EP_HOST = 10.10.10.162DCR_EP_PORT = 9542 [GRP] DCR_GRP_TYPE = ASMDCR_GRP_NAME = GRP_ASMDCR_GRP_N_EP = 2DCR_GRP_DSKCHK_CNT = 60 [GRP_ASM] DCR_EP_NAME = ASM0DCR_EP_SHM_KEY = 93360DCR_EP_SHM_SIZE = 10DCR_EP_HOST = 10.18.13.161DCR_EP_PORT = 9641DCR_EP_ASM_LOAD_PATH = / dev/ raw [GRP _ ASM] DCR_EP_NAME = ASM1DCR_EP_SHM_KEY = 93361DCR_EP_SHM_SIZE = 10DCR_EP_HOST = 10.18.13.162DCR_EP_PORT = 9642DCR_EP_ASM_LOAD_PATH = / dev/raw [GRP] DCR_GRP_TYPE = DBDCR_GRP_NAME = GRP_RACDCR_GRP_N_EP = 2DCR_GRP_DSKCHK_CNT = 60 [GRP_RAC] DCR_EP_NAME = RAC0DCR_EP_SEQNO = 0DCR_EP_PORT = 5236DCR_CHECK_PORT = 9741 [GRP_RAC] DCR_EP_NAME = RAC1DCR_EP_SEQNO = 1DCR_EP_PORT = 5236DCR_CHECK_PORT = 9742

Initialization using the DMASMCMD tool (executed by any node)

[dmdba@dmrac1 data] $dmasmcmdDMASMCMD V7.1.6.46-Build (2018.02.08-89107) ENTASM > create dcrdisk'/ dev/raw/raw1' 'dcr'the ASM initialize dcrdisk / dev/raw/raw1 to name DMASMdcrUsed time: 9.322 (ms) .ASM > create votedisk' / dev/raw/raw2' 'vote'the ASM initialize votedisk / dev/raw/raw2 to name DMASMvoteUsed time: 6.251 (ms) .ASM > create asmdisk' / dev/raw/raw3' 'LOG0'the ASM initialize asmdisk / dev/raw / raw3 to name DMASMLOG0Used time: 8.825 (ms) .ASM > create asmdisk'/ dev/raw/raw4' 'DATA0'the ASM initialize asmdisk / dev/raw/raw4 to name DMASMDATA0Used time: 6.145 (ms) .ASM > init dcrdisk' / dev/raw/raw1' from'/ dm7/data/dmdcr_cfg.ini' identified by 'dameng123' [Trace] DG 126 allocate 4 extents for file 0xfe000002.Check dcrdisk failed Please check and try againUsed time: 84.489 (ms). Please execute ASM > init dcrdisk'/ dev/raw/raw1' from'/ dm7/data/dmdcr_cfg.ini' identified by 'dameng123' [Trace] DG 126 allocate 4 extents for file 0xfe000002.Used time: 00:00:06.078.ASM > init votedisk' / dev/raw/raw2' from'/ dm7/data/dmdcr_cfg.ini' [Trace] DG 125 allocate 4 extents for file 0xfd000002.Used time: 36.305 (ms) again.

Prepare the MAL configuration file for DMASM

Create a DMASM MAL configuration file (named dmasvrmal.ini) under the / dm7/data directory of the 2 nodes, and all nodes that use DMASM should be configured with exactly the same content.

[dmdba@dmrac1 data] $vi dmasvrmal.ini [Mal _ INST1] MAL_INST_NAME = ASM0MAL_HOST = 10.10.10.161MAL_PORT = 7236 [MAL_INST2] MAL_INST_NAME = ASM1MAL_HOST = 10.10.10.162MAL_PORT = 7237 [dmdba@dmrac2 data] $vi d masvrmal.ini [Mal _ INST1] MAL_INST_NAME = ASM0MAL_HOST = 10.10.10.161MAL_PORT = 7236 [MAL_INST2] MAL_INST_NAME = ASM1MAL_HOST = 10.10.10.162MAL_PORT = 7237 ~

IX. Prepare dmdcr.ini configuration file

Dmdcr.ini is the input parameter for the dmcss, dmasmsvr, and dmasmtool tools. The current node serial number and DCR disk path are recorded.

Create a dmdcr.ini configuration file under the / dm/dmdbms/data directory of the two nodes, with the same dmdcr_path and the same contents of the dmasvrmal.ini file, with dmdcr_seqo of 0 and 1, respectively.

Node 1:

[dmdba@dmrac1 data] $vi dmdcr.iniDMDCR_PATH = / dev/raw/raw1DMDCR_MAL_PATH = / dm7/data/dmasvrmal.iniDMDCR_SEQNO = 0#ASMDMDCR_ASM_RESTART_INTERVAL = 0DMDCR_ASM_STARTUP_CMD = / dm7/bin/dmasmsvr dcr_ini=/dm7/data/dmdcr.ini#DBDMDCR_DB_RESTART_INTERVAL = 0DMDCR_DB_STARTUP_CMD = / dm7/bin/dmserver path=/dm7/data/rac0_config/dm.ini dcr_ini=/dm7/data/dmdcr.ini

Node 2:

[dmdba@dmrac2 data] $vi dmdcr.iniDMDCR_PATH = / dev/raw/raw1DMDCR_MAL_PATH = / dm7/data/dmasvrmal.iniDMDCR_SEQNO = 1#ASMDMDCR_ASM_RESTART_INTERVAL = 0DMDCR_ASM_STARTUP_CMD = / dm7/bin/dmasmsvr dcr_ini=/dm7/data/dmdcr.ini#DBDMDCR_DB_RESTART_INTERVAL = 0DMDCR_DB_STARTUP_CMD = / dm7/bin/dmserver path=/dm7/data/rac1_config/dm.ini dcr_ini=/dm7/data/dmdcr.ini

Start DMCSS and DMASM service programs

1. Register for DMCSS and DMASM services

Node one:

[root@dmrac1 ~] # / dm7/script/root/dm_service_installer.sh-t dmcss-I / dm7/data/dmdcr.ini-p rac1Move the service script file (/ dm7/bin/DmCSSServicerac1 to / etc/rc.d/init.d/DmCSSServicerac1) Finished to create the service (DmCSSServicerac1) [root@dmrac1 ~] # / dm7/script/root/dm_service_installer.sh-t dmasmsvr-I / dm7/data/dmdcr.ini-p rac1Move the service script file (/ dm7/bin/DmASMSvrServicerac1) To / etc/rc.d/init.d/DmASMSvrServicerac1) Finished to create the service (DmASMSvrServicerac1) [root@dmrac1 ~] #

Node 2:

[root@dmrac2 ~] # / dm7/script/root/dm_service_installer.sh-t dmcss-I / dm7/data/dmdcr.ini-p rac2Move the service script file (/ dm7/bin/DmCSSServicerac2 to / etc/rc.d/init.d/DmCSSServicerac2) Finished to create the service (DmCSSServicerac2) [root@dmrac2 ~] # / dm7/script/root/dm_service_installer.sh-t dmasmsvr-I / dm7/data/dmdcr.ini-p rac2Move the service script file (/ dm7/bin/DmASMSvrServicerac2) To / etc/rc.d/init.d/DmASMSvrServicerac2) Finished to create the service (DmASMSvrServicerac2)

2. Start DMCSS and DMASM services

Node one:

[root@dmrac1 init.d] # service DmCSSServicerac1 startStarting DmCSSServicerac1: [OK] [root@dmrac1 init.d] # service DmASMSvrServicerac1 startStarting DmASMSvrServicerac1: [OK]

Node 2:

[root@dmrac2 init.d] # service DmCSSServicerac2 startStarting DmCSSServicerac2: [OK] [root@dmrac2 init.d] # service DmASMSvrServicerac2 startStarting DmASMSvrServicerac2: [OK]

Create a DMASM disk group

Use the dmasmtool tool to create an DMASM disk group at any node.

[dmdba@dmrac1] $dmasmtool DCR_INI=/dm7/data/dmdcr.iniDMASMTOOL V7.1.6.46-Build (2018.02.08-89107) ENTASM > create diskgroup 'DMLOG' asmdisk' / dev/raw/raw3'Used time: 00:00:06.363.ASM > create diskgroup 'DMDATA' asmdisk' / dev/raw/raw4'Used time: 06.504.

12. Prepare the dminit.ini configuration file

Create a dminit.ini configuration file in the / dm/dmdbms/data directory of the 2 nodes and add the following. Created on both nodes.

[dmdba@dmrac1 data] $vi dminit.inidb_name = racsystem_path = + DMDATA/datasystem = + DMDATA/data/rac/system.dbfsystem_size = 128roll = + DMDATA/data/rac/roll.dbfroll_size = 128main = + DMDATA/data/rac/main.dbfmain_size = 128ctl_path = + DMDATA/data/rac/dm.ctlctl_size = 8log_size = 256dcr_path = / dev/raw/raw1 # dcr disk path, asm is not supported Only bare devices dcr_seqno = 0auto_overwrite = 1 [RAC0] # inst_name and DCR_EP_NAME in DB type group in dmdcr_cfg.ini correspond to config_path = / dm7/data/rac0_configport_num = 5236mal_host = 10.10.10.161mal_port = 9340log_path = + DMLOG/log/rac0_log01.loglog_path = + DMLOG/log/rac0_ log02.log [RAC1] # inst_name and DCR_EP_ in DB type group in dmdcr_cfg.ini NAME corresponds to config_path = / dm7/data/rac1_configport_num = 5236mal_host = 10.10.10.162mal_port = 9341log_path = + DMLOG/log/rac1_log01.loglog_path = + DMLOG/log/rac1_ log02.log [dmdba @ dmrac2 data] $vi dminit.inidb_name = racsystem_path = + DMDATA/datasystem = + DMDATA/data/rac/system.dbfsystem_size = 128roll = + DMDATA/data/rac/roll.dbfroll_size = 128main = + DMDATA/data/rac/main.dbfmain_size = 128ctl _ path = + DMDATA/data/rac/dm.ctlctl_size = 8log_size = 256dcr_path = / dev/raw/raw1 # dcr disk path Asm is not currently supported Only bare devices dcr_seqno = 0auto_overwrite = 1 [RAC0] # inst_name and DCR_EP_NAME in DB type group in dmdcr_cfg.ini correspond to config_path = / dm7/data/rac0_configport_num = 5236mal_host = 10.10.10.161mal_port = 9340log_path = + DMLOG/log/rac0_log01.loglog_path = + DMLOG/log/rac0_ log02.log [RAC1] # inst_name and DCR_EP_ in DB type group in dmdcr_cfg.ini NAME corresponds to config_path = / dm7/data/rac1_configport_num = 5236mal_host = 10.10.10.162mal_port = 9341log_path = + DMLOG/log/rac1_log01.loglog_path = + DMLOG/log/rac1_log02.log

Use dminit to initialize the database

Start the dminit tool at any node to initialize the database. After the dminit execution is complete, the configuration files dm.ini and dmmal.ini are generated in the config_path directory (/ dm7/data/rac0_config and / dm7/data/rac1_config).

[dmdba@dmrac1 data] $dminit control=/dm7/data/dminit.iniinitdb V7.1.6.46-Build (2018.02.08-89107) ENTdb version: 0x7000afile dm.key not found, use default license will expire on 2020-05-08log file path: + DMLOG/log/rac0_log01.loglog file path: + DMLOG/log/rac0_log02.loglog file path: + DMLOG/log/rac1_log01.loglog file path: + DMLOG/log/rac1_log02.logwrite to dir [+ DMDATA/data/rac] .create dm database success. 2020-04-24 16:39:03

Copy the configuration file for Node 1 to Node 2:

[dmdba@dmrac1 data] $scp-r rac1_config 10.18.13.162: `pwd`the authenticity of host '10.18.13.162 (10.18.13.162)' can't be established.RSA key fingerprint is 89:fc:3e:e3:2d:27:94:07:0e:6b:fc:c5:e8:89:44:1f.Are you sure you want to continue connecting (yes/no)? YesWarning: Permanently added '10.18.13.162' (RSA) to the list of known hosts.dmdba@10.18.13.162's password:sqllog.ini 100% 479 0.5KB/s 00:00dm.ini 100% 40KB 39.8KB/s 00:00dmmal.ini 100% 204 0.2KB/s 00:00 [dmdba@dmrac1 data] $

XIV. Start the database server

1. Register the DM database service on two nodes:

Node one:

[root@dmrac1 init.d] # / dm7/script/root/dm_service_installer.sh-t dmserver-I / dm7/data/rac0_config/dm.ini-d / dm7/data/dmdcr.ini-p rac1Move the service script file (/ dm7/bin/DmServicerac1 to / etc/rc.d/init.d/DmServicerac1) Finished to create the service (DmServicerac1)

Node 2:

[root@dmrac2] # / dm7/script/root/dm_service_installer.sh-t dmserver-I / dm7/data/rac1_config/dm.ini-d / dm7/data/dmdcr.ini-p rac2Move the service script file (/ dm7/bin/DmServicerac2 to / etc/rc.d/init.d/DmServicerac2) Finished to create the service (DmServicerac2)

2. Start the database

[root@dmrac1 init.d] # service DmServicerac1 startStarting DmServicerac1: [OK] [root@dmrac2 ~] # service DmServicerac2 startStarting DmServicerac2: [OK]

The manual startup command is as follows, and the window cannot be closed after manual startup, so

. / dmserver / dm7/data/rac0_config/dm.ini dcr_ini=/dm7/data/dmdcr.ini./dmserver / dm7/data/rac1_config/dm.ini dcr_ini=/dm7/data/dmdcr.ini

15 connection database verification

15.1 configure the service name file

[dmdba@dmrac1] $vi / etc/dm_svc.confTIME_ZONE= (480) rac= (10.18.13.161) SWITCH_TIME= (10000) SWITCH_INTERVAL= (10) TIME_ZONE= (480) LANGUAGE= (en) $vi / etc/dm_svc.confTIME_ZONE= (480) rac= (10.18.13.161) SWITCH_TIME= (10000) SWITCH_INTERVAL= (10) TIME_ZONE= (480) LANGUAGE= (en)

15.2 connect to RAC cluster

Node one:

[dmdba@dmrac1 ~] $disql SYSDBA/SYSDBA@rac

Server [10.18.13.161:5236]: mode is normal, state is open

Login used time: 10.365 (ms)

Disql V7.1.6.46-Build (2018.02.08-89107) ENT

Connected to: DM 7.1.6.46

SQL > select instance_name from v$instance

LINEID INSTANCE_NAME

--

1 RAC0

Used time: 18.248 (ms). Execute id is 807.

SQL > select * from v$rac_ep_info

LINEID EP_NAME EP_SEQNO EP_GUID EP_TIMESTAMP EP_MODE EP_STATUS

1 RAC0 0 2067076818 2067077298 MASTER OK

2 RAC1 1 2067098084 2067098537 SLAVE OK

Used time: 2.741 (ms). Execute id is 808.

Node 2:

[dmdba@dmrac2] $disql SYSDBA/SYSDBA@racServer [10.18.13.162 ms]: mode is normal, state is openlogin used time: 16.835 (ms) disql V7.1.6.46-Build (2018.02.08-89107) ENTConnected to: DM 7.1.6.46SQL > select instance_name from vastness instance INSTANCE_NAME--1 RAC1used time: 106.703 (ms). Execute id is 1.SQL > select * from v$rac_ep_info LINEID EP_NAME EP_SEQNO EP_GUID EP_TIMESTAMP EP_MODE EP_STATUS--1 RAC0 0 2067076818 2067077305 MASTER OK2 RAC1 1 2067098084 2067098544 SLAVE OKused time: 7.358 (ms). Execute id is 2. After reading this article, I believe you have a certain understanding of "how DM7 uses DMASM to install DMRAC". If you want to know more about it, you are welcome to follow the industry information channel. Thank you for reading!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.