选择区域语言: EN CN HK

H3C VCFC-DC 操作日志信息参考-5W100

手册下载

 

1 简介··· 1

1.1 查看操作日志·· 1

1.2 Syslog日志格式说明·· 1

1.3 文档使用说明·· 4

2 BSM·· 5

2.1 Create mapping table of access network· 5

2.2 Update mapping table of access network· 6

2.3 Delete mapping table of access network· 7

2.4 Modify inspection port status· 8

2.5 Bound working port to mapping table· 9

2.6 Unbound working port to mapping table· 11

2.7 Add default access VLAN· 13

2.8 Delete default access VLAN· 13

2.9 Create mapping table of service network· 14

2.10 Update mapping table of service network· 15

2.11 Delete mapping table of service network· 16

2.12 Bound mapping table to device· 17

2.13 Updated binding relationship between mapping table and device· 18

2.14 Delete bindings between mapping table and all devices· 19

2.15 Bound port to mapping table· 20

2.16 Update binding relationship between port and mapping table· 21

2.17 Deleted bindings between mapping table and all ports· 22

3 CON_APP· 23

3.1 Application install 23

3.2 Application start 23

3.3 Application stop· 23

3.4 Application uninstall 24

3.5 Application upload· 24

4 CON_AUTH·· 25

4.1 Added an API authentication-free IP· 25

4.2 Deleted an API authentication-free IP· 25

4.3 Add an IP address to white list 26

4.4 Delete an IP address from white list 26

5 CON_LICENSE· 27

5.1 Connect the license server 27

5.2 Disconnect the license server 27

5.3 Upload license file· 28

5.4 Update the quantity of requested licenses· 28

6 CON_LISTENER·· 29

6.1 Register Alert Topic· 29

6.2 Update Alert Topic· 29

6.3 Remove Alert Topic· 30

7 CON_NetworkMonitor 31

7.1 Change thresholds for a CPU· 32

7.2 Change thresholds for all CPUs· 34

8 CON_OAM·· 36

8.1 Create radar detection task· 36

8.2 Delete radar detection task· 37

8.3 Clear periodic radar detection tasks· 37

9 CON_OPENFLOW·· 38

9.1 Create flow table entry· 38

9.2 Modify flow table entry· 38

9.3 Delete flow table entry· 39

9.4 Delete group table entry· 40

9.5 Devices change to fail-safe mode· 40

9.6 Devices change to normal mode· 40

10 CON_REGION·· 41

10.1 Create Region· 41

10.2 Delete Region· 42

10.3 Update Region· 42

11 CON_ROUTERCONFIGS· 44

11.1 Assign an IP address to the loopback interface· 44

11.2 Delete the IP address of the loopback interface· 44

11.3 Add BGP Instance· 45

11.4 Clear BGP configuration· 45

11.5 Add BGP Network· 46

11.6 Delete BGP Network· 46

11.7 Add BGP Neighbor 47

11.8 Delete BGP Neighbor 47

11.9 Add Timer 48

11.10 Add OSPF RouterId· 49

11.11 Add OSPF Network· 49

11.12 Delete OSPF Network· 50

11.13 Clear OSPF configuration· 50

11.14 Add OSPF area· 51

11.15 Delete OSPF area· 52

12 CON_SNMP· 53

12.1 Create traditional NE· 53

12.2 Update traditional NE· 53

12.3 Delete traditional NE· 54

12.4 Start scanning traditional NE· 54

12.5 Stop scanning traditional NE· 55

13 CON_SYSTEM·· 56

13.1 Backup· 56

13.2 Upload· 56

13.3 Restore· 57

13.4 Download· 57

13.5 Modify backup settings· 58

13.6 Modify configuration· 58

13.7 Restore configuration· 59

13.8 Prepared for upgrade· 60

13.9 Modify alert log remote transmission mode· 60

13.10 Modify audit log transmission mode· 60

13.11 Enter upgrade mode· 61

13.12 Quit upgrade mode· 61

14 CON_TEAM·· 62

14.1 Create Team·· 62

14.2 Delete Team·· 63

14.3 Modify Team·· 63

14.4 Add Member 63

14.5 Delete Member 64

14.6 Modify Member 64

15 CON_TOPOLOGY· 66

15.1 Update device· 66

15.2 Update device layer 66

15.3 Delete inactive link· 67

15.4 Update port thresholds· 67

15.5 Clear events on a device· 67

15.6 Clear events on all devices· 68

16 CON_USER·· 69

16.1 Add a user 69

16.2 Deleted a user 69

16.3 Changed user password· 70

16.4 Update user config· 71

16.5 Add a role· 72

16.6 Update a role· 73

16.7 Delete a role· 74

17 Fabrics· 75

17.1 Create Fabric· 76

17.2 Update Fabric· 78

17.3 Delete Fabric· 80

17.4 Search Fabric· 81

17.5 Create Fabric Connection· 82

17.6 Update Fabric Connection· 84

17.7 Delete Fabric Connection· 86

18 FWaaS· 87

18.1 Create time range· 87

18.2 Update time range· 88

18.3 Delete time range· 89

18.4 Create firewall rule· 90

18.5 Update firewall rule· 91

18.6 Delete firewall rule· 92

18.7 Create firewall policy· 93

18.8 Update firewall policy· 94

18.9 Delete firewall policy· 95

18.10 Create firewall 96

18.11 Update firewall 98

18.12 Delete firewall 100

18.13 Create IPS policy· 100

18.14 Update IPS policy· 101

18.15 Delete IPS policy· 101

18.16 Create IPS template· 102

18.17 Update IPS template· 103

18.18 Delete IPS template· 103

18.19 Upload IPS signature library from local device· 104

18.20 Create AV policy· 105

18.21 Update AV policy· 106

18.22 Delete AV policy· 107

18.23 Create AV template· 108

18.24 Update AV template· 109

18.25 Delete AV template· 110

18.26 Upload virus library from local device· 110

18.27 Upload application library from local device· 111

18.28 Create attack defense policy· 111

18.29 Update attack defense policy· 112

18.30 Delete attack defense policy· 112

18.31 Create URL filter category· 113

18.32 Update URL filter category· 114

18.33 Delete URL filter category· 114

18.34 Create URL filter rule· 115

18.35 Update URL filter rule· 115

18.36 Delete URL filter rule· 116

18.37 Create URL filter policy· 116

18.38 Update URL filter policy· 117

18.39 Delete URL filter policy· 117

19 IDM·· 118

19.1 Add NETCONF template· 119

19.2 Update NETCONF template· 121

19.3 Delete NETCONF template· 123

19.4 Add configuration file· 124

19.5 Delete configuration file· 125

19.6 Deploy configuration snippets· 126

19.7 Deploy commands· 127

19.8 Start automatic configuration process· 128

19.9 Stop automatic configuration process· 129

19.10 Add SNMP template· 130

19.11 Delete SNMP template· 131

19.12 Update SNMP template· 132

19.13 Add aggregate interface· 134

19.14 Update aggregate interface· 135

19.15 Configure aggregate interface· 136

19.16 Add automated configuration template· 137

19.17 Add automation parameters· 140

19.18 Add automation policy· 141

19.19 Bring up interfaces· 142

19.20 Shut down interfaces· 143

19.21 Configure interface· 144

19.22 Add automatic device replacement task· 145

19.23 Add fabric and deploy resource pool 146

20 LBaaS· 148

20.1 Create load balancer 149

20.2 Update load balancer 151

20.3 Delete load balancer 153

20.4 Create VIP· 154

20.5 Update VIP· 155

20.6 Delete VIP· 156

20.7 Create listener 157

20.8 Update listener 159

20.9 Delete listener 160

20.10 Create policy· 161

20.11 Update policy· 163

20.12 Delete policy· 164

20.13 Create rule· 165

20.14 Update rule· 166

20.15 Delete rule· 167

20.16 Create pool 168

20.17 Update pool 170

20.18 Delete pool 172

20.19 Create VIP· 173

20.20 Update VIP· 175

20.21 Delete VIP· 176

20.22 Create member 177

20.23 Update member 179

20.24 Delete member 180

20.25 Create health monitor 181

20.26 Update health monitor 183

20.27 Delete health monitor 184

20.28 Bind health monitor 184

20.29 Unbind health monitor 185

21 NEM·· 186

21.1 Create VLAN-VXLAN mapping table· 186

21.2 Update VLAN-VXLAN mapping table· 187

21.3 Delete VLAN-VXLAN mapping table· 188

21.4 Create QinQ-VXLAN mapping table· 188

21.5 Update QinQ-VXLAN mapping table· 190

21.6 Delete QinQ-VXLAN mapping table· 193

21.7 Bind VLAN-VXLAN mapping table· 194

21.8 Update VLAN-VXLAN mapping table binding· 195

21.9 Delete VLAN-VXLAN mapping table binding· 196

21.10 Bind ports to VLAN-VXLAN mapping table· 197

21.11 Update bindings between ports and VLAN-VXLAN mapping table· 198

21.12 Delete bindings between ports and VLAN-VXLAN mapping table· 199

21.13 Bind ports to QinQ-VXLAN mapping table· 200

21.14 Update bindings between ports and QinQ-VXLAN mapping table· 201

21.15 Delete bindings between ports and QinQ-VXLAN mapping table· 202

21.16 Create gateway group· 203

21.17 Update gateway group· 206

21.18 Delete gateway group· 208

21.19 Create IP address pool 209

21.20 Update IP address pool 211

21.21 Delete IP address pool 213

21.22 Create gateway group VLAN range· 214

21.23 Update gateway group VLAN range· 215

21.24 Delete gateway group VLAN range· 216

21.25 Create VXLAN pool 217

21.26 Update VXLAN pool 218

21.27 Delete VXLAN pool 219

21.28 Create physical NE· 220

21.29 Update physical NE· 223

21.30 Delete physical NE· 225

21.31 Batch add physical NEs· 226

21.32 Start scanning physical NE· 226

21.33 Stop scanning physical NE· 227

21.34 Start migration on physical gateway· 227

21.35 Complete migration on physical gateway· 228

21.36 Start data synchronization on physical NE· 229

21.37 Start configuration auditing on physical NE· 230

21.38 Start data synchronization on virtual NE· 230

21.39 Start configuration auditing on virtual NE· 231

21.40 Create NETCONF default user 231

21.41 Configure default MAC address· 232

21.42 Delete default MAC address· 232

21.43 Create third party NE· 233

21.44 Delete third party NE· 235

21.45 Configure reserved option· 235

21.46 Create address pool 236

21.47 Update address pool 237

21.48 Delete address pool 238

21.49 Add resource· 238

21.50 Delete resource· 242

21.51 Configure VNFM·· 243

21.52 Configure gateway network· 244

21.53 Update gateway network· 245

21.54 Router bound to gateway· 246

21.55 Add vRouter to resource· 247

21.56 Create aggregation group member 248

21.57 Update aggregation group member 249

21.58 Delete aggregation group member 250

21.59 Create aggregation group· 251

21.60 Update aggregation group· 252

21.61 Delete aggregation group· 253

21.62 Create global aggregation group configuration· 254

21.63 Update global aggregation group configuration· 255

21.64 Delete global aggregation group configuration· 256

21.65 Delete NE VXLAN tunnels· 257

21.66 Create connection limit rule· 258

21.67 Update connection limit rule· 259

21.68 Delete connection limit rule· 260

21.69 Create device configuration template· 261

21.70 Update device configuration template· 266

21.71 Delete device configuration template· 270

21.72 Create control protocol template· 271

21.73 Update control protocol template· 273

21.74 Delete control protocol template· 274

21.75 Create deploy resource pool 275

21.76 Update deploy resource pool 277

21.77 Delete deploy resource pool 279

21.78 Create auto detected· 280

21.79 Stop auto detected· 282

21.80 Delete auto detected· 282

21.81 Update global setting· 283

21.82 Create DHCP server 284

21.83 Update DHCP server 285

21.84 Delete DHCP server 286

21.85 Upload software· 287

21.86 Update software· 289

21.87 Delete software· 290

21.88 Upgrade softeware· 291

21.89 Replace physical NE· 292

21.90 Create tenant-gateway binding relationship· 294

21.91 Update tenant-gateway binding relationship· 295

21.92 Delete tenant-gateway binding relationship· 296

21.93 Create gateway· 297

21.94 Update gateway· 299

21.95 Delete gateway· 301

21.96 Create gateway member 302

21.97 Update gateway member 304

21.98 Delete gateway member 306

21.99 Create device whitelist 307

21.100 Update device whitelist 308

21.101 Delete device whitelist 309

21.102 Delete assetlist 309

21.103 Synchronization device bridgeMac and serialNumber infor 310

22 NEYANGM·· 311

22.1 Download YANG files· 311

22.2 Get YANG files from NE· 311

22.3 Set YANG files identifier 311

23 NGFWM·· 313

23.1 Add device· 313

23.2 Update device· 314

23.3 Delete device· 314

23.4 Start data synchronization on device· 315

23.5 Start configuration audit on device· 315

23.6 Create template· 315

23.7 Delete template· 317

23.8 Create NGFW resource· 317

23.9 Update NGFW resource· 319

23.10 Delete NGFW resource· 320

23.11 Create resource pool 320

23.12 Update resource pool 321

23.13 Delete resource pool 322

23.14 Set default user 322

24 ResourceAccessTemplate· 323

24.1 Create resource access template· 324

24.2 Delete resource access template· 325

25 ServiceChain· 326

25.1 Create service chain· 327

25.2 Update service chain· 330

25.3 Delete service chain· 332

25.4 Create context 333

25.5 Update context 334

25.6 Delete context 335

26 SSLVPNaaS· 336

26.1 Create PKI domain· 337

26.2 Update PKI domain· 338

26.3 Delete PKI domain· 339

26.4 Create SSL policy· 340

26.5 Update SSL policy· 341

26.6 Delete SSL policy· 342

26.7 Create SSL VPN gateway· 343

26.8 Update SSL VPN gateway· 345

26.9 Delete SSL VPN gateway· 347

26.10 Create IP address pool 348

26.11 Update IP address pool 350

26.12 Delete IP address pool 352

26.13 Create SSL VPN context 353

26.14 Update SSL VPN context 355

26.15 Delete SSL VPN context 357

26.16 Create route list 358

26.17 Update route list 359

26.18 Delete route list 360

26.19 Create policy group· 361

26.20 Update policy group· 362

26.21 Delete policy group· 363

27 Tenant 364

27.1 Add tenant 364

27.2 Update tenant 364

27.3 Delete tenant 365

