Operation logs record system operations and configuration modifications, such as application operations (installing, starting, stopping, or uninstalling an application) and team configuration. Operation log messages include operation 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 VCF controller products.

Viewing operation log messages

Select Monitor > Operation Log to enter operation log view. The generated operation log messages are displayed on pages as shown in Figure 1.

Figure 1 Operation log messages

Table 1 Operation log message elements

Element	Description
Date/Time	Date and time when the log message was generated.
User	Name of the user that triggered the log generation.
IP	IP address of the terminal where the user performed the operation.
Origin	Name of the service module that produced the message.
Description	Text string that contains detailed information about the operation.
Result	Operation result: Success or Failure.
Failure reason	Possible reasons for an operation failure.

Syslog message format

VCF controllers can send operation logs to syslog servers through the syslog protocol. To set the IP address and port number of a syslog server, select Controller > System > Configurations on the top navigation bar, and then select Operation Log.

By default, controllers send operation logs 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 server or virtual machine where the controller that produced the message resides.
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: User=username IP=user IP Description=description Result=result Cause=operation failure causes

Table 3 lists all service modules that might produce operation log messages.

Table 3 Service module list

Service module name	Description
CON_APP	Application management module.
CON_AUTH	Authentication management module.
CON_LICENSE	License management module.
CON_LISTENER	Listener module.
CON_OPENFLOW	OpenFlow module.
CON_REGION	Region module.
CON_ROUTERCONFIGS	Route configuration module.
CON_SYSTEM	System management module.
CON_TEAM	Team module.
CON_USER	User management module.
FWaaS	Firewall service module.
LBaaS	Load balancing module.
NEM	Carrier network module.
NGFWM	NGFW manager module.
ServiceChain	Service chain module.
Tenant	Tenant module.
VPNaaS	IPsec VPN service module.
VSM	Virtual network module.
ZTP	Zero touch provisioning 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 message severity level	Syslog message severity level
0	6
1	4

Using this document

This document categories operation log messages 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.	UPLOAD_APP_OP
Message text	Presents the message description.	Uploaded application: $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: Name of the application installation package.
Example	Provides a real message example.	Uploaded application: arp-2156.zip.
Explanation	Explains the message.	An application installation package was uploaded.
Possible failure causes	Provides possible causes of an operation failure.	· Unsigned or untrusted jars contained within. · The application already exists.

CON_APP

This section contains CON_APP messages.

Install application

Keyword	INSTALL_APP_OP
Message text	$1 had been installed.
Variable fields	$1: Application name.
Example	H3C VCFC ARP had been installed.
Explanation	An application was installed.
Possible failure causes	N/A

Start application

Keyword	START_APP_OP
Message text	$1 had been started.
Variable fields	$1: Application name.
Example	H3C VCFC ARP had been started.
Explanation	An application was started.
Possible failure causes	N/A

Stop application

Keyword	STOP_APP_OP
Message text	$1 had been stopped.
Variable fields	$1: Application name.
Example	H3C VCFC ARP had been stopped.
Explanation	An application was stopped.
Possible failure causes	N/A

Uninstall application

Keyword	REMOVE_APP_OP
Message text	$1 had been removed.
Variable fields	$1: Application name.
Example	H3C VCFC ARP had been removed.
Explanation	An application was uninstalled.
Possible failure causes	N/A

Upload application

Keyword	UPLOAD_APP_OP
Message text	Uploaded application: $1.
Variable fields	$1: Name of the application installation package.
Example	Uploaded application: arp-2156.zip.
Explanation	An application installation package was uploaded.
Possible failure causes	· Unsigned or untrusted jars contained within. · Bad application package. · The number of applications exceeded the license limit. · The application already exists. · An unknown error occurs during the application package uploading process.

CON_AUTH

This section contains CON_AUTH messages.

Add an authentication-free IP

Keyword	ADD_AUTH_FREEIP_OP
Message text	Added an authentication-free IP: $1
Variable fields	$1: IP address of the authentication-free user.
Example	Added an authentication-free IP: 192.168.56.13
Explanation	An authentication-free user was added.
Possible failure causes	· Invalid IP address. · The IP address already exists. · Can't add an authentication-free IP due to permission limit. · Unknown error. · Invalid role. · Invalid description.

Delete an authentication-free IP

Keyword	DELETE_AUTH_FREEIP_OP
Message text	Deleted an authentication-free IP: $1
Variable fields	$1: IP address of the authentication-free user.
Example	Deleted an authentication-free IP: 192.168.56.13
Explanation	An authentication-free user was deleted.
Possible failure causes	· Can't delete an authentication-free IP due to permission limit. · Unknown error. · Invalid IP address. · The IP address does not exist.

CON_LICENSE

This section contains CON_LICENSE messages.

Upload license file

Keyword	UPLOAD_LICENSE_FILE_OP
Message text	Uploaded license file
Variable fields	N/A
Example	Uploaded license file
Explanation	A license file was uploaded.
Possible failure causes	License file error.

Update the quantity of requested licenses

Keyword	UPDATE_REQUESTED_LICENSES_OP
Message text	Updated the quantity of requested licenses:$1.
Variable fields	$1: Information about the quantity of requested licenses.
Example	Updated the quantity of requested licenses: APP license: 1 MaxNodeNum license: 1 VirtualServiceNode license: 1 vSwitch license: 0 ZTP license: true API license: true Overlay license: true OverlayHardwareEntity license: 1 ServiceChain license: true Base license: 1.
Explanation	The quantity of requested licenses was changed.
Possible failure causes	Failed to save the configuration.

Connect the license server

Keyword	CONNECT_LICS_OP
Message text	Connected the license server: $1
Variable fields	$1: License server configuration information.
Example	Connected the license server: License server IP: 192.168.40.40 Port: 5555 Username: sdn Password: ******
Explanation	The user attempted to connect the controller to the license server.
Possible failure causes	· Incorrect license server IP address or port number. · Incorrect username or password.

Disconnect the license server

Keyword	DISCONNECT_LICS_OP
Message text	Disconnected the license server: $1
Variable fields	$1: License server IP address.
Example	Disconnected the license server: 192.168.1.1
Explanation	The user disconnected the controller from the license server.
Possible failure causes	N/A

CON_LISTENER

This section contains CON_LISTENER messages.

Register alert topic

Keyword	REGISTER_ LISTENER_OP
Message text	Registered alert topic listener: $1
Variable fields	$1: Alert topic listener configuration.
Example	Registered alert topic listener: { "alert": { "url": "http://192.168.16.2/vnetcontroller/alter", "level": "warn", "subject": ["tunnel", "session"], "app_name": "vnetcontroller", "push_history": true } }
Explanation	An alert topic listener was registered.
Possible failure causes	A listener with the same app_name has already been registered.

Update alert topic

Keyword	UPDATE_LISTENER_OP
Message text	Updated alert topic listener: $1
Variable fields	$1: Alert topic listener configuration.
Example	Updated alert topic listener: { "alert": { "app_name": "vnetcontroller", "level": "warn", "subject": ["tunnel", "session"] } }
Explanation	An alert topic listener was modified.
Possible failure causes	N/A.

Remove alert topic

Keyword	REMOVE_LISTENER_OP
Message text	Removed alert topic listener: $1
Variable fields	$1: Name of the alert topic listener.
Example	Removed alert topic listener: vnetcontroller
Explanation	An alert topic listener was removed.
Possible failure causes	N/A.

CON_OPENFLOW

This section contains CON_OPENFLOW messages.

Create flow table entry

Keyword	CREATE_FLOWTABLE_OP
Message text	A flow table entry was added.
Variable fields	N/A
Example	A flow table entry was added.
Explanation	A flow table entry was added.
Possible failure causes	N/A

Modify flow table entry

Keyword	MODIFY_FLOWTABLE_OP
Message text	A flow table entry was modified.
Variable fields	N/A
Example	A flow table entry was modified.
Explanation	A flow table entry was modified.
Possible failure causes	N/A

Delete flow table entry

Keyword	DELETE_FLOWTABLE_OP
Message text	A flow table entry was deleted.
Variable fields	N/A
Example	A flow table entry was deleted.
Explanation	A flow table entry was deleted.
Possible failure causes	No such device: Datapath ID: OpenFlow network device has been disconnected.

Devices change to fail-safe mode

Keyword	CHANGE_DEVICE_FAILSAFE_OP
Message text	Devices changed to fail-safe mode. All controllers in the team are disallowed to accept OpenFlow connection requests.
Variable fields	N/A
Example	Devices changed to fail-safe mode. All controllers in the team are disallowed to accept OpenFlow connection requests.
Explanation	The fail-safe mode was set.
Possible failure causes	Abnormal connections between the active leader and other controllers in the team.

Devices change to normal mode

Keyword	CHANGE_DEVICE_NORMAL_OP
Message text	Devices changed to normal mode. All controllers in the team are allowed to accept OpenFlow connection requests.
Variable fields	N/A
Example	Devices changed to normal mode. All controllers in the team are allowed to accept OpenFlow connection requests.
Explanation	The normal mode was set.
Possible failure causes	Abnormal connections between the active leader and other controllers in the team.

CON_REGION

This section contains CON_REGION messages.

Create region

Keyword	CREATE_REGION_ OP
Message text	Created region: $1
Variable fields	$1: Region information.
Example	Created region: Name:region1 Region ID:fdd9f2d3-d2b2-4afe-942f-e6943b54e259 DenyvSwitch:false Master:192.168.56.153 Subordinate: 192.168.56.154 ManagedNodeSubnets: 192.168.38.25/24 192.168.39.25/24
Explanation	A region was created.
Possible failure causes	· The team doesn't exist. · Incorrect controller IP address. · The region name is already used. · The controller was already in a region. · The controller is not the active leader. · Incorrect JSON format. · The request can't be null. · Incorrect controller name. · The master IP address must be different from the subordinate IP address. · Incorrect IP address or mask format for the managed node subnets.

Delete region

Keyword	DELETE_REGION_OP
Message text	Deleted region:$1
Variable fields	$1: Region information.
Example	Deleted region: Name: region1 Region ID: fdd9f2d3-d2b2-4afe-942f-e6943b54e259 DenyvSwitch:false Master:192.168.56.153 Subordinate: 192.168.56.154 ManagedNodeSubnets: 192.168.38.25/24 192.168.39.25/24
Explanation	A region was deleted.
Possible failure causes	· The controller is not the active leader. · Incorrect JSON format. · The region does not exist.

Update region

Keyword	UPDATE_REGION_OP
Message text	Updated region:$1
Variable fields	$1: Region information.
Example	Updated region: Name: region1 Region ID: fdd9f2d3-d2b2-4afe-942f-e6943b54e259 DenyvSwitch:false Master:192.168.56.153 Subordinate: 192.168.56.154 ManagedNodeSubnets: 192.168.38.25/24 192.168.39.25/24
Explanation	A region was updated.
Possible failure causes	· The region does not exist. · The controller is not the active leader. · Incorrect JSON format. · The request can't be null. · The input region information was incorrect. · Incorrect IP address or mask format for the managed node subnets.

CON_ROUTERCONFIGS

This section contains CON_ROUTERCONFIGS messages.

Assign an IP address to the loopback interface

Keyword	ADD_LOOPBACK_OP
Message text	Assigned an IP address to the loopback interface: IP: $1
Variable fields	$1: IP address of the loopback interface.
Example	Assigned an IP address to the loopback interface: IP: 2.3.3.3
Explanation	An IP address is assigned to the loopback interface.
Possible failure causes	· The loopback interface already has an IP address. · Failed to deploy the address configuration of the loopback interface.

Delete the IP address of the loopback interface

Keyword	DELETE_LOOPBACK_OP
Message text	Deleted the IP address of the loopback interface: IP: $1
Variable fields	$1: IP address of the loopback interface.
Example	Deleted the IP address of the loopback interface: IP: 2.3.3.3
Explanation	The IP address of the loopback interface was removed.
Possible failure causes	· The IP address doesn't exist. · Failed to deploy the request for deleting the IP address.

Add BGP instance

Keyword	ADD_BGPINSTANCE_OP
Message text	Added BGP instance: Router ID: $1 Local AS number: $2
Variable fields	$1: Router ID of the BGP instance. $2: Local AS number of the BGP instance.
Example	Added BGP instance: Router ID: 10.10.10.10 Local AS number: 1000
Explanation	A BGP instance was added.
Possible failure causes	· The local AS number already exists. · Failed to connect to bgpd. Check whether Quagga is correctly installed or the BGP daemon is enabled. · Failed to deploy the BGP instance configuration. · Failed to deploy the BGP router ID configuration. · Operation failed because the controller is deploying routing configuration. Please try again later.

Clear BGP configuration

Keyword	CLEAR_BGP_CONF_OP
Message text	Cleared BGP configuration.
Variable fields	N/A
Example	Cleared BGP configuration.
Explanation	The BGP configuration was cleared.
Possible failure causes	· Failed to deploy the request for deleting BGP instance. · Failed to connect to bgpd. Check whether Quagga is correctly installed or the BGP daemon is enabled. · The BGP instance doesn't exist. · Operation failed because the controller is deploying routing configuration. Please try again later.

Add BGP network

Keyword	ADD_BGPNETWORK_OP
Message text	Added BGP network: IP: $1
Variable fields	$1: Local network address.
Example	Added BGP network: IP: 10.10.10.10/32
Explanation	A local network was injected to the BGP routing table.
Possible failure causes	· The BGP instance doesn't exist. · The network already exists. · Failed to deploy the network configuration. · Failed to connect to bgpd. Check whether Quagga is correctly installed or the BGP daemon is enabled. · The number of networks reaches the upper limit. · Operation failed because the controller is deploying routing configuration. Please try again later.

Delete BGP network

Keyword	DELETE_BGPNETWORK_OP
Message text	Deleted BGP network: IP: $1
Variable fields	$1: Local network address.
Example	Deleted BGP network: IP: 10.10.10.10/32
Explanation	The specified local network was removed from the BGP routing table.
Possible failure causes	· The BGP instance doesn't exist. · The network doesn’t exist. · Failed to deploy the request for deleting network. · Failed to connect to bgpd. Check whether Quagga is correctly installed or the BGP daemon is enabled. · Operation failed because the controller is deploying routing configuration. Please try again later.

Add BGP neighbor

Keyword	ADD_BGPNEIGHBOR_OP
Message text	Added BGP neighbor: IP: $1 Remote AS number: $2 Filtering policy: $3
Variable fields	$1: IP address of the BGP neighbor. $2: AS number of the BGP neighbor. $3: Filtering policy.
Example	Added BGP neighbor: IP: 10.10.10.11 Remote AS number: 1000 Filtering policy: in
Explanation	A BGP neighbor was added.
Possible failure causes	· The BGP instance doesn't exist. · The neighbor already exists. · Failed to deploy the neighbor configuration. · Failed to connect to bgpd. Check whether Quagga is correctly installed or the BGP daemon is enabled. · The number of BGP neighbors reaches the upper limit. · Operation failed because the controller is deploying routing configuration. Please try again later.

Delete BGP neighbor

Keyword	DELETE_BGPNEIGHBOR_OP
Message text	Deleted BGP neighbor: IP: $1 Remote AS number: $2 Filtering policy: $3
Variable fields	$1: IP address of the BGP neighbor. $2: AS number of the BGP neighbor. $3: Filtering policy.
Example	Deleted BGP neighbor: IP: 10.10.10.11 Remote AS number: 1000 Filtering policy: in
Explanation	The specified BGP neighbor was deleted.
Possible failure causes	· The BGP instance doesn't exist. · The neighbor doesn't exist. · Failed to deploy the request for deleting neighbor. · Failed to connect to bgpd. Check whether Quagga is correctly installed or the BGP daemon is enabled. · Operation failed because the controller is deploying routing configuration. Please try again later.

Add timer

Keyword	ADD_BGPTIMER_OP
Message text	Added timer: Keepalive interval: $1 Hold time: $2
Variable fields	$1: Keepalive interval of BGP sessions, in seconds. $2: Hold time of BGP sessions, in seconds.
Example	Added timer: Keepalive interval: 600 Hold time: 1800
Explanation	The BGP keepalive interval and hold time were set.
Possible failure causes	· Failed to deploy the keepalive interval and hold time configuration. · Failed to connect to bgpd. Check whether Quagga is correctly installed or the BGP daemon is enabled. · The BGP instance doesn't exist. · Operation failed because the controller is deploying routing configuration. Please try again later.

Add OSPF router ID

Keyword	ADD_OSPFROUTERID_OP
Message text	Added OSPF router ID: IP: $1
Variable fields	$1: OSPF router ID
Example	Added OSPF router ID: IP: 10.10.10.10
Explanation	An OSPF router ID was added.
Possible failure causes	· The router ID already exists. · Failed to deploy the router ID configuration. · Failed to connect to ospfd. Check whether Quagga is correctly installed or the OSPF daemon is enabled. · Operation failed because the controller is deploying routing configuration. Please try again later.

Add OSPF network

Keyword	ADD_OSPFNETWORK_OP
Message text	Added OSPF network: IP: $1 Area ID: $2
Variable fields	$1: Network address. $2: Area ID.
Example	Added OSPF network: IP: 10.10.10.10/32 Area ID: 0
Explanation	An OSPF network route was added.
Possible failure causes	· The network already exists. · Failed to deploy the network configuration. · Failed to connect to ospfd. Check whether Quagga is correctly installed or the OSPF daemon is enabled. · The number of networks reaches the upper limit. · Operation failed because the controller is deploying routing configuration. Please try again later.

Delete OSPF network

Keyword	DELETE_OSPFNETWORK_OP
Message text	Deleted OSPF network: IP: $1 Area ID: $2
Variable fields	$1: Network address. $2: Area ID.
Example	Deleted OSPF network: IP: 10.10.10.10 Area ID: 0
Explanation	An OSPF network route was deleted.
Possible failure causes	· The network doesn't exist. · Failed to deploy the request for deleting network. · Failed to connect to ospfd. Check whether Quagga is correctly installed or the OSPF daemon is enabled. · Operation failed because the controller is deploying routing configuration. Please try again later.

Clear OSPF configuration

Keyword	CLEAR_OSPF_CONF_OP
Message text	Cleared OSPF configuration.
Variable fields	N/A
Example	Cleared OSPF configuration.
Explanation	The OSPF configuration was cleared.
Possible failure causes	· Failed to deploy the request for deleting OSPF configuration. · Failed to connect to ospfd. Check whether Quagga is correctly installed or the OSPF daemon is enabled. · Operation failed because the controller is deploying routing configuration. Please try again later.

Add OSPF area

Keyword	ADD_OSPFAREA_OP
Message text	Added OSPF area: Area ID: $1 NSSA: $2 Authentication: $3
Variable fields	$1: Area ID. $2: NSSA area attribute. $3: Authentication mode.
Example	Added OSPF area: Area ID: 1.2.3.6 NSSA: translate-candidate Authentication: message-digest
Explanation	An OSPF area was added.
Possible failure causes	· The area already exists. · Failed to deploy the area configuration. · Failed to connect to ospfd. Check whether Quagga is correctly installed or the OSPF daemon is enabled. · Operation failed because the controller is deploying routing configuration. Please try again later.

Delete OSPF area

Keyword	DELETE_OSPFAREA_OP
Message text	Deleted OSPF area: Area ID: $1
Variable fields	$1: Area ID.
Example	Deleted OSPF area: Area ID: 0.0.0.0
Explanation	The specified OSPF area was deleted.
Possible failure causes	· The area doesn't exist. · Failed to deploy the request for deleting area. · Failed to connect to ospfd. Check whether Quagga is correctly installed or the OSPF daemon is enabled. · Operation failed because the controller is deploying routing configuration. Please try again later.

CON_SYSTEM

This section contains CON_SYSTEM messages.

Back up configuration

Keyword	BACKUP_OP
Message text	Backed up the configuration.
Variable fields	N/A
Example	Backed up the configuration.
Explanation	A backup session was completed.
Possible failure causes	· The operation requires the administrator privilege. · Failed to create the backup file. · The system is recovering the configuration. · The team to which the controller belongs has no active leader.

Upload backup file

Keyword	UPLOAD_BACKUPFILE_OP
Message text	Uploaded the backup file.
Variable fields	N/A
Example	Uploaded the backup file.
Explanation	A backup file was uploaded.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · Invalid backup file format. · Invalid backup file content. · The active leader can't send the backup file to other controllers due to network errors. · The system is recovering the configuration. · The team to which the controller belongs has no active leader.

Recover configuration

Keyword	RESTORE_OP
Message text	Restored the configuration.
Variable fields	N/A
Example	Restored the configuration.
Explanation	The configuration was recovered.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · The backup file doesn't exist. · The backup file doesn't include the required files. · The controller's IP address is not included in the team settings of the backup file. · The active leader can't restore the configuration of other controllers due to network errors. · The system is recovering the configuration. · The team to which the controller belongs has no active leader.

Download backup file

Keyword	DOWNLOAD_BACKUPFILE_OP
Message text	Downloaded the backup file.
Variable fields	N/A
Example	Downloaded the backup file.
Explanation	The backup file had been successfully downloaded.
Possible failure causes	· The operation requires the administrator privilege. · The backup file doesn't exist. · The system is recovering the configuration. · The team to which the controller belongs has no active leader.

