Device management 1

Device management overview·· 1

Configuring the device name· 1

Configuring the system time· 2

Configuration procedure· 2

System time configuration examples 2

Enabling the display of copyright information· 5

Configuring banners 5

Introduction to banners 5

Configuring banners 6

Configuring the exception handling method· 7

Rebooting the device· 7

Configuring a scheduled task· 8

What is a scheduled task· 8

Configuration approaches 9

Scheduled task configuration example· 9

Configuring the detection timer 11

Configuring temperature thresholds for a card· 11

Clearing unused 16-bit interface indexes 12

Identifying and diagnosing pluggable transceivers 12

Introduction to pluggable transceivers 12

Identifying pluggable transceivers 13

Diagnosing pluggable transceivers 13

Displaying and maintaining device management configuration· 14

 

This chapter includes these sections:

·          Device management overview

·          Configuring the device name

·          Configuring the system time

·          Enabling the display of copyright information

·          Configuring banners

·          Configuring the exception handling method

·          Rebooting the device

·          Configuring a scheduled task

·          Configuring the detection timer

·          Configuring temperature thresholds for a card

·          Clearing unused 16-bit interface indexes

·          Identifying and diagnosing pluggable transceivers

·          Displaying and maintaining device management configuration

 

NOTE: ·      The term "switch" or "device" in this chapter refers to the switching engine on a WX3000E wireless switch. ·      The WX3000E series comprises WX3024E and WX3010E wireless switches. ·      The port numbers in this chapter are for illustration only. ·      The configuration tasks in this chapter are all optional and independent from one another.

 

Device management overview

Device management functions enable you to check the operating status and configure the running parameters of devices.

Configuring the device name

A device name identifies a device in a network. If the device name is Sysname, the prompt of user view is <Sysname>.

Follow these steps to configure the device name:

To do…	Use the command…	Remarks
Enter system view	system-view	—
Configure the device name	sysname sysname	Optional By default, the device name is H3C.

 

Configuring the system time

Configuration procedure

The system time is determined by the configured relative time, time zone, and daylight saving time. To view the system time, use the display clock command.

Follow these steps to configure the system time:

To do…		Use the command…	Remarks
Set the time and date		clock datetime time date	Optional Available in user view.
Enter system view		system-view	—
Set the time zone		clock timezone zone-name { add | minus } zone-offset	Optional Universal time coordinated (UTC) time zone by default.
Set a daylight saving time scheme	Adopt daylight saving time from the start-time on the start-date to the end-time on the end-date in this year. Daylight saving time is the standard time plus the add-time.	clock summer-time zone-name one-off start-time start-date end-time end-date add-time	Optional Use either command By default, daylight saving time is not configured on the device, and the UTC time zone is applied.
	Adopt daylight saving time every year	clock summer-time zone-name repeating start-time start-date end-time end-date add-time

 

System time configuration examples

The system time is determined by the commands clock datetime, clock timezone and clock summer-time. If these three commands are not configured, the display clock command displays the original system time. If you combine these three commands in different ways, the system time is displayed in the ways as shown in Table 1. The numbers in the configuration column are described below:

·          1 indicates that the date-time has been configured with the clock datetime command.

·          2 indicates that the time-zone has been configured with the clock timezone command and the offset time is zone-offset.

·          3 indicates that the daylight saving time has been configured with the clock summer-time command and the offset time is summer-offset.

·          [1] indicates that the clock datetime command is optional.

·          The default system time is 2005/1/1 1:00:00 in the example.

Table 1 System time configuration