27.4 Import tenants· 366

28 TPFW·· 367

28.1 Add TPFW·· 368

28.2 Update TPFW·· 369

28.3 Delete TPFW·· 371

28.4 Create vRouter link· 372

28.5 Delete vRouter link· 373

29 VPNaaS· 374

29.1 Create IKE policy· 374

29.2 Delete IKE policy· 375

29.3 Update IKE policy· 375

29.4 Create IPsec policy· 376

29.5 Delete IPsec policy· 376

29.6 Update IPsec policy· 377

29.7 Create VPN service· 378

29.8 Delete VPN service· 379

29.9 Update VPN service· 379

29.10 Create IPsec Site Connections· 380

29.11 Delete IPsec Site Connection· 381

29.12 Update IPsec Site Connections· 382

29.13 Create IPsec site connection peer CIDR· 383

29.14 Delete IPsec site connection peer CIDR· 383

30 VSM·· 384

30.1 Create VDS· 385

30.2 Update VDS· 386

30.3 Delete VDS· 388

30.4 Add host 389

30.5 Update host 390

30.6 Delete host 391

30.7 Create vRouter 392

30.8 Update vRouter 394

30.9 Delete vRouter 396

30.10 Create internal route· 397

30.11 Delete internal route· 398

30.12 Creat interface· 399

30.13 Delete interface· 400

30.14 Create network· 401

30.15 Update network· 402

30.16 Delete network· 404

30.17 Create subnet 405

30.18 Update subnet 406

30.19 Delete subnet 408

30.20 Create network policy· 409

30.21 Update network policy· 410

30.22 Delete network policy· 411

30.23 Create security policy· 411

30.24 Update security policy· 412

30.25 Delete security policy· 412

30.26 Create floating IP· 413

30.27 Update floating IP· 415

30.28 Delete floating IP· 417

30.29 Create port group· 418

30.30 Update port group· 419

30.31 Delete port group· 419

30.32 Create security rules· 420

30.33 Update security rule· 422

30.34 Delete security rule· 423

30.35 Authenticate with vCenter 424

30.36 Disconnect with vCenter 425

30.37 Upload vib· 425

30.38 Delete vib· 426

30.39 Install VFE· 426

30.40 Update VFE· 427

30.41 Uninstall VFE· 427

30.42 Create domain· 428

30.43 Update domain· 429

30.44 Delete domain· 430

30.45 Create vPort 431

30.46 Update vPort 434

30.47 Delete vPort 436

30.48 Create router link· 437

30.49 Update router link· 438

30.50 Delete router link· 438

30.51 Create route table· 439

30.52 Update route table· 440

30.53 Delete route table· 440

30.54 Create route entry· 441

30.55 Update route entry· 442

30.56 Delete route entry· 442

30.57 Create APP cluster VIP· 443

30.58 Update APP cluster VIP· 444

30.59 Delete APP cluster VIP· 444

30.60 Create flooding domain· 445

30.61 Update flooding domain· 446

30.62 Delete flooding domain· 447

30.63 Update vCenter status· 447

30.64 Create port name prefix· 448

30.65 Delete port name prefix· 448

30.66 Update advanced setting· 449

30.67 Create netoverlay host 449

30.68 Delete netoverlay host 450

30.69 Update netoverlay host 450

30.70 Create netoverlay group· 451

30.71 Delete netoverlay group· 451

30.72 Create VLAN-VXLAN map· 452

30.73 Delete VLAN-VXLAN map· 453

30.74 Configured batch vSwitch deployment parameters· 453

30.75 Import host file· 454

30.76 Run custom script 454

30.77 Export host file· 454

30.78 Export SSH key· 455

30.79 Upload custom script 455

30.80 Installe vSwitch· 455

30.81 Update vSwitch· 456

30.82 Uninstall vSwitch· 456

30.83 Check host status· 457

30.84 Upload vSwitch file· 457

30.85 Delete vSwitch file· 457

30.86 Create network nodes· 458

30.87 Update network node· 459

30.88 Delete network node· 459

30.89 Update global default action· 460

30.90 Create DFW policy· 460

30.91 Update DFW policy· 461

30.92 Delete DFW policy· 461

30.93 Create DFW policy rule· 462

30.94 Delete DFW policy rule· 463

30.95 Create DFW IP set 464

30.96 Update DFW IP set 464

30.97 Delete DFW IP set 465

30.98 Create DFW IP set rule· 466

30.99 Delete DFW IP set rule· 467

30.100 Track flow entry of IP packet 468

30.101 Track flow entry of ARP packet 470

30.102 Start auditing on host 471

30.103 Start synchronization on host 472

30.104 Created static link· 473

30.105 Deleted static link· 473

30.106 Create vRouter interconnection· 474

30.107 Update vRouter interconnection· 475

30.108 Delete vRouter interconnection· 476

30.109 Create Layer 2 DC interconnection· 477

30.110 Update Layer 2 DC interconnection· 478

30.111 Delete Layer 2 DC interconnection· 479

30.112 Create Layer 3 DC interconnection· 480

30.113 Update Layer 3 DC interconnection· 482

30.114 Delete Layer 3 DC interconnection· 484

30.115 Add subnet to Layer 3 DC interconnection· 484

30.116 Delete Layer 3 DC interconnection subnet 485

30.117 Upload the vSwitch license file· 485

30.118 Updated host load limit 486


1 简介

操作日志记录的是用户进行的系统操作、配置更改等事件,例如应用操作(加载、启动、停止和卸载应用)、集群配置等。操作日志信息包含日志的操作描述、操作结果和失败原因等,为用户进行系统诊断和维护提供参考。

本文假设您已具备数据通信技术知识,并熟悉H3C VCFC-DC产品。

1.1  查看操作日志

单击[保障 > 日志信息]菜单项,单击“操作日志”页签,进入操作日志视图。操作日志列表将分页显示系统生成的用户操作日志信息,如1-1所示。

图1-1 操作日志信息列表

 

 

表1-1 日志字段说明

字段

描述

日期/时间

生成操作日志信息的日期和时间

用户

触发生成操作日志的用户名称

用户操作地址

执行操作时,用户所在终端的IP地址

业务名称

用户操作所属的业务模块名称

操作描述

操作日志具体内容,描述用户进行的操作事件

操作结果

用户操作的结果,成功或失败

失败原因

当用户操作失败时,将显示可能的具体失败原因

 

1.2  Syslog日志格式说明

VCFC-DC支持将操作日志通过Syslog协议发送至Syslog日志服务器。Syslog日志服务器的IP地址和端口号可以通过[系统 > 参数]页面中的“操作日志”组件设置。

缺省情况下,控制器以Syslog协议发送的操作日志信息格式如下:

<PRI>TIMESTAMP Hostname Origin/severity/Keywords CONTENT

表1-2 Syslog日志字段说明

字段

描述

<PRI>

优先级标识符,优先级的计算公式为:facility×8severity

·     facility表示Syslog定义的程序模块,目前VCFC-DC发送Syslog日志的facility一般为user-level,取值为1

·     severity表示Syslog协议定义的日志严重等级,具体说明请参见1-4

TIMESTAMP

时间戳记录了日志信息产生的时间,方便用户查看和定位操作事件

Hostname

生成该日志信息的控制器所在服务器或虚拟机的名称或IP地址

Origin

生成该操作日志信息的业务模块的名称

severity

VCFC-DC定义的操作日志信息的等级,具体说明请参见1-5,该等级与Syslog协议定义的日志严重等级之间的对应关系如1-6所示

Keywords

关键字,本字段为该日志信息的概述,用于搜索或助记

CONTENT

该日志的具体内容,格式如下:

User=用户名 IP=用户操作地址 Description=操作描述 Result=操作结果 Cause=失败原因

 

1-3列出了可能生成操作日志信息的业务模块。

表1-3 业务模块列表

业务模块名称

说明

BSM

裸金属模块

CON_APP

应用管理模块

CON_AUTH

认证管理模块

CON_LICENSE

License管理模块

CON_LISTENER

监听器模块

CON_NetworkMonitor

网络健康监控模块

CON_OAM

OAM模块

CON_OPENFLOW

OpenFlow模块

CON_REGION

Region模块

CON_ROUTERCONFIGS

路由配置模块

CON_SNMP

SNMP模块

CON_SYSTEM

系统管理模块

CON_TEAM

集群模块

CON_TOPOLOGY

拓扑管理模块

CON_USER

用户管理模块

Fabric

Fabric模块

FWaaS

防火墙服务模块

IDM

综合部署模块

LBaaS

负载均衡服务模块

NEM

承载网络模块

NEYANGM

网元YANG Manager模块

NGFWM

NGFW Manager模块

ResourceAccessTemplate

资源接入模板模块

ServiceChain

服务链模块

SSLVPNaaS

SSL VPN服务模块

Tenant

租户管理模块

TPFW

第三方防火墙模块

VPNaaS

IPsec VPN服务模块

VSM

虚拟网络模块

 

Syslog协议定义的日志严重等级如1-4所示,各等级的严重性依照数值从07依次降低。

表1-4 Syslog日志严重等级说明

级别

严重等级

描述

0

Emergency

表示紧急信息,可能导致系统不可用

1

Alert

表示必须立即修复的状态

2

Critical

表示严重信息

3

Error

表示错误信息

4

Warning

表示警告信息

5

Notice

表示正常出现但是重要的信息

6

Informational

表示需要记录的通知信息

7

Debug

表示调试过程产生的信息

 

VCFC-DC定义的操作日志信息的等级如1-5所示。

表1-5 控制器操作日志等级说明

级别

严重等级

描述

0

Info

操作成功时,操作日志信息的级别为Info,表示该日志为需要记录的通知信息

1

Warning

操作失败时,操作日志信息的级别为Warning,表示该日志为警告信息

 

VCFC-DC定义的操作日志信息的等级与Syslog协议定义的日志严重等级之间的对应关系如1-6所示。

表1-6 日志等级对应关系

VCFC-DC定义的操作日志信息等级

Syslog协议定义的日志严重等级

0

6

1

4

 

1.3  文档使用说明

本文将操作日志信息按照业务模块分类,以表格的形式对日志信息进行介绍。有关表中各项的含义请参考1-7

表1-7 日志信息表内容说明

表项

说明

举例

关键字

日志信息的概述,用于搜索或助记

UPLOAD_APP_OP

日志内容

显示日志信息的具体内容

Uploaded application: $1.

参数解释

按照参数在日志中出现的顺序对参数进行解释

参数顺序用“$数字”表示,例如“$1”表示在该日志中出现的第一个参数

$1:应用的安装包名称

举例

日志信息举例

Uploaded application: arp-2156.zip.

日志说明

描述日志所表达的操作事件

用户进行了上传应用的操作

失败原因

列举操作失败时可能的原因

当操作失败时,可能的原因如下:

·     Unsigned or untrusted jars contained withinJAR包签名失败或应用程序包含不信任的JAR

·     The application already exists相同名称的应用程序已存在

 


2 BSM

本节介绍裸金属管理模块输出的操作日志信息。

2.1  Create mapping table of access network

关键字

CREATE_BSM_ACCESS_NETWORK_OP

日志内容

Created a VLAN-VXLAN mapping table for the access network: $1.

参数解释

$1:裸金属接入端网络的映射表配置信息

举例

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]

].

日志说明

用户创建了裸金属接入端网络的映射表

失败原因

当操作失败时,可能的原因如下:

·     Invalid JSON format:无效的JSON格式

·     Internal server error:内部错误

·     Please perform the operation on the active leader:请在主Leader上进行操作

·     Configuration recovery is in progress:配置正在恢复过程中

·     Invalid mapping table name:无效的映射表名称

·     The VLAN ID is invalid or out of rangeVLAN值无效或超出范围

·     The VXLAN ID is invalid or out of rangeVXLAN值无效或超出范围

·     The mapping table already exists:映射表已存在

 

2.2  Update mapping table of access network

关键字

UPDATE_BSM_ACCESS_NETWORK_OP

日志内容

Updated a VLAN-VXLAN mapping table of the access network: $1.

参数解释

$1:裸金属接入端网络的映射表配置信息

举例

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]

].

日志说明

用户修改了裸金属接入端网络的映射表

失败原因

当操作失败时,可能的原因如下:

·     Invalid JSON format:无效的JSON格式

·     Internal server error:内部错误

·     Please perform the operation on the active leader:请在主Leader上进行操作

·     Configuration recovery is in progress:配置正在恢复过程中

·     The mapping table does not exist:映射表不存在

·     Invalid mapping table name:无效的映射表名称

·     The VLAN ID is invalid or out of rangeVLAN值无效或超出范围

·     The VXLAN ID is invalid or out of rangeVXLAN值无效或超出范围

·     The reserved VLAN ID conflicts with a VLAN ID of an VLAN-VXLAN mapping:存储VLANVLAN-VXLAN映射冲突

 

2.3  Delete mapping table of access network

关键字

DELETE_BSM_ACCESS_NETWORK_OP

日志内容

Deleted a VLAN-VXLAN mapping table from the access network: $1.

参数解释

$1:裸金属接入端网络的映射表ID

举例

Deleted a VLAN-VXLAN mapping table from the access network: 3a24b5b8-8fd1-492d-b867-88976c198d17.

日志说明

用户删除了裸金属接入端网络的映射表

失败原因

当操作失败时,可能的原因如下:

·     Invalid JSON format:无效的JSON格式

·     Internal server error:内部错误

·     Please perform the operation on the active leader:请在主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:该映射表已绑定接口

 

2.4  Modify inspection port status

关键字

MODIFY_BSM_INSPECT_STATUS_OP

日志内容

Modified states of inspection network interfaces: $1.

参数解释

$1Inspection网络端口的状态信息

举例

Modified states of inspection network interfaces:

Port_status: [INACTIVE]

Port_list: [

Device_type: [DEVICE_NAME], device_value: [TOR1], port_name: [GigabitEthernet1/0/1]

].

日志说明

用户修改了Inspection网络端口的状态

失败原因

当操作失败时,可能的原因如下:

·     Invalid JSON format:无效的JSON格式

·     Internal server error:内部错误

·     Please perform the operation on the active leader:请在主Leader上进行操作

·     Configuration recovery is in progress:配置正在恢复过程中

·     Invalid interface list:无效的接口列表

·     Invalid interface names exist:存在无效的接口名称

·     Nonexistent devices are specified:设备不存在

·     Invalid device MAC addresses exist:无效的设备MAC地址

·     Invalid device names exist:存在无效的设备名称

·     Non-VTEP interfaces exist:存在非VTEP接口

