H3C VCFC-Campus Operation Log Messages Reference-5W100

HomeSupportResource CenterSDNH3C SeerEngine-CampusH3C SeerEngine-CampusTechnical DocumentsReference GuidesLog Message ReferencesH3C VCFC-Campus Operation Log Messages Reference-5W100
Download Book
Table of Contents
Related Documents

Contents

Introduction· 1

Viewing operation log messages· 1

Syslog message format 2

Using this document 4

Campus· 5

Create isolation domain· 5

Update isolation domain· 6

Delete isolation domain· 6

Create private network· 7

Update private network· 8

Delete private network· 8

Create security group· 9

Update security group· 10

Delete security group· 11

Create subnet 12

Update subnet 13

Delete subnet 13

Bind security group to access scenario· 14

Unbind security group from access scenario· 14

Modify access scenario priority· 15

Create authentication server 16

Update authentication server 16

Delete authentication server 17

Smooth EIA· 17

Create resource group· 18

Update resource group· 19

Delete resource group· 19

CON_APP·· 20

Install application· 20

Start application· 20

Stop application· 20

Uninstall application· 21

Upload application· 21

CON_AUTH·· 22

Add an API authentication-free IP· 22

Delete an API authentication-free IP· 22

Add an IP address to white list 23

Delete an IP address from white list 23

CON_LICENSE·· 24

Connect the license server 24

Disconnect the license server 24

Upload license file· 25

Update the quantity of requested licenses· 25

CON_LISTENER·· 26

Register alert topic· 26

Update alert topic· 26

Remove alert topic· 27

CON_NetworkMonitor 28

Change thresholds for a CPU· 29

Change thresholds for all CPUs· 30

CON_OAM·· 31

Create radar detection task· 31

Delete radar detection task· 32

Clear periodic radar detection tasks· 32

CON_OPENFLOW··· 33

Create flow table entry· 33

Modify flow table entry· 33

Delete flow table entry· 34

Devices change to fail-safe mode· 34

Devices change to normal mode· 34

CON_REGION·· 35

Create region· 35

Delete region· 36

Update region· 37

CON_SNMP·· 38

Create traditional NE· 38

Update traditional NE· 39

Delete traditional NE· 39

Start scanning traditional NE· 40

Stop scanning traditional NE· 40

CON_SYSTEM·· 41

Back up configuration· 41

Upload backup file· 41

Start recovery· 42

Download backup file· 42

Modify backup settings· 43

Modify configuration· 43

Restore configuration· 44

Prepare for upgrade· 44

Modify alert log remote transmission mode· 45

Modify audit log transmission mode· 45

Enter upgrade mode· 45

Quit upgrade mode· 46

CON_TEAM·· 47

Create team·· 47

Delete team·· 48

Modify team·· 48

Add member 49

Delete member 49

Modify member 50

CON_TOPOLOGY· 51

Update device· 51

Update device layer 51

Delete inactive link· 52

Update port thresholds· 52

Clear events on a device· 53

Clear events on all devices· 53

CON_USER·· 54

Add a user 54

Delete a user 54

Change user password· 55

Update user config· 56

Add a role· 57

Update a role· 58

Delete a role· 59

DHCP·· 60

Create DHCP server 60

Update DHCP server 61

Delete DHCP server 61

Synchronize data from DHCP server 62

DHCP address pool 63

Create DHCP address pool 63

Delete DHCP address pool 64

General Group· 65

Create general group· 65

Update general group· 65

Delete general group· 66

Add device to device group· 66

Delete device from device group· 67

Add interface to interface group· 67

Delete interface from interface group· 68

Bind policy· 68

Unbind policy· 69

IDM·· 70

Add NETCONF template· 70

Update NETCONF template· 72

Delete NETCONF template· 74

Add configuration file· 75

Delete configuration file· 76

Deploy configuration snippets· 76

Deploy commands· 77

Start automatic configuration process· 77

Stop automatic configuration process· 78

Add SNMP template· 79

Delete SNMP template· 80

Update SNMP template· 81

Add aggregate interface· 82

Update aggregate interface· 83

Configure aggregate interface· 84

Add automated configuration template· 85

Add automation parameters· 87

Add automation policy· 88

Bring up interfaces· 89

Shut down interfaces· 90

Configure interface· 91

Add automatic device replacement task· 92

Add fabric and deploy resource pool 93

NBAC·· 95

Create Application Description· 96

Update Application Description· 97

Delete Application Description· 98

Create Policy· 99

Update Policy· 100

Delete Policy· 101

Create Rule· 102

Update Rule· 103

Delete Rule· 104

Create Time Range· 105

Update Time Range· 106

Delete Time Range· 107

NEM·· 108

Create VLAN-VXLAN mapping table· 108

Update VLAN-VXLAN mapping table· 109

Delete VLAN-VXLAN mapping table· 110

Create QinQ-VXLAN mapping table· 111

Update QinQ-VXLAN mapping table· 113

Delete QinQ-VXLAN mapping table· 114

Bind VLAN-VXLAN mapping table· 115

Update VLAN-VXLAN mapping table binding· 116

Delete VLAN-VXLAN mapping table binding· 117

Bind ports to VLAN-VXLAN mapping table· 118

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

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

Bind ports to QinQ-VXLAN mapping table· 121

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

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

Create gateway group· 124

Update gateway group· 126

Delete gateway group· 128

Create IP address pool 129

Update IP address pool 131

Delete IP address pool 132

Create gateway group VLAN range· 133

Update gateway group VLAN range· 134

Delete gateway group VLAN range· 134

Create VXLAN pool 135

Update VXLAN pool 136

Delete VXLAN pool 137

Create physical NE· 138

Update physical NE· 140

Delete physical NE· 142

Batch add physical NEs· 142

Start scanning physical NE· 143

Stop scanning physical NE· 143

Start migration on physical gateway· 143

Complete migration on physical gateway· 144

Start data synchronization on physical NE· 144

Start configuration auditing on physical NE· 145

Start data synchronization on virtual NE· 145

Start configuration auditing on virtual NE· 146

Create NETCONF default user 146

Configure default MAC address· 147

Delete default MAC address· 147

Create third party NE· 148

Delete third party NE· 149

Configure reserved option· 149

Create address pool 150

Update address pool 151

Delete address pool 152

Add resource· 153

Delete resource· 155

Configure VNFM·· 156

Configure gateway network· 157

Update gateway network· 157

Router bound to gateway· 158

Create aggregation group member 159

Update aggregation group member 160

Delete aggregation group member 161

Create aggregation group· 162

Update aggregation group· 163

Delete aggregation group· 163

Create global aggregation group configuration· 164

Update global aggregation group configuration· 165

Delete global aggregation group configuration· 165

Delete NE VXLAN tunnels· 166

Create connection limit rule· 167

Update connection limit rule· 168

Delete connection limit rule· 169

Create device configuration template· 170

Update device configuration template· 173

Delete device configuration template· 175

Create control protocol template· 176

Update control protocol template· 177

Delete control protocol template· 178

Create deploy resource pool 178

Update deploy resource pool 180

Delete deploy resource pool 181

Create auto detected· 182

Stop auto detected· 183

Delete auto detected· 183

Update global setting· 183

Create DHCP server 184

Update DHCP server 185

Delete DHCP server 185

Upload software· 186

Update software· 187

Delete software· 188

Upgrade software· 189

Replace physical NE· 190

Create tenant-gateway binding relationship· 191

Update tenant-gateway binding relationship· 192

Delete tenant-gateway binding relationship· 193

Create gateway· 194

Update gateway· 196

Delete gateway· 198

Create gateway member 199

Update gateway member 200

Delete gateway member 201

Create device whitelist 201

Update device whitelist 202

Delete device whitelist 202

Delete assetlist 203

Create egress interface· 203

Update egress interface· 204

Delete egress interface· 204

Create external connectivity· 205

Update external connectivity· 205

Delete external connectivity· 206

Add AAA template· 207

Update AAA template· 209

Delete AAA template· 210

Add MAC template· 211

Update MAC template· 213

Delete MAC template· 214

Add 802.1X template· 215

Update 802.1X auth template· 217

Delete 802.1X auth template· 218

ServiceChain· 219

Create service chain· 220

Update service chain· 222

Delete service chain· 223

Create context 224

Update context 225

Delete context 226

VSM·· 227

Create VDS· 227

Update VDS· 228

Delete VDS· 229

Add host 230

Update host 231

Delete host 231

Create vRouter 232

Update vRouter 233

Delete vRouter 234

Create internal route· 235

Delete internal route· 235

Create interface· 236

Delete interface· 237

Create network· 238

Update network· 239

Delete network· 240

Create subnet 241

Update subnet 242

Delete subnet 243

Create network policy· 243

Update network policy· 244

Delete network policy· 244

Create security policy· 245

Update security policy· 245

Delete security policy· 246

Create floating IP· 247

Update floating IP· 249

Delete floating IP· 250

Create port group· 250

Update port group· 251

Delete port group· 251

Create security rules· 252

Update security rule· 253

Delete security rule· 254

Authenticate with vCenter 254

Disconnect with vCenter 255

Upload vib· 255

Delete vib· 255

Install VFE· 256

Update VFE· 256

Uninstall VFE· 256

Create domain· 257

Update domain· 258

Delete domain· 258

Create vPort 259

Update vPort 261

Delete vPort 262

Create router link· 263

Update router link· 263

Delete router link· 264

Create route table· 264

Update route table· 265

Delete route table· 265

Create route entry· 266

Update route entry· 266

Delete route entry· 267

Create APP cluster VIP· 267

Update APP cluster VIP· 268

Delete APP cluster VIP· 268

Create flooding domain· 269

Update flooding domain· 270

Delete flooding domain· 270

Update vCenter status· 271

Create port name prefix· 271

Delete vPort prefix name· 271

Update advanced setting· 272

Create netoverlay host 272

Delete netoverlay host 273

Update netoverlay host 273

Create netoverlay group· 274

Delete netoverlay group· 274

Create VLAN-VXLAN map· 275

Delete VLAN-VXLAN map· 275

Configure batch vSwitch deployment parameters· 276

Import host file· 276

Run custom script 276

Export host file· 277

Export SSH key· 277

Upload custom script 277

Install vSwitch· 278

Update vSwitch· 278

Uninstall vSwitch· 279

Check host status· 279

Upload vSwitch file· 279

Delete vSwitch file· 280

Create network nodes· 280

Update network node· 281

Delete network node· 281

Update global default action· 281

Create DFW policy· 282

Update DFW policy· 282

Delete DFW policy· 283

Create DFW policy rule· 284

Delete DFW policy rule· 286

Create DFW IP set 286

Update DFW IP set 287

Delete DFW IP set 287

Create DFW IP set rule· 288

Delete DFW IP set rule· 288

Track flow entry of IP packet 289

Track flow entry of ARP packet 290

Start auditing on host 291

Start synchronization on host 291

Created static link· 292

Deleted static link· 292

Create vRouter interconnection· 293

Update vRouter interconnection· 294

Delete vRouter interconnection· 295

Create Layer 2 DC interconnection· 295

Update Layer 2 DC interconnection· 296

Delete Layer 2 DC interconnection· 296

Create Layer 3 DC interconnection· 297

Update Layer 3 DC interconnection· 299

Delete Layer 3 DC interconnection· 300

