time: Specifies a time in the hh:mm:ss format. The value range for hh is 0 to 23. The value range for mm is 0 to 59. The value range for ss is 0 to 59. The leading zero in a segment can be omitted. If the seconds segment is 0 (hh:mm:00), you can omit it. If both the minutes and seconds segments are 0 (hh:00:00), you can omit both of the segments. For example, to specify 08:00:00, you can enter 8.

date: Specifies a date in the MM/DD/YYYY or YYYY/MM/DD format. The value range for YYYY is 2000 to 2035. The value range for MM is 1 to 12. The value range for DD varies by month.

Usage guidelines

CAUTION:

This command changes the system time, which affects the execution of system time-related features (for example, scheduled tasks) and collaborative operations of the device with other devices (for example, log reporting and statistics collection). Before executing this command, make sure you fully understand its impact on your live network.

‌

Correct system time is essential to network management and communication. You must configure the system time correctly before you run the device on the network.

For the device to use the local system time, execute the clock protocol none command and this command in turn. The specified system time takes effect immediately. Then, the device uses the clock signals generated by its built-in crystal oscillator to maintain the system time.

A device power cycling operation restores the local system time to the default. After the device is power cycled, you must execute this command again to set the local system time.

Examples

# Set the system time to 08:08:08 01/01/2015.

<Sysname> clock datetime 8:8:8 1/1/2015

# Set the system time to 08:10:00 01/01/2015.

<Sysname> clock datetime 8:10 2015/1/1

Related commands

clock protocol

clock summer-time

clock timezone

display clock

clock protocol

Use clock protocol to specify the system time source.

Use undo clock protocol to restore the default.

Syntax

clock protocol { none | ntp | ptp }

undo clock protocol

Default

The device obtains the UTC time from an NTP time source.

Views

System view

Predefined user roles

network-admin

Parameters

none: Uses the system time set by using the clock datetime command.

ptp: Uses PTP to obtain the UTC time. You must configure PTP correctly. For more information about PTP and PTP configuration, see Network Management and Monitoring Configuration Guide.

ntp: Uses NTP to obtain the UTC time. You must configure NTP correctly. For more information about NTP and NTP configuration, see Network Management and Monitoring Configuration Guide.

Usage guidelines

Correct system time is essential to network management and communication. You must configure the system time correctly before you run the device on the network.

The device can use the locally set system time, or obtain the UTC time from a time source on the network and calculate the system time.

If you execute the clock protocol none command, the device uses the locally set system time. The device then uses the clock signals generated by its built-in crystal oscillator to maintain the system time.

If you execute the clock protocol { ntp | ptp } command, the device obtains the UTC time through NTP or PTP and calculates the system time. The device then periodically synchronizes the UTC time and recalculates the system time.

If you execute this command multiple times, the most recent configuration takes effect.

Examples

# Configure the device to use the local UTC time.

<Sysname> system-view

[Sysname] clock protocol none

clock summer-time

Use clock summer-time to set the daylight saving time.

Use undo clock summer-time to restore the default.

Syntax

clock summer-time name start-time start-date end-time end-date add-time

undo clock summer-time

Default

The daylight saving time is not set.

Views

System view

Predefined user roles

network-admin

Parameters

name: Specifies a name for the daylight saving time schedule, a case-sensitive string of 1 to 32 characters.

start-time: Specifies the start time in the hh:mm:ss format. The value range for hh is 0 to 23. The value range for mm is 0 to 59. The value range for ss is 0 to 59. The leading zero in a segment can be omitted. If the seconds segment is 0 (hh:mm:00), you can omit it. If both the minutes and seconds segments are 0 (hh:00:00), you can omit both of the segments. For example, to specify 08:00:00, you can enter 8.

start-date: Specifies the start date in one of the following formats:

· MM/DD. The value range for MM is 1 to 12. The value range for DD varies by month.

· month week day, where:

¡ month—Takes January, February, March, April, May, June, July, August, September, October, November or December.

¡ week—Represents week of the month. It takes first, second, third, fourth, fifth, or last.

¡ day—Takes Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, or Saturday.

end-time: Specifies the end time in the hh:mm:ss format. The value range for hh is 0 to 23. The value range for mm is 0 to 59. The value range for ss is 0 to 59. The leading zero in a segment can be omitted. If the seconds segment is 0 (hh:mm:00), you can omit it. If both the minutes and seconds segments are 0 (hh:00:00), you can omit both of the segments. For example, to specify 08:00:00, you can enter 8.

end-date: Specifies the end date in one of the following formats:

· MM/DD. The value range for MM is 1 to 12. The value range for DD varies by month.

· month week day, where:

¡ month—Takes January, February, March, April, May, June, July, August, September, October, November or December.

¡ week—Represents week of the month. It takes first, second, third, fourth, fifth, or last.

¡ day—Takes Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, or Saturday.

add-time: Specifies the time to be added to the standard time, in the hh:mm:ss format. The value range for hh is 0 to 23. The value range for mm is 0 to 59. The value range for ss is 0 to 59. The leading zero in a segment can be omitted. If the seconds segment is 0 (hh:mm:00), you can omit it. If both the minutes and seconds segments are 0 (hh:00:00), you can omit both of the segments. For example, to specify 08:00:00, you can enter 8.

Usage guidelines

Correct system time is essential to network management and communication. You must configure the system time correctly before you run the device on the network.

After you set the daylight saving time, the device recalculates the system time. To view the system time, use the display clock command.

Make sure all devices on the network are using the same daylight saving time as the local time.

Examples

# Set the system time ahead 1 hour for the period between 06:00:00 on 08/01 and 06:00:00 on 09/01.

<Sysname> system-view

[Sysname] clock summer-time PDT 6 08/01 6 09/01 1

Related commands

clock datetime

clock timezone

display clock

clock timezone

Use clock timezone to set the time zone.

Use undo clock timezone to restore the default.

Syntax

clock timezone zone-name { add | minus } zone-offset

undo clock timezone

Default

The UTC time zone is used.

Views

System view

Predefined user roles

network-admin

Parameters

zone-name: Specifies a time zone by its name, a case-sensitive string of 1 to 32 characters.

add: Adds an offset to the UTC time.

minus: Decreases the UTC time by an offset.

zone-offset: Specifies an offset to the UTC time, in the hh:mm:ss format. The value range for hh is 0 to 23. The value range for mm is 0 to 59. The value range for ss is 0 to 59. The leading zero in a segment can be omitted. If the seconds segment is 0 (hh:mm:00), you can omit it. If both the minutes and seconds segments are 0 (hh:00:00), you can omit both of the segments. For example, to specify 08:00:00, you can enter 8.

Usage guidelines

Correct system time is essential to network management and communication. You must configure the system time correctly before you run the device on the network.

After you set the time zone, the device recalculates the system time. To view the system time, use the display clock command.

Make sure all devices on the network are using the same time zone as the local time.

Examples

# Set the name of the time zone to Z5, and add 5 hours to the UTC time.

<Sysname> system-view

[Sysname] clock timezone Z5 add 5

Related commands

clock datetime

clock summer-time

display clock

command

Use command to assign a command to a job.

Use undo command to revoke a command.

Syntax

command id command

undo command id

Default

No command is assigned to a job.

Views

Job view

Predefined user roles

network-admin

Parameters

id: Specifies an ID for the command, in the range of 0 to 4294967295. A command ID uniquely identifies a command in a job. Commands in a job are executed in ascending order of their command IDs.

command: Specifies the command to be assigned to the job.

Usage guidelines

To assign a command (command A) to a job, you must first assign the job the command or commands for entering the view of command A.

If you specify the ID of an existing command for another command, the existing command is replaced.

Make sure all commands in a schedule are compliant to the command syntax. The system does not examine the syntax when you assign a command to a job.

If a command requires a yes or no answer, the system always assumes that a Y or Yes is entered. If a command requires a character string input, the system assumes that either the default character string (if any) or a null string is entered.

A job cannot contain the telnet, ftp, ssh2, or monitor process command.

Examples

# Assign commands to the backupconfig job to back up the startup.cfg file to the TFTP server at 192.168.100.11.

<Sysname> system-view

[Sysname] scheduler job backupconfig

[Sysname-job-backupconfig] command 2 tftp 192.168.100.11 put flash:/startup.cfg backup.cfg

# Assign commands to the shutdownGE job to shut down HundredGigE 1/1/1.

<Sysname> system-view

[Sysname] scheduler job shutdownGE

[Sysname-job-shutdownGE] command 1 system-view

[Sysname-job-shutdownGE] command 2 interface hundredgige 1/1/1

[Sysname-job-shutdownGE] command 3 shutdown

Related commands

scheduler job

copyright-info enable

Use copyright-info enable to enable copyright statement display.

Use undo copyright-info enable to disable copyright statement display.

Syntax

undo copyright-info enable

Default

Views

System view

Predefined user roles

network-admin

Examples

# Enable copyright statement display.

<Sysname> system-view

[Sysname] copyright-info enable

The device will display the following statement when a user logs in:

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

* Without the owner's prior written consent, *

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

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

display alarm

Use display alarm to display alarm information.

Syntax

