Download Book

Title	Size	Downloads
H3C SeerEngine-DC Operation Log Messages Reference-E37xx-5W702-book.pdf	3.63 MB

Table of Contents

H3C SeerEngine-DC Operation Log Messages Reference-E37xx-5W702

Related Documents

H3C SeerEngine-DC

Operation Log Messages Reference

Document version: 5W702-20220219

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

Create BGP instance· 8

Update BGP instance· 10

Delete BGP instance· 11

Synchronize route· 11

Update NQA· 12

Synchronized injected route configuration and learned route configuration to vBGP· 12

BSM·· 13

Create mapping table of access network· 13

Update mapping table of access network· 14

Delete mapping table of access network· 14

Modify inspection port status· 15

Bound working port to mapping table· 16

Unbound working port to mapping table· 17

Add default access VLAN· 18

Delete default access VLAN· 19

Create mapping table of service network· 19

Update mapping table of service network· 20

Delete mapping table of service network· 20

Bound mapping table to device· 21

Updated binding relationship between mapping table and device· 22

Delete bindings between mapping table and all devices· 23

Bound port to mapping table· 24

Update binding relationship between port and mapping table· 25

Deleted bindings between mapping table and all ports· 26

CAPACITY·· 27

Execute capacity simulation task· 27

Get simulation config change task· 28

Interrupt capacity simulation task· 28

CLOSE_LOOP·· 29

Update SeerAnalyzer info· 30

Delete SeerAnalyzer info· 31

Close event 31

Deploy solution· 32

Undeploy solution· 34

CON_CERTM·· 35

Import a certificate· 35

Delete a certificate· 35

Export a certificate· 36

Activate a certificate for a service· 36

Deactivate certificates for a service· 37

Update alarm config· 37

CON_NetworkMonitor 39

Change thresholds for a CPU· 40

Change thresholds for all CPUs· 41

CON_OPENFLOW··· 42

Create flow table entry· 42

Modify flow table entry· 42

Delete flow table entry· 43

Delete group table entry· 43

Devices change to fail-safe mode· 43

Devices change to normal mode· 44

Modify interface status by interface index· 44

Single device change to fail-safe mode· 45

Single device change to normal mode· 46

CON_ROUTERCONFIGS·· 50

Add BGP instance· 50

Delete BGP instance· 51

Add BGP network route· 51

Delete BGP network route· 52

Add BGP neighbor 53

Delete BGP neighbor 54

Update BGP session settings· 55

Add OSPF instance· 56

Delete OSPF instance· 56

Add OSPF network route· 57

Delete OSPF network route· 58

Add OSPF area· 59

Delete OSPF area· 60

CON_SNMP·· 61

Create traditional NE· 61

Update traditional NE· 62

Delete traditional NE· 62

Start scanning traditional NE· 63

Stop scanning traditional NE· 63

CON_SYSTEM·· 64

Back up configuration· 64

Upload backup file· 64

Start recovery· 65

Download backup file· 65

Modify backup settings· 66

Modify configuration· 66

Restore configuration· 67

Prepare for upgrade· 67

Modify alert log remote transmission mode· 68

Modify audit log transmission mode· 68

Enter upgrade mode· 68

Quit upgrade mode· 69

Update device layer 74

Delete inactive link· 75

Update port thresholds· 75

Clear events on a device· 76

Clear events on all devices· 76

Create server link· 76

Delete server link· 77

Import server link· 77

CON_USER·· 78

Add a user 78

Delete a user 78

Change user password· 79

Update user config· 80

Create custom site· 85

Update custom site· 85

Delete custom site· 86

Create custom outgoing external flow· 86

Update custom outgoing external flow· 87

Delete custom outgoing external flow· 88

Create custom service flow· 88

Update custom service flow· 89

Delete custom service flow· 89

Create Fabric Connection· 96

Update Fabric Connection· 98

Delete Fabric Connection· 99

FWaaS·· 100

Create time range· 100

Update time range· 101

Delete time range· 102

Create firewall object group· 102

Update firewall object group· 103

Delete firewall object group· 104

Create firewall object 105

Update firewall object 106

Delete firewall object 107

Create firewall rule· 108

Update firewall rule· 109

Delete firewall rule· 110

Create firewall policy· 111

Update firewall policy· 112

Delete firewall policy· 112

Create firewall 113

Update firewall 115

Delete firewall 116

Create IPS policy· 117

Update IPS policy· 117

Delete IPS policy· 118

Create IPS template· 118

Update IPS template· 119

Delete IPS template· 119

Upload IPS signature library from local device· 120

Create AV policy· 120

Update AV policy· 121

Delete AV policy· 121

Create AV template· 122

Update AV template· 123

Delete AV template· 123

Upload virus library from local device· 124

Upload application library from local device· 124

Create attack defense policy· 125

Update attack defense policy· 125

Delete attack defense policy· 126

Create URL filter category· 126

Update URL filter category· 127

Delete URL filter category· 127

Create URL filter rule· 128

Update URL filter rule· 128

Delete URL filter rule· 129

Create URL filter policy· 129

Update URL filter policy· 130

Delete URL filter policy· 130

LBaaS·· 132

Create load balancer 133

Update load balancer 135

Delete load balancer 136

Create health monitor 161

Update health monitor 162

Delete health monitor 163

Bind health monitor 163

Unbind health monitor 164

NBAC·· 165

Create application description· 166

Update application description· 169

Delete application description· 171

Create VLAN-VXLAN mapping table· 177

Update VLAN-VXLAN mapping table· 177

Delete VLAN-VXLAN mapping table· 178

Create QinQ-VXLAN mapping table· 179

Update QinQ-VXLAN mapping table· 180

Delete QinQ-VXLAN mapping table· 182

Bind VLAN-VXLAN mapping table· 182

Update VLAN-VXLAN mapping table binding· 183

Delete VLAN-VXLAN mapping table binding· 184

Bind ports to VLAN-VXLAN mapping table· 184

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

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

Bind ports to QinQ-VXLAN mapping table· 186

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

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

Create VLAN-network mapping table· 188

Update VLAN-network mapping table· 189

Delete VLAN-network mapping table· 189

Bind ports to VLAN-network mapping table· 190

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

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

Create border device group· 192

Update border device group· 194

Delete border device group· 196

Create IP address pool 197

Update IP address pool 199

Delete IP address pool 200

Create border device group VLAN range· 201

Update border device group VLAN range· 201

Delete border device group VLAN range· 202

Create VXLAN pool 202

Update VXLAN pool 203

Delete VXLAN pool 204

Create physical NE· 204

Update physical NE· 207

Delete physical NE· 210

Batch add physical NEs· 210

Start scanning physical NE· 211

Stop scanning physical NE· 211

Start migration on physical gateway· 211

Complete migration on physical gateway· 212

Start data synchronization on physical NE· 212

Start configuration auditing on physical NE· 213

Start data synchronization on virtual NE· 213

Start configuration auditing on virtual NE· 214

Update VNF device· 215

Create NETCONF default user 216

Edit BFD settings· 216

Configure default MAC address· 217

Delete default MAC address· 217

Create third party NE· 217

Delete third party NE· 218

Configure reserved option· 219

Create address pool 219

Update address pool 220

Delete address pool 221

Add resource· 221

Delete resource· 223

Configure VNFM·· 224

Configure gateway network· 224

Update gateway network· 225

Router bound to gateway· 225

Router unbound to gateway· 227

Add vRouter to resource· 227

Create aggregation group member 228

Update aggregation group member 229

Delete aggregation group member 229

Create aggregation group· 230

Update aggregation group· 230

Delete aggregation group· 231

Create global aggregation group configuration· 231

Update global aggregation group configuration· 232

Delete global aggregation group configuration· 233

Delete NE VXLAN tunnels· 233

Create connection limit rule· 234

Update connection limit rule· 234

Delete connection limit rule· 235

Create device configuration template· 236

Update device configuration template· 240

Delete device configuration template· 244

Create control protocol template· 244

Update control protocol template· 245

Delete control protocol template· 246

Create deploy resource pool 246

Update deploy resource pool 249

Delete deploy resource pool 251

Create auto detected· 251

Stop auto detected· 252

Delete auto detected· 252

Update global setting· 253

Update Security global setting· 253

Create manual backup· 254

Create DHCP server 254

Update DHCP server 255

Delete DHCP server 255

Upload software· 256

Update software· 256

Delete software· 257

Upgrade softeware· 258

Replace physical NE· 258

Create tenant-gateway binding relationship· 260

Update tenant-gateway binding relationship· 261

Delete tenant-gateway binding relationship· 261

Create gateway· 262

Update gateway· 263

Delete gateway· 264

Create gateway member 265

Update gateway member 266

Delete gateway member 267

Create device information· 267

Update device information· 268

Delete device information· 269

Create link information· 270

Update link information· 271

Delete link information· 271

Import device list 272

Delete assetlist 272

Synchronization device bridgeMac and serialNumber info· 273

Create DC connection· 274

Update DC connection· 275

Delete DC connection· 275

Create replacement task· 276

Delete replacement task· 277

Create BGP neighbor 278

Update BGP neighbor 280

Delete BGP neighbor 281

Create border interface· 282

Update border interface· 283

Delete border interface· 284

Created cloud private line· 285

Updated cloud private line· 286

Deleted cloud private line· 287

Create SSM mapping· 295

Delete SSM mapping· 296

Create SSM mapping rule· 296

Delete SSM mapping rule· 297

Create multicast source· 298

Delete multicast source· 299

Create MSDP peer 300

Update MSDP peer 301

Delete MSDP peer 302

Create BUM multicast replication profile· 303

Update BUM multicast replication profile· 304

Delete BUM multicast replication profile· 305

Create interface-specific multicast network· 306

Update interface-specific multicast network· 308

Delete interface-specific multicast network· 309

Create PIM template· 310

Update PIM template· 311

Delete PIM template· 311

Create IGMP template· 312

Update IGMP template· 313

Delete IGMP template· 314

Create DR group· 314

Delete DR group· 315

Start fine-grained data synchronization on physical device· 315

Create DR System·· 316

Update DR System·· 318

Delete DR System·· 319

Create LAG Group· 320

Delete LAG Group· 320

Create User-Defined Device Info· 321

Delete User-Defined Device Info· 322

Create address prefix· 322

Update address prefix· 323

Delete address prefix· 324

Create address prefix rule· 325

Update address prefix rule· 326

Delete address prefix rule· 327

Create routing policy· 328

Update routing policy· 329

Delete routing policy· 330

Create routing policy node· 331

Update routing policy node· 332

Delete routing policy node· 333

Create OSPF policy· 334

Update OSPF policy· 335

Delete OSPF policy· 336

Create OSPFv3 policy· 337

Update OSPFv3 policy· 338

Delete OSPFv3 policy· 339

Create OSPF area· 340

Update OSPF area· 341

Delete OSPF area· 342

Create OSPFv3 area· 343

Update OSPFv3 area· 344

Delete OSPFv3 area· 345

Create OSPF route redistribution rule· 346

Update OSPF route redistribution rule· 347

Delete OSPF route redistribution rule· 348

Create OSPFv3 route redistribution rule· 349

Update OSPFv3 route redistribution rule· 350

Delete OSPFv3 route redistribution rule· 351

Create OSPF interface policy· 352

Update OSPF interface policy· 353

Delete OSPF interface policy· 354

Create OSPFv3 interface policy· 355

Update OSPFv3 interface policy· 356

Delete OSPFv3 interface policy· 357

Create OSPF policy application· 358

Update OSPF policy application· 359

Delete OSPF policy application· 360

Create OSPFv3 policy application· 361

Update OSPFv3 policy application· 362

Delete OSPFv3 policy application· 363

Update policy application· 364

Delete policy application· 365

Create configuration audit task· 366

Update configuration audit task· 367

Delete configuration audit task· 368

Execute one-off configuration audit task· 369

Manually trigger periodic configuration audit task once· 370

Create third-party service device· 371

Update third-party service device· 373

Delete third-party service device· 374

Resource bind NQA· 374

Resource unbind NQA· 374

Create port PVIDs· 375

Update port PVIDs· 376

Delete port PVIDs· 377

Delete port PVID·· 378

Clear auto discovered device list 378

Refreshed lock configuration successfully· 379

Failed to refresh lock configuration because of parameter errors· 379

Failed to refresh lock configuration because of module service conflicts· 380

Locked multiple devices in bulk successfully· 380

Failed to lock multiple devices in bulk because of parameter errors· 381

Failed to lock device because of module service conflicts· 381

Unlocked multiple devices in bulk successfully· 382

Failed to unlock multiple devices in bulk because of parameter errors· 382

Failed to unlock device because of module service conflicts· 383

Create DRNI information· 384

Update DRNI information· 385

Delete DRNI information· 386

Batch delete DRNI informations· 387

Create DRNI routed IPL· 388

Update DRNI routed IPL· 390

Delete DRNI routed IPL· 391

Create BGP Network· 392

Update BGP Network· 393

Delete BGP Network· 394

NEYANGM·· 395

Download YANG files· 395

Get YANG files from NE· 395

Set YANG files identifier 396

Start data synchronization on device· 399

Start configuration audit on device· 399

Create template· 400

Delete template· 403

Create NGFW resource· 404

Update NGFW resource· 406

Delete NGFW resource· 407

Create resource pool 408

Update resource pool 409

Delete resource pool 410

Set default user 410

OAM·· 411

Create radar detection task· 411

Delete radar detection task· 413

Clear periodic radar detection tasks· 413

Create Network Check· 414

Cancel Network Check· 414

Upload image file· 415

Update image file· 415

Bulk delete image file· 416

Retrieve device disk partitions· 416

Sync image file· 417

Upgrade image file· 418

Delete upgrade record· 419

Suspend upgrade· 419

Restart upgrade· 420

Configure scheduled upgrade· 421

Delete scheduled upgrade· 422

ISSU upgrade image file· 423

Create replacement task· 425

Delete replacement task· 426

Create configuration file backup task· 426

Restore device· 427

Upload config file· 427

Configure scheduled backup· 428

Delete config file· 428

Start data check· 429

Stop data check· 429

Modify interface status by interface index· 430

Start one-click check· 430

Stop one-click check· 431

Update check setttings· 431

Create restore point 432

Update restore point 432

Delete restore point 433

Create rollback record· 433

Roll back device· 434

RCAM·· 435

Create resource access template· 435

Delete resource access template· 436

RDR·· 437

Create RDR system·· 437

Update RDR system·· 438

Delete RDR system·· 438

Fix RDR system·· 438

Create RDR relation· 439

Delete RDR relation· 439

Component switched to primary role· 440

Component switched to backup role· 440

SEERENGINE·· 441

Create rate limit profile· 441

Update rate limit profile· 442

Delete rate limit profile· 443

Create mirroring destination profile· 444

Update mirroring destination profile· 445

Delete mirroring destination profile· 446

Create classifier 446

Update classifier 448

Delete classifier 449

Create flow policy· 450

Update flow policy· 451

Delete flow policy· 451

Create physical port policy· 452

Update physical port policy· 454

Delete physical port policy· 455

Create mirroring profile· 456

Update mirroring profile· 457

Delete mirroring profile· 458

Update default VXLAN· 458

Create congestion management profile· 459

Update congestion management profile· 460

Delete congestion management profile· 461

Create GTS profile· 462

Update GTS profile· 463

Delete GTS profile· 464

ServiceChain· 465

Create service chain· 466

Update service chain· 469

Delete service chain· 471

Create context 472

Update context 474

Delete context 475

Create service path· 476

Update service path· 478

Delete service path· 480

Create detection task· 481

Update detection task· 482

Delete detection task· 483

Update service chain settings for a tenant 483

SIMULATION·· 484

Create network-wide impact analysis task· 484

Refresh network-wide impact analysis task· 485

Create connectivity test task· 486

Stop simulation task· 487

Enable tenant design mode· 487

Disable tenant design mode· 488

Receive request to deploy services to tenant 514

Deploy services to tenant 515

SIMULATION_NETWORK·· 516

Start simulation network model creation task· 516

Start simulation network model update task· 517

Start simulation network model deletion task· 518

Start vPort creation task· 519

Start vPort deletion task· 520

Create PKI domain· 526

Update PKI domain· 527

Delete PKI domain· 528

Create SSL policy· 529

Update SSL policy· 530

Delete SSL policy· 531

Create SSL VPN gateway· 532

Update SSL VPN gateway· 533

Delete SSL VPN gateway· 534

Create IP address pool 535

Update IP address pool 537

Delete IP address pool 538

Create SSL VPN context 539

Update SSL VPN context 541

Delete SSL VPN context 542

Create route list 543

Update route list 544

Delete route list 545

Create policy group· 546

Update policy group· 547

Delete policy group· 548

Create SSL VPN user 549

Update SSL VPN user 550

Delete SSL VPN user 551

Create user group· 552

Update user group· 553

Delete user group· 554

Update gRPC common information· 557

Create gRPC device· 558

Update gRPC device· 559

Delete gRPC device· 560

Create INT device· 560

Update INT device· 561

Delete INT device· 561

Create INT node· 562

Update INT node· 563

Delete INT node· 564

Create ERSPAN device· 565

Update ERSPAN device· 566

Delete ERSPAN device· 567

Create telemetry stream profile· 568

Update telemetry stream profile· 569

Delete telemetry stream profile· 570

Create third-party service device· 574

Update third-party service device· 575

Delete third-party service device· 576

Create third-party service· 576

Update third-party service· 577

Delete third party service· 577

Create vRouter link· 582

Delete vRouter link· 583

Create QoS profile· 588

Update QoS profile· 589

Delete QoS profile· 590

Create VDS distributed port group· 591

Update VDS distributed port group· 593

Delete VDS distributed port group· 594

Sync vCenter data· 595

Sync vPort data of vCenter 595

Updated auto audit and sync settings of vCenter 596

Audit vCenter 597

Export vCenter difference details· 597

Create interface availability zone· 598

Delete interface availability zone· 599

Update interface availability zone· 600

Discover data of vCenter 601

Pull and incorporate data from vCenter 601

Create logical network· 606

Delete logical network· 607

Audit data for RHVM·· 607

Sync data for RHVM·· 608

Detect data on RHVM·· 608

Pull and incorporate data from RHVM·· 609

Update auto audit and sync settings of RHVM·· 610

Create OpenStack-based cloud platform·· 611

Update OpenStack-based cloud platform·· 613

Delete OpenStack-based cloud platform·· 615

Sync data of OpenStack-based cloud platform·· 615

Update auto audit and sync settings of OpenStack-based cloud platform·· 616

Audit data of OpenStack-based cloud platform·· 617

Create agent 618

Synchronized agents· 619

Create floating IP· 637

Update floating IP· 639

Delete floating IP· 641

Create mirroring destination profile· 657

Update mirroring destination profile· 658

Delete mirroring destination profile· 659

Create mirroring profile· 660

Update mirroring profile· 661

Delete mirroring profile· 662

Create BGP neighbor 663

Update BGP neighbor 665

Delete BGP neighbor 666

Create route entry· 667

Delete extended route entry· 670

Delete route entry· 671

Create VPC connection· 681

Update VPC connection· 683

Delete VPC connection· 685

Create security group· 686

Update security group· 687

Delete security group· 688

Create security group rule· 689

Update security group rule· 690

Delete security group rule· 691

Create VLAN-VXLAN mapping· 692

Delete VLAN-VXLAN mapping· 693

Create IKE policy· 703

Delete IKE policy· 703

Update IKE policy· 704

Create IPsec policy· 705

Delete IPsec policy· 705

Update IPsec policy· 706

Create VPN service· 707

Delete VPN service· 707

Update VPN service· 708

Create IPsec Site Connections· 709

Delete IPsec Site Connection· 710

Update IPsec Site Connections· 711

Create IPsec site connection peer CIDR· 712

Delete IPsec site connection peer CIDR· 712

Create internal route· 725

Delete internal route· 726

Create interface· 726

Delete interface· 728

Create security policy· 737

Update security policy· 738

Delete security policy· 738

Create floating IP· 739

Update floating IP· 740

Delete floating IP· 741

Create port group· 741

Update port group· 742

Delete port group· 742

Create security rules· 743

Update security rule· 744

Delete security rule· 744

Authenticate with vCenter 745

Disconnect with vCenter 745

Create router link· 754

Update router link· 755

Delete router link· 755

Create route table· 755

Update route table· 756

Delete route table· 756

Create route entry· 757

Update route entry· 758

Delete route entry· 759

Create APP cluster VIP· 759

Update APP cluster VIP· 760

Delete APP cluster VIP· 760

Create flooding domain· 761

Update flooding domain· 761

Delete flooding domain· 762

Update vCenter status· 762

Create port name prefix· 763

Delete port name prefix· 763

Updated the global configuration of the controller 764

Create netoverlay host 764

Delete netoverlay host 764

Update netoverlay host 765

Create netoverlay group· 765

Delete netoverlay group· 765

Create VLAN-VXLAN map· 766

Delete VLAN-VXLAN map· 766

Configure batch vSwitch deployment parameters· 767

Import host file· 767

Run custom script 767

Export host file· 768

Export SSH key· 768

Upload custom script 768

Install vSwitch· 769

Update vSwitch· 769

Uninstall vSwitch· 769

Check host status· 770

Upload vSwitch file· 770

Delete vSwitch file· 770

Create network nodes· 771

Update network node· 771

Delete network node· 771

Update global default action· 772

Create DFW policy· 772

Update DFW policy· 773

Delete DFW policy· 773

Create DFW policy rule· 773

Delete DFW policy rule· 775

Create DFW IP set 775

Update DFW IP set 775

Delete DFW IP set 776

Create DFW IP set rule· 776

Delete DFW IP set rule· 777

Track flow entry of IP packet 777

Track flow entry of ARP packet 778

Start auditing on host 779

Start synchronization to host 779

Start auditing OVSDB configuration on host 780

Start synchronization OVSDB configuration on host 780

Start auditing DHCP configuration on host 781

Start synchronization DHCP configuration to host 781

Created static link· 782

Deleted static link· 782

Create vRouter interconnection· 782

Update vRouter interconnection· 784

Delete vRouter interconnection· 785

Create Layer 2 DC interconnection· 785

Update Layer 2 DC interconnection· 786

Delete Layer 2 DC interconnection· 787

Create Layer 3 DC interconnection· 788

Update Layer 3 DC interconnection· 789

Delete Layer 3 DC interconnection· 791

Create Layer 3 DC interconnection extra· 792

Update Layer 3 DC interconnection extra· 793

Delete Layer 3 DC interconnection extra· 793

Add subnet to Layer 3 DC interconnection· 793

Delete Layer 3 DC interconnection subnet 794

Upload the vSwitch license file· 794

Updated host load limit 795

Created subports· 799

Deleted subports· 799

Update Network Cloud feature· 800

Download audit difference· 800

Import hosts· 801

Batch delete hosts· 802

Create DHCP host group· 802

Update DHCP host group· 803

Delete DHCP host group· 803

Create DHCP resource pool 804

Update DHCP resource pool 805

Delete DHCP resource pool 805

Add DHCP host group to DHCP resource pool 806

Delete DHCP host group from DHCP resource pool 806

Update uplink port name· 807

Back up flow tables· 807

Restore flow tables· 808

Update settings· 808

Update the auto identification of vPorts without host IDs in network overlay feature· 809

Create NQA profile· 809

Update NQA profile· 810

Delete NQA profile· 810

Exported floating IPs· 810

Introduction

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

This document assumes that the readers are familiar with data communications technologies and controller products.

Viewing operation log messages

1. Log in to SNA Center.

2. Click Settings in the System area.

3. On the top navigation bar, click Logs.

4. From the left navigation pane, select Information.

5. Click the Operation Logs tab.

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

Figure 1 Operation log message list

Table 1 Operation log element

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

Syslog message format

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

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

<PRI>TIMESTAMP Hostname Origin/severity/Keywords CONTENT

Table 2 Syslog message elements

Element	Description
<PRI>	Priority identifier. It is calculated by using the following formula: Priority identifier=facilityx8+severity Where: · Facility represents the programming module defined by syslog. In the current software version, the facility is user-level and its value is 1. · Severity represents the syslog message severity level. For more information, see Table 4.
TIMESTAMP	Date and time when the event occurred.
Hostname	Name or IP address of the host that produced the message.
Origin	Name of the service module that produced the message.
severity	Severity level of the message. For more information, see Table 5. For more information about the mappings between operation log message severity levels and syslog message severity levels, see Table 6.
Keywords	Keywords of the message that facilitate searching or memorizing.
CONTENT	Text string that contains detailed information about the operation, in the following format: -Module="module name"-UserIp=" user IP"-UserName="username"-OperResult="result"-Reason="operation failure causes"

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

Table 3 Service module list

Service module name	Description
BGP	BGP module.
BSM	Bare metal server module.
CLOSE_LOOP	Issues module.
CON_AUTH	Authentication management module.
CON_CERTM	Certificate management module.
CON_LICENSE	License management module.
CON_LISTENER	Listener module.
CON_NetworkMonitor	Network monitoring module.
CON_OPENFLOW	OpenFlow module.
CON_REGION	Region module.
CON_ROUTERCONFIGS	Route configuration module.
CON_SNMP	SNMP module.
CON_SYSTEM	System management module.
CON_TEAM	Team module.
CON_TOPOLOGY	Topology management module.
CON_USER	User management module.
DataCheck	Data check module.
DNEC	DNEC module.
Fabric	Fabric module.
FWaaS	Firewall service module.
Global	Global configuration nodule.
IDM	Integrated deployment module.
LBaaS	Load balancing module.
NBAC	NBAC module.
NEM	Carrier network module.
NEYANGM	NEYANG manager module.
OAM	OAM module.
NGFWM	NGFW manager module.
RCAM	Resource access template module.
RDR	Remote disaster recovery module.
SEERENGINE	SEERENGINE module.
ServiceChain	Service chain module.
SSLVPNaaS	SSL VPN service module.
Tenant	Tenant module.
TPFW	Third-party firewall module.
VMM	Virtual networking module.
VPNaaS	IPsec VPN service 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 categories operation log messages by service module. This document explains messages in tables. Table 7 describes information provided in these tables.

Table 7 Message explanation table contents

Item	Content	Example
Keyword	Summary of the message that facilitates searching or memorizing.	UPLOAD_APP_OP
Message text	Presents the message description.	Uploaded application: $1.
Variable fields	Briefly describes the variable fields in the order that they appear in the message text. The variable fields are numbered in the "$Number" form to help you identify their location in the message text.	$1: Name of the application installation package.
Example	Provides a real message example.	Uploaded application: arp-2156.zip.
Explanation	Explains the message.	An application installation package was uploaded.
Possible failure causes	Provides possible causes of an operation failure.	· The application already exists.

BGP

This section contains BGP messages.

Create BGP cluster

Keyword	CREATE_BGP_CLUSTER_OP
Message text	Created BGP cluster: $1
Variable fields	$1: BGP cluster information.
Example	Created BGP cluster: name: [BGPcluster1] member_ips: [“1.1.1.1”,”1.1.1.2”]
Explanation	A BGP cluster was created.
Possible failure causes	· The BGP clusters created in bulk cannot use the same ID. · The management IP is required. · The management IP is invalid. · Member IPs are required. · A maximum of two member IPs are supported. · The member IPs cannot be identical. · The request is invalid. · Unknown error. · The parameter (%s) is required. · The parameter (%s) is invalid. · The parameter (%s) can't exceed 255 characters. · The controller is not the active leader. · Configuration recovery is in progress. · You have no privilege to perform this operation. · Invalid ID.

Update BGP cluster

Keyword	UPDATE_BGP_CLUSTER_OP
Message text	Updated BGP cluster: $1.
Variable fields	$1: BGP cluster information.
Example	Updated BGP cluster: name: [BGPcluster1] member_ips: [“1.1.1.1”,”1.1.1.2”]
Explanation	A BGP cluster was modified.
Possible failure causes	· The management IP is required. · The management IP is invalid. · Member IPs are required. · A maximum of two member IPs are supported. · The member IPs cannot be identical. · A minimum of one master IP is required. · The request is invalid. · Unknown error. · The parameter (%s) can't be modified. · The parameter (%s) is required. · The parameter (%s) is invalid. · The parameter (%s) can't exceed 255 characters. · The controller is not the active leader. · Configuration recovery is in progress. · You have no privilege to perform this operation. · The BGP cluster is in shared mode and has been bound to a BGP instance. You cannot change its sharing mode to exclusive.

Delete BGP cluster

Keyword	DELETE_BGP_CLUSTER_OP
Message text	Deleted BGP cluster: $1
Variable fields	$1: BGP cluster name.
Example	Deleted BGP cluster: 218b5f2f-e435-4365-a1ab-0eaa03b7fa19
Explanation	A BGP cluster was deleted.
Possible failure causes	· The controller is not the active leader. · You have no privilege to perform this operation. · You cannot delete this cluster. It has been bound to a BGP instance.

Create BGP instance

Keyword	CREATE_BGP_INSTANCE_OP
Message text	Created BGP instance: $1
Variable fields	$1: BGP instance information.
Example	Created BGP instance: bgp_instance_name: [default] bgp_as_number: [65535] graceful_restart_timer: [15] bgp_peer_ip: [1.1.1.1] bgp_peer_as_number: [65535] graceful_restart_timer_extra: [no-limit] fabric_id: [7ffdcfab-3312-41ae-82cd-1a0547b359c1]
Explanation	A BGP instance was created.
Possible failure causes	· The BGP instances created in bulk cannot use the same ID. · The BGP instance ID is invalid. · The BGP peer IP is invalid. · The AS number is an integer in the range of 1 to 4294967295. · The BGP instance name is required. · The fabric ID is required. · The fabric doesn’t exist. · The BGP instance name is invalid. · The BGP instance name can't exceed 31 characters. · The GR timer is in the range of 3 to 600. · The GR timer is invalid. · The Extra GR timer is in the range of 0 to 86400. · The Extra GR timer is invalid. · Only one BGP instance is supported. · The request is invalid. · Unknown error. · The parameter (%s) can't be modified. · The parameter (%s) is required. · The parameter (%s) is invalid. · The parameter (%s) can't exceed 255 characters. · The controller is not the active leader. · Configuration recovery is in progress. · You have no privilege to perform this operation. · The BGP instance has been bound to a shared cluster. The maximum number of optimal routes must be equal to or higher than the number of BGP peers in the instance. · The specified BGP cluster does not exist. · The cluster has been bound to another BGP instance. · The AS number has been assigned to another BGP instance or BGP peer. · Invalid fabric ID. · The fabric has been bound to another BGP instance or BGP peer. · Invalid ID. · The peer IP address already exists in the BGP instance. · You cannot configure the ebgp_max_hop field when the sharing mode of the cluster is exclusive. · The value for the ebgp_max_hop field must be an integer in the range of 1 to 255. · The BGP instance is bound to a shared cluster. You can configure the maximum number of hops to a peer only if it uses a different AS number than any one of its BGP peers. · The cluster bound to the BGP instance is in shared mode.In this mode,make sure all BGP peers bound to the BGP instance have the same fabric ID and AS number. Alternatively, make sure each of the peers has a unique fabric ID and AS number. · Please make sure the AS number of the BGP peer is unique among all BGP instances bound to exclusive clusters and all BGP peers bound to shared clusters. · Please make sure the AS number of the BGP instance is unique among all BGP instances bound to exclusive clusters and all BGP peers bound to shared clusters. · The system has more than one BGP instance. Please bind this BGP instance to a BGP cluster. · Two or more BGP clusters exist. Please bind the BGP instance to a BGP cluste.

Update BGP instance

Keyword	UPDATE_BGP_INSTANCE_OP
Message text	Updated BGP instance: $1.
Variable fields	$1: BGP instance information.
Example	Updated BGP instance: bgp_instance_name: [default] bgp_as_number: [65535] graceful_restart_timer: [150] bgp_peer_ip: [1.1.1.1] bgp_peer_as_number: [65535] graceful_restart_timer_extra: [no-limit] fabric_id: [7ffdcfab-3312-41ae-82cd-1a0547b359c1]
Explanation	A BGP instance was modified.
Possible failure causes	· The BGP instance ID is invalid. · The BGP peer IP is invalid. · The AS number is an integer in the range of 1 to 4294967295. · The BGP instance name is required. · The fabric ID is required. · The fabric doesn’t exist. · The BGP instance name is invalid. · The BGP instance name can't exceed 31 characters. · The GR timer is in the range of 3 to 600. · The GR timer is invalid. · The Extra GR timer is in the range of 0 to 86400. · The Extra GR timer is invalid. · The request is invalid. · Unknown error. · The parameter (%s) can't be modified. · The parameter (%s) is required. · The parameter (%s) is invalid. · The parameter (%s) can't exceed 255 characters. · The controller is not the active leader. · Configuration recovery is in progress. · You have no privilege to perform this operation. · The BGP instance has been bound to a shared cluster. The maximum number of optimal routes must be equal to or higher than the number of BGP peers in the instance. · Invalid fabric ID. · The fabric has been bound to another BGP instance or BGP peer. · The peer IP address already exists in the BGP instance. · You cannot configure the ebgp_max_hop field when the sharing mode of the cluster is exclusive. · The value for the ebgp_max_hop field must be an integer in the range of 1 to 255. · The BGP instance is bound to a shared cluster. You can configure the maximum number of hops to a peer only if it uses a different AS number than any one of its BGP peers. · The cluster bound to the BGP instance is in shared mode.In this mode,make sure all BGP peers bound to the BGP instance have the same fabric ID and AS number. Alternatively, make sure each of the peers has a unique fabric ID and AS number. · Please make sure the AS number of the BGP peer is unique among all BGP instances bound to exclusive clusters and all BGP peers bound to shared clusters. · Please make sure the AS number of the BGP instance is unique among all BGP instances bound to exclusive clusters and all BGP peers bound to shared clusters.

Delete BGP instance

Keyword	DELETE_BGP_INSTANCE_OP
Message text	Deleted BGP instance: $1
Variable fields	$1: BGP instance name.
Example	Deleted BGP instance: [218b5f2f-e435-4365-a1ab-0eaa03b7fa19]
Explanation	A BGP instance was deleted.
Possible failure causes	· The controller is not the active leader. · You have no privilege to perform this operation.

Synchronize route

Keyword	SYNC_ROUTE_OP
Message text	Synchronized routes.
Variable fields	N/A
Example	Synchronized routes: node management ip: [1.1.1.1] instance name: [default]
Explanation	A user performed a configuration and route synchronization operation from the controller to vBGP.
Possible failure causes	· The management IP is invalid. · The BGP instance name is invalid. · You have no privilege to perform this operation.

Update NQA

Keyword	UPDATE_BGPNQAC_OP
Message text	Updated NQA: $1
Variable fields	$1: NQA configuration.
Example	Updated NQA: Northbound IP detection: on Probe timeout:"14" Frequency:"14" Probe failure consecutive times:"14".
Explanation	The NQA settings were updated.
Possible failure causes	· Token aged. · Cannot edit the NQA parameters when northbound IP detection is disabled. · The controller is not the active leader. · Please specify a probe timeout value. · The timeout value must be an integer in the range of 10 to 3600000. · Please specify a frequency value. · The frequency must be an integer in the range of 0 to 604800000. · Please specify the number of probe failure consecutive times. · The number of probe failure consecutive times must be an integer in the range of 1 to 16. · You have no privilege to perform this operation.

Synchronized injected route configuration and learned route configuration to vBGP

Keyword	SMOOTH_INJECTED_LEARNED_ROUTE_OP
Message text	Synchronized injected route configuration and learned route configuration to vBGP cluster $1.
Variable fields	$1: vBGP cluster name.
Example	Synchronized injected route configuration and learned route configuration to vBGP cluster test1.
Explanation	The controller synchronized injected route configuration and learned route configuration to a vBGP cluster.
Possible failure causes	· The controller is not the active leader. · The BGP cluster can contain only one primary node. · The NETCONF session to the BGP node is not up.

BSM

This section contains bare metal management module messages.

Create mapping table of access network

Keyword	CREATE_BSM_ACCESS_NETWORK_OP
Message text	Created a VLAN-VXLAN mapping table for the access network: $1.
Variable fields	$1: VLAN-VXLAN mapping table configuration information.
Example	Created a VLAN-VXLAN mapping table for the access network: Type: [VXLAN] Network: [INSPECTION] Default_PVID: [null] Domain: [ Name: [aaa] ID: [29577831-31d1-46e7-a33a-40f6ae6f4179] VLAN: [10] VXLAN: [100] ].
Explanation	A VLAN-VXLAN mapping table was created for the access network.
Possible failure causes	· Invalid JSON format. · Internal server error. · Please perform the operation on the active leader. · Configuration recovery is in progress. · Invalid mapping table name. · The VLAN ID is invalid or out of range. · The VXLAN ID is invalid or out of range. · The mapping table already exists. · You have no privilege to perform this operation.

Update mapping table of access network

Keyword	UPDATE_BSM_ACCESS_NETWORK_OP
Message text	Updated a VLAN-VXLAN mapping table of the access network: $1.
Variable fields	$1: VLAN-VXLAN mapping table configuration information.
Example	Updated a VLAN-VXLAN mapping table of the access network: Type: [VXLAN] Network: [WORKING] Default_PVID: [null] Domain: [ Name: [new_name] ID: [3a24b5b8-8fd1-492d-b867-88976c198d17] VLAN: [30] VXLAN: [300] ].
Explanation	A VLAN-VXLAN mapping table of the access network was modified.
Possible failure causes	· Invalid JSON format. · Internal server error. · Please perform the operation on the active leader. · Configuration recovery is in progress. · The mapping table does not exist. · Invalid mapping table name. · The VLAN ID is invalid or out of range. · The VXLAN ID is invalid or out of range. · The reserved VLAN ID conflicts with a VLAN ID of a VLAN-VXLAN mapping. · You have no privilege to perform this operation.

Delete mapping table of access network

Keyword	DELETE_BSM_ACCESS_NETWORK_OP
Message text	Deleted a VLAN-VXLAN mapping table from the access network: $1.
Variable fields	$1: ID of the VLAN-VXLAN mapping table.
Example	Deleted a VLAN-VXLAN mapping table from the access network: 3a24b5b8-8fd1-492d-b867-88976c198d17.
Explanation	A VLAN-VXLAN mapping table was deleted from the access network.
Possible failure causes	· Invalid JSON format. · Internal server error. · Please perform the operation on the active leader. · Configuration recovery is in progress. · The mapping table does not exist. · The mapping table has been bound to devices. · The mapping table has been bound to interfaces. · You have no privilege to perform this operation.

Modify inspection port status

Keyword	MODIFY_BSM_INSPECT_STATUS_OP
Message text	Modified states of inspection network interfaces: $1.
Variable fields	$1: Inspection network interface status.
Example	Modified states of inspection network interfaces: Port_status: [INACTIVE] Port_list: [ Device_type: [DEVICE_NAME], device_value: [TOR1], port_name: [GigabitEthernet1/0/1] ].
Explanation	The states of the inspection network interfaces were modified.
Possible failure causes	· Invalid JSON format. · Internal server error. · Please perform the operation on the active leader. · Configuration recovery is in progress. · Invalid interface list. · Invalid interface names exist. · Nonexistent devices are specified. · Invalid device MAC addresses exist. · Invalid device names exist. · Non-VTEP interfaces exist. · Interfaces not bound to the inspection network exist. · Interfaces bound to non-inspection networks exist. · You have no privilege to perform this operation.

Bound working port to mapping table

Keyword	CREATE_BSM_WORK_PORTBIND_OP
Message text	Bound working network interfaces to a VLAN-VXLAN mapping table: $1.
Variable fields	$1: Working network interface binding information.
Example	Bound working network interfaces to a VLAN-VXLAN mapping table: VLAN: [100] VXLAN: [1000] Domain_ID: [49df9c11-b06d-4910-bc54-5992a4459959] Domain_name: [working_100_1000] Port_list: [ Bond_mode: [4], info: [ Device_type: [DEVICE_NAME], device_value: [TOR1], port_name: [GigabitEthernet1/0/2] Device_type: [DEVICE_NAME], device_value: [TOR1], port_name: [GigabitEthernet1/0/3] ] Bond_mode: [4], info: [ Device_type: [DEVICE_NAME], device_value: [TOR2], port_name: [GigabitEthernet1/0/2] Device_type: [DEVICE_NAME], device_value: [TOR2], port_name: [GigabitEthernet1/0/3] ] ].
Explanation	Bound working network interfaces to a VLAN-VXLAN mapping table.
Possible failure causes	· Invalid JSON format. · Internal server error. · Please perform the operation on the active leader. · Configuration recovery is in progress. · The VLAN ID is invalid or out of range. · The VXLAN ID is invalid or out of range. · Invalid interface list. · Invalid interface names exist. · Nonexistent devices are specified. · Invalid device MAC addresses exist. · Invalid device names exist. · The default access VLAN does not exist. · Invalid interface list. · Non-VTEP interfaces exist. · Interfaces bound to other VLAN-VXLAN mapping tables exist. · Duplicate interfaces exist. · Interfaces already bound to the VLAN-VXLAN mapping table exist. · Interfaces bound to the inspection network exist. · You have no privilege to perform this operation. · The specified interface already exists in an interface and PVID mapping.

Unbound working port to mapping table

Keyword	DELETE_BSM_WORK_PORTBIND_OP
Message text	Unbound working network interfaces from a VLAN-VXLAN mapping table: $1.
Variable fields	$1: Working network interface binding information.
Example	Unbound working network interfaces from a VLAN-VXLAN mapping table: VLAN: [100] VXLAN: [1000] Domain_ID: [null] Domain_name: [null] Port_list: [ Bond_mode: [4], info: [ Device_type: [DEVICE_NAME], device_value: [TOR1], port_name: [GigabitEthernet1/0/2] Device_type: [DEVICE_NAME], device_value: [TOR1], port_name: [GigabitEthernet1/0/3] ] Bond_mode: [4], Info: [ Device_type: [DEVICE_NAME], device_value: [TOR2], port_name: [GigabitEthernet1/0/2] Device_type: [DEVICE_NAME], device_value: [TOR2], port_name: [GigabitEthernet1/0/3] ] ].
Explanation	Unbound working network interfaces from a VLAN-VXLAN mapping table.
Possible failure causes	· Invalid JSON format. · Internal server error. · Please perform the operation on the active leader. · Configuration recovery is in progress. · The VLAN ID is invalid or out of range. · The VXLAN ID is invalid or out of range. · Invalid interface list. · Invalid interface names exist. · Nonexistent devices are specified. · Invalid device MAC addresses exist. · Invalid device names exist. · The default access VLAN does not exist. · Invalid interface list. · Duplicate interfaces exist. · The mapping table does not exist. · Interfaces not bound to the working network exist. · Interfaces not bound to the VLAN-VXLAN mapping table exist. · Non-VTEP interfaces exist. · Duplicate interfaces exist. · The mapping table has been bound to devices. · The mapping table has been bound to interfaces. · You have no privilege to perform this operation.

Add default access VLAN

Keyword	CREATE_BSM_WORKING_VLAN_OP
Message text	Added a default access VLAN for the working network: $1.
Variable fields	$1: Default access VLAN.
Example	Added a default access VLAN for the working network: VLAN: [100].
Explanation	A default access VLAN was added to the working network.
Possible failure causes	· Invalid JSON format. · Internal server error. · Please perform the operation on the active leader. · Configuration recovery is in progress. · The VLAN ID is invalid or out of range. · The working network has been configured with a default access VLAN. · You have no privilege to perform this operation.

Delete default access VLAN

Keyword	DELETE_BSM_WORKING_VLAN_OP
Message text	Deleted the default access VLAN from the working network.
Variable fields	N/A
Example	Deleted the default access VLAN from the working network.
Explanation	The default access VLAN was deleted from the working network.
Possible failure causes	· Invalid JSON format. · Internal server error. · Please perform the operation on the active leader. · Configuration recovery is in progress. · The default access VLAN does not exist. · The default access VLAN is being used. · You have no privilege to perform this operation.

Create mapping table of service network

Keyword	CREATE_BSM_VLAN_DOMAIN_OP
Message text	Created a VLAN-VXLAN mapping table for the service network: $1.
Variable fields	$1: VLAN-VXLAN mapping table configuration information.
Example	Created a VLAN-VXLAN mapping table for the service network: Domain_name: [domain1] ID: [5473e36e-5b34-4e9d-9d20-206310d1d478] Mappings: [ Start_VLAN: [50], end_VLAN: [60], start_VXLAN: [310], end_VXLAN: [310], access_mode: [ETHERNET] ].
Explanation	A VLAN-VXLAN mapping table was created for the service network.
Possible failure causes	· Invalid JSON format. · Internal server error. · Please perform the operation on the active leader. · Configuration recovery is in progress. · Invalid mapping table name. · The VLAN ID is invalid or out of range. · The VXLAN ID is invalid or out of range. · Overlapping mappings exist. · The mapping table already exists. · You have no privilege to perform this operation.

Update mapping table of service network

Keyword	UPDATE_BSM_VLAN_DOMAIN_OP
Message text	Updated a VLAN-VXLAN mapping table of the service network: $1.
Variable fields	$1: VLAN-VXLAN mapping table configuration information.
Example	Updated a VLAN-VXLAN mapping table of the service network: Domain_name: [domain2] ID: [5473e36e-5b34-4e9d-9d20-206310d1d478] Mappings: [ Start_VLAN: [50], end_VLAN: [60], start_VXLAN: [320], end_VXLAN: [320], access_mode: [ETHERNET] ].
Explanation	A VLAN-VXLAN mapping table of the service network was modified.
Possible failure causes	· Invalid JSON format. · Internal server error. · Please perform the operation on the active leader. · Configuration recovery is in progress. · The mapping table does not exist. · Invalid mapping table name. · The VLAN ID is invalid or out of range. · The VXLAN ID is invalid or out of range. · Overlapping mappings exist. · The reserved VLAN ID conflicts with a VLAN ID of a VLAN-VXLAN mapping. · You have no privilege to perform this operation.

Delete mapping table of service network

Keyword	DELETE_BSM_VLAN_DOMAIN_OP
Message text	Deleted a VLAN-VXLAN mapping table from the service network: $1.
Variable fields	$1: ID of the VLAN-VXLAN mapping table.
Example	Deleted a VLAN-VXLAN mapping table from the service network: 5473e36e-5b34-4e9d-9d20-206310d1d478.
Explanation	A VLAN-VXLAN mapping table was deleted from the service network.
Possible failure causes	· Invalid JSON format. · Internal server error. · Please perform the operation on the active leader. · Configuration recovery is in progress. · The mapping table does not exist. · The mapping table has been bound to devices. · The mapping table has been bound to interfaces. · You have no privilege to perform this operation.

Bound mapping table to device

Keyword	CREATE_BSM_VLAN_DOMAIN_BIND_OP
Message text	Bound devices to a VLAN-VXLAN mapping table: $1.
Variable fields	$1: VLAN-VXLAN mapping table binding information.
Example	Bound devices to a VLAN-VXLAN mapping table: Domain_ID: [29577831-31d1-46e7-a33a-40f6ae6f4179] Name: [aaa] Device_list: [ Device_ID: [ffd1efeb-5582-40af-b378-910d8e68bd6d], device_name: [TOR2] Device_ID: [bc96fa18-0888-474e-979d-9cf18f0433dd], device_name: [TOR1] ].
Explanation	Bound devices to a VLAN-VXLAN mapping table.
Possible failure causes	· Invalid JSON format. · Internal server error. · Please perform the operation on the active leader. · Configuration recovery is in progress. · Devices already bound to the mapping table exist. · Nonexistent devices are specified. · Duplicate devices exist. · Devices bound to other mapping tables exist. · The mapping table does not exist. · The port on the specified device has been bound to a QinQ-VXLAN mapping table. · The reserved VLAN ID conflicts with a VLAN ID of a VLAN-VXLAN mapping. · You have no privilege to perform this operation.

Updated binding relationship between mapping table and device

Keyword	UPDATE_BSM_VLAN_DOMAIN_BIND_OP
Message text	Updated binding relationships between a VLAN-VXLAN mapping table and devices: $1.
Variable fields	$1: VLAN-VXLAN mapping table binding information.
Example	Updated binding relationships between a VLAN-VXLAN mapping table and devices: Domain_ID: [29577831-31d1-46e7-a33a-40f6ae6f4179] Name: [aaa] Device_list: [ Device_ID: [ffd1efeb-5582-40af-b378-910d8e68bd6d], device_name: [TOR2] Device_ID: [bc96fa18-0888-474e-979d-9cf18f0433dd], device_name: [TOR1] ].
Explanation	Updated binding relationships between a VLAN-VXLAN mapping table and devices.
Possible failure causes	· Invalid JSON format. · Internal server error. · Please perform the operation on the active leader. · Configuration recovery is in progress. · Devices not bound to the mapping table exist. · Nonexistent devices are specified. · Duplicate devices exist. · Devices bound to other mapping tables exist. · The mapping table does not exist. · The port on the specified device has been bound to a QinQ-VXLAN mapping table. · The reserved VLAN ID conflicts with a VLAN ID of a VLAN-VXLAN mapping. · You have no privilege to perform this operation.

Delete bindings between mapping table and all devices

Keyword	DELETE_BSM_VLAN_DOMAIN_BIND_OP
Message text	Deleted binding relationships between a VLAN-VXLAN mapping table and all devices: $1.
Variable fields	$1: ID of the VLAN-VXLAN mapping table.
Example	Deleted binding relationships between a VLAN-VXLAN mapping table and all devices: 29577831-31d1-46e7-a33a-40f6ae6f4179.
Explanation	Deleted binding relationships between a VLAN-VXLAN mapping table and all devices.
Possible failure causes	· Invalid JSON format. · Internal server error. · Please perform the operation on the active leader. · Configuration recovery is in progress. · Devices already unbound from the mapping table exist. · The mapping table does not exist. · You have no privilege to perform this operation.

Bound port to mapping table

Keyword	CREATE_BSM_PORT_VLAN_DOMAIN_BIND_OP
Message text	Bound interfaces to a VLAN-VXLAN mapping table: $1.
Variable fields	$1: VLAN-VXLAN mapping table binding information.
Example	Bound interfaces to a VLAN-VXLAN mapping table: Domain_ID: [29577831-31d1-46e7-a33a-40f6ae6f4179] Name: [aaa] Bind_port_list: [ Device_ID: [bc96fa18-0888-474e-979d-9cf18f0433dd], device_name: [TOR1], port_name: [GigabitEthernet1/0/1], PVID: [30], port_status: [ACTIVE] ].
Explanation	Bound interfaces to a VLAN-VXLAN mapping table.
Possible failure causes	· Invalid JSON format. · Internal server error. · Please perform the operation on the active leader. · Configuration recovery is in progress. · Invalid interface list. · Invalid interface names exist. · Nonexistent devices are specified. · Invalid device MAC addresses exist. · Invalid device names exist. · The VLAN ID is invalid or out of range. · Interfaces already bound to the mapping table exist. · Duplicate interfaces exist. · Non-VTEP interfaces exist. · Interfaces bound to the inspection network exist. · Interfaces bound to other mapping tables exist. · The mapping table does not exist. · The reserved VLAN ID conflicts with a VLAN ID of a VLAN-VXLAN mapping. · You have no privilege to perform this operation. · The specified interface already exists in an interface and PVID mapping.

Update binding relationship between port and mapping table

Keyword	UPDATE_BSM_PORT_VLAN_DOMAIN_BIND_OP
Message text	Updated binding relationships between interfaces and a VLAN-VXLAN mapping table: $1.
Variable fields	$1: VLAN-VXLAN mapping table binding information.
Example	Updated binding relationships between interfaces and a VLAN-VXLAN mapping table: Domain_ID: [29577831-31d1-46e7-a33a-40f6ae6f4179] Name: [aaa] Bind_port_list: [ Device_ID: [bc96fa18-0888-474e-979d-9cf18f0433dd], device_name: [TOR1], port_name: [GigabitEthernet1/0/1], PVID: [30], port_status: [ACTIVE] ].
Explanation	Updated binding relationships between interfaces and a VLAN-VXLAN mapping table.
Possible failure causes	· Invalid JSON format. · Internal server error. · Please perform the operation on the active leader. · Configuration recovery is in progress. · Invalid interface list. · Invalid interface names exist. · Nonexistent devices are specified. · Invalid device MAC addresses exist. · Invalid device names exist. · The VLAN ID is invalid or out of range. · Interfaces not bound to the mapping table exist. · Duplicate interfaces exist. · Non-VTEP interfaces exist. · Interfaces bound to the inspection network exist. · Interfaces bound to other mapping tables exist. · The mapping table does not exist. · The reserved VLAN ID conflicts with a VLAN ID of a VLAN-VXLAN mapping. · You have no privilege to perform this operation. · The specified interface already exists in an interface and PVID mapping.

Deleted bindings between mapping table and all ports

Keyword	DELETE_BSM_PORT_VLAN_DOMAIN_BIND_OP
Message text	Deleted binding relationships between a VLAN-VXLAN mapping table and all interfaces: $1.
Variable fields	$1: ID of the VLAN-VXLAN mapping table.
Example	Deleted binding relationships between a VLAN-VXLAN mapping table and all interfaces: 29577831-31d1-46e7-a33a-40f6ae6f4179.
Explanation	Deleted binding relationships between a VLAN-VXLAN mapping table and all interfaces.
Possible failure causes	· Invalid JSON format. · Internal server error. · Please perform the operation on the active leader. · Configuration recovery is in progress. · Interfaces already unbound from the mapping table exist. · The mapping table does not exist. · You have no privilege to perform this operation.

CAPACITY

This section contains capacity simulation messages.

Execute capacity simulation task

Keyword	EXECUTE_CAPACITY_SIMULATION_TASK_OP
Message text	Executed capacity simulation task: $1.
Variable fields	$1: Capacity simulation task UUID.
Example	Execute capacity simulation task: aae71a62-889b-47e7-9f1a-e73c32c61004.
Explanation	A capacity simulation task was executed.
Possible failure causes	· Invalid JSON format. · Invalid XML format. · Invalid parameter. · The request body cannot be empty. · The (parameter) parameter cannot be empty. · Internal error. · The service does not exist. · Thread is interrupted. · The (parameter) parameter value does not match the regular expression. · The value for the type parameter can only be AC, VSI, VSI-Interface, VRF, Route. · The NETCONF configuration file does not exist. · The NETCONF configuration file is empty or has no valid resources. · The NETCONF configuration file content does not match the regular expression. · Failed to obtain command configuration from the device. · Failed to connect to the database. · The specified {resourceType} with {indexType} values {indexValue} does not exist. · Failed to query tenant design. · Another user is processing this resource. Please try again later. · Executor reject to execute task. · The simulated device is not found in the real network. · Cannot find the specified device. · The system service does not respond. · Failed to obtain capacity information from the device. · Failed to convert object to json string. · The capacity simulation task does not exist.

Get simulation config change task

Keyword	GET_SIMULATION_CONFIG_ALTER_OP
Message text	Get simulation configuration changes.
Variable fields	N/A
Example	Get simulation configuration changes.
Explanation	Simulation configuration changes were obtained.
Possible failure causes	· Invalid parameter. · Invalid XML format. · Cannot find the specified device. · Another user is processing this resource. Please try again later. · Get redis lock exception. · The NETCONF configuration file does not exist. · The NETCONF configuration file content does not match the regular expression. · Internal error. · Failed to obtain command configuration from the device. · The specified {resourceType} with {indexType} values {indexValue} does not exist. · The system service does not respond.

Interrupt capacity simulation task

Keyword	INTERRUPT_CAPACITY_SIMULATION_TASK_OP
Message text	Interrupt capacity simulation task: $1.
Variable fields	$1: Capacity simulation task UUID.
Example	Interrupt capacity simulation task: aae71a62-889b-47e7-9f1a-e73c32c61004.
Explanation	A capacity simulation task was interrupted.
Possible failure causes	· Invalid parameter. · The capacity simulation task does not exist.

CLOSE_LOOP

This section contains messages generated by the issues module.

Register SeerAnalyzer info

Keyword	REGISTER_SEERANALYSIS_OP
Message text	Registered SeerAnalyzer info:$1.
Variable fields	$1: Configuration information of SeerAnalyzer.
Example	Register SeerAnalyzer info: { ID: f3b3a9e6-b3ef-4da6-95c7-ebee6042568e Name: outer-sa URL: https://192.158.25.20:10443 Username: admin Password: ****** }.
Explanation	The controller connected to the SeerAnalyzer component.
Possible failure causes	· Please specify all required parameters. · Please specify an analyzer name. · Invalid analyzer name length. · Please specify a URL for the analyzer. · Invalid URL length. · Invalid URL format. · Please specify a username. · Invalid username length. · Invalid username format. · Please specify a password. · Password encryption failed. · Password decryption failed. · Invalid password length. · Invalid password format. · The analyzer is not available. · Another user is processing, Please try later. · The system service does not respond. · Failed to connect to the analyzer. · The analyzer name or address already exists.

Update SeerAnalyzer info

Keyword	UPDATE_SEERANALYSIS_OP
Message text	Updated SeerAnalyzer info: $1
Variable fields	$1: Configuration information of SeerAnalyzer.
Example	Updated SeerAnalyzer info: { ID: f3b3a9e6-b3ef-4da6-95c7-ebee6042568e Name: outer-sa URL: https://192.158.25.20:10443 Username: admin Password: ****** }.
Explanation	The configuration information of SeerAnalyzer was edited.
Possible failure causes	· The specified resource does not exist. · Please specify all required parameters. · Please specify a UUID. · Invalid UUID. · Please specify an oldpassword. · Incorrect old password. · Please specify an analyzer name. · Invalid analyzer name length. · Please specify a URL for the analyzer. · Invalid URL length. · Invalid URL format. · Please specify a username. · Invalid username length. · Invalid username format. · Please specify a password. · Invalid password length. · Invalid password format. · Password encryption failed. · Password decryption failed. · Oldpassword decryption failed. · The analyzer is not available. · Another user is processing, Please try later. · The system service does not respond. · Failed to connect to the analyzer. · The analyzer name or address already exists.

Delete SeerAnalyzer info

Keyword	DELETE_SEERANALYSIS_OP
Message text	Deleted SeerAnalyzer info: $1
Variable fields	$1: SeerAnalyzer UUID.
Example	Deleted SeerAnalyzer info: f3b3a9e6-b3ef-4da6-95c7-ebee6042568e.
Explanation	A SeerAnalyzer was deleted.
Possible failure causes	· Invalid UUID. · The specified resource does not exist.

Close event

Keyword	CLOSE_FAULT_OP
Message text	Closed event: $1
Variable fields	$1: UUID of the fault event.
Example	Closed event: f3b3a9e6-b3ef-4da6-95c7-ebee6042568e
Explanation	A fault event was closed.
Possible failure causes	· The specified resource does not exist. · Please specify a UUID for the event. · Invalid UUID for the event. · The analyzer is not available. · Another user is processing, Please try later. · The specified event has been closed. · Please undeploy the solution before closing the event. · The comment on the close action cannot exceed 120 characters. · The system service does not respond. · You have no privilege to perform the operation. · Failed to find the analyzer by saIp. The analyzer might not be registered with the controller. · Cannot find the analyzer that reported the issue. The controller has multiple registered analyzers, but the issue does not contain analyzer address information. · The analyzer is not registered with the controller.

Deploy solution

Keyword	IMPLEMENT_PROPOSAL_OP
Message text	Deployed solution:$1.
Variable fields	$1: Solution information.
Example	Deployed solution: { "faultId": "bb8bb083-c4a4-45eb-b5dc-2b251a7921f3", "planId": "118bb083-c4a4-45eb-b5dc-2b251a7921f3",, "detailId": "333bb083-c4a4-45eb-b5dc-2b251a7921f3" }.
Explanation	A solution was deployed.
Possible failure causes	· Invalid JSON format. · The specified resource does not exist. · Please specify a UUID for the event. · Please specify a planId. · Invalid value for the planId field. · Please specify a detailId. · Invalid value for the detailId field. · Another user is processing, Please try later. · The deploy action is available only for active events. · The fault event type isn't isolation or recovery cannot be issued. · Other plans for specified event have been issued. · The solution with the specified UUID does not exist. · The solution detail with the specified UUID does not exist. · The analyzer is not available. · Failed to isolate the port. · Failed to add the device configuration fragment. · Failed to obtain the switch interface information. · Failed to deploy the device configuration fragment. · The system service does not respond. · The specified solution detail has been deployed. · The device is a traditional device and does not support solution deployment. · Failed to synchronize solution to the analyzer. · You have no privilege to perform the operation. · Failed to obtain failure event information from SeerAnalyzer. · Cannot find the failure event on SeerAnalyzer. The controller will close the failure event automatically. · The failure event is already closed on SeerAnalyzer. The controller will close the failure event automatically. · Failed to deploy the device configuration netconf. · Failed to find the analyzer by saIp. The analyzer might not be registered with the controller. · Cannot find the analyzer that reported the issue. The controller has multiple registered analyzers, but the issue does not contain analyzer address information. · The analyzer is not registered with the controller.

Undeploy solution

Keyword	FALLBACK_PROPOSAL_OP
Message text	Undeployed solution: $1
Variable fields	$1: Solution information.
Example	Undeployed solution: { "faultId": "bb8bb083-c4a4-45eb-b5dc-2b251a7921f3", "planId": "118bb083-c4a4-45eb-b5dc-2b251a7921f3",, "detailId": "333bb083-c4a4-45eb-b5dc-2b251a7921f3" }.
Explanation	A deployed solution was undeployed.
Possible failure causes	· Invalid JSON format. · The specified resource does not exist. · Please specify a UUID for the event. · Please specify a planId. · Invalid value for the planId field. · Please specify a detailId. · Invalid value for the detailId field. · The solution with the specified UUID does not exist. · The solution detail with the specified UUID does not exist. · Another user is processing, Please try later. · The specified event has been closed. · The undeploy action is supported only for events that have solutions deployed. · The analyzer is not available. · The solution has not been deployed. · The system service does not respond. · Failed to isolate the port. · Failed to add the device configuration fragment. · Failed to obtain the switch interface information. · Failed to deploy the device configuration fragment. · The device is a traditional device and does not support solution deployment. · Failed to synchronize solution to the analyzer. · You have no privilege to perform the operation. · Failed to deploy the device configuration netconf. · Failed to obtain failure event information from SeerAnalyzer. · Cannot find the failure event on SeerAnalyzer. The controller will close the failure event automatically. · The failure event is already closed on SeerAnalyzer. The controller will close the failure event automatically. · Failed to find the analyzer by saIp. The analyzer might not be registered with the controller. · Cannot find the analyzer that reported the issue. The controller has multiple registered analyzers, but the issue does not contain analyzer address information. · The analyzer is not registered with the controller

CON_CERTM

This section contains certificate management messages.

Import a certificate

Keyword	IMPORT_CERTIFICATE_OP
Message text	Import a certificate: ID=$1, name=$2, type=$3, service =$4. $5
Variable fields	$1: Certificate ID. $2: Certificate name. $3: Certificate type. $4: Service name. $5: Subject information.
Example	Import a certificate: ID=98b770b1-ed38-462e-8191-d45ee3e8a273, name=keystore.jks, type=keystore, service=OpenFlow. With subject "CN=*.h3c.com, OU=SDN, O=H3C, ST=ZJ, C=CN".
Explanation	A certificate was imported for the specified service.
Possible failure causes	· The user role doesn't provide the permission to perform the operation. · The system is not responding. · Invalid service. · This function is not supported. · The certificate type is not specified. · Invalid certificate. · Invalid certificate name. · The certificate file size cannot exceed 50 KB. · Invalid certificate type. · The certificate is not valid yet. · The certificate has expired. · The specified service does not exist. · A certificate already exists with the specified name. · The fingerprint has been used in another certificate. · The certificate file in CER format cannot be of the private key type.

Delete a certificate

Keyword	DELETE_CERTIFICATE_OP
Message text	Delete a certificate: ID=$1, name=$2, type=$3, service=$4.
Variable fields	$1: Certificate ID. $2: Certificate name. $3: Certificate type. $4: Service name.
Example	Delete a certificate: ID=ed42ec14-d74c-4940-a0c1-ae7aba8694dc, name=keystore.jks, type=keystore, service=OpenFlow.
Explanation	A certificate was deleted.
Possible failure causes	· The user role doesn't provide the permission to perform the operation. · The system is not responding. · The resource doesn't exist. · The certificate is in use.

Export a certificate

Keyword	EXPORT_CERTIFICATE_OP
Message text	Export a certificate: ID=$1, name=$2, type=$3, service =$4.
Variable fields	$1: Certificate ID. $2: Certificate name. $3: Certificate type. $4: Service name.
Example	Export a certificate: ID=8032909d-47a1-4715-90af-5153ffe39899, name =ca.pem, type=keystore, service=OpenFlow.
Explanation	A certificate was exported.
Possible failure causes	· The system is not responding. · The resource doesn't exist.

Activate a certificate for a service

Keyword	ACTIVE_CERTIFICATE_OP
Message text	Activate a certificate: ID=$1, name=$2, type=$3, service=$4.
Variable fields	$1: Certificate ID. $2: Certificate name. $3: Certificate type. $4: Service to which the certificate belongs.
Example	Activate a certificate: ID=3156d95b-3292-4d0e-a314-284a820118be, name=truststore.jks, type=truststore, service=OpenFlow.
Explanation	A certificate was activated for a specific service.
Possible failure causes	· The user role doesn't provide the permission to perform the operation. · The system is not responding. · This function is not supported. · The specified service does not exist.

Deactivate certificates for a service

Keyword	INACTIVE_CERTIFICATE_OP
Message text	Deactivate a certificate: ID=$1, name=$2, type=$3, service=$4.
Variable fields	$1: Certificate ID. $2: Certificate name. $3: Service to which the certificate belongs.
Example	Deactivate a certificate: ID=b29d3356-95b8-451b-bd86-1d35916dfe5f, name=github.cer, type=truststore, service=OpenFlow.
Explanation	A certificate was deactivated for a specific service.
Possible failure causes	· The user role doesn't provide the permission to perform the operation. · The system is not responding. · This function is not supported. · The specified service does not exist.

Update alarm config

Keyword	UPDATE_ALARM_CONFIG_OP
Message text	Update the alarm configuration: $1
Variable fields	$1: Alarm settings.
Example	Update the alarm configuration: { "period": 1, "threshold": 90 }
Explanation	Alarm settings were edited.
Possible failure causes	· Invalid certificate check interval. · Invalid certificate expiration reminder value. · The user role doesn't provide the permission to perform the operation. · The system is not responding. · Invalid JSON format.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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	You have no privilege to perform this operation.

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	You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

Delete group table entry

Keyword	DELETE_GROUPTABLE_OP
Message text	A group table entry was deleted on device $1: $2
Variable fields	$1: Device IP address. $2: Group table ID.
Example	A group table entry was deleted on device 192.168.133.68: {“group_id: 3”}
Explanation	A group table entry was deleted.
Possible failure causes	You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

Modify interface status by interface index

Keyword	MODIFY_INTERFACE_STATUS_BY_INDEX_OP
Message text	Modified interface status by index: $1
Variable fields	$1: Interface information.
Example	Modified interface status by index: IP: [1.1.1.1] Interface Index: [1, 2, 3] Shutdown: [true]
Explanation	An interface was found by its index and was brought up or shut down.
Possible failure causes	· Configuration recovery is in progress. · The is_shut_down parameter is required. · Invalid IP address. · Internal server error. · Invalid JSON format. · The is_shut_down parameter value must be true or false, which is case insensitive. · The controller is not the active leader. · The port ID is required. · Invalid port ID. · Unsupported device type. · The specified device doesn't exist. · You have no privilege to perform this operation. · The specified port doesn't exist.

Single device change to fail-safe mode

关键字	CHANGE_SINGLE_DEVICE_FAILSAFE_OP
日志内容	OpenFlow device with data path ID $1 and IP $2 switched to fail-safe mode.
参数解释	$1: Datapath ID $2: 设备的IP地址
举例	OpenFlow device with data path ID 00:03:00:0c:29:43:67:ce and IP 98.0.50.19 switched to fail-safe mode.
日志说明	用户对指定OpenFlow设备进行了逃生的操作
失败原因	· Abnormal connections between the active leader and other controllers in the team. · Please specify the device data path ID. · Invalid device data path ID. · Invalid JSON format. · The request is invalid. · The value of the is_connect field can only be true or false. · Failed to synchronize data on controllers {IP} to the database. · Cannot perform operations on devices when the fail-safe mode is enabled. · The controller is not the active leader. · Invalid device ID. · Invalid IP address. · Internal server error.

Single device change to normal mode

关键字	CHANGE_SINGLE_DEVICE_NORMAL_OP
日志内容	OpenFlow device with data path ID $1 and IP $2 switched to normal mode.
参数解释	$1: Datapath ID $2: 设备的IP地址
举例	OpenFlow device with data path ID 00:03:00:0c:29:43:67:ce and IP 98.0.50.19 switched to normal mode.
日志说明	用户对指定OpenFlow设备进行了恢复的操作
失败原因	· Abnormal connections between the active leader and other controllers in the team. · Please specify the device data path ID. · Invalid device data path ID. · Invalid JSON format. · The request is invalid. · The value of the is_connect field can only be true or false. · Failed to synchronize data on controllers {IP} to the database. · Cannot perform operations on devices when the fail-safe mode is enabled. · The controller is not the active leader. · Invalid device ID. · Invalid IP address. · Internal server error.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

CON_ROUTERCONFIGS

This section contains CON_ROUTERCONFIGS messages.

Add BGP instance

Keyword	ADD_BGP_INSTANCE_OP
Message text	Added BGP instance: $1.
Variable fields	$1: BGP instance information.
Example	Added BGP instance: { "router_id":"1.1.1.1", "as":"1", "keepalive":60, "hold_time":180, "controller":"192.168.109.202" }.
Explanation	A BGP instance was added to the controller.
Possible failure causes	· Please specify a controller IP address. · Invalid IP address. · Please specify a router ID. · Invalid router ID. · Please specify an AS number. · Invalid AS number. · Invalid keepalive interval. · Invalid hold time. · The hold time must be at least three times the keepalive interval. · Failed to issue configuration to Quagga. · The BGP instance already exists. · Internal system error. · Operation failed because the user role doesn't have the permission.

Delete BGP instance

Keyword	DEL_BGP_INSTANCE_OP
Message text	Deleted BGP instance from $1
Variable fields	$1: IP address of the target controller.
Example	Deleted BGP instance from 192.168.109.202.
Explanation	A BGP instance was deleted from the specified controller.
Possible failure causes	· Invalid IP address. · The BGP instance does not exist. · Failed to issue configuration to Quagga. · Internal system error. · Operation failed because the user role doesn't have the permission.

Add BGP network route

Keyword	ADD_BGP_NETWORK_OP
Message text	Added BGP network route: $1.
Variable fields	$1: BGP network route information.
Example	Added BGP network route: { "controller":"192.168.109.202", "network":"3.3.3.3/24" }.
Explanation	A local network route was injected to the BGP routing table.
Possible failure causes	· Please specify a controller IP address. · Invalid IP address. · Please specify a network address. · Invalid network address. · Invalid network mask. · The specified network already exists. · The BGP instance does not exist. · Failed to issue configuration to Quagga. · Internal system error. · Operation failed because the user role doesn't have the permission.

Delete BGP network route

Keyword	DELETE_BGP_NETWORK_OP
Message text	Deleted BGP network route: $1.
Variable fields	$1: BGP network route information.
Example	Deleted BGP network route: { "controller":"192.168.109.202", "network":"3.3.3.0/24" }.
Explanation	The specified local network route was removed from the BGP routing table on a controller.
Possible failure causes	· Please specify a controller IP address. · Invalid IP address. · Please specify a network address. · Invalid network address. · Invalid network mask. · The specified network does not exist. · The BGP instance does not exist. · Failed to issue configuration to Quagga. · Internal system error. · Operation failed because the user role doesn't have the permission.

Add BGP neighbor

Keyword	ADD_BGP_NEIGHBOR_OP
Message text	Added BGP neighbor: $1.
Variable fields	$1: BGP neighbor information.
Example	Added BGP neighbor: { "controller":"192.168.109.202", "ip":"12.0.0.0", "remote_as":3, "filter":"in" }.
Explanation	A BGP neighbor was added.
Possible failure causes	· Please specify a controller IP address. · Invalid IP address. · Please specify a neighbor IP address. · Invalid neighbor IP address. · Please specify the remote AS number for the neighbor. · Invalid remote AS number for the neighbor. · Please specify the filtering policy setting for the neighbor. · Invalid filtering policy setting for the neighbor. · The BGP neighbor already exists. · The BGP instance does not exist. · Failed to issue configuration to Quagga. · Internal system error. · Operation failed because the user role doesn't have the permission.

Delete BGP neighbor

Keyword	DELETE_BGP_NEIGHBOR_OP
Message text	Deleted BGP neighbor: $1.
Variable fields	$1: BGP neighbor information.
Example	Deleted BGP neighbor: { "controller":"192.168.109.202", "ip":"12.0.0.0" }.
Explanation	The specified BGP neighbor was deleted from a controller.
Possible failure causes	· Please specify a controller IP address. · Invalid IP address. · Please specify a neighbor IP address. · The BGP neighbor does not exist. · The BGP instance does not exist. · Failed to issue configuration to Quagga. · Internal system error. · Operation failed because the user role doesn't have the permission.

Update BGP session settings

Keyword	UPDATE_BGP_SESSION_OP
Message text	Updated BGP session settings: $1.
Variable fields	$1: BGP session settings.
Example	Updated BGP session settings: { "keepalive":"32", "hold_time":"50000", "controller":"192.168.109.202" }.
Explanation	The BGP session settings were updated on the controller.
Possible failure causes	· Please specify a controller IP address. · Invalid IP address. · Invalid keepalive interval. · Invalid hold time. · The hold time must be at least three times the keepalive interval. · The BGP instance does not exist. · Failed to issue configuration to Quagga. · Internal system error. · Operation failed because the user role doesn't have the permission.

Add OSPF instance

Keyword	ADD_OSPF_INSTANCE_OP
Message text	Added OSPF instance: $1.
Variable fields	$1: OSPF instance information.
Example	Added OSPF instance: { "router_id": "192.168.109.89", "auth": "MD5", "keyId": "2", "passwd": "MjM0NTY3OA==", "controller": "109.168.10.2" }.
Explanation	An OSPF instance was added to the controller.
Possible failure causes	· Please specify a controller IP address. · Invalid IP address. · Please specify a router ID. · Invalid router ID. · You must select an authentication mode for the OSPF instance. · Invalid authentication mode. · You must enter a password when the authentication mode is MD5. · You must enter a key ID when the authentication mode is MD5. · The key ID must be an integer in the range of 1 to 255. · The OSPF instance already exists. · Failed to issue configuration to Quagga. · Internal system error. · Operation failed because the user role doesn't have the permission.

Delete OSPF instance

Keyword	DEL_OSPF_INSTANCE_OP
Message text	Deleted OSPF instance from $1.
Variable fields	$1: IP address of the controller.
Example	Deleted OSPF instance from 192.168.109.202.
Explanation	An OSPF instance was deleted from the specified controller.
Possible failure causes	· Invalid IP address. · The OSPF instance does not exist. · Failed to issue configuration to Quagga. · Internal system error. · Operation failed because the user role doesn't have the permission.

Add OSPF network route

Keyword	ADD_OSPF_NETWORK_OP
Message text	Added OSPF network route: $1.
Variable fields	$1: OSPF network route information.
Example	Added OSPF network route: { "area":"76756", "ifname":"", "network":"2.0.0.0/8", "controller":"192.168.109.201" }.
Explanation	An OSPF network route was added to the controller.
Possible failure causes	· Please specify a controller IP address. · Invalid IP address. · Please specify an area ID. · Invalid area ID. · Please specify a network address. · Invalid network address. · Invalid network mask. · Please specify an interface. · Invalid interface. · The OSPF instance does not exist. · The specified network already exists. · Failed to issue configuration to Quagga. · Internal system error. · Operation failed because the user role doesn't have the permission.

Delete OSPF network route

Keyword	DEL_OSPF_NETWORK_OP
Message text	Deleted OSPF network route: $1.
Variable fields	$1: OSPF network route information.
Example	Deleted OSPF network route: { "network":"2.0.0.0/8", "controller":"192.168.109.201" }.
Explanation	An OSPF network route was deleted from the controller.
Possible failure causes	· Please specify a controller IP address. · Invalid IP address. · Please specify a network address. · Invalid network address. · Invalid network mask. · Please specify an interface. · Invalid interface. · The OSPF instance does not exist. · The specified network does not exist. · Failed to issue configuration to Quagga. · Internal system error. · Operation failed because the user role doesn't have the permission.

Add OSPF area

Keyword	ADD_OSPF_AREA_OP
Message text	Added OSPF area: $1.
Variable fields	$1: OSPF area information.
Example	Added OSPF area: { "area": "1.1.1.1", "enableAuth": true, "nssa": "translate-candidate", "controller": "192.168.0.1" }.
Explanation	An OSPF area was added to the controller.
Possible failure causes	· Please specify a controller IP address. · Invalid IP address. · Please specify an area ID. · Invalid area ID. · Please specify the NSSA setting for the area. · Invalid NSSA setting for the area. · The OSPF instance does not exist. · The area already exists. · You must select an option other than None for NSSA when the authentication mode is none. · Failed to issue configuration to Quagga. · Internal system error. · Operation failed because the user role doesn't have the permission.

Delete OSPF area

Keyword	DEL_OSPF_AREA_OP
Message text	Deleted OSPF area: $1.
Variable fields	$1: OSPF area information.
Example	Deleted OSPF area: { "area":"3.47.53.27", "controller":"192.168.109.201" }.
Explanation	The specified OSPF area was deleted from the controller.
Possible failure causes	· Please specify a controller IP address. · Invalid IP address. · Please specify an area ID. · Invalid area ID. · The area does not exist. · Failed to issue configuration to Quagga. · Internal system error. · Operation failed because the user role doesn't have the permission.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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	You have no privilege to perform this operation.

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	You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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	You have no privilege to perform this operation.

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	You have no privilege to perform this operation.

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	You have no privilege to perform this operation.

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	You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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	You have no privilege to perform this operation.

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	You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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	You have no privilege to perform this operation.

Create server link

Keyword	CREATE_SERVER_LINK_OP
Message text	Created server link: $1
Variable fields	$1: Server link information.
Example	Created server link: device_name: [1] system_name: [2] mac: [52:5c:60:1d:08:00] phy_port: [3] port_name: [GE2/0/3]
Explanation	A server link was added.
Possible failure causes	· You have no privilege to perform this operation. · The specified server link already exists. · Internal error.

Delete server link

Keyword	DEL_SERVER_LINK_OP
Message text	Deleted server link: $1
Variable fields	$1: Server link information.
Example	Deleted server link: device_name: [1] system_name: [2] mac: [52:5c:60:1d:08:00] phy_port: [3]
Explanation	A server link was deleted.
Possible failure causes	· You have no privilege to perform this operation. · The specified server link does not exist. · Internal error.

Import server link

Keyword	IMPORT_SERVER_LINK_OP
Message text	Imported server links from “$1”. Imported links: “$2”.
Variable fields	$1: Template name. $2: Number of server links that have been successfully imported.
Example	Imported server links from "Batch import server link example.xlsx". Imported links: "210".
Explanation	Server links were imported.
Possible failure causes	· You have no privilege to perform this operation. · The specified server link does not exist. · Internal error.

CON_USER

This section contains CON_USER messages.

Add a user

Keyword	ADD_USER_OP
Message text	Added a user:$1.
Variable fields	$1: User name.
Example	Added a user:11.
Explanation	A user was added.
Possible failure causes	· Invalid username. · The username already exists. · The password length is out of range or the password contains only letters, digits, or special characters. · Invalid role. · The controller is not the active leader. · Incorrect format. · Failed to add the user. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

DATACHECK

This section contains data check messages.

Start data check

Keyword	START_DATA_CHECK_OP
Message text	Started data check for module [$1].
Variable fields	$1: Module name.
Example	Started data check for module [VSM].
Explanation	Data check was started for a specific module.
Possible failure causes	· The controller has not finished initialization. · Administrator privileges required. · The JSON string cannot be empty. · Please specify the module. · Invalid module. · Please specify the data check UUID. · Invalid data check UUID. · Cannot start the data check because the previous data check is not finished. · Unknown error.

Stop data check

Keyword	STOP_DATA_CHECK_OP
Message text	Stopped data check.
Variable fields	N/A
Example	Stopped data check.
Explanation	Data check was stopped.
Possible failure causes	N/A

DNEC

This section contains DNEC module messages.

Create custom site

Keyword	CREATE_UC_SITE_CUSTOM
Message text	Created custom U-Center site.
Variable fields	N/A
Example	Created custom U-Center site.
Explanation	A custom site was created.
Possible failure causes	· The request message body is empty. · The site name is required. · Please specify a site name. · Invalid site name. · A site already exists with the specified name. · The specified area already has a local data center. · Please select the province where the site is located. · A district already exists with a site. · Please select the local_data parameter and set its value to true or false. · The total number of devices supported must be an integer in the range of 0 to 99999. · Please select the city where the site is located. · The district does not exist. · Please select the district where the site is located. · The system service does not respond.

Update custom site

Keyword	UPDATE_UC_SITE_CUSTOM
Message text	Updated custom U-Center site.
Variable fields	N/A
Example	Updated custom U-Center site.
Explanation	A custom site was edited.
Possible failure causes	· The UUID is invalid. · The request message body is empty. · A site already exists with the specified name. · The specified area already has a local data center. · Please select the province where the site is located. · A district already exists with a site. · Please select the local_data parameter and set its value to true or false. · The total number of devices supported must be an integer in the range of 0 to 99999. · Please select the city where the site is located. · The district does not exist. · Please select the district where the site is located. · The system service does not respond.

Delete custom site

Keyword	DELETE_UC_SITE_CUSTOM
Message text	Deleted custom U-Center site.
Variable fields	N/A
Example	Deleted custom U-Center site.
Explanation	A custom site was deleted.
Possible failure causes	· The UUID is invalid. · The specified site does not exist. · The system service does not respond.

Create custom outgoing external flow

Keyword	CREATE_UC_OUT_NETWORK_TRAFFIC_CUSTOM
Message text	Created custom U-Center outgoing external flow.
Variable fields	N/A
Example	Created custom U-Center outing external flow.
Explanation	A custom outgoing external flow was created.
Possible failure causes	· Invalid JSON format. · The external network traffic has been bound. · The fabric ID is required. · Please specify a fabric ID. · Invalid fabric ID. · The fabric name is required. · Please specify a fabric name. · Invalid fabric name. · The group ID is required. · Please specify a group ID. · Invalid group ID. · The device ID is required. · Please specify a device ID. · Invalid device ID. · The device IP is required. · Please specify a device IP. · Invalid device IP. · The device name is required. · Please specify a device name. · Invalid device name. · The interface name is required. · The interface name is required. · Invalid interface name. · The specified fabric ID does not exist. · The specified group ID does not exist. · The specified fabric name does not exist. · The specified device ID does not exist. · The specified device IP does not exist. · The specified device name does not exist. · The specified interface name does not exist. · DataCenter service is not available. · The system service does not respond.

Update custom outgoing external flow

Keyword	UPDATE_UC_OUT_NETWORK_TRAFFIC_CUSTOM
Message text	Updated custom U-Center outgoing external flow.
Variable fields	N/A
Example	Updated custom U-Center outgoing external flow.
Explanation	A custom outgoing external flow was edited.
Possible failure causes	· Invalid JSON format. · The UUID is invalid. · The fabric ID is required. · Please specify a fabric ID. · Invalid fabric ID. · The fabric name is required. · Please specify a fabric name. · Invalid fabric name. · The group ID is required. · Please specify a group ID. · Invalid group ID. · The device ID is required. · Please specify a device ID. · Invalid device ID. · The device IP is required. · Please specify a device IP. · Invalid device IP. · The device name is required. · Please specify a device name. · Invalid device name. · The interface name is required. · The interface name is required. · Invalid interface name. · The specified fabric ID does not exist. · The specified group ID does not exist. · The specified fabric name does not exist. · The specified device ID does not exist. · The specified device IP does not exist. · The specified device name does not exist. · The specified interface name does not exist. · The DC service is unavailable. · The custom info does not exist. · The system service does not respond.

Delete custom outgoing external flow

Keyword	CREATE_UC_OUT_NETWORK_TRAFFIC_CUSTOM
Message text	Deleted custom U-Center outgoing external flow.
Variable fields	N/A
Example	Deleted custom U-Center outgoing external flow.
Explanation	A custom outgoing external flow was deleted.
Possible failure causes	· The UUID is invalid. · The custom info does not exist. · The system service does not respond.

Create custom service flow

Keyword	CREATE_UC_SERVICE_TRAFFIC_CUSTOM
Message text	Created custom U-Center service flow.
Variable fields	N/A
Example	Created custom U-Center service flow.
Explanation	A custom service flow was created.
Possible failure causes	· The request message body is empty. · The traffic type must be LB or FW. · The traffic type is required. · The traffic attribute is required. · The traffic attribute must be incoming traffic or outgoing traffic. · Invalid tenant name. · The specified tenant name does not exist. · A flow of the specified type already exists. · The DC service is unavailable. · The system service does not respond.

Update custom service flow

Keyword	UPDATE_UC_SERVICE_TRAFFIC_CUSTOM
Message text	Updated custom U-Center service flow.
Variable fields	N/A
Example	Updated custom U-Center service flow.
Explanation	A custom service flow was edited.
Possible failure causes	· The UUID is invalid. · The request message body is empty. · The traffic type must be LB or FW. · The traffic type is required. · The traffic attribute is required. · The traffic attribute must be incoming traffic or outgoing traffic. · Invalid tenant name. · The specified tenant name does not exist. · The DC service is unavailable. · The system service does not respond.

Delete custom service flow

Keyword	DELETE_UC_SERVICE_TRAFFIC_CUSTOM
Message text	Deleted custom U-Center service flow.
Variable fields	N/A
Example	Deleted custom U-Center service flow.
Explanation	A custom service flow was deleted.
Possible failure causes	· The UUID is invalid. · The custom info does not exist. · The system service does not respond.

Fabrics

This section contains fabric messages.

Create Fabric

Keyword	CREATE_FABRIC_OP
Message text	Created fabric: $1
Variable fields	$1: Fabric name.
Example	Created fabric: “fabric1”.
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. · You have no privilege to perform this operation. · Failed to change the AS number, because the new AS number introduces RT conflicts. · The MTU must be an integer in the range of 68 to 9216.

Update Fabric

Keyword	UPDATE_FABRIC _OP
Message text	Updated fabric: $1
Variable fields	$1: Fabric name.
Example	Updated fabric: “fabric1”.
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. · Cannot modify the AS number of the fabric in which the border devices already have DC connections established. · You have no privilege to perform this operation. · Cannot enable multicast network capabilities because the fabric has been added to a fabric connection · Failed to change the AS number, because the new AS number introduces RT conflicts. · The MTU must be an integer in the range of 68 to 9216.

Delete Fabric

Keyword	DELETE_FABRIC _OP
Message text	Deleted fabric: $1
Variable fields	$1: Fabric name.
Example	Deleted fabric: “fabric1”.
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 being used by a DHCP host group. · 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. · You have no privilege to perform this operation. · You cannot delete the fabric. It has been bound to a BGP peer. · The fabric is used by a bgp instance, and cannot be deleted.

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. · You have no privilege to perform this operation.

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 border device group. · Unknown internal server error. · You have no privilege to perform this operation. · Cannot configure a fabric connection because multicast network capabilities have been enabled for the fabric. · The source and destination devices must use the same version of VTEP IP addresses to establish a fabric connection.

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 border device group. · Unknown internal server error. · You have no privilege to perform this operation. · Cannot configure a fabric connection because multicast network capabilities have been enabled for the fabric.

Delete Fabric Connection

Keyword	DELETE_FABRIC_CONNECTION_OP
Message text	Deleted fabric connection: $1
Variable fields	$1: Fabric UUID.
Example	Deleted fabric connection: 218b5f2f-e435-4365-a1ab-0eaa03b7fa19
Explanation	A user deleted a fabric.
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. · You have no privilege to perform this operation.

FWaaS

This section contains messages from the firewall service module.

Create time range

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

Update time range

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

Delete time range

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

Create firewall object group

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

Update firewall object group

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

Delete firewall object group

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

Create firewall object

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

Update firewall object

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

Delete firewall object

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

Create firewall rule

Keyword	CREATE_FWRULE_OP
Message text	Created firewall rule $1.
Variable fields	$1: Information about the firewall rule.
Example	Created firewall rule ID: b52fff79-7bcf-4bff-9340-68c5f6c1c495 Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: fw_rule Description: firewall rule Shared: true Protocol: null IP version: IPv4 Source IP address: 22.2.2.2 Destination IP address: 11.1.1.1 Source port: 100:200 Destination port: 300:400 Position: null Action: INSPECT Enabled: true Time range ID: 9a83d713-8e79-4ca8-a2e9-8df29daf5fd6 App profile ID: 62214486-42a8-455a-ae6c-90853038fd0a IPS policy ID: 00000000-0000-0000-0000-000000000000 URL filter policy ID: 230f47be-63f4-4ae0-a488-b72a8d841b1f AV policy ID: 00000000-0000-0000-0000-000000000000 Logging: true Counting: true Object group-based matching: true Source IP object group ID: b52fff79-7bcf-4bff-9340-68c5f6cfffff Destination IP object group ID: b52fff79-7bcf-4bff-9340-68c5f6ceeeee Service object group ID: b52fff79-7bcf-4bff-9340-68c5f6crrrrr
Explanation	A firewall rule was created.
Possible failure causes	· The configuration item already exists. · The tenant specified for the configuration item doesn't exist. · The tenant IDs for the configuration items are different. · The time range specified for the rule doesn't exist. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The firewall service has not been found. · The match rules for virtual firewalls do not support the reject action. · Failed to add the configuration item. · If the action is DPI, you must specify an IPS policy, AV policy, or URL filtering policy by its ID. · The source IP object group name is read only. · The destination IP object group name is read only. · The service object group name is read only. · The policy ID is read only. · The policy name is read only. · You have no privilege to perform this operation.

Update firewall rule

Keyword	UPDATE_FWRULE_OP
Message text	Updated firewall rule $1.
Variable fields	$1: Information about the firewall rule.
Example	Updated firewall rule ID: b52fff79-7bcf-4bff-9340-68c5f6c1c495 Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: fw_rule Description: firewall rule Shared: true Protocol: TCP IP version: IPv4 Source IP address: 22.2.2.2 Destination IP address: 11.1.1.1 Source port: 1222:1222 Destination port: 1333:1333 Position: null Action: INSPECT Enabled: true Time range ID: 9a83d713-8e79-4ca8-a2e9-8df29daf5fd6 Time range ID: 9a83d713-8e79-4ca8-a2e9-8df29daf5fd6 App profile ID: 62214486-42a8-455a-ae6c-90853038fd0a IPS policy ID: 00000000-0000-0000-0000-000000000000 URL filter policy ID: 230f47be-63f4-4ae0-a488-b72a8d841b1f AV policy ID: 00000000-0000-0000-0000-000000000000 Logging: true Counting: true Object group match: true Source IP object group ID: b52fff79-7bcf-4bff-9340-68c5f6cfffff Destination IP object group ID: b52fff79-7bcf-4bff-9340-68c5f6ceeeee Service object group ID: b52fff79-7bcf-4bff-9340-68c5f6crrrrr
Explanation	A firewall rule was modified.
Possible failure causes	· The time range specified for the rule doesn't exist. · The tenant IDs for the configuration items are different. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The firewall service has not been found. · The configuration item doesn't exist. · The match rules for virtual firewalls do not support the reject action. · If the action is DPI, you must specify an IPS policy, AV policy, or URL filtering policy by its ID. · The source IP object group name is read only. · The destination IP object group name is read only. · The service object group name is read only. · The ID is read only. · The tenant ID is read only. · The policy ID is read only. · The policy name is read only. · You have no privilege to perform this operation.

Delete firewall rule

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

Create firewall policy

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

Update firewall policy

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

Delete firewall policy

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

Create firewall

Keyword	CREATE_FW_OP
Message text	Created firewall $1.
Variable fields	$1: Information about the firewall.
Example	Created firewall ID: 6835896c-5152-4bed-a2ab-092c9980e2b8 Tenant ID : ffffffff-0000-0000-0000-000000000001 Name: fw Description: firewall Status: DOWN Shared: true Forward firewall policy ID: d233005f-22bd-4e2b-8ac0-bdef810f533a Backward firewall policy ID: c133005f-23bd-5a6b-7bb0-dbef710f524c Forward attack defense policy ID: d233005f-22bd-4e2b-8ac0-bdef810f533e Backward attack defense policy ID: d233005f-22bd-4e2b-8ac0-bdef810f533f Mode: GATEWAY Router ID: 78dce1d6-8ba5-4bb4-b909-0d83659c40b2.
Explanation	A firewall was created.
Possible failure causes	· The configuration item already exists. · The tenant specified for the configuration item doesn't exist. · The tenant IDs for the firewall and the specified forward firewall policy are different. · The tenant IDs for the firewall and the specified backward firewall policy are different. · The tenant IDs for the firewall and the specified vRouter are different. · The tenant IDs for the firewall and the specified network resource are different. · The forward firewall policy specified for the firewall doesn't exist. · The backward firewall policy specified for the firewall doesn't exist. · The forward firewall policy is already used by another firewall. · The backward firewall policy is already used by another firewall. · The forward attack defense policy is already used by another firewall. · The backward attack defense policy is already used by another firewall. · The vRouter specified for the firewall doesn't exist. · The vRouter is already used by another firewall. · The type of the network resource specified for the firewall is not vFW. · The network resource specified for the firewall doesn't exist. · The number of firewalls bound to the resource exceeded the limit. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The firewall service has not been found. · The specified resource is not associated with any resource access template or the associated resource access template is unavailable. · You have no privilege to perform this operation. · Total firewall rules reached the limit. · Make sure the access device in the resource access template and the service chain firewall use the same connection mode. · You cannot specify a connection mode for the gateway firewall. · The firewall is configured for service chaining, please specify a connection mode. · You cannot specify an outbound attack prevention policy for a one-arm firewall to be used as a service chain node. · You cannot specify an outbound security policy for a one-arm firewall to be used as a service chain node.

Update firewall

Keyword	UPDATE_FW_OP
Message text	Updated firewall $1.
Variable fields	$1: Information about the firewall.
Example	Updated firewall ID: 6835896c-5152-4bed-a2ab-092c9980e2b8 Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: fw Description: firewall Status: ACTIVE Shared: true Forward firewall policy ID: 572744ad-6bda-4617-aef2-78b58a068f93 Backward firewall policy ID: c133005f-23bd-5a6b-7bb0-dbef710f524c Forward attack defense policy ID: d233005f-22bd-4e2b-8ac0-bdef810f533e Backward attack defense policy ID: d233005f-22bd-4e2b-8ac0-bdef810f533f Mode: GATEWAY Router ID: 2bdbafbf-f899-42af-b2ce-e21122ad1d1b.
Explanation	A firewall was modified.
Possible failure causes	· The tenant IDs for the firewall and the specified forward firewall policy are different. · The tenant IDs for the firewall and the specified backward firewall policy are different. · The tenant IDs for the firewall and the specified vRouter are different. · The tenant IDs for the firewall and the specified network resource are different. · The forward firewall policy specified for the firewall doesn't exist. · The backward firewall policy specified for the firewall doesn't exist. · The forward firewall policy is already used by another firewall. · The backward firewall policy is already used by another firewall. · The forward attack defense policy is already used by another firewall. · The backward attack defense policy is already used by another firewall. · The vRouter specified for the firewall doesn't exist. · The vRouter is already used by another firewall. · The type of the network resource specified for the firewall is not vFW. · The network resource specified for the firewall doesn't exist. · The number of firewalls bound to the resource exceeded the limit. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration deletion is in progress. · Configuration recovery is in progress. · The firewall service has not been found. · The configuration item doesn't exist. · The specified resource is not associated with any resource access template or the associated resource access template is unavailable. · You have no privilege to perform this operation. · Total firewall rules reached the limit. · You cannot change the connection mode of the firewall, because it has been bound to a service path. · You cannot unbind the resource, because the firewall has been bound to a service chain or service path. · Make sure the access device in the resource access template and the service chain firewall use the same connection mode. · You cannot specify a connection mode for the gateway firewall. · The firewall is configured for service chaining, please specify a connection mode. · You cannot specify an outbound attack prevention policy for a one-arm firewall to be used as a service chain node. · You cannot specify an outbound security policy for a one-arm firewall to be used as a service chain node.

Delete firewall

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

Create IPS policy

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

Update IPS policy

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

Delete IPS policy

Keyword	DELETE_IPSPOLICY_OP
Message text	Deleted IPS policy $1.
Variable fields	$1: IPS policy name.
Example	Deleted IPS policy IPS.
Explanation	An IPS policy was deleted.
Possible failure causes	· The configuration item doesn't exist. · The controller is not the active leader. · Configuration recovery is in progress. · The service has not been found. · You have no privilege to perform this operation.

Create IPS template

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

Update IPS template

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

Delete IPS template

Keyword	DELETE_IPSTEMPLATE_OP
Message text	Deleted IPS template $1.
Variable fields	$1: IPS template name.
Example	Deleted IPS template IPS.
Explanation	An IPS template was deleted.
Possible failure causes	· The configuration item doesn't exist. · The controller is not the active leader. · Configuration recovery is in progress. · The service has not been found. · You have no privilege to perform this operation.

Upload IPS signature library from local device

Keyword	UPLOAD_IPSSIGNATURE_OP
Message text	Uploaded IPS signature library $1 from local device.
Variable fields	$1: Name of the IPS signature library file.
Example	Uploaded IPS signature library V7-IPS-1.0.15.dat from local device.
Explanation	An IPS signature library file was uploaded from the local device to the SDN controller.
Possible failure causes	· The IPS signature library file is invalid or it can’t be parsed. · The controller is not the active leader. · Configuration recovery is in progress. · The service has not been found. · Uploading aborted because of abnormal firewall service. · The signature library service has not been found. · You have no privilege to perform this operation.

Create AV policy

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

Update AV policy

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

Delete AV policy

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

Create AV template

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

Update AV template

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

Delete AV template

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

Upload virus library from local device

Keyword	UPLOAD_VIRUSLIBRARY_OP
Message text	Uploaded virus library $1 from local device.
Variable fields	$1: Name of the virus library file.
Example	Uploaded virus library V7-AV-1.0.15.dat from local device.
Explanation	A virus library file was uploaded from the local device to the SDN controller.
Possible failure causes	· The virus library file is invalid or it can’t be parsed. · The controller is not the active leader. · Configuration recovery is in progress. · The service has not been found. · Uploading aborted because of abnormal firewall service. · The signature library service has not been found. · You have no privilege to perform this operation.

Upload application library from local device

Keyword	UPLOAD_APPLIBRARY_OP
Message text	Uploaded application library $1 from local device.
Variable fields	$1: Name of the application library file.
Example	Uploaded application library V7-APP-1.0.41.dat from local device.
Explanation	An application library file was uploaded from the local device to the SDN controller.
Possible failure causes	· The application library file is invalid or it can’t be parsed. · The controller is not the active leader. · Configuration recovery is in progress. · The service has not been found. · Uploading aborted because of abnormal firewall service. · The signature library service has not been found. · You have no privilege to perform this operation.

Create attack defense policy

Keyword	CREATE_ATKDEFPOLICY_OP
Message text	Created attack defense policy $1.
Variable fields	$1: Information about the attack defense policy.
Example	Created attack defense policy ID: 70dc3186-ac5b-4ba1-ac7f-7a27ef566efb Name: fw_policy Tenant ID: ffffffff-0000-0000-0000-000000000001 Description: policy
Explanation	An attack defense policy was created.
Possible failure causes	· No tenant ID is specified. · No policy name is specified. · Invalid JSON format. · The value of the threshold must be an integer in the range of 1 to 1000000. · The configuration item already exists. · The tenant specified for the configuration item doesn't exist. · The controller is not the active leader. · The large ICMP packet length is an integer in the range of 28 to 65534. · You have no privilege to perform this operation.

Update attack defense policy

Keyword	UPDATE_ATKDEFPOLICY_OP
Message text	Updated attack defense policy $1.
Variable fields	$1: Information about the attack defense policy.
Example	Updated attack defense policy ID: 5f206f6d-e400-4f25-896f-791678132664 Name: policy Tenant ID: ffffffff-0000-0000-0000-000000000001 Description: ABCDEFG.
Explanation	An attack defense policy was modified.
Possible failure causes	· Invalid JSON format. · The value of the threshold must be an integer in the range of 1 to 1000000. · The controller is not the active leader. · The configuration item doesn't exist. · The large ICMP packet length is an integer in the range of 28 to 65534. · You have no privilege to perform this operation.

Delete attack defense policy

Keyword	DELETE_ATKDEFPOLICY_OP
Message text	Deleted attack defense policy $1.
Variable fields	$1: Name of the attack defense policy
Example	Deleted attack defense policy atk_policy.
Explanation	An attack defense policy was deleted.
Possible failure causes	· The configuration item is in use. · The configuration item doesn’t exist. · The controller is not the active leader. · You have no privilege to perform this operation.

Create URL filter category

Keyword	CREATE_URL_CATEGORY_OP
Message text	Created URL filter category $1.
Variable fields	$1: Information about the URL filter category.
Example	Created URL filter category ID: 0ad7e32e-f163-4fb9-b272-f9e2977d40be Name: category1 Tenant ID: ffffffff-0000-0000-0000-000000000001 Tenant name: default Severity: 1000 Description: category1 URL filter rules: [].
Explanation	A URL filter category was created.
Possible failure causes	· The configuration item already exists. · The tenant specified for the configuration item doesn't exist. · The controller is not the active leader. · Invalid JSON format. · The URL filter categories created for the sane tenant must have different severity levels. · You have no privilege to perform this operation.

Update URL filter category

Keyword	UPDATE_URL_CATEGORY_OP
Message text	Updated URL filter category $1.
Variable fields	$1: Information about the URL filter category.
Example	Updated URL filter category ID: 0ad7e32e-f163-4fb9-b272-f9e2977d40be Name: category1 Tenant ID: ffffffff-0000-0000-0000-000000000001 Tenant name: default Severity: 1000 Description: category1 URL filter rules: [].
Explanation	A URL filter category was modified.
Possible failure causes	· The controller is not the active leader. · The configuration item doesn’t exist. · Invalid JSON format. · The URL filter categories created for the sane tenant must have different severity levels. · You have no privilege to perform this operation.

Delete URL filter category

Keyword	DELETE_URL_CATEGORY_OP
Message text	Deleted URL filter category $1.
Variable fields	$1: Name of the URL filter category.
Example	Deleted URL filter category category1.
Explanation	A URL filter category was deleted.
Possible failure causes	· The configuration item is in use. · The configuration item doesn’t exist. · The controller is not the active leader. · You have no privilege to perform this operation.

Create URL filter rule

Keyword	CREATE_URL_RULE_OP
Message text	Created URL filter rule $1.
Variable fields	$1: Information about the URL filter rule.
Example	Created URL filter rule ID: 954a1680-fd27-4cc1-b5ec-8f530c81f57a Category ID: f600c3fc-3c53-4b31-bc30-bfdd7177660b Rule ID: 1 Host filter type: TEXT Host name: 1234 URI filter type: REGEX URI: 12345
Explanation	A URL filter rule was created.
Possible failure causes	· The configuration item already exists. · The tenant specified for the configuration item doesn't exist. · The controller is not the active leader. · Invalid JSON format. · You have no privilege to perform this operation.

Update URL filter rule

Keyword	UPDATE_URL_RULE_OP
Message text	Updated URL filter rule $1.
Variable fields	$1: Information about the URL filter rule.
Example	Updated URL filter rule ID: 954a1680-fd27-4cc1-b5ec-8f530c81f57a Category ID: f600c3fc-3c53-4b31-bc30-bfdd7177660b Rule ID: 1 Host filter type: TEXT Host name: 1234 URI filter type: REGEX URI: 12345..
Explanation	A URL filter rule was modified.
Possible failure causes	· The controller is not the active leader. · The configuration item doesn’t exist. · Invalid JSON format. · You have no privilege to perform this operation.

Delete URL filter rule

Keyword	DELETE_URL_RULE_OP
Message text	Deleted URL filter rule $1.
Variable fields	$1: ID of the URL filter rule.
Example	Deleted URL filter rule 954a1680-fd27-4cc1-b5ec-8f530c81f57a.
Explanation	A URL filter rule was deleted.
Possible failure causes	· The configuration item is in use. · The configuration item doesn’t exist. · The controller is not the active leader. · You have no privilege to perform this operation.

Create URL filter policy

Keyword	CREATE_URL_POLICY_OP
Message text	Created URL filter policy $1.
Variable fields	$1: Information about the URL filter policy.
Example	Created URL filter policy ID: e9c2d8b7-1a6f-49db-b36a-b86ed8ca3a04 Name: policy1 Tenant ID: 28a270bd-fd71-455d-b337-6281f9175bd9 Tenant name: ht Description: null
Explanation	A URL filter policy was created.
Possible failure causes	· The configuration item already exists. · The tenant specified for the configuration item doesn't exist. · The selected URL filter categories contain invalid categories. · The controller is not the active leader. · Invalid JSON format. · You have no privilege to perform this operation.

Update URL filter policy

Keyword	UPDATE_URL_POLICY_OP
Message text	Updated URL filter policy $1.
Variable fields	$1: Information about the URL filter policy.
Example	Updated URL filter policy ID: e9c2d8b7-1a6f-49db-b36a-b86ed8ca3a04 Name: policy1 Tenant ID: 28a270bd-fd71-455d-b337-6281f9175bd9 Tenant name: ht Description: null
Explanation	A URL filter policy was modified.
Possible failure causes	· The controller is not the active leader. · The configuration item doesn’t exist. · The selected URL filter categories contain invalid categories. · Invalid JSON format. · You have no privilege to perform this operation.

Delete URL filter policy

Keyword	DELETE_URL_POLICY_OP
Message text	Deleted URL filter policy $1.
Variable fields	$1: Name of the URL filter policy.
Example	Deleted URL filter policy policy1.
Explanation	A URL filter policy was deleted.
Possible failure causes	· The configuration item is in use. · The configuration item doesn’t exist. · The controller is not the active leader. · You have no privilege to perform this operation.

LBaaS

This section contains load balancing messages.

Create load balancer

Keyword	CREATE_LB_OP
Message text	Created load balancer $1.
Variable fields	$1: Load balancer information.
Example	Created load balancer ID: 41e38478-da02-49e3-986e-6356ddd304f8 Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: 9 Description: Type: SERVER Mode: GATEWAY Router ID: 5f96684a-5368-433c-bd26-158d351affd4 Status: DOWN Listener IDs: [ 4914ac1e-4acf-4966-b7de-c5c495751da9 ] Version: LB_V2.
Explanation	A load balancer was created.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · The service has not been found. · The configuration item already exists. · The tenant specified for the configuration item doesn't exist. · The load balancer mode can only be GATEWAY, CGSR, or SERVICE_CHAIN. · The resource specified for the load balancer doesn't exist. · The pool specified for the load balancer doesn't exist. · The pool is already used by another the load balancer. · The tenant IDs for the load balancer and the specified pool are different. · The VIP address must belong to the subnet of the pool. · The load balancers in the same VIP must have the same mode. · The subnet for the VIP and member are different. · Only the SERVICE_CHAIN type load balancers support server pool list configuration. · The VIP corresponding to the specified pool is enabled with SNAT and cannot be used by the SERVICE_CHAIN type load balancers. · The listener specified for the load balancer doesn't exist. · The listener is already used by another the load balancer. · The tenant IDs for the load balancer and the specified listener are different. · Only the SERVICE_CHAIN type load balancers support listener list configuration. · The listeners using the same VIP can be used only by the load balancers of the same mode. · The specified listener is already enabled with SNAT. The pool cannot be applied to a SERVICE_CHAIN type load balancer. · The tenant ID must be specified. · The status is read only. · The tenant name is read only. · The resource name is read only. · The pool name is read only. · Failed to add the configuration item. · The resource ID can not be specified in gateway mode. · The load balancer in service chain mode supports only network resources of the LB type. · The router ID is read only. · The router name is read only. · Only SERVER type load balancer supported. · The specified pool is not referenced by any listener. · The load balancer can not have pools and listeners at one time. · The specified resource is not associated with any resource access template or the associated resource access template is unavailable. · The port number and associated virtual server IP address of one listener cannot both be the same as the port number and associated virtual server IP address of another listener. · The IP addresses and port numbers of virtual servers associated with two server pools cannot both be the same. · You have no privilege to perform this operation. · Load balancers do not support the one-arm connection mode. · In EVPN networking environment, listeners using the same pool cannot be bound to multiple service-chain load balancers.

Update load balancer

Keyword	UPDATE_LB_OP
Message text	Updated load balancer $1.
Variable fields	$1: Load balancer information.
Example	Updated load balancer ID: 41e38478-da02-49e3-986e-6356ddd304f8 Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: 9 Description: Type: SERVER Mode: GATEWAY Router ID: 5f96684a-5368-433c-bd26-158d351affd4 Status: DOWN Listener IDs: [ 4914ac1e-4acf-4966-b7de-c5c495751da9 ] Version: LB_V2.
Explanation	A load balancer was modified.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · The service has not been found. · The configuration item doesn't exist. · The resource specified for the load balancer doesn't exist. · The pool specified for the load balancer doesn't exist. · The pool is already used by another the load balancer. · The tenant IDs for the load balancer and the specified pool are different. · The VIP address must belong to the subnet of the pool. · The subnet for the VIP and member are different. · Only the SERVICE_CHAIN type load balancers support server pool list configuration. · The VIP corresponding to the specified pool is enabled with SNAT and cannot be used by the SERVICE_CHAIN type load balancers. · The listener specified for the load balancer doesn't exist. · The listener is already used by another the load balancer. · The tenant IDs for the load balancer and the specified listener are different. · Only the SERVICE_CHAIN type load balancers support listener list configuration. · The specified listener is already enabled with SNAT. The pool cannot be applied to a SERVICE_CHAIN type load balancer. · The listeners using the same VIP can be used only by the load balancers of the same mode. · The status is read only. · The tenant name is read only. · The resource name is read only. · The pool name is read only. · The ID can not be modified. · The mode can not be modified. · The tenant ID can not be modified. · Failed to modify the configuration item. · The resource ID can not be specified in gateway mode. · The load balancer in service chain mode supports only network resources of the LB type. · The router ID is read only. · The router name is read only. · The specified pool is not referenced by any listener. · The load balancer can not have pools and listeners at one time. · The specified resource is not associated with any resource access template or the associated resource access template is unavailable. · The port number and associated virtual server IP address of one listener cannot both be the same as the port number and associated virtual server IP address of another listener. · The IP addresses and port numbers of virtual servers associated with two server pools cannot both be the same. · You have no privilege to perform this operation. · You cannot unbind the resource, because the load balancer has been bound to a service chain or service path. · Load balancers do not support the one-arm connection mode. · In EVPN networking environment, listeners using the same pool cannot be bound to multiple service-chain load balancers.

Delete load balancer

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

Create VIP

Keyword	CREATE_VIRTUALIP_OP
Message text	Created VIP $1.
Variable fields	$1: Virtual server information.
Example	Created VIP ID: 6db0736e-4557-4062-b17e-820dfccc54d4 Name: virly Description: Tenant ID: ffffffff-0000-0000-0000-000000000001 Subnet ID: 97e33f9d-da04-4caa-808d-e48a82718b2f IP address: 10.10.10.10 Admin state up: true Status: DOWN
Explanation	A virtual server was created for load balancing v2.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Invalid json format. · The service has not been found. · The configuration item already exists. · The tenant specified for the configuration item doesn't exist. · The IP address already exists. · The IP address doesn't belong to the subnet. · The subnet specified for the VIP doesn’t exist. · The tenant IDs for the VIP and the specified subnet are different. · The specified VIP address conflicts with a vPort IP, gateway IP, APP cluster VIP, or available address pair. · The tenant ID must be specified. · Only an IPv4 subnet can be specified. · You have no privilege to perform this operation.

Update VIP

Keyword	UPDATE_VIRTUALIP_OP
Message text	Updated VIP $1.
Variable fields	$1: Virtual server information.
Example	Updated VIP ID: 6db0736e-4557-4062-b17e-820dfccc54d4 Name: virly Description: Tenant ID: ffffffff-0000-0000-0000-000000000001 Subnet ID: 97e33f9d-da04-4caa-808d-e48a82718b2f IP address: 10.10.10.10 Admin state up: true Status: DOWN.
Explanation	A virtual server was modified for load balancing v2.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · The service has not been found. · The configuration item doesn't exist. · The IP address already exists. · The VIP ID is read-only. · The VIP name is read-only. · The subnet ID is read-only. · The virtual port ID is read-only. · The IP address doesn't belong to the subnet. · The tenant IDs for the VIP and the specified subnet are different. · You have no privilege to perform this operation.

Delete VIP

Keyword	DELETE_VIRTUALIP_OP
Message text		Deleted VIP $1.
Variable fields		$1: Virtual server name.
Example		Deleted VIP virtualip60.
Explanation		A virtual server was deleted for load balancing v2.
Possible failure causes		· The controller is not the active leader. · Configuration recovery is in progress. · The service has not been found. · The configuration item doesn't exist. · The configuration item is in use. · Failed to delete the configuration item. · You have no privilege to perform this operation.

Create listener

Keyword	CREATE_LISTENER_OP
Message text	Created listener $1.
Variable fields	$1: Listener information.
Example	Created listener ID: ab8121f1-65b6-4709-8153-43695b83a187 Name: listener60 Description: Tenant ID: 00000000-0000-0000-0000-000000000000 Default pool ID: 5ba4d32a-8373-423c-b1e9-78de52f0733d Protocol: HTTP Protocol port: 6 Admin state up: true Connection limit: 0 VIP ID: ab8121f1-65b6-4709-8153-43695b83a121 Enable SNAT: false Status: DOWN.
Explanation	A listener was created.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · The service has not been found. · The configuration item already exists. · The configuration item doesn't exist. · The tenant specified for the configuration item doesn't exist. · The tenant IDs for the listener and the specified VIP are different. · The port number is used by another listener using the same VIP. · The tenant IDs for the listener and the specified default pool are different. · The VIP for the specified default pool is different from the VIP used by the listener. · The vRouters for the default pool and the VIP are different for the listener. · The tenant name is read only. · The pool name is read only. · The tenant ID must be specified. · The protocol must be specified. · The protocol port must be specified. · The connection limit must be specified. · Failed to add the configuration item. · The virtual IP specified for the configuration item doesn't exist. · The defaultPoolId specified for the configuration item doesn't exist. · The virtualIp ID must be specified. · The policy can be bound only to the listener whose protocol type is HTTP or HTTPS. · A TCP-type listener doesn't support enabling XFF. · Only HTTPS-type listeners support SSL certificate and SSL key configuration. · The SSL certificate and SSL key must be both specified or both left unspecified. · To enable XFF for a listener whose protocol is HTTPS, you must specify SSL settings first. · Invalid SSL certificate. · Invalid SSL key. · You must configure a digital certificate when the listening protocol is HTTPS and multi-pool policies have been added. · You must configure a digital certificate when the listening protocol is HTTPS and XFF is enabled. · You have no privilege to perform this operation.

Update listener

Keyword	UPDATE_LISTENER_OP
Message text	Updated listener $1.
Variable fields	$1: Listener information.
Example	Updated listener ID: ab8121f1-65b6-4709-8153-43695b83a187 Name: listener60 Description: Tenant ID: 00000000-0000-0000-0000-000000000000 Default pool ID: 5ba4d32a-8373-423c-b1e9-78de52f0733d Protocol: HTTP Protocol port: 6 Admin state up: true Connection limit: 0 VIP ID: ab8121f1-65b6-4709-8153-43695b83a121 Enable SNAT: false Status: DOWN.
Explanation	A listener was modified.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · The service has not been found. · The configuration item doesn't exist. · The tenant IDs for the VIP and the specified listener are different. · The tenant IDs for the listener and the specified default pool are different. · The VIP for the specified default pool is different from the VIP used by the listener. · The vRouters for the default pool and the VIP are different for the listener. · The virtualIp specified for the configuration item doesn't exist. · The defaultPoolId specified for the configuration item doesn't exist. · The virtualIp ID must be specified. · The default pool name can not be modified. · The virtualip ID can not be modified. · A TCP-type listener doesn't support enabling XFF. · Only HTTPS-type listeners support SSL certificate and SSL key configuration. · The SSL certificate and SSL key must be both specified or both left unspecified. · To enable XFF for a listener whose protocol is HTTPS, you must specify SSL settings first. · Invalid SSL certificate. · Invalid SSL key. · SSL-related configuration can’t be deleted if the listener of the HTTPS protocol type has been bound with a policy. · You must configure a digital certificate when the listening protocol is HTTPS and multi-pool policies have been added. · You must configure a digital certificate when the listening protocol is HTTPS and XFF is enabled. · You have no privilege to perform this operation.

Delete listener

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

Create policy

Keyword	CREATE_LBPOLICY_OP
Message text		Created policy $1.
Variable fields		$1: Policy configuration information.
Example		Created policy ID: 0f4777cb-724d-4298-b2dd-1700f4183399 Name: l7test Description: Tenant ID: ffffffff-0000-0000-0000-000000000001 Listener ID: eeed4b2e-f42c-4f03-b9f0-acfe2cfea565 Priority: 1 Actions: { Type: Redirect to URL Redirect URL: aaa } Admin state up: true.
Explanation		A policy was created.
Possible failure causes		· The controller is not the active leader. · Invalid json format. · The configuration item already exists. · Configuration recovery is in progress. · The service has not been found. · The configuration item doesn't exist. · The tenant ID must be specified. · The actions is required. · The listener ID is required. · The tenant specified for the configuration item doesn't exist. · Invalid URL. · The listener specified for the policy doesn't exist. · The tenant IDs for the specified listener and the specified pool are different. · A listener can be bound to a maximum of 5000 policies. · The VIP for the specified pool is different from the VIP used by the listener bound with the policy. · The vRouters for the pool and the listener are different for the policy. · The policy can be bound only to the listener whose protocol type is HTTP or HTTPS. · A policy can contain only one action. · The tenant IDs for the specified pool and the policy are different. · The action type is required. · When the action type is REDIRECT_TO_POOL, you must specify the pool ID. · When the action type is REDIRECT_TO_URL, you must specify the URL. · The specified pool doesn't exist. · No VIP is specified for the listener. · The tenant IDs for the specified listener and the policy are different. · The policy is required. · Failed to add the configuration item. · You have no privilege to perform this operation. · In EVPN networking environment, listeners using the same pool cannot be bound to multiple service-chain load balancers

Update policy

Keyword	UPDATE_LBPOLICY_OP
Message text		Updated policy $1.
Variable fields		$1: Policy configuration information.
Example		Updated policy ID: 0f4777cb-724d-4298-b2dd-1700f4183399 Name: l7test Description: Admin state up: true Tenant ID: ffffffff-0000-0000-0000-000000000001 Listener ID: eeed4b2e-f42c-4f03-b9f0-acfe2cfea565 Priority: 1 Actions: { Type: Redirect to URL Redirect URL: aaa }.
Explanation		A policy was modified.
Possible failure causes		· The controller is not the active leader. · Invalid json format. · Configuration recovery is in progress. · The service has not been found. · The configuration item doesn't exist. · The ID can not be modified. · The tenant ID can not be modified. · The listener ID can not be modified. · The pool specified for the configuration item doesn't exist. · Failed to modify the configuration item. · Invalid URL. · The tenant IDs for the specified listener and the specified pool are different. · The VIP for the specified pool is different from the VIP used by the listener bound with the policy. · The vRouters for the pool and the listener are different for the policy. · The actions is required. · The policy name is read only. · A policy can contain only one action. · The tenant IDs for the specified pool and the policy are different. · The action type is required. · When the action type is REDIRECT_TO_POOL, you must specify the pool ID. · When the action type is REDIRECT_TO_URL, you must specify the URL. · No VIP is specified for the listener. · Failed to modify the configuration item. · You have no privilege to perform this operation. · In EVPN networking environment, listeners using the same pool cannot be bound to multiple service-chain load balancers.

Delete policy

Keyword	DELETE_LBPOLICY_OP
Message text		Deleted policy $1.
Variable fields		$1: Policy name.
Example		Deleted policy L7test.
Explanation		A policy was deleted.
Possible failure causes		· The controller is not the active leader. · The configuration item doesn't exist. · The service has not been found. · Failed to delete the configuration item. · Configuration recovery is in progress. · You have no privilege to perform this operation.

Create rule

Keyword	CREATE_LBRULE_OP
Message text		Created rule $1.
Variable fields		$1: Rule configuration information.
Example		Created rule ID: 3390118d-b9b7-4a3b-8f7c-d9d240bbf881 Type: HTTP cookie Invert: false Match item: aabb Match type: Equal to Match value: html Policy ID: 3ecfaa2e-9086-4c1c-ac8f-0c8d08e66fcc. Admin state up: true
Explanation		A rule was created.
Possible failure causes		· The controller is not the active leader. · Configuration recovery is in progress. · The service has not been found. · Invalid json format. · The configuration item already exists. · The policy ID is required. · The type is required. · The key is required. · The value is required. · The compare_type is required. · The policy doesn't exist. · When the type is FILE_TYPE, the match type only can be EQUAL_TO. · Invalid value. · Invalid key. · The key is not required when the type is FILE_TYPE, HOST_NAME, or PATH. · A policy can contain a maximum of 256 rules. · Invalid compare_type. · Invalid type. · You have no privilege to perform this operation.

Update rule

Keyword	UPDATE_LBRULE_OP
Message text		Updated rule $1.
Variable fields		$1: Rule configuration information.
Example		Updated rule ID: 3390118d-b9b7-4a3b-8f7c-d9d240bbf881 Type: HTTP cookie Invert: False Match item: aabb Match type: Equal to Match value: html Policy ID: 3ecfaa2e-9086-4c1c-ac8f-0c8d08e66fcc. Admin state up: true
Explanation		A rule was modified.
Possible failure causes		· The controller is not the active leader. · Configuration recovery is in progress. · The service has not been found. · Invalid json format. · The ID can not be modified. · The configuration item doesn't exist. · When the type is FILE_TYPE, the match type only can be EQUAL_TO. · Invalid value. · Invalid key. · The key is not required when the type is FILE_TYPE, HOST_NAME, or PATH. · Failed to modify the configuration item. · The policy ID is read only. · The key is required. · You have no privilege to perform this operation.

Delete rule

Keyword	DELETE_LBRULE_OP
Message text		Deleted rule $1.
Variable fields		$1: Rule ID.
Example		Deleted rule 3390118d-b9b7-4a3b-8f7c-d9d240bbf881.
Explanation		A rule was deleted.
Possible failure causes		· The controller is not the active leader. · Configuration recovery is in progress. · The service has not been found. · The configuration item doesn't exist. · You have no privilege to perform this operation.

Create pool

Keyword	CREATE_POOL_OP
Message text	Created pool $1.
Variable fields	$1: Pool information.
Example	Created pool ID: 5ba4d32a-8373-423c-b1e9-78de52f0733d Tenant ID: 00000000-0000-0000-0000-000000000000 Name: pool70 Description: pool 70 LB method: ROUND_ROBIN Session persistence type: SOURCE_IP Admin state up: true Session persistence cookie name: Status: DOWN Version: LB_V2.
Explanation	A pool was created.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · The service has not been found. · The configuration item already exists. · The tenant specified for the configuration item doesn't exist. · The tenant IDs for the pool and the specified listener are different. · The listener ID must be specified. · The protocol types of the pool and the specified listener are different. · All listeners bound with the pool must specify the same VIP. · The vRouters for the specified listeners and the pool are different. · Invalid listener IDs exist in the listener list. · The status is read only. · The tenant name is read only. · The subnet name is read only. · The health monitor name is read only. · The member ID is read only. · The tenant ID must be specified. · The tenant specified for the configuration item doesn't exist. · The specified subnet doesn't exist. · The tenant IDs for the pool and the specified subnet are different. · The health monitor specified for the pool doesn't exist. · The tenant IDs for the pool and the specified health monitor are different. · Failed to add the configuration item. · The subnet id is read only. · The members of pool are read only. · The member ip is read only. · The method of pool must be specified. · Only an IPv4 subnet can be specified. · You have no privilege to perform this operation.

Update pool

Keyword	UPDATE_POOL_OP
Message text	Updated pool $1.
Variable fields	$1: Pool information.
Example	Updated pool ID: 5ba4d32a-8373-423c-b1e9-78de52f0733d Tenant ID: 00000000-0000-0000-0000-000000000000 Name: pool70 Description: pool 70 LB method: ROUND_ROBIN Session persistence type: SOURCE_IP Session persistence cookie name Admin state up: true Status: DOWN Version: LB_V2.
Explanation	A pool was modified.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · The service has not been found. · The configuration item doesn't exist. · All listeners bound with the pool must specify the same VIP. · The VIP for the specified pool is different from the VIP used by the listeners. · The vRouters for the specified listeners and the pool are different. · The tenant IDs for the pool and the specified listener are different. · The listener ID is read-only · Invalid listener IDs exist in the listener list. · The status is read only. · The members of pool are read only. · The tenant name is read only. · The subnet name is read only. · The health monitor name is read only. · The member ID is read only. · The ID can not be modified. · The tenant ID can not be modified. · The listener id can not be modified. · The health monitor specified for the pool doesn't exist. · The tenant IDs for the pool and the specified health monitor are different. · Failed to modify the configuration item. · The subnet id can not be modified. · The specified subnet doesn't exist. · The tenant IDs for the pool and the specified subnet are different. · The member ip is read only. · The members of pool are read only. · The subnet id is read only. · The pool is used by the SERVICE_CHAIN mode load balancer, and it must contain member IP addresses on the specified subnet. · Only an IPv4 subnet can be specified. · You have no privilege to perform this operation.

Delete pool

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

Create VIP

Keyword	CREATE_VIP_OP
Message text	Created VIP $1.
Variable fields	$1: Virtual server information.
Example	Created VIP ID: ab8121f1-65b6-4709-8153-43695b83a187 Tenant ID: 00000000-0000-0000-0000-000000000000 Name: vip60 Description: Protocol: HTTPS Pool ID: e5c2996e-36d6-4e80-aa2b-deedac360468 Port ID: 09296b20-1f8d-4b17-9862-b920884e34dc Address: 60.0.0.90 Protocol port: 6 Connection limit: 0 Session persistence type: SOURCE_IP Session persistence cookie name: Admin state up: true Status: DOWN.
Explanation	A virtual server was created for load balancing v1.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · The service has not been found. · The configuration item already exists. · The tenant specified for the configuration item doesn't exist. · The protocol types of the VIP and the pool are different. · The pool is already used by another VIP. · The tenant IDs for the VIP and the specified pool are different. · The specified subnet doesn't exist. · The VIP address conflicts with the IP address of a vPort or the subnets of the VIP address and member IP addresses belong to different virtual link layer networks. · The pool specified for the VIP doesn't exist. · The IP address is already used by another VIP. · The VIP address must belong to the subnet of the pool. · The IP address doesn't belong to the subnet. · The pool used by the VIP is used by the SERVICE_CHAIN type load balancers and cannot be enabled with SNAT. · The tenant ID must be specified. · Only an IPv4 subnet can be specified. · The server pool has been referenced by a load balancer, and the IP address and port number cannot both be the same as the IP address and port number of a virtual server associated with any other server pool referenced by the load balancer. · A virtual server of the TCP type or bound with a TCP-type server farm doesn't support enabling XFF. · Only virtual servers of the TCP type or bound with a TCP-type server farm support SSL certificate and SSL key configuration. · To enable XFF for a virtual server whose protocol is HTTPS, you must specify SSL settings first. · The SSL certificate and SSL key must be both specified or both left unspecified. · Invalid SSL certificate. · Invalid SSL key. · You have no privilege to perform this operation.

Update VIP

Keyword	UPDATE_VIP_OP
Message text	Updated VIP $1.
Variable fields	$1: Virtual server information.
Example	Updated VIP ID: ab8121f1-65b6-4709-8153-43695b83a187 Tenant ID: 00000000-0000-0000-0000-000000000000 Name: vip60 Description: Protocol: HTTPS Pool ID: e5c2996e-36d6-4e80-aa2b-deedac360468 Port ID: 09296b20-1f8d-4b17-9862-b920884e34dc Address: 60.0.0.90 Protocol port: 6 Connection limit: 0 Session persistence type: SOURCE_IP Session persistence cookie name: Admin state up: true Status: DOWN.
Explanation	A virtual server was modified for load balancing v1.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · The service has not been found. · The configuration item doesn't exist. · The protocol types of the VIP and the pool are different. · The pool is already used by another VIP. · The tenant IDs for the VIP and the specified pool are different. · The pool specified for the VIP doesn't exist. · The IP address is already used by another VIP. · The pool used by the VIP is used by the SERVICE_CHAIN type load balancers and cannot be enabled with SNAT. · Only an IPv4 subnet can be specified. · The server pool has been referenced by a load balancer, and the IP address and port number cannot both be the same as the IP address and port number of a virtual server associated with any other server pool referenced by the load balancer. · A virtual server of the TCP type or bound with a TCP-type server farm doesn't support enabling XFF. · Only virtual servers of the TCP type or bound with a TCP-type server farm support SSL certificate and SSL key configuration. · To enable XFF for a virtual server whose protocol is HTTPS, you must specify SSL settings first. · The SSL certificate and SSL key must be both specified or both left unspecified. · Invalid SSL certificate. · Invalid SSL key. · You have no privilege to perform this operation.

Delete VIP

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

Create member

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

Update member

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

Delete member

Keyword	DELETE_MEMBER_OP
Message text		Deleted member $1.
Variable fields		$1: Real server configuration information.
Example		Deleted member IP address: 204.1.1.11 Protocol port: 223 Pool ID: f8472b01-3aa2-4a6c-a292-80e7872ceca3.
Explanation		A real server was deleted.
Possible failure causes		· The controller is not the active leader. · Configuration recovery is in progress. · The service has not been found. · The configuration item doesn't exist. · Failed to delete the configuration item. · You have no privilege to perform this operation.

Create health monitor

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

Update health monitor

Keyword	UPDATE_HEALTH_MONITOR_OP
Message text	Updated health monitor $1.
Variable fields	$1: Health monitoring method information.
Example	Updated health monitor ID: 0711c857-2729-41f2-b213-dc4e715bf9bd Tenant ID: 00000000-0000-0000-0000-000000000000 Pool ID: 00000000-0000-0000-0000-000000000010 Name: hm Type: HTTPS Timeout: 11 Delay: 10 Max retries: 12 HTTP method: GET URL path: / Expected codes: 233 Status: DOWN.
Explanation	A health monitoring method was modified.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · The service has not been found. · The configuration item doesn't exist. · The expected_data_type, expected_data and expected_offset parameters are available only when the monitor type is HTTP or HTTPS. · Invalid json format. · The status is read only. · The tenant name is read only. · The ID can not be modified. · The tenant ID can not be modified. · The type can not be modified. · The method can not be specified when type is not http or https. · The url path can not be specified when type is not http or https. · The monitor port parameter is available only when the monitor type is TCP. · The monitor port exceed limit. · The timeout exceed limit. · You have no privilege to perform this operation.

Delete health monitor

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

Bind health monitor

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

Unbind health monitor

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

NBAC

This section contains NBAC messages.

Create application description

Keyword	CREATE_APPLICATION_DESCIRIPTION_OP
Message text	Created application description “$1”.
Variable fields	$1: Application description information.
Example	Created application description {"application_descriptions":[{"id":"e81094fb-1e83-44ab-80b3-eb98b674646e","source":null,"destination":null,"description_name":"lb","policy_id":"ffffffff-ffff-ffff-0000-000000000002","policy_name":"Deny All","exception_policy_id":"d120d631-923a-4464-9ec4-98754560c2d7","policy_direction":"bi-direction","source_name":null,"destination_name":null,"tenant_id":"822b73c4-5ef7-486d-b54a-887fe04ad520","vrouter_id":"0b1c981d-2f7e-47a0-8a46-dec192a09e20","source_type":"any","destination_type":"any","exception_rules":[{"id":"d1b92d61-08c9-4644-9949-8b0650b4cc61","number":1,"protocol":"IP","action":"redirect","source":"a10b1787-1ca6-4363-b1b6-449a5dcce105","destination":"12d00966-9fbd-4597-8abf-25ac331833c1","direction":"both","policy_id":"d120d631-923a-4464-9ec4-98754560c2d7","policy_name":null,"source_subnet":null,"destination_subnet":null,"ip_version":"4&6","source_port":null,"destination_port":null,"time_range_id":null,"time_range_name":null,"service_chain_id":"8eb88900-8cb0-4fb4-a36c-b2983c38e517","service_chain_name":"lb1"}]}]}.
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. · The application description name already exists. · The tenant ID must be specified. · The source EPG is required. · The destination EPG is required. · The source EPG does not exist. · The destination EPG does not exist. · The source EPG type is required. · The destination EPG type is required. · Invalid source EPG type. · Invalid destination EPG type. · The policy ID does not exist. · The specified policy does not match the policy type. · 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 application description ID already exists. · 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 have no privilege to perform this operation. · You cannot specify a vRouter generated upon PBR service chain creation. · When the action is redirect, make sure the source or destination EPG is not Any or Ungrouped. · Invalid IP version. · Please specify a direction. · Invalid direction. · When the action is redirect, make sure both directions are specified. · When the action is permit or deny, make sure the service chain UUID is not specified. · You cannot specify an EPG automatically generated upon service path creation. · Make sure the exception rule and service path use the same IP version. · Check the vSubnets of the vRouter bound to the source EPG. Make sure none of them contains the vPort IP addresses of any service nodes. · Check the vSubnets of the vRouter bound to the destination EPG. Make sure none of them contains the vPort IP addresses of any service nodes. · Make sure the source EPG and service instances in the service path are bound to different vRouters. · Make sure the destination EPG and service instances in the service path are bound to different vRouters. · When the action is redirect, you cannot specify an external EPG as the source or destination EPG. · Cannot configure IPv4 or IPv4&IPv6 application policies for the vRouter, because the vRouter has been configured with service chains. · The routers of application description and source EPG are different. · The routers of application description and destination EPG are different. · The vRouter bound to the application policy has only one gateway member or external subnet. Make sure the EPGs in the exception rule use the single gateway deployment mode. · The vRouter bound to the application policy has two gateway members or two external subnets. Make sure the EPGs in the exception rule use the primary/backup gateway deployment mode. · Please specify two and only two external subnets for the external EPG. This is required because the EPG uses primary/backup gateway deployment mode and the edge device to the external network in the vRouter for the EPG is the border device. · Please specify one and only one external subnets for the external EPG. This is required because the EPG uses single gateway deployment mode and the edge device to the external network in the vRouter for the EPG is the border device. · The destination EPG cannot be external when the service type is PBRLoadbalance. · The types of the source and destination EPGs cannot both be external. · The external EPG is specified in multiple application policies. Make sure the application policies use the same default action setting. · When the protocol type is IP, ICMP, ICMPv6, or ICMP&ICMPv6, you cannot specify source ports or destination ports. · When the protocol type is TCP or UDP, you must specify at least one source port or one destination port. · The value for the source_port field cannot exceed 255 characters. · The value for the destination_port field cannot exceed 255 characters. · Invalid source ports exist. · Duplicate source ports exist. · Invalid destination ports exist. · Duplicate destination ports exist. · Invalid parameters. · When the source and destination EPGs and source and destination ports are the same, make sure the service path contains only a one-arm service node. · When the source and destination EPGs and source and destination ports are different, make sure the service path does not contain any one-arm service nodes. · When the source and destination EPGs and source and destination ports are the same, make sure the action is redirect. · Without the source and destination ports specified, the exception rule cannot use the same set of source EPG, destination EPG, or protocol setting as an existing exception rule. · Invalid protocol type. · The protocol type does not match the IP version. · The specified service path does not exist. · Check for two rules that have the same source and destination EPGs. If one rule has a greater source port range, its destination port range cannot be smaller than the other rule. · Check for two rules that have swapped source and destination EPGs. If one rule has a greater source port range than the other rule's destination port range, its destination port range cannot be smaller than the other rule's source port range. · Check for two rules that have swapped source and destination EPGs. If one rule has a smaller source port range than the other rule's destination port range, its destination port range cannot be greater than the other rule's source port range. · Check for two rules that have the same source and destination EPGs and the same source port ranges. Make sure neither rule has a greater or smaller destination port range. · Check for two rules that have swapped source and destination EPGs. If one rule has the same range of source ports as the other rule's destination ports, its destination port range cannot be greater or smaller than the other's source port range. · Check for two rules that have the same source and destination EPGs and the same destination port ranges. Make sure neither rule has a greater or smaller source port range. · Check for two rules that have the same source and destination EPGs and the same source port ranges. Make sure they have different destination port ranges. · Check for two rules that have swapped source and destination EPGs. If one rule has the same range of source ports as the other rule's destination ports, make sure it has a different range of destination ports than the other rule's source ports. · When multiple service nodes exist in the service path, make sure all service nodes use the two-arm connection mode. · When the source or destination EPG is an external EPG, the service path can contain only two-arm service nodes.

Update application description

Keyword	UPDATE_APPLICATION_DESCIRIPTION_OP
Message text	Updated application description “$1”.
Variable fields	$1: Application description information.
Example	Updated application description {"application_description":{"id":"1c5f10fa-9b1b-4651-ae71-9df395244a64","source":null,"destination":null,"description_name":"aaab","policy_id":"ffffffff-ffff-ffff-0000-000000000002","policy_name":"Deny All","exception_policy_id":"ac31815e-f95e-4e48-9ed1-e21793cf6033","policy_direction":"bi-direction","source_name":null,"destination_name":null,"tenant_id":"a63b97f1-840b-4c73-afb1-87e7b224bd85","vrouter_id":"7e1ca3ef-3e46-4dfb-86f1-c4839f85de77","source_type":"any","destination_type":"any","exception_rules":[{"id":"84724fdc-a944-45d8-b9c3-52cb83b17782","number":1,"protocol":"IP","action":"permit","source":"4ebe56d7-6f6a-46e4-9ebb-b5aba8689ba7","destination":"46771c89-c629-44cd-81e8-7d44e67750c1","policy_id":"ac31815e-f95e-4e48-9ed1-e21793cf6033","policy_name":null,"source_subnet":null,"destination_subnet":null,"ip_version":null,"source_port":null,"destination_port":null,"time_range_id":null,"time_range_name":null,"service_chain_id":null,"service_chain_name":null}]}}.
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. · The policy cannot be modified. · The policy cannot be edited. · Policy direction cannot be changed. · The tenant cannot be modified. · The vRouter cannot be modified. · The vRouter ID is required. · The source EPG is required. · The destination EPG is required. · The source EPG does not exist. · The destination EPG does not exist. · The source EPG type is required. · An exception rule already exists for the source and destination EPG pair. · The specified application description does not exist. · The policy direction is required. · The policy direction is invalid. · The specified exception policy ID does not exist. · The exception policy has been bound to another application description. · 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 have no privilege to perform this operation. · You cannot specify a vRouter generated upon PBR service chain creation. · When the action is redirect, make sure the source or destination EPG is not Any or Ungrouped. · Invalid IP version. · Invalid direction. · When the action is redirect, make sure both directions are specified. · When the action is permit or deny, make sure the service chain UUID is not specified. · You cannot specify an EPG automatically generated upon service path creation. · Make sure the exception rule and service path use the same IP version. · Check the vSubnets of the vRouter bound to the source EPG. Make sure none of them contains the vPort IP addresses of any service nodes. · Check the vSubnets of the vRouter bound to the destination EPG. Make sure none of them contains the vPort IP addresses of any service nodes. · Make sure the source EPG and service instances in the service path are bound to different vRouters. · Make sure the destination EPG and service instances in the service path are bound to different vRouters. · When the source and destination EPGs are the same, make sure the action is redirect. · When the action is redirect, you cannot specify an external EPG as the source or destination EPG. · When the source and destination EPGs are the same, make sure the service chain contains only a one-arm service node. · When the source and destination EPGs are different, make sure the service chain does not contain any one-arm service nodes. · Cannot configure IPv4 or IPv4&IPv6 application policies for the vRouter, because the vRouter has been configured with service chains. · The routers of application description and source EPG are different. · The routers of application description and destination EPG are different. · The vRouter bound to the application policy has only one gateway member or external subnet. Make sure the EPGs in the exception rule use the single gateway deployment mode. · The vRouter bound to the application policy has two gateway members or two external subnets. Make sure the EPGs in the exception rule use the primary/backup gateway deployment mode. · Please specify two and only two external subnets for the external EPG. This is required because the EPG uses primary/backup gateway deployment mode and the edge device to the external network in the vRouter for the EPG is the border device. · Please specify one and only one external subnets for the external EPG. This is required because the EPG uses single gateway deployment mode and the edge device to the external network in the vRouter for the EPG is the border device. · The destination EPG cannot be external when the service type is PBRLoadbalance. · The types of the source and destination EPGs cannot both be external. · The external EPG is specified in multiple application policies. Make sure the application policies use the same default action setting. · When multiple service nodes exist in the service path, make sure all service nodes use the two-arm connection mode. · When the source or destination EPG is an external EPG, the service path can contain only two-arm service nodes.

Delete application description

Keyword	DELETE_APPLICATION_DESCIRIPTION_OP
Message text	Deleted application description “$1”.
Variable fields	$1: Application description information.
Example	Deleted application description "sourceName: null, destinationName: null, id: 1c5f10fa-9b1b-4651-ae71-9df395244a64, descriptionName: aaab".
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. · 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. · You have no privilege to perform this operation.

Create EPG

Keyword	CREATE_EPG_OP
Message text	Created EPG “$1”.
Variable fields	$1: EPG ID.
Example	Created EPG “1c6d3cf4-d622-4121-b193-bfac63a5e409”.
Explanation	An EPG was created.
Possible failure causes	· The service is disabled. · The controller is not the active leader. · Configuration recovery is in progress. · The tenant name cannot be modified. · The tenant ID is required. · The vRouter ID is required. · The name is required. · The EPG type is required. · Invalid JSON format. · The name cannot exceed 255 characters. · The network ID already exists. · The subnet ID already exist. · The external CIDR already exists. · Invalid external network address. · Duplicated external network addresses exist. · The terminal IP address already exists. · Invalid IP address. · This type of EPG supports only endpoint IP members. · This type of EPG supports only subnet members. · This type of EPG supports only network members. · This type of EPG supports only external CIDR members. · The specified tenant doesn't exist. · The specified vRouter doesn't exist. · The router is not matching tenant. · The specified vSubnet doesn't exist. · The specified vSubnet must have the same tenant ID as the EPG. · The specified vSubnet must have the same vRouter ID as the EPG. · The subnet resource cannot be used because it is used in a PBR service chain. · The specified vNetwork doesn't exist. · The specified vNetwork must have the same tenant ID as the EPG. · The specified vNetwork must have the same vRouter ID as the EPG. · The network resource cannot be used because it is used in a PBR service chain. · A member cannot be added to different EPGs of the same vRouter. An external EPG of one tenant cannot contain members in the EPGs of any other tenant. · The EPG already exists. · Failed to add the EPG. · You have no privilege to perform this operation. · The vRouter bound to the source EPG, destination EPG or third-party service instance does not exist. · You cannot create a vRouter link of the normal, PBR, or NBAC type, because the local or remote vRouter on the link has been bound to both a centralized vNetwork and an IPv6 subnet.. · The vPort ID already exists. · You must specify the VM match rule when the EPG type is terminal and the terminal filter setting is VM. · You must specify the VM filter when the EPG type is terminal and the terminal filter setting is VM. · Please specify the VM string. · The VM string already exists. · The VM filter and match rule settings already exist. · The specified vPort does not exist. · The tenant IDs for the EPG and the specified vPort are different. · The vPort resource cannot be used because it is created by PBR service chain. · The router ID for the EPG and the specified vPort are different. · The VM string is case sensitive and cannot exceed 255 characters. · For the exact match rule, make sure the MAC address format is XX:XX:XX:XX:XX:XX. For any other match rules, make sure the MAC address format is XX, XX:XX, XX:XX:XX, XX:XX:XX:XX, XX:XX:XX:XX:XX, or XX:XX:XX:XX:XX:XX. · The edge device to the external network for the vRouter is a firewall. Do not specify any external subnets for the EPG. · The edge device to the external network for the vRouter is a border device. Please specify external subnets for the EPG. · The vRouter uses a border device as its edge device to the external network and the EPG uses the primary/backup gateway deployment mode. You can specify only two IPv4 external subnets, two IPv6 external subnets, or two IPv4 and two IPv6 external subnets for the EPG. · The vRouter uses a border device as its edge device to the external network and the EPG uses the single gateway deployment mode. You can specify only one IPv4 external subnet, one IPv6 external subnet, or one IPv4 and one IPv6 external subnet for the EPG. · The edge device to the external network for the vRouter is a border device. Please specify external subnets for the EPG. · The specified external subnet does not exist. · The value for flag can only be true (On) or false (Off). · Failed to bind the vRouter to the EPG, because the vRouter has been used by a service chain with two contexts. One context is the external type without external network CIDRs specified, and the other context is the non-external type associated with this vRouter.

Update EPG

Keyword	UPDATE_EPG_OP
Message text	Updated EPG “$1”.
Variable fields	$1: EPG ID.
Example	Updated EPG “1c6d3cf4-d622-4121-b193-bfac63a5e409”.
Explanation	An EPG was modified.
Possible failure causes	· The service is disabled. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid UUID. · The specified resource doesn't exist. · The tenant name cannot be modified. · The tenant ID is required. · The vRouter ID is required. · The name is required. · The EPG type is required. · The tenant ID cannot be modified. · The ID can not be modified. · The router ID can not be modified. · Invalid JSON format. · The name cannot exceed 255 characters. · The network ID already exists. · The subnet ID already exist. · The external CIDR already exists. · Invalid external network address. · Duplicated external network addresses exist. · The terminal IP address already exists. · Invalid IP address. · This type of EPG supports only endpoint IP members. · This type of EPG supports only subnet members. · This type of EPG supports only network members. · This type of EPG supports only external CIDR members. · The specified vSubnet doesn't exist. · The specified vSubnet must have the same tenant ID as the EPG. · The specified vSubnet must have the same vRouter ID as the EPG. · The subnet resource cannot be used because it is used in a PBR service chain. · The specified vNetwork doesn't exist. · The specified vNetwork must have the same tenant ID as the EPG. · The specified vNetwork must have the same vRouter ID as the EPG. · The network resource cannot be used because it is used in a PBR service chain. · A member cannot be added to different EPGs of the same vRouter. An external EPG of one tenant cannot contain members in the EPGs of any other tenant. · Failed to edit the EPG. · You have no privilege to perform this operation. · You cannot edit an EPG automatically generated upon service path creation. · The vPort ID already exists. · You must specify the VM match rule when the EPG type is terminal and the terminal filter setting is VM. · You must specify the VM filter when the EPG type is terminal and the terminal filter setting is VM. · Please specify the VM string. · The VM string already exists. · The VM filter and match rule settings already exist. · The specified vPort does not exist. · The tenant IDs for the EPG and the specified vPort are different. · The vPort resource cannot be used because it is created by PBR service chain. · The router ID for the EPG and the specified vPort are different. · The VM string is case sensitive and cannot exceed 255 characters. · For the exact match rule, make sure the MAC address format is XX:XX:XX:XX:XX:XX. For any other match rules, make sure the MAC address format is XX, XX:XX, XX:XX:XX, XX:XX:XX:XX, XX:XX:XX:XX:XX, or XX:XX:XX:XX:XX:XX. · The edge device to the external network for the vRouter is a firewall. Do not specify any external subnets for the EPG. · The edge device to the external network for the vRouter is a border device. Please specify external subnets for the EPG. · The vRouter uses a border device as its edge device to the external network and the EPG uses the primary/backup gateway deployment mode. You can specify only two IPv4 external subnets, two IPv6 external subnets, or two IPv4 and two IPv6 external subnets for the EPG. · The vRouter uses a border device as its edge device to the external network and the EPG uses the single gateway deployment mode. You can specify only one IPv4 external subnet, one IPv6 external subnet, or one IPv4 and one IPv6 external subnet for the EPG. · The edge device to the external network for the vRouter is a border device. Please specify external subnets for the EPG. · The specified external subnet does not exist. · The value for flag can only be true (On) or false (Off). · Failed to bind the vRouter to the EPG, because the vRouter has been used by a service chain with two contexts. One context is the external type without external network CIDRs specified, and the other context is the non-external type associated with this vRouter.

Delete EPG

Keyword	DELETE_EPG_OP
Message text	Deleted EPG “$1”.
Variable fields	$1: EPG ID.
Example	Deleted EPG “1c6d3cf4-d622-4121-b193-bfac63a5e409”.
Explanation	An EPG was deleted.
Possible failure causes	· The service is disabled. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid UUID. · The specified resource doesn't exist. · Failed to delete the EPG. · The EPG is being used by an application policy. · You have no privilege to perform this operation. · You cannot delete an EPG automatically generated upon service path creation.

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. · You have no privilege to perform this operation. · You have selected interfaces on an inactive device (management IP: management IP).

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. · You have no privilege to perform this operation. · You have selected interfaces on an inactive device (management IP: management IP).

Delete VLAN-VXLAN mapping table

Keyword	DELETE_VLAN-VXLAN_OP
Message text	Deleted VLAN-VXLAN mapping table: $1
Variable fields	$1: VLAN-VXLAN mapping table ID.
Example	Deleted VLAN-VXLAN mapping table: 218b5f2f-e435-4365-a1ab-0eaa03b7fa19
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. · You have no privilege to perform this operation. · You have selected interfaces on an inactive device (management IP: management IP).

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. · You have no privilege to perform this operation. · You have selected interfaces on an inactive device (management IP: management IP).

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. · You have no privilege to perform this operation. · You have selected interfaces on an inactive device (management IP: management IP).

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. · You have no privilege to perform this operation. · You have selected interfaces on an inactive device (management IP: management IP).

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. · You have no privilege to perform this operation. · You cannot bind a VLAN-network mapping table to the device.

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. · You have no privilege to perform this operation. · You cannot bind a VLAN-network mapping table to the device.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation. · A VLAN range has been bound to another vNetwork.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

Create VLAN-network mapping table

Keyword	CREATE_VLAN-VXLAN_OP
Message text	Created VLAN-network mapping table: $1
Variable fields	$1: VLAN-VXLAN mapping table information.
Example	Created VLAN-network mapping table: ID: [218b5f2f-e435-4365-a1ab-0eaa03b7fa19] Name: [table] VLAN-network 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. · You cannot configure both the vNetwork UUID and the VXLAN ID. · You can bind the VLAN-network mapping table only to a device in the fabric for the vNetwork. · The vNetwork does not exist.

Update VLAN-network 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-network mappings: [ VLAN: [2--13], VXLAN: [4--4], Assignment only: [false], Access mode: [VLAN] ]
Explanation	A VLAN-VXLAN mapping table was edited.
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. · 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 reserved VLAN ID conflicts with a VLAN ID of a VLAN-VXLAN mapping. · Unknown internal server error. · You have no privilege to perform this operation.

Delete VLAN-network mapping table

Keyword	DELETE_VLAN-VXLAN_OP
Message text	Deleted VLAN-VXLAN mapping table: $1
Variable fields	$1: VLAN-VXLAN mapping table ID.
Example	Deleted VLAN-network mapping table: 218b5f2f-e435-4365-a1ab-0eaa03b7fa19
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. · Unknown internal server error. · You have no privilege to perform this operation.

Bind ports to VLAN-network mapping table

Keyword	CREATE_PORTBIND_OP
Message text	Bound ports to VLAN-network mapping table: $1
Variable fields	$1: Information about the binding between the ports and the VLAN-VXLAN mapping table.
Example	Bound ports to VLAN-network 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	Bound ports to a VLAN-VXLAN mapping table.
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 device type doesn't match. · Duplicate physical access device IDs. · Unknown internal server error. · Duplicated interfaces exist. · You have no privilege to perform this operation. · The VLAN-VXLAN mapping table has been bound to the device. You cannot bind the VLAN-network mapping table to interfaces on the device. · You can bind the VLAN-network mapping table only to a device in the fabric for the vNetwork.

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 the binding between the ports and the VLAN-VXLAN mapping table.
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	Updated bindings between ports and a VLAN-VXLAN mapping table.
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 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. · You have no privilege to perform this operation. · The VLAN-VXLAN mapping table has been bound to the device. You cannot bind the VLAN-network mapping table to interfaces on the device. · You can bind the VLAN-network mapping table only to a device in the fabric for the vNetwork.

Delete bindings between ports and VLAN-VXLAN mapping table

Keyword	DEL_PORTBIND_OP
Message text	Deleted bindings between ports and VLAN-network mapping table: $1
Variable fields	$1: VLAN-VXLAN mapping table ID.
Example	Deleted bindings between ports and VLAN-network mapping table: e866fcca-6df6-4c4d-8eb7-418ef487732a
Explanation	Deleted bindings between ports and a VLAN-VXLAN mapping table.
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. · You have no privilege to perform this operation.

Create border device group

Keyword	CREATE_GWGROUP_OP
Message text	Created border device group: $1
Variable fields	$1: Gateway group information.
Example	Created border device 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 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 border device group already exists · Invalid name. · Invalid parameter. · Invalid description. · Invalid IP address. · Invalid IP address pool name. · The device type and the border device control mode do not match. · The border device 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 border device group. · The default IP address pool cannot be bound to border device groups. · Border device groups that use the default IP address pool cannot be bound to other IP address pools · Border device 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 border device group's MAC address conflicts with the NE's default MAC address · A border device 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 · Border device 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 · Cannot edit the subnet gateway feature for border device groups on the fabric when asymmetric IRB is enabled. · You have no privilege to perform this operation. · Not enough IP address pools. · The VTEP IP already exists. · The third-party firewall deployment mode is invalid. · The third-party firewall option must be set to Off when the network cloud feature is enabled. · The network position must be border gateway when the border device group is a remote device group. · The connection mode must be IPs from different networks when the border device group is a remote device group. · The connection mode cannot be edited when the border device group is a remote device group. · When the border device group is a remote device group, the value for the firewall service parameter must be IPv4 External Traffic. · Please select a Tenant Carrier FW Internal Network address pool. · You can select only one custom Tenant Carrier FW Internal Network address pool. · The values for the dc_interconnect and dc_connect parameters cannot be both true. · You cannot enable the multicast capabilities, because the network position of the border device group corresponding to the external network is fabric interconnection. · An API request cannot contain the third_fw_security_option parameter together with the third_fw_status or fw_access_mode parameter. · The value for the third-party firewall option is invalid. · The value for the firewall deployment mode is invalid. · Only DC Interconnection is selected for the position of the border device group. You cannot configure remote device group, subnet gateway, third-party firewall deployment mode, or multi-active HA mode. · You can enable DRNI route backup for a border device group only when its HA mode is DRNI. · The value for the DRNI route backup parameter is invalid. · Cannot edit the firewall deployment mode because multicast network has been created. · The VLAN pool name is invalid.

Update border device group

Keyword	UPDATE_GWGROUP_OP
Message text	Updated border device group: $1
Variable fields	$1: Border device group information.
Example	Updated border device 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 border device 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. · The border device group is in use · The border device group doesn't exist · The device type and the border device control mode do not match · The border device 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 border device group · The default IP address pool cannot be bound to border device groups · The VLAN pool does not exist · The VLAN pool has been bound to another border device group · The default VLAN pool cannot be bound to border device groups · Border device groups that use the default IP address pool cannot be bound to other IP address pools · Border device 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 border device group's MAC address conflicts with the NE’s default MAC address · A border device 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 · Border device groups cannot be bound to security external IP address pools · Please make sure none of the selected IP address pools contains allocated IP addresses. · Please make sure none of the selected VLAN pools contains allocated VLANs. · The network element is being deleted or being removed from the gateway group · Cannot modify the work mode of a border device 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 disable the subnet gateway feature for border device groups on the fabric when asymmetric IRB is enabled. · You have no privilege to perform this operation. · Not enough IP address pools. · The VTEP IP already exists. · The third-party firewall option must be set to Off when the network cloud feature is enabled. · Please select a Tenant Carrier FW Internal Network address pool. · You can select only one custom Tenant Carrier FW Internal Network address pool. · Cannot change the third-party firewall deployment mode. The border gateway to which the border device group belongs has been bound to a vRouter. · The is_remote_group field cannot be edited. · You cannot enable the multicast capabilities, because the network position of the border device group corresponding to the external network is fabric interconnection. · An API request cannot contain the third_fw_security_option parameter together with the third_fw_status or fw_access_mode parameter. · In the network cloud scenario, the firewall deployment mode cannot be edited. · The firewall deployment mode for a vRouter-attached border device group cannot be hairpin mode when the IP addresses or subnets in the vRouter-attached external network use different firewall settings. · The border device group is a border gateway member. You cannot use the border device group for DCI, because the tenant already has a border gateway that contains a member used for DCI. · The border device group cannot be used for DCI, because it is used in a border gateway that contains multiple members. · You can enable DRNI route backup for a border device group only when its HA mode is DRNI. · The value for the DRNI route backup parameter is invalid. · Cannot edit the firewall deployment mode because multicast network has been created. · The VLAN pool name is invalid.

Delete border device group

Keyword	DELETE_GWGROUP_OP
Message text	Deleted border device group: $1
Variable fields	$1: Border device ID.
Example	Deleted border device group: 741f1414-d71e-4775-acf9-d68bbb55e803
Explanation	A border device 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 border device group doesn't exist. · The border device group is in use. · The device group is being used by DC connection.

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] } ] IPv6 address range list [ { Start IP: [34:0:0:0:0:0:0:10] End IP: [34:0:0:0:0:0:0:20] Status: [false] Assigned addresses: [[]] } { Start IP: [34:0:0:0:0:0:0:1] End IP: [34:0:0:0:0:0:0:3] Status: [false] Assigned addresses: [[]] } ]
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. · A physical management network IP address pool cannot contain any management IP addresses. · Cannot create a default address pool for security external networks when a FW service resource is bound to a vRouter. · You have no privilege to perform this operation. · The system supports only one multicast address pool and the multicast address pool must be the default IP address pool. · The multicast address pool can contain only multicast addresses, which cannot be permanent group addresses. · The default group or data group cannot be a multicast address in the multicast address pool. · Failed to apply the management IP pool. Please make sure none of the added IP ranges contains network addresses, broadcast addresses, or anycast addresses.

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] } ] IPv6 address range list [ { Start IP: [34:0:0:0:0:0:0:10] End IP: [34:0:0:0:0:0:0:20] Status: [false] Assigned addresses: [[]] } { Start IP: [34:0:0:0:0:0:0:1] End IP: [34:0:0:0:0:0:0:3] Status: [false] Assigned addresses: [[]] } ]
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. · You have no privilege to perform this operation. · The multicast address pool can contain only multicast addresses, which cannot be permanent group addresses. · The default group or data group cannot be a multicast address in the multicast address pool.

Delete IP address pool

Keyword	DELETE_IPPOOL_OP
Message text	Deleted IP address pool: $1
Variable fields	$1: IP address pool ID.
Example	Deleted IP address pool: 4272f686-1faf-4587-b7a2-2f68246666e2
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. · You have no privilege to perform this operation.

Create border device group VLAN range

Keyword	CREATE_GWVLANRANGE_OP
Message text	Created border device group VLAN range: $1
Variable fields	$1: VLAN pool information.
Example	Created border device 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]
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. · The VLAN range cannot contain the VLAN IDs already assigned to cloud private lines. · You have no privilege to perform this operation. · Cannot specify both the range and range_list parameters. · The end VLAN ID must be greater than or equal to the start VLAN ID. · VLAN range conflicts exist.

Update border device group VLAN range

Keyword	UPDATE_GWVLANRANGE_OP
Message text	Updated border device group VLAN range: $1
Variable fields	$1: VLAN pool information.
Example	Updated border device 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 border device group. · The new VLAN range of the vRouter interconnection network VLAN pool must include the original VLAN range of the pool. · The VLAN range cannot contain the VLAN IDs already assigned to cloud private lines. · You have no privilege to perform this operation. · You can use only the range_list parameter to edit VLAN ranges when multiple VLAN ranges exist. · Cannot specify both the range and range_list parameters. · The end VLAN ID must be greater than or equal to the start VLAN ID. · VLAN range conflicts exist.

Delete border device group VLAN range

Keyword	DELETE_GWVLANRANGE_OP
Message text	Deleted border device group VLAN range: $1
Variable fields	$1: VLAN pool ID.
Example	Deleted border device 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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation. · Cannot specify both the range and range_list parameters. · VLAN range conflicts exist. · The VXLAN range contains the reserved VXLAN ID configured for the automation template and the DR system.

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. · You have no privilege to perform this operation. · Cannot specify both the range and range_list parameters. · You can use only the range_list parameter to edit VXLAN ranges when multiple VXLAN ranges exist. · VLAN range conflicts exist.

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. · You have no privilege to perform this operation.

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 IP6: [22:0:0:0:0:0:0:11] 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] openflowSslAccessControlPolicyName:[dcp] 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 border device group doesn't exist. · Physical gateway service devices can be bound only to BIND_PHY type border device groups. · The border device group is already bound to a gateway service device. · Invalid IP address. · The VTEP IP has been used. · 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. · 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. · The VTEP IP of the specified device has already been used by a device on the whitelist. · Cannot specify a VTEP IP address in the underlay address pool. · The VTEP IP already exists. · The VTEP IP cannot belong to the underlay IP range or loopback1 IP range. · The underlay address pool cannot contain existing VTEP IP addresses. · The DCI VTEP IP already exists. · The VTEP IP cannot be the same as the DCI VTEP IP of the peer device in the DC connection. · The DCI VTEP IP cannot be the same as the DCI VTEP IP of the peer device in the DC connection. · Only border device support the DCI VTEP IP configuration. · The DCI VTEP IP cannot be the same as the VTEP IP address of a device. · The VTEP IP cannot be the same as the DCI VTEP IP address of a device. · The management IP address has already been added to a device autodeploy list. · The management IP address has been used. · The management IP address cannot belong to any existing address pools except for the management address pool. · In multi-active mode, you must configure one IPv4 VTEP address or one IPv6 VTEP address, but not both. · You must configure one IPv4 VTEP address or one IPv6 VTEP address, but not both. · You have no privilege to perform this operation. · The certificate-based access control policy name cannot exceed 31 characters. · To configure the certificate-based access control policy name, please first configure the SSL policy name. · The value for the remote device parameter must be false for non-border switching devices. · Remote device group members must be remote devices. · Remote devices cannot be used as service device group members. · Failed to assign IP addresses to devices, because the IP addresses in the primary IP allocation are insufficient. · The specified management IP address is the IP address of a L4-L7 device. Please select another IP address. · You can reserve loopback interface numbers only for access devices and border devices. · The list of reserved loopback interface numbers cannot exceed 255 characters. · Make sure each reserved loopback interface number is an integer in the range of 50 to 1000. · The label can contain up to 64 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 IP6: [22:0:0:0:0:0:0:11] 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] openflowSslAccessControlPolicyName:[dcp] 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 border device group doesn't exist. · Physical gateway service devices can be bound only to BIND_PHY type border device groups. · The border device 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 border device 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 DCI VTEP IP already exists. · Cannot modify the DCI VTEP IP of the device that has a DC connection established. · Cannot remove the device from the device group because the device has a DC connection established. · The DCI VTEP IP cannot be the same as the DCI VTEP IP of the peer device in the DC connection. · Only border device support the DCI VTEP IP configuration. · The DCI VTEP IP cannot be the same as the VTEP IP address of a device. · The VTEP IP cannot be the same as the DCI VTEP IP address of a device. · You must configure one IPv4 VTEP address or one IPv6 VTEP address, but not both · The vtepIP version of group and device are not same. · You have no privilege to perform this operation. · The certificate-based access control policy name cannot exceed 31 characters. · To configure the certificate-based access control policy name, please first configure the SSL policy name. · The is_remote parameter for switching devices cannot be edited. · Remote device group members must be remote devices. · Remote devices cannot be used as service device group members. · Failed to assign IP addresses to devices, because the IP addresses in the primary IP allocation are insufficient. · The reserved loopback interface numbers cannot be editedYou cannot edit the enabling status of VXLAN service preconfiguration for this device type. · You cannot edit the enabling status of VXLAN service preconfiguration on a border device group member used for fabric interconnection. · You cannot edit the enabling status of VXLAN service preconfiguration when the device has QinQ mappings on its interfaces. · You cannot change the state of the VXLAN service preconfiguration feature when the network cloud feature is enabled. · You cannot edit the name of this device. · The label for a physical device cannot be edited.

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 the device has a DC connection established. · You have no privilege to perform this operation. · The main ip pool not enough. · The reserved loopback interface numbers cannot be edited.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · The device does 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. · You have no privilege to perform this operation.

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. · The device does 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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · The virtual network function node doesn't exist. · You have no privilege to perform this operation.

Update VNF device

Keyword	UPDATE_VNF_OP
Message text	Updated VNF device : $1
Variable fields	$1: VNF device information.
Example	Updated VNF device : NE ID: [aa3431ec-08af-4e0d-93a6-b0c01d2ae5f9] NE name: [VFW_0377248511] NE MAC: [3c:8c:40:4e:dd:49] Description: [Reth1] NE type: [VLANSN] Gateway group name: [Reth2] NETCONF username: [admin] NETCONF password: [null] Management IP: [98.0.87.5] Provider type: [VNGFW] NE capability: [FW] 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] Data Path Id:[00:01:74:25:8a:e3:a3:6c] connect interface name:[Reth3] Fabric ID: [null] Gateway: [false] Under deployment: [false] Is Auto Create: [false] ] devSnList: [ ] Region ID:[d284da7f-5393-46e2-903e-f1e42f3fc7e4] Region name:[re...
Explanation	A VNF device was modified.
Possible failure causes	· Invalid license. · The service is disabled. · Netconf session is down. · Invalid NETCONF password. · The virtual network function node doesn't exist. · Configuration recovery is in progress. · The controller is not the active leader. · Failed to update the NETCONF username or password. · Failed to save the configuration of the device. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

Edit BFD settings

Keyword	UPDATE_DEVICE_DEFAULT_BFD_OP
Message text	Edited BFD settings in the switching device default settings: $1 $2
Variable fields	$1: Minimum multihop echo-mode detection interval. $2: Multihop echo-mode detection time multiplier.
Example	Edited BFD settings in the switching device default settings: Min multihop echo-mode detection interval:[400] Multihop detection time multiplier:[40]
Explanation	The default BFD settings were edited.
Possible failure causes	· Invalid license. · The service is disabled. · Invalid JSON format. · Configuration recovery is in progress. · The controller is not the active leader. · You have no privilege to perform this operation. · Unknown internal server error. · The minimum multihop echo-mode detection interval must be 0 or a multiple of 10 in the range of 3 to 10000. · The multihop detection time multiplier must be an integer in the range of 3 to 50. · Southbound devices at the following IP addresses were disconnected: {IP addresses}.

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 border device 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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation. · Cannot enable the network cloud scenario when the third-party firewall deployment mode of the border device group is hairpin or inline.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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 border device 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 border device 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 border device 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 device group that uses the default address pool and default VLAN pool. · A tenant bound to a border device 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. · You have no privilege to perform this operation. · The network function for this resource has been used by a resource that differs from this resource in service type. · The network function for this resource has been used by a resource in a different resource family. · You can specify only one network function for a service resource. · You can specify only an existing custom resource access template.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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 device group. · The vRouter has been used to create a Layer 3 DC interconnection and can be bound to only one single-member border gateway. The device group used as the gateway member must be enabled with the DC interconnection feature. · The vRouter link to which the vRouter belongs is enabled with the firewall feature. You can bind only a single-member border gateway to the vRouter. · The vRouter can be bound to only one border gateway because it has been bound to more than one load balancing service resource. · Unknown internal server error. · Cannot configure a priority for the gateway resource. For more information, see the online help. · The vRouter can be bound to only one border gateway. · You have no privilege to perform this operation. · You cannot bind the vRouter to any other border gateways. The vRouter uses a firewall as the edge device to the external network and has been bound to a border gateway that uses a border device group enabled with third-party firewall deployment. · The vRouter uses firewalls as edge devices and the border gateway contains remote device group members. To bind the border gateway to the vRouter, set the third-party firewall option to On for the remote device group members. · The border gateway specified for the vRouter contains members with the third-party firewall option enabled. This is not allowed, because the external network bound to this vRouter is also bound to vRouters that use border devices as edge devices. · The vRouter has been bound to the same external network and border device as some other vRouters. Please make sure the gateway selected for this vRouter uses the same device groups as those vRouters. · The extranet IP has been used by another gateway resource. · The vRouter has been bound to the same external network and border device as some other vRouters. Please make sure the gateway selected for this vRouter uses the same device groups as those vRouters. · Failed to assign IP addresses to devices attached to the border gateway, because the IP addresses in the primary IP allocation are insufficient. · Check the directly connected external networks and the border interfaces in the border device group bound to this vRouter with the same segment ID. Make sure only one primary IPv4 address exists for the border interface. · The third-party firewall option must be set to Off when the vRouter is bound to an external network with network segmentation enabled. · The firewall deployment mode for a vRouter-attached border device group cannot be hairpin mode when the IP addresses or subnets in the vRouter-attached external network use different firewall settings. · The gateway contains members that enable the third-party firewall option. You cannot bind it to the vRouter, because the vRouter has a different setting for its firewall option than any vRouter-attached external vPorts. · The address pool does not exist or no IPv4 or IPv6 addresses are available in the address pool. · The vRouter is on a vRouter link disabled with the firewall feature. The border gateway for the vRouter must be bound to the same border device group as the remote vRouter in the vRouter link. · Gateway of hairpin firewall deployment cannot be bound to the selected vRouter which is used by multicast network.

Router unbound to gateway

Keyword	UNBIND_ROUTER_GW_OP
Message text	Router unbound to gateway: RouterGatewayConfig [routerId=$1, gatewayIdList=[$2]]
Variable fields	$1: vRouter ID. $2: Gateway ID.
Example	Router unbound to gateway: RouterGatewayConfig [routerId=2b693f0e-70ed-4ef6-ae59-a8fb5272f473, gatewayIdList=[5093467e-158c-4a17-b1b5-710c7bf0da47]]
Explanation	Unbound a gateway from a vRouter.
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. · The router already has service resource. · The gateway has been used by an MSDP peer.

Add vRouter to resource

Keyword	BIND_VROUTER_OP
Message text	Added vRouter $1 to resource $2.
Variable fields	$1: vRouter name. $2: Service resource ID.
Example	Added vRouter route1 to resource aa68bc06-8e30-468d-a805-d4f48952c646.
Explanation	A vRouter was bound to a service resource.
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. · Failed to bind the service resource. The address pool does not exist or no IP addresses are available in the address pool. · Failed to bind the service resource. The VLAN pool does not exist or no VLAN IDs are available in the VLAN pool. · Cannot bind load balancing service resources to the vRouter because the vRouter has been bound to more than one border gateway. · Unknown internal server error. · You have no privilege to perform this operation. · The address pool does not exist or no IPv4 or IPv6 addresses are available in the address pool.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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] Link type: [TRUNK] 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. · You have no privilege to perform this operation. · Invalid link type.

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] Link type: [TRUNK] 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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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: Created device configuration template: ID:[95ef9fd6-e3b5-4238-8215-2e21082772dd] Fabric ID:[7b892fe9-4227-49f0-94ed-f3be16c3d4b2] File path:[null] Name:[11.template] Description:[null] CommandSegment:[null] Role name:[spine] Username:[null] Password:[null] NTP server address:[null] Control protocol template ID:[f6cfecf8-a967-4e75-a900-fa2857a01679] Software ID:[null] Software name:[null] Software version:[null] Patch ID:[null] Patch name:[null] Patch version:[null] Patch size:[null] Aggregation mode:[null] IRF stacking:[true] Border IRF stacking:[false] Enable aggregation:[null] Enable mlag:[false] Mlag mode:[null] DR group ID range:[null] Master spine MAC:[null] BGP RR MAC:[22:22:22:22:22:22] ECMP configure:[null] IS-IS name:[null] IS-IS password:[null] Spine BGP AS Number:[null] Leaf BGP AS number:[null] BGP MD5 password:[null] Border MAC:[null] EVPN control:[null] OSPF ID:[11] OSPF area:[11] IS-IS ID:[null] Underlay IP range:[null] LoopBack1 IP range:[null] Backup server:[null] Access capability:[false] BFD mad:[true] Needwhitelist:[true] CustomizedDeviceInfo:[null]
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 exsit. · 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. · The underlay IP range can be specified only for spine devices. · The underlay IP range cannot contain existing VTEP IPs. · The loopback1 IP range cannot contain existing VTEP IPs. · The underlay IP range overlaps with an existing IP range. · The loopback1 IP range overlaps with an existing IP range. · The underlay IP range overlaps with loopback1 IP range. · The underlay routing protocol can only be OSPF for an aggregation device. · You cannot assign a BGP AS number to an aggregation device. · An aggregation device does not support border IRF stacking. · You cannot configure EVPN for an aggregation device. · BGP RR MAC is not configurable because an aggregation device cannot act as a BGP RR. · You cannot set a BGP MD5 password for an aggregation device. · Border MAC is not configurable because you cannot configure an aggregation device as a border device. · Please specify a NETCONF username and password for the default protocol template. · You have no privilege to perform this operation. · The OSPF area ID is required when the underlay protocol is OSPF. · Invalid OSPF area ID. · The OSPF area ID can be configured only when the underlay protocol is OSPF. · The OSPF area ID in the configuration templates of all devices in a fabric must be the same. · You can set the DR aggregation mode only in a configuration template for leaf and spine nodes. · An access device does not support border IRF stacking. · An access device does not support IRF stacking. · Please do not configure ECMP settings for an access device. · Please do not configure IS-IS settings for an access device. · Please do not configure OSPF settings for an access device. · Please do not configure BGP settings for an access device. · An access device does not support EVPN settings. · An access device does not support a border MAC. · The critical VLAN ID must be an integer in the range of 2 to 4094. · The reserved VXLAN ID must be an integer in the range of 1 to 16777215. · Invalid keepalive link type. · Please specify a keepalive link type. · Make sure the reserved VXLAN is not in any existing VXLAN pool. · Invalid dr group id range. · You can set the DR aggregation mode only in a configuration template for leaf and spine nodes. · Invalid link aggregation mode for DR interfaces. · Please specify the DR group ID range.

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:[95ef9fd6-e3b5-4238-8215-2e21082772dd] Fabric ID:[7b892fe9-4227-49f0-94ed-f3be16c3d4b2] File path:[null] Name:[11.template] Description:[null] CommandSegment:[null] Role name:[spine] Username:[null] Password:[null] NTP server address:[null] Control protocol template ID:[f6cfecf8-a967-4e75-a900-fa2857a01679] Software ID:[null] Software name:[null] Software version:[null] Patch ID:[null] Patch name:[null] Patch version:[null] Patch size:[null] Aggregation mode:[null] IRF stacking:[true] Border IRF stacking:[false] Enable aggregation:[null] Enable mlag:[false] Mlag mode:[null] DR group ID range:[null] Master spine MAC:[null] BGP RR MAC:[22:22:22:22:22:22] ECMP configure:[null] IS-IS name:[null] IS-IS password:[null] Spine BGP AS Number:[null] Leaf BGP AS number:[null] BGP MD5 password:[null] Border MAC:[null] EVPN control:[null] OSPF ID:[11] OSPF area:[11] IS-IS ID:[null] Underlay IP range:[null] LoopBack1 IP range:[null] Backup server:[null] Access capability:[false] BFD mad:[true] Needwhitelist:[true] CustomizedDeviceInfo:[null]
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 field. · 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 configure template doesn't exist. · The import configure template can not modify. · The CIDR is required. · Invalid CIDR. · The underlay IP range overlaps with loopback1 IP range. · Cannot modify the Loopback1 IP range or underlay IP range of the template because the template has been bound to devices. · The underlay IP range cannot contain existing VTEP IPs. · The loopback1 IP range cannot contain existing VTEP IPs. · The underlay IP range overlaps with an existing IP range. · The loopback1 IP range overlaps with an existing IP range. · An aggregation device does not support border IRF stacking. · You cannot configure EVPN for an aggregation device. · BGP RR MAC is not configurable because an aggregation device cannot act as a BGP RR. · You cannot set a BGP MD5 password for an aggregation device. · Border MAC is not configurable because you cannot configure an aggregation device as a border device. · The RR MAC cannot be modified because the corresponding device is active. · Please specify a NETCONF username and password for the default protocol template. · You have no privilege to perform this operation. · An access device does not support border IRF stacking. · An access device does not support IRF stacking. · Please do not configure ECMP settings for an access device. · Please do not configure IS-IS settings for an access device. · Please do not configure OSPF settings for an access device. · Please do not configure BGP settings for an access device. · An access device does not support EVPN settings. · An access device does not support a border MAC. · The critical VLAN ID must be an integer in the range of 2 to 4094. · The reserved VXLAN ID must be an integer in the range of 1 to 16777215. · Invalid keepalive link type. · Please specify a keepalive link type. · Make sure the reserved VXLAN is not in any existing VXLAN pool. · Invalid dr group id range. · You can set the DR aggregation mode only in a configuration template for leaf and spine nodes. · Invalid link aggregation mode for DR interfaces. · Please specify the DR group ID range.

Delete device configuration template

Keyword	DELETE_CONFIGURE_TEMPLATE_OP
Message text	Deleted device configuration template $1.
Variable fields	$1: Device configuration template ID.
Example	Deleted device configuration template 54dfc6cc-5110-4bf8-b23c-b5a84692bf43.
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. · Failed to delete the template. The address pool in the fabric of the template is not released. · You have no privilege to perform this operation. · Delete device configuration.

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.Chinese characters are not supported, and cannot be all-spaces. · The SNMP read community name can contain up to 32 characters. Chinese characters are not supported, and cannot be all-spaces. · The SNMP write community name can contain up to 32 characters. Chinese characters are not supported, and cannot be all-spaces. · 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. · You have no privilege to perform this operation.

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. Chinese characters are not supported, and cannot be all-spaces. · The SNMP read community name can contain up to 32 characters. Chinese characters are not supported, and cannot be all-spaces. · The SNMP write community name can contain up to 32 characters. Chinese characters are not supported, and cannot be all-spaces. · 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. · You have no privilege to perform this operation.

Delete control protocol template

Keyword	DELETE_CONTROL_PROTOCOL_TEMPLATE_OP
Message text	Deleted control protocol template $1.
Variable fields	$1: Control protocol template ID.
Example	Deleted control protocol template d23575f4-aa11-4683-855a-68d9edb95702.
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. · You have no privilege to perform this operation.

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[ Type: [out-of-band] Fabric ID: [d51aa540-40ec-4d68-9abd-623f884cc227] DHCP server settings:[ ID: [902dcff2-fc8a-48fb-91bb-9a99943a4e69] ] VTEP IP pool list: [ VTEP IP pool settings :[ ID: [a943dff1-61b5-4f35-b0de-6ecb007af11b] ] ] Loopback1 pool list: [ ] Management IP pool list :[ Management IP pool settings :[ ID: [73faf202-9225-4e23-b235-38d3ca4bf7cc] ] ] Temp management IP pool list :[ Temp management IP pool settings :[ ID: [e6f7f40b-4b77-4793-bd9b-b59eab103bc8] ] ] Remote management IP pool list :[ Remote management pool settings :[ ID: [c8f024b1-9c07-4f71-ab54-cca7d49b0745] ] ] Remote temp management IP pool list :[ Remote temp management pool settings :[ ID: [65c2e8fc-e830-4b09-9602-b4b94a1060fc] ] ] Remote VTEP IP pool list :[ Remote VTEP IP pool settings :[ ID: [65c2e8fc-e830-4b09-9602-b4b94a1060xc] ] ]
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 default DHCP server does not exist. · An underlay address pool cannot contain loopback0 interface IP addresses of whitelist. · The VTEP IP pool conflicts with the underlay IP range specified in the device configuration template. · The VTEP IP pool conflicts with the loopback1 IP range specified in the device configuration template. · The underlay IP pool conflicts with the underlay IP range specified in the device configuration template. · The underlay IP pool conflicts with the loopback1 IP range specified in the device configuration template. · The IP pool for auto deployment does not exist. · The IP pool for auto deployment has been bound to another fabric. · Invalid IP pool for auto deployment. · An IP pool for auto deployment cannot contain the management IP address of a device. · An IP pool for auto deployment cannot contain the IP address of a managed device. · You can specify only one address pool of each pool type. · The management address pool and the IP pool for auto deployment must be different. · You have no privilege to perform this operation. · You can configure a remote address pool only when the underlay protocol is OSPF. · To configure a remote address pool, you must first configure a remote management IP pool. · To configure a remote address pool, you must first configure a remote IP pool for auto deployment. · To configure a remote address pool, you must first configure a remote VTEP IP pool. · The remote management network address pool and the remote auto deployment address pool must have the same gateway address. · The local and remote management network address pools cannot reside in the same network. · The remote management network address pool and local auto deployment address pool cannot reside in the same network. · The remote auto deployment address pool and local management network address pool cannot reside in the same network. · The local and remote auto deployment address pools cannot reside in the same network. · The specified remote management IP pool has been bound to another fabric. · The specified remote IP pool for auto deployment has been bound to another fabric. · The specified remote VTEP IP pool has been bound to another fabric. · Invalid remote management IP pool. · Invalid remote IP pool for auto deployment. · Make sure the remote auto deployment IP pool contains only one address range. · Invalid remote VTEP IP pool. · The remote IP pool for auto deployment cannot contain IP addresses in the device list. · The remote IP pool for auto deployment cannot contain IP addresses of incorporated devices. · The specified remote management IP pool does not exist. · he specified remote management IP pool does not exist. · The specified remote IP pool for auto deployment does not exist. · The specified remote VTEP IP pool does not exist. · The local management IP pool and the remote management IP pool must be different. · The local management IP pool and the remote IP pool for auto deployment must be different. · The local IP pool for auto deployment and the remote management IP pool must be different. · The local IP pool for auto deployment and the remote IP pool for auto deployment must be different. · The remote management IP pool and the remote IP pool for auto deployment must be different. · The local VTEP IP pool and the remote VTEP IP pool must be different. · The local management IP pool cannot contain any management IP addresses in the remote device list. · The remote management IP pool cannot contain any management IP addresses in the local device list.

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: [b6ff4eb8-6a12-45f3-891e-3e77be157df8] DHCP server settings:[ ID: [ad5c2c16-9861-4d8d-9ad4-60e54d19abc4 ] ] ]
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. · Cannot modify the management address pool because IP addresses in the management address pool have been used. · Cannot delete or edit the IP pool for auto deployment. It is being used. · The IP pool for auto deployment does not exist. · The IP pool for auto deployment has been bound to another fabric. · Cannot edit the address ranges in an IP pool for auto deployment. · Cannot edit the gateway address in an IP pool for auto deployment. · Invalid IP pool for auto deployment. · An IP pool for auto deployment cannot contain the management IP address of a device. · An IP pool for auto deployment cannot contain the IP address of a managed device. · You can specify only one address pool of each pool type. · The management address pool and the IP pool for auto deployment must be different. · The IP pool for auto deployment cannot be edited. · You have no privilege to perform this operation. · The local management IP pool and the remote management IP pool must be different. · The local management IP pool and the remote IP pool for auto deployment must be different. · The local IP pool for auto deployment and the remote management IP pool must be different. · The local IP pool for auto deployment and the remote IP pool for auto deployment must be different. · The remote management IP pool and the remote IP pool for auto deployment must be different. · The local VTEP IP pool and the remote VTEP IP pool must be different. · The remote management IP pool cannot be edited. · The remote IP pool for auto deployment cannot be edited. · The remote VTEP IP pool cannot be edited. · Please specify a remote IP pool for auto deployment. · Please specify a remote management IP pool. · Please specify a remote VTEP IP pool. · You cannot edit the IP pool for auto deployment, because the fabric contains devices that are being deployed automatically. · You cannot edit the remote IP pool for auto deployment, because the fabric contains devices that are being deployed automatically.

Delete deploy resource pool

Keyword	DELETE_DEPLOY_RESSOURCEPOOL_OP
Message text	Deleted deployment resource pool $1.
Variable fields	$1: Deployment resource pool ID.
Example	Deleted deployment resource pool cc06ca44-5b72-49c2-af36-5834970b8ab4.
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. · Cannot delete the management address pool because IP addresses in the management address pool have been used. · Cannot delete or edit the IP pool for auto deployment. It is being used. · You have no privilege to perform this operation. · The fabric contains devices that are being deployed automatically.

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. · The specified user does not exist. · The current user is not authorized to perform this operation. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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: Auto backup: [false] TftpServerAddress: [98.0.31.100] Frequency: [1] Time: [12:00] Week: [1] Date: [0] MaxCfgNum: [1]
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 have no privilege to perform this operation.

Update Security global setting

Keyword	UPDATE_SECURITY_GLOBAL_CONFIG_OP
Message text	Updated security global config: $1
Variable fields	$1: Global security settings.
Example	Updated security global config: FipToIfSubAddrEnable: [false] FipUseNatServerEnable: [true]
Explanation	Updated global security settings.
Possible failure causes	· Invalid JSON format. · Configuration recovery is in progress. · The controller is not the active leader. · Unknown internal server error. · You have no privilege to perform this operation. · Cannot disable NAT server mappings for floating IPs.

Create manual backup

Keyword	CREATE_MANUAL_BACKUP_OP
Message text	Created manual backup:$1
Variable fields	$1: UUIDs of the device to back up.
Example	Create Manual Backup: deviceIdList:[76f15eab-b5db-4184-b92f-3b64427b0387]
Explanation	A manual backup was performed on devices.
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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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 should 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. · You have no privilege to perform this operation.

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 uploading, can not operate it. · The software is upgrading, can not operate it. · You have no privilege to perform this operation.

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 uploading, can not operate it. · The software is upgrading, can not operate it. · You have no privilege to perform this operation.

Upgrade softeware

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 uploading, can not operate it. · You have no privilege to perform this operation.

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. · The device with the specified serial number has been incorporated and cannot be used as a replacement device. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation. · The selected gateway cannot be used as the default gateway, because one of its gateway members is placed only for DCI. · A vRouter in the tenant has been bound to a Layer 3 DCI enabled with the firewall feature. In this scenario, you cannot bind the selected border gateway to the tenant, because one of the gateway members is placed only for DCI.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation. · The gateway has been used by an MSDP peer.

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 border device groups. · The gateway members must belong to the same type of border device groups. · The border device groups to which the gateway members belong must have the same fw_for_external parameter value. · The border device groups to which the gateway members belong must have the same fw_only_for_external parameter value. · The border device groups to which the gateway members belong must have the same fw_for_internal parameter value. · The border device 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 border device group is not enabled with EVPN. · The fabrics of the border device 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. · You have no privilege to perform this operation.

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 border device groups. · The gateway members must belong to the same type of border device groups. · The border device groups to which the gateway members belong must have the same fw_for_external parameter value. · The border device groups to which the gateway members belong must have the same fw_only_for_external parameter value. · The border device groups to which the gateway members belong must have the same fw_for_internal parameter value. · The border device 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 border device group is not enabled with EVPN. · The fabrics of the border device 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 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. · You have no privilege to perform this operation. · You cannot bind the vRouter to a border gateway that uses a border device group only for DC Interconnection. · Only DC Interconnection is selected for the position of the gateway members. You cannot configure gateway sharing or method to deploy basic external connectivity settings for the border gateway.

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 by an external network. · The gateway is being used by a tenant. · The gateway is being used by a vRouter. · The gateway has gateway members. · You have no privilege to perform this operation.

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 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 border device group doesn't exist. · The default VLAN pool does not exist. · The device 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 border device 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. · You have no privilege to perform this operation. · When a member of a border gateway is bound to a remote device group, the border gateway can be bound to only one member. · The VPN instance is already used.

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 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 group doesn't exist. · The default VLAN pool does not exist. · The device 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 border device 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. · You have no privilege to perform this operation. · The VPN instance is already used.

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. · You have no privilege to perform this operation.

Create device information

Keyword	CREATE_DEVICE_INFORMATION_OP
Message text	Created device information: $1
Variable fields	$1: Device information.
Example	Created device information: ID:[deb8c576-9871-4224-b3fb-1d43988cf01c] Serial number:[spine] Index number:[spine] Role name:[spine] Management IP:[2.1.1.1] Gateway:[false] Fabric ID:[d51aa540-40ec-4d68-9abd-623f884cc227] Fabric name:[fabric] MLAG:[false] Remote:[false]
Explanation	A device 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. · An aggregation device cannot provide gateway services. · Failed to add device to the device list. It is already managed by the controller. · The specified Management IP has been used by another whitelist. · The Management IP on the specified whitelist has been used by a managed device. · The management IP address has been used. · Please first configure an IP pool for auto deployment. · The management IP address cannot belong to any existing address pools except for the management address pool. · The management IP address cannot belong to the IP pool for auto deployment. · You have no privilege to perform this operation. · An access device cannot provide gateway services. · You cannot enable DRNI on an access device. Please set the mlag parameter to false. · Only leaf border devices can be configured as remote devices. · The management IP address cannot belong to the IP pool for remote auto deployment. · The management IP address of local device cannot belong to the remote management IP pool. · The management IP address of remote device cannot belong to the local management IP pool. · Downlink interfaces cannot exceed 255 characters. · Invalid downlink interfaces. · When the service network type of the fabric is VLAN, the device type must be underlay and the device role must be spine or leaf for automatic onboarding. · When the service network type for a fabric is VLAN, you cannot configure the IRF fabric settings. · When the service network type of the fabric is VXLAN, not support the device type is underlay and the device role id leaf for automatic onboarding.

Update device information

Keyword	UPDATE_DEVICE_INFORMATION_OP
Message text	Updated device information: $1
Variable fields	$1: Device information.
Example	Updated device information: ID:[ d5c1d35e-62f5-4259-a905-98183d9fd065] Serial number:[210235A2C4H187000881] Role name:[leaf] Sysname:[68-95] Management IP:[12.12.12.1] NetworkEntity ID:[ab.cdef.1234.5678.9abc.00] Loopback IP:[68.0.0.15] Gateway:[false]
Explanation	A device was edited.
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. · An aggregation device cannot provide gateway services. · Failed to add device to the device list. It is already managed by the controller. · The specified Management IP has been used by another whitelist. · The Management IP on the specified whitelist has been used by a managed device. · The management IP address has been used. · Please first configure an IP pool for auto deployment. · The management IP address cannot belong to any existing address pools except for the management address pool. · The management IP address cannot belong to the IP pool for auto deployment. · You have no privilege to perform this operation. · An access device cannot provide gateway services. · You cannot enable DRNI on an access device. Please set the mlag parameter to false. · Only leaf border devices can be configured as remote devices. · The device type field in the device list cannot be edited, because the device list has been used by a edge link. · The remote device field in the device list cannot be edited, because the device list has been used by a link. · The management IP address cannot belong to the IP pool for remote auto deployment. · The management IP address of local device cannot belong to the remote management IP pool. · The management IP address of remote device cannot belong to the local management IP pool. · You cannot edit the NETCONF username. The device has been locked. · Downlink interfaces cannot exceed 255 characters. · Invalid downlink interfaces. · When the service network type of the fabric is VLAN, the device type must be underlay and the device role must be spine or leaf for automatic onboarding. · When the service network type for a fabric is VLAN, you cannot configure the IRF fabric settings. · When the service network type of the fabric is VXLAN, not support the device type is underlay and the device role id leaf for automatic onboarding.

Delete device information

Keyword	DELETE_DEVICE_INFORMATION_OP
Message text	Deleted device information: $1
Variable fields	$1: Device ID.
Example	Deleted device information: d5c1d35e-62f5-4259-a905-98183d9fd065
Explanation	A device 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. · You have no privilege to perform this operation.

Create link information

Keyword	CREATE_LINK_INFORMATION_OP
Message text	Created link information: $1
Variable fields	$1: Link information.
Example	Created link information [ ID=3b55e8b8-45eb-4513-8e53-d67a810bba51, Serial number 4A=210235A1TXH165000106, Index number 4A=localSpine, Port 4A=xge1/0/1, Serial number 4B=210235A1TYH178000044, Index number 4B=remoteLeaf, Port 4B=xge1/0/5, Usage=edge_link, Fabric ID=97e73e1a-aac6-4583-be3f-20edfb1b666f, Fabric name=null ]
Explanation	A link was created.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · Unknown internal server error. · You have no privilege to perform this operation. · Please specify a link type. · Invalid link type.. · To create a edge link, you must specify a spine device and a leaf device. · To create a edge link, you must configure the leaf device as a border device. · A local device cannot be specified in a edge link. · A remote device cannot be specified in a local link.

Update link information

Keyword	UPDATE_LINK_INFORMATION_OP
Message text	Update link information: $1
Variable fields	$1: Link information.
Example	Updated link information [ ID=3b55e8b8-45eb-4513-8e53-d67a810bba51, Serial number 4A=210235A1TXH165000106, Index number 4A=localSpine, Port4A=xge1/0/1, Serial number 4B=210235A1TYH178000044, Index number 4B=remoteLeaf, Port 4B=xge1/0/5, Usage=edge_link, Fabric ID=97e73e1a-aac6-4583-be3f-20edfb1b666f, Fabric name=null ]
Explanation	A link was edited.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · Unknown internal server error. · You have no privilege to perform this operation. · Please specify a link type. · Invalid link type. · To create a edge link, you must specify a spine device and a leaf device. · To create a edge link, you must configure the leaf device as a border device. · A local device cannot be specified in a edge link. · A remote device cannot be specified in a local link.

Delete link information

Keyword	DELETE_LINK_INFORMATION_OP
Message text	Deleted link information: $1
Variable fields	$1: Link ID.
Example	Deleted link information: ID:[3b55e8b8-45eb-4513-8e53-d67a810bba51] Index number4A:[localSpine Index number4B:[remoteLeaf]
Explanation	A link was deleted.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · Unknown internal server error. · You have no privilege to perform this operation.

Import device list

Keyword	IMPORT_DEVICE_LIST_OP
Message text	Bulk added devices to the device list: $1
Variable fields	$1: Device list information.
Example	Bulk added devices to the device list: Added devices: 0, Added links: 0, Added MLAGs: 0 Ignored devices: 2, Ignored links: 1, Ignored MLAGs: 1
Explanation	Imported multiple devices to the device list.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · Unknown internal server error. · You have no privilege to perform this operation. · Please specify a link type. · Invalid link type. · To create a edge link, you must specify a spine device and a leaf device. · To create a edge link, you must configure the leaf device as a border device. · A local device cannot be specified in a edge link. · A remote device cannot be specified in a local link. · Only leaf border devices can be configured as remote devices. · The management IP address cannot belong to the IP pool for remote auto deploymen. · The management IP address of local device cannot belong to the remote management IP pool. · The management IP address of remote device cannot belong to the local management IP pool. · Downlink interfaces cannot exceed 255 characters. · Invalid downlink interfaces. · When the service network type of the fabric is VLAN, the device type must be underlay and the device role must be spine or leaf for automatic onboarding. · When the service network type for a fabric is VLAN, you cannot configure the IRF fabric settings. · When the service network type of the fabric is VXLAN, not support the device type is underlay and the device role id leaf for automatic onboarding.

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. · Only unmanaged assets can be deleted. · You have no privilege to perform this operation.

Synchronization device bridgeMac and serialNumber info

Keyword	START_DATA_SYNCHRONIZATION_OP
Message text	Started to synchronize physical NE bridgeMac and serialNumber info:SynchronizationCache [reversRefresh=$1]
Variable fields	$1: Whether the controller is enabled to synchronize bridge MAC and serial number information from devices.
Example	Started to synchronize physical NE bridgeMac and serialNumber info: SynchronizationCache [reversRefresh=false]
Explanation	The controller synchronized bridge MAC and serial number information from devices.
Possible failure causes	· A device synchronization task is in progress. Cannot create device synchronization tasks. · Unknown internal server error. · Failed to obtain information about the IRF fabric. · You have no privilege to perform this operation.

Create DC connection

Keyword	CREATE_DC_CONNECTION_OP
Message text	Created DC connection: $1
Variable fields	$1: Data center interconnect information.
Example	Created DC connection: ID:[17dce0ce-4e46-425d-9aeb-fe39e8933b04] localDeviceId:[5512a2df-51ad-46d9-82d8-f7676ceab2af] peerDeviceInfo: [ deviceName: a dciVtepIp: 2.2.2.4 asNumber: 24 ]
Explanation	A data center interconnect 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. · Invalid parameter. · Invalid name. · The local device does not exist. · DC interconnect must be enabled for the device group to which the local devices belong. · Invalid AS number of the peer device info. · Invalid device name of the peer device info. · The DC connection already exists. · The DC connection name already exists. · The DCI VTEP IP of the peer device cannot be the same as the VTEP IP of any device of the local controller. · The DCI VTEP IP of the local device is required. · A DC connection already exists between the local and remote devices. · The DCI VTEP IP of the peer device cannot be the same as the DCI VTEP IP of any device of the local controller. · The AS number of the fabric to which the local device belongs cannot be empty. · The AS number of the fabric to which the local device belongs cannot be the same as the AS number of the fabric to which the peer device belongs. · Invalid IP address. · You have no privilege to perform this operation. · The source and destination devices must use the same version of VTEP IP addresses to establish a DCI connection.

Update DC connection

Keyword	UPDATE_DC_CONNECTION_OP
Message text	Updated DC connection: $1
Variable fields	$1: Data center interconnect information.
Example	Updated DC connection: ID:[23f1465b-574d-4a51-8ff5-59041ae19467] Name:[aa] localDeviceId:[5512a2df-51ad-46d9-82d8-f7676ceab2af] peerDeviceInfo: [ deviceName: a dciVtepIp: 1.1.1.8 asNumber: 8 ]
Explanation	A data center interconnect 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. · Invalid name. · Invalid parameter. · There are non-modifiable fields in this parameter. · The DC connection does not exist. · The DC connection name already exists. · You have no privilege to perform this operation.

Delete DC connection

Keyword	DELETE_DC_CONNECTION_OP
Message text	Deleted DC connection: $1.
Variable fields	$1: Data center interconnect ID.
Example	Deleted DC connection:23f1465b-574d-4a51-8ff5-59041ae19467.
Explanation	A data center interconnect 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. · Invalid parameter. · Unknown internal server error. · The DC connection does not exist. · You have no privilege to perform this operation.

Create replacement task

Keyword	CREATE_REPLACE_TASK_OP
Message text	Created replacement task: $1
Variable fields	$1: Device 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 device 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. · You have no privilege to perform this operation.

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 device 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. · You have no privilege to perform this operation.

Create BGP neighbor

Keyword	CREATE_BGP_NEIGHBOR_OP
Message text	Created BGP neighbor: $1.
Variable fields	$1: BGP neighbor information.
Example	Created BGP neighbor: ID: [c962169b-1a71-449c-8407-a36e938916ec] Router ID: [94e28779-629f-4159-a7c6-261a57241658] Tenant ID: [28ebfffc-865f-4784-a7d5-33938daf8db1] BGP neighbor description:[] IP version:[4] Local AS number:[30] BGP neighbor name:[tt] Peer AS number:[31] Peer IP address:[31.1.1.1] Source IP: [[30.0.0.1]] Suppress:[false] Cloud region name: region
Explanation	A BGP neighbor was configured.
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 parameter. · Unknown internal server error. · A name is required for the BGP instance. · A tenant ID is required. · A router ID is required for the BGP instance. · Specify either a source IP address or an external subnet ID. · A local AS number is required. · Invalid local AS number. · Invalid IP version. · The IP address of the BGP peer must be the same version as the source IP address. · An AS number is required for the BGP peer. · The AS number of the BGP peer is invalid. · The BGP peer UUID already exists. · An IP address is required for the BGP peer. · The source IP address or external subnet ID is invalid. · A name is required. · A UUID is required for the BGP peer. · An external subnet ID is required. · An IP version is required. · The IP address of the BGP peer is invalid. · An IP address is required for the BGP peer. · An AS number is required for the BGP peer. · The specified BGP peer has already been bound to the vRouter. · The specified subnet is not an external subnet. · The connection type of the external network must be Directly Connected. · The external subnet type must be VLAN. · The specified external subnet has not been bound to a vRouter. · The vRouter to which the external subnet is bound is different from the vRouter specified by the router_id parameter. · When the HA mode is multi-active, you must specify two different source IP addresses for the BGP neighbor. · You have no privilege to perform this operation. · When the Network Cloud feature is disabled, you cannot create BGP peers. · Southbound devices at the following IP addresses were disconnected: {IP addresses}. · Up to 255 characters, case sensitive.

Update BGP neighbor

Keyword	UPDATE_BGP_NEIGHBOR_OP
Message text	Updated BGP neighbor: $1.
Variable fields	$1: BGP neighbor information.
Example	Updated BGP neighbor: ID: [c962169b-1a71-449c-8407-a36e938916ec] Router ID: [94e28779-629f-4159-a7c6-261a57241658] Tenant ID: [28ebfffc-865f-4784-a7d5-33938daf8db1] BGP neighbor description:[] IP version:[4] Local AS number:[30] BGP neighbor name:[tt] Peer AS number:[31] Peer IP address:[31.1.1.1] Source IP: [[30.0.0.1]] Suppress:[false] Cloud region name: region
Explanation	A BGP neighbor was edited.
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 parameter. · Unknown internal server error. · The BGP peer UUID does not exist. · The BGP peer UUID cannot be modified. · The tenant ID cannot be modified. · The router ID of the BGP instance cannot be modified. · The local AS number cannot be modified. · The IP version cannot be modified. · The IP address of the BGP peer cannot be modified. · The AS number of the BGP peer cannot be modified. · You have no privilege to perform this operation. · When the Network Cloud feature is disabled, you cannot edit BGP peers. · Southbound devices at the following IP addresses were disconnected: {IP addresses}. · You cannot edit or delete the cloud region name. · Up to 255 characters, case sensitive.

Delete BGP neighbor

Keyword	DELETE_BGP_NEIGHBOR_OP
Message text	Deleted BGP neighbor: $1.
Variable fields	$1: BGP neighbor ID.
Example	Deleted BGP neighbor: c962169b-1a71-449c-8407-a36e938916ec
Explanation	A BGP neighbor 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. · Invalid parameter. · Unknown internal server error. · The BGP peer UUID does not exist. · You have no privilege to perform this operation. · Southbound devices at the following IP addresses were disconnected: {IP addresses}.

Create border interface

Keyword	CREATE_PHYSICAL_NETWORK_INTERFACE_OP
Message text	Created physical network interface: $1.
Variable fields	$1: External network egress information.
Example	Created physical network interface: ID: [586682ac-8f9b-4016-a03e-f879213102cd] Device ID: [e62b5d9a-b9e3-44d5-9e1e-9f53d350a7f8] Port name: [GigabitEthernet1/0/1] Segments : [ Segment ID : [100] IP ranges: [26.0.0.0/24]
Explanation	An external network egress 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 parameter. · Unknown internal server error. · The border interface name already exists. · The border interface name is required. · The NE doesn't exist. · The border interface device is not gateway. · The border interface port name already exists. · The border interface segments is required. · The border interface port name is required. · Invalid border interface name. · Invalid border interface port name. · Invalid border interface name. · You have no privilege to perform this operation. · When the Network Cloud feature is disabled, you cannot create border interfaces. · Check the directly connected external networks and the border interfaces in the border device group bound to this vRouter with the same segment ID. Make sure only one primary IPv4 address exists for the border interface. · Southbound devices at the following IP addresses were disconnected: {IP addresses}.

Update border interface

Keyword	UPDATE_PHYSICAL_NETWORK_INTERFACE_OP
Message text	Updated physical network interface: $1.
Variable fields	$1: External network egress information.
Example	ID: [586682ac-8f9b-4016-a03e-f879213102cd] Device ID: [e62b5d9a-b9e3-44d5-9e1e-9f53d350a7f8] Port name: [GigabitEthernet1/0/1] Segments : [ Segment ID : [100] IP ranges: [26.0.0.0/24]
Explanation	An external network egress was edited.
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 parameter. · Unknown internal server error. · You have no privilege to perform this operation. · When the Network Cloud feature is disabled, you cannot edit border interfaces. · Check the directly connected external networks and the border interfaces in the border device group bound to this vRouter with the same segment ID. Make sure only one primary IPv4 address exists for the border interface. · Southbound devices at the following IP addresses were disconnected: {IP addresses}.

Delete border interface

Keyword	DELETE_PHYSICAL_NETWORK_INTERFACE_OP
Message text	Deleted physical network interface: $1.
Variable fields	$1: External network egress ID.
Example	Deleted physical network interface: 23f1465b-574d-4a51-8ff5-59041ae19467.
Explanation	An external network egress 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. · Invalid parameter. · Unknown internal server error. · You have no privilege to perform this operation. · Southbound devices at the following IP addresses were disconnected: {IP addresses}.

Created cloud private line

Keyword	CREATE_CLOUD_PL_OP
Message text	Created cloud private line:$1
Variable fields	$1: Cloud private line information.
Example	Created cloud private line: UUID:[a31eb312-012e-4ecf-826c-76c69772cbba] Router_ID:[a8c10620-460d-4351-b8f8-98983fa65abe] Cloud private line CIDRs:[[33.23.23.0/24]] IP_address:[23.23.23.23] Subnet mask:[255.255.255.0] Gateway_IP:[23.23.23.2] VLAN_ID:90
Explanation	A cloud private line 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 parameter. · The virtual router doesn't exist. · The VLAN ID is already in a VLAN pool. · Invalid IP address. · Invalid subnet mask. · The VLAN ID is invalid or out of range. · The VLAN ID is already assigned to a cloud private line. · The local network has already been bound to the vRouter. · The CIDR already exists. · The local IP address has already been bound to the vRouter. · Invalid subnet. · You have no privilege to perform this operation.

Updated cloud private line

Keyword	UPDATE_CLOUD_PL_OP
Message text	Updated cloud private line:$1
Variable fields	$1: Cloud private line information.
Example	Updated cloud private line: UUID:[a31eb312-012e-4ecf-826c-76c69772cbba] Router_ID:[a8c10620-460d-4351-b8f8-98983fa65abe] Cloud private line CIDRs:[[33.23.23.0/24]] IP_address:[23.23.23.23] Subnet mask:[255.255.255.0] Gateway_IP:[23.23.23.2] VLAN_ID:90
Explanation	A cloud private line was edited.
Possible failure causes	· Invalid JSON format. · Configuration recovery is in progress. · The controller is not the active leader. · Unknown internal server error. · Invalid parameter. · The virtual router doesn't exist. · The VLAN ID is already in a VLAN pool. · Invalid IP address. · Invalid subnet mask. · The VLAN ID is invalid or out of range. · The VLAN ID is already assigned to a cloud private line. · The local network has already been bound to the vRouter. · The CIDR already exists. · The local IP address has already been bound to the vRouter. · Invalid subnet. · You have no privilege to perform this operation.

Deleted cloud private line

Keyword	DELETE_CLOUD_PL_OP
Message text	Deleted cloud private line:$1.
Variable fields	$1: Cloud private line ID.
Example	Deleted cloud private line:a31eb312-012e-4ecf-826c-76c69772cbba
Explanation	A cloud private line 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. · Invalid parameter. · Unknown internal server error. · The cloud private line does not exist. · You have no privilege to perform this operation.

Create multicast

Keyword	CREATE_MULTICAST_OP
Message text	Created multicast: $1.
Variable fields	$1: Layer 3 multicast network information.
Example	Created multicast:LogicMulticastConfig [id=68dafdfe-b2eb-4be5-9554-9b184d30dec1, name=test2, rpAddress=2.3.5.4, vrouterId=636d12f7-700a-4c3f-a079-706a54b1b346, mdtConfig=MdtConfig [defaultGroup=null, defaultGroupAuto=false, dataGroup=null, dataGroupAuto=false, autoDataNUm=null, sourcePort=null, dataDelay=null, aclId=null, sourceActive=false], 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], multicastResources=[], externalVpn=false, external_network_id=d3d2ae8a-9081-4177-9091-8a15ba6ad8bg, ext_segment_uuid=646d12f7-700a-4c3f-a079-706a54b1b346]
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 multicast already exist. · The name is required. · Invalid name. · The router is required. · The VSM service is not available. · The specified router does not exist. · The vrouter does not enable multicast. · The multicast with the name is already exist. · The multicast with the vrouter is already exist. · Invalid IP address. · The RP address is required. · Invalid pim protocol. · Invalid default group. · The default group is null, but data group not null. · Invalid data group. · The switchover delay is out of range. · The ACL doesn't exist. · The mdt ACL is must advanced ACL. · The SSM policy cannot has with PIM-SM protocol. · The hello interval is out of range. · The hello holdtime is out of range. · The join or prune interval is out of range. · The join or prune holdtime is out of range. · The propagation delay is out of range. · The override interval is out of range. · The SSM policy ACL must be basic ACL. · The neighbor policy ACL is must basic ACL. · The join policy ACL is must basic ACL. · The other querier present time is out of range. · The SSM mapping doesn't exist. · The default group and data group is overlap. · The IGMP version is invalid. · The SSM mapping is not null when IGMP version is V3. · 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 default group or data group conflicts with before or multicast pool. · The multicast address pool does not exist. · The multicast address pool does not have enough addresses for allocation. · Cannot specify the default group when auto default group allocation is enabled. · Invalid number of data groups to be automatically allocated. · Cannot bind the selected vRouter to the multicast network, because the external network bound to the selected vRouter is also bound to a vRouter used in a multicast network for external services. · To enable external services, please first bind the reveiver vRouter to an external network. · The other querier present time must be greater than the general query interval. · The general query interval must be greater than the max response time. · Cannot set the max response time when the IGMP version is v1. · Cannot set the last member query interval when the IGMP version is v1. · Cannot set the other querier present time when the IGMP version is v1. · The general query interval must be less than the default value for the other querier present time (255). · The other querier present time must be greater than the default general query interval (125). · The general query interval must be greater than the default max response time (10). · The max response time must be less than the default general query interval (125). · You have no privilege to perform this operation. · The PIM-SM domain border cannot be enabled when external services are disabled. · The value for the PIM-SM domain border field can only be true or false. · You must disable the publishing multicast source information by default option if auto default group assignment is disabled and no default group is specified. · Please select a vRouter that is not bound to a segmented external network. · When external services are enabled, you must select a vRouter that is not bound to a segmented external network. · Make sure the specified network segment has been bound to the vRouter. · You cannot specify an network segment, because network segmentation is not enabled for the external network bound to the specified vRouter. · You must specify an network segment when network segmentation has been enabled for the external network bound to the specified vRouter and the external network service has been enabled. · You cannot select an network segment when the external network service is disabled. · The specified network segment has already been bound to another Layer 3 multicast network. · You cannot edit the ID of the network segment. · The source vRouter of a multicast source and the receiver vRouter of the multicast source's Layer 3 multicast network must be bound to the same network segment. · You cannot edit the ID of the external network. · You cannot select an external network when the external network service is disabled. · Please select an external network. · Cannot add multicast network when the firewall deployment mode of gateway is hairpin. · The external network has been bound to a vRouter through a vPort, and a Layer 3 multicast network cannot be added to the external network.

Update multicast

Keyword	UPDATE_MULTICAST_OP
Message text	Updated multicast: $1.
Variable fields	$1: Layer 3 multicast network information.
Example	Updated multicast:LogicMulticastConfig [id=68dafdfe-b2eb-4be5-9554-9b184d30dec1, name=test2, rpAddress=2.3.5.4, vrouterId=636d12f7-700a-4c3f-a079-706a54b1b346, mdtConfig=MdtConfig [defaultGroup=null, defaultGroupAuto=false, dataGroup=null, dataGroupAuto=false, autoDataNUm=null, sourcePort=null, dataDelay=null, aclId=null, sourceActive=false], 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], multicastResources=[], externalVpn=false]
Explanation	A Layer 3 multicast network was edited.
Possible failure causes	· Configuration recovery is in progress. · Invalid JSON format. · The controller is not the active leader. · Unknown internal server error. · The multicast id is required when put. · The multicast name cannot be modified. · The vrouter id cannot be modified. · Invalid IP address. · The RP address is required. · Invalid pim protocol. · Invalid default group. · The default group is null, but data group not null. · Invalid data group. · The switchover delay is out of range. · The ACL doesn't exist. · The mdt ACL is must advanced ACL. · The SSM policy cannot has with PIM-SM protocol. · The hello interval is out of range. · The hello holdtime is out of range. · The join or prune interval is out of range. · The join or prune holdtime is out of range. · The propagation delay is out of range. · The override interval is out of range. · The SSM policy ACL must be basic ACL. · The neighbor policy ACL is must basic ACL. · The join policy ACL is must basic ACL. · The other querier present time is out of range. · The SSM mapping doesn't exist. · The default group and data group is overlap. · The multicast doesn't exist. · The multicast name cannot be modified. · Invalid source port. · Please specify a default group and a source port. · If you do not specify a data group, you must leave the switchover delay and multicast policy empty. · Cannot edit the PIM protocol because the vRouter bound to the Layer 3 multicast network has been bound to a multicast source of another Layer 3 multicast network. · The IGMP version is invalid. · The SSM mapping is not null when IGMP version is V3. · 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 default group or data group conflicts with before or multicast pool. · The multicast address pool does not exist. · The multicast address pool does not have enough addresses for allocation. · Cannot specify the default group when auto default group allocation is enabled. · Invalid number of data groups to be automatically allocated. · Cannot edit the status of external services for an existing Layer 3 multicast network. · Cannot remove the distributed RP from the Layer 3 multicast network. The vRouter bound to the Layer 3 multicast network has been used by an MSDP peer. · The other querier present time must be greater than the general query interval. · The general query interval must be greater than the max response time. · Cannot set the max response time when the IGMP version is v1. · Cannot set the last member query interval when the IGMP version is v1. · Cannot set the other querier present time when the IGMP version is v1. · The general query interval must be less than the default value for the other querier present time (255). · The other querier present time must be greater than the default general query interval (125). · The general query interval must be greater than the default max response time (10). · The max response time must be less than the default general query interval (125). · The SSM Mapping field must be empty if PIM-SM is used. · The IGMP version must be v3 if PIM-SM is used. · You have no privilege to perform this operation. · The PIM-SM domain border cannot be enabled when external services are disabled. · The value for the PIM-SM domain border field can only be true or false. · The Layer 3 multicast network and its multicast network interfaces must run the same PIM protocol. · You must disable the publishing multicast source information by default option if auto default group assignment is disabled and no default group is specified.

Delete multicast

Keyword	DELETE_MULTICAST_OP
Message text	Deleted multicast: $1.
Variable fields	$1: UUID of the Layer 3 multicast network.
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. · The specified replacement task does not exist. · Invalid parameter. · The vRouter is used by multicast source. · Cannot delete the Layer 3 multicast network. The vRouter bound to the Layer 3 multicast network has been used by an MSDP peer. · You have no privilege to perform this operation.

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. · The ACL with the same name already exists. · Invalid description. · You have no privilege to perform this operation. · The specified ACL does not exist.

Delete ACL

Keyword	DELETE_ACL_OP
Message text	Deleted ACL: $1.
Variable fields	$1: ACL UUID.
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. · You have no privilege to perform this operation.

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 for the specified UUID doesn’t exist. · The ACL with the same name already exists. · The ACL IDs of all rules are not same. · Invalid source IP address. · Invalid destination IP address. · The specified ACL rule already exists. · The specified ACL rule conflicts with existed rule. · The ACL rule list parameter contains duplicated rules. · The ACL rule number must be in the range of 1 to 1000. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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	An 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. · The SSM Mapping name already exists. · Invalid description. · You have no privilege to perform this operation.

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	An SSM mapping 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. · You have no privilege to perform this operation.

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	An 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 group ip. · The SSM Mapping rule already exists. · The SSM Mapping rule list parameter contains duplicated rules. · You have no privilege to perform this operation.

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: 178d9370-884a-4538-b75b-51b0a42ffaf5.
Explanation	An 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. · You have no privilege to perform this operation.

Create multicast source

Keyword	CREATE_MULTICAST_SOURCE_OP
Message text	Created multicast source:$1
Variable fields	$1: Multicast source information.
Example	Created multicast source: MulticastSourceConfig [id=eef1860b-b0b9-467e-a37a-64ee75a8ee83, sourceIp=115.3.2.0/24, groupIp=225.3.3.0/24, vrouterId=e94e8c6a-be65-4008-9ce9-07622a82043c, externalVpn=true, multicastId=567d5dad-ab7d-4adb-94a5-32c917324170, external_network_id=d3d2ae8a-9081-4177-9091-8a15ba6ad8bg, ext_segment_uuid=646d12f7-700a-4c3f-a079-706a54b1b346]
Explanation	A multicast source was created.
Possible failure causes	· Invalid JSON format. · Invalid UUID:parameter. · Invalid parameter. · The multicast source cannot be bound to the same vRouter as its Layer 3 multicast network. · The vRouter does not enable multicast. · The multicast source already exists. · Please specify the multicast source address. · Invalid multicast source address. · The multicast doesn't exist. · Invalid IP address. · Please select a vRouter that has been bound to a Layer 3 multicast network for the multicast source. · Invalid multicast group address. · The specified vRouter does not exist. · The device netconf session doesn't up. · Internal server error. · Please perform the operation on the active leader. · Configuration recovery is in progress. · Unknown internal server error. · The VSM service is disabled. · The service is disabled. · Please specify the multicast group address. · Operation failed. The PIM protocol configured for the Layer 3 multicast network of the multicast source is different from that configured for the Layer 3 multicast network to which the selected vRouter is bound. · The multicast source addresses in a Layer 3 multicast network can overlap but they must be different. · The multicast group addresses in a Layer 3 multicast network can't overlap. · The multicast source's vRouter is required. · Cannot edit the PIM protocol because the vRouter bound to the Layer 3 multicast network has been bound to a multicast source of another Layer 3 multicast network. · The multicast's id is required. · The multicast source address is required. · The multicast group address is required. · The Layer 3 multicast network and its multicast sources cannot be both used for external network service. · The multicast network or the multicast source is configured to provide external services. Please bind them to the same vRouter or bind them to different vRouters that are bound to the same external network. · The multicast network or the multicast source is configured to provide external services. Please bind them to the same vRouter. · To enable external services, please first bind the source vRouter to an external network. · You have no privilege to perform this operation. · Please select a vRouter that is not bound to a segmented external network. · The Layer 3 multicast network and its multicast sources cannot be both used for external network service. · The multicast network or the multicast source is configured to provide external services. Please bind them to the same vRouter or bind them to different vRouters that are bound to the same external network. · The multicast network or the multicast source is configured to provide external services. Please bind them to the same vRouter. · To enable external services, please first bind the source vRouter to an external network. · Make sure the specified network segment has been bound to the vRouter. · You cannot specify an network segment, because network segmentation is not enabled for the external network bound to the specified vRouter. · You must specify an network segment when network segmentation has been enabled for the external network bound to the specified vRouter and the external network service has been enabled. · You cannot select an network segment when the external network service is disabled. · You cannot select an network segment when the external network service is disabled. · You cannot edit the ID of the network segment. · The source vRouter of a multicast source and the receiver vRouter of the multicast source's Layer 3 multicast network must be bound to the same network segment. · You cannot edit the ID of the external network. · Please select an external network.

Delete multicast source

Keyword	DELETE_MULTICAST_SOURCE_OP
Message text	Deleted multicast source: $1.
Variable fields	$1: Multicast source UUID.
Example	Deleted multicast source:a563fa7f-19ef-4fba-908f-37a486027f8b
Explanation	A multicast source 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. · You have no privilege to perform this operation.

Create MSDP peer

Keyword	CREATE_MULTICAST_MSDP_OP
Message text	Created MSDP peer: $1
Variable fields	$1: MSDP peer information.
Example	Created MSDP peer:MulticastMsdpConfig [ id:[d3d2ae8a-9081-4177-9091-8a15ba6ad8fc] vRouterId:[636d12f7-700a-4c3f-a079-706a54b1b346] name:[msdp] peerAddress:[115.1.1.1] retryInterval:[1] keepAlive:[2] holdTime:[3] msdpAuthType:[simple_password] simplePassword:[xxxx] external_network_id: [d3d2ae8a-9081-4177-9091-8a15ba6ad8bg] ext_segment_uuid: [646d12f7-700a-4c3f-a079-706a54b1b346]]
Explanation	An MSDP peer was created.
Possible failure causes	· Invalid JSON format. · Configuration recovery is in progress. · Invalid UUID:parameter. · Invalid parameter. · Invalid MSDP peer name. · The MSDP peer already exists. · The vRouter has been bound to another MSDP peer. · A MSDP peer already exists with the specified name. · Please specify the IP address of the MSDP peer. · The MSDP peer hold time must be less than the MSDP session keepalive interval. · Please specify both the MSDP peer hold time and the MSDP keepalive interval. · The MSDP connection retry interval must be in the range of 1 to 60 seconds. · The MSDP peer hold time must be in the range of 1 to 65535 seconds. · The MSDP session keepalive interval must be in the range of 1 to 21845 seconds. · Invalid authentication mode for MSDP. · Invalid password. · Please assign an IP address to the loopback interface. · The device and the vRouter must be associated with the same VDS. · The MSDP peer does not exist. · The Layer 3 multicast network with the external network enabled does not exist. · Please specify a distributed RP for the Layer 3 multicast network bound to the specified vRouter. · You have no privilege to perform this operation. · The MSDP session keepalive interval must be in the range of 1 to 21845 seconds. · The network segment is already in use. · Make sure the specified network segment has been bound to the vRouter. · You cannot specify an network segment, because network segmentation is not enabled for the external network bound to the specified vRouter. · Please select an external network. · You must specify an network segment when network segmentation has been enabled for the external network bound to the specified vRouter. · Please select a gateway, an external network, or both. · You cannot select the gateway for the MSDP peer, because the gateway uses the same border device group as the gateway of an existing MSDP peer. · The Layer 3 multicast network with external network disabled does not exist. · The specified border gateway does not exist. · The border gateway is not bound to the selected vRouter. · You cannot select both a border gateway and a segmented external network for the MSDP peer. · Failed to create the MSDP peer, because the external network has been bound to a vRouter with a firewall specified as the edge device.

Update MSDP peer

Keyword	UPDATE_MULTICAST_MSDP_OP
Message text	Updated MSDP peer: $1.
Variable fields	$1: MSDP peer information.
Example	Updated MSDP peer:MulticastMsdpConfig [ id:[d3d2ae8a-9081-4177-9091-8a15ba6ad8fc] vRouterId:[636d12f7-700a-4c3f-a079-706a54b1b346] name:[msdp] peerAddress:[115.1.1.1] retryInterval:[1] keepAlive:[2] holdTime:[3] msdpAuthType:[simple_password] simplePassword:[xxxx]]
Explanation	An MSDP peer was edited.
Possible failure causes	· Configuration recovery is in progress. · Invalid license. · The controller is not the active leader. · Unknown internal server error. · Invalid parameter. · Invalid MSDP peer name. · A MSDP peer already exists with the specified name. · The MSDP with the vrouter already exist. · Please specify the IP address of the MSDP peer. · The MSDP connection retry interval must be in the range of 1 to 60 seconds. · The MSDP peer hold time must be in the range of 1 to 65535 seconds. · The MSDP session keepalive interval must be in the range of 1 to 21845 seconds. · The MSDP peer hold time must be less than the MSDP session keepalive interval. · Please specify both the MSDP peer hold time and the MSDP keepalive interval. · Invalid authentication mode for MSDP. · Invalid password. · Please assign an IP address to the loopback interface. · The device and the vRouter must be associated with the same VDS. · The MSDP does not exist. · There are non-modifiable fields in this parameter. · You have no privilege to perform this operation. · The MSDP session keepalive interval must be in the range of 1 to 21845 seconds.

Delete MSDP peer

Keyword	DELETE_MULTICAST_MSDP_OP
Message text	Deleted MSDP peer: $1.
Variable fields	$1: UUID of the MSDP peer.
Example	Deleted MSDP peer: 0b532731-429c-4ae0-bf01-43c314777017
Explanation	An MSDP peer 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. · You have no privilege to perform this operation.

Create BUM multicast replication profile

Keyword	CREATE_MULTICAST_BUM_OP
Message text	Created BUM multicast replication profile: $1
Variable fields	$1: BUM multicast replication profile information.
Example	Created BUM multicast replication profile: MulticastBumConfig [name=dd, id=b413566b-0a6c-4399-ba66-dd7541ef030b, vnetworkId=f89acc82-c8b4-4980-b970-b3f7efb8fdc6, groupIpAuto=false, groupIp=234.2.2.2]
Explanation	A BUM multicast replication profile was created.
Possible failure causes	· Invalid JSON format. · The controller is not the active leader. · Unknown internal server error. · Invalid parameter. · Configuration recovery is in progress. · A BUM multicast replication profile already exists with the specified name. · The BUM multicast replication profile already exists. · The vNetwork has already been bound to a BUM multicast replication profile. · The specified network does not exist. · Please specify a vNetwork. · Please specify the name of a BUM multicast replication profile. · The vNetwork cannot be an external network. · The multicast address pool does not have enough addresses for allocation. · Cannot specify the group address when auto group address allocation is enabled. · Please specify a multicast group that is not in the multicast address pool. · Invalid multicast group address. · Please specify the multicast group address. · You have no privilege to perform this operation.

Update BUM multicast replication profile

Keyword	UPDATE_MULTICAST_BUM_OP
Message text	Updated BUM multicast replication profile: $1.
Variable fields	$1: BUM multicast replication profile information.
Example	Updated BUM multicast replication profile: MulticastBumConfig [name=dd, id=b413566b-0a6c-4399-ba66-dd7541ef030b, vnetworkId=f89acc82-c8b4-4980-b970-b3f7efb8fdc6, groupIpAuto=false, groupIp=234.2.2.2]
Explanation	A BUM multicast replication profile was edited.
Possible failure causes	· Configuration recovery is in progress. · Invalid license. · The controller is not the active leader. · Unknown internal server error. · Invalid parameter. · Invalid JSON format. · Cannot edit the name of the BUM multicast replication profile. · The vNetwork cannot be an external network. · Please specify the ID of the BUM multicast replication profile. · Cannot edit the ID of the vNetwork. · The specified network does not exist. · The BUM multicast replication profile does not exist. · The multicast address pool does not have enough addresses for allocation. · Cannot specify the group address when auto group address allocation is enabled. · Please specify a multicast group that is not in the multicast address pool. · Invalid multicast group address. · Please specify the multicast group address. · You have no privilege to perform this operation.

Delete BUM multicast replication profile

Keyword	DELETE_MULTICAST_BUM_OP
Message text	Deleted BUM multicast replication profile: $1.
Variable fields	$1: UUID of the BUM multicast replication profile.
Example	Deleted BUM multicast replication profile: 0b532731-429c-4ae0-bf01-43c314777017
Explanation	A BUM multicast replication profile 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 BUM multicast replication profile does not exist. · You have no privilege to perform this operation.

Create interface-specific multicast network

Keyword	CREATE_INTERFACE_MULTICAST_OP
Message text	Created interface-specific multicast network: $1
Variable fields	$1: Interface-specific multicast network information.
Example	Created interface-specific multicast network: InterfaceMulticastConfig{id=9a44bd22-4934-4841-bfd4-fbfa453c5b1c, name='11', multicastId='43882183-4b5d-46a2-bda3-a97b50ad480a', belongerNetworkId='f4afb793-3fa2-4dbb-9477-faf3ddf2de8c', pimTemplateConfig=PimTemplateConfig [protocol=PIM-SM, helloInterval=22, helloHoldtime=22, joinPruneInterval=21, joinPruneHoldtime=22, lanDelay=22, overrideInterval=22, 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	An interface-specific multicast network was created.
Possible failure causes	· Invalid JSON format. · Configuration recovery is in progress. · Invalid UUID:parameter. · Invalid parameter. · The hello interval is out of range. · The hello holdtime is out of range. · The join or prune interval is out of range. · The join or prune holdtime is out of range. · The propagation delay is out of range. · The override interval is out of range. · The neighbor policy ACL must be basic ACL. · The join policy ACL must be basic ACL. · The IGMP version is invalid. · 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 interface-specific multicast network already exists. · Invalid interface-specific multicast network name. · An interface-specific multicast network already exists with the specified name. · Invalid multicast network ID. · Cannot configure an interface-specific multicast network in the Layer 3 multicast network.The Layer 3 multicast network has been configured to provide external services. · Invalid vNetwork ID. · The VSM service is not available. · The vNetwork does not exist. · Cannot configure an interface-specific multicast network with external vNetWork. · Please enable multicast capabilities for the vNetwork. · The vNetwork has been bound to another interface-specific multicast network. · Please specify a vNetwork that is bound to the same vRouter with the interface-specific multicast network. · Please set the PIM protocol to PIM-SM. · Please leave the SSM multicast group range empty. · Please leave the SSM mapping empty. · The join or prune interval must be less than the joined or pruned state holdtime. · The joined or pruned state hold time must be greater than the default join or prune interval (60). · The join or prune interval must be less than the default joined or pruned state hold time (210). · Cannot set the max response time when the IGMP version is v1. · Cannot set the last member query interval when the IGMP version is v1. · Cannot set the other querier present time when the IGMP version is v1. · The other querier present time must be greater than the general query interval. · The other querier present time must be greater than the default general query interval (125). · The general query interval must be less than the default value for the other querier present time (255). · The general query interval must be greater than the max response time. · The max response time must be less than the default general query interval (125). · The general query interval must be greater than the default max response time (10). · The Layer 3 multicast network does not exist. · You have no privilege to perform this operation. · The IGMP version must be v3 if PIM-SM is used. · The Layer 3 multicast network and its multicast network interfaces must run the same PIM protocol.

Update interface-specific multicast network

Keyword	UPDATE_INTERFACE_MULTICAST_OP
Message text	Updated interface-specific multicast network: $1.
Variable fields	$1: Interface-specific multicast network information.
Example	Updated interface-specific multicast network: InterfaceMulticastConfig{id=9a44bd22-4934-4841-bfd4-fbfa453c5b1c, name='11', multicastId='43882183-4b5d-46a2-bda3-a97b50ad480a', belongerNetworkId='f4afb793-3fa2-4dbb-9477-faf3ddf2de8c', pimTemplateConfig=PimTemplateConfig [protocol=PIM-SM, helloInterval=33, helloHoldtime=22, joinPruneInterval=21, joinPruneHoldtime=22, lanDelay=22, overrideInterval=22, 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	An interface-specific multicast network was edited.
Possible failure causes	· Configuration recovery is in progress. · Invalid license. · The controller is not the active leader. · Unknown internal server error. · Invalid parameter. · The hello interval is out of range. · The hello holdtime is out of range. · The join or prune interval is out of range. · The join or prune holdtime is out of range. · The propagation delay is out of range. · The override interval is out of range. · The neighbor policy ACL must be basic ACL. · The join policy ACL must be basic ACL. · The IGMP version is invalid. · 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. · Please set the PIM protocol to PIM-SM. · Please leave the SSM multicast group range empty. · Please leave the SSM mapping empty. · The join or prune interval must be less than the joined or pruned state holdtime. · The joined or pruned state hold time must be greater than the default join or prune interval (60). · The join or prune interval must be less than the default joined or pruned state hold time (210). · Cannot set the max response time when the IGMP version is v1. · Cannot set the last member query interval when the IGMP version is v1. · Cannot set the other querier present time when the IGMP version is v1. · The other querier present time must be greater than the general query interval. · The other querier present time must be greater than the default general query interval (125). · The general query interval must be less than the default value for the other querier present time (255). · The general query interval must be greater than the max response time. · The max response time must be less than the default general query interval (125). · The general query interval must be greater than the default max response time (10). · Cannot edit the ID of a Layer 3 multicast network. · Cannot edit the ID of a vNetwork. · Cannot edit the name of an interface-specific multicast network. · Please specify the ID of the interface-specific multicast network. · You have no privilege to perform this operation. · The IGMP version must be v3 if PIM-SM is used. · The Layer 3 multicast network and its multicast network interfaces must run the same PIM protocol.

Delete interface-specific multicast network

Keyword	DELETE_INTERFACE_MULTICAST_OP
Message text	Deleted interface-specific multicast network: $1.
Variable fields	$1: UUID of the interface-specific multicast network.
Example	Deleted interface-specific multicast network: 9a44bd22-4934-4841-bfd4-fbfa453c5b1c
Explanation	An interface-specific 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. · You have no privilege to perform this operation.

Create PIM template

Keyword	CREATE_PIM_TEMPLATE_OP
Message text	Created PIM template: $1.
Variable fields	$1: PIM template information.
Example	Created PIM template: PimTemplate [id=0eff3238-7210-468f-bdae-032a17b23758, name=PimTest, pimTemplateConfig=PimTemplateConfig [protocol=PIM-SM, helloInterval=5, helloHoldtime=5, joinPruneInterval=4, joinPruneHoldtime=5, lanDelay=5, overrideInterval=5, passive=false, ssmPolicy=null]].
Explanation	A PIM template 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 PIM template name. · A PIM template already exists with the specified name. · Invalid PIM passive mode. · Invalid PIM protocol. · The hello interval is out of range. · The hello holdtime is out of range. · The join or prune interval is out of range. · The join or prune holdtime is out of range. · The propagation delay is out of range. · The override interval is out of range. · The join or prune interval must be less than the joined or pruned state holdtime. · The joined or pruned state hold time must be greater than the default join or prune interval (60). · The join or prune interval must be less than the default joined or pruned state hold time (210). · You have no privilege to perform this operation.

Update PIM template

Keyword	UPDATE_PIM_TEMPLATE_OP
Message text	Updated PIM template: $1.
Variable fields	$1: PIM template information.
Example	Updated PIM template:PimTemplate [id=0eff3238-7210-468f-bdae-032a17b23758, name=PimTest, pimTemplateConfig=PimTemplateConfig [protocol=PIM-SM, helloInterval=5, helloHoldtime=5, joinPruneInterval=4, joinPruneHoldtime=5, lanDelay=6, overrideInterval=5, passive=false, ssmPolicy=null]].
Explanation	A PIM template was edited.
Possible failure causes	· Configuration recovery is in progress. · Invalid JSON format. · The controller is not the active leader. · Unknown internal server error. · The PIM template does not exist. · Please specify the ID of the PIM template. · Cannot edit the name of the PIM template. · Invalid PIM passive mode. · Invalid PIM protocol. · The hello interval is out of range. · The hello holdtime is out of range. · The join or prune interval is out of range. · The join or prune holdtime is out of range. · The propagation delay is out of range. · The override interval is out of range. · The join or prune interval must be less than the joined or pruned state holdtime. · The joined or pruned state hold time must be greater than the default join or prune interval (60). · The join or prune interval must be less than the default joined or pruned state hold time (210). · You have no privilege to perform this operation.

Delete PIM template

Keyword	DELETE_PIM_TEMPLATE_OP
Message text	Deleted PIM template: $1.
Variable fields	$1: PIM template information.
Example	Deleted PIM template:0eff3238-7210-468f-bdae-032a17b23758.
Explanation	A PIM template was deleted.
Possible failure causes	· Configuration recovery is in progress. · Invalid license. · The controller is not the active leader. · Unknown internal server error. · You have no privilege to perform this operation.

Create IGMP template

Keyword	CREATE_IGMP_TEMPLATE_OP
Message text	Created IGMP template: $1.
Variable fields	$1: IGMP template information.
Example	Created IGMP template: IgmpTemplate [id=3007347f-d41a-4726-ac29-530109877156, name=igmp_template, igmpTemplateConfig=IgmpTemplateConfig [version=V2, robustCount=11, queryInterval=22, maxResponseTime=11, lastMemberQueryInterval=23, otherQuerierPresent=44, ssmMappingId=null]]
Explanation	An IGMP template was created.
Possible failure causes	· Configuration recovery is in progress · Invalid JSON format. · The controller is not the active leade. · Unknown internal server error. · Invalid name. · The name is required. · The IGMP version is invalid. · An IGMP template already exists with the specified name. · The other querier present time must be greater than the general query interval. · The general query interval must be greater than the max response time. · Cannot set the max response time when the IGMP version is v1. · Cannot set the last member query interval when the IGMP version is v1. · Cannot set the other querier present time when the IGMP version is v1. · 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 general query interval must be less than the default value for the other querier present time (255). · The other querier present time must be greater than the default general query interval (125). · The general query interval must be greater than the default max response time (10). · The max response time must be less than the default general query interval (125). · You have no privilege to perform this operation.

Update IGMP template

Keyword	UPDATE_IGMP_TEMPLATE_OP
Message text	Updated IGMP template: $1.
Variable fields	$1: IGMP template information.
Example	Updated IGMP template: IgmpTemplate [id=3007347f-d41a-4726-ac29-530109877156, name=igmp_template, igmpTemplateConfig=IgmpTemplateConfig [version=V2, robustCount=11, queryInterval=22, maxResponseTime=11, lastMemberQueryInterval=23, otherQuerierPresent=44, ssmMappingId=null]]
Explanation	An IGMP template was edited.
Possible failure causes	· Configuration recovery is in progress. · Invalid JSON format. · The controller is not the active leader. · Unknown internal server error. · The IGMP template does not exist. · Please specify the ID of the IGMP template. · Cannot edit the name of the IGMP template. · The IGMP version is invalid. · The other querier present time must be greater than the general query interval. · The general query interval must be greater than the max response time. · Cannot set the max response time when the IGMP version is v1. · Cannot set the last member query interval when the IGMP version is v1. · Cannot set the other querier present time when the IGMP version is v1. · 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 general query interval must be less than the default value for the other querier present time (255). · The other querier present time must be greater than the default general query interval (125). · The general query interval must be greater than the default max response time (10). · The max response time must be less than the default general query interval (125). · You have no privilege to perform this operation.

Delete IGMP template

Keyword	DELETE_IGMP_TEMPLATE_OP
Message text	Deleted IGMP template: $1.
Variable fields	$1: UUID of the IGMP template.
Example	Deleted IGMP template: 349f858b-4b34-470c-b5af-e98de3ff71ff.
Explanation	An IGMP template was deleted.
Possible failure causes	· Configuration recovery is in progress. · Invalid license. · The controller is not the active leader. · Unknown internal server error. · You have no privilege to perform this operation.

Create DR group

Keyword	CREATE_DR_GROUP_OP
Message text	Created a DR group: $1
Variable fields	$1: DR group information.
Example	Created a DR group: Id:f471887b-6831-4119-92d4-4aa5c2102685, drnidevice1:d480fe8f-42ba-46cd-bff8-39a3393bc159, drnidevice2:3230fc37-1dd5-4f0f-a576-8bc4a6876c4b, numberrange:3-69
Explanation	A DR group was created.
Possible failure causes	· The device is already a member of a DR system. · The specified device does not exist. · DR group ID range error. · The controller is not the active leader. · Configuration recovery is in progress. · Unknown system error. · Invalid JSON format. · The member devices of the DR system must have the same device type. · The member devices of the DR system must belong to the same fabric. · You have no privilege to perform this operation. · The DR group ID range cannot exceed 255 characters.

Delete DR group

Keyword	DELETE_DR_GROUP_OP
Message text	Deleted a DR group: $1
Variable fields	$1: DR group UUID.
Example	Deleted a DR group: f471887b-6831-4119-92d4-4aa5c2102685
Explanation	A DR group was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown system error. · The DR group ID range is in use. · You have no privilege to perform this operation.

Start fine-grained data synchronization on physical device

Keyword	START_FINE_GRAINED_DATA_SYNCHRONIZATION_OP
Message text	Started fine-grained data synchronization on physical device: $1
Variable fields	$1: UUID of the physical device.
Example	Started fine-grained data synchronization on physical device: 28424135-36f5-4dde-ad2e-29580411de8d
Explanation	Started fine-grained data synchronization on a physical device.
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 device does not support this function. · The device is being deleted or being removed from the gateway group. · The system is performing data synchronization or configuration auditing for the device. · You have no privilege to perform this operation. · Invalid JSON format.

Create DR System

Keyword	CREATE_MLAG_GROUP_OP
Message text	Created a DR system: “$1”
Variable fields	$1: DR system information.
Example	Created a DR system: { "mlag_groups": [{ "name": "mlag", "join_type": "USER_CREATE", "fabric_id": "04332242-9754-4826-8ff9-f276d3b83943", "escape_vlan_id": 852, "mlag_mode": "dynamic", "drni_type": "has_peer_link", "member_list": [{ "device_id": "e304b697-3c26-463a-a362-8bd23fa47073" }, { "device_id": "0c203b4c-b13b-4582-b4ce-91c863a2abaa" }], "keep_alive_link_type": "direct_link" }] }
Explanation	A DR system was created.
Possible failure causes	· Invalid JSON format. · The controller is not the active leader. · Configuration recovery is in progress. · You have no privilege to perform this operation. · Unknown internal server error. · The DR system name already exists. · The DR system name cannot be empty. · To use a directly connected link as the keepalive link, you must set up directly connected links between the DR member devices to act as the IPL and the keepalive link. · To use a management link as the keepalive link, make sure an IPL tunnel exists between the DR member devices. · The DR system name cannot exceed 255 characters. · The DR system description cannot exceed 255 characters. · The device ID is not specified. · The device does not exist. · The device does not belong to the fabric. · The device ID is exist in DR system. · The value of join_type must be USER_CREATE or AUTO_ONLINE. · The vtep pool of deploy resource pool is not existed. · Invalid ID. · The DR system ID already exists. · The DR system does not exist. · Failed to assign IP addresses from the physical VTEP network address pool. · Failed to check the availability of the highest tunnel ID. · Failed to establish an NETCONF connection between the controller and the device. · The DR member devices must have the same device role and device type. · The DR member devices must be leaf access devices, leaf border devices, or spine border devices. · The DR member devices must belong to the same border device group. · To establish a DR system, make sure both devices are in Active state. · Invalid critical VLAN ID. · Please specify a scene. · Invalid scene. · Please specify the link aggregation mode for DR interfaces. · Invalid link aggregation mode for DR interfaces. · Do not specify a DR address pool for automatic device deployment. · You must specify a DR address pool for manual device deployment. · The specified DR address pool does not exist. · The DR address pool has been used for automatic deployment. · The DR member devices must have the same deployment mode. · Please specify a keepalive link type. · Invalid keepalive link type. · Keep alive link type must be management when drni type is no peer link. · Please specify an underlay protocol. · The underlay protocol must be OSPF, IS-IS, or BGP. · You must select the underlay protocol used on the fabric. · Please specify an OSPF ID. · Please specify an OSPF area. · Invalid OSPF area ID. · You must enter the OSPF ID configured in the automation template. · The OSPF ID must be in the range of 1 to 65536. · You must select the OSPF area configured in the automation template. · Please specify an IS-IS ID. · You must enter the IS-IS ID configured in the automation template. · The IS-IS ID must be in the range of 1 to 65536. · Please specify a BGP instance. · Invalid BGP instance. · Please specify a DR group ID range. · Failed to obtain the highest tunnel ID. · The highest tunnel ID is in use. · Please first configure a critical VLAN ID in the automation template. · Please specify a reserved VXLAN ID. · The reserved VXLAN ID must be an integer in the range of 1 to 16777215. · Make sure the reserved VXLAN is not in any existing VXLAN pool. · Please first configure a reserved VXLAN ID in the automation template. · The fabric ID is required. · The specified fabric doesn't exist. · Failed to obtain the EVPN global MAC address. · The VXLAN range contains the reserved VXLAN on the DR system. · The reserved VXLAN ID cannot be identical to the segment ID of a vNetwork or vRouter.

Update DR System

Keyword	UPDATE_MLAG_GROUP_OP
Message text	Updated a DR system: “$1”
Variable fields	$1: DR system information.
Example	Updated a DR system: ID:[9b6fd1fe-975b-40e9-bce4-6cb4e3c9f215] Name:[mlag] Description:[null] JoinType:[USER_CREATE]
Explanation	A DR system was edited.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · You have no privilege to perform this operation. · Unknown internal server error. · The DR system name already exists. · The DR system name cannot be empty. · The DR system name cannot exceed 255 characters. · The DR system description cannot exceed 255 characters. · The device ID is not specified. · The device does not exist. · The DR system does not exist. · Please specify the link aggregation mode for DR interfaces. · Invalid link aggregation mode for DR interfaces.

Delete DR System

Keyword	DELETE_MLAG_GROUP_OP
Message text	Deleted DR system “$1”.
Variable fields	$1: DR system information.
Example	Deleted DR system: ID: [9b6fd1fe-975b-40e9-bce4-6cb4e3c9f215] Name: [mlag] Description: [peer link mlag]. \ joinType: [USER_CREATE]
Explanation	A DR system was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · You have no privilege to perform this operation. · Unknown internal server error. · The DR system does not exist. · Cannot delete the DR system. It contains DR groups. · Cannot delete the DR system. It contains LAG groups. · The DR group does not exist.

Create LAG Group

Keyword	CREATE_MLAG_LAGG_GROUP_OP
Message text	Created a LAG group: “$1”
Variable fields	$1: Link aggregation group information.
Example	Created a LAG group: { "id": "fd6e250a-ab65-4b80-98b7-8a6d607d7a36", "data_source": "AUTO_ONLINE", "member_list": [ "5b1ae1a2-a26a-4625-8656-20d9dc62a27a", "1fe507b0-af05-40ef-9156-1a61542326c9" }
Explanation	A link aggregation group was created.
Possible failure causes	· Invalid JSON format. · The controller is not the active leader. · Configuration recovery is in progress. · Bridge aggregation must be dynamic. · You must specify two different member devices for a DR system. · The device already is a DR system member. · The LAG group does not exist. · Please specify the DR group ID range. · The DR group has not obtained an ID from the DR group ID range. · The DR system ID already exists. · You have no privilege to perform this operation.

Delete LAG Group

Keyword	DELETE_MLAG_LAGG_GROUP_OP
Message text	Deleted LAG group “$1”.
Variable fields	$1: Link aggregation group name.
Example	Deleted LAG group laggroup.
Explanation	A link aggregation group was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown error. · The LAG group does not exist. · You have no privilege to perform this operation.

Create User-Defined Device Info

Keyword	CREATE_CUSTOMIZED_DEVICE_INFO_OP
Message text	Customized configuration of $1 devices: $2
Variable fields	$1: Device role. Options include spine, leaf, aggregation, and access. $2: Customized device configuration.
Example	Customized configuration of spine devices: [ [H3CS6800] driver = 6800 ##VXLAN resources ##Riot-mode start _vxlan_resource = l3gw40k _border_vxlan_resource = border40k ##Riot-mode end ##Switch-mode resources _switch_mode = 4 [H3CS125] driver = 125AF _vxlan_resource = normal [H3CS5560X] driver = 5560X _switch_mode = 1 _ecmp_num = 4 ].
Explanation	Customized configuration for a device.
Possible failure causes	· Invalid JSON format. · The controller is not the active leader. · Configuration recovery is in progress. · The device does not exist. · You have no privilege to perform this operation. · The device role can only be spine, leaf, aggregation, or access.

Delete User-Defined Device Info

Keyword	DELETE_CUSTOMIZED_DEVICE_INFO_OP
Message text	Deleted configuration file $1 for $2 devices.
Variable fields	$1: File name. $2: Device role. Options include spine, leaf, aggregation, and access.
Example	Deleted configuration file spine.config for spine devices.
Explanation	Deleted the configuration file of a device.
Possible failure causes	· Invalid JSON format. · The controller is not the active leader. · Configuration recovery is in progress. · The device does not exist. · You have no privilege to perform this operation. · The device role can only be spine, leaf, aggregation, or access

Create address prefix

Keyword	CREATE_IPPREFIX_OP
Message text	Created address prefix: $1
Variable fields	$1: Address prefix information.
Example	Created address prefix: [ ipPrefix UUID:[1459ae05-70bf-44ef-8aa9-328838611ace] ipPrefix name:[111] ipPrefix ipVersion:[4] ipPrefix description:[] ipPrefix tenantId:[3d2c2819-1106-4e81-867d-38907a2bd20b] ipPrefix rules:[[]]]
Explanation	An address prefix was added.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid JSON format. · The address prefix already exists. · Invalid name. · Invalid description. · Duplicate name exists. · Invalid IP version. · Invalid tenant ID. · You have no privilege to perform this operation.

Update address prefix

Keyword	UPDATE_IPPREFIX_OP
Message text	Updated address prefix: $1
Variable fields	$1: Address prefix information.
Example	Updated address prefix: ipPrefix UUID:[66132e94-22fb-443c-9472-4d2e55c1ac0a] ipPrefix name:[1] ipPrefix ipVersion:[4] ipPrefix description:[] ipPrefix tenantId:[ef7fbcf5-aecd-45f6-9f69-fee7329b208d] ipPrefix rules:[[ ipPrefixRule UUID:[23e6d07e-ca28-4925-93c0-46003e7da0eb] ipPrefixRule prefixId:[66132e94-22fb-443c-9472-4d2e55c1ac0a] ipPrefixRule indexNumber:[1] ipPrefixRule permit:[true] ipPrefixRule ipPrefix:[0.0.0.0] ipPrefixRule mask:[1] ipPrefixRule lessEqual:[1] ipPrefixRule greatEqual:[1]]]
Explanation	An address prefix was edited.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid JSON format. · The specified address prefix does not exist. · Invalid description. · You have no privilege to perform this operation.

Delete address prefix

Keyword	DELETE_IPPREFIX_OP
Message text	Deleted address prefix: $1
Variable fields	$1: Address prefix information.
Example	Deleted address prefix: ipPrefix UUID:[960e15c4-4274-499a-9643-a22da32a64ae] ipPrefix name:[ip_prefix] ipPrefix ipVersion:[4] ipPrefix description:[ip_prefix] ipPrefix tenantId:[4607eb06-0b5d-45b0-bf13-6d94344ac3df] ipPrefix rules: [ [ ipPrefixRule UUID:[a8134e8f-084b-44bb-bd73-8778a216bd1d] ipPrefixRule prefixId:[960e15c4-4274-499a-9643-a22da32a64ae] ipPrefixRule indexNumber:[22] ipPrefixRule permit:[true] ipPrefixRule ipPrefix:[22.22.0.0] ipPrefixRule mask:[16] ipPrefixRule lessEqual:[18] ipPrefixRule greatEqual:[22] ] ]
Explanation	An address prefix was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · The specified address prefix does not exist. · Cannot delete the address prefix because it has been bound to a routing policy. · Cannot delete the address prefix because it has prefix rules configured. · You have no privilege to perform this operation.

Create address prefix rule

Keyword	CREATE_IPPREFIXRULE_OP
Message text	Created address prefix rule: $1
Variable fields	$1: Address prefix rule information.
Example	Created address prefix rule: [ ipPrefixRule UUID:[23e6d07e-ca28-4925-93c0-46003e7da0eb] ipPrefixRule prefixId:[66132e94-22fb-443c-9472-4d2e55c1ac0a] ipPrefixRule indexNumber:[1] ipPrefixRule permit:[true] ipPrefixRule ipPrefix:[0.0.0.0] ipPrefixRule mask:[0] ipPrefixRule lessEqual:[1] ipPrefixRule greatEqual:[1]]
Explanation	An address prefix rule was added.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid JSON format. · The specified address prefix does not exist. · Duplicate index exists. · Please specify an address prefix UUID. · Please specify a mode. · Invalid mode. · Invalid network address. · Please specify an ID. · Invalid index. · The ID already exists. · Invalid minimum prefix length. · Invalid maximum prefix length. · Different prefix rules cannot have the same match criteria. · A prefix rule with the same match criteria already exists. · You have no privilege to perform this operation.

Update address prefix rule

Keyword	UPDATE_IPPREFIXRULE_OP
Message text	Updated address prefix rule: $1
Variable fields	$1: Address prefix rule information.
Example	Updated address prefix rule: ipPrefixRule UUID:[23e6d07e-ca28-4925-93c0-46003e7da0eb] ipPrefixRule prefixId:[66132e94-22fb-443c-9472-4d2e55c1ac0a] ipPrefixRule indexNumber:[1] ipPrefixRule permit:[true] ipPrefixRule ipPrefix:[0.0.0.0] ipPrefixRule mask:[1] ipPrefixRule lessEqual:[1] ipPrefixRule greatEqual:[1]
Explanation	An address prefix rule was edited.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid JSON format. · The specified prefix rule does not exist. · Invalid mode. · Invalid network address. · Invalid minimum prefix length. · Invalid maximum prefix length. · A prefix rule with the same match criteria already exists. · You have no privilege to perform this operation.

Delete address prefix rule

Keyword	DELETE_IPPREFIXRULE_OP
Message text	Deleted address prefix rule: $1
Variable fields	$1: Address prefix rule information.
Example	Deleted address prefix rule: ipPrefixRule UUID:[4fa579be-a6bb-49d6-b589-c19b11c7e9c2] ipPrefixRule prefixId:[960e15c4-4274-499a-9643-a22da32a64ae] ipPrefixRule indexNumber:[23] ipPrefixRule permit:[true] ipPrefixRule ipPrefix:[22.22.0.0] ipPrefixRule mask:[15] ipPrefixRule lessEqual:[16] ipPrefixRule greatEqual:[19]
Explanation	An address prefix rule was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · The specified prefix rule does not exist. · You have no privilege to perform this operation.

Create routing policy

Keyword	CREATE_ROUTE_POLICY_OP
Message text	Created routing policy: $1
Variable fields	$1: Routing policy information.
Example	Created routing policy:[ id: bff339b7-07f0-4caa-82ed-d642c0394284 name: adads description: tenantId: c4468dbb-ab73-4c35-b3eb-bb09715e6f90 nodes: []]
Explanation	A routing policy was created.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid JSON format. · Invalid parameter. · Invalid description. · Invalid name. · The specified tenant does not exist. · Please specify a mode. · A routing policy already exists with the specified name. · Please specify a name. · Invalid tenant ID. · You have no privilege to perform this operation.

Update routing policy

Keyword	UPDATE_ROUTE_POLICY_OP
Message text	Updated routing policy: $1
Variable fields	$1: Routing policy information.
Example	Updated routing policy: id: 5ebe31ca-b07a-4d28-8ece-f43a790e8b57 name: route description: route tenantId: c4468dbb-ab73-4c35-b3eb-bb09715e6f90 nodes: [ id: c7133f3c-46d0-4446-b93b-e9cbfa108aee type: address-prefix permit: false number: 123 ipv4PrefixId: ed43ae0f-fe4b-495e-9206-06104ad70256 policyId: 5ebe31ca-b07a-4d28-8ece-f43a790e8b57]
Explanation	A routing policy was edited.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid JSON format. · Invalid parameter. · Invalid description. · Cannot edit the routing policy UUID. · The specified routing policy does not exist. · Cannot edit the routing policy name. · The specified resource does not exist. · The tenant ID cannot be modified. · You have no privilege to perform this operation.

Delete routing policy

Keyword	DELETE_ROUTE_POLICY_OP
Message text	Deleted routing policy: $1
Variable fields	$1: Routing policy information.
Example	Deleted routing policy: { "RoutePolicyConfig": { "id":498ce629-7839-4225-b7e3-d9628e6df7d1, "decodeId":null, "name":"router_policy", "tenantId":4607eb06-0b5d-45b0-bf13-6d94344ac3df, "desc":"router policy", "ipVersion":4, "nodes":[] } }
Explanation	A routing policy was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · The specified routing policy does not exist. · Cannot delete the routing policy because it has nodes configured. · Cannot delete the routing policy because it has been bound to an OSPF policy. · You have no privilege to perform this operation.

Create routing policy node

Keyword	CREATE_ROUTE_POLICY_NODE_OP
Message text	Created routing policy node: $1
Variable fields	$1: Routing policy node information.
Example	Created routing policy node:[ id: 774a9a81-eabe-4f06-8f05-1e7e7f64fbe3 type: permit: false number: 0 ipv4PrefixId: policyId: bff339b7-07f0-4caa-82ed-d642c0394284]
Explanation	A routing policy node was added.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid JSON format. · Invalid parameter. · Invalid match rule. · Please specify a node number. · The specified routing policy does not exist. · Please specify a routing policy ID. · Duplicate node number exists. · The routing policy node already exists. · The specified node number already exists. · The specifiedaddress prefix does not exist. · Invalid number. · You have no privilege to perform this operation.

Update routing policy node

Keyword	UPDATE_ROUTE_POLICY_NODE_OP
Message text	Updated routing policy node: $1
Variable fields	$1: Routing policy node information.
Example	Updated routing policy node: id: 3cdd1179-239a-4705-9cb8-427fceb0733d type: permit: false number: 0 ipv4PrefixId: policyId: 850f2fce-c246-4fad-84c6-b565c4d31b1d
Explanation	A routing policy node was edited.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid JSON format. · Invalid parameter. · Invalid match rule. · annot edit the routing policy UUID. · The specifiedaddress prefix does not exist. · You have no privilege to perform this operation.

Delete routing policy node

Keyword	DELETE_ROUTE_POLICY_NODE_OP
Message text	Deleted routing policy node: $1
Variable fields	$1: Routing policy node information.
Example	Deleted routing policy node: { "RoutePolicyNodeConfig": { "id":"d5fabf1b-8ac8-4503-b0e4-c5c5a63250f1", "policyId":498ce629-7839-4225-b7e3-d9628e6df7d1, "type":"address-prefix", "permit":true, "number":21, "ipv4PrefixId":"960e15c4-4274-499a-9643-a22da32a64ae", "ipv6PrefixId":"null" } }
Explanation	A routing policy node was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · The specified resource does not exist. · You have no privilege to perform this operation.

Create OSPF policy

Keyword	CREATE_OSPF_POLICY_OP
Message text	Created OSPF policy: $1
Variable fields	$1: OSPF policy information.
Example	Created OSPF policy: [{"OspfPolicyConfig":{"id":14c2f824-cc5f-43c1-9f12-9b26e698f18c, "name":"1", "tenantId":ef7fbcf5-aecd-45f6-9f69-fee7329b208d, "description":"", "ipVersion":4, "nsr":false, "vpnInstanceCapability":1, "routerId":"", "fabricImportOspfRoutePolicy":null, "fabricImportOspfRoutePolicyName":"null", "ospfAreaConfigs":[], "ospfImportRouteConfigs":[], "ospfInterfacePolicyConfigs":[]}}]
Explanation	An OSPF policy was created.
Possible failure causes	· The controller is not the active leader. · ion recovery is in progress. · Unknown internal server error. · Invalid JSON format. · Invalid parameter. · Invalid name. · Invalid description. · The specified tenant does not exist. · Invalid IP version. · The specified routing policy does not exist. · The OSPF policy name already exists. · An OSPF policy already exists with the specified name. · Invalid tenant ID. · You have no privilege to perform this operation. · IP version mismatch.

Update OSPF policy

Keyword	UPDATE_OSPF_POLICY_OP
Message text	Updated OSPF policy: $1
Variable fields	$1: OSPF policy information.
Example	Updated OSPF policy:{"OspfPolicyConfig":{ "id":3d416fc0-5846-4693-863b-3115f54c37dd, "name":"shw_ospf_2", "tenantId":fa580b08-9f94-4ccb-b53f-8e84841df8f2, "description":"", "ipVersion":4, "nsr":false, "vpnInstanceCapability":1, "routerId":"1.1.1.1", "fabricImportOspfRoutePolicy":null, "fabricImportOspfRoutePolicyName":"null", "ospfAreaConfigs":[], "ospfImportRouteConfigs":[], "ospfInterfacePolicyConfigs":[]}}
Explanation	An OSPF policy was edited.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid JSON format. · Invalid parameter. · Invalid description. · The specified OSPF or OSPFv3 policy does not exist. · The specified routing policy does not exist. · Cannot edit the OSPF policy name. · You have no privilege to perform this operation. · IP version mismatch.

Delete OSPF policy

Keyword	DELETE_OSPF_POLICY_OP
Message text	Deleted OSPF policy: $1
Variable fields	$1: OSPF policy information.
Example	Deleted OSPF policy: { "OspfPolicyConfig": { "id":5a53d2e1-e939-40e1-b7ce-2eb0ef761010, "name":"ospf_policy", "tenantId":4607eb06-0b5d-45b0-bf13-6d94344ac3df, "description":"ospf policy", "ipVersion":4, "nsr":true, "vpnInstanceCapability":1, "fabricImportOspfRoutePolicy":498ce629-7839-4225-b7e3-d9628e6df7d1, "fabricImportOspfRoutePolicyName":"router_policy", "ospfAreaConfigs":[], "ospfImportRouteConfigs":[], "ospfInterfacePolicyConfigs":[] } }
Explanation	An OSPF policy was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · The specified OSPF policy does not exist. · Cannot delete the OSPF policy because it contains area, route redistribution, or interface policy settings. · Cannot delete the OSPF policy because it has been bound. · You have no privilege to perform this operation.

Create OSPFv3 policy

Keyword	CREATE_OSPFV3_POLICY_OP
Message text	Created OSPFv3 policy: $1
Variable fields	$1: OSPFv3 policy information.
Example	Created OSPFv3 policy:[{ "OspfPolicyConfig":{ "id":bf97cd8e-4e46-4554-9366-469301279f1c, "name":"fds", "tenantId":null, "description":"", "ipVersion":6, "nsr":false, "vpnInstanceCapability":1, "fabricImportOspfRoutePolicy":null, "fabricImportOspfRoutePolicyName":"null", "ospfAreaConfigs":[], "ospfImportRouteConfigs":[], "ospfInterfacePolicyConfigs":[] } }]
Explanation	An OSPFv3 policy was created.
Possible failure causes	· The controller is not the active leader. · ion recovery is in progress. · Unknown internal server error. · Invalid JSON format. · Invalid parameter. · Invalid name. · Invalid description. · The specified tenant does not exist. · Invalid IP version. · The specified routing policy does not exist. · The OSPFv3 policy name already exists. · An OSPFv3 policy already exists with the specified name. · Invalid tenant ID. · You have no privilege to perform this operation. · IP version mismatch.

Update OSPFv3 policy

Keyword	UPDATE_OSPFV3_POLICY_OP
Message text	Updated OSPFv3 policy: $1
Variable fields	$1: OSPFv3 policy information.
Example	Updated OSPFv3 policy:[{ "OspfPolicyConfig":{ "id":224318aa-8a75-488e-a030-4fae5a1fdd23, "name":"testv6", "tenantId":null, "description":"", "ipVersion":6, "nsr":false, "vpnInstanceCapability":1, "fabricImportOspfRoutePolicy":null, "fabricImportOspfRoutePolicyName":"null", "ospfAreaConfigs":[], "ospfImportRouteConfigs":[], "ospfInterfacePolicyConfigs":[{ "OspfInterfacePolicyConfig":{ "id":0835de81-4459-446e-9860-b2f5c6bdb7e6, "ospfPolicyId":224318aa-8a75-488e-a030-4fae5a1fdd23, "name":"2", "vsiName":"null", "description":"null", "networkType":null, "interfaceCost":null, "bfdEnable":false, "deadTimer":2, "drPriority":1, "helloTimer":null, "ospfInstanceName":null, "authentications":[] } }]
Explanation	An OSPFv3 policy was edited.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid JSON format. · Invalid parameter. · Invalid description. · The specified OSPF or OSPFv3 policy does not exist. · The specified routing policy does not exist. · Cannot edit the OSPFv3 policy name. · You have no privilege to perform this operation. · IP version mismatch.

Delete OSPFv3 policy

Keyword	DELETE_OSPFV3_POLICY_OP
Message text	Deleted OSPFv3 policy: $1
Variable fields	$1: OSPFv3 policy information.
Example	Deleted OSPFv3 policy: { "OspfPolicyConfig": { "id":5a53d2e1-e939-40e1-b7ce-2eb0ef761010, "name":"ospfv3_policy", "tenantId":4607eb06-0b5d-45b0-bf13-6d94344ac3df, "description":"ospfv3 policy", "ipVersion":6, "nsr":true, "vpnInstanceCapability":1, "fabricImportOspfRoutePolicy":498ce629-7839-4225-b7e3-d9628e6df7d1, "fabricImportOspfRoutePolicyName":"router_policy", "ospfAreaConfigs":[], "ospfImportRouteConfigs":[], "ospfInterfacePolicyConfigs":[] } }
Explanation	An OSPFv3 policy was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · The specified OSPF or OSPFv3 policy does not exist. · Cannot delete the OSPFv3 policy because it contains area, route redistribution, or interface policy settings. · Cannot delete the OSPFv3 policy because it has been bound. · You have no privilege to perform this operation.

Create OSPF area

Keyword	CREATE_OSPF_AREA_OP
Message text	Created OSPF area: $1
Variable fields	$1: OSPF area information.
Example	Created OSPF area:[{"OspfAreaConfig":{ "id":1220cc43-9bee-4204-b445-ff98f1ed7cfd, "ospfPolicyId":ba460ae5-483d-4698-aca1-45b27a090024, "type":0, "areaId":"23.24.24.5", "network":"null", "mask":null, "tenantID":null}}]
Explanation	An OSPF area was added.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid JSON format. · Invalid parameter. · Invalid network address. · Invalid area type. · Invalid area ID. · The specified OSPF policy does not exist. · The area newtork overlaps with another area network. · You have no privilege to perform this operation.

Update OSPF area

Keyword	UPDATE_OSPF_AREA_OP
Message text	Updated OSPF area: $1
Variable fields	$1: OSPF area information.
Example	Updated OSPF area:{"OspfAreaConfig":{ "id":076aec50-2f8c-4832-bb1e-3553f2f55138, "ospfPolicyId":5289f321-6ee2-40ef-9124-08d5010b4843, "type":0, "areaId":"0.0.0.0", "network":"52.1.1.0", "mask":24, "tenantID":null}}
Explanation	An OSPF area was edited.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid JSON format. · Invalid parameter. · Invalid network address. · Invalid area type. · The area newtork overlaps with another area network. · You have no privilege to perform this operation.

Delete OSPF area

Keyword	DELETE_OSPF_AREA_OP
Message text	Deleted OSPF area: $1
Variable fields	$1: OSPF area information.
Example	Deleted OSPF area: { "OspfAreaConfig": { "id":e02dcb2a-3fea-4811-ac31-0527a53d13f8, "ospfPolicyId":5a53d2e1-e939-40e1-b7ce-2eb0ef761010, "type":0, "areaId":"0.0.0.0" } }
Explanation	An OSPF area was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · The specified OSPF area does not exist. · Cannot delete the area because it has been bound to an interface policy. · You have no privilege to perform this operation.

Create OSPFv3 area

Keyword	CREATE_OSPFV3_AREA_OP
Message text	Created OSPFv3 area: $1
Variable fields	$1: OSPFv3 area information.
Example	Created OSPFv3 area:[{"OspfAreaConfig":{ "id":1220cc43-9bee-4204-b445-ff98f1ed7cfd, "ospfPolicyId":ba460ae5-483d-4698-aca1-45b27a090024, "type":0, "areaId":"23.24.24.5", "network":"null", "mask":null, "tenantID":null}}]
Explanation	An OSPFv3 area was created.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid JSON format. · Invalid parameter. · Invalid network address. · Invalid area type. · Invalid area ID. · The specified OSPF policy does not exist. · The area newtork overlaps with another area newtork. · You have no privilege to perform this operation.

Update OSPFv3 area

Keyword	UPDATE_OSPFV3_AREA_OP
Message text	Updated OSPFv3 area: $1
Variable fields	$1: OSPFv3 area information.
Example	Updated OSPFv3 area:{"OspfAreaConfig":{ "id":076aec50-2f8c-4832-bb1e-3553f2f55138, "ospfPolicyId":5289f321-6ee2-40ef-9124-08d5010b4843, "type":0, "areaId":"0.0.0.0", "network":"52.1.1.0", "mask":24, "tenantID":null}}
Explanation	An OSPFv3 area was edited.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid JSON format. · Invalid parameter. · Invalid network address. · Invalid area type. · The area newtork overlaps with another area newtork. · You have no privilege to perform this operation.

Delete OSPFv3 area

Keyword	DELETE_OSPFV3_AREA_OP
Message text	Deleted OSPFv3 area: $1
Variable fields	$1: OSPFv3 area information.
Example	Deleted OSPFv3 area: { "OspfAreaConfig": { "id":e02dcb2a-3fea-4811-ac31-0527a53d13f8, "ospfPolicyId":5a53d2e1-e939-40e1-b7ce-2eb0ef761010, "type":0, "areaId":"0.0.0.0" } }
Explanation	An OSPFv3 area was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · The specified OSPF policy does not exist. · Cannot delete the area because it has been bound to an interface policy. · You have no privilege to perform this operation.

Create OSPF route redistribution rule

Keyword	CREATE_OSPF_IMPORT_ROUTE_OP
Message text	Created OSPF route redistribution rule: $1
Variable fields	$1: OSPF route redistribution rule information.
Example	Created OSPF route redistribution rule:[{"OspfImportRouteConfig":{ "id":5cb92655-8a6b-4847-9fec-75b9ed331f00, "ospfPolicyId":50724bf4-9367-4941-af47-a98ce0dcfa06, "cost":"2", "protocol":"bgp", "asNumber":"1", "allowIbgp":true, "routePolicyId":null, "routePolicyName":"null"}}]
Explanation	An OSPF route redistribution rule was added.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid JSON format. · Invalid parameter. · Invalid protocol. · The protocol has already been specified. · Invalid route cost. · Invalid allow_ibgp. · Invalid process ID. · The specified OSPF policy does not exist. · The specified routing policy does not exist. · Invalid OSPF policy UUID. · You have no privilege to perform this operation. · IP version mismatch.

Update OSPF route redistribution rule

Keyword	UPDATE_OSPF_IMPORT_ROUTE_OP
Message text	Updated OSPF route redistribution rule: $1
Variable fields	$1: OSPF route redistribution rule information.
Example	Updated OSPF route redistribution rule:{"OspfImportRouteConfig":{ "id":dbb18f11-1d43-4498-89ef-0ef661d92676, "ospfPolicyId":5af962ab-fefe-43f9-8d5f-f0c77c5cf4d0, "cost":"1", "protocol":"bgp", "asNumber":"1", "allowIbgp":true, "routePolicyId":850f2fce-c246-4fad-84c6-b565c4d31b1d, "routePolicyName":"2"}}
Explanation	An OSPF route redistribution rule was edited.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid JSON format. · Invalid parameter. · Invalid protocol. · The protocol has already been specified. · Invalid route cost. · Invalid allow_ibgp. · Invalid process ID. · The specified routing policy does not exist. · Invalid OSPF policy UUID. · The specified resource does not exist. · You have no privilege to perform this operation. · IP version mismatch.

Delete OSPF route redistribution rule

Keyword	DELETE_OSPF_IMPORT_ROUTE_OP
Message text	Deleted OSPF route redistribution rule: $1
Variable fields	$1: OSPF route redistribution rule information.
Example	Deleted OSPF route redistribution rule: { "OspfImportRouteConfig": { "id":9178924a-8d3a-4651-9fd1-e33ac01b73aa, "ospfPolicyId":5a53d2e1-e939-40e1-b7ce-2eb0ef761010, "cost":"22", "protocol":"bgp", "asNumber":"22", "allowIbgp":true, "routePolicyId":498ce629-7839-4225-b7e3-d9628e6df7d1, "routePolicyName":"router_policy" } }
Explanation	An OSPF route redistribution rule was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · The specified resource does not exist. · You have no privilege to perform this operation.

Create OSPFv3 route redistribution rule

Keyword	CREATE_OSPFV3_IMPORT_ROUTE_OP
Message text	Created OSPFv3 route redistribution rule: $1
Variable fields	$1:OSPFv3 route redistribution rule information.
Example	Created OSPFv3 route redistribution rule:[{"OspfImportRouteConfig":{ "id":5cb92655-8a6b-4847-9fec-75b9ed331f00, "ospfPolicyId":50724bf4-9367-4941-af47-a98ce0dcfa06, "cost":"2", "protocol":"bgp", "asNumber":"1", "allowIbgp":true, "routePolicyId":null, "routePolicyName":"null"}}]
Explanation	An OSPFv3 route redistribution rule was created.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid JSON format. · Invalid parameter. · Invalid protocol. · The protocol has already been specified. · Invalid route cost. · Invalid allow_ibgp. · Invalid process ID. · The specified OSPF policy does not exist. · The specified routing policy does not exist. · Invalid OSPF policy UUID. · You have no privilege to perform this operation. · IP version mismatch.

Update OSPFv3 route redistribution rule

Keyword	UPDATE_OSPFV3_IMPORT_ROUTE_OP
Message text	Updated OSPFv3 route redistribution rule: $1
Variable fields	$1: OSPFv3 route redistribution rule information.
Example	Updated OSPFv3 route redistribution rule:{"OspfImportRouteConfig":{ "id":dbb18f11-1d43-4498-89ef-0ef661d92676, "ospfPolicyId":5af962ab-fefe-43f9-8d5f-f0c77c5cf4d0, "cost":"1", "protocol":"bgp", "asNumber":"1", "allowIbgp":true, "routePolicyId":850f2fce-c246-4fad-84c6-b565c4d31b1d, "routePolicyName":"2"}}
Explanation	An OSPFv3 route redistribution rule was edited.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid JSON format. · Invalid parameter. · Invalid protocol. · The protocol has already been specified. · Invalid route cost. · Invalid allow_ibgp. · Invalid process ID. · The specified routing policy does not exist. · Invalid OSPF policy UUID. · The specified resource does not exist. · You have no privilege to perform this operation. · IP version mismatch.

Delete OSPFv3 route redistribution rule

Keyword	DELETE_OSPFV3_IMPORT_ROUTE_OP
Message text	Deleted OSPFv3 route redistribution rule: $1
Variable fields	$1: OSPFv3 route redistribution rule information.
Example	Deleted OSPFv3 route redistribution rule: { "OspfImportRouteConfig": { "id":9178924a-8d3a-4651-9fd1-e33ac01b73aa, "ospfPolicyId":5a53d2e1-e939-40e1-b7ce-2eb0ef761010, "cost":"22", "protocol":"bgp", "asNumber":"22", "allowIbgp":true, "routePolicyId":498ce629-7839-4225-b7e3-d9628e6df7d1, "routePolicyName":"router_policy" } }
Explanation	An OSPFv3 route redistribution rule was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · The specified resource does not exist, · You have no privilege to perform this operation.

Create OSPF interface policy

Keyword	CREATE_OSPF_INTERFACE_POLICY_OP
Message text	Created OSPF interface policy: $1
Variable fields	$1: OSPF interface policy information.
Example	Created OSPF interface policy:[{"OspfInterfacePolicyConfig":{ "id":bdc309e3-2158-478a-9563-70cc00836d43, "ospfPolicyId":ba460ae5-483d-4698-aca1-45b27a090024, "name":"22", "vsiName":"null", "description":"null", "networkType":1, "areaId":"23.24.24.5", "interfaceCost":null, "bfdEnable":false, "deadTimer":null, "drPriority":1, "helloTimer":null, "ospfInstanceName":null}}]
Explanation	An OSPF interface policy was added.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid JSON format. · Invalid parameter. · Invalid network type. · The interface policy name already exists. · Invalid name. · Invalid interface cost. · Invalid description. · Invalid hello interval. · Invalid dead interval. · Invalid router priority. · The specified OSPF policy does not exist. · The specified OSPF area does not exist. · Invalid area ID. · You have no privilege to perform this operation.

Update OSPF interface policy

Keyword	UPDATE_OSPF_INTERFACE_POLICY_OP
Message text	Updated OSPF interface policy: $1
Variable fields	$1: OSPF interface policy information.
Example	Updated OSPF interface policy:[{"OspfInterfacePolicyConfig":{ "id":bdc309e3-2158-478a-9563-70cc00836d43, "ospfPolicyId":ba460ae5-483d-4698-aca1-45b27a090024, "name":"22", "vsiName":"null", "description":"null", "networkType":1, "areaId":"23.24.24.5", "interfaceCost":null, "bfdEnable":false, "deadTimer":null, "drPriority":1, "helloTimer":null, "ospfInstanceName":null}}]
Explanation	An OSPF interface policy was edited.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid JSON format. · Invalid parameter. · Invalid network type. · Invalid interface cost. · Invalid description. · Invalid hello interval. · Invalid dead interval. · Invalid router priority. · The specified OSPF area does not exist. · Invalid area ID. · You have no privilege to perform this operation.

Delete OSPF interface policy

Keyword	DELETE_OSPF_INTERFACE_POLICY_OP
Message text	Deleted OSPF interface policy: $1
Variable fields	$1: OSPF interface policy information.
Example	Deleted OSPF interface policy: { "OspfInterfacePolicyConfig": { "id":a20ea450-2628-42b8-9d8e-ade68c2eab14, "ospfPolicyId":5a53d2e1-e939-40e1-b7ce-2eb0ef761010, "name":"interface_policy", "vsiName":"null", "description":"interface policy", "networkType":1, "interfaceCost":22, "bfdEnable":false, "deadTimer":22, "drPriority":1, "helloTimer":22, "ospfInstanceName":null, "authentications": [ { "OspfInterfaceAuthentication": { "id":7b3173a9-3191-4aae-ae97-42dd45921a6c, "authenticationMode":1, "keyId":22, "cipher":2, "password":"********" } } ] } }
Explanation	An OSPF interface policy was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · The specified interface policy does not exist. · Cannot delete the interface policy because it has been bound. · You have no privilege to perform this operation.

Create OSPFv3 interface policy

Keyword	CREATE_OSPFV3_INTERFACE_POLICY_OP
Message text	Created OSPFv3 interface policy: $1
Variable fields	$1: OSPFv3 interface policy information.
Example	Created OSPFv3 interface policy:[{"OspfInterfacePolicyConfig":{ "id":bdc309e3-2158-478a-9563-70cc00836d43, "ospfPolicyId":ba460ae5-483d-4698-aca1-45b27a090024, "name":"22", "vsiName":"null", "description":"null", "networkType":1, "areaId":"23.24.24.5", "interfaceCost":null, "bfdEnable":false, "deadTimer":null, "drPriority":1, "helloTimer":null, "ospfInstanceName":null}}]
Explanation	An OSPFv3 interface policy was created.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid JSON format. · Invalid parameter. · Invalid network type. · The interface policy name already exists. · Invalid name. · Invalid interface cost. · Invalid description. · Invalid hello interval. · Invalid dead interval. · Invalid router priority. · The specified OSPF policy does not exist. · The specified OSPF area does not exist. · Invalid area ID. · You have no privilege to perform this operation.

Update OSPFv3 interface policy

Keyword	UPDATE_OSPFV3_INTERFACE_POLICY_OP
Message text	Updated OSPFv3 interface policy: $1
Variable fields	$1: OSPFv3 interface policy information.
Example	Updated OSPFv3 interface policy:[{"OspfInterfacePolicyConfig":{ "id":bdc309e3-2158-478a-9563-70cc00836d43, "ospfPolicyId":ba460ae5-483d-4698-aca1-45b27a090024, "name":"22", "vsiName":"null", "description":"null", "networkType":1, "areaId":"23.24.24.5", "interfaceCost":null, "bfdEnable":false, "deadTimer":null, "drPriority":1, "helloTimer":null, "ospfInstanceName":null}}]
Explanation	An OSPFv3 interface policy was edited.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid JSON format. · Invalid parameter. · Invalid network type. · Invalid interface cost. · Invalid description. · Invalid hello interval. · Invalid dead interval. · Invalid router priority. · The specified OSPF area does not exist. · Invalid area ID. · You have no privilege to perform this operation.

Delete OSPFv3 interface policy

Keyword	DELETE_OSPFV3_INTERFACE_POLICY_OP
Message text	Deleted OSPFv3 interface policy: $1
Variable fields	$1: OSPFv3 interface policy information.
Example	Deleted OSPFv3 interface policy: { "OspfInterfacePolicyConfig": { "id":a20ea450-2628-42b8-9d8e-ade68c2eab14, "ospfPolicyId":5a53d2e1-e939-40e1-b7ce-2eb0ef761010, "name":"interface_policy", "vsiName":"null", "description":"interface policy", "networkType":1, "interfaceCost":22, "bfdEnable":false, "deadTimer":22, "drPriority":1, "helloTimer":22, "ospfInstanceName":null, "authentications": [ { "OspfInterfaceAuthentication": { "id":7b3173a9-3191-4aae-ae97-42dd45921a6c, "authenticationMode":1, "keyId":22, "cipher":2, "password":"********" } } ] } }
Explanation	An OSPFv3 interface policy was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · The specified interface policy does not exist. · Cannot delete the interface policy because it has been bound. · You have no privilege to perform this operation.

Create OSPF policy application

Keyword	CREATE_OSPF_POLICY_APPLY_OP
Message text	Created OSPF policy application: $1
Variable fields	$1: OSPF policy application information.
Example	Created OSPF policy application:[{"OspfPolicyApplyConfig":{ "id":d483f937-1cd5-4649-bc4d-d91d5bea5bb0, "object":0, "sourceName":"null", "ospfPolicyId":24bf351d-b04b-4a2d-8f8b-b94761a716d1, "tenantId":fa580b08-9f94-4ccb-b53f-8e84841df8f2, "policyName":"null", "networkId":f4d4a104-c33f-4b72-b968-c4d38c3304b3, "typeName":"null", "ospfInterfacePolicyId":null, "interfaceName":"null", "instanceId":33 "routeId":99.55.23.33, "ipVersion":4 }}]
Explanation	An OSPF policy application was added.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid JSON format. · Invalid parameter. · Invalid tenant ID. · Please specify an OSPF policy UUID. · The ospf policy apply already exists. · Invalid OSPF policy UUID. · Invalid interface policy UUID. · Invalid OSPF process ID. · The process ID already exists. · You cannot bind an OSPF policy to a vNetwork generated upon PBR service chain creation. · You have no privilege to perform this operation. · IP version mismatch. · Invalid router ID.

Update OSPF policy application

Keyword	UPDATE_OSPF_POLICY_APPLY_OP
Message text	Updated OSPF policy application: $1
Variable fields	$1: OSPF policy application information.
Example	Updated OSPF policy application:[{"OspfPolicyApplyConfig":{ "id":d483f937-1cd5-4649-bc4d-d91d5bea5bb0, "object":0, "sourceName":"null", "ospfPolicyId":24bf351d-b04b-4a2d-8f8b-b94761a716d1, "tenantId":fa580b08-9f94-4ccb-b53f-8e84841df8f2, "policyName":"null", "networkId":f4d4a104-c33f-4b72-b968-c4d38c3304b3, "typeName":"null", "ospfInterfacePolicyId":null, "interfaceName":"null", "instanceId":33 "routeId":99.55.23.33, "ipVersion":4 }}]
Explanation	An OSPF policy application was edited.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid JSON format. · Invalid parameter. · The ospf policy apply already exists. · Invalid OSPF policy UUID. · Invalid interface policy UUID. · The specified OSPF or OSPFv3 policy application does not exist. · You have no privilege to perform this operation. · IP version mismatch. · Invalid router ID.

Delete OSPF policy application

Keyword	DELETE_OSPF_POLICY_APPLY_OP
Message text	Deleted OSPF policy application: $1
Variable fields	$1: OSPF policy application information.
Example	Deleted OSPF policy application: { "OspfPolicyApplyConfig": { "id":110dceec-f498-4316-ac5667228e6bfa9e, "object":0, "sourceName":"vln", "ospfPolicyId":5a53d2e1-e939-40e1-b7ce-2eb0ef761010, "tenantId":4607eb06-0b5d-45b0-bf13-6d94344ac3df, "policyName":"ospf_policy", "networkId":09d0c494-28f8-4ca4-9d77-76d459f5c189, "vni":222, "ospfAreaId":"0.0.0.0", "description":"null", "ospfInterfacePolicyId":a20ea450-2628-42b8-9d8e-ade68c2eab14, "interfaceName":"interface_policy", "deviceInterface":"null", "instanceId":null, "ospfProcessConfigs":[], "routerId":null, "ipVersion":4 } }
Explanation	An OSPF policy application was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · You have no privilege to perform this operation. · The specified OSPF or OSPFv3 policy application does not exist.

Create OSPFv3 policy application

Keyword	CREATE_OSPFV3_POLICY_APPLY_OP
Message text	Created OSPFv3 policy application: $1
Variable fields	$1: OSPFv3 policy application information.
Example	Created OSPFv3 policy application:[{ "OspfPolicyApplyConfig":{ "id":7532bc3a-e159-46c4-a196-1a55fc76e892, "object":0, "sourceName":"v-link002", "ospfPolicyId":84fa17a0-da14-47a9-9e5d-27f5ea517895, "tenantId":2755b0fd-0bff-4636-9035-3316fcc1d096, "policyName":"999999999999999999", "networkId":c19ba35e-c2c8-47d0-a591-7a08e7599aa3, "vni":449, "ospfAreaId":"99.99.3.5", "description":"null", "ospfInterfacePolicyId":da5bc2d7-26d7-4c43-b793-a339bb68c9dd, "interfaceName":"2543254", "deviceInterface":"null", "instanceId":null, "ospfProcessConfigs":[], "routeId":99.55.23.33, "ipVersion":6 } }]
Explanation	An OSPFv3 policy application was created.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid JSON format. · Invalid parameter. · Invalid tenant ID. · Please specify an OSPF policy UUID. · The ospfv3 policy apply already exists. · Invalid OSPF policy UUID. · Invalid interface policy UUID. · Invalid OSPF process ID. · The process ID already exists. · You cannot bind an OSPF policy to a vNetwork generated upon PBR service chain creation. · You have no privilege to perform this operation. · IP version mismatch. · Invalid router ID.

Update OSPFv3 policy application

Keyword	UPDATE_OSPFV3_POLICY_APPLY_OP
Message text	Updated OSPFv3 policy application: $1
Variable fields	$1: OSPFv3 policy application information.
Example	Updated OSPFv3 policy application:{ "OspfPolicyApplyConfig":{ "id":e68226e8-ee93-42f0-b3ae-b634a65911d0, "object":1, "sourceName":"zsx_ext", "ospfPolicyId":4afc27dd-d6b7-4b8d-98da-681a8733d4ca, "tenantId":null, "policyName":"all-null-ospfv333", "networkId":5ef0f18b-2fe2-46c0-8d97-59751ade49cb, "vni":1300, "ospfAreaId":"12.13.14.15", "description":"null", "ospfInterfacePolicyId":47eeb4c6-ca60-4355-90c0-0d187b2ef6d0, "interfaceName":"003", "deviceInterface":"null", "instanceId":1, "ospfProcessConfigs":[ { "OspfProcessConfig":{ "id":"031a2e80-e146-4bef-8a8e-877ab9ceacdc", "deviceId":"e46508d9-a119-4982-a1ec-7bfb1c50f360", "instanceId":2 } } } ], "routeId":29.3.3.32, "ipVersion":6 } }
Explanation	An OSPFv3 policy application was edited.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid JSON format. · Invalid parameter. · The ospfv3 policy apply already exists. · Invalid OSPF policy UUID. · Invalid interface policy UUID. · The specified OSPF or OSPFv3 policy application does not exist. · You have no privilege to perform this operation. · IP version mismatch. · Invalid router ID.

Delete OSPFv3 policy application

Keyword	DELETE_OSPFV3_POLICY_APPLY_OP
Message text	Deleted OSPFv3 policy application: $1
Variable fields	$1: OSPFv3 policy application information.
Example	Deleted OSPFv3 policy application: { "OspfPolicyApplyConfig": { "id":110dceec-f498-4316-ac5667228e6bfa9e, "object":0, "sourceName":"vln", "ospfPolicyId":5a53d2e1-e939-40e1-b7ce-2eb0ef761010, "tenantId":4607eb06-0b5d-45b0-bf13-6d94344ac3df, "policyName":"ospfv3_policy", "networkId":09d0c494-28f8-4ca4-9d77-76d459f5c189, "vni":222, "ospfAreaId":"0.0.0.0", "description":"null", "ospfInterfacePolicyId":a20ea450-2628-42b8-9d8e-ade68c2eab14, "interfaceName":"interface_policy", "deviceInterface":"null", "instanceId":null, "ospfProcessConfigs":[], "routerId":"3.3.3.3", "ipVersion":6 } }
Explanation	An OSPFv3 policy application was deleted.
Possible failure causes	· The controller is not the active leade. · Configuration recovery is in progress. · Unknown internal server error. · The specified OSPF or OSPFv3 policy application does not exist. · You have no privilege to perform this operation.

Update policy application

Keyword	UPDATE_POLICY_APPLY_OP
Message text	Updated policy application: $1
Variable fields	$1: Policy application information.
Example	Updated policy application:{ "OspfPolicyApplyConfig":{ "id":e68226e8-ee93-42f0-b3ae-b634a65911d0, "object":1, "sourceName":"zsx_ext", "ospfPolicyId":4afc27dd-d6b7-4b8d-98da-681a8733d4ca, "tenantId":null, "policyName":"all-null-ospfv333", "networkId":5ef0f18b-2fe2-46c0-8d97-59751ade49cb, "vni":1300, "ospfAreaId":"12.13.14.15", "description":"null", "ospfInterfacePolicyId":47eeb4c6-ca60-4355-90c0-0d187b2ef6d0, "interfaceName":"003", "deviceInterface":"null", "instanceId":1, "ospfProcessConfigs":[ { "OspfProcessConfig":{ "id":"031a2e80-e146-4bef-8a8e-877ab9ceacdc", "deviceId":"e46508d9-a119-4982-a1ec-7bfb1c50f360", "instanceId":2 } } } ], "routeId":29.3.3.32, "ipVersion":6 } }
Explanation	A policy application was edited.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid JSON format. · Invalid parameter. · The ospfv3 policy apply already exists. · Invalid OSPF policy UUID. · Invalid interface policy UUID. · The specified OSPF or OSPFv3 policy application does not exist. · You have no privilege to perform this operation. · IP version mismatch. · Invalid router ID.

Delete policy application

Keyword	DELETE_POLICY_APPLY_OP
Message text	Deleted policy application: $1
Variable fields	$1: UUID of the policy application.
Example	Deleted policy application: 110dceec-f498-4316-ac5667228e6bfa9e
Explanation	An policy application was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · The specified OSPF or OSPFv3 policy application does not exist. · You have no privilege to perform this operation.

Create configuration audit task

Keyword	CREATE_CONFIG_AUDIT_OP
Message text	Created configuration audit task: $1
Variable fields	$1: Configuration audit task information.
Example	Created configuration audit task: [ ID:[39811f54-30fc-4519-8eed-ffbc52afb96b] Name:[11] Description:[description] Object type:[Fabric] Audit At:[ Time: [12]:[30]:[00] Date: Days:[] Months:[] Days of week:[?]] Objects to audit:[ { Fabric ID:[eca72cea-91ea-4177-95fd-923e0552ac69] Fabric name:[fabric1] } ] Enabled:[true]]
Explanation	A configuration audit task was added.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid JSON format. · Invalid parameter. · Invalid audited object type. · Invalid audit task UUID. · Please specify fabric UUIDs or device UUIDs. · Some device UUIDs do not belong to the specified fabric. · Check the device name and device UUID pairs for mismatches. · Some of the specified devices do not exist. · Cannot specify device UUIDs or names when the audited object type is fabric. · Some of the specified fabrics do not exist. · Check the fabric name and fabric UUID pairs for mismatches. · The audit task UUID already exists. · Invalid Cron expression parameters. · The audit task failed to start the scheduler. · Please specify Cron expression parameters. · Duplicated devices exist. · You have no privilege to perform this operation.

Update configuration audit task

Keyword	UPDATE_CONFIG_AUDIT_OP
Message text	Updated configuration audit task: $1
Variable fields	$1: Configuration audit task information.
Example	Updated configuration audit task: ID:[39811f54-30fc-4519-8eed-ffbc52afb96b] Name:[11] Description:[description] Object type:[Fabric] Audit At:[ Time: [12]:[30]:[00] Date: Days:[?] Months:[*] Days of week:[2,3]] Objects to audit:[ { Fabric ID:[eca72cea-91ea-4177-95fd-923e0552ac69] Fabric name:[fabric1] } ] Enabled:[true]
Explanation	A configuration audit task was edited.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid JSON format. · Invalid parameter. · Invalid audited object type. · Invalid audit task UUID. · Please specify fabric UUIDs or device UUIDs. · Some device UUIDs do not belong to the specified fabric. · Check the device name and device UUID pairs for mismatches. · Some of the specified devices do not exist. · Cannot specify device UUIDs or names when the audited object type is fabric. · Some of the specified fabrics do not exist. · Check the fabric name and fabric UUID pairs for mismatches. · The audit task UUID already exists. · Invalid Cron expression parameters. · The audit task failed to start the scheduler. · Please specify Cron expression parameters. · The configuration audit task does not exist. · Duplicated devices exist. · You have no privilege to perform this operation.

Delete configuration audit task

Keyword	DELETE_CONFIG_AUDIT_OP
Message text	Deleted configuration audit task: $1
Variable fields	$1: UUID of the configuration audit task.
Example	Deleted configuration audit task: 39811f54-30fc-4519-8eed-ffbc52afb96b
Explanation	A configuration audit task was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid audit task UUID. · The configuration audit task does not exist. · You have no privilege to perform this operation.

Execute one-off configuration audit task

Keyword	PERFORM_CONFIG_AUDIT_OP
Message text	Executed one-off configuration audit task: $1
Variable fields	$1: One-off configuration audit task information.
Example	Executed one-off configuration audit task: ID:[88b8634e-917e-41c1-9318-02035944408d] Object type:[Fabric] Objects to audit:[ { Fabric ID:[eca72cea-91ea-4177-95fd-923e0552ac69] Fabric name:[fabric1] } ] Enabled:[true]
Explanation	Executed an one-off configuration audit task.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid JSON format. · Invalid parameter. · Invalid audited object type. · Please specify fabric UUIDs or device UUIDs. · Some device UUIDs do not belong to the specified fabric. · Check the device name and device UUID pairs for mismatches. · Some of the specified devices do not exist. · Cannot specify device UUIDs or names when the audited object type is fabric. · Some of the specified fabrics do not exist. · Check the fabric name and fabric UUID pairs for mismatches. · The audit task UUID already exists. · Invalid Cron expression parameters. · The audit task failed to start the scheduler. · Please specify Cron expression parameters. · You have no privilege to perform this operation.

Manually trigger periodic configuration audit task once

Keyword	TRIGGER_CONFIG_AUDIT_OP
Message text	Manually triggered periodic configuration audit task once: $1
Variable fields	$1: Periodic configuration audit task information.
Example	Manually triggered periodic configuration audit task once: 39811f54-30fc-4519-8eed-ffbc52afb96b
Explanation	Manually triggered a periodic configuration audit task once.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid JSON format. · Invalid parameter. · Invalid audit task UUID. · The configuration audit task does not exist. · You have no privilege to perform this operation.

Create third-party service device

Keyword	CREATE_THIRD_PARTY_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: [49023bc8-5aa2-454d-80f5-4ee9d8ddacca] Name: [ttt] Description: [] Tenant ID: [ffffffff-0000-0000-0000-000000000001] Ingress VXLAN: [44] Ingress IP address: [3.3.3.3] Ingress IPv6 address: [5:0:0:0:0:0:0:5] Egress VXLAN: [45] Egress IP address: [3.5.3.3] Egress IPv6 address: [6:0:0:0:0:0:0:5] Access type: [auto] In use: [false] VIP: [ 3.4.4.4 4:0:0:0:0:0:0:4 ] SNAT IP: [ 3.6.4.4 9:0:0:0:0:0:0:4 ]
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. · Invalid parameter. · The ID of the third party service device already exists. · The name of the third party service device already exists. · Failed to create third party service device because the ingress port is invalid. · Failed to create third party service device because the egress port is invalid. · Failed to create third party service device because either ingress or egress port is in use. · 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 ingress vPort ID is required. · The egress vPort ID is required. · The ingress port does not exist. · The egress port does not exist. · The VXLAN ID is invalid or out of range. · When the ingress virtual port has the same VXLAN ID and IP address settings as the egress virtual port, you can't set vip_list and snat_ip_list. · Invalid IP address. · Make sure the egress and ingress vPort IP addresses use the same IP version. · Make sure the VIPs and the egress and ingress vPort IP addresses use the same IP version. · Make sure the SNAT IP addresses and the egress and ingress vPort IP addresses use the same IP version. · Make sure the VXLAN IDs for the ingress and egress vPorts are different when the third-party service device is deployed in two-arm mode. · Make sure the IP addresses for the ingress and egress vPorts are different when the third-party service device is deployed in two-arm mode. · You have no privilege to perform this operation.

Update third-party service device

Keyword	UPDATE_THIRD_PARTY_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: [49023bc8-5aa2-454d-80f5-4ee9d8ddacca] Name: [ttt1] Description: [] Tenant ID: [ffffffff-0000-0000-0000-000000000001] Ingress VXLAN: [44] Ingress IP address: [3.3.3.3] Ingress IPv6 address: [5:0:0:0:0:0:0:5] Egress VXLAN: [45] Egress IP address: [3.5.3.3] Egress IPv6 address: [6:0:0:0:0:0:0:5] Access type: [auto] In use: [true] VIP: [ 3.4.4.4 4:0:0:0:0:0:0:4 ] SNAT IP: [ 3.6.4.4 9:0:0:0:0:0:0:4 ]
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. · Invalid name. · Invalid description. · Invalid parameter. · The third party service device tenant id is read only. · The access mode field is read only. · The third party service device ingress ip is read only. · The third party service device ingress port is read only. · The third party service device ingress vxlan is read only. · The third party service device egress ip is read only. · The third party service device egress port is read only. · The third party service device egress vxlan is read only. · The third party service device inuse is read only. · The VIP list cannot be modified. · The SNAT IP list cannot be modified. · You have no privilege to perform this operation.

Delete third-party service device

Keyword	DELETE_THIRD_PARTY_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: third
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. · Failed to delete the third party service device because it is used by a third party service function. · You have no privilege to perform this operation.

Resource bind NQA

Keyword	START_RESOURCE_BIND_NQA_OP
Message text	Started resource bind nqa, resourceid : $1
Variable fields	$1: Service resource ID.
Example	Started resource bind nqa, resourceid : b1e045fd-9de1-4347-8dae-30bb14b68a78
Explanation	Bound a service resource to an NQA profile.
Possible failure causes	· The specified NQA profile does not exist. · Cannot bind the service resource to an NQA profile. The gateway member in the service resource has been bound to a track entry. · You can bind a service resource to only one NQA profile. · The specified NQA profile has been bound to another service resource. · The specified NQA profile has been bound to another external network. · You cannot bind the service resource to an NQA profile when the auto NQA profile mode is used.

Resource unbind NQA

Keyword	START_RESOURCE_UNBIND_NQA_OP
Message text	Started resource unbind nqa, resourceid : $1
Variable fields	$1: Service resource ID.
Example	Started resource unbind nqa, resourceid :b1e045fd-9de1-4347-8dae-30bb14b68a78
Explanation	Unbound a service resource from an NQA profile.
Possible failure causes	Please specify an NQA profile for the service resource.

Create port PVIDs

Keyword	CREATE_PORTPVID_OP
Message text	Created interface and PVID mapping: $1
Variable fields	$1: Interface and PVID mapping information.
Example	Created interface and PVID mapping: [ ID: 20035139-964d-458a-9cd2-138cc15dd06f Device ID: 9790e274-423f-40ed-b502-210a35aab9bb Device name: 100.115 Port name: GigabitEthernet1/0/4 Port number: 0x5 Port PVID: 78 Data source:DEFAULT Port VLAN domain ID:null, ID: f3783346-0601-45af-bb1f-71d3b215d537 Device ID: 9790e274-423f-40ed-b502-210a35aab9bb Port name: GigabitEthernet1/0/12 Port number: 0xd Port PVID: 78 Data source:DEFAULT Port VLAN domain ID:null]
Explanation	An interface and PVID mapping was created.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid JSON format. · You have no privilege to perform this operation. · Invalid parameter. · The device_ID cannot be null. · Please specify interfaces. · Some of the specified PVIDs are invalid or out of range. · Please specify PVIDs. · The device type doesn't match. · The device to which the interface belongs or the device to which a bound interface belongs is inactive. · Non-VTEP interfaces exist. · Duplicated interfaces exist. · You cannot edit the interface and PVID mappings for bare metal servers. · The device does not exist.

Update port PVIDs

Keyword	MODIFY_PORTPVID_OP
Message text	Edited interface and PVID mapping: $1
Variable fields	$1: Interface and PVID mapping information.
Example	Edited interface and PVID mapping: ID: a94ff6ba-be13-4d31-a19b-0f0c76a8856b Device ID: 89aa65a3-13f5-41be-aa26-823ef0ab976d Port name: Route-Aggregation200 Port number: 0x51d Port PVID: 2312 Data source:DEFAULT Port VLAN domain ID:null
Explanation	An interface and PVID mapping was edited.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid JSON format. · Invalid parameter. · You have no privilege to perform this operation. · The device_ID cannot be null. · Please specify interfaces. · Some of the specified PVIDs are invalid or out of range. · Please specify PVIDs. · The device type doesn't match. · The device to which the interface belongs or the device to which a bound interface belongs is inactive. · Non-VTEP interfaces exist. · Duplicated interfaces exist. · The specified interface and PVID mapping does not exist. · You cannot edit the interface and PVID mappings for bare metal servers. · The device does not exist.

Delete port PVIDs

Keyword	DELETE_PORTPVID_OP
Message text	Deleted interface and PVID mapping: $1
Variable fields	$1: Interface and PVID mapping information.
Example	Deleted interface and PVID mapping: Deleted [3] interface and PVID mappings from device [leaf1].
Explanation	Bulk deleted interface and PVID mappings.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid JSON format. · Invalid parameter. · You have no privilege to perform this operation. · Please specify PVIDs. · The device_ID cannot be null. · Please specify interfaces. · You cannot delete the interface and PVID mappings for bare metal servers on the current page. · You cannot delete the interface and PVID mappings for service chains on the current page. · When bulk deleting interface and PVID mappings, you cannot both delete all mappings of a device and delete the specific mappings of the device. · The specified interface and PVID mapping does not exist.

Delete port PVID

Keyword	DELETE_PORTPVID_OP
Message text	Deleted interface and PVID mapping: $1
Variable fields	$1: UUID of the interface and PVID mapping.
Example	Deleted interface and PVID mapping: ID : [a02c1e04-2e9c-4488-9da9-752e9578d0cc]
Explanation	An interface and PVID mapping was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid parameter. · You have no privilege to perform this operation. · Please specify PVIDs. · The device_ID cannot be null. · Please specify interfaces. · You cannot delete the interface and PVID mappings for bare metal servers on the current page. · You cannot delete the interface and PVID mappings for service chains on the current page. · The specified interface and PVID mapping does not exist.

Clear auto discovered device list

Keyword	CLEAR_AUTO_DISCOVERED_DEVICE_OP
Message text	User $1 cleared the auto-discovered device list.
Variable fields	$1: Username.
Example	User admin cleared the auto-discovered device list.
Explanation	A user cleared devices in the auto-discovered device list.
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. · You have no privilege to perform this operation.

Refreshed lock configuration successfully

Keyword	REFRESH_DEV_LOCK_SUCC_OP
Message text	Refreshed lock configuration for $1 devices successfully, UUIDs of devices: $2
Variable fields	$1: Number of devices. $2: UUIDs of the devices.
Example	Refreshed lock configuration for 2 devices, UUIDs of devices: [be111c50-493c-42de-bf9a-20e7cb7cdadb, f7554d87-1a30-4e47-83ec-f1d3a290bc33]
Explanation	Refreshed lock configuration for multiple devices successfully.
Possible failure causes	N/A

Failed to refresh lock configuration because of parameter errors

Keyword	REFRESH_DEV_LOCK_FAIL_PARAMETER_OP
Message text	Failed to refresh lock configuration for $1 devices: $2
Variable fields	$1: Number of devices. $2: UUIDs of the devices.
Example	Failed to refresh lock configuration for 2 devices: [be111c50-493c-42de-bf9a-20e7cb7cdadb, f7554d87-1a30-4e47-83ec-f1d3a290bc33]
Explanation	Failed to refresh lock configuration for multiple devices.
Possible failure causes	· The device is inactive. · Invalid parameter. · The device_ID cannot be null. · The physical access device doesn't exist. · Invalid JSON format. · The device does not support lock management. · The network element is being deleted or being removed from the border device group or being removed from the fabric. · The controller does not contain lock data about the device · You have no privilege to perform this operation.

Failed to refresh lock configuration because of module service conflicts

Keyword	REFRESH_DEV_LOCK_FAIL_BUSINESS_OP
Message text	Failed to refresh lock configuration for device: $1
Variable fields	$1: UUID of the device.
Example	Failed to refresh lock configuration for device: 965e8b6a-c651-4d71-9cda-7cdedc30f41d
Explanation	Failed to refresh lock configuration for a device because of module service conflicts.
Possible failure causes	· The device_ID cannot be null. · The physical access device doesn't exist. · The controller does not contain lock data about the device.

Locked multiple devices in bulk successfully

Keyword	LOCK_DEV_LOCK_SUCC_OP
Message text	Locked $1 devices in bulk successfully, UUIDs of devices: $2
Variable fields	$1: Number of devices. $2: UUIDs of the devices.
Example	Locked 2 devices in bulk successfully, UUIDs of devices: [be111c50-493c-42de-bf9a-20e7cb7cdadb, f7554d87-1a30-4e47-83ec-f1d3a290bc33]
Explanation	Locked multiple devices in bulk successfully.
Possible failure causes	N/A

Failed to lock multiple devices in bulk because of parameter errors

Keyword	LOCK_DEV_LOCK_FAIL_PARAMETER_OP
Message text	Failed to lock $1 devices: $2
Variable fields	$1: UUIDs of the devices.
Example	Failed to lock 2 devices: [be111c50-493c-42de-bf9a-20e7cb7cdadb, f7554d87-1a30-4e47-83ec-f1d3a290bc33]
Explanation	Failed to lock multiple devices.
Possible failure causes	· The device is inactive. · Invalid parameter. · The device_ID cannot be null. · The physical access device doesn't exist. · Invalid JSON format. · The device does not support lock management. · The network element is being deleted or being removed from the border device group or being removed from the fabric. · The controller does not contain lock data about the device. · Please do not select locked devices. · You have no privilege to perform this operation.

Failed to lock device because of module service conflicts

Keyword	LOCK_DEV_LOCK_FAIL_BUSINESS_OP
Message text	Failed to lock device: $1
Variable fields	$1: UUID of the device.
Example	Failed to lock device: 965e8b6a-c651-4d71-9cda-7cdedc30f41d
Explanation	Failed to lock a device because of module service conflicts.
Possible failure causes	· The device_ID cannot be null. · The physical access device doesn't exist. · The controller does not contain lock data about the device.

Unlocked multiple devices in bulk successfully

Keyword	UNLOCK_DEV_LOCK_SUCC_OP
Message text	Unlocked $1 devices in bulk successfully, UUIDs of devices: $2
Variable fields	$1: Number of devices. $2: UUIDs of the devices.
Example	Unlocked 2 devices in bulk successfully, UUIDs of devices: [be111c50-493c-42de-bf9a-20e7cb7cdadb, f7554d87-1a30-4e47-83ec-f1d3a290bc33]
Explanation	Unlocked multiple devices in bulk successfully.
Possible failure causes	N/A

Failed to unlock multiple devices in bulk because of parameter errors

Keyword	UNLOCK_DEV_LOCK_FAIL_PARAMETER_OP
Message text	Failed to unlock $1 devices : $2
Variable fields	$1: UUIDs of the devices.
Example	Failed to unlock 2 devices: [be111c50-493c-42de-bf9a-20e7cb7cdadb, f7554d87-1a30-4e47-83ec-f1d3a290bc33]
Explanation	Failed to unlock multiple devices in bulk because of parameter errors.
Possible failure causes	· The device is inactive. · Invalid parameter. · The device_ID cannot be null. · The physical access device doesn't exist. · Invalid JSON format. · The device does not support lock management. · The network element is being deleted or being removed from the border device group or being removed from the fabric. · The controller does not contain lock data about the device. · Please do not select unlocked devices. · You have no privilege to perform this operation.

Failed to unlock device because of module service conflicts

Keyword	UNLOCK_DEV_LOCK_FAIL_BUSINESS_OP
Message text	Failed to unlock device: $1
Variable fields	$1: UUID of the device.
Example	Failed to unlock device: 965e8b6a-c651-4d71-9cda-7cdedc30f41d
Explanation	Failed to unlock a device because of module service conflicts.
Possible failure causes	· The device_ID cannot be null. · The physical access device doesn't exist. · The controller does not contain lock data about the device.

Create DRNI information

Keyword	CREATE_MLAG_INFO_OP
Message text	Created DRNI information: $1
Variable fields	$1: DR system information.
Example	Created DRNI information: id: [26c3cb3b-83c9-48d3-a34d-a8fb9a2a76ed] serialNumberA: [11] portAList: null serialNumberB: [111] portBList: null usage: [no_peer_link] borderAccess: [false]
Explanation	A DR system was created.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid JSON format. · You have no privilege to perform this operation. · Invalid parameter. · The serial number cannot be empty. · Invalid serial number. · Please specify different serial numbers for Device A and Device B. · Invalid port name. · If the IPL is an Ethernet aggregate link, you must configure the port names. · Duplicated Device port. · The port has been specified for DRNI use. · Please specify a usage. · Invalid usage. · The specified devices already have DRNI information entries used in the other scene. You must select the same scene for all DRNI information entries for the specified devices. · Invalid ID. · The serial number has been configured on another DR system. · If the IPL is a VXLAN tunnel, you must leave the port names empty or configure the port names for both devices.

Update DRNI information

Keyword	UPDATE_MLAG_INFO_OP
Message text	Updated DRNI information: $1
Variable fields	$1: DR system information.
Example	Updated DRNI information: id: [26c3cb3b-83c9-48d3-a34d-a8fb9a2a76ed] serialNumberA: [11] portAList: null serialNumberB: [1111] portBList: null usage: [no_peer_link] borderAccess: [false]
Explanation	A DR system was edited.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid JSON format. · Invalid parameter. · You have no privilege to perform this operation. · The serial number cannot be empty. · Invalid serial number. · Please specify different serial numbers for Device A and Device B. · Invalid port name. · If the IPL is an Ethernet aggregate link, you must configure the port names. · Duplicated Device port. · The port has been specified for DRNI use. · Please specify a usage. · Invalid usage. · The specified devices already have DRNI information entries used in the other scene. You must select the same scene for all DRNI information entries for the specified devices · Invalid ID. · The serial number has been configured on another DR system. · If the IPL is a VXLAN tunnel, you must leave the port names empty or configure the port names for both devices.

Delete DRNI information

Keyword	DELETE_MLAG_INFO_OP
Message text	Deleted DRNI information: $1
Variable fields	$1: DR system information.
Example	Deleted DRNI information: id: [0e2b1d65-9a00-44ff-9fc6-5f2215a1ecc0] serialNumberA: [1] portAList: null serialNumberB: [2] portBList: null usage: [no_peer_link]
Explanation	A DR system was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid JSON format. · Invalid parameter. · You have no privilege to perform this operation. · The specified resource is not found.

Batch delete DRNI informations

Keyword	BATCH_DELETE_MLAG_INFO_OP
Message text	Batch deleted DRNI informations: $1
Variable fields	$1: DR system list.
Example	Batch deleted DRNI informations: [ id: [69eb6554-b4eb-4c5d-a426-5f5f26630117] serialNumberA: [3] portAList: [tem1/1/1/12] serialNumberB: [4] portBList: [tem1/1/1/12] usage: [has_peer_link] borderAccess: [false] id: [26c3cb3b-83c9-48d3-a34d-a8fb9a2a76ed] serialNumberA: [11] portAList: null serialNumberB: [1111] portBList: null usage: [no_peer_link] borderAccess: [false] ]
Explanation	Deleted multiple DR systems in bulk.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · Invalid parameter. · You have no privilege to perform this operation.

Create DRNI routed IPL

Keyword	ACTION_CREATE_ROUTER_ESCAPE_OP
Message text	Created DRNI routed IPL: $1
Variable fields	$1: DRNI routed IPL information.
Example	Created DRNI routed IPL: [DRNI routed IPL: { ID:” 555a3407-73d4-4614-8ce1-346525a14924”, Name:"test1", Description:"", Router ID:"12faf8ab-88d8-4ae8-bd52-426d47860607", VLAN ID:44, Device list:[ DRNI routed IPL device:{ Device ID:"662ee793-51f0-4ccc-a38c-fc184b62fca1", IPv4 address:"1.1.1.1/31", IPv6 address:"" }, DRNI routed IPL device: { Device ID:"3f7686cc-f1ea-4983-867e-052440aa83f4", IPv4 address:"1.1.1.2/31", IPv6 address:"" }] } ]
Explanation	A DRNI routed IPL 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. · You have no privilege to perform this operation. · You must specify two devices in the device_list. · The device_list contains invalid device IDs. · The device_list must contain a minimum of one IP version. · The IP addresses of the two devices in the device_list do not match. · The VLAN ID range is 1 to 4094. · Invalid router_id value. · Invalid description. · Invalid IP address. · Invalid IPv6 address. · Invalid Mask. · The DRNI routed IPL ID is invalid. · When you set up a DRNI routed IPL for a vRouter, make sure no DRNI routed IPL exists on the specified devices. · The device configuration on the controller is inconsistent with the actual device configuration. · The device type is not supported. · The devices at the two ends of the DRNI routed IPL cannot have the same IP address. · The vRouter doesn't exist. · The VLAN ID cannot be identical to a segment ID or in a VLAN ID pool for a tenant carrier network. · The device is not a border gateway. To specify a border device, make sure it is in a border device group whose position is border gateway. · You must configure the same mask for the local and peer devices. · The device does not exist. · The IP addresses used for setting up the DRNI routed IPL must belong to the same subnet. · If the device has multiple DRNI routed IPLs, make sure the VLAN IDs configured for the IPLs are unique. · The IP addresses used for setting up the DRNI routed IPL must belong to the same subnet. · The device does not exist.

Update DRNI routed IPL

Keyword	ACTION_UPDATE_ROUTER_ESCAPE_OP
Message text	Updated DRNI routed IPL: $1
Variable fields	$1: DRNI routed IPL information.
Example	Updated DRNI routed IPL: DRNI routed IPL: { ID:” 555a3407-73d4-4614-8ce1-346525a14924” Name:"test1", Description:"", Device list:[ DRNI routed IPL device:{ Device ID:"662ee793-51f0-4ccc-a38c-fc184b62fca1", IPv4 address:"1.1.1.1/31", IPv6 address:"" }, DRNI routed IPL device: { Device ID:"3f7686cc-f1ea-4983-867e-052440aa83f4", IPv4 address:"1.1.1.2/31", IPv6 address:"" }] }
Explanation	A DRNI routed IPL was edited.
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. · You have no privilege to perform this operation. · Invalid name. · Invalid description. · Invalid IP address. · Invalid IPv6 address. · Invalid Mask. · You must specify two devices in the device_list. · The device_list contains invalid device IDs. · The device_list must contain a minimum of one IP version. · The IP addresses of the two devices in the device_list do not match. · The VLAN ID range is 1 to 4094. · Invalid router_id value. · The DRNI routed IPL ID is invalid. · The DRNI routed IPL does not exist. · The device_list must contain a minimum of one IP version. · The IP addresses of the two devices in the device_list do not match. · When you set up a DRNI routed IPL for a vRouter, make sure no DRNI routed IPL exists on the specified devices. · The device configuration on the controller is inconsistent with the actual device configuration. · The device type is not supported. · The devices at the two ends of the DRNI routed IPL cannot have the same IP address. · he VLAN ID cannot be identical to a segment ID or in a VLAN ID pool for a tenant carrier network. · The device is not a border gateway. To specify a border device, make sure it is in a border device group whose position is border gateway. · You must configure the same mask for the local and peer devices. · The IP addresses used for setting up the DRNI routed IPL must belong to the same subnet. · If the device has multiple DRNI routed IPLs, make sure the VLAN IDs configured for the IPLs are unique. · The device does not exist.

Delete DRNI routed IPL

Keyword	ACTION_DELETE_ROUTER_ESCAPE_OP
Message text	Deleted DRNI routed IPL $1.
Variable fields	$1: DRNI routed IPL ID.
Example	Deleted DRNI routed IPL 747cf8c8-8ab4-4a02-9550-0878dcc4ca5a.
Explanation	A DRNI routed IPL 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. · You have no privilege to perform this operation.

Create BGP Network

Keyword	ACTION_CREATE_BGP_NETWORK_OP
Message text	Create BGP Network: $1
Variable fields	$1: BGP network information.
Example	Create BGP Network:[BGP Network:{ ID: c4cce82c-980d-45b6-935d-274d08221a63 CIDR: 43.4.4.0/24 Router ID: 237fa40d-7118-4502-a985-81c1decf5271 IP Version: IPv4 Device list: [[BGP Network device: { Device ID: 6973d2a2-a736-45d6-9630-34879b960cf9 } ]] }]
Explanation	A BGP network 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. · The BGP local network UUID is invalid. · You must specify a vRouter UUID for the BGP local network. · The vRouter UUID for the BGP local network is invalid. · The device list contains devices without a UUID. · Devices with invalid UUIDs exist. · Devices with the same UUID exist. · The specified device does not exist. · Only border devices and access devices are supported. · You must specify an IP version for the BGP local network. · The IP version of the BGP local network is invalid. · You must specify a CIDR mask for the BGP local network. · The BGP local network and its CIDR mask must be the same IP version. · A BGP local network already exists with the specified UUID. · The vRouter for the BGP local network does not exist. · The vRouter has BGP local networks with the same CIDR mask.

Update BGP Network

Keyword	ACTION_UPDATE_BGP_NETWORK_OP
Message text	Update BGP Network:$1
Variable fields	$1: BGP network information.
Example	Update BGP Network:BGP Network:{ ID: b15a0329-644f-494e-ad86-0b66b33f8adf CIDR: 9::7/128 Router ID: 237fa40d-7118-4502-a985-81c1decf5271 IP Version: IPv6 Device list: [[BGP Network device: { Device ID: 6973d2a2-a736-45d6-9630-34879b960cf9 } , BGP Network device: { Device ID: e8754b47-2759-4fc6-8627-a4804b20ba4a } ]] }
Explanation	A BGP network was updated.
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. · You have no privilege to perform this operation. · The device list contains devices without a UUID. · Devices with invalid UUIDs exist. · Devices with the same UUID exist. · The specified BGP local network UUID does not exist. · The specified device does not exist. · Only border devices and access devices are supported. · The CIDR mask, IP version, and vRouter UUID for a BGP local network cannot be edited.

Delete BGP Network

Keyword	ACTION_DELETE_BGP_NETWORK_OP
Message text	Delete BGP Network: $1.
Variable fields	$1: BGP network ID.
Example	Delete BGP Network:29e3d995-13cd-417e-9d21-bb0e4c419f49
Explanation	A BGP network was deleted.
Possible failure causes	· Invalid license. · The service is disabled. · The controller is not the active leader. · Configuration recovery is in progress. · Unknown internal server error. · You have no privilege to perform this operation.

NEYANGM

This section contains network element YANG manager messages.

Download YANG files

Keyword	DOWNLOAD_YANG_FILES_OP
Message text	Download YANG files: $1
Variable fields	$1: Network element ID.
Example	Download YANG files: NE ID: 84f2ab2c-fd56-48f1-9030-bf1c6297d644
Explanation	The YANG files of a network element were downloaded.
Possible failure causes	· The operation requires the administrator privilege. · The controller is not the active leader. · The controller is obtaining the YANG files. · You have no privilege to perform this operation.

Get YANG files from NE

Keyword	GET_YANG_FILES_FROM_NE_OP
Message text	Get YANG files from NE: $1
Variable fields	$1: Network element ID.
Example	Get YANG files from NE: NE ID: 84f2ab2c-fd56-48f1-9030-bf1c6297d644
Explanation	The YANG files of a network element were synchronized.
Possible failure causes	· The operation requires the administrator privilege. · The controller is not the active leader. · The controller is obtaining the YANG files. · You have no privilege to perform this operation.

Set YANG files identifier

Keyword	SET_YANG_FILES_IDENTIFIER_OP
Message text	Set YANG files identifier: $1
Variable fields	$1: YANG file identifier.
Example	Set YANG files identifier: NE ID: 84f2ab2c-fd56-48f1-9030-bf1c6297d644 Identifier: aaa
Explanation	An identifier was configured for the YANG files of a network element.
Possible failure causes	· The operation requires the administrator privilege. · The controller is not the active leader. · You have no privilege to perform this operation.

NGFWM

This section contains NGFW manager messages.

Add device

Keyword	ADD_DEVICE_OP
Message text	Added device: $1
Variable fields	$1: Device information.
Example	Added device: ID: 8dfb8b46-50d9-46c1-87c4-7aac7976ef5b Name: device1 IP: 192.168.34.15 Port: 832 Username: admin Vendor: F5 Max. number of NGFW resources: 64 Data synchronization: ON
Explanation	A device was added.
Possible failure causes	· The device name already exists. · Invalid device port. · Invalid username. · Invalid password. · Invalid device name. · The IP address is used by a device. · Invalid IP address. · The device is unreachable or the username or password is incorrect. · The NGFWM service is not started. · The F5 service is not started. · Failed to add the F5 device. · Invalid vendor. · Server processing error. · Invalid JSON format. · The maximum number of NGFW resources must be an integer in the range of 1 to 2147483647. · Failed to establish an SSH connection between the controller and the device. · The controller is not the active leader. · You do not have privilege to perform the operation. · Configuration recovery is in progress. · You have no privilege to perform this operation. · The specified IP address of the L4-L7 device is a management IP address. Please select another IP address.

Update device

Keyword	UPDATE_DEVICE_OP
Message text	Updated device: $1
Variable fields	$1: Device configuration.
Example	Updated device: ID: 8dfb8b46-50d9-46c1-87c4-7aac7976ef5b Name: device1 IP: 192.168.34.15 Port: 832 Username: admin Max. number of NGFW resources: 64 Data synchronization: ON
Explanation	The configuration of a device was modified.
Possible failure causes	· The max. number of NGFW resources cannot be smaller than the number of NGFW resources existing on the device. · The maximum number of NGFW resources must be an integer in the range of 1 to 2147483647. · The configuration item does not exist. · The NGFWM service is not started. · Server processing error. · Invalid JSON format. · F5 devices do not support changing NETCONF passwords. · The controller is not the active leader. · You do not have privilege to perform the operation. · Configuration recovery is in progress. · You have no privilege to perform this operation.

Delete device

Keyword	DELETE_DEVICE_OP
Message text	Deleted device: $1
Variable fields	$1: Device name.
Example	Deleted device: DeviceName
Explanation	A device was deleted.
Possible failure causes	· The NGFWM service is not started. · Server processing error. · The configuration item does not exist. · Delete the NGFW resources on the device first. · Failed to delete the F5 device. · The device is in an F5 group and cannot be deleted. · The controller is not the active leader. · You do not have privilege to perform the operation. · Configuration recovery is in progress. · You have no privilege to perform this operation.

Start data synchronization on device

Keyword	START_NGFW_DEVICE_DATA_SYNCHRONIZATION_OP
Message text	Started data synchronization on device: $1
Variable fields	$1: Device name.
Example	Started data synchronization on device: m9k
Explanation	Data synchronization was started on a device.
Possible failure causes	· The NGFWM service is not started. · Server processing error. · Invalid JSON format. · F5 devices do not support this function. · The controller is not the active leader. · You do not have privilege to perform the operation. · Configuration recovery is in progress. · You have no privilege to perform this operation.

Start configuration audit on device

Keyword	START_NGFW_DEVICE_CONFIG_AUDIT_OP
Message text	Started configuration auditing on device: $1
Variable fields	$1: Device name.
Example	Started configuration auditing on device: m9k
Explanation	Configuration auditing was started on a device.
Possible failure causes	· The NGFWM service is not started. · Server processing error. · Invalid JSON format. · F5 devices do not support this function. · The controller is not the active leader. · You do not have privilege to perform the operation. · Configuration recovery is in progress. · You have no privilege to perform this operation.

Create template

Keyword	CREATE_TEMPLATE_OP
Message text	Created template: $1
Variable fields	$1: Template information.
Example	Created template: ID: 8dfb8b46-50d9-46c1-87c4-7aac7976ef5b Name: F1000tmp108 Device name: M9000 Security engine group ID: 3 Resource pool name: FW1 Template type: GatewayGroupFW Interface list: [ { Interface name: GigabitEthernet1/0/1 Interface type: Management } { Interface name: GigabitEthernet1/0/2 Interface type: Uplink } { Interface name: GigabitEthernet1/0/3 Interface type: Downlink } ] Extend setting: ip vpn-instance external_vpn ip vpn-instance external_vpn ospf 1 vpn-instance external_vpn import-route direct import-route static area 0.0.0.0 interface GigabitEthernet1/0/2 ip binding vpn-instance external_vpn ospf 1 area 0.0.0.0 ip route-static 0.0.0.0 0 1.2.2.254 interface loopback 2 ip binding vpn-instance external_vpn security-zone name SEC_ZONE_DEFAULT import interface GigabitEthernet1/0/1 Object-policy ip SEC_POLICY_DEFAULT rule 0 pass security-zone intra-zone default permit zone-pair security source Any destination Any object-policy apply ip SEC_POLICY_DEFAULT session synchronization enable nat port-block synchronization enable ipsec redundancy enable
Explanation	A template was created.
Possible failure causes	· Invalid template name. · The template name already exists. · Invalid parameter. · No available device. · Invalid security engine group ID. · Invalid resource pool name. · The security engine group is not bound to the resource pool. · Invalid interface name. · The NGFWM service is not started. · The IP address pool cannot contain broadcast, loopback, multicast, or reserved address. · An F5 device supports only gateway group LB resource templates. · Server processing error. · Invalid JSON format. · The IP address pool of the uplink interface has been used by another template. · An interface with the same name already exists for the interface type. · All interfaces in a template of this type cannot be configured with IP address pools. · For a template of this type, the uplink interface can be configured with IP address pools, and the management interface and downlink interface cannot be configured with IP address pools. · For a template of this type, the uplink interface cannot be configured with IP address pools, and the management interface and downlink interface must be configured with IP address pools. · The name of the management VRF must be management_vpn. · You can configure the management VRF name only for gateway group FW resource and gateway group LB resource templates. · The name of the cloud private-line interface to external network must be unique. · You can configure the vRouter interconnect interface and cloud private-line interface to external network only for gateway group FW resource templates. · The vRouter interconnect interface name cannot be the same as the downlink interface name. · Invalid resource pool type. · The F5 group does not exist. · The IP address pool does not exist. · The controller is not the active leader. · You do not have privilege to perform the operation. · Configuration recovery is in progress. · You have no privilege to perform this operation. · Invalid max concurrent context sessions. · Invalid session establishment rate. · Invalid throughput. · Invalid unit of measurement for throughput. · Invalid total firewall rules. · Invalid number of SSL VPN users. · Throughput and its unit of measurement do not match. · Invalid gateway IPv4 or IPv6 address. · To configure the gateway IPv4 address, you must first specify the IPv4 address pool and subnet mask. · To configure the gateway IPv6 address, you must first specify the IPv6 address pool and prefix length. · The start IP address, end IP address, and gateway IP address must be on the same segment.

Delete template

Keyword	DELETE_TEMPLATE_OP
Message text	Deleted template: $1
Variable fields	$1: Template name.
Example	Deleted template: TemplateName
Explanation	A template was deleted.
Possible failure causes	· The NGFWM service is not started. · Server processing error. · The configuration item does not exist. · The controller is not the active leader. · You do not have privilege to perform the operation. · Configuration recovery is in progress. · You have no privilege to perform this operation.

Create NGFW resource

Keyword	CREATE_NGFW_RESOURCE_OP
Message text	Created NGFW resource: $1
Variable fields	$1: NGFW resource information.
Example	Created NGFW resource: Name: resource1 Device name: device1 Resource pool name: FW Template type: GatewayGroupFW Description: XXXXX CPU weight: 2 Disk: 1000 Memory: 2000 Username: default Interface list: [ { Interface name: GigabitEthernet1/0/1 Interface type: Management IP: 1.2.3.3 Mask: 255.255.0.0 } { Interface name: GigabitEthernet1/0/2 Interface type: Uplink IP: 1.2.30.5 Mask: 255.255.0.0 } ]
Explanation	An NGFW resource was created.
Possible failure causes	· Invalid NGFW resource name. · The NGFW resource name already exists. · The interface name and type of the NGFW resource are required. · The IP address and mask must be both configured. · Invalid parameter. · Server processing error. · The NGFWM service is not started. · Invalid JSON format. · Failed to deploy the extended configuration and custom configuration to the NGFW resource through SSH. · Failed to establish the SSH connection between the controller and the device. · The number of NGFW resources on all devices in the resource pool has reached the upper limit. · The F5 service is not started. · Failed to assign resources to the NGFW resource by using NETCONF. · Failed to get information of the device where the NGFW resource resides. · The CPU weight of the NGFW resource must be in the range of 1 to 10. · The disk of the NGFW resource must be in the range of 1 to 999999999. · The memory of the NGFW resource must be in the range of 1 to 999999999. · The disk size can’t exceed the disk size of the security engine where the NGFW resource resides. · The memory size can’t exceed the memory size of the security engine where the NGFW resource resides. · Failed to create the NGFW resource. · Failed to obtain the maximum number of NGFW resources supported by the device. · Failed to allocate interfaces for the NGFW resource through NETCONF. · No available templates of this type. · Invalid subnet. · The controller is not the active leader. · You do not have privilege to perform the operation. · Configuration recovery is in progress. · The NGFW resource interface failed to obtain an IP address from the IP address pool. · You have no privilege to perform this operation.

Update NGFW resource

Keyword	UPDATE_NGFW_RESOURCE_OP
Message text	Updated NGFW resource: $1
Variable fields	$1: NGFW resource information.
Example	Updated NGFW resource: Name: resource1 Device name: device1 Resource pool name: FW Template type: GatewayGroupFW Description: XXXXX CPU weight: 2 Disk: 1000 Memory: 2000 Username: default Interface list: [ { Interface name: GigabitEthernet1/0/1 Interface type: Management IP: 1.2.3.3 Mask: 255.255.0.0 } { Interface name: GigabitEthernet1/0/2 Interface type: Uplink IP: 1.2.30.5 Mask: 255.255.0.0 } ]
Explanation	An NGFW resource was modified.
Possible failure causes	· The NGFWM service is not started. · Server processing error. · The configuration item does not exist. · Failed to assign resources to the NGFW resource by using NETCONF. · Failed to get information of the device where the NGFW resource resides. · The CPU weight of the NGFW resource must be in the range of 1 to 10. · The disk of the NGFW resource must be in the range of 1 to 999999999. · The memory of the NGFW resource must be in the range of 1 to 999999999. · The disk size can’t exceed the disk size of the security engine where the NGFW resource resides. · The memory size can’t exceed the memory size of the security engine where the NGFW resource resides. · Failed to update the NGFW resource. · The controller is not the active leader. · You do not have privilege to perform the operation. · Configuration recovery is in progress. · You have no privilege to perform this operation.

Delete NGFW resource

Keyword	DELETE_NGFW_RESOURCE_OP
Message text	Deleted NGFW resource: $1
Variable fields	$1: NGFW resource name.
Example	Deleted NGFW resource: aa
Explanation	An NGFW resource was deleted.
Possible failure causes	· 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 controller is not the active leader. · You do not have privilege to perform the operation. · Configuration recovery is in progress. · You have no privilege to perform this operation.

Create resource pool

Keyword	CREATE_RESOURCE_POOL_OP
Message text	Created resource pool: $1
Variable fields	$1: Resource pool information.
Example	Created resource pool: Name: FW1 Type: FW Device list: [ { Device name: M9K Security engine group ID: 1 } ]
Explanation	A resource pool was created.
Possible failure causes	· The NGFWM service is not started. · Server processing error. · The resource pool name already exists. · The default user of the NGFW resource must be configured. · Invalid resource pool name. · Invalid device name. · The device bound to the resource pool doesn't exist. · Invalid JSON format. · Invalid resource pool type. · The security engine group has been bound to another resource pool. · The controller is not the active leader. · You do not have privilege to perform the operation. · Configuration recovery is in progress. · You have no privilege to perform this operation.

Update resource pool

Keyword	UPDATE_RESOURCE_POOL_OP
Message text	Updated resource pool: $1
Variable fields	$1: Resource pool information.
Example	Updated resource pool: Name: FW1 Type: FW Device list: [ { Device name: M9K Security engine group ID: 1 } ]
Explanation	A resource pool was modified.
Possible failure causes	· The NGFWM service is not started. · Server processing error. · The resource pool name already exists. · The default user of the NGFW resource must be configured. · Invalid resource pool name. · Invalid device name. · The device bound to the resource pool doesn't exist. · Invalid JSON format. · Cannot unbind the security engine F5 group from the resource pool because the security engine F5 group has NGFW resources. · The resource pool type cannot be changed. · The controller is not the active leader. · You do not have privilege to perform the operation. · Configuration recovery is in progress. · You have no privilege to perform this operation.

Delete resource pool

Keyword	DELETE_RESOURCE_POOL_OP
Message text	Deleted resource pool: $1
Variable fields	$1: Resource pool name.
Example	Deleted resource pool: aa
Explanation	A resource pool was deleted.
Possible failure causes	· The NGFWM service is not started. · Server processing error. · The configuration item does not exist. · Cannot delete the resource pool because the resource pool has NGFW resources. · The controller is not the active leader. · You do not have privilege to perform the operation. · Configuration recovery is in progress. · You have no privilege to perform this operation.

Set default user

Keyword	SET_DEFAULT_USER_OP
Message text	Set default user: $1
Variable fields	$1: NGFW resource default user information.
Example	Set default user: Username: admin
Explanation	The NGFW resource default username and password were set.
Possible failure causes	· The NGFWM service is not started. · Server processing error. · Invalid username. · Invalid password. · Invalid JSON format. · The controller is not the active leader. · You do not have privilege to perform the operation. · Configuration recovery is in progress. · You have no privilege to perform this operation.

OAM

This section contains OAM messages.

Create radar detection task

Keyword	CREATE_RADAR_DETECTION_OP
Message text	Created radar detection task: $1
Variable fields	$1: Radar detection task parameters.
Example	Created radar detection task: Username: sdn Mission Id: 5e9693cc-c9d4-44a2-89d2-c9e7e5734cd2 Task type: multiple Task info: Path type: single Network type: vxlan Segment ID: 2 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. · You have no privilege to perform this operation. · The source and destination addresses must be of the same IP version. · The source IP address does not exist. · The task is running. Please try again late. · Wrong source device. · The start device IP address and ingress port are required. · Packets out of range(1-100). · Vni out of range(1-16777215). · Interval out of range(0-30). · Timeout out of range(10-3600). · Detection Interval out of range(10-2592000). · Detection Duration out of range(1-525600). · The source vPort is not found. · The start device does not exist. · The source vPort is in Inactive state. · The destination vPort is not found. · The destination vPort is in Inactive state. · Please specify a DSCP value for the probe packets. · Invalid destination IP address. · The specified IP address does not match the actual IP address of the vPort. · Multipath radar detection is not available for hosts. · The source IP address and destination IP address are on different devices. · Failed to send the request. · Coding error. · Cannot find the master controller for the device. · Cannot find the subnet for the source IP address. · The VLAN and VNI parameters cannot be both specified. · Please specify the source IP address. · Please specify the destination IP address. · Please specify the source port ID. · Please specify the destination VXLAN ID. · Please specify the destination port ID. · Please specify the destination VTEP IP address. · Please specify the source VTEP IP address. · Please specify the source IP address, source VXLAN ID, and the vPort-attached interface on the start device. · Unsupported probe packet type. · The port number must be an integer in the range of 0 to 65535. · The DSCP value must be an integer in the range of 1 to 63. · The path type can only be single or multiple. · The direction can only be forward or reverse. · The device with the specified source VTEP IP address does not exist. · The device with the specified destination VTEP IP address does not exist. · The source IP address cannot be same as the destination IP address. · The start device is in abnormal state. · The destination device is in abnormal state. · The source IP address cannot be the gateway IP address of a subnet. · The destination IP address cannot be the gateway IP address of a subnet. · Invalid IP address. · Invalid JSON format. · Please use another means to test the connectivity between the specified VMs. The VMs are in the same vNetwork and attached to the same vPort. In a network overlay environment, the traffic between them does not traverse their access switch and cannot be detected by using radar detection.

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. · You have no privilege to perform this operation. · The periodic scanning task does not exist.

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 the periodic radar detection tasks of a user were deleted.
Possible failure causes	· The controller is not the active leader. · Radar detection is disabled. · You have no privilege to perform this operation.

Create Network Check

Keyword	OAM_NETWORK_CHECK_CREATE_OP
Message text	Create Network Check: fabricId: $1
Variable fields	$1: Fabric ID.
Example	Create Network Check: fabricId: 1
Explanation	A network check task was executed on a fabric.
Possible failure causes	· The fabric does not exist. · Please first enable radar detection. · A network check task is running on the specified fabric. · You have no privilege to perform this operation.

Cancel Network Check

Keyword	OAM_NETWORK_CHECK_CANCEL_OP
Message text	Cancel Network Check: fabricId: $1
Variable fields	$1: Fabric ID.
Example	Cancel Network Check: fabricId: 1
Explanation	A network check task on a fabric was cancelled.
Possible failure causes	· The fabric does not exist. · Please first enable radar detection. · The task has not started yet. · You have no privilege to perform this operation.

Upload image file

Keyword	UPLOAD_IMAGE_FILE_OP
Message text	Uploaded image file: $1.
Variable fields	$1: Image file name.
Example	Uploaded image file: 6800.ipe.
Explanation	An image file was uploaded.
Possible failure causes	· Invalid image file. · The microservice is initializing. · The image file with the specified name already exists. · Failed to upload the image file. · The system service does not respond.

Update image file

Keyword	UPDATE_IMAGE_FILE_OP
Message text	Updated image file:$1.
Variable fields	$1: Image file information.
Example	Updated image file: { "software_name":"s9850-h3c.ipe", "description":"111", "year_software":"true", }.
Explanation	An image file was modified.
Possible failure causes	· The microservice is initializing. · The system service does not respond. · The image file does not exist. · The image file is in use. · Operation failed.

Bulk delete image file

Keyword	BULK_DELETE_IMAGE_FILE_OP
Message text	Bulk deleted image files: $1
Variable fields	$1: Names of the image files.
Example	Bulk deleted image files: { "Files deleted": [ "wa2600a.ipe" ], "Files failed to be deleted": [ "hp425.ipe" ] }
Explanation	Multiple image files were deleted in bulk.
Possible failure causes	· The microservice was initializing. · The system service did not respond. · The image file does not exist. · The image file was in use. · Operation failed.

Retrieve device disk partitions

Keyword	GET_DEVICE_DISK_OP
Message text	Retrieved the disk partitions of device: $1
Variable fields	$1: Device IP address.
Example	Retrieved the disk partitions of device: 192.168.1.1
Explanation	The disk partition information of a device was retrieved.
Possible failure causes	· The microservice is initializing. · Failed to connect to the device.

Sync image file

Keyword	SYNC_IMAGE_FILE_OP
Message text	Synced image file: $1
Variable fields	$1: Image file information.
Example	Synced image file: { "software_name":"s9850-h3c.ipe", }.
Explanation	An image file was synchronized.
Possible failure causes	· The microservice is initializing. · The system service does not respond. · The image file does not exist.

Upgrade image file

Keyword	UPGRADE_IMAGE_FILE_OP
Message text	Upgraded image file:$1
Variable fields	$1: Image file information.
Example	Upgraded image file: { “time_out":900, "selected_steps":[ "ISSU_UPGRADE_PRE_CHECK", "DISK_CHECK", "FTP_TRANSFER", "GIR_OUT", "ISSU_UPGRADE_SET_MPU_FILE", "ISSU_UPGRADE_TEST", "SAVE", "ISSU_UPGRADE_INSTALL", "ISSU_UPGRADE_RESET", "GIR_BACK" ], "paused_steps":[ "GIR_OUT", "ISSU_UPGRADE_SET_MPU_FILE", "GIR_BACK" ], "software_name": "vBRAS1000-CMW710-BOOT-E1218P01-X64.bin", "devices": [ { "name": "90.6", "ip": "192.168.1.1", "device_id": "605b26bc-b826-48aa-8476-5c6a3abed199", "device_disk": "" } ] }
Explanation	The image file of a device was upgraded.
Possible failure causes	· The microservice is initializing. · Failed to connect to the device. · The image file does not exist. · The image file is in use. · You can upgrade the members in a DR system only one by one. · The device at %s is being upgraded.

Delete upgrade record

Keyword	DELETE_UPGRADE_RECORD_OP
Message text	Deleted device upgrade record: $1.
Variable fields	$1: Device IP address.
Example	Deleted device upgrade record: 192.168.1.1
Explanation	The upgrade records of a device were deleted.
Possible failure causes	· The microservice is initializing. · The system service does not respond. · Device upgrade in progress and the upgrade record cannot be deleted.

Suspend upgrade

Keyword	SUSPEND_UPGRADE_OP
Message text	Suspended device upgrade: $1.
Variable fields	$1: Device information
Example	Suspended device upgrade: { "devices": [ { "device_id": "c8741379-ebe4-4594-9fe2-e7e5c51bdd4b", "device_ip": "192.168.1.1", "device_name": "lll-2", "software_name": "vBRAS1000-X64-20191116-test12.ipe" } ] }
Explanation	An ongoing device upgrade process was suspended.
Possible failure causes	· The microservice is initializing.

Restart upgrade

Keyword	RESTART_UPGRADE_OP
Message text	Restarted device upgrade: $1.
Variable fields	$1: Device information
Example	Restarted device upgrade: { "devices": [ { "device_id": "c8741379-ebe4-4594-9fe2-e7e5c51bdd4b", "device_ip": "192.168.1.1", "device_name": "lll-2", "software_name": "vBRAS1000-X64-20191116-test12.ipe" } ] }
Explanation	A suspended device upgrade process was resumed.
Possible failure causes	· The microservice is initializing.

Configure scheduled upgrade

Keyword	CONFIG_SCHEDULED_UPGRADE_OP
Message text	Configured scheduled upgrade: $1.
Variable fields	$1: User-defined scheduled upgrade information.
Example	Configured scheduled upgrade: { time_out":900, "selected_steps":[ "ISSU_UPGRADE_PRE_CHECK", "DISK_CHECK", "FTP_TRANSFER", "GIR_OUT", "ISSU_UPGRADE_SET_MPU_FILE", "ISSU_UPGRADE_TEST", "SAVE", "ISSU_UPGRADE_INSTALL", "ISSU_UPGRADE_RESET", "GIR_BACK" ], "paused_steps":[ "GIR_OUT", "ISSU_UPGRADE_SET_MPU_FILE", "GIR_BACK" ], "pre_upgrade_time": "2020-01-17 00:00:00", "upgrade_time": "2020-01-18 00:00:00", "devices": [ { “name”: “73.8”, "ip": "192.168.73.8", "device_id": "605b26bc-b826-48aa-8476-5c6a3abed199", “device_disk”: “”, “software_name”: “vBRAS1000-CMW710-BOOT-E1218P01-X64.bin” } ] }
Explanation	Scheduled upgrade settings were configured.
Possible failure causes	· The microservice is initializing. · Failed to connect to the device. · The image file does not exist. · The image file is in use. · Invalid upgrade time. · You can upgrade the members in a DR system only one by one. · The device at %s is being upgraded.

Delete scheduled upgrade

Keyword	DELETE_SCHEDULED_UPGRADE_OP
Message text	Deleted scheduled upgrade: $1.
Variable fields	$1: Scheduled upgrade time.
Example	Deleted scheduled upgrade: 2020-01-18 00:00:00
Explanation	A scheduled upgrade task was deleted.
Possible failure causes	· The microservice is initializing. · Failed to connect to the device.

ISSU upgrade image file

Keyword	ISSU_UPGRADE_IMAGE_FILE_OP
Message text	Performed an ISSU with upgrade image file $1.
Variable fields	$1: ISSU information.
Example	ISSU upgrade image file: { "time_out":900, "selected_steps":[ "ISSU_UPGRADE_PRE_CHECK", "DISK_CHECK", "FTP_TRANSFER", "GIR_OUT", "ISSU_UPGRADE_SET_MPU_FILE", "ISSU_UPGRADE_TEST", "SAVE", "ISSU_UPGRADE_INSTALL", "ISSU_UPGRADE_RESET", "GIR_BACK" ], "paused_steps":[ "GIR_OUT", "ISSU_UPGRADE_SET_MPU_FILE", "GIR_BACK" ], "devices":[ { "name":"leaf-192.168.73.60", "device_id":"5cbf68f4-4f80-4fe2-8a53-1745f72ca627", "time":null, "device_disk":"", "boot":"s6800-cmw710-boot-f2802.bin", "system":"s6800-cmw710-system-f2802.bin", "features":null, "patches":null, "ipe":null } ] }
Explanation	A software upgrade was performed for the device by using ISSU.
Possible failure causes	· The microservice is initializing. · Failed to connect to the device. · The image file does not exist. · The image file is in use. · You can upgrade the members in a DR system only one by one. · The device at %s is being upgraded.

Create replacement task

Keyword	CREATE_REPLACE_TASK_OP
Message text	Created replacement task: $1
Variable fields	$1: Replacement task information.
Example	"Created replacement task": { "deviceId" : "837a4046-5ecc-4a48-9837-bb55eee69148", "deviceSn" : "005056b9321c542d20041013", "replaceDeviceSn" : "005056b962a1d82e20041013" }, Influece tenant Information: { "access": [{ "tenant": "xxx", "vrouter": ["vrouter1", "vrouter2"] }], "export": [{ "tenant": "xxx", "vrouter": ["vrouter1", "vrouter2"] }], "security": [{ "tenant": "xxx", "vrouter": ["vrouter1", "vrouter2"] }], "dci": [{ "tenant": "xxx", "vrouter": ["vrouter1", "vrouter2"] }] }
Explanation	A device replacement task was created.
Possible failure causes	· The TFTP service is disabled. · Invalid JSON format. · Internal error. · The backup configuration file of the faulty 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. · Cannot replace a standalone device with an IRF fabric member device. · The device with the specified serial number does not exist. · The device has replaced the original device for 30 minutes but has not onboarded yet. Please check the device settings. · The replacement device must have the same role as the failed device. · The replacement task already exists. · The faulty device is being used in another replacement task. · The replacement device does not exist. · Invalid network entity ID. · Please specify the serial number of the replacement device. · Replacement device with the specified serial number has been specified in another replacement task. · Failed to update the DHCP client ID. · The device is being replaced. · Cannot create the replacement task because a configuration backup or restore operation is being performed on the replacement device. · Failed to obtain information about the IRF fabric. · The member number of fault device and replace device for stack whole replace is not same.

Delete replacement task

Keyword	DELETE_REPLACE_TASK_OP
Message text	Deleted replacement task: $1.
Variable fields	$1: UUID of the faulty device.
Example	Deleted replacement task: 29ced688-57ce-319c-9f72-5cdbfe2edb1c
Explanation	A device replacement task was deleted.
Possible failure causes	· Invalid JSON format. · Internal error. · The specified replacement task does not exist. · The replacement task cannot be deleted in the current phase.

Create configuration file backup task

Keyword	BACKUP_AND_SYNC_DEV_CFG_OP
Message text	Created configuration file backup task:$1
Variable fields	$1: IP addresses of the devices on which creation of the configuration file backup task succeeded/failed.
Example	Created backup config file task: { "Operation succeeded on devices" : [ "192.168.116.134", "192.168.116.130" ], "Operation failed on devices" : [] }
Explanation	A configuration file backup task was created.
Possible failure causes	· Failed to back up and synchronize the configuration file. · Invalid JSON format. · Internal error.

Restore device

Keyword	CREATE_RESTORE_TASK_OP
Message text	Restored device: $1
Variable fields	$1: Configuration file name and device ID.
Example	Restored device: { "fileName" : "192.168.67.203_20200808143922_m.cfg", "deviceId" : "837a4046-5ecc-4a48-9837-bb55eee69148" }
Explanation	A configuration file was restored on a device.
Possible failure causes	· Invalid JSON format. · Internal error. · Failed to send the configuration file to the device.

Upload config file

Keyword	UPLOAD_CFG_OP
Message text	Uploaded config file: $1
Variable fields	$1: Configuration file name and device ID.
Example	Uploaded config file: { "fileName" : "192.168.67.203_20200808143922_m.cfg", "deviceId" : "f2016ce7-0d15-4721-a765-1a69f49e18ec" }
Explanation	A configuration file was uploaded.
Possible failure causes	· Invalid JSON format. · Internal error.

Configure scheduled backup

Keyword	CONFIG_SCHEDULED_BACKUP_OP
Message text	Configured scheduled backup task: $1
Variable fields	$1: Scheduled backup task information.
Example	Configured scheduled backup task: { "autoBackup" : true, "frequency" : "every month", "time" : "10:33", "week" : "", "date" : "" }
Explanation	A scheduled backup task was created.
Possible failure causes	· Invalid JSON format. · Internal error.

Delete config file

Keyword	DELETE_CONFIG_FILE_OP
Message text	Deleted config file: $1.
Variable fields	$1: Scheduled backup task information.
Example	Deleted config file: { "configFileName" : "192.168.67.203_20200808143922_m.cfg", "deviceId" : "f2016ce7-0d15-4721-a765-1a69f49e18ec" }
Explanation	The configuration file of a device was deleted.
Possible failure causes	· Invalid JSON format. · Internal error. · The NE device doesn't not exist.

Start data check

Keyword	START_DATA_CHECK_OP
Message text	Started data check for module [$1].
Variable fields	$1: Module name.
Example	Started data check for module [VSM].
Explanation	Data check was started for a module.
Possible failure causes	· Internal error. · Cannot start the data check because the previous data check is not finished. · Invalid parameter. · Failed to start the data check.

Stop data check

Keyword	STOP_DATA_CHECK_OP
Message text	Stopped data check.
Variable fields	N/A
Example	Stopped data check.
Explanation	Data check was stopped.
Possible failure causes	· Internal error. · No ongoing data check exists.

Modify interface status by interface index

Keyword	MODIFY_INTERFACE_STATUS_BY_INDEX_OP
Message text	Modified interface status by index: $1
Variable fields	$1: Interface information.
Example	Modified interface status by index: IP: [1.1.1.1] Interface Index: [1, 2, 3] Shutdown: [true]
Explanation	An interface with the specified index was shut down or brought up.
Possible failure causes	· Configuration recovery is in progress. · The is_shut_down parameter is required. · Invalid IP address. · Internal server error. · Invalid JSON format. · The is_shut_down parameter value must be true or false, which is case insensitive. · The controller is not the active leader. · The port ID is required. · Invalid port ID. · Unsupported device type. · The specified device doesn't exist. · You have no privilege to perform this operation. · Can not be configured with port up-mode command together.

Start one-click check

Keyword	START_ONE_CLICK_CHECK_OP
Message text	Started one-click check.
Variable fields	N/A
Example	Started one-click check.
Explanation	A one-click check task was started.
Possible failure causes	· Data consistency check is in progress. Please try again later. · The user has no privilege to this operation. · The check task is in progress. Please try again later. · Database operation failed. · Unknown errors.

Stop one-click check

Keyword	STOP_ONE_CLICK_CHECK_OP
Message text	Stopped one-click check: $1
Variable fields	$1: Controller IP address.
Example	Stopped one-click check: 10.10.10.12
Explanation	A one-click check task was stopped.
Possible failure causes	· Cannot stop the check task, because it has finished. · The user has no privilege to this operation. · Unknown errors.

Update check setttings

Keyword	UPDATE_CHECK_PARAM_OP
Message text	Updated check settings: $1
Variable fields	$1: Check parameter settings.
Example	Updated check settings: { "timing_check":{ "date":"1", "week":"1", "hour":"0", "status":"close", "frequency":"day", "minute":"0" }, "node_max_num":"1" }
Explanation	The check parameter settings were updated.
Possible failure causes	· The check task is in progress. Please try again later. · Unknown errors.

Create restore point

Keyword	CREATE_RESTORE_POINT_OP
Message text	Created restore point: $1
Variable fields	$1: Restore point information.
Example	Created restore point: { “id”:”5cb9db7e-eca5-4b0a-a866-13c65ce3425d”, “serial_number”:”20210310130256001”, "north_lock":true, "description":"1111", "devices":[ "e87701a4-af3b-467b-a571-8b7115a7389e", "eb8323f5-f046-4d53-a081-12fbd4d60a05e" ] }
Explanation	A restore point was created based on the controller and device settings.
Possible failure causes	· A configuration restoration task is in progress. Please try again later. · Unknown errors.

Update restore point

Keyword	UPDATE_RESTORE_POINT_OP
Message text	Updated restore point: $1
Variable fields	$1: Restore point information.
Example	Updated restore point: { “id”:”5cb9db7e-eca5-4b0a-a866-13c65ce3425d”, “serial_number”:”20210310130256001”, "north_lock":true, "description":"1111", "devices":[ "e87701a4-af3b-467b-a571-8b7115a7389e", "eb8323f5-f046-4d53-a081-12fbd4d60a05e" ] }
Explanation	The settings of a specific restore point were edited.
Possible failure causes	· The restore point does not exist. · Unknown errors.

Delete restore point

Keyword	DELETE_RESTORE_POINT_OP
Message text	Deleted restore point: $1
Variable fields	$1: Restore point information.
Example	Deleted restore point: { "id_list":[ "e87701a4-af3b-467b-a571-8b7115a7389e", "eb8323f5-f046-4d53-a081-12fbd4d60a05e" ] }
Explanation	Specific restore point settings were deleted.
Possible failure causes	· Unknown errors. · Restore point is in use. · The restore point does not exist.

Create rollback record

Keyword	CREATE_ROLLBACK_RECORD_OP
Message text	Created rollback record: $1
Variable fields	$1: Rollback record information.
Example	Created rollback record: { "id":"8eed6dfd-eb33-4e96-9760-e66636e6739f", “point_id”:” 5cb9db7e-eca5-4b0a-a866-13c65ce3425d”, "north_lock":"true", "devices":[ "e87701a4-af3b-467b-a571-8b7115a7389e", "eb8323f5-f046-4d53-a081-12fbd4d60a05e" ] "timeout":35 }
Explanation	A rollback record was created.
Possible failure causes	· A configuration restoration task is in progress. Please try again later. · Unknown errors. · The specified restore point does not exist.

Roll back device

Keyword	ROLLBACK_DEVICE_OP
Message text	Rolled back device: $1
Variable fields	$1: Rollback record information.
Example	Rolled back device: { "id":"8eed6dfd-eb33-4e96-9760-e66636e6739f", "devices":[ "e87701a4-af3b-467b-a571-8b7115a7389e"， "eb8323f5-f046-4d53-a081-12fbd4d60a05e" ] }
Explanation	A rollback operation was performed for a device with rollback failure.
Possible failure causes	· A configuration restoration task is in progress. Please try again later. · Unknown errors. · The specified restore point does not exist.

RCAM

This section contains resource access template messages.

Create resource access template

Keyword	CREATE_RESOURCETEMPLATE_OP
Message text	Created resource access template: $1.
Variable fields	$1: Resource access template configuration.
Example	Created resource access template: id: [a10578f3-ddbe-4d68-92b4-8929233a8094] name: [devtemp1] vlanPoolId: [21ee339c-423d-4001-a8c1-270cabdd1601] vlanPoolName: [vlan1] vxlanPoolId: [340da567-9508-437d-9f73-faeb5af80637] vxlanPoolName: [vxlan1] ipPoolId: [19f399eb-8b98-48be-9781-4f845cb24f7e] ipPoolName: [ippool] rsTemplate Name: [lkf6280] rsTemplate Type: [VNF] doubleArm: [true] deviceId: [91d244cc-2cc6-429f-82f7-bd2c4b1224a0] deviceName: [11] ingressPort: [GigabitEthernet1/0/1] egressPort: [Twenty-FiveGigE1/1/5].
Explanation	A resource access template was created.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · The resource access template already exists. · 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 VXLAN pool doesn't exists. · The VLAN pool doesn't exists. · The IP pool doesn't exists. · Invalid name. · The type of resource can only be VNF or NGFW. · Duplicate entries exist in the resource access template. · The resource access template cannot contain more than 16 entries. · You have no privilege to perform this operation. · When the connection mode is one arm, make sure the input and output interfaces for the access device are the same. · When the connection mode is one arm, make sure the service type is FW for the associated resource template. · When the connection mode is one arm, make sure the uplink and downlink interfaces for the associated resource template are the same. · The specified VNF template does not exist. · The specified NGFW template does not exist. · Incorrect resource template type. Please select the PBR service chain FW or PBR service chain LB. · The resource source can only be VNF, NGFW, or Custom. · The rs_template_id parameter is required when the resource source is NGFW. · The rs_template_name parameter is required when the resource source is VNF. · The name parameter is required. · The rs_template_type parameter is required. · The egress_port parameter is required. · The ingress_port parameter is required. · The device_id parameter is required. · The ip_pool_id parameter is required. · The vxlan_pool_id parameter is required. · The vlan_pool_id parameter is required. · The device_name parameter is read only. · The vxlan_pool_name parameter is read only. · The vlan_pool_name parameter is read only.

Delete resource access template

Keyword	DELETE_RESOURCETEMPLATE_OP
Message text	Deleted resource access template: $1.
Variable fields	$1: UUID of the resource access template.
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. · You have no privilege to perform this operation. · Cannot delete the resource access template, because it has been bound to a service resource.

RDR

This section contains remote disaster recovery messages.

Create RDR system

Keyword	CREATE_RDRS_OP
Message text	Created a remote disaster recovery system.
Variable fields	N/A
Example	Created a remote disaster recovery system.
Explanation	A remote disaster recovery system was created.
Possible failure causes	· The system service does not respond. · The operation is not performed on the site where the primary component is installed. · Another operation is in progress. Please try again later. · Failed to create the RDRS. · The NTP service is not configured for the site. · The SNA Center running on the primary site and backup site are of different versions. · Cannot create the RDRS because deletion of the existing RDRS is not completed. · Cannot create the RDRS because of an internal error on the primary site. · The specified backup site is already in another RDRS. · Access to the backup site denied. Please verify that 1) The Web interface of the backup site can be accessed. 2) The allow list entries, if any, are correctly configured to allow authorized access to the system. 3) Certificate settings are correctly configured if bidirectional authentication is enabled. · Cannot connect to the backup site. Please verify the validity of the backup site's username and password and the network connectivity, and then try again. · You must enter the cluster internal virtual IP of the local site for the primary site IP. · You must enter the cluster internal virtual IP of the remote site for the backup site IP. · Cannot create the RDRS because the node where the primary site or backup site resides fails. · Failed to obtain status of the disaster recovery components. · You cannot create the RDRS. Please make sure the status of the disaster recovery component at the local site is primary. · You cannot create the RDRS. Please make sure the status of the disaster recovery component at the backup site is backup. · Failed to obtain the role of the site. · Failed to connect to the third-party site. Make sure the IP address of the third-party site.

Update RDR system

Keyword	UPDATE_RDRS_OP
Message text	Updated a remote disaster recovery system. Switchover mode is $1.
Variable fields	$1: Switchover mode. Options are manual switchover and auto switchover with arbitration.
Example	Updated a remote disaster recovery system. Switchover mode is manual switchover.
Explanation	A remote disaster recovery system was edited.
Possible failure causes	· The system service does not respond. · Another operation is in progress. Please try again later. · Failed to connect to the third-party site. Make sure the IP address of the third-party site is correct and a network connection is available. · The operation is not performed on the site where the primary component is installed.

Delete RDR system

Keyword	DEL_RDRS_OP
Message text	Deleted a remote disaster recovery system.
Variable fields	N/A
Example	Deleted a remote disaster recovery system.
Explanation	A remote disaster recovery system was deleted.
Possible failure causes	· The system service does not respond. · The operation is not performed on the site where the primary component is installed. · The disaster recovery system contains backup relationships and cannot be deleted. · Another operation is in progress. Please try again later. · Cannot delete the RDRS because the RDRS setup is not completed.

Fix RDR system

Keyword	FIX_RDRS_OP
Message text	Fixed a remote disaster recovery system.
Variable fields	N/A
Example	Fixed a remote disaster recovery system.
Explanation	A remote disaster recovery system was fixed.
Possible failure causes	· The system service does not respond. · Failed to restore the arbitration service. · Another operation is in progress. Please try again later. · The operation is not performed on the site where the primary component is installed. · Failed to connect to the third-party site. Make sure the IP address of the third-party site is correct and a network connection is available.

Create RDR relation

Keyword	CREATE_RDRS_RELATION_OP
Message text	Created a remote disaster recovery relation.
Variable fields	N/A
Example	Created a remote disaster recovery relation.
Explanation	A remote disaster recovery component was created.
Possible failure causes	· The system service does not respond. · The operation is not performed on the site where the primary component is installed. · Another operation is in progress. Please try again later. · The specified component does not exist on the backup site. · The components on the primary site and the components on the backup site cannot communicate through the RDRS network. · Failed to add the disaster recovery component. · The number of containers deployed for the component at the primary site and backup site do not match. · The backup site has not completed site configuration. Please try again later. · The primary site and backup site cannot use the same IP address for NIC eth2. · The primary and backup sites are inconsistent in vDHCP or vBGP deployment. · The version of app is not same.

Delete RDR relation

Keyword	DEL_RDRS_RELATION_OP
Message text	Deleted a remote disaster recovery relation.
Variable fields	N/A
Example	Deleted a remote disaster recovery relation.
Explanation	A remote disaster recovery component was deleted.
Possible failure causes	· Invalid JSON format. · The system service does not respond. · The operation is not performed on the site where the primary component is installed. · A primary/backup role switchover is in progress. · Another operation is in progress. Please try again later. · Cannot delete the disaster recovery component because a primary/backup switchover operation is in progress for the component. · To delete the disaster recovery component at the backup site, please access the backup site.

Component switched to primary role

Keyword	TAKE_OVER_APP_OP
Message text	Component $1 switched to primary role successfully
Variable fields	$1: Component name.
Example	Component VCFCDC switched to primary role successfully.
Explanation	A component was switched to the primary role.
Possible failure causes	· The system service does not respond. · Cannot perform the operation on the primary component. · Another operation is in progress. Please try again later. · Cannot perform the primary/backup switchover because a node at the backup site is faulty.

Component switched to backup role

Keyword	DROP_APP_OP
Message text	Component $1 switched to backup role successfully.
Variable fields	$1: Component name.
Example	Component VCFCDC switched to backup role successfully.
Explanation	A component was switched to the backup role.
Possible failure causes	· The system service does not respond. · Cannot perform the operation on the backup component. · Another operation is in progress. Please try again later. · Cannot perform the primary/backup switchover because a node at the backup site is faulty. · The operation is not performed on the site where the primary component is installed.

SEERENGINE

This section contains SEERENGINE messages.

Create rate limit profile

Keyword	CREATE_CAR_PROFILE_OP
Message text	Created rate limit profile: ID: $1 Name: $2 Description: $3 CIR: $4 CBS: $5 PIR: $6 EBS: $7 Status: $8
Variable fields	$1: Rate limit profile ID. $2: Rate limit profile name. $3: Rate limit profile description. $4: Committed information rate (kbps). $5: Committed burst size (bytes). $6: Peak information rate (kbps). $7: Excess burst size (bytes). $8: Rate limit profile usage state.
Example	Created rate limit profile: ID: [dfbce4db-8e72-4fd4-a659-f6889c709e15] Name: [addTest ] Description: [111] CIR: [64] CBS: [512] PIR: [80] EBS: [512] Status: [false].
Explanation	A rate limit profile was created.
Possible failure causes	· The service does not exist. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The name is required and cannot exceed 255 characters. · The description cannot exceed 255 characters. · The CIR cannot be null. · If the EBS is not null, the CBS and PIR are required. · The CIR must be a multiple of 8 and in the range of 8 to 4294967288. · The CBS must be a multiple of 512 and in the range of 512 to 256000000. · The PIR must be a multiple of 8 and in the range of 8 to 4294967288. Its value must be smaller than the CIR. · The EBS must be a multiple of 512 and in the range or 0 to 256000000. · Failed to add the configuration item. · You have no privilege to perform this operation.

Update rate limit profile

Keyword	UPDATE_CAR_PROFILE_OP
Message text	Updated rate limit profile: ID: $1 Name: $2 Description: $3 CIR: $4 CBS: $5 PIR: $6 EBS: $7 Status: $8
Variable fields	$1: Rate limit profile ID. $2: Rate limit profile name. $3: Rate limit profile description. $4: Committed information rate (kbps). $5: Committed burst size (bytes). $6: Peak information rate (kbps). $7: Excess burst size (bytes). $8: Rate limit profile usage state.
Example	Updated rate limit profile ID: [dfbce4db-8e72-4fd4-a659-f6889c709e15] Name: [modTest] Description: [01]↵ CIR: [64]↵ CBS: [512] PIR: [80] EBS : [512] Status: [false].
Explanation	A rate limit profile was edited.
Possible failure causes	· The service does not exist. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The configuration item does not exist. · The rate limit profile ID cannot be edited. · The rate limit profile name cannot be edited. · The CIR cannot be modified. · The CBS cannot be modified. · The PIR cannot be modified. · The EBS cannot be modified. · The status field cannot be modified. · The description cannot exceed 255 characters. · Failed to modify the configuration item. · You have no privilege to perform this operation.

Delete rate limit profile

Keyword	DELETE_CAR_PROFILE_OP
Message text	Deleted rate limit profile $1.
Variable fields	$1: Rate limit profile name.
Example	Deleted rate limit profile test
Explanation	A rate limit profile was deleted.
Possible failure causes	· The service does not exist. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The configuration item does not exist. · The rate limit profile is used. · You have no privilege to perform this operation.

Create mirroring destination profile

Keyword	CREATE_MIRROR_DESTINATION_PROFILE_OP
Message text	Created mirroring destination profile: ID: $1 Name: $2 Description: $3 Destination vPort: $4 Destination IPv4 addresses: $5 Status: $6 Tenant ID: $7 VXLAN ID: $8. VXLAN ID Source: $9
Variable fields	$1: Mirroring destination profile ID. $2: Mirroring destination profile name. $3: Mirroring destination profile description. $4: Destination vPort ID. $5: Destination IPv4 address list. $6: Mirroring destination profile usage state. $7: Tenant ID. $8: VXLAN ID. $9: VXLAN ID pool.
Example	Created mirroring destination profile: ID: [a36f1d47-3cc5-4b1c-ad1b-64a07fc6ad66] Name: [addMirrorTemplate] Description: [description111] Destination vPort: [94575fea-604d-4c18-8f65-3b5c3871384a] Destination IPv4 addresses: [18.16.15.16, 16.15.16.15, 192.168.16.15] Cloud region name:[aaa] Status: [false] Tenant ID: [null] VXLAN ID: [null] VXLAN ID Source: [94575fea-604d-4c18-8f65-3b5c3871384a]
Explanation	A mirroring destination profile was created.
Possible failure causes	· The service does not exist. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The name is required and cannot exceed 255 characters. · Failed to add the configuration item. · You have no privilege to perform this operation.

Update mirroring destination profile

Keyword	UPDATE_MIRROR_DESTINATION_PROFILE_OP
Message text	Updated mirroring destination profile: ID: $1 Name: $2 Description: $3 Destination vPort: $4 Destination IPv4 addresses: $5 Status: $6 Tenant ID: $7 VXLAN ID: $8. VXLAN ID Source: $9
Variable fields	$1: Mirroring destination profile ID. $2: Mirroring destination profile name. $3: Mirroring destination profile description. $4: Destination vPort ID. $5: Destination IPv4 address list. $6: Mirroring destination profile usage state. $7: Tenant ID. $8: VXLAN ID. $9: VXLAN ID pool.
Example	Updated mirroring destination profile: ID: [a36f1d47-3cc5-4b1c-ad1b-64a07fc6ad66] Name: [test] Description: [111] Destination vPort: [94575fea-604d-4c18-8f65-3b5c3871384a] Destination IPv4 addresses: [18.16.15.16, 16.15.16.15, 192.168.16.15] Cloud region name:[aaa] Status: [false] Tenant ID: [null] VXLAN ID: [null] VXLAN ID Source: [94575fea-604d-4c18-8f65-3b5c3871384a]
Explanation	A mirroring destination profile was edited.
Possible failure causes	· The service does not exist. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The configuration item does not exist. · The name is required and cannot exceed 255 characters. · Failed to modify the configuration item. · You have no privilege to perform this operation.

Delete mirroring destination profile

Keyword	DELETE_MIRROR_DESTINATION_PROFILE_OP
Message text	Deleted mirroring destination profile $1.
Variable fields	$1: Mirroring destination profile name.
Example	Deleted mirroring destination profile test.
Explanation	A mirroring destination profile was deleted.
Possible failure causes	· The service does not exist. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The configuration item does not exist. · The specified mirroring destination profile is used. · You have no privilege to perform this operation.

Create classifier

Keyword	CREATE_CLASSIFIER_OP
Message text	Created classifier: ID: $1 Name: $2 Description: $3 Status: $4 ACL rules: $5 { Rule ID: Id[value=$6] Rule name: $7 Rule protocol: $8 Rule source IP: $9 Rule destination IP: $10 Rule source port: $11 Rule destination port: $12 Rule IP type: $13 Rule VRF: $14 }
Variable fields	$1: Classifier ID. $2: Classifier name. $3: Classifier description. $4: Classifier usage state. $5: ACL rule list. $6: ACL rule ID. $7: ACL rule name. $8: Protocol specified in an ACL rule. $9: Source IP address specified in an ACL rule. $10: Destination IP address specified in an ACL rule. $11: Source port number specified in an ACL rule. $12: Destination port number specified in an ACL rule. $13: IP type specified for an ACL rule. $13: VRF of the specified gateway bound to a vRouter.
Example	Created classifier: ID: [76d78185-3144-410a-96c1-3fe212c5a2de] Name : [addTest] Description: [01] Status: [false] ACL rules: { Rule ID: Id[value=aa25f6d9-2354-4e74-9679-a905376b3d29] Rule name: [ruleName02] Rule protocol: [UDP] Rule source IP: [16.16.16.16/24] Rule destination IP: [16.16.16.188/24] Rule source Port: [5] Rule destination port: [4] Rule IP type: [IPV4] Rule VRF: [7of0ho1hqt9scbseq4vhqh8g91] } { Rule ID: Id[value=30f40435-55fb-490f-a650-9ee3cd5ae5e1] Rule name: [ruleName01] Rule protocol: [TCP] Rule source IP: [16.15.16.16/24] Rule destination IP: [15.16.16.16/24] Rule source port: [5] Rule destination port: [6] Rule IP type: [IPV4] Rule VRF: [5oc54lmbue9arr9ecop71hqdln] }
Explanation	A classifier was created.
Possible failure causes	· The service does not exist. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The name is required and cannot exceed 255 characters. · The description cannot exceed 255 characters. · Failed to add the configuration item. · You have no privilege to perform this operation.

Update classifier

Keyword	UPDATE_CLASSIFIER_OP
Message text	Updated classifier: ID: $1 Name: $2 Description: $3 Status: $4 ACL rules: $5 { Rule ID: Id[value=$6] Rule name: $7 Rule protocol: $8 Rule source IP: $9 Rule destination IP: $10 Rule source port: $11 Rule destination port: $12 Rule IP type: $13 Rule VRF: $14 }
Variable fields	$1: Classifier ID. $2: Classifier name. $3: Classifier description. $4: Classifier usage state. $5: ACL rule list. $6: ACL rule ID. $7: ACL rule name. $8: Protocol specified in an ACL rule. $9: Source IP address specified in an ACL rule. $10: Destination IP address specified in an ACL rule. $11: Source port number specified in an ACL rule. $12: Destination port number specified in an ACL rule. $13: IP type specified for an ACL rule. $13: VRF of the specified gateway bound to a vRouter.
Example	Updated classifier: ID: [76d78185-3144-410a-96c1-3fe212c5a2de] Name: [modTest01] Description: [description111] Status: [false] ACL rules: { Rule ID: Id[value=aa25f6d9-2354-4e74-9679-a905376b3d29] Rule name: [ruleName02] Rule protocol: [UDP] Rule source IP: [16.16.16.16/24] Rule destination IP: [16.16.16.188/24] Rule source port: [5] Rule destination port: [4] Rule IP type: [IPV4] Rule VRF: [7of0ho1hqt9scbseq4vhqh8g91] }
Explanation	A classifier was edited.
Possible failure causes	· The service does not exist. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The configuration item does not exist. · The name is required and cannot exceed 255 characters. · The description cannot exceed 255 characters. · Failed to modify the configuration item. · You have no privilege to perform this operation. · Southbound devices at the following IP addresses were disconnected: {IP addresses}.

Delete classifier

Keyword	DELETE_CLASSIFIER_OP
Message text	Deleted classifier $1.
Variable fields	$1: Classifier name.
Example	Deleted classifier test.
Explanation	A classifier was deleted.
Possible failure causes	· The service does not exist. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The configuration item does not exist. · The specified classifier is used. · You have no privilege to perform this operation.

Create flow policy

Keyword	CREATE_FLOW_POLICY_OP
Message text	Created flow policy: ID: $1 Name: $2 Dot1p: $3 Classifier ID: $4 Mirroring destination profile ID: $5 Rate limit profile ID: $6
Variable fields	$1: Flow policy ID. $2: Flow policy name. $3: 802.1p priority. $4: Classifier ID. $5: Mirroring destination profile ID. $6: Rate limit profile ID.
Example	Created flow policy: ID: [e075ca4c-938d-4d57-abb1-1ba2ccde5981] Name: [PolicyName11] Dot1p: [233] Classifier ID: [060455ab-61da-4313-b370-d67c2da33b71] Mirroring destination profile ID: [1942b945-756a-4c5d-b1dc-bab33d1328cc] Rate limit profile ID: [52d32dab-19fc-4f7c-a2ab-e52218ef7ac3]
Explanation	A flow policy was created.
Possible failure causes	· The service does not exist. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The name is required and cannot exceed 255 characters. · Failed to add the configuration item. · You have no privilege to perform this operation.

Update flow policy

Keyword	UPDATE_FLOW_POLICY_OP
Message text	Updated flow policy: ID: $1 Name: $2 Dot1p: $3 Classifier ID: $4 Mirroring destination profile ID: $5 Rate limit profile ID: $6
Variable fields	$1: Flow policy ID. $2: Flow policy name. $3: 802.1p priority. $4: Classifier ID. $5: Mirroring destination profile ID. $6: Rate limit profile ID.
Example	Updated flow policy: ID: [e075ca4c-938d-4d57-abb1-1ba2ccde5981] Name: [11] Dot1p: [233] Classifier ID: [060455ab-61da-4313-b370-d67c2da33b71] Mirroring destination profile ID: [1942b945-756a-4c5d-b1dc-bab33d1328cc] Rate limit profile ID: [52d32dab-19fc-4f7c-a2ab-e52218ef7ac3]
Explanation	A flow policy was edited.
Possible failure causes	· The service does not exist. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The configuration item does not exist. · The name is required and cannot exceed 255 characters. · Failed to modify the configuration item. · You have no privilege to perform this operation.

Delete flow policy

Keyword	DELETE_FLOW_POLICY_OP
Message text	Deleted flow policy $1.
Variable fields	$1: Flow policy name.
Example	Deleted flow policy 11.
Explanation	A flow policy was deleted.
Possible failure causes	· The service does not exist. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The configuration item does not exist. · You have no privilege to perform this operation.

Create physical port policy

Keyword	CREATE_PHYSICAL_PORT_POLICY_OP
Message text	Created physical port policy: ID: $1 Name: $2 Description: $3 Device IP: $4 Interfaces: $5 Congestion temp ID: $6 Traffic policies: [ ID: $7 Name: $8 Remark: $9 Classifier ID: $10 Rate limit profile ID: $11 Mirroring destination profile ID: $12 Local mirror interface names: $13 Direction: $14 Traffic size measurement: $15 ]
Variable fields	$1: Physical port policy ID. $2: Physical port policy name. $3: Physical port policy description. $4: Device IP. $5: Interface list. $6: Congested queue ID. $7: Flow policy ID. $8: Flow policy name. $9: Priority values to be marked, including 802.1p priority value, local precedence value, and DSCP value. $10: Classifier ID. $11: Rate limit profile ID. $12: Mirroring destination profile ID. $13: Destination port list of local mirroring. $14: Direction in which the policy is applied. $15: Traffic measurement unit.
Example	Created physical port policy: ID: [6913d1cc-bad2-454b-b213-65ee4f6181be] Name: [11] Description: [111] Device IP: [192.168.67.208] Interfaces: [[XGE1/0/1, XGE1/0/4]] Congestion temp ID: [6913d1cc-bad2-454b-b213-65ee4f6181bb] Traffic policies: [ ID: [072f501d-fdf8-4131-b1f5-4e85761fd08a] Name: [policy] Remark: [TaasRemark{dot1p=null, localPrecedence=null, dscp=null}] Classifier ID: [Id[value=4d3e94e8-d8f0-452d-a8c1-4f171eb1ad22]] Rate limit profile ID: [null] Mirroring destination profile ID: [[Id[value=0cc5a797-5989-4d0b-88cd-d5bf8eee00ae]]] Local mirror interface names: [[WGE1/0/3, WGE1/0/4]] Direction: [IN] Traffic size measurement: [In Bytes] ]
Explanation	A physical port policy was created.
Possible failure causes	· The service does not exist. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The name is required and cannot exceed 255 characters. · Failed to add the configuration item. · You have no privilege to perform this operation. · The switching device is not active.

Update physical port policy

Keyword	UPDATE_PHYSICAL_PORT_POLICY_OP
Message text	Updated physical port policy: ID: $1 Name: $2 Description: $3 Device IP: $4 Interfaces: $5 Congestion temp ID: $6 Traffic policies: [ ID: $7 Name: $8 Remark: $9 Classifier ID: $10 Rate limit profile ID: $11 Mirroring destination profile ID: $12 Local mirror interface names: $13 Direction: $14 Traffic size measurement: $15 ]
Variable fields	$1: Physical port policy ID. $2: Physical port policy name. $3: Physical port policy description. $4: Device IP. $5: Interface list. $6: Congested queue ID. $7: Flow policy ID. $8: Flow policy name. $9: Priority values to be marked, including 802.1p priority value, local precedence value, and DSCP value. $10: Classifier ID. $11: Rate limit profile ID. $12: Mirroring destination profile ID. $13: Destination port list of local mirroring. $14: Direction in which the policy is applied. $15: Traffic measurement unit.
Example	Updated physical port policy: ID: [6913d1cc-bad2-454b-b213-65ee4f6181be] Name: [11] Description: [111] Device IP: [192.168.67.208] Interfaces: [[XGE1/0/1, XGE1/0/4]] Congestion temp ID: [6913d1cc-bad2-454b-b213-65ee4f6181bb] Traffic policies: [ ID: [072f501d-fdf8-4131-b1f5-4e85761fd08a] Name: [policy] Remark: [TaasRemark{dot1p=null, localPrecedence=null, dscp=null}] Classifier ID: [Id[value=4d3e94e8-d8f0-452d-a8c1-4f171eb1ad22]] Rate limit profile ID: [null] Mirroring destination profile ID: [[Id[value=0cc5a797-5989-4d0b-88cd-d5bf8eee00ae]]] Local mirror interface names: [[WGE1/0/3, WGE1/0/4]] Direction: [IN]. Traffic size measurement: [In Bytes] ]
Explanation	A physical port policy was edited.
Possible failure causes	· The service does not exist. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The configuration item does not exist. · The name is required and cannot exceed 255 characters. · Failed to modify the configuration item. · You have no privilege to perform this operation. · The switching device is not active.

Delete physical port policy

Keyword	DELETE_PHYSICAL_PORT_POLICY_OP
Message text	Deleted physical port policy $1.
Variable fields	$1: Physical port policy name.
Example	Deleted physical port policy 11.
Explanation	A physical port policy was deleted.
Possible failure causes	· The service does not exist. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The configuration item does not exist. · You have no privilege to perform this operation. · The switching device is not active.

Create mirroring profile

Keyword	CREATE_MIRRORING_PROFILE_OP
Message text	Created mirroring profile: ID: $1 Name: $2 Description: $3 Tenant ID: $4 vPort ID: $5 Destination IPv4: $6 Destination IPv6: $7 Mirroring destination template ID: $8 Direction: $9
Variable fields	$1: Mirroring profile ID. $2: Mirroring profile name. $3: Mirroring profile description. $4: Tenant ID. $5: Bound vPort ID. $6: Destination IPv4 subnet. $7: Destination IPv6 subnet. $8: Remote mirroring destination profile ID. $9: Direction.
Example	Created mirroring profile: ID: [39e57447-76e2-4b66-894d-625428ecb8e5] Name: [flowName01] Description: [desc01] Tenant ID:[bde03f0b-bf0c-4fcd-a124-b1feb7802c71] Cloud region name:[aaa] vPort ID: [785f1a33-b1c0-48cb-bcae-dfae830ac6df] Destination IPv4: [1.2.5.0/24] Destination IPv6: [null] Mirroring destination template ID: [1942b945-756a-4c5d-b1dc-bab33d1328cc] Direction: [OUT]
Explanation	A mirroring profile was created.
Possible failure causes	· The service does not exist. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The default VXLAN is required. · The name is required and cannot exceed 255 characters. · The description cannot exceed 255 characters. · The vPort is required. · The vPort cannot be the same as the vPort in the mirroring destination profile. · Failed to add the configuration item. · No available VXLAN IDs. · The specified mirroring destination profile does not exist. · No VXLAN resources are configured, or VXLAN resources have been used up. · Southbound devices at the following IP addresses were disconnected: {IP addresses}.

Update mirroring profile

Keyword	UPDATE_MIRRORING_PROFILE_OP
Message text	Updated mirroring profile: ID: $1 Name: $2 Description: $3 Tenant ID: $4 vPort ID: $5 Destination IPv4: $6 Destination IPv6: $7 Mirroring destination template ID: $8 Direction: $9
Variable fields	$1: Mirroring profile ID. $2: Mirroring profile name. $3: Mirroring profile description. $4: Tenant ID. $5: Bound vPort ID. $6: Destination IPv4 subnet. $7: Destination IPv6 subnet. $8: Remote mirroring destination profile ID. $9: Direction.
Example	Updated mirroring profile: ID: [39e57447-76e2-4b66-894d-625428ecb8e5] Name: [flowName01] Description: [desc01] Tenant ID: [bde03f0b-bf0c-4fcd-a124-b1feb7802c71] Cloud region name:[aaa] vPort ID: [785f1a33-b1c0-48cb-bcae-dfae830ac6df] Destination IPv4: [1.2.5.0/24] Destination IPv6: [null] Mirroring destination template ID: [1942b945-756a-4c5d-b1dc-bab33d1328cc] Direction: [IN]
Explanation	A mirroring profile was edited.
Possible failure causes	· The service does not exist. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The configuration item does not exist. · The default VXLAN is required. · The name is required and cannot exceed 255 characters. · The description cannot exceed 255 characters. · The vPort cannot be edited. · The VXLAN ID cannot be modified. · The vPort cannot be the same as the vPort in the mirroring destination profile. · Failed to modify the configuration item.

Delete mirroring profile

Keyword	DELETE_MIRRORING_PROFILE_OP
Message text	Deleted mirroring profile $1.
Variable fields	$1: Mirroring profile name.
Example	Deleted mirroring profile 11.
Explanation	A mirroring profile was deleted.
Possible failure causes	· The service does not exist. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The configuration item does not exist. · Southbound devices at the following IP addresses were disconnected: {IP addresses}.

Update default VXLAN

Keyword	UPDATE_DEFAULT_VXLAN_OP
Message text	Updated default VXLAN: ID: $1 VXLAN ID: $2
Variable fields	$1: Default VXLAN pool UUID. $2: Default VLAN UUID.
Example	Updated default VXLAN: ID: [ae851830-a200-45e5-8456-e5e79b3a07d6] VXLAN ID: [11]
Explanation	The default VXLAN was modified.
Possible failure causes	· The service does not exist. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The default VXLAN is in use and cannot be edited. · Failed to modify the configuration item. · You have no privilege to perform this operation.

Create congestion management profile

Keyword	CREATE_CONGESTION_MANAGE_PROFILE_OP
Message text	Created congestion management profile: ID: $1 Name: $2 Description: $3 Scheduling mode: $4 Queues: { Queue number: $5 Priority queue group: $6 Scheduling weight: $7 Min bandwidth: $8 }
Variable fields	$1: Congestion management profile ID. $2: Congestion management profile name. $3: Congestion management profile description. $4: Scheduling mode. When the scheduling mode is SP, you do not need to configure the queue information. When the scheduling mode is WRR or WFQ, you need to configure queue information. $5: Queue ID. $6: Priority queue group. When the value is SP, you do not need to configure the scheduling weight or minimum bandwidth. When the value is 1 and the scheduling mode is WRR, you need to configure the scheduling weight and do not need to configure the minimum bandwidth. When the value is 1 and the scheduling mode is WFQ, you need to configure the scheduling weight and minimum bandwidth. $7: Scheduling weight. You need to configure this parameter when the scheduling mode is WRR and the priority queue group value is 1. $8: Minimum bandwidth. You need to configure this parameter when the scheduling mode is WFQ and the priority queue group value is 1.
Example	Created congestion management profile: ID: [dfbce4db-8e72-4fd4-a659-f6889c709e15] Name: [addTest ] Description: [111] Scheduling mode: [Packet-Count WFQ] Queues: { Queue number: [111] Priority queue group: [1] Scheduling weight: [2] Min bandwidth: [1] }
Explanation	A congestion management profile was created.
Possible failure causes	· The service does not exist. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The name is required and cannot exceed 255 characters. · The description cannot exceed 255 characters. · Failed to add the configuration item. · You have no privilege to perform this operation.

Update congestion management profile

Keyword	UPDATE_CONGESTION_MANAGE_PROFILE_OP
Message text	Updated congestion management profile: ID: $1 Name: $2 Description: $3 Scheduling mode: $4 Queues: { Queue number: $5 Priority queue group: $6 Scheduling weight: $7 Min bandwidth: $8 }
Variable fields	$1: Congestion management profile ID. $2: Congestion management profile name. $3: Congestion management profile description. $4: Scheduling mode. When the scheduling mode is SP, you do not need to configure the queue information. When the scheduling mode is WRR or WFQ, you need to configure queue information. $5: Queue ID. $6: Priority queue group. When the value is SP, you do not need to configure the scheduling weight or minimum bandwidth. When the value is 1 and the scheduling mode is WRR, you need to configure the scheduling weight and do not need to configure the minimum bandwidth. When the value is 1 and the scheduling mode is WFQ, you need to configure the scheduling weight and minimum bandwidth. $7: Scheduling weight. You need to configure this parameter when the scheduling mode is WRR and the priority queue group value is 1. $8: Minimum bandwidth. You need to configure this parameter when the scheduling mode is WFQ and the priority queue group value is 1.
Example	Updated congestion management profile: ID: [dfbce4db-8e72-4fd4-a659-f6889c709e15] Name: [modTest] Description: [01]↵ Scheduling mode: [Packet-Count WRR] Queues: { Queue number: [111] Priority queue group: [1] Scheduling weight: [2] }
Explanation	A congestion management profile was edited.
Possible failure causes	· The service does not exist. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The configuration item does not exist. · The description cannot exceed 255 characters. · Failed to modify the configuration item. · You have no privilege to perform this operation.

Delete congestion management profile

Keyword	DELETE_CONGESTION_MANAGE_PROFILE_OP
Message text	Deleted congestion management profile $1.
Variable fields	$1: Congestion management profile name.
Example	Deleted congestion management profile test
Explanation	A congestion management profile was deleted.
Possible failure causes	· The service does not exist. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The configuration item does not exist. · You have no privilege to perform this operation.

Create GTS profile

Keyword	CREATE_GTS_MANAGE_PROFILE_OP
Message text	Created GTS profile: ID: $1 Name: $2 Description: $3 Queues: { Queue number: $4 CIR $5 CBS: $6 }
Variable fields	$1: GTS profile ID. $2: GTS profile name. $3: GTS profile description. $4: Queue ID. $5: Committed information rate. $6: Committed burst size.
Example	Created GTS profile: ID: [dfbce4db-8e72-4fd4-a659-f6889c709e15] Name: [addTest ] Description: [111] Queues: { Queue number: [111] CIR: [2] CBS: [1] }
Explanation	A GTS profile was created.
Possible failure causes	· The service does not exist. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The name is required and cannot exceed 255 characters. · The description cannot exceed 255 characters. · Failed to add the configuration item. · You have no privilege to perform this operation.

Update GTS profile

Keyword	UPDATE_GTS_MANAGE_PROFILE_OP
Message text	Updated GTS profile: ID: $1 Name: $2 Description: $3 Queues: { Queue number: $4 CIR: $5 CBS: $6 }
Variable fields	$1: GTS profile ID. $2: GTS profile name. $3: GTS profile description. $4: Queue ID. $5: Committed information rate. $6: Committed burst size.
Example	Updated GTS profile: ID: [dfbce4db-8e72-4fd4-a659-f6889c709e15] Name: [addTest ] Description: [111] Queues: { Queue number: [111] CIR: [2] CBS: [1] }
Explanation	A GTS profile was edited.
Possible failure causes	· The service does not exist. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The name is required and cannot exceed 255 characters. · The description cannot exceed 255 characters. · Failed to add the configuration item. · You have no privilege to perform this operation.

Delete GTS profile

Keyword	DELETE_GTS_MANAGE_PROFILE_OP
Message text	Deleted GTS profile $1.
Variable fields	$1: GTS profile name.
Example	Deleted GTS profile 111.
Explanation	A GTS profile was deleted.
Possible failure causes	· The service does not exist. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The configuration item does not exist. · You have no privilege to perform this operation.

ServiceChain

This section contains service chain messages.

Create service chain

Keyword	CREATE_SC_OP
Message text	Created service chain $1
Variable fields	$1: Service chain information.
Example	Created service chain ID: 7fda0d76-9a0a-4129-bc53-31e3b215f854 Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: sc1 Base: Source context: Name: any Flag: ANY Destination context: Name: external Flag: EXTERNAL Source port: 0 Destination port: 0 Protocol: HTTP Service nodes: Type: FW Service ID: a3645da8-a8d3-4dce-887f-87f310dc662a Provider ID: 5236ccde-8156-43df-9825-db2473877782 Resource ID: 2758558b-0a9c-4bdd-bee7-85149c2f0c82 Management IP: 98.0.0.27 Vtep IP: 10.0.0.3 Service name: fw1 Bypass : NONE Status: ACTIVE Service path ID: 1
Explanation	A service chain was created.
Possible failure causes	· The firewall service has not been found. · The load balancer service has not been found. · Configuration recovery is in progress. · The controller is not the active leader. · The operation requires the administrator privilege. · The service chain already exists. · The specified context doesn't exist. · The specified tenant doesn't exist. · The service instance doesn't exist. · The tenant IDs for the service chain and the specified service instance are different. · The mode of the service instance is not SERVICE_CHAIN. · The tenant IDs for the service chain and the specified source or destination context are different. · The source and destination contexts are already used by another service chain. · The types of the source and destination contexts cannot both be external. · The service instance is already used by another service chain. · Only one firewall service instance is allowed in a service chain. · Only one loadbalancer service instance is allowed in a service chain. · The name cannot exceed 255 characters. · Failed to obtain fabric information. · A service instance of the PBR firewall type cannot form a service chain with service instances of other types. · A service chain can contain a maximum of 1 PBR firewall service instances. · The resource access template corresponding to the PBR firewall service instance has configuration errors or does not exist. · Not enough VLAN pools, VXLAN pools, or address pools in the resource access template corresponding to the PBR firewall service instance. · The subnets of the vRouter to which the source context belongs cannot include vPort IP addresses of service instances. · The subnets of the vRouter to which the destination context belongs cannot include vPort IP addresses of service instances. · The external subnet of the source and destination contexts cannot be empty when both source and destination contexts are external contexts. · A service instance of the Third-party type cannot form a service chain with service instances of other types. · A PBRFirewall or PBRLoadbalance service instance cannot form a service chain with service instances of other types. · The destination context cannot be external when the service type is PBRLoadbalance. · The context ID cannot be specified in any type · Unknown internal service error. · You have no privilege to perform this operation. · Cannot configure the subnet as a context member because the subnet has been bound to a vRouter enabled with multicast network capabilities. · When firewall service nodes exist in the service chain,make sure all service nodes use the two-arm connection mode. · You cannot create a vRouter link of the normal, PBR, or NBAC type, because the local or remote vRouter on the link has been bound to both a centralized vNetwork and an IPv6 subnet. · The source or destination context of the service chain cannot be any. · Duplicate external network CIDRs exist. · You can specify up to 12 external network CIDRs. · Invalid external network CIDRs. · The node is a third-party node configured with IPsec or NAT. A service chain for north-south traffic can have a maximum of one such node. · The service chain contains a third-party node with IPsec or NAT configured and an external context. Make sure no NAT-capable node exists between them. · The node is a third-party node configured with IPsec or NAT. It can be used only by a service chain for north-south traffic. · The destination context can't be External when the service type is PBRLoadbalance. · The external network CIDRs of the source and destination contexts cannot be both empty when both source and destination contexts are external contexts. · The external subnet of the source and destination contexts cannot be empty when both source and destination contexts are external contexts. · Cannot configure service chains for the vRouter, because the vRouter has been configured with IPv4 or IPv4&IPv6 application policies. · The segment ID is out of range. · The source context already has onboarded vPorts in an associated external network. · The destination context already has onboarded vPorts in an associated external network. · The source context has a vRouter bound to a vPort in an external network. · The destination context has a vRouter bound to a vPort in an external network. · The source and destination contexts overlap with the source and destination contexts used by another service chain. · The context uses primary/backup gateway deployment mode. Make sure the associated vRouter is bound to two gateway members or external subnets. · The context uses single gateway deployment mode. Make sure the associated vRouter is bound to one gateway member or external subnet. · One or more selected third-party service instances are invalid. · PBR firewall service instances of a service chain must belong to different virtual devices. · Failed to bind the context to the service chain, because a vRouter associated with this context has been bound to an external EPG containing external network CIDR 0.0.0.0/0.

Update service chain

Keyword	UPDATE_SC_OP
Message text	Updated service chain $1
Variable fields	$1: Service chain information.
Example	Updated service chain ID: 7fda0d76-9a0a-4129-bc53-31e3b215f854 Tenant ID: ffffffff-0000-0000-0000-000000000001 Name: sc1 Base: Source context: Name: any Flag: ANY Destination context: Name: external Flag: EXTERNAL Source port: 0 Destination port: 0 Protocol: HTTP Service nodes: Type: FW Service ID: a3645da8-a8d3-4dce-887f-87f310dc662a Provider ID: 5236ccde-8156-43df-9825-db2473877782 Resource ID: 2758558b-0a9c-4bdd-bee7-85149c2f0c82 Management IP: 98.0.0.27 Vtep IP: 10.0.0.3 Service name: fw1 Bypass : NONE Status: ACTIVE Service path ID: 1
Explanation	A service chain was edited.
Possible failure causes	· The service of the service chain has not been found. · Configuration recovery is in progress. · The controller is not the active leader. · The operation requires the administrator privilege. · The configuration item doesn't exist. · The specified context doesn't exist. · The service instance doesn't exist. · The tenant IDs for the service chain and the specified service instance are different. · The mode of the service instance is not SERVICE_CHAIN. · The tenant IDs for the service chain and the specified source or destination context are different. · The source and destination contexts are already used by another service chain. · The types of the source and destination contexts can't both be external. · The service instance is already used by another service chain. · Only one firewall service instance is allowed in a service chain. · Only one loadbalancer service instance is allowed in a service chain. · The name cannot exceed 255 characters. · Failed to obtain fabric information. · A service instance of the PBR firewall type can't form a service chain with service instances of other types. · A service chain can contain a maximum of 1 PBR firewall service instances. · The resource access template corresponding to the PBR firewall service instance has configuration errors or does not exist. · Not enough VLAN pools, VXLAN pools, or address pools in the resource access template corresponding to the PBR firewall service instance. · The subnets of the vRouter to which the source context belongs cannot include vPort IP addresses of service instances. · The subnets of the vRouter to which the destination context belongs cannot include vPort IP addresses of service instances. · The external subnet of the source and destination contexts cannot be empty when both source and destination contexts are external contexts. · Unknown internal service error. · You have no privilege to perform this operation. · Cannot configure the subnet as a context member because the subnet has been bound to a vRouter enabled with multicast network capabilities. · When firewall service nodes exist in the service chain,make sure all service nodes use the two-arm connection mode. · You cannot create a vRouter link of the normal, PBR, or NBAC type, because the local or remote vRouter on the link has been bound to both a centralized vNetwork and an IPv6 subnet. · The source or destination context of the service chain cannot be any. · Duplicate external network CIDRs exist. · You can specify up to 12 external network CIDRs. · Invalid external network CIDRs. · The node is a third-party node configured with IPsec or NAT. A service chain for north-south traffic can have a maximum of one such node. · The service chain contains a third-party node with IPsec or NAT configured and an external context. Make sure no NAT-capable node exists between them. · The node is a third-party node configured with IPsec or NAT. It can be used only by a service chain for north-south traffic. · The destination context can't be External when the service type is PBRLoadbalance. · The external network CIDRs of the source and destination contexts cannot be both empty when both source and destination contexts are external contexts. · The external subnet of the source and destination contexts cannot be empty when both source and destination contexts are external contexts. · Cannot configure service chains for the vRouter, because the vRouter has been configured with IPv4 or IPv4&IPv6 application policies. · The segment ID is out of range. · The source context already has onboarded vPorts in an associated external network. · The destination context already has onboarded vPorts in an associated external network. · The source context has a vRouter bound to a vPort in an external network. · The destination context has a vRouter bound to a vPort in an external network. · The source and destination contexts overlap with the source and destination contexts used by another service chain. · The context uses primary/backup gateway deployment mode. Make sure the associated vRouter is bound to two gateway members or external subnets. · The context uses single gateway deployment mode. Make sure the associated vRouter is bound to one gateway member or external subnet. · One or more selected third-party service instances are invalid. · PBR firewall service instances of a service chain must belong to different virtual devices. · Failed to bind the context to the service chain, because a vRouter associated with this context has been bound to an external EPG containing external network CIDR 0.0.0.0/0.

Delete service chain

Keyword	DELETE_SC_OP
Message text	Deleted service 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 service of the service chain has not been found. · Configuration recovery is in progress. · The controller is not the active leader. · The operation requires the administrator privilege. · The configuration item doesn't exist. · You have no privilege to perform this operation.

Create context

Keyword	CREATE_CONTEXT_OP
Message text	Created context $1
Variable fields	$1: Context information.
Example	Created context id: 764a2ebe-eb47-43f7-98f3-e492b7b8ebeb tenant id: ffffffff-0000-0000-0000-000000000001 name: net1 context base: type: NETWORK networks: e3672c88-04db-4c85-bd1c-3e8b869c94b3 53b5199d-7181-41f6-8f8a-4637603a9e04 tenant name: default in chain: false
Explanation	A context was created.
Possible failure causes	· The service of the service chain has not been found. · Configuration recovery is in progress. · The controller is not the active leader. · The operation requires the administrator privilege. · The context already exists. · The specified tenant doesn't exist. · The specified vPort doesn't exist. · The tenant IDs for the context and the specified vPort are different. · The specified vSubnet doesn't exist. · The tenant IDs for the context and the specified vSubnet are different. · The specified vNetwork doesn't exist. · The tenant IDs for the context and the specified vNetwork are different. · The specified external subnet does not exist. · The specified subnet is not an external subnet. · The context uses single gateway deployment mode.Please specify one and only one external subnet, or do not specify any external subnets. · The context uses primary/backup gateway deployment mode. Please specify two and only two external subnets, or do not specify any external subnets. · The context uses primary/backup gateway deployment mode. Make sure the associated vRouter is bound to two gateway members or external subnets. · The context uses single gateway deployment mode. Make sure the associated vRouter is bound to one gateway member or external subnet. · The name cannot exceed 255 characters. · The specified IP address for the context of the Manual type cannot be broadcast, multicast, or loopback address. · The vPort resource cannot be used because it is created by PBR service chain. · The subnet resource cannot be used because it is created by PBR service chain. · The network resource cannot be used because it is created by PBR service chain. · The external subnet cannot be configured as a context member when the context type is subnet. · You have no privilege to perform this operation. · Duplicate external network CIDRs exist. · You can specify up to 12 external network CIDRs. · Invalid external network CIDRs. · Only external contexts support exception CIDRs. · Make sure all specified exception CIDRs are valid. · Make sure the context does not have overlapping exception CIDRs. · Exception CIDRs support only IPv4 addresses. · The exception CIDRs must be within the ranges of the external network CIDRs. · You can specify only the vRouter UUID for the context of the router type. · Duplicate vRouter UUIDs exist. · The tenant UUIDs for the context and the specified vRouter are different. · A PBR-type vRouter cannot be specified for a router-type context. · A context cannot contain vPorts of external networks.

Update context

Keyword	UPDATE_CONTEXT_OP
Message text	Updated context $1
Variable fields	$1: Context information.
Example	Updated context id: 764a2ebe-eb47-43f7-98f3-e492b7b8ebeb tenant id: ffffffff-0000-0000-0000-000000000001 name: net1 context base: type: NETWORK networks: e3672c88-04db-4c85-bd1c-3e8b869c94b3 53b5199d-7181-41f6-8f8a-4637603a9e04 tenant name: default in chain: false
Explanation	A context was edited.
Possible failure causes	· The service of the service chain has not been found. · Configuration recovery is in progress. · The controller is not the active leader. · The operation requires the administrator privilege. · The configuration item doesn't exist. · The context is being used by a service chain. · The specified vPort doesn't exist. · The tenant IDs for the context and the specified vPort are different. · The specified vSubnet doesn't exist. · The tenant IDs for the context and the specified vSubnet are different. · The specified vNetwork doesn't exist. · The tenant IDs for the context and the specified vNetwork are different. · The specified external subnet does not exist. · The specified subnet is not an external subnet. · The context uses single gateway deployment mode.Please specify one and only one external subnet, or do not specify any external subnets. · The context uses primary/backup gateway deployment mode. Please specify two and only two external subnets, or do not specify any external subnets. · The context uses primary/backup gateway deployment mode. Make sure the associated vRouter is bound to two gateway members or external subnets. · The context uses single gateway deployment mode. Make sure the associated vRouter is bound to one gateway member or external subnet. · The name cannot exceed 255 characters. · You have no privilege to perform this operation. · The external subnet cannot be configured as a context member when the context type is subnet. · The source or destination context of the service chain cannot be any. · Duplicate external network CIDRs exist. · You can specify up to 12 external network CIDRs. · Invalid external network CIDRs. · The destination context can't be External when the service type is PBRLoadbalance. · The external network CIDRs of the source and destination contexts cannot be both empty when both source and destination contexts are external contexts. · The external subnet of the source and destination contexts cannot be empty when both source and destination contexts are external contexts. · The context has been specified for a service chain. Make sure the context members do not use the vRouters of any IPv4 or IPv4 & IPv6 application policies. · Only external contexts support exception CIDRs. · Make sure all specified exception CIDRs are valid. · Make sure the context does not have overlapping exception CIDRs. · Exception CIDRs support only IPv4 addresses. · The exception CIDRs must be within the ranges of the external network CIDRs. · You can specify only the vRouter UUID for the context of the router type. · Duplicate vRouter UUIDs exist. · The tenant UUIDs for the context and the specified vRouter are different. · A PBR-type vRouter cannot be specified for a router-type context. · A context cannot contain vPorts of external networks. · The source and destination contexts overlap with the source and destination contexts used by another service chain. · Failed to change the context type, because the context has been used by a service chain and an associated vRouter has been bound to an external EPG containing external network CIDR 0.0.0.0/0.

Delete context

Keyword	DELETE_CONTEXT_OP
Message text	Deleted context $1.
Variable fields	$1: Context UUID.
Example	Deleted context ab7a8b0f-9704-4ba0-8411-b689c98ace7e
Explanation	A context was deleted.
Possible failure causes	· The service of the service chain has not been found. · Configuration recovery is in progress. · The controller is not the active leader. · The operation requires the administrator privilege. · The configuration item doesn't exist. · The context is being used by a service chain. · You have no privilege to perform this operation. · Cannot configure the subnet as a context member because the subnet has been bound to a vRouter enabled with multicast network capabilities.

Create service path

Keyword	CREATE_SERVICE_PATH_OP
Message text	Created service path $1
Variable fields	$1: Service path configuration information.
Example	Created service path ID: d8dab9d3-d91b-413d-9108-edb60d47a29e Name: service path1 Tenant ID: ffffffff-0000-0000-0000-000000000001 Tenant name: default Service nodes: Type: PBR_LB Service ID: 9496f44f-4326-4a71-baca-1b7e2df5780d Provider ID: 6a8eb188-96f6-4f65-94a5-75f28e7bbdac Resource ID: 63a76194-132f-4d2c-9055-c7389b7e9218 Management IP: 98.0.14.222 Service name: lb VIP: [20.0.0.100] Real IP: [20.0.0.0/24] Service path ID: 1 Used in service chains: IP version: 6
Explanation	A service path was created.
Possible failure causes	· The firewall service has not been found. · The load balancer service has not been found. · Configuration recovery is in progress. · The controller is not the active leader. · The operation requires the administrator privilege. · The service chain already exists. · The specified tenant doesn't exist. · The service instance doesn't exist. · Invalid IP version. · When multiple service nodes exist in the service path, make sure all service nodes use the two-arm connection mode. · The service instance is already used by another service chain. · Only one loadbalancer service instance is allowed in a service path. · The name cannot exceed 255 characters. · Failed to obtain fabric information. · A resource is required to be bound with each PBRFirewall or PBRLoadbalance service instance. · A service path can contain a maximum of 16 PBRFirewall or PBRLoadbalance service instances. · Duplicated service instances exist in the service path. · A service path can contain a maximum of 16 third-party service instances. · A service instance of the Third-party type cannot form a service path with service instances of other types. · A PBRFirewall or PBRLoadbalance service instance cannot form a service chain with service instances of other types. · You cannot add a shared third-party service node to the service path. · Please specify a resource for the service node. · Make sure the service node and the resource access template use the same connection mode. · Make sure the third-party service path and all service devices in it use the same IP version. · Make sure no EPGs contain any member IP address of the EPG automatically generated upon service path creation. · Make sure a vRouter is bound to each of the subnets attached to the ingress and egress vPorts. · Unknown internal service error. · You have no privilege to perform this operation. · A subnet of the third-party service device is not bound to a vNetwork. · A subnet of the third-party service device is not bound to a vRouter. · One or more selected third-party service instances are invalid. · The service path cannot contain both a third-party LB service node and a controller-managed LB service node. · The service path does not support third-party service nodes with IPsec or SNAT settings. · A service path can contain a maximum of 16 service instances. · PBR firewall service instances of a service path must belong to different virtual devices.

Update service path

Keyword	UPDATE_SERVICE_PATH_OP
Message text	Updated service path $1
Variable fields	$1: Service path configuration information.
Example	Updated service path ID: d8dab9d3-d91b-413d-9108-edb60d47a29e Name: service path1 Tenant ID: ffffffff-0000-0000-0000-000000000001 Tenant name: default Service nodes: Type: PBR_LB Service ID: 9496f44f-4326-4a71-baca-1b7e2df5780d Provider ID: 6a8eb188-96f6-4f65-94a5-75f28e7bbdac Resource ID: 63a76194-132f-4d2c-9055-c7389b7e9218 Management IP: 98.0.14.222 Service name: lb VIP: [20.0.0.100] Real IP: [20.0.0.0/24] Service path ID: 1 Used in service chains: ID: c8a55a80-72e9-49c0-a5da-478b158042ba Source contexts: epg1 Destination contexts: epg2 Invoker module name: NBAC IP version: 4
Explanation	A service path was edited.
Possible failure causes	· The firewall service has not been found. · The load balancer service has not been found. · Configuration recovery is in progress. · The controller is not the active leader. · The operation requires the administrator privilege. · The service chain already exists. · The specified tenant doesn't exist. · The service instance doesn't exist. · The tenant ID cannot be modified. · The ID cannot be modified. · Invalid IP version. · When multiple service nodes exist in the service path, make sure all service nodes use the two-arm connection mode. · The service instance is already used by another service chain. · Only one loadbalancer service instance is allowed in a service chain. · The name cannot exceed 255 characters. · Failed to obtain fabric information. · A resource is required to be bound with each PBRFirewall or PBRLoadbalance service instance. · A service chain can contain a maximum of 16 PBRFirewall or PBRLoadbalance service instances. · Duplicated service instances exist in the service chain. · A service chain can contain a maximum of 16 third-party service instances. · A service instance of the Third-party type cannot form a service chain with service instances of other types. · A PBRFirewall or PBRLoadbalance service instance cannot form a service chain with service instances of other types. · You cannot add a shared third-party service node to the service path. · You cannot change the IP version of the service path, because it has been specified in an exception rule. · Please specify a resource for the service node. · Make sure the service node and the resource access template use the same connection mode. · Make sure the third-party service path and all service devices in it use the same IP version. · The service path name cannot be modified. · Make sure no EPGs contain any member IP address of the EPG automatically generated upon service path creation. · Make sure a vRouter is bound to each of the subnets attached to the ingress and egress vPorts · Unknown internal service error · You have no privilege to perform this operation · A subnet of the third-party service device is not bound to a vNetwork · A subnet of the third-party service device is not bound to a vRouter. · One or more selected third-party service instances are invalid. The service path cannot contain both a third-party LB service node and a controller-managed LB service node. · The service path does not support third-party service nodes with IPsec or SNAT settings. · A service path can contain a maximum of 16 service instances. · PBR firewall service instances of a service path must belong to different virtual devices. · When the source or destination EPG is an external EPG, the service path can contain only two-arm service nodes. · When the source and destination EPGs are the same, make sure the service path contains only a one-arm service node. · The service path cannot contain PBRLoadbalance service instances. This is because it has been specified for an exception rule in an application policy, and the exception rule uses an external destination EPG.

Delete service path

Keyword	DELETE_SERVICE_PATH_OP
Message text	Deleted service path $1
Variable fields	$1: Service path UUID.
Example	Deleted service path service path1
Explanation	A service path was deleted.
Possible failure causes	· The service has not been found. · Configuration recovery is in progress. · The controller is not the active leader. · The operation requires the administrator privilege. · The configuration item doesn't exist. · You have no privilege to perform this operation. · The service chain has been used by a redirection rule and cannot be deleted.

Create detection task

Keyword	CREATE_DETECT_OP
Message text	Created detection task $1
Variable fields	$1: Link detection task settings.
Example	Created detection task serviceGraphId:[1207a043-3d28-41d5-b5e6-3e4a12f40c42] type:[MANUAL] period:[0] startTime:[285257789920110] endTime:[285268889383909] isDetectEnd:[true] service graph: serviceInstanceId: 26009cd3-38b5-4e77-acd9-d5d6bdc047bc ingressPortId: 569cdf15-73d1-4c9c-ac4b-625395c32040 ingressPortIpv4Address: 12.0.1.1 ingressPortIpv4Status: DOWN ingressDeviceSet egressPortId: c877acb0-3740-404d-918c-6d5602b604e9 egressPortIpv4Address: 12.0.1.5 egressPortIpv4Status: DOWN egressPortIpv6Address egressPortIpv6Status ingressPortIpv6Address ingressPortIpv6Status
Explanation	A link detection task was created.
Possible failure causes	· The service has not been found. · Configuration recovery is in progress. · The controller is not the active leader. · The detection task already exists. · Make sure the detection type is manual or periodic. · Make sure the service path ID or service chain ID is specified. · You can specify only the service path ID or service chain ID for the detection task, not both. · Invalid detection interval. · Please specify a detection interval. · The specified service path does not exist. · The specified service chain does not exist. · Please specify the detection type.

Update detection task

Keyword	UPDATE_DETECT_OP
Message text	Updated detection task $1
Variable fields	$1: Link detection task settings.
Example	Updated detection task serviceGraphId:[1207a043-3d28-41d5-b5e6-3e4a12f40c42] type:[AUTO] period:[20] startTime:[280569280462205] endTime:[0] isDetectEnd:[false] service graph: serviceInstanceId: 26009cd3-38b5-4e77-acd9-d5d6bdc047bc ingressPortId: 569cdf15-73d1-4c9c-ac4b-625395c32040 ingressPortIpv4Address: 12.0.1.1 ingressPortIpv4Status: DETECTING egressPortId: c877acb0-3740-404d-918c-6d5602b604e9 egressPortIpv4Address: 12.0.1.5 egressPortIpv4Status: DETECTING ingressDev...
Explanation	A link detection task was edited.
Possible failure causes	· The service has not been found. · Configuration recovery is in progress. · The controller is not the active leader. · Invalid detection interval. · The service path ID cannot be edited. · Please specify a detection interval. · The service chain ID cannot be edited. · The detection type cannot be edited. · Please specify the detection type. · The detection interval does not take effect on a manual detection task.

Delete detection task

Keyword	DELETE_DETECT_OP
Message text	Deleted detection task for $1 $2
Variable fields	$1: Service chain or service path. $2: Name of the service chain or service path.
Example	Deleted detection task for service path fw.
Explanation	A link detection task was deleted.
Possible failure causes	· The service has not been found. · Configuration recovery is in progress. · The controller is not the active leader. · The configuration item doesn't exist.

Update service chain settings for a tenant

Keyword	UPDATE_SC_TENANT_CONFIG_OP
Message text	Updated service chain settings for a tenant $1.
Variable fields	$1: Global service chain settings for the tenant.
Example	Updated service chain settings for a tenant Tenant ID: ffffffff-0000-0000-0000-000000000001 Set priority: true
Explanation	The global service chain settings were edited for a tenant.
Possible failure causes	· The configuration item doesn't exist. · Failed to modify the configuration item. · Invalid JSON format. · The tenant ID must be specified. · Invalid tenant ID. · You cannot turn off this option, because some service chains have priority settings.

SIMULATION

This section contains simulation messages.

Create network-wide impact analysis task

Keyword	CREATE_NETWORK_WIDE_IMPACT_ANALYSIS_OP
Message text	Created network-wide impact analysis task: $1.
Variable fields	$1: Network impact analysis parameters.
Example	Created network-wide impact analysis task: { "network_analysis": { "tenant_id": "aca81959-a3a9-4928-a30e-3784a7dfdbf4", "type": "simulation_after" } }
Explanation	A network-wide impact analysis task was created.
Possible failure causes	· The request body cannot be empty. · The tenantId parameter cannot be empty when type is simulation_after. · The tenantId parameter does not match regex. · The type parameter range must be simulation_before,simulation_after. · The controller is unreachable. · The vPort cannot be empty. · Internal error. · Failed to obtain resources.

Refresh network-wide impact analysis task

Keyword	REFRESH_NETWORK_WIDE_ANALYSIS_DATA
Message text	Refreshed network-wide analysis data: $1.
Variable fields	$1: Network impact analysis parameters.
Example	Refreshed network-wide analysis data: { "network_analysis": { "tenant_id": "e6ee5063-05f4-40e8-8e27-e909b0ce7ff2" } }
Explanation	Network-wide impact analysis data was refreshed.
Possible failure causes	· Invalid parameter. · Internal error.

Create connectivity test task

Keyword	CREATE_CONNECTIVITY_TEST_TASK_OP
Message text	Created connectivity test task: $1.
Variable fields	$1: Connectivity test information.
Example	Created connectivity test task: { "connectivityDetectId": "5ed58808-3796-4dfa-9a71-bdc404a1d9b3", "connectivity_detect": { "protocol": "6", "ori_device": [ { "src_ip": "81.1.1.2", "type": "vPort", "vni": "81", "origin_device": "172.20.8.114", "inport": "WGE1/0/2", "inDcport": "WGE1/0/2", "src_port": "10000", "subnetId": "3d120566-1a15-4f66-a31d-37919b2cc690" } ], "dst_device": [ { "dst_ip": "80.1.1.2", "type": "vPort", "dst_port": "50000", "dst_device": "172.20.8.110", "dstDcInport": "WGE1/0/2", "dst_inport": "WGE1/0/2", "subnetId": "f034cc3f-a536-4c3f-a698-0335eebfba6c" } ] }, "taskNum": "1" }
Explanation	A connectivity test check was created.
Possible failure causes	· The system service does not respond. · Invalid parameter. · Failed to obtain resources. · Failed to enable DC detection. · Failed to obtain resources.

Stop simulation task

Keyword	STOP_SIMULATION_OP
Message text	Stopped simulation task: $1.
Variable fields	$1: Simulation task information.
Example	Stopped simulation task: simulation_before
Explanation	A simulation task was stopped.
Possible failure causes	· The request body cannot be empty. · The operation does not exist.

Enable tenant design mode

Keyword	ENABLE_TENANT_DESIGN_STATE_OP
Message text	Enabled design mode for tenant: $1
Variable fields	$1: Tenant ID.
Example	Enabled design mode for tenant: 95a541c8-dcb4-4d18-8a8c-16d79ff524c9
Explanation	The design mode was enabled for a tenant.
Possible failure causes	· The specified tenant does not exist on the controller. · Internal error. · The (parameter) parameter value does not match the regular expression. · Cannot enable the design mode for the tenant, because the design mode has been enabled for another tenant. · Failed to enable the design mode for the tenant. · The controller is synchronizing data to all tenants in design mode. Please try again later. · The design mode has been enabled for the tenant. · No simulation network is built for the tenant.

Disable tenant design mode

Keyword	ENABLE_TENANT_DESIGN_STATE_OP
Message text	Disabled design mode for tenant: $1
Variable fields	$1: Tenant ID.
Example	Disabled design mode for tenant: e6ee5063-05f4-40e8-8e27-e909b0ce7ff2
Explanation	The design mode was disabled for a tenant.
Possible failure causes	· The (parameter) parameter value does not match the regular expression. · Internal error. · The design mode has been disabled for the tenant. · Failed to disable the design mode for the tenant. · Another user is processing this resource. Please try again later.

Create vNetwork

Keyword	SIMULATION_CREATE_NETWORK_OP
Message text	Created vNetwork for simulation: $1
Variable fields	$1: vNetwork request body.
Example	Created vNetwork for simulation: { "networks":[ { "id":null, "name":"Tokyo", "tenant_id":null, "status":null, "shared":false, "admin_state_up":null, "subnets":null, "arp_send_rate":null, "distributed":false, "dhcp_relay":{ "server_ips":[ "192.168.0.254" ] }, "provider:network_type":"VXLAN", "provider:original_network_type": "VXLAN", "provider:domain":"ffffffff-0000-0000-0000-000000000001", "provider:segmentation_id":null, "router:external": false, "segments": [], "arp_ctrl": { "arp_flooding":"DEFAULT", "arp_proxy":"DEFAULT", "arp_to_controller":"DEFAULT" }, "dhcp_ctrl":{ "dhcp_to_controller":"DEFAULT" }, "floodingdisable_ctrl":{ "unknownunicast":"DEFAULT", "multicast":"DEFAULT", "broadcast":"DEFAULT" }, "rarp_ctrl":{ "rarp_to_controller":"ENABLE", "rarp_flooding":"DISABLE" }, "force_flat":false, "vswitch_flood_and_learn": "DEFAULT", "nd_ctrl": { "nsna_flooding": "DEFAULT", "nd_proxy": "DEFAULT", "nsna_to_controller": "DEFAULT", "rsra_to_controller": "DEFAULT", "rsra_flooding": "DEFAULT" }, "dhcpv6_ctrl": { "dhcpv6_to_controller": "DEFAULT" }, "mac_advertising": "DEFAULT" } ] }
Explanation	A vNetwork was created.
Possible failure causes	· Invalid JSON format. · The request body cannot be empty. · The (parameter) parameter value does not match the regular expression. · Another user is processing this resource. Please try again later. · Invalid parameter. · The design mode has been disabled for the tenant. · Internal error. · The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid tenant ID. · The segment ID number 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 tenant. · 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. · The provider field and the segment field cannot be both configured. · The flat type external network cannot be configured with segment. · The ID already exists. · The value of the network type can only be VLAN. · The network type is required. · The segment ID is not in the VLAN pool. · The physical network is required. · The specified composite gateway doesn't exist. · You can create segments only for external networks. · The segment name cannot exceed 255 characters. · The description cannot exceed 255 characters. · Invalid segment UUID. · The external network has been bound to a vRouter. · Invalid segment ID. · The value of the MTU must be an integer in the range of 68 to 65535. · The specified QoS policy doesn't exist. · Unknown error. · Invalid value in the physical_network field. · A vNetwork cannot use directly connected mode. · When the Network Cloud feature is disabled, directly connected external networks are not supported. · Only internal network can be configured as resource operating mode. · You have no privilege to perform this operation. · Cannot bind the DHCP host group to an external network. · The DHCP host group does not exist. · The RT generated based on the segment ID of the vNetwork conflicts with the import RT of the Layer 2 DC interconnect associated with the vNetwork. · The RT generated based on the segment ID of the vNetwork conflicts with the export RT of the Layer 2 DC interconnect associated with the vNetwork. · The RT reserved for a fabric connection on the vNetwork conflicts with the import RT of the Layer 2 DC interconnect associated with the vNetwork. · The RT reserved for a fabric connection on the vNetwork conflicts with the export RT of the Layer 2 DC interconnect associated with the vNetwork. · The RT generated based on the segment ID of the vNetwork conflicts with the import RT of the Layer 3 DC interconnect associated with the vNetwork. · The RT generated based on the segment ID of the vNetwork conflicts with the export RT of the Layer 3 DC interconnect associated with the vNetwork. · The RT reserved for a fabric connection on the vNetwork conflicts with the import RT of the Layer 3 DC interconnect associated with the vNetwork. · The RT reserved for a fabric connection on the vNetwork conflicts with the export RT of the Layer 3 DC interconnect associated with the vNetwork. · Invalid auto port creation configuration. · You cannot bind the DHCP host group to the vNetwork. A network node in the DHCP host group has already created a DHCP vPort for the vNetwork. · To disable preprovisioning, make sure all its dependent features use their default settings. For information about these features, see online help. · Make sure the segment ID (VLAN ID) is not in a tenant carrier network VLAN pool and vRouter interconnection network VLAN pool when the external network or vNetwork type is VLAN. · You cannot change the status of the multicast network feature when the network segmentation feature is enabled. · The segment ID cannot be identical to a VXLAN ID in a VXLAN pool or the VXLAN ID reserved for the automation template and the DR system.

Update vNetwork

Keyword	SIMULATION_UPDATE_NETWORK_OP
Message text	Updated vNetwork for simulation: $1
Variable fields	$1: vNetwork ID.
Example	Updated vNetwork for simulation: 1d3a2b14-5ea2-452e-b4fd-16b684675178.
Explanation	A vNetwork was edited.
Possible failure causes	· Invalid JSON format. · The request body cannot be empty. · The (parameter) parameter value does not match the regular expression. · Another user is processing this resource. Please try again later. · Invalid parameter. · The design mode has been disabled for the tenant. · Internal error. · The request is invalid. · 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. · Cannot segment the external network because it has been bound to a vRouter that is bound to a gateway resource configured with a priority. · The value of the MTU must be an integer in the range of 68 to 65535. · The specified QoS policy doesn't exist. · Invalid value in the physical_network field. · A vNetwork cannot use directly connected mode. · When the Network Cloud feature is disabled, directly connected external networks are not supported. · You have no privilege to perform this operation. · Cannot enable multicast network capabilities for the vNetwork because the vNetwork has been bound to a Layer 2 DC interconnect. · Cannot bind the DHCP host group to an external network. · The DHCP host group does not exist. · Invalid auto port creation configuration. · You cannot bind the DHCP host group to the vNetwork. A network node in the DHCP host group has already created a DHCP vPort for the vNetwork. · The vNetwork is an interface-specific multicast network. You cannot disable its multicast capabilities. · To disable preprovisioning, make sure all its dependent features use their default settings. For information about these features, see online help. · You cannot change the status of the multicast network feature when the network segmentation feature is enabled.

Delete vNetwork

Keyword	SIMULATION_DELETE_NETWORK_OP
Message text	Deleted vNetwork for simulation: $1
Variable fields	$1: vNetwork ID.
Example	Deleted vNetwork for simulation: 1d3a2b14-5ea2-452e-b4fd-16b684675178
Explanation	A vNetwork was deleted.
Possible failure causes	· Another user is processing this resource. Please try again later. · Invalid parameter. · The design mode has been disabled for the tenant. · Internal error. · The request is invalid. · 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. · You have no privilege to perform this operation. · Cannot delete the vNetwork because it has been bound to an OSPF or OSPFv3 policy.

Create subnet

Keyword	SIMULATION_CREATE_SUBNET_OP
Message text	Created subnet for simulation: $1
Variable fields	$1: Subnet request body.
Example	Created subnet for simulation: { "subnets": [ { "name":"sample_subnet1", "network_id":"d65e6edc-4ea0-4d0d-92bf-a2813401b8cb", "segment_id":"d65e6edc-4ea0-4d0d-92bf-a28134013456", "cidr":"192.168.100.0/24", "gateway_ip":"192.168.100.1", "enable_dhcp":true, "allocation_pools": [ { "start": "192.168.100.2", "end": "192.168.100.3" }, { "start": "192.168.100.4", "end": "192.168.100.5" } ], "dhcp_options": { "server_identifier":"192.168.100.254", "domain_name":"dhcp_domain" }, "dns_nameservers": [], "host_routes": [ { "destination":"10.20.30.0/24", "nexthop":"192.168.100.12" }, { "destination":"40.50.60.0/25", "nexthop":"192.168.100.13" } ], "leaseTime": { "day":365 } }, { "name":"sample_subnet2", "network_id":"d65e6edc-4ea0-4d0d-92bf-a2813401b8cb", "cidr":"192.168.200.0/24", "gateway_ip":"192.168.200.1", "dhcp_options": { "server_identifier":"192.168.200.254", "domain_name":"dhcp_domain" } } ] }
Explanation	A subnet was created.
Possible failure causes	· Invalid JSON format. · The request body cannot be empty. · The (parameter) parameter value does not match the regular expression. · Another user is processing this resource. Please try again later. · Invalid parameter. · The design mode has been disabled for the tenant. · Internal error. · The request is invalid. · 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. · Please check the DHCP address pool for overlapping subnets. · 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. · Failed to add subnets because the segment ID of the external network is empty and no segments exist. · You must associate the subnet with a segment because the external network of the subnet has multiple segments. · The subnet and its associated segment must belong to the same external network. · The segment doesn't exist. · Unknown error. · You have no privilege to perform this operation. · The NQA profile has been bound to another external network. · The specified NQA profile has been bound to another service resource. · The specified NQA profile does not exist. · Cannot bind the subnet to an NQA profile. The border gateway in the subnet has been bound to a track entry. · Failed to add the subnet to the vNetwork, because it overlaps with a network bound to the context in another service chain. · A vNetwork supports only one primary IP.

Update subnet

Keyword	SIMULATION_UPDATE_SUBNET_OP
Message text	Updated subnet for simulation: $1
Variable fields	$1: Subnet ID.
Example	Updated subnet for simulation: 279cadb6-12f8-431f-9f06-200d9c01e788
Explanation	A subnet was edited.
Possible failure causes	· Invalid JSON format. · The request body cannot be empty. · The (parameter) parameter value does not match the regular expression. · Another user is processing this resource. Please try again later. · Invalid parameter. · The design mode has been disabled for the tenant. · Internal error. · The request is invalid. · 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. · Please check the DHCP address pool for overlapping subnets. · 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 to 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. · The segment UUID can't be deleted or modified. · An IP address in the DHCP address pool has been automatically assigned to an online vPort. The DHCP address pool must still contain the IP address after being edited. · The DHCP address pool cannot contain IP addresses that have been manually assigned to online vPorts. · An IP address in the DHCP address pool has been automatically assigned to an online vPort. The DHCP address pool must still contain the IP address after being edited. · The DHCP address pool cannot contain IP addresses that have been manually assigned to online vPorts. · Unknown error. · You have no privilege to perform this operation. · Cannot edit the primary IP allocation setting for a subnet if the subnet is already used for primary IP allocation. · Cannot edit the primary IP allocation setting for a subnet if the subnet is already used for primary IP allocation. · The gateway IP address has been used as the primary IP address. · The external subnet contains an IP address that has been assigned to a vPort. You cannot bind the external subnet to an NQA profile. · The NQA profile has been bound to another external network. · The specified NQA profile has been bound to another service resource. · The specified NQA profile does not exist. · Cannot bind the subnet to an NQA profile. The border gateway in the subnet has been bound to a track entry. · A vNetwork supports only one primary IP.

Delete subnet

Keyword	SIMULATION_DELETE_SUBNET_OP
Message text	Deleted subnet for simulation: $1
Variable fields	$1: Subnet request body.
Example	Deleted subnet for simulation: { "subnets": [ { "id": "279cadb6-12f8-431f-9f06-200d9c01e788" }, { "id": "da0bd073-7b3a-4277-b14b-2bfe6e3b15bd" }] }
Explanation	A subnet was deleted.
Possible failure causes	· Invalid JSON format. · The request body cannot be empty. · The (parameter) parameter value does not match the regular expression. · Another user is processing this resource. Please try again later. · Invalid parameter. · The design mode has been disabled for the tenant. · Internal error. · 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. · You have no privilege to perform this operation · The vNetwork is an interface-specific multicast network. You cannot unbind its only subnet from the vRouter.

Create router

Keyword	SIMULATION_CREATE_ROUTER_OP
Message text	Created router for simulation: $1
Variable fields	$1: vRouter request body.
Example	Created router for simulation: { "routers": [ { "id": "12faf8ab-88d8-4ae8-bd52-426d47860607", "tenant_id": "ffffffff-0000-0000-0000-000000000001", "name": "vRouter3", "admin_state_up": false, "bgp_peers": [], "cidrs": [], "ecmp_number": null, "aggregate_cidrs": [], "provider:domain": "ffffffff-0000-0000-0000-000000000001", "provider:vpninstance_name": "ivbsan26o9bkbqki2dl3oc1g7", "disable_internal_l3flow_offload": false, "import_default_route": false, "import_static_route": false, "provider:segmentation_id": 12345, "tags": [ "GW:8140a7ad-2e41-421a-b8af-325a0f5369aa:1" ], "empty_external_gwinfo_action": true, "direct_external": false } ] }
Explanation	A vRouter was created on the specified tenant.
Possible failure causes	· Invalid JSON format. · The request body cannot be empty. · The (parameter) parameter value does not match the regular expression. · Another user is processing this resource. Please try again later. · Invalid parameter. · The design mode has been disabled for the tenant. · Internal error. · The request is invalid. · 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 number 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 cannot be configured with the same summary route network. · The vRouters using the public VRF cannot be bound to the same service device 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 bytes. · 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. · The external network bound to the vRouter does not have segments. The vRouter can be bound only to one IPv4 subnet. · The border gateways to the IPv4 and IPv6 external subnets are located on the same interface. You must configure them with the same segment ID. · The external network egress IP has been bound to another vRouter. To bind the current vRouter to the external network egress IP, you must make sure the current vRouter has exactly the same external subnet bindings as that vRouter. · Unknown error · The address pool does not exist or no IP addresses are available in the address pool. · The segment or border gateway already has a priority. · If a vRouter is bound to both a gateway resource and a network segment, you can configure a priority for either the gateway resource or the network segment, but not both. · The priorities of the gateways bound to the same vRouter must be different. · Invalid tags. · The priority is out of range. · The specified segment doesn't exist. · The specified gateway doesn't exist. · Cannot configure a priority for the gateway resource. For more information, see the online help. · Failed to bind the vRouter to an external network because the specified network is not an indirectly connected external network. · Cannot disable east-west traffic offload in network cloud scenarios. · The public network VRF cannot be configured in the weak control scenario. · You have no privilege to perform this operation. · Cannot create vRouter links when the Network Cloud feature is enabled. · A vRouter can be bound to subnets or external network vPorts, but not both. · A vRouter cannot be bound to internal network vPorts. · The type of vPorts bound to a vRouter can only be none. · Cannot bind the external network vPort to the vRouter, because the vRouter has been bound to the external network to which the vPort belongs. · A vRouter cannot be bound to multiple IPv6 external network vPorts in the same network. · Cannot bind the external network to the vRouter, because the vRouter has been bound to a vPort in the external network. · You cannot bind VLAN external networks to a vRouter after you bind a flat external network to the vRouter. Only one flat external network can be bound to a vRouter. · A VRF name cannot start with “external_vpn”. · The RT generated based on the segment ID of the vRouter conflicts with the import RT of a Layer 2 DC interconnect associated with the vRouter. · The RT generated based on the segment ID of the vRouter conflicts with the export RT of a Layer 2 DC interconnect associated with the vRouter. · The RT reserved for the vRouter link conflicts with the import RT of a Layer 2 DC interconnect associated with the local or remote vRouter. · The RT reserved for the vRouter link conflicts with the export RT of a Layer 2 DC interconnect associated with the local or remote vRouter. · The RT generated based on the segment ID of the vRouter conflicts with the import RT of the Layer 3 DC interconnect associated with the vRouter. · The RT generated based on the segment ID of the vRouter conflicts with the export RT of the Layer 3 DC interconnect associated with the vRouter. · The RT reserved for the vRouter link conflicts with the import RT of the Layer 3 DC interconnect associated with the local or remote vRouter. · The RT reserved for the vRouter link conflicts with the export RT of the Layer 3 DC interconnect associated with the local or remote vRouter. · Check the directly connected external networks and the border interfaces in the border device group bound to this vRouter with the same segment ID. Make sure only one primary IPv4 address exists for each border interface. · vRouters do not support vPorts in flat external networks. · The vRouter context or external network vPort context has been used in a service chain. · The segment ID cannot be identical to a VXLAN ID in a VXLAN pool or the VXLAN ID reserved for the automation template and the DR system.

Update router

Keyword	SIMULATION_UPDATE_ROUTER_OP
Message text	Updated router for simulation: $1
Variable fields	$1: vRouter ID.
Example	Updated router for simulation: 3502a951-ab0a-49a9-856c-78b9bf4176c2
Explanation	A vRouter on the specified tenant was edited.
Possible failure causes	· Invalid JSON format. · The request body cannot be empty · The (parameter) parameter value does not match the regular expression(parameter) · Another user is processing this resource. Please try again later · Invalid parameter · The design mode has been disabled for the tenant · Internal error · The request is invalid. · 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 device 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 and the gateway must have been bound to a device group. · For vRouters bound to a service device 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 number 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 cannot 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. · Make sure all vRouters that use this sharing IP are bound to the same edge device for external network access. · 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. · The exit gateway corresponding to the subnet repeats. · You must specify a priority value for each subnet when more than one subnet is bound to the vRouter. · The tags field has duplicate segment IDs. · The tags field has duplicate priorities. · Invalid priority. · The external subnet is bound to the vRouter. · The external network bound to the vRouter does not have segments. The vRouter can be bound only to one IPv4 subnet. · The exit gateway corresponding to the subnet repeats. · 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 subnet of the VLAN type segment at the same time. · The vRouter to which the external network belongs is in a vRouter link, and a vPort on the peer vRouter of the vRouter link has been bound to the floating IP address of the external network. · The specified external network is segmented and has only IPv4 subnets. You must bind at least one of its IPv4 subnets to the vRouter. · The external network is segmented. You cannot unbind a subnet from the vRouter if that subnet is an IPv4 subnet and is the only subnet in the external network. · The border gateways to the IPv4 and IPv6 external subnets are located on the same interface. You must configure them with the same segment ID. · The external network egress IP has been bound to another vRouter. To bind the current vRouter to the external network egress IP, you must make sure the current vRouter has exactly the same external subnet bindings as that vRouter. · Unknown error · The address pool does not exist or no IP addresses are available in the address pool. · The external network specified for the vRouter is not segmented. You can bind only one IPv4 subnet and one IPv6 subnet to the vRouter. · The vRouter is bound to multiple IPv4 and IPv6 external subnets. The network segments to which external subnets of the same IP version are bound cannot be bound to the same border gateway. · The border gateways to the IPv4 and IPv6 external subnets are located on the same interface. You must configure them with the same segment ID. · The segment or border gateway already has a priority. · If a vRouter is bound to both a gateway resource and a network segment, you can configure a priority for either the gateway resource or the network segment, but not both. · You cannot assign priorities to the external subnets bound to the vRouter if they belong to different segments configured with the same border gateway. · The priorities of the gateways bound to the same vRouter must be different. · Invalid tags. · The priority is out of range. · The specified segment doesn't exist. · The specified gateway doesn't exist. · Cannot configure a priority for the gateway resource. For more information, see the online help. · External subnets of the same version bound to the vRouter cannot be bound to the same network segment. · Cannot specify a gateway resource configured with a priority and a segmented external network for a vRouter at the same time. · The external network specified for the vRouter is segmented. You must bind a minimum of one external subnet to the vRouter. · The external network egress IP has already been bound to a vRouter that uses different gateway resources from the current vRouter. Only vRouters that use the same gateway resources can share an external network egress IP. · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot overlap with any vNetwork subnet on another vRouter. · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot overlap with any external subnet on another vRouter. · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot be the same as any vNetwork subnet gateway IP of another vRouter. · The source IP address of a route entry on the vRouter cannot be the same as any vNetwork subnet gateway IP on the vRouter. · The source IP address of a route entry on the vRouter cannot be within any vNetwork subnet on the vRouter. · The source IP address of a route entry on the vRouter cannot be within any external subnet on the vRouter. · Failed to bind the vRouter to an external network because the specified network is not an indirectly connected external network · Failed to configure BGP peers for the vRouter because the vRouter has been configured with BGP neighbors. · Cannot disable east-west traffic offload in network cloud scenarios. · You cannot bind the routing table to the vRouter. The routing table contains a BFD-enabled route entry whose next hop is a vPort with the same IP address as the gateway IP address of a vNetwork bound to the vRouter. · Failed to enable multicast capabilities because the vRouter has already established a vRouter link. · Cannot bind the subnet to a vRouter enabled with multicast network capabilities because the subnet has been configured as a context member. · You have no privilege to perform this operation. · Cannot enable multicast network capabilities for the vRouter because the vRouter has been bound to a Layer 3 DC interconnect. · A vRouter can be bound to subnets or external network vPorts, but not both. · A vRouter cannot be bound to internal network vPorts. · The type of vPorts bound to a vRouter can only be none. · Cannot bind the external network vPort to the vRouter, because the vRouter has been bound to the external network to which the vPort belongs. · A vRouter cannot be bound to multiple IPv6 external network vPorts in the same network. · Cannot bind the external network to the vRouter, because the vRouter has been bound to a vPort in the external network. · You cannot bind VLAN external networks to a vRouter after you bind a flat external network to the vRouter. Only one flat external network can be bound to a vRouter. · You cannot bind the vRouter to a segmented external network. The vRouter uses a firewall as the edge device to the external network and has been bound to a border device group that uses the hairpin or inline third-party firewall deployment mode. · The RT generated based on the segment ID of the vRouter conflicts with the import RT of a Layer 2 DC interconnect associated with the vRouter. · The RT generated based on the segment ID of the vRouter conflicts with the export RT of a Layer 2 DC interconnect associated with the vRouter. · The RT reserved for the vRouter link conflicts with the import RT of a Layer 2 DC interconnect associated with the local or remote vRouter. · The RT reserved for the vRouter link conflicts with the export RT of a Layer 2 DC interconnect associated with the local or remote vRouter. · The RT generated based on the segment ID of the vRouter conflicts with the import RT of the Layer 3 DC interconnect associated with the vRouter. · The RT generated based on the segment ID of the vRouter conflicts with the export RT of the Layer 3 DC interconnect associated with the vRouter. · The RT reserved for the vRouter link conflicts with the import RT of the Layer 3 DC interconnect associated with the local or remote vRouter. · The RT reserved for the vRouter link conflicts with the export RT of the Layer 3 DC interconnect associated with the local or remote vRouter. · Cannot bind the subnet to a vRouter if the subnet is used for primary IP allocation. · Subnets in the external network do not have sufficient IP addresses for allocation. · Failed to assign IP addresses to devices attached to the border gateway, because the IP addresses in the primary IP allocation are insufficient. · Cannot bind the subnet to a vRouter if the subnet is used for primary IP allocation. · Subnets in the external network do not have sufficient IP addresses for allocation. · Failed to assign IP addresses to devices attached to the border gateway, because the IP addresses in the primary IP allocation are insufficient. · Check the directly connected external networks and the border interfaces in the border device group bound to this vRouter with the same segment ID. Make sure only one primary IPv4 address exists for each border interface. · vRouters do not support vPorts in flat external networks. · The vRouter context or external network vPort context has been used in a service chain. · Please specify two and only two external subnets for the external context. This is required because the context uses primary/backup gateway deployment mode and the edge device to the external network in the vRouter for the context is the border device. · The external subnet has been bound to a context. Please access the context page to remove the binding first. · The context uses primary/backup gateway deployment mode. Make sure the associated vRouter is bound to two gateway members or external subnets. · The context uses single gateway deployment mode. Make sure the associated vRouter is bound to one gateway member or external subnet. · The vRouter-attached gateway members enable the third-party firewall option. Please enable or disable the firewall option across all IP addresses or subnets in the vRouter-attached external network if the egress of the external network is the firewall or border device, respectively. · The vRouter-attached gateway members disable the third-party firewall option and use hairpin firewall deployment. Please make sure the firewall is enabled or disabled across all IP addresses and subnets in the external network. · Failed to unbind the vRouter from the external network. The vRouter has been bound to a Layer 3 multicast network or a multicast source used for external services. · The request is invalid. · 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. · 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. · The port ID is different than the gateway port ID. · The selected subnet cannot overlap with the network that contains the ingress or egress vPort in the vRouter's service chain. · Unknown error. · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot overlap with any vNetwork subnet on another vRouter. · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot overlap with any external subnet on another vRouter. · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot be the same as any vNetwork subnet gateway IP of another vRouter. · The source IP address of a route entry on the vRouter cannot be the same as any vNetwork subnet gateway IP on the vRouter. · The source IP address of a route entry on the vRouter cannot be within any vNetwork subnet on the vRouter. · The source IP address of a route entry on the vRouter cannot be within any external subnet on the vRouter. · Subnets in the same vNetwork must be bound to the same vRouter. · The indirectly connected external network can't be directly deleted from or added to the router. · Subnets in the same external network must be bound to the same vRouter. · You cannot bind a vRouter to a vPort created by using a subnet for primary IP allocation. · The IPv4 subnet has been bound to a context, or it overlaps with the subnet attached to a service instance's ingress/egress vPort in a service chain. It cannot be assigned to the vRouter already specified in an IPv4 or IPv4 & IPv6 application policy. · The IPv4 subnet overlaps with the subnet attached to the ingress or egress vPort for a service instance of a service path specified in an application policy. It cannot be assigned to this vRouter, which has been bound to a service chain. · Failed to assign the IPv4 subnet to the vRouter, because the vRouter has been bound to both a router context in a service chain and an IPv4 or IPv4 & IPv6 application policy. · Failed to add some of the vSubnets. Please make sure the selected vSubnets are not used in the service chain associated with the vRouter. · Failed to bind the subnet to the vRouter, because it overlaps with a network bound to the context in another service chain. · 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. · The indirectly connected external network can't be directly deleted from or added to the router. · Failed to remove the subnet from the vRouter because the vRouter has BGP peers on this subnet. · You have no privilege to perform this operation. · The vRouter has not been bound to the port. · The vNetwork is an interface-specific multicast network. You cannot unbind its only subnet from the vRouter. · The segment ID cannot be identical to a VXLAN ID in a VXLAN pool or the VXLAN ID reserved for the automation template and the DR system.

Delete router

Keyword	SIMULATION_DELETE_ROUTER_OP
Message text	Deleted router for simulation: $1
Variable fields	$1: vRouter ID.
Example	Deleted router for simulation: 3502a951-ab0a-49a9-856c-78b9bf4176c2
Explanation	A vRouter on the specified tenant was deleted.
Possible failure causes	· Another user is processing this resource. Please try again later. · Invalid parameter. · The design mode has been disabled for the tenant. · Internal error. · 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. · Failed to delete the vRouter because the vRouter has BGP peers. · You have no privilege to perform this operation. · You cannot delete the vRouter, because it has been bound to an EPG. · You cannot delete the vRouter, because it has been bound to an application policy.

Create link

Keyword	SIMULATION_CREATE_LINK_OP
Message text	Created link for simulation:$1
Variable fields	$1: Link request body.
Example	Created link for simulation: { "link": { "resource_type": "routerLink", "routerlinks": [ { "id": "d65e6edc-4ea0-4d0d-92bf-a2813401b8cb", "tenant_id": "ffffffff-0000-0000-0000-000000000001", "name": "routerlink1", "description": "this is a vrouter link", "router_id1": "d65e6edc-4ea0-4d0d-92bf-a2813401b8cc", "router_id2": "d65e6edc-4ea0-4d0d-92bf-a2813401b8cd" } ], "DCILinks": [] } }
Explanation	A link was created on the specified tenant.
Possible failure causes	· Invalid JSON format. · The request body cannot be empty. · The (parameter) parameter value does not match the regular expression. · Another user is processing this resource. Please try again later. · Invalid parameter. · The design mode has been disabled for the tenant. · Internal error. · 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. · Cannot create distributed vRouter links in Network cloud feature. · You have no privilege to perform this operation.

Update link

Keyword	SIMULATION_UPDATE_LINK_OP
Message text	Updated link for simulation: $1
Variable fields	$1: Link request body.
Example	Updated link for simulation: "link": { "resource_type": "routerLink", "routerlinks": [ { "id": "d65e6edc-4ea0-4d0d-92bf-a2813401b8cb", "tenant_id": "ffffffff-0000-0000-0000-000000000001", "name": "routerlink1", "description": "this is a vrouter link", "router_id1": "d65e6edc-4ea0-4d0d-92bf-a2813401b8cc", "router_id2": "d65e6edc-4ea0-4d0d-92bf-a2813401b8cd" } ], "DCILinks": [] } }
Explanation	A link on the specified tenant was edited.
Possible failure causes	· Invalid JSON format. · The request body cannot be empty. · The (parameter) parameter value does not match the regular expression. · Another user is processing this resource. Please try again later. · Invalid parameter. · The design mode has been disabled for the tenant. · Internal error. · 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. · You have no privilege to perform this operation.

Delete link

Keyword	SIMULATION_DELETE_LINK_OP
Message text	Deleted link for simulation: $1
Variable fields	$1: vRouter link ID.
Example	Deleted link for simulation: d65e6edc-4ea0-4d0d-92bf-a2813401b8cb
Explanation	A link on the specified tenant was deleted.
Possible failure causes	· Another user is processing this resource. Please try again later. · Invalid parameter. · The design mode has been disabled for the tenant. · Internal error. · The controller is not the active leader. · Configuration recovery is in progress. · The specified resource doesn't exist. · A vPort on one vRouter of the vRouter link has been bound to the floating IP address of the external network bound to the other vRouter of the vRouter link. · Unknown error. · You have no privilege to perform this operation.

Receive request to deploy services to tenant

Keyword	RCV_DEPLOY_REQ
Message text	Received request to deploy services to tenant $1.
Variable fields	$1: Tenant ID.
Example	Received request to deploy services to tenant 95a541c8-dcb4-4d18-8a8c-16d79ff524c9.
Explanation	A user deployed services to the specified tenant.
Possible failure causes	N/A

Deploy services to tenant

Keyword	DEPLOY_OP
Message text	Deployed services to tenant: $1.
Variable fields	$1: Configuration details to deploy.
Example	Deployed services to tenant : { "deployed_resources": [{ "resource_type": "subnet", "number": 12 }, { "resource_type": "vRouter", "number": 10 }] }
Explanation	The controller processed the user requests and deployed services to the specified tenant.
Possible failure causes	· Internal error. · The specified tenant does not exist on the controller. · The (parameter) parameter value does not match the regular expression. · The design mode has been disabled for the tenant. · Failed to deploy the service. · No services to deploy. · Another user is processing this resource. Please try again later.

SIMULATION_NETWORK

This section contains simulation network messages.

Start simulation network model creation task

Keyword	CREATE_SIMNETWORK_OP
Message text	Started simulation network model creation task: $1.
Variable fields	$1: Network model information.
Example	Started simulation network model creation task: { " SimNetworkProcessModel ": { " processId ": "b82c8540-4275-4b23-bf9c-e3fede6b18a8" } }.
Explanation	A simulation network model creation task was started.
Possible failure causes	· Invalid JSON format. · The number of fabric_id only supports one. · Invalid fabric_id. · The system service does not respond. · The fabric does not exist. · Internal error. · Invalid token. · The HTTP method is not supported.

Start simulation network model update task

Keyword	UPDATE_SIMNETWORK_OP
Message text	Started simulation network model update task : $1.
Variable fields	$1: Network model information.
Example	Started simulation network model update task: { " SimNetworkProcessModel ": { " processId ": "b82c8540-4275-4b23-bf9c-e3fede6b18a8" } }.
Explanation	A simulation network model update task was started.
Possible failure causes	· Invalid JSON format. · The number of fabric_id only supports one. · Invalid fabric_id. · The system service does not respond. · The fabric does not exist. · Internal error. · Invalid token. · The HTTP method is not supported.

Start simulation network model deletion task

Keyword	DELETE_SIMNETWORK_OP
Message text	Started simulation network model deletion task: $1.
Variable fields	$1: Network model information.
Example	Started simulation network model deletion task: { "fabrics": [{ "fabric_id": "b82c8540-4275-4b23-bf9c-e3fede6b18a8" }] }.
Explanation	A simulation network model deletion task was started.
Possible failure causes	· Invalid JSON format. · Please specify all required parameters. · Only one fabric ID can be specified. · Invalid fabric ID. · The specified network model does not exist. · Failed to delete the VNF. · Failed to add the operation record. · Failed to delete the VNF template. · Failed to delete the network model. · Failed to delete simulation configuration. · The simulation network model is being operated. Please try again later. · Internal error. · Invalid token. · VNFM processing failed. · The HTTP method is not supported. · VNFM authentication failed. · The system service does not respond. · Password decryption failed. · Password encryption failed.

Start vPort creation task

Keyword	CREATE_VPORT_OP
Message text	Started vPort creation task: $1.
Variable fields	$1: vPort information.
Example	Started vPort creation task: { "ports": [ { “id”: "b82c8540-4275-4b23-bf9c-e3fede6b18a8", "cidr": "192.168.1.0/16", "gateway_ip": "3.1.1.1", "mac_address": "00:50:56:ba:e4:89", "vlan": "50", "abbreviated_access_port_name": "XGE1/0/27", "access_device_id": "b82c8540-4275-4b23-bf9c-e3fede6b18a8" } ] }.
Explanation	A vPort creation task was started.
Possible failure causes	· Invalid JSON format. · Invalid vPort ID. · vPort information conflicts. · Invalid gateway IP address. · Invalid CIDR. · Invalid value for the abbreviated_access_port_name parameter. · Invalid access device ID. · Please specify all required parameters. · Failed to create the vPort. · The specified vPort already exists. · The CIDR and subnet gateway IP of a vPort must be the same IP version. · Internal error. · Invalid token. · VNFM processing failed. · The HTTP method is not supported. · VNFM authentication failed. · The system service does not respond. · Password decryption failed. · Password encryption failed.

Start vPort deletion task

Keyword	DELETE_VPORT_OP
Message text	Started vPort deletion task: $1.
Variable fields	$1: vPort information.
Example	Started vPort deletion task: { "ports": [ { “id”: "b82c8540-4275-4b23-bf9c-e3fede6b18a8", } ] }.
Explanation	A vPort deletion task was started.
Possible failure causes	· Invalid JSON format. · Invalid vPort ID. · vPort information conflicts. · Failed to delete the vPort. · The specified vPort does not exist. · Please specify all required parameters. · Internal error. · Invalid token. · VNFM processing failed. · The HTTP method is not supported. · VNFM authentication failed. · The system service does not respond. · Password decryption failed. · Password encryption failed.

Add host

Keyword	ADD_HOST_OP
Message text	Added host: $1
Variable fields	$1: Host information.
Example	Added host: { "host": { "name": "host1", "ip_address": "192.168.12.42", "user": "root", "password": "******" } }
Explanation	A host was created.
Possible failure causes	· The specified VNFM does not exist. · Invalid JSON format. · Please specify all required parameters. · Invalid username. · Invalid host name. · Invalid host IP. · Invalid host password. · The system service does not respond. · Failed to add the host. · The host already exists. · Internal error. · Invalid token. · The HTTP method is not supported. · Password decryption failed · Password encryption failed · Failed to connect to the VNFM.

Delete host

Keyword	DELETE_HOST_OP
Message text	Deleted host “$1”.
Variable fields	$1: Host name.
Example	Deleted host “hostName1”.
Explanation	A host was deleted.
Possible failure causes	· The system service does not respond. · You cannot delete the host, because some VMs are running on the host. · Failed to delete the host. · The simulation network model is being operated. Please try again later. · Internal error. · Invalid token. · The HTTP method is not supported. · Invalid JSON format. · Failed to connect to the VNFM.

Add VNFM

Keyword	ADD_VNFM_OP
Message text	Added VNFM: $1.
Variable fields	$1: VNFM information.
Example	Added VNFM: { "vnfm": { "name": "vnfm", "ip": "192.168.16.214", "password": "******", "username": "sdn" } }
Explanation	A VNFM was added.
Possible failure causes	· The specified VNFM already exists. · Invalid JSON format. · Please specify all required parameters. · Invalid VNFM name. · Invalid VNFM IP. · Invalid username. · Invalid VNFM password. · VNFM authentication failed. · Internal error. · Invalid token. · The HTTP method is not supported. · The system service does not respond. · Password decryption failed. · Password encryption failed.

Update VNFM

Keyword	UPDATE_VNFM_OP
Message text	Updated VNFM: $1.
Variable fields	$1: VNFM information.
Example	Updated VNFM "eaeed71d-4f47-415a-8b66-5750bbf2d22e".
Explanation	A VNFM was edited.
Possible failure causes	· Invalid VNFM name. · Invalid VNFM IP. · Invalid username · Invalid VNFM password. · The specified VNFM does not exist. · VNFM authentication failed. · You cannot edit the VNFM IP. · The uuid is invalid. · Invalid JSON format. · Please specify all required parameters. · VNFM authentication failed. · Internal error. · Invalid token. · The HTTP method is not supported. · The system service does not respond. · Password decryption failed · Password encryption failed.

Delete VNFM

Keyword	DELETE_VNFM_OP
Message text	Deleted VNFM $1 “”.
Variable fields	$1: VNFM ID.
Example	Deleted VNFM "eaeed71d-4f47-415a-8b66-5750bbf2d22e".
Explanation	A VNFM was deleted.
Possible failure causes	· The specified VNFM does not exist. · The uuid is invalid. · The VNFM is in use. · Invalid JSON format. · VNFM authentication failed. · Please specify all required parameters. · Internal error. · Invalid token. · The HTTP method is not supported. · The system service does not respond.

SSLVPNaaS

This section contains messages from the SSL VPN module.

Create PKI domain

Keyword	CREATE_PKI_DOMAIN_OP
Message text	Created PKI domain $1
Variable fields	$1: Information about the PKI domain.
Example	Created PKI domain ID: 9a83d713-8e79-4ca8-a2e9-8df29daf5fd6 Name: pkiDomain1 Tenant ID: ffffffff-0000-0000-0000-000000000001 Tenant name: default Description: pki domain Public key name: dmpubkey Local certification file name: local.crt CA certification file name: ca.crt
Explanation	A PKI domain was created.
Possible failure causes	· The configuration item ID already exists. · The configuration item name already exists. · The tenant doesn't exist. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · Unknown error. · Invalid PKI domain name. · Invalid description. · The PKI domain name is required. · The public key name is required. · Invalid public key name. · The CA certification file name is required. · The local certification file name is required. · Invalid CA certification file name. · Invalid local certification file name. · The tenant ID is required. · Invalid tenant ID. · Invalid JSON format. · You have no privilege to perform this operation.

Update PKI domain

Keyword	UPDATE_PKI_DOMAIN_OP
Message text	Updated PKI domain $1.
Variable fields	$1: Information about the PKI domain.
Example	Updated PKI domain ID: 9a83d713-8e79-4ca8-a2e9-8df29daf5fd6 Name: pkiDomain1 Tenant ID: ffffffff-0000-0000-0000-000000000001 Tenant name: default Description: pki domain Public key name: dmpubkey Local certification file name: local.crt CA certification file name: ca.crt
Explanation	A PKI domain was modified.
Possible failure causes	· The PKI domain doesn't exist. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · Unknown error. · The PKI domain ID is read only. · Invalid PKI domain name. · Invalid description. · The PKI domain name is read only. · Invalid PKI domain ID. · Invalid public key name. · Invalid CA certification file name. · Invalid local certification file name. · The tenant ID is read only. · Invalid JSON format. · You have no privilege to perform this operation.

Delete PKI domain

Keyword	DELETE_PKI_DOMAIN_OP
Message text	Deleted PKI domain $1
Variable fields	$1: PKI domain name.
Example	Deleted PKI domain pki
Explanation	A PKI domain was deleted.
Possible failure causes	· The PKI domain doesn't exist. · The PKI domain is being used by an SSL policy. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · Unknown error. · Invalid PKI domain ID. · You have no privilege to perform this operation.

Create SSL policy

Keyword	CREATE_SSL_POLICY_OP
Message text	Created SSL policy $1
Variable fields	$1: Information about the SSL policy.
Example	Created SSL policy ID: b52fff79-7bcf-4bff-9340-68c5f6c1c495 Name: sslpolicy Tenant ID: ffffffff-0000-0000-0000-000000000001 Tenant name: default PKI domain ID: e0cdcbe7-3623-4270-becb-8390d88d8009 PKI domain name: pkidomain Description: sslpolicy
Explanation	An SSL policy was created.
Possible failure causes	· The configuration item ID already exists. · The PKI domain doesn't exist. · The SSL policy and PKI domain belong to different tenants. · The configuration item name already exists. · The tenant doesn't exist. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · Unknown error. · The PKI domain ID is required. · Invalid description. · The SSL policy name is required. · Invalid SSL policy name. · The tenant ID is required. · Invalid tenant ID. · Invalid JSON format. · You have no privilege to perform this operation.

Update SSL policy

Keyword	UPDATE_SSL_POLICY_OP
Message text	Updated SSL policy $1
Variable fields	$1: Information about the SSL policy.
Example	Updated SSL policy ID: b52fff79-7bcf-4bff-9340-68c5f6c1c495 Name: sslpolicy Tenant ID: ffffffff-0000-0000-0000-000000000001 Tenant name: default PKI domain ID: e0cdcbe7-3623-4270-becb-8390d88d8009 PKI domain name: pkidomain Description: sslpolicy
Explanation	An SSL policy was modified.
Possible failure causes	· The configuration item doesn’t exist. · The PKI domain doesn't exist. · The SSL policy and PKI domain belong to different tenants. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · The SSL policy doesn't exist. · Unknown error. · Invalid description. · Invalid SSL policy ID. · The SSL policy ID is read only. · The SSL policy name is read only. · Invalid SSL policy name. · The tenant ID is read only. · Invalid JSON format. · You have no privilege to perform this operation.

Delete SSL policy

Keyword	DELETE_SSL_POLICY_OP
Message text	Deleted SSL policy $1
Variable fields	$1: SSL policy name.
Example	Deleted SSL policy sslpolicy
Explanation	An SSL policy was deleted.
Possible failure causes	· The SSL policy doesn't exist. · The SSL policy is being used by gateways. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · Unknown error. · Invalid SSL policy ID. · You have no privilege to perform this operation.

Create SSL VPN gateway

Keyword	CREATE_SSLVPN_GATEWAY_OP
Message text	Created SSL VPN gateway $1
Variable fields	$1: Information about the SSL VPN gateway.
Example	Created SSL VPN gateway ID: 70dc3186-ac5b-4ba1-ac7f-7a27ef566efb Name: sslvpngateway Tenant ID: ffffffff-0000-0000-0000-000000000001 Tenant name: default IP: 192.168.0.1 Port: 443 Description: sslvpngateway vRouter ID: e9f32f57-a8f0-4bfa-9b6c-7b377775f0f0 vRouter name: def Enabled: true
Explanation	An SSL VPN gateway was created.
Possible failure causes	· The configuration item name already exists. · The vRouter doesn't exist. · The configuration item and the bound vRouter belong to different tenants. · The SSL policy doesn't exist. · The gateway and SSL policy belong to different tenants. · If two gateways are bound with different vRouters but the vRouters share the same external IP address, the gateways must use different port numbers. · No external network is specified for the vRouter. · The configuration item ID already exists. · The tenant doesn't exist. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · Invalid gateway port number. · Unknown error. · Invalid description. · The gateway name is required. · Invalid gateway name. · The gateway port number is required. · The tenant ID is required. · Invalid tenant ID. · The vRouter ID is required. · Invalid vRouter ID. · Invalid JSON format. · Cannot specify the vRouter enabled with gateway forwarding of external traffic. · You have no privilege to perform this operation.

Update SSL VPN gateway

Keyword	UPDATE_SSLVPN_GATEWAY_OP
Message text	Updated SSL VPN gateway $1
Variable fields	$1: Information about the SSL VPN gateway.
Example	Updated SSL VPN gateway ID: 70dc3186-ac5b-4ba1-ac7f-7a27ef566efb Name: sslvpngateway Tenant ID: ffffffff-0000-0000-0000-000000000001 Tenant name: default IP: 192.168.0.1 Port: 443 Description: sslvpngateway vRouter ID: e9f32f57-a8f0-4bfa-9b6c-7b377775f0f0 vRouter name: def Enabled: true
Explanation	An SSL VPN gateway was modified.
Possible failure causes	· The configuration item doesn’t exist. · The SSL policy doesn't exist. · The gateway and SSL policy belong to different tenants. · If two gateways are bound with different vRouters but the vRouters share the same external IP address, the gateways must use different port numbers · No external network is specified for the vRouter. · The configuration item and the bound vRouter belong to different tenants. · The gateway is being used by SSL VPN contexts. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · The gateway doesn't exist. · Invalid gateway port number. · The vRouter doesn't exist. · Unknown error. · Invalid description. · Invalid gateway ID. · The gateway ID is read only. · Invalid gateway name. · The gateway name is read only. · The tenant ID is read only. · The vRouter ID is required. · Invalid JSON format. · Cannot specify the vRouter enabled with gateway forwarding of external traffic. · You have no privilege to perform this operation.

Delete SSL VPN gateway

Keyword	DELETE_SSLVPN_GATEWAY_OP
Message text	Deleted SSL VPN gateway $1
Variable fields	$1: Name of the SSL VPN gateway.
Example	Deleted SSL VPN gateway gateway
Explanation	An SSL VPN gateway was deleted.
Possible failure causes	· The gateway doesn't exist. · The gateway is being used by SSL VPN contexts. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · Unknown error. · Invalid gateway ID. · You have no privilege to perform this operation.

Create IP address pool

Keyword	CREATE_SSLVPN_POOL_OP
Message text	Created SSL VPN IP address pool $1
Variable fields	$1: Information about the SSL VPN address pool.
Example	Created SSL VPN IP address pool ID: 6835896c-5152-4bed-a2ab-092c9980e2b8 Name: ippool Tenant ID: ffffffff-0000-0000-0000-000000000001 Tenant name: default vRouter ID: ffffffff-0000-0000-0000-000000000001 vRouter name: vrt1 Start IP address: 14.14.14.14 End IP address: 14.14.14.16 Mask: 255.255.0.0 Description: ippool
Explanation	An SSL VPN address pool was created.
Possible failure causes	· The configuration item ID already exists. · The configuration item name already exists. · The start IP address must be lower than the end IP address. · The number of SSL VPN AC interfaces reached the maximum on the gateway or service resource for the specified vRouter. · Overlapping IP address pool range. · The tenant doesn't exist. · The vRouter doesn't exist. · The configuration item and the bound vRouter belong to different tenants. · The controller is not the active leader. · The operation requires the administrator privilege. · For different IP address pools, their start IP addresses must belong to different subnets. · Configuration recovery is in progress. · The service has not been found. · Invalid start IP address. · Invalid end IP address. · Unknown error. · Invalid description. · Invalid IP address pool name. · The IP address pool name is required. · The start IP address is required. · The end IP address is required. · The subnet mask is required. · Invalid subnet mask. · The tenant ID is required. · Invalid tenant ID. · The vRouter ID is required. · Invalid vRouter ID. · Invalid JSON format. · The specified IP address range conflicts with the subnet associated with the vRouter. · Cannot specify the vRouter enabled with gateway forwarding of external traffic. · You have no privilege to perform this operation.

Update IP address pool

Keyword	UPDATE_SSLVPN_POOL_OP
Message text	Updated SSL VPN IP address pool $1
Variable fields	$1: Information about the SSL VPN address pool.
Example	Updated SSL VPN IP address pool ID: 6835896c-5152-4bed-a2ab-092c9980e2b8 Name: ippool Tenant ID: ffffffff-0000-0000-0000-000000000001 Tenant name: default vRouter ID: ffffffff-0000-0000-0000-000000000001 vRouter name: vrt1 Start IP address: 14.14.14.14 End IP address: 14.14.14.16 Mask: 255.255.0.0 Description: ippool
Explanation	An SSL VPN address pool was modified.
Possible failure causes	· The configuration item doesn’t exist. · The start IP address must be lower than the end IP address. · Overlapping IP address pool range. · The vRouter doesn't exist. · The configuration item and the bound vRouter belong to different tenants. · The controller is not the active leader. · The operation requires the administrator privilege. · For different IP address pools, their start IP addresses must belong to different subnets. · Configuration recovery is in progress. · The service has not been found. · Invalid start IP address. · Invalid end IP address. · The IP address pool doesn't exist. · The IP address pool is being used by SSL VPN contexts. · The number of SSL VPN AC interfaces reached the maximum on the gateway or service resource for the specified vRouter. · Unknown error. · Invalid description. · The IP address pool ID is read only. · Invalid IP address pool ID. · Invalid IP address pool name. · The IP address pool name is read only. · Invalid subnet mask. · The tenant ID is read only. · The vRouter ID is required. · Invalid JSON format. · The specified IP address range conflicts with the subnet associated with the vRouter. · Cannot specify the vRouter enabled with gateway forwarding of external traffic. · You have no privilege to perform this operation.

Delete IP address pool

Keyword	DELETE_SSLVPN_POOL_OP
Message text	Deleted SSL VPN IP address pool $1
Variable fields	$1: Name of the SSL VPN address pool.
Example	Deleted SSL VPN IP address pool ippool
Explanation	An SSL VPN address pool was deleted.
Possible failure causes	· The IP address pool doesn't exist. · The IP address pool is being used by SSL VPN contexts. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · Unknown error. · Invalid IP address pool ID. · You have no privilege to perform this operation.

Create SSL VPN context

Keyword	CREATE_SSLVPN_CONTEXT_OP
Message text	Created SSL VPN context $1
Variable fields	$1: Information about the SSL VPN context.
Example	Created SSL VPN context ID: 6835896c-5152-4bed-a2ab-092c9980e2b8 Name: 123 Tenant ID: ffffffff-0000-0000-0000-000000000001 Tenant name: default vRouter ID: e9f32f57-a8f0-4bfa-9b6c-7b377775f0f0 vRouter name: def SSL VPN gateway ID: 83974693-027a-441b-9c40-805910abfdd2 SSL VPN gateway name: gateway IP address pool ID: 0b403e57-06b8-41ee-85f6-6feb8fa4c2bc IP address pool name: ippool ISP domain: aaa Description: sslvpnContext Enabled: true
Explanation	An SSL VPN context was created.
Possible failure causes	· The configuration item ID already exists. · The tenant doesn't exist. · The vRouter doesn't exist. · The gateway doesn't exist. · The configuration item and the bound vRouter belong to different tenants. · The SSL VPN context and gateway belong to different vRouters. · The configuration item name already exists. · The IP address pool doesn't exist. · The SSL VPN context and IP address pool belong to different tenants. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · Invalid domain name. · Unknown error. · Invalid description. · The gateway ID is required. · The IP address pool ID is required. · The SSL VPN context name is required. · Invalid SSL VPN context name. · Invalid ISP domain name. · The tenant ID is required. · Invalid tenant ID. · The vRouter ID is required. · Invalid vRouter ID. · Invalid JSON format. · Cannot specify the vRouter enabled with gateway forwarding of external traffic. · You have no privilege to perform this operation.

Update SSL VPN context

Keyword	UPDATE_SSLVPN_CONTEXT_OP
Message text	Updated SSL VPN context $1
Variable fields	$1: Information about the SSL VPN context.
Example	Updated SSL VPN context ID: 6835896c-5152-4bed-a2ab-092c9980e2b8 Name: 123 Tenant ID: ffffffff-0000-0000-0000-000000000001 Tenant name: default vRouter ID: e9f32f57-a8f0-4bfa-9b6c-7b377775f0f0 vRouter name: def SSL VPN gateway ID: 83974693-027a-441b-9c40-805910abfdd2 SSL VPN gateway name: gateway IP address pool ID: 0b403e57-06b8-41ee-85f6-6feb8fa4c2bc IP address pool name: ippool ISP domain: aaa Description: sslvpnContext Enabled: true
Explanation	An SSL VPN context was modified.
Possible failure causes	· The SSL VPN context doesn't exist. · The gateway doesn't exist. · The SSL VPN context and gateway belong to different vRouters. · The IP address pool doesn't exist. · The SSL VPN context and IP address pool belong to different tenants. · The configuration item and the bound vRouter belong to different tenants. · The tenant doesn't exist. · The vRouter doesn't exist. · The configuration item and the bound vRouter belong to different tenants. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · Invalid domain name. · Unknown error. · Invalid description. · The gateway ID is required. · The IP address pool ID is required. · The SSL VPN context ID is read only. · Invalid SSL VPN context name. · The SSL VPN context name is read only. · Invalid ISP domain name. · The tenant ID is read only. · Invalid JSON format. · Cannot specify the vRouter enabled with gateway forwarding of external traffic. · You have no privilege to perform this operation.

Delete SSL VPN context

Keyword	DELETE_SSLVPN_CONTEXT_OP
Message text	Deleted SSL VPN context $1
Variable fields	$1: Name of the SSL VPN context.
Example	Deleted SSL VPN context context1
Explanation	An SSL VPN context was deleted.
Possible failure causes	· The SSL VPN context doesn't exist. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · Unknown error. · Invalid SSL VPN context ID. · You have no privilege to perform this operation.

Create route list

Keyword	CREATE_ROUTE_LIST_OP
Message text	Created route list $1
Variable fields	$1: Information about the route list.
Example	Created route list ID: 6835896c-5152-4bed-a2ab-092c9980e2b8 Name: 123 SSL VPN context ID: e5471ec1-4a5d-4ce8-81a8-70fc74634c24 SSL VPN context name: sslvpncontext Route list: [ CIDR: 192.168.0.1/8, CIDR: 192.168.0.2/16 ]
Explanation	A route list was created.
Possible failure causes	· The configuration item ID already exists. · The SSL VPN context doesn't exist. · The configuration item name already exists. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · Invalid CIDR. · Unknown error. · The SSL VPN context ID is required. · Invalid route list name. · The route list name is required. · Invalid JSON format. · You have no privilege to perform this operation.

Update route list

Keyword	UPDATE_ROUTE_LIST_OP
Message text	Updated route list $1
Variable fields	$1: Information about the route list.
Example	Updated route list ID: 6835896c-5152-4bed-a2ab-092c9980e2b8 Name: 123 SSL VPN context ID: e5471ec1-4a5d-4ce8-81a8-70fc74634c24 SSL VPN context name: sslvpncontext Route list: [ CIDR: 192.168.0.1/8, CIDR: 192.168.0.2/16 ]
Explanation	A route list was modified.
Possible failure causes	· The route list doesn't exist. · The SSL VPN context doesn't exist. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · Invalid CIDR. · Unknown error. · Invalid SSL VPN context ID. · The SSL VPN context ID is read only. · Invalid policy group ID. · The route list ID is read only. · The route list name is read only. · The route list doesn't exist. · Invalid JSON format. · You have no privilege to perform this operation.

Delete route list

Keyword	DELETE_ROUTE_LIST_OP
Message text	Deleted route list $1
Variable fields	$1: Name of the route list.
Example	Deleted route list routelist1
Explanation	A route list was deleted.
Possible failure causes	· The route list doesn't exist. · The route list is being used by policy groups. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · Unknown error. · The route list doesn't exist. · You have no privilege to perform this operation.

Create policy group

Keyword	CREATE_POLICY_GROUP_OP
Message text	Created policy group $1
Variable fields	$1: Information about the SSL VPN policy group.
Example	Created policy group ID: 6835896c-5152-4bed-a2ab-092c9980e2b8 Name: 123 SSL VPN context ID: e5471ec1-4a5d-4ce8-81a8-70fc74634c24 SSL VPN context name: sslvpncontext Route type: ROUTE_LIST Route list ID: 3b020a55-cc55-4882-b6f1-d26d5f21f8a9 Route list name: routelist
Explanation	An SSL VPN policy group was created.
Possible failure causes	· The SSL VPN context doesn't exist. · The route list doesn't exist. · The configuration item ID already exists. · The configuration item name already exists. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · Invalid policy group name. · Unknown error. · The SSL VPN context ID is required. · The policy group name is required. · The route list ID is required. · The route list doesn't exist. · Invalid JSON format. · You have no privilege to perform this operation.

Update policy group

Keyword	UPDATE_POLICY_GROUP_OP
Message text	Updated policy group $1
Variable fields	$1: Information about the SSL VPN policy group.
Example	Updated policy group ID: 6835896c-5152-4bed-a2ab-092c9980e2b8 Name: 123 SSL VPN context ID: e5471ec1-4a5d-4ce8-81a8-70fc74634c24 SSL VPN context name: sslvpncontext Route type: ROUTE_LIST Route list ID: 3b020a55-cc55-4882-b6f1-d26d5f21f8a9 Route list name: routelist
Explanation	An SSL VPN policy group was modified.
Possible failure causes	· The policy group doesn't exist. · The SSL VPN context doesn't exist. · The route list doesn't exist. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · Invalid policy group name. · Unknown error. · Invalid SSL VPN context ID. · The SSL VPN context ID is read only. · Invalid policy group ID. · The policy group ID is read only. · The policy group name is read only. · Invalid JSON format. · You have no privilege to perform this operation.

Delete policy group

Keyword	DELETE_POLICY_GROUP_OP
Message text	Deleted policy group $1
Variable fields	$1: Policy group name.
Example	Deleted policy group policygroup1
Explanation	An SSL VPN policy group was deleted.
Possible failure causes	· The policy group doesn't exist. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · Unknown error. · The policy group doesn't exist. · Invalid JSON format. · You have no privilege to perform this operation.

Create SSL VPN user

Keyword	CREATE_SSLVPN_USER_OP
Message text	Created SSL VPN user $1
Variable fields	$1: Settings for the SSL VPN user.
Example	Created SSL VPN user ID : 53b06a75-bd34-4b68-864d-243b171ba70f Name : user1 Description : ssl vpn user Tenant ID : 6632aef0-5c2a-49b5-8ac0-ec4a9809f0de Tenant name : default Username : sdn User password : sdn123456 User type : local
Explanation	An SSL VPN user was created.
Possible failure causes	· Invalid user UUID. · The login username is required. · The password is required. · The user type is required. · Invalid username. · Invalid user type. · Invalid login username. · Invalid password. · The login username already exists. · Invalid JSON format. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · Unknown error. · You have no privilege to perform this operation.

Update SSL VPN user

Keyword	UPDATE_SSLVPN_USER_OP
Message text	Updated SSL VPN user $1
Variable fields	$1: Settings for the SSL VPN user.
Example	Updated SSL VPN user ID : 53b06a75-bd34-4b68-864d-243b171ba70f Name: user1 Description : ssl vpn user Tenant ID : 6632aef0-5c2a-49b5-8ac0-ec4a9809f0de Tenant name : default Username : sdn User password : sdn123456 User type : local
Explanation	An SSL VPN user was edited.
Possible failure causes	· Invalid user UUID. · The user UUID cannot be edited. · The user does not exist. · The username cannot be edited. · The user type cannot be edited. · Invalid login username. · Invalid password. · The login username already exists. · Invalid JSON format. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · Unknown error. · You have no privilege to perform this operation.

Delete SSL VPN user

Keyword	DELETE_SSLVPN_USER_OP
Message text	Deleted SSL VPN user $1
Variable fields	$1: Name of the SSL VPN user.
Example	Deleted SSL VPN user user1
Explanation	An SSL VPN user was deleted.
Possible failure causes	· Invalid user UUID. · The user does not exist. · Cannot delete the user because it is being used. · Invalid JSON format. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · Unknown error. · You have no privilege to perform this operation.

Create user group

Keyword	CREATE_USER_GROUP_OP
Message text	Created SSL VPN user group $1
Variable fields	$1: Settings for the SSL VPN user group.
Example	Created SSL VPN User Group ID: ee009cbb-6563-48f7-9c2b-922ea7447253 Name: userGroup1 Tenant ID: 6632aef0-5c2a-49b5-8ac0-ec4a9809f0de User group type : local Context ID: e45a4086-9c34-446c-9db3-25a77e20a2ea Policy group ID: e45a4086-9c34-446c-9db3-25a77e20a2ea Description: user group
Explanation	An SSL VPN user group was created.
Possible failure causes	· Invalid user group UUID. · The user group type is required. · Invalid user group type. · Invalid user group name. · The user group and the SSL VPN context must belong to the same tenant. · The policy group has been used by another user group. · The SSL VPN context and policy group bound to the user group must be both specified or both not specified. · Invalid JSON format. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · Unknown error. · You have no privilege to perform this operation.

Update user group

Keyword	UPDATE_USER_GROUP_OP
Message text	Updated SSL VPN user group $1
Variable fields	$1: Settings for the SSL VPN user group.
Example	Updated SSL VPN user group ID : ee009cbb-6563-48f7-9c2b-922ea7447253 Name : userGroup1 Tenant ID : 6632aef0-5c2a-49b5-8ac0-ec4a9809f0de User group Type : local Context ID : e45a4086-9c34-446c-9db3-25a77e20a2ea User list : [18b322aa-6b77-492e-b510-ee30c4c9cfc9, 53b06a75-bd34-4b68-864d-243b171ba70f, 3341bda9-ce17-4ff2-a7ff-a4506df184e4, 72345b2e-b716-43f5-8374-7376506551c1] Policy group ID: e45a4086-9c34-446c-9db3-25a77e20a2ea Description : user group
Explanation	An SSL VPN user group was edited.
Possible failure causes	· The user group UUID cannot be edited. · The user group name cannot be edited. · The tenant to which the user group belongs cannot be edited. · The user group type cannot be edited. · The user group does not exist. · The user group and the SSL VPN context must belong to the same tenant. · The policy group has been used by another user group. · The user has been used by another user group. · The user group does not contain the user. · The user and the user group must belong to the same tenant. · The user type and user group type must be the same. · The SSL VPN context and policy group bound to the user group must be both specified or both not specified. · Invalid JSON format. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · Unknown error. · You have no privilege to perform this operation.

Delete user group

Keyword	DELETE_USER_GROUP_OP
Message text	Deleted SSL VPN user group $1
Variable fields	$1: Name of the SSL VPN user group.
Example	Deleted SSL VPN user group userGroup1
Explanation	An SSL VPN user group was deleted.
Possible failure causes	· Invalid user group UUID. · The user group does not exist. · Invalid JSON format. · The controller is not the active leader. · The operation requires the administrator privilege. · Configuration recovery is in progress. · The service has not been found. · Unknown error. · You have no privilege to perform this operation.

TELEMETRY

This section contains telemetry messages.

Create collector

Keyword	CREATE_COLLECTOR_OP
Message text	Created SeerEngine collector: ID: $1 Name: $2 ip_address: $3 port: $4 isUsed: $5
Variable fields	$1: Collector ID. $2: Collector name. $3: Collector IP address. $4: Collector port number. $5: Collector status.
Example	Created SeerEngine collector: ID: [1] Name: [TEST_COLLECTOR] ip_address: [1] port: [2] isUsed: [In use]
Explanation	A user created a collector.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The UUID already exists. · The name is required and cannot exceed 255 characters. · The port number range is 0 to 65535. · The collector with the same IP and port already exists. · The state cannot be modified. · You have no privilege to perform this operation.

Update collector

Keyword	UPDATE_COLLECTOR_OP
Message text	Updated SeerEngine collector: ID: $1 Name: $2 ip_address: $3 port:$4 isUsed: $5
Variable fields	$1: Collector ID. $2: Collector name. $3: Collector IP address. $4: Collector port number. $5: Collector status.
Example	Updated SeerEngine collector: ID: [1] Name: [TEST_COLLECTOR] ip_address: [1] port: [2] isUsed: [In use]
Explanation	A user updated a collector.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The state cannot be modified. · The port number cannot be modified. · The ID cannot be modified. · The IP address cannot be modified. · The configuration item does not exist. · You have no privilege to perform this operation.

Delete collector

Keyword	DELETE_COLLECTOR_OP
Message text	Deleted SeerEngine collector: $1.
Variable fields	$1: Collector name.
Example	Deleted SeerEngine collector: 1.
Explanation	A user deleted a collector.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · The configuration item does not exist. · The configuration item is in use. · You have no privilege to perform this operation.

Update gRPC common information

Keyword	UPDATE_COMM_INFO_OP
Message text	Updated gRPC common info: ID: $1 Sample_interval: $2 PathList: $3
Variable fields	$1: ID of the common gRPC configuration. $2: Sampling interval. $3: Sensor paths.
Example	Updated gRPC common info: ID: [1] Sample_interval: 10 PathList: [-1]
Explanation	A user updated common gRPC settings.
Possible failure causes	· The controller is not the active leader. · Invalid JSON format. · The sensor path is required. · You have no privilege to perform this operation. · Southbound devices at the following IP addresses were disconnected: {IP addresses}.

Create gRPC device

Keyword	CREATE_GRPC_DEV_OP
Message text	Created gRPC device: ID: $1 Name: $2 Device IP List: $3 Collector List: $4
Variable fields	$1: gRPC device ID. $2: gRPC device name. $3: Switching device IP address list. $4: Collectors.
Example	Created gRPC device: ID: [1] Name: [TEST_GRPC] Device IP List: [10.2.1.1] Collector List: [3]
Explanation	A user created a gRPC device.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The name is required and cannot exceed 255 characters. · The collector name is read only. · The collector does not exist. · The switching device does not exist. · The configuration item already exists. · You have no privilege to perform this operation. · The device list cannot be empty. · Southbound devices at the following IP addresses were disconnected: {IP addresses}.

Update gRPC device

Keyword	UPDATE_GRPC_DEV_OP
Message text	Updated gRPC device: ID: $1 Name: $2 Device IP List: $3 Collector List: $4
Variable fields	$1: gRPC device ID. $2: gRPC device name. $3: Switching device IP address list. $4: Collectors.
Example	Updated gRPC device: ID: [1] Name: [TEST_GRPC] Device IP List: [10.2.1.1] Collector List: [3]
Explanation	A user updated a gRPC device.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The name is required and cannot exceed 255 characters. · The collector name is read only. · The switching device does not exist. · The name is required and cannot exceed 255 characters. · The collector does not exist. · The switching device does not exist. · You have no privilege to perform this operation. · The device list cannot be empty. · Southbound devices at the following IP addresses were disconnected: {IP addresses}.

Delete gRPC device

Keyword	DELETE_GRPC_DEV_OP
Message text	Deleted gRPC device: $1
Variable fields	$1: gRPC device name.
Example	Deleted gRPC device: 1
Explanation	A user deleted a gRPC device.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The configuration item does not exist. · You have no privilege to perform this operation. · Southbound devices at the following IP addresses were disconnected: {IP addresses}.

Create INT device

Keyword	CREATE_INT_DEV_OP
Message text	Created INT device: ID: $1 Name: $2 Device IP: $3
Variable fields	$1: INT device ID. $2: INT device name. $3: Switching device IP address.
Example	Created INT device: ID: [1] Name: [TEST_INT_DEVICE] Device IP: [2]
Explanation	A user created an INT device.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The service has not been found. · The name is required and cannot exceed 255 characters. · The switching device does not exist. · The UUID already exists. · You have no privilege to perform this operation. · The switching device is not active.

Update INT device

Keyword	UPDATE_INT_DEV_OP
Message text	Updated INT device: ID: $1 Name: $2 Device IP: $3
Variable fields	$1: INT device ID. $2: INT device name. $3: Switching device IP address.
Example	Updated INT device: ID: [1] Name: [TEST_INT_DEVICE] Device IP: [2]
Explanation	A user updated an INT device.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The name is required and cannot exceed 255 characters. · The ID cannot be modified. · The IP address cannot be modified. · The configuration item does not exist. · You have no privilege to perform this operation. · The switching device is not active.

Delete INT device

Keyword	DELETE_INT_DEV_OP
Message text	Deleted INT device: $1
Variable fields	$1: INT device name.
Example	Deleted INT device: [TEST_INT_DEVICE]
Explanation	A user deleted an INT device.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The configuration item does not exist. · You have no privilege to perform this operation. · The switching device is not active.

Create INT node

Keyword	CREATE_IFA_NODE_OP
Message text	Created INT node: ID: $1 Name: $2 Device ID: $3 Interface Name: $4 Type: $5 Sample Rate: $6 Egress IP: $7 Egress Port: $8 Collector ID: $9 Rules: $10
Variable fields	$1: INT node ID. $2: INT node name. $3: INT device ID. $4: Interface type and number. $5: Interface role. $6: Sampling rate. $7: Source IP address. $8: Source port number. $9: Collector ID. $10: ACL rules.
Example	Created INT node: ID: [1] Name: [TEST_INT_NODE] Device ID: [2] Interface Name: [3] Type: [egress] Egress IP: [4] Egress Port: [5] Collector ID: [6]
Explanation	A user created an INT node.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The name is required and cannot exceed 255 characters. · The collector name is read only. · The interface name is required. · The switching device ID is required. · The switching device does not exist. · Invalid interface. · The UUID already exists. · The collector does not exist. · The collector ID is required. · The configuration item already exists. · Integer (1 to 86400): Value range of the sampling rate. · You have no privilege to perform this operation. · The switching device is not active.

Update INT node

Keyword	UPDATE_IFA_NODE_OP
Message text	Updated INT node: Name: $1 Sample Rate: $2 Egress IP: $3 Egress Port: $4 Collector ID: $5 Rules: $6
Variable fields	$1: INT node name. $2: Sampling rate. $3: Source IP address. $4: Source port number. $5: Collector ID. $6: ACL rules.
Example	Updated INT node: Name: [TEST_INT_NODE] Egress IP: [4] Egress Port: [5] Collector ID: [6]
Explanation	A user updated an INT node.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The name is required and cannot exceed 255 characters. · The collector name is read only. · The switching device does not exist. · The collector ID is required. · The collector does not exist. · Interface list is read only. · You have no privilege to perform this operation. · The switching device is not active.

Delete INT node

Keyword	DELETE_IFA_NODE_OP
Message text	Deleted INT node: $1
Variable fields	$1: INT node name.
Example	Deleted INT node: [TEST_INT_NODE]
Explanation	A user deleted an INT node.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The configuration item does not exist. · You have no privilege to perform this operation. · The switching device is not active.

Create ERSPAN device

Keyword	CREATE_ERS_DEV_OP
Message text	Created ERSPAN device: ID: $1 Name: $2 Device IP: $3 Interface Name: $4 Collector ID: $5
Variable fields	$1: ERSPAN device ID. $2: ERSPAN device name. $3: Device IP address. $4: Interface type and number. $5: Collector ID.
Example	Created ERSPAN device: ID: [1] Name: [TEST_ERSPAN_DEVICE] Device IP: [2] Interface Name: [3] Collector ID: [4]
Explanation	A user created an ERSPAN device.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The name is required and cannot exceed 255 characters. · The collector name is read only. · The switching device does not exist. · The collector does not exist. · The configuration item already exists. · Invalid interface. · The UUID already exists. · You have no privilege to perform this operation. · The switching device is not active.

Update ERSPAN device

Keyword	UPDATE_ERS_DEV_OP
Message text	Updated ERSPAN device: ID: $1 Name: $2 Device IP: $3 Interface Name: $4 Collector ID: $5
Variable fields	$1: ERSPAN device ID. $2: ERSPAN device name. $3: Device IP address. $4: Interface type and number. $5: Collector ID.
Example	Updated ERSPAN device: ID: [1] Name: [TEST_ERSPAN_DEVICE] Device IP: [2] Interface Name: [3] Collector ID: [4]
Explanation	A user updated an ERSPAN device.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The name is required and cannot exceed 255 characters. · The collector name is read only. · The switching device does not exist. · The collector does not exist. · The configuration item already exists. · Invalid interface. · You have no privilege to perform this operation. · The switching device is not active.

Delete ERSPAN device

Keyword	DELETE_ERS_DEV_OP
Message text	Deleted ERSPAN device: $1
Variable fields	$1: ERSPAN device name.
Example	Deleted ERSPAN device: TEST_ERSPAN_DEVICE
Explanation	A user deleted an ERSPAN device.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The configuration item does not exist. · You have no privilege to perform this operation. · The switching device is not active.

Create telemetry stream profile

Keyword	CREATE_TELEMETRY_STREAM_DEV_OP
Message text	Created telemetry stream profile: $1
Variable fields	$1: Telemetry stream information.
Example	Created telemetry stream profile: ID : 9a8265fe-2d99-417a-ac18-1774a597f685 Name: 3 deviceIpList: [192.168.67.204] sourceIp: 192.168.67.204 sourcePort: 12 collectorId: Id[value=3d9f3712-54dc-4d2a-af8a-e8ab8438a4da] serviceLoopbackInterfaceNames: [WGE1/0/4] policies: [ id : Id[value=d34c8109-19c4-4a00-9e9e-db38fb422376] interfaceNames : [WGE1/0/2, WGE1/0/3] sampleRate: 4].
Explanation	A user created a telemetry stream profile.
Possible failure causes	· The collector name is read only. · Invalid JSON format. · Internal error. · The name is required and cannot exceed 255 characters. · The source IP is required. · Only IPv4 is supported. · The source port is required. · The port number range is 0 to 65535. · The collector ID is required. · The collector does not exist. · The collector has no ports. · The interface doesn't exist or is illegal. · The interface name or sampling rate is required. · The sampling rate is required. · The sampling interval value must be in the range of 0 to 15. · The device list cannot be empty. · The switching device does not exist. · The switching device is not active. · The switching device has already been bound to INT or telemetry stream. · The switching device does not support telemetry stream. · Failed to add the configuration item.

Update telemetry stream profile

Keyword	UPDATE_TELEMETRY_STREAM_OP
Message text	Updated telemetry stream profile: $1
Variable fields	$1: Telemetry stream information.
Example	Updated telemetry stream profile: ID : 47ae87b0-f7f2-4fd9-bf15-93fb78033de2 Name: 3 deviceIpList: [192.168.67.204] sourceIp: 192.168.67.204 sourcePort: 12 collectorId: Id[value=3d9f3712-54dc-4d2a-af8a-e8ab8438a4da] collectorName: 1 serviceLoopbackInterfaceNames: [] policies: [ id : Id[value=44fe2a6d-7712-4a5a-a1a5-ee8d8c373f0d] interfaceNames : [WGE1/0/1, WGE1/0/2, WGE1/0/3] sampleRate: 3 telemetryStreamId: Id[value=47ae87b0-f7f2-4fd9-bf15-93fb78033de2]].
Explanation	A user modified a telemetry stream profile.
Possible failure causes	· The name is required and cannot exceed 255 characters. · The source IP is required. · Only IPv4 is supported. · The source port is required. · The port number range is 0 to 65535. · The collector ID is required. · The collector does not exist.. · The collector has no ports. · The interface doesn't exist or illegal. · The interface name or sampling rate is required. · The sampling rate is required. · The sampling interval value must be in the range of 0 to 15. · The device list cannot be empty. · The switching device does not exist.. · The switching device is not active. · The switching device has already been bound to INT or telemetry stream. · The switching device does not support telemetry stream. · Failed to modify the configuration item. · Invalid JSON format. · Internal error.

Delete telemetry stream profile

Keyword	DEL_TELEMETRY_STREAM_OP
Message text	Deleted telemetry stream profile “$1”.
Variable fields	$1: Telemetry stream information.
Example	Deleted telemetry stream profile “3”.
Explanation	A user deleted a telemetry stream profile.
Possible failure causes	· Invalid JSON format. · Internal error. · The configuration item does not exist.

Tenant

This section contains tenant messages.

Add tenant

Keyword	ADD_TENANT_OP
Message text	Add tenant $1
Variable fields	$1: Information about the tenant.
Example	Added tenant ID: ec4bf666-5c73-4897-b4fc-3fcbae79f746 Name: tenant1 Type: local-create VDS ID: ffffffff-0000-0000-0000-000000000001 Auto allocation: true Cloud region name: region Cloud domain name: domain
Explanation	A tenant was added.
Possible failure causes	· The service has not been found. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The length of name is too long. · Invalid parameter. · The tenant already exists. · The tenant name is required. · You have no privilege to perform this operation. · Up to 255 characters, case sensitive.

Update tenant

Keyword	UPDATE_TENANT_OP
Message text	Update tenant $1
Variable fields	$1: Information about the tenant.
Example	Updated tenant ID: ec4bf666-5c73-4897-b4fc-3fcbae79f746 Name: tenant1 Type: local-create VDS ID: ffffffff-0000-0000-0000-000000000001 Auto allocation: true Cloud region name: region Cloud domain name: domain
Explanation	A tenant was modified.
Possible failure causes	· The service has not been found. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The length of name is too long. · Invalid parameter. · The tenant name is required. · Can't modify the default tenant. · You have no privilege to perform this operation. · You cannot edit or delete the cloud region name. · You cannot edit or delete the domain name. · Up to 255 characters, case sensitive.

Delete tenant

Keyword	DELETE_TENANT_OP
Message text	Delete tenant $1
Variable fields	$1: Information about the tenant.
Example	Delete tenant ID: ec4bf666-5c73-4897-b4fc-3fcbae79f746 Name: tenant1 Type: local-create
Explanation	A tenant was deleted.
Possible failure causes	· The service has not been found. · The controller is not the active leader. · Configuration recovery is in progress. · Can't delete the default tenant. · The tenant has bound resources. · You have no privilege to perform this operation. · The tenant has already been bound to a gateway. · An OSPF or OSPFv3 policy has been configured for the tenant. · A route policy has been configured for the tenant. · An IP prefix has been configured for the tenant. · A security policyhas been configured for the tenant. · A vRouter link hasbeen configured for the tenant. · A vRouterinterconnection has been configured for the tenant. · A network has been configured for the tenant. · A vRouter has been configured for the tenant.

Import tenants

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

TPaaS

This section contains third-party service module messages.

Create third-party service device

Keyword	CREATE_THIRD_PARTY_SERVICE_DEVICE_OP
Message text	Created third-party service device: $1
Variable fields	$1: Third-party service device settings.
Example	Created third-party service device: UUID: 8032909d-47a1-4715-90af-5153ffe39899 Name: TP1 Description: text Incoming vPort VXLAN ID: 100 Outgoing vPort VXLAN ID: 200 Incoming vPort IP address: 1.1.1.1 Outgoing vPort IP address: 192.168.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 access mode. · The vPort does not exist. · The incoming vPort does not exist. · The outgoing vPort 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. · The incoming vPort has been used by another third-party service device. · The outgoing vPort has been used by another third-party service device. · When the access mode is auto access, only the incoming vPort VXLAN ID, outgoing vPort VXLAN ID, incoming vPort IP address, and outgoing vPort IP address can be configured. · An egress vPort and an ingress vPort cannot belong to the same virtual link layer network. · The type of egress/ingress vPort only supports phy. · The access type of the third party service device is invalid. · When the access mode is set to manual access, you cannot specify the ingress/egress vPort VXLAN ID or IP address. · You have no privilege to perform this operation. · Please specify a local IP address. · Please specify a peer IP address. · Please specify a local subnet. · Please specify a peer subnet. · Invalid local subnet. · Invalid peer subnet. · Make sure the local subnets do not overlap. · Make sure the peer subnets do not overlap. · Cannot configure IPsec settings for the third-party service device because its deployment mode is Single vPort. · Cannot configure IPsec settings for the third-party service device because its deployment mode is Single vPort. · The same IPsec settings have been specified. · Make sure the local and peer subnets do not overlap. · Make sure the local IP address and peer IP address are different. · Make sure the local and peer IP addresses have not been specified in existing IPsec settings. · Make sure the local and peer subnets do not overlap with the subnets in existing IPsec settings.

Update third-party service device

Keyword	UPDATE_THIRD_PARTY_SERVICE_DEVICE_OP
Message text	Updated third-party service device: $1
Variable fields	$1: Third-party service device settings.
Example	Updated third-party service device: UUID: 8032909d-47a1-4715-90af-5153ffe39899 Name: TP1 Description: text1
Explanation	A third-party service device 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 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 VXLAN ID field is read only. · The outgoing vPort VXLAN ID 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 VIP list cannot be modified. · The SNAT IP list cannot be modified. · You have no privilege to perform this operation. · The local_address field is read-only. · The peer_address field is read-only. · The local_cidrs field is read-only. · The peer_cidrs field is read-only.

Delete third-party service device

Keyword	DELETE_THIRD_PARTY_SERVICE_DEVICE_OP
Message text	Deleted third-party service device: $1
Variable fields	$1: Name of the third-party service device.
Example	Deleted third-party service device: fw1
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. · You have no privilege to perform this operation.

Create third-party service

Keyword	CREATE_THIRD_PARTY_SERVICE_FUNC_OP
Message text	Created third-party service function: $1
Variable fields	$1: Third-party service resource settings.
Example	Created third-party service function: UUID: 8032909d-47a1-4715-90af-5153ffe39899 Name: TPservice Description: text Tenant: ffffffff-0000-0000-0000-000000000001 Third-party service device: 954a1680-fd27-4cc1-b5ec-8f530c81f57a
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. · You have no privilege to perform this operation.

Update third-party service

Keyword	UPDATE_THIRD_PARTY_SERVICE_FUNCTION_OP
Message text	Updated third-party service function: $1
Variable fields	$1: Third-party service resource settings.
Example	Updated third-party service function: UUID: 8032909d-47a1-4715-90af-5153ffe39899 Name: TPservice Description: text1
Explanation	A third-party service resource 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 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. · You have no privilege to perform this operation.

Delete third party service

Keyword	DELETE_THIRD_PARTY_SERVICE_FUNCTION_OP
Message text	Deleted third-party service function: $1
Variable fields	$1: Name of the third-party service resource.
Example	Deleted third-party service function: TPservice
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. · You have no privilege to perform this operation.

TPFW

This section contains third-party firewall messages.

Add TPFW

Keyword	ADD_TPFW_OP
Message text	Added third-party firewall $1.
Variable fields	$1: Name of the third-party firewall. If the firewall name does not exist, its UUID is displayed.
Example	Added third-party firewall tpfw1.
Explanation	A third-party firewall was added.
Possible failure causes	· The controller is not the active leader. · You have no privilege to perform the operation. · Configuration recovery is in progress. · Invalid JSON format. · The configuration item already exists. · The name field up to 60 characters, case sensitive. Valid characters include Chinese characters, letters, digits, and underscores (_). · The description field up to 255 characters, case sensitive. · Incorrect UUID format of the synchronization operation. · Can't find the BUS type for the operation. · Team HA startup failure. · Team HA processing error. · Data format error. · Failed to insert the data. · Failed to add the configuration. · Failed to bind the dedicated subnet to the dedicated vRouter. · The redirect subnet can't be null. · The redirect IP address can't be null. · The dedicated vRouter can't be null. · The dedicated subnet can't be null. · The dedicated IP address can't be null. · The service NE can't be null. · The UUID of the redirect vRouter is read-only. · The redirect subnet doesn't exist. · The dedicated vRouter doesn't exist. · The dedicated subnet doesn't exist. · The redirect IP address and dedicated IP address can't be the same. · The dedicated IP address is not in the dedicated subnet. · The redirect IP address is not in the redirect subnet. · The redirect subnet and dedicated subnet can't be the same. · You have no privilege to perform this operation.

Update TPFW

Keyword	UPDATE_TPFW_OP
Message text	Updated third-party firewall $1.
Variable fields	$1: Name of the third-party firewall. If the firewall name does not exist, its UUID is displayed.
Example	Updated third-party firewall tpfw1.
Explanation	A third-party firewall was modified.
Possible failure causes	· The controller is not the active leader. · You have no privilege to perform the operation. · Configuration recovery is in progress. · UUID format error. · The UUID can't be modified. · Invalid JSON format. · Incorrect UUID format of the synchronization operation. · Can't find the BUS type for the operation. · Team HA startup failure. · Team HA processing error. · Team HA update failure. · The configuration doesn't exist. · Failed to modify the configuration. · The name field up to 60 characters, case sensitive. Valid characters include Chinese characters, letters, digits, and underscores (_). · The description field up to 255 characters, case sensitive. · The name of the third-party firewall can't be modified. · The redirect IP address can't be modified. · The dedicated IP address can't be modified. · The service NE ID can't be modified. · A vRouter link already exists on the third-party firewall. · The UUID of the vRouter can't be modified. · The redirect vRouter doesn't exist. · Failed to add the redirect routing table. · Failed to add the dedicated routing table. · Failed to add the routes to the third-party firewall. · Failed to delete the dedicated routing table. · Failed to delete the redirect routing table. · Failed to bind the redirect subnet to the redirect vRouter. · Failed to unbound the redirect subnet from the redirect vRouter. · The redirect vRouter and dedicated vRouter are the same. · The configuration doesn't exist. · Data format error. · Failed to update the data in the database. · You have no privilege to perform this operation.

Delete TPFW

Keyword	DELETE_TPFW_OP
Message text	Deleted third-party firewall $1.
Variable fields	$1: Name of the third-party firewall. If the firewall name does not exist, its UUID is displayed.
Example	Deleted third-party firewall tpfw1.
Explanation	A third-party firewall was deleted.
Possible failure causes	· The controller is not the active leader. · You have no privilege to perform the operation. · Configuration recovery is in progress. · UUID format error. · Incorrect UUID format of the synchronization operation. · Can't find the BUS type for the operation. · Team HA startup failure. · Team HA processing error. · Team HA deletion failure. · The configuration doesn't exist. · Data deletion error. · Can't delete the third-party firewall because it is already bound to a Redirect vRouter. · Failed to unbind the dedicated vRouter from the dedicated subnet. · You have no privilege to perform this operation.

Create vRouter link

Keyword	CREATE_VROUTERLINK_OP
Message text	Created vRouter link $1.
Variable fields	$1: Name of the vRouter link. If the vRouter link name does not exist, its UUID is displayed.
Example	Created vRouter link vrlink1.
Explanation	A vRouter link was added.
Possible failure causes	· The controller is not the active leader. · You have no privilege to perform the operation. · Configuration recovery is in progress. · Invalid JSON format. · The configuration item already exists. · The name field up to 60 characters, case sensitive. Valid characters include Chinese characters, letters, digits, and underscores (_). · Team HA startup failure. · Data format error. · Failed to insert the data. · Failed to add the configuration. · Failed to create the vRouter link. · vRouter 1 doesn't exist. · vRouter 2 doesn't exist. · vRouter 1 can't be null. · vRouter 2 can't be null. · You have no privilege to perform this operation.

Delete vRouter link

Keyword	DELETE_VROUTERLINK_OP
Message text	Deleted vRouter link $1.
Variable fields	$1: Name of the vRouter link. If the vRouter link name does not exist, its UUID is displayed.
Example	Deleted vRouter link vrlink1.
Explanation	A vRouter link was deleted.
Possible failure causes	· The controller is not the active leader. · You have no privilege to perform the operation. · Configuration recovery is in progress. · UUID format error. · The configuration doesn't exist. · Data format error. · Team HA startup failure. · Team HA deletion failure. · Data deletion error. · Failed to delete the vRouter link. · You have no privilege to perform this operation.

VMM

This section contains VMM messages.

Create vCenter

Keyword	CREATE_VCENTER_OP
Message text	Created vCenter $1.
Variable fields	$1: vCenter parameter body.
Example	Created vCenter { "uuid":"bce117e8-bf42-420f-9e2b-ca2a6cad9069", "name":"vCenter", "ip address":"3.2.6.3", "port number":"443", "tls protocol":"TLSv1.2", "certificate":"vcenter.cer", "connect status":"false", "smooth status":"consistant" “vlan_pool_id”:”6c28a7e8-b242-420f-a22b-ca2a691ca260” }.
Explanation	A vCenter server was created.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · The request is invalid. · Invalid vCenter name. · Invalid username. · Invalid password. · Invalid IP address. · The IP address already exists. · The specified certificate does not exist or is not activated. · Invalid TLS protocol. · The port number must be an integer in the range of 0 to 65535. · The vCenter name already exists. · The UUID already exists. · Each vCenter server must have a unique name. · Each vCenter server must have a unique UUID. · Each vCenter server must have a unique IP address. · The specified VLAN pool does not exist. · The VLAN pool has already been used by another resource. · Failed to bind the vCenter platform to the VLAN pool. · Please specify a VLAN pool configured for tenant access networks. · You have no privilege to perform this operation.

Update vCenter

Keyword	UPDATE_VCENTER_OP
Message text	Updated vCenter $1.
Variable fields	$1: vCenter parameter body.
Example	Update vCenter { "uuid":"f4c6e8be-cea2-4b2a-9738-2aa6d7108e38", "name":"vCenter", "ip address":"6.3.2.3", "port number":"443", "tls protocol":"TLSv1.2", "certificate":"vcenter.cer", "connect status":"false", "smooth status":"consistant" }.
Explanation	A vCenter server was edited.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · The request is invalid. · The specified vCenter does not exist. · The vCenter name cannot be modified. · The IP address cannot be modified. · Invalid username. · Invalid password. · Invalid TLS protocol. · The specified certificate does not exist or is not activated. · The specified VLAN pool does not exist. · The VLAN pool has already been used by another resource. · The port number must be an integer in the range of 0 to 65535. · Failed to bind the vCenter platform to the VLAN pool. · Failed to unbind the vCenter platform to the VLAN pool. · Please specify a VLAN pool configured for tenant access networks. · You have no privilege to perform this operation.

Delete vCenter

Keyword	DELETE_VCENTER_OP
Message text	Deleted vCenter $1.
Variable fields	$1: vCenter parameter body.
Example	Delete vCenter { "uuid":"f4c6e8be-cea2-4b2a-9738-2aa6d7108e38", "name":"vCenter", "ip address":"6.3.2.3", "port number":"4432", "tls protocol":"TLSv1.2", "certificate":"vcenter.cer", "connect status":"false", "smooth status":"consistant" }.
Explanation	A vCenter server was deleted.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · The specified vCenter does not exist. · Cannot delete the vCenter because it contains VDSs. · The specified VLAN ID in the VLAN pool has been allocated. · The specified VLAN pool does not exist. · Failed to unbind the vCenter platform to the VLAN pool. · You have no privilege to perform this operation.

Create VDS

Keyword	CREATE_VDS_OP
Message text	Added vCenter VDS $1.
Variable fields	$1: VDS parameter body.
Example	Added vCenter VDS { "name":"21", "dc_name":"21" “vds_version”:”6.0.0” }.
Explanation	A VDS was created.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · The request is invalid. · Illegal VDS name. · Illegal data center name. · In vCenter, only one vCenter data center and vCenter VDS binding relationship can be set. · The specified vCenter does not exist. · Invalid VDS version. · VDS already exists. · You have no privilege to perform this operation.

Delete VDS

Keyword	DELETE_VDS_OP
Message text	Deleted vCenter VDS $1.
Variable fields	$1: VDS parameter body.
Example	Deleted vCenter VDS { "name":"21", "dc_name":"21" }
Explanation	A VDS was deleted.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · The VDS does not exist. · Cannot delete the VDS because it has distributed port groups. · The specified vCenter does not exist. · You have no privilege to perform this operation.

Create QoS profile

Keyword	CREATE_QOS_PROFILE_OP
Message text	Created QoS profile $1.
Variable fields	$1: QoS profile parameter body.
Example	Created QoS profile { "name":"qos1", "uuid":"2c0c46d2-84a4-4848-884e-91cac7fdb84d", "inbound_policy":{ "avg_bandwidth":"100000", "peak_bandwidth":"100000", "burst_size":"102400" }, "outbound_policy":{ "avg_bandwidth":"100000", "peak_bandwidth":"100000", "burst_size":"102400" } }
Explanation	A QoS profile was created.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · The request is invalid. · Illegal QoS profile name. · The QoS profile already exists. · The average bandwidth cannot be greater than the peak bandwidth. · The average bandwidth value must be an integer in the range of 1 to 9007199254740991. · The peak bandwidth value must be an integer in the range of 1 to 9007199254740991. · The burst size must be an integer in the range of 1 to 9007199254740991. · Each QoS profile must have a unique name. · Each QoS profile must have a unique UUID. · The UUID already exists. · Invalid QoS policy status. · You have no privilege to perform this operation.

Update QoS profile

Keyword	UPDATE_QOS_PROFILE_OP
Message text	Updated QoS profile $1.
Variable fields	$1: QoS profile parameter body.
Example	Updated QoS profile { "name":"qos1", "uuid":"2c0c46d2-84a4-4848-884e-91cac7fdb84d", "inbound_policy":{ "avg_bandwidth":"100000", "peak_bandwidth":"100000", "burst_size":"102400" }, "outbound_policy":{ "avg_bandwidth":"100000", "peak_bandwidth":"100000", "burst_size":"102400" } }
Explanation	A QoS profile was edited.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · The request is invalid. · Illegal QoS profile name. · The specified QoS profile does not exist. · The average bandwidth cannot be greater than the peak bandwidth. · The average bandwidth value must be an integer in the range of 1 to 9007199254740991. · The peak bandwidth value must be an integer in the range of 1 to 9007199254740991. · The burst size must be an integer in the range of 1 to 9007199254740991. · Cannot edit the QoS profile name. · Invalid QoS policy status. · You have no privilege to perform this operation.

Delete QoS profile

Keyword	DELETE_QOS_PROFILE_OP
Message text	Deleted QOS profile $1.
Variable fields	$1: QoS profile parameter body.
Example	Deleted QOS profile { "name":"qos1", "uuid":"2c0c46d2-84a4-4848-884e-91cac7fdb84d", "inbound_policy":{ "avg_bandwidth":"100000", "peak_bandwidth":"100000", "burst_size":"102400" }, "outbound_policy":{ "avg_bandwidth":"100000", "peak_bandwidth":"100000", "burst_size":"102400" } }
Explanation	A QoS profile was deleted.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · The specified QoS profile does not exist. · The specified QoS profile has been used and cannot be deleted. · You have no privilege to perform this operation.

Create VDS distributed port group

Keyword	CREATE_VDS_DISTRIBUTED_PORT_GROUP_OP
Message text	Created distributed port group $1
Variable fields	$1: Distributed port group parameter body.
Example	Created distributed port group { "uuid":"ba9d834d-7bcc-4dde-987a-b89167df29a2", "name":"ffffffff-0000-0000-0000-000000000001\|xuni\|21", "vdsID":"d0e9522b-c8f4-4a72-bfb5-76770cd15c00", "vlanType":"VLAN", "vlanRange":"21", "qosID":"f332a43f-a801-42c8-bdfc-78be1c9c1949", "vnetworkID":"9585fee4-52eb-4037-b410-3c7e7d218d01", "uplinkMode":"DEPENDENTUPLINK", "lagName":"null", "lbAlgorithms":"ROUTE_ON_ORIGINATING_VIRTUAL_POR", "interfaceAvailabilityZone":"null", “qosInboundFlowStatus":"enable", "qosOutboundFlowStatus":"disable" }.
Explanation	A distributed port group was created.
Possible failure causes	· Invalid parameter. · The distributed port group name cannot exceed 80 characters. · The specified vNetwork does not exist. · The link aggregation group name cannot exceed 16 characters. · The specified uplink mode does not exist. · The VLAN type does not exist. · Invalid VLAN ID or VLAN range. · Duplicated distributed port group names exist. · The distributed port group already exists. · Each distributed port group must have a unique UUID. · The distributed port group name already exists. · The specified QoS profile does not exist. · The specified uplink LB policy does not exist. · The VLAN type does not exist. · VLAN ID needs to be specified or VLAN pool needs to be configured. · No VLAN ID available. · The distributed port group name already exists in the same vCenter datacenter. · Please specify a VLAN pool for the vCenter platform when no VLAN ID is specified. · When multiple distributed port groups for different vNetworks use the same interface availability zone, make sure they do not contain overlapping VLAN IDs. · When multiple distributed port groups for different vNetworks use the same interface availability zone, make sure they do not contain the same or overlapping VLAN IDs. · No VLAN ID is available in the VLAN pool. · The specified LAG name does not exist on VDS. · You have no privilege to perform this operation. · The VLAN ID must be an integer in the range of 1 to 4094. · Invalid egress traffic shaping status. · Invalid ingress traffic shaping status. · When no QoS profile is bound to the distributed port group, you must leave both the ingress traffic shaping status and egress traffic shaping status fields empty. · On the same vCenter server, if the vCenter VDSs of two distributed port groups are the same and the VLAN IDs of the two distributed port groups overlap, the vNetworks of the two distributed port groups must be the same. · On the same vCenter server, if the vCenter VDSs of two distributed port groups are different, the VLAN IDs of the two distributed port groups cannot overlap.

Update VDS distributed port group

Keyword	UPDATE_VDS_DISTRIBUTED_PORT_GROUP_OP
Message text	Updated distributed port group $1
Variable fields	$1: Part of the distributed port group parameter body.
Example	Updated distributed port group { "uuid":"d150f90e-8ac5-4299-a9e0-27774e9315fc", "name":"ffffffff-0000-0000-0000-000000000001\|xuni3\|21", "vdsID":"d0e9522b-c8f4-4a72-bfb5-76770cd15c00", "vlanType":"VLAN", "vlanRange":"21", "qosID":"f332a43f-a801-42c8-bdfc-78be1c9c1949", "vnetworkID":"314ad88b-a105-4884-94f4-21d892e5eb60", "uplinkMode":"DEPENDENTUPLINK", "lagName":"null", "lbAlgorithms":"ROUTE_ON_ORIGINATING_VIRTUAL_POR", "interfaceAvailabilityZone":"null", “qosInboundFlowStatus":"enable", "qosOutboundFlowStatus":"disable" }.
Explanation	A distributed port group was edited.
Possible failure causes	· Invalid parameter. · Invalid UUID. · The specified distributed port group does not exist. · The specified uplink mode does not exist. · The specified uplink LB policy does not exist. · The specified QoS profile does not exist. · Cannot edit the distributed port group name. · When multiple distributed port groups for different vNetworks use the same interface availability zone, make sure they do not contain the same or overlapping VLAN IDs. · Cannot edit the interface availability zone. It is being used by a distributed port group that has VMs. · The specified LAG name does not exist on VDS. · You have no privilege to perform this operation. · Invalid egress traffic shaping status. · Invalid ingress traffic shaping status. · When no QoS profile is bound to the distributed port group, you must leave both the ingress traffic shaping status and egress traffic shaping status fields empty.

Delete VDS distributed port group

Keyword	DELETE_VDS_DISTRIBUTED_PORT_GROUP_OP
Message text	Deleted distributed port group $1
Variable fields	$1: Part of the distributed port group parameter body.
Example	Deleted distributed port group { "uuid":"d2c4bad4-a81a-449c-a8d8-795647a75f26", "name":"ffffffff-0000-0000-0000-000000000001\|xuni3\|22", "vdsID":"d0e9522b-c8f4-4a72-bfb5-76770cd15c00", "vlanType":"VLAN", "vlanRange":"22", "qosID":"436192ec-b605-4d14-a317-0f1dea87de9a", "vnetworkID":"314ad88b-a105-4884-94f4-21d892e5eb60", "uplinkMode":"DEPENDENTUPLINK", "lagName":"null", "lbAlgorithms":"ROUTE_ON_ORIGINATING_VIRTUAL_POR", "interfaceAvailabilityZone":"null", "qosInboundFlowStatus":"disable", "qosOutboundFlowStatus ":"disable" }.
Explanation	A distributed port group was deleted.
Possible failure causes	· Invalid parameter. · Invalid UUID. · The distributed port group contains VMs and cannot be deleted. · The specified distributed port group does not exist. · You have no privilege to perform this operation.

Sync vCenter data

Keyword	SYNC_VCENTER_OP
Message text	Synchronized data of vCenter: $1.
Variable fields	$1: vCenter server name.
Example	Synchronized data of vCenter: vCenter1.
Explanation	The configuration differences of a vCenter server were repaired.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · vCenter connection error. · The vCenter does not exist. · Cannot audit or synchronize a vCenter that is in Audit or Sync state. · You have no privilege to perform this operation.

Sync vPort data of vCenter

Keyword	SYNC_VCENTER_VPORT_OP
Message text	Synchronized data of vPort: $1
Variable fields	$1: vPort UUID.
Example	Synchronized data of vPort: 29a70df9-cdee-4e9b-9ce1-df7f324246df
Explanation	The configuration differences of a vPort were repaired.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · vCenter connection error. · The vCenter does not exist. · The vPort doesn't exist. · Cannot audit or synchronize a vCenter that is in Audit or Sync state. · You have no privilege to perform this operation.

Updated auto audit and sync settings of vCenter

Keyword	UPDATE_VCENTER_SMOOTH_SETTING_OP
Message text	Updated auto audit and sync settings for vCenters: audit interval:$1 minutes, auto audit state:$2, auto sync state:$3, audit schedule:$4, Schedule:{ "months":$5, "days of week":$6, "days of month":$7, "hh":$8, "mm":$9, "ss":$10 }.
Variable fields	$1: Audit interval. $2: Auto audit state. $3: Auto sync state. $4: Audit schedule. $5: Monthly. $6: Weekly. $7: Daily. $8: hh $9: mm $10: ss
Example	Updated auto audit and sync settings for vCenters: audit interval:null minutes, auto audit state:true, auto sync state:OFF, audit schedule:TIMING, Schedule:{ "months":"", "days of week":"?", "days of month":"", "hh":"0", "mm":"0", "ss":"0" }.
Explanation	Updated auto audit and sync settings for vCenters.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · The request is invalid. · Invalid auto smooth setting. · The value of the auto sync interval must be an integer in the range of 60 to 10080. · Invalid sync parameters. · The vCenter does not exist. · You have no privilege to perform this operation. · When the audit schedule is interval-based, you must specify the audit interva. · Please configure Cron expression parameters. · Invalid Cron expression parameters.

Audit vCenter

Keyword	AUDIT_VCENTER_OP
Message text	Audited data of vCenter: $1.
Variable fields	$1: vCenter server name.
Example	Audited data of vCenter: vcenter1.
Explanation	A vCenter server was audited.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · vCenter connection error. · The vCenter does not exist. · Cannot audit or synchronize a vCenter that is in Audit or Sync state. · You have no privilege to perform this operation.

Export vCenter difference details

Keyword	EXPORT_VCENTER_DIFFERENCE_DETAILS_OP
Message text	Exported vCenter difference details: $1.
Variable fields	$1: vCenter server name.
Example	Exported vCenter difference details: vcenter1.
Explanation	The difference details of a vCenter server were exported.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · The vCenter does not exist. · The vCenter platform is in Audit or Sync state. Please export the differences later. · The specified vCenter platform is exporting configuration differences. Please try again later. · You have no privilege to perform this operation.

Create interface availability zone

Keyword	CREATED_ZONE_OP
Message text	Created interface availability zone: $1.
Variable fields	$1: Interface availability zone information.
Example	Created interface availability zone: { "interface_availability_zones": [ { "id": "0ef2a524-b889-4fc9-8ab5-91b8287a5403", "name": "group01", "bind_port_list": [ { "device_id": "1ef2a524-b889-4fc9-8ab5-91b8287a5402", "port_name": "Ten-GigabitEthernet1/0/48" } ] }, { "id": "0ef2a524-b889-4fc9-8ab5-91b8287a540d", "name": "group02", "bind_port_list": [ { "device_id": "1ef2a524-b889-4fc9-8ab5-91b8287a5402", "port_name": "Ten-GigabitEthernet1/0/47" } ] } ] }
Explanation	An interface availability zone was created.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · The specified resource does not exist. · Invalid parameter. · The specified device does not exist. · The device to which the interface belongs or the device to which a bound interface belongs is inactive. · The device type doesn't match. · Non-VTEP interfaces exist. · Invalid UUID. · Invalid interface availability zone name. · Duplicate interface availability zone name. · Duplicate interface availability zone UUID. · Duplicate interfaces exist in the interface availability zone. · An interface availability zone already exists with the specified name. · The specified device interface has already been bound to another interface availability zone. · You have no privilege to perform this operation.

Delete interface availability zone

Keyword	DELETED_ZONE_OP
Message text	Deleted interface availability zone: $1.
Variable fields	$1: Interface AZ information.
Example	Deleted interface availability zone { "name":" group02", "id":"cc7c3ead-0f7a-4422-8fcd-18d1e1f5cae9", "bind_port_list":[], }
Explanation	An interface availability zone was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · The specified interface availability zone does not exist. · Cannot delete the interface availability zone. It has already been used by a distributed port group. · You have no privilege to perform this operation.

Update interface availability zone

Keyword	UPDATED_ZONE_OP
Message text	Updated interface availability zone: $1.
Variable fields	$1: Interface availability zone information.
Example	Updated interface availability zone: { "interface_availability_zone": { "id": "0ef2a524-b889-4fc9-8ab5-91b8287a540d", "name": "group01", "bind_port_list": [ { "device_id": "1ef2a524-b889-4fc9-8ab5-91b8287a5402", "port_name": "Ten-GigabitEthernet1/0/48" } ] } }
Explanation	An interface availability zone was edited.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · The specified resource does not exist. · Invalid parameter. · The specified device does not exist. · The device to which the interface belongs or the device to which a bound interface belongs is inactive. · The device type doesn't match. · Non-VTEP interfaces exist. · The specified device interface is bound to another interface availability zone. · Invalid UUID. · Invalid interface availability zone name. · You have no privilege to perform this operation.

Discover data of vCenter

Keyword	DISCOVER_VCENTER_OP
Message text	Discovered data of vCenter: $1.
Variable fields	$1: vCenter server name.
Example	Discovered data of vCenter: vCenter1.
Explanation	The data of a vCenter server was discovered.
Possible failure causes	· The specified vCenter does not exist. · vCenter connection error. · The vCenter status does not allow audit smoothing and reverse management related operations. · You have no privilege to perform this operation.

Pull and incorporate data from vCenter

Keyword	REVERSE_SYNC_VCENTER_OP
Message text	Pulled and incorporated data from vCenter: $1.
Variable fields	$1: vCenter server name.
Example	Pulled and incorporated data from vCenter: vCenter1.
Explanation	The data of a vCenter server was pulled and incorporated.
Possible failure causes	· The specified vCenter does not exist. · vCenter connection error. · The vCenter status does not allow audit smoothing and reverse management related operations. · Invalid parameter. · The data to incorporate is inconsistent with the data discovered. · The specified vNetwork does not exist. · The specified VDS already exists. · You have no privilege to perform this operation.

Create RHVM

Keyword	CREATE_RHVM_OP
Message text	Created RHVM $1.
Variable fields	$1: RHVM parameter body.
Example	Created RHVM { "uuid":"cd05ab0b-d499-435b-80a5-d594282eb525", "name":"yuyang", "ip address":"192.168.125.1", "port number":"443", "vlan pool":"vlan-zj", "connect status":"false" "certificate name":"null", "smooth status":"init", "reverse status":"init" }.
Explanation	A RHV manager was created.
Possible failure causes	· The request is invalid. · Unknown error code. · The controller is not the active leader. · Server processing error. · The UUID already exists. · Invalid RedHat VM name. · Invalid username. · Invalid password. · The port number must be an integer in the range of 0 to 65535. · Invalid IP address. · Please specify a VLAN pool configured for tenant access networks. · The specified VLAN pool does not exist. · The RedHat VM name already exists. · The IP address already exists. · Failed to bind the RHVM to a VLAN pool. · Duplicate RHVM IPs in bulk creation. · Duplicate RHVM names in bulk creation. · Duplicate RHVM UUIDs in bulk creation. · You have no privilege to perform this operation. · The specified certificate does not exist or is not activated.

Update RHVM

Keyword	UPDATE_RHVM_OP
Message text	Updated RHVM $1.
Variable fields	$1: RHVM parameter body.
Example	Updated RHVM { "uuid":"96bd9627-caf0-436e-aad1-885fe62ec274", "name":"13", "ip address":"192.168.25.3", "port number":"443", "vlan pool":"null", "connect status":"false", "certificate name":"null", "smooth status":"init", "reverse status":"init" }.
Explanation	A RHV manager was edited.
Possible failure causes	· The request is invalid. · Unknown error code. · The controller is not the active leader. · Server processing error. · The specified RedHat VM does not exist. · Invalid username. · Invalid password. · Please specify a VLAN pool configured for tenant access networks. · The specified VLAN pool does not exist. · The specified VLAN ID in the VLAN pool has been allocated. · Cannot edit the RHVM name. · The port number must be an integer in the range of 0 to 65535. · The IP address cannot be modified. · You have no privilege to perform this operation. · The specified certificate does not exist or is not activated.

Delete RHVM

Keyword	DELETE_RHVM_OP
Message text	Deleted RHVM $1.
Variable fields	$1: RHVM parameter body.
Example	Deleted RHVM { "uuid":"ecc6f914-79dc-4fe2-97f1-5714c30f7f1c", "name":"1", "ip address":"192.168.23.3", "port number":"443", "vlan pool":"null", "connect status":"false", "certificate name":"null", "smooth status":"init", "reverse status":"init" }.
Explanation	A RHV manager was deleted.
Possible failure causes	· The request is invalid. · Unknown error code. · The controller is not the active leader. · Server processing error. · The specified RedHat VM does not exist. · Cannot delete the RHVM, because it has logical networks. · You have no privilege to perform this operation.

Reconnect RHVM

Keyword	RECONNECT_RHVM_OP
Message text	Reconnected RHVM $1.
Variable fields	$1: RHVM parameter body.
Example	Reconnected RHVM { "uuid":"96bd9627-caf0-436e-aad1-885fe62ec274", "name":"13", "ip address":"192.168.25.3", "port number":"443", "vlan pool":"null", "connect status":"false", "certificate name":"null", "smooth status":"init", "reverse status":"init" }.
Explanation	A RHV manager was reconnected.
Possible failure causes	· The request is invalid. · Unknown error code. · The controller is not the active leader. · Server processing error. · The specified RedHat VM does not exist. · The controller failed to connect to the RHVM. The account is locked or disabled. · The controller failed to connect to the RHVM. The account failed to pass authentication. · The controller failed to connect to the RHVM. · You have no privilege to perform this operation.

Create logical network

Keyword	CREATE_LOGICAL_NETWORK_OP
Message text	Created logical network $1.
Variable fields	$1: Logical network parameter body.
Example	Created logical network { "uuid":"da51f7ee-8d3f-4b62-8759-5ab93603f42b", "name":"default\|zjtnetwork\|123", "rhvmId":"760c2dd3-8512-48f4-bbce-862b1319923e", "rhvmName":"rhvm", "vlanType":"VLAN", "vlanRange":"123", "dcName":"Default", "vnetworkID":"4d8091b6-2104-4757-a9d7-7436ac754b58", "vnetworkName":"zjtnetwork" }.
Explanation	A logical network was created.
Possible failure causes	· The controller is not the active leader. · The request is invalid. · Invalid parameter. · Invalid UUID. · The specified RedHat VM does not exist. · Cannot create the logical network, because the RHVM is disconnected. · The specified vNetwork does not exist. · Illegal data center name. · The data center does not exist. · Invalid VLAN type. · The specified VLAN ID in the VLAN pool has been allocated. · Please configure a VLAN ID for the logical network because the RedHat VM bound to the network is not configured with a VLAN pool. · No VLAN ID is available in the VLAN pool. · The VLAN ID must be an integer in the range of 1 to 4094. · The logical network name cannot exceed 256 characters or be all spaces. · The logical network name already exists. · You have no privilege to perform this operation.

Delete logical network

Keyword	DELETE_LOGICAL_NETWORK_OP
Message text	Deleted logical network $1.
Variable fields	$1: Logical network parameter body.
Example	Deleted logical network { "uuid":"da51f7ee-8d3f-4b62-8759-5ab93603f42b", "name":"default\|zjtnetwork\|123", "rhvmId":"760c2dd3-8512-48f4-bbce-862b1319923e", "rhvmName":"rhvm", "vlanType":"VLAN", "vlanRange":"123", "dcName":"Default", "vnetworkID":"4d8091b6-2104-4757-a9d7-7436ac754b58", "vnetworkName":"zjtnetwork", }.
Explanation	A logical network was deleted.
Possible failure causes	· The controller is not the active leader. · The specified logical network does not exist. · Cannot delete the logical network, because it has VMs. · You have no privilege to perform this operation.

Audit data for RHVM

Keyword	AUDIT_RHVM_OP
Message text	Audited data for RHVM: $1.
Variable fields	$1: RHVM name
Example	Audited data for RHVM: RHVM.
Explanation	Audited data for an RHVM.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · The specified RedHat VM does not exist. · The connection state of the RHVM is abnormal. · The system is auditing or synchronizing data for the RHVM. Please try again later. · The system is detecting or incorporating data on the RHVM. Please try again later. · You have no privilege to perform this operation.

Sync data for RHVM

Keyword	SYNC_RHVM_OP
Message text	Synchronized data for RHVM: $1.
Variable fields	$1: RHVM name
Example	Synchronized data for RHVM: RHVM.
Explanation	Synchronized data for an RHVM.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · The specified RedHat VM does not exist. · The connection state of the RHVM is abnormal. · The system is auditing or synchronizing data for the RHVM. Please try again later. · The system is detecting or incorporating data on the RHVM. Please try again later. · You have no privilege to perform this operation.

Detect data on RHVM

Keyword	DISCOVERY_RHVM_OP
Message text	Detected data on RHVM: $1.
Variable fields	$1: RHVM name
Example	Detected data on RHVM: RHVM.
Explanation	Detected data on an RHVM.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · The specified RedHat VM does not exist. · The connection state of the RHVM is abnormal. · The system is auditing or synchronizing data for the RHVM. Please try again later. · The system is detecting or incorporating data on the RHVM. Please try again later. · You have no privilege to perform this operation.

Pull and incorporate data from RHVM

Keyword	REVERSE_SYNC_RHVM_OP
Message text	Pulled and incorporated data from RHVM: $1.
Variable fields	$1: RHVM name
Example	Pulled and incorporated data from RHVM: RHVM.
Explanation	Pulled and incorporated data from an RHVM.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · The specified RedHat VM does not exist. · The connection state of the RHVM is abnormal. · The system is auditing or synchronizing data for the RHVM. Please try again later. · The system is detecting or incorporating data on the RHVM. Please try again later. · Invalid parameter. · The data to incorporate is inconsistent with the data discovered. · Data incorporation failed. Make sure data detection has been performed and new configuration exists. · Please specify a vNetwork. · The specified vNetwork does not exist. · You have no privilege to perform this operation.

Update auto audit and sync settings of RHVM

Keyword	UPDATE_RHVM_SMOOTH_SETTING_OP
Message text	Updated auto audit and sync settings for RHVMs: audit interval:$1 minutes, auto audit state:$2, auto sync state:$3, audit schedule:$4, Schedule:{ "months":$5, "days of week":$6, "days of month":$7, "hh":$8, "mm":$9, "ss":$10 }.
Variable fields	$1: Audit interval. $2: Auto audit state. $3: Auto sync state. $4: Audit schedule. $5: Monthly. $6: Weekly. $7: Daily. $8: hh $9: mm $10: ss
Example	Updated auto audit and sync settings for RHVMs: audit interval:null minutes, auto audit state:true, auto sync state:OFF, audit schedule:TIMING, Schedule:{ "months":"", "days of week":"?", "days of month":"", "hh":"19", "mm":"40", "ss":"0" }.
Explanation	Updated auto audit and sync settings for RHVMs.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · The request is invalid. · The value of the auto sync interval must be an integer in the range of 60 to 10080. · Invalid auto smooth setting. · Invalid sync parameters. · You have no privilege to perform this operation. · Invalid audit schedule. · When the audit schedule is interval-based, you must specify the audit interval. · Please configure Cron expression parameters. · Invalid Cron expression parameters.

Create OpenStack-based cloud platform

Keyword	CREATE_OPENSTACK_OP
Message text	Created OpenStack-based cloud platform $1.
Variable fields	$1: OpenStack-based cloud platform parameter body.
Example	Created OpenStack-based cloud platform { "uuid":"17be5f2d-cd3a-4799-b828-bc5f925e958c", "name":"op1", "vni range list":"[1-2]", "data sync status":"init", "controller node list":"[]", "default openstack":"false", "openstack config":"{ "network overlay mode":"true", "ip mac binding":"true", "dhcp lease time":"365", "network force flat":"true", "directly external suffix":"null", "generate vrf":"false", "enableMultiSeg":"false", "tenantGwName":"null", "directly external":"ANY", "emptyRuleAction":"deny", "tenantGwSelectionStrategy":"match_first", "network Node access strategy":"NO_ACCESS", "dhcp service proxy":"false", }" }.
Explanation	An OpenStack-based cloud platform was created.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · The request is invalid. · Please specify a VNI range for the cloud platform. · The start number of a VNI range cannot be greater than the end number. · The UUID already exists. · Invalid cloud platform name. · Invalid tenant name. · Invalid username. · Invalid password. · The port number must be an integer in the range of 1 to 65535. · Invalid URL type. · Invalid certificate version. · You can specify a domain name only when the certificate version is set to V3. · Invalid domain name. · The cloud platform name already exists. · The VNI range conflicts with a VNI range on another OpenStack-based cloud platform. · Each OpenStack-based cloud platform must have a unique IP address. · Each OpenStack-based cloud platform must have a unique name. · Each OpenStack-based cloud platform must have a unique UUID. · When the certificate version is V2, the region cannot be configured. · The IP address of the controller node is invalid. · The IP address of the controller node already exists. · The IP address of the controller node cannot be duplicated. · Invalid region. · Invalid keystone URL. · When the communication mode is Keystone authentication, please specify a Keystone URL for the cloud platform. · When the communication mode is WebSocket, the username field is not supported. · When the communication mode is WebSocket, the password field is not supported. · When the communication mode is WebSocket, the tenant field is not supported. · When the communication mode is WebSocket, the certificate version field is not supported. · When the communication mode is WebSocket, the domain field is not supported. · When the communication mode is WebSocket, the URL type field is not supported. · When the communication mode is WebSocket, the Keystone URL field is not supported. · When the communication mode is WebSocket, the northbound link state status field is not supported. · When the communication mode is WebSocket, the region field is not supported. · Please specify a valid value for the keystone auth parameter. · The OpenStack-based cloud platform cannot have the same region and Keystone URL as any other OpenStack-based cloud platform. · You have no privilege to perform this operation. · Invalid empty rule action for the security policy. · Invalid external network configuration. · Invalid tenant border gateway policy. · When the value of the tenant border gateway policy is not the border gateway name, the border gateway name must be empty. · Invalid border gateway name. · Invalid vRouter name suffix. · The DHCP lease duration must be an integer in the range of 0 to 365.

Update OpenStack-based cloud platform

Keyword	UPDATE_OPENSTACK_OP
Message text	Updated OpenStack-based cloud platform $1.
Variable fields	$1: OpenStack-based cloud platform parameter body.
Example	Updated OpenStack-based cloud platform { "uuid":"17be5f2d-cd3a-4799-b828-bc5f925e958c", "name":"op1", "vni range list":"[1-2]", "data sync status":"init", "controller node list":"[]", "default openstack":"false", "openstack config":"{ "network overlay mode":"false", "ip mac binding":"true", "dhcp lease time":"365", "network force flat":"true", "directly external suffix":"null", "generate vrf":"false", "enableMultiSeg":"false", "tenantGwName":"null", "directly external":"ANY", "emptyRuleAction":"deny", "tenantGwSelectionStrategy":"match_first", "network Node access strategy":"NO_ACCESS", "dhcp service proxy":"false", }" }.
Explanation	An OpenStack-based cloud platform was edited.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · The request is invalid. · The specified OpenStack-based cloud platform does not exist. · Please specify a VNI range for the cloud platform. · The start number of a VNI range cannot be greater than the end number. · The port number must be an integer in the range of 1 to 65535. · Invalid tenant name. · Invalid username. · Invalid password. · Invalid certificate version. · You can specify a domain name only when the certificate version is set to V3. · Invalid domain name. · Invalid URL type. · The VNI range conflicts with a VNI range on another OpenStack-based cloud platform. · Cannot edit the VNI range. The VNI range is being used by DHCP vPorts. · The IP address of the controller node is invalid. · The IP address of the controller node already exists. · The IP address of the controller node cannot be duplicated. · When the communication mode is Keystone authentication, please specify a Keystone URL for the cloud platform. · When the communication mode is WebSocket, the username field is not supported. · When the communication mode is WebSocket, the password field is not supported. · When the communication mode is WebSocket, the tenant field is not supported. · When the communication mode is WebSocket, the certificate version field is not supported. · When the communication mode is WebSocket, the domain field is not supported. · When the communication mode is WebSocket, the URL type field is not supported. · When the communication mode is WebSocket, the Keystone URL field is not supported. · When the communication mode is WebSocket, the northbound link state status field is not supported. · When the communication mode is WebSocket, the region field is not supported. · You have no privilege to perform this operation. · Invalid empty rule action for the security policy. · Invalid external network configuration. · Invalid tenant border gateway policy. · When the value of the tenant border gateway policy is not the border gateway name, the border gateway name must be empty. · Invalid border gateway name. · Invalid vRouter name suffix. · The DHCP lease duration must be an integer in the range of 0 to 365.

Delete OpenStack-based cloud platform

Keyword	DELETE_OPENSTACK_OP
Message text	Deleted OpenStack-based cloud platform $1.
Variable fields	$1: OpenStack-based cloud platform parameter body.
Example	Deleted OpenStack-based cloud platform { "uuid":"851d14bb-0938-456e-a076-8aa931330675", "name":"Openstack", "vni range list":"[600-999]", "data sync status":"consistent" "controller node list":"[ControllerNode{ip='192.168.132.221', controllerStatus='connected', openstackUuid='851d14bb-0938-456e-a076-8aa931330675'}]" }.
Explanation	An OpenStack-based cloud platform was deleted.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · Invalid UUID. · The specified OpenStack-based cloud platform does not exist. · Cannot delete the platform. The platform contains DHCP vPorts. · You have no privilege to perform this operation.

Sync data of OpenStack-based cloud platform

Keyword	SYNC_OPENSTACK_OP
Message text	Synchronized data of OpenStack-based cloud platform: $1.
Variable fields	$1: OpenStack-based cloud platform name.
Example	Synchronized data of OpenStack-based cloud platform: OpenStack1.
Explanation	Data differences of an OpenStack-based cloud platform were repaired.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · The specified OpenStack-based cloud platform does not exist. · Cannot start an audit or repair. The northbound links of the platform are abnormal. · Cannot repair the cloud platform. The platform is being audited or repaired. · No controller node is available on the OpenStack-based cloud platform. The OpenStack-based cloud platform cannot start an audit or repair. · You have no privilege to perform this operation. · You cannot repair configuration differences on the OpenStack cloud platform, because the DHCP agent feature is not enabled for the platform.

Update auto audit and sync settings of OpenStack-based cloud platform

Keyword	UPDATE_OPENSTACK_RECONCILIATION_SETTING_OP
Message text	Updated auto audit and sync settings for OpenStack-based cloud platforms: audit interval:$1 minutes, auto audit state:$2, auto sync state:$3, audit schedule:$4, Schedule:{ "months":$5, "days of week":$6, "days of month":$7, "hh":$8, "mm":$9, "ss":$10 }.
Variable fields	$1: Audit interval. $2: Auto audit state. $3: Auto sync state. $4: Audit schedule. $5: Monthly. $6: Weekly. $7: Daily. $8: hh $9: mm $10: ss
Example	Updated auto audit and sync settings for OpenStack-based cloud platforms: audit interval:null minutes, auto audit state:true, auto sync state:true, audit schedule:TIMING, Schedule:{ "months":"", "days of week":"?", "days of month":"", "hh":"19", "mm":"40", "ss":"0" }.
Explanation	Updated auto audit and sync settings for OpenStack-based cloud platforms.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · The request is invalid. · The reconciliation interval must be an integer in the range of 60 to 10080. · Please specify a valid value for the auto reconciliation parameter. · Please specify a valid value for the auto smooth parameter. · You have no privilege to perform this operation. · Invalid audit schedule. · When the audit schedule is interval-based, you must specify the audit interval. · Please configure Cron expression parameters. · Invalid Cron expression parameters.

Audit data of OpenStack-based cloud platform

Keyword	AUDIT_OPENSTACK_OP
Message text	Audited data of OpenStack-based cloud platform: $1.
Variable fields	$1: OpenStack-based cloud platform name.
Example	Audited data of OpenStack-based cloud platform: OpenStack.
Explanation	Data of an OpenStack-based cloud platform was audited.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · The specified OpenStack-based cloud platform does not exist. · Cannot start an audit or repair. The northbound links of the platform are abnormal. · Cannot start audit on a cloud platform. The cloud platform is being audited or repaired. · No controller node is available on the OpenStack-based cloud platform. The OpenStack-based cloud platform cannot start an audit or repair. · You have no privilege to perform this operation. · You cannot audit configuration differences on the OpenStack cloud platform, because the DHCP agent feature is not enabled for the platform.

Create agent

Keyword	CREATE_PLUGIN_AGENT_OP
Message text	Created agent $1.
Variable fields	$1: Agent information.
Example	Created agent { "id":"a12159d8-3817-4e9b-9aa7-6c81c3ee2e12", "host":"network", "binary":"neutron-dhcp-agent", "alive":"false", "agentType":"DHCP agent", "cloudRegionName":"default", "configuration":{ "tunnelingIp":"null", "networkSegmentPhysicalNetwork":"null", } }.
Explanation	An agent was created.
Possible failure causes	· The request is invalid. · Invalid host. · Invalid binary value. · Invalid agent type. · Invalid network segment physical network name. · Invalid device mapping key. · Invalid device mapping value. · Invalid bridge mapping key. · Invalid bridge mapping value. · Invalid icontrol endpoint. · Invalid device name. · The controller is not the active leader. · Configuration recovery is in progress. · The specified OpenStack-based cloud platform does not exist. · Unknown error. · You have no privilege to perform this operation.

Synchronized agents

Keyword	SYNC_PLUGIN_AGENT_OP
Message text	Synchronized agents $1.
Variable fields	$1: Agent information.
Example	Synchronized agents { "id":"e1269b89-5138-4e8c-bc32-66f1a12fd9cd", "host":"network", "binary":"neutron-metadata-agent", "alive":"false", "agentType":"Metadata agent", "cloudRegionName":"default", "configuration":{ "tunnelingIp":"null", "networkSegmentPhysicalNetwork":"null", } }.
Explanation	Agent information was synchronized.
Possible failure causes	· The request is invalid. · Invalid host. · Invalid binary value. · Invalid agent type. · Invalid network segment physical network name. · Invalid device mapping key. · Invalid device mapping value. · Invalid bridge mapping key. · Invalid bridge mapping value. · Invalid icontrol endpoint. · Invalid device name. · The controller is not the active leader. · Configuration recovery is in progress. · The specified OpenStack-based cloud platform does not exist. · Unknown error. · You have no privilege to perform this operation. · Make sure each agent has a unique UUID.

Update agent

Keyword	UPDATE_PLUGIN_AGENT_OP
Message text	Updated agent $1.
Variable fields	$1: Agent information.
Example	Updated agent { "id":"a12159d8-3817-4e9b-9aa7-6c81c3ee2e12", "host":"network", "binary":"neutron-dhcp-agent", "alive":"false", "agentType":"DHCP agent", "cloudRegionName":"default", "configuration":{ "tunnelingIp":"null", "networkSegmentPhysicalNetwork":"null", } }.
Explanation	An agent was edited.
Possible failure causes	· The request is invalid. · Invalid host. · Invalid binary value. · Invalid agent type. · Invalid network segment physical network name. · Invalid device mapping key. · Invalid device mapping value. · Invalid bridge mapping key. · Invalid bridge mapping value. · Invalid icontrol endpoint. · Invalid device name. · The controller is not the active leader. · Configuration recovery is in progress. · The specified agent does not exist. · The specified OpenStack-based cloud platform does not exist. · Unknown error. · You have no privilege to perform this operation.

Delete agent

Keyword	DELETE_PLUGIN_AGENT_OP
Message text	Deleted agent $1.
Variable fields	$1: Agent information.
Example	Deleted agent { "id":"a12159d8-3817-4e9b-9aa7-6c81c3ee2e12", "host":"network", "binary":"neutron-dhcp-agent", "alive":"false", "agentType":"DHCP agent", "cloudRegionName":"default", "configuration":{ "tunnelingIp":"null", "networkSegmentPhysicalNetwork":"null", } }.
Explanation	An agent was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · The specified OpenStack-based cloud platform does not exist. · The specified agent does not exist. · Unknown error. · You have no privilege to perform this operation.

Create vRouter

Keyword	CREATE_ROUTER_OP
Message text	Created vRouter $1.
Variable fields	$1: vRouter information.
Example	Created vRouter { "id":"56a937a9-55ce-48c1-866b-0be6386f16ec", "admin_state_up":"vrouter", "external_gateway_info":"{ "network_id":"10236dae-b97a-49b7-89ed-c225baa39d4e", "enable_snat":"true", "external_fixed_ips":"[FixedIpDto { "ip address":"26.3.3.10", "subnet id":"e2d81808-6b61-4ef2-85c6-65839489172b", }]" }", "name":"vrouter", "routes":"[{ "destination":"23.3.3.3/32", "nexthop":"12.3.3.31" }]", "tenant_id":"2b2151a2-f111-40f0-a0ea-61a76879e972", "tenant_name":"admin", "gw_port_id":"null", "tags":"[]", "cloud_region_name":"openstack", "subnets":"null" }.
Explanation	A vRouter was created.
Possible failure causes	· The request is invalid. · 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 number 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 cannot be configured with the same summary route network. · The vRouters using the public VRF cannot be bound to the same service device 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 bytes. · 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. · The external network bound to the vRouter does not have segments. The vRouter can be bound only to one IPv4 subnet. · The border gateways to the IPv4 and IPv6 external subnets are located on the same interface. You must configure them with the same segment ID. · The external network egress IP has been bound to another vRouter. To bind the current vRouter to the external network egress IP, you must make sure the current vRouter has exactly the same external subnet bindings as that vRouter. · Unknown error. · The address pool does not exist or no IP addresses are available in the address pool. · The segment or border gateway already has a priority. · If a vRouter is bound to both a gateway resource and a network segment, you can configure a priority for either the gateway resource or the network segment, but not both. · The priorities of the gateways bound to the same vRouter must be different. · Invalid tags. · The priority is out of range. · The specified segment doesn't exist. · The specified gateway doesn't exist. · Cannot configure a priority for the gateway resource. For more information, see the online help. · Failed to bind the vRouter to an external network because the specified network is not an indirectly connected external network. · Cannot disable east-west traffic offload in network cloud scenarios. · The public network VRF cannot be configured in the weak control scenario. · You have no privilege to perform this operation. · A vRouter can be bound to subnets or external network vPorts, but not both. · A vRouter cannot be bound to internal network vPorts. · The type of vPorts bound to a vRouter can only be none. · Cannot bind the external network vPort to the vRouter, because the vRouter has been bound to the external network to which the vPort belongs. · A vRouter cannot be bound to multiple IPv6 external network vPorts in the same network. · Cannot bind the external network to the vRouter, because the vRouter has been bound to a vPort in the external network. · You cannot bind VLAN external networks to a vRouter after you bind a flat external network to the vRouter. Only one flat external network can be bound to a vRouter. · A VRF name cannot start with “external_vpn”. · The RT generated based on the segment ID of the vRouter conflicts with the import RT of a Layer 2 DC interconnect associated with the vRouter. · The RT generated based on the segment ID of the vRouter conflicts with the export RT of a Layer 2 DC interconnect associated with the vRouter. · The RT reserved for the vRouter link conflicts with the import RT of a Layer 2 DC interconnect associated with the local or remote vRouter. · The RT reserved for the vRouter link conflicts with the export RT of a Layer 2 DC interconnect associated with the local or remote vRouter. · The RT generated based on the segment ID of the vRouter conflicts with the import RT of the Layer 3 DC interconnect associated with the vRouter. · The RT generated based on the segment ID of the vRouter conflicts with the export RT of the Layer 3 DC interconnect associated with the vRouter. · The RT reserved for the vRouter link conflicts with the import RT of the Layer 3 DC interconnect associated with the local or remote vRouter. · The RT reserved for the vRouter link conflicts with the export RT of the Layer 3 DC interconnect associated with the local or remote vRouter. · Check the directly connected external networks and the border interfaces in the border device group bound to this vRouter with the same segment ID. Make sure only one primary IPv4 address exists for each border interface. · vRouters do not support vPorts in flat external networks. · The vRouter context or external network vPort context has been used in a service chain. · Southbound devices at the following IP addresses were disconnected. · The segment ID cannot be identical to a VXLAN ID in a VXLAN pool or the VXLAN ID reserved for the automation template and the DR system. · Please specify a value for the ip_addr field. · Invalid ip_addr value. · Invalid source_ip value. · Invalid ip_version value. · The IP addresses specified for the ip_addr and source_ip fields must have the same IP version. · The ip_addr and ip_version fields do not match. · The peer IP address cannot be the same as the source IP address. · Please specify the device ID, device name, or both. · Please specify the device ID, device name, or both.

Update vRouter

Keyword	UPDATE_ROUTER_OP
Message text	Updated vRouter $1.
Variable fields	$1: vRouter information.
Example	Updated vRouter { "id":"56a937a9-55ce-48c1-866b-0be6386f16ec", "admin_state_up":"vrouter", "external_gateway_info":"{ "network_id":"10236dae-b97a-49b7-89ed-c225baa39d4e", "enable_snat":"true", "external_fixed_ips":"[FixedIpDto { "ip address":"26.3.3.10", "subnet id":"e2d81808-6b61-4ef2-85c6-65839489172b", }]" }", "name":"vrouter", "routes":"[{ "destination":"23.3.3.3/32", "nexthop":"12.3.3.31" }]", "tenant_id":"2b2151a2-f111-40f0-a0ea-61a76879e972", "tenant_name":"admin", "gw_port_id":"null", "tags":"[]", "cloud_region_name":"openstack", "subnets":"null" }.
Explanation	A vRouter was edited.
Possible failure causes	· The request is invalid. · 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 device 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 and the gateway must have been bound to a device group. · For vRouters bound to a service device 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 number 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 cannot 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. · Make sure all vRouters that use this sharing IP are bound to the same edge device for external network access. · 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. · The exit gateway corresponding to the subnet repeats. · You must specify a priority value for each subnet when more than one subnet is bound to the vRouter. · The tags field has duplicate segment IDs. · The tags field has duplicate priorities. · Invalid priority. · The external subnet is bound to the vRouter. · The external network bound to the vRouter does not have segments. The vRouter can be bound only to one IPv4 subnet. · 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 subnet of the VLAN type segment at the same time. · The vRouter to which the external network belongs is in a vRouter link, and a vPort on the peer vRouter of the vRouter link has been bound to the floating IP address of the external network. · The specified external network is segmented and has only IPv4 subnets. You must bind at least one of its IPv4 subnets to the vRouter. · The external network is segmented. You cannot unbind a subnet from the vRouter if that subnet is an IPv4 subnet and is the only subnet in the external network. · The border gateways to the IPv4 and IPv6 external subnets are located on the same interface. You must configure them with the same segment ID. · The external network egress IP has been bound to another vRouter. To bind the current vRouter to the external network egress IP, you must make sure the current vRouter has exactly the same external subnet bindings as that vRouter. · Unknown error. · The address pool does not exist or no IP addresses are available in the address pool. · The external network specified for the vRouter is not segmented. You can bind only one IPv4 subnet and one IPv6 subnet to the vRouter. · The vRouter is bound to multiple IPv4 and IPv6 external subnets. The network segments to which external subnets of the same IP version are bound cannot be bound to the same border gateway. · The border gateways to the IPv4 and IPv6 external subnets are located on the same interface. You must configure them with the same segment ID. · The segment or border gateway already has a priority. · If a vRouter is bound to both a gateway resource and a network segment, you can configure a priority for either the gateway resource or the network segment, but not both. · You cannot assign priorities to the external subnets bound to the vRouter if they belong to different segments configured with the same border gateway. · The priorities of the gateways bound to the same vRouter must be different. · Invalid tags. · The priority is out of range. · The specified segment doesn't exist. · The specified gateway doesn't exist. · Cannot configure a priority for the gateway resource. For more information, see the online help. · External subnets of the same version bound to the vRouter cannot be bound to the same network segment. · Cannot specify a gateway resource configured with a priority and a segmented external network for a vRouter at the same time. · The external network specified for the vRouter is segmented. You must bind a minimum of one external subnet to the vRouter. · The external network egress IP has already been bound to a vRouter that uses different gateway resources from the current vRouter. Only vRouters that use the same gateway resources can share an external network egress IP. · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot overlap with any vNetwork subnet on another vRouter. · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot overlap with any external subnet on another vRouter. · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot be the same as any vNetwork subnet gateway IP of another vRouter. · The source IP address of a route entry on the vRouter cannot be the same as any vNetwork subnet gateway IP on the vRouter. · The source IP address of a route entry on the vRouter cannot be within any vNetwork subnet on the vRouter. · The source IP address of a route entry on the vRouter cannot be within any external subnet on the vRouter. · Failed to bind the vRouter to an external network because the specified network is not an indirectly connected external network. · Failed to configure BGP peers for the vRouter because the vRouter has been configured with BGP neighbors. · Cannot disable east-west traffic offload in network cloud scenarios. · You cannot bind the routing table to the vRouter. The routing table contains a BFD-enabled route entry whose next hop is a vPort with the same IP address as the gateway IP address of a vNetwork bound to the vRouter. · Failed to enable multicast capabilities because the vRouter has already established a vRouter link. · You have no privilege to perform this operation. · Cannot enable multicast network capabilities for the vRouter because the vRouter has been bound to a Layer 3 DC interconnect. · A vRouter can be bound to subnets or external network vPorts, but not both. · A vRouter cannot be bound to internal network vPorts. · The type of vPorts bound to a vRouter can only be none. · Cannot bind the external network vPort to the vRouter, because the vRouter has been bound to the external network to which the vPort belongs. · A vRouter cannot be bound to multiple IPv6 external network vPorts in the same network. · Cannot bind the external network to the vRouter, because the vRouter has been bound to a vPort in the external network. · You cannot bind VLAN external networks to a vRouter after you bind a flat external network to the vRouter. Only one flat external network can be bound to a vRouter. · You cannot bind the vRouter to a segmented external network. The vRouter uses a firewall as the edge device to the external network and has been bound to a border device group that uses the hairpin or inline third-party firewall deployment mode. · The RT generated based on the segment ID of the vRouter conflicts with the import RT of a Layer 2 DC interconnect associated with the vRouter. · The RT generated based on the segment ID of the vRouter conflicts with the export RT of a Layer 2 DC interconnect associated with the vRouter. · The RT reserved for the vRouter link conflicts with the import RT of a Layer 2 DC interconnect associated with the local or remote vRouter. · The RT reserved for the vRouter link conflicts with the export RT of a Layer 2 DC interconnect associated with the local or remote vRouter. · The RT generated based on the segment ID of the vRouter conflicts with the import RT of the Layer 3 DC interconnect associated with the vRouter. · The RT generated based on the segment ID of the vRouter conflicts with the export RT of the Layer 3 DC interconnect associated with the vRouter. · The RT reserved for the vRouter link conflicts with the import RT of the Layer 3 DC interconnect associated with the local or remote vRouter. · The RT reserved for the vRouter link conflicts with the export RT of the Layer 3 DC interconnect associated with the local or remote vRouter. · Cannot bind the subnet to a vRouter if the subnet is used for primary IP allocation. · Subnets in the external network do not have sufficient IP addresses for allocation. · Failed to assign IP addresses to devices attached to the border gateway, because the IP addresses in the primary IP allocation are insufficient. · Cannot bind the subnet to a vRouter if the subnet is used for primary IP allocation. · Check the directly connected external networks and the border interfaces in the border device group bound to this vRouter with the same segment ID. Make sure only one primary IPv4 address exists for each border interface. · vRouters do not support vPorts in flat external networks. · The vRouter context or external network vPort context has been used in a service chain. · Please specify two and only two external subnets for the external context. This is required because the context uses primary/backup gateway deployment mode and the edge device to the external network in the vRouter for the context is the border device. · The external subnet has been bound to a context. Please access the context page to remove the binding first. · The context uses primary/backup gateway deployment mode. Make sure the associated vRouter is bound to two gateway members or external subnets. · The context uses single gateway deployment mode. Make sure the associated vRouter is bound to one gateway member or external subnet. · The vRouter-attached gateway members enable the third-party firewall option. Please enable or disable the firewall option across all IP addresses or subnets in the vRouter-attached external network if the egress of the external network is the firewall or border device, respectively. · The vRouter-attached gateway members disable the third-party firewall option and use hairpin firewall deployment. Please make sure the firewall is enabled or disabled across all IP addresses and subnets in the external network. · Failed to unbind the vRouter from the external network. The vRouter has been bound to a Layer 3 multicast network or a multicast source used for external services. · Not enough addresses in subnets in network segment. · Failed to unbind the vRouter from the subnet. The subnet has been bound to a Layer 3 multicast network or a multicast source used for external services. · Southbound devices at the following IP addresses were disconnected. · The segment ID cannot be identical to a VXLAN ID in a VXLAN pool or the VXLAN ID reserved for the automation template and the DR system. · Please specify a value for the ip_addr field. · Invalid ip_addr value. · Invalid source_ip value. · Invalid ip_version value. · The IP addresses specified for the ip_addr and source_ip fields must have the same IP version. · The ip_addr and ip_version fields do not match. · The peer IP address cannot be the same as the source IP address. · Please specify the device ID, device name, or both. · Please specify the device ID, device name, or both. · You cannot edit or delete the cloud region name. · You cannot edit the segment ID of the vRouter, because the vRouter has OVS vPorts.

Delete vRouter

Keyword	DELETE_ROUTE_OP
Message text	Deleted vRouter $1.
Variable fields	$1: vRouter information.
Example	Deleted vRouter { "id":"56a937a9-55ce-48c1-866b-0be6386f16ec", "admin_state_up":"vrouter", "external_gateway_info":"{ "network_id":"10236dae-b97a-49b7-89ed-c225baa39d4e", "enable_snat":"true", "external_fixed_ips":"[FixedIpDto { "ip address":"26.3.3.10", "subnet id":"e2d81808-6b61-4ef2-85c6-65839489172b", }]" }", "name":"vrouter", "routes":"[{ "destination":"23.3.3.3/32", "nexthop":"12.3.3.31" }]", "tenant_id":"2b2151a2-f111-40f0-a0ea-61a76879e972", "tenant_name":"admin", "gw_port_id":"null", "tags":"[]", "cloud_region_name":"openstack", "subnets":"null" }.
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. · Failed to delete the vRouter because the vRouter has BGP peers. · You have no privilege to perform this operation. · You cannot delete the vRouter, because it has been bound to a EPG. · Southbound devices at the following IP addresses were disconnected. · You cannot delete the vRouter, because it has been bound to an application policy.

Create QoS

Keyword	CREATE_QOS_POLICY_OP
Message text	Created QoS policy $1.
Variable fields	$1: QoS policy information.
Example	Created QoS policy { "id":"80a9c840-41be-416f-b70f-abd8ddb1adee", "name":"111", "description":"null", "rules":"[{ "max_kbps":"null", "max_burst_kbps":"null", "rule_type":"dscp_marking", "dscp_mark":"5", "direction":"null" }, { "max_kbps":"1", "max_burst_kbps":"16", "rule_type":"bandwidth_limit", "dscp_mark":"null", "direction":"INGRESS" }, { "max_kbps":"3", "max_burst_kbps":"32", "rule_type":"bandwidth_limit", "dscp_mark":"null", "direction":"EGRESS" }]", "cloud_region_name":"openstack" }.
Explanation	A QoS policy was created.
Possible failure causes	· The request is invalid. · 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. · Invalid rate value. · Network policies created in bulk cannot use the same UUID. · Unknown error. · You have no privilege to perform this operation.

Update QoS

Keyword	UPDATE_QOS_POLICY_OP
Message text	Updated QoS policy $1.
Variable fields	$1: QoS policy information.
Example	Updated QoS policy { "id":"80a9c840-41be-416f-b70f-abd8ddb1adee", "name":"111", "description":"null", "rules":"[{ "max_kbps":"null", "max_burst_kbps":"null", "rule_type":"dscp_marking", "dscp_mark":"5", "direction":"null" }, { "max_kbps":"1", "max_burst_kbps":"16", "rule_type":"bandwidth_limit", "dscp_mark":"null", "direction":"INGRESS" }, { "max_kbps":"3", "max_burst_kbps":"32", "rule_type":"bandwidth_limit", "dscp_mark":"null", "direction":"EGRESS" }]", "cloud_region_name":"openstack" }.
Explanation	A QoS policy was edited.
Possible failure causes	· The request is invalid. · 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. · Invalid rate value. · Unknown error. · You have no privilege to perform this operation. · Southbound devices at the following IP addresses were disconnected: {IP addresses}. · You cannot edit or delete the cloud region name.

Delete QoS

Keyword	DELETE_QOS_POLICY_OP
Message text	Deleted QoS policy $1.
Variable fields	$1: QoS policy information.
Example	Deleted QoS policy { "id":"80a9c840-41be-416f-b70f-abd8ddb1adee", "name":"111", "description":"null", "rules":"[{ "max_kbps":"null", "max_burst_kbps":"null", "rule_type":"dscp_marking", "dscp_mark":"5", "direction":"null" }, { "max_kbps":"1", "max_burst_kbps":"16", "rule_type":"bandwidth_limit", "dscp_mark":"null", "direction":"INGRESS" }, { "max_kbps":"3", "max_burst_kbps":"32", "rule_type":"bandwidth_limit", "dscp_mark":"null", "direction":"EGRESS" }]", "cloud_region_name":"openstack" }.
Explanation	A QoS policy was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · The Qos policy has been bound to a port. · The Qos policy has been bound to a port group. · The Qos policy has been bound to a virtual network. · The QoS policy has been bound to floating Ips. · The specified resource doesn't exist. · Unknown error. · You have no privilege to perform this operation.

Create floating IP

Keyword	CREATE_FLOATING_IP_OP
Message text	Created floating IP $1.
Variable fields	$1: Floating IP information.
Example	Created floating IP { "id":"74d2775e-3065-4fb0-bf88-6629ef0abcea", "tenant_id":"2b2151a2-f111-40f0-a0ea-61a76879e972", "qos_policy_id":"null", "floating_network_id":"0184331f-e0b4-431a-9a8c-dcf7245cbaf6", "router_id":"null", "floating_ip_address":"20.20.0.3", "port_id":"3f829afd-2581-4d34-bc22-55f69eee4c01", "extra":"{ "rx_averateLimit":"null", "tx_averateLimit":"null" }", "protocol":"null", "port_number":"null", "local_port_number":"null", "local_port_number":"null", "cloud_region_name":"openstack" }.
Explanation	A floating IP was created.
Possible failure causes	· The request is invalid. · 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. · Cannot set floating IPs for a directly connected external network. · When you create a floating IP, if you specify only the vPort or App cluster VIP and the vRouter of the floating IP is bound to one external network with network segmentation enabled or multiple external networks, you must specify an IP address for the floating IP. · You have no privilege to perform this operation. · You cannot select a subnet for primary IP allocation when creating a floating IP. · The external network does not have IPv4 vSubnets for allocating floating Ips.

Update floating IP

Keyword	UPDATE_FLOATING_IP_OP
Message text	Updated floating IP $1.
Variable fields	$1: Floating IP information.
Example	Updated floating IP { "id":"74d2775e-3065-4fb0-bf88-6629ef0abcea", "tenant_id":"2b2151a2-f111-40f0-a0ea-61a76879e972", "qos_policy_id":"null", "floating_network_id":"0184331f-e0b4-431a-9a8c-dcf7245cbaf6", "router_id":"null", "floating_ip_address":"20.20.0.3", "port_id":"3f829afd-2581-4d34-bc22-55f69eee4c01", "extra":"{ "rx_averateLimit":"null", "tx_averateLimit":"null" }", "protocol":"null", "port_number":"null", "local_port_number":"null", "local_port_number":"null", "cloud_region_name":"openstack" }.
Explanation	A floating IP was edited.
Possible failure causes	· The request is invalid. · 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. · The subnet to which the floating IP belongs has been bound to a network segment, and no subnet bound to the network segment has been bound to a vRouter. · Unknown error. · Cannot set floating IPs for a directly connected external network. · You have no privilege to perform this operation. · You cannot edit or delete the cloud region name.

Delete floating IP

Keyword	DELETE_FLOATING_IP_OP
Message text	Deleted floating IP $1.
Variable fields	$1: Floating IP information.
Example	Deleted floating IP { "id":"74d2775e-3065-4fb0-bf88-6629ef0abcea", "tenant_id":"2b2151a2-f111-40f0-a0ea-61a76879e972", "qos_policy_id":"null", "floating_network_id":"0184331f-e0b4-431a-9a8c-dcf7245cbaf6", "router_id":"null", "floating_ip_address":"20.20.0.3", "port_id":"3f829afd-2581-4d34-bc22-55f69eee4c01", "extra":"{ "rx_averateLimit":"null", "tx_averateLimit":"null" }", "protocol":"null", "port_number":"null", "local_port_number":"null", "local_port_number":"null", "cloud_region_name":"openstack" }.
Explanation	A floating IP 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. · You have no privilege to perform this operation.

Create vPort

Keyword	CREATE_PORT_OP
Message text	Created vPort $1.
Variable fields	$1: vPort information.
Example	Created vPort { "id":"46d4bfb9-b26e-41f3-bd2e-e6dcc1ccedb2", "name":"", "description":"", "mac address":"fa:16:3e:23:fd:d7", "device id":"5e3898d7-11be-483e-9732-b2f5eccd2b2e", "device owner":"compute:nova", "network id":"6a21c566-692a-4214-a3a1-79eb654ba9ab", "tenant id":"4fd44f30-2929-45e4-81c7-b8a0c8908869", "allowed address pairs":"[AllowedAddressPairDTO { "ipAddress":"4.4.4.3", "macAddress":"fa:14:2a:b3:cb:f0", }]", "extra dhcp opts":"[ExtraDhcpOptDTO { "opt value":"pxelinux.0", "ip version":"4", "opt name":"bootfile-name", }]", "fixed ips":"[FixedIpDto { "ip address":"4.4.4.5", "subnet id":"8941dfed-517f-42e6-a56a-576e82efb740", }]", "port security enabled":"true", "security groups":"[5d6465f7-de67-4a53-9d41-4ba857ba029b]", "qos policy id":"null", "binding profile":"BindingProfileDTO { "enable_snat": “true”, "fw_enabled": "false", "migrating_to": “null”, "cvk host":"123", "esxi host":"234", "local link information":"[LocalLinkInfoDTO { "switch id":"111111", "port id"...
Explanation	A vPort was created.
Possible failure causes	· The request is invalid. · 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. · You cannot delete the gateway vPort. · 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. · vPorts do not support directly connected external networks. · The value of the port_security_enabled is invalid. · A port group cannot be bound to a security policy when it contains port security disabled vPorts. · A vPort with port security disabled cannot be bound to a security policy. · A vPort with port security disabled cannot be configured with allowed address pairs. · You have no privilege to perform this operation. · The MAC address cannot contain all zeros or all Fs. · Do not specify the port_isolated field when you create a vPort. · A vPort name cannot start with "gateway". · Please enter an IP address for the external network vPort. · Do not specify the port_isolated field when you create a vPort. · You cannot bind a vPort to a subnet for primary IP allocation in an external network. · The external subnet where the specified IP address resides has been bound to an NQA profile. You cannot assign the IP address to a vPort. · Failed to connect to (hosts or access devices). Host or access device Ips. · The latest links are invalid or no links exist on the netoverlay hosts found by names of (hosts or access devices). · No device exists at either end or both ends of the latest links on the netoverlay hosts found by names of (hosts or access devices). · No device exists at either end or both ends of the links found by names of (hosts or access devices). · The interfaces of some links found by names of (hosts or access devices) are not AC interfaces. · The destination host name for the migrating_to parameter cannot exceed 255 characters.

Update vPort

Keyword	UPDATE_PORT_OP
Message text	Updated vPort $1.
Variable fields	$1: vPort information.
Example	Updated vPort { "id":"46d4bfb9-b26e-41f3-bd2e-e6dcc1ccedb2", "name":"", "description":"", "mac address":"fa:16:3e:23:fd:d7", "device id":"5e3898d7-11be-483e-9732-b2f5eccd2b2e", "device owner":"compute:nova", "network id":"6a21c566-692a-4214-a3a1-79eb654ba9ab", "tenant id":"4fd44f30-2929-45e4-81c7-b8a0c8908869", "allowed address pairs":"[AllowedAddressPairDTO { "ipAddress":"4.4.4.3", "macAddress":"fa:14:2a:b3:cb:f0", }]", "extra dhcp opts":"[ExtraDhcpOptDTO { "opt value":"pxelinux.0", "ip version":"4", "opt name":"bootfile-name", }]", "fixed ips":"[FixedIpDto { "ip address":"4.4.4.5", "subnet id":"8941dfed-517f-42e6-a56a-576e82efb740", }]", "port security enabled":"true", "security groups":"[5d6465f7-de67-4a53-9d41-4ba857ba029b]", "qos policy id":"null", "binding profile":"BindingProfileDTO { "enable_snat": “true”, "fw_enabled": "false", "migrating_to": “null”, "cvk host":"123", "esxi host":"234", "local link information":"[LocalLinkInfoDTO { "switch id":"111111", "port id"...
Explanation	A vPort was edited.
Possible failure causes	· The request is invalid. · 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. · 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. · vPorts do not support directly connected external networks. · The value of the port_security_enabled is invalid. · A port group cannot be bound to a security policy when it contains port security disabled vPorts. · A vPort with port security disabled cannot be bound to a security policy. · A vPort with port security disabled cannot be configured with allowed address pairs. · You have no privilege to perform this operation. · The MAC address cannot contain all zeros or all Fs. · A vPort name cannot start with "gateway". · Please enter an IP address for the external network vPort. · Only OVS vPorts can be blocked. · You cannot bind a vPort to a subnet for primary IP allocation in an external network. · The external subnet where the specified IP address resides has been bound to an NQA profile. You cannot assign the IP address to a vPort. · Failed to edit the IP address for the vPort, because the new IP address is in a network bound to the context in another service chain. · The value for the fw_enabled parameter is invalid. · The vRouter-attached gateway members enable the third-party firewall option. Please enable or disable the firewall option across all IP addresses or subnets in the vRouter-attached external network if the egress of the external network is the firewall or border device, respectively. · The vRouter-attached gateway members disable the third-party firewall option and use hairpin firewall deployment. Please make sure the firewall is enabled or disabled across all IP addresses and subnets in the external network. · Failed to connect to (hosts or access devices). Host or access device Ips. · The latest links are invalid or no links exist on the netoverlay hosts found by names of (hosts or access devices). · No device exists at either end or both ends of the latest links on the netoverlay hosts found by names of (hosts or access devices). · No device exists at either end or both ends of the links found by names of (hosts or access devices). · The interfaces of some links found by names of (hosts or access devices) are not AC interfaces. · The destination host name for the migrating_to parameter cannot exceed 255 characters. · You cannot edit or delete the cloud region name.

Delete vPort

Keyword	DELETE_PORT_OP
Message text	Deleted vPort $1.
Variable fields	$1: vPort information.
Example	Deleted vPort { "id":"46d4bfb9-b26e-41f3-bd2e-e6dcc1ccedb2", "name":"", "description":"", "mac address":"fa:16:3e:23:fd:d7", "device id":"5e3898d7-11be-483e-9732-b2f5eccd2b2e", "device owner":"compute:nova", "network id":"6a21c566-692a-4214-a3a1-79eb654ba9ab", "tenant id":"4fd44f30-2929-45e4-81c7-b8a0c8908869", "allowed address pairs":"[AllowedAddressPairDTO { "ipAddress":"4.4.4.3", "macAddress":"fa:14:2a:b3:cb:f0", }]", "extra dhcp opts":"[ExtraDhcpOptDTO { "opt value":"pxelinux.0", "ip version":"4", "opt name":"bootfile-name", }]", "fixed ips":"[FixedIpDto { "ip address":"4.4.4.5", "subnet id":"8941dfed-517f-42e6-a56a-576e82efb740", }]", "port security enabled":"true", "security groups":"[5d6465f7-de67-4a53-9d41-4ba857ba029b]", "qos policy id":"null", "binding profile":"BindingProfileDTO { "enable_snat": “true”, "fw_enabled": "false", "migrating_to": “null”, "cvk host":"123", "esxi host":"234", "local link information":"[LocalLinkInfoDTO { "switch id":"111111", "port id"...
Explanation	A vPort was deleted.
Possible failure causes	· The request is invalid. · 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. · You cannot delete the gateway vPort. · Unknown error. · You have no privilege to perform this operation. · Failed to connect to (hosts or access devices). Host or access device Ips. · The latest links are invalid or no links exist on the netoverlay hosts found by names of (hosts or access devices). · No device exists at either end or both ends of the latest links on the netoverlay hosts found by names of (hosts or access devices). · No device exists at either end or both ends of the links found by names of (hosts or access devices). · The interfaces of some links found by names of (hosts or access devices) are not AC interfaces. · The destination host name for the migrating_to parameter cannot exceed 255 characters.

Create network

Keyword	CREATE_NETWORK_OP
Message text	Created network $1.
Variable fields	$1: vNetwork information.
Example	Created network { "id":"null", "name":"waiwang", "tenant id":"4fd44f30-2929-45e4-81c7-b8a0c8908869", "tenant name":"zuhu", "admin state up":"true", "domain":"null", "mtu":"1500", "qos policy id":"c4cdbf7e-52b2-4be5-9416-e97f7b95f21b", "router external":"false", "shared":"false", "status":"ACTIVE", "subnets":"[]", "network type":"vlan", "original network type":"null", "physical network":"public", "segmentation id":"3", "segment uuid":"null", "segments":"null", "cloud region name":"openstack", "description":"null", "vswitch flood and learn":"null", "dhcp ctrl":"null", "dhcpv6 ctrl":"null", }.
Explanation	A vNetwork was created.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid tenant ID. · The segment ID number 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 tenant. · 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. · The provider field and the segment field cannot be both configured. · The flat type external network cannot be configured with segment. · The ID already exists. · The value of the network type can only be VLAN. · The network type is required. · The segment ID is not in the VLAN pool. · physical network is required. · The specified composite gateway doesn't exist. · You can create segments only for external networks. · The segment name cannot exceed 255 characters. · The description cannot exceed 255 characters. · Invalid segmentUUID. · The external network has been bound to a vRouter. · Invalid segment ID. · The value of the MTU must be an integer in the range of 68 to 65535. · The specified QoS policy doesn't exist. · Unknown error. · Invalid value in the physical_network field. · A vNetwork cannot use directly connected mode. · When the Network Cloud feature is disabled, directly connected external networks are not supported. · Only internal network can be configured as resource operating mode. · You have no privilege to perform this operation. · Cannot bind the DHCP host group to an external network. · The DHCP host group does not exist. · The RT generated based on the segment ID of the vNetwork conflicts with the import RT of the Layer 2 DC interconnect associated with the vNetwork. · The RT generated based on the segment ID of the vNetwork conflicts with the export RT of the Layer 2 DC interconnect associated with the vNetwork. · The RT reserved for a fabric connection on the vNetwork conflicts with the import RT of the Layer 2 DC interconnect associated with the vNetwork. · The RT reserved for a fabric connection on the vNetwork conflicts with the export RT of the Layer 2 DC interconnect associated with the vNetwork. · The RT generated based on the segment ID of the vNetwork conflicts with the import RT of the Layer 3 DC interconnect associated with the vNetwork. · The RT generated based on the segment ID of the vNetwork conflicts with the export RT of the Layer 3 DC interconnect associated with the vNetwork. · The RT reserved for a fabric connection on the vNetwork conflicts with the import RT of the Layer 3 DC interconnect associated with the vNetwork. · The RT reserved for a fabric connection on the vNetwork conflicts with the export RT of the Layer 3 DC interconnect associated with the vNetwork. · Invalid auto port creation configuration. · You cannot bind the DHCP host group to the vNetwork. A network node in the DHCP host group has already created a DHCP vPort for the vNetwork. · To disable preprovisioning, make sure all its dependent features use their default settings. For information about these features, see online help. · Make sure the segment ID (VLAN ID) is not in a tenant carrier network VLAN pool and vRouter interconnection network VLAN pool when the external network or vNetwork type is VLAN. · You cannot change the status of the multicast network feature when the network segmentation feature is enabled. · The external segment ID is already in use. · The external segment ID is out of range. · Southbound devices at the following IP addresses were disconnected. · You can enable external route redistribution only for external networks. · You can enable external route redistribution only when the L3VNI is specified. · The segment ID cannot be identical to a VXLAN ID in a VXLAN pool or the VXLAN ID reserved for the automation template and the DR system. · VLAN ID of VLAN type network is not allowed to conflict with DRNI Routed IPLs border device VLAN ID. · You must specify a valid VXLAN pool type when automatic allocation of L3VNIs for external networks is enabled. · vxlanPoolType cannot be vxlanPoolForL3vni or vdsPoolForL3vni when automatic allocation is not enabled. · Automatic allocation cannot be enabled when l3vni is exist.

Update network

Keyword	UPDATE_NETWORK_OP
Message text	Updated network $1.
Variable fields	$1: vNetwork information.
Example	Updated network { "id":"null", "name":"waiwang", "tenant id":"4fd44f30-2929-45e4-81c7-b8a0c8908869", "tenant name":"zuhu", "admin state up":"true", "domain":"null", "mtu":"1500", "qos policy id":"c4cdbf7e-52b2-4be5-9416-e97f7b95f21b", "router external":"false", "shared":"false", "status":"ACTIVE", "subnets":"[]", "network type":"vlan", "original network type":"null", "physical network":"public", "segmentation id":"3", "segment uuid":"null", "segments":"null", "cloud region name":"openstack", "description":"null", "vswitch flood and learn":"null", "dhcp ctrl":"null", "dhcpv6 ctrl":"null", }.
Explanation	A vNetwork was edited.
Possible failure causes	· The request is invalid. · 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. · Cannot segment the external network because it has been bound to a vRouter that is bound to a gateway resource configured with a priority. · The value of the MTU must be an integer in the range of 68 to 65535. · The specified QoS policy doesn't exist. · Invalid value in the physical_network field. · A vNetwork cannot use directly connected mode. · When the Network Cloud feature is disabled, directly connected external networks are not supported. · You have no privilege to perform this operation. · Cannot enable multicast network capabilities for the vNetwork because the vNetwork has been bound to a Layer 2 DC interconnect. · Cannot bind the DHCP host group to an external network. · The DHCP host group does not exist. · Invalid auto port creation configuration. · You cannot bind the DHCP host group to the vNetwork. A network node in the DHCP host group has already created a DHCP vPort for the vNetwork. · The vNetwork is an interface-specific multicast network. You cannot disable its multicast capabilities. · To disable preprovisioning, make sure all its dependent features use their default settings. For information about these features, see online help. · You cannot change the status of the multicast network feature when the network segmentation feature is enabled. · The external segment ID is already in use. · The external segment ID is out of range. · Southbound devices at the following IP addresses were disconnected. · You can enable external route redistribution only for external networks. · You can enable external route redistribution only when the L3VNI is specified. · You cannot edit or delete the cloud region name. · The external network has been bound to a vRouter through a vPort, and the multicast network feature cannot be enabled for the external network. · You must specify a valid VXLAN pool type when automatic allocation of L3VNIs for external networks is enabled. · vxlanPoolType cannot be vxlanPoolForL3vni or vdsPoolForL3vni when automatic allocation is not enabled. · Automatic allocation cannot be enabled when l3vni is exist. · You cannot enable automatic segment ID allocation when the external network contains segments. · You cannot set the VXLAN pool type to VXLAN or VDS when the external network contains segments.

Delete network

Keyword	DELETE_NETWORK_OP
Message text	Deleted network $1.
Variable fields	$1: vNetwork information.
Example	Deleted network { "id":"null", "name":"waiwang", "tenant id":"4fd44f30-2929-45e4-81c7-b8a0c8908869", "tenant name":"zuhu", "admin state up":"true", "domain":"null", "mtu":"1500", "qos policy id":"c4cdbf7e-52b2-4be5-9416-e97f7b95f21b", "router external":"false", "shared":"false", "status":"ACTIVE", "subnets":"[]", "network type":"vlan", "original network type":"null", "physical network":"public", "segmentation id":"3", "segment uuid":"null", "segments":"null", "cloud region name":"openstack", "description":"null", "vswitch flood and learn":"null", "dhcp ctrl":"null", "dhcpv6 ctrl":"null", }.
Explanation	A vNetwork was deleted.
Possible failure causes	· The request is invalid. · 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. · You have no privilege to perform this operation. · Southbound devices at the following IP addresses were disconnected. · Cannot delete the vNetwork because it has been bound to an OSPF or OSPFv3 policy.

Create mirroring destination profile

Keyword	CREATE_MIRROR_DESTINATION_PROFILE_OP
Message text	Created mirroring destination profile: $1.
Variable fields	$1: Mirroring destination profile information.
Example	Created tap mirroring destination profile { "id":"c352f537-ad49-48eb-ab05-1c6b8cb900ff", "name":"tap1", "tenant_id":"6883573e-ba4e-4fd5-8df5-f59b6c365b5b", "description":"", "port_id":"c9beb5a1-21f5-4225-9eaf-02ddccdd50a9", "remote_v4ip":"192.122.222.8" }.
Explanation	A mirroring destination profile was created.
Possible failure causes	· The service does not exist. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The name is required and cannot exceed 255 characters. · Failed to add the configuration item. · You have no privilege to perform this operation.

Update mirroring destination profile

Keyword	UPDATE_MIRROR_DESTINATION_PROFILE_OP
Message text	Updated mirroring destination profile: $1.
Variable fields	$1: Mirroring destination profile information.
Example	Updated mirroring destination profile { "id":"c352f537-ad49-48eb-ab05-1c6b8cb900ff", "name":"tap1", "tenant_id":"6883573e-ba4e-4fd5-8df5-f59b6c365b5b", "description":"", "port_id":"c9beb5a1-21f5-4225-9eaf-02ddccdd50a9", "remote_v4ip":"192.122.222.8" }.
Explanation	A mirroring destination profile was edited.
Possible failure causes	· The service does not exist. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The configuration item does not exist. · The name is required and cannot exceed 255 characters. · Failed to modify the configuration item. · You have no privilege to perform this operation.

Delete mirroring destination profile

Keyword	DELETE_MIRROR_DESTINATION_PROFILE_OP
Message text	Deleted mirroring destination profile $1.
Variable fields	$1: Mirroring destination profile information.
Example	Deleted mirroring destination profile { "id":"c352f537-ad49-48eb-ab05-1c6b8cb900ff", "name":"tap1", "tenant_id":"6883573e-ba4e-4fd5-8df5-f59b6c365b5b", "description":"", "port_id":"c9beb5a1-21f5-4225-9eaf-02ddccdd50a9", "remote_v4ip":"192.122.222.8" }.
Explanation	A mirroring destination profile was deleted.
Possible failure causes	· The service does not exist. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The configuration item does not exist. · The specified mirroring destination profile is used. · You have no privilege to perform this operation.

Create mirroring profile

Keyword	CREATE_MIRRORING_PROFILE_OP
Message text	Created mirroring profile $1.
Variable fields	$1: Mirroring profile information.
Example	Created mirroring profile { "id":"cc47f881-345f-4e62-ad24-bea79eb28304", "name":"flow1", "tenant_id":"2b2151a2-f111-40f0-a0ea-61a76879e972", "description":"", "source_port":"d396a0e8-d89a-40d7-9f86-b7cb8ee96905", "destination_v4ip_prefix":"1.2.5.0/24", "tap_service_id":"1a97a957-b4f4-431e-94f3-38a25c82b158", "direction":"OUT" }.
Explanation	A mirroring profile was created.
Possible failure causes	· The service does not exist. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The default VXLAN is required. · The name is required and cannot exceed 255 characters. · The description cannot exceed 255 characters. · The vPort is required. · The vPort cannot be the same as the vPort in the mirroring destination profile. · Failed to add the configuration item. · No available VXLAN IDs. · The specified mirroring destination profile does not exist. · No VXLAN resources are configured, or VXLAN resources have been used up. · Southbound devices at the following IP addresses were disconnected.

Update mirroring profile

Keyword	UPDATE_MIRRORING_PROFILE_OP
Message text	Updated mirroring profile $1.
Variable fields	$1: Mirroring profile information.
Example	Updated mirroring profile { "id":"cc47f881-345f-4e62-ad24-bea79eb28304", "name":"flow1", "tenant_id":"2b2151a2-f111-40f0-a0ea-61a76879e972", "description":"", "source_port":"d396a0e8-d89a-40d7-9f86-b7cb8ee96905", "destination_v4ip_prefix":"1.2.5.0/24", "tap_service_id":"1a97a957-b4f4-431e-94f3-38a25c82b158", "direction":"OUT" }.
Explanation	A mirroring profile was edited.
Possible failure causes	· The service does not exist. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The configuration item does not exist. · The default VXLAN is required. · The name is required and cannot exceed 255 characters. · The description cannot exceed 255 characters. · The vPort cannot be edited. · The VXLAN ID cannot be modified. · The vPort cannot be the same as the vPort in the mirroring destination profile. · Failed to modify the configuration item.

Delete mirroring profile

Keyword	DELETE_MIRRORING_PROFILE_OP
Message text	Deleted mirroring profile $1.
Variable fields	$1: Mirroring profile information.
Example	Deleted mirroring profile { "id":"cc47f881-345f-4e62-ad24-bea79eb28304", "name":"flow1", "tenant_id":"2b2151a2-f111-40f0-a0ea-61a76879e972", "description":"", "source_port":"d396a0e8-d89a-40d7-9f86-b7cb8ee96905", "destination_v4ip_prefix":"1.2.5.0/24", "tap_service_id":"1a97a957-b4f4-431e-94f3-38a25c82b158", "direction":"OUT" }.
Explanation	A mirroring profile was deleted.
Possible failure causes	· The service does not exist. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The configuration item does not exist. · Southbound devices at the following IP addresses were disconnected.

Create BGP neighbor

Keyword	CREATE_BGP_NEIGHBOR_OP
Message text	Created BGP neighbor $1.
Variable fields	$1: BGP neighbor information.
Example	Created BGP neighbor { "bgpneighbor_id":"b3848485-eff1-427f-a012-f1fff28c65c8", "name":"bgpn_example", "description":"", "tenant_id":"6883573e-ba4e-4fd5-8df5-f59b6c365b5b", "router_id":"2f5d01a1-1cef-4067-9280-f6dcf086b43c", "exsubnet_id":"null", "local_as_number":"1", "ip_version":"4", "peer_ip_address":"1.1.1.1", "peer_as_number":"2", "suppress":"true", "source_ips":"[2.2.2.2]" }.
Explanation	A BGP neighbor 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 parameter. · Unknown internal server error. · A name is required for the BGP instance. · A tenant ID is required. · A router ID is required for the BGP instance. · Specify either a source IP address or an external subnet ID. · A local AS number is required. · Invalid local AS number. · Invalid IP version. · The IP address of the BGP peer must be the same version as the source IP address. · An AS number is required for the BGP peer. · The AS number of the BGP peer is invalid. · The BGP peer UUID already exists. · An IP address is required for the BGP peer. · The source IP address or external subnet ID is invalid. · A name is required. · A UUID is required for the BGP peer. · An external subnet ID is required. · An IP version is required. · The IP address of the BGP peer is invalid. · An IP address is required for the BGP peer. · An AS number is required for the BGP peer. · The specified BGP peer has already been bound to the vRouter. · The specified subnet is not an external subnet. · The connection type of the external network must be Directly Connected. · The external subnet type must be VLAN. · The specified external subnet has not been bound to a vRouter. · The vRouter to which the external subnet is bound is different from the vRouter specified by the router_id parameter. · When the HA mode is multi-active, you must specify two different source IP addresses for the BGP neighbor. · You have no privilege to perform this operation. · When the Network Cloud feature is disabled, you cannot create BGP peers. · BGP peer with the specified IP address already exists. · Southbound devices at the following IP addresses were disconnected. · Up to 255 characters, case sensitive.

Update BGP neighbor

Keyword	UPDATE_BGP_NEIGHBOR_OP
Message text	Updated BGP neighbor $1.
Variable fields	$1: BGP neighbor information.
Example	Updated BGP neighbor { "bgpneighbor_id":"b3848485-eff1-427f-a012-f1fff28c65c8", "name":"bgpn_example", "description":"", "tenant_id":"6883573e-ba4e-4fd5-8df5-f59b6c365b5b", "router_id":"2f5d01a1-1cef-4067-9280-f6dcf086b43c", "exsubnet_id":"null", "local_as_number":"1", "ip_version":"4", "peer_ip_address":"1.1.1.1", "peer_as_number":"2", "suppress":"true", "source_ips":"[2.2.2.2]" }.
Explanation	A BGP neighbor was edited.
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 parameter. · Unknown internal server error. · The BGP peer UUID does not exist. · The BGP peer UUID cannot be modified. · The tenant ID cannot be modified. · The router ID of the BGP instance cannot be modified. · The local AS number cannot be modified. · The IP version cannot be modified. · The IP address of the BGP peer cannot be modified. · The AS number of the BGP peer cannot be modified. · You have no privilege to perform this operation. · When the Network Cloud feature is disabled, you cannot edit BGP peers. · Southbound devices at the following IP addresses were disconnected. · You cannot edit or delete the cloud region name. · Up to 255 characters, case sensitive.

Delete BGP neighbor

Keyword	DELETE_BGP_NEIGHBOR_OP
Message text	Deleted BGP neighbor $1.
Variable fields	$1: BGP neighbor information.
Example	Deleted BGP neighbor { "bgpneighbor_id":"b3848485-eff1-427f-a012-f1fff28c65c8", "name":"bgpn_example", "description":"", "tenant_id":"6883573e-ba4e-4fd5-8df5-f59b6c365b5b", "router_id":"2f5d01a1-1cef-4067-9280-f6dcf086b43c", "exsubnet_id":"null", "local_as_number":"1", "ip_version":"4", "peer_ip_address":"1.1.1.1", "peer_as_number":"2", "suppress":"true", "source_ips":"[2.2.2.2]" }.
Explanation	A BGP neighbor 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. · Invalid parameter. · Unknown internal server error. · The BGP peer UUID does not exist. · You have no privilege to perform this operation. · Southbound devices at the following IP addresses were disconnected.

Create route entry

Keyword	CREATE_ROUTE_ENTITY_OP
Message text	Created route entities $1
Variable fields	$1: Route entry information.
Example	Created route entities { "id":"null", "destination":"10.10.0.0/16", "nexthop":"12.3.3.3", "type":"401", "ip_version":"4", "source_ips":"[1.0.0.2]", "bfd":"true", "routetable_id":"b930d7f6-ceb7-40a0-8b81-a425dd994ccf", "cloud_region_name":"openstack" },{ "id":"null", "destination":"11.11.0.0/16", "nexthop":"13.3.3.3", "type":"401", "ip_version":"4", "source_ips":"[1.0.0.2]", "bfd":"true", "routetable_id":"b930d7f6-ceb7-40a0-8b81-a425dd994ccf", "cloud_region_name":"openstack" }.
Explanation	Route entries were 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. · The route entries cannot be created on edge devices. · Can't specify a vRouter whose origin is PBR. · The first BFD source IP address in a route entry cannot be the same as the second BFD source IP address in another route entry, and vice versa. · The first BFD source IP address in a route entry cannot be the same as the second source IP address of a BGP peer bound to the same vRouter as the route entry, and vice versa. · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot overlap with any vNetwork subnet on another vRouter. · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot overlap with any external subnet on another vRouter. · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot be the same as any vNetwork subnet gateway IP of another vRouter. · The source IP address of a route entry on the vRouter cannot be the same as any vNetwork subnet gateway IP on the vRouter. · The source IP address of a route entry on the vRouter cannot be within any vNetwork subnet on the vRouter. · The source IP address of a route entry on the vRouter cannot be within any external subnet on the vRouter. · The next hop type cannot be blackhole when the value of the type field is 401 or 402. · When network cloud is enabled, the value for the type field cannot be 0. · The value of the type field is invalid. · The IP version of the IP address is invalid. · The two source IP address must be different. · Invalid source IP address. · When the value of the type field is 401 and BFD enabled, a source IP is required. · A maximum of two source IP addresses are supported. · When the Network Cloud feature is disabled, routes with vPort or non-vPort as the next hop type are not supported. · The next hop type and next hop IP address do not match. · The destination subnet and the next hop type do not match. · When the next hop type is IPv6, host route recursion is not supported. · Route entries that are enabled with BFD and use vPort next hops must have the same source IP address if they have the same next hop IP address. · A route entry with the same settings already exists. Route entries that are enabled with BFD and use vPort next hops cannot have the same next hop IP address. · Cannot enable BFD for route entries that use non-vPort next hops. · Route entries that use vPort or non-vPort next hops cannot be edited. · When BFD is disabled, a source IP address is not required. · The source IP address cannot be the same as the IP address of any gateway bound to the vRouter. · The source IP address cannot belong to any subnet bound to the vRouter. · The source IP address cannot belong to any external subnet bound to the vRouter. · Do not specify the next hop vRouter when the next hop type is ExtIPv4 or ExtIPv6. · The next hop in the route entry is a vPort and BFD is enabled for the route entry. You cannot set its IP address to be the gateway IP address of a vNetwork bound to the same vRouter as the routing table. · Cannot apply the route entry to devices when the next hop type of the route entry is ExtIPv4 or ExtIPv6. · You have no privilege to perform this operation. · The source IP address cannot be within the destination subnet. · The source IP address conflicts with the next hop IP address. · Southbound devices at the following IP addresses were disconnected.

Delete extended route entry

Keyword	DELETE_ROUTE_ENTITY_OP
Message text	Deleted extended route entities $1
Variable fields	$1: Route entry information.
Example	Deleted extended route entities { "id":"null", "destination":"10.10.0.0/16", "nexthop":"12.3.3.3", "type":"401", "ip_version":"4", "source_ips":"[1.0.0.2]", "bfd":"true", "routetable_id":"b930d7f6-ceb7-40a0-8b81-a425dd994ccf", "cloud_region_name":"openstack" },{ "id":"null", "destination":"11.11.0.0/16", "nexthop":"13.3.3.3", "type":"401", "ip_version":"4", "source_ips":"[1.0.0.2]", "bfd":"true", "routetable_id":"b930d7f6-ceb7-40a0-8b81-a425dd994ccf", "cloud_region_name":"openstack" }.
Explanation	Route entries were 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. · The specified device doesn't exist. · The device ID and the device name do not match. · Duplicate devices exist. · Unknown error. · The route entries cannot be created on edge devices. · The value of the type field is invalid. · When the Network Cloud feature is disabled, routes with vPort or non-vPort as the next hop type are not supported. · When the next hop type is IPv6, host route recursion is not supported. · Cannot apply the route entry to devices when the next hop type of the route entry is ExtIPv4 or ExtIPv6. · You have no privilege to perform this operation. · Southbound devices at the following IP addresses were disconnected. · You cannot edit or delete the cloud region name.

Delete route entry

Keyword	DELETE_ROUTE_ENTITY_OP
Message text	Deleted route entry $1.
Variable fields	$1: Route entry information.
Example	Deleted route entry { "id":"e13b19a2-e8a7-4d04-afe3-c71ffeb467f9", "destination":"10.10.0.0/16", "nexthop":"12.3.3.3", "type":"401", "ip_version":"4", "source_ips":"[1.0.0.2]", "bfd":"true", "routetable_id":"6e439816-a1a1-4985-beba-2604f04e68e3", "cloud_region_name":"openstack" }.
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. · You have no privilege to perform this operation. · Southbound devices at the following IP addresses were disconnected.

Create segment

Keyword	CREATE_SEGMENT_OP
Message text	Created segment $1.
Variable fields	$1: Network segment information.
Example	Created segment { "id":"57fe85e4-ca2f-4192-b3cd-d5c249d7a21f", "name":"se01", "network_id":"5c0cb560-4089-41dd-be29-469907a23b49", "segmentation_id":"2000", "network_type":"vlan", "physical_network":"segment-1", "description":"11111", "cloud_region_name":"openstack", }.
Explanation	A network segment was added.
Possible failure causes	· The request is invalid. · The operation requires the administrator privilege. · The ID already exists. · The segment ID number already exists. · The value of the network type can only be VLAN. · The network type is required. · The network ID is required. · The segment ID is not in the VLAN pool. · The segment has been bound to subnets. · physical network is required. · The specified composite gateway doesn't exist. · The network doesn't exist. · Invalid segmentUUID. · You can create segments only for external networks. · The segment name cannot exceed 255 characters. · The description cannot exceed 255 characters. · When you create the first segment for the external network, the segment type must be the same as the type of the external network. · When you create the first segment for the external network, the ID of the segment must be the same as the segment ID of the external network. · Operation failed. To enable network segmentation for the external network, make sure all vRouters bound to the external network use the same border gateway or none of them uses a border gateway. · The external network is bound to a vRouter that is configured with a gateway, and you must specify this gateway for the segment. · Invalid segment ID. · Cannot segment the external network because it has been bound to a vRouter that is bound to a gateway resource configured with a priority. · You have no privilege to perform this operation. · You cannot change the status of the network segmentation feature when the multicast network feature is enabled. · You cannot change the network segmentation state for the external network, because it has been bound to a Layer 3 multicast network. · The external segment ID is already in use. · The external segment ID is out of range. · The RT reserved for a fabric connection on the vNetwork conflicts with the import RT of a Layer 2 DC interconnect. · The RT reserved for a fabric connection on the vNetwork conflicts with the export RT of a Layer 2 DC interconnect. · The RT reserved for a fabric connection on the vNetwork conflicts with the import RT of a Layer 3 DC interconnect. · The RT reserved for a fabric connection on the vNetwork conflicts with the export RT of a Layer 3 DC interconnect. · You cannot bind the external network segment to a border gateway that uses a border device group only for DC Interconnection. · You are creating the first segment for the external network.Please configure the segment with the same VXLAN pool type as the external network. · You cannot enable automatic segment ID allocation when you are creating the first segment for the external network. · You must specify a valid VXLAN pool type when automatic allocation of L3VNIs for external networks is enabled. · vxlanPoolType cannot be vxlanPoolForL3vni or vdsPoolForL3vni when automatic allocation is not enabled. · Automatic allocation cannot be enabled when l3vni is exist.

Update segment

Keyword	UPDATE_SEGMENT_OP
Message text	Updated segment $1.
Variable fields	$1: Network segment information.
Example	Updated segment { "id":"57fe85e4-ca2f-4192-b3cd-d5c249d7a21f", "name":"se01", "network_id":"5c0cb560-4089-41dd-be29-469907a23b49", "segmentation_id":"2000", "network_type":"vlan", "physical_network":"segment-1", "description":"11111", "cloud_region_name":"openstack", }.
Explanation	A network segment was edited.
Possible failure causes	· The request is invalid. · The operation requires the administrator privilege. · The specified resource doesn't exist. · The segment name cannot exceed 255 characters. · The description cannot exceed 255 characters. · You have no privilege to perform this operation. · The external segment ID is already in use. · The external segment ID is out of range. · The RT reserved for a fabric connection on the vNetwork conflicts with the import RT of a Layer 2 DC interconnect. · The RT reserved for a fabric connection on the vNetwork conflicts with the export RT of a Layer 2 DC interconnect. · The RT reserved for a fabric connection on the vNetwork conflicts with the import RT of a Layer 3 DC interconnect. · The RT reserved for a fabric connection on the vNetwork conflicts with the export RT of a Layer 3 DC interconnect. · You cannot edit or delete the cloud region name. · You must specify a valid VXLAN pool type when automatic allocation of L3VNIs for external networks is enabled. · vxlanPoolType cannot be vxlanPoolForL3vni or vdsPoolForL3vni when automatic allocation is not enabled. · Automatic allocation cannot be enabled when l3vni is exist.

Delete segment

Keyword	DELETE_SEGMENT_OP
Message text	Deleted segment $1.
Variable fields	$1: Network segment information.
Example	Deleted segment { "id":"57fe85e4-ca2f-4192-b3cd-d5c249d7a21f", "name":"se01", "network_id":"5c0cb560-4089-41dd-be29-469907a23b49", "segmentation_id":"2000", "network_type":"vlan", "physical_network":"segment-1", "description":"11111", "cloud_region_name":"openstack", }.
Explanation	A network segment was deleted.
Possible failure causes	· The operation requires the administrator privilege. · The segment has been bound to subnets. · The specified resource doesn't exist. · You have no privilege to perform this operation.

Create trunk

Keyword	CREATE_TRUNK_OP
Message text	Created trunk $1.
Variable fields	$1: Trunk information.
Example	Created trunk { "sub_ports":"[{ "segmentation id":"44", "port id":"4b4c691b-086d-43d2-8a65-5487e9434155", "segmentation type":"vlan", }]", "name":"foo", "tenant_id":"145a14e4-a64b-49bf-98ba-ad8945dbd4f1", "port_id":"8027c4da-772f-4e43-bfbf-023b4a4e63de", "id"":"114a26b1-d124-4835-bb4f-021d3d886023", "description"":"", }.
Explanation	A trunk was added.
Possible failure causes	· The trunk name is invalid. · The tenant ID is invalid. · The parent port has been bound to another trunk. · The parent port does not exist. · The parent port and subport must be the same type. · The port ID of the parent is invalid. · The port ID of the subport is invalid. · The subport has been bound to another trunk. · The trunk ID already exists. · The value of the segmentation_Type on subport must be VLAN. · The segmentation_Type of the subport is invalid. · Duplicate segmentation ID. · The segmentation ID is out of range. · The segmentation ID of the subport is invalid. · The trunk description cannot exceed 255 characters. · The trunk name cannot exceed 255 characters. · Duplicate trunk ID. · Duplicate parent port ID. · Duplicate subport port ID. · The subport does not exist. · The controller is not the active leader. · Token aged. · Online vPorts cannot be used as subports. · The parent port and the subport cannot be the same. · The tenant ID of the parent port and the subport must be the same as the specified tenant ID. · You have no privilege to perform this operation. · Trunks do not support LB, GW, DHCP, or PBR vPorts. · Up to 255 characters, case sensitive.

Update trunk

Keyword	UPDATE_TRUNK_OP
Message text	Updated trunk $1.
Variable fields	$1: Trunk information.
Example	Updated trunk { "sub_ports":"[{ "segmentation id":"44", "port id":"4b4c691b-086d-43d2-8a65-5487e9434155", "segmentation type":"vlan", }]", "name":"foo", "tenant_id":"145a14e4-a64b-49bf-98ba-ad8945dbd4f1", "port_id":"8027c4da-772f-4e43-bfbf-023b4a4e63de", "id"":"114a26b1-d124-4835-bb4f-021d3d886023", "description"":"", }.
Explanation	A trunk was edited.
Possible failure causes	· The specified trunk does not exist. · The trunk name is invalid. · The controller is not the active leader. · The trunk description cannot exceed 255 characters. · The trunk name cannot exceed 255 characters. · Token aged. · You have no privilege to perform this operation. · Trunks do not support LB, GW, DHCP, or PBR vPorts. · You cannot edit or delete the cloud region name.

Delete trunk

Keyword	DELETE_TRUNK_OP
Message text	Deleted trunk $1.
Variable fields	$1: Trunk information.
Example	Deleted trunk { "sub_ports":"[{ "segmentation id":"44", "port id":"4b4c691b-086d-43d2-8a65-5487e9434155", "segmentation type":"vlan", }]", "name":"foo", "tenant_id":"145a14e4-a64b-49bf-98ba-ad8945dbd4f1", "port_id":"8027c4da-772f-4e43-bfbf-023b4a4e63de", "id"":"114a26b1-d124-4835-bb4f-021d3d886023", "description"":"", }.
Explanation	A trunk was deleted.
Possible failure causes	· The specified trunk does not exist. · The controller is not the active leader. · Token aged. · You have no privilege to perform this operation.

Create subports

Keyword	CREATE_SUBPORT_OP
Message text	Created subports $1.
Variable fields	$1: Subport information.
Example	Created subports { "sub port list":"[{ "segmentation id":"44", "port id":"4b4c691b-086d-43d2-8a65-5487e9434155", "segmentation type":"vlan", }]", [{ "segmentation id":"44", "port id":"4b4c691b-086d-43d2-8a65-5487e9434155", "segmentation type":"vlan", }] }.
Explanation	Subports were added.
Possible failure causes	· The specified trunk does not exist. · The parent port and subport must be the same type. · The port ID of the subport is invalid. · The subport has been bound to another trunk. · The value of the segmentation_Type on subport must be VLAN. · The segmentation_Type of the subport is invalid. · The segmentation ID of the subport is invalid. · The segmentation ID is out of range. · Duplicate segmentation ID. · Duplicate subport port ID. · The subport does not exist. · The controller is not the active leader. · Token aged. · Online vPorts cannot be used as subports. · You have no privilege to perform this operation. · Trunks do not support LB, GW, DHCP, or PBR vPorts.

Delete subports

Keyword	DELETE_SUBPORT_OP
Message text	Deleted subports $1.
Variable fields	$1: Subport information.
Example	Deleted subport s{ "sub port list":"[{ "segmentation id":"44", "port id":"4b4c691b-086d-43d2-8a65-5487e9434155", "segmentation type":"vlan", }]", [{ "segmentation id":"44", "port id":"4b4c691b-086d-43d2-8a65-5487e9434155", "segmentation type":"vlan", }] }.
Explanation	Subports were deleted.
Possible failure causes	· The specified trunk does not exist. · The subport does not exist. · The controller is not the active leader. · You have no privilege to perform this operation.

Create VPC connection

Keyword	CREATE_VPC_CONNECTION_OP
Message text	Created VPC connection $1.
Variable fields	$1: VPC connection information.
Example	Created VPC connection { "id":"e594591e-27ba-45e9-8792-9ce5ca29b0ed", "vpc_connection_id":"e594591e-27ba-45e9-8792-9ce5ca29b0ed", "fw_enabled":"e594591e-27ba-45e9-8792-9ce5ca29b0ed", "name":"vpc1", "tenant_id":"ffffffff-0000-0000-0000-000000000001", "description":"aaaaaaaaa", "local_router":"ffffffff-0000-0000-0000-000000000001", "local_cidrs":"[10.10.10.10/24]", "local_subnets"":"[073ceea5-4c17-4b24-8eb0-18407ca420e8]", "local_firewall_enable"":"false", "peer_router":"355973f6-69dd-4018-82f3-8ba3159ddf1e", "peer_cidrs":"[20.20.20.20/24]", "peer_subnets"":"[2de17490-4293-448d-9eee-b82aa446b4db]", "peer_firewall_enable"":"false", "mode":"0", "cloud_region_name":"openstack", }.
Explanation	A VPC connection 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. · The vRouter link is enabled with the firewall feature. You can add only vRouters that are bound to a single-member gateway to the vRouter link. · Unknown error. · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot overlap with any vNetwork subnet on another vRouter. · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot overlap with any external subnet on another vRouter. · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot be the same as any vNetwork subnet gateway IP of another vRouter. · The value of the firewallenable field must be true (case sensitive) or false (case sensitive). · The local_router and peer_router fields must be configured. · The value of the mode field is invalid. · When the value of the Mode field is 1, local subnets and remote subnets are not supported. · Local CIDRs cannot overlap with remote subnets. · Local CIDRs cannot overlap with remote subnets that already have VPC connections. · Local subnets cannot overlap with remote subnets. · Local CIDRs cannot overlap with remote CIDRs. · Invalid subnet mask. · Invalid IP address. · Remote CIDRs cannot overlap with remote subnets that already have VPC connections. · When the value of the Mode field is 1, local CIDRs are required. · When the value of the Mode field is 1, remote CIDRs are required. · Duplicated CIDRs exist in local or remote CIDRs. · When the network cloud feature is off, the mode value cannot be 1. · You have no privilege to perform this operation. · The vRouter link is disabled with the firewall feature. The border gateways for the local and remote vRouters must be bound to the same border device group. · Southbound devices at the following IP addresses were disconnected.

Update VPC connection

Keyword	UPDATE_ VPC_CONNECTION_OP
Message text	Updated VPC connection $1.
Variable fields	$1: VPC connection information.
Example	Updated VPC connection { "id":"e594591e-27ba-45e9-8792-9ce5ca29b0ed", "vpc_connection_id":"e594591e-27ba-45e9-8792-9ce5ca29b0ed", "fw_enabled":"e594591e-27ba-45e9-8792-9ce5ca29b0ed", "name":"vpc1", "tenant_id":"ffffffff-0000-0000-0000-000000000001", "description":"aaaaaaaaa", "local_router":"ffffffff-0000-0000-0000-000000000001", "local_cidrs":"[10.10.10.10/24]", "local_subnets"":"[073ceea5-4c17-4b24-8eb0-18407ca420e8]", "local_firewall_enable"":"false", "peer_router":"355973f6-69dd-4018-82f3-8ba3159ddf1e", "peer_cidrs":"[20.20.20.20/24]", "peer_subnets"":"[2de17490-4293-448d-9eee-b82aa446b4db]", "peer_firewall_enable"":"false", "mode":"0", "cloud_region_name":"openstack", }.
Explanation	A VPC connection was edited.
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. · The local_router and peer_router fields must be configured. · When the value of the Mode field is 1, local subnets and remote subnets are not supported. · Local CIDRs cannot overlap with remote subnets. · Local CIDRs cannot overlap with remote subnets that already have VPC connections. · Local subnets cannot overlap with remote subnets. · Local CIDRs cannot overlap with remote CIDRs. · Cannot edit the local or remote router. · Invalid subnet mask. · Invalid IP address. · Remote CIDRs cannot overlap with remote subnets that already have VPC connections. · When the value of the Mode field is 1, local CIDRs are required. · When the value of the Mode field is 1, remote CIDRs are required. · Duplicated CIDRs exist in local or remote CIDRs. · The mode field cannot be modified. · You have no privilege to perform this operation. · Southbound devices at the following IP addresses were disconnected. · You cannot edit or delete the cloud region name.

Delete VPC connection

Keyword	DELETE_VPC_CONNECTION_OP
Message text	Deleted VPC connection $1.
Variable fields	$1: VPC connection information.
Example	Deleted VPC connection { "id":"e594591e-27ba-45e9-8792-9ce5ca29b0ed", "vpc_connection_id":"e594591e-27ba-45e9-8792-9ce5ca29b0ed", "fw_enabled":"e594591e-27ba-45e9-8792-9ce5ca29b0ed", "name":"vpc1", "tenant_id":"ffffffff-0000-0000-0000-000000000001", "description":"aaaaaaaaa", "local_router":"ffffffff-0000-0000-0000-000000000001", "local_cidrs":"[10.10.10.10/24]", "local_subnets"":"[073ceea5-4c17-4b24-8eb0-18407ca420e8]", "local_firewall_enable"":"false", "peer_router":"355973f6-69dd-4018-82f3-8ba3159ddf1e", "peer_cidrs":"[20.20.20.20/24]", "peer_subnets"":"[2de17490-4293-448d-9eee-b82aa446b4db]", "peer_firewall_enable"":"false", "mode":"0", "cloud_region_name":"openstack", }.
Explanation	A VPN connection 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. · You have no privilege to perform this operation. · Southbound devices at the following IP addresses were disconnected.

Create security group

Keyword	CREATE_SECURITY_GROUP_OP
Message text	Created security group $1.
Variable fields	$1: Security group information.
Example	Created security group { "id":"85cc3048-abc3-43cc-89b3-377341426ac6", "name":"default", "tenant id":"2b2151a2-f111-40f0-a0ea-61a76879e972", "tenant name":"admin2333", "rules":"[{ "direction":"ingress", "ether type":"IPv4", "id":"0cf4ffd7-4e7c-4fac-98c4-8c301d6d3015", "port range max":"65534", "port range min":"65534", "protocol":"udp", "remote group id":"null", "remote ip prefix":"0.0.0.0/0", "description":"", "security group id":"bcf2512f-e8c9-40d2-98ef-a8ab1df1b8d9", "tenant id":"2b2151a2-f111-40f0-a0ea-61a76879e972", "cloud region name":"default", }]", "cloud region name":"default" }.
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. · Duplicate security policy UUID. · Security policies created in bulk cannot use the same ID. · Invalid empty rule action. · The security policy name cannot exceed 255 characters. · The ip_mac_bingding is required. · Unknown error. · You have no privilege to perform this operation.

Update security group

Keyword	UPDATE_SECURITY_GROUP_OP
Message text	Updated security group $1.
Variable fields	$1: Security group information.
Example	Updated security group { "id":"85cc3048-abc3-43cc-89b3-377341426ac5", "name":"mysecgroup", "tenant id":"ae511e66-546b-45a2-ad3e-a46cf64600a3", "tenant name":"admin2333", "rules":"null", "cloud region name":"default" }.
Explanation	A security group was edited.
Possible failure causes	· The request is invalid. · 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. · You have no privilege to perform this operation. · Southbound devices at the following IP addresses were disconnected. · You cannot edit or delete the cloud region name.

Delete security group

Keyword	DELETE_SECURITY_GROUP_OP
Message text	Deleted security group $1.
Variable fields	$1: Security group information.
Example	Deleted security group { "id":"85cc3048-abc3-43cc-89b3-377341426ac6", "name":"default", "tenant id":"2b2151a2-f111-40f0-a0ea-61a76879e972", "rules":"[{ "direction":"ingress", "ether type":"IPv4", "id":"0cf4ffd7-4e7c-4fac-98c4-8c301d6d3015", "port range max":"65534", "port range min":"65534", "protocol":"udp", "remote group id":"null", "remote ip prefix":"0.0.0.0/0", "description":"", "security group id":"85cc3048-abc3-43cc-89b3-377341426ac6", "tenant id":"2b2151a2-f111-40f0-a0ea-61a76879e972", "cloud region name":"default", }]", "cloud region name":"default" }.
Explanation	A security group 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 specified resource doesn't exist. · Unknown error. · You have no privilege to perform this operation.

Create security group rule

Keyword	CREATE_SECURITY_GROUP_RULE_OP
Message text	Created security group rule $1.
Variable fields	$1: Security group rule information.
Example	Created security group rule { "direction":"ingress", "ether type":"IPv4", "id":"93aa42e5-80db-4581-9391-3a608bd0e448", "port range max":"null", "port range min":"null", "protocol":"null", "remote group id":"null", "remote ip prefix":"null", "description":"rule2", "security group id":"85cc3048-abc3-43cc-89b3-377341426ac5", "tenant id":"2b2151a2-f111-40f0-a0ea-61a76879e972", "cloud region name":"default" }.
Explanation	A security group rule was created.
Possible failure causes	· The request is invalid. · 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. · You have no privilege to perform this operation. · Southbound devices at the following IP addresses were disconnected.

Update security group rule

Keyword	UPDATE_SECURITY_GROUP_RULE_OP
Message text	Updated security group rule $1.
Variable fields	$1: Security group rule information.
Example	Updated security group rule { "direction":"ingress", "ether type":"IPv4", "id":"0cf4ffd7-4e7c-4fac-98c4-8c301d6d3015", "port range max":"65534", "port range min":"65534", "protocol":"udp", "remote group id":"null", "remote ip prefix":"0.0.0.0/0", "description":"default", "security group id":"bcf2512f-e8c9-40d2-98ef-a8ab1df1b8d9", "tenant id":"2b2151a2-f111-40f0-a0ea-61a76879e972", "cloud region name":"null" }.
Explanation	A security group rule was edited.
Possible failure causes	· The request is invalid. · 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. · You have no privilege to perform this operation. · Southbound devices at the following IP addresses were disconnected. · You cannot edit or delete the cloud region name.

Delete security group rule

Keyword	DELETE_SECURITY_GROUP_RULE_OP
Message text	Deleted security group rule $1.
Variable fields	$1: Security group rule information.
Example	Deleted security group rule { "direction":"ingress", "ether type":"IPv4", "id":"93aa42e5-80db-4581-9391-3a608bd0e448", "port range max":"null", "port range min":"null", "protocol":"null", "remote group id":"null", "remote ip prefix":"null", "description":"rule2", "security group id":"85cc3048-abc3-43cc-89b3-377341426ac5", "tenant id":"2b2151a2-f111-40f0-a0ea-61a76879e972", "cloud region name":"default" }.
Explanation	A security group 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. · You have no privilege to perform this operation. · Southbound devices at the following IP addresses were disconnected.

Create VLAN-VXLAN mapping

Keyword	CREATE_VLANMAP_OP
Message text	Created VLAN-VXLAN mapping $1.
Variable fields	$1: VLAN-VXLAN mapping information.
Example	Created VLAN-VXLAN mapping { "id":"null", "host id":"null", "host name":"null", "group id":"d266e3b2-8f5c-4a13-b9a1-034522de725a", "group name":"null", "vlan range":"120", "vxlan range":"2", "cloud region name":"openstack", }.
Explanation	A VLAN-VXLAN mapping was 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. · You have no privilege to perform this operation.

Delete VLAN-VXLAN mapping

Keyword	DELETE_VLANMAP_OP
Message text	Deleted VLAN-VXLAN mapping $1.
Variable fields	$1: VLAN-VXLAN mapping information.
Example	Deleted VLAN-VXLAN mapping { "id":"null", "host id":"null", "host name":"null", "group id":"d266e3b2-8f5c-4a13-b9a1-034522de725a", "group name":"null", "vlan range":"120", "vxlan range":"2", "cloud region name":"openstack", }.
Explanation	A VLAN-VXLAN mapping 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. · You have no privilege to perform this operation. · Cannot delete VLAN-VXLAN mapping because it was created on VMM.

Create subnet

Keyword	CREATE_SUBNET_OP
Message text	Created subnet $1.
Variable fields	$1: Subnet information.
Example	Created subnet { "id":"54d6f61d-db07-451c-9ab3-b9609b6b6f0c", "name":"subnet1", "network id":"d32019d3-bc6e-4319-9c1d-6722fc136a33", "segment id":"null", "router id":"null", "domain":"null", "lease time":"null", "tenant id":"4fd44f30-2929-45e4-81c7-b8a0c8908869", "cidr":"192.0.0.0/8", "ip version":"4", "gateway ip":"192.0.0.1", "enable dhcp":"true", "ipv6 address mode":"null", "ipv6 ra mode":"null", "allocation pools":"[{ "start":"192.0.0.2", "end":"192.255.255.254", }]", "dns name servers":"[]", "service types":"[]", "host routes":"[{ "destination":"172.16.0.0/24", "nexthop":"10.0.2.20", }]", "route table id":"null", "external":"null", "multicast enable":"null", "origin":"null", "secondary":"false", "network name":"null", "physical network":"null", "cloud region name":"openstack", "nqa policy id":"null", }.
Explanation	A subnet was created.
Possible failure causes	· The request is invalid. · 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 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. · Please check the DHCP address pool for overlappingsubnets. · 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. · Failed to add subnets because the segment ID of the external network is empty and no segments exist. · You must associate the subnet with a segment because the external network of the subnet has multiple segments. · The subnet and its associated segment must belong to the same external network. · The segment doesn't exist. · Unknown error. · You have no privilege to perform this operation. · The NQA profile has been bound to another external network. · The specified NQA profile has been bound to another service resource. · The specified NQA profile does not exist. · Cannot bind the subnet to an NQA profile. The border gateway in the subnet has been bound to a track entry. · Failed to add the subnet to the vNetwork, because it overlaps with a network bound to the context in another service chain. · A vNetwork supports only one primary IP. · Up to one primray IP can be configured for an external network.

Update subnet

Keyword	UPDATE_SUBNET_OP
Message text	Updated subnet $1.
Variable fields	$1: Subnet information.
Example	Updated subnet { "id":"54d6f61d-db07-451c-9ab3-b9609b6b6f0c", "name":"subnet1", "network id":"d32019d3-bc6e-4319-9c1d-6722fc136a33", "segment id":"null", "router id":"null", "domain":"null", "lease time":"null", "tenant id":"4fd44f30-2929-45e4-81c7-b8a0c8908869", "cidr":"192.0.0.0/8", "ip version":"4", "gateway ip":"192.0.0.1", "enable dhcp":"true", "ipv6 address mode":"null", "ipv6 ra mode":"null", "allocation pools":"[{ "start":"192.0.0.2", "end":"192.255.255.254", }]", "dns name servers":"[]", "service types":"[]", "host routes":"[{ "destination":"172.16.0.0/24", "nexthop":"10.0.2.20", }]", "route table id":"null", "external":"null", "multicast enable":"null", "origin":"null", "secondary":"false", "network name":"null", "physical network":"null", "cloud region name":"openstack", "nqa policy id":"null", }.
Explanation	A subnet was edited.
Possible failure causes	· The request is invalid. · 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. · Please check the DHCP address pool for overlappingsubnets. · 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 to 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. · The segment UUID can't be delete or modify. · An IP address in the DHCP address pool has been automatically assigned to an online vPort. The DHCP address pool must still contain the IP address after being edited. · The DHCP address pool cannot contain IP addresses that have been manually assigned to online vPorts. · An IP address in the DHCP address pool has been automatically assigned to an online vPort. The DHCP address pool must still contain the IP address after being edited. · The DHCP address pool cannot contain IP addresses that have been manually assigned to online vPorts. · Unknown error. · You have no privilege to perform this operation. · Cannot edit the primary IP allocation se tting for a subnet if the subnet is already used for primary IP allocation. · Cannot edit the primary IP allocation se tting for a subnet if the subnet is already used for primary IP allocation. · The gateway IP address has been used as the primary IP address. · The external subnet contains an IP address that has been assigned to a vPort. You cannot bind the external subnet to an NQA profile. · The NQA profile has been bound to another external network. · The specified NQA profile has been bound to another service resource. · The specified NQA profile does not exist. · Cannot bind the subnet to an NQA profile. The border gateway in the subnet has been bound to a track entry. · A vNetwork supports only one primary IP. · Southbound devices at the following IP addresses were disconnected: {IP addresses}. · You cannot edit or delete the cloud region name.

Delete subnet

Keyword	DELETE_SUBNET_OP
Message text	Deleted subnet $1.
Variable fields	$1: Subnet information.
Example	Deleted subnet { "id":"54d6f61d-db07-451c-9ab3-b9609b6b6f0c", "name":"subnet1", "network id":"d32019d3-bc6e-4319-9c1d-6722fc136a33", "segment id":"null", "router id":"null", "domain":"null", "lease time":"null", "tenant id":"4fd44f30-2929-45e4-81c7-b8a0c8908869", "cidr":"192.0.0.0/8", "ip version":"4", "gateway ip":"192.0.0.1", "enable dhcp":"true", "ipv6 address mode":"null", "ipv6 ra mode":"null", "allocation pools":"[{ "start":"192.0.0.2", "end":"192.255.255.254", }]", "dns name servers":"[]", "service types":"[]", "host routes":"[{ "destination":"172.16.0.0/24", "nexthop":"10.0.2.20", }]", "route table id":"null", "external":"null", "multicast enable":"null", "origin":"null", "secondary":"false", "network name":"null", "physical network":"null", "cloud region name":"openstack", "nqa policy id":"null", }.
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. · You have no privilege to perform this operation. · The vNetwork is an interface-specific multicast network. You cannot unbind its only subnet from the vRouter. · Southbound devices at the following IP addresses were disconnected: {IP addresses}.

Create tenant

Keyword	CREATE_TENANT_OP
Message text	Created tenant $1.
Variable fields	$1: Tenant information.
Example	Created tenant { "id":"ae511e66-546b-45a2-ad3e-a46cf64600af", "name":"admin2" }.
Explanation	A tenant was created.
Possible failure causes	· The service has not been found. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The length of name is too long. · Invalid parameter. · The tenant already exists. · The tenant name is required. · The VDS ID is required. · Invalid VDS ID. · You have no privilege to perform this operation. · Up to 255 characters, case sensitive.

Update tenant

Keyword	UPDATE_TENANT_OP
Message text	Updated tenant $1.
Variable fields	$1: Tenant information.
Example	Updated tenant { "id":"ae511e66-546b-45a2-ad3e-a46cf64600af", "name":"2" }
Explanation	A tenant was edited.
Possible failure causes	· The service has not been found. · The controller is not the active leader. · Configuration recovery is in progress. · Invalid JSON format. · The length of name is too long. · Invalid parameter. · The tenant name is required. · Can't modify the default tenant. · The VDS ID cannot be modified. · The NEM service does not exist. · Cannot modify the auto allocation setting because the tenant has automatically allocated resources. · You have no privilege to perform this operation. · You cannot edit or delete the cloud region name. · You cannot edit or delete the domain name. · Up to 255 characters, case sensitive.

Delete tenant

Keyword	DELETE_TENANT_OP
Message text	Delete tenant $1.
Variable fields	$1: Tenant information.
Example	Deleted tenant { "id":"ae511e66-546b-45a2-ad3e-a46cf64600af", "name":"admin2" }.
Explanation	A tenant was deleted.
Possible failure causes	· The service has not been found. · The controller is not the active leader. · Configuration recovery is in progress. · Can't delete the default tenant. · The tenant has bound resources. · A vPort has been configured for the tenant. · You have no privilege to perform this operation. · The tenant has already been bound to a gateway. · An OSPF or OSPFv3 policy has been configured for the tenant. · A route policy has been configured for the tenant. · An IP prefix has been configured for the tenant. · A security policyhas been configured for the tenant. · A vRouter link hasbeen configured for the tenant. · A vRouterinterconnection has been configured for the tenant. · A network has been configured for the tenant. · A vRouter has been configured for the tenant.

VPNaaS

This section contains messages from the IPsec VPN service module.

Create IKE policy

Keyword	CREATE_IKEPOLICY_OP
Message text	Create IKE policy $1
Variable fields	$1: Information about the IKE policy.
Example	Create IKE policy Name: ikepolicy1 UUID: 5522aff7-1b3c-48dd-9c3c-b50f016b73db Description: ikepolicy1 IKE Version: v1 Auth Algorithm: sha1 Encryption Algorithm: aes-128 PFS: group5 Phase1 Negotiation Mode: main Lifetime: Units: seconds Value: 3600
Explanation	An IKE policy was created.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · The tenant doesn't exist. · You have no privilege to perform this operation.

Delete IKE policy

Keyword	DELETE_IKEPOLICY_OP
Message text	Delete IKE policy $1
Variable fields	$1: UUID of the IKE policy.
Example	Delete IKE policy UUID: 5522aff7-1b3c-48dd-9c3c-b50f016b73db
Explanation	An IKE policy was deleted.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · The IKE policy is in use. · You have no privilege to perform this operation.

Update IKE policy

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

Create IPsec policy

Keyword	CREATE_IPSECPOLICY_OP
Message text	Create IPsec policy $1
Variable fields	$1: Information about the IPsec policy.
Example	Create IPsec policy Name: policy UUID: 5291b189-fd84-46e5-84bd-78f40c05d69c Description: policy1 Encapsulation Mode: tunnel Transform Protocol: ESP Auth Algorithm: sha1 Encryption Algorithm: aes-128 Lifetime: Units: seconds Value: 3600 PFS: group5
Explanation	An IPsec policy was created.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · The tenant doesn't exist. · You have no privilege to perform this operation.

Delete IPsec policy

Keyword	DELETE_IPSECPOLICY_OP
Message text	Delete IPsec policy $1
Variable fields	$1: UUID of the IPsec policy.
Example	Delete IPsec policy UUID: 5291b189-fd84-46e5-84bd-78f40c05d69c
Explanation	An IPsec policy was deleted.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · The IPsec policy is in use. · You have no privilege to perform this operation.

Update IPsec policy

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

Create VPN service

Keyword	CREATE_VPNSERVICE_OP
Message text	Create VPN service $1
Variable fields	$1: Information about the VPN service.
Example	Create VPN service Name: vpn1 UUID: 9faaf49f-dd89-4e39-a8c6-101839aa49bc Description: 33 Router Id: ec8619be-0ba8-4955-8835-3b49ddb76f89 Subnet Id: f4fb4528-ed93-467c-a57b-11c7ea9f963e Admin State Up: ACTIVE
Explanation	A VPN service was created.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · The VPN service can't be bound to external subnet. · The tenant doesn't exist. · The vRouter doesn't exist. · The vSubnet doesn't exist. · The VPN service and the specified vRouter belong to different tenants. · The vSubnet is not bound to the specified vRouter. · Only an IPv4 subnet can be specified. · All local subnets must use the same IP version. · You have no privilege to perform this operation.

Delete VPN service

Keyword	DELETE_VPNSERVICE_OP
Message text	Delete VPN service $1
Variable fields	$1: UUID of the VPN service.
Example	Delete VPN service UUID: 9faaf49f-dd89-4e39-a8c6-101839aa49bc
Explanation	A VPN service was deleted.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · The VPN service is in use. · You have no privilege to perform this operation.

Update VPN service

Keyword	UPDATE_VPNSERVICE_OP
Message text	Update VPN service $1
Variable fields	$1: Information about the VPN service.
Example	Update VPN service Name: vpn1 UUID: 9faaf49f-dd89-4e39-a8c6-101839aa49bc Description: vpnservice1
Explanation	A VPN service was modified.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · The VPN service is in use. · The vSubnet doesn't exist. · The vSubnet is not bound to the specified vRouter. · Only an IPv4 subnet can be specified. · All local subnets must use the same IP version. · You have no privilege to perform this operation.

Create IPsec Site Connections

Keyword	CREATE_IPSEC_SITE_CONNS_OP
Message text	Create IPsec Site Connections $1
Variable fields	$1: Information about the IPsec site connection.
Example	Create IPsec Site Connections Name: vpnconnection1 UUID: cbc152a0-7e93-4f98-9f04-b085a4bf2511 Description: connections 1 VPN Service Id: c2f3178d-5530-4c4a-89fc-050ecd552636 IKE Policy Id: bf5612ac-15fb-460c-9b3d-6453da2fafa2 IPsec Policy Id: 8ba867b2-67eb-4835-bb61-c226804a1584 Peer Address: 172.24.4.226 Peer Id: 172.24.4.226 Peer CIDRS: [10.1.0.0/24] Auth Mode: PSK PSK: ****** Initiator: bi-directional Admin State Up: true MTU: 1500 DPD: Action: clear Interval: 30 Timeout: 120 Route Mode: static
Explanation	An IPsec site connection was created.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · The tenant doesn't exist. · The IPsec site connection and the specified VPN service belong to different tenants. · The IPsec site connection and the specified IKE policy belong to different tenants. · The IPsec site connection and the specified IPsec policy belong to different tenants. · The VPN service doesn't exist. · The IKE policy doesn't exist. · The IPsec policy doesn't exist. · Configuration recovery is in progress. · The number of IPsec site connections has reached the maximum. · The PSK parameter cannot be null if the authentication mode is PSK. · The VPN service referenced by the IPsec site connection is not bound to a vSubnet. · The local subnet and peer subnet must use the same IP version. · The peer address and peer subnet must use the same IP version. · The local subnet, peer subnet, peer address, and peer ID (in IP address format) must use the same IP version. · You have no privilege to perform this operation.

Delete IPsec Site Connection

Keyword	DELETE_IPSEC_SITE_CONN_OP
Message text	Delete IPsec Site Connection $1
Variable fields	$1: UUID of the IPsec site connection.
Example	Delete IPsec Site Connection UUID: cbc152a0-7e93-4f98-9f04-b085a4bf2511
Explanation	An IPsec site connection was deleted.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · You have no privilege to perform this operation.

Update IPsec Site Connections

Keyword	UPDATE_IPSEC_SITE_CONNS_OP
Message text	Update IPsec Site Connections $1.
Variable fields	$1: Information about the IPsec site connection.
Example	Update IPsec Site Connections Name: vpnconnection1 UUID: cbc152a0-7e93-4f98-9f04-b085a4bf2511 Description: connections 2 Peer Address: 172.24.4.226 Peer Id: 172.24.4.226 Peer CIDRS: [10.1.0.0/24] PSK: ****** Initiator: bi-directional Admin State Up: true MTU: 1500 DPD: Action: clear Interval: 30 Timeout: 120 Route Mode: static
Explanation	An IPsec site connection was modified.
Possible failure causes	· The controller is not the active leader. · The operation requires the administrator privilege. · The IPsec site connection and the specified VPN service belong to different tenants. · The IPsec site connection and the specified IKE policy belong to different tenants. · The IPsec site connection and the specified IPsec policy belong to different tenants. · The VPN service doesn't exist. · The IKE policy doesn't exist. · The IPsec policy doesn't exist. · Configuration recovery is in progress. · The VPN service referenced by the IPsec site connection is not bound to a vSubnet. · The local subnet and peer subnet must use the same IP version. · The peer address and peer subnet must use the same IP version. · The local subnet, peer subnet, peer address, and peer ID (in IP address format) must use the same IP version. · You have no privilege to perform this operation.

Create IPsec site connection peer CIDR

Keyword	CREATE_IPSEC_SITE_CONNS_PEER_CIDR_OP
Message text	Create IPsec site connection peer CIDR $1.
Variable fields	$1: Information about the peer subnet.
Example	Create IPsec site connection peer CIDR IPsec site connection UUID: cbc152a0-7e93-4f98-9f04-b085a4bf2511 Peer CIDR: 12.2.2.2/12.
Explanation	A peer subnet was created for an IPsec site connection.
Possible failure causes	· The IPsec site connection doesn't exist. · The IPsec site peer CIDR already exists. · The number of IPsec site connections has reached the maximum. · The VPN service referenced by the IPsec site connection is not bound to a vSubnet. · You have no privilege to perform this operation.

Delete IPsec site connection peer CIDR

Keyword	DELETE_IPSEC_SITE_CONNS_PEER_CIDR_OP
Message text	Delete IPsec site connection peer CIDR $1.
Variable fields	$1: Information about the peer subnet.
Example	Delete IPsec site connection peer CIDR IPsec site connection UUID: cbc152a0-7e93-4f98-9f04-b085a4bf2511 Peer CIDR: 12.2.2.2/12.
Explanation	A peer subnet of an IPsec site connection was deleted.
Possible failure causes	· The IPsec site connection doesn't exist. · The IPsec site peer CIDR doesn't exist. · The VPN service referenced by the IPsec site connection is not bound to a vSubnet. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation. · The RT generated based on the AS number of the fabric conflicts with the import RT of a Layer 2 DC interconnect associated with the VDS. · The RT generated based on the AS number of the fabric conflicts with the export RT of a Layer 2 DC interconnect associated with the VDS. · The RT generated based on the AS number of the fabric conflicts with the import RT of a Layer 3 DC interconnect associated with the VDS. · The RT generated based on the AS number of the fabric conflicts with the export RT of a Layer 3 DC interconnect associated with the VDS. · The RT reserved for the fabric connection conflicts with the import RT of a Layer 2 DC interconnect associated with the VDS. · The RT reserved for the fabric connection conflicts with the export RT of a Layer 2 DC interconnect associated with the VDS. · The RT reserved for the fabric connection conflicts with the import RT of a Layer 3 DC interconnect associated with the VDS. · The RT reserved for the fabric connection conflicts with the export RT of a Layer 3 DC interconnect associated with the VDS.

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. · You have no privilege to perform this operation. · Failed to add the fabric because the VDS has already been configured with a full-mesh fabric connection and the fabric has been enabled with multicast network capabilities. · The RT generated based on the AS number of the fabric conflicts with the import RT of a Layer 2 DC interconnect associated with the VDS. · The RT generated based on the AS number of the fabric conflicts with the export RT of a Layer 2 DC interconnect associated with the VDS. · The RT generated based on the AS number of the fabric conflicts with the import RT of a Layer 3 DC interconnect associated with the VDS. · The RT generated based on the AS number of the fabric conflicts with the export RT of a Layer 3 DC interconnect associated with the VDS. · The RT reserved for the fabric connection conflicts with the import RT of a Layer 2 DC interconnect associated with the VDS. · The RT reserved for the fabric connection conflicts with the export RT of a Layer 2 DC interconnect associated with the VDS. · The RT reserved for the fabric connection conflicts with the import RT of a Layer 3 DC interconnect associated with the VDS. · The RT reserved for the fabric connection conflicts with the export RT of a Layer 3 DC interconnect associated with the VDS.

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. · Can’t delete the specified VDS because it has been bound to a tenant. · Can’t delete the specified VDS because it create fabric connection. · Unknown error. · You have no privilege to perform this operation.

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. · Insufficient third-party vSwitch licenses. · Failed to get the vSwitch version. · You have no privilege to perform this operation. · The VXLAN tunnel name of the VDS cannot exceed 15 characters. · The bridge name of the VDS cannot exceed 15 characters. · Invalid role. · The nodes added to a DHCP host group can only be network nodes. · The DHCP host group does not exist. · A DHCP host group can contain a maximum of two network nodes. · The network node and the DHCP host group are in different fabrics. · The uplink interface name is a case-senstive string of up to 255 characters. Valid characters are letters, digits, underscores (_), hyphens (-) and dots(.).

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. · You have no privilege to perform this operation. · The uplink interface name is a case-senstive string of up to 255 characters. Valid characters are letters, digits, underscores (_), hyphens (-) and dots(.). · The host name cannot exceed 255 characters. · You cannot edit or delete the cloud region name.

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. · You have no privilege to perform this operation. · The address pool for the vRouter interconnection network does not exist or no IP addresses are available in the address pool.

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 number 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 cannot be configured with the same summary route network. · The vRouters using the public VRF cannot be bound to the same service device 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 bytes. · 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. · The external network bound to the vRouter does not have segments. The vRouter can be bound only to one IPv4 subnet. · The border gateways to the IPv4 and IPv6 external subnets are located on the same interface. You must configure them with the same segment ID. · The external network egress IP has been bound to another vRouter. To bind the current vRouter to the external network egress IP, you must make sure the current vRouter has exactly the same external subnet bindings as that vRouter. · Unknown error. · The address pool does not exist or no IP addresses are available in the address pool. · The segment or border gateway already has a priority. · If a vRouter is bound to both a gateway resource and a network segment, you can configure a priority for either the gateway resource or the network segment, but not both. · The priorities of the gateways bound to the same vRouter must be different. · Invalid tags. · The priority is out of range. · The specified segment doesn't exist. · The specified gateway doesn't exist. · Cannot configure a priority for the gateway resource. For more information, see the online help. · Failed to bind the vRouter to an external network because the specified network is not an indirectly connected external network. · Cannot disable east-west traffic offload in network cloud scenarios. · The public network VRF cannot be configured in the weak control scenario. · You have no privilege to perform this operation. · A vRouter can be bound to subnets or external network vPorts, but not both. · A vRouter cannot be bound to internal network vPorts. · The type of vPorts bound to a vRouter can only be none. · Cannot bind the external network vPort to the vRouter, because the vRouter has been bound to the external network to which the vPort belongs. · A vRouter cannot be bound to multiple IPv6 external network vPorts in the same network. · Cannot bind the external network to the vRouter, because the vRouter has been bound to a vPort in the external network. · You cannot bind VLAN external networks to a vRouter after you bind a flat external network to the vRouter. Only one flat external network can be bound to a vRouter. · A VRF name cannot start with “external_vpn”. · The RT generated based on the segment ID of the vRouter conflicts with the import RT of a Layer 2 DC interconnect associated with the vRouter. · The RT generated based on the segment ID of the vRouter conflicts with the export RT of a Layer 2 DC interconnect associated with the vRouter. · The RT reserved for the vRouter link conflicts with the import RT of a Layer 2 DC interconnect associated with the local or remote vRouter. · The RT reserved for the vRouter link conflicts with the export RT of a Layer 2 DC interconnect associated with the local or remote vRouter. · The RT generated based on the segment ID of the vRouter conflicts with the import RT of the Layer 3 DC interconnect associated with the vRouter. · The RT generated based on the segment ID of the vRouter conflicts with the export RT of the Layer 3 DC interconnect associated with the vRouter. · The RT reserved for the vRouter link conflicts with the import RT of the Layer 3 DC interconnect associated with the local or remote vRouter. · The RT reserved for the vRouter link conflicts with the export RT of the Layer 3 DC interconnect associated with the local or remote vRouter. · Check the directly connected external networks and the border interfaces in the border device group bound to this vRouter with the same segment ID. Make sure only one primary IPv4 address exists for each border interface. · vRouters do not support vPorts in flat external networks. · The vRouter context or external network vPort context has been used in a service chain. · Southbound devices at the following IP addresses were disconnected: {IP addresses}. · The segment ID cannot be identical to a VXLAN ID in a VXLAN pool or the VXLAN ID reserved for the automation template and the DR system. · Please specify a value for the ip_addr field. · Invalid ip_addr value. · Invalid source_ip value. · Invalid ip_version value. · The IP addresses specified for the ip_addr and source_ip fields must have the same IP version. · The ip_addr and ip_version fields do not match. · The peer IP address cannot be the same as the source IP address. · Please specify the device ID, device name, or both. · Please specify the device ID, device name, or both.

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 device 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 and the gateway must have been bound to a device group. · For vRouters bound to a service device group to share an external IP address, these vRouter must be bound to a gateway service resource. · 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 number 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 cannot 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. · Make sure all vRouters that use this sharing IP are bound to the same edge device for external network access. · 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. · You must specify a priority value for each subnet when more than one subnet is bound to the vRouter. · The tags field has duplicate segment IDs. · The tags field has duplicate priorities. · Invalid priority. · The external subnet is bound to the vRouter. · The external network bound to the vRouter does not have segments. The vRouter can be bound only to one IPv4 subnet. · 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 subnet of the VLAN type segment at the same time. · The vRouter to which the external network belongs is in a vRouter link, and a vPort on the peer vRouter of the vRouter link has been bound to the floating IP address of the external network. · The specified external network is segmented and has only IPv4 subnets. You must bind at least one of its IPv4 subnets to the vRouter. · The external network is segmented. You cannot unbind a subnet from the vRouter if that subnet is an IPv4 subnet and is the only subnet in the external network. · The border gateways to the IPv4 and IPv6 external subnets are located on the same interface. You must configure them with the same segment ID. · The external network egress IP has been bound to another vRouter. To bind the current vRouter to the external network egress IP, you must make sure the current vRouter has exactly the same external subnet bindings as that vRouter. · Unknown error. · The address pool does not exist or no IP addresses are available in the address pool. · The external network specified for the vRouter is not segmented. You can bind only one IPv4 subnet and one IPv6 subnet to the vRouter. · The vRouter is bound to multiple IPv4 and IPv6 external subnets. The network segments to which external subnets of the same IP version are bound cannot be bound to the same border gateway. · The border gateways to the IPv4 and IPv6 external subnets are located on the same interface. You must configure them with the same segment ID. · The segment or border gateway already has a priority. · If a vRouter is bound to both a gateway resource and a network segment, you can configure a priority for either the gateway resource or the network segment, but not both. · You cannot assign priorities to the external subnets bound to the vRouter if they belong to different segments configured with the same border gateway. · The priorities of the gateways bound to the same vRouter must be different. · Invalid tags. · The priority is out of range. · The specified segment doesn't exist. · The specified gateway doesn't exist. · Cannot configure a priority for the gateway resource. For more information, see the online help. · External subnets of the same version bound to the vRouter cannot be bound to the same network segment. · Cannot specify a gateway resource configured with a priority and a segmented external network for a vRouter at the same time. · The external network specified for the vRouter is segmented. You must bind a minimum of one external subnet to the vRouter. · The external network egress IP has already been bound to a vRouter that uses different gateway resources from the current vRouter. Only vRouters that use the same gateway resources can share an external network egress IP. · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot overlap with any vNetwork subnet on another vRouter. · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot overlap with any external subnet on another vRouter. · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot be the same as any vNetwork subnet gateway IP of another vRouter. · The source IP address of a route entry on the vRouter cannot be the same as any vNetwork subnet gateway IP on the vRouter. · The source IP address of a route entry on the vRouter cannot be within any vNetwork subnet on the vRouter. · The source IP address of a route entry on the vRouter cannot be within any external subnet on the vRouter. · Failed to bind the vRouter to an external network because the specified network is not an indirectly connected external network. · Failed to configure BGP peers for the vRouter because the vRouter has been configured with BGP neighbors. · Cannot disable east-west traffic offload in network cloud scenarios. · You cannot bind the routing table to the vRouter. The routing table contains a BFD-enabled route entry whose next hop is a vPort with the same IP address as the gateway IP address of a vNetwork bound to the vRouter. · Failed to enable multicast capabilities because the vRouter has already established a vRouter link. · You have no privilege to perform this operation. · Cannot enable multicast network capabilities for the vRouter because the vRouter has been bound to a Layer 3 DC interconnect. · A vRouter can be bound to subnets or external network vPorts, but not both. · A vRouter cannot be bound to internal network vPorts. · The type of vPorts bound to a vRouter can only be none. · Cannot bind the external network vPort to the vRouter, because the vRouter has been bound to the external network to which the vPort belongs. · A vRouter cannot be bound to multiple IPv6 external network vPorts in the same network. · Cannot bind the external network to the vRouter, because the vRouter has been bound to a vPort in the external network. · You cannot bind VLAN external networks to a vRouter after you bind a flat external network to the vRouter. Only one flat external network can be bound to a vRouter. · You cannot bind the vRouter to a segmented external network. The vRouter uses a firewall as the edge device to the external network and has been bound to a border device group that uses the hairpin or inline third-party firewall deployment mode. · The RT generated based on the segment ID of the vRouter conflicts with the import RT of a Layer 2 DC interconnect associated with the vRouter. · The RT generated based on the segment ID of the vRouter conflicts with the export RT of a Layer 2 DC interconnect associated with the vRouter. · The RT reserved for the vRouter link conflicts with the import RT of a Layer 2 DC interconnect associated with the local or remote vRouter. · The RT reserved for the vRouter link conflicts with the export RT of a Layer 2 DC interconnect associated with the local or remote vRouter. · The RT generated based on the segment ID of the vRouter conflicts with the import RT of the Layer 3 DC interconnect associated with the vRouter. · The RT generated based on the segment ID of the vRouter conflicts with the export RT of the Layer 3 DC interconnect associated with the vRouter. · The RT reserved for the vRouter link conflicts with the import RT of the Layer 3 DC interconnect associated with the local or remote vRouter. · The RT reserved for the vRouter link conflicts with the export RT of the Layer 3 DC interconnect associated with the local or remote vRouter. · Cannot bind the subnet to a vRouter if the subnet is used for primary IP allocation. · Cannot bind the subnet to a vRouter if the subnet is used for primary IP allocation. · Subnets in the external network do not have sufficient IP addresses for allocation. · Failed to assign IP addresses to devices attached to the border gateway, because the IP addresses in the primary IP allocation are insufficient. · Check the directly connected external networks and the border interfaces in the border device group bound to this vRouter with the same segment ID. Make sure only one primary IPv4 address exists for each border interface. · vRouters do not support vPorts in flat external networks. · The vRouter context or external network vPort context has been used in a service chain. · Please specify two and only two external subnets for the external context. This is required because the context uses primary/backup gateway deployment mode and the edge device to the external network in the vRouter for the context is the border device. · The external subnet has been bound to a context. Please access the context page to remove the binding first. · The context uses primary/backup gateway deployment mode. Make sure the associated vRouter is bound to two gateway members or external subnets. · The context uses single gateway deployment mode. Make sure the associated vRouter is bound to one gateway member or external subnet. · The vRouter-attached gateway members enable the third-party firewall option. Please enable or disable the firewall option across all IP addresses or subnets in the vRouter-attached external network if the egress of the external network is the firewall or border device, respectively. · The vRouter-attached gateway members disable the third-party firewall option and use hairpin firewall deployment. Please make sure the firewall is enabled or disabled across all IP addresses and subnets in the external network. · Failed to unbind the vRouter from the external network. The vRouter has been bound to a Layer 3 multicast network or a multicast source used for external services. · Not enough addresses in subnets in network segment. · Failed to unbind the vRouter from the subnet. The subnet has been bound to a Layer 3 multicast network or a multicast source used for external services. · Southbound devices at the following IP addresses were disconnected: {IP addresses}. · The segment ID cannot be identical to a VXLAN ID in a VXLAN pool or the VXLAN ID reserved for the automation template and the DR system. · Please specify a value for the ip_addr field. · Invalid ip_addr value. · Invalid source_ip value. · Invalid ip_version value. · The IP addresses specified for the ip_addr and source_ip fields must have the same IP version. · The ip_addr and ip_version fields do not match. · The peer IP address cannot be the same as the source IP address. · Please specify the device ID, device name, or both. · Please specify the device ID, device name, or both. · You cannot edit or delete the cloud region name. · You cannot edit the segment ID of the vRouter, because the vRouter has OVS vPorts.

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. · You have no privilege to perform this operation. · Failed to delete the vRouter because the vRouter has BGP peers. · You cannot delete the vRouter, because it has been bound to a EPG. · You cannot delete the vRouter, because it has been bound to a context. · Southbound devices at the following IP addresses were disconnected. · You cannot delete the vRouter, because it has been bound to an application policy.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · 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 vPort already exists. · The port ID is different than the gateway port ID. · The selected subnet cannot overlap with the network that contains the ingress or egress vPort in the vRouter's service chain. · Unknown error. · You have no privilege to perform this operation. · The subnet overlaps with a remote subnet in a Layer 3 DC interconnection that involves the vRouter. · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot overlap with any vNetwork subnet on another vRouter. · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot overlap with any external subnet on another vRouter. · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot be the same as any vNetwork subnet gateway IP of another vRouter. · The source IP address of a route entry on the vRouter cannot be the same as any vNetwork subnet gateway IP on the vRouter. · The source IP address of a route entry on the vRouter cannot be within any vNetwork subnet on the vRouter. · The source IP address of a route entry on the vRouter cannot be within any external subnet on the vRouter. · Subnets in the same vNetwork must be bound to the same vRouter. · The indirectly connected external network can't be directly deleted from or added to the router. · Subnets in the same external network must be bound to the same vRouter. · You cannot bind a vRouter to a vPort created by using a subnet for primary IP allocation. · The IPv4 subnet has been bound to a context, or it overlaps with the subnet attached to a service instance's ingress/egress vPort in a service chain. It cannot be assignedto the vRouter already specified in an IPv4 or IPv4 & IPv6 application policy. · The IPv4 subnet overlaps with the subnet attached to the ingress or egress vPort for a service instance of a service path specified in an application policy. It cannot be assigned to this vRouter, which has been bound to a service chain. · Failed to assign the IPv4 subnet to the vRouter, because the vRouter has been bound to both a router context in a service chain and an IPv4 or IPv4 & IPv6 application policy. · Failed to add some of the vSubnets. Please make sure the selected vSubnets are not used in the service chain associated with the vRouter. · Failed to bind the subnet to the vRouter, because it overlaps with a network bound to the context in another service chain. · The vRouter-attached gateway members enable the third-party firewall option. Please enable or disable the firewall option across all IP addresses or subnets in the vRouter-attached external network if the egress of the external network is the firewall or border device, respectively. · The vRouter-attached gateway members disable the third-party firewall option and use hairpin firewall deployment. Please make sure the firewall is enabled or disabled across all IP addresses and subnets in the external network. · Southbound devices at the following IP addresses were disconnected: {IP addresses}. · You cannot bind the IPv6 subnet to the vRouter, because the vRouter belongs to a vRouter link and has been bound to a centralized vNetwork. · Failed to bind the subnet to the vRouter, because the vRouter has been used by a service chain and bound to an external EPG containing external network CIDR 0.0.0.0/0. · The multicast network feature has been enabled for the external network, and the external network cannot be bound to a vRouter through a vPort. · A Layer 3 multicast network has been added to the external network, and the external network cannot be bound to a vRouter through a vPort.

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. · You have no privilege to perform this operation. · The indirectly connected external network can't be directly deleted from or added to the router. · Failed to remove the subnet from the vRouter because the vRouter has BGP peers on this subnet. · The vRouter has not been bound to the port. · The vNetwork is an interface-specific multicast network. You cannot unbind its only subnet from the vRouter. · Southbound devices at the following IP addresses were disconnected: {IP addresses}.

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 number 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. · The provider field and the segment field cannot be both configured. · The flat type external network cannot be configured with segment. · The ID already exists. · The value of the network type can only be VLAN. · The network type is required. · The segment ID is not in the VLAN pool. · physical network is required. · The specified composite gateway doesn't exist. · You can create segments only for external networks. · The segment name cannot exceed 255 characters. · The description cannot exceed 255 characters. · Invalid segmentUUID. · The external network has been bound to a vRouter. · Invalid segment ID. · Unknown error. · The value of the MTU must be an integer in the range of 68 to 65535. · The specified QoS policy doesn't exist. · Invalid value in the physical_network field. · A vNetwork cannot use directly connected mode. · When the Network Cloud feature is disabled, directly connected external networks are not supported. · Only internal network can be configured as resource operating mode. · You have no privilege to perform this operation. · Cannot bind the DHCP host group to an external network. · The DHCP host group does not exist. · The RT generated based on the segment ID of the vNetwork conflicts with the import RT of the Layer 2 DC interconnect associated with the vNetwork. · The RT generated based on the segment ID of the vNetwork conflicts with the export RT of the Layer 2 DC interconnect associated with the vNetwork. · The RT reserved for a fabric connection on the vNetwork conflicts with the import RT of the Layer 2 DC interconnect associated with the vNetwork. · The RT reserved for a fabric connection on the vNetwork conflicts with the export RT of the Layer 2 DC interconnect associated with the vNetwork. · The RT generated based on the segment ID of the vNetwork conflicts with the import RT of the Layer 3 DC interconnect associated with the vNetwork. · The RT generated based on the segment ID of the vNetwork conflicts with the export RT of the Layer 3 DC interconnect associated with the vNetwork. · The RT reserved for a fabric connection on the vNetwork conflicts with the import RT of the Layer 3 DC interconnect associated with the vNetwork. · The RT reserved for a fabric connection on the vNetwork conflicts with the export RT of the Layer 3 DC interconnect associated with the vNetwork. · Invalid auto port creation configuration. · You cannot bind the DHCP host group to the vNetwork. A network node in the DHCP host group has already created a DHCP vPort for the vNetwork. · To disable preprovisioning, make sure all its dependent features use their default settings. · Make sure the segment ID (VLAN ID) is not in a tenant carrier network VLAN pool and vRouter interconnection network VLAN pool when the external network or vNetwork type is VLAN. · You cannot change the status of the multicast network feature when the network segmentation feature is enabled. · The external segment ID is already in use. · The external segment ID is out of range. · Southbound devices at the following IP addresses were disconnected: {IP addresses}. · You can enable external route redistribution only for external networks. · You can enable external route redistribution only when the L3VNI is specified. · The segment ID cannot be identical to a VXLAN ID in a VXLAN pool or the VXLAN ID reserved for the automation template and the DR system. · VLAN ID of VLAN type network is not allowed to conflict with DRNI Routed IPLs border device VLAN ID

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. · Cannot segment the external network because it has been bound to a vRouter that is bound to a gateway resource configured with a priority. · The value of the MTU must be an integer in the range of 68 to 65535. · The specified QoS policy doesn't exist. · Invalid value in the physical_network field. · A vNetwork cannot use directly connected mode. · When the Network Cloud feature is disabled, directly connected external networks are not supported. · You have no privilege to perform this operation. · Cannot enable multicast network capabilities for the vNetwork because the vNetwork has been bound to a Layer 2 DC interconnect. · Cannot bind the DHCP host group to an external network. · The DHCP host group does not exist. · Invalid auto port creation configuration. · You cannot bind the DHCP host group to the vNetwork. A network node in the DHCP host group has already created a DHCP vPort for the vNetwork. · The vNetwork is an interface-specific multicast network. You cannot disable its multicast capabilities. · To disable preprovisioning, make sure all its dependent features use their default settings. For information about these features, see online help. · You cannot change the status of the multicast network feature when the network segmentation feature is enabled. · The external segment ID is already in use. · The external segment ID is out of range. · Southbound devices at the following IP addresses were disconnected: {IP addresses}. · You can enable external route redistribution only for external networks. · You can enable external route redistribution only when the L3VNI is specified. · You cannot edit or delete the cloud region name. · The external network has been bound to a vRouter through a vPort, and the multicast network feature cannot be enabled for the external network.

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. · You have no privilege to perform this operation. · Southbound devices at the following IP addresses were disconnected: {IP addresses}. · Cannot delete the vNetwork because it has been bound to an OSPF or OSPFv3 policy.

Create subnet

Keyword	CREATE_SUBNET_OP
Message text	Created subnet "$1" in vNetwork "$2" for tenant "$3".
Variable fields	$1: Subnet name. $2: Name or UUID of the vNetwork to which the subnet belongs. $3: Name or UUID of the tenant to which the subnet belongs.
Example	Created subnet "sub1" in vNetwork “net1” for tenant “admin”.
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 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. · Please check the DHCP address pool for overlappingsubnets. · 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. · Failed to add subnets because the segment ID of the external network is empty and no segments exist. · You must associate the subnet with a segment because the external network of the subnet has multiple segments. · The subnet and its associated segment must belong to the same external network. · The segment doesn't exist. · Unknown error. · You have no privilege to perform this operation. · The NQA profile has been bound to another external network. · The specified NQA profile has been bound to another service resource. · The specified NQA profile does not exist. · Cannot bind the subnet to an NQA profile. The border gateway in the subnet has been bound to a track entry. · Failed to add the subnet to the vNetwork, because it overlaps with a network bound to the context in another service chain. · A vNetwork supports only one primary IP. · Up to one primray IP can be configured for an external network.

Update subnet

Keyword	UPDATE_SUBNET_OP
Message text	Updated subnet "$1" in vNetwork “$2” for tenant “$3”.
Variable fields	$1: Subnet name. $2: Name or UUID of the vNetwork to which the subnet belongs. $3: Name or UUID of the tenant to which the subnet belongs.
Example	Updated subnet "sub2" in vNetwork “net2” for tenant “admin”.
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. · Please check the DHCP address pool for overlappingsubnets. · 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 to 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. · The segment UUID can't be delete or modify. · An IP address in the DHCP address pool has been automatically assigned to an online vPort. The DHCP address pool must still contain the IP address after being edited. · The DHCP address pool cannot contain IP addresses that have been manually assigned to online vPorts. · Unknown error. · You have no privilege to perform this operation. · An IP address in the DHCP address pool has been automatically assigned to an online vPort. The DHCP address pool must still contain the IP address after being edited. · The DHCP address pool cannot contain IP addresses that have been manually assigned to online vPorts. · Cannot edit the primary IP allocation se tting for a subnet if the subnet is already used for primary IP allocation. · Cannot edit the primary IP allocation se tting for a subnet if the subnet is already used for primary IP allocation. · The gateway IP address has been used as the primary IP address. · The external subnet contains an IP address that has been assigned to a vPort. You cannot bind the external subnet to an NQA profile. · The NQA profile has been bound to another external network. · The specified NQA profile has been bound to another service resource. · The specified NQA profile does not exist. · Cannot bind the subnet to an NQA profile. The border gateway in the subnet has been bound to a track entry. · A vNetwork supports only one primary IP. · Southbound devices at the following IP addresses were disconnected: {IP addresses}. · You cannot edit or delete the cloud region name.

Delete subnet

Keyword	DELETE_SUBNET_OP
Message text	Deleted subnet "$1" in vNetwork “$2” for tenant “$3”.
Variable fields	$1: Subnet name. $2: Name or UUID of the vNetwork to which the subnet belongs. $3: Name or UUID of the tenant to which the subnet belongs.
Example	Deleted subnet "sub3" in vNetwork “net3” for tenant “admin”.
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. · You have no privilege to perform this operation. · The vNetwork is an interface-specific multicast network. You cannot unbind its only subnet from the vRouter. · Southbound devices at the following IP addresses were disconnected: {IP addresses}.

Create QoS

Keyword	CREATE_QOS_OP
Message text	Created QoS "$1".
Variable fields	$1: QoS policy name.
Example	Created QoS "policy01".
Explanation	A QoS 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. · Invalid rate value. · Network policies created in bulk cannot use the same UUID. · Unknown error. · You have no privilege to perform this operation.

Update QoS

Keyword	UPDATE_QOS_OP
Message text	Updated QoS "$1".
Variable fields	$1: QoS policy name.
Example	Updated QoS "policy01".
Explanation	A QoS 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. · Invalid rate value. · Unknown error. · You have no privilege to perform this operation. · Southbound devices at the following IP addresses were disconnected: {IP addresses}. · You cannot edit or delete the cloud region name.

Delete QoS

Keyword	DELETE_QOS_OP
Message text	Deleted QoS "$1".
Variable fields	$1: QoS policy name.
Example	Deleted QoS "policy01".
Explanation	A QoS policy was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · The QoS policy has been bound to floating IPs. · The specified resource doesn't exist. · Unknown error. · You have no privilege to perform this operation. · The Qos policy has been bound to a port. · The Qos policy has been bound to a port group. · The Qos policy has been bound to a virtual network.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation. · Southbound devices at the following IP addresses were disconnected: {IP addresses}. · You cannot edit or delete the cloud region name.

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 specified resource doesn't exist. · Unknown error. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation. · Cannot set floating IPs for a directly connected external network. · When you create a floating IP, if you specify only the vPort or App cluster VIP and the vRouter of the floating IP is bound to one external network with network segmentation enabled or multiple external networks, you must specify an IP address for the floating IP. · You cannot select a subnet for primary IP allocation when creating a floating IP. · The external network does not have IPv4 vSubnets for allocating floating Ips.

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. · The subnet to which the floating IP belongs has been bound to a network segment, and no subnet bound to the network segment has been bound to a vRouter. · Unknown error. · You have no privilege to perform this operation. · Cannot set floating IPs for a directly connected external network. · You cannot edit or delete the cloud region name.

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. · You have no privilege to perform this operation.

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 description cannot exceed 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. · Can't specify a network whose origin is PBR. · Unknown error. · You have no privilege to perform this operation. · A port group cannot be bound to a security policy when it contains port security disabled vPorts.

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. · The description cannot exceed 255 characters. · Unknown error. · You have no privilege to perform this operation. · A port group cannot be bound to a security policy when it contains port security disabled vPorts. · Southbound devices at the following IP addresses were disconnected: {IP addresses}.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation. · Southbound devices at the following IP addresses were disconnected: {IP addresses}.

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. · You have no privilege to perform this operation. · Southbound devices at the following IP addresses were disconnected: {IP addresses}. · You cannot edit or delete the cloud region name.

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. · You have no privilege to perform this operation. · Southbound devices at the following IP addresses were disconnected: {IP addresses}.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

Create vPort

Keyword	CREATE_VPORT_OP
Message text	Created vPort "Name: $1, IPv4: $2, IPv6: $3, MAC: $4".
Variable fields	$1: Name of the subnet to which the vPort belongs. $2: IPv4 address of the vPort. $3: IPv6 address of the vPort. $4: MAC address of the vPort.
Example	Created vPort "Name: tap1, IPv4:100.1.1, IPv6: 150:1:ABCD, MAC: 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. · You cannot delete the gateway vPort. · 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. · You have no privilege to perform this operation. · vPorts do not support directly connected external networks. · The value of the port_security_enabled is invalid. · A port group cannot be bound to a security policy when it contains port security disabled vPorts. · A vPort with port security disabled cannot be bound to a security policy. · A vPort with port security disabled cannot be configured with allowed address pairs. · The MAC address cannot contain all zeros or all Fs. · Do not specify the port_isolated field when you create a vPort. · A vPort name cannot start with "gateway". · Please enter an IP address for the external network vPort. · You cannot select a subnet for primary IP allocation when creating a vPort . · You cannot bind a vPort to a subnet for primary IP allocation in an external network. · The external subnet where the specified IP address resides has been bound to an NQA profile. You cannot assign the IP address to a vPort. · Failed to connect to (hosts or access devices). Host or access device Ips. · The latest links are invalid or no links exist on the netoverlay hosts found by names of (hosts or access devices). · No device exists at either end or both ends of the latest links on the netoverlay hosts found by names of (hosts or access devices). · No device exists at either end or both ends of the links found by names of (hosts or access devices). · The interfaces of some links found by names of (hosts or access devices) are not AC interfaces. · The destination host name for the migrating_to parameter cannot exceed 255 characters.

Update vPort

Keyword	UPDATE_VPORT_OP
Message text	Updated vPort "Name: $1, IPv4: $2, IPv6: $3, MAC: $4".
Variable fields	$1: Name of the vPort. $2: IPv4 address of the vPort. $3: IPv6 address of the vPort. $4: MAC address of the vPort.
Example	Updated vPort "Name: tap1, IPv4:100.1.1, IPv6: 150:1:ABCD, MAC: 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. · 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. · You have no privilege to perform this operation. · vPorts do not support directly connected external networks. · The value of the port_security_enabled is invalid. · A port group cannot be bound to a security policy when it contains port security disabled vPorts. · A vPort with port security disabled cannot be bound to a security policy. · A vPort with port security disabled cannot be configured with allowed address pairs. · The MAC address cannot contain all zeros or all Fs. · A vPort name cannot start with "gateway". · Please enter an IP address for the external network vPort. · Only OVS vPorts can be blocked. · You cannot bind a vPort to a subnet for primary IP allocation in an external network. · The external subnet where the specified IP address resides has been bound to an NQA profile. You cannot assign the IP address to a vPort. · Failed to edit the IP address for the vPort, because the new IP address is in a network bound to the context in another service chain. · The value for the fw_enabled parameter is invalid. · The vRouter-attached gateway members enable the third-party firewall option. Please enable or disable the firewall option across all IP addresses or subnets in the vRouter-attached external network if the egress of the external network is the firewall or border device, respectively. · The vRouter-attached gateway members disable the third-party firewall option and use hairpin firewall deployment. Please make sure the firewall is enabled or disabled across all IP addresses and subnets in the external network. · Failed to connect to (hosts or access devices). Host or access device Ips. · The latest links are invalid or no links exist on the netoverlay hosts found by names of (hosts or access devices). · No device exists at either end or both ends of the latest links on the netoverlay hosts found by names of (hosts or access devices). · No device exists at either end or both ends of the links found by names of (hosts or access devices). · The interfaces of some links found by names of (hosts or access devices) are not AC interfaces. · The destination host name for the migrating_to parameter cannot exceed 255 characters. · You cannot edit or delete the cloud region name.

Delete vPort

Keyword	DELETE_VPORT_OP
Message text	Deleted vPort "Name: $1, IPv4: $2, IPv6: $3, MAC: $4".
Variable fields	$1: Name of the subnet to which the vPort belongs. $2: IPv4 address of the vPort. $3: IPv6 address of the vPort. $3: MAC address of the vPort.
Example	Deleted vPort "Name: tap1, IPv4:100.1.1, IPv6: 150:1:ABCD, MAC: 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. · You cannot delete the gateway vPort. · Unknown error. · You have no privilege to perform this operation. · Failed to connect to (hosts or access devices). Host or access device Ips. · The latest links are invalid or no links exist on the netoverlay hosts found by names of (hosts or access devices). · No device exists at either end or both ends of the latest links on the netoverlay hosts found by names of (hosts or access devices). · No device exists at either end or both ends of the links found by names of (hosts or access devices). · The interfaces of some links found by names of (hosts or access devices) are not AC interfaces. · The destination host name for the migrating_to parameter cannot exceed 255 characters.

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. · Cannot create distributed vRouter links in Network cloud feature. · You have no privilege to perform this operation. · Cannot create vRouter links when the Network Cloud feature is enabled. · You cannot create a vRouter link of the normal, PBR, or NBAC type, because the local or remote vRouter on the link has been bound to both a centralized vNetwork and an IPv6 subnet.

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. · You have no privilege to perform this operation.

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. · A vPort on one vRouter of the vRouter link has been bound to the floating IP address of the external network bound to the other vRouter of the vRouter link. · Unknown error. · You have no privilege to perform this operation.

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. · Can't specify a vRouter whose origin is PBR. · Unknown error. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation. · You cannot edit or delete the cloud region name.

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. · You have no privilege to perform this operation.

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: 1.1.1.0/24, next hop type: IPv4, next hop: 1.1.1.1, type: 0, enable BFD: false, source IPs: []".
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. · The route entries cannot be created on edge devices. · Can't specify a vRouter whose origin is PBR. · The first BFD source IP address in a route entry cannot be the same as the second BFD source IP address in another route entry, and vice versa. · The first BFD source IP address in a route entry cannot be the same as the second source IP address of a BGP peer bound to the same vRouter as the route entry, and vice versa. · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot overlap with any vNetwork subnet on another vRouter. · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot overlap with any external subnet on another vRouter. · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot be the same as any vNetwork subnet gateway IP of another vRouter. · The source IP address of a route entry on the vRouter cannot be the same as any vNetwork subnet gateway IP on the vRouter. · The source IP address of a route entry on the vRouter cannot be within any vNetwork subnet on the vRouter. · The source IP address of a route entry on the vRouter cannot be within any external subnet on the vRouter. · The next hop type cannot be blackhole when the value of the type field is 401 or 402. · When network cloud is enabled, the value for the type field cannot be 0. · The value of the type field is invalid. · The IP version of the IP address is invalid. · The two source IP address must be different. · Invalid source IP address. · When the value of the type field is 401 and BFD enabled, a source IP is required. · A maximum of two source IP addresses are supported. · When the Network Cloud feature is disabled, routes with vPort or non-vPort as the next hop type are not supported. · The next hop type and next hop IP address do not match. · The destination subnet and the next hop type do not match. · When the next hop type is IPv6, host route recursion is not supported. · Route entries that are enabled with BFD and use vPort next hops must have the same source IP address if they have the same next hop IP address. · A route entry with the same settings already exists. Route entries that are enabled with BFD and use vPort next hops cannot have the same next hop IP address. · Cannot enable BFD for route entries that use non-vPort next hops. · Route entries that use vPort or non-vPort next hops cannot be edited. · When BFD is disabled, a source IP address is not required. · The source IP address cannot be the same as the IP address of any gateway bound to the vRouter. · The source IP address cannot belong to any subnet bound to the vRouter. · The source IP address cannot belong to any external subnet bound to the vRouter. · Do not specify the next hop vRouter when the next hop type is ExtIPv4 or ExtIPv6. · The next hop in the route entry is a vPort and BFD is enabled for the route entry. You cannot set its IP address to be the gateway IP address of a vNetwork bound to the same vRouter as the routing table. · Cannot apply the route entry to devices when the next hop type of the route entry is ExtIPv4 or ExtIPv6. · You have no privilege to perform this operation. · The source IP address cannot be within the destination subnet. · The source IP address conflicts with the next hop IP address. · Southbound devices at the following IP addresses were disconnected: {IP addresses}.

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: 1.1.1.0/24, next hop type: IPv4, next hop: 1.1.1.1, type: 0, enable BFD: false, source IPs: []".
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. · The route entries cannot be created on edge devices. · The value of the type field is invalid. · When the Network Cloud feature is disabled, routes with vPort or non-vPort as the next hop type are not supported. · When the next hop type is IPv6, host route recursion is not supported. · Cannot apply the route entry to devices when the next hop type of the route entry is ExtIPv4 or ExtIPv6. · You have no privilege to perform this operation. · Southbound devices at the following IP addresses were disconnected: {IP addresses}. · You cannot edit or delete the cloud region name.

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: 1.1.1.0/24, next hop type: IPv4, next hop: 1.1.1.1, type: 0, enable BFD: false, source IPs: []".
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. · You have no privilege to perform this operation. · Southbound devices at the following IP addresses were disconnected: {IP addresses}.

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. · Can't specify a network whose origin is PBR. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation. · Southbound devices at the following IP addresses were disconnected: {IP addresses}.

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. · Can't specify a network whose origin is PBR. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation. · Southbound devices at the following IP addresses were disconnected: {IP addresses}.

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. · You have no privilege to perform this operation. · Southbound devices at the following IP addresses were disconnected: {IP addresses}.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

Delete port name prefix

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. · You have no privilege to perform this operation.

Updated the global configuration of the controller

Keyword	UPDATE_GLOBAL_CONFIG_OP
Message text	Updated the global configuration of the controller: $1.
Variable fields	$1: Global configuration.
Example	Updated the global configuration of the controller. Stateful flow table: On.
Explanation	The global configuration was edited.
Possible failure causes	· Configuration recovery is in progress. · The controller is not the active leader. · The VXLAN pool doesn't exists. · You have no privilege to perform this operation. · The VDS doesn't exist. · Invalid DHCP failover to third-party servers. · You cannot enable DHCP failover to third-party servers when distributed DHCP is enabled for host overlay. · You cannot enable distributed DHCP for host overlay when DHCP failover to third-party servers is enabled.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation. · Cannot delete netoverlay host because it was created on VMM.

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. · You have no privilege to perform this operation. · You cannot edit or delete the cloud region name.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation. · Cannot delete VLAN-VXLAN mapping because it was created on VMM.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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	· You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation. · You cannot edit or delete the cloud region name.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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 can specify the subpolicy only when the value of the target is sub-policy. · Invalid target. · 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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation. · Invalid NS packet type. · The NS packet type cannot be empty if the packet type is ICMP and the ICMP packet type is 135. · Invalid target address. · The target address cannot be empty if the packet type is ICMP and the ICMP packet type is 135. · The target address must be global unicast address or link local address.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

Start synchronization to host

Keyword	START_OPENFLOW_ DATA_SYNCHRONIZATION_OP
Message text	Started synchronizing $1 to host $2.
Variable fields	$1: Data synchronization object. $2: Host IP address.
Example	Started synchronizing [flow tables, group tables] to 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. · You have no privilege to perform this operation.

Start auditing OVSDB configuration on host

Keyword	START_OVSDB_AUDIT_OP
Message text	Started auditing “$1” on host “$2”
Variable fields	$1: OVSDB configuration, such as MTU. $2: IP address of the host.
Example	Started auditing “MTU” on host “1.1.1.1”.
Explanation	Audited OVSDB configuration for a host.
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. · You have no privilege to perform this operation.

Start synchronization OVSDB configuration on host

Keyword	START_OVSDB_DATA_SYNCHRONIZATION_OP
Message text	Started synchronizing “$1” on host “$2”.
Variable fields	$1: OVSDB configuration, such as MTU. $2: IP address of the host.
Example	Started synchronizing “MTU” on host “1.1.1.2”.
Explanation	Synchronized OVSDB configuration for a host.
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. · You have no privilege to perform this operation.

Start auditing DHCP configuration on host

Keyword	START_DHCP_CONFIG_AUDIT_OP
Message text	Started auditing DHCP configuration on host $1.
Variable fields	$1: IP address of the host.
Example	Started auditing DHCP configuration on host 1.1.1.1.
Explanation	Audited the DHCP configuration on a host.
Possible failure causes	· The controller is not the active leader. · Configuration restoration is in progress. · Invalid IP address. · The host has not established a WebSocket connection to the controller. · The device model does not support data synchronization or audit because of the device type restriction. · The system is synchronizing or auditing data for the host. · Unknown error. · You have no privilege to perform this operation.

Start synchronization DHCP configuration to host

Keyword	START_DHCP_CONFIG_SYNCHRONIZATION_OP
Message text	Started synchronizing DHCP configuration to host $1.
Variable fields	$1: IP address of the host.
Example	Started synchronizing DHCP configuration to host 1.1.1.2.
Explanation	Synchronized DHCP configuration to a host.
Possible failure causes	· The controller is not the active leader. · Configuration restoration is in progress. · Invalid IP address. · The host has not established a WebSocket connection to the controller. · The device model does not support data synchronization or audit because of the device type restriction. · The system is synchronizing or auditing data for the host. · Unknown error. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation. · Cannot delete static link because it was created on VMM.

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. · The vRouter link is enabled with the firewall feature. You can add only vRouters that are bound to a single-member gateway to the vRouter link. · Unknown error. · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot overlap with any vNetwork subnet on another vRouter. · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot overlap with any external subnet on another vRouter. · The source IP address of a route entry with a vPort-type next hop on the vRouter cannot be the same as any vNetwork subnet gateway IP of another vRouter. · The value of the firewallenable field must be true (case sensitive) or false (case sensitive). · The local_router and peer_router fields must be configured. · The value of the mode field is invalid. · When the value of the Mode field is 1, local subnets and remote subnets are not supported. · Local CIDRs cannot overlap with remote subnets. · Local CIDRs cannot overlap with remote subnets that already have VPC connections. · Local subnets cannot overlap with remote subnets. · Local CIDRs cannot overlap with remote CIDRs. · Invalid subnet mask. · Invalid IP address. · Remote CIDRs cannot overlap with remote subnets that already have VPC connections. · When the value of the Mode field is 1, local CIDRs are required. · When the value of the Mode field is 1, remote CIDRs are required. · Duplicated CIDRs exist in local or remote CIDRs. · When the network cloud feature is off, the mode value cannot be 1. · You have no privilege to perform this operation. · The vRouter link is disabled with the firewall feature. The border gateways for the local and remote vRouters must be bound to the same border device group. · Southbound devices at the following IP addresses were disconnected.

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. · You have no privilege to perform this operation. · The local_router and peer_router fields must be configured. · When the value of the Mode field is 1, local subnets and remote subnets are not supported. · Local CIDRs cannot overlap with remote subnets. · Local CIDRs cannot overlap with remote subnets that already have VPC connections. · Local subnets cannot overlap with remote subnets. · Local CIDRs cannot overlap with remote CIDRs. · Cannot edit the local or remote router. · Invalid subnet mask. · Invalid IP address. · Remote CIDRs cannot overlap with remote subnets that already have VPC connections. · When the value of the Mode field is 1, local CIDRs are required. · When the value of the Mode field is 1, remote CIDRs are required. · Duplicated CIDRs exist in local or remote CIDRs. · The mode field cannot be modified. · Southbound devices at the following IP addresses were disconnected {IP addresses}. · You cannot edit or delete the cloud region name.

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. · You have no privilege to perform this operation. · Southbound devices at the following IP addresses were disconnected {IP addresses}.

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. · You have no privilege to perform this operation. · The import RT of the Layer 2 DC interconnect conflicts with the RT of the vNetwork associated with the Layer 2 DC interconnect. · The export RT of the Layer 2 DC interconnect conflicts with the RT of the vNetwork associated with the Layer 2 DC interconnect. · The import RT of the Layer 2 DC interconnect conflicts with the RT reserved for a fabric connection associated with the Layer 2 DC interconnect. · The export RT of the Layer 2 DC interconnect conflicts with the RT reserved for a fabric connection associated with the Layer 2 DC interconnect. · The import RT of the Layer 2 DC interconnect conflicts with the RT of the vRouter associated with the Layer 2 DC interconnect. · The export RT of the Layer 2 DC interconnect conflicts with the RT of the vRouter associated with the Layer 2 DC interconnect. · The import RT of the Layer 2 DC interconnect conflicts with the RT reserved for a vRouter link associated with the Layer 2 DC interconnect. · The export RT of the Layer 2 DC interconnect conflicts with the RT reserved for a vRouter link associated with the Layer 2 DC interconnect. · Failed to bind the Layer 2 DC interconnect to the vNetwork because multicast network capabilities have been enabled for the vNetwork.

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. · You have no privilege to perform this operation. · Failed to bind the Layer 2 DC interconnect to the vNetwork because multicast network capabilities have been enabled for the vNetwork. · The import RT of the Layer 2 DC interconnect conflicts with the RT of the vNetwork associated with the Layer 2 DC interconnect. · The export RT of the Layer 2 DC interconnect conflicts with the RT of the vNetwork associated with the Layer 2 DC interconnect. · The import RT of the Layer 2 DC interconnect conflicts with the RT reserved for a fabric connection associated with the Layer 2 DC interconnect. · The export RT of the Layer 2 DC interconnect conflicts with the RT reserved for a fabric connection associated with the Layer 2 DC interconnect. · The import RT of the Layer 2 DC interconnect conflicts with the RT of the vRouter associated with the Layer 2 DC interconnect. · The export RT of the Layer 2 DC interconnect conflicts with the RT of the vRouter associated with the Layer 2 DC interconnect. · The import RT of the Layer 2 DC interconnect conflicts with the RT reserved for a vRouter link associated with the Layer 2 DC interconnect. · The export RT of the Layer 2 DC interconnect conflicts with the RT reserved for a vRouter link associated with the Layer 2 DC interconnect.

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. · You have no privilege to perform this operation.

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 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 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. · 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. · The vRouter can be bound to only one border gateway. Make sure the vRouter or the vRouter-attached tenant is bound to a border gateway that uses a border device group only for DC Interconnection. · Unknown error. · You have no privilege to perform this operation. · The mapping segment ID already exists. · The import RT of the Layer 3 DC interconnect conflicts with the RT of a vNetwork associated with the Layer 3 DC interconnect. · The export RT of the Layer 3 DC interconnect conflicts with the RT of a vNetwork associated with the Layer 3 DC interconnect. · The import RT of the Layer 3 DC interconnect conflicts with the RT reserved for a fabric connection associated with the Layer 3 DC interconnect. · The export RT of the Layer 3 DC interconnect conflicts with the RT reserved for a fabric connection associated with the Layer 3 DC interconnect. · The import RT of the Layer 3 DC interconnect conflicts with the RT of the vRouter associated with the Layer 3 DC interconnect. · The export RT of the Layer 3 DC interconnect conflicts with the RT of the vRouter associated with the Layer 3 DC interconnect. · The import RT of the Layer 3 DC interconnect conflicts with the RT reserved for a vRouter link associated with the Layer 3 DC interconnect. · The export RT of the Layer 3 DC interconnect conflicts with the RT reserved for a vRouter link associated with the Layer 3 DC interconnect. · You cannot enable the firewall option for the Layer 3 DC interconnect. This is because either the vRouter or the vRouter-attached tenant is bound to a border gateway that uses a border device group only for DC Interconnection.

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 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 subnets overlap with the subnets of the vRouter. · The remote subnet is required when the firewall service is enabled. · 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. · 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. · You have no privilege to perform this operation. · The mapping segment ID already exists. · The import RT of the Layer 3 DC interconnect conflicts with the RT of a vNetwork associated with the Layer 3 DC interconnect. · The export RT of the Layer 3 DC interconnect conflicts with the RT of a vNetwork associated with the Layer 3 DC interconnect. · The import RT of the Layer 3 DC interconnect conflicts with the RT reserved for a fabric connection associated with the Layer 3 DC interconnect. · The export RT of the Layer 3 DC interconnect conflicts with the RT reserved for a fabric connection associated with the Layer 3 DC interconnect. · The import RT of the Layer 3 DC interconnect conflicts with the RT of the vRouter associated with the Layer 3 DC interconnect. · The export RT of the Layer 3 DC interconnect conflicts with the RT of the vRouter associated with the Layer 3 DC interconnect. · The import RT of the Layer 3 DC interconnect conflicts with the RT reserved for a vRouter link associated with the Layer 3 DC interconnect. · The export RT of the Layer 3 DC interconnect conflicts with the RT reserved for a vRouter link associated with the Layer 3 DC interconnect.

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. · You have no privilege to perform this operation.

Create Layer 3 DC interconnection extra

Keyword	CREATE_L3DCICONNECT_EXTRA_OP
Message text	Created an extra Layer 3 DC interconnection.
Variable fields	N/A
Example	Created an extra Layer 3 DC interconnection.
Explanation	Created an extra Layer 3 DC interconnection.
Possible failure causes	· The request is invalid. · The extra UUID already exists. · The L3 DC interconnection ID is required. · The specified resource doesn't exist. · Invalid CIDR. · IPv6 link-local addresses cannot be used as subnet addresses. · The subnets in the redistributed routes overlap. · The subnets in the summary routes overlap. · When the firewall is enabled, do not set routeControlMode to denylist. · Invalid routeControlMode value. · When the firewall is enabled, do not configure EXTERNALCIDRS. · When the firewall is enabled, do not set MACIPROUTESUPPRESSION to true. · Unknown error. · You have no privilege to perform this operation.

Update Layer 3 DC interconnection extra

Keyword	UPDATE_L3DCICONNECT_OP
Message text	Updated the extra Layer 3 DC interconnection.
Variable fields	N/A
Example	Updated the extra Layer 3 DC interconnection.
Explanation	Updated the extra Layer 3 DC interconnection.
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 L3 DC interconnection ID is required. · Invalid CIDR. · IPv6 link-local addresses cannot be used as subnet addresses. · The subnets in the redistributed routes overlap. · The subnets in the summary routes overlap. · When the firewall is enabled, do not set routeControlMode to denylist. · Invalid routeControlMode value. · When the firewall is enabled, do not configure EXTERNALCIDRS. · When the firewall is enabled, do not set MACIPROUTESUPPRESSION to true. · Unknown error. · You have no privilege to perform this operation.

Delete Layer 3 DC interconnection extra

Keyword	DELETE_L3DCICONNECT_OP_EXTRA
Message text	Deleted the extra Layer 3 DC interconnection.
Variable fields	N/A
Example	Deleted the extra Layer 3 DC interconnection.
Explanation	Deleted the extra Layer 3 DC interconnection.
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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

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. · You have no privilege to perform this operation.

Create segment

Keyword	CREATE_SEGMENT_OP
Message text	Created segment $1.
Variable fields	$1: Network segment name.
Example	Created segment “segment01”.
Explanation	A network segment was created.
Possible failure causes	· The request is invalid. · The operation requires the administrator privilege. · The ID already exists. · The value of the network type can only be VLAN. · The network type is required. · The network ID is required. · The segment ID is not in the VLAN pool. · The segment has been bound to subnets. · physical network is required. · The specified composite gateway doesn't exist. · The network doesn't exist. · Invalid segmentUUID. · You can create segments only for external networks. · The segment name cannot exceed 255 characters. · The description cannot exceed 255 characters. · When you create the first segment for the external network, the segment type must be the same as the type of the external network. · When you create the first segment for the external network, the ID of the segment must be the same as the segment ID of the external network. · Operation failed. To enable network segmentation for the external network, make sure all vRouters bound to the external network use the same border gateway or none of them uses a border gateway. · The external network is bound to a vRouter that is configured with a gateway, and you must specify this gateway for the segment. · Invalid segment ID. · Cannot segment the external network because it has been bound to a vRouter that is bound to a gateway resource configured with a priority. · You have no privilege to perform this operation. · The segment ID number already exists. · You cannot change the status of the network segmentation feature when the multicast network feature is enabled. · You cannot change the network segmentation state for the external network, because it has been bound to a Layer 3 multicast network. · The external segment ID is already in use. · The external segment ID is out of range. · The RT reserved for a fabric connection on the vNetwork conflicts with the import RT of a Layer 2 DC interconnect. · The RT reserved for a fabric connection on the vNetwork conflicts with the export RT of a Layer 2 DC interconnect. · The RT reserved for a fabric connection on the vNetwork conflicts with the import RT of a Layer 3 DC interconnect. · The RT reserved for a fabric connection on the vNetwork conflicts with the export RT of a Layer 3 DC interconnect. · You cannot bind the external network segment to a border gateway that uses a border device group only for DC Interconnection.

Update segment

Keyword	UPDATE_SEGMENT_OP
Message text	Updated segment $1.
Variable fields	$1: Network segment name.
Example	Updated segment “segment01”.
Explanation	A network segment was modified.
Possible failure causes	· The request is invalid. · The operation requires the administrator privilege. · The specified resource doesn't exist. · The segment name cannot exceed 255 characters. · The description cannot exceed 255 characters. · You have no privilege to perform this operation. · The external segment ID is already in use. · The external segment ID is out of range. · The RT reserved for a fabric connection on the vNetwork conflicts with the import RT of a Layer 2 DC interconnect. · The RT reserved for a fabric connection on the vNetwork conflicts with the export RT of a Layer 2 DC interconnect. · The RT reserved for a fabric connection on the vNetwork conflicts with the import RT of a Layer 3 DC interconnect. · The RT reserved for a fabric connection on the vNetwork conflicts with the export RT of a Layer 3 DC interconnect. · You cannot edit or delete the cloud region name.

Delete segment

Keyword	DELETE_SEGMENT_OP
Message text	Deleted segment $1.
Variable fields	$1: Network segment name.
Example	Deleted segment “segment01”
Explanation	A network segment was deleted.
Possible failure causes	· The operation requires the administrator privilege. · The segment has been bound to subnets. · The specified resource doesn't exist. · You have no privilege to perform this operation.

Created trunk

Keyword	CREATE_TRUNK_OP
Message text	Create trunk $1.
Variable fields	$1: Trunk name.
Example	Create trunk "trunk0".
Explanation	A trunk was created.
Possible failure causes	· The trunk name is invalid. · The tenant ID is invalid. · The parent port has been bound to another trunk. · The parent port does not exist. · The parent port and subport must be the same type. · The port ID of the parent is invalid. · The port ID of the subport is invalid. · The subport has been bound to another trunk. · The trunk ID already exists. · The value of the segmentation_Type on subport must be VLAN. · The segmentation_Type of the subport is invalid.. · Duplicate segmentation ID. · The segmentation ID is out of range. · The segmentation ID of the subport is invalid. · The trunk description cannot exceed 255 characters. · The trunk name cannot exceed 255 characters. · Duplicate trunk ID. · Duplicate parent port ID. · Duplicate subport port ID. · The subport does not exist. · The controller is not the active leader. · Token aged. · Online vPorts cannot be used as subports. · The parent port and the subport cannot be the same. · The tenant ID of the parent port and the subport must be the same as the specified tenant ID. · You have no privilege to perform this operation. · Trunks do not support LB, GW, DHCP, or PBR vPorts. · Up to 255 characters, case sensitive.

Update trunk

Keyword	UPDATE_TRUNK _OP
Message text	Update trunk $1.
Variable fields	$1: Trunk name.
Example	Update trunk "trunk0".
Explanation	A trunk was updated.
Possible failure causes	· The specified trunk does not exist. · The trunk name is invalid. · The controller is not the active leader. · The trunk description cannot exceed 255 characters. · The trunk name cannot exceed 255 characters. · You have no privilege to perform this operation. · Trunks do not support LB, GW, DHCP, or PBR vPorts. · You cannot edit or delete the cloud region name.

Deleted trunk

Keyword	DELETE_TRUNK _OP
Message text	Delete trunk $1.
Variable fields	$1: Trunk name.
Example	Delete trunk "trunk1".
Explanation	A trunk was deleted.
Possible failure causes	· The specified trunk does not exist. · The controller is not the active leader. · Token aged. · You have no privilege to perform this operation.

Created subports

Keyword	CREATE_SUBPORTS_OP
Message text	Created subports to trunk “$1”. The subports information is as follows: $2.
Variable fields	$1: Trunk name. $2: Subport information.
Example	Created subports to trunk "trunk". The subports information is as follows: [ SubportEntity [ segmentationType=VLAN, portId=72114d24-d550-45e4-99e1-f5da5ba982ee, segmentationId=103]].
Explanation	A subport was added to the trunk.
Possible failure causes	· The specified trunk does not exist. · The parent port and subport must be the same type. · The port ID of the subport is invalid. · The subport has been bound to another trunk. · The value of the segmentation_Type on subport must be VLAN. · The segmentation_Type of the subport is invalid. · The segmentation ID of the subport is invalid. · The segmentation ID is out of range. · Duplicate segmentation ID. · Duplicate subport port ID. · The subport does not exist. · The controller is not the active leader. · Token aged. · Online vPorts cannot be used as subports. · You have no privilege to perform this operation. · Trunks do not support LB, GW, DHCP, or PBR vPorts.

Deleted subports

Keyword	DELETE_SUBPORTS_OP
Message text	Deleted subports from trunk “$1”. The subports information is as follows: $2.
Variable fields	$1: Trunk name. $2: Subport information.
Example	Deleted subports from trunk "trunk". The subports information is as follows: [ SubportEntity [ segmentationType= VLAN, portId=72114d24-d550-45e4-99e1-f5da5ba982ee, segmentationId=103]].
Explanation	A subport was deleted from the trunk.
Possible failure causes	· The specified trunk does not exist. · The subport does not exist. · The controller is not the active leader. · You have no privilege to perform this operation.

Update Network Cloud feature

Keyword	UPDATE_GLOBALCONFIG_OP
Message text	Updated Network Cloud feature: $1
Variable fields	$1: Network cloud scenario switch.
Example	Updated Network Cloud feature “true”.
Explanation	The network cloud scenario state was switched.
Possible failure causes	· Failed to disable the Network Cloud feature. The controller cannot have virtual link layer networks or external networks. · Failed to disable the Network Cloud feature. The controller cannot host vRouters. · Cannot disable the Network Cloud feature because border devices exist. · You have no privilege to perform this operation. · Cannot enable the network cloud scenario when the third-party firewall deployment mode of the border device group is hairpin or inline.

Download audit difference

Keyword	DOWNLOAD_AUDIT_DIFF_OP
Message text	Started downloading audit difference $1.
Variable fields	$1: Audit difference file name.
Example	Started downloading audit difference 00-05-00-50-56-9a-6c-08-flow.xlsx.
Explanation	An audit difference file was downloaded.
Possible failure causes	· The specified resource doesn't exist. · Unknown error. · You have no privilege to perform this operation.

Import hosts

Keyword	BATCH_IMPORT_HOST_OP
Message text	Imported “$1” hosts.
Variable fields	$1: Number of the hosts.
Example	Imported 2 hosts.
Explanation	Hosts were imported.
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. · Insufficient third-party vSwitch licenses. · Failed to get the vSwitch version. · You have no privilege to perform this operation. · Please specify a compute domain name. · Please specify a fabric. · The fabric does not exist. · Invalid OVSDB port number. · The OVSDB port number must be an integer in the range of 0 to 65535. · Invalid template. Please download the latest template.

Batch delete hosts

Keyword	BATCH_DELETE_HOST_OP
Message text	Batch deleted hosts “$1”.
Variable fields	$1: IP addresses of the hosts.
Example	Batch deleted hosts “1.1.1.1,1.1.1.2”.
Explanation	Multiple hosts were deleted in bulk.
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. · You have no privilege to perform this operation.

Create DHCP host group

Keyword	ADD_DHCP_HOST_GROUP_OP
Message text	Created DHCP host group “$1”.
Variable fields	$1: Name of the DHCP host pool.
Example	Created DHCP host group “group”.
Explanation	A DHCP host group was created.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · Please specify a DHCP host group name. · The DHCP host group name cannot exceed 255 characters. · Please specify a fabric UUID. · The fabric does not exist. · A DHCP host group already exists with the specified UUID. · A DHCP host group already exists with the specified name. · Please examine the DHCP host group UUIDs and make sure they are all unique. · Please examine the DHCP host group names and make sure they are all unique. · You have no privilege to perform this operation.

Update DHCP host group

Keyword	UPDATE_DHCP_HOST_GROUP_OP
Message text	Updated DHCP host group “$1”.
Variable fields	$1: Name of the DHCP host pool.
Example	Updated DHCP host group “group”.
Explanation	A DHCP host pool was edited.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · Please specify a DHCP host group name. · The DHCP host group name cannot exceed 255 characters. · Please specify a fabric UUID. · The fabric does not exist. · A DHCP host group already exists with the specified name. · Cannot edit the fabric UUID. · You have no privilege to perform this operation.

Delete DHCP host group

Keyword	DELETE_DHCP_HOST_GROUP_OP
Message text	Deleted DHCP host group “$1”.
Variable fields	$1: Name of the DHCP host pool.
Example	Deleted DHCP host group “group”.
Explanation	A DHCP host group was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · Cannot delete the DHCP host group. The group contains network nodes. · Cannot delete the DHCP host group. The group has been bound to a vNetwork. · Cannot delete the DHCP host group. The group has been bound to a DHCP resource pool. · You have no privilege to perform this operation.

Create DHCP resource pool

Keyword	ADD_DHCP_RESOURCE_OP
Message text	Created DHCP resource pool “$1”.
Variable fields	$1: Name of the DHCP resource pool.
Example	Created DHCP resource pool “resource”.
Explanation	A DHCP resource pool was created.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · Please specify a DHCP resource pool name. · You have no privilege to perform this operation. · The DHCP resource pool name cannot exceed 255 characters. · Please specify a VNI range. · Invalid VNI range. · Please specify a VNI value in the range of 1 to 16777215. · Please examine the VNI ranges and make sure they do not overlap. · Invalid DHCP host group UUID. · Some of the specified DHCP host groups have not been created yet. · Please examine the DHCP host group UUIDs and make sure they are all unique. · A DHCP resource pool already exists with the specified UUID. · A DHCP resource pool already exists with the specified name. · Please specify a DHCP host group that has not been bound to any DHCP resource pool. · The VNI ranges overlap with those in another DHCP resource pool. · Please examine the DHCP resource pool UUIDs and make sure they are all unique. · Please examine the DHCP resource pool names and make sure they are all unique. · Please make sure no DHCP host groups are added to more than one DHCP resource pool. · Please examine the VNI ranges and make sure they do not overlap.

Update DHCP resource pool

Keyword	UPDATE_DHCP_RESOURCE_OP
Message text	Updated DHCP resource pool “$1”.
Variable fields	$1: Name of the DHCP resource pool.
Example	Updated DHCP resource pool “group”.
Explanation	A DHCP resource pool was edited.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · Please specify a DHCP resource pool name. · You have no privilege to perform this operation. · The DHCP resource pool name cannot exceed 255 characters. · Please specify a VNI range. · Invalid VNI range. · Please specify a VNI value in the range of 1 to 16777215. · Please examine the VNI ranges and make sure they do not overlap. · Invalid DHCP host group UUID. · Some of the specified DHCP host groups have not been created yet. · Please examine the DHCP host group UUIDs and make sure they are all unique. · The API does not support editing the DHCP host group list. · The VNI ranges overlap with those in another DHCP resource pool. · A DHCP resource pool already exists with the specified name.

Delete DHCP resource pool

Keyword	DELETE_DHCP_RESOURCE_OP
Message text	Deleted DHCP resource pool “$1”.
Variable fields	$1: Name of the DHCP resource pool.
Example	Deleted DHCP resource pool “group”.
Explanation	A DHCP resource pool was deleted.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · You have no privilege to perform this operation.

Add DHCP host group to DHCP resource pool

Keyword	ADD_HOSTGROUP_INTERFACE_OP
Message text	Added DHCP host group “$1” to DHCP resource pool “$2”.
Variable fields	$1: DHCP host group name. $2: DHCP resource pool name.
Example	Added DHCP host group “group” to DHCP resource “resource”.
Explanation	Added DHCP host groups to a DHCP resource pool.
Possible failure causes	· The request is invalid. · The controller is not the active leader. · Configuration recovery is in progress. · You have no privilege to perform this operation. · Invalid DHCP host group UUID. · Some of the specified DHCP host groups have not been created yet. · Please examine the DHCP host group UUIDs and make sure they are all unique. · Some of the specified DHCP host groups have already been added to the DHCP resource pool. · Please specify a DHCP host group that has not been bound to any DHCP resource pool.

Delete DHCP host group from DHCP resource pool

Keyword	DELETE_HOSTGROUP_INTERFACE_OP
Message text	Deleted DHCP host group “$1” from DHCP resource “$2”.
Variable fields	$1: DHCP host group name. $2: DHCP resource pool name.
Example	Delete DHCP host group “group” from DHCP resource “resource”.
Explanation	DHCP host groups were deleted from a DHCP resource pool.
Possible failure causes	· The controller is not the active leader. · Configuration recovery is in progress. · You have no privilege to perform this operation. · The request is invalid.

Update uplink port name

Keyword	UPDATE_DETECT_UPLINK_OP
Message text	Updated the name of the uplink port on the host. Uplink port name: $1.
Variable fields	$1: Uplink port name.
Example	Updated the name of the uplink port on the host. Uplink port name: ens255.
Explanation	The name of an uplink port was edited.
Possible failure causes	· The uplink interface name is a case-senstive string of up to 255 characters. Valid characters are letters, digits, underscores (_), hyphens (-) and dots(.). · You have no privilege to perform this operation.

Back up flow tables

Keyword	FLOW_BACKUP_OP
Message text	· If flow table backup failed on all hosts, this field displays Backed up flow tables. · If flow table backup finished on all hosts, this field displays Backup completed on all selected hosts. · If flow table backup finished on some hosts, this field displays Backup succeeded on hosts: $1. · If no flow table is backed up, this field displays Backup not performed on any one of the hosts. Please check for backup-incapable hosts or OVS bridge disconnection.
Variable fields	$1: IP addresses of hosts.
Example	· Backed up flow tables. · Backup completed on all selected hosts. · Backup succeeded on hosts: 98.0.69.8,98.0.69.9 · Backup not performed on any one of the hosts. Please check for backup-incapable hosts or OVS bridge disconnection.
Explanation	Backed up flow tables of all hosts.
Possible failure causes	· OpenFlow connections are disconnected on some hosts. · The specified device doesn't exist. · Invalid IP address. · Unknown error. · The value for the coverage field must be all or batch. · The host list cannot be empty when the coverage field is set to batch. · Host configuration obtaining or deployment timed out.

Restore flow tables

Keyword	FLOW_RESTORE_OP
Message text	· If flow table restoration failed on all hosts, this field displays Restored flow tables. · If flow table restoration finished on all hosts, this field displays Restoration completed on all selected hosts. · If flow table restoration finished on some hosts, this field displays Restoration succeeded on hosts: $1. · If no flow table is restored, this field displays Restoration not performed on any one of the hosts. Please check for restoration-incapable hosts or OVS bridge disconnection.
Variable fields	$1: IP addresses of hosts.
Example	· Restored flow tables. · Restoration completed on all selected hosts. · Restoration succeeded on hosts: 98.0.69.8,98.0.69.9 · Restoration not performed on any one of the hosts. Please check for restoration-incapable hosts or OVS bridge disconnection.
Explanation	Restored flow tables of all hosts.
Possible failure causes	· Please specify a file name. · The flow table restoration mode can only be replace or merge. · OpenFlow connections are disconnected on some hosts. · The specified device doesn't exist. · Invalid IP address. · Unknown error. · The request is invalid. · The value for the coverage field must be all or batch. · The host list cannot be empty when the coverage field is set to batch. · Host configuration obtaining or deployment timed out.

Update settings

Keyword	PUT_BACKUP_OP
Message text	Updated settings: $1.
Variable fields	$1: New settings.
Example	Updated settings: backup_enable: true, backup_internal: 12, backup_filenumber: 10, delete_backup_file: false
Explanation	Updated settings.
Possible failure causes	· The backup interval must be an integer in the range of 1 to 128. · The maximum number of files to retain must be an integer in the range of 1 to 30. · Unknown error. · The request is invalid.

Update the auto identification of vPorts without host IDs in network overlay feature

Keyword	UPDATE_GLOBALCONFIG_OP
Message text	Set the state of the auto identification of vPorts without host IDs in network overlay feature to $1.
Variable fields	$1: Enabling state of the auto identification of vPorts without host IDs in network overlay feature.
Example	Set the state of the auto identification of vPorts without host IDs in network overlay feature to On.
Explanation	Edited the state of the auto identification of vPorts without host IDs in network overlay feature.
Possible failure causes	N/A

Create NQA profile

Keyword	CREATE_NQAPOLICY_OP
Message text	Created NqaProfile “$1”.
Variable fields	$1: NQA profile name.
Example	Created NqaProfile “nqa1”.
Explanation	An NQA profile was created.
Possible failure causes	· An NQA profile already exists with the specified name. · An NQA operation already exists with the specified admin name and tag. · The NQA profile name cannot exceed 255 characters. · The NQA operation admin name cannot exceed 32 characters. · The NQA operation tag cannot exceed 32 characters. · The NQA description cannot exceed 255 characters. · Please specify an NQA profile name. · Please specify an NQA operation admin name. · You cannot specify an NQA operation admin name when the manual NQA profile mode is used. · You cannot specify an NQA operation tag when the manual NQA profile mode is used. · You cannot specify an NQA probe interval when the manual NQA profile mode is used. · You cannot specify the maximum number of consecutive NQA probe failures when the manual NQA profile mode is used. · Please specify an NQA track entry number. · You cannot specify an NQA track entry number when the auto NQA profile mode is used. · The track entry number must be an integer in the range of 1 to 512. · Please specify an NQA operation tag.

Update NQA profile

Keyword	UPDATE_NQAPOLICY_OP
Message text	Updated NqaProfile “$1”.
Variable fields	$1: NQA profile name.
Example	Updated NqaProfile “nqa1”.
Explanation	An NQA profile was edited.
Possible failure causes	· The NQA description cannot exceed 255 characters. · An NQA profile already exists with the specified name. · The NQA profile name cannot exceed 255 characters. · The NQA operation admin name cannot be edited. · The NQA operation tag cannot be edited. · The probe interval cannot be edited. · The probe failure count cannot be edited.

Delete NQA profile

Keyword	DELETE_NQAPOLICY_OP
Message text	Deleted NqaProfile “$1”.
Variable fields	$1: NQA profile name.
Example	Deleted NqaProfile “nqa1”.
Explanation	An NQA profile was deleted.
Possible failure causes	· The specified NQA profile has been bound to another service resource. · The NQA profile has been bound to an external network and cannot be deleted.

Exported floating IPs

Keyword	EXPORT_FLOATING_IP_OP
Message text	Exported floating IPs.
Variable fields	N/A
Example	Exported floating IPs.
Explanation	Floating IPs were exported.
Possible failure causes	· Unknown error. · Failed to export floating IP addresses.

H3C SeerEngine-DC Operation Log Messages Reference-E37xx-5W702

Create mapping table of access network

Execute capacity simulation task

Register SeerAnalyzer info

Back up configuration

Upload backup file

Download backup file

Modify configuration