Download Book

Title	Size	Downloads
H3C SeerEngine-Campus Operation Log Messages Reference-E65XX-5W100-book.pdf	1.84 MB

Table of Contents

H3C SeerEngine-Campus Operation Log Messages Reference-E65XX-5W100

Related Documents


H3C SeerEngine-Campus
Operation Log Messages Reference

Document version: 5W100-20220725

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

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

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

Contents

Introduction· 1

Viewing operation log messages· 1

Syslog message format 2

Using this document 4

Campus· 6

Create isolation domain· 7

Update isolation domain· 9

Delete isolation domain· 11

Create isolate domain interconnect 12

Update isolate domain interconnect 13

Delete isolate domain interconnect 14

Create private network· 15

Update private network· 17

Delete private network· 18

Create security group· 19

Update security group· 22

Delete security group· 24

Create Layer 2 network domain· 25

Update Layer 2 network domain· 28

Delete Layer 2 network domain· 30

Create Layer 3 campus interconnect 30

Update Layer 3 campus interconnect 32

Delete Layer 3 campus interconnect 33

Create subnet 34

Update subnet 35

Delete subnet 36

Bind security group to access scenario· 37

Unbind security group from access scenario· 37

Modify access scenario priority· 38

Create authentication server 38

Update authentication server 39

Delete authentication server 39

Smooth EIA· 40

Create resource group· 41

Update resource group· 43

Delete resource group· 44

Create network range· 44

Delete network range· 45

CON_APP·· 46

Install application· 46

Start application· 46

Stop application· 46

Uninstall application· 47

Upload application· 47

CON_AUTH·· 48

Add an API authentication-free IP· 48

Delete an API authentication-free IP· 48

Add an IP address to white list 49

Delete an IP address from white list 49

CON_LICENSE·· 50

Connect the license server 50

Disconnect the license server 50

Upload license file· 51

Update the quantity of requested licenses· 51

CON_LISTENER·· 52

Update alert topic· 52

Remove alert topic· 53

CON_NetworkMonitor 54

Change thresholds for a CPU· 55

Change thresholds for all CPUs· 56

CON_OAM·· 57

Create radar detection task· 57

Delete radar detection task· 58

Clear periodic radar detection tasks· 58

CON_OPENFLOW··· 59

Create flow table entry· 59

Modify flow table entry· 59

Delete flow table entry· 59

Devices change to fail-safe mode· 60

Devices change to normal mode· 60

Create traditional NE· 64

Update traditional NE· 65

Delete traditional NE· 65

Start scanning traditional NE· 66

Stop scanning traditional NE· 66

CON_SYSTEM·· 67

Back up configuration· 67

Upload backup file· 67

Start recovery· 68

Download backup file· 68

Modify backup settings· 69

Modify configuration· 69

Restore configuration· 70

Prepare for upgrade· 70

Modify alert log remote transmission mode· 71

Modify audit log transmission mode· 71

Enter upgrade mode· 71

Quit upgrade mode· 72

Update device layer 77

Delete inactive link· 78

Update port thresholds· 78

Clear events on a device· 79

Clear events on all devices· 79

CON_USER·· 80

Add a user 80

Delete a user 80

Change user password· 81

Update user config· 82

Create DHCP server 86

Update DHCP server 87

Delete DHCP server 87

Synchronize data from DHCP server 88

Stop Synchronizing data from DHCP server 88

Update IP Conflict Detection from DHCP server 89

DHCP address pool 90

Create DHCP address pool 90

Update DHCP address pool 91

Delete DHCP address pool 91

Synchronize data from DHCP address pool 92

Stop Synchronizing data from DHCP address pool 92

DHCP IP bind· 93

Update DHCP IP bind· 93

DHCP forbidden IP·· 94

Create DHCP forbidden IP· 94

Delete DHCP forbidden IP· 94

DHCP option· 95

Add DHCP option· 95

Delete DHCP option· 96

Create Fabric Connection· 102

Update Fabric Connection· 103

Delete Fabric Connection· 104

General Group· 105

Create general group· 105

Update general group· 105

Delete general group· 106

Add device to device group· 106

Delete device from device group· 107

Add interface to interface group· 108

Delete interface from interface group· 109

Bind policy· 109

Unbind policy· 110

IDM·· 111

Add NETCONF template· 111

Update NETCONF template· 113

Delete NETCONF template· 114

Add configuration file· 115

Delete configuration file· 116

Deploy configuration snippets· 116

Deploy commands· 117

Start automatic configuration process· 117

Stop automatic configuration process· 118

Add SNMP template· 119

Delete SNMP template· 120

Update SNMP template· 121

Add aggregate interface· 122

Update aggregate interface· 123

Configure aggregate interface· 124

Add automated configuration template· 125

Add automation parameters· 127

Add automation policy· 128

Bring up interfaces· 129

Shut down interfaces· 130

Configure interface· 131

Add automatic device replacement task· 132

Add fabric and deploy resource pool 133

NBAC·· 135

Create Application Description· 136

Update Application Description· 138

Delete Application Description· 139

Create Time Range· 148

Update Time Range· 149

Delete Time Range· 150

Create intergroup policy· 150

Update intergroup policy· 151

Created policy enforcement device group· 152

Updated policy enforcement device group· 153

Deleted policy enforcement device group· 154

NEM·· 155

Create VLAN-VXLAN mapping table· 155

Update VLAN-VXLAN mapping table· 155

Delete VLAN-VXLAN mapping table· 156

Create QinQ-VXLAN mapping table· 157

Update QinQ-VXLAN mapping table· 158

Delete QinQ-VXLAN mapping table· 160

Bind VLAN-VXLAN mapping table· 160

Update VLAN-VXLAN mapping table binding· 161

Delete VLAN-VXLAN mapping table binding· 161

Bind ports to VLAN-VXLAN mapping table· 162

Update bindings between ports and VLAN-VXLAN mapping table· 162

Delete bindings between ports and VLAN-VXLAN mapping table· 163

Bind ports to QinQ-VXLAN mapping table· 164

Update bindings between ports and QinQ-VXLAN mapping table· 164

Delete bindings between ports and QinQ-VXLAN mapping table· 165

Create gateway group· 166

Update gateway group· 168

Delete gateway group· 169

Create IP address pool 170

Update IP address pool 171

Delete IP address pool 172

Create gateway group VLAN range· 173

Update gateway group VLAN range· 173

Delete gateway group VLAN range· 174

Create VXLAN pool 174

Update VXLAN pool 175

Delete VXLAN pool 176

Create physical NE· 176

Update physical NE· 178

Delete physical NE· 180

Reboot physical NE· 181

Batch add physical NEs· 181

Start scanning physical NE· 182

Stop scanning physical NE· 182

Start migration on physical gateway· 182

Complete migration on physical gateway· 183

Start data synchronization on physical NE· 183

Start configuration auditing on physical NE· 184

Start data synchronization on virtual NE· 184

Start configuration auditing on virtual NE· 184

Create NETCONF default user 185

Configure default MAC address· 185

Delete default MAC address· 186

Create third party NE· 186

Delete third party NE· 187

Configure reserved option· 187

Create address pool 188

Update address pool 188

Delete address pool 189

Add resource· 189

Delete resource· 191

Configure VNFM·· 192

Configure gateway network· 192

Update gateway network· 193

Router bound to gateway· 193

Create aggregation group member 194

Update aggregation group member 195

Delete aggregation group member 195

Create aggregation group· 196

Update aggregation group· 196

Delete aggregation group· 197

Create global aggregation group configuration· 197

Update global aggregation group configuration· 198

Delete global aggregation group configuration· 199

Delete NE VXLAN tunnels· 199

Create connection limit rule· 199

Update connection limit rule· 200

Delete connection limit rule· 201

Create device configuration template· 201

Update device configuration template· 205

Delete device configuration template· 207

Create control protocol template· 208

Update control protocol template· 209

Delete control protocol template· 210

Create deploy resource pool 210

Update deploy resource pool 211

Delete deploy resource pool 212

Create auto detected· 213

Stop auto detected· 214

Delete auto detected· 214

Update global setting· 214

Create manual backup· 215

Recover configuration· 216

Create DHCP server 216

Update DHCP server 217

Delete DHCP server 217

Upload software· 218

Update software· 218

Delete software· 219

Upgrade software· 220

Replace physical NE· 220

Create tenant-gateway binding relationship· 222

Update tenant-gateway binding relationship· 222

Delete tenant-gateway binding relationship· 223

Create gateway· 223

Update gateway· 225

Delete gateway· 226

Create gateway member 226

Update gateway member 227

Delete gateway member 228

Create device whitelist 228

Update device whitelist 229

Delete device whitelist 230

Delete assetlist 230

Create egress interface· 231

Update egress interface· 233

Delete egress interface· 234

Create external connectivity· 235

Update external connectivity· 235

Delete external connectivity· 236

Add AAA template· 237

Update AAA template· 239

Delete AAA template· 240

Add MAC template· 241

Update MAC template· 243

Delete MAC template· 244

Add 802.1X template· 245

Update 802.1X auth template· 247

Delete 802.1X auth template· 248

Synchronization device bridgeMac and serialNumber infor 249

Create replacement task· 250

Delete replacement task· 251

Add Redundant Port 253

Update Redundant Port 253

Delete Redundant Port 254

Batch import wireless APs to ACs· 254

Synchronization ACs info· 254

Delete APs from the AC· 255

Redeployed traditional access devices· 255

Create third-party service device· 256

Update third-party service device· 257

Delete third-party service device· 258

Create third-party service· 259

Update third-party service· 260

Delete third party service· 260

Create third-party device config template· 261

Update third-party device config template· 262

Delete third-party device config template· 263

Add configuration task· 263

Delete configuration task· 264

Add failure signature· 264

Delete failure signature· 265

Add Step· 266

Update Step· 267

Delete Step· 268

Copy existing template· 268

Create FW Resource· 269

Update FW Resource· 271

Delete VFW Resource· 271

Create GW Member 272

Update GW Member 272

Create External Interface· 273

Update External Interface· 273

Create Extenal Network· 274

Smooth Asset and Template· 274

Create Server Resource· 275

Update Server Resource· 276

Delete Server Resource· 277

Create campus full mesh· 277

Delete campus full mesh· 278

Create auth free template· 278

Delete auth free template· 279

Create SSM mapping· 286

Delete SSM mapping· 286

Create SSM mapping rule· 287

Delete SSM mapping rule· 287

Create Network Range· 287

Delete Network Range· 288

Create Device_websocket info· 289

Delete Device_websocket info· 289

Create SGT Pools· 289

Update SGT Pools· 290

Delete SGT Pools· 291

Add Auth Config· 291

Update Auth Config· 292

Delete Auth Config· 292

Add Inter Auth Config· 293

Update Inter Auth Config· 293

Delete Inter Auth Config· 294

Add Interface_isolate· 295

Update Interface_isolate· 295

Delete Interface_isolate· 296

Add bras interconnect fabric· 297

Update bras interconnect fabric· 297

RCAM·· 299

Create resource access template· 299

Delete resource access template· 300

ServiceChain· 301

Create service chain· 302

Update service chain· 304

Delete service chain· 305

SITE·· 306

Create Site table· 306

Update Site table· 307

Delete Site table· 308

Create internal route· 317

Delete internal route· 317

Create interface· 318

Delete interface· 319

Create network policy· 325

Update network policy· 326

Delete network policy· 326

Create security policy· 327

Update security policy· 327

Delete security policy· 328

Create floating IP· 329

Update floating IP· 330

Delete floating IP· 331

Create port group· 331

Update port group· 332

Delete port group· 332

Create security rules· 333

Update security rule· 334

Delete security rule· 335

Authenticate with vCenter 335

Disconnect with vCenter 336

Create router link· 344

Update router link· 344

Delete router link· 345

Create route table· 345

Update route table· 346

Delete route table· 346

Create route entry· 347

Update route entry· 347

Delete route entry· 348

Create APP cluster VIP· 348

Update APP cluster VIP· 349

Delete APP cluster VIP· 349

Create flooding domain· 350

Update flooding domain· 351

Delete flooding domain· 351

Update vCenter status· 352

Create port name prefix· 352

Delete vPort prefix name· 353

Update advanced setting· 353

Create netoverlay host 354

Delete netoverlay host 354

Update netoverlay host 355

Create netoverlay group· 355

Delete netoverlay group· 356

Create VLAN-VXLAN map· 356

Delete VLAN-VXLAN map· 357

Configure batch vSwitch deployment parameters· 357

Import host file· 357

Run custom script 358

Export host file· 358

Export SSH key· 358

Upload custom script 359

Install vSwitch· 359

Update vSwitch· 359

Uninstall vSwitch· 360

Check host status· 360

Upload vSwitch file· 360

Delete vSwitch file· 361

Create network nodes· 361

Update network node· 362

Delete network node· 362

Update global default action· 362

Create DFW policy· 363

Update DFW policy· 363

Delete DFW policy· 364

Create DFW policy rule· 365

Delete DFW policy rule· 366

Create DFW IP set 366

Update DFW IP set 367

Delete DFW IP set 367

Create DFW IP set rule· 368

Delete DFW IP set rule· 368

Track flow entry of IP packet 369

Track flow entry of ARP packet 370

Start auditing on host 371

Start synchronization on host 371

Created static link· 372

Deleted static link· 372

Create vRouter interconnection· 373

Update vRouter interconnection· 374

Delete vRouter interconnection· 375

Create Layer 2 DC interconnection· 375

Update Layer 2 DC interconnection· 376

Delete Layer 2 DC interconnection· 376

Create Layer 3 DC interconnection· 377

Update Layer 3 DC interconnection· 379

Delete Layer 3 DC interconnection· 380

Add subnet to Layer 3 DC interconnection· 380

Delete Layer 3 DC interconnection subnet 381

Upload the vSwitch license file· 381

Updated host load limit 382

Introduction

Operation logs record system operations and configuration modifications, such as device operations (adding, editing, or deleting a device) and policy 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 SeerEngine-Campus controller products.

Viewing operation log messages

The SeerEngine-Campus product is deployed based on the H3C SNA Center platform. To view the operation log messages:

1. Log in to SNA Center.

2. Click Settings.

3. On the top navigation bar, click Logs.

4. From the navigation pane, select Information.

5. Click the Operation Logs tab.

6. Select SeerEngine-Campus from the SNA Component Name list, and click Query.

The generated SeerEngine-Campus operation log messages are displayed as shown in Figure 1.

Figure 1 Operation log messages

Table 1 Operation log message elements

Element	Description
Time	Date and time when the log message was generated.
SNA Component Name	Name of the SNA component that produced the message.
Username	Name of the user that triggered the log generation.
User IP	IP address of the terminal where the user performed the operation.
Host Name	Name of the host that produced the message.
Service Name	Name of the service that produced the message.
Module Name	Name of the module that produced the message.
Operation Result	Operation result: Succeeded or Failed.
Operation Description	Text string that contains detailed information about the operation.
Failure Reason	Possible reasons for an operation failure.

Syslog message format

SeerEngine-Campus controllers can send operation logs to syslog servers through the syslog protocol. To set the IP addresses and port numbers of syslog servers:

1. On the top navigation bar, click Logs.

2. From the navigation pane, select Configuration.

3. Click the Operation Logs tab.

4. Set the IP addresses and port numbers of syslog servers.

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
Campus	Policy management module.
CON_APP	Application management module.
CON_AUTH	Authentication management module.
CON_LICENSE	License management module.
CON_LISTENER	Listener module.
CON_NetworkMonitor	Network monitoring module.
CON_OAM	OAM module.
CON_OPENFLOW	OpenFlow module.
CON_REGION	Region module.
CON_SNMP	SNMP module.
CON_SYSTEM	System management module.
CON_TEAM	Team module.
CON_TOPOLOGY	Topology management module.
CON_USER	User management module.
DHCP	DHCP module.
Fabric	Fabric module
GeneralGroup	General group module.
IDM	Integrated deployment module.
NBAC	Network-based access control module.
NEM	Carrier network module.
ServiceChain	Service chain module.
VSM	Virtual network 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 categorizes 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.	DELETE_FABRIC_OP
Message text	Presents the message description.	Deleted fabric: $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: Fabric UUID.
Example	Provides a real message example.	Deleted fabric: 218b5f2f-e435-4365-a1ab-0eaa03b7fa19
Explanation	Explains the message.	A fabric was deleted.
Possible failure causes	Provides possible causes of an operation failure.	· Configuration recovery is in progress. · The service has not been found. · The controller is not the active leader. · The fabric does not exist. · Unknown error. · The request is invalid. · The fabric has devices. · The fabric has border device groups. · …

Campus

This section contains operation log messages of the campus module.

Create isolation domain

Keyword	CREATE_ISOLATE_DOMAIN_OP
Message text	Created isolation domain “$1”.
Variable fields	$1: Isolation domain name.
Example	Created isolation domain “domain1”.
Explanation	An isolation domain was created.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · Unknown error. · The isolation domain name cannot exceed 62 characters. · The isolation domain name is required. · The isolation domain ID already exists. · The isolation domain name already exists. · Invalid VXLAN ID range. · Duplicated IDs exist for the isolation domains created in bulk. · Duplicated names exist for the isolation domains created in bulk. · The VLAN pool cannot be empty. · The VLAN pool does not exist. · Failed to create the isolation domain. Errors occurred during tenant creation. · The DHCP server does not exist. · The service is disabled. · The VXLAN ID range must contain 4092. · In a DHCP network in tight coupling mode, to bind a DHCP server to an isolation domain, make sure the DHCP server is up. · Invalid wireless forwarding mode. · Failed to synchronously create the address pool. An address pool with the same name already exists. · Failed to synchronously create the address pool. An address pool with the same network segment already exists. · To bind a DHCPv4 server in tight collaboration mode to an isolation domain, make sure the DHCPv4 server is up. · The specified DHCP server does not support IPv4. · The specified DHCP server does not support IPv6. · To bind a DHCPv6 server in tight collaboration mode to an isolation domain, make sure the DHCPv6 server is up. · To bind a DHCPv4 server in tight collaboration mode to a security group, make sure the DHCPv4 server is up. · To bind a DHCPv6 server in tight collaboration mode to a security group, make sure the DHCPv6 server is up. · The DHCPv4 server doesn't exist. · The DHCPv6 server doesn't exist. · Authentication server is not synchronized. · Failed to bind the fabric to the isolation domain, because the isolation domain has already been configured with a full-mesh fabric connection and the fabric has been enabled with multicast network capabilities. · The ARP scan and probe rate is out of range. · The ND scan and probe rate is out of range. · The ARP scan and probe rate must be a multiple of 10. · The ND scan and probe rate must be a multiple of 10. · You cannot specify the same isolation domain for both the router server and a client of the route server. · You cannot specify the same exit device for both the route server and a client of the route server. · You cannot disable IP security group tag subscription when VLAN preprovisioning for WLAN is enabled. · You cannot change the state of selective VXLAN deployment when group-based policy mode is used.

Update isolation domain

Keyword	UPDATE_ISOLATE_DOMAIN_OP
Message text	Updated isolation domain “$1”.
Variable fields	$1: Isolation domain name.
Example	Updated isolation domain “domain1”.
Explanation	An isolation domain was updated.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · Unknown error. · The isolation domain does not exist. · The VXLAN ID range cannot be modified. · The isolation domain name cannot be modified. · The VLAN pool cannot be empty. · Cannot modify the VLAN pool because the isolation domain has security groups. · The VLAN pool does not exist. · Failed to modify the isolation domain. Errors occurred during the DHCP server update process. · The service is disabled. · In a DHCP network in tight coupling mode, to bind a DHCP server to an isolation domain, make sure the DHCP server is up. · Invalid wireless forwarding mode. · The specified resource doesn't exist. · If no DNS servers are specified, the subnet will use the DNS servers specified for its isolation domain. · To bind a DHCPv4 server in tight collaboration mode to an isolation domain, make sure the DHCPv4 server is up. · The specified DHCP server does not support IPv4. · The specified DHCP server does not support IPv6. · To bind a DHCPv6 server in tight collaboration mode to an isolation domain, make sure the DHCPv6 server is up. · Failed to edit the DHCPv4 server for the isolation domain. · To bind a DHCPv4 server in tight collaboration mode to a security group, make sure the DHCPv4 server is up. · To bind a DHCPv6 server in tight collaboration mode to a security group, make sure the DHCPv6 server is up. · Cannot edit the policy mode of the isolation domain, because it has been bound to a Layer 2 network domain. · Cannot edit the policy mode of the isolation domain, because fabrics have been bound to the isolation domain. · Cannot edit the isolation domain, because its BYOD security group is used by an authentication server. · The DHCPv4 server doesn't exist. · The DHCPv6 server doesn't exist. · Authentication server is not synchronized. · Failed to bind the fabric to the isolation domain, because the isolation domain has already been configured with a full-mesh fabric connection and the fabric has been enabled with multicast network capabilities. · You cannot edit the policy mode for user-defined isolation domains. · The ARP scan and probe rate is out of range. · The ND scan and probe is out of range. · The ARP scan and probe must be a multiple of 10. · The ND scan and probe rate must be a multiple of 10. · Failed to change the enabling status of IP-security group tag subscription, because the isolation domain has been added to an isolation domain interconnect. · You cannot specify the same isolation domain for both the router server and a client of the route server. · You cannot specify the same exit device for both the route server and a client of the route server. · You cannot change the policy mode of the isolation domain,because the isolation domain is bound to a security group. · Invalid isolation domain type. · The VLAN preprovisioning for WLAN of the isolation domain cannot be modified. · You cannot change the state of selective VXLAN deployment when group-based policy mode is used. · You cannot change the state of selective VXLAN deployment, because Layer 2 network domains exist in the isolation domain · You cannot change the setting of Level 2 DHCP relay, because the isolation domain is already bound to a Layer 2 network domain.

Delete isolation domain

Keyword	DELETE_ISOLATE_DOMAIN_OP
Message text	Deleted isolation domain “$1”.
Variable fields	$1: Isolation domain name.
Example	Deleted isolation domain “domain1”.
Explanation	An isolation domain was deleted.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · Unknown error. · Failed to delete the isolation domain because the isolation domain has private networks. · The isolation domain is the default isolation domain and cannot be deleted. · The isolation domain has been used by isolation domain interconnect and cannot be deleted. · Cannot delete the specified isolation domain,because it has fabric connections. · The service is disabled. · The specified resource doesn't exist. · Cannot delete the isolation domain because its default private network vpn-default has security groups. · Cannot delete the isolation domain because its default private network vpn-default has resource groups. · Cannot delete the isolation domain because its default private network vpn-default has Layer 2 network domains. · Cannot delete the isolation domain because its BYOD security group is used by an authentication server. · Authentication server is not synchronized. · You cannot delete the isolation domain, because it has been bound to security groups. · You cannot delete the isolation domain, because it has policy enforcement device groups

Create isolate domain interconnect

Keyword	CREATE_ISOLATE_DOMAIN_INTERCONNECT_OP
Message text	Created isolation domain interconnect “$1”
Variable fields	$1: Isolation domain interconnect parameters.
Example	Created isolation domain interconnect: ID: connect Name: isolation interconnect Description":"Isolation domain interconnect", Interconnect members":[ { Isolate domain ID: db57e239-025f-45d7-bd75-246fdf2acdc7 Ed device ID: 6d0f85d6-5460-4e09-b384-9654836bbb70 Ed device name: Device1 }, { Isolate domain ID: db57e239-025f-45d7-bd75-246fdf2acdc7 Ed device ID: 6d0f85d6-5460-4e09-b384-9654836bbb70 Ed device name: Device1 }, ]
Explanation	An isolation domain interconnect was created.
Possible failure causes	· Invalid license. · The controller is not the active leader. · Configuration recovery is in progress. · The service is disabled. · The specified resource doesn't exist. · The request is invalid. · Unknown error. · The isolation domain interconnect with the specified ID already exists. · The isolation domain interconnect name cannot be empty. · The isolation domain interconnect name can contain up to 255 characters. · The isolation domain interconnect with the specified name already exists. · The isolation domain interconnect description can contain up to 255 characters. · The isolation domain interconnect ID cannot be empty. · The isolation domain interconnect with the specified ID does not exist. · The isolation domain interconnect must contain a minimum of two members. · The IDs of isolation domain interconnects to be bulk created cannot be duplicated. · The names of isolation domain interconnects to be bulk created cannot be duplicated. · The member IDs in the same isolation domain interconnect cannot be duplicated. · Some members in the isolation domain interconnect to be created are already assigned to another isolation domain interconnect. · The members of the isolation domain interconnect cannot be empty. · The enabling status of IP-security group tag subscription must be consistent across all isolation domain members on the isolation domain interconnect. · The member isolation domains must use the same policy mode.

Update isolate domain interconnect

Keyword	UPDATE_ISOLATE_DOMAIN_INTERCONNECT_OP
Message text	Updated isolation domain interconnect: “$1”
Variable fields	$1: Isolation domain interconnect parameters.
Example	Updated isolation domain interconnect: Description":"Isolation domain interconnect", Interconnect members": [ { Isolate domain ID: db57e239-025f-45d7-bd75-246fdf2acdc7 Ed device ID: 6d0f85d6-5460-4e09-b384-9654836bbb70 Ed device name: Device2 }, { Isolate domain ID: db57e239-025f-45d7-bd75-246fdf2acdc7 Ed device ID: 6d0f85d6-5460-4e09-b384-9654836bbb70 Ed device name: Device2 }, ]
Explanation	An isolation domain interconnect was edited.
Possible failure causes	· Invalid license. · The controller is not the active leader. · Configuration recovery is in progress. · The service is disabled. · The specified resource doesn't exist. · The request is invalid. · Unknown error. · The isolation domain interconnect ID cannot be empty. · The isolation domain interconnect with the specified ID does not exist. · The isolation domain interconnect must contain a minimum of two members. · The IDs of isolation domain interconnects to be bulk created cannot be duplicated. · Some members in the isolation domain interconnect to be created are already assigned to another isolation domain interconnect. · The isolation domain interconnect ID cannot be edited. · The isolation domain interconnect name cannot be edited. · The members of the isolation domain interconnect cannot be empty. · The enabling status of IP-security group tag subscription must be consistent across all isolation domain members on the isolation domain interconnect. · The member isolation domains must use the same policy mode.

Delete isolate domain interconnect

Keyword	DELETE_ISOLATE_DOMAIN_INTERCONNECT_OP
Message text	Deleted isolation domain interconnect: “$1”
Variable fields	$1: Isolation domain interconnect name.
Example	Deleted isolation domain interconnect: connect
Explanation	An isolation domain interconnect was deleted.
Possible failure causes	· Invalid license. · The controller is not the active leader. · Configuration recovery is in progress. · The service is disabled. · The specified resource doesn't exist. · The request is invalid. · Unknown error.

Create private network

Keyword	CREATE_PRIVATE_NETWORK_OP
Message text	Created private network “$1”.
Variable fields	$1: Private network name.
Example	Created private network “vpn1”.
Explanation	A private network was created.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · The description cannot exceed 255 characters. · The L3VNI is out of range. · The segment ID has been used. · VXLAN 4094 is reserved. · The IP address of the DNS server is invalid. · The VPN instance name is required. · The VPN instance name cannot exceed 31 characters. · The VPN instance name already exists. · The number of DNS servers on the DNS relay agent cannot exceed 8. · Duplicated DNS server IP addresses exist. · The isolation domain ID does not exist. · The private network name is required. · The private network name cannot exceed 255 characters. · The private network ID already exists. · The private network name already exists. · Unknown error. · The service is disabled. · VXLAN 4093 is reserved. · VXLAN 1 is reserved. · The VPN name is already used. · The VPN instance name is case sensitive. Valid characters are letters, digits, underscores (_), and hyphens (-). · The default action is required. · Supported default actions are permit and deny. · No available VXLAN IDs. · The segment ID is out of range. · The segment ID has been used. · No available segment IDs. · Segment 1, Segment 4092, and Segment 4094 are reserved and cannot be used. · Cannot bind a gateway with the firewall function enabled to the private network, because the private network is in group-based policy mode. · The private network name cannot start with ' SDN_SC_'. · The VPN instance name cannot start with ' SDN_SC_' · The default private network and a user-defined private network cannot both be bound to a gateway. · Make sure the isolation domain of each gateway member bound to the private network is configured with the same policy mode as the private network. · To apply the policy to IPv6 users, please first enable IPv6 in the controller global settings. · Invalid method for communication with vpn-default. · The egress IPv4 addresses of border gatewa members mustbe in different subnets · The egress Ipv6 addresses of border gatewa members mustbe in different subnets

Update private network

Keyword	UPDATE_PRIVATE_NETWORK_OP
Message text	Updated private network “$1”.
Variable fields	$1: Private network name.
Example	Updated private network “vpn1”.
Explanation	A private network was updated.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · The private network does not exist. · The private network ID cannot be modified. · The private network name cannot be modified. · The isolation domain ID cannot be modified. · The VPN instance name cannot be modified. · The IP address of the DNS server is invalid. · The description cannot exceed 255 characters. · The number of DNS servers on the DNS relay agent cannot exceed 8. · Unknown error. · The service is disabled. · The specified resource doesn't exist. · The segment ID cannot be modified. · Cannot unbind or replace the border gateway for the private network because a security group in the private network is being used by a security server · Cannot edit the policy mode of the private network, because it has been bound to Layer 2 network domains. · Cannot edit the object to which the policy is applied, because it has been bound to Layer 2 network domains. · Cannot edit the policy mode of the private network, because it has been bound to security groups. · Cannot edit the policy mode of the private network, because it has been bound to resource groups. · A service chain policy template has been applied to this private network. The policy application scope cannot include IPv6 users. · Cannot edit the object to which the policy is applied, because it has been bound to Layer 2 network domains. · Cannot edit the policy mode of the private network, because it has been bound to security groups. · Cannot edit the policy mode of the private network, because it has been bound to resource groups. · Cannot edit the private network because it is being used by a Layer 3 multicast network. · Cannot edit the border gateway, because the private network has a Layer 3 campus interconnect configured. · Cannot enable multicast network capabilities for the private network because the private network has been bound to a Layer 3 campus interconnect. · Cannot bind a gateway with the firewall function enabled to the private network, because the private network is in group-based policy mode. · Cannot change the policy mode of the private network to group-based, because a firewall has been attached to a gateway of the private network. · The default private network and a user-defined private network cannot both be bound to a gateway. · The private network has been bound to a firewall service. You cannot detach the private network from the egress gateway. · Cannot edit the policy mode of the private network, because it has been bound to a gateway. · To apply the policy to IPv6 users, please first enable IPv6 in the controller global settings · Cannot edit the method for communication with vpn-default of the private network, because it has been bound to security groups. · Cannot edit the method for communication with vpn-default of the private network, because it has been bound to Layer 2 network domains · The egress IPv4 addresses of border gatewa members mustbe in different subnets · The egress Ipv6 addresses of border gatewa members mustbe in different subnets

Delete private network

Keyword	DELETE_PRIVATE_NETWORK_OP
Message text	Deleted private network “$1”.
Variable fields	$1: Private network name.
Example	Deleted private network “vpn1”.
Explanation	A private network was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · The default private network cannot be deleted. · The private network cannot be deleted because it has security groups. · Unknown error. · The service is disabled. · The private network cannot be deleted because it has resource groups. · The specified resource doesn't exist. · The private network does not exist. · Cannot delete the private network because it is being used by a Layer 3 network. · Cannot delete the private network, because a firewall has been attached to a gateway of the private network.

Create security group

Keyword	CREATE_SECURITYGROUP_OP
Message text	Created security group “$1”.
Variable fields	$1: Security group name.
Example	Created security group “sg1”
Explanation	A security group was created.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · The security group name is required. · The security group name cannot exceed 64 characters. · The private network ID is required. · Invalid security group type. · VXLAN 4094 is reserved. · The VXLAN ID is out of range. · The VSI interface description cannot exceed 251 characters. · The VSI MAC address is invalid. · A maximum of seven ACs can be configured. · The IP address of the AC is invalid. · Duplicated IP addresses exist for the ACs. · The security group ID already exists. · Duplicated security group IDs exist for the security groups created in bulk. · The security group name already exists. · Duplicated security group names exist for the security groups created in bulk. · The VLAN ID of the security group is invalid. · The VXLAN ID has been used. · The VLAN ID has been used. · Unknown error. · The service is disabled. · The BYOD security group can be configured only in the default private network. · Only can configure ACs when security group is wireless type. · Only one wireless security group can be configured in an isolation domain. · Only one critical security group can be configured in an isolation domain. · The AC ips is required. · In a DHCP network in tight coupling mode, to bind a DHCP server to a security group, make sure the DHCP server is up. · The DHCP server does not exist. · Only one BYOD security group can be configured. · Failed to add the security group because no available campus app license exists. · VLAN 4093 is reserved. · VXLAN 4093 is reserved. · VXLAN 1 is reserved. · The VLAN ID is out of range. · No available VXLAN IDs. · The DHCP server can be configured only for a critical or BYOD security group. · No available VLAN IDs. · The specified Layer 2 network domain does not exist. · A security group can be bound to only one Layer 2 network domain of one isolation domain. · The security group and the Layer 2 network domain to be bound must be of the same type. · The Layer 2 network domain has been bound to another security group. · Each of the Layer 2 network domains bulk created cannot be bound to multiple security groups. · A security group can be bound to only one Layer 2 network domain in the current software version. · An external network security group cannot be configured with Layer 2 network domains. · The security group is not configured with a Layer 2 network domain. · Only one external network security group can be configured in a private network. · An external network security group does not support specifying a VLAN ID. · An external network security group does not support specifying a VXLAN ID. · An external network security group does not support enabling DHCP. · An external network security group does not support enabling ARP proxy. · An external network security group does not support enabling ARP detection. · An external network security group does not support enabling IGMP snooping. · An external network security group does not support enabling allowing Layer 2 applications. · An external network security group does not support setting the VSI interface description. · An external network security group does not support setting the VSI MAC. · Wireless security groups can be configured only in the default private network. · The private network does not exist. · The Primary parameter cannot be empty. · The parent security group with the specified UUID does not exist. · Cannot specify a SGT in group-based policy mode. · Invalid value for the maximum number of security subgroups. · Make sure the security subgroups use the same policy mode as their parent security group. · Make sure the security subgroups are associated with the same private network as their parent security group. · The type is different with primary security group. · The child security group does not support to bind l2 network domain. · The security groups created in a private network must be configured with the same policy mode as the private network. · Cannot edit the policy mode of the security group. · The security group name cannot be the same as the BYOD security group name. · The security subgroup name already exists. · Please specify the Primary parameter. · The type of the security subgroup is different than the parent security group. · The security subgroup does not support binding to a Layer 2 network domain. · The name is reserved for the default security group. Please specify another one. · The security group and the Layer 2 network domain are not in the same private network. · The isolation domains bound to the critical security group conflict with those bound to another critical security group. · Only a normal or critical security group can be bound to isolation domains · Only a parent security group can be bound to isolation domains. · Only a security group with the group-based policy mode can be bound to isolation domains. · An external network security group does not support specifying a SGT. · No available SGTs. · You must select at least the isolation domains of all Layer 2 network domains bound to the security group. · A security group already exists with the specified SGT ID. · You cannot both configure the security subgroup and manually specify an SGT. · The SGT ID is out of range. · You must select at least the isolation domains of all Layer 2 network domains bound to the security group. · A VLAN network does not support configuring private networks for a security group. · Invalid network type for the security group. · You can create only one security group of the external network type. · You can specify an isolation domain for a security group only when the security group type is Normal, Critical, Guest, Authentication Failure, or AuthFree. · Only a normal or critical security group can be bound to isolation domains

Update security group

Keyword	UPDATE_SECURITYGROUP_OP
Message text	Updated security group “$1”.
Variable fields	$1: Security group name.
Example	Updated security group ”sg1”
Explanation	A security group was updated.
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. · The security group ID cannot be modified. · The private network ID cannot be modified. · The security group type cannot be modified. · The subnets cannot be modified. · The VLAN ID cannot be modified. · The ARP proxy settings cannot be modified. · The VSI interface description cannot be modified. · The VSI MAC address cannot be modified. · The ARP check settings cannot be modified. · The IGMP snooping settings cannot be modified. · The DHCP enabling state is required. · The Layer 2 application settings cannot be modified. · The security group name already exists. · Unknown error. · The service is disabled. · Cannot edit the DHCP server when DHCP is enabled. · Cannot edit the DHCP enabling state for the security group because it is being used by an authentication server. · Cannot edit the DHCP server for the security group because it is being used by an authentication server. · The specified Layer 2 network domain does not exist. · The security group and the Layer 2 network domain to be bound must be of the same type.. · A security group can be bound to only one Layer 2 network domain of one isolation domain. · he security group and the Layer 2 network domain to be bound must be of the same type. · Each of the Layer 2 network domains bulk created cannot be bound to multiple security groups. · A security group can be bound to only one Layer 2 network domain in the current software version. · Cannot remove the Layer 2 network domain binding of the security group because the security group is being used in an inter-group policy. · Cannot remove the Layer 2 network domain binding of the security group because the security group is being used by an authentication server. · Cannot remove the Layer 2 network domain binding of the security group because the security group is being used in a Layer 3 campus interconnect. · An external network security group cannot be configured with Layer 2 network domains. · The security group is not configured with a Layer 2 network domain. · An external network security group does not support enabling DHCP. · Cannot unbind or replace the Layer 2 network domain for the security group because the security group is being used by a security server. · The child security group does not support to bind Layer 2 network domain. · The security subgroup name already exists. · Cannot edit the list of Layer 2 network domains bound to the security group. The security group has been used on an authentication server. · Authentication server is not synchronized. · VLAN 4093 is reserved. · The VLAN ID has been used. · The VLAN ID of the security group is invalid. · The VLAN ID is out of range. · An external network security group does not support specifying a VLAN ID. · Cannot delete the Layer 2 network domain. It has been bound to an authentication-free policy template. · The security group and the Layer 2 network domain are not in the same private network. · The isolation domains bound to the critical security group conflict with those bound to another critical security group. · Only a normal or critical security group can be bound to isolation domains. · Only a parent security group can be bound to isolation domains. · Only a security group with the group-based policy mode can be bound to isolation domains. · You must select at least the isolation domains of all Layer 2 network domains bound to the security group. · You can specify an isolation domain for a security group only when the security group type is Normal, Critical, Guest, Authentication Failure, or AuthFree. · Only a normal or critical security group can be bound to isolation domains.

Delete security group

Keyword	DELETE_SECURITYGROUP_OP
Message text	Deleted security group “$1”.
Variable fields	$1: Security group name.
Example	Deleted security group ”sg1”.
Explanation	A security group was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · The specified resource doesn't exist. · Failed to delete the security group. The security group is being used by the authentication server. · Unknown error. · The service is disabled. · The security group which is used by application description cannot be deleted. · Cannot delete the security group because it is being used by a security server. · The security group cannot be deleted because it contains security subgroups. · Cannot delete the security subgroup because it has been used in an exception group policy rule. · Authentication server is not synchronized. · The wireless AC's IP cannot be a subnet gateway IP.

Create Layer 2 network domain

Keyword	CREATE_L2NETWORKDOMAIN_OP
Message text	Created Layer 2 network domain: “$1”
Variable fields	$1: Layer 2 network domain configuration parameters.
Example	Created Layer 2 network domain: Name: [l2NetworkDomain1]
Explanation	A Layer 2 network domain was added.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · Layer 2 network domain names cannot be duplicated. · Layer 2 network domain IDs cannot be duplicated. · The specified segment ID is already used. · The wireless ACs can be configured only for wireless Layer 2 network domains. · The Layer 2 network domain with the specified ID already exists. · The Layer 2 network domain name cannot be empty. · The Layer 2 network domain name can contain up to 255 characters. · The Layer 2 network domain with the specified name already exists. · Invalid Layer 2 network domain type. · BYOD Layer 2 network domains can be configured only in the default private network. · An isolation domain can be bound to only one BYOD Layer 2 network domain. · An isolation domain can be bound to only one wireless Layer 2 network domain. · An isolation domain can be bound to only one auth-fail Layer 2 network domain. · The DHCP server can be configured only for critical or BYOD Layer 2 network domain. · To bind a DHCP server in tight collaboration mode to a security group, make sure the DHCP server is up. · To bind a DHCPv4 server in tight collaboration mode to an isolation domain, make sure the DHCPv4 server is up. · The specified DHCP server does not support IPv4. · The specified DHCP server does not support IPv6. · To bind a DHCPv6 server in tight collaboration mode to an isolation domain, make sure the DHCPv6 server is up. · To configure a DHCPv4 server, make sure the IPv4 address assignment mode is DHCP. · To bind a DHCPv4 server in tight collaboration mode to a security group, make sure the DHCPv4 server is up. · To bind a DHCPv6 server in tight collaboration mode to a security group, make sure the DHCPv6 server is up. · To configure a DHCPv6 server, make sure the IPv6 address allocation method is stateful DHCPv6 or stateless DHCPv6. · Wireless Layer 2 network domains can be configured only in the default private network. · The isolate domain does not exist. · The segment ID is out of range. · The segment ID has been used. · No available segment IDs. · Segment 1, Segment 4092, and Segment 4094 are reserved and cannot be used. · The subnet gateway address cannot be the same as the IP address of the ingress or egress port of a service member. · The AC IP address conflicts with an existing IP address pool or with the management IP address of a device. · The AC IP cannot be contained in CIDRs of any other Layer 2 network domain. · The AC IP cannot be any subnet gateway IP of the Layer 2 network domain. · The isolation domain does not exist. · The specified private network does not exist. · IPv6 ND detection and ND snooping cannot be both enabled. · ARP packet validity check and ARP snooping cannot be both enabled. · Cannot specify a policy mode for a Layer 2 network domain. · The AC IP cannot be contained in CIDRs of any other Layer 2 network domain. · The AC IP cannot be any subnet gateway IP of the Layer 2 network domain. · Cannot change the IPv6 address allocation mode because the Layer 2 network domain contains an IPv6 subnet. · You can enable the IGMP snooping dropping unknown multicast packets feature only when multicast network capabilities are enabled. · You can enable the IGMP snooping querier only when multicast network capabilities are enabled. · You can enable the IGMP snooping proxy only when multicast network capabilities are enabled. · The Layer 2 network domain name cannot start with 'SDN_SC_'. · The static access can be set only for normal Layer 2 network domains. · Lease duration out of range. · The interface to be added in a networkrange and the interface to be added for port authentication cannot be the same. · Invalid network type for the Layer 2 network domain. · Invalid gateway device or fabric. · The VLAN ID is in use. · Invalid VLAN ID for the Layer 2 network domain. · The specified security group does not exist. · No available VLAN pool. · The security subgroup does not support binding to a Layer 2 network domain. · The security group and the Layer 2 network domain to be bound must be the same type. · Invalid network type for the security group. · You must select at least the isolation domains of all Layer 2 network domains bound to the security group. · The Unified Platform toker is null. · The fabric does not exist. · Invalid device interface configuration ID. · The interface configuration already exists. · Please specify a device ID. · Invalid device ID. · Invalid interface name. · The interface name already exists. · Invalid link type. · Invalid connection type. · Invalid spanning tree mode. · Invalid PVID. · A minimum of one permitted VLAN is invalid. · The link type does not match the permitted VLANs. · Invalid link type and VLAN configuration. · Invalid tagged VLANs. · A minimum of one untagged VLAN is invalid. · Invalid broadcast suppression threshold. · Invalid multicast suppression threshold. · Invalid unicast suppression threshold. · Please specify a device interface configuration ID. · Configuration recovery is in progress. · Invalid JSON format. · Unknown internal server error. · Internal Server Error. · The interface configuration does not exist. · Please check tagged and untagged VLANs for ID conflicts. · Get Unified Platform authority failed. · The number of items per page must be an integer in the range of 1 to 2147483647. · Invalid page index. · The specified device interfaces cannot overlap with border gateway members. · No wired service VLAN pool is available. · No wireless service VLAN pool is available. · No auth-free VLAN pool is available. · You can configure only one Layer 2 network domain for wireless management on a fabric · Please select a peer device type · Invalid peer device type · On a fabric, the VLAN IDs set on the core device for gateway IP assignment to Layer 2 domains cannot be the same as those set on any distribution devices. · The gateway device does not exist · The gateway device already exists. · You cannot configure Layer 2 multicast for the Layer 2 network domain, because selective VXLAN deployment is enabled for the isolation domain that contains the Layer 2 network domain. · You must also add the M-LAG member devices to the gateway device list for the Layer 2 network domain. · Invalid loopback detection interval time for the Layer 2 network domain. · Please specify the scenario for the Layer 2 network domain. · Invalid scenario for the Layer 2 network domain.

Update Layer 2 network domain

Keyword	UPDATE_L2NETWORKDOMAIN_OP
Message text	Updated Layer 2 network domain: “$1”
Variable fields	$1: Layer 2 network domain configuration parameters.
Example	Updated Layer 2 network domain: Name: [l2NetworkDomain1]
Explanation	A Layer 2 network domain was edited.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · The Layer 2 network domain name cannot be edited. · The Layer 2 network domain type cannot be edited. · The CIDR cannot be edited. · The VLAN ID cannot be edited. · The VXLAN ID cannot be edited. · The ARP proxy settings cannot be edited. · The VSI MAC address cannot be edited. · The ARP check settings cannot be edited. · The IGMP snooping settings cannot be edited. · To bind a DHCPv4 server in tight collaboration mode to an isolation domain, make sure the DHCPv4 server is up. · The specified DHCP server does not support IPv4. · The specified DHCP server does not support IPv6. · To bind a DHCPv6 server in tight collaboration mode to an isolation domain, make sure the DHCPv6 server is up. · Failed to edit the DHCPv4 server for the isolation domain. · To configure a DHCPv4 server, make sure the IPv4 address assignment mode is DHCP. · To bind a DHCPv4 server in tight collaboration mode to a security group, make sure the DHCPv4 server is up. · To bind a DHCPv6 server in tight collaboration mode to a security group, make sure the DHCPv6 server is up. · The segment ID cannot be modified. · The specified Layer 2 network domain does not exist. · The subnet gateway address cannot be the same as the IP address of the ingress or egress port of a service member. · IPv6 ND detection and ND snooping cannot be both enabled. · ARP packet validity check and ARP snooping cannot be both enabled. · Cannot edit the policy mode of the security group the Layer 2 network domain. · Cannot change the IPv6 address allocation mode because the Layer 2 network domain contains an IPv6 subnet. · You can enable the IGMP snooping dropping unknown multicast packets feature only when multicast network capabilities are enabled. · You can enable the IGMP snooping querier only when multicast network capabilities are enabled. · You can enable the IGMP snooping proxy only when multicast network capabilities are enabled. · The security group bound to the Layer 2 network domain has been used on an authentication server. You cannot change the IPv6 address allocation method from stateful DHCPv6 or stateless DHCPv6 to manual or SLAAC. · Lease duration out of range. · The interface to be added in a networkrange and the interface to be added for port authentication cannot be the same. · You cannot change the fabric ID for a Layer 2 network domain. · You cannot change the VLAN ID for a Layer 2 network domain. · You cannot change the gateway devices for a Layer 2 network domain. · The specified security group does not exist. · The security subgroup does not support binding to a Layer 2 network domain. · The security group and the Layer 2 network domain to be bound must be the same type. · Invalid network type for the security group. · You must select at least the isolation domains of all Layer 2 network domains bound to the security group. · The Unified Platform toker is null. · The fabric does not exist. · Invalid device interface configuration ID. · The interface configuration already exists. · Please specify a device ID. · Invalid device ID. · Invalid interface name. · The interface name already exists. · Invalid link type. · Invalid connection type. · Invalid spanning tree mode. · Invalid PVID. · A minimum of one permitted VLAN is invalid. · The link type does not match the permitted VLANs. · Invalid link type and VLAN configuration. · Invalid tagged VLANs. · A minimum of one untagged VLAN is invalid. · Invalid broadcast suppression threshold. · Invalid multicast suppression threshold. · Invalid unicast suppression threshold. · Please specify a device interface configuration ID. · Configuration recovery is in progress. · Invalid JSON format. · Unknown internal server error. · Internal Server Error. · The interface configuration does not exist. · Please check tagged and untagged VLANs for ID conflicts. · Get Unified Platform authority failed. · The number of items per page must be an integer in the range of 1 to 2147483647. · Invalid page index. · The specified device interfaces cannot overlap with border gateway members · Please select a peer device type · Invalid peer device type · The gateway device does not exist · The gateway device already exists. · You cannot configure Layer 2 multicast for the Layer 2 network domain, because selective VXLAN deployment is enabled for the isolation domain that contains the Layer 2 network domain. · You must also add the M-LAG member devices to the gateway device list for the Layer 2 network domain. · You cannot change the scenario for the Layer 2 networkdomain.

Delete Layer 2 network domain

Keyword	DELETE_L2NETWORKDOMAIN_OP
Message text	Deleted Layer 2 network domain: “$1”
Variable fields	$1: Layer 2 network domain name.
Example	Deleted Layer 2 network domain: l2NetworkDomain1
Explanation	A Layer 2 network domain was deleted.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · The Layer 2 network domain name cannot be empty. · The Layer 2 network domain has been bound to security group. · The Layer 2 network domain which is used by security group cannot be delete. · The Layer 2 networkdomain contains subnets and cannot be deleted. · Cannot delete the Layer 2 network domain because the Segment ID is being used by the ingress or egress port of a service member in a service chain. · Cannot delete the Layer 2 network domain because the Segment ID is being used by network range. · You cannot delete the Layer 2 network domain, because it has been bound to a Layer 2 multicast network.

Create Layer 3 campus interconnect

Keyword	CREATE_L3_CAMPUS_INTERCONNECT_OP
Message text	Created Layer 3 campus interconnect: “$1”
Variable fields	$1: Layer 3 campus interconnect information.
Example	Created Layer 3 campus interconnect: { "l3_campus_interconnects": [ { "id": "9ec0ead0-b288-42a1-b1b6-8606646a6f5c", "name": "l3_campus_interconnect", "description": "l3_campus_interconnect", "private_network_id":"1c6d3cf4-d622-4121-b193-bfac63a5e401", "private_network_name":"privateNetwork1", "local_security_groups": [ "1c6d3cf4-d622-4121-b193-bfac63a5e409", "1c6d3cf4-d622-4121-b193-bfac63a5e410" ], "import_rts": [ "1:6000" ], "export_rts": [ "1:1000" ], "data_mode": "vxlan", "l3_vni": 9 } ] }
Explanation	A Layer 3 campus interconnect was added.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · The Layer 3 campus interconnect ID already exists. · The Layer 3 campus interconnect name is required. · The Layer 3 campus interconnect name cannot exceed 255 characters. · The Layer 3 campus interconnect name already exists. · The Layer 3 campus interconnect description cannot exceed 255 characters. · The private network ID is required. · The specified private network does not exist. · The default private network cannot be used by a Layer 3 campus interconnect. · The specified private network is used by a multi-campus interconnection. · The local security group list is required. · The specified security group doesn't exist. · The private network to which a security group in the local security group list belongs must be bound to the Layer 3 campus interconnect. · The specified security group is used by a Layer 3 campus interconnect. · The Layer 3 campus interconnect import RT list is required. · The Layer 3 campus interconnect export RT list is required. · Invalid packet encapsulation type. · The L3VNI is out of range. · The L3VNI has been used. · The IDs of Layer 3 campus interconnects created in bulk cannot be duplicated. · The names of Layer 3 campus interconnects created in bulk cannot be duplicated. · The specified security group is used by another Layer 3 campus interconnect. · L3VNI 1, L3VNI 4092 and L3VNI 4094 are reserved and cannot be used. · The mapping L3VNI is required. · The campus has not established a session with the datacenter.

Update Layer 3 campus interconnect

Keyword	UPDATE_L3_CAMPUS_INTERCONNECT_OP
Message text	Updated Layer 3 campus interconnect: “$1”
Variable fields	$1: Layer 3 campus interconnect information.
Example	Updated Layer 3 campus interconnect { "l3_campus_interconnect": { "name": "l3_campus_interconnect1", "description": "modify l3_campus_interconnect1", "local_security_groups": [ "1c6d3cf4-d622-4121-b193-bfac63a5e409" ], "import_rts": [ "1:6006" ], "export_rts": [ "1:1001" ], "l3_vni": 9 } }
Explanation	A Layer 3 campus interconnect was edited.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown error. · The specified resource doesn't exist. · The Layer 3 campus interconnect ID cannot be modified. · The private network bound to a Layer 3 campus interconnect cannot be modified. · The Layer 3 campus interconnect data mode cannot be modified. · The Layer 3 campus interconnect name is required. · The Layer 3 campus interconnect name cannot exceed 255 characters. · The Layer 3 campus interconnect name already exists. · The Layer 3 campus interconnect description cannot exceed 255 characters. · The local security group list is required. · The specified security group doesn't exist. · The private network to which a security group in the local security group list belongs must be bound to the Layer 3 campus interconnect. · The specified security group is used by another Layer 3 campus interconnect. · The Layer 3 campus interconnect import RT list is required. · The Layer 3 campus interconnect export RT list is required. · The L3VNI is out of range. · The L3VNI has been used. · L3VNI 1, L3VNI 4092 and L3VNI 4094 are reserved and cannot be used. · The mapping L3VNI is required. · The campus has not established a session with the datacenter.

Delete Layer 3 campus interconnect

Keyword	DELETE_L3_CAMPUS_INTERCONNECT_OP
Message text	Deleted Layer 3 campus interconnect “$1”
Variable fields	$1: Layer 3 campus interconnect name.
Example	Deleted Layer 3 campus interconnect “l3CI1”
Explanation	A Layer 3 campus interconnect was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown error. · The specified resource doesn't exist.

Create subnet

Keyword	CREATE_SUBNET_OP
Message text	Created subnet “$1”
Variable fields	$1: Subnet name.
Example	Created subnet “sd”
Explanation	A subnet was created.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · The subnet name is required. · The subnet name already exists. · The IP version of the subnet is invalid. · The CIDR already exists. · Only one IPv4 primary subnet is allowed. · Only one IPv6 subnet can be configured and the IPv6 subnet must be used as the primary subnet. · The number of DNS servers on the DNS relay agent cannot exceed 8. · Cannot configure DNS servers for secondary subnets. · The IP address of the DNS server is invalid. · Duplicated DNS server IP addresses exist. · The CIDR is required. · The IP address of the subnet gateway is required. · The IP address of the subnet gateway is invalid. · The IP address of the subnet gateway does not belong to the CIDR. · The subnet gateway IP address and the subnet broadcast IP address cannot be the same. · The subnet address and the gateway address cannot be the same. · Invalid CIDR. · The subnet and resource group subnet of a private network cannot overlap. · The subnet name cannot exceed 255 characters. · The security group ID is required. · The security group ID does not exist. · The subnet ID already exists. · Duplicated subnet IDs exist for the subnets created in bulk. · Unknown error. · The service is disabled. · Duplicated subnet names exist for the subnets created in bulk. · Please make sure all subnets in the BYOD Layer 2 network domain are the same IP version. · When the IPv6 address allocation method is SLAAC or stateless DHCPv6, the IPv6 address prefix must be 64 bits in length. · The IP version of the subnet CIDR must be the same as the specified IP version. · The IP version of the gateway IP address must be the same as the specified IP version. · The IP version of the DNS server IP address must be the same as the specified IP version. · An external network security group does not support creating subnets. · Operation failed. IP address ranges specified for the L2 network domain contain IP addresses of a switching device. · The subnet address overlaps with IP address pools or with the management IP addresses of devices. · The CIDR cannot contain AC IPs of any other Layer 2 network domain. · The subnet gateway IP cannot be any AC IP of the Layer 2 network domain. · The subnets created in bulk for a BYOD Layer 2 network domain must use the same IP version. · The subnet gateway IP cannot be a wireless AC's IP. · Cannot delete the subnet, because an IP address in the subnet is the ingress or egress port IP address of a service chain member. · The selected private network uses group-based policy mode. You cannot add this subnet, because it overlaps with a subnet in the resource group for a private network that also uses group-based policy mode. · To add a secondary subnet to the Layer 2 network domain, first make sure the Layer 2 network domain already has primary subnets. · The subnet name cannot start with 'SDN_SC_'.

Update subnet

Keyword	UPDATE_SUBNET_OP
Message text	Updated subnet “$1”
Variable fields	$1: Subnet name.
Example	Updated subnet “sd”
Explanation	A subnet was updated.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · The specified resource doesn't exist. · The subnet ID cannot be modified. · The subnet name cannot be modified. · The security group ID cannot be modified. · The IP version of the subnet cannot be modified. · The CIDR of the subnet cannot be modified. · The IP address of the subnet gateway cannot be modified. · The secondary field cannot be modified. · Unknown error. · The service is disabled.

Delete subnet

Keyword	DELETE_SUBNET_OP
Message text	Deleted subnet “$1”.
Variable fields	$1: Subnet name.
Example	Deleted subnet “sd”.
Explanation	A subnet 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. · The service is disabled. · Failed to synchronously create the address pool. An address pool named xxx already exists. · Failed to synchronously create the address pool. An address pool with the same network segment already exists. · Failed to delete the IPv4 subnet because the security group bound to the IPv4 subnet's Layer 2 network domain is being used by an authentication server. · Failed to delete the IPv6 subnet because the security group bound to the IPv6 subnet's Layer 2 network domain is being used by an authentication server. · Failed to delete the IPv4 subnet because the security group to which the IPv4 subnet belongs is being used by a security server. · Failed to delete the IPv6 subnet because the security group to which the IPv6 subnet belongs is being used by a security server. · Failed to delete primary subnets from the Layer 2 network domain, because the Layer 2 network domain has secondary subnets. · Failed to delete the subnet, because group policies are configured for the IT resource group and the security group associated with the Layer 2 network domain where the subnet is located.Please delete the group policies first

Bind security group to access scenario

Keyword	ACCESS_STRATEGY_ADD_SECURITY_GROUP_OP
Message text	Bound security group $3 to access scenario $2 for user group $1.
Variable fields	$1: User group ID. $2: Access scenario ID. $3: Security group ID.
Example	Bound security group $3 to access scenario $2 for user group $1.
Explanation	A security group was bound to an access scenario in a user group.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown error. · The operation requires the administrator privilege. · No security group is specified. · The security group does not exist. · The user group does not exist. · No user group is specified. · The access scenario does not exist. · No access scenario is specified. · The service is disabled.

Unbind security group from access scenario

Keyword	ACCESS_STRATEGY_DEL_SECURITY_GROUP_OP
Message text	Unbound the security group from access scenario $2 for user group $1.
Variable fields	$1: User group ID. $2: Access scenario ID.
Example	Unbound the security group from access scenario $2 for user group $1.
Explanation	A security group was unbound from an access scenario in a user group.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · Unknown error. · The user group does not exist. · No user group is specified. · The access scenario does not exist. · No access scenario is specified. · The service is disabled.

Modify access scenario priority

Keyword	SERVICE_STRATEGY_CHANGE_PRIORITY_OP
Message text	Modified access scenario priorities for user groups “$1”
Variable fields	$1: Set of user groups.
Example	Modified access scenario priorities for user groups “userAccessGroups”.
Explanation	The access scenario priorities were modified in user groups.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · Unknown error. · Nonexistent user groups have been specified. · The user group is required . · Nonexistent access scenarios have been specified. · The access scenario is required. · A priority is required for an access scenario. · Cannot modify the priority of the default access scenario. · The service is disabled.

Create authentication server

Keyword	ADD_AUTH_OP
Message text	Created authentication server “$1”
Variable fields	$1: Authentication server ID.
Example	Created authentication server “ffffffff-0000-0000-0000-000000000012”
Explanation	An authentication server was created.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · The request is invalid. · The authentication server ID already exists. · The authentication server ID is required. · The authentication server IP is invalid. · The port number of the authentication server is required. · The port number of the authentication server is invalid. · The authentication server with the IP address and port number already exists. · The authentication server type is required. · The authentication server type already exists. · The authentication server password is required. · The authentication server password cannot exceed 255 characters. · The authentication server username is required. · The authentication server username cannot exceed 255 characters. · The service is disabled.

Update authentication server

Keyword	UPDATE_AUTH_OP
Message text	Updated authentication server “$1”
Variable fields	$1: Authentication server ID.
Example	Updated authentication server “ffffffff-0000-0000-0000-000000000012”
Explanation	An authentication server was modified.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown error. · The authentication server ID does not exist. · The authentication server ID cannot be modified. · The authentication server type cannot be modified. · The service is disabled.

Delete authentication server

Keyword	DELETE_AUTH_OP
Message text	Deleted authentication server “$1”
Variable fields	$1: Authentication server ID.
Example	Deleted authentication server “ffffffff-0000-0000-0000-000000000012”
Explanation	An authentication server was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown error. · The authentication server ID does not exist. · The service is disabled.

Smooth EIA

Keyword	SMOOTH_EIA_OP
Message text	Smoothed EIA authentication server “$1”.
Variable fields	$1: Authentication server ID.
Example	Smoothed EIA authentication server “ffffffff-0000-0000-0000-000000000012”.
Explanation	The EIA authentication server was synchronized.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown error. · Failed to synchronize security group information to the authentication server. · Failed to synchronize user role information to the authentication server. · Failed to synchronize link information to the authentication server. · Failed to synchronize IP binding information from the authentication server to the DHCP server.

Create resource group

Keyword	CREATE_RESOURCEGROUP_OP
Message text	Created resource groups “$1”
Variable fields	$1: Resource group name.
Example	Created resource groups ”resourceGroup1”
Explanation	A resource group was created.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · The service is disabled. · The resource group ID already exists. · The resource group name is required. · The resource group name cannot exceed 255 characters. · The resource group name already exists. · The private network ID is required. · The specified private network does not exist. · The description cannot exceed 255 characters. · The address entries are required. · The address type is required. · Invalid address type. · The IP address range of the resource group is required. · Invalid IP address. · Up to 253 IP address ranges can be configured. · The end IP address must be higher than the start IP address in an IP address range. · The IP address ranges of resource groups cannot overlap. · The subnet and resource group subnet of a private network cannot overlap. · Duplicated IDs exist for the resource groups created in bulk. · Duplicated names exist for the resource groups created in bulk. · Unknown error. · The IP address of the resource group conflicts in the same private network. · To interconnect two private networks, make sure the subnets in their resource groups do not overlap. · Operation failed. IP address ranges specified for the resource group contain IP addresses of a switching device. · The subnet address overlaps with IP address pools or with the management IP addresses of devices. · The specified private network does not exist. · The resource groups created in a private network must be configured with the same policy mode as the private network. · The resource group does not support specifying a Tag ID. · The selected private network uses group-based policy mode. You cannot add this subnet, because it overlaps with a subnet in the resource group for a private network that also uses group-based policy mode. · The selected private network uses group-based policy mode. You cannot add this subnet, because it overlaps with a subnet in the Layer 2 network domain for a private network that also uses group-based policy mode. · The IP address ranges in the resource groups of a shared VRF cannot overlap with the IP address ranges in the resource groups of a non-shared VRF. · You cannot change the network type of an IT resource group. · A VLAN network does not support configuring private networks for a resource group. · Invalid network type for the IT resource group. · In group-based policy mode,the subnets in the same IT resource group or in different IT resource groupscannot overlap. · The L3 CI EPG is required. · The L3 CI EPG does not exist. · Duplicate L3 CI EPG IDs exist for the resource groups created in bulk.

Update resource group

Keyword	UPDATE_RESOURCEGROUP_OP
Message text	Updated resource group “$1”
Variable fields	$1: Resource group name.
Example	Updated resource group “resourceGrpoup1”
Explanation	A resource group was updated.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · The service is disabled. · Unknown error. · The resource group name cannot be modified. · The specified resource doesn't exist. · The resource group ID cannot be modified. · The private network ID cannot be modified. · The description cannot exceed 255 characters. · The address entries are required. · The address type is required. · Invalid address type. · The IP address ranges of resource groups cannot overlap. · The address entries cannot be modified for a resource group that is being used by an intergroup policy. · To interconnect two private networks, make sure the subnets in their resource groups do not overlap. · Operation failed. IP address ranges specified for the resource group contain IP addresses of a switching device. · Cannot edit the tag of the resource group. · Cannot edit the policy mode of the resource group. · The selected private network uses group-based policy mode. You cannot add this subnet, because it overlaps with a subnet in the resource group for a private network that also uses group-based policy mode. · The selected private network uses group-based policy mode. You cannot add this subnet, because it overlaps with a subnet in the Layer 2 network domain for a private network that also uses group-based policy mode. · The IT resource group must contain IPv4 subnets, because IPv4 has been enabled on a minimum of one gateway member bound to the IT resource group. · The IT resource group must contain IPv6 subnets, because IPv6 has been enabled on a minimum of one gateway member bound to the IT resource group. · You cannot edit the IT resource group, because firewall has been enabled on a minimum of one gateway member bound to the IT resource group. · The IP address ranges in the resource groups of a shared VRF cannot overlap with the IP address ranges in the resource groups of a non-shared VRF. · In group-based policy mode,the subnets in the same IT resource group or in different IT resource groupscannot overlap. · The L3 CI EPG is required. · The L3 CI EPG does not exist. · Duplicate L3 CI EPG IDs exist for the resource groups created in bulk.

Delete resource group

Keyword	DELETE_RESOURCEGROUP_OP
Message text	Deleted resource group “$1”
Variable fields	$1: Resource group name.
Example	Deleted resource group “resourceGroup1”
Explanation	A resource group was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown error. · The service is disabled. · The specified resource doesn't exist. · The resource group is being used by an intergroup policy and cannot be deleted · You cannot delete the IT resource group, because gateway members have been bound to the IT resource group. · You cannot edit the EPG ID of a resource group.

Create network range

Keyword	CREATE_LAYER2_NETWORKDOMAIN_interface_OP
Message text	Created Layer 2 network domain interface “$1”
Variable fields	$1：Network range configuration parameters.
Example	Created Layer 2 network domain interface: "access:GigabitEthernet1/0/48"
Explanation	A network range was created.
Possible failure causes	· A device interface already exists with the same UUID. · The device interface has been used by another access scenario of a Layer 2 network domain. · The device interface has been added. · Only the wireless scene supports selecting AP direct-access interface group for leafs and AP non-direct access interface group for leafs

Delete network range

Keyword	DELETE_LAYER2_NETWORKDOMAIN_interface_OP
Message text	Deleted Layer 2 network domain interface “$1”
Variable fields	$1：Network range configuration parameters.
Example	Deleted Layer 2 network domain interface: "access:GigabitEthernet1/0/48"
Explanation	A network range was deleted.
Possible failure causes	· Please first delete the port authentication configuration of the device interface.

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 API authentication-free IP

Keyword	ADD_API_AUTH_FREEIP_OP
Message text	Added an API authentication-free IP: $1
Variable fields	$1: IP address of the API authentication-free user.
Example	Added an API authentication-free IP: 192.168.56.13
Explanation	An API authentication-free user was added.
Possible failure causes	· Invalid IP address. · The IP address already exists. · The controller is not the active leader. · Unknown error. · Invalid role. · Invalid type · Invalid description.

Delete an API authentication-free IP

Keyword	DELETE_API_AUTH_FREEIP_OP
Message text	Deleted an API authentication-free IP: $1
Variable fields	$1: IP address of the API authentication-free user.
Example	Deleted an API authentication-free IP: 192.168.56.13
Explanation	An API authentication-free user was deleted.
Possible failure causes	· The controller is not the active leader. · Unknown error. · Invalid IP address. · Invalid type · The IP address does not exist.

Add an IP address to white list

Keyword	ADD_IP_TO_WHITELIST_OP
Message text	Added IP address $1 to the white list.
Variable fields	$1: IP address added to the white list.
Example	Added IP address 192.168.56.13 to the white list.
Explanation	A user was added to the white list.
Possible failure causes	· Invalid IP address. · The IP address already exists. · The controller is not the active leader. · Unknown error. · Invalid type. · Invalid description.

Delete an IP address from white list

Keyword	DELETE_IP_FROM_WHITELIST_OP
Message text	Deleted IP address $1 from the white list.
Variable fields	$1: IP address removed from the white list.
Example	Deleted IP address 192.168.56.13 from the white list.
Explanation	A user was removed from the white list.
Possible failure causes	· Invalid IP address. · The controller is not the active leader. · The IP address does not exist. · Unknown error. · Invalid type.

CON_LICENSE

This section contains CON_LICENSE messages.

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 connected 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

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.

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_NetworkMonitor

This section contains CON_NetworkMonitor messages.

Change thresholds for a CPU

Keyword	CHANGE_THRESHOLDS_OP
Message text	Changed network monitor thresholds for CPU $1 in slot $2 of chassis $3 on device $4: $5
Variable fields	$1: CPU ID. $2: Slot number. $3: Chassis number. $4: IP address of the device. $5: Resource usage alarm thresholds.
Example	Changed network monitor thresholds for CPU 1 in slot 1 of chassis 1 on device 192.168.150.21: { cpuRecoveryThreshold: 10 cpuMinorThreshold: 20 cpuWarningThreshold: 40 memorySecureThreshold: 10 memoryEarlyWarningThreshold: 20 memoryNormalThreshold: 30 memoryMinorThreshold: 30 memorySevereThreshold: 40 memoryCriticalThreshold: 50 aclMinorThreshold: 50 aclSevereThreshold: 60 acMinorThreshold: 20 acSevereThreshold: 40 vsiMinorThreshold: 20 vsiSevereThreshold: 40 vlanMinorThreshold: 20 vlanSevereThreshold: 40 }
Explanation	The resource usage alarm thresholds were modified for a specific CPU.
Possible failure causes	· The controller is not the active leader. · The device is not a physical device. · The device is offline. · The device does not exist. · The device does not support configuring CPU usage threshold. · The device does not support configuring memory usage threshold. · The device does not support configuring ACL resource usage threshold. · The device does not support configuring AC resource usage threshold. · The device does not support configuring VSI interface resource usage threshold. · The device does not support configuring VLAN interface resource usage threshold.

Change thresholds for all CPUs

Keyword	CHANGE_THRESHOLDS_ALL_OP
Message text	Changed network monitor thresholds for all CPUs on device $1: $2
Variable fields	$1: IP address of the device. $2: Resource usage thresholds.
Example	Changed network monitor thresholds for all CPUs on device 192.168.150.21: { cpuRecoveryThreshold: 10 cpuMinorThreshold: 20 cpuWarningThreshold: 40 memorySecureThreshold: 10 memoryEarlyWarningThreshold: 20 memoryNormalThreshold: 30 memoryMinorThreshold: 30 memorySevereThreshold: 40 memoryCriticalThreshold: 50 aclMinorThreshold: 50 aclSevereThreshold: 60 acMinorThreshold: 20 acSevereThreshold: 40 vsiMinorThreshold: 20 vsiSevereThreshold: 40 vlanMinorThreshold: 20 vlanSevereThreshold: 40 }
Explanation	The resource usage thresholds were modified for all CPUs.
Possible failure causes	· The controller is not the active leader. · The device is not a physical device. · The device is offline. · The device does not exist. · The device does not support configuring CPU usage threshold. · The device does not support configuring memory usage threshold. · The device does not support configuring ACL resource usage threshold. · The device does not support configuring AC resource usage threshold. · The device does not support configuring VSI interface resource usage threshold. · The device does not support configuring VLAN interface resource usage threshold.

CON_OAM

This section contains CON_OAM messages.

Create radar detection task

Keyword	CREATE_RADAR_DETECTION_OP
Message text	Created radar detection task: $1
Variable fields	$1: Parameters for the radar detection task.
Example	Created radar detection task: Username: sdn Task type: multiple Task info: Path type: single Network type: vxlan Segment ID: 2 Protocol: TCP Source IP: 70.68.68.68 Source port: 10000 Start device IP: 192.168.70.68 Start device ingress port: 0x1 Destination IP: 168.168.1.2 Destination port: 50000 End device IP: null DSCP: 62 Interval: 0 Packet count: 1 Timeout: 10 Period: 1440 Frequency: 600
Explanation	A radar detection task was created.
Possible failure causes	· The start device IP address doesn't exist. · Task already exists. Please try again later. · The controller hasn't obtained start device port information. · The start device ingress port doesn't exist. · The destination IP address doesn't exist. · The gateway device that source device belongs to doesn't exist. · The controller is not the active leader. · Can't find the vPort with the source IP address. · The number of periodic detection tasks has reached the maximum. · Radar detection is disabled. · The number of periodic radar detection tasks has reached the upper limit.

Delete radar detection task

Keyword	Delete_RADAR_DETECTION_OP
Message text	Deleted radar detection task: $1
Variable fields	$1: UUID of the radar detection task.
Example	Deleted radar detection task: 218b5f2f-e435-4365-a1ab-0eaa03b7fa19
Explanation	A radar detection task was deleted.
Possible failure causes	· The controller is not the active leader. · Radar detection is disabled. · The periodic scanning task ID doesn’t match the username of the task creator.

Clear periodic radar detection tasks

Keyword	CLEAR_RADAR_DETECTION_OP
Message text	Clear all periodic radar detection tasks for user $1.
Variable fields	$1: Username.
Example	Clear all periodic radar detection tasks for user sdn.
Explanation	All periodic radar detection tasks created by the user were cleared.
Possible failure causes	· The controller is not the active leader. · Radar detection is disabled.

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_SNMP

This section contains CON_SNMP messages.

Create traditional NE

Keyword	CREATE_TRADITIONAL_NE_OP
Message text	Created traditional NE: $1
Variable fields	$1: Traditional NE configuration information.
Example	Created traditional NE: IP: 192.168.9.198 MAC: 74:25:8a:c4:e2:de Read community: public Write community: private Controller IP: 192.168.89.155 Access attribute: access Status: Inactive
Explanation	The user added a traditional NE.
Possible failure causes	· The controller is not the active leader. · Invalid network element IP address. · The traditional network element at X.X.X.X already exists. · Invalid controller IP address. · The controller IP address doesn't exist in the team. · The IP address for a controller in standalone mode must be 127.0.0.1. · Invalid access attribute. · The traditional network element has been added to the controller by using X.X.X.X.

Update traditional NE

Keyword	UPDATE_TRADITIONAL_NE_OP
Message text	Updated traditional NE: $1
Variable fields	$1: Traditional NE configuration information.
Example	Updated traditional NE: IP: 192.168.9.198 MAC: 74:25:8a:c4:e2:de Read community: public Write community: private Controller IP: 192.168.89.155 Access attribute: access Status: Inactive
Explanation	The user modified the traditional NE.
Possible failure causes	· The controller is not the active leader. · Invalid network element IP address. · The network element IP address doesn't exist. · Invalid controller IP address. · The controller IP address doesn't exist in the team. · The IP address for a controller in standalone mode must be 127.0.0.1. · Invalid access attribute. · Unknown error.

Delete traditional NE

Keyword	DELETE_TRADITIONAL_NE_OP
Message text	Deleted traditional NE: $1
Variable fields	$1: IP address of the traditional NE.
Example	Deleted traditional NE: 192.168.9.198
Explanation	The user deleted the traditional NE.
Possible failure causes	· The controller is not the active leader. · Invalid network element IP address. · The network element IP address doesn't exist.

Start scanning traditional NE

Keyword	START_SCAN_TRADITIONAL_NE_OP
Message text	Started scanning traditional NEs: $1
Variable fields	$1: Settings for auto traditional NE scanning.
Example	Started scanning traditional NEs: Start IP: 192.168.125.0 End IP: 192.168.125.255 SNMP read community: public SNMP write community: private
Explanation	The user started auto traditional NE scanning.
Possible failure causes	N/A

Stop scanning traditional NE

Keyword	STOP_SCAN_TRADITIONAL_NE_OP
Message text	Stopped scanning traditional NEs
Variable fields	N/A
Example	Stopped scanning traditional NEs
Explanation	The user stopped auto traditional NE scanning.
Possible failure causes	N/A

CON_SYSTEM

This section contains CON_SYSTEM messages.

Back up configuration

Keyword	BACKUP_OP
Message text	Backed up the configuration.
Variable fields	$1: Session name.
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. · Can’t upload the backup file because some controllers are down: $1, $2, $3.

Start recovery

Keyword	RESTORE_OP
Message text	Restored the configuration.
Variable fields	N/A
Example	Restored the configuration.
Explanation	A recovery was started.
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. · Can’t perform configuration recovery because some controllers are down.

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 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 settings for configuration backup 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 prepares for upgrade.
Example	Prepared for upgrade
Explanation	Upgrade preparation was performed.
Possible failure causes	Invalid request.

Modify alert log remote transmission mode

Keyword	MODIFY_ALERTLOG_TRANSMISSION_OP
Message text	The alert log remote transmission mode was set to sending logs to the syslog server.
Variable fields	N/A
Example	The alert log remote transmission mode was set to sending logs to the syslog server.
Explanation	The user changed the system log settings by enabling the syslog server feature. System logs will be sent to the specified syslog server.
Possible failure causes	N/A

Modify audit log transmission mode

Keyword	MODIFY_AUDITLOG_TRANSMISSION_OP
Message text	The audit log remote transmission mode was set to sending logs to the syslog server.
Variable fields	N/A
Example	The audit log remote transmission mode was set to sending logs to the syslog server.
Explanation	The user changed the operation log settings by enabling the syslog server feature. Operation logs will be sent to the specified syslog server.
Possible failure causes	N/A

Enter upgrade mode

Keyword	ENTER_UPGRADE_MODE_OP
Message text	Enter upgrade mode.
Variable fields	N/A
Example	Enter upgrade mode.
Explanation	The operation for entering the upgrade mode was performed.
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 operation for quitting the upgrade mode was performed.
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_TOPOLOGY

This section contains CON_TOPOLOGY messages.

Update device

Keyword	UPDATE_DEVICE_INFO_OP
Message text	Updated device: $1
Variable fields	$1: Device information.
Example	Updated device: IP address: 192.168.9.198 Datapath ID: 00:00:74:25:8a:c4:e2:de Asset number: 201605181600 Device description: H3C Comware Platform Software, Software Version 7.1.070, ESS 2505P01 Location: A13-A13 Function: core Remarks: description Device name: 201-98 Status: Inactive
Explanation	The user modified the device information on the device statistics page.
Possible failure causes	The device doesn't exist.

Update device layer

Keyword	UPDATE_DEVICE_LAYER_OP
Message text	Updated the layer for device (IP address $1 and datapath ID $2): $3.
Variable fields	$1: IP address of the device. $2: Datapath ID of the device. $3: Layer of the device. Options are access, convergence, and core.
Example	Updated the layer for device (IP address 192.168.9.198 and datapath ID 00:00:74:25:8a:c4:e2:de): core.
Explanation	The user modified the layer for the device specified on the physical topology page.
Possible failure causes	The device doesn't exist.

Delete inactive link

Keyword	DELETE_INACTIVE_LINK_OP
Message text	Deleted an inactive link. Link information: $1
Variable fields	$1: Inactive link information.
Example	Deleted an inactive link. Link information: From: Port GigabitEthernet1/0/3 on device (IP address 192.168.150.44 and datapath ID 00:00:68 b:10 a:04:00). To: Port GigabitEthernet1/0/5 on device (IP address 192.168.150.42 and datapath ID 00:00:94:e2:4e:53:02:00).
Explanation	The user deleted the inactive link for the device.
Possible failure causes	N/A

Update port thresholds

Keyword	UPDATE_PORT_THRESHOLD_OP
Message text	Updated port thresholds: $1
Variable fields	$1: Port thresholds.
Example	Updated port monitor thresholds: Inbound bandwidth usage: 12% Outbound bandwidth usage: 32% Inbound error packet rate: 43% Outbound error packet rate: 43% Inbound packet loss rate: 54% Outbound packet loss rate: 65%
Explanation	The user modified the port thresholds.
Possible failure causes	N/A

Clear events on a device

Keyword	CLEAR_DEVICE_EVENTS_OP
Message text	Clear events on device: $1.
Variable fields	$1: IP address of the device.
Example	Clear events on device: 192.168.5.3.
Explanation	The user cleared the events on a device.
Possible failure causes	The device doesn't exist.

Clear events on all devices

Keyword	CLEAR_ALL_DEVICES_EVENTS_OP
Message text	Clear events on all devices.
Variable fields	N/A
Example	Clear events on all devices.
Explanation	The user cleared the events on all devices.
Possible failure causes	N/A

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. · Invalid role. · The username already exists. · The password length is out of range or the password contains only letters, digits, or special characters. · The controller is not the active leader. · Incorrect format. · Failed to add the user.

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 itself. · The controller is not the active leader. · Can't delete an online user. · Token aged.

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 user's password due to permission limit. · The controller is not the active leader. · Token aged. · The user doesn’t exist. · Failed to update the user’s password.

Update user config

Keyword	UPDATE_USER_OP
Message text	Updated user configuration: $1
Variable fields	$1: User configuration information.
Example	Updated user configuration: Username: sdn Password: ****** Role: sdn-admin Service logs to display: ARP, CON, NEM, VSM Lock state: unlock
Explanation	The user configuration was changed.
Possible failure causes	· The user does not exist. · Invalid parameter for locking the user. · Invalid user role. · Invalid old password. · Invalid username. · Incorrect format. · The controller is not the active leader. · Can't modify another user's configuration due to permission limit. · Can't lock the current user. · Can't modify the role of the current user. · Can't change the types of service logs to display due to permission limit. · The password length is out of range or the password contains only letters, digits, or special characters. · Token aged. · Failed to update the user. · Can't modify the configuration of other online users.

Add a role

Keyword	ADD_ROLE_OP
Message text	Added a role: $1.
Variable fields	$1: Role name.
Example	Added a role: role1.
Explanation	A role was added.
Possible failure causes	· Invalid role name. · Invalid role rule. · Invalid description. · The role already exists. · You have no privilege to perform the operation. · The controller is not the active leader. · Incorrect format. · Failed to add the role.

Update a role

Keyword	UPDATE_ROLE_OP
Message text	Updated role configuration: $1
Variable fields	$1: Role configuration.
Example	Updated role configuration: Rolename: test2, Description:, RoleRules: { "rolerules": { "/lb/v2.0": { "details": [ { "access": "POST", "controlled": "/loadbalancers" } ], "module": "LBaaS v2.0", "type": "REST" }, "c-NetworkService": { "details": [ { "access": "R", "controlled": "n-LoadBalance" } ], "type": "UI" } } }
Explanation	A role was modified.
Possible failure causes	· You have no privilege to perform the operation. · Incorrect format. · The controller is not the active leader. · Invalid role name. · Invalid role rule · Invalid description. · Can't modify default roles. · The role doesn’t exist. · Failed to update the role.

Delete a role

Keyword	DELETE_ROLE_OP
Message text	Deleted a role: $1.
Variable fields	$1: Role name.
Example	Deleted a role: 11.
Explanation	A role was deleted.
Possible failure causes	· Invalid role name. · The controller is not the active leader. · Can't delete system default roles. · Can’t delete the role because it is already assigned to users.

DHCP

This section contains DHCP messages.

Create DHCP server

Keyword	CREATE_DHCP_SERVER_OP
Message text	Created DHCP server $1/$2.
Variable fields	$1: Name of the DHCP server. $2: IP address of the DHCP server.
Example	Created DHCP server Vsr-26.72/98.0.26.72.
Explanation	A DHCP server was created.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · Unknown error. · The IP address of the DHCP server is required. · Invalid IP address. · Invalid role. · The DHCP server name is required. · The DHCP server name cannot exceed 255 characters. · The NETCONF username of the DHCP server is required. · The NETCONF username of the DHCP server cannot exceed 55 characters. · The NETCONF password of the DHCP server is required. · The NETCONF password of the DHCP server cannot exceed 63 characters. · The DHCP server with the specified UUID already exists. · The DHCP server name is already used. · The DHCP server IP is already used. · Invalid DHCP server type. · The status field of the DHCP server is read-only. · The DHCP server does not support the master-backup mode. · The second IP is required in master-backup mode. · The DHCP servers in master-backup mode cannot use the same IP address. · The second IP address is invalid. · The DHCP server name cannot end with _peer. · Invalid unicast addresses. · The DHCP server name supports only Chinese characters, letters, digits, hyphens (-), and underscores (_). · Only one IP address is allowed in standalone mode. · Invalid DHCP server IP address.

Update DHCP server

Keyword	UPDATE_DHCP_SERVER_OP
Message text	Updated DHCP server $1/$2.
Variable fields	$1: Name of the DHCP server. $2: IP address of the DHCP server.
Example	Updated DHCP server Vsr-26.72/98.0.26.72.
Explanation	A DHCP server was modified.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · The request is invalid. · Unknown error. · The specified resource doesn't exist. · The IP field of the DHCP server is read-only. · The name field of the DHCP server is read-only. · The status field of the DHCP server is read-only. · The type field of the DHCP server is read-only. · The NETCONF username of the DHCP server is required. · The NETCONF username of the DHCP server cannot exceed 55 characters. · The NETCONF password of the DHCP server is required. · The NETCONF password of the DHCP server cannot exceed 63 characters. · The DHCP server name supports only Chinese characters, letters, digits, hyphens (-), and underscores (_).

Delete DHCP server

Keyword	DELETE_DHCP_SERVER_OP
Message text	Deleted DHCP server $1/$2.
Variable fields	$1: Name of the DHCP server. $2: IP address of the DHCP server.
Example	Deleted DHCP server Vsr-26.72/98.0.26.72.
Explanation	A DHCP server was deleted.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · Unknown error. · The specified resource doesn't exist. · Can't delete the DHCP server. The DHCP server has address pools.

Synchronize data from DHCP server

Keyword	SYNCHRONIZE_DATA_FROM_DHCP_SERVER_OP
Message text	Synchronized data from DHCP server $1.
Variable fields	$1: UUID of the DHCP server.
Example	Synchronized data from DHCP server 218b5f2f-e435-4365-a1ab-0eaa03b7fa19.
Explanation	Data from a DHCP server was synchronized.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · Unknown error. · The DHCP server ID doesn't exist. · The server is synchronizing DHCP subnet information.

Stop Synchronizing data from DHCP server

Keyword	STOP_SYNCHRONIZING_DATA_FROM_DHCP_SERVER_OP
Message text	Stopped Synchronizing data from DHCP server $1.
Variable fields	$1: UUID of the DHCP server.
Example	Stopped synchronizing data from DHCP server 218b5f2f-e435-4365-a1ab-0eaa03b7fa19.
Explanation	Data synchronization from a DHCP server was stopped.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · Unknown error. · The DHCP server doesn't exist. · The DHCP server is not in Synchronizing state. · The DHCP server in the loose networking mode does not support this operation.

Update IP Conflict Detection from DHCP server

Keyword	UPDATE _IP_CONFLICT_DETECTION_FROM_DHCP_SERVER_OP
Message text	Updated IP conflict detection from DHCP server $1.
Variable fields	$1：Name of the DHCP server.
Example	Updated IP conflict detection from DHCP server Vsr-26.72.
Explanation	IP conflict detection from DHCP server was updated
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · Unknown error. · The DHCP server doesn't exist. · The DHCP server is switching to HA mode. Please do not perform any other operations. · DHCP primary server unknown. · The connection between the DHCP server and the controller is abnormal. · The request is invalid.

DHCP address pool

This section contains DHCP address pool messages.

Create DHCP address pool

Keyword	CREATE_DHCP_ADDRESS_POOL_OP
Message text	Created DHCP address pool: $1
Variable fields	$1: DHCP address pool information.
Example	Created DHCP address pool: { "dhcp_server_id": "79e1cf00-602a-4650-9706-a7ab904e3431", "name": "ddi_pool_test", "description": "ddi_pool_test", "subnet": "98.0.2.0/24", "options":[{"key":"3","value":"98.0.2.254"}], "policy":[{"condition":"relay","value":"3030303034303934","wildcard":"append"},{"condition":"client","value":"34","wildcard":"prefix"}] }
Explanation	A DHCP address pool was created.
Possible failure causes	· Configuration recovery is in progress · The controller is not the active leader. · The DHCP address pool name is required. · The DHCP pool name cannot exceed 255 characters. · The DHCP address pool description cannot exceed 255 characters. · The DHCP server ID is required. · The DHCP address pool option is required. · The subnet is required in the DHCP address pool. · The subnet in the DHCP address pool is invalid. · The DHCP address pool policy is invalid. · The DHCP server doesn't exist. · The DHCP address pool name has been used. · Overlapping subnet in the DHCP address pool. · Unknown error. · The DHCP server does not support custom address pools. · Invalid DHCP address pool option. · The DHCP pool name is invalid.

Update DHCP address pool

Keyword	UPDATE_DHCP_ADDRESS_POOL_OP
Message text	Updated DHCP address pool: $1
Variable fields	$1: DHCP address pool information.
Example	Updated DHCP address pool: { "dhcp_server_id": "79e1cf00-602a-4650-9706-a7ab904e3431", "deploy_type": "add", "dhcp_pool_id": "79e1cf00-602a-4650-9706-a7ab904e3430", "dhcp_pool_name": "" }
Explanation	A DHCP address pool was modified.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · The request is invalid. · Unknown error. · The DHCP server doesn't exist. · The DHCP server in the loose networking mode does not support this operation. · The deployed type is required. · The deployed type is invalid. · The ID of the DHCP address pool is required. · The DHCP address pool name is required. · The DHCP address pool doesn't exist.

Delete DHCP address pool

Keyword	DELETE_DHCP_ADDRESS_POOL_OP
Message text	Deleted DHCP address pool $1 on DHCP server $2
Variable fields	$1: ID of the DHCP address pool. $2: ID of the DHCP server.
Example	Deleted DHCP address pool 14ed05b2-2a52-4f04-aa4e-6f215e622a39 on DHCP server 25ed05b2-6a52-9a04-aa4e-9a215e622a46.
Explanation	A DHCP address pool was deleted.
Possible failure causes	· The specified resource doesn't exist. · Only custom DHCP address pools can be deleted. · Configuration recovery is in progress. · The controller is not the active leader. · The DHCP server doesn't exist. · The DHCP address pool doesn't exist. · Unknown error.

Synchronize data from DHCP address pool

Keyword	SYNCHRONIZE_DATA_FROM_DHCP_ADDRESS_POOL_OP
Message text	Synchronized data from DHCP address pool: $1
Variable fields	$1: DHCP address pool information.
Example	Synchronized data from DHCP address pool: { "dhcp_server_id": "1c6d3cf4-d622-4121-b193-bfac63a5e401", "subnets": "1.1.1.0/24, 2.2.2.0/24" }
Explanation	Data from a DHCP address pool was synchronized.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · Unknown error. · The DHCP server doesn't exist. · The DHCP address pool doesn't exist. · The DHCP server is syncing.

Stop Synchronizing data from DHCP address pool

Keyword	STOP_SYNCHRONIZING_DATA_FROM_DHCP_ADDRESS_POOL_OP
Message text	Stopped synchronizing data from DHCP address pool $1.
Variable fields	$1: DHCP address pool information.
Example	Stopped synchronizing data from DHCP address pool: { "dhcp_server_id":"1c6d3cf4-d622-4121-b193-bfac63a5e401", "subnets": "1.1.1.0/24, 2.2.2.0/24" }
Explanation	Data synchronization from a DHCP address pool was stopped.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · Unknown error. · The DHCP server doesn't exist. · The DHCP address pool doesn't exist. · The DHCP AddressPool is not syncing.

DHCP IP bind

Update DHCP IP bind

Keyword	UPDATE_DHCP_IP_BIND_OP
Message text	Updated DHCP IP bind: $1
Variable fields	$1: DHCP IP binding information.
Example	Updated DHCP IP bind: { "dhcp_server_ip": "192.168.135.102", "dhcp_pool_id": "dcc08e71-1851-4fa8-ba1f-68133c2eeb90", "bind_id": "c152bdfe-3ffe-41ff-b233-6efdf372c1d7", "bind_ip": "", "deploy_type": "add" }
Explanation	A DHCP binding was modified.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · The request is invalid. · Unknown error. · The DHCP server doesn't exist. · The DHCP server in the loose networking mode does not support this operation. · The deployed type is required. · The deployed type is invalid. · The ID of the DHCP address pool is required. · The DHCP address pool doesn't exist. · Synchronizing information. Please do not perform any other operations. · The DHCP bind IP info doesn't exist. · Please specify the ID of the IP-MAC binding entry. · Please specify the IP address to delete. · The specified IP address is invalid. · The DHCP server IP is required. · Please first synchronize DHCP server information.

DHCP forbidden IP

Create DHCP forbidden IP

Keyword	CREATE_DHCP_FORBIDDEN_IP_OP
Message text	Created DHCP forbidden IP: $1
Variable fields	$1: IP addresses exclueded from DHCP dynamic address allocation.
Example	Created DHCP forbidden IP: { "id": "b21adf3f-1eeb-4a3b-9a3f-2a5cbaafa324", "dhcp_server_id": "63be9e42-c9d4-4d45-b415-5b630a505ee8", "start_ip": "1.1.1.160", "end_ip": "1.1.1.200" }
Explanation	An IP address was excluded from DHCP dynamic allocation.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · The request is invalid. · The UUID of the specified excluded IP range already exists. · The DHCP server doesn't exist. · The start or end IP address of the excluded IP range is invalid. · The end IP address of the excluded IP range must be higher than the start IP address. · The excluded IP range overlaps with an existing one. · The specified UUID already exists. · An excluded IP range can contain a maximum of 255 IP addresses. · Unknown error.

Delete DHCP forbidden IP

Keyword	DELETE_DHCP_ FORBIDDEN_IP_OP
Message text	Deleted DHCP forbidden IP $1
Variable fields	$1: ID of the IP address excluded from DHCP dynamic allocation.
Example	Deleted DHCP forbidden IP 14ed05b2-2a52-4f04-aa4e-6f215e622a39.
Explanation	An IP address excluded from DHCP dynamic allocation was deleted.
Possible failure causes	· The specified resource doesn't exist. · Configuration recovery is in progress. · The controller is not the active leader. · The DHCP server doesn't exist. · Unknown error.

DHCP option

Add DHCP option

Keyword	CREATE_DHCP_OPTION_OP
Message text	Added dhcp address pool option: $1
Variable fields	$1: DHCP server option information.
Example	Added dhcp address pool option: serverName: [33] poolName: [34] optionCode: [4] optionValue: [abcde]
Explanation	A DHCP server option was added.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · The request is invalid. · The option value is an integer in the range of 2 to 254. · The DHCP server doesn't exist. · The option value in ASCII format supports a maximum of 255 characters. · The option value in hexadecimal format supports a maximum of 256 characters. · The option value must be in hexadecimal format. · The value must start with 0x. · If the IP address pool belongs to a Layer 2 network domain, Available option codes do not contain 3 6 43 50 51 52 53 54 56 58 59 61 and 82. · Available option codes do not contain 3 6 50 51 52 53 54 56 58 59 61 66 67 and 82. · Options are configurable only for vDHCP. · The DHCP server coupling is error. · Only in address pools with an origin of Auto Deployment (the NEM module) or Policy (the Campus module). · Please make sure both option code and value are specified. · The option value is an integer in the range of 2 to 254. · The option value field can contain only eight IP addresses. · The value must be a space-separated list of IP addresses in dotted decimal notation. Broadcast, loopback, multicast, and reserved IP addresses are not supported. · The selected option does not exist. · Supported node type values are 0x01, 0x02, 0x04, and 0x08. · The length of hexadecimal string must be an even number in the range of 2 to 256. · Please verify that all IP addresses in the IP list are unique. · Unknown error.

Delete DHCP option

Keyword	DELETE_DHCP_OPTION_OP
Message text	Deleted option of dhcp address pool, DHCP server name: $1, ip pool name: $2, option code is: $3
Variable fields	$1: Name of the DHCP server. $2: Name of the DHCP address pool. $3: DHCP server option code.
Example	Deleted option of dhcp address pool, DHCP server name: 33, ip pool name: 34, option code is: 15
Explanation	A DHCP server option was deleted.
Possible failure causes	· The specified resource doesn't exist. · Configuration recovery is in progress. · The controller is not the active leader. · The DHCP server doesn't exist. · The DHCP address pool doesn't exist. · Unknown error.

Fabrics

This section contains fabric messages.

Create Fabric

Keyword	CREATE_FABRIC_OP
Message text	Created fabric: $1
Variable fields	$1: Fabric configuration.
Example	Created fabric: ID: [9cd56545-d3b9-428e-bbf5-5a88313ec039] Name: [fabric1] Underlay protocol: [BGP] EVPN: [true] ARP control: [ ARP flooding: [false] ARP proxy: [false] ARP to controller: [false] ] DHCP control: [ DHCP to controller: [false] ] RARP Ctrl: [ RARP flooding: [false] RARP to controller: [false] ] LLDP to controller: [false] AS number: [65534]. ospf_area_id: [1]
Explanation	A user created a fabric.
Possible failure causes	· Configuration recovery is in progress. · The service has not been found. · The controller is not the active leader. · The fabric already exists. · The fabric name already exists. · Parameters (parameters) are required. · Unknown error. · The request is invalid. · Failed to create the fabric. · The fabric name cannot exceed 255 characters. · The VTEP IP allocation mode is incorrect. · The underlay protocol is invalid. · The AS number is invalid. · The AS number already exists. · Invalid ARP configuration. · Invalid ARP proxy configuration. · Invalid ARP flooding configuration. · Invalid ARP to controller configuration. · Invalid RARP configuration. · Invalid RARP to controller configuration. · Invalid RARP flooding configuration. · Invalid DHCP configuration. · Invalid DHCP to controller configuration. · Invalid ND configuration. · Invalid ND proxy configuration. · Invalid NSNA flooding configuration. · Invalid NSNA to controller configuration. · Invalid RSRA to controller configuration. · Invalid RSRA flooding configuration. · Invalid DHCPv6 configuration. · Invalid DHCPv6 to controller configuration. · Invalid mac advertising configuration. · The RR MAC address list contains invalid MAC addresses. · You must create a device whitelist for the fabric when the underlay protocol is IS-IS and the master spine is configured to assign VTEP IPs. · The default fabric cannot be created. · The default fabric ID cannot be used. · The fabric name is default fabric name. · The VTEP IP allocation mode is incorrect. · The OSPF area ID must be an integer in the range of 0 to 4294967295. · OSPF area ID is not supported for a VXLAN-based fabric. · You must specify an OSPF area ID for a VLAN-based fabric.

Update Fabric

Keyword	UPDATE_FABRIC _OP
Message text	Updated fabric: $1
Variable fields	$1: Fabric configuration.
Example	Updated fabric: ID: [9cd56545-d3b9-428e-bbf5-5a88313ec039] Name: [fabric1] Underlay protocol: [BGP] EVPN: [true] ARP control: [ ARP flooding: [false] ARP proxy: [false] ARP to controller: [false] ] DHCP control: [ DHCP to controller: [false] ] RARP control: [ RARP flooding: [false] RARP to controller: [false] ] LLDP to controller: [false] AS number: [65534].
Explanation	A user changed the configuration of a fabric.
Possible failure causes	· Configuration recovery is in progress. · The service has not been found. · The controller is not the active leader. · The fabric does not exist. · The fabric name already exists. · Parameters (parameters) cannot be modified. · Unknown error. · The request is invalid. · The fabric name cannot exceed 255 characters. · The VTEP IP allocation mode is incorrect. · The underlay protocol is invalid. · Invalid ARP configuration. · Invalid ARP proxy configuration. · Invalid ARP flooding configuration. · Invalid ARP to controller configuration. · Invalid RARP configuration. · Invalid RARP to controller configuration. · Invalid RARP flooding configuration. · Invalid DHCP configuration. · Invalid DHCP to controller configuration. · Invalid ND configuration. · Invalid ND proxy configuration. · Invalid NSNA flooding configuration. · Invalid NSNA to controller configuration. · Invalid RSRA to controller configuration. · Invalid RSRA flooding configuration. · Invalid DHCPv6 configuration. · Invalid DHCPv6 to controller configuration. · Invalid mac advertising configuration. · The AS number is used by a device configuration template, and cannot be deleted. · The AS number is used by a fabric connection, and cannot be modified. · The AS number is used by a group gateway, and cannot be modified. · The underlay protocol is used by a deployment resource pool, and cannot be modified. · The underlay protocol is used by a device configuration template, and cannot be modified. · The RR MAC cannot be modified because the corresponding device is active. · You must create a device whitelist for the fabric when the underlay protocol is IS-IS and the master spine is configured to assign VTEP IPs. · The VTEP IP allocation method has been bound to an address pool, and cannot be modified. · The VTEP IP allocation method has been bound to a device configuration template, and cannot be modified. · The fabric name is default fabric name. · The default fabric name cannot be modified. · Failed to update the default fabric. · The VTEP IP allocation method has been bound to an address pool, and cannot be modified. · The VTEP IP allocation method has been bound to a device configuration template, and cannot be modified. · The OSPF area ID must be an integer in the range of 0 to 4294967295. · You cannot edit the OSPF area ID. · OSPF area ID is not supported for a VXLAN-based fabric. · You must specify an OSPF area ID for a VLAN-based fabric.

Delete Fabric

Keyword	DELETE_FABRIC _OP
Message text	Deleted fabric: $1
Variable fields	$1: Fabric UUID.
Example	Deleted fabric: 218b5f2f-e435-4365-a1ab-0eaa03b7fa19
Explanation	A user deleted a fabric.
Possible failure causes	· Configuration recovery is in progress. · The service has not been found. · The controller is not the active leader. · The fabric does not exist. · Unknown error. · The request is invalid. · The fabric has devices. · The fabric has border device groups. · The fabric is being used by a VDS. · The fabric is being used by a host. · The fabric is used by a configuration template, and cannot be deleted. · The fabric is used by a device control protocol template, and cannot be deleted. · The fabric is used by a deployment resource pool, and cannot be deleted. · The default fabric cannot be deleted. · The fabric is being used by a network range.

Search Fabric

Keyword	SEARCH_FABRIC _OP
Message text	Searched fabric: $1
Variable fields	$1: Fabric UUID. If no UUID is specified, all fabrics are searched.
Example	Searched fabric: 218b5f2f-e435-4365-a1ab-0eaa03b7fa19
Explanation	A user searched a fabric.
Possible failure causes	· Configuration recovery is in progress. · The service has not been found. · The controller is not the active leader. · The fabric does not exist. · Unknown error. · The request is invalid. · The page number must be an integer in the range of 1 to 2147483647. · The number of items per page must be an integer in the range of 1 to 2147483647.

Create Fabric Connection

Keyword	CREATE_FABRIC_CONNECTION_OP
Message text	Created fabric connection: $1
Variable fields	$1: Fabric connection configuration.
Example	Created fabric connection: ID:[e7f605c0-2336-4e4a-8586-69cd543455bc] Name:[e7f605c0-2336-4e4a-8586-69cd543455bc] VDS ID:[ffffffff-0000-0000-0000-000000000001] Connection type:[DEFINED] Default fabric connection:[false] ED groups:[ Local ED ID: d4dd289e-ae05-43c3-b2ee-16be09a01f3f Peer ED ID: b1b2003c-dbe0-43f4-bea2-40c76edd1a32 Local ED ID: d4dd289e-ae05-43c3-b2ee-16be09a01f3f Peer ED ID: c20e22a7-3c95-4f3a-8a70-fb8b8d2b6576 Local ED ID: b1b2003c-dbe0-43f4-bea2-40c76edd1a32 Peer ED ID: c20e22a7-3c95-4f3a-8a70-fb8b8d2b6576 ]
Explanation	A user created a fabric connection.
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 VDS ID is required. · The VDS does not exist. · The VDS already has a fabric connection. · The fabric connection already exists. · The fabric connection name already exists. · The fabric connection type is required. · Invalid name. · The fabric connection type is invalid. · The VSM service does not exist. · Invalid VDS ID. · The ED group settings are invalid. · Invalid local or peer ED exist. · Cannot configure ED group settings when the fabric connection type is ALLCONNECT. · The ED group settings are required when the fabric connection type is DEFINED. · Cannot specify nonexistent EDs. · The local and peer EDs cannot be the same. · The local and peer EDs in an ED group cannot belong to the same fabric. · The local or peer ED is not added to a DC interconnection gateway group. · Unknown internal server error.

Update Fabric Connection

Keyword	UPDATE_FABRIC_CONNECTION_OP
Message text	Updated fabric connection: $1
Variable fields	$1: Fabric connection configuration.
Example	Updated fabric connection: ID:[e7f605c0-2336-4e4a-8586-69cd543455bc] Connection type:[DEFINED] Default fabric connection:[false] ED groups:[ Local ED ID: d4dd289e-ae05-43c3-b2ee-16be09a01f3f Peer ED ID: b1b2003c-dbe0-43f4-bea2-40c76edd1a32 Local ED ID: d4dd289e-ae05-43c3-b2ee-16be09a01f3f Peer ED ID: c20e22a7-3c95-4f3a-8a70-fb8b8d2b6576 Local ED ID: b1b2003c-dbe0-43f4-bea2-40c76edd1a32 Peer ED ID: c20e22a7-3c95-4f3a-8a70-fb8b8d2b6576 ]
Explanation	A user changed the configuration of a fabric connection.
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 fabric connection already exists. · The fabric connection name already exists. · The fabric connection type is required. · Read-only parameters cannot be modified. · Invalid name. · The fabric connection type is invalid. · The VSM service does not exist. · Invalid VDS ID. · The ED group settings are invalid. · Invalid local or peer ED exist. · Cannot configure ED group settings when the fabric connection type is ALLCONNECT. · The ED group settings are required when the fabric connection type is DEFINED. · Cannot specify nonexistent EDs. · The local and peer EDs cannot be the same. · The local and peer EDs in an ED group cannot belong to the same fabric. · The local or peer ED is not added to a DC interconnection gateway group. · Unknown internal server error.

Delete Fabric Connection

Keyword	DELETE_FABRIC_CONNECTION_OP
Message text	Deleted fabric connection: ID: $1 Name: $2
Variable fields	$1: Fabric connection UUID. $2: Fabric connection name.
Example	Deleted fabric connection: ID: [218b5f2f-e435-4365-a1ab-0eaa03b7fa19] Name: [fabric_conn]
Explanation	A user deleted a fabric connection.
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 fabric connection UUID is required. · The fabric connection does not exist. · Unknown internal server error.

General Group

This section contains operation log messages of the general group module.

Create general group

Keyword	CREATE_GENERAL_GROUP_OP
Message text	Created general group: $1.
Variable fields	$1: Information about the created general group.
Example	Created general group: ID:[cee6d907-7dd7-4d18-9e83-e55bdeb031f8] Name:[default_leaf_group] Description:[515] Type:[DEVICE_GROUP]
Explanation	A general group was created.
Possible failure causes	· Invalid JSON format. · The general group name already exists. · Unknown internal server error. · The specified fabric doesn’t exist.

Update general group

Keyword	UPDATE_GENERAL_GROUP_OP
Message text	Updated general group: $1
Variable fields	$1: General group information.
Example	Updated general group: ID:[cee6d907-7dd7-4d18-9e83-e55bdeb031f8] Name:[default_leaf_group] Description:[test] Type:[DEVICE_GROUP]
Explanation	A general group was updated.
Possible failure causes	· Invalid JSON format. · The general group with the specified ID does not exist. · Unknown internal server error.

Delete general group

Keyword	DELETE_GENERAL_GROUP_OP
Message text	Deleted general group: $1
Variable fields	$1: General group information.
Example	Deleted general group: ID:[cee6d907-7dd7-4d18-9e83-e55bdeb031f8] Name:[default_leaf_group] Description:[test] Type:[DEVICE_GROUP]
Explanation	A general group was deleted.
Possible failure causes	· Invalid JSON format. · The general group with the specified ID does not exist.

Add device to device group

Keyword	ADD_DEVICE_GENERALGROUP_OP
Message text	Added $1 devices to device group: $2.
Variable fields	$1: Number of devices added. $2: Device group information.
Example	Added 10 devices to device group: ID:[cee6d907-7dd7-4d18-9e83-e55bdeb031f8] Name:[default_leaf_group] Description:[515] Type:[DEVICE_GROUP]
Explanation	Devices were added to a device group.
Possible failure causes	· Invalid JSON format. · The device group with the specified ID does not exist. · The NE doesn't exist. · The network element is being deleted or being removed from the gateway group or being removed from the fabric. · The device has already belonged to the device group. · Unknown internal server error.

Delete device from device group

Keyword	DELETE_DEVICE_GENERALGROUP_OP
Message text	Deleted $1 devices from device group: $2.
Variable fields	$1: Number of devices deleted. $2: Device group information.
Example	Deleted 10 devices from device group: ID:[cee6d907-7dd7-4d18-9e83-e55bdeb031f8] Name:[default_leaf_group] Description:[515] Type:[DEVICE_GROUP]
Explanation	Devices were deleted from a device group.
Possible failure causes	· Invalid JSON format. · The device group with the specified ID does not exist. · The NE doesn't exist. · The network element is being deleted or being removed from the gateway group or being removed from the fabric. · The device doesn't belong to this device group. · Unknown internal server error.

Add interface to interface group

Keyword	ADD_INTERFACE_GENERAL_GROUP_OP
Message text	Added $1 interfaces to interface group: $2.
Variable fields	$1: Number of interfaces added. $2: Interface group information.
Example	Added 10 interfaces to interface group: ID:[cee6d907-7dd7-4d18-9e83-e55bdeb031f8] Name:[default_leaf_group] Description:[515] Type:[INTERFACE_GROUP]
Explanation	Interfaces were added to an interface group.
Possible failure causes	· Invalid JSON format. · The interface group with the specified ID does not exist. · The NE doesn't exist. · The network element is being deleted or being removed from the gateway group or being removed from the fabric. · The interface has been the member of this interface group. · Unknown internal server error. · A static access interface group does not support interfaces on leaf devices. · An interface can be assigned to only one static access or authentication-free interface group. · The static access interface group bind by network range. · The port isolate device group add dev illegal. · The device already used by port isolate device group. · Only interfaces on access devices can be added to authentication-free interface groups.

Delete interface from interface group

Keyword	DELETE_INTERFACE_GENERAL_GROUP_OP
Message text	Deleted $1 interfaces from interface group: $2.
Variable fields	$1: Number of interfaces deleted. $2: Interface group information.
Example	Deleted 10 interfaces from interface group: ID:[cee6d907-7dd7-4d18-9e83-e55bdeb031f8] Name:[default_leaf_group] Description:[515] Type:[INTERFACE_GROUP]
Explanation	Interfaces were deleted from an interface group.
Possible failure causes	· Invalid JSON format. · The interface group with the specified ID does not exist. · The NE doesn't exist. · The network element is being deleted or being removed from the gateway group or being removed from the fabric. · The interface does not exist in this interface group. · Unknown internal server error. · The static access interface group bind by network range.

Bind policy

Keyword	BIND_POLICY_OP
Message text	Bound $1 policies to general group: $2.
Variable fields	$1: Number of policies bound. $2: Information about the bound general group.
Example	Bound 10 policies to general group: ID:[cee6d907-7dd7-4d18-9e83-e55bdeb031f8] Name:[default_leaf_group] Description:[515] Type:[INTERFACE_GROUP]
Explanation	Policies were bound to a general group.
Possible failure causes	· Invalid JSON format. · The general group with the specified ID does not exist. · The specified policy does not exist. · Failed to bind to the general group: The same category field exists in the template. · The bound template type does not match. · The group policy has already been bound to a general group. · Cannot bind this policy to this general group. · Unknown internal server error.

Unbind policy

Keyword	UNBIND_POLICY_OP
Message text	Unbound $1 policies from general group: $2.
Variable fields	$1: Number of policies unbound. $2: Information about the unbound general group.
Example	Unbound 10 policies from general group: ID:[cee6d907-7dd7-4d18-9e83-e55bdeb031f8] Name:[default_leaf_group] Description:[testdev] Type:[INTERFACE_GROUP]
Explanation	Policies were unbound from a general group.
Possible failure causes	· Invalid JSON format. · The general group with the specified ID does not exist. · The policy is not bound to this general group. · Unknown internal server error.

IDM

This section contains IDM messages.

Add NETCONF template

Keyword	ADD_NETCONF_TEMPLATE_OP
Message text	Added a NETCONF template: id: $1 templateName: $2 vender: $3 description:$4 createType: $5 netConfProtocolList: [ { id: $6 type: $7, netConfInfo: $8 tempId: $9 } ].
Variable fields	$1: NETCONF template ID. $2: NETCONF template name. $3: Vendor name. $4: Template description. $5: Creation mode. Options include 0, 1, and 2. 0 indicates that the template is created on the configuration page. 1 represents normal creation used for automation templates. 2 represents templates created for devices. $6: NETCONF protocol ID. $7: NETCONF template type. Options include 0 and 1. 0 represents HTTP and 1 represents HTTPS. Only HTTPS is supported in the current software version. $8: NETCONF information. $9: Template ID.
Example	Added a NETCONF template: id: [1] templateName: [TEST_NETCONF] vender: [1] description: [] createType: [0] netConfProtocolList: [ { id: [1] type: [1] netConfInfo:[ type=1%%accessType=SOAP/HTTPS%%protocol=HTTPS%% port=832%%rootPath=/soap/netconf/%%userName=adg%% password=cbjaLmV3o4lxV+CzQPCumA==%%] tempId: [1] } ]
Explanation	A NETCONF template was added.
Possible failure causes	· The NETCONF template parameters cannot be empty. · The controller is not the active leader. · Configuration recovery is in progress. · The NETCONF template name is required. · The NETCONF template name already exists. · The value of the protocol type field can only be 1. · The protocol type is required. · The NETCONF template protocol type must be the same as that in the NETCONF information. · The NETCONF information must contain a username and a password. · The NETCONF information is required. · The value of the NETCONFtemplate ID is an integer in the range of 1 to 2147483647. · The value of the protocol ID is an integer in the range of 1 to 2147483647. · A maximum of one protocol is supported in the NETCONF protocol list. · The value of the creation type field can only be 0, 1, or 2. · The vender is required. · The value of the vender is an integer in the range of 1 to 2147483647. · The netConfProtocolList can not be null. · Failed to synchronize information from the primary controller to the backup controller. · The netConfInfo field can contain up to 255 characters. · The description field can contain up to 255 characters. · The NETCONF template name field can contain up to 255 characters. · Unknown system error. · Invalid JSON format.

Update NETCONF template

Keyword	UPDATE_NETCONF_TEMPLATE_OP
Message text	Updated NETCONF template $1: id: $2 templateName: $3 vender: $4 description:$5 createType: $6 netConfProtocolList: [ { id: $7 , type: $8, netConfInfo: $9, tempId: $10 } ]
Variable fields	$1: NETCONF template ID. $2: NETCONF template ID. $3: NETCONF template name. $4: Vendor name. $5: NETCONF template description. $6: Creation mode. Options include 0, 1, and 2. 0 indicates that the template is created on the configuration page. 1 represents normal creation used for automation templates. 2 represents templates created for devices. $7: NETCONF protocol ID. $8: NETCONF template type. Options include 0 and 1. 0 represents HTTP and 1 represents HTTPS. Only HTTPS is supported in the current software version. $9: NETCONF protocol information. $10: Template ID.
Example	Updated NETCONF template 1: id: [1], templateName: [TEST_NETCONF], vender: [1] description: [] createType: [0] netConfProtocolList: [ { id: [1] type: [1] netConfInfo:[ type=1%%accessType=SOAP/HTTPS%%protocol=HTTPS%% port=832%%rootPath=/soap/netconf/%%userName=adg%% password=cbjaLmV3o4lxV+CzQPCumA==%%] tempId: [1] } ]
Explanation	A NETCONF template was modified.
Possible failure causes	· The NETCONF template parameters cannot be empty. · The controller was not the active leader. · Configuration recovery is in progress. · The value of the protocol type field can only be 1. · The protocol type is required. · The NETCONF template protocol type must be the same as that in the NETCONF information. · The NETCONF information must contain a username and a password. · The NETCONF information is required. · The value of the NETCONF template ID is an integer in the range of 1 to 2147483647. · The value of the protocol ID is an integer in the range of 1 to 2147483647. · A maximum of one protocol is supported in the NETCONF protocol list. · The value of the creation type field can only be 0, 1, or 2. · The vender is required. · The value of the vender is an integer in the range of 1 to 2147483647. · Failed to synchronize information from the primary controller to the backup controller. · Unknown system error. · The NETCONF template ID must be the same as that in the NETCONF information. · The protocol ID does not exist. · The netConfProtocolList cannot be null. · The protocol ID cannot be null. · Invalid JSON format. · The netConfInfo field can contain up to 255 characters. · The description field can contain up to 255 characters. · The NETCONF template name field can contain up to 255 characters. · The NETCONF template ID is required in NETCONF protocol list. · The NETCONF template ID does not exist.

Delete NETCONF template

Keyword	DELETE_NETCONF_TEMPLATE_OP
Message text	Deleted NETCONF template: $1.
Variable fields	$1: NETCONF template ID.
Example	Deleted NETCONF template: 1.
Explanation	A NETCONF template was deleted.
Possible failure causes	· The controller was not the active leader. · Configuration recovery is in progress. · Failed to synchronize information from the primary controller to the backup controller. · Unknown system error. · The value of the NETCONF template ID is an integer in the range of 1 to 2147483647. · The NETCONF template ID does not exist.

Add configuration file

Keyword	ADD_CONF_FILE_OP
Message text	Added a configuration file: confFileName:$1 confFileType:$2 cfgFileParent:$3 appliedDevices:$4 content:$5
Variable fields	$1: Configuration file name. $2: Configuration file type. Options include -1, 1, and 2. -1 represents folder, 1 represents configuration file, and 2 represents configuration snippet. $3: ID of the folder to which the file belongs. $4: IDs of the devices to which the configuration file is applicable. $5: Configuration file contents.
Example	Added a configuration file: confFileName:[test_json_4.cfg] confFileType:[-1] cfgFileParent:[-1] appliedDevices:[1] content:[system test ]
Explanation	A configuration file was added.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · The configuration file parameters cannot be empty. · Failed to add the configuration file. The values of the configuration file type and configuration file ID fields can contain only digits. · The configuration file does not folder. · Failed to synchronize information from the primary controller to the backup controller. · Configuration recovery is in progress. · The configuration file name is required. · The configuration file type is required. · The value of the configuration file type can only be –1,1 or 2. · The confFileName field can contain up to 255 characters. · The confFilePath field can contain up to 255 characters. · The appliedDevices field can contain up to 255 characters. · The configuration file contents are required. · The configuration file folder is required. · The configuration file folder does not exist. · The configuration file name already exists. · Unknown system error.

Delete configuration file

Keyword	DELETE_CONF_FILE_OP
Message text	Deleted configuration file $1.
Variable fields	$1: Configuration file ID.
Example	Deleted configuration file 1.
Explanation	A configuration file was deleted.
Possible failure causes	· Data synchronization error. · Data channel error. · The configuration file ID is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · The configuration file does not exist. · Unknown system error.

Deploy configuration snippets

Keyword	DEPLOY_CONF_SNIPPET_OP
Message text	Deployed configuration snippets to the device:$1
Variable fields	$1: Configuration snippet contents.
Example	Deployed configuration snippets to the device: confFileId:[3] deviceIds:[1] replaceParams:[[ReplaceParamRs [key=, value=]]] confFilePath:[\] confFileName:[test_json_4.cfg]
Explanation	Configuration snippets were deployed to a device.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · The configuration file ID is invalid. · The configuration file folder does not exist. · The file must be a configuration segment file. · Invalid device ID. · The device ID does not exist. · The request is invalid. · The configuration file name is required. · The parameters are empty. · Unknown system error.

Deploy commands

Keyword	DEPLOY_COMMAND_OP
Message text	Deployed commands to the device:$1
Variable fields	$1: Device ID and deployed commands.
Example	Deployed commands to the device: deviceId:[2] cmdlist:[[CmdList [cmd=[system, test]]]]
Explanation	Commands were deployed to a device and executed.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · The request is invalid. · The parameters are empty. · Invalid device ID. · The device ID does not exist. · The configuration list that the controller deployed to the device is empty. · Unknown system error.

Start automatic configuration process

Keyword	START_DEVICE_AUTO_CFG_OP
Message text	Started the automatic configuration process for device $1.
Variable fields	$1: Device ID.
Example	Started the automatic configuration process for device 1011.
Explanation	Started the automatic configuration process for a device.
Possible failure causes	· Invalid JSON format. · Service not started. · Configuration recovery is in progress. · The controller is not the active leader. · Invalid device ID. · The asset information does not exist. · The device IP corresponding to the device ID does not exist. · The configuration list that the controller deployed to the device is empty. · The IP address of the master node is invalid. · Internal error.

Stop automatic configuration process

Keyword	STOP_DEVICE_AUTO_CFG_OP
Message text	Stopped the automatic configuration process for device $1.
Variable fields	$1: Device ID.
Example	Stopped the automatic configuration process for device 1011.
Explanation	Stopped the automatic configuration process for a device.
Possible failure causes	· Invalid JSON format. · Service not started. · Configuration recovery is in progress. · The controller is not the active leader. · Invalid device ID. · The asset information does not exist. · The device IP corresponding to the device ID does not exist. · The configuration list that the controller deployed to the device is empty. · The IP address of the master node is invalid. · Internal error.

Add SNMP template

Keyword	ADD_SNMP_TEMPLATE_OP
Message text	Added an SNMP template:$1
Variable fields	$1: SNMP template information.
Example	Added an SNMP template: id: [34] name: [test1] version: [2] type: [1] paraType: [SNMPv2c] retries: [3] timeout: [5] roCommunity: [public] rwCommunity: [private] snmpPort: [161] accessType: [1] isAutodiscoverTemp: [1] creator: [creator] operatorGroupStr: []
Explanation	An SNMP template was created.
Possible failure causes	· Invalid json format. · The controller is not the active leader. · Configuration recovery is in progress. · The SNMP template name already exists. · The SNMP template ID is invalid. · The SNMP template name cannot exceed 64 characters. · The value of the version field can only be 2. · The value of the timeout is an integer in the range of 1 to 60 (seconds). · The value of the retries is an integer in the range of 1 to 20. · The timeout is required. · The retries is required. · The value of the isAutodiscoverTemp field can only be 1 or 2. · The value of the accessType field can only be 1 or 2. · The value of the type field can only be 0 or 1. · Failed to synchronize information from the primary controller to the backup controller. · Unknown error. · The snmpPort value is an integer in the range of 1 to 65535. · The roCommunity field can contain up to 96 characters. · The rwCommunity field can contain up to 96 characters. · The creator field can contain up to 255 characters. · The operatorGroupStr field can contain up to 255 characters.

Delete SNMP template

Keyword	DELETE_SNMP_TEMPLATE_OP
Message text	Deleted SNMP template: $1.
Variable fields	$1: SNMP template ID.
Example	Deleted SNMP template: 2.
Explanation	An SNMP template was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · The SNMP template ID is invalid. · The SNMP template ID does not exist. · The default template cannot be deleted.

Update SNMP template

Keyword	UPDATE_SNMP_TEMPLATE_OP
Message text	Updated SNMP template $1:$2
Variable fields	$1: SNMP template ID. $2: SNMP template information.
Example	Updated SNMP template 2: id:[34] name: [test] version: [2] type: [1] paraType: [SNMPv2c] retries: [3] timeout: [5] roCommunity: [public] rwCommunity: [private] snmpPort: [161] accessType:[1] isAutodiscoverTemp: [1] creator: [creator] operatorGroupStr: []
Explanation	An SNMP template was modified.
Possible failure causes	· Invalid JSON format. · The controller is not the active leader. · Configuration recovery is in progress. · The SNMP template name already exists. · The SNMP template ID is invalid. · The SNMP template name cannot exceed 64 characters. · The value of the version field can only be 2. · The value of the timeout is an integer in the range of 1 to 60 (seconds). · The value of the retries is an integer in the range of 1 to 20. · The timeout is required. · The number is required. · The value of the isAutodiscoverTemp field can only be 1 or 2. · The value of the accessType field can only be 1 or 2. · The value of the type field can only be 0 or 1. · Failed to synchronize information from the primary controller to the backup controller. · Unknown error. · The SNMP template ID does not exist. · The default template name cannot be modified. · The snmpPort value is an integer in the range of 1 to 65535. · The roCommunity field can contain up to 96 characters. · The rwCommunity field can contain up to 96 characters. · The creator field can contain up to 255 characters. · The operatorGroupStr field can contain up to 255 characters.

Add aggregate interface

Keyword	ADD_AGGRE_INTERFACE_OP
Message text	Added an aggregate interface:$1
Variable fields	$1: Aggregate interface information.
Example	Added an aggregate interface: deviceId: [1] aggregateInterface: [Bridge-Aggregation11] physicalInterface: [WGE1/0/38,WGE1/0/39]
Explanation	An aggregate interface was created.
Possible failure causes	· Invalid JSON format. · The controller is not the active leader. · Configuration recovery is in progress. · The device ID doesn't exist. · The aggregate interface ID is invalid. · The group index cannot be a reserved index. · The group index has been used by another group. · The aggregation group member already exists on the device. · The device ID is required. · Invalid deviceId value. · aggregateInterface is empty. · Invalid aggregateInterface value. · physicalInterface is empty. · Invalid physicalInterface value. · Unknown error.

Update aggregate interface

Keyword	UPDATE_AGGRE_INTERFACE_OP
Message text	Updated aggregate interface: $1
Variable fields	$1: Aggregate interface information.
Example	Updated aggregate interface: deviceId: [1] interfaces: [ Bridge-Aggregation6, Bridge-Aggregation7] model: [1]
Explanation	An aggregate interface was modified.
Possible failure causes	· Invalid JSON format. · The controller is not the active leader. · Configuration recovery is in progress. · The aggregation group doesn’t exist. · The aggregation group member doesn’t exist. · Unknown error. · The value of the interfaces field is invalid. · Invalid deviceId value. · The value of the model field must be 1, 2, or 3. · The device ID doesn't exist.

Configure aggregate interface

Keyword	CONFIG_AGGRE_INTERFACE_OP
Message text	Configured aggregate interfaces:$1
Variable fields	$1: Aggregate interface information.
Example	Configured aggregate interfaces: deviceId: [2] model: [1] aggregate: [Bridge-Aggregation1010,Bridge-Aggregation1012\|Ten-GigabitEthernet2/2/0/15,Bridge-Aggregation1011\|Ten-GigabitEthernet2/2/0/10\|Ten-GigabitEthernet2/2/0/11\|Ten-GigabitEthernet2/2/0/9\|Ten-GigabitEthernet2/2/0/8, Bridge-Aggregation1013] physical: [Ten-GigabitEthernet2/2/0/9\|\|1,Ten-GigabitEthernet2/2/0/8\|bbbbb\|,Ten-GigabitEthernet2/2/0/11,Ten-GigabitEthernet2/2/0/10\|aaaaaaaaaaaa\|1,Ten-GigabitEthernet2/2/0/15\|CCCCCCCC]
Explanation	Aggregate interfaces were configured.
Possible failure causes	· Invalid JSON format. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid deviceId value. · The value of the model field must be 1, 2, or 3. · Port configuration error. · The aggregation and physical fields cannot both be empty. · The aggregation group member doesn't exist. · The aggregation group ID is out of range. · The device ID does not exist. · The group index has been used by another group. · The aggregation group member already exists on the device. · Invalid aggregateInterface value. · Invalid physicalInterface value. · Unknown Error.

Add automated configuration template

Keyword	ADD_AUTOCFG_TEMPLATE_OP
Message text	Added an automated configuration template:$1
Variable fields	$1: Automated configuration template information.
Example	Added an automated configuration template: perspectiveId:[1] gatewayScheme:[2] roleType:[$2] underlayType:[1] fabricId:[ffffffff-0000-0000-0000-000000000001] name:[underlay_ll.template] desc:[testdesc] segment:[] "openOptional": [false], "vtepIpAssignWay": [1], "autoCfgRequiredMap": [ { paraName:[username] paraValue:[admin] paraTip:[Username. 1 to 55 characters. Letters, digits, hyphens (-), and underscores (_) are allowed. Make sure the spine and leaf devices in a data center have the same username and password. ] required:[true] }, { paraName:[master_spine_mac] paraValue:[C4CA-D930-5D6E] paraTip:[MAC addresses of the master spine device, in xxxx-xxxx-xxxx format. All-zero, broadcast, and multicast MAC addresses are not allowed. The second digit cannot be an odd number. Separate different MAC addresses with commas (,). ] required:[true] }, { paraName:[irf_disable] paraValue:[False] paraTip:[IRF fabric state. Options include False and True.] required:[true] }, { paraName:[bgp_as] paraValue:[100] paraTip:[BGP AS number, in the range of 1 to 4294967295. This parameter is applicable only to overlay BGP.] required:[true] }, { paraName:[ntp_server] paraValue:[11.100.65.111] paraTip:[NTP server address. IPv4 address in dotted decimal format.] required:[true] }, { paraName:[password] paraValue:[123456] paraTip:[Password. Letters, digits, hyphens (-), and underscores (_) are allowed. Make sure the spine and leaf devices in a data center have the same username and password. ] required:[true] } ] "autoCfgOptionalMap": [ { paraName:[evpn] paraValue:[True] paraTip:[EVPN enabling state. Options include True and False.] required:[false] } ]
Explanation	An automated configuration template was added.
Possible failure causes	· Invalid JSON format. · The controller is not the active leader. · Configuration recovery is in progress. · The value of the vtepIpAssignWay field can only be 1 or 2. · The default fabric does not exist in the controller. · The value of the openOptional field is invalid. · The underlay protocol type of the fabric must be the same as that specified by the underlayType field. · The VTEP IP allocation mode of the fabric must be the same as that specified by the vtepIpAssignWay field. · The EVPN state of the fabric must be compatible with the gateway mode specified by the gatewayScheme field. · The requested perspectiveId is invalid. · The requested perspectiveId is required. · The requested gatewayScheme is invalid. · The requested gatewayScheme is required. · The requested roleType is invalid. · The requested roleType is required. · The requested underlayType is invalid. · The requested underlayType is required.

Add automation parameters

Keyword	ADD_AUTOPARAM_OP
Message text	Added automation parameters:$1
Variable fields	$1: Information about automation parameters.
Example	Added automation parameters: name:[test] snmpTempId:[1] netconfTempId:[4] netconfTempType:[1] fabricId:[a1fb8545-0b41-4299-8c2d-fdb32bba961b]
Explanation	Automation parameters were added.
Possible failure causes	· Invalid JSON format. · The controller is not the active leader. · Configuration recovery is in progress. · The NETCONF template ID does not exist. · The NETCONF template type does not exist. · The NETCONF template ID is required. · The NETCONF template type is required. · The SNMP template ID is required. · The SNMP template ID does not exist. · The default fabric does not exist in the controller.

Add automation policy

Keyword	ADD_AUTOPOLICY_OP
Message text	Added an automation policy:$1
Variable fields	$1: Automation policy information.
Example	Added an automation policy: name:[test] executeCondition:[4] autoCfgId:[250f362f-de09-4c28-ab01-586451b897a5] autoParamId:[d5c1d35e-62f5-4259-a905-98183d9fd065] softwareId:[bc790ff8-bafe-4c5b-bb39-837a1b16532e] softwarePatchId:[bc790ff8-bafe-4c5b-bb39-837a1b16531e]
Explanation	An automation policy was added.
Possible failure causes	· The controller is not the active leader. · The automation policy name is required. · The policy name is invalid. · The execute condition is invalid. · The executeCondition field cannot be empty. · The automated configuration template ID is required. · The automated configuration template ID is invalid. · The automation parameters are required. · The automation parameter ID is invalid. · The software version or patch is invalid. · Configuration recovery is in progress.

Bring up interfaces

Keyword	BRINGUP_INTERFACE_OP
Message text	Brought up interfaces:$1
Variable fields	$1: Interface information.
Example	Brought up interfaces: begin:[FortyGigE1/0/49] deviceId:[1] end:[FortyGigE1/0/50]
Explanation	Interfaces were brought up.
Possible failure causes	· Invalid request. · Service not started. · Invalid JSON format. · Configuration recovery is in progress. · The controller is not the active leader. · The start interface name is required. · The start interface name is invalid. · The end interface name is required. · The end interface name is invalid. · The device ID is required. · Invalid device ID. · Internal server error.

Shut down interfaces

Keyword	SHUTDOWN_INTERFACE_OP
Message text	Shut down interfaces:$1
Variable fields	$1: Interface information.
Example	Shut down interfaces: begin:[FortyGigE1/0/49] deviceId:[1] end:[FortyGigE1/0/50]
Explanation	Interfaces were shut down.
Possible failure causes	· Invalid request. · Service not started. · Invalid JSON format. · Configuration recovery is in progress. · The controller is not the active leader. · The start interface name is required. · The start interface name is invalid. · The end interface name is required. · The end interface name is invalid. · The device ID is required. · Invalid device ID. · Internal server error.

Configure interface

Keyword	CFG_INTERFACE_OP
Message text	Configured an interface:$1
Variable fields	$1: Interface information.
Example	Configured an interface: interfaceName:[FortyGigE1/0/49] deviceId:[1] portDesc:[ FortyGigE1/0/49 desc] edgedPort:[stp edged-port]
Explanation	An interface was configured.
Possible failure causes	· Invalid request. · Service not started. · Invalid JSON format. · Configuration recovery is in progress. · The controller is not the active leader. · The interface name is required. · The interface name is invalid. · The device ID is required. · Invalid device ID. · Invalid edge interface configuration. · The description cannot exceed 255 characters. · Internal server error.

Add automatic device replacement task

Keyword	ADD_AUTO_REPLACE_TASK_OP
Message text	Added an automatic device replacement task:$1
Variable fields	$1: Automatic device replacement task information.
Example	Added an automatic device replacement task: newDevId:[1] fileId:[2] replaceType:[3] taskName:[testTask] devSn:[13212adasd2q321dadsa] faultDevId:[6] masterSpineMac:[01-23-45-67-89-ab] stackMemberId:[7]
Explanation	An automatic device replacement task was added.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The task name is required. · The device serial number is required. · The failed device ID is required. · The replacement type is required. · The replacement type is invalid. · The master spine MAC does not exist. · The master spine MAC is invalid. · The replacement device does not in asset information. · The fault device does not in asset information. · The fault device is same as replacement device. · The replace device is UN_MANAGED. · The fault device is UN_MANAGED. · Failed to create member ID. · Failed to obtain the maximum stacking capability of the device. · Failed to obtain the master device ID. · Failed to obtain the replacement device ID. · Unknown system error.

Add fabric and deploy resource pool

Keyword	ADD_FABRIC_AND_DEPLOY_RESOURCE_POOL_OP
Message text	Added a fabric and a deploy resource pool:$1
Variable fields	$1: Fabric and deployment resource pool information.
Example	Added a fabric and a deploy resource pool: fabric:[ id: [edfed45a-d3a9-4bb0-bfe3-b5fe5c2c9018] name: [fabric1] underlayProtocol: [BGP] vtepIpAssignWay: [MASTER_SPINE_ALLOC] evpn: [true] arpCtrl: [ arpFlooding: [false] arpProxy: [false] arpToController: [false] ] dhcpCtrl: [ dhcpToController: [false] ] rarpCtrl: [ rarpFlooding: [false] rarpToController: [false] ] ndCtrl: [ ndProxy: [true] nsnaFlooding: [false] nsnaToController: [true] rsraToController: [true] rsraFlooding: [false] ] dhcpv6Ctrl: [ dhcpv6ToController: [true] ] macAdvertising: [false] lldpToController: [false] asNumber: [100] defaultFabric: [false] needWhiteList: [false] rrMacList: [00:01:00:01:00:02 ]], deploy_resource_pool=[ Type: [out-of-band] Fabric ID: [edfed45a-d3a9-4bb0-bfe3-b5fe5c2c9018] DHCP server settings:[ ID: [14ed05b2-2a52-4f04-aa4e-6f215e622a39] ] VTEP IP pool list:[ VTEP IP pool settings :[ ID: [4d43be3b-0f7d-42c2-a5a0-2bbfcdb9dfa1] ] ] Loopback1 pool list:[ loopback1 pool settings :[ ID: [4d43be3b-0f7d-42c2-a5a0-2bbfcdb9dfa2] ] ] Management IP pool list :[ Management IP pool settings :[ ID: [4d43be3b-0f7d-42c2-a5a0-2bbfcdb9dfae] ] ] Vlan1 IP pool list:[ Vlan1 IP pool settings :[ ID: [4d43be3b-0f7d-42c2-a5a0-2bbfcdb9dfa3] ] ] vlan4094PoolConfigs IP pool list:[ vlan4094 IP pool settings :[ ID: [4d43be3b-0f7d-42c2-a5a0-2bbfcdb9dfa3] ] ] ]]
Explanation	A fabric and a deployment resource pool were added.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · The system VDS does not exist. · The default DHCP server does not exist.

NBAC

This section contains NBAC messages.

Create Application Description

Keyword	CREATE_APPLICATION_DESCIRIPTION_OP
Message text	Created application descriptions “$1”.
Variable fields	$1: Application description information.
Example	Created application description "source_name: s1, destination_name: s2, id: 8d8f152e-02df-4354-b63c-a396121dc743".
Explanation	An application description was created.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · Unknown error. · The application description name already exists. · The specified policy does not exist. · The specified policy does not match the policy type. · A unidirectional application description cannot be bound to a policy that contains service chains. · The policy direction is required. · The policy direction is invalid. · The exception policy does not exist. · The policy type is invalid. · An application description cannot be bound to an exception policy that contains rules. · The exception policy has been bound to another application description. · The specified destination type does not support bidirectional policies. · The source traffic characteristic group ID is required. · The destination traffic characteristic group ID is required. · The source and destination traffic characteristic groups of a bidirectional application description must be bound to the same policy. · An application description with the same source and destination traffic characteristic groups already exists. · The application description ID already exists. · Application descriptions with the same source and destination traffic characteristic groups exist in the bulk created application descriptions. · The symmetrical application description has been bound to a policy. · The parameter is required. · The parameter can't be modified. · Internal server error. · Request parameter error. · This operation is not allowed. · This operation has no permissions. · This operation is conflict. · Unknown error code. · The service is disabled. · The policy template contains service chain rules. It cannot be applied to the private network on which the policy application scope includes IPv6 users. · Policy mode differs between the private networks bound to the security group and the service chain. · The network type in the policy template is different from that in the application description. · Invalid network type. · · Make sure the policy mode is the same across the source security group, destination security group, and application description. · The service chain does not support the VLAN network type.

Update Application Description

Keyword	UPDATE_APPLICATION_DESCIRIPTION_OP
Message text	Updated application description “$1”.
Variable fields	$1: Application description information.
Example	Updated application description "source_name: s1, destination_name: s2, id: 63b9b820-09d3-4e92-875e-9e78e0bbcb81"..
Explanation	An application description was modified.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · Unknown error. · The specified application description does not exist. · The destination traffic characteristic group ID cannot be modified. · The source traffic characteristic group ID cannot be modified. · The specified policy does not exist. · The specified policy does not match the policy type. · A unidirectional application description cannot be bound to a policy that contains service chains. · The policy direction is required. · The policy direction is invalid. · Exception policies containing rules cannot be modified. · The specified exception policy ID does not exist. · An application description cannot be bound to an exception policy that contains rules. · The exception policy has been bound to another application description. · The source and destination traffic characteristic groups of a bidirectional application description must be bound to the same policy. · The parameter is required. · The parameter can't be modified. · Internal server error. · Request parameter error. · This operation is not allowed. · This operation has no permissions. · This operation is conflict. · Unknown error code. · The service is disabled. · The policy template contains service chain rules. It cannot be applied to the private network on which the policy application scope includes IPv6 users. · Policy mode differs between the private networks bound to the security group and the service chain. · The network type in the policy template is different from that in the application description · The service chain does not support the VLAN network type.

Delete Application Description

Keyword	DELETE_APPLICATION_DESCIRIPTION_OP
Message text	Deleted application description “$1”.
Variable fields	$1: Application description information.
Example	Deleted application description "source_name: s1, destination_name: s2, id: 8d8f152e-02df-4354-b63c-a396121dc743".
Explanation	An application description was deleted.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · Unknown error. · The specified application description does not exist. · The parameter is required. · The parameter can't be modified. · Internal server error. · Request parameter error. · This operation is not allowed. · This operation has no permissions. · This operation is conflict. · Unknown error code. · The service is disabled.

Create Policy

Keyword	CREATE_POLICY_OP
Message text	Created policies “$1”.
Variable fields	$1: Policy information.
Example	Created policies “Name:[policy3] Type:[policy]”.
Explanation	A policy was added.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · Unknown error. · The policy ID already exists. · The policy name is required. · The policy name cannot exceed 255 characters. · The policy name already exists. · The description cannot exceed 255 characters. · The policy type is required. · The policy type is invalid. · Duplicated IDs exist for the policies created in bulk. · Duplicated names exist for the policies created in bulk. · The parameter is required. · The parameter can't be modified. · Internal server error. · Request parameter error. · This operation is not allowed. · This operation has no permissions. · This operation is conflict. · Unknown error code. · The service is disabled. · Invalid network type. · The network type in the policy template is different from that associated with the time range.

Update Policy

Keyword	UPDATE_POLICY_OP
Message text	Updated policy “ $1”
Variable fields	$1: Policy information.
Example	Updated policy “Name:[ext_policy] Type:[external-policy]”.
Explanation	A policy was modified.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · Unknown error. · The specified policy does not exist. · The default policy cannot be modified. · The policy ID cannot be modified. · The policy name cannot be modified. · The policy type cannot be modified. · The description cannot exceed 255 characters. · The parameter is required. · The parameter can't be modified. · Internal server error. · Request parameter error. · This operation is not allowed. · This operation has no permissions. · This operation is conflict. · Unknown error code. · The service is disabled. · You cannot change the network type in the policy template. · The network type in the policy template is different from that associated with the time range.

Delete Policy

Keyword	DELETE_POLICY_OP
Message text	Deleted policy “$1”.
Variable fields	$1: Policy information.
Example	Deleted policy “Name:[policy3] Type:[policy]”.
Explanation	A policy was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown error. · The specified policy does not exist. · The default policy cannot be deleted. · The policy cannot be deleted because it has been bound to an application description. · The exception policy cannot be deleted because it contains rules. · The parameter is required. · The parameter can't be modified. · Internal server error. · Request parameter error. · This operation is not allowed. · This operation has no permissions. · This operation is conflict. · Unknown error code. · The service is disabled.

Create Rule

Keyword	CREATE_RULE_OP
Message text	Created rules “$1”.
Variable fields	$1: Rule information.
Example	Created rules “Protocol:[IP] Source subnet:[null] Destination subnet:[null] Source port:[null] Destination port:[null] Action:[permit]”.
Explanation	A rule was created.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · Unknown error. · The rule ID already exists. · The policy ID is required. · The specified policy does not exist. · Cannot add, modify, or delete rules for the default policy. · You cannot add rules to an exception policy until you bind the policy to an application description. · The protocol type is required. · The protocol type can only be IP, ICMP, TCP, or UDP. · Invalid port range. · The ACL action is required. · The action can only be permit, deny, or redirect. · Cannot set the action to redirect for rules in an exception policy. · When the action of a rule is redirect, the policy to which the rule belongs must be bound to a bidirectional application description. · A service chain ID can be specified only when the action is redirect. · All rules in the same policy must be bound to the same service chain. · A rule already bound to a policy cannot be bound to another policy. · The IP version can only be 4 or 6. · The specified time range does not exist. · The rule number is out of range. · The source network of a rule is required when its policy is an exception policy. · Invalid source network. · The destination network of a rule is required when its policy is an exception policy. · Invalid destination network. · Duplicated IDs exist for the rules created in bulk. · The parameter is required. · The parameter can't be modified. · Internal server error. · Request parameter error. · This operation is not allowed. · This operation has no permissions. · This operation is conflict. · Unknown error code. · The service is disabled. · The specified rule is the same as an existing rule. · Only one rule that redirects traffic to a service chain can be created in an external network policy template. · The protocol can only be IP for rules in an external network policy template. · A service chain cannot be used by both an internal network policy and an external network policy. · The specified service chain is used by a rule of another external network policy. · The specified service chain has been used by a rule of an internal network policy and cannot be used by a rule of an external network policy any more. · Cannot config service chain rules in the policy template. The policy template has been applied to IPv6 users on a private network. · The Layer 2 network domain with the segment ID as the ingress port VXLAN ID of the service chain member does not exis. · No subnet contains the ingress port IP address of the service chain member. · The Layer 2 network domain with the segment ID as the egress port VXLAN ID of the service chain member does not exist. · No subnet contains the egress port IP address of the service chain member. · Policy mode differs between the private networks bound to the security group and the service chain. · The network type in the policy template is different from that associated with the time range.

Update Rule

Keyword	UPDATE_RULE_OP
Message text	Updated rule “$1”.
Variable fields	$1: Rule information.
Example	Updated rule ”Protocol:[UDP] Source subnet:[null] Destination subnet:[null] Source port:[111] Destination port:[112] Action:[permit]”.
Explanation	A rule was modified.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · Unknown error. · The specified rule does not exist. · Cannot add, modify, or delete rules for the default policy template. · The policy ID cannot be modified. · The IP version cannot be modified. · The rule number is out of range. · The protocol type is required. · The protocol type can only be IP, ICMP, TCP, or UDP. · Invalid port range. · The IP version can only be 4 or 6. · Invalid port. · The specified time range does not exist. · The ACL action is required. · The action can only be permit, deny, or redirect. · Cannot set the action to redirect for rules in an exception policy. · When the action of a rule is redirect, the policy to which the rule belongs must be bound to a bidirectional application description. · The source network of a rule is required when its policy is an exception policy. · Invalid source network. · The destination network of a rule is required when its policy is an exception policy. · Invalid destination network. · When you modify a rule, the number field cannot be null. · A service chain ID can be specified only when the action is redirect. · All rules in the same policy must be bound to the same service chain. · A rule already bound to a policy cannot be bound to another policy. · The parameter is required. · The parameter can't be modified. · Internal server error. · Request parameter error. · This operation is not allowed. · This operation has no permissions. · This operation is conflict. · Unknown error code. · The service is disabled. · The specified rule is the same as an existing rule. · Only one rule that redirects traffic to a service chain can be created in an external network policy. · The protocol can only be IP for rules in an external network policy. · A service chain cannot be used by both an internal network policy and an external network policy. · The specified service chain is used by a rule of another external network policy. · The Layer 2 network domain with the segment ID as the ingress port VXLAN ID of the service chain member does not exis. · No subnet contains the ingress port IP address of the service chain member. · The Layer 2 network domain with the segment ID as the egress port VXLAN ID of the service chain member does not exist. · No subnet contains the egress port IP address of the service chain member. · Policy mode differs between the private networks bound to the security group and the service chain. · The rule has been used in a group policy. You cannot change the action in the rule from Permit or Deny to Redirect. · The rule has been used in a group policy. You cannot change the action in the rule from Redirect to Permit or Deny. · The network type in the policy template is different from that associated with the time range.

Delete Rule

Keyword	DELETE_RULE_OP
Message text	Deleted rule “$1”.
Variable fields	$1: Rule information.
Example	Deleted rule ”Protocol:[IP] Source subnet:[null] Destination subnet:[null] Source port:[null] Destination port:[null] Action:[deny]”.
Explanation	A rule was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown error. · The specified rule does not exist. · Cannot add, modify, or delete rules for the default policy. · The parameter is required. · The parameter can't be modified. · Internal server error. · Request parameter error. · This operation is not allowed. · This operation has no permissions. · This operation is conflict. · Unknown error code. · The service is disabled.

Create Time Range

Keyword	CREATE_TIME_RANGE_OP
Message text	Created time ranges “$1”
Variable fields	$1: Time range name.
Example	Created time ranges “timeRange1”
Explanation	A time range was created.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · Unknown error. · The maximum number of time ranges is 1024. · The time range ID already exists. · The time range name is required. · The time range name cannot exceed 255 characters. · The time range name already exists. · The field length cannot exceed 255 characters. · A time range must contain a minimum of one subrange. · The maximum number of periodical time ranges is 32. · The date or time is required. · The days of week must be specified. · The maximum number of absolute time ranges is 12. · Years 1970 through 2100 are available for time range configuration. · Duplicated IDs exist for the time ranges created in bulk. · Duplicated names exist for the time ranges created in bulk. · The parameter is required. · The parameter can't be modified. · Internal server error. · Request parameter error. · This operation is not allowed. · This operation has no permissions. · This operation is conflict. · Unknown error code. · The service is disabled. · Invalid network type.

Update Time Range

Keyword	UPDATE_TIME_RANGE_OP
Message text	Updated time range “$1”
Variable fields	$1: Time range name.
Example	Updated time range “timeRange1”
Explanation	A time range was modified.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown error. · The time range does not exist. · The time range name cannot be modified. · The field length cannot exceed 255 characters. · A time range must contain a minimum of one subrange. · The maximum number of absolute time ranges is 12. · The date or time is required. · Years 1970 through 2100 are available for time range configuration. · The maximum number of periodical time ranges is 32. · The days of week must be specified. · The parameter is required. · The parameter can't be modified. · Internal server error. · Request parameter error. · This operation is not allowed. · This operation has no permissions. · This operation is conflict. · Unknown error code. · The service is disabled.

Delete Time Range

Keyword	DELETE_TIME_RANGE_OP
Message text	Deleted time range “$1”
Variable fields	$1: Time range name.
Example	Deleted time range “timeRange1”
Explanation	A time range was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown error. · The specified time range does not exist. · The time range is being used and cannot be deleted. · The parameter is required. · The parameter can't be modified. · Internal server error. · Request parameter error. · This operation is not allowed. · This operation has no permissions. · This operation is conflict. · Unknown error code. · The service is disabled.

Create intergroup policy

Keyword	CREATE_INTERGROUP_POLICY_OP
Message text	Created intergroup policy ”$1”.
Variable fields	$1: UUID of the intergroup policy.
Example	Created intergroup policy “1c6d3cf4-d622-4121-b193-bfac63a5e409”.
Explanation	An intergroup policy was created.
Possible failure causes	· An intergroup policy cannot be created between external network security groups. · An intergroup policy cannot be created between a non-external-network security group and an external network security group that do not belong to the same private network. · An exception rule cannot be configured for an intergroup policy created between a non-external-network security group and an external network security group. · Only an external network policy template can be used to create an intergroup policy between a non-external-network security group and an external network security group. · The specified external network policy template has been used by intergroup policies in other private networks. · An external network policy template can only be used to create an intergroup policy between a non-external-network security group and an external network security group. · An intergroup policy cannot be created between an external network security group and a resource group.

Update intergroup policy

Keyword	UPDATE_INTERGROUP_POLICY_OP
Message text	Updated intergroup policy “$1”.
Variable fields	$1: UUID of the intergroup policy.
Example	Updated intergroup policy “1c6d3cf4-d622-4121-b193-bfac63a5e409”.
Explanation	An intergroup policy was updated.
Possible failure causes	· The source private network ID of the intergroup policy cannot be edited. · The destination private network ID of the intergroup policy cannot be edited. · An exception rule cannot be configured for an intergroup policy created between a non-external-network security group and an external network security group. · Only an external network policy template can be used to create an intergroup policy between a non-external-network security group and an external network security group. · The specified external network policy template has been used by intergroup policies in other private networks.

Created policy enforcement device group

Keyword	CREATE_POLICY_ENFORCEMENT_DEVICE_GROUP_OP
Message text	Created policy enforcement device group “$1”
Variable fields	$1：Policy Enforcement Device Group information
Example	Created policy enforcement device group "id: c444adbc-4252-4a57-a9ce-26e078ce6c93 name: test isolateDomianId: 1b55c00a-ef32-4056-b6c1-bfa04afe7549 isolateDomianName: vlan-group deviceList: 24a44e9a-e46d-4ccd-ba1c-8500963677f7,a38e3d62-8d13-4e79-888b-ea52ff942911 defaultPoint: false autoLinked: false".
Explanation	An policy enforcement device group was created.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · Unknown error. · The parameter is required. · Internal server error. · Request parameter error. · This operation is not allowed. · This operation has no permissions. · This operation is conflict. · Unknown error code. · The service is disabled. · The policy execute point id has already been existed. · The default policy enforcement device group has been specified for the isolation domain. · Please specify an isolation domain ID. · The isolation domain ID does not exist. · Please specify a device ID. · The device ID does not exist. · The device IDs are duplicate. · Please specify a security group ID. · The security group ID does not exist. · The security group ids are duplicate. · The policy enforcement device group name already exists. · The security group has been bound to another policy enforcement device group for the isolation domain.

Updated policy enforcement device group

Keyword	UPDATE_POLICY_ENFORCEMENT_DEVICE_GROUP_OP
Message text	Updated policy enforcement device group “$1”
Variable fields	$1：Policy Enforcement Device Group information
Example	Updated policy enforcement device group "id: c444adbc-4252-4a57-a9ce-26e078ce6c93 name: test isolateDomianId: 1b55c00a-ef32-4056-b6c1-bfa04afe7549 isolateDomianName: vlan-group deviceList: 24a44e9a-e46d-4ccd-ba1c-8500963677f7,a38e3d62-8d13-4e79-888b-ea52ff942911 defaultPoint: false autoLinked: false securityGroupList: 2b23bcfd-14ef-4167-8589-2f278d69171f,67b8c22d-ad3f-444b-88fa-2facd978bb61".
Explanation	An policy enforcement device group was modified.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · Unknown error. · The parameter is required. · The parameter can't be modified. · Internal server error. · Request parameter error. · This operation is not allowed. · This operation has no permissions. · This operation is conflict. · Unknown error code. · The service is disabled. · The default policy enforcement device group has been specified for the isolation domain. · You cannot edit the isolation domain ID. · You cannot edit the isolation domain name. · Please specify a device ID. · The device ID does not exist. · The device IDs are duplicate. · Please specify a security group ID. · The security group ID does not exist. · The security group ids are duplicate. · The policy enforcement device group name already exists. · The security group has been bound to another policy enforcement device group for the isolation domain. · You cannot edit the policy enforcement device group name. · You cannot edit the default policy enforcement device group. · The specified resource doesn't exist.

Deleted policy enforcement device group

Keyword	DELETE_POLICY_ENFORCEMENT_DEVICE_GROUP_OP
Message text	Deleted policy enforcement device group “$1”
Variable fields	$1：Policy Enforcement Device Group information
Example	Deleted policy enforcement device group a8f1dace-ec10-437d-90ea-b323a3d3047f.
Explanation	An policy enforcement device group was deleted.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · Unknown error. · The parameter is required. · Internal server error. · Request parameter error. · This operation is not allowed. · This operation has no permissions. · This operation is conflict. · Unknown error code. · The service is disabled. · The specified resource 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: [ VLAN: [2--13], VXLAN: [4--4], Assignment only: [false], Access mode: [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. · Invalid name. · The VLAN ID is invalid or out of range. · Invalid VXLAN ID. · The mapping table already exists. · No name is specified. · Two same mappings exist in the mapping table. · Overlapped mappings exist in the mapping table. · All mappings in the same mapping table must be the same type. · Inconsistent mapping table type and mapping type. · vlanif mapping tables do not support the start_cvlan, end_cvlan, and rewrite_rules parameters. · The reserved VLAN ID conflicts with a VLAN ID of an VLAN-VXLAN mapping. · 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: [ VLAN: [2--13], VXLAN: [4--4], Assignment only: [false], Access mode: [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. · Invalid name. · The VLAN ID is invalid or out of range. · Invalid VXLAN ID. · No name is specified. · Two same mappings exist in the mapping table. · Overlapped mappings exist in the mapping table. · The mapping table doesn't exist. · All mappings in the same mapping table must be the same type. · Inconsistent mapping table type and mapping type. · The mapping table is created through the bare metal module and cannot be modified. · The mapping table is created through the resource access template module and cannot be modified. · The reserved VLAN ID conflicts with a VLAN ID of an VLAN-VXLAN mapping. · Unknown internal server error.

Delete VLAN-VXLAN mapping table

Keyword	DELETE_VLAN-VXLAN_OP
Message text	Deleted VLAN-VXLAN mapping table: ID: $1 Name: $2
Variable fields	$1: VLAN-VXLAN mapping table ID. $2: VLAN-VXLAN mapping table name.
Example	Deleted VLAN-VXLAN mapping table: ID: [e7137b75-0fbb-4f66-9b88-6345d63da951] Name: [222]
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 mapping table is already bound to ports. · The mapping table is already bound to physical access devices. · The mapping table doesn't exist. · The mapping table is created through the bare metal module and cannot be deleted. · The mapping table is created through the resource access template module and cannot be deleted. · Unknown internal server error.

Create QinQ-VXLAN mapping table

Keyword	CREATE_QINQ-VXLAN_OP
Message text	Created QinQ-VXLAN mapping table: $1
Variable fields	$1: QinQ-VXLAN mapping table information.
Example	Created QinQ-VXLAN mapping table: ID: [218b5f2f-e435-4365-a1ab-0eaa03b7fa19] Name: [table] QinQ-VXLAN mappings: [ [ SVLAN: [1--1], CVLAN: [2--3], VXLAN: [3--3], Assignment only: [false], Access mode: [Ethernet] Rewrite rule list: [ Direction: [inbound], Type: [NEST], SVLAN: [1], CVLAN: [2], Symmetric: [false] ] ] ]
Explanation	A QinQ-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. · Invalid name. · The VLAN ID is invalid or out of range. · Invalid VXLAN ID. · The mapping table already exists. · No name is specified. · Overlapped mappings exist in the mapping table. · The QinQ-VXLAN mapping range must be the same as the SVLAN or CVLAN mapping range. · The symmetric parameter can only be configured as false in the outbound rule. · A maximum of one rewrite rule can be configured in one direction of a QinQ-VXLAN mapping. · No outbound rule can be configured if the symmetric parameter has been configured as true for an inbound rule. · The rewrite_svlan_id parameter is required when the rewrite rule in the inbound direction is NEST. · The rewrite_cvlan_id and rewrite_svlan_id parameters cannot be both empty if the rewrite rule is REMARK_ONE. · The rewrite_cvlan_id and rewrite_svlan_id parameters cannot be both empty if the rewrite rule is REMARK_TWO. · The rewrite_svlan_id parameter is required when the rewrite rule in the inbound direction is REMARK_ONE. · The symmetric cannot be configured as true when the rewrite rule in the inbound direction is REMARK_ONE and the rewrite_cvlan_id is greater than 0. · The symmetric cannot be configured as true when the rewrite rule in the inbound direction is REMARK_TWO and both the rewrite_cvlan_id and rewrite_svlan_id are greater than 0. · The rewrite_svlan_id parameter is required when the rewrite rule in the outbound direction is NEST. · The rewrite_svlan_id parameter is required when the rewrite rule in the outbound direction is REMARK_ONE. · The SVLAN mapping range and CVLAN mapping range cannot be both greater than 1. · Invalid rewrite direction. · The rewrite_cvlan_id and rewrite_svlan_id parameters are not required if the rewrite rule is STRIP. · All mappings in the same mapping table must be the same type. · The SVLAN and CVLAN mapping ranges of all mappings in the same mapping table must be the same. · Inconsistent mapping table type and mapping type. · QinQ-VXLAN mapping tables with the VLAN access mode do not support the rewrite_rules parameter. · The gaps between the start IDs and end IDs of the SVLAN mapping range, CVLAN mapping range, and VXLAN mapping range cannot be all greater than 1. · Unknown internal server error. · The reserved VLAN ID conflicts with a VLAN ID of an VLAN-VXLAN mapping.

Update QinQ-VXLAN mapping table

Keyword	UPDATE_QINQ-VXLAN_OP
Message text	Updated QinQ-VXLAN mapping table: $1
Variable fields	$1: QinQ-VXLAN mapping table information.
Example	Updated QinQ-VXLAN mapping table: ID: [218b5f2f-e435-4365-a1ab-0eaa03b7fa19] Name: [table] QinQ-VXLAN mappings: [ [ SVLAN: [1--1], CVLAN: [2--3], VXLAN: [3--3], Assignment only: [false], Access mode: [Ethernet] Rewrite rule list: [ Direction: [inbound], Type: [NEST], SVLAN: [1], CVLAN: [2], Symmetric: [false] ] ] ]
Explanation	A QinQ-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. · Invalid name. · The VLAN ID is invalid or out of range. · Invalid VXLAN ID. · Overlapped mappings exist in the mapping table. · The mapping table doesn't exist. · The QinQ-VXLAN mapping range must be the same as the SVLAN or CVLAN mapping range. · The symmetric parameter can only be configured as false in the outbound rule. · A maximum of one rewrite rule can be configured in one direction of a QinQ-VXLAN mapping. · No outbound rule can be configured if the symmetric parameter has been configured as true for an inbound rule. · The rewrite_svlan_id parameter is required when the rewrite rule in the inbound direction is NEST. · The rewrite_cvlan_id and rewrite_svlan_id parameters cannot be both empty if the rewrite rule is REMARK_ONE. · The rewrite_cvlan_id and rewrite_svlan_id parameters cannot be both empty if the rewrite rule is REMARK_TWO. · The rewrite_svlan_id parameter is required when the rewrite rule in the inbound direction is REMARK_ONE. · The symmetric cannot be configured as true when the rewrite rule in the inbound direction is REMARK_ONE and the rewrite_cvlan_id is greater than 0. · The symmetric cannot be configured as true when the rewrite rule in the inbound direction is REMARK_TWO and both the rewrite_cvlan_id and rewrite_svlan_id are greater than 0. · The rewrite_svlan_id parameter is required when the rewrite rule in the outbound direction is NEST. · The rewrite_svlan_id parameter is required when the rewrite rule in the outbound direction is REMARK_ONE. · The SVLAN mapping range and CVLAN mapping range cannot be both greater than 1. · Invalid rewrite direction. · The rewrite_cvlan_id and rewrite_svlan_id parameters are not required if the rewrite rule is STRIP. · All mappings in the same mapping table must be the same type. · The SVLAN and CVLAN mapping ranges of all mappings in the same mapping table must be the same. · Inconsistent mapping table type and mapping type. · QinQ-VXLAN mapping tables with the VLAN access mode do not support the rewrite_rules parameter. · The gaps between the start IDs and end IDs of the SVLAN mapping range, CVLAN mapping range, and VXLAN mapping range cannot be all greater than 1. · Unknown internal server error. · The reserved VLAN ID conflicts with a VLAN ID of an VLAN-VXLAN mapping.

Delete QinQ-VXLAN mapping table

Keyword	DELETE_QINQ-VXLAN_OP
Message text	Deleted QinQ-VXLAN mapping table: $1
Variable fields	$1: QinQ-VXLAN mapping table ID.
Example	Deleted QinQ-VXLAN mapping table: 218b5f2f-e435-4365-a1ab-0eaa03b7fa19
Explanation	A QinQ-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 mapping table is already bound to ports. · The mapping table is already bound to physical access devices. · The 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 about 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. · Invalid name. · The 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. · The port on the specified device has been bound to a QinQ-VXLAN mapping table. · The QinQ-VXLAN mapping table does not support device binding. · 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 about 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. · Invalid name. · The 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. · The port on the specified device has been bound to a QinQ-VXLAN mapping table. · The QinQ-VXLAN mapping table does not support device binding. · 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 ID.
Example	Deleted VLAN-VXLAN mapping table binding: 218b5f2f-e435-4365-a1ab-0eaa03b7fa19
Explanation	The bindings between a VLAN-VXLAN mapping table and all 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 mapping table doesn't exist. · The binding doesn't exist.

Bind ports to VLAN-VXLAN mapping table

Keyword	CREATE_PORTBIND_OP
Message text	Bound ports to VLAN-VXLAN mapping table: $1
Variable fields	$1: Information about bindings between a VLAN-VXLAN mapping table and ports.
Example	Bound ports to VLAN-VXLAN mapping table: Mapping table ID: [fe17ff86-82c2-417f-bb2d-47500aad4113] Mapping table name: [1] Device port list: [ [ Device ID: 1a310715-255d-444d-a321-da98764c53ee Device name: 125 Port name: FortyGigE3/4/0/2 Port num: 0x30fa Port untagged VLAN ID: null ] ]
Explanation	A VLAN-VXLAN mapping table was bound to ports.
Possible failure causes	· Invalid license. · Invalid JSON format. · The service is disabled. · Configuration recovery is in progress. · The controller is not the active leader. · Invalid name. · The mapping table doesn't exist. · The physical access device doesn't exist. · The port is already bound to another mapping table. · The device type doesn't match. · Duplicate physical access device IDs. · Unknown internal server error. · Duplicated interfaces exist.

Update bindings between ports and VLAN-VXLAN mapping table

Keyword	UPDATE_PORTBIND_OP
Message text	Updated bindings between ports and QinQ-VXLAN mapping table: $1
Variable fields	$1: Information about bindings between a VLAN-VXLAN mapping table and ports.
Example	Updated bindings between ports and QinQ-VXLAN mapping table: Mapping table ID: [fe17ff86-82c2-417f-bb2d-47500aad4113] Mapping table name: [1] Device port list: [ [ Device ID: 1a310715-255d-444d-a321-da98764c53ee Device name: 125 Port name: FortyGigE3/4/0/2 Port num: 0x30fa Port untagged VLAN ID: null ] ]
Explanation	The bindings between a VLAN-VXLAN mapping table and ports 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. · Invalid name. · The mapping table doesn't exist. · The port is already bound to another mapping table. · The physical access device doesn't exist. · The device type doesn't match. · Duplicate physical access device IDs. · The binding between the mapping table and ports doesn't exist. · Unknown internal server error. · Duplicated interfaces exist.

Delete bindings between ports and VLAN-VXLAN mapping table

Keyword	DEL_PORTBIND_OP
Message text	Deleted bindings between ports and VLAN-VXLAN mapping table: $1
Variable fields	$1: VLAN-VXLAN mapping table ID.
Example	Deleted bindings between ports and VLAN-VXLAN mapping table: e866fcca-6df6-4c4d-8eb7-418ef487732a
Explanation	The bindings between a VLAN-VXLAN mapping table and all ports were deleted.
Possible failure causes	· Invalid license. · The service is disabled. · Configuration recovery is in progress. · The controller is not the active leader. · The mapping table doesn't exist. · The binding between the mapping table and ports doesn't exist.

Bind ports to QinQ-VXLAN mapping table

Keyword	BIND_QINQ-VXLAN_PORT_OP
Message text	Bound ports to QinQ-VXLAN mapping table: $1
Variable fields	$1: Information about bindings between a QinQ-VXLAN mapping table and ports.
Example	Bound ports to QinQ-VXLAN mapping table: Mapping table ID: [fe17ff86-82c2-417f-bb2d-47500aad4113] Mapping table name: [1] Device port list: [ [ Device ID: 1a310715-255d-444d-a321-da98764c53ee Device name: 125 Port name: FortyGigE3/4/0/2 Port num: 0x30fa Port untagged VLAN ID: null ] ]
Explanation	A QinQ-VXLAN mapping table was bound to ports.
Possible failure causes	· Invalid license. · Invalid JSON format. · The service is disabled. · Configuration recovery is in progress. · The controller is not the active leader. · Invalid name. · The mapping table doesn't exist. · The physical access device doesn't exist. · The port is already bound to another mapping table. · The device type doesn't match. · Duplicate physical access device IDs. · The port has been bound to another QinQ-VXLAN mapping table. · A device binding exists on the device to which the specified port belongs. · Unknown internal server error. · Duplicated interfaces exist.

Update bindings between ports and QinQ-VXLAN mapping table

Keyword	UPDATE_QINQ-VXLAN_PORTBIND_OP
Message text	Updated bindings between ports and QinQ-VXLAN mapping table: $1
Variable fields	$1: Information about bindings between a QinQ-VXLAN mapping table and ports.
Example	Updated bindings between ports and QinQ-VXLAN mapping table: Mapping table ID: [fe17ff86-82c2-417f-bb2d-47500aad4113] Mapping table name: [1] Device port list: [ [ Device ID: 1a310715-255d-444d-a321-da98764c53ee Device name: 125 Port name: FortyGigE3/4/0/2 Port num: 0x30fa Port untagged VLAN ID: null ] ]
Explanation	The bindings between a QinQ-VXLAN mapping table and ports 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. · Invalid name. · The mapping table doesn't exist. · The port is already bound to another mapping table. · The physical access device doesn't exist. · The device type doesn't match. · Duplicate physical access device IDs. · The port has been bound to another QinQ-VXLAN mapping table. · A device binding exists on the device to which the specified port belongs. · The binding between the mapping table and ports doesn't exist. · Unknown internal server error. · Duplicated interfaces exist.

Delete bindings between ports and QinQ-VXLAN mapping table

Keyword	DELETE_QINQ-VXLAN_PORTBIND_OP
Message text	Deleted bindings between ports and QinQ-VXLAN mapping table: $1
Variable fields	$1: QinQ-VXLAN mapping table ID.
Example	Deleted bindings between ports and QinQ-VXLAN mapping table: e866fcca-6df6-4c4d-8eb7-418ef487732a
Explanation	The bindings between a QinQ-VXLAN mapping table and all ports were deleted.
Possible failure causes	· Invalid license. · The service is disabled. · Configuration recovery is in progress. · The controller is not the active leader. · The mapping table doesn't exist. · The binding between the mapping table and ports 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:[8032909d-47a1-4715-90af-5153ffe39899] Name:[group] MAC:[3c:8c:40:4e:dd:46] Description:[A] Type:[GROUPCGSR] Members:[ ] VTEP IP:[[168.0.0.26]] Connect mode:[VLAN] Firewall for only external traffic:[false] Firewall for external traffic:[false] Firewall for internal traffic:[true] isBind IpPool:[true] isBind VlanRange:[true] Export gateway:[true] DC interconnecion:[false] Fabric ID:[9c1d2a72-22fb-4410-b39f-2bdd2db05279] bindIpPools:[ IpPoolName: carrier network IpPoolName: firewall IpPoolName: load balancing IpPoolName: vRouter interconnect IpPoolName: security internal network IpPoolName: virtual device management ] bindVlanRanges:[ VlanRangeName: vlan pool ] Control mode:[EVPN]
Explanation	A gateway group was created.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · 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. · Invalid IP address pool name. · Invalid VLAN pool name. · The device type and the gateway control mode do not match. · The gateway group's MAC address conflicts with the VM's MAC address. · The IP address pool does not exist. · The IP address pool has been bound to another gateway group. · The default IP address pool cannot be bound to gateway groups. · The VLAN pool does not exist. · The VLAN pool has been bound to another gateway group. · The default VLAN pool cannot be bound to gateway groups. · Gateway groups that use the default IP address pool cannot be bound to other IP address pools. · Gateway groups that use the default VLAN pool cannot be bound to other VLAN pools. · Do not set the MAC address to 3C:8C:40:4E:DD:47, 3C:8C:40:4E:DD:48, 3C:8C:40:4E:DD:49, 3C:8C:40:4E:DD:4A or 68:05:CA:21:D6:E5 for the gateway group. These MAC addresses are reserved for the controller. · The gateway group's MAC address conflicts with the NE’s default MAC address. · A gateway group can be bound to only one IP address pool of each type. · The gateway group is not bound to the specified type of IP address pool. · Gateway groups cannot be bound to security external IP address pools. · The network element is being deleted or being removed from the gateway group. · No fabric is specified for the device group. · The NE and the device group to which the NE belongs must be in the same fabric. · You must set the value of the export gateway field, the value of the DC interconnection field, or both values to true. · You must specify the export gateway, DC interconnection, or both. · Cannot specify a VTEP IP address in the VTEP IP address pool. · A border device group already exists with the specified name. · The campus egress VLAN pool and the security egress VLAN pool overlap. · The member devices in the border device group arenot configured with VTEP IP addresses. You cannot select intra-domain orinter-domain interconnect as the location.. · You cannot clear the Intra-Domain Interconnect option for the border device group. · You cannot clear the Inter-Domain Interconnect option for the border device group. · You can add only one campus-WAN interconnect device group on one fabric.

Update gateway group

Keyword	UPDATE_GWGROUP_OP
Message text	Updated gateway group: $1
Variable fields	$1: Gateway group information.
Example	Updated gateway group: ID:[8032909d-47a1-4715-90af-5153ffe39899] Name:[group] MAC:[3c:8c:40:4e:dd:46] Description:[A] Type:[GROUPCGSR] Members:[ ] VTEP IP:[[168.0.0.26]] Connect mode:[VLAN] Firewall for only external traffic:[false] Firewall for external traffic:[false] Firewall for internal traffic:[true] isBind IpPool:[true] isBind VlanRange:[true] Export gateway:[true] DC interconnection:[false] Fabric ID:[9c1d2a72-22fb-4410-b39f-2bdd2db05279] bindIpPools:[ IpPoolName: carrier network IpPoolName: firewall IpPoolName: load balancing IpPoolName: vRouter interconnect IpPoolName: security internal network IpPoolName: virtual device management ] bindVlanRanges:[ VlanRangeName: vlan pool ] Control mode:[EVPN]
Explanation	A gateway group was modified.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · Unknown internal server error. · Invalid description. · Invalid parameter. · Invalid IP address pool name. · Invalid VLAN pool name. · The gateway group is in use. · The gateway group doesn't exist. · The device type and the gateway control mode do not match. · The gateway group's MAC address conflicts with the VM's MAC address. · The IP address pool does not exist. · The IP address pool has been bound to another gateway group. · The default IP address pool cannot be bound to gateway groups. · The VLAN pool does not exist. · The VLAN pool has been bound to another gateway group. · The default VLAN pool cannot be bound to gateway groups. · Gateway groups that use the default IP address pool cannot be bound to other IP address pools. · Gateway groups that use the default VLAN pool cannot be bound to other VLAN pools. · Do not set the MAC address to 3C:8C:40:4E:DD:47, 3C:8C:40:4E:DD:48, 3C:8C:40:4E:DD:49, 3C:8C:40:4E:DD:4A or 68:05:CA:21:D6:E5 for the gateway group. These MAC addresses are reserved for the controller. · The gateway group's MAC address conflicts with the NE’s default MAC address. · A gateway group can be bound to only one IP address pool of each type. · The gateway group is not bound to the specified type of IP address pool. · Gateway groups cannot be bound to security external IP address pools. · The gateway group cannot be unbound from VLAN pools that are in use. · The gateway group cannot be unbound from IP address pools that are in use. · The network element is being deleted or being removed from the gateway group. · Cannot modify the work mode of a gateway group with the EVPN network type. · The export gateway cannot be edited. · The DC interconnection cannot be edited. · Cannot unbind the device group from the fabric because some member devices in the group have been bound to the fabric. · Before binding a device group to a fabric, unbind the group from its original fabric. · Cannot remove the device from the border device group, because the group has been used by a gateway member. · The campus egress VLAN pool and the security egress VLAN pool overlap. · You can add only one campus-WAN interconnect device group on one fabric.

Delete gateway group

Keyword	DELETE_GWGROUP_OP
Message text	Deleted gateway group: ID: $1 Name: $2
Variable fields	$1: Gateway group ID. $2: Gateway group name.
Example	Deleted gateway group: ID: [7777945d-befe-47fa-8a6b-edf10bea11e4] Name: [sss]
Explanation	A gateway group was deleted.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · Configuration recovery is in progress. · The gateway group doesn't exist. · The gateway group is in use.

Create IP address pool

Keyword	CREATE_IPPOOL_OP
Message text	Created IP address pool: $1
Variable fields	$1: IP address pool information.
Example	Created IP address pool: ID: [b12059c8-4f72-4efd-af06-8707d836f275] Name: [huha_lb] Type: [TENANT_SUPPORT_LB] CIDR: [19.19.19.0/24] Allocated: [false] Can be bound: [false] Address range list [ { Start IP: [19.19.19.1] End IP: [19.19.19.4] Status: [false] } { Start IP: [19.19.19.6] End IP: [19.19.19.10] Status: [false] } ]
Explanation	An IP address pool was created.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · Invalid JSON format. · Invalid name. · Invalid CIDR. · 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 must belong to the specified network. · The start IP address and end IP address must belong to the specified network. · The IP address range overlaps with another one. · The status field is read only. · The start IP address or end IP address cannot be a broadcast address or network address. · The gateway address cannot be a broadcast address or network address. · Unknown internal server error. · For each IP address pool type, only one default address pool is allowed. · The network address overlaps with a network address in another IP address pool. · Network addresses cannot be configured for this type of address pools. · Address ranges are required for this type of address pools. · The team can have only one vRouter interconnection IP pool and the pool must be configured as the default IP pool. · Only one address range can be configured for a management network address pool. · The next hop is required.

Update IP address pool

Keyword	MODIFY_IPPOOL_OP
Message text	Updated IP address pool: $1
Variable fields	$1: IP address pool information.
Example	Updated IP address pool: ID: [4272f686-1faf-4587-b7a2-2f68246666e2] Name: [1222] Type: [NGFW_MANAGE] CIDR: [10.1.1.0/24] Nexthop: [10.0.0.254] Allocated: [false] Can be bound: [false] Address range list [ { Start IP: [19.19.19.1] End IP: [19.19.19.4] Status: [false] } { Start IP: [19.19.19.6] End IP: [19.19.19.10] Status: [false] } ]
Explanation	An IP address pool was modified.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · 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. · The IP address range overlaps with another one. · The network address field is read only. · The status field is read only. · The start IP address and end IP address must belong to the specified network. · The start IP address or end IP address cannot be a broadcast address or network address. · Address ranges are required for this type of address pools. · Unknown internal server error. · The VTEP IP address pool has been used and cannot be expanded. · The management network address pool has been used by the deployment resource pool and cannot be modified. · Only one address range can be configured for a management network address pool. · Address ranges are required for this type of address pools.

Delete IP address pool

Keyword	DELETE_IPPOOL_OP
Message text	Deleted IP address pool: ID: $1 Name: $2
Variable fields	$1: IP address pool ID. $2: IP address pool name.
Example	Deleted IP address pool: ID: [a713e64d-1ad0-48c0-98a9-dc7b5c877fc6] Name: [22331]
Explanation	An IP address pool was deleted.
Possible failure causes	· Invalid license. · Invalid JSON format. · The service is disabled. · The controller is not the active leader. · Configuration recovery is in progress. · The IP address pool doesn't exist. · The IP address pool is already used. · Unknown internal server error. · Failed to delete the security external IP address pool. The pool has been bound to a VNF virtual gateway resource. · The address pool has been used by the deployment resource pool and cannot be deleted.

Create gateway group VLAN range

Keyword	CREATE_GWVLANRANGE_OP
Message text	Created gateway group VLAN range: $1
Variable fields	$1: VLAN pool 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] VLAN needBind: [false] VLAN networkType: [vlan]
Explanation	A VLAN pool was created.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · Invalid JSON format. · Invalid name. · The VLAN pool is already used. · The VLAN pool ID already exists. · The VLAN pool name already exists. · The VLAN pool overlaps with another one. · The VLAN ID is invalid or out of range. · The vRouter interconnection network VLAN pool already exists. · Configuration recovery is in progress. · Unknown internal server error. · Invalid network type.

Update gateway group VLAN range

Keyword	UPDATE_GWVLANRANGE_OP
Message text	Updated gateway group VLAN range: $1
Variable fields	$1: VLAN pool information.
Example	Updated gateway group VLAN range: VLAN range ID: [445dd33e-3b27-44a5-b7f1-c6fb0a859311] VLAN range name: [newRange] Start VLAN: [12] End VLAN: [4011] VLAN allocated: [false] VLAN needBind: [false]
Explanation	A VLAN pool was modified.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · Invalid JSON format. · The VLAN ID is invalid or out of range. · Invalid name. · The VLAN pool is already used. · The VLAN pool doesn't exist. · Unknown internal server error. · The VLAN pool overlaps with another VLAN pool bound to the same gateway group. · The new VLAN range of the vRouter interconnection network VLAN pool must include the original VLAN range of the pool. · The VLAN pool ranges corresponding to the user VLAN and the Layer 2 network domain cannot overlap.

Delete gateway group VLAN range

Keyword	DELETE_GWVLANRANGE_OP
Message text	Deleted gateway group VLAN range: $1
Variable fields	$1: VLAN pool ID.
Example	Deleted gateway group VLAN range: 8688051f-5095-4b27-93c1-89922ff9b0b6
Explanation	A VLAN pool was deleted.
Possible failure causes	· Invalid license. · Invalid JSON format. · The service is disabled. · The controller is not the active leader. · Configuration recovery is in progress. · The VLAN pool doesn't exist. · The VLAN pool is already used. · The VLAN pool is already used by device group. · vRouter interconnection network VLAN pools cannot be deleted. · Unknown internal server error. · Cannot delete the campus auth-free VLAN ranges.

Create VXLAN pool

Keyword	ACTION_CREATE_VXLANPOOL
Message text	Created VXLAN pool: $1
Variable fields	$1: VXLAN pool information.
Example	Created VXLAN pool: VXLAN pool ID:[8ca117d1-b2ea-4538-9464-6a924f7fdf89] VXLAN pool name:[B] Start VNI:[3] End VNI:[3] VXLAN pool allocated:[false]
Explanation	A VXLAN pool was created.
Possible failure causes	· Invalid license. · Invalid JSON format. · The service is disabled. · The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid name. · Invalid start VNI value. · Invalid end VNI value. · VNI value is out of range. · The name is required. · The range is required. · The start value is required. · The end value is required. · The VXLAN pool name already exists. · The VXLAN pool ID already exists. · The end VXLAN ID must be greater than or equal to the start VXLAN ID. · The VXLAN pool overlaps with another VXLAN pool. · The VXLAN range cannot contain existing segment IDs or mapping segment IDs.

Update VXLAN pool

Keyword	ACTION_UPDATE_VXLANPOOL
Message text	Updated VXLAN pool: $1
Variable fields	$1: VXLAN pool information.
Example	Updated VXLAN pool: VXLAN pool ID:[8ca117d1-b2ea-4538-9464-6a924f7fdf89] VXLAN pool name:[BA] Start VNI:[334] End VNI:[3344] VXLAN allocated:[false]
Explanation	A VXLAN pool was modified.
Possible failure causes	· Invalid license. · Invalid JSON format. · The service is disabled. · The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid name. · Invalid start VNI value. · Invalid end VNI value. · The name is required. · The range is required. · The start value is required. · The end value is required. · VNI value is out of range. · The VXLAN pool does not exist. · The VXLAN pool name already exists. · VXLAN pools in use cannot be modified or deleted. · The end VXLAN ID must be greater than or equal to the start VXLAN ID. · The VXLAN pool overlaps with another VXLAN pool. · The VXLAN range cannot contain existing segment IDs or mapping segment IDs.

Delete VXLAN pool

Keyword	ACTION_DELETE_VXLANPOOL
Message text	Deleted VXLAN pool: $1
Variable fields	$1: VXLAN pool ID.
Example	Deleted VXLAN pool: 8ca117d1-b2ea-4538-9464-6a924f7fdf89
Explanation	A VXLAN pool was deleted.
Possible failure causes	· Invalid license. · Invalid JSON format. · The service is disabled. · The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · The VXLAN pool does not exist. · VXLAN pools in use cannot be modified or deleted.

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: [5986bede-08f2-4d4e-bd01-9e7907272e5d] NE name: [l2vtep] NE type: [L2GW] VTEP IP: [[68.0.0.15]] VDS ID: [ffffffff-0000-0000-0000-000000000001] NETCONF username: [sdn] NETCONF password: [123456] Provider type: [PHY_DEVICE] NE capability: [L2GW] Vrf: [mgmt] Reserved tunnel ID: [256] Supporting autoconfiguration: [true] Supporting VTEP: [true] Service migration: [false] PreCfgVxlanService: [false] OpenflowPermitPort: [false] PreStatVxlanService: [false] openflowControllerPort: [null] openflowSslPolicyName: [null] Clear configuration: [false] Data synchronization: [DEFAULT] externalInfoList: [ ] isDeleting: [false] Role name: [leaf] Serial number: [210235A2C4H187000881] Fabric ID: [b07f126a-54bb-480a-ba4c-a98fe1153d14] Gateway: [false] Read community: [public] Write community: [private] Under deployment: [false] Loopback1 IP: ] NE status:[INACTIVE] Inactive reason:[DEVICE_INACTIVE_REASON_DEVICE_IS_NO_FINISH_AUTOMAIN_ON_LINE]
Explanation	A physical NE was created.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · 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. · The management IP address conflicts with the host IP. · Invalid BGP instance name. · The reserved VLAN ID conflicts with a VLAN ID of an VLAN-VXLAN mapping. · Invalid serial number. · The alias cannot exceed 63 characters. · The device MAC address already exists. · The device serial number already exists. · The DC interconnection IP address is required. · The DC interconnection IP address cannot be configured. · Invalid network entity ID. · The system IDs of different NEs in a fabric cannot be the same. · The fabric ID is required. · The software version is read only. · The device type field is read only. · Invalid device type. · The NETCONF username is required. · The NETCONF password is required. · The SNMP read community name is required. · The SNMP write community name is required. · No available VTEP IPs. · An NE can be added to a device group only after it is bound to a fabric. · The device model cannot be edited. · The fabric does not exist. · Cannot specify a VTEP IP address in the VTEP IP address pool. · The alias can contain up to 63 characters, and cannot be all-spaces.

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: [00dbdaab-8cdc-46cd-88e0-9a86e1269853] NE name: [deviceGate] Description: [A] NE type: [L3GW] VTEP IP: [[192.168.100.3]] NETCONF username: [sdn] NETCONF password: [******] Provider type: [PHY_DEVICE] NE capability: [L3GW] Vrf: [mgmt] Reserved tunnel ID: [256] Supporting autoconfiguration: [true] Supporting VTEP: [true] Service migration: [false] PreCfgVxlanService: [false] OpenflowPermitPort: [false] PreStatVxlanService: [false] openflowControllerPort: [null] openflowSslPolicyName: [null] Clear configuration: [false] Data synchronization: [DEFAULT] externalInfoList: [ ] isDeleting: [false] Role name: [spine] Serial number: [45039507705P06] Fabric ID: [889933a9-c49b-4e8c-b56d-037830062601] Gateway: [true] asNumber is: [0] Under deployment: [false] Loopback1 IP: ] NE status:[INACTIVE] Inactive reason:[DEVICE_NOT_IN_GROUP]
Explanation	A physical NE was modified.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · 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. · The network element is being deleted or being removed from the gateway group. · The reserved VLAN ID conflicts with a VLAN ID of an VLAN-VXLAN mapping. · The NE has been bound to a gateway group. It cannot be unbound from the fabric. · The DC interconnection IP address cannot be configured. · The fabric ID has been used. · The NE type specified in the fabric must be the same as the NE type of the device. · The role name cannot be edited because the NE has been bound to a fabric. · The gateway cannot be edited because the NE has been bound to a fabric. · The network entity ID cannot be edited. · Before binding a device group to a fabric, unbind the group from its original fabric. · An NE can be added to a device group only after it is bound to a fabric. · The device model cannot be edited. · The software version field is read only. · The device type field is read only. · The fabric does not exist. · Before binding a device to a fabric, unbind the device from its original fabric. · The alias can contain up to 63 characters, and cannot be all-spaces.

Delete physical NE

Keyword	DELETE_PHYNE_OP
Message text	Deleted physical NE: ID: $1 Name: $2 Management IP: $3
Variable fields	$1: ID of the physical NE. $2: Name of the physical NE. $3: Management IP of the physical NE.
Example	Deleted physical NE: ID: [f10dbcef-b96a-48ad-8613-47fc7fe9f4e8] Name: [125] Management IP: [97.0.1.12]
Explanation	A physical NE was deleted.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · Configuration recovery is in progress. · The NE doesn't exist. · The NE is migrating services. · The network element is being deleted or being removed from the gateway group. · Cannot delete the device, because it has been bound to a local service resource. · You cannot delete the gateway device. It has been specified for a Layer 2 network domain · You cannot delete the device, because it has been specified as a border device for a border gateway member.

Reboot physical NE

Keyword	REBOOT_PHYNE_OP
Message text	Rebooted physical NE: Name: $1 ID: $2
Variable fields	$1: Physical device name. $2: Physical device ID.
Example	Rebooted physical NE: ID: [f10dbcef-b96a-48ad-8613-47fc7fe9f4e8]
Explanation	A physical device was restarted.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · Configuration recovery is in progress. · The physical NE doesn't exist. · The physical NE is being deleted or being removed from the gateway group. · The device is inactive.

Batch add physical NEs

Keyword	BATCH_ADD_PHYNE_OP
Message text	Batch added physical NEs: Added NEs: $1 Ignored NEs: $2
Variable fields	$1: Number of added physical NEs. $2: Number of ignored physical NEs. A physical NE is ignored and not added to the controller if the information about the physical NE conflicts with that of an NE on the controller.
Example	Batch added physical NEs: Added NEs: 10 Ignored NEs: 5
Explanation	Multiple physical NEs were added in bulk.
Possible failure causes	· Information about the NE in row m of sheet n is invalid. · Information about the NE in row m of sheet n conflicts with that of an NE on the controller. · Failed to import the device data in row m of sheet n. The number of physical devices has exceeded the limit allowed by the overlay hardware entity license. · Failed to import the device data in row m of sheet n. The number of devices has exceeded the limit required by the node license.

Start scanning physical NE

Keyword	START_SCAN_PHYNE_OP
Message text	Started scanning physical NEs: $1
Variable fields	$1: Settings for auto physical NE discovery.
Example	Started scanning physical NEs: Start management IP: [192.168.125.0] End management IP: [192.168.125.10] NETCONF username: [admin] NETCONF password: [admin]
Explanation	Auto physical NE discovery was started.
Possible failure causes	The service is disabled.

Stop scanning physical NE

Keyword	STOP_SCAN_PHYNE_OP
Message text	Stopped scanning physical NEs
Variable fields	N/A
Example	Stopped scanning physical NEs
Explanation	Auto physical NE discovery was stopped.
Possible failure causes	The service is disabled.

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. · Configuration recovery is in progress. · The device doesn't exist. · The device is inactive. · The device is migrating services. · The network element is being deleted or being removed from the gateway group.

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. · Configuration recovery is in progress. · The device doesn't exist. · Only physical gateway devices support migration. · The device has already completed migration. · The network element is being deleted or being removed from the gateway group.

Start data synchronization on physical NE

Keyword	START_DATA_SYNCHRONIZATION_OP
Message text	Started data synchronization on physical NE: $1
Variable fields	$1: Physical gateway ID.
Example	Started data synchronization on physical NE: 28424135-36f5-4dde-ad2e-29580411de8d
Explanation	Data synchronization was started on a physical NE.
Possible failure causes	· Invalid license. · The service is disabled. · The device doesn't exist. · The device is inactive. · Configuration recovery is in progress. · The controller is not the active leader. · Underlay devices do not support this function. · The network element is being deleted or being removed from the gateway group. · The system is performing data synchronization or configuration auditing for the network element.

Start configuration auditing on physical NE

Keyword	START_PHYNE_CONFIG_AUDIT_OP
Message text	Started configuration auditing on physical NE $1
Variable fields	$1: Physical NE ID.
Example	Started configuration auditing on physical NE 28424135-36f5-4dde-ad2e-29580411de8d
Explanation	Configuration auditing was started on a physical NE.
Possible failure causes	· Invalid license. · The service is disabled. · The device doesn't exist. · The device is inactive. · Configuration recovery is in progress. · The controller is not the active leader. · Underlay devices do not support this function. · The network element is being deleted or being removed from the gateway group. · The system is performing data synchronization or configuration auditing for the network element.

Start data synchronization on virtual NE

Keyword	START_VIRTUAL_NE_DATA_SYNCHRONIZATION_OP
Message text	Started data synchronization on virtual NE $1
Variable fields	$1: Virtual NE ID.
Example	Started data synchronization on virtual NE 28424135-36f5-4dde-ad2e-29580411de8d
Explanation	Data synchronization was started on a virtual NE.
Possible failure causes	· Invalid license. · The service is disabled. · The device doesn't exist. · The device is inactive. · Configuration recovery is in progress. · The controller is not the active leader. · The system is performing data synchronization or configuration auditing for the network element.

Start configuration auditing on virtual NE

Keyword	START_VIRTUAL_NE_CONFIG_AUDIT_OP
Message text	Started configuration auditing on virtual NE $1
Variable fields	$1: Virtual NE ID.
Example	Started configuration auditing on virtual NE 28424135-36f5-4dde-ad2e-29580411de8d
Explanation	Configuration auditing was started on a virtual NE.
Possible failure causes	· Invalid license. · The service is disabled. · The device doesn't exist. · The device is inactive. · Configuration recovery is in progress. · The controller is not the active leader. · The system is performing data synchronization or configuration auditing for the network element.

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.

Configure default MAC address

Keyword	CONFIGURE_DEFAULT_MAC_ADDRESS_OP
Message text	Configured default MAC address: $1
Variable fields	$1: Default MAC address.
Example	Configured default MAC address: 6A:12:7C:5F:2D:2C
Explanation	The default MAC address was configured.
Possible failure causes	· Unknown internal server error. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The service is disabled. · Invalid default MAC address. · The default MAC address conflicts with the VM's MAC address. · The default MAC address conflicts with the gateway group's MAC address. · Do not set the MAC address to 3C:8C:40:4E:DD:47, 3C:8C:40:4E:DD:48, 3C:8C:40:4E:DD:49, or 3C:8C:40:4E:DD:4A for the NE default. These MAC addresses are reserved for the controller.

Delete default MAC address

Keyword	DELETE_DEFAULT_MAC_ADDRESS_OP
Message text	Deleted default MAC address: $1
Variable fields	$1: Default MAC address.
Example	Deleted default MAC address: A6:12:7B:5F:D2:2C
Explanation	The default MAC address was deleted.
Possible failure causes	· Unknown internal server error. · The controller is not the active leader. · Configuration recovery is in progress. · The default MAC address doesn't exist.

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. · 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: ID of the third-party NE.
Example	Deleted third party NE: 8032909d-47a1-4715-90af-5153ffe39899
Explanation	A third-party NE was deleted.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · Configuration recovery is in progress. · The third party NE doesn't exist. · Failed to delete the third party network element because it is used by a service chain. · The service chain service is disabled.

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. · 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. · 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 modified.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · 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. · The VTEP IP address pool has been used and cannot be expanded. · The address pool has been used by the deployment resource pool and cannot be deleted. · The management network address pool has been used by the deployment resource pool and cannot be expanded.

Delete address pool

Keyword	DELETE_ADDRPOOL_OP
Message text	Deleted address pool: $1
Variable fields	$1: Address pool ID.
Example	Deleted address pool: 0e447abc-9716-4171-902c-ecb8a090cebb
Explanation	A VTEP address pool was deleted.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · Configuration recovery is in progress. · The address pool doesn't exist. · The address pool is in use. · Unknown internal server error. · The address pool has been used by the deployment resource pool and cannot be deleted.

Add resource

Keyword	ADD_RESOURCE_OP
Message text	Added resource: $1
Variable fields	$1: Resource information.
Example	Added resource: Resource ID: [94f94495-d510-4872-b221-294098a6a247] Resource name: [VSR_6232412828] Tenant ID: [ffffffff-0000-0000-0000-000000000001] Tenant name: [default] Resource feature: [GW+GWSN] Resource family: [NFV] Resource type: [VSR] Supporting VTEP: [true] Supporting share: [false] Supporting HA: [true] NF list: [ { NF ID: [fb1671e4-496c-446a-8b4e-1ae834ba8546] NF name: [VSR_6463834061] NF management IP: [8.8.8.1] Data synchronization: [DEFAULT] } ] VNF template name: [test] Gateway member ID: 8032909d-47a1-4715-90af-5153ffe39861, Auto created: true
Explanation	A resource was added.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · 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 network function ID doesn't exist. · The management IP address is already used. · No network function list is specified for the physical resource. · The gateway group doesn't exist. · The VTEP 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. · The tenant service is disabled. · The NGFWM service is not started. · Server processing error. · No permission to add the resource. · The VNFM service is not loaded. · Before creating resources through VNFM3.0, delete all resources created through VNFM2.0. · Switch to VNFM2.0 and then create resources through VNFM2.0. · The management IP address for the virtual NE doesn't exist. · The management IP address conflicts with the host IP. · The tenant is not bound to a service gateway group resource. · The two tenants bound to different gateway groups can't share a service resource of the GATEWAY_SERVICE type. · The tenant has GATEWAY_SERVICE service resources. Please bind the tenant to a service gateway group that uses the default address pool and default VLAN pool. · A tenant bound to a gateway group using a non-default address pool or non-default VLAN pool cannot share GATEWAY_SERVICE service resources with a tenant not bound to any gateway resources. · The gateway member does not exist. · The resource parameters and gateway member parameters do not match. · The gateway to which the gateway member belongs does not exist. · The tenant of the gateway to which the gateway member belongs is different from the tenant of the resource. · The tenant does not support automatic service resource creation. · The gateway member has been bound to another resource. · A resource already exists with the specified name. · The number of resource sharers has reached the upper limit. · Failed to allocate resources, because the specified firewall management address pool does not have enough IP addresses.

Delete resource

Keyword	DELETE_RESOURCE_OP
Message text	Deleted resource: $1
Variable fields	$1: Resource ID.
Example	Deleted resource: 0e447abc-9716-4171-902c-ecb8a090cebb
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. · Unknown internal server error. · The VNFM is not configured. · The resource is already bound to the extranet. · The NGFWM service is not started. · Server processing error. · The configuration item does not exist. · Failed to delete the NGFW resource. Please manually delete the NGFW resource. · The virtual gateway resource still exists. · No permission to delete the resource. · The vRouter bound to the resource has been bound to the sharing external IP. · A vPort or APP cluster VIP on the vRouter bound to the resource has been bound to a floating IP with a protocol specified. · The service gateway group resource cannot be deleted because the address pool of the resource is being used by the GATEWAY_SERVICE service resource of the tenant.

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: [******] Version: [VNFM2.0]
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 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. · The VNFM version must be VNFM3.0 or VNFM2.0. · Before modifying the VNFM version, please delete all VNF resources.

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 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 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.

Router bound 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 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. · The vRouters using the public VRF can not be bound to the same service gateway group. · Unknown internal server error. · The resource group connected to the gateway member must map to the same private network attached to the gateway. · The gateway is not bound to the private network.

Create aggregation group member

Keyword	CREATE_AGGGROUP_MEMBER_OP
Message text	Created aggregation group member: $1
Variable fields	$1: Aggregation group member configuration information.
Example	Created aggregation group member: ID: [beea3a3d-685d-4e22-b64c-44b1a360b19c] Name: [ceshi] Description: [Description] Device ID: [fc8bbc44-76a6-4654-a0eb-1e6cdb642b95] Device name: [68] Group ID: [9f42cc59-80a6-4d52-98d7-847b4c360882] LACP short period enable: [False] Member port: [FortyGigE1/0/49] Group index: [7] Group mode: [1] Member port priority: [123] Selected status: [0] Unselected reason: [0]
Explanation	An aggregation group member was created.
Possible failure causes	· Invalid JSON format. · The service is disabled. · Configuration recovery is in progress. · The controller is not the active leader. · Invalid name. · Invalid description. · Unknown internal server error. · The aggregation group member already exists on the device. · The aggregation group member already exists. · The device ID doesn't exist. · The aggregation group doesn't exist on the device. · Invalid interface priority. · The device ID cannot be null. · No aggregation group ID is specified. · No name is specified.

Update aggregation group member

Keyword	UPDATE_AGGGROUP_MEMBER_OP
Message text	Updated aggregation group member: $1
Variable fields	$1: Aggregation group member configuration information.
Example	Updated aggregation group member: ID: [beea3a3d-685d-4e22-b64c-44b1a360b19c] Name: [ceshi] Description: [Change] Device ID: [fc8bbc44-76a6-4654-a0eb-1e6cdb642b95] Device name: [68] Group ID: [9f42cc59-80a6-4d52-98d7-847b4c360882] LACP short period enable: [False] Member port: [FortyGigE1/0/49] Group index: [7] Group mode: [1] Member port priority: [456] Selected status: [0] Unselected reason: [0]
Explanation	An aggregation group member was modified.
Possible failure causes	· Invalid JSON format. · The service is disabled. · Configuration recovery is in progress. · The controller is not the active leader. · Invalid name. · Invalid description. · Unknown internal server error. · The aggregation group member doesn't exist. · The aggregate interface and member interface are different types. · Invalid interface priority. · The aggregation group ID doesn't exist. · The aggregation group member is created through the bare metal module and cannot be modified.

Delete aggregation group member

Keyword	DELETE_AGGGROUP_MEMBER_OP
Message text	Deleted aggregation group member: $1
Variable fields	$1: Aggregation group member ID.
Example	Deleted aggregation group member: beea3a3d-685d-4e22-b64c-44b1a360b19c
Explanation	An aggregation group member was deleted.
Possible failure causes	· The service is disabled. · Configuration recovery is in progress. · The controller is not the active leader. · Unknown internal server error. · The aggregation group member doesn't exist. · The aggregation group member is created through the bare metal module and cannot be deleted.

Create aggregation group

Keyword	CREATE_AGGGROUP_OP
Message text	Created aggregation group: $1
Variable fields	$1: Aggregation group configuration information.
Example	Created aggregation group: ID: [9f42cc59-80a6-4d52-98d7-847b4c360882] Name: [test] Device ID: [fc8bbc44-76a6-4654-a0eb-1e6cdb642b95] Device name: [68] Group index: [7] Link mode: [Dynamic] LACP edge enable: [False] Load sharing mode type: [Default] VTEP enable: [False]
Explanation	An aggregation group was created.
Possible failure causes	· Invalid JSON format. · The service is disabled. · Configuration recovery is in progress. · The controller is not the active leader. · Invalid name. · Invalid description. · Unknown internal server error. · Duplicate aggregation group ID. · The device ID doesn't exist. · The aggregate interface ID is invalid. · The aggregate interface cannot be used as an access interface. · The aggregation group already exists on the device. · The aggregation group doesn't exist. · No available aggregation group indexes. · The global aggregation group settings are not configured. · The group index cannot be a reserved index. · The group index has been used by another group.

Update aggregation group

Keyword	UPDATE_AGGGROUP_OP
Message text	Updated aggregation group: $1
Variable fields	$1: Aggregation group configuration information.
Example	Updated aggregation group: ID: [ff9f1d56-507f-4190-bc52-70da3fe96dc5] Name: [test] Description: [B] Device ID: [fc8bbc44-76a6-4654-a0eb-1e6cdb642b95] Device name: [68] Group index: [7] Link mode: [Dynamic] LACP edge enable: [False] Load sharing mode type: [Default] VTEP enable: [True]
Explanation	An aggregation group was modified.
Possible failure causes	· Invalid JSON format. · The service is disabled. · Configuration recovery is in progress. · The controller is not the active leader. · Invalid description. · Unknown internal server error. · The aggregation group doesn't exist. · The aggregate group is created through the bare metal module and cannot be modified.

Delete aggregation group

Keyword	DELETE_AGGGROUP_OP
Message text	Deleted aggregation group: $1
Variable fields	$1: Aggregation group ID.
Example	Deleted aggregation group: ff9f1d56-507f-4190-bc52-70da3fe96dc5
Explanation	An aggregation group was deleted.
Possible failure causes	· The service is disabled. · Configuration recovery is in progress. · The controller is not the active leader. · Unknown internal server error. · The aggregation group doesn't exist. · The aggregate group is created through the bare metal module and cannot be deleted.

Create global aggregation group configuration

Keyword	CREATE_GLOBAL_AGGGROUP_CONFIG_OP
Message text	Created global aggregation group configuration: $1
Variable fields	$1: Global aggregation group configuration information.
Example	Created global aggregation group configuration: ID: [b57f56eb-bb3f-4908-bb68-1e1c4508a210] Name: [test] Description: [666] Device ID: [fc8bbc44-76a6-4654-a0eb-1e6cdb642b95] Device name: [68] System priority: [32768] Load sharing mode: [0] Reserved group indexes: [1-16384]
Explanation	Global aggregation group configuration was created.
Possible failure causes	· Invalid JSON format. · The service is disabled. · Configuration recovery is in progress. · The controller is not the active leader. · Invalid name. · Invalid description. · Unknown internal server error. · The global aggregation group configuration already exists. · Duplicate global aggregation group configuration. · Invalid reserved aggregation group indexes.

Update global aggregation group configuration

Keyword	UPDATE_GLOBAL_AGGGROUP_CONFIG_OP
Message text	Updated global aggregation group configuration: $1
Variable fields	$1: Global aggregation group configuration information.
Example	Updated global aggregation group configuration: ID: [b57f56eb-bb3f-4908-bb68-1e1c4508a210] Name: [test] Description: [66666666] Device ID: [fc8bbc44-76a6-4654-a0eb-1e6cdb642b95] Device name: [68] System priority: [32768] Load sharing mode: [0] Reserved group indexes: [1-16384]
Explanation	Global aggregation group configuration was modified.
Possible failure causes	· Invalid JSON format. · The service is disabled. · Configuration recovery is in progress. · The controller is not the active leader. · Invalid description. · Unknown internal server error. · The global aggregation group configuration doesn't exist.

Delete global aggregation group configuration

Keyword	DELETE_GLOBAL_AGGGROUP_CONFIG_OP
Message text	Deleted global aggregation group configuration: $1
Variable fields	$1: Global aggregation group configuration ID.
Example	Deleted global aggregation group configuration: 7c3bcda6-7bec-4318-bd7b-3e49fc96c54e
Explanation	Global aggregation group configuration was deleted.
Possible failure causes	· The service is disabled. · Configuration recovery is in progress. · The controller is not the active leader. · Unknown internal server error. · The global aggregation group configuration doesn't exist. · The device is configured with aggregation groups. Cannot delete the global aggregation group settings.

Delete NE VXLAN tunnels

Keyword	DELETE_NE_TUNNEL_OP
Message text	Deleted NE VXLAN tunnels: NE ID: $1 Tunnels: $2
Variable fields	$1: NE ID. $2: VXLAN tunnel list.
Example	Deleted NE VXLAN tunnels: NE ID: 28424135-36f5-4dde-ad2e-29580411de8d Tunnels: [ { Source IP: 98.0.57.16 Destination IP: 6.6.6.3 } ]
Explanation	The specified VXLAN tunnel on the specified NE was deleted, but the VXLAN tunnel on the device will not be deleted.
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. · Invalid JSON format. · Unknown internal server error.

Create connection limit rule

Keyword	CREATE_CONNECTIONLIMIT_OP
Message text	Created connection limit rule: $1
Variable fields	$1: Connection limit rule configuration information.
Example	Created connection limit rule: ID: [fecaab1f-2dc4-4cb0-b77a-2a4dbdfb9da8] Name: [connlimit] Description: [conn-vsr] Tenant ID: [ffffffff-0000-0000-0000-000000000001] AE type: [subnet] Per-service connection limit: [true] Per-source connection limit: [false] Per-destination connection limit: [true] Upper limit connection limit: [100] Lower limit connection limit: [100] AE list: [ { AE ID: [f98344e9-927e-4697-a6df-1170ed08eb4b] Limit direction: [ALL] } ]
Explanation	A connection limit rule was added.
Possible failure causes	· Invalid JSON format. · The service is disabled. · Configuration recovery is in progress. · The controller is not the active leader. · Unknown internal server error. · The lower connection limit cannot be larger than the upper connection limit. · Please select at least one of the per-service, per-source, and per-destination connection limit filtering methods. · A virtual subnet or vPort can be bound to only one connection limit rule. · The virtual subnet or vPort doesn't exist. · The virtual subnet or vPort doesn't belong to the tenant. · The limit direction must be IN, OUT, or ALL.

Update connection limit rule

Keyword	UPDATE_CONNECTIONLIMIT_OP
Message text	Updated connection limit rule: $1
Variable fields	$1: Connection limit rule configuration information.
Example	Updated connection limit rule: ID: [fecaab1f-2dc4-4cb0-b77a-2a4dbdfb9da8] Name: [connlimit] Description: [conn-vsr] Tenant ID: [ffffffff-0000-0000-0000-000000000001] AE type: [subnet] Per-service connection limit: [true] Per-source connection limit: [false] Per-destination connection limit: [true] Upper limit connection limit: [100] Lower limit connection limit: [100] AE list: [ { AE ID: [f98344e9-927e-4697-a6df-1170ed08eb4b] Limit direction: [ALL] } ]
Explanation	A connection limit rule was modified.
Possible failure causes	· Invalid JSON format. · The service is disabled. · Configuration recovery is in progress. · The controller is not the active leader. · Unknown internal server error. · The lower connection limit cannot be larger than the upper connection limit. · The virtual subnet or vPort doesn't exist. · The virtual subnet or vPort doesn't belong to the tenant. · The limit direction must be IN, OUT, or ALL. · Please select at least one of the per-service, per-source, and per-destination connection limit filtering methods. · A virtual subnet or vPort can be bound to only one connection limit rule. · The AE type field is read only.

Delete connection limit rule

Keyword	DELETE_CONNECTIONLIMIT_OP
Message text	Deleted connection limit rule: $1
Variable fields	$1: Connection limit rule ID.
Example	Deleted connection limit rule: fecaab1f-2dc4-4cb0-b77a-2a4dbdfb9da8
Explanation	A connection limit rule was deleted.
Possible failure causes	· The service is disabled. · Configuration recovery is in progress. · The controller is not the active leader. · Unknown internal server error. · The connection limit rule doesn't exist.

Create device configuration template

Keyword	CREATE_CONFIGURE_TEMPLATE_OP
Message text	Created device configuration template: $1
Variable fields	$1: Device configuration template information.
Example	Created device configuration template: ID: [6d84352b-4336-40a9-9f0e-b16b05cc98a8] Fabric ID: [457fce6f-a17c-4f06-ad29-ef08d2f7777c] File path:[null] Name:[bgp.template] Description:[ spine] Import flag:[false] Command line:[null] Role name:[spine] Username:[admin] Password:[123456] NTP server address:[12.2.2.240] Loopback1 IP range:[12.2.2.0/24] Control protocol template ID:[dd6aa058-88bb-4d41-9569-a5b16a941d72] Software ID:[null] Patch ID:[null] Aggregation mode:[null] IRF fabric:[false] Border IRF fabric:[null] Enable aggregation:[null] Master spine MAC:[78:9c:2f:5f:02:12] BGP RR MAC:[null] ECMP setting:[50] IS-IS name:[null] IS-IS password:[null] Spine BGP AS number:[500] Leaf BGP AS number:[400] BGP MD5 password:[123456] Border MAC:[null] EVPN control:[true]
Explanation	A device configuration template was created.
Possible failure causes	· Invalid JSON format. · Configuration recovery is in progress. · The controller is not the active leader. · Unknown internal server error. · Invalid template name. · A configuration template of a specific role has existed in the same fabric. · The fabric doesn't exist. · ECMP is not supported when the underlay protocol is OSPF. · ECMP must be configured when the underlay protocol is IS-IS or BGP. · The configuration template name already exists. · The BGP AS number in the configuration template is different from the BGP AS number in the fabric to which the configuration template belongs. · The BGP route reflector MAC can be configured only when EVPN is enabled. · Invalid BGP route reflector MAC. · Invalid role name. · The control protocol template doesn't exist. · The configuration template name for all devices in the same fabric must be the same. · The fabric ID is required. · The NTP server IP address is required. · The username and password are required. · The username and password must be the same for roles in the same fabric. · A border can be configured to operate in IRF mode only when the underlay protocol is OSPF or BGP and EVPN is enabled. · The BGP RR MAC is required when EVPN is enabled. · Link aggregation can be enabled for leaf devices only when the underlay protocol is IS-IS and EVPN is disabled. · Invalid link aggregation mode. · Link aggregation can be enabled for spine devices only when the underlay protocol is IS-IS and EVPN is enabled. · The IS-IS username and password are required when the underlay protocol is IS-IS. · The ISIS username and password can be configured only when the underlay protocol is IS-IS. · The leaf/spine AS number is required when the underlay protocol is BGP. · The Loopback1 IP range is required when the underlay protocol is BGP, and the role name is spine. · Invalid border MAC. · The border MAC is required when EVPN and optional parameter configuration are enabled. · The configuration template file already exists. · The EVPN control feature can be configured only when EVPN is disabled. · Invalid description. · A command line in the template can contain a maximum of 512 characters. Chinese characters are not supported. · Invalid IS-IS host name or neighbor authentication password. · Invalid BGP MD5 password. · Invalid ECMP settings. · In the configuration template, the BGP AS number, the BGP AS number for a spine device, and the BGP AS number for a leaf device must be different when the underlay protocol is BGP. · the leaf bgp as num or spine bgp as num can configure only when the protocol is BGP. · The BGP MD5 password can be configured only when you enable optional parameter configuration. · The border MAC address can be configured only when you enable both EVPN and optional parameter configuration. · The template file name must end with character string .template. · Invalid BGP AS number. · The fabric doesn't exist. · The BGP AS number cannot be modified because the fabric has network elements. · The NTP server address is required when the underlay protocol is OSPF or BGP. · The NTP server address cannot be configured when the underlay protocol is IS-IS and EVPN is disabled. · The template does not exist. · The template cannot be modified. · The master or spine MAC address is required. · The device configuration template name is required. · The software version or patch does not exist. · The role name is required. · The template file path is required. · The Loopback1 IP range is required when the underlay protocol is BGP, and the role name is spine. · The fabric ID of the configuration template and the fabric ID of the used control protocol template must be the same. · The fabric ID is required. · Invalid NTP server address. · Invalid master spine MAC address. · The IS-IS process ID is required when the underlay protocol is IS-IS. · The border MAC is required when EVPN is enabled. · Invalid command line. · Invalid is-is name or password. · A border can be configured to operate in IRF mode only when the underlay protocol is OSPF or BGP and EVPN is enabled. · The spine BGP AS number cannot be the same as the leaf BGP AS number. · The leaf BGP AS number and spine BGP AS number can be configured only when the protocol is BGP. · The Loopback1 IP range can be configured only when the underlay protocol is BGP, and the role name is spine. · The loopback1 ip range must require when the protocol is bgp and the role is spine. · The OSPF process ID is required when the underlay protocol is OSPF. · Invalid IS-IS process ID. · The OSPF process ID can be configured only when the underlay protocol is OSPF. · The IS-IS process ID can be configured only when the underlay protocol is IS-IS. · The OSPF process IDs in the configuration templates of all devices in a fabric must be the same. · The IS-IS process IDs in the configuration templates of all devices in a fabric must be the same. · The NTP server address is required when the underlay protocol is OSPF or BGP. · The NTP server address cannot be configured when the underlay protocol is IS-IS and EVPN is disabled. · The role name is required. · The template file path is required. · The master or spine MAC address is required. · The CIDR is required. · Invalid CIDR. · The Loopback1 IP range can be configured for the spine configuration template only when the underlay protocol is BGP. · Cannot configure the underlay IP range when the fabric allocation mode is controller allocation. · Cannot configure the Loopback1 IP range when the fabric allocation mode is controller allocation. · The underlay IP range is required when the fabric allocation mode is master spine allocation. · The Loopback1 IP range is required when the fabric allocation mode is master spine allocation. · If the local usernamein the device configuration template is the same as the NETCONF username in thedevice control protocol template, the password for the local user must also bethe same as the password for the NETCONF user.

Update device configuration template

Keyword	UPDATE_CONFIGURE_TEMPLATE_OP
Message text	Updated device configuration template: $1
Variable fields	$1: Device configuration template information.
Example	Updated device configuration template: ID:[6d84352b-4336-40a9-9f0e-b16b05cc98a8] Fabric ID:[457fce6f-a17c-4f06-ad29-ef08d2f7777c] File path:[null] Name:[bgp.template] Description:[device template spine] Import flag:[false] Command line:[null] Role name:[spine] Username:[admin] Password:[123456] NTP server address:[12.2.2.240] Loopback1 IP range:[12.2.2.0/24] Control protocol template ID:[dd6aa058-88bb-4d41-9569-a5b16a941d72] Software ID:[null] Patch ID:[null] Aggregation mode:[null] IRF fabric:[false] Border IRF fabric:[null] Enable aggregation:[null] Master spine MAC:[78:9c:2f:5f:02:12] BGP RR MAC:[null] ECMP setting:[50] IS-IS name:[null] IS-IS password:[null] Spine BGP AS number:[500] Leaf BGP AS number:[400] BGP MD5 password:[123456] Border MAC:[null] EVPN control:[true]
Explanation	A device configuration template was modified.
Possible failure causes	· Invalid JSON format. · Configuration recovery is in progress. · The controller is not the active leader. · Unknown internal server error. · The fabric doesn't exist. · The control protocol template doesn't exist. · Invalid description. · The NTP server IP address is required. · The username and password are required. · The username and password must be the same for roles in the same fabric. · A border can be configured to operate in IRF mode only when the underlay protocol is OSPF or BGP and EVPN is enabled. · The BGP RR MAC is required when EVPN is enabled. · Link aggregation can be enabled for leaf devices only when the underlay protocol is IS-IS and EVPN is disabled. · Invalid link aggregation mode. · Link aggregation can be enabled for spine devices only when the underlay protocol is IS-IS and EVPN is enabled. · The IS-IS username and password are required when the underlay protocol is IS-IS. · The ISIS username and password can be configured only when the underlay protocol is IS-IS. · The leaf/spine AS number is required when the underlay protocol is BGP. · The Loopback1 IP range is required when the underlay protocol is BGP, and the role name is spine. · The Loopback1 IP range can be configured only when the underlay protocol is BGP, and the role name is spine. · The configuration template file already exists. · The EVPN control feature can be configured only when EVPN is disabled. · Invalid description. · Invalid IS-IS host name or neighbor authentication password. · Invalid BGP MD5 password. · Invalid ECMP settings. · In the configuration template, the BGP AS number, the BGP AS number for a spine device, and the BGP AS number for a leaf device must be different when the underlay protocol is BGP. · the leaf bgp as num or spine bgp as num can configure only when the protocol is BGP. · The template file name must end with character string .template. · Invalid BGP AS number. · The BGP AS number cannot be modified because the fabric has network elements. · The NTP server address is required when the underlay protocol is OSPF or BGP. · The NTP server address cannot be configured when the underlay protocol is IS-IS and EVPN is disabled. · The template does not exist. · The master or spine MAC address is required. · The template name is required. · The software version or patch does not exist. · The role name is required. · The template file path is required. · The request json include read only param. · ECMP is not supported when the underlay protocol is OSPF. · ECMP must be configured when the underlay protocol is IS-IS or BGP. · The BGP route reflector MAC can be configured only when EVPN is enabled. · Invalid BGP route reflector MAC. · The fabric ID of the configuration template and the fabric ID of the used control protocol template must be the same. · Invalid NTP server address. · Invalid master spine MAC address. · Invalid border MAC. · The border MAC is required when EVPN is enabled. · Invalid parameter. · Invalid command line. · The border irf stacking can not be configured when the protocol is ospf or bgp and evpn is disabled. · The spine BGP AS number cannot be the same as the leaf BGP AS number. · The leaf BGP AS number and spine BGP AS number can be configured only when the protocol is BGP. · The Loopback1 IP range can be configured only when the underlay protocol is BGP, and the role name is spine. · The BGP AS number cannot be edited when the fabric has NEs. · The NTP server address is required when the underlay protocol is OSPF or BGP. · The NTP server address cannot be configured when the underlay protocol is IS-IS and EVPN is disabled. · The configureTemplate doesn't exist. · The import configure template can not modify. · The CIDR is required. · Invalid CIDR. · If the local usernamein the device configuration template is the same as the NETCONF username in thedevice control protocol template, the password for the local user must also bethe same as the password for the NETCONF user.

Delete device configuration template

Keyword	DELETE_CONFIGURE_TEMPLATE_OP
Message text	Deleted device configuration template id: $1. name: $2
Variable fields	$1: Device configuration template ID. $2: Device configuration template name.
Example	Deleted device configuration template id:[1c3cb5d0-d300-401d-b02a-9702004b0dd2] name:[111222.template]
Explanation	A device configuration template was deleted.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · Unknown internal server error. · The device configuration template doesn't exist. · The asset list doesn't exist.

Create control protocol template

Keyword	CREATE_CONTROL_PROTOCOL_TEMPLATE_OP
Message text	Created control protocol template: $1
Variable fields	$1: Control protocol template information.
Example	Created control protocol template: ID: [d23575f4-aa11-4683-855a-68d9edb95702] Name:[sdq] Fabric ID:[457fce6f-a17c-4f06-ad29-ef08d2f7777c] NETCONF settings:[ Username: admin Password: **** ] SNMP settings:[ Read community: public Write community: private ] FTP settings:[ Username: sdn Password: **** Timeout: 10 ]
Explanation	A control protocol template was created.
Possible failure causes	· Invalid JSON format. · The service is disabled. · Configuration recovery is in progress. · The controller is not the active leader. · Unknown internal server error. · The control protocol template name already exists. · The control protocol template name is required. · The NETCONF configuration is required. · The SNMP configuration is required. · The NETCONF username cannot exceed 55 characters, and cannot be all-spaces. · The NETCONF password cannot exceed 63 characters, and cannot be all-spaces. Chinese characters are not supported. · The SNMP read community name can contain up to 32 characters, and cannot be all-spaces. Chinese characters are not supported. · The SNMP write community name can contain up to 32 characters, and cannot be all-spaces. Chinese characters are not supported. · The SNMP read community is required. · The control protocol template with the UUID already exists. · Invalid control protocol template name. · The control protocol template with the UUID already exists. · The fabric ID is required.

Update control protocol template

Keyword	UPDATE_CONTROL_PROTOCOL_TEMPLATE_OP
Message text	Updated control protocol template: $1
Variable fields	$1: Control protocol template information.
Example	Updated control protocol template: ID: [d23575f4-aa11-4683-855a-68d9edb95702] Name:[sdq] Fabric ID:[457fce6f-a17c-4f06-ad29-ef08d2f7777c] NETCONF settings:[ Username: admin Password: **** ] SNMP settings:[ Read community: public Write community: private ] FTP settings:[ Username: sdn Password: **** Timeout: 1 ]
Explanation	A control protocol template was modified.
Possible failure causes	· Invalid JSON format. · The service is disabled. · Configuration recovery is in progress. · The controller is not the active leader. · Unknown internal server error. · The NETCONF username cannot exceed 55 characters, and cannot be all-spaces. · The NETCONF password cannot exceed 63 characters, and cannot be all-spaces. Chinese characters are not supported. · The SNMP read community name can contain up to 32 characters, and cannot be all-spaces. Chinese characters are not supported. · The SNMP write community name can contain up to 32 characters, and cannot be all-spaces. Chinese characters are not supported. · The SNMP read community is required. · The control protocol template name cannot be modified. · The fabric ID cannot be modified. · The control protocol template name cannot be modified. · The control protocol template doesn't exist. · If the NETCONFusername in the device control protocol template is the same as the localusername in the device configuration template, the password for the NETCONFuser must also be the same as the password for the local user.

Delete control protocol template

Keyword	DELETE_CONTROL_PROTOCOL_TEMPLATE_OP
Message text	Deleted control protocol template id: $1. name: $2
Variable fields	$1: Control protocol template ID. $2: Control protocol template name.
Example	Deleted control protocol template id:[ebd054f3-575e-4d30-ba4d-70160d82630c] name:[sss]
Explanation	A control protocol template was deleted.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · Unknown internal server error. · The service is disabled. · The default control protocol template cannot be deleted. · The control protocol template is in use. · The control protocol template doesn't exist.

Create deploy resource pool

Keyword	CREATE_DEPLOY_RESOURCEPOOL_OP
Message text	Created deployment resource pool: $1.
Variable fields	$1: Deployment resource pool information.
Example	Created deployment resource pool: [ ID: [5268d9a5-4403-4849-ad88-37d67692b6f9] Type: [out-of-band] Fabric ID: [c10d5b21-66d3-44c7-b482-095eb46c7aa2] DHCP server settings: [[ ID: [71299cd8-f90f-4599-8643-0e33cc284c0c] ]] VTEP IP pool list:[ VTEP IP pool settings :[ ID: [7ac5b035-d310-434b-90a2-a14cfe6acbb1] ] ] Management IP pool list:[ Management IP pool settings :[ ID: [a31cc0a9-0398-4ba1-9d68-0c6f88c92b1a] ] ] ]
Explanation	A deployment resource pool was created.
Possible failure causes	· Invalid JSON format. · Configuration recovery is in progress. · The controller is not the active leader. · Unknown internal server error. · The management mode is required. · Invalid management mode. · The DHCP server is required. · The DHCP server doesn't exist. · The management network is required. · The management address pool doesn't exist. · The management address pool is used by another fabric. · The VTEP IP address pool is required. · The VTEP IP address pool doesn't exist. · The VTEP IP address pool has been used. · The deployment resource pool already exists. · Invalid management network type. · Invalid VTEP IP type. · The fabric ID is required. · The fabric does not exist. · The fabric has been bound to another resource pool. · The server network list contains invalid networks. · The VLAN1 address pool is invalid. · The VLAN4094 address pool is invalid. · The specified VLAN pool does not exist. · The VLAN1 address pool requires a management network. · The specified VLAN pool has been bound to another fabric. · The VLAN4094 address pool requires a management network. · The server network list contains invalid networks. · Cannot configure a VTEP IP address pool when the fabric allocation mode is master spine allocation. · Cannot configure an underlay address pool when the fabric allocation mode is master spine allocation. · The system does not support Microsoft DHCP servers for automatic management of devices.

Update deploy resource pool

Keyword	UPDATE_DEPLOY_RESOURCEPOOL_OP
Message text	Updated deployment resource pool: $1.
Variable fields	$1: Deployment resource pool information.
Example	Updated deployment resource pool:[ ID: [cc06ca44-5b72-49c2-af36-5834970b8ab4] DHCP server settings: [[ ID: [c9d00027-d872-4f4c-bc28-43a582fc2680] ]] Management IP pool list:[ Management IP pool settings:[ ID: [ff57f6fb-ca53-4871-99cb-6027ea83e311] ] ] ]
Explanation	A deployment resource pool was modified.
Possible failure causes	· Invalid JSON format. · Configuration recovery is in progress. · The controller is not the active leader. · Unknown internal server error. · The management mode cannot be modified. · The IP address of the DHCP server cannot be modified. · The name of the DHCP server cannot be modified. · The fabric ID cannot be modified. · Subnets of the management network cannot be modified. · The gateway address of the management network cannot be modified. · Subnet addresses specified in the VTEP address pool cannot be modified. · The VTEP IP address pool cannot be modified. · The DHCP server doesn't exist. · The VTEP IP address pool doesn't exist. · The management address pool is used by another fabric. · The deployment resource pool doesn't exist. · Invalid management network type. · The fabric ID is required. · The server network list contains invalid networks. · The VLAN1 address pool is invalid. · The VLAN4094 address pool is invalid. · The specified VLAN pool does not exist. · The specified VLAN pool has been bound to another fabric. · The subnet bound to the VLAN pool cannot be modified. · The server network list contains invalid networks. · The system does not support Microsoft DHCP servers for automatic management of devices.

Delete deploy resource pool

Keyword	DELETE_DEPLOY_RESSOURCEPOOL_OP
Message text	Deleted deployment resource pool Id: $1. fabricName: $2
Variable fields	$1: Deployment resource pool ID. $2: Name of the fabric to which the deployment resource pool belongs.
Example	Deleted deployment resource pool id:[08a8e6b9-5b29-4bb0-a338-9fb4029e7b37] fabricName:[sss]
Explanation	A deployment resource pool was deleted.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · The deployment resource pool doesn't exist. · Cannot delete a VTEP IP address pool in use.

Create auto detected

Keyword	CREATE_AUTO_DISCOVERY_OP
Message text	Created auto discovery task: $1
Variable fields	$1: Auto discovery task information.
Example	Created auto discovery task: Username:[admin] Name:[null] Start IP:[98.0.19.92] End IP:[98.0.19.92] NETCONF username:[sdn] NETCONF password:[123456] Read community:[null] Write community:[null]
Explanation	An auto discovery task was created.
Possible failure causes	· Invalid JSON format. · Configuration recovery is in progress. · The controller is not the active leader. · Unknown internal server error. · The number of IP addresses must be in range of 1 to 1000. · The start IP address is required. · The end IP address is required. · NETCONF and SNMP cannot be both empty. · The SNMP read and write communities must be both configured or both empty. · The NETCONF username and password must be both configured or both empty. · The start IP address must be lower than the end IP address. · Invalid IP address. · The SNMP read community name is required. · The SNMP write community name is required. · The NETCONF username is required. · The NETCONF password is required. · The username is required. · Invalid username. · The NETCONF username cannot exceed 55 characters. · The NETCONF password cannot exceed 63 characters. Chinese characters are not supported. · The SNMP read community name can contain up to 32 characters. Chinese characters are not supported. · The SNMP write community name can contain up to 32 characters. Chinese characters are not supported.

Stop auto detected

Keyword	STOP_AUTO_DISCOVERY_OP
Message text	Stopped auto discovery task: $1.
Variable fields	$1: Whether the auto discovery task is stopped.
Example	Stopped auto discovery task: true.
Explanation	An auto discovery task was stopped.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · Unknown internal server error. · The auto-detection task has stopped. · The auto-detection task doesn't exist. · Invalid username.

Delete auto detected

Keyword	DELETE_AUTO_DISCOVERY_OP
Message text	Deleted auto discovery task $1.
Variable fields	$1: Username of the auto discovery task.
Example	Deleted auto discovery task admin.
Explanation	An auto discovery task was deleted.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · Unknown internal server error. · The auto-detection task is not completed and cannot be deleted. · The auto-detection task doesn't exist. · Invalid username.

Update global setting

Keyword	UPDATE_GLOBAL_SETTING_OP
Message text	Updated global setting: $1
Variable fields	$1: Whether scheduled backup for startup configuration files is enabled globally.
Example	Updated global setting: GlobalSettingConfig: [autoBackup=false, staticAccess=true, radarDetection=false, tftpServerAddress=null, frequency=0, week=0, date=0, time=00:00, maxCfgNum=30, selectCityName=null, firstSet=null acOnDemand=false
Explanation	The state of scheduled backup for startup configuration files was modified.
Possible failure causes	· Invalid JSON format. · Configuration recovery is in progress. · The controller is not the active leader. · Unknown internal server error. · You cannot disable static access, because a static access service has been configured. · You cannot enable static access, because no available VLANs exist.

Create manual backup

Keyword	CREATE_MANUAL_BACKUP_OP
Message text	Created manual backup:$1
Variable fields	$1: UUID of the device that was backed up.
Example	Create Manual Backup: deviceIdList:[76f15eab-b5db-4184-b92f-3b64427b0387]
Explanation	A device was backed up.
Possible failure causes	· Invalid JSON format. · Configuration recovery is in progress. · The controller is not the active leader. · Unknown internal server error. · The TFTP service and the Syslog service are not enabled. · The device is restoring configuration.

Recover configuration

Keyword	CREATE_MANUAL_CONFIG_ROLLBACK_OP
Message text	Recovered configuration: Device name: $1 Device ID: “$2”, Backup file name: “$3”.
Variable fields	$1: Device name. $2: Device ID. $3: Configuration file name.
Example	Create manual configuration rollback: device name: device01 device id: [ee0d4675-31ee-4e7b-9fa3-c7db6c4e232b] backup file name: [162.162.163.4_manual_20200220170629_startup.cfg]
Explanation	A device was restored.
Possible failure causes	· Invalid JSON format. · Configuration recovery is in progress. · The controller is not the active leader. · Unknown internal server error. · TFTP is not enabled. · The physical NE doesn't exist. · No device specified for configuration recovery. · The specified backup configuration file doesn't exist. · The device is backing up configuration. · The device is restoring configuration. · The device is inactive.

Create DHCP server

Keyword	CREATE_DHCP_SERVER_OP
Message text	Created DHCP server $1/$2.
Variable fields	$1: DHCP server name. $2: DHCP server IP.
Example	Created DHCP server Vsr-26.72/98.0.26.72.
Explanation	A DHCP server was created.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · The DHCP server name is required. · The DHCP server name cannot exceed 255 characters. · The DHCP server IP is required. · Invalid IP address. · The DHCP server NETCONF username is required. · The DHCP server NETCONF name cannot exceed 55 characters. · The DHCP server NETCONF password is required. · The DHCP server NETCONF password cannot exceed 63 characters. · The DHCP server already exists. · The DHCP server name is already used. · The DHCP server IP is already used. · The request is invalid. · Unknown error. · The DHCP server type is invalid. · The DHCP server status field is read only.

Update DHCP server

Keyword	UPDATE_DHCP_SERVER_OP
Message text	Updated DHCP server $1/$2.
Variable fields	$1: DHCP server name. $2: DHCP server IP.
Example	Updated DHCP server Vsr-26.72/98.0.26.72.
Explanation	A DHCP server was modified.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · The request is invalid. · Unknown error. · The specified resource doesn't exist. · The DHCP server status field is read only. · The DHCP server IP field is read only. · The DHCP server name field is read only. · The DHCP server type field cannot be edited. · The DHCP server NETCONF username is required. · The DHCP server NETCONF name cannot exceed 55 characters. · The DHCP server NETCONF password is required. · The DHCP server NETCONF password cannot exceed 63 characters.

Delete DHCP server

Keyword	DELETE_DHCP_SERVER_OP
Message text	Deleted DHCP server $1/$2.
Variable fields	$1: DHCP server name. $2: DHCP server IP.
Example	Deleted DHCP server Vsr-26.72/98.0.26.72.
Explanation	A DHCP server was deleted.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · Can't delete the DHCP server. The DHCP server has address pools. · Unknown error. · The specified resource doesn't exist.

Upload software

Keyword	UPLOAD_SOFTWARE_OP
Message text	Uploaded software package: $1
Variable fields	$1: Software/patch information.
Example	Uploaded software package: Software ID: [6b5f0ea1-590f-421d-9675-c3bbe9a39c0b] Software FTP path: [ftp://sdn:123456@98.0.26.1/6800.ipe] Software name: [6800.ipe] Software size: [135473152] Software version: [R2612] Software description: [s6800] Software type: [ipe] Software release date: [2018-08-17] Software import time: [2018-10-30 07:59:04] Device: [S6800] Device version: [Release 2612] Software platform version: [7.1.070 ] Software state: [ready] ]
Explanation	A software/patch was uploaded.
Possible failure causes	· Invalid JSON format. · The service is disabled. · Configuration recovery is in progress. · The controller is not the active leader. · Unknown internal server error. · The software name already exists. · The software already exists. · Invalid FTP path. · Invalid release date. · Invalid type of software. · Invalid software name. · Length of file name must be less than 63. · Unknown error code. · The FTP path is required. · The software name is required. · The software size field is read only. · The import_time attribute is read only. · The available devices field is read only. · The version field is read only. · The software type is requested.

Update software

Keyword	UPDATE_SOFTWARE_OP
Message text	Updated software package: $1
Variable fields	$1: Software/patch information.
Example	Updated software package: Software ID: [6b5f0ea1-590f-421d-9675-c3bbe9a39c0b] Software FTP path: [ftp://sdn:123456@98.0.26.1/6800.ipe] Software name: [6800.ipe] Software size: [0] Software version: [null] Software description: [s6800] Software type: [ipe] Software release date: [2018-08-17] Software import time: [2018-10-30 07:59:04] Device: [null] Device version: [null] Software platform version: [null] Software state: [ftp failed] ]
Explanation	Software/patch information was modified.
Possible failure causes	· Invalid JSON format. · The service is disabled. · Configuration recovery is in progress. · The controller is not the active leader. · Unknown internal server error. · The applicable devices are read only and cannot be modified. · The software does not exist. · The software type cannot be modified. · Invalid release date. · Unknown error code. · The software size field is read only. · The available devices field is read only. · The import time field is read only. · The version field is read only. · The software is being uploaded, cannot operate it. · The software is being upgraded, cannot operate it.

Delete software

Keyword	DELETE_SOFTWARE_OP
Message text	Deleted software package $1.
Variable fields	$1: Software/patch ID.
Example	Deleted software package 52db1e10-e09c-45c5-b7df-08bed8fbc474.
Explanation	Software/patch was deleted.
Possible failure causes	· The service is disabled. · Configuration recovery is in progress. · The controller is not the active leader. · Unknown internal server error. · Cannot delete the software. The software is being used. · The software does not exist. · Failed to delete the software. · Unknown error code. · The software is being uploaded, cannot operate it. · The software is being upgraded, cannot operate it.

Upgrade software

Keyword	CONFIGURE_SOFTWARE_UPGRADE
Message text	Upgraded software package: $1
Variable fields	$1: Software/patch information.
Example	Upgraded software package: Software ID: [cc4af032-5e4b-430d-9be1-5228717b48f7] Device information: [ Device ID: [2b48fee5-c261-4721-a740-53a073264e64] Software path: [flash:/] Space check flag: [true] Restart flag: [true]]
Explanation	Software/patch was upgraded.
Possible failure causes	· Invalid JSON format. · The service is disabled. · Configuration recovery is in progress. · The controller is not the active leader. · Unknown internal server error. · Invalid boot path. · The software does not exist. · The device is required. · The device is not active. · Unknown error code. · The software ID is required. · The device ID is required. · The software storage path is required. · Invalid boot path. · The device name is read only. · The software is being uploaded, cannot operate it.

Replace physical NE

Keyword	REPLACE_PHYNE_OP
Message text	Replaced physical NE: $1
Variable fields	$1: Device information.
Example	Replaced physical NE: NE ID: [5986bede-08f2-4d4e-bd01-9e7907272e5d] NE name: [l2vtep] NE type: [L2GW] VTEP IP: [[68.0.0.15]] VDS ID: [ffffffff-0000-0000-0000-000000000001] NETCONF username: [sdn] NETCONF password: [123456] Provider type: [PHY_DEVICE] NE capability: [L2GW] VRF: [mgmt] Reserved tunnel ID: [256] Supporting auto configuration: [true] Supporting VTEP: [true] Service migration: [false] PreCfgVxlanService: [false] OpenflowPermitPort: [false] PreStatVxlanService: [false] OpenFlow controller port: [null] OpenFlow SSL policy name: [null] Clear configuration: [false] Data synchronization: [DEFAULT] externalInfoList: [ ] Being deleted: [false] Role name: [leaf] Serial number: [210235A2C4H187000881] Fabric ID: [b07f126a-54bb-480a-ba4c-a98fe1153d14] Gateway: [false] Read community: [public] Write community: [private] Under deployment: [false] ] NE state:[INACTIVE] Inactive reason:[DEVICE_INACTIVE_REASON_DEVICE_IS_NO_FINISH_AUTOMAIN_ON_LINE]
Explanation	A failed device was replaced. Configuration of the failed device was migrated to the replacement device.
Possible failure causes	· Invalid license. · Invalid JSON format. · The service is disabled. · Configuration recovery is in progress. · The controller is not the active leader. · Unknown internal server error. · The replacement device is no activate. · The device is not bound to the fabric. · The replacement device is not bound to the fabric. · The faulty device and the replacement device must belong to the same fabric. · The device and replace device role are not same. · The backup start configuration file for the faulty device does not exist. · No configuration template is configured for the fabric to which the replacement device is bound. · FTP is not configured for the control protocol template associated with the replacement device. · A faulty underlay device cannot be replaced. · The replacement device type cannot be Underlay.

Create tenant-gateway binding relationship

Keyword	CREATE_TENANT_BIND_GATEWAY_OP
Message text	Created tenant-gateway binding relationship: $1
Variable fields	$1: Tenant-gateway binding relationship information.
Example	Created tenant-gateway binding relationship: ID: [ade5d887-818d-4555-a336-7f72a547fb1a] Tenant: [ffffffff-0000-0000-0000-000000000001] Default gateway: [fc8e40f9-d609-4ac6-ac0d-4f61875b86aa] Gateway list: [fc8e40f9-d609-4ac6-ac0d-4f61875b86aa].
Explanation	A tenant-gateway binding relationship 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. · Unknown internal server error. · The tenant-gateway binding relationship already exists. · The tenant does not exist. · The gateway list cannot contain duplicated gateways. · The tenant has been used by another tenant-gateway binding relationship. · Cannot specify nonexistent gateways. · Only gateways in the gateway list can be specified as the default gateway.

Update tenant-gateway binding relationship

Keyword	UPDATE_TENANT_BIND_GATEWAY_OP
Message text	Updated tenant-gateway binding relationship: $1
Variable fields	$1: Tenant-gateway binding relationship information.
Example	Updated tenant-gateway binding relationship: ID:[ade5d887-818d-4555-a336-7f72a547fb1a] Tenant:[ffffffff-0000-0000-0000-000000000001] Default gateway:[fc8e40f9-d609-4ac6-ac0d-4f61875b86aa] Gateway list:[fc8e40f9-d609-4ac6-ac0d-4f61875b86aa]
Explanation	A tenant-gateway binding relationship 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. · Unknown internal server error. · The tenant-gateway binding relationship does not exist. · The tenant-gateway binding relationship already exists. · The tenant has been used by another tenant-gateway binding relationship. · The gateway list cannot contain duplicated gateways. · Cannot specify nonexistent gateways. · The default gateway has been bound to a resource and cannot be modified. · Invalid parameter. · Only gateways in the gateway list can be specified as the default gateway.

Delete tenant-gateway binding relationship

Keyword	DELETE_TENANT_BIND_GATEWAY_OP
Message text	Deleted tenant-gateway binding relationship: $1
Variable fields	$1: Tenant-gateway binding relationship UUID.
Example	Deleted tenant-gateway binding relationship: 218b5f2f-e435-4365-a1ab-0eaa03b7fa19
Explanation	A tenant-gateway binding relationship 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. · Unknown internal server error. · The tenant-gateway binding relationship does not exist. · The default gateway has been bound to a resource and cannot be modified. · Invalid parameter.

Create gateway

Keyword	CREATE_GATEWAY_OP
Message text	Created gateway : $1
Variable fields	$1: Gateway information.
Example	Created gateway : ID: [741f1414-d71e-4775-acf9-d68bbb55e803] Name: [gatewayName]] Description: [create gateway] Type: [GROUP] Gateway member list: [ 5da35b42-1e37-4c3f-928b-0afc77fcfd34 ffd8176c-820a-4dc5-94a9-5f4c4fbff0c5 ]
Explanation	A gateway was created.
Possible failure causes	· The service is disabled. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · Unknown internal server error. · Invalid description. · Invalid name. · Invalid parameter. · The gateway already exists. · Invalid gateway type. · The gateway name already exists. · You can specify a maximum of two gateway members when the gateway type is GROUP. · You can specify only one gateway member when the gateway type is VIRTUAL. · Cannot specify nonexistent gateway members. · The gateway type and gateway member type do not match. · Duplicated gateway members exist. · The gateway members of a gateway must belong to different gateway groups. · The gateway members must belong to the same type of gateway groups. · The gateway groups to which the gateway members belong must have the same fw_for_external parameter value. · The gateway groups to which the gateway members belong must have the same fw_only_for_external parameter value. · The gateway groups to which the gateway members belong must have the same fw_for_internal parameter value. · The gateway groups to which the gateway members belong must have the same connection type. · You can specify only one gateway member when the fabric of the gateway group is not enabled with EVPN. · The fabrics of the gateway groups to which the gateway members belong must have the same EVPN state. · The gateway member has been bound to another gateway. · The gateway member must have different priorities. · The policy mode of the fabric bound to the newly added gateway member must be the same as that of existing gateway members. · The resource groups connected to the gateway members must map to the same private network. · Members of a gateway must use different IPv4 route priorities if they connect to the same external network resources and belong to the same fabric. · Members of a gateway must use different IPv6 route priorities if they connect to the same external network resources and belong to the same fabric. · The external resource group connected to the gateway member must map to the private network created for the shared gateway. · The resource group connected to the gateway member must map to the same private network attached to the gateway.

Update gateway

Keyword	UPDATE_GATEWAY_OP
Message text	Updated gateway: $1
Variable fields	$1: Gateway information.
Example	Updated gateway: ID: [741f1414-d71e-4775-acf9-d68bbb55e803] Name: [gatewayName]] Description: [create gateway] Type: [GROUP] Gateway member list: [ 5da35b42-1e37-4c3f-928b-0afc77fcfd34 ]
Explanation	A gateway was modified.
Possible failure causes	· The service is disabled. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · Unknown internal server error. · Invalid description. · Invalid name. · Invalid parameter. · The gateway does not exist. · The gateway is being used. · The gateway name already exists. · The gateway type cannot be edited. · You can specify a maximum of two gateway members when the gateway type is GROUP. · You can specify only one gateway member when the gateway type is VIRTUAL. · Cannot specify nonexistent gateway members. · The gateway type and gateway member type do not match. · Duplicated gateway members exist. · The gateway members of a gateway must belong to different gateway groups. · The gateway members must belong to the same type of gateway groups. · The gateway groups to which the gateway members belong must have the same fw_for_external parameter value. · The gateway groups to which the gateway members belong must have the same fw_only_for_external parameter value. · The gateway groups to which the gateway members belong must have the same fw_for_internal parameter value. · The gateway groups to which the gateway members belong must have the same connection type. · You can specify only one gateway member when the fabric of the gateway group is not enabled with EVPN. · The fabrics of the gateway groups to which the gateway members belong must have the same EVPN state. · The gateway member has been bound to another gateway. · The gateway member must have different priorities. · Cannot edit the border gateway, because the private network has a Layer 3 campus interconnect configured. · Cannot add a gateway member with the firewall function enabled to the gateway, because the gateway has been bound to a private network in group-based policy mode. · You cannot delete the egress gateway member, because a group policy is configured between the security group of the private network and the IT resource group of the egress gateway member.

Delete gateway

Keyword	DELETE_GATEWAY_OP
Message text	Deleted gateway: $1
Variable fields	$1: Gateway UUID.
Example	Deleted gateway: [741f1414-d71e-4775-acf9-d68bbb55e803]
Explanation	A gateway was deleted.
Possible failure causes	· The service is disabled. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid parameter. · The gateway does not exist. · The gateway is being used. · The gateway has gateway members.

Create gateway member

Keyword	CREATE_GATEWAY_MEMBER_OP
Message text	Created gateway member: $1
Variable fields	$1: Gateway member information.
Example	Created gateway member: ID: [741f1414-d71e-4775-acf9-d68bbb55e803] Name: [gwMemberName]] Description: [create gateway member] Family:[PHY_DEV ] Group ID:[ as1f1414-d71e-4775-acf9-d68bbb55e632] Priority: 0
Explanation	A gateway member was created.
Possible failure causes	· The service is disabled. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · Unknown internal server error. · Invalid description. · Invalid name. · Invalid parameter. · No network function list is specified for the physical resource. · The gateway group doesn't exist. · The management IP address conflicts with the host IP. · Invalid NETCONF username. · Invalid NETCONF password. · The IP address pool doesn't exist. · The VNFM service is not loaded. · The gateway group doesn't exist. · The default VLAN pool does not exist. · The gateway group is not bound to the specified type of default IP address pool. · The gateway member already exists. · The resource type is required. · The gateway member name already exists. · A virtual gateway member can be bound to only one resource pool. · NGFW gateway members cannot be bound to VNF templates. · A virtual gateway member can be bound to only one VNF template. · NFV gateway members cannot be bound to resource pools. · The gateway group is not enabled with the gateway feature. · Cannot specify priorities for virtual gateway members. · Network parameters are required. · The management IP address already exists. · Only NFV gateway members support the sec_ext_ip_pool parameter. · Invalid network type for the border gateway member. · No campus egress VLAN pool is specified for the border gateway members. · A campus egress VLAN pool of the VLAN type must be bound to the border gateway members. · A campus egress VLAN pool cannot be specified for the border gateway members on a VXLAN network.

Update gateway member

Keyword	UPDATE_GATEWAY_MEMBER_OP
Message text	Updated gateway member: $1
Variable fields	$1: Gateway member information.
Example	Updated gateway member: ID: [741f1414-d71e-4775-acf9-d68bbb55e803] Name: [gwMemberNameUpdate]] Description: [update gateway member] Family: [PHY_DEV ] Group ID:[ fs1f1414-d71e-4775-acf9-d68bbb55e639] Priority: 0
Explanation	A gateway member was modified.
Possible failure causes	· The service is disabled. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · Unknown internal server error. · Invalid description. · Invalid name. · Invalid parameter. · No network function list is specified for the physical resource. · The gateway group doesn't exist. · The management IP address conflicts with the host IP. · Invalid NETCONF username. · Invalid NETCONF password. · The IP address pool doesn't exist. · The VNFM service is not loaded. · The gateway group doesn't exist. · The default VLAN pool does not exist. · The gateway group is not bound to the specified type of default IP address pool. · The gateway member is being using. · The resource type is required. · The gateway member name already exists. · A virtual gateway member can be bound to only one resource pool. · NGFW gateway members cannot be bound to VNF templates. · A virtual gateway member can be bound to only one VNF template. · NFV gateway members cannot be bound to resource pools. · The gateway group is not enabled with the gateway feature. · Cannot specify priorities for virtual gateway members. · Network parameters are required. · The management IP address already exists. · Only NFV gateway members support the sec_ext_ip_pool parameter.

Delete gateway member

Keyword	DELETE_GATEWAY_MEMBER_OP
Message text	Deleted gateway member: $1
Variable fields	$1: Gateway member UUID.
Example	Deleted gateway member: 741f1414-d71e-4775-acf9-d68bbb55e803
Explanation	A gateway member was deleted.
Possible failure causes	· The service is disabled. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid parameter. · The gateway member does not exist. · The gateway member is being using.

Create device whitelist

Keyword	CREATE_DEVICE_WHITE_LIST_OP
Message text	Created device whitelist: $1
Variable fields	$1: Device whitelist information.
Example	Created device whitelist: ID:[ d5c1d35e-62f5-4259-a905-98183d9fd065] Serial number:[210235A2C4H187000881] Role name:[leaf] Sysname:[68-95] NetworkEntity ID:[ab.cdef.1234.5678.9abc.00] Loopback IP:[68.0.0.15] Gateway:[false]
Explanation	A device whitelist was created.
Possible failure causes	· Invalid JSON format. · Configuration recovery is in progress. · The controller is not the active leader. · Unknown internal server error. · Invalid device serial number. · To create a device whitelist, you must specify a device serial number. · Invalid role name. · The system name cannot exceed 64 characters. · Invalid network entity ID. · Invalid parameter. · Invalid IP address.

Update device whitelist

Keyword	UPDATE_DEVICE_WHITE_LIST_OP
Message text	Updated device whitelist: $1
Variable fields	$1: Device whitelist information.
Example	Updated device whitelist: ID:[ d5c1d35e-62f5-4259-a905-98183d9fd065] Serial number:[210235A2C4H187000881] Role name:[leaf] Sysname:[68-95] NetworkEntity ID:[ab.cdef.1234.5678.9abc.00] Loopback IP:[68.0.0.15] Gateway:[false]
Explanation	A device whitelist was modified.
Possible failure causes	· Invalid JSON format. · Configuration recovery is in progress. · The controller is not the active leader. · Unknown internal server error. · The specified device whitelist does not exist. · Invalid device serial number. · Invalid role name. · The system name cannot exceed 64 characters. · Invalid network entity ID. · Invalid parameter. · Invalid IP address.

Delete device whitelist

Keyword	DELETE_DEVICE_WHITE_LIST_OP
Message text	Deleted device whitelist: id: $1 serialNumber: $2
Variable fields	$1: Device whitelist ID. $2: Device serial number.
Example	Deleted device whitelist: id: [6a0627cb-1f15-41ee-b978-4e11056b7427] serialNumber: [1111]
Explanation	A device whitelist was deleted.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · Unknown internal server error. · The device whitelist doesn't exist.

Delete assetlist

Keyword	DELETE_ASSETLIST_OP
Message text	Deleted assetlist: $1
Variable fields	$1: Asset list ID.
Example	Deleted assetlist: c6c1d35e-62f5-4259-a905-98183d9fd065
Explanation	An asset list was deleted.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · Unknown internal server error. · The specified asset list does not exist.

Create egress interface

Keyword	CREATE_EGRESS_INTERFACE_OP
Message text	Created egress interface: $1.
Variable fields	$1: Egress interface information.
Example	Created egress interface: ID:[99fbae42-6da8-4dc0-bba3-5eb68ce89ad5] Device group ID:[50c2111d-bb35-43ea-90c0-4a8fed9c41b9] Device group name:[border] VLAN:[1111] Local IP:[192.168.34.3] Remote IP:[192.168.34.4] mask:[24] Mask: [24] Local ipv6: [1:0:0:0:0:0:0:1] Remote ipv6: [1:0:0:0:0:0:0:2] Prefix length: [96] ipv4Priority:[58] ipv4PriLevel:[null] ipv6Priority:[58] ipv6PriLevel:[null] extResources:[[ExtResource [resourceType=RESOURCE_GROUP, resourceId=d0254176-6caf-4e80-94f4-34393777a0f4, subnet=[158.0.0.0/24, 156.0.0.0/24, 1570:0:0:0:0:0:0:0/64]]]]
Explanation	An egress interface was created.
Possible failure causes	· A device group ID is required. · Invalid CIDR. · A VLAN ID is required. · A remote IP address is required. · The controller is not the active leader. · A local IP address is required. · A subnet mask is required. · Invalid VLAN ID. · The VLAN ID has been used. · The gateway member has been bound to another egress. · A remote IPv6 address is required. · Invalid remote IPv6 address. · Invalid local IPv6 address. · A local IPv6 address is required. · The local and remote IP addresses of the egress interface are not on the same subnet. · The local and remote IPv6 addresses of the egress interface are not on the same subnet. · The resource id is required when the resource type is resource_group. · The resource groups connected to the gateway members must map to the same private network. · Members of a gateway must use different IPv4 route priorities if they connect to the same external network resources and belong to the same fabric. · Members of a gateway must use different IPv6 route priorities if they connect to the same external network resources and belong to the same fabric. · The resource id does not exist. · Please add a minimum of one subnet to the IT resource group mapped to the gateway member. · The resource group mapped to a gateway member cannot contain address ranges. · IPv4 is selected. Please add IPv4 subnets to the resource group mapped to the gateway member. · IPv6 is selected. Please add IPv6 subnets to the resource group mapped to the gateway. · The external resource group connected to the gateway member must map to the private network created for the shared gateway. · The resource group connected to the gateway member must map to the same private network attached to the gateway. · The IPv4 route priority must be an integer in the range of 1 to 255. · The IPv6 route priority must be an integer in the range of 1 to 255. · The specified device interfaces cannot overlap with border gateway members. · The device has been specified for another gateway member. · The egress vlan pool id is required. · A VLAN network does not support automatically assigning IP addresses or VLANs.

Update egress interface

Keyword	UPDATE_EGRESS_INTERFACE_OP
Message text	Updated egress interface: $1.
Variable fields	$1: Egress interface information.
Example	Updated egress interface: ID:[99fbae42-6da8-4dc0-bba3-5eb68ce89ad5] Device group ID:[50c2111d-bb35-43ea-90c0-4a8fed9c41b9] Device group name:[border] VLAN:[1112] Local IP:[192.168.34.3] Remote IP:[192.168.34.4] Mask: [24] Local ipv6: [1:0:0:0:0:0:0:1] Remote ipv6: [1:0:0:0:0:0:0:2] Prefix length: [96] ipv4Priority:[58] ipv4PriLevel:[null] ipv6Priority:[58] ipv6PriLevel:[null] extResources:[[ExtResource [resourceType=RESOURCE_GROUP, resourceId=d0254176-6caf-4e80-94f4-34393777a0f4, subnet=[158.0.0.0/24, 156.0.0.0/24, 1570:0:0:0:0:0:0:0/64]]]]
Explanation	An egress interface was modified.
Possible failure causes	· Unknown internal server error. · The external interface does not exist. · The gateway member does not exist. · The gateway member has been bound to another egress. · The egress has been bound to another gateway member. · The resource id is required when the resource type is resource_group. · The resource groups connected to the gateway members must map to the same private network. · Members of a gateway must use different IPv4 route priorities if they connect to the same external network resources and belong to the same fabric. · Members of a gateway must use different IPv6 route priorities if they connect to the same external network resources and belong to the same fabric. · The resource id does not exist. · Please add a minimum of one subnet to the IT resource group mapped to the gateway member. · The resource group mapped to a gateway member cannot contain address ranges. · IPv4 is selected. Please add IPv4 subnets to the resource group mapped to the gateway member. · IPv6 is selected. Please add IPv6 subnets to the resource group mapped to the gateway. · The external resource group connected to the gateway member must map to the private network created for the shared gateway. · The resource group connected to the gateway member must map to the same private network attached to the gateway. · The IPv4 route priority must be an integer in the range of 1 to 255. · The IPv6 route priority must be an integer in the range of 1 to 255.

Delete egress interface

Keyword	DELETE_EGRESS_INTERFACE_OP
Message text	Deleted egress interface: $1.
Variable fields	$1: Egress interface information.
Example	Deleted egress interface: ID:[99fbae42-6da8-4dc0-bba3-5eb68ce89ad5] Device group ID:[50c2111d-bb35-43ea-90c0-4a8fed9c41b9] Device group name:[border] VLAN:[1113] Local IP:[192.168.34.3] Remote IP:[192.168.34.4] Mask: [24] Local ipv6: [1:0:0:0:0:0:0:1] Remote ipv6: [1:0:0:0:0:0:0:2] Prefix length: [96]
Explanation	An egress interface was deleted.
Possible failure causes	· The external interface does not exist. · The controller is not the active leader. · The egress is being used by a gateway member and cannot be deleted. · Token aged. · Invalid parameter.

Create external connectivity

Keyword	CREATE_EXTCONNECT_OP
Message text	Created external connectivity: $1.
Variable fields	$1: External connectivity information.
Example	Created external connectivity: ID=e49474a4-7035-4dd3-b512-35ae11abf5ee Gateway ID=584f5471-d601-40be-8ac5-b0622a526a28 Gateway name:[chukou_gw1] Mode=public VRF=ck1
Explanation	An external connectivity was created.
Possible failure causes	· Invalid external connectivity mode. · The VPN instance name has been used. · The VPN instance name cannot exceed 31 characters. · The external connectivity already exists. · The controller is not the active leader. · The gateway does not exist. · Please specify a VPN instance (VRF) when the gateway is shared by multiple VPNs. · Do not specify a VPN instance (VRF) when the gateway is bound with only one VPN.

Update external connectivity

Keyword	UPDATE_ EXTCONNECT_OP
Message text	Updated ExtNetwork: $1.
Variable fields	$1: External connectivity information.
Example	Updated external connectivity: ID=e49474a4-7035-4dd3-b512-35ae11abf5ee Gateway ID=584f5471-d601-40be-8ac5-b0622a526a28 Gateway name:[chukou_gw1] Mode=public VRF=ck2
Explanation	An external connectivity was modified.
Possible failure causes	· Unknown internal server error. · The external connectivity does not exist. · The gateway does not exist. · The gateway mode cannot be modified. · The VPN instance to which the external connectivity belongs cannot be modified.

Delete external connectivity

Keyword	DELETE_ EXTCONNECT_OP
Message text	Deleted external connectivity: $1.
Variable fields	$1: External connectivity information.
Example	Deleted external connectivity: ID=e49474a4-7035-4dd3-b512-35ae11abf5ee Gateway ID=584f5471-d601-40be-8ac5-b0622a526a28 Gateway name:[chukou_gw1] Mode=public VRF=ck1
Explanation	An external connectivity was deleted.
Possible failure causes	· Invalid parameter. · The controller is not the active leader.

Add AAA template

Keyword	ADD_AAA_TEMPLATE_OP
Message text	Created AAA templates: "$1".
Variable fields	$1: AAA template information.
Example	Created AAA templates: { "AAA template": [ { "ID": "", "Template name": "bf02", "Default domain": "1234", "Server IP": "192.168.25.98", "Secondary server IP": "", "Password": "1234", "RADIUS schemes": [ { Name": "bf02", Carry domain names": "true", Accounting interval": "", Domain names": [ { "Domain name": "1234" }, { "Domain name": "123" } ] } ] } ] }
Explanation	One or multiple AAA templates were created.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · The AAA template ID already exists. · An AAA template name is required. · The AAA template name cannot exceed 255 characters. · The AAA template name already exists. · The IP address of the primary server is required. · The IP address of the primary server is invalid. · The IP address of the secondary server is invalid. · A password is required. · The password cannot exceed 64 characters. · A default domain name is required. · The default domain name cannot exceed 255 characters. · The RADIUS scheme field is empty. · The RADIUS scheme name field is empty. · The RADIUS scheme name cannot exceed 32 characters. · A RADIUS scheme name already exists. · You must specify whether to carry domain names in the RADIUS schemes. · A domain name specified in a RADIUS scheme already exists. · The domain name specified in a RADIUS scheme cannot exceed 255 characters. · The default domain name must be specified in a RADIUS scheme. · The AAA template ID is invalid. · A RADIUS scheme ID is invalid. · An AAA template supports a maximum of 16 RADIUS schemes.

Update AAA template

Keyword	UPDATE_AAA_TEMPLATE_OP
Message text	Update AAA template “$1”
Variable fields	$1: AAA template information.
Example	Updated AAA template: { "AAA template": { "ID": "", "Template name": "bf02", "Default domain": "1234", "Server IP": "192.168.25.98", "Secondary server IP": "", "Password": "1234", "RADIUS schemes": [ { Name": "bf02", Carry domain names": "true", Accounting interval": "", Domain names": [ { "Domain name": "1234" }, { "Domain name": "123" } ] } ] } }
Explanation	An AAA template was modified.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · An AAA template name is required. · The AAA template name cannot exceed 255 characters. · The AAA template name already exists. · The IP address of the primary server is required. · The IP address of the primary server is invalid. · The IP address of the secondary server is invalid. · A password is required. · The password cannot exceed 64 characters. · A default domain name is required. · The default domain name cannot exceed 255 characters. · The RADIUS scheme field is empty. · The RADIUS scheme name field is empty. · The RADIUS scheme name cannot exceed 32 characters. · A RADIUS scheme name already exists. · You must specify whether to carry domain names in the RADIUS schemes. · A domain name specified in a RADIUS scheme already exists. · The domain name specified in a RADIUS scheme cannot exceed 255 characters. · The default domain name must be specified in a RADIUS scheme. · The AAA template ID is invalid. · A RADIUS scheme ID is invalid. · An AAA template supports a maximum of 16 RADIUS schemes.

Delete AAA template

Keyword	DELETE_AAA_TEMPLATE_OP
Message text	Delete AAA template “$1”.
Variable fields	$1: AAA template ID.
Example	Deleted AAA template “1c6d3cf4-d622-4121-b193-bfac63a5e409”.
Explanation	An AAA template was deleted.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · The AAA template does not exist. · The AAA template has been used.

Add MAC template

Keyword	ADD_MAC_TEMPLATE_OP
Message text	Created MAC authentication templates: “$1”.
Variable fields	$1: MAC authentication template information.
Example	Created MAC authentication templates: Device-level: { "MAC template": [{ "ID": "51162974-2903-4c28-a62b-9053c669c8fc", "Template name": "mac", "Template type": "DEV", "Template category": "MAC", "Portal authentication": true, "Portal IP": ["10.10.10.1"], "Domain": null, "Guest VSI": null, "Critical VSI": null, "cmd": null, "User defined": true }] } } Or Interface-level: { "MAC template": [{ "ID": "044e318a-c306-4146-8363-0966536c8275", "Template name": "mac_if", "Template type": "IF", "Template category": "MAC", "Portal authentication": null, "Portal IP": null, "Domain": "1234", "Guest VSI": null, "Critical VSI": true, "cmd": null, "User defined": true }] }
Explanation	One or multiple MAC authentication templates were created.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · The MAC authentication template ID already exists. · Invalid MAC authentication template type. · A MAC authentication template type is required. · The MAC authentication template name cannot exceed 255 characters. Only Chinese characters, letters, digits, and underscores (_) are allowed. · The domain name is invalid. · A MAC authentication template name is required. · Invalid portal IP. · You must specify whether to enable portal authentication. · A portal IP is required. · You cannot enter a portal IP when portal authentication is disabled. · The Critical VSI field cannot be empty in an interface-level template. · The Domain field must be empty in a device-level template. · The Portal IP and Portal authentication fields must be empty in an interface-level template.

Update MAC template

Keyword	UPDATE_MAC_TEMPLATE_OP
Message text	Updated MAC authentication template: “$1”.
Variable fields	$1: MAC authentication template information.
Example	Updated MAC authentication template: Device-level: { "MAC template": { "ID": "51162974-2903-4c28-a62b-9053c669c8fc", "Template name": "mac", "Template type": "DEV", "Template category": "MAC", "Portal authentication": true, "Portal IP": ["10.10.10.1"], "Domain": null, "Guest VSI": null, "Critical VSI": null, "cmd": null, "User defined": true }] } } Or Interface-level: { "MAC template":{ "ID": "044e318a-c306-4146-8363-0966536c8275", "Template name": "mac_if", "Template type": "IF", "Template category": "MAC", "Portal authentication": null, "Portal IP": null, "Domain": "1234", "Guest VSI": null, "Critical VSI": true, "cmd": null, "User defined": true } }
Explanation	A MAC authentication template was modified.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · The template ID cannot be modified. · The template type cannot be modified. · The User defined field cannot be modified. · The MAC authentication template name already exists. · Invalid MAC authentication template type. · A MAC authentication template type is required. · The MAC authentication template name cannot exceed 255 characters. Only Chinese characters, letters, digits, and underscores (_) are allowed. · The domain name is invalid. · A MAC authentication template name is required. · Invalid portal IP. · You must specify whether to enable portal authentication. · A portal IP is required. · You cannot enter a portal IP when portal authentication is disabled. · The Critical VSI field cannot be empty in an interface-level template. · The Domain field must be empty in a device-level template. · The Portal IP and Portal authentication fields must be empty in an interface-level template.

Delete MAC template

Keyword	DELETE_MAC_TEMPLATE_OP
Message text	Deleted MAC authentication template “$1”.
Variable fields	$1: MAC authentication template ID.
Example	Deleted MAC authentication template “1c6d3cf4-d622-4121-b193-bfac63a5e409”.
Explanation	A MAC authentication template was deleted.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · The MAC authentication template does not exist. · The MAC authentication template has been used.

Add 802.1X template

Keyword	ADD_802.1X_TEMPLATE_OP
Message text	Created 802.1X authentication templates: “$1”.
Variable fields	$1: 802.1X authentication template information.
Example	Created 802.1X authentication templates: Device-level: { "802.1X templates": [{ "ID": "d2b449f7-95d6-4e02-8e44-ce7d09d68a4e", "Template name": "dot", "Template type": "DEV", "Template category": "DOT", "Authentication method": "PAP", "Auth fail VSI": null, "Guest VSI": null, "Critical VSI": null, "cmd": null, "User defined": true }] } Or Interface-level: { "802.1X templates":[ { "ID": "710f075e-259d-4012-9225-921bb87a2a0e", "Template name": "dot_if", "Template type": "IF", "Category": "DOT", "Authentication method": null, "Auth fail VSI": null, "Guest VSI": null, "Critical VSI": true, "cmd": null, "User defined": true }] }
Explanation	One or multiple 802.1X authentication templates were created.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · The 802.1X authentication template ID already exists. · The 802.1X authentication method is invalid. · The 802.1X authentication template type is invalid. · An 802.1X authentication template type is required. · The 802.1X authentication template name cannot exceed 255 characters. Only Chinese characters, letters, digits, and underscores (_) are allowed. · An 802.1X authentication template name is required. · The 802.1X authentication template name already exists. · The Authentication method field must be empty in an interface-level template. · The Critical VSI field cannot be empty in an interface-level template. · The Authentication method field cannot be empty in a device-level template.

Update 802.1X auth template

Keyword	UPDATE_802.1X_TEMPLATE_OP
Message text	Updated 802.1X authentication template: “$1”.
Variable fields	$1: 802.1X authentication template information.
Example	Updated 802.1X authentication template: Device-level: { "802.1X template": { "ID": "d2b449f7-95d6-4e02-8e44-ce7d09d68a4e", "Template name": "dot", "Template type": "DEV", "Category": "DOT", "Authentication method": "PAP", "Auth fail VSI": null, "Guest VSI": null, "Critical VSI": null, "cmd": null, "User defined": true } } Or Interface-level: { "802.1X template": { "ID": "710f075e-259d-4012-9225-921bb87a2a0e", "Template name": "dot_if", "Template type": "IF", "Category": "DOT", "Authentication method": null, "Auth fail VSI": null, "Guest VSI": null, "Critical VSI": true, "cmd": null, "User defined": true } }
Explanation	An 802.1X authentication template was modified.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · The 802.1X authentication template ID cannot be modified. · The 802.1X authentication template category cannot be modified. · The 802.1X authentication template type cannot be modified. · The User defined field cannot be modified. · The 802.1X authentication method is invalid. · The 802.1X authentication template type is invalid. · An 802.1X authentication template type is required. · The 802.1X authentication template name cannot exceed 255 characters. Only Chinese characters, letters, digits, and underscores (_) are allowed. · An 802.1X authentication template name is required. · The 802.1X authentication template name already exists. · The Authentication method field must be empty in an interface-level template. · The Critical VSI field cannot be empty in an interface-level template. · The Authentication method field cannot be empty in a device-level template.

Delete 802.1X auth template

Keyword	DELETE_802.1X_TEMPLATE_OP
Message text	Deleted 802.1X authentication template “$1”.
Variable fields	$1: 802.1X authentication template ID.
Example	Deleted 802.1X authentication template “1c6d3cf4-d622-4121-b193-bfac63a5e409”.
Explanation	An 802.1X authentication template was deleted.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · The 802.1X authentication template does not exist. · The 802.1X authentication template has been used.

Synchronization device bridgeMac and serialNumber infor

Keyword	START_SYNCHRONIZATION_BRIDGEMAC_SERIALNUMBER_OP
Message text	Started to synchronize physical NE bridgeMac and serialNumber info: $1
Variable fields	$1: Synchronized information.
Example	Started to synchronize physical NE bridgeMac and serialNumber info: deviceList: [ 59c0178f-aec7-4d75-abfb-01834cacd000, 124e419b-6965-4fc3-af67-31c98dd9e345, ] reversRefresh: [false]
Explanation	Synchronized bridge MAC and serial number information on the controller to the devices.
Possible failure causes	· Unknown internal server error. · Failed to obtain information about the IRF fabric.

Create replacement task

Keyword	CREATE_REPLACE_TASK_OP
Message text	Created replacement task: $1
Variable fields	$1: Replacement task information.
Example	Created replacement task: replaceDeviceId:[ bbc199ca-8792-4656-8bab-5a16fc52c806] replaceType:[1] faultDevId:[bbc199ca-8792-4656-8bab-5a16fc52c806] devSn:[13212adasd2q321dadsa] masteSpineMac:[01-23-45-67-89-ab] startCfgName:[10.100.0.2_20190611093442_startup.cfg] faultDeviceSn:[13212adasd2q321dadss]
Explanation	A replacement task was created.
Possible failure causes	· Configuration recovery is in progress. · Invalid JSON format. · The controller is not the active leader. · Unknown internal server error. · A master spine MAC is required when the replacement type is master spine. · The master spine MAC is invalid. · The number of running replacement tasks cannot exceed 5. · A master spine device supports only the master spine replacement type. · The backup configuration file of the failed device does not exist. · The replacement device does not exist. · The serial number of the replacement device is invalid. · The replacement device and failed device cannot be the same. · Replacement device with the specified serial number has been specified in another replacement task. · If you specify a replacement device by its serial number, make sure the device is not managed by the controller. · Cannot replace a standalone device with an IRF fabric. · Failed device with the specified serial number does not exist. · The replacement device type cannot be underlay. · The failed device is not bound to a fabric. · The replacement device is not bound to a fabric. · The replacement device must belong to the same fabric as the failed device. · The replacement device is not activated. · The replacement device must have the same role as the failed device. · Internal error. · The replacement task already exists. · The specified failed device does not exist. · The failed device is being deleted. · Failed device with the specified ID does not exist. · The replacement device must have the same role as the failed device. · The replacement device must belong to same fabric as the failed device. · The fault device has been in another replacement task. · No faulty device information was found.

Delete replacement task

Keyword	DELETE_REPLACE_TASK_OP
Message text	Deleted replacement task: $1.
Variable fields	$1: UUID of the replacement device.
Example	Deleted replacement task: fa906566-87d5-4480-b7e7-12dc20bc6173.
Explanation	A replacement task was deleted.
Possible failure causes	· Configuration recovery is in progress. · Invalid JSON format. · The controller is not the active leader. · Unknown internal server error. · The specified replacement task does not exist. · The current stage of the replacement task does not support deletion.

Update ONU

Keyword	UPDATE_ONU_OP
Message text	Updated ONU: $1
Variable fields	$1: ONU information.
Example	Updated ONU: ID:[cee6d907-7dd7-4d18-9e83-e55bdeb031f8] Name:[Onu4/0/6:1] BindMac:[94:28:2e:c3:64:04] SiteName: [Hangzhou] Location:[teachBuilding]
Explanation	An ONU was edited. Only the site name and location can be edited in the current software version.
Possible failure causes	· Invalid JSON format. · The ONU with the specified ID does not exist. · Unknown internal server error.

Delete ONU

Keyword	DELETE_ONU_OP
Message text	Deleted ONU: $1
Variable fields	$1: UUID of the ONU.
Example	Deleted ONU: ID:[cee6d907-7dd7-4d18-9e83-e55bdeb031f8]
Explanation	An ONU was deleted.
Possible failure causes	· The ONU with the specified ID does not exist. · The OLT to which the ONU belongs is inactive. · Unknown internal server error.

Create AP

Keyword	CREATE_AP_OP
Message text	Created AP: $1
Variable fields	$1: AP device information.
Example	Created AP: Name:[ap1] OnuId:[dee6d907-7dd7-4d18-9e83-e55bdeb031f8] OltId:[dee6d907-7dd7-4d18-9e83-e55bdeb031f1] OnuIfIndex:[18726] UniNumber:[3]
Explanation	An AP was created.
Possible failure causes	· Invalid JSON format. · The OLT with the specified ID does not exist. · The ONU with the specified ID does not exist. · Unknown internal server error.

Delete AP

Keyword	DELETE_AP_OP
Message text	Deleted AP: $1
Variable fields	$1: UUID of the AP.
Example	Deleted AP: ID:[ dee6d907-7dd7-4d18-9e83-e55bdeb031f8]
Explanation	An AP was deleted.
Possible failure causes	· Invalid JSON format. · The AP with the specified ID does not exist. · Unknown internal server error.

Add Redundant Port

Keyword	ADD_REDUNDANT_PORT_OP
Message text	Added redundant port: $1
Variable fields	$1: Redundant interface information.
Example	Added redundant port: OltId:[dee6d907-7dd7-4d18-9e83-e55bdeb031f8] Index:[3] Description:[Rolt3] PrimaryPort:[ Olt4/0/1] StandbyPort:[ Olt4/0/1]
Explanation	A redundant interface was created.
Possible failure causes	· Invalid JSON format. · Unknown internal server error. · The index number already exists. · The OLT member ports cannot be null. · The OLT member port has been bound to another redundant port. · The two OLT member ports cannot be the same. · The description cannot exceed 255 characters.

Update Redundant Port

Keyword	UPDATE_REDUNDANT_PORT_OP
Message text	Updated redundant port: $1
Variable fields	$1: Redundant interface information.
Example	Updated redundant port: OltId:[dee6d907-7dd7-4d18-9e83-e55bdeb031f8] Description:[Rolt3] OltPort:[ Olt4/0/1] NewPort:[ Olt4/0/3]
Explanation	A redundant interface was edited.
Possible failure causes	· Invalid JSON format. · Unknown internal server error. · The OLT member ports cannot be null. · The OLT member port has been bound to another redundant port. · The description cannot exceed 255 characters.

Delete Redundant Port

Keyword	DELETE_REDUNDANT_PORT_OP
Message text	Deleted redundant port: $1
Variable fields	$1: UUID of the redundant interface.
Example	Deleted redundant port: ID:[ceb6d907-7dd6-4d18-9e83-e55bdeb031e9]
Explanation	A redundant interface was deleted.
Possible failure causes	· Unknown internal server error. · The redundant port does not exist.

Batch import wireless APs to ACs

Keyword	IMPORT_AP_OP
Message text	Import wireless APs finished, success count: $1
Variable fields	$1: Number of APs successfully imported.
Example	Import wireless APs finished, success count: 50
Explanation	Multiple APs were imported in bulk.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · The import file doesn`t exists. · The import file must be a excel. · The import excel template is not match, please download new excel template. · The import file found no AP information. · Ap import all failed. · Unknown error.

Synchronization ACs info

Keyword	SYNCHRONIZATION_AC_INFO_OP
Message text	Obtained IP addresses of multiple ACs ($1) in bulk.
Variable fields	$1: IP addresses of ACs.
Example	Obtained IP addresses of multiple ACs (1.1.1.1, 2.2.2.2) in bulk.
Explanation	Obtained IP addresses of multiple ACs in bulk.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Internal server error.

Delete APs from the AC

Keyword	DELETE_APS_OP
Message text	Deleted multiple APs from the AC $1 in bulk.
Variable fields	$1: AC name.
Example	Deleted multiple APs from the AC wlan in bulk.
Explanation	Multiple APs on an AC were deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Internal server error.

Redeployed traditional access devices

Keyword	REDEPLOY_TRADITIONAL_ACCESS_OP
Message text	Redeployed traditional access devices: $1
Variable fields	$1: Redeployed settings.
Example	Redeployed traditional access devices:[ { Traditional access device UUID:[14f3e43e-ec4b-438a-8687-acfc9a77dd04] Traditional access device service type :[STP] Traditional access device keyServiceParam:[Ethernet1/0/10] }, { Traditional access device UUID:[14f3e43e-ec4b-438a-8687-acfc9a77dd04] Traditional access device service type :[STP] Traditional access device keyServiceParam:[Ethernet1/0/12] } ]
Explanation	Redeployed settings to an access device.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · The device does not exist. · The device is not active. · The device is being deleted. · Security group VLAN $1 does not exist. · Cannot configure STP settings for interface $1. · Cannot deploy PVID $1 to port $2.

Create third-party service device

Keyword	CREATE_THIRDPARTY_SERVICE_DEVICE_OP
Message text	Created third-party service device: $1
Variable fields	$1: Third-party service device information.
Example	Created third party service device: ID:[e9d78b81-1116-463a-b7be-fdd51291eca8] Name:[fw_device] Description:[] Tenant ID:[264852ef-f01e-4c51-9206-0a6363f531c1] Ingress VXLAN :[100] Ingress IP Address :[100.0.0.1] Egress VXLAN :[101] Egress IP Address :[101.0.0.1]
Explanation	A third-party service device was created.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · Unknown internal server error. · Invalid name. · Invalid description. · The specified tenant does not exist. · Invalid incoming vPort VXLAN ID. · Invalid outgoing vPort VXLAN ID. · Invalid incoming vPort IP address. · Invalid outgoing vPort IP address. · The ingress vPort IP address is required. · The egress vPort IP address is required. · The ingress vPort VXLAN ID is required. · The egress vPort VXLAN ID is required. · The UUID already exists. · The name already exists. · Failed to create third party service device because either ingress or egress port is in use. · The Layer 2 network domain with the segment ID as the ingress port VXLAN ID does not exist. · The ingress port IP address is not within the subnets of the ingress port Layer 2 network domain. · The Layer 2 network domain with the segment ID as the egress port VXLAN ID does not exist. · The egress port IP address is not within the subnets of the egress port Layer 2 network domain.

Update third-party service device

Keyword	UPDATE_THIRDPARTY_SERVICE_DEVICE_OP
Message text	Updated third-party service device: $1
Variable fields	$1: Third-party service device information.
Example	Updated third party service device: ID:[e9d78b81-1116-463a-b7be-fdd51291eca8] Name:[fw_device] Description:[fw_device]
Explanation	A third-party service device was edited.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · Unknown internal server error. · The third-party service device does not exist. · Invalid name. · Invalid description. · The tenant field is read only. · The access mode field is read only. · The incoming vPort IP address field is read only. · The outgoing vPort IP address field is read only. · The incoming vPort field is read only. · The outgoing vPort field is read only. · The Layer 2 network domain with the segment ID as the ingress port VXLAN ID does not exist. · The ingress port IP address is not within the subnets of the ingress port Layer 2 network domain. · The Layer 2 network domain with the segment ID as the egress port VXLAN ID does not exist. · The egress port IP address is not within the subnets of the egress port Layer 2 network domain.

Delete third-party service device

Keyword	DELETE_THIRDPARTY_SERVICE_DEVICE_OP
Message text	Deleted third-party service device: $1
Variable fields	$1: Third-party service device name.
Example	Deleted third party service device:fw_device
Explanation	A third-party service device was deleted.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · Configuration recovery is in progress. · The third-party service device does not exist. · Failed to delete the third-party service device because it has been used by a service. · Invalid UUID.

Create third-party service

Keyword	CREATE_THIRDPARTY_SERVICE_OP
Message text	Created third-party service function: $1
Variable fields	$1: Third-party service resource information.
Example	Created third party service function: ID:[42771aed-6aa3-4234-b897-4652f4c07c23] Name:[fw_function] Description:[] Tenant ID:[264852ef-f01e-4c51-9206-0a6363f531c1] Referenced DeivceIdList:[ third party device config id:[Id[value=e9d78b81-1116-463a-b7be-fdd51291eca8]] ]
Explanation	A third-party service resource was created.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · Unknown internal server error. · Invalid name. · Invalid parameter. · Invalid description. · The tenant doesn’t exist. · The UUID already exists. · The third party service device is not existed. · Failed to bind third party service device because it is used by another third party service function. · The third party service resource does not exist. · The Layer 2 network domain and service member for the VXLAN belong to different isolation domains. · The isolation domain does not exist.

Update third-party service

Keyword	UPDATE_THIRDPARTY_SERVICE_OP
Message text	Updated third-party service function: $1
Variable fields	$1: Third-party service resource information.
Example	Updated third party service function: ID:[42771aed-6aa3-4234-b897-4652f4c07c23] Name:[fw_function] Description:[fw_function]
Explanation	A third-party service resource was edited.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · Unknown internal server error. · The third-party service device does not exist. · Invalid name. · Invalid description. · The tenant field is read only. · The third-party service device field is read only.

Delete third party service

Keyword	DELETE_THIRDPARTY_SERVICE_OP
Message text	Deleted third-party service function: $1
Variable fields	$1: Third-party service resource name.
Example	Deleted third party service function:fw_function
Explanation	A third-party service resource was deleted.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · Configuration recovery is in progress. · The third-party service does not exist. · Failed to delete the third-party service because it has been used by a service chain. · Invalid UUID.

Create third-party device config template

Keyword	ADD_TRADITIONAL_DEVICE_CFG_MODEL_OP
Message text	Created third-party device config template: $1
Variable fields	$1: Third-party device configuration template information.
Example	Created third-party device config template: { "models": [ { “id": "6b1cd62d-587a-4d0a-abbf-c5a011a18ec8", "name": "H3C_V3", "sysOid": "1.3.6.1.4.1.25506.1.1845", "sysDesc": "H3C Comware Platform Software, Software Version 3.1" }, ] }
Explanation	A third-party device configuration template was created.
Possible failure causes	· Invalid UUID. · Duplicated third-party device config template ID exist. · Please specify the third-party device config template name. · Duplicated third-party device config template name exist. · Please specify the third-party device config template system OID. · The system OID cannot exceed 255 characters. · The system description cannot exceed 255 characters. · The system OID already exist. · The system OID and description already exist. · The third-party device config template ID already exist. · The third-party device config template name cannot exceed 64 characters. · The third-party device config template name already exist. · The third-party device config template doesn't exist. · The third-party device config template ID is required. · Invalid third-party device config template ID. · The system OID and system description already exist. · The system OID already exist. · Invalid JSON format.

Update third-party device config template

Keyword	UPD_TRADITIONAL_DEVICE_CFG_MODEL_OP
Message text	Updated third-party device config template: $1
Variable fields	$1: Third-party device configuration template information.
Example	Updated third-party device config template: { "models": [ { “id": "6b1cd62d-587a-4d0a-abbf-c5a011a18Ed9", "name": "H3C_V3", "sysOid": "1.3.6.1.4.1.25506.1.1845", "sysDesc": "H3C Comware Platform Software, Software Version 3.1" }, ] }
Explanation	A third-party device configuration template was updated.
Possible failure causes	· Invalid UUID. · Duplicated third-party device config template ID exist. · Please specify the third-party device config template name. · Duplicated third-party device config template name exist. · Please specify the third-party device config template system OID. · The system OID cannot exceed 255 characters. · The system description cannot exceed 255 characters. · The system OID already exist. · The system OID and description already exist. · The third-party device config template ID already exist. · The third-party device config template name cannot exceed 64 characters. · The third-party device config template name already exist. · The third-party device config template doesn't exist. · The third-party device config template ID is required. · Invalid third-party device config template ID. · The system OID and system description already exist. · The system OID already exist. · Invalid JSON format.

Delete third-party device config template

Keyword	DEL_TRADITIONAL_DEVICE_CFG_MODEL_OP
Message text	Deleted third-party device config template: $1
Variable fields	$1: Third-party device configuration template name.
Example	Deleted third-party device config template: aaa
Explanation	A third-party device configuration template was deleted.
Possible failure causes	· The third-party device config template doesn't exist. · Invalid UUID.

Add configuration task

Keyword	ADD_REQUEST_DEFINE_OP
Message text	Added configuration task: $1
Variable fields	$1: Configuration task information.
Example	Added configuration task: $1 { "request_defines": [ { "modelId":"223c5cf4-d621-4111-b193-bfac63a5e47a", "name": "user_define", "type": "UserDefine", "category":"basic" } ] }
Explanation	A configuration task was created.
Possible failure causes	· Invalid UUID. · Duplicated configuration task ID exist. · Please specify the configuration task name. · Duplicated configuration task name exist. · The configuration task ID already exist. · The configuration task name cannot exceed 255 characters. · The configuration task name already exist. · Please specify configuration task type name. · Invalid configuration task type. · The configuration task type already exist. · Please specify configuration task type ID. · The configuration task doesn't exist.

Delete configuration task

Keyword	DEL_REQUEST_DEFINE
Message text	Deleted configuration task: $1
Variable fields	$1: Configuration task name.
Example	Deleted configuration task: aaa
Explanation	A configuration task was deleted.
Possible failure causes	The configuration task doesn't exist.

Add failure signature

Keyword	ADD_ERROR_MESSAGE_OP
Message text	Added failure signature: $1
Variable fields	$1: Failure signature information.
Example	Added failure signature: $1 { "error_messages": [ { "id":"794a6de8-4239-fdb2-ccad-b5736d28", "modelId":"694a6de8-4239-fdb2-ccad-b5736d45", "message":"failed" }, ] }
Explanation	A failure signature was created.
Possible failure causes	· Please specify failure signature. · The failure signature ID already exist. · Please specify failure signature. · The failure signature cannot exceed 255 characters. · The failure signature of a third-party device config template cannot be duplicated. · Duplicated failure signature ID exist. · Please specify failure signature ID. · The failure signature doesn't exist.

Delete failure signature

Keyword	DELETE_ERROR_MESSAGE_OP
Message text	Deleted failure signature: $1
Variable fields	$1: Failure signature name.
Example	Deleted failure signature: aa
Explanation	A failure signature was deleted.
Possible failure causes	The failure signature doesn't exist.

Add Step

Keyword	ADD_STEP_OP
Message text	Added step: $1
Variable fields	$1: Step information.
Example	Added step: $1 { "steps": [ { "id":"ffffffe8-4239-fdb2-ccad-000000011", "name": "Set interface PVID_HAWEI", "reference":"basic_request_name", "request_id":"794a6de8-4239-fdb2-ccad-b5736d28", "index":"1" }, ] }
Explanation	A step was created.
Possible failure causes	· The step ID of a third-party device config template cannot be duplicated. · Please specify step name. · The step name cannot exceed 255 characters. · Invalid step number. · The configuration task name doesn't exist. · Please specify step command. · The step command cannot exceed 255 characters. · Please specify success identifier. · The success identifier cannot exceed 255 characters. · Invalid read interval. · Invalid timeout. · The timeout must be higher than the read interval. · The step name of a third-party device config template cannot be duplicated. · The step number of a third-party device config template cannot be duplicated. · The step ID doesn't exist.

Update Step

Keyword	UPD_STEP_OP
Message text	Updated step: $1
Variable fields	$1: Step information.
Example	Updated step: $1 { "steps": [ { "id":"ffffffe8-4239-fdb2-ccad-000000022", "name": "Set interface PVID_HAWEI", "reference":"basic_request_name", "request_id":"794a6de8-4239-fdb2-ccad-b5736d28", "index":"1" }, ] }
Explanation	A step was updated.
Possible failure causes	· The step ID of a third-party device config template cannot be duplicated. · Please specify step name. · The step name cannot exceed 255 characters. · Invalid step number. · The configuration task name doesn't exist. · Please specify step command. · The step command cannot exceed 255 characters. · Please specify success identifier. · The success identifier cannot exceed 255 characters. · Invalid read interval. · Invalid timeout. · The timeout must be higher than the read interval. · The step name of a third-party device config template cannot be duplicated. · The step number of a third-party device config template cannot be duplicated. · The step ID doesn't exist.

Delete Step

Keyword	DEL_STEP_OP
Message text	Deleted step: $1
Variable fields	$1: Step ID.
Example	Deleted step: 2
Explanation	A step was deleted.
Possible failure causes	The step ID doesn't exist.

Copy existing template

Keyword	CLONE_TRADITIONAL_DEVICE_CFG_MODEL_OP
Message text	Copy existing template: $1
Variable fields	$1: UUID of the existing template.
Example	Copy existing template: 00000000-587a-4d0a-abbf-c5a00fffffff
Explanation	An existing template was copied.
Possible failure causes	· Invalid JSON format. · The third-party device config template doesn't exist.

Create FW Resource

Keyword	CREATE_FW_RESOURCE_OP
Message text	Created firewall resource “$1”.
Variable fields	$1: Firewall resource configuration.
Example	Created firewall resource: ID: “1c6d3cf4-d622-4121-b193-bfac63a5e409” Management network: Gateway address: Egress VLAN: Egress IPv4 address: Egress IPv6 address:
Explanation	A firewall resource was created.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · Unknown error. · Invalid JSON format. · The firewall resource ID already exists. · The firewall management network is required. · The firewall gateway address is required. · The egress IPv4 address is required. · The egress IPv6 address is required. · Invalid gateway address. · The gateway address and management address must belong to the same network. · The management address and gateway address cannot be the same. · The management address must be an IPv4 address. · The gateway address must be an IPv4 address. · The egress IPv4 address must be an IPv4 address. · The egress IPv6 address must be an IPv6 address. · Invalid egress IPv4 address. · Invalid egress IPv6 address. · The firewall already exists with the specified management address. · The firewall already exists with the specified egress IPv4 address. · The firewall already exists with the specified gateway address. · The firewall already exists with the specified egress IPv6 address. · The firewall already exists with the specified egress VLAN. · Duplicated IDs exist for the firewall resources created in bulk. · Duplicated VLAN IDs exist for the firewall resources created in bulk. · Invalid management address. · The management address and egress IPv4 address cannot belong to the same network. · The egress IPv4 address and the management IPv4 address of the firewall resource must be on different subnets. · The egress IPv4 address and the uplink IPv4 address of the firewall resource must be on different subnets. · The egress IPv6 address and the uplink IPv6 address of the firewall resource must be on different subnets. · Failed to create the context. · The firewall egress VLAN of the gateway member cannot be the same as the egress VLAN of the gateway member's border device group. · Failed to allocate resources, because the specified security egress address pool does not have enough IP addresses. · Failed to allocate resources, because the security egress VLAN pool does not have enough VLAN IDs. · Failed to allocate resources, because the specified firewall management address pool does not have enough IP addresses. External Interface · Invalid external IPv4 next hop. · Invalid external destination IPv4 address. · Invalid external IPv6 next hop. · Invalid external destination IPv6 address. · Failed to allocate resources, because the specified border device group is not bound to a security egress address pool. · Failed to allocate resources, because the specified border device group is not bound to a firewall management address pool. · Failed to allocate resources, because the specified border device group is not bound to a security egress VLAN pool. · The specified uplink VLAN has been used by another firewall network resource. · The specified uplink VLAN ID is not in the security egress VLAN pool bound to the border device group. · The VLAN specified for the egress network resources and the uplink VLAN specified for the firewall network resources must be different.

Update FW Resource

Keyword	CREATE_FW_RESOURCE_OP
Message text	Updated firewall resource “$1”
Variable fields	$1: Firewall resource configuration.
Example	Updated firewall resource ID: “1c6d3cf4-d622-4121-b193-bfac63a5e409” Management network: Gateway address: Egress VLAN: Egress IPv4 address: Egress IPv6 address:
Explanation	A firewall resource was updated.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · Unknown error. · Invalid JSON format. · The specified resource doesn't exist. · Cannot edit the firewall resource ID. · Cannot edit the firewall management network. · Cannot edit the firewall gateway address. · Cannot edit the firewall egress IPv6 address. · Cannot edit the firewall egress VLAN ID. · The firewall resource has been used by a border gateway.

Delete VFW Resource

Keyword	DELETE_FW_RESOURCE_OP
Message text	Deleted firewall resource “$1”.
Variable fields	$1: Firewall resource ID.
Example	Deleted firewall resource “1c6d3cf4-d622-4121-b193-bfac63a5e409”.Egress IPv6 address:
Explanation	A firewall resource was deleted.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · Unknown error. · The specified resource doesn't exist. · The firewall resource has been used by a border gateway. · Failed to delete the context.

Create GW Member

Keyword	CREATE_GW_MEMBER_OP
Message text	Created gateway member “$1”
Variable fields	$1: Gateway member ID.
Example	Created gateway member “1c6d3cf4-d622-4121-b193-bfac63a5e409”.
Explanation	A gateway member was created.
Possible failure causes	· The specified resource pool does not exist. · The specified resource pool has been used. · The border device group used by the gateway member does not have a member.

Update GW Member

Keyword	UPDATE_GW_MEMBER_OP
Message text	Updated gateway member “ $1”
Variable fields	$1: Gateway member ID.
Example	Updated gateway member “1c6d3cf4-d622-4121-b193-bfac63a5e409”
Explanation	A gateway member was updated.
Possible failure causes	The resource pool cannot be edited.

Create External Interface

Keyword	CREATE_EXTERNAL_INTERFACE_OP
Message text	Created egress interface “$1”.
Variable fields	$1: Egress interface ID.
Example	Created egress interface “1c6d3cf4-d622-4121-b193-bfac63a5e409”
Explanation	An egress interface was created.
Possible failure causes	· The firewall resource does not exist. · The gateway member has not been associated with a resource pool. · The remote IP address and the firewall management address cannot belong to the same network. · The remote IP address and the firewall egress IPv4 address cannot belong to the same network. · The remote IP address and the firewall egress IPv6 address cannot belong to the same network. · The firewall resource has been used. · The egress VLAN of the gateway member's border device group cannot be the same as the firewall egress VLAN of the gateway member. · Failed to allocate resources, because the specified campus egress address pool does not have enough IP addresses. · Failed to allocate resources, because the specified campus egress VLAN pool does not have enough VLAN IDs. · Failed to allocate resources, because the specified border device group is not bound to a campus egress address pool. · Failed to allocate resources, because the specified border device group is not bound to a campus egress VLAN pool. · The specified VLAN has been used by other egress network resources. · The specified VLAN ID is not in the campus egress VLAN pool bound to the border device group. · The VLAN specified for the egress network resources and the uplink VLAN specified for the firewall network resources must be different.

Update External Interface

Keyword	UPDATE_EXTERNAL_INTERFACE_OP
Message text	Updated egress interface “$1”.
Variable fields	$1: Egress interface ID.
Example	Updated egress interface ” 1c6d3cf4-d622-4121-b193-bfac63a5e409”
Explanation	An egress interface was updated.
Possible failure causes	· The firewall resource does not exist. · The gateway member has not been associated with a resource pool. · The firewall resource has been used. · Cannot edit the gateway member. · Cannot edit the firewall resource.

Create Extenal Network

Keyword	CREATE_EXTERNAL_NETWORK_OP
Message text	Created egress network “$1”.
Variable fields	$1: Egress network ID.
Example	Created egress network “1c6d3cf4-d622-4121-b193-bfac63a5e409”
Explanation	An egress network was created.
Possible failure causes	Only border gateways in exclusive mode support firewall resources.

Smooth Asset and Template

Keyword	SMOOTH_CONTEXT_TEMPLATES_OP
Message text	Synchronized asset and firewall resource pool information from security server “$1”.
Variable fields	$1: Security server ID.
Example	Synchronized asset and firewall resource pool information from security server “1c6d3cf4-d622-4121-b193-bfac63a5e409”.
Explanation	The controller synchronized asset and firewall resource information from the security server.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown error. · The security server does not exist. · Failed to connect to the security server. · Failed to synchronize asset data from the security server. · Failed to synchronize the firewall resource pool information from the security server. · Some configuration data was not synchronized. · The sites to which some physical assets belong do not exist.

Create Server Resource

Keyword	CREATE_SERCURITY_SERVERS_OP
Message text	Created security server “$1”.
Variable fields	$1: Security server configuration.
Example	Created security server : ID: Name: IP address: Protocol: Port: Username: Password: ******
Explanation	A security server was created.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · Unknown error. · Invalid JSON format. · The security server ID already exists. · The security server IP address is required. · The security server IP address is invalid. · The security server already exists with the specified IP address. · The security server port number is required. · The security server port number is invalid. · The security server username cannot exceed 255 characters. · The security server username is required. · The security server password cannot exceed 255 characters. · The security server password is required. · The security server protocol can only be HTTPS. · The security server protocol is required. · Only one security server is allowed.

Update Server Resource

Keyword	UPDATE_SERCURITY_SERVERS_OP
Message text	Updated security server “$1”.
Variable fields	$1: Security server configuration.
Example	Updated security server ID: Name: IP address: Protocol: Port: Username: Password: ******
Explanation	A security server was updated.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · Unknown error. · Invalid JSON format. · The security server does not exist. · Cannot edit the security server ID. · Cannot edit the security server protocol. · The security server IP address is required. · The security server IP address is invalid. · The security server already exists with the specified IP address. · The security server port number is required. · The security server port number is invalid. · The security server username cannot exceed 255 characters. · The security server username is required. · The security server password cannot exceed 255 characters. · The security server password is required. · The security server protocol can only be HTTPS. · The security server protocol is required.

Delete Server Resource

Keyword	DELETE_SERCURITY_SERVERS_OP
Message text	Deleted security server “$1”.
Variable fields	$1: Security server ID.
Example	Deleted security server “1c6d3cf4-d622-4121-b193-bfac63a5e409”.
Explanation	A security server was deleted.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · Unknown error. · The specified resource doesn't exist. · The resource pool corresponding to the assets of the security server has been bound to a gateway member and cannot be deleted. · The security server does not exist. · You cannot delete the security server, because the firewall context template of an asset has been bound to a local service resource. · You cannot delete the security server because it has site and physical asset binding.

Create campus full mesh

Keyword	CREATE_CAMPUS_FULL_MESH_OP
Message text	Created campus full mesh: $1
Variable fields	$1: Campus full mesh parameters.
Example	Created campus full mesh: ID: dfbce4db-8e72-4fd4-a659-f6889c709e15 DeviceIdList:“dfbce4db-8e72-4fd4-a659-f6889c709e11”, “dfbce4db-8e72-4fd4-a659-f6889c709e12”
Explanation	A campus full mesh was created.
Possible failure causes	· Invalid campus full mesh ID. · Some devices to be assigned to the campus full mesh have invalid IDs. · Some devices to be assigned to the campus full mesh have duplicate IDs. · A campus full mesh must contain a minimum of two devices. · Some devices to be assigned to the campus full mesh have been assigned to other campus full meshes. · Some of the specified devices do not exist. · The campus interconnect VTEP IP configuration is required for each device to be assigned to the campus full mesh. · The devices to be assigned to the campus full mesh must be added to the same border device group.

Delete campus full mesh

Keyword	DELETE_CAMPUS_FULL_MESH_OP
Message text	Deleted campus full mesh: $1.
Variable fields	$1: Campus full mesh ID.
Example	Deleted campus full mesh dfbce4db-8e72-4fd4-a659-f6889c709e15
Explanation	A campus full mesh was deleted.
Possible failure causes	· The campus full mesh with the specified ID does not exist.

Create auth free template

Keyword	ADD_AUTH_FREE_TEMPLATE_OP
Message text	Added authentication-free policy template “$1:$2”, and bound the template to security group “$3”.
Variable fields	$1: Authentication-free policy template ID. $2: Authentication-free policy template name. $3: Bound security group ID.
Example	Added authentication-free policy template “dfbce4db-8e72-4fd4-a659-f6889c709e15:aaa”, and bound the template to security group “dfbce4db-8e72-4fd4-a659-f6889c709a16”.
Explanation	An authentication-free policy template was created.
Possible failure causes	· Invalid security group ID. · The security group does not exist. · The security group has been bound to another authentication-free policy template. · The authentication-free policy template name is invalid. · The authentication-free policy template type is invalid. · The authentication-free policy template name already exists. · he security group ID has been specified in another authentication-free policy template. · The authentication-free policy template already exists.

Delete auth free template

Keyword	DELETE_AUTH_FREE_TEMPLATE_OP
Message text	Deleted authentication-free policy template $1.
Variable fields	$1: Authentication-free policy template ID.
Example	Deleted authentication-free policy template dfbce4db-8e72-4fd4-a659-f6889c709e15
Explanation	An authentication-free policy template was deleted.
Possible failure causes	· The authentication-free policy template ID is invalid. · The authentication-free policy template already exists.

Create multicast

Keyword	CREATE_MULTICAST_OP
Message text	Created Layer 3 multicast network: $1.
Variable fields	$1:Layer 3 multicast information.
Example	Created multicast: id: 694aae52-b4b3-48a1-9829-6e4ba6673cf5 name: L3 rpAddress: 1.1.1.1 vrouterId: 8c58ad6d-12c0-404d-a968-b98012a1bd29 multicastResources:[ ] mdtConfig: MdtConfig [defaultGroup=224.1.1.1, sourcePort=loopback0, dataGroup=234.1.1.0/24, threshold=25, dataDelay=12, aclId=28f1be1d-cff1-4a81-beda-aeaa331f9adf] pimTemplateConfig: PimTemplateConfig [protocol=PIM-SM, helloInterval=null, helloHoldtime=null, joinPruneInterval=null, joinPruneHoldtime=null, lanDelay=null, overrideInterval=null, passive=false, ssmPolicy=null] pimPolicyConfig: PimPolicyConfig [neighborPolicy=null, joinPolicy=null] igmpTemplateConfig: IgmpTemplateConfig [version=V2, robustCount=null, queryInterval=null, maxResponseTime=null, lastMemberQueryInterval=null, otherQuerierPresent=null, ssmMappingId=null] igmpPolicyConfig: IgmpPolicyConfig [groupPolicy=null].
Explanation	A Layer 3 multicast network was created.
Possible failure causes	· Configuration recovery is in progress. · Invalid JSON format. · The controller is not the active leader. · Unknown internal server error. · Invalid parameter. · The Layer 3 multicast network already exists. · The name is required. · Invalid name. · The private network is required. · The specified private network does not exist. · The private network has not been enabled with multicast. · A Layer 3 multicast network already exists with the specified name. · The private network is being used by another Layer 3 multicast network. · Invalid IP address. · The RP address is required. · Invalid PIM protocol. · Invalid default group. · The data group is required when the default group is null. · Invalid data group. · The switchover delay is out of range. · The ACL does not exist. · The MDT policy must be an advanced ACL. · The SSM multicast group range cannot be configured for the PIM-SM protocol. · The hello interval is out of range. · The hello holdtime is out of range. · The join/prune interval is out of range. · The join/prune holdtime is out of range. · The propagation delay is out of range. · The override interval is out of range. · The SSM policy must be a basic ACL. · The neighbor policy must be a basic ACL. · The join policy must be a basic ACL. · The SSM mapping cannot be configured for IGMPv3. · The IGMP querier’s robustness variable is out of range. · The IGMP query interval is out of range. · The IGMP max response time is out of range. · The IGMP last member query interval is out of range. · The other querier present time is out of range. · The SSM mapping does not exist. · Invalid source port. · Please specify a default group or source port. · If you do not specify a data group, you must leave the switchover delay and multicast policy fields empty. · The default group and data group overlap with each other. · The default group or the data group range cannot overlap with any existing default group or data group range of other Layer 3 multicast networks. · You can specify an SSM mapping only when PIM-SSM and IGMPv3 are used on the Layer 3 multicast network.

Update multicast

Keyword	UPDATE_MULTICAST_OP
Message text	Updated Layer 3 multicast network: $1.
Variable fields	$1:Layer 3 multicast information.
Example	Updated multicast: id: 694aae52-b4b3-48a1-9829-6e4ba6673cf5 name: L3 rpAddress: 1.2.3.4 vrouterId: 8c58ad6d-12c0-404d-a968-b98012a1bd29 multicastResources:[ ] mdtConfig: MdtConfig [defaultGroup=224.11.11.11, sourcePort=loopback0, dataGroup=234.11.11.0/24, threshold=24, dataDelay=1, aclId=5efba02a-5106-46cf-b824-25891546d640] pimTemplateConfig: PimTemplateConfig [protocol=PIM-SM, helloInterval=null, helloHoldtime=null, joinPruneInterval=null, joinPruneHoldtime=null, lanDelay=null, overrideInterval=null, passive=false, ssmPolicy=null] pimPolicyConfig: PimPolicyConfig [neighborPolicy=null, joinPolicy=null] igmpTemplateConfig: IgmpTemplateConfig [version=V2, robustCount=null, queryInterval=null, maxResponseTime=null, lastMemberQueryInterval=null, otherQuerierPresent=null, ssmMappingId=null] igmpPolicyConfig: IgmpPolicyConfig [groupPolicy=null].
Explanation	A Layer 3 multicast network was updated.
Possible failure causes	· Configuration recovery is in progress. · Invalid JSON format. · The controller is not the active leader. · Unknown internal server error. · The ID of the private network cannot be edited. · Invalid IP address. · The RP address is required. · Invalid PIM protocol. · Invalid default group. · The data group is required when the default group is null. · Invalid data group. · The switchover delay is out of range. · The ACL does not exist. · The MDT policy must be an advanced ACL. · The SSM multicast group range cannot be configured for the PIM-SM protocol. · The hello interval is out of range. · The hello holdtime is out of range. · The join/prune interval is out of range. · The join/prune holdtime is out of range. · The propagation delay is out of range. · The override interval is out of range. · The SSM policy must be a basic ACL. · The neighbor policy must a basic ACL. · The join policy must a basic ACL. · Invalid IGMP version. · The SSM mapping cannot be configured for IGMPv3. · The IGMP querier’s robustness variable is out of range. · The IGMP query interval is out of range. · The IGMP max response time is out of range. · The IGMP last member query interval is out of range. · The other querier present time is out of range. · The SSM mapping does not exist. · The default group and data group overlap with each other. · The Layer 3 multicast network does not exist. · The name of the Layer 3 multicast network cannot be edited. · Invalid source port. · Please specify a default group or source port. · If you do not specify a data group, you must leave the switchover delay and multicast policy fields empty. · The specified PIM protocol must be the same as the PIM protocol used by the Layer 3 multicast network bound to the private network of the multicast source. · The default group or the data group range cannot overlap with any existing default group or data group range of other Layer 3 multicast networks. · You can specify an SSM mapping only when PIM-SSM and IGMPv3 are used on the Layer 3 multicast network.

Delete multicast

Keyword	DELETE_MULTICAST_OP
Message text	Deleted Layer 3 multicast network: $1.
Variable fields	$1:UUID of the Layer 3 multicast
Example	Deleted multicast: 694aae52-b4b3-48a1-9829-6e4ba6673cf5.
Explanation	A Layer 3 multicast network was deleted.
Possible failure causes	· Configuration recovery is in progress. · Invalid license. · The controller is not the active leader. · Unknown internal server error. · Invalid parameter. · The private network is used by a multicast source.

Create ACL

Keyword	CREATE_ACL_OP
Message text	Created ACL: $1.
Variable fields	$1:ACL information.
Example	Added acl:MulticastAcl [id=5efba02a-5106-46cf-b824-25891546d640, name=acl_high1, desc=null, aclType=ADVANCED, aclRules=[]].
Explanation	An ACL was created.
Possible failure causes	· Configuration recovery is in progress. · Invalid JSON format. · The controller is not the active leader. · Unknown internal server error. · Invalid ACL name. · An ACL already exists with the specified name. · Invalid description.

Delete ACL

Keyword	DELETE_ACL_OP
Message text	Deleted ACL: $1.
Variable fields	$1:UUID of the ACL
Example	Deleted ACL: ab498204-5a8d-46cd-b4af-e1740fc2c374.
Explanation	An ACL was deleted.
Possible failure causes	· Configuration recovery is in progress. · Invalid license. · The controller is not the active leader. · Unknown internal server error. · Failed to delete the ACL because it is being used.

Create ACL rule

Keyword	CREATE_ACL_RULE_OP
Message text	Created ACL rule: $1.
Variable fields	$1:ACL rule information.
Example	Create ACL rule:[MulticastAclRule{id=ab498204-5a8d-46cd-b4af-e1740fc2c374, aclId=5efba02a-5106-46cf-b824-25891546d640, sourceIP='192.168.2.2', destinationIP='192.158.2.2', action=PERMIT}]5.
Explanation	An ACL rule was created.
Possible failure causes	· Configuration recovery is in progress. · Invalid JSON format. · The controller is not the active leader. · Unknown internal server error. · The ACL with the specified ID does not exist. · An ACL already exists with the specified name. · The IDs for different ACLs must be different. · Invalid source IP address. · Invalid destination IP address. · The specified ACL rule already exists. · The specified ACL rule conflicts with an existing rule. · The ACL rule list contains duplicated rules. · An ACL can have a maximum of 1000 rules.

Delete ACL rule

Keyword	DELETE_ACL_RULE_OP
Message text	Deleted ACL rule: $1.
Variable fields	$1:UUID of the ACL rule.
Example	Deleted ACL: ab498204-5a8d-46cd-b4af-e1740fc2c374.
Explanation	An ACL rule was deleted.
Possible failure causes	· Configuration recovery is in progress. · Invalid license. · The controller is not the active leader. · Unknown internal server error.

Create SSM mapping

Keyword	CREATE_SSM_MAPPING_OP
Message text	Created SSM mapping: $1.
Variable fields	$1:SSM mapping information.
Example	Created SSM mapping: ID:[178d9370-884a-4538-b75b-51b0a42ffaf5] Name:[ssm_maapping1] Desc:[].
Explanation	A SSM mapping was created.
Possible failure causes	· Configuration recovery is in progress. · Invalid JSON format. · The controller is not the active leader. · Unknown internal server error. · Invalid SSM mapping name. · An SSM mapping already exists with the specified name. · Invalid description.

Delete SSM mapping

Keyword	DELETE_SSM_MAPPING_OP
Message text	Deleted SSM mapping: $1.
Variable fields	$1:UUID of the SSM mapping.
Example	Deleted SSM mapping: 178d9370-884a-4538-b75b-51b0a42ffaf5.
Explanation	A SSM mapping rule was deleted.
Possible failure causes	· Configuration recovery is in progress. · Invalid license. · The controller is not the active leader. · Unknown internal server error. · Failed to delete the SSM mapping because it is being used.

Create SSM mapping rule

Keyword	CREATE_SSM_MAPPING_RULE_OP
Message text	Created SSM mapping rule: $1.
Variable fields	$1:SSM mapping rule information.
Example	Created SSM mapping rule:[ ID:[d96b4ede-1781-43f0-8de2-01fb07e78c6a] ssmMappingId:[178d9370-884a-4538-b75b-51b0a42ffaf5] SourceIp:[192.168.10.10] GroupIp:[225.1.1.0/24]].
Explanation	A SSM mapping rule was created.
Possible failure causes	· Configuration recovery is in progress. · Invalid JSON format. · The controller is not the active leader. · Unknown internal server error. · The SSM mapping does not exist. · Invalid source IP address. · Invalid multicast group address. · The SSM mapping rule already exists. · The SSM mapping rule list contains duplicated rules.

Delete SSM mapping rule

Keyword	DELETE_SSM_MAPPING_RULE_OP
Message text	Deleted SSM mapping rule: $1.
Variable fields	$1:UUID of the SSM mapping rule.
Example	Deleted SSM mapping rule: 178d9370-884a-4538-b75b-51b0a42ffaf5.
Explanation	A SSM mapping rule was deleted.
Possible failure causes	· Configuration recovery is in progress. · Invalid license. · The controller is not the active leader. · Unknown internal server error.

Create Network Range

Keyword	CREATE_NETWORK_GROUP_OP
Message text	Created network range:NetworkRangeConfig “$1”.
Variable fields	$1:Network range information.
Example	Created network range:NetworkRangeConfig [id=971ee53c-6a54-481a-8f0f-971c51d35650, fabricId=ee399d42-02a2-4897-b395-0be4b2e2f6de, fabricName=fa, generalGroupId=e455e23d-73ca-4c86-a9d3-089bf3c782b4, generalGroupName=sss, vxlanId=5, vlan=2809, isoId=c936547b-c4ae-4cc2-aa34-0d06ef767a08]
Explanation	A network range was created.
Possible failure causes	· Invalid JSON format. · The static access interface group has been bound to another network range . · A network range already exists with the specified ID. · The fabric does not exist. · The fabric ID and the fabric name do not match. · The specified interface group does not exist . · Incorrect interface group subtype. · The interface group ID and the interface group name do not match. · The specified Layer 2 network domain does not exist. · The specified VLAN has already been used. · Failed to allocate the specified VLAN. · The VLAN pool has been exhausted. · Invalid VLAN ID. · No scenario is specified for the network range：未指定网络范围的场景 · Invalid network range scenario：无效的网络范围场景 · Some interfaces in the specified static access interface group are in the static access interface group specified for another network range：该网络范围使用的静态接入接口组中的接口已被其他网络范围使用 · The interface has been used by a static access interface group and a network range for wired scenario：该接口已被静态接入接口组和有线场景的网络范围使用 · The interface has been used by a static access interface group and a network range for wireless scenario：该接口已被静态接入接口组和无线场景的网络范围使用

Delete Network Range

Keyword	DELETE_NETWORK_GROUP_OP
Message text	Deleted network range $1.
Variable fields	$1：Network range ID
Example	Deleted network range:971ee53c-6a54-481a-8f0f-971c51d35650
Explanation	A network range was deleted.
Possible failure causes	无

Create Device_websocket info

Keyword	CREATE_ DEVICEWEBSOCKETINFO_OP
Message text	Create device websocket source: $1
Variable fields	$1: Device WebSocket configuration.
Example	Create device WebSocket source:[DeviceWebsocketConfig [deviceId=c4f05b09-e1a1-4ab8-a824-ce020c7be085, serverType=LOCAL_UCENTER, sources=[EIA]]]
Explanation	A user subscribed to the device on the EIA authentication server, and the controller deployed the WebSocket server configuration.
Possible failure causes	Invalid JSON format. The NE doesn't exist. Please specify a source. Invalid sources. Invalid server ip. The websoket server ip is conflict with exited one

Delete Device_websocket info

Keyword	DELETE_ DEVICEWEBSOCKETINFO_OP
Message text	Delete device websocket source: $1
Variable fields	$1: Device WebSocket configuration.
Example	Delete device WebSocket source:[DeviceWebsocketConfig [deviceId=c4f05b09-e1a1-4ab8-a824-ce020c7be085, serverType=LOCAL_UCENTER, sources=[EIA]]]
Explanation	A user unsubscribed from the device on the EIA authentication server, and the controller deleted the WebSocket server configuration.
Possible failure causes	Invalid JSON forma. Please specify a source. Invalid sources. The websoket server ip is conflict with exited one.

Create SGT Pools

Keyword	ACTION_ADD_SGTPOOL_OP
Message text	Created SGT pool: $1
Variable fields	$1: SGT Pool information.
Example	Created SGT pool: ID: [218b5f2f-e435-4365-a1ab-0eaa03b7fa19] Name: [table], Type:”default_resource_group” Ranges: [ {15001,15300} ]
Explanation	A SGT Pool 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. · Unknown internal server error. · SGT pool UUIDs are duplicate. · An SGT pool already exists with the specified UUID. · SGT pool names are duplicate. · Please specify an SGT pool name. · An SGT pool name cannot exceed 255 characters. · An SGT pool already exists with the specified name. · The specified SGT pool does not exist. · SGT ranges in the SGT pool overlap. · Invalid SGT range in the SGT pool.

Update SGT Pools

Keyword	ACTION_MOD_SGTPOOL_OP
Message text	Updated SGT_Pools
Variable fields	$1: SGT Pools information.
Example	Updated SGT pool: Ranges: [ {15001,15300} ]
Explanation	A SGT pool 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. · Unknown internal server error. · The specified SGT pool does not exist. · Invalid SGT range in the SGT pool. · SGT ranges in the SGT pool overlap. · The SGT pool is in use and cannot be edited. · A security subgroup already exists with the specified SGT ID

Delete SGT Pools

Keyword	ACTION_DEL_SGTPOOL_OP
Message text	Deleted SGT Pools ID: $1
Variable fields	$1: SGT Pool ID.
Example	Deleted SGT Pool: ID: [e7137b75-0fbb-4f66-9b88-6345d63da951]
Explanation	A SGT Pool 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. · Unknown internal server error.

Add Auth Config

Keyword	ADD_AUTH_CONFIG_OP
Message text	Add Auth Config: $1
Variable fields	$1: Auth Configuration.
Example	Add Auth Config:{"auth_configs":[{"device_id":"1e8e21fe-8b26-4c5d-99f7-ac996a0b2b10","dot1x_auth":true,"authentication_method":"PAP","mac_auth":true,"portal_auth":true,"server_name":"sdn","secret_key":"c2RuMTIzMTIz","redirect_url":"http://1.htm","server_ip":"1.1.1.1","redirect_port":""}]}
Explanation	Several auth configs were 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. · Make sure the global authentication configuration ID is unique. · Please specify a device ID. · Make sure the device ID is unique. · The authentication configuration already exists. · The device does not exist. · The device({{deviceName}}) already has authentication settings. · Please specify the authentication method when 802.1X authentication is enabled. · The port number must be in the range of 1 to 65535. · The portal server name cannot exceed 32 characters. · Portal server IP address is required. · The IP address of the portal server is invalid. · Portal server secret key is required. · The portal server secret key cannot exceed 64 characters. · Portal server redirect URL is required. · The portal server redirect URL cannot exceed 256 characters. · An AC device does not support portal authentication settings. · An AC device only support dot1x authentication EAP method.

Update Auth Config

Keyword	UPD_AUTH_CONFIG_OP
Message text	Upd Auth Config: $1
Variable fields	$1: Auth Configuration.
Example	Upd Auth Config:{"auth_config":{"dot1x_auth":false,"authentication_method":null,"mac_auth":true,"portal_auth":true,"redirect_url":"http://1.htm","server_ip":"1.1.1.1","redirect_port":null}}1.htm","server_ip":"1.1.1.1","redirect_port":""}]}
Explanation	An auth config 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. · Invalid global authentication configuration ID. · The authentication configuration does not exist. · You cannot edit the global authentication configuration ID. · You cannot edit the device ID. · You cannot edit the tenant ID. · You cannot edit the portal server name. · Please specify the authentication method when 802.1X authentication is enabled., · The port number must be in the range of 1 to 65535, · The portal server name cannot exceed 32 characters., · Portal server IP address is required, · The IP address of the portal server is invalid., · server secret key is required., · The portal server secret key cannot exceed 64 characters., · Portal server redirect URL is required, · The portal server redirect URL cannot exceed 256 characters,

Delete Auth Config

Keyword	DEL_AUTH_CONFIG_OP
Message text	Del Auth Config:ID: $1
Variable fields	$1: Auth Configuration ID.
Example	Del Auth Config: ID:[db467522-e530-4af7-a26c-c5a817daf6af] device_id:[43393f37-0924-4375-8bb2-7dd9de8ea311]
Explanation	A auth config 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 authentication configuration does not exist.

Add Inter Auth Config

Keyword	ADD_INTER_AUTH_CONFIG_OP
Message text	Add inter auth config: $1
Variable fields	$1:Inter Auth Configuration.
Example	Add inter auth config:{"interface_list":[{"device_id":"1e8e21fe-8b26-4c5d-99f7-ac996a0b2b10","ifname":"GigabitEthernet1/0/14","auth_config":{"dot1x_enable":true,"dot1x_guest":false,"dot1x_guest_vlan":"102","dot1x_critical":false,"dot1x_critical_vlan":"103","dot1x_authfail":false,"dot1x_authfail_vlan":"101","dot1x_unicast":true,"mac_enable":false,"mac_domain":"","mac_critical":false,"mac_critical_vlan":"","mac_authorder":false,"portal_enable":false,"portal_isp":null,"portal_baseip":"","portal_master_server":""}}]}
Explanation	Several inter auth configs were 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. · Invalid interface authentication parameters. · The interface information cannot be null. · Invalid device ID. · The device does not exist. · The interface name is illegal. · A cloud-managed AP does not support authentication settings on interfaces. · The port auth config is not configured. · Interface authentication is not enabled. · If portal authentication has been configured, you cannot configure 802.1X or MAC authentication, and vice versa. · Enabling guest must also enable unicast triggering. · Invalid auth-fail VLAN for 802.1X authentication. · Invalid guest VLAN for 802.1X authentication. · Invalid critical VLAN for 802.1X authentication. · Invalid critical VLAN for MAC authentication. · Invalid ISP domain name length for MAC or portal authentication. · Invalid ISP domain name for MAC or portal authentication. · Invalid bas-ip in the Portal authentication. · Invalid portal server name in the Portal authentication.

Update Inter Auth Config

Keyword	UPD_INTER_AUTH_CONFIG_OP
Message text	Upd interface authen Config: $1
Variable fields	$1: Inter Auth Configuration.
Example	Upd interface authen Config:{"interface_info":{"device_id":"1e8e21fe-8b26-4c5d-99f7-ac996a0b2b10","ifname":"GigabitEthernet1/0/14","auth_config":{"dot1x_enable":false,"dot1x_guest":false,"dot1x_guest_vlan":null,"dot1x_critical":false,"dot1x_critical_vlan":null,"dot1x_unicast":true,"dot1x_authfail":false,"dot1x_authfail_vlan":null,"mac_enable":true,"mac_domain":"123","mac_critical":false,"mac_critical_vlan":null,"mac_authorder":true,"portal_enable":false,"portal_isp":null,"portal_baseip":null,"portal_master_server":null}}}
Explanation	An inter auth config 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 interface configuration does not exist. · The interface information cannot be null. · : Invalid device ID. · The device does not exist. · The interface name is illegal. · A cloud-managed AP does not support authentication settings on interfaces. · The port auth config is not configured. · Interface authentication is not enabled. · If portal authentication has been configured, you cannot configure 802.1X or MAC authentication, and vice versa. · Enabling guest must also enable unicast triggering. · Invalid auth-fail VLAN for 802.1X authentication. · Invalid guest VLAN for 802.1X authentication. · Invalid critical VLAN for 802.1X authentication. · Invalid critical VLAN for MAC authentication. · Invalid ISP domain name length for MAC or portal authentication. · Invalid ISP domain name for MAC or portal authentication. · Invalid bas-ip in the Portal authentication. · Invalid portal server name in the Portal authentication.

Delete Inter Auth Config

Keyword	UPD_INTER_AUTH_CONFIG_OP
Message text	Del Auth Config:ID: $1
Variable fields	$1: Auth Configuration ID.
Example	Del Auth Config: ID:[db467522-e530-4af7-a26c-c5a817daf6af] device_id:[43393f37-0924-4375-8bb2-7dd9de8ea311]
Explanation	A auth config 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 authentication configuration does not exist.

Add Interface_isolate

Keyword	ADD_DEVICE_INTERFACE_ISOLATE_OP
Message text	Add interface isolate: $1
Variable fields	$1: Device Interface Isolate configuration.
Example	Add interface isolate： { "interface_list": [ { "device_id": "8d4957fd-dff3-4129-a99c-dd8e7319ca98", "ifname": "GigabitEthernet1/2/0/5", "isolate_group":1 }, { "device_id": "8d4957fd-dff3-4129-a99c-dd8e7319ca98", "ifname": "GigabitEthernet1/2/0/6", "isolate_group":2 } ] }
Explanation	The operator configured port isolation on the port isolation page, and the controller deployed port isolation configuration to the selected device
Possible failure causes	Invalid JSON format. No response from the server. Invalid interface name. The group ID must be an integer in the range of 1 to 8. Please specify a device ID. Interface (ifName) on device (deviceName) has been configured with settings above.

Update Interface_isolate

Keyword	MOD_DEVICE_INTERFACE_ISOLATE_OP
Message text	Mod interface isolate: $1
Variable fields	$1: Device Interface Isolate configuration.
Example	Update interface isolate： { "device_id": "8d4957fd-dff3-4129-a99c-dd8e7319ca98", "ifname": "GigabitEthernet1/2/0/5", "isolate_group":1 }
Explanation	The operator edited port isolation configuration on the port isolation page, and the controller updated port isolation configuration on the selected device
Possible failure causes	Invalid JSON format. No response from the server. Invalid interface name. The group ID must be an integer in the range of 1 to 8. Please specify a device ID. The port does not have isolation configuration.

Delete Interface_isolate

Keyword	DEL_DEVICE_INTERFACE_ISOLATE_OP
Message text	Delete interface isolate: $1
Variable fields	$1: Device Interface Isolate configuration.
Example	Delete interface isolate： { "interface_list": [ { "device_id": "8d4957fd-dff3-4129-a99c-dd8e7319ca98", "ifname": "GigabitEthernet1/2/0/5", "isolate_group":1 }, { "device_id": "8d4957fd-dff3-4129-a99c-dd8e7319ca98", "ifname": "GigabitEthernet1/2/0/6", "isolate_group":2 } ] }
Explanation	The operator deleted port isolation configuration on the port isolation page, and the controller deleted port isolation configuration from the selected device
Possible failure causes	Invalid JSON format. No response from the server. Invalid interface name. The group ID must be an integer in the range of 1 to 8. Please specify a device ID.

Add bras interconnect fabric

Keyword	ADD_BRAS_INTERCONNECT_FABRIC_OP
Message text	Add bras interconnect fabric:: $1
Variable fields	$1: Bras interconnect fabric information.
Example	Add bras interconnect fabric : {device Id:62e15112-5cc0-4f4f-8943-b3ffe5368a6a fabric Id:bfc581c7-5dfd-41d5-91c8-952561bf8ebb [{bras_ipv4:5.6.6.6, bras_ipv6:2001:0DB8::2202}]}
Explanation	A bras interconnect fabric was created.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · Unknown internal server error. · A BRAS-fabric binding already exists with the specified ID. · The fabric does not exist. · Some of the specified devices do not exist. · Invalid IP address. · Colon hexadecimal notation. Only global unicast addresses are supported. · The fabric already exists. Please specify another one. · This fabric has been specified for another BRAS device. · The IPv4 address for the fabric interconnect interface is used by another BRAS. · The IPv6 address for the fabric interconnect interface is used by another BRAS. · Fabric You cannot specify a fabric of the VLAN network type.

Update bras interconnect fabric

Keyword	UPDATE_BRAS_INTERCONNECT_FABRIC_OP
Message text	Update bras interconnect fabric:: $1
Variable fields	$1: Bras interconnect fabric information.
Example	Add bras interconnect fabric : {device Id:62e15112-5cc0-4f4f-8943-b3ffe5368a6a fabric Id:bfc581c7-5dfd-41d5-91c8-952561bf8ebb [{bras_ipv4:5.6.6.6, bras_ipv6:2001:0DB8::2202}]}
Explanation	A bras interconnect fabric was modified.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · Unknown internal server error. · A BRAS-fabric binding already exists with the specified ID. · The fabric does not exist. · Some of the specified devices do not exist. · Invalid IP address. · Colon hexadecimal notation. Only global unicast addresses are supported. · The fabric already exists. Please specify another one. · This fabric has been specified for another BRAS device. · The IPv4 address for the fabric interconnect interface is used by another BRAS. · The IPv6 address for the fabric interconnect interface is used by another BRAS. · Fabric You cannot specify a fabric of the VLAN network type.

RCAM

This section contains RCAM messages.

Create resource access template

Keyword	CREATE_RESOURCETEMPLATE_OP
Message text	Created resource access template: $1.
Variable fields	$1：Resource access template information
Example	Created resource access template: id:[f5379427-250d-4f2c-b0fa-cc9c3d58f35f] name:[ss3] ipPoolId:[1822301b-e3d2-40ff-bad9-fdfaf9f1e49e] rsTemplateId:[c81e728d-9d4c-3f63-af06-7f89cc14862c] rsTemplateName:[context2] rsTemplateType:[NGFW] ingressIpPoolId:[3d9179d9-0b49-4eec-a44b-333438cbf956] egressIpPoolId:[3d9179d9-0b49-4eec-a44b-333438cbf956] ingressVlanPoolId:[7bc013f7-ba6a-4b92-b75f-857311f46752] egressVlanPoolId:[7bc013f7-ba6a-4b92-b75f-857311f46752] accessDevice:[ deviceId:[8dc52ab4-9fe1-4e89-b672-098c32bcc5b3] ingressPort:[GigabitEthernet1/0/2] egressPort:[GigabitEthernet1/0/4]]
Explanation	A resource access template was created.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · The ingress port isn't the downlink port of the access device. · The egress port isn't the downlink port of the access device. · The specified access device doesn't exists. · The IP pool doesn't exists. · The attached network already exists.. · The number of attached networks cannot exceed 16. · The firewall context template has been used by a gateway member. · The specified service chain node inbound address pool does not exist. · The specified service chain node inbound VLAN pool does not exist. · The specified service chain node outbound address pool does not exist. · The specified service chain node outbound VLAN pool does not exist.

Delete resource access template

Keyword	DELETE_RESOURCETEMPLATE_OP
Message text	Deleted resource access template: $1.
Variable fields	$1：Resource access template UUID
Example	Deleted resource access template: 7fda0d76-9a0a-4129-bc53-31e3b215f854.
Explanation	A resource access template was deleted.
Possible failure causes	· The resource access template doesn't exist. · Configuration recovery is in progress. · The controller is not the active leader. · The context template has been used by a service resource.

ServiceChain

This section contains service chain messages.

Create service chain

Keyword	CREATE_GRAPH_OP
Message text	Created graph $1
Variable fields	$1: Service chain information.
Example	Created graph id: 9d90aa89-ba67-4ed0-91e3-94552b596ad4 name: chain_ tenant id: f491313b-1f53-4b57-b73f-c037d375deff tenant name: isolate_domain1 service nodes: type: PBR_FW service id: c856678b-640e-4c53-a89e-c845e33a3105 provider id: e0910ac2-c263-4815-873b-c2ec44bbf558 resource id: 9ac924bc-8e83-4692-9aa7-ee80ee69cf37 management ip: 192.168.159.66 service name: fw1 vip : [] rip : [] servie path id: 1
Explanation	A service chain was created.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · The name cannot contain spaces. · Invalid service type. · The service instance doesn't exist. · The firewall of the service node does not exist. · Only firewalls in service chain mode are supported. · A service instance of the Third-party type cannot form a service chain with service instances of other types. · A service chain can contain a maximum of 16 third-party service instances. · Duplicated service instances exist in the service chain. · The service chain already has a PBR_FW service instance. You cannot specify any other types of service instances for the service chain. · You can specify a maximum of 16 PBR_FW service instances for a service chain. · Duplicated service instances exist in the service chain. · The service instance is already used by another service chain. · The service chain already exists. · Failed to add the configuration item. · Make sure the PBR_FW service instance has been bound to a firewall. · The number of virtual service nodes exceeds the license limit. · One or more selected third-party service instances are invalid. · Third-party service instances of a service chain must belong to different virtual link layer networks. · Third-party service instances of a service chain must be bound to the same vRouter. · Third-party service instances bound to the same vRouter must belong to the same service chain. · Unknown internal service error. · The service is disabled. · The access device is belong to different vds. · Please specify a VDS for the fabric of the access device in the resource access template bound to the service instance. · The specified service chain node inbound address pool does not exist. · The specified service chain node inbound address pool does not have enough IP addresses. · The specified service chain node inbound address pool does not have enough IP addresses. · The specified service chain node inbound address pool does not exist. · The specified service chain node inbound VLAN pool does not exist. · The specified service chain node inbound VLAN pool does not have enough VLAN IDs. · The specified service chain node outbound address pool does not exist. · The specified service chain node outbound address pool does not have enough IP addresses. · The specified service chain node outbound VLAN pool does not exist. · The specified service chain node outbound VLAN pool does not have enough VLAN IDs. · Make sure all service nodes on the service chain are in the same isolation domain.

Update service chain

Keyword	UPDATE_GRAPH_OP
Message text	Updated graph $1
Variable fields	$1: Service chain information.
Example	Updated graph id: 9d90aa89-ba67-4ed0-91e3-94552b596ad4 name: chain_ tenant id: f491313b-1f53-4b57-b73f-c037d375deff tenant name: isolate_domain1 service nodes: type: PBR_FW service id: c856678b-640e-4c53-a89e-c845e33a3105 provider id: e0910ac2-c263-4815-873b-c2ec44bbf558 resource id: 9ac924bc-8e83-4692-9aa7-ee80ee69cf37 management ip: 192.168.159.66 service name: fw1 vip : [] rip : [] servie path id: 1
Explanation	A service chain was modified.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · The configuration item doesn't exist. · Invalid service type. · The service instance doesn't exist. · The firewall of the service node does not exist. · Only firewalls in service chain mode are supported. · A service instance of the Third-party type cannot form a service chain with service instances of other types. · A service chain can contain a maximum of 16 third-party service instances. · Duplicated service instances exist in the service chain. · The service chain already has a PBR_FW service instance. You cannot specify any other types of service instances for the service chain. · You can specify a maximum of 16 PBR_FW service instances for a service chain. · Duplicated service instances exist in the service chain. · The service instance is already used by another service chain. · Policy mode differs between the private networks bound to the security group and the service chain. · Make sure the PBR_FW service instance has been bound to a firewall. · The number of virtual service nodes exceeds the license limit. · One or more selected third-party service instances are invalid. · Third-party service instances of a service chain must belong to different virtual link layer networks. · Third-party service instances of a service chain must be bound to the same vRouter. · Third-party service instances bound to the same vRouter must belong to the same service chain. · Resource template doesn't exist. · Unknown internal service error. · Failed to modify the configuration item. · The specified service chain node inbound address pool does not have enough IP addresses. · The specified service chain node inbound address pool does not exist. · The specified service chain node inbound VLAN pool does not exist. · The specified service chain node inbound VLAN pool does not have enough VLAN IDs. · The specified service chain node outbound address pool does not exist. · The specified service chain node outbound address pool does not have enough IP addresses. · The specified service chain node outbound VLAN pool does not exist. · The specified service chain node outbound VLAN pool does not have enough VLAN IDs. · You cannot change the type of a node in the service chain between third-party and firewall. · Make sure all service nodes on the service chain are in the same isolation domain.

Delete service chain

Keyword	DELETE_GRAPH_OP
Message text	Deleted graph chain $1
Variable fields	$1: Service chain UUID.
Example	Deleted service chain 7fda0d76-9a0a-4129-bc53-31e3b215f854
Explanation	A service chain was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · The configuration item doesn't exist. · The service chain is refered. · The service chain has been used by a redirection rule and cannot be deleted. · Failed to delete the configuration item.

SITE

This section contains SITE messages.

Create Site table

Keyword	CREATE_SITE_OP
Message text	Created Site table: $1
Variable fields	$1：Site table
Example	Created Site table: parentId : [edfed45a-d3a9-4bb0-bfe3-b5fe5c2c9018] name: [hangzhou site1] xaxis: [100] yaxis: [50] description: [hangzhou xihu]
Explanation	A site 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. · Unknown error. · The request is invalid. · The specified resource doesn't exist. · Site id already exist. · Site id and parent id can't be the same. · Site name should not be null. · Site name cannot exceed 255 characters. · Site name already exist. · This site name not allowed following characters. · Site description cannot exceed 255 characters. · Site longitude should not be null. · Site longitude must be number and in the range of -180 to 180. · Site latitude should not be null. · Site latitude must be number and in the range of -90 to 90. · Fail to create site,because collect site data is doing in smooth.

Update Site table

Keyword	UPDATE_SITE_OP
Message text	Updated Site table: $1
Variable fields	$1：Site table
Example	Updated Site: parentId : [edfed45a-d3a9-4bb0-bfe3-b5fe5c2c9018] name: [hangzhou site1] xaxis: [100] yaxis: [50] description: [hangzhou xihu]
Explanation	A site 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. · Unknown error. · The request is invalid. · The specified resource doesn't exist. · Site id already exis. · Site id and parent id can't be the same. · Site name should not be null. · Site name cannot exceed 255 characters. · Failed to edit the site. The specified parent site is a descendant site of the current site. · Site name already exist. · This site name not allowed following characters. · Site description cannot exceed 255 characters. · Site longitude should not be null. · Site longitude must be number and in the range of -180 to 180. · Site latitude should not be null. · Site latitude must be number and in the range of -90 to 90.

Delete Site table

Keyword	DELETE_SITE_OP
Message text	Deleted VLAN-VXLAN mapping table: ID: $1
Variable fields	$1：Site table
Example	Deleted Site table: ID: [edfed45a-d3a9-4bb0-bfe3-b55c2c9018]
Explanation	A site 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. · Unknown error. · The request is invalid. · The specified resource doesn't exist. · Failed to delete the site because of security server connection error. · Failed to delete the site, because the site has physical assets. · The site still has child site. · Fail to delete site,because collect site data is doing in smooth. · This site cannot be deleted, because it contains physical assets

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. · Configuration recovery is in progress. · The VDS name already exists. · VDSs created in bulk cannot use the same ID. · The bridge name cannot exceed 255 characters. · The VXLAN tunnel name cannot exceed 255 characters. · The length of the automatically generated VXLAN tunnel name exceeds the limit. · The bridge name already exists. · The VXLAN tunnel name already exists. · The openflow hard 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 VDS name and the bridge name cannot both be null. · The VDS already exists. · The VXLAN ID range is required. · The number of VXLAN ID digits in VSI interface name is invalid. · The VDS name cannot exceed 62 characters. · Unknown error. · The selected fabrics must be configured with the same policy mode as the isolation domain.

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. · Configuration recovery is in progress. · Cannot modify the bridge name because the VDS has been bound to a domain. · Cannot modify the VXLAN range because the VXLAN range after modification does not contain VXLAN IDs being used. · Cannot modify the VXLAN tunnel interface name because the VDS has been bound to a domain. · Cannot modify the global virtual MAC address because the VDS has virtual link layer networks. · The value of the vswitch_flood_and_learn field is invalid. · The VDS ID is required. · The VDS name already exists. · The bridge name already exists. · The VXLAN tunnel name already exists. · The bridge name cannot exceed 255 characters. · The VXLAN tunnel name cannot exceed 255 characters. · The openflow hard 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 default VDS name. · Can't modify the number of VXLAN ID digits in VSI interface name. · The bridge name is required. · The VXLAN tunnel name is required. · The parameter (parameters) can't be modified. · The VDS name cannot exceed 62 characters. · The backup_link_enable is required. · The lldp_to_controller is required. · Unknown error. · The selected fabrics must be configured with the same policy mode as the isolation domain.

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. · 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. · Cannot delete the VDS because it has fabrics. · 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. · Configuration recovery is in progress. · Invalid IP address. · Cannot add the host because no available regions exist. · The UUID already exists. · Failed to add the host because the domain type is vCenter. · The bridge of the host does not match any bridges of VDSs bound to the domain to which the host belongs. · Unknown error. · Number of CPUs that can be managed is insufficient. Please purchase a new license or expand the old one. · The domain doesn't exist. · The request is invalid. · No available IP addresses in the VTEP IP address pool. · Host host, parameter is required. · The host type and the domain type do not match. · The host name cannot exceed 255 characters. · The IP address is already used. · No VDS exists in the domain. · The bridge configuration is invalid. · Bridges on the same host cannot use the same name. · You can select a fabric for a host only from fabrics of VDSs in the domain to which the host belongs.

Update host

Keyword	UPDATE_HOST_OP
Message text	Updated host “$1”.
Variable fields	$1: IP address of the host.
Example	Updated host “1.1.1.1”.
Explanation	A host was modified.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Failed to add the host because the domain type is vCenter. · The bridge of the host does not match any bridges of VDSs bound to the domain to which the host belongs. · Invalid IP address. · The domain doesn't exist. · The request is invalid. · Unknown error. · No available IP addresses in the VTEP IP address pool. · Host host, parameter is required. · 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. · No VDS exists in the domain. · The bridge configuration is invalid. · The IP address and UUID cannot both be null. · The IP address and UUID do not match. · Bridges on the same host cannot use the same name. · You can select a fabric for a host only from fabrics of VDSs in the domain to which the host belongs.

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. · 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_ROUTE_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. · Configuration recovery is in progress. · Invalid tenant ID. · The router ID is already used. · vRouters created in bulk cannot use the same ID. · The router is required. · The is_bind_gw field is a read-only field. · The segment ID is already used. · The segment ID is out of range. · Invalid routing table. · The VDS doesn't exist. · The VPN name is already used. · The AS number is required. · The value for the maximum number of ECMP routes is invalid. · Invalid summary route network. · The IPv4 address of the peer is required. · Invalid CIDR. · The CIDR overlaps with another CIDR. · The IPv4 address of the peer is invalid. · The AS number of the peer is invalid. · The vRouter can not be configured with the same summary route network. · The vRouters using the public VRF can not be bound to the same service gateway group. · The specified device doesn't exist. · The device ID and the device name do not match. · The BGP peer already exists. · The vRouter name cannot exceed 255 characters. · The VPN name cannot exceed 31 characters. · The specified tenant doesn't exist. · Failed to add the vRouter because the number of vRouters has reached the limit. · The specified tenant doesn't bind VDS. · The VDS of the vRouter is different than the tenant. · Unknown error.

Update vRouter

Keyword	UPDATE_ROUTE_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. · Configuration recovery is in progress. · The subnet and the router are not in the same VDS. · 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. · For vRouters bound to a service gateway group to share an external IP address, these vRouter must be bound to the same gateway service resource. · The vRouters to which the sharing IP belongs must have been bound to a gateway. · For vRouters bound to a service gateway group to share an external IP address, these vRouter must be bound to a gateway service resource. · The IP address is already used by another port. · Invalid routing table. · The segment ID is already used. · The segment ID is out of range. · The AS number is required. · The value for the maximum number of ECMP routes is invalid. · Invalid summary route network. · The ID of the routing table is different than the vRouter. · The IPv4 address of the peer is required. · Invalid CIDR. · The IPv4 address of the peer is invalid. · The AS number of the peer is invalid. · The is_bind_gw field is a read-only field. · The subnet overlaps with another subnet. · The subnet must belong to the specified network. · The CIDR overlaps with another CIDR. · Failed to bind the vRouter to an external 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 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 doesn't exist. · The extranet IP has been used by another gateway resource. · The vRouter can not be configured with the same summary route network. · A vPort or APP cluster VIP on the vRouter has been bound to a floating IP. · The specified device doesn't exist. · The device ID and the device name do not match. · The BGP peer already exists. · The vRouter name cannot exceed 255 characters. · The settings of whether traffic from the vRouter to the external network is directly forwarded by the gateway must be the same on vRouters bound to the same sharing IP. · When the value of the direct_external field is true, the external network bound to the vRouter must be a VLAN and the value of the force_flat field must be false. · If the value of the direct_external parameter is false for a vRouter, the vRouter cannot be bound to a virtual firewall configured with a security external network address pool and an external network of the VLAN type at the same time. · The router and network doesn't belong to the same VDS. · Unknown error.

Delete vRouter

Keyword	DELETE_ROUTE_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. · 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. · Failed to delete the vRouter because it has been bound to a vRouter link. · Failed to delete the vRouter because the vRouter has routing tables. · Failed to delete the vRouter because a routing table has been bound to the vRouter. · The vRouter has been bound to a vRouter interconnection. · The vRouter has been bound to a Layer 3 DC interconnection. · Failed to delete the vRouter because it has been bound to route entries. · 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. · Configuration recovery is in progress. · 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. · Configuration recovery is in progress. · The specified resource doesn't exist. · The subnet has been bound to a vRouter interconnection. · The subnet has been bound to a Layer 3 DC interconnection. · 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. · Configuration recovery is in progress. · The subnet has already been bound to another 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. · The subnet of the vRouter overlaps with the subnet of the other vRouter of the vRouter link. · The subnet overlaps with a selected subnet of the other vRouter in a vRouter interconnection. · The subnet overlaps with a remote subnet in a Layer 3 DC interconnection that involves the vRouter. · The vPort already exists. · 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. · 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 router. · The subnet ID is required. · Failed to delete the interface from the vRouter, because the vPort or APP cluster VIP in the subnet has a floating IP. · The specified resource doesn't exist. · The subnet has been bound to a routing table. · The vPort has been bound to a routing table. · The subnet overlaps with the destination subnet of the route entry. · Unknown error.

Create 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. · Configuration recovery is in progress. · Invalid tenant ID. · The segment ID is already used. · The segment ID is out of range. · The network's parameter is incorrect. · The network already exists. · Networks created in bulk cannot use the same ID. · The router doesn't exist. · The router and network doesn't belong to the same VDS. · Failed to create the VXLAN because no available overlay license exists. · Invalid broadcast suppression configuration. · Invalid unknown multicast suppression configuration. · Invalid unknown unicast suppression configuration. · 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. · The number of DHCP servers on the DHCP relay agent can't exceed 8. · The IP address of the DHCP server is invalid. · The IP address of the DHCP server is required. · External networks and VLANs do not support network sharing. · No available segment ID. · The network name cannot exceed 255 characters. · The specified tenant doesn't exist. · Only external networks can be configured as flat networks. · When the external network is a VXLAN, the value of the force_flat field cannot be false. · The segment ID of a flat network must be null. · The value of the force_flat field can be configured as true only when the network is an external network. · The value of the router:external field is required. · The value of the shared field is required. · The value of the admin_state_up field is required. · The value of the distributed field is required. · The value of the vswitch_flood_and_learn field is invalid. · The specified tenant doesn't bind VDS. · The VDS of the network is different than the tenant. · 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. · Configuration recovery is in progress. · The external attribute can't be modified. · The network's parameter is incorrect. · The specified resource doesn't exist. · Invalid broadcast suppression configuration. · Invalid unknown multicast suppression configuration. · Invalid unknown unicast suppression configuration. · The ARP packet sending rate exceeds the rate limit. · The number of DHCP servers on the DHCP relay agent can't exceed 8. · The IP address of the DHCP server is invalid. · The IP address of the DHCP server is required. · 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. · The network name cannot exceed 255 characters. · The VDS doesn't exist. · The value of the router:external field is required. · The value of the shared field is required. · The value of the admin_state_up field is required. · The value of the distributed field is required. · The value of the vswitch_flood_and_learn field is invalid. · 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. · Configuration recovery is in progress. · Can’t delete the network because a port resides on the network. · 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. · The network has been bound to a Layer 2 DC interconnection. · 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. · 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 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 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 pool's start IP can't be higher than the end IP. · The IP range of the address pool overlaps with the IP range of another address pool. · The subnet's tenant ID is different than the network. · The subnet ID already exists. · Subnets created in bulk cannot use the same ID. · 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 routes. · Invalid CIDR. · The configuration contains duplicate DNS. · Failed to create subnets for a VXLAN because no available overlay license exists. · The subnet name cannot exceed 255 characters. · An external subnet must be configured with a gateway IP address. · Subnets not configured with a gateway IP address cannot be enabled with DHCP. · The gateway IP for the subnet of a VLAN cannot be null. · Failed to add the subnet because the number of subnets has reached the limit. · You must specify whether to enable DHCP for the subnet or not. · 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. · Configuration recovery is in progress. · The subnet ID is required. · The pool's start IP can't be higher than the end IP. · The IP range of the 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 routing table. · 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 routes. · The address pool of the internal subnet can't be modified. · The specified resource doesn't exist. · The subnet is not bound to a vRouter. · The configuration contains duplicate DNS. · The subnet name cannot exceed 255 characters. · The gateway IP address doesn’t belong to the subnet. · The gateway IP address conflicts with the subnet broadcast address. · The gateway IP address conflicts with the subnet address. · An external subnet must be configured with a gateway IP address. · Subnets not configured with a gateway IP address cannot be enabled with DHCP. · The gateway IP for the subnet of a VLAN cannot be null. · Cannot modify the gateway IP address for the subnet, because the subnet is bound a vRouter. · The gateway IP address is already used by a vPort. · The gateway IP address is already used by an APP cluster VIP. · The gateway IP address is already used by a floating IP. · You must specify whether to enable DHCP for the subnet or not. · 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. · 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. · An APP cluster VIP resides on the subnet. · The specified resource doesn't exist. · The external subnet has floating IPs. · The subnet has been bound to a vRouter interconnection. · The subnet has been bound to a Layer 3 DC interconnection. · 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. · 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 profile name is required. · Invalid rate value. · Network policies created in bulk cannot use the same UUID. · 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. · Configuration recovery is in progress. · The QoS policy ID is required. · 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 profile 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. · Configuration recovery is in progress. · The network policy has been bound to a port or a port group. · The QoS policy has been bound to floating IPs. · 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. · Configuration recovery is in progress. · Duplicate security policy UUID. · Security policies created in bulk cannot use the same ID. · Invalid empty rule action. · The subnet name cannot exceed 255 characters. · The ip_mac_bingding is required. · 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. · Configuration recovery is in progress. · The security policy ID is required. · Invalid empty rule action. · The specified resource doesn't exist. · The security policy name cannot exceed 255 characters. · The specified tenant ID cannot be modified. · 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. · Configuration recovery is in progress. · The security policy has been bound to a port or a port group. · The security policy has been specified as a remote security policy. · 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. · 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 network bound to the vRouter of the vPort or APP cluster VIP. · The floating IP ID already exists. · Floating IPs created in bulk cannot use the same ID. · 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. · The network policy and inbound/outbound CIR cannot be both configured. · 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. · 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. · The gateway of the vRouter to which the floating IP belongs doesn't support floating IP addresses. · The floating IP address has been used by another gateway resource. · The vRouter to which the floating IP address belongs doesn't bind a gateway service resource. · The vRouter to which the floating IP address belongs has not been bound to a gateway. · Failed to bind the floating IP to the vPort or APP cluster VIP, because the floating IP doesn't belong to the external network 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. · Invalid IP address. · 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 UUIDs of the vPort, APP cluster VIP, subnet, and network to which the floating IP belongs are not specified. · The network policy and inbound/outbound CIR cannot be both configured. · 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. · 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. · Configuration recovery is in progress. · The port group name is already used. · The port group ID is already used. · Port groups created in bulk cannot use the same ID. · The port group name should be less than 255 characters. · The network ID is required. · The network doesn't exist. · The specified port policy doesn't exist. · The specified security policy doesn't exist. · Failed to create the port group on the vCenter. · The ID of the specified tenant is different than the tenant to which the specified virtual link layer network belongs. · The port group name is required. · 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. · 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. · Operation failed. The security policy rule failed to take effect because of insufficient hardware resources. · 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. · Configuration recovery is in progress. · The port group contains visible ports. · The specified resource doesn't exist. · Unknown error.

Create security rules

Keyword	CREATE_SECURITY_RULE_OP
Message text	Created security rules $1.
Variable fields	$1: Security rule configuration.
Example	Created security rules { UUID: 9dc511fc-c4ba-413a-aa8e-c182cdb20e18 Security policy name: test1 Direction: egress IPv4 prefix: 2.2.2.0/24 Protocol type: UDP Port range: 3~17 }, { UUID: f48b45ff-db86-4969-93a7-b184ad8807aa Security policy name: test2 Direction: ingress Remote security policy name: remote1 Protocol type: UDP Port range: 1~2 }.
Explanation	A security rule was created.
Possible failure causes	· The request is invalid: Incorrect JSON. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid security policy UUID. · Duplicate security rule UUID. · Security rules created in bulk cannot use the same UUID. · The new security rule conflicts with the old rules. · Invalid IP version. · Invalid IP prefix. · Invalid protocol type. · Invalid port range. · Invalid ICMP type. · Invalid ICMP code. · Invalid direction. · Operation failed. The security policy rule failed to take effect because of insufficient hardware resources. · The IP prefix and the security policy can't both be configured. · The IP prefix and the IP version do not match. · Unknown error.

Update security rule

Keyword	UPDATE_SECURITY_RULE_OP
Message text	Updated security rule $1.
Variable fields	$1: Security rule configuration.
Example	Updated security rule { UUID: 536be81d-413e-420d-8c5f-8075b11affa6 Security policy name: test5 Direction: egress IPv4 prefix: 4.2.2.0/24 Protocol type: ICMP Type: 1 Code: 2 }.
Explanation	A security rule was modified.
Possible failure causes	· The request is invalid: Incorrect JSON. · The controller is not the active leader. · Configuration recovery is in progress. · The new security rule conflicts with the old rules. · 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. · Operation failed. The security policy rule failed to take effect because of insufficient hardware resources. · The IP prefix and the security policy can't both be configured. · The IP prefix and the IP version do not match. · Unknown error.

Delete security rule

Keyword	DELETE_SECURITY_RULE_OP
Message text	Deleted security rule $1.
Variable fields	$1: Security rule configuration.
Example	Deleted security rule { UUID: 536be81d-413e-420d-8c5f-8075b11affa6 Security policy name: test5 Direction: egress IPv4 prefix: 4.2.2.0/24 Protocol type: ICMP Type: 1 Code: 2 }.
Explanation	A security 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.

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	· 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. · The domain doesn't exist. · The vCenter username cannot exceed 255 characters. · The vCenter password cannot exceed 255 characters. · The vCenter name cannot exceed 255 characters. · Domains of this type cannot connect to the vCenter. · The domain type is not vCenter. · 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 controller is not the active leader. · The specified resource doesn't exist. · Failed to connect to the vCenter. · Configuration recovery is in progress. · Cannot delete the vCenter because it has connected to a domain. · 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	The vSwitch version file name is invalid.

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	· Failed to delete the installation file. · The controller is not the active leader. · Configuration recovery is in progress. · The specified resource doesn't exist.

Install VFE

Keyword	INSTALL_VFE_OP
Message text	Installed VFE
Variable fields	N/A
Example	Installed VFE
Explanation	A vSwitch version was installed.
Possible failure causes	· Failed to connect to the vCenter. · Installation failed. · Failed to get the installation file.

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	· Update failed. · Failed to get the installation file. · Versions not match.

Uninstall VFE

Keyword	UNINSTALL_VFE_OP
Message text	Uninstalled VFE.
Variable fields	N/A
Example	Uninstalled VFE.
Explanation	The vSwitch version was uninstalled.
Possible failure causes	· The request is invalid: Incorrect JSON. · Uninstallation failed. · Connection to the vCenter is not established.

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. · Configuration recovery is in progress. · The domain name is required. · Invalid domain type. · The domain UUID is already used. · Domains created in bulk cannot use the same UUID. · The bridge name of the VDS cannot exceed 15 characters. · The VXLAN tunnel name of the VDS cannot exceed 15 characters. · The domain name is already used. · The host doesn't exist. · The VDS doesn't exist. · The domain name cannot exceed 255 characters. · 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. · 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 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. · The domain name cannot exceed 255 characters. · Cannot modify the name of the default domain. · The bridge name of the VDS cannot exceed 15 characters. · The VXLAN tunnel name of the VDS cannot exceed 15 characters. · 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. · Configuration recovery is in progress. · Failed to delete the domain. · Can't delete the default domain. · 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 subnet to which the vPort belongs. $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. · Configuration recovery is in progress. · Invalid tenant ID. · The network doesn't exist. · Ports created in bulk cannot use the same ID. · 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. · The mirror direction is required. · The mirror type is required. · Invalid mirror direction. · Invalid mirror type. · Invalid mirror remote IP. · The mirror remote IP is required. · The length of the description is out of range. · 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 don't reside on the same network. · The flooding domain and the vPort don't reside on 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 cannot exceed 255 characters. · APP cluster VIPs bound to the same vPort must belong to the same subnet. · The subnet to which the vPort belongs must be bound to a vRouter because the vPort has been bound to a routing table. · The subnets of the flooding domains bound to the same vPort can't overlap with each other. · The specified resource doesn't exist. · The MAC address conflicts with the gateway MAC address or reserved gateway MAC address. · Invalid MAC address. · The vPort name cannot exceed 255 characters. · Operation failed. The security policy rule failed to take effect because of insufficient hardware resources. · The specified tenant doesn't exist. · The extend_dhcp_options field is invalid. · The value of the opt_name field is required. · The value of the opt_name field is invalid. · The value of the opt_value field is required. · The value of the server-ip-address DHCP option is invalid. · The value of the tftp-server DHCP option cannot exceed 63 characters. · The value of the bootfile-name DHCP option cannot exceed 127 characters. · The values of the opt_name fields cannot be the same. · The number of NTP server addresses cannot exceed 63. · The NTP server address is invalid. · Duplicated NTP server addresses exist. · The fixed_ips field is required. · The IP address of a vPort can be null only when the vPort resides on an external network or the subnet to which the vPort belongs is enabled with DHCP. · The vPort cannot have duplicated IP addresses. · The vPort type is invalid. · The vPort is not a dvPort. · The value of the device owner parameter for LB vPorts must be neutron:LOADBALANCER or neutron:LOADBALANCERV2. · The vPort type and the value of the device owner parameter do not match. · IP addresses in the subnet to which the vPort belongs are used up. · 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. · 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 mirror direction is required. · The mirror type is required. · Invalid mirror direction. · Invalid mirror type. · Invalid mirror remote IP. · The mirror remote IP is required. · 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. · The subnet must belong to the specified network. · Unknown error. · The vPort is created through vCenter and the port group can't be modified. · The network doesn't exist. · The specified subnet doesn't exist. · The specified resource doesn't exist. · The length of the description is out of range. · Invalid APP cluster VIP. · The APP cluster VIP and the vPort don't reside on the same network. · The flooding domain and the vPort don't reside on 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 cannot exceed 255 characters. · APP cluster VIPs bound to the same vPort must belong to the same subnet. · The subnet to which the vPort belongs must be bound to a vRouter because the vPort has been bound to a routing table. · The MAC address conflicts with the gateway MAC address or reserved gateway MAC address. · Invalid MAC address. · The vPort name cannot exceed 255 characters. · Operation failed. The security policy rule failed to take effect because of insufficient hardware resources. · The extend_dhcp_options field is invalid. · The value of the opt_name field is required. · The value of the opt_name field is invalid. · The value of the opt_value field is required. · The value of the server-ip-address DHCP option is invalid. · The value of the tftp-server DHCP option cannot exceed 63 characters. · The value of the bootfile-name DHCP option cannot exceed 127 characters. · The values of the opt_name fields cannot be the same. · The number of NTP server addresses cannot exceed 63. · The NTP server address is invalid. · Duplicated NTP server addresses exist. · The fixed_ips field is required. · The IP address of a vPort can be null only when the vPort resides on an external network or the subnet to which the vPort belongs is enabled with DHCP. · The vPort cannot have duplicated IP addresses. · The vPort type is invalid. · The vPort type and the value of the device owner parameter do not match. · IP addresses in the subnet to which the vPort belongs are used up.

Delete vPort

Keyword	DELETE_VPORT_OP
Message text	Deleted vPort "$1: $2/$3".
Variable fields	$1: Name of the subnet to which the vPort belongs. $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 request is invalid: Incorrect JSON. · The controller is not the active leader. · Configuration recovery is in progress. · Can't delete the port because it is created by vCenter. · Can't delete the auto created LB vPort. · The specified resource doesn't exist. · The vPort is not a dvPort. · Unknown error.

Create router link

Keyword	CREATE_ROUTERLINK_OP
Message text	Created router link "$1"
Variable fields	$1: Name of the vRouter link.
Example	Created router link "zn_routelink"
Explanation	A vRouter link was created.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · The vRouter link ID has already been used. · vRouter links created in bulk cannot use the same ID. · The specified vRouter doesn't exist. · The specified vRouter IDs cannot be the same. · The vRouter link already exists. · Both router_id1 and router_id2 are required. · The subnet of vRouter1 overlaps with the subnet of vRouter2. · The vRouter link name cannot exceed 255 characters. · Unknown error.

Update router link

Keyword	UPDATE_ROUTERLINK_OP
Message text	Updated router link "$1"
Variable fields	$1: Name of the vRouter link.
Example	Updated router link "zn_routelink"
Explanation	A vRouter link was modified.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · The vRouter link ID is required. · The specified resource doesn't exist. · The vRouter link name cannot exceed 255 characters. · Unknown error.

Delete router link

Keyword	DELETE_ROUTERLINK_OP
Message text	Deleted router link "$1"
Variable fields	$1: Name of the vRouter link.
Example	Deleted router link "zn_routelink"
Explanation	A vRouter link 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.

Create route table

Keyword	CREATE_ROUTETABLE_OP
Message text	Created routing table "$1"
Variable fields	$1: Name of the routing table.
Example	Created routing table "zn_routetable"
Explanation	A routing table was created.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · The routing table already exists. · Route tables created in bulk cannot use the same ID. · The router ID is required. · The router doesn't exist. · The tenant ID of the routing table is different than the vRouter. · The tenant name of the routing table is different than the vRouter. · Failed to create the routing table because physical MAC address forwarding is disabled. · The routing table name cannot exceed 255 characters. · Unknown error.

Update route table

Keyword	UPDATE_ROUTETABLE_OP
Message text	Updated routing table "$1"
Variable fields	$1: Name of the routing table.
Example	Updated routing table "zn_routetable"
Explanation	A routing table 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. · The route table id is required. · The routing table name cannot exceed 255 characters. · The parameter (parameters) can’t be modified. · Unknown error.

Delete route table

Keyword	DELETE_ROUTETABLE_OP
Message text	Deleted routing table "$1"
Variable fields	$1: Name of the routing table.
Example	Deleted routing table "zn_routetable"
Explanation	A routing table was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · The specified resource doesn't exist. · The routing table is being used by a subnet. · The routing table is being used by a vPort. · The routing table is used by a vRouter. · Unknown error.

Create route entry

Keyword	CREATE_ROUTE_OP
Message text	Created route "CIDR: $1, next hop type: $2"
Variable fields	$1: Destination address. $2: Next hop type.
Example	Created route "CIDR: 2.1.1.0/24, next hop type: IPv4"
Explanation	A route entry was created.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · The route has already existed. · Invalid next hop. · Invalid CIDR. · Invalid routing table ID. · Invalid next hop type. · The destination subnet of the route entry overlaps with the subnet bound to the interface of the vRouter. · The specified device doesn't exist. · The device ID and the device name do not match. · Duplicate devices exist. · The specified next hop vRouter does not exist. · When the next hop type is Blackhole, the next hop is not required. · When the next hop type is Blackhole, the value of the is_distributed parameter must be false. · When the next hop type is Blackhole, the next hop vRouter is not required. · Unknown error.

Update route entry

Keyword	UPDATE_ROUTE_OP
Message text	Updated route "CIDR: $1, next hop type: $2"
Variable fields	$1: Destination address. $2: Next hop type.
Example	Updated route "CIDR: 2.1.1.0/24, next hop type: IPv4".
Explanation	A route entry 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. · The specified device doesn't exist. · The device ID and the device name do not match. · Duplicate devices exist. · Unknown error.

Delete route entry

Keyword	DELETE_ROUTE_OP
Message text	Deleted route "CIDR: $1, next hop type: $2"
Variable fields	$1: Destination address. $2: Next hop type.
Example	Deleted route "CIDR: 2.1.1.0/24, next hop type: IPv4"
Explanation	A route entry 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.

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. · APP cluster VIPs created in bulk cannot use the same ID. · 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.

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.

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.

Create flooding domain

Keyword	CREATE_FLOODINGDOMAIN_OP
Message text	Created flooding domain “$1”.
Variable fields	$1: Name of the flooding domain.
Example	Created flooding 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 cannot exceed 255 characters. · The flooding domain ID already exists. · Flooding domains created in bulk cannot use the same ID. · The flooding domain name is required. · The MAC address type must be ANY for the flooding domain. · 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 specified tenant doesn't exist.

Update flooding domain

Keyword	UPDATE_FLOODINGDOMAIN_OP
Message text	Updated flooding domain “$1”.
Variable fields	$1: Name of the flooding domain.
Example	Updated flooding domain “domain1”.
Explanation	A flooding domain was modified.
Possible failure causes	· The MAC address type must be ANY for the flooding domain. · 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.

Delete flooding domain

Keyword	DELETE_FLOODINGDOMAIN_OP
Message text	Deleted flooding domain “$1”.
Variable fields	$1: Name of the flooding domain.
Example	Deleted flooding domain “domain1”.
Explanation	A flooding domain 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.

Update vCenter status

Keyword	SET_VCENTER_STATUS_OP
Message text	Updated vCenter status to “$1”.
Variable fields	$1: vCenter connection status. Options include connected and 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. · Unknown error.

Create port name prefix

Keyword	CREATE_PORT_PREFNAME_OP
Message text	Created port name prefix port type ”$1”, prefix name [$2].
Variable fields	$1: Port type. $2: Port name prefix.
Example	Created port name prefix port type “UPLINK”, prefix name [aaa, bbb], port type “VPORT”, prefix name [a1, b1].
Explanation	A port name prefix was added.
Possible failure causes	· The request is invalid. · Configuration recovery is in progress. · The controller is not the active leader. · Invalid port type. · The port name prefix prefixName already exists. · Invalid port name prefix. · The port name prefix cannot exceed 64 characters.

Delete vPort prefix name

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

Update advanced setting

Keyword	UPDATE_GLOBAL_CONFIG_OP
Message text	Updated the advanced settings. Stateful flow table: $1, NE bidirectional IPv4 security policy: $2.
Variable fields	$1: On/off state of the stateful flow table mode, printed only when the state changes. $2: On/off state of the NE bidirectional security policy, printed only when the state changes.
Example	Updated the advanced settings. Stateful flow table: off, NE bidirectional IPv4 security policy: off.
Explanation	The user enabled or disabled the advanced settings.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown error.

Create netoverlay host

Keyword	CREATE_NETOVERLAYHOST_OP
Message text	Created netoverlay host "$1".
Variable fields	$1: Name of the network overlay host.
Example	Created netoverlay host "112".
Explanation	A network overlay host was created.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · The netoverlay host name is required. · The netoverlay host already exists. · Netoverlay hosts created in bulk cannot use the same ID. · The netoverlay host name cannot exceed 255 characters. · Unknown error.

Delete netoverlay host

Keyword	DELETE_NETOVERLAY_HOST_OP
Message text	Deleted netoverlay host "$1".
Variable fields	$1: Name of the network overlay host.
Example	Deleted netoverlay host "112".
Explanation	A network overlay host 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.

Update netoverlay host

Keyword	UPDATE_NETOVERLAYHOST_OP
Message text	Updated netoverlay host "$1".
Variable fields	$1: Name of the network overlay host.
Example	Updated netoverlay host "112".
Explanation	A network overlay host was modified.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · The netoverlay host name is required. · The netoverlay host already exists. · The specified netoverlay group does not exist. · A netoverlay host with VLAN-VXLAN mappings added cannot be bound to a netoverlay group. · The netoverlay host name cannot exceed 255 characters. · Unknown error.

Create netoverlay group

Keyword	CREATE_NETOVERLAYGROUP_OP
Message text	Created netoverlay group "$1".
Variable fields	$1: Name of the network overlay group.
Example	Created netoverlay group "group1".
Explanation	A network overlay group was created.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · The netoverlay group name is required. · The netoverlay group already exists. · The netoverlay group name cannot exceed 255 characters. · Unknown error.

Delete netoverlay group

Keyword	DELETE_NETOVERLAY_GROUP_OP
Message text	Deleted netoverlay group "$1".
Variable fields	$1: Name of the network overlay group.
Example	Deleted netoverlay group "group1".
Explanation	A network overlay group 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.

Create VLAN-VXLAN map

Keyword	CREATE_VLANVXLAN_MAP_OP
Message text	Created VLAN-VXLAN map "$1-$2".
Variable fields	$1: VLAN ID. $2: VXLAN ID.
Example	Created VLAN-VXLAN map "11-22".
Explanation	A VLAN-VXLAN mapping is created.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · The netoverlay host ID is required. · The netoverlay host does not exist. · The VLAN ranges of hosts in a netoverlay cannot be the same. · The VLAN ranges of hosts in a netoverlay already exists. · VLAN-VXLAN mappings cannot be added on a netoverlay host bound to a netoverlay group. · The netoverlay host and the netoverlay group cannot both be null. · The specified netoverlay group does not exist. · The netoverlay host and the netoverlay group cannot be both configured. · The VLAN ID is required. · The VXLAN ID is required. · The VLAN ID is out of range. · The VXLAN ID is out of range. · Unknown error.

Delete VLAN-VXLAN map

Keyword	DELETE_VLANVXLAN_MAP_OP
Message text	Deleted VLAN-VXLAN map "$1-$2".
Variable fields	$1: VLAN ID. $2: VXLAN ID.
Example	Deleted VLAN-VXLAN map "11-22".
Explanation	A VLAN-VXLAN mapping is deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · The specified resource doesn't exist. · Unknown error.

Configure batch vSwitch deployment parameters

Keyword	SET_VSWITCH_CFG_OP
Message text	Configured batch vSwitch deployment parameters.
Variable fields	N/A
Example	Configured batch vSwitch deployment parameters.
Explanation	Batch vSwitch deployment parameters were configured.
Possible failure causes	· The request is invalid. · The start IP address can't be higher than the end IP address. · The IP address ranges of VTEP IP address pool 1 and VTEP IP address pool 2 can't overlap with each other. · Unknown error.

Import host file

Keyword	IMPORT_HOST_LIST_OP
Message text	Imported host file.
Variable fields	N/A
Example	Imported host file.
Explanation	A host file was imported.
Possible failure causes	· Host host-IP, parameter is required. · Unknown error.

Run custom script

Keyword	CUSTOM_SCRIPT_OP
Message text	Ran custom script. Total: $1. Success: $2. Failure: $3.
Variable fields	$1: Number of hosts that run custom scripts. $2: Number of hosts that successfully run custom scripts. $3: Number of hosts that fail to run custom scripts.
Example	Ran custom script.
Explanation	The custom script is executed for the host.
Possible failure causes	· The request is invalid. · The task has been terminated by user user. · For more information, see the deployment logs. · Deploying. Please try later. · Unknown error.

Export host file

Keyword	EXPORT_HOST_LIST_OP
Message text	Exported host file.
Variable fields	N/A
Example	Exported host file.
Explanation	The host list is exported.
Possible failure causes	N/A

Export SSH key

Keyword	EXPORT_SSH_KEY_OP
Message text	Exported SSH key.
Variable fields	N/A
Example	Exported SSH key.
Explanation	The SSH key is exported.
Possible failure causes	Unknown error.

Upload custom script

Keyword	UPLOAD_CUSTOM_SCRIPT_OP
Message text	Uploaded custom script ”$1”.
Variable fields	$1: Name of the custom script.
Example	Uploaded custom script “selfShell.sh”.
Explanation	A custom script is uploaded.
Possible failure causes	Unknown error.

Install vSwitch

Keyword	INSTALL_VSWITCH_OP
Message text	Installed vSwitch. Total: $1. Success: $2. Failure: $3.
Variable fields	$1: Number of hosts that are installed with vSwitch versions. $2: Number of hosts that are successfully installed with vSwitch versions. $3: Number of hosts that fail to be installed with vSwitch versions.
Example	Installed vSwitch.
Explanation	A vSwitch version is installed for the host.
Possible failure causes	· The request is invalid. · The task has been terminated by user user. · For more information, see the deployment logs. · Deploying. Please try later. · Unknown error.

Update vSwitch

Keyword	UPDATE_VSWITCH_OP
Message text	Updated vSwitch. Total: $1. Success: $2. Failure: $3.
Variable fields	$1: Number of hosts whose vSwitch versions are updated. $2: Number of hosts whose vSwitch versions are successfully updated. $3: Number of hosts whose vSwitch versions fail to be updated.
Example	Updated vSwitch.
Explanation	A vSwitch version is upgraded for the host.
Possible failure causes	· The request is invalid. · The task has been terminated by user user. · For more information, see the deployment logs. · Deploying. Please try later. · Unknown error.

Uninstall vSwitch

Keyword	UNINSTALL_VSWITCH_OP
Message text	Uninstalled vSwitch. Total: $1. Success: $2. Failure: $3.
Variable fields	$1: Number of hosts whose vSwitch versions are uninstalled. $2: Number of hosts whose vSwitch versions are successfully uninstalled. $3: Number of hosts whose vSwitch versions fail to be uninstalled.
Example	Uninstalled vSwitch.
Explanation	The vSwitch version is unloaded for a host.
Possible failure causes	· The request is invalid. · The task has been terminated by user user. · For more information, see the deployment logs. · Deploying. Please try later. · Unknown error.

Check host status

Keyword	CHECK_HOST_STATUS
Message text	Checked host status.
Variable fields	N/A
Example	Checked host status.
Explanation	The host status is checked.
Possible failure causes	· The request is invalid. · The task has been terminated by user (sdn). · Unknown error.

Upload vSwitch file

Keyword	UPLOAD_VSWITCH_FILE_OP
Message text	Uploaded vSwitch file ”$1”.
Variable fields	$1: vSwitch version file name.
Example	Uploaded vSwitch file “s1020v_F2237.zip”.
Explanation	A vSwitch version file is uploaded.
Possible failure causes	· Parse zip file failure. · The installation file of the same version already exists. · Unknown error.

Delete vSwitch file

Keyword	DELETE_VSWITCH_FILE_OP
Message text	Deleted vSwitch file ”$1”.
Variable fields	$1: vSwitch version file name.
Example	Deleted vSwitch file “s1020v_F2237.zip”.
Explanation	A vSwitch version file is deleted.
Possible failure causes	Unknown error.

Create network nodes

Keyword	CREATE_NETWORKNODE_OP
Message text	Created network nodes ”$1”.
Variable fields	$1: Names of the network nodes.
Example	Created network nodes "network1", "network2".
Explanation	One or multiple network nodes were created.
Possible failure causes	· Unknown error. · Duplicated VTEP IP addresses exist for the network nodes created in bulk. · Network nodes created in bulk cannot use the same UUID. · Duplicated names exist for the bulk-created network nodes of the same VDS. · The request is invalid. · The network node is already used. · The VDS doesn't exist. · Invalid VTEP IP address. · VTEP IP is required. · The network node name cannot exceed 255 characters. · The specified resource doesn't exist. · The name has been used by another network node in the same VDS. · The VTEP IP is already used.

Update network node

Keyword	UPDATE_NETWORKNODE_OP
Message text	Updated network node ”$1”.
Variable fields	$1: Name of the network node.
Example	Updated network node “netnode”.
Explanation	A network node was modified.
Possible failure causes	· Unknown error. · The request is invalid. · Invalid VTEP IP address. · The name cannot be modified. · The VDS ID cannot be modified. · VTEP IP is required. · The specified resource doesn't exist.

Delete network node

Keyword	DELETE_NETWORKNODE_OP
Message text	Deleted network node ”$1”.
Variable fields	$1: Name of the network node.
Example	Deleted network node “netnode”.
Explanation	A network node was deleted.
Possible failure causes	· Unknown error. · The request is invalid. · The specified resource doesn't exist.

Update global default action

Keyword	UPDATE_GLOBALDEFAULTACTION_OP
Message text	Updated global default action “$1”.
Variable fields	$1: DFW global default action.
Example	Updated global default action “forward”.
Explanation	The DFW global default action was modified.
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: DFW policy or subpolicy name.
Example	Created DFW policy “policy1”.
Explanation	A DFW 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. · DFW Policies created in bulk cannot use the same ID. · Unknown error.

Update DFW policy

Keyword	UPDATE_DFW_POLICY_OP
Message text	Updated DFW policy “$1”.
Variable fields	$1: DFW policy or subpolicy name.
Example	Updated DFW policy “policy1”.
Explanation	A DFW 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. · The specified tenant ID cannot be modified. · Unknown error.

Delete DFW policy

Keyword	DELETE_DFW_POLICY_OP
Message text	Deleted DFW policy “$1”.
Variable fields	$1: DFW policy or subpolicy name.
Example	Deleted DFW policy “policy1”.
Explanation	A DFW 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: DFW policy or subpolicy rule name.
Example	Created DFW policy rule “rule1”.
Explanation	A DFW 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. · DFW policy rules created in bulk cannot use the same ID. · Unknown error.

Delete DFW policy rule

Keyword	DELETE_DFW_POLICY_RULE_OP
Message text	Deleted DFW policy rule “$1”.
Variable fields	$1: DFW policy or subpolicy rule name.
Example	Deleted DFW policy rule “rule1”.
Explanation	A DFW 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: DFW IP set name.
Example	Created DFW IP set “set1”.
Explanation	A DFW IP 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. · IP sets created in bulk cannot use the same ID. · Unknown error.

Update DFW IP set

Keyword	UPDATE_DFW_IPSET_OP
Message text	Updated DFW IP set “$1”.
Variable fields	$1: DFW IP set name.
Example	Updated DFW IP set “set1”.
Explanation	A DFW IP 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: DFW IP set name.
Example	Deleted DFW IP set “set1”.
Explanation	A DFW IP 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: DFW IP set rule name.
Example	Created DFW IP set rule “rule1”.
Explanation	A DFW IP 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. · IP set rules created in bulk cannot use the same ID. · The IP set rule name cannot exceed 255 characters. · Unknown error.

Delete DFW IP set rule

Keyword	DELETE_DFW_IPSET_RULE_OP
Message text	Deleted DFW IP set rule “$1”.
Variable fields	$1: DFW IP set rule name.
Example	Deleted DFW IP set rule “rule1”.
Explanation	A DFW IP 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.

Track flow entry of IP packet

Keyword	TRACK_FLOWENTRY_IP_PACKET_OP
Message text	Tracked the flow entries of an IP packet on $1.
Variable fields	$1: IP address of the host where the packet resides.
Example	Tracked the flow entries of an IP packet on 172.16.1.1.
Explanation	Flow entries of an IP packet were tracked on a host.
Possible failure causes	· The request is invalid. · The host IP address is required. · Invalid host IP address. · The OpenFlow input port number is required. · Invalid OpenFlow input port number. · Supported packet type is IP, TCP, UDP, or ICMP. · Invalid VXLAN ID. · The source IP address is required. · Invalid source IP address. · The destination IP address is required. · Invalid destination IP address. · Invalid source MAC address. · Invalid destination MAC address. · Invalid source port number. · Invalid destination port number. · Invalid ICMP message type. · Invalid ICMP message code. · Only ICMP packets support the ICMP message type and code configurations. · Only TCP or UDP packets support the source and destination port number configurations. · Invalid SSH port number. · The username is required. · The password is required. · The username cannot exceed 255 characters. · The password cannot exceed 255 characters. · Tracking the flow entries of packets is not supported on a host with a stateful flow table deployed by the controller. · SSH connection failed. · Error username or password. · Tracking the flow entries of packets is supported only on an online host installed with S1020V. · The port has not come online on the specified host. · Unknown error.

Track flow entry of ARP packet

Keyword	TRACK_FLOWENTRY_ARP_PACKET__OP
Message text	Tracked the flow entries of an ARP packet on $1.
Variable fields	$1: IP address of the host where the packet resides.
Example	Tracked the flow entries of an ARP packet on 172.16.1.1.
Explanation	Flow entries of an ARP packet were tracked on a host.
Possible failure causes	· The request is invalid. · The host IP address is required. · Invalid host IP address. · The OpenFlow input port number is required. · Invalid OpenFlow input port number. · Invalid VXLAN ID. · The source IP address is required. · Invalid source IP address. · The destination IP address is required. · Invalid destination IP address. · Invalid source MAC address. · Invalid destination MAC address. · The ARP message type is required. · Invalid ARP message type. · Invalid sender MAC address. · Invalid target MAC address. · Invalid SSH port number. · The username is required. · The password is required. · The username cannot exceed 255 characters. · The password cannot exceed 255 characters. · Tracking the flow entries of packets is not supported on a host with a stateful flow table deployed by the controller. · SSH connection failed. · Error username or password. · Tracking the flow entries of packets is supported only on an online host installed with S1020V. · The port has not come online on the specified host. · Unknown error.

Start auditing on host

Keyword	START_OPENFLOW_AUDIT_OP
Message text	Started auditing $1 on host $2.
Variable fields	$1: Auditing object. $2: Host IP address.
Example	Started auditing [flow tables, group tables] on host 1.1.1.1.
Explanation	The flow tables and group tables of a host were audited.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Invalid IP address. · The host has not established an OpenFlow connection to the controller. · The device does not support data synchronization or audit because of the device type restriction. · The host is not connected to the master controller. Please try again later. · Unknown error.

Start synchronization on host

Keyword	START_OPENFLOW_ DATA_SYNCHRONIZATION_OP
Message text	Started synchronizing $1 on host $2.
Variable fields	$1: Data synchronization object. $2: Host IP address.
Example	Started synchronizing [flow tables, group tables] on host 1.1.1.2.
Explanation	The flow tables and group tables of a host were synchronized.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Invalid IP address. · The host has not established an OpenFlow connection to the controller. · The device does not support data synchronization or audit because of the device type restriction. · The host is not connected to the master controller. Please try again later. · Unknown error.

Created static link

Keyword	CREATE_STATICLINK_OP
Message text	Created static link “$1”.
Variable fields	$1: Static link name.
Example	Created static link “link1”.
Explanation	A static link was created.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · The request is invalid. · The system name is required. · The system name cannot exceed 255 characters. · The device IP is required. · The device IP is invalid. · The abbreviated access port name is required. · The abbreviated access port name cannot exceed 255 characters. · The static link already exists. · The netoverlay host contains duplicate static link. · Unknown error. · The static link created in bulk cannot use the same ID.

Deleted static link

Keyword	DELETE_STATICLINK_OP
Message text	Deleted static link “$1”.
Variable fields	$1: Static link name.
Example	Deleted static link “link1”.
Explanation	A static link 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.

Create vRouter interconnection

Keyword	CREATE_VROUTERCONNECTION_OP
Message text	Created vRouter interconnection "$1".
Variable fields	$1: vRouter interconnection name.
Example	Created vRouter interconnection "vpc 01".
Explanation	A vRouter interconnection was created.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · The vRouter interconnection ID already exists. · The tenant ID is required. · The tenant does not exist. · The local vRouter ID is required. · The remote vRouter ID is required. · The local vRouter does not exist. · The remote vRouter does not exist. · The local subnet ID is required. · The remote subnet ID is required. · The local subnet list contains nonexistent subnets. · The remote subnet list contains nonexistent subnets. · A remote subnet of the vRouter interconnection overlaps with a remote subnet of a Layer 3 DC interconnection. The subnet of the vRouter interconnection must cover the overlapping subnet of the Layer 3 DC interconnection. · The local vRouter and the remote vRouter cannot be the same. · The local subnets overlap with the subnets of the remote vRouter. · The remote subnets overlap with the subnets of the local vRouter. · The vRouter interconnection already exists. · The status field is a read-only field. · The vRouter interconnection name cannot exceed 255 characters. · The vRouter interconnection description cannot exceed 255 characters. · The network to which the remote subnet belongs cannot be a VLAN. · The remote subnet cannot be an external subnet. · The network to which the local subnet belongs cannot be a VLAN. · The local subnet cannot be an external subnet. · If a vRouter is bound to multiple vRouter interconnections, the selected subnets of the other vRouters bound to these vRouter interconnections cannot overlap. · Unknown error.

Update vRouter interconnection

Keyword	UPDATE_VROUTERCONNECTION_OP
Message text	Updated vRouter interconnection "$1".
Variable fields	$1: vRouter interconnection name.
Example	Updated vRouter interconnection "vpc ".
Explanation	A vRouter interconnection 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. · The status field is a read-only field. · The local subnetID is required. · The remote subnet ID is required. · The local subnet list contains nonexistent subnets. · The remote subnet list contains nonexistent subnets. · The local vRouter cannot be modified. · The remote vRouter cannot be modified. · The tenant cannot be modified. · A remote subnet of the vRouter interconnection overlaps with a remote subnet of a Layer 3 DC interconnection. The subnet of the vRouter interconnection must cover the overlapping subnet of the Layer 3 DC interconnection. · The vRouter interconnection name cannot exceed 255 characters. · The vRouter interconnection description cannot exceed 255 characters. · The network to which the remote subnet belongs cannot be a VLAN. · The remote subnet cannot be an external subnet. · The network to which the local subnet belongs cannot be a VLAN. · The local subnet cannot be an external subnet. · If a vRouter is bound to multiple vRouter interconnections, the selected subnets of the other vRouters bound to these vRouter interconnections cannot overlap. · Unknown error.

Delete vRouter interconnection

Keyword	DELETE_VPCCONNECTION_OP
Message text	Deleted vRouter interconnection "$1".
Variable fields	$1: vRouter interconnection name.
Example	Deleted vRouter interconnection "vpc".
Explanation	A vRouter interconnection was deleted.
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. · Unknown error.

Create Layer 2 DC interconnection

Keyword	CREATE_L2DCICONNECT_OP
Message text	Created Layer 2 DC interconnection "$1".
Variable fields	$1: Layer 2 DC interconnection name.
Example	Created Layer 2 DC interconnection "l2-dci-connect 01".
Explanation	A Layer 2 DC interconnection was created.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · The Layer 2 DC interconnection ID has already been used. · The Layer 2 DC interconnection name is required. · The network ID is required. · The mapping segment ID is required. · The network has been bound to another Layer 2 DC interconnection. · The VDS doesn't exist. · The mapping segment ID is out of range. · The mapping segment ID is already used. · Invalid import target. · Invalid export target. · The Layer 2 DC import target is required. · The Layer 2 DC export target is required. · The export target conflicts with the export target of a Layer 2 DC interconnection. · The export target conflicts with the export target of a Layer 3 DC interconnection. · The network type cannot be VLAN. · The network cannot be external. · The Layer 2 DC interconnection name cannot exceed 255 characters. · The Layer 2 DC interconnection description cannot exceed 255 characters. · Unknown error.

Update Layer 2 DC interconnection

Keyword	UPDATE_L2DCICONNECT_OP
Message text	Updated Layer 2 DC interconnection "$1".
Variable fields	$1: Layer 2 DC interconnection name.
Example	Updated Layer 2 DC interconnection "l2-dci-connect".
Explanation	A Layer 2 DC interconnection 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. · The name cannot be modified. · The network ID cannot be modified. · The mapping segment ID is required. · Invalid import target. · Invalid export target. · The Layer 2 DC import target is required. · The Layer 2 DC export target is required. · The export target conflicts with the export target of a Layer 2 DC interconnection. · The export target conflicts with the export target of a Layer 3 DC interconnection. · The Layer 2 DC interconnection description cannot exceed 255 characters. · Unknown error.

Delete Layer 2 DC interconnection

Keyword	DELETE_L2DCICONNECT_OP
Message text	Deleted Layer 2 DC interconnection "$1".
Variable fields	$1: Layer 2 DC interconnection name.
Example	Deleted Layer 2 DC interconnection "l2-dci-connect".
Explanation	A Layer 2 DC interconnection was deleted.
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. · Unknown error.

Create Layer 3 DC interconnection

Keyword	CREATE_L3DCICONNECT_OP
Message text	Created Layer 3 DC interconnection "$1".
Variable fields	$1: Layer 3 DC interconnection name.
Example	Created Layer 3 DC interconnection "l3-dci-connect 01".
Explanation	A Layer 3 DC interconnection was created.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · The layer 3 DC interconnection name is required. · The local subnet ID is required. · The router ID is required. · The specified vRouter doesn't exist. · The remote subnet is required when the firewall service is enabled. · Invalid remote subnet. · Duplicated remote subnets exist. · A remote subnet of the Layer 3 DC interconnection overlaps with a remote subnet of a vRouter interconnection. The subnet of the Layer 3 DC interconnection must be covered by the overlapping subnet of the vRouter interconnection. · The remote subnets overlap with the subnets of the vRouter. · The remote subnet cannot be configured when the firewall service is disabled. · Invalid packet encapsulation type. · The specified subnet doesn't exist. · The specified subnet is not bound to the vRouter. · The mapping segment ID is required. · The VDS doesn't exist. · The mapping segment ID is out of range. · The mapping segment ID is already used. · Invalid export target. · The Layer 3 DC export target is required. · The Layer 3 DC interconnection ID has already been used. · Invalid import target. · The Layer 3 DC import target is required. · The export target conflicts with the export target of a Layer 2 DC interconnection. · The export target conflicts with the export target of a Layer 3 DC interconnection. · The VPN instance name is already used. Please modify the mapping segment ID. · You can configure the same mapping segment ID for multiple Layer 3 DC interconnections using different vRouters only when all these interconnections are enabled with the firewall service. · The Layer 3 DC interconnection name cannot exceed 255 characters. · The Layer 3 DC interconnection description cannot exceed 255 characters. · Some remote subnets overlap with the remote subnets of other Layer 3 DC interconnections of the vRouter. · The mapping segment ID has been used by another Layer 3 DC interconnection of the vRouter. · For two Layer 3 DC interconnections configured with the same mapping segment ID, their remote subnets and local subnets cannot both overlap. · For two Layer 3 DC interconnections configured with the same mapping segment ID, the remote subnets of one Layer 3 DC interconnection cannot overlap with the local subnets of the other Layer 3 DC interconnection. · The network to which the local subnet belongs cannot be a VLAN. · The local subnet cannot be an external subnet. · When two Layer 3 DC interconnections of the same vRouter are both not enabled with the firewall function, the local subnets cannot overlap. · The import RTs of Layer 3 DC interconnections configured with the same mapping segment ID must be the same, and so must the export RTs. · The vRouter does not bind a gateway or the gateway bound to the vRouter is not assigned with a data center interconnection network IP address. · Unknown error.

Update Layer 3 DC interconnection

Keyword	UPDATE_L3DCICONNECT_OP
Message text	Updated Layer 3 DC interconnection "$1".
Variable fields	$1: Layer 3 DC interconnection name.
Example	Updated Layer 3 DC interconnection "l3-dci-connect".
Explanation	A Layer 3 DC interconnection 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. · The name cannot be modified. · The vRouter ID cannot be modified. · The firewall service status cannot be modified. · The logical firewall cannot be modified. · The packet encapsulation type cannot be modified. · The local subnet ID is required. · The specified subnet does not exist. · The specified subnet is not bound to the vRouter. · A remote subnet of the Layer 3 DC interconnection overlaps with a remote subnet of a vRouter interconnection. · The mapping segment ID is required. · A remote subnet of the Layer 3 DC interconnection overlaps with a remote subnet of a vRouter interconnection. The subnet of the Layer 3 DC interconnection must be covered by the overlapping subnet of the vRouter interconnection. · The remote subnet is required when the firewall service is enabled. · The remote subnets overlap with the subnets of the vRouter. · The remote subnet cannot be configured when the firewall service is disabled. · Invalid import target. · Invalid export target. · The Layer 3 DC import target is required. · The Layer 3 DC export target is required. · The export target conflicts with the export target of a Layer 2 DC interconnection. · The export target conflicts with the export target of a Layer 3 DC interconnection. · You can configure the same mapping segment ID for multiple Layer 3 DC interconnections using different vRouters only when all these interconnections are enabled with the firewall service. · The Layer 3 DC interconnection description cannot exceed 255 characters. · Some remote subnets overlap with the remote subnets of other Layer 3 DC interconnections of the vRouter. · The mapping segment ID has been used by another Layer 3 DC interconnection of the vRouter. · For two Layer 3 DC interconnections configured with the same mapping segment ID, their remote subnets and local subnets cannot both overlap. · For two Layer 3 DC interconnections configured with the same mapping segment ID, the remote subnets of one Layer 3 DC interconnection cannot overlap with the local subnets of the other Layer 3 DC interconnection. · The network to which the local subnet belongs cannot be a VLAN. · The local subnet cannot be an external subnet. · When two Layer 3 DC interconnections of the same vRouter are both not enabled with the firewall function, the local subnets cannot overlap. · The import RTs of Layer 3 DC interconnections configured with the same mapping segment ID must be the same, and so must the export RTs. · Unknown error.

Delete Layer 3 DC interconnection

Keyword	DELETE_L3DCICONNECT_OP
Message text	Deleted Layer 3 DC interconnection "$1".
Variable fields	$1: Layer 3 DC interconnection name.
Example	Deleted Layer 3 DC interconnection "l3-dci-connect".
Explanation	A Layer 3 DC interconnection was deleted.
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. · Unknown error.

Add subnet to Layer 3 DC interconnection

Keyword	ADD_L3DCICONNECTSUBNET_OP
Message text	Added subnet "$1" to Layer 3 DC interconnection "$2"
Variable fields	$1: Local subnet name. $2: Layer 3 DC interconnection name.
Example	Added subnet "subnet 1" to Layer 3 DC interconnection "l3-dci-connect 2"
Explanation	A local subnet was added to a Layer 3 DC interconnection.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · The subnet ID was null. · The router ID is required. · The specified subnet doesn't exist. · The specified subnet is not bound to the vRouter. · The specified vRouter doesn't exist. · The subnet has already been bound to the Layer 3 DC interconnection. · The request is invalid. · The specified resource doesn't exist. · Unknown error.

Delete Layer 3 DC interconnection subnet

Keyword	DELETE_L3DCICONNECTsubnet_OP
Message text	Deleted subnet "$1" from Layer 3 DC interconnection "$2"
Variable fields	$1: Local subnet name. $2: Layer 3 DC interconnection name.
Example	Deleted subnet "interface 1" from Layer 3 DC interconnection "l3-dci-connect 2"
Explanation	A local subnet was deleted from a Layer 3 DC interconnection.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · The subnet ID is required. · The vRouter ID is required. · The specified subnet doesn't exist. · The specified vRouter doesn't exist. · The subnet is not bound to the Layer 3 DC interconnection. · The specified subnet is not bound to the vRouter. · The specified resource is not exist. · The request is invalid. · Unknown error.

Upload the vSwitch license file

Keyword	UPLOAD_LICENSE_OP
Message text	Uploaded the vSwitch license file.
Variable fields	N/A
Example	Uploaded the vSwitch license file.
Explanation	A local vSwitch license file was uploaded.
Possible failure causes	· Failed to upload the file. · License file error. · Configuration recovery is in progress.

Updated host load limit

Keyword	UPDATE_HOSTLOADLIMIT_OP
Message text	Updated host load limit “$1”.
Variable fields	$1: Host IP address.
Example	Updated host load limit “98.0.25.103”.
Explanation	The vSwitch bridge configuration of a host was modified.
Possible failure causes	· The max packet-in packet rate is invalid. · The host version does not support the max packet-in packet rate parameter. · The flow entry aging acceleration threshold is invalid. · The host version does not support the flow entry aging acceleration threshold parameter. · Failed to deploy the max packet-in packet rate to the host. · Failed to deploy the flow entry aging acceleration threshold to the host. · ESXi hosts do not support the max packet-in packet rate or flow entry aging acceleration threshold parameter. · The request is invalid. · Unknown error. · The specified resource doesn't exist.

H3C SeerEngine-Campus Operation Log Messages Reference-E65XX-5W100

Campus

Create isolation domain

Update isolation domain

Delete isolation domain

Update private network

Delete private network

Create security group

Create subnet

Update subnet

Delete subnet

Create radar detection task

Delete radar detection task

Back up configuration

Upload backup file

Download backup file

Modify configuration

Create Fabric