H3C SNA Center Operation Log Messages Reference-E11xx-5W103

HomeSupportResource CenterSDNH3C SNA CenterH3C SNA CenterTechnical DocumentsMaintainMessage ReferencesH3C SNA Center Operation Log Messages Reference-E11xx-5W103
Download Book

 

H3C SNA Center

Operation Log Messages Reference

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Document version: 5W103-20191210

 

Copyright © 2019 New H3C Technologies Co., Ltd. All rights reserved.

No part of this manual may be reproduced or transmitted in any form or by any means without prior written consent of New H3C Technologies Co., Ltd.

Except for the trademarks of New H3C Technologies Co., Ltd., any trademarks that may be mentioned in this document are the property of their respective owners.

The information in this document is subject to change without notice.


Contents

Introduction· 2

Viewing operation log messages· 2

Syslog message format 3

Using this document 5

BACKUP_RESTORE·· 7

Execute backup· 7

Restore from uploaded file· 7

Restore from history file· 8

Upload file for restoration· 8

Update backup configuration· 9

Download backup file· 9

IAM_AUTH·· 10

Login· 10

Logout 10

RBAC· 10

IAM_AUTH_FREE_IP·· 11

Add auth-free IP· 11

Delete auth-free IP· 11

IAM_USER·· 12

Add a user 12

Update user configuration· 12

Delete a user 13

LICENSE·· 14

Connect to the license server 14

Disconnect from the license server 14

Update the quantity of requested licenses· 15

LOG_DIAG·· 16

Update diagnosis log configuration· 16

LOG_OPERLOG·· 17

Delete an operation log· 17

Update operation log configuration· 17

LOG_RBAC·· 19

RBAC· 19

LOG_SYSLOG·· 20

Delete a system log· 20

Update system log configuration· 21

SNACenter 22

Update user monitor 22

Update full screen title· 23

Update homepage customization· 24

Upload package· 24

Delete package· 24

Create network· 25

Delete network· 25

Create subnet 26

Modify subnet 27

Delete subnet 27

Bind host uplink interface· 28

Unbind host uplink interface· 28

Install component 29

Reinstall component 30

Uninstall component 31

Re-uninstall component 31

Update component 32

Rollback component 33

Stop installing component 34

Create third-party system·· 35

Update third-party system·· 36

Scale out component 37

Re-scale out component 38

Cancel a failed component scale-out operation· 39

Uninstall scaled-out component instance· 40

SNAInstaller 41

Add node· 42

Update node· 44

Upload RPM·· 45

Repair node· 46

Upgrade node· 47

Delete node· 48

Deploy cluster 49

Update system config· 50

Add network· 52

Update network· 54

Delete network· 55

Upload app package· 55

Install app package· 56

Uninstall app· 59

Delete app package· 60

Change password· 60

Introduction

Operation logs record system operations and configuration modifications, such as application operations (installing, uninstalling, and deleting an application) and user configurations. Operation log messages include operation time, description, result, and failure reasons, and provide reference for system analysis and maintenance.

This document assumes that the readers are familiar with data communications technologies and H3C SNA Center products.

Viewing operation log messages

1.     Log in to SNA Center.

2.     Click Settings in the System area.

3.     On the top navigation bar, click Logs.

4.     From the left navigation pane, select Information.

5.     Click the Operation Logs tab.

The operation log message list is displayed, as shown in Figure 1.

Figure 1 Operation log message list

 

Table 1 Operation log element

Element

Description

Time

Date and time when the log was generated.

SNA Component Name

Name of the SNA component that generated the log.

Username

Name of the user that triggered the log generation.

User IP

IP address of the terminal where the user performed the operation.

Host Name

Name of the host that generated the log.

Service Name

Name of the service that produced the log.

Module Name

Name of the service module to which the user operation belongs.

Operation Result

Operation result: Succeeded or Failed.

Operation Description

Description of the user operation.

Failure Reason

Possible reasons for an operation failure.

 

Syslog message format

SNA Center can send operation logs to syslog servers through the syslog protocol. To configure operation log output to syslog servers, go to the Logs > Configuration > Operation Logs page.

By default, SNA Center sends operation logs to syslog servers in the following format:

<PRI>TIMESTAMP Hostname Origin/severity/Keywords CONTENT

Table 2 Syslog message elements

Element

Description

<PRI>

Priority identifier. It is calculated by using the following formula:

Priority identifier=facilityx8+severity

Where:

·     Facility represents the programming module defined by syslog. In the current software version, the facility is user-level and its value is 1.

·     Severity represents the syslog message severity level. For more information, see Table 4.

TIMESTAMP

Date and time when the event occurred.

Hostname

Name or IP address of the host that produced the message.

Origin

Name of the service module that produced the message.

severity

Severity level of the message. For more information, see Table 5. For more information about the mappings between operation log message severity levels and syslog message severity levels, see Table 6.

Keywords

Keywords of the message that facilitate searching or memorizing.

CONTENT

Text string that contains detailed information about the operation, in the following format:

-Module="module name"-UserIp=" user IP"-UserName="username"-OperResult="result"-Reason="operation failure causes"

 

Table 3 lists the log source modules supported by SNA Center.

Table 3 Service module list

Service module name

Description

BACKUP_RESTORE

Backup and restoration module.

IAM_AUTH

IAM authentication module.

IAM_AUTH_FREE_IP

IAM authentication-free module.

IAM_USER

IAM user management module.

LICENSE

License module.

LOG_DIAGLOG

Diagnostic log management module.

LOG_OPERLOG

Operation log management module.

LOG_RBAC

Log privilege control module.

LOG_SYSLOG

Syslog management module.

SNACenter

SNA Center basic service module.

SNAInstaller

SNA Installer module.

 

Syslog messages are classified into eight severity levels from 0 to 7. The lower the number, the higher the severity, as shown in Table 4.

Table 4 Syslog message severity levels

Level

Severity

Description

0

Emergency

The system is unusable.

1

Alert

Action must be taken immediately.

2

Critical

Critical condition.

3

Error

Error condition.

4

Warning

Warning condition.

5

Notice

Normal but significant condition.

6

Informational

Informational message.

7

Debug

Debugging message.

 

Operation log messages are classified into two severity levels, as shown in Table 5.

Table 5 Operation log message severity levels

Level

Severity

Description

0

Info

Information message. It indicates that the operation succeeded.

1

Warning

Warning condition. It indicates that the operation failed.

 

Table 6 shows the mappings between operation log message severity levels and syslog message severity levels.

Table 6 Severity level mappings

Operation log severity level

Syslog severity level

0

6

1

4

 

Using this document

This document categories operation logs by service module. This document explains messages in tables. Table 7 describes information provided in these tables.

Table 7 Message explanation table contents

Item

Content

Example

Keyword

Summary of the message that facilitates searching or memorizing.

IAM_OPT_ADD_USER

Message text

Presents the message description.

Added user “$1”.

Variable fields

Briefly describes the variable fields in the order that they appear in the message text.

The variable fields are numbered in the "$Number" form to help you identify their location in the message text.

$1: Username.

Example

Provides a real message example.

Added user “admin”.

Explanation

Explains the message.

A user was added.

Possible failure causes

Provides possible causes of an operation failure.

·     A username is required.

·     A password is required.

·     A user role is required.

·     Invalid JSON format.

·     Internal error.

·     The user already exists.

·     Invalid password.

·     Invalid description.

 


BACKUP_RESTORE