Add subnet to Layer 3 DC interconnection· 300

Delete Layer 3 DC interconnection subnet 301

Upload the vSwitch license file· 301

Updated host load limit 302

 


Introduction

Operation logs record system operations and configuration modifications, such as device operations (adding, modifying, or deleting a device) and policy configuration. Operation log messages include operation description, result, and failure reasons, and provide reference for system analysis and maintenance.

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

Viewing operation log messages

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

1.     Log in to SNA Center.

2.     Click Settings.

3.     On the top navigation bar, click Logs.

4.     From the navigation pane, select Information.

5.     Click the Operation Logs tab.

6.     Select VCFCCampus from the SNA Component Name list, and click Query.

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

Figure 1 Operation log messages

 

Table 1 Operation log message elements

Element

Description

Time

Date and time when the log message was generated.

SNA Component Name

Name of the SNA component that produced the message. The name of the VCFC-Campus component is VCFCCampus.

Username

Name of the user that triggered the log generation.

User IP

IP address of the terminal where the user performed the operation.

Host Name

Name of the host that produced the message.

Service Name

Name of the service that produced the message.

Module Name

Name of the module that produced the message.

Operation Result

Operation result: Succeeded or Failed.

Operation Description

Text string that contains detailed information about the operation.

Failure Reason

Possible reasons for an operation failure.

 

Syslog message format

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

1.     On the top navigation bar, click Logs.

2.     From the navigation pane, select Configuration.

3.     Click the Operation Logs tab.

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

By default, controllers send operation logs in the following format:

<PRI>TIMESTAMP Hostname Origin/severity/Keywords CONTENT

Table 2 Syslog message elements

Element

Description

<PRI>

Priority identifier. It is calculated by using the following formula:

Priority identifier=facilityx8+severity

Where:

·     Facility represents the programming module defined by syslog. In the current software version, the facility is user-level and its value is 1.

·     Severity represents the syslog message severity level. For more information, see Table 4.

TIMESTAMP

Date and time when the event occurred.

Hostname

Name or IP address of the server or virtual machine where the controller that produced the message resides.

Origin

Name of the service module that produced the message.

severity

Severity level of the message. For more information, see Table 5. For more information about the mappings between operation log message severity levels and syslog message severity levels, see Table 6.

Keywords

Keywords of the message that facilitate searching or memorizing.

CONTENT

Text string that contains detailed information about the operation, in the following format:

User=username IP=user IP Description=description Result=result Cause=operation failure causes

 

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

Table 3 Service module list

Service module name

Description

Campus

Policy management module.

CON_APP

Application management module.

CON_AUTH

Authentication management module.

CON_LICENSE

License management module.

CON_LISTENER

Listener module.

CON_NetworkMonitor

Network monitoring module.

CON_OAM

OAM module.

CON_OPENFLOW

OpenFlow module.

CON_REGION

Region module.

CON_SNMP

SNMP module.

CON_SYSTEM

System management module.

CON_TEAM

Team module.

CON_TOPOLOGY

Topology management module.

CON_USER

User management module.

DHCP

DHCP module.

Fabric

Fabric module

GeneralGroup

General group module.

IDM

Integrated deployment module.

NBAC

Network-based access control module.

NEM

Carrier network module.

ServiceChain

Service chain module.

VSM

Virtual network module.

 

Syslog messages are classified into eight severity levels from 0 to 7. The lower the number, the higher the severity, as shown in Table 4.

Table 4 Syslog message severity levels

Level

Severity

Description

0

Emergency

The system is unusable.

1

Alert

Action must be taken immediately.

2

Critical

Critical condition.

3

Error

Error condition.

4

Warning

Warning condition.

5

Notice

Normal but significant condition.

6

Informational

Informational message.

7

Debug

Debugging message.

 

Operation log messages are classified into two severity levels, as shown in Table 5.

Table 5 Operation log message severity levels

Level

Severity

Description

0

Info

Information message. It indicates that the operation succeeded.

1

Warning

Warning condition. It indicates that the operation failed.

 

Table 6 shows the mappings between operation log message severity levels and syslog message severity levels.

Table 6 Severity level mappings

Operation log message severity level

Syslog message severity level

0

6

1

4

 

Using this document

This document categorizes operation log messages by service module. This document explains messages in tables. Table 7 describes information provided in these tables.

Table 7 Message explanation table contents

Item

Content

Example

Keyword

Summary of the message that facilitates searching or memorizing.

DELETE_FABRIC_OP

Message text

Presents the message description.

Deleted fabric: $1

Variable fields

Briefly describes the variable fields in the order that they appear in the message text.

The variable fields are numbered in the "$Number" form to help you identify their location in the message text.

$1: Fabric UUID.

Example

Provides a real message example.

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

Explanation

Explains the message.

A fabric was deleted.

Possible failure causes

Provides possible causes of an operation failure.

·     Configuration recovery is in progress.

·     The service has not been found.

·     The controller is not the active leader.

·     The fabric does not exist.

·     Unknown error.

·     The request is invalid.

·     The fabric has devices.

·     The fabric has border device groups.

·     

 


Campus

This section contains operation log messages of the campus module.

Create isolation domain

Keyword

CREATE_ISOLATE_DOMAIN_OP

Message text

Created isolation domain “$1”.

Variable fields

$1: Isolation domain name.

Example

Created isolation domain “domain1”.

Explanation

An isolation domain was created.

Possible failure causes

·     The request is invalid.

·     The controller is not the active leader.

·     Configuration recovery is in progress.

·     Unknown error.

·     The isolation domain name cannot exceed 62 characters.

·     The isolation domain name is required.

·     The isolation domain ID already exists.

·     The isolation domain name already exists.

·     Invalid VXLAN ID range.

·     Duplicated IDs exist for the isolation domains created in bulk.

·     Duplicated names exist for the isolation domains created in bulk.

·     The VLAN pool cannot be empty.

·     The VLAN pool does not exist.

·     Failed to create the isolation domain. Errors occurred during tenant creation.

·     The DHCP server does not exist.

·     The service is disabled.

 

Update isolation domain

Keyword

UPDATE_ISOLATE_DOMAIN_OP

Message text

Updated isolation domain “$1”.

Variable fields

$1: Isolation domain name.

Example

Updated isolation domain “domain1”.

Explanation

An isolation domain was updated.

Possible failure causes

·     The request is invalid.

·     The controller is not the active leader.

·     Configuration recovery is in progress.

·     Unknown error.

·     The isolation domain does not exist.

·     The VXLAN ID range cannot be modified.

·     The isolation domain name cannot be modified.

·     The VLAN pool cannot be empty.

·     Cannot modify the VLAN pool because the isolation domain has security groups.

·     The VLAN pool does not exist.

·     Failed to modify the isolation domain. Errors occurred during the DHCP server update process.

·     The service is disabled.

·     Failed to synchronously create the address pool. An address pool with the same name already exists.

·     Failed to synchronously create the address pool. An address pool with the same network segment already exists.

 

Delete isolation domain

Keyword

DELETE_ISOLATE_DOMAIN_OP

Message text

Deleted isolation domain “$1”.

Variable fields

$1: Isolation domain name.

Example

Deleted isolation domain “domain1”.

Explanation

An isolation domain was deleted.

Possible failure causes

·     The request is invalid.

·     The controller is not the active leader.

·     Configuration recovery is in progress.

·     Unknown error.

·     Failed to delete the isolation domain because the isolation domain has private networks.

·     The isolation domain is the default isolation domain and cannot be deleted.

·     The service is disabled.

 

Create private network

Keyword

CREATE_PRIVATE_NETWORK_OP

Message text

Created private network “$1”.

Variable fields

$1: Private network name.

Example

Created private network “vpn1”.

Explanation

A private network was created.

Possible failure causes

·     The request is invalid.

·     The controller is not the active leader.

·     Configuration recovery is in progress.

·     The description cannot exceed 255 characters.

·     The L3VNI has been used.

·     VXLAN 4094 is reserved.

·     The IP address of the DNS server is invalid.

·     The VPN instance name is required.

·     The VPN instance name cannot exceed 31 characters.

·     The VPN instance name already exists.

·     The number of DNS servers on the DNS relay agent cannot exceed 8.

·     Duplicated DNS server IP addresses exist.

·     The isolation domain ID does not exist.

·     The private network name is required.

·     The private network name cannot exceed 255 characters.

·     The private network ID already exists.

·     The private network name already exists.

·     Unknown error.

·     The service is disabled.

·     No available VXLAN IDs.

 

Update private network

Keyword

UPDATE_PRIVATE_NETWORK_OP

Message text

Updated private network “$1”.

Variable fields

$1: Private network name.

Example

Updated private network “vpn1”.

Explanation

A private network was updated.

Possible failure causes

·     The request is invalid.

·     The controller is not the active leader.

·     Configuration recovery is in progress.

·     The private network does not exist.

·     The private network ID cannot be modified.

·     The private network name cannot be modified.

·     The isolation domain ID cannot be modified.

·     The VPN instance name cannot be modified.

·     The L3VNI cannot be modified.

·     The IP address of the DNS server is invalid.

·     The description cannot exceed 255 characters.

·     The number of DNS servers on the DNS relay agent cannot exceed 8.

·     Unknown error.

·     The service is disabled.

 

Delete private network

Keyword

DELETE_PRIVATE_NETWORK_OP

Message text

Deleted private network “$1”.

Variable fields

$1: Private network name.

Example

Deleted private network “vpn1”.

Explanation

A private network was deleted.

Possible failure causes

·     The controller is not the active leader.

·     Configuration recovery is in progress.

·     The private network ID does not exist.

·     The default private network cannot be deleted.

·     The private network cannot be deleted because it has security groups.

·     Unknown error.

·     The service is disabled.

 

Create security group

Keyword

CREATE_SECURITYGROUP_OP

Message text

Created security group “$1”.

Variable fields

$1: Security group name.

Example

Created security group “sg1”

Explanation

A security group was created.

Possible failure causes

·     The request is invalid.

·     The controller is not the active leader.

·     Configuration recovery is in progress.

·     The security group name is required.

·     The security group name cannot exceed 255 characters.

·     The private network ID is required.

·     The private network ID does not exist.

·     Invalid security group type.

·     The SSL VPN group ID is out of range.

·     The SSL VPN group ID already exists.

·     The IPv6 address mode is invalid.

·     VXLAN 4094 is reserved.

·     The VXLAN ID is out of range.

·     The VSI interface description cannot exceed 251 characters.

·     The VSI MAC address is invalid.

·     A maximum of seven ACs can be configured.

·     The IP address of the AC is invalid.

·     Duplicated IP addresses exist for the ACs.

·     The security group ID already exists.

·     Duplicated security group IDs exist for the security groups created in bulk.

·     The security group name already exists.

·     Duplicated security group names exist for the security groups created in bulk.

·     The VLAN ID of the security group is invalid.

·     The VXLAN ID has been used.

·     The VLAN ID has been used.

·     Unknown error.

·     The service is disabled.

·     No available VXLAN IDs.

 

Update security group

Keyword

UPDATE_SECURITYGROUP_OP

Message text

Updated security group “$1”.

Variable fields

$1: Security group name.

Example

Updated security group ”sg1”

Explanation

A security group was updated.

Possible failure causes

·     The request is invalid.

