H3C VNF Manager App System Log Messages Reference-5W300

HomeSupportResource CenterSDNVNF ManagerVNF ManagerTechnical DocumentsReference GuidesLog Message ReferencesH3C VNF Manager App System Log Messages Reference-5W300
Download Book

Introduction

System logs record internal events that occur on the virtualized network function (VNF) manager app. System log messages include field description, message explanation, and recommended action, and provide reference for system analysis and maintenance.

This document assumes that the readers are familiar with data communications technologies and the H3C VNF manager app.

Viewing system log messages

On the H3C VCF controller interface, select Monitor > Log > System Log to enter system log view. The generated system log messages are displayed on pages as shown in Figure 1. The system logs with the origin as VNFM are generated by the VNFM manager app.

Figure 1 System log messages

 

Table 1 System log message elements

Element

Description

Severity

Severity level of the message. For more information about severity levels, see Table 4.

Time

Date and time when the log message was generated.

IP

IP address of the VCF controller where the VNF manager app resides.

Origin

Name of the service module that produced the message. For more information about service modules, see Table 1. The name of the VNF manager app is displayed as VNFM.

Topic

Topic for the log message.

Description

Text string that contains detailed information about the event or error.

 

Syslog message format

The VNF manager app can use the H3C VCF controller on which it resides to send system logs to syslog servers through the syslog protocol. To set the IP address and port number of a syslog server, select Controller > System > Configurations on the top navigation bar, and then select System Log.

By default, the system logs sent through the syslog protocol are 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 3.

TIMESTAMP

Date and time when the event occurred.

Hostname

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

Origin

Name of the service module that produced the message. For more information about service modules, see Table 1. The name of the VNF manager app is displayed as VNFM.

severity

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

Keywords

Keywords of the message that facilitate searching or memorizing.

CONTENT

Text string that contains detailed information about the event or error.

 

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

Table 3 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.

 

System log messages are classified into five severity levels from 0 to 4. The higher the number, the higher the severity, as shown in Table 4.

Table 4 System log message severity levels

Level

Icon

Severity

Description

0

alert-info

Info

Information message.

1

Warning

Warning condition.

2

Error

Error condition.

3

Serious

Serious condition.

4

alert-crit

Critical

Critical condition.

 

Table 5 shows the mappings between system log message severity levels and syslog message severity levels.

Table 5 Severity level mappings

System log message severity level

Syslog message severity level

0

6

1

4

2

3

3

2

4

0

 

Using this document

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.

DELETE_HOST_SUCCESS

Message text

Presents the message description.

Deleted host $1 with IP address $2.

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: Host name.

$2: IP address of the host.

Severity level

Provides the severity level of the message.

alert-info

Example

Provides a real message example.

Deleted host 255_101 with IP address 192.168.255.101.

Explanation

Explains the message, including the event or error cause.

The host is successfully deleted.

Recommended action

Provides recommended actions. For informational messages, no action is required.

No action is required.

 

 


VNFM

This section contains VNF manager app messages.

Add an existing VNF flavor

Keyword

FLAVOR_EXISTS

Message text

VNF flavor $1 already exists on host $2.

Variable fields

$1: VNF flavor name.

$ 2: Host name.

Severity level

alert-info

Example

VNF flavor 1_cpu_1024MB_memory_8192MB_storage already exists on host 16.

Explanation

The VNF flavor to be added to a host already exists on the host. This message appears if the system detects the existence of a VNF flavor on a host before adding the VNF flavor to the host.

Recommended action

No action is required.

 

Failure to add a VNF flavor

Keyword

ADD_FLAVOR_FAILED

Message text

Failed to add VNF flavor $1 to host $2.

Variable fields

$1: VNF descriptor name.

$ 2: Host name.

Severity level

Example

Failed to add VNF flavor test to host 16.

Explanation

The system failed to add a VNF flavor to a host. Possible failure causes include incorrect parameters for connecting to the host and network interruption.