Modify backup settings

Keyword	MODIFY_BACKUPSET_OP
Message text	Modified settings for configuration backup.
Variable fields	N/A
Example	Modified settings for configuration backup.
Explanation	The configuration backup settings were modified.
Possible failure causes	· Illegal backup settings. · The operation requires the administrator privilege. · The controller is not the active leader. · Not permitted to access the backup path. · Failed to save the settings. · The system is recovering the configuration. · The team to which the controller belongs has no active leader.

Modify configuration

Keyword	MODIFY_CONFIG_OP
Message text	Modified configuration: $1.
Variable fields	$1: Component name and configuration items.
Example	Modified configuration: Authentication Manager { ConnPoolMaxActive=4 AuthenticationProtocol=PAP SharedKey=****** AuthMode=local AAAServerIP=192.168.56.19 ConnPoolMaxIdle=1 CachedTokenIdle=900 }.
Explanation	The values for the configuration items of the specified component were modified. If a password or key is included in the component, it is displayed with asterisks (******).
Possible failure causes	· Failed to update the configuration file. · The existing team token must be deleted before you configure a new one. · Invalid value for parameter $1. · Failed to encrypt the password or key.

Restore configuration

Keyword	RESTORE_CONFIG_OP
Message text	Restored configuration: $1.
Variable fields	$1: Component name and configuration items. If the values for all configuration items are restored, only the component name is displayed.
Example	Restored configuration: Authentication Manager { ConnPoolMaxActive=4 AuthenticationProtocol=PAP SharedKey=****** AuthMode=local AAAServerIP=192.168.56.19 ConnPoolMaxIdle=1 CachedTokenIdle=900 }.
Explanation	The values for the configuration items of the specified component were restored to the default. If a password or key is included in the component, it is displayed with asterisks (******).
Possible failure causes	· Can't delete the team token in team mode. · Failed to update the configuration file.

Prepare for upgrade

Keyword	UPGRADE_PREPARE_OP
Message text	Prepared for upgrade: $1
Variable fields	$1: IP address of the controller that performed the upgrade preparation.
Example	Prepared for upgrade
Explanation	Upgrade preparation was performed.
Possible failure causes	· Can't prepare for upgrade due to permission limit. · Invalid request.

Enter upgrade mode

Keyword	ENTER_UPGRADE_MODE_OP
Message text	Enter upgrade mode.
Variable fields	N/A
Example	Enter upgrade mode.
Explanation	The user performed the operation of entering the upgrade mode.
Possible failure causes	N/A

Quit upgrade mode

Keyword	QUIT_UPGRADE_MODE_OP
Message text	Quit upgrade mode.
Variable fields	N/A
Example	Quit upgrade mode.
Explanation	The user performed the operation of quitting the upgrade mode.
Possible failure causes	N/A

CON_TEAM

This section contains CON_TEAM messages.

Create team

Keyword	CREATE_TEAM_OP
Message text	Created team: $1
Variable fields	$1: Configuration of the team.
Example	Created team: Name: TestCluster1 IP: 192.168.40.40 Mask: 255.255.255.0 Mode:1 Version: 1404159495844 Team ID: f892866f-0ec9-4ef0-a0a8-6df783ef7b19 Leaders: [ {Name: leader1, IP: 192.168.56.147, Priority: 200, Network_device: eth0, Server ID: 1}, {Name: leader2, IP: 192.168.56.148, Priority: 100, Network_device: eth1, Server ID: 2} ] Members: [ {Name: member, IP: 192.168.40.146, Priority: 1016, Network_device: , Server ID: 5} ]
Explanation	A team was created.
Possible failure causes	· The team contained only one leader. · The controller was not a leader. · Team IP address and member IP address must be different. · Member IP addresses must be different. · Member names must be different. · Leader priorities must be different. · The number of controllers exceeded the upper limit (32). · Server processing error. · The versions of the controllers are inconsistent. · The team token is not configured for the controller.

Delete team

Keyword	DELETE_TEAM_OP
Message text	Deleted team: $1
Variable fields	$1: Configuration of the team.
Example	Deleted team: Name: TestCluster1 IP: 192.168.40.40
Explanation	A team was deleted.
Possible failure causes	· The team didn't exist. · The controller was not the active leader. · Server processing error.

Modify team

Keyword	MODIFY_TEAM_OP
Message text	Modified team: $1
Variable fields	$1: Configuration modification of the team.
Example	Modified team: Name:TestCluster1->TestCluster2 IP:192.168.35.11->192.168.35.12 Mask:255.255.255.0->255.255.0.0
Explanation	A team was modified.
Possible failure causes	· The controller was not the active leader. · The team didn't exist. · Server processing error. · The team name is invalid.

Add member

Keyword	ADD_MEMBER_OP
Message text	Added member: $1
Variable fields	$1: Member information.
Example	Added member: Name:leader1 IP:192.168.56.147
Explanation	A member was added.
Possible failure causes	· The controller was not the active leader. · The team didn't exist. · The member IP address must be different from the team IP address. · The member IP address was already used. · The member name was already used. · Server processing error. · The version of the selected controller is different than the team.

Delete member

Keyword	DELETE_MEMBER_OP
Message text	Deleted member: $1
Variable fields	$1: Member information.
Example	Deleted member: Name:leader1 IP:192.168.56.147
Explanation	A member was deleted.
Possible failure causes	· The controller was not the active leader or the member to be deleted. · The member didn't exist. · A leader can't be deleted. · The member was in a region. · Server processing error.

Modify member

Keyword	MODIFY_MEMBER_OP
Message text	Modified member: $1
Variable fields	$1: Member modification information.
Example	Modified member: Name:member1->member2 IP:192.168.35.11 Network_device:eth0->eth1
Explanation	A member was modified.
Possible failure causes	· The controller was not the active leader. · NIC for the member can't be changed. · Server processing error. · The controller name is invalid. · The member name was already used.

CON_USER

This section contains CON_USER messages.

Add a user

Keyword	ADD_USER_OP
Message text	Added a user:$1.
Variable fields	$1: User name.
Example	Added a user:11.
Explanation	A user was added.
Possible failure causes	· Invalid username. · The username already exists. · No permission to add a new user. · The password length is out of range or the password contains only letters, digits, or special characters. · Invalid role.

Delete a user

Keyword	DELETE_USER_OP
Message text	Deleted a user: $1.
Variable fields	$1: User name.
Example	Deleted a user: 11.
Explanation	A user was deleted.
Possible failure causes	· Invalid username. · No permission to delete a user. · The user does not exist. · No permission to delete itself. · Can't delete an online user.

Change user password

Keyword	CHANGE_PASSWORD_OP
Message text	Changed user $1's password.
Variable fields	$1: Username.
Example	Changed user 11's password.
Explanation	A user's password was changed.
Possible failure causes	· Invalid username. · Invalid old password. · The password length is out of range or the password contains only letters, digits, or special characters. · Can't modify another users' password due to permission limit. · Can't modify the configuration of other online users.

FWaaS

This section contains messages from the firewall service module.

Create time range

Keyword	CREATE_TIMERANGE_OP
Message text	Created time range $1.
Variable fields	$1: Information about the time range.
Example	Created time range ID: 9a83d713-8e79-4ca8-a2e9-8df29daf5fd6 Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: tr Description: time range Shared: false In use: false Periodic range list: Position: 1 Start time: 00:00 End time: 24:00 Days of week: [MON, TUE, WED, THU, FRI, SAT] Absolute range list: Position: 1 Start time: 00:00 Start date: 2014-08-02 End time: 24:00 End date: 2100-12-31.
Explanation	A time range was created.
Possible failure causes	· Invalid json format. · The configuration item already exists. · The tenant specified for the configuration item doesn't exist. · The number of configuration items exceeded the limit. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The firewall service has not been found. · The inused field should be read only.

Update time range

Keyword	UPDATE_TIMERANGE_OP
Message text	Updated time range $1.
Variable fields	$1: Information about the time range.
Example	Updated time range ID: 9a83d713-8e79-4ca8-a2e9-8df29daf5fd6 Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: tr Description: time range Shared: false In use: false Periodic range list: Position: 1 Start time: 00:00 End time: 20:00 Days of week: [MON, TUE, WED, THU, FRI, SAT] Absolute range list: Position: 1 Start time: 00:00 Start date: 2014-08-02 End time: 24:00 End date: 2100-12-30.
Explanation	A time range was modified.
Possible failure causes	· Invalid json format. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The firewall service has not been found. · The configuration item doesn't exist.

Delete time range

Keyword	DELETE_TIMERANGE_OP
Message text		Deleted time range $1.
Variable fields		$1: Name of the time range.
Example		Deleted time range tr.
Explanation		A time range was deleted.
Possible failure causes		· Invalid UUID string: asd-+. · The configuration item is in use. · The configuration item doesn't exist. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The firewall service has not been found.

Create firewall object group

Keyword	CREATE_FWOBJECTGROUP_OP
Message text	Created firewall object group $1.
Variable fields	$1: Information about the firewall object group.
Example	Created firewall object group ID: b52fff79-7bcf-4bff-9340-68c5f6c1c495 Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: fw_objectgroup Description: firewall object group Type: IPv4.
Explanation	A firewall object group was created.
Possible failure causes	· Invalid json format. · The configuration item already exists. · The tenant specified for the configuration item doesn't exist. · No tenant ID is specified. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The firewall service has not been found.

Update firewall object group

Keyword	UPDATE_FWOBJECTGROUP_OP
Message text	Updated firewall object group $1.
Variable fields	$1: Information about the firewall object group.
Example	Updated firewall object group ID: b52fff79-7bcf-4bff-9340-68c5f6c1c495 Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: fw_objectgroup Description: firewall object group Type: IPv4 Audited: true.
Explanation	A firewall object group was modified.
Possible failure causes	· Invalid json format. · The tenant ID is read only. · The object group type is read only. · The tenant name is read only. · The object group ID is read only. · The object group name is read only. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The firewall service has not been found. · The configuration item doesn't exist.

Delete firewall object group

Keyword	DELETE_FWOBJECTGROUP_OP
Message text	Deleted firewall object group $1.
Variable fields	$1: Name of the firewall object group.
Example	Deleted firewall object group fw_objectgroup.
Explanation	A firewall object group was deleted.
Possible failure causes	· Invalid UUID string: asd-+. · The configuration item is in use. · The configuration item doesn't exist. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The firewall service has not been found.

Create firewall object

Keyword	CREATE_FWOBJECT_OP
Message text	Created firewall object $1.
Variable fields	$1: Information about the firewall object.
Example	Created firewall object ID: b52fff79-7bcf-4bff-9340-68c5f6c1c495 Name: fw_object Sequence: 0 Protocol: TCP Source port: 100:200 Destination port: 300:400 Object group ID: 9a83d713-8e79-4ca8-a2e9-8df29daf5fd6.
Explanation	A firewall object was created.
Possible failure causes	· Invalid json format. · No object group ID is specified. · The object group specified for the configuration item doesn't exist. · The configuration item already exists. · The IPv4_address is available only when the object group type is IPv4. · The source_port, destination_port, and protocol are available only when the object group type is service. · The name is required. · The IPv4 address is required. · The protocol is required. · The number of configuration items exceeded the limit. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The firewall service has not been found. · The sequence number is read only.

Update firewall object

Keyword	UPDATE_FWOBJECT_OP
Message text	Updated firewall object $1.
Variable fields	$1: Information about the firewall object.
Example	Updated firewall object ID: b52fff79-7bcf-4bff-9340-68c5f6c1c495 Name: fw_object Sequence: 0 Protocol: TCP Source port: 100:200 Destination port: 300:400 Object group ID: 9a83d713-8e79-4ca8-a2e9-8df29daf5fd6.
Explanation	A firewall object was modified.
Possible failure causes	· Invalid json format. · The ID is read only. · The object name is read only. · The sequence number is read only. · The object group ID is read only. · The IPv4_address is available only when the object group type is IPv4. · The source_port, destination_port, and protocol are available only when the object group type is service. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The firewall service has not been found. · The configuration item doesn't exist.

Delete firewall object

Keyword	DELETE_FWOBJECT_OP
Message text	Deleted firewall object $1.
Variable fields	$1: Name of the firewall object.
Example	Deleted firewall object fw_object.
Explanation	A firewall object was deleted.
Possible failure causes	· Invalid UUID string: asd-+. · The configuration item doesn't exist. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The firewall service has not been found.

Create firewall rule

Keyword	CREATE_FWRULE_OP
Message text	Created firewall rule $1.
Variable fields	$1: Information about the firewall rule.
Example	Created firewall rule ID: b52fff79-7bcf-4bff-9340-68c5f6c1c495 Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: fw_rule Description: firewall rule Shared: true Protocol: null IP version: IPv4 Source IP address: 22.2.2.2 Destination IP address: 11.1.1.1 Source port: 100:200 Destination port: 300:400 Position: null Action: ALLOW Enabled: true Time range ID: 9a83d713-8e79-4ca8-a2e9-8df29daf5fd6 Logging: true Counting: true Object group-based matching: true Source IP object group ID: b52fff79-7bcf-4bff-9340-68c5f6cfffff Destination IP object group ID: b52fff79-7bcf-4bff-9340-68c5f6ceeeee Service object group ID: b52fff79-7bcf-4bff-9340-68c5f6crrrrr
Explanation	A firewall rule was created.
Possible failure causes	· Invalid json format. · The configuration item already exists. · The tenant specified for the configuration item doesn't exist. · The tenant IDs for the configuration items are different. · The time range specified for the rule doesn't exist. · The source object group specified for the rule doesn't exist. · The destination object group specified for the rule doesn't exist. · The service object group specified for the rule doesn't exist. · Failed to add the configuration item. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The firewall service has not been found. · The match rules for virtual firewalls do not support the reject action.

Update firewall rule

Keyword	UPDATE_FWRULE_OP
Message text	Updated firewall rule $1.
Variable fields	$1: Information about the firewall rule.
Example	Updated firewall rule ID: b52fff79-7bcf-4bff-9340-68c5f6c1c495 Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: fw_rule Description: firewall rule Shared: true Protocol: TCP IP version: IPv4 Source IP address: 22.2.2.2 Destination IP address: 11.1.1.1 Source port: 1222:1222 Destination port: 1333:1333 Position: null Action: ALLOW Enabled: true Time range ID: 9a83d713-8e79-4ca8-a2e9-8df29daf5fd6 Logging: true Counting: true Object group match: true Source IP object group ID: b52fff79-7bcf-4bff-9340-68c5f6cfffff Destination IP object group ID: b52fff79-7bcf-4bff-9340-68c5f6ceeeee Service object group ID: b52fff79-7bcf-4bff-9340-68c5f6crrrrr
Explanation	A firewall rule was modified.
Possible failure causes	· Invalid json format. · The time range specified for the rule doesn't exist. · The source object group specified for the rule doesn't exist. · The destination object group specified for the rule doesn't exist. · The service object group specified for the rule doesn't exist. · The tenant IDs for the configuration items are different. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The firewall service has not been found. · The configuration item doesn't exist. · The match rules for virtual firewalls do not support the reject action.

Delete firewall rule

Keyword	DELETE_FWRULE_OP
Message text	Deleted firewall rule $1.
Variable fields	$1: Name of the firewall rule.
Example	Deleted firewall rule fw_rule.
Explanation	A firewall rule was deleted.
Possible failure causes	· Invalid UUID string: asd-+. · The configuration item is in use. · The configuration item doesn't exist. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The firewall service has not been found.

Create firewall policy

Keyword	CREATE_FWPOLICY_OP
Message text	Created firewall policy $1.
Variable fields	$1: Information about the firewall policy.
Example	Created firewall policy ID: 70dc3186-ac5b-4ba1-ac7f-7a27ef566efb Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: fw_policy Description: firewall policy Shared: false Rule list: [1510d574-ac17-4078-9a60-719ac7740f84] Audited: true.
Explanation	A firewall policy was created.
Possible failure causes	· Invalid json format. · The configuration item already exists. · The tenant specified for the configuration item doesn't exist. · The tenant IDs for the configuration items are different. · The rule specified for the policy doesn't exist. · The rule is already used by another policy. · The number of rules specified for the policy exceeded the limit. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The firewall service has not been found.

Update firewall policy

Keyword	UPDATE_FWPOLICY_OP
Message text	Updated firewall policy $1.
Variable fields	$1: Information about the firewall policy.
Example	Updated firewall policy ID: 70dc3186-ac5b-4ba1-ac7f-7a27ef566efb Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: fw_policy Description: firewall policy Shared: false Rule list: [1510d574-ac17-4078-9a60-719ac7740f84] Audited: false.
Explanation	A firewall policy was modified.
Possible failure causes	· Invalid json format. · The tenant IDs for the configuration items are different. · The rule specified for the policy doesn't exist. · The rule is already used by another policy. · The number of rules specified for the policy exceeded the limit. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The firewall service has not been found. · The configuration item doesn't exist.

Delete firewall policy

Keyword	DELETE_FWPOLICY_OP
Message text	Deleted firewall policy $1.
Variable fields	$1: Name of the firewall policy.
Example	Deleted firewall policy fw_policy.
Explanation	A firewall policy was deleted.
Possible failure causes	· Invalid UUID string: asd-+. · The configuration item is in use. · The configuration item doesn't exist. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The firewall service has not been found.

Create firewall

Keyword	CREATE_FW_OP
Message text	Created firewall $1.
Variable fields	$1: Information about the firewall.
Example	Created firewall ID: 6835896c-5152-4bed-a2ab-092c9980e2b8 Tenant ID : ffffffff-0000-0000-0000-000000000001 Name: fw Description: firewall Status: DOWN Shared: true Forward Policy ID: d233005f-22bd-4e2b-8ac0-bdef810f533a Backward Policy ID: c133005f-23bd-5a6b-7bb0-dbef710f524c Mode: GATEWAY.
Explanation	A firewall was created.
Possible failure causes	· Invalid json format. · The configuration item already exists. · The tenant specified for the configuration item doesn't exist. · The tenant IDs for the firewall and the specified forward policy are different. · The tenant IDs for the firewall and the specified backward policy are different. · The tenant IDs for the firewall and the specified vRouter are different. · The tenant IDs for the firewall and the specified network resource are different. · The forward policy specified for the firewall doesn't exist. · The backward policy specified for the firewall doesn't exist. · The forward policy is already used by another firewall. · The backward policy is already used by another firewall. · The vRouter specified for the firewall doesn't exist. · The vRouter is already used by another firewall. · The type of the network resource specified for the firewall is not vFW. · The network resource specified for the firewall doesn't exist. · The number of firewalls bound to the resource exceeded the limit. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The firewall service has not been found.

Update firewall

Keyword	UPDATE_FW_OP
Message text	Updated firewall $1.
Variable fields	$1: Information about the firewall.
Example	Updated firewall ID: 6835896c-5152-4bed-a2ab-092c9980e2b8 Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: fw Description: firewall Status: ACTIVE Shared: true Forward Policy ID: 572744ad-6bda-4617-aef2-78b58a068f93 Backward Policy ID: c133005f-23bd-5a6b-7bb0-dbef710f524c Mode: GATEWAY Router ID: 2bdbafbf-f899-42af-b2ce-e21122ad1d1b.
Explanation	A firewall was modified.
Possible failure causes	· Invalid json format. · The tenant IDs for the firewall and the specified forward policy are different. · The tenant IDs for the firewall and the specified backward policy are different. · The tenant IDs for the firewall and the specified vRouter are different. · The tenant IDs for the firewall and the specified network resource are different. · The forward policy specified for the firewall doesn't exist. · The backward policy specified for the firewall doesn't exist. · The forward policy is already used by another firewall. · The backward policy is already used by another firewall. · The vRouter specified for the firewall doesn't exist. · The vRouter is already used by another firewall. · The type of the network resource specified for the firewall is not vFW. · The network resource specified for the firewall doesn't exist. · The number of firewalls bound to the resource exceeded the limit. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration deletion is in progress. · Configuration recovery is in progress. · The firewall service has not been found. · The configuration item doesn't exist.

Delete firewall

Keyword	DELETE_FW_OP
Message text	Deleted firewall $1.
Variable fields	$1: Name of the firewall.
Example	Deleted firewall fw.
Explanation	A firewall was deleted.
Possible failure causes	· Invalid UUID string: asd-+. · The configuration item is in use. · The configuration item doesn't exist. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration deletion is in progress. · Configuration recovery is in progress. · The firewall service has not been found.

Create IPS policy

Keyword	CREATE_IPSPOLICY_OP
Message text	Created IPS policy $1.
Variable fields	$1: Information about the IPS policy.
Example	Created IPS policy ID: 70dc3186-ac5b-4ba1-ac7f-7a27ef566efb Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: IPS Description: ips policy
Explanation	An IPS policy was added.
Possible failure causes	· No signature library is uploaded. · The tenant name is read only. · Invalid JSON format. · No tenant ID is specified. · The specified tenant doesn't exist. · The configuration item already exists. · The controller is not the active leader. · Configuration recovery is in progress. · The service has not been found.

Update IPS policy

