No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Fat AP and Cloud AP V200R008C00 CLI-based Configuration Guide

Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Configuring Information Center

Configuring Information Center

This section describes how to configure the information center.

Configuring Log Output

Pre-configuration Tasks

Logs of a specific module can be output to the log buffer, log file, console, terminal, or log host.

Before enabling log output, start the AP.

Configuration Process
Table 5-8 lists the configuration process for enabling log output.
Table 5-8  Configuration process for enabling log output
No. Configuration Task Description Remarks
1 Enabling the Information Center

You can configure the information center only after the information center is enabled.

By default, the information center is enabled.

Steps 2 to 4 are optional and can be performed in any sequence.

2 (Optional) Naming an Information Channel

You can easy-to-remember names for channels to facilitate information center usage.

3 (Optional) Configuring Log Filtering

If some logs are unnecessary, configure the AP not to output these logs.

4 (Optional) Setting the Timestamp Format of Logs

To adjust the time format and time precision for information output, configure the timestamp.

5 Configuring the Device to Output Logs to the Log Buffer

To view logs in the log buffer, configure the AP to output logs to the log buffer.

Steps 5 to 9 can be configured in any sequence. You can view logs in the log buffer, log file, console, terminal, or log host.

6 Configuring the Device to Output Logs to a Log File

After logs are output to a log file, you can download the log file anytime to monitor device running based on the logs.

7 Configuring the Device to Output Logs to the Console

After logs are output to the console, you can view logs on the console (host from which you can log in to the AP through the console interface) to monitor device running.

8 Configuring the Device to Output Logs to a Terminal

After logs are output to a user terminal, you can view logs on the user terminal (host from which you log in to the AP through STelnet) to monitor device running.

9 Configuring the Device to Output Logs to a Log Host

After configuring the AP to output logs to a log host, you can view logs saved on the log host to monitor device running.

Enabling the Information Center

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    info-center enable

    The information center is enabled.

    By default, the information center is enabled.

(Optional) Naming an Information Channel

Context

You can rename channels, which facilitates memorization and usage.

NOTE:

Channel names must be unique. It is recommended that channel names represent channel functions.

The following lists default channel names.

Table 5-9  Default channel names

Channel Number

Default Channel Name

0

console

1

monitor

2

loghost

3

trapbuffer

4

logbuffer

5

snmpagent

6

channel6

7

channel7

8

channel8

9

channel9

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    info-center channel channel-number name channel-name

    A name is configured for the information channel with the specified number.

(Optional) Configuring Log Filtering

Context

If some logs are unnecessary, configure the device not to output these logs. When the filtering function is enabled, the information center does not send the specified logs that satisfy the filtering condition to any channel. As a result, all output directions cannot receive the specified logs.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    info-center filter-id { id | bymodule-alias modname alias } * &<1-50>

    or

    The filtering function is configured for specified logs.

    NOTE:
    • Currently, the device can filter logs or modules with a maximum of 50 log IDs or modules. If there are more than 50 log IDs or modules, the system displays a message indicating that the filtering table is full. To configure the filtering function, run the undo info-center filter-id { all | { id | bymodule-alias modname alias } * &<1-50> } command to delete original IDs or modules, and reconfigure the log ID or module.

    • To add multiple IDs or modules at a time, use a space to separate IDs or modules. The system displays a message to report the result of adding each ID or module.

    • You cannot add the same ID or module repeatedly.

    • When you add an unregistered or nonexistent log ID or alias name, the system displays a message indicating that the system fails to filter the log with the specified log ID or alias name.

(Optional) Setting the Timestamp Format of Logs

Context

To adjust the time format and time precision for information output, configure the timestamp.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    info-center timestamp log { { date | short-date | format-date } [ precision-time { tenth-second | millisecond } ] | boot | none }

    The timestamp format of logs is configured.

    By default, the timestamp format of logs is date.

(Optional) Configuring the Suppression of the Log Processing Rate

Context

