H3C Super Controller Operation Log Messages Reference-5W100

HomeSupportResource CenterSDNSuper ControllerSuper ControllerTechnical DocumentsReference GuidesLog Message ReferencesH3C Super Controller Operation Log Messages Reference-5W100
Download Book

Introduction

Operation logs record system operations and configuration modifications, such as application operations (installing, starting, stopping, or uninstalling an application) and team 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 super controller products.

Viewing operation log messages

Select System > Log > Operation Log to enter operation log view. The generated operation log messages are displayed on pages 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.

User

Name of the user that triggered the log generation.

IP

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

Micro service

Name of the microservice that produced the log message.

Service

Name of the service module that produced the log message.

Operation

Text string that contains detailed information about the operation.

Result

Operation result: Success or Failure.

Failure reason

Possible reasons for an operation failure.

 

Syslog message format

The super controller can send operation logs to syslog servers through the syslog protocol. To set the IP address and port number of a syslog server, select System > Settings > Log Settings on the top navigation bar, and then select Operation Log.

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

<PRI>TIMESTAMP Hostname Service/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 of the container that produced the message.

Service

Name of the microservice that produced the message.

severity

Severity level of the message. For more information, see Table 5. Two syslog message severity levels, are used.

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

AUTH

Authentication management module

LICENSE

License management module

LOG_ALERT

System log module

LOG_AUDIT

Operation log module

LOG_DIAG

Diagnosis log module

NSO_AUDIT

NSO microservice module

SYSTEM

System management module

USER

User management module

WEB

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

 

The super controller uses two syslog message severity levels, as shown in Table 5.

Table 5 Operation log message severity levels

Level

Severity

Description

6

Informational

Information message. It indicates that the operation succeeded.

4

Warning

Warning condition. It indicates that the operation failed.

 

Using this document

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

Table 6 Message explanation table contents

Item

Content

Example

Keyword

Summary of the message that facilitates searching or memorizing.

ADD_AUTH_FREEIP_OP

Message text

Presents the message description.

Added an authentication-free IP: $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: Authentication-free user.

Example

Provides a real message example.

Added an authentication-free IP: 192.168.56.13.

Explanation

Explains the message.

An authentication-free user was added.

Possible failure causes

Provides possible causes of an operation failure.

·     Invalid IP address.

·     The IP address already exists.

·     Unable to read/write database.

·     Invalid role.

·     Invalid domain.

·     Invalid description.


AUTH

This section contains authentication management messages.

Added an authentication-free IP

Keyword

ADD_AUTH_FREEIP_OP

Message text

Added an authentication-free IP: $1.

Variable fields

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

Example

Added an authentication-free IP: 192.168.56.13.

Explanation

An authentication-free user was added.

Possible failure causes

·     Invalid JSON format.

·     Invalid IP address.

·     The IP address already exists.

·     Invalid role.

·     Invalid description.

·     The system is recovering.

·     Internal error.

 

Deleted an authentication-free IP

Keyword

DELETE_AUTH_FREEIP_OP

Message text

Deleted an authentication-free IP: $1.

Variable fields

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

Example

Deleted an authentication-free IP: 192.168.56.13.

Explanation

An authentication-free user was deleted.

Possible failure causes

·     Invalid IP address.

·     The system is recovering.

·     Internal error.

 

Added an IP address to whitelist

Keyword

ADD_WHITELIST_OP

Message text

Added IP address $1 to the whitelist.

Variable fields

$1: IP address added to the whitelist.

Example

Added IP address 192.168.56.13 to the whitelist.

Explanation

A user was added to the whitelist.

Possible failure causes

·     Invalid JSON format.

·     Invalid IP address.

·     The whitelist already exists.

·     Invalid description.

·     The system is recovering.

·     Internal error.

 

Deleted an IP address from whitelist

Keyword

DELETE_WHITELIST_OP

Message text

Deleted IP address $1 from the whitelist.

Variable fields

$1: IP address deleted from the whitelist.

Example

Deleted IP address 192.168.56.13 from the whitelist.

Explanation

