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

CX11x, CX31x, CX710 (Earlier Than V6.03), and CX91x Series Switch Modules V100R001C10 Configuration Guide 12

The documents describe the configuration of various services supported by the CX11x&CX31x&CX91x series switch modules The description covers configuration examples and function configurations.
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

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

Pre-configuration Tasks

Before enabling log output, complete the following task:

Starting the Switch Module

Configuration Process
Table 3-7 lists the configuration process for enabling log output.
Table 3-7 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 6 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 Log Filtering

If some logs are unnecessary, configure the device 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 (Optional) Setting the Severity of Logs

The system defines the default severity for each log. You can change the severity of a log according to severity level and urgency.

6 (Optional) Enabling Suppression of Statistics About Consecutive Repeated Logs

You can enable duplicate log statistics suppression to protect the information center against the impact of a large number of logs.

7 Configuring the Device to Output Logs to the Log Buffer

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

Steps 7 to 11 can be configured in any sequence. You can configure the device to output logs to one or more destinations according to your needs.

8 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.

9 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 device through the console interface) to monitor device running.

10 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 device through STelnet) to monitor device running.

11 Configuring the Device to Output Logs to a Log Host

After configuring the device 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.

  3. Run:

    commit

    The configuration is committed.

(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 3-8 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.

  3. Run:

    commit

    The configuration is committed.

(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 }

    The filtering function is configured for specified logs.

  3. Run:

    commit

    The configuration is committed.

(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 | format-date | short-date } [ precision-time { second | tenth-second | millisecond } ] | boot | none }

    The timestamp format of logs is configured.

    By default, the timestamp format of logs is date.

  3. Run:

    commit

    The configuration is committed.

(Optional) Setting the Severity of Logs

Context

The system defines the default severity for each log. You can change the severity of a log according to severity level and urgency.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    info-center log-severity bymodule-alias module-name log-name severity severity

    The severity of logs is set.

  3. Run:

    commit

    The configuration is committed.

(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, VRRP, 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.

  3. Run:

    commit

    The configuration is committed.

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 } [ size logbuffer-size ]

    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 [ channel { channel-number | channel-name } ]

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

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

  6. Run:

    commit

    The configuration is committed.

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

  5. (Optional) Run:

    info-center max-logfile-number filenumbers

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

    By default, a maximum of 200 log files can be saved.

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

  6. Run:

    commit

    The configuration is committed.

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:

    commit

    The configuration is committed.

  5. Run:

    quit

    Return to the user view.

  6. Run:

    terminal monitor

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

    By default, terminal display is enabled.

  7. Run:

    terminal logging

    Log display is enabled on the user terminal.

    By default, log display is disabled 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 Switch Module 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:

    commit

    The configuration is committed.

  5. Run:

    quit

    Return to the user view.

  6. Run:

    terminal monitor

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

    By default, terminal display is enabled.

  7. Run:

    terminal logging

    Log display is enabled on the user terminal.

    By default, log display is disabled 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.

NOTE:

The device can use the SSL protocol to encrypt the logs sent to the log host. It is recommended that you use this log transmission mode to enhance security.

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. Run the following command as required.

    • Run:

      info-center loghost ip-address [ channel { channel-number | channel-name } | { public-net | vpn-instance vpn-insname } | facility local-number | port port-number | level info-level | { local-time | utc } | transport { udp | tcp [ ssl-policy policy-name ] } ] *

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

    • Run:

      info-center loghost ipv6 ipv6-address [ channel { channel-number | channel-name } | facility local-number | port port-number | level info-level | { local-time | utc } | transport { udp | tcp [ ssl-policy policy-name ] } ] *

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

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

    The device can output logs to eight log hosts (IPv4 and IPv6 hosts) to implement backup among log hosts.

  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 messages to a log host is specified.

    By default, the source interface for a device to send messages to a log host is the actual interface that sends the messages.

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

  5. Run:

    commit

    The configuration is committed.

Checking the Configuration

Procedure

  • Run the display info-center channel [ channel-number | channel-name ] command to view the channel configuration.
  • Run the display logbuffer command to check logs recorded in the log buffer.
  • Run the display logfile file-name [ offset ] command to check the log file.

Configuring Trap Output

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

Pre-configuration Tasks

Before enabling trap output, complete the following task:

Starting the Switch Module

Configuration Process
Table 3-9 lists the configuration process for enabling trap output.
Table 3-9 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 Switch Module 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 Switch Module 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 Switch Module 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 Switch Module 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 Switch Module through STelnet) to monitor device running.

9 Configuring the Device to Output Traps to a Log Host