This section contains operation log messages generated by the Backup & Restore module of SNA Center.

Execute backup

Keyword

EXECUTE_BACKUP_OP

Message text

Executed backup for backupFile: $1.

Variable fields

$1: Backup file name.

Example

Executed backup for backupFile: SNACenter_E1103_20190828084133_M.zip.

Explanation

The configurations of the selected components were backed up and saved to the file with the specified name.

Possible failure causes

·     The system service does not respond.

 

Restore from uploaded file

Keyword

RESTORE_FROM_UPLOAD_FILE_OP

Message text

Restored the configuration in uploaded file: $1.

Variable fields

$1: File name.

Example

Restored the configuration in uploaded file: SNACenter_E1103_20190828084133_M.zip.

Explanation

The configuration in the file uploaded to SNA Center was restored.

Possible failure causes

·     File content error.

·     The product does not exist.

·     A configuration backup or restoration operation is in progress.

·     The file does not exist.

·     The system service does not respond.

 

Restore from history file

Keyword

RESTORE_FROM_HISTORY_FILE_OP

Message text

Restored configuration in history file: $1.

Variable fields

$1: Backup file name.

Example

Restored configuration in history file: SNACenter_E1103_20190828084133_M.zip.

Explanation

The configuration in the backup file on the History File list was restored.

Possible failure causes

·     Invalid file format.

·     The product does not exist.

·     A configuration backup or restoration operation is in progress.

·     File transfer failed.

·     File content error.

·     The system service does not respond.

 

Upload file for restoration

Keyword

UPLOAD_RESTORE_FILE_OP

Message text

Uploaded file for configuration restoration: $1

Variable fields

$1: File name.

Example

Uploaded file for configuration restoration: SNACenter_E1103_20190828084133_M.zip.

Explanation

A file for configuration restoration was uploaded to SNA Center.

Possible failure causes

·     File content error.

·     File transfer failed.

 

Update backup configuration

Keyword

UPDATE_BACKUP_PARAM_OP

Message text

Updated backup configuration parameters: $1

Variable fields

$1: Backup parameter settings.

Example

Updated backup configuration parameters:

{

    "backup_config": {

        "backup_path": "/opt/matrix/app/data/base-service/backupRecovery/historyFiles",

        "date": "",

        "frequency": "PER_WEEK",

        "prefix": "FWF11",

        "remote_ip": "190.16.66.36",

        "remote_user": "sdn",

        "reservation": 20,

        "status": "open",

        "time": "9:0",

        "week": "Thursday"

    }

}

Explanation

The backup parameter settings were updated.

Possible failure causes

·     Invalid configuration parameters.

·     The system service does not respond.

 

Download backup file

Keyword

DOWNLOAD_BACKUPFILE_OP

Message text

Downloaded backup file: $1

Variable fields

$1: Backup file name.

Example

Downloaded backup file: SNACenter_E1103_20190828084133_M.zip.

Explanation

A backup file on the History File list was downloaded to the local host.

Possible failure causes

·     The backup file doesn't exist.

·     The system service does not respond.

 


IAM_AUTH

This section contains operation log messages generated by the IAM authentication module.

Login

Keyword

IAM_OPT_USER_LOGIN

Message text

A user logged in: username=“$1”, user role=“$2”.

Variable fields

$1: Username.

$2: User role.

Example

A user logged in: username=“test”, user role=“admin”.

Explanation

A user logged in.

Possible failure causes

·     Invalid JSON format.

·     Wrong password or username.

·     The system service does not respond.

 

Logout

Keyword

IAM_OPT_USER_LOGOUT

Message text

A user logged out: username=“$1”, user role=“$2”.

Variable fields

$1: Username.

$2: User role.

Example

A user logged out: username=“test”, user role=“admin”.

Explanation

A user logged out.

Possible failure causes

The system service does not respond.

 

RBAC

Keyword

IAM_OPT_IAM_RBAC_FAILED

Message text

The operation of user “$1” with role “$2” failed.

Variable fields

$1: Username.

$2: User role.

Example

A user logged out: username=“test”, user role=“admin”.

Explanation

A user failed to perform an operation because of lack of permissions.

Possible failure causes

The user role doesn't provide the permission to perform the operation.

 

 


IAM_AUTH_FREE_IP

This section contains operation log messages generated by the IAM authentication-free IP module.

Add auth-free IP

Keyword

IAM_OPT_ADD_FREE_AUTH

Message text

Added auth-free IP “$1”.

Variable fields

$1: IP address.

Example

Added auth-free IP “192.168.109.1”.

Explanation

An authentication-free IP address was added.

Possible failure causes

·     The IP address is required.

·     The role is required.

·     Invalid IP address.

·     The system service does not respond.

·     The configuration already exists.

 

Delete auth-free IP

Keyword

IAM_OPT_DELETE_FREE_AUTH

Message text

Deleted auth-free IP “$1”.

Variable fields

$1: IP address.

Example

Deleted auth-free IP “192.168.109.1”.

Explanation

An authentication-free IP address was deleted.

Possible failure causes

The system service does not respond.

 

 


IAM_USER

This section contains operation log messages generated by the IAM user management module.

Add a user

Keyword

IAM_OPT_ADD_USER

Message text

Added user “$1”.

Variable fields

$1: Username.

Example

Added user “admin”.

Explanation

A user was added.

Possible failure causes

·     A username is required.

·     A password is required.

·     A user role is required.

·     Invalid JSON format.

·     The system service does not respond.

·     The user already exists.

·     Invalid username.

·     Invalid password.

·     Invalid description.

 

Update user configuration

Keyword

IAM_OPT_UPDATE_USER

Message text

Updated settings for user $1.

Variable fields

$1: Username.

Example

Updated settings for user “admin”.

Explanation

The settings of a user were updated.

Possible failure causes

·     A username is required.

·     The user role is unchangeable.

·     Invalid JSON format.

·     The system service does not respond.

·     The user role doesn't provide the permission to perform the operation.

·     The resource doesn't exist.

·     Wrong password.

·     The description for the default administrator cannot be modified.

 

Delete a user

Keyword

IAM_OPT_DELETE_USER

Message text

Deleted user “$1”.

Variable fields

$1: Username.

Example

Deleted user “admin”.

Explanation

A user was deleted.

Possible failure causes

·     A user can't delete his or her own account.

·     The system service does not respond.

·     The default administrator cannot be deleted.

 


LICENSE

This section contains license management messages.

Connect to the license server

Keyword

CONNECT_LICS_OP

Message text

Connected to the license server: $1

Variable fields

$1: License server information.

Example

Connected to the license server:{

“username”: “sdn”

 “password”: “******”,

“ip”: “192.168.40.40”,

“port”: “5555”,

}

Explanation

The controller initiated a connection to the specified license server.

Possible failure causes

·     Invalid JSON format.

·     Invalid server IP.

·     Invalid port.

·     The connection is already exist.

·     The system is recovering.

·     Failed to connect to the license server.

·     Incorrect username or password.

·     The connection has been established.

·     Internal error.

·     The user role doesn't provide the permission to perform the operation.

·     Members can't execute this operation.

 

Disconnect from the license server

Keyword

DISCONNECT_LICS_OP

Message text

Disconnected from the license server: $1.

Variable fields

$1: License server IP address.

Example

Disconnected from the license server: 192.168.1.1.

Explanation

This message is sent when the controller is disconnected from the specified license server.

Possible failure causes

·     The system is recovering.

·     Internal error.

