- Table of Contents
-
- 01-Fundamentals Command Reference
- 00-Preface
- 01-CLI commands
- 02-RBAC commands
- 03-Login management commands
- 04-FTP and TFTP commands
- 05-File system management commands
- 06-Configuration file management commands
- 07-Software upgrade commands
- 08-ISSU commands
- 09-Emergency shell commands
- 10-Target configuration management commands
- 11-Device management commands
- 12-Tcl commands
- 13-Python commands
- Related Documents
-
Title | Size | Download |
---|---|---|
11-Device management commands | 402.32 KB |
display cpu-usage configuration
display device manuinfo chassis-only
display device manuinfo power-tray
display diagnostic-information
display non-stop-routing status
display transceiver itu-channel
Device management commands
clock datetime
Use clock datetime to set the system time.
Syntax
clock datetime time date
Default
The system time is UTC time 00:00:00 01/01/2011.
Views
User view
Predefined user roles
network-admin
Parameters
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
This command is supported only on the default MDC.
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.
If you set the time zone or daylight saving time after you configure this command, the device recalculates the system time. To view the system time, use the display clock command.
Examples
# Set the system time to 08:08:08 01/01/2012.
<Sysname> clock datetime 8:8:8 1/1/2012
# Set the system time to 08:10:00 01/01/2012.
<Sysname> clock datetime 8:10 2012/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 } mdc mdc-id }
undo clock protocol
Default
The device obtains the UTC time from an NTP time source specified on the default MDC.
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.
mdc mdc-id: Specifies the MDC to be used for time synchronization. The value range is 1 to 8.
Usage guidelines
This command is supported only on the default MDC.
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.
· If you configure 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 configure 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.
The system time calculated by using the UTC time from an NTP or PTP time source is more precise.
If you execute this command multiple times, the most recent configuration takes effect.
If you set the time zone or daylight saving time after you configure this command, the device recalculates the system time. To view the system time, use the display clock command.
All MDCs on the device use the same system time. After obtaining the system time from an MDC, the device automatically synchronizes the system time to the other MDCs.
Examples
# Configure the device to use the local system 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
This command is supported only on the default MDC.
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 or local system time.
minus: Decreases the UTC time or local system time by an offset.
zone-offset: Specifies the offset 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
This command is supported only on the default MDC.
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 or local system 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
mdc-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 GigabitEthernet 1/2/0/1.
<Sysname> system-view
[Sysname] scheduler job shutdownGE
[Sysname-job-shutdownGE] command 1 system-view
[Sysname-job-shutdownGE] command 2 interface gigabitethernet 1/2/0/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
copyright-info enable
undo copyright-info enable
Default
Copyright statement display is enabled.
Views
System view
Predefined user roles
network-admin
mdc-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:
******************************************************************************
* Copyright (c) 2004-2017 New H3C Technologies Co., Ltd. All rights reserved.*
* Without the owner's prior written consent, *
* no decompiling or reverse-engineering shall be allowed. *
******************************************************************************
diagnostic counters reset
Use diagnostic counters reset to clear card or device statistics.
Syntax
diagnostic counters [ chassis chassis-number [ slot slot-number ] ] reset
Views
User view
Predefined user roles
network-admin
Parameters
chassis chassis-number: Specifies a member device in the cluster by its member ID. If you do not specify a member device, this command clears statistics on all member devices.
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command clears statistics on all cards.
Examples
# Clear statistics stored on a card.
<Sysname>diagnostic counters chassis 1 slot 2 reset
Parallel execution of this command causes errors. Please make sure this command is not being executed by other users. Continue? [Y/N]:y
Processing, please wait...Elapsed 0:0:9
Related commands
diagnostic counters save
diagnostic counters upload
diagnostic counters save
Use diagnostic counters save to collect and save card or device statistics.
Syntax
diagnostic counters [ chassis chassis-number [ slot slot-number ] ] save filename
Views
User view
Predefined user roles
network-admin
Parameters
chassis chassis-number: Specifies a member device in the cluster by its member ID. If you do not specify a member device, this command collects and saves statistics on all member devices.
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command collects and saves statistics on all cards.
filename: Saves the statistics to a file. The filename argument is a case-sensitive string that can have a maximum of 31 characters.
Examples
# Collect and save statistics on a card to the abc file.
<Sysname>diagnostic counters chassis 1 slot 2 save abc
Parallel execution of this command causes errors. Please make sure this command is not being executed by other users. Continue? [Y/N]:y
Processing, please wait...Elapsed 0:0:9
Related commands
diagnostic counters reset
diagnostic counters upload
diagnostic counters upload
Use diagnostic counters upload to collect and upload card or device statistics to a server.
Syntax
diagnostic counters [ chassis chassis-number [ slot slot-number ] ] upload { tftp server-ip | ftp server-ip username } filename
Views
User view
Predefined user roles
network-admin
Parameters
chassis chassis-number: Specifies a member device in the cluster by its member ID. If you do not specify a member device, this command collects and uploads statistics on all member devices.
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command collects and uploads statistics on all cards.
tftp server-ip: Specifies a TFTP server by its IP address.
ftp server-ip username: Specifies an FTP server by its IP address. The username argument is the username for logging in to the FTP server.
filename: Saves the statistics to a file. The filename argument is a case-sensitive string that can have a maximum of 31 characters.
Examples
# Collect and upload statistics on a card to the abc file on a server.
<Sysname>diagnostic counters chassis 1 slot 2 upload tftp 1.1.1.1 abc
Parallel execution of this command causes errors. Please make sure this command is not being executed by other users. Continue? [Y/N]:y
Processing, please wait...Elapsed 0:0:9
Related commands
diagnostic counters reset
diagnostic counters save
diagnostic keyinfo save
Use diagnostic keyinfo save to collect and save key card or device information.
Syntax
diagnostic keyinfo [ chassis chassis-number [ slot slot-number ] ] save filename
Views
User view
Predefined user roles
network-admin
Parameters
chassis chassis-number: Specifies a member device in the cluster by its member ID. If you do not specify a member device, this command collects and saves key information on all member devices.
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command collects and saves key information on all cards.
filename: Saves the key information to a file. The filename argument is a case-sensitive string that can have a maximum of 31 characters.
Examples
# Collect save key information for a card to the abc file.
<Sysname>diagnostic keyinfo chassis 1 slot 2 save abc
Parallel execution of this command causes errors. Please make sure this command is not being executed by other users. Continue? [Y/N]:y
Processing, please wait...Elapsed 0:0:9
Related commands
diagnostic keyinfo upload
diagnostic keyinfo upload
Use diagnostic keyinfo upload to collect and upload card or device key information to a server.
Syntax
diagnostic keyinfo [ chassis chassis-number [ slot slot-number ] ] upload { tftp server-ip | ftp server-ip username } filename
Views
User view
Predefined user roles
network-admin
Parameters
chassis chassis-number: Specifies a member device in the cluster by its member ID. If you do not specify a member device, this command collects and uploads key information on all member devices.
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command collects and uploads key information on all cards.
tftp server-ip: Specifies a TFTP server by its IP address.
ftp server-ip username: Specifies an FTP server by its IP address. The username argument is the username for logging in to the FTP server.
filename: Saves the key information to a file. The filename argument is a case-sensitive string that can have a maximum of 31 characters.
Examples
# Collect and upload key information for a card to the abc file on a server.
<Sysname>diagnostic keyinfo chassis 1 slot 2 upload tftp 1.1.1.1 abc
Parallel execution of this command causes errors. Please make sure this command is not being executed by other users. Continue? [Y/N]:y
Processing, please wait...Elapsed 0:0:9
Related commands
diagnostic keyinfo save
display alarm
Use display alarm to display alarm information.
Syntax
display alarm [ chassis chassis-number slot slot-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
chassis chassis-number slot slot-number: Specifies a card on a cluster member device. The chassis-number argument represents the member ID of the cluster member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command displays alarm information for all cards.
Usage guidelines
This command is supported only on the default MDC.
Examples
# Display alarm information.
<Sysname> display alarm
Chassis Slot CPU Level Info
1 9 0 ERROR Board is 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: · Board is 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. · 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
mdc-admin
mdc-operator
Examples
# Display the system time and date when the time zone is not specified.
<Sysname> display clock
10:09:00 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 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 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
mdc-admin
mdc-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 ] [ chassis chassis-number slot slot-number [ cpu cpu-number [ core { core-number | all } ] ] ]
display cpu-usage [ control-plane | data-plane ] [ summary ] [ chassis chassis-number slot slot-number [ cpu cpu-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
control-plane: Displays CPU usage statistics for the control plane.
data-plane: Displays CPU usage statistics for the data plane.
summary: Displays CPU usage statistics in table form. If you do not specify this keyword, the command displays CPU usage statistics in text form.
chassis chassis-number slot slot-number: Specifies a card on a cluster member device. The chassis-number argument represents the member ID of the cluster member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command displays CPU usage statistics for all cards.
cpu cpu-number: Specifies a CPU by its number.
core core-number: Specifies a CPU core by its number.
core all: Specifies all CPU cores.
Usage guidelines
Executing this command on an MDC displays the current CPU usage statistics for the MDC.
Examples
# Display the current CPU usage statistics in text form.
<Sysname> display cpu-usage
Chassis 1 Slot 8 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 summary
Chassis Slot CPU Last 5 sec Last 1 min Last 5 min
1 8 0 0% 1% 1%
Table 2 Command output
Field |
Description |
x% in last 5 seconds Last 5 sec |
Average CPU usage during the most recent 5-second interval. |
y% in last 1 minute Last 1 min |
Average CPU usage during the most recent 1-minute interval. |
z% in last 5 minutes Last 5 min |
Average CPU 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 [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]
Views
Any view
Predefined user roles
network-admin
mdc-admin
Parameters
chassis chassis-number slot slot-number: Specifies a card on a cluster member device. The chassis-number argument represents the member ID of the cluster member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command displays the CPU usage monitoring settings for the global active MPU.
cpu cpu-number: Specifies a CPU by its number.
Usage guidelines
Executing this command on an MDC displays CPU usage monitoring settings for the MDC.
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 minor alarm threshold is 80%.
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. |
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 ] [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-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.
chassis chassis-number slot slot-number: Specifies a card on a cluster member device. The chassis-number argument represents the member ID of the cluster member device. The slot-number argument represents the slot number of the card. If you specify a process but do not specify a card, this command displays the statistics for the process on the global active MPU. If you do not specify any options, this command displays the statistics for all processes on all cards.
cpu cpu-number: Specifies a CPU by its number. If you specify a process but do not specify a CPU, this command displays the statistics for the default CPU. If you do not specify a process or CPU, this command displays the historical statistics for all CPUs.
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.
Executing this command on an MDC displays the historical CPU usage statistics for the MDC.
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 (Chassis 1 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 on chassis 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 | harddisk | usb ] [ chassis chassis-number [ slot slot-number [ subslot subslot-number ] ] | verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
flash: Displays flash memory information.
harddisk: Displays hard disk information.
usb: Displays USB interface information.
chassis chassis-number: Specifies a cluster member device by its member ID. If you do not specify a member device, this command displays information for all member devices.
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays information for all cards.
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, harddisk, and usb keywords, this command displays information about cards.
Examples
# Display device information.
<Sysname> display device
Slot No. Board type Status Primary SubSlots
---------------------------------------------------------------------
1/1 CR-LPU-4004 Startup N/A 4
1/2 CR-19K-LPU-CC08 Startup N/A 0
1/3 CR-LPU-CC08 Startup N/A 0
1/8 CR-19K-MPU-08A Normal Master 0
1/9 CR-19K-MPU-08A Startup Standby 0
1/10 CR-19K-SFU-08C Startup N/A 0
+: Next Master
*: Local Master
Table 4 Command output
Field |
Description |
Board Type |
Hardware type of the card. |
Status |
Card status: · Startup—The card has started up. · Normal—The card is operating correctly. · Fault—The card is faulty and cannot start up. · Disable—The card has been powered off manually by using the power-supply off command. · Wait—The card is waiting to be powered on. |
Primary |
Card role: · Standby—The card is the standby MPU. · Master—The card is the active MPU. |
SubSlots |
Maximum number of subcards that the card supports. |
+: Next Master |
Global standby MPU. |
*: Local Master |
Local active MPU. |
display device manuinfo
Use display device manuinfo to display electronic label information for the device.
Syntax
display device manuinfo [ chassis chassis-number [ slot slot-number [ subslot subslot-number ] ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
chassis chassis-number: Specifies a cluster member device by its member ID. If you do not specify a member device, this command displays electronic label information for all member devices.
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays electronic label information of all cards.
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 chassis 1 slot 8
Chassis 1:
Slot 8 CPU 0:
DEVICE_NAME : LSXM1SUP08C0
DEVICE_SERIAL_NUMBER : 210231A5WFH172000079
MAC_ADDRESS : NONE
MANUFACTURING_DATE : 2017-03-04
VENDOR_NAME : H3C
Table 5 Command output
Field |
Description |
DEVICE_NAME |
Device name. |
DEVICE_SERIAL_NUMBER |
Serial number. |
MAC_ADDRESS |
MAC address. |
MANUFACTURING_DATE |
Manufacturing date. |
VENDOR_NAME |
Vendor name. |
display device manuinfo chassis-only
Use display device manuinfo chassis-only to display electronic label information for the backplane.
Syntax
display device manuinfo chassis chassis-number chassis-only
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
chassis chassis-number: Specifies a cluster member device by its member ID.
Usage guidelines
This command is supported only on the default MDC.
Examples
# Display electronic label information for the backplane.
<Sysname> display device manuinfo chassis 1 chassis-only
Chassis 1:
Chassis self:
DEVICE_NAME : backplane
DEVICE_SERIAL_NUMBER : 210235A36L1234567890
MAC_ADDRESS : NONE
MANUFACTURING_DATE : 2015-01-20
VENDOR_NAME : H3C
display device manuinfo fan
Use display device manuinfo fan to display electronic label information for a fan tray.
Syntax
display device manuinfo chassis chassis-number fan fan-id
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
chassis chassis-number: Specifies a cluster member device by its member ID.
fan-id: Specifies a fan tray by its ID.
Usage guidelines
This command is supported only on the default MDC.
Examples
# Display electronic label information for a fan tray.
<Sysname> display device manuinfo chassis 1 fan 1
Chassis 1:
Fan 1:
DEVICE_NAME : LSXM108CFAN
DEVICE_SERIAL_NUMBER : 210231A5WGX173000005
MAC_ADDRESS : NONE
MANUFACTURING_DATE : 2017-03-12
VENDOR_NAME : H3C
display device manuinfo power
Use display device manuinfo power to display electronic label information for a power supply.
Syntax
display device manuinfo chassis chassis-number power power-id
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
chassis chassis-number: Specifies a cluster member device by its member ID.
power-id: Specifies a power supply by its ID.
Usage guidelines
This command is supported only on the default MDC.
Examples
# Display electronic label information for a power supply.
<Sysname> display device manuinfo chassis 1 power 7
Chassis 1:
Power 7:
DEVICE_NAME : PSR2400-54A
DEVICE_SERIAL_NUMBER : 210231A2SNH156000011
MAC_ADDRESS : NONE
MANUFACTURING_DATE : 2015-06-07
VENDOR_NAME : H3C
display device manuinfo power-tray
Use display device manuinfo power-tray to display electronic label information for a power tray.
Syntax
display device manuinfo chassis chassis-number power-tray pt-id
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
chassis chassis-number: Specifies a cluster member device by its member ID.
pt-id: Specifies a power tray by its ID.
Examples
# Display electronic label information for power tray 1 of member device 1.
<Sysname> display device manuinfo chassis 1 power-tray 1
Chassis 1:
PowerTray 1:
DEVICE_NAME : PowerTray
DEVICE_SERIAL_NUMBER : 210235A36L1234567890
MAC_ADDRESS : NONE
MANUFACTURING_DATE : 2017-01-20
VENDOR_NAME : H3C
display device uptime
Use display device uptime to display information about device uptime since the latest startup.
Syntax
display device uptime
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Examples
# Display information about device uptime since the latest startup.
<Sysname> display device uptime
Slot No. Board Type Status Primary UP time(DD:HH:MM)
1 LSQM2MPUC0 Normal Master 0000:01:43
Table 6 Command output
Field |
Description |
Board Type |
Card model. |
Status |
Card status: · Normal—The card is operating correctly. · Startup—The card is starting up. · Wait—The card cannot be powered on because of insufficient power. · Absent—The slot is not installed with a card. · Fault—The card is faulty and cannot start up. · Disable—The card is powered off separately. |
Primary |
Card role: · Master—Global active MPU. · Standby—Global standby MPU. |
UP time(DD:HH:MM) |
Device uptime since the latest startup. |
display diagnostic-file
Use display diagnostic-file to display the contents of diagnostic files on the device.
Syntax
display diagnostic-file [ bootlog | diagfile | diagmon | flowmon | logfile | tracefile ]* [ last modification [ interval ] ] [ list ] [ chassis chassis-number [ slot slot-number ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
bootlog: Specifies the boot log files. This keyword is supported only on the default MDC.
diagfile: Specifies the diagnostic log files.
diagmon: Specifies the diagnostic monitor log files. This keyword is supported only on the default MDC.
flowmon: Specifies the flow monitor log files. This keyword is supported only on the default MDC.
logfile: Specifies the log files.
tracefile: Specifies the trace log files.
last modification [ interval ]: Specifies a time range to display diagnostic files the most recent modification of which occurred during the time range. The last modification argument specifies a past time period from the current system time in hours, in the range of 1 to 86400. The interval argument specifies a time length from the start time of the time period specified by the ast modification argument in hours, in the range of 1 to 720. If you do not specify the last modification argument, the system displays the diagnostic files the most recent modification of which occurred during the past 48 hours. If you specify the last modification argument but not the interval argument, the time length is a maximum of 48 hours.
For example, if you specify the last modification argument as 24 and do not specify the interval argument, the system displays the most recent modification of which occurred during the past 24 hours. If you specify the last modification and interval arguments as 6 and 2, respectively, the system displays the diagnostic files the most recent modification of which occurred during the first 2 hours of the past 6 hours.
list: Displays the diagnostic file list, not the contents of the files.
chassis chassis-number: Specifies a chassis by its number. If you do not specify a chassis number, the system displays the diagnostic files for all chasses.
slot slot-number: Specifies an MPU by its slot number. If you do not specify an MPU, the system displays the diagnostic files for all MPUs.
Usage guidelines
The device records the abnormalities and faults that occurred during the operation in the diagnostic files. You can use this command to view the contents of these diagnostic files for fault location and diagnosis.
Examples
# Display all log files on the device.
<Sysname> display diagnostic-file logfile
#####lcc1#slot20#flash:#####
#####2020-03-28 22:01:17 lcc1#slot20#flash:/logfile8.log#####
@364739%Jan 17 14:05:08:541 2020 CR19000-20_3 ARP/6/DUPIFIP: -Chassis=1-Slot=9;
Duplicate address 23.1.80.1 on interface HundredGigE1/9/1/1.80, sourced from 9ce8-95c4-3b31
%@364740%Jan 17 14:05:08:541 2020 CR19000-20_3 ARP/6/DUPIFIP: -Chassis=1-Slot=9;
Duplicate address 23.1.81.1 on interface HundredGigE1/9/1/1.81, sourced from 9ce8-95c4-3b31
%@364741%Jan 17 14:05:08:541 2020 CR19000-20_3 ARP/6/DUPIFIP: -Chassis=1-Slot=9;
Duplicate address 23.1.82.1 on interface HundredGigE1/9/1/1.82, sourced from 9ce8-95c4-3b31
%@364742%Jan 17 14:05:08:541 2020 CR19000-20_3 ARP/6/DUPIFIP: -Chassis=1-Slot=9;
Duplicate address 23.1.83.1 on interface HundredGigE1/9/1/1.83, sourced from 9ce8-95c4-3b31
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
mdc-admin
mdc-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 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 suffix. 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, the display diagnostic-information command automatically compresses information before saving 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 any feature parameters, this command displays or saves the operating information for all features and modules.
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 (>), and pipeline signs (|). For example, if the device name is A/B, the device name in the file name will be A_B, as in flash:/diag_A_B_20160101-000438.tar.gz.
This command does not support the |, >, or >> option.
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/2012
=================================================
===============display version===============
...
# Save the operating information for all features and modules 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 the test.tar.gz file.
<Sysname> display diagnostic-information test.tar.gz
Diagnostic information is outputting to flash:/test.tar.gz.
Please wait...
Save successfully.
Related commands
gunzip
more
tar extract
display environment
Use display environment to display temperature information.
Syntax
display environment [ chassis chassis-number [ slot slot-number ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
chassis chassis-number: Specifies a cluster member device by its member ID. If you do not specify a member device, this command displays temperature information for all member devices.
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays information for all cards.
Usage guidelines
This command displays information about all temperature sensors in the cluster if you do not specify a cluster member device. If you specify a cluster member device but do not specify a card, this command displays information about all sensors on the member device.
This command is supported only on the default MDC.
Examples
# Display information about all temperature sensors on the device.
<Sysname> display environment
System temperature information (degree centigrade):
------------------------------------------------------------------------------
Slot Sensor Temperature Status LowerLimit WarningLimit AlarmLimit ShutdownLimit
1/8 Inflow 1 25 Normal 0 50 60 127
1/8 Hotspot 1 31 Normal 0 85 92 127
1/8 Hotspot 2 31 Normal 0 88 102 127
1/8 Hotspot 3 32 Normal 0 80 90 127
Table 7 Command output
Field |
Description |
System Temperature information (degree centigrade) |
Temperature information (°C). |
sensor |
Temperature sensor: · hotspot—Hotspot sensor. · inflow—Air inlet sensor. |
Slot |
Sensor position. |
Temperature |
Current temperature. |
LowerLimit |
Lower temperature limit. If the device does not support this field, this field displays NA. |
WarningLimit |
Warning temperature threshold. If the device does not support this field, this field displays NA. |
AlarmLimit |
Alarming temperature threshold. If the device does not support this field, this field displays NA. |
ShutdownLimit |
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 [ chassis chassis-number [ fan-id ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
chassis chassis-number: Specifies a cluster member device by its member ID. If you do not specify a member device, this command displays fan tray operating status information for all member devices.
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.
Usage guidelines
This command is supported only on the default MDC.
Examples
# Display the operating states of all fan trays.
<Sysname> display fan
Frame Frame-State Fan State Speed Mode
-------------------------------------------------------------
1/1 Normal 1 Normal 3194(26%) Silence
1/1 Normal 2 Normal 7356(61%) Silence
1/1 Normal 3 Normal 3173(26%) Silence
1/2 Normal 1 Normal 3268(27%) Silence
1/2 Normal 2 Normal 7228(60%) Silence
1/2 Normal 3 Normal 3188(26%) Silence
Table 8 Command output
Field |
Description |
Frame |
Frame number. |
Frame-State |
Frame status: · Absent—The frame is not installed. · Fault—The frame is faulty. · Normal—The frame is operating correctly. |
Fan |
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. |
Speed |
Fan speed and its percentage of the maximum speed. |
Mode |
Fan operating mode: · Low-temperature. · Silence. · Command. · Equip. |
display health
Use display health to display CPU and memory usage.
Syntax
display health [ chassis chassis-number [ slot slot-number [ cpu cpu-number ] ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
chassis chassis-number slot slot-number: Specifies a card on a cluster member device. The chassis-number argument represents the member ID of the cluster member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command displays CPU and memory usage on all cards.
cpu cpu-number: Specifies a CPU by its number.
Examples
# Display the CPU and memory usage on all cards.
<Sysname> display health
Chassis Slot CPU Role CPU Usage(%) Memory Usage(%) Used/Total(MB)
1 8 0 MPU(Master) 0 23 3821/15960
Table 9 Command output
Field |
Description |
Role |
Card role: · MPU(Master)—Global active MPU. · MPU(Standby)—Global standby MPU. · LPU—LPU. |
CPU Usage(%) |
Average CPU usage during the past 5 seconds, in percentage. |
Memory Usage(%) |
Memory usage in percentage. |
Used/Total(MB) |
Memory usage and total amount of memory in MB. |
display memory
Use display memory to display memory usage information.
Syntax
display memory [ summary ] [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
summary: Displays brief information about memory usage. If you do not specify this keyword, the command displays detailed information about memory usage.
chassis chassis-number slot slot-number: Specifies a card on a cluster member device. The chassis-number argument represents the member ID of the cluster member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command displays memory usage for all MPUs.
cpu cpu-number: Specifies a CPU by its number.
Usage guidelines
Executing this command on an MDC displays memory usage information on the MDC.
Examples
# Display detailed memory usage information.
<Sysname> display memory
Memory statistics are measured in KB:
Chassis 1 Slot 8:
Total Used Free Shared Buffers Cached FreeRatio
Mem: 16343156 4249648 12093508 0 48 540000 76.1%
-/+ Buffers/Cache: 3709600 12633556
Swap: 0 0 0
# Display brief memory usage information.
<Sysname> display memory summary
Memory statistics are measured in KB:
Chassis Slot CPU Total Used Free Buffers Caches FreeRatio
1 8 0 16343156 4249488 12093668 48 540024 76.1%
Table 10 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 [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]
Views
Any view
Predefined user roles
network-admin
Parameters
chassis chassis-number slot slot-number: Specifies a card on a cluster member device. The chassis-number argument represents the member ID of the cluster member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command displays the memory usage thresholds and statistics for the global active MPU.
cpu cpu-number: Specifies a CPU by its number.
Usage guidelines
This command is supported only on the default MDC.
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 threshold:
Minor: 957M
Severe: 638M
Critical: 319M
Normal: 1276M
Current memory state: Normal
Event statistics:
[Back to normal state]
First notification: 0.0
Latest notification: 0.0
Total number of notifications sent: 0
[Enter minor low-memory state]
First notification at: 0.0
Latest notification at: 0.0
Total number of notifications sent: 0
[Back to minor low-memory state]
First notification at: 0.0
Latest notification at: 0.0
Total number of notifications sent: 0
[Enter severe low-memory state]
First notification at: 0.0
Latest notification at: 0.0
Total number of notifications sent: 0
[Back to severe low-memory state]
First notification at: 0.0
Latest notification at: 0.0
Total number of notifications sent: 0
[Enter critical low-memory state]
First notification at: 0.0
Latest notification at: 0.0
Total number of notifications sent: 0
display non-stop-routing status
Use display non-stop-routing status to display nonstop routing (NSR) status information for modules that support the NSR feature.
Syntax
display non-stop-routing status
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Examples
# Display NSR status information for modules that support the NSR feature.
<Sysname> display non-stop-routing status
System NSR status: Not ready
Module name(instance name/process ID) Status
--------------------------------------------------------------
MSDP Not ready
OSPF(1) Ready
OSPF(2) Ready
BGP(default) Ready
BGP(aaa) Ready
PIM Not configured
Table 11 Command output
Field |
Description |
System NSR status |
Global NSR status: · Ready—NSR is in stable state for all NSR-enabled modules. · Not ready—NSR is not in stable state for one or more NSR-enabled modules. · Not configured—NSR is not enabled for any modules. · No standby—No backup hardware exists for NSR. |
Module name(instance name/process ID) |
Name of an NSR-capable module and the instance name or process ID, for example, BGP(default) and OSPF(1). If there is no instance name or process, this field displays only the module name. |
Status |
NSR status: · Ready—NSR is in stable state status for the module. · Not ready—NSR is not in stable state for the module. You cannot perform a process switchover or active/standby switchover. · Not configured—NSR is not enabled for the module. You cannot perform a process switchover or active/standby switchover. |
display power
Use display power to display power supply information.
Syntax
display power [ chassis chassis-number [ power-id | verbose ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
chassis chassis-number: Specifies a cluster member device by its member ID. If you do not specify a member device, this command displays power supply information for all member devices.
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. If you do not specify this keyword, the command displays brief information.
Usage guidelines
This command is supported only on the default MDC.
Examples
# Display brief power supply information.
<Sysname> display power
Chassis InPower(W) OutPower(W)
----------------------------------------------
1 990 753.48
PowerID. State InVoltage(V) InPower(W) OutVoltage(V) OutCurrent(A) OutPower(W)
--------------------------------------------------------------------------------------------------
1/1 Normal 236 635 53.82 8.00 430.56
1/2 Normal 246 355 53.82 6.00 322.92
1/3 Absent -- -- -- -- --
1/4 Absent -- -- -- -- --
1/5 Absent -- -- -- -- --
1/6 Absent -- -- -- -- --
1/7 Absent -- -- -- -- --
1/8 Absent -- -- -- -- --
Table 12 Command output
Field |
Description |
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. |
InVoltage(V) |
Input voltage of the power supply, in volts. If this field is not supported, two hyphens (--) are displayed. |
InPower(W) |
Input power of the power supply, in watts. If this field is not supported, two hyphens (--) are displayed. |
OutVoltage(V) |
Output voltage of the power supply, in volts. If this field is not supported, two hyphens (--) are displayed. |
OutCurrent(A) |
Output current of the power supply, in amperes. If this field is not supported, two hyphens (--) are displayed. |
OutPower(W) |
Output power of the power supply, in watts. If this field is not supported, two hyphens (--) are displayed. |
# Display detailed power supply information.
<Sysname> display power verbose
Chassis InPower(W) OutPower(W)
----------------------------------------------
1 1016 766.93
System power information on chassis 1:
Power modules installed: 2
Power modules usable: 2
Power capacity: 2400(W)
Total DC output: 14.25(A)
PowerID. State InVoltage(V) InPower(W) OutVoltage(V) OutCurrent(A) OutPower(W)
----------------------------------------------------------------------------------------1/1 Normal 236 625 53.82 7.75 417.10
1/2 Normal 246 391 53.82 6.50 349.83
1/3 Absent -- -- -- -- --
1/4 Absent -- -- -- -- --
1/5 Absent -- -- -- -- --
1/6 Absent -- -- -- -- --
1/7 Absent -- -- -- -- --
1/8 Absent -- -- -- -- --
Board power information:
Slot Type Current(A) Power(W) Status
------------------------------------------------------------------
1/0 NA -- 0(0) Absent
1/1 NA -- 0(0) Absent
1/2 NA -- 0(0) Absent
1/3 CR-19K-LPU-4004 -- 626(0)* Startup
1/4 NA -- 0(0) Absent
1/5 NA -- 0(0) Absent
1/6 NA -- 0(0) Absent
1/7 NA -- 0(0) Absent
1/8 CR-19K-MPU-08A -- 47(0)* Normal
1/9 CR-19K-MPU-08A -- 47(0)* Normal
1/10 CR-19K-SFU-08C -- 133(0)* Startup
1/11 Unknown -- 133(0) Disable
1/12 Unknown -- 133(0) Disable
1/13 Unknown -- 142(0) Disable
1/14 NA -- 0(0) Absent
1/15 NA -- 0(0) Absent
Table 13 Command output
Field |
Description |
Power modules installed |
Number of power supplies installed on the device. |
Power modules usable |
Number of available power supplies. |
Power capacity |
Power of a power supply, in watts. |
Power redundant |
Redundant power, in watts. |
Power available |
Available power, in watts. |
Power used |
Total used power, in watts. |
Total DC output |
Total output current of all power supplies, in amperes. |
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. |
InVoltage(V) |
Input voltage of the power supply, in volts. If this field is not supported, two hyphens (--) are displayed. |
InPower(W) |
Input power of the power supply, in watts. If this field is not supported, two hyphens (--) are displayed. |
OutVoltage(V) |
Output voltage of the power supply, in volts. If this field is not supported, two hyphens (--) are displayed. |
OutCurrent(A) |
Output current of the power supply, in amperes. If this field is not supported, two hyphens (--) are displayed. |
OutPower(W) |
Output power of the power supply, in watts. If this field is not supported, two hyphens (--) are displayed. |
Board power information |
Power supply usage information for slots. |
Slot |
Slot number of the card. |
Type |
Card type. |
Current(A) |
Input current of the card, in amperes. If this field is not supported, two hyphens (--) are displayed. |
Power(W) |
Rated power of the card, in watts. If this field is not supported, two hyphens (--) are displayed. |
Status |
Status of the card: · Absent—The slot is not installed with a card. · Fault—The card is faulty. · Normal—The card is operating correctly. |
display power-supply
Use display power-supply to display power supply management information.
Syntax
display power-supply [ chassis chassis-number ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
chassis chassis-number: Specifies a cluster member device by its member ID. If you do not specify a member device, this command displays power supply management information for all member devices.
verbose: Displays detailed power supply management information. If you do not specify this keyword, this command displays the brief information.
Usage guidelines
This command is supported only on the default MDC.
Examples
# Display power supply management information.
<Sysname> display power-supply
Chassis Policy Redundant Num Board Num(Power On) Module Capacity(W)
Power Available(W) Power Used(W)
-------------------------------------------------------------------------------------------------------------------
0 Enabled 0 2 2400
2476 2324
Table 14 Command output
Field |
Description |
Chassis |
Slot number. |
Policy |
Whether power supply management is enabled: · Enabled. · Disabled. |
Redundant Num |
Number of redundant power supplies. |
Board Num(Power On) |
Number of the cards that are powered on. |
Module Capacity(W) |
Power of a power supply, in watts. |
Power Available(W) |
Available power, in watts. |
Power Used(W) |
Used power, in watts. |
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
mdc-admin
mdc-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: 123
// 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
mdc-admin
mdc-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 2011
Completion time : Tue Dec 27 10:44:47 2011
--------------------------------- Job output -----------------------------------
<Sysname>system-view
System View: return to User View with Ctrl+Z.
[Sysname]interface rang gigabitethernet 1/2/0/1 to gigabitethernet 1/2/0/3
[Sysname-if-range]shutdown
Table 15 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
mdc-admin
mdc-operator
Examples
# Display the automatic reboot schedule.
<Sysname> display scheduler reboot
System will reboot at 16:32:00 05/23/2011 (in 1 hours and 39 minutes).
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
mdc-admin
mdc-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 2011
Last execution time : Tue Dec 27 10:44:42 2011
Last completion time : Tue Dec 27 10:44:47 2011
Execution counts : 1
-----------------------------------------------------------------------
Job name Last execution status
shutdown Successful
Table 16 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 [ mdc { mdc-id | all } ] [ summary ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
mdc { mdc-id | all }: Specifies an MDC by its ID or specifies all MDCs.
summary: Displays brief information about system stability and status, including system status, redundancy status, and NSR status. If you do not specify this keyword, the command displays detailed information about system status, redundancy status, and CPU role and status.
Usage guidelines
If you do not specify an MDC, this command displays stability information for the system.
Before performing an ISSU or a switchover, execute this command multiple times to identify whether the system is operating stably. If the value of the System State field is not Stable, you cannot perform an ISSU. If the value of the Redundancy Stable field is not Stable, you cannot perform a switchover.
The device or MDC 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 or MDCs 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 ha service-group command to display the status of HA service groups and identify the groups in batch backup state.
· Use the display system internal process state command in probe view to display service operating status.
Examples
# Display brief information about system stability and status.
<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 : Not ready
Redundancy state : Not ready
Chassis Slot CPU Role State
1 8 0 Active Stable
* 1 1 0 Other Board inserted
* 1 2 0 Other Kernel initiating
* 1 3 0 Other Board inserted
* 1 9 0 Standby Board inserted
* 1 10 0 Other Board inserted
Table 17 Command output
Field |
Description |
System state |
Operating status of all cards: · Stable—All cards are operating stably. · Not ready—One or more cards are not operating stably. You cannot perform an ISSU. |
Redundancy state |
System redundancy status: · Stable—Both MPUs are operating stably. You can perform a switchover. · No redundance—The system has only one MPU. You cannot perform a switchover. · Not ready—The system is not operating stably. You cannot perform a switchover. |
Role |
Role of the card in the system: · Active—The card is the active MPU. · Standby—The card is the standby MPU. · Other—The card is a service card. |
State |
Operating status of the card: · Stable—The card is operating stably. · Board inserted—The card has just been installed. · Kernel initiating—Card kernel is being initialized. · Service starting—Services are starting. · Service stopping—Services are stopping. · HA Batch backup—An HA batch backup is going on. · Interface data batch backup—An interface data batch backup is in progress. · MDC starting—MDCs are starting. · MDC stopping—MDCs are stopping. |
* |
The object is not operating stably. |
Related commands
display device
display ha service-group (High Availability Command Reference)
display mdc (Virtual Technologies Command Reference)
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
mdc-admin
mdc-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 18 shows the common transceiver alarm components. If no error occurs, "None" is displayed.
Table 18 Common transceiver alarm components
Field |
Description |
APD |
Avalanche photo diode |
PCS |
Physical coding sublayer |
PHY XS |
PHY extended sublayer |
PMA/PMD |
Physical medium attachment/physical medium dependent |
power |
Optical power |
REFCLK |
Reference clock |
RX |
Receive |
TEC |
Thermoelectric cooler |
Temp |
Temperature |
TX |
Transmit |
WIS |
WAN interface sublayer |
Examples
# Display the alarms present on the transceiver module in interface GigabitEthernet 1/2/0/1.
<Sysname> display transceiver alarm interface gigabitethernet 1/2/0/1
GigabitEthernet1/2/0/1 transceiver current alarm information:
RX signal loss
RX power low
Table 19 Command output
Field |
Description |
transceiver current alarm information |
Alarms present on the transceiver module. |
RX signal loss |
Input signal loss occurred. |
RX power low |
Received power is low. |
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
mdc-admin
mdc-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 GigabitEthernet 1/2/0/1.
<Sysname> display transceiver diagnosis interface gigabitethernet 1/2/0/1
GigabitEthernet1/2/0/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/2/0/1.
<Sysname> display transceiver diagnosis interface hundredgige 1/2/0/1
HundredGigE1/2/0/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
Optical statistics over PM interval:
Parameter Current Average Min Max
TX Power(dBm) 0 0 -1 1
RX Power(dBm) 0 0 -1 1
Chromatic Dispersion(ps/nm) 3 3 1 5
Differential Group Delay(ps) 1 1 0 2
Q(dB) 0.5 0.3 0.2 0.4
Carrier Frequency(MHz) 200 300 50 500
SNR(dB) 12 15 10 16
SNR of X Polarization(dB) 13.7 N/A N/A N/A
SNR of Y Polarization (dB) 14.5 N/A N/A N/A
BER 6.00E-07 5.00E-07 3.00E-07 1.00E-08
OSNR(dB) 12 15 10 16
OSNR of X Polarization(dB) 13.7 N/A N/A N/A
OSNR of Y Polarization (dB) 14.5 N/A N/A N/A
Table 20 Command output
Field |
Description |
transceiver diagnostic information |
Digital diagnosis information for the transceiver module in the interface. |
Wave.er(nm) |
Wavelength offset in nm, accurate to 0.001 nm. This field is supported only on the CFP2-200G-DCO-Tunable transceiver module. |
Freq.er(GHz) |
Frequency offset in GHz, accurate to 0.1 GHz. This field is supported only on the CFP2-200G-DCO-Tunable transceiver module. |
Temp.(°C) |
Temperature in °C, accurate to 1°C. |
Voltage(V) |
Voltage in V, accurate to 0.01 V. |
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. |
Table 21 Command output for the CFP2-200G-DCO-Tunable transceiver module
Field |
Description |
transceiver diagnostic information |
Digital diagnosis information for the transceiver module in the interface. |
TX power(dBm) |
Transmit power in dBm, accurate to 0.01 dBm. |
RX power(dBm) |
Receive power in dBm, accurate to 0.01 dBm. |
Chromatic dispersion(ps/nm) |
Chromatic dispersion in ps/nm, accurate to 1 ps/nm. |
Differential group delay(ps) |
Differential group delay in ps, accurate to 1 ps. |
Q(dB) |
Q factor in dB, accurate to 0.1 dB. |
Carrier frequency(MHz) |
Carrier frequency offset in MHz, accurate to 1 MHz. |
SNR(dB) |
Signal noise ratio in dB, accurate to 0.1 dB. |
SNR of X polarization(dB) |
SNR of X polarization in dB, accurate to 0.1 dB. |
SNR of Y polarization (dB) |
SNR of Y polarization in dB, accurate to 0.1 dB. |
BER |
Bit error rate in scientific notation, accurate to 2 decimal places. |
OSNR(dB) |
Optical signal to noise ratio in dB, accurate to 0.1 dB. |
OSNR of X polarization(dB) |
OSNR of X polarization in dB, accurate to 0.1 dB. |
OSNR of Y polarization (dB) |
OSNR of X polarization in dB, accurate to 0.1 dB. |
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
mdc-admin
mdc-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 GigabitEthernet 1/2/0/1.
<Sysname> display transceiver interface gigabitethernet 1/2/0/1
GigabitEthernet1/2/0/1 transceiver information:
Transceiver Type : 1000_BASE_SX_SFP
Connector Type : LC
Wavelength(nm) : 850
Transfer Distance(m) : 550(50um),275(62.5um)
Digital Diagnostic Monitoring : YES
Vendor Name : H3C
Table 22 Command output
Field |
Description |
Connector Type |
Connector types: · SC—Fiber connector developed by NTT. · LC—1.25 mm/RJ-45 fiber connector developed by Lucent. · RJ-45. · CX 4. |
Wavelength(nm) |
Central wavelength (in nm) of the transmit laser. If the transceiver supports multiple wavelengths, every two wavelength values are separated by a comma. For a copper cable, this field displays N/A. |
Transfer Distance(xx) |
Transmission distance, where xx indicates the distance unit: · km—Kilometers, for single-mode transceiver modules. · m—Meters, for other transceiver modules. If the transceiver module supports multiple types of transmission media, this field displays the transmission distance for each type, in the form of transmission distance (medium type). Transmission medium types include: · 9 um—9/125 µm single-mode fiber. · 50 um—50/125 µm multimode fiber. · 62.5 um—62.5/125 µm multimode fiber. · TP—Twisted pair. · CX4—CX4 cable. |
Digital Diagnostic Monitoring |
Support for digital diagnosis: · YES—Supported. · NO—Not supported. |
display transceiver itu-channel
Use display transceiver itu-channel to display ITU channel information for transceiver modules.
Syntax
display transceiver itu-channel interface [ interface-type interface-number [ supported-channel ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
interface [ interface-type interface-number ]: Specifies an interface by its type and number. If no interface is specified, this command displays ITU channel information for all transceiver modules.
supported channel: Specifies ITU channels supported on the interface. If this keyword is not specified, the command displays the ITU channel that is being used on the interface.
Usage guidelines
This command is supported only on the CFP2-200G-DCO-Tunable transceiver module.
Only 100-GE interfaces on the CR-HIC-CC01 subcard support the CFP2-200G-DCO-Tunable transceiver module.
Examples
# Display ITU channels used by the transceiver module in HundredGigE 1/2/0/1.
<Sysname> display transceiver itu-channel interface hundredgige 1/2/0/1
Interface Channel WaveLength(nm) Frequency(THz)
HGE1/2/0/1 1 1566.72 191.35
# Display ITU channels supported by the transceiver module in HundredGigE 1/2/0/1.
<Sysname> display transceiver itu-channel interface hundredgige 1/2/0/1 supported-channel
ITU channel settings supported on HundredGigE1/2/0/1 :
Channel WaveLength(nm) Frequency(THz)
1 1566.72 191.35
2 1566.31 191.40
3 1565.90 191.45
4 1565.50 191.50
5 1565.09 191.55
6 1564.68 191.60
7 1564.27 191.65
8 1563.86 191.70
...
Table 23 Command output
Field |
Description |
WaveLength(nm) |
Wavelength of the channel in nm, accurate to 0.01 nm. This field displays a hyphen (-) in the following situations: · No transceiver module is installed on the interface. · The transceiver module does not support specifying an ITU channel number. · The command failed to obtain the ITU channel information. · The device does not support the ITU channel number stored on the transceiver module. |
Frequency(THz) |
Frequency of the channel in THz, accurate to 0.01 THz. This field displays a hyphen (-) in the following situations: · No transceiver module is installed on the interface. · The transceiver module does not support specifying an ITU channel number. · The command failed to obtain the ITU channel information. · The device does not support the ITU channel number stored on the transceiver module. |
Related commands
itu-channel
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
mdc-admin
mdc-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 GigabitEthernet 1/2/0/1.
<Sysname> display transceiver manuinfo interface gigabitethernet 1/2/0/1
GigabitEthernet1/2/0/1 transceiver manufacture information:
Manu. Serial Number : 213410A0000054000251
Manufacturing Date : 2012-09-01
Vendor Name : H3C
Table 24 Command output
Field |
Description |
Manu. Serial Number |
Serial number generated during production of the transceiver module. |
Manufacturing Date |
Date when the electronic label information was written to the transceiver module. |
display transceiver optics interface
Use display transceiver optics interface to display key optical parameters for transceiver modules.
Syntax
display transceiver optics interface [ interface-type interface-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
interface-type interface-number: Specifies an interface by its type and number. If no interface is specified, this command displays key optical parameters for all interfaces that support configuring optical parameters.
Usage guidelines
This command is supported only on the CFP2-200G-DCO-Tunable transceiver module.
Only 100-GE interfaces on the CR-HIC-CC01 subcard support the CFP2-200G-DCO-Tunable transceiver module.
Examples
# Display key optical parameters for the transceiver module in interface HundredGigE 1/2/0/1.
<Sysname> display transceiver optics interface hundredgige 1/2/0/1
HundredGigE1/2/0/1 transceiver optics information:
Modulation mode : Non-diff 15% SD-FEC DP-8QAM Denali Compatible
Grid spacing : 50GHz
Frequency : 194.10THz
Configured transmission power : -5.0dBm
Related commands
optics modulation-mode
optics tx-power
display version
Use display version to display system version information.
Syntax
display version
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Examples
# Display system version information.
<Sysname> display version
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
This command is supported only on the default MDC.
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 2014 at 06:23:54):
*Name : simware-cmw710-boot-a5301.bin
Version : 7.1.053 Alpha 7153
Compile time: Mar 25 2014 15:52:43
*Name : simware-cmw710-system-a5301.bin
Version : 7.1.053 Alpha 7153
Compile time: Mar 25 2014 15:52:43
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
display voltage
Use display voltage to display voltage information.
Syntax
display voltage [ chassis chassis-number [ slot slot-number ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
chassis chassis-number: Specifies a cluster member device by its member ID.
slot slot-number: Specifies a card by its slot number.
Usage guidelines
This command is supported only on the default MDC.
If you do not specify a member device, this command displays voltage information for all member devices. If you specify a member device but do not specify a card, this command displays voltage information for all cards on the member device.
If the voltage is lower than the lower limit or higher than the higher limit, the device sends a log message and a trap.
Examples
# Display voltage information.
<Sysname> display voltage
System voltage information (volt):
------------------------------------------------------------------------------
Slot Sensor Voltage Status Required LowLimit HighLimit Description
1/8 1 3.320 Normal 3.300 2.967 3.626 3.30
1/8 2 5.079 Normal 5.000 4.498 5.497 5.00
1/8 3 1.860 Normal 1.800 1.618 1.978 1.80
1/8 4 1.514 Normal 1.500 1.348 1.649 1.50
1/8 5 12.022 Normal 12.000 10.797 13.195 12.00
1/8 6 0.932 Normal 0.900 0.810 0.990 0.90
1/8 7 1.203 Normal 1.200 1.080 1.320 1.20
1/8 8 1.009 Normal 1.000 0.900 1.100 1.00
1/8 9 1.026 Normal 1.000 0.900 1.100 1.00
1/8 10 1.280 Normal 1.250 1.125 1.375 1.25
Table 26 Command output
Field |
Description |
Sensor |
ID of the sensor. |
Voltage |
Current voltage of the sensor. |
Description |
Description for the sensor. This field is generated by the device. It displays the rated voltage of the sensor. If another sensor has the same rated voltage value, a string is automatically inserted before the rated voltage value to uniquely identify the item. |
fan auto-control-mode
Use fan auto-control-mode to set the fan operating mode.
Use undo fan auto-control-mode to restore the default.
Syntax
fan auto-control-mode chassis chassis-number { low-temperature | silence }
undo fan auto-control-mode chassis chassis-number
Default
Fans operate in silent mode.
Views
System view
Predefined user roles
network-admin
mdc-admin
Parameters
chassis chassis-number: Specifies a cluster member device by its member ID.
low-temperature: Operates at a higher speed to provide better cooling service.
silence: Operates at a lower speed to reduce the noise at the cost of lower cooling service quality. This mode applies to noise-sensitive environments.
Examples
# Set the fan operating mode to silence.
<Sysname> system-view
[Sysname] fan auto-control-mode silence
header
Use header to configure a banner.
Use undo header to delete a banner.
Syntax
header { legal | login | motd | shell } text
undo header { legal | login | motd | shell }
Default
No banner is configured.
Views
System view
Predefined user roles
network-admin
mdc-admin
Parameters
legal: Configures the banner to be displayed before a user inputs the username and password to access the CLI.
login: Configures the banner to be displayed before password or scheme authentication is performed for a login user.
motd: Configures the greeting banner to be displayed before the legal banner appears.
shell: Configures the banner to be displayed before a 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%
itu-channel
Use itu-channel to set the ITU channel number for a transceiver module.
Use undo itu-channel to restore the default.
Syntax
itu-channel channel-number
undo itu-channel
Default
The ITU channel number is 1.
Views
Ethernet interface view
Predefined user roles
network-admin
mdc-admin
Parameters
channel-number: Specifies the ITU channel number.
Usage guidelines
This command is supported only on the CFP2-200G-DCO-Tunable transceiver module.
Only 100-GE interfaces on the CR-HIC-CC01 subcard support the CFP2-200G-DCO-Tunable transceiver module.
Examples
# Set the ITU channel number to 2 for the transceiver module in HundredGigE 1/2/0/1.
<Sysname> system-view
[Sysname] interface hundredgige 1/2/0/1
[Sysname-HundredGigE1/2/0/1] itu-channel 2
Changing the channel number causes the service to be down for a while. Continue? [Y/N]:Y
Related commands
display transceiver itu-channel
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
mdc-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 the save-job job to the saveconfig schedule.
<Sysname> system-view
[Sysname] scheduler schedule saveconfig
[Sysname-schedule-saveconfig] job save-job
Related commands
scheduler job
scheduler schedule
memory-threshold
Use memory-threshold to set free-memory thresholds.
Use undo memory-threshold to restore the defaults.
Syntax
memory-threshold [ chassis chassis-number slot slot-number [ cpu cpu-number ] ] minor minor-value severe severe-value critical critical-value normal normal-value
undo memory-threshold [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]
Default
The default settings vary by device model.
Views
System view
Predefined user roles
network-admin
Parameters
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. This threshold must be equal to or less than the normal state threshold. 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. This threshold must be equal to or less than the minor alarm threshold. 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. This threshold must be equal to or less than the severe alarm threshold. 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. This threshold must be equal to or less than the total memory size.
chassis chassis-number slot slot-number: Specifies a card on a cluster member device. The chassis-number argument represents the member ID of the cluster member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command sets free-memory thresholds for the global active MPU.
cpu cpu-number: Specifies a CPU by its number.
Usage guidelines
This command is supported only on the default MDC.
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.
For more information about the alarm thresholds, see Fundamentals Configuration Guide.
# 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
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 [ chassis chassis-number slot slot-number [ cpu cpu-number ] ] usage memory-threshold
undo memory-threshold [ chassis chassis-number slot slot-number [ cpu cpu-number ] ] usage
Default
The memory usage threshold is 100%.
Views
System view
Predefined user roles
network-admin
Parameters
chassis chassis-number slot slot-number: Specifies a card on a cluster member device. The chassis-number argument represents the member ID of the cluster member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command sets the memory usage threshold for the global active MPU.
cpu cpu-number: Specifies a CPU by its number.
memory-threshold: Specifies the memory usage threshold in percentage. The value range is 0 to 100.
Usage guidelines
This command is supported only on the default MDC.
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 [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]
undo monitor cpu-usage enable [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]
Default
CPU usage monitoring is enabled.
Views
System view
Predefined user roles
network-admin
mdc-admin
Parameters
chassis chassis-number slot slot-number: Specifies a card on a cluster member device. The chassis-number argument represents the member ID of the cluster member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command enables CPU usage monitoring for the global active MPU.
cpu cpu-number: Specifies a CPU by its number.
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
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 default settings.
Syntax
monitor cpu-usage interval interval [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]
undo monitor cpu-usage interval [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]
Default
The system samples CPU usage every 1 minute.
Views
System view
Predefined user roles
network-admin
mdc-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.
chassis chassis-number slot slot-number: Specifies a card on a cluster member device. The chassis-number argument represents the member ID of the cluster member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command sets the interval for the global active MPU.
cpu cpu-number: Specifies a CPU by its number.
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 the CPU usage threshold.
Use undo monitor cpu-usage threshold to restore the default.
Syntax
monitor cpu-usage threshold cpu-threshold [ minor-threshold minor-threshold ] [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]
undo monitor cpu-usage threshold [ minor-threshold ] [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]
Default
The CPU usage threshold is 99%.
Views
System view
Predefined user roles
network-admin
mdc-admin
Parameters
cpu-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. If you do not specify this option, the minor CPU usage alarm threshold is 80 percent of the severe CPU usage alarm threshold.
chassis chassis-number slot slot-number: Specifies a card on a cluster member device. The chassis-number argument represents the member ID of the cluster member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command sets the CPU usage threshold for the global active MPU.
cpu cpu-number: Specifies a CPU by its number.
Usage guidelines
The device samples CPU usage at 1-minute intervals. If the sample is greater than a CPU usage alarm threshold, the device sends a trap. If the sample is equal to or less than the CPU usage recovery threshold, the device determines that the CPU usage is normal.
Examples
# Set the severe CPU usage threshold to 80%.
<Sysname> system-view
[Sysname] monitor cpu-usage threshold 80
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 default settings.
Syntax
monitor resend cpu-usage { minor-interval minor-interval | severe-interval severe-interval } * [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]
undo monitor resend cpu-usage [ minor-interval | severe-interval ] [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]
Default
The minor CPU usage alarm resending interval is 300 seconds. The severe CPU usage alarm resending interval is 60 seconds.
Views
System view
Predefined user roles
network-admin
mdc-admin
Parameters
minor-interval minor-interval: Specifies the minor CPU usage alarm resending interval in seconds, a multiple of 5 in the range of 10 to 3600.
severe-interval severe-interval: Specifies the severe CPU usage alarm resending interval in seconds, a multiple of 5 in the range of 10 to 3600.
chassis chassis-number slot slot-number: Specifies a card on a cluster member device. The chassis-number argument represents the member ID of the cluster member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command sets the interval for the global active MPU.
cpu cpu-number: Specifies a CPU by its number.
Usage guidelines
The device samples CPU usage at intervals, and compares the samples with CPU usage thresholds to identify the CPU usage status and send alarms or notifications accordingly.
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. In severe alarm state, the device sends severe alarms periodically until the severe alarm is removed. This command sets the alarm resending intervals.
If you do not specify a keyword for the undo monitor resend cpu-usage command, the command restores the default minor and severe CPU usage alarm resending intervals.
Examples
# Set the minor CPU usage alarm resending interval to 60 seconds for a slot.
<Sysname> system-view
[Sysname] monitor resend cpu-usage minor-interval 60 chassis 1 slot 8 cpu 0
optics modulation-mode
Use optics modulation-mode to specify a modulation mode for a transceiver module.
Use undo optics modulation-mode to restore the default.
Syntax
optics modulation-mode mode
undo optics modulation-mode
Default
The modulation mode of a transceiver module is 1.
Views
100-GE interface view
Predefined user roles
network-admin
mdc-admin
Parameters
mode: Specifies a modulation mode for the transceiver module.
· 0—Diff, QPSK, and 15% SD-FEC Everest Compatible.
· 1—Non-diff, QPSK, and 15% SD-FEC Denali Compatible.
· 2—Non-diff, 8QAM, and 15% SD-FEC Denali Compatible.
· 3—Non-diff, 16QAM, and 15% SD-FEC Denali Compatible.
Usage guidelines
This command is supported only on the CFP2-200G-DCO-Tunable transceiver module.
Only 100-GE interfaces on the CR-HIC-CC01 subcard support the CFP2-200G-DCO-Tunable transceiver module.
Before using this command for a transceiver module, prepare a backup link for the traffic on the current link. This command causes the transceiver module to negotiate mode parameters with its peer and re-establish the link.
Examples
# Set the modulation mode to 0 for the transceiver module in interface HundredGigE 1/2/0/1.
<Sysname> system-view
[Sysname] interface hundredgige 1/2/0/1
[Sysname-HundredGigE1/2/0/1] optics modulation-mode 0
This operation causes the service to be down for a while. Continue? [Y/N]:y
Related commands
display transceiver optics interface
optics tx-power
Use optics tx-power to set the output power for a transceiver module.
Use undo optics txpower to restore the default.
Syntax
optics tx-power tx-power
undo optics tx-power
Default
The output power for a transceiver module is 0 dBm.
Views
100-GE interface view
Predefined user roles
network-admin
mdc-admin
Parameters
tx-power: Specifies the output power in dBm, accurate to 0.1 dBm. The value range is –15.0 to +1.0.
Usage guidelines
This command is supported only on the CFP2-200G-DCO-Tunable transceiver module.
Only 100-GE interfaces on the CR-HIC-CC01 subcard support the CFP2-200G-DCO-Tunable transceiver module.
Before using this command, configure a backup link for the transceiver module and its peer. This command causes the transceiver module to negotiate mode parameters with its peer and re-establish the current link.
Examples
# Set the output power to –14.3 dBm for the transceiver module in interface HundredGigE 1/2/0/1.
<Sysname> system-view
[Sysname] interface hundredgige 1/2/0/1
[Sysname-HundredGigE1/2/0/1] optics tx-power -14.3
This operation causes the service to be down for a while. Continue? [Y/N]:Y
Related commands
display transceiver optics interface
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
This command is supported only on the default MDC.
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.
To access the device configuration without authentication, you must connect to the active MPU and access the BootWare menu while the MPU is starting up.
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
power-supply off
Use power-supply off to power off a card.
Syntax
power-supply off chassis chassis-number slot slot-number [ subslot subslot-number ]
Views
User view
Predefined user roles
network-admin
Parameters
chassis chassis-number slot slot-number: Specifies a card on a cluster member device. The chassis-number argument represents the member ID of the cluster member device. The slot-number argument represents the slot number of the card.
subslot subslot-number: Specifies a subcard by its subslot number. If you do not specify a subcard, this command stops supplying power to all subcards on the card.
Usage guidelines
This command is supported only on the default MDC.
To use this command, you must enable power supply management first.
When power is insufficient, you can power off interface cards that are idle or connected to unimportant network nodes to ensure power supply to critical interface cards.
Examples
# Power off a card.
<Sysname> power-supply off chassis 1 slot 8
Related commands
power-supply policy enable
power-supply on
Use power-supply on to power on a card or subcard.
Syntax
power-supply on chassis chassis-number slot slot-number [ subslot subslot-number ]
Views
User view
Predefined user roles
network-admin
Parameters
chassis chassis-number slot slot-number: Specifies a card on a cluster member device. The chassis-number argument represents the member ID of the cluster member device. The slot-number argument represents the slot number of the card.
subslot subslot-number: Specifies a subcard by its subslot number. If you do not specify a subcard, this command starts power supply to all subcards on the card.
Usage guidelines
This command is supported only on the default MDC.
To use this command, you must enable power supply management first.
Examples
# Power on a card.
<Sysname> power-supply on chassis 1 slot 8
Related commands
power-supply policy enable
power-supply policy enable
Use power-supply policy enable to enable power supply management.
Use undo power-supply policy enable to disable power supply management.
Syntax
power-supply policy chassis chassis-number enable
undo power-supply policy chassis chassis-number enable
Default
Power supply management is disabled.
Views
System view
Predefined user roles
network-admin
Parameters
chassis chassis-number: Specifies a cluster member device by its member ID.
Usage guidelines
This command is supported only on the default MDC.
Examples
# Enable power supply management.
<Sysname> system-view
[Sysname] power-supply policy chassis 1 enable
power-supply policy priority
Use power-supply policy priority to specify a power supply priority for an interface card.
Use undo power-supply policy priority to restore the default.
Syntax
power-supply policy chassis chassis-number slot slot-number priority priority
undo power-supply policy chassis chassis-number slot slot-number priority
Default
The power supply priority is 5 for an interface card.
Views
System view
Predefined user roles
network-admin
Parameters
priority: Specifies the priority value. The value range is 0 to 9. A smaller priority value represents a higher priority.
chassis chassis-number slot slot-number: Specifies an interface card on a cluster member device. The chassis-number argument represents the member ID of the cluster member device. The slot-number argument represents the slot number of the card.
Usage guidelines
This command is supported only on the default MDC.
This command takes effect only if power supply management is enabled.
Specify smaller priority values for critical-service cards so they are preferentially powered.
Examples
# Set the power supply priority for a card to 10.
<Sysname> system-view
[Sysname] power-supply policy chassis 1 slot 2 priority 10
Related commands
power-supply policy enable
power-supply policy redundant
Use power-supply policy redundant to specify the number of redundant power supplies.
Use undo power-supply policy redundant to restore the default.
Syntax
power-supply policy chassis chassis-number redundant module-count
undo power-supply policy chassis chassis-number redundant
Default
The number of redundant power supplies is 0.
Views
System view
Predefined user roles
network-admin
Parameters
chassis chassis-number: Specifies a cluster member device by its member ID.
module-count: Specifies the number of redundant power supplies. To view the value range for this argument, enter a question mark (?) in the place of this argument. The upper limit for the value range is the maximum number of redundant power supplies supported by the system. The actual number of redundant power supplies that you can specify varies by the number of the interface cards and their power consumption. The actual number is smaller than or equal to the maximum number.
Usage guidelines
This command is supported only on the default MDC.
This command takes effect only if power supply management is enabled.
Examples
# Set the number of redundant power supplies to 1.
<Sysname> system-view
[Sysname] power-supply policy chassis 1 redundant 1
Related commands
power-supply policy enable
reboot
Use reboot to reboot the device.
Syntax
reboot [ chassis chassis-number [ slot slot-number [ subslot subslot-number ] ] ] [ force ]
Views
User view
Predefined user roles
network-admin
mdc-admin
Parameters
chassis chassis-number: Specifies a cluster member device by its member ID. If you do not specify a cluster member device, the command reboots all cluster member devices.
slot slot-number: Specifies a card by its slot number. If you do not specify a card, the command reboots the cluster member device.
subslot subslot-number: Specifies a subcard by its subslot number. If you do not specify a subslot number, the command reboots the slot.
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.
If the cluster has only one MPU, rebooting the MPU reboots the entire cluster. If the cluster has a global standby MPU and the MPU is operating correctly, rebooting the global active MPU triggers a switchover.
To ensure correct operation of the cluster and cards, do not trigger a switchover by rebooting the global active MPU if no global standby MPUs are in Stable state. To view the status of global standby MPUs, execute the display system stable state command.
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
Usage guidelines
This command is supported only on the default MDC.
Examples
# Clear job execution log information.
<Sysname> reset scheduler logfile
Related commands
display scheduler logfile
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
Usage guidelines
This command is supported only on the default MDC.
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
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 is disruptive. 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. |
This command is supported only on the default MDC.
The command takes effect after the device reboots.
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
mdc-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
mdc-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
mdc-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: Device reboot interrupts network services. |
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, 2011.
<Sysname> scheduler reboot at 12:00
Reboot system at 12:00:00 06/06/2011 (in 0 hours and 16 minutes). Confirm? [Y/N]:
Related commands
scheduler reboot delay
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
mdc-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, 2011.
<Sysname> scheduler reboot delay 88
Reboot system at 13:16 06/06/2011(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
mdc-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
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
mdc-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
system switchover
Use system switchover to manually trigger an active/standby or master/subordinate switchover.
Syntax
system switchover [ chassis chassis-number ]
Views
System view
Predefined user roles
network-admin
Parameters
chassis chassis-number: Specifies a cluster member device by its member ID.
Usage guidelines
This command is supported only on the default MDC.
On a cluster, you must specify a dual-MPU member device for this command.
· If you specify the master, this command will trigger a global active MPU election. The current global active MPU will reboot and then join the cluster as a global standby MPU.
· If you specify a subordinate member, this command will trigger an active/standby MPU switchover on the member device. The current local active MPU will reboot to join the cluster and act as the local standby MPU on the member device.
Examples
# Manually trigger an active/standby MPU switchover.
<Sysname> system-view
[Sysname] system switchover
This command will trigger the election of a new active slot and reboot the original active slot. Continue? [Y/N]:y
Rebooting the original active slot. Please wait...
# Manually trigger an active/standby switchover in private-mode view or exclusive-mode view.
<Sysname> system-view exclusive
Info: The current configuration is locked.
~[Sysname] system switchover
This operation will clear uncommitted changes. Continue? [Y/N]:y
This command will trigger the election of a new active slot and reboot the original active slot. Continue? [Y/N]:y
Rebooting the original active slot. Please wait...
temperature-limit
Use temperature-limit to set the temperature alarm thresholds.
Use undo temperature-limit to restore the default.
Syntax
temperature-limit chassis chassis-number slot slot-number { hotspot | inflow } sensor-number lowlimit warninglimit [ alarmlimit ]
undo temperature-limit chassis chassis-number slot slot-number { hotspot | inflow } 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
mdc-admin
Parameters
chassis chassis-number: Specifies a cluster member device by its member ID.
slot slot-number: Specifies a card by its slot number.
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.
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.
This command is supported only on the default MDC.
Examples
# Set temperature alarm thresholds for hotspot sensor 1 in a slot.
<Sysname> system-view
[Sysname] temperature-limit chassis 1 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
mdc-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 each other. The most recently configured command takes effect.
Examples
# Configure the device to execute the saveconfig schedule at 01:01 a.m. on May 11, 2011.
<Sysname> system-view
[Sysname] scheduler schedule saveconfig
[Sysname-schedule-saveconfig] time at 1:1 2011/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
mdc-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 each other. The most recently configured command takes effect.
Examples
# Configure the device to execute the saveconfig schedule 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 the saveconfig schedule 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 the saveconfig schedule 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 the saveconfig schedule 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
mdc-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 each other, whichever is configured most recently takes effect.
Examples
# Configure the device to execute the saveconfig schedule 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 the saveconfig schedule 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 the saveconfig schedule 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 the saveconfig schedule 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 the saveconfig schedule 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
usb disable
Use usb disable to disable USB interfaces.
Use undo usb disable to enable USB interfaces.
Syntax
usb disable
undo usb disable
Default
All USB interfaces are enabled.
Views
System view
Predefined user roles
network-admin
Usage guidelines
This command is supported only on the default MDC.
You can use USB interfaces to upload or download files. By default, all USB interfaces are enabled.
Before executing this command, use the umount command to unmount all USB file systems..
Examples
# Unmount all USB file systems before disabling USB interfaces.
<Sysname> umount usba0:
<Sysname> system-view
[Sysname] usb disable
# Enable USB interfaces.
<Sysname> system-view
[Sysname] undo usb disable
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
mdc-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, mdc-admin, mdc-operator, and level-0 to level-15.
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 the 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.
The security log manager user role is mutually exclusive with other user roles. That is, if the security log manager user role has been assigned, the system will automatically remove the existing other user roles. If the other user roles have been assigned, the system will automatically remove the existing security log manager user role.
Examples
# Assign the rolename user role to the test schedule.
<sysname> system-view
[Sysname] scheduler schedule test
[Sysname-schedule-test] user-role rolename
Related commands
command
scheduler schedule