During the running of a device, if too many logs with the same log ID are generated, the information center is too busy processing these logs to process logs with other log IDs, which may even affect the running service. The information center monitors the traffic of logs with different log IDs. When the traffic of logs with a specific log ID repeatedly exceeds the threshold during the monitoring period, the information center suppresses the processing rate of these specified logs by processing only the conforming traffic and discarding the non-conforming traffic; when the traffic of logs with the specific log ID falls below the threshold and remains below the threshold for five monitoring periods, the suppression is removed.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    info-center rate-limit threshold value [ byinfoid infoID | bymodule-alias modname alias ]

    The maximum number of logs with the same log ID that the information center can process every second is set.

    By default, the information center processes a maximum of 30 logs with the same log ID in every second. In certain application scenarios, the default threshold may be higher than 50. You can set thresholds for logs with different log IDs.
    NOTE:
    • If the threshold is too low, some logs may be discarded.
    • If the threshold is too high, the information center cannot identify the log ID under which too many logs are generated.

  3. Run:

    info-center rate-limit global-threshold value

    The total number of logs that the information center can process each second is set.

  4. Run:

    info-center rate-limit monitor-period value

    The period for the information center to limit the log processing rate is set.

  5. Run:

    info-center rate-limit except { byinfoid infoID | bymodule-alias modname alias }

    (Optional) Cancel the log processing rate limit for logs with the specified ID or module name.

    If logs with the specified ID or module name will never be generated in a huge number, you can run this command to cancel the log processing rate limit for the logs. After this command is run, the configured log processing rate limit will not be effective for logs with the specified ID or module name.

(Optional) Enabling Suppression of Statistics About Consecutive Repeated Logs

Context

On the system, service modules generate logs and control the volume of generated logs. The information center processes the received logs.

In some scenarios, service modules, such as ARP and ACL, generate a large number of repeated logs within a short period. In this situation, you can enable suppression of statistics about consecutive repeated logs to protect the information center against the impact of a large number of repeated logs.
NOTE:

Logs that are generated consecutively and have identical log IDs and parameters can be regarded as repeated logs.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    info-center statistic-suppress enable

    Suppression of statistics about consecutive repeated logs is enabled.

    By default, suppression of statistics about consecutive repeated logs is enabled.

Configuring the Device to Output Logs to the Log Buffer

Context

To view logs in the log buffer, configure the device to output logs to the log buffer.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    info-center logbuffer

    The device is enabled to output information to the log buffer.

    By default, the device is enabled to output logs to the log buffer.

  3. Run:

    info-center logbuffer channel { channel-number | channel-name }

    The channel used by the device to output logs to the log buffer is specified.

    By default, the device uses channel 4 to output logs to the log buffer.

  4. Run:

    info-center source { module-name | default } channel { channel-number | channel-name } log { state { off | on } | level severity } *

    A rule for outputting logs to a channel is set.

    By default, channel 4 is enabled to output logs and the lowest log severity is warning.

  5. (Optional) Run:

    info-center logbuffer size logbuffer-size

    The maximum number of logs in the log buffer is set.

    By default, a log buffer can store a maximum of 512 logs.

Configuring the Device to Output Logs to a Log File

Context

After logs are output to a log file, you can view the log file anytime to monitor device running based on the logs.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    info-center logfile channel { channel-number | channel-name }

    A channel through which logs are output to a log file is specified.

    By default, the device uses channel 9 to output logs to a log file.

  3. Run:

    info-center source { module-name | default } channel { channel-number | channel-name } log { state { off | on } | level severity } *

    A rule for outputting logs to a channel is set.

    By default, channel 9 is enabled to output logs and the lowest log severity is debugging.

  4. (Optional) Run:

    info-center logfile path path

    The path where log files are saved is specified.

  5. (Optional) Run:

    info-center logfile size size

    The log file size is set.

    By default, the log file size is 8 MB.

    NOTE:
    • If the size of a log file generated on the device exceeds the configured log file size, the system decompresses the log file into a zip file.

    • You can run the save logfile command to save information to a log file.

    • When the remaining storage space of the device is smaller than the log file size, log information is saved in the log buffer to replace the existing logs but is not saved to the device's storage space. Beside, you will fail to run the save logfile command. In this case, you can configure log information to be saved on a log host. For details, see Configuring the Device to Output Logs to a Log Host.

  6. (Optional) Run:

    info-center max-logfile-number file numbers

    The maximum number of log files that can be saved is set.

    By default, the AD9430DN-12 and AD9431DN-24X allow a maximum of 10 log files to be saved, and other devices allow a maximum of 200 log files to be saved.

    If the number of log files generated on the AP exceeds the limit, the system deletes the oldest log file.

Configuring the Device to Output Logs to the Console