Configuration	System time configured	Example
1	date-time	Configure: clock datetime 1:00 2007/1/1 System time configured: 01:00:00 UTC Mon 01/01/2007
2	The original system time ± “zone-offset”	Configure: clock timezone zone-time add 1 System time configured: 02:00:00 zone-time Sat 01/01/2005
1 and 2	date-time ± zone-offset	Configure: clock datetime 2:00 2007/2/2 and clock timezone zone-time add 1 System time configured: 03:00:00 zone-time Fri 02/02/2007
[1], 2 and 1	date-time	Configure: clock timezone zone-time add 1 and clock datetime 3:00 2007/3/3 System time configured: 03:00:00 zone-time Sat 03/03/2007
3	If the original system time is not in the daylight saving time range, the system time configured is the original system time.	Configure: clock summer-time ss one-off 1:00 2006/1/1 1:00 2006/8/8 2 System time configured: 01:00:00 UTC Sat 01/01/2005
	If the original system time is in the daylight saving time range, the system time configured is the original system time + “summer-offset”.	Configure: clock summer-time ss one-off 00:30 2005/1/1 1:00 2005/8/8 2 System time configured: 03:00:00 ss Sat 01/01/2005
1 and 3	If “date-time” is not in the daylight saving time range, the system time configured is “date-time”.	Configure: clock datetime 1:00 2007/1/1 and clock summer-time ss one-off 1:00 2006/1/1 1:00 2006/8/8 2 System time configured: 01:00:00 UTC Mon 01/01/2007
	If “date-time” is in the daylight saving time range, the system time configured is “date-time” + “summer-offset”.	Configure: clock datetime 8:00 2007/1/1 and clock summer-time ss one-off 1:00 2007/1/1 1:00 2007/8/8 2 System time configured: 10:00:00 ss Mon 01/01/2007
[1], 3 and 1	If “date-time” is not in the daylight saving time range, the system time configured is “date-time”.	Configure: clock summer-time ss one-off 1:00 2007/1/1 1:00 2007/8/8 2 and clock datetime 1:00 2008/1/1 System time configured: 01:00:00 UTC Tue 01/01/2008
	“date-time” is in the daylight saving time range: If the value of “date-time” - “summer-offset” is not in the summer-time range, the system time configured is “date-time” - “summer-offset”; If the value of “date-time” - “summer-offset” is in the summer-time range, the system time configured is “date-time”.	Configure: clock summer-time ss one-off 1:00 2007/1/1 1:00 2007/8/8 2 and clock datetime 1:30 2007/1/1 System time configured: 23:30:00 UTC Sun 12/31/2006
		Configure: clock summer-time ss one-off 1:00 2007/1/1 1:00 2007/8/8 2 and clock datetime 3:00 2007/1/1 System time configured: 03:00:00 ss Mon 01/01/2007
2 and 3 or 3 and 2	If the value of the original system time ± “zone-offset” is not in the summer-time range, the system time configured is the original system time ± “zone-offset”.	Configure: clock timezone zone-time add 1 and clock summer-time ss one-off 1:00 2007/1/1 1:00 2007/8/8 2 System time configured: 02:00:00 zone-time Sat 01/01/2005
	If the value of the original system time ± “zone-offset” is in the summer-time range, the system time configured is the original system time ± “zone-offset” + ”summer-offset”.	Configure: clock timezone zone-time add 1 and clock summer-time ss one-off 1:00 2005/1/1 1:00 2005/8/8 2 System time configured: 04:00:00 ss Sat 01/01/2005
1, 2 and 3 or 1, 3 and 2	If the value of "date-time"±"zone-offset" is not in the summer-time range, the system time configured is "date-time"±"zone-offset".	Configure: clock datetime 1:00 2007/1/1, clock timezone zone-time add 1 and clock summer-time ss one-off 1:00 2008/1/1 1:00 2008/8/8 2 System time configured: 02:00:00 zone-time Mon 01/01/2007
	If the value of "date-time"±"zone-offset" is in the summer-time range, the system time configured is "date-time"±"zone-offset"+”summer-offset”.	Configure: clock datetime 1:00 2007/1/1, clock timezone zone-time add 1 and clock summer-time ss one-off 1:00 2007/1/1 1:00 2007/8/8 2 System time configured: 04:00:00 ss Mon 01/01/2007