·     The user role doesn't provide the permission to perform the operation.

·     Members can't execute this operation.

 

Update the quantity of requested licenses

Keyword

UPDATE_REQUESTED_LICENSES_OP

Message text

Updated the quantity of requested licenses: $1

Variable fields

$1: Number of requested licenses.

Example

Updated the quantity of requested licenses: [

{

APP license: all

MaxNodeNum license: all

SET_VNFM_STD license: true

VirtualServiceNode licnese: all

Unlimited license: true

API license: true

OverlayHardwareEntity licnese: all

ServiceChain License: true

Base license: all

}

]

Explanation

This message is sent when a user changes the quantity of requested licenses.

Possible failure causes

·     Invalid JSON format.

·     The feature name does not exist.

·     The system is recovering.

·     The count is out of range.

·     Internal error.

·     The user role doesn't provide the permission to perform the operation.

·     Members can't execute this operation.

 


LOG_DIAG

This section contains operation log messages generated by the diagnostic module.

Update diagnosis log configuration

Keyword

UPDATE_LOG_DIAGLOG_CONFIG_OP

Message text

Updated diagnosis log configuration: $1.

Variable fields

$1: Diagnosis log configuration information.

Example

Updated diagnosis log configuration:

{

"diaglog-configs" :

{

"space" : 500,

"percent" : 57

}

}

Explanation

The diagnosis log configuration was modified.

Possible failure causes

·     Invalid parameter.

·     Invalid JSON format.

·     Invalid percentage of reserved messages at purge.

·     Invalid diag disk space.

·     Internal error.

·     The system service does not respond.

 


LOG_OPERLOG

This section contains operation log messages generated by the operation log management module.

Delete an operation log

Keyword

DELETE_LOG_OPERLOG_OP

Message text

Deleted $1 operation logs.

Variable fields

$1: Name of an SNA module or all.

Example

Deleted all operation logs.

Deleted log-center operation logs.

Explanation

Operation logs were deleted.

Possible failure causes

Internal error.

 

Update operation log configuration

Keyword

UPDATE_LOG_OPERLOG_CONFIG_OP

Message text

Updated operation log configuration: $1.

Variable fields

$1: Operation log configuration information.

Example

Updated operation log configuration:

{

"operlog-configs" :

{

"duration" : 365,

"purge_clock" : "12:00",

"syslog_server1_ip" : "100.3.1.82",

"syslog_server1_port" : 514,

"syslog_server2_ip" : "100.3.1.81",

"syslog_server2_port" : 514,

"syslog_severity" : "INFO"

}

}

Explanation

The operation log configuration was modified.

Possible failure causes

·     Invalid parameter.

·     Invalid JSON format.

·     Invalid storage duration.

·     Invalid expired log purge time.

·     Invalid IP address of log server 1.

·     Invalid port number of log server 1.

·     Invalid IP address of log server 2.

·     Invalid port number of log server 2.

·     Invalid parameter syslog_severity.

·     Internal error.

 


LOG_RBAC

This section contains operation logs generated by the LOG_RBAC module.

RBAC

Keyword

LOG_RBAC_FAILED

Message text

The operation of user $1 with role $2 failed.

Variable fields

$1: Username.

$2: User role.

Example

The operation of user test1 with role observer failed.

Explanation

A user failed to perform an operation because the user role doesn't provide the permission to perform that operation.

Possible failure causes

The user role doesn't provide the permission to perform the operation.

 


LOG_SYSLOG

This section contains operation log messages generated by the system log management module.

Delete a system log

Keyword

DELETE_LOG_SYSLOG_OP

Message text

Deleted $1 system logs.

Variable fields

$1: Name of an SNA module or all.

Example

Deleted log-center system logs.

Deleted all system logs.

Explanation

System logs were deleted.

Possible failure causes

·     Internal error.

·     Invalid parameter appname.

 

Update system log configuration

Keyword

UPDATE_LOG_SYSLOG_CONFIG_OP

Message text

Updated system log configuration: $1.

Variable fields

$1: System log configuration information.

Example

Updated system log configuration:

{

"syslog-configs" :

{

"duration" : 5,

"purge_clock" : "12:00",

"syslog_server1_ip" : "100.3.1.82",

"syslog_server1_port" : 514,

"syslog_server2_ip" : "100.3.1.82",

"syslog_server2_port" : 514,

"syslog_severity" : "WARN"

}

 }

Explanation

The system log configuration was modified.

Possible failure causes

·     Invalid parameter

·     Invalid JSON format.

·     Invalid storage duration.

·     Invalid expired log purge time.

·     Invalid IP address of log server 1.

·     Invalid port number of log server 1.

·     Invalid IP address of log server 2.

·     Invalid port number of log server 2.

·     Invalid parameter syslog_severity.

·     Internal error.

·     The system service does not respond.

 


SNACenter

This section contains operation log messages produced by SNA Center.

Update user monitor

Keyword

UPDATE_USER_MONITOR_OP

Message text

Updated user monitor: $1.

Variable fields

$1: User monitor name.

Example

Updated user monitor:

{

    "userMonitors": [

         "Access method",

         "Terminal information"

    ]

}

Explanation

A user's monitor configuration profile was updated.

Possible failure causes

·     Invalid JSON format.

·     Monitor information can't be configured for the scene.

·     The system service does not respond.

·     Parameter is empty.

 

Update full screen title

Keyword

UPDATE_title_OP

Message text

Updated fullscreen title: $1.

Variable fields

$1: Full screen title.

Example

Updated fullscreen title:

{

"titleInstance":{

"title":"Campus network overview",

"fontSize":"30",

"color":"#ffffff"

}

}

Explanation

The full screen title was modified.

Possible failure causes

·     Invalid JSON format.

·     The system service does not respond.

·     Parameter is empty.

·     Full screen title is empty.

·     The font size of title is empty.

·     The font color of title is empty.

·     Invalid full screen title.

·     Invalid font size.

·     Invalid font color.

 

Update homepage customization

Keyword

UPDATE_HOMEPAGE_OP

Message text

Updated homepage customization: $1.

Variable fields

$1: Homepage customization information.

Example

Updated homepage customization:

{

"homepageInstance":{

"scene":"DC",

"url":""

}

}

Explanation

The homepage was customized.

Possible failure causes

·     Invalid JSON format.

·     The system service does not respond.

·     The request message body is empty.

·     The scene name is incorrect.

·     The scene name is empty.

 

Upload package

Keyword

UPLOAD_PACKAGE_OP

Message text

Uploaded package: $1

Variable fields

$1: Installation package name.

Example

Uploaded package: campus.rar

Explanation

A component installation package was uploaded to SNA Center.

Possible failure causes

·     The request parameter cannot be null.

·     Failed to call the internal interface.

 

Delete package

Keyword

DELETE_PACKAGE_OP

Message text

Deleted package: $1

Variable fields

$1: Comma-separated list of installation package names.

Example

Deleted package: supercontroller-v1.zip, bigdata-v1.zip

Explanation

One or more installation packages were deleted.

Possible failure causes

Failed to call the internal interface.

 

Create network

Keyword

CREATE_NETWORK_OP

Message text

Created network “$1”.

Variable fields

$1: Network name.

Example

Created network “network1”.

Explanation

A network was created.

Possible failure causes

·     The parameter cannot be null.

·     The network name cannot be null.

·     Invalid network name.

·     The network name already exists.

·     Cannot create or modify the network because it already exists on SNA Installer.

·     The VLAN ID must in the range of 0 to 4094.