Context

After logs are output to the console, you can view logs on the console (host from which you can log in to the device through the console interface) to monitor device running.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    info-center console channel { channel-number | channel-name }

    A channel through which logs are output to the console is specified.

    By default, the device uses channel 0 to output logs to the console.

  3. Run:

    info-center source { module-name | default } channel { channel-number | channel-name } log { state { off | on } | level severity } *

    A rule for outputting logs to a channel is set.

    By default, channel 0 is enabled to output logs and the lowest log severity is warning.

  4. Run:

    quit

    Return to the user view.

  5. Run:

    terminal monitor

    Display of logs, traps, and debugging message output is enabled on the user terminal.

    By default, terminal display is disabled.

  6. Run:

    terminal logging

    Log display is enabled on the user terminal.

    By default, log display is enabled on the user terminal.

Configuring the Device to Output Logs to a Terminal

Context

After logs are output to a user terminal, you can view logs on the user terminal (host from which you log in to the device through Telnet) to monitor device running.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    info-center monitor channel { channel-number | channel-name }

    A channel through which logs are output to a user terminal is specified.

    By default, the AP uses channel 1 to output logs to a user terminal.

  3. Run:

    info-center source { module-name | default } channel { channel-number | channel-name } log { state { off | on } | level severity } *

    A rule for outputting logs to a channel is set.

    By default, channel 1 is enabled to output logs and the lowest log severity is warning.

  4. Run:

    quit

    Return to the user view.

  5. Run:

    terminal monitor

    Display of logs, traps, and debugging message output is enabled on the user terminal.

    By default, terminal display is disabled.

  6. Run:

    terminal logging

    Log display is enabled on the user terminal.

    By default, log display is enabled on the user terminal.

Configuring the Device to Output Logs to a Log Host

Context

After configuring the device to output logs to a log host, you can view logs saved on the log host to monitor device running.

Pre-configuration Tasks

There is a reachable route between the device and the log host.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Configure the device to output logs to the log host.

    • Run the info-center loghost ip-address [ channel { channel-number | channel-name } | facility local-number | { language language-name | binary [ port ] } | transport { udp | tcp ssl-policy policy-name } ] * command.

      The device is configured to output logs to the IPv4 log host.

    By default, the device does not output logs to a log host.

  3. Run:

    info-center source { module-name | default } channel { channel-number | channel-name } log { state { off | on } | level severity } *

    A rule for outputting logs to a channel is set.

    By default, channel 2 is enabled to output logs and the lowest log severity is informational.

  4. (Optional) Run:

    info-center loghost source interface-type interface-number

    The source interface used by the device to send logs to a log host is specified.

    By default, the source interface is the interface that sends logs.

    After the source interface is specified, the log host determines the device that sends messages. The log host then can easily retrieve received messages.

Checking the Configuration

Procedure

  • Run the display channel [ channel-number | channel-name ] command to view the channel configuration.
  • Run the display info-center filter-id [ id | bymodule-alias modname alias ] command to view information filtered by the information center.
  • Run the display info-center logfile path command to check the path where log files are saved.
  • Run the display logbuffer command to check logs recorded in the log buffer.
  • Run the display logfile file-name [ offset | hex ] * command to check the log file.

    NOTE:

    This command also allows you to check the user operation log operation.log.

Configuring Trap Output

Pre-configuration Tasks

Traps of a specific module can be output to the trap buffer, log file, console, terminal, log host, or SNMP agent.

Before enabling trap output, start the AP.

Starting the AP

Configuration Process
Table 5-10 lists the configuration process for enabling trap output.
Table 5-10  Configuration process for enabling trap output
No. Name Description Remarks
1 Enabling the Information Center

You can configure the information center only after the information center is enabled.

By default, the information center is enabled.

Steps 2 to 4 are optional and can be performed in any sequence.

2 (Optional) Naming an Information Channel

You can rename channels, which facilitates memorization and usage.

3 (Optional) Configuring Trap Filtering

If some traps are unnecessary, configure the AP not to output these traps.

4 (Optional) Setting the Timestamp Format of Traps

To adjust the time format and time precision for information output, configure the timestamp.

5 Configuring the Device to Output Traps to the Trap Buffer

To view traps in the trap buffer, configure the AP to output traps to the trap buffer.