display alarm [ slot slot-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

Examples

# Display alarm information.

<Sysname> display alarm

Slot CPU Level Info

1 0 ERROR faulty

Table 1 Command output

Field	Description
Slot	Slot that generated the alarm. If the alarm was generated by the frame, this field displays a hyphen (-).
Level	Alarm severity. Possible values include ERROR, WARNING, NOTICE, and INFO, in descending order.
Info	Detailed alarm information: · faulty—The slot is starting up or faulty. · Fan n is absent—The specified fan is absent. · Power n is absent—The specified power supply is absent. · Power n is faulty—The specified power supply is faulty. · The temperature of sensor n exceeds the lower limit—The temperature of the specified sensor is lower than the low-temperature threshold. · The temperature of sensor n exceeds the upper limit—The temperature of the specified sensor is higher than the high-temperature warning threshold.

‌

display clock

Use display clock to display the system time, date, time zone, and daylight saving time.

Syntax

display clock

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

# Display the system time and date when the time zone is not specified.

<Sysname> display clock

10:09:00.258 UTC Fri 03/16/2015

The time is in the hour:minute:second.milliseconds format.

# Display the system time and date when the time zone Z5 is specified.

<Sysname> display clock

15:10:00.152 Z5 Fri 03/16/2015

Time Zone : Z5 add 05:00:00

# Display the system time and date when the time zone Z5 and daylight saving time PDT are specified.

<Sysname> display clock

15:11:00.211 Z5 Fri 03/16/2015

Time Zone : Z5 add 05:00:00

Summer Time : PDT 06:00:00 08/01 06:00:00 09/01 01:00:00

Related commands

clock datetime

clock timezone

clock summer-time

display copyright

Use display copyright to display the copyright statement.

Syntax

display copyright

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

# Display the copyright statement.

<Sysname> display copyright

...

display cpu-usage

Use display cpu-usage to display the current CPU usage statistics.

Syntax

display cpu-usage [ summary ] [ slot slot-number [ cpu cpu-number [ core { core-number| all } ] ] ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

summary: Displays CPU usage statistics in table form. If you do not specify this keyword, the command displays CPU usage statistics in text form.

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

cpu cpu-number: Specifies a CPU by its number, which is fixed at 0.

core core-number: Specifies a CPU core by its number.

core all: Specifies all CPU cores.

Examples

# Display the current CPU usage statistics in text form.

<Sysname> display cpu-usage

Slot 1 CPU 0 CPU usage:

1% in last 5 seconds

1% in last 1 minute

1% in last 5 minutes

# Display the current CPU usage statistics in table form.

<Sysname> display cpu-usage

Slot CPU Last 5 sec Last 1 min Last 5 min

1 0 17% 29% 28%

Table 2 Command output

Field	Description
x% in last 5 seconds Last 5 sec	Average CPU or CPU core usage during the most recent 5-second interval.
y% in last 1 minute Last 1 min	Average CPU or CPU core usage during the most recent 1-minute interval.
z% in last 5 minutes Last 5 min	Average CPU or CPU core usage during the most recent 5-minute interval.

‌

display cpu-usage configuration

Use display cpu-usage configuration to display CPU usage monitoring settings.

Syntax

display cpu-usage configuration [ slot slot-number [ cpu cpu-number ] ]

Views

Any view

Predefined user roles

network-admin

Parameters

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

cpu cpu-number: Specifies a CPU by its number, which is fixed at 0.

Examples

# Display the CPU usage monitoring settings.

<Sysname> display cpu-usage configuration

CPU usage monitor is enabled.

Current monitor interval is 60 seconds.

Current severe alarm threshold is 90%.

Current severe alarm threshold is 85% for the following cores: 0.

Current minor alarm threshold is 80%.

Current recovery-threshold is 40%.

Table 3 Command output

Field	Description
CPU usage monitor is xxx.	Whether CPU usage tracking is enabled.
Current monitor interval is xxx.	Sampling interval for CPU usage tracking.
Current severe alarm monitor threshold is xxx.	Severe CPU usage alarm threshold.
Current minor alarm threshold is xxx.	Minor CPU usage alarm threshold.
Current recovery threshold is xxx.	CPU usage recovery threshold.

‌

Related commands

monitor cpu-usage enable

monitor cpu-usage interval

monitor cpu-usage threshold

display cpu-usage history

Use display cpu-usage history to display the historical CPU usage statistics in a coordinate system.

Syntax

display cpu-usage history [ job job-id ] [ slot slot-number [ cpu cpu-number ] ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

job job-id: Specifies a process by its ID. The value range for job-id is 1 to 2147483647. If you do not specify a process, this command displays the statistics for the entire system's CPU usage (the total CPU usage of all processes). To view the IDs and names of the running processes, use the display process command. For more information, see Network Management and Monitoring Configuration Guide.

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

cpu cpu-number: Specifies a CPU by its number, which is fixed at 0.

Usage guidelines

After CPU usage monitoring is enabled, the system regularly samples CPU usage and saves the samples to the history record buffer. This command displays the most recent 60 samples in a coordinate system as follows:

· The vertical axis represents the CPU usage. If a statistic is not a multiple of the usage step, it is rounded up or down to the closest multiple of the usage step. For example, if the CPU usage step is 5%, the statistic 53% is rounded up to 55%, and the statistic 52% is rounded down to 50%.

· The horizontal axis represents the time.

· Pound signs (#) indicate the CPU usage. The value on the vertical axis for the topmost pound sign at a specific time represents the CPU usage at that time.

Examples

# Display the historical CPU usage statistics.

<Sysname> display cpu-usage history

100%|

95%|

90%|

85%|

80%|

75%|

70%|

65%|

60%|

55%|

50%|

45%|

40%|

35%|

30%|

25%|

20%|

15%| #

10%| ### #

5%| ########

------------------------------------------------------------

10 20 30 40 50 60 (minutes)

cpu-usage (Slot 1 CPU 0) last 60 minutes (SYSTEM)

The output shows the following items:

· Process name. The name SYSTEM represents the entire system.

· CPU that is holding the process: CPU 0 in slot 1.

· Historical CPU usage statistics for the entire system during the last 60 minutes.

¡ 12 minutes ago—Approximately 5%.

¡ 13 minutes ago—Approximately 10%.

¡ 14 minutes ago—Approximately 15%.

¡ 15 minutes ago—Approximately 10%.

¡ 16 and 17 minutes ago—Approximately 5%.

¡ 18 minutes ago—Approximately 10%.

¡ 19 minutes ago—Approximately 5%.

¡ Other time—2% or lower.

Related commands

monitor cpu-usage enable

monitor cpu-usage interval

display device

Use display device to display device information.

Syntax

display device [ flash | usb ] [ slot slot-number [ subslot subslot-number ] | verbose ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

flash: Displays flash memory information.

usb: Displays USB interface information.

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

subslot subslot-number: Specifies a subcard by its subslot number. If you do not specify a subcard, this command does not display information about any subcards.

verbose: Displays detailed information. If you do not specify this keyword, this command displays brief information, and does not display firewall card information.

Usage guidelines

If you do not specify the flash or usb keyword, this command displays information about the device.

Examples

# Display device information.

<Sysname> display device

Slot 1

Slot Type State Subslot Soft Ver Patch Ver

1 S9820-8C Master 0 S9820-8C-6607 None

Table 4 Command output

Field	Description
Type	Device type.
State	Role of the device.
Soft Ver	Software version of the device.
Patch Ver	Most recently released patch image version that is running on the device. If no patch image is installed, this field displays None. If both incremental and non-incremental patch images are running on the device, this field displays the most recently released incremental patch image version. For more information about patch image types, see "Upgrading software."

‌

display device manuinfo

Use display device manuinfo to display electronic label information for the device.

Syntax

display device manuinfo [ slot slot-number [ subslot subslot-number ] ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

subslot subslot-number: Specifies a subcard by its subslot number. If you do not specify a subcard, this command does not display information about any subcards.

Usage guidelines

An electronic label contains the permanent configuration information, including the hardware serial number, manufacturing date, MAC address, and vendor name. The data is written to the storage component during hardware debugging or testing. This command displays only part of the electronic label information.

Examples

# Display electronic label information for the device.

<Sysname> display device manuinfo

...

display device manuinfo fan

Use display device manuinfo fan to display electronic label information for a fan tray.

Syntax

display device manuinfo slot slot-number fan fan-id

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

fan-id: Specifies a fan tray by its ID.

Examples

# Display electronic label information for a fan tray.

<Sysname> display device manuinfo slot 1 fan 1

...

display device manuinfo power

Use display device manuinfo power to display electronic label information for a power supply.

Syntax

display device manuinfo slot slot-number power power-id

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

power-id: Specifies a power supply by its ID.

Examples

# Display electronic label information for a power supply.

<Sysname> display device manuinfo slot 1 power 1

...

display diagnostic-information

Use display diagnostic-information to display or save operating information for features and hardware modules.

Syntax

display diagnostic-information [ hardware | infrastructure | l2 | l3 | service ] [ key-info ] [ filename ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

hardware: Specifies hardware-related operating information.

infrastructure: Specifies operating information for the fundamental features.

l2: Specifies operating information for the Layer 2 features.

l3: Specifies operating information for the Layer 3 features.

service: Specifies operating information for Layer 4 and upper-layer features.

key-info: Displays or saves only critical operating information. The device might have a large amount of operating information if an exception occurs or after the device runs for a long period of time. Specifying this keyword reduces the command execution time and helps you focus on critical operating information. If you do not specify this keyword, the command displays or saves both critical and non-critical operating information.

filename: Saves the information to a file. The filename argument must use the .tar.gz extension. If you do not specify this argument, the command prompts you to choose whether to save the information to a file or display the information.

Usage guidelines

You can use one of the following methods to collect operating statistics for diagnostics and troubleshooting:

· Use separate display commands to collect operating information feature by feature or module by module.

· Use the display diagnostic-information command to collect operating information for multiple or all features and hardware modules.

To save storage space, this command automatically compresses the information before saving the information to a file. To view the file content:

1. Use the tar extract command to extract the file.

2. Use the gunzip command to decompress the extracted file.

3. Use the more command to view the content of the decompressed file.

If you abort the display diagnostic-information command, the gunzip command might not be able to decompress the extracted file. To decompress the extracted file, export the extracted file to a PC that is running Linux, and use the gunzip -c command.

If you do not specify a file name for the command, the system prompts you to choose whether to display or save the information. If you choose to save the information, the system automatically assigns a file name and displays the file name in brackets. For file name uniqueness, the file name includes the device name and the current system time. If the device name contains any of the following special characters, the system uses an underscore (_) to replace each special character: forward slashes (/), backward slashes (\), colons (:), asterisks (*), question marks (?), less than signs (<), greater than signs (>), pipeline signs (|), and quotation marks ("). For example, device name A/B will change to A_B in the file name, as in flash:/diag_A_B_20160101-000438.tar.gz.

If you do not specify any feature parameters, this command displays or saves the operating information for all features and modules.

This command does not support the |, >, and >> options.

While the device is executing this command, do not execute any other commands. Executing other commands might affect the collected operating information.

Examples

# Display the operating information for all features and modules.

<Sysname> display diagnostic-information

Save or display diagnostic information (Y=save, N=display)? [Y/N]:n

===============================================

===============display clock===============

14:03:55 UTC Thu 01/05/2015

=================================================

===============display version===============

...

# Save the operating information to the default file.

<Sysname> display diagnostic-information

Save or display diagnostic information (Y=save, N=display)? [Y/N]:y

Please input the file name(*.tar.gz)[flash:/diag_Sysname_20160101-024601.tar.gz]:

Diagnostic information is outputting to flash:/diag_Sysname_20160101-024601.tar.gz.

Please wait...

Save successfully.

Press Enter when the system prompts you to enter the file name.

# Save the operating information for all features and modules to file test.tar.gz.

<Sysname> display diagnostic-information test.tar.gz

Diagnostic information is outputting to flash:/test.tar.gz.

Please wait...

Save successfully.

Related commands

gunzip

tar extract

display environment

Use display environment to display temperature information.

Syntax

display environment [ slot slot-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

Examples

# Display information about all temperature sensors on the device.

<Sysname> display environment

System temperature information (degree centigrade):

-----------------------------------------------------------------------------

Slot Sensor Temperature Lower Warning Alarm Shutdown

1 hotspot 1 38 10 40 50 100

1 hotspot 2 42 10 50 80 100

Table 5 Command output

Field	Description
System Temperature information (degree centigrade)	Temperature information (°C).
sensor	Temperature sensor: · hotspot—Hotspot sensor. · inflow—Air inlet sensor. · outflow—Air outlet sensor.
Slot	Sensor position.
Temperature	Current temperature.
Lower	Lower temperature limit. If the device does not support this field, this field displays NA.
Warning	Warning temperature threshold. If the device does not support this field, this field displays NA.
Alarm	Alarming temperature threshold. If the device does not support this field, this field displays NA.
Shutdown	Shutdown temperature threshold. When the sensor temperature reaches the limit, the system shuts down automatically. If the device does not support this field, this field displays NA.

‌

display fan

Use display fan to display fan tray operating status information.

Syntax

display fan [ slot slot-number [ fan-id ] ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

fan-id: Specifies a fan tray by its ID. If you do not specify a fan tray, this command displays operating status information for all fan trays at the specified position.

Examples

# Display the operating states of all fan trays.

<Sysname> display fan

Slot 1:

Fan 1:

State : Normal

Airflow Direction: Port-to-power

Prefer Airflow Direction: Port-to-power

Table 6 Command output

Field	Description
Slot 1	Device ID.
Fan 1	Fan tray number.
State	Fan status: · Absent—The slot is not installed with a fan tray. · Fault—The fan is faulty. · Normal—The fan is operating correctly. · FanDirectionFault—The actual airflow direction is not the preferred direction.
Airflow Direction	Actual airflow direction: · Port-to-power—From the port side to the power supply side. · Power-to-port—From the power supply side to the port side.
Prefer Airflow Direction	Preferred airflow direction: · Port-to-power—From the port side to the power supply side. · Power-to-port—From the power supply side to the port side.

‌

display hardware-failure-detection

Use display hardware-failure-detection to display the hardware failure detection settings and the latest 10 fix records.

Syntax

display hardware-failure-detection

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

# Display hardware failure detection settings and fix records.

<Sysname> display hardware-failure-detection

Current level:

chip : isolate

board : isolate

forwarding : warning

Recent record:

--------------------------Slot 0 executed records:-----------------------------

There is no record.

--------------------------Slot 0 trapped records:-----------------------------

There is no record.

Table 7 Command output

Field	Description
Current level	Fix actions specified for hardware failures.
chip	Fix action for hardware failures on components.
board	Fix action for hardware failures on the device.
forwarding	Fix action for hardware failures on the forwarding plane.
Recent record	Recent failure fix records.

display hardware-resource switch-mode

Use display hardware-resource switch-mode to display hardware resource mode information for the MAC address table, ARP and ND tables, and routing tables.

Syntax

display hardware-resource [ switch-mode ]

Views

Any view

Predefined user roles

network-admin

network-operator

Usage guidelines

If you do not specify the switch-mode keyword, the command displays hardware resource mode information for all hardware resources.

Examples

# Display the hardware resource mode information for the MAC address table, ARP and ND tables, and routing tables.

<H3C>display hardware-resource switch-mode

Switch-mode resource(switch-mode), all supported modes:

NORMAL MAC table:8K, ARP and ND tables:32K, routing table:364K

ROUTING MAC table:8K, ARP and ND tables:16K, routing table:931K

EM MAC table:8K, ARP and ND tables:16K, routing table:245K

-----------------------------------------------

Default Current Next

NORMAL NORMAL NORMAL

NOTE:

The device does not support the EM mode.

Related commands

hardware-resource switch-mode

display memory

Use display memory to display memory usage information.

Syntax

display memory [ summary ] [ slot slot-number [ cpu cpu-number ] ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

summary: Displays brief information about memory usage. If you do not specify this keyword, the command displays detailed information about memory usage.

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

cpu cpu-number: Specifies a CPU by its number, which is fixed at 0.

Examples

# Display detailed memory usage information.

<Sysname> display memory

Memory statistics are measured in KB:

Slot 1:

Total Used Free Shared Buffers Cached FreeRatio

Mem: 984560 456128 528432 0 4 45616 53.7%

-/+ Buffers/Cache: 410508 574052

Swap: 0 0 0

# Display brief memory usage information.

<Sysname> display memory summary

Memory statistics are measured in KB:

Slot CPU Total Used Free Buffers Caches FreeRatio

1 0 984560 456128 528432 4 45616 53.7%

Table 8 Command output

Field	Description
Mem	Memory usage information.
Total	Total size of the physical memory space that can be allocated. The memory space is virtually divided into two parts. Part 1 is solely used for kernel code, kernel management, and ISSU functions. Part 2 can be allocated and used for such tasks as running service modules and storing files. The size of part 2 equals the total size minus the size of part 1.
Used	Used physical memory.
Free	Free physical memory.
Shared	Physical memory shared by processes. If this field is not supported, two hyphens (--) are displayed.
Buffers	Physical memory used for buffers. If this field is not supported, two hyphens (--) are displayed.
Cached Caches	Physical memory used for caches. If this field is not supported, two hyphens (--) are displayed.
FreeRatio	Free memory ratio.
-/+ Buffers/Cache	-/+ Buffers/Cache:used = Mem:Used – Mem:Buffers – Mem:Cached, which indicates the physical memory used by applications. -/+ Buffers/Cache:free = Mem:Free + Mem:Buffers + Mem:Cached, which indicates the physical memory available for applications.
Swap	Memory space for swapping.

‌

display memory-threshold

Use display memory-threshold to display memory alarm thresholds and statistics.

Syntax

display memory-threshold [ slot slot-number [ cpu cpu-number ] ]

Views

Any view

Predefined user roles

network-admin

Parameters

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

cpu cpu-number: Specifies a CPU by its number, which is fixed at 0.

Usage guidelines

For more information about memory usage notifications, see log information containing MEM_EXCEED_THRESHOLD or MEM_BELOW_THRESHOLD.

Examples

# Display memory alarm thresholds and statistics.

<Sysname> display memory-threshold

Memory usage threshold: 100%

Free-memory thresholds:

Minor: 96M

Severe: 64M

Critical: 48M

Normal: 128M

Early-warning: 256M

Secure: 304M

Current free-memory state: Normal (secure)

Free-memory event statistics:

[Back to secure state]

First notification: 0.0

Latest notification: 0.0

Total number of notifications sent: 0

[Entered early-warning state]

First notification at: 0.0

Latest notification at: 0.0

Total number of notifications sent: 0

[Back to normal state]

First notification: 0.0

Latest notification: 0.0

Total number of notifications sent: 0

[Entered minor alarm state]

First notification at: 0.0

Latest notification at: 0.0

Total number of notifications sent: 0

[Back to minor alarm state]

First notification at: 0.0

Latest notification at: 0.0

Total number of notifications sent: 0

[Entered severe alarm state]

First notification at: 0.0

Latest notification at: 0.0

Total number of notifications sent: 0

[Back to severe alarm state]

First notification at: 0.0

Latest notification at: 0.0

Total number of notifications sent: 0

[Entered critical alarm state]

First notification at: 0.0

Latest notification at: 0.0

Total number of notifications sent: 0

display power

Use display power to display power supply information.

Syntax

display power [ slot slot-number [ power-id | verbose ] ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

power-id: Specifies a power supply by its ID. If you do not specify a power supply, this command displays information about all power supplies at the specified position.

verbose: Displays detailed information. The system displays the same information regardless of whether you specify this keyword or not.

Examples

# Display brief power supply information.

<Sysname> display power

Slot 1:

Input Power: 219(W)

PowerID State Mode Current(A) Voltage(V) Power(W) FanDirection

1 Normal AC 18.12 12.01 219 PortToPower

2 Fault -- -- -- -- --

3 Absent -- -- -- -- --

4 Absent -- -- -- -- --

Table 9 Command output

Field	Description
Slot 1	Device ID.
Input Power	Rated power.
PowerID	Power supply ID.
State	Power supply status. · Absent—The slot is not installed with a power supply. · Fault—The power supply is faulty. · Normal—The power supply is operating correctly.
Mode	Mode of the power supply: · AC—AC power supply. · DC—DC power supply.
Current(A)	Output current of the power supply, in amperes. If this field is not supported, two hyphens (--) are displayed.
Voltage(V)	Output voltage of the power supply, in volts. If this field is not supported, two hyphens (--) are displayed.
Power(W)	Output power of the power supply, in watts. If this field is not supported, two hyphens (--) are displayed.
FanDirection	Airflow direction of the power supply: · PowerToPort—From the power supply side to the port side. · PortToPower—From the port supply side to the power side.

‌

display resource-monitor

Use display resource-monitor to display resource monitoring information.

Syntax

display resource-monitor [ resource resource-name ] [ slot slot-number [ cpu cpu-number ] ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

resource resource-name: Specifies a resource type by its name.

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

cpu cpu-number: Specifies a CPU by its number, which is fixed at 0.

Examples

# Display ARP resource monitoring information.

<Sysname> display resource-monitor resource arp

Minor alarms resending: Enabled

Slot 1:

Resource Minor Severe Free/Total

(%) (%) (absolute)

arp 50 20 90095/90098

Table 10 Command output

Field	Description
Minor alarms resending	Status of the minor resource depletion alarm resending feature, Enabled or Disabled.
Resource	Monitored resource type. NOTE: The device does not support monitoring routing resources.
Minor (%)	Minor resource depletion threshold, in percentage.
Severe (%)	Severe resource depletion threshold, in percentage.
Free/Total (absolute)	Numbers of available resources and total resources, in absolute values.

‌

Related commands

resource-monitor minor resend enable

resource-monitor resource

display scheduler job

Use display scheduler job to display job configuration information.

Syntax

display scheduler job [ job-name ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

job-name: Specifies a job by its name, a case-sensitive string of 1 to 47 characters. If you do not specify a job, this command displays configuration information for all jobs.

Examples

# Display configuration information for all jobs.

<Sysname> display scheduler job

Job name: saveconfig

copy startup.cfg backup.cfg

Job name: backupconfig

Job name: creat-VLAN100

system-view

vlan 100

// The output shows that the device has three jobs: the first has one command, the second does not have any commands, and the third has two commands. Jobs are separated by blank lines.

display scheduler logfile

Use display scheduler logfile to display job execution log information.

Syntax

display scheduler logfile

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

# Display job execution log information.

<Sysname> display scheduler logfile

Logfile Size: 1902 Bytes.

Job name : shutdown

Schedule name : shutdown

Execution time : Tue Dec 27 10:44:42 2015

Completion time : Tue Dec 27 10:44:47 2015

--------------------------------- Job output -----------------------------------

<Sysname>system-view

System View: return to User View with Ctrl+Z.

[Sysname]interface rang hundredgige 1/1/1 to hundredgige 1/1/3

[Sysname-if-range]shutdown

Table 11 Command output

Field	Description
Logfile Size	Size of the log file, in bytes.
Schedule name	Schedule to which the job belongs.
Execution time	Time when the job was started.
Completion time	Time when the job was completed. If the job has never been executed or the job does not have any commands, this field is blank.
Job output	Commands in the job and their output.

‌

Related commands

reset scheduler logfile

display scheduler reboot

Use display scheduler reboot to display the automatic reboot schedule.

Syntax

display scheduler reboot

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

# Display the automatic reboot schedule.

<Sysname> display scheduler reboot

System will reboot at 16:32:00 05/23/2015 (in 1 hours and 39 minutes).

Related commands

scheduler reboot at

scheduler reboot delay

display scheduler schedule

Use display scheduler schedule to display schedule information.

Syntax

display scheduler schedule [ schedule-name ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

schedule-name: Specifies a schedule by its name, a case-sensitive string of 1 to 47 characters. If you do not specify a schedule, this command displays information about all schedules.

Examples

# Display information about all schedules.

<Sysname> display scheduler schedule

Schedule name : shutdown

Schedule type : Run once after 0 hours 2 minutes

Start time : Tue Dec 27 10:44:42 2015

Last execution time : Tue Dec 27 10:44:42 2015

Last completion time : Tue Dec 27 10:44:47 2015

Execution counts : 1

-----------------------------------------------------------------------

Job name Last execution status

shutdown Successful

Table 12 Command output

Field	Description
Schedule type	Execution time setting of the schedule. If no execution time is specified, this field is not displayed.
Start time	Time to execute the schedule for the first time. If no execution time is specified, this field is not displayed.
Last execution time	Last time when the schedule was executed. If no execution time is specified, this field is not displayed. If the schedule has never been executed, "Yet to be executed" is displayed for this field.
Last completion time	Last time when the schedule was completed. If no execution time is specified, this field is not displayed.
Execution counts	Number of times the schedule has been executed. If the schedule has never been executed, this field is not displayed.
Job name	Name of a job under the schedule.
Last execution status	Result of the most recent execution: · Successful. · Failed. · Waiting—The device is executing the schedule and the job is waiting to be executed. · In process—The job is being executed. · -NA-—The execution time has not arrived yet. To view information about whether the commands in the job has been executed and the execution results, execute the display scheduler logfile command.

‌

display system stable state

Use display system stable state to display system stability and status information.

Syntax

display system stable state [ summary ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

summary: Displays brief information about system status. If you do not specify this keyword, the command displays detailed information about CPU role and status.

Usage guidelines

The device startup process takes some time. If the values of the status fields do not change to Stable, execute this command multiple times to identify the devices that are not in Stable state. You can also use other commands to identify the faulty components. For example:

· Use the display device command to identify the device operating status.

· Use the display system internal process state command in probe view to display service operating status.

Examples

# Display brief system stability and status information.

<Sysname> display system stable state summary

System state : Stable

Redundancy state : No redundance

NSR state : No standby

# Display system stability and status information.

<Sysname> display system stable state

System state : Stable

Redundancy state: No redundance

Slot CPU Role State

1 0 Active Stable

Table 13 Command output

Field	Description
System state	Operating status of the device: · Stable—The device is operating stably. · Not ready—The device is not operating stably.
Redundancy state	System redundancy status. No redundance indicates that the system has only one device. You cannot perform a switchover.
NSR state	This field is not supported in the current software version. NSR status of all devices: · Stable—NSR is operating correctly on all devices where it is enabled. · Not ready—NSR is not operating correctly on all devices where it is enabled. You cannot perform a process switchover. · No standby—The system has only one device. · Not configured—NSR is not enabled.
Role	Role of the device in the system.
State	Device status: · Stable—The device is operating stably. · Kernel initiating—The device kernel is being initialized. · Service starting—Services are starting on the device. · Service stopping—Services are stopping on the device.
*	The object is not operating stably.

‌

Related commands

display device

display ha service-group (High Availability Command Reference)

display system-working-mode

Use display system-working-mode to display system working mode information.

Syntax

display system-working-mode

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

# Display system working mode information.

<Sysname> display system-working-mode

The current system working mode is standard.

The system working mode for next startup is standard.

display transceiver active-control

Use display transceiver active-control to display the active control information of 400-GE transceiver modules.

NOTE:

This command is supported only in Release 6635 and later.

Syntax

display transceiver active-control interface [ interface-type interface-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

interface [ interface-type interface-number ]: Specifies an interface by its type and number. If no interface is specified, this command applies to all interfaces.

Examples

# Display the active control information of the 400-GE transceiver module in interface FourHundredGigE 1/1/1.

<Sysname> display transceiver active-control interface fourhundredgige 1/1/1

FourHundredGigE1/1/1 transceiver active-control options:

Current ApSel Code : 0002b

Lane LowestHostLane Pre-Cursor Post-Cursor Amplitude

Lane 1 Lane 1 0.5dB 1dB 100-400mV

Lane 2 Lane 1 0.5dB 1dB 100-400mV

Lane 3 Lane 1 0.5dB 1dB 100-400mV

Lane 4 Lane 1 0.5dB 1dB 100-400mV

Lane 5 Lane 5 0.5dB 1dB 100-400mV

Lane 6 Lane 5 0.5dB 1dB 100-400mV

Lane 7 Lane 5 0.5dB 1dB 100-400mV

Lane 8 Lane 5 0.5dB 1dB 100-400mV

Table 14 Command output

Field	Description
Current ApSel Code	Current application type of the transceiver module.
Lane	Current lane.
LowestHostLane	Host lane with the smallest number in the lane group currently used by the transceiver module.
Pre-Cursor	Pre-cursor when the transceiver module acts as the receiver.
Post-Cursor	Post-cursor when the transceiver module acts as the receiver.
Amplitude	Amplitude when the transceiver module acts as the receiver.

‌

display transceiver advertising

Use display transceiver advertising to display the advertising information of 400-GE transceiver modules.

NOTE:

This command is supported only in Release 6635 and later.

Syntax

display transceiver advertising interface [ interface-type interface-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

interface [ interface-type interface-number ]: Specifies an interface by its type and number. If no interface is specified, this command applies to all interfaces.

Examples

# Display the advertising information of the 400-GE transceiver module in interface FourHundredGigE 1/0/1.

<Sysname> display transceiver advertising interface fourhundredgige 1/1/1

FourHundredGigE1/1/1 transceiver advertising information:

CMIS Revision : 3.0

Versatile Diagnostic Monitoring : YES

Tx clock recovery capabilities : Tx input lanes 1-4 and 5-8 to be in separate Tx synchronous groups

Max Tx Input Eq(dB) : 9

Max Rx Output Eq Pre-cursor(dB) : 1.5

Max Rx Output Eq Post-cursor(dB) : 3

Tx disable implemented : YES

Tx Force Squelch implemented : YES

Tx Squelch implemented : NO

Tunable transmitter : YES

Tx bypass CDR implemented : YES

Rx bypass CDR implemented : YES

Tx Input Eq Adaptive : YES

CDB implemented : NO

Table 15 Command output

Field	Description
CMIS revision	QSFP-DD CMIS version. The value is 3.0 or 4.0.
Versatile diagnostic monitoring	Support for versatile diagnostic monitoring: · YES. · NO.
Tx clock recovery capabilities	Clock recovery capabilities when the transceiver module acts as the transmitter: · All Tx input lanes to be in a single Tx synchronous group. · Tx input lanes 1-4 and 5-8 to be in separate Tx synchronous groups. · Tx input lanes 1-2, 3-4, 5-6, 7-8 to be in separate Tx synchronous groups. · Each Tx input lane to be in a separate Tx synchronous group.
Max Tx input Eq (dB)	Maximum Tx Input Equalization control value.
Max Rx output Eq pre-cursor (dB)	Maximum Rx Output Eq Pre-cursor control value.
Max Rx output Eq post-cursor (dB)	Maximum Rx Output Eq Post-cursor control value.
Tx disable implemented	Support for Tx disable: · YES. · NO.
Tx Force Squelch implemented	Support for Tx Force Squelch: · YES. · NO.
Tx Squelch implemented	Support for Tx Squelch: · NO. · OMA—Implements Tx Squelch based on OMA. · Pave—Implements Tx Squelch based on Pave. · Both—Implements Tx Squelch based on OMA or Pave as needed.
Tunable transmitter	Indicates whether the transmitter is tunable: · YES. · NO.
Tx bypass CDR implemented	Support for bypass CDR when the transceiver module acts as the transmitter: · YES. · NO.
Rx bypass CDR implemented	Support for bypass CDR when the transceiver module acts as the receiver: · YES. · NO.
Tx input Eq adaptive	Support for the input equalization adaptive control when the transceiver module acts as the transmitter: · YES. · NO.
CDB implemented	Support for CDB: · NO. · One instance of CDB—Supports one CDB instance. · Two instances of CDB—Supports two CDB instances. · Unknown.

‌

display transceiver alarm

Use display transceiver alarm to display transceiver alarms.

Syntax

display transceiver alarm interface [ interface-type interface-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

interface [ interface-type interface-number ]: Specifies an interface by its type and number. If no interface is specified, this command displays the alarms present on every transceiver module.

Usage guidelines

Table 16 shows the common transceiver alarm components. If no error occurs, None is displayed.

Table 16 Common transceiver alarm components

Field	Description
RX	Receive
TEC	Thermoelectric cooler
Temp	Temperature
TX	Transmit
CDR	Clock data recovery
LoL	Loss of lock
eq	Equalization

‌

Examples

# Display the alarms present on the transceiver module in interface HundredGigE 1/1/1.

<Sysname> display transceiver alarm interface hundredgige 1/1/1

HundredGigE1/1/1 transceiver current alarm information:

RX signal loss

RX power low

Table 17 Command output

Field	Description
transceiver current alarm information	Alarms present on the transceiver module.
RX signal loss	Inbound signal loss occurred.
RX power low	Received power is low.

‌

display transceiver application

Use display transceiver application to display application related information for 400-GE transceiver modules.

NOTE:

This command is supported only in Release 6635 and later.

Syntax

display transceiver application interface [ interface-type interface-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

interface [ interface-type interface-number ]: Specifies an interface by its type and number. If no interface is specified, this command applies to all interfaces.

Examples

# Display application related information for the 400-GE transceiver module in interface FourHundredGigE 1/0/1.

<Sysname> display transceiver application interface fourhundredgige 1/1/1

FourHundredGigE1/1/1 transceiver application information:

ApSel code: 0001b

Host electrical interface code : 400GAUI-8 C2M

Module media interface code : 400G-SR8

Host lanes : 8

Media lanes : 8

Lowest host lane : 1

Lowest media lane : 1

ApSel Code: 0002b

Host Electrical Interface code : 200GAUI-4

Module Media Interface Code : 200G-SR4

Host Lane Count : 4

Media Lane Count : 4

The Lowest host Lane : 1,5

The Lowest media lane : 1,5

Table 18 Command output

Field	Description
ApSel Code	Current application of the transceiver module represented by the ApSel code.
The Lowest host Lane	Host lane with the smallest number for the application in each lane group. The supported number of lanes varies by application of the transceiver module. These lanes are divides into groups.
The Lowest media lane	Media lane with the smallest number for the application.

‌

display transceiver diagnosis

Use display transceiver diagnosis to display the current values of the digital diagnosis parameters on transceiver modules.

Syntax

display transceiver diagnosis interface [ interface-type interface-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

interface [ interface-type interface-number ]: Specifies an interface by its type and number. If no interface is specified, this command displays the current values of the digital diagnosis parameters on every transceiver module.

Examples

# Display the current values of the digital diagnosis parameters on the transceiver module in interface HundredGigE 1/1/1.

<Sysname> display transceiver diagnosis interface hundredgige 1/1/1

HundredGigE1/1/1 transceiver diagnostic information:

Current diagnostic parameters:

Temp(°C) Voltage(V) Bias(mA) RX power(dBm) TX power(dBm)

36 3.31 6.13 -35.64 -5.19

Alarm thresholds:

Temp(°C) Voltage(V) Bias(mA) RX power(dBM) TX power(dBM)

High 50 3.55 1.44 -10.00 5.00

Low 30 3.01 1.01 -30.00 0.00

# Display the current values of the digital diagnosis parameters on the transceiver module in interface HundredGigE 1/1/1.

<Sysname>display transceiver diagnostic interface FourHundredGigE1/1/1

FourHundredGigE1/1/1 transceiver diagnostic information:

Current diagnostic parameters:

[Module] Temp.(°C) Voltage(V) TEC Curr. (%) Laser Temp. (°C)

40 3.34 38 53

[Channel] Bias(mA) RX power(dBm) TX power (dBm)

1 1.13 -20.43 -1.0

2 1.13 -20.43 -1.0

3 1.13 -20.43 -1.0

4 1.13 -20.43 -1.0

5 1.13 -20.43 -1.0

6 1.13 -20.43 -1.0

7 1.13 -20.43 -1.0

8 1.13 -20.43 -1.0

Alarm thresholds:

Temp.(°C) Voltage(V) Bias(mA) RX power(dBm) TX power(dBm)

High 80 3.64 15.00 5.00 5.50

Low -10 2.97 4.50 -12.00 -3.50

# Display the main status parameters on the transceiver module in interface HundredGigE 1/1/1. (This example is available only for a transceiver module that supports CMIS 4.0.)

<Sysname> display transceiver diagnostic interface fourhundredgige 1/1/1

FourHundredGigE1/1/1 transceiver diagnostic information:

Current diagnostic parameters:

Temp(°C) Voltage(V) Bias(mA) RX power(dBm) TX power(dBm)

36 3.31 6.13 -35.64 -5.19

Alarm thresholds:

Temp(°C) Voltage(V) Bias(mA) RX power(dBM) TX power(dBM)

High 50 3.55 1.44 -10.00 5.00

Low 30 3.01 1.01 -30.00 0.00

Media performance monitoring:

RX bits : 12345678901234567890

FEC corrected bits : 12345678901234567890

RX frames : 12345678901234567890

RX uncorrectable frames : 12345678901234567890

ost performance monitoring:

RX bits : 12345678901234567890

FEC corrected bits : 12345678901234567890

RX frames : 12345678901234567890

RS uncorrectable frames : 12345678901234567890

Table 19 Command output

Field	Description
transceiver diagnostic information	Digital diagnosis information for the transceiver module in the interface.
Temp.(°C)	Temperature in °C, accurate to 1°C.
Voltage(V)	Voltage in V, accurate to 0.01 V.
TEC Curr. (%)	Rated TEC current in percentage, accurate to 0.01%.
Laser Temp. (°C)	Rated laser temperature in °C, accurate to 0.01°C.
Bias(mA)	Bias current in mA, accurate to 0.01 mA.
RX power(dBm)	Receive power in dBm, accurate to 0.01 dBm.
TX power(dBm)	Transmit power in dBm, accurate to 0.01 dBm.

‌

display transceiver interface

Use display transceiver interface to display the key parameters of transceiver modules.

Syntax

display transceiver interface [ interface-type interface-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface, this command displays the key parameters of every transceiver module.

Examples

# Display the key parameters of the transceiver module in interface HundredGigE 1/1/1.

<Sysname> display transceiver interface hundredgige 1/1/1

...

display transceiver manuinfo

Use display transceiver manuinfo to display electronic label information for transceiver modules.

Syntax

display transceiver manuinfo interface [ interface-type interface-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

interface [ interface-type interface-number ]: Specifies an interface by its type and number. If no interface is specified, this command displays electronic label information for all transceiver modules.

Examples

# Display electronic label information for the transceiver module in interface HundredGigE 1/1/1.

<Sysname> display transceiver manuinfo interface hundredgige 1/1/1

...

display transceiver status

Use display transceiver status to display 400-GE transceiver module status information.

NOTE:

This command is supported only in Release 6635 and later.

Syntax

display transceiver status interface [ interface-type interface-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

interface [ interface-type interface-number ]: Specifies an interface by its type and number. If you do not specify an interface, this command applies to all interfaces.

Examples

# Display status information for the 400-GE transceiver module in interface FourHundredGigE 1/1/1.

<Sysname> display transceiver status interface fourhundredgige 1/1/1

FourHundredGigE1/1/1 transceiver status information:

Module status : Low power

Interrupt : Yes

Lane Data path state Media lane state

lane1 Deactivated Enabled

lane2 Deactivated Enabled

lane3 Deactivated Enabled

lane4 Deactivated Enabled

lane5 Deactivated Enabled

lane6 Deactivated Enabled

lane7 Deactivated Enabled

lane8 Deactivated Enabled

Table 20 Command output

Field	Description
Module status	Transceiver module status: · Low power—The transceiver module operates in low power. · Power up—The transceiver module is powered on. · Ready—The transceiver module is ready. · Power down—The transceiver module is powered off. · Faulty—The transceiver module is faulty. · Unknown.
Interrupt alarm	Indicates whether the transceiver module is in interrupt alarm status: · Yes. · No.
Data path state	Data path status: · Unknown. · Deactivated. · Initial—The transceiver module is performing initialization tasks on the data path. · Deinit—The data path is deinitialized. · Activated. · TxTurnOn—Tx output is enabled. · TxTurnOff—Tx output is disabled. · Initialized—The data path is fully initialized.
Media Lane State	Media lane status: · Enabled. · Disabled.

‌

display transceiver vdm

Use display transceiver vdm to display the versatile diagnostics monitoring (VDM) information of a transceiver module.

NOTE:

This command is supported only in Release 6635 and later.

Syntax

display transceiver vdm interface interface-type interface-number vdm-id vdm-id

Views

Any view

Predefined user roles

network-admin

Parameters

interface-type interface-number: Specifies an interface by its type and number.

vdm-id vdm-id: Specifies a VDM by its ID. The value range varies by transceiver module model.

Examples

# Display the VDM 1 information of the transceiver module in FourHundredGigE 1/1/1.

<Sysname> display transceiver vdm interface fourhundredgige 1/1/1 vdm-id 1

FourHundredGigE1/1/1 transceiver VDM 1 information:

VDM description Module/lane VDM value

eSNR media input Lane1 18dB

Warning/Alarm thresholds:

Warning Alarm

High 20dB 22dB

Low 16dB 14dB

# Display the VDM 2 information of the transceiver module in FourHundredGigE 1/1/1.

<Sysname> display transceiver vdm interface fourhundredgige 1/1/1 vdm-id 2

FourHundredGigE1/1/1 transceiver VDM 2 information:

VDM description Module/lane VDM value

CFO Module 5MHz

Alarm/Warning thresholds:

Warning Alarm

High 10MHz 15MHz

Low -10MHz -15MHz

display version

Use display version to display system version information.

Syntax

display version

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

# Display system version information.

<Sysname> display version

H3C Comware Software, Version 7.1.070, Feature 2607

H3C S6800-54QT uptime is 0 weeks, 0 days, 2 hours, 14 minutes

Last reboot reason : Cold reboot

Boot image: flash:/s6800-cmw710-boot-f2607.bin

Boot image version: 7.1.070, Feature 2607

Compiled May 15 2017 16:00:00

System image: flash:/s6800-cmw710-system-f2607.bin

System image version: 7.1.070, Feature 2607

Compiled May 15 2017 16:00:00

...

Table 21 Command output

Field	Description
Last reboot reason	Reason for the last reboot: · User reboot—The reboot was manually initiated from a user interface, such as the CLI or SNMP. · Cold reboot—The reboot was caused by a power cycle. · Kernel abnormality reboot—The reboot was caused by kernel exceptions. · DeadLoop reboot—The reboot was caused by a kernel thread dead loop. · DEV HandShake reboot—The reboot was caused by a device management handshake failure. · Auto Update reboot—The reboot was caused by an automatic software upgrade. · Memory exhaust reboot—The reboot was caused by a memory-exhausted event.

Field

Description

Last reboot reason

Reason for the last reboot:

· User reboot—The reboot was manually initiated from a user interface, such as the CLI or SNMP.

· Cold reboot—The reboot was caused by a power cycle.

· Kernel abnormality reboot—The reboot was caused by kernel exceptions.

· DeadLoop reboot—The reboot was caused by a kernel thread dead loop.

· DEV HandShake reboot—The reboot was caused by a device management handshake failure.

· Auto Update reboot—The reboot was caused by an automatic software upgrade.

· Memory exhaust reboot—The reboot was caused by a memory-exhausted event.

‌

display version-update-record

Use display version-update-record to display startup software image upgrade records.

Syntax

display version-update-record

Views

Any view

Predefined user roles

network-admin

network-operator

Usage guidelines

The device records its current startup software version information whenever it starts up, and records all software version update information. Such information can survive reboots.

Examples

# Display the startup software image upgrade records.

<Sysname> display version-update-record

Record 1 (updated on Apr 18 2015 at 06:23:54):

*Name : simware-cmw710-boot.bin

Version : 7.1.070 Test 0001

Compile time: Mar 25 2015 15:52:43

*Name : simware-cmw710-system.bin

Version : 7.1.070 Test 0001

Compile time: Mar 25 2015 15:52:43

Table 22 Command output

Field	Description
Record n	Number of the startup software image upgrade record. Record 1 is the most recent record.
Name	Software image file name.
*	The software image version changed during the upgrade.

‌

Related commands

reset version-update-record

fan prefer-direction

Use fan prefer-direction to specify the preferred airflow direction for the device.

Use undo fan prefer-direction to restore the default.

Syntax

fan prefer-direction slot slot-number { port-to-power | power-to-port }

undo fan prefer-direction slot slot-number

Default

The preferred airflow direction is from the power supply side to the port side.

Views

System view

Predefined user roles

network-admin

Parameters

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

port-to-power: Specifies the airflow direction from the port side to the power supply side.

power-to-port: Specifies the airflow direction from the power supply side to the port side.

Examples

# Set the preferred airflow direction to port-to-power for the device.

<Sysname> system-view

[Sysname] fan prefer-direction slot 1 port-to-power

Related commands

display fan

hardware-failure-detection

Use hardware-failure-detection to specify the action to be taken in response to hardware failures.

Use undo hardware-failure-detection to restore the default.

Syntax

hardware-failure-detection { board | chip | forwarding } { isolate | off | reset | warning }

undo hardware-failure-detection { board | chip | forwarding }

Default

The system takes the warning action in response to hardware failures on chips, the device, and the forwarding plane.

Views

System view

Predefined user roles

network-admin

Parameters

board: Specifies failures on control paths and the device.

chip: Specifies failures on components of the device such as the chips, capacitances, and resistances.

forwarding: Specifies failures on the forwarding plane (including services and other relevant items).

isolate: Takes one or more of the following actions:

· Shuts down the relevant ports.

· Prohibits loading software.

· Powers off the device.

off: Takes no action.

reset: Restarts the relevant components or the device to recover from failures.

warning: Sends traps to notify you of the failures.

Usage guidelines

The system automatically and continuously checks the components, the device, and the forwarding plane for hardware failures. You can specify the actions to be taken in response to detected failures.

Examples

# Configure the system to send traps in response to failures on components.

<Sysname> system-view

[Sysname] hardware-failure-detection chip warning

hardware-resource switch-mode

Use hardware-resource switch-mode to set the hardware resource mode for the MAC address table, ARP/ND table, and routing tables.

Use undo hardware-resource switch-mode to restore the default.

Syntax

hardware-resource switch-mode { NORMAL | ROUTING }

undo hardware-resource switch-mode

Default

The hardware resource mode is NORMAL.

Views

System view

Predefined user roles

network-admin

Parameters

NORMAL: Specifies the normal mode.

ROUTING: Specifies the routing mode. This mode provides larger routing tables than the normal mode.

Usage guidelines

The device supports multiple hardware resource modes for the MAC address table, ARP/ND table, and routing tables. The capacities of the tables vary by hardware resource mode. For more information, see device management in Fundamentals Configuration Guide.

This setting takes effect after you save the running configuration and reboot the device. Before rebooting the device, make sure you know the possible impact on the network.

Examples

# Set the hardware resource mode to routing.

<Sysname> system-view

[Sysname] hardware-resource switch-mode routing

Do you want to change the specified hardware resource working mode? [Y/N]:y

The hardware resource working mode is changed, please save the configuration and

reboot the system to make it effective.

Related commands

display hardware-resource switch-mode

header

Use header to configure a banner.

Use undo header to delete a banner.

Syntax

header { incoming | legal | login | motd | shell } text

undo header { incoming | legal | login | motd | shell }

Default

The device does not have banners.

Views

System view

Predefined user roles

network-admin

Parameters

incoming: Configures the banner to be displayed before a modem dial-in user accesses user view. If authentication is required, the incoming banner appears after the authentication is passed.

legal: Configures the banner to be displayed before a user inputs the username and password to access the CLI.

motd: Configures the greeting banner to be displayed before the legal banner appears.

shell: Configures the banner to be displayed before a non-modem dial-in user accesses user view.

text: Specifies the banner message. You can enter the banner message on the same line as the keywords or on different lines. For more information, see Fundamentals Configuration Guide.

Examples

# Configure the legal banner.

<Sysname> system-view

[Sysname] header legal

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

Welcome to use the legal banner%

job

Use job to assign a job to a schedule.

Use undo job to revoke a job.

Syntax

job job-name

undo job job-name

Default

No job is assigned to a schedule.

Views

Schedule view

Predefined user roles

network-admin

Parameters

job-name: Specifies the job name, a case-sensitive string of 1 to 47 characters.

Usage guidelines

You can assign multiple jobs to a schedule. The jobs in a schedule are executed concurrently.

The jobs to be assigned to a schedule must already exist. To create a job, use the scheduler job command.

Examples

# Assign job save-job to schedule saveconfig.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] job save-job

Related commands

scheduler job

scheduler schedule

locator blink

Use locator blink blink-time to start LED flashing to locate devices.

Use locator blink stop to stop LED flashing.

Syntax

locator [ slot slot-number ] blink blink-time

locator [ slot slot-number ] blink stop

Views

User view

Predefined user roles

network-admin

Parameters

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

blink-time: Specifies the flash duration in seconds. The value range is 5 to 120.

stop: Stops flashing.

Usage guidelines

The device provides a LED for device locating. The locator blink blink-time command flashes the specified LEDs quickly for a period of time unless you execute the locator blink stop command. You can observe the LEDs to locate the devices.

Examples

# Start LED flashing to locate devices.

<Sysname> locator blink 30

# Stop LED flashing.

<Sysname> locator blink stop

memory-threshold

Use memory-threshold to set free-memory thresholds.

Use undo memory-threshold to restore the defaults.

Syntax

memory-threshold [ slot slot-number [ cpu cpu-number ] ] [ ratio ] minor minor-value severe severe-value critical critical-value normal normal-value [ early-warning early-warning-value secure secure-value ]

undo memory-threshold [ slot slot-number [ cpu cpu-number ] ]

Default

Minor alarm threshold: 96 MB.

Severe alarm threshold: 64 MB.

Critical alarm threshold: 48 MB.

Normal state threshold: 128 MB.

Views

System view

Predefined user roles

network-admin

Parameters

ratio: Specifies free-memory thresholds in percentage. If you do not specify this keyword, the command sets free-memory thresholds in MB.

minor minor-value: Specifies the minor alarm threshold. To view the value range for this threshold, enter a question mark (?) in the place of the minor-value argument. Setting this threshold to 0 disables the minor alarm feature.

severe severe-value: Specifies the severe alarm threshold. To view the value range for this threshold, enter a question mark (?) in the place of the severe-value argument. Setting this threshold to 0 disables the severe alarm feature.

critical critical-value: Specifies the critical alarm threshold. To view the value range for this threshold, enter a question mark (?) in the place of the critical-value argument. Setting this threshold to 0 disables the critical alarm feature.

normal normal-value: Specifies the normal state threshold. To view the value range for this threshold, enter a question mark (?) in the place of the normal-value argument.

early-warning early-warning-value: Specifies the early-warning threshold. To view the value range for this threshold, enter a question mark (?) in the place of the early-warning-value argument. Setting this threshold to 0 disables the early warning feature.

secure secure-value: Specifies the sufficient-memory threshold. To view the value range for this threshold, enter a question mark (?) in the place of the secure-value argument.

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

cpu cpu-number: Specifies a CPU by its number, which is fixed at 0.

Usage guidelines

To ensure correct operation and improve memory efficiency, the system monitors the amount of free memory space in real time. If the amount of free memory space decreases to or below the minor, severe, or critical alarm threshold, the system issues an alarm to affected service modules or processes.

You can use the display memory command to display memory usage information.

The early warning feature warns you of an approaching insufficient-memory condition.

If a memory alarm occurs, delete unused configuration items or disable some features to increase the free memory space. Because the memory space is insufficient, some configuration items might not be able to be deleted.

For more information about the thresholds, see Fundamentals Configuration Guide.

Examples

# Set the minor alarm, severe alarm, critical alarm, and normal state thresholds to 64 MB, 48 MB, 32 MB, and 96 MB, respectively.

<Sysname> system-view

[Sysname] memory-threshold minor 64 severe 48 critical 32 normal 96

# Set the minor alarm, severe alarm, critical alarm, and normal state thresholds to 3%, 2%, 1%, and 5% of the total memory size, respectively.

<Sysname> system-view

[Sysname] memory-threshold ratio minor 3 severe 2 critical 1 normal 5

Related commands

display memory-threshold

memory-threshold usage

Use memory-threshold usage to set the memory usage threshold.

Use undo memory-threshold usage to restore the default.

Syntax

memory-threshold [ slot slot-number [ cpu cpu-number ] ] usage memory-threshold

undo memory-threshold [ slot slot-number [ cpu cpu-number ] ] usage

Default

The memory usage threshold is 100%.

Views

System view

Predefined user roles

network-admin

Parameters

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

cpu cpu-number: Specifies a CPU by its number, which is fixed at 0.

memory-threshold: Specifies the memory usage threshold in percentage. The value range is 0 to 100.

Usage guidelines

The device samples memory usage at 1-minute intervals. If the sample is greater than the memory usage threshold, the device sends a trap.

Examples

# Set the memory usage threshold to 80%.

<Sysname> system-view

[Sysname] memory-threshold usage 80

Related commands

display memory-threshold

monitor cpu-usage enable

Use monitor cpu-usage enable to enable CPU usage monitoring.

Use undo monitor cpu-usage enable to disable CPU usage monitoring.

Syntax

monitor cpu-usage enable [ slot slot-number [ cpu cpu-number ] ]

undo monitor cpu-usage enable [ slot slot-number [ cpu cpu-number ] ]

Default

CPU usage monitoring is enabled.

Views

System view

Predefined user roles

network-admin

Parameters

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

cpu cpu-number: Specifies a CPU by its number, which is fixed at 0.

Usage guidelines

After CPU usage monitoring is enabled, the system samples and saves CPU usage at the interval specified by the monitor cpu-usage interval command. You can use the display cpu-usage history command to view recent CPU usage.

Examples

# Enable CPU usage monitoring.

<Sysname> system-view

[Sysname] monitor cpu-usage enable

Related commands

display cpu-usage configuration

display cpu-usage history

monitor cpu-usage interval

Use monitor cpu-usage interval to set the sampling interval for CPU usage monitoring.

Use undo monitor cpu-usage interval to restore the default.

Syntax

monitor cpu-usage interval interval [ slot slot-number [ cpu cpu-number ] ]

undo monitor cpu-usage interval [ slot slot-number [ cpu cpu-number ] ]

Default

The system samples CPU usage every 1 minute.

Views

System view

Predefined user roles

network-admin

Parameters

interval: Specifies the sampling interval for CPU usage monitoring. Valid values include 5Sec (5 seconds), 1Min (1 minute), and 5Min (5 minutes), case insensitive.

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

cpu cpu-number: Specifies a CPU by its number, which is fixed at 0.

Usage guidelines

After CPU usage monitoring is enabled, the system samples and saves CPU usage at the specified interval. You can use the display cpu-usage history command to view recent CPU usage.

Examples

# Set the sampling interval for CPU usage monitoring to 5 seconds.

<Sysname> system-view

[Sysname] monitor cpu-usage interval 5Sec

Related commands

display cpu-usage configuration

display cpu-usage history

monitor cpu-usage enable

monitor cpu-usage threshold

Use monitor cpu-usage threshold to set CPU usage alarm thresholds.

Use undo monitor cpu-usage threshold to restore the default.

Syntax

Release 6607:

monitor cpu-usage threshold severe-threshold minor-threshold minor-threshold recovery-threshold recovery-threshold [ slot slot-number [ cpu cpu-number ] ]

undo monitor cpu-usage threshold minor-threshold recovery-threshold [ slot slot-number [ cpu cpu-number ] ]

Release 6616 and later:

monitor cpu-usage threshold severe-threshold { minor-threshold minor-threshold recovery-threshold recovery-threshold | slot slot-number cpu cpu-number core core-id-list }

undo monitor cpu-usage threshold { minor-threshold recovery-threshold | slot slot-number cpu cpu-number core core-id-list }

Default

Severe CPU usage alarm threshold: 99%.

Minor CPU usage alarm threshold: 90%.

CPU usage recovery threshold: 60%.

Views

System view

Predefined user roles

network-admin

Parameters

severe-threshold: Specifies the severe CPU usage alarm threshold in percentage. The value range for this argument is 2 to 100.

minor-threshold minor-threshold: Specifies the minor CPU usage alarm threshold in percentage. The value range for this argument is 1 to the severe CPU usage alarm threshold minus 1.

recovery-threshold recovery-threshold: Specifies the CPU usage recovery threshold in percentage. The value range for this argument is 0 to the minor CPU usage alarm threshold minus 1.

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

cpu cpu-number: Specifies a CPU by its number, which is fixed at 0.

core core-id-list: Specifies a space-separated list of up to 10 CPU core items. Each item specifies a CPU core or a range of CPU cores in the form of core-id1 [ to core-id2 ]. The value for core-id2 must be greater than or equal to the value for core-id1. (This option is supported only in Release 6616 and later.)

Usage guidelines

CAUTION:

If you set the severe CPU usage alarm threshold to a too low value, the device will reach the threshold easily. Normal services will be affected.

‌

The device samples CPU usage and CPU core usage at 1-minute intervals. If the sample is greater than a usage threshold, the device will handle the issue accordingly.

Examples

# Set the severe CPU usage alarm threshold to 90%, minor CPU usage alarm threshold to 80%, and CPU usage recovery threshold to 70%.

<Sysname> system-view

[Sysname] monitor cpu-usage threshold 90 minor-threshold 80 recovery-threshold 70

Related commands

display cpu-usage configuration

monitor resend cpu-usage

Use monitor resend cpu-usage to set CPU usage alarm resending intervals.

Use undo monitor resend cpu-usage to restore the default.

Syntax

monitor resend cpu-usage { minor-interval minor-interval | severe-interval severe-interval } * [ slot slot-number [ cpu cpu-number ] ]

undo monitor resend cpu-usage [ minor-interval | severe-interval ] [ slot slot-number [ cpu cpu-number ] ]

Default

The minor alarm resending interval is 300 seconds. The severe alarm resending interval is 60 seconds.

Views

System view

Predefined user roles

network-admin

Parameters

minor-interval minor-interval: Specifies the minor alarm resending interval in seconds, a multiple of five in the range of 10 to 3600.

severe-interval severe-interval: Specifies the severe alarm resending interval in seconds, a multiple of five in the range of 10 to 3600.

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

cpu cpu-number: Specifies a CPU by its number, which is fixed at 0.

Usage guidelines

The device samples CPU usage periodically and compares the sample with the CPU usage threshold. If the sample increases above an alarm threshold, the CPU usage enters an alarm state and the device sends an alarm.

While the CPU usage is in minor alarm state, the device sends minor alarms periodically until the CPU usage increases above the severe threshold or the minor alarm is removed.

While the CPU usage is in severe alarm state, the device sends severe alarms periodically until the severe alarm is removed.

You can use this command to change CPU usage alarm resending intervals.

If you do not specify the minor-interval or severe-interval keyword, the undo monitor resend cpu-usage command restores default settings for both the minor and severe alarm resending intervals.

Examples

# Set the CPU usage minor alarm resending interval to 60 seconds for CPU 0 in slot 1.

<Sysname> system-view

[Sysname] monitor resend cpu-usage minor-interval 60 slot 1 cpu 0

monitor resend memory-threshold

Use monitor resend memory-threshold to set memory depletion alarm resending intervals.

Use undo monitor resend memory-threshold to restore the default.

Syntax

monitor resend memory-threshold { critical-interval critical-interval | early-warning-interval early-warning-interval | minor-interval minor-interval | severe-interval severe-interval } * [ slot slot-number [ cpu cpu-number ] ]

undo monitor resend memory-threshold [ critical-interval | early-warning-interval | minor-interval | severe-interval ] * [ slot slot-number [ cpu cpu-number ] ]

Default

· Early warning resending interval: 1 hour.

· Minor alarm resending interval: 12 hours.

· Severe alarm resending interval: 3 hours.

· Critical alarm resending interval: 1 hour.

Views

System view

Predefined user roles

network-admin

Parameters

critical-interval critical-interval: Specifies the critical alarm resending interval in hours, in the range of 1 to 48.

early-warning-interval early-warning-interval: Specifies the early warning resending interval in hours, in the range of 1 to 48.

minor-interval minor-interval: Specifies the minor alarm resending interval in hours, in the range of 1 to 48.

severe-interval severe-interval: Specifies the severe alarm resending interval in hours, in the range of 1 to 48.

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

cpu cpu-number: Specifies a CPU by its number, which is fixed at 0.

Usage guidelines

The device samples the amount of free memory space periodically and compares the sample with free-memory thresholds. If the sample decreases to or below a threshold, the device enters a memory depletion alarm state and sends an alarm.

In critical alarm state, the device sends critical alarm notifications periodically until the critical alarm is removed.

In a lower alarm state, the device sends notifications for the alarm state periodically until it enters a higher alarm state or the current alarm is removed.

You can use this command to change the alarm resending intervals.

If you do not specify any memory depletion alarm resending intervals, the undo monitor resend memory-threshold command restores default settings for all memory depletion alarm resending intervals.

Examples

# Set the minor memory depletion alarm resending interval to 12 hours for CPU 0 in slot 1.

<Sysname> system-view

[Sysname] monitor resend memory-threshold minor-interval 12 slot 1 cpu 0

parity-error consistency-check log enable

Use parity-error consistency-check log enable to enable consistency error logging for software and hardware forwarding entries.

Use undo parity-error consistency-check log enable to disable consistency error logging for software and hardware forwarding entries.

Syntax

parity-error consistency-check log enable

undo parity-error consistency-check log enable

Default

Consistency error logging is disabled for software and hardware forwarding entries.

Views

System view

Predefined user roles

network-admin

Usage guidelines

To forward packets, the device generates hardware forwarding entries in forwarding chips and software forwarding entries in memory at the same time. The device automatically detects whether the hardware forwarding entries and the software forwarding entries are consistent.

After you execute this command, the device collects consistency errors periodically. If the number of consistency errors in a statistics period reaches or exceeds the logging threshold, the device generates a log message.

Examples

# Enable consistency error logging for software and hardware forwarding entries.

<Sysname> system-view

[Sysname] parity-error consistency-check log enable

Related commands

parity-error consistency-check period

parity-error consistency-check threshold

parity-error consistency-check period

Use parity-error consistency-check period to set the statistics period for consistency errors between software and hardware forwarding entries.

Use undo parity-error consistency-check period to restore the default.

Syntax

parity-error consistency-check period value

undo parity-error consistency-check period

Default

The statistics period is 3600 seconds.

Views

System view

Predefined user roles

network-admin

Parameters

value: Specifies the statistics period (in seconds) for consistency errors between software and hardware forwarding entries, in the range of 600 to 31536000.

Usage guidelines

This command determines the period for the device to collect consistency error statistics.

As a best practice, set the consistency error statistics period to a value greater than 3600 seconds.

Examples

# Set the statistics period to 600 seconds for consistency errors between software and hardware forwarding entries.

<Sysname> system-view

[Sysname] parity-error consistency-check period 600

Related commands

parity-error consistency-check log enable

parity-error consistency-check threshold

Use parity-error consistency-check period to set the logging threshold for consistency errors between software and hardware forwarding entries.

Use undo parity-error consistency-check period to restore the default.

Syntax

parity-error consistency-check threshold value

undo parity-error consistency-check threshold

Default

The logging threshold is 10.

Views

System view

Predefined user roles

network-admin

Parameters

value: Specifies the logging threshold for consistency errors between software and hardware forwarding entries, in the range of 1 to 2147483647.

Usage guidelines

After you enable consistency error logging for software and hardware forwarding entries, the device collects statistics for consistency errors periodically. If the number of consistency errors reaches or exceeds the logging threshold, the device generates a log message.

Examples

# Set the logging threshold to 20 for consistency errors between software and hardware forwarding entries.

<Sysname> system-view

[Sysname] parity-error consistency-check threshold 20

Related commands

parity-error consistency-check log enable

parity-error consistency-check period

parity-error monitor log enable

Use parity-error monitor log enable to enable parity error logging for entries on forwarding chips.

Use undo parity-error monitor log enable to disable parity error logging for entries on forwarding chips.

Syntax

parity-error monitor log enable

undo parity-error monitor log enable

Default

Parity error logging is disabled for entries on forwarding chips.

Views

System view

Predefined user roles

network-admin

Usage guidelines

The device detects parity errors in entries on forwarding chips. The parity error logging feature collects parity error statistics periodically and generates log messages as defined.

Examples

# Enable parity error logging for entries on forwarding chips.

<Sysname> system-view

[Sysname] parity-error monitor log enable

Related commands

parity-error monitor period

parity-error monitor threshold

parity-error monitor period

Use parity-error monitor period to set the parity error statistics period for entries on forwarding chips.

Use undo parity-error monitor period to restore the default.

Syntax

parity-error monitor period value

undo parity-error monitor period

Default

The parity error statistics period is 60 seconds for entries on forwarding chips.

Views

System view

Parameters

value: Specifies the parity error statistics period in seconds, in the range of 1 to 86400.

Predefined user roles

network-admin

Usage guidelines

The device detects parity errors in entries on forwarding chips. The parity error logging feature collects parity error statistics periodically. This command sets the statistics period.

Examples

# Set the parity error statistics period to 120 seconds.

<Sysname> system-view

[Sysname] parity-error monitor period 120

Related commands

parity-error monitor log enable

parity-error monitor threshold

Use parity-error monitor threshold to set the parity error logging threshold for entries on forwarding chips.

Use undo parity-error monitor threshold to restore the default.

Syntax

parity-error monitor threshold value

undo parity-error monitor threshold

Default

The parity error logging threshold is 5000 for entries on forwarding chips.

Views

System view

Parameters

value: Specifies the parity error logging threshold for entries on forwarding chips, in the range of 1 to 1000000.

Predefined user roles

network-admin

Usage guidelines

The device detects parity errors in entries on forwarding chips. The parity error logging feature collects parity error statistics periodically, and generates a log message if the number of parity errors exceeds the logging threshold. This command sets the logging threshold.

Examples

# Set the parity error logging threshold to 8000 for entries on forwarding chips.

<Sysname> system-view

[Sysname] parity-error monitor threshold 8000

Related commands

parity-error monitor log enable

parity-error monitor period

password-recovery enable

Use password-recovery enable to enable password recovery capability.

Use undo password-recovery enable to disable password recovery capability.

Syntax

password-recovery enable

undo password-recovery enable

Default

Password recovery capability is enabled.

Views

System view

Predefined user roles

network-admin

Usage guidelines

Password recovery capability controls console user access to the device configuration and SDRAM from BootWare menus.

If password recovery capability is enabled, a console user can access the device configuration without authentication to configure new passwords.

If password recovery capability is disabled, console users must restore the factory-default configuration before they can configure new passwords. Restoring the factory-default configuration deletes the next-startup configuration files.

To enhance system security, disable password recovery capability.

Availability of BootWare menu options depends on the password recovery capability setting. For more information, see the release notes.

Examples

# Disable password recovery capability.

<Sysname> system-view

[Sysname] undo password-recovery enable

reboot

Use reboot to reboot the device.

Syntax

reboot [ slot slot-number [ subslot subslot-number ] ] [ force ]

Views

User view

Predefined user roles

network-admin

Parameters

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

force: Reboots the device immediately without performing software or hard disk check. If this keyword is not specified, the system first identifies whether the reboot might result in data loss or a system failure. For example, the system identifies whether the main system software image file exists and whether a write operation is in progress on a storage medium. If the reboot might cause problems, the system does not reboot the device.

Usage guidelines

CAUTION:

· A reboot might interrupt network services.

· Use the force keyword only when the device fails or a reboot command without the force keyword cannot perform a reboot correctly. A reboot command with the force keyword might result in file system corruption because it does not perform data protection.

‌

If the main startup software images are corrupt or missing, you must re-specify a set of main startup software images before executing the reboot command.

For data security, the device does not reboot if you reboot the device while the device is performing file operations.

Examples

# Reboot the device. Save the running configuration at prompt.

<Sysname> reboot

Start to check configuration with next startup configuration file, please wait.........DONE!

Current configuration will be lost after the reboot, save current configuration? [Y/N]:y

Please input the file name(*.cfg)[flash:/startup.cfg]

(To leave the existing filename unchanged, press the enter key):

flash:/startup.cfg exists, overwrite? [Y/N]:y

Validating file. Please wait...

Configuration is saved to mainboard device successfully.

This command will reboot the device. Continue? [Y/N]:y

Now rebooting, please wait...

# Reboot the device immediately without performing software check.

<Sysname> reboot force

A forced reboot might cause the storage medium to be corrupted. Continue? [Y/N]:y

Now rebooting, please wait...

Related commands

display system stable state

reset scheduler logfile

Use reset scheduler logfile to clear job execution log information.

Syntax

reset scheduler logfile

Views

User view

Predefined user roles

network-admin

Examples

# Clear job execution log information.

<Sysname> reset scheduler logfile

Related commands

display scheduler logfile

reset transceiver interface

Use reset transceiver interface to reset 400-GE transceiver modules.

NOTE:

This command is supported only in Release 6635 and later.

Syntax

reset transceiver interface [ interface-type interface-number ]

Views

User view

Predefined user roles

network-admin

Parameters

interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface, this command applies to all interfaces.

Usage guidelines

This command is disruptive. Use this command only when you cannot troubleshoot transceiver modules by using other methods.

This command will restart transceiver modules.

Examples

# Reset the 400-GE transceiver module in interface FourHundredGigE 1/1/1.

<Sysname> reset transceiver interface fourhundredgige 1/1/1

This operation causes services on the transceiver module to be down for a while. Continue? [Y/N]: Y

reset version-update-record

Use reset version-update-record to clear startup software image upgrade records.

Syntax

reset version-update-record

Views

System view

Predefined user roles

network-admin

Examples

# Clear the startup software image upgrade records.

<Sysname> system-view

[Sysname] reset version-update-record

This command will delete all records of version update. Continue? [Y/N]:y

Related commands

display version-update-record

resource-monitor minor resend enable

Use resource-monitor minor resend enable to enable resending of minor resource depletion alarms.

Use undo resource-monitor minor resend enable to disable resending of minor resource depletion alarms.

Syntax

resource-monitor minor resend enable

undo resource-monitor minor resend enable

Default

Resending of minor resource depletion alarms is enabled.

Views

System view

Predefined user roles

network-admin

Usage guidelines

When a resource type enters minor alarm state, the device issues a minor alarm. If the resource type stays in minor alarm state or changes from severe alarm state to minor alarm state, the device identifies whether resending of minor resource depletion alarms is enabled. If the feature is disabled, the device does not issue additional minor alarms. If the feature is enabled, the device resends minor alarms periodically.

The resending period is fixed at 24 hours for a severe alarm and is fixed at 7 * 24 hours for a minor alarm.

Examples

# Enable resending of minor resource depletion alarms.

<Sysname> system-view

[Sysname] resource-monitor minor resend enable

Related commands

display resource-monitor

resource-monitor output

resource-monitor resource

resource-monitor output

Use resource-monitor output to specify destinations for resource depletion alarms.

Use undo resource-monitor output to remove destinations for resource depletion alarms.

Syntax

resource-monitor output { netconf-event | snmp-notification | syslog } *

undo resource-monitor output [ netconf-event | snmp-notification | syslog ] *

Default

Resource depletion alarms are sent to NETCONF, SNMP, and the information center.

Views

System view

Predefined user roles

network-admin

Parameters

netconf-event: Sends resource depletion alarms to the NETCONF feature to encapsulate the alarms in NETCONF events. For more information, see NETCONF in Network Management and Monitoring Configuration Guide.

snmp-notification: Sends resource depletion alarms to the SNMP feature to encapsulate the alarms in SNMP traps and informs. For more information, see SNMP in Network Management and Monitoring Configuration Guide.

syslog: Sends resource depletion alarms to the information center to encapsulate the alarms in log messages. For more information, see information center in Network Management and Monitoring Configuration Guide.

Usage guidelines

If you do not specify any keywords for the undo resource-monitor output command, the command disables resource depletion alarm output.

Examples

# Specify the information center module as the output destination for resource depletion alarms.

<Sysname> system-view

[Sysname] resource-monitor output syslog

Related commands

resource-monitor minor resend enable

resource-monitor resource

Use resource-monitor resource to set resource depletion thresholds.

Use undo resource-monitor resource to disable resource depletion thresholds.

Syntax

resource-monitor resource resource-name slot slot-number cpu cpu-number by-percent minor-threshold minor-threshold severe-threshold severe-threshold

undo resource-monitor resource resource-name slot slot-number cpu cpu-number

Default

The default settings vary by resource type. Use the display resource-monitor command to display the resource depletion thresholds.

Views

System view

Predefined user roles

network-admin

Parameters

resource-name: Specifies a resource type by its name. The values for this argument are case insensitive and cannot be abbreviated. Table 23 shows the resource types that can be monitored.

Table 23 Resource types that can be monitored

Resource type	Description
agg_group	Aggregation group resources.
arp	ARP resources.
ecmpgroup	ECMP group resources.
ecmpgroup_overlay	ECMP group resources on the overlay network.
g_rsvd_vlan	Reserved global VLAN interface resources.
ipv6_127	Resources for IPv6 routes with a prefix length of 65 to 127 bits. NOTE: The device does not support monitoring these resources.
ipv6_128	Resources for IPv6 routes with a prefix length of 128 bits. NOTE: The device does not support monitoring these resources.
ipv6_64	Resources for IPv6 routes with a prefix length of 0 to 64 bits. NOTE: The device does not support monitoring these resources.
mac	MAC address table resources.
mqcin	Inbound MQC resources.
mqcin_c0_p0	Inbound MQC resources of Pipe 0 on Chip 0.
mqcin_c0_p1	Inbound MQC resources of Pipe 1 on Chip 0.
mqcin_c0_p2	Inbound MQC resources of Pipe 2 on Chip 0.
mqcin_c0_p3	Inbound MQC resources of Pipe 3 on Chip 0.
mqcin_c0_p4	Inbound MQC resources of Pipe 4 on Chip 0.
mqcin_c0_p5	Inbound MQC resources of Pipe 5 on Chip 0.
mqcin_c0_p6	Inbound MQC resources of Pipe 6 on Chip 0.
mqcin_c0_p7	Inbound MQC resources of Pipe 7 on Chip 0.
mqcout	Outbound MQC resources.
mqcout_c0	Outbound MQC resources on Chip 0.
nd	ND resources.
nexthoppool1	Next-hop pool resources for the underlay network.
nexthoppool2	Next-hop pool resources for the overlay network.
nexthoppool3	Layer 3 ECMP resource pool.
nexthoppool4	Layer 3 ECMP resource pool on the overlay network.
openflow	OpenFlow resources.
openflowin_c0_p0	OpenFlow resources of Pipe 0 on Chip 0.
openflowin_c0_p1	OpenFlow resources of Pipe 1 on Chip 0.
openflowin_c0_p2	OpenFlow resources of Pipe 2 on Chip 0.
openflowin_c0_p3	OpenFlow resources of Pipe 3 on Chip 0.
openflowin_c0_p4	OpenFlow resources of Pipe 4 on Chip 0.
openflowin_c0_p5	OpenFlow resources of Pipe 5 on Chip 0.
openflowin_c0_p6	OpenFlow resources of Pipe 6 on Chip 0.
openflowin_c0_p7	OpenFlow resources of Pipe 7 on Chip 0.
pbr	PBR resources.
pbrin_c0_p0	PBR resources of Pipe 0 on Chip 0.
pbrin_c0_p1	PBR resources of Pipe 1 on Chip 0.
pbrin_c0_p2	PBR resources of Pipe 2 on Chip 0.
pbrin_c0_p3	PBR resources of Pipe 3 on Chip 0.
pbrin_c0_p4	PBR resources of Pipe 4 on Chip 0.
pbrin_c0_p5	PBR resources of Pipe 5 on Chip 0.
pbrin_c0_p6	PBR resources of Pipe 6 on Chip 0.
pbrin_c0_p7	PBR resources of Pipe 7 on Chip 0.
pfilterin	Inbound packet filter resources.
pfilterin_c0_p0	Inbound packet filter resources of Pipe 0 on Chip 0.
pfilterin_c0_p1	Inbound packet filter resources of Pipe 1 on Chip 0.
pfilterin_c0_p2	Inbound packet filter resources of Pipe 2 on Chip 0.
pfilterin_c0_p3	Inbound packet filter resources of Pipe 3 on Chip 0.
pfilterin_c0_p4	Inbound packet filter resources of Pipe 4 on Chip 0.
pfilterin_c0_p5	Inbound packet filter resources of Pipe 5 on Chip 0.
pfilterin_c0_p6	Inbound packet filter resources of Pipe 6 on Chip 0.
pfilterin_c0_p7	Inbound packet filter resources of Pipe 7 on Chip 0.
pfilterout	Outbound packet filter resources.
pfilterout_c0	Outbound packet filter resources on Chip 0.
route	Routing resources. NOTE: The device does not support monitoring these resources.
rport	Layer 3 Ethernet interface resources.
subrport	Layer 3 Ethernet subinterface resources.
vlaninterface	VLAN interface resources.
vrf	VPN instance resources.

‌

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

cpu cpu-number: Specifies a CPU by its number, which is fixed at 0.

by-percent: Specifies resource depletion thresholds in percentage.

minor-threshold minor-threshold: Specifies the minor resource depletion threshold. To view the value range, enter a question mark (?) in the place of the minor-threshold argument.

severe-threshold severe-threshold: Specifies the severe resource depletion threshold. To view the value range, enter a question mark (?) in the place of the severe-threshold argument.

Usage guidelines

After you execute this command for a resource type, the device monitors the available amount of the type of resources. The device samples the available amount at intervals, compares the sample with the resource depletion thresholds to identify the resource depletion status, and sends alarms as configured.

Examples

# Set the minor resource depletion threshold to 30% and the severe resource depletion threshold to 10% for ARP entry resources on slot 1.

<Sysname> system-view

[Sysname] resource-monitor resource arp slot 1 cpu 0 by-percent minor-threshold 30 severe-threshold 10

Related commands

display resource-monitor

resource-monitor minor resend enable

resource-monitor output

restore factory-default

Use restore factory-default to restore the factory-default configuration for the device.

Syntax

restore factory-default

Views

User view

Predefined user roles

network-admin

Usage guidelines

CAUTION:

This command restores the device to the factory default settings. Before executing this command, make sure you understand its impact on the live network.

‌

Use this command only when you cannot troubleshoot the device by using other methods, or you want to use the device in a different scenario.

Examples

# Restore the factory-default configuration for the device.

<Sysname> restore factory-default

This command will restore the system to the factory default configuration and clear the operation data. Continue [Y/N]:y

Restoring the factory default configuration. This process might take a few minutes. Please wait..........................................................................................................Done.

Please reboot the system to place the factory default configuration into effect.

Related commands

reboot

scheduler job

Use scheduler job to create a job and enter its view, or enter the view of an existing job.

Use undo scheduler job to delete a job.

Syntax

scheduler job job-name

undo scheduler job job-name

Default

No job exists.

Views

System view

Predefined user roles

network-admin

Parameters

job-name: Specifies the job name, a case-sensitive string of 1 to 47 characters.

Usage guidelines

A job can be referenced by multiple schedules. In job view, you can assign commands to the job.

Examples

# Create a job named backupconfig and enter job view.

<Sysname> system-view

[Sysname] scheduler job backupconfig

[Sysname-job-backupconfig]

Related commands

command

scheduler schedule

scheduler logfile size

Use scheduler logfile size to set the size of the job execution log file.

Syntax

scheduler logfile size value

Default

The size of the job execution log file is 16 KB.

Views

System view

Predefined user roles

network-admin

Parameters

value: Specifies the size of the job execution log file, in KB. The value range is 16 to 1024.

Usage guidelines

The job execution log file saves the execution information of jobs. If the file is full, old records are deleted to make room for new records. If the size of the log information to be written to the file is greater than the file size, the excessive information is not written to the file.

Examples

# Set the size of the job execution log file to 32 KB.

<Sysname> system-view

[Sysname] scheduler logfile size 32

Related commands

display scheduler logfile

scheduler reboot at

Use scheduler reboot at to specify the reboot date and time.

Use undo scheduler reboot to delete the reboot schedule configuration.

Syntax

scheduler reboot at time [ date ]

undo scheduler reboot

Default

No reboot date or time is specified.

Views

User view

Predefined user roles

network-admin

Parameters

time: Specifies the reboot time in the hh:mm format. The value range for hh is 0 to 23. The value range for mm is 0 to 59.

date: Specifies the reboot date in the MM/DD/YYYY or YYYY/MM/DD format. The value range for YYYY is 2000 to 2035. The value range for MM is 1 to 12. The value range for DD varies by month.

Usage guidelines

CAUTION:

This command enables the device to reboot at a scheduled time, which causes service interruption. Before using this command, make sure you fully understand its impact on your live network.

‌

When the date argument is not specified, the system uses the following rules to determine the reboot time:

· If the reboot time is later than the current time, a reboot occurs at the reboot time of the current day.

· If the reboot time is earlier than the current time, a reboot occurs at the reboot time the next day.

The device supports only one device reboot schedule. If you execute both the scheduler reboot delay and scheduler reboot at commands or execute one of the commands multiple times, the most recent configuration takes effect.

For data security, the system does not reboot at the reboot time if a file operation is being performed.

Examples

# Configure the device to reboot at 12:00 p.m. This example assumes that the current time is 11:43 a.m. on June 6, 2015.

<Sysname> scheduler reboot at 12:00

Reboot system at 12:00:00 06/06/2015 (in 0 hours and 16 minutes). Confirm? [Y/N]:

Related commands

scheduler reboot delay

Use scheduler reboot delay to specify the reboot delay time.

Use undo scheduler reboot to delete the reboot schedule configuration.

Syntax

scheduler reboot delay time

undo scheduler reboot

Default

No reboot delay time is specified.

Views

User view

Predefined user roles

network-admin

Parameters

time: Specifies the reboot delay time in the hh:mm or mm format. This argument can contain up to six characters. When in the hh:mm format, mm must be in the range of 0 to 59.

Usage guidelines

CAUTION:

Device reboot interrupts network services.

‌

The device supports only one device reboot schedule. If you execute both the scheduler reboot delay and schedule reboot at commands or execute one of the commands multiple times, the most recent configuration takes effect.

For data security, the system does not reboot at the reboot time if a file operation is being performed.

Examples

# Configure the device to reboot after 88 minutes. This example assumes that the current time is 11:48 a.m. on June 6, 2015.

<Sysname> scheduler reboot delay 88

Reboot system at 13:16 06/06/2015(in 1 hours and 28 minutes). Confirm? [Y/N]:

scheduler schedule

Use scheduler schedule to create a schedule and enter its view, or enter the view of an existing schedule.

Use undo scheduler schedule to delete a schedule.

Syntax

scheduler schedule schedule-name

undo scheduler schedule schedule-name

Default

No schedule exists.

Views

System view

Predefined user roles

network-admin

Parameters

schedule-name: Specifies the schedule name, a case-sensitive string of 1 to 47 characters.

Usage guidelines

You can configure a schedule to have the device automatically run a command or a set of commands without administrative interference.

To configure a schedule:

1. Use the scheduler job command to create a job and enter job view.

2. Use the command command to assign commands to the job.

3. Use the scheduler schedule command to create a schedule and enter schedule view.

4. Use the job command to assign the job to the schedule. You can assign multiple jobs to a schedule. The jobs must already exist.

5. Use the user-role command to assign user roles to the schedule. You can assign up to 64 user roles to a schedule.

6. Use the time at, time once, or time repeating command to specify an execution time for the schedule. You can specify only one execution time for a schedule.

Examples

# Create a schedule named saveconfig.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

Related commands

job

time at

time once

shutdown-interval

Use shutdown-interval to set the port status detection timer.

Use undo shutdown-interval to restore the default.

Syntax

shutdown-interval interval

undo shutdown-interval

Default

The port status detection timer setting is 30 seconds.

Views

System view

Predefined user roles

network-admin

Parameters

interval: Specifies the port status detection timer value in seconds. The value range is 0 to 300. If you set this argument to 0, automatic port status detection is disabled, and you need to manually bring up a port.

Usage guidelines

The device starts a port status detection timer when a port is shut down by a protocol. Once the timer expires, the device brings up the port so the port status reflects the port's physical status.

If you change the timer setting during port detection, the device compares the new setting (T1) with the time that elapsed since the port was shut down (T).

If T < T1, the port will be brought up after T1 – T seconds.

If T ≥ T1, the port is brought up immediately.

For example, the timer setting is 30 seconds. If you change it to 10 seconds 2 seconds after the port is shut down, the port will come up 8 seconds later. If you change the timer setting to 2 seconds 10 seconds after the port is shut down, the port comes up immediately.

Examples

# Set the port status detection timer to 100 seconds.

<Sysname> system-view

[Sysname] shutdown-interval 100

sysname

Use sysname to set the device name.

Use undo sysname to restore the default.

Syntax

sysname sysname

undo sysname

Default

The device name is H3C.

Views

System view

Predefined user roles

network-admin

Parameters

sysname: Specifies a name for the device, a string of 1 to 64 characters.

Usage guidelines

A device name identifies a device in a network and is used in CLI view prompts. For example, if the device name is Sysname, the user view prompt is <Sysname>.

Examples

# Set the name of the device to R2000.

<Sysname> system-view

[Sysname] sysname R2000

[R2000]

system-working-mode

Use system-working-mode to set the system operating mode.

Use undo system-working-mode to restore the default.

Syntax

system-working-mode { advance | standard }

undo system-working-mode

Default

The device operates in standard mode.

Views

System view

Predefined user roles

network-admin

Parameters

advance: Sets the system operating mode to advanced.

standard: Sets the system operating mode to standard.

Usage guidelines

The system operating mode determines the supported features and the feature specifications. For more information, see device management in Fundamentals Configuration Guide.

Change to the operating mode takes effect after a reboot.

Examples

# Set the system operating mode to advanced.

<Sysname> system-view

[Sysname] system-working-mode advance

Do you want to change the system working mode? [Y/N]:y

System working mode changed. For the change to take effect, save the running configuration and reboot the device.

temperature-limit

Use temperature-limit to set the temperature alarm thresholds.

Use undo temperature-limit to restore the default.

Syntax

temperature-limit slot slot-number { hotspot | inflow | outflow } sensor-number lowlimit warninglimit [ alarmlimit ]

undo temperature-limit slot slot-number { hotspot | inflow | outflow } sensor-number

Default

The defaults vary by temperature sensor model. To view the defaults, execute the undo temperature-limit and display environment commands in turn.

Views

System view

Predefined user roles

network-admin

Parameters

slot slot-number: Specifies the slot number of the device, which is fixed at 1.

hotspot: Configures temperature alarm thresholds for hotspot sensors. A hotspot sensor is typically located near a high-heat chip to monitor the chip temperature.

inflow: Configures temperature alarm thresholds for inlet sensors. An inflow sensor is located near an air inlet to monitor the ambient temperature.

outflow: Configures temperature alarm thresholds for outlet sensors. An outflow sensor is located near an air outlet to monitor the device temperature.

sensor-number: Specifies a sensor by its number. To view the value range, enter a question mark (?) in the place of this argument.

lowlimit: Specifies the low-temperature threshold in Celsius degrees. The value range varies by temperature sensor. To view the value range, enter a question mark (?) in the place of this argument.

warninglimit: Specifies the high-temperature warning threshold in Celsius degrees. This threshold must be greater than the low-temperature threshold. To view the value range, enter a question mark (?) in the place of this argument.

alarmlimit: Specifies the high-temperature alarming threshold in Celsius degrees. This threshold must be greater than the warning threshold. To view the value range, enter a question mark (?) in the place of this argument.

Usage guidelines

When the device temperature drops below the low-temperature threshold or reaches the high-temperature warning or alarming threshold, the device performs the following operations:

· Sends log messages and traps.

· Sets LEDs on the device panel.

Examples

# Set temperature alarm thresholds for hotspot sensor 1 in a slot.

<Sysname> system-view

[Sysname] temperature-limit slot 1 hotspot 1 -10 50 60

Related commands

display environment

time at

Use time at to specify an execution date and time for a non-periodic schedule.

Use undo time to delete the execution date and time configuration for a non-periodic schedule.

Syntax

time at time date

undo time

Default

No execution time or date is specified for a non-periodic schedule.

Views

Schedule view

Predefined user roles

network-admin

Parameters

time: Specifies the schedule execution time in the hh:mm format. The value range for hh is 0 to 23. The value range for mm is 0 to 59.

date: Specifies the schedule execution date in the MM/DD/YYYY or YYYY/MM/DD format. The value range for YYYY is 2000 to 2035. The value range for MM is 1 to 12. The value range for DD varies by month.

Usage guidelines

The specified time (date plus time) must be later than the current system time.

The time at command, the time once command, and the time repeating command overwrite one another. The most recently executed command takes effect.

Examples

# Configure the device to execute schedule saveconfig at 01:01 a.m. on May 11, 2015.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] time at 1:1 2015/05/11

Related commands

scheduler schedule

time once

Use time once to specify one or more execution days and the execution time for a non-periodic schedule.

Use undo time to delete the execution day and time configuration for a non-periodic schedule.

Syntax

time once at time [ month-date month-day | week-day week-day&<1-7> ]

time once delay time

undo time

Default

No execution time or day is specified for a non-periodic schedule.

Views

Schedule view

Predefined user roles

network-admin

Parameters

at time: Specifies the execution time in the hh:mm format. The value range for hh is 0 to 23. The value range for mm is 0 to 59.

month-date month-day: Specifies a day in the current month, in the range of 1 to 31. If you specify a day that does not exist in the current month, the configuration takes effect on that day in the next month.

week-day week-day&<1-7>: Specifies a space-separated list of up to seven week days for the schedule. Valid week day values include Mon, Tue, Wed, Thu, Fri, Sat, and Sun.

delay time: Specifies the delay time for executing the schedule, in the hh:mm or mm format. This argument can have up to six characters. When in the hh:mm format, mm must be in the range of 0 to 59.

Usage guidelines

If the specified time has already occurred, the schedule will be executed at the specified time the following day.

If the day in the month has already occurred, the schedule will be executed at the specified day in the following month.

If the specified day in a week has already occurred, the schedule will be executed at the specified day in the following week.

The time at command, the time once command, and the time repeating command overwrite one another. The most recently executed command takes effect.

Examples

# Configure the device to execute schedule saveconfig once at 15:00.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] time once at 15:00

Schedule starts at 15:00 5/11/2011.

# Configure the device to execute schedule saveconfig once at 15:00 on the coming 15th day in a month.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] time once at 15:00 month-date 15

# Configure the device to execute schedule saveconfig at 12:00 p.m. on the coming Monday and Friday.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] time once at 12:00 week-day mon fri

# Configure the device to execute schedule saveconfig after 10 minutes.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] time once delay 10

Related commands

scheduler schedule

time repeating

Use time repeating to specify an execution time table for a periodic schedule.

Use undo time to delete the execution time table configuration for a periodic schedule.

Syntax

time repeating [ at time [ date ] ] interval interval

time repeating at time [ month-date [ month-day | last ] | week-day week-day&<1-7> ]

undo time

Default

No execution time table is specified for a periodic schedule.

Views

Schedule view

Predefined user roles

network-admin

Parameters

at time: Specifies the execution time in the hh:mm format. The value range for hh is 0 to 23. The value range for mm is 0 to 59. If you do not specify this option, the current system time is used as the execution time.

date: Specifies the start date for the periodic schedule, in the MM/DD/YYYY or YYYY/MM/DD format. The value range for YYYY is 2000 to 2035. The value range for MM is 1 to 12. The value range for DD varies by month. If you do not specify this argument, the execution start date is the first day when the specified time arrives.

interval interval: Specifies the execution time interval in the hh:mm or mm format. This argument can have up to six characters. When in the hh:mm format, mm must be in the range of 0 to 59. When in the mm format, this argument must be equal to or greater than 1 minute.

month-date [ month-day | last ]: Specifies a day in a month, in the range 1 to 31. The last keyword indicates the last day of a month. If you specify a day that does not exist in a month, the configuration takes effect on that day in the next month.

week-day week-day&<1-7>: Specifies a space-separated list of up to seven week days for the schedule. Valid week day values include Mon, Tue, Wed, Thu, Fri, Sat, and Sun.

Usage guidelines

The time repeating [ at time [ date ] ] interval interval command configures the device to execute a schedule at intervals from the specified time on.

The time repeating at time [ month-date [ month-day | last ] | week-day week-day&<1-7> ] command configures the device to execute a schedule at the specified time on every specified day in a month or week.

The time at command, the time once command, and the time repeating command overwrite one another, whichever is executed most recently takes effect.

Examples

# Configure the device to execute schedule saveconfig once an hour from 8:00 a.m. on.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] time repeating at 8:00 interval 60

# Configure the device to execute schedule saveconfig at 12:00 p.m. every day.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] time repeating at 12:00

# Configure the device to execute schedule saveconfig at 8:00 a.m. on the 5th of every month.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] time repeating at 8:00 month-date 5

# Configure the device to execute schedule saveconfig at 8:00 a.m. on the last day of every month.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] time repeating at 8:00 month-date last

# Configure the device to execute schedule saveconfig at 8:00 a.m. every Friday and Saturday.

<Sysname> system-view

[Sysname] scheduler schedule saveconfig

[Sysname-schedule-saveconfig] time repeating at 8:00 week-day fri sat

Related commands

scheduler schedule

transceiver diagnostic selector

Use transceiver diagnostic selector to specify a diagnostic selector for a transceiver module and display specified diagnostic information.

NOTE:

This command is supported only in Release 6635 and later.

Syntax

transceiver diagnostic selector selector-id

Default

No diagnostic selector is specified for a transceiver module.

Views

400GE interface view

Predefined user roles

network-admin

Parameters

selector-id: Specifies a diagnostic selector. The value range varies by transceiver module model.

Usage guidelines

This command is available only for 400G transceiver modules that support CMIS 4.0.

The command settings will be saved in a register of the transceiver module. If the transceiver module has a power loss, the command settings will be cleared. You must re-execute the command after a power recovery.

Examples

# Specify diagnostic selector 1 for the transceiver module in FourHundredGigE 1/1/1 and display specified diagnostic information.

<Sysname> system-view

[Sysname] interface fourhundredgige 1/1/1

[Sysname-FourHundredGigE1/1/1] transceiver diagnostic selector 1

Lane Host side BER Media side BER

Lane1 1.00E-7 1.00E-7

Lane2 1.00E-7 1.00E-7

Lane3 1.00E-7 1.00E-7

Lane4 1.00E-7 1.00E-7

Lane5 1.00E-7 1.00E-7

Lane6 1.00E-7 1.00E-7

Lane7 1.00E-7 1.00E-7

Lane8 1.00E-7 1.00E-7

# Specify diagnostic selector 2 for the transceiver module in FourHundredGigE 1/1/1 and display specified diagnostic information.

<Sysname> system-view

[Sysname] interface fourhundredgige 1/1/1

[Sysname-FourHundredGigE1/1/1] transceiver diagnostic selector 2

Lane Host error count Host total bits

Lane1 1234567890 1234567890123456789

Lane2 1234567890 1234567890123456789

Lane3 1234567890 1234567890123456789

Lane4 1234567890 1234567890123456789

# Specify diagnostic selector 6 for the transceiver module in FourHundredGigE 1/1/1 and display specified diagnostic information.

<Sysname> system-view

[Sysname] interface fourhundredgige 1/1/1

[Sysname-FourHundredGigE1/1/1] transceiver diagnostic selector 6

Lane Host peak detect Host SNR Media peak detect Media SNR

Lane1 12345 18.00dB 12345 18.00dB

Lane2 12345 18.00dB 12345 18.00dB

Lane3 12345 18.00dB 12345 18.00dB

Lane4 12345 18.00dB 12345 18.00dB

Lane5 12345 18.00dB 12345 18.00dB

Lane6 12345 18.00dB 12345 18.00dB

Lane7 12345 18.00dB 12345 18.00dB

Lane8 12345 18.00dB 12345 18.00dB

transceiver lane enable

Use transceiver lane enable to enable lanes on a 400-GE transceiver module.

Use undo transceiver lane to disable lanes on a 400-GE transceiver module.

NOTE:

This command is supported only in Release 6635 and later.

Syntax

transceiver lane [ lane-number ] enable

undo transceiver lane [ lane-number ] enable

Default

All lanes on a transceiver module are enabled.

Views

400-GE Ethernet interface view and its breakout interface view

Predefined user roles

network-admin

Parameters

lane-number: Specifies a lane by its number in the range of 1 to 8. If you do not specify a lane, this command enables all lanes on the transceiver module.

Usage guidelines

Execute this command only for transceiver module debugging or testing.

Disabling a lane will stop signal transmission on the lane.

Disabling a lane will stop signal transmission on the fiber port where the lane is located.

The lane enablement setting is saved in a register on the transceiver module. It is not saved to the configuration file.

Examples

# Enable lane 1 on the 400-GE transceiver module in interface FourHundredGigE 1/1/1.

<Sysname> system-view

[Sysname] interface fourhundredgige 1/1/1

[Sysname-FourHundredGigE1/1/1] transceiver lane 1 enable

Related commands

display transceiver status

transceiver lane equalization

Use transceiver lane equalization to configure the pre-cursor and post-cursor equalizers, and amplitude for a 400-GE transceiver module.

Use undo transceiver lane equalization to restore the default.

NOTE:

This command is supported only in Release 6635 and later.

Syntax

transceiver lane [ lane-number ] equalization { precursor precursor-value | postcursor postcursor-value | amplitude amplitude-value }

undo transceiver lane [ lane-number ] equalization { precursor | postcursor | amplitude }

Default

The default settings vary by transceiver module model.

Views

400-GE Ethernet interface view and its breakout interface view

Predefined user roles

network-admin

Parameters

lane-number: Specifies a lane by its number in the range of 1 to 8. If you do not specify a lane, this command configures the settings for all lanes on the transceiver module.

precursor precursor-value: Specifies the code value of the pre-cursor. The following shows all code values:

· level0—No equalization.

· level1—0.5 dB.

· level2—1 dB.

· level3—1.5 dB.

· level4—2 dB.

· level5—2.5 dB.

· level6—3 dB.

· level7—3.5 dB.

postcursor postcursor-value: Specifies the code value of the post-cursor. The following shows all code values:

· level0—No equalization.

· level1—1 dB.

· level2—2 dB.

· level3—3 dB.

· level4—4 dB.

· level5—5 dB.

· level6—6 dB.

· level7—7 dB.

amplitude amplitude-value: Specifies the code value of the amplitude. The following shows all code values:

· range0—100 to 400 mV.

· range1—300 to 600 mV.

· range2—400 to 800 mV.

· Range3—600 to 1200 mV.

Usage guidelines

Execute this command for debugging and testing on high speed signals to achieve optimal link status. The default settings are generally applied. To change the default settings, contact professional engineers to avoid transceiver module exceptions.

As a best practice, do not execute this command when the interface is transmitting traffic. This command enables the device to automatically disable and then enable the transceiver module, which affects traffic transmission.

The configuration by this command is saved in a register on the transceiver module. It is not saved to the configuration file.

Examples

# Configure the pre-cursor and post-cursor equalizers, and amplitude for the 400-GE transceiver module in interface FourHundredGigE 1/1/1.

<Sysname> system-view

[Sysname] interface fourhundredgige 1/1/1

[Sysname-FourHundredGigE1/1/1] transceiver lane 1 equalization pre-cursor 1 post-cursor 8 amplitude 3

This operation will shut down and then bring up the transceiver module, affecting data transmission. Continue? [Y/N]:Y

Related commands

display transceiver active-control

transceiver lane loopback

Use transceiver lane loopback to enable loopback testing on a transceiver module lane and specify a loopback testing mode.

Use undo transceiver lane loopback to restore the default.

NOTE:

This command is supported only in Release 6635 and later.

Syntax

transceiver lane [ lane-number ] loopback loopback-mode

undo transceiver lane [ lane-number ] loopback loopback-mode

Default

Loopback testing is disabled for transceiver module lanes.

Views

400GE interface view

Predefined user roles

network-admin

Parameters

lane-number: Specifies a lane by its number. The value is in the range of 1 to 8 for a 400G transceiver module. If you do not specify a lane, this command applies to all lanes of the transceiver module.

loopback-mode: Specifies a loopback testing mode.

· host-input: Loopbacks the signal from the transmitter of the host side to the receiver of the host side as the input signal of the host.

· host-output: Loopbacks the signal received by the receiver of the host side to the transmitter of the host side as the output signal of the host.

· media-input: Loopbacks the signal from the transmitter of the media side to the receiver of the media side as the input signal of the media.

· media-output: Loopbacks the signal received by the receiver of the media side to the transmitter of the media side as the output signal of the media.

Usage guidelines

This command is available only for 400G transceiver modules that support CMIS 4.0.

This command tests whether messages can be forwarded correctly between the designated transmitter and receiver and helps identify the point of failure when the transceiver module fails to forward messages.

Examples

# Enable loopback testing and specify a loopback testing mode for lanes of the transceiver module in FourHundredGigE 1/1/1.

<Sysname> system-view

[Sysname] interface fourhundredgige 1/1/1

[Sysname-FourHundredGigE1/1/1] transceiver lane loopback media-input

This operation causes the service to be down for a while. Continue? [Y/N]:Y

Related commands

transceiver lane pattern

Use transceiver lane pattern to configure the signal mode and signal transmission Pseudo Random Binary Sequence (PRBS) pattern for a transceiver module lane.

Use undo transceiver lane pattern to restore the default.

NOTE:

This command is supported only in Release 6635 and later.

Syntax

transceiver lane [ lane-number ] pattern [ host-checker | host-generator media-checker | media-generator ] prbs-pattern

undo transceiver lane [ lane-number ] pattern

Default

The default settings varies by transceiver module model.

Views

400GE interface view

Predefined user roles

network-admin

Parameters

host-checker: Specifies the host-side signal check mode.

host-generator: Specifies the host-side signal generation mode.

media-checker: Specifies the media-side signal check mode.

media-generator: Specifies the medial-side signal generation mode.

prbs-pattern: Specifies a signal transmission PRBS pattern. The value range varies by transceiver module model.

Usage guidelines

This command is available only for 400G transceiver modules that support CMIS 4.0.

This command settings will be saved in a register of the transceiver module. If the transceiver module has a power loss, the command settings will be cleared. You must re-execute the command after a power recovery.

Examples

# Specify the host-side signal generation mode and signal transmission pattern of PRBS-31Q for all lanes of the transceiver module in FourHundredGigE 1/1/1.

<Sysname> system-view

[Sysname] interface fourhundredgige 1/1/1

[Sysname-FourHundredGigE1/1/1] transceiver lane pattern host-generator PRBS-31Q

This operation causes the service to be down for a while. Continue? [Y/N]:Y

transceiver power-mode

Use transceiver power-mode to set a power mode for a 400-GE transceiver module.

Use undo transceiver power-mode to restore the default.

NOTE:

This command is supported only in Release 6635 and later.

Syntax

transceiver power-mode { high | low }

undo transceiver power-mode

Default

The default settings vary by transceiver module model.

Views

400-GE Ethernet interface view and its breakout interface view

Predefined user roles

network-admin

Usage guidelines

A transceiver module generally operates in high power mode. If the transceiver module does not work for a long time, you can switch the transceiver module to low power mode to reduce power consumption. In low power mode, the transceiver module does not transmit signals.

The power mode setting is saved in a register on the transceiver module. It is not saved to the configuration file.

Examples

# Set the 400-GE transceiver module in interface FourHundredGigE 1/1/1 to high power mode.

<Sysname> system-view

[Sysname] interface fourhundredgige 1/1/1

[Sysname-FourHundredGigE1/1/1] transceiver power-mode high

# Set the 400-GE transceiver module in interface FourHundredGigE 1/1/1 to low power mode.

<Sysname> system-view

[Sysname] interface fourhundredgige 1/1/1

[Sysname-FourHundredGigE1/1/1] transceiver power-mode low

This command will place the transceiver module in low-power-consumption mode, disabling the transceiver module from transmitting data. Continue? [Y/N]:Y

Related commands

display transceiver status

transceiver working-mode

Use transceiver working-mode to set an operating mode for a 400-GE transceiver module.

Use transceiver working-mode to restore the default.

NOTE:

This command is supported only in Release 6635 and later.

Syntax

transceiver working-mode working-mode

undo transceiver working-mode

Default

The default settings vary by transceiver module model.

Views

400-GE Ethernet interface view and its breakout interface view

Predefined user roles

network-admin

Parameters

working-mode: Specifies an operating mode in a case-insensitive string, such as 400G-SR8 and 200G-SR4.

Usage guidelines

For successful communication, two directly connected transceiver modules must be configured with the same operating mode.

The operating mode setting is saved in a register on the transceiver module. It is not saved to the configuration file.

Examples

# Set the operating mode to 400G-SR8 for the 400-GE transceiver module in interface FourHundredGigE 1/1/1.

<Sysname> system-view

[Sysname] interface fourhundredgige 1/1/1

[Sysname-FourHundredGigE1/1/1] transceiver working-mode 400G-SR8

This operation will shut down and then bring up the transceiver module, affecting data transmission. Continue? [Y/N]:Y

Related commands

display transceiver active-control

user-role

Use user-role to assign user roles to a schedule.

Use undo user-role to remove user roles from a schedule.

Syntax

user-role role-name

undo user-role role-name

Default

A schedule has the user roles of the schedule creator.

Views

Schedule view

Predefined user roles

network-admin

Parameters

role-name: Specifies a user role name, a case-sensitive string of 1 to 63 characters. The user role can be user-defined or predefined. Predefined user roles include network-admin, network-operator, and level-0 to level-15.

Usage guidelines

A schedule must have one or more user roles. A command in a schedule can be executed if it is permitted by one or more user roles of the schedule. For more information about user roles, see RBAC configuration in Fundamentals Configuration Guide.

A schedule can have a maximum of 64 user roles. After the limit is reached, you cannot assign additional user roles to the schedule.

Examples

# Assign user role rolename to schedule test.

<Sysname> system-view

[Sysname] scheduler schedule test

[Sysname-schedule-test] user-role rolename

Related commands

command

scheduler schedule

01-Fundamentals Command Reference

clock datetime

display copyright

display device manuinfo fan

display fan

display memory

display resource-monitor

display scheduler job

display system stable state

display version-update-record

job

memory-threshold usage

monitor cpu-usage interval

resource-monitor minor resend enable

resource-monitor resource

scheduler reboot at

sysname

system-working-mode

time once

transceiver diagnostic selector

Cloud & AI

InterConnect

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Resources

Partner Business Management

Company Information

News & Events

Contact Us