·     Interfaces not bound to the inspection network exist:接口未绑定在Inspection网络上

·     Interfaces bound to non-inspection networks exist:接口已被绑定在非Inspection网络上

 

2.5  Bound working port to mapping table

关键字

CREATE_BSM_WORK_PORTBIND_OP

日志内容

Bound working network interfaces to a VLAN-VXLAN mapping table: $1.

参数解释

$1Working网络端口的绑定信息

举例

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]

]

].

日志说明

用户增加了Working网络端口的绑定关系

失败原因

当操作失败时,可能的原因如下:

·     Invalid JSON format:无效的JSON格式

·     Internal server error:内部错误

·     Please perform the operation on the active leader:请在主Leader上进行操作

·     Configuration recovery is in progress:配置正在恢复过程中

·     The VLAN ID is invalid or out of rangeVLAN值无效或超出范围

·     The VXLAN ID is invalid or out of rangeVXLAN值无效或超出范围

·     Invalid interface list:无效的接口列表

·     Invalid interface names exist:存在无效的接口名称

·     Nonexistent devices are specified:设备不存在

·     Invalid device MAC addresses exist:存在无效的设备MAC地址

·     Invalid device names exist:存在无效的设备名称

·     The default access VLAN does not exist:默认接入VLAN不存在

·     Invalid interface list:无效的接口列表

·     Non-VTEP interfaces exist:存在非VTEP接口

·     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:接口已被绑定在Inspection网络上

 

2.6  Unbound working port to mapping table

关键字

DELETE_BSM_WORK_PORTBIND_OP

日志内容

Unbound working network interfaces from a VLAN-VXLAN mapping table: $1.

参数解释

$1Working网络端口的绑定信息

举例

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]

]

].

日志说明

用户删除了working网络端口的绑定关系

失败原因

当操作失败时,可能的原因如下:

·     Invalid JSON format:无效的JSON格式

·     Internal server error:内部错误

·     Please perform the operation on the active leader:请在主Leader上进行操作

·     Configuration recovery is in progress:配置正在恢复过程中

·     The VLAN ID is invalid or out of rangeVLAN值无效或超出范围

·     The VXLAN ID is invalid or out of rangeVXLAN值无效或超出范围

·     Invalid interface list:无效的接口列表

·     Invalid interface names exist:无效的接口名称

·     Nonexistent devices are specified:设备不存在

·     Invalid device MAC addresses exist:无效的设备MAC地址

·     Invalid device names exist:无效的设备名称

·     The default access VLAN does not exist:默认接入VLAN不存在

·     Invalid interface list:无效的接口列表

·     Duplicate interfaces exist:存在重复的接口

·     The mapping table does not exist:映射表不存在

·     Interfaces not bound to the working network exist:接口未绑定在Working网络上

·     Interfaces not bound to the VLAN-VXLAN mapping table exist:接口绑定不存在

·     Non-VTEP interfaces exist:存在非VTEP接口

·     Duplicate interfaces exist:存在重复的接口

·     The mapping table has been bound to devices:该映射表已绑定设备

·     The mapping table has been bound to interfaces:该映射表已绑定接口

 

2.7  Add default access VLAN

关键字

CREATE_BSM_WORKING_VLAN_OP

日志内容

Added a default access VLAN for the working network: $1.

参数解释

$1:默认接入VLAN

举例

Added a default access VLAN for the working network: VLAN: [100].

日志说明

用户进行了配置Working网络的默认接入VLAN的操作

失败原因

当操作失败时,可能的原因如下:

·     Invalid JSON format:无效的JSON格式

·     Internal server error:内部错误

·     Please perform the operation on the active leader:请在主Leader上进行操作

·     Configuration recovery is in progress:配置正在恢复过程中

·     The VLAN ID is invalid or out of rangeVLAN值无效或超出范围

·     The working network has been configured with a default access VLAN:默认接入VLAN已存在

 

2.8  Delete default access VLAN

关键字

DELETE_BSM_WORKING_VLAN_OP

日志内容

Deleted the default access VLAN from the working network.

参数解释

举例

Deleted the default access VLAN from the working network.

日志说明

用户进行了删除Working网络的默认接入VLAN的操作

失败原因

当操作失败时,可能的原因如下:

·     Invalid JSON format:无效的JSON格式

·     Internal server error:内部错误

·     Please perform the operation on the active leader:请在主Leader上进行操作

·     Configuration recovery is in progress:配置正在恢复过程中

·     The default access VLAN does not exist:默认接入VLAN不存在

·     The default access VLAN is being used:默认接入VLAN已被占用

 

2.9  Create mapping table of service network

关键字

CREATE_BSM_VLAN_DOMAIN_OP

日志内容

Created a VLAN-VXLAN mapping table for the service network: $1.

参数解释

$1:裸金属服务端的映射表配置信息

举例

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]

].

日志说明

用户创建了裸金属服务端的映射表

失败原因

当操作失败时,可能的原因如下:

·     Invalid JSON format:无效的JSON格式

·     Internal server error:内部错误

·     Please perform the operation on the active leader:请在主Leader上进行操作

·     Configuration recovery is in progress:配置正在恢复过程中

·     Invalid mapping table name:无效的映射表名称

·     The VLAN ID is invalid or out of rangeVLAN值无效或超出范围

·     The VXLAN ID is invalid or out of rangeVXLAN值无效或超出范围

·     Overlapping mappings exist:映射关系存在重叠

·     The mapping table already exists:映射表已存在

 

2.10  Update mapping table of service network

关键字

UPDATE_BSM_VLAN_DOMAIN_OP

日志内容

Updated a VLAN-VXLAN mapping table of the service network: $1.

参数解释

$1:裸金属服务端的映射表配置信息

举例

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]

].

日志说明

用户修改了裸金属服务端的映射表

失败原因

当操作失败时,可能的原因如下:

·     Invalid JSON format:无效的JSON格式

·     Internal server error:内部错误

·     Please perform the operation on the active leader:请在主Leader上进行操作

·     Configuration recovery is in progress:配置正在恢复过程中

·     The mapping table does not exist:映射表不存在

·     Invalid mapping table name:无效的映射表名称

·     The VLAN ID is invalid or out of rangeVLAN值无效或超出范围

·     The VXLAN ID is invalid or out of rangeVXLAN值无效或超出范围

·     Overlapping mappings exist:映射关系存在重叠

·     The reserved VLAN ID conflicts with a VLAN ID of an VLAN-VXLAN mapping:存储VLANVLAN-VXLAN映射冲突

 

2.11  Delete mapping table of service network

关键字

DELETE_BSM_VLAN_DOMAIN_OP

日志内容

Deleted a VLAN-VXLAN mapping table from the service network: $1.

参数解释

$1:裸金属服务端的映射表ID

举例

Deleted a VLAN-VXLAN mapping table from the service network: 5473e36e-5b34-4e9d-9d20-206310d1d478.

日志说明

用户删除了裸金属服务端的映射表

失败原因

当操作失败时,可能的原因如下:

·     Invalid JSON format:无效的JSON格式

·     Internal server error:内部错误

·     Please perform the operation on the active leader:请在主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:该映射表已绑定接口

 

2.12  Bound mapping table to device

关键字

CREATE_BSM_VLAN_DOMAIN_BIND_OP

日志内容

Bound devices to a VLAN-VXLAN mapping table: $1.

参数解释

$1VLAN-VXLAN映射表与设备绑定信息

举例

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]

].

日志说明

用户进行了VLAN-VXLAN映射表与设备绑定的操作

失败原因

当操作失败时,可能的原因如下:

·     Invalid JSON format:无效的JSON格式

·     Internal server error:内部错误

·     Please perform the operation on the active leader:请在主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:指定设备下的接口已被QinQ-VXLAN映射表绑定

·     The reserved VLAN ID conflicts with a VLAN ID of an VLAN-VXLAN mapping:存储VLANVLAN-VXLAN映射冲突

 

2.13  Updated binding relationship between mapping table and device

关键字

UPDATE_BSM_VLAN_DOMAIN_BIND_OP

日志内容

Updated binding relationships between a VLAN-VXLAN mapping table and devices: $1.

参数解释

$1VLAN-VXLAN映射表与设备绑定信息

举例

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]

].

日志说明

用户进行了修改VLAN-VXLAN映射表与设备绑定的操作

失败原因

当操作失败时,可能的原因如下:

·     Invalid JSON format:无效的JSON格式

·     Internal server error:内部错误

·     Please perform the operation on the active leader:请在主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:指定设备下的接口已被QinQ-VXLAN映射表绑定

·     The reserved VLAN ID conflicts with a VLAN ID of an VLAN-VXLAN mapping:存储VLANVLAN-VXLAN映射冲突

 

2.14  Delete bindings between mapping table and all devices

关键字

DELETE_BSM_VLAN_DOMAIN_BIND_OP

日志内容

Deleted binding relationships between a VLAN-VXLAN mapping table and all devices: $1.

参数解释

$1VLAN-VXLAN映射表ID

举例

Deleted binding relationships between a VLAN-VXLAN mapping table and all devices: 29577831-31d1-46e7-a33a-40f6ae6f4179.

日志说明

用户进行了删除VLAN-VXLAN映射表与所有设备的绑定关系的操作

失败原因

当操作失败时,可能的原因如下:

·     Invalid JSON format:无效的JSON格式

·     Internal server error:内部错误

·     Please perform the operation on the active leader:请在主Leader上进行操作

·     Configuration recovery is in progress:配置正在恢复过程中

·     Devices already unbound from the mapping table exist:该绑定关系不存在

·     The mapping table does not exist:映射表不存在

 

2.15  Bound port to mapping table

关键字

CREATE_BSM_PORT_VLAN_DOMAIN_BIND_OP

日志内容

Bound interfaces to a VLAN-VXLAN mapping table: $1.

参数解释

$1VLAN-VXLAN映射表与接口绑定信息

举例

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]

].

日志说明

用户进行了把VLAN-VXLAN映射表与接口绑定的操作

失败原因

当操作失败时,可能的原因如下:

·     Invalid JSON format:无效的JSON格式

·     Internal server error:内部错误

·     Please perform the operation on the active leader:请在主Leader上进行操作

·     Configuration recovery is in progress:配置正在恢复过程中

·     Invalid interface list:无效的接口列表

·     Invalid interface names exist:无效的接口名称

·     Nonexistent devices are specified:设备不存在

·     Invalid device MAC addresses exist:无效的设备MAC地址

·     Invalid device names exist:无效的设备名称

·     The VLAN ID is invalid or out of rangeVLAN值无效或超出范围

·     Interfaces already bound to the mapping table exist:接口绑定已存在

·     Duplicate interfaces exist:存在重复的接口

·     Non-VTEP interfaces exist:存在非VTEP接口

·     Interfaces bound to the inspection network exist:接口已被绑定在Inspection网络上:

·     Interfaces bound to other mapping tables exist:接口已被绑定

·     The mapping table does not exist:映射表不存在

·     The reserved VLAN ID conflicts with a VLAN ID of an VLAN-VXLAN mapping:存储VLANVLAN-VXLAN映射冲突

 

2.16  Update binding relationship between port and mapping table

关键字

UPDATE_BSM_PORT_VLAN_DOMAIN_BIND_OP

日志内容

Updated binding relationships between interfaces and a VLAN-VXLAN mapping table: $1.

参数解释

$1VLAN-VXLAN映射表与接口绑定信息

举例

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]

].

日志说明

用户进行了修改VLAN-VXLAN映射表与接口绑定的操作

失败原因

当操作失败时,可能的原因如下:

·     Invalid JSON format:无效的JSON格式

·     Internal server error:内部错误

·     Please perform the operation on the active leader:请在主Leader上进行操作

·     Configuration recovery is in progress:配置正在恢复过程中

·     Invalid interface list:无效的接口列表

·     Invalid interface names exist:无效的接口名称

·     Nonexistent devices are specified:设备不存在

·     Invalid device MAC addresses exist:无效的设备MAC地址

·     Invalid device names exist:无效的设备名称

·     The VLAN ID is invalid or out of rangeVLAN值无效或超出范围

·     Interfaces not bound to the mapping table exist:接口绑定不存在

·     Duplicate interfaces exist:存在重复的接口

·     Non-VTEP interfaces exist:存在非VTEP接口

·     Interfaces bound to the inspection network exist:接口已被绑定在Inspection网络上:

·     Interfaces bound to other mapping tables exist:接口已被绑定

·     The mapping table does not exist:映射表不存在

·     The reserved VLAN ID conflicts with a VLAN ID of an VLAN-VXLAN mapping:存储VLANVLAN-VXLAN映射冲突

 

2.17  Deleted bindings between mapping table and all ports

关键字

DELETE_BSM_PORT_VLAN_DOMAIN_BIND_OP

日志内容

Deleted binding relationships between a VLAN-VXLAN mapping table and all interfaces: $1.

参数解释

$1VLAN-VXLAN映射表ID

举例

Deleted binding relationships between a VLAN-VXLAN mapping table and all interfaces: 29577831-31d1-46e7-a33a-40f6ae6f4179.

日志说明

用户进行了删除VLAN-VXLAN映射表与所有接口的绑定关系的操作

失败原因

当操作失败时,可能的原因如下:

·     Invalid JSON format:无效的JSON格式

·     Internal server error:内部错误

·     Please perform the operation on the active leader:请在主Leader上进行操作

·     Configuration recovery is in progress:配置正在恢复过程中

·     Interfaces already unbound from the mapping table exist:接口绑定不存在

·     The mapping table does not exist:映射表不存在

 


3 CON_APP

本节介绍应用管理模块输出的操作日志信息。

3.1  Application install

关键字

INSTALL_APP_OP

日志内容

$1 had been installed.

参数解释

$1:应用名称

举例

H3C VCFC ARP had been installed.

日志说明

用户进行了加载应用的操作

失败原因

 

3.2  Application start

关键字

START_APP_OP

日志内容

$1 had been started.

参数解释

$1:应用名称

举例

H3C VCFC ARP had been started.

日志说明

用户进行了启动应用的操作

失败原因

 

3.3  Application stop

关键字

STOP_APP_OP

日志内容

$1 had been stopped.

参数解释

$1:应用名称

举例

H3C VCFC ARP had been stopped.

日志说明

用户进行了停止应用的操作

失败原因

 

3.4  Application uninstall

关键字

REMOVE_APP_OP

日志内容

$1 had been removed.

参数解释

$1:应用名称

举例

H3C VCFC ARP had been removed.

日志说明

用户进行了卸载应用的操作