Steps 5 to 10 can be configured in any sequence. You can configure the device to output traps to one or more destinations according to your needs.

6 Configuring the Device to Output Traps to a Log File

After traps are output to a log file, you can download the log file anytime to view traps generated by the AP to monitor device running.

7 Configuring the Device to Output Traps to the Console

After traps are output to the console, you can view traps on the console (host from which you can log in to the AP through the console interface) to monitor device running.

8 Configuring the Device to Output Traps to a Terminal

After traps are output to a user terminal, you can view traps on the user terminal (host from which you log in to the AP through STelnet) to monitor device running.

9 Configuring the Device to Output Traps to a Log Host

After configuring the AP to output traps to a log host, you can view traps saved on the log host to monitor device running.

10 Configuring the Device to Output Traps to an SNMP Agent

When an exception or a fault occurs on the AP, the network administrator wants to learn device running. You can configure the AP to output traps to an NMS server so that the network administrator can monitor the AP in real time and locate faults immediately. Before configuring the AP to output traps to an NMS server, configure the AP to output traps to an SNMP agent. Then the SNMP agent sends traps to the NMS server.

Enabling the Information Center

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    info-center enable

    The information center is enabled.

    By default, the information center is enabled.

(Optional) Naming an Information Channel

Context

You can rename channels, which facilitates memorization and usage.

NOTE:

Channel names must be unique. It is recommended that channel names represent channel functions.

The following lists default channel names.

Table 5-11  Default channel names

Channel Number

Default Channel Name

0

console

1

monitor

2

loghost

3

trapbuffer

4

logbuffer

5

snmpagent

6

channel6

7

channel7

8

channel8

9

channel9

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    info-center channel channel-number name channel-name

    A name is configured for the information channel with the specified number.

(Optional) Configuring Trap Filtering

Context

If some traps are unnecessary, configure the device not to output these traps. When the filtering function is enabled, the information center does not send the specified traps that satisfy the filtering condition to any channel. As a result, all output directions cannot receive the specified traps.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    info-center filter-id { id | bymodule-alias modname alias } * &<1-50>

    The filtering function is configured for specified traps.

    NOTE:
    • Currently, the device can filter logs or modules with a maximum of 50 log IDs or modules. If there are more than 50 log IDs or modules, the system displays a message indicating that the filtering table is full. To configure the filtering function, run the undo info-center filter-id { all | { id | bymodule-alias modname alias } * &<1-50> } command to delete original IDs or modules, and reconfigure the log ID or module.

    • To add multiple IDs or modules at a time, use a space to separate IDs or modules. The system displays a message to report the result of adding each ID or module.

    • You cannot add the same ID or module repeatedly.

    • When you add an unregistered or nonexistent ID or alias name, the system displays a message indicating that the system fails to filter the trap with the specified ID or alias name.

(Optional) Setting the Timestamp Format of Traps

Context

To adjust the time format and time precision for information output, configure the timestamp.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    info-center timestamp trap { { date | short-date | format-date } [ precision-time { tenth-second | millisecond } ] | boot | none }

    The timestamp format of traps is set.

    By default, the timestamp format of traps is date.

Configuring the Device to Output Traps to the Trap Buffer

Context

To view traps in the trap buffer, configure the device to output traps to the trap buffer.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    info-center trapbuffer

    The device is enabled to output traps to the trap buffer.

    By default, the device is enabled to output traps to the trap buffer.

  3. Run:

    info-center trapbuffer channel { channel-number | channel-name }

    The channel used by the device to output traps to the trap buffer is specified.

    By default, the device uses channel 3 to output traps to the trap buffer.

  4. Run:

    info-center source { module-name | default } channel { channel-number | channel-name } trap { state { off | on } | level severity } *

    A rule for outputting traps to a channel is set.

    By default, channel 3 is enabled to output traps and the lowest severity is debugging.

  5. (Optional) Run:

    info-center trapbuffer size trapbuffer-size

    The maximum number of traps in the trap buffer is set.

    By default, the trap buffer can store a maximum of 256 traps.

Configuring the Device to Output Traps to a Log File

Context