·     The controller is not the active leader.

·     Configuration recovery is in progress.

·     The specified resource doesn't exist.

·     The security group ID cannot be modified.

·     The private network ID cannot be modified.

·     The security group type cannot be modified.

·     The subnets cannot be modified.

·     The IPv6 address mode cannot be modified.

·     The VLAN ID cannot be modified.

·     The VXLAN ID cannot be modified.

·     The ARP proxy settings cannot be modified.

·     The VSI interface description cannot be modified.

·     The VSI MAC address cannot be modified.

·     The ARP check settings cannot be modified.

·     The IP addresses of the ACs cannot be modified.

·     The IGMP snooping settings cannot be modified.

·     The DHCP enabling state is required.

·     The Layer 2 application settings cannot be modified.

·     The SSL VPN group ID cannot be modified.

·     The security group name already exists.

·     Unknown error.

·     The service is disabled.

·     Failed to modify the security group. The security group is being used by the authentication server.

 

Delete security group

Keyword

DELETE_SECURITYGROUP_OP

Message text

Deleted security group “$1”.

Variable fields

$1: Security group name.

Example

Deleted security group ”sg1”.

Explanation

A security group was deleted.

Possible failure causes

·     The controller is not the active leader.

·     Configuration recovery is in progress.

·     The specified resource doesn't exist.

·     Failed to delete the security group. The security group is being used by the authentication server.

·     Unknown error.

·     The service is disabled.

 

Create subnet

Keyword

CREATE_SUBNET_OP

Message text

Created subnet “$1”

Variable fields

$1: Subnet name.

Example

Created subnet “sd”

Explanation

A subnet was created.

Possible failure causes

·     The request is invalid.

·     The controller is not the active leader.

·     Configuration recovery is in progress.

·     The subnet name is required.

·     The IP version of the subnet is invalid.

·     The CIDR already exists.

·     Only one IPv4 primary subnet is allowed.

·     Only one IPv6 subnet can be configured and the IPv6 subnet must be used as the primary subnet.

·     The number of DNS servers on the DNS relay agent cannot exceed 8.

·     Cannot configure DNS servers for secondary subnets.

·     The IP address of the DNS server is invalid.

·     Duplicated DNS server IP addresses exist.

·     The CIDR is required.

·     The IP address of the subnet gateway is required.

·     The IP address of the subnet gateway is invalid.

·     The IP address of the subnet gateway does not belong to the CIDR.

·     The subnet gateway IP address and the subnet broadcast IP address cannot be the same.

·     The subnet address and the gateway address cannot be the same.

·     Invalid CIDR.

·     Subnets of the same private network cannot overlap with each other.

·     The subnet name cannot exceed 255 characters.

·     The security group ID is required.

·     The security group ID does not exist.

·     The subnet ID already exists.

·     Duplicated subnet IDs exist for the subnets created in bulk.

·     Unknown error.

·     The service is disabled.

  

Update subnet

Keyword

UPDATE_SUBNET_OP

Message text

Updated subnet “$1”

Variable fields

$1: Subnet name.

Example

Updated subnet “sd”

Explanation

A subnet was updated.

Possible failure causes

·     The controller is not the active leader.

·     Configuration recovery is in progress.

·     The specified resource doesn't exist.

·     The subnet ID cannot be modified.

·     The subnet name cannot be modified.

·     The security group ID cannot be modified.

·     The IP version of the subnet cannot be modified.

·     The CIDR of the subnet cannot be modified.

·     The IP address of the subnet gateway cannot be modified.

·     The secondary field cannot be modified.

·     Unknown error.

·     The service is disabled.

 

Delete subnet

Keyword

DELETE_SUBNET_OP

Message text

Deleted subnet “$1”.

Variable fields

$1: Subnet name.

Example

Deleted subnet “sd”.

Explanation

A subnet was deleted.

Possible failure causes

·     The controller is not the active leader.

·     Configuration recovery is in progress.

·     The specified resource doesn't exist.

·     Unknown error.

·     The service is disabled.

 

Bind security group to access scenario

Keyword

ACCESS_STRATEGY_ADD_SECURITY_GROUP_OP

Message text

Bound security group $3 to access scenario $2 for user group $1.

Variable fields

$1: User group ID.

$2: Access scenario ID.

$3: Security group ID.

Example

Bound security group $3 to access scenario $2 for user group $1.

Explanation

A security group was bound to an access scenario in a user group.

Possible failure causes

·     The controller is not the active leader.

·     Configuration recovery is in progress.

·     Unknown error.

·     The operation requires the administrator privilege.

·     No security group is specified.

·     The security group does not exist.

·     The user group does not exist.

·     No user group is specified.

·     The access scenario does not exist.

·     No access scenario is specified.

·     The service is disabled.

 

Unbind security group from access scenario

Keyword

ACCESS_STRATEGY_DEL_SECURITY_GROUP_OP

Message text

Unbound the security group from access scenario $2 for user group $1.

Variable fields

$1: User group ID.

$2: Access scenario ID.

Example

Unbound the security group from access scenario $2 for user group $1.

Explanation

A security group was unbound from an access scenario in a user group.

Possible failure causes

·     The controller is not the active leader.

·     The operation requires the administrator privilege.

·     Configuration recovery is in progress.

·     Unknown error.

·     The user group does not exist.

·     No user group is specified.

·     The access scenario does not exist.

·     No access scenario is specified.

·     The service is disabled.

 

Modify access scenario priority

Keyword

SERVICE_STRATEGY_CHANGE_PRIORITY_OP

Message text

Modified access scenario priorities for user groups “$1”

Variable fields

$1: Set of user groups.

Example

Modified access scenario priorities for user groups “userAccessGroups”.

Explanation

The access scenario priorities were modified in user groups.

Possible failure causes

·     The controller is not the active leader.

·     The operation requires the administrator privilege.

·     Configuration recovery is in progress.

·     Unknown error.

·     Nonexistent user groups have been specified.

·     The user group is required .

·     Nonexistent access scenarios have been specified.

·     The access scenario is required.

·     A priority is required for an access scenario.

·     Cannot modify the priority of the default access scenario.

·     The service is disabled.

 

Create authentication server

Keyword

ADD_AUTH_OP

Message text

Created authentication server “$1”

Variable fields

$1: Authentication server ID.

Example

Created authentication server “ffffffff-0000-0000-0000-000000000012”

Explanation

An authentication server was created.

Possible failure causes

·     The request is invalid.

·     The controller is not the active leader.

·     Configuration recovery is in progress.

·     The request is invalid.

·     The authentication server ID already exists.

·     The authentication server ID is required.

·     The authentication server IP is invalid.

·     The port number of the authentication server is required.

·     The port number of the authentication server is invalid.

·     The authentication server with the IP address and port number already exists.

·     The authentication server type is required.

·     The authentication server type already exists.

·     The authentication server password is required.

·     The authentication server password cannot exceed 255 characters.

·     The authentication server username is required.

·     The authentication server username cannot exceed 255 characters.

·     The service is disabled.

 

Update authentication server

Keyword

UPDATE_AUTH_OP

Message text

Updated authentication server “$1”

Variable fields

$1: Authentication server ID.

Example

Updated authentication server “ffffffff-0000-0000-0000-000000000012”

Explanation

An authentication server was modified.

Possible failure causes

·     The controller is not the active leader.

·     Configuration recovery is in progress.

·     Unknown error.

·     The authentication server ID does not exist.

·     The authentication server ID cannot be modified.

·     The authentication server type cannot be modified.

·     The service is disabled.

 

Delete authentication server

Keyword

DELETE_AUTH_OP

Message text

Deleted authentication server “$1”

Variable fields

$1: Authentication server ID.

Example

Deleted authentication server “ffffffff-0000-0000-0000-000000000012”

Explanation

An authentication server was deleted.

Possible failure causes

·     The controller is not the active leader.

·     Configuration recovery is in progress.

·     Unknown error.

·     The authentication server ID does not exist.

·     The service is disabled.

 

Smooth EIA

Keyword

SMOOTH_EIA_OP

Message text

Smoothed EIA authentication server “$1”.

Variable fields

$1: Authentication server ID.

Example

Smoothed EIA authentication server “ffffffff-0000-0000-0000-000000000012”.

Explanation

The EIA authentication server was synchronized.

Possible failure causes

·     The controller is not the active leader.

·     Configuration recovery is in progress.

·     Unknown error.

·     Failed to synchronize security group information to the authentication server.

·     Failed to synchronize user role information to the authentication server.

·     Failed to synchronize link information to the authentication server.

·     Failed to synchronize IP binding information from the authentication server to the DHCP server.

 

Create resource group

Keyword

CREATE_RESOURCEGROUP_OP

Message text

Created resource groups “$1”

Variable fields

$1: Resource group name.

Example

Created resource groups ”resourceGroup1”

Explanation

A resource group was created.

Possible failure causes

·     The request is invalid.

·     The controller is not the active leader.

·     Configuration recovery is in progress.

·     The description cannot exceed 255 characters.

·     The resource group ID already exists.

·     The resource group name is required.

·     The resource group name cannot exceed 255 characters.

·     The resource group name already exists.

·     The specified private network does not exist.

·     The resource pool is required.

·     The resource pool type is required.

·     Invalid resource pool type.

·     You must configure IP settings for the resource pool.

·     The IP settings of the resource pool are invalid.

·     The number of IP address ranges in the resource pool cannot exceed 253.

·     The end IP must be higher than the start IP.

·     IP address ranges in the resource pool cannot overlap.

·     Duplicated IDs exist for the resource groups created in bulk.

·     Duplicated names exist for the resource groups created in bulk.

·     The service is disabled.

 

Update resource group

Keyword

UPDATE_RESOURCEGROUP_OP

Message text

Updated resource group “$1”

Variable fields

$1: Resource group name.

Example

Updated resource group “resourceGrpoup1”

Explanation

A resource group was updated.

Possible failure causes

·     The controller is not the active leader.

·     Configuration recovery is in progress.

·     Unknown error.

·     The description cannot exceed 255 characters.

·     The specified resource group does not exist.

·     The resource group ID cannot be modified.

·     The resource group name cannot be modified.

·     The private network ID cannot be modified.

·     The resource pool is required.

·     The resource pool type is required.

·     Invalid resource pool type.

·     IP address ranges in the resource pool cannot overlap.

·     The service is disabled.

 

Delete resource group

Keyword

DELETE_RESOURCEGROUP_OP

Message text

Deleted resource group “$1”

Variable fields

$1: Resource group name.

Example

Deleted resource group “resourceGroup1”

Explanation

A resource group was deleted.

Possible failure causes

·     The controller is not the active leader.

·     Configuration recovery is in progress.

·     Unknown error.

·     The specified resource group does not exist.

·     The resource group is being used by an application description and cannot be deleted.

·     The service is disabled.

 


CON_APP

This section contains CON_APP messages.

Install application

Keyword

INSTALL_APP_OP

Message text

$1 had been installed.

Variable fields

$1: Application name.

Example

H3C VCFC ARP had been installed.

Explanation

An application was installed.

Possible failure causes

N/A

 

Start application

Keyword

START_APP_OP

Message text

$1 had been started.

Variable fields

$1: Application name.

Example

H3C VCFC ARP had been started.

Explanation

An application was started.

Possible failure causes

N/A

 