失败原因

 

3.5  Application upload

关键字

UPLOAD_APP_OP

日志内容

Uploaded application: $1.

参数解释

$1:应用的安装包名称

举例

Uploaded application: arp-2156.zip.

日志说明

用户进行了上传应用的操作

失败原因

当操作失败时,可能的原因如下:

·     Unsigned or untrusted jars contained withinJAR包签名失败或应用程序包含不信任的JAR

·     Bad application package用户上传的应用程序安装包存在错误

·     The number of applications exceeded the license limit:安装的应用程序数量超过License的最大授权数

·     The application already exists相同名称的应用程序已存在

·     An unknown error occurs during the application package uploading process:应用程序安装包上传过程中出现未知错误

 


4 CON_AUTH

本节介绍认证管理模块输出的操作日志信息。

4.1  Added an API authentication-free IP

关键字

ADD_API_AUTH_FREEIP_OP

日志内容

Added an API authentication-free IP: $1

参数解释

$1:免认证用户

举例

Added an API authentication-free IP: 192.168.56.13

日志说明

用户进行了增加免认证用户的操作

失败原因

当操作失败时,可能的原因如下:

·     Invalid IP address:输入的IP地址错误

·     The IP address already exists:该IP地址已存在

·     The controller is not the active leader:该控制器不是主Leader

·     Unknown error:未知错误

·     Invalid role:输入的角色错误

·     Invalid type:输入的认证类型错误

·     Invalid description:输入的描述信息错误

 

4.2  Deleted an API authentication-free IP

关键字

DELETE_API_AUTH_FREEIP_OP

日志内容

Deleted an API authentication-free IP: $1

参数解释

$1:免认证用户

举例

Deleted an API authentication-free IP: 192.168.56.13

日志说明

用户进行了删除免认证用户的操作

失败原因

当操作失败时,可能的原因如下:

·     The controller is not the active leader:该控制器不是主Leader

·     Unknown error:未知错误

·     Invalid IP address:输入的IP地址错误

·     Invalid type:输入的认证类型错误

·     The IP address does not exist:该IP地址不存在

 

4.3  Add an IP address to white list

关键字

ADD_IP_TO_WHITELIST_OP

日志内容

Added IP address $1 to the white list.

参数解释

$1:需加入登录白名单的IP地址

举例

Added IP address 192.168.56.13 to the white list.

日志说明

用户进行了增加登录白名单用户的操作

失败原因

当操作失败时,可能的原因如下:

·     Invalid IP address:输入的IP地址错误

·     The IP address already exists:该IP地址已存在

·     The controller is not the active leader:该控制器不是主Leader

·     Unknown error:未知错误

·     Invalid type:输入的认证类型错误

·     Invalid description:输入的描述信息错误

 

4.4  Delete an IP address from white list

关键字

DELETE_IP_FROM_WHITELIST_OP

日志内容

Deleted IP address $1 from the white list.

参数解释

$1:需从登录白名单中删除的IP地址

举例

Deleted IP address 192.168.56.13 from the white list.

日志说明

用户进行了删除登录白名单用户的操作

失败原因

当操作失败时,可能的原因如下:

·     Invalid IP address:输入的IP地址错误

·     The controller is not the active leader:该控制器不是主Leader

·     The IP address does not exist:该IP地址不存在

·     Unknown error:未知错误

·     Invalid type:输入的认证类型错误

 


5 CON_LICENSE

本节介绍License管理模块输出的操作日志信息。

5.1  Connect the license server

关键字

CONNECT_LICS_OP

日志内容

Connected the license server: $1

参数解释

$1License server配置信息

举例

Connected the license server:

License server IP: 192.168.40.40

Port: 5555

Username: sdn

Password: ******

日志说明

用户进行了连接License server的操作

失败原因

当操作失败时,可能的原因如下:

·     Incorrect license server IP address or port number:指定License serverIP地址或端口号错误

·     Incorrect username or password:用户名或密码错误

 

5.2  Disconnect the license server

关键字

DISCONNECT_LICS_OP

日志内容

Disconnected the license server: $1

参数解释

$1License serverIP地址

举例

Disconnected the license server: 192.168.1.1

日志说明

用户进行了断开与License server连接的操作

失败原因

 

5.3  Upload license file

关键字

UPLOAD_LICENSE_FILE_OP

日志内容

Uploaded license file

参数解释

举例

Uploaded license file

日志说明

用户进行了上传License文件的操作

失败原因

License file error:上传的License文件错误

 

5.4  Update the quantity of requested licenses

关键字

UPDATE_REQUESTED_LICENSES_OP

日志内容

Updated the quantity of requested licenses: $1.

参数解释

$1License申请数量信息

举例

Updated the quantity of requested licenses:

APP license: 1

MaxNodeNum license: 1

VirtualServiceNode license: 1

vSwitch license: 0

ZTP license: true

API license: true

Overlay license: true

OverlayHardwareEntity license: 1

ServiceChain license: true

Base license: 1.

日志说明

用户进行了更新License申请数量的操作

失败原因

Failed to save the configuration:配置保存失败

 

 


6 CON_LISTENER

本节介绍监听器模块输出的操作日志信息。

6.1  Register Alert Topic

关键字

REGISTER_ LISTENER_OP

日志内容

Registered alert topic listener: $1.

参数解释

$1:监听器配置信息

举例

Registered alert topic listener:

{

    "alert":

    {

        "url": "http://192.168.16.2/vnetcontroller/alter",

        "level": "warn",

        "subject": ["tunnel", "session"],

        "app_name": "vnetcontroller",

        "push_history": true

    }

}

日志说明

用户进行了注册监听器的操作

失败原因

当操作失败时,可能的原因如下:

A listener with the same app_name has already been registered:指定名称的监听器已经存在。

 

6.2  Update Alert Topic

关键字

UPDATE_LISTENER_OP

日志内容

Updated alert topic listener: $1.

参数解释

$1:监听器配置信息

举例

Updated alert topic listener:

{

    "alert":

    {

        "app_name": "vnetcontroller",

        "level": "warn",

        "subject": ["tunnel", "session"]

    }

}

日志说明

用户进行了修改监听器的操作

失败原因

 

6.3  Remove Alert Topic

关键字

REMOVE_LISTENER_OP

日志内容

Removed alert topic listener: $1.

参数解释

$1:监听器名称

举例

Removed alert topic listener: vnetcontroller

日志说明

用户进行了删除监听器的操作

失败原因

 


7 CON_NetworkMonitor

本节介绍网络健康监控模块输出的操作日志信息。

7.1  Change thresholds for a CPU

关键字

CHANGE_THRESHOLDS_OP

日志内容

Changed network monitor thresholds for CPU $1 in slot $2 of chassis $3 on device $4: $5

参数解释

$1:设备的CPU ID

$2:设备的槽位号

$3:设备的机框号

$4:设备的IP地址

$5:设备的阈值信息

举例

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

  }

日志说明

用户进行了修改设备指定告警阈值的操作

失败原因

当操作失败时,可能的原因如下:

·     The controller is not the active leader: 该控制器不是主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:该设备暂不支持配置CPU使用率门限

·     The device does not support configuring memory usage threshold:该设备暂不支持配置内存使用率门限

·     The device does not support configuring ACL resource usage threshold:该设备暂不支持配置ACL使用率门限

·     The device does not support configuring AC resource usage threshold:该设备暂不支持配置AC使用率门限

·     The device does not support configuring VSI interface resource usage threshold:该设备暂不支持配置VSI接口使用率门限

·     The device does not support configuring VLAN interface resource usage threshold:该设备暂不支持配置VLAN接口使用率门限

 

7.2  Change thresholds for all CPUs

关键字

CHANGE_THRESHOLDS_ALL_OP

日志内容

Changed network monitor thresholds for all CPUs on device $1: $2

参数解释

$1:设备的IP地址

$2:设备的阈值信息

举例

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

  }

日志说明

用户进行了修改设备所有告警阈值的操作

失败原因

当操作失败时,可能的原因如下:

·     The controller is not the active leader: 该控制器不是主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:该设备暂不支持配置CPU使用率门限

·     The device does not support configuring memory usage threshold:该设备暂不支持配置内存使用率门限

·     The device does not support configuring ACL resource usage threshold:该设备暂不支持配置ACL使用率门限

·     The device does not support configuring AC resource usage threshold:该设备暂不支持配置AC使用率门限

·     The device does not support configuring VSI interface resource usage threshold:该设备暂不支持配置VSI接口使用率门限

·     The device does not support configuring VLAN interface resource usage threshold:该设备暂不支持配置VLAN接口使用率门限

 


8 CON_OAM

本节介绍OAM模块输出的操作日志信息。

8.1  Create radar detection task

关键字

CREATE_RADAR_DETECTION_OP

日志内容

Created radar detection task: $1

参数解释

$1:雷达探测任务的参数信息

举例

Created radar detection task:

  Username: sdn

  Task type: multiple

  Task info:

  Path type: single

  Network type: vxlan

  Segment ID: 2

  Source IP: 70.68.68.68

  Source port: 10000

  Start device IP: 192.168.70.68

  Start device ingress port: 0x1

  Destination IP: 168.168.1.2

  Destination port: 50000

  End device IP: null

  DSCP: 62

  Interval: 0

  Packet count: 1

  Timeout: 10

  Period: 1440

  Frequency: 600

日志说明

用户进行了创建指定雷达探测任务的操作

失败原因

当操作失败时,可能的原因如下:

·     The start device IP address doesn't exist:起始探测设备IP不存在

·     Task already exists. Please try again later:该探测任务正在进行,请稍后重试

·     The controller hasn't obtained start device port information:控制器上未获取到起始探测设备的任何接口信息

·     The start device ingress port doesn't exist:起始探测设备入接口不存在

·     The destination IP address doesn't exist:目的IP地址不存在。

·     The gateway device that source device belongs to doesn't exist:源设备所在的物理网关设备不存在

·     The controller is not the active leader该控制器不是主Leader

·     Can't find the vPort with the source IP address:源IP地址对应的虚拟端口不存在

·     The number of periodic detection tasks has reached the maximum:持续探测任务的数量已达最大值

·     Radar detection is disabled:雷达探测功能未开启

·     The number of periodic radar detection tasks has reached the upper limit:持续探测任务总数已达上限

 

8.2  Delete radar detection task

关键字

Delete_RADAR_DETECTION_OP

日志内容

Deleted radar detection task: $1

参数解释

$1:雷达探测任务的UUID

举例

Deleted radar detection task: 218b5f2f-e435-4365-a1ab-0eaa03b7fa19

日志说明

用户进行了删除指定雷达持续探测任务的操作

失败原因

当操作失败时,可能的原因如下:

·     The controller is not the active leader该控制器不是主Leader

·     Radar detection is disabled:雷达探测功能未开启

·     The periodic scanning task ID doesn’t match the username of the task creator:用户名和持续探测任务的ID不匹配

 

8.3  Clear periodic radar detection tasks

关键字

CLEAR_RADAR_DETECTION_OP

日志内容

Clear all periodic radar detection tasks for user $1.

参数解释

$1:用户名

举例

Clear all periodic radar detection tasks for user sdn.

日志说明

用户进行了清空该用户的所有雷达持续探测任务的操作

失败原因

当操作失败时,可能的原因如下:

·     The controller is not the active leader该控制器不是主Leader

·     Radar detection is disabled:雷达探测功能未开启

 


9 CON_OPENFLOW

本节介绍OpenFlow模块输出的操作日志信息。

9.1  Create flow table entry

关键字

CREATE_FLOWTABLE_OP

日志内容

A flow table entry was added

参数解释

举例

A flow table entry was added

日志说明

用户进行了添加流表项的操作

失败原因

 

9.2  Modify flow table entry

关键字

MODIFY_FLOWTABLE_OP

日志内容

A flow table entry was modified

参数解释

举例

A flow table entry was modified

日志说明

用户进行了修改流表项的操作

失败原因

 

9.3  Delete flow table entry

关键字

DELETE_FLOWTABLE_OP

日志内容

A flow table entry was deleted on device $1: $2

参数解释

$1:设备IP地址

$2:流表信息

举例

A flow table entry was deleted on device 192.168.133.68: {

  "flow": {

    "table_id": 1,

    "duration_sec": 7,

    "duration_nsec": 4294967295,

    "priority": 61000,

    "idle_timeout": 0,

    "hard_timeout": 0,

    "cookie": "0x2c324757415057",

    "packet_count": 24,

    "byte_count": 0,

    "match": [

      {"eth_type": "ipv4"},

      {"ip_proto": "udp"},

      {"udp_src": 67},

      {"udp_dst": 68}],

      "flow_mod_flags":

         ["send_flow_rem"],

        "instructions": null,

        "flow_mod_cmd": "delete_strict"

      ]

  }

}

日志说明

用户进行了删除流表项的操作

失败原因

当操作失败时,可能的原因如下:

No such device: Datapath IDOpenFlow网络设备已断开

 

9.4  Delete group table entry

关键字

DELETE_GROUPTABLE_OP

日志内容

A group table entry was deleted on device $1: $2

参数解释

$1:设备IP地址

$2:组表ID信息

举例

A group table entry was deleted on device 192.168.133.68: {“group_id: 3”}

日志说明

用户进行了删除组表的操作

失败原因

 

9.5  Devices change to fail-safe mode

关键字

CHANGE_DEVICE_FAILSAFE_OP

日志内容

Devices changed to fail-safe mode. All controllers in the team are disallowed to accept OpenFlow connection requests.

参数解释

举例

Devices changed to fail-safe mode. All controllers in the team are disallowed to accept OpenFlow connection requests.

日志说明

用户进行了一键逃生的操作

失败原因

当操作失败时,可能的原因如下:

Abnormal connections between the active leader and other controllers in the team:集群内主Leader控制器与其他控制器连接异常

 

9.6  Devices change to normal mode

关键字

CHANGE_DEVICE_NORMAL_OP

日志内容

Devices changed to normal mode. All controllers in the team are allowed to accept OpenFlow connection requests.

参数解释

举例

Devices changed to normal mode. All controllers in the team are allowed to accept OpenFlow connection requests.

日志说明

用户进行了一键恢复的操作

失败原因

当操作失败时,可能的原因如下:

Abnormal connections between the active leader and other controllers in the team:集群内主Leader控制器与其他控制器连接异常

 


10 CON_REGION

本节介绍Region模块输出的操作日志信息。

10.1  Create Region

关键字

CREATE_REGION_ OP

日志内容

Created region: $1

参数解释

$1Region配置信息

举例

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

日志说明