Keyword	UPDATE_IPSPOLICY_OP
Message text	Updated IPS policy $1.
Variable fields	$1: Information about the IPS policy.
Example	Updated IPS policy ID: 70dc3186-ac5b-4ba1-ac7f-7a27ef566efb Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: IPS Description: ips policy
Explanation	An IPS policy was modified.
Possible failure causes	· The IPS policy ID can't be modified. · The tenant ID can't be modified. · The tenant name is read only. · Invalid JSON format. · The configuration item doesn't exist. · The predefined IPS policy can't be modified. · The controller is not the active leader. · Configuration recovery is in progress. · The service has not been found.

Delete IPS policy

Keyword	DELETE_IPSPOLICY_OP
Message text	Deleted IPS policy $1.
Variable fields	$1: Name of the IPS policy.
Example	Deleted IPS policy IPS.
Explanation	An IPS policy was deleted.
Possible failure causes	· The configuration item doesn't exist. · The controller is not the active leader. · Configuration recovery is in progress. · The service has not been found.

Create IPS template

Keyword	CREATE_IPSTEMPLATE_OP
Message text	Created IPS template $1.
Variable fields	$1: Information about the IPS template.
Example	Created IPS template ID: 70dc3186-ac5b-4ba1-ac7f-7a27ef566efb Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: IPS Description: ips template
Explanation	An IPS template was added.
Possible failure causes	· No signature library is uploaded. · The tenant name is read only. · The template type is read only. · Invalid JSON format. · No tenant ID is specified. · The specified tenant doesn't exist. · The configuration item already exists. · The controller is not the active leader. · Configuration recovery is in progress. · The service has not been found.

Update IPS template

Keyword	UPDATE_IPSTEMPLATE_OP
Message text	Updated IPS template $1.
Variable fields	$1: Information about the IPS template.
Example	Updated IPS template ID: 70dc3186-ac5b-4ba1-ac7f-7a27ef566efb Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: IPS Description: ips template
Explanation	An IPS template was modified.
Possible failure causes	· The IPS template ID can't be modified. · The tenant ID can't be modified. · The tenant name is read only. · The template type is read only. · Invalid JSON format. · The configuration item doesn't exist. · The predefined IPS template can't be modified. · The controller is not the active leader. · Configuration recovery is in progress. · The service has not been found.

Delete IPS template

Keyword	DELETE_IPSTEMPLATE_OP
Message text	Deleted IPS template $1.
Variable fields	$1: Name of the IPS template.
Example	Deleted IPS template IPS.
Explanation	An IPS template was deleted.
Possible failure causes	· The configuration item doesn't exist. · The controller is not the active leader. · Configuration recovery is in progress. · The service has not been found.

Upload IPS signature library from local device

Keyword	UPLOAD_IPSSIGNATURE_OP
Message text	Uploaded IPS signature library $1 from local device.
Variable fields	$1: Name of the IPS signature library.
Example	Uploaded IPS signature library V7-IPS-1.0.15.dat from local device.
Explanation	An IPS signature library file was uploaded from the local device to the SDN controller.
Possible failure causes	· Invalid IPS signature library file. · The controller is not the active leader. · Configuration recovery is in progress. · The service has not been found. · Uploading aborted because of abnormal firewall service.

Create AV policy

Keyword	CREATE_AVPOLICY_OP
Message text	Created AV policy $1.
Variable fields	$1: Information about the antivirus policy.
Example	Created AV policy ID: 70dc3186-ac5b-4ba1-ac7f-7a27ef566efb Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: AV Description: av policy
Explanation	An antivirus policy was added.
Possible failure causes	· No virus library is uploaded. · The tenant name is read only. · Invalid JSON format. · No tenant ID is specified. · The specified tenant doesn't exist. · The configuration item already exists. · The application library must be uploaded before the application exceptions are added. · The virus library must be uploaded before the virus exceptions are added. · The application exception is not included in the application library. · The virus exception is not included in the virus library. · The controller is not the active leader. · Configuration recovery is in progress. · The service has not been found.

Update AV policy

Keyword	UPDATE_AVPOLICY_OP
Message text	Updated AV policy $1.
Variable fields	$1: Information about the antivirus policy.
Example	Updated AV policy ID: 70dc3186-ac5b-4ba1-ac7f-7a27ef566efb Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: AV Description: av policy
Explanation	An antivirus policy was modified.
Possible failure causes	· The antivirus policy ID can't be modified. · The tenant ID can't be modified. · The tenant name is read only. · Invalid JSON format. · The configuration item doesn't exist. · The predefined antivirus policy can't be modified. · The application library must be uploaded before the application exceptions are added. · The virus library must be uploaded before the virus exceptions are added. · The application exception is not included in the application library. · The virus exception is not included in the virus library. · The controller is not the active leader. · Configuration recovery is in progress. · The service has not been found. · Invalid virus exceptions exist. · Invalid application exceptions exist.

Delete AV policy

Keyword	DELETE_AVPOLICY_OP
Message text	Deleted AV policy $1.
Variable fields	$1: Name of the antivirus policy.
Example	Deleted AV policy AV.
Explanation	An antivirus policy was deleted.
Possible failure causes	· The configuration item doesn't exist. · The controller is not the active leader. · Configuration recovery is in progress. · The service has not been found.

Create AV template

Keyword	CREATE_AVTEMPLATE_OP
Message text	Created AV template $1.
Variable fields	$1: Information about the antivirus template.
Example	Created AV template ID: 70dc3186-ac5b-4ba1-ac7f-7a27ef566efb Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: AV Description: av template
Explanation	An antivirus template was added.
Possible failure causes	· No virus library is uploaded. · The tenant name is read only. · The antivirus template type is read only. · Invalid JSON format. · No tenant ID is specified. · The specified tenant doesn't exist. · The configuration item already exists. · The application library must be uploaded before the application exceptions are added. · The virus library must be uploaded before the virus exceptions are added. · The application exception is not included in the application library. · The virus exception is not included in the virus library. · The controller is not the active leader. · Configuration recovery is in progress. · The service has not been found.

Update AV template

Keyword	UPDATE_AVTEMPLATE_OP
Message text	Updated AV template $1.
Variable fields	$1: Information about the antivirus template.
Example	Updated AV template ID: 70dc3186-ac5b-4ba1-ac7f-7a27ef566efb Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: AV Description: av template
Explanation	An antivirus template was modified.
Possible failure causes	· The antivirus template ID can't be modified. · The tenant ID can't be modified. · The tenant name is read only. · The antivirus template type is read only. · Invalid JSON format. · The configuration item doesn't exist. · The predefined antivirus template can't be modified. · The application library must be uploaded before the application exceptions are added. · The virus library must be uploaded before the virus exceptions are added. · The application exception is not included in the application library. · The virus exception is not included in the virus library. · The controller is not the active leader. · Configuration recovery is in progress. · The service has not been found. · Invalid virus exceptions exist. · Invalid application exceptions exist.

Delete AV template

Keyword	DELETE_AVTEMPLATE_OP
Message text	Deleted AV template $1.
Variable fields	$1: Name of the antivirus template.
Example	Deleted AV template AV.
Explanation	An antivirus template was deleted.
Possible failure causes	· The configuration item doesn't exist. · The controller is not the active leader. · Configuration recovery is in progress. · The service has not been found.

Upload virus library from local device

Keyword	UPLOAD_VIRUSLIBRARY_OP
Message text	Uploaded virus library $1 from local device.
Variable fields	$1: Name of the virus library.
Example	Uploaded virus library V7-AV-1.0.15.dat from local device.
Explanation	A virus library file was uploaded from the local device to the SDN controller.
Possible failure causes	· Invalid virus library file. · The controller is not the active leader. · Configuration recovery is in progress. · The service has not been found. · Uploading aborted because of abnormal firewall service.

Upload application library from local device

Keyword	UPLOAD_APPLIBRARY_OP
Message text	Uploaded application library $1 from local device.
Variable fields	$1: Name of the application library.
Example	Uploaded application library V7-APP-1.0.41.dat from local device.
Explanation	An application library file was uploaded from the local device to the SDN controller.
Possible failure causes	· Invalid application library file. · The controller is not the active leader. · Configuration recovery is in progress. · The service has not been found. · Uploading aborted because of abnormal firewall service.

LBaaS

This section contains load balancing messages.

Create load balancer

Keyword	CREATE_LB_OP
Message text	Created load balancer $1.
Variable fields	$1: Load balancer information.
Example	Created load balancer ID: 41e38478-da02-49e3-986e-6356ddd304f8 Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: 9 Description: Type: SERVER Pool ID: 4914ac1e-4acf-4966-b7de-c5c495751da9 Mode: GATEWAY Router ID: 5f96684a-5368-433c-bd26-158d351affd4 Status: DOWN.
Explanation	A load balancer was created.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · The configuration item already exists. · The tenant specified for the configuration item doesn't exist. · The pool specified for the load balancer doesn't exist. · The pool is already used by another the load balancer. · The tenant IDs for the load balancer and the specified pool are different. · The VIP address must belong to the subnet of the pool. · Only the SERVICE_CHAIN type load balancers support server pool list configuration. · The load balancers in the same VIP must have the same mode. · The subnets for the VIP and member are different.

Update load balancer

Keyword	UPDATE_LB_OP
Message text	Updated load balancer $1.
Variable fields	$1: Load balancer information.
Example	Updated load balancer ID: 41e38478-da02-49e3-986e-6356ddd304f8 Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: 9 Description: Type: SERVER Pool ID: 4914ac1e-4acf-4966-b7de-c5c495751da9 Mode: GATEWAY Router ID: 5f96684a-5368-433c-bd26-158d351affd4 Status: DOWN.
Explanation	A load balancer was modified.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · The configuration item doesn't exist. · The pool specified for the load balancer doesn't exist. · The pool is already used by another the load balancer. · The tenant IDs for the load balancer and the specified pool are different. · The VIP address must belong to the subnet of the pool. · Only the SERVICE_CHAIN type load balancers support server pool list configuration. · The subnets for the VIP and member are different.

Delete load balancer

Keyword	DELETE_LB_OP
Message text		Deleted load balancer $1.
Variable fields		$1: Load balancer name.
Example		Deleted load balancer lb70.
Explanation		A load balancer was deleted.
Possible failure causes		· The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · The configuration item doesn't exist. · The configuration item is in use.

Create VIP

Keyword	CREATE_VIRTUALIP_OP
Message text		Created VIP $1.
Variable fields		$1: VIP configuration information.
Example		Created VIP ID: ab8121f1-65b6-4709-8153-43695b83a187 Tenant ID: 00000000-0000-0000-0000-000000000000 Name: virtualip60 Description: Protocol: HTTPS Listener IDs: {e5c2996e-36d6-4e80-aa2b-deedac360468} Port ID: 09296b20-1f8d-4b17-9862-b920884e34dc Address: 60.0.0.90 Admin state up: true Status: DOWN.
Explanation		A VIP was created.
Possible failure causes		· The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · The configuration item already exists. · The tenant specified for the configuration item doesn't exist. · The IP address already exists. · The VIP address conflicts with the IP address of a vPort.

Update VIP

Keyword	UPDATE_VIRTUALIP_OP
Message text		Updated VIP $1.
Variable fields		$1: VIP configuration information.
Example		Updated VIP ID: ab8121f1-65b6-4709-8153-43695b83a187 Tenant ID: 00000000-0000-0000-0000-000000000000 Name: virtualip 60 Description: Protocol: HTTPS Listener IDs: {e5c2996e-36d6-4e80-aa2b-deedac360468} Port ID: 09296b20-1f8d-4b17-9862-b920884e34dc Address: 60.0.0.90 Admin state up: true Status: DOWN.
Explanation		A VIP was modified.
Possible failure causes		· The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · The configuration item doesn't exist. · The IP address already exists. · The VIP ID is read-only. · The VIP name is read-only. · The subnet ID is read-only. · The virtual port ID is read-only.

Delete VIP

Keyword	DELETE_VIRTUALIP_OP
Message text		Deleted VIP $1.
Variable fields		$1: VIP name.
Example		Deleted VIP virtualip60.
Explanation		A VIP was deleted.
Possible failure causes		· The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · The configuration item doesn't exist.

Create listener

Keyword	CREATE_LISTENER_OP
Message text		Created listener $1.
Variable fields		$1: Listener configuration information.
Example		Created listener ID: ab8121f1-65b6-4709-8153-43695b83a187 Tenant ID: 00000000-0000-0000-0000-000000000000 Name: listener60 Description: Protocol port: 6 VIP ID: ab8121f1-65b6-4709-8153-43695b83a121 Connection limit: 0 Admin state up: true Status: DOWN.
Explanation		A listener was deleted.
Possible failure causes		· The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · The configuration item already exists. · The tenant specified for the configuration item doesn't exist. · The tenant IDs for the listener and the specified VIP are different. · The port number is already used.

Update listener

Keyword	UPDATE_LISTENER_OP
Message text		Updated listener $1.
Variable fields		$1: Listener configuration information.
Example		Updated listener ID: ab8121f1-65b6-4709-8153-43695b83a187 Tenant ID: 00000000-0000-0000-0000-000000000000 Name: listener60 Description: Protocol port: 6 VIP ID: ab8121f1-65b6-4709-8153-43695b83a121 Connection limit: 0 Admin state up: true Status: DOWN.
Explanation		A listener was modified.
Possible failure causes		· The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · The configuration item doesn't exist. · The tenant IDs for the VIP and the specified listener are different.

Delete listener

Keyword	DELETE_LISTENER_OP
Message text		Deleted listener $1.
Variable fields		$1: Listener name.
Example		Deleted listener listener60.
Explanation		A listener was deleted.
Possible failure causes		· The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · The configuration item doesn't exist.

Create pool

Keyword	CREATE_POOL_OP
Message text	Created pool $1.
Variable fields	$1: Pool information.
Example	Created pool ID: 5ba4d32a-8373-423c-b1e9-78de52f0733d Tenant ID: 00000000-0000-0000-0000-000000000000 Name: pool70 Description: pool 70 Protocol: HTTP Listener ID : 00000000-0000-0000-0000-000000000011 Session persistence type: SOURCE_IP Session persistence cookie name: Status: DOWN.
Explanation	A pool was created.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · The configuration item already exists. · The tenant specified for the configuration item doesn't exist. · The listener specified for the pool doesn't exist. · The tenant IDs for the pool and the specified listener are different. · The subnet specified for the pool doesn't exist. · The tenant IDs for the pool and the specified subnet are different. · The health monitor specified for the pool doesn't exist. · The tenant IDs for the pool and the specified health monitor are different. · The listener ID must be specified. · The protocol types of the pool and the specified listener are different. · The listener is used by another pool.

Update pool

Keyword	UPDATE_POOL_OP
Message text	Updated pool $1.
Variable fields	$1: Pool information.
Example	Updated pool ID: 5ba4d32a-8373-423c-b1e9-78de52f0733d Tenant ID: 00000000-0000-0000-0000-000000000000 Name: pool70 Description: pool 70 Protocol: HTTP Listener ID : 00000000-0000-0000-0000-000000000011 Session persistence type: SOURCE_IP Session persistence cookie name Status: DOWN.
Explanation	A pool was modified.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · The configuration item doesn't exist. · The listener specified for the pool doesn't exist. · The tenant IDs for the pool and the specified listener are different. · The listener ID is read-only. · The subnet specified for the pool doesn't exist. · The tenant IDs for the pool and the specified subnet are different. · The health monitor specified for the pool doesn't exist. · The tenant IDs for the pool and the specified health monitor are different. · The VIP address must belong to the subnet of the pool.

Delete pool

Keyword	DELETE_POOL_OP
Message text		Deleted pool $1.
Variable fields		$1: Pool name.
Example		Deleted pool pool70.
Explanation		A pool was deleted.
Possible failure causes		· The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · The configuration item doesn't exist. · The configuration item is in use.

Create VIP

Keyword	CREATE_VIP_OP
Message text	Created VIP $1.
Variable fields	$1: Virtual server information.
Example	Created VIP ID: ab8121f1-65b6-4709-8153-43695b83a187 Tenant ID: 00000000-0000-0000-0000-000000000000 Name: vip60 Description: Protocol: HTTPS Pool ID: e5c2996e-36d6-4e80-aa2b-deedac360468 Port ID: 09296b20-1f8d-4b17-9862-b920884e34dc Address: 60.0.0.90 Protocol port: 6 Connection limit: 0 Session persistence type: SOURCE_IP Session persistence cookie name: Admin state up: true Status: DOWN.
Explanation	A virtual server was created.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · The configuration item already exists. · The tenant specified for the configuration item doesn't exist. · The protocol types of the VIP and the pool are different. · The pool is already used by another VIP. · The tenant IDs for the VIP and the specified pool are different. · The pool specified for the VIP doesn't exist. · The IP address is already used by another VIP. · The VIP address must belong to the subnet of the pool. · The VIP address conflicts with the IP address of a vPort or the subnets of the VIP address and member IP addresses belong to different virtual link layer networks.

Update VIP

Keyword	UPDATE_VIP_OP
Message text	Updated VIP $1.
Variable fields	$1: Virtual server information.
Example	Updated VIP ID: ab8121f1-65b6-4709-8153-43695b83a187 Tenant ID: 00000000-0000-0000-0000-000000000000 Name: vip60 Description: Protocol: HTTPS Pool ID: e5c2996e-36d6-4e80-aa2b-deedac360468 Port ID: 09296b20-1f8d-4b17-9862-b920884e34dc Address: 60.0.0.90 Protocol port: 6 Connection limit: 0 Session persistence type: SOURCE_IP Session persistence cookie name: Admin state up: true Status: DOWN.
Explanation	A virtual server was modified.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · The configuration item doesn't exist. · The protocol types of the VIP and the pool are different. · The pool is already used by another VIP. · The tenant IDs for the VIP and the specified pool are different. · The pool specified for the VIP doesn't exist. · The IP address is already used by another VIP. · The VIP address must belong to the subnet of the pool. · The VIP address conflicts with the IP address of a vPort or the subnets of the VIP address and member IP addresses belong to different virtual link layer networks.

Delete VIP

Keyword	DELETE_VIP_OP
Message text		Deleted VIP $1.
Variable fields		$1: Virtual server name.
Example		Deleted VIP vip60.
Explanation		A virtual server was deleted.
Possible failure causes		· The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · The configuration item doesn't exist.

Create member

Keyword	CREATE_MEMBER_OP
Message text	Created member $1.
Variable fields	$1: Real server information.
Example	Created member ID: 9f421f95-5772-4127-b8e4-47dfe5a7d43e Tenant ID: 00000000-0000-0000-0000-000000000000 Name: 9f421f95-5772-4127-b8e4-47dfe5a7d43e Pool ID: f8472b01-3aa2-4a6c-a292-80e7872ceca3 Subnet ID: f8472b01-3aa2-4a6c-a292-80e7872cec11 Address: 60.0.0.11 Protocol port: 2 Weight: 1 Admin state up: true Status: DOWN.
Explanation	A real server was created.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · The configuration item already exists. · The tenant specified for the configuration item doesn't exist. · The pool specified for the member doesn't exist. · The tenant IDs for the member and the specified pool are different. · The IP address is already used by another VIP. · The VIP address must belong to the subnet of the pool. · The vRouters for the member and the VIP are different. · The subnets for the VIP and member are different.

Update member

Keyword	UPDATE_MEMBER_OP
Message text	Updated member $1.
Variable fields	$1: Real server information.
Example	Updated member ID: 9f421f95-5772-4127-b8e4-47dfe5a7d43e Tenant ID: 00000000-0000-0000-0000-000000000000 Name: 9f421f95-5772-4127-b8e4-47dfe5a7d43e Pool ID: f8472b01-3aa2-4a6c-a292-80e7872ceca3 Subnet ID: f8472b01-3aa2-4a6c-a292-80e7872cec11 Address: 60.0.0.11 Protocol port: 2 Weight: 1 Admin state up: true Status: DOWN.
Explanation	A real server was modified.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · The configuration item doesn't exist. · The pool specified for the member doesn't exist. · The tenant IDs for the member and the specified pool are different. · The VIP address must belong to the subnet of the pool. · The pool ID is read-only. · The subnets for the VIP and member are different.

Delete member

Keyword	DELETE_MEMBER_OP
Message text		Deleted member $1.
Variable fields		$1: Real server IP address.
Example		Deleted member 60.0.0.11.
Explanation		A real server was deleted.
Possible failure causes		· The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · The configuration item doesn't exist.

Create health monitor

Keyword	CREATE_HEALTH_MONITOR_OP
Message text	Created health monitor $1.
Variable fields	$1: Health monitoring method information.
Example	Created health monitor ID: 0711c857-2729-41f2-b213-dc4e715bf9bd Tenant ID: 00000000-0000-0000-0000-000000000000 Name: hm Type: HTTPS Timeout: 11 Delay: 10 Max retries: 12 HTTP method: GET URL path: / Expected codes: 233 Status: DOWN.
Explanation	A health monitoring method was created.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · The configuration item already exists. · The tenant specified for the configuration item doesn't exist. · The tenant IDs for the health monitor and the specified pool are different. · The url path can not be specified when type is not HTTP or HTTPS. · The expected_data_type, expected_data, and expected_offset parameters are available only when the monitor type is HTTP or HTTPS. · The monitor port parameter is available only when the monitor type is TCP.

Update health monitor