Stop application

Keyword

STOP_APP_OP

Message text

$1 had been stopped.

Variable fields

$1: Application name.

Example

H3C VCFC ARP had been stopped.

Explanation

An application was stopped.

Possible failure causes

N/A

 

Uninstall application

Keyword

REMOVE_APP_OP

Message text

$1 had been removed.

Variable fields

$1: Application name.

Example

H3C VCFC ARP had been removed.

Explanation

An application was uninstalled.

Possible failure causes

N/A

 

Upload application

Keyword

UPLOAD_APP_OP

Message text

Uploaded application: $1.

Variable fields

$1: Name of the application installation package.

Example

Uploaded application: arp-2156.zip.

Explanation

An application installation package was uploaded.

Possible failure causes

·     Unsigned or untrusted jars contained within.

·     Bad application package.

·     The number of applications exceeded the license limit.

·     The application already exists.

·     An unknown error occurs during the application package uploading process.

 


CON_AUTH

This section contains CON_AUTH messages.

Add an API authentication-free IP

Keyword

ADD_API_AUTH_FREEIP_OP

Message text

Added an API authentication-free IP: $1

Variable fields

$1: IP address of the API authentication-free user.

Example

Added an API authentication-free IP: 192.168.56.13

Explanation

An API authentication-free user was added.

Possible failure causes

·     Invalid IP address.

·     The IP address already exists.

·     The controller is not the active leader.

·     Unknown error.

·     Invalid role.

·     Invalid type

·     Invalid description.

 

Delete an API authentication-free IP

Keyword

DELETE_API_AUTH_FREEIP_OP

Message text

Deleted an API authentication-free IP: $1

Variable fields

$1: IP address of the API authentication-free user.

Example

Deleted an API authentication-free IP: 192.168.56.13

Explanation

An API authentication-free user was deleted.

Possible failure causes

·     The controller is not the active leader.

·     Unknown error.

·     Invalid IP address.

·     Invalid type

·     The IP address does not exist.

 

Add an IP address to white list

Keyword

ADD_IP_TO_WHITELIST_OP

Message text

Added IP address $1 to the white list.

Variable fields

$1: IP address added to the white list.

Example

Added IP address 192.168.56.13 to the white list.

Explanation

A user was added to the white list.

Possible failure causes

·     Invalid IP address.

·     The IP address already exists.

·     The controller is not the active leader.

·     Unknown error.

·     Invalid type.

·     Invalid description.

 

Delete an IP address from white list

Keyword

DELETE_IP_FROM_WHITELIST_OP

Message text

Deleted IP address $1 from the white list.

Variable fields

$1: IP address removed from the white list.

Example

Deleted IP address 192.168.56.13 from the white list.

Explanation

A user was removed from the white list.

Possible failure causes

·     Invalid IP address.

·     The controller is not the active leader.

·     The IP address does not exist.

·     Unknown error.

·     Invalid type.

 

 


CON_LICENSE

This section contains CON_LICENSE messages.

Connect the license server

Keyword

CONNECT_LICS_OP

Message text

Connected the license server: $1

Variable fields

$1: License server configuration information.

Example

Connected the license server:

License server IP: 192.168.40.40

Port: 5555

Username: sdn

Password: ******

Explanation

The user connected the controller to the license server.

Possible failure causes

·     Incorrect license server IP address or port number.

·     Incorrect username or password.

 

Disconnect the license server

Keyword

DISCONNECT_LICS_OP

Message text

Disconnected the license server: $1

Variable fields

$1: License server IP address.

Example

Disconnected the license server: 192.168.1.1

Explanation

The user disconnected the controller from the license server.

Possible failure causes

N/A

 

Upload license file

Keyword

UPLOAD_LICENSE_FILE_OP

Message text

Uploaded license file

Variable fields

N/A

Example

Uploaded license file

Explanation

A license file was uploaded.

Possible failure causes

License file error.

 

Update the quantity of requested licenses

Keyword

UPDATE_REQUESTED_LICENSES_OP

Message text

Updated the quantity of requested licenses: $1.

Variable fields

$1: Information about the quantity of requested licenses.

Example

Updated the quantity of requested licenses:

APP license: 1

MaxNodeNum license: 1

VirtualServiceNode license: 1

vSwitch license: 0

ZTP license: true

API license: true

Overlay license: true

OverlayHardwareEntity license: 1

ServiceChain license: true

Base license: 1.

Explanation

The quantity of requested licenses was changed.

Possible failure causes

Failed to save the configuration.

 

 


CON_LISTENER

This section contains CON_LISTENER messages.

Register alert topic

Keyword

REGISTER_ LISTENER_OP

Message text

Registered alert topic listener: $1

Variable fields

$1: Alert topic listener configuration.

Example

Registered alert topic listener:

{

    "alert":

    {

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

        "level": "warn",

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

        "app_name": "vnetcontroller",

        "push_history": true

    }

}

Explanation

An alert topic listener was registered.

Possible failure causes

A listener with the same app_name has already been registered.

 

Update alert topic

Keyword

UPDATE_LISTENER_OP

Message text

Updated alert topic listener: $1

Variable fields

$1: Alert topic listener configuration.

Example

Updated alert topic listener:

{

    "alert":

    {

        "app_name": "vnetcontroller",

        "level": "warn",

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

    }

}

Explanation

An alert topic listener was modified.

Possible failure causes

N/A.

 

Remove alert topic

Keyword

REMOVE_LISTENER_OP

Message text

Removed alert topic listener: $1

Variable fields

$1: Name of the alert topic listener.

Example

Removed alert topic listener: vnetcontroller

Explanation

An alert topic listener was removed.

Possible failure causes

N/A.

 


CON_NetworkMonitor

This section contains CON_NetworkMonitor messages.

Change thresholds for a CPU

Keyword

CHANGE_THRESHOLDS_OP

Message text

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

Variable fields

$1: CPU ID.

$2: Slot number.

$3: Chassis number.

$4: IP address of the device.

$5: Resource usage alarm thresholds.

Example

Changed network monitor thresholds for CPU 1 in slot 1 of chassis 1 on device 192.168.150.21:

  {

    cpuRecoveryThreshold: 10

    cpuMinorThreshold: 20

    cpuWarningThreshold: 40

    memorySecureThreshold: 10

    memoryEarlyWarningThreshold: 20

    memoryNormalThreshold: 30

    memoryMinorThreshold: 30

    memorySevereThreshold: 40

    memoryCriticalThreshold: 50

    aclMinorThreshold: 50

aclSevereThreshold: 60

acMinorThreshold: 20

acSevereThreshold: 40

vsiMinorThreshold: 20

vsiSevereThreshold: 40

vlanMinorThreshold: 20

vlanSevereThreshold: 40

  }

Explanation

The resource usage alarm thresholds were modified for a specific CPU.

Possible failure causes

·     The controller is not the active leader.

·     The device is not a physical device.

·     The device is offline.

·     The device does not exist.

·     The device does not support configuring CPU usage threshold.

·     The device does not support configuring memory usage threshold.

·     The device does not support configuring ACL resource usage threshold.

·     The device does not support configuring AC resource usage threshold.

·     The device does not support configuring VSI interface resource usage threshold.

·     The device does not support configuring VLAN interface resource usage threshold.

 

Change thresholds for all CPUs

Keyword

CHANGE_THRESHOLDS_ALL_OP

Message text

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

Variable fields

$1: IP address of the device.

$2: Resource usage thresholds.

Example

Changed network monitor thresholds for all CPUs on device 192.168.150.21:

  {

    cpuRecoveryThreshold: 10

    cpuMinorThreshold: 20

    cpuWarningThreshold: 40

    memorySecureThreshold: 10

    memoryEarlyWarningThreshold: 20

    memoryNormalThreshold: 30

    memoryMinorThreshold: 30

    memorySevereThreshold: 40

    memoryCriticalThreshold: 50

    aclMinorThreshold: 50

aclSevereThreshold: 60

acMinorThreshold: 20

acSevereThreshold: 40

vsiMinorThreshold: 20

vsiSevereThreshold: 40

vlanMinorThreshold: 20

vlanSevereThreshold: 40

  }

Explanation

The resource usage thresholds were modified for all CPUs.

Possible failure causes

·     The controller is not the active leader.

·     The device is not a physical device.

·     The device is offline.

·     The device does not exist.

·     The device does not support configuring CPU usage threshold.

·     The device does not support configuring memory usage threshold.

·     The device does not support configuring ACL resource usage threshold.

·     The device does not support configuring AC resource usage threshold.

·     The device does not support configuring VSI interface resource usage threshold.

·     The device does not support configuring VLAN interface resource usage threshold.

 


CON_OAM

This section contains CON_OAM messages.

Create radar detection task

Keyword

CREATE_RADAR_DETECTION_OP

Message text

Created radar detection task: $1

Variable fields

$1: Parameters for the radar detection task.

Example

Created radar detection task:

  Username: sdn

  Task type: multiple

  Task info:

  Path type: single

  Network type: vxlan

  Segment ID: 2

  Protocol: TCP

  Source IP: 70.68.68.68

  Source port: 10000

  Start device IP: 192.168.70.68

  Start device ingress port: 0x1

  Destination IP: 168.168.1.2

  Destination port: 50000

  End device IP: null

  DSCP: 62

  Interval: 0

  Packet count: 1

  Timeout: 10

  Period: 1440

  Frequency: 600

Explanation

A radar detection task was created.

Possible failure causes

·     The start device IP address doesn't exist.

·     Task already exists. Please try again later.

·     The controller hasn't obtained start device port information.

·     The start device ingress port doesn't exist.

·     The destination IP address doesn't exist.

·     The gateway device that source device belongs to doesn't exist.

·     The controller is not the active leader.

·     Can't find the vPort with the source IP address.

·     The number of periodic detection tasks has reached the maximum.

·     Radar detection is disabled.

·     The number of periodic radar detection tasks has reached the upper limit.

 

Delete radar detection task

Keyword

Delete_RADAR_DETECTION_OP

Message text

Deleted radar detection task: $1

Variable fields

$1: UUID of the radar detection task.

Example

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

Explanation

A radar detection task was deleted.

Possible failure causes

·     The controller is not the active leader.

·     Radar detection is disabled.

·     The periodic scanning task ID doesn’t match the username of the task creator.

 

Clear periodic radar detection tasks

Keyword

CLEAR_RADAR_DETECTION_OP

Message text

Clear all periodic radar detection tasks for user $1.

Variable fields

$1: Username.

Example

Clear all periodic radar detection tasks for user sdn.

Explanation

All periodic radar detection tasks created by the user were cleared.

Possible failure causes

·     The controller is not the active leader.

·     Radar detection is disabled.

 


CON_OPENFLOW

This section contains CON_OPENFLOW messages.

Create flow table entry

Keyword

CREATE_FLOWTABLE_OP

Message text

A flow table entry was added.

Variable fields

N/A

Example

A flow table entry was added.

Explanation

A flow table entry was added.

Possible failure causes

N/A

 

Modify flow table entry

Keyword

MODIFY_FLOWTABLE_OP

Message text

A flow table entry was modified.

Variable fields

N/A

Example

A flow table entry was modified.

Explanation

A flow table entry was modified.

Possible failure causes

N/A

 

Delete flow table entry

Keyword