用户进行了创建Region的操作

失败原因

当操作失败时,可能的原因如下:

·     The team doesn't existTeam创建

·     Incorrect controller IP addressRegion内控制器的IP地址不正确

·     The region name is already used:指定的Region名称已存在

·     The controller was already in a region:控制器已经属于某一Region,不能属于其它Region

·     The controller is not the active leader该控制器不是主Leader

·     Incorrect JSON formatRequest请求中JSON串格式不正确

·     The request can't be nullRequest请求为空

·     Incorrect controller name:控制器名称不正确

·     The master IP address must be different from the subordinate IP addressRegion控制器IP地址和备用控制器IP地址相同

·     Incorrect IP address or mask format for the managed node subnets管理设备网段的IP地址或掩码格式错误

 

10.2  Delete Region

关键字

DELETE_REGION_OP

日志内容

Deleted region:$1

参数解释

$1Region配置信息

举例

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

日志说明

用户进行了删除Region的操作

失败原因

当操作失败时,可能的原因如下:

·     The controller is not the active leader该控制器不是主Leader

·     Incorrect JSON formatrequest请求中JSON格式不正确

·     The region does not existRegion不存在

 

10.3  Update Region

关键字

UPDATE_REGION_OP

日志内容

Updated region:$1

参数解释

$1Region配置信息

举例

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

日志说明

用户进行了更新Region的操作

失败原因

当操作失败时,可能的原因如下:

·     The region does not existRegion不存在

·     The controller is not the active leader该控制器不是主Leader

·     Incorrect JSON formatrequest请求中JSON串格式不正确

·     The request can't be nullrequest请求为空

·     The input region information was incorrect :输入Region信息不匹配

·     Incorrect IP address or mask format for the managed node subnets管理设备网段的IP地址或掩码格式错误

 


11 CON_ROUTERCONFIGS

本节介绍路由配置模块输出的操作日志信息。

11.1  Assign an IP address to the loopback interface

关键字

ADD_LOOPBACK_OP

日志内容

Assigned an IP address to the loopback interface:

IP: $1

参数解释

$1:环回口IP地址

举例

Assigned an IP address to the loopback interface:

IP: 2.3.3.3

日志说明

用户进行了配置控制器环回口IP地址的操作

失败原因

当操作失败时,可能的原因如下:

·     The loopback interface already has an IP address:环回口IP地址已存在

·     Failed to deploy the address configuration of the loopback interface:环回口IP地址配置下发失败

 

11.2  Delete the IP address of the loopback interface

关键字

DELETE_LOOPBACK_OP

日志内容

Deleted the IP address of the loopback interface:

IP: $1

参数解释

$1:环回口IP地址

举例

Deleted the IP address of the loopback interface:

IP: 2.3.3.3

日志说明

用户进行了删除环回口IP地址的操作

失败原因

当操作失败时,可能的原因如下:

·     The IP address doesn't exist:环回口IP地址存在

·     Failed to deploy the request for deleting the IP address:删除请求下发失败

 

11.3  Add BGP Instance

关键字

ADD_BGPINSTANCE_OP

日志内容

Added BGP instance:

Router ID: $1

Local AS number: $2

参数解释

$1:控制器BGP实例的Router ID

$2:控制器BGP实例的本地AS

举例

Added BGP instance:

Router ID: 10.10.10.10

Local AS number: 1000

日志说明

用户进行了配置BGP实例的操作

失败原因

当操作失败时,可能的原因如下:

·     The local AS number already existsBGP本地AS号已存在

·     Failed to connect to bgpd. Check whether Quagga is correctly installed or the BGP daemon is enabledQuagga连接失败。请检查是否正确安装Quagga软件或是否启动BGP进程

·     Failed to deploy the BGP instance configurationBGP实例配置下发失败

·     Failed to deploy the BGP router ID configurationBGP Router ID配置下发失败

·     Operation failed because the controller is deploying routing configuration. Please try again later:由于正在进行路由配置下发,本次配置失败,请稍后再试

 

11.4  Clear BGP configuration

关键字

CLEAR_BGP_CONF_OP

日志内容

Cleared BGP configuration.

参数解释

举例

Cleared BGP configuration.

日志说明

用户进行了清除BGP配置的操作

失败原因

当操作失败时,可能的原因如下:

·     Failed to deploy the request for deleting BGP instanceBGP实例删除请求下发失败

·     Failed to connect to bgpd. Check whether Quagga is correctly installed or the BGP daemon is enabledQuagga连接失败。请检查是否正确安装Quagga软件或是否启动BGP进程

·     The BGP instance doesn't existBGP实例不存在

·     Operation failed because the controller is deploying routing configuration. Please try again later:由于正在进行路由配置下发,本次配置失败,请稍后再试

 

11.5  Add BGP Network

关键字

ADD_BGPNETWORK_OP

日志内容

Added BGP network:

IP: $1

参数解释

$1BGP发布的本地网段路由

举例

Added BGP network:

IP: 10.10.10.10/32

日志说明

用户进行了添加BGP发布的本地网段路由的操作

失败原因

当操作失败时,可能的原因如下:

·     The BGP instance doesn't existBGP实例不存在

·     The network already exists:该Network已存在,请勿重复添加

·     Failed to deploy the network configurationNetwork配置下发失败

·     Failed to connect to bgpd. Check whether Quagga is correctly installed or the BGP daemon is enabledQuagga连接失败。请检查是否正确安装Quagga软件或是否启动BGP进程

·     The number of networks reaches the upper limitNetwork配置数量已达最大值

·     Operation failed because the controller is deploying routing configuration. Please try again later:由于正在进行路由配置下发,本次配置失败,请稍后再试

 

11.6  Delete BGP Network

关键字

DELETE_BGPNETWORK_OP

日志内容

Deleted BGP network:

IP: $1

参数解释

$1BGP发布的本地网段路由

举例

Deleted BGP network:

IP: 10.10.10.10/32

日志说明

用户进行了删除BGP发布的本地网段路由的操作

失败原因

当操作失败时,可能的原因如下:

·     The BGP instance doesn't existBGP实例不存在

·     The network doesn’t exist:该Network配置不存在

·     Failed to deploy the request for deleting networkNetwork删除请求下发失败

·     Failed to connect to bgpd. Check whether Quagga is correctly installed or the BGP daemon is enabledQuagga连接失败。请检查是否正确安装Quagga软件或是否启动BGP进程

·     Operation failed because the controller is deploying routing configuration. Please try again later:由于正在进行路由配置下发,本次配置失败,请稍后再试

 

11.7  Add BGP Neighbor

关键字

ADD_BGPNEIGHBOR_OP

日志内容

Added BGP neighbor:

IP: $1

Remote AS number: $2

Filtering policy: $3

参数解释

$1:邻居的IP地址

$2:邻居的AS

$3:路由过滤策略

举例

Added BGP neighbor:

IP: 10.10.10.11

Remote AS number: 1000

Filtering policy: in

日志说明

用户进行了配置BGP邻居的操作

失败原因

当操作失败时,可能的原因如下:

·     The BGP instance doesn't existBGP实例不存在

·     The neighbor already exists:该Neighbor已存在,请勿重复配置

·     Failed to deploy the neighbor configurationNeighbor配置下发失败

·     Failed to connect to bgpd. Check whether Quagga is correctly installed or the BGP daemon is enabledQuagga连接失败。请检查是否正确安装Quagga软件或是否启动BGP进程

·     The number of BGP neighbors reaches the upper limitNeighbor配置数量已达最大值

·     Operation failed because the controller is deploying routing configuration. Please try again later:由于正在进行路由配置下发,本次配置失败,请稍后再试

 

11.8  Delete BGP Neighbor

关键字

DELETE_BGPNEIGHBOR_OP

日志内容

Deleted BGP neighbor:

IP: $1

Remote AS number: $2

Filtering policy: $3

参数解释

$1:邻居的IP地址

$2:邻居的AS

$3:路由过滤策略

举例

Deleted BGP neighbor:

IP: 10.10.10.11

Remote AS number: 1000

Filtering policy: in

日志说明

用户进行了删除BGP邻居的操作

失败原因

当操作失败时,可能的原因如下:

·     The BGP instance doesn't existBGP实例不存在

·     The neighbor doesn't exist:该Neighbor配置不存在

·     Failed to deploy the request for deleting neighborNeighbor删除请求下发失败

·     Failed to connect to bgpd. Check whether Quagga is correctly installed or the BGP daemon is enabledQuagga连接失败。请检查是否正确安装Quagga软件或是否启动BGP进程

·     Operation failed because the controller is deploying routing configuration. Please try again later:由于正在进行路由配置下发,本次配置失败,请稍后再试

 

11.9  Add Timer

关键字

ADD_BGPTIMER_OP

日志内容

Added timer:

Keepalive interval: $1

Hold time: $2

参数解释

$1:会话存活时间间隔,单位为秒

$2:会话保持时间,单位为秒

举例

Added timer:

Keepalive interval: 600

Hold time: 1800

日志说明

用户进行了配置会话存活时间间隔和会话保持时间的操作

失败原因

当操作失败时,可能的原因如下:

·     Failed to deploy the keepalive interval and hold time configuration:会话存活时间间隔与保持时间配置下发失败

·     Failed to connect to bgpd. Check whether Quagga is correctly installed or the BGP daemon is enabledQuagga连接失败。请检查是否正确安装Quagga软件或是否启动BGP进程

·     The BGP instance doesn't existBGP实例不存在

·     Operation failed because the controller is deploying routing configuration. Please try again later:由于正在进行路由配置下发,本次配置失败,请稍后再试

 

11.10  Add OSPF RouterId

关键字

ADD_OSPFROUTERID_OP

日志内容

Added OSPF router ID:

IP: $1

参数解释

$1OSPF router ID

举例

Added OSPF router ID:

IP: 10.10.10.10

日志说明

用户进行了配置OSPF Router ID的操作

失败原因

当操作失败时,可能的原因如下:

·     The router ID already exists:该Router ID已存在,请勿重复配置

·     Failed to deploy the router ID configurationRouter ID配置下发失败

·     Failed to connect to ospfd. Check whether Quagga is correctly installed or the OSPF daemon is enabledQuagga连接失败。请检查是否正确安装Quagga软件或是否启动OSPF进程

·     Operation failed because the controller is deploying routing configuration. Please try again later:由于正在进行路由配置下发,本次配置失败,请稍后再试

 

11.11  Add OSPF Network

关键字

ADD_OSPFNETWORK_OP

日志内容

Added OSPF network:

IP: $1

Area ID: $2

参数解释

$1OSPF网段路由

$2OSPF区域号

举例

Added OSPF network:

IP: 10.10.10.10/32

Area ID: 0

日志说明

用户进行了配置OSPF网段路由的操作

失败原因

当操作失败时,可能的原因如下:

·     The network already exists:该Network已存在,请勿重复配置

·     Failed to deploy the network configurationNetwork配置下发失败

·     Failed to connect to ospfd. Check whether Quagga is correctly installed or the OSPF daemon is enabledQuagga连接失败。请检查是否正确安装Quagga软件或是否启动OSPF进程

·     The number of networks reaches the upper limitNetwork配置数量已达最大值

·     Operation failed because the controller is deploying routing configuration. Please try again later:由于正在进行路由配置下发,本次配置失败,请稍后再试

 

11.12  Delete OSPF Network

关键字

DELETE_OSPFNETWORK_OP

日志内容

Deleted OSPF network:

IP: $1

Area ID: $2

参数解释

$1OSPF网段路由

$2OSPF区域号

举例

Deleted OSPF network:

IP: 10.10.10.10

Area ID: 0

日志说明

用户进行了删除OSPF网段路由的操作

失败原因

当操作失败时,可能的原因如下:

·     The network doesn't exist:该Network配置不存在

·     Failed to deploy the request for deleting networkNetwork删除请求下发失败

·     Failed to connect to ospfd. Check whether Quagga is correctly installed or the OSPF daemon is enabledQuagga连接失败。请检查是否正确安装Quagga软件或是否启动OSPF进程

·     Operation failed because the controller is deploying routing configuration. Please try again later:由于正在进行路由配置下发,本次配置失败,请稍后再试

 

11.13  Clear OSPF configuration

关键字

CLEAR_OSPF_CONF_OP

日志内容

Cleared OSPF configuration.

参数解释

举例

Cleared OSPF configuration.

日志说明

用户进行了清除OSPF配置的操作

失败原因

当操作失败时,可能的原因如下:

·     Failed to deploy the request for deleting OSPF configurationOSPF配置清除请求下发失败

·     Failed to connect to ospfd. Check whether Quagga is correctly installed or the OSPF daemon is enabledQuagga连接失败。请检查是否正确安装Quagga软件或是否启动OSPF进程

·     Operation failed because the controller is deploying routing configuration. Please try again later:由于正在进行路由配置下发,本次配置失败,请稍后再试

 

11.14  Add OSPF area

关键字

ADD_OSPFAREA_OP

日志内容

Added OSPF area:

Area ID: $1

NSSA: $2

Authentication: $3

参数解释

$1OSPF区域号

$2OSPF NSSA区域属性

$3OSPF的验证模式

举例

Added OSPF area:

Area ID: 1.2.3.6

NSSA: translate-candidate

Authentication: message-digest

日志说明

用户进行了配置OSPF区域的操作

失败原因

当操作失败时,可能的原因如下:

·     The area already exists:该Area已存在,请勿重复配置

·     Failed to deploy the area configurationArea配置下发失败

·     Failed to connect to ospfd. Check whether Quagga is correctly installed or the OSPF daemon is enabledQuagga连接失败。请检查是否正确安装Quagga软件或是否启动OSPF进程

·     Operation failed because the controller is deploying routing configuration. Please try again later:由于正在进行路由配置下发,本次配置失败,请稍后再试

 

11.15  Delete OSPF area

关键字

DELETE_OSPFAREA_OP

日志内容

Deleted OSPF area:

Area ID: $1

参数解释

$1OSPF区域号

举例

Deleted OSPF area:

Area ID: 0.0.0.0

日志说明

用户进行了删除OSPF区域的操作

失败原因

当操作失败时,可能的原因如下:

·     The area doesn't exist:该Area配置不存在

·     Failed to deploy the request for deleting areaArea删除请求下发失败

·     Failed to connect to ospfd. Check whether Quagga is correctly installed or the OSPF daemon is enabledQuagga连接失败。请检查是否正确安装Quagga软件或是否启动OSPF进程

·     Operation failed because the controller is deploying routing configuration. Please try again later:由于正在进行路由配置下发,本次配置失败,请稍后再试

 