Keyword	UPDATE_HEALTH_MONITOR_OP
Message text	Updated health monitor $1.
Variable fields	$1: Health monitoring method information.
Example	Updated health monitor ID: 0711c857-2729-41f2-b213-dc4e715bf9bd Tenant ID: 00000000-0000-0000-0000-000000000000 Name: hm Type: HTTPS Timeout: 11 Delay: 10 Max retries: 12 HTTP method: GET URL path: / Expected codes: 233 Status: DOWN.
Explanation	A health monitoring method was modified.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · The configuration item doesn't exist. · The expected_data_type, expected_data, and expected_offset parameters are available only when the monitor type is HTTP or HTTPS. · The monitor port parameter is available only when the monitor type is TCP.

Delete health monitor

Keyword	DELETE_HEALTH_MONITOR_OP
Message text		Deleted health monitor $1.
Variable fields		$1: Health monitoring method name.
Example		A health monitoring method was deleted.
Explanation		A health monitoring method was deleted.
Possible failure causes		· The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · The configuration item doesn't exist. · The configuration item is in use.

Bind health monitor

Keyword	BIND_HEALTH_MONITOR_OP
Message text	Bound health monitor: $1.
Variable fields	$1: UUID of the health monitoring method.
Example	Bound health monitor: ID: [380e1f64-4722-4039-8aec-af1643d10be6]
Explanation	A health monitoring method was bound to a server farm.
Possible failure causes	· Invalid license. · Invalid JSON format. · The service is disabled. · Configuration recovery is in progress. · The controller is not the active leader. · The operation requires the administrator privilege. · The configuration item doesn't exist. · The health monitor specified for the pool doesn't exist. · The tenant IDs for the pool and the specified health monitor are different.

Unbind health monitor

Keyword	UNBIND_HEALTH_MONITOR_OP
Message text	Unbound health monitor: $1.
Variable fields	$1: UUID of the health monitoring method.
Example	Unbound health monitor: ID: [380e1f64-4722-4039-8aec-af1643d10be6]
Explanation	A health monitoring method was unbound from a server farm.
Possible failure causes	· Invalid license. · Invalid JSON format. · The service is disabled. · Configuration recovery is in progress. · The controller is not the active leader. · The operation requires the administrator privilege. · The configuration item doesn't exist. · The health monitor specified for the pool doesn't exist.

NEM

This section contains carrier network messages.

Create VLAN-VXLAN mapping table

Keyword	CREATE_VLAN-VXLAN_OP
Message text	Created VLAN-VXLAN mapping table: $1
Variable fields	$1: VLAN-VXLAN mapping table information.
Example	Created VLAN-VXLAN mapping table: ID: [218b5f2f-e435-4365-a1ab-0eaa03b7fa19] Name: [table] VLAN-VXLAN mappings: [ 2--13 : 4--4 AssignmentOnly : false AccessMode : VLAN ]
Explanation	A VLAN-VXLAN mapping table was created.
Possible failure causes	· Invalid license. · Invalid JSON format. · The service is disabled. · Configuration recovery is in progress. · The controller is not the active leader. · The operation requires the administrator privilege. · Invalid name. · The VLAN ID is invalid or out of range. · Invalid VXLAN ID. · The VLAN-VXLAN mapping table already exists. · No name is specified. · No mapping exists in the VLAN-VXLAN mapping table. · Two same mappings exist in the VLAN-VXLAN mapping table. · The VLAN-VXLAN mappings overlap. · Unknown internal server error.

Update VLAN-VXLAN mapping table

Keyword	UPDATE_VLAN-VXLAN_OP
Message text	Updated VLAN-VXLAN mapping table: $1
Variable fields	$1: VLAN-VXLAN mapping table information.
Example	Updated VLAN-VXLAN mapping table: ID: [218b5f2f-e435-4365-a1ab-0eaa03b7fa19] Name: [table] VLAN-VXLAN mappings: [ 2--13 : 4--4 AssignmentOnly : false AccessMode : VLAN ]
Explanation	A VLAN-VXLAN mapping table was modified.
Possible failure causes	· Invalid license. · Invalid JSON format. · The service is disabled. · Configuration recovery is in progress. · The controller is not the active leader. · The operation requires the administrator privilege. · Invalid name. · The VLAN ID is invalid or out of range. · Invalid VXLAN ID. · No name is specified. · No mapping exists in the VLAN-VXLAN mapping table. · Two same mappings exist in the VLAN-VXLAN mapping table. · The VLAN-VXLAN mappings overlap. · The VLAN-VXLAN mapping table doesn't exist. · Unknown internal server error.

Delete VLAN-VXLAN mapping table

Keyword	DELETE_VLAN-VXLAN_OP
Message text	Deleted VLAN-VXLAN mapping table: $1
Variable fields	$1: VLAN-VXLAN mapping table name.
Example	Deleted VLAN-VXLAN mapping table: table
Explanation	A VLAN-VXLAN mapping table was deleted.
Possible failure causes	· Invalid license. · Invalid JSON format. · The service is disabled. · Configuration recovery is in progress. · The controller is not the active leader. · The operation requires the administrator privilege. · The VLAN-VXLAN mapping table is already bound to physical access devices. · The VLAN-VXLAN mapping table doesn't exist. · Unknown internal server error.

Bind VLAN-VXLAN mapping table

Keyword	BIND_VLAN-VXLAN_OP
Message text	Bound VLAN-VXLAN mapping table: $1
Variable fields	$1: Information for bindings between a VLAN-VXLAN mapping table and physical access devices.
Example	Bound VLAN-VXLAN mapping table: ID: [218b5f2f-e435-4365-a1ab-0eaa03b7fa19] Name: [table] Physical access device: [ c1a3e882-51ad-4847-8dbb-d7d972a5934f ]
Explanation	A VLAN-VXLAN mapping table was bound to physical access devices.
Possible failure causes	· Invalid license. · Invalid JSON format. · The service is disabled. · Configuration recovery is in progress. · The controller is not the active leader. · The operation requires the administrator privilege. · Invalid name. · The VLAN-VXLAN mapping table doesn't exist. · The physical access device doesn't exist. · The physical access device is already bound to a VLAN-VXLAN mapping table. · No physical access device ID list is specified for the VLAN-VXLAN mapping table. · The device type doesn't match. · Duplicate physical access device IDs. · Unknown internal server error.

Update VLAN-VXLAN mapping table binding

Keyword	UPDATE_VLAN-VXLAN_BINDING_OP
Message text	Updated VLAN-VXLAN mapping table binding: $1
Variable fields	$1: Information for bindings between a VLAN-VXLAN mapping table and physical access devices.
Example	Updated VLAN-VXLAN mapping table binding: ID: [218b5f2f-e435-4365-a1ab-0eaa03b7fa19] Name: [table] Physical access device: [ c1a3e882-51ad-4847-8dbb-d7d972a5934f ]
Explanation	The bindings between a VLAN-VXLAN mapping table and physical access devices were modified.
Possible failure causes	· Invalid license. · Invalid JSON format. · The service is disabled. · Configuration recovery is in progress. · The controller is not the active leader. · The operation requires the administrator privilege. · Invalid name. · The VLAN-VXLAN mapping table doesn't exist. · The physical access device doesn't exist. · The physical access device is already bound to a VLAN-VXLAN mapping table. · No physical access device ID list is specified for the VLAN-VXLAN mapping table. · The device type doesn't match. · Duplicate physical access device IDs. · Unknown internal server error.

Delete VLAN-VXLAN mapping table binding

Keyword	DELETE_VLAN-VXLAN_BINDING_OP
Message text	Deleted VLAN-VXLAN mapping table binding: $1
Variable fields	$1: VLAN-VXLAN mapping table name.
Example	Deleted VLAN-VXLAN mapping table binding: table
Explanation	The bindings between a VLAN-VXLAN mapping table and physical access devices were deleted.
Possible failure causes	· Invalid license. · The service is disabled. · Configuration recovery is in progress. · The controller is not the active leader. · The operation requires the administrator privilege. · The VLAN-VXLAN mapping table doesn't exist. · The binding doesn't exist.

Create gateway group

Keyword	CREATE_GWGROUP_OP
Message text	Created gateway group: $1
Variable fields	$1: Gateway group information.
Example	Created gateway group: ID: [741f1414-d71e-4775-acf9-d68bbb55e803] Name: [L3GW] MAC: [3c:8c:40:4e:dd:46] Description: [123] Type: [GROUPCGSR] Members: [ 5da35b42-1e37-4c3f-928b-0afc77fcfd34 ffd8176c-820a-4dc5-94a9-5f4c4fbff0c5 ] VTEP IP: [1.1.1.1] Connect mode: [VLAN] Firewall for only external traffic: [false]
Explanation	A gateway group was created.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · Invalid JSON format. · Unknown internal server error. · The gateway group already exists. · Invalid name. · Invalid parameter. · Invalid description. · Invalid IP address. · The gateway group's MAC address conflicts with the VM's MAC address.

Update gateway group

Keyword	UPDATE_GWGROUP_OP
Message text	Updated gateway group: $1
Variable fields	$1: Gateway group information.
Example	Updated gateway group: ID: [741f1414-d71e-4775-acf9-d68bbb55e803] Name: [L3GW] MAC: [3c:8c:40:4e:dd:46] Description: [123] Type: [GROUPCGSR] Members: [ 5da35b42-1e37-4c3f-928b-0afc77fcfd34 ] VTEP IP: [1.1.1.1] Connect mode: [VLAN] Firewall for only external traffic: [false]
Explanation	A gateway group was modified.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · Invalid JSON format. · Unknown internal server error. · Invalid description. · Invalid parameter. · The gateway group is in use. · The gateway group doesn't exist. · The gateway group's MAC address conflicts with the VM's MAC address.

Delete gateway group

Keyword	DELETE_GWGROUP_OP
Message text	Deleted gateway group: $1
Variable fields	$1: Gateway group name.
Example	Deleted gateway group: L3GW
Explanation	A gateway group was deleted.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The gateway group doesn't exist. · The gateway group is in use.

Create gateway group IP pool

Keyword	CREATE_GWGROUP_IPPOOL_OP
Message text	Created gateway group IP pool: $1
Variable fields	$1: Gateway group IP address pool configuration information.
Example	Created gateway group IP pool: IP pool ID: [b12059c8-4f72-4efd-af06-8707d836f275] IP pool name: [huha_lb] IP pool type: [TENANT_SUPPORT_LB] IP pool CIDR: [19.19.19.0/24] IP pool allocated: [false]
Explanation	A gateway group IP address pool was created.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · The operation requires the administrator privilege. · Invalid JSON format. · Invalid name. · The IP address pool is already used. · The IP address pool ID already exists. · The CIDR of the IP address pool is invalid. · Configuration recovery is in progress. · The IP address pool type is already exist. · The IP address pool name already exists. · The gateway address and network address must belong to the same network segment. · Unknown internal server error. · The network address overlaps with a network address in another IP address pool.

Update gateway group IP pool

Keyword	UPDATE_GWGROUP_IPPOOL_OP
Message text	Updated gateway group IP pool: $1
Variable fields	$1: Gateway group IP address pool configuration information.
Example	Updated gateway group IP pool: IP pool ID: [4272f686-1faf-4587-b7a2-2f68246666e2] IP pool name: [1222] IP pool type: [NGFW_MANAGE] IP pool CIDR: [10.1.1.0/24] IP pool nexthop: [10.0.0.254] IP pool allocated: [false]
Explanation	A gateway group IP address pool was modified.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · The operation requires the administrator privilege. · Invalid name. · Invalid JSON format. · The CIDR of the IP address pool is invalid. · The IP address pool name already exists. · The IP address pool is already used. · Unknown internal server error. · The network address overlaps with a network address in another IP address pool.

Delete gateway group IP pool

Keyword	DELETE_GWGROUP_IPPOOL_OP
Message text	Deleted gateway group IP pool: $1
Variable fields	$1: Gateway group IP address pool name.
Example	Deleted gateway group IP pool: 1222
Explanation	A gateway group IP address pool was deleted.
Possible failure causes	· Invalid license. · Invalid JSON format. · The service is disabled. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The IP address pool doesn't exist. · The IP address pool is already used. · Unknown internal server error.

Create gateway group VLAN range

Keyword	CREATE_GWGROUP_VLAN_RANGE_OP
Message text	Created gateway group VLAN range: $1
Variable fields	$1: Gateway group VLAN range configuration information.
Example	Created gateway group VLAN range: VLAN range ID: [445dd33e-3b27-44a5-b7f1-c6fb0a859311] VLAN range name: [newRange] Start VLAN: [11] End VLAN: [4011] VLAN allocated: [false]
Explanation	A VLAN range was created for the gateway group.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · The operation requires the administrator privilege. · Invalid JSON format. · Invalid name. · The VLAN range is already used. · The VLAN range ID already exists. · The VLAN range name already exists. · The VLAN range overlaps with another one. · The VLAN ID is invalid or out of range. · Configuration recovery is in progress. · Unknown internal server error.

Update gateway group VLAN range

Keyword	UPDATE_GWGROUP_VLAN_RANGE_OP
Message text	Updated gateway group VLAN range: $1
Variable fields	$1: Gateway group VLAN range configuration information.
Example	Updated gateway group VLAN range: VLAN range ID: [8688051f-5095-4b27-93c1-89922ff9b0b6] VLAN range name: [newRange] Start VLAN: [4020] End VLAN: [4050] VLAN allocated: [false]
Explanation	The VLAN range was modified for the gateway group.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · The operation requires the administrator privilege. · Invalid JSON format. · The VLAN ID is invalid or out of range. · Invalid name. · The VLAN range is already used. · The VLAN range doesn't exist. · Unknown internal server error.

Delete gateway group VLAN range

Keyword	DELETE_GWGROUP_VLAN_RANGE_OP
Message text	Deleted gateway group VLAN range: $1
Variable fields	$1: Gateway group VLAN range name.
Example	Deleted gateway group VLAN range: newRange
Explanation	The VLAN range for the gateway group was deleted.
Possible failure causes	· Invalid license. · Invalid JSON format. · The service is disabled. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The VLAN range doesn't exist. · The VLAN range is already used. · Unknown internal server error.

Create physical NE

Keyword	CREATE_PHYNE_OP
Message text	Created physical NE: $1
Variable fields	$1: Physical NE information.
Example	Created physical NE: NE ID: [f10dbcef-b96a-48ad-8613-47fc7fe9f4e8] NE name: [12] Description: [1111] NE type: [L3GW] NETCONF username: [gao] NETCONF password: [******] Management IP: [97.0.1.12] Provider type: [PHY_DEVICE] Priority region ID: [fdd9f2d3-d2b2-4afe-942f-e6943b54e259] Priority region name: [region] Reserved tunnel ID: [256] Supporting autoconfiguration: [true] Supporting VTEP: [true] Service migration: [false] PreCfgVxlanService: [false] OpenflowPermitPort: [false] PreStatVxlanService: [false] Region ID: [fdd9f2d3-d2b2-4afe-942f-e6943b54e259] Region name: [region] NE status: [INACTIVE] Inactive reason: [DEVICE_INACTIVE_REASON_OPENFLOWLINK_DOWN]
Explanation	A physical NE was created.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · Invalid JSON format. · Unknown internal server error. · Invalid name. · The NE ID already exists. · The NE name already exists. · The management IP address already exists. · Invalid description. · Invalid parameter. · The gateway group doesn't exist. · Physical gateway service devices can be bound only to BIND_PHY type gateway groups. · The gateway group is already bound to a gateway service device. · Invalid IP address. · The VTEP IP already exists. · The NETCONF username or password is not configured. · Invalid NETCONF username. · Invalid NETCONF password. · The VSM service is disabled. · Invalid VDS ID. · The preferred region doesn't exist. · Invalid tunnel ID. · The number of physical NEs exceeds the limit of the overlay hardware entity license.

Update physical NE

Keyword	UPDATE_PHYNE_OP
Message text	Updated physical NE: $1
Variable fields	$1: Physical NE information.
Example	Updated physical NE: NE ID: [f10dbcef-b96a-48ad-8613-47fc7fe9f4e8] NE name: [12] Description: [1111] NE type: [L3GW] NETCONF username: [ gao] NETCONF password: [ ******] Management IP: [ 97.0.1.12] Provider type: [ PHY_DEVICE] Priority region ID: [fdd9f2d3-d2b2-4afe-942f-e6943b54e259] Priority region name: [region] Reserved tunnel ID: [ 256] Supporting autoconfiguration: [ true] Supporting VTEP: [true] Service migration: [ false] PreCfgVxlanService: [false] OpenflowPermitPort: [false] PreStatVxlanService: [false] Region ID: [fdd9f2d3-d2b2-4afe-942f-e6943b54e259] Region name: [region] NE status: [ INACTIVE] Inactive reason: [ DEVICE_INACTIVE_REASON_OPENFLOWLINK_DOWN]
Explanation	A physical NE was modified.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · Invalid JSON format. · Unknown internal server error. · The NE doesn't exist. · Invalid description. · Invalid parameter. · The gateway group doesn't exist. · Physical gateway service devices can be bound only to BIND_PHY type gateway groups. · The gateway group is already bound to a gateway service device. · Invalid IP address. · The VTEP IP already exists. · Invalid NETCONF username. · Invalid NETCONF password.

Delete physical NE

Keyword	DELETE_PHYNE_OP
Message text	Deleted physical NE: $1
Variable fields	$1: Physical NE name.
Example	Deleted physical NE: 12
Explanation	A physical NE was deleted.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The NE doesn't exist. · The NE is migrating services.

Start migration on physical gateway

Keyword	START_MIGRATION_PHYGW_OP
Message text	Started migration on physical gateway: $1
Variable fields	$1: Physical gateway ID.
Example	Started migration on physical gateway: f10dbcef-b96a-48ad-8613-47fc7fe9f4e8
Explanation	A service migration was started on a physical gateway.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The device doesn't exist. · The physical gateway device is inactive. · The device is migrating services.

Complete migration on physical gateway

Keyword	COMPLETE_MIGRATION_PHYGW_OP
Message text	Completed migration on physical gateway: $1
Variable fields	$1: Physical gateway ID.
Example	Completed migration on physical gateway: f10dbcef-b96a-48ad-8613-47fc7fe9f4e8
Explanation	Service migration on a physical gateway completed.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The device doesn't exist. · Only physical gateway devices support migration. · The device has already completed migration.

Create NETCONF default user

Keyword	CREATE_NETCONF_DEFAULT_USER_OP
Message text	Created NETCONF default user: $1
Variable fields	$1: NETCONF default user information.
Example	Created NETCONF default user: Username: [admin] Password: [******]
Explanation	A NETCONF default user was created.
Possible failure causes	· Invalid license. · The service is disabled. · Invalid parameter. · Invalid JSON format. · Configuration recovery is in progress. · The controller is not the active leader. · The operation requires the administrator privilege.

Create third party NE

Keyword	CREATE_THIRD_PARTY_NE_OP
Message text	Created third party NE: $1
Variable fields	$1: Third-party NE information.
Example	Created third party NE: ID: [8032909d-47a1-4715-90af-5153ffe39899] Name: [IPS1] Description: [thirdPartyIPS] Access device ID: [8032909d-47a1-4715-90af-5153ffe39811] Access device name: [6800] Access device VTEP IP: [12.1.1.1] Ingress port ID: [151] Egress port ID: [153] VLAN of ingress port: [100] VLAN of egress port: [100]
Explanation	A third-party NE was created.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · Invalid JSON format. · Unknown internal server error. · Invalid name. · Invalid description. · Invalid parameter. · The number of virtual service nodes exceeds the license limit. · The service chain license is not available. · The ingress port doesn't exist. · The egress port doesn't exist. · Invalid VLAN ID of the ingress port. · Invalid VLAN ID of the egress port. · Invalid ingress port ID. · Invalid egress port ID. · The ID of the third party NE already exists. · The name of the third party NE already exists. · The IDs of the third party NE and physical access device must be different. · The ingress port is already used. · The egress port is already used. · The name of the physical access device is read only. · The VTEP IP of the physical access device is read only.

Delete third party NE

Keyword	DELETE_THIRD_PARTY_NE_OP
Message text	Deleted third party NE: $1
Variable fields	$1: Name of the third-party NE.
Example	Deleted third party NE: IPS1
Explanation	A third-party NE was deleted.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The third party NE doesn't exist.

Configure reserved option

Keyword	CONFIGURE_RESERVE_OPTION_OP
Message text	Configured reserved option: $1
Variable fields	$1: Value of the reserved option.
Example	Configured reserved option: Reserved option: [true]
Explanation	The reserved option was configured. The values for the reserved option are as follows: · true—Enables the reserved option. The physical gateway can advertise overlay subnet routes through BGP. · false—Disables the reserved option. The physical gateway cannot advertise overlay subnet routes through BGP.
Possible failure causes	· Invalid license. · The service is disabled. · Invalid JSON format. · Configuration recovery is in progress. · The controller is not the active leader. · The operation requires the administrator privilege. · Unknown internal server error.

Create address pool