DELETE_FLOWTABLE_OP

Message text

A flow table entry was deleted.

Variable fields

N/A

Example

A flow table entry was deleted.

Explanation

A flow table entry was deleted.

Possible failure causes

No such device: Datapath ID: OpenFlow network device has been disconnected.

 

Devices change to fail-safe mode

Keyword

CHANGE_DEVICE_FAILSAFE_OP

Message text

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

Variable fields

N/A

Example

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

Explanation

The fail-safe mode was set.

Possible failure causes

Abnormal connections between the active leader and other controllers in the team.

 

Devices change to normal mode

Keyword

CHANGE_DEVICE_NORMAL_OP

Message text

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

Variable fields

N/A

Example

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

Explanation

The normal mode was set.

Possible failure causes

Abnormal connections between the active leader and other controllers in the team.

 

 


CON_REGION

This section contains CON_REGION messages.

Create region

Keyword

CREATE_REGION_ OP

Message text

Created region: $1

Variable fields

$1: Region information.

Example

Created region:

Name:region1

Region ID:fdd9f2d3-d2b2-4afe-942f-e6943b54e259

DenyvSwitch:false

Master:192.168.56.153

Subordinate:

192.168.56.154

ManagedNodeSubnets:

         192.168.38.25/24

         192.168.39.25/24

Explanation

A region was created.

Possible failure causes

·     The team doesn't exist.

·     Incorrect controller IP address.

·     The region name is already used.

·     The controller was already in a region.

·     The controller is not the active leader.

·     Incorrect JSON format.

·     The request can't be null.

·     Incorrect controller name.

·     The master IP address must be different from the subordinate IP address.

·     Incorrect IP address or mask format for the managed node subnets.

 

Delete region

Keyword

DELETE_REGION_OP

Message text

Deleted region:$1

Variable fields

$1: Region information.

Example

Deleted region:

Name: region1

Region ID: fdd9f2d3-d2b2-4afe-942f-e6943b54e259

DenyvSwitch:false

Master:192.168.56.153

Subordinate:

192.168.56.154

ManagedNodeSubnets:

         192.168.38.25/24

         192.168.39.25/24

Explanation

A region was deleted.

Possible failure causes

·     The controller is not the active leader.

·     Incorrect JSON format.

·     The region does not exist.

 

Update region

Keyword

UPDATE_REGION_OP

Message text

Updated region:$1

Variable fields

$1: Region information.

Example

Updated region:

Name: region1

Region ID: fdd9f2d3-d2b2-4afe-942f-e6943b54e259

DenyvSwitch:false

Master:192.168.56.153

Subordinate:

192.168.56.154

ManagedNodeSubnets:

         192.168.38.25/24

         192.168.39.25/24

Explanation

A region was updated.

Possible failure causes

·     The region does not exist.

·     The controller is not the active leader.

·     Incorrect JSON format.

·     The request can't be null.

·     The input region information was incorrect.

·     Incorrect IP address or mask format for the managed node subnets.

 


CON_SNMP

This section contains CON_SNMP messages.

Create traditional NE

Keyword

CREATE_TRADITIONAL_NE_OP

Message text

Created traditional NE: $1

Variable fields

$1: Traditional NE configuration information.

Example

Created traditional NE:

IP: 192.168.9.198

MAC: 74:25:8a:c4:e2:de

Read community: public

Write community: private

Controller IP: 192.168.89.155

Access attribute: access

Status: Inactive

Explanation

The user added a traditional NE.

Possible failure causes

·     The controller is not the active leader.

·     Invalid network element IP address.

·     The traditional network element at X.X.X.X already exists.

·     Invalid controller IP address.

·     The controller IP address doesn't exist in the team.

·     The IP address for a controller in standalone mode must be 127.0.0.1.

·     Invalid access attribute.

·     The traditional network element has been added to the controller by using X.X.X.X.

 

Update traditional NE

Keyword

UPDATE_TRADITIONAL_NE_OP

Message text

Updated traditional NE: $1

Variable fields

$1: Traditional NE configuration information.

Example

Updated traditional NE:

IP: 192.168.9.198

MAC: 74:25:8a:c4:e2:de

Read community: public

Write community: private

Controller IP: 192.168.89.155

Access attribute: access

Status: Inactive

Explanation

The user modified the traditional NE.

Possible failure causes

·     The controller is not the active leader.

·     Invalid network element IP address.

·     The network element IP address doesn't exist.

·     Invalid controller IP address.

·     The controller IP address doesn't exist in the team.

·     The IP address for a controller in standalone mode must be 127.0.0.1.

·     Invalid access attribute.

·     Unknown error.

 

Delete traditional NE

Keyword

DELETE_TRADITIONAL_NE_OP

Message text

Deleted traditional NE: $1

Variable fields

$1: IP address of the traditional NE.

Example

Deleted traditional NE: 192.168.9.198

Explanation

The user deleted the traditional NE.

Possible failure causes

·     The controller is not the active leader.

·     Invalid network element IP address.

·     The network element IP address doesn't exist.

 

Start scanning traditional NE

Keyword

START_SCAN_TRADITIONAL_NE_OP

Message text

Started scanning traditional NEs: $1

Variable fields

$1: Settings for auto traditional NE scanning.

Example

Started scanning traditional NEs:

  Start IP: 192.168.125.0

  End IP: 192.168.125.255

  SNMP read community: public

  SNMP write community: private

Explanation

The user started auto traditional NE scanning.

Possible failure causes

N/A

 

Stop scanning traditional NE

Keyword

STOP_SCAN_TRADITIONAL_NE_OP

Message text

Stopped scanning traditional NEs

Variable fields

N/A

Example

Stopped scanning traditional NEs

Explanation

The user stopped auto traditional NE scanning.

Possible failure causes

N/A

 

 


CON_SYSTEM

This section contains CON_SYSTEM messages.

Back up configuration

Keyword

BACKUP_OP

Message text

Backed up the configuration.

Variable fields

$1: Session name.

Example

Backed up the configuration.

Explanation

A backup session was completed.

Possible failure causes

·     The operation requires the administrator privilege.

·     Failed to create the backup file.

·     The system is recovering the configuration.

·     The team to which the controller belongs has no active leader.

 

Upload backup file

Keyword

UPLOAD_BACKUPFILE_OP

Message text

Uploaded the backup file.

Variable fields

N/A

Example

Uploaded the backup file.

Explanation

A backup file was uploaded.

Possible failure causes

·     The controller is not the active leader.

·     The operation requires the administrator privilege.

·     Invalid backup file format.

·     Invalid backup file content.

·     The active leader can't send the backup file to other controllers due to network errors.

·     The system is recovering the configuration.

·     The team to which the controller belongs has no active leader.

·     Can’t upload the backup file because some controllers are down: $1, $2, $3.

 

Start recovery

Keyword

RESTORE_OP

Message text

Restored the configuration.

Variable fields

N/A

Example

Restored the configuration.

Explanation

A recovery was started.

Possible failure causes

·     The controller is not the active leader.

·     The operation requires the administrator privilege.

·     The backup file doesn't exist.

·     The backup file doesn't include the required files.

·     The controller's IP address is not included in the team settings of the backup file.

·     The active leader can't restore the configuration of other controllers due to network errors.

·     The system is recovering the configuration.

·     The team to which the controller belongs has no active leader.

·     Can’t perform configuration recovery because some controllers are down.

 

Download backup file

Keyword

DOWNLOAD_BACKUPFILE_OP

Message text

Downloaded the backup file.

Variable fields

N/A

Example

Downloaded the backup file.

Explanation

The backup file had been successfully downloaded.

Possible failure causes

·     The backup file doesn't exist.

·     The system is recovering the configuration.

·     The team to which the controller belongs has no active leader.

 

Modify backup settings

Keyword

MODIFY_BACKUPSET_OP

Message text

Modified settings for configuration backup.

Variable fields

N/A

Example

Modified settings for configuration backup.

Explanation

The settings for configuration backup were modified.

Possible failure causes

·     Illegal backup settings.

·     The operation requires the administrator privilege.

·     The controller is not the active leader.

·     Not permitted to access the backup path.

·     Failed to save the settings.

·     The system is recovering the configuration.

·     The team to which the controller belongs has no active leader.

 

Modify configuration

Keyword

MODIFY_CONFIG_OP

Message text

Modified configuration: $1.

Variable fields

$1: Component name and configuration items.

Example

Modified configuration: Authentication Manager {

ConnPoolMaxActive=4

AuthenticationProtocol=PAP

SharedKey=******

AuthMode=local

AAAServerIP=192.168.56.19

ConnPoolMaxIdle=1

CachedTokenIdle=900

}.

Explanation

The values for the configuration items of the specified component were modified. If a password or key is included in the component, it is displayed with asterisks (******).

Possible failure causes

·     Failed to update the configuration file.

·     The existing team token must be deleted before you configure a new one.

·     Invalid value for parameter $1.

·     Failed to encrypt the password or key.

 

Restore configuration

Keyword

RESTORE_CONFIG_OP

Message text

Restored configuration: $1.

Variable fields

$1: Component name and configuration items. If the values for all configuration items are restored, only the component name is displayed.

Example

Restored configuration: Authentication Manager {

ConnPoolMaxActive=4

AuthenticationProtocol=PAP

SharedKey=******

AuthMode=local

AAAServerIP=192.168.56.19

ConnPoolMaxIdle=1

CachedTokenIdle=900

}.

Explanation

The values for the configuration items of the specified component were restored to the default. If a password or key is included in the component, it is displayed with asterisks (******).

Possible failure causes

·     Can't delete the team token in team mode.

·     Failed to update the configuration file.

 

Prepare for upgrade

Keyword

UPGRADE_PREPARE_OP

Message text

Prepared for upgrade: $1

Variable fields

$1: IP address of the controller that prepares for upgrade.

Example

Prepared for upgrade

Explanation

Upgrade preparation was performed.

Possible failure causes

Invalid request.

 

Modify alert log remote transmission mode

Keyword

MODIFY_ALERTLOG_TRANSMISSION_OP

Message text

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

Variable fields

N/A

Example

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

Explanation

The user changed the system log settings by enabling the syslog server feature. System logs will be sent to the specified syslog server.

Possible failure causes

N/A

 

Modify audit log transmission mode

Keyword

MODIFY_AUDITLOG_TRANSMISSION_OP

Message text

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

Variable fields

N/A

Example

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

Explanation

The user changed the operation log settings by enabling the syslog server feature. Operation logs will be sent to the specified syslog server.

Possible failure causes

N/A

 

Enter upgrade mode

Keyword

ENTER_UPGRADE_MODE_OP

Message text

Enter upgrade mode.

Variable fields

N/A

Example

Enter upgrade mode.

Explanation

The operation for entering the upgrade mode was performed.

Possible failure causes

N/A

 

Quit upgrade mode

Keyword

QUIT_UPGRADE_MODE_OP

Message text

Quit upgrade mode.

Variable fields

N/A

Example

Quit upgrade mode.

Explanation

The operation for quitting the upgrade mode was performed.

Possible failure causes

N/A

 

 


CON_TEAM

This section contains CON_TEAM messages.

Create team

Keyword

CREATE_TEAM_OP

Message text

Created team: $1

Variable fields

$1: Configuration of the team.

Example

Created team:

Name: TestCluster1

