- Table of Contents
- Related Documents
-
Title | Size | Download |
---|---|---|
06-Device management commands | 595.15 KB |
display cpu-usage configuration
display diagnostic-information
display hardware-failure-detection
display kernel memory alloc-failure
display kernel memory fragment free
memory-threshold usage resend-interval
monitor cpu-usage statistics-interval core
monitor cpu-usage threshold core
monitor kernel memory fragment interval
monitor kernel memory fragment ratio
monitor resend cpu-usage core-interval
monitor resend memory-threshold
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 09:00:00 12/07/2013.
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
CAUTION: This command changes the system time, which affects the execution of system time-related features (for example, scheduled tasks) and collaborative operations of the device with other devices (for example, log reporting and statistics collection). Before executing this command, make sure you fully understand its impact on your live network. |
Correct system time is essential to network management and communication. You must configure the system time correctly before you run the device on the network.
For the device to use the local system time, execute the clock protocol none command and this command in turn. The specified system time takes effect immediately. Then, the device uses the clock signals generated by its built-in crystal oscillator to maintain the system time.
If you set the time zone or daylight saving time after you execute this command, the device recalculates the system time. To view the system time, use the display clock command.
A device power cycling operation restores the local system time to the default. You must execute this command again to set the local system time.
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 }
undo clock protocol
Default
The device obtains the UTC time from an NTP time source.
Views
System view
Predefined user roles
network-admin
Parameters
none: Uses the system time set by using the clock datetime command.
ptp: Uses PTP to obtain the UTC time. You must configure PTP correctly. For more information about PTP and PTP configuration, see Network Management and Monitoring Configuration Guide.
ntp: Uses NTP to obtain the UTC time. You must configure NTP correctly. For more information about NTP and NTP configuration, see Network Management and Monitoring Configuration Guide.
Usage guidelines
This command is supported only on BRAS-VMs or FWD-VMs.
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 execute the clock protocol none command, the device uses the locally set system time. The device then uses the clock signals generated by its built-in crystal oscillator to maintain the system time.
· If you execute the clock protocol { ntp | ptp } command, the device obtains the UTC time through NTP or PTP and calculates the system time. The device then periodically synchronizes the UTC time and recalculates the system time.
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 execute this command, the device recalculates the system time. To view the system time, use the display clock command.
Examples
# Configure the device to use the local system time.
<Sysname> system-view
[Sysname] clock protocol none
# Configure the device to use the local system time.
<Sysname> system-view
[Sysname] switchto vm-net-setup
Enter password:
<Sysname-vm-net> system-view
[Sysname-vm-net] clock protocol none
clock summer-time
Use clock summer-time to set the daylight saving time.
Use undo clock summer-time to restore the default.
Syntax
clock summer-time name start-time start-date end-time end-date add-time
undo clock summer-time
Default
The daylight saving time is not set.
Views
System view
Predefined user roles
network-admin
Parameters
name: Specifies a name for the daylight saving time schedule, a case-sensitive string of 1 to 32 characters.
start-time: Specifies the start time in the hh:mm:ss format. The value range for hh is 0 to 23. The value range for mm is 0 to 59. The value range for ss is 0 to 59. The leading zero in a segment can be omitted. If the seconds segment is 0 (hh:mm:00), you can omit it. If both the minutes and seconds segments are 0 (hh:00:00), you can omit both of the segments. For example, to specify 08:00:00, you can enter 8.
start-date: Specifies the start date in one of the following formats:
· MM/DD. The value range for MM is 1 to 12. The value range for DD varies by month.
· month week day, where:
¡ month—Takes January, February, March, April, May, June, July, August, September, October, November, or December.
¡ week—Represents week of the month. It takes first, second, third, fourth, fifth, or last.
¡ day—Takes Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, or Saturday.
end-time: Specifies the end time in the hh:mm:ss format. The value range for hh is 0 to 23. The value range for mm is 0 to 59. The value range for ss is 0 to 59. The leading zero in a segment can be omitted. If the seconds segment is 0 (hh:mm:00), you can omit it. If both the minutes and seconds segments are 0 (hh:00:00), you can omit both of the segments. For example, to specify 08:00:00, you can enter 8.
end-date: Specifies the end date in one of the following formats:
· MM/DD. The value range for MM is 1 to 12. The value range for DD varies by month.
· month week day, where:
¡ month—Takes January, February, March, April, May, June, July, August, September, October, November or December.
¡ week—Represents week of the month. It takes first, second, third, fourth, fifth, or last.
¡ day—Takes Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, or Saturday.
add-time: Specifies the time to be added to the standard time, in the hh:mm:ss format. The value range for hh is 0 to 23. The value range for mm is 0 to 59. The value range for ss is 0 to 59. The leading zero in a segment can be omitted. If the seconds segment is 0 (hh:mm:00), you can omit it. If both the minutes and seconds segments are 0 (hh:00:00), you can omit both of the segments. For example, to specify 08:00:00, you can enter 8.
Usage guidelines
Correct system time is essential to network management and communication. You must configure the system time correctly before you run the device on the network.
After you set the daylight saving time, the device recalculates the system time. To view the system time, use the display clock command.
Make sure all devices on the network are using the same daylight saving time as the local time.
Examples
# Set the system time ahead 1 hour for the period between 06:00:00 on 08/01 and 06:00:00 on 09/01.
<Sysname> system-view
[Sysname] clock summer-time PDT 6 08/01 6 09/01 1
Related commands
clock datetime
clock timezone
display clock
clock timezone
Use clock timezone to set the time zone.
Use undo clock timezone to restore the default.
Syntax
clock timezone zone-name { add | minus } zone-offset
undo clock timezone
Default
The UTC time zone is used.
Views
System view
Predefined user roles
network-admin
Parameters
zone-name: Specifies a time zone by its name, a case-sensitive string of 1 to 32 characters.
add: Adds an offset to the UTC time 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
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
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/0/6.
<Sysname> system-view
[Sysname] scheduler job shutdownGE
[Sysname-job-shutdownGE] command 1 system-view
[Sysname-job-shutdownGE] command 2 interface gigabitethernet 1/0/6
[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
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. *
******************************************************************************
display alarm
Use display alarm to display alarm information.
Syntax
display alarm [ slot slot-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies the entire device. The value is fixed at 0.
Usage guidelines
If a power module, CPU, or fan is operating abnormally on the device, you can use the display alarm command to view the alarm information. To view historical alarms that have been cleared, use the display alarm history command. To view active alarms that were generated in the past and have not been cleared on the device, use the display alarm active command.
Examples
# Display alarm information.
<Sysname> display alarm
Slot CPU Level Info
0 0 ERROR faulty
Table 1 Command output
Field |
Description |
Slot |
The value for this field is fixed at 0. |
Level |
Alarm severity. Possible values include ERROR, WARNING, NOTICE, and INFO, in descending order of severity. |
Info |
Detailed alarm information: · faulty—The card is starting up or faulty. · Fan n is absent—The specified fan is absent. |
display alarm active
Use display alarm active to display information about active alarms.
Syntax
display alarm active [ module module-name ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
module module-name: Specifies a module by its name. If you do not specify a module, this command displays alarm information for all modules.
verbose: Displays detailed information. If you do not specify this keyword, this command displays brief information.
Usage guidelines
If a power module, CPU, or fan is operating abnormally on the device, you can use the display alarm command to view the alarm information. To view historical alarms that have been cleared, use the display alarm history command. To view active alarms that were generated in the past and have not been cleared on the device, use the display alarm active command.
Examples
# Display information about active alarms.
<Sysname> display alarm active
Seq Module Level Time Info
24 BGP Minor 2023-11-08 20:11:55 BGP peer 14.1.1.99 state changed to IDLE.
23 IF Major 2023-11-08 20:33:10 Line protocol state on the interface
Field |
Description |
Seq |
Alarm sequence number, assigned when an alarm occurs. |
Module |
Alarm module name. |
Level |
Alarm severity. The values include Critical, Major, Minor, and Warning, in descending order of severity. |
Time |
Time when the alarm occurs. |
Info |
Detailed alarm information. The values include: · Fan n is absent—The specified fan is absent. · Fan n is failed—The specified fan is abnormal. · Power n is absent—The specified power module is absent. · Power n failed—The specified power module is abnormal. · Temperature is higher than the high-temperature alarming threshold on sensor inflow—The temperature of the specified sensor has exceeded the high-temperature warning threshold. · Memory minor threshold has been exceeded—The amount of free memory space has exceeded the minor alarm threshold. · CPU usage is in minor alarm state—The CPU usage has exceeded the minor alarm threshold. · Interface-name: RX power is high!—The optical power on the specified interface is too high. · Interface-name:The bit error ratio exceeds the upper threshold—The bit error rate of the specified interface has exceeded the upper limit. · SSH user username (IP: IP-Address) connected to the server successfully—The specified SSH user at the specified IP address has logged in to the server successfully. · Member port xx of aggregation group xx changed to the inactive state, because xx.—The specified member port of the specified aggregation group changed to inactive for a reason. · LDP Session ($1, $2) status changed to $3.—The LDP session status changes: ¡ $1—LDP ID of the peer. If the device fails to obtain the LDP ID of the peer, this field displays 0.0.0.0:0. ¡ $2—VPN instance name. If the LDP session belongs to the public network, this field displays public instance. ¡ $3—LDP session status, including, including nonexistent, initialized, openrec, opensent, and operational. · The number of routes received from the BGP peer exceeded the max number of routes that can be received from the peer. (Instance=$1, AFI=$2, SAFI=$3, PeerAddrType=$4, PeerAddr=$5, MaxRouteNum=$6) ¡ $1: BGP instance name. ¡ $2: Address Family Identifier (AFI). ¡ $3: Subsequent Address Family Identifier (SAFI). ¡ $4: IP type of the BGP peer. ¡ $5: IP address of the BGP peer. ¡ $6: The maximum number of routes that the device can receive from a BGP peer. · BGP $1.$2: The number of routes from peer $3 ($4-$5) exceeds the limit $6. ¡ $1: BGP instance name. ¡ $2: VPN instance name. For a log message on public network, this field is null. ¡ $3: IP address of the BGP peer. ¡ $4: Address Family Identifier (AFI). ¡ $5: Subsequent Address Family Identifier (SAFI). ¡ $6: The maximum number of route prefixes that can be received from the peer. · BGP $1.$2: The ratio of the number of routes received from peer $3 ($4-$5) to the number of allowed routes ($6) has reached the threshold ($7). ¡ $1: BGP instance name. ¡ $2: VPN instance name. For a log message on public network, this field is null. ¡ $3: IP address of the BGP peer. ¡ $4: Address Family Identifier (AFI). ¡ $5: Subsequent Address Family Identifier (SAFI). ¡ $6: The maximum number of routes that the device can receive from a BGP peer. ¡ $7: The number of routes received by the device when the percentage of received routes to the maximum number of allowed routes reaches the alarm threshold. · The number of routes received from the BGP peer exceeded the alarm threshold. (Instance=$1, AFI=$2, SAFI=$3, PeerAddrType=$4, PeerAddr=$5, MaxRouteNumber=$6, alarm threshold=$7) ¡ $1: BGP instance name. ¡ $2: Address Family Identifier (AFI). ¡ $3: Subsequent Address Family Identifier (SAFI). ¡ $4: IP type of the BGP peer. ¡ $5: IP address of the BGP peer. ¡ $6: The maximum number of routes that the device can receive from a BGP peer. ¡ $7: The number of routes received by the device when the percentage of received routes to the maximum number of allowed routes reaches the alarm threshold. · Address pool pool-name has run out of assignable subnets · Address pool pool-name has run out of IP addresses · Address pool group pool-group-name has run out of IP addresses · Address pool group pool-group-name has run out of assignable subnets · Address pool pool-name has run out of IPv6 prefix ranges · IPv6 pool pool-name has run out of addresses · Address pool pool-name has run out of IPv6 prefixes · IPv6 pool group pool-group-name has run out of addresses · Address pool group pool-group-name has run out of assignable subnets · Address pool group pool-group-name has run out of IPv6 prefix ranges · Memory alert has been triggered for reaching the minor threshold |
# Display detailed information about active alarms.
<Sysname> display alarm active verbose
Seq 4
Module: BGP
Alarm name: bgpPeerStateChange
Level: Minor
Start time: 2022-05-16 18:58:46
Info: BGP peer 14.1.1.99 state changed to IDLE.
Table 3 Command output
Field |
Description |
Seq |
Alarm sequence number, assigned when an alarm occurs. |
Module |
Alarm module name. |
Level |
Alarm severity. The values include Critical, Major, Minor, and Warning, in descending order of severity. |
Start time |
Time when the alarm occurs. |
Info |
Detailed alarm information. |
Related commands
display alarm
display alarm history
display alarm history
Use display alarm history to display information about historical alarms that have been cleared.
Syntax
display alarm history [ module module-name ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
module module-name: Specifies a module by its name. If you do not specify a module, this command displays alarm information for all modules.
verbose: Displays detailed information. If you do not specify this keyword, this command displays brief information.
Usage guidelines
If a power module, CPU, or fan is operating abnormally on the device, use the display alarm command to view the alarm information. To view historical alarms that have been cleared, use the display alarm history command. To view active alarms that were generated in the past and have not been cleared on the device, use the display alarm active command.
Examples
# Display brief information about historical alarms.
<Sysname> display alarm history
Seq Module Time Info
5 IF 2023-11-08 20:12:21 Line protocol state on the interface GigabitEthernet1/0/6 changed to up.
For information about the fields in the command output, see Table 2.
# Display detailed information about historical alarms.
<Sysname> display alarm history verbose
Seq 4
Module: IF
Alarm name: linkUpDown
Alarm source: interface GigabitEthernet1/0/6
Level: Minor
Start time: 2023-12-27 16:04:59
Info: Line protocol state on the interface GigabitEthernet1/0/6 changed to down.
Recovery time: 2023-12-27 16:08:26
Info: Line protocol state on the interface GigabitEthernet1/0/6 changed to up.
Table 4 Command output
Field |
Description |
Seq |
Alarm sequence number, assigned automatically by the system when an alarm occurs. |
Module |
Alarm module name. |
Alarm source |
Location where the alarm occurs. |
Start time |
Time when the alarm occurs. |
Level |
Alarm severity. The values include Critical, Major, Minor, and Warning, in descending order of severity. |
Recovery time |
Time when the alarm is cleared. |
Info |
Detailed alarm information. The values include: · BGP $1.$2: The ratio of the number of routes received from peer $3 ($4-$5) to the number of allowed routes ($6) has fallen below the threshold ($7). ¡ $1: BGP instance name. ¡ $2: VPN instance name. For a log message on public network, this field is null. ¡ $3: IP address of the BGP peer. ¡ $4: Address Family Identifier (AFI). ¡ $5: Subsequent Address Family Identifier (SAFI). ¡ $6: The maximum number of routes that can be received from the peer. ¡ $7: The number of routes received by the device when the percentage of received routes to the maximum number of allowed routes reaches the alarm threshold. · The number of routes received from the BGP peer decreased below the alarm threshold. (Instance=$1, AFI=$2, SAFI=$3, PeerAddrType=$4, PeerAddr=$5, MaxRouteNumber=$6, alarm threshold=$7). ¡ $1: BGP instance name. ¡ $2: Address Family Identifier (AFI). ¡ $3: Subsequent Address Family Identifier (SAFI). ¡ $4: IP type of the BGP peer. ¡ $5: IP address of the BGP peer. ¡ $6: The maximum number of routes that the device can receive from a BGP peer. ¡ $7: The number of routes received by the device when the percentage of received routes to the maximum number of allowed routes reaches the alarm threshold. · The number of routes received from the BGP peer decreased below the max number of routes that can be received from the peer. (Instance=$1, AFI=$2, SAFI=$3, PeerAddrType=$4, PeerAddr=$5, MaxRouteNum=$6) ¡ $1: BGP instance name. ¡ $2: Address Family Identifier (AFI). ¡ $3: Subsequent Address Family Identifier (SAFI). ¡ $4: IP type of the BGP peer. ¡ $5: IP address of the BGP peer. ¡ $6: The maximum number of routes that the device can receive from a BGP peer. · BGP $1.$2: The number of routes from peer $3 ($4-$5) fell below the limit $6. ¡ $1: BGP instance name. ¡ $2: VPN instance name. For a log message on public network, this field is null. ¡ $3: IP address of the BGP peer. ¡ $4: Address Family Identifier (AFI). ¡ $5: Subsequent Address Family Identifier (SAFI). ¡ $6: The maximum number of routes that the device can receive from a BGP peer. · The subnet usage of pool pool-name has descended to or dropped below 90%. · The IP address usage of pool pool-name has descended to 90%. · The IP address usage of pool group pool-group-name has descended to 90%. · The subnet usage of pool group pool-group-name has descended to or dropped below 90%. · The IPv6 prefix range usage of address pool pool-name has descended to or dropped below 90%. · The IPv6 address usage of pool pool-name has dropped to or below 90%. · The IPv6 prefix usage of pool pool-name has descended to 90%. · The IPv6 address usage of pool group pool-group-name has dropped to or below 90%. · The subnet usage of pool group pool-group-name has descended to or dropped below 90%. · The IPv6 prefix range usage of address pool group pool-group-name has descended to or dropped below 90%. · The memory usage has returned to a normal state. |
Related commands
display alarm
display alarm active
display clock
Use display clock to display the system time, date, time zone, and daylight saving time.
Syntax
display clock
Views
Any view
Predefined user roles
network-admin
network-operator
Examples
# Display the system time and date when the time zone is not specified.
<Sysname> display clock
10:09:00 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
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 ] [ cpu cpu-number [ core { core-number | all } ] ]
display cpu-usage [ control-plane | data-plane ] [ summary ] [ cpu cpu-number ]
Views
Any view
Predefined user roles
network-admin
network-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.
core core-number: Specifies a CPU core by its number.
core all: Specifies all CPU cores.
Usage guidelines
If you do not specify the control-plane or data-plane keyword, the command displays the total CPU usage statistics for the control plane.
If two hyphens (--) are displayed for the CPU usage during the most recent 5-second, 1-minute, and 5-minute intervals, the command might fail to obtain data from the database on the device. Try the command later.
Examples
# Display the current CPU usage statistics in text form.
<Sysname> display cpu-usage
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
CPU Last 5 sec Last 1 min Last 5 min
0 2% 2% 10%
Table 5 Command output
Field |
Description |
x% in last 5 seconds Last 5 sec |
Average CPU or CPU core usage during the most recent 5-second interval. |
y% in last 1 minute Last 1 min |
Average CPU or CPU core usage during the most recent 1-minute interval. |
z% in last 5 minutes Last 5 min |
Average CPU or CPU core usage during the most recent 5-minute interval. |
display cpu-usage configuration
Use display cpu-usage configuration to display CPU usage monitoring settings.
Syntax
display cpu-usage configuration
Views
Any view
Predefined user roles
network-admin
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%.
Current statistics interval is 60 seconds for the following cores: 0 to 3.
Table 6 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 threshold is xxx. |
Severe CPU usage alarm threshold. |
Current minor alarm threshold is xxx. |
Minor CPU usage alarm threshold. |
Current statistics interval is xxx seconds for the following cores: |
CPU core usage statistics interval. |
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 ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
job job-id: Specifies a process by its ID in the range of 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.
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.
In an IRF 3.1 system, follow these guidelines:
· To display the historical CPU usage statistics for a process on a PEX, log in to the PEX, specify the process ID for the command, and execute the command.
· To display the historical CPU usage statistics for a PEX, use one of the following methods:
¡ Log in to the PEX and execute the command without specifying a process ID.
¡ (MDC-capable devices.) Log in to the MDC to which the PEX belongs and execute the command without specifying a process ID.
¡ (MDC-incapable devices.) Execute the command on the parent without specifying a process ID.
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 last 60 minutes (SYSTEM)
The output shows the following items:
· Process name. The name SYSTEM represents the entire system.
· 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 [ cf-card | flash | harddisk | sd-card | usb ] [ subslot subslot-number | verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
cf-card: Displays CF card information.
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 cf-card, flash, harddisk, sd-card, and usb keywords, this command displays information about the device.
Examples
# Display device information.
<Sysname> display device
Slot No. Board Type Status Max Ports
-------------------------------------------------------
0 RPU Normal 6
Table 7 Command output
Field |
Description |
Board Type |
Hardware type. |
Status |
Device status: · Illegal—The device is not operating correctly. · Normal—The device is operating correctly. |
Max Ports |
Maximum number of physical ports that the device supports. |
# Display device information.
<Sysname> display device
Slot No. Board Type Status Primary SubSlots
----------------------------------------------------------------------------
1 RSU Normal Master 0
Table 8 Command output
Field |
Description |
Slot No |
Number of the slot where the card resides. |
Board Type |
Hardware type of the card. |
Status |
Card status. |
Primary |
Card role. |
SubSlots |
Slot number of the subcard. |
# Display detailed device information.
<Sysname> display device verbose
Slot No. Board Type Status Primary SubSlots
----------------------------------------------------------------------------
1 RSU Normal Master 0
Slot 1:
Device Name: H3C RA5100-G-EI
Subslot No. Board Type Status Max Ports
--------------------------------------------------------------
0 Fixed SubCard on Board Normal 20
Slot 1:
Subslot 0
Status: Normal
Type: Fixed SubCard on Board
Hardware: Ver.A
Driver: 1.0
CPLD: 1.0
FPGA1: 5.00
FPGA2: 2.10
Table 9 Command output
Field |
Description |
Slot No |
Slot number of the card. |
Board Type |
Hardware type of the card. |
Status |
Card status. |
Primary |
Card role. |
SubSlots |
Number of subslots on the card. |
Device Name |
Device model. |
Subslot No |
Slot number of the subcard. |
Board Type |
Hardware type of the subcard. |
Status |
Subcard status. |
Max Ports |
Maximum number of ports on the subcard. |
Type |
Hardware type. |
Hardware |
Hardware version. |
Driver |
Driver software version. |
CPLD |
CPLD version. |
FPGA |
FPGA version. |
display device manuinfo
Use display device manuinfo to display electronic label information for the device.
Syntax
display device manuinfo [ subslot subslot-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
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
Slot 0
DEVICE_NAME : aaaa
DEVICE_SERIAL_NUMBER : xxxx
MAC_ADDRESS : 000F-E26A-58EA
MANUFACTURING_DATE : 2012-11-10
VENDOR_NAME : H3C
PRODUCT ID : XXXXXX
Table 10 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 diagnostic-information
Use display diagnostic-information to display or save diagnostic information for features and hardware modules.
Syntax
display diagnostic-information [ hardware | infrastructure | l2 | l3 | service ] [ key-info | verbose ] [ filename ] [ background ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
hardware: Specifies hardware-related diagnostic information.
infrastructure: Specifies diagnostic information for the fundamental features.
l2: Specifies diagnostic information for the Layer 2 features.
l3: Specifies diagnostic information for the Layer 3 features.
service: Specifies diagnostic information for Layer 4 and upper-layer features.
key-info: Displays or saves only critical diagnostic information. The device might have a large amount of diagnostic information if an exception is present or after the device has run for a long period of time. Specifying this keyword reduces the command execution time and helps you focus on critical diagnostic information. If you do not specify this keyword, the command displays or saves both critical and non-critical diagnostic information.
verbose: Saves detailed diagnostic 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.
background: Saves diagnostic information in the background. If you do not specify this keyword, the system displays or saves diagnostic information in the CLI and you cannot execute other commands during the process. It is time consuming if a large amount of diagnostic information is to be collected. If you specify this keyword, the system saves diagnostic information in the background and users can execute other commands in the CLI during the process.
Usage guidelines
You can use one of the following methods to collect diagnostic statistics for diagnostics and troubleshooting:
· Use separate display commands to collect diagnostic information by feature or module by module.
· Use the display diagnostic-information command to collect diagnostic 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 diagnostic 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 diagnostic information.
Examples
# Display the diagnostic 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 diagnostic 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 diagnostic 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.
# Save the diagnostic information in the background to the default file.
<Sysname> display diagnostic-information background
Please input the file name (*.tar.gz)[flash:/diag_Sysname_20201215-163501.tar.gz]:
Diagnostic information is outputting to flash:/diag_Sysname_20201215-163501.tar.gz in the background.
Related commands
gunzip
more
tar extract
display dying-gasp host
Use display dying-gasp host to display poweroff alarm destination host settings.
Syntax
display dying-gasp host
Views
Any view
Predefined user roles
network-admin
network-operator
Examples
# Display poweroff alarm destination host settings.
<Sysname> display dying-gasp host
IPv4 address: 1.1.1.0
Message type: SNMP Trap
Securityname: p1
Version: V1
IPv4 address: 1.1.1.1
Message type: Syslog
Table 11 Command output
Field |
Description |
IPv4 address |
IPv4 address of the poweroff alarm destination host. |
IPv6 address |
IPv6 address of the poweroff alarm destination host. |
VPN instance |
VPN instance to which the poweroff alarm destination host belongs. |
Message type |
Message types that the poweroff alarm destination host supports: · SNMP Trap—SNMP notification. · Syslog—Log message. |
Securityname |
SNMPv1 or SNMPv2c community name. This field is displayed when the message type is SNMP Trap. |
Version |
SNMP version: · v1—SNMPv1. · v2c—SNMPv2c. This field is displayed when the message type is SNMP Trap. |
Related commands
dying-gasp host
display environment
Use display environment to display temperature information.
Syntax
display environment [ slot slot-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies 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 on the device if you do not specify a card.
Examples
# Display information about all temperature sensors on the device.
<Sysname> display environment
System temperature information (degree centigrade):
Slot Subslot Sensor ID Temperature LowerLimit WarningLimit AlarmLimit Shutdown
--------------------------------------------------------------------------------
1 0 inflow 1 36 -20 68 71 N/A
1 0 hotspot 1 49 -10 82 85 N/A
1 0 hotspot 2 58 -10 80 83 85
…
Table 12 Command output
Field |
Description |
System Temperature information (degree centigrade) |
Temperature information (°C). |
Slot |
Slot number. |
Subslot |
Subslot number. |
sensor |
Temperature sensor |
ID |
Temperature sensor ID. |
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. |
Shutdown |
Shutdown temperature threshold. When the sensor temperature reaches the limit, the system shuts down automatically. If the device does not support this field, this field displays NA. |
display fan
Use display fan to display fan tray operating status information.
Syntax
display fan [ slot slot-number [ fan-id ] ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies a device by its slot number. 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.
Examples
# Display the operating states of all fan trays.
<Sysname> display fan
Slot No. Index Status Speedlevel
--------------------------------------
1 1 Normal 28%
Table 13 Command output
Field |
Description |
Slot No |
Slot number of the device. |
Index |
Index of the fan tray on the device. |
Status |
Fan status: · Absent—The slot is not installed with a fan tray. · Fault—The fan is faulty. · Normal—The fan is operating correctly. · FanDirectionFault—The actual airflow direction is not the preferred direction. |
Speedlevel |
Speed level of the fan tray. |
display hardware-failure-detection
Use display hardware-failure-detection to display the hardware failure detection settings and the latest 10 fix records for each card.
Syntax
display hardware-failure-detection
Views
Any view
Predefined user roles
network-admin
network-operator
Usage guidelines
Examples
# Display hardware failure detection settings and fix records.
<Sysname> display hardware-failure-detection
Current level:
chip : isolate
board : isolate
forwarding : warning
Recent record:
--------------------------Slot 0 executed records:-----------------------------
There is no record.
--------------------------Slot 0 trapped records:-----------------------------
There is no record.
Table 14 Command output
Field |
Description |
Current level |
Fix actions specified for hardware failures. |
chip |
Fix action for hardware failures on components of cards. |
board |
Fix action for hardware failures on control paths. |
forwarding |
Fix action for hardware failures on the forwarding plane. |
Recent record |
Recent failure fix records. |
xxx executed records |
Fix records stored on an MPU. |
xxx trapped records |
Trap records stored on an MPU. |
display health
Use display health to display CPU and memory usage.
Syntax
display health [ slot slot-number [ cpu cpu-number ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number [ cpu cpu-number ]: Specifies a CPU on a card. 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. The cpu-number argument represents the number of the CPU. If you specify a card but do not specify a CPU, this command displays all CPU and memory usage on the card.
Examples
# Display the CPU and memory usage.
<Sysname> display health
Slot CPU Role CPU Usage(%) Memory Usage(%) Used/Total(MB)
1 0 MPU(Master) 3 53 4145/7785
Table 15 Command output
Field |
Description |
Role |
Device role. |
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 kernel memory alloc-failure
Use display kernel memory alloc-failure to display kernel memory allocation failure information.
Syntax
display kernel memory alloc-failure
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
cpu cpu-number: Specifies a CPU by its number.
Examples
# Display kernel memory allocation failure information.
<System> display kernel memory alloc-failure
kmalloc_tag failures: 55.
kcalloc_tag failures: 0.
kzalloc_tag failures: 0.
krealloc_tag failures: 0.
kmem_cache_alloc_tag failures: 0.
Table 16 Command output
Field |
Description |
kmalloc_tag failures |
Number of memory allocation failures on the use of kmalloc_tag. |
kcalloc_tag failures |
Number of memory allocation failures on the use of kcalloc_tag. |
kzalloc_tag failures |
Number of memory allocation failures on the use of kzalloc_tag. |
krealloc_tag failures |
Number of memory allocation failures on the use of krealloc_tag. |
kmem_cache_alloc_tag failures |
Number of memory allocation failures on the use of kmem_cache_alloc_tag. |
display kernel memory fragment free
Use display kernel memory fragment free to display the kernel memory fragment statistics.
Syntax
display kernel memory fragment free
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
cpu cpu-number: Specifies a CPU by its number.
Examples
# Display the kernel memory fragment statistics.
<Sysname> display kernel memory fragment free
Kernel memory free ratio: 0.13%
cfq_io_context memory free (in kbytes): 0
LFIB_NhlfeEntryCache26 memory free (in kbytes): 0
LFIB_NhlfeEntryCache74 memory free (in kbytes): 0
L2VFIB_TUNNELBMP_Cache memory free (in kbytes): 0
NAT_SESSION_EXT_INFO memory free (in kbytes): 0
ARP_VSISUP_Entry_cache memory free (in kbytes): 0
LFIB_NhlfeEntryCache1 memory free (in kbytes): 0
FVN_FwdCache19 memory free (in kbytes): 0
...
Table 17 Command output
Field |
Description |
Kernel memory free ratio |
Memory fragment ratio in the kernel space. |
cfq_io_context memory free (in kbytes) |
Memory fragment size in the slab named cfq_io_context, in KB. |
display memory
Use display memory to display memory usage information.
Syntax
display memory [ summary ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
summary: Displays brief information about memory usage. If you do not specify this keyword, the command displays detailed information about memory usage.
Usage guidelines
If two hyphens (--) are displayed for all the fields in a line of the command output, the command might fail to obtain data from the database on the device. Try the command later.
Examples
# Display detailed memory usage information.
<Sysname> display memory
Memory statistics are measured in KB:
Total Used Free Shared Buffers Cached FreeRatio
Mem: 507980 154896 353084 0 488 54488 69.5%
-/+ Buffers/Cache: 99920 408060
Swap: 0 0 0
LowMem: 888420 80776 807644 -- -- -- 90.9%
HighMem: 904128 564844 339284 -- -- -- 37.5%
# Display brief memory usage information.
<Sysname> display memory summary
Memory statistics are measured in KB:
CPU Total Used Free Buffers Caches FreeRatio
0 1029476 325012 704464 2404 143008 68.4%
Low memory statistics are measured in KB:
CPU Total Used Free Buffers Caches FreeRatio
0 739824 375552 364272 -- -- 49.2%
High memory statistics are measured in KB:
CPU Total Used Free Buffers Caches FreeRatio
0 244736 80576 164160 -- -- 67.1%
Table 18 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 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. |
Caches |
Physical memory used for caches. |
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 dma
Use display memory dma to display DMA memory usage information.
Syntax
display memory dma
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
cpu cpu-number: Specifies a CPU by its number.
Examples
# Display DMA memory usage information.
<System> display memory dma
DMA memory statistics measured in KB on the device:
Total Used Free FreeRatio
16384 6140 10244 63%
Table 19 Command output
Field |
Description |
Total |
Total size of the DMA memory space, including the free and used DMA memory. |
Used |
Used DMA memory. |
Free |
Free DMA memory. |
FreeRatio |
Free DMA memory ratio. |
display memory-threshold
Use display memory-threshold to display memory alarm thresholds and statistics.
Syntax
display memory-threshold
Views
Any view
Predefined user roles
network-admin
network-operator
Usage guidelines
For more information about memory usage notifications, see log information containing MEM_EXCEED_THRESHOLD or MEM_BELOW_THRESHOLD.
Examples
# Display memory alarm thresholds and statistics.
<Sysname> display memory-threshold
Memory usage threshold: 85%
Free-memory thresholds:
Minor: 0M
Severe: 0M
Critical: 0M
Normal: 0M
Current free-memory state: Normal
Free-memory event statistics:
[Back to normal state]
First notification: 0.0
Latest notification: 0.0
Total number of notifications sent: 0
[Entered minor alarm state]
First notification at: 0.0
Latest notification at: 0.0
Total number of notifications sent: 0
[Back to minor alarm state]
First notification at: 0.0
Latest notification at: 0.0
Total number of notifications sent: 0
[Entered severe alarm state]
First notification at: 0.0
Latest notification at: 0.0
Total number of notifications sent: 0
[Back to severe alarm state]
First notification at: 0.0
Latest notification at: 0.0
Total number of notifications sent: 0
[Entered critical alarm state]
First notification at: 0.0
Latest notification at: 0.0
Total number of notifications sent: 0
Table 20 Command output
Field |
Description |
Free-memory thresholds Minor Severe Critical Normal |
Free-memory thresholds, including: · Minor—Minor alarm threshold in MB. If this field displays two hyphens (--), the device failed to obtain the minor alarm threshold. · Severe—Severe alarm threshold in MB. If this field displays two hyphens (--), the device failed to obtain the severe alarm threshold. · Critical—Critical alarm threshold in MB. If this field displays two hyphens (--), the device failed to obtain the critical alarm threshold. · Normal—Normal state threshold in MB. If this field displays two hyphens (--), the device failed to obtain the normal state threshold. |
Current free-memory state |
Current state of the free memory in the system: · Normal—Normal state. · Minor—Minor alarm threshold. · Severe—Severe alarm threshold. · Critical—Critical alarm threshold. |
display memory-threshold dma
Use display memory-threshold dma to display DMA memory alarm information.
Syntax
display memory-threshold dma
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
cpu cpu-number: Specifies a CPU by its number.
Examples
# Display DMA memory alarm information.
<Sysname> display memory-threshold dma
Free DMA memory thresholds:
Critical: 2048KB
Normal: 4096KB
Current DMA memory state: Normal
Free memory event statistics:
[Back to normal state]
First notification: 0.0
Latest notification: 0.0
Total number of notifications sent: 0
[Entered to critcal state]
First notificatio: 0.0
Latest notification: 0.0
Total number of notifications sent: 0
display power
Use display power to display power module information.
Syntax
display power [ slot slot-number [ power-id | verbose ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies the device by its slot number. If you do not specify a member device, this command displays power module information for all member devices.
power-id: Specifies a power module by its ID. If you do not specify a power module, this command displays information about all power modules at the specified position.
verbose: Displays detailed information. If you do not specify this keyword, the command displays brief information.
Examples
# Display brief power module information.
<Sysname> display power
Index Status
----------------------
PWR1 Failed
Table 21 Command output
Field |
Description |
Index |
Slot number of the power module. |
Status |
Power module status. · Fault—The power module is faulty. · Normal—The power module is operating correctly. |
# Display detailed power module information.
<Sysname> display power verbose
System power information:
Power modules installed: 1
Power modules usable: 1
Rated power: 2000 W
Usable power: 1495 W
Used power: 139.60 W
Redundant power: 0 W
Total DC output : 2.8 A
PowerID State InVoltage(V) InPower(W) OutVoltage(V) OutCurrent(A) OutPower(W)
1 Normal 220 2000 50 2.8 140
2 Absent -- -- -- -- --
Table 22 Command output
Field |
Description |
Index |
Index of the power module on the device. |
Status |
Power module status. Options include: · Absent—The slot is not installed with a power module. · Fault—The power module is faulty. · Normal—The power module is operating correctly. |
Type |
Type of the power module. |
Description |
Description for the power module. |
Power supply information for chassis 0 |
Device where the power module resides. |
Redundancy mode |
Redundancy mode of the power module. |
Redundancy status |
Redundancy status of the power module. |
Rated system power |
Rated power of the power module. |
Current system power |
Current power of the power module. |
Rated power ratio |
Percentage of the current power of the power module to its rated power. |
display power-supply
Use display power-supply to display power supply management information.
Syntax
display power-supply [ slot slot-number ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies the device by its slot number. If you do not specify the device, this command also displays power supply management information for the device.
verbose: Displays detailed power supply management information. If you do not specify this keyword, this command displays the brief information.
Examples
# Display brief information of power supply management.
<Sysname> display power-supply
Index Status
----------------------
PWR1 Normal
PWR2 Failed
# Display detailed information of power supply management.
<Sysname> display power-supply verbose
Index Status Type Description
-----------------------------------------------------------
PWR1 Normal DC 48V DC Power
PWR2 Failed DC 48V DC Power
Power supply information for slot 1
-----------------------------------------------------------
Redundancy mode : 1 + 1
Redundancy status : Inactive
Rated system power : 150 W
Current system power : 86 W
Rated power ratio : 57.3 %
Table 23 Command output
Field |
Description |
Index |
Index of the power module on the device. |
Status |
Status of the power module. Options include: · Absent—The slot is not installed with a power module. · Failed—The power module is faulty. · Normal—The power module is operating correctly. |
Type |
Type of the power module. |
Description |
Description for the power module. |
Power supply information for chassis 0 |
Device where the power module resides. |
Redundancy mode |
Redundancy mode of the power module. |
Redundancy status |
Redundancy status of the power module. |
Rated system power |
Rated power of the power module. |
Current system power |
Current power of the power module. |
Rated power ratio |
Percentage of the current power of the power module to its rated power. |
display scheduler job
Use display scheduler job to display job configuration information.
Syntax
display scheduler job [ job-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
job-name: Specifies a job by its name, a case-sensitive string of 1 to 47 characters. If you do not specify a job, this command displays configuration information for all jobs.
Examples
# Display configuration information for all jobs.
<Sysname> display scheduler job
Job name: saveconfig
copy startup.cfg backup.cfg
Job name: backupconfig
Job name: 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
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/0/6 to gigabitethernet 1/0/8
[Sysname-if-range]shutdown
Table 24 Command output
Field |
Description |
Logfile Size |
Size of the log file, in bytes. |
Schedule name |
Schedule to which the job belongs. |
Execution time |
Time when the job was started. |
Completion time |
Time when the job was completed. If the job has never been executed or the job does not have any commands, this field is blank. |
Job output |
Commands in the job and their output. |
Related commands
reset scheduler logfile
display scheduler reboot
Use display scheduler reboot to display the automatic reboot schedule.
Syntax
display scheduler reboot
Views
Any view
Predefined user roles
network-admin
network-operator
Examples
# Display the automatic reboot schedule.
<Sysname> display scheduler reboot
System will reboot at 16:32:00 05/23/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
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 25 Command output
Field |
Description |
Schedule type |
Execution time setting of the schedule. If no execution time is specified, this field is not displayed. |
Start time |
Time to execute the schedule for the first time. If no execution time is specified, this field is not displayed. |
Last execution time |
Last time when the schedule was executed. If no execution time is specified, this field is not displayed. If the schedule has never been executed, "Yet to be executed" is displayed for this field. |
Last completion time |
Last time when the schedule was completed. If no execution time is specified, this field is not displayed. |
Execution counts |
Number of times the schedule has been executed. If the schedule has never been executed, this field is not displayed. |
Job name |
Name of a job under the schedule. |
Last execution status |
Result of the most recent execution: · Successful. · Failed. · Waiting—The device is executing the schedule and the job is waiting to be executed. · In process—The job is being executed. · -NA-—The execution time has not arrived yet. To view information about whether the commands in the job has been executed and the execution results, execute the display scheduler logfile command. |
display system stable state
Use display system stable state to display system stability and status information.
Syntax
display system stable state[ summary ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
summary: Displays brief information about system 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
The device/card/MDC/context 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/cards/MDCs/contexts 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 redundancy
NSR state : No standby
# Display system stability and status information.
<Sysname> display system stable state
System state : Stable
Role State
Active Stable
Table 26 Command output
Field |
Description |
System state |
This field displays Stable if the system is operating stably. |
Redundancy state |
System redundancy status: · Stable—The system is operating stably. You can perform a switchover. · No redundancy—The system has only one device. You cannot perform a switchover. · Not ready—The system is not operating stably. You cannot perform a switchover. |
NSR state |
Readiness of modules for nonstop routing: · Ready—All NSR-enabled modules are operating correctly. · Not ready—NSR is not operating correctly. You cannot perform a process or MPU switchover. · No standby—The system has only one device. · Not configured—NSR is not enabled. |
Role |
Device role. The value of this field is fixed at Active. |
State |
Device status: Stable—The device is operating stably. |
* |
The object is not operating stably. |
# Display system stability and status information.
<Sysname> display system stable state
System state : Stable
Redundancy state : No redundancy
Slot CPU Role State
1 0 Active Stable
Table 27 Command output
Field |
Description |
System state |
Operating status of the system: · Stable—The system is operating stably. · Not ready—The system is not operating stably. You cannot perform an ISSU. |
Redundancy state |
System redundancy status: · Stable—The MPUs are operating stably. You can perform a switchover. · No redundancy—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. |
State |
Card status. |
Related commands
display device
display ha service-group (High Availability 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
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
You can use the display transceiver alarm command to display alarms present on transceiver modules.
If no error occurs, None is displayed. The following tables describe the alarm information that might be present on transceiver module.
Table 28 Command output on SFP/SFP28/SFP+ transceiver modules
Field |
Description |
RX signal loss |
Receive signal loss. |
RX power high alarm |
Alarm on a high receive optical power. |
RX power high warning |
Early warning on a high receive optical power. |
RX power low alarm |
Alarm on a low receive optical power. |
RX power low warning |
Early warning on a low receive optical power. |
TX fault |
Transmit fault. |
TX bias high alarm |
Alarm on a high transmit bias current. |
TX bias high warning |
Early warning on a high transmit bias current. |
TX bias low alarm |
Alarm on a low transmit bias current. |
TX power high warning |
Early warning on a high transmit optical power. |
TX power high alarm |
Alarm on a high transmit optical power. |
TX power high warning |
Early warning on a high transmit optical power. |
TX power low alarm |
Alarm on a low transmit optical power. |
TX power low warning |
Early warning on a low transmit optical power. |
Temp high alarm |
Alarm on a high temperature. |
Temp high warning |
Early warning on a high temperature. |
Temp low alarm |
Alarm on a low temperature. |
Temp low warning |
Early warning on a low temperature. |
Voltage high alarm |
Alarm on a high voltage. |
Voltage high warning |
Early warning on a high voltage. |
Voltage low alarm |
Alarm on a low voltage. |
Voltage low warning |
Early warning on a low voltage. |
Transceiver info I/O error |
N/A |
Transceiver info checksum error |
N/A |
Transceiver type and port configuration mismatch |
The transceiver type does not match port configuration. |
Transceiver type not supported by port hardware |
The transceiver type is not supported on the port. |
TEC error |
Thermoelectric Cooler (TEC) fault. This field is available only for the HPE X130 10G SFP+ LC LH80 tunable Transceiver (JL250A), SFP-XG-LH80-Tunable, and CFP2-200G-DCO-Tunable transceiver modules. |
Wavelength unlocked |
Optical signal wavelength is out of lock. This field is available only for the HPE X130 10G SFP+ LC LH80 tunable Transceiver (JL250A), SFP-XG-LH80-Tunable, and CFP2-200G-DCO-Tunable transceiver modules. |
Tx is not ready due to tunning |
The transmitter is not ready when the signal wavelength changes. This field is available only for the HPE X130 10G SFP+ LC LH80 tunable Transceiver (JL250A), SFP-XG-LH80-Tunable, and CFP2-200G-DCO-Tunable transceiver modules. |
Received an ITU channel number request |
An ITU channel number request was received. This field is available only for the HPE X130 10G SFP+ LC LH80 tunable Transceiver (JL250A), SFP-XG-LH80-Tunable, and CFP2-200G-DCO-Tunable transceiver modules. |
Requested ITU channel number is invalid |
The requested ITU channel number is invalid. This field is available only for the HPE X130 10G SFP+ LC LH80 tunable Transceiver (JL250A), SFP-XG-LH80-Tunable, and CFP2-200G-DCO-Tunable transceiver modules. |
Tx dither not supported |
Transmit dithering is not supported. This field is available only for the HPE X130 10G SFP+ LC LH80 tunable Transceiver (JL250A), SFP-XG-LH80-Tunable, and CFP2-200G-DCO-Tunable transceiver modules. |
RX CDR loss of lock |
Receive CDR loss of lock, indicating poor signal. |
TX CDR loss of lock |
Transmit CDR loss of lock, indicating poor signal. |
Examples
# Display the alarms present on the transceiver module in interface GigabitEthernet 1/0/6.
<Sysname> display transceiver alarm interface gigabitethernet 1/0/6
GigabitEthernet1/0/6 transceiver current alarm information:
RX signal loss
RX power low
Table 29 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
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/0/6.
<Sysname> display transceiver diagnosis interface gigabitethernet 1/0/6
GigabitEthernet1/0/6 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
Warning thresholds:
Temp(C) Voltage(V) Bias(mA) RX power(dBM) TX power(dBM)
High 45 3.25 1.25 -15.00 4.00
Low 25 2.85 0.85 -25.00 1.00
Table 30 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 HPE X130 10G SFP+ LC LH80 tunable Transceiver (JL250A), SFP-XG-LH80-Tunable, and CFP2-200G-DCO-Tunable transceiver modules. |
Freq.er(GHz) |
Frequency offset in GHz, accurate to 0.1 GHz. This field is supported only on the HPE X130 10G SFP+ LC LH80 tunable Transceiver (JL250A), SFP-XG-LH80-Tunable, and CFP2-200G-DCO-Tunable transceiver modules. |
Temp(C) |
Temperature in °C, accurate to 1°C. |
Voltage(V) |
Voltage in V, accurate to 0.01 V. |
Total RX power(dBm) |
Total receive power in dBm, accurate to 0.01 dBm. |
Total TX power(dBm) |
Total transmit power in dBm, accurate to 0.01 dBm. |
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. |
Total average launch power(dBm) |
Total average launch power on the multi-lane transceiver module in dBM, accurate to 0.01 dBm. |
Table 31 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
Parameters
interface [ 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/0/6.
<Sysname> display transceiver interface gigabitethernet 1/0/6
GigabitEthernet1/0/6 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 32 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 multi-mode OM2 fiber. · 62.5um—62.5/125 um multi-mode OM1 fiber. · CX4—CX4 cable. · OM3—50 um multi-mode OM3 fiber. · OM4—50 um multi-mode OM4 fiber. · OM5—50 um multi-mode OM5 fiber. · STACK—Stack cable. · TP—Twisted pair. |
Digital Diagnostic Monitoring |
Support for digital diagnosis: · YES—Supported. · NO—Not supported. |
display transceiver manuinfo
Use display transceiver manuinfo to display electronic label information for transceiver modules.
Syntax
display transceiver manuinfo interface [ interface-type interface-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface [ interface-type interface-number ]: Specifies an interface by its type and number. If no interface is specified, this command displays electronic label information for all transceiver modules.
Examples
# Display electronic label information for the transceiver module in interface GigabitEthernet 1/0/6.
<Sysname> display transceiver manuinfo interface gigabitethernet 1/0/6
GigabitEthernet1/0/6 transceiver manufacture information:
Manu. Serial Number : 213410A0000054000251
Manufacturing Date : 2012-09-01
Vendor Name : H3C
Table 33 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 version
Use display version to display system version information.
Syntax
display version
Views
Any view
Predefined user roles
network-admin
network-operator
Examples
# Display system version information.
<Sysname> display version
...
display version-update-record
Use display version-update-record to display startup software image upgrade records.
Syntax
display version-update-record
Views
Any view
Predefined user roles
network-admin
network-operator
Usage guidelines
The device records its current startup software version information whenever it starts up, and records all software version update information. Such information can survive reboots.
Examples
# Display the startup software image upgrade records.
<Sysname> display version-update-record
Record 1 (updated on Aug 23 2023 at 09:44:33):
*Name : ra5300rsu4xx-cmw710-boot-e7752.bin
Version : 7.1.075 ESS 7752
Compile time: Jul 26 2023 11:00:00
*Name : ra5300rsu4xx-cmw710-system-e7752.bin
Version : 7.1.075 ESS 7752
Compile time: Jul 26 2023 11:00:00
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 [ slot slot-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number : Specifies a card by its slot number.
Usage guidelines
If you do not specify a card, this command displays voltage information for all cards.
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 Subslot Channel Status ReqVolta CurVolta LowThreshold HighThreshold
Major Fatal Major Fatal
-------------------------------------------------------------------------------
1 0 1 Absent N/A N/A N/A N/A N/A N/A
1 0 2 Absent N/A N/A N/A N/A N/A N/A
1 0 3 Absent N/A N/A N/A N/A N/A N/A
1 0 4 Absent N/A N/A N/A N/A N/A N/A
1 0 5 Absent N/A N/A N/A N/A N/A N/A
1 0 6 Absent N/A N/A N/A N/A N/A N/A
1 0 7 Absent N/A N/A N/A N/A N/A N/A
1 0 8 Absent N/A N/A N/A N/A N/A N/A
Table 35 Command output
Field |
Description |
Slot |
If the value for this field is not a number, it is the chassis ID. If the value for this field is a number, it is the slot number. |
Subslot |
Subslot number. |
Channel |
Channel number. |
Status |
Status of the voltage sensor. |
ReqVolta |
Rated voltage of the voltage sensor. |
CurVolta |
Current voltage of the voltage sensor. |
LowThreshold |
Low voltage alarm threshold of the voltage sensor. |
HighThreshold |
High voltage alarm threshold of the voltage sensor. |
downlink-mode
Use downlink-mode to set the downlink operating mode.
Use undo downlink-mode to restore the default.
Syntax
downlink-mode { 10g | 20g }
undo downlink-mode
Default
The downlink operating mode is 10 Gbps.
Views
System view
Predefined user roles
network-admin
parameters
10g: Sets the downlink operating mode to 10 Gbps mode.
20g: Sets the downlink operating mode to 20 Gbps mode.
Usage guidelines
The device supports multiple downlink operating modes. If the following restrictions exist, use this task to change the device's downlink operating mode to be the same as the operating mode of downlink devices:
· Some downlink devices support only 10 Gbps mode and 20 Gbps mode.
· The device cannot negotiate a link operating mode automatically with the downlink devices.
To use the 20 Gbps mode, make sure all downlinks and all downlink devices support the mode. Packet loss might occur if a downlink or a downlink device does not support 20 Gbps mode.
Which interfaces on the device are downlink interfaces depends on the device model.
Examples
# Set the downlink operating mode to 10 Gbps mode.
<Sysname> system-view
[Sysname] downlink-mode 10g
Set the downlink mode successfully. Please reboot the device to make the setting take effect.
dying-gasp host
Use dying-gasp host to configure poweroff alarm destination host settings.
Use undo dying-gasp host to remove poweroff alarm destination host settings.
Syntax
dying-gasp host { ip-address | ipv6 ipv6-address } [ vpn-instance vpn-instance-name ] snmp-trap version { v1 | v2c } securityname security-string
dying-gasp host { ip-address | ipv6 ipv6-address } [ vpn-instance vpn-instance-name ] syslog
undo dying-gasp host { ip-address | ipv6 ipv6-address } [ vpn-instance vpn-instance-name ] { snmp-trap | syslog }
Default
No poweroff alarm destination host settings are configured.
Views
System view
Predefined user roles
network-admin
Parameters
ip-address: Specifies the IPv4 address of the destination host to which the device sends the poweroff alarm.
ipv6 ipv6-address: Specifies the IPv6 address of the destination host to which the device sends the poweroff alarm.
vpn-instance vpn-instance-name: Specifies the MPLS L3VPN instance to which the destination host belongs. The vpn-instance-name argument represents the VPN instance name, a case-sensitive string of 1 to 31 characters. If the destination host belongs to the public network, do not specify this option.
snmp-trap: Uses an SNMP notification to send the poweroff alarm.
version: Specifies the SNMP version.
v1: Uses SNMPv1.
v2c: Uses SNMPv2c.
securityname security-string: Specifies an SNMPv1 or SNMPv2c community name, a case-sensitive string of 1 to 32 characters.
syslog: Uses a log message to send the poweroff alarm.
Usage guidelines
The device can send the poweroff alarm by using either or both of an SNMP notification and a log message.
The device can send the poweroff alarm to multiple destination hosts at the same time.
Examples
# Configure the device to send the poweroff alarm to the host at 1.1.1.1 by using an SNMPv1 notification. The community name is public.
<Sysname> system-view
[Sysname] dying-gasp host 1.1.1.1 snmp-trap version v1 securityname public
Related commands
display dying-gasp host
dying-gasp source
dying-gasp source
Use dying-gasp source to specify the source interface for sending the poweroff alarm.
Use undo dying-gasp source to restore the default.
Syntax
dying-gasp source interface-type { interface-number | interface-number.subnumber }
undo dying-gasp source
Default
No source interface is specified. On an IPv4 network, the device uses the primary IPv4 address of the output interface for the route to the destination host as the source address. On an IPv6 network, the device selects a source IPv6 address as defined in RFC 3484.
Views
System view
Predefined user roles
network-admin
Parameters
interface-type { interface-number | interface-number.subnumber }: Specifies a Layer 3 interface or subinterface. The interface-type argument specifies the interface type. The interface-number argument specifies the interface number. The subnumber argument specifies the subinterface number and is in the range of 1 to 4094.
Usage guidelines
The device uses the IPv6 address or primary IPv4 address of the specified source interface as the source address for outgoing poweroff alarm packets. The destination hosts use this address to identify SNMP notifications or log messages received from the device.
If no address is configured for the specified source interface, this command does not take effect. For this command to take effect, assign an address to the source interface.
Examples
# Use the Loopback 1 interface as the source interface for sending the poweroff alarm.
<Sysname> system-view
[Sysname] dying-gasp source loopback 1
Related commands
dying-gasp host
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
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%
job
Use job to assign a job to a schedule.
Use undo job to revoke a job.
Syntax
job job-name
undo job job-name
Default
No job is assigned to a schedule.
Views
Schedule view
Predefined user roles
network-admin
Parameters
job-name: Specifies the job name, a case-sensitive string of 1 to 47 characters.
Usage guidelines
You can assign multiple jobs to a schedule. The jobs in a schedule are executed concurrently.
The jobs to be assigned to a schedule must already exist. To create a job, use the scheduler job command.
Examples
# Assign 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 default.
Syntax
memory-threshold [ ratio ] minor minor-value severe severe-value critical critical-value normal normal-value [ early-warning early-warning-value secure secure-value ]
undo memory-threshold
Default
Minor alarm threshold: 96 MB.
Severe alarm threshold: 64 MB.
Critical alarm threshold: 48 MB.
Normal state threshold: 128 MB.
Views
System view
Predefined user roles
network-admin
Parameters
ratio: Specifies free-memory thresholds in percentage. If you do not specify this keyword, the command sets free-memory thresholds in MB.
minor minor-value: Specifies the minor alarm threshold. To view the value range for this threshold, enter a question mark (?) in the place of the minor-value argument. 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.
cpu cpu-number: Specifies a CPU by its number.
Usage guidelines
To ensure correct operation and improve memory efficiency, the system monitors the amount of free memory space in real time. If the amount of free memory space decreases to or below the minor, severe, or critical alarm threshold, the system issues an alarm to affected service modules or processes.
(On devices that do not support low memory.) You can use the display memory command to display memory usage information.
(On devices that support low memory.) The system monitors only the amount of free low-memory space. You can use the display memory command to display memory usage information.
(On devices with slots that support low memory.) For slots that support low memory, the system monitors only the amount of free low-memory space. You can use the display memory command to display memory usage information. If the LowMem field is displayed for a slot, the slot supports low memory.
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 dma
Use memory-threshold dma to set DMA memory thresholds.
Use undo memory-threshold dma to restore the default.
Syntax
memory-threshold dma [ ratio ] critical critical-value normal normal-value
undo memory-threshold dma
Default
The DMA memory alarm threshold is 2048 KB, and the normal state threshold is 4096 KB.
Views
System view
Predefined user roles
network-admin
network-operator
Parameters
cpu cpu-number: Specifies a CPU by its number.
ratio: Specifies DMA memory thresholds in percentage.
critical critical-value: Specifies the DMA memory alarm threshold. If the ratio keyword is specified, the value range for the critical-value argument is 1 to 100 in percentage. If the ratio keyword is not specified, you can enter a question mark (?) in the place of the critical-value argument to view the value range for the threshold..
normal normal-value: Specifies the normal state threshold. If the ratio keyword is specified, the value range for the normal-value argument is 1 to 100 in percentage. If the ratio keyword is not specified, you can enter a question mark (?) in the place of the normal-value argument to view the value range.
Usage guidelines
To ensure correct operation of the services that require DMA memory, the system monitors the amount of free DMA memory space regularly. If the amount of free DMA memory space decreases to or below the alarm threshold, the system generates a notification indicating that the DMA memory space is insufficient. If the amount of free DMA memory space increases above the normal state threshold, the system generates a notification indicating that the DMA memory space is sufficient.
Examples
# Set the DMA memory alarm threshold and the normal state threshold to 32KB and 96 KB, respectively.
<System> system-view
[System] memory-threshold dma critical 32 normal 96
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 usage memory-threshold
undo memory-threshold usage
Default
The memory usage threshold is 100%.
Views
System view
Predefined user roles
network-admin
Parameters
memory-threshold: Specifies the memory usage threshold in percentage. The value range is 0 to 100.
Usage guidelines
The device samples memory usage at 1-minute intervals. If the sample is greater than the memory usage threshold, the device sends a trap.
Examples
# Set the memory usage threshold to 80%.
<Sysname> system-view
[Sysname] memory-threshold usage 80
Related commands
display memory-threshold
memory-threshold usage resend-interval
Use memory-threshold usage resend-interval to set the memory usage alarm resending interval.
Use undo memory-threshold usage resend-interval to restore the default.
Syntax
memory-threshold usage resend-interval interval-value
undo memory-threshold usage resend-interval
Default
The memory usage alarm resending interval is 300 seconds.
Views
System view
Predefined user roles
network-admin
Parameters
resend-interval interval-value: Specifies the memory usage alarm resending interval in the range of 1 to 3600, in minutes.
Usage guidelines
The device samples memory usage periodically, and compares the sampled value with the memory usage thresholds. If the sampled value exceeds an alarm threshold, the device enters alarm state and generates an alarm (log and trap) to notify the administrator. If the memory usage remains in the alarm state after the memory usage alarm resending interval is reached, the device outputs the alarm again.
Examples
# Set the memory usage alarm resending interval to 60 minutes.
<Sysname> system-view
[Sysname] memory-threshold usage resend-interval 60
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
undo monitor cpu-usage enable
Default
CPU usage monitoring is enabled.
Views
System view
Predefined user roles
network-admin
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 the default.
Syntax
monitor cpu-usage interval interval
undo monitor cpu-usage interval
Default
The system samples CPU usage every 1 minute.
Views
System view
Predefined user roles
network-admin
Parameters
interval: Specifies the sampling interval for CPU usage monitoring. Valid values include 5Sec (5 seconds), 1Min (1 minute), and 5Min (5 minutes), case insensitive.
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 statistics-interval core
Use monitor cpu-usage statistics-interval core to set the CPU core usage statistics interval.
Use undo monitor cpu-usage statistics-interval core to restore the default.
Syntax
monitor cpu-usage statistics-interval interval slot slot-number cpu cpu-number core core-id-list
undo monitor cpu-usage statistics-interval slot slot-number cpu cpu-number core core-id-list
Default
The CPU core usage statistics interval is 60 seconds.
Views
System view
Predefined user roles
network-admin
Parameters
interval: Specifies the CPU core usage statistics interval in seconds. The value range for this argument is 10 to 3600. As a best practice, set this argument to a multiple of the sampling interval, which is fixed at 5 seconds. If you do not do so, the effective statistics interval is the biggest multiple of the sampling interval that is smaller than the setting. For example, if you set this argument to 12 seconds, the effective statistics interval is 10 seconds.
slot slot-number: Specifies a card by its slot number.
cpu cpu-number: Specifies a CPU by its number.
core-id-list: Specifies a space-separated list of up to 10 CPU core items. Each item specifies a CPU core or a range of CPU cores in the form of core-id1 [ to core-id2 ]. The value for core-id2 must be equal to or greater than the value for core-id1.
Usage guidelines
The device samples CPU core usage at 5-second intervals and calculates the average value during each CPU core usage statistics interval. If the value during an interval is greater than a CPU core usage alarm threshold, the device issues an alarm and logs the event.
Examples
# Set the usage statistics interval to 60 seconds for a CPU core.
<Sysname> system-view
[Sysname] monitor cpu-usage statistics-interval 60 slot 1 cpu 0 core 0
Related commands
monitor cpu-usage threshold core
monitor resend cpu-usage core-interval
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 recovery-threshold recovery-threshold ]
undo monitor cpu-usage threshold [ minor-threshold recovery-threshold ]
Default
The severe CPU usage alarm threshold is 99%. The minor CPU usage alarm threshold is 79%.
Views
System view
Predefined user roles
network-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.
cpu cpu-number: Specifies a CPU by its number.
Usage guidelines
CAUTION: If you set the severe CPU usage alarm threshold to a too low value, the device will reach the threshold easily. Normal service processing will be affected. |
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 cpu-usage threshold core
Use monitor cpu-usage threshold core to set CPU core usage alarm thresholds.
Use undo monitor cpu-usage threshold core to restore the default.
Syntax
monitor cpu-usage threshold severe-threshold [ minor-threshold minor-threshold recovery-threshold recovery-threshold ] slot slot-number cpu cpu-number core core-id-list
undo monitor cpu-usage threshold [ minor-threshold recovery-threshold ] slot slot-number cpu cpu-number core core-id-list
Default
The severe CPU usage alarm threshold is 99%, and the minor CPU usage alarm threshold is 79%.
Views
System view
Predefined user roles
network-admin
Parameters
severe-threshold : Specifies the severe CPU core usage alarm threshold in percentage. The value range for this argument is 2 to 100.
minor-threshold minor-threshold: Specifies the minor CPU core usage alarm threshold in percentage. The value range for this argument is 1 to the severe CPU core usage alarm threshold minus 1. If you do not specify this option, the minor CPU core usage alarm threshold is 80 percent of the severe CPU core usage alarm threshold.
recovery-threshold recovery-threshold: Specifies the CPU core usage recovery threshold in percentage. The value range for this argument is 0 to the minor CPU core usage alarm threshold minus 1. If you do not specify this option, the CPU core usage recovery threshold is 70 percent of the severe CPU core usage alarm threshold.
slot slot-number: Specifies a card by its slot number.
cpu cpu-number: Specifies a CPU by its slot number.
core core-id-list: Specifies a space-separated list of up to 10 CPU core items. Each item specifies a CPU core or a range of CPU cores in the form of core-id1 [ to core-id2 ]. The value for core-id2 must be equal to or greater than the value for core-id1.
Usage guidelines
The device samples CPU core usage at 5-second intervals and calculates the average value during each CPU core usage statistics interval. If the value during an interval is greater than a CPU core usage alarm threshold, the device issues an alarm and logs the event.
Examples
# Set the severe CPU core usage alarm threshold to 90% for a CPU core.
<Sysname> system-view
[Sysname] monitor cpu-usage threshold 90 slot 1 cpu 0 core 0
Related commands
display cpu-usage configuration
monitor cpu-usage statistics-interval core
monitor disk-usage disk
Use monitor disk-usage disk to set the disk usage threshold.
Use undo monitor disk-usage disk to restore the default.
Syntax
monitor disk-usage disk disk-name threshold threshold-value
undo monitor disk-usage disk disk-name threshold
Default
The disk usage threshold is 90%.
Views
System view
Predefined user roles
network-admin
Parameters
disk disk-name: Specifies a disk by its name. This option is case sensitive. The system will prompt a parameter error if you enter this option incorrectly.
threshold threshold-value: Specifies the disk usage threshold in percentage, in the range of 1 to 100.
Usage guidelines
After you set the disk usage threshold, the device compares the usage of the disk with the threshold at each sampling. If the usage exceeds the threshold, the device sends a high disk usage alarm to the NETCONF module. For more information about the NETCONF module see Network Management and Monitoring Configuration Guide.
Examples
# Set the disk usage threshold to 80%.
<Sysname> system-view
[Sysname] monitor disk-usage disk flash threshold 80
Related commands
monitor disk-usage interval
monitor disk-usage interval
Use monitor disk-usage interval to set the disk usage sampling interval.
Use undo monitor disk-usage interval to restore the default.
Syntax
monitor disk-usage interval interval
undo monitor disk-usage interval
Default
The disk usage sampling interval is 300 seconds.
Views
System view
Predefined user roles
network-admin
Parameters
interval interval-time: Specifies the disk usage sampling interval in seconds, a multiple of 5 in the range of 5 to 1800.
Usage guidelines
After you set the disk usage sampling interval, the device samples the disk usage at the specified intervals.
Examples
# Set the disk usage sampling interval to 120 seconds.
<Sysname> system-view
[Sysname] monitor disk-usage interval 120
Related commands
monitor disk-usage disk
monitor kernel memory fragment interval
Use monitor kernel memory fragment interval to set the interval for collecting kernel memory fragment information.
Use undo monitor kernel memory fragment interval to restore the default.
Syntax
monitor kernel memory fragment interval interval-value
undo monitor kernel memory fragment interval
Default
The interval is five minutes for collecting kernel memory fragment information.
Views
System view
Predefined user roles
network-admin
network-operator
Parameters
interval-value: Specifies the interval in minutes. The value range is 1 to 65535.
cpu cpu-number: Specifies a CPU by its number.
Usage guidelines
The device collects kernel memory fragment statistics at the intervals specified by this command. To view the statistics and identify whether the kernel memory fragment ratio is normal, execute the display kernel memory fragment free command.
Examples
# Set the interval for collecting memory fragment information to 5 minutes.
<System> system-view
[System] monitor kernel memory fragment interval 5
monitor kernel memory fragment ratio
Use monitor kernel memory fragment ratio to set the kernel memory fragment ratio alarm threshold.
Use undo monitor kernel memory fragment ratio to restore the default.
Syntax
monitor kernel memory fragment ratio ratio-value
undo monitor kernel memory fragment ratio
Default
The kernel memory fragment ratio alarm threshold is 20%.
Views
System view
Predefined user roles
network-admin
network-operator
Parameters
ratio ratio-value: Specifies the kernel memory fragment ratio alarm threshold in percentage, in the range of 1 to 100.
cpu cpu-number: Specifies a CPU by its number.
Usage guidelines
A running kernel thread's process requires memory allocation from the system. The system allocates and releases this memory as a whole. If the process is still running and some memory blocks have been used but are no longer used, these memory blocks will not be released in advance. These free but currently unusable memory blocks are also referred to as memory fragments.
This command enables the device to monitor the kernel memory fragment ratio. If the kernel memory fragment ratio decreases to or below the alarm threshold, the kernel memory usage is low and an alarm notification is generated. If the kernel memory fragment ratio increases above the alarm threshold, the kernel memory usage returns to the normal state and a recovery notification is generated.
Examples
# Set the kernel memory fragment ratio alarm threshold to 80.
<System> system-view
[System] monitor kernel memory fragment ratio 80
monitor resend cpu-usage
Use monitor resend cpu-usage to set CPU usage alarm resending intervals.
Use undo monitor resend cpu-usage to restore the default.
Syntax
monitor resend cpu-usage { minor-interval minor-interval | severe-interval severe-interval } *
undo monitor resend cpu-usage [ minor-interval | severe-interval ]
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
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.
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.
<Sysname> system-view
[Sysname] monitor resend cpu-usage minor-interval 60
monitor resend cpu-usage core-interval
Use monitor resend cpu-usage core-interval to set CPU core usage alarm resending intervals.
Use undo monitor resend cpu-usage core-interval to restore the default.
Syntax
monitor resend cpu-usage core-interval { minor-interval minor-interval | severe-interval severe-interval } * [ slot slot-number [ cpu cpu-number ] ]
undo monitor resend cpu-usage core-interval [ minor-interval | severe-interval ] [ slot slot-number [ cpu cpu-number ] ]
Default
The minor CPU core usage alarm resending interval is 300 seconds and severe CPU core usage alarm resending interval is 60 seconds.
Views
System view
Predefined user roles
network-admin
Parameters
minor-interval minor-interval: Specifies the resending interval for minor CPU core usage alarms in seconds, a multiple of 5 in the range of 10 to 3600.
severe-interval severe-interval: Specifies the resending interval for severe CPU core usage alarms in seconds, a multiple of 5 in the range of 10 to 3600.
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command sets the interval for the active MPU.
cpu cpu-number: Specifies a CPU by its number.
Usage guidelines
The device samples CPU core usage at intervals, and compares the samples with CPU core usage thresholds to identify the CPU core usage status and send alarms or notifications accordingly.
In minor alarm state, the device sends minor alarms periodically until the CPU core 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.
Examples
# Set the resending interval for minor CPU core usage alarms to 100 seconds and the resending interval for severe CPU core usage alarms 60 seconds.
<Sysname> system-view
[Sysname] monitor resend cpu-usage core-interval minor-interval 100 severe-interval 60
monitor resend memory-threshold
Use monitor resend memory-threshold to set free memory depletion alarm resending intervals.
Use undo monitor resend memory-threshold to restore the default.
Syntax
monitor resend memory-threshold { critical-interval critical-interval | early-warning-interval early-warning-interval | minor-interval minor-interval | severe-interval severe-interval } *
undo monitor resend memory-threshold [ critical-interval | early-warning-interval | minor-interval | severe-interval ] *
Default
· Early warning resending interval: 1 hour.
· Minor alarm resending interval: 12 hours.
· Severe alarm resending interval: 3 hours.
· Critical alarm resending interval: 1 hour.
Views
System view
Predefined user roles
network-admin
Parameters
critical-interval critical-interval: Specifies the critical alarm resending interval in hours, in the range of 1 to 48.
minor-interval minor-interval: Specifies the minor alarm resending interval in hours, in the range of 1 to 48.
severe-interval severe-interval: Specifies the severe alarm resending interval in hours, in the range of 1 to 48.
Usage guidelines
The device samples the amount of free memory space periodically and compares the sampled value with free-memory thresholds. If the sampled value decreases to or below a threshold, the device enters a memory depletion alarm state and sends an alarm.
In critical alarm state, the device sends critical alarm notifications periodically until the critical alarm is removed.
In a lower alarm state, the device sends notifications for the alarm state periodically until it enters a higher alarm state or the current alarm is removed.
You can use this command to change the alarm resending intervals.
Examples
# Set the minor memory depletion alarm resending interval to 12 hours.
<Sysname> system-view
[Sysname] monitor resend memory-threshold minor-interval 12
monitor resend memory-threshold dma
Use monitor resend memory-threshold dma to set the DMA memory alarm resending interval.
Use undo monitor resend memory-threshold dma to restore the default.
Syntax
monitor resend memory-threshold dma critical-interval critical-interval
undo monitor resend memory-threshold dma critical-interval
Default
The DMA memory alarm resending interval is 300 seconds.
Views
System view
Predefined user roles
network-admin
Parameters
critical-interval critical-interval: Specifies the resending interval for the DMA memory alarms in seconds, in the range of 10 to 3600.
cpu cpu-number: Specifies a CPU by its number.
Usage guidelines
The device samples DMA memory usage at intervals, and compares the samples with the DMA memory alarm threshold to identify the DMA memory usage status and send alarms or notifications accordingly.
Examples
# Set the resending interval for the DMA memory alarms to 100 seconds.
<Sysname> system-view
[Sysname] monitor resend memory-threshold dma critical-interval 100<Sysname> system-view
password-recovery enable
Use password-recovery enable to enable password recovery capability.
Use undo password-recovery enable to disable password recovery capability.
Syntax
password-recovery enable
undo password-recovery enable
Default
Password recovery capability is enabled.
Views
System view
Predefined user roles
network-admin
Usage guidelines
Password recovery capability controls console user access to the device configuration and SDRAM from BootWare menus.
If password recovery capability is enabled, a console user can access the device configuration without authentication to configure new passwords.
If password recovery capability is disabled, console users must restore the factory-default configuration before they can configure new passwords. Restoring the factory-default configuration deletes the next-startup configuration files.
To enhance system security, disable password recovery capability.
Availability of BootWare menu options depends on the password recovery capability setting. For more information, see the release notes.
Examples
# Disable password recovery capability.
<Sysname> system-view
[Sysname] undo password-recovery enable
reboot
Use reboot to reboot the device.
Syntax
reboot [ slot slot-number ] [ force ]
Views
User view
Predefined user roles
network-admin
Parameters
slot slot-number: Specifies a card by its slot number. If you do not specify a card, the command reboots the entire device.
force: Reboots the device immediately without performing software or hard disk check. If this keyword is not specified, the system first identifies whether the reboot might result in data loss or a system failure. For example, the system identifies whether the main system software image file exists and whether a write operation is in progress on a storage medium. If the reboot might cause problems, the system does not reboot the device.
Usage guidelines
CAUTION: · A reboot might interrupt network services. · Use the force keyword only when the device fails or a reboot command without the force keyword cannot perform a reboot correctly. A reboot command with the force keyword might result in file system corruption because it does not perform data protection. |
If the main startup software images are corrupt or missing, you must re-specify a set of main startup software images before executing the reboot command.
For data security, the device does not reboot if you reboot the device while the device is performing file operations.
Examples
# Reboot the device. Save the running configuration at prompt.
<Sysname> reboot
Start to check configuration with next startup configuration file, please wait.........DONE!
Current configuration will be lost after the reboot, save current configuration? [Y/N]:y
Please input the file name(*.cfg)[flash:/startup.cfg]
(To leave the existing filename unchanged, press the enter key):
flash:/startup.cfg exists, overwrite? [Y/N]:y
Validating file. Please wait...
Configuration is saved to 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 alarm active
Use reset alarm active to clear active alarm information on the device.
Syntax
reset alarm active { all | sequence-number sequence-number }
Default
The active alarm information on the device is not cleared.
Views
System view
Predefined user roles
network-admin
Parameter
all: Specifies all active alarms.
sequence-number sequence-number: Specifies an active alarm by its sequence number, in the range of 1 to 4294967295.
Usage guidelines
When the system has information about active alarms, you can execute this command to manually clear these alarms. After clearance, the system will not display information about these alarms.
Examples
# Clear the active alarm with sequence number 1.
<Sysname> system-view
[Sysname] reset alarm active sequence-number 1
Related commands
display alarm active
display alarm history
reset scheduler logfile
Use reset scheduler logfile to clear job execution log information.
Syntax
reset scheduler logfile
Views
User view
Predefined user roles
network-admin
Examples
# Clear job execution log information.
<Sysname> reset scheduler logfile
Related commands
display scheduler logfile
reset version-update-record
Use reset version-update-record to clear startup software image upgrade records.
Syntax
reset version-update-record
Views
System view
Predefined user roles
network-admin
Examples
# Clear the startup software image upgrade records.
<Sysname> system-view
[Sysname] reset version-update-record
This command will delete all records of version update. Continue? [Y/N]:y
Related commands
display version-update-record
restore factory-default
Use restore factory-default to restore the factory-default configuration for the device.
Syntax
restore factory-default
Views
User view
Predefined user roles
network-admin
Usage guidelines
CAUTION: This command restores the device to the factory default settings. Before using this command, make sure you fully understand its impact on your live network. |
Use this command only when you cannot troubleshoot the device by using other methods, or you want to use the device in a different scenario.
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
Parameters
job-name: Specifies the job name, a case-sensitive string of 1 to 47 characters.
Usage guidelines
A job can be referenced by multiple schedules. In job view, you can assign commands to the job.
Examples
# Create a job named backupconfig and enter job view.
<Sysname> system-view
[Sysname] scheduler job backupconfig
[Sysname-job-backupconfig]
Related commands
command
scheduler schedule
scheduler logfile size
Use scheduler logfile size to set the size of the job execution log file.
Syntax
scheduler logfile size value
Default
The size of the job execution log file is 16 KB.
Views
System view
Predefined user roles
network-admin
Parameters
value: Specifies the size of the job execution log file, in KB. The value range is 16 to 1024.
Usage guidelines
The job execution log file saves the execution information of jobs. If the file is full, old records are deleted to make room for new records. If the size of the log information to be written to the file is greater than the file size, the excessive information is not written to the file.
Examples
# Set the size of the job execution log file to 32 KB.
<Sysname> system-view
[Sysname] scheduler logfile size 32
Related commands
display scheduler logfile
scheduler reboot at
Use scheduler reboot at to specify the reboot date and time.
Use undo scheduler reboot to delete the reboot schedule configuration.
Syntax
scheduler reboot at time [ date ]
undo scheduler reboot
Default
No reboot date or time is specified.
Views
User view
Predefined user roles
network-admin
Parameters
time: Specifies the reboot time in the hh:mm format. The value range for hh is 0 to 23. The value range for mm is 0 to 59.
date: Specifies the reboot date in the MM/DD/YYYY or YYYY/MM/DD format. The value range for YYYY is 2000 to 2035. The value range for MM is 1 to 12. The value range for DD varies by month.
Usage guidelines
CAUTION: This command enables the device to reboot at a scheduled time, which causes service interruption. Before using this command, make sure you fully understand its impact on your live network. |
When the date argument is not specified, the system uses the following rules to determine the reboot time:
· If the reboot time is later than the current time, a reboot occurs at the reboot time of the current day.
· If the reboot time is earlier than the current time, a reboot occurs at the reboot time the next day.
The device supports only one device reboot schedule. If you execute both the scheduler reboot delay and scheduler reboot at commands or execute one of the commands multiple times, the most recent configuration takes effect.
For data security, the system does not reboot at the reboot time if a file operation is being performed.
Examples
# Configure the device to reboot at 12:00 p.m. This example assumes that the current time is 11:43 a.m. on June 6, 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
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: This command enables the device to reboot at a scheduled time, which causes service interruption. Before using this command, make sure you fully understand its impact on your live network. |
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
Parameters
schedule-name: Specifies the schedule name, a case-sensitive string of 1 to 47 characters.
Usage guidelines
You can configure a schedule to have the device automatically run a command or a set of commands without administrative interference.
To configure a schedule:
1. Use the scheduler job command to create a job and enter job view.
2. Use the command command to assign commands to the job.
3. Use the scheduler schedule command to create a schedule and enter schedule view.
4. Use the job command to assign the job to the schedule. You can assign multiple jobs to a schedule. The jobs must already exist.
5. Use the user-role command to assign user roles to the schedule. You can assign up to 64 user roles to a schedule.
6. Use the time at, time once, or time repeating command to specify an execution time for the schedule. You can specify only one execution time for a schedule.
Examples
# Create a schedule named saveconfig.
<Sysname> system-view
[Sysname] scheduler schedule saveconfig
Related commands
job
time at
time once
shutdown-interval
Use shutdown-interval to set the port status detection timer.
Use undo shutdown-interval to restore the default.
Syntax
shutdown-interval interval
undo shutdown-interval
Default
The port status detection timer setting is 30 seconds.
Views
System view
Predefined user roles
network-admin
Parameters
interval: Specifies the port status detection timer value in seconds. The value range is 0 to 300. The value of 0 indicates that port status detection is not automatically performed, and you need to execute the undo shutdown command to restore the port status manually.
Usage guidelines
If the port has been in down state before the timer expires, the device will set the port status to the port's physical status.
If you change the timer setting during port detection, the device compares the new setting (T1) with the time that elapsed since the port was shut down (T).
· If T < T1, the port will be brought up after T1 – T seconds.
· If T ≥ T1, the port is brought up immediately.
For example, the timer setting is 30 seconds. If you change it to 10 seconds 2 seconds after the port is shut down, the port will come up 8 seconds later. If you change the timer setting to 2 seconds 10 seconds after the port is shut down, the port comes up immediately.
Examples
# Set the port status detection timer to 100 seconds.
<Sysname> system-view
[Sysname] shutdown-interval 100
sysname
Use sysname to set the device name.
Use undo sysname to restore the default.
Syntax
sysname sysname
undo sysname
Default
The device name is H3C.
Views
System view
Predefined user roles
network-admin
Parameters
sysname: Specifies a name for the device, a string of 1 to 64 characters.
Usage guidelines
A device name identifies a device in a network and is used in CLI view prompts. For example, if the device name is Sysname, the user view prompt is <Sysname>.
Examples
# Set the name of the device to R2000.
<Sysname> system-view
[Sysname] sysname R2000
time at
Use time at to specify an execution date and time for a non-periodic schedule.
Use undo time to delete the execution date and time configuration for a non-periodic schedule.
Syntax
time at time date
undo time
Default
No execution time or date is specified for a non-periodic schedule.
Views
Schedule view
Predefined user roles
network-admin
Parameters
time: Specifies the schedule execution time in the hh:mm format. The value range for hh is 0 to 23. The value range for mm is 0 to 59.
date: Specifies the schedule execution date in the MM/DD/YYYY or YYYY/MM/DD format. The value range for YYYY is 2000 to 2035. The value range for MM is 1 to 12. The value range for DD varies by month.
Usage guidelines
The specified time (date plus time) must be later than the current system time.
The time at command, the time once command, and the time repeating command overwrite each other. The most recently executed 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
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 executed 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
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 executed 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
user-role
Use user-role to assign user roles to a schedule.
Use undo user-role to remove user roles from a schedule.
Syntax
user-role role-name
undo user-role role-name
Default
A schedule has the user roles of the schedule creator.
Views
Schedule view
Predefined user roles
network-admin
Parameters
role-name: Specifies a user role name, a case-sensitive string of 1 to 63 characters. The user role can be user-defined or predefined. Predefined user roles include network-admin, network-operator, and level-0 to level-15.
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
# Assign the security-audit user role to the test schedule.
<sysname> system-view
[Sysname] scheduler schedule test
[Sysname-schedule-test]user-role security-audit
This operation will delete all other user roles for the schedule. Are you sure? [Y/N]:y
# Change the user role assigned to the test schedule from security-audit to network-admin.
<sysname> system-view
[Sysname] scheduler schedule test
[Sysname-schedule-test]user-role network-admin
This operation will delete security auditor user role for the schedule. Are you sure? [Y/N]:y
Related commands
command
scheduler schedule