A user was removed from the whitelist.

Possible failure causes

·     Invalid IP address.

·     The system is recovering.

·     Internal error.

 

Updated authentication configuration

Keyword

UPDATE_AUTH_CONFIG_OP

Message text

Updated authentication configuration: $1.

Variable fields

$1: Current authentication settings.

Example

Updated authentication configuration:

Auth mode = local

Auth protocol = null

User idle timeout = 900

Auth server IP = 1.1.1.74

Shared key = 123

Explanation

A user modified the authentication settings.

Possible failure causes

·     Invalid JSON format.

·     Invalid authentication mode.

·     Invalid authentication protocol.

·     Invalid remote authentication server IP address.

·     Invalid shared key.

·     Invalid user idle timeout time.

·     The system is recovering.

·     Internal error.

 


LICENSE

This section contains license management messages.

Connect to the license server

Keyword

CONNECT_LICS_OP

Message text

Connected to the license server: $1

Variable fields

$1: License server information.

Example

Connected to the license server:{

"ip”: “192.168.40.40”,

"password”: “******”,

"port”: “5555”,

"username”: “sdn”

}

Explanation

The controller initiated a connection to the specified license server.

Possible failure causes

·     Invalid JSON format.

·     Invalid server IP.

·     Invalid port.

·     The connection is already exist.

·     The system is recovering.

·     Internal error.

·     Failed to connect to the license server.

·     Incorrect username or password.

 

Disconnect from the license server

Keyword

DISCONNECT_LICS_OP

Message text

Disconnected from the license server: $1.

Variable fields

$1: License server IP address.

Example

Disconnected from the license server: 192.168.1.1.

Explanation

The controller disconnected from the specified license server.

Possible failure causes

·     The system is recovering.

·     Internal error.

 

Update the quantity of requested licenses

Keyword

UPDATE_REQUESTED_LICENSES_OP

Message text

Updated the quantity of requested licenses: $1

Variable fields

$1: Types and numbers of licenses updated.

Example

Updated the quantity of requested licenses: [

{

 “featureName”:”SiteNodeNum”,

  “needCount”:”6”

}

]

Explanation

A user changed the quantity of requested licenses.

Possible failure causes

·     Invalid JSON format.

·     The atom does not existe.

·     The system is recovering.

·     The count is out of range.

·     Internal error.

 

Apply license

Keyword

APPLY_LICENSES_OP

Message text

Applied for license: $1.

Variable fields

$1: Types and numbers of licenses applied for.

Example

Apply License:

SiteNodeNum license: 1.

Explanation

A user applied for licenses.

Possible failure causes

·     Invalid JSON format.

·     The atom does not exist.

·     The license type mismatches.

·     The system is recovering.

·     The count is out of range.

 

Release license

Keyword

RELEASE_LICENSES_OP

Message text

Released licenses: $1.

Variable fields

$1: Types and numbers of licenses released.

Example

Release licenses:

SiteNodeNum license: 1.

Explanation

A user released licenses.

Possible failure causes

·     The team is not ready.

·     Invalid JSON format.

·     The atom does not existed.

·     The license type mismatches.

·     The system is recovering.

·     The count is out of range.

 

Synchorize licenses

Keyword

SYNC_LICENSES_OP

Message text

Sync licenses:$1.

Variable fields

$1: Types and numbers of licenses synchronized.

Example

Sync licenses:

SiteNodeNum license: 1

Explanation

A user synchronized licenses.

Possible failure causes

·     Invalid JSON format.

·     The atom does not existed.

·     The license type mismatches.

·     The system is recovering.

·     The count is out of range.

 

 


LOG_ALERT

This section contains operation log messages of the system log module.

Delete a system log

Keyword

DELETE_LOG_ALERT_OP

Message text

Deleted a system log.

Variable fields

N/A

Example

Deleted a system log.

Explanation

This message is sent when a user deletes a system log.

Possible failure causes

Internal error.

 

Update system log configuration

Keyword

UPDATE_LOG_ALERT_CONFIG_OP

Message text

Updated system log configuration: $1.