IP: 192.168.40.40

Mask: 255.255.255.0

Mode:1

Version: 1404159495844

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

Leaders: [

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

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

]

Members: [

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

]

Explanation

A team was created.

Possible failure causes

·     The team contained only one leader.

·     The controller was not a leader.

·     Team IP address and member IP address must be different.

·     Member IP addresses must be different.

·     Member names must be different.

·     Leader priorities must be different.

·     The number of controllers exceeded the upper limit (32).

·     Server processing error.

·     The versions of the controllers are inconsistent.

·     The team token is not configured for the controller.

 

Delete team

Keyword

DELETE_TEAM_OP

Message text

Deleted team: $1

Variable fields

$1: Configuration of the team.

Example

Deleted team:

Name: TestCluster1

IP: 192.168.40.40

Explanation

A team was deleted.

Possible failure causes

·     The team didn't exist.

·     The controller was not the active leader.

·     Server processing error.

 

Modify team

Keyword

MODIFY_TEAM_OP

Message text

Modified team: $1

Variable fields

$1: Configuration modification of the team.

Example

Modified team:

Name:TestCluster1->TestCluster2

IP:192.168.35.11->192.168.35.12

Mask:255.255.255.0->255.255.0.0

Explanation

A team was modified.

Possible failure causes

·     The controller was not the active leader.

·     The team didn't exist.

·     Server processing error.

·     The team name is invalid.

 

Add member

Keyword

ADD_MEMBER_OP

Message text

Added member: $1

Variable fields

$1: Member information.

Example

Added member:

Name:leader1

IP:192.168.56.147

Explanation

A member was added.

Possible failure causes

·     The controller was not the active leader.

·     The team didn't exist.

·     The member IP address must be different from the team IP address.

·     The member IP address was already used.

·     The member name was already used.

·     Server processing error.

·     The version of the selected controller is different than the team.

 

Delete member

Keyword

DELETE_MEMBER_OP

Message text

Deleted member: $1

Variable fields

$1: Member information.

Example

Deleted member:

Name:leader1

IP:192.168.56.147

Explanation

A member was deleted.

Possible failure causes

·     The controller was not the active leader or the member to be deleted.

·     The member didn't exist.

·     A leader can't be deleted.

·     The member was in a region.

·     Server processing error.

 

Modify member

Keyword

MODIFY_MEMBER_OP

Message text

Modified member: $1

Variable fields

$1: Member modification information.

Example

Modified member:

Name:member1->member2

IP:192.168.35.11

Network_device:eth0->eth1

Explanation

A member was modified.

Possible failure causes

·     The controller was not the active leader.

·     NIC for the member can't be changed.

·     Server processing error.

·     The controller name is invalid.

·     The member name was already used.

 


CON_TOPOLOGY

This section contains CON_TOPOLOGY messages.

Update device

Keyword

UPDATE_DEVICE_INFO_OP

Message text

Updated device: $1

Variable fields

$1: Device information.

Example

Updated device:

IP address: 192.168.9.198

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

Asset number: 201605181600

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

Location: A13-A13

Function: core

Remarks: description

Device name: 201-98

Status: Inactive

Explanation

The user modified the device information on the device statistics page.

Possible failure causes

The device doesn't exist.

 

Update device layer

Keyword

UPDATE_DEVICE_LAYER_OP

Message text

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

Variable fields

$1: IP address of the device.

$2: Datapath ID of the device.

$3: Layer of the device. Options are access, convergence, and core.

Example

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

Explanation

The user modified the layer for the device specified on the physical topology page.

Possible failure causes

The device doesn't exist.

 

Delete inactive link

Keyword

DELETE_INACTIVE_LINK_OP

Message text

Deleted an inactive link. Link information: $1

Variable fields

$1: Inactive link information.

Example

Deleted an inactive link. Link information:

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

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

Explanation

The user deleted the inactive link for the device.

Possible failure causes

N/A

 

Update port thresholds

Keyword

UPDATE_PORT_THRESHOLD_OP

Message text

Updated port thresholds: $1

Variable fields

$1: Port thresholds.

Example

Updated port monitor thresholds:

  Inbound bandwidth usage: 12%

  Outbound bandwidth usage: 32%

  Inbound error packet rate: 43%

  Outbound error packet rate: 43%

  Inbound packet loss rate: 54%

  Outbound packet loss rate: 65%

Explanation

The user modified the port thresholds.

Possible failure causes

N/A

 

Clear events on a device

Keyword

CLEAR_DEVICE_EVENTS_OP

Message text

Clear events on device: $1.

Variable fields

$1: IP address of the device.

Example

Clear events on device: 192.168.5.3.

Explanation

The user cleared the events on a device.

Possible failure causes

The device doesn't exist.

 

Clear events on all devices

Keyword

CLEAR_ALL_DEVICES_EVENTS_OP

Message text

Clear events on all devices.

Variable fields

N/A

Example

Clear events on all devices.

Explanation

The user cleared the events on all devices.

Possible failure causes

N/A

 


CON_USER

This section contains CON_USER messages.

Add a user

Keyword

ADD_USER_OP

Message text

Added a user:$1.

Variable fields

$1: User name.

Example

Added a user:11.

Explanation

A user was added.

Possible failure causes

·     Invalid username.

·     The username already exists.

·     The password length is out of range or the password contains only letters, digits, or special characters.

·     Invalid role.

·     The controller is not the active leader.

·     Incorrect format.

·     Failed to add the user.

 

Delete a user

Keyword

DELETE_USER_OP

Message text

Deleted a user: $1.

Variable fields

$1: User name.

Example

Deleted a user: 11.

Explanation

A user was deleted.

Possible failure causes

·     Invalid username.

·     No permission to delete itself.

·     The controller is not the active leader.

·     Can't delete an online user.

·     Token aged.

 

Change user password

Keyword

CHANGE_PASSWORD_OP

Message text

Changed user $1's password.

Variable fields

$1: Username.

Example

Changed user 11's password.

Explanation

A user's password was changed.

Possible failure causes

·     Invalid username.

·     Invalid old password.

·     The password length is out of range or the password contains only letters, digits, or special characters.

·     Can't modify another user's password due to permission limit.

·     The controller is not the active leader.

·     Token aged.

·     The user doesn’t exist.

·     Failed to update the user’s password.

 

Update user config

Keyword

UPDATE_USER_OP

Message text

Updated user configuration: $1

Variable fields

$1: User configuration information.

Example

Updated user configuration:

Username: sdn

Password: ******

Role: sdn-admin

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

Lock state: unlock

Explanation

The user configuration was changed.

Possible failure causes

·     The user does not exist.

·     Invalid parameter for locking the user.

·     Invalid user role.

·     Invalid old password.

·     Invalid username.

·     Incorrect format.

·     The controller is not the active leader.

·     Can't modify another user's configuration due to permission limit.

·     Can't lock the current user.

·     Can't modify the role of the current user.

·     Can't change the types of service logs to display due to permission limit.

·     The password length is out of range or the password contains only letters, digits, or special characters.

·     Token aged.

·     Failed to update the user.

·     Can't modify the configuration of other online users.

 

Add a role

Keyword

ADD_ROLE_OP

Message text

Added a role: $1.

Variable fields

$1: Role name.

Example

Added a role: role1.

Explanation

A role was added.

Possible failure causes

·     Invalid role name.

·     Invalid role rule.

·     Invalid description.

·     The role already exists.

·     You have no privilege to perform the operation.

·     The controller is not the active leader.

·     Incorrect format.

·     Failed to add the role.

 

Update a role

Keyword

UPDATE_ROLE_OP

Message text

Updated role configuration: $1

Variable fields

$1: Role configuration.

Example

Updated role configuration:

Rolename: test2,

Description:,

RoleRules: {

  "rolerules": {

    "/lb/v2.0": {

      "details": [

        {

          "access": "POST",

          "controlled": "/loadbalancers"

        }

      ],

      "module": "LBaaS v2.0",

      "type": "REST"

    },

    "c-NetworkService": {

      "details": [

        {

          "access": "R",

          "controlled": "n-LoadBalance"

        }

      ],

      "type": "UI"

    }

  }

}

Explanation

A role was modified.

Possible failure causes

·     You have no privilege to perform the operation.

·     Incorrect format.

·     The controller is not the active leader.

·     Invalid role name.

·     Invalid role rule

·     Invalid description.

·     Can't modify default roles.

·     The role doesn’t exist.

·     Failed to update the role.

 

Delete a role

Keyword

DELETE_ROLE_OP

Message text

Deleted a role: $1.

Variable fields

$1: Role name.

Example

Deleted a role: 11.

Explanation

A role was deleted.

Possible failure causes

·     Invalid role name.

·     The controller is not the active leader.

·     Can't delete system default roles.

·     Can’t delete the role because it is already assigned to users.

 

 

 


DHCP

This section contains DHCP messages.

Create DHCP server

Keyword

CREATE_DHCP_SERVER_OP

Message text

Created DHCP server $1/$2.

Variable fields

$1: Name of the DHCP server.

$2: IP address of the DHCP server.

Example

Created DHCP server Vsr-26.72/98.0.26.72.

Explanation

A DHCP server was created.

Possible failure causes

·     Configuration recovery is in progress.

·     The controller is not the active leader.

·     Unknown error.

·     The IP address of the DHCP server is required.

·     Invalid IP address.

·     Invalid role.

·     The DHCP server name is required.

·     The DHCP server name cannot exceed 255 characters.

·     The NETCONF username of the DHCP server is required.

·     The NETCONF username of the DHCP server cannot exceed 55 characters.

·     The NETCONF password of the DHCP server is required.

·     The NETCONF password of the DHCP server cannot exceed 63 characters.

·     The DHCP server with the specified UUID already exists.

·     The DHCP server name is already used.

·     The DHCP server IP is already used.

·     Invalid DHCP server type.

·     The status field of the DHCP server is read-only.

·     The DHCP server does not support the master-backup mode.

·     The second IP is required in master-backup mode.

·     The DHCP servers in master-backup mode cannot use the same IP address.

·     The second IP address is invalid.

·     The DHCP server name cannot end with _peer.

·     Invalid unicast addresses.

·     The DHCP server name supports only Chinese characters, letters, digits, hyphens (-), and underscores (_).

·     Only one IP address is allowed in standalone mode.

·     Invalid DHCP server IP address.

 

Update DHCP server

Keyword

UPDATE_DHCP_SERVER_OP

Message text

Updated DHCP server $1/$2.

Variable fields

$1: Name of the DHCP server.

$2: IP address of the DHCP server.

Example

Updated DHCP server Vsr-26.72/98.0.26.72.

Explanation

A DHCP server was modified.

Possible failure causes

·     Configuration recovery is in progress.

·     The controller is not the active leader.

·     The request is invalid.

·     Unknown error.

·     The specified resource doesn't exist.

·     The IP field of the DHCP server is read-only.

·     The name field of the DHCP server is read-only.

·     The status field of the DHCP server is read-only.

·     The type field of the DHCP server is read-only.

·     The NETCONF username of the DHCP server is required.

·     The NETCONF username of the DHCP server cannot exceed 55 characters.

·     The NETCONF password of the DHCP server is required.

·     The NETCONF password of the DHCP server cannot exceed 63 characters.

·     The DHCP server name supports only Chinese characters, letters, digits, hyphens (-), and underscores (_).

 