[1], 2, 3 and 1 or [1], 3, 2 and 1	If “date-time” is not in the daylight saving time range, the system time configured is “date-time”.	Configure: clock timezone zone-time add 1, clock summer-time ss one-off 1:00 2008/1/1 1:00 2008/8/8 2 and clock datetime 1:00 2007/1/1 System time configured: 01:00:00 zone-time Mon 01/01/2007
	“date-time” is in the daylight saving time range: If the value of “date-time”-“summer-offset” is not in the summer-time range, the system time configured is “date-time”-“summer-offset”; If the value of “date-time”-“summer-offset” is in the summer-time range, the system time configured is “date-time”.	Configure: clock timezone zone-time add 1, clock summer-time ss one-off 1:00 2008/1/1 1:00 2008/8/8 2 and clock datetime 1:30 2008/1/1 System time configured: 23:30:00 zone-time Mon 12/31/2007
		Configure: clock timezone zone-time add 1, clock summer-time ss one-off 1:00 2008/1/1 1:00 2008/8/8 2 and clock datetime 3:00 2008/1/1 System time configured: 03:00:00 ss Tue 01/01/2008

 

Enabling the display of copyright information

·          When the display of copyright information is enabled, the copyright information appears when a user logs in through Telnet or SSH, or when a user quits user view after logging in to the device through OAP. The copyright information is displayed in the following format:

******************************************************************************

* Copyright (c) 2004-2011 Hangzhou H3C Tech. Co., Ltd. All rights reserved.  *

* Without the owner's prior written consent,                                 *

* no decompiling or reverse-engineering shall be allowed.                    *

******************************************************************************

·          When the display of copyright information is disabled, the copyright information never appears.

Follow these steps to enable the display of copyright information:

To do…	Use the command…	Remarks
Enter system view	system-view	—
Enable the display of copyright information	copyright-info enable	Optional Enabled by default.

 

Configuring banners

Introduction to banners

Banners are prompt information that the system displays when users are connected to the device, perform login authentication, and start interactive configuration. The administrator can set banners as needed.

At present, the system supports the following types of banners.

·          shell banner—Also called session banner, displayed when a non TTY Modem user enters user view.

·          incoming banner—Also called user interface banner, displayed when a user interface is activated by a Modem user.

·          login banner—Login welcome information, displayed when password or scheme authentication is configured.

·          motd (Message of the Day) banner—Welcome information displayed before authentication.

·          legal banner—Also called license information, displayed when a user logs in. If entering Y or pressing the Enter key, the user enters the authentication or login process. If entering N, the user quits the authentication or login process. Y and N are case insensitive.

Configuring banners

Follow these steps to configure banners:

To do…	Use the command…	Remarks
Enter system view	system-view	—
Configure the incoming banner (for Modem login users)	header incoming text	Optional
Configure the login banner	header login text	Optional
Configure the legal banner	header legal text	Optional
Configure the shell banner (for non Modem login users)	header shell text	Optional
Configure the motd banner	header motd text	Optional

 

The system supports single-line input and multiple-line input for configuring a banner.

Single-line input

In single-line input mode, all banner information is input in the same line. The start and end characters of the input text must be the same and are not part of the banner information. The input text, together with the command keywords, cannot exceed 510 characters. In this mode, do not press Enter after typing the banner information. For example, to configure a banner like “Have a nice day.”, use the following command:

<System> system-view

[System] header shell %Have a nice day.%

Multiple-line input

In multiple-line input mode, you can press Enter to separate the banner information in multiple lines. In this case, up to 2000 characters can be typed.

Multi-line input can be performed with the following methods:

·          Method I—Press the Enter key directly after the command keywords, type the banner information, and finish your setting with the % character. The % character is not part of the banner information. For example, to configure a banner like “Have a nice day. Please input the Password!”, use the following commands:

<System> system-view

[System] header shell

Please input banner content, and quit with the character '%'.――System prompt

Have a nice day.

Please input the Password!%