Recommended action

Verify that parameters for connecting to the host and network connection are correct.

 

Failure to delete a VNF flavor

Keyword

DELETE_FLAVOR_FAILED

Message text

Failed to delete VNF flavor $1 from host $2.

Variable fields

$1: VNF flavor name.

$ 2: Host name.

Severity level

Example

Failed to delete VNF flavor test from host 16.

Explanation

The system failed to delete a VNF flavor from a host. Possible failure causes include incorrect parameters for connecting to the host and network interruption.

Recommended action

Verify that parameters for connecting to the host and network connection are correct.

 

Success in adding a host

Keyword

ADD_HOST_SUCCESS

Message text

Added host $1 with IP address $2.

Variable fields

$1: Host name.

$ 2: IP address of the host.

Severity level

alert-info

Example

Added host 255_101 with IP address 192.168.255.101.

Explanation

A host was added successfully.

Recommended action

No action is required.

 

Success in deleting a host

Keyword

DELETE_HOST_SUCCESS

Message text

Deleted host $1 with IP address $2.

Variable fields

$1: Host name.

$ 2: IP address of the host.

Severity level

alert-info

Example

Deleted host 255_101 with IP address 192.168.255.101.

Explanation

A host was deleted successfully.

Recommended action

No action is required.

 

Success in modifying an image file

Keyword

MODIFY_HOST_SUCCESS

Message text

Modified host $1 with IP address $2.

Variable fields

$1: Host name.

$ 2: IP address of the host.

Severity level

alert-info

Example

Modified host 192.168.1.250 with IP address 192.168.1.250.

Explanation

The configuration of a host was successfully modified.

Recommended action

No action is required.

 

Success in uploading an image file

Keyword

UPLOAD_IMAGE_SUCCESS

Message text

Uploaded image $1.

Variable fields

$1: Image file name.

Severity level

alert-info

Example

Uploaded image VSR1000_H3C-CMW710-E0321-X64.qco.

Explanation

An image file was successfully uploaded to all connected hosts.

Recommended action

No action is required.

 

Success in deleting an image file

Keyword

DELETE_IMAGE_SUCCESS

Message text

Deleted image $1.

Variable fields

$1: Image file name.

Severity level

alert-info

Example

Deleted image VSR1000_H3C-CMW710-E0321-X64.qco.

Explanation

An image file was successfully deleted.

Recommended action

No action is required.

 

Success in referencing an image file

Keyword

REFERENCE_IMAGE_SUCCESS

Message text

Referenced image $1.

Variable fields

$1: Image file name.

Severity level

alert-info

Example

Referenced image vBRAS1000_H3C-CMW710-E0324L03-X64.qco.

Explanation

An image file was successfully referenced.

Recommended action

No action is required.

 

Success in uploading an image file to a host

Keyword

UPLOAD_IMAGE_TO_HOST

Message text

Uploaded image $1:$2 to host $3.

Variable fields

$1: Image file name.

$2: Image file ID.

$3: Host name.

Severity level

alert-info

Example

Uploaded image VSR1000_H3C-CMW710-E0321-X64.qco:0689b5a4-3062-4112-9a78-83d1dea511a3 to host 255_101.

Explanation

An image file was successfully uploaded to a host.

Recommended action

No action is required.

 

Failure to upload an image file to a host

Keyword

UPLOAD_IMAGE_TO_HOST_FAILED

Message text

Failed to upload image $1 to host $2.

Variable fields

$1: Image file name.

$2: Host name.

Severity level

Example

Failed to upload image VSR1000_H3C-CMW710-E0321-X64.qco to host 255_101.

Explanation

The system failed to upload an image file to a host. Possible failure causes include the following:

·     Incorrect parameters for connecting to the host.

·     Network interruption.

·     Insufficient disk space on the host.

Recommended action

Verify the following information:

·     Parameters for connecting to the host are correct.

·     Network connection is correct.