Keyword	CREATE_ADDRPOOL_OP
Message text	Created address pool: $1
Variable fields	$1: Address pool information.
Example	Created address pool: Address pool ID: [aa68bc06-8e30-468d-a805-d4f48952c646] Address pool name: [a] Start IP address: [10.1.1.1] End IP address: [10.1.1.100] IP address allocated: [false]
Explanation	A VTEP address pool was created.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · The operation requires the administrator privilege. · Invalid JSON format. · Configuration recovery is in progress. · The address pool ID is already used. · No IP address is specified for the address pool. · Invalid name. · The address pool name is already used. · The start IP address is higher than the end IP address. · The address pool contains special or reserved IP addresses. · The IP range of the address pool overlaps with that of another address pool. · Unknown internal server error.

Update address pool

Keyword	UPDATE_ADDRPOOL_OP
Message text	Updated address pool: $1
Variable fields	$1: Address pool information.
Example	Updated address pool: Address pool ID: [aa68bc06-8e30-468d-a805-d4f48952c646] Address pool name: [a] Start IP address: [10.1.1.1] End IP address: [10.1.1.100] IP address allocated: [false]
Explanation	A VTEP address pool was updated.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · The operation requires the administrator privilege. · Invalid JSON format. · Configuration recovery is in progress. · The address pool doesn't exist. · Invalid name. · The address pool name is already used. · The start IP address is higher than the end IP address. · The address pool contains special or reserved IP addresses. · The address pool is in use. · The IP range of the address pool overlaps with that of another address pool. · Unknown internal server error.

Delete address pool

Keyword	DELETE_ADDRPOOL_OP
Message text	Deleted address pool: $1
Variable fields	$1: Address pool name.
Example	Deleted address pool: a
Explanation	A VTEP address pool was deleted.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The address pool doesn't exist. · The address pool is in use. · Unknown internal server error.

Add resource

Keyword	ADD_RESOURCE_OP
Message text	Added resource: $1
Variable fields	$1: Resource information.
Example	Added resource: Resource ID: [0e447abc-9716-4171-902c-ecb8a090cebb] Resource name: [group_7786138066] Tenant ID: [ffffffff-0000-0000-0000-000000000001] Tenant name: [default] Resource feature: [GW] Resource family: [PHY_DEV] Supporting VTEP: [true] Supporting share: [false] Supporting HA: [true] Auto Share: 1 NF list: [ { NF ID: [6e9a235c-c20d-415b-89c1-4c58b5f60100] NF name: [group] NF management IP: [212.2.248.5] } ]
Explanation	A resource was added.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · Invalid JSON format. · The resource already exists. · Invalid parameter. · Unknown internal server error. · The number of virtual service nodes exceeds the license limit. · The service chain license is not available. · The VNFM is not configured. · Invalid name. · The tenant doesn't exist. · The network function ID is already used. · The management IP address is already used. · No network function list is specified for the physical resource. · The gateway group doesn't exist. · The address pool is not configured or doesn't have enough assignable IP addresses. · Duplicate network function IDs. · Duplicate management IP addresses. · Failed to get resources from the VNFM. · No physical gateway resource is configured for the tenant. · A physical gateway resource is already configured for the tenant. · The resource family conflicts with the gateway network type. · The physical gateway resource has only one network function node. · Physical gateway devices can't be separately used as resources. · No physical gateway service node is bound to the gateway group. · Physical gateway service nodes can't be used as resources. · Physical access devices can't be used as resources. · No physical gateway device exists in the gateway group. · The tenant service is disabled. · No permission to add the resource. · Invalid maximum shares.

Delete resource

Keyword	DELETE_RESOURCE_OP
Message text	Deleted resource: $1
Variable fields	$1: Resource name.
Example	Deleted resource: group_7786138066
Explanation	A resource was deleted.
Possible failure causes	· Invalid license. · The service is disabled. · Invalid parameter. · Invalid JSON format. · Configuration recovery is in progress. · The controller is not the active leader. · The operation requires the administrator privilege. · Unknown internal server error. · The VNFM is not configured. · The resource is already bound to the extranet. · The resource doesn't exist. · The virtual gateway resource still exists. · No permission to delete the resource. · A vPort or APP cluster VIP on the vRouter bound to the resource has been bound to a floating IP with a protocol specified.

Configure VNFM

Keyword	CONFIGURE_VNFM_OP
Message text	Configured VNFM: $1
Variable fields	$1: VNF Manager information.
Example	Configured VNFM: IP address: [3.3.3.3] Port number: [8080] Username: [admin] Password: [******]
Explanation	A VNF Manager was specified or modified.
Possible failure causes	· Invalid license. · The service is disabled. · Invalid parameter. · Invalid JSON format. · Configuration recovery is in progress. · The controller is not the active leader. · The operation requires the administrator privilege. · The port number is not in the range of 0 to 65535. · The VNFM address or port is incorrect. · The VNFM username or password is incorrect. · Unknown internal server error.

Configure gateway network

Keyword	CONFIGURE_GWNETWORK_OP
Message text	Configured gateway network: $1
Variable fields	$1: Gateway network information.
Example	Configured gateway network: Tenant ID: [ffffffff-0000-0000-0000-000000000001] Gateway network type: [GROUP] Status: [UNUSABLE]
Explanation	The gateway mode for the gateway group was specified.
Possible failure causes	· Invalid license. · The service is disabled. · Invalid parameter. · Invalid JSON format. · Configuration recovery is in progress. · The controller is not the active leader. · The operation requires the administrator privilege. · The tenant doesn't exist. · The gateway network type is already specified for the tenant. · No permission to specify the gateway network for the tenant. · Unknown internal server error.

Update gateway network

Keyword	UPDATE_GWNETWORK_OP
Message text	Updated gateway network: $1
Variable fields	$1: Gateway network information.
Example	Updated gateway network: Tenant ID: [ffffffff-0000-0000-0000-000000000001] Gateway network type: [GROUP] Status: [UNUSABLE]
Explanation	The gateway mode for the gateway group was modified.
Possible failure causes	· Invalid license. · The service is disabled. · Invalid parameter. · Invalid JSON format. · Configuration recovery is in progress. · The controller is not the active leader. · The operation requires the administrator privilege. · The tenant doesn't exist. · Resources are already allocated for the tenant. · No permission to modify the gateway network for the tenant. · Unknown internal server error.

Bind router to gateway

Keyword	BIND_ROUTER_GW_OP
Message text	Router bound to gateway: $1
Variable fields	$1: Virtual router ID.
Example	Router bound to gateway: aa68bc06-8e30-468d-a805-d4f48952c646
Explanation	A virtual router was bound to a gateway.
Possible failure causes	· Invalid license. · The service is disabled. · Invalid parameter. · Invalid JSON format. · Configuration recovery is in progress. · The controller is not the active leader. · The operation requires the administrator privilege. · The virtual router doesn't exist. · No gateway network type is specified for the tenant. · The gateway is unavailable. · The virtual router is already bound to a gateway resource. · No permission to bind the virtual router to the gateway. · Unknown internal server error.

Configure data synchronization

Keyword	CONFIG_DATA_SYNCHRONIZATION_OP
Message text	Configured data synchronization: DATA_SYNCHRONIZATION_SWITCH: [$1]
Variable fields	$1: Data synchronization policy. · On. · Off. · Reserve extra configuration.
Example	Configured data synchronization: DATA_SYNCHRONIZATION_SWITCH: [On]
Explanation	A data synchronization operation was performed on the global settings page.
Possible failure causes	· Invalid license. · The service is disabled. · Invalid parameter. · Invalid JSON format. · Configuration recovery is in progress. · The controller is not the active leader. · The operation requires the administrator privilege.

Start data synchronization on NE

Keyword	START_DATA_SYNCHRONIZATION_OP
Message text	Started data synchronization on NE: $1
Variable fields	$1: Physical NE ID.
Example	Started data synchronization on NE: 28424135-36f5-4dde-ad2e-29580411de8d
Explanation	A physical NE was triggered manually to synchronize data.
Possible failure causes	· Invalid license. · The service is disabled. · The device doesn't exist. · The physical gateway device is inactive. · Configuration recovery is in progress. · The controller is not the active leader. · The operation requires the administrator privilege.

Delete NE VXLAN tunnels

Keyword	DELETE_NE_TUNNEL_OP
Message text	Deleted NE VXLAN tunnels: NE ID: $1 Tunnel list: $2
Variable fields	$1: NE ID. $2: VXLAN tunnel list.
Example	Deleted NE VXLAN tunnels: NE ID: 28424135-36f5-4dde-ad2e-29580411de8d Tunnel list: [ { Source IP: 98.0.57.16 Destination IP: 6.6.6.3 } ]
Explanation	The VXLAN tunnel settings on the specified NE were removed from the memory of the controller. The operation does not delete the VXLAN tunnel settings from the NE.
Possible failure causes	· Invalid license. · The service is disabled. · The NE doesn't exist. · Configuration recovery is in progress. · The controller is not the active leader. · The operation requires the administrator privilege. · Invalid JSON format. · Unknown internal server error.

NGFWM

This section contains NGFW manager messages.

Add device

Keyword	ADD_DEVICE_OP
Message text	Added device: $1
Variable fields	$1: Device information.
Example	Added device: ID: 8dfb8b46-50d9-46c1-87c4-7aac7976ef5b Name: device1 IP: 192.168.34.15 Port: 832 Username: admin Max. number of contexts: 64
Explanation	A device was added.
Possible failure causes	· The device name already exists. · Invalid device port. · Invalid username. · Invalid password. · Invalid device name. · The IP address is used by a device. · Invalid IP address. · The device doesn't exist. · The NGFWM service is not started. · Server processing error. · Invalid JSON format. · The device is unreachable or the username or password is incorrect.

Update device

Keyword	UPDATE_DEVICE_OP
Message text	Updated device: $1
Variable fields	$1: Device information.
Example	Updated device: ID: 8dfb8b46-50d9-46c1-87c4-7aac7976ef5b Name: device1 IP: 192.168.34.15 Port: 832 Username: admin Max. number of contexts: 64
Explanation	A device was modified.
Possible failure causes	· The max. context number cannot be smaller than the number of contexts existing on the device. · The max. context number must be greater than 0. · The resource doesn't exist. · The NGFWM service is not started. · Server processing error. · Invalid JSON format.

Delete device

Keyword	DELETE_DEVICE_OP
Message text	Deleted device: $1
Variable fields	$1: Device name.
Example	Deleted device: DeviceName
Explanation	A device was deleted.
Possible failure causes	· The NGFWM service is not started. · Server processing error. · The resource doesn't exist. · Operation failed. Delete the contexts on the device first.

Create template

Keyword	CREATE_TEMPLATE_OP
Message text	Created template: $1
Variable fields	$1: Template information.
Example	Created template: ID: 8dfb8b46-50d9-46c1-87c4-7aac7976ef5b Name: F1000tmp108 Device name: device1 Security engine group ID: 3 Resource pool name: FW1 Template type: GatewayGroupFW Interface list: [ { Interface name: GigabitEthernet1/0/1 Interface type: Management } { Interface name: GigabitEthernet1/0/3 Interface type: Downlink } { Interface name: GigabitEthernet1/0/2 Interface type: Uplink } ] Extend setting: ip vpn-instance external_vpn ip vpn-instance external_vpn ospf 1 vpn-instance external_vpn import-route direct import-route static area 0.0.0.0 interface GigabitEthernet1/0/2 ip binding vpn-instance external_vpn ospf 1 area 0.0.0.0 ip route-static 0.0.0.0 0 1.2.2.254 interface loopback 2 ip binding vpn-instance external_vpn security-zone name SEC_ZONE_DEFAULT import interface GigabitEthernet1/0/1 Object-policy ip SEC_POLICY_DEFAULT rule 0 pass security-zone intra-zone default permit zone-pair security source Any destination Any object-policy apply ip SEC_POLICY_DEFAULT session synchronization enable nat port-block synchronization enable ipsec redundancy enable
Explanation	A template was created.
Possible failure causes	· Invalid template name. · The template name already exists. · Invalid parameter. · No available device. · Invalid security engine group ID. · Invalid resource pool name. · The security engine group is not bound to the resource pool. · Invalid interface name. · The NGFWM service is not started. · Server processing error. · Invalid JSON format

Delete template

Keyword	DELETE_TEMPLATE_OP
Message text	Deleted template: $1
Variable fields	$1: Template name.
Example	Deleted template: TemplateName
Explanation	A template was deleted.
Possible failure causes	· The NGFWM service is not started. · Server processing error. · The resource doesn't exist.

Create context

Keyword	CREATE_CONTEXT_OP
Message text	Created context: $1
Variable fields	$1: Context information.
Example	Created context: Name: context1 Device name: device1 Resource pool name: FW Template type: GatewayGroupFW Description: XXXXX CPU weight: 2 Disk: 1000 Memory: 2000 Username: default Interface list: [ { Interface name: GigabitEthernet1/0/1 Interface type: Management IP: 1.2.3.3 Mask: 255.255.0.0 } { Interface name: GigabitEthernet1/0/3 Interface type: Downlink IP: 1.3.30.5 Mask: 255.255.0.0 } { Interface name: GigabitEthernet1/0/2 Interface type: Uplink IP: 1.2.30.5 Mask: 255.255.0.0 } ]
Explanation	A context was created.
Possible failure causes	· Invalid context name. · The context name already exists. · The context interface name and type are required. · The IP address and mask must be both configured. · Failed to assign resources to the context by using NETCONF. · Failed to get information of the device where the context resides. · The CPU weight of the context must be in the range of 1 to 10. · The disk of the context must be in the range of 1 to 999999999. · The memory of the context must be in the range of 1 to 999999999. · The disk size can’t exceed the disk size of the security engine where the context resides. · The memory size can’t exceed the memory size of the security engine where the context resides. · Invalid parameter. · Server processing error. · The NGFWM service is not started. · Invalid JSON format. · The number of contexts on all devices in the resource pool has reached the upper limit. · Failed to create a context by NETCONF.

Update context

Keyword	UPDATE_CONTEXT_OP
Message text	Updated context: $1
Variable fields	$1: Context information.
Example	Updated context: Name: context1 Device name: device1 Resource pool name: FW Template type: GatewayGroupFW Description: XXXXX CPU weight: 2 Disk: 1000 Memory: 2000 Username: default Interface list: [ { Interface name: GigabitEthernet1/0/1 Interface type: Management IP: 1.2.3.3 Mask: 255.255.0.0 } { Interface name: GigabitEthernet1/0/2 Interface type: Uplink IP: 1.2.30.5 Mask: 255.255.0.0 } ]
Explanation	A context was updated.
Possible failure causes	· The NGFWM service is not started. · Server processing error. · The resource doesn't exist. · Failed to assign resources to the context by using NETCONF. · Failed to get information of the device where the context resides. · The CPU weight of the context must be in the range of 1 to 10. · The disk of the context must be in the range of 1 to 999999999. · The memory of the context must be in the range of 1 to 999999999. · The disk size can’t exceed the disk size of the security engine where the context resides. · The memory size can’t exceed the memory size of the security engine where the context resides. · The device where the context resides is unreachable or the username or password is incorrect. · Failed to modify a context by NETCONF.

Delete context

Keyword	DELETE_CONTEXT_OP
Message text	Deleted context: $1
Variable fields	$1: Context name.
Example	Deleted context: aa
Explanation	A context was deleted.
Possible failure causes	· The NGFWM service is not started. · Server processing error. · The resource doesn't exist.

Create resource pool

Keyword	CREATE_RESOURCE_POOL_OP
Message text	Created resource pool: $1
Variable fields	$1: Resource pool information.
Example	Created resource pool: Name: FW1 Type: FW Device list: [ { Device name: M9K Security engine group ID: 1 } ]
Explanation	A resource pool was created.
Possible failure causes	· The NGFWM service is not started. · Server processing error. · The resource pool name already exists. · The context default user must be configured. · Invalid resource pool name. · Invalid device name. · The device bound to the resource pool doesn't exist. · Invalid JSON format.

Update resource pool

Keyword	UPDATE_RESOURCE_POOL_OP
Message text	Updated resource pool: $1
Variable fields	$1: Resource pool information.
Example	Updated resource pool: Name: FW1 Type: FW Device list: [ { Device name: M9K Security engine group ID: 1 } ]
Explanation	A resource pool was modified.
Possible failure causes	· The NGFWM service is not started. · Server processing error. · The resource pool name already exists. · The context default user must be configured. · Invalid resource pool name. · Invalid device name. · The device bound to the resource pool doesn't exist. · Invalid JSON format. · Can't unbind the security engine group from the resource pool because the security engine group has contexts.

Delete resource pool

Keyword	DELETE_RESOURCE_POOL_OP
Message text	Deleted resource pool: $1
Variable fields	$1: Resource pool name.
Example	Deleted resource pool: aa
Explanation	A resource pool was deleted.
Possible failure causes	· The NGFWM service is not started. · Server processing error. · The resource doesn't exist. · Can't delete the resource pool because the resource pool has contexts.

Set default user

Keyword	SET_DEFAULT_USER_OP
Message text	Set default user: $1
Variable fields	$1: Context default user information.
Example	Set default user: Username: admin
Explanation	The context default username and password were set.
Possible failure causes	· The NGFWM service is not started. · Server processing error. · Invalid username. · Invalid password. · Invalid JSON format.

ServiceChain

This section contains service chain messages.

Create service chain

Keyword	CREATE_SC_OP
Message text	Created service chain $1
Variable fields	$1: Service chain information.
Example	Created service chain id: 7fda0d76-9a0a-4129-bc53-31e3b215f854 tenant id: ffffffff-0000-0000-0000-000000000001 name: sc1 base: source context: name: any flag: ANY destination context: name: external flag: EXTERNAL source port: 0 destination port: 0 protocol: HTTP service nodes: type: FW service id: a3645da8-a8d3-4dce-887f-87f310dc662a provider id: 5236ccde-8156-43df-9825-db2473877782 resource id: 2758558b-0a9c-4bdd-bee7-85149c2f0c82 management ip: 98.0.0.27 vtep IP: 10.0.0.3 service name: fw1 status: ACTIVE service path id: 1
Explanation	A service chain was created.
Possible failure causes	· The firewall service has not been found. · The load balancer service has not been found. · Configuration recovery is in progress. · The controller is not the active leader. · The operation requires the administrator privilege. · The service chain already exists. · The specified context doesn't exist. · The specified tenant doesn't exist. · The service instance doesn't exist. · The tenant IDs for the service chain and the specified service instance are different. · The mode of the service instance is not SERVICE_CHAIN. · The tenant IDs for the service chain and the specified source or destination context are different. · The source and destination contexts are already used by another service chain. · The types of the source and destination contexts can't both be external. · The service instance is already used by another service chain. · Only one firewall service instance is allowed in a service chain. · Only one loadbalancer service instance is allowed in a service chain.

Delete service chain

Keyword	DELETE_SC_OP
Message text	Deleted service chain $1
Variable fields	$1: Name of the service chain.
Example	Deleted service chain sc1
Explanation	A service chain was deleted.
Possible failure causes	· The service of the service chain has not been found. · Configuration recovery is in progress. · The controller is not the active leader. · The operation requires the administrator privilege. · The configuration item doesn't exist.

Update service chain

Keyword	UPDATE_SC_OP
Message text	Updated service chain $1
Variable fields	$1: Service chain information.
Example	Updated service chain id: 7fda0d76-9a0a-4129-bc53-31e3b215f854 tenant id: ffffffff-0000-0000-0000-000000000001 name: sc1 base: source context: name: any flag: ANY destination context: name: external flag: EXTERNAL source port: 0 destination port: 0 protocol: HTTP service nodes: type: FW service id: a3645da8-a8d3-4dce-887f-87f310dc662a provider id: 5236ccde-8156-43df-9825-db2473877782 resource id: 2758558b-0a9c-4bdd-bee7-85149c2f0c82 management ip: 98.0.0.27 vtep IP: 10.0.0.3 service name: fw1 status: ACTIVE service path id: 1
Explanation	A service chain was modified.
Possible failure causes	· The service of the service chain has not been found. · Configuration recovery is in progress. · The controller is not the active leader. · The operation requires the administrator privilege. · The configuration item doesn't exist. · The specified context doesn't exist. · The service instance doesn't exist. · The tenant IDs for the service chain and the specified service instance are different. · The mode of the service instance is not SERVICE_CHAIN. · The tenant IDs for the service chain and the specified source or destination context are different. · The source and destination contexts are already used by another service chain. · The types of the source and destination contexts can't both be external. · The service instance is already used by another service chain. · Only one firewall service instance is allowed in a service chain. · Only one loadbalancer service instance is allowed in a service chain.

Create context

Keyword	CREATE_CONTEXT_OP
Message text	Created context $1
Variable fields	$1: Context information.
Example	Created context id: 764a2ebe-eb47-43f7-98f3-e492b7b8ebeb tenant id: ffffffff-0000-0000-0000-000000000001 name: net1 context base: type: NETWORK networks: e3672c88-04db-4c85-bd1c-3e8b869c94b3 53b5199d-7181-41f6-8f8a-4637603a9e04 manualMap: tenant name: default in chain: false
Explanation	A context was created.
Possible failure causes	· The service of the service chain has not been found. · Configuration recovery is in progress. · The controller is not the active leader. · The operation requires the administrator privilege. · The context already exists. · The specified tenant doesn't exist. · The specified vPort doesn't exist. · The tenant IDs for the context and the specified vPort are different. · The specified vSubnet doesn't exist. · The tenant IDs for the context and the specified vSubnet are different. · The specified vNetwork doesn't exist. · The tenant IDs for the context and the specified vNetwork are different.