Variable fields

$1: System log configuration.

Example

Updated system log configuration:

{

"h3c-supercontroller-log-alert-config:configs":

{

"duration":82,

"purge.clock":"19:20",

"syslog.server1.ip":"0.0.0.0",

"syslog.server1.port":514,

"syslog.server2.ip":"0.0.0.0",

"syslog.server2.port":514,

"syslog.level":4

}

}.

Explanation

This message is sent when a user modifies the system log configuration.

Possible failure causes

·     Invalid parameter.

·     Invalid JSON format.

·     Invalid storage duration.

·     Invalid expired log purge time.

·     Invalid IP address of log server 1.

·     Invalid port number of log server 1.

·     Invalid IP address of log server 2.

·     Invalid port number of log server 2.

·     Invalid severity level.

·     Internal error.

 


LOG_AUDIT

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

Delete an operation log

Keyword

DELETE_LOG_AUDIT_OP

Message text

Deleted an operation log.

Variable fields

N/A

Example

Deleted an operation log.

Explanation

This message is sent when a user deletes an operation log.

Possible failure causes

Internal error.

 

Update operation log configuration

Keyword

UPDATE_LOG_AUDIT_CONFIG_OP

Message text

Updated the configuration of operation log: $1.

Variable fields

$1: Operation log configuration.

Example

Updated operation log configuration:

{

"h3c-supercontroller-log-audit-config:configs":

{

"duration":82,

"purge.clock":"19:20",

"syslog.server1.ip":"0.0.0.0",

"syslog.server1.port":514,

"syslog.server2.ip":"0.0.0.0",

"syslog.server2.port":514,

"syslog.level":4

}

}.

Explanation

This message is sent when a user modifies the operation log configuration.

Possible failure causes

·     Invalid parameter.

·     Invalid JSON format.

·     Invalid storage duration.

·     Invalid expired log purge time.

·     Invalid IP address of log server 1.

·     Invalid port number of log server 1.

·     Invalid IP address of log server 2.

·     Invalid port number of log server 2.

·     Invalid severity level.

·     Internal error.

 


LOG_DIAG

This section contains diagnosis messages.

Update diagnosis log configuration

Keyword

UPDATE_DIAGLOG_CONFIG_OP

Message text

Updated diagnosis log configuration: $1.

Variable fields

$1: Diagnosis log settings.

Example

Updated diagnosis log configuration:

{

"h3c-supercontroller-log-diag-config:configs":

{

"space":52,

"percent":92,

"level": 6

}

}.

Explanation

A user modified the diagnosis log settings.

Possible failure causes

·     Invalid parameter.

·     Invalid JSON format.

·     Invalid percentage of reserved messages at purge.

·     Invalid parameter diag disk space.

·     Invalid parameter diag level.

·     Internal error.

 

 


NSO_AUDIT

This section contains NSO microservice messages.

Add logic network

Keyword

ADD_NSO_LOGICNETWORK_OP

Message text

Added logic network “$1”.

Variable fields

$1: UUID of the logical network.

Example

Added logic network “edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027”.

Explanation

A logical network was added.

Possible failure causes

·     Invalid JSON format.

·     The UUID is required.

·     The logical network name is required.

·     The tenant UUID is required.

·     Invalid request.

·     The tenant bound to the logical network does not exist.

·     The specified site does not exist.

·     Duplicate sites exist.

·     Failed to add the resource.

·     Operation failed. The UUID already exists.

·     Different logical networks of a tenant cannot use the same name.

·     The specified site is not bound to any tenants.

·     A logical network must be bound with sites when the tenant to which the logical network belongs is bound with sites.

·     DriverManager microservice processing failed.

·     The timer for waiting for driver responses expired.

·     Site processing failed.

·     Cannot reach sites.

 

Update logic network

Keyword

UPDATE_NSO_LOGICNETWORK_OP

Message text

Updated logic network “$1”.

Variable fields

$1: UUID of the logical network.

Example

Updated logic network “edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027”.

Explanation

A logical network was modified.

Possible failure causes

·     Invalid JSON format.