12 CON_SNMP

本节介绍SNMP模块输出的操作日志信息。

12.1  Create traditional NE

关键字

CREATE_TRADITIONAL_NE_OP

日志内容

Created traditional NE: $1

参数解释

$1:传统网元的配置信息

举例

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

日志说明

用户进行了增加传统网元的操作

失败原因

当操作失败时,可能的原因如下:

·     The controller is not the active leader:该控制器不是主Leader

·     Invalid network element IP address:无效的网元IP地址

·     The traditional network element at X.X.X.X already exists:网元IP地址为X.X.X.X的传统网元已存在

·     Invalid controller IP address:无效的控制器IP地址

·     The controller IP address doesn't exist in the team:指定的控制器IP地址在集群内不存在

·     The IP address for a controller in standalone mode must be 127.0.0.1:独立运行模式下,控制器IP地址只能为127.0.0.1

·     Invalid access attribute:无效的接入属性

·     The traditional network element has been added to the controller by using X.X.X.X:该传统网元已通过IP地址X.X.X.X增加到控制器

 

12.2  Update traditional NE

关键字

UPDATE_TRADITIONAL_NE_OP

日志内容

Updated traditional NE: $1

参数解释

$1:传统网元的配置信息

举例

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

日志说明

用户进行了修改传统网元的操作

失败原因

·     The controller is not the active leader:该控制器不是主Leader

·     Invalid network element IP address:无效的网元IP地址

·     The network element IP address doesn't exist:指定的网元IP地址不存在

·     Invalid controller IP address:无效的控制器IP地址

·     The controller IP address doesn't exist in the team:指定的控制器IP在集群内不存在

·     The IP address for a controller in standalone mode must be 127.0.0.1:独立运行模式下,控制器IP地址只能为127.0.0.1

·     Invalid access attribute:无效的接入属性

·     Unknown error:未知错误

 

12.3  Delete traditional NE

关键字

DELETE_TRADITIONAL_NE_OP

日志内容

Deleted traditional NE: $1

参数解释

$1:传统网元的IP地址

举例

Deleted traditional NE: 192.168.9.198

日志说明

用户进行了删除传统网元的操作

失败原因

·     The controller is not the active leader:该控制器不是主Leader

·     Invalid network element IP address:无效的网元IP地址

·     The network element IP address doesn't exist:指定的网元IP地址不存在

 

12.4  Start scanning traditional NE

关键字

START_SCAN_TRADITIONAL_NE_OP

日志内容

Started scanning traditional NEs: $1

参数解释

$1:传统网元的自动发现配置

举例

Started scanning traditional NEs:

  Start IP: 192.168.125.0

  End IP: 192.168.125.255

  SNMP read community: public

  SNMP write community: private

日志说明

用户进行了自动发现传统网元的操作

失败原因

 

12.5  Stop scanning traditional NE

关键字

STOP_SCAN_TRADITIONAL_NE_OP

日志内容

Stopped scanning traditional NEs

参数解释

举例

Stopped scanning traditional NEs

日志说明

用户进行了停止自动发现传统网元的操作

失败原因

 


13 CON_SYSTEM

本节介绍系统管理模块输出的操作日志信息。

13.1  Backup

关键字

BACKUP_OP

日志内容

Backed up the configuration.

参数解释

$1:备份的Session名,是用于标识本次备份操作的标识码

举例

Backed up the configuration.

日志说明

用户进行了配置备份的操作

失败原因

当操作失败时,可能的原因如下:

·     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:当前控制器所在集群不存在Leader

 

13.2  Upload

关键字

UPLOAD_BACKUPFILE_OP

日志内容

Uploaded the backup file.

参数解释

举例

Uploaded the backup file.

日志说明

用户进行了备份文件上传的操作

失败原因

当操作失败时,可能的原因如下:

·     The controller is not the active leader该控制器不是主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:由于网络原因,Leader控制器将备份文件发送到其他控制器失败

·     The system is recovering the configuration:系统正在恢复配置

·     The team to which the controller belongs has no active leader:当前控制器所在集群不存在Leader

·     Can’t upload the backup file because some controllers are down: $1, $2, $3控制器:$1$2$3状态为down,无法上传备份文件

 

13.3  Restore

关键字

RESTORE_OP

日志内容

Restored the configuration.

参数解释

举例

Restored the configuration

日志说明

用户进行了配置恢复的操作

失败原因

当操作失败时,可能的原因如下:

·     The controller is not the active leader该控制器不是主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:备份文件的集群配置中不包含本控制器IP

·     The active leader can't restore the configuration of other controllers due to network errors:由于网络原因,Leader控制器不能对其它控制器进行配置恢复

·     The system is recovering the configuration:系统正在恢复配置

·     The team to which the controller belongs has no active leader:当前控制器所在集群不存在Leader

·     Can’t perform configuration recovery because some controllers are down: $1, $2, $3控制器:$1$2$3状态为down,无法进行备份恢复操作

 

13.4  Download

关键字

DOWNLOAD_BACKUPFILE_OP

日志内容

Downloaded the backup file.

参数解释

举例

Downloaded the backup file.

日志说明

备份文件下载成功

失败原因

当操作失败时,可能的原因如下:

·     The backup file doesn't exist:待下载的备份文件不存在

·     The system is recovering the configuration:系统正在恢复配置

·     The team to which the controller belongs has no active leader:当前控制器所在集群不存在Leader

 

13.5  Modify backup settings

关键字

MODIFY_BACKUPSET_OP

日志内容

Modified settings for configuration backup. $1

参数解释

$1:备份参数配置信息

举例

Modified settings for configuration backup.

{backupPath:"/opt/sdn/backupHistory/",

reservation:"30",

remoteIP:"192.168.138.60",

prefix:"AAAA",

status:"open",

frequency:"PER_MONTH",

week:"1",

date:"15",

time:"8:30"}

日志说明

用户修改了备份功能的配置信息

失败原因

当操作失败时,可能的原因如下:

·     Illegal backup settings:修改的配置参数不合法

·     The operation requires the administrator privilege:需要管理员角色才能执行此操作

·     The controller is not the active leader该控制器不是主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:当前控制器所在集群不存在Leader

 

13.6  Modify configuration

关键字

MODIFY_CONFIG_OP

日志内容

Modified configuration: $1.

参数解释

$1:组件名及配置项

举例

Modified configuration: Authentication Manager {

ConnPoolMaxActive=4

AuthenticationProtocol=PAP

SharedKey=******

AuthMode=local

AAAServerIP=192.168.56.19

ConnPoolMaxIdle=1

CachedTokenIdle=900

}.

日志说明

用户进行了修改组件配置项的操作。如果组件中包括密钥或密码配置项,该配置项的值以“******”表示

失败原因

当操作失败时,可能的原因如下:

·     Failed to update the configuration file:更新配置文件失败

·     The existing team token must be deleted before you configure a new one集群Token已存在,请先删除再修改集群Token

·     Invalid value for parameter $1:输入的配置项的值($1)不合法

·     Failed to encrypt the password or key:密钥或密码参数加密失败

 

13.7  Restore configuration

关键字

RESTORE_CONFIG_OP

日志内容

Restored configuration: $1.

参数解释

$1:组件名及配置项。如果重置组件所有配置项的值,则只显示组件名

举例

Restored configuration: Authentication Manager {

ConnPoolMaxActive=4

AuthenticationProtocol=PAP

SharedKey=******

AuthMode=local

AAAServerIP=192.168.56.19

ConnPoolMaxIdle=1

CachedTokenIdle=900

}.

日志说明

用户进行了重置组件配置项为默认值的操作。如果组件中包括密钥或密码配置项,该配置项的值以“******”表示

失败原因

当操作失败时,可能的原因如下:

·     Can't delete the team token in team mode:集群模式下,无法删除集群Token

·     Failed to update the configuration file:更新配置文件失败

 

13.8  Prepared for upgrade

关键字

UPGRADE_PREPARE_OP

日志内容

Prepared for upgrade: $1

参数解释

$1:进行升级准备的控制器IP地址

举例

Prepared for upgrade

日志说明

用户进行了升级准备的操作

失败原因

当操作失败时,可能的原因如下:

·     Invalid request请求参数不合法

 

13.9  Modify alert log remote transmission mode

关键字

MODIFY_ALERTLOG_TRANSMISSION_OP

日志内容

The alert log remote transmission mode was set to sending logs to the syslog server.

参数解释

举例

The alert log remote transmission mode was set to sending logs to the syslog server.

日志说明

用户进行系统日志配置修改的操作,开启Syslog日志服务器功能,系统日志将被发送到指定的日志服务器

失败原因

 

13.10  Modify audit log transmission mode

关键字

MODIFY_AUDITLOG_TRANSMISSION_OP

日志内容

The audit log remote transmission mode was set to sending logs to the syslog server.

参数解释

举例

The audit log remote transmission mode was set to sending logs to the syslog server.

日志说明

用户进行操作日志配置修改的操作,开启Syslog日志服务器功能,操作日志将被发送到指定的日志服务器

失败原因

 

13.11  Enter upgrade mode

关键字

ENTER_UPGRADE_MODE_OP

日志内容

Enter upgrade mode.

参数解释

举例

Enter upgrade mode.

日志说明

用户进行了进入升级模式的操作

失败原因

 

13.12  Quit upgrade mode

关键字

QUIT_UPGRADE_MODE_OP

日志内容

Quit upgrade mode.

参数解释

举例

Quit upgrade mode.

日志说明

用户进行了退出升级模式的操作

失败原因

 


14 CON_TEAM

本节介绍集群模块输出的操作日志信息。

14.1  Create Team

关键字

CREATE_TEAM_OP

日志内容

Created team: $1

参数解释

$1:集群配置信息

举例

Created team:

Name: TestCluster1

IP: 192.168.40.40

Mask: 255.255.255.0

Mode:1

Version: 1404159495844

Team ID: f892866f-0ec9-4ef0-a0a8-6df783ef7b19

Leaders: [

{Name: leader1, IP: 192.168.56.147, Priority: 200, Network_device: eth0, Server ID: 1},

{Name: leader2, IP: 192.168.56.148, Priority: 100, Network_device: eth1, Server ID: 2}

]

Members: [

{Name: member, IP: 192.168.40.146, Priority: 1016, Network_device: , Server ID: 5}

]

日志说明

用户进行了创建集群的操作

失败原因

当操作失败时,可能的原因如下:

·     The team contained only one leader:无法创建只有一个Leader的集群

·     The controller was not a leader:当前所操作的控制器没有配置为Leader

·     Team IP address and member IP address must be different:集群IP地址和成员控制器IP地址不能相同

·     Member IP addresses must be different:成员控制器IP地址不能相同

·     Member names must be different:成员名称不能相同

·     Leader priorities must be differentLeader角色控制器优先级不能相同

·     The number of controllers exceeded the upper limit (32):控制器数目超过32的上限数

·     Server processing error:服务器处理失败

·     The versions of the controllers are inconsistent:用于创建集群的各控制器版本不完全一致

·     The team token is not configured for the controller:控制器未配置集群Token

 

14.2  Delete Team

关键字

DELETE_TEAM_OP

日志内容

Deleted team: $1

参数解释

$1:集群配置信息

举例

Deleted team:

Name: TestCluster1

IP: 192.168.40.40

日志说明

用户进行了删除集群的操作

失败原因

当操作失败时,可能的原因如下:

·     The team didn't exist:不存在该集群

·     The controller was not the active leader:该控制器不是主Leader

·     Server processing error:服务器处理失败

 

14.3  Modify Team

关键字

MODIFY_TEAM_OP

日志内容

Modified team: $1

参数解释

$1:集群配置修改信息

举例

Modified team:

Name:TestCluster1->TestCluster2

IP:192.168.35.11->192.168.35.12

Mask:255.255.255.0->255.255.0.0

日志说明

用户进行了修改集群的操作

失败原因

当操作失败时,可能的原因如下:

·     The controller was not the active leader:该控制器不是主Leader

·     The team didn't exist:不存在该集群

·     Server processing error:服务器处理失败

·     The team name is invalid:集群名称无效

 

14.4  Add Member

关键字

ADD_MEMBER_OP

日志内容

Added member: $1

参数解释

$1:成员信息

举例

Added member:

Name:leader1

IP:192.168.56.147

日志说明

用户进行了添加集群成员的操作

失败原因

当操作失败时,可能的原因如下:

·     The controller was not the active leader:该控制器不是主Leader

·     The team didn't exist:不存在该集群

·     The member IP address must be different from the team IP address:成员控制器IP地址和集群IP地址不能相同

·     The member IP address was already used:成员控制器IP地址和已有成员控制器IP地址相同

·     The member name was already used:成员控制器名称和已有成员名称相同

·     Server processing error:服务器处理失败

·     The version of the selected controller is different than the team:待加入集群的控制器版本与集群已有成员控制器版本不一致

 

14.5  Delete Member

关键字

DELETE_MEMBER_OP

日志内容

Deleted member: $1

参数解释

$1:成员信息

举例

Deleted member:

Name:leader1

IP:192.168.56.147

日志说明

用户进行了删除集群成员的操作

失败原因

当操作失败时,可能的原因如下:

·     The controller was not the active leader or the member to be deleted:请登录主Leader或需退出集群的控制器,进行控制器的删除操作

·     The member didn't exist:不存在该成员控制器

·     A leader can't be deleted:无法删除该Leader控制器

·     The member was in a region:集群成员控制器处于Region

·     Server processing error:服务器处理失败

 

14.6  Modify Member

关键字

MODIFY_MEMBER_OP

日志内容

Modified member: $1

参数解释

$1:成员修改信息

举例

Modified member:

Name:member1->member2

IP:192.168.35.11

Network_device:eth0->eth1

日志说明

用户进行了修改集群成员的操作

失败原因

当操作失败时,可能的原因如下:

·     The controller was not the active leader:该控制器不是主Leader

·     NIC for the member can't be changed:无法在Member角色控制器上修改NIC属性

·     Server processing error服务器处理失败

·     The controller name is invalid:控制器名称无效

·     The member name was already used:成员控制器名称和已有成员名称相同

 


15 CON_TOPOLOGY

本节介绍拓扑管理模块输出的操作日志信息。

15.1  Update device

关键字

UPDATE_DEVICE_INFO_OP

日志内容

Updated device: $1

参数解释

$1:设备信息

举例

Updated device:

IP address: 192.168.9.198

Datapath ID: 00:00:74:25:8a:c4:e2:de

Asset number: 201605181600