After traps are output to a log file, you can view the log file anytime to monitor device running based on the traps.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    info-center logfile channel { channel-number | channel-name }

    A channel through which traps are output to a log file is specified.

    By default, the device uses channel 9 to output traps to a log file.

  3. Run:

    info-center source { module-name | default } channel { channel-number | channel-name } trap { state { off | on } | level severity } *

    A rule for outputting traps to a channel is set.

    By default, channel 9 is enabled to output traps and the lowest severity is debugging.

  4. (Optional) Run:

    info-center logfile path path

    The path where log files are saved is specified.

  5. (Optional) Run:

    info-center logfile size size

    The log file size is set.

    By default, the log file size is 8 MB.

    NOTE:
    • If the size of a log file generated on the device exceeds the configured log file size, the system decompresses the log file into a zip file.

    • You can run the save logfile command to manually save traps in the log file buffer to a log file.

  6. (Optional) Run:

    info-center max-logfile-number file numbers

    The maximum number of log files that can be saved is set.

    By default, the AD9430DN-12 and AD9431DN-24X allow a maximum of 10 log files to be saved, and other devices allow a maximum of 200 log files to be saved.

    If the number of log files generated on the AP exceeds the limit, the system deletes the oldest log file.

Configuring the Device to Output Traps to the Console

Context

After traps are output to the console, you can view traps on the console (host from which you can log in to the device through the console interface) to monitor device running.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    info-center console channel { channel-number | channel-name }

    A channel through which traps are output to the console is specified.

    By default, the device uses channel 0 to output traps to the console.

  3. Run:

    info-center source { module-name | default } channel { channel-number | channel-name } trap { state { off | on } | level severity } *

    A rule for outputting traps to a channel is set.

    By default, channel 0 is enabled to output traps and the lowest severity is debugging.

  4. Run:

    quit

    Return to the user view.

  5. Run:

    terminal monitor

    Display of logs, traps, and debugging message output is enabled on the user terminal.

    By default, terminal display is disabled.

  6. Run:

    terminal trapping

    Traps display is enabled on the user terminal.

    By default, traps display is enabled on the user terminal.

Configuring the Device to Output Traps to a Terminal

Context

After traps are output to a user terminal, you can view traps on the user terminal (host from which you log in to the device through Telnet) to monitor device running.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    info-center monitor channel { channel-number | channel-name }

    A channel through which traps are output to a user terminal is specified.

    By default, the device uses channel 1 to output traps to a user terminal.

  3. Run:

    info-center source { module-name | default } channel { channel-number | channel-name } trap { state { off | on } | level severity } *

    A rule for outputting traps to a channel is set.

    By default, channel 1 is enabled to output traps and the lowest severity is debugging.

  4. Run:

    quit

    Return to the user view.

  5. Run:

    terminal monitor

    Display of logs, traps, and debugging message output is enabled on the user terminal.

    By default, terminal display is disabled.

  6. Run:

    terminal trapping

    Traps display is enabled on the user terminal.

    By default, traps display is enabled on the user terminal.

Configuring the Device to Output Traps to a Log Host

Context

After configuring the device to output traps to a log host, you can view traps saved on the log host to monitor device running.

Pre-configuration Tasks

There is a reachable route between the device and the log host.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Configure the device to output traps to the log host.

    • Run the info-center loghost ip-address [ channel { channel-number | channel-name } | facility local-number | { language language-name | binary [ port ] } | transport { udp | tcp ssl-policy policy-name } ] * command.

      The device is configured to output traps to the IPv4 log host.

    By default, the AP does not output traps to a log host.

  3. Run:

    info-center source { module-name | default } channel { channel-number | channel-name } trap { state { off | on } | level severity } *

    A rule for outputting traps to a channel is set.

    By default, channel 2 is enabled to output traps and the lowest severity is debugging.

  4. (Optional) Run:

    info-center loghost source interface-type interface-number

    The source interface used by the device to send logs to a log host is specified.

    By default, the source interface is the interface that sends logs.

    After the source interface is specified, the log host determines the device that sends messages. The log host then can easily retrieve received messages.

Configuring the Device to Output Traps to an SNMP Agent

Context