·     The UUID is required.

·     The tenant UUID cannot be modified.

·     Invalid request.

·     The resource does not exist.

·     Different logical networks of a tenant cannot use the same name.

·     A logical network must be bound with sites when the tenant to which the logical network belongs is bound with sites.

·     The site has been bound to virtual subnets.

·     The specified site is not bound to any tenants.

·     The specified site does not exist.

·     DriverManager microservice processing failed.

·     The timer for waiting for driver responses expired.

·     Site processing failed.

·     Cannot reach sites.

·     Failed to modify the resource.

 

Delete logic network

Keyword

DEL_NSO_LOGICNETWORK_OP

Message text

Deleted logic network “$1”.

Variable fields

$1: UUID of the logical network.

Example

Deleted logic network “edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027”.

Explanation

A logical network was deleted.

Possible failure causes

·     Invalid request.

·     The logical network has vRouters.

·     The logical network has virtual link layer networks.

·     The logical network has virtual subnets.

·     DriverManager microservice processing failed.

·     The timer for waiting for driver responses expired.

·     Site processing failed.

·     Cannot reach sites.

·     The resource does not exist.

·     Failed to delete the resource.

 

Add network

Keyword

ADD_NSO_NETWORK_OP

Message text

Added network “$1”.

Variable fields

$1: UUID of the virtual link layer network.

Example

Added network “edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027”.

Explanation

A virtual link layer network was created.

Possible failure causes

·     Invalid JSON format.

·     The virtual link layer network name is required.

·     The specified logical network does not exist.

·     The number of virtual link layer networks has reached the limit specified in the resource pool.

·     Different virtual link layer networks in a logical network cannot use the same name.

·     VNI allocation failed.

·     Operation failed. The UUID already exists.

·     The number of virtual link layer networks has reached the limit specified in the resource pool.

·     Failed to add the resource.

·     No available VNIs.

·     The VNI has been used.

 

Update network

Keyword

UPDATE_NSO_NETWORK_OP

Message text

Updated network “$1”.

Variable fields

$1: UUID of the virtual link layer network.

Example

Updated network “edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027”.

Explanation

A virtual link layer network was modified.

Possible failure causes

·     Invalid JSON format.

·     The UUID is required.

·     The External network parameter of a virtual link layer network cannot be modified.

·     The network type of a virtual link layer network cannot be modified.

·     The segment ID of a virtual link layer network cannot be modified.

·     The UUID of a logical network cannot be modified.

·     Different virtual link layer networks in a logical network cannot use the same name.

·     DriverManager microservice processing failed.

·     The timer for waiting for driver responses expired.

·     Site processing failed.

·     Cannot reach sites.

·     The resource does not exist.

·     Failed to modify the resource.

 

Delete network

Keyword

DEL_NSO_NETWORK_OP

Message text

Deleted network “$1”.

Variable fields

$1: UUID of the virtual link layer network.

Example

Deleted network “edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027”.

Explanation

A virtual link layer network was deleted.

Possible failure causes

·     The resource does not exist.

·     The virtual link layer network has virtual subnets.

·     The virtual link layer network has vPorts.

·     Internal error.

·     DriverManager microservice processing failed.

·     The timer for waiting for driver responses expired.

·     Site processing failed.

·     Cannot reach sites.

·     Failed to delete the resource.

 

Add vPort

Keyword

ADD_NSO_PORT_OP

Message text

Added port “$1”.

Variable fields

$1: UUID of the vPort.

Example

Added port “edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027”.

Explanation

A vPort was added.

Possible failure causes

·     Invalid request.

·     The UUID is required.

·     The tenant UUID is required.

·     The virtual link layer network UUID is required.

·     Internal error.

·     Invalid JSON format.

·     The specified tenant does not exist.

·     The specified virtual link layer network does not exist.

·     The specified virtual link layer network and vPort do not belong to same tenant.

·     The specified virtual subnet does not exist.

·     The specified virtual subnet and vPort do not belong to same tenant.

·     Invalid IP address.

·     Operation failed. The UUID already exists.