Device description: H3C Comware Platform Software, Software Version 7.1.070, ESS 2505P01

Location: A13-A13

Function: core

Remarks: description

Device name: 201-98

Status: Inactive

日志说明

用户进行了修改设备清单中设备信息的操作

失败原因

当操作失败时,可能的原因如下:

·     The device doesn't exist该设备不存在

 

15.2  Update device layer

关键字

UPDATE_DEVICE_LAYER_OP

日志内容

Updated the layer for device (IP address $1 and datapath ID $2): $3.

参数解释

$1:设备的IP地址

$2:设备的Datapath ID

$3:设备的接入属性,取值包括:accessconvergencecore

举例

Updated the layer for device (IP address 192.168.9.198 and datapath ID 00:00:74:25:8a:c4:e2:de): core.

日志说明

用户进行了修改物理拓扑页面指定设备的接入属性的操作

失败原因

当操作失败时,可能的原因如下:

·     The device doesn't exist该设备不存在

 

15.3  Delete inactive link

关键字

DELETE_INACTIVE_LINK_OP

日志内容

Deleted an inactive link. Link information: $1

参数解释

$1:设备的下线链路信息

举例

Deleted an inactive link. Link information:

From: Port GigabitEthernet1/0/3 on device (IP address 192.168.150.44 and datapath ID 00:00:68 b:10 a:04:00).

To: Port GigabitEthernet1/0/5 on device (IP address 192.168.150.42 and datapath ID 00:00:94:e2:4e:53:02:00).

日志说明

用户进行了删除设备的下线链路的操作

失败原因

 

15.4  Update port thresholds

关键字

UPDATE_PORT_THRESHOLD_OP

日志内容

Updated port thresholds: $1

参数解释

$1:接口阈值信息

举例

Updated port monitor thresholds:

  Inbound bandwidth usage: 12%

  Outbound bandwidth usage: 32%

  Inbound error packet rate: 43%

  Outbound error packet rate: 43%

  Inbound packet loss rate: 54%

  Outbound packet loss rate: 65%

日志说明

用户进行了修改设备接口阈值的操作

失败原因

 

15.5  Clear events on a device

关键字

CLEAR_DEVICE_EVENTS_OP

日志内容

Clear events on device: $1.

参数解释

$1:设备的IP地址

举例

Clear events on device: 192.168.5.3.

日志说明

用户进行了清除指定设备的事件的操作

失败原因

当操作失败时,可能的原因如下:

·     The device doesn't exist该设备不存在

 

15.6  Clear events on all devices

关键字

CLEAR_ALL_DEVICES_EVENTS_OP

日志内容

Clear events on all devices.

参数解释

举例

Clear events on all devices.

日志说明

用户进行了清除所有设备的事件的操作

失败原因

 

 


16 CON_USER

本节介绍用户管理模块输出的操作日志信息。

16.1  Add a user

关键字

ADD_USER_OP

日志内容

Added a user:$1.

参数解释

$1:增加用户的用户名

举例

Added a user:11.

日志说明

用户进行了增加用户的操作

失败原因

当操作失败时,可能的原因如下:

·     Invalid username:输入的用户名无效

·     Invalid role:输入的用户角色无效

·     The username already exists:该用户名已存在

·     The password length is out of range or the password contains only letters, digits, or special characters:密码长度范围不正确或未包含数字、字母和特殊字符中的两种类型

·     The controller is not the active leader:当前设备不是Leader控制器,无法进行此操作

·     Incorrect format:格式错误

·     Failed to add the user用户添加失败

 

16.2  Deleted a user

关键字

DELETE_USER_OP

日志内容

Deleted a user: $1.

参数解释

$1:删除用户的用户名

举例

Deleted a user: 11.

日志说明

用户进行了删除用户的操作

失败原因

当操作失败时,可能的原因如下:

·     Invalid username:输入的用户名无效

·     No permission to delete itself:当前用户不能执行删除自己操作

·     The controller is not the active leader:当前设备不是Leader控制器,无法进行此操作

·     Can't delete an online user不允许删除在线用户

·     Token agedToken已老化

 

16.3  Changed user password

关键字

CHANGE_PASSWORD_OP

日志内容

Changed user $1's password.

参数解释

$1:修改密码的用户

举例

Changed user 11's password.

日志说明

用户进行了修改密码的操作

失败原因

当操作失败时,可能的原因如下:

·     Invalid username:输入的用户名无效

·     Invalid old password:输入的密码无效

·     The password length is out of range or the password contains only letters, digits, or special characters:密码长度范围不正确或未包含数字、字母和特殊字符中的两种类型

·     Can't modify another user's password due to permission limit权限不足无法修改其他用户的密码

·     The controller is not the active leader:当前设备不是Leader控制器,无法进行此操作

·     Token agedToken已老化

·     The user doesn’t exist:用户不存在

·     Failed to update the user’s password:修改用户密码失败

 

16.4  Update user config

关键字

UPDATE_USER_OP

日志内容

Updated user configuration: $1

参数解释

$1:用户配置信息

举例

Updated user configuration:

Username: sdn

Password: ******

Role: sdn-admin

Service logs to display: ARP, CON, NEM, VSM

Lock state: unlock

日志说明

用户进行了修改用户配置的操作

失败原因

当操作失败时,可能的原因如下:

·     The user does not exist:用户不存在

·     Invalid parameter for locking the user:输入的锁定值无效

·     Invalid user role:输入的用户角色无效

·     Invalid old password:输入的旧密码无效

·     Invalid username:输入的用户名无效

·     Incorrect format:格式错误

·     The controller is not the active leader:该设备不是Leader控制器,无法进行此操作

·     Can't modify another user's configuration due to permission limit权限不足无法修改其他用户的配置

·     Can't lock the current user:当前用户不能对自身执行锁定操作

·     Can't modify the role of the current user.:当前用户不能对自身执行角色修改操作

·     Can't change the types of service logs to display due to permission limit权限不足无法修改可查看业务日志类型

·     The password length is out of range or the password contains only letters, digits, or special characters:密码长度范围不正确或未包含数字、字母和特殊字符中的两种类型

·     Token agedToken已老化

·     Failed to update the user:修改用户失败

·     Can't modify the configuration of other online users:不允许修改其它在线用户的配置

 

16.5  Add a role

关键字

ADD_ROLE_OP

日志内容

Added a role: $1.

参数解释

$1:角色名称

举例

Added a role: role1.

日志说明

用户进行了增加角色的操作

失败原因

当操作失败时,可能的原因如下:

·     Invalid role name:输入的角色名无效

·     Invalid role rule:输入的权限规则无效

·     Invalid description:输入的描述无效

·     The role already exists:该角色名已存在

·     You have no privilege to perform the operation:当前用户无权限执行此项操作

·     The controller is not the active leader:当前设备不是Leader控制器,无法进行此操作

·     Incorrect format:格式错误

·     Failed to add the role:角色添加失败

 

16.6  Update a role

关键字

UPDATE_ROLE_OP

日志内容

Updated role configuration: $1

参数解释

$1:角色配置信息

举例

Updated role configuration:

Rolename: test2,

Description:,

RoleRules: {

  "rolerules": {

    "/lb/v2.0": {

      "details": [

        {

          "access": "POST",

          "controlled": "/loadbalancers"

        }

      ],

      "module": "LBaaS v2.0",

      "type": "REST"

    },

    "c-NetworkService": {

      "details": [

        {

          "access": "R",

          "controlled": "n-LoadBalance"

        }

      ],

      "type": "UI"

    }

  }

}

日志说明

用户进行了修改角色配置的操作

失败原因

当操作失败时,可能的原因如下:

·     You have no privilege to perform the operation:当前用户无权限执行此项操作

·     Incorrect format:格式错误

·     The controller is not the active leader:当前设备不是Leader控制器,无法进行此操作

·     Invalid role name输入的角色名无效

·     Invalid role rule:输入的权限规则无效

·     Invalid description:输入的描述信息无效

·     Can't modify default roles:系统默认角色不允许修改

·     The role doesn’t exist:该角色不存在

·     Failed to update the role:修改角色失败

 

16.7  Delete a role

关键字

DELETE_ROLE_OP

日志内容

Deleted a role: $1.

参数解释

$1:删除角色的角色名

举例

Deleted a role: 11.

日志说明

用户进行了删除角色的操作

失败原因

当操作失败时,可能的原因如下:

·     Invalid role name:输入的角色名无效

·     The controller is not the active leader:当前设备不是Leader控制器,无法进行此操作

·     Can't delete system default roles系统默认角色不允许删除

·     Can’t delete the role because it is already assigned to users:该角色已被授权给用户,不能删除

 

 


17 Fabrics

本节介绍Fabrics模块输出的操作日志信息。

17.1  Create Fabric

关键字

CREATE_FABRIC_OP

日志内容

Created fabric: $1

参数解释

$1Fabric配置信息

举例

Created fabric:

ID: [9cd56545-d3b9-428e-bbf5-5a88313ec039]

Name: [fabric1]

Underlay protocol: [BGP]

EVPN: [true]

ARP control: [

ARP flooding: [false]

ARP proxy: [false]

ARP to controller: [false] ]

DHCP control: [

DHCP to controller: [false] ]

RARP Ctrl: [

RARP flooding: [false]

RARP to controller: [false] ]

LLDP to controller: [false]

AS number: [65534].

日志说明

用户进行了创建Fabric的操作

失败原因

当操作失败时,可能的原因如下:

·     Configuration recovery is in progress:配置正在恢复过程中

·     The service has not been found:服务未启动

·     The controller is not the active leader:该控制器不是主Leader

·     The fabric already exists:指定的Fabric已存在

·     The fabric name already exists:指定的Fabric名称已存在

·     Parameters (parameters) are required(parameters)参数为必选项

·     Unknown error:未知错误

·     The request is invalid:无效的请求

·     Failed to create the fabricFabric创建失败

·     The fabric name cannot exceed 255 charactersFabric名称长度不能超过255字符

·     The VTEP IP allocation mode is incorrectVTEP IP分配方式有误

·     The underlay protocol is invalid:无效的Underlay协议

·     The AS number is invalid:无效的AS

·     The AS number already exists:指定的AS号已存在

·     Invalid ARP configuration:无效的ARP配置

·     Invalid ARP proxy configuration无效的ARP代答配置

·     Invalid ARP flooding configuration无效的ARP泛洪配置

·     Invalid ARP to controller configuration无效的ARP上送控制器配置

·     Invalid RARP configuration:无效的RARP配置

·     Invalid RARP to controller configuration无效的RARP上送控制器配置

·     Invalid RARP flooding configuration无效的RARP泛洪配置

·     Invalid DHCP configuration:无效的DHCP配置

·     Invalid DHCP to controller configuration无效的DHCP上送控制器配置

·     Invalid ND configuration:无效的ND配置

·     Invalid ND proxy configuration:无效的ND代答配置

·     Invalid NSNA flooding configuration:无效的NSNA泛洪配置

·     Invalid NSNA to controller configuration:无效的NSNA报文上送控制器配置

·     Invalid RSRA to controller configuration:无效的RSRA报文上送控制器配置

·     Invalid RSRA flooding configuration:无效的RSRA报文泛洪配置

·     Invalid DHCPv6 configuration:无效的DHCPv6配置

·     Invalid DHCPv6 to controller configuration:无效的DHCPv6报文上送控制器配置

·     Invalid mac advertising configuration:无效的MAC地址通告开关

·     The RR MAC address list contains invalid MAC addressesRR设备的MAC地址列表中存在不合法地址

·     You must create a device whitelist for the fabric when the underlay protocol is IS-IS and the master spine is configured to assign VTEP IPs:当Underlay协议为ISIS时且VTEP IP的分配方式为Master Spine时,Fabric必须创建设备白名单

·     The default fabric cannot be created:不允许创建默认Fabric

·     The default fabric ID cannot be used:不允许使用默认Fabric ID

·     The fabric name is default fabric name:指定修改的Fabric名称为默认Fabric名称

·     The VTEP IP allocation mode is incorrectVTEP IP分配方式有误

 

17.2  Update Fabric

关键字

UPDATE_FABRIC _OP

日志内容

Updated fabric: $1

参数解释

$1Fabric配置信息

举例

Updated fabric:

ID: [9cd56545-d3b9-428e-bbf5-5a88313ec039]

Name: [fabric1]

Underlay protocol: [BGP]

EVPN: [true]

ARP control: [

ARP flooding: [false]

ARP proxy: [false]

ARP to controller: [false] ]

DHCP control: [

DHCP to controller: [false] ]

RARP control: [

RARP flooding: [false]

RARP to controller: [false] ]

LLDP to controller: [false]

AS number: [65534].

日志说明

用户进行了修改Fabric的操作

失败原因

当操作失败时,可能的原因如下:

·     Configuration recovery is in progress:配置正在恢复过程中

·     The service has not been found:服务未启动

·     The controller is not the active leader:该控制器不是主Leader

·     The fabric does not exist:指定的Fabric不存在

·     The fabric name already exists:指定的Fabric名称已存在

·     Parameters (parameters) cannot be modified(parameters)参数不允许修改

·     Unknown error:未知错误

·     The request is invalid:无效的请求

·     The fabric name cannot exceed 255 charactersFabric名称长度不能超过255字符

·     The VTEP IP allocation mode is incorrectVTEP IP分配方式有误

·     The underlay protocol is invalid:无效的Underlay协议

·     Invalid ARP configuration:无效的ARP配置

·     Invalid ARP proxy configuration无效的ARP代答配置

·     Invalid ARP flooding configuration无效的ARP泛洪配置

·     Invalid ARP to controller configuration无效的ARP上送控制器配置

·     Invalid RARP configuration:无效的RARP配置

·     Invalid RARP to controller configuration无效的RARP上送控制器配置

·     Invalid RARP flooding configuration无效的RARP泛洪配置

·     Invalid DHCP configuration:无效的DHCP配置

·     Invalid DHCP to controller configuration无效的DHCP上送控制器配置

·     Invalid ND configuration:无效的ND配置

·     Invalid ND proxy configuration:无效的ND代答配置

·     Invalid NSNA flooding configuration:无效的NSNA泛洪配置

·     Invalid NSNA to controller configuration:无效的NSNA报文上送控制器配置

·     Invalid RSRA to controller configuration:无效的RSRA报文上送控制器配置

·     Invalid RSRA flooding configuration:无效的RSRA报文泛洪配置

·     Invalid DHCPv6 configuration:无效的DHCPv6配置

·     Invalid DHCPv6 to controller configuration:无效的DHCPv6报文上送控制器配置