·     The host has enough disk space.

 

Success in deleting an image file from a host

Keyword

DELETE_IMAGE_FROM_HOST

Message text

Deleted image $1:$2 from host $3.

Variable fields

$1: Image file name.

$2: Image file ID.

$3: Host name.

Severity level

alert-info

Example

Deleted image VSR1000_H3C-CMW710-E0321-X64.qco:0689b5a4-3062-4112-9a78-83d1dea511a3 from host 255_101.

Explanation

An image file was successfully deleted from a host.

Recommended action

No action is required.

 

Failure to delete an image file from a host

Keyword

DELETE_IMAGE_FROM_HOST_FAILED

Message text

Failed to delete image $1:$2 from host $3.

Variable fields

$1: Image file name.

$2: Image file ID.

$3: Host name.

Severity level

Example

Failed to delete image VSR1000_H3C-CMW710-E0321-X64.qco: 403cc5e9-8f31-4379-9c01-7a93dba58c18 from host 255_101.

Explanation

The system failed to delete an image file from a host. Possible failure causes include incorrect parameters for connecting to the host and network interruption.

Recommended action

Verify that parameters for connecting to the host and network connection are correct.

 

Successful ISSU upgrade

Keyword

ISSU_SUCCESS

Message text

Performed ISSU for VNF $1 by using IP address $2, username $3, and IPE file $4.

Variable fields

$1: VNF name.

$2: Management IP address of the VNF.

$3: NETCONF username of the VNF.

$4: IPE file name.

Severity level

alert-info

Example

Performed ISSU for VNF vnf_ha by using IP address 192.168.112.12, username admin, and IPE file VSR1000-X64_base.ipe.

Explanation

A VNF was successfully upgraded through ISSU.

Recommended action

No action is required.

 

Success in assigning a management IP address to an IRF VNF

Keyword

ALLOCATED_MANAGENMENT_IP

Message text

Allocated management IP $1 mask $2 to VNF $3 from VNF descriptor $4.

Variable fields

$1: IP address assigned to a VNF.

$2: Mask of the IP address.

$3: VNF name.

$4: VNF descriptor name.

Severity level

alert-info

Example

Allocated management IP 2.2.2.1 mask 255.255.255.255 to VNF test1 from VNF descriptor ha.

Explanation

When creating an IRF VNF, the system successfully assigned a management IP address in the management IP address pool of the VNF descriptor to the VNF.

Recommended action

No action is required.

 

Failure to assign a management IP address to an IRF VNF

Keyword

ALLOCATED_MANAGENMENT_IP_FAILED

Message text

Failed to allocate a management IP to VNF $1 from VNF descriptor $2.

Variable fields

$1: VNF name.

$2: VNF descriptor name.

Severity level

Example

Failed to allocate a management IP to VNF test2 from VNF descriptor ha.

Explanation

When creating an IRF VNF, the system failed to assign a management IP address in the management IP address pool of the VNF descriptor to the VNF.

Recommended action

Log in to the VNF and manually assign a management IP address to the VNF.

 

Success in assigning an IP address to a VNF port

Keyword

ALLOCATED_PORT_IP

Message text

Allocated IP $1 mask $2 to port $3 of VNF $4 from NIC $5 of host $6.

Variable fields

$1: IP address assigned to the VNF port.

$2: Mask of the IP address.

$3: VNF port name.

$4: VNF name.

$5: Name of the NIC on the host.

$6: Host name.

Severity level

alert-info

Example

Allocated IP 192.168.34.180 mask 255.255.255.0 to port 2/0 of VNF test1 from NIC ens161 of host 18.

Explanation

When creating a VNF, the system successfully assigned an IP address in the IP address pool of a NIC on a host to a port of the VNF.

Recommended action

No action is required.

 

Failure to assign an IP address to a VNF port

Keyword

ALLOCATE_PORT_IP_FAILED

Message text

Failed to allocate an IP to port $1 of VNF $2 from NIC $3 of host $4.