·     Data format error.

·     The VLAN conflicts with the configuration on SNA Installer.

·     Failed to obtain the network on SNA Installer.

·     Failed to create the network on SNA Installer.

·     Internal error.

 

Delete network

Keyword

DELETE_NETWORK_OP

Message text

Deleted network: “$1”.

Variable fields

$1: Network name.

Example

Deleted network: “network1”.

Explanation

A network was deleted.

Possible failure causes

·     The network name cannot be null.

·     Invalid network name.

·     The network cannot be deleted because it has been deployed.

·     The network does not exist.

·     Database operation failed.

·     Failed to obtain the network on SNA Installer.

·     Failed to delete the network from SNA Installer.

 

Create subnet

Keyword

CREATE_SUBNET_OP

Message text

Created subnet: “$1”.

Variable fields

$1: Subnet name.

Example

Created subnet: “subnet1”.

Explanation

A subnet was created.

Possible failure causes

·     Invalid parameters.

·     The request body cannot be empty.

·     Invalid network name.

·     Invalid subnet name.

·     Invalid subnet CIDR format.

·     Invalid CIDR host bytes.

·     Invalid start IP address of the address pool.

·     Invalid end IP address of the address pool.

·     The start IP address of the address pool is not in the subnet CIDR.

·     The end IP address of the address pool is not in the subnet CIDR.

·     The start IP address of the address pool must be lower than the end IP address.

·     The start IP address of the address pool cannot be the same as the subnet CIDR.

·     The host portion of an IP address in binary form cannot be all ones.

·     The number of IP addresses cannot be smaller than 32 in the subnet IP address pool.

·     Invalid gateway IP address.

·     The gateway IP address is not in the subnet CIDR.

·     The specified network does not exist.

·     The subnet name already exists.

·     The specified subnet already exists.

·     Fail to add the subnet.

 

Modify subnet

Keyword

MODIFY_SUBNET_OP

Message text

Modified subnet: “$1”.

Variable fields

$1: Subnet name.

Example

Modified subnet: “subnet1”.

Explanation

The settings of a subnet were modified.

Possible failure causes

·     The parameter cannot be null.

·     The request body cannot be empty.

·     Invalid network name.

·     Invalid subnet name.

·     Invalid subnet format.

·     The binary host bits of the subnet must be all zero.

·     The specified subnet already exists.

·     Invalid start IP address of the address pool.

·     Invalid end IP address of the address pool.

·     The specified network does not exist.

·     The specified subnet does not exist.

·     The start IP address of the address pool is not in the subnet.

·     The end IP address of the address pool is not in the subnet.

·     The start IP address of the address pool must be lower than the end IP address.

·     The host portion of an IP address in binary form cannot be all ones

·     The number of IP addresses cannot be smaller than 32 in the subnet IP address pool.

·     Invalid gateway IP address.

·     The gateway IP address is not in the subnet CIDR.

·     The specified subnet has been used.

·     Failed to modify the subnet.

 

Delete subnet

Keyword

DELETE_SUBNET_OP

Message text

Deleted subnet: “$1”.

Variable fields

$1: Subnet name.

Example

Deleted subnet: “subnet1”.

Explanation

A subnet was deleted.

Possible failure causes

·     The parameter cannot be null.

·     Invalid network name.

·     Invalid subnet name.

·     The specified subnet does not exist.

·     The specified subnet has been used.

·     Internal error.

 

Bind host uplink interface

Keyword

BIND_HOST_IF_OP

Message text

Bound host uplink interface to network: $1

Variable fields

$1: Network name.

Example

Bound host uplink interface to network: network1

Explanation

A network was bound to the uplink interface of a host.

Possible failure causes

·     The parameter cannot be null.

·     The request body cannot be empty.

·     The host list cannot be empty.

·     The specified network does not exist.

·     Invalid parameters.

·     Only one uplink interface on the host can be bound.

·     The specified host has already been bound.

·     Cannot bind the same uplink interface of a host.

·     The physical NIC name cannot be null.

·     Networks with the same VLAN configured cannot be bound to the same uplink interface of a host.

·     Internal error.

 

Unbind host uplink interface

Keyword

DELETE_BIND_HOST_IF_OP

Message text

Unbound host uplink interface from network: $1

Variable fields

$1: Network name.

Example

Unbound host uplink interface from network: network1

Explanation

A network-to-host uplink interface binding was deleted.

Possible failure causes

·     The parameter cannot be null.

·     The request body cannot be empty.

·     The network name cannot be null.

·     Invalid network name.

·     The host list cannot be empty.

·     The network has been used by a component.

·     Internal error.

·     The VLAN conflicts with the configuration on SNA Installer.

·     Failed to modify the binding of the network on the SNA Installer.

 

Install component

Keyword

INSTALL_COMPONENT_OP

Message text

Installed component: $1

Variable fields

$1: Comma-separated list of component names.

Example

Installed component: CAMPUS,VDHCP

Explanation

One or more components were installed.

Possible failure causes

·     The parameter cannot be null.

·     There are installation tasks that are not completed.

·     There are uninstallation tasks that are not completed.

·     Request body format error.

·     Failed to get the token.

·     The configuration data sent is not the newest.

·     The request body cannot be empty.

·     The specified component does not exist.

·     The specified network does not exist.

·     Failed to obtain component configuration information.

·     The network name cannot be null.

·     The subnet name cannot be null.

·     Failed to execute the script.

·     Failed to obtain component configuration information from the configuration file.

·     Failed to obtain the deployment progress.

·     Failed to check whether SNA Installer is idle.

·     The SNA Installer is busy processing tasks.

·     The installation task for the component does not exist.

·     Failed to obtain the component version from the database.

·     Failed to obtain component installation packages.

·     Failed to obtain the component installation package name.

·     Configuration file format error.

·     Internal error.

·     Failed to parse the component.

·     Failed to obtain the installation progress.

 

Reinstall component

Keyword

REINSTALL_COMPONENT_OP

Message text

Reinstalled component: $1

Variable fields

$1: Component name.

Example

Reinstalled component: CAMPUS

Explanation

A component was reinstalled.

Possible failure causes

·     There are installation tasks that are not completed.

·     There are uninstallation tasks that are not completed.

·     The request body cannot be empty.

·     The component name cannot be null.

·     The installation task for the component does not exist.

·     The component does not need to be reinstalled.

·     Failed to obtain the component version from the database.

·     Failed to obtain component installation packages.

·     Failed to obtain the software package name.

·     Configuration file format error.

·     Failed to check whether SNA Installer is idle.

·     SNA Installer is busy processing tasks.

·     Failed to parse the component.

·     Internal error.

·     Failed to obtain the deployment progress.

·     Failed to obtain the installation progress.

 

Uninstall component

Keyword

UNINSTALL_COMPONENT_OP

Message text

Uninstalled component: $1

Variable fields

$1: Comma-separated list of component names.

Example

Uninstalled component: CAMPUS, VDHCP

Explanation

One or more components were uninstalled.

Possible failure causes

·     There are installation tasks that are not completed.

·     There are uninstallation tasks that are not completed.

·     The specified component does not exist.

·     The specified component cannot be uninstalled.

·     Configuration file format error.

·     Failed to check whether SNA Installer is idle.

·     Failed to obtain the deployment progress.

·     The SNA Installer is busy processing tasks.

·     The component name cannot be null.

·     The component uninstallation task does not exist.

·     Internal error.

·     Failed to uninstall the component.