·     The vPort name has been used.

·     DriverManager microservice processing failed.

·     The timer for waiting for driver responses expired.

·     Site processing failed.

·     Cannot reach sites.

·     Failed to add the resource.

 

Update vPort

Keyword

UPDATE_NSO_PORT_OP

Message text

Updated port “$1”.

Variable fields

$1: UUID of the vPort.

Example

Updated port “edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027”.

Explanation

A vPort was modified.

Possible failure causes

·     Invalid JSON format.

·     The UUID is required.

·     The tenant cannot be modified.

·     The virtual link layer network cannot be modified.

·     Different virtual subnets in a logical network cannot use the same name.

·     The specified virtual subnet and vPort do not belong to same tenant.

·     The specified virtual subnet does not exist.

·     The resource does not exist.

·     Internal error.

·     DriverManager microservice processing failed.

·     The timer for waiting for driver responses expired.

·     Site processing failed.

·     Cannot reach sites.

·     The vPort name has been used.

·     Invalid IP address.

·     Failed to modify the resource.

 

Delete vPort

Keyword

DEL_NSO_PORT_OP

Message text

Deleted port “$1”.

Variable fields

$1: UUID of the vPort.

Example

Deleted port “edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027”.

Explanation

A vPort was deleted.

Possible failure causes

·     Invalid request.

·     The resource does not exist.

·     Internal error.

·     DriverManager microservice processing failed.

·     The timer for waiting for driver responses expired.

·     Site processing failed.

·     Cannot reach sites.

·     Failed to delete the resource.

 

Add router

Keyword

ADD_NSO_ROUTER_OP

Message text

Added router “$1”.

Variable fields

$1: UUID of the vRouter.

Example

Added router “edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027”.

Explanation

A vRouter was created.

Possible failure causes

·     Invalid JSON format.

·     The vRouter name is required.

·     A minimum of one CIDR is required.

·     The UUID is required.

·     The specified logical network does not exist.

·     The number of vRouters has reached the limit specified in the resource pool.

·     Different vRouters in a logical network cannot use the same name.

·     Different CIDRs cannot overlap.

·     Failed to send MQ messages.

·     Failed to add the resource.

·     The UUID of logical network is required.

·     Operation failed. The UUID already exists.

·     No available VNIs.

 

Update router

Keyword

UPDATE_NSO_ROUTER_OP

Message text

Updated router “$1”.

Variable fields

$1: UUID of the vRouter.

Example

Updated router “edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027”.

Explanation

A vRouter was modified.

Possible failure causes

·     Invalid JSON format.

·     The UUID is required.

·     The logical network cannot be modified.

·     The CIDR has been used by a virtual subnet.

·     Different CIDRs cannot overlap.

·     Different vRouters in a logical network cannot use the same name.

·     Internal error.

·     Failed to modify the resource.

·     The resource does not exist.

 

Delete router

Keyword

DEL_NSO_ROUTER_OP

Message text

Deleted router “$1”.

Variable fields

$1: UUID of the vRouter.

Example

Deleted router “edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027”.

Explanation

A vRouter was deleted.

Possible failure causes

·     The resource does not exist.

·     The vRouter has been bound to virtual subnets.

·     Failed to delete the resource.

·     Internal error.

 

Add Site

Keyword

ADD_NSO_SIET_OP

Message text

Added site “$1”.

Variable fields

$1: UUID of the site.

Example

Added site “edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027”.

Explanation

A site was added.

Possible failure causes

·     Invalid JSON format.

·     The UUID is required.

·     The site name is required.

·     The URL is required.

·     The username is required.

·     The password is required.

·     The driver type is required.

·     The license capacity is insufficient.

·     Invalid request.

·     Internal error.

·     Failed to add the resource.

·     Operation failed. The UUID already exists.

·     The site name has been used.

·     The url has been used.

·     Failed to register the site with the DriverManager microservice.

 

Update Site

Keyword

UPDATE_NSO_SIET_OP

Message text

Updated site “$1”.

Variable fields

$1: UUID of the site.