·          Method II—Type a character after the command keywords at the first line, and then press Enter. Type the banner information, and finish your setting with the character you typed at the first line. The start character and the end character are not part of the banner information. For example, to configure a banner like “Have a nice day. Please input the Password!”, use the following commands:

<System> system-view

[System] header shell A

Please input banner content, and quit with the character 'A'.――System prompt

Have a nice day.

Please input the Password!A

·          Method III—Type multiple characters after the command keywords at the first line (with the first and last characters being different), and then press Enter. Type the rest banner information, and finish your setting with the first character you typed at the first line. The first input character at the first line and the end character are not part of the banner information. For example, to configure a banner like “Have a nice day. Please input the Password!”, use the following commands:

<System> system-view

[System] header shell AHave a nice day.

Please input banner content, and quit with the character 'A'.――System prompt

Please input the Password!A

Configuring the exception handling method

You can configure the device to handle software exceptions with either of the following methods:

·          reboot—The system reboots to remove exceptions.

·          maintain—The system stays in the current state. You need to manually recover the system, such as rebooting the system. Sometimes, it is difficult to make a system problem reoccur, or the prompts output during the failure are lost after a reboot. You can use this method to keep the abnormal state and troubleshoot the problem.

Follow these steps to configure the exception handling method:

To do…	Use the command…	Remarks
Enter system view	system-view	—
Configure the exception handling method	system-failure { maintain | reboot }	Optional By default, the system adopts the reboot method to handle exceptions.

 

Rebooting the device

When a fault occurs to a running device, you can remove the fault by rebooting the device with one of the following methods:

·          Power off and then power on the device. This method is also called “hard reboot” or “cold start”.  It will cause data loss and hardware damage. H3C does not recommend this method.

·          Reboot the device at the CLI immediately.

·          Reboot the device at a specified time at the CLI. You can set a time at which the device will automatically reboot, or set a delay so that the device will automatically reboot after the delay.

The last two methods are also called hot start, which is mainly used to reboot a device remotely.

Follow the step to immediately reboot the device at the CLI:

To do…	Use the command…	Remarks
Reboot the device immediately	reboot [ slot slot-number ]	Required Available in user view

 

Follow these steps to reboot the device at a time at the CLI:

To do…	Use the command…	Remarks
Reboot the device at a specified time	schedule reboot at hh:mm [ date ]	Required Use either approach. Not configured by default. Available in user view.
Reboot the device after a delay	schedule reboot delay { hh:mm | mm }

 

CAUTION: ·      A device reboot interrupts ongoing services. Use these commands with caution. ·      Before rebooting a device, use the save command to save the current configurations. For more information about the save command, see the Fundamentals Command Reference. ·      Before rebooting a device, use the display startup command to check whether the configuration file to be used at the next boot are configured. For more information about the display startup command, see the Fundamentals Command Reference. ·      The precision of the reboot timer is 1 minute. One minute before the specified reboot time, the device prompts “REBOOT IN ONE MINUTE” and reboots after one minute. ·      If the main boot file fails or does not exist, the device cannot be rebooted with the reboot command. In this case, you can re-specify a main boot file to reboot the device, or you can power off the device then power it on and the system automatically uses the backup boot file to restart the device. ·      If you are performing file operations when the reboot time is reached, the system does not execute the reboot operation for security.

 

Configuring a scheduled task

What is a scheduled task

A scheduled task executes specified commands at a specified time. This feature enables automated operations and improves usability.

With a scheduled task configured, the device checks the configured task list every minute. If the device finds that the time to execute a command is reached, it automatically executes the command.

Configuration approaches

 

NOTE: ·      Only one view can be specified for a task, which means all commands in the task are executed in the same specified view. If different views are specified by executing the view view-name command repeatedly, only the last configuration takes effect. ·      The view must be supported by the system, and the view name must be complete instead of an abbreviation. Most commonly used view names include: monitor for user view, system for system view, GigabitEthernetx/x/x for Ethernet interface view, and Vlan-interfacex for VLAN interface view. ·      A scheduled task can contain up to 10 commands. If you want more than 10 commands to be executed, configure them in different tasks. ·      The system does not check whether input view and command arguments are correct. You must ensure their correctness. Otherwise, the specified commands in the scheduled task cannot be executed.

 

