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

HomeSupportResource CenterSDNH3C SeerEngine-DCH3C SeerEngine-DCTechnical DocumentsMaintainMessage ReferencesH3C SeerEngine-DC Operation Log Messages Reference-E37xx-5W701

H3C SeerEngine-DC

Operation Log Messages Reference

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Document version: 5W701-20210702

 

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

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

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

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


Contents

Introduction· 1

Viewing operation log messages· 1

Syslog message format 2

Using this document 4

BGP·· 6

Create BGP cluster 6

Update BGP cluster 7

Delete BGP cluster 7

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

Register SeerAnalyzer info· 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_REGION·· 47

Create region· 47

Delete region· 48

Update region· 49

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

CON_TEAM·· 70

Create team·· 70

Delete team·· 71

Modify team·· 71

Add member 72

Delete member 72

Modify member 73

CON_TOPOLOGY·· 74

Update device· 74

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

Add a role· 81

Update a role· 82

Delete a role· 83

DATACHECK·· 84

Start data check· 84

Stop data check· 84

DNEC·· 85

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

Fabrics· 90

Create Fabric· 91

Update Fabric· 93

Delete Fabric· 94

Search Fabric· 95

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 VIP· 137

Update VIP· 138

Delete VIP· 139

Create listener 140

Update listener 142

Delete listener 143

Create policy· 144

Update policy· 146

Delete policy· 147

Create rule· 148

Update rule· 149

Delete rule· 150

Create pool 151

Update pool 152

Delete pool 153

Create VIP· 154

Update VIP· 156

Delete VIP· 157

Create member 158

Update member 159

Delete member 160

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 EPG·· 172

Update EPG·· 174

Delete EPG·· 176

NEM·· 177

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 multicast 288

Update multicast 291

Delete multicast 293

Create ACL· 293

Delete ACL· 294

Create ACL rule· 294

Delete ACL rule· 295

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

NGFWM·· 397

Add device· 397

Update device· 398

Delete device· 398

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

Create vNetwork· 489

Update vNetwork· 493

Delete vNetwork· 494

Create subnet 495

Update subnet 499

Delete subnet 501

Create router 502

Update router 505

Delete router 511

Create link· 512

Update link· 513

Delete link· 514

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

Add host 521

Delete host 522

Add VNFM·· 523

Update VNFM·· 524

Delete VNFM·· 525

SSLVPNaaS·· 526

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

TELEMETRY·· 555

Create collector 555

Update collector 556

Delete collector 556

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

Tenant 571

Add tenant 571

Update tenant 571

Delete tenant 572

Import tenants· 573

TPaaS·· 574

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

TPFW··· 579

Add TPFW·· 579

Update TPFW·· 580

Delete TPFW·· 581

Create vRouter link· 582

Delete vRouter link· 583

VMM·· 584

Create vCenter 584

Update vCenter 585

Delete vCenter 586

Create VDS· 587

Delete VDS· 587

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 RHVM·· 602

Update RHVM·· 603

Delete RHVM·· 604

Reconnect RHVM·· 605

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

Update agent 620

Delete agent 621

Create vRouter 622

Update vRouter 625

Delete vRouter 631

Create QoS· 633

Update QoS· 634

Delete QoS· 636

Create floating IP· 637

Update floating IP· 639

Delete floating IP· 641

Create vPort 642

Update vPort 645

Delete vPort 648

Create network· 650

Update network· 653

Delete network· 656

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 segment 672

Update segment 674

Delete segment 675

Create trunk· 676

Update trunk· 677

Delete trunk· 678

Create subports· 679

Delete subports· 680

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 subnet 694

Update subnet 696

Delete subnet 699

Create tenant 700

Update tenant 701

Delete tenant 702

VPNaaS·· 703

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

VSM·· 713

Create VDS· 713

Update VDS· 714

Delete VDS· 715

Add host 715

Update host 716

Delete host 717

Create vRouter 717

Update vRouter 720

Delete vRouter 724

Create internal route· 725

Delete internal route· 726

Create interface· 726

Delete interface· 728

Create network· 728

Update network· 731

Delete network· 732

Create subnet 733

Update subnet 734

Delete subnet 735

Create QoS· 736

Update QoS· 736

Delete QoS· 737

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

Upload vib· 746

Delete vib· 746

Install VFE· 746

Update VFE· 747

Uninstall VFE· 747

Create domain· 747

Update domain· 748

Delete domain· 748

Create vPort 749

Update vPort 751

Delete vPort 753

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

Create segment 795

Update segment 796

Delete segment 797

Created trunk· 797

Update trunk· 798

Deleted trunk· 798

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.

·     Unsigned or untrusted jars contained within.

·     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 doesnt 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