Example

Updated site “edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027”.

Explanation

A site was modified.

Possible failure causes

·     Invalid JSON format.

·     The UUID is required.

·     The site name cannot be modified.

·     The custom settings of a site cannot be modified.

·     Invalid request.

·     The site has been bound to tenants.

·     The site has been bound to tenants.

·     Failed to update the site on the DriverManager microservice.

·     Internal error.

·     The resource does not exist.

·     The url has been used.

·     The maximum number of vRouters that can be bound to the site is smaller than the number of existing vRouters bound to the site.

·     The maximum number of virtual link layer networks that can be bound to the site is smaller than the number of existing virtual link layer networks bound to the site.

·     The maximum number of virtual subnets that can be bound to the site is smaller than the number of existing virtual subnets bound to the site.

·     Failed to modify the resource.

 

Delete Site

Keyword

DEL_NSO_SIET_OP

Message text

Deleted site “$1”.

Variable fields

$1: UUID of the site.

Example

Deleted site “edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027”.

Explanation

A site was deleted.

Possible failure causes

·     Invalid request.

·     The site has been bound to tenants.

·     The resource does not exist.

·     Failed to delete the resource.

 

Add subnet

Keyword

ADD_NSO_SUBNET_OP

Message text

Added subnet “$1”.

Variable fields

$1: UUID of the virtual subnet.

Example

Added subnet “edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027”.

Explanation

A virtual subnet was created.

Possible failure causes

·     The UUID is required.

·     The virtual subnet name is required.

·     The virtual link layer network UUID is required.

·     The IP version is required.

·     Invalid JSON format.

·     Different virtual subnets in a logical network cannot use the same name.

·     Internal error.

·     The specified virtual link layer network does not exist.

·     Failed to add the resource.

·     Operation failed. The UUID already exists.

·     The gateway IP address is required when the virtual link layer network is an external network.

·     The gateway IP address doesn’t belong to the subnet.

·     The CIDR overlaps with another CIDR in the same virtual link layer network.

·     Invalid address pool.

·     Only sites specified for the logical network are available.

·     DriverManager microservice processing failed.

·     The timer for waiting for driver responses expired.

·     Site processing failed.

·     Cannot reach sites.

 

Delete subnet

Keyword

DEL_NSO_SUBNET_OP

Message text

Deleted subnet “$1”.

Variable fields

$1: UUID of the virtual subnet.

Example

Deleted subnet “edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027”.

Explanation

A virtual subnet was deleted.

Possible failure causes

·     Invalid request.

·     The resource does not exist.

·     Internal error.

·     DriverManager microservice processing failed.

·     The timer for waiting for driver responses expired.

·     Site processing failed.

·     Cannot reach sites.

·     The virtual subnet has been bound to a vRouter.

·     The virtual subnet has vPorts.

·     Failed to delete the resource.

 

Add tenant

Keyword

ADD_NSO_TENANT_OP

Message text

Added tenant “$1”.

Variable fields

$1: UUID of the tenant.

Example

Added tenant “edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027”.

Explanation

A tenant was created.

Possible failure causes

·     Invalid JSON format.

·     The tenant name is required.

·     Invalid request.

·     Cannot reach sites.

·     The specified site does not exist.

·     Duplicate sites exist.

·     Failed to add the resource.

·     Invalid tenant type.

·     Operation failed. The UUID already exists.

·     The tenant name has been used.

·     DriverManager microservice processing failed.

·     The timer for waiting for driver responses expired.

·     Site processing failed.

 

Update tenant

Keyword

UPDATE_NSO_TENANT_OP

Message text

Updated tenant “$1”.

Variable fields

$1: UUID of the tenant.

Example

Updated tenant “edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027”.

Explanation

A tenant was modified.

Possible failure causes

·     Invalid JSON format.

·     The UUID is required.

·     The tenant type cannot be modified.

·     The username of the tenant administrator cannot be modified.

·     The password of the tenant administrator cannot be modified.

·     Invalid request.

·     The site has been bound to logical networks.

