Software Installation

Log in to the device where MEF Center is to be installed as the root user.
Upload the obtained software package to any directory on the device. It is recommended that the permission on this directory be root and other users have no write permission on this directory.

Decompress the software package.

Run the following command to decompress the software package:

unzip Ascend-mindxedge-mefcenter_{version}_linux-{arch}.zip

**Table 1** Decompressed files
File	Description
Ascend-mindxedge-mefcenter_{version}_linux-{arch}.tar.gz	Installation package
Ascend-mindxedge-mefcenter_{version}_linux-{arch}.tar.gz.cms	CMS signature file
Ascend-mindxedge-mefcenter_{version}_linux-{arch}.tar.gz.crl	CRL

Replace Ascend-mindxedge-mefcenter_{version}_linux-{arch}.zip with the actual package name. The CMS file and CRL are used to verify the inner signature of the software package.

Run the following command to decompress the tar.gz package again:

tar -zxvf Ascend-mindxedge-mefcenter_{version}_linux-{arch}.tar.gz

**Table 2** Directories after decompression
Directory	Description
installer/	MEF Center installation module
cert-manager/	Certificate management module
edge-manager/	Container management module
nginx-manager/	Gateway management module
alarm-manager/	Alarm management module

Install MEF Center.

Switch to the installation directory.

cd Software_package_upload_path/installer

Run the following command to install MEF Center:

./install.sh

The cert-manager, nginx-manager, edge-manager, and alarm-manager modules are automatically installed during MEF Center installation. For details about other parameters, see Table 3.

**Table 3** install.sh description
Parameter	Mandatory/Optional	Description
install_path	Optional	MEF Center installation path. If this parameter is not specified, the default installation path /usr/local is used. An absolute path is required if the installation path needs to be specified.
log_path	Optional	MEF Center log installation path. If this parameter is not specified, the default installation path /var is used. An absolute path is required if the installation path needs to be specified. You are advised to reserve 5.3 GB drive space for this directory.
log_backup_path	Optional	MEF Center log dump path. If this parameter is not specified, the default installation path /var is used. An absolute path is required if the installation path needs to be specified. You are advised to reserve 5.3 GB drive space for this directory.

Parameter formats supported by install.sh (-install_path is used as an example):

./install.sh -install_path: If this parameter is not specified, the default installation path /usr/local is used.
./install.sh -install_path=/usr/local or ./install.sh --install_path=/usr/local
./install.sh -install_path /usr/local or ./install.sh --install_path /usr/local

The preceding command formats can run properly. If the parameter of install.sh does not contain a hyphen (-), for example, ./install.sh h, the parameter is ignored and the command execution continues.

The installation path, log path, and log dump path cannot be located in a temporary file system and cannot contain soft links. The path length must be less than 4096, and the number of directory levels must be less than 99. The owner must be root, and users in the same group and other users do not have the write permission.

--version: queries the software version.
--h/help: prints help information.

The installation is successful if the following information is displayed:
```
install MEF center success
```
After the installation, the software is deployed in Installation path/MEF-Center, logs are stored in Log path/mef-center-log, and dump logs are stored in Log dump path/mef-center-log-backup. For details about the log paths, see Viewing Log Information.

Changing the system time may cause loss of dump logs.

Start MEF Center.

Go to the path where MEF Center is located.

cd Installation_path/MEF-Center/mef-center

Run the following command to start all MEF Center modules:
```
./run.sh start
```

If the following information is displayed, the operation is successful:

start all component successful

The run.sh command requires the root permission. Table 4 lists some sub-commands of run.sh.

**Table 4** run.sh description
Command	Sub-command	Description
start	start parameters	Starts MEF Center.
restart	restart parameters	Restarts MEF Center.
stop	stop parameters	Stops MEF Center.
upgrade	upgrade parameters	Upgrades MEF Center.
uninstall	None	Uninstalls MEF Center.
exchangeca	exchangeca parameters	Exchanges the root certificate with MEF Center.
importcrl	importcrl parameters	Imports the CRL of a third-party management platform.
updatekmc	None	Updates the KMC encryption key.
alarmconfig	alarmconfig parameters	Configures alarms. For details, see Configuring and Querying the MEF Center Certificate Expiration Alarm.
getalarmconfig	None	Obtains alarm configurations. For details, see Configuring and Querying the MEF Center Certificate Expiration Alarm.
getunusedcert	getunusedcert parameters	Queries the information about the backup root certificate imported to MEF Center.
deletecert	deletecert parameters	Deletes the backup root certificate imported to MEF Center.
restorecert	restorecert parameters	Restores the root certificate imported to MEF Center.
-h/--h/-help/--help	None	Prints help information.
-version/--version	None	Prints the binary version.

Follow-up Procedure

If the following information is displayed, the module (for example, edge-manager) fails to be started. In this case, restart the module. For details, see Restarting MEF Center.

start component edge-manager failed

Parent topic: Installing and Deploying MEF Center