When an exception or a fault occurs on the device, the network administrator needs to learn the device running status. You can configure the device to output traps to an NMS server so that the network administrator can monitor the device in real time and locate faults immediately. Before configuring the device to output traps to an NMS server, configure the device to output traps to an SNMP agent. Then the SNMP agent sends traps to the NMS server.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    info-center snmp channel { channel-number | channel-name }

    The channel used by the device to output traps to an SNMP agent is specified.

    By default, the device uses channel 5 to output traps to an SNMP agent.

  3. Run:

    info-center source { module-name | default } channel { channel-number | channel-name } trap { state { off | on } | level severity } *

    A rule for outputting traps to a channel is set.

    By default, channel 5 is enabled to output traps and the lowest severity is debugging.

  4. Run:

    snmp-agent

    The SNMP agent function is enabled.

    By default, the SNMP agent function is disabled.

    The SNMP agent can work properly and receive traps only when the SNMP agent function is enabled.

    NOTE:

    For details on how to configure the SNMP agent, see SNMP Configuration.

Checking the Configuration

Procedure

  • Run the display channel [ channel-number | channel-name ] command to view the channel configuration.
  • Run the display info-center filter-id [ id | bymodule-alias modname alias ] command to view information filtered by the information center.
  • Run the display info-center logfile path command to check the path where log files are saved.
  • Run the display logfile file-name [ offset | hex ] * command to check the log file.

    NOTE:

    This command also allows you to check the user operation log operation.log.

  • Run the display trapbuffer [ size value ] command to check traps recorded in the trap buffer.

Configuring Debugging Message Output

Pre-configuration Tasks

Debugging messages of a specific module can be output to the log file, console, terminal, or log host.

Before enabling debugging message output, start the AP.

Starting the AP

Debugging occupies CPU resources on the device, affecting system running. After debugging, run the undo debugging all command to disable it immediately.

Configuration Process
Table 5-12 lists the configuration process for enabling debugging message output.
Table 5-12  Configuration process for enabling debugging message output
No. Configuration Task Description Remarks
1 Enabling the Information Center

You can configure the information center only after the information center is enabled.

By default, the information center is enabled.

Steps 2 and 3 are optional and can be performed in any sequence.

2 (Optional) Naming an Information Channel

You can easy-to-remember names for channels to facilitate information center usage.

3 (Optional) Setting the Timestamp Format of Debugging Messages

To adjust the time format and time precision for information output, configure the timestamp.

4 Configuring the Device to Output Debugging Messages to the Log File

After debugging messages are output to a log file, you can download the log file anytime to monitor device running based on debugging messages.

Steps 4 to 7 can be performed in any sequence. You can view debugging messages in the console or terminal.

5 Configuring the Device to Output Debugging Messages to the Console

After debugging messages are output to the console, you can view debugging messages on the console (host from which you can log in to the through the console interface) to monitor device running.

6 Configuring the Device to Output Debugging Messages to the Terminal

After debugging messages are output to a user terminal, you can view debugging messages on the user terminal (host from which you log in to the AP through STelnet) to monitor device running.

7 Configuring the Device to Output Debugging Messages to the Log Host

After configuring the AP to output debugging messages to a log host, you can view debugging messages saved on the log host to monitor device running.

Enabling the Information Center

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    info-center enable

    The information center is enabled.

    By default, the information center is enabled.

(Optional) Naming an Information Channel

Context

You can rename channels, which facilitates memorization and usage.

NOTE:

Channel names must be unique. It is recommended that channel names represent channel functions.

The following lists default channel names.

Table 5-13  Default channel names

Channel Number

Default Channel Name

0

console

1

monitor

2

loghost

3

trapbuffer

4

logbuffer

5

snmpagent

6

channel6

7

channel7

8

channel8

9

channel9

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    info-center channel channel-number name channel-name

    A name is configured for the information channel with the specified number.

(Optional) Setting the Timestamp Format of Debugging Messages

Context

To adjust the time format and time precision for information output, configure the timestamp.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    info-center timestamp debugging { { date | short-date | format-date } [ precision-time { tenth-second | second } ] | boot | none }

    The timestamp format of debugging messages is set.

    By default, the timestamp format of debugging messages is date.

Configuring the Device to Output Debugging Messages to the Log File

Context