·     Failed to obtain the uninstallation progress.

 

Re-uninstall component

Keyword

REUNINSTALL_COMPONENT_OP

Message text

Re-uninstalled component: $1

Variable fields

$1: Component name.

Example

Re-uninstalled component: CAMPUS

Explanation

A component was uninstalled again.

Possible failure causes

·     There are installation tasks that are not completed.

·     There are uninstallation tasks that are not completed.

·     The request body cannot be empty.

·     Failed to obtain the deployment progress.

·     Failed to check whether SNA Installer is idle.

·     The SNA Installer is busy processing tasks.

·     The component name cannot be null.

·     No components are available to be re-uninstalled.

·     The component does not need to be re-uninstalled.

·     Configuration file format error.

·     The component uninstallation task does not exist.

·     The matrixPdtName for the component cannot be null.

·     Failed to uninstall the component.

·     Failed to obtain the uninstallation progress.

·     Failed to re-uninstall the component.

 

Update component

Keyword

UPDATE_COMPONENT_OP

Message text

Updated component: $1

Variable fields

$1: Component name.

Example

Updated component: CAMPUS

Explanation

A component was upgraded.

Possible failure causes

·     There are installation tasks that are not completed.

·     There are uninstallation tasks that are not completed.

·     The parameter cannot be null.

·     Failed to obtain the list of all installed components.

·     The component is not installed.

·     Failed to update the component.

·     Failed to obtain the deployment progress.

·     Failed to check whether SNA Installer is idle.

·     The SNA Installer is busy processing tasks.

·     The specified network does not exist.

·     Failed to obtain component configuration information.

·     The network name cannot be null.

·     The subnet name cannot be null.

·     Failed to execute the script.

·     Failed to obtain component configuration information from the configuration file.

·     The installation task for the component does not exist.

·     Failed to obtain component installation packages.

·     Failed to obtain the software package name.

·     Configuration file format error.

·     Failed to parse the component.

·     Internal error.

·     Failed to obtain the installation progress.

 

Rollback component

Keyword

ROLLBACK_COMPONENT_OP

Message text

Rollbacked component: $1

Variable fields

$1: Component name.

Example

Rollbacked component: CAMPUS

Explanation

A component was rolled back to a previous version after an upgrade failure.

Possible failure causes

·     There are installation tasks that are not completed.

·     There are uninstallation tasks that are not completed.

·     The request body cannot be empty.

·     The component name cannot be null.

·     The installation task for the component does not exist.

·     The component does not need to be reinstalled.

·     Failed to obtain the component version from the database.

·     Failed to obtain component installation packages.

·     Failed to obtain the software package name.

·     Configuration file format error.

·     Failed to check whether SNA Installer is idle.

·     The SNA Installer is busy processing tasks.

·     Failed to parse the component.

·     Failed to rollback the component.

·     Failed to obtain the deployment progress.

·     Failed to obtain the installation progress.

·     Internal error.

 

Stop installing component

Keyword

STOP_INSTALL_COMPONENT_OP

Message text

Stopped installing component: $1

Variable fields

$1: Component name.

Example

Stopped installing component: CAMPUS

Explanation

The component installation process was stopped by the user.

Possible failure causes

·     There are installation tasks that are not completed.

·     There are uninstallation tasks that are not completed.

·     The request body cannot be empty.

·     The parameter cannot be null.

·     The terminateFlag value can only be install or uninstall.

·     Failed to check whether SNA Installer is idle.

·     The SNA Installer is busy processing tasks.

·     Failed to obtain the deployment progress.

·     The installation task for the component does not exist.

·     Fail to operate the database.

·     Failed to stop installation.

 

Create third-party system

Keyword

CREATE_THIRD_PARTY_SYSTEM_OP

Message text

Created third-party system: $1.

Variable fields

$1: Information about a third-party system.

Example

Created third-party system: thirdPartySystem={

    "thirdpartysystem": {

    "ip": "12.01.1.1",

    "port": "1024",

    "username": "admin",

    "password": "******",

    "type": "IMC"

    }

}

Explanation

A third-party system was added.

Possible failure causes

·     Parameters cant be empty.

·     Invalid IP address.

·     The port number is in the range of 1 to 65535.

·     Invalid username.

·     Invalid password.

·     Invalid JSON format.

·     The third-party system information already exists.

·     Invalid third-party system type.

·     Failed to add the third-party system configuration.

·     Failed to get the third-party system configuration.

·     Internal error.

·     The system service does not respond.

·     The user role doesn't provide the permission to perform the operation,

 

Update third-party system

Keyword

UPDATE_THIRD_PARTY_SYSTEM_OP

Message text

Updated third-party system: $1.

Variable fields

$1: Third-party system ID.

Example

Updated third-party system: id=ebedbc33-1043-4095-b4f5-46df1af1066c

thirdPartySystem={

    "thirdpartysystem": {

    "ip": "12.01.1.1",

    "port": "1024",

    "username": "admin",

    "password": "******",

    "type": "IMC"

    }

}

Explanation

The configuration of a third-party system was updated.

Possible failure causes

·     Parameters cant be empty.

·     Invalid IP address.

·     The port number is in the range of 1 to 65535.

·     Invalid username.

·     Invalid password.

·     Invalid JSON format.

·     The third-party system information already exists.

·     Invalid third-party system type.

·     The third-party system does not exist.

·     Failed to update the third-party system configuration.

·     Internal error.

·     The system service does not respond.

·     The user role doesn't provide the permission to perform the operation.

 

Scale out component

Keyword

SCALEOUT_COMPONENT_OP

Message text

Scaled out component: $1

Variable fields

$1: Component name.

Example

Scaled out component: CAMPUS

Explanation

A component was scaled out.

Possible failure causes

·     The user role doesn't provide the permission to perform the operation.

·     The request body cannot be empty.

·     The component name cannot be empty.

·     The specified component cannot be scaled out.

·     Failed to get the IP address allocation information.

·     The SNA Center is busy processing tasks. Please try again later.

·     Failed to scale out the component.

·     Failed to check whether SNA Installer is idle.

·     The SNA Installer is busy processing tasks.

·     Failed to get the token.

·     The configuration data sent is not the latest.

·     Failed to get component information from the database.

·     The component is already deployed on the specified host.

·     Cannot find the uplink interface bound to the specified network.

·     The specified subnet does not exist on the SNA Installer.

·     Cannot find the uplink interface bound to the specified network.

·     Failed to get the subnet information.

·     The host count does not meet the scaling requirements.

·     The component's IP address allocation information in the request is incorrect.

·     The specified node does not exist.

·     The component is already deployed on the specified host.

·     Abnormal node status.

·     When you scale out the component from single-host mode to cluster mode, you must set the new host as a Master node.

·     When you scale out the component in cluster mode, you must set the new host as a Worker.

·     The network configuration does not match the network policy.

·     The network settings in the request do not match settings of the network used when the component was deployed.

·     The specified network does not exist on the SNA Installer.

·     There are installation tasks that are not completed.

·     There are uninstallation tasks that are not completed.

·     There are update tasks that are not completed.

·     There are scaling tasks that are not completed.

 

Re-scale out component

Keyword

RE-SCALEOUT_COMPONENT_OP

Message text

Re-scaled out component: $1

Variable fields

$1: Component name.

Example

Re-scaled out component: CAMPUS

Explanation

A component was scaled out again after the previous scale-out operation failed.

Possible failure causes

·     The user role doesn't provide the permission to perform the operation.