Variable fields

$1: VNF port name.

$2: VNF name.

$3: Name of the NIC on the host.

$4: Host name.

Severity level

Example

Failed to allocate an IP to port 4/0 of VNF test1 from NIC ens193 of host 18.

Explanation

When creating a VNF, the system failed to assign an IP address in the IP address pool of a NIC on a host to a port of the VNF.

Recommended action

Log in to the VNF and manually assign an IP address to the port of the VNF.

 

Release the management IP address of an IRF VNF

Keyword

RELEASED_MANAGEMENT_IP

Message text

Released management IP $1 mask $2 of VNF $3 to VNF descriptor $4.

Variable fields

$1: IP address released.

$2: Mask of the IP address.

$3: VNF name.

$4: VNF descriptor name.

Severity level

alert-info

Example

Released management IP 2.2.2.1 mask 255.255.255.255 of VNF test1 to VNF descriptor ha.

Explanation

When deleting an IRF VNF, the system released the management IP address of the VNF, which was obtained from the management IP address pool of the VNF descriptor.

Recommended action

No action is required.

 

Release the IP address of a VNF port

Keyword

RELEASED_PORT_IP

Message text

Released IP $1 mask $2 of port $3 on VNF $4 to NIC $5 of host $6.

Variable fields

$1: IP address released.

$2: Mask of the IP address.

$3: VNF port name.

$4: VNF name.

$5: Name of the NIC on the host.

$6: Host name.

Severity level

alert-info

Example

Released IP 192.168.34.180 mask 255.255.255.0 of port 2/0 on VNF test1 to NIC ens161 of host 18.

Explanation

When deleting a VNF, the system released the IP address of a port on the VNF, which was obtained from the IP address pool of a NIC on a host.

Recommended action

No action is required.

 

Create a virtual machine for a VNF

Keyword

CREATE_VM

Message text

Created VM $1 for VNF $2 on host $3.

Variable fields

$1: Virtual machine ID.

$2: VNF name.

$3: Host name.

Severity level

alert-info

Example

Created VM 5f17bcc6-ea15-4040-9b75-aa092ba80ae4 for VNF test2 on host 18.

Explanation

When creating a VNF, the system created a virtual machine for the VNF on a host.

Recommended action

No action is required.

 

Create a virtual machine port

Keyword

CREATE_PORT

Message text

Created port $1 to connect the VM of VNF $2 to NIC $3 of host $4.

Variable fields

$1: ID of the port created for a virtual machine.

$2: VNF name.

$3: Name of the NIC on the host.

$4: Host name.

Severity level

alert-info

Example

Created port ca8cddd7-82fe-42c2-b9c2-a1afc4017549 to connect the VM of VNF test2 to NIC ens161 of host 18.

Explanation

When creating a VNF, the system created a port for the virtual machine of the VNF to connect to a NIC of a host.

Recommended action

No action is required.

 

Delete a virtual machine

Keyword

DELETE_VM

Message text

Deleted VM $1 of VNF $2 from host $3.

Variable fields

$1: ID of the virtual machine.

$2: VNF name.

$3: Host name.

Severity level

alert-info

Example

Deleted VM 51028c50-dba8-4e06-81bd-b371a51fd5d7 of VNF test1 from host 18.

Explanation

When deleting a VNF, the system deleted the virtual machine of the VNF from a host and deleted the port of the virtual machine.

Recommended action

No action is required.

 

Failure to connect to a host

Keyword

CONNECT_HOST_FAILED

Message text

Failed to connect to host $1. $2.

Variable fields

$1: Host IP address.

$2: Failure reason.

Severity level

Example

Failed to connect to host 192.168.250.214. Connect to 192.168.250.214:5000 [/192.168.250.214] failed: connect timed out.

Explanation

The system failed to connect to a host when performing operations such as creating a VNF flavor or uploading an image file. Possible failure causes include incorrect parameters for connecting to the host and network interruption.