After debugging messages are output to a log file, you can download the log file anytime to monitor device running based on debugging messages.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    info-center logfile channel { channel-number | channel-name }

    The channel used by the device to output debugging messages to a log file is specified.

    By default, the device uses channel 9 to output debugging messages into a log file.

  3. Run:

    info-center source { module-name | default } channel { channel-number | channel-name } debug { state { off | on } | level severity } *

    A rule for outputting debugging messages to a channel is set.

    By default, channel 9 is disabled to output debugging messages and the lowest severity is debugging.

  4. (Optional) Run:

    info-center logfile path path

    The path where log files are saved is specified.

  5. (Optional) Run:

    info-center logfile size size

    The log file size is set.

    By default, the log file size is 8 MB.

    NOTE:

    If the size of a log file generated on the device exceeds the configured log file size, the system decompresses the log file into a zip file.

  6. (Optional) Run:

    info-center max-logfile-number file numbers

    The maximum number of log files that can be saved is set.

    By default, the AD9430DN-12 and AD9431DN-24X allow a maximum of 10 log files to be saved, and other devices allow a maximum of 200 log files to be saved.

    If the number of log files generated on the AP exceeds the limit, the system deletes the oldest log file.

Configuring the Device to Output Debugging Messages to the Console

Context

After debugging messages are output to the console, you can view debugging messages on the console (host from which you can log in to the device through the console interface) to monitor device running.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    info-center console channel { channel-number | channel-name }

    A channel used by the device to output debugging messages to the console is specified.

    By default, the device uses channel 0 to output debugging messages to the console.

  3. Run:

    info-center source { module-name | default } channel { channel-number | channel-name } debug { state { off | on } | level severity } *

    A rule for outputting debugging messages to a channel is set.

    By default, channel 0 is enabled to output debugging messages and the lowest severity is debugging.

  4. Run:

    quit

    Return to the user view.

  5. Run:

    terminal monitor

    Display of logs, traps, and debugging message output is enabled on the user terminal.

    By default, terminal display is disabled.

  6. Run:

    terminal debugging

    Debugging message display is enabled on the user terminal.

    By default, debugging message display is disabled on the user terminal.

Configuring the Device to Output Debugging Messages to the Terminal

Context

After debugging messages are output to a user terminal, you can view debugging messages on the user terminal (host from which you log in to the device through STelnet) to monitor device running.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    info-center monitor channel { channel-number | channel-name }

    A channel used by the device to output debugging messages to a user terminal is specified.

    By default, the device uses channel 1 to output debugging messages to a user terminal.

  3. Run:

    info-center source { module-name | default } channel { channel-number | channel-name } debug { state { off | on } | level severity } *

    A rule for outputting debugging messages to a channel is set.

    By default, channel 1 is enabled to output debugging messages and the lowest severity is debugging.

  4. Run:

    quit

    Return to the user view.

  5. Run:

    terminal monitor

    Display of logs, traps, and debugging message output is enabled on the user terminal.

    By default, terminal display is disabled.

  6. Run:

    terminal debugging

    Debugging message display is enabled on the user terminal.

    By default, debugging message display is disabled on the user terminal.

Configuring the Device to Output Debugging Messages to the Log Host

Context

After configuring the device to output debugging messages to a log host, you can view debugging messages saved on the log host to monitor device running.

Prerequisites
  • There is a reachable route between the device and the log host.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Configure the device to output debugging messages to the log host.

    • Run the info-center loghost ip-address [ channel { channel-number | channel-name } | facility local-number | { language language-name | binary [ port ] } | transport { udp | tcp ssl-policy policy-name } ] * command.

      The device is configured to output debugging messages to the IPv4 log host.

    By default, the device does not output debugging messages to a log host.

  3. Run:

    info-center source { module-name | default } channel { channel-number | channel-name } debug { state { off | on } | level severity } *

    A rule for outputting debugging messages to a channel is set.

    By default, channel 2 is disabled to output debugging messages and the lowest severity is debugging.

  4. (Optional) Run:

    info-center loghost source interface-type interface-number

    The source interface used by the device to send logs to a log host is specified.

    By default, the source interface is the interface that sends logs.

    After the source interface is specified, the log host determines the device that sends messages. The log host then can easily retrieve received messages.

Checking the Configuration

Procedure

  • Run the display channel [ channel-number | channel-name ] command to view the channel configuration.
  • Run the display info-center filter-id [ id | bymodule-alias modname alias ] command to view information filtered by the information center.
  • Run the display info-center logfile path command to check the path where log files are saved.
  • Run the display logfile file-name [ offset | hex ] * command to check the log file.

    NOTE:

    This command also allows you to check the user operation log operation.log.

Translation
Download
Updated: 2019-01-11

Document ID: EDOC1000176006

Views: 116401

Downloads: 309

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next