Title | Size | Downloads |
---|---|---|
H3C SNA Center System Log Messages Reference-E11xx-5W101-book.pdf | 225.72 KB |
- Table of Contents
- Related Documents
-
|
H3C SNA Center |
System Log Messages Reference |
|
|
Document version: 5W101-20191009
Copyright © 2019 New H3C Technologies Co., Ltd. All rights reserved.
No part of this manual may be reproduced or transmitted in any form or by any means without prior written consent of New H3C Technologies Co., Ltd.
Except for the trademarks of New H3C Technologies Co., Ltd., any trademarks that may be mentioned in this document are the property of their respective owners.
The information in this document is subject to change without notice.
Contents
Viewing system log messages· 1
License installed successfully· 4
Disconnection from the license server 5
Reconnection to the license server 5
Failure of connection to the license server 6
Controller forced offline by license server 6
Reconnection to the license server due to ageout 6
Entered fail-safe state due to authorization failure· 7
Entered fail-safe state due to connection failure· 7
Exited fail-safe state after the fail-safe period· 7
Exited fail-safe state after authorization· 8
Exited fail-safe state after disconnection· 8
License expiration early warning· 8
Insufficient quantity-based licenses· 9
Expansion of a matrix cluster 9
Quantity-based license applied successfully· 10
Failure to apply for quantity-based licenses· 10
Quantity-based license released successfully· 11
Failure to release quantity-based licenses· 11
Quantity-based license synchronized successfully· 12
Failure to synchronize quantity-based licenses· 12
Product information registered successfully· 13
Failure to register product information· 14
Product information deregistered successfully· 15
Failure to deregister product information· 15
Applied for licenses from the license server successfully· 16
Failure to apply for licenses from the license server 16
Deploy mircoservice started successfully· 18
Failure to connect to database· 18
Failure to create database table· 18
Failure to obtain component's system configuration file· 19
Component installed successfully· 19
Component re-installed successfully· 19
Component uninstalled successfully· 20
Component re-uninstalled successfully· 20
Component upgraded successfully· 20
Component rolled back successfully· 21
Component installation stopped successfully· 21
Component uninstallation stopped successfully· 21
Introduction
System logs record internal events that occur on SNA Center. 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 H3C SNA Center products.
Viewing system log messages
1. Log in to SNA Center.
2. Click Settings in the System area.
3. On the top navigation bar, click Logs.
4. From the left navigation pane, select Information.
5. Click the System Logs tab.
The paginated system log message list is displayed, as shown in Figure 1.
Figure 1 System log message list
Table 1 System log message elements
Element | Description |
Severity level | Severity level of the log message. For more information about severity levels, see Table 5. |
Time | Date and time when the log message was generated. |
SNA Component Name | Name of the SNA component that generated the log message. |
Host Name | Name of the host that generated the log message. |
Service Name | Name of the service that produced the log message. |
Description | Text string that contains detailed information about the event or error. |
Syslog message format
SNA Center can send system logs to syslog servers through the syslog protocol. To configure system log output to syslog servers, go to the Logs > Configuration > System Logs page.
By default, SNA Center sends system logs to syslog servers 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 or IP address of the host that produced the message. |
Service | Name of the service module that produced the message. For more information about service modules, see Table 3. |
severity | Severity level of the message. For more information, 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. |
Table 3 lists the SNA Center service modules that might produce system log messages.
Service module name | Description |
LICENSE | License module. |
SNACenter | SNA Center module. |
The syslog protocol classifies syslog messages into eight severity levels from 0 to 7. The lower the number, the higher the severity, as shown in Table 4.
Table 4 Syslog severity levels defined by the Syslog protocol
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. |
SNA Center uses the eight severity levels defined by the syslog protocol to classify its system logs, with a unique icon assigned each severity level, as shown in Table 5.
Table 5 System log severity levels in SNA Center
Level | Icon | Severity | Description |
0 | Emergent | 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 | Info | Informational message. | |
7 | Debug | Debugging message. |
Using this document
This document categories system log messages by service module and explains the 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. | LICENSE_INSTALL |
Message text | Presents the message description. | $1 license successfully installed. |
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: License name. |
Severity level | Provides the severity level of the message. | Info |
Example | Provides a real message example. | Base license successfully installed. |
Explanation | Explains the message. | A license was installed. |
Recommended action | Provides recommended actions. For informational messages, no action is required. | No action is required. |
LICENSE
This section contains license management messages.
License installed successfully
Keyword | LICENSE_INSTALL |
Message text | License ($1, $2) installed successfully. |
Variable fields | $1: Product ID. $2: License name. |
Severity level | Info |
Example | License (B0000002, SUCNodeNum) installed successfully. |
Explanation | The specified license was successfully installed. |
Recommended action | No action is required. |
Single license reclaimed
Keyword | LICENSE_RECLAIM |
Message text | License($1, $2) has been reclaimed. Count: $3. |
Variable fields | $1: Product ID. $2: License name. $3: Capacity of the reclaimed license. This field is displayed only when a quantity-based license is reclaimed. |
Severity level | Warning |
Example | License (B0000002, SUCNodeNum) has been reclaimed. Count: $3. |
Explanation | The specified license was reclaimed. |
Recommended action | No action is required. |
License server connection
Keyword | LICENSE_SERVER_CONNECT |
Message text | The controller established a connection to the license server. |
Variable fields | N/A |
Severity level | Info |
Example | The controller established a connection to the license server. |
Explanation | The controller established a connection to the license server. |
Recommended action | No action is required. |
Disconnection from the license server
Keyword | LICENSE_SERVER_DISCONNECT |
Message text | The controller was disconnected from the license server. |
Variable fields | N/A |
Severity level | Warning |
Example | The controller was disconnected from the license server. |
Explanation | The controller was disconnected from the license server. |
Recommended action | If a user disconnected the controller from the license server, no action is required. If the disconnection is unexpected, follow these steps: 1. Examine the connectivity between the controller and the license server. 2. Verify that the license server settings on the controller are correct. 3. Verify that the license server is operating correctly and providing services. |
Reconnection to the license server
Keyword | LICENSE_SERVER_RECONNECT |
Message text | Reconnecting to the license server after a disconnection. |
Variable fields | N/A |
Severity level | Warning |
Example | Reconnecting to the license server after a disconnection. |
Explanation | This message is sent when the controller failed to re-connect to the license server when the controller in LOGIN state was first disconnected from the license server. |
Recommended action | If a user disconnected the controller from the license server, no action is required. If the connection failure is unexpected, follow these steps: 1. Examine the connectivity between the controller and the license server. 2. Verify that the license server settings on the controller are correct. 3. Verify that the license server is operating correctly and providing services. |
Failure of connection to the license server
Keyword | LICENSE_SERVER_CONNECT_FAILED |
Message text | Failed to connect to the license server. |
Variable fields | N/A |
Severity level | Warning |
Example | Failed to connect to the license server. |
Explanation | The controller failed to connect to the license server. |
Recommended action | 1. Verify that the license server settings on the controller are correct. 2. Verify that the license server is operating correctly. |
Controller forced offline by license server
Keyword | LICENSE_SERVER_FORCE_CLIENT_OFFLINE |
Message text | The controller was forced offline by license server. |
Variable fields | N/A |
Severity level | Warning |
Example | The controller was forced offline by license server. |
Explanation | The license server forced the controller to go offline. |
Recommended action | To obtain authorization, reconnect the controller to the license server. |
Reconnection to the license server due to ageout
Keyword | LICENSE_SERVER_AGED_RECONNECT |
Message text | The controller started to reconnect to the license server because the token of the controller aged out. |
Variable fields | N/A |
Severity level | Warning |
Example | The controller started to reconnect to the license server because the token of the controller aged out. |
Explanation | The token of the controller aged out and the controller started to reconnect to the license server. |
Recommended action | Verify the network connectivity between the license server and the controller. |
Entered fail-safe state due to authorization failure
Keyword | ENTER_FAILSAFE_NO_LICENSE |
Message text | The controller entered into fail-safe mode because it failed to obtain licenses from the remote license server. |
Variable fields | N/A |
Severity level | Warning |
Example | The controller entered into fail-safe mode because it failed to obtain licenses from the remote license server. |
Explanation | After the controller connected to the license server, the controller failed to obtain a license and entered fail-safe state. |
Recommended action | Log in to the license server and verify that the status of the required license is normal. |
Entered fail-safe state due to connection failure
Keyword | ENTER_FAILSAFE_CONNECT_FAILED |
Message text | The controller entered into fail-safe mode because a connection error occurred between the controller and the license server. |
Variable fields | N/A |
Severity level | Warning |
Example | The controller entered into fail-safe mode because a connection error occurred between the controller and the license server. |
Explanation | The controller lost its connection to the license server and entered fail-safe state. |
Recommended action | Verify the network connectivity between the license server and the controller. |
Exited fail-safe state after the fail-safe period
Keyword | EXIT_FAILSAFE_EXPIRED |
Message text | The controller exited from fail-safe mode because the 30-day fail-safe period expired. |
Variable fields | N/A |
Severity level | Warning |
Example | The controller exited from fail-safe mode because the 30-day fail-safe period expired. |
Explanation | The 30-day fail-safe period expired and the controller exited fail-safe state. |
Recommended action | 1. On the license management page, verify that the controller is connected to the license server. 2. Verify that the license server can assign a license to the controller. |
Exited fail-safe state after authorization
Keyword | EXIT_FAILSAFE_OBTAINED |
Message text | The controller exited from fail-safe mode because it had obtained licenses from the license server. |
Variable fields | N/A |
Severity level | Warning |
Example | The controller exited from fail-safe mode because it had obtained licenses from the license server. |
Explanation | The controller obtained a license and exited fail-safe state. |
Recommended action | No action is required. |
Exited fail-safe state after disconnection
Keyword | EXIT_FAILSAFE_DISCONNECTED |
Message text | The controller exited from fail-safe mode because it disconnected from the license server. |
Variable fields | N/A |
Severity level | Warning |
Example | The controller exited from fail-safe mode because it disconnected from the license server. |
Explanation | The controller closed its connection to the license server and exited fail-safe state. |
Recommended action | No action is required. |
License expiration early warning
Keyword | LICENSE_EXPIRED |
Message text | License ($1, $2) is about to expire in 10 days. |
Variable fields | $1: Product ID. $2: License name. |
Severity level | Warning |
Example | License (B0000002, SUCNodeNum) is about to expire in 10 days. |
Explanation | The specified remote license is about to expire in 10 days. |
Recommended action | 1. Log in to the license server to verify that the remote license is authorized. 2. If the remote license is not authorized, purchase the license. |
Insufficient quantity-based licenses
Keyword | LICENSE_INSUFFICIENT |
Message text | Insufficient $1 licenses. Please purchase more licenses. |
Variable fields | $1: Name of the quantity-based licenses. |
Severity level | Critical |
Example | Insufficient MaxNodeNum licenses. Please purchase more licenses. |
Explanation | This message is sent when a quantity-based license is insufficient. |
Recommended action | Purchase more licenses. |
Expansion of a matrix cluster
Keyword | LICENSE_K8S_NODE_ADD |
Message text | Member $1 joined the cluster. Current cluster members are $2. |
Variable fields | $1: Node that joined the cluster, in the host name/host IP address format. $2: All nodes that are currently in the cluster, each in the host name/host IP address format. |
Severity level | Info |
Example | Member node2/192.168.139.31 joined the cluster. Current cluster members are node2/192.168.139.31; node1/192.168.139.30; node3/192.168.139.32. |
Explanation | This message is sent when a node joins the Matrix cluster. |
Recommended action | No action is required. |
Shrink of a matrix cluster
Keyword | LICENSE_K8S_NODE_DELETE |
Message text | Member $1 left the cluster. Current cluster members are $2. |
Variable fields | $1: Node that left the cluster, in the host name/host IP address format. $2: All nodes that are currently in the cluster, each in the host name/host IP address format. |
Severity level | Info |
Example | Member node3/192.168.139.32 left the cluster. Current cluster members are node2/192.168.139.31; node1/192.168.139.30. |
Explanation | This message is sent when a node leaves the Matrix cluster. |
Recommended action | No action is required. |
Quantity-based license applied successfully
Keyword | LICENSES_APPLY |
Message text | Succeed to apply licenses: $1. |
Variable fields | $1: License information. |
Severity level | Info |
Example | Succeed to apply licenses: { "count": 6, "featureName": "SiteNodeNum", "pdtId": "0B000002" }. |
Explanation | The devices successfully applied for a quantity-based license. |
Recommended action | No action is required. |
Failure to apply for quantity-based licenses
Keyword | LICENSES_APPLY |
Message text | Failed to apply licenses: $1. |
Variable fields | $1: License information. |
Severity level | Warning |
Example | Failed to apply licenses: { "count": 6, "featureName": "SiteNodeNum1", "pdtId": "0B000002" }. |
Explanation | Failed to apply for a quantity-based license. |
Recommended action | Verify that the license server has enough licenses. |
Quantity-based license released successfully
Keyword | LICENSES_RELEASE |
Message text | Succeed to release licenses: $1. |
Variable fields | $1: License information. |
Severity level | Info |
Example | Succeed to release licenses: { "count": 6, "featureName": "SiteNodeNum", "pdtId": "0B000002" }. |
Explanation | The quantity-based license was successfully released. |
Recommended action | No action is required. |
Failure to release quantity-based licenses
Keyword | LICENSES_RELEASE |
Message text | Failed to release licenses: $1. |
Variable fields | $1: License information. |
Severity level | Warning |
Example | Failed to release licenses: { "count": 6, "featureName": "SiteNodeNum1", "pdtId": "0B000002" }. |
Explanation | Failed to release a quantity-based license. |
Recommended action | Verify that the specified license information is correct. |
Quantity-based license synchronized successfully
Keyword | LICENSES_SYNC |
Message text | Succeed to synchronize licenses: $1. |
Variable fields | $1: License information. |
Severity level | Info |
Example | Succeed to synchronize licenses: { "count": 6, "featureName": "SiteNodeNum", "pdtId": "0B000002" }. |
Explanation | The quantity-based license was successfully synchronized. |
Recommended action | No action is required. |
Failure to synchronize quantity-based licenses
Keyword | LICENSES_SYNC |
Message text | Failed to synchronize licenses: $1. |
Variable fields | $1: License information. |
Severity level | Warning |
Example | Failed to synchronize licenses: { "count": 6, "featureName": "SiteNodeNum1", "pdtId": "0B000002" }. |
Explanation | Failed to synchronize the quantity-based licenses. |
Recommended action | Verify that the cluster status is normal. |
Product information registered successfully
Keyword | LICENSE_REGISTER |
Message text | Succeed to register the product information $1. |
Variable fields | $1: License information. |
Severity level | Info |
Example | Succeed to register the product information B000002{ "pdt_name":"abc", "licenses":[ { "name":"SUCNodeNum", "function":false, "base":true }, { "name":"SiteNodeNum", "function":false } ] }. |
Explanation | The device successfully registered its product information to the license server. |
Recommended action | No action is required. |
Failure to register product information
Keyword | LICENSE_REGISTER |
Message text | Failed to register the product information $1. |
Variable fields | $1: License information. |
Severity level | Info |
Example | Failed to register the product information 0B000002 : { "pdt_name":"abc", "licenses" : [ { "name1": "SUCNodeNum", "function": false, "base": true }, { "name": "SiteNodeNum", "function": false } ] } |
Explanation | The device failed to register the product information to the license server. |
Recommended action | Verify that the specified license information is correct. |
Product information deregistered successfully
Keyword | LICENSE_REGISTER |
Message text | · Deregister the specified license of the product: Succeed to deregister the product information $1: $2. · Deregister all licenses of the product: Succeed to deregister the product information $1. |
Variable fields | · Deregister the specified license: ¡ $1: Product information. ¡ $2: License information. · Deregister all licenses: ¡ $1: Product information. |
Severity level | Info |
Example | · Deregister the specified license of the product: Succeed to deregister the product information abc/0B000002: [SUCNodeNum]. · Deregister all licenses of the product: Succeed to deregister the product information 0B000002. |
Explanation | The device successfully deregistered its product information from the license server. |
Recommended action | No action is required. |
Failure to deregister product information
Keyword | LICENSE_REGISTER |
Message text | Failed to deregister the product information $1. |
Variable fields | $1: Product information. |
Severity level | Info |
Example | Failed to deregister the product information 0B000002. |
Explanation | The device failed to deregister the product information from the license server. |
Recommended action | Verify that the cluster status is normal. |
Applied for licenses from the license server successfully
Keyword | LICENSE_UPDATE |
Message text | Succeed to update licenses: $1 |
Variable fields | $1: Product information. |
Severity level | Info |
Example | Succeed to update licenses: [ { "feature_name": "SUCunLimited", "need_function": false, "pdt_id": "B000002" }, { "feature_name": "SiteNodeNum", "need_count": 10, "pdt_id": "B000002" }, { "feature_name": "SUCNodeNum", "need_count": 10, "pdt_id": "B000002" } ] |
Explanation | The device applied for licenses from the license server successfully. |
Recommended action | No action is required. |
Failure to apply for licenses from the license server
LICENSE_UPDATE | |
Message text | Failed to update licenses:$1 |
Variable fields | $1: Product information. |
Severity level | Warning |
Example | Failed to update licenses: {"config":[{"feature_name": "SUCNodeNum","need_count": 10}]} |
Explanation | Failed to apply for licenses from the license server. |
Recommended action | · Verify that the specified license information is correct. · Verify that the cluster status is normal. |
SNACenter
This section contains log messages generated by the SNA Center component deployment module.
Deploy mircoservice started successfully
Keyword | START_DEPLOY_SYSTEM |
Message text | Started deploy system successfully |
Variable fields | N/A |
Severity level | Info |
Example | Started deploy system successfully |
Explanation | The deploy mircoservice started successfully. |
Recommended action | No action is required. |
Failure to connect to database
Keyword | CONNECT_DATABASE |
Message text | Failed to connect database |
Variable fields | N/A |
Severity level | Warning |
Example | Failed to connect database |
Explanation | Failed to connect to the database. |
Recommended action | Verify that the specified database address and port number are correct. |
Failure to create database table
Keyword | CREATE_DATABASE_TABLE |
Message text | Failed to create database table |
Variable fields | N/A |
Severity level | Warning |
Example | Failed to create database table |
Explanation | Failed to create the database table. |
Recommended action | Contact technical support to check for SQL script syntax errors. |
Failure to obtain component's system configuration file
Keyword | GET_COMPONENT_CONFIGURATION |
Message text | Failed to get system configuration file for the component |
Variable fields | N/A |
Severity level | Warning |
Example | Failed to get system configuration file for the component |
Explanation | Failed to obtain the system configuration file of the component. |
Recommended action | Contact technical support to identify whether the app.json file exists and whether the specified file path is correct. |
Component installed successfully
Keyword | INSTALL_COMPONENT |
Message text | Installed component $1 successfully |
Variable fields | $1: Comma-separated list of component names. |
Severity level | Info |
Example | Installed component CAMPUS, VDHCP successfully |
Explanation | One or more components were installed successfully. |
Recommended action | No action is required. |
Component re-installed successfully
Keyword | REINSTALL_COMPONENT |
Message text | Reinstalled component $1 successfully |
Variable fields | $1: Comma-separated list of component names. |
Severity level | Info |
Example | Reinstalled component CAMPUS successfully |
Explanation | One or more components were re-installed successfully. |
Recommended action | No action is required. |
Component uninstalled successfully
Keyword | UNINSTALL_COMPONENT |
Message text | Uninstalled component $1 successfully |
Variable fields | $1: Comma-separated list of component names. |
Severity level | Info |
Example | Uninstalled component CAMPUS, VDHCP successfully |
Explanation | One or more components were uninstalled successfully. |
Recommended action | No action is required. |
Component re-uninstalled successfully
Keyword | REUNINSTALL_COMPONENT |
Message text | Re-uninstalled component $1 successfully |
Variable fields | $1: Component name. |
Severity level | Info |
Example | Re-uninstalled component CAMPUS successfully |
Explanation | A component was re-uninstalled successfully. |
Recommended action | No action is required. |
Component upgraded successfully
Keyword | UPDATE_COMPONENT |
Message text | Updated component $1 successfully |
Variable fields | $1: Component name. |
Severity level | Info |
Example | Updated component CAMPUS successfully |
Explanation | A component was upgraded successfully. |
Recommended action | No action is required. |
Component rolled back successfully
Keyword | ROLLBACK_COMPONENT |
Message text | Rollbacked component $1 successfully |
Variable fields | $1: Component name. |
Severity level | Info |
Example | Rollbacked component CAMPUS successfully |
Explanation | A component was rolled back to a previous version successfully. |
Recommended action | No action is required. |
Component installation stopped successfully
Keyword | STOP_INSTALL_COMPONENT |
Message text | Stopped installing component: $1 successfully |
Variable fields | $1: Component name. |
Severity level | Info |
Example | Stopped installing component CAMPUS successfully |
Explanation | The installation process of a component was stopped successfully. |
Recommended action | No action is required. |
Component uninstallation stopped successfully
Keyword | STOP_UNINSTALL_COMPONENT |
Message text | Stopped uninstalling component $1 successfully |
Variable fields | $1: Component name. |
Severity level | Info |
Example | Stopped uninstalling component CAMPUS successfully |
Explanation | The uninstallation process of a component was stopped successfully. |
Recommended action | No action is required. |