·     The specified site does not exist.

·     The resource does not exist.

·     The tenant name has been used.

·     The site has been bound to logical networks.

·     DriverManager microservice processing failed.

·     The timer for waiting for driver responses expired.

·     Site processing failed.

·     Cannot reach sites.

·     Failed to modify the resource.

 

Delete tenant

Keyword

DEL_NSO_TENANT_OP

Message text

Deleted tenant “$1”.

Variable fields

$1: UUID of the tenant.

Example

Deleted tenant “edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027”.

Explanation

A tenant was deleted.

Possible failure causes

·     The tenant has vPorts.

·     The tenant has logical networks.

·     Invalid request.

·     The resource does not exist.

·     DriverManager microservice processing failed.

·     The timer for waiting for driver responses expired.

·     Site processing failed.

·     Cannot reach sites.

·     Failed to delete the resource.

 

Add VNI

Keyword

ADD_NSO_VNI_OP

Message text

Added VNI “$1”.

Variable fields

$1: UUID of the global resource pool.

Example

Added VNI “edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027”.

Explanation

A global resource pool was created.

Possible failure causes

·     Invalid JSON format.

·     Invalid request.

·     The VNI name is required.

·     The VNI range is required.

·     Invalid VNI range.

·     Internal error.

·     Failed to add the resource.

·     Operation failed. The UUID already exists.

·     The VNI name has been used.

 

Update VNI

Keyword

UPDATE_NSO_VNI_OP

Message text

Updated VNI “$1”.

Variable fields

$1: UUID of the global resource pool.

Example

Updated VNI “edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027”.

Explanation

A global resource pool was modified.

Possible failure causes

·     The UUID is required.

·     The VNI name cannot be modified.

·     The VNI type cannot be modified.

·     Invalid JSON format.

·     Invalid request.

·     The resource does not exist.

·     Internal error.

·     Invalid VNI range.

·     The VNI name has been used.

·     The VNI has been used and cannot be modified.

·     Different VNI ranges cannot overlap.

·     Failed to modify the resource.

 

Delete VNI

Keyword

DEL_NSO_VNI_OP

Message text

Deleted VNI “$1”.

Variable fields

$1: UUID of the global resource pool.

Example

Deleted VNI “edfed45a-d3a9-4bb0-bfe4-b5fe5c3c9027”.

Explanation

A global resource pool was deleted.

Possible failure causes

·     Invalid request.

·     The resource does not exist.

·     Internal error.

·     Failed to delete the resource.

 


SYSTEM

This section contains system management messages.

Back up the configuration

Keyword

BACKUP_CONF_OP

Message text

Backed up the configuration.

Variable fields

N/A

Example

Backed up the configuration.

Explanation

A user backed up the configuration.

Possible failure causes

·     Failed to create the backup file.

·     The system is recovering.

·     The team to which the controller belongs is not recovered.

 

Update the diagnosis log level

Keyword

UPDATE_DIAG_LEVEL_OP

Message text

Updated the diagnosis log level: $1.

Variable fields

$1: Diagnosis log level setting:

·     3: 错误

·     4: 警告

·     6: 提示

·     7: 调试

·     -1: Disables diagnosis log entry output.

Example

Updated the diagnosis log level: {"diag": {"level": 6}}.

Explanation

A user changed the diagnosis log level setting.

Possible failure causes

·     Invalid JSON format.

·     Invalid level.

·     Internal error.

 

 


USER

This section contains user management messages.

Add a user

Keyword

ADD_USER_OP

Message text

Added a user: name: $1,request: $2

Variable fields

$1: Username.

$2: Detailed user information. If the operation fails, the message does not have this field.

Example

Added a user: name: 11, request: {

  "lock": "unlock",

  "password": "******",

  "system-roles": [

    {

      "role": "Administrator"

    }

  ]

}

Explanation

A user was added.

Possible failure causes

·     System role and tenant role can't be null at the same time.

·     The system role doesn’t exist.

·     Invalid JSON format.

·     Invalid system role.

·     Invalid tenant role

·     Invalid username.