·     The request body cannot be empty.

·     The component name cannot be empty.

·     The scaling task for the component does not exist.

·     Failed to scale out the component. Another scale-out attempt is not supported.

·     Failed to get configuration of the component from the database.

·     The SNA Center is busy processing tasks. Please try again later.

·     Failed to scale out the component.

·     Failed to check whether SNA Installer is idle.

·     The SNA Installer is busy processing tasks.

·     There are installation tasks that are not completed.

·     There are uninstallation tasks that are not completed.

·     There are update tasks that are not completed.

·     There are scaling tasks that are not completed.

 

Cancel a failed component scale-out operation

Keyword

STOP_SCALEOUT_COMPONENT_OP

Message text

Stopped scaling out component: $1

Variable fields

$1: Component name.

Example

Stopped scaling out component: CAMPUS

Explanation

A failed component scale-out operation was cancelled by the user.

Possible failure causes

·     The user role doesn't provide the permission to perform the operation.

·     Failed to check whether SNA Installer is idle.

·     The SNA Installer is busy processing tasks.

·     The scaling task for the component does not exist.

·     The SNA Center is busy processing tasks. Please try again later.

·     Failed to stop the scaling process.

·     There are installation tasks that are not completed.

·     There are uninstallation tasks that are not completed.

·     There are update tasks that are not completed.

·     There are scaling tasks that are not completed.

 

Uninstall scaled-out component instance

Keyword

UNINSTALL_SCALEDOUT_POD_OP

Message text

Uninstalled scaled-out pod: $1

Variable fields

$1: Component instance name.

Example

Uninstalled scaled-out pod: campus-pod1

Explanation

A component instance that was newly installed on a host through a scale-out operation was removed from the host.

Possible failure causes

·     The user role doesn't provide the permission to perform the operation.

·     There are uninstallation tasks that are not completed.

·     The specified component does not exist.

·     The component uninstallation cannot be performed on individual hosts.

·     The component on the specified host can not be uninstalled.

·     The component's IP address allocation information in the database is incorrect.

·     The SNA Center is busy processing tasks. Please try again later: SNA Center.

·     The system service does not respond.

·     There are installation tasks that are not completed.

·     There are uninstallation tasks that are not completed.

·     There are update tasks that are not completed.

·     There are scaling tasks that are not completed.

·     Failed to check whether SNA Installer is idle.

·     The SNA Installer is busy processing tasks.

 

 


SNAInstaller

This section contains SNAInstaller messages.

Add node

Keyword

ADD_NODE_OP

Message text

Added node: $1.

Variable fields

$1: Node information.

Example

Added node:

{

"nodeName":"",

"ipList":["100.3.1.12"],

"role":"Master",

"username":"root",

"password":"123456",

"masterId":null,

"workerId":null,

"unschedulable":false,

"nodeScheduleStatus":"IDLE"

}

Explanation

A node was added.

Possible failure causes

·     Cluster system initialization error.

·     The cluster is not deployed.

·     No configuration privilege on the backup master node.

·     Node information is being saved.

·     The cluster is being deployed.

·     Failed to obtain the node information.

·     Parameter error.

·     Invalid IP address.

·     Empty node type.

·     The host username of the node is invalid.

·     The node is unreachable.

·     Username or password error.

·     The northbound service virtual IP, cluster internal virtual IP, and node IP must be on the same network segment.

·     All node IP addresses must be on the same network segment.

·     The container IP pool can't contain node IP addresses.

·     The service IP pool can't contain node IP addresses.

·     The NTP server IP address and the node IP address are duplicate.

·     The cluster is deployed.

·     The cluster internal virtual IP address and the node IP address are duplicate.

·     The northbound service virtual IP address and the node IP address are duplicate.

·     Matrix service could not be found.

·     Invalid username.

·     Only the username used for host login when SNA Installer is installed is supported.

·     The name of the host where the specified node resides is invalid.

·     The host name of node in the cluster is different from the host name obtained when the node is added to the cluster.

·     The host names (case-insensitive) of nodes in a cluster cannot be the same.

·     Failed to add the node.

 

Update node

Keyword

UPDATE_NODE_OP

Message text

Updated node: $1 $2.

Variable fields

$1: Node ID.

$2: Node information.

Example

Updated node: node1

{

"nodeName":"",

"ipList":["100.3.1.12"],

"role":"Master",

"username":"root",

"password":"123456",

"masterId":null,

"workerId":null,

"unschedulable":false,

"nodeScheduleStatus":"IDLE"

}

Explanation

A node was modified.

Possible failure causes

·     Cluster system initialization error.

·     The cluster is not deployed.

·     No configuration privilege on the backup master node.

·     Node information is being updated.

·     Parameter error.

·     The cluster is being deployed.

·     Failed to obtain the node information.

·     The node does not exist in the cluster.

·     Enabling the nodes.

·     Failed to enable the node.

·     The cluster is not deployed.

·     The node is not deployed.

·     The node is being enabled.

·     Failed to disable the node.

·     Disabling the nodes.

·     The node is being disabled.

·     The node disable failed. Node's kubelet component is abnormal.

·     The node is being deployed.

·     The node is unreachable.

·     Matrix service could not be found.

·     The host username of the node is invalid.

·     Invalid username.

·     Only the username used for host login when SNA Installer is installed is supported.

·     Failed to modify the node.

 

Upload RPM

Keyword

UPLOAD_RPM_OP

Message text

Node $1 uploaded RPM package $2.

Variable fields

$1: Node name.

$2: RPM software package name.

Example

Node node1 uploaded RPM package SNA Installer-V500R001B02D001.x86_64.rpm.

Explanation

An RPM package was uploaded on the specified node.

Possible failure causes

·     Failed to upload the file.

·     Cluster system initialization error.

·     The cluster is not deployed.

·     No configuration privilege on the backup master node.

·     The RPM package is being uploaded.

·     Failed to obtain the node information.

·     The node does not exist in the cluster.

·     The node is unreachable.

·     File format error.

·     File operation error.

·     File transmission error.

 

Repair node

Keyword

REPAIR_NODE_OP

Message text

Repaired node: $1.

Variable fields

$1: Node repair information.

Example

Repaired node:

{

"nodeId" : "node2",

"fileName" : null,

"fileSource" : "LOCAL",

"mode" : "REPAIR"

}

Explanation

A node was repaired.

Possible failure causes

·     Parameter error.

·     Cluster system initialization error.

·     The cluster is not deployed.

·     No configuration privilege on the backup master node.

·     Repairing the nodes.

·     Upgrading the nodes.

·     The cluster is being deployed.

·     Failed to obtain the node information.

·     The node does not exist in the cluster.

·     The Leader node cannot be repaired and upgraded.

·     The node is being deployed.

·     The node is not deployed.

·     The node is being disabled.

·     The node is being enabled.

·     The node is unreachable.

·     File format error.

·     Failed to obtain the original RPM software package version information.

·     Failed to obtain the resources.

·     RPM software package is not the same version.

·     Failed to obtain the cluster parameters.

·     Cluster parameters are not set.

·     Two or more master nodes operate abnormally in the cluster.

·     The original RPM software package is corrupt.

·     The host username of the node is invalid.

·     Invalid username.

·     Only the username used for host login when SNA Installer is installed is supported.

·     The name of the host where the specified node resides is invalid.

·     The host name of node in the cluster is different from the host name obtained when the node is added to the cluster.

·     The host names (case-insensitive) of nodes in a cluster cannot be the same.