Delete context

Keyword	DELETE_CONTEXT_OP
Message text	Deleted context $1
Variable fields	$1: Name of the context.
Example	Deleted context net1
Explanation	A context was deleted.
Possible failure causes	· The service of the service chain has not been found. · Configuration recovery is in progress. · The controller is not the active leader. · The operation requires the administrator privilege. · The configuration item doesn't exist. · The context is being used by a service chain.

Update context

Keyword	UPDATE_CONTEXT_OP
Message text	Updated context $1
Variable fields	$1: Context information.
Example	Updated context id: 764a2ebe-eb47-43f7-98f3-e492b7b8ebeb tenant id: ffffffff-0000-0000-0000-000000000001 name: net1 context base: type: NETWORK networks: e3672c88-04db-4c85-bd1c-3e8b869c94b3 53b5199d-7181-41f6-8f8a-4637603a9e04 manualMap: tenant name: default in chain: false
Explanation	A context was modified.
Possible failure causes	· The service of the service chain has not been found. · Configuration recovery is in progress. · The controller is not the active leader. · The operation requires the administrator privilege. · The configuration item doesn't exist. · The context is being used by a service chain. · The specified vPort doesn't exist. · The tenant IDs for the context and the specified vPort are different. · The specified vSubnet doesn't exist. · The tenant IDs for the context and the specified vSubnet are different. · The specified vNetwork doesn't exist. · The tenant IDs for the context and the specified vNetwork are different.

Tenant

This section contains tenant messages.

Add tenant

Keyword	ADD_TENANT_OP
Message text	Add tenant : $1
Variable fields	$1: Tenant configuration information.
Example	Add tenant ID: ec4bf666-5c73-4897-b4fc-3fcbae79f746 Name: tenant1 Type: local-create
Explanation	A tenant was added.
Possible failure causes	· The service has not been found. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The length of name is too long. · Invalid parameter. · The tenant already exists. · No permission to add the tenant. · The tenant name is required.

Update tenant

Keyword	UPDATE_TENANT_OP
Message text	Update tenant: $1
Variable fields	$1: UUID of the tenant.
Example	Update tenant: ec4bf666-5c73-4897-b4fc-3fcbae79f746
Explanation	A tenant was modified.
Possible failure causes	· The service has not been found. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The length of name is too long. · Invalid parameter. · The tenant name is required. · No permission to modify the tenant. · Can't modify the default tenant.

Delete tenant

Keyword	DELETE_TENANT_OP
Message text	Delete tenant $1
Variable fields	$1: Name of the tenant.
Example	Delete tenant tenant1
Explanation	A tenant was deleted.
Possible failure causes	· The service has not been found. · The controller is not the active leader. · Configuration recovery is in progress. · Can't delete the default tenant. · The tenant has bound resources. · No permission to delete the tenant. · Failed to delete the contexts on the device for the tenant. Please manually delete the contexts.

Import tenants

Keyword	IMPORT_TENANTS_OP
Message text	Import tenants
Variable fields	None.
Example	Import tenants
Explanation	Tenants were imported.
Possible failure causes	· The service has not been found. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The Keystone URL can't be null. · The administrator name can't be null. · The administrator password can't be null. · The administrator tenant can't be null. · The Keystone URL is too long. · The administrator name is too long. · The administrator password is too long. · The administrator tenant name is too long. · Invalid parameter. · Invalid Keystone URL format. · Failed to import tenant accounts from the OpenStack server. · No permission to import the tenants from the OpenStack server.

VPNaaS

This section contains messages from the IPsec VPN service module.

Create IKE policy

Keyword	CREATE_IKEPOLICY_OP
Message text	Create IKE policy $1
Variable fields	$1: Information about the IKE policy.
Example	Create IKE policy Name: ikepolicy1 UUID: 5522aff7-1b3c-48dd-9c3c-b50f016b73db Description: ikepolicy1 Tenant id：ffffffff-0000-0000-0000-000000000001 IKE Version: v1 Auth Algorithm: sha1 Encryption Algorithm: aes-128 PFS: group5 Phase1 Negotiation Mode: main Lifetime: Units: seconds Value: 3600
Explanation	An IKE policy was created.
Possible failure causes	· Invalid JSON format. · The controller is not the active leader. · The operation requires the administrator privilege. · The IKE policy cannot use the same authentication algorithm, encryption algorithm, DH algorithm, and phase-1 negotiation mode as an existing IKE policy. · The tenant doesn't exist.

Delete IKE policy

Keyword	DELETE_IKEPOLICY_OP
Message text	Delete IKE policy $1
Variable fields	$1: Name of the IKE policy.
Example	Delete IKE policy ikepolicy1
Explanation	An IKE policy was deleted.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · The IKE policy is in use.

Update IKE policy

Keyword	UPDATE_IKEPOLICY_OP
Message text	Update IKE policy $1
Variable fields	$1: Information about the IKE policy.
Example	Update IKE policy Name: ikepolicy1 Description: ikepolicy1 IKE Version: v1 Auth Algorithm: sha1 Encryption Algorithm: aes-128 PFS: group5 Phase1 Negotiation Mode: main Lifetime: Units: seconds Value: 3600
Explanation	An IKE policy was modified.
Possible failure causes	· Invalid JSON format. · The controller is not the active leader. · The operation requires the administrator privilege. · The IKE policy is in use.

Create IPsec policy

Keyword	CREATE_IPSECPOLICY_OP
Message text	Create IPsec policy $1
Variable fields	$1: Information about the IPsec policy.
Example	Create IPsec policy Name: policy UUID: 5291b189-fd84-46e5-84bd-78f40c05d69c Description: policy1 Tenant id：ffffffff-0000-0000-0000-000000000001 Encapsulation Mode: tunnel Transform Protocol: ESP Auth Algorithm: sha1 Encryption Algorithm: aes-128 Lifetime: Units: seconds Value: 3600 PFS: group5
Explanation	An IPsec policy was created.
Possible failure causes	· Invalid JSON format. · The controller is not the active leader. · The operation requires the administrator privilege. · Invalid encryption algorithm. · The IPsec policy cannot use the same encapsulation mode, security protocol, authentication algorithm, encryption algorithm, and perfect forward secrecy as an existing IPsec policy. · The tenant doesn't exist.

Delete IPsec policy

Keyword	DELETE_IPSECPOLICY_OP
Message text	Delete IPsec policy $1
Variable fields	$1: Name of the IPsec policy.
Example	Delete IPsec policy policy
Explanation	An IPsec policy was deleted.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · The IPsec policy is in use. · The IPsec policy doesn't exist.

Update IPsec policy

Keyword	UPDATE_IPSECPOLICY_OP
Message text	Update IPsec policy $1
Variable fields	$1: Information about the IPsec policy.
Example	Update IPsec policy Name: policy Description: policy1 Encapsulation Mode: tunnel Transform Protocol: AH Auth Algorithm: sha1 Encryption Algorithm: aes-128 Lifetime: Units: seconds Value: 3600 PFS: group5
Explanation	An IPsec policy was modified.
Possible failure causes	· Invalid JSON format. · The controller is not the active leader. · The operation requires the administrator privilege. · The IPsec policy is in use.

Create VPN service

Keyword	CREATE_VPNSERVICE_OP
Message text	Create VPN service $1
Variable fields	$1: Information about the VPN service.
Example	Create VPN service Name: vpn1 UUID: 9faaf49f-dd89-4e39-a8c6-101839aa49bc Description: 33 Tenant id：ffffffff-0000-0000-0000-000000000001 Router Id: ec8619be-0ba8-4955-8835-3b49ddb76f89 Subnet Id: f4fb4528-ed93-467c-a57b-11c7ea9f963e Admin State Up: ACTIVE
Explanation	A VPN service was created.
Possible failure causes	· Invalid JSON format. · The controller is not the active leader. · The operation requires the administrator privilege. · The VPN service can't be bound to external subnet. · The tenant doesn't exist. · The vRouter doesn't exist. · The vSubnet doesn't exist. · The vSubnet is already used by a VPN service. · The VPN service and the specified vRouter belong to different tenants. · The vSubnet is not bound to the specified vRouter.

Delete VPN service

Keyword	DELETE_VPNSERVICE_OP
Message text	Delete VPN service $1
Variable fields	$1: Name of the VPN service.
Example	Delete VPN service vpn1
Explanation	A VPN service was deleted.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · The VPN service is in use.

Update VPN service

Keyword	UPDATE_VPNSERVICE_OP
Message text	Update VPN service $1
Variable fields	$1: Information about the VPN service.
Example	Update VPN service Name: vpn1 UUID: 9faaf49f-dd89-4e39-a8c6-101839aa49bc Description: vpnservice1 Subnet Id: f4fb4528-ed93-467c-a57b-11c7ea9f963e
Explanation	A VPN service was modified.
Possible failure causes	· Invalid JSON format. · The controller is not the active leader. · The operation requires the administrator privilege. · The VPN service is in use. · The vSubnet doesn't exist. · The vSubnet is not bound to the specified vRouter.

Create IPsec Site Connections

Keyword	CREATE_IPSEC_SITE_CONNS_OP
Message text	Create IPsec Site Connections $1
Variable fields	$1: Information about the IPsec site connection.
Example	Create IPsec Site Connections Name: vpnconnection1 UUID: cbc152a0-7e93-4f98-9f04-b085a4bf2511 Description: connections 1 Tenant id：ffffffff-0000-0000-0000-000000000001 VPN Service Id: c2f3178d-5530-4c4a-89fc-050ecd552636 IKE Policy Id: bf5612ac-15fb-460c-9b3d-6453da2fafa2 IPsec Policy Id: 8ba867b2-67eb-4835-bb61-c226804a1584 Peer Address: 172.24.4.226 Peer Id: 172.24.4.226 Peer CIDRS: [10.1.0.0/24] Auth Mode: PSK PSK: ****** Initiator: bi-directional Admin State Up: true MTU: 1500 DPD: Action: clear Interval: 30 Timeout: 120 Route Mode: static
Explanation	An IPsec site connection was created.
Possible failure causes	· Invalid JSON format. · Invalid parameter. · The controller is not the active leader. · The operation requires the administrator privilege. · The tenant doesn't exist. · The IPsec site connection already exists. · The vSubnet is not bound to the VPN service. · If the peer ID and vRouter bound to the VPN services of the IPsec site are the same as other IPsec sites, you must configure the same IKE policy and DPD interval for all these IPsec sites. · The IPsec site connection and the specified VPN service belong to different tenants. · The IPsec site connection and the specified IKE policy belong to different tenants. · The IPsec site connection and the specified IPsec policy belong to different tenants. · The VPN service doesn't exist. · The IKE policy doesn't exist. · The IPsec policy doesn't exist.

Delete IPsec Site Connection

Keyword	DELETE_IPSEC_SITE_CONN_OP
Message text	Delete IPsec Site Connection $1
Variable fields	$1: Name of the IPsec site connection.
Example	Delete IPsec Site Connection vpnconnection1
Explanation	An IPsec site connection was deleted.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · The IPsec site connection doesn't exist. · The IPsec site connection and the specified VPN service belong to different tenants. · The IPsec site connection and the specified IKE policy belong to different tenants. · The IPsec site connection and the specified IPsec policy belong to different tenants. · The VPN service doesn't exist. · The IKE policy doesn't exist. · The IPsec policy doesn't exist.

Update IPsec Site Connections

Keyword	UPDATE_IPSEC_SITE_CONNS_OP
Message text	Update IPsec Site Connections $1.
Variable fields	$1: Information about the IPsec site connection.
Example	Update IPsec Site Connections Name: vpnconnection1 UUID: cbc152a0-7e93-4f98-9f04-b085a4bf2511 Description: connections 2 VPN Service Id: c2f3178d-5530-4c4a-89fc-050ecd552636 IKE Policy Id: bf5612ac-15fb-460c-9b3d-6453da2fafa2 IPsec Policy Id: 8ba867b2-67eb-4835-bb61-c226804a1584 Peer Address: 172.24.4.226 Peer Id: 172.24.4.226 Peer CIDRS: [10.1.0.0/24] PSK: ****** Initiator: bi-directional Admin State Up: true MTU: 1500 DPD: Action: clear Interval: 30 Timeout: 120 Route Mode: static
Explanation	An IPsec site connection was modified.
Possible failure causes	· Invalid JSON format. · Invalid parameter. · The controller is not the active leader. · The operation requires the administrator privilege. · The IPsec site connection already exists. · The IPsec site connection doesn't exist. · The vSubnet is not bound to the VPN service. · If the peer ID and vRouter bound to the VPN services of the IPsec site are the same as other IPsec sites, you must configure the same IKE policy and DPD interval for all these IPsec sites.

VSM

This section contains virtual network messages.

Create VDS

Keyword	CREATE_VDS_OP
Message text	Created VDS "$1".
Variable fields	$1: VDS name.
Example	Created VDS "vds2".
Explanation	A VDS was created.
Possible failure causes	· The request is invalid: Incorrect JSON. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The VDS name already exists. · The length of the bridge name exceeds the limit. · The bridge name already exists. · The VXLAN tunnel name already exists. · The length of the VXLAN tunnel name exceeds the limit. · The openflow idle aging time exceeds the limit. · The openflow hard aging time exceeds the limit. · The anti-spoofing flow table aging time exceeds the limit. · Invalid VXLAN range. · Invalid global virtual MAC address. · Invalid VTEP IP for the network node. · Invalid VTEP MAC for the network node. · Invalid forwarding mode. · The length of the automatically generated VXLAN tunnel name exceeds the limit. · The VDS name and the bridge name cannot both be null. · The VDS already exists. · Can't modify the name of the default VDS. · Unknown error.

Update VDS

Keyword	UPDATE_VDS_OP
Message text	Updated VDS "$1".
Variable fields	$1: VDS name.
Example	Updated VDS "vds2".
Explanation	A VDS was modified.
Possible failure causes	· The request is invalid: Incorrect JSON. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · Can't modify the global virtual MAC address, bridge name, VXLAN range, VXLAN tunnel name, forward mode, and auto port creation for the VDS. · The VDS ID is required. · The VDS name already exists. · The length of the bridge name exceeds the limit. · The bridge name already exists. · The VXLAN tunnel name already exists. · The length of the VXLAN tunnel name exceeds the limit. · The openflow idle aging time exceeds the limit. · The openflow hard aging time exceeds the limit. · The anti-spoofing flow table aging time exceeds the limit. · Invalid VXLAN range. · Invalid global virtual MAC address. · Invalid VTEP IP for the network node. · Invalid VTEP MAC for the network node. · Invalid forwarding mode. · The specified resource doesn't exist. · Can't modify the name of the default VDS. · The bridge name is required. · The VXLAN tunnel name is required. · Unknown error.

Delete VDS

Keyword	DELETE_VDS_OP
Message text	Deleted VDS "$1".
Variable fields	$1: VDS name.
Example	Deleted VDS "vds2".
Explanation	A VDS was deleted.
Possible failure causes	· The request is invalid: Incorrect JSON. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The specified resource doesn't exist. · Can't delete the VDS because it is in use. · Can't delete the default VDS. · Failed to delete the router, because it has a bound subnet. · Unknown error.

Add host

Keyword	ADD_HOST_OP
Message text	Added host "$1".
Variable fields	$1: IP address of the host.
Example	Added host "1.1.1.1"
Explanation	A host was added.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · Invalid IP address. · No available region. · The HA module has not been found. · Failed to add the host because no region accepts vSwitches. · The host already exists. · Failed to add the host because the domain type is vCenter. · The bridge doesn't exist. · Unknown error. · Invalid overlay license. · Can't reach the host. · The number of CPUs that can be managed is insufficient. Please purchase a new license or expand the existing one. · Not allowed to access the host. · Incorrect bridge configuration on the host. · The request is invalid. · The host type and the domain type do not match. · The IP address is already used by a network element.

Update host

Keyword	UPDATE_HOST_OP
Message text	Updated host
Variable fields	N/A
Example	Updated host
Explanation	A host was modified.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · Failed to add the host because no region accepts vSwitches. · Failed to add the host because the domain type is vCenter. · The host already exists. · The bridge doesn't exist. · No available region. · Invalid overlay license. · Invalid IP address. · The domain doesn't exist. · The request is invalid. · The max packet-in packet rate is invalid. · Cannot configure the max packet-in packet rate. · The flow entry aging acceleration threshold is invalid. · Cannot configure the flow entry aging acceleration threshold. · Unknown error.

Delete host

Keyword	DELETE_HOST_OP
Message text	Deleted host "$1".
Variable fields	$1: IP address of the host.
Example	Deleted host "1.1.1.1"
Explanation	A host was deleted.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The specified resource doesn't exist. · Cannot delete the host because it is a network element. · Unknown error.

Create vRouter

Keyword	CREATE_VROUTER_OP
Message text	Created vRouter "$1".
Variable fields	$1: vRouter name.
Example	Created vRouter "router01"
Explanation	A vRouter was created.
Possible failure causes	· The request is invalid: Incorrect JSON. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · Invalid tenant ID. · The router ID is already used. · The router is required. · The field is_bind_gw is a read-only field. · The VDS doesn't exist. · Unknown error.

Update vRouter

Keyword	UPDATE_VROUTER_OP
Message text	Updated vRouter "$1".
Variable fields	$1: vRouter name.
Example	Updated vRouter "router01"
Explanation	A vRouter was modified.
Possible failure causes	· The request is invalid: Incorrect JSON. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The subnet and the router are not in the same VDS. · The router has not been bound to a gateway. · The specified external network doesn't exist. · The specified external network has no subnet. · Failed to bind the router to the external network, because the external subnet doesn't have enough assignable IP addresses. · The router ID is required. · The specified resource doesn't exist. · The field is_bind_gw is a read-only field. · The subnet overlaps with another subnet. · A vPort or APP cluster VIP on the vRouter has been bound to a floating IP. · The subnet must belong to the specified network. · Failed to bind the vRouter to the network because the specified network is not an external network. · The IP address doesn't belong to the network. · The IP address doesn't belong to the subnet. · The extranet IP is invalid. · The external network is required. · The subnet and the extranet IP can't both be null. · The extranet IP conflicts with another extranet IP. · The extranet IP conflicts with a floating IP. · The extranet IP conflicts with a gateway IP. · The extranet IP conflicts with the broadcast address of the subnet. · The extranet IP conflicts with the subnet address. · The external subnet overlaps with the external subnet of another vRouter. · Unknown error.

Delete vRouter

Keyword	DELETE_VROUTER_OP
Message text	Deleted vRouter "$1".
Variable fields	$1: vRouter name.
Example	Deleted vRouter "router01".
Explanation	A vRouter was deleted.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The specified resource doesn't exist. · Failed to delete the router, because it has a bound subnet. · Failed to delete the vRouter because it has been bound to service resources. · Unknown error.

Create internal route

Keyword	CREATE_INTERNAL_ROUTE_OP
Message text	Created internal route to router "$1", "dest: $2, next hop: $3".
Variable fields	$1: vRouter name. $2: Destination network of the intranet route. $3: Next hop of the intranet route.
Example	Created internal route to router "vRouter1", "dest: 100.1.1.1/24, next hop: 100.1.1.1".
Explanation	An intranet route was created.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The next hop address doesn't belong to the destination network of the route. · The destination network of the route overlaps with that of another internal route. · The destination is required. · The next hop is required. · The specified resource doesn't exist. · Invalid IP address. · Invalid CIDR. · The request is invalid. · Unknown error.

Delete internal route

Keyword	DELETE_INTERNAL_ROUTE_OP
Message text	Deleted internal route from router $1, "dest: $2, next hop: $3".
Variable fields	$1: vRouter name. $2: Destination network of the intranet route. $3: Next hop of the intranet route.
Example	Deleted internal route from router "vrouter1", "dest: 100.1.1.1/24, next hop: 100.1.1.1".
Explanation	An intranet route was deleted.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The specified resource doesn't exist. · Unknown error.

Create interface

Keyword	CREATE_INTERFACE_OP
Message text	Created interface "$1" to vRouter "$2".
Variable fields	$1: Name of the subnet with which the interface associates. $2: vRouter name.
Example	Created interface "subnet3" to vRouter "vrouter1".
Explanation	An interface was created.
Possible failure causes	· The request is invalid: Incorrect JSON. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The subnet has already been bound to another router. · The subnet can't be directly deleted from or added to the router. · The subnet and the router are not in the same VDS. · The specified subnet doesn't exist. · Subnets in the same network must be bound to the same router. · The specified resource doesn't exist. · The subnet overlaps with another subnet. · The subnet ID was null. · The subnet and the vRouter are not in the same tenant. · The subnet has already been bound to the vRouter. · Unknown error.

Delete interface

Keyword	DELETE_INTERFACE_OP
Message text	Deleted interface "$1" from vRouter "$2".
Variable fields	$1: Name of the subnet with which the interface associates. $2: vRouter name.
Example	Deleted interface "subnet1" from vRouter "vrouter1".
Explanation	An interface was deleted.
Possible failure causes	· The request is invalid: Incorrect JSON. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The subnet can't be directly deleted from or added to the router. · The specified subnet doesn't exist. · The subnet has already been unbound from the router. · The subnet ID is required. · Failed to unbind the interface from the vRouter, because a vPort or APP cluster VIP in the subnet has been bound to a floating IP. · The specified resource doesn't exist. · Unknown error.