Configuring a scheduled task

Follow these steps to configure a scheduled task:

To do…	Use the command…	Remarks
Enter system view	system-view	—
Create a scheduled task and enter job view	job job-name	Required
Specify the view in which the task is executed	view view-name	Required You can specify only one view for a task.
Configure a command to be executed at a specific time	time time-id at time date command command	Required Use any of the commands. ·      If you use the time at command, changing the system time will change the execution time of the scheduled task. ·      If you use the time delay command, changing the system time will not change the execution time of the scheduled task.
	time time-id { one-off | repeating } at time [ month-date month-day | week-day week-daylist ] command command
Configure a command to be executed after a delay time	time time-id { one-off | repeating } delay time command command

 

Scheduled task configuration example

Network requirements

Configure scheduled tasks on the device to enable interfaces GigabitEthernet 1/0/1, GigabitEthernet 1/0/2, and GigabitEthernet 1/0/3 at 8:00 and disabled them at 18:00 on working days every week, to control the access of the PCs connected to these interfaces.

Configuration procedure

# Enter system view.

<Sysname> system-view

# Create scheduled task pc1, and enter its view.

[Sysname] job pc1

# Configure the task to be executed in the view of GigabitEthernet 1/0/1.

[Sysname-job-pc1] view gigbaitethernet 1/0/1

# Configure the device to start Ethernet 1/1 at 8:00 on working days every week.

[Sysname-job-pc1] time 1 repeating at 8:00 week-day mon tue wed thu fri command undo shutdown

# Configure the device to shut down GigabitEthernet 1/0/1 at 18:00 on working days every week.

[Sysname-job-pc1] time 2 repeating at 18:00 week-day mon tue wed thu fri command shutdown

[Sysname-job-pc1] quit

# Create scheduled task pc2, and enter its view.

[Sysname] job pc2

# Configure the task to be executed in the view of GigabitEthernet 1/0/2.

[Sysname-job-pc2] view gigabitethernet 1/0/2

# Configure the device to start GigabitEthernet 1/0/2 at 8:00 on working days every week.

[Sysname-job-pc2] time 1 repeating at 8:00 week-day mon tue wed thu fri command undo shutdown

# Configure the device to shut down GigabitEthernet 1/0/2 at 18:00 on working days every week.

[Sysname-job-pc2] time 2 repeating at 18:00 week-day mon tue wed thu fri command shutdown

[Sysname-job-pc2] quit

# Create scheduled task pc3, and enter its view.

[Sysname] job pc3

# Configure the task to be executed in the view of GigabitEthernet 1/0/3.

[Sysname-job-pc3] view gigabitethernet 1/0/3

# Configure the device to start GigabitEthernet 1/0/3 at 8:00 on working days every week.

[Sysname-job-pc3] time 1 repeating at 8:00 week-day mon tue wed thu fri command undo shutdown

# Configure the device to shut down GigabitEthernet 1/0/3 at 18:00 on working days every week.

[Sysname-job-pc3] time 2 repeating at 18:00 week-day mon tue wed thu fri command shutdown

[Sysname-job-pc3] quit

# Display information about scheduled tasks.

[Sysname] display job

Job name: pc1

  Specified view: GigabitEthernet1/0/1

  Time 1: Execute command undo shutdown at 08:00 Mondays Tuesdays Wednesdays Thursdays Fridays

  Time 2: Execute command shutdown at 18:00 Mondays Tuesdays Wednesdays Thursdays Fridays

Job name: pc2

  Specified view: GigabitEthernet1/0/2

  Time 1: Execute command undo shutdown at 08:00 Mondays Tuesdays Wednesdays Thursdays Fridays

  Time 2: Execute command shutdown at 18:00 Mondays Tuesdays Wednesdays Thursdays Fridays