·     Internal error.

 

Upgrade node

Keyword

UPGRADE_NODE_OP

Message text

Upgraded node: $1.

Variable fields

$1: Upgrade information.

Example

Upgraded node:{

"nodeId" : "node3",

"fileName" : "SNA Installer-V500R001B03D001.x86_64.rpm",

"fileSource" : "UPLOAD",

"mode" : "UPGRADE"

}

Explanation

A node was upgraded.

Possible failure causes

·     Parameter error.

·     Cluster system initialization error.

·     The cluster is not deployed.

·     No configuration privilege on the backup master node.

·     Repairing the nodes.

·     Upgrading the nodes.

·     The cluster is being deployed.

·     Failed to obtain the node information.

·     The node does not exist in the cluster.

·     The Leader node cannot be repaired and upgraded.

·     The node is being deployed.

·     The node is not deployed.

·     The node is being disabled.

·     The node is being enabled.

·     The node is unreachable.

·     File format error.

·     Failed to obtain the original RPM software package version information.

·     Failed to obtain the resources.

·     RPM software package is same version.

·     Failed to obtain the cluster parameters.

·     Cluster parameters are not set.

·     Two or more master nodes operate abnormally in the cluster.

·     The original RPM software package is corrupt.

·     The host username of the node is invalid.

·     Invalid username.

·     Only the username used for host login when SNA Installer is installed is supported.

·     The name of the host where the specified node resides is invalid.

·     The host name of node in the cluster is different from the host name obtained when the node is added to the cluster.

·     The host names (case-insensitive) of nodes in a cluster cannot be the same.

·     Internal error.

 

Delete node

Keyword

DELETE_NODE_OP

Message text

Deleted node: $1.

Variable fields

$1: Node ID.

Example

Deleted node: node1.

Explanation

A node was deleted.

Possible failure causes

·     Parameter error.

·     Cluster system initialization error.

·     The cluster is not deployed.

·     No configuration privilege on the backup master node.

·     Nodes are being deleted.

·     Failed to delete the node.

·     The node does not exist in the cluster.

·     The node is being deployed.

·     The node is being enabled.

·     The node is being disabled.

·     The master node cannot be deleted after cluster deployment.

·     The node is being deleted.

·     Failed to delete the node because the node has been associated with a network.

 

Deploy cluster

Keyword

DEPLOY_CLUSTER_OP

Message text

Deployed cluster: initial deployment / Deployed cluster: worker node deployment.

Variable fields

None.

Example

Deployed cluster: initial deployment / Deployed cluster: worker node deployment.

Explanation

A cluster was deployed.

Possible failure causes

·     Cluster system initialization error.

·     The cluster is not deployed.

·     No configuration privilege on the backup master node.

·     The cluster is being deployed.

·     The worker node is being deployed.

·     Initial cluster deployment failed.

·     Failed to obtain the newly added node information.

·     Parameter error.

·     The node is unreachable.

·     The name of the host where the specified node resides is invalid.

·     The host name of node in the cluster is different from the host name obtained when the node is added to the cluster.

·     The host names (case-insensitive) of nodes in a cluster cannot be the same.

·     Worker node deployment failed.

·     The cluster is being deployed for the first time.

·     The cluster is deployed.

·     Cluster parameters are not set.

·     Failed to obtain the node information.

·     The number of master nodes exceeds the limit.

·     Internal error.

 

Update system config

Keyword

UPDATE_SYSTEM_CONFIG_OP

Message text

Updated system config: $1.

Variable fields

$1: System configuration.

Example

Updated system config:

{

"nfsStorage" :

{

"storage_type" : "NONE",

"external_storage_path" : null

},

"podIpPoolList" : [ "177.177.0.0/16" ],

"serviceIpPoolList" : [ "10.96.0.0/16" ],

"nodeIpPoolList" : null,

"clusterInnerVipList" : [ "10.99.212.158/32" ],

"northernServiceVipList" : [ "10.99.212.159/32" ],

"ntp_server" : "",

”clusterStatus” : ”null”

}

Explanation

System configuration was edited.

Possible failure causes

·     Cluster system initialization error.

·     The cluster is not deployed.

·     No configuration privilege on the backup master node.

·     System parameters are being saved.

·     Parameter error.

·     Failed to obtain the cluster parameters.

·     Invalid IP address.

·     The mask for a cluster internal virtual IP must be 32 bits.

·     IP address conflicts exist in the cluster parameters.

·     The mask for a northbound service virtual IP must be 32 bits.

·     Invalid IP address pool.

·     Failed to obtain the node information.

·     The remote NTP server is unreachable.

·     Cluster parameters are not set.

·     Invalid external storage path.

·     The container IP pool and service IP pool can't overlap.

·     The container IP pool can't contain NTP server IP addresses.

·     The service IP pool can't contain NTP server IP addresses.

·     The container IP pool can't contain cluster internal virtual IP addresses.

·     The service IP pool can't contain cluster internal virtual IP addresses.

·     The container IP pool can't contain northern service virtual IP addresses.

·     The service IP pool can't contain northern service virtual IP addresses.

·     The container IP pool can't contain node IP addresses.

·     The service IP pool can't contain node IP addresses.

·     The northbound service virtual IP, cluster internal virtual IP, and node IP must be on the same network segment.

·     The NTP server IP address and the node IP address are duplicate.

·     The northbound service virtual IP address and the node IP address are duplicate.

·     The cluster internal virtual IP address and the node IP address are duplicate.

·     The node is unreachable.

·     The node is being deployed.

·     The subordinate node does not have the configuration privilege.

·     Internal error.

·     Failed to apply the cluster parameters.

·     Failed to obtain the NIC information.

 

Add network

Keyword

ADD_NETWORK_OP

Message text

Added network: $1.

Variable fields

$: Network configuration.

Example

Added network:

{

"networkName" : "net1",

"vlan" : 2,

"networkType" : "macvlan",

"interfaceList" :

[ {

"nodeId" : "node3",

"interfaceNames" : [ "eth0" ]

} ],

"subnetList" :

[ {

"subnetName" : "subnet1",

"cidr" : "10.100.0.0/24",

"gateway" : "10.100.0.1"

} ]

}

Explanation

A network was added.

Possible failure causes

·     Cluster system initialization error.

·     The cluster is not deployed.

·     No configuration privilege on the backup master node.

·     The network is being added.

·     Failed to obtain network information.

·     Parameter error.

·     Invalid network name.

·     The network name already exists.

·     Invalid VLAN.

·     The associated network interface list cannot be empty.

·     Invalid parameters exist in the associated network interface.

·     The associated node cannot be duplicated.

·     One node can be associated with only one network interface.

·     The node ID does not exist.

·     Failed to obtain the resources.

·     Failed to obtain the NIC information.

·     The NIC does not exist.

·     The associated subnet list cannot be empty.

·     Interface parameters are invalid in the subnet list.

·     Invalid subnet name.

·     The subnet name cannot be duplicated.

·     The CIDR and gateway IP of the subnet are invalid.

·     The gateway IP address and the subnet address must reside on the same network segment.

·     The network segments of different subnets cannot overlap.

·     Failed to obtain VLAN information of all networks.

·     VLANs of the same network interface on the same node cannot communicate.

·     Failed to create the network.

 

Update network

Keyword

UPDATE_NETWORK_OP

Message text

Updated network: $1 $2.

Variable fields

$1: Network name.

$2: Network configuration.

Example