·     Invalid mac advertising configuration:无效的MAC地址通告开关

·     The AS number is used by a device configuration etemplate, and cannot be deleted:指定的AS号已被设备配置模板使用,不允许修改

·     The AS number is used by a fabric connection, and cannot be modified:指定的AS号已被Fabric连接使用,不允许修改

·     The AS number is used by a group gateway, and cannot be modified:指定的AS号已被组合出口网关中的备设备使用,不允许修改

·     The underlay protocol is used by a deployment resource pool, and cannot be modifiedUnderlay协议已被管理部署资源池使用,不允许修改

·     The underlay protocol is used by a device configuration template, and cannot be modifiedUnderlay协议已被设备配置模板使用,不允许修改

·     The RR MAC cannot be modified because the corresponding device is active:当前RR MAC地址对应的设备处于激活状态,MAC地址不允许修改

·     You must create a device whitelist for the fabric when the underlay protocol is IS-IS and the master spine is configured to assign VTEP IPs:当Underlay协议为ISIS时且VTEP IP的分配方式为Master Spine时,Fabric必须创建设备白名单

·     The VTEP IP allocation method has been bound to an address pool, and cannot be modifiedVTEP IP分配方式已绑定地址池,不允许修改。

·     The VTEP IP allocation method has been bound to a device configuration template, and cannot be modifiedVTEP IP分配方式已绑定设备配置模板,不允许修改

·     The fabric name is default fabric name:指定修改的Fabric名称为默认Fabric名称

·     The default fabric name cannot be modified:默认Fabric名称不允许修改

·     Failed to update the default fabric:修改默认Fabric失败

·     The VTEP IP allocation method has been bound to an address pool, and cannot be modifiedVTEP IP分配方式已绑定地址池,不允许修改

·     The VTEP IP allocation method has been bound to a device configuration template, and cannot be modifiedVTEP IP分配方式已绑定设备配置模板,不允许修改

 

17.3  Delete Fabric

关键字

DELETE_FABRIC _OP

日志内容

Deleted fabric: $1

参数解释

$1FabricUUID

举例

Deleted fabric: 218b5f2f-e435-4365-a1ab-0eaa03b7fa19

日志说明

用户进行了修改Fabric的操作

失败原因

当操作失败时,可能的原因如下:

·     Configuration recovery is in progress:配置正在恢复过程中

·     The service has not been found:服务未启动

·     The controller is not the active leader:该控制器不是主Leader

·     The fabric does not exist:指定的Fabric不存在

·     Unknown error:未知错误

·     The request is invalid:无效的请求

·     The fabric has devicesFabric中存在已被纳管的设备

·     The fabric has border device groupsFabric中存在已被纳管的边界设备组

·     The fabric is being used by a VDSFabric正在被VDS使用

·     The fabric is being used by a hostFabric正在被主机使用

·     The fabric is used by a configuration template, and cannot be deletedFabric已被设备配置模板引用,不允许删除

·     The fabric is used by a device control protocol template, and cannot be deletedFabric已被设备控制协议模板引用,不允许删除

·     The fabric is used by a deployment resource pool, and cannot be deletedFabric已被管理部署资源池引用,不允许删除

·     The default fabric cannot be deleted:默认Fabric不允许删除

 

17.4  Search Fabric

关键字

SEARCH_FABRIC _OP

日志内容

Searched fabric: $1

参数解释

$1FabricUUID,当不指定该参数时表示查询所有Fabric信息

举例

Searched fabric: 218b5f2f-e435-4365-a1ab-0eaa03b7fa19

日志说明

用户进行了查询Fabric信息的操作

失败原因

当操作失败时,可能的原因如下:

·     Configuration recovery is in progress:配置正在恢复过程中

·     The service has not been found:服务未启动

·     The controller is not the active leader:该控制器不是主Leader

·     The fabric does not exist:指定的Fabric不存在

·     Unknown error:未知错误

·     The request is invalid:无效的请求

·     The page number must be an integer in the range of 1 to 2147483647:页数取值范围为12147483647的整数

·     The number of items per page must be an integer in the range of 1 to 2147483647:每页显示个数的取值范围为12147483647的整数

 

17.5  Create Fabric Connection

关键字

CREATE_FABRIC_CONNECTION_OP

日志内容

Created fabric connection: $1

参数解释

$1Fabric连接的配置信息

举例

Created fabric connection:

ID:[e7f605c0-2336-4e4a-8586-69cd543455bc]

Name:[e7f605c0-2336-4e4a-8586-69cd543455bc]

VDS ID:[ffffffff-0000-0000-0000-000000000001]

Connection type:[DEFINED]

Default fabric connection:[false]

ED groups:[

Local ED ID:   d4dd289e-ae05-43c3-b2ee-16be09a01f3f

  Peer ED ID:   b1b2003c-dbe0-43f4-bea2-40c76edd1a32

  Local ED ID:   d4dd289e-ae05-43c3-b2ee-16be09a01f3f

  Peer ED ID:   c20e22a7-3c95-4f3a-8a70-fb8b8d2b6576

Local ED ID:   b1b2003c-dbe0-43f4-bea2-40c76edd1a32

  Peer ED ID:   c20e22a7-3c95-4f3a-8a70-fb8b8d2b6576

    ]   

日志说明

用户进行了创建Fabric连接的操作

失败原因

当操作失败时,可能的原因如下:

·     Invalid license:无效的License

·     Invalid JSON format:无效的JSON格式

·     The service is disabled:服务未启动

·     Configuration recovery is in progress:配置正在恢复过程中

·     The controller is not the active leader:该控制器不是主Leader

·     The VDS ID is required:未指定VDS ID

·     The VDS does not exist:指定的VDS不存在

·     The VDS already has a fabric connection:指定的VDS已与其他Fabric连接绑定

·     The fabric connection already existsFabric连接已存在

·     The fabric connection name already existsFabric连接的名称已经存在

·     The fabric connection type is required:未指定连接类型

·     Invalid name无效的名称

·     The fabric connection type is invalid:无效的连接类型

·     The VSM service does not existVSM服务不存在

·     Invalid VDS ID:无效的VDS ID

·     The ED group settings are invalid:无效的ED组配置

·     Invalid local or peer ED existED组中的本端或对端ED无效

·     Cannot configure ED group settings when the fabric connection type is ALLCONNECT:当Fabric连接类型为全互联时不允许指定ED组配置

·     The ED group settings are required when the fabric connection type is DEFINED:当Fabric连接类型为自定义时,必须指定ED组配置

·     Cannot specify nonexistent EDs:本端或对端ED对应的网元不存在

·     The local and peer EDs cannot be the same:本端和对端ED不允许相同

·     The local and peer EDs in an ED group cannot belong to the same fabric:本端和对端ED不允许属于同一个Fabric

·     The local or peer ED is not added to a DC interconnection gateway group:本端ED或者对端ED未加入到DC互联类型的网关组中

·     Unknown internal server error:未知的内部服务器错误

 

17.6  Update Fabric Connection

关键字

UPDATE_FABRIC_CONNECTION_OP

日志内容

Updated fabric connection: $1

参数解释

$1Fabric连接的配置信息

举例

Updated fabric connection:

 ID:[e7f605c0-2336-4e4a-8586-69cd543455bc]

 Connection type:[DEFINED]

 Default fabric connection:[false]

 ED groups:[

 Local ED ID:   d4dd289e-ae05-43c3-b2ee-16be09a01f3f

 Peer ED ID:   b1b2003c-dbe0-43f4-bea2-40c76edd1a32

 Local ED ID:   d4dd289e-ae05-43c3-b2ee-16be09a01f3f

 Peer ED ID:   c20e22a7-3c95-4f3a-8a70-fb8b8d2b6576

 Local ED ID:   b1b2003c-dbe0-43f4-bea2-40c76edd1a32

 Peer ED ID:   c20e22a7-3c95-4f3a-8a70-fb8b8d2b6576

    ]     

日志说明

用户进行了修改Fabric连接的操作

失败原因

当操作失败时,可能的原因如下:

·     Invalid license:无效的License

·     Invalid JSON format:无效的JSON格式

·     The service is disabled:服务未启动

·     Configuration recovery is in progress:配置正在恢复过程中

·     The controller is not the active leader:该控制器不是主Leader

·     The fabric connection already existsFabric连接已存在

·     The fabric connection name already existsFabric连接的名称已经存在

·     The fabric connection type is required:未指定连接类型

·     Read-only parameters cannot be modified:修改时不允许携带只读字段

·     Invalid name无效的名称

·     The fabric connection type is invalid:无效的连接类型

·     The VSM service does not existVSM服务不存在

·     Invalid VDS ID:无效的VDS ID

·     The ED group settings are invalid:无效的ED组配置

·     Invalid local or peer ED existED组中的本端或对端ED无效

·     Cannot configure ED group settings when the fabric connection type is ALLCONNECT:当Fabric连接类型为全互联时不允许指定ED组配置

·     The ED group settings are required when the fabric connection type is DEFINED:当Fabric连接类型为自定义时,必须指定ED组配置

·     Cannot specify nonexistent EDs:本端或对端ED对应的网元不存在

·     The local and peer EDs cannot be the same:本端和对端ED不允许相同

·     The local and peer EDs in an ED group cannot belong to the same fabric:本端和对端ED不允许属于同一个Fabric

·     The local or peer ED is not added to a DC interconnection gateway group:本端ED或者对端ED未加入到DC互联类型的网关组中

·     Unknown internal server error:未知的内部服务器错误

 

17.7  Delete Fabric Connection

关键字

DELETE_FABRIC_CONNECTION_OP

日志内容

Deleted fabric connection: $1

参数解释

$1Fabric连接的UUID

举例

Deleted fabric connection: 218b5f2f-e435-4365-a1ab-0eaa03b7fa19

日志说明

用户进行了删除Fabric连接的操作

失败原因

当操作失败时,可能的原因如下:

·     Invalid license:无效的License

·     Invalid JSON format:无效的JSON格式

·     The service is disabled:服务未启动

·     Configuration recovery is in progress:配置正在恢复过程中

·     The controller is not the active leader:该控制器不是主Leader

·     The fabric connection UUID is required:未指定Fabric连接的UUID

·     The fabric connection does not exist:指定的Fabric连接不存在

·     Unknown internal server error:未知的内部服务器错误

 


18 FWaaS

本节介绍防火墙服务模块输出的操作日志信息。

18.1  Create time range

关键字

CREATE_TIMERANGE_OP

日志内容

Created time range $1.

参数解释

$1:时间段配置信息

举例

Created time range

ID: 9a83d713-8e79-4ca8-a2e9-8df29daf5fd6

Tenant ID: ffffffff-0000-0000-0000-000000000001

Name: tr

Description: time range

Shared: false

In use: false

Periodic range list:

Position: 1

Start time: 00:00

End time: 24:00

Days of week: [MON, TUE, WED, THU, FRI, SAT]

Absolute range list:

Position: 1

Start time: 00:00

Start date: 2014-08-02

End time: 24:00

End date: 2100-12-31.

日志说明

用户进行了创建时间段的操作

失败原因

当操作失败时,可能的原因如下:

·     The configuration item already exists:配置项已存在

·     The tenant specified for the configuration item doesn't exist:配置项指定的租户不存在

·     The number of configuration items exceeded the limit配置项个数超出限制

·     The controller is not the active leader该控制器不是主Leader

·     The operation requires the administrator privilege:您需要管理员权限才能执行此操作

·     Configuration recovery is in progress配置正在恢复过程中

·     The firewall service has not been found防火墙服务未启动

·     The inused field should be read only时间段状态只读字段

 

18.2  Update time range

关键字

UPDATE_TIMERANGE_OP

日志内容

Updated time range $1.

参数解释

$1:时间段配置信息

举例

Updated time range

ID: 9a83d713-8e79-4ca8-a2e9-8df29daf5fd6

Tenant ID: ffffffff-0000-0000-0000-000000000001

Name: tr

Description: time range

Shared: false

In use: false

Periodic range list:

Position: 1

Start time: 00:00

End time: 20:00

Days of week: [MON, TUE, WED, THU, FRI, SAT]

Absolute range list:

Position: 1

Start time: 00:00

Start date: 2014-08-02

End time: 24:00

End date: 2100-12-30.

日志说明

用户进行了修改时间段的操作

失败原因

当操作失败时,可能的原因如下:

·     The controller is not the active leader该控制器不是主Leader

·     The operation requires the administrator privilege:您需要管理员权限才能执行此操作

·     Configuration recovery is in progress配置正在恢复过程中

·     The firewall service has not been found防火墙服务未启动

·     The configuration item doesnt exist配置项不存在

 

18.3  Delete time range

关键字

DELETE_TIMERANGE_OP

日志内容

Deleted time range $1.

参数解释

$1:时间段名称

举例

Deleted time range tr.

日志说明

用户进行了删除时间段的操作

失败原因

当操作失败时,可能的原因如下:

·     The configuration item is in use配置项正在被使用

·     The configuration item doesnt exist配置项不存在

·     The controller is not the active leader该控制器不是主Leader

·     The operation requires the administrator privilege:您需要管理员权限才能执行此操作

·     Configuration recovery is in progress配置正在恢复过程中

·     The firewall service has not been found防火墙服务未启动

 

18.4  Create firewall rule

关键字

CREATE_FWRULE_OP

日志内容

Created firewall rule $1.

参数解释

$1:防火墙规则配置信息

举例

Created firewall rule

ID: b52fff79-7bcf-4bff-9340-68c5f6c1c495

Tenant ID: ffffffff-0000-0000-0000-000000000001

Name: fw_rule

Description: firewall rule

Shared: true

Protocol: null

IP version: IPv4

Source IP address: 22.2.2.2

Destination IP address: 11.1.1.1

Source port: 100:200

Destination port: 300:400

Position: null

Action: INSPECT

Enabled: true

Time range ID: 9a83d713-8e79-4ca8-a2e9-8df29daf5fd6

App profile ID: 62214486-42a8-455a-ae6c-90853038fd0a

IPS policy ID: 00000000-0000-0000-0000-000000000000

URL filter policy ID: 230f47be-63f4-4ae0-a488-b72a8d841b1f

AV policy ID: 00000000-0000-0000-0000-000000000000.

日志说明

用户进行了创建防火墙规则的操作

失败原因

当操作失败时,可能的原因如下:

·     The configuration item already exists:配置项已存在

·     The tenant specified for the configuration item doesn't exist:配置项指定的租户不存在

·     The tenant IDs for the configuration items are different配置项租户ID