Recommended action

Verify that parameters for connecting to the host and network connection are correct.

 

Host status change

Keyword

HOST_CHANGE_STATUS

Message text

The host status of $1 changed from $2 to $3.

Variable fields

$1: Host name.

$2: Old host status.

$3: New host status.

Severity level

Example

The host status of host1 changed from Abnormal to Normal.

Explanation

The host status changed.

Recommended action

If the current host status is normal, no action is required. If the current host status is abnormal, perform the following tasks:

·     Verify that the connection between the VNF Manager app and the host is normal.

·     Verify that the host is running properly.

 

Success in allocating IP to logical interface on VNF

Keyword

ALLOCATED_INTERFACE_IP

Message text

Assigned IP address $1 with mask $2 to interface $3 of VNF $4.

Variable fields

$1: IP address allocated to a VNF logical interface.

$2: Mask of the IP address allocated to a VNF logical interface.

$3: VNF logical interface name.

$4: VNF name.

Severity level

alert-info

Example

Assigned IP address 192.168.161.133 with mask 255.255.0.0 to interface Reth233 of VNF xl-vnf1.

Explanation

The system successfully allocated the logical interface an available IP address in the IP address pool configured for the logical interface when a VNF was created.

Recommended action

No action is required.

 

Failure to allocate IP to logical interface on VNF

Keyword

ALLOCATE_INTERFACE_IP_FAILED

Message text

Failed to assign an IP address to interface $1 of VNF $2.

Variable fields

$1: VNF logical interface name.

$2: VNF name.

Severity level

Example

Failed to assign an IP address to interface Reth233 of VNF xl-vnf1.

Explanation

The system failed to allocate the logical interface an available IP address in the IP address pool configured for the logical interface when a VNF was created.

Recommended action

·     Verify that the IP address pool has available IP addresses.

·     Log in to the VNF and manually configure an IP address for the logical interface.

 

Success in deleting a VNF flavor

Keyword

DELETE_FLAVOR_SUCCESS

Message text

Deleted flavor $1.

Variable fields

$1: Flavor name.

Severity level

alert-info

Example

Deleted flavor flavor1.

Explanation

A flavor was successfully deleted.

Recommended action

No action is required.

 

Release logical interface IP on VNF

Keyword

RELEASED_INTERFACE_IP

Message text

Released IP address $1 with mask $2 from interface $3 of VNF $4.

Variable fields

$1: Released IP address.

$2: Mask of the released IP address.

$3: VNF logical interface name.

$4: VNF name.

Severity level

alert-info

Example

Released IP address 192.168.161.133 with mask 255.255.0.0 from interface Reth233 of VNF vnf1.

Explanation

When a VNF was deleted and the VNF logical interface IP address was allocated from the IP address pool of the logical interface, the IP address was released.

Recommended action

No action is required.

 

VNF ISSU failure

Keyword

ISSU_VNF_FAILED

Message text

VNF ISSU failed: $1

Variable fields

$1: Failure reason.

Severity level

alert-info

Example

VNF ISSU failed: flash:/Vbras1000_H3C-CMW710-E0324L03-X64.ipe is already active and can’t be active again.

Explanation

VNF ISSU failed. The failure reason was prompted.

Recommended action

Perform an action according to the failure reason.

 

VNF status change

Keyword

VNF_CHANGE_STATUS

Message text

The VNF status of $1 changed from $2 to $3.

Variable fields

$1: VNF name.

$2: Old VNF status.

$3: New VNF status.

Severity level

Example

The VNF status of test_vnf changed from Unknown to Active.

Explanation

The VNF status changed.

Recommended action

If the current VNF status is normal, no action is required. If the current VNF status is abnormal, perform the following tasks:

·     Verify that the connection between the VNF Manager app and the host is normal.

·     Log in to the host and verify that the VNF exists and operates properly on the host.

 

 

  • 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
新华三官网