Updated network: net1

{

"networkName" : "net1",

"vlan" : 2,

"networkType" : "macvlan",

"interfaceList" :

[ {

"nodeId" : "node3",

"interfaceNames" : [ "eth0" ]

} ],

"subnetList" :

[ {

"subnetName" : "subnet1",

"cidr" : "10.100.0.0/24",

"gateway" : "10.100.0.2"

} ]

}

Explanation

Network configuration was edited.

Possible failure causes

·     Cluster system initialization error.

·     The cluster is not deployed.

·     No configuration privilege on the backup master node.

·     The network is being updated.

·     Parameter error.

·     Failed to obtain network information.

·     The network does not exist.

·     The network name cannot be modified.

·     The VLAN cannot be modified.

·     The associated network interface list cannot be empty.

·     Invalid parameters exist in the associated network interface.

·     The associated node cannot be duplicated.

·     One node can be associated with only one network interface.

·     The node ID does not exist.

·     Failed to obtain the resources.

·     Failed to obtain the NIC information.

·     The NIC does not exist.

·     The associated subnet list cannot be empty.

·     Interface parameters are invalid in the subnet list.

·     Invalid subnet name.

·     The subnet name cannot be duplicated.

·     The CIDR and gateway IP of the subnet are invalid.

·     The gateway IP address and the subnet address must reside on the same network segment.

·     The network segments of different subnets cannot overlap.

·     Failed to obtain VLAN information of all networks.

·     VLANs of the same network interface on the same node cannot communicate.

·     Failed to update the network.

 

Delete network

Keyword

DELETE_NETWORK_OP

Message text

Deleted network: $1.

Variable fields

$1: Network name.

Example

Deleted network: net1

Explanation

A network was deleted.

Possible failure causes

·     Cluster system initialization error.

·     The cluster is not deployed.

·     No configuration privilege on the backup master node.

·     The network is being deleted.

·     Parameter error.

·     Failed to obtain network information.

·     The network does not exist.

·     Failed to delete the network.

 

 

Upload app package

Keyword

UPLOAD_APP_PACKAGE_OP

Message text

Uploaded app package: $1.

Variable fields

$1: Application package name.

Example

Uploaded app package: dataengine-1.0.0-dao2048.zip.

Explanation

An application package was uploaded.

Possible failure causes

·     Failed to upload the file.

·     Cluster system initialization error.

·     The cluster is not deployed.

·     No configuration privilege on the backup master node.

·     The application package is being uploaded.

·     Failed to obtain the node information.

·     The network between nodes is unreachable.

·     Invalid parameters.

·     Failed to upload the installation package.

·     The installation package already exists.

·     Failed to synchronize the installation package to other nodes.

 

Install app package

Keyword

INSTALL_APP_OP

Message text

Installed app package: $1.

Variable fields

$1: Application package to install or upgrade.

Example

Installed app package:

{

"children" :

[ {

"children" :

[ {

"children" : [ ],

"installType" : "INSTALL",

"hierarchyEn" : "microservice",

"hierarchyZh" : "微服务",

"name" : "nginx",

"version" : "v1.0",

"oldVersion" : "",

"descriptionEn" : "this is nginx microservice",

"descriptionZh" : "这是一个名为nginx的微服务",

"path" : "dataengine/system/nginx",

"mandatory" : true,

"appClusters" : [ ],

"appClusterName" : null,

"scaleOutWithStandaloneToClusterStatus" : null,

"appScaleOutWithStandaloneToClusterSupported" : false,

"externalDatabases" : [ ],

"externalStorages" :

{

"volumes" : [ ]

},

"configParams" : [ ],

"k8sResources" : null

} ],

"installType" : "INSTALL",

"hierarchyEn" : "component",

"hierarchyZh" : "组件",

"name" : "system",

"version" : "1.0.0",

"oldVersion" : "",

"descriptionEn" : "this is system component",

"descriptionZh" : "这是一个名为system的组件",

"path" : "dataengine/system",

"mandatory" : true,

"appClusters" : [ ],

"appClusterName" : null,

"externalDatabases" : [ ],

"externalStorages" :

{

"volumes" : [ ]

},

"configParams" : [ ],

"k8sResources" : null

} ],

"installType" : "INSTALL",

"hierarchyEn" : "product",

"hierarchyZh" : "产品",

"name" : "dataengine",

"version" : "1.0.0",

"oldVersion" : "",

"descriptionEn" : "this is dataengine production",

"descriptionZh" : "这是一个名为dataengine的产品",

"path" : "dataengine",

"mandatory" : true,

"appClusters" : [ ],

"appClusterName" : null,

"externalDatabases" : [ ],

"externalStorages" :

{

"volumes" : [ ]

},

"configParams" : [ ],

"k8sResources" : null

}

Explanation

An application package was installed or upgraded.

Possible failure causes

·     Parameter error.

·     Cluster system initialization error.

·     The cluster is not deployed.

·     No configuration privilege on the backup master node.

·     The application package is being deployed.

·     Failed to obtain the node information.

·     Master nodes being deployed exist in the cluster.

·     Undeployed master nodes exist in the cluster.

·     Master nodes failing to be deployed exist in the cluster.

·     Master nodes operating abnormally exist in the cluster.

·     Disabled master nodes exist in the cluster.

·     The network between nodes is unreachable.

·     Invalid parameters.

·     Multiple users are not allowed to simultaneously perform deployment.

·     Etcd is operating abnormally.

·     Share storage configuration error.

·     Database configuration error.

·     Params configuration error.

·     Failed to execute the remote Linux command.

·     Invalid configuration item parameters.

·     Internal error.

 

Uninstall app

Keyword

UNINSTALL_APP_OP

Message text

Uninstalled app: $1.

Variable fields

$1: Application parameter.

Example

Uninstalled app:

{

"path" : "dataengine"

}

Explanation

An application was uninstalled.

Possible failure causes

·     Parameter error.

·     Cluster system initialization error.

·     The cluster is not deployed.

·     No configuration privilege on the backup master node.

·     The application package is being uninstalled.

·     Failed to obtain the node information.

·     The network between nodes is unreachable.

·     The application information has expired.

·     Invalid installation package hierarchy.

·     Can't be uninstalled.

·     Invalid parameters.

·     Etcd is operating abnormally.

·     Internal error.

 

Delete app package

Keyword

DELETE_APP_PACKAGE_OP

Message text

Deleted app package: $1.

Variable fields

$1: Application package.

Example

Deleted app package:

[ {

"name" : "system-service-3.2.11.zip"

} ]

Explanation

An application package was deleted.

Possible failure causes

·     Parameter error.

·     Cluster system initialization error.

·     The cluster is not deployed.

·     No configuration privilege on the backup master node.

·     The application package is being deleted.

·     Invalid parameters.

·     Failed to obtain the node information.

·     Failed to delete the installation package.

Change password

Keyword

CHANGE_PASSWORD_OP

Message text

Changed password: $1.

Variable fields

$1: Password change information.

Example

Changed password:

{

"username" : "admin",

"oldpassword" : "******",

"newpassword" : "******"

}

Explanation

The password for logging in to SNA Installer was changed.

Possible failure causes

·     Cluster system initialization error.

·     The cluster is not deployed.

·     No configuration privilege on the backup master node.

·     Parameter error.

·     The new password is the same as the old password.

·     Incorrect old password.

·     Invalid token.

·     Invalid password.

·     The Etcd service is not started for the cluster.

·     Failed to change the password.