After configuring the Switch Module 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 Switch Module, the network administrator wants to learn device running. You can configure the Switch Module to output traps to an NMS server so that the network administrator can monitor the Switch Module in real time and locate faults immediately. Before configuring the Switch Module to output traps to an NMS server, configure the Switch Module 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.

  3. Run:

    commit

    The configuration is committed.

(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 3-10 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.

  3. Run:

    commit

    The configuration is committed.

(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 }

    The filtering function is configured for specified traps.

  3. Run:

    commit

    The configuration is committed.

(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 | format-date | short-date } [ precision-time { second | tenth-second | millisecond } ] | boot | none }

    The timestamp format of traps is set.

    By default, the timestamp format of traps is date.

  3. Run:

    commit

    The configuration is committed.

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 } [ size trapbuffer-size ]

    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 [ channel { channel-number | channel-name } ]

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

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

  6. Run:

    commit

    The configuration is committed.

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

  5. (Optional) Run:

    info-center max-logfile-number filenumbers

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

    By default, a maximum of 200 log files can be saved.

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

  6. Run:

    commit

    The configuration is committed.

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:

    commit

    The configuration is committed.

  5. Run:

    quit

    Return to the user view.

  6. Run:

    terminal monitor

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

    By default, terminal display is enabled.

  7. Run:

    terminal trapping

    Traps display is enabled on the user terminal.

    By default, traps display is disabled 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:

    commit

    The configuration is committed.

  5. Run:

    quit

    Return to the user view.

  6. Run:

    terminal monitor

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

    By default, terminal display is enabled.

  7. Run:

    terminal trapping

    Traps display is enabled on the user terminal.

    By default, traps display is disabled 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.

NOTE:

The device can use the SSL protocol to encrypt the traps sent to the log host. It is recommended that you use this log transmission mode to enhance security.

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. Run the following command as required.

    • Run:

      info-center loghost ip-address [ channel { channel-number | channel-name } | { public-net | vpn-instance vpn-insname } | facility local-number | port port-number | level info-level | { local-time | utc } | transport { udp | tcp [ ssl-policy policy-name ] } ] *

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

    • Run:

      info-center loghost ipv6 ipv6-address [ channel { channel-number | channel-name } | facility local-number | port port-number | level info-level | { local-time | utc } | transport { udp | tcp [ ssl-policy policy-name ] } ] *

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

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

    The device can output traps to eight log hosts (IPv4 and IPv6 hosts) to implement backup among log hosts.

  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 messages to a log host is specified.

    By default, the source interface for a device to send messages to a log host is the actual interface that sends the messages.

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

  5. Run:

    commit

    The configuration is committed.

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 in the CX11x&CX31x&CX91x Series Switch Modules Configuration Guide - Network Management.

  5. Run:

    commit

    The configuration is committed.

Checking the Configuration

Procedure

  • Run the display info-center channel [ channel-number | channel-name ] command to view the channel configuration.
  • Run the display logfile file-name [ offset ] command to check the log file.
  • Run the display trapbuffer [ size value ] command to check traps recorded in the trap buffer.

Configuring Debugging Message Output

Debugging messages of a specific module can be output to the console and terminal.

Pre-configuration Tasks

Before enabling debugging message output, complete the following task:

Starting the Switch Module

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 3-11 lists the configuration process for enabling debugging message output.
Table 3-11 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 rename channels, which facilitates memorization and 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 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.

Steps 4 to 5 can be performed in any sequence. You can configure the device to output debugging messages to one or more destinations according to your needs.

5

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 Switch Module through STelnet) 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.

  3. Run:

    commit

    The configuration is committed.

(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 3-12 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.

  3. Run:

    commit

    The configuration is committed.

(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 | format-date | short-date } [ precision-time { second | tenth-second | millisecond } ] | boot | none }

    The timestamp format of debugging messages is set.

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

  3. Run:

    commit

    The configuration is committed.

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:

    commit

    The configuration is committed.

  5. Run:

    quit

    Return to the user view.

  6. Run:

    terminal monitor

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

    By default, terminal display is enabled.

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

    commit

    The configuration is committed.

  5. Run:

    quit

    Return to the user view.

  6. Run:

    terminal monitor

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

    By default, terminal display is enabled.

  7. Run:

    terminal debugging

    Debugging message display is enabled on the user terminal.

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

Checking the Configuration

Procedure

  • Run the display info-center channel [ channel-number | channel-name ] command to view the channel configuration.
Translation
Download
Updated: 2019-08-09

Document ID: EDOC1000041694

Views: 59718

Downloads: 3623

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