·     Invalid password.

·     Failed to add the user.

·     The user already exists.

·     The system is recovering.

·     Internal error.

 

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.

·     Can't delete an online user.

·     The user doesn't exist.

·     The system is recovering.

·     Internal error.

 

Update user configuration

Keyword

UPDATE_USER_OP

Message text

Updated user configuration: name: $1, request:$2

Variable fields

$1: Username.

$2: User information.

Example

Updated user configuration: name: 11,request:{

newpassword”:”******”,

password”:”******”

}

Explanation

A user account was modified.

Possible failure causes

·     Invalid system role.

·     Invalid tenant role.

·     Invalid JSON format.

·     The token aging timer expired for the user.

·     Operation failed, because the user role doesn't have the permission.

·     Can't lock the user account you are using.

·     Invalid lock status of the user.

·     Invalid password.

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

·     The user doesn't exist.

·     The role doesn't exist.

·     The system is recovering.

·     Internal error.

 

Add a role

Keyword

ADD_ROLE_OP

Message text

Added a role: rolename: $1, request:$2

Variable fields

$1: Role name.

$2: Role information.

Example

Added a role: rolename: b, request: {

  "description": "test",

  "rules": {

    "rest": "POST,PUT,PATCH"

  }

}

Explanation

A role was added.

Possible failure causes

·     Invalid JSON format.

·     Invalid role rule.

·     Invalid Web menu.

·     Invalid description.

·     Invalid role name.

·     Invalid REST API rule.

·     The role name already exists.

·     Can’t assign the specified UI menu to the role.

·     The system is recovering.

·     The role name cannot be the same as the system default roles.

·     Internal error.

 

Delete a role

Keyword

DELETE_ROLE_OP

Message text

Deleted a role: $1.

Variable fields

$1: Role name.

Example

Deleted a role: role1.

Explanation

A user role was deleted.

Possible failure causes

·     Invalid role name.

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

·     Can’t delete system default roles.

·     The role does not exist.

·     The system is recovering.

·     Internal error.

 

Update a role

Keyword

UPDATE_ROLE_OP

Message text

Updated a role: rolename: $1, request: $2

Variable fields

$1: Role name.

$2: Role information.

Example

Updated a role: rolename: b, request: {

  "description": "",

  "rules": {

    "rest": "",

    "ui": [

      {

        "menu_name": "System",

        "menu_name_zh": "系统",

        "widgets": [

          {

            "subitems": [

              {

                "access": "R",

                "subitem_name": "Operator Log",

                "subitem_name_zh": "操作日志"

              },

            "widget_name": "Log",

            "widget_name_zh": "日志"

          }

       ]

    ]

  }

}

Explanation

A role was modified.

Possible failure causes

·     Invalid JSON format.

·     Invalid role name.

·     The role doesn't exist.

·     Invalid Web menu.

·     Invalid description.

·     Can't modify system default roles.

·     Invalid REST API rule.

·     The system is recovering.

·     Internal error.

 


WEB_DIAG

This section contains Web microservice messages.

Update diagnosis log level

Keyword

WEB_UPDATE_LOGGER_LEVER

Message text

Updated the diagnosis log level: $1.

Variable fields

$1: Diagnosis logging level setting:

·     3: Error.

·     4: Warning.

·     6: Informational.

·     7: Debug.

·     -1: Close. This setting disables diagnosis log entry output.

Example

Updated the diagnosis log level: {"diag": {"level": 6}}.

Explanation

The minimum diagnosis logging level changed.

Possible failure causes

·     Invalid json format.

·     Invalid parameter.

·     Internal server error.

 

 

  • Cloud & AI
  • InterConnect
  • Intelligent Computing
  • Security
  • SMB Products
  • Intelligent Terminal Products
  • Product Support Services
  • Technical Service Solutions
All Services
  • Resource Center
  • Policy
  • Online Help
All Support
  • Become a Partner
  • Partner Resources
  • Partner Business Management
All Partners
  • Profile
  • News & Events
  • Online Exhibition Center
  • Contact Us
All About Us
新华三官网