Delete DHCP server

Keyword

DELETE_DHCP_SERVER_OP

Message text

Deleted DHCP server $1/$2.

Variable fields

$1: Name of the DHCP server.

$2: IP address of the DHCP server.

Example

Deleted DHCP server Vsr-26.72/98.0.26.72.

Explanation

A DHCP server was deleted.

Possible failure causes

·     Configuration recovery is in progress.

·     The controller is not the active leader.

·     Unknown error.

·     The specified resource doesn't exist.

·     Can't delete the DHCP server. The DHCP server has address pools.

 

Synchronize data from DHCP server

Keyword

SYNCHRONIZE_DATA_FROM_DHCP_SERVER_OP

Message text

Synchronized data from DHCP server $1.

Variable fields

$1: UUID of the DHCP server.

Example

Synchronized data from DHCP server 218b5f2f-e435-4365-a1ab-0eaa03b7fa19.

Explanation

Data from a DHCP server was synchronized.

Possible failure causes

·     Configuration recovery is in progress.

·     The controller is not the active leader.

·     Unknown error.

·     The DHCP server ID doesn't exist.

·     The server is synchronizing DHCP subnet information.

 


DHCP address pool

This section contains DHCP address pool messages.

Create DHCP address pool

Keyword

CREATE_DHCP_ADDRESS_POOL_OP

Message text

Created DHCP address pool: $1

Variable fields

$1: DHCP address pool information.

Example

Created DHCP address pool:

{

"dhcp_server_id": "79e1cf00-602a-4650-9706-a7ab904e3431",

"name": "ddi_pool_test",

"description": "ddi_pool_test",

"subnet": "98.0.2.0/24",

"options":[{"key":"3","value":"98.0.2.254"}],

"policy":[{"condition":"relay","value":"3030303034303934","wildcard":"append"},{"c

ondition":"client","value":"34","wildcard":"prefix"}]

}

Explanation

A DHCP address pool was created.

Possible failure causes

·     Configuration recovery is in progress

·     The controller is not the active leader.

·     The DHCP address pool name is required.

·     The DHCP pool name cannot exceed 255 characters.

·     The DHCP address pool description cannot exceed 255 characters.

·     The DHCP server ID is required.

·     The DHCP address pool option is required.

·     The subnet is required in the DHCP address pool.

·     The subnet in the DHCP address pool is invalid.

·     The DHCP address pool policy is invalid.

·     The DHCP server doesn't exist.

·     The DHCP address pool name has been used.

·     Overlapping subnet in the DHCP address pool.

·     Unknown error.

·     The DHCP server does not support custom address pools.

·     Invalid DHCP address pool option.

·     The DHCP pool name is invalid.

 

Delete DHCP address pool

Keyword

DELETE_DHCP_ADDRESS_POOL_OP

Message text

Deleted DHCP address pool $1 on DHCP server $2

Variable fields

$1: ID of the DHCP address pool.

$2: ID of the DHCP server.

Example

Deleted DHCP address pool 14ed05b2-2a52-4f04-aa4e-6f215e622a39 on DHCP server 25ed05b2-6a52-9a04-aa4e-9a215e622a46.

Explanation

A DHCP address pool was deleted.

Possible failure causes

·     The specified resource doesn't exist.

·     Only custom DHCP address pools can be deleted.

·     Configuration recovery is in progress.

·     The controller is not the active leader.

·     The DHCP server doesn't exist.

·     The DHCP address pool doesn't exist.

·     Unknown error.

 


General Group

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

Create general group

Keyword

CREATE_GENERAL_GROUP_OP

Message text

Created general group: $1.

Variable fields

$1: Information about the created general group.

Example

Created general group:

ID:[cee6d907-7dd7-4d18-9e83-e55bdeb031f8]

Name:[default_leaf_group]

Description:[515]

Type:[DEVICE_GROUP]

Explanation

A general group was created.

Possible failure causes

·     Invalid JSON format.

·     The general group name already exists.

·     Unknown internal server error.

·     The specified fabric doesn’t exist.

 

Update general group

Keyword

UPDATE_GENERAL_GROUP_OP

Message text

Updated general group: $1

Variable fields

$1: General group information.

Example

Updated general group:

ID:[cee6d907-7dd7-4d18-9e83-e55bdeb031f8]

Name:[default_leaf_group]

Description:[test]

Type:[DEVICE_GROUP]

Explanation

A general group was updated.

Possible failure causes

·     Invalid JSON format.

·     The general group with the specified ID does not exist.

·     Unknown internal server error.

 

Delete general group

Keyword

DELETE_GENERAL_GROUP_OP

Message text

Deleted general group: $1

Variable fields

$1: General group information.

Example

Deleted general group:

ID:[cee6d907-7dd7-4d18-9e83-e55bdeb031f8]

Name:[default_leaf_group]

Description:[test]

Type:[DEVICE_GROUP]

Explanation

A general group was deleted.

Possible failure causes

·     Invalid JSON format.

·     The general group with the specified ID does not exist.

 

Add device to device group

Keyword

ADD_DEVICE_GENERALGROUP_OP

Message text

Added $1 devices to device group: $2.

Variable fields

$1: Number of devices added.

$2: Device group information.

Example

Added 10 devices to device group:

ID:[cee6d907-7dd7-4d18-9e83-e55bdeb031f8]

Name:[default_leaf_group]

Description:[515]

Type:[DEVICE_GROUP]

Explanation

Devices were added to a device group.

Possible failure causes

·     Invalid JSON format.

·     The device group with the specified ID does not exist.

·     The NE doesn't exist.

·     The network element is being deleted or being removed from the gateway group or being removed from the fabric.

·     The device has already belonged to the device group.

·     Unknown internal server error.

 

Delete device from device group

Keyword

DELETE_DEVICE_GENERALGROUP_OP

Message text

Deleted $1 devices from device group: $2.

Variable fields

$1: Number of devices deleted.

$2: Device group information.

Example

Deleted 10 devices from device group:

ID:[cee6d907-7dd7-4d18-9e83-e55bdeb031f8]

Name:[default_leaf_group]

Description:[515]

Type:[DEVICE_GROUP]

Explanation

Devices were deleted from a device group.

Possible failure causes

·     Invalid JSON format.

·     The device group with the specified ID does not   exist.

·     The NE doesn't exist.

·     The network element is being deleted or being removed from the gateway group or being removed from the fabric.

·     The device doesn't belong to this device group.

·     Unknown internal server error.

 

Add interface to interface group

Keyword

ADD_INTERFACE_GENERAL_GROUP_OP

Message text

Added $1 interfaces to interface group: $2.

Variable fields

$1: Number of interfaces added.

$2: Interface group information.

Example

Added 10 interfaces to interface group:

ID:[cee6d907-7dd7-4d18-9e83-e55bdeb031f8]

Name:[default_leaf_group]

Description:[515]

Type:[INTERFACE_GROUP]

Explanation

Interfaces were added to an interface group.

Possible failure causes

·     Invalid JSON format.

·     The interface group  with the specified ID does not exist.

·     The  NE doesn't exist.

·     The network element is being deleted or being removed from the gateway group or being removed from the fabric.

·     The interface has  been the member of this interface group.

·     Unknown internal server error.

 

Delete interface from interface group

Keyword

DELETE_INTERFACE_GENERAL_GROUP_OP

Message text

Deleted $1 interfaces from interface group: $2.

Variable fields

$1: Number of interfaces deleted.

$2: Interface group information.

Example

Deleted 10 interfaces from interface group:

ID:[cee6d907-7dd7-4d18-9e83-e55bdeb031f8]

Name:[default_leaf_group]

Description:[515]

Type:[INTERFACE_GROUP]

Explanation

Interfaces were deleted from an interface group.

Possible failure causes

·     Invalid JSON format.

·     The interface group with the specified ID does not  exist.

·     The NE doesn't exist.

·     The network element is being deleted or being removed from the gateway group or being removed from the fabric.

·     The interface does not exist in  this interface group.

·     Unknown internal server error.

 

Bind policy

Keyword

BIND_POLICY_OP

Message text

Bound $1 policies to general group: $2.

Variable fields

$1: Number of policies bound.

$2: Information about the bound general group.

Example

Bound 10 policies to general group:

ID:[cee6d907-7dd7-4d18-9e83-e55bdeb031f8]

Name:[default_leaf_group]

Description:[515]

Type:[INTERFACE_GROUP]

Explanation

Policies were bound to a general group.

Possible failure causes

·     Invalid JSON format.

·     The general group with the specified ID does not  exist.

·     The specified policy does not exist.

·     Failed to bind to the general group: The same category field exists in the template.

·     The bound template type does not match.

·     The group policy has already been bound to a  general group.

·     Cannot bind this policy to this general group.

·     Unknown internal server error.

 

Unbind policy

Keyword

UNBIND_POLICY_OP

Message text

Unbound $1 policies from general group: $2.

Variable fields

$1: Number of policies unbound.

$2: Information about the unbound general group.

Example

Unbound 10 policies from general group:

ID:[cee6d907-7dd7-4d18-9e83-e55bdeb031f8]

Name:[default_leaf_group]

Description:[testdev]

Type:[INTERFACE_GROUP]

Explanation

Policies were unbound from a general group.

Possible failure causes

·     Invalid JSON format.

·     The general group with the specified ID does not exist.

·     The policy is not bound to this general group.

·     Unknown internal server error.

 


IDM

This section contains IDM messages.

Add NETCONF template

Keyword

ADD_NETCONF_TEMPLATE_OP

Message text

Added a NETCONF template:

id: $1

templateName: $2

vender: $3

description:$4

createType: $5

netConfProtocolList: [

{

id: $6

type: $7,

netConfInfo: $8

tempId: $9

}

].

Variable fields

$1: NETCONF template ID.

$2: NETCONF template name.

$3: Vendor name.

$4: Template description.

$5: Creation mode. Options include 0, 1, and 2. 0 indicates that the template is created on the configuration page. 1 represents normal creation used for automation templates. 2 represents templates created for devices.

$6: NETCONF protocol ID.

$7: NETCONF template type. Options include 0 and 1. 0 represents HTTP and 1 represents HTTPS. Only HTTPS is supported in the current software version.

$8: NETCONF information.

$9: Template ID.

Example

Added a NETCONF template:

id: [1]

templateName: [TEST_NETCONF]

vender: [1]

description: []

createType: [0]

netConfProtocolList: [

{

id: [1]

type: [1] netConfInfo:[ type=1%%accessType=SOAP/HTTPS%%protocol=HTTPS%%

port=832%%rootPath=/soap/netconf/%%userName=adg%%

password=cbjaLmV3o4lxV+CzQPCumA==%%]

tempId: [1]

}

]

Explanation

A NETCONF template was added.

Possible failure causes

·     The NETCONF template parameters cannot be empty.

·     The controller is not the active leader.

·     Configuration recovery is in progress.

·     The NETCONF template name is required.

·     The NETCONF template name already exists.

·     The value of the protocol type field can only be 1.

·     The protocol type is required.

·     The NETCONF template protocol type must be the same as that in the NETCONF information.

·     The NETCONF information must contain a username and a password.

·     The NETCONF information is required.

·     The value of the NETCONFtemplate ID is an integer in the range of 1 to 2147483647.

·     The value of the protocol ID is an integer in the range of 1 to 2147483647.

·     A maximum of one protocol is supported in the NETCONF protocol list.

·     The value of the creation type field can only be 0, 1, or 2.

·     The vender is required.

·     The value of the vender is an integer in the range of 1 to 2147483647.

·     The netConfProtocolList cannot be null.

·     Failed to synchronize information from the primary controller to the backup controller.

·     The netConfInfo field can contain up to 255 characters.

·     The description field can contain up to 255 characters.

·     The NETCONF template name field can contain up to 255 characters.

·     Unknown system error.

·     Invalid JSON format.

 

Update NETCONF template

Keyword

UPDATE_NETCONF_TEMPLATE_OP

Message text

Updated NETCONF template $1:

id: $2

templateName: $3

vender: $4

description:$5

createType: $6

netConfProtocolList: [

{

id: $7 ,

type: $8,

netConfInfo: $9,

tempId: $10

}

]

Variable fields

$1: NETCONF template ID.

$2: NETCONF template ID.

$3: NETCONF template name.

$4: Vendor name.

$5: NETCONF template description.

$6: Creation mode. Options include 0, 1, and 2. 0 indicates that the template is created on the configuration page. 1 represents normal creation used for automation templates. 2 represents templates created for devices.

$7: NETCONF protocol ID.

$8: NETCONF template type. Options include 0 and 1. 0 represents HTTP and 1 represents HTTPS. Only HTTPS is supported in the current software version.

$9: NETCONF protocol information.

$10: Template ID.

Example

Updated NETCONF template 1:

id: [1],

templateName: [TEST_NETCONF],

vender: [1]

description: []

createType: [0]

netConfProtocolList: [

{

id: [1]

type: [1] netConfInfo:[ type=1%%accessType=SOAP/HTTPS%%protocol=HTTPS%%

port=832%%rootPath=/soap/netconf/%%userName=adg%%

password=cbjaLmV3o4lxV+CzQPCumA==%%]

tempId: [1]

}

]

Explanation

A NETCONF template was modified.

Possible failure causes

·     The NETCONF template parameters cannot be empty.

·     The controller was not the active leader.

·     Configuration recovery is in progress.

·     The value of the protocol type field can only be 1.

·     The protocol type is required.

·     The NETCONF template protocol type must be the same as that in the NETCONF information.

·     The NETCONF information must contain a username and a password.

·     The NETCONF information is required.

·     The value of the NETCONF template ID is an integer in the range of 1 to 2147483647.

·     The value of the protocol ID is an integer in the range of 1 to 2147483647.

·     A maximum of one protocol is supported in the NETCONF protocol list.

·     The value of the creation type field can only be 0, 1, or 2.

·     The vender is required.

·     The value of the vender is an integer in the range of 1 to 2147483647.

·     Failed to synchronize information from the primary controller to the backup controller.

·     Unknown system error.

·     The NETCONF template ID must be the same as that in the NETCONF information.

·     The protocol ID does not exist.

·     The netConfProtocolList cannot be null.

·     The protocol ID cannot be null.

·     Invalid JSON format.

·     The netConfInfo field can contain up to 255 characters.

·     The description field can contain up to 255 characters.

·     The NETCONF template name field can contain up to 255 characters.

·     The NETCONF template ID is required in NETCONF protocol list.

·     The NETCONF template ID does not exist.

 

Delete NETCONF template

Keyword

DELETE_NETCONF_TEMPLATE_OP

Message text

Deleted NETCONF template: $1.

Variable fields

$1: NETCONF template ID.

Example

Deleted NETCONF template: 1.

Explanation

A NETCONF template was deleted.

Possible failure causes

·     The controller was not the active leader.

·     Configuration recovery is in progress.

·     Failed to synchronize information from the primary controller to the backup controller.

·     Unknown system error.

·     The value of the NETCONF template ID is an integer in the range of 1 to 2147483647.

·     The NETCONF template ID does not exist.

 

Add configuration file

Keyword

ADD_CONF_FILE_OP

Message text

Added a configuration file:

  confFileName:$1

  confFileType:$2

  cfgFileParent:$3

  appliedDevices:$4

  content:$5

Variable fields

$1: Configuration file name.

$2: Configuration file type. Options include -1, 1, and 2. -1 represents folder, 1 represents configuration file, and 2 represents configuration snippet.

$3: ID of the folder to which the file belongs.

$4: IDs of the devices to which the configuration file is applicable.

$5: Configuration file contents.

Example

Added a configuration file:

  confFileName:[test_json_4.cfg]

  confFileType:[-1]

  cfgFileParent:[-1]

  appliedDevices:[1]

  content:[system

test

]

Explanation

A configuration file was added.

Possible failure causes

·     The request is invalid.

·     The controller is not the active leader.

·     Failed to add the configuration file. The values of the configuration file type and folder ID fields can contain only digits.

·     The configuration file does not folder.

·     Failed to synchronize information from the primary controller to the backup controller.

·     Configuration recovery is in progress.

·     The configuration file name is required.

·     The configuration file type is required.

·     The value of the configuration file type can only be –1, 1 or 2.

·     The confFileName field can contain up to 255 characters.

·     The confFilePath field can contain up to 255 characters.

·     The appliedDevices field can contain up to 255 characters.

·     The configuration file contents are required.

·     The configuration file folder is required.

·     The configuration file folder does not exist.

·     The configuration file name already exists.

·     Unknown system error.

 

Delete configuration file

Keyword

DELETE_CONF_FILE_OP

Message text

Deleted configuration file $1.

Variable fields

$1: Configuration file ID.

Example

Deleted configuration file 1.

Explanation

A configuration file was deleted.

Possible failure causes

·     Failed to synchronize information from the primary controller to the backup controller.

·     The configuration file ID is invalid.

·     The controller is not the active leader.

·     Configuration recovery is in progress.

·     The configuration file does not exist.

·     Unknown system error.

 

Deploy configuration snippets

Keyword

DEPLOY_CONF_SNIPPET_OP

Message text

Deployed configuration snippets to the device:$1

Variable fields

$1: Configuration snippet contents.

Example

Deployed configuration snippets to the device:

confFileId:[3]

deviceIds:[1]

replaceParams:[[ReplaceParamRs [key=, value=]]]

confFilePath:[/]

confFileName:[test_json_4.cfg]

Explanation

Configuration snippets were deployed to a device.

Possible failure causes

·     The controller is not the active leader.

·     Configuration recovery is in progress.

·     The configuration file ID is invalid.

·     The configuration file folder does not exist.

·     The file must be a configuration snippet file.

·     When the confFileId is empty, the confFilePath and confFileName fields are required.

·     The configuration snippet does not exist.

·     Deployment failed.

·     Partially succeeded.

·     Invalid device ID.

·     The device ID does not exist.

·     The request is invalid.

·     The configuration file name is required.

·     The parameters are empty.

·     Unknown system error.

 

Deploy commands

Keyword

DEPLOY_COMMAND_OP

Message text

Deployed commands to the device:$1

Variable fields

$1: Device ID and deployed commands.

Example

Deployed commands to the device:

deviceId:[2]

cmdlist:[[CmdList [cmd=[system, test]]]]

Explanation

Commands were deployed to a device and executed.

Possible failure causes

·     The controller is not the active leader.

·     Configuration recovery is in progress.

·     The request is invalid.

·     The parameters are empty.

·     Invalid device ID.

·     The device ID does not exist.

·     The configuration list that the controller deployed to the device is empty.

·     Unknown system error.

 

Start automatic configuration process

Keyword

START_DEVICE_AUTO_CFG_OP

Message text

Started the automatic configuration process for device $1.

Variable fields

$1: Device ID.

Example

Started the automatic configuration process for device 1011.

Explanation

Started the automatic configuration process for a device.

Possible failure causes

·     Invalid JSON format.

·     Service not started.

·     Configuration recovery is in progress.

·     The controller is not the active leader.

·     Invalid device ID.

·     The asset information does not exist.

·     The device IP corresponding to the device ID does not exist.

·     The configuration list that the controller deployed to the device is empty.

·     The IP address of the master node is invalid.

·     Internal error.

 

Stop automatic configuration process

Keyword

STOP_DEVICE_AUTO_CFG_OP

Message text

Stopped the automatic configuration process for device $1.

Variable fields

$1: Device ID.

Example

Stopped the automatic configuration process for device 1011.

Explanation

Stopped the automatic configuration process for a device.

Possible failure causes

·     Invalid JSON format.

·     Service not started.

·     Configuration recovery is in progress.

·     The controller is not the active leader.

·     Invalid device ID.

·     The asset information does not exist.

·     The device IP corresponding to the device ID does not exist.

·     The configuration list that the controller deployed to the device is empty.

·     The IP address of the master node is invalid.

·     Internal error.

 

Add SNMP template

Keyword

ADD_SNMP_TEMPLATE_OP

Message text

Added an SNMP template:$1

Variable fields

$1: SNMP template information.

Example

Added an SNMP template:

id: [34]

  name: [test1]

  version: [2]

  type: [1]

  paraType: [SNMPv2c]

  retries: [3]

  timeout: [5]

  roCommunity: [public]

  rwCommunity: [private]

  snmpPort: [161]

  accessType: [1]

  isAutodiscoverTemp: [1]

  creator: [creator]

  operatorGroupStr: []

Explanation

An SNMP template was created.

Possible failure causes

·     Invalid json format.

·     The controller is not the active leader.

·     Configuration recovery is in progress.

·     The SNMP template name already exists.

·     The SNMP template ID is invalid.

·     The SNMP template name cannot exceed 64 characters.

·     The value of the version field can only be 2.

·     The value of the timeout is an integer in the range of 1 to 60 (seconds).

·     The value of the retries is an integer in the range of 1 to 20.

·     The timeout is required.

·     The retries is required.

·     The value of the isAutodiscoverTemp field can only be 1 or 2.

·     The value of the accessType field can only be 1 or 2.

·     The value of the type field can only be 0 or 1.

·     Failed to synchronize information from the primary controller to the backup controller.

·     Unknown error.

·     The snmpPort value is an integer in the range of 1 to 65535.

·     The roCommunity field can contain up to 96 characters.

·     The rwCommunity field can contain up to 96 characters.

·     The creator field can contain up to 255 characters.

·     The operatorGroupStr field can contain up to 255 characters.

 

Delete SNMP template

Keyword

DELETE_SNMP_TEMPLATE_OP

Message text

Deleted SNMP template: $1.

Variable fields

$1: SNMP template ID.

Example

Deleted SNMP template: 2.

Explanation

An SNMP template was deleted.

Possible failure causes

·     The controller is not the active leader.

·     Configuration recovery is in progress.

·     The SNMP template ID is invalid.

·     The SNMP template ID does not exist.

·     The default template cannot be deleted.

·     Failed to synchronize information from the primary controller to the backup controller.

 

Update SNMP template

Keyword

UPDATE_SNMP_TEMPLATE_OP

Message text

Updated SNMP template $1:$2

Variable fields

$1: SNMP template ID.

$2: SNMP template information.

Example

Updated SNMP template 2:

  id:[34]

name: [test]

  version: [2]

  type: [1]

  paraType: [SNMPv2c]

  retries: [3]

  timeout: [5]

  roCommunity: [public]

  rwCommunity: [private]