Created Network

Keyword	CREATE_NETWORK_OP
Message text	Created network "$1".
Variable fields	$1: Name of the virtual link layer network.
Example	Created network "network01".
Explanation	A virtual link layer network was created.
Possible failure causes	· The request is invalid: Incorrect JSON. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · Invalid tenant ID. · The segment ID is already used. · The segment ID is out of range. · The shared attribute is not supported. · The network's parameter is incorrect. · The network already exists. · The service IP address does not match the gateway type. · The add-to-router attribute is not supported in external and VLAN network. · The router doesn't exist. · The router and network doesn't belong to the same tenant. · The router and network doesn't belong to the same VDS. · Failed to create the VXLAN because no available overlay license exists. · Unknown network type. · The type of the network is different than the other networks in the tenant. · The ARP packet sending rate exceeds the rate limit. · The VDS doesn't exist. · Invalid ARP flooding configuration. · Invalid ARP proxy configuration. · Invalid DHCP to controller configuration. · No available segment ID. · External networks and VLANs do not support network sharing. · Unknown error.

Update Network

Keyword	UPDATE_NETWORK_OP
Message text	Updated network "$1".
Variable fields	$1: Name of the virtual link layer network.
Example	Updated network "network01".
Explanation	A virtual link layer network was modified.
Possible failure causes	· The request is invalid: Incorrect JSON. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The shared attribute is not supported. · The external attribute can't be modified. · The network's parameter is incorrect. · The specified resource doesn't exist. · The ARP packet sending rate exceeds the rate limit. · Invalid ARP flooding configuration. · Invalid ARP proxy configuration. · Invalid DHCP to controller configuration. · Failed to disable network sharing for the virtual link layer network because it is being used by other tenants. · External networks and VLANs do not support network sharing. · Unknown error.

Delete Network

Keyword	DELETE_NETWORK_OP
Message text	Deleted network "$1".
Variable fields	$1: Name of the virtual link layer network.
Example	Deleted network "network02".
Explanation	A virtual link layer network was deleted.
Possible failure causes	· The request is invalid: Incorrect JSON. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · Can’t delete the network because a port group resides on the network. · The network contains a subnet. · The specified resource doesn't exist. · The port group has not been unbound from the subnet. · The subnet has not been unbound from the router. · A port resides on the subnet. · Can't delete the network because the network has flooding domains. · Unknown error.

Create Subnet

Keyword	CREATE_SUBNET_OP
Message text	Created subnet "$1".
Variable fields	$1: Subnet name.
Example	Created subnet "subnet01".
Explanation	A subnet was created.
Possible failure causes	· The request is invalid: Incorrect JSON. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · Invalid tenant ID. · The network doesn't exist. · The CIDR is required. · The gateway IP is required. · The gateway IP address doesn't belong to the subnet. · The service IP address doesn't belong to the subnet. · The DHCP attribute of the subnet is not the same in the network. · The IP addresses in the address pool don't belong to the subnet. · The service IP address conflicts with the gateway IP address. · The gateway IP address conflicts with the subnet broadcast address. · The gateway IP address conflicts with the subnet address. · The subnet overlaps with another subnet. · The service IP can't be specified in non-traditional-forwarding. · The start IP address can't be greater than the end IP address. · The IP range of address pool overlaps with the IP range of another address pool. · The tenant ID of the subnet is different than the network. · The subnet ID already exists. · Invalid IP address. · The domain name can't exceed 255 characters. · Invalid server identifier. · The lease duration exceeds the limit. · The address pool address format is invalid. · The DNS server address format is invalid. · The format of the host route destination is invalid. · The format of the host route next hop is invalid. · The configuration contains duplicate host route. · Invalid CIDR. · The configuration contains duplicate DNS. · Failed to create subnets for a VXLAN because no available overlay license exists. · Unknown error.

Update Subnet

Keyword	UPDATE_SUBNET_OP
Message text	Updated subnet "$1".
Variable fields	$1: Subnet name.
Example	Updated subnet "subnet01".
Explanation	A subnet was modified.
Possible failure causes	· The request is invalid: Incorrect JSON. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The start IP address can't be greater than the end IP address. · The IP range of address pool overlaps with the IP range of another address pool. · The IP addresses in the address pool don't belong to the subnet. · Invalid IP address. · The domain name can't exceed 255 characters. · Invalid server identifier. · The format of the host route destination is invalid. · The format of the host route next hop is invalid. · The configuration contains duplicate host route. · The address pool of the internal subnet can't be modified. · The configuration contains duplicate DNS. · Unknown error.

Delete Subnet

Keyword	DELETE_SUBNET_OP
Message text	Deleted subnet "$1".
Variable fields	$1: Subnet name.
Example	Deleted subnet "subnet01".
Explanation	A subnet was deleted.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · A port resides on the subnet. · The port group has not been unbound from the subnet. · The subnet has not been unbound from the router. · A vPort or APP cluster VIP on the vRouter has been bound to a floating IP. · An APP cluster VIP resides on the subnet. · Unknown error. · The specified resource doesn't exist. · The external subnet has floating IPs. · Unknown error.

Create network policy

Keyword	CREATE_NETWORK_POLICY_OP
Message text	Created network policy "$1".
Variable fields	$1: Network policy name.
Example	Created network policy "policy01".
Explanation	A network policy was created.
Possible failure causes	· The request is invalid: Incorrect JSON. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The QoS policy UUID is already used. · Invalid CIR value of inbound QoS. · Invalid CIR value of outbound QoS. · Invalid CBS value of inbound QoS. · Invalid CBS value of outbound QoS. · Invalid DSCP value. · The network policy name is required. · Invalid rate value. · Unknown error.

Update network policy

Keyword	UPDATE_NETWORK_POLICY_OP
Message text	Updated network policy "$1".
Variable fields	$1: Network policy name.
Example	Updated network policy "policy01".
Explanation	A network policy was modified.
Possible failure causes	· The request is invalid: Incorrect JSON. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The QoS policy ID is required. · Failed to configure inbound QoS. · Failed to configure outbound QoS. · Failed to remove the inbound QoS configuration. · Failed to remove the outbound QoS configuration. · Invalid CIR value of inbound QoS. · Invalid CIR value of outbound QoS. · Invalid CBS value of inbound QoS. · Invalid CBS value of outbound QoS. · Invalid DSCP value. · The specified resource doesn't exist. · The network policy name is required. · Invalid rate value. · Unknown error.

Delete network policy

Keyword	DELETE_NETWORK_POLICY_OP
Message text	Deleted network policy "$1".
Variable fields	$1: Network policy name.
Example	Deleted network policy "policy01".
Explanation	A network policy was deleted.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · Can't delete the default network policy. · The network policy has been bound to a port or a port group. · The specified resource doesn't exist. · Unknown error.

Create security policy

Keyword	CREATE_SECURITY_POLICY_OP
Message text	Created security policy "$1".
Variable fields	$1: Security policy name.
Example	Created security policy "spolicy01".
Explanation	A security policy was created.
Possible failure causes	· The request is invalid: Incorrect JSON. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · Duplicate security policy UUID. · Invalid anti-spoofing flow entry aging time. · Invalid empty rule action. · Unknown error.

Update security policy

Keyword	UPDATE_SECURITY_POLICY_OP
Message text	Updated security policy "$1".
Variable fields	$1: Security policy name.
Example	Updated security policy "spolicy01".
Explanation	A security policy was modified.
Possible failure causes	· The request is invalid: Incorrect JSON. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The security policy ID is required. · Invalid deny flow age. · Invalid empty rule action. · The specified resource doesn't exist. · Unknown error.

Delete security policy

Keyword	DELETE_SECURITY_POLICY_OP
Message text	Deleted security policy "$1".
Variable fields	$1: Security policy name.
Example	Deleted security policy "spolicy01".
Explanation	A security policy was deleted.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The security policy has been bound to a port or a port group. · The specified resource doesn't exist. · Unknown error.

Create floating IP

Keyword	CREATE_FLOATING_IP_OP
Message text	Created floating IP "$1".
Variable fields	$1: Floating IP address.
Example	Created floating ip "202.100.1.10".
Explanation	A floating IP address was created.
Possible failure causes	· The request is invalid: Incorrect JSON. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The specified subnet doesn't exist. · The specified subnet is not an external subnet. · The specified port doesn't exist. · Invalid port type. · The fixed IP address must be the IP address of the port. · The port has not been bound to the router. · Floating IP address allocation failed. · The IP address must belong to the specified subnet. · The network doesn't exist. · Failed to bind the floating IP to the vPort or APP cluster VIP, because the floating IP doesn't belong to the external subnet bound to the vRouter of the vPort or APP cluster VIP. · The floating IP ID already exists. · The APP cluster VIP doesn't exist. · Invalid protocol type. · Invalid port number. · The configuration conflicts with the configuration of an existing floating IP. · The floating IP can be bound only to a vPort or an APP cluster VIP. · The subnet to which the APP cluster VIP belongs is not bound to a vRouter. · The configuration of the floating IP conflicts with the configuration of a bound floating IP. · Invalid local port number. · The IP address doesn't belong to the network. · The specified network is not an external network. · The specified subnet doesn't belong to the network. · The vRouter is not bound to an external network. · The external network doesn't exist. · The external network doesn't have any subnets. · The floating IP conflicts with an extranet IP. · The floating IP conflicts with a gateway IP. · The floating IP conflicts with the broadcast address of the subnet. · The floating IP conflicts with the subnet address. · The UUIDs of the vPort, APP cluster VIP, subnet, and network to which the floating IP belongs are not specified. · Invalid IP address. · Unknown error.

Update floating IP

Keyword	UPDATE_FLOATING_IP_OP
Message text	Updated floating IP $1.
Variable fields	$1: Floating IP address.
Example	Updated floating IP "202.100.1.10".
Explanation	A floating IP address was modified.
Possible failure causes	· The request is invalid: Incorrect JSON. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The specified port doesn't exist. · The port has not been bound to the router. · The external network doesn't exist. · The floating IP has been bound to another port. · The specified resource doesn't exist. · Failed to bind the floating IP to the vPort or APP cluster VIP, because the floating IP doesn't belong to the external subnet bound to the vRouter of the vPort or APP cluster VIP. · The APP cluster VIP doesn't exist. · Invalid protocol type. · Invalid port number. · The floating IP can be bound only to a vPort or an APP cluster VIP. · The subnet to which the APP cluster VIP belongs is not bound to a vRouter. · The floating IP has been bound to another APP cluster VIP. · The configuration of the floating IP conflicts with the configuration of a bound floating IP. · Invalid local port number. · The IP address of the floating IP can't be modified. · The protocol type and the port number of the floating IP can't be modified. · The floating IP has been used by another gateway resource. · The vRouter to which the floating IP belongs doesn't bind a gateway service resource. · The UUIDs of the vPort, APP cluster VIP, subnet, and network to which the floating IP belongs are not specified. · Invalid IP address. · Unknown error.

Delete floating IP

Keyword	DELETE_FLOATING_IP_OP
Message text	Deleted floating IP $1.
Variable fields	$1: Floating IP address.
Example	Deleted floating IP "202.100.1.10".
Explanation	A floating IP address was deleted.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The specified resource doesn't exist. · Unknown error.

Create port group

Keyword	CREATE_PORT_GROUP_OP
Message text	Created port group "$1".
Variable fields	$1: Port group name.
Example	Created port group "group01".
Explanation	A port group was created.
Possible failure causes	· The request is invalid: Incorrect JSON. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The port group name is already used. · The port group ID is already used. · The port group name should be less than 80 characters. · The network ID is required. · The port group name is required. · The port group name is case sensitive and can contain only Chinese characters, letters, digits, underscores (_), and hyphens (-). · The network doesn't exist. · No subnet is created. · The specified port policy doesn't exist. · The specified security policy doesn't exist. · Failed to create the port group on the vCenter. · Invalid tenant ID. · Unknown error.

Update port group

Keyword	UPDATE_PORT_GROUP_OP
Message text	Updated port group "$1".
Variable fields	$1: Port group name.
Example	Updated port group "group01".
Explanation	A port group was modified.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The specified port policy doesn't exist. · The specified security policy doesn't exist. · The port group ID is required. · Can't modify the port group name. · Can't modify the network where the port group resides. · The specified resource doesn't exist. · The request is invalid. · Unknown error.

Delete port group

Keyword	DELETE_PORT_GROUP_OP
Message text	Deleted port group "$1".
Variable fields	$1: Port group name.
Example	Deleted port group "group01".
Explanation	A port group was deleted.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The port group ID is required. · The port group contains visible ports. · The specified resource doesn't exist. · Unknown error.

Create security rule

Keyword	CREATE_SECURITY_RULE_OP
Message text	Created security rule “$1” for security policy “$2”.
Variable fields	$1: UUID of the security rule. $2: Name of the security policy.
Example	Created security rule “d32019d3-bc6e-4319-9c1d-6722fc136a22” for security policy “policy1”.
Explanation	An ACL rule was created.
Possible failure causes	· The request is invalid: Incorrect JSON. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · Invalid security policy UUID. · Duplicate security rule UUID. · The new security rule conflicts with the old rules. · IPv6 is not supported. · Invalid IP version. · Invalid IP prefix. · Invalid protocol type. · Invalid port range. · Invalid ICMP type. · Invalid ICMP code. · Invalid direction. · Unknown error.

Update security rule

Keyword	UPDATE_SECURITY_RULE_OP
Message text	Updated security rule “$1” of security policy “$2”.
Variable fields	$1: UUID of the security rule. $2: Name of the security policy.
Example	Updated security rule “d32019d3-bc6e-4319-9c1d-6722fc136a22” of security policy “policy1”.
Explanation	An ACL rule was modified.
Possible failure causes	· The request is invalid: Incorrect JSON. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The new security rule conflicts with the old rules. · IPv6 is not supported. · Invalid IP version. · Invalid IP prefix. · Invalid protocol type. · Invalid port range. · Invalid ICMP type. · Invalid ICMP code. · Invalid direction. · The specified resource doesn't exist. · Unknown error.

Delete security rule

Keyword	DELETE_SECURITY_RULE_OP
Message text	Deleted security rule “$1” from security policy “$2”.
Variable fields	$1: UUID of the security rule. $2: Name of the security policy.
Example	Deleted security rule “d32019d3-bc6e-4319-9c1d-6722fc136a22” from security policy “policy1”.
Explanation	An ACL rule was deleted.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The specified resource doesn't exist. · Unknown error.

Authenticate with vCenter

Keyword	AUTH_VCENTER_OP
Message text	Authenticated with vCenter.
Variable fields	N/A
Example	Authenticated with vCenter.
Explanation	The controller was connected to the vCenter server.
Possible failure causes	· The request is invalid: Incorrect JSON. · The controller is not the active leader. · The operation requires the administrator privilege. · Failed to connect to the vCenter. · The vCenter has connected to another domain. · Invalid IP address. · The domain ID is required. · The domain can't connect to the vCenter. · Configuration recovery is in progress. · Unknown error.

Disconnect with vCenter

Keyword	DISCONNECT_VCENTER_OP
Message text	Disconnected with vCenter.
Variable fields	N/A
Example	Disconnected with vCenter.
Explanation	The controller was disconnected from the vCenter server.
Possible failure causes	· The request is invalid: Incorrect JSON. · The controller is not the active leader. · The operation requires the administrator privilege. · The specified resource doesn't exist. · Failed to connect to the vCenter. · Configuration recovery is in progress. · Unknown error.

Upload vib

Keyword	UPLOAD_VIB_OP
Message text	Uploaded vib “$1”.
Variable fields	$1: Name of the .vib file.
Example	Uploaded vib “s1020v_esx6.0.0-3.1.1.11.1_amd64.zip”.
Explanation	A .vib file was added.
Possible failure causes	N/A

Delete vib

Keyword	DELETE_VIB_OP
Message text	Deleted vib “$1”.
Variable fields	$1: UUID of the .vib file.
Example	Deleted vib “501172da-2514-3013-9a7e-5fb1f75d6090”.
Explanation	A .vib file was deleted.
Possible failure causes	· The request is invalid: Incorrect JSON. · Failed to delete the installation file. · The controller is not the active leader. · Configuration recovery is in progress. · The specified resource doesn't exist. · The operation requires the administrator privilege.

Install VFE

Keyword	INSTALL_VFE_OP
Message text	Installed VFE ”$1”.
Variable fields	$1: vSwitch version.
Example	Installed VFE “1.0-1.001.55.D002”.
Explanation	A vSwitch version was installed.
Possible failure causes	· The request is invalid: Incorrect JSON. · Failed to connect to the vCenter. · Installation failed. · Failed to get the installation file. · The vSwitch version doesn't match the EXSi version. · The operation requires the administrator privilege.

Update VFE

Keyword	UPDATE_VFE_OP
Message text	Updated VFE “$1”.
Variable fields	$1: vSwitch version.
Example	Updated VFE “1.0-1.001.55.D002”.
Explanation	The vSwitch version was updated.
Possible failure causes	· The request is invalid: Incorrect JSON. · Update failed. · Failed to get the installation file. · The vSwitch version doesn't match the EXSi version. · The operation requires the administrator privilege.

Uninstall VFE

Keyword	UNINSTALL_VFE_OP
Message text	Uninstalled VFE “$1”.
Variable fields	$1: vSwitch version.
Example	Uninstalled VFE “1.0-1.001.55.D002”.
Explanation	The vSwitch version was uninstalled.
Possible failure causes	· The request is invalid: Incorrect JSON. · Uninstallation failed. · Connection to the vCenter is not established. · The operation requires the administrator privilege.

Create domain

Keyword	CREATE_DOMAIN_OP
Message text	Created domain "$1".
Variable fields	$1: Domain name.
Example	Created domain "domain01".
Explanation	A domain was created.
Possible failure causes	· The request is invalid: Incorrect JSON. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The domain name is required. · Invalid domain type. · The domain UUID is already used. · The domain name is already used. · The host doesn't exist. · The VDS doesn't exist. · Unknown error.

Update domain

Keyword	UPDATE_DOMAIN_OP
Message text	Updated domain "$1".
Variable fields	$1: Domain name.
Example	Updated domain "domain01".
Explanation	A domain was modified.
Possible failure causes	· The request is invalid: Incorrect JSON. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The domain ID is required. · The domain name is required. · The specified resource doesn't exist. · The host doesn't exist. · Invalid domain type. · The domain name is already used. · Can't modify the default domain name. · Can't unbind the default VDS from the default domain. · Can't unbind the VDS from the domain because online hosts exist. · The VDS doesn't exist. · Can't unbind the VDS from the domain because the VDS has hosts. · Unknown error.

Delete domain

Keyword	DELETE_DOMAIN_OP
Message text	Deleted domain "$1".
Variable fields	$1: Domain name.
Example	Deleted domain "domain01".
Explanation	A domain was deleted.
Possible failure causes	· The request is invalid: Incorrect JSON. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · Failed to delete the domain. · Can't delete the default domain. · Failed to connect to the vCenter. · The specified resource doesn't exist. · Can't delete the domain because it has been connected to vCenter. · Can't delete the domain because it has been bound to VDS. · Unknown error.

Create vPort

Keyword	CREATE_VPORT_OP
Message text	Created vport "$1: $2/$3".
Variable fields	$1: Name of the vPort. $2: IP address of the vPort. $3: MAC address of the vPort.
Example	Created vport " tap1: 100.1.1.100/00: 01: 00: 01: 10: 00".
Explanation	A vPort was created.
Possible failure causes	· The request is invalid: Incorrect JSON. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · Invalid tenant ID. · The network doesn't exist. · Duplicate port ID. · The network ID is required. · Invalid port group ID. · The port group and the port don't reside on the same network. · The default uplink port policy can't be used as the port policy. · Invalid port policy ID. · Invalid port security policy UUID. · The MAC address is already used by another port. · The port and the gateway can't use the same IP address. · Neither the MAC address nor the IP address is configured. · The IP address is already used by another port. · The port IP address must belong to an existing subnet. · The IP address must belong to the specified subnet. · The subnet must belong to the specified network. · The domain doesn't exist. · Invalid mirroring direction. · Invalid mirroring type. · The mirroring direction is not specified. · The mirroring type is not specified. · The mirror remote IP is required. · The length of the description exceeds the limit. · The VLAN ID must be an integer in the range of 1 to 4094. · Invalid flooding domain. · Invalid APP cluster VIP. · The APP cluster VIP and the vPort are not in the same network. · The flooding domain and the vPort are not in the same network. · The vPort can be bound to a maximum of 10 flooding domains. · The specified subnet doesn't exist. · Invalid IP address. · The host name can't exceed 255 characters. · APP cluster VIPs bound to the same vPort must belong to the same subnet. · The subnets of the flooding domains bound to the same vPort can't overlap with each other. · The interface MTU is out of range. · The MAC address conflicts with the gateway MAC address or reserved gateway MAC address. · Invalid MAC address. · Unknown error.

Update vPort

Keyword	UPDATE_VPORT_OP
Message text	Updated vport "$1: $2/$3".
Variable fields	$1: Name of the vPort. $2: IP address of the vPort. $3: MAC address of the vPort.
Example	Updated vport " tap01: 100.1.1.100/00: 01: 00: 01: 10: 00".
Explanation	A vPort was modified.
Possible failure causes	· The request is invalid: Incorrect JSON. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The parameter (parameters) can't be modified. · Invalid port group ID. · The port group and the port don't reside on the same network. · The default uplink port policy can't be used as the port policy. · Invalid port policy ID. · Invalid port security policy UUID. · The mirroring direction is not specified. · The mirroring type is not specified. · Invalid mirroring direction. · Invalid mirroring type. · The mirroring remote IP address is not specified. · The port IP address must belong to an existing subnet. · The IP address is already used by another port. · The port and the gateway can't use the same IP address. · Can't update the MAC address. · The IP address must belong to the specified subnet. · Can't update the port name. · Can't update the port domain. · The subnet must belong to the specified network. · The floating IP has been bound to another port. · Unknown error. · Can't move the vPort to another port group because the vPort is created through vCenter. · The network doesn't exist. · The specified subnet doesn't exist. · The specified resource doesn't exist. · The length of the description exceeds the limit. · Invalid APP cluster VIP. · The APP cluster VIP and the vPort are not in the same network. · The flooding domain and the vPort are not in the same network. · The vPort can be bound to a maximum of 10 flooding domains. · Failed to modify the IP address of the port because the port is a physical port. · Invalid IP address. · The flooding domain doesn't exist. · The host name can't exceed 255 characters. · APP cluster VIPs bound to the same vPort must belong to the same subnet. · The subnets of the flooding domains bound to the same vPort can't overlap with each other. · The interface MTU is out of range. · The MAC address conflicts with the gateway MAC address or reserved gateway MAC address. · Invalid MAC address.

Delete vPort

Keyword	DELETE_VPORT_OP
Message text	Deleted vport "$1: $2/$3".
Variable fields	$1: Name of the vPort. $2: IP address of the vPort. $3: MAC address of the vPort.
Example	Deleted vport " tap1: 100.1.1.100/00: 01: 00: 01: 10: 00".
Explanation	A vPort was deleted.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The specified resource doesn't exist. · Can't delete the port because it is created by vCenter. · Can’t delete LB vPorts. · Unknown error.

Create APP cluster VIP

Keyword	CREATE_CLUSTER_IP_OP
Message text	Created cluster ip ”$1”.
Variable fields	$1: IP address of the APP cluster VIP.
Example	Created cluster ip ”192.168.1.1”.
Explanation	An APP cluster VIP was created.
Possible failure causes	· The network doesn't exist. · Invalid tenant ID. · Invalid IP address. · The APP cluster VIP ID already exists. · The APP cluster VIP already exists. · The APP cluster VIP is required. · The APP cluster VIP conflicts with the IP address of a vPort. · The APP cluster VIP must belong to an existing subnet. · The tenant is required. · The network is required. · The APP cluster VIP conflicts with the broadcast address of the subnet. · The APP cluster VIP conflicts with the subnet address. · The APP cluster mode is invalid. · The request is invalid. · Unknown error. · The controller is not the active leader. · Configuration recovery is in progress. · The operation requires the administrator privilege.

Update APP cluster VIP

Keyword	UPDATE_CLUSTER_IP_OP
Message text	Updated cluster ip ”$1”.
Variable fields	$1: IP address of the APP cluster VIP.
Example	Updated cluster ip ”192.168.1.1”.
Explanation	An APP cluster VIP was modified.
Possible failure causes	· The APP cluster mode is invalid. · The request is invalid. · Unknown error. · The controller is not the active leader. · Configuration recovery is in progress. · The specified resource doesn't exist. · The parameter (parameters) can’t be modified. · The operation requires the administrator privilege.

Delete APP cluster VIP

Keyword	DELETE_CLUSTER_IP_OP
Message text	Deleted cluster ip “$1”.
Variable fields	$1: IP address of the APP cluster VIP.
Example	Deleted cluster ip ”192.168.100.100”.
Explanation	An APP cluster VIP was deleted.
Possible failure causes	· Unknown error. · The controller is not the active leader. · Configuration recovery is in progress. · The specified resource doesn't exist. · The operation requires the administrator privilege.

Create flooding domain

Keyword	CREATE_BROADCASTDOMAIN_OP
Message text	Created broadcast domain “$1”.
Variable fields	$1: Flooding domain name.
Example	Created broadcast domain “domain1”.
Explanation	A flooding domain was created.
Possible failure causes	· The network doesn't exist. · The network ID is required. · The flooding domain name already exists. · The flooding domain name is case sensitive and can contain only Chinese characters, letters, digits, underscores (_), and hyphens (-). · The flooding domain name can't exceed 80 characters. · The flooding domain ID already exists. · The flooding domain name is required. · The MAC address type must be ANY for the flooding domain. · The flooding domain CIDR is required. · The MAC address type is required. · The mask length for the subnet address of the flooding domain must be in the range of 4 to 32 bits. · The subnet address conflicts with the subnet address of another flooding domain within the same network. · No valid group IDs exist. · The IP address of the flooding domain must be a multicast or broadcast address. · Invalid CIDR. · The request is invalid. · Unknown error. · The controller is not the active leader. · Configuration recovery is in progress. · The operation requires the administrator privilege. · Invalid tenant ID.

Update flooding domain

Keyword	UPDATE_BROADCASTDOMAIN_OP
Message text	Updated broadcast domain “$1”.
Variable fields	$1: Flooding domain name.
Example	Updated broadcast domain “domain1”.
Explanation	A flooding domain was modified.
Possible failure causes	· The MAC address type must be ANY for the flooding domain. · The flooding domain CIDR is required. · The MAC address type is required. · The mask length for the subnet address of the flooding domain must be in the range of 4 to 32 bits. · The subnet address conflicts with the subnet address of another flooding domain within the same network. · The IP address of the flooding domain must be a multicast or broadcast address. · The IP address of the flooding domain conflicts with the IP address of another flooding domain bound to the same vPort. · Invalid CIDR. · The request is invalid. · Unknown error. · The controller is not the active leader. · Configuration recovery is in progress. · The specified resource doesn't exist. · The parameter (parameters) can’t be modified. · The operation requires the administrator privilege.

Delete flooding domain

Keyword	DELETE_BROADCASTDOMAIN_OP
Message text	Deleted broadcast domain “$1”.
Variable fields	$1: Flooding domain name.
Example	Deleted broadcast domain “domain1”.
Explanation	A flooding domain was deleted.
Possible failure causes	· The flooding domain ID doesn't exist. · Unknown error. · The controller is not the active leader. · Configuration recovery is in progress. · The specified resource doesn't exist. · The operation requires the administrator privilege.

Update vCenter status

Keyword	SET_VCENTER_STATUS_OP
Message text	Updated vCenter status to $1.
Variable fields	$1: vCenter status: connected or disconnected.
Example	Updated vCenter status to connected.
Explanation	The vCenter status was updated.
Possible failure causes	· Failed to connect to the vCenter. · The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · The operation requires the administrator privilege. · Unknown error.

Delete vPort prefix name

Keyword	DELETE_PORT_PREFNAME_OP
Message text	Deleted vPort prefix name “$1”.
Variable fields	$1: Port prefix name.
Example	Deleted vPort prefix name “a1”.
Explanation	A port prefix name was deleted.
Possible failure causes	· Can't delete the default vPort prefix names. · Unknown error. · The controller is not the active leader. · Configuration recovery is in progress. · The specified resource doesn't exist. · The operation requires the administrator privilege.

Delete QoS device

Keyword	DELETE_QOSDEV_OP
Message text	Deleted QoS device “$1”.
Variable fields	$1: QoS device name.
Example	Deleted QoS device ”device1”.
Explanation	A QoS device was deleted.
Possible failure causes	· The specified IP address doesn't exist. · Unknown error. · The controller is not the active leader. · Configuration recovery is in progress. · The operation requires the administrator privilege.

Update global config

Keyword	UPDATE_GLOBAL_CONFIG_OP
Message text	Updated the advanced settings Fail-safe mode: “$1”.
Variable fields	$1: Status of the fail-safe mode.
Example	Updated the advanced settings Fail-safe mode: “on”.
Explanation	The fail-safe mode was enabled.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · The operation requires the administrator privilege. · Unknown error.

Update global default action

Keyword	UPDATE_GLOBALDEFAULTACTION_OP
Message text	Updated global default action “$1”.
Variable fields	$1: Global default action of distributed firewalls.
Example	Updated global default action “forward”.
Explanation	A global default action was configured for distributed firewalls.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · The global default action is required. · The global default action is invalid. · The maximum number of sessions is invalid. · Unknown error.

Create DFW policy

Keyword	CREATE_DFW_POLICY_OP
Message text	Created DFW policy “$1”.
Variable fields	$1: Name of the distributed firewall policy or subpolicy.
Example	Created DFW policy “policy1”.
Explanation	A distributed firewall policy or subpolicy was created.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · The DFW policy already exists. · The DFW policy name cannot exceed 255 characters. · The DFW policy description cannot exceed 255 characters. · The policy type is required. · The default action is required. · The default action is invalid. · Unknown error.

Update DFW policy

Keyword	UPDATE_DFW_POLICY_OP
Message text	Updated DFW policy “$1”.
Variable fields	$1: Name of the distributed firewall policy or subpolicy.
Example	Updated DFW policy “policy1”.
Explanation	A distributed firewall policy or subpolicy was modified.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · The specified resource doesn't exist. · Invalid DFW policy ID. · The DFW policy does not exist. · The DFW policy name cannot exceed 255 characters. · The DFW policy description cannot exceed 255 characters. · The default action is invalid. · Unknown error.

Delete DFW policy

Keyword	DELETE_DFW_POLICY_OP
Message text	Deleted DFW policy “$1”.
Variable fields	$1: Name of the distributed firewall policy or subpolicy.
Example	Deleted DFW policy “policy1”.
Explanation	A distributed firewall policy or subpolicy was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · The specified resource doesn't exist. · The DFW subpolicy cannot be deleted because it is in used. · Unknown error.

Create DFW policy rule

Keyword	CREATE_DFW_POLICY_RULE_OP
Message text	Created DFW policy rule “$1”.
Variable fields	$1: Name of the distributed firewall policy or subpolicy rule.
Example	Created DFW policy rule “rule1”.
Explanation	A distributed firewall policy or subpolicy rule was created.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid policy rule ID. · The policy rule already exists. · The specified subpolicy does not exist. · You cannot specify a subpolicy for the subpolicy rule. · Invalid action. · The policy rule number is out of range. · The specified policy or subpolicy does not exist. · The policy rule name cannot exceed 255 characters. · The source IP is invalid. · The destination IP is invalid. · The IP set does not exist. · The source IP and the source IP set cannot be both configured. · The Net&Port IP set and protocol cannot be configured at the same time. · The Net&Port IP set and port range cannot be configured at the same time. · The source IP set port direction is invalid. · Cannot configure the port direction for a NET IP set. · The destination IP and the destination IP set cannot be both configured. · The destination IP set port direction is invalid. · The ICMP type is required. · Invalid ICMP type. · Invalid ICMP code. · The ICMP protocol type and port range cannot be configured at the same time. · The ICMP protocol type and TCP flag check or match cannot be configured at the same time. · The tcp flag match and check must be configured at the same time. · The TCP flag check is invalid. · The TCP flag match is invalid. · The TCP flag match parameter is not a TCP flag check parameter. · The UDP protocol type and ICMP flag cannot be configured at the same time. · The UDP protocol type and TCP flag cannot be configured at the same time. · The protocol type is invalid. · The protocol type is required. · Invalid port number range. · Invalid port number. · The start port number cannot be greater than the end port number. · Invalid state. · The new DFW policy rule conflicts with another rule. · Unknown error.

Delete DFW policy rule

Keyword	DELETE_DFW_POLICY_RULE_OP
Message text	Deleted DFW policy rule “$1”.
Variable fields	$1: Name of the distributed firewall policy or subpolicy rule.
Example	Deleted DFW policy rule “rule1”.
Explanation	A distributed firewall policy or subpolicy rule was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · The specified resource doesn't exist. · The rule does not belong to any DFW policy. · Unknown error.

Create DFW IP set

Keyword	CREATE_DFW_IPSET_OP
Message text	Created DFW IP set “$1”.
Variable fields	$1: Name of the distributed firewall IP address set.
Example	Created DFW IP set “set1”.
Explanation	A distributed firewall IP address set was created.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · The IP set ID is invalid. · The IP set already exists. · The IP set name cannot exceed 255 characters. · The IP set type is invalid. · The maximum number of IP set rules is invalid. · Unknown error.

Update DFW IP set

Keyword	UPDATE_DFW_IPSET_OP
Message text	Updated DFW IP set “$1”.
Variable fields	$1: Name of the distributed firewall IP address set.
Example	Updated DFW IP set “set1”.
Explanation	A distributed firewall IP address set was modified.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · The IP set ID is required. · The IP set does not exist. · The IP set name cannot exceed 255 characters. · Unknown error.

Delete DFW IP set

Keyword	DELETE_DFW_IPSET_OP
Message text	Deleted DFW IP set “$1”.
Variable fields	$1: Name of the distributed firewall IP address set.
Example	Deleted DFW IP set “set1”.
Explanation	A distributed firewall IP address set was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · The specified resource doesn't exist. · The IP set is used by a policy rule. · Unknown error.

Create DFW IP set rule

Keyword	CREATE_DFW_IPSET_RULE_OP
Message text	Created DFW IP set rule “$1”.
Variable fields	$1: Name of the distributed firewall IP address set rule.
Example	Created DFW IP set rule “rule1”.
Explanation	A distributed firewall IP address set rule was created.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · The IP set rule ID is invalid. · The IP set rule already exists. · The IP set ID is required. · The IP set does not exist. · The CIDR is required. · Invalid CIDR. · The ICMP type is required. · The ICMP code is required. · Invalid ICMP type. · Invalid ICMP code. · The protocol type is invalid. · You cannot specify a protocol type for a Net IP set. · The IP set rule overlaps with another rule. · The number of IP set rules exceeds the limit. · Unknown error.

Delete DFW IP set rule

Keyword	DELETE_DFW_IPSET_RULE_OP
Message text	Deleted DFW IP set rule “$1”.
Variable fields	$1: Name of the distributed firewall IP address set rule.
Example	Deleted DFW IP set rule “rule1”.
Explanation	A distributed firewall IP address set rule was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · The specified resource doesn't exist. · Unknown error.

ZTP

This section contains zero touch provisioning (ZTP) messages.

Create provisioning

Keyword	ADD_PROVISIONING_OP
Message text	Created provisioning: $1
Variable fields	$1: Provisioning information.
Example	Created provisioning: MAC address: 02:6f:56:3e:2a:62, device ID: 02:6f:56:3e:2a:62, IP address: 192.168.2.2, subnet mask:255.255.255.0, configuration file: tt.cfg, description: switch
Explanation	A provisioning was created.
Possible failure causes	· ZTP license was required. · The controller was not the active leader. · The DHCP server was not installed. · The zero touch provisioning service was starting up. · Permission limit. · Incorrect IP address. · The MAC address was already used. · The device ID was already used. · The IP address was already used. · Failed to modify the DHCP configuration file. · Incorrect MAC address. · Incorrect subnet mask. · Incorrect device configuration file name. · The start IP, end IP, and gateway IP were not in the same subnet.

Modify provisioning

Keyword	MODIFY_PROVISIONING_OP
Message text	Modified provisioning: $1
Variable fields	$1: Provisioning information.
Example	Modified provisioning: MAC address: 02:6f:56:3e:2a:62, device ID: 02:6f:56:3e:2a:63, IP address: 192.168.5.6, subnet mask:255.255.255.0,configuration file: xx.cfg, description: switch2
Explanation	A provisioning was modified.
Possible failure causes	· ZTP license was required. · The controller was not the active leader. · The DHCP server was not installed. · The zero touch provisioning service was starting up. · Permission limit. · Incorrect IP address. · The provisioning didn't exist. · The device ID was already used. · The IP address was already used. · Failed to modify the DHCP configuration file. · Incorrect MAC address. · Incorrect subnet mask. · Incorrect device configuration file name.

Delete provisioning

Keyword	DELETE_PROVISIONING_OP
Message text	Deleted provisioning: $1
Variable fields	$1: Provisioning information.
Example	Deleted provisioning: MAC address: 02:6f:56:3e:2a:62
Explanation	A provisioning was deleted.
Possible failure causes	· The controller was not the active leader. · The DHCP server was not installed. · The zero touch provisioning service was starting up. · Permission limit. · The provisioning didn't exist. · Failed to modify the DHCP configuration file. · Incorrect MAC address.

Create address pool

Keyword	CREATE_ZTP_POOL_OP
Message text	Created address pool: $1
Variable fields	$1: Address pool information.
Example	Created address pool: IP range: 5.2.2.2-5.2.2.188, subnet mask: 255.255.0.0, gateway: 5.2.2.1
Explanation	An address pool was created.
Possible failure causes	· ZTP license was required. · The controller was not the active leader. · The DHCP server was not installed. · The zero touch provisioning service was starting up. · Permission limit. · Incorrect IP address. · Incorrect gateway IP address. · The number of address pools exceeded the upper limit (125). · The address pool overlapped with the existing address pools. · Failed to modify the DHCP configuration file. · Incorrect subnet mask. · Incorrect IP address range.

Delete address pool

Keyword	DELETE_ZTP_POOL_OP
Message text	Deleted address pool: $1
Variable fields	$1: Address pool information.
Example	Deleted address pool: IP range: 5.2.2.2-5.2.2.188
Explanation	An address pool was deleted.
Possible failure causes	· The controller was not the active leader. · The DHCP server was not installed. · The zero touch provisioning service was starting up. · Permission limit. · The address pool didn't exist. · Failed to modify the DHCP configuration file. · Incorrect IP address. · Incorrect IP address range.

Modify file server address

Keyword	MODIFY_FILESERVER_OP
Message text	Modified file server address: $1
Variable fields	$1: IP address of the local file server or URL of a third-party file server.
Example	Modified file server address: 192.168.1.3 Modified file server address: tftp://192.168.1.3/
Explanation	The file server address was modified.
Possible failure causes	· ZTP license was required. · The controller was not the active leader. · The DHCP server was not installed. · The zero touch provisioning service was starting up. · Permission limit. · Incorrect third-party file server address. · Failed to modify the DHCP configuration file. · Incorrect IP address.

Upload DHCP configuration file

Keyword	UPLOAD_DHCP_CONF_OP
Message text	Uploaded DHCP configuration file
Variable fields	N/A
Example	Uploaded DHCP configuration file
Explanation	A DHCP configuration file was uploaded.
Possible failure causes	· ZTP license was required. · The controller was not the active leader. · The DHCP server was not installed. · The zero touch provisioning service was starting up. · Permission limit. · Incorrect DHCP configuration file name. · Incorrect configuration format existed in the DHCP configuration file. · The device ID was already used. · The MAC address was already used. · The IP address was already used. · The address pool overlapped with the existing address pools. · The number of address pools exceeded the upper limit (125). · Failed to modify the DHCP configuration file. · Incorrect IP address.

Upload device configuration file

Keyword	UPLOAD_CFGGC_OP
Message text	Uploaded device configuration file
Variable fields	N/A
Example	Uploaded device configuration file
Explanation	A configuration file (.cfg) for physical network devices was uploaded through single-node provisioning.
Possible failure causes	· ZTP license was required. · Permission limit. · Incorrect device configuration file name. · Failed to save the device configuration file.

Upload device configuration file

Keyword	UPLOAD_CFGSC_OP
Message text	Uploaded device configuration file
Variable fields	N/A
Example	Uploaded device configuration file
Explanation	A configuration file (.cfg) for physical network devices was uploaded through multi-node provisioning.
Possible failure causes	· ZTP license was required. · Permission limit. · Incorrect device configuration file name. · Failed to save the device configuration file.

Upload device configuration file

Keyword	UPLOAD_CFGZIP_OP
Message text	Uploaded device configuration file
Variable fields	N/A
Example	Uploaded device configuration file
Explanation	A ZIP file containing configuration files for physical network devices was uploaded.
Possible failure causes	· ZTP license was required. · Permission limit. · Incorrect device configuration file name. · Failed to save the device configuration file.

Apply DHCP configuration

Keyword	ACTIVATE_OPENDHCP_OP
Message text	Applied DHCP configuration
Variable fields	N/A
Example	Applied DHCP configuration
Explanation	The DHCP configuration was applied.
Possible failure causes	· The controller was not the active leader. · The DHCP server was not installed. · The zero touch provisioning service was starting up. · Permission limit.

H3C VCF Controller Operation Log Messages Reference-5W222

CON_LISTENER

Assign an IP address to the loopback interface

Delete the IP address of the loopback interface

Clear BGP configuration

Back up configuration

Upload backup file

Download backup file

Modify configuration

Update VLAN-VXLAN mapping table

Delete VLAN-VXLAN mapping table

Bind VLAN-VXLAN mapping table

Update VLAN-VXLAN mapping table binding

Delete VLAN-VXLAN mapping table binding

Start migration on physical gateway