Job name: pc3

  Specified view: GigabitEthernet1/0/3

  Time 1: Execute command undo shutdown at 08:00 Mondays Tuesdays Wednesdays Thursdays Fridays

  Time 2: Execute command shutdown at 18:00 Mondays Tuesdays Wednesdays Thursdays Fridays

Configuring the detection timer

Some protocols might shut down ports under specific circumstances. For example, MSTP shuts down a BPDU guard enabled port when the port receives a BPDU. Then, the device starts the detection timer. If the port is not up before the detection timer times out, the device automatically brings up the port.

Follow these steps to configure the detection timer:

To do…	Use the command…	Remarks
Enter system view	system-view	—
Configure the detection timer	shutdown-interval time	Optional The detection interval is 30 seconds by default.

 

Configuring temperature thresholds for a card

You can set temperature thresholds by using the following commands. When the temperature of a card reaches a threshold, the device generates alarms.

You can set low temperature threshold, warning temperature threshold, and alarming temperature threshold.

·          If the temperature is lower than the low temperature threshold, the device logs the event and outputs log and trap information.

·          If the temperature reaches the warning threshold, the device logs the event and outputs log and trap information.

·          If the temperature reaches the alarming threshold, the device not only repeatedly outputs log and trap information in the terminal display, but also alerts users through the LED on the device panel.

Follow these steps to configure temperature thresholds for a card:

To do…	Use the command…	Remarks
Enter system view	system-view	—
Configure temperature alarm thresholds for a card	temperature-limit slot slot-number hotspot sensor-number lowerlimit warninglimit [ alarmlimit ]	Optional By default, the warning threshold is 82°C (179.6°F), and the alarming threshold is 92°C (197.6°F).. The warning and alarming thresholds must be higher than the low temperature threshold. The alarming threshold must be higher than the warning threshold.

 

Clearing unused 16-bit interface indexes

The network management software requires devices to provide uniform and stable 16-bit interface indexes. That is, a one-to-one relationship should be kept between an interface’s name and the interface’s index on the same device.

For this purpose, the system will save the 16-bit index for an interface after the logical interface is removed.

If you create and delete a large number of logical interfaces of different types, the interface indexes will be used up, and new interfaces cannot be created. To solve this problem, you can clear all unused 16-bit interface indexe in user view.

After the clearing operation,

·          A re-created interface’s index might not be consistent with the original index.

·          Existing interfaces’ indexes remain unchanged.

Follow these steps to clear unused 16-bit interface indexes:

To do…	Use the command…	Remarks
Clear unused 16-bit interface indexes	reset unused porttag	Required Available in user view.

 

CAUTION: A confirmation is required when you execute this command. If you fail to make a confirmation within 30 seconds or enter N to cancel the operation, the command will not be executed.

 

Identifying and diagnosing pluggable transceivers

Introduction to pluggable transceivers

Table 2 lists the commonly used pluggable transceivers that the WX3000E series wireless switches support:

Table 2 Commonly used pluggable transceivers

Transceiver type	Application environment	Whether can be an optical transceiver		Whether can be an electrical transceiver
SFP (Small Form-factor Pluggable)	Generally used for 1000M Ethernet interfaces		Yes		Yes
XFP (10-Gigabit small Form-factor Pluggable)	Generally used for 10G Ethernet interfaces		Yes		No

 

Identifying pluggable transceivers

Pluggable transceivers are of various types and from different vendors. You can use the following commands to view the key parameters of the pluggable transceivers, including transceiver type, connector type, laser central wavelength, transmission distance and vendor name.

Follow these steps to identify pluggable transceivers:

To do…	Use the command…	Remarks
Display key parameters of the pluggable transceivers	display transceiver interface [ interface-type interface-number ] [ | { begin | exclude | include } regular-expression ]	Available for all pluggable transceivers.
Display part of the electrical label information of the anti-spoofing transceivers customized by H3C	display transceiver manuinfo interface [ interface-type interface-number ] [ | { begin | exclude | include } regular-expression ]	Available for anti-spoofing pluggable transceivers customized by H3C only.

 

·          A vendor name of H3C indicates an H3C-customized anti-spoofing transceiver. Use the display transceiver command to verify it.

·          Electrical label information is also called permanent configuration data or archive information, which is written to the storage component of a card during device testing. The information includes name of the card, device serial number, and vendor name or name of the vendor who customizes the transceiver.

Diagnosing pluggable transceivers

The system outputs alarm information for you to diagnose and troubleshoot faults of pluggable transceivers. Optical transceivers customized by H3C also support the digital diagnosis function, which monitors the key parameters of a transceiver, such as temperature, voltage, laser bias current, TX power, and RX power. When these parameters are abnormal, you can take corresponding measures to prevent transceiver faults.

Follow these steps to diagnose pluggable transceivers:

To do…	Use the command…	Remarks
Display the current alarm information of the pluggable transceivers	display transceiver alarm interface [ interface-type interface-number ] [ | { begin | exclude | include } regular-expression ]	Available for all pluggable transceivers.
Display the currently measured values of the digital diagnosis parameters of the anti-spoofing optical transceivers customized by H3C	display transceiver diagnosis interface [ interface-type interface-number ] [ | { begin | exclude | include } regular-expression ]	Available for anti-spoofing pluggable optical transceivers customized by H3C only.

 

Displaying and maintaining device management configuration

To do…	Use the command…	Remarks
Display the system version information	display version [ | { begin | exclude | include } regular-expression ]	Available in any view
Display the system time information	display clock [ | { begin | exclude | include } regular-expression ]	Available in any view
Display or save the operation statistics of multiple functional modules	display diagnostic-information [ | { begin | exclude | include } regular-expression ]	Available in any view
Display CPU usage statistics	display cpu-usage [ slot slot-number [ cpu cpu-number ] ] [ | { begin | exclude | include } regular-expression ] display cpu-usage entry-number [ offset ] [ verbose ] [ slot slot-number ] [ from-device ] [ | { begin | exclude | include } regular-expression ]	Available in any view
Display CPU usage history statistics in a coordinate plane	display cpu-usage history [ task task-id ] [ | { begin | exclude | include } regular-expression ]	Available in any view
Display information about the device	display device [ slot slot-number | verbose ] [ | { begin | exclude | include } regular-expression ]	Available in any view
Display the electrical label information	display device manuinfo [ | { begin | exclude | include } regular-expression ]	Available in any view
Display the temperature information	display environment [ slot slot-number | vent ] [ | { begin | exclude | include } regular-expression ]	Available in any view
Display fan operating states	display fan [ fan-id | verbose ] [ | { begin | exclude | include } regular-expression ]	Available in any view
Display memory usage	display memory [ cpu cpu-number ] [ | { begin | exclude | include } regular-expression ]	Available in any view
Display the power state	display power [ power-id ] [ | { begin | exclude | include } regular-expression ]	Available in any view
Display the reboot type	display reboot-type [ slot slot-number ] [ | { begin | exclude | include } regular-expression ]	Available in any view
Display the reboot time	display schedule reboot [ | { begin | exclude | include } regular-expression ]	Available in any view
Display the configuration of scheduled tasks configured by the job command	display job [ job-name ] [ | { begin | exclude | include } regular-expression ]	Available in any view
Display the exception handling method	display system-failure [ | { begin | exclude | include } regular-expression ]	Available in any view

 

During daily maintenance or when the system is operating abnormally, you need to display the running status of each functional module to locate the problem. Generally, you need to execute the corresponding display commands for each module, because each module has independent running information.

To collect more information at one time, you can execute the display diagnostic-information command to display or save the operation statistics of multiple functional modules in the system. Execution of the display diagnostic-information command equals execution of the commands display clock, display version, display